BSS08, Motorola

CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
Cellular Infrastructure Group
ISSUE 3 REVISION 1
BSS08 BSSC APPLICATIONS
FOR TRAINING PURPOSES ONLY
ISSUE 3 REVISION 1
ISSUE 3 REVISION 1
BSS08 BSSC Applications
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999 All Rights Reserved Printed in the U.K.
EMOTOROLA LTD. 2001
BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY
ISSUE 3 REVISION 1
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. EMOTOROLA LTD. 2001
ii
ISSUE 3 REVISION 1
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Artificial respiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Burns treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Do not ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toxic material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposure ceilings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power density measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inhalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skin contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eye contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disposal methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product life cycle implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
1 1 1 1 2 2 3 3 3 3 4 4 4 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 9 10 10 10 11 11 11 11 12 12 12 12 12 13 13 13 13 13 13
iii
ISSUE 3 REVISION 1
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 14 14 15 15 15 15 16 16 16 17 17 17
Chapter 1 GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Transeiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RX/TX Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Control Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Control software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC BTS Interconnection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder XCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder( XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding + Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling Interface Interconnections (BSC/RXCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder Basesite link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
i
11 12 14 14 14 14 14 14 16 16 18 18 18 18 110 110 112 114 116 116 116 116 118 118 118 120 120 120 120 122 124 126
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
Chapter 2 BSSC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Temperature Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet Internal Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU / RXU Shelf (upto Two Per cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Distribution Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Alarm Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Unit Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Unit (BSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Transcoder Unit (RXU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnect Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +27Vdc input power (ve earth) Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48/60Vdc input power (+ve earth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Power Supply Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic Processor (GPROC) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software for the GPROCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Based Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Based Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code Storage Facility Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Serial Interface (MSI2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Msi Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gclk Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
i
21 22 22 22 22 24 24 24 24 26 28 28 210 212 214 216 216 216 218 218 220 220 222 222 222 224 226 226 226 228 228 230 230 230 230 232 232 232 232 234 234 234 234
ISSUE 3 REVISION 1
Closed Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Extender Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder/GDP Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full-Rate Transcoder (XCDR) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR processor/DSP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic DSP Processor (GDP) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP Processor/DSP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Interface Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Alarm System (EAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf Internal Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
238 240 240 242 242 242 242 244 246 248 248 250 252
Chapter 3 RXCDR/BSC Digital Communication Buses . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Area Network Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola Cellular Advanced Processor (MCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCAP Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Division Multiplexed Bus (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport Switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM BUS Timeslot Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Bus Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Bus Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Highway Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Remote Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Expansion Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Watchdog Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
i
31 32 34 36 36 38 38 310 310 310 312 312 314 314 316 318 318 318 318 320 320 320 322 322 324 326 328 330 331
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport Switch Extender Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332 334 336
Chapter 4 BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software functional areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executive and Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Executive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Isolation and Memory Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexible Interprocess Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Man Machine Interface (MMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management Database Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Build Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Authority (CA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Authority Device States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Detection and Handling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message formats: Standard Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC OML defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR OML defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation in RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CP at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CP at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part L2 (MTP_L2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part L3/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
i
41 42 44 44 46 46 46 46 48 48 410 412 412 414 414 416 416 418 418 420 422 424 426 426 426 428 428 430 430 432 434 434 434 434 436 438 438 438 440 440 440 440 440
vii
ISSUE 3 REVISION 1
Call Processing at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Scheduler (CBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocation Manager (AM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 1 Protocol (Layer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Configuration and Fault Management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . Handover Detection and Power Control (HDPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Decision Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
442 442 442 442 442 444 446 446 448 448 450 452 454 456 458 460
Chapter 5 Appendix A Cabinet Interconnecting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1/T1 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport/Timeslot Switch Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport/Timeslot Switch Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport/Timeslot Switch Expansion (4 x KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW and GCLK Extension (2 Cabinets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Area Network Extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 52 52 52 54 54 56 56 58 58 510 510 512 514 516 518 518 520
Chapter 9 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A ......................................................................... B ......................................................................... C .........................................................................
viii
i
61 62 65 68
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X ......................................................................... Z .........................................................................
612 615 617 619 621 622 624 625 627 631 633 635 638 639 642 646 649 650 651 652 653
EMOTOROLA LTD. 2001
ix
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
General information
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals are intended to support the delivery of Technical Education only and are not intended to replace the use of Customer Product Documentation. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
About this manual
EMOTOROLA LTD. 2001
General information
ISSUE 3 REVISION 1
Cross references
Throughout this manual, cross references are made to the chapter numbers and section names. The section name cross references are printed bold in text. This manual is divided into uniquely identified and numbered chapters that, in turn, are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CTRL-c ALT-f | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return (Enter) key. The Return key is identified with the symbol on both the X terminal and the SPARCstation keyboards. The SPARCstation keyboard Return key is also identified with the word Return.
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
First aid in case of electric shock
First aid in case of electric shock

Warning
WARNING Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor.
Artificial respiration
In the event of an electric shock it may be necessary to carry out artificial respiration. Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration, carry out the following: 1. 2. 3. Do not attempt to remove clothing adhering to the burn. If help is available, or as soon as artificial respiration is no longer required, cover the wound with a dry dressing. Do not apply oil or grease in any form.
EMOTOROLA LTD. 2001
Reporting safety issues
ISSUE 3 REVISION 1
Reporting safety issues

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: 1. 2. 3. 4. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM MCSC +44 (0)1793 430040 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the MCSC.
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Warnings and cautions
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its calibration due date when testing Motorola base stations.
EMOTOROLA LTD. 2001
General warnings
ISSUE 3 REVISION 1
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
6
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
General warnings
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipments have to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Do not ...
... substitute parts or modify equipment. Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S Beryllium materials are absorbed into the body tissues through the skin, mouth, or a wound. The dust created by breakage of Beryllia is inhaled. Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
EMOTOROLA LTD. 2001
Human exposure to radio frequency energy (PCS1900 only)
ISSUE 3 REVISION 1

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

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

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

Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4p r W Pin
2
1930MHz +39.0 dBm (8 watts) 2.0dB PCL = +39.02.0 = +37.0dB (5watts) 16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+
GPin + 43.65 5 + 1.16m 4p W 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.
10
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Beryllium health and safety precautions

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 220 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.
EMOTOROLA LTD. 2001
11
ISSUE 3 REVISION 1
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.
12
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.
EMOTOROLA LTD. 2001
13
Devices sensitive to static
ISSUE 3 REVISION 1
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads shorted together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced observe the following precautions when handling the replacement: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Motorola GSM manual set

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are release dependent:
Category number
GSM-100-101 GSM-100-201 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-501 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721
Name
System Information: General Technical Description: OMC in a GSM System Technical Description: BSS Implementation Technical Description: BSS Command Reference Installation & Configuration: GSM System Configuration Installation & Configuration: BSS Optimization Maintenance Information: Alarm Handling at the OMC Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting Maintenance Information: GSM Statistics Application Software Release Notes: BSS/RXCDR
Catalogue number
68P02901W01 68P02901W31 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W26 68P02901W57 68P02901W51 68P02901W56 68P02901W72
Operating Information: GSM System Operation 68P02901W14 Technical Description: OMC Database Schema 68P02901W34
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems deploying Tandem S300 and 1475:
Category number
GSM-100-202 GSM-100-712
Name
Operating Information: OMC System Administration Software Release Notes: OMC System
Catalogue number
68P02901W13 68P02901W71
EMOTOROLA LTD. 2001
15
ISSUE 3 REVISION 1
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in the GSM manual set:
Category number
GSM-100-202 GSM-100-413 GSM-100-712
Name
Catalogue number
Operating Information: Scaleable OMC System 68P02901W19 Administration Installation & Configuration: Scaleable OMC Clean Install Software Release Notes: Scaleable OMC System 68P02901W47 68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category number
GSM-001-103 GSM-002-103 GSM-005-103 GSM-008-403
Name
System Information: BSS Equipment Planning System Information: DataGen System Information: Advance Operational Impact Installation & Configuration: Expert Adviser
Catalogue number
68P02900W21 68P02900W22 68P02900W25 68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not release dependent. The internal organization and makeup of service manual sets may vary, they may consist of from one to four separate manuals, but they can all be ordered using the overall catalogue number shown below:
Category number
GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-200-SERIES
Name
Service Manual: BTS Service Manual: BSC/RXCDR Service Manual: M-Cell2 Service Manual: M-Cell6 Service Manual: M-Cellcity Service Manual: M-Cellaccess ExCell4 Documentation Set ExCell6 Documentation Set TopCell Documentation Set M-Cellmicro Documentation Set
Catalogue number
68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02900W50 68P02900W70 68P02901W80 68P02901W90
EMOTOROLA LTD. 2001
16
ISSUE 3 REVISION 1
Category number
The category number is used to identify the type and level of a manual. For example, manuals with the category number GSM-100-2xx contain operating information.
Catalogue number
The Motorola 68P catalogue number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or Representative. Manuals are ordered using the catalogue number. Remember, specify the manual issue required by quoting the correct suffix letter.
EMOTOROLA LTD. 2001
17
ISSUE 3 REVISION 1
18
EMOTOROLA LTD. 2001
Chapter 1
GSM Network Components
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Chapter 1 GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Transeiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RX/TX Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Control Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM Control software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC BTS Interconnection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder XCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder( XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding + Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling Interface Interconnections (BSC/RXCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder Basesite link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 12 14 14 14 14 14 14 16 16 18 18 18 18 110 110 112 114 116 116 116 116 118 118 118 120 120 120 120 122 124 126 128
EMOTOROLA LTD. 2001
iii
ISSUE 3 REVISION 1
iv
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Objectives
Objectives
On completion of this section the student will be able to: S S Understand the generic function of the BSS entities. Identify the location and function of the: Radio Signalling Link (RSL) Message Transfer Link (MTL) Cell Broadcast Link (CBL) Transcoder Base Site Link (XBL) Operation and Maintenance Link (OML) S S Identify the interconnection requirements between a BSC-BTS and BSC-RXCDR. Understand the principles of infrastructure sharing.
EMOTOROLA LTD. 2001
11
ISSUE 3 REVISION 1

The following is a listing with a brief explanation of the major system components of the GSM System.
MS (Mobile Station)
The radio equipment and man-machine interface that a subscriber needs to access PLMN services.
BSS (Base Station System)

The fixed end of the radio interface that provides control and radio coverage functions for one or more sites and their associated mobile stations. The BSS includes:
BTS (Base Transceiver Station)

The BTS cabinet is capable of operating as a BTS or as a completely self-contained BSS with up to five RF carriers in a single cabinet. The BTS is discussed in greater detail later in this course.
BSC (Base Station Controller)

The BSC cabinet is only used at BSC sites and provides the required expansion capabilities to interface to the maximum number of remote BTSs allowed by the Motorola GSM BSS offering. The BSC can be a cabinet to itself or as a function at other cabinets. The BSC is discussed in greater detail later in this course.
XCDR (Transcoder Function)

Converts the signal from 64Kbs A-law to 13kbit/s GSM speech.
MSC (Mobile Switching Centre)

The telephone switching exchange for mobile originated or terminated subscriber traffic.
AUC (Authentication Centre)

Generates and stores authentication parameters for subscriber identification.
EIR (Equipment Identity Register)

The data base oriented processing network entity that contains centralized data base information for validating mobile stations based on their international mobile equipment identity.
VLR (Visitor Location Register)

The database oriented processing network entity that temporarily contains information for subscribers roaming in a given location area.
HLR (Home Location Register)

The database oriented processing network entity that contains the master data base of the subscribers to a PLMN.
EC (Echo Canceller)
Performs echo suppression for all voice circuits.
IWF (Interworking Function)

Performs data rate adaptation between Public Land Mobile Network (PLMN) and other existing land networks.
OMC (Operations and Maintenance Centre)

A central network entity that controls and monitors other network entities, including the quality of service provided by the network. Two OMCs are used OMC-R for the BSS monitoring and OMC-S for MSC monitoring.
NMC (Network Management Centre)

Performs hierarchical regionalized network management of the complete GSM system.
12
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
GSM Network Component

PST N
AUC HLR
IWF
EIR
EC
VLR M SC
VLR M SC
OM CS
NM C
OM CR
BSS
XCDR
BTS
XCD R BSC BTS
XCDR
BSS
BSC
BTS
BTS
EMOTOROLA LTD. 2001
13
Base Transeiver Station (BTS)
ISSUE 3 REVISION 1

The function of the Base Transceiver Station (BTS) is to provide the radio link to the mobile station (MS), to enable the user of the MS to initiate or receive and to maintain a telephone call. Each BTS can contain up to six cells, which define the area of the BTSs radio coverage. There are several Hardware / software entities which form together within the BTS to perform these tasks. These entities, considered generically, include the following:
RX/TX Modules
These provide the modulation/demodulation and the amplification of the Downlink (to the MS) and Uplink (from the MS). It also provides the raw data to measure the signal strength and quality of the two-way link.
Radio Control Software

This software controls the RX/TX module functionality. This includes setting the amplification, frequency and instructing the radio when to transmit. It also controls functions such as receive equalization, which improves signal quality and the formatting of the signal strength and quality information to be passed onto further entities.
GSM Control software

As the link between the BTS and MS needs to follow the GSM specifications it needs to be controlled by a dedicated software section. This software controls the layer 1 physical formatting of the air interface. This process includes configuring of the air interface links for the GSM TDMA format, formatting the data in each timeslot on that link, and also helps in controlling the paging and access grant messages. It processes the signal strength and quality information from the Radio control software, passing it to the BSC. This information is used to make sure the BTS-MS link is maintained at a good quality level or is the MS handed over to another cell/BTS.
Static Switch
This section switches the channels containing traffic from the Radio sections of the BTS to the terrestrial connections section, thus connecting the air interface channel with the rest of the network and eventually to other party. The static switch also routes any control information sent from entities further up in the network to the correct controlling software, usually the resident on the control processor. The static switch means that once it has been initialized it will keep the switching matrix the same all the time, thus keeping the same connections routed through.
Terrestrial Interface
The Terrestrial Interface provides the necessary connection to the network via a suitable link. This interface provides the correct formatting and impedance matching to the relevant physical link. The most common link types are 2.048Mbit/s E1 link or 1.544Mbit/s T1 link.
14
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Functions of a BTS
Synchronizing clock Site Control GSM Call Processing GSM Timeslot M onitoring Control Processor GSM Cntl s/w GSM Cntl s/w Terrestrial Interface Terrestrial Interface
Static Switch
Radio Cntl s/w RX/TX M odules
Radio Cntl s/w RX/TX M odules
EMOTOROLA LTD. 2001
15
Control Processor
ISSUE 3 REVISION 1
Control Processor
The Control Processor is the main processor of the site and can really be split into three main areas:
Site Control
This section is in control of the main processes and hardware to maintain the site integrity. The main functions include internal data bus control and initialization of the site at power up as well as reporting any faults or operational problems back to the controlling BSC further up in the network.
GSM Call Processing

Although the GSM control software looks after the link to Mobile station from a very basic level (i.e. layer 1 process implementing the physical air interface link). The GSM call processings role is that of call management. This process is used to interface GSM control messaging from the Base Station Controller to the GSM control software and to activate the allocated timeslot ready for the call to take place.
GSM Timeslot Monitoring

The GSM Timeslot Monitoring process manages the air interface timeslot usage, keeping a database of which timeslots are being used and for what purpose, recording the interference levels on each idle timeslot, prioritizing them for future use. Upon a request for a call, this process allocates the best available timeslot, dependant on interference level.
Synchronizing clock
As all the above processes need specific and accurate timing signals, each BTS will be equipped with a clock to make sure everything is synchronized.
16
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Control Processor
EMOTOROLA LTD. 2001
17
Base Station Controller (BSC)
ISSUE 3 REVISION 1

The function of the Base Station Controller (BSC) is to provide the overall control for the BSS. It controls and manages the associated BTSs, and interfaces with the Operations and Maintenance Centre (OMC) and the Mobile Switching Services Centre (MSC). The generic entities include the following:
Dynamic Switch
During the call set-up procedure the mobile is instructed to use a particular time slot on the air interface, to send and receive its traffic bursts. This channel allocation is done by the BSC GSM call processing software. However, the call in progress not only requires an air interface channel, but it will require a terrestrial circuit to connect it through to the MSC. This circuit allocation is done by the MSC. The function of the switch is to connect each BSC allocated channel to the correct MSC allocated circuit. This is done on a per call basis, therefore the switching has to be done on a dynamic basis, as there will be calls starting and finishing all the time and all requiring the separate connection. The switching matrix also lets the BSS perform handovers within a single BSS without involving the MSC.
The Terrestrial interface provides the necessary connection to the network via a suitable link. This interface provides the correct formatting and impedance matching to the relevant physical link. The most common link types are 2.048Mbit/s E1 link or 1.544Mbit/s T1 link.
Main Control Processor

This Processor is the main processor of the site and can really be split into three main areas:
Site Control
This section is in control of the main processes and hardware to maintain the site integrity. The main functions include internal data bus control and initialization of the site at power up. It will also look after the environmental aspects of the site, for example temperature levels.
Operations and Maintenance

As well as collecting any faults or operational problems from within the whole BSS it will also collect performance statistics and report them back to the controlling entity further up in the network (the OMC). These statistics are used to monitor the network elements, everything from the performance of the radios in maintaining the links to the mobiles, to the amount of processing power used.
Switch Manager
The switch manager will connect a mobile terrestrial circuit, allocated by the MSC for a particular call, to the Air interface channel allocated by the BSS. In this respect it is in control of the dynamic switch making sure that all calls and signaling are put through to the correct place be it a control processor or ultimately the Mobile Station. Information about which connections are to made is received form the GSM call processing software resident on the link control processors.
18
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Functions of a BSC
Terrestrial Interface Terrestrial Interface Terrestrial Interface Terrestrial Interface
Synchronizing clock Ops + M ain.
Site Control
M SC Link Processing
Dynamic Switch
Switch M anager
GSM Call Processing
GSM Call Processing Terrestrial Interface Terrestrial Interface Terrestrial Interface Terrestrial Interface
M ain Control Processor
Link Control Processor
Link Control Processo r
EMOTOROLA LTD. 2001
19
ISSUE 3 REVISION 1

The Link Control Processor maintains communications to each of the BTSs within the BSS and/or the MSC. In addition to this it provides the overall call management within the BSS, i.e. making sure calls are routed correctly and the calls are being processed by the best BTS/cell available to the mobile station. It is made up of two main functional areas:
GSM Call Processing

The BSCs GSM call processing is responsible for layer 3 call management operations. These include the connection signaling (e.g. messaging to a particular Mobile) and connectionless signaling (e.g. Messaging relating to global resets, load limiting, blocking). This messaging, via the Radio Signaling Link (RSL) connects the BSC call processing to the relevant GSM call processes on the BTSs within that BSS. Together both GSM call processing sections maintain the call for its duration ensuring the best link to the mobile is available. Note: This process controls the RSL.
MSC Link Processing

The MSC Link process, as the name suggests, controls the link back to the MSC from the BSC, the Message Transfer Link (MTL). This process deals with the layer 2 and layer 3 messaging protocols required to interface with the MSC. The MTL carries messages relating to call processing and operation status. Note: Generally at the Link Processor only one of the processes are active at any one time, either GSM call processing or MSC Link Processing.
Synchronizing clock
As all the above processes need specific and accurate timing signals each BTS will be equipped with a clock to make sure everything is synchronized.
110
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BTS-BSC Interconnection Requirement

0 1 2 3 SYNC RSL To synchronize link and provide error protection
To provide a signaling link from BSC to BTS E1 Linking BSC to BTS E1 =32 X 64kbit/s Traffic from/to the BSC link. 28 29 30 31 RTF 1 RTF 1 RTF 2 RTF 2 TCH is 16kbit/s 4 x TCH per Timeslot. 2 per Radio to give 8 tch from the air interface.
EMOTOROLA LTD. 2001
111
BSC BTS Interconnection Requirements
ISSUE 3 REVISION 1

The BSCBTS interconnection is provided by 64kbit/s timeslots on 2 Mbit/s links. These 2 Mbit/s links are interfaced at the BSC by using the Terrestrial Interface Boards. Terrestrial Interface Board can interface two independent 2 Mbit/s links with each 2 Mbit/s link, providing 31 usable 64 Kbit/s timeslots, The first timeslot being used by the interfaces to synchronize the link as well as provide basic error detection. To calculate the required number of 64 Kbit/s timeslots required between a BSC and BTS site, the site must be viewed as consisting of its own equipment and also the equipment at any sites that are connected to it. However, the amount of 64 Kbit/s timeslots to a BTS site must always be calculated so the interconnection feature can be planned. In the GSM transmission system, the speech data between the BSC and BTS is encoded into 16 Kbit/s channels using the GSM defined format. As the E1 link utilizes 64 Kbit/s timeslots, using Sub-rate multiplexing we can allocate upto 4 X 16 Kbit/s channels per time slot. Each active Radio will have, at a BTS site, an associated Receive / Transmit Function (RTF) to send the speech data back to the BSC and the rest of the network. Each RTF has data from 8 timeslots on the air interface therefore, it requires 2 x 64 Kbit/s timeslots on the E1 link to support its traffic data. To Support the call processing software at the BTS, the BSC must be able to send and receive control information to it. Also this link will have to support all other controlling aspects of the BSS including statistic collection and fault reporting. This Link is the Radio Signaling Link (RSL). Each RSL uses the LAPD formatted signaling to a site and requires 1 x 64 Kbit/s timeslot or 1 X 16kbit/s Channel. Each BTS site will require a minimum of 1 LAPD signaling channel.
112
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSC-BTS Link Configurations
Star Primary Path for BTS2

BTS7
BTS1
BTS2
BTS3
BTS4
BTS5
BTS6
Loop
Daisy Chain
EMOTOROLA LTD. 2001
113
Transcoder XCDR
ISSUE 3 REVISION 1
Transcoder XCDR
The Transcoder (XCDR) is required to convert the speech or data output from the MSC (64 Kbit/s PCM), into the form specified by GSM specifications for transmission over the air interface, that is, between the BSS and MS (13 Kbit/s). The 64 Kbit/s Pulse Code Modulation (PCM) circuits from the MSC, if transmitted on the air interface without modification, would occupy an excessive amount of radio bandwidth. This would use the available radio spectrum inefficiently. The required bandwidth is therefore reduced by processing the 64 Kbit/s circuits so that the amount of information required to transmit digitized voice falls to 13 Kbit/s. The 3 Kbit/s of TRAU data contains information to control the channel coders and call status information such as is DTX on or off during the call. The Transcoding function may be located at the MSC, BSC, or BTS. The TRAU data of 3 Kbit/s is added to the 13 Kbit/s channel leaving the Transcoding function to form a gross traffic channel of 16 Kbit/s which is transmitted over the terrestrial interfaces to the BTS. At the BTS the TRAU data is removed and the 13 Kbit/s is processed to form a gross rate of 22.8 Kbit/s for transmission over the air interface. For data transmissions the data is not Transcoded but data rate adapted from 9.6 Kbit/s (4.8 Kbit/s or 2.4 Kbit/s may also be used) up to a gross rate of 16 Kbit/s for transmission over the terrestrial interfaces. Again this 16 Kbit/s contains a 3 Kbit/s TRAU. As can be seen from the diagram opposite; although the reason for Transcoding was to reduce the data rate over the air interface, the loading of the terrestrial links is also reduced approximately on a 4:1 ratio.
114
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Transcoder XCDR
Transcoder Functionality
64 KBIT/S TS ON E1 64 KBIT/S TS ON E1
16
16 M TL 1
M N O P
I
M TL 1
E F G H
A B C D
S Y N C
J K L
BSC
16 KBIT/S TCH 2 bits per sub group
U
RESERVED RESERVED
Q R
S Y N C
RESERVED
RESERVED
M TL 2
M TL 2
T R A N S C O D E R
Y
C B A
N C
64 KBIT/S TCH 8 bits per timeslot

16
M SC
S Y N C
J
W S X T
EMOTOROLA LTD. 2001
115
Transcoder( XCDR)
ISSUE 3 REVISION 1
Transcoder( XCDR)
The function of the Transcoder is to interface the data link from the MSC to the data link to the mobile, via the BSS.
The Terrestrial interface provides the necessary connection to the network via a suitable link. This interface provides the correct formatting and impedance matching to the relevant physical link. The most common link types are 2.048Mbit/s E1 link or 1.544Mbit/s
Main Control Processor

This Processor is the main processor of the site and can really be split into three main areas:
Site Control
This section is in control of the main processes and hardware to maintain the site integrity. The main functions include internal data bus control and initialization of the site at power up. It will also look after the environmental aspects of the site, for example temperature levels.

This process collects any faults or operational problems from within the Transcoder site and report them back to the OMC. It will also report any errors on the Transcoding boards to the BSC to allow the BSC to inform the MSC to stop using the faulty circuits, this is because there are no signaling links between the Transcoder and the MSC. These statistics are used to monitor the network elements, everything from the performance of the radios in maintaining the links to the mobiles, to the amount of processing power used.
Synchronizing clock
As all the above processes need specific and accurate timing signals each RXCDR will be equipped with a clock to make sure everything is synchronized.
116
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Transcoder( XCDR)
Function of the Transcoder

MSC
Synchronizing clock
Terrestrial Interface + Transcoding
Ops + Sync M ain. c hroni lzing o Site c Control k
Static Switch
OMC
M ain Control Processor
EMOTOROLA LTD. 2001
117
Transcoding + Terrestrial Interface
ISSUE 3 REVISION 1

The data sent to the mobile from the MSC, which represents the voice of the user, is coded using the Pulse Coding Modulation techniques (PCM). The problem is that this PCM data is at the data rate of 64 Kbit/s, which is to high for the limited bandwidth of the air interface link to the mobile. To overcome this problem, the data is Transcoded. This Transcoding process reduces the amount of data sent to the mobile by the ratio of 4:1 (64 Kbit/s data in from the MSC converting it to 16kbit/s (13kibit/s data +3 Kbit/s signaling)). The output of the Transcoder can be considered as a model of the original PCM representation. The Transcoder also performs sub-rate multiplexing (multiplexing 4X16kbit/s Channels into one 64Kbit/s E1 channel) to increase the utilization of the links. The Transcoding board also contains the functionality of the terrestrial interface.
Transcoding Location
The location of the XCDR affects the overall cost of leased lines.
Transcoding at the BSC

If Transcoding takes place at the BSC, then the number of leased lines required to connect the BSC to the required BTS sites are reduced.
Remote Transcoding at the MSC

If Transcoding takes place remotely at the MSC, then the number of leased lines from the MSC (RXCDR) to the BSC are also reduced, thus providing an even greater saving.
Static Switch
This section Sub-rate switches the channels containing 64 Kbit/s traffic from the MSC links to Transcoded 16 Kbit/s BSC links and vica versa. The static switch also routes any control information sent from MSC to the correct BSC. The static switch means that once it has been initialized it will keep the switching matrix the same all the time, thus keeping the same connections routed through.
118
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
119
Signalling Interface Interconnections (BSC/RXCDR)
ISSUE 3 REVISION 1

To enable each of the network entities to function correctly they must be able to pass control and status messages to each other. This is done by using several signaling links. Each of the signaling interfaces uses a single 64 Kbit/s timeslot on the common 2 Mbit/s link carrier. Some interfaces support multiple timeslot configurations, i.e. more than one timeslot may be configured to support the signal flow.
Transcoder Basesite link (XBL)

This is an optional link for control and communications between the RXCDR and BSC. The XBL provides two-way communication between the master processor in the BSC and the master processor in the RXCDR. A dedicated 64 Kbit/s timeslot is used on the E1/T1 line between the RXCDR and the BSC. The XBL enables the RXCDR to report failed traffic circuits at the RXCDR to the BSC. The BSC performs different functions depending on the type of fault the RXCDR reports: If RXCDR traffic circuits fail, the BSC disables the circuits by sending blocking messages to the MSC. If there are internal RXCDR circuit faults, or faults that do not cause the loss of the serial communications link, the BSC blocks the affected traffic circuits. For example, if a XCDR board fails, the BSC blocks the 30 traffic channels associated with that XCDR board.
Operations and Maintenance Link (OML)

This link is for control and communications between the BSS and OMC. OML links from BSCs are nailed through the RXCDR, and OML links from the RXCDR are direct to the OMC. The OML uses the X.25 protocol. The OMC uses the OML to: S S S S S S Load software. Load configuration parameters. Send messages to, and receive messages from the BSS. Collect statistics from BSS Fault / event management Message Transfer Link (MTL)
This link exists between the BSC and MSC. The MTL uses the C7 signalling system including the BSS application part (BSSAP). This link provides all control information between the BSC MSC, MSC MS including: S S S Requests for initial connection. Any change in the attributes in call connection. Handling handovers.
Cell Broadcast Link (CBL)

This link exists between the BSC and the Cell Broadcast Centre (CBC). The CBL uses the LAPB/X25 protocol. The link is used to pass Short Message Service cell broadcast information from outside the GSM network to the BSC.
120
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Transcoder/BSC Interconnectivity
Sync 1x TFC 64 kbps 1x TFC 64 kbps
M SC
1 2
0 1 2
Sync 1x TFC 64 kbps 1x TFC 64 kbps 16 M TL BSC 1
OMC
OM L 1 RXCDR OM C Sync
(C7)
30 1x TFC 64 kbps
16
M TL BSC 1
31 1x TFC 64 kbps
(C7)
30 1x TFC 64 kbps 31 1x TFC 64 kbps 31
(X.25)
31 30 0 1 2 Sync X OM L B 1 L XBL 1 0
(X.25)
16
M TL BSC 1
B 30 4x TFC 16 kbps S C 31 4x TFC 16 kbps 1
CBC
0 1 2 Sync OM L 1 XBL
16
M TL BSC 1
(C7)
30 4x TFC 16 kbps 31 4x TFC 16 kbps
BSC 1
BSC 2
EMOTOROLA LTD. 2001
OM L Sync 2
121
Infrastructure Sharing
ISSUE 3 REVISION 1
Infrastructure sharing allows a single Network Operator with licenses in multiple frequency bands to support multi-band mobiles. By using infrastructure sharing the cost of implementing multi-band operation is reduced. A single RXCDR and BSC supports both 900 and 1800/1900 BTS sites in the same BSS. It is also allowed to locate 900 and 1800/1900 cabinets at the same BTS sites, however in this case the equipment types must be compatible. It is not allowed to mix an M-Cell6 cabinet and a BTS6 at the same site. Multi-band networking can also support single or multi-layer operation so that you could have a 900 Macro cell served by a 1800/1900 Micro underlay, alternatively a 900 Macro cell could operate alongside an 1800/1900 Macro cell. Within the multi-band network mobiles capable of supporting multi-band operation will be able to perform inter-cell handovers to a different frequency band eg, A cell operating at 900 can handover transparently to an 1800/1900 cell. However intra-cell multi-band handovers are not allowed. The implementation of multi-band networks requires careful planning and optimisation due to a number of factors. For example, the maturity of the network, the number of subscribers using dual band mobiles and the propagation differences between 900 and 1800/1900 frequencies. Since path loss is higher for 1800/1900 there will be a tendency for dual-band mobiles to favour the 900 cells. Therefore, it is important that database parameters are set correctly to control how multi-band operation is handled. For example, whether handovers are made to the best candidate regardless of band or to the best target in the preferred band selected by the operator. In general, Infrastructure Sharing offers: S S S S S S S S S Transparent handovers between different frequency bands Increased traffic capacity in a given area Single PLMN number and MNC for the network Single RXCDR and BSC for multi-band BSS Single-band mobiles are supported Multi-band operation controlled by database parameters Mixing of RF equipment within cabinets is not allowed No mixing of product types No band re-assignment on emergency calls
122
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Infrastructure Sharing M SC
Individual BTS sites Same BSC
One BTS site LAN Extension
DCS
GSM
PCS
GSM
EMOTOROLA LTD. 2001
123
Call Establishment
ISSUE 3 REVISION 1
Call Establishment
The following description covers the interprocess communication to place a mobile on a DCCH and have the mobile in communication with the MSC. 1. 2. 3. 4. The mobile accesses the system with a Random Access burst on the BCCH. The GSM Cntl Software passes the request onto the GSM Call Processing software (BTS) in the form of a Channel Required message. GSM Call processing software (BTS) asks the GSM timeslot monitoring software to assign a SDCCH channel and the GSM timeslot monitoring software responds. GSM Call processing software (BTS) tells the GSM Cntl Software which DCCH the mobile is to go to and the GSM Cntl Software activates that channel. When channel activated, the GSM Cntl Software informs the GSM Call Processing software (BTS). The GSM Call Processing software (BTS) then tells the mobile via the GSM Cntl Software on an Access Granted Channel, which DCCH the mobile is to move to. The mobile moves to the DCCH and establishes two way communication with its allocated BTS. The Mobile forwards CM Service Request, telling the GSM Call processing software (BTS) what the mobile wants to do. Is it Responding to a Page from the MSC? Doing a Location Update? IMSI Deregistration? Wanting to establish a call? Trying to salvage an established call? GSM Call Processing informs the mobile of power control and timing advance. The GSM Call Processing software forwards the CM service request up to the GSM Call Processing (BSC). The GSM Call Processing (BSC) then has to request the MSC to handle the call Via the MSC link Processing.
5. 6.
S S S S S 7. 8. 9.
124
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Call Establishment
Call Establishment BTS

GSM Call Processing
GSM Timeslot M onitoring
BSC
3 8
GSM Call Processing Switch M anager
9 2 4 1 5 6
M SC Link Processing To M SC
GSM
Cntl s/w
EMOTOROLA LTD. 2001
125
Traffic Channel Assignment
ISSUE 3 REVISION 1

The following text describes the inter-process communication for the assignment of a mobile from a DCCH to a traffic channel. This procedure assumes that all authentication has taken place on the DCCH. 1. 2. 3. 4. 5. 6. 7. 8. 9. The MSC sends a message to the GSM Call Processing (BSC) assigning the mobile a terrestrial circuit. The GSM Call Processing (BSC) sends an initiate assignment command to the GSM Call Processing (BTS) to assign a channel to the mobile. The GSM Call Processing (BTS) asks the GSM Timeslot Monitoring to assign Traffic a channel. The GSM Timeslot Monitoring responds with the channel. The GSM Call Processing (BTS) then asks the GSM Cntl Software to supply the timing information for the mobile concerned. The GSM Call Processing (BTS) then tells the GSM Cntl Software to activate the required Traffic Channel. The GSM Call Processing (BTS) then instructs the mobile via the GSM Cntl Software to move onto the new traffic channel. The mobile now moves to the new traffic channel and establishes signalling links. The GSM Call processing deactivates the signalling link on the SDCCH. The GSM CALL PROCESSING (BTS) then informs the GSM Call Processing (BSC) that mobile is on its new channel and signalling links have been established, and deactivates the SDCCH channel. The GSM Call Processing (BSC) then tells the Switch Manager to connect the radio channel to the terrestrial MSC circuit. The Switch Manager responds when complete. The GSM Call Processing (BSC) then tells the MSC that the mobile is on the new channel and that the radio channel has been connected to the MSC channel.
10.
11.
When this procedure is completed, it leaves the mobile on its new traffic channel and talking to the MSC.
126
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Traffic Channel Assignment BTS

GSM Timeslot M onitoring GSM Call
BSC
Processing 10
9 3
11 GSM Call Processing Switch M anager
5 4 6
7 8
1
GSM Cntl s/w
To M SC
EMOTOROLA LTD. 2001
127
Intra BSS Handover
ISSUE 3 REVISION 1
Intra BSS Handover

The following text describes the inter-process messages for an intra-BSS handover. The term source describes the cell from which the mobile is moving, whilst target describes the cell to which the mobile is moving. 1. 2. 3. The handover Detection and Power Control process decides whether a Handover is required. The GSM Cntl Software forwards the message to the GSM Call Processing (BSC) (Handover Evaluation Process). The GSM Call Processing (BSC) (Handover Evaluation Process) decides where the mobile is to move and sends a message to the GSM Timeslot Monitoring of the target cell requesting a channel. The GSM Timeslot Monitoring target then tells the GSM Call Processing (BTS) target that a channel has been assigned. The GSM Call Processing (BTS) target tells the GSM Cntl Software target to activate the channel. Target GSM Cntl Software activates the channel and sends a channel activation acknowledgement to target GSM Call Processing (BTS). Target GSM Call Processing (BTS) then informs GSM Call Processing (BSC) at the BSC of the channel allocation for the handover. The GSM Call Processing (BSC) then sends the GSM Call Processing (BTS) source the initiate handover; message which contains the channel information for the mobile. This information is then passed via the GSM Cntl Software source to the mobile. The mobile then moves to the new channel. The mobile is detected on the new channel by the GSM Cntl Software target and the signaling links are established between GSM Cntl Software target and the mobile. The GSM Call Processing (BTS) target is informed that the mobile has been detected on the new channel and signaling links have been established. The GSM Call Processing (BTS) target informs the GSM Call Processing (BSC) that the mobile has been detected and is completing the link establishment. This enables the GSM Call Processing (BSC) to inform the Switch Manager to change the traffic connection to the new BTS. GSM Call Processing (BTS) target then informs the GSM Call Processing (BSC) that the handover has been successful. The GSM Call Processing (BSC) then informs the MSC as to the new location of the mobile. The GSM Call Processing (BSC) then tells the GSM Call Processing (BTS) source to release the mobiles old radio channel.
4. 5.
6. 7.
8.
9. 10.
11.
12.
The handover process is now complete.
128
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Intra BSS Handover
Intra BSS Handover

GSM Timeslo M onitoring t
BTS Source
BSC
12 2 7 3
Switch M anager
10b
GSM Call Processing
GSM Call Processing
6 10a 11b 11a
GSM
Cntl s/w
BTS Target GSM Timeslot M onitoring
4
GSM Call Processing
5 8
GSM
To M SC
9
Cntl s/w
EMOTOROLA LTD. 2001
129
Intra BSS Handover
ISSUE 3 REVISION 1
130
EMOTOROLA LTD. 2001
Chapter 2
BSSC Cabinet
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Chapter 2 BSSC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Temperature Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet Internal Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU / RXU Shelf (upto Two Per cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Distribution Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Alarm Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSC Cabinet Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Unit Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Unit (BSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Transcoder Unit (RXU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnect Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +27Vdc input power (ve earth) Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48/60Vdc input power (+ve earth) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Power Supply Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic Processor (GPROC) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software for the GPROCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Based Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC Based Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code Storage Facility Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Serial Interface (MSI2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Msi Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gclk Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closed Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
i
21 22 22 22 22 24 24 24 24 26 28 28 210 212 214 216 216 216 218 218 220 220 222 222 222 224 226 226 226 228 228 230 230 230 230 232 232 232 232 234 234 234 234 238
iii
ISSUE 3 REVISION 1
Clock Extender Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder/GDP Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full-Rate Transcoder (XCDR) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR processor/DSP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic DSP Processor (GDP) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP Processor/DSP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Interface Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Alarm System (EAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf Internal Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
240 240 242 242 242 242 244 246 248 248 250 252
iv
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Objectives
Objectives
On completion of this section the student will be able to: S S S Identify the components of the BSSC cabinet. State the differences between the BSU and RXU. State the functions of the following BSSC components: Top panel Distribution alarm panel Circuit Breakers Base Station Unit shelf (BSU) Remote Transcoder Unit shelf Full size digital boards: GPROC, MSI, XCDR, GCLK, BTC, GDP Half size Boards: PIX, BBBX Power Supply Modules (IPSM/EPSM) S State the three modes of the GCLK and the function of each mode.
EMOTOROLA LTD. 2001
21
BSSC Cabinet
ISSUE 3 REVISION 1
BSSC Cabinet
Physical Description
The interior of a BSSC cabinet is only accessible through its front door, which is hinged from the left-hand side. The BSSC cabinet door has four air vents with grilles. From bottom to top, the vents are intake, exhaust, intake and exhaust. The top two vents provide air circulation to cool equipment located in the upper portion of the cabinet. The bottom two vents provide air circulation to cool equipment located in the lower portion of the cabinet. The intake vents are equipped with air filters All connections to a cabinet are made at the Interconnect panel on top of the cabinet. The panel also has feed through tubes for routing fibre optic inter-cabinet cables in and out of the cabinet. All cabinets are RF/EMI shielded.
Cabinet Dimensions
All cabinets have the following dimensions: Height Width Depth Depth 210 cm 71.2 cm 40.0 cm 41.5 cm (82.5 in) (28in) (15.75 in) (16.34 in)
(Improved cabinet)
Operating Temperature Range

00C to +500C.
22
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSSC Cabinet
BSSC Cabinet
Height: Width: Depth: Operating temperature Range 210 cm 71.2 cm 41.5 cm
All Connections Via Top Panel
0 to 50 _c
Cool Air Intake
Warm Air Exhaust Cool Air Intake
Warm Air Exhaust
EMOTOROLA LTD. 2001
23
BSSC Cabinet Internal Components
ISSUE 3 REVISION 1

The internal components of the BSSC cabinet include the following:
BSU / RXU Shelf (upto Two Per cabinet)

The function of these shelves is to house the main processing section of the BSC / RXCDR. It is made up from several different sections:
Half size modules

These cards are generally used for the shelf expansion / extension interfaces, including interfaces for the LAN, Data bus, synchronising clock.
Full size cards

These cards run the main BSC / RXCDR software. These software processes include the GSM call processing software, site control, operations and maintenance etc. Also included amongst the full size cards are the switching matrix and synchronising clock.
Power Supply Modules

The PSMs converts the input voltage to the correct voltage for the shelfs cards.
Cooling Fans
These re-circulate the air across the processing cards and PSMs to maintain a cool working temperature.
Power Distribution Board

This Board provides protection in the form of circuit breakers for the shelves against surges in the input voltage.
Distribution Alarm Board

This board provides a method of the monitoring and reporting any alarms generated from the BSSC cabinet
24
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

Power Distribution Distribution Alarm Board
Half Size Modules
Full Size Modules
BSU / RXU Shelf
Cooling Fans
EMOTOROLA LTD. 2001
25
BSSC Cabinet Configurations
ISSUE 3 REVISION 1

A BSSC cabinet configured as a BSC, is equipped with at least one BSU shelf assembly located in the lower portion of the cabinet, a second BSU may be located in the upper portion of the cabinet. Transcoding may be integrated into the BSU or a separate RXU shelf assembly can be located in the upper portion of the cabinet instead of a second BSU. A BSSC cabinet, configured as an RXCDR will be equipped with at least one RXU shelf assembly located in the lower portion of the cabinet, a second RXU may be located in the upper portion of the cabinet.
26
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSU [OPTIONAL]
RXU [OPTIONAL]
RXU [OPTIONAL]
BSU
BSU
RXU
EMOTOROLA LTD. 2001
27
Base Station Unit Shelf
ISSUE 3 REVISION 1

A shelf assembly consists of a backplane, two vertical slot module shelves and a three compartment shelf. The lower portion of the two vertical slot shelves hold full size digital modules; the upper portion of the shelf holds half size digital modules. (All digital modules, except for two Bus Termination Cards (BTC) and one Local Area Network Extender (LANX) module are optional). At the very bottom of the BSU shelf assembly, there are three compartments with slide-in mounting for plug-in power supply modules. The left hand compartment is for an optional redundant power supply module. The full size digital boards are located in the lower row of the Shelf at both the RXCDR and BSC cabinets. There are Two main types of shelf Base Station Unit (BSU) and Remote Transcoder Unit (RXU)
Base Station Unit (BSU)

Max numbers of Full Size Boards Contained within the BSU. 2 x Kiloport Switch (KSW)
12 x Multiport Serial Interface (MSI) 2 8 6 6 2 x Generic Clock (GCLK) x Generic Processor (GPROC) x Full-Rate Transcoder (XCDR) x Generic DSP Processor (GDP) x Bus Terminator Card (BTC)
Max numbers of Half Size Boards Contained within the BSU 18 x Kiloport Switch Extender (KSWX) 6 2 2 3 x Clock Extender (CLKX) x Local Area Network Extender (LANX) x Parallel Interface Extender (PIX) x Battery Backup Board (BBBX)
28
EMOTOROLA LTD. 2001
L28 AI 2 L27 AI 1 AI 0 L26 L25 L24 MS 0 KS 0 L23 L22 L21 L20 L19 L18 L17 DRI(M ) 5 XCDR 0 M SI 0 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 GCLK B KSW / TSW B L1 L0 BTC 1 U3 U2 U1 U0 GDP 1 XCDR 1 M SI 1 DRI(M ) 4 XCDR 2 M SI 2 GDP 3 XCDR 3 M SI 3 DRI(M ) 3 XCDR 4 M SI 4 GDP 5 XCDR 5 M SI 5 DRI(M ) 2 XCDR 6 M SI 6 GDP 7 XCDR 7 M SI 7 DRI(M ) 1 XCDR 8 M SI 8 GDP 9 XCDR 9 M SI 9 DRI(M ) 0 XCDR 10 M SI 10 GDP 11 XCDR 11 M SI 11 GCLK A L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 PIX 1 BBBX PIX 0 BBBX DRIX 5 DRIX 4 DRIX 3 DRIX 2 MS 2 DRIX 1 DRIX 0 EXP KSWX B0 EXP KSWX B1 EXP KSWX B2 CLKX A0 RM T KSWX B0 CLKX A1 RM T KSWX B1 CLKX A2 RM T KSWX B2 CLKX B0 RM T KSWX B3 CLKX B1 RM T KSWX B4 CLKX B2 LCL KSWX A LCL KSWX B GK 0 KS 1 MS 3 DR 0 DR 1 DR 2 DR 3 GRPOC 0 U18 PIX 2 BBBX MS 1 DR 4 GRPOC 1 U19 LAN B GRPOC 2 U20 LAN A GRPOC 3 U21 EXP KSWX A0 DR 5 GRPOC 4 U22 EXP KSWX A1 GRPOC 5 U23 EXP KSWX A2 GRPOC 6 U24 RM T KSWX A0 GRPOC 7 U25 RM T KSWX A1 SPARE RM T KSWX A2 U26 KSW / TSW A U27 RM T KSWX A3
ISSUE 3 REVISION 1
BSU Shelf Module Layout
EMOTOROLA LTD. 2001

BTC 0 U28 RM T KSWX A4 L5 L3
BSS08: BSSC Applications
29
Remote Transcoder Unit (RXU)
ISSUE 3 REVISION 1

Max numbers of Full Size Boards Contained within the RXU. 2 6 2 2 x Kiloport Switch (KSW) x Multiport Serial Interface (MSI) x Generic Clock (GCLK) x Generic Processor (GPROC)
16 x Full-Rate Transcoder (XCDR) 16 x Generic DSP Processor (GDP) 2 x Bus Terminator Card (BTC)
Max numbers of Half Size Boards Contained within the RXU 18 x Kiloport Switch Extender (KSWX) 6 2 2 3 x Clock Extender (CLKX) x Local Area Network Extender (LANX) x Parallel Interface Extender (PIX) x Battery Backup Board (BBBX)
210
EMOTOROLA LTD. 2001
L28 BTC 0 RM T KSWX A4 AI 2 RM T KSWX A3 AI 1 AI 0 RM T KSWX A2 RM T KSWX A1 RM T KSWX A0 MS 0 EXP KSWX A2 EXP KSWX A1 EXP KSWX A0 LAN A LAN B SPARE MS 1 SPARE PIX 0 PIX 1 Not used Not used U13 U12 U11 U10 U9 U8 U7 U6 U5 GCLK A U4 L3 GCLK B KSW / TSW B L1 L0 BTC 1 U3 U2 U1 U0 Not used MS 2 Not used Not used EXP KSWX B0 EXP KSWX B1 EXP KSWX B2 CLKX A0 RM T KSWX B0 CLKX A1 MS 3 RM T KSWX B1 CLKX A2 RM T KSWX B2 CLKX B0 RM T KSWX B3 CLKX B1 RM T KSWX B4 CLKX B2 LCL KSWX A LCL KSWX B GK 0 KS 1 KS 0 KSW / TSW A GRPOC 1 GRPOC 0 GDP 0 XCDR 0 GDP 1 XCDR 1 XCDR 2 XCDR 3 XCDR 4 XCDR 5 XCDR 6 XCDR 7 XCDR 8 XCDR 9 XCDR 10 XCDR 11 XCDR 12 XCDR 13 GDP 14 XCDR 14 M SI 0 GDP 14 XCDR 15 M SI 1 M SI 2 M SI 3 M SI 4 U14 U15 U16 U17 U18 U19 U20 U21 U22 U23 U24 U25 U26 U27 U28 L27 L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5
ISSUE 3 REVISION 1
RXU Shelf Module Layout
EMOTOROLA LTD. 2001
211
Interconnect Panel
ISSUE 3 REVISION 1
Interconnect Panel
The BSSC2 interconnect panel is located on top of the cabinet and provides connections for DC input power, El/T1 line interconnect modules, customer defined alarm equipment input/output, +27 V DC power/alarm for external receiver multicoupler and +27 V battery back-up input for DRAM. This panel also has feed through-tubes for routing fibre optic inter-cabinet cables into and out of the cabinet.
Note:
The feed-through tubes do not compromise the EMC screening of the cabinet, as they are operated below their waveguide cut-off frequency. The El/T1 interconnection modules provide impedance matching between the El/T1 links and the BSU/RXU backplanes. Each contains connections for 6 input and 6 output lines. These modules can be: S S Type 43 (T43) for 75 ohm coaxial El lines. Balanced Line Interconnect Boards (BIB) for 120 ohm balanced El and T1 lines.
212
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Interconnect Panel
BSSC Cabinet Interconnect Panel
MS4-MS7 CONNECTS E1 LINKS TO TOP CAGE
Fibre cable feedthrough tube
External alarms
PIX PIX
1 0
M S4 T43
or
M S5 T43
or
M S6 T43 BIB 6 M S2 T43

or or
M S7 T43
or
BIB M S T43
or
BIB M S1 T43
or
BIB M S3 T43
or
BIB 0
BIB
BIB
BIB
G c l k 0
B B B X
Vin
0V MS0-MS3 CONNECTS E1 LINKS TO BOTTOM CAGE
S S
Type 43 (T43) 75 coaxial links Balanced line interconnect boards (BIB) 120 balanced links
EMOTOROLA LTD. 2001
213
Distribution Alarm Board (DAB)
ISSUE 3 REVISION 1

The DAB distributes +27vdc to units within the cabinet through 25 fuses, monitors alarm lines and passes individual alarms to the GPROC. There are two bi-coloured LED mounted on the DAB, which indicates a DAB and / or cabinet based fault. The DAB processes operational failure signals from: S S Ruptured fuses The Fan stall sense line from each cooling fan.
214
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Distribution Alarm Boar

PC 3 to Backplane of cages (serial Bus) Switch 2 LED D43 LED D8 Circuit breaker monitor lines Fuses F4-9 F21-26 LEDs PC 6 Power to external equipment
PC 4 BBBX for GPROCS
Switch 1
PC 5 Power to fans LEDs
LEDs
PC 2 to Backplane of cages (serial Bus)
Fuses F10-15 F18-20 F27-30
EMOTOROLA LTD. 2001
215
Power Distribution
ISSUE 3 REVISION 1
Power Distribution
The Power Distribution Unit (PDU) is mounted on the top shelf of the cabinet and is accessible from the front of the cabinet when the door is open. The PDU, which distributes dc power throughout the cabinet and provides an alarm interface, consists of a circuit breaker panel containing a maximum of 10 dc circuit breakers and the Distribution Alarm Board (DAB). The BSSC cabinet is delivered in one of two forms: S or S 48/60Vdc input power (+ve earth) +27Vdc input power (ve earth ) Cabinet
+27Vdc input power (ve earth) Cabinet

DC input power applied at the interconnection panel, on top of the cabinet, is routed to the VIN bus bar and the (GND) bus bar in the PDU. A second bus bar, operating at +27 V, obtains power By bus bar link in the cabinet.
Circuit Breakers
Power is distributed to units within the cabinet through circuit breakers: S S S CB1, at 30 A, provides +27 V power to the DAB. CB8 to CB1 0, provide +27 V to the EPSMs in the bottom shelf. CB 5 to CB7, provide +27 V to the EPSMs in the top shelf.
216
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Power Distribution
Power Distribution +27vDC input (-ve earth)

Vin Bus Top Panel BBBX PC3 PC4 PC2 CB10 CB1
AI 0
0v PC5
DAB
27v bus
27v
To Top cage PSUs
BBBX
AI 1 AI 2
Bottom BSU/RXU Cage
EPSM
EPSM
EPSM
To Top Cage Fans
EMOTOROLA LTD. 2001
217
48/60Vdc input power (+ve earth)
ISSUE 3 REVISION 1

DC input power applied at the interconnection panel, on top of the cabinet, is routed to the VIN bus bar and the (GND) bus bar in the PDU. A second bus bar, operating at +27 V, obtains power from the Integrated Power Supply Modules (IPSMs) in the lower Base Station Unit (BSU) by bus bar link in the cabinet.
Circuit Breakers
Power is distributed to units within the cabinet through circuit breakers: S S S CB1, at 30 A, provides +27 Vdc power to the DAB. CB8 to CB1 0, 48/60 Vdc to the IPSMs in the bottom shelf. CB 5 to CB7, provide 48/60 Vdc to the EPSMs in the top shelf.
218
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Power Distribution -48/-60v input (-ve earth)

Vin Bus 27v bus Top Panel BBBX PC3 PC4 PC2 0v PC5 DAB
CB10
CB1
27v
To Top cage PSUs
AI 0
BBBX
AI 1 AI 2
Bottom BSU/RXU Cage
IPSM
IPSM
IPSM
To Top Cage Fans
EMOTOROLA LTD. 2001
219
Integrated Power Supply Modules
ISSUE 3 REVISION 1

The DC input power 48 DC/60V DC is applied via the associated circuit breakers at the top of the cabinet and BSU backplane to the IPSM input. The 48V/60V input is then converted to: S S S S +5.1V + 2% @ 85A (Full load current) +12V + 5% @ 2.5 A (Full load current) 12V + 5% @ 2.5 A (Full load current) +27.5V+5%
The regulated DC outputs are applied via the backplane to power the BSU modules. The +5\4 12V and +12V output are sensed to provide output voltage regulation, overvoltage protection and overcurrent protection. For additional IPSM protection the cabinet circuit breaker will trip if the input DC polarity is reversed and if the ambient temperature of the device exceeds a safe level then an alarm indication will be sent to the controlling processor via the serial bus and the device will be shut down.
EPSM
For+27V DC supplied cabinets an EPSM will be used. The EPSM functions the same as the IPSM, that is DC/DC converts the input voltage to the required voltages for the BSU/RXU, but does not supply the +27V DC to the FANs/DAB as this is supplied via the VIN bus bar directly from the primary input.
220
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

Integrated PSMs S S Input Voltage -48/-60 VDC Output to digital cage +5.1 V + 2% @ 85 A +12 V + 5% @ 2.5 A -12 V + 5% @ 2.5 A S S S S S S S Output to Fans/DAB +27.5 V + 5% Output Voltage Regulation Over Voltage/Current Protection Polarity Reversal Protection Ambient Temperature Protection
Enhanced PSMs Input Voltage +27 VDC Output to digital cage +5.1 V + 2% @ 85 A +12 V + 5% @ 2.5 A -12 V + 5% @ 2.5 A S S S S Output Voltage Regulation Over Voltage/Current Protection Polarity Reversal Protection Ambient Temperature Protection
EMOTOROLA LTD. 2001
221
Generic Processor (GPROC) Board
ISSUE 3 REVISION 1

Introduction
The GPROC 1 has a 25 MHz Motorola 68030 processor whose function is dependent on the software loaded. This also provides a memory management unit, which supports task and data isolation methods. GPROC2 is a new version of GPROC, available from GSR2 onwards. It has a Motorola 68040 processor working at 33MHz and also increased DRAM capacity. At GSR2 it is interchangeable with GPROCs and can be used on the same LAN. However, it assumes greater significance from GSR3 onwards when it will be used to handle a greater number of signalling links at the BSC and so increases the capacity. The increased DRAM capacity also removes the requirement to have a GPROC dedicated as a code storage facility processor at the BSC if M-CelI BTS sites are supported. Fault tolerance is enhanced by these redundant interfaces, by an on-board watchdog timer, and by power-fail detection devices. The GPROCs, like all BSS boards, may be removed or inserted while the cage is powered and operational. The parallel port outputs signals to the front panel LEDs and receives input signals (via the register ports) from the backplane containing information, such as shelf ID, slot ID, backplane type, backplane revision level, etc. The module runs on-board self-diagnostics during initial power-up. These on-board self-diagnostics can also be operated under control of the maintenance TTY The maintenance port is configured to meet the requirements of the EIA RS232c and CCITT V.24 specifications.
Interface Links
The board also contains interfaces for: 1. A 16 Mbit/s IEEE 802.5 (token ring) LAN, which provides communication between GPROCs so that Call processing software can pass data to each other as well as monitor / report messages to each other. TDM highway, which gives access up to 16 x, E1/T1 interfaces. This handles all the communication the GPROC has to do to the external entities such as the OMC, MSC, RXCDR, BTS etc using the Links RSL, OML, XBL, MTL. Serial interfaces are provided which may be used for asynchronous or synchronous communications. One port is available on the front panel for connection of a maintenance TTY or personal computer. The TTY can be used for software monitoring and control while performing maintenance and or trouble shooting. A serial interface is used to communicate with the half size cards to issue control messages and to monitor status information. MCAP bus providing operational control of the full-size cards such as GCLKs, MSIs, KSWs etc. The MCAP Bus is used to download on initialisation and report alarm information.
2.
3.
4.
222
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Generic Processor
Reset Switch WATCHDOG TIM ERS TIM ING CONTROL L.E.D.s LAPD PROC. LAN PROCS LAN INTF A B Backplane info 5v to dram 5v power Clock ref. From GCLK 16.38mhz 6.12s 60ms 125ms Comms to other GPROCS Comms with non GPROC full size cards To receive signaling from the E1 links. [RSL OM L XBL M TL] Comms with half size cards and Cab alarms
Data bus
M AIN PROCESSOR
M CAP INTF. TDM INTF
A B
M EM ORY:DRAM NVRAM EPROM SERIAL BUS CONTROLLER
A B
TTY PORT
A B
S S S S S S S S S
Backplane connector
Support of the MSC signaling links (MTLCCITT SS#7) Support of the layer 3 call processing functions Support of the BSC to BTS signalling links (RSLLAPD) BSC control functions (fault management, switch control...) Support of the OMC-R interface (OMLX.25) Support of the CBC interface (CBLX.25) Support of the RXCDR interface (XBLLAPD) GPROC 16meg DRAM GPROC2 upto 64meg DRAM (no need for CSFP for M-Cell objects)
EMOTOROLA LTD. 2001
223
ISSUE 3 REVISION 1
GPROC Memory Usage

Each GPROC 2 is equipped with upto 64Mbytes of DRAM which holds the downloaded operating code and the CM database. The DRAM can have a battery back-up as long as the module remains in the cage. The GPROC 1 has only 16 Mbytes on DRAM for the same purpose. The GPROC has 1Meg of downloadable flash EPROM containing the bootstrap loading code. The new bootstrap software is downloaded as a new code object and broadcast to all GPROCs. The processor then determines if the bootstrap code object, held in the DRAM, is the same as that in the flash EPROM. If so, then no further action is required. If not, then the version held in the flash EPROMs is replaced with that held in the DRAM. A visual indication notifies the technician operating on site that a bootstrap reprogramming cycle is in progress. Both the red and green GPROC front panel LEDs flash on and off continuously while the bootstrap is erased and reprogrammed. An MMI command is available to verify that the bootstrap programming has been successful. If the technician operates from the OMC, the GPROC(s) are monitored with printed messages via the rlogin capability from the OMC. 32 kbytes of Non Volatile RAM is available on the GPROC for storing important data such as the OMC DTE addresses required to support the Operations and Maintenance Link (OML) between the BSC and OMC.
224
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
225
Software for the GPROCs
ISSUE 3 REVISION 1

The GPROC module is the building block that provides the processing platform for the BSS software. Every GPROC is identical from a hardware standpoint. The function of a GPROC is dependent on the software loaded into it. The set of tasks that a GPROC is assigned to perform depends upon the configuration and capacity required.
GPROC Based Devices

The GPROC device is the hardware based on which the GSM BSS software operates. The GPROC device is further divided into smaller categories based on the functionality implemented by the GPROC device. Each of the GPROC categories will fall into two groups: hard and soft devices. The following definitions apply: S S Hard device a GPROC device which has a pre-defined and static functionality. Soft device a GPROC device whose functionality is dynamically assigned.
The GPROC device may be divided into several categories based on functionality. The GPROC categories are listed below. Also shown below is the hard/soft device group to which each category belongs. S S S BSP (Base Site Processor) This GPROC device is a hard device and is the main controller and master GPROC at the BSS/BSC/RXCDR. CSFP (Code Storage Facility Processor) This GPROC device is a hard device and is used to enhance code loading tasks at the BSS. GPROC (Generic processor) This GPROC device is a soft device and its actual functionality is determined by the GPROC function to which it is assigned. GPROCs in this category are placed in a pool for assignment to GPROC functions.
GPROC Based Functions

Pool GPROCs are assigned functionality via GPROC functions. The following GPROC functions exist: S S LCF (Link Control Function) Provides support for the MSCBSS/BSC and the BSS/BSCBTS interfaces. OMF (Operation and Maintenance Function) Used to support the OMCRBSS interface.
226
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Software for GPROCs
Terrestrial Interface Terrestrial Interface
GPROC Ops + M ain. Site Control Switch M anager M ain Control Processor
GPROC M SC Link Processing GSM Call Processing Link Control Processor
GPROC Stats Collection
GPROC New software Old Software
GPROC No immediate function
Storage Processor
Pool Processor
Base Site Processor. Main Control of site defined to a slot position
Operations and Maintenance function. Controls stats collection from BTSs
Pool Processor. Used as redundant Processor in case of failure.
Link Control function. Controls links to/from BSC and call processing.
Code Storage Facility Processor. Stores additional versions of BSC software to assist in upgrading.
EMOTOROLA LTD. 2001
227
Operations and control Processor
Dynamic Switch
Synchronizing clock
Code Storage Facility Processor
ISSUE 3 REVISION 1

The Code Storage Facility Processor (CSFP) is a GPROC device which facilitates the propagation of new software instances with reduced system downtime. A software instance is a complete set of software and firmware objects including the database object. In the past, propagating new software required the BSS to be unavailable for considerable periods of time. The majority of the down time was due to link throughput and network topology limitations. The CSFP reduces the time when the system is unavailable by downloading the software instance while the system is online. After the software has been populated to all the desired sites, the BSS is reset for activation of the new software instance. Since the new software instance exists locally link throughput and network topology is no longer the limiting factor and network outage time is reduced. i.e., The new software instance is propagated to all GPROCs at each site via the 16 Mbit/s LAN rather that the 64 Kbit/s OML link. In addition to migrating to new software loads, the CSFP feature also provides the ability to fall back easily and quickly to an existing software instance. As described above, a new software instance is dispersed to all the CSFPs in the BSS. Then, the network is reset. After reset, all non-CSFP GPROCs begin executing the new software load, while the CSFP optionally retains the old software load. In other words, the CSFP and the GPROCs exchange software loads.
Operation
Performing a CSFP download, with or without fallback, is a four step procedure. These steps execute in the order listed. S S S S Configure the BSS with CSFPs Download the new software instance to the equipped CSFPs Reset the BSS network, propagate the CSFP objects locally and optionally save the existing objects Unconfigure the CSFPs (optional)
Each of these four steps is independent of the others, and each step is a self contained procedure. The planning, execution and error handling of one step does not influence the others. In other words, the BSS may be configured with CSFPs one day, downloaded the next, and the new objects populated on the third day. The fallback capability, managed and defined per site, is enabled by equipping CSFPs in the new database. Sites which contain a CSFP both before reset and after reset automatically contain fallback CSFPs. The operational procedures are identical with and without fallback.
228
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Code Storage Facility (CSFP)

OM C 4. Unconfigure the BSS with CSFP
2. Download new Software to CSFP CLOCK
NEW CODE OPERATIONAL CODE M ASTER GPROC OLD CODE CSFP
3. Code Swap so Operational code is replaced with new code and old code is stored on CSFP
1. Configure the BSS with CSFP
Downloading of new software codes

S Saving of downtime S 4 step procedure S GPROC at every site
EMOTOROLA LTD. 2001
229
Multiple Serial Interface (MSI2)
ISSUE 3 REVISION 1

Introduction
The Multiple Serial Interface (MSI2) board interfaces two El/T1 link circuits to the TDM switch highway. A main processor performs the control functions required on this board. The MSI2 provides surge protection, clock extraction, jitter attenuation, frame alignment, and support for the procedures required to synchronise multiple BSCs within a network. The maximum MSI2 per BSC is 24. Each MSI has the capability of interfacing up to two 2 Mbit/s links using two ports, 0 and 1. To identify an El link on an MSI board each port is referred to as an MMS. So on MSI 000 there will be a possibility of having two MMSs; MMS 000 will refer to port 0 MMS 010 will refer to port 1.
Processor Section
A Motorola MC68000 DSP operating at 8 MHz is used to control the TDM interface and the multiplexer that selects which of the two extracted clocks to be routed to GCLKs via the backplane. The DSP communicates with the controlling GPROC via the MCAP bus to report extracted clock failures, frame alignment errors, bipolar violation, CRC4 errors and transmit/receive errors. The EPROM consists of 128 Kbytes of bootstrap program code which will, on power up, request the GPROC to download the MSIs operating code via the MCAP bus. The operating code is loaded into the SRAM and is permanently saved in EEPROM.
Msi Line Interface

The Impedance Matching section performs impedance matching and provides secondary voltage surge protection to MSI from high voltage transients such as lightning strikes, which may come down the El links. The received PCM serial data is applied to a level converter, which converts the data from bi-polar to TTL level unipolar, within the E1 interface section. The data is then applied to the loopback multiplexer, which can support diagnostic functions, distance measuring or for when the drop and insert feature is being implemented. The received data is then HDB3 and CRC4 decoded as per CCITT recommendation G704 for digital multiplexer equipment and sent to the TDM interface section. The TDM interface converts the data from serial to parallel and the two receive data streams are interleaved on to the TDM Highway in groups of two and are spaced out by 32 timeslots. The interleaving process enables each 64 kbps timeslots to be alternately mapped onto the TDM Highway requiring a total of 64 TDM Highway timeslots. Similarly data received from the TDM highway is parallel to serial converted, CRC4 and HDB3 encoded and fed out on the El link via impedance matching circuitry.
230
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Multiple Serial Interface

L.E.D.S M EM ORY M AIN PROCESSOR Reset Switch CLOCK EXTRACTION LOOPBACK M ULTIPLEXER DATA ENCODER TTY test port M CAP INTF. A B Comms to GPROCS
DATA DECODER
TDM INTF E1 INTF TDM INTF
A B
TDM Switchbound Highway A+B Rx Tx Span 1
A B
TDM Outbound Highway A+B Clock ref. To GCLK
CLOCK M ULTIPLEXER CLOCK EXTRACTION LOOPBACK M ULTIPLEXER DATA ENCODER DATA DECODER TDM INTF E1 INTF TDM A B A B
TDM Switchbound Highway A+B Rx Tx Span 2
INTF
TDM Outbound Highway a+b
S S S S
2 X E1 / T1 link interfaces. Serial (E1 / T1) to parallel (TDM highway) conversion. Clock Extraction from link for GCLK. 12 per BSC.
EMOTOROLA LTD. 2001
231
Generic Clock (GCLK)
ISSUE 3 REVISION 1

Introduction
The Generic Clock Board (GCLK) generates all timing reference signals required at the BSS site. The master TDM clock will be normally synthesised from the on-board reference oscillator, 16.384Mhz, which may be phase locked to the recovered clock from the selected 2 Mbps circuit or may free run. The GCLK board provides 0.05 ppm reference stability as specified by GSM. The maximum GCLK per site is two.
Gclk Functionality
The GCLK generates all timing reference signals on a site basis which include: S S S S 16.384 MHz TDM clock 125 s TDM Highway frame reference 60 ms Synchronisation reference 6.12 second super frame counter
The GCLK can be locked to the recovered clock of a selected 2 Mbit/s link provided via a MSI/XCDR module. In the event of loss of recovered clock the GCLK is able to free run providing better than 0.05 ppm reference stability. The module is able to perform self-diagnostics capable of detecting on board faults and in response select a redundant GCLK if available. Each clock pair operate in a master/slave configuration with the slaves output being synchronised to the master. If an error is detected the clock control circuitry reverses the master/slave status. Fault conditions are reported to the controlling GPROC via the MCAP bus. The reference oscillator uses a phase lock loop (PLL) and a frequency multiplier to synthesise 16.384 MHz from a 2 Mbit/s Links reference. The PLL consists of a digital phase detector, a loop filter, a voltage controlled ovenised crystal oscillator and a divide by eight loop divider. In the event of loss of the 2 Mbit/s link reference the oscillator can free run stability being maintained by the ovenised crystal oscillator. The output of each reference counter is routed to a multiplexer which is used to switch the reference outputs from the master or slave GCLK. The output of each reference counter is also routed to the reference encoder which encodes all of the reference signals together and are then routed together to a clock extender so that they can be optically transmitted to all cages at the site. The reference fail detect monitors the 2 Mbit/s link reference and failures are reported to the clock control/alarm logic. In the event of reference failure the GCLK may select the secondary reference or may allow the GCLK to free run. In either case an alarm is reported to the controlling GPROC via the MCAP bus. Buffered test ports are available on the front of the GCLK for test and measurement of the input reference and output clock reference signals.
GCLK Equipage
The maximum number of GCLKs in redundancy mode at a BSC/RXCDR site is two, both being located in the same digital cage. Clock signals from a GCLK can be distributed to each cage at a site via CLKX modules.
232
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Generic Clock
6.12S 60ms 125ms Encoded clock 16.38M hz 6.12S 60ms 125ms Encoded clock To CLKX
16.38M hz
ED.s M ASTER / SLAVE SELECTION + OUTPUT ENABLE
From mate GCLK
REF. ENCODER
To cage Backplane
125ms REFERENCE COUNTER 60ms REFERENCE COUNTER 6.12S REFERENCE COUNTER REFERENCE OSCILLATOR CLOCK CONTROL LOGIC / ALARM LOGIC U X REF. FAIL DETECT M CAP INTF. A B M
125ms To mate GCLK 60ms To mate GCLK
6.12S To mate GCLK
16.384M hz To mate GCLK Extracted ref. A+B
M CAP buses Comms to GPROCS
S All timing reference signals for site. S On board reference oscillator. S Free running mode (not referenced to external source - low maintenance). S Phase locked mode (referenced to external source - low maintenance). S Accuracy 0.05 ppm (free run mode). S 2 per site for redundancy.
EMOTOROLA LTD. 2001
233
GCLK Operating Modes
ISSUE 3 REVISION 1

There are four modes that the GCLK board can operate in, these are: Free Run, Hold Frequency, Set Frequency and Closed loop. Each mode is explained below using the diagram opposite.
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.O5ppm.
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 a GPROC to set the DAC to control the output of the OXCO during loss of the El/T1reference signal (this is after the transitional Hold Frequency mode). One GPROC in the master cage will be responsible for the GCLK operation and will monitor the input to the DAC during Closed Loop operation. In the event of reference signal failure the GPROC will calculate a best value to set the DAC to maintain the accuracy of the OXCO. This value is called the Long Term Average and is calculated from samples read from the GCLK via the MCAP interface. A sample is taken every 30 minutes, up to a total of 48 samples representing the previous 24 hours. When the 49th sample is read it over-writes the 1st sample to maintain a total of 48.
234
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

16.384 M Hz Feedback output Phase signal Detector LPF F in Input signal 2.048 M Hz OS.IN LOCK DET V in Conv.CS 16.384 M Hz Vref Calibration Adjust 256 KHz 8 EN 80 (Hex) Buffer OE Read Freq Latch OE Set Freq Latch OE
ADC
DAC
OXCO
Reference Fail Detect
Control
GPROC (M CP data bus)
EMOTOROLA LTD. 2001
235
ISSUE 3 REVISION 1
236
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
GCLK Synchronisation Configuration

E1 LINKS
GCLK
M SI PRIORITY 250
M SI PRIORITY 251
M SI PRIORITY 253
GPROC Ops + M ain. Site Control Switch M anager M ain Control Processor
GPROC M SC Link Processing GSM Call Processing Link Control Processor M SI PRIORITY 0
Dynamic Switch
M SI PRIORITY 0
M SI PRIORITY 0
E1 LINKS
To use the E1 as a reference it must have a priority between 1(low) and 255(high) priority. 0 the extracted clock is not used
M SC
RXCDR
BSC
BTS
BTS
All entities must be synchronised with a higher level
EMOTOROLA LTD. 2001
237
Closed Loop
ISSUE 3 REVISION 1
Closed Loop
The Closed Loop Mode is provided to eliminate frame slips due to reference clock failure and/or OXCO ageing. In this mode the 16.384MHz clock frequency will be exactly eight times the mean frequency of the incoming reference clock. The reference clock source must be accurate to +/0.01 ppm. When the GCLK is frequency locked the calibration and ageing of the OXCO can be monitored using the LTA. If the LTA is outside a database predefined limit then an alarm will be raised, typically this alarm will allow the GCLK to operate for another 30 days before re-calibration is required (10% upper/lower values of LTA, as defined in the database). When in closed loop mode the loop is immune to line breaks of less than 80 microseconds. Due to this GCLK calibration will take place every 37 years. Within the closed loop mode there are two sub modes or states: S S Acquiring Frequency Lock State 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 El/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 dependent 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).
238
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Closed Loop

Unlock Bit
+ 0
C
Tim e A= Acquiring Frequency Lock State B= Frequency Lock State C= Closed Loop
EMOTOROLA LTD. 2001
239
Clock Extender Board
ISSUE 3 REVISION 1

Introduction
The Clock Extender board (CLKX) is a half size board which provides the extension of the system clock and reference signals from the Generic Clock (GCLK) to the Base Station System Controller Unit (BSU) shelves via fibre optics. The GCLK board generates the system clock and references which are multiplexed into one signal to reduce the number of interconnections between shelves. The diagram depicts the CLKXs role in the system clock distribution. The CLKX receives the encoded clock line from the GCLK and optically extends the encoded clock to six local Kiloport Switch Extenders (KSWXs) located in different shelves. The KSWX in shelf #1 ensures that the time delay is the same for all cages, therefore maintaining site synchronisation. The CLKX uses the Base Station System (BSS) serial bus to report its board ID and revision level to the Generic Processor (GPROC).
BACKPLANE CONNECTOR
FIBRE OPTIC TRANSMITTEROPFIBRE TIC TRANSMITTEROPFIBRE TIC TRANSMITTEROPFIBRE TIC TRANSMITTEROPFIBRE TIC TRANSMITTEROPFIBRE TIC TRANSMITBSS SERIAL INTERFACE TER
REGISTERS
DRIVER CIRCUITRY DRIVER CIRCUITRY DRIVER CIRCUITRY DRIVER CIRCUITRY DRIVER CIRCUITRY DRIVER CIRCUITRY
BSS SERIAL BUS A
ENCODED CLOCK / REFERENCES (FROM GCLK)
1. REVISION LEVEL 2. BOARD TYPE 3. SLOT ID
BSS SERIAL BUS B
240
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
GCLK Distribution
shelf #1 shelf #2 16 MHz 6.12 S 125 mS 60 mS
GCLK
Encoded Clock
CLKX
KSWXL
BACKPLANE 16 MHz 6.12 S KSWX L 125 mS 60 mS
BACKPLANE
shelf #3 16 MHz 6.12 S 125 mS KSWXL 60 mS BACKPLANE
shelf #4 16 6.12 MHz 125 S 60 mS mS BACKPLANE
KSWXL
L KSWX in the local mode
fibre optic cable
EMOTOROLA LTD. 2001
241
Transcoder/GDP Board
ISSUE 3 REVISION 1
Full-Rate Transcoder (XCDR) Board
The digital signal-processing card that performs the GSM defined speech encoding/decoding and data rate adaption on up to 30 TCH. The XCDR also sub-rate multiplexes 4 TCH on to a single switch bound TDM timeslot. Transcoding in GSM is performed to reduce the number of bits (information) transmitted over the air interface, also as a consequence of this efficient use of the 2 Mbit/s links are realised. In addition to processing the 30 TCH the XCDR board can process a single signalling link (MTL). The XCDR function can reside at a BSC site or a Remote Transcoder site (RXCDR), the later option is the more common configuration.
XCDR processor/DSP System

The main component of the processor system is the microcontroller unit (MCU) which controls and interfaces all five major systems on the XCDR module. The MCU supports on board self diagnostics and periodically strobes the watchdog timer. If the watchdog timer is not strobed by the MCU before it times out the MCU is reset and an alarm sent to the controlling GPROC via the MCAP bus. The DSP system consists of thirty programmed DSPs subrate multiplexer, serial port timing generator and an MCU interface for control purposes. The DSP units are arranged in four groups, three of eight and one of six. The subrate multiplexer can operate in three modes, DSP loopback, 16k Multiplexed and 64k non-multiplexed. In the DSP loopback mode the DSP output is logically switched to its input enabling a self test function. In the 16K mode each DSP receives 16 bits of data, the first two bits received from the 16 Kbit/s subrate channel routed from the TDM Highway, the next six bits are filler bits and the last eight bits are routed from the 2 Mbit/s links data stream. In the 64 kbps non-multiplexed mode each DSP receives 16 bits of data, the first eight are routed from the TDM Highway and the second 8 bits routed from the 2 Mbit/s links data stream. The serial port timing generator ensures all DSPs are synchronised.
Generic DSP Processor (GDP) Board

The GDP also performs speech encoding, decoding and sub-multiplexing functions. The GDP board enhances the transcoder function by providing support for full rate, enhanced full rate and half rate transcoding as well as data rate adaption on user data calls. Each GDP board can support 30 traffic channels. The maximum GDP boards per BSU is 6 at a BTS, 12 at a BSC. Normally transcoding is not supported at a BTS however the GDP board may be used at a BTS where lines are shared with other equipment such as a local PABX.
242
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
LEDs M EM ORY M AIN PROCESSOR RESET SWITCH TTY Test port M CAP INTF. RECEIVED CLOCK E1 INTF SWITCHING SYSTEM DATA ENCODER DATA DECODER TDM INTF TDM INTF A B A B A B Comms to GPROCS Clock ref. To GCLK Rx Tx SPAN 1
TDM Outbound Highway A+B TDM Switchbound Highway A+B
SERIAL DATA FORM ATTERS AND PORT TIM ING GENERATOR
DSP SUB SYSTEM 1-30
DSP CONTROL
XCDR
S S S S S
Speech Encoding / Decoding / Data Rate adaptation. Sub-multiplexing BSC/RXCDR Upto 30 traffic channels 1 X E1 link interfaced
Generic Digital signal Processor (GDP)

S S S S S S Speech Encoding / Decoding / Data Rate adaptation. Sub-multiplexing BSC/RXCDR/BTS Upto 30 traffic channels 1 X E1 link interfaced Enhanced full-rate
EMOTOROLA LTD. 2001
243
ISSUE 3 REVISION 1
GDP Processor/DSP System

The GDP board has been developed to support the Transcoding for full rate, enhanced full rate and half rate speech on the GSM air interface. It is the next generation Transcoder board using downloadable DSPs to enable easier upgrades and increased functionality. In addition to the GSM air interface algorithms the GDP will also support G.728 Transcoding where 64 Kbit/s PCM channels are compressed to 16 Kbit/s using low delay code excited linear prediction to enhance nailed connection of other equipment such as a local PABX, allowing a 4 to 1 utilisation of the leased lines. A further enhancement is the capability to provide uplink and Downlink volume control of the traffic channels in 1 dB steps over a range of 30dB (15dB to + 15dB). Unlike the XCDR board, GDP supports both El and T1 line interfaces with different versions of the board to remove the requirement to use MSI2 boards as T1 to El converters and it may be equipped at the BTS to support G.728 Transcoding for nailed connections. Selection of the Transcoding algorithm is carried out on a per call basis with signalling contained within the TRAU frames used to configure the channel coders at the BTS and the DSPs on the GDP. The GDP makes use of a Motorola MC68360 processor as its main controller with 15 Motorola Digital Signal Processor D5P56301 to support 30 traffic circuits (each DSP handling two traffic circuits each). It is compatible with the existing BSU and RXU cages and can perform all the functions of the current XCDR boards.
GDP features
S S S S S S Supports thirty compressed voice and data services using 15 DSPs. DSP firmware is downloadable. Non-volatile storage of DSP firmware. Selectable El or T1 interfaces. Line interface provides clock and data extraction, jitter attenuation, HDB3/AMI decoding, bipolar conversion and CRC4 checks. Dual redundant TDM and MCAP interfaces. Pin compatibility with XCDR board.
244
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
245
Internal Alarm System
ISSUE 3 REVISION 1

This feature will provide the functionality to maintain the colours of the two LEDs on the DAB, and also to report any alarms detected by the DAB to the Fault Collection Process (FCP)/Fault Translation Process (FTP) subsystem, where they may be displayed on a local TTY or uploaded to the OMC. The DAB and PSMs are polled via the serial bus. Since serial busses are local to a cage, this polling must be performed by a process running on a GPROC within each cage. In the BSSC cabinet, where there are two cages, the DAB will be connected to one cage. The polling process in each cage will both poll the DAB, but only one process will receive a response, while the other will not. A new process (the Internal Alarm System (lAS)) will be created in each cage. This process is responsible for regularly polling the PSM and DAB devices to determine the alarm status, and will inform the FCP/FTP subsystem when an alarm condition changes state from clear to set, or from set to clear. This feature will: S S S S S provide the customer with the ability to determine from the OMC when problems occur with various hardware equipment. poll all DAB at a site on a regular basis to determine the status of all alarms monitored by such boards. poll all IPSM/EPSM at a site on a regular basis to determine the status of all alarms associated with the modules. notify the FCP/FTP subsystem when it determines that an alarm condition occurs, and again when the alarm condition is cleared. cause the alarm text to be displayed on the local TTY or at the OMC in the manner consistent with other alarm string displays.
246
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

To OM C/TTY
GPROC (IAS)
Fault M anager in Digital cage
Polled Via serial bus
DAB
PSM
PSM
PSM
S S S S
Run by a GPROC in every cage. Polls each power supply module for its status. Polls the DAB for the status of all monitored alarms hardware. Reports any alarms back to the OMC
EMOTOROLA LTD. 2001
247
Parallel Interface Extender
ISSUE 3 REVISION 1

The Parallel Interface Extender (PIX) is a daughter board which resides in the upper board portion of the BSU shelf. The PIX provides an interface to the serial I/O lines of the processor boards in a shelf. The parallel outputs are used for control functions e.g. an audible alarm. The inputs are used for monitoring various alarms either inside or outside the BSS rack. A maximum of two PIX daughter boards can reside in a given shelf to provide a total of 16 external inputs and 8 external outputs. In total one board provides 8 sets of dry contact inputs and 4 sets of dry contact outputs to be defined by the customer. Four relays provided on the PIX board to control different functions defined by the user. The relays can be activated by the GPROC using serial lines in the interface. The PIX is connected to the processor board in the shelf via the backplane and to the external devices via a 62 pin connector.
External Alarm System (EAS)

There are a number of customer definable alarms associated with the External Alarm System (EAS). The Parallel Interface Extender (PIX) board provides the interface hardware for this system. The EAS Alarm table is an indexed listing of up to 20 user-defined alarm text strings for each BSS. Each alarm indicates a change in the state of the Customer defined alarm since the last time it was polled. The alarm is identified by the number of the optocoupler device on the PIX board which triggered it and by a customer defined alarm string, which is reported in the additional information field. The alarm string used and associated with optocoupler devices is made with MMI commands. Parallel Interface Extender (PIX) The Parallel Interface Extender (PIX) card is required in the first cabinet of each site to provide the interface between the BSS processors and the customers site equipment. This board will provide 8 sets of dry contact inputs and 4 sets of dry contact outputs, to be defined by the customer. The board will contain the required interface logic between the GPROC parallel I/O lines and relays. A maximum of two PIX boards can reside in each cage, allowing for an expandable amount of I/O. The maximum PIX per BSU/RXU is two (2 PIX per BSSC).
248
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
External Alarm System

Pix 0 Pix 1 Top Panel
8 Alarm inputs PIX
4 Alarm outputs
GPROC (EAS)
Via serial lines on backplane
S Via PIX board

-8
Optocoupler sensors - 4 Relay drivers
S Customer defined alarm

- Intruder - Fire - Door open - AC power - M ains alarm
EMOTOROLA LTD. 2001
249
BBBX Module
ISSUE 3 REVISION 1
BBBX Module
The Battery Back-up Board (BBBX) module provides a back-up supply of +5V at 8A, in the event of a main supply loss. There are no connections to the backplane. Battery backup supply, +5 V DRAM, is used to: S S Maintain power to the optical circuitry on the Local Area Network Extender (LANX) module. Prevent corruption of the Generic Processor (GPROC) code load due to loss of primary dc power.
250
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BBBX Module
Battery Backup Board

4 PIN AM P ." CONNECTOR OUTPUT VOLTAGE (+5 V @ 8A) INPUT VOLTAGE (20 TO 75 V SURGE PROTECTION BRIDGE RECTIFIER DC to DC CONVERTER ALARM SIGNALS OVER VOLTAGE OVER TEM PERATURE
@ 3.2 TO 0.85 A)
OUTPUT GOOD INPUT GOOD
9 PIN D" CONNECTOR
S S
Provides back up power to DRAM on GPROC Provides backup power to optical circuitry on LANX cards
EMOTOROLA LTD. 2001
251
Shelf Internal Connections Overview
ISSUE 3 REVISION 1

To process all the data required to make and maintain the call, each software process and therefore digital card must be able to communicate which each other and to any external entities such as the MSC or BTS. Each card has one or more connections to one or more data buses to co-ordinate this data transfer. Each bus has differing functions and can be summarised below:
TDM (Time Division Multiplexed) highway

This bus is used to pass call and signalling data from the BTS to the MSC and vice versa. The TDM highway is split into two separate sections :
Switchbound highway
Handles data routed towards the switch. Data is either from an external source (via the E1/T1 interfaces) or is generated by the GPROCs internally.
Outbound highway
This is data that has been switched and is now being routed out of the BSC /RXCDR (via the E1/T1 interfaces) or towards the internal GPROCs. The cards connected to the TDM highways are:
GPROCs
Send and receive control data to/from external entities such as the MSC (MTL) , BTS (RSL) , RXCDR (XBL), OMC (OML) and CBC (CBL).
E1/T1 interfaces
MSI / XCDR / GDP boards. These cards interface the E1/T1 links to the TDM highway to make sure the data incoming an out going is in the correct format.
KSW
This board takes the data in from the Switchbound highway and switches it to the correct section on the Outbound highway.
Bus Terminator Card (BTC)

The Bus Terminator Card (BTC) provides the terminations necessary for all of the signals on the BSU backplane and is required due to the high speed buses contained in the backplanes. Two BTC cards are required in each cage, one at each end, in order to guarantee the proper termination characteristics. The maximum/minimum BTC in the BSU/RXU is two.
MCAP (Motorola Cellular Application Processor) bus

The MCAP bus provides the GPROCs within the shelf to monitor and control all the other full size cards, except other GPROCs.
LAN (Local Area Network)

The LAN allows all GPROCs to communicate to each other via a dedicated high-speed bus.
Serial bus
Interfaces the DAB, PSMs and the Half size cards to the GPROCs for control and monitoring purposes.
252
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Shelf Interconnections Overview

Links to M SC or BTS External Alarms To 2nd Cage for expansion KSWX EXP of KSW T43 / BIB PIX LANX LAN CLKX XCDR
253
To other cages at the site
DAB/PSM s Half size cards
GPROC
GPROC
KSW
Remote KSWX RM T
TDM
Outbound Highway
Remote
TDM
Switchbound Highway
To 2nd Cage for Extension TDM Highway
M CAP BUS
EMOTOROLA LTD. 2001
GCLK
M SI
GDP
Serial Bus
ISSUE 3 REVISION 1
254
EMOTOROLA LTD. 2001
Chapter 3
RXCDR/BSC Digital Communication Buses
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Chapter 3 RXCDR/BSC Digital Communication Buses . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Area Network Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola Cellular Advanced Processor (MCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCAP Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Division Multiplexed Bus (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport Switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM BUS Timeslot Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Bus Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Bus Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Highway Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Remote Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TDM Expansion Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Watchdog Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport Switch Extender Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 32 34 36 36 38 38 310 310 310 312 312 314 314 316 318 318 318 318 320 320 320 322 322 324 326 328 330 331 332 334 336
EMOTOROLA LTD. 2001
iii
ISSUE 3 REVISION 1
iv
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Objectives
Objectives
On completion of this section the student should be able to: S S S S Identify the functions of the Local Area Network (LAN) Identify the functions of the Motorola Cellular Advanced Processor (MCAP) Identify the functions of the Time Division Multiplex (TDM) Highway Identify the functions and operational ability of the Kiloport Switch (KSW) and state how the KSW can be expanded and extended
EMOTOROLA LTD. 2001
31
Local Area Network (LAN)
ISSUE 3 REVISION 1

A 16 Mbps IEEE 802.5 token ring LAN is used for interprocessor communications. This LAN supports the looselycoupled multiprocessor architecture employed in the Motorola BSS. For a GPROC to be able to use the LAN it must be able to: 1. 2. 3. Provide the LAN data to the LANX. Receive the LAN data from the LANX. Inform the LANX that it is present in the ring.
The LANX is able to support up to 8 GPROCs in one shelf and is also extendable to other shelves/cabinets via fibre optic cable. To facilitate this the LANX contains an electrical/optical converter. Before a GPROC can transmit data via the ring it must first be in possession of the token. Once in possession of the token, no other GPROC is able to transmit data. The data being transmitted can be addressed to all GPROCs inserted in the ring or to specific GPROCs. Data on the ring is read by all GPROCs and if the address does not correspond to that GPROC it will not act upon that data. Once the transmitting GPROC has finished transmitting it places the token on the ring which then can be seized by any other GPROC wishing to transmit data. When the ring is not being extended to other cabinets/shelves then the LANX is looped to complete the ring. The LANX contains backup circuitry with its own backup power supply. This includes the optical/electrical converters so that in the event of power failure that shelf is bypassed. For redundancy two LANX boards are used in a given BSU and each GPROC is able to use either. These two LANX boards provide two independent fibre optic paths between each BSU shelf.
32
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSS Local Area Network

S
16 Mbps IEEE 802.5 Token Ring
Loop (Fibre Optic)
TX
GPROC 0 LANX
RX
GPROC 7
GPROC 1
GPROC 6
TOKEN
GPROC 2
GPROC 5
DEFAULT MASTER SLOT 20
GPROC 3
GPROC 4
EMOTOROLA LTD. 2001
33
LAN Extension
ISSUE 3 REVISION 1
LAN Extension
The system software at the BSC site is designed and operated on a per site basis. Therefore all the GPROCs in any BSC cabinet on a site must have the ability to communicate with one another. Inter GPROC communication is supported by the Local Area Network (LAN), so the Local Area Network Extension (LANX) cards in each of the Digital Cages. One LANX card is provided with each Digital Cage, but for full redundancy on the Local Area Network, a second LANX card is required in EACH Digital Cage. The LANX can support a network of 14 Digital cages maximum at any one BSC site. The first Digital Cage at a BSC site is always given the cage designation 0. This is set by use of a rotary switch on the LANX, whose switch settings go from 0 to F in hex values. Therefore the first Digital Cage at a BSC site has the rotary switch on the LANX set to 0. The next Digital Cage at the same BSC site has its LANX rotary switch set to 1. Each subsequent Digital Cage at the BSC site has its LANX switch set as to reflect working anticlockwise around the switch settings. The LANX cards each have a Transmit and Receive fibreoptic connector. The LANXs are interconnected in a serial fashion, ie Tx on one LANX card is connected to the Rx on the next LANX until the ring is completed.
34
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
LAN Extension
LANX Requirements
BSSC BSSC
LANX A
LANX B
CAGE 1
LANX A
LANX B
CAGE 3
LANX LANX A B
LANX LANX A B
CAGE 0
CAGE 2
f e d c
RX FIBRE CONNECTOR 1 2 3 4 5 TX FIBRE CONNECTOR ROTARY SWITCH
a 9 8 76
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
LANX Cage 0
LANX Cage 1
LANX Cage 2
LANX Cage 3
Fibre Optic
EMOTOROLA LTD. 2001
35
Local Area Network Extender
ISSUE 3 REVISION 1

Operation
The LAN Extender (LANX) is a daughter board which resides in the upper portion of the BSU shelf. The LANX provides the capability to extend one of the two LANs to other shelves and racks via optical fibres. In addition, the LANX provides a central point for the LAN connections from all the GPROC boards which sit on the LAN ring. This feature allows the LANX to switch empty board slots or failed boards off the LAN to keep the LAN in operation. Two LANX daughter boards are used in a given shelf to provide primary and redundant LAN interfaces. Each LANX board receives the LAN data from another shelf, route the LAN data to the first GPROC, receive the LAN data back from the first GPROC, and route to the second GPROC, and so on until all GPROCs have received the LAN data. The LAN data output of the last board is converted to an optical fibre signal and sent to the next shelf. If a board is not present or has failed, the LANX bypasses it and passes the LAN data to the next GPROC. Each LANX board has two serial buses for communication with the GPROC board. The selection between which bus to use is controlled by the GPROC boards serial interface circuitry. The LANX also performs the arbiter function for the dual MCAP buses.
CAGE 0 SLOT U20
Rx
LANX
Tx
LANX A
BSU
CAGE 1 SLOT U20
BSU
LANX A Rx
Tx
36
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
LANX Module
BACKPLANE CONNECTOR SERIAL BUS A SERIAL BUS B
REVISION/SLOT ID
BUS ARBITER LAN LOCAL/EXTERNAL
FIBER OPTIC RECEIVER
M UX
BUS GRANT 0 LAN DATA OUT 0 BUS REQUEST 0 LAN DATA IN 0 INSERT 0
WARNING
Possible laser radiation when fiber optic cables are disconnected. Do not look directly into beam with or without the use of any optical aids. Radiation can come from either the data in/out connectors or unterminated fiber optic cables connected to data in/out connectors.
GPR OC SLO T0 GPR OC SLO T1 GPR OC SLO T2 GPROC SLOTS 3, 4, 5, 6
M UX
M UX
POWER FAIL DETECT POWER DISTRIBUTION FIBER OPTIC TRANSMITTER
M UX
GPR OC SLO T7
EMOTOROLA LTD. 2001
37
Motorola Cellular Advanced Processor (MCAP)
ISSUE 3 REVISION 1

Introduction
The MCAP is a parallel communications bus clocked at a rate of 16.384 MHz. It allows one GPROC in the BSU or RXU cage to communicate with the following peripheral boards: 1. 2. 3. 4. 5. Kiloport Switch (KSW) Multiple Serial Interface (MSI) Generic Clock (GCLK) Transcoder (XCDR) Generic Digital Signal Processor (GDP)
GPROCs communicate with each other via the LAN interface, whilst the MCAP bus is used for comunications between the GPROCs and the peripheral boards. In order to gain access to the MCAP bus, a GPROC must go through an arbitration sequence carried out on the LANX. Each MCAP bus (A or B) has its own arbiter located on a LANX (A or B) card. There are effectively two buses on the backplane (A and B). One bus, A or B is active and the other will be in standby mode, depending on the state of the system. The operations of both buses are identical. The only distinction made will be active bus or standby bus. Within a BSC or RXCDR each cage will have one GPROC assigned as MCAP master. This GPROC controls all communication to the peripheral boards and so will always be granted use of the MCAP bus by the LANX card. (In a non-M-Cell BTS there will be GPROCs assigned as DHPs (Digital Host Processor) controlling DRIM (Digital Radio Interface) cards via the MCAP bus. In this case the LANX will provide arbitration between the DHPs and the MCAP master GPROC).
38
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
MCAP
Token Ring LAN Between GPROC boards
BSP
1 MCAP MASTER
GPROC
GPROC 2
GPROC N
M CAP Bus
Peripheral Board
Peripheral Board
Peripheral Board
All cards controlled by a single GPROC in the cage
Peripheral Boards: GCLK, KSW, M SI, XCDR.
Logical Association of GPROC Boards and Peripheral Boards
EMOTOROLA LTD. 2001
39
MCAP Introduction
ISSUE 3 REVISION 1
MCAP Introduction
The GPROC communicates with peripheral boards (ie. KSW, MSI, XCDR, etc) via the Motorola Cellular Advanced Processor Bus (MCAP Bus). The process on the GPROC that controls this interaction is called the MCAP DLSP. The MCAP DLSP provides multiple services to MCAP bus user processes. These services are; S S A high level interface between application processes on GPROCs and peripheral boards connected to the MCAP bus. Managing code loading of the peripheral boards connected to the MCAP bus. The term code loading refers to the collected actions of code downloading and code uploading. Maintaining cage configuration with regard to the peripheral boards within the cage. This information is based on the types of peripheral boards contained within the cage. Overflow protection for MCAP message buffers. A routing facility for messages that flow between the application processes (on the GPROCs) and the peripheral board firmware. MCAP DLSP is also responsible for providing an error free communication path between the peripheral boards and application software.
S S
Since the MCAP bus is confined to one cage (not extendable), the MCAP DLSP is only responsible for providing a communicating path between GPROCS and peripheral boards that reside in the same cage. Application processes that need to communicate with peripheral boards in different cages will have to use different MCAP DLSPs. A MCAP DLSP may reside on any GPROC but there is only one active MCAP DLSP per cage.
Address Area
Individual boards are addressed using a physical location system, where each of the boards are assigned a 5 bit address related to its physical card slot position (ID) in the cage plus 18 bits giving an address range of 256 k locations for each board and an additional bit to control selection of either MCAP A or MCAP B buses.
Data Area
The physical data width of the bus is 16 lines (2 bytes or word). However a separate line from the bus master(s) allows the bus to support dynamic sizing, e.g. the width of the bus changes to correspond to the width of the data i.e 8 or 16 bits. A parity bit is also added for error detection.
310
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
MCAP Introduction
MCAP DLSP
ADDRESS
MCAP DLSP
DATA
CONTROL
5 18 1 16 1 1
Address lines [slot position] Address lines [256 k locations] MCAP BUS Select [A or B] Data lines Dynamic Bus Sizing Parity Bit Parallel bus clocked at 16.384 MHz
EMOTOROLA LTD. 2001
311
Time Division Multiplexed Bus (TDM)
ISSUE 3 REVISION 1

Introduction
The time division multiplexed bus is a parallel highway used in the BSU and RXU cages to switch traffic and signalling data within the site. The TDM highway allows the GPROCS and peripheral cards to interface to the 2.048 Mbps E1 links connecting the network together. The TDM bus consists of two highways, each operating a frame structure of 1024 timeslots every 125us. Each timeslot consists of 8 data bits and is equivalent to a 64kbps channel with an additional parity bit for error detection. The Kiloport Switch is in control of the TDM highways known as the switchbound and outbound highways. The switchbound identifies the highways going into the KSW whilst the outbound identifies the highway going away from the KSW. In a multiple cage site the TDM highways must be extended or expanded to all cages in the site. At a BSC or RXCDR it is more usual to expand the highways. The decision on whether to extend or expand is dependent on the requirements of the site configuration.
312
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
TDM Bus
2 Mbit/s E1 link
MSC
Switchbound highway
MSI
Outbound highway
XCDR
Switchbound highway Outbound highway
KSW
KSW
MSI
BTS MSI
2 Mbit/s E1 link
BTS
EMOTOROLA LTD. 2001
313
Kiloport Switch (KSW)
ISSUE 3 REVISION 1

Introduction
The KSW is a time division digital switch whose function is to interconnect the terrestrial 64 kbps circuits on the external 2 Mbit/s links to the digital modules within the RXCDR and BSC sites. At the BSC the KSW is dynamically configured enabling the mapping of a terrestrial circuit from the MSC to be connected to a radio channel on a call basis. It is this ability which allows the BSC to control call setups and handovers. The KSW in an RXU provides one to one mapping between traffic to/from the BSC and MSC. Each KSW can switch connections between 1024 timeslots on the switchbound and the 1024 timeslots on the outbound highway. Each TDM Highway can be extended to five additional extension cages and can be expanded to a maximum capacity of four highway where each KSW is connected providing the ability to switch data from 2048, 3072 or 4096 64kbps input ports and its 1024 output ports. The primary function of a KSW is to support the switching of timeslots on the TDM highways. Secondary functions include tone generation, static pattern generation, and dynamic pattern generation. Each KSW controls a dedicated TDM bus. A single KSW can provide 1024 timeslots. The KSW is capable of supporting several subrate switching modes in order to satisfy a variety of switching requirements. The KSW can process any given timeslot as a 64Kbps traffic channel, two 32Kbps traffic channels, four 16Kbps traffic channels, or a combination of 32 and 16Kbps traffic channels. In general, the KSW will treat each TDM timeslot as four 16 Kbit/s traffic channels
BTS
N I U
M C U
T C U
RXCDR
M S C
64 kbits
BSC TSW
X C D R
K S W
M S I
16 kbits
M S I
K S W
M S I
BTS
KSW STATIC
KSW DYNAMIC
N I U
M C U
T C U
TSW
314
EMOTOROLA LTD. 2001
Note: This example shows E1 links only
Dynamic Switching BSC

K S W M M S 0 M M S 1 MMS0 MMS1
2 Mbit/s Link 0 1 x D x x 2 B C x x 3 4 5 6 FAW
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
BTS2
M M S 0 M M S 1 TCU
Air Interface
2 Mbit/s Link
FAW B C
315
E D
0 1 2 3 4 5 6
M M S 0 M M S 1
M C U
31
31
2 Mbit/s Link
0 1 2 3 4 5 6 7
0 1 2 3 X x X x 4 A x E x 5 6 FAW
BTS1 NIU
D B C
MCU TCU
31
0 1 2 3 4 5 6 7
Air Interface
TDM BUS Timeslot Use
ISSUE 3 REVISION 1

Every BSC Site requires a minimum of 1 switching board in one of the BSC cabinets installed. As the BSC site grows, ie extra BSSC cabinets and digital hardware are installed, the requirements of all the hardware start exceeding the 1024 timeslots provided by a single switch so expansion of the switching fabric is required. There are five device types that require a timeslot allocation on the TDM BUS at a BSC/RXCDR site. These are GPROCs, MSI, XCDR, GDP and KSW. Each of these devices require the following timeslot allocation. GPROC The number of TDM BUS timeslots allocated to each GPROC on a site is defined in the database for that BSC site. There is a database parameter called gproc_slots. There are 3 settings for this parameter, they are 8,16 or 32. This details how many TDM BUS timeslots are to be allocated to each GPROC. In either case 1 timeslot is reserved for testing, leaving 7,15 or 31 ports for the sending and receipt of the signalling. Note: gproc_slot should only be set to 32 if GPROC2 boards are available. XCDR/GDP 16, The number of TDM Bus timeslots allocated for each XCDR carried is as traffic channels are operating at 16Kbits.
MSI The number of TDM timeslots allocated to each MSI card is 64, this is because the MSI supports upto two 2 Mbit/s links. KSW 8 timeslots are allocated per KSW and are used for by the KSW during Expansion/Extension working.
316
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
TDM Bus Timeslot Allocation at a BSC/RXCDR Site

0
8,16 or 32 Timeslots Each GPROC
64 Timeslots
Each MSI
TDM BUS 1024 Timeslots
16 Timeslots
Each XCDR/GDP
(8 bit parallel bus)

8 Timeslots
KSW
1023
EMOTOROLA LTD. 2001
317
TDM Overview
ISSUE 3 REVISION 1
TDM Overview
The device management of KSW, TDM and TBUS is intended to provide control for configuration and operation of the KSW,TDM and TBUS. Up to two KSWs can reside in a cage ( one active and one redundant). Similarly, two TBUSs (explained below) reside in a cage ( one active and one redundant). The logical device TDM represents the combination of all TBUSs (from one highway, either A or B) for all cages in a site.
TBUS
A TBUS is a logical device used to identify the TDM highway backplane connection in a cage, local and remote KSWXs (if they exist) and the fibre optic cable that interconnects the KSWXs as one physical device. Each cage has two (one active and one redundant) TBUS associated with it. The state of the TBUS depends upon the state of its parent KSW, therefore a change in KSW state will also affect the corresponding TBUS. A fault in any of the physical components which make up the TBUS will result in a TBUS alarm being sent to the OMC.
TDM
The TDM (Time Division Multiplexing) bus can be viewed as an extension of the KSW. TDM is a logical device consisting of its associated TBUSs. The TDM device is based exclusively on TBUS devices from one highway (A or B) within a site. Combination of TBUSs from both highways A and B is not allowed. Therefore TDM A consists all TBUS A devices and TDM B consists all TBUS B devices. Only one TDM can be active at a given time, therefore only TBUS A or TBUS B for a cage can be active at a given time. As with the TBUS any fault on any of the components which make up the TDM devices will result in a TDM alarm being sent to the OMC.
Redundancy
A failure of the active TDM highway will result in an automatic switchover to the redundant TDM highway if available. In order to support this the redundant KSW is updated with the same connections as the active KSW. However, the redundant KSW will not drive its associated highway until it is made the active device. ie, the active KSW fails and the system switches to the redundant highway.
318
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
TDM Overview
KSW SLOT 1
TBUS B
TDM Architecture
EMOTOROLA LTD. 2001
KSW SLOT 27
TBUS A
PERIPHERAL BOARDS
319
TDM Frame Structure
ISSUE 3 REVISION 1
TDM Frame Structure

The TDM frame consists of 1024 timeslots each of 122nsec giving an overall frame duration of 125 msec. The TDM bus has a 8bit wide data field and uses a 1bit parity check enabling a data rate of 64 kbit/sec on each TDM timeslot. The bus has 480 frames per TDM multiframe over 60 msec duration. The 60 mS TDM multiframe is used for synchronisation of the TDM Highway and the air interface.
TDM Bus Integrity

The TDM bus structure uses parity to check the bus integrity. The outbound TDM bus (outbound with respect to the switch) uses even parity. Even parity causes a floating bus with pullup resistors to generate a parity alarm on the receiving expansion Interface cards. Thus, if the switch or KSWX is removed from the shelf, a bus parity alarm is generated on the expansion Interface cards. This parity alarm is one factor in determining which TDM bus is active on any given expansion Interface card. The switchbound TDM bus is also at even parity. The reason is the same; namely, a floating bus (expansion Interface card pulled or not present) generates a parity alarm. The KSW has the ability to change the expected parity sense to odd in order to induce TDM bus parity alarms. This feature provides a means of checking the parity logic.
TDM Bus Interfaces

The TDM bus is structured around an 8.192 MHz timeslot (8000 x 1024). In an effort to eliminate bus contention from one timeslot to the next, the expansion Interface cards drive the TDM switchbound bus on their assigned timeslots for only approximately 3/4 of the timeslot. The last 1/4 of the timeslot is set aside to ensure that two expansion Interface cards do not attempt to drive the bus simultaneously. The bus receivers sample the bus in the centre of the timeslot. This provides for approximately 60 nsec of setup time and 30 nsec of holding time. The KSW will drive the TDM outbound bus during the complete timeslot rather than only the first 3/4 of the timeslot. This is allowable since the KSW is the only card that is driving the outbound TDM bus; thus, bus contention is not a factor.
320
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
TDM Frame Structure
TDM Highway
SET UP 60nS HOLD 60nS
Outbound
RX
GPROC MSI XCDR GDP InterfaceCard K S W
TX
Guard Period 30nS
HOLD 30 nS
SET UP 60 nS Switchbound
1 bit period
EMOTOROLA LTD. 2001
321
Processor Module
ISSUE 3 REVISION 1
Processor Module
The KSW is internally controlled by a Motorola MC 56001 Digital Signal Processor (DSP) whose primary function is to control the interconnection process between incoming and outgoing ports on the TDM Highway. Its secondary function include KSW self diagnostics control of inbound and outbound multiplexers, processing alarms and updating the dynamic pattern registers. Diagnostics include both internal (KSW related) and external (TDM Highway related) tests. Communication between GPROC and KSW is via the MCAP bus
TDM Highway Interface

The switchbound TDM Highway Interface consists of a series of multiplexers which are used to select one of five switchbound highways and is under control of the DSP. The switchbound highway and the outbound highway are divided into two parts, local and remote. The local switchbound and outbound highways are active when the KSW in communicating with highway interface cards in the same cage as the KSW.
322
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Processor Module
TDM Highway Interface Single BSU/RXU
Local Switchbound
KSW
Local Outbound
EMOTOROLA LTD. 2001
323
TDM Remote Highways
ISSUE 3 REVISION 1
TDM Remote Highways

The remote switchbound and outbound highways are active when the KSW is switching traffic and signalling data to the peripheral boards in extended cages. In this way the TDM highway and switching capacity of the KSW are extended to the remote cages at a site. In the master cage (the one with the KSW), KSWX cards in remote positions are used to send and receive highway data to and from the extended cages. In the extended cages (no KSW fitted) KSWX cards in the Local position, send and receive the highway data and drive the local switchbound and outbound highways. Local highways have a 12 TDM timeslot delay to compensate for the delays associated with extension.
324
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
Highway Extension (Remote)

Cage 0
Remote KSWX
Cage 1
Fibre Optic Cables Remote Outbound and Switchbound Local KSWX K S W X A 0
K S W X A 4
K S W X A 3
K S W X A 2
K S W X A 1
K S W X A 0
Local Switchbound KSW Local Outbound
Local Switchbound
TDM Remote Highways
Local Outbound
325
TDM Expansion Highways
ISSUE 3 REVISION 1

The KSW boards in an expanded site each have an expansion outbound highway to enable all KSWs in the site access to the data on their switchbound highways. A site may be expanded up to a maximum of 4 KSWs therefore each KSW has access to 3 expansion highways inbound that are connected to the respective expansion highways of the KSWs in the site. This architecture results in each KSW having the potential to switch data to and from any of the 1024 timeslots of all the KSWs in the system. For example in a system expanded to the maximum of 4 KSWs, each KSW can switch any of 4096 timeslots on their switchbound/inbound highways to any of the 4096 timeslots on the outbound highways. All of the KSWs in the site receive their connection data from the master GPROC at the site. The process that deals with this is the Switch Manager process, which executes on the Master GPROC at each site.
326
EMOTOROLA LTD. 2001
Highway Expansion
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
Cage 0
Expansion Outbound Expansion KSWX K S W X A 2 K S W X A 1 K S W X A 0
Cage 1 Expansion Outbound Expansion KSWX K S W X A 2 K S W X A 1 K S W X A 0
Cage 1
EXP HWY 1
EXP HWY 1 Local Switchbound KSW Local Outbound Local Switchbound KSW
Local Outbound
327
TSI Operation
ISSUE 3 REVISION 1
TSI Operation
The TSI section is the main section of the KSW. It performs switching of data from a given timeslot on one of the four switchbound TDM Highways to a given timeslot on the outbound TDM Highway. The TSI section consists of four independent TSI blocks operating in parallel in order to support subrate switching each TSI block switching 16 kbps of data. If a particular timeslot is associated with a 64 kbps channel then all four TSI blocks will be allocated the same path connected for that timeslot. Conversely, if a timeslot is associated with two 32 kbps channels two TSI blocks will be allocated a similar path connection and the other two to a different path connection. When a timeslot contains four 16 kbps channels each TSI section will be allocated a different path connection. The Connection Ram (CRAM) control is the interface between the Processor and the TSI section. It provides Processor isolation from the strict timing constraints associated with TSI operation. On leaving the TSI section data sent to either the TSI mode multiplexer which selects either full rate or subrate switching or the third party conference (TPC) memory section. The TPC memory operates in real time allowing the KSW to support any number of TPC calls. After traffic data leaves the TSI it is sent direct to the Outbound select multiplexer.
328
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
TSI Operation
Timeslot Interchanger (TSI)

DELAY
EXPANSION SWITCHBOUND HIGHWAYS 1, 2 AND 3 LOCAL SWITCHBOUND REMOTE SWITCHBOUND
CONTROL
MUX
DSP
EACH 16 Kbps
CONNECTION RAM CONTROL
TSI
TSI
TSI
TSI
FIXED PATTERNS
MUX
DELAY
EXPANSION OUTBOUND HIGHWAY LOCAL OUTBOUND HIGHWAY REMOTE OUTBOUND HIGHWAY
CONTROL
EMOTOROLA LTD. 2001
329
Diagnostics
ISSUE 3 REVISION 1
Diagnostics
The Processor can write to any of the four switchbound highways allowing the insertion of known static/dynamic data patterns into any switchbound timeslot. The fixed/dynamic pattern registers can generate fixed patterns such as the idle channel code and a variety of dynamic patterns which generate tones, data sequences or dynamic test patterns. As well as being able to insert data into any switchbound timeslot data can be looped back within the KSW and compared by the two highway monitors, one before and one after the TSI section. The monitor before the TSI section can selectively monitor any of the four switchbound highways. The one after the TSI section can monitor the output of the outbound selection multiplexer. The DSP uses these monitors for monitoring outbound and switchbound data in any timeslot.
330
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Watchdog Timer
Watchdog Timer
The watchdog timer is used to ensure that the DSP is functioning normally. If the DSP stops functioning the watchdog timer times out causing the front panel red LED to illuminate and the GPROC informed via the MCAP bus. In the event of DSP failure the TSI section is still able to operate but no new path connection implemented. This allows existing calls to be held while the system is reconfigured around the failed KSW.
EMOTOROLA LTD. 2001
331
Serial Interface
ISSUE 3 REVISION 1
Serial Interface
The serial Interface Logic supports the TTY interface. The interface is connected to a dedicated buffered backplane RS232C port. It is used during factory testing to control the KSW, monitor KSW operation status and support KSW diagnostics. Timing Reference Section The timing reference section generates the necessary clock signals, timeslot counts and frame counts required by the other sections of the KSW and the TDM highways.
332
EMOTOROLA LTD. 2001
KSW
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
Reference Clocks A & B
Timing Reference Logic

333
Serial Interface Logic M C56001 27M Hz DSP M CAP BUS Interface Logic Highway Control
TTY I/F M CAP Bus A & B Rmt I/F KSWX
GSM /TDM Counters
WDT
HWY M onitor
Outbound Control Ram
Connection Ram Control
HWY M onitor Switchbound M ultiplexing Section Local Hwy 0 Rmt Hwy 0 Exp Hwy 1 Exp Hwy 2 Exp Hwy 3
Serial Interface
Local Hwy 0 Rmt Hwy 0 Exp Out Hwy
Outbound M ultiplexing Section
Timeslot Interchanger Section
3rd Party Conference Pattern Generator
KSW Capabilities
ISSUE 3 REVISION 1
KSW Capabilities
1. On fault detection the switching will be automatically swapped over to the standby KSW if it is available i.e. unlocked, enabled and equipped in the database configuration. The operator may initiate a swap over without a site reset. Extension and expansion of the KSW is possible. Extension to 5 other cages and expansion to 3 other cages. The KSW device supports the MMI commands from the LMT or OMC of lock, unlock, ins_device, equip, unequip and swap. All call connections are monitored and updated to both KSWs. This will ensure that on failure of the active KSW the standby will take over with no interruption to service. However, new calls are not supported during the change over period.
2. 3. 4. 5.
334
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
KSW Capabilities
KSW Capabilities
1. 2. 3. 4. Automatic Switchover Operator Initiated Switchover Extension/Expansion supported Supports the MMI Commands: Lock Unlock Equip Unequip and Swa[ ins_device 5. Call connections are updated to both KSWs
EMOTOROLA LTD. 2001
335
Kiloport Switch Extender Board
ISSUE 3 REVISION 1

The Kiloport Switch eXtender (KSWX) board is a multifunction board which is responsible for the optical transmission of all Time Division Multiplexed (TDM) bus information between shelves and TDM clock and reference pulses in the Base Station System (BSS) shelves. The KSWX has three operational modes depending on its location in the system. 1. 2. 3. Expansion (EXP) mode expands the TDM bus between Kiloport Switches (KSW). Remote (RMT) mode extends the TDM bus to a cage for use by the highway interface cards contained in that shelf. Local (LCL) mode terminates and distributes the TDM bus extended by the RMT mode KSWX and the TDM clock and reference pulses distributed by the Clock Extender (CLKX). In an extension or expansion cage the KSWX in the local position supplies all of the clock signals and references required for the full size cards in its cage.There are delays incurred on the TDM highway when extending or expanding. Therefore, in order to keep all cages within a system synchronized it is required to extend the clock to a KSWX in the local position of the parent cage. That is the cage which holds the GCLK and CLKX for the site. By extending the clock and reference signals to the parent cages as well as the daughter cages, we introduce the same delays and allow the cages to remain synchronized.
The exercise in the Appendix gives an example of expanding the LAN, TDM highway and clock bus to multiple cages.
336
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
KSWX
INCOM ING FIBRE OPTIC CABLE FIBRE OPTIC RECEIVER OUTGOING FIBRE OPTIC CABLE RECEIVER BACKPLANE CONNECTOR
CAGE SYNCHRON IZER WRITE READ
TDM INTERFACE
TDM TDM
BUS OUTBOUND (LCL) OR BUS SWITCHBOUND (RM T, EXP)
FIBRE OPTIC TRANSM ITTER
TRANSM ITTER
TDM INTERFACE
TDM TDM
BUS SWITCHBOUND (LCL) OR BUS OUTBOUND (RM T, EXP)
FRAM E COUNTER R/W CONTROL 8 M HZ CLOCK CLK DISTRIBUTION CLOCK SELECT
16.384 M HZ CLOCK A 16.384 M HZ CLOCK B 125uS REF A 125uS REF B 60 M S REF A 60 M S REF B 6.12 S REF A 6.12 S REF B
DELAY LINE
16.384 M HZ FROM M UX
M ATE KSWX
16.384 M HZ TO BACKPLANE
INCOM ING FIBRE OPTIC CABLE
CLOCK FAIL DETECT FIBRE OPTIC RECEIVER EDGE DETECTOR
M ASTER/ SLAVE CONTROL LOGIC M UX
M ASTER REQUEST FROM
M ATE
M ASTER REQUEST TO M ATE
DECODER REFERENCE STATE DECODER
125US REF TO BACKPLANE 60 M S REF TO BACKPLANE
M UX
M UX
6.12 S REF TO BACKPLANE ENCODED CLK FROM M ATE
ENCODED CLK TO M ATE M ODULE CONTROL M ODULE ALARM S & STATUS SERIAL INTERFACE REGISTRATION M ODULE ID REVISION LEVEL SERIAL BSS BUS A SERIAL BSS BUS B
EMOTOROLA LTD. 2001
337
ISSUE 3 REVISION 1
338
EMOTOROLA LTD. 2001
Chapter 4
BSS Software
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Chapter 4 BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software functional areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Executive and Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Executive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Isolation and Memory Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexible Interprocess Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Man Machine Interface (MMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management Database Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Build Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Authority (CA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Authority Device States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Detection and Handling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message formats: Standard Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC OML defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR OML defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initialisation in RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CP at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CP at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part L2 (MTP_L2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part L3/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2001
i
41 42 44 44 46 46 46 46 48 48 410 412 412 414 414 416 416 418 418 420 422 424 426 426 426 428 428 430 430 432 434 434 434 434 436 438 438 438 440 440 440 440 440
iii
ISSUE 3 REVISION 1
Call Processing at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Scheduler (CBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocation Manager (AM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 1 Protocol (Layer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Configuration and Fault Management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . Handover Detection and Power Control (HDPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Decision Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
442 442 442 442 442 444 446 446 448 448 450 452 454 456 458 460
iv
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Objectives
Objectives
On completion of this section the student will be able to: S Identify the major sections of the BSS software. BSS Executive/Operating BSS Operations and Maintenance Radio Subsystem Call Processing S S Identify the Motorola software configuration State the basic GSM Call and Handover sequences.
EMOTOROLA LTD. 2001
41
Software Architecture
ISSUE 3 REVISION 1
The BSS software is composed of many processes, which carry out specific functions within the BSS. These processes will be distributed among the GPROCs at the site according to the configuration given in the database. At initialisation the different processes are downloaded to the site as code objects, this is part of the initialisation process permanently stored in the boot ROM. A code object is a binary file that can be built into an application process by the operating system, which runs on the GPROC boards. Each GPROC will be loaded with a complete set of the code objects for the type of site i.e., RXCDR, BSC or BTS, however not all the objects will be started as applications. Which objects are started will depend on what functions are being supported by each GPROC. For instance a BSP (master GPROC) will run different processes to a LCF (link control function). In addition to the code objects required by the GPROCs there are code objects downloaded for the peripheral devices (KSW, MSI, XCDR and GDP). These devices will receive their code from a GPROC via the MCAP bus at initialisation or whenever that device is brought into service. The operating system is called the executive and is responsible for running the application processes, passing of messages between application processes, the hardware interfaces to the application processes and memory management. This architecture means that in a lot of cases application processes are not aware of the physical location of the other processes they communicate with and because of this functions can move without any adverse affect on other processes. E.g. A LCF could be moved from one GPROC to another at a BSC without adversely affecting processes communicating with that function.
42
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSS Software Code Object Files
Code Object Files can create a System Process
All GPROCs at the same site downloaded with all Code Object Files
EMOTOROLA LTD. 2001
43
Software functional areas
ISSUE 3 REVISION 1

The BSS software can be split into five main functional areas. Each functional area is made up of a number of application processes. The five main functional areas are: 1. 2. 3. 4. 5. Executive and protocol Fault management Operations and maintenance Call Processing Radio SubSystem (only found at the BTS) Data Link Service Process Interface Man Machine Interface
DLSP: INT: MMI:
Executive and Protocol

The executive is the operating system of the GPROC, however it is made up of several processes to provide different functions for the application processes. For example the MCAP DLSP (data link service process) is an executive process that provides the application processes with an interface to the MCAP bus for communication with the peripheral cards. The EXEC DLSP provides a similar function for communications between GPROCs via the LAN or across a RSL (ie a message sent to or from the BSC and BTS). The TTY DLSP provides an interface to the serial bus for the local Maintenance terminal and for remote logins from the OMC. These are a small selection of the processes that make up the executive function.
44
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSS SYSTEM SOFTWARE
EXECUTIVE/ OPERATING SYSTEM
FAULT MANAGEMENT
OPERATIONS AND MAINTENANCE
CALL PROCESSING
RADIO SUBSYSTEM
MCAP DLSP TTY DLSP EXEC DLSP
CENTRAL AUTHORITY FAULT TRANSLATION PROCESS SWITCH MANAGER
CONFIGURATION MANAGEMENT MMI AGENT CENTRAL STATISTICS PROCESS
CELL RESOURCE MANAGER SCCP STATE MACHINE RADIO RESOURCE STATE MACHINE
LAYER 1 INT LAYER 2 INT HAND OVER AND POWER CONTROL ABIS INT CONFIGURATION AND FAULT MANAGEMENT
Note:
Not all processes are shown here.
EMOTOROLA LTD. 2001
45
BSS Executive
ISSUE 3 REVISION 1
BSS Executive
Operating System Structure
The BSS Executive software running on each of the Generic Processor boards creates the operating system for the application processes to run on. As part of this it uses process isolation and memory protection with flexible interprocess communication.
Process Isolation and Memory Protection

The executive utilises a memory management unit to isolate the memory used by each application process from every other application process. It is therefore impossible for one process to write into the memory area of another process. The memory management unit gives each application process an area of memory dedicated to that process. Allocation of memory is dynamic and these memory areas are created and destroyed as required by the software. A supervisor is created at the base of each of the memory areas allocated to the application processes. The supervisor contains functions that allow the application process to talk with the executive and so pass messages to other processes via the executive. All communication to and from the application process must go through the supervisor.
Flexible Interprocess Communication

The executive supports a flexible message routing system for passing messages between application processes and provides five modes of addressing. S S S S S Physical Logical Active Subsystem Active Cage Active Link
The differences in these modes of addressing are beyond the scope of this course, however the different modes give the routing mechanism flexibility. In order to support each mode of addressing the executive requires a set of routing tables, which contain information on where to route messages for each process in the BSS. These tables are created and updated by the Central Authority and the Router Process at initialisation and whenever changes are made to the configuration of the BSS.
46
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BSS Executive
BSS Operating Systems Overview
CA APPLICATION
ROUTER PROCESS
SUPERVISOR
ROUTER TABLES EXEC ROUTER
EXECUTIVE
CA:
Central Authority
EMOTOROLA LTD. 2001
47
ISSUE 3 REVISION 1

Operations and maintenance consists of the following functional areas: 1. 2. 3. 4. OMC Interface Man Machine Interface Configuration Management Performance Management
OMC Interface
The OML link provides the connection between the OMCR and the BSC and supports communications for the four main functions of the OMC, which are: Download of code Upload of code Event reporting Download of the code objects and the database object Upload of Statistics, Database and Code Objects Reporting events and alarm information
Remote login Access to the site man machine interface for diagnostics and configuration The four main functions relate to unique X.25 addresses at the OMC and are routed to different functional areas within the OMC. Usually there will be two X.25 addresses for download, two for event reporting, one for upload and one for remote login. The RXCDR or BSC have only one X.25 address and so all communications to and from the OMC go through the X.25 Packet Link Protocol and the Agent process. The X.25 PLP deals with the layer 3 processing of the X.25 packets and passes data to and from the Agent. The agent is responsible for routing the data to and from the correct processes within the BSS. It can be thought of as a funnel through which all communications with the OMC are passed.
48
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Operations and Maintenance OMC Interface
Switched virtual circuits support: Alarms/Events reporting Remote Login (MMI) Downloads (code loads/configuation changes) Uploads (Database, statistics)
S S
Machine (OMC) to Machine (BSC) X25 64 Kbit/s
EMOTOROLA LTD. 2001
49
Man Machine Interface (MMI)
ISSUE 3 REVISION 1

The MMI process provides an interface between the human operator and the software applications to enter commands for controlling devices, displaying information and configuring the system. The MMI can receive commands from the Local Maintenance Terminal or via a Remote Login from the OMC. The MMI process checks each command for syntax before forwarding to the relevant processes for processing. The MMI process provides three levels of access by the operator for security. S S S Level 1 Monitor commands only Level 2 All MMI commands supported Level 3 Motorola engineers only. (Provides access to restricted command library for specialist diagnostics)
For descriptions of all the MMI commands refer to the BSS Command Reference Manual 68P02901W23 in the Customer Documentation Set.
410
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Operations and Maintenance MMI
MMI is available at: S S S S S OMCR All BSS sites
Remote log in available: BSC to any BTS site From one MMI process to another at the same site From BTS to controlling BSC
MMI process interfaces with TTY DLSP. MMI process interfaces with Serial DLSP at M-Cell BTS(s).
EMOTOROLA LTD. 2001
411
Configuration Management
ISSUE 3 REVISION 1
Overview
The Configuration Management (CM) software is responsible for maintaining and updating the configuration management database at the BSC. This database holds all the configuration information for the BSC and all the BTS sites under its control. The RXCDR is considered as a separate network entity and has its own configuration database. The database is downloaded as an object file and contains site parameters such as carrier frequencies, site configuration, handover thresholds, device functionality and timing information. At the BSC the database is copied across all active GPROCs and all processes have access to the database. Similarly, at the BTS all processes can read the database. However only at the BSC may changes be made and only by the master GPROC which has write access as well as read. If there are any changes to be made to the database, the new information is written into the master database via the CM process. Once the changes have been made the CM and CA (Central Authority) check that the changes are valid before broadcasting the changes to all other GPROCs. If the changes are invalid then they are deleted from the master copy. If the database changes are required by one or more BTS sites then the master CM process will forward the changes to the CM master at each site via the RSL. Database level numbers are used to track changes and provide control. Once a database has been changed, the changes will be reflected at the OMC terminals, however, it should be uploaded to the OMC in order to update the database object held there. If the database object is not uploaded and the site was reset the OMC would download the old copy and the changes will be lost.
412
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Configuration Management Overview
All Other Processes

Read only Read/Write
CM DATABASE
CM Process

GPROC GPROC Process Y Process C
slave CM process
BSC
GPROC Process A Process B
slave CM process
Process Z
Database Copy
Database Copy
D D D
slave CM process
Database Copy
LAN
MASTER CM PROCESS Master Database
GPROC
EMOTOROLA LTD. 2001
413
Configuration Management Database Dependencies
ISSUE 3 REVISION 1

The following chart shows device and function dependencies. Due to system requirements some devices and functions can only be equipped after other specific devices have been equipped. For example, before a Message Transfer Link (MTL) can be equipped there must be a MSI card equipped in the database to take the MTL device.
Database Build Example:

EQUIP SITE
EQUIP CABINET
EQUIP CAGE
CHANGE ELEMENT (SITE CONFIGURATION)
EQUIP DEVICES
CHANGE ELEMENT (TIMERS)
ADD CIRCUITS
KSW CONFIGURATION
414
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Device and Function Dependence BSC

BSC
SITE
CABINET
CAGE
EAS
GCLK
BSP
GPROC
CSFP
KSW
MSI
LCF
OMF
XBL MTL
OML
CBL
EMOTOROLA LTD. 2001
415
Performance Management
ISSUE 3 REVISION 1
Overview
The performance management applications gather and transport to the OMC the BSS statistics in order to track trends and gives a picture of network efficiency. All application processes responsible for collecting statistics in the BSS will create a Distributed Statistics Function as a sub-process to look after the statistic information of the process. A DSF can store up to 12 sets of statistics equivalent to 12 gathering periods. The gathering period duration is set by the network operator in the configuration database and typically is 30 minutes or 60 minutes. At the BSC a Central Statistics Process (CSP) takes responsibility for the co-ordination and collection of statistics from all sites in the BSS and provides an interface to the Agent process for control of the statistic process between the OMC and BSS. All sites in the BSS (including the BSC) will start a Site Statistics Process (SSP) responsible for interfacing to the CSP and registering with DSFs at their site. At the end of the gathering period CSP will send a file ready indication to the OMC-R via the Agent. When the OMC-R requests an upload the CSP will send a similar request to all SSPs and DSFs in the BSS. At this time the SSPs will collate all statistics for their site and consolidate statistics from processes performing the same function before sending them on to the CSP at the BSC. The CSP consolidates statistics from all sites in the BSS into one report and converts them into a binary object file ready for file transfer via the Code Object Upload Process (COUP) and the Agent to the OMC-R. The COUP takes responsibility for any code upload whether it is the statistics object from CSP, a database object from CM or a code object from the Code Object Manager (COM). If statistics exceed an alarm threshold set in the configuration database, during the gathering period, this will be reported by CSP via the Agent to the OMC-R.
416
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
OMCR
X25 OMCR BSC

AGENT
COUP
CENTRAL STATISTICS PROCESS (CSP)
BTS
Remote BTS Remote BTS Remote BTS
SSP
SSP
SSP
DSF
DSF
DSF
DSF
DSF
DSF
EMOTOROLA LTD. 2001
417
Fault Management
ISSUE 3 REVISION 1
Fault Management
Overview
The fault management system can be split into two main areas, the fault detection, alarm handling and reporting and the Central Authority, although the Central Authority is also involved in fault handling. S S Fault Detection and handling Central Authority
The fault management software is designed to operate on a site basis and it has responsibility for maintaining the site integrity in response to any fault/alarm indications that may occur with the hardware or the software and operator initiated configuration/state changes. The fault detection and handling system is tasked with detecting any alarms and deciding on any hardware/software re-configurations required. The Central Authority, under direction of the fault detection and handling system is then responsible for carrying out reconfigurations and state changes. This may include, taking hardware out of service and bringing in other hardware or the creation/deletion of software processes.
418
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Fault Management
Fault Management
Fault Detection and Handling System
Central Authority
Hardware/Software reconfigurations on per site/LAN basis
EMOTOROLA LTD. 2001
419
Central Authority (CA)
ISSUE 3 REVISION 1

At site initialisation the Central Authority (CA) is one of the first processes created by the operating system. Its first task is to query the configuration database to obtain site configuration and device equipage. The CA is then responsible for creating all the necessary software processes on the GPROCs as well as downloading and bringing into service all the peripheral boards and devices. On completion of site initialisation, the CA works as an independent process and maintains a dynamic database to keep track of all the device function and software process states. The CA supervises all state changes at the site although this can be in response to MMI commands issued from the Local Maintenance Terminal, an OMC Remote Login or initiated by the fault detection and handling processes in response to a fault/alarm condition. In all cases the CA will update the dynamic database to show the new state and this will also be reported to the OMC as an alarm/event. Configuration changes may affect the routing tables used by the operating system throughout the site or possibly the BSS. In these cases the CA will initiate an update of the routing tables by the various Routing Processes in the site or BSS. This allows the software to reconfigure dynamically to any changes made. At the BSC and RXCDR the CA is also involved along with the fault handling processes with the selection of the reference clock source for the GCLK.
420
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Central Authority Functions
A) 1. 2. 3. 4. 5.
Site Initialisation Queries for database for site configuration and equipage. Downloading software to the hardware Create Software on GPROCS Creating routing tables Creating state tables
B) 1. 2. 3. 4. Hardware Software
Initiate and Direct Configuration Changes
Updating Router Updating state tables
EMOTOROLA LTD. 2001
421
Central Authority Device States
ISSUE 3 REVISION 1

Each device in the system has a device state that is reported to the Central Authority and consists of two parts: 1. 2. Administrative (lock, unlock, not equipped) Operational (enabled, disabled, shutting down, busy)
The administrative part is generally under the control of the operator by using MMI commands at the OMC or LMT. The operational states indicate the state from the viewpoint of the software. It is a combination of these two conditions which will determine if a device can/cannot be used/operated within the system. The flowchart gives an idea of how the device states are used in the system.
Not equipped
The device may be physically in the system but has not been entered into the configuration database and therefore cannot be used by the software.
Locked enabled
The device is available for use but has been made unusable by the system operator using the lock command from the MMI. If it was intended to replace a board such as an MSI this should be the state before physically removing it from the cage.
Unlocked enabled
The device is ready for use but at this time is not performing any function. It can be thought of as being in standby.
Unlocked Busy
The device is in use and operating correctly.
Busy shutting down

Operator has decided to take the device out of service in a controlled way. The device will continue with the tasks that it has active but will not take on any new tasks. When all the active tasks have been completely the device will be idle.
Unlocked disabled
The device has been taken out of service by the fault management processes possibly in response to an alarm condition on the device or an associated device.
Locked disabled
The device is taken out of service by the fault management processes and has been locked by the operator, possibly in preparation for replacement.
422
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Device States Flow Chart

NOT EQUIPPED LOCKED ENABLED
UNLOCKED ENABLED
UNLOCKED BUSY
FAULT OCCURS
BUSY SHUTTING DOWN
UNLOCKED DISABLE
LOCKED ENABLED
FAULT OCCURS
LOCKED DISABLED
EMOTOROLA LTD. 2001
423
ISSUE 3 REVISION 1

The fault detection and handling process is based around three processes
1. Fault Collection Process (FCP)

The fault collection process exists on every GPROC in a site. It collects alarm reports from all processes on the GPROC where it is active and also any other devices that the GPROC is associated with. For example the peripheral boards will raise alarms to the GPROC controlling the MCAP bus. FCP will acknowledge receipt of each alarm to the alarmed process/device and generates an alarm message, which it sends on to the Fault Translation Process.
2. Fault Translation Process (FTP)

The fault translation process exists only on the site master. FCPs throughout the site send alarm information to FTP whose task is to diagnose the problem and decide the action to take in each case. FTP holds a table of fault scenarios and the action to be taken in each case. Once a course of action has been decided FTP will request the CA to carry out the required state change. For example, reset the alarmed device. In addition FTP will send the alarm message to the OMC. FTP keeps a record of all active alarm conditions in a table called the active alarms list. The active alarms list can be retrieved at the MMI with the command disp_act_alarms # where # is the site number.
3. System Audit Process (SAP)

The system audit process exists on every GPROC in a site. The SAP periodically performs a local audit where it checks the BSS software and forwards any faults found to the fault collection process for normal fault management processing. The SAP can also be set up to perform audits on the hardware in the site. The system operator from the MMI controls this and may set the audit to be scheduled in different ways. S S S Continuously at a set interval, e.g. every hour Once at a specific time e.g. at a specific time every 24 hours. At set intervals in a specific time range e.g. every 15 minutes between 0300 0400 hours each day.
There are two types of hardware audit: S S Cage Site Audits the hardware in the cage where the audit is scheduled. Audits the hardware in the site where the audit is scheduled.
Note:
In some cases the SAP will be invoked by the FTP in order to obtain more information on a fault condition.
424
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Fault Translation Process

OMC
O&M MMI
CENTRAL AUTHORITY
Fault Translation Process (FTP)
TABLE OF FAULT SCENARIOS AND ACTIONS
Fault Collection Process (FCP)
BSS DEVICES
HARDWARE/SOFTWARE
EMOTOROLA LTD. 2001
425
BSS Alarm Categories
ISSUE 3 REVISION 1

Fault reporting
Hardware alarms are automatically sent to the OMC by FTP, however they will not be output at the local maintenance terminal unless enabled from the MMI using the command enable_alarms # where # is the site number.
Alarm Categories
For the purpose of alarm reporting and clearing alarms are arrange in three categories:
1. Intermittent alarms:
These occur but generally do not remain active. Intermittent alarms are regarded as information and FTP does not add them to the active alarm list. However, FTP will increment a counter for every intermittent alarm received and if the counter reaches 6 FTP will request CA to reset the device associated with the alarm. For every minute that passes without the alarm occurring FTP will decrement the counter until it returns to zero. If a device is reset 3 times in 10 minutes the device will be taken out of service. Therefore if an intermittent alarm proves to be causing a serious problem the fault management software can take further action.
Alarm Throttle
There is a command, which can be used at the MMI to set a period of up to 24 hours to inhibit an intermittent alarm from being displayed. The alarm_throttle when set allows the first intermittent alarm to be displayed but will stop any further display for the period set. At the end of this duration the next receipt of the alarm will trigger another display including a count of the number of times the alarm occurred during the throttle period. This is a useful way of stopping intermittent alarms causing a distraction at the OMC.
2. FM Initiated Clear Alarm (FMIC)

After a fault condition has been fixed/cleared the fault management software will automatically clear the alarm from FTPs active alarm list.
3. Operator Initiated Clear (OIC)

When the fault has been dealt with the system operator must clear the alarm from FTPs active alarm list by using a MMI command.
426
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
1) Intermittent Alarms 2) Fault Man Initiated Clear 3) Operator Initiated Clear
EMOTOROLA LTD. 2001
427
Alarm Message Format
ISSUE 3 REVISION 1

Alarm messages contain information to help the system operator analyse the fault condition in order to take appropriate action to fix the problem. Alarm messages should be analysed by using the Alarm Handling at the OMC manual 68P02901W26 however all alarms follow the same basic format.
Message formats: Standard Alarm

The format shown is a standard alarm message. The asterisk (*) preceding each line indicates that this output is not a response to operator action, it has been generated by the software. <alarm code> <alarm Description> <severity> <device type> <device id> <(subtype)> <site> <cage> <slot> <date> <time> <alarm type> <hardware version> <additional info> Number representing the type of alarm Text describing the specific alarm Critical, Major, Minor, Warning, Clear, Investigate e.g. KSW, BSP, MSI etc Device identity made up of the 1st, 2nd and 3rd id elements Subtype of the device e.g. MSI, XCDR or GDP Which site the device is located at Which cage the device is located in Which slot the device is located in The date the alarm occurred The time the alarm occurred Intermittent, FMIC or OIC Hardware version of the device Refer to the alarms manual
428
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Standard Alarm Message Format

*Device Alarm Tag(hex): <config tag> * *(<Alarm code>) <alarm description> *Severity: <severity> Category: <category> *<device type><device id><(subtype)>[<function id>] *Site:<site> Cage:<cage> Slot:<slot> *Time:<date><time> *Alarm Type:<alarm type> Number of Suppressed Alarms: <suppressed> *FRU KIT Number: <kit number> *Hardware Version Number(hex): <hardware version> *Additional Info:<additional info> Example: *Device Alarm Tag(hex): 01800001 * *(242) Device(s) OOS due to action on this device *Severity: INVESTIGATE Category: EQUIPMENT *MSI 1 0 0 (MSI) *Site: 1 Cage: 15 Slot:16 *Time: Wed 25/3/1998 13:51:51:000 *Alarm Type: Fault Management Initiated Clear *FRU KIT Number: hvn= 4 *Hardware Version Number(hex): 04
EMOTOROLA LTD. 2001
429
ISSUE 3 REVISION 1
Alarm Severity
This field is a text string that indicates the severity of the alarm condition. Refer to the alarm manual for a more complete definition of the six possible strings: S S S S S S Critical Major Minor Warning Clear Investigate Site out of service Site partially out of service Repair required but no loss of service Maintenance required Condition cleared Unable to assign severity, check it out!
Alarm Category
This field indicates the general category of system operation affected by the alarm. Refer to the alarm manual for a more complete definition of the six possible strings: S S S S S S Communication Quality of service Processing Equipment Environment SWFM Notice E1 link failure Slow call setup Firmware problem on a peripheral card Radio failure Customer defined alarm (PIX) GPROC software fault
430
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Severity: Critical Major Minor Warning Clear Investigate
Category: Communication Quality of Service Processing Equipment Environment SWFM Notice
EMOTOROLA LTD. 2001
431
Switch Manager (SM)
ISSUE 3 REVISION 1
Switch Manager (SM)

The switch manager (SM) exists on the master GPROC only. It is responsible for controlling the TDM highway switch connection made on the KSW. At the BSC the SM is responsible for mapping the logical channels (CICs) on the A interface to the channels on the Abis interface on a per call basis. Dynamic switching at 16kbps enables call setup and handovers at the BSC. At the RXCDR and BTS switching is static therefore the switch manager at these sites will make connections at initialisation which will remain unchanged for the duration of operation or the network is re-configured.
432
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Switch Manager (SM)
Operations and Maintenance Switch Manager
S S S
SM BSC/RXCDR Static Switching RXCDR (16 kbit/s) Dynamic Switching BSC (16 kbit/s)
EMOTOROLA LTD. 2001
433
Initialisation Process
ISSUE 3 REVISION 1
The executive is responsible for starting the initialisation of the GPROC, using the Initialisation Process (IP) stored in EEPROM. The IP has no knowledge of the database therefore it works with default values for site configuration, such as a master GPROC in slot 20 or 24 of the first cage. Default positions for the OML to the OMC:
BSC OML defaults

1st default 2nd default 3rd Default 4th Default Cage 0 Slot 16 MMS 0 Timeslot 1 Cage 0 Slot 16 MMS 1 Timeslot 1 Cage 0 Slot 14 MMS 0 Timeslot 1 Cage 1 Slot 16 MMS 0 Timeslot 1
RXCDR OML defaults

1st default 2nd default 3rd Default 4th Default Cage 0 Slot 10 MMS 0 Timeslot 1 Cage 0 Slot 10 MMS 1 Timeslot 1 Cage 0 Slot 8 MMS 0 Timeslot 1 Cage 1 Slot 10 MMS 0 Timeslot 1
Initialisation in ROM
The IP first initialises the LAN and waits for all GPROCs at the site to broadcast their presence on the LAN. The master GPROC then takes control (ie the GPROC in slot 20 or 24). Assuming the site has no code available the IP then tests to see if there are enough peripheral cards to support a link to the OMC on one of the default link positions. I.e. KSW, GCLK and a MSI or XCDR in slot 16 or 14 (10 or 8 at a RXCDR). A link is then established to the OMC. The master GPROC checks to see if any GPROC has valid code objects (identical to those held at the OMC) that could be used to crossload to all GPROCs. If no code exists on any GPROC then the code will be downloaded from the OMC. When the master GPROC has received all the code objects from the OMC it will crossload all the GPROCs at the site over the LAN. On receipt of a successful crossload from all GPROCs the master broadcasts a Jump to RAM message.
434
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Initialisation Process in ROM

Reboot
Establish LAN
Bring GPROCs on to LAN
Select master GPROC
Check if there is enough equipment for a download of code
Y
Connect to OMC within 6 mins Is a download required?
Jump to RAM
N N
Download Code
Is there code in RAM? Cross Load code to all GPROCs
EMOTOROLA LTD. 2001
435
Initialisation in RAM
ISSUE 3 REVISION 1
Once the system has moved to RAM the IP starts again but this time it executes from RAM. The move to RAM causes the LAN to deactivate therefore the first task is to re-establish the LAN. When the LAN is up and running the IP checks to see if a valid database exists on any of the GPROCs. If a database exists the IP co-ordinates a crossload to all GPROcs. If no database is available (it is not necessary to download a database from the OMC) the IP waits for 45 seconds before re-booting the site and starting the initialisation process again. A system operator has this time to enter a MMI command called sysgen_mode on. This tells IP that a database script file is going to be provided. A database script file contains all the necessary information to allow the master GPROC to build a database object. The IP then reinitialises the site and goes through the IP process as describe so far. When it gets to this point the second time it stops and waits for the script to be provided. The script is uploaded to the GPROC via the TTY interface from the Local Maintenance Terminal. Once the script has been uploaded the system operator enters the command sysgen off to return the site to normal operation. At this point the CM and CA processes check that the database provided is sane. If for any reason the database is invalid the IP will remain in sysgen mode (indicated by the MMI prompt) and waits for corrections to be made with MMI commands or a new script to be entered. A report of why the script failed is provided to aid correction. When sysgen is successful the IP crossloads the new database object to all GPROCs and IP initiates the CA process which then takes control. The CA then configures the site according to the database and takes it into call processing mode. At the BSC the CA will then work on bringing the BTS sites into operation.
436
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
RAM
Reestablish LAN
Does a database exist?
N
Inform user a sysgen is required Do all GPROCs have the same database?
N
Reboot
Has sysgen mode been started within 45 seconds?
XLoad Y
Ask user to reset site
Initialise CA
continue bootup
Sysgen mode
EMOTOROLA LTD. 2001
437
Call Processing
ISSUE 3 REVISION 1
Call Processing
The purpose of Call Processing (CP) is controlling communications between the MSC, BSC, BTS and MS. Call Processing and the Radio Subsystem (RSS) interact to control call set-up and clearing, handovers, encryption and movement of direct transfer application part (DTAP) messages between the MSC and MS. In the Motorola software architecture the call processing system has been split into two parts. One part is executed at the BSC the other at the BTS. This is a departure from the normal architecture that distributes the call processing functions only at the BSC. With the Motorola structure the BTS takes some of the CP functions along with all of the RSS functions.
CP at the BSC
S S S S Connectionless manager (CLM) Message Transfer part L3 (MTPL3) SCCP pre-processor (SCCP) SCCP state machine (SSM)
CP at the BTS
S S S S Radio Resource State Machine (RRSM) Cell Resource Manager (CRM) Cell Broadcast Scheduler (CBS) Radio Channel Interface (RCI)
The SCCP state machine (SSM) at the BSC, manages the SCCP interface to the MSC. The Radio Resource state machine (RRSM) manages the radio resource interface to the Radio Subsystem. The division of the call processing state machine into two levels allows each state machine to handle common procedures at its own level without knowing the background for the specific request. For example, if the SSM sends a release radio channel to the RRSM, the RRSM can invoke the normal radio channel release procedure without knowing if the channel is being released because of a Clear Command from the MSC, a break in the SCCP connection, or O & M intervention. Similarly, if the SSM receives a radio channel released message from the RRSM, it proceeds in the same manner regardless of whether this message was generated as a result of a timer expiry or a radio channel link error. The advantage of this is a reduction in the amount of signalling required between the BSC and BTS for call processing.
438
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Call Processing
Call Processing
S S Collection of layer 3 Protocols Functions Call set-up/clearing Message transfer (DTAP/BSSMAP) Control handovers CP RSS Interface Encryption
Two state machines for CP. CPBSC CLM MTPL3 SCCP SSM SM AM CPBTS RRSM/RCI CRM CBS RCI AM
EMOTOROLA LTD. 2001
439
Call Processing at the BSC
ISSUE 3 REVISION 1

Message Transfer Part L2 (MTP_L2)
The MTP_L2 process is responsible for the data link layer operations (layer 2 processing) of the MTL link at the BSC. It terminates the C7 signalling on the LCF GPROC controlling the MTL link at the BSC and provides error detection and flow control for the link.
Message Transfer Part L3/SCCP Preprocessor

The MTP_L3 process also executes on the LCF GPROC controlling the MTL link and is responsible for maintaining the signalling link between the BSC and MSC. As part of the MTP_L3 process there is a function called the SCCP Preprocessor responsible for determining the type of messages being passed (DTAP/BSSMAP) and routing the messages internally at the BSC.
SCCP State Machine

The SSM executes on LCF GPROCs controlling RSLs to BTS sites. The SSM process is responsible for call setup, maintenance, release and the primary control of handovers. A handover evaluator process is part of the SSM process and is responsible for determining the target BTS for a handover. The SSM also provides a call trace facilility within the BSS.
Connectionless Manager
The CLM executes on the master GPROC (BSP) at the BSC and is responsible for connectionless signalling procedures on the MTL link to and from the MSC. Connectionless procedures are all procedures that are needed to maintain operation between the BSS and the MSC that are not directly connected with calls. Examples are circuit blocking, reset of circuits, global reset and signalling point inaccessible.
440
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

To MSC LCF
MTP L2
17
MTP L3
16
LCF To BTS
SSM
33
HO EVALUATOR
BSP
CLM
35
AM
SM
64
EMOTOROLA LTD. 2001
441
Call Processing at the BTS
ISSUE 3 REVISION 1

The following call processing functions all execute on the master processor at the BTS and will not be found active at the BSC.
Radio Resource State Machine (RRSM)

Radio Resource State Machine (RRSM) is responsible for maintaining the state of the radio channels allocated to calls at the BTS. This involves channel requests for call set-up, maintenance and release on call termination.
Radio Channel Interface (RCI)

The Radio Channel Interface provides an interface between Radio Subsystem processes and Call Processing. Calls are tracked within Call Processing by a unique identifier called the SCCP reference number, however within the Radio Subsystem calls are tracked by a Radio Channel Identifier. The RCI process provides a mapping function for SCCP references to Radio Channel Identifiers.
Cell Resource Manager (CRM)

The Cell Resource Manager (CRM) is responsible for managing the allocation of radio resources within the BTS site. Upon request for a radio channel, CRM determines what radio resources to use based on how the cell is being used, loading on the cell and interference levels on the available resources. CRM also takes care of intracell handovers, dynamic configuration of traffic channels to SDCCH and generation of SCCP reference numbers at call set-up.
Cell Broadcast Scheduler (CBS)

The Cell Broadcast Scheduler (CBS) is responsible for Short Message Service Cell Broadcast message scheduling. The Cell Broadcast Centre (CBC) sends messages and scheduling information to the BSC and this is forwarded to the CBS at the BTS. The CBS works with the CRM and RRSM to ensure SMSCB messages are sent out. Both CBC and OMC can send messages for broadcasting but CBC messages will take priority over OMC messages.
442
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
To BSC
BTP
AM
CRM
RRSM RCI CBS
DHP
RSS
EMOTOROLA LTD. 2001
443
Allocation Manager (AM)
ISSUE 3 REVISION 1

The Allocation Manager process exists at the BSC and the BTS to manage the dynamic allocation of terrestrial channels between the BSC and BTS. When dynamic allocation is in use the Cell Resource Manager sends a request to the allocation manager at the BTS for a terrestrial backhaul channel. That is, a 16Kbps sub-channel on an E1 link to the BSC. The BTS Allocation Manager forwards the request to the Allocation Manager at the BSC, which in turn takes responsibility for setting up the channel with the BSC Switch Manager process. When the Cell Resource Manager requests a backhaul channel it identifies the TCH with a Radio Channel Identifier (RCI). This is sent by the BTS AM and used at the BSC Switch Manager to correlate between the Radio Channel Identifier (RCI) and the Network Channel Identifier (NCI) used to identify the terrestrial backhaul channel. On release the RCI and NCI become available for another call although not necessarily as a pair as would be the case without dynamic allocation where the RCI specifically identifies timeslots on the air interface to 16Kbps channels on the terrestrial link between the BTS and BSC.
444
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Call Processing Allocation Manager

SM
SSM BSC
TCHs
AM
BTS RRSM AM
CRM SM
EMOTOROLA LTD. 2001
445
Radio Subsystem
ISSUE 3 REVISION 1
Radio Subsystem
Overview
The Radio Subsystem (RSS) is a collection of application processes responsible for managing the radio hardware at the BTS. The RSS consists of five processes: 1. 2. 3. 4. 5. RSS Abis Interface RSS Layer 2 Protocol RSS Layer 1 Protocol RSS Configuration and Fault Management Handover Detection and Power Control
RSS Abis Interface (Abis)

Abis supports the interface and message protocol between the RSS and Call Processing (CP). It supports a pseudo Abis interface, designed to conform closely with GSM requirements between the RSS and the Call Processing function located at the BTS (RRSM/RCI, CRM and CBS). All messages between CP and RSS go through the RSS Abis to RCI. The main responsibilities of the RSS Abis interface are: S S S S Initialising the RSS Abis interface to call processing. Checking the validity of downlink messages. Translation of messages received from CP into internal RSS messgaes. Translation of messages to CP from the RSS.
RSS Layer 2 Protocol (Layer 2)

Layer 2 provides the data link layer processing of the air interface signalling link. DTAP and System information messages for the mobile station are formatted by Layer 2 for the LAPDm protocol used on the air interface. Similarly DTAP and System messages received from the mobile are converted back from LADm to a format suitable for their destination. Error detection and flow control on the air interface signalling link are performed as part of the Layer 2 function.
446
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Radio Subsystem
Radio Subsystem (RSS)
S S
Software Interface procedures between BSS RF hardware and mobile station (MS) Each subsystem is contained within its respective TCU
EMOTOROLA LTD. 2001
447
ISSUE 3 REVISION 1

The layer 1 process interfaces the software processes in the RSS to the hardware interface to the radio hardware. The functions of Layer 1 are: S S S S S S S Download of firmware to the radio hardware Message link between RSS Hardware Reports on communication problems between the RSS and radio hardware to the Fault Collection Process (FCP) Maintains a database for CRM regarding multiple pages, immediate assignments and immediate assignment rejects. Translates downlink messages received from Layer 2 into a format suitable for transfer to the radio hardware Translates uplink messages received from the radio hardware into layer 2 messages Obtaining timer information for nonsynchronised handovers
RSS Configuration and Fault Management (CFM)

The Configuration and Fault Management process controls initialisation of the RSS and supervises codeload and configuration of the radio hardware. CFM takes responsibility for configuration changes during operation and reporting of alarms from the radio hardware.
448
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Radio Subsystem
To call processing To fault management
DHP
Abis
CFM
Layer 2 HDPC
Layer 1
To the radio hardware
EMOTOROLA LTD. 2001
449
Handover Detection and Power Control (HDPC)
ISSUE 3 REVISION 1

The handover Detection and Power Control (HDPC) process has by far the most function to fulfil within the RSS. It controls the transmission power of the mobile station (Uplink) and the transmission power of the BTS (Downlink) on a per timeslot basis. The object is to keep transmission power in the system to a minimum to avoid unnecessary interference. HDPC is also responsible for calculating the mobiles timing advance base on measurements by the BTS radio hardware. HDPC is also responsible for detecting when a handover is required based on the measurement reports received from the mobile and the BTS radio hardware. Idle timeslots are monitored by the radio hardware for interference, HDPC collects the measurements into a report to be sent periodically to CRM where they are used to order the radio resources so that CRM can allocate channels with the least uplink interference. Once a call to a mobile has been established, if the mobile was then to leave the system without releasing, the radio channel resource would be wasted. To protect against this HDPC monitors the SACCH messages from all mobiles in calls. The HDPC process will decrement a counter for every SACCH message that fails to appear from a mobile and if the count reaches zero the channel will be released by the BTS. If a SACCH message is successfully received after the counter has been decreased the count will be incremented by two up to but not above the initial value of the counter. In this way the counter is biased to keeping the channel open but if the call is lost then the radio channel will be released and so become available for use by another call. The initial value of the SACCH counter is determined in the configuration database and informed to HDPC at initialisation. The HDPC process is not a true RSS process but because of the Motorola architecture it resides with the RSS processes. For this reason all messaging to and from the HDPC process is in GSM Abis format so that in theory the location of the HDPC is interchangeable and it could be executed at the BSC if required.
450
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Handover Detection and Power Control
Functions S S S S S S Controls transmission power of MS Controls the timing advance of MS Controls the transmission power of the BSS Determine the need for handover (intra_BSS and inter_BSS) Monitors the interference level on idle channels Detects loss of SACCH messages (conserving resources)
EMOTOROLA LTD. 2001
451
Handover Decision Criteria
ISSUE 3 REVISION 1

For intra-BSS handovers the at BSC will select the cell to which a call is to be handed over to based on the following criteria. 1. 2. 3. 4. 5. Receive Quality (Uplink and Downlink) Receive Signal Strength (Uplink and Downlink) Distance (Timing advance) Power Budget Interference
At the BSC each of the five criteria are dealt with in order of priority where receive quality is the highest and power budget is the lowest. This means that if there are more bids for handovers than channels available the bids with handover cause of receive quality will be allocated first whilst those with power budget cause will be last. Target cells for a handover can also be placed priority and if two target cells meet the same criteria for handover selection then the cell with the highest priority will be selected. This enables macro cells in a multi-layer network to be gven a low priority and so encourage mobiles to stay in the micro layer. Channel congestion in the best cell will cause the choice of the second best cell. If no second cell is available and call queuing is employed then the MS will be placed in the queue until the relevant cell becomes available. Mobiles in a queue for handover take priority over new calls.
452
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

S S S S S Receive Quality Receive Signal Strength Distance Power Budget Interference
Target Cell Priority

S S S List of candidate Priority Interference Level
EMOTOROLA LTD. 2001
453
Motorola Systems
ISSUE 3 REVISION 1
Motorola Systems
Using the Motorola system, the control of the radio and terrestrial circuits are split between the BSC and BTS. The BSC retains the processes that control the terrestrial links to the MSC and the final decision process concerning handovers. The BTS has all processes necessary to monitor and control the radio channels and because of this the amount of signalling required between the BSC and BTS is reduced. This maximises the use of the E1 link between the BSC and BTS as more timeslots are available for carrying traffic than with architecture that locates all the call processing functions at the BSC.
454
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Motorola Systems
Motorola System MSC

MTP L3/SCCP PREPROCESSOR
Connectionless Manager
SCCP State Machine
Allocation Manager
Switch Manager
BSC
Radio Resource State Machine
Cell Resource Manager
Allocation Manager
Radio Channel Interface
BTS
Radio Subsystem
D D D
Radio Subsystem
Radio Channel Process
D D D
EMOTOROLA LTD. 2001
455
Call Establishment
ISSUE 3 REVISION 1
Call Establishment
The following description covers the interprocess communication to place a mobile on a DCCH and have the mobile in communication with the MSC. 1. 2. 3. 4. 5. 6. The mobile accesses the system with a Random Access burst on the BCCH. The RSS passes the request onto the RRSM via the RCI in the form of a Channel Required message. RRSM asks the CRM to assign a SDCCH channel and the CRM responds. RRSM tells the RSS which DCCH the mobile is to go to and the RSS activates the channel. When channel activated, the RSS informs the RRSM. The RRSM then tells the mobile via the RSS on an Access Granted Channel, which DCCH the mobile is to move to. The mobile moves to the DCCH and establishes two way communication with its allocated BTS. The Mobile forwards CM Service Request, telling the RRSM what the mobile wants to do. Is it responding to a Page from the MSC? doing a Location Update? IMSI Deregistration? wanting to establish a call? trying to salvage an established call? 7. 8. The RRSM forwards the CM service request up to the SCCP State Machine (SSM). The SSM then has to request the MSC to handle the call. RSS: RRSM: CRM: SSM: MTP: Radio Subsystem Radio Resource State Machine Cell Resource Manager SCCP State Machine Message Transfer Port
456
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Call Establishment
Call Establishment
BTS FUNCTIONS
Mobile
Random access
RSS
CRM
RRSM/ RCI
Channel required Channel required Channel assigned Choose DCCH
Base site checks out Channel AGCH M obile moves to DCCH
SDCCH Channel Activation Channel Activation Acknowledgement Immediate Assign Command
BSC FUNCTIONS
SSM
MTP
Establish Indication CM Power Control M S Power Control
Service Requirement
Initial Layer 3 Info CM
Service Req Complete Layer 3 Information
MSC
MSC Requested to handle call
EMOTOROLA LTD. 2001
457
Voice Channel Assignment
ISSUE 3 REVISION 1

The following text describes the interprocess communication for the assignment of a mobile from a DCCH to a traffic channel. This procedure assumes that all authentication has taken place on the DCCH. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. The MSC sends a message to the SSM assigning the mobile a terrestrial circuit. The SSM sends an initiate assignment command to the RRSM to assign a channel to the mobile. The RRSM asks the CRM to assign Traffic a channel. The CRM responds with the channel. The RRSM then asks the RSS to supply the timing information for the mobile concerned. The RRSM then tells the RSS to activate the required Traffic Channel. The RRSM then instructs the mobile via the RSS to move onto the new traffic channel. The mobile now moves to the new traffic channel and establishes signalling links. The RRSM then informs the SSM that mobile is on its new channel and signalling links have been established, and deactivates the SDCCH channel. The SSM then tells the SM to connect the radio channel to the terrestrial MSC circuit. The SM responds when complete. The SSM then tells the MSC that the mobile is on the new channel and that the radio channel has been connected to the MSC channel.
When this procedure is completed, it leaves the mobile on its new traffic channel and talking to the MSC.
458
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1

BTS FUNCTIONS BSC FUNCTIONS
RSS
CRM
RRSM/ RCI
SM
SSM
MTP
DTI Assignment
MSC
Request
Initiate Assignment Assign TFC
Mobile
Ch Request Channel Assigned Physical Context Req Physical Context Confirm Channel Activation Channel Activation Ack Assignment Command
Mobile timing advance obtained from DCCH
Mobile moves to TFC Ch
Ch info to M obile Establish Indication Data Indication Assign Com Deallocate DCCH Assignment Successful Connect Radio Ch to Terrestrial Ch Mobile on new channel
Connection Req Switch Resp Assign Complete Assign Complete
EMOTOROLA LTD. 2001
459
Intra BSS Handover
ISSUE 3 REVISION 1
Intra BSS Handover

The following text describes the interprocess messages for an intraBSS handover. The term source describes the cell from which the mobile is moving, whilst target describes the cell to which the mobile is moving. 1. 2. 3. 4. 5. 6. The handover Detection and Power Control process decides whether a Handover is required. The RSS forwards the message to the SSM (Handover Evaluation Process). The SSM (Handover Evaluation Process) decides where the mobile is to move and sends a message to the CRM of the target cell requesting a channel. The CRM target then tells the RRSM target that a channel has been assigned. The RRSM target tells the RSS target to activate the channel. Target RSS activates the channel and sends a channel activation acknowledgement to target RRSM. Target RRSM then informs SSM at the BSC of the channel allocation for the handover. The SSM then sends the RRSM source the initiate handover; message which contains the channel information for the mobile. This information is then passed via the RSS source to the mobile. The mobile then moves to the new channel. The mobile is detected on the new channel by the RSS target and the signalling links are established between RSS target and the mobile. The RRSM target is informed that the mobile has been detected on the new channel and signalling links have been established. The RRSM target informs the SSM that the mobile has been detected and is completing the link establishment. This enables the SSM to inform the SM to change the traffic connection to the new BTS. RRSM target then informs the SSM that the handover has been successful. The SSM then informs the MSC as to the new location of the mobile. The SSM then tells the RRSM source to release the mobiles old radio channel.
7.
8. 9. 10.
11. 12.
The handover process is now complete.
460
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Intra BSS Handover
Intra BSS Handover
SOURCE BTS Mobile RSS

Handover detection procedure Handover recognised
BSC SM SSM
RRSM
TARGET BTS RSS CRM RRSM
Request for channel
Channel Assigned + Activated
Handover Allocation
Initiate handover Mobile moves to new channel Handover Command
M S Access Phys Info
Handover detected
Handover Detected
Make Connection Handover Successful Release Radio Channel
MSC inform
EMOTOROLA LTD. 2001
461
Intra BSS Handover
ISSUE 3 REVISION 1
462
EMOTOROLA LTD. 2001
Chapter 5
Appendix A Cabinet Interconnecting Examples
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
EMOTOROLA LTD. 2001
iii
ISSUE 3 REVISION 1
Appendix A
Appendix A
EMOTOROLA LTD. 2001
51
Introduction
ISSUE 3 REVISION 1
Introduction
There are two methods of inter-cabling GSM racks: S S E1/T1 links (these lines can also be over fibre optic cables). Fibre optics
E1/T1 Links
Used for links to the MSC or for Daisy chaining to other BSS racks. these lines terminate on either the BIB/T43IB mounted on the top Interconnect panel.
Fibre Optics
Used generally for connecting remote cabinets (racks) close together ie. the same building. Also used for expansion/extension of functions between cabinets. The fibre optic cables are fed out of the rack via Below waveguide Cutoff filters which exit through the top Interconnect panel of the cabinet.
52
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Introduction
Inter-Cabinet Connection
S S
E1/T1 Links (T43IB, BIB) Fibre Optics remote cabinets (50 metre max) expansion/extension
EMOTOROLA LTD. 2001
53
System Numbering
ISSUE 3 REVISION 1
System Numbering
Definitions
Site:
Identifies the Location of the cabinets which are on the same LAN. There may be more than one site at any one physical location [valid range= 0 to 40].
Cabinet (CAB):
Identifies a cabinet within a site. [Valid range= 0 to 15].
Cage:
Identifies the BSU/RXU within a cabinet. The cage number setting on the LANX card. [Valid range= 0 to 15] must be equal to the setting in the database. Valid identities for cages at a BSC site are 0 to 13. The 1st BSC cage must be numbered 0. Valid identities for cages at a BTS site are 15 to 2. The 1st BTS cage at any site must be numbered 15. Valid identifies for cages at a RXCDR are 0 to 3. The 1st RXU cage must be numbered 0. The RXCDR is a standalone network element and so its site number can always be 0.
54
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
System Numbering
System Numbering
E1/T1 Cable Fibre Optics
CAGE (BSU) CAGE (BSU) CAGE (BSU)
BSC SITE 0
BTS
BTS
BTS
Fibre Optics
F(15)
CAGE (BSU)
E(14)
D(13)
BTS SITE 1
BTS
BTS
EMOTOROLA LTD. 2001
55
Kiloport/Timeslot Switch Extender
ISSUE 3 REVISION 1

Introduction
The Kiloport Switch Extender (KSWX) board is a multifunction board which is responsible for the optical transmission of all Time Division Muliplexed (TDM) bus information between shelves. It is also responsible for the distribution of received clock reference pulses. There are three modes in which the KSWX may operate, these modes depend on which slot is used on the shelf. S S S Expansion (EXP) mode; expands the TDM bus between kiloport/timeslot switches (KSW/TSW). Remote (RMT) mode; extends the TDM bus to another BSU shelf for use by the highway interface modules contained in that shelf. Local (LCL) mode; terminates the TDM bus extended by the remote KSWX and the TDM Clock and reference pulses distributed by the clock extender (CLKX).
The Kiloport Switch Extender is required when a site has more than one cabinet, it extends the 1024 ports of a KSW/TSW to other shelves and/or interconnects up to 4 KSW/TSW modules. When extending the TDM switch highway between two BSU shelves a KSWX module is required in each shelf. For each operating mode of the KSWX, the following number of boards lots are allocated per KSW/TSW in the BSU shelf: KSW A EXP 3 Slots (U21, U22, U23) RMT 5 Slots (U24, U25, U26, U27, U28) LCL 1 Slot KSW B EXP 3 Slots (U9, U8, U7) RMT 5 Slots (U6, U5, U4, U3, U2) LCL 1 Slot (U0) (U1)
56
EMOTOROLA LTD. 2001
AI 0 AI AI 1 2
BTC 0 KSW/TSW A RM T RM T RM T RM T EXP EXP EXP KSWX A2 KSWX A1 KSWX A0 LANX A LANX B KSWX A0 KSWX A1 KSWX A2 KSWX A3
ISSUE 3 REVISION 1
RM T
KSWX A4
EMOTOROLA LTD. 2001

spare GPROC 7 M ASTER GPROC 6 GPROC 5 GPROC 4 GPROC 3 M ASTER GPROC 2 GPROC 1 GPROC 0 XCDR 0 XCDR 1 DRI(M ) 4 XCDR 2 XCDR 3 DRI(M ) 3 XCDR 4 XCDR 5 DRI(M ) 2 XCDR 6 XCDR 7 DRI(M ) 1 XCDR 8 M SI 0
KS0 MS 0 DR5
PIX/BBBX
MS 1
DR4
PIX/BBBX
M SI 1 M ASTER M SI 2
PIX/BBBX

DRIM M SI 3 M ASTER M SI 4 M SI 5 M SI 6 M SI 7 M SI 8 5 DRIX 4 DRIX 3 DRIX 2 DRIX 1 DRIX 0 EXP KSWX B0
DR3

L 9
XCDR 9 M SI 9
BSU Shelf Modules Slot Assignment Layout
U28U27U26 U2 U24 U2 U2 U21 U20 U U1 U1 U1 U1 U1 U13U12U11U10 U U 5 3 2 19 8 7 6 5 4 9 8
L2 L2 L2 L2 L2 L2 L2 L2 L2 L19 L1 L1 L1 L1 L1 L1 L12 L1 L1 8 7 6 5 4 3 2 1 0 8 7 6 5 4 3 1 0

L L 8 7 L 6 L 5 L3 L 1 U 7
DRI(M ) 0 XCDR 10 XCDR 11 M SI 10 M SI 11
MS 2
EXP KSWX B1 CLKX A0 EXP KSWX B2 CLKX A1 RM T KSWX B0
DR2 DR1
U U 6 5
GCLK A
CLKX A2 RM T KSWX B1
MS 3
CLKX B0 RM T KSWX B2 CLKX B1 RM T KSWX B3 GCLK B KSW/TSW B BTC 1 CLKX B2 RM T KSWX B4 LCL KSWX A LCL KSWX B U0
DR0
U U U U 4 3 2 1
G K0
57
KS1
L 0
Kiloport/Timeslot Switch Expansion
ISSUE 3 REVISION 1

The switching capacity of a system may be expanded by operating two, three or four interconnected KSW/TSWs on mutually exclusive TDM buses. The resulting switching fabric will support 2048, 3072 or 4096 TDM timeslots, respectively. When any form of extension or expansion is carried out then a KSWX card must be positioned in the LCL slot, to enable timing to be Rx from a CLCKX card.
Example 1
2 x KSWs are connected together to give 2048 timeslots; ie. BSSC cabinet with 2 x BSUs. A total of 4 x KSWX cards required (No redundancy). Note: The extension of the CLOCK is not shown for clarity.
58
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
KSW/TSW Expansion Example 1

CAGE 0
Rx
Tx
KSWX (E)
K S W A
CLKX
SLOT U21
EXP A0
SLOT U1
GC L K
L C L
SLOT L27 FIBRE OPTIC CABLE CAGE 1
Rx
Tx
KSWX (E)
SLOT U21
SLOT U1
K S W A
EXP A0
L C L
SLOT L27
EMOTOROLA LTD. 2001
59
Kiloport/Timeslot Switch Expansion (4 x KSW)
ISSUE 3 REVISION 1

Example 2
Kiloport Switch Expansion can be upto 4 x KSW giving a total of 4096 ports. This requires each BSU cage to be fitted with 3 x KSWX in slots U21U23. Each BSU is connected to every other BSU. This takes a total of 12 x KSWX cards, and 4 x KSWX cards in the LCL slots. Note: The above example refers to expanding KSW A. KSW B would follow the same principle but different card lots would be used. Also, clock extension is not shown for clarity.
510
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
KSW Expansion Example 2

CAGE 0

K S W A SLOT L27
CLKX
SLOTS U2123
SLOT U1
G C L K
L C L
CAGE 1

K S W A SLOT L27
SLOTS U2123
SLOT U1
L C L
CAGE 2

K S W A SLOT L27
SLOTS U2123
SLOT U1
L C L
CAGE 3

K S W A SLOT L27
SLOTS U2123
SLOT U1
L C L
EMOTOROLA LTD. 2001
511
Kiloport Extension
ISSUE 3 REVISION 1
Kiloport Extension
The function enables the local KSW to be extended to a remote BSU shelf and provide the TDM bus highway with KSW A (slot 27). This requires a KSWX in slot U24 (RMT) connected to the KSWX slot U1 (LCL) in the remote cage Tx (bottom fibre optic connection) to Rx (top fibre optic connection). This requires 3 x KSWX cards. Note: Clock extension is not shown for clarity.
512
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Kiloport Extension
KSW Extension
CAGE 0
Rx
Tx
KSWX (R)
K S W A
FIBRE OPTIC CABLE CAGE 1
RMT A0 LCL A
BSU
Required for clock extension
CLKX
SLOT U24
SLOT U1
G C L K
SLOT L27
BSU
SLOT U1
Rx
Tx
KSWX (L)
No KSW
LCL A
EMOTOROLA LTD. 2001
513
Clock Extension
ISSUE 3 REVISION 1
Clock Extension
The clock extender board (CLKX) provides the extension of the system clock and reference signals from the Generic Clock (GCLK) to the other BSU shelves via fibre optics. The GCLK board generates the system clock and reference which are multiplexed into one signal to reduce the number of interconnection between shelves. Up to three CLKX boards per GCLK each with six outputs, may be used to send the Clock signals to 17 shelves (one output must be used for local clock). The connection requires the use of a KSWX, in the Local (LCL) mode, for each extension. Any of the six fibre outputs can be connected to the middle fibre optic connection (KSWX)
514
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Clock Extension
CLKX Extension
CAGE 0
SLOT U7
6 O/Ps
CLKX A0
BSU
CLKX
SLOT L5
GC L K A
SLOT U1 LCL A
Fibre Optic Cable
KSWX (L)
CAGE 1
BSU
SLOT U1 LCL A
KSWX (L)
No GCLK
EMOTOROLA LTD. 2001
515
KSW and GCLK Extension (2 Cabinets)
ISSUE 3 REVISION 1

When the KSW has been extended to another shelf, the received clock signal uses the same KSW (L) board as shown. This requires three fibre optic cables for the interconnection. Note: Redundancy is not shown.
516
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
KSW/TSW and GCLK Extension
Rx
Tx
KSWX (R)
CAGE 0
SLOT U24 RMT A0
K SW

SLOT L27
BSU
SLOT U7 CLKX A0

SLOT L5
CLKX
GC L K A
SLOT U1 LCL A
KSWX (L)
CAGE 1 Fibre Optic Cable
BSU
SLOT U1 LCL A
Rx
KSWX (L)
Tx
No KSW/TSW
No GCLK
EMOTOROLA LTD. 2001
517
Local Area Network Extender (LANX)
ISSUE 3 REVISION 1

Introduction
The LANX provides the capacity to extend one of the two LANs to other shelves via optical fibres. In addition, the LANX provides a central point for the LAN connections from all the GPROC boards which sit on the LAN ring. This feature allows the LANX to switch empty board slots or failed boards off the LAN to keep the LAN in operation. Two LANX boards are used in a given shelf to provide primary and redundant interfaces to other shelves or racks. Each LANX board receives the LAN data from another shelf, routes the LAN data to the first GPROC, receive the LAN data back from the first GPROC, and route that to the second GPROC, and so on until all GPROCs have received the LAN data. The LAN data output of the last board is converted to an optical fibre signal and sent to the next shelf. If a board is not present or has failed, the LANX bypasses it and passes the LAN data to the next GPROC. Each LANX board has two serial buses for communication with the GPROC board. The selection between which bus to use is controlled by the GPROC boards serial interface circuitry. Connection of the LAN via Rx (top fibre optic connection) to Tx (bottom fibre optic connection) to ensure a complete ring. Diagram shows only one LAN extension.
518
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
LANX Extension (2 cages)

CAGE 0
Rx
SLOT U20
LANX
Tx
LANX A
BSU
CAGE 1
SLOT U20 LANX A Rx
BSU
Tx
EMOTOROLA LTD. 2001
519
LANX Extension
ISSUE 3 REVISION 1
LANX Extension
Diagram shows 4 cage LANX extension, (only one LAN shown for clarity).
520
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
LANX Extension
LANX Extension (4 cages)

CAGE 0 Rx SLOT U20
Tx
LANX A
BSU
CAGE 1 SLOT U20
BSU
LANX A Rx Fibre Optic Cable Tx
CAGE 2 SLOT U20
BSU
Rx
LANX A
Tx
CAGE 3 SLOT U20
BSU
Rx
LANX A
Tx
EMOTOROLA LTD. 2001
521
LANX Extension
ISSUE 3 REVISION 1
522
EMOTOROLA LTD. 2001
Chapter 6
Glossary of technical terms and abbreviations
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
ii
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Chapter 9 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X ......................................................................... Z .........................................................................
i
91 92 95 98 912 915 917 919 921 922 924 925 927 931 933 935 938 939 942 946 949 950 951 952 953
EMOTOROLA LTD. 2001
iii
ISSUE 3 REVISION 1
iv
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Numbers
Numbers
# 2 Mbit/s link Number. As used in this manual set, the term applies to the European 4-wire 2.048 Mbit/s digital line or link which can carry 30 A-law PCM channels or 120 16 kbit/s GSM channels. 4th Generation Language.
4GL
EMOTOROLA LTD. 2001
61
ISSUE 3 REVISION 1
A
A interface A3 A38 A5 A8 AB Abis interface Interface between MSC and BSS. Authentication algorithm that produces SRES, using RAND and Ki. A single algorithm performing the function of A3 and A8. Stream cipher algorithm, residing on an MS, that produces ciphertext out of plaintext, using Kc. Ciphering key generating algorithm that produces Kc using RAND and Ki. Access Burst. Interface between a remote BSC and BTS. Motorola offers a GSM standard and a unique Motorola Abis interface. The Motorola interface reduces the amount of message traffic and thus the number of 2 Mbit/s lines required between BSC and BTS. Answer Bid Ratio. ACDC Power Supply module. Alternating Current. Access Class (C0 to C15). Application Context. Automatic Congestion Control. Associated Control CHannel. ACKnowledgement. Accumulated Call meter. Address Complete Message. AC Power Interface Module. Used in M-Cell6 indor ac BTS equipment. AC Power Supply Module. Used in M-Cell6 BTS equipment. Associated Control Service Element. Antenna Combining Unit. Analogue to Digital (converter). ADministration Centre. Analogue to Digital Converter. ADvanced Communications Control Protocol. ADMinistration processor. ADMINistration. Abbreviated Dialling Number. Adaptive Differential Pulse Code Modulation. Application Entity. Accoustic Echo Control. Additional Elementary Functions.
ABR acdc PSM ac AC AC ACC ACCH ACK, Ack ACM ACM ACPIM AC PSM ACSE ACU A/D ADC ADC ADCCP ADM ADMIN ADN ADPCM AE AEC AEF
62
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
AET
Active Events Table. Alarms and events are sent to the Events Log in the GUI. Different operators will have different subscription lists. All alarms and events are sent to the AET before they are re-routed to different subscription lists. Automatic Frequency Control. Absolute Frame Number. Automatic Gain Control. Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH. Action indicator. Artificial Intelligence. Alarm Interface Board. A class of processor. The radio link between the BTS and the MS. Amplitude Modulation. Automatic Message Accounting (processor). Cell broadcast mobile terminated message. A message broadcast to all MSs in a cell. Advice of Change. Advice of Change Charging supplementary service. Advice of Change Information supplementary service. Automatic Output Control. Application Process. Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number. Automatic ReQuest for retransmission. Address Resolution Protocol. Association Control Service Element. An ASE which provides an AP with the means to establish and control an association with an AP in a remote NE. Maps directly onto the Presentation layer (OMC). Application Service Element (OMC) Application Specific Entity (TCAP). Abstract Syntax Notation One. Alarm and Status Panel. Answer Seizure Ratio. All Trunks Busy. Antenna Transceiver Interface. ATTach. Automatic Trunk Testing Subsystem. Access Unit. Authentication Centre. A GSM network entity which provides the functionality for verifying the identity of an MS when requested by the system. Often a part of the HLR.
AFC AFN AGC AGCH Ai AI AIB AIO Air interface AM AMA AM/MP AoC AoCC AoCI AOC AP ARFCN ARQ ARP ASCE
ASE ASE ASN.1 ASP ASR ATB ATI ATT (flag) ATTS AU AuC
EMOTOROLA LTD. 2001
63
ISSUE 3 REVISION 1
AUT(H) AUTO
AUThentication. AUTOmatic mode.
64
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
B
B Interface BA BAIC BAOC BBBX BBH BCC BCCH Interface between MSC and VLR. BCCH Allocation. The radio frequency channels allocated in a cell for BCCH transmission. Barring of All Incoming Calls supplementary service. Barring of All Outgoing Calls supplementary service. Battery Backup Board. Base Band Hopping. BTS Colour Code. Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis. Binary Coded Decimal. Base station Control Function. The GSM term for the digital control circuitry which controls the BTS. In Motorola cell sites this is a normally a BCU which includes DRI modules and is located in the BTS cabinet. Bearer Capability Information Element. Base station Control Unit. A functional entity of the BSS which provides the base control function at a BTS site. The term no longer applies to a type of shelf (see BSC and BSU). Base Controller Unit Power. Bit Error Rate. A measure of signal quality in the GSM system. Business Exchange Services. Bad Frame Indication. Busy Hour Call Attempt. all Barring of All Incoming call supplementary service. Balanced-line Interconnect Board. Provides interface to 12 balanced (6-pair) 120 ohm (37-pin D-type connector) lines for 2 Mbit/s circuits (See also T43). Barring of All Incoming Calls when Roaming outside the Home PLMN Country supplementary service. Balanced-line Interconnect Module. An area in a data array used to store information. BootLoad. Also known as download. For example, databases and software can be downloaded to the NEs from the BSS. BiLLiNG. Bits per second (bps). Full rate traffic channel. Bit Number. Number which identifies the position of a particular bit period within a timeslot. Bandpass Filter. mBCU Power Supply Module.
BCD BCF
BCIE BCU
BCUP BER BES BFI BHCA BI BIB
BICRoam BIM Bin BL BLLNG bit/s Bm BN BPF BPSM
EMOTOROLA LTD. 2001
65
ISSUE 3 REVISION 1
BS BS
Basic Service (group). Bearer Service. A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. The PLMN connection type used to support a bearer service may be identical to that used to support other types of telecommunication service. Base Station Controller. A network component in the GSM PLMN which has the digital control function of controlling all BTSs. The BSC can be located within a single BTS cabinet (forming a BSS) but is more often located remotely and controls several BTSs (see BCF, BCU, and BSU). Basic Service Group. Base Transceiver Station Identity Code. A block of code, consisting of the GSM PLMN colour code and a base station colour code. One Base Station can have several Base Station Colour Codes. BSIC of an adjacent cell. Base Site control Processor (at BSC). Backward Sequence Number. Base Station System. The system of base station equipment (Transceivers, controllers and so on) which is viewed by the MSC through a single interface as defined by the GSM 08 series of recommendations, as being the entity responsible for communicating with MSs in a certain area. The radio equipment of a BSS may cover one or more cells. A BSS may consist of one or more base stations. If an internal interface is implemented according to the GSM 08.5x series of recommendations, then the BSS consists of one BSC and several BTSs. BSS Application Part (of Signalling System No. 7) (DTAP + BSSMAP). Base Station System Control cabinet. The cabinet which houses one or two BSU shelves at a BSC or one or two RXU shelves at a remote transcoder. Base Station System Management Application Part (6-8). BSS Operation and Maintenance Application Part (of Signalling System No. 7). Base Station Unit shelf. The shelf which houses the digital control modules for the BTS (p/o BTS cabinet) or BSC (p/o BSSC cabinet). British Telecom. Bus Terminator. Bus Terminator Card. Base Transceiver Function. Base Transceiver Processor (at BTS). One of the six basic task groups within the GPROC.
BSC
BSG BSIC
BSIC-NCELL BSP BSN BSS
BSSAP BSSC
BSSMAP BSSOMAP BSU
BT BT BTC BTF BTP
66
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
BTS
Base Transceiver Station. A network component in the GSM PLMN which serves one cell, and is controlled by a BSC. The BTS contains one or more Transceivers (TRXs). A period of modulated carrier less than one timeslot. The physical content of a timeslot.
Burst
EMOTOROLA LTD. 2001
67
ISSUE 3 REVISION 1
C
C C Interface C7 CA CA CAB CADM Conditional. Interface between MSC and HLR/AUC. ITU-TSS Signalling System 7 (sometimes referred to as S7 or SS#7). Cell Allocation. The radio frequency channels allocated to a particular cell. Central Authority. Cabinet. Country ADMinistration. The Motorola procedure used within DataGen to create new country and network files in the DataGen database. Charge Advice Information. Cell Analysis Tool. Cell Broadcast. Circuit Breaker. Cell Broadcast Centre. Cell Broadcast CHannel. Combining Bandpass Filter. Cell Broadcast Link. Circuit Breaker Module. Cell Broadcast Message Identifier. Cell Broadcast Short Message Service. Clock Bus. Connection Confirm (Part of SCCP network connectivity). Country Code. Call Control. Cavity Combining Block, a three way RF combiner. There are two types of CCB, CCB (Output) and CCB (Extension). These, with up to two CCB Control cards, may comprise the TATI. The second card may be used for redundancy. Completion of Calls to Busy Subscriber supplementary service. Common Control CHannels. A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH. Group of MSs in idle mode. Common Channel Distributor. Channel Coding Digital Signal Processor. Conditional Call Forwarding. Control CHannel. Control channels are channels which carry system management messages. Council for Communications Harmonization (referred to in GSM Recommendations).
EMOTOROLA LTD. 2001
CAI CAT CB CB CBC CBCH CBF CBL CBM CBMI CBSMS CBUS CC CC CC CCB
CCBS CCCH
CCCH_GROUP CCD CCDSP CCF CCH CCH
68
ISSUE 3 REVISION 1
CCIT
Comit Consultatif International Tlgraphique et Tlphonique. This term has been superceded by ITUTSS (International Telecommunications Union Telecommunications Sector). Current Call Meter. Capability/Configuration Parameter. Control Channel Protocol Entity. Hundred call-seconds. The unit in which amounts of telephone traffic are measured. A single call lasting one hundred seconds is one CCS. See also erlang. Circuit. Control Driver Board. Common Desktop Environment. Part of the SUN software (crontab cron job file). Call Detail Records. Chargeable DURation. Control Equalizer Board (BTS). Called station identifier. Central Equipment Identity Register. By GSM definition, a cell is an RF coverage area. At an omni-site, cell is synonymous with site; at a sectored site, cell is synonymous with sector. This differs from analogue systems where cell is taken to mean the same thing as site. (See below).
CCM CCP CCPE CCS
Cct CDB CDE CDR CDUR CEB CED CEIR Cell
1 Cell = 1 Sector
Omni Site 1-Cell Site (1 BTS)
6-Sector Site or 6-Cell Site (6 BTSs)
CEND CEPT CERM CF CF CFB CFC CFNRc CFNRy
End of charge point. Confrence des administrations Europennes des Postes et Telecommunications. Circuit Error Rate Monitor. Conversion Facility. all Call Forwarding services. Call Forwarding on mobile subscriber Busy supplementary service. Conditional Call Forward. Call Forwarding on mobile subscriber Not Reachable supplementary service. Call Forwarding on No Reply supplementary service.
EMOTOROLA LTD. 2001
69
ISSUE 3 REVISION 1
CFU Channel
Call Forwarding Unconditional supplementary service. A means of one-way transmission. A defined sequence of periods (for example, timeslots) in a TDMA system; a defined frequency band in an FDMA system; a defined sequence of periods and frequency bands in a frequency hopped system. Coaxial Interconnect Module. CHarging Point. Card Holder Verification information. Ciphering Key Sequence Number. Cell Identity. A block of code which identifies a cell within a location area. CUG Index. Circuit Identity Code. Carrier to Interference Ratio. Unintelligible data produced through the use of encipherment. Ciphering Key Sequence Number. Calling Line Identity. Calling Line Identification Presentation supplementary service. Calling Line Identification Restriction supplementary service. Clock. Clock Extender half size board. The fibre optic link that distributes GCLK to boards in system (p/o BSS etc). Connectionless Manager. CLeaR. Configuration Management. An OMC application. Connection Management. CoMmanD. Channel Mode Modify. Common Management Information Protocol. Common Management Information Service Element. An ASE which provides a means to transfer management information via CMIP messages with another NE over an association established by ASCE using ROSE (OMC). Cellular Manual Revision. CalliNg tone. COnnected Line Identity. Placed together; two or more items together in the same place. A cell which has a co-located neighbour whose cell boundary follows the boundary of the said cell. The coincident cell has a different frequency type, but the same BSIC, as that of the neighbour cell. COnnected Line Identification Presentation supplementary service.
EMOTOROLA LTD. 2001
CIM CHP CHV CKSN CI CI CIC CIR, C/I Ciphertext CKSN CLI CLIP CLIR CLK CLKX CLM CLR CM CM CMD CMM CMIP CMISE
CMR CNG COLI Collocated Coincident Cell
COLP
610
ISSUE 3 REVISION 1
COLR CODEX COM COM COMB CONNACK COMM, Comms CommsLink CONF CONFIG CP CPU C/R CR CR CRC CRE CREF CRM CRM-LS/HS
COnnected Line Identification Restriction supplementary service. Manufacturers name for a type of multiplexer and packet switch commonly installed at the Motorola OMC-R. Code Object Manager. COMplete. Combiner. CONNect ACKnowledgement. COMMunications. Communications Link. (2Mbit/s) CONFerence circuit. CONFIGuration Control Program. Call Processing. Central Processing Unit. Command/Response field bit. Carriage Return (RETURN). Connection Request (Part of SCCP network connectivity). Cyclic Redundancy Check (3 bit). Call RE-establishment procedure. Connection REFused (Part of SCCP network connectivity). Cell Resource Manager. Cellular Radio Modem-Low Speed/High Speed. Low speed modem used to interwork 300 to 2400 bit/s data services under V.22bis, V.23, or V.21 standards. High speed modem used to interwork 1200 to 9600 bit/s data services under V.22bis, V.32, or V.29/V.27ter/V.21 standards. Cathode Ray Tube (video display terminal). Code Storage Facility Processor (at BSC and BTS). Central Statistics Process. The statistics process in the BSC. Circuit Switched Public Data Network. Call Transfer supplementary service. Channel Tester. Channel Type. Call Trace Product (Tool). Common Technical Regulation. Clear to Send. Method of flow control (RS232 Interface). Compact Transceiver Unit (M-Cellhorizon radio). Closed User Group supplementary service. The total value for an entire statistical interval. Call Waiting supplementary service.
CRT CSFP CSP CSPDN CT CT CT CTP CTR CTS CTU CUG Cumulative value CW
EMOTOROLA LTD. 2001
611
ISSUE 3 REVISION 1
D
D Interface D/A DAB DAC DACS DAN DAS DAT DataGen dB DB DB DBA DBMS dc DCB DCCH Interface between VLR and HLR. Digital to Analogue (converter). Disribution Alarm Board. Digital to Analogue Converter. Digital Access Cross-connect System. Digital ANnouncer (for recorded announcements on MSC). Data Acquisition System. Digital Audio Tape. Sysgen Builder System. A Motorola offline BSS binary object configuration tool. Decibel. A unit of power ratio measurement. DataBase. Dummy Burst (see Dummy burst). DataBase Administration/Database Administrator. DataBase Management System. Direct Current. Diversity Control Board (p/o DRCU). Dedicated Control CHannel. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and SACCH. Data Carrier Detect signal. Data Circuit terminating Equipment. Data Communications Function. Duplexed Combining bandpass Filter. (Used in Horizonmacro). Data Communications Network. A DCN connects Network Elements with internal mediation functions or mediation devices to the Operations Systems. DC Power Supply Module. Digital Cellular System at 1800 MHz. A cellular phone network using digital techniques similar to those used in GSM 900, but operating on frequencies of 1710 1785 MHz and 1805 1880 MHz. Dual-stage Duplexed combining Filter. (Used in Horizonmacro). DataGen Directory Structure. Data Drive Storage. Direct Digital Synthesis. Diversity Equalizer Board. DETach. Decision Feedback Equalizer. Data Gathering Tool.
EMOTOROLA LTD. 2001
DCD DCE DCF DCF DCN
DC PSM DCS1800
DDF DDS DDS DDS DEQB DET DFE DGT
612
ISSUE 3 REVISION 1
DHP DIA DINO E1/HDSL DINO T1 DISC Discon DIQ DIR DL DLCI DLD DLNB DLSP DLSP Dm DMA DMA DMR DMX DN DNIC Downlink DP DPC
Digital Host Processor. Drum Intercept Announcer. Line termination module. Line termination module. DISConnect. Discontiuous. Diversity In phase and Quadrature phase. Device Interface Routine. Data Link (layer). Data Link Connection Identifier. Data Link Discriminator. Diversity Low Noise Block. Data Link Service Process. Digital Link Signalling Processor. Control channel (ISDN terminology applied to mobile service). Deferred Maintenance Alarm. An alarm report level; an immediate or deferred response is required (see also PMA). Direct Memory Access. Digital Mobile Radio. Distributed Electronic Mobile Exchange (Motorolas networked EMX family). Directory Number. Data network identifier. Physical link from the BTS towards the MS (BTS transmits, MS receives). Dial/Dialled Pulse. Destination Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) destination point of the message. Digital Processing and Control board. Digital Private Network Signalling System (BT standard for PABX interface). Dual Path Preselector. Dual Port Random Access Memory. Digital Power Supply Module. Dynamic Random Access Memory. Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF). Diversity Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see RCU). Generic term for radio channel unit. May be standard RCU or diversity radio channel unit DRCU.
DPC DPNSS DPP DPR, DPRAM DPSM DRAM DRC
DRCU (D)RCU
EMOTOROLA LTD. 2001
613
ISSUE 3 REVISION 1
DRI DRIM DRIX DRX, DRx
Digital Radio Interface. Provides encoding/decoding and encryption/decryption for radio channel (p/o BSS). Digital Radio Interface extended Memory. A DRI with extra memory. DRI Extender half size board. Fibre optic link from DRI to BCU (p/o BSS). Discontinuous reception (mechanism). A means of saving battery power (for example in hand-portable units) by periodically and automatically switching the MS receiver on and off. German term for 2 Mbit/s line (PCM interface). Data Switching Exchange. Digital Speech Interpolation. Digital Signal Processor. Digital Subscriber Signalling No 1. Diversity Signal Strength Indication. Direct Transfer Application Part (6-8). Data Terminal Equipment. Digital Trunk Frame. DaTa form 1 (Part of SCCP network connectivity). Digital Trunk Interface. Dual Tone Multi-Frequency (tone signalling type). Data Terminal Ready signal. Method of flow control (RS232 Interface). Dual Transceiver Module. (Radio used in M-Cellarena and M-Cellarena macro). Discontinuous Transmission (mechanism). A means of saving battery power (for example in hand-portable units) and reducing interference by automatically switching the transmitter off when no speech or data are to be sent. A period of carrier less than one timeslot whose modulation is a defined sequence that carries no useful information. A dummy burst fills a timeslot with an RF signal when no information is to be delivered to a channel. DYnamic NETwork. Used to specify BTSs sharing dynamic resources.
DS-2 DSE DSI DSP DSS1 DSSI DTAP DTE DTF DT1 DTI DTMF DTR DTRX DTX, DTx
Dummy burst
DYNET
614
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
E
E E Interface EA EAS Eb/No EBCG EC ECB ECID ECM Ec/No ECT ECT EEL EEPROM EGSM900 EI EIR EIRP EIRP EL EM EMC EMF EMI eMLPP EMMI EMU EMX en bloc See Erlang. Interface between MSC and MSC. External Alarms. External Alarm System. Energy per Bit/Noise floor. Elementary Basic Service Group. Echo Canceller. Performs echo suppression for all voice circuits. Provides echo cancelling for telephone trunks for 30 channels (EC). The Motorola European Cellular Infrastructure Division. Error Correction Mode (facsimile). Ratio of energy per modulating bit to the noise spectral density. Event Counting Tool. Explicit Call Transfer supplementary service. Electric Echo Loss. Electrically Erasable Programmable Read Only Memory. Extended GSM900. Events Interface. Part of the OMC-R GUI. Equipment Identity Register. Effective Isotropic Radiated Power. Equipment Identity Register Procedure. Echo Loss. Event Management. An OMC application. ElectroMagnetic Compatibility. Electro Motive Force. Electro Magnetic Interference. enhanced Multi-Level Precedence and Pre-emption service. Electrical Man Machine Interface. Exchange office Management Unit (p/o Horizonoffice) Electronic Mobile Exchange (Motorolas MSC family). Fr. all at once (a CCITT #7 Digital Transmission scheme); En bloc sending means that digits are sent from one system to another ~ (that is, all the digits for a given call are sent at the same time as a group). ~ sending is the opposite of overlap sending. A system using ~ sending will wait until it has collected all the digits for a given call before it attempts to send digits to the next system. All the digits are then sent as a group. End of Tape. Erasable Programmable Read Only Memory.
EOT EPROM
EMOTOROLA LTD. 2001
615
ISSUE 3 REVISION 1
EPSM EQB EQCP EQ DSP Erlang
Enhanced Power Supply Module (+27 V). Equalizer Board. Control circuit for equalization for 8 time slots each with equalizing circuitry and a DSP (p/o RCU). Equalizer Control Processor. Equalizer Digitizer Signal Processor. International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 CCS. In the US this is also known as a traffic unit (TU). Ear Reference Point. Effective Radiated Power. ERRor. Electro-static Point. Embedded SQL (Structured Query Language). An RDBMS programming interface language. Extended TACS (analogue cellular system, extended). Type of Local Area Network. ETSI Technical Report. European Telecommunication Standard. European Telecommunications Standards Institute. End of Transmission. Executive Process.
ERP ERP ERR ESP ESQL E-TACS Ethernet ETR ETS ETSI ETX EXEC
616
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
F
F Interface FA FA FA FAC FACCH Interface between MSC and EIR. Fax Adaptor. Full Allocation. Functional Area. Final Assembly Code. Fast Associated Control Channel. A GSM dedicated control channel which is associated with a TCH and carries control information after a call is set up (see SDCCH). Fast Associated Control Channel/Full rate. Fast Associated Control Channel/Half rate. Frequency correction Burst (see Frequency correction burst). Fibre Channel Arbitration Loop. (Type of hard disc). Frequency Correction CHannel. A GSM broadcast control channel which carries information for frequency correction of the mobile (MS). Fault Collection Process (in BTS). Frame Check Sequence. Frequency Division Multiplex. Frequency Division Multiple Access. Fixed Dialling Number. Fault Diagnostic Procedure. Forward Error Correction. Front End Processor. Frame Erasure Ratio. For Further Study. Frequency Hopping. Forward Indicator Bit. Finite Impulse Response (filter type). Foreign Key. A database column attribute; the foreign key indicates an index into another table. Fault Management (at OMC). Frequency Modulation. Fault Management Initiated Clear. Fibre optic MUltipleXer. Frame Number. Identifies the position of a particular TDMA frame within a hyperframe. First Office Application. Fibre Optic eXtender. Full Rate. Refers to the current capacity of a data channel on the GSM air interface, that is, 8 simultaneous calls per carrier (see also HR Half Rate).
FACCH/F FACCH/H FB FC-AL FCCH
FCP FCS FDM FDMA FDN FDP FEC FEP FER FFS, FS FH FIB FIR FK FM FM FMIC FMUX FN FOA FOX FR
EMOTOROLA LTD. 2001
617
ISSUE 3 REVISION 1
FRU Frequency correction
Field Replaceable Unit. Period of RF carrier less than one timeslot whose modulation bit stream allows frequency correction to be performed easily within an MS burst. Frequency Synchronization. Free Space Loss. The decrease in the strength of a radio signal as it travels between a transmitter and receiver. The FSL is a function of the frequency of the radio signal and the distance the radio signal has travelled from the point source. Forward Sequence Number. File Transfer, Access, and Management. An ASE which provides a means to transfer information from file to file (OMC). forwarded-to number. Fault Translation Process (in BTS). File Transfer Protocol.
FS FSL
FSN FTAM
ftn FTP FTP
618
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
G
G Interface Gateway MSC Interface between VLR and VLR. An MSC that provides an entry point into the GSM PLMN from another network or service. A gateway MSC is also an interrogating node for incoming PLMN calls. Gigabyte. Gigabit Interface Converter. Generic Clock board. System clock source, one per site (p/o BSS, BTS, BSC, IWF, RXCDR). Group Call Register. Generic DSP Processor board. Interchangeable with the XCDR board. GDP board configured for E1 link usage. GDP board configured for T1 link usage. Giga-Hertz (109). Group ID. A unique number used by the system to identify a users primary group. GSM Multiplexer Board (p/o BSC). GSM Manual Revision. Gateway Mobile-services Switching Centre (see Gateway MSC). Gaussian Minimum Shift Keying. The modulation technique used in GSM. GrouND. Grade of Service. GSM PLMN Area. General Protocol Converter. Generic Processor board. GSM generic processor board: a 68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). Generic Processor board. GSM generic processor board: a 68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). General Packet Radio Service. Global Positioning by Satellite. GSM Service Area. The area in which an MS can be reached by a fixed subscriber, without the subscribers knowledge of the location of the MS. A GSA may include the areas served by several GSM PLMNs. GSM System Area. The group of GSM PLMN areas accessible by GSM MSs. Groupe Spcial Mobile (the committee). Global System for Mobile communications (the system). GSM Mobile Station. GSM Public Land Mobile Network.
GB, Gbyte GBIC GCLK GCR GDP GDP E1 GDP T1 GHz GID GMB GMR GMSC GMSK GND GOS GPA GPC GPROC
GPROC2 GPRS GPS GSA
GSA GSM GSM GSM MS GSM PLMN
EMOTOROLA LTD. 2001
619
ISSUE 3 REVISION 1
GSR GT GTE Guard period GUI GUI client GUI server
GSM Software Release. Global Title. Generic Table Editor. The Motorola procedure which allows users to display and edit MCDF input files. Period at the beginning and end of timeslot during which MS transmission is attenuated. Graphical User Interface. A computer used to display a GUI from an OMC-R GUI application which is beingbrun on a GUI server. A computer used to serve the OMC-R GUI application process running locally (on its processor) to other computers (Gui clients or other MMI processors). GateWaY (MSC/LR) interface to PSTN.
GWY
620
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
H
H Interface H-M HAD, HAP HANDO, Handover Interface between HLR and AUC. Human-Machine Terminals. HLR Authentication Distributor. HANDOver. The action of switching a call in progress from one radio channel to another radio channel. Handover allows established calls to continue by switching them to another radio resource, as when an MS moves from one BTS area to another. Handovers may take place between the following GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC. Hybrid Combining Unit. (Used in Horizonmacro). High level Data Link Control. High bit-rate Digital Subscriber Line. High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal. Home Location Register. The LR where the current location and all subscriber parameters of an MS are permanently stored. Heat Management System. The system that provides environmental control of the components inside the ExCell, TopCell and M-Cell cabinets. HandOver. (see HANDO above). Hand Portable Unit. Call hold supplementary service. Home PLMN. Half Rate. Refers to a type of data channel that will double the current GSM air interface capacity to 16 simultaneous calls per carrier (see also FR Full Rate). HandSet. High Speed Interface card. HLR Subscriber Management. Hopping Sequence Number. Home Units. Hardware. 2048 superframes. The longest recurrent time period of the frame structure.
HCU HDLC HDSL HLC
HLR
HMS
HO HPU HOLD HPLMN HR
HS HSI/S HSM HSN HU HW Hyperframe
EMOTOROLA LTD. 2001
621
ISSUE 3 REVISION 1
I
I IA IA5 IADU IAM IAS IC IC IC(pref) ICB ICC ICM ICMP ID, Id IDN IDS IE IEC IEEE IEI I-ETS IF IFAM IM IMACS IMEI Information frames (RLP). Incomming Access (closed user group (CUG) SS (supplementary service)). International Alphanumeric 5. Integrated Antenna Distribution Unit. (The IADU is the equivalent of the Receive Matrix used on pre-M-Cell BTSs). Initial Address Message. Internal Alarm System. Integrated Circuit. Interlock Code (CUG SS). Interlock Code op the preferential CUG. Incoming Calls Barred. Integrated Circuit(s) Card. In-Call Modification. Internet Control Message Protocol. IDentification/IDentity/IDentifier. Integrated Digital Network. INFOMIX Database Server. (OMC-R relational database management system). Information Element (signalling). International Electrotechnical Commission. Institute of Electrical and Electronic Engineers. Information Element Identifier. Interim European Telecommunication Standard. Intermediate Frequency. Initial and Final Address Message. InterModulation. Intelligent Monitor And Control System. International Mobile station Equipment Identity. Electronic serial number that uniquely identifies the MS as a piece or assembly of equipment. The IMEI is sent by the MS along with request for service. IMMediate assignment message. International Mobile Subscriber Identity. Published mobile number (prior to ISDN) (see also MSISDN) that uniquely identifies the subscription. It can serve as a key to derive subscriber information such as directory number(s) from the HLR. Intelligent Network. Interrogating Node. A switching node that interrogates an HLR, to route a call for an MS to the visited MSC. IN Service.
EMOTOROLA LTD. 2001
IMM IMSI
IN IN INS
622
ISSUE 3 REVISION 1
INS InterAlg Interworking
Intelligent Network Service. Interference Algorithm. A single interference algorithm in a cell. The general term used to describe the inter-operation of networks, services, supplementary services and so on. See also IWF. A recording period of time in which a statistic is pegged. The end of an interval. Input/Output. Intelligent Optimization Platform. Initialisation Process. Internet Protocol. Inter-Process Communication. INtermodulation Products. Intellectual PRoperty. Integrated Power Supply Module (48 V). (A hardware component). Indexed Sequential Access Method. International Switching Centre. Integrated Services Digital Network. An integrated services network that provides digital connections between user-network interfaces. Motorola Information Systems group (formally CODEX). International Organisation for Standardization. Informix Structured Query Language. ISDN User Part (of signalling system No. 7). Inactivity Test (Part of SCCP network connectivity). Information Transfer Capability. International Telecommunication Union. International Telecommunication Union Telecommunications Sector. InterWorking Function. A network functional entity which provides network interworking, service interworking, supplementary service interworking or signalling interworking. It may be a part of one or more logical or physical entities in a GSM PLMN. InterWorking MSC. InterWorking Unit.
Interval Interval expiry I/O IOS IP IP IPC IP, INP IPR IPSM IPX ISAM ISC ISDN
ISG ISO ISQL ISUP IT ITC ITU ITUTSS IWF
IWMSC IWU
EMOTOROLA LTD. 2001
623
ISSUE 3 REVISION 1
K
k k K KAIO kb, kbit kbit/s, kbps kbyte Kc kHz Ki KIO KSW KSWX kW kilo (103). Windows size. Constraint length of the convolutional code. Kernal Asynchronous Input/Output. kilo-bit. kilo-bits per second. kilobyte. Ciphering key. A sequence of symbols that controls the operation of encipherment and decipherment. kilo-Hertz (103). Individual subscriber authentication Key (p/o authentication process of AUC). A class of processor. Kiloport SWitch board. TDM timeslot interchanger to connect calls (p/o BSS). KSW Expander half size board. Fibre optic distribution of TDM bus (p/o BSS). kilo-Watt.
624
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
L
L1 L2ML L2R Layer 1. Layer 2 Management Link. Layer 2 Relay function. A function of an MS and IWF that adapts a users known layer2 protocol LAPB onto RLP for transmission between the MT and IWF. L2R Bit Orientated Protocol. L2R Character Orientated Protocol. Layer 3. Location Area. An area in which an MS may move freely without updating the location register. An LA may comprise one or several base station areas. Location Area Code. Location Area Identity. The information indicating the location area in which a cell is located. Local Area Network. LAN Extender half size board. Fibre optic distribution of LAN to/from other cabinets (p/o BSS etc). Link Access Protocol Balanced (of ITUTSS Rec. x.25). Link Access Protocol Data. Link Access Protocol on the Dm channel. Inductor Capacitor (type of filter). Link Control Function. Local Communications Network. Link Control Processor. Local Exchange. Light Emitting Diode. Line Feed. Length Indicator. Line Identity. Lower Layer Compatibility. The LLC can carry information defining the lower layer characteristics of the terminal. Traffic channel with capacity lower than a Bm. LAN Monitor Process. Least Mean Square. Local Mobile Station Identity. A unique identity temporarily allocated to visiting mobile subscribers in order to speed up the search for subscriber data in the VLR, when the MSRN allocation is done on a per cell basis. Local Maintenance Terminal. Low Noise Amplifier. Last Number Dialled.
L2R BOP L2R COP L3 LA
LAC LAI LAN LANX LAPB LAPD LAPDm LC LCF LCN LCP LE LED LF LI LI LLC Lm LMP LMS LMSI
LMT LNA LND
EMOTOROLA LTD. 2001
625
ISSUE 3 REVISION 1
Location area
An area in which a mobile station may move freely without updating the location register. A location area may comprise one or several base station areas. Linear Predictive Code. Local PLMN. Location Register. The GSM functional unit where MS location information is stored. The HLR and VLR are location registers. Link Stations Signalling Unit (Part of MTP transport system). Listener Side Tone Rating. Long Term Average. The value required in a BTSs GCLK frequency register to produce a 16.384 MHz clock. Local Terminal Emulator. Long Term Predictive. Line Terminating Unit. Local Units. Location Update. Length and Value.
LPC LPLMN LR
LSSU LSTR LTA LTE LTP LTU LU LU LV
626
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
M
M M M-Cell M&TS Mandatory. Mega (106). Motorola Cell. Maintenance and Troubleshooting. Functional area of Network Management software which (1) collects and displays alarms, (2) collects and displays Software/Hardware errors, and (3) activates test diagnostics at the NEs (OMC). Mobile Allocation. The radio frequency channels allocated to an MS for use in its frequency hopping sequence. Medium Access Control. Mobile Allocation Channel Number. A cell in which the base station antenna is generally mounted away from buildings or above rooftop level. Mobile Additional Function. Mobile Access Hunting supplementary service. Mobile Allocation Index. Mean Accumulated Intrinsic Down Time. MAINTenance. Mobile Allocation Index Offset. Mobile Application Part (of signalling system No. 7). The inter-networking signalling between MSCs and LRs and EIRs. Mobile Application Part Processor. Megabyte. Megabits per second. Motorola Cellular Advanced Processor. Mobile Country Code. Motorola Customer Data Format used by DataGen for simple data entry and retrieval. Malicious Call Identification supplementary service. Motorola Customer Support Centre. Main Control Unit for M-Cell2/6. Also referred to as the Micro Control Unit in software. Main Control Unit, with dual FMUX. (Used in M-Cellhorizon). Main Control Unit for M-Cell Micro sites (M-Cellm). Also referred to as the Micro Control Unit in software. The software subtype representation of the Field Replaceable Unit (FRU) for the MCU-m. Mediation Device. (mobile) Management (entity) - Data Link (layer). Maintenance Entity (GSM Rec. 12.00).
MA MAC MACN Macrocell MAF MAH MAI MAIDT MAINT MAIO MAP MAPP MB, Mbyte Mbit/s MCAP MCC MCDF MCI MCSC MCU MCUF MCU-m MCUm MD MDL ME
EMOTOROLA LTD. 2001
627
ISSUE 3 REVISION 1
ME
Mobile Equipment. Equipment intended to access a set of GSM PLMN and/or DCS telecommunication services, but which does not contain subscriber related information. Services may be accessed while the equipment, capable of surface movement within the GSM system area, is in motion or during halts at unspecified points. Maintenance Entity Function (GSM Rec. 12.00). MultiFrame. Multi-Frequency (tone signalling type). MultiFunction block. Management. Manager. Message Handling System. Mobile Handling Service. Mega-Hertz (106). Maintenance Information. Management Information Base. A Motorola OMC-R database. There is a CM MIB and an EM MIB. Mobile Interface Controller. A cell in which the base station antenna is generally mounted below rooftop level. Radio wave propagation is by diffraction and scattering around buildings, the main propagation is within street canyons. minute(s). micro-second (106). Micro Base Control Unit. Management Information Tree. Name of a file on the Motorola OMC-R. Man Machine. Mobility Management. Mobile Management Entity. Middle Man Funnel process. Man Machine Interface. The method in which the user interfaces with the software to request a function or change parameters. A machine configured to use the OMC-R software from an MMI server. MMI client/MMI server. A computer which has its own local copy of the OMC-R software. It can run the OMC-R software for MMI clients to mount. Man Machine Language. The tool of MMI. Multiple Serial Interface Link. (see also 2Mbit/s link) Mobile Network Code. MaiNTenance.
MEF MF MF MF MGMT, mgmt MGR MHS MHS MHz MI MIB MIC Microcell
min ms mBCU MIT MM MM MME MMF MMI
MMI client MMI processor MMI server
MML MMS MNC MNT
628
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
MO MO/PP MOMAP MoU MPC MPH MPTY MPX MRC MRN MRP MS MSC MSCM MSCU msec MSI MSIN MSISDN
Mobile Originated. Mobile Originated Point-to-Point messages. Motorola OMAP. Memorandum of Understanding. Multi Personal Computer (was p/o OMC). (mobile) Management (entity) - PHysical (layer) [primitive]. MultiParTY (Multi ParTY) supplementary service. MultiPleXed. Micro Radio Control Unit. Mobile Roaming Number. Mouth Reference Point. Mobile Station. The GSM subscriber unit. Mobile-services Switching Centre, Mobile Switching Centre. Mobile Station Class Mark. Mobile Station Control Unit. millisecond (.001 second). Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS). Mobile Station Identification Number. Mobile Station International ISDN Number. Published mobile number (see also IMSI). Uniquely defines the mobile station as an ISDN terminal. It consists of three parts: the Country Code (CC), the National Destination Code (NDC) and the Subscriber Number (SN). Mobile Station Roaming Number. A number assigned by the MSC to service and track a visiting subscriber. Message Signal Unit (Part of MTP transport system). A signal unit containing a service information octet and a signalling information field which is retransmitted by the signalling link control, if it is received in error. Mobile Terminated. Describes a call or short message destined for an MS. Mobile Termination. The part of the MS which terminates the radio transmission to and from the network and adapts terminal equipment (TE) capabilities to those of the radio transmission. MT0 is mobile termination with no support for terminal, MT1 is mobile termination with support for an S-type interface and MT2 is mobile termination with support for an R-type interface. Mobile-To-Mobile (call). Message Transfer Part. Mobile Terminated Point-to-Point messages. Mean Time Between Failures. Message Transfer LinK. MTP Transport Layer Link (A interface).
MSRN MSU
MT MT (0, 1, 2)
MTM MTP MT/PP MTBF MTK MTL
EMOTOROLA LTD. 2001
629
ISSUE 3 REVISION 1
MTP MTTR Multiframe
Message Transfer Part. Mean Time To Repair. Two types of multiframe are defined in the system: a 26-frame multiframe with a period of 120 ms and a 51-frame multiframe with a period of 3060/13 ms. Mark Up. Multi User Mobile Station. Multiplexer.
MU MUMS MUX
630
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
N
N/W NB NBIN NCC NCELL NCH ND Network. Normal Burst (see Normal burst). A parameter in the hoping sequence. Network (PLMN) Colour Code. Neighbouring (of current serving) Cell. Notification CHannel. No Duplicates. A database column attribute meaning the column contains unique values (used only with indexed columns). National Destination Code. Network Determined User Busy. Network Element (Network Entity). Network Element Function block. Norme Europennes de Telecommunications. Frequency planning tool. Network Function. Network File System. Network Health Analyst. Optional OMC-R processor feature. Network Interface Card. Network Independent Clocking. Network Information Service. It allows centralised control of network information for example hostnames, IP addresses and passwords. Network Interface Unit. Network Interface Unit, micro. Network LinK processor(s). Newton metres. Network Management (manager). NM is all activities which control, monitor and record the use and the performance of resources of a telecommunications network in order to provide telecommunication services to customers/users at a certain level of quality. Network Management Application Service Element. Network Management Centre. The NMC node of the GSM TMN provides global and centralised GSM PLMN monitoring and control, by being at the top of the TMN hierarchy and linked to subordinate OMC nodes. National Mobile Station Identification number. Nordic Mobile Telephone system. No Nulls. A database column attribute meaning the column must contain a value in all rows. A period of modulated carrier less than a timeslot. Number Plan Identifier.
NDC NDUB NE NEF NET NETPlan NF NFS NHA NIC NIC NIS
NIU NIU-m NLK Nm NM
NMASE NMC
NMSI NMT NN Normal burst NPI
EMOTOROLA LTD. 2001
631
ISSUE 3 REVISION 1
NRZ NSAP NSP NSS NT NT NTAAB NUA NUI NUP NV NVRAM nW
Non Return to Zero. Network Service Access Point. Network Service Provider. Network Status Summary. Network Termination. Non Transparent. New Type Approval Advisory Board. Network User Access. Network User Identification. National User Part (of signalling system No. 7). NonVolatile. Non-Volatile Random Access Memory. Nano-Watt (109).
632
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
O
O OA O&M OASCU Optional. Outgoing Access (CUG SS). Operations and Maintenance. Off-Air-Call-Set-Up. The procedure in which a telecommunication connection is being established whilst the RF link between the MS and the BTS is not occupied. Outgoing Calls Barred within the CUG. Oversized Voltage Controlled Crystal Oscillator. Optional for operators to implement for their aim. % OverFlow. IDS shutdown state. IDS normal operatng state. Operator Initiated Clear. Off_Line MIB. A Motorola DataGen database, used to modify and carry out Radio Frequency planning on multiple BSS binary files. Overall Loudness Rating. Operations and Maintenance Application Part (of signalling system No. 7) (was OAMP). Operations and Maintenance Centre. The OMC node of the GSM TMN provides dynamic O&M monitoring and control of the PLMN nodes operating in the geographical area controlled by the specific OMC. Operations and Maintenance Centre Gateway Part. (Iridium) Operations and Maintenance Centre GPRS Part. Operations and Maintenance Centre Radio Part. Operations and Maintenance Centre Switch Part. Operations and Maintenance Function (at BSC). Operations and Maintenance Link. Operation and Maintenance Processor. Operation and Maintenance System (BSCOMC). Operation and Maintenance SubSystem. Out Of Service. Originating Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) origination point of the message. Olympus Radio Architecture Chipset. Operating System. Open Systems Interconnection. OSI Reference Model. Operation Systems Function block.
OCB OCXO OD OFL offline online OIC OLM
OLR OMAP OMC
OMC-G OMC-G OMC-R OMC-S OMF OML OMP OMS OMSS OOS OPC
ORAC OS OSI OSI RM OSF
EMOTOROLA LTD. 2001
633
ISSUE 3 REVISION 1
OSF/MOTIF OSS Overlap
Open Software Foundation Motif. The basis of the GUI used for the Motorola OMC-R MMI. Operator Services System. Overlap sending means that digits are sent from one system to another as soon as they are received by the sending system. A system using ~ will not wait until it has received all digits of a call before it starts to send the digits to the next system. This is the opposite of en bloc sending where all digits for a given call are sent at one time.
634
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
P
PA PAB PABX PAD Paging Power Amplifier. Power Alarm Board. Private Automatic Branch eXchange. Packet Assembler/Disassembler facility. The procedure by which a GSM PLMN fixed infrastructure attempts to reach an MS within its location area, before any other network-initiated procedure can take place. CEPT 2 Mbit/s route through the BSS network. Processor Bus. Private Branch eXchange. Personal Computer. Paging CHannel. A GSM common control channel used to send paging messages to the MSs. Paging Channel Network. Physical Channel. Pulse Code Modulation (see also 2 Mbit/s link which is the physical bearer of PCM). Personal Communications Network. Preventative Cyclic Retransmission. A form of error correction suitable for use on links with long transmission delays, such as satellite links. Packet Control Unit (p/o GPRS). Picocell Control unit (p/o M-Cellaccess). Potential difference. Protocol Discriminator. Public Data. Power Distribution Board. Power Distribution Frame (MSC/LR). Public Data Networks. Power Distribution Unit. Protected Data Unit. Pan European Digital Cellular. A single incremental action modifying the value of a statistic. Modifying a statistical value. Packet Handler. PHysical (layer). Packet Handler Interface. Presentation Indicator. A cell site where the base station antenna is mounted within a building. Protocol Implementation Conformance Statement.
PATH PBUS PBX PC PCH PCHN PCHN PCM PCN PCR
PCU PCU pd PD PD PDB PDF PDN PDU PDU PEDC Peg Pegging PH PH PHI PI Picocell PICS
EMOTOROLA LTD. 2001
635
ISSUE 3 REVISION 1
PID PIM PIN PIN PIX PIXT PK Plaintext PlaNET PLL PLMN PM PM-UI PMA PMS PMUX PN PNE POI POTS p/o pp, p-p PP ppb PPE ppm Pref CUG Primary Cell
Process IDentifier/Process ID. PCM Interface Module (MSC). Personal Identification Number. Problem Identification Number. Parallel Interface Extender half size board. Customer alarm interface (p/o BSS). Protocol Implementation eXtra information for Testing. Primary Key. A database column attribute, the primary key is a not-null, non-duplicate index. Unciphered data. Frequency planning tool. Phase Lock Loop (refers to phase locking the GCLK in the BTS). Public Land Mobile Network. The mobile communications network. Performance Management. An OMC application. Performance Management User Interface. Prompt Maintenance Alarm. An alarm report level; immediate action is necessary (see also DMA). Pseudo MMS. PCM MUltipleXer. Permanent Nucleus (of GSM). Prsentation des Normes Europennes. Point of Interconnection (with PSTN). Plain Old Telephone Service (basic telephone services). Part of. Peak-to-peak. Point-to-Point. Parts per billion. Primative Procedure Entity. Parts per million (x 106). Preferential CUG. A cell which is already optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The primary cell has a preferred band equal to the frequency type of the coincident cell. Programmable Read Only Memory. Location probability. Periodic Supervision of Accessability. Presentation Services Access Point. Power Supply Module.
PROM Ps PSA PSAP PSM
636
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
PSPDN
Packet Switched Public Data Network. Public data communications network. x.25 links required for NE to OMC communications will probably be carried by PSPDN. Public Switched Telephone Network. The UK land line telephone network. Power Supply Unit. Pure Sine Wave. Public Telecommunications Operator. Price per Unit Currency Table. Permanent Virtual Circuit. Pass Word. Power. Private eXchange Public Data Network.
PSTN PSU PSW PTO PUCT PVC PW PWR PXPDN
EMOTOROLA LTD. 2001
637
ISSUE 3 REVISION 1
Q
QA Q3 Q-adapter QAF QEI QIC QOS Quiescent mode Q (Interface) Adapter. Interface between NMC and GSM network. Used to connect MEs and SEs to TMN (GSM Rec. 12.00). Q-Adapter Function. Quad European Interface. Interfaces four 2 Mbit/s circuits to TDM switch highway (see MSI). Quarter Inch Cartridge (Data storage format). Quality Of Service. IDS intermediate state before shutdown.
638
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
R
R Value of reduction of the MS transmitted RF power relative to the maximum allowed output power of the highest power class of MS (A). RAndom mode request information field. Random Access Burst. Random Access Control CHannel. A GSM common control channel used to originate a call or respond to a page. Random Access CHannel. Random Access Memory. RANDom number (used for authentication). Receive Antenna Transceiver Interface. Rate Adaptation. Remote BSS Diagnostic System (a discontinued Motorola diagnostic facility). Residual Bit Error Ratio. Remote Base Transceiver Station. Radio Control Board (p/o DRCU). Radio Channel Identifier. Radio Control Processor. Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see DRCU). Receiver. Relational DataBase Management System (INFORMIX). Radio Digital Interface System. Restricted Digital Information. Reference Distribution Module. Relative Distinguished Name. A series of RDN form a unique identifier, the distinguished name, for a particular network element. RECommendation. REJect(ion). RELease. Residual Excited Linear Predictive. RELP Long Term Prediction. A name for GSM full rate (see full rate). Resynchronize/resynchronization. REQuest. A Motorola DataGen utility for producing an MMI script from a binary object database. Radio Frequency.
RA RAB RACCH RACH RAM RAND RATI RAx RBDS RBER RBTS RCB RCI RCP RCU RCVR RDBMS RDI RDIS RDM RDN
REC, Rec REJ REL RELP RELP-LTP resync REQ Revgen RF
EMOTOROLA LTD. 2001
639
ISSUE 3 REVISION 1
RFC, RFCH
Radio Frequency Channel. A partition of the system RF spectrum allocation with a defined bandwidth and centre frequency. Receiver Front End (shelf). Receiver Front End Board (p/o DRCU II). Radio Frequency Interference. Radio Frequency Module. Reduced TDMA Frame Number. Reserved for Future Use. Network cable/Connector type. Reduced Instruction Set Computer. Remote login. Release Complete. Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22. Receiver Loudness Rating. ReLeaSeD. Root Mean Square (value). Remote Mobile Switching Unit. Table of 128 integers in the hopping sequence. Read Only Memory. Remote Operations Service Element. An ASE which carries a message between devices over an association established by ASCE (a CCITT specification for O & M) (OMC). Time period between transmit and receive instant of a timeslot in the BTS, propagation determined by the response behaviour of the MS and the MS to BTS delay distance. Regular Pulse Excited. Regular Pulse Excitation - Long Term Prediction. The GSM digital speech coding scheme. Recognised Private Operating Agency. Read Privilege Required. Access to the column is allowed only for privileged accounts. Radio Resource management. Receive Ready (frame). Radio Resource State Machine. Standard serial interface. Radio System Entity. Radio Signalling Link. Radio System Link Function. Radio System Link Processor. Radio SubSystem (replaced by BSS). Received Signal Strength Indicator.
RFE RFEB RFI RFM RFN RFU RJ45 RISC RL RLC RLP RLR RLSD RMS RMSU RNTABLE ROM ROSE
Roundtrip
RPE RPE-LTP RPOA RPR RR RR RRSM RS232 RSE RSL RSLF RSLP RSS RSSI
640
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
RSZI RTC RTE RTF RTF RTS RU Run level Rx RXCDR RXF RXLEV-D RXLEV-U RXQUAL-D RXQUAL-U RXU
Regional Subscription Zone Identity. Remotely Tuneable Channel Combiner. Remote Terminal Emulator. Radio Transceiver Function. Receive Transmit Functions. Request to Send. Method of flow control (RS232 Interface). Rack Unit. System processor operating mode. Receive(r). Remote Transcoder. Receive Function (of the RTF). Received signal level downlink. Received signal level uplink. Received signal quality downlink. Received signal quality uplink. Remote Transcoder Unit. The shelf which houses the remote transcoder modules in a BSSC cabinet at a remote transcoder site.
EMOTOROLA LTD. 2001
641
ISSUE 3 REVISION 1
S
S/W SABM SABME SACCH SoftWare. Set Asynchronous Balanced Mode. A message which establishes the signalling link over the air interface. SABM Extended. Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements. Slow Associated Control CHannel/SDCCH/4. Slow Associated Control CHannel/SDCCH/8. Slow Associated Control CHannel/Traffic channel. Slow Associated Control CHannel/Traffic channel Full rate. Slow Associated Control CHannel/Traffic channel Half rate. A brand of trunk test equipment. Service Access Point. In the reference model for OSI, SAPs of a layer are defined as gates through which services are offered to an adjacent higher layer. System Audits Process. Service Access Point Indicator (identifier). Surface Acoustic Wave. Synchronization Burst (see Synchronization burst). Serial Bus. Service Centre (used for Short Message Service). Service Code. System Change Control Administration. Software module which allows full or partial software download to the NE (OMC). Signalling Connection Control Part (6-8). Speech Coding Experts Group (of GSM). Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations. Status Control Interface. Serial Communication Interface Processor. Status Control Manager. Sub-Channel Number. One of the parameters defining a particular physical channel in a BS. Service Control Point (an intelligent network entity). Small Computer Systems Interface. Slim Channel Unit. Slim Channel Unit for GSM900. Stand-alone Dedicated Control CHannel. A GSM control channel where the majority of call setup occurs. Used for MS to BTS communications before MS assigned to TCH.
EMOTOROLA LTD. 2001
SACCH/C4 SACCH/C8 SACCH/T SACCH/TF SACCH/TH SAGE SAP
SAP SAPI SAW SB SBUS SC SC SCCA
SCCP SCEG SCH
SCI SCIP SCM SCN SCP SCSI SCU SCU900 SDCCH
642
ISSUE 3 REVISION 1
SDL SDT SDU SDR SE Secondary Cell
Specification Description Language. SDL Developement Tool. Service Data Unit. Special Drawing Rights (an international basket currency for billing). Support Entity (GSM Rec. 12.00). A cell which is not optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The secondary cell has a preferred band the same as that of its own frequency type. Support Entity Function (GSM Rec.12.00). Slow Frequency Hopping. Screening Indicator. Service Interworking. Supplementary Information. Supplementary Information A. Silence Descriptor. Signal Information Field. The bits of a message signal unit that carry information for a certain user transaction; the SIF always contains a label. Subscriber Identity Module. Removable module which is inserted into a mobile equipment; it is considered as part of the MS. It contains security related information (IMSI, Ki, PIN), other subscriber related information and the algorithms A3 and A8. Single Inline Memory module. System Integrated Memory Module. Service Information Octet. Eight bits contained in a message signal unit, comprising the service indicator and sub-service field. BSC, BTS or collocated BSC-BTS site. Serial Interface eXtender. Converts interface levels to TTL levels. Used to extend 2 serial ports from GPROC to external devices (RS232, RS422, and fibre optics). Secondary Key. A database column attribute, the secondary key indicates an additional index and/or usage as a composite key. Signalling Link. Serial Link. Send Loudness Rating. Signalling Link Test Message. Switch Manager. Summing Manager. System Management Application Entity (CCITT Q795, ISO 9596). Short Message Cell Broadcast.
SEF SFH SI SI SI SIA SID SIF
SIM
SIMM SIMM SIO
SITE SIX
SK
SL SLNK SLR SLTM SM SM SMAE SMCB
EMOTOROLA LTD. 2001
643
ISSUE 3 REVISION 1
SME SMG SMP SMS SMSCB SMS-SC SMS/PP Smt SN SND SNDR SNR SOA SP
Short Message Entity. Special Mobile Group. Motorola Software Maintenance Program. Short Message Service. Short Message Service Cell Broadcast. Short Message Service - Service Centre. Short Message Service/Point-to-Point. Short message terminal. Subscriber Number. SeND. SeNDeR. Serial NumbeR. Suppress Outgoing Access (CUG SS). Service Provider. The organisation through which the subscriber obtains GSM telecommunications services. This may be a network operator or possibly a separate body. Signalling Point. Special Product. SPare. Signalling Point Code. Suppress Preferential CUG. Signalling Point Inaccessible. Single Path Preselector. Signal Quality Error. Structured Query Language. Service Request Distributor. Signed RESponse (authentication). Supplementary Service. A modification of, or a supplement to, a basic telecommunication service. System Simulator. SCCP messages, Subsystem-allowed (see CCITT Q.712 para 1.15). Site System Audits Processor. Supplementary Service Control string. Subservice Field. The level 3 field containing the network indicator and two spare bits. Signalling State Machine. SubSystem Number. Service Switching Point (an intelligent network element). SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18). SubSystem Prohibited message.
SP SP SP SPC SPC SPI SPP SQE SQL SRD SRES SS SS SSA SSAP SSC SSF SSM SSN SSP SSP SSP
644
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
SSS SS7 STAN STAT stats STC STMR SUERM STP Superframe Super user SURF SVC SVM SVN SW SWFM sync Synchronization burst
Switching SubSystem (comprising the MSC and the LRs). ANSI Signalling System No. 7 (alias C7). Statistical ANalysis (processor). STATistics. Statistics. System Timing Controller. Side Tone Masking rating. Signal Unit Error Rate Monitor. Signalling Transfer Point. 51 traffic/associated control multiframes or 26 broadcast/common control multiframes (period 6.12s). User account that can access all files, regardless of protection settings, and control all user accounts. Sectorized Universal Receiver Front-end (Used in Horizonmacro). Switch Virtual Circuit. SerVice Manager. Software Version Number. Software. SoftWare Fault Management. synchronize/synchronization. Period of RF carrier less than one timeslot whose modulation bit stream carries information for the MS to synchronize its frame to that of the received signal. SYStem. SYStem GENeration. The Motorola procedure for loading a configuration database into a BTS.
SYS SYSGEN
EMOTOROLA LTD. 2001
645
ISSUE 3 REVISION 1
T
T T T T43 Timer. Transparent. Type only. Type 43 Interconnect Board. Provides interface to 12 unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for 2 Mbit/s circuits (See BIB). Terminal Adaptor. A physical entity in the MS providing terminal adaptation functions (see GSM 04.02). Timing Advance. Type Approval Code. Total Access Communications System (European analogue cellular system). Terminal Adaptation Function. Transmit Antenna Transceiver Interface. The TATI consists of RF combining equipments, either Hybrid or Cavity Combining. (See CCB). Transparent Asynchronous Transmitter/Receiver Interface (physical layer). To Be Determined. Technical Basis for Regulation. TDM Bus. Transaction Capabilities. Transaction Capabilities Application Part (of Signalling System No. 7). TATI Control Board. Traffic CHannel. GSM logical channels which carry either encoded speech or user data. A full rate TCH. A full rate TCH at 2.4 kbit/s. A full rate TCH at 4.8 kbit/s. A full rate TCH at 9.6 kbit/s. A full rate Speech TCH. A half rate TCH. A half rate TCH at 2.4 kbit/s. A half rate TCH at 4.8 kbit/s. A half rate Speech TCH). Transceiver Control Interface. Transmission Control Protocol/Internet Protocol. Technical Commitee Technical Report. Transceiver Control Unit. Twin Duplexed Filter. (Used in M-Cellhorizon). Time Division Multiplexing.
EMOTOROLA LTD. 2001
TA TA TAC TACS TAF TATI
TAXI TBD TBR TBUS TC TCAP TCB TCH TCH/F TCH/F2.4 TCH/F4.8 TCH/F9.6 TCH/FS TCH/H TCH/H2.4 TCH/H4.8 TCH/HS TCI TCP/IP TC-TR TCU TDF TDM
646
ISSUE 3 REVISION 1
TDMA TDU TE
Time Division Multiple Access. TopCell Digital Unit. Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user. Terminal endpoint identifier. Terminal Equipment Identity. TEMPorary. TEST control processor. TransFer Allowed. TransFer Prohibited. Trivial File Transfer Protocol. Transaction Identifier. The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots. A signal sent by the BTS to the MS. It enables the MS to advance the timing of its transmission to the BTS so as to compensate for propagation delay. Type, Length and Value. Traffic Manager. TDM Modem Interface board. Provides analogue interface from IWF to modems for 16 circuits (p/o IWF). Traffic Metering and Measuring. Telecommunications Management Network. The implementation of the Network Management functionality required for the PLMN is in terms of physical entities which together constitute the TMN. Temporary Mobile Subscriber Identity. A unique identity temporarily allocated by the MSC to a visiting mobile subscriber to process a call. May be changed between calls and even during a call, to preserve subscriber confidentiality. Timeslot Number. Type Of Number. Channels which carry users speech or data (see also TCH). Equivalent to an erlang. Sequence of modulating bits employed to facilitate timing recovery and channel equalization in the receiver. Transcoder Rate Adaption Unit. TopCell Radio unit. Transceiver(s). A network component which can serve full duplex communication on 8 full-rate traffic channels according to specification GSM 05.02. If Slow Frequency Hopping (SFH) is not used, then the TRX serves the communication on one RF carrier. Technical Specification.
Tei TEI TEMP TEST TFA TFP TFTP TI Timeslot
Timing advance
TLV TM TMI TMM TMN
TMSI
TN TON Traffic channels Traffic unit Training sequence TRAU TRU TRX
TS
EMOTOROLA LTD. 2001
647
ISSUE 3 REVISION 1
TS TS TSA TSA TSDA TSC TSI TSDI TSM TSW TTCN TTL TTY TU TUP TV Tx TXF TXPWR
TeleService. TimeSlot (see Timeslot). TimeSlot Acquisition. TimeSlot Assignment. Transceiver Speech & Data Interface. Training Sequence Code. TimeSlot Interchange. Transceiver Speech and Data Interface. Transceiver Station Manager. Timeslot SWitch. Tree and Tabular Combined Notation. Transistor to Transistor Logic. TeleTYpe (refers to any terminal). Traffic Unit. Telephone User Part (SS7). Type and Value. Transmit(ter). Transmit Function (of the RTF). Transmit PoWeR. Tx power level in the MS_TXPWR_REQUEST and MS_TXPWR_CONF parameters. Transmit Bandpass Filter.
TxBPF
648
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
U
UA Unnumbered Acknowledgment. A message sent from the MS to the BSS to acknowledge release of radio resources when a call is being cleared. Unrestricted Digital Information. User Datagram Protocol. User Determined User Busy. Ultra High Frequency. Unnumbered Information (Frame). Union International des Chemins de Fer. User ID. Unique number used by the system to identify the user. Upload (of software or database from an NE to a BSS). Air interface. Universal Mobile Telecommunication System. Uniform PCM Interface (13 bit). Up to Date. Physical link from the MS towards the BTS (MS transmits, BTS receives). Uninterruptable Power Supply. User Part Unavailable. That part of the burst used by the demodulator; differs from the full burst because of the bit shift of the I and Q parts of the GMSK signal. Unstructured Supplementary Service Data. User-to-User Signalling supplementary service.
UDI UDP UDUB UHF UI UIC UID UL Um UMTS UPCMI UPD Uplink UPS UPU Useful part of burst
USSD UUS
EMOTOROLA LTD. 2001
649
ISSUE 3 REVISION 1
V
V VA VAD VAP VBS VC VCO VCXO VDU VGCS VLR Value only. Viterbi Algorithm (used in channel equalizers). Voice Activity Detection. A process used to identify presence or absence of speech data bits. VAD is used with DTX. Videotex Access Point. Voice Broadcast Service. Virtual Circuit. Voltage Controlled Oscillator. Voltage Controlled Crystal Oscillator. Visual Display Unit. Voice Group Call Service. Visitor Location Register. A GSM network element which provides a temporary register for subscriber information for a visiting subscriber. Often a part of the MSC. Very Large Scale Integration (in ICs). Visited MSC. (Recommendation not to be used). Voice Operated Transmission. Visited PLMN. Videotex Service Centre. Send state variable. Vehicular Speaker Phone. Voltage Standing Wave Ratio. The components dedecated to Videotex service.
VLSI VMSC VOX VPLMN VSC V(SD) VSP VSWR VTX host
650
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
W
WAN WPA WS Wide Area Network. Wrong Password Attempts (counter). Work Station. The remote device via which O&M personnel execute input and output transactions for network management purposes. Work Station Function block. World Wide Web.
WSF WWW
EMOTOROLA LTD. 2001
651
ISSUE 3 REVISION 1
X
X.25 X.25 link XBL XCB XCDR XCDR board CCITT specification and protocols for public packet-switched networks (see PSPDN). A communications link which conforms to X.25 specifications and uses X.25 protocol (NE to OMC links). Transcoder to BSS Link. The carrier communications link between the Transcoder (XCDR) and the BSS. Transceiver Control Board (p/o Transceiver). Full-rate Transcoder. Provides speech transcoding and 4:1 submultiplexing (p/o BSS, BSC or XCDR). The circuit board required to perform speech transcoding at the BSS or (R)XCDR). Also known as the MSI (XCDR) board. Interchangeable with the GDP board. Transfer. eXchange IDentifier. X terminal window.
XFER XID X-Term
652
EMOTOROLA LTD. 2001
ISSUE 3 REVISION 1
Z
ZC Zone Code
EMOTOROLA LTD. 2001
653
ISSUE 3 REVISION 1
654
EMOTOROLA LTD. 2001

BSS08, Motorola

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BSS08, Motorola

Transféré par

Droits d'auteur :

Formats disponibles

CHAPTER 1

Cellular Infrastructure Group

BSS08 BSSC APPLICATIONS

FOR TRAINING PURPOSES ONLY

BSS08 BSSC APPLICATIONS

FOR TRAINING PURPOSES ONLY

BSS08 BSSC APPLICATIONS

BSS08 BSSC Applications

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Chapter 1 GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 BSSC Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Chapter 3 RXCDR/BSC Digital Communication Buses . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

332 334 336

Chapter 4 BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Chapter 5 Appendix A Cabinet Interconnecting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

About this manual

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Special key sequences

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

First aid in case of electric shock

First aid in case of electric shock

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Reporting safety issues

Reporting safety issues

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Warnings and cautions

Warnings and cautions

Example and format

Example and format

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

EMOTOROLA LTD. 2001

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

Human exposure to radio frequency energy (PCS1900 only)

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposures

Power density (S)

BSS08: BSSC Applications FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Human exposure to radio frequency energy (PCS1900 only)