Sys03 Bss Database Application

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
REMOTE TRANSCODER BSC SCRIPT BUILDING POWER AND HANDOVER BTS SCRIPT BUILDING PATH
SCRIPT BUILDING CONTROL
CHAPTER 6 CHAPTER 7 APPENDIX A GLOSSARY OF
HOPPING SCRIPT DATABASE BUILDING TERMS
EXERCISE
Cellular Infrastructure Group
ISSUE 10 REVISION 3
SYS03
BSS DATABASE APPLICATION
FOR TRAINING PURPOSES ONLY

ISSUE 10
REVISION 3
SYS03
BSS DATABASE
APPLICATION
FOR TRAINING
PURPOSES ONLY
SYS03
BSS DATABASE APPLICATION
ISSUE 10 REVISION 3
SYS03
BSS Database Application
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 2000

All Rights Reserved
Printed in the U.K.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application i

ISSUE 10 REVISION 3
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 SYS03: BSS Database Application EMOTOROLA LTD. 2000

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

ISSUE 10 REVISION 3
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1
Remote Transcoder Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Remote Transcoder Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Remote Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RXCDR Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RXCDR 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Equipping Terrestrial Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
CIC(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MMS ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Starting Timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Starting Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Circuit Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Add Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Circuit/Channel Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Relationship Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Unequipped Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
XBL Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
XBL Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
XBL Connectivity Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
XBL Connectivity Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Enhanced Terrestrial Circuit Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Link Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Transcoder On-line Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
iv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
MSC Quietone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Downlink DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Audio Volume Control at the GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Enhanced Full Rate Speech (EFR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
EFR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Handovers in EFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Internal Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
External Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
GCLK Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Closed Loop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Chapter 2
BSC Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Base Station Controller (BSC) Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
BSC 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
XBL Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Battery Conservation, Mains Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
External Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
EAS Alarm Text String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
EAS Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BTS Script (site 32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BTS Script (site 33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Statistics Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
MTP Level 3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Signalling Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Emergency Call Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Multiple Encryption Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Circuit Error Rate Monitor (CERM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
EMOTOROLA LTD. 2000 SYS03: BSS Database Application v

ISSUE 10 REVISION 3
Short Message Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Multiple Background Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Point to Point SMS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Traffic Channel SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
RACH Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CRM Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Chapter 3
Power and Handover Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Power and Handover Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MS Measurement Cycle, Traffic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
MS Measurement Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
BSS Measurement Averaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
N and P Voting Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hreqave/Hreqt and N/P Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Diagram Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Oscillation Prevention For MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Oscillation Prevention for BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
The Power Budget Assessment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Downlink RXLEV Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Adapted Power Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Uplink Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Power Budget Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Handover Decision Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Neighbouring Cell Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Sporadic Neighbour Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Maximum Disuse Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Criterion 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
vi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
Criterion 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Per Cause, per Neighbour Handover Margins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Handover Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Uplink/Downlink Quality Handover Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Quality Handover Bounce Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Uplink/Downlink Interference Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Quality Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Intra-cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Uplink Level Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Downlink Level Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Distance Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Power Budget Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Chapter 4
BTS Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BTS Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
BTS 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Missing Report (add_cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Hreqave and Hreqt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Pointing Averaging Mechanisms to Decision Processes . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Special Case of RXLEV_DL_HO and SURROUND_CELL . . . . . . . . . . . . . . . . . . . . . . . . 424
Averaging Mechanisms, Decision Processes and Thresholds . . . . . . . . . . . . . . . . . . . . . 426
Alternate Processing of RXQUAL Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Weighted Quality Flag w_qual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Interference Averaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
RF Resource Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Support of BCCH/SDCCH in GSM Extension Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Chapter 5
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
EMOTOROLA LTD. 2000 SYS03: BSS Database Application vii

ISSUE 10 REVISION 3
Path Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Path Statement 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
BER Monitoring Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Nailed Timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Nailing a Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Path Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Path Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
BSC BTS Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Allocation of Terrestrial Backing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
DYNET Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
shared_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
dynet_tchs_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
dynet_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Reserved Timeslot Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Neighbour Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Chapter 6
Hopping Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Hopping Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Baseband Hopping Script GSR4 Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Synthesiser Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Base Band Hopping (BBH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Frequency Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Hopping Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Frequency Hopping Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Frequency Redefinition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Baseband Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Frequency Redefinition Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Channel Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Invoking hopping configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Cell frequency hopping view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Frequency Hopping Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
viii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
Frequency Hopping support via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Changing mobile allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Chapter 7
Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Practical Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Remote Transcoder Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
LAPD Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
DSP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Traffic Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
GCLK Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
BTS Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Geographical Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
SMS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
CRM Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
BTS Site 1 Specific (In-Cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Equipment Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
External Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Mains Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Rapid Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Cell Specific Information (Cell 39) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Averaging Algorithm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Intave Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Quality Flags Uplink and Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
BTS Site 2 Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Cell Broadcast SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
GSM Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Cell Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
BTS Site 3 Specific (micro-cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Cell Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Path Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appi
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosi

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosii
A ................................................................... Glosii
B ................................................................... Glosiv
C ................................................................... Glosvi
D ................................................................... Glosx
EMOTOROLA LTD. 2000 SYS03: BSS Database Application ix

ISSUE 10 REVISION 3
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxiii
F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxiv
G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxvi
H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxvii
I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxviii
K ................................................................... Glosxx
L ................................................................... Glosxx
M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxii
N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxv
O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxvi
P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxvii
Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxx
R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxx
S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxii
T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxvi
U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxix
V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosxxxix
W .................................................................. Glosxl
X ................................................................... Glosxl
Z ................................................................... Glosxl
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers1
Power Budget Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers3
XBL Connectivity Exercise answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers5
EAS Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers6
BTS Script (site 32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers6
BTS Script (site 33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers6
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers6
# Script for SYS03 RXCDR Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers7
# BSC No. 1 Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers11
# BTS Number 1 Answer Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers16
# BTS Number 2 Answer Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers23
# BTS Number 3 (M_Cellarena) Answer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers34
# Path Script Chain 1 Answers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers39
# 1.6.0.0 (GSR 4) # Hopping Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Answers45
x SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 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
The manual contains ...

!
" # !
EMOTOROLA LTD. 2000 SYS03: BSS Database Application 1

General information ISSUE 10 REVISION 3
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 Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
| Press the pipe symbol key.
CR or RETURN Press the Return (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 SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 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. Do not attempt to remove clothing adhering to the burn.
2. If help is available, or as soon as artificial respiration is no longer required, cover
the wound with a dry dressing.
3. Do not apply oil or grease in any form.

Reporting safety issues ISSUE 10 REVISION 3
Reporting safety issues
Introduction
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1. Make the equipment concerned safe, for example, by removing power.
2. Make no further attempt to tamper with the equipment.
3. 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).
4. Collect evidence from the equipment under the guidance of the MCSC.

ISSUE 10 REVISION 3 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.

General warnings ISSUE 10 REVISION 3
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 ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
S 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.

ISSUE 10 REVISION 3 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 Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
S The dust created by breakage of Beryllia is inhaled.
S Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.

Human exposure to radio frequency energy (PCS1900 only) ISSUE 10 REVISION 3
Human exposure to radio frequency energy (PCS1900 only)

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,
S + E + 377
2
H2
377
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.

ISSUE 10 REVISION 3 Human exposure to radio frequency energy (PCS1900 only)
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 Controlled Environment

1930MHz 1970MHz 1930MHz 1970MHz
Ceiling 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.

Human exposure to radio frequency energy (PCS1900 only) ISSUE 10 REVISION 3
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 1930MHz
Base station cabinet output power, P +39.0 dBm (8 watts)
Antenna feeder cable loss, CL 2.0dB
Antenna input power Pin PCL = +39.02.0 = +37.0dB (5watts)
Antenna gain, G 16.4dBi (43.65)
Using the following relationship:
G + 4pr W
2
Pin
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 + 43.65 5 + 1.16m

4pW 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.

ISSUE 10 REVISION 3 Beryllium health and safety precautions
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.

Beryllium health and safety precautions ISSUE 10 REVISION 3
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.

ISSUE 10 REVISION 3 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.

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

ISSUE 10 REVISION 3 Motorola GSM manual set
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 Name Catalogue

number number
GSM-100-101 System Information: General 68P02901W01
GSM-100-201 Operating Information: GSM System Operation 68P02901W14
GSM-100-311 Technical Description: OMC in a GSM System 68P02901W31
GSM-100-313 Technical Description: OMC Database Schema 68P02901W34
GSM-100-320 Technical Description: BSS Implementation 68P02901W36
GSM-100-321 Technical Description: BSS Command 68P02901W23
Reference
GSM-100-403 Installation & Configuration: GSM System 68P02901W17
Configuration
GSM-100-423 Installation & Configuration: BSS Optimization 68P02901W43
GSM-100-501 Maintenance Information: Alarm Handling at 68P02901W26
the OMC
GSM-100-521 Maintenance Information: Device State 68P02901W57
Transitions
GSM-100-523 Maintenance Information: BSS Field 68P02901W51
Troubleshooting
GSM-100-503 Maintenance Information: GSM Statistics 68P02901W56
Application
GSM-100-721 Software Release Notes: BSS/RXCDR 68P02901W72
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems
deploying Tandem S300 and 1475:

number number
GSM-100-202 Operating Information: OMC System 68P02901W13
Administration
GSM-100-712 Software Release Notes: OMC System 68P02901W71

Motorola GSM manual set ISSUE 10 REVISION 3
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in
the GSM manual set:

number number
GSM-100-202 Operating Information: Scaleable OMC System 68P02901W19
Administration
GSM-100-413 Installation & Configuration: Scaleable OMC 68P02901W47
Clean Install
GSM-100-712 Software Release Notes: Scaleable OMC 68P02901W74
System
Related manuals
The following are related Motorola GSM manuals:

number number
GSM-001-103 System Information: BSS Equipment Planning 68P02900W21
GSM-002-103 System Information: DataGen 68P02900W22
GSM-005-103 System Information: Advance Operational 68P02900W25
Impact
GSM-008-403 Installation & Configuration: Expert Adviser 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:

number number
GSM-100-020 Service Manual: BTS 68P02901W37
GSM-100-030 Service Manual: BSC/RXCDR 68P02901W38
GSM-105-020 Service Manual: M-Cell2 68P02901W75
GSM-106-020 Service Manual: M-Cell6 68P02901W85
GSM-201-020 Service Manual: M-Cellcity 68P02901W95
GSM-202-020 Service Manual: M-Cellaccess 68P02901W65
GSM-101-SERIES ExCell4 Documentation Set 68P02900W50
GSM-103-SERIES ExCell6 Documentation Set 68P02900W70
GSM-102-SERIES TopCell Documentation Set 68P02901W80
GSM-200-SERIES M-Cellmicro Documentation Set 68P02901W90

ISSUE 10 REVISION 3 Motorola GSM manual set
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.

Motorola GSM manual set ISSUE 10 REVISION 3

Chapter 1
Remote Transcoder Script Building

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 1
Remote Transcoder Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Remote Transcoder Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Remote Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RXCDR Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RXCDR 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
CIC(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MMS ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Starting Timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Starting Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Circuit Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Add Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Circuit/Channel Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Relationship Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Unequipped Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
XBL Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
XBL Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
XBL Connectivity Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
XBL Connectivity Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Enhanced Terrestrial Circuit Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Link Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Transcoder On-line Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
MSC Quietone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Downlink DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Audio Volume Control at the GDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Enhanced Full Rate Speech (EFR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
EFR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Handovers in EFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Internal Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
External Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

ISSUE 10 REVISION 3
GCLK Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Closed Loop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

ISSUE 10 REVISION 3 Remote Transcoder Script Building
Remote Transcoder Script Building
Objectives
By the end of this chapter the student will be able to:
S Understand all the parameters used within a Remote Transcoder database script.

Remote Transcoder ISSUE 10 REVISION 3
Remote Transcoder
RXCDR Script
Building
The script building chart shown opposite specifies the groups of parameters necessary to
populate a Remote Trancoder database. The actual parameters can be examined more
closely by following the example script overleaf.

ISSUE 10 REVISION 3 Remote Transcoder
RXCDR Script Building Chart


RXCDR 1.6.0.x Script Files ISSUE 10 REVISION 3
RXCDR 1.6.0.x Script Files

# EXAMPLE RXCDR DATABASE
# GSR4 (1.6.0.0)
equip bsc SITE
0
chg_element fm_site_type 3 0
equip bsc CAB
0
5
equip bsc CAGE
0
0
0
yes
chg_element gproc_slots 16 0
chg_element bsc_type 1 0
equip bsc KSW
0
0
0
no
equip bsc BSP
0
0
25
equip bsc BSP
1
0
26
equip bsc GCLK
0
0
no
no
no
equip bsc MSI
6
0
6
0
equip bsc MSI
8
0
8

ISSUE 10 REVISION 3 RXCDR 1.6.0.x Script Files
0
equip bsc MSI
10
0
10
0
equip bsc MSI
15
0
9
1
equip bsc MSI
17
0
7
1
equip bsc OML
0
10
0
1
equip bsc XBL
0
64
8
1
25
2500
3
7
chg_element stat_interval 30 0
add_link 6 1 16 17 0 16
add_link 6 0 16 15 0 16
add_link 10 0 4 8 1 1
add_link 10 0 3 8 0 1
add_link 10 0 2 10 1 1
add_bss_conn 8 1 1 1 0
add_channel 8 0 2 0 15 0 5
add_channel 8 0 2 1 15 0 6
add_channel 8 0 2 2 15 0 7
add_channel 8 0 2 3 15 0 8
add_channel 8 0 3 0 15 0 9
add_channel 8 0 3 1 15 0 10
add_channel 8 0 3 2 15 0 11
add_channel 8 0 3 3 15 0 12
add_channel 8 1 2 0 17 0 5
add_channel 8 1 2 1 17 0 6
add_channel 8 1 2 2 17 0 7
add_channel 8 1 2 3 17 0 8

RXCDR 1.6.0.x Script Files ISSUE 10 REVISION 3
add_channel 8 1 3 0 17 0 9
add_channel 8 1 3 1 17 0 10
add_channel 8 1 3 2 17 0 11
add_channel 8 1 3 3 17 0 12
chg_element ber_loss_daily 4 0
chg_element ber_loss_hourly 6 0
chg_element remote_loss_daily 20 0
chg_element remote_loss_hourly 16 0
chg_element remote_loss_oos 511 0
chg_element remote_loss_restore 10 0
chg_element remote_time_oos 500 0
chg_element remote_time_restore 500 0
chg_element slip_loss_daily 10 0
chg_element slip_loss_hourly 4 0
chg_element slip_loss_oos 255 0
chg_element slip_loss_restore 10 0
chg_element sync_loss_daily 20 0
chg_element sync_loss_hourly 16 0
chg_element sync_loss_oos 511 0
chg_element sync_loss_restore 10 0
chg_element sync_time_oos 90 0
chg_element sync_time_restore 30 0
modify_value 0 phase_lock_duration 0 MMS 6 0 0

modify_value 0 mms_priority 0 MMS 6 0 0
chg_element phase_lock_gclk 1 0
chg_element wait_for_reselection 240 0
chg_element lta_alarm_range 10 0
chg_element enh_ter_cic_mgt_ena 1 0 bss_id=1
chg_element enh_ter_cic_mgt_ena 1 0 bss_id=2

ISSUE 10 REVISION 3 RXCDR 1.6.0.x Script Files

Equipping Terrestrial Circuits ISSUE 10 REVISION 3
Equipping Terrestrial Circuits
Overview
Once an MSI/XCDR/GDP has been equipped the 16 or 64 kb/s trunks can then be
added.
This is performed by using the equip 0 CIC command. This command is not applicable
to RXCDRs and can only be entered at BSC/BSS sites.
CIC(s)
Identifies the singular unique 16/64 kb/s Circuit Identity Code (CIC) or range of unique
CIC(s) (up to 124) to be equipped.
MMS ID
Identifies the MMS card and port that will interface to the E1/T1 link.
Starting Timeslot
Identifies either the specific timeslot on the E1/T1 link on which to add the circuit or the
first timeslot if a range of circuits is to be equipped. The first CIC in the range will be
equipped on the timeslot specified. Subsequent CICs follow sequentially through the
entire range.
Starting Group
This prompt only appears when circuits are being added to a BSC and when the
transcoding has been carried out remotely.
In this case 4 x 16 kb/s timeslot channels are fitted into 1 x 64 kb/s timeslot and are
numbered 0 3.
A particular CIC cannot be equipped more than once per BSC. When a range is
equipped, all CICs within the range are tested for timeslot availability and uniqueness. If
any number of the CICs are not able to be equipped because the CIC is non-unique or
the timeslot/group is not available, the command will be accepted with a warning to the
operator specifying the CICs that were not able to be equipped. If all CICs specified in
the command cannot be equipped then the command is rejected.
Note:
This is a BSC command that has a relationship with the add_channel command entered
at the RXCDR.

ISSUE 10 REVISION 3 Equipping Terrestrial Circuits
Equip Terrestrial Circuits
equip 0/bsc CIC
S Enter CIC(s): <CIC> [to <CIC>]

0 - 65535
S Enter MMS ID: <Card ID> <Port>

0 - 55 0-1
S Enter starting timeslot: 1 - 31 (E1)

1 - 24 (T1)
S Enter starting group: 0-3

(only prompted for RXCDR)
MSC MSC
XCDR/GDP
RXCDR
MSI
MSI XCDR/GDP
BSC BSC
Group numbers necessary Group numbers not used

Equipping Terrestrial Circuits ISSUE 10 REVISION 3
Equipping Terrestrial Circuits
Circuit Number
The individual circuit number is constructed by combing the link number and the timeslot
number of the particular traffic channel.
The 5 least significant bits (LSB) denote the timeslot number of the traffic channel, whilst
the remaining 11 bits represent the link number.
Once the timeslot and link number have been entered the entire 16 bit number is read as
a whole to determine the circuit number.
Circuit number 0 or any multiple of 16 are not allowed.
Circuit number 0, 32, 64, etc will refer to the synchronization timeslot and therefore
cannot be designated to carry traffic.
Circuit number 16, 48, etc are reserved for carrying Message Transfer Links (MTL) from
the MSC to the BSC and cannot be processed by an RXCDR card. These also cannot be
designated to carry traffic.

ISSUE 10 REVISION 3 Equipping Terrestrial Circuits
CIC Numbers
32768
16384
8192
4096
2048
1024
512
256
128
64
32
16
8
4
2
1
0 0 0 0 0 0 0 0 0 1 1 0 1 0 1 0 CIC = 106
Link = 3 Timeslot = 10
Link number Timeslot number

GSM 08.08 3.2.2.2
MSI 8
MSI 7
XCDR
Link 3
14
0
T.S. = 10
MSC RXCDR BSC

0
Link 2
Link 1
1
Link 0
SYS03_1_CIC_numbers

Add Channel ISSUE 10 REVISION 3
Add Channel
This command is only applicable at the RXCDR and describes traffic circuit connections
from the MSC to the BSC through the Remote Transcoder.
add_channel <span_a_id_1><span_a_id_2>
<timeslot_number_a><group_number_a><span_b_id_1>
<span_b_id_2><timeslot_number_b>
Inbound from BSC

Span_a_id_1: First MMS id
Span_a_id_2: Second MMS id
timeslot_number_a: 64 kbs timeslot (131)
group_number_a: Group within 64 kbs timeslot (transcoded circuit) 03
Outbound to MSC
span_b_id_1: First MMS id
Span_b_id_2: Second MMS id
timeslot_number_b: 64kbs timeslot (131)

ISSUE 10 REVISION 3 Add Channel
Add Channel

MSC
Span B Link 3
T.S. = 10
XCDR 14 0
Add_Channel 8 0 6 2 14 0 10
RXCDR
MSI 8 0 1
Equip CIC 106

Span A T.S. = 6
Group = 2 71
6
MSI 7 0 1
2
BSC
SYS03_1_add_channel

Circuit/Channel Relationship ISSUE 10 REVISION 3
Circuit/Channel Relationship
Overview
Certain circuit numbering conventions are used by the MSC, it is of utmost importance
for the CCT ID nominated in the switch to physically match up to the CCT ID in the BSC.
Dynamic switching in the BSC will be seriously impaired if this is not the case. The
numbering scheme that the switch follows is reasonably simple:
1. CCT ID 0 is never used

2. CCT ID 16 and multiples of 16 are never used.
1st SPAN CCT IDS 131 TS 131 (TS16 being omitted)

2nd SPAN CCT IDS 3363 TS 131 (TS16 being omitted)
3rd SPAN CCT IDS 6595 TS 131 (TS16 being omitted)
etc...
The idea of this from the switch perspective is that CCT IDs match timeslot numbers in a
set pattern.
A typical example of this scheme is shown opposite.
Relationship
Example
RXCDR (64 kbs-1) BSC

T S2
SPAN 0
TS 5
22/0 KSW
10/0 * 1/0
TCH
add_channel 10 0 2 0 22 0 5 equip 0 CIC

CIC= 5 (16kbs-1) 5
Group= 0 1 0
TS= 2 2
0

ISSUE 10 REVISION 3 Circuit/Channel Relationship
T he CIC is shown in
brackets after the

add_chanel
commands. It is not
part of the command
24 23 22 21

add_chan 10 1 2 0 24 0 5 (5) add_chan 10 1 8 2 23 0 1 (33) add_chan 10 1 17 0 22 0 1 (65) add_chan 10 1 24 2 21 0 1 (97)

add_chan 10 1 2 2 24 0 7 (7)
add_chan 10 1 12 0 23 0 15 (47) add_chan 10 1 20 2 22 0 15 (79) add_chan 10 1 28 0 21 0 15 (111)

add_chan 10 1 4 2 24 0 17 (17)

add_chan 10 1 12 1 23 0 27 (49) add_chan 10 1 24 1 22 0 31 (95) add_chan 10 131 3 21 0 31 (127)
add_chan 10 1 8 1 24 0 31 (31)

10/1
1/0
equip 0 CIC equip 0 CIC equip 0 CIC equip 0 CIC

5 to 15 33 to 47 65 to 79 97 to 111
1 0 1 0 1 0 1 0
2 8 17 24
0 2 0 2
equip 0 CIC equip 0 CIC equip 0 CIC equip 0 CIC

17 to 31 49 to 63 81 to 95 113 to 127
1 0 1 0 1 0 1 0
4 12 20 28
3 1 3 1
CIC = 0, 16 AND MULT IPLES OF 16 ARE NOT USED T S 16 IS USED FOR MT L

Unequipped Circuits ISSUE 10 REVISION 3
Unequipped Circuits
Note: This parameter is set only at the BSC.
If the MSC specifies an unequipped circuit in the CIC, i.e. a circuit that does not appear
in add_circuit at the BSC, then the BSC can:
S Send an alarm up the OML to the OMC
S Indicate the unequipped circuit to MSC (via the MTL) so that the MSC does not
specify it again
S Do both of the above.
The action is specified by the unequipped_circuit_allowed parameter opposite, which
is a purchasable option.

ISSUE 10 REVISION 3 Unequipped Circuits
Unequipped Circuits
"

!
Note: T his is a purchasable option feature

XBL Equipage ISSUE 10 REVISION 3
XBL Equipage
Overview
Between the RXCDR and the BSC there can exist a fault management communications
link is called the XBL. The XBL is able to provide bi-directional communications between
the BSP in the BSC and the BSP in the RXCDR. The purpose of the XBL is to enable a
notification of failed traffic circuits at the RXCDR to be sent to the BSC. The BSC will
then send the appropriate blocking messages to the MSC along the MTL. The XBL must
be equipped at both the RXCDR and BSC as these are separate GSM entities. A
maximum of 2 XBLs can be enabled between each RXCDR and BSC.
Device ID
This number uniquely identifies the XBL within the transcoder. It does not have to be
identical to the id given to the same XBL in the BSC, convention is that it will be.
Data Rate
The XBL can be 16 kbit/s or 64 kbit/s, i.e. occupying a quarter of a timeslot or a whole
timeslot.
First MMS Description

This number identifies the MSI card within the transcoder.
Second MMS Description

This number identifies the port on the MSI card.
Timeslot
This is the timeslot on the MMS.
Group
Only appears if the data rate is 16 kbit/s. Identifies which quarter of the timeslot is used
for the XBL maximum 2 XBLs per timeslot.
LAPD T200 Timer

This is the maximum time the LAPD (Layer 2) transmitter will wait for an
acknowledgement before making a retransmission.
LAPD N200
This is the maximum number of retransmissions a transmitter will make.
LAPD K Value
This is the maximum number of Unacknowledged Information frames a transmitter will
allow before holding up transmission.

XBL=0
EQUIP XBL ID= 0 EQUIP XBL ID=0
AND PLACE IN T S 2 T S =2 AND PLACE IN T S 2

ISSUE 10 REVISION 3 XBL Equipage
Equip XBL
equip (site number) XBL: <CR>
S Enter the device identification for the XBL: 0-9

S Enter the data rate for the XBL: 16 or 64
S Enter the first MMS description for this device: 0-71
S Enter the second MMS description for this device: 0-1
S Enter the timeslot on the MMS where this device appears:
1-31
S Enter the group of the timeslot where this device appears:
0-3
S Enter the LAPD T200 Timer value for this device: 200-5000
mS ( in 50 mS intervals)
S Enter the LAPD N200 value for this device: 1-5
S Enter the LAPD K value for this device: 1-127
NOTE: The XBL is also equipped at the BSC. It

should have the same XBL id and must have the same
timeslot at the BSC as at the RXCDR. Also the LAPD
parameters should be the same at each end.

XBL Connectivity ISSUE 10 REVISION 3
XBL Connectivity
Overview
In order for correct XBL operation, network connectivity information must be entered at
the RXCDR. Using the add_bss_conn command every RXCDR to BSC span line must
be specified separately. This parameter can only be used at the RXCDR.
add_bss_conn
<RXCDR MSI>: mms id 1: 1st span line identifier at the RXCDR.
<RXCDR port>: 2nd span line identifier at the RXCDR.
<BSC No>: BSC number in the range 031. This number is

completely arbitary as long as each BSC connected to
the RXCDR is numbered uniquely the connectivity will
be set up correctly.
<BSC MSI>: 1st span line identifier at the BSC.
<BSC Port>: 2nd span line identifier at the BSC.
This connectivity information will enable circuit or board failure information at a RXCDR
to be transmitted to the corresponding BSCs.

ISSUE 10 REVISION 3 XBL Connectivity
XBL Connectivity


XBL Connectivity Tables ISSUE 10 REVISION 3
XBL Connectivity Tables
Overview
In the event of either XCDR equipment or link failure affecting the RXCDRs 2Mb inputs
from the MSC, the appropriate BSCs, whose circuits have been affected, can be
informed via message sequences on the XBL. These messages will inform the fault
management of the BSC of the incoming span id, slot and group number of each circuit
affected. This information can then be used by the BSC to format the appropriate
blocking messages to be sent to the MSC.
To enable the RXCDRs FM to specify these circuit details to the BSC, XBL connectivity
tables are produced by the RXCDRs FM from the following database parameters:
add_channel: Will specify incoming (from BSC), span id, timeslot and
group number to outgoing (to MSC) span id and
timeslot.
add_bss_conn: Will specify every span id to span id connection from the
transcoder to each BSC. As each BSC is notionally
numbered a group of span ids can be attributed to one
BSC.
equip XBL: Will specify the span id holding the XBL. This span id
will be one of the spans within the group of spans
attributed to one BSC
The table below can then be constructed by the RXCDRs FM. If a fault occurs to a
particular XCDR card, then add_channel will point to outgoing spans (to BSCs),
timeslots and group numbers which are affected by the incoming failure. These outgoing
spans have been identified by the add_bss_conn parameter as belonging to a group of
spans notionally attributed to a specified BSC. The failure messages can then be sent
down an XBL having a span id consistent with one of the spans within the notional group.

!!

ISSUE 10 REVISION 3 XBL Connectivity Tables
XBL Connectivity


XBL Connectivity Exercise ISSUE 10 REVISION 3
XBL Connectivity Exercise

Complete the database parameters for the connectivity shown opposite.


ISSUE 10 REVISION 3 XBL Connectivity Exercise
XBL Connectivity Exercise


Enhanced Terrestrial Circuit Device Management ISSUE 10 REVISION 3
Enhanced Terrestrial Circuit Device Management
Overview
The element enh_ter_cic_mgt_ena acts as a flag to enable a BSS to support enhanced
Terrestrial Circuit Device Management (TCDM).
Prior to GSR4 if an XCDR card went faulty, blocking information stating that the MSC
side MMS was OOS went to the BSC to block all circuits associated with that XCDR
card. With enhanced TCDM single DSP management is possible.
Single DSP management means that when a single DSP goes faulty on a XCDR the
card is not taken OOS, instead, blocking information regarding the individual CIC that is
affected is sent.
The element enh_ter_cic_mgt_ena is used by the RXCDR to determine if blocking
information relating to individual DSPs can be sent to the BSC. It is possible that a BSC
may not have been upgraded to support enhanced TCDM but the RXCDR has. This
element will block messages that will not be understood from being sent to the BSC. The
element should be set to a 1 at the RXCDR for those BSCs that have been upgraded.

ISSUE 10 REVISION 3 Enhanced Terrestrial Circuit Device Management
Enhanced Terrestrial Circuit Device Managment

"
!

"

!

"


Link Description ISSUE 10 REVISION 3
Link Description
Overview
This command is only applicable to a RXCDR and describes a nailed 64kbs circuit
cross-connected through the site. It is used to establish a static connection through the
KSW at initialisation, it can be used to nail an OML, MTL or CBL.
add_link <span_a_id_1><span_a_id_2>
<timeslot_number_a><span_b_id_1><span_b_id_2>
<timeslot_number_b>
Inbound (from BSC)

Span_a_id_1: First MMS id
Span_a_id_2: Second MMS id
timeslot_number_a: 64 kbs timeslot (131)
Outbound
span_b_id_1: First MMS id
Span_b_id_2: Second MMS id
timeslot_number_b: 64kbs timeslot (131)

ISSUE 10 REVISION 3 Link Description
ADD_LINK

MTL RXCDR
MSI 7
MSI 8
TS 16
0
MTL
Link 2 TS 16
MSC BSC
0
0
XCDR 14
KSW OML
Link 1
1
1
TS 1
Link 0
MSI 10 0 1
add_link 8 0 16 14 0 16
OML TS 2
OMC
add_link 8 0 1 10 0 2
SYS03_1_add_link

Transcoder On-line Expansion ISSUE 10 REVISION 3
Transcoder On-line Expansion
Overview
The transcoding capacity (and therefore the traffic circuit capacity) of a network can now
be increased on-line, i.e. without interruption to service. This is possible because the
associated commands are now allowed outside sysgen mode. Traffic circuits can be
added or deleted at the BSC and RXCDR, signalling links can be equipped, unequipped
or mapped through the RXCDR and XBL connectivity can be added or removed, all
on-line.
The full list of commands now possible outside sysgen mode is shown opposite.
Before removing a signalling link, it must be locked, as is the case before unequipping
any other device.

ISSUE 10 REVISION 3 Transcoder On-line Expansion
XCDR On-Line Expansion
S
S

S

S

S
S
S
S

MSC Quietone ISSUE 10 REVISION 3
MSC Quietone
Overview
During call set-up or handover the MSCRXCDR circuit will be idle, the bit pattern that
the MSC transmits and expects to receive for this condition is called MSC Quietone.
Different switch manufacturers may require a different quiet tone and therefore this
pattern can be set.
This parameter is only valid at a site that is equipped with a transcoder card, the range is
0255 (one byte).

ISSUE 10 REVISION 3 MSC Quietone
MSC Quietone
MSC
IDLE CONDITION
(MSC QUIETONE)
RXCDR
IDLE FRAME
BTS
chg_element msc_qt <*> <site>
* 0-255

Downlink DTX ISSUE 10 REVISION 3
Downlink DTX
Overview
Within the XCDR card is a Voice Activity Detector (VAD), together with its firmware
routine this device can detect, if enabled, the difference between speech and noise being
received on each PCM channel. The 320 bit (260 Bits GSM defined speech plus 60 bits
TRAU) block will either be identified as speech or a silence descriptor frame (block), by
the TRAU overhead. DTX may be in use for this air interface channel, if so, the channel
coder within the DRIM card will transmit appropriate SID frames on the air interface. If
downlink DTX is not being used for this call then the channel coder will process each SID
frame as if it were traffic.
This parameter is applicable only in locations where the XCDR is present and if disabled
will not allow DTX to take place regardless of other DTX parameters.

ISSUE 10 REVISION 3 Downlink DTX
Downlink DTX
DTX specified
dnlk_vad_dtx from MSC
DATA,
NOISE
OR
SPEECH
PCM VAD CC SPEECH
VAD
SPEECH AND/OR
NOISE MANDATORY MS
SID
XCDR DRIM BLOCKS
chg_element dnlk_vad_dtx <*>
* 0 = Downlink DTX disabled

1 = Downlink DTX enabled

Audio Volume Control at the GDP ISSUE 10 REVISION 3
Audio Volume Control at the GDP
Overview
It is possible to increase or decrease the audio level of the speech in both the uplink and
downlink directions by manipulating the database.
As the digital PCM signal arriving at the GDP card in the RXCDR or BSC is essentially a
binary representation of an integer value representing the amplitude of a sound wave at a
certain point in time, it is possible to apply a multiplication factor to this binary value. This
factor can either increase or decrease the amplitude as represented by the binary value.
The effect of this volume change is to give better quality louder calls (in the case of
volume increase) than would be the case with the standard volume control performed at
the CCDSP in the BTS.
Care must be taken when choosing the amount by which to change the volume, as the
change is applied to all PCM signals regardless of their previous volume. So for example
if the maximum increase of 15 dB is applied to already loud audio signals the customer
perception may be negative. The choice of level change can be considered an
optimization question.
The advantage of this feature is that the volume change is performed at the point of
transcoding (GDP card) rather that at the BTS with an already transcoded signal.

ISSUE 10 REVISION 3 Audio Volume Control at the GDP
Volume Control at the GDP
Level
T ime
m

m

m

Parameters ISSUE 10 REVISION 3
Parameters
The volume control feature is enabled using the parameters shown opposite.
The volume_control_type parameter enables the feature on a per RXCDR or BSC
basis. If an RXCDR is connected to 2 BSCs for example, where one uses volume
control and one does not, then all CICs associated with the volume control using BSC
must be processed by GDP cards. In this case the bss_id element of this parameter is
used to indicate which BSC is concerned, using the BSC number specified in
add_bss_conn; it therefore follows that add_bss_conn must be entered before this
parameter. Care must also be taken to ensure that the add_channel command does
not connect a CIC from a GDP to a non-volume control BSC. If local transcoding is
being used then the above restrictions do not apply, although GDPs must be used
throughout, in place of XCDR cards.
The volume change is specified by ul_audio_lev_offset for the link and by
dl_audio_lev_offset for the downlink. A range of 30 dB is possible, that is +15 to 15,
and it is acceptable to enter the minus sign in the database

ISSUE 10 REVISION 3 Parameters
Volume Control at the GDP
S chg_element volume_control_type <*><site ID>[bss_id = <bss id>]
<*> 0= Disable GDP volume control

1= Enable GDP volume control
<site ID> Always 0 or bsc
<bss ID> Only required at a RXCDR.

Must be consistent with add_bss_conn
S chg_element ul_audio_lev_offset <*><site ID>[bss_id = <bss id>]
S chg_element dl_audio_lev_offset <*><site ID>[bss_id = <bss id>]
<*> -15 to +15 dB in integer steps (1 Step = 1 dB)
<site ID> Always 0 or bsc
<bss ID> Only required at an RXCDR.

Must be consistent with add_bss_conn

Enhanced Full Rate Speech (EFR) ISSUE 10 REVISION 3
Enhanced Full Rate Speech (EFR)
Overview
The EFR speech feature can optionally provide calls involving phase 2+ mobiles with
superior voice quality. This is achieved by using a modified transcoding algorithm on
generic Digital Signal processor (GDP) cards instead of the XCDR card.
Call setup is handled in the usual way, except that the MSC must know the mobiles
capabilities before the assignment request is sent to the BSC. This information is
provided by the mobile while on its SDCCH in the Call Setup DTAP message. The MSC
then indicates in the assignment request message that the BSS should provide an EFR
or full rate channel or either.
The RXCDR is not involved in any call setup signalling, and therefore has no idea
whether the speech will be EFR or full rate until it arrives at the GDP. The first speech of
any call is always in the uplink direction, however, so the GDP detects the first TRAU and
uses EFR or full rate as appropriate from then on in the call.

ISSUE 10 REVISION 3 Enhanced Full Rate Speech (EFR)
EFR Call Setup
MS RRSM SSM MSC

CM Service Request
initial L3 Info
CR
CALL SETUP DTAP MESSAGES including EFR capability
assignment request
initiate assignment
CRM
assignment
resource request
assignment
RSS channel assigned
physical context Req
physical context confirmed
channel activation
channel activation acknowledge
assignment command
assignment complete
assignment successful
SM
connection
request
switch response
success
assignment complete
GDP
TCH 1st TRAU frame= EFR 16 kbit/s
TCH 64 kbit/s

EFR Configuration ISSUE 10 REVISION 3
EFR Configuration
Parameter
The EFR feature must be enabled at the BSC and RXCDR, using the efr_enabled
parameter. GDP cards must be equipped to handle all transcoding associated with EFR
traffic circuits. To accommodate this a new msi_type value of 2 (or GDP) is now
acceptable in the equip 0 MSI command.
When the MSC specifies a choice of EFR or full rate in the assignment request message,
the BSS database can override the system and force it to use one particular type of
coding algorithm. This is achieved by the override_speech_version parameter.

ISSUE 10 REVISION 3 EFR Configuration
EFR Parameters
S chg_element efr_enabled<*><Site ID>bss_id=<BSS ID>
<*> 0= EFR disabled

1= EFR enabled
<location> Always 0
[BSS ID] Only at RXCDR. Must equal BSC

number in add_bss_conn
S equip 0 MSI
<ID>= 0 to 55
<cage>= 0 to 13
<slot>= 6 to 24
<type>= 0 or MSI
1 or XCDR
2 or GDP
255 or msi2_conv
S chg_element override_speech_version <*>0<BSS_id>
<*> 0= no override
1= full rate
2= EFR

Handovers in EFR ISSUE 10 REVISION 3
Handovers in EFR
Overview
When a handover occurs, the behaviour of the BSS in terms of EFR depends upon
whether the handover is internal or external.
Internal
Handovers
As EFR is enabled on a per BSS basis, the target cell provides a channel of the same
type (EFR or full rate) as was being used in the source cell.
External
Handovers
External handovers use, in the target cell, whichever algorithm is enabled in the target
BSS, chosen as described in the call setup (efr_enabled and override_speech_version).
It is important to ensure that the speech version in use in the source cell is indicated in
the handover_required message. This is so that the source and target speech version
can be compared in order to inform the mobile, in the handover command, of the type of
transcoding to be used in the new cell if that is different from the source cell. This is set
by the handover_required_sp_ver_used parameter. Failure to set this may result in
garbled or no speech, as it will be assumed that the source cell was using full rate; if the
target cell chooses full rate but the source was in reality using EFR, the mobile will not be
told to change mode in the handover command. This causes EFR speech to be
transmitted by the mobile into a full rate only BSS.

ISSUE 10 REVISION 3 Handovers in EFR
EFR Parameters
S


GCLK Synchronisation ISSUE 10 REVISION 3
GCLK Synchronisation
Overview
This feature will provide frequency synchronisation of the GCLK output signals based on
the standard provided by an incoming 2 Mbit/s link. The aim of GCLK synchronisation is
to provide RF carrier frequencies to within +/ 0.05 ppm. Synchronisation to an E1 or T1
link will also minimise frame slips and reduce the frequency of on site calibrations.
The network clock should be maintained at +/ 0.01 ppm of 2.048 Mhz (E1) or 1.544 Mhz
(T1). To maintain synchronisation the clock data should have no breaks greater that 80
micro seconds. The synchronisation circuitry resides on the GCLK card fitted at every
site. This feature will operate with BTSs connected in star, daisy chain and loop
topologies.
In order to phase lock, a GCLK must have a span assigned as a reference source.
Parameters in the database can be used to specify priorities applicable to each span at a
site. These priorities will be used to determine the order of selection of spans as a
reference source
There are four modes that the GCLK board can operate in, these are: Free Run, Hold
Frequency, Set frequency and Closed loop.
Free Run
When a GCLK is inserted into the digital cage (or on power up) a 30 minute warm up
period is required for the ovenised crystal oscillator (OXCO) to reach the correct
operating temperature, during this time the GCLK is in free run mode and the input to the
DAC is set to 80(hex). The value 80(hex) cannot be changed. The OXCO in free run
mode will produce a clock output accurate to 0.05ppm.
Note: The 30 minute warm up period is set by Motorola and cannot be changed.
Hold Frequency
The hold frequency mode is used to maintain a specific clock frequency in the event that
the 2.048MHz reference should fail. This mode uses the last 8 bit word output from the
ADC to set the DAC. The hold frequency mode is a transitional mode (typically 10 secs)
until the set frequency mode is activated by the software.
Set Frequency
The Set Frequency mode allows the software to use the LTA to set the DAC to control
the output of the OXCO during loss of the 2.048mhz reference signal (This is after the
transitional Hold Frequency mode).

Phase Lock Loop (PLL) Circuit of a GCLK
ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
16.384 MHZ
Feedback
output Phase
signal Detector ADC DAC OXCO
f in
LPF Vin
SYS03: BSS Database Application
Input signal 16.384 MHZ
OSC.IN
LOCK DET
2.048 MHZ
Conv.CS Vref
Calibration
256 KHz Adjust
Divide by
8 80(Hex) Read Freq Set Freq
Latch Latch
EN Buffer
OE OE OE
Reference Fail Detect Control
GPROC (MCAP data bus)
147
Closed Loop
Mode
Within the closed loop mode there are two sub modes or states:
S Acquiring Frequency Lock State
S Frequency Lock State
The acquiring frequency lock state is the operating condition where the GCLK PLL
output is converging towards the long term frequency of the E1/T1 line. The time spent
in this state is dependant on the hardware revision level of the GCLK board, current build
boards will be in this state a maximum of 2 minutes, typically much less. Once this state
is reached (i.e. the output is within GSM specifications) the second sub state, frequency
lock state is activated.
This mode is again dependant on the GCLK hardware revision level (either 2 or 10
minutes), and is used to confirm that the GCLK output is stable within the GSM
specification for the set period (2/10 minutes).
The following command is used to enable or disable phase locking at a site:
chg_element phase_lock_gclk <*> <site>
* 0 Disable phase locking
1 Enable phase locking
Should the chosen span subsequently go oos a GCLK reference fail alarm will be
initiated. The following timer controls the time the system will wait before selecting
another span for extraction. If the current span returns to ins before the timer expires
then it will remain the clock extraction source.
chg_element wait_for_reselection <*><site>
* 0255 (seconds)
To enable the GCLK to synchronise to an E1 or T1 a suitable source must exist. The
priority for source selection is:
1. MMS in service.
2. Priority of MMS (database parameter)
3. Number of times the MMS has gone oos in a given period
4. If priority and MMS oos are equal the order of selection of sources shall be on a
rotation basis.
The priority of each MMS can be individually set:
modify_value <site> mms_priority <*> mms <mms_id 1> <mms_id 2>
* 0255 0 MMS will not be selected
1 Lowest priority
255 Highest priority

ISSUE 10 REVISION 3 GCLK Synchronisation
chg_element phase_lock_gclk <*><site>
* 0 Disable phase locking

1 Enable phase locking
0 DEFAULT
chg_element wait_for_reselection <*><site>
* 0-255 (seconds)
modify_value <site> mms_priority <*> mms

<mms_id 1> <mms_id 2> <mms_id 3>
* 0-255 0 - MMS will not be selected

1 - Lowest priority
255 - Highest priority

A count of the number of times the MMS goes oos is kept to enable the prioritizing
algorithm to function. A reset period is used to delimit the time for which an oos count is
held. At the end of each reset period the oos count is reset to zero and the count begins
again.
chg_element clk_src_fail_reset_period <*><site>
* 1255 Hours
After initialisation of the site the GCLK will attempt to synchronise to the chosen MMS,
the time duration taken for this synchronisation will vary depending on the hardware
revision level of the card. If the synchronisation has been maintained for
phase_lock_duration the CA will declare the GCLK phase locked. The default value
for this variable is 0 which indicates that there is no change from the minimum period
defined for the revision level of the GCLK. The variable may be set on an mms basis to
account for different transmission media.
modify_value<site>phase_lock_duration <*> mms <mms_id 1> <mms_id 2>
* 0 Default, GCLK revision level dependent, any mms details
ignored
1 3600 seconds, mms details used
The GCLK is polled once every 30 minutes to establish the current 8 bit DAC value. A
rolling average mechanism of the previous 48 DAC values (24 hours in time) produces a
Long Term Average (LTA). This average is used as the DAC setting in the case of Set
Frequency Mode. Every polling period the previous 48 averages are checked against
the current LTA. If 25% of the values vary by a specified range an alarm is then raised.
The range is specified as follows:
chg_element lta_alarm_range <*> <site>
* 1255
Note:
The part of the database used to enter these commands can vary dependant on the site
type of dependencies.

ISSUE 10 REVISION 3 GCLK Synchronisation
chg_element clk_src_fail_reset_period <*><site>
* 1-255 Hours
modify_value <site>phase_lock_duration <*> mms

<mms_id 1> <mms_id 2> <mms_id 3>
* 0 - Default, GCLK revision level dependent,

any mms details ignored
1 - 3600 seconds mms details used
chg_element lta_alarm_range <*><site>
* 1-255


Chapter 2
BSC Script Building

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 2
BSC Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Base Station Controller (BSC) Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
BSC 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
XBL Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Battery Conservation, Mains Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
External Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
EAS Alarm Text String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
EAS Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BTS Script (site 32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BTS Script (site 33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Statistics Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
MTP Level 3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Signalling Point Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Emergency Call Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Multiple Encryption Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Circuit Error Rate Monitor (CERM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Short Message Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Multiple Background Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Point to Point SMS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Traffic Channel SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
RACH Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CRM Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 Base Station Controller (BSC) Script Building
Base Station Controller (BSC) Script Building
Objectives
By the end of this chapter the student should be able to:
S Understand all the parameters used within a BSC database script.

BSC Script Building ISSUE 10 REVISION 3
BSC Script Building
Script Chart
The script chart shown opposite specifies the groups of parameters necessary to
populate a BSC database. The actual parameters can be examined more closely by
following the example script overleaf.

ISSUE 10 REVISION 3 BSC Script Building
BSC Script Building Chart


BSC 1.6.0.x Script Files ISSUE 10 REVISION 3
BSC 1.6.0.x Script Files

# EXAMPLE BSC DATABASE
# GSR4 (1600)
equip bsc SITE

0
equip bsc CAB
0
3
1
equip bsc CAGE
0
0
0
yes
chg_element transcoder_location 0 0

ISSUE 10 REVISION 3 BSC 1.6.0.x Script Files
equip bsc KSW

0
0
0
no
equip bsc GPROC
1
0
19
equip bsc GPROC
3
0
21
equip bsc GPROC
4
0
22
equip bsc GPROC
5
0
23
equip bsc BSP
0
0
20
equip bsc CSFP
0
0
18
equip bsc LCF
0
1
0
equip bsc LCF
1
0
0
equip bsc LCF
2
0
0

equip bsc LCF

3
0
0
# DEFAULT ALARM MESSAGES
chg_eas_alarm 0 0 Burglar
chg_eas_alarm 1 2 High Temperature
chg_eas_alarm 2 2 Low Temperature
chg_eas_alarm 3 2 Door Intruder Alarm
chg_eas_alarm 4 2 Burglar Alarm
chg_eas_alarm 5 2 Window Intruder Alarm
chg_eas_alarm 6 0 Low Humidity
chg_eas_alarm 7 0 Tower Beacon Outage
chg_eas_alarm 8 0 Surge Arrestor Failure
chg_eas_alarm 9 0 Microwave Trans. Failure
chg_eas_alarm 10 0 AC Power Failure
chg_eas_alarm 11 0 Generator Running
chg_eas_alarm 12 0 Generator Failed
chg_eas_alarm 13 0 PSU Rectifier
chg_eas_alarm 14 0 PSU Battery
chg_eas_alarm 15 0 PSU Fuse
chg_eas_alarm 16 0 Personnel on Site
chg_eas_alarm 17 0 General Alarm 1
chg_eas_alarm 20 0 PCU Over Temperature
chg_eas_alarm 21 0 PCU Customer Defined 1
chg_eas_alarm 22 0 PCU Door Open
chg_eas_alarm 23 0 PCU DC Fail
chg_eas_alarm 24 0 PCU Circuit Breaker
chg_eas_alarm 25 0 PCU AC Fail
chg_eas_alarm 26 0 PCU Comms Equipment
chg_eas_alarm 27 0 TDU Over Temperature
chg_eas_alarm 28 0 TDU Door Open
chg_eas_alarm 29 0 TDU Circuit Breaker
chg_eas_alarm 30 0 TDU Battery
chg_eas_alarm 31 0 TDU Customer Defined 1
equip bsc GCLK

0
0
no
no
no
equip bsc MSI

0
0
16
0

equip bsc MSI

1
0
15
0
equip bsc MSI
2
0
14
0
equip bsc MTL
0
0
0
16
equip bsc OML
0
0
0
1
equip bsc XBL
0
64
0
0
2
2500
3
7
chg_element opc 15 0
chg_element dpc 33 0
chg_element ni 2 0
chg_element option_alg_a5_1 1 0
chg_a5_alg_pr 1 2 0
chg_ksw_config 0 0 0 1 2 3

equip 0 CIC
5 to 8
0 0
5
0
chg_element option_emergency_preempt 1 0
modify_value 0 nbit 0 MMS 0 0 0
modify_value 0 ber_oos_mon_period 1 MMS 0 0 0
modify_value 0 ber_restore_mon_period 6000 MMS 0 0 0


XBL Equipage ISSUE 10 REVISION 3
XBL Equipage
Overview
Between the RXCDR and the BSC there can exist a fault management communications
link, which is called the XBL. The XBL is able to provide bi-directional communications
between the BSP in the BSC and the BSP in the RXCDR. The purpose of the XBL is to
enable a notification of failed traffic circuits at the RXCDR to be sent to the BSC. The
BSC will then send the appropriate blocking messages to the MSC along the MTL. The
XBL must be equipped at both the RXCDR and BSC as these are separate GSM
entities. A maximum of 2 XBLs can be enabled between each RXCDR and BSC.
Device ID
This number uniquely identifies the XBL within the transcoder. It does not have to be
identical to the id given to the same XBL in the BSC, convention is that it will be.
Data Rate
The XBL can be 16 kbit/s or 64 kbit/s, i.e. occupying a quarter of a timeslot or a whole
timeslot.
First MMS Description

This number identifies the MSI card within the transcoder.
Second MMS Description

This number identifies the port on the MSI card.
Timeslot
This is the timeslot on the MMS.
Group
Only appears if the data rate is 16 kbit/s. Identifies which quarter of the timeslot is used
for the XBL maximum 2 XBLs per timeslot.
LAPD T200 Timer

This is the maximum time the LAPD (Layer 2) transmitter will wait for an
acknowledgement before making a retransmission.
LAPD N200
This is the maximum number of retransmissions a transmitter will make.
LAPD K Value
This is the maximum number of Unacknowledged Information frames a transmitter will
allow before holding up transmission.

EQUIP XBL ID= 0 XBL=0 EQUIP XBL ID=0
AND PLACE IN T S 2 T S =2 AND PLACE IN T S 2

ISSUE 10 REVISION 3 XBL Equipage
Equip XBL
equip (site number) XBL: <CR>
S Enter the device identification for the XBL: 0-9

S Enter the data rate for the XBL: 16 or 64
S Enter the first MMS description for this device: 0-50
S Enter the second MMS description for this device: 0-1
S Enter the timeslot on the MMS where this device
appears: 1-31
S Enter the group of the timeslot where this device
appears: 0-3
S Enter the LAPD T200 Timer value for this device:
200-5000 mS ( in 50 mS intervals)
S Enter the LAPD N200 value for this device: 1-5
S Enter the LAPD K value for this device: 1-127
NOTE: The XBL is also equipped at the BSC. It should

have the same XBL id and must have the same
timeslot at the BSC as at the RXCDR. Also the
LAPD parameters should be the same at each end.

Battery Conservation, Mains Power Failure ISSUE 10 REVISION 3
Battery Conservation, Mains Power Failure
Overview
If an external battery backup supply is available in the case of mains failure, this feature
will extend that battery supplies life by deactivating a specified number of carriers. Mains
failure will be detected by one of the input sensors on the PIX card. The input to be used
can be specified in the database command equip EAS. The text string associated with
such an alarm cannot be specified by the customer and is preset as EAS has detected
main Power Failure. Two chg_element commands further control this feature:
carrier_disable_time
When a mains power failure has occurred the EAS will inform the CA which will wait this
period before disabling the first carrier. The CA will also wait this period in between
disabling subsequent carriers.
carriers_ins_pwr_fail
This number of carriers will always remain in service despite a mains power failure.
Note:
This feature is of no use at an M-Cellmicro site.

ISSUE 10 REVISION 3 Battery Conservation, Mains Power Failure
Battery Conservation, Mains Power Failure
+27v
PIX
MAINS
FAILURE
SENSOR
BATTERY MAINS
BTS 6
chg_element carrier_disable_time <*><SITE NUMBER>

* seconds
chg_element carriers_ins_pwr_fail <*><SITE NUMBER>
* No of carriers

External Alarm System ISSUE 10 REVISION 3
External Alarm System
Overview
The required customer site alarms can be connected through the parallel Interface
extension cards, fitted in the digital cage of In-Cell, upper slots 15 & 16 or the digital
frame in M-Cell. These PIX cards each have eight opto inputs and four dry contact relay
outputs. In database upto 8 cards can be specified per BTS for In-Cell, although each
PIX card must be configured separately for M-Cell only one card can be configured per
cabinet to a maximum of 4 per site. The functionality resides on an AB6 at an M-Cell
site.
First ID
The Identity of the PIX card within the site, for In-cell sites and it is the cabinet id for
M-Cell sites.
Cage ID
The cage identity where the PIX is fitted. (Not prompted at M-Cell sites)
Backplane slot position

Although this field has a valid range of 031 slots, the PIX card can only be fitted into
slots 15 & 16 in an RXU and slots 1518 in a BSU, depending on its age. (Not prompted
at M-Cell sites)
Initial output relay settings

Each output relay can be initially set to the open (1) or closed (0) position. Four outputs
must be set, regardless if they are being used or not.
Input optos no alarm condition

The no alarm condition has to be specified for each of 8 or 16 opto alarm inputs, open
(1) and closed (0). Eight conditions must be set, regardless if they are being used or not.
Reported Opto state changes

The master GPROC will only report on a change of state of an opto input if specified in
this list.
Alarm index
A text string which will appear in a resulting alarm condition can be specified for each of
the 8 or 16 opto inputs. Eight alarm indexes must be specified regardless if they are
being used or not.
The text string mpf is used in place of one of the integers to indicate which opto input is
used for the EAS mains power failure alarm.

ISSUE 10 REVISION 3 External Alarm System
Equip Device EAS
equip (site Number) EAS :
S Enter the first ID for the EAS: 0-15 -MCell

(This is the cabinet id for MCell)
0-7 - InCell
(This is the EAS id for InCell)
S Enter the cage where the PIX is connected: 0-15

(Not prompted for MCell sites)
S Enter the daughter slot where the PIX is located: 15-18

(Not prompted for MCell sites)
S Enter the initial output settings of the 4 relays: 0/1 0/1

0/1 0/1
S Enter the input of the optos for no alarm condition: (0 or

1)
Enter 1 to 8 for InCell and 1 to 16 for MCell sites.
S Enter each opto whose state changes are to be

reported:
Enter 1 to 8 for InCell and 1 to 16 for MCell sites.
S Enter the user defined alarm index for the 8 or 16 optos:

list 0-33, mpf.

EAS Alarm Text String ISSUE 10 REVISION 3
EAS Alarm Text String

As mentioned on the previous page, a text string, which will appear in any resulting alarm
condition, can be specified for each of the eight opto inputs. Thirty-four text string
messages may be entered per BSS (033) each with a unique id.
chg_eas_alarm <1><2><3>
1. Alarm_table_index
Values are in the range 033, thirty-four text strings can be specified for each BSS.
This value corresponds to the number entered as the last parameter in the
equip_device EAS.
2. Severity
The severity level of an alarm can be nominated out of five categories:
0 indeterminate
1 critical
2 major
3 minor
4 warning
3. Text string
The maximum length of the alarm text string is 24 characters and must be entered
between quotation marks, i.e. TEXT.

ISSUE 10 REVISION 3 EAS Alarm Text String
EAS Alarm Text String
chg_eas_alarm <1> <2> <3>
1. alarm table index (0-33)
2. severity (0-4)
3. Text string (upto 24 characters) and must

be entered between quotation marks, i.e.
TEXT"
Note: If an EAS is equipped at an RXCDR this command

must also be entered as the RXCDR has its own OML.

EAS Exercise ISSUE 10 REVISION 3
EAS Exercise
Using the details specified opposite complete the following database parameters:
BTS Script (site

32)
equip _ _ _ _ EAS
____
____
____
____ ____ ____ ____
____ ____ ____ ____ ____ ____ ____ ____
____ ____ ____ ____ ____
____ ____ ____ ____ ____ ____ ____ ____
BTS Script (site

33)
equip _ _ _ _ EAS
____
____ ____ ____ ____
__ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __
____ ____
__ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __
BSC Script
chg_eas_alarm ____ ____ _____________________
chg_eas_alarm ____ ____ _____________________
chg_eas_alarm ____ ____ _____________________
chg_eas_alarm ____ ____ _____________________
chg_eas_alarm ____ ____ _____________________

ISSUE 10 REVISION 3 EAS Exercise
Pix Alarm Details
S SIT E 32, ONLY 1 CAGE
ONLY 1 PIX CARD, SLOT 16 OF BSU
Outputs include:
O/P 1: Burglar alarm reset (rest condition is closed)

O/P 2: Smoke alarm reset (rest condition is open)
Inputs include:
I/P 1: Burglar alarm (alarm condition is open)

I/P 2: Smoke alarm (alarm condition is open)
I/P 3: Door intruder (alarm condition is open)
I/P 4: High temperature (alarm condition is closed)
I/P 5: Low temperature (alarm condition is open)
S SIT E 33 (MCell6 site)
An AB6 with no extension is fitted.
No outputs
Inputs Include:
I/P 1: High temperature (alarm condition is closed)

I/P 2: Low temperature (alarm condition is open)
S All inputs connected to the card are to be reported (i.e. optos used)
S Use appropriate text strings, numbered from 0-4 as per alarm inputs to site 32.
S Alarm severity for all alarms is `major'.
S T he DON'T CARE" option (X) can be specified.

Statistics
Interval
Statistics are uploaded from the BSC to OMC at regular intervals, the interval can be set
to either 30 or 60 minutes using the chg_element stat_interval command. This
parameter is only entered at the BSC and RXCDR (i.e. all site 0s) and must be set to the
same value as all the other BSCs connected to the same OMC. The interval, 30 or 60, is
determined by the OMC system administrator who will enter the same interval at the
OMC.

ISSUE 10 REVISION 3 EAS Exercise
Statistics Interval

OML OML
BSC 1 RXCDR
OMC
OML
OML
BSC 2 BSC 2
chg_element stat_interval 30 0 chg_element stat_interval 30 0

SYS03_2_statistics_interval

MTP Level 3 Parameters ISSUE 10 REVISION 3
MTP Level 3 Parameters
Signalling Point
Codes
The signalling protocol used on the A interface is CCITT signalling system No7. The first
three layers of this protocol are constructed using Message Transfer Part level 1, 2 and
3. Level 3, in a true SSNo7 network, would be responsible for routing messages to
particular signalling points, to enable this each signalling point is allocated a Signalling
Point Code (SPC). This SPC can then be included, within MTP level 3, in any message
directed at that signalling point.
This wider use of signalling point codes is not implemented on the A interface, as
network addressing is further processed by the MSC. Signalling point codes still have to
be entered but only for each end of the A interface.
A network indicator (NI) also has to be specified for each message, again this has a
much wider use in a true SSNo7 network. As far as the MTP layer 3 on the A interface is
concerned each message will terminate at the MSC and therefore the value used for this
parameter should equal 2, for a National Network.

ISSUE 10 REVISION 3 MTP Level 3 Parameters
MTP Level 3
AInterface
BSC MSC
SPC= 15 SPC= 33
Originating Point Code= 15 Originating Point Code= 33

Destination Point Code= 33 Destination Point Code= 15
chg_element opc <value><site>

chg_element dpc<value><site>
chg_element ni <*><site>
* value in range 0-3

0 - international network
1 - spare
2 - national network
3 - reserved for national use

Emergency Call Pre-emption ISSUE 10 REVISION 3
Emergency Call Pre-emption
Overview
The emergency call pre-emption feature, if enabled, will allow a BSS to provide access
for an emergency call on a particular cell regardless of other calls in progress. The
emergency call is identified in the Channel Request with a specified cause value of 101,
upon receipt of this cause value the BSS will make all attempts to assign a channel.
If no idle channels are available when the emergency request is received at the BSS then
the BSS will dislodge a currently active call on the cell in order to make room for the
emergency request. Calls will be dislodged on a priority basis, those with the lowest
priority levels being dislodged first. Emergency calls in progress will not be pre-empted
by other emergency requests.
The emergency call preemption feature is enabled and disabled by a database flag.
Immediate assignment of an emergency channel request to a TCH shall occur in all
cases so long as there are TCHs available.
The following are example scenarios to clarify the processing of an emergency channel
request in respect to resource allocation:
TCH Available for immediate assignment, eme pre-empt flag irrelevant

Request is assigned TCH, call set-up signalling completed, emergency call in progress.
No TCH Available, SDCCH Available, eme pre-empt flag enabled

SDDCH allocated for call set-up, BSS initiates the release of a low priority call. When the
BSS receives the assignment request for the emergency call the BSS queues the
request and waits for the released channel to become available. Emergency call
queueing is independent of normal call queueing (queue_management_information )
and MSC decision, 25 emergency assignment requests are permitted to queue.
No TCH Available, No SDCCH Available, eme pre-empt flag enabled

The emergency channel request is answered by an immediate assignment reject
message. A low priority call is dislodged to free resources for when the MS retries.
The channel freed by this dislodging is not available to ordinary queued calls. The
channel is placed in a reserved list for emergency calls for a period of time
emerg_reserved (crm_timer_value, 8). After this timer expires the channel will be made
available to ordinary assignment requests.

ISSUE 10 REVISION 3 Emergency Call Pre-emption

MS RRSM
Example 1 RACH
Immediate Assignment MS is allocated direct
to a TCH so the
Assignment Command Emergency call can
proceed
Example 2 RACH During this time
Immediate Assignment another dedicated MS
is dropped from a
TCH so the
Assignment Command Emergency call can
proceed
Example 3 RACH During this time

another dedicated MS
Immediate Assignment Reject
Wait is dropped from a
indicatio TCH so the
n period RACH Emergency call can
proceed
sys03_2_emergency_call

Multiple Encryption Algorithms ISSUE 10 REVISION 3
Multiple Encryption Algorithms
Overview
Multiple encryption algorithms can be loaded into the BSS via the software download.
During configuration of the BSC the CA informs the SSM of the encryption algorithms
supported by the BSS software. Purchasable algorithms include A5/0 (Null encryption),
A5/1 (Full encryption) and A5/2 (Prime). When the MSC sends the Cypher mode
command or handover request, the message may include just one or a number of
permitted algorithms. The SSM will then, if given a number of permitted algorithms,
decide which algorithms are to be used upon the following criteria:
1. Capability of the MS as indicated by the classmark.
2. Permitted algorithms supplied by the MSC.
3. Algorithms purchased by the operator (stored in the GSM database).
4. Algorithms supported by the DRIM Firmware.
5. Operator prioritized list of algorithms (stored in the CM database).
If no algorithms meet the above criteria the SSM sends the appropriate failure message,
if the BSS selects the encryption algorithm from the set of more than one supplied by the
MSC the SSM includes the chosen algorithm in the Cypher mode complete or
Handover Request Acknowledge message to the MSC.
The individual algorithms (17) can be used independantly from the multiple encryption
option. i.e. a customer may purchase just A51, therefore, the requirement for multiple
encryption priority is removed.
Multiple A5 Encryption algorithm versions can be purchased by the operator, but cannot
be used unless they have been enabled by the change element option_alg_a5
command and prioritized by the chg_a5_alg_pr database command. The order in which
they are entered prioritizes their use. The encryption algorithms are prioritized on a per
BSS basis and only those prioritized can be used, if no algorithms are prioritized then no
encryption is the default.

ISSUE 10 REVISION 3 Multiple Encryption Algorithms
Multiple Encryption Algorithms
Ho Resource Allocation Cypher mode control
MS BSS MSC MS BSS MSC
Ho request Cypher mode cmd
Ho request Ack Cypher mode cmd
Ho complete Cypher mode complete
Ho complete cypher mode complete
S chg_element option_alg_a5_* <**><0 or bsc>

* 1-7
** 0-disabled
1-enabled
S chg_a5_alg_pr <1st ALG>[<2nd ALG>....<8th ALG>]
(If multiple encryption algorithm is purchased and the
operator is using more than one algorithm)
Parameter Description Values

1st ALG Algorithm with highest 0= no encryption
priority 1= A5/1 2= A5/2
3= A5/3 4= A5/4
5= A5/5 6= A5/6
7= A5/7 Default =0
2nd ALG through Algorithms with Same as above
8th ALG successively less priority

Circuit Error Rate Monitor (CERM) ISSUE 10 REVISION 3
Circuit Error Rate Monitor (CERM)
Overview
The CERM feature provides the ability to identify a discontinuity in a traffic circuit path
through the GSM network from RXCDR to BTS. The path can be divided into two parts,
namely the CIC (RXCDR to BSC) and the radio channel identifier (RCI, BSC to BTS).
The link between these is the switch manager (SM).
The channel coders at the DRI and the XCDR/GDP monitor TRAU frames, i.e. the 3
kbit/s added on to the 13 kbit/s of speech after transcoding and can detect when a valid
TRAU frame is not detected. When this happens, an error is reported to the SM (via
FCP and FTP), which maintains a count of all such errors associated with the CIC and
RCI involved with the call. If this counter reaches a pre-set level an alarm is raised.
TRAU frame error can be detected in 3 ways:
S Initial TRAU errors, where the channel coder is activated and expects to receive
the first TRAU frame within a certain period (initial_sync_timer). If a TRAU
frame is not received within this period, an error indication is sent to FCP.
S Downlink TRAU errors where, after receiving the first TRAU frame, the DRIs
channel coder monitors TRAU frame synchronisation. If it loses synchronisation
for more than downlink_sync_timer, an error indication is sent to FCP.
S Uplink TRAU errors, which are detected by the XCDR/GDPs channel when an
uplink TRAU is not detected. An alarm pattern is sent in the downlink TRAU, to be
detected by the DRIs channel coder. If this pattern exists for the period of
uplink_sync_timer the DRIs channel coder sends an error indication to FCP.

ISSUE 10 REVISION 3 Circuit Error Rate Monitor (CERM)
CERM Error Detection

"

"

! !
!

Circuit Error Rate Monitor (CERM) ISSUE 10 REVISION 3
When a TRAU error is detected in a call, the error counters for both the CIC and the RCI
involved are incremented by cic_error_increment and rci_error_increment
respectively, at the SM, because it is the SMs job to join the CIC and the RCI together. If
the counters reach or exceed cic_error_gen_threshold or rci_gen_threshold
respectively and alarm is generated.
Whenever a call is made, maintained and completed on a CIC/RCI combination with no
TRAU frame errors detected, the counters are decremented by cic_error_decrement
and rci_error_decrement respectively. If the counters fall below
cic_error_clr_threshold or rci_error_clr_threshold respectively the alarms previously
raised are cleared.
It is important to understand that the BSS software cannot distinguish between a CIC
problem and an RCI problem in one particular call; when a TRAU error is detected both
counters are incremented as above. However, probability says that the same CIC/RCI
combination will not be used for subsequent calls, so the CIC and RCI counters will be
incremented and decremented independently over a period of time. Also, due to
handovers, it is possible that a single call could use several different RCIs and more than
one CIC during its course; the definition of call completion used to decrement the
counters is that the CIC or RCI is no longer required, which could be due to termination
or handover.
Note that the timers associated with this feature cannot be modified or displayed at the
BSC unless it is actually a standalone BSS.

ISSUE 10 REVISION 3 Circuit Error Rate Monitor (CERM)
CERM Parameters

initial_sync timer 1500 - 7000 ms

downlink_sync_timer
uplink_sync_timer 1000 - 3000 ms

cic_error_increment 0 - 255
rci_error_increment (0 disables CERM)
cic_error_decrement
rci_error_decrement 1 - 127

cic_error_gen_threshold
rci_error_gen_threshold 2 - 255

cic_error_clr_threshold
rci_error_clr_threshold 0 - 253


Short Message Service Options ISSUE 10 REVISION 3
Short Message Service Options
Overview
There are a number of database parameters which control the use of Short Message
Service. The service itself is specified by GSM and can be divided into two functions Cell
Broadcast and Point to Point.
Cell Broadcast
The GSM defined Cell Broadcast feature is a means of unilaterally transmitting data to
mobiles on a per cell basis, by use of the Cell Broadcast channel. A BSC can be
connected to a Cell Broadcast Centre, which is responsible for downloading cell
broadcast messages to the BSC, together with repetition rate, and the number of
broadcasts required per meassage. The BSC is then responsible for transmitting these
updates to the BTSs affected, which will then ensure that the message is transmitted as
requested.
If this option is purchased and enabled, frequency, slot, and subslot information present
within BCCH system information will cause suitably equipped mobiles to monitor the Cell
Broadcast Channel (CBCH). This channel, when enabled, fits into the 102 frame
multiframe in place of SDCCH subslot 2 on an SDCCH/4, and on the SDCCH subslot
number pointed to by bs_ag_blks_res for an SDCCH/8. It can appear on BCCH or
NonBCCH carriers on timeslots 03 inclusive. Only one CBCH will exist within a cell
and an algorithm specified in GSM 05.02 will control its whereabouts. A cell broadcast
block is made up of 23 bytes (184 bits) which is encoded to produce the familiar 456 bit
block, this is then transmitted over four successive air interface bursts. In a period of 8
multiframes the CBCH will only be transmitted on 4 of them. In the case where the the
CBCH resides on a BCCH carrier dummy bursts will be transmitted in the other 4
multiframes.
The SMS Cell Broadcast service is designed to minimise the battery usage requirements
for an MS. The SMSCB DRX GSM requirement is supported, every 1 minute the cell
will broadcast a scheduler message on the cell broadcast channel. The MS will use this
information to restrict reception to those messages the customer is not interested in
receiving, perhaps because of language or information choice. The MS user may choose
the information he requires through the channel number selection which is a feature on
certain MS mobiles. SMSCB scheduler messages are detailed in GSM 04.12.
SMSCB is a purchaseable feature which is enabled on a cell basis using the following
database command:
chg_element cbch_enabled <*> <site> cell_number=<cell_id>
* 0 disabled
1 enabled

ISSUE 10 REVISION 3 Short Message Service Options
SMS Cell Broadcast

Combined Multiframe DCCH Multiframe

DOWNLINK DOWNLINK
Dummy Bursts (BCCH ONLY)
0

1 2 3 4 5 6 7

0

1 2 3 4 5 6 7

.... ...

4 Successive
51 frame multiframes
Bursts
CBCH 23 Bytes 23 Bytes 23 Bytes 23 Bytes

Multiple Background Messages ISSUE 10 REVISION 3
Multiple Background Messages
Overview
Cell Broadcast backgound messages can be a maximum of 93 characters and will be
sent on the SMSCB channel in the absence of messages originating from the Cell
Broadcast Center (CBC). A maximum of four background messages can be specified
using the following database commands:
chg_smscb_msg <msg_num> <msg_id> <gs> <msg_code> <language>

cell_number= <cell id>
msg_num (03) This number is not sent to the MS, but is used as a
message identifier within the Motorola BSS software.
msg_id (065535) Identifies the logical channel used within the physical
CBSMS slot. This corresponds to the channel number
entered in the MMI of the MS.
gs (03) This field indicates to the MS the geographical area over

which the message code is unique. It also indicates the
display mode to the mobile.
0 Immediate, Cell Wide

1 Normal, PLMN Wide
2 Normal, Location Area (LAC) Wide
3 Normal, Cell Wide
msg_code (01023) This field is used by the MS to differentiate between

different messages being broadcast using the same
msg_id.
<update_number> (015) indicates that an existing message has been
updated. the MS usually does not read the same
message twice, but if an update has occurred this field
causes the MS to decode the message.
language (0255) This field specifies the alphabet/coding scheme being

used in the message. Values specified in W23.
(English= 1)

ISSUE 10 REVISION 3 Multiple Background Messages
Multiple Background Messages


Point to Point SMS Options ISSUE 10 REVISION 3
Point to Point SMS Options
Overview
Point to Point SMS provides a means of sending messages of limited size (255 message
bytes) to and from GSM mobiles. The ability to provide SMS requires a Service Centre
which acts as a store and forward for short messages. To allow for SMS transfer, the
mobile station and BSS must set up the appropriate air interface protocol (LAPD). The
logical channel used for this data transfer will depend on the status of the mobile:
Mobile idle SDCCH used
Mobile on SDCCH SDCCH used
Mobile busy SACCH or FACCH used
The ability to enable/disable mobile originated/terminated SMS is also available.
change_element sms_dl_allowed
change_element sms_ul_allowed

ISSUE 10 REVISION 3 Point to Point SMS Options
Point to Point SMS

* 0 disable
1 enable

Traffic Channel SMS ISSUE 10 REVISION 3
Traffic Channel SMS
Overview
Whilst engaged on a traffic channel the mobile can still receive SMS via FACCH or the
SACCH. If the FACCH is chosen as the means of delivery then an SMS block (23 octets
of information) can be transmitted in 8 successive TDMA frames. Due to the timing
constraints of the SACCH, an SMS block can be delivered in 104 frames if this method of
delivery is used. The disadvantage of FACCH is that traffic frames are stolen, with
injurious effect on the audio quality, this frame stealing would become more noticeable as
the size of the short message increase.

ISSUE 10 REVISION 3 Traffic Channel SMS
Traffic Channel SMS

* 0= via BSS decision
1= FACCH always used
2= SACCH always used

RACH Flow Control ISSUE 10 REVISION 3
RACH Flow Control

These two parameters rach_load_period and ccch_load_period work in conjunction
with a change_element command, rach_load_threshold. These three parameters
provide traffic flow control by allowing the RSS to monitor the number of channel
requests received in a given period. If this number exceeds the rach_load_threshold
then the RSS will transmit a load indication message to call processing.
Call Processing (CP) on receipt of this message will then bar one random access class
(09). Simultaneously CP will start timer t1 & t2 (flow_control_t1 & flow_control_t2).
Only when t1 has expired will CP bar one more access class in receipt of another load
indication message from RSS. If period t2 elapses without CP receiving another load
indication message from RSS then an access class is unbarred. t2 must be greater
than t1.

The decision of which access class is to be barred first is decided at random by CP and
further access classes are barred on a cyclic basis, low to high. All access classes that
subsequently becomes unbarred will not be barred again until every other access class
has also been barred. Unbarring begins where barring started (i.e. the first class to be
unbarred is the class which has been barred longest).
Both the rach_load_period and ccch_load_period are in multiples of 235.5mS (1 x 51
frame). The rach_load_period determines the period over which the RACH load is
monitored. The ccch_load_period is in operation only when an overload condition has
been triggered in the previous period (RACH or CCCH).
The recommended method of calculating rach_load_threshold can be seen opposite.
The numerator consists of the addition of the number of SDCCH sub-slots and TCHs
configured for the cell. The denominator is the number of available RACH slots in 4 x 51
frame multiframes, this will change depending on the value of ccch_conf. This division
is then made into a percentage and can be used as the rach_load_threshold which has
a granuality of 0.01 %.

ISSUE 10 REVISION 3 RACH Flow Control
RACH Flow Control
S rach_load_period=<*> default 16
S ccch_load_period=<*> default 40
* 1-1020 (x235.5ms)
RACH LOAD THRESHOLD

Number of
Conf. Carriers SDCCH TCH ccch_conf Combined TCH/SDCCH
MAX RACH
A 3 16 21 0 NO 18.1%
B 3 16 20 2 NO 8.8%
C 1 4 7 1 YES 10.18%
Rach Load threshold= Total no of channels (TCH/SDCCH)

x 100
No of rachs in 4 x 51 frame multiframes
for Conf A 37 x 100= 18.1%

204

CRM Flow Control ISSUE 10 REVISION 3
CRM Flow Control
Overview
CRM flow control can result from RACH, CRM and SSM overload. CRM overload control
can be enabled by the change_element command tch_flow_control. It is further
controlled by two parameters tch_busy_critical_threshold and
tch_busy_norm_threshold.
When the CRM allocates a TCH it checks both of the above thresholds. If the
tch_busy_norm_threshold is exceeded then the CRM will randomly bar one access
class 09. Upon barring this class two timers are started T1 and T2 flow_control_t1
and flow_control_t2. T1 and T2 control the rate at which access classes are barred
and unbarred. If the threshold is once more exceeded when T1 is still running, an
access class will not be barred. If T1 has expired and T2 is still running and the
threshold is exceeded then another access class is randomly barred. At this point T1
and T2 are restarted. Access classes are unbarred upon the expiry of successive T2
periods.
If tch_busy_critical_threshold is exceeded the CRM will bar any remaining unbarred
classes two at a time, each subsequent time the threshold is exceeded. T1 and T2 still
take an active part in barring and unbarring classes.

ISSUE 10 REVISION 3 CRM Flow Control
Flow Control
chg_element . . . .
tch_flow_control <*><site>cell_number=<cell number>
* 0 Disabled
1 Enabled
tch_busy_critical_threshold <*> <site number>
tch_busy_norm_threshold <*> <site number>
* % of Busy TCH's

CRM Flow Control ISSUE 10 REVISION 3

Chapter 3
Power and Handover Control

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 3
Power and Handover Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Power and Handover Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MS Measurement Cycle, Traffic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
MS Measurement Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
BSS Measurement Averaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
N and P Voting Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hreqave/Hreqt and N/P Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Diagram Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Oscillation Prevention For MS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Oscillation Prevention for BTS Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
The Power Budget Assessment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Downlink RXLEV Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Adapted Power Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Uplink Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Power Budget Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Handover Decision Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Neighbouring Cell Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Sporadic Neighbour Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Maximum Disuse Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Criterion 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Criterion 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Per Cause, per Neighbour Handover Margins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Handover Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Uplink/Downlink Quality Handover Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Quality Handover Bounce Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Uplink/Downlink Interference Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Quality Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

ISSUE 10 REVISION 3
Intra-cell Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Uplink Level Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Distance Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Power Budget Handover Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

ISSUE 10 REVISION 3 Power and Handover Control
Objectives
On completion of this chapter the student should be able to:
S Understand Power Control.
S Understand the Power Budget Assessment process.
S Understand criteria 1 and 2.
S Understand the uses of Quality Flags.
S Understand the RSS process involved in every handover type.

Power and Handover Control ISSUE 10 REVISION 3
MS Measurement
Cycle, Traffic
Mode
The mobile station has the opportunity to measure neighbour BCCH frequencies
between the uplink transmission and downlink reception of consecutive TDMA frames.
There are 26 measurement opportunities within the 26 frame multiframe, although a
mobile may only measure on 25, the idle frame may be excluded.
The period between transmission and reception will equal four burst periods plus the
timing advance, in total a time greater than 2mS.
GSM recommendations require a mobile to report on the best six neighbours at least
once per second. The reporting period is based on a SACCH multiframe, 480mS, and
therefore it would normally be possible for a mobile to report on the best six neighbours
twice in a one second period. This is subject to parallel activity on the SACCH (SMS
perhaps).
The mobile can make 100 or 104 measurement samples of neighbours within a SACCH
multiframe period, the number of samples per neighbour would depend on the number of
neighbours in the BA list. For example, a BA list of 10 neighbours would lead to 1011
measurements per neighbour, these 10 or 11 measurements would result in one overall
average per measurement period.

ISSUE 10 REVISION 3 Power and Handover Control
MS Measurement Cycle
A Mobile Receives
Serving Neighbour
C Mobile Transmits Mobile retunes

D and listens to
B Mobile Neighbour cell
TDMA Retunes and retunes to
serving cell
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
Downlink A B C D
Sample
1ms 2ms
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
Uplink
SYS03_3_measurement_cycle

MS Measurement Reporting ISSUE 10 REVISION 3
MS Measurement Reporting
Overview
At the end of each measurement reporting period (480mS) the mobile is able to produce
an overall, unweighted average for each neighbour in the BA list. The mobile will then
report the best six neighbours averages to the BSS in the form of an uplink SACCH
message. A SACCH message is made up of 4 successive SACCH bursts.
The bulk of the measurement report contains the averaged RXLEV of each of the best
six neighbours, to qualify each RXLEV average the neighbours BCCH frequency and
BSIC are included. The measurement report begins with the timing advance and uplink
power level the MS is currently using, as instructed by the BSS in the previous downlink
SACCH.
The BA flag is also included to confirm the neighbour list used when making the last
periods measurements. The DTX flag is also present to confirm uplink DTX. The mobile
actively measures the downlink transmission of the serving cell, for quality and level.
These two are averaged over the SACCH period and reported in the next period. When
the base station is employing downlink DTX it will only examine the sub Rxlev and
RxQual values in the uplink measurement report as these are averaged by the MS over
the mandatory downlink Silence Description frames on burst 5259 (modulo 104) of the
previous SACCH period.

ISSUE 10 REVISION 3 MS Measurement Reporting
MS Measurement Report
FREQ
RXLEV BSIC
28 2 0 0 17 0 17 0 6 34 23 66 . . . . . . 28 26 66
Rxlev & Rxlev & NCell 1 NCell 6

RxQual RxQual
(Full) (Sub)
Power DTX
Level Used
BA Number of
Used Neighbours
Timing
Advance

BSS Measurement Averaging ISSUE 10 REVISION 3
BSS Measurement Averaging
Overview
Similar to the MS producing one average for DL Rxlev, DL Rxqual and DL Rxlev of each
neighbour per measurement period, the BSS also produces one average per
measurement period of each of UL Rxlev, UL Rxqual, timing advance and UL channel
interference on idle DRCU slots.
All of the above measurements are re-averaged by the RSS, at present this process
produces a series of unweighted averages every SACCH multiframe, three parameters
control this averaging function hreqave, hreqt, and intave.
hreqave: The number of reported averages required to produce one rolling
average as one instance of hreqt.
hreqt: The number of averages retained in the Handover software task, needs
to be at least equal to the n parameter for that particular threshold.
intave: The number of interference averages, reported by the (D)RCU, that are
used to produce one rolling average every 480 mS.
Note:
Hreqt & Hreqave have a maximum value of 32, although Hreqt x Hreqave for the same
averaging process must equal 32 or less (Hreqt x Hreqave 32)
Hreqave and Hreqt must be defined for:

Rxqual UL/DL Handover (_ho) & Power Control (_pc)
Rxlev UL/DL Handover (_ho) & Power Control (_pc)
Surrounding Cell DL Handover (s_cell)
Timing AdvanceMS to BS Timing advance (rel_tim_adv)
Intave and Hreqt must be defined for:

Idle Interference UL Idle Channel Processing

BSS Rolling Averages
ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
UPLINK SACCH MEASUREMENT REPORTS FOR 1 NEIGHBOUR HREQAVE= 4
HREQT= 2
480mS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

A E
averages A B C D C G E I .............
performed
B F D H
A ~ average of sacch measurements 1-4 G average of sacch measurements 7-10
B ~ average of sacch measurements 2-5 H average of sacch measurements 8-11
BSS Measurement Averaging

C ~ average of sacch measurements 3-6 I average of sacch measurements 9-12
D ~ average of sacch measurements 4-7

E ~ average of sacch measurements 5-8
F ~ average of sacch measurements 6-9
37
N and P Voting Mechanism ISSUE 10 REVISION 3
N and P Voting Mechanism
Overview
Together with Hreqave and Hreqt the N and P voting mechanism will ensure that a power
control or handover decision is made over a number of averages and not just a snapshot
of mobile activity. The N and P parameters for each decision process can be entered in
the add_cell command, they are defined as follows:
N defines the number of BSS produced averages required for a decision to be
made.
P defines the minimum number of BSS produced averages, over the threshold
value, to cause a positive trigger.
A vote occurs for each decision process every SACCH multiframe. If P out of N votes
exceed the threshold then a handover/power control condition will be flagged.
As a special note:
N hreqt

ISSUE 10 REVISION 3 N and P Voting Mechanism
N and P Voting Mechanism
HREQAVE= 5
HREQT = 4
= 4
= 3
E
D
23
N5
P5
C
B
A
Z
22
Y
X
W
V
21
U
T
exceed l_dl_rxlev_h
VOTE 3 OUT OF 4
S
R
MEASUREMENT REPORTS 20
Q
P
BSS AVERAGES
UPLINK SACCH
FOR DL RXLEV
Hreqave/Hreqt and N/P Relationship ISSUE 10 REVISION 3
Hreqave/Hreqt and N/P Relationship
Diagram
Overview
On the diagram opposite is shown a stream of serving downlink measurements as
reported by the mobile at each reporting period. Hreqave has been set at 4 and Hreqt
has been set at 3. The RXLEV Downlink handover threshold has been set to 90dBm.
Setting the P of N number to a higher value, ie 3 out of 3 will delay the handover trigger,
this effect may be desirable as it will reduce the possibility of the mobile bouncing back to
the source cell. However, in a situation where the slow fade effect was accelerated by a
fast moving vehicle the RXLEV of the source may become to low to perform such
handover.
Setting the P out of N number to a lower value, i.e. 2 out of 3 will trigger a quicker
handover, increasing the chance of the mobile bouncing back to the source cell, but
ensuring an RXLEV of sufficient value to perform the handover.

RXLEV HO TRIGGER RXLEV HO TRIGGER
N=3 N=3
P=2 P=3
ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000

-85 -86 -87 -88 -88 -88 -89 -91 -91 -91 -91 -92 -94 -94 -95 -96 -97 -97 -98 -98 -99
-91 -93.75 -97
-90.5 -92.75 -96.25
HREQAVE= 4
HREQT= 3
-89.75 -92 -95.5
L_RXLEV_DL_H= 20 (-90dBm)
-88.75 -91.25 -94.75

HREQAVE/HREQT and N/P Relationship
-89 -91 -93.75
-87.75 -90.5 -92.75
-87.25 -89.75 -92
-86.5 -89 -91.25 Values in dBm
311
Hreqave/Hreqt and N/P Relationship ISSUE 10 REVISION 3
Diagram
Overview
The diagram opposite represents exactly the same mobiles measurements reports and
similar parameters except Hreqave has been set to 3.
The result of this has been a quicker response to the need for a handover trigger, by
reducing the size of the rolling average window.

RXLEV HO TRIGGER RXLEV HO TRIGGER
N=3 N=3
ISSUE 10 REVISION 3
P=2 P=3
EMOTOROLA LTD. 2000

-85 -86 -87 -88 -88 -88 -89 -91 -91 -91 -91 -92 -94 -94 -95 -96 -97 -97 -98 -98 -99
Values in dBm
-90.3 -91.3 -94.3
-89.3 -91 -93.3
HREQAVE= 3
HREQT= 3
-88.7 -91 -92.3
L_RXLEV_DL_H= 20 (-90dBm)

-88 -90.3 -91.7
HREQAVE/HREQT and N/P Relationship
-87.7 -89.3 -91
-87 -88.3 -91
-86 -88 -90.3
313
Power Control ISSUE 10 REVISION 3
Power Control
As previously mentioned Downlink serving power as perceived by the mobile is reported
in the uplink SACCH message, in addition the uplink power is also processed by the BSS
and averaged in the same manner. The HDPC tries to maintain the mobile within an
uplink and downlink power window, this process is subject to the N & P voting
mechanism described previously. The following equations summarise this:
RXLEV_XX u U_RXLEV_XX_P DECREASE (TXPWR)
t L_RXLEV_XX_P INCREASE (TXPWR)
all others NO ACTION
RXQUAL_XX u U_RXQUAL_XX_P DECREASE (TXPWR)
t L_RXQUAL_XX_P INCREASE (TXPWR)
all others NO ACTION
XX ~ UL/DL
As both Quality and Level Processing is occurring simultaneously the resultant action of
combinations involving both increments and decrements through both causes, in the
same processing period, is shown opposite. These resultant actions are only valid when
decision_alg_number = 0.
When decision_alg_number=1 ms and bts_p_con_ack will be used and the table
functions opposite will be amended slightly.

ISSUE 10 REVISION 3 Power Control
Power Control Combinations For Uplink and Downlink
RXLEV_XX RXQUAL_XX Result
1 Decrease Decrease Decrease
2 Decrease Increase No action***
3 Decrease No action Decrease
4 Increase Increase Increase
5 Increase Decrease Increase*
6 Increase No action Increase
7 No action No action No action
8 No action Decrease Decrease**
9 No action Increase Increase**
* There is no such thing as too good" quality.
** Before this decision is taken it will be checked for possible

oscillation.
*** If you wish the increase in quality to take precedence in this situation
set the algorithm to on in the add_cell command. This is done using
decision_alg_number= 1. Remember this will mean you will now
use MS and bts_p_con_ack.

Oscillation Prevention For MS Power Control ISSUE 10 REVISION 3
Oscillation Prevention For MS Power Control
Overview
The problem mentioned on the previous page is more complex than it seems. If the
pow_red_step_size_ul is equal to 2 dB and the situation mentioned in serial 8 occurs
then the HDPC will check if the present power level 2 dB is not below l_rxlev_ul_p if
this is the case then a power decrease is ordered. The problem occurs because of the
specified tolerance in mobiles which is +/ 1.5dBm. Thus although the HDPC calculates
that the threshold will not be exceeded, in actual fact, depending on the tolerance of the
mobile, it could be. The pow_inc_step_size_ul set by many operators is 6 dBm, to
allow for a fast recovery in the case of a rxlev problem. The problem diagram opposite
shows the effect of this.
This oscillation can be prevented by an algorithm within the HDPC such that the power
level remains reasonably constant just above the lower rxlev threshold and does not
allow subsequent power decreases through rxqual.
The algorithm is only initiated when the rxlev drops below the rxlev threshold when the
last power control instruction was a decrease because of quality. The HDPC will
compute the increase necessary and will adjust the power increment step size to that
which is required and not use the set database value. The effect of oscillation would be
reduced although the condition may still exist to a smaller degree, this mainly due to the
computing algorithm being constrained to using fixed 2 dB steps. To remove these
oscillations completely the HDPC will track when successive power control increases
through rxlev follow power decreases through rxqual. If this is the case power control
decreases through rxqual will not be ordered. The solution diagram opposite shows
this effect
The database field controlling the use this algorithm can be found in add_cell:
mspwr_alg=<*>
* 0 enhanced power control algorithm not used
1 enhanced power control algorithm used.

ISSUE 10 REVISION 3 Oscillation Prevention For MS Power Control
Oscillation Prevention for MS Power Control
Problem
RXLEV
30
28
26
24
22
20
18
16
l_rxlev_ul_p = 20
u_rxqual_ul_p = 100
Solution
RXLEV
30
28
26
24
22

20
18
16
mspwr_alg = <*>
* 0 enhanced power control algorithm not used
1 enhanced power control algorithm used

Oscillation Prevention for BTS Power Control ISSUE 10 REVISION 3
Oscillation Prevention for BTS Power Control
Overview
With the implementation of this feature, the BSS prevents BTS power downlink
oscillations when a decision to decrease power level due to good quality is immediately
followed by a decision to increase power due to a low power level.
To prevent unnecessary power changes, oscillation is detected and controlled. If the
following condition is true then a quality-based power reduction will not be performed.
av_rxlev_dl<(l_rxlev_dl_p + pow_red_step_size_dl + 2dB)

ISSUE 10 REVISION 3 Oscillation Prevention for BTS Power Control
Oscillation Prevention for BTS Power Control
No quality based power reduction if:
av_rxlev_dl< (l_rxlev_dl_p + pow_red_step_size_dl + 2 dB)
63 -47 dBm
u_rxlev_dl_p
av_rxlev_dl 1
2
pow_red_step_size_dl + 2 dB av_rxlev_dl
l_rxlev_dl_p
0 -110 dBm
1 Quality based power reduction allowed
2 Quality based power reduction not allowed

The Power Budget Assessment Process ISSUE 10 REVISION 3
The Power Budget Assessment Process
Overview
To gain an understanding of the BSS Handover mechanism it is essential to understand
the power budget assessment process.
The Power Budget formula can be considered in two parts, the left hand side considers
the serving cell and the right hand side the neighbour cell. The power budget calculation
is carried out every half second (SACCH multiframe) for each reported neighbour of all
mobiles engaged in traffic. The assessment is not subject to N & P voting.
"!" " !

"!" "

At first glance this formula is very complex to understand and needs to be broken down
to discover its real purpose. The aim of the formula is to afford the mobile the lowest
uplink pathloss.

ISSUE 10 REVISION 3 The Power Budget Assessment Process
Power Budget Assessment
All Values in dBm

Min (ms_txpwr_max, P) - Rxlev_DL - PWR_C_D
Min (ms_txpwr_max, P) - Rxlev_DL

NEIGHBOUR
SERVING
-
PBGT (n) =

Downlink RXLEV Only ISSUE 10 REVISION 3
Downlink RXLEV Only
Overview
Probably the most important factor in any handover decision and selection process
should be the mobiles perception of its serving downlink level as compared to neighbours
downlink level. This is accounted for in the power budget expression:

As can be noted, all the other inputs to the formula have been removed and this level
comparison can be easily seen. PBGT(n) will become a value greater than 0 if the
reported neighbour level becomes greater than the server.

ISSUE 10 REVISION 3 Downlink RXLEV Only
Considering RXLEV Only


Adapted Power Consideration ISSUE 10 REVISION 3
Adapted Power Consideration
Overview
A direct level comparison is not always correct because the mobile is potentially reporting
adapted power on the serving cell whereas, the neighbour is being measured at its full
BCCH power level. A correction factor must therefore be considered:

Where PWR_C_D= max_tx_bts Actual BTS ouput power.

PWR_C_D will always equal a positive value, or zero when the MS can no longer be
maintained in the downlink power window.

ISSUE 10 REVISION 3 Adapted Power Consideration
Adapted Power Correction Factor


Uplink Consideration ISSUE 10 REVISION 3
Uplink Consideration
Overview
Remember that the aim of this formula is to provide the mobile with the lowest uplink
pathloss, so far the uplink path has not been considered. The first part of each side of
the formula provides this comparison.
min (ms_txpwr_max OR P)
ms_txpwr_max of the server equates to the value specified in max_tx_ms in the
add_cell. ms_txpwr_max of the neighbour can be specified in add_neighbour for an
external cell. For an internal neighbour ms_txpwr_max will be specified by max_tx_ms
in the neighbours add_cell. The value of P equates to the maximum power of the
mobile concerned.
The power budget formula is designed for a mobile suited to the PLMN being used, that
is that the mobile always has sufficient power to support all cells within the PLMN. In this
case the P value is never used and the ms_txpwr_max is always the deciding uplink
factor. The following examples illustrate this ideal.

ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
CONDITION 1
S EQUALLY SIZED CELLS
S MS ABLE TO SUPPORT SERVER AND NEIGHBOUR
S max_tx_ms (SERVER)= ms_txpwr_max (NEIGHBOUR)
PBGT (n) > 0

SERVER NEIGHBOUR
BCCH BCCH
327

ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
CONDITION 2
S LARGE SERVER, SMALL NEIGHBOUR
S max_tx_ms (SERVER) >ms_txpwr_max (N EIGHBOUR)
PBGT (n) > 0

SERVER
NEIGHBOUR
PBGT(n)= [HIGHER SERVER] - [LOWER NEIGHBOUR]
329

ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
CONDITION 3
S SMALL SERVER, LARGE NEIGHBOUR
S max_tx_ms (SERVER) < ms txpwr_max (NEIGHBOUR)
PBGT (n) > 0

SERVER NEIGHBOUR
PBGT(n)= [LOWER SERVER] - [HIGHER NEIGHBOUR]
331
Power Budget Exercise ISSUE 10 REVISION 3
Power Budget Exercise

The figures specified on the facing page can be used by the HDPC to calculate the
Power budget assessment. Use the working area to calculate PBGT (n)

serving = min (ms_txpwr_max,P) Rxlev_DL PWR_C_D
serving =
serving =

neighbour = min (ms_txpwr_max(n),P) RXLEV_NCELL (n)
neighbour =
neighbour =
PBGT (n)= serving Neighbour
PBGT (n)=
PBGT (n)=

ISSUE 10 REVISION 3 Power Budget Exercise
Power Budget Example
S SERVING CELL DATABASE PARAMETERS

Cell identity= 234 10 255 038
max_tx_ms= 39
max_tx_bts= 0
ms_txpwr_max_def= 39
add_neighbour external 234 10 256 039
ms_txpwr_max_cell= 39
S BEST NEIGHBOUR DATABASE PARAMETERS

Cell identity= 234 10 256 039
ms_txpwr_max_def= 39
ms_txpwr_max_cell= 39
S RXLEV AVERAGE
SERVING (Reported)= -90dBm
NEIGHBOUR= -75 dBm
S SERVING CELL DL OUTPUT POWER= 32dBm
S MOBILE= CLASS 4
CLASS MAX POWER dBm

1 20W 43
2 8W 39
3 5W 37
4 2W 33
5 0.8W 29

Handover Decision Procedure ISSUE 10 REVISION 3
Handover Decision Procedure
Overview
The BSS handover procedure will usually take place every SACCH multiframe, for each
MS engaged in a call. The following procedure does not include any reference to the
microcellular feature, the handover procedure in this case is covered in the SYS08
course.
The ho_counter decreases from a maximum equal to ho_recognised_period. The
counter will be reset to this maximum immediately a handover recognised message has
been sent from RSS to CP. As can be clearly seen if a ho_recognised_message has
been sent within ho_recognised_period, the RSS will not process handover decisions for
that MS.
The RSS will progress through each handover decision in a priority order:
ul_rxqual (ul_interference)
dl_rxqual (dl_interference)
ul_rxlev
dl_rxlev
ms_distance
power budget
If a handover is triggered through one decision process in the priority list, the others
further down the list are ignored. That handover trigger will then lead to further
processing.
For each handover decision in turn the RSS will first check that the specified handover
type has been enabled, and then, if necessary process the voting decision. If a handover
has been disabled then that decision mechanism is skipped.
Both ul and dl positive quality decisions are further processed to determine whether the
handover is indeed quality or interference

ISSUE 10 REVISION 3 Handover Decision Procedure

hd This process start every 480 ms
ho counter=0 NO decrement ho
counter MEAS_REP_WT
(ho_rec_period) (await meas rep)
ho_rec_period
YES
NO
ul_rxqual_ho_allowed
flag set?
YES NO
at least decision_1_p6 YES YES at least decision_1_p7 NO

out of decision_1_n6 out of decision_1_n7 set cause =
RXQUAL_UL averages interfer_ho_allowed RXLEV_UL averages UL_RXQUAL
>L_RXQUAL_UL_H? flag set? >U_RXLEV_UL_IH?
YES
NO
set ho.cause = HO
UL_INTERFERENCE
NO
dl_rxqual_ho_allowed
flag set?
YES NO
at least decision_1_p6 YES YES at least decision_1_p7 NO

out of decision_1_n6 out of decision_1_n7 set cause =
RXQUAL_DL averages interfer_ho_allowed RXLEV_DL averages DL_RXQUAL
>L_RXQUAL_DL_H? flag set? >U_RXLEV_DL_IH?
NO YES
set ho.cause = HO
hd1 DL_INTERFERENCE


hd1
NO
ul_rxlev_ho_allowed
flag set?
YES
NO
at least decision_1_p5
out of decision_1_n5 set ho.cause = UL_RXLEV
RXLEV_UL averages
>L_RXLEV_UL_H?
YES
HO
NO
dl_rxlev_ho_allowed
flag set?
YES
NO
out of decision_1_n5 set ho.cause = DL_RXLEV
RXLEV_DL averages
>L_RXLEV_DL_H?
YES
HO
NO
ms_distance_allowed
flag set?
YES
YES
out of decision_1_n8 set ho.cause = DISTANCE
MS_BTS averages
>MS_RANGE_MAX?
NO
HO
hd2

The lowest priority for processing is the Power Budget handover. The condition that must
be met for this cause value is as follows:
PBGT (n) > ho_margin
The handover margin for each neighbour can be set differently. The margin is specified in
the add_neighbour command, although this field is optional for internal cells and may
be interpolated by the servers ho_margin_def value, found in add_cell.

hd2
NO
Pwr_handover_allowed
flag set?
YES
YES
PBGT>ho_margin set ho.cause = PBGT
for any neighbour
cell?
NO
HO
MEAS_REP_WT
(await meas rep)
IF no handover causes have triggered return to hd earlier in the

procedure and start again on receipt of the next measurement report.

All handover triggers for any cause value will be further processed in the manner shown
opposite. Criterion 1 and Criterion 2 are fully explained on the pages that follow.
After completion of these two criteria, neighbours identified as passing criterion 1, with
their results from criterion 2 (positive or negative), are passed to a specific handover
process consistent with the original cause value.



Neighbouring Cell Processing ISSUE 10 REVISION 3
Neighbouring Cell Processing
Sporadic
Neighbour
Reporting
A mobile will report up to 6 neighbours every sacch period, those neighbours reported in
that period are considered qualified candidates for further Criteria 1 and 2 processing.
A neighbour can often be reported sporadically, in that it falls in the top six neighbours in
one report and then out of the top six in the next. This sporadically reported neighbour
may, under certain conditions, be considered as qualified for further Criteria 1 and 2
processing. This qualification is dependent upon the parameters neighbor_journal and
disuse_cnt_hreqave:
neighbor_journal= 0
Each time a neighbour is not reported a Disuse counter is incremented, only neighbours
having a disuse counter of zero are considered qualified. This means that a neighbour
can only be qualified if reported in the last sacch period. For averaging in subsequent
sacch periods the number used to compute hreqt for that missing report is repeated from
the last reported value. If the disuse counter should reach a maximum (as defined by
disuse_cnt_hreqave) then that neighbours previous reports are deleted and its
averaging mechanism will be reset.
neighbor_journal= 1
Qualified neighbours are those having a disuse count less than the surround_cell
hreqave value. This time the value used to calculate hreqt when the neighbour is not
reported will equal 110 dBm. Previous reports for that neighbour are deleted when the
disuse counter equals a maximum value (as defined by disuse_cnt_hreqave).
In addition there is no warm up period for neighbours. Initially, all neighbour information
is padded with values of 110dBm and averaging/power budget calculations will begin
immediately.

ISSUE 10 REVISION 3 Neighbouring Cell Processing
Sporadic Neighbour Reporting
neighbor_journal= 0
hreqave= 4
Disuse R R R NR NR R R R NR R
Counter
0 0 0 1 2 0 0 0 1 0
Q Q Q NQ NQ Q Q Q NQ Q
RXLEV
80 82 81 81 81 79 82 83 83 79
hreqt
hreqt
neighbor_journal= 1 hreqt
hreqave= 4
R R R NR NR R R R NR R
Disuse
Counter
0 0 0 1 2 0 0 0 1 0
Q Q Q Q Q Q Q Q Q Q
RXLEV 80 82 81 110 110 79 82 83 110 79
hreqt
hreqt
hreqt
Key
NR - Not Reported Q - Qualified
R - Reported NQ - Not Qualified

Neighbouring Cell Processing ISSUE 10 REVISION 3
Maximum Disuse
Counter
The disuse count is the number of consecutive measurement reports not reported by a
mobile station and relating to a previously reported neighbour. If the neighbour is
reported before a maximum disuse count is reached, then the disuse count is reset to
zero. If the disuse count reaches a maximum then that neighbours previous reports are
deleted and its averaging mechanism reset.
The maximum disuse count is set using the database parameter disuse_cnt_hreqave.
disuse_cnt_hreqave= 0
The maximum disuse count is set to 8.
disuse_cnt_hreqave= 1
Tha maximum disuse count is defined by the surrounding cell hreqave.

ISSUE 10 REVISION 3 Neighbouring Cell Processing
Neighbouring Cell Processing
chg_cell_element neighbor_journal <*><site><cell_desc>
* 0- warmup period allowed.
last received RXLEV for unreported

neighbour is used.
1- No warm up period allowed
Value of -110 dBm used for unreported

neighbour
(default= 0)
chg_cell_element disuse_cnt_hreqave<*><site><cell_desc>
* 0- Max disuse count= 8
1- Max disuse count = surrounding cell hreqave
(default= 0)

Criterion 1 ISSUE 10 REVISION 3
Criterion 1
Criterion 1 ensures that the mobile is perceiving each neighbours Rxlev at a power level
good enough for the downlink path to support a good call, criterion 1 is as follows:
Rxlev_ncell > Rxlev_min(n) + Max (0, Pa)
Rxlev_ncell is the latest averaged average processed for that neighbour. Rxlev_min (n)
is the database parameter set in the add_neighbour command. For internal cells
rxlev_min_cell is optional and if not specified then rxlev_min_def in the add_cell
command of the server is used.
The last part of this calculation tempers the perceived downlink rxlev average with the
potential uplink path.
max (0, Pa) where Pa= ms_txpwr_max(n) P
P= max power of ms
If the MS is suited for the PLMN in question Pa will always equal either zero or a
negative value and will therefore not be considered.
If the MS is not suited to that neighbour, i.e. its maximum power can not support that
required by that cell then the averaged Rxlev_ncell would have to become a greater
value to overcome this handicap. Criterion 1 would therefore prevent such a handover
until the MS was deeper into that neighbour.
Any neighbour failing Criterion 1 is not further considered in any handover decision
process.

ISSUE 10 REVISION 3 Criterion 1
First Criterion


Criterion 2 ISSUE 10 REVISION 3
Criterion 2
Each neighbour, for that mobile, that satisfies criterion 1 is then subjected to criterion 2:
CRITERION 2 = PBGT(n) Ho_margin
Ho_margin for both external and internal cells can be specified in the add_neighbor
command. For internal cells this parameter is optional and if not specified then the
ho_margin_def in the add_cell of the server is used.
Criterion 2 will produce a result for each neighbour, either positive or negative. That result
is further considered in the specific handover procedure to follow.

ISSUE 10 REVISION 3 Criterion 2
Second Criterion


Per Cause, per Neighbour Handover Margins ISSUE 10 REVISION 3
Per Cause, per Neighbour Handover Margins
Overview
After a handover has been triggered as described earlier it is possible to influence which
neighbour(s) are selected as target(s) for the handover. This influence takes place in two
ways, namely that criterion 2 sorts the neighbours in order from best to worst and then
neighbours can be excluded in different ways depending upon the cause value.
The approach taken in criterion 2 depends upon the ho_margin_usage_flag parameter.
If set to 0, criterion 2 is as normal, ie, Pbgt(n) ho_margin. If this parameter is set to 1,
however, then criterion 2 is modified as follows:
S RxQual HOs: Pbgt(n) ho_margin_rxqual(n)
S RxLev HOs: Pbgt(n) ho_margin_rxlev(n)
S All other HO causes: Pbgt(n) ho_marginl(n)
Neighbour cell exclusion tests are carried out in the relevant handover processes after
Criteria 2 as follows. Remove the neighbour from the candidate list if:
S RxQual HOs: Pbgt(n) ho_margin_rxqual(n)<0
S RxLev HOs: Pbgt(n) ho_margin_rxlev(n)<0
S Better Cell HO: Pbgt(n) ho_marginl(n)<0
Using these handover margins it is possible to exclude particular types of handover from
particular cells by setting the relevant margin to 63, the highest value, for that neighbour.
ho_margin_rxqual(n) and ho_margin_rxlev(n) are set using the modify_neighbor
command

ISSUE 10 REVISION 3 Per Cause, per Neighbour Handover Margins
Per Cause, per Neighbour Handover Margins
"

!
"

!


Handover Processing ISSUE 10 REVISION 3
Handover Processing
Overview
After completion of criteria 1 and 2, neighbours identified as passing criterion 1 and
ordered using criterion 2 are passed to a specific handover process consistent with the
original cause value.
Depending upon the cause value the specific handover process may further depend upon
the setting of the element ho_only_max_pwr.
ho_only_max_pwr
If this parameter is enabled (1), the MS/BTS must be at full power before a RXLEV or
RXQUAL handover can be performed.
In addition, all candidates for interference handovers are removed until the MS/BTS is at
full power.
Note:
decision_alg_num=1 must be used with this functionality to allow the MS/BTS to reach
full power for quality cases.

ISSUE 10 REVISION 3 Handover Processing
Handover Processing

" !

Note:
"

Uplink/Downlink Quality Handover Processing. ISSUE 10 REVISION 3
Uplink/Downlink Quality Handover Processing.
Overview
The uplink and downlink quality handover procedures are identical.
If one or more handover candidates are available then the procedure opposite will take
place, making use of the quality flags if set.
The following flags have been appended to the standard averaging algorithm to allow
RXQUAL_UL/DL type handovers despite a potentially poorer RF path. The specifics of
how to enter these flags will be covered later.
qual_pwr_flag (0/1)
If enabled (1) will only allow further decision processing if the MS or BS is fully powered
up, this will function as a check to verify that power control has had a chance to fight the
quality problem.
qual_margin_flag (0/1)
If enabled, each handover candidate is further subjected to neighbour protection. The
idea being to eliminate neighbours with a poor Criterion 2 result from being included in
the final ho_recognised message.
If this flag is disabled, then no neighbour protection is provided and candidates with
potentially poor Criterion 2 results will be included in the final ho_recognised message.
adj_qual_margin (031)
With the qual_margin_flag set, this margin will be used to increase the PBGT(n) of
each neighbour.
Note:
The ho_recognised command will only be sent if num_ho_cand > 0.

ISSUE 10 REVISION 3 Uplink/Downlink Quality Handover Processing.
Uplink/Downlink Quality Handover Processing
Uplink/Downlink
ho_process
For each candidate:

YES
pwr_bgt-ho_margin_rxqual < 0, if yes,
ho_margin_usage_flag remove neighbour from cand list and
=1 decrement num_ho_cand
NO
YES
num_ho_cand=0 Abort handover
NO
NO
YES
MS/bts
ho_only_max_pwr ul/dl
=1 Full power?
NO NO YES
YES MS/bts
qual_pwr_flag ul/dl
set? Full power?
NO YES
For each candidate:

pwr_bgt + adj_qual_margin < 0
YES if yes remove neighbour from
qual_margin_flag cand list and decrement
set? num_ho_cand
NO
send ho_rec message with

num_ho_cand cells ordered best
to worst by criterion 2 result
(only if num_ho_cand > 0)
decison_alg_num= 1 must be used with ho_only_max_pwr and qual_pwr_flag.

Quality Handover Bounce Protection ISSUE 10 REVISION 3
Quality Handover Bounce Protection
Overview
When performing a handover to a new cell, due to rxqual problems in the serving cell, it
is possible that the serving cells rxlev could be much better than the target cells rxlev.
Thus, after arriving in the target cell, the mobile could immediately hand over back to the
original server due to Pbgt, followed very quickly by another rxqual handover, and so
one. This condition is known as ping-pong or bouncing.
To cure this problem, an extra handover margin bounce_protect_margin can be added
for a defined period of time bounce_protect_qual_timer in the target cell after a
channel is activated in that cell. This makes it more difficult for the mobile to hand over
back to the original cell after an rxqual handover.
The same functionality can be applied after a handover due to congestion relief, but is
controlled by the bounce_protect_cong_timer.

ISSUE 10 REVISION 3 Quality Handover Bounce Protection
Bounce Protection
Server Neighbour
Qual HO
Pbgt HO
Good level Bad level
S chg_ele bounce_protect_margin <*> <cell_desc>
<*>= 0 to 127 dB
S chg_ele bounce_protect_qual_tmr <*><cell_desc>
S chg_ele bounce_protect_cong_tmr <*><cell_desc>
<*>= 0 to 255 SACCH multiframes

(0=disabled)

Uplink/Downlink Interference Handover Procedure ISSUE 10 REVISION 3
Uplink/Downlink Interference Handover Procedure

Once again the uplink and downlink interference handover procedures are identical.
The uplink/downlink interference handover procedure is similar to the uplink/downlink
quality handover except the at the ho_recognised command will be sent, even if
num_ho_cand= 0.

ISSUE 10 REVISION 3 Uplink/Downlink Interference Handover Procedure
Uplink/Downlink Interference Handover Procedure
Uplink/Downlink
ho_process
YES
num_ho_cand=0 Abort handover
NO
NO
YES MS/bts
ho_only_max_pwr ul/dl
=1 Full power?
YES
NO
NO
YES MS/bts
qual_pwr_flag ul/dl
set? Full power?
NO YES
For each candidate:

YES pwr_bgt + adj_qual_margin < 0
if yes remove neighbour from
qual_margin_flag cand list and decrement
set? num_ho_cand
NO
send ho_rec message with

num_ho_cand cells ordered best
to worst by criterion 2 result
decison_alg_num= 1 must be used with ho_only_max_pwr and qual_pwr_flag.

Quality Flag ISSUE 10 REVISION 3
Quality Flag
Exercise
The mobile shown opposite has run into an area of poor quality although the RXLEV
downlink from the serving cell is reasonably good.
Assume that all handover types have been enabled.
The N + P voting mechanisms for downlink quality and downlink interference have both
triggered a handover.
Using the details opposite calculate whether the ho_recognised message is sent, and
specify if the message contains any neighbours.
Work out PBGT(n):
SERVING
serving= min (ms_txpwr_max,P) - Rxlev_DL - PWR_C_D
serving= - -
serving=
NEIGHBOUR
neighbour= min (ms_txpwr_max(n),P - RXLEV_NCELL(n)
neighbour= -
neighbour=
PBGT (n)= serving - neighbour
PBGT (n)= -
PBGT (n)=

ISSUE 10 REVISION 3 Quality Flag
Quality Flag Exercise
CELL ID= 234 10 256 039

CELL ID= 234 10 255 038
DATABASE PARAMETERS
max_tx_ms= 25
max_tx_bts= 7 (29dBm)
ho_only_max_pwr= 0
add_neighbor external
Ho_margin= 6
ms_txpwr_max_cell=25
Rxlev_min_cell= 20 (-90dBm)
Quality_pwr_flag= 0
Qual_margin_flag= 1
Adj_quality_margin= 6
ho_margin_usage_flag= 0
MOBILE CLASS 2
Only Reported Neighbour

Rxlev_dl= -70 dBm
Reported Server
Rxlev_dl= -65 dBm
BTS O/P Power= 20 dBm
POOR QUALITY

Intra-cell Handovers ISSUE 10 REVISION 3
Intra-cell Handovers
Intra-cell handovers due to interference are subject to a limit which, when exceeded,
causes the mobile to handover to a different cell. The number of intra-cell handovers
performed in a call is counted, and if this number exceeds hop_count in a period defined
by hop_count_tmr, then the handover is modified to be inter_cell with a cause value of
quality. This prevents the situation where carrier is suffering heavy downlink interference
but the CRM thinks it is a clean frequency because the uplink (monitored during idle
periods) is clean. Regular intra-cell handovers would occur due to downlink interference,
with the new channel selected on the basis of uplink interference each time. So after
hop_count_timer period, the call will be handed over to a new cell.
If no neighbors are suitable targets for the inter cell handover, then the call stays in the
source cell and continues until hop_count is exceeded again, when another attempt at
inter cell handover is made.

ISSUE 10 REVISION 3 Intra-cell Handovers
S
!

S


Intra-cell Handovers ISSUE 10 REVISION 3
When an intra-cell handover is attempted the CRM tries to allocate a new channel on a
different carrier frequency than the original channel. If no channels are available on the
different carrier then the CRM tries to allocate a channel on the same carrier, and if none
are available this time the handover is aborted.
In non-hopping cells the BCCH carrier traffic channels are preferred as targets, while in
hopping cells a non-BCCH carrier is preferred; in both cases, if no channel is available on
the preferred carrier then the CRM selects its best channel in the usual way.
The intra-cell handover may move a call to a channel with worse uplink interference, but
statistically it is more likely to benefit the call than handing over to a different timeslot on
the same carrier.
This function is always enabled and requires no database entries.

ISSUE 10 REVISION 3 Intra-cell Handovers
S

S


Uplink Level Handover Procedure ISSUE 10 REVISION 3
Uplink Level Handover Procedure
Overview
The uplink handover procedure is much the same as the downlink level case. The only
real difference is that the RSS does not remove weaker candidates from the
ho_recognised message.

ISSUE 10 REVISION 3 Uplink Level Handover Procedure
Uplink Level Handover Procedure
"

!
%$# ! #
#

!
# % !
Note: decision_alg_num= 1 must be used if ho_only_max_pwr is to be enabled.

Downlink Level Handover Procedure ISSUE 10 REVISION 3
Downlink Level Handover Procedure
Overview
After completion of criteria 1 and 2, neighbours identified as passing criterion 1 and
ordered using criterion 2 are passed to a specific handover process consistent with the
original cause value.
Depending upon the cause value the specific handover process may further depend upon
the settings of the two elements worse_neighbor_ho and ho_only_max_pwr.
worse_neighbor_ho
If this parameter is enabled (1), neighbours with lower RXLEV than the current serving
cell are allowed as valid candidates. Otherwise these neighbours are removed from the
candidate list.

ISSUE 10 REVISION 3 Downlink Level Handover Procedure
chg_cell_element . . . .
worse_neighbor_ho <*><location><cell desc>
* 0- disable HO to a neighbour with lower

RXLEV than serving cell
1- enable HO to neighbour with lower

RXLEV than serving cell
(default= 0)

Downlink Level Handover Procedure ISSUE 10 REVISION 3
Overview
Only candidates passing Criterion 1 are considered further in the downlink level handover
procedure. The process followed will depend upon the settings of
ho_margin_usage_flag, ho_only_max_pwr and worse_neighbor_ho.
If ho_only_max_pwr is enabled and no candidates have a positive criterion 2 then the
handover will be aborted if the BTS is not at max_tx_bts (as specified in add_cell). If the
BTS is transmitting at full power and worse_neighbor_ho is NOT enabled, then an
RXLEV check is made to delete possible target cells having weaker RXLEV than the
server. This deletion of a candidate will happen if the last computed neighbour RXLEV
average is less than the last computed serving cell RXLEV average. When the handover
recognised message is sent it will contain neighbours ordered on a best to worst basis
using the results from criterion 2.
Note:
decision_alg_num=1 must be used if ho_only_max_pwr is to be enabled.

ISSUE 10 REVISION 3 Downlink Level Handover Procedure
Downlink level
ho_process
For each candidate:

NO pwr_bgt-ho_margin_rxlev <
ho_margin_usage_flag
0 if yes remove neighbour
=0 from cand list and decrement
num_ho_cand
YES
Remove candidates with

NO
lower RXLEV than the server
worse_neighbour_ho
from candidate list.
=1
Decrement num_ho_cand
YES
YES
Abort num_ho_cand=0
NO
NO
BTS on full ho_only_max_pwr

power? =1
YES NO
Send ho_rec message with

num_ho_cand cells ordered
best to worse by Criterion 2
results
Note: decision_alg_num=1 must be used if ho_only_max_pwr is to be

enabled.

Distance Handover Procedure ISSUE 10 REVISION 3
Distance Handover Procedure
Overview
The distance handover procedure will only result in a handover recognised message if
candidates have met criterion 1. Criterion 2 is used as a scaling factor to position each
candidate in the ho_recognised message.

ISSUE 10 REVISION 3 Distance Handover Procedure
Distance Handover Procedure

!

! "


Power Budget Handover Procedure ISSUE 10 REVISION 3
Power Budget Handover Procedure
Overview
The power budget handover procedure will only result in a ho_recognised message when
candidates have a positive Criterion 2 result. Any candidates not meeting this criterion
are omitted from the message.

ISSUE 10 REVISION 3 Power Budget Handover Procedure
Power Budget Handover Procedure
"
!

#
#

" !

"

" #


Power Budget Handover Procedure ISSUE 10 REVISION 3

Chapter 4
BTS Script Building

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 4
BTS Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BTS Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Script Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
BTS 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Missing Report (add_cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Hreqave and Hreqt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Pointing Averaging Mechanisms to Decision Processes . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Special Case of RXLEV_DL_HO and SURROUND_CELL . . . . . . . . . . . . . . . . . . . . . . . . 424
Averaging Mechanisms, Decision Processes and Thresholds . . . . . . . . . . . . . . . . . . . . . 426
Alternate Processing of RXQUAL Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Weighted Quality Flag w_qual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Interference Averaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
RF Resource Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Support of BCCH/SDCCH in GSM Extension Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 BTS Script Building
BTS Script Building
Objectives
S Understand all the parameters used within a Base Transceiver Station database
script.

BTS Script Building ISSUE 10 REVISION 3
BTS Script Building
Script Chart
The script building chart shown opposite specifies the groups of parameters necessary to
populate a BTS database. The actual parameters can be examined more closely by
following the example script overleaf.

ISSUE 10 REVISION 3 BTS Script Building
BTS Script Building Chart


BTS 1.6.0.x Script Files ISSUE 10 REVISION 3
BTS 1.6.0.x Script Files

# EXAMPLE MCELL6 BTS DATABASE
# GSR4 (1.6.0.0)
# 3 CARRIER OMNI WITH CCB
equip 0 SITE
4
LCF
0
64
no
equip 4 CAB
0
11
1
add_cell 2 3 4 0 1 678 4 4 Swindon East
frequency_type = 1
bsic = 8h
wait_indication_parameters = 20
ccch_conf = 0
bs_ag_blks_res = 1
bs_pa_mfrms = 1
extended_paging_active = 1
number_sdcchs_preferred = 8
en_incom_ho = 1
intra_cell_handover_allowed = 1
inter_cell_handover_allowed = 1
number_of_preferred_cells = 6
ho_margin_def = 8
handover_recognized_period = 12
ul_rxqual_ho_allowed = 1
dl_rxqual_ho_allowed = 1
ul_rxlev_ho_allowed = 1
dl_rxlev_ho_allowed = 1
sdcch_ho = 0

ISSUE 10 REVISION 3 BTS 1.6.0.x Script Files
sdcch_timer_ho = 1
interfer_ho_allowed = 1
pwr_handover_allowed = 1
ms_distance_allowed = 0
mspwr_alg = 0
handover_power_level = 6
pwrc = 1
intave = 8
timing_advance_period = 4
ms_p_con_interval = 2
ms_p_con_ack = 2
ms_power_control_allowed = 1
bts_p_con_interval = 4
bts_p_con_ack = 2
bts_power_control_allowed = 0
pow_inc_step_size_ul = 6
pow_inc_step_size_dl = 6
pow_red_step_size_ul = 4
pow_red_step_size_dl = 4
dyn_step_adj= 0
dyn_step_adj_fmpr = 10
max_tx_bts = 0
max_tx_ms = 31
rxlev_min_def = 0
ms_txpwr_max_def = 31
decision_alg_num = 0
decision_1_dl_rxlev_av_h = 1
decision_1_dl_rxlev_av_ih = 0
decision_1_dl_rxlev_av_p = 0
decision_1_dl_rxqual_av_h = 0
decision_1_dl_rxqual_av_p = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_ncell_rxlev_av_h_calc = 0
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
decision_1_p_bgt_rxlev_av_h = 0
decision_1_tim_adv_av_alg = 0
decision_1_ul_rxlev_av_h = 0
decision_1_ul_rxlev_av_ih = 0
decision_1_ul_rxlev_av_p = 0
decision_1_ul_rxqual_av_h = 0
decision_1_ul_rxqual_av_p = 0
alt_qual_proc = 0
l_rxqual_ul_p = 226

l_rxqual_dl_p = 226
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 400
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
link_about_to_fail = 1
full_pwr_rfloss = 1
cell_bar_access_switch = 0
cell_bar_access_class = 0
emergency_class_switch = 0
report_resource_tch_f_high_water_mark = 1
report_resource_tch_f_low_water_mark = 5
rxlev_access_min = 0
dtx_required = 0
attach_detach = 0
ncc_of_plmn_allowed = 2h
max_retran = 3
ms_txpwr_max_cch = 6
tx_integer = 12
radio_link_timeout = 2
reestablish_allowed = 1
cell_reselect_hysteresis = 2
cell_reselect_param_ind = 0
cell_bar_qualify = 0
cell_reselect_offset = 0
temporary_offset = 0
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 40
rpd_offset = 8
rpd_period = 2
chg_element cbch_enabled 1 4 cell_number = 2 3 4 0 1 678 4

chg_act_alg_data surround_cell 2 3 4 0 1 678 4 0 0 8,0
chg_act_alg_data rel_tim_adv 2 3 4 0 1 678 4 0 0 4,0
chg_act_alg_data rxlev_dl_ho 2 3 4 0 1 678 4 0 0 8,0

chg_act_alg_data rxlev_dl_pc 2 3 4 0 1 678 4 0 0 8,0

chg_act_alg_data rxlev_ul_ho 2 3 4 0 1 678 4 0 0 8,0
chg_act_alg_data rxlev_ul_pc 2 3 4 0 1 678 4 0 0 8,0
chg_act_alg_data rxqual_dl_ho 2 3 4 0 1 678 4 0 0 2,0
chg_act_alg_data rxqual_dl_pc 2 3 4 0 1 678 4 0 0 2,0
chg_act_alg_data rxqual_ul_ho 2 3 4 0 1 678 4 0 0 2,0
chg_act_alg_data rxqual_ul_pc 2 3 4 0 1 678 4 0 0 2,0
chg_element max_number_of_sdcchs 32 4 cell_number = 2 3 4 0 1 678 4
chg_element sdcch_need_low_water_mark 10 4 cell_number = 2 3 4 0 1 678 4
chg_element interfer_bands,0 0 4 cell_number = 2 3 4 0 1 678 4
equip 4 BTP
0
equip 4 MSI
0
0
0
equip 4 COMB
0
0
00
01
equip 4 EAS
0
0000
1111111111111111
12345678
01234567

equip 4 DRI
00
0
fox
0
2 3 4 0 1 678 4
1
00
0
1
4
equip 4 DRI
01
0
fox
1
2 3 4 0 1 678 4
1
00
1
1
4
equip 4 DRI
02
0
fox
2
2 3 4 0 1 678 4
1
00
2
1
4
chg_element rf_res_ind_period 20 4
chg_element tch_busy_norm_threshold 95 4
chg_element tch_busy_critical_threshold 95 4
Note:
The MMS priority and gclk_sync enable are not shown. These commands can be part of
the PATH statement.


Missing Report (add_cell) ISSUE 10 REVISION 3
Missing Report (add_cell)
Overview
The RSS expects an uplink measurement report from the ms every half second (SAACH
multiframe), this report may not arrive perhaps due to SMS, or the message itself may
have been corrupted and could not be decoded. In either situation the RSS has missed
a report. The action, by the RSS, upon missing this report is controlled by a database
flag in add_cell.
When the flag is set to one, in respect of downlink, it is as if that reporting period did not
take place at all, no storing, averaging, decision making, or actions will be taken upon the
expiry of the SAACH period. Subsequent reporting periods will continue to average in the
normal way ignoring the missed period. For the uplink case, averaging and decision
making will progress in the normal way.
When the flag is set to zero, the previously received report is repeated and averaging
goes ahead as normal, all related voting etc continues.

ISSUE 10 REVISION 3 Missing Report (add_cell)
Missing Report (add_cell)
FLAG= 1
Report missing
No downlink voting
No P_bgt calculated
Hreqt= 2
Hreqave= 4
FLAG= 0
repeated
Voting continues
P_bgt calculated
S missing_rpt= 0/1
1- measurement not repeated

0- measurement repeated

Hreqave and Hreqt ISSUE 10 REVISION 3
Hreqave and Hreqt

Both of these parameters are specified individually for each averaging mechanism in
every cell.
chg_act_alg_data <alg name><cell id><bin_num>
<alg_num><alg_data>,<index>
<alg_name>
The algorithm name specifies the averaging mechanism to be enabled.

surround_cell neighbour Rxlev
rel_tim_adv timing advance
rxlev_dl_ho rxlev downlink handover
rxlev_ul_ho rxlev uplink handover
rxlev_dl_pc rxlev downlink power control
rxlev_ul_pc rxlev uplink power control
rxqual_dl_ho rxqual downlink handover
rxqual_ul_ho rxqual uplink handover
rxqual_dl_pc rxqual downlink power control
rxqual_ul_pc rxqual uplink power control
Note:
For surround_cell it is possible to use the hreqave value set here only to produce the
neighbour rxlev measurement used in target cell selection processing (eg criterias 1 and
2). A different hreqave can be set in add_neighbor for neighbor rxlev calues to be used
in power budget handover trigger calculations. In both cases, hreqt is set to 1 by default
as no voting is involved in power budget calculations. To use the per neighbour hreqave
value, the parameter use_neighbor_pbgt_hreqave must be set to 1 and a 0 value means
the per cell value shown here will be used in all cases.

ISSUE 10 REVISION 3 Hreqave and Hreqt
Hreqave and Hreqt


Hreqave and Hreqt

<cell_id>
GSM cell identity
<bin_num>
In most cases only one set of algorithm data will be necessary for each averaging
mechanism, this data, calculated from the hreqt/hreqave specified, will be stored in a
software bin. It is possible to create more than one set of algorithm data for each
averaging mechanism specifying different hreqt/hreqave for each. The maximum
number of sets being equal to four and therefore bin numbers are in the range 03.
<alg_num>
There are two possible algorithms which can be applied, weighted (1) and unweighted
(0). The weighted algorithm can only be applied to quality related decisions (pc/ho) and
requires a specified weighting factor. The unweighted algorithm can be applied to all
averaging mechanisms.
If this is set to 255 then the alg_data and index are not prompted. This may only be
done if no decision parameters are using this specifed bin or no DRIs or RTFs are
associated with the specified cell.
This algorithm number bears no relation to the microcellular purchasable option algorithm
number.

Hreqave and Hreqt


Hreqave and Hreqt

<alg_data>
alg_data specifies the value of hreqt, hreqave and in the case of rxqual averaging
mechanisms the quality flags and weighting factor.
<index>
The index points to which parameter the data belongs.
The table opposite summarises the last two fields.
Note:
The product of Hreqt and Hreqave can, at maximum equal 32, as only 32 averages can
be stored at any moment in time.

Hreqave and Hreqt
chg_act_alg_data <alg_name><cell_id><bin_num>
<alg_num><alg_data>, <index>
Averaging
Parameter <index> <alg data> Mechanisms
Hreqave 0 1-31 ALL
Hreqt 1 1-31 ALL
Only Rxqual_pc/ho
qual_weight 2 0-255 Only required if quality
weighting alg_num=1
Rxqual_ho Intefere_ho
qual_pwr_flag 3 0/1 Note: This can only be set to
a 1 if decision_alg_num= 1
qual_margin_flag 4 0/1 Rxqual_ho

Intefere_ho
Adj_qual_margin 6 -63 to Rxqual_ho

+63 dBs Intefere_ho

Pointing Averaging Mechanisms to Decision Processes ISSUE 10 REVISION 3
Pointing Averaging Mechanisms to Decision Processes

Each averaging mechanism produces at least one set of averages every SACCH
multiframe, these averages are used by decision processes controlling handover and
power control. The software bin where each set of averages are stored has to be
pointed to the decision process utilising them. This pinpointing is specified in add_cell.
A simple example to focus on is uplink power control:
chg_act_alg_data rxlev_ul_pc 5 4 2 1 0F111h 0 0 4, 0
chg_act_alg_data rxlev_ul_pc 5 4 2 1 0F111h 0 0 8, 1
The data produced by this averaging mechanism can only possibly be used by one
decision process, decision_1_ul_rxlev_av_p=0. The decision process points to bin
number 0 where the averaging data has been stored in the chg_act_alg_data
command.
NUMBERS N & P DEFINITIONS AVERAGING BIN

POINTER
decision_1 .............
N1/P1 Power Increase due to Level dl_rxlev_av_p
ul_rxlev_av_p
N2/P2 Power Decrease due to Level dl_rxlev_av_p
ul_rxlev_av_p
N3/P3 Power Increases due to Qual dl_rxqual_av_p
ul_rxqual_av_p
N4/P4 Power Decreases due to Qual dl_rxqual_av_p
ul_rxqual_av_p
N5/P5 Handover decision - Level dl_rxlev_av_h
ul_rxlev_av_h
N6/P6 Handover decision - Qual dl_rxqual_av_h
ul_rxqual_av_h
N7/P7 Handover decision - dl_rxlev_av_ih
Lev/interference ul_rxlev_av_ih
N8/P8 Handover decision - Timing tim_adv_av_alg
Advance
Note: N must equal or be lower than HREQT. P must be equal to or lower than N.

ISSUE 10 REVISION 3 Pointing Averaging Mechanisms to Decision Processes
Pinpointing Averaging Processes to Decision Algorithms

Criteria 1 and 2 for every handover

chg_act_alg_data surround_cell 5 4 3 2 1 0F11h 2220h 0 0 8, 0
chg_act_alg_data surround_cell 5 4 3 2 1 0F11h 2220h 0 0 1, 1
Rxlev_dl ho averages are also required for criteria 2, they are

pointed to by decision_l_p_bgt_rxlev_av_h
handover_required_reject_switch=0
T3103= 4100
T3101= 1700
Downlink Rxlev Handover
decision_alg_num= 0
decision_1_dl_rxlev_av_h= 0 chg_act_alg_data rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 8, 0
decision_1_dl_rxlev_av_ih= 0 chg_act_alg_data rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 4, 1
decision_1_dl_rxlev_av_p= 0
decision_1_dl_rxqual_av_h= 0

decision_1_dl_rxqual_av_p= 0
decision_1_n1= 2
decision_1_n2= 2
decision_1_n3= 8
decision_1_n4= 8
decision_1_n5= 4
decision_1_n6= 2
decision_1_n7= 4
decision_1_n8= 2
decision_1_ncell_rxlev_av_calc=0
decision_1_p1= 2
decision_1_p2= 2
decision_1_p3= 8
decision_1_p4= 8
decision_1_p5= 3
decision_1_p6= 2
decision_1_p7= 4
decision_1_p8= 2
decision_1_p_bgt_rxlev_av_h= 0
decision_1_tim_adv_av_alg= 0
decision_1_ul_rxlev_av_h= 0
decision_1_ul_rxlev_av_ih= 0
decision_1_ul_rxlev_av_p= 0
decision_1_ul_rxqual_av_h= 0
decision_1_ul_rxqual_av_p= 0
interfer_bands,0= 0
interfer_bands,1= 8
Uplink Interference Handover

chg_act_alg_data rxlev_ul_ho 5 4 3 2 1 0F111h 2220h 0 0 8, 0
chg_act_alg_data rxlev_ul_ho 5 4 3 2 1 0F111h 2220h 0 0 4, 1



Pinpointing Averaging Processes to Decision Algorithms

Downlink Rxqual Power Control
chg_act_alg_data rxqual_dl_pc 5 4 3 2 1 0F111h 2220h 0 0 4, 0
chg_act_alg_data rxqual_dl_pc 5 4 3 2 1 0F111h 2220h 0 0 8, 1

Timing Advance Handovers

chg_act_alg_data rel_tim_adv 5 4 3 2 1 0F111h 2220h 0 0 4, 0
chg_act_alg_data rel_tim_adv 5 4 3 2 1 0F111h 2220h 0 0 2, 1

Uplink RXLEV Power Control

chg_act_alg_data rxlev_ul_pc 5 4 3 2 1 0F111h 2220h 0 0 4, 0
chg_act_alg_data rxlev_ul_pc 5 4 3 2 1 0F111h 2220h 0 0 8, 1

Downlink Rxlev Power Control

chg_act_alg_data rxlev_dl_pc 5 4 3 2 1 0F111h 2220h 0 0 8, 0
handover_required_reject_switch=0 chg_act_alg_data rxlev_dl_pc 5 4 3 2 1 0F111h 2220h 0 0 4, 1
T3103= 4100
T3101= 1700

decision_alg_num= 0
decision_1_dl_rxlev_av_h= 0 Downlink Rxqual Handover
decision_1_dl_rxlev_av_ih= 0
decision_1_dl_rxlev_av_p= 0 chg_act_alg_data rxqual_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 2, 0
decision_1_dl_rxqual_av_h= 0 chg_act_alg_data rxqual_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 2, 1
decision_1_dl_rxqual_av_p= 0 chg_act_alg_data rxqual_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 0, 3
decision_1_n1= 2 chg_act_alg_data rxqual_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 1, 4
decision_1_n2= 2 chg_act_alg_data rxqual_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 4, 6
decision_1_n3= 8
decision_1_n4= 8 Hreqt, Hreqave used in the N & P process
decision_1_n5= 4 Quality flags also specified
decision_1_n6= 2
decision_1_n7= 4
decision_1_n8= 2
decision_1_p1= 2
decision_1_p2= 2
decision_1_p3= 8 UPLINK Rxqual Handover
decision_1_p4= 8
chg_act_alg_data rxqual_ul_ho 5 4 3 2 1 0F111h 2220h 0 0 2, 0
decision_1_p5= 3
decision_1_p6= 2
decision_1_p7= 4
decision_1_p8= 2
Hreqt, Hreqave used in the N & P process
decision_1_ul_rxlev_av_ih= 0 Quality flags also specified
decision_1_ul_rxlev_av_p= 0
decision_1_ul_rxqual_av_h= 0 UPLINK RXQUAL Power control
decision_1_ul_rxqual_av_p= 0
chg_act_alg_data rxqual_ul_pc 5 4 3 2 1 0F111h 2220h 0 0 4, 0
interfer_bands,0= 0
chg_act_alg_data rxqual_ul_pc 5 4 3 2 1 0F111h 2220h 0 0 8, 1
interfer_bands,1= 8


As will be noted from the previous page, data produced by one averaging mechanism
can be used by more than one decision process. The table opposite illustrates this:
It is possible that multiple sets of averages can be produced by each averaging
mechanism to provide a different averaging strategy for each decision. rxlev_dl_ho, for
example can be used by three different decision processes, this is the reason for having
multiple bins.
In the case where a decision process uses two averaging mechanisms, the bin number
points to both, for example:
decision_1_p_bgt_rxlev_av_h=0
This would indicate bin 0 for the surround_cell averages and also bin 0 for the
rxlev_dl_ho averages.

Pointing Averaging Mechanisms to Decision Processes


Special Case of RXLEV_DL_HO and SURROUND_CELL ISSUE 10 REVISION 3
Special Case of RXLEV_DL_HO and SURROUND_CELL

In general an averaging process has only one decision process using it, take
rel_tim_adv, this averaging process is only used by the decision process
decision_1_ tim_adv_av_h.
The averaging processes Rxlev_dl_ho and surround_cell are special cases in that
these values are used by the following decision processes.
Averaging Process Decision Process
Rxlev_dl_ho dl_rxlev_av_h
p_bgt_rxlev_av_h
Criteria 2 (for every handover)
dl_rxlev_av_ih
Surround_cell p_bgt_rxlev_av_h
Criteria 1 & 2 (for every handover)
As these averaging processes are used by a number of decision processes it is possible
to specify different Hreqt/Hreqave pairs in each case. This is done by using separate
bins, and specifying different values for Hreqt/Hreqave.
The example opposite clearly shows this.

ISSUE 10 REVISION 3 Special Case of RXLEV_DL_HO and SURROUND_CELL
Rxlev_dl_ho and Surround_cell
Extract from add_cell
handover_required_reject_switch=0
T3103= 4100 Downlink Rxlev Handover
T3101= 1700
decision_alg_num= 0 chg_act_alg rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 4, 0
decision_1_dl_rxlev_av_h= 0 chg_act_alg rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 0 0 4, 1
decision_1_dl_rxlev_av_ih= 0
decision_1_dl_rxlev_av_p= 0
decision_1_dl_rxqual_av_h= 0
decision_1_dl_rxqual_av_p= 0
decision_1_n1= 2
decision_1_n2= 2
decision_1_n3= 8 Criteria 1 and 2 for every handover
decision_1_n4= 8
decision_1_n5= 4 chg_act_alg surround_cell 5 4 3 2 1 0F111h 2220h 0 0 4, 0
decision_1_n6= 2 chg_act_alg surround_cell 5 4 3 2 1 0F111h 2220h 0 0 1, 1
decision_1_n7= 4
decision_1_n8= 2

decision_1_p1= 2
decision_1_p2= 2
decision_1_p3= 8
decision_1_p4= 8
decision_1_p5= 3
decision_1_p6= 2
decision_1_p7= 4
decision_1_p8= 2
decision_1_ul_rxlev_av_ih= 0
decision_1_ul_rxlev_av_p= 0 Power Budget Assessment
decision_1_ul_rxqual_av_h= 0
decision_1_ul_rxqual_av_p= 0 chg_act_alg rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 1 0 8, 0
interfer_bands,0= 0 chg_act_alg rxlev_dl_ho 5 4 3 2 1 0F111h 2220h 1 0 1, 1
interfer_bands,1= 8 chg_act_alg surround_cell 5 4 3 2 1 0F111h 2220h 1 0 8, 0
chg_act_alg surround_cell 5 4 3 2 1 0F111h 2220h 1 0 1, 1
Hreqt/Hreqave for rxlev_dl and surround cell both using the

second bin (number 1).

Averaging Mechanisms, Decision Processes and Thresholds ISSUE 10 REVISION 3
Averaging Mechanisms, Decision Processes and Thresholds

See diagram opposite.

ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
Activity Link Enable Averaging Decision Threshold Voting Notes
Quality Up ul_rxqual_ho_allowed rxqual_ul_ho decision_1_ul_rxqual_av_h l_rxqual_ul_h P6, N6 Used by

interference
Handover handover
Down dl_rxqual_ho_allowed rxqual_dl_ho decision_1_dl_rxqual_av_h l_rxqual_dl_h P6, N6
as well
Level Up ul_rxlev_ho_allowed rxlev_ul_ho decision_1_ul_rxlev_av_h l_rxlev_ul_h P5, N5
handover Down dl_rxlev_ho_allowed rxlev_dl_ho decision_1_dl_rxlev_av_h l_rxlev_dl_h P5, N5

Relevant
Averaging Mechanisms, Decision Processes and Thresholds

Interference Up interfer_ho_allowed rxlev_ul_ho decision_1_ul_rxlev_av_ih u_rxlev_ul_ih P7, N7 quality
handover
Handover Down interfer_ho_allowed rxlev_dl_ho decision_1_dl_rxlev_av_ih u_rxlev_dl_ih P7, N7 must trigger
first
Distance
- - ms_distance_allowed rel_tim_adv decision_1_tim_adv_av_alg ms_max_range P8, N8 Uplink only
Handover
Power rxlev_dl_ho No voting as

Budget - - pwr_handover_allowed decision_1_pbgt_rxlev_av_hhandover_margin -- latest hreqt
handover surround_cell used
l_rxlev_ul_p P1, N1
Power Up ms_power_control_allowedrxlev_ul_pc decision_1_ul_rxlev_av_p u_rxlev_ul_p (increase)
Control
due to l_rxlev_dl_p P2, N2
Level Down bts_power_control_allowedrxlev_dl_pc decision_1_dl_rxlev_av_p
u_rxlev_dl_p (decrease)
Power l_rxqual_ul_p P3, N3

Up ms_power_control_allowedrxqual_ul_pc decision_1_ul_rxqual_p (increase)
Control u_rxqual_ul_p
due to l_rxqual_dl_p P4, N4
Quality Down bts_power_control_allowedrxqual_dl_pc decision_1_dl_rxqual_p
427
u_rxqual_dl_p (decrease)
Alternate Processing of RXQUAL Measurements ISSUE 10 REVISION 3
Alternate Processing of RXQUAL Measurements

Radio path quality measurements for active calls are reported by the RCU and mobile
station. These measurements allow the HDPC to make handover decisions and power
control adjustments based on the uplink and downlink quality of the link. These
measurements are reported to the HDPC in the form of quality bands ranging from 07
where 0 corresponds to little or no deterioration of receive quality on the channel and 7
corresponds to greater than 12.8% bit error rate on the channel. These bands, once
received by the HDPC, are mapped to an assumed BER value (defined in GSM 05.08),
they are then stored and averaged in the usual way using the defined hreqt and hreqave
values specified. The resulting hreqt number of averages are then used in the applicable
voting decision for handover and power control.
An alternate way of processing the rxqual measurements exists, in that the reported
bands, 07, can be used as the input to the averaging mechanism, instead of the
assumed BER. This modification will also require the threshold parameters to be based
on bands aswell, as the reaveraged values produced will of course be related to the
bands rather than BER percentages.
This option can be specified by the add_cell flag:
alt_qual_proc=<*>
* 0 processing based on BER
1 processing based on quality bands
As mentioned above this flag will impact the setting of the quality threshold parameters in
add_cell, those affected will be:
l_rxqual_ul_p
l_rxqual_dl_p
u_rxqual_ul_p
u_rxqual_dl_p
l_rxqual_ul_h
l_rxqual_dl_h
They should each be set in the following ranges:
alt_qual_proc=0 01810
alt_qual_proc=1 07

ISSUE 10 REVISION 3 Alternate Processing of RXQUAL Measurements
Alternative Processing of RXQUAL Measurements
RXQUAL Range
BER ASSUMED BER
0= Less than 0.2% 0.14%

1= 0.2 - 0.4% 0.28%
2= 0.4 - 0.8% 0.57%
3= 0.8 - 1.6% 1.13%
4= 1.6 - 3.2% 2.26%
5= 3.2 - 6.4% 4.53%
6= 6.4 - 12.8% 9.05%
7= Greater than 12.8% 18.1%
add_cell .........
alt_qual_proc = <*>
* 0 - processing based on BER
1 - processing based on quality Bands
0 1
L_rxqual_ul_p
l_rxqual_dl_p
u_rxqual_ul_p
01810% 07
u_rxqual_dl_p
l_rxqual_ul_h
l_rxqual_dl_h

Weighted Quality Flag w_qual ISSUE 10 REVISION 3
Weighted Quality Flag w_qual

The w_qual flag can only be applied to quality related averaging mechanisms when the
weighted averaging algorithm (number 1) is being used. As can be clearly seen on the
opposite page the weighting algorithm causes the most recent reported averages to be
repeated a number of times, as per the weighting factor, before an average is calculated
by the averaging mechanism.
The weighted algorithm will only apply when the reported averages are full values i.e. not
sub (DTX).

ISSUE 10 REVISION 3 Weighted Quality Flag w_qual
W_QUAL
Hreqave= 3
Hreqt = 3
w_qual = 2
Actual reported Rxqual averages

480ms
3 2 2 1 2 2 3 2 1 1 1 1 0 0 1 1 2 3 3 4
Normal Weighting Re avg avg's 0.3 1.3 3.3
w_qual weighting 0, 0 1, 1 1, 1 2, 2 3, 3 3, 3 4 4
Re avg avg's 1.6 3 3.5
The latest measurement report average

is used twice (w_qual= 2) to give it more
influence in the outcome of the quality voting.

Interference Averaging ISSUE 10 REVISION 3
Interference Averaging
The DRCU/TCU will sample each idle timeslot for noise interference, these
measurements are taken for every TDMA frame in the SACCH multiframe. This leads to
104 samples for a TCH and 102 for a SDCCH. An unweighted overall average is
produced for every SACCH multiframe, this average is sent to the HDPC on the GPROC.
The HDPC will produce a rolling average using the INTAVE parameter specified in
add_cell, rather like Hreqave. Hreqt is also specified for this process and is set to one by
default, ie. one rolling average is produced every SACCH multiframe. From this average
the HDPC can catagorise the idle slot into one of the interferer bands specified in the
add_cell part of the database.

ISSUE 10 REVISION 3 Interference Averaging
S intave set in add_cell
S hreqt= 1 by default
Range 0 to 31
0 0 SACCH Multiframes
1 2
2 4
.
.
.
31 62 SACCH Multiframes
Default 8

Interference Averaging ISSUE 10 REVISION 3
RF Resource
Reporting
Idle slots within a cell are constantly monitored for interference by the Handover
Detection and power control process. The samples taken will be averaged using the
INTAVE parameter, and compared against the interferer band categories.
One such category for each idle slot is passed to the Cell Resource Manager using the
RF resource indication message. These messages are sent at the end of every
rf_res_ind_period. This time is measured in SACCH multiframes and is the range
1127.

ISSUE 10 REVISION 3 Interference Averaging
RF Resource Reporting
chg_element rf_res_ind_period<*><SITE No>
* 1-127 SACCH MULTIFRAMES

EGSM ISSUE 10 REVISION 3
EGSM
The BSS software is capable of supporting EGSM900 when the feature is purchased by
the customer. The extra band provided by this feature consists of 880 890 Mhz for
mobile transmit and 925 935 Mhz for BSS transmit.
Provided the frequency type has been specified as EGSM900 in the equip cab
command and the freq_types_allowed command enables EGSM in the BSS, all cells in
that cabinet can be configured as EGSM900 optional utilising EGSM900 as well. EGSM
frequencies can only be utilised if the correct Radio hardware is available.
When the CRM allocates a TCH for an EGSM mobile it shall proceed in such a way that
the search is between extended then primary band frequencies starting from best to
worst interference bands until a channel is found. To avoid blocking of primary mobiles,
an extended mobile using a primary resource can be forced to handover to an idle
extended band resource. This feature can be controlled by use of a database parameter:

For the handover to occur an idle extended channel with an interference band residing
above or meeting the threshold must exist
An idle mobile is notified of the frequencies active in the cell via the cell channel
description element in the system information messages. This element contains 16
available octets in which to encode the carrier frequencies in use. The number of
frequencies that is possible to encode in this element depends upon the frequency range
in use and if channel 0 is active. If EGSM frequencies are active 49 carriers may be
specified. If channel 0 is also active only 17 frequencies may be encoded.

ISSUE 10 REVISION 3 EGSM
EGSM
FREQ (MHZ) CHANNEL

959.8
124

935.2
1 BASE STATION TX
935
934.8

0
1023

925.2

975

914.8
124

MS TX
890.2
1
890 0

889.8
1023

880.2
975
chg_element egsm_handover_threshold <*><site> cell number= <cell id>
* 0: forced handovers are not allowed

1: interference band 0 allowed
2: interference band 1 and above allowed

Support of BCCH/SDCCH in GSM Extension Band ISSUE 10 REVISION 3
Support of BCCH/SDCCH in GSM Extension Band

Prior to GSR4 all control channels (including BCCH) must be set within the GSM900
band to ensure mobile compatibility. This feature allows the configuration of BCCH
carriers and the placement of SDCCH channels in the GSM900 extension band
(ARFCNs 9751023) dependant on an operator defined database parameter
egsm_bcch_sd. This impacts the operation of non-EGSM mobiles in that they may not
have service since they are not able to access the BCCH frequency and SDCCH
channels in the GSM900 extension band.
The operator is thus able to configure a standalone GSM extension band cell by
exclusively selecting GSM extension band frequencies from the EGSM band.
In addition, this feature allows hopping systems to support the EGSM frequency band
(PGSM + GSM extension bands).
In a dual band system (e.g. EGSM and DCS1800), hopping is only supported within the
bands but not between the bands (as per GSM specifications).

ISSUE 10 REVISION 3 Support of BCCH/SDCCH in GSM Extension Band
Support of BCCH/SDCCH in GSM Extension Band
chg_element egsm_bcch_sd <*><site><cell_desc>
* 0- Disallow BCCH and SDCCH in the

GSM900 extension band
1- Allow BCCH and SDCCH in the GSM900

extension band
(default= 0)

Support of BCCH/SDCCH in GSM Extension Band ISSUE 10 REVISION 3

Chapter 5
Path

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 5
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Path Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Path Statement 1.6.0.x Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
BER Monitoring Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
N Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Nailed Timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Nailing a Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Path Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Path Timeslot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
BSC BTS Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Allocation of Terrestrial Backing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
DYNET Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
shared_timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
dynet_tchs_reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
dynet_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Reserved Timeslot Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Neighbour Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 Path
Path
Objectives
On completion of this chapter the student will be able to:
S Understand all the parameters used within a Path database script.

Path Script Building ISSUE 10 REVISION 3
Path Script Building

The script chart shown opposite specifies the groups of parameters necessary to
populate a Path database script. The actual parameters can be examined more closely
by following the example script shown overleaf.

ISSUE 10 REVISION 3 Path Script Building
Path Script Building Chart


Path Script Building ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 Path Statement 1.6.0.x Script Files
Path Statement 1.6.0.x Script Files
# Path Script
# 1.6.0.0. (GSR 4)
# PATHS
# Path 0,Site 1
equip 0 path
1
0
30
1
10
# Path 1,Site 1
equip 0 path
1
1
20
3
00
01
2
00
01
1
30
# Path 0,Site 2
equip 0 path
2
0
30
1
10
30
2
01
# Path 1,Site 2
equip 0 path
2
1
20
3
00
01
2
00
# Path 0, Site 3

Path Statement 1.6.0.x Script Files ISSUE 10 REVISION 3
equip 0 path
3
0
20
3
00
# Path 1,Site 3
equip 0 path
3
1
30
1
10
30
2
01
00
3
01
# RSLs Site 1
equip 0 RSL
1
0
0
2500
3
7
equip 0 RSL
1
1
1
2500
3
7
# RSLs Site 2
equip 0 RSL
2
0
0
2500
3
7
equip 0 RSL
2
1
1
2500
3
7

# RSLs Site 3
equip 0 RSL
3
0
0
2500
3
7
equip 0 RSL
3
1
1
2500
3
7
# RTFs
# RTFs, Site 1
equip 1 RTF
FULL
BCCH
00
0
1
2 3 4 1 0 368 39
65
255 255 255 255 255 255 255 255
00000000
0
0
equip 1 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 0 368 39
55
255 255 255 255 255 255 255 255
00000000
0
0
0
equip 1 RTF
FULL
NON_BCCH
02
0
1
2 3 4 1 0 368 39
45
255 255 255 255 255 255 255 255
00000000
0

0
0
equip 1 RTF
FULL
NON_BCCH
03
0
1
2 3 4 1 0 368 39
35
255 255 255 255 255 255 255 255
00000000
0
0
0
equip 1 RTF
FULL
NON_BCCH
04
0
1
2 3 4 1 0 368 39
25
255 255 255 255 255 255 255 255
00000000
00
0
# RTFs Site 2
equip 2 RTF
FULL
BCCH
00
0
1
2 3 4 1 1 368 36
512
255 255 255 255 255 255 255 255
00000000
0
0
equip 2 RTF
BCCH
10
0
1
2 3 4 1 1 368 37
600
255 255 255 255 255 255 255 255
55555555
0
0

equip 2 RTF
FULL
BCCH
20
0
1
2 3 4 1 1 368 38
885
255 255 255 255 255 255 255 255
22222222
0
0
equip 2 RTF
FULL
NON_BCCH
21
0
1
2 3 4 1 1 368 38
716
255 255 255 255 255 255 255 255
22222222
0
0
0
# RTFs, Site 3
equip 3 RTF
FULL
BCCH
00
0
1
2 3 4 1 0 368 40
110
255 255 255 255 255 255 255 255
55555555
0
0
equip 3 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 0 368 40
115
255 255 255 255 255 255 255 255
00000000
0
0
0
# MMS Priorities
modify_value 1 mms_priority 250 mms 1 0


# Enable GCLK sync
# LINK PARAMETERS
modify_value all nbit 0 MMS
modify_value all ber_oos_mon_period 50 MMS
modify_value all ber_restore_mon_period 1800 MMS
# NEIGHBOUR DEFINITIONS
add_neighbor 2 3 4 1 1 368 36 2 3 4 1 1 368 37 internal
1

1

1


1

1

1

0
add_neighbor 2 3 4 1 0 368 39 2 3 4 1 0 368 41 external ba_sacch

pgsm
100
23
33
5
10

0
52
10
8

Link Parameters ISSUE 10 REVISION 3
Link Parameters
There are four link parameters which are normally set in the path script. Each of these
parameters uses the modify_value command.
BER Monitoring
Periods
The MSI/XCDR card monitors the Bit error rate of the incoming 2MB, the BER can be
determined using the fixed bits of the Frame Alignment Word and Frame Data Word.
The fixed Bits do not alter and therefore are ideal to calculate BER.
The ber_oos_mon_period is the period that an in-service MMS must exceed the set
BER rate before it is taken out of service. The BER rate is set in firmware at 10e3.
The ber_restore_mon_period is the amount of time an out of service MMS must
exceed the set BER rate before it can be put back in service. The location for both of
these periods can be set individually for each site but more usually is set to all to include
every site in the BSS.

ISSUE 10 REVISION 3 Link Parameters
BER Monitoring
TIMESLOT 0 STRUCTURE
FIXED BITS
1 2 3 4 5 6 7 8
CRC EVEN
CHECK 0 0 1 1 0 1 1 FRAMES
(FAW)
SYNC TOGGLE
ODD
I.U 1 REMOTE N BIT I.U SPARE SPARE SPARE FRAMES
ALARM (FDW)
1 2 3 4 5 6 7 8
FIXED BIT
I.U = International usage
modify_value<location>ber_oos_mon_period <*> MMS
* 1-60 seconds
Default 1
modify_value<location>ber_restore_mon_period<*> MMS
* integer (100mS periods)

* 1-18000
Default 6000

N Bit ISSUE 10 REVISION 3
N Bit
It is possible to set an extra remote alarm bit, the n bit. The bit which is used for this
purpose is bit 4 of the frame data word. The actual use of this bit is specified by the
customer but the bit must be enabled using the modify_value command. Again this bit
can be enabled for all sites using the all location index, although any in-service MMSs
will not use it until they are reset.

ISSUE 10 REVISION 3 N Bit
N Bit
TIMESLOT 0 STRUCTURE
SYNC REMOTE FDW

I.U N BIT I.U SPARE SPARE SPARE
TOGGLE ALARM
1 2 3 4 5 6 7 8
modify_value<location>nbit<*>MMS
* 0 disabled
1 enabled

Nailed Timeslots ISSUE 10 REVISION 3
Nailed Timeslots
The nailing of timeslots through a site is an enhancement of the Reserved Timeslots
feature. It enables third party non-GSM connections to be nailed through GSM nodes.
Nailing is the physical connection of one timeslot incoming to one timeslot outgoing this
cross-connect being provided by the switchcard at that site. The Reserved Timeslots
feature will work independently of Nailed Timeslots , it simply allows timeslots to be be
reserved and not used by the software to be configured as RTFs and RSLs slots.
The nailed timeslots feature allows the nailing of single or indeed a range of contiguous
MMS timeslots, it is also possible for slots to be nailed for the length of a specified path.
The nailing capability is supported at all site types, BSC, RXCDR and BTS.
When a timeslot is nailed it will be barred from use by the BSS, a timeslot can be nailed
from the unused or reserved states. The method of nailing a timeslot uses the
chg_ts_usage command, later prompts depend on the first field, operation. To nail
single or multiple timeslots the command will be as follows;
chg_ts_usage <operation> <site> <mms1_id_1> <mms1_id_2> <mms1_ts>
<mms2_id_1> <mms2_id_2> <mms2_ts> <ts_range>
The operation field will be set to nail. The nail option will nail specified incoming
timeslots to specified outgoing timeslots. These can be specified in multiples, provided
the timeslots are contiguous on both incoming and outgoing legs. The ts_range will
define the number of contiguous timeslots to be nailed.

ISSUE 10 REVISION 3 Nailed Timeslots
Nailed Timeslots
chg_ts_usage <operation> <site> <mms1_id_1> <mms1_id_2>

<mms1_ts> <mms2_id_1> <mms2_id_2> <mms2_ts> <ts_range>
Nailing a Single Timeslot

Port 0, Timeslot 5
MSI3
K B
S T
W S
13
MSI5
Port 1, Timeslot 14
chg_ts_usage NAIL 13 3 0 5 5 1 14 1
Nailing Multiple Timeslots
Port 0, Timeslot 5-7
MSI3
B
T
S
T
W S
13
MSI5
Port 1, Timeslot 14-16

chg_ts_usage NAIL 13 3 0 5 5 1 14 3

Nailing a Path ISSUE 10 REVISION 3
Nailing a Path
It is possible to nail single or multiple timeslots for the length of a path, for intermediate
BTSs the actual timeslots to be used will be decided by FM software but will always be
initially in the unused state.
The chg_ts_usage command is once again used to specify the necessary details in the
database:
chg_ts_usage <operation> <path_id_1> <path_id_2> <site_1> <mms1_id1>
<mms1_id2> <site_1_ts> <site_2><mms2_id1> <mms2_id2> <site_2_ts> <ts_range>
The operation field will be set to nail_path. The ts_range will define the number of
contiguous timeslots to be nailed through the path. An example of this command is
shown opposite. BTS 12 has one path, path 0. Timeslots 5, 6 and 7 incoming on MMS
2 0 on the BSC are nailed through path 0 of BTS 12 to MMS 3 1, timeslots 7, 8 and 9.
If an external switching equipment is used, as part of the aggregate a-bis feature, then
TS_SWITCH can be entered as an intermediate site ID in equip path. However, when
nailing a path, as shown here, nailing cannot involve a TS_SWITCH. Any attempt to nail
a path through a TS_SWITCH will be rejected.

ISSUE 10 REVISION 3 Nailing a Path
Nailing a Path


Path Failure ISSUE 10 REVISION 3
Path Failure
If a path carrying an RTF fails, then the RTF of course has no way of carrying traffic to
the BTS and hence to the cell. There are two ways to combat this problem:
1. Equip a secondary path for the RTF so that if the primary path fails, the RTF can
switch to a new path. This has a disadvantage in that two complete paths, with
timeslots set aside for the purpose, must be provided. So, two timeslots are
required on each path of each RTF, meaning that a number of timeslots are
unused in normal operation.
2. Use the RTF path fault containment feature, whereby no redundant path is
required. If the primary path fails, all calls supported by the RTF concerned are
forced to intra-cell handover to a different RTF. If no channels are available the
call is dropped. The failed RTF is no longer available for traffic, and so its air
interface timeslots are blocked to TCH use, although the carrier can still be used
for SDCCH and BCCH if applicable.
The choice of approach is made by the rtf_path_enable parameter at the BSC as shown
opposite.

ISSUE 10 REVISION 3 Path Failure
Path Failure
S chg_element rtf_path_enable <*> bsc
<*>= 0:
BSC
Secondary path
Primary path
(2 TS used) (2 TS used)
BTS
<*>= 1:
BSC
Primary path Primary path

for other RTF
in same cell (2 TS used)
BTS

Path Timeslot Allocation ISSUE 10 REVISION 3
Path Timeslot Allocation

When equipping RTFs and RSLs on a path between a BSC and a BTS, it is normal that
the RSL terminating at the site be allocated timeslot 1 and the associated RTFs allocated
to high numbered timeslots (31/30, 29/28 etc). The RSLs and RTFs for subsequent sites
are also allocated high numbered timeslots (27, 26/25, 24/23 etc). This is logical as, at
the BTS where the path is terminated, the RSL must be in timeslot 1 so that the BTS can
contact the BSC while still in ROM in order to obtain a code download. However, if the
BTS is of low capacity, for example 2 carriers, it will only need one timeslot for the RSL
and two for each carrier RTF, giving a total of five timeslots required and twenty-six
unused on an E1 link. Clearly this is inefficient and costly.
An alternative is to use switching equipment in the path between BSC and BTS, so that
several BTS sites can share the resources of the E1 link for most of the distance to the
BSC, before branching out from the switch close to the BTS sites.
To do this the usual timeslot allocation algorithm above must be modified so that the RSL
and RTF timeslots for each site occupy a contiguous block on the E1 link. This is
because link providers normally lease blocks of timeslots together. The modified
algorithm is activated by the ts_alloc_flag parameter.

ISSUE 10 REVISION 3 Path Timeslot Allocation
Path Timeslot Allocation
S


BSC BTS Dynamic Allocation ISSUE 10 REVISION 3
BSC BTS Dynamic Allocation

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 Kbps portion of a timeslot 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 Kbps terrestrial backing resources requires 16 Kbps switching at the
BTS site. M-Cell BTSs do not support 16 Kbps switching. InCell BTSs support 16 Kbps
when equipped with a KSW. In-building picocellular systems also support 16 Kbps.

ISSUE 10 REVISION 3 BSC BTS Dynamic Allocation
BSC BTS Dynamic Allocation Network Topologies


Allocation of
Terrestrial
Backing
Resources
This feature attempts to minimize the BTS interaction needed to allocate or free a
terrestrial backing resource. The terrestrial backing resources are initially a set of nailed
connections throughout a BTS network. When a resource is allocated to a BTS, that
BTS breaks its nailed connection. A connection to the TCH is made in place of the nailed
connection. When the resource is freed, the BTS re-establishes the nailed connection.
No change in connections is required at any other BTS in the BTS network.
The diagram opposite shows a resource allocated to BTS 2. BTS 2 connects the
resource to the TCH using one of the two possible paths to the BSC. BTS 2 changes the
connection if the path being used fails during the call. BTS 2 connects the unused path
to the A-bis idle tone.
Note:
The closed loop daisy chain has the potential to use the same resource in both portions
of the loop. For example, in the diagram opposite both BTS 1 and BTS 3 could be using
the same resource. BTS 1 could use the resource on the span between the BSC and
BTS 1. BTS 3 could use the resource on the span between the BSC and BTS 3. If
either span failed, one of the calls would no longer be able to use the resource.
This feature does not support the use of closed loop daisy chains for additional capacity
when all spans are available. This feature treats the closed loop nature of the closed
loop daisy chain as existing for purposes of redundancy. Such a design ensures that no
calls are dropped when a span becomes unavailable in a closed loop configuration. This
design also simplifies the tracking of terrestrial backing resources.

Allocation of Terrestrial Backing Resources


Call Handling
The existing functionality for call congestion handling, priority call handling, and
emergency call handling deals with the radio resources as dynamically allocatable
resources, but treats the terrestrial backhaul resources as statically allocated. Hence,
this functionality clashes with dynamic allocation of terrestrial backhaul resources. This
feature limits call congestion handling and priority call handling to radio resource
considerations. Failure to allocate terrestrial backhaul resources only affects emergency
calls. Non-emergency calls are lost if terrestrial backhaul resources cannot be allocated.
Emergency calls take precedence over non-emergency calls. If no terrestrial backhaul
resources are available when an emergency call requests a resource, an existing
non-emergency call is terminated to provide the resource needed.
In addition, emergency calls take precedence over reserve resources for specific cells.
Emergency calls use whatever free terrestrial backhaul resources become available first.
They then bump non-emergency calls in the same cell. They next bump non-emergency
calls on the same site. Finally, they bump non-emergency calls from other sites. If all
available terrestrial backhaul resources are in use by emergency calls or no terrestrial
backhaul resources are available, the new emergency call is lost.

Call Handling


DYNET Equipage ISSUE 10 REVISION 3
DYNET Equipage
The DYNET device represents a dynamic network of BTSs that share terrestrial backing
resources. This device can be equipped or unequipped, but may not be locked, unlocked
or shut down. The prompts for the DYNET device define the connectivity of spans
between the BSC and the network of BTSs.
First and Second Unique Dynet IDs

The primary unique identifier for the DYNET device defines different BTS networks (20
max)
The secondary identifier allows multiple spans (3 max) to be specified for a BTS network
and the number of terrestrial backing resources to be specified per span.
BSC MMS IDs

These are MSI card and port IDs at the BSC.
Site ID
This is the identity of the next BTS/timeslot switching site/BSC in the network. If a
timeslot switching site is entered, the upstream and downstream MMS prompts are
skipped as timeslot switching sites do not have MMS IDs that are known to the BSS. If a
BSC site is entered (i.e. in case of closed loop configuration) the command will terminate.
The number in a DYNET is limited to ten.
Upstream MMS IDs:

These are the MSI card and port IDs at the BTS site, facing upstream (towards the
BSC).
Downstream MMS IDs

These are the MSI card and port IDs at the BTS site, facing downstream (away from
BSC).
Notes:
1. At least one site within the DYNET definition must support dynamic allocation.
2. The ordering of sites must match between all DYNETs with the same first ID.
3. For each site specified in a DYNET, PATHs are automatically equipped for the
BTSs that support dynamic allocation.
4. The equip command does not prompt for the PATHs for an RTF when the RTF is
equipped to a dynamic allocation BTS. Additionally, no prompt for the associated
RSL occurs if 16 Kbps RSLs are chosen for a dynamic allocation BTS.
5. Sub-equipped RTFs are not allowed.

ISSUE 10 REVISION 3 DYNET Equipage
DYNET Equipage
equip 0/BSC DYNET
S enter first and second unique DYNET identifiers:(0-19) (0-2)
S enter BSC MMS identifiers: <card><port>

(0-50) (0-1)
S enter SITE identifier: <site ID>

(0-100, TS_SWITCH, BSC)
enter upstream MMS identifiers:<card><port>

S
(0-9) (0-1)*
S enter downstream MMS identifiers:<card><port>

(0-9) (0-1)*
(No entry to terminate prompts)
* Ranges differ for different products. Ranges given for

Incell BTS.

DYNET Equipage ISSUE 10 REVISION 3
DYNET Equipage
shared_timeslots
When a DYNET device is equipped, the number of pool timeslots reserved is set to
zero. This command is used to increase or decrease the number of timeslots that are
reserved for dynamic allocation within a BTS network.
Simply allowing capacity to move dynamically between BTSs could result in some BTSs
(or some cells in a BTS) receiving no terrestrial backing resources when all resources are
in use. This situation may not be desirable to the operator. To ensure that some capacity
exists for a given cell, terrestrial resources can be reserved on a per cell basis.
dynet_tchs_reser
ved
This element specifies the amount of backing resources that are reserved for a cell when
dynamic allocation is enabled for the site containing the cell. The reserve cell capacity
does not actually reserve terrestrial backing resources. Instead, terrestrial backing
resources are prevented from being allocated to a cell once that cell has exceeded its
reserved amount and insufficient resources exist for the unused reserved capacity for the
other cells in the network configuration.
This element cannot be changed such that its new value causes the total terrestrial
backing resources for a BTS network to be less than the total reserved cell capacity.
dynet_retry_time
This element specifies the time (in milliseconds) that the BTS waits for a response from
the BSC when requesting a terrestrial backing resource. The value should be set based
upon whether satellites are used to connect the BSC to BTS (satellites introduce a one
way delay of 600ms).

ISSUE 10 REVISION 3 DYNET Equipage
DYNET Equipage
modify_value 0/BSC shared_timeslots <*> DYNET <id1><id2>

(0-19)(0-2)
* Number of timeslots reserved for dynamic allocation (0-31)

(default= 0)
chg_element dynet_tchs_reserved <*><site> <cell ID>

(1-100)
* Number of reserved T CHs (0-32)

(default= 0)
chg_element dynet_retry_time <*><site>

(1-100)
* Retry time (in milliseconds) when BT S requests terrestrial

backing resource from BSC (150-3000mS)
(default= 1000mS)

Reserved Timeslot Examples ISSUE 10 REVISION 3
Reserved Timeslot Examples
Example 1
To illustrate the concept of reserved timeslots, consider a network that:
A. Contains two cells, A and B.
B. Has two span timeslots available for terrestrial backhaul resources.
C. Has the cell reserve capacity set at three TCHs for both of its cells.
Assume that cell A has five calls occuping TCHs and cell B has one occupying a TCH.
At this point, there are only sufficient terrestrial backhaul resources for two more TCHs.
Cell A has already reached its reserve cell capacity of three. Cell B requires two more
TCHs to reach its cell reserve capacity, this is the total number of terrestrial backhaul
resources left. Subsequently, if cell A requests a terrestrial backhaul resource, its
request is rejected due to the lack of capacity.
Example 2
The 16 Kbps RSL functionality is available to BTSs using dynamic allocation. However,
resources that share the timeslot with a 16 Kbps RSL are reserved for use by the 16
Kbps site and are the first terrestrial backing resources to be allocated to the site. These
resources may be allocated to the site even if insufficient resources remain for the
unused reserve capacity.

ISSUE 10 REVISION 3 Reserved Timeslot Examples
Reserved Timeslots examples
e.g. 1) SITE A/B 64 Kbps RSL e.g. 2) SITE B 16 Kbps RSL

disp_mms_ts_usage 0 0 0 disp_mms_ts_usage 0 0 0

TS 0
TS 0
1

RSL A

1 RSL A
BSC
2 A A B A shared_timeslots= 2 2 A A A A
DYNET MSI 0 DYNET
3 A A 0 1 3 A
.
.
.
.
.
.
.
.
.
. .
.
dynet_tchs_res= 3
RSL
31 RSL B 31 B
B
Site A
dynet_tchs_res= 3
Site B

Neighbour Definitions ISSUE 10 REVISION 3
Neighbour Definitions
The operator is able to select neighbours to be broadcast in the BCCH allocation both on
SACCH and the BCCH. Neighbours can be optionally broadcast in either or both lists.
The BA sent in System Information Message Type 2 on the BCCH is a list of BCCH
frequencies in use by a given PLMN in a given geographical area. It is used by the MS
in cell selection and reselection. The BA sent in System Information Message Type 5 on
SACCH indicates to the MS the BCCH frequencies to be monitored for Handover
purposes.
By maintaining two distinct BA lists, the operator is given the flexibility to vary the
frequencies the MS monitors in idle mode independent of the frequencies the MS
monitors as potential neighbours in active mode.
The operator can set up to a combined total of 64 neighbours in both lists. A GSM
restriction confines the operator to set a maximum of 32 neighbours in the BA_SACCH,
this is consistent with the number of neighbours a mobile is able to report. The
BA_BCCH may contain up to 64 distinct neighbours but only if all the frequencies
included in the BA_SACCH are included in the BA_BCCH.
Two types of neighbour can be defined in the neighbour list, internal or external. An
internal neighbour specifies a cell which is operational through the same BSC as the
server. An external neighbour specifies a cell which is controlled by a different BSC.

ISSUE 10 REVISION 3 Neighbour Definitions
Internal/External Neighbour


For every neighbour being added to the BA List the add_neighbor command must be
entered. The command is essentially prompt based after the first command line. The
add_neighbor command shown below does not incorporate the purchasable
microcellular feature. If this feature is purchased and activated the MMI process will
prompt for further information, these details are extensively covered in the SYS08 course
Microcellular Principles
add_neighbor <source> <target> <placement> [<list type>]
placement: One of internal or external, the further prompts will depend on the entry
made here.
list type: One of: ba_bcch
ba_sacch
both
this field is optional and if the operator fails to enter it, then both is the default.

S Enable synchronization:
0/1
S Enter the neighbor cell frequency type:

pgsm, egsm, dcs1800 or pcs1900
S Enter the BCCH frequency number:

1-124 GSM 900
512-885 DCS 1800
975-1023 EGSM
S Enter the base station identity code (bsic):
S Enter the MS transmit power maximum:

5-39 GSM900 (odd values only)
0-30 DCS (even values only)
S Enter neighbor receive level minimum:

0-63
S Enter neighbor handover margin:

-63 to +63dB
S Enter the power budget surrounding cell

hreqave:
1-32
Note: Other prompts appear as a result of purchasing

microcellular or directed retry.

Prompts
Enable synchronization:0/1 This parameter is only prompted when an internal
neighbour is being added to the ba_sacch. At present synchronised handovers can only
be performed between two cells using the same GCLK, i.e. at the same site. If the flag is
accidently set to 1 (synchronised), when the cells are external or simply not at the same
site the software will treat the handover as unsynchronised.
Enter the neighbour cell frequency type. This parameter is only prompted when the
placement is external. This parameter is important in a multiband environment where the
source and target cells could be of different frequency bands. Where multiband is
disabled, the value must be the same as the source cells freq_type parameter in
add_cell.
Enter the BCCH frequency number: Ranges include: 1124 GSM 900
512885 DCS 1800
This parameter is only prompted when the placement is external.
Enter the base station identity code (bsic): This parameter is only prompted when the
placement is external
Enter the MS transmit power maximum: Odd values only ranges include:
539 GSM 900 (odd values only)
030 DCS 1800 (even values only)
This parameter is only prompted when the placement is external. The value is used in
the power budget assessment process.
Enter neighbor receive level minimum: 063. This field sets the minimum rxlev that
must be exceeded for a neighbour cell to be considered as a possible handover target
cell. This value usually corresponds to rxlev_acces_min. This parameter is optional for
internal neighbours and mandatory for external neighbours.
Enter neighbor handover margin: 63 to +63 dB Sets the level by which the target
cell must exceed the serving cell in order to allow a power budget handover to take
place. This parameter is optional for internal neighbours and mandatory for external
neighbours.
Surrounding cell hreqave: The averaging parameter for the neighbour rxlev part of the
power budget formula detailed in section 3 and 4.

S Enable synchronization:
0/1
S Enter the neighbor cell frequency type:

pgsm, egsm, dcs1800 or pcs1900
S Enter the BCCH frequency number:

1-124 GSM 900
512-885 DCS 1800
S Enter the Base Station Identity Code (BSIC):
S Enter the MS transmit power maximum:

5-39 GSM900 (odd values only)
0-30 DCS (even values only)
S Enter neighbor receive level minimum:

0-63
S Enter neighbor handover margin:

-63 to +63dB
S Enter the power budget surrounding cell

hreqave:
1-32
Note: Other prompts appear as a result of purchasing
microcellular or directed retry.


Chapter 6
Hopping Script

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 6
Hopping Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Hopping Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Baseband Hopping Script GSR4 Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Base Band Hopping (BBH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Frequency Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Hopping Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Frequency Hopping Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Baseband Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Frequency Redefinition Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Channel Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Invoking hopping configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Cell frequency hopping view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Frequency Hopping Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Frequency Hopping support via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Changing mobile allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 Hopping Script
Hopping Script
Objectives
S Correctly build a Baseband and Fast Tune hopping script.

Baseband Hopping Script GSR4 Script Files ISSUE 10 REVISION 3
Baseband Hopping Script GSR4 Script Files

# 1.6.0.x. (GSR 4) Script Files.
# sample Baseband Hopping Script, 5 carriers, hopping through the
BCCH
# This script has been amended from a working one to remove excess
# repetition for the student
chg_element hopping_support 2 0 cell_number=4 2 7 0 1 10101 10101
chg_element hopping_systems_enabled,0 1 0 cell_number=4 2 7 0 1 10101 10101
chg_element hopping_systems_hsn,0 0 0 cell_number=4 2 7 0 1 10101 10101
chg_hopping 4 2 7 0 1 10101 10101 0 3 15 27 39 51
chg_hopping 4 2 7 0 1 10101 10101 1 15 27 39 51

Implementing Frequency Hopping
ISSUE 10 REVISION 3
EMOTOROLA LTD. 2000
Frequency Separation
0 0 0 0 0 0
Never Hops
1 1 1 1 1 1
Never Hops 2 ccch 2 2 2 2 2

3 3 3 3 3 3
4 4 4 4 4 4 Time
separation
5 5 5 5 5 5
Baseband Hopping Script GSR4 Script Files

6 6 6 6 6 6
7 7 7 7 7 7
CellA-BCCH CellA-C1 CellA-C2 CellA-C3 CellA-C4 CellA-C5
Sysgen Off
When this is typed at the RAM MMI prompt the system will put a notional call in each timeslot
through all the hopping systems. Any occurrences of an illegal combination (for example the same
requency in the same timeslot at the same time) will be displayed, this includes BCCH violation.
63
Frequency Hopping ISSUE 10 REVISION 3
Frequency Hopping
The frequency hopping feature may be supported by a cell to help overcome the effect of
multi-path fading. Frequency hopping can be implemented by two means:
Synthesiser
Frequency
Hopping
Fast tune synthesiser frequency hopping uses the DRCUs frequency agility in that it is
able to change RF channels on a timeslot basis. The DRCU contains 2 pairs of
frequency synthesisers, one pair being active during odd timeslots and the other pair
during even timeslots. Whilst one pair is active the other is retuning to the next transmit
and receive frequency (can be retuned in approximately 64 mS) and then the synthesiser
pairs can be switched ready for the next timeslot.
The transmit and receive frequencies are duplex pairs on 45 MHz spacing but must work
independently due to GSM timing. As a result of the dynamic nature of the transmit
frequency, broad band hybrid combining of the transmitter is necessary. The combining
losses associated with this technique must be tolerable. A mobiles call will remain on
the same RCU using this technique which may be used on cell where only a few RCUs
are used.
Base Band
Hopping (BBH)
If there are a large number of RCUs to be combined the losses associated with hybrid
combining may become unacceptable and an alternative method must be used. Whilst
BBH the RCU transmit frequencies do not change and therefore remote tune cavity
combining can be used. BBH is accomplished by routing the traffic data to different
RCUs on fixed carrier therefore the number of frequencies of which a mobile can hop is
the same as the number of RCUs.
Note:
Both systems allow 217 hops a second over a maximum of 64 frequencies for each
timeslot.

ISSUE 10 REVISION 3 Frequency Hopping
Fast Tune Frequency Hopping

Base Band Frequency Hopping


Frequency Hopping Parameters ISSUE 10 REVISION 3
Frequency Hopping Parameters

A number of parameters control frequency hopping at a particular site, before using
these parameters a number of rules need to be adhered to:
1. Only one hopping system may contain the BCCH frequency.

2. Timeslot 0 of the BCCH carrier cannot hop.
3. Any timeslot configured as a CCCH cannot hop
4. Both synthesised and base band hopping can be conducted through the BCCH
frequency.
5. If synthesised hopping is conducted through the BCCH frequency the DRCU
transmitting the BCCH cannot handle traffic.
6. If synthesised hopping is not conducted through the BCCH carrier the BCCH
DRCU can still handle traffic but the timeslots will not be hopped.
7. If BBH is conducted through the BCCH frequency the DRCU transmitting the
BCCH frequency can handle a maximum of 7 TCH (ie 2 DRCUs gives 15 TCH).
Timeslot 0 on the other DRCUs in the cell must use a different Hopping system not
using the BCCH frequency.
8. If BBH is not conducted through the BCCH frequency, the DRCU transmitting the
BCCH frequency can handle upto 7 traffic channels, but these channels will not
hop.
Parameters
chg_element hopping support

This command determines if hopping is enabled at a site and what type of hopping is to
be used.

ISSUE 10 REVISION 3 Frequency Hopping Parameters
chg_element hopping_support <*><SITE No><Cell No>
* 0= No Hopping
1= Synthesiser Hopping
2= Baseband Hopping
Note: This field must be consistent in each cell at a site,

as hopping is enabled within a cell.

Hopping Systems ISSUE 10 REVISION 3
Hopping Systems
A number of hopping systems may be specified for each cell, and they are assigned on a
per slot basis when equippng an RTF. Each hopping system may consist of various
frequencies and different Hopping Sequence numbers (HSN).
chg_element hopping_systems_enabled
This field specifies whether a hopping system is active (enabled) or not.
chg_element hopping_system_hsn
This field selects the hopping sequence number to be used by each system. Cyclic
hopping causes the MS to hop from low to high frequencies in a repeated pattern.
chg_hopping
This field specifies the mobile allocation list for each hopping system.
A least two frequencies must be specified upto a maximum of 64. Frequency ranges as
follows:
GSM 900 0124
GSM 900 extended 0124, 9751023
DCS 1800 512885
PCS 2000 512710

ISSUE 10 REVISION 3 Hopping Systems
hopping_systems_enabled,<FHI><*><SITE ID>cell_number=<cell id>
* 0- disabled
1- enabled
FHI = 0-3
255 No Hopping
hopping_systems_hsn,<FHI><*><SITE ID><Cell No>
* HSN 0 Cyclic
1-63 Random Hopping
chg_hopping<Cell ID><FHI><*><*><*>
* frequencies T he ARFCNs of the frequencies

used in this cell for this FHI are
entered here. T he maximum
number allowed is 64.

Frequency Hopping Enhancements ISSUE 10 REVISION 3
Frequency Hopping Enhancements

The operability of frequency hopping is enhanced by the introduction of various new
parameters and commands, and by allowing changes to be made outside sysgen mode.
The frequency hopping used in a cell can now be modified via one command instead of
several, namely by using the chg_hop_params command. This command combines
the functionality of the hopping_support , hopping_systems_enabled and
hopping_systems_hsn parameters, and the chg_hopping command, enabling the
hopping parameters of several hopping systems to be changed in one command. Note
that the affected site(s) reset upon completion of this command.
Hopping verification is also performed after command completion.
Hopping support and enable FHI cannot be simultaneously changed to zero in the same
chg_hop_params command.
Note: The affected site(s) will be promted for reset upon completion of this command.
This is only mandatory if the BCCH frequency has been included in the mobile allocation.

ISSUE 10 REVISION 3 Frequency Hopping Enhancements
Changing a hopping system
chg_hop_params <site> [<cell_desc>]
S hopping systems (FHIs) to be modified: in cell <cell_desc> (return=

no change for this cell): <fhi1> . . . . .<fhin>
S hopping support: 0= no hopping

1= synthesizer
2= baseband
FHI <fhi1> status: 0= disable

FHI to be modifed
S
Repeat for each
1= enable
S Mobile allocation (ARFCNs) for FHI <fhi1>: <arfcn1>........<arfcnn>
S HSN for FHI <fhi1>: 0= cyclic

1-63= pseudorandom
S site reset?: <Y or N>

Frequency Redefinition ISSUE 10 REVISION 3
Frequency Redefinition
This feature implements the ETSI defined frequency redefinition procedure which
provides Mobile Stations, on a channel, the ability to dynamically modify the frequencies
and hopping sequences when hopping reconfiguration occurs.
At GSR3, a mobile station assigned to a channel affected by hopping reconfiguration is
handed over (INTRA-CELL) to an unaffected channel or dropped if there are no channels
available. At GSR4 with the frequency redefinition procedure enabled, the affected
mobiles and base stations are provided with the information describing the new hopping
system and the timing of the move to the new hopping system parameters. In this way,
the change to the new hopping system is co-ordinated between the MS and BTS,
allowing dynamic change with no impact to calls in progress.
This feature is an enhancement to the existing, optional, frequency hopping functionality
which can be enabled and disabled via the hopping_support database element.
The way this feature interacts with the system is dependant on whether synthesiser
frequency hopping or baseband frequency hopping is being used.
Synthesiser
Frequency
Hopping
In a synthesiser frequency hopping system, frequency redefinition will only occur when:
S Enabling a frequency hopping indicator
S Disabling a frequency hopping indicator
S Changing the hopping sequence number of an enabled frequency hopping
indicator.
S Changing the mobile allocation of an enabled frequency hopping indicator.

ISSUE 10 REVISION 3 Frequency Redefinition
Synthesiser Frequency Hopping

! ! !
!
S
S
S

Baseband Frequency Hopping ISSUE 10 REVISION 3
Baseband Frequency Hopping

In a baseband frequency hopping system, frequency redefinition will only occur when:
S A carrier with hopping timeslots transitions from the in-service state to the out of
service state.
S A carrier with hopping timeslots transitions the out of service state to the in-service
state.
S Enabling a frequency hopping indicator.
S Disabling a frequency hopping indicator.
S Changing the hopping sequence number of an enabled frequency hopping
indicator.
S No frequency redefinition occurs during timeslot state changes. A timeslot that is
taken out of service is barred for traffic use only.
Note:
At GSR4, the per site element hopping_ins_mode is no longer supported.
In baseband hopping systems, carriers always come in-service as hopping.

ISSUE 10 REVISION 3 Baseband Frequency Hopping
Baseband Frequency Hopping
" "

! " !
S !

S
S

hopping_ins_mode
supported at GSR4

Frequency Redefinition Message ISSUE 10 REVISION 3
Frequency Redefinition Message

With the implementation of the frequency redefinition feature, the BSS supports the
sending of the GSM TS 04.08 (Phase 2+) FREQUENCY REDEFINITION message to
the Mobile Station. All calls on a channel which is undergoing hopping reconfiguration
will be notified of the new hopping parameter changes via the FREQUENCY
REDEFINITION message. This message includes the new hopping parameters together
with a starting time indication.
Upon an error condition (MS gets MA containing ARFCNs that are not all in one band)
and the start time has NOT elapsed then the MS stays on the current channel and sends
the RR STATUS message back to the BSS. The RR STATUS message will contain the
cause value, (Frequency Not Implemented).
If the start time has elapsed then the MS aborts the radio connection and, if permitted,
attempts Call Re-establishment.

ISSUE 10 REVISION 3 Frequency Redefinition Message
Frequency Redefinition Message
FREQUENCY REDEFINITION
S Start time (TDMA Frame No.)
BTS
S Mobile Allocation (MA)
S Hopping Sequence No. (HSN)
MS
S MAIO
1. Upon error condition and start time not elapsed:
RR Status BTS
<cause>
MS stays on
current channel
2. Upon error condition and start time elapsed:
BTS
MS aborts radio
connection

Frequency Redefinition ISSUE 10 REVISION 3
Frequency Redefinition
Channel
Restrictions
Channels undergoing hopping reconfiguration are subject to a number of restrictions:
1. All calls on channels undergoing hopping reconfiguration cannot be handed over or
released as a result of the hopping reconfiguration procedure.
2. Any call attempting to establish on a SDCCH or TCH shall not be granted a
channel undergoing hopping reconfiguration. Calls attempting to establish are
queued (if queuing is enabled) or rejected if no channels (unaffected by the
hopping configuration) are available.
3. When reconfiguring the channel attributes during hopping reconfiguration, the BSS
shall initiate only one hopping reconfiguration at a time for a particular timeslot.
4. Channels undergoing hopping reconfiguration are made available for intra-cell
handovers which are initiated due to a carrier going out of service.
5. Hopping configuration takes 1020 seconds (approx) in In-Cell equipment and
milliseconds in M-Cell equipment

ISSUE 10 REVISION 3 Frequency Redefinition
Channel Restrictions

S Can handover or release calls due to the

reconfiguration process.
S Can be assigned to a call attempting to establish

(call queued or rejected if no channels are free).
S Do support multiple hopping reconfigurations

per timeslot.
S be assigned for intracell handovers due to

carrier going OOS.
S 10-20 seconds (InCell)

Milliseconds (MCell)

Frequency Hopping support via GUI ISSUE 10 REVISION 3
Frequency Hopping support via GUI
Feature
overview
Frequency hopping enables each timeslot to use a set of frequencies defined in one of
four frequency hopping systems. This feature simplifies the viewing and setting of the
frequencies in each of the hopping systems, and also provides a single GUI screen
giving a high level summary view of the frequency hopping configuraton for a cell.
Feature
description
This feature only affects the GUI process at the OMC. Two new forms have been
provided, the first enables the operator to set the mobile_allocation attribute of the
FreqHopSys object; the second enables the operator to view, in a single window, all the
frequency hopping information associated with all of the carriers in a cell.
The first form is activated by selecting FreqHopSys from the configuration management
window and selecting detailed view from the edit drop down menu. This presents the
operator with a separate form containing a list of avaliable Absolute Radio Frequency
Channel Numbers (ARFCNs) from which new values may be selected and old values
deselected when in edit mode.
The second form is invoked by selecting a cell on the OMC Navigation Tree and invoking
the appropriate menu option, it can also be invoked from a cell detailed view.
The operation of these two forms is described in the following sections:
Invoking hopping
configuration
view
Figure 1 shows a example of the hopping configuration window being invoked for a cell
from the OMC Navigation Tree. Figure 2 shows this option being invoked from a cell
detailed view.

ISSUE 10 REVISION 3 Frequency Hopping support via GUI
Invoking hopping configuration from Navigation Tree

Figure 1
Navigation Form
File Edit View Display LoadMgt Fault Mgt Config Mgt Options Help
Audit
Audit Logs ...
Sources and Neighbours ...

MSC Templates ...
Neighbour
Frequency Hopping...
OMC
Proxy Cells ...
EASRadio
Alarms...
Freq Cell 0010111
SITE1
Invoking hopping configuration from Navigation Tree

Figure 2
CELL BSS_City:SITE1: 1 CELL:0010111 <Monitor>
File Edit Find View Fault Mgt Options Help
Sources and Neighbors

Identification
Frequency Hopping
Name : 0010111
Propagate to SITE
Propagate to BSS
GSM Cell ID : 001 01 1 1 DEC
Propagate to Network
Navigation Tree ...

Base Station Identity Code (BSIC) : 23
Remote Login ...
Layer Type : Macro Layer (0)
RDN Class : RTF
RDN Instance : 0

Cell frequency
hopping view
The diagram opposite shows the frequency hopping configuration window. This is a
simple read-only window with no editable fields. Clicking on the RTF button invokes the
RTF detailed view. Similarly, clicking on any hopping system invokes the detailed view for
the corresponding frequency hopping object.

Cell frequency hopping view
BSS_City:SITE1: 1 CELL:0010111 < Frequency Hopping View >
File Help
Cell Name : 0010111 GSM Cell ID : 0010111 Hopping Support : Synthesizer Hopping
Hopping System Enabled HSN Mobile Allocation
FreqHopSys 0 True 0 17 23 25 29 35 37 39
FreqHopSys 1 True 0 17 24 26 28 30 32 33 34 36
FreqHopSys 2 True 0 94 95 96
FreqHopSys 3 False 0
Frequency Hopping Indicators for Timeslots
RTF Carrier Type ARFCN TS 0 TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7
RTF 0 0 BCCH (0) 33 None 1 1 1 1 1 1 1
RTF 0 1 NONBCCH (1) 17 0 1 1 1 1 1 1 1
RTF 0 0 NONBCCH (1) 27 None None None None None None None None
RTF 0 1 NONBCCH (1) 47 None None None None None None None None

Frequency Hopping Exercise ISSUE 10 REVISION 3
Frequency Hopping Exercise

Contained on the student disc is a file named hopping.stu, this file contains a working
standalone BSS script. Alter this script in order to implement fast tune frequency
hopping as per the details shown opposite.

ISSUE 10 REVISION 3 Frequency Hopping Exercise
Frequency Hopping Exercise
BCCH CARRIER NON BCCH RTF NON BCCH RTF

f= 98 f= 95 f= 83
S Fast tune frequency hopping: Not through the BCCH

carrier.
S Cyclic hopping is to be used throughout.
S Frequencies to be used: 10, 32, 63, 78, 83, 95.

Frequency Hopping support via GUI
Changing mobile
allocation
The frequency hopping system detailed view has an additional menu option which is
used to edit the mobile_allocation attribute. This menu option is shown in the diagram
opposite. Selecting this menu option presents a list of the allowed set of ARFCN values
as shown in the diagram on page .

Changing mobile allocation attribute from FreqHopSys

detailed view
FreqHopSys BSS_lab1:SITE1: 1 FreqHopSys 0010111 1 <Monitor>
File Edit Find View Options Help
Monitor
Edit Identification
Mobile Allocation RDN Class : FreqHopSys
RDN Instance : 1
NMC RDN Instance :
Parent Detail View : 0010111
Additional Information
Additional Information :
General
Hopping Systems Enabled : True
Hopping Sequence Number: 0
Mobile Allocation
ARFCN values 0 to 3 : 1 5 8 11
ARFCN values 4 to 7 : 24 29 31 45
ARFCN values 8 to 11: 67 69
ARFCN values 12 to 15 :
ARFCN values 24 to 27:

Changing mobile
allocation
The diagram opposite shows the mobile allocation selector form. This form enables the
operator to select new frequencies for the mobile allocation attribute by clicking on the
appropriate value. Frequencies already selected may be removed by clicking on them a
second time. Once the required frequencies have been selected, clicking on the OK
button transfers these values to the original frequency hopping system detailed view, in
ascending order. The operator then clicks on the Save button to set the value of the
mobile allocation attribute at the remote BSS.
The mobile allocation selector form is shown with values appropriate for a GSM900 cell.
If the cell in question was at a DCS1800 site, then the values presented would be in the
range 512 to 885. Similarly, if the cell supported PCS1900, then the range presented
would be in the range 512 to 810, based on the individual bit settings of the
BSS:pcs_freq_blocks attribute as follows:
Bit 0 : channels 512 to 585 (Frequency Block A)
Bit 1 : channels 587 to 610 (Frequency Block D)
Bit 2 : channels 612 to 685 (Frequency Block B)
Bit 3 : channels 687 to 710 (Frequency Block E)
Bit 4 : channels 712 to 735 (Frequency Block F)
Bit 5 : channels 737 to 810 (Frequency Block C)
If the GSM900 extended range of frequencies is being presented (0 to 124 and 975 to
1023), then it is not possible to select frequencies from both the normal GSM900 range
(1 to 124) and the extended GSM900 range (0, 975 to 1023) at the same time unless the
cell::egsm.bcch.sd attribute is enabled.

Mobile allocation selector form
BSS_lab1:SITE1: 1 FreqHopSys 0010111 0 <Mobile Allocation Selector>
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 31 32 33 34 35 36 37 38 39
40 41 42 43 44 45 46 47 48 49
50 51 52 53 54 55 56 57 58 59
60 61 62 63 64 65 66 67 68 69
70 71 72 73 74 75 76 77 78 79
80 81 82 83 84 85 86 87 88 89
90 91 92 93 94 95 96 97 98 99
100 101 102 103 104 105 106 107 108 109
110 111 112 113 114 115 116 117 118 119
120 121 122 123 124
OK Cancel Help


Chapter 7
Database Building Exercise

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Chapter 7
Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Practical Database Building Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Remote Transcoder Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
LAPD Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
DSP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Traffic Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
BSC Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
BTS Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Geographical Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
SMS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
CRM Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
BTS Site 1 Specific (In-Cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Equipment Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Mains Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Rapid Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Cell Specific Information (Cell 39) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Averaging Algorithm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Intave Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Quality Flags Uplink and Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
BTS Site 2 Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Cell Broadcast SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
GSM Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Cell Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
BTS Site 3 Specific (micro-cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Cell Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
Path Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

ISSUE 10 REVISION 3

ISSUE 10 REVISION 3 Database Building Exercise
Database Building Exercise
Objectives
S Write a database for a complete BSS including three BTS sites in a closed loop.

Practical Database Building Exercise ISSUE 10 REVISION 3
Practical Database Building Exercise

This exercise will test the students knowledge and understanding of the first and present
database courses. The exercise itself centres around the GSM entities of a mini training
network.
To complete the exercise use a PC and write the scripts using DOS EDIT. You will be
supplied with a disc containing files where each script is to be built. These files will have
the extension .STU and within each file are timer values and MMS thresholds to help
quicken the script writing process.
An answer script for each GSM entity is available from your instructor, it is advisable to
check your answers before moving onto the next script.

ISSUE 10 REVISION 3 Practical Database Building Exercise
Network Connectivity


Remote Transcoder Script ISSUE 10 REVISION 3
Remote Transcoder Script

The first task in this database building exercise is to produce a transcoder script for this
mini network. The necessary terrestrial connectivity needed to complete this part of the
exercise is shown over the next few pages. The Remote Transcoder is connected to an
MSC and 2 BSCs, numbered 1 & 2.
Only one cage is present at the RXCDR, it is fitted into a BSSC cabinet (DAB), its layout
is specified in the diagrams that follow, use this when equipping the necessary devices.
All devices have to be equipped, numbering should follow the normal Motorola
convention using the shelf map.

ISSUE 10 REVISION 3 Remote Transcoder Script
Remote Transcoder Connectivity



BSC 1 Terrestrial Connectivity



BSC 2 Terrestrial Connectivity


LAPD Timers
Use the following LAPD timers for the XBLs.
T200 Timer: 2500 mS
N200: 3
K: 7
DSP Options
Downlink DTX may be in use by each BSS connected to this RXCDR. The MSC will
employ a quietone of 84.
Traffic Circuits
Traffic slots shall be allocated using the convention discussed in Section 1.
GCLK
Synchronisation
Enable GCLK synchronisation to the MSC. MMS 23 0 should be set to the highest
priority, MMS 22 0 and MMS 21 0 should be equal but lower than MMS 23 0. The
system should wait up to 4 minutes on a span that has gone OOS before reselecting to
another synchronisation source. The delimiting time for the OOS counter should be set
to 24 hours. The lta alarm range should be set to 10.

RXU Shelf Layout
AI0 KS0 KS1

AI1 MS0 MS1 MS2 MS3
AI2

EXP KSWX B0
EXP KSWX B1
CLKX A0 EXP KSWX B2
KSWX B0
KSWX B1
KSWX B2
KSWX B3
KSWX B4
LCL KSWX A
LCL KSWX B
KSWX A4
KSWX A3
KSWX A2
KSWX A1
KSWX A0
KSWX A2
KSWX A1
KSWX A0

LANX B
LANX A
BBBX
BBBX
PIX 0
PIX 1

CLKX A1 RMT
CLKX A2 RMT
CLKX B0 RMT
CLKX B1 RMT
CLKX B2 RMT

EXP
EXP
EXP
RMT
RMT
RMT
RMT
RMT

U0

U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1

MSI 0
MSI 1
MSI 2
MSI 3
MSI 4

GPROC 1
GPROC 0
XCDR 10
XCDR 11
XCDR 12
XCDR 13
XCDR 14
XCDR 15
XCDR 16
XCDR 17
XCDR 18
GCLK B
GCLK A
XCDR 0
XCDR 1
XCDR 2
XCDR 3
XCDR 4
XCDR 5
XCDR 6
XCDR 7
XCDR 8
XCDR 9
KSW B
KSW A
BT C 0
BT C 1
L28

L27 L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5 L3 L1 L0


BSC Script ISSUE 10 REVISION 3
BSC Script
The second task in this exercise is to produce a BSC script, for BSC 1 only. The
terrestrial connectivity necessary to complete this exercise is shown opposite. The BSC
is connected to two BTS chains, one is a closed loop the other is open.
The BSC comprises of one digital shelf fitted into a BSSC_DAB cabinet, its layout is
included overleaf, all boards need equipping using conventional numbering. One BSP
and one CSFP need to be equipped, the remainder of the GRPOCs being LCFs.
Traffic circuits should be equipped using the convention discussed in Section 1. The
statistics interval should be set to 60 minutes.
External Alarm Service

Six possible alarm strings are required for this BSS, the index number, severity and
appropriate text string are entered below.

1 Major High T emperature
2 Major Low T emperature
3 Major Door Intruder Alarm
4 Major Burglar alarm
5 Major Window Intruder Alarm
LAPD Timers
Similar LAPD timers should be used to those specified in the RXCDR script.
Encryption
All three available encryption algorithms have been loaded, their priority for use should
be A5/1, A5/2 then A5/0.

This feature should be enabled.
Point to Point SMS

Point to Point SMS should be enabled for this BSS.
GCLK synchronisation should be enabled. As far as necessary, parameters should be
set to the same values as the RXCDR.
Cell Broadcast Link

The operator names for the CBL should be:
BSS Operator : Sys03test
CBC Operator : CBCtest
The CBL should be processed by LCF 2 O O.

ISSUE 10 REVISION 3 BSC Script
BSC Terrestrial Connectivity



BSU Shelf Layout BSC 1
EXP KSWX B0
EXP KSWX B1
CLKX A0 EXP KSWX B2
KSWX B0
KSWX B1
KSWX B2
KSWX B3
KSWX B4
LCL KSWX A
LCL KSWX B

KSWX A4
KSWX A3
KSWX A2
KSWX A1
KSWX A0
KSWX A2
KSWX A1
KSWX A0
BBBX PIX2
BBBX PIX1
LANX B
LANX A
DRIX 4
DRIX 3
DRIX 2
DRIX 1
DRIX 0

DRIX5
PIX 0
CLKX A1 RMT
CLKX A2 RMT
CLKX B0 RMT
CLKX B1 RMT
CLKX B2 RMT

EXP
EXP
EXP
RMT
RMT
RMT
RMT
RMT

U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1 U0

MSI 10
MSI 11
MSI 0
MSI 1
MSI 2
MSI 3
MSI 4
MSI 5
MSI 6
MSI 7
MSI 8
MSI 9

GPROC 7
GPROC 6
GPROC 5
GPROC 4
GPROC 3
GPROC 2
GPROC 1
GPROC 0
KSW/T SW B
KSW/T SW A
XCDR 10
XCDR 11
GCLK B
GCLK A
XCDR 3
XCDR 4
XCDR 5
XCDR 6
XCDR 7
XCDR 8
XCDR 9
XCDR 0
XCDR 1
XCDR 2
spare
BT C 0
BT C 1

DRI(M) 5
DRI(M) 4
DRI(M) 3
DRI(M) 2
DRI(M) 1
DRI(M) 0
L28

L27

L26 L25

L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5 L3 L1 L0



RSL/MTL & Processor Distribution


BTS Scripts ISSUE 10 REVISION 3
BTS Scripts
The third task in this exercise is to produce a number of BTS scripts one each for sites
1, 2 and 3. The scripts for BTS sites 4, 5 and 6 do not have to be written. General
information concerning all sites is shown in the next couple of pages. Site specific
information follows. The terrestrial connectivity for these sites is shown opposite. To be
consistent with the earlier sections of this exercise all fitted cards & equipment should be
equipped.
The sample copy of add_cell found in each BTS student file was populated with typical
values which may be used for each cell in the BSS, however be aware that some
alterations on a cell basis will be necessary.

ISSUE 10 REVISION 3 BTS Scripts
BTS Terrestrial Connectivity Chain 1


BTS Scripts ISSUE 10 REVISION 3
Geographical
Location
A geographical map showing the cell identities and BCCH frequency information is
shown opposite.
SMS Options
Short message service for both uplink and downlink data transfers shall be allowed in all
cells, when an MS is already engaged in traffic the SMS will use the SACCH.
CRM Flow
Control
CRM flow control shall be implemented for this BSS. If 85% of traffic channels are in use
when an assignment resource request is received from the SSM, then the CRM shall
randomly bar 1 access class. If 95% of traffic channels are in use when an assignment
resource request is received from the SSM the CRM shall randomly bar two access
classes if any access classes are still unbarred.
GCLK
Synchronisation
GCLK synchronisation should be enabled throughout the BSS. The clock sources should
conform to the following diagram

As far as necessary, parameter values should follow that of the transcoder. BTS3 shall
prioritise the direct BSC link as higher than the BTS2 link.

ISSUE 10 REVISION 3 BTS Scripts
Cell Geographical Map
ROAMING IN
OPERATION
NCC= 6
External
Neighbour
GSM900 PLMN Details

MCC= 234 SITE 1
MNC= 11
LAC= 368 Cell 39
NCC= 3 BCCH= 65
BCC= 0
BCCH= 70
BCC= 7
BCCH= 80
BCC= 2 Cell 36
Cell 38
SITE 2
Cell 37
SITE 3 BCCH= 75
BCC= 5
Cell 40
BCCH= 600
BCC= 5
DCS1800 PLMN Details
MCC= 234
MNC= 10
LAC= 368
NCC= 2
INTERNATIONAL BORDER

BTS Site 1 Specific (In-Cell) ISSUE 10 REVISION 3
BTS Site 1 Specific (In-Cell)
Equipment
Shelves
The BTS cabinet being used is a BTS 5. The BSU shelf layout and RF cage diagram
should provide enough information to equip all the necessary devices.
External Alarm
System
As can be noted from the shelf layout a pix card has been fitted, the physically equipped
sensors and their inputs are shown below.

1 High T emperature 1
2 Low T emperature 1
3 Door Intruder 1
4 Burglar Alarm 0
8 Mains Failure 0
All alarms must be reported, there are no relay outputs at this site.
Mains Failure
In the event of mains failure a back up supply is available, two carriers should always be
left in use and five minutes should elapse before the first and subsequent carriers are
removed from service.
Rapid Power
Down
Rapid power down is enabled in this cell. The trigger is -65 db and the offset is -12 dbm.
The power down should happen within 2 SACCH multiframes.

ISSUE 10 REVISION 3 BTS Site 1 Specific (In-Cell)

Cell Specific
Information (Cell
39)
S Timeslot 0 and 2 of the BCCH carrier configured as 9 CCCH,1 x AGCH
8 x PGCH
S Number of SDCCHs preferred should be 8, with a maximum of 32.
S Channel Reconfiguration is allowed.
S SDCCH high water mark= 2

SDCCH low water mark= 12
S Reconfiguration, TCH SD should only occur when there are 6 or more free
TCHs.
S Extended paging should be made active.
S There should be 3 multiframes between successive paging groups.
S A downlink transmission failure should be declared by the MS after approximately

6 seconds.
S This PLMN operator has a roaming agreement with a network operator in the
adjoining country.
S The N and P voting mechanism for power control and handover due to level should
be set at P=75% of N where N= hreqt.
S The N and P voting mechanism for all quality related decisions including level for
interference handovers should be set at P=100% of N where N=hreqt. The N and
P values for maximum range should be set at P=50% of N where N=hreqt.
Cell Broadcast
Two background messages should be broadcasted:
1st message MOTOROLA GSM
2nd message FREE CALLS TODAY
The language id should be set to English. The message id should be 200 for both
messages, message codes being 1022 and 1023.


Averaging
Algorithm
Configuration
Averaging Process HREQAVE HREQT

Neighbour cells 8 1
Timing advance 4 2
RXLEV Downlink ho/pc 8 4
RXLEV Uplink ho/pc 8 4
RXQUAL Downlink ho/pc 2 2
RXQUAL Uplink ho/pc 2 2
Intave Parameter
INTAVE HREQT
Interference Average 10 1
S The RF resource indication messages should be sent every 9.6 seconds.
Quality Flags
Uplink and
Downlink
S Quality handovers are permitted regardless of the MS or BS being fully powered
up.

BSU Shelf Layout BTS 1

EXP KSWX B0
EXP KSWX B1
CLKX A0 EXP KSWX B2
KSWX B0
KSWX B1
KSWX B2
KSWX B3
KSWX B4

LCL KSWX A
LCL KSWX B
KSWX A4
KSWX A3
KSWX A2
KSWX A1
KSWX A0
KSWX A2
KSWX A1
KSWX A0

LANX B
LANX A
DRIX 4
DRIX 3
DRIX 2
DRIX 1
DRIX 0
BBBX
BBBX
PIX 0
PIX 1
CLKX A1 RMT
CLKX A2 RMT
CLKX B0 RMT
CLKX B1 RMT
CLKX B2 RMT

EXP
EXP
EXP

RMT
RMT
RMT
RMT
RMT

U28

U27 U26 U25 U24

U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1 U0

MSI 10
MSI 11
MSI 0
MSI 1
MSI 2
MSI 3
MSI 4
MSI 5
MSI 6
MSI 7
MSI 8
MSI 9

GPROC 7
GPROC 6
GPROC 5
GPROC 4
GPROC 3
GPROC 2
GPROC 1
GPROC 0
KSW/T SW B
KSw/T SW A
XCDR 10
XCDR 11

GCLK B
GCLK A
XCDR 3
XCDR 4
XCDR 5
XCDR 6
XCDR 7
XCDR 8
XCDR 9
XCDR 0
XCDR 1
XCDR 2
spare
BT C 0
BT C 1

DRI(M) 5
DRI(M) 4
DRI(M) 3
DRI(M) 2
DRI(M) 1
DRI(M) 0

L28

L27

L26 L25

L24 L23 L22
L21
L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5 L3 L1 L0



RF Shelf Layout BTS 1
ANTENNA
RTC Combining
BPF
CAV 3 CAV 1
CAV 4 CAV 2 CAV 0 COMB.ID=0

COMB.ADD=255
TX O/P TX O/P TX O/P TX O/P TX O/P
C25 C35 C45 C55 C65

SECONDARY PRIMARY
CONTROL CONTROL
OF RTC OF RTC
RXI/P RXI/P RXI/P RXI/P RXI/P
Receiver
Front
PRESELECTOR PRESELECTOR End
ANTENNA

BTS Site 2 Specific ISSUE 10 REVISION 3
BTS Site 2 Specific
M-Cell6
This site is using a GSM900 M-Cell6 cabinet.
External Alarm
System
It can be noted from the shelf layout a PIX card has been fitted, the physically equipped
sensors and their inputs are shown below.

1 High T emperature 1
2 Low T emperature 1
3 Burglar Alarm 0
All alarms must be reported, there are no relay outputs at this site.
Cell Broadcast
SMS
No background messages should be broadcast.
GSM Frequency
BTS2 is a GSM900 site.

ISSUE 10 REVISION 3 BTS Site 2 Specific

Cell Specific Information ISSUE 10 REVISION 3
Cell Specific Information

Cells 36 and 37
S Timeslots 0 of the BCCH carrier is to be configured as a combined timeslot.
S Number of SDCCHs upon initialisation should be 4, with a maximum of 12.
S Channel reconfiguration is allowed
S SDCCH high water mark=1
S Reconfiguration, TCH SD, should only occur when there are 3 or more free
TCHs.
S A downlink transmission failure should be declared by MS after approximately 12
seconds.
S The N and P voting mechanism for power control and handover due to level should
equal P=75% of N where N= hreqt.
The N and P voting mechanism for all quality related decisions including level for
interference handovers should equal P=100% of N where N=hreqt. The N and P
values for maximum range should be P=50% of N where N=hreqt.
Cell 38
S Timeslot 0 of the BCCH carrier is to be configured as a combined timeslot.
S Channel reconfiguration is allowed
S SDCCH high water mark= 2
TCHs.
S A downlink transmission failure should be declared by the mobile after
approximately 12 seconds.
S The N & P voting mechanism for each criteria shall be configured in the same way
as cell 36 & 37

ISSUE 10 REVISION 3 Cell Specific Information

Averaging Algorithm Configuration (Cell 36, 37 & 38)

These parameters should be set the same as cell 39.
Interference Averaging (Cell 36, 37 & 38)

These parameter should be set the same as cell 39.
Quality Flags Uplink and Downlink (Cell 36, 37 & 38)

S Quality handovers are permitted regardless of the MS or BS being fully powered
up.
S The ad_qual_margin should be set to 6.

BTS2 M-Cell6 Frame 0



RF Shelf Layout BTS 2
Cell 38 Cell 37 Cell 36

RxAnt 1 RxAnt 2 RxAnt 3
IADU
T T T T
C C C C
U U U U
C80 C75 C70

FREQ - C85 (Redundancy (Redundancy (Redundancy
Group 2) Group 1) Group 0)
0 1 2 3
FOX
Note: The Tx path of Cell 38 is using a hybrid combiners.
IADU - Internal Antenna Distribution Unit

FOX - Fibre Optic extender

BTS Site 3 Specific (micro-cell) ISSUE 10 REVISION 3
BTS Site 3 Specific (micro-cell)

M-Cellarena
This site is using a DCS1800 M-Cellarena.
Cell Broadcast
No Cell Broadcast SMS should be activated in this cell.
Cell Specific
Information
Cell 40
S Timeslot 0 of the BCCH carrier should be configured as a combined timeslot.
S Channel configuration is allowed.
S SDCCH high watermark= 2
SDCCH low watermark= 12
TCHs.
S A downlink transmission failure should be declared by the mobile after
approximately 12 seconds.
S The N & P voting mechanism for each criteria shall be configured in the same way
as cell 38.
S Rapid power down is enabled and using default levels.
S ARFCN of non-BCCH carrier is 650.
Averaging Algorithm Configuration

These parameters should be set the same as cell 39
These parameters should be set the same as cell 39
Quality Flags Uplink and Downlink

These flags should be set the same as cell 39

ISSUE 10 REVISION 3 BTS Site 3 Specific (micro-cell)
BTS 3 M-Cellarena
/

' ' (+# && & /!! (( #' "#( ')$$#&(
'$ *&' (- )( #' ')$$#&( '-"(' .& &%)"-
#$$ " (# "! " ( ' ,& '

Path Script ISSUE 10 REVISION 3
Path Script
The last task in this exercise it to produce a path script for chain 1 incorporating BTS
sites 1, 2 and 3. Each site is to be equipped with two paths, each RTF can therefore be
equipped with a redundant path and the two RSLs at each site can be allocated separate
paths. In the case of site 2 the primary path for both RTFs and RSLs should be through
BTS1.
LAPD Timers
Two RSLs should be equipped to each site, their LAPD timers will be the same as the
XBL LAPD timers previously stated.
Link Parameters
The N-bit is not to be used. When the BER exceeds the threshold for a period of more
than 50 seconds the MMS should be taken out of service. The MMS should only be
restored if the BER threshold is exceeded for 3 minutes.
Hopping
Frequency Hopping is not in operation at any site.
Neighbor Definitions
To make the script comparable to the instructors answer script, start the neighbour
definitions from the lowest numbered cell and progress logically onwards. The handover
decision process shall use the add_cell default values in every case. The BA_SACCH
and BA_BCCH should contain the same neighbours. Note that site 3 is DCS1800, and
there are to be no handovers between this site and site 1 or 2.
External Neighbor (cell 39 to 41)

The external neighbor must be placed in the SYSINFO5 or Dedicated broadcast
allocation list. The ms_txpr_max for cell 41 is 2 w. The MS must perceive a minimum
downlink power of -105 dBm from cell 41 before criteria 1 will be satisfied. Use a
ho_margin of 10.

ISSUE 10 REVISION 3 Path Script
Neighbour Information
External Neighbor
Cell 234 11 368 41
ASYNC H/O ARFCN= 100
BSIC= 23
Cell 39
ASYNC H/O's
Cell 36
SYNC H/O
Cell 38
SYNC H/O
Cell 40 (DCS1800)
SYNC H/O
Cell 37

Path Script ISSUE 10 REVISION 3

ISSUE 10 REVISION 3
Appendix A
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Appi

ISSUE 10 REVISION 3
Appii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
GSM Burst Types
FRAME 1 FRAME 2
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
3 NORMAL BURST (NB) 3

Encrypted Bits Training Sequence Encrypted Bits
TB 57 26 57 TB GP
1 1 8.25
3 FREQ CORRECTION BURST (FB) 3

Fixed Bits
TB 142 TB GP
8.25
3 SYNCHRONISATION BURST (SB) 3

Encrypted Bits Synchronisation Sequence Encrypted Bits
TB TB GP
39 64 39
8.25
3 DUMMY BURST 3
Fixed Bits Training Sequence Fixed Bits
TB 57 26 TB GP

1 1 8.25
3 ACCESS BURST
Synchronisation Sequence Encrypted Bits GP
TB
73.25
41 36
3
156.25 Bit Durations
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Appiii

ISSUE 10 REVISION 3
26-Frame Multiframe
0.577ms
Timeslot
TDMA frame
4.615ms
2 1 0

Idle SACCH
Multiframe

120ms
Time
Appiv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
51-Frame Multiframe Control Channel
0.577ms
Timeslot
TDMA frame
4.615ms
2 1 0

Multiframe

240ms
Time
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Appv

ISSUE 10 REVISION 3
Control Channels
CCH
Control Channel

BCCH
DCCH
- downlink only
SDCCH ACCH Synch.

BCCH
Channels

FACCH SACCH SCH FCH
CCCH

RACH- PCH/AGCH
uplink - downlink
ACRONYMS!!
NB= NORMAL BURST

FB = FREQUENCY BURST
SB = SYCHRONISATION BURST
AB = ACCESS BURST
DB = DUMMY BURST
Appvi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
BCCH/CCCH Multiframe

50

I KEY
50 R
R
R
C R= RACH (Random)
R
B= BCCH (Broadcast) R
F= FCCH (Frequency) R
S= SCH (Sync.) R
C C= CCCH (Common) R
I= Idle R
S R
40 F 40 R
R
C R
R
R
R
C R
R
R
S R
30 F 30 R
R
C R
R
R
R
C R
R
R
S R
20 F 20 R
R
C R
R
R
R
C R
R
R
S R
10 F 10 R
R
C R
R
R
R
B R
R
R
Downlink S Uplink R
0 F 0 R
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Appvii

ISSUE 10 REVISION 3
DCCH Multiframe
50

I I 50
I I

I

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

I

I
I
I
10

10

I I
D2 D2 A7 A3
D1 D1 A6 A2
Downlink D0 D0 Uplink A5 A1
0 0
Appviii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
Combined Multiframe

50 I I 50

D2 D2

A1 A3
KEY

R
R
R
R

R= RACH (Random)
B= BCCH (Broadcast)

A0 A2
F= FCCH (Frequency) D1 D1
40

S
F
S
F
S=
C=
D=
SCH (Sync.)
CCCH (Common)
SDCCH/4 (Dedicated) 40
A= SACCH/C4 (Associated) D0 D0
D3 D3 I= Idle
R R
R R
D2 D2 R R
R R
R R
S S R R
30 F F 30 R R
R R
D1 D1 R R
R R
R R
R R
D0 D0 R R
R R
R R
S S R R
20 F F 20 R R
R R
C C R R
R R
R R

R R
R R
C C

A3 A1

S S
10 F F 10

C C

A2 A0

R R
B B R R
Downlink S S Uplink D3 D3
0 F F 0
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Appix

ISSUE 10 REVISION 3
Appx SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
Glossary of Terms
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosi

Numbers ISSUE 10 REVISION 3
Numbers
# Number.
2 Mbit/s link 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.
4GL 4th Generation Language.
A
A interface Interface between MSC and BSS.
A3 Authentication algorithm that produces SRES, using RAND
and Ki.
A38 A single algorithm performing the function of A3 and A8.
A5 Stream cipher algorithm, residing on an MS, that produces
ciphertext out of plaintext, using Kc.
A8 Ciphering key generating algorithm that produces Kc using
RAND and Ki.
AB Access Burst.
Abis interface 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.
ABR Answer Bid Ratio.
acdc PSM ACDC Power Supply module.
ac Alternating Current.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control.
ACCH Associated Control CHannel.
ACK, Ack ACKnowledgement.
ACM Accumulated Call meter.
ACM Address Complete Message.
ACPIM AC Power Interface Module. Used in M-Cell6 indor ac BTS
equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE Associated Control Service Element.
ACU Antenna Combining Unit.
A/D Analogue to Digital (converter).
ADC ADministration Centre.
ADC Analogue to Digital Converter.
ADCCP ADvanced Communications Control Protocol.
ADM ADMinistration processor.
ADMIN ADMINistration.
ADN Abbreviated Dialling Number.
Glosii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 A
ADPCM Adaptive Differential Pulse Code Modulation.

AE Application Entity.
AEC Accoustic Echo Control.
AEF Additional Elementary Functions.
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.
AFC Automatic Frequency Control.
AFN Absolute Frame Number.
AGC Automatic Gain Control.
AGCH Access Grant CHannel. A GSM common control channel
used to assign MS to a SDCCH or a TCH.
Ai Action indicator.
AI Artificial Intelligence.
AIB Alarm Interface Board.
AIO A class of processor.
Air interface The radio link between the BTS and the MS.
AM Amplitude Modulation.
AMA Automatic Message Accounting (processor).
AM/MP Cell broadcast mobile terminated message. A message
broadcast to all MSs in a cell.
AoC Advice of Change.
AoCC Advice of Change Charging supplementary service.
AoCI Advice of Change Information supplementary service.
AOC Automatic Output Control.
AP Application Process.
ARFCN Absolute Radio Frequency Channel Number. An integer
which defines the absolute RF channel number.
ARQ Automatic ReQuest for retransmission.
ARP Address Resolution Protocol.
ASCE 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).
ASE Application Service Element (OMC)
ASE Application Specific Entity (TCAP).
ASN.1 Abstract Syntax Notation One.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio.
ATB All Trunks Busy.
ATI Antenna Transceiver Interface.
ATT (flag) ATTach.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosiii

B ISSUE 10 REVISION 3
ATTS Automatic Trunk Testing Subsystem.

AU Access Unit.
AuC 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.
AUT(H) AUThentication.
AUTO AUTOmatic mode.
B
B Interface Interface between MSC and VLR.
BA BCCH Allocation. The radio frequency channels allocated in a
cell for BCCH transmission.
BAIC Barring of All Incoming Calls supplementary service.
BAOC Barring of All Outgoing Calls supplementary service.
BBBX Battery Backup Board.
BBH Base Band Hopping.
BCC BTS Colour Code.
BCCH Broadcast Control CHannel. A GSM control channel used to
broadcast general information about a BTS site on a per cell
or sector basis.
BCD Binary Coded Decimal.
BCF 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.
BCIE Bearer Capability Information Element.
BCU 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).
BCUP Base Controller Unit Power.
BER Bit Error Rate. A measure of signal quality in the GSM
system.
BES Business Exchange Services.
BFI Bad Frame Indication.
BHCA Busy Hour Call Attempt.
BI all Barring of All Incoming call supplementary service.
BIB 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).
BICRoam Barring of All Incoming Calls when Roaming outside the
Home PLMN Country supplementary service.
BIM Balanced-line Interconnect Module.
Bin An area in a data array used to store information.
BL BootLoad. Also known as download. For example, databases
and software can be downloaded to the NEs from the BSS.
Glosiv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 B
BLLNG BiLLiNG.
bit/s Bits per second (bps).
Bm Full rate traffic channel.
BN Bit Number. Number which identifies the position of a
particular bit period within a timeslot.
BPF Bandpass Filter.
BPSM mBCU Power Supply Module.
BS Basic Service (group).
BS 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.
BSC 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).
BSG Basic Service Group.
BSIC 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-NCELL BSIC of an adjacent cell.
BSP Base Site control Processor (at BSC).
BSN Backward Sequence Number.
BSS 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.
BSSAP BSS Application Part (of Signalling System No. 7) (DTAP +
BSSMAP).
BSSC 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.
BSSMAP Base Station System Management Application Part (6-8).
BSSOMAP BSS Operation and Maintenance Application Part (of
Signalling System No. 7).
BSU 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).
BT British Telecom.
BT Bus Terminator.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosv

C ISSUE 10 REVISION 3
BTC Bus Terminator Card.

BTF Base Transceiver Function.
BTP Base Transceiver Processor (at BTS). One of the six basic
task groups within the GPROC.
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).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.
C
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 ITU-TSS Signalling System 7 (sometimes referred to as S7 or
SS#7).
CA Cell Allocation. The radio frequency channels allocated to a
particular cell.
CA Central Authority.
CAB Cabinet.
CADM Country ADMinistration. The Motorola procedure used within
DataGen to create new country and network files in the
DataGen database.
CAI Charge Advice Information.
CAT Cell Analysis Tool.
CB Cell Broadcast.
CB Circuit Breaker.
CBC Cell Broadcast Centre.
CBCH Cell Broadcast CHannel.
CBF Combining Bandpass Filter.
CBL Cell Broadcast Link.
CBM Circuit Breaker Module.
CBMI Cell Broadcast Message Identifier.
CBSMS Cell Broadcast Short Message Service.
CBUS Clock Bus.
CC Connection Confirm (Part of SCCP network connectivity).
CC Country Code.
CC Call Control.
CCB 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.
CCBS Completion of Calls to Busy Subscriber supplementary
service.
Glosvi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 C
CCCH Common Control CHannels. A class of GSM control

channels used to control paging and grant access. Includes
AGCH, PCH, and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding.
CCH Control CHannel. Control channels are channels which carry
system management messages.
CCH Council for Communications Harmonization (referred to in
GSM Recommendations).
CCIT Comit Consultatif International Tlgraphique et
Tlphonique. This term has been superceded by ITUTSS
(International Telecommunications Union
Telecommunications Sector).
CCM Current Call Meter.
CCP Capability/Configuration Parameter.
CCPE Control Channel Protocol Entity.
CCS 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.
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab cron job file).
CDR Call Detail Records.
CDUR Chargeable DURation.
CEB Control Equalizer Board (BTS).
CED Called station identifier.
CEIR Central Equipment Identity Register.
Cell 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).
1 Cell =
1 Sector
Omni Site 6-Sector Site

1-Cell Site or
(1 BTS) 6-Cell Site
(6 BTSs)
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosvii

C ISSUE 10 REVISION 3
CEND End of charge point.

CEPT Confrence des administrations Europennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor.
CF Conversion Facility.
CF all Call Forwarding services.
CFB Call Forwarding on mobile subscriber Busy supplementary
service.
CFC Conditional Call Forward.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service.
CFNRy Call Forwarding on No Reply supplementary service.
CFU Call Forwarding Unconditional supplementary service.
Channel 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.
CIM Coaxial Interconnect Module.
CHP CHarging Point.
CHV Card Holder Verification information.
CKSN Ciphering Key Sequence Number.
CI Cell Identity. A block of code which identifies a cell within a
location area.
CI CUG Index.
CIC Circuit Identity Code.
CIR, C/I Carrier to Interference Ratio.
Ciphertext Unintelligible data produced through the use of encipherment.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity.
CLIP Calling Line Identification Presentation supplementary
service.
CLIR Calling Line Identification Restriction supplementary service.
CLK Clock.
CLKX Clock Extender half size board. The fibre optic link that
distributes GCLK to boards in system (p/o BSS etc).
CLM Connectionless Manager.
CLR CLeaR.
CM Configuration Management. An OMC application.
CM Connection Management.
CMD CoMmanD.
CMM Channel Mode Modify.
CMIP Common Management Information Protocol.
Glosviii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 C
CMISE 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).
CMR Cellular Manual Revision.
CNG CalliNg tone.
COLI COnnected Line Identity.
Collocated Placed together; two or more items together in the same
place.
Coincident Cell 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.
COLP COnnected Line Identification Presentation supplementary
service.
COLR COnnected Line Identification Restriction supplementary
service.
CODEX Manufacturers name for a type of multiplexer and packet
switch commonly installed at the Motorola OMC-R.
COM Code Object Manager.
COM COMplete.
COMB Combiner.
CONNACK CONNect ACKnowledgement.
COMM, Comms COMMunications.
CommsLink Communications Link. (2Mbit/s)
CONF CONFerence circuit.
CONFIG CONFIGuration Control Program.
CP Call Processing.
CPU Central Processing Unit.
C/R Command/Response field bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity).
CRC Cyclic Redundancy Check (3 bit).
CRE Call RE-establishment procedure.
CREF Connection REFused (Part of SCCP network connectivity).
CRM Cell Resource Manager.
CRM-LS/HS 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.
CRT Cathode Ray Tube (video display terminal).
CSFP Code Storage Facility Processor (at BSC and BTS).
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosix

D ISSUE 10 REVISION 3
CT Call Transfer supplementary service.

CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool).
CTR Common Technical Regulation.
CTS Clear to Send. Method of flow control (RS232 Interface).
CTU Compact Transceiver Unit (M-Cellhorizon radio).
CUG Closed User Group supplementary service.
Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service.
D
D Interface Interface between VLR and HLR.
D/A Digital to Analogue (converter).
DAB Disribution Alarm Board.
DAC Digital to Analogue Converter.
DACS Digital Access Cross-connect System.
DAN Digital ANnouncer (for recorded announcements on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape.
DataGen Sysgen Builder System. A Motorola offline BSS binary object
configuration tool.
dB Decibel. A unit of power ratio measurement.
DB DataBase.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration/Database Administrator.
DBMS DataBase Management System.
dc Direct Current.
DCB Diversity Control Board (p/o DRCU).
DCCH Dedicated Control CHannel. A class of GSM control
channels used to set up calls and report measurements.
Includes SDCCH, FACCH, and SACCH.
DCD Data Carrier Detect signal.
DCE Data Circuit terminating Equipment.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in
Horizonmacro).
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation
devices to the Operations Systems.
DC PSM DC Power Supply Module.
Glosx SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 D
DCS1800 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.
DDF Dual-stage Duplexed combining Filter. (Used in
Horizonmacro).
DDS DataGen Directory Structure.
DDS Data Drive Storage.
DDS Direct Digital Synthesis.
DEQB Diversity Equalizer Board.
DET DETach.
DFE Decision Feedback Equalizer.
DGT Data Gathering Tool.
DHP Digital Host Processor.
DIA Drum Intercept Announcer.
DINO E1/HDSL Line termination module.
DINO T1 Line termination module.
DISC DISConnect.
Discon Discontiuous.
DIQ Diversity In phase and Quadrature phase.
DIR Device Interface Routine.
DL Data Link (layer).
DLCI Data Link Connection Identifier.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLSP Data Link Service Process.
DLSP Digital Link Signalling Processor.
Dm Control channel (ISDN terminology applied to mobile service).
DMA Deferred Maintenance Alarm. An alarm report level; an
immediate or deferred response is required (see also PMA).
DMA Direct Memory Access.
DMR Digital Mobile Radio.
DMX Distributed Electronic Mobile Exchange (Motorolas
networked EMX family).
DN Directory Number.
DNIC Data network identifier.
Downlink Physical link from the BTS towards the MS (BTS transmits,
MS receives).
DP Dial/Dialled Pulse.
DPC 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.
DPC Digital Processing and Control board.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxi

D ISSUE 10 REVISION 3
DPNSS Digital Private Network Signalling System (BT standard for

PABX interface).
DPP Dual Path Preselector.
DPR, DPRAM Dual Port Random Access Memory.
DPSM Digital Power Supply Module.
DRAM Dynamic Random Access Memory.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for 8
circuits (p/o IWF).
DRCU Diversity Radio Channel Unit. Contains transceiver, digital
control circuits, and power supply (p/o BSS) (see RCU).
(D)RCU Generic term for radio channel unit. May be standard RCU or
diversity radio channel unit DRCU.
DRI Digital Radio Interface. Provides encoding/decoding and
encryption/decryption for radio channel (p/o BSS).
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
DRIX DRI Extender half size board. Fibre optic link from DRI to
BCU (p/o BSS).
DRX, DRx 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.
DS-2 German term for 2 Mbit/s line (PCM interface).
DSE Data Switching Exchange.
DSI Digital Speech Interpolation.
DSP Digital Signal Processor.
DSS1 Digital Subscriber Signalling No 1.
DSSI Diversity Signal Strength Indication.
DTAP Direct Transfer Application Part (6-8).
DTE Data Terminal Equipment.
DTF Digital Trunk Frame.
DT1 DaTa form 1 (Part of SCCP network connectivity).
DTI Digital Trunk Interface.
DTMF Dual Tone Multi-Frequency (tone signalling type).
DTR Data Terminal Ready signal. Method of flow control (RS232
Interface).
DTRX Dual Transceiver Module. (Radio used in M-Cellarena and
M-Cellarena macro).
DTX, DTx 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.
Glosxii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 E
Dummy burst 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.
DYNET DYnamic NETwork. Used to specify BTSs sharing dynamic
resources.
E
E See Erlang.
E Interface Interface between MSC and MSC.
EA External Alarms.
EAS External Alarm System.
Eb/No Energy per Bit/Noise floor.
EBCG Elementary Basic Service Group.
EC Echo Canceller. Performs echo suppression for all voice
circuits.
ECB Provides echo cancelling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode (facsimile).
Ec/No Ratio of energy per modulating bit to the noise spectral
density.
ECT Event Counting Tool.
ECT Explicit Call Transfer supplementary service.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable Read Only Memory.
EGSM900 Extended GSM900.
EI Events Interface. Part of the OMC-R GUI.
EIR Equipment Identity Register.
EIRP Effective Isotropic Radiated Power.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC application.
EMC ElectroMagnetic Compatibility.
EMF Electro Motive Force.
EMI Electro Magnetic Interference.
eMLPP enhanced Multi-Level Precedence and Pre-emption service.
EMMI Electrical Man Machine Interface.
EMU Exchange office Management Unit (p/o Horizonoffice)
EMX Electronic Mobile Exchange (Motorolas MSC family).
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxiii

F ISSUE 10 REVISION 3
en bloc 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.
EOT End of Tape.
EPROM Erasable Programmable Read Only Memory.
EPSM Enhanced Power Supply Module (+27 V).
EQB Equalizer Board. Control circuit for equalization for 8 time
slots each with equalizing circuitry and a DSP (p/o RCU).
EQCP Equalizer Control Processor.
EQ DSP Equalizer Digitizer Signal Processor.
Erlang 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).
ERP Ear Reference Point.
ERP Effective Radiated Power.
ERR ERRor.
ESP Electro-static Point.
ESQL Embedded SQL (Structured Query Language). An RDBMS
programming interface language.
E-TACS Extended TACS (analogue cellular system, extended).
Ethernet Type of Local Area Network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETSI European Telecommunications Standards Institute.
ETX End of Transmission.
EXEC Executive Process.
F
F Interface Interface between MSC and EIR.
FA Fax Adaptor.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACCH 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).
FACCH/F Fast Associated Control Channel/Full rate.
FACCH/H Fast Associated Control Channel/Half rate.
FB Frequency correction Burst (see Frequency correction burst).
Glosxiv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 F
FC-AL Fibre Channel Arbitration Loop. (Type of hard disc).

FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction of
the mobile (MS).
FCP Fault Collection Process (in BTS).
FCS Frame Check Sequence.
FDM Frequency Division Multiplex.
FDMA Frequency Division Multiple Access.
FDN Fixed Dialling Number.
FDP Fault Diagnostic Procedure.
FEC Forward Error Correction.
FEP Front End Processor.
FER Frame Erasure Ratio.
FFS, FS For Further Study.
FH Frequency Hopping.
FIB Forward Indicator Bit.
FIR Finite Impulse Response (filter type).
FK Foreign Key. A database column attribute; the foreign key
indicates an index into another table.
FM Fault Management (at OMC).
FM Frequency Modulation.
FMIC Fault Management Initiated Clear.
FMUX Fibre optic MUltipleXer.
FN Frame Number. Identifies the position of a particular TDMA
frame within a hyperframe.
FOA First Office Application.
FOX Fibre Optic eXtender.
FR 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).
FRU Field Replaceable Unit.
Frequency correction Period of RF carrier less than one timeslot whose modulation
bit stream allows frequency correction to be performed easily
within an MS burst.
FS Frequency Synchronization.
FSL 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.
FSN Forward Sequence Number.
FTAM File Transfer, Access, and Management. An ASE which
provides a means to transfer information from file to file
(OMC).
ftn forwarded-to number.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxv

G ISSUE 10 REVISION 3
FTP Fault Translation Process (in BTS).

FTP File Transfer Protocol.
G
G Interface Interface between VLR and VLR.
Gateway MSC 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.
GB, Gbyte Gigabyte.
GBIC Gigabit Interface Converter.
GCLK Generic Clock board. System clock source, one per site (p/o
BSS, BTS, BSC, IWF, RXCDR).
GCR Group Call Register.
GDP Generic DSP Processor board. Interchangeable with the XCDR
board.
GDP E1 GDP board configured for E1 link usage.
GDP T1 GDP board configured for T1 link usage.
GHz Giga-Hertz (109).
GID Group ID. A unique number used by the system to identify a
users primary group.
GMB GSM Multiplexer Board (p/o BSC).
GMR GSM Manual Revision.
GMSC Gateway Mobile-services Switching Centre (see Gateway
MSC).
GMSK Gaussian Minimum Shift Keying. The modulation technique
used in GSM.
GND GrouND.
GOS Grade of Service.
GPA GSM PLMN Area.
GPC General Protocol Converter.
GPROC Generic Processor board. GSM generic processor board: a
68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF,
RXCDR).
GPROC2 Generic Processor board. GSM generic processor board: a
68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR).
GPRS General Packet Radio Service.
GPS Global Positioning by Satellite.
GSA 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.
GSA GSM System Area. The group of GSM PLMN areas
accessible by GSM MSs.
GSM Groupe Spcial Mobile (the committee).
GSM Global System for Mobile communications (the system).
Glosxvi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 H
GSM MS GSM Mobile Station.

GSM PLMN GSM Public Land Mobile Network.
GSR GSM Software Release.
GT Global Title.
GTE Generic Table Editor. The Motorola procedure which allows
users to display and edit MCDF input files.
Guard period Period at the beginning and end of timeslot during which MS
transmission is attenuated.
GUI Graphical User Interface.
GUI client A computer used to display a GUI from an OMC-R GUI
application which is beingbrun on a GUI server.
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).
GWY GateWaY (MSC/LR) interface to PSTN.
H
H Interface Interface between HLR and AUC.
H-M Human-Machine Terminals.
HAD, HAP HLR Authentication Distributor.
HANDO, Handover 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.
HCU Hybrid Combining Unit. (Used in Horizonmacro).
HDLC High level Data Link Control.
HDSL High bit-rate Digital Subscriber Line.
HLC High Layer Compatibility. The HLC can carry information
defining the higher layer characteristics of a teleservice active
on the terminal.
HLR Home Location Register. The LR where the current location
and all subscriber parameters of an MS are permanently
stored.
HMS Heat Management System. The system that provides
environmental control of the components inside the ExCell,
TopCell and M-Cell cabinets.
HO HandOver. (see HANDO above).
HPU Hand Portable Unit.
HOLD Call hold supplementary service.
HPLMN Home PLMN.
HR 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).
HS HandSet.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxvii

I ISSUE 10 REVISION 3
HSI/S High Speed Interface card.

HSM HLR Subscriber Management.
HSN Hopping Sequence Number.
HU Home Units.
HW Hardware.
Hyperframe 2048 superframes. The longest recurrent time period of the
frame structure.
I
I Information frames (RLP).
IA Incomming Access (closed user group (CUG) SS
(supplementary service)).
IA5 International Alphanumeric 5.
IADU Integrated Antenna Distribution Unit. (The IADU is the
equivalent of the Receive Matrix used on pre-M-Cell BTSs).
IAM Initial Address Message.
IAS Internal Alarm System.
IC Integrated Circuit.
IC Interlock Code (CUG SS).
IC(pref) Interlock Code op the preferential CUG.
ICB Incoming Calls Barred.
ICC Integrated Circuit(s) Card.
ICM In-Call Modification.
ICMP Internet Control Message Protocol.
ID, Id IDentification/IDentity/IDentifier.
IDN Integrated Digital Network.
IDS INFOMIX Database Server. (OMC-R relational database
management system).
IE Information Element (signalling).
IEC International Electrotechnical Commission.
IEEE Institute of Electrical and Electronic Engineers.
IEI Information Element Identifier.
I-ETS Interim European Telecommunication Standard.
IF Intermediate Frequency.
IFAM Initial and Final Address Message.
IM InterModulation.
IMACS Intelligent Monitor And Control System.
IMEI 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.
IMM IMMediate assignment message.
Glosxviii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 I
IMSI 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.
IN Intelligent Network.
IN Interrogating Node. A switching node that interrogates an
HLR, to route a call for an MS to the visited MSC.
INS IN Service.
INS Intelligent Network Service.
InterAlg Interference Algorithm. A single interference algorithm in a
cell.
Interworking The general term used to describe the inter-operation of
networks, services, supplementary services and so on. See
also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Platform.
IP Initialisation Process.
IP Internet Protocol.
IPC Inter-Process Communication.
IP, INP INtermodulation Products.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (48 V).
IPX (A hardware component).
ISAM Indexed Sequential Access Method.
ISC International Switching Centre.
ISDN Integrated Services Digital Network. An integrated services
network that provides digital connections between
user-network interfaces.
ISG Motorola Information Systems group (formally CODEX).
ISO International Organisation for Standardization.
ISQL Informix Structured Query Language.
ISUP ISDN User Part (of signalling system No. 7).
IT Inactivity Test (Part of SCCP network connectivity).
ITC Information Transfer Capability.
ITU International Telecommunication Union.
ITUTSS International Telecommunication Union Telecommunications
Sector.
IWF 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.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxix

K ISSUE 10 REVISION 3
IWMSC InterWorking MSC.

IWU InterWorking Unit.
K
k kilo (103).
k Windows size.
K Constraint length of the convolutional code.
KAIO Kernal Asynchronous Input/Output.
kb, kbit kilo-bit.
kbit/s, kbps kilo-bits per second.
kbyte kilobyte.
Kc Ciphering key. A sequence of symbols that controls the
operation of encipherment and decipherment.
kHz kilo-Hertz (103).
Ki Individual subscriber authentication Key (p/o authentication
process of AUC).
KIO A class of processor.
KSW Kiloport SWitch board. TDM timeslot interchanger to connect
calls (p/o BSS).
KSWX KSW Expander half size board. Fibre optic distribution of
TDM bus (p/o BSS).
kW kilo-Watt.
L
L1 Layer 1.
L2ML Layer 2 Management Link.
L2R 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 BOP L2R Bit Orientated Protocol.
L2R COP L2R Character Orientated Protocol.
L3 Layer 3.
LA 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.
LAC Location Area Code.
LAI Location Area Identity. The information indicating the location
area in which a cell is located.
LAN Local Area Network.
LANX LAN Extender half size board. Fibre optic distribution of LAN
to/from other cabinets (p/o BSS etc).
LAPB Link Access Protocol Balanced (of ITUTSS Rec. x.25).
LAPD Link Access Protocol Data.
LAPDm Link Access Protocol on the Dm channel.
Glosxx SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 L
LC Inductor Capacitor (type of filter).

LCF Link Control Function.
LCN Local Communications Network.
LCP Link Control Processor.
LE Local Exchange.
LED Light Emitting Diode.
LF Line Feed.
LI Length Indicator.
LI Line Identity.
LLC Lower Layer Compatibility. The LLC can carry information
defining the lower layer characteristics of the terminal.
Lm Traffic channel with capacity lower than a Bm.
LMP LAN Monitor Process.
LMS Least Mean Square.
LMSI 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.
LMT Local Maintenance Terminal.
LNA Low Noise Amplifier.
LND Last Number Dialled.
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.
LPC Linear Predictive Code.
LPLMN Local PLMN.
LR Location Register. The GSM functional unit where MS
location information is stored. The HLR and VLR are location
registers.
LSSU Link Stations Signalling Unit (Part of MTP transport system).
LSTR Listener Side Tone Rating.
LTA Long Term Average. The value required in a BTSs GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
LU Local Units.
LU Location Update.
LV Length and Value.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxi

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

ISSUE 10 REVISION 3 M
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.
MEF Maintenance Entity Function (GSM Rec. 12.00).
MF MultiFrame.
MF Multi-Frequency (tone signalling type).
MF MultiFunction block.
MGMT, mgmt Management.
MGR Manager.
MHS Message Handling System.
MHS Mobile Handling Service.
MHz Mega-Hertz (106).
MI Maintenance Information.
MIB Management Information Base. A Motorola OMC-R
database. There is a CM MIB and an EM MIB.
MIC Mobile Interface Controller.
Microcell 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.
min minute(s).
ms micro-second (106).
mBCU Micro Base Control Unit.
MIT Management Information Tree. Name of a file on the
Motorola OMC-R.
MM Man Machine.
MM Mobility Management.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method in which the user
interfaces with the software to request a function or change
parameters.
MMI client A machine configured to use the OMC-R software from an
MMI server.
MMI processor MMI client/MMI server.
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.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (see also 2Mbit/s link)
MNC Mobile Network Code.
MNT MaiNTenance.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxiii

M ISSUE 10 REVISION 3
MO Mobile Originated.
MO/PP Mobile Originated Point-to-Point messages.
MOMAP Motorola OMAP.
MoU Memorandum of Understanding.
MPC Multi Personal Computer (was p/o OMC).
MPH (mobile) Management (entity) - PHysical (layer) [primitive].
MPTY MultiParTY (Multi ParTY) supplementary service.
MPX MultiPleXed.
MRC Micro Radio Control Unit.
MRN Mobile Roaming Number.
MRP Mouth Reference Point.
MS Mobile Station. The GSM subscriber unit.
MSC Mobile-services Switching Centre, Mobile Switching Centre.
MSCM Mobile Station Class Mark.
MSCU Mobile Station Control Unit.
msec millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface to two
2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS).
MSIN Mobile Station Identification Number.
MSISDN 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).
MSRN Mobile Station Roaming Number. A number assigned by the
MSC to service and track a visiting subscriber.
MSU 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.
MT Mobile Terminated. Describes a call or short message
destined for an MS.
MT (0, 1, 2) 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.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part.
MT/PP Mobile Terminated Point-to-Point messages.
MTBF Mean Time Between Failures.
MTK Message Transfer LinK.
MTL MTP Transport Layer Link (A interface).
Glosxxiv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 N
MTP Message Transfer Part.

MTTR Mean Time To Repair.
Multiframe 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.
MU Mark Up.
MUMS Multi User Mobile Station.
MUX Multiplexer.
N
N/W Network.
NB Normal Burst (see Normal burst).
NBIN A parameter in the hoping sequence.
NCC Network (PLMN) Colour Code.
NCELL Neighbouring (of current serving) Cell.
NCH Notification CHannel.
ND No Duplicates. A database column attribute meaning the
column contains unique values (used only with indexed
columns).
NDC National Destination Code.
NDUB Network Determined User Busy.
NE Network Element (Network Entity).
NEF Network Element Function block.
NET Norme Europennes de Telecommunications.
NETPlan Frequency planning tool.
NF Network Function.
NFS Network File System.
NHA Network Health Analyst. Optional OMC-R processor feature.
NIC Network Interface Card.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralised control of
network information for example hostnames, IP addresses
and passwords.
NIU Network Interface Unit.
NIU-m Network Interface Unit, micro.
NLK Network LinK processor(s).
Nm Newton metres.
NM 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.
NMASE Network Management Application Service Element.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxv

O ISSUE 10 REVISION 3
NMC 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.
NMSI National Mobile Station Identification number.
NMT Nordic Mobile Telephone system.
NN No Nulls. A database column attribute meaning the column
must contain a value in all rows.
Normal burst A period of modulated carrier less than a timeslot.
NPI Number Plan Identifier.
NRZ Non Return to Zero.
NSAP Network Service Access Point.
NSP Network Service Provider.
NSS Network Status Summary.
NT Network Termination.
NT Non Transparent.
NTAAB New Type Approval Advisory Board.
NUA Network User Access.
NUI Network User Identification.
NUP National User Part (of signalling system No. 7).
NV NonVolatile.
NVRAM Non-Volatile Random Access Memory.
nW Nano-Watt (109).
O Optional.
OA Outgoing Access (CUG SS).
O&M Operations and Maintenance.
OASCU 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.
OCB Outgoing Calls Barred within the CUG.
OCXO Oversized Voltage Controlled Crystal Oscillator.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
offline IDS shutdown state.
online IDS normal operatng state.
OIC Operator Initiated Clear.
OLM Off_Line MIB. A Motorola DataGen database, used to modify
and carry out Radio Frequency planning on multiple BSS
binary files.
OLR Overall Loudness Rating.
Glosxxvi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 P
OMAP Operations and Maintenance Application Part (of signalling

system No. 7) (was OAMP).
OMC 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.
OMC-G Operations and Maintenance Centre Gateway Part.
(Iridium)
OMC-G Operations and Maintenance Centre GPRS Part.
OMC-R Operations and Maintenance Centre Radio Part.
OMC-S Operations and Maintenance Centre Switch Part.
OMF Operations and Maintenance Function (at BSC).
OML Operations and Maintenance Link.
OMP Operation and Maintenance Processor.
OMS Operation and Maintenance System (BSCOMC).
OMSS Operation and Maintenance SubSystem.
OOS Out Of Service.
OPC 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.
ORAC Olympus Radio Architecture Chipset.
OS Operating System.
OSI Open Systems Interconnection.
OSI RM OSI Reference Model.
OSF Operation Systems Function block.
OSF/MOTIF Open Software Foundation Motif. The basis of the GUI used
for the Motorola OMC-R MMI.
OSS Operator Services System.
Overlap 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.
P
PA Power Amplifier.
PAB Power Alarm Board.
PABX Private Automatic Branch eXchange.
PAD Packet Assembler/Disassembler facility.
Paging 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.
PATH CEPT 2 Mbit/s route through the BSS network.
PBUS Processor Bus.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxvii

P ISSUE 10 REVISION 3
PBX Private Branch eXchange.

PC Personal Computer.
PCH Paging CHannel. A GSM common control channel used to
send paging messages to the MSs.
PCHN Paging Channel Network.
PCHN Physical Channel.
PCM Pulse Code Modulation (see also 2 Mbit/s link which is the
physical bearer of PCM).
PCN Personal Communications Network.
PCR Preventative Cyclic Retransmission. A form of error
correction suitable for use on links with long transmission
delays, such as satellite links.
PCU Packet Control Unit (p/o GPRS).
PCU Picocell Control unit (p/o M-Cellaccess).
pd Potential difference.
PD Protocol Discriminator.
PD Public Data.
PDB Power Distribution Board.
PDF Power Distribution Frame (MSC/LR).
PDN Public Data Networks.
PDU Power Distribution Unit.
PDU Protected Data Unit.
PEDC Pan European Digital Cellular.
Peg A single incremental action modifying the value of a statistic.
Pegging Modifying a statistical value.
PH Packet Handler.
PH PHysical (layer).
PHI Packet Handler Interface.
PI Presentation Indicator.
Picocell A cell site where the base station antenna is mounted within a
building.
PICS Protocol Implementation Conformance Statement.
PID Process IDentifier/Process ID.
PIM PCM Interface Module (MSC).
PIN Personal Identification Number.
PIN Problem Identification Number.
PIX Parallel Interface Extender half size board. Customer alarm
interface (p/o BSS).
PIXT Protocol Implementation eXtra information for Testing.
PK Primary Key. A database column attribute, the primary key is
a not-null, non-duplicate index.
Plaintext Unciphered data.
Glosxxviii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 P
PlaNET Frequency planning tool.

PLL Phase Lock Loop (refers to phase locking the GCLK in the
BTS).
PLMN Public Land Mobile Network. The mobile communications
network.
PM Performance Management. An OMC application.
PM-UI Performance Management User Interface.
PMA Prompt Maintenance Alarm. An alarm report level; immediate
action is necessary (see also DMA).
PMS Pseudo MMS.
PMUX PCM MUltipleXer.
PN Permanent Nucleus (of GSM).
PNE Prsentation des Normes Europennes.
POI Point of Interconnection (with PSTN).
POTS Plain Old Telephone Service (basic telephone services).
p/o Part of.
pp, p-p Peak-to-peak.
PP Point-to-Point.
ppb Parts per billion.
PPE Primative Procedure Entity.
ppm Parts per million (x 106).
Pref CUG Preferential CUG.
Primary Cell 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.
PROM Programmable Read Only Memory.
Ps Location probability.
PSA Periodic Supervision of Accessability.
PSAP Presentation Services Access Point.
PSM Power Supply Module.
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.
PSTN Public Switched Telephone Network. The UK land line
telephone network.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTO Public Telecommunications Operator.
PUCT Price per Unit Currency Table.
PVC Permanent Virtual Circuit.
PW Pass Word.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxix

Q ISSUE 10 REVISION 3
PWR Power.
PXPDN Private eXchange Public Data Network.
Q
QA Q (Interface) Adapter.
Q3 Interface between NMC and GSM network.
Q-adapter Used to connect MEs and SEs to TMN (GSM Rec. 12.00).
QAF Q-Adapter Function.
QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to
TDM switch highway (see MSI).
QIC Quarter Inch Cartridge (Data storage format).
QOS Quality Of Service.
Quiescent mode IDS intermediate state before shutdown.
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).
RA RAndom mode request information field.
RAB Random Access Burst.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel.
RAM Random Access Memory.
RAND RANDom number (used for authentication).
RATI Receive Antenna Transceiver Interface.
RAx Rate Adaptation.
RBDS Remote BSS Diagnostic System (a discontinued Motorola
diagnostic facility).
RBER Residual Bit Error Ratio.
RBTS Remote Base Transceiver Station.
RCB Radio Control Board (p/o DRCU).
RCI Radio Channel Identifier.
RCP Radio Control Processor.
RCU Radio Channel Unit. Contains transceiver, digital control
circuits, and power supply (p/o BSS) (see DRCU).
RCVR Receiver.
RDBMS Relational DataBase Management System (INFORMIX).
RDI Radio Digital Interface System.
RDIS Restricted Digital Information.
RDM Reference Distribution Module.
RDN Relative Distinguished Name. A series of RDN form a unique
identifier, the distinguished name, for a particular network
element.
Glosxxx SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 R
REC, Rec RECommendation.

REJ REJect(ion).
REL RELease.
RELP Residual Excited Linear Predictive.
RELP-LTP RELP Long Term Prediction. A name for GSM full rate (see
full rate).
resync Resynchronize/resynchronization.
REQ REQuest.
Revgen A Motorola DataGen utility for producing an MMI script from a
binary object database.
RF Radio Frequency.
RFC, RFCH Radio Frequency Channel. A partition of the system RF
spectrum allocation with a defined bandwidth and centre
frequency.
RFE Receiver Front End (shelf).
RFEB Receiver Front End Board (p/o DRCU II).
RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RFN Reduced TDMA Frame Number.
RFU Reserved for Future Use.
RJ45 Network cable/Connector type.
RISC Reduced Instruction Set Computer.
RL Remote login.
RLC Release Complete.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between an MT and IWF. See GSM 04.22.
RLR Receiver Loudness Rating.
RLSD ReLeaSeD.
RMS Root Mean Square (value).
RMSU Remote Mobile Switching Unit.
RNTABLE Table of 128 integers in the hopping sequence.
ROM Read Only Memory.
ROSE 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).
Roundtrip 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.
RPE Regular Pulse Excited.
RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSM
digital speech coding scheme.
RPOA Recognised Private Operating Agency.
RPR Read Privilege Required. Access to the column is allowed
only for privileged accounts.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxxi

S ISSUE 10 REVISION 3
RR Radio Resource management.

RR Receive Ready (frame).
RRSM Radio Resource State Machine.
RS232 Standard serial interface.
RSE Radio System Entity.
RSL Radio Signalling Link.
RSLF Radio System Link Function.
RSLP Radio System Link Processor.
RSS Radio SubSystem (replaced by BSS).
RSSI Received Signal Strength Indicator.
RSZI Regional Subscription Zone Identity.
RTC Remotely Tuneable Channel Combiner.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function.
RTF Receive Transmit Functions.
RTS Request to Send. Method of flow control (RS232 Interface).
RU Rack Unit.
Run level System processor operating mode.
Rx Receive(r).
RXCDR Remote Transcoder.
RXF Receive Function (of the RTF).
RXLEV-D Received signal level downlink.
RXLEV-U Received signal level uplink.
RXQUAL-D Received signal quality downlink.
RXQUAL-U Received signal quality uplink.
RXU Remote Transcoder Unit. The shelf which houses the
remote transcoder modules in a BSSC cabinet at a remote
transcoder site.
S
S/W SoftWare.
SABM Set Asynchronous Balanced Mode. A message which
establishes the signalling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for reporting RSSI and signal quality
measurements.
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.
SACCH/C8 Slow Associated Control CHannel/SDCCH/8.
SACCH/T Slow Associated Control CHannel/Traffic channel.
SACCH/TF Slow Associated Control CHannel/Traffic channel Full rate.
SACCH/TH Slow Associated Control CHannel/Traffic channel Half rate.
Glosxxxii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 S
SAGE A brand of trunk test equipment.

SAP 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.
SAP System Audits Process.
SAPI Service Access Point Indicator (identifier).
SAW Surface Acoustic Wave.
SB Synchronization Burst (see Synchronization burst).
SBUS Serial Bus.
SC Service Centre (used for Short Message Service).
SC Service Code.
SCCA System Change Control Administration. Software module
which allows full or partial software download to the NE
(OMC).
SCCP Signalling Connection Control Part (6-8).
SCEG Speech Coding Experts Group (of GSM).
SCH Synchronization CHannel. A GSM broadcast control channel
used to carry information for frame synchronization of MSs
and identification of base stations.
SCI Status Control Interface.
SCIP Serial Communication Interface Processor.
SCM Status Control Manager.
SCN Sub-Channel Number. One of the parameters defining a
particular physical channel in a BS.
SCP Service Control Point (an intelligent network entity).
SCSI Small Computer Systems Interface.
SCU Slim Channel Unit.
SCU900 Slim Channel Unit for GSM900.
SDCCH 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.
SDL Specification Description Language.
SDT SDL Developement Tool.
SDU Service Data Unit.
SDR Special Drawing Rights (an international basket currency for
billing).
SE Support Entity (GSM Rec. 12.00).
Secondary Cell 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.
SEF Support Entity Function (GSM Rec.12.00).
SFH Slow Frequency Hopping.
SI Screening Indicator.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxxiii

S ISSUE 10 REVISION 3
SI Service Interworking.
SI Supplementary Information.
SIA Supplementary Information A.
SID Silence Descriptor.
SIF Signal Information Field. The bits of a message signal unit
that carry information for a certain user transaction; the SIF
always contains a label.
SIM 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.
SIMM Single Inline Memory module.
SIMM System Integrated Memory Module.
SIO Service Information Octet. Eight bits contained in a message
signal unit, comprising the service indicator and sub-service
field.
SITE BSC, BTS or collocated BSC-BTS site.
SIX 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).
SK Secondary Key. A database column attribute, the secondary
key indicates an additional index and/or usage as a
composite key.
SL Signalling Link.
SLNK Serial Link.
SLR Send Loudness Rating.
SLTM Signalling Link Test Message.
SM Switch Manager.
SM Summing Manager.
SMAE System Management Application Entity (CCITT Q795, ISO
9596).
SMCB Short Message Cell Broadcast.
SME Short Message Entity.
SMG Special Mobile Group.
SMP Motorola Software Maintenance Program.
SMS Short Message Service.
SMSCB Short Message Service Cell Broadcast.
SMS-SC Short Message Service - Service Centre.
SMS/PP Short Message Service/Point-to-Point.
Smt Short message terminal.
SN Subscriber Number.
SND SeND.
SNDR SeNDeR.
Glosxxxiv SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 S
SNR Serial NumbeR.

SOA Suppress Outgoing Access (CUG SS).
SP Service Provider. The organisation through which the
subscriber obtains GSM telecommunications services. This
may be a network operator or possibly a separate body.
SP Signalling Point.
SP Special Product.
SP SPare.
SPC Signalling Point Code.
SPC Suppress Preferential CUG.
SPI Signalling Point Inaccessible.
SPP Single Path Preselector.
SQE Signal Quality Error.
SQL Structured Query Language.
SRD Service Request Distributor.
SRES Signed RESponse (authentication).
SS Supplementary Service. A modification of, or a supplement
to, a basic telecommunication service.
SS System Simulator.
SSA SCCP messages, Subsystem-allowed (see CCITT Q.712
para 1.15).
SSAP Site System Audits Processor.
SSC Supplementary Service Control string.
SSF Subservice Field. The level 3 field containing the network
indicator and two spare bits.
SSM Signalling State Machine.
SSN SubSystem Number.
SSP Service Switching Point (an intelligent network element).
SSP SCCP messages, Subsystem-prohibited (see CCITT Q.712
para 1.18).
SSP SubSystem Prohibited message.
SSS Switching SubSystem (comprising the MSC and the LRs).
SS7 ANSI Signalling System No. 7 (alias C7).
STAN Statistical ANalysis (processor).
STAT STATistics.
stats Statistics.
STC System Timing Controller.
STMR Side Tone Masking rating.
SUERM Signal Unit Error Rate Monitor.
STP Signalling Transfer Point.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxxv

T ISSUE 10 REVISION 3
Super user User account that can access all files, regardless of
protection settings, and control all user accounts.
SURF Sectorized Universal Receiver Front-end (Used in
Horizonmacro).
SVC Switch Virtual Circuit.
SVM SerVice Manager.
SVN Software Version Number.
SW Software.
SWFM SoftWare Fault Management.
sync synchronize/synchronization.
Synchronization burst 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.
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for loading a
configuration database into a BTS.
T
T Timer.
T Transparent.
T Type only.
T43 Type 43 Interconnect Board. Provides interface to 12
unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for
2 Mbit/s circuits (See BIB).
TA Terminal Adaptor. A physical entity in the MS providing
terminal adaptation functions (see GSM 04.02).
TA Timing Advance.
TAC Type Approval Code.
TACS Total Access Communications System (European analogue
cellular system).
TAF Terminal Adaptation Function.
TATI Transmit Antenna Transceiver Interface. The TATI consists
of RF combining equipments, either Hybrid or Cavity
Combining. (See CCB).
TAXI Transparent Asynchronous Transmitter/Receiver Interface
(physical layer).
TBD To Be Determined.
TBR Technical Basis for Regulation.
TBUS TDM Bus.
TC Transaction Capabilities.
TCAP Transaction Capabilities Application Part (of Signalling
System No. 7).
TCB TATI Control Board.
TCH Traffic CHannel. GSM logical channels which carry either
encoded speech or user data.
Glosxxxvi SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 T
TCH/F A full rate TCH.

TCH/F2.4 A full rate TCH at 2.4 kbit/s.
TCH/FS A full rate Speech TCH.
TCH/H A half rate TCH.
TCH/H2.4 A half rate TCH at 2.4 kbit/s.
TCH/H4.8 A half rate TCH at 4.8 kbit/s.
TCH/HS A half rate Speech TCH).
TCI Transceiver Control Interface.
TCP/IP Transmission Control Protocol/Internet Protocol.
TC-TR Technical Commitee Technical Report.
TCU Transceiver Control Unit.
TDF Twin Duplexed Filter. (Used in M-Cellhorizon).
TDM Time Division Multiplexing.
TDMA Time Division Multiple Access.
TDU TopCell Digital Unit.
TE Terminal Equipment. Equipment that provides the functions
necessary for the operation of the access protocols by the
user.
Tei Terminal endpoint identifier.
TEI Terminal Equipment Identity.
TEMP TEMPorary.
TEST TEST control processor.
TFA TransFer Allowed.
TFP TransFer Prohibited.
TFTP Trivial File Transfer Protocol.
TI Transaction Identifier.
Timeslot The multiplex subdivision in which voice and signalling bits
are sent over the air. Each RF carrier is divided into 8
timeslots.
Timing advance 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.
TLV Type, Length and Value.
TM Traffic Manager.
TMI TDM Modem Interface board. Provides analogue interface
from IWF to modems for 16 circuits (p/o IWF).
TMM Traffic Metering and Measuring.
TMN 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.
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxxvii

T ISSUE 10 REVISION 3
TMSI 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.
TN Timeslot Number.
TON Type Of Number.
Traffic channels Channels which carry users speech or data (see also TCH).
Traffic unit Equivalent to an erlang.
Training sequence Sequence of modulating bits employed to facilitate timing
recovery and channel equalization in the receiver.
TRAU Transcoder Rate Adaption Unit.
TRU TopCell Radio unit.
TRX 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.
TS Technical Specification.
TS TeleService.
TS TimeSlot (see Timeslot).
TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech & Data Interface.
TSC Training Sequence Code.
TSI TimeSlot Interchange.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSW Timeslot SWitch.
TTCN Tree and Tabular Combined Notation.
TTL Transistor to Transistor Logic.
TTY TeleTYpe (refers to any terminal).
TU Traffic Unit.
TUP Telephone User Part (SS7).
TV Type and Value.
Tx Transmit(ter).
TXF Transmit Function (of the RTF).
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter.
Glosxxxviii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 U
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.
UDI Unrestricted Digital Information.
UDP User Datagram Protocol.
UDUB User Determined User Busy.
UHF Ultra High Frequency.
UI Unnumbered Information (Frame).
UIC Union International des Chemins de Fer.
UID User ID. Unique number used by the system to identify the
user.
UL Upload (of software or database from an NE to a BSS).
Um Air interface.
UMTS Universal Mobile Telecommunication System.
UPCMI Uniform PCM Interface (13 bit).
UPD Up to Date.
Uplink Physical link from the MS towards the BTS (MS transmits,
BTS receives).
UPS Uninterruptable Power Supply.
UPU User Part Unavailable.
Useful part of burst 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.
USSD Unstructured Supplementary Service Data.
UUS User-to-User Signalling supplementary service.
V
V Value only.
VA Viterbi Algorithm (used in channel equalizers).
VAD Voice Activity Detection. A process used to identify presence
or absence of speech data bits. VAD is used with DTX.
VAP Videotex Access Point.
VBS Voice Broadcast Service.
VC Virtual Circuit.
VCO Voltage Controlled Oscillator.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit.
VGCS Voice Group Call Service.
VLR 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.
VLSI Very Large Scale Integration (in ICs).
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxxxix

W ISSUE 10 REVISION 3
VMSC Visited MSC. (Recommendation not to be used).

VOX Voice Operated Transmission.
VPLMN Visited PLMN.
VSC Videotex Service Centre.
V(SD) Send state variable.
VSP Vehicular Speaker Phone.
VSWR Voltage Standing Wave Ratio.
VTX host The components dedecated to Videotex service.
W
WAN Wide Area Network.
WPA Wrong Password Attempts (counter).
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network
management purposes.
WSF Work Station Function block.
WWW World Wide Web.
X
X.25 CCITT specification and protocols for public packet-switched
networks (see PSPDN).
X.25 link A communications link which conforms to X.25 specifications
and uses X.25 protocol (NE to OMC links).
XBL Transcoder to BSS Link. The carrier communications link
between the Transcoder (XCDR) and the BSS.
XCB Transceiver Control Board (p/o Transceiver).
XCDR Full-rate Transcoder. Provides speech transcoding and 4:1
submultiplexing (p/o BSS, BSC or XCDR).
XCDR board 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.
XFER Transfer.
XID eXchange IDentifier.
X-Term X terminal window.
Z
ZC Zone Code
Glosxl SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 Z
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Glosxli

Z ISSUE 10 REVISION 3
Glosxlii SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3
Answers
EMOTOROLA LTD. 2000 SYS03: BSS Database Application Answers1

ISSUE 10 REVISION 3
Answers2 SYS03: BSS Database Application EMOTOROLA LTD. 2000

ISSUE 10 REVISION 3 Power Budget Exercise
Power Budget Exercise

The figures specified on the facing page can be used by the HDPC to calculate the
Power budget assessment. Use the working area to calculate PBGT(n).

serving = 33 (90) 11
serving = 112

neighbour = min (ms_txpwr_max(n),P) RXLEV_NCELL (n)
neighbour = 33 (75)
neighbour = 108
PBGT (n)= serving Neighbour
PBGT (n)= 112 108
PBGT (n)= 4

Power Budget Exercise ISSUE 10 REVISION 3
Quality Flag Exercise Answer
SERVING
serving = 25 (65) 9
serving = 81
NEIGHBOUR
neighbour = min (ms_txpwr_max(n),P RXLEV_NCELL (n)
serving = 25 (70)
serving = 95
PBGT (n) = serving neighbour

PBGT (n) = 81 95
PBGT (n) = 14
CRITERION 1
PASS
CRITERION 2
= +20
ho_only_max_pwr=0
Qual_pwr_flag=0
Qual_margin_flag=1
(14+6)<0
YES
Remove neighbour
from candidate list
ho_rec message
sent. Contains
no neighbours

ISSUE 10 REVISION 3 XBL Connectivity Exercise answers
XBL Connectivity Exercise answers

Complete the database parameters for the connectivity shown opposite.

EAS Exercise
Using the details specified opposite complete the following database parameters:
BTS Script (site

32)
equip 32 EAS
0
15
15
0 1 X X
0 0 0 1 0 X X X
1 2 3 4 5
0 1 2 3 4 X X X
BTS Script (site

33)
equip 33 EAS
0
X X X X
1 0 X X X X X X X X X X X X X
X
1 2
3 4 X X X X X X X X X X X X X
X
BSC Script
chg_eas_alarm 1 2 Smoke Alarm
chg_eas_alarm 2 2 Door Intruder

ISSUE 10 REVISION 3 # Script for SYS03 RXCDR Answers
# Script for SYS03 RXCDR Answers
# 1.6.0.0 (GSR 4)
equip 0 SITE
0
equip 0 CAB
0
5
equip 0 CAGE
0
0
0
yes
equip 0 KSW
0
0
0
no
equip 0 BSP
0
0
25

# Script for SYS03 RXCDR Answers ISSUE 10 REVISION 3
equip 0 MSI
6
0
6
0
equip 0 MSI
8
0
8
0
equip 0 MSI
10
0
10
0
equip 0 MSI
21
0
21
1
equip 0 MSI
22
0
22
1
equip 0 MSI
23
0
23
1
equip 0 GCLK
0
0
no
no
no
# XBL to BSC 1
equip 0 XBL
0
64
8
1
25
2500
3
7
# XBL to BSC 2

ISSUE 10 REVISION 3 # Script for SYS03 RXCDR Answers
equip 0 XBL
1
64
8
0
15
2500
3
7
equip 0 OML
0
10
0
1
# XBL Connections
# DSP Options
chg_element dnlk_vad_dtx 1 0
chg_element msc_qt 84 0
# MTL/OML/CBL Descriptions
add_link 8 1 1 10 0 2
add_link 10 1 1 10 0 3
add_link 8 1 8 6 0 1
add_link 10 1 8 6 0 2
add_link 8 1 16 23 0 16
add_link 10 1 16 22 0 16
add_channel 8 1 2 0 23 0 5
add_channel 8 1 2 1 23 0 6
add_channel 8 1 2 2 23 0 7
add_channel 8 1 2 3 23 0 8
add_channel 8 1 3 0 23 0 9
add_channel 8 1 3 1 23 0 10
add_channel 8 1 3 2 23 0 11
add_channel 8 1 3 3 23 0 12
add_channel 8 1 4 0 23 0 13
add_channel 8 1 4 1 23 0 14
add_channel 8 1 4 2 23 0 15
add_channel 8 1 4 3 23 0 17
add_channel 8 1 5 0 23 0 18
add_channel 8 1 5 1 23 0 19
add_channel 8 1 5 2 23 0 20
add_channel 8 1 5 3 23 0 21
add_channel 8 1 6 0 23 0 22
add_channel 8 1 6 1 23 0 23
add_channel 8 0 1 0 21 0 1
add_channel 8 0 1 1 21 0 2
add_channel 8 0 1 2 21 0 3
add_channel 8 0 1 3 21 0 4
add_channel 8 0 2 0 21 0 5

# Script for SYS03 RXCDR Answers ISSUE 10 REVISION 3
add_channel 10 1 2 0 22 0 5
add_channel 10 1 2 1 22 0 6
add_channel 10 1 2 2 22 0 7
add_channel 10 1 2 3 22 0 8
add_channel 10 1 3 0 22 0 9
add_channel 10 1 3 1 22 0 10
add_channel 10 1 3 2 22 0 11
add_channel 10 1 3 3 22 0 12
chg_element clk_src_fail_reset_period 24 0
chg_element enh_ter_cic_mgt_ena 1 1
chg_element enh_ter_cic_mgt_ena 1 2

ISSUE 10 REVISION 3 # BSC No. 1 Answers
# BSC No. 1 Answers
# 1.6.0.0 (GSR 4)
freq_types_allowed 7
equip 0 SITE
0
equip 0 CAB
0
3
5
equip 0 CAGE
0
0
0
yes
equip 0 KSW
0
0
0
no
equip 0 KSW
0
1
0
no

# BSC No. 1 Answers ISSUE 10 REVISION 3
equip 0 BSP
0
0
20
equip 0 CSFP
0
0
18
equip 0 GPROC
1
0
19
equip 0 GPROC
3
0
21
equip 0 GPROC
4
0
22
equip 0 LCF
0
0
0
equip 0 LCF
1
0
0
equip 0 LCF
2
1
1
equip 0 MSI
1
0
16
0
equip 0 MSI
2
0
15
0
equip 0 MSI
3
0
14
0

equip 0 MSI
4
0
13
0
equip 0 GCLK
0
0
no
no
no
equip 0 GCLK
1
0
no
no
no
# XBL to BSC 1
equip bsc XBL
0
64
1
0
25
2500
3
7
equip 0 MTL
0
1
0
16
equip 0 OML
0
1
0
1
equip 0 CBL
0
1
0
8
sys03test
cbctest
# TIMER CONFIGURATION
chg_element SS7_L3_T1 850 0

# BSC No. 1 Answers ISSUE 10 REVISION 3

chg_element SS7_SLT_T1 8000 0
chg_element SCCP_TCONN_EST 30000 0
chg_element CLEAR_COMMAND 30000 0
chg_element RADIO_CHAN_RELEASED 30000 0
chg_element CIPHERING_SUCCESSFUL 30000 0
chg_element HO_SUCCESSFUL 4100 0
chg_element HO_ALLOCATION 30000 0
chg_element SCCP_RELEASED 30000 0
chg_element ASSIGN_SUCCESSFUL 4100 0
chg_element BSC_AUDIT 30001 0
chg_element SM_AUDIT_RESPONSE 30000 0
chg_element SCCP_TIAS 420000 0
chg_element SCCP_TIAR 900000 0
chg_element BSSMAP_T7 10000 0
chg_element BSC_AUDIT_RESPONSE 30000 0
chg_element BSSMAP_TQHO 30000 0
chg_element HO_REQUEST 30000 0
chg_element EXT_HO_ALLOCATION 30000 0
chg_element SCCP_TREL 15000 0
chg_element CIRCUIT_RESET_ACK 70000 0
chg_element SPI 10000 0
chg_element START_ACK 20000 0
# EQUIP CIRCUITS
equip 0 CIC
5 to 15
10
2
0
equip 0 CIC
17 to 23
10
4
3
# MISCELLANEOUS

chg_element mb_preference 0 0
chg_element dpc 33 0
chg_element opc 15 0
chg_element ni 2 0
chg_a5_alg_pr 1 2 0
chg_element option_emergency_preempt 1 0
chg_eas_alarm 3 2 Door Intruder Alarm
chg_eas_alarm 5 2 Window Intruder Alarm

# BTS Number 1 Answer Script ISSUE 10 REVISION 3
# BTS Number 1 Answer Script
# 1.6.0.0 (GSR 4)
equip 0 SITE
1
LCF
0
64
no
equip 1 CAB
0
9
pgsm
equip 1 CAGE
15
0
0
yes
# SITE CONFIGURATION
chg_element bts_type 1 1
# MMS THRESHOLDS DEFAULTED
# SMS OPTIONS
chg_element sms_dl_allowed 1 1
chg_element sms_ul_allowed 1 1
chg_element sms_tch_chan 2 1
add_cell 2 3 4 1 1 368 39 1
frequency_type = pgsm
bsic = 16
ccch_conf = 2
bs_ag_blks_res = 1
bs_pa_mfrms = 1
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1

ISSUE 10 REVISION 3 # BTS Number 1 Answer Script
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 0
max_tx_ms = 33
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
l_rxqual_ul_p = 1800
l_rxqual_dl_p = 1800
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900

l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
ncc_of_plmn_allowed = 255
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 1
rpd_trigger = 45
rpd_offset = 12
rpd_period = 2
chg_cell_element queue_management_information 0 2 3 4 1 1 368 39

chg_cell_element max_q_length_sdcch 0 2 3 4 1 1 368 39
chg_cell_element channel_reconfiguration_switch 1 2 3 4 1 1 368 39
chg_cell_element max_number_of_sdcchs 32 2 3 4 1 1 368 39
chg_cell_element sdcch_need_low_water_mark 12 2 3 4 1 1 368 39
chg_cell_element sdcch_need_high_water_mark 2 2 3 4 1 1 368 39
chg_cell_element tch_full_need_low_water_mark 5 2 3 4 1 1 368 39
chg_cell_element rr_t3109 12000 2 3 4 1 1 368 39
chg_cell_element rr_t3111_tch 1500 2 3 4 1 1 368 39
chg_cell_element dealloc_inact 10000 2 3 4 1 1 368 39
chg_cell_element ho_ack 10000 2 3 4 1 1 368 39
chg_cell_element rf_chan_rel_ack 20000 2 3 4 1 1 368 39
chg_element handover_required_reject_switch 0 0 cell_number=2 3 4 1 1 368 39
chg_cell_element interfer_bands,0 0 2 3 4 1 1 368 39


chg_cell_element rach_load_period 5 2 3 4 1 1 368 39
chg_cell_element ccch_load_period 5 2 3 4 1 1 368 39
chg_cell_element rr_ny1_rep 10 2 3 4 1 1 368 39
# AVERAGING ALGORITHM CONFIGURATION
# DEVICE\FUNCTION EQUIPAGE
equip 1 KSW
0
0
15
yes
equip 1 BTP
0
15
20
3
equip 1 DHP
15
2
22
3

equip 1 DHP
15
1
24
3
equip 1 GCLK
0
15
no
no
no
equip 1 MSI
1
15
16
0
equip 1 MSI
3
15
14
0
equip 1 COMB
0
255
00
01
equip 1 EAS
0
15
16
1111
00010001
12348
12346789
equip 1 DRI
00
0
drim
15
7
2 3 4 1 1 368 39
1
00
0
1
4
equip 1 DRI
01
0
drim
15
9

2 3 4 1 1 368 39
1
00
1
1
4
equip 1 DRI
02
0
drim
15
11
2 3 4 1 1 368 39
1
00
2
1
4
equip 1 DRI
03
0
drim
15
13
2 3 4 1 1 368 39
1
00
3
1
4
equip 1 DRI
04
0
drim
15
15
2 3 4 1 1 368 39
1
00
4
1
4
# TIMERS DEFAULTED
chg_element carriers_ins_pwr_fail 2 1
chg_element carrier_disable_time 300 1
chg_element tch_flow_control 1 1 cell_number=2 3 4 1 1 368 39

chg_element cbch_enabled 1 1 cell_number=2 3 4 1 1 368 39
chg_smscb_msg 0 200 3 1023 1 2 cell_number=2 3 4 1 1 368 39
MOTOROLA GSM
chg_smscb_msg 1 200 3 1022 1 2 cell_number=2 3 4 1 1 368 39
FREE CALLS TODAY

# BTS Number 2 Answer Script
# This is an M_Cell6 Site

# 1.6.0.0 (GSR 4)
equip 0 SITE
2
LCF
1
64
no
equip 2 CAB
0
11
1
# SMS OPTIONS
add_cell 2 3 4 1 1 368 36 2
bsic = 31
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2

bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30

u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 5
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2

add_cell 2 3 4 1 1 368 37 2

bsic = 29
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2

decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 5
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12

penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2

add_cell 2 3 4 1 1 368 38 2
bsic = 26
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0

pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5

l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 0
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2








equip 2 BTP
0
equip 2 MSI
0
0
0
equip 2 EAS
0
1111
0010000000000000
123
1 2 4 5 6 7 8 9 10 12 11 13 14 15 16 17
equip 2 DRI
00
0
fox
0
2 3 4 1 1 368 36
3
1
4

equip 2 DRI
10
0
fox
1
2 3 4 1 1 368 37
2
1
4
equip 2 DRI
20
0
fox
2
2 3 4 1 1 368 38
1
1
4
equip 2 DRI
21
0
fox
3
2 3 4 1 1 368 38
1
1
4
# TIMERS DEFAULTED

# BTS Number 3 (M_Cellarena) Answer ISSUE 10 REVISION 3
# BTS Number 3 (M_Cellarena) Answer
# 1.6.0.0 (GSR 4)
equip 0 SITE
3
LCF
0
64
no
equip 3 CAB
0
16
2
# SMS OPTIONS
add_cell 2 3 4 1 1 368 40 3
frequency_type = egsm
bsic = 21
ccch_conf = 1
bs_ag_blks_res = 1
bs_pa_mfrms = 0
en_incom_ho = 1
ho_margin_def = 8
sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2

ISSUE 10 REVISION 3 # BTS Number 3 (M_Cellarena) Answer
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1
alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35

missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 1
rpd_trigger = 45
rpd_offset = 8
rpd_period = 2



ISSUE 10 REVISION 3 # BTS Number 3 (M_Cellarena) Answer

equip 3 BTP
equip 3 MSI
0
0
0
equip 3 DRI
00
0
4
0
2 3 4 1 1 368 40
1
0
0
equip 3 DRI
01
0
4
1
2 3 4 1 1 368 40
1
0
0
# TIMERS DEFAULTED



ISSUE 10 REVISION 3 # Path Script Chain 1 Answers
# Path Script Chain 1 Answers
# Path Script Answer

# 1.6.0.0 (GSR 4)
# PATHS
# Path 0,Site 1
equip 0 path
1
0
30
1
10
# Path 1,Site 1
equip 0 path
1
1
20
3
00
01
2
00
01
1
30
# Path 0,Site 2
equip 0 path
2
0
30
1
10
30
2
01
# Path 1,Site 2
equip 0 path
2
1
20
3
00
01
2
00
# Path 0, Site 3
equip 0 path
3
0

# Path Script Chain 1 Answers ISSUE 10 REVISION 3
20
3
00
# Path 1,Site 3
equip 0 path
3
1
30
1
10
30
2
01
00
3
01
# RSLs Site 1
equip 0 RSL
1
0
0
2500
3
7
equip 0 RSL
1
1
1
2500
3
7
# RSLs Site 2
equip 0 RSL
2
0
0
2500
3
7
equip 0 RSL
2
1
1
2500
3
7
# RSLs Site 3

equip 0 RSL
3
0
0
2500
3
7
equip 0 RSL
3
1
1
2500
3
7
# RTFs
# RTFs, Site 1
equip 1 RTF
FULL
BCCH
00
0
1
2 3 4 1 1 368 39
65
255 255 255 255 255 255 255 255
00000000
0
0
equip 1 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 1 368 39
55
255 255 255 255 255 255 255 255
00000000
0
0
0
equip 1 RTF
FULL
NON_BCCH
02
0
1
2 3 4 1 1 368 39
45
255 255 255 255 255 255 255 255
00000000
0
0
0

equip 1 RTF
FULL
NON_BCCH
03
0
1
2 3 4 1 1 368 39
35
255 255 255 255 255 255 255 255
00000000
0
0
0
equip 1 RTF
FULL
NON_BCCH
04
0
1
2 3 4 1 1 368 39
25
255 255 255 255 255 255 255 255
00000000
0
0
0
# RTFs Site 2
equip 2 RTF
FULL
BCCH
00
0
1
2 3 4 1 1 368 36
70
255 255 255 255 255 255 255 255
77777777
0
equip 2 RTF
FULL
BCCH
10
0
1
2 3 4 1 1 368 37
75
255 255 255 255 255 255 255 255
55555555
0

equip 2 RTF
FULL
BCCH
20
0
1
2 3 4 1 1 368 38
80
255 255 255 255 255 255 255 255
22222222
0
equip 2 RTF
FULL
NON_BCCH
21
0
1
2 3 4 1 1 368 38
85
255 255 255 255 255 255 255 255
22222222
0
0
# RTFs, Site 3
equip 3 RTF
FULL
BCCH
00
0
1
2 3 4 1 1 368 40
10
255 255 255 255 255 255 255 255
55555555
0
equip 3 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 1 368 40
20
255 255 255 255 255 255 255 255
00000000
0
0
# MMS Priorities


# Enable GCLK sync
# LINK PARAMETERS
modify_value all nbit 0 MMS
modify_value all ber_oos_mon_period 50 MMS
modify_value all ber_restore_mon_period 1800 MMS
# NEIGHBOUR DEFINITIONS
1
1
0
1
1
1
1
0
0
0
add_neighbor 2 3 4 1 1 368 39 2 3 4 1 1 368 41 external ba_sacch
pgsm
100
23
33
5
10

ISSUE 10 REVISION 3 # 1.6.0.0 (GSR 4) # Hopping Answers
# 1.6.0.0 (GSR 4) # Hopping Answers
# 1.6.0.0 (GSR 4)
equip 0 SITE
0
equip 0 CAB
0
9
pgsm
equip 0 CAGE
0
0
0
yes
chg_element bts_type 0 0
equip 0 KSW
0
0
0
yes

# 1.6.0.0 (GSR 4) # Hopping Answers ISSUE 10 REVISION 3
equip 0 KSW
0
1
0
yes
equip 0 BSP
0
0
20
1
equip 0 BTF
3
equip 0 MSI
1
0
16
1
equip 0 MTL
0
1
0
16
equip 0 GCLK
0
0
chg_element dpc 2 0
chg_element opc 1 0
equip 0 CIC
1 to 6
10
2
chg_element ni 2 0
add_cell 2 3 4 1 0 368 39 0
bsic = 16
ccch_conf = 2
bs_ag_blks_res = 1
bs_pa_mfrms = 1
en_incom_ho = 1
ho_margin_def = 8

sdcch_ho = 0
sdcch_timer_ho = 1
mspwr_alg = 0
pwrc = 1
intave = 3
ms_p_con_ack = 2
bts_p_con_ack = 2
dyn_step_adj = 0
max_tx_bts = 6
max_tx_ms = 31
rxlev_min_def = 0
decision_1_n1 = 4
decision_1_n2 = 4
decision_1_n3 = 2
decision_1_n4 = 2
decision_1_n5 = 4
decision_1_n6 = 2
decision_1_n7 = 2
decision_1_n8 = 2
decision_1_p1 = 3
decision_1_p2 = 3
decision_1_p3 = 2
decision_1_p4 = 2
decision_1_p5 = 3
decision_1_p6 = 2
decision_1_p7 = 2
decision_1_p8 = 1

alt_qual_proc = 0
u_rxqual_ul_p = 0
u_rxqual_dl_p = 0
l_rxqual_ul_h = 900
l_rxqual_dl_h = 400
l_rxlev_ul_h = 5
l_rxlev_dl_h = 10
u_rxlev_ul_ih = 35
u_rxlev_dl_ih = 63
ms_max_range = 63
l_rxlev_ul_p = 20
l_rxlev_dl_p = 25
u_rxlev_ul_p = 30
u_rxlev_dl_p = 35
missing_rpt = 1
ba_alloc_proc = 0
link_fail = 2
full_pwr_rfloss = 1
dtx_required = 2
attach_detach = 0
max_retran = 3
tx_integer = 12
penalty_time = 0
rapid_pwr_down = 1
rpd_trigger = 40
rpd_offset = 8
rpd_period = 10



equip 0 DRI
00
0
drim
0
7
2 3 4 1 0 368 39
1
1
4
equip 0 DRI
01
0
drim
0
9
2 3 4 1 0 368 39
1
1
4
equip 0 DRI
02
0
drim
0
13
2 3 4 1 0 368 39
1
1
4

equip 0 RTF
FULL
BCCH
00
0
1
2 3 4 1 0 368 39
98
255 255 255 255 255 255 255 255
00000000
0
0
equip 0 RTF
FULL
NON_BCCH
01
0
1
2 3 4 1 0 368 39
95
00000000
11111111
0
0
0
equip 0 RTF
FULL
NON_BCCH
02
0
1
2 3 4 1 0 368 39
83
00000000
11111111
0
0
0
# CONFIGURE HOPPING SYSTEM
chg_element hopping_support 1 0 cell_number=2 3 4 1 0 368 39
chg_hopping 2 3 4 1 0 368 39 0 10 32 63 78 83 95



Sys03 Bss Database Application

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sys03 Bss Database Application

Caricato da

Copyright:

Formati disponibili

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5

FOR TRAINING PURPOSES ONLY

E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 2000

EMOTOROLA LTD. 2000 SYS03: BSS Database Application i

FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

and MOTOROLA are trademarks of Motorola Inc.

ii SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000 SYS03: BSS Database Application iii

FOR TRAINING PURPOSES ONLY

Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

iv SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

MSC Quietone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

EMOTOROLA LTD. 2000 SYS03: BSS Database Application v

FOR TRAINING PURPOSES ONLY

Short Message Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

vi SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000 SYS03: BSS Database Application vii

FOR TRAINING PURPOSES ONLY

Path Script Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

viii SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Frequency Hopping support via GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glosi

EMOTOROLA LTD. 2000 SYS03: BSS Database Application ix

FOR TRAINING PURPOSES ONLY

x SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 1

FOR TRAINING PURPOSES ONLY

Special key sequences

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

2 SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

First aid in case of electric shock

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 3

FOR TRAINING PURPOSES ONLY

Reporting safety issues

4 SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Warnings and cautions

Example and format

Example and format

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 5

FOR TRAINING PURPOSES ONLY

6 SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 7

FOR TRAINING PURPOSES ONLY

Human exposure to radio frequency energy (PCS1900 only)

Power density (S)

8 SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Uncontrolled Environment Controlled Environment

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 9

FOR TRAINING PURPOSES ONLY

r+ GPin + 43.65 5 + 1.16m

10 SYS03: BSS Database Application EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Beryllium health and safety precautions

EMOTOROLA LTD. 2000 SYS03: BSS Database Application 11