CTU Calibration

GSM-100-423 GSM Software Release 5
Installation & Configuration BSS Optimization
E Motorola 19932001 All Rights Reserved Printed in the U.K.
Installation & Configuration: BSS Optimization

31st Jul 01
68P02901W43-J
GSM-100-423
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
and MOTOROLA are registered trademarks of Motorola Inc. M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
ii
Installation & Configuration: BSS Optimization 68P02901W43-J
31st Jul 01
GSM-100-423
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 2 4 5 6 7 9 12 14 15 16 19 20
Chapter 1 Introduction to BSS optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Guide to using this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 11 11 11 11 12 12 12
Chapter 2 BTS4/5/6 ExCell TopCell & BSC optimization . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BTS4/5/6, ExCell, TopCell & BSC optimization . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 9-way cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 25-way cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the dc power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually tuning the RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 21 22 22 22 23 23 24 24 24 25 25 25 25 25 27 29 29 29 29 29

31st Jul 01
68P02901W43-J
iii
GSM-100-423
Calibrating DRCUs Tx power and VSWR check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the DRCU, DRCUII and DRCU3 bay level offset tables . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating SCU Tx power and VSWR check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the SCU900/1800 bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic check of the SCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database for devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1/T1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK calibration record form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization 68P02901W43-J
211 211 212 213 214 217 217 217 218 219 225 225 226 226 227 231 231 231 232 233 234 236 237 237 237 238 239 239 240 240 240 240 240 242 242 242 242 242 244 244 244 244 244 246 246 246 246 247 250 251 251 251 251 252 254
iv
31st Jul 01
GSM-100-423
Verifying ExCell alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smoke alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overtemperature alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Door open alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mains fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rectifier fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Low dc voltage alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inverter fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCB trip alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery fault alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comms PSU fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying DRCU faults on site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symptoms during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symptoms during commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure during commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255 255 255 255 255 256 256 257 257 258 258 259 259 260 260 261 261 262 262 263 263 264 264 264 264 265 268
Chapter 3 M-Cell2/6 optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to M-Cell2/6 optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test lead calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating TCU output power and checking VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell site offsite calibration (Tx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting cellsite power M-Cell6 with CCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B VSWR and cellsite offset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR and cellsite offsite information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 32 32 32 33 33 36 36 37 37 38 39 39 310 311 312 313 314 317 319 319 320 320 321 322 322

31st Jul 01
68P02901W43-J
GSM-100-423
Normal TCU-B VSWR and cellsite power calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal VSWR information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating TCU-B transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B VSWR and cellsite power calibration for CCBs . . . . . . . . . . . . . . . . . . . . . . . . . . . CCB calibration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating M-Cell2/6 TCU900/1800/1900 bay level offset tables . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking radio, dummy load and TCU reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silencing PLL_LK alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up TCU for Bay Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic check of TCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating M-Cell2/6 TCU-B bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for bay level calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch 1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B diagnostic check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking serial connections and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization 68P02901W43-J
324 324 325 326 327 329 329 331 335 337 337 337 337 339 340 341 342 349 350 350 351 352 354 355 356 356 356 357 358 361 365 366 366 367 368 370 371 372 372 372 372 373 373 375 375 375 375 375 376 377 377 377 378 378 378
vi
31st Jul 01
GSM-100-423
Calibrating the MCU (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to calibrate the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up for calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
379 379 379 379 380 381
Chapter 4 Horizonmacro optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Horizonmacro optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test lead calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU VSWR and cellsite offset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR and cellsite offsite information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal CTU VSWR and cellsite power calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal VSWR information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating CTU transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU VSWR and cellsite power calibration for CCBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCB calibration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating Horizonmacro CTU bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for bay level calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch 1 RX0A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for Rx1800 0A on 900 (Dualband) SURF . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 42 42 42 43 43 46 46 47 47 48 49 49 411 411 412 413 414 416 416 418 423 425 425 425 426 427 429 432 433 434 435 435 436 438 439 439 439 439 440 440

31st Jul 01
68P02901W43-J
vii
GSM-100-423
Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking serial connections and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the MCUF (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to calibrate the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up for calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
442 442 442 442 442 443 444 444 444 445 445 445 446 446 446 446 447 448
Chapter 5 Preserve calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preserve transceiver calibration feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preserve calibration introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration data overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the preserve feature at the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the preserve feature at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a transceiver using preserved data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsequent replacement of calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a transceiver using new data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the calibration data in CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 51 52 52 52 53 53 54 55 56
Chapter 6 M-Cellcity/M-Cellcity+ optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cellcity/M-Cellcity+ optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment and test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCMCIA card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download from PCMCIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCMCIA download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking VSWR and output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCCH swap procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization 68P02901W43-J
i
61 61 62 62 63 64 65 65 65 66 66 66 66 67 612 612 612 613
viii
31st Jul 01
GSM-100-423
Download from BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download Procedure with example results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site status check procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1/T1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fitting chassis bottom cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating an MCU-m GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
615 615 622 625 625 625 625 625 627 627 627 627 627 628 628 629 629 629 629
Chapter 7 M-Cellaccess and Horizonoffice optimization . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cellaccess and Horizonoffice optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 9-way cable (M-Cellaccess) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 25-way cable (M-Cellaccess and Horizonoffice) . . . . . . . . . . . . . . . . . . . Test plugs for M-Cellaccess and Horizonoffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the dc power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database for devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying PSM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
71 71 71 72 72 72 73 74 75 76 76 76 76 76 77 79 79 79 79 79 712 712 712 712 712 714 714 714 714 714

31st Jul 01
68P02901W43-J
ix
GSM-100-423
Integrating the transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the M-Cellaccess or Horizonoffice GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK calibration record form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
715 715 715 715 715 718 719 719 719 719 720 722
Chapter 8 Base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reason for base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site using logging software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site without logging software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site with no connection to the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 81 82 82 82 82 82 83 84 85 85 85 85 85 86 87 88 88 88 88 88 89 810
Chapter 9 Channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channels and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PGSM channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended GSM channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCS1800 channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization 68P02901W43-J
i
91 91 92 92 98 98 911 911
31st Jul 01
GSM-100-423
PCS1900 channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
930 930
Chapter 10 Network optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network optimization chapter topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stages in an optimization exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the drive test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . optimizing for worst case interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive test process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data collection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data collection process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FICS explained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification of test calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnosing drive test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysis of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High handover failure rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High set-up failure rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High dropped call rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No audio calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Noisy calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Poor quality of service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High blocking cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio call faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean time between drops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive test report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementation of a drive test recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . Effects of a recommendation implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Residual defect investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
101 101 101 102 102 103 104 104 104 106 108 108 108 109 109 109 1010 1011 1011 1011 1012 1013 1014 1016 1016 1016 1016 1018 1019 1020 1020 1020 1021
Chapter 11 Optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS/BSC optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna reflected power tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRCU tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCU/TCU900/ TCU-B/CTU900 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCU/TCU1800/ CTU1800 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU1900 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loopback and RTC checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
111 111 111 112 112 113 113 114 1110 1116 1128 1140

31st Jul 01
68P02901W43-J
xi
GSM-100-423
BSC/RXCDR optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1/T1 loopback (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1/T1 loopback (RXCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellaccess PCC optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loopback checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellaccess BSC/XCDR results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 loopback (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 loopback (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing optimization forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms in this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tick Sheet Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommendation Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feeder Information Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing optimization tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tables in this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1141 1141 1141 1142 1142 1142 1143 1144 1145 1146 1146 1146 1147 1148 1148 1149 1150 1150 1150 1151 1152 1152 1153 1154 1155 1155 1155 1156 1157 1158 1160 1160 1160
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I1
xii
31st Jul 01
GSM-100-423
Issue status of this manual
Issue status of this manual

Introduction
The following shows the issue status of this manual since it was first released.
Version information
The following lists the versions of this manual in order of manual issue: Manual issue O A B C D E F G H J Date of issue 3rd Oct 94 30th Dec 94 1st Sep 95 31st May 96 28th Mar 97 29th Aug 97 27th Apr 98 12th Mar 99 14th Jul 00 31st Jul 01 Remarks Original issue Software release 1.2.2.x Issue A Software release 1.2.3.x Issue B Software release 1.3.0.x Issue C Software release 1.4.0.x Issue D Software release 1.4.1.x Issue E GSM Software Release 2 Issue F GSM Software Release 3 Issue G GSM Software Release 4 Issue H GSM Software Release 4.1 Issue J GSM Software Release 5
Resolution of Service Requests

The following Service Requests are now resolved in this manual: Service Request SR 46112 SR 47985 SR 48605 SR 49372 GMR Number Remarks Page 3-79 change to calibrating MCU (GCLK). Chapter 2, Warning added to RCU/DRCU/SCU and Chapter 3 TCU bay level calibration. Chapter 4 adding dual band surf testing. Chapter 2, 3 and 4 change to GCLK calibration.

31st Jul 01
68P02901W43-J
General information
GSM-100-423
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) manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola GSM equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
About this manual

The manual contains optimization, configuration and integration information. This GSR5 document supports the following Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, M-Cellcity+, M-Cellaccess, Horizonoffice and Horizonmacro. The transceivers use, depending on capability, PGSM, EGSM, DCS1800 and PCS1900 frequencies.
31st Jul 01
GSM-100-423
General information
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: CTRLc ALTf | 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.

31st Jul 01
68P02901W43-J
First aid in case of electric shock
GSM-100-423
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.
31st Jul 01
GSM-100-423
Reporting safety issues
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. 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 Customer Network Resolution Centre +44 (0)1793 565444 (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 Customer Network Resolution Centre.
4.

31st Jul 01
68P02901W43-J
Warnings and cautions
GSM-100-423
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.
31st Jul 01
GSM-100-423
General warnings
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 supply which is potentially lethal. Therefore, the areas where the ac supply 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 ac 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.

31st Jul 01
68P02901W43-J
General warnings
GSM-100-423
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.
31st Jul 01
GSM-100-423
Human exposure to radio frequency energy (PCS1900 only)

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

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

Power per unit area normal to the direction of propagation, usually expressed in units of watts per square metre (W/m2) or, for convenience, units such as milliwatts per square centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and magnetic field strength (H) are related by the impedance of free space, 377 ohms. In particular,
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.

31st Jul 01
68P02901W43-J
GSM-100-423
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 6.567mW/cm 2
1.287mW/cm 2 1.313mW/cm 2 6.433mW/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.
10
31st Jul 01
GSM-100-423
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: 1930 MHz Base station cabinet output power, P: +39.0 dBm (8 watts) Antenna feeder cable loss, CL: 2.0 dB Antenna input power Pin: PCL = +39.02.0 = +37.0 dB (5watts) Antenna gain, G: 16.4 dBi (43.65) Using the following relationship: G + 4pr W Pin
2
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+ GPin + 4pW 43.65 5 + 1.16m 4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.
Power density measurements

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

31st Jul 01
68P02901W43-J
11
Beryllium health and safety precautions
GSM-100-423

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 2-20 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.
12
31st Jul 01
GSM-100-423
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.

31st Jul 01
68P02901W43-J
13
General cautions
GSM-100-423
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.
14
31st Jul 01
GSM-100-423
Devices sensitive to static
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.

31st Jul 01
68P02901W43-J
15
Motorola GSM manual set
GSM-100-423

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM and GSM Packet Radio Service (GPRS) equipment.
Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals are release dependent: Classification number GSM-100-101 GSM-100-201 GSM-100-202 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-413 GSM-100-501 GSM-100-520 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721 GSM-100-712 Name System Information: General . . . . . . . . . . . . . . . . . . . Operating Information: GSM System Operation . . . Operating Information: OMC-R System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description: OMC-R in a GSM System . . Technical Description: OMC-R Database Schema . Technical Description: BSS Implementation . . . . . . . Technical Description: BSS Command Reference . Installation & Configuration: GSM System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization . . . . Installation & Configuration: OMC-R Clean Install . . Maintenance Information: Alarm Handling at the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: BSS Timers . . . . . . . . . . . Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: GSM Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Release Notes: BSS/RXCDR . . . . . . . . . . Software Release Notes: OMC-R System . . . . . . . . Order number 68P02901W01 68P02901W14 68P02901W19 68P02901W31 68P02901W34 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W47 68P02901W26 68P02901W58 68P02901W57 68P02901W51 68P02901W56 68P02901W72 68P02901W74
16
31st Jul 01
GSM-100-423
Related GSM manuals

The following are related Motorola GSM manuals: Classification number GSM-001-103 GSM-002-103 GSM-002-703 GSM-005-103 GSM-008-403 GSM-008-703 GSM-TOOLS-001 GSM-TOOLS-002 GSM-TOOLS-701 GSM-TOOLS-702 GSM-006-202 GSM-006-413 GSM-006-712 Name System Information: BSS Equipment Planning . . . . System Information: DataGen . . . . . . . . . . . . . . . . . . Software Release Notes: DataGen . . . . . . . . . . . . . . System Information: GSM Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: Network Health Analyst Software Release Notes: Network Health Analyst . System Information: Cell Optimization (COP) . . . . . System Information: Motorola Analysis and Reporting System (MARS) . . . . . . . . . . . . . . . . . . . . . Software Release Notes: Cell Optimization (COP) . Software Release Notes: Motorola Analysis and Reporting System (MARS) . . . . . . . . . . . . . . . . . . . . . Operating Information: OMC-R System Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: OSI Clean Install . . . . . Software Release Notes: OMC-R OSI System . . . . Order number 68P02900W21 68P02900W22 68P02900W76 68P02900W25 68P02900W36 68P02900W77 68P02900W90 68P02900W94 68P02900W69 68P02900W68 68P02901W10 68P02901W39 68P02901W70
Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals are release dependent: Classification number GPRS-300-101 GPRS-300-202 GPRS-300-222 GPRS-300-311 GPRS-300-313 GPRS-300-321 GPRS-300-423 GPRS-300-413 GPRS-300-501 GPRS-300-503 GPRS-300-722 GPRS-300-712 Name System Information: GPRS Overview . . . . . . . . . . . . Operating Information: OMC-G System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Information: GSN System Administration Technical Description: OMC-G in a GPRS System . Technical Description: OMC-G Database Schema . Technical Description: GSN Command Reference . Installation & Configuration: GSN Clean Install . . . . Installation & Configuration: OMC-G Clean Install . Maintenance Information: Alarm Handling at the OMC-G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: GSN Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Release Notes: GSN System . . . . . . . . . . Software Release Notes: OMC-G System . . . . . . . . Order number 68P02903W01 68P02903W03 68P02903W37 68P02903W29 68P02903W46 68P02903W18 68P02903W47 68P02903W04 68P02903W19 68P02903W20 68P02903W76 68P02903W70
Related GPRS manuals

The following are related Motorola GPRS manuals: GPRS-001-103 GPRS-005-103 System Information: GPRS Equipment Planning . . 68P02903W02 System Information: GSN Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38

31st Jul 01
68P02901W43-J
17
GSM-100-423
BSS service manuals

The following are the Motorola Base Station service manuals, these manuals are not release dependent. The internal organization and makeup of service manual sets may vary, they may consist of from one to four separate manuals, but they can all be ordered using the overall catalogue number shown below: Classification number GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-203-020 GSM-206-020 GSM-205-020 GSM-204-020 GSM-207-020 GSM-209-020 GSM-208-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-104-SERIES GSM-200-SERIES Name Service Manual: BTS . . . . . . . . . . . . . . . . . . . . . . . . . . Service Manual: BSC/RXCDR . . . . . . . . . . . . . . . . . . Service Manual: M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cellcity and M-Cellcity+ . . . . . . . Service Manual: M-Cellaccess . . . . . . . . . . . . . . . . . . Service Manual: Horizonmicro . . . . . . . . . . . . . . . . . . Service Manual: Horizoncompact . . . . . . . . . . . . . . . Service Manual: Horizonmacro Indoor . . . . . . . . . . . Service Manual: Horizonmacro Outdoor . . . . . . . . . . Service Manual: Horizonoffice . . . . . . . . . . . . . . . . . . Service Manual: Horizonmicro2 Horizoncompact2 . Service Manual: Horizonmacro 12 Carrier Outdoor ExCell4 Documentation Set . . . . . . . . . . . . . . . . . . . . ExCell6 Documentation Set . . . . . . . . . . . . . . . . . . . . TopCell Documentation Set (GSM900) . . . . . . . . . . . TopCell Documentation Set (DCS1800) . . . . . . . . . . M-Cellmicro Documentation Set . . . . . . . . . . . . . . . . . Order number 68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02902W36 68P02902W15 68P02902W06 68P02902W12 68P02902W46 68P02902W61 68P02902W66 68P02900W50 68P02900W70 68P02901W80 68P02902W80 68P02901W90
GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include the Packet Control Unit (PCU) service manual which becomes part of the BSS for GPRS: Classification number GPRS-301-020 GPRS-302-020 Name Order number
Service Manual:GPRS Support Nodes (GSN) . . . . . 68P02903W05 Service Manual: Packet Control Unit (PCU) . . . . . . . 68P02903W10
Classification number
The classification number is used to identify the type and level of a manual. For example, manuals with the classification number GSM-100-2xx contain operating information.
Order number
The Motorola 68P order (catalogue) number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or Representative. Manuals are ordered using the order (catalogue) number. Remember, specify the manual issue required by quoting the correct suffix letter. Installation & Configuration: BSS Optimization 68P02901W43-J
18
31st Jul 01
GSM-100-423
GMR amendment
GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue. GMRs are issued in the form of loose leaf pages, with a pink instruction sheet on the front.
GMR procedure
When a GMR is received, check on the GMR amendment record page of this manual that previous GMRs, if any, have been incorporated. If not, contact your administrator or Motorola Local Office to obtain the missing GMRs. Remove and replace pages in this manual, as detailed on the GMR pink instruction sheet.

31st Jul 01
68P02901W43-J
19
GMR amendment record
GSM-100-423
GMR amendment record

Instructions
When a GMR is inserted in this manual, the amendment record below must be filled in to record the insertion. Retain the pink instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Incorporated by (signature)
Date
20
31st Jul 01
Chapter 1
Introduction to BSS optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 1 Introduction to BSS optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Guide to using this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrastructure sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 11 11 11 11 12 12 12

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Guide to using this manual

Purpose of this chapter
This chapter: S S S S Gives the purpose of the manual. Lists the prerequisites for using the manual. Explains the purpose of each manual chapter. States the range of equipment supported.
Audience
This manual is for technicians who work at base station system (BSS) sites. The manual assumes a degree of familiarity with Motorola BSS hardware and software. Technicians may use this manual to install, configure and optimize the BSS cabinets.
Purpose of the manual

Use this manual to: S S S S Optimize and integrate BSS and BTS sites. Calibrate the transceiver transmit power and check VSWR. Calibrate transceiver bay level offsets. Check other communications and calibrations relevant to each system.
Prerequisites
This manual assumes the reader knows: S S How to operate a local maintenance terminal (LMT). How the BSS and BTS systems work.
Structure
The manual contains the following chapters: S S S S S S S S S S Optimization chapter for all non M-Cell systems. Optimization chapter for M-Cell2 and M-Cell6. Optimization chapter for Horizonmacro. Preserve calibration procedure for all systems in previous chapters. Optimization chapter for M-Cellcity. Optimization chapter for M-Cellaccess and Horizonoffice. Integration chapter for all systems. Channel numbers and frequencies associated with all systems. Optimization chapter for drive testing a network. Optimization results forms used for those systems that have manual calibration.

31st Jul 01
68P02901W43-J
11
GSM-100-423
Related documentation
Refer to the appropriate service manuals.
Equipment supported
This GSR5 document supports the following Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, M-Cellaccess, Horizonmicro, Horizoncompact, Horizonoffice and Horizonmacro. The transceivers use, depending on capability, PGSM, EGSM, DCS1800 and PCS1900 frequencies.
Infrastructure sharing
Equipment from GSR3 onwards can employ infrastructure sharing, for use by multiband mobiles. This enables multiband support at site level, and for inter-cell handovers. GSM900 and DCS1800 equipment may be supported at a single site, but in separate cabinets for GSR3. Care should be taken to ensure that appropriate equipment and cables are used for each type, and that the appropriate parts of the Service Manuals are consulted.
12
31st Jul 01
Chapter 2
BTS4/5/6 ExCell TopCell & BSC optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 2 BTS4/5/6 ExCell TopCell & BSC optimization . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BTS4/5/6, ExCell, TopCell & BSC optimization . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 9-way cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 25-way cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test plug C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the dc power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually tuning the RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating DRCUs Tx power and VSWR check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the DRCU, DRCUII and DRCU3 bay level offset tables . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating SCU Tx power and VSWR check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the SCU900/1800 bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic check of the SCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 21 22 22 22 23 23 24 24 24 25 25 25 25 25 27 29 29 29 29 29 211 211 212 213 214 217 217 217 218 219 225 225 226 226 227 231 231 231 232 233 234 236 237 237 237 238 239 239

31st Jul 01
68P02901W43-J
iii
GSM-100-423
Checking the database for devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1/T1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK calibration record form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying ExCell alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smoke alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overtemperature alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Door open alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mains fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rectifier fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Low dc voltage alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inverter fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCB trip alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery fault alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comms PSU fail alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External alarm 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying DRCU faults on site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symptoms during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symptoms during commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure during normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure during commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization 68P02901W43-J
240 240 240 240 240 242 242 242 242 242 244 244 244 244 244 246 246 246 246 247 250 251 251 251 251 252 254 255 255 255 255 255 256 256 257 257 258 258 259 259 260 260 261 261 262 262 263 263 264 264 264 264 265 268
iv
31st Jul 01
GSM-100-423
Introduction to BTS4/5/6, ExCell, TopCell & BSC optimization
Introduction to BTS4/5/6, ExCell, TopCell & BSC optimization

This chapter provides information required to optimize and configure Motorola BTS4, BTS5, BTS6, ExCell, TopCell and BSC cabinets. For information about equipment not supplied by Motorola, for example battery chargers, power supplies and antennas, refer to the site specific documentation and the vendor instructions provided with the equipment. WARNING Hazardous voltages in excess of 50 V dc exist inside 48 V and 60 V cabinets. Use extreme caution when working on a cabinet with power applied. Remove all rings, watches and other jewellery.
NOTE In this chapter DRCU is used to mean DRCU, DRCUII, DRCU3, SCU900 or SCU1800. All procedures are the same for each unless otherwise indicated.
Code download
At initial loading, or when new system software is distributed to the system, the system software is downloaded from the OMC-R. If a new load is required at a site, request a download from the OMC-R to that site. NOTE If the existing software detects a corrupted segment in the current load, it automatically requests a download from the OMC-R.

31st Jul 01
68P02901W43-J
21
Test equipment, leads and plugs
GSM-100-423

Introduction
Various test equipment and test leads are required to carry out the optimization tests. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory, not in the field. Do not use test equipment that is beyond its due calibration date.
NOTE Allow test equipment to warm up for 30 minutes before use.
Requirements
The table lists the equipment required for system optimization: Quantity 1 Item IBM-compatible personal computer (PC) with: At least a 386 processor At least a 60 Mbyte hard drive At least 4 Mbit/s of RAM PCMCIA type 2 slot Signal generator Rubidium standard (minimum accuracy 1x1010) Commercial terminal emulator software (PC Plus or similar) Digital multimeter (HP E2378A or equivalent) 50 ohm RF dummy load (50 W minimum) Transportable cellphone ESD protection kit RF adaptor kit (RTLXQ98088 or equivalent) Adaptors: N to 7/16 in and N to N RF wattmeter (Bird model 43 or equivalent) with 5 W, 10 W, 25 W and 50 W elements N to N male coaxial cable (2 m long, calibrated) N to N male coaxial cable (4 m long, calibrated) 9 to 9-way cable (PC to DCB/CEB, DRCU, MCU, RTC or TCU) 9 to 25-way cable (PC to GPROC) Type 43 loopback cables 23 cm (9 in.) long BIB loopback plug Test plugs A, B and C
1 1 1 1 1 1 1 1 1 1 1 1 1 2 6 1 1 each
22
31st Jul 01
GSM-100-423
9-way to 9-way cable

The diagram shows the cable for PC to DCB/CEB, DRCU, MCU, RTC, or TCU connections:
PIN NUMBER PIN NUMBER
2 3 5 4 6 7 8
4 m LONG SCREENED CABLE TO PC COMMUNICATIONS PORT 9-WAY D-TYPE F
3 2 7 5
TO DESTINATION PORT CONNECTOR 9-WAY D-TYPE M
9-way to 25-way cable

The diagram shows the cable for PC to GPROC connection:
1 2 3 4 5 6 7 8 9
4 m LONG SCREENED CABLE 9-WAY D-TYPE F
8 3 2 20 7 6 4 5 22
25-WAY D-TYPE M

31st Jul 01
68P02901W43-J
23
GSM-100-423
Test plug A
The table lists the pin connections for test plug A: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Connect with a 1 kohm resistor Connect with a 1 kohm resistor Connect with a 1 kohm resistor Connect with a 1 kohm resistor Connect with a 10 kohm resistor Connect with a 10 kohm resistor Connect with a 10 kohm resistor Connect with a 10 kohm resistor
Test plug B
The table lists the pin connections for test plug B: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Test plug C
The table lists the pin connections for test plug C: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link
24
31st Jul 01
GSM-100-423
Testing the dc power supply

Introduction
WARNING The person carrying out these tests must be accompanied by a second person acting in a safety capacity. The objective of the dc power supply tests is to verify that the main dc supply and power supply modules are operating. NOTE In this section, the term PSM is used to indicate a DPSM, EPSM, or IPSM as appropriate.
Test equipment
No special test equipment is required to carry out the dc power supply tests.
Commands
No special software commands are required for the dc power supply tests.
Procedure
To carry out the dc power supply tests:
Preparation for test

1. 2. 3. Ensure that none of the full-size modules, half-size modules or PSMs are seated in their backplane connectors. Set all cabinet power supply circuit breakers to the OFF position. Positive earth BTS4 cabinets only. Go to step 4. All other BTS cabinets and all BSSC cabinets. Go to Power supply test step 1. Firmly seat all power converters (up to four depending upon the cabinet configuration).
4.

31st Jul 01
68P02901W43-J
25
GSM-100-423
Power supply test

1. 2. Apply power to the cabinet. Positive earth BTS4 cabinets only. Set circuit breakers CB5 and CB6. Positive earth BSSC cabinets only. Set circuit breakers CB4 and CB5. Negative earth BTS6 and BSSC2 cabinets only. Set circuit breaker CB1. Positive earth BTS6 and BSSC2 cabinets only. Set circuit breaker CB1 and go to step 4. Check that the cabinet fans are operating. If the fans are not operating: Step a. Action Check that dc power is connected to the cabinet (if not, suspect the dc power supply, the power cabling and the cabinet power input connections). Check the fan fuses and the dc power cabling to the fans, and to the power converters (positive earth BTS4) or fan power converters (positive earth BSSC). Verify correct power converter (positive earth BTS4) or fan power converter (positive earth BSSC) operation by substituting known good units. NOTE With exception to the cabinets detailed in step 6 below. The fans must be operating before PSMs or DRCUs can be switched on. 4. 5. 6. Firmly seat all PSMs in their backplane connectors. Set the circuit breaker to ON for each PSM. Check that the green LED active indicator for the chosen PSM lights. Positive earth BTS6 and BSSC2 cabinets only. Check that the cabinet fans are operating. If the fans are not operating: Step a. Action Check that dc power is connected to the cabinet (if not, suspect the dc power supply, the power cabling or the cabinet input power connections). Check the fan fuses and the dc power cabling to the fans.
3.
b.
c.
b. 7.
Set the circuit breaker for each DRCU to ON.
Site restoration
1. 2. Insert all processor cards into their backplane connectors. Insert all other modules into their backplane connectors.
26
31st Jul 01
GSM-100-423
Circuit breakers
The tables list the cabinet circuit breaker assignments:
48/60 V BTS cabinets

BTS4 CB 11 10 9 8 7 6 5 4 3 2 1 Protects PSM2 PSM1 PSM0 PC4 PC3 PC2 PC1 DRCU3 DRCU2 DRCU1 DRCU0 CB 11 10 9 8 7 6 5 4 3 2 1 BTS6 Protects Not fitted IPSM2 IPSM1 IPSM0 DRCU5 DRCU4 DRCU3 DRCU2 DRCU1 DRCU0 DAB
+27 V BTS cabinets

BTS4/BTS5 CB 11 10 9 8 7 6 5 4 3 2 1 Protects PSM2 PSM1 PSM0 Not used Not used Not used DRCU4 DRCU3 DRCU2 DRCU1 DRCU0 CB 11 10 9 8 7 6 5 4 3 2 1 BTS6 Protects Not fitted EPSM2 EPSM1 EPSM0 DRCU5 DRCU4 DRCU3 DRCU2 DRCU1 DRCU0 DAB

31st Jul 01
68P02901W43-J
27
GSM-100-423
48/60 V BSSC/RXCDR cabinets

BSSC CB 11 10 9 8 7 6 5 4 3 2 1 Protects PSM2L PSM1L PSM0L PSM2U PSM1U PSM0U FPC2 FPC1 Not used Not used Not used CB 11 10 9 8 7 6 5 4 3 2 1 BSSC2 Protects Not fitted IPSM2L IPSM1L IPSM0L IPSM2U IPSM1U IPSM0U Not used Not used Not used DAB
+27 V BSSC/RXCDR cabinets

BSSC CB 11 10 9 8 7 6 5 4 3 2 1 Protects PSM2L PSM1L PSM0L PSM2U PSM1U PSM0U Not used Not used Not used Not used Not used CB 11 10 9 8 7 6 5 4 3 2 1 BSSC2 Protects Not fitted EPSM2L EPSM1L EPSM0L EPSM2U EPSM1U EPSM0U Not used Not used Not used DAB
28
31st Jul 01
GSM-100-423
Manually tuning the RTC

Introduction
Follow this procedure to tune a remotely tuneable combiner (RTC) to a desired frequency. NOTE This procedure is not applicable to DCS1800 or PCS1900 systems.
Test equipment
The following test equipment is required to carry out this procedure: S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A copy of the RTC control program. A 9 to 9-way cable.
Commands
No special software commands are required for this procedure.
Procedure
Proceed as follows:
Tuning preparation
1. 2. Ensure that the RTC jumpers are in the correct position for manual operation. Only one link must be fitted; remove the redundant link. Connect the 9 to 9-way cable from the serial A port on the PC to the RS232 port on the RTC (behind the top left side of the RTC).
Tuning the RTC

1. Type the following command at the PC to start the RTC tuning program: COM00_02 2. Press Enter eleven times. The following message is displayed:
Press a highlighted letter of an option or parameter.
3.
Select the manual mode of communication with the RTC by typing: V
4. 5.
Press Enter four times. The following message is displayed:

Press a highlighted letter of an option or parameter.
Select address by typing: A

31st Jul 01
68P02901W43-J
29
GSM-100-423
6.
Enter the required address: 255 or the address determined by the jumpers and then press Enter.
7.
Select cavity by typing: Y
8. 9.
Follow the instructions displayed at the bottom of the screen and then press Enter. Select channel by typing: C
10. 11.
Follow the instructions displayed at the bottom of the screen and select the cavity to be tuned. Select download by typing: D Repeat step 9 to step 11 for each cavity that is to be tuned.
12.
Quit the RTC tuning program by typing: Q To restore the site return the RTC jumpers to the auto position.
210
31st Jul 01
GSM-100-423
Calibrating DRCUs Tx power and VSWR check

Introduction
Follow this procedure to set the predefined maximum transmitter output power at the top of the cabinet, and to ensure that antenna feeders and connectors are properly terminated. The objective of the VSWR check and output power calibration procedure is to ensure that antenna feeders and connectors are properly terminated and then set the pre-defined maximum transmitter output power at the top of the cabinet. When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures. These procedures aim to produce a radio that exhibits a flat frequency response over the full PGSM band. In the case of the transmitter, this is performed by sharing out the 124 channels over eight detector groups (the detector being the device that maintains a steady output power level). In the field, the procedure for setting the transmit output power involves using a set of commands called Cell Site Power (CSPWR). During CSPWR the cabinet output power can be trimmed to account for any abnormalities that may occur between the DRCU and the top of the cabinet. The offset is effectively subtracted from the requested power level, such that for whatever channel is selected, a steady output is maintained at the top of the cabinet. When the CSPWR command is typed at the DCB/RCB/SCB prompt, it effectively executes a small script containing the following commands: TS A CHAN 60 TS A TX 00 MDLTR UC Set all timeslots to channel 60. Set all timeslots to full power. Turn the modulation off.
Prior to executing the CSPWR command, it assumes that the synthesizers are hopping (not locked) as is the case after the unit is powered up for the first time. To alter the power, typing U increments or typing D decrements the power setting byte. On completion, the command is exited and the appropriate power byte is saved to RAM. To specify a specific channel (instead of defaulting to channel 60), two extra commands must be entered prior to executing the CSPWR command, one to set the appropriate channel and the other to lock the synthesizer. By locking the synthesizer, the channel selection made in the CSPWR command will be ignored and the output is maintained at the frequency specified. NOTE This procedure applies to the DRCU, DRCUII and DRCU3. In this section DRCU is used to mean DRCU, DRCUII, or DRCU3. The DCB prompt applies to the DRCU. The RCB prompt applies to the DRCUII. The SCB prompt applies to the DRCU3.

31st Jul 01
68P02901W43-J
211
GSM-100-423
Test equipment
The following equipment is needed to carry out the procedure: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter or equivalent, with 5 W and 50 W elements. A 50 ohm 50 W dummy load. A 9 to 9-way cable. A 9 to 25-way cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola cellular base stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
212
31st Jul 01
GSM-100-423
Commands
The following commands must be used to carry out the procedure: BSS MMI command lock_device unlock_device clear_cal_data DRCU emulator command SWAP C 0 SWAP E A SWAP P 0 EXEC C 0 EXEC P 0 HALT P 0 HALT C 0 TEST ACTIVE P 0 CSPWR Function Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis. Function Swaps control code between memories to check data. Swaps equalizer code between memories to check data. Swaps PA code between memories to check data. Executes control code currently held in RAM. Executes PA code currently held in RAM. Places the power amplifier into active standby mode. Places the SCB into active standby mode. Places the DRCU into test mode. Places the power amplifier into call processing mode. Sets the cell site power level using the following controls: u Increases cell site power by 0.2 dB. d Decreases cell site power by 0.2 dB. ESC Exits the calibration session and stores the settings. TS T CHAN XX
Timeslot set up. Where: T = timeslot number or A = ALL. XX = ARFCN to tune timeslot to.
SYNTH N
Locks the transmitted frequency on synthesizer n.
NOTE The symbol 0 in the commands listed above is a zero.

31st Jul 01
68P02901W43-J
213
GSM-100-423
Procedure
Proceed as follows:
Initial preparation
1. 2. 3. 4. Connect the 9 to 25-way cable from the PC serial A port to a GPROC TTY port. At the PC start the terminal emulator program. At the CUST/MMI prompt, enter the password. Type: lock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). the DRI number on the antenna.
5.
Type: clear_cal_data # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). the DRI number on the antenna.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 6. Connect the wattmeter, with 50 W element and dummy load to the TX port, at the top of the cabinet. If a remote tune combiner is fitted, the relevant port must be tuned to channel 60. In the case of external combiners, connect the wattmeter, with 50 W element and dummy load, to the output port of the combiner. 7. 8. 9. 10. Disconnect and remove the 9 to 25-way cable. Disable the DRI controlling the DRCU under test using the disable switch on the DRI front panel. Connect the 9 to 9-way cable from the PC serial A port to a CONT PRCSR port on the DRCU. Reset the DRCU using the manual reset button. Installation & Configuration: BSS Optimization 68P02901W43-J
214
31st Jul 01
GSM-100-423
Tx forward power check

1. 2. Enter the boot code passwords. Type: SWAP C 0 EXEC C 0 3. 4. At the DCB/RCB/SCB prompt, enter the op code password. Type: SWAP P 0 EXEC P 0 SWAP E A TEST ACTIV P 0 5. 6. If an RTC is fitted go to step 7. To select all timeslots and a particular channel, enter the following commands at the DCB/RCB/SCB prompt: TS A CHAN NNN SYNTH N Where: A NNN N 7. At the DCB/RCB/SCB prompt type: CSPWR 8. 9. Monitor and record the wattmeter reading (the forward output power). Press ESC. is: all the timeslots. the specified channel number. the synthesizer number.
Tx reverse power check

1. 2. 3. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Type CSPWR. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 1 W or 5% of forward power. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 4. Press ESC.

31st Jul 01
68P02901W43-J
215
GSM-100-423
Setting Tx output power

1. 2. Replace the 5 W element in the wattmeter with a 50 W element, and connect the meter in the forward direction. Type CSPWR. The following message is displayed:
Hit U or D until desired max is measured then hit (ESC, CTLY OR CTLC)
3.
Type U or D to achieve 43 dBm (20 W) measured power at the top of the cabinet. When combiners are used the full power may not be achieved. The acceptable measured power levels are tabulated below: Equipment fitted 1 stage combiner RTC Measured power 42.55 dBm (18 W) 42.75 dBm (18.8 W)
An additional hybrid combiner can add a 3.2 dB loss. As U or D is entered a message similar to the following example is displayed:
D P:47.8 dBm Cell Site Offset :1
The message indicates the DRCU output power and offset (1 step=0.2 dB). 4. When the required level is achieved press: ESC The cell site offset can be checked by connecting to the CONT PRCSR port and reading the following memory locations: For a DRCU, enter For a DRCUII, enter For a DRCU3, enter R E:5B13 R E:5B0C R E:5B0C
Site restoration
1. 2. 3. 4. 5. Remove the 9 to 9-way cable and reconnect the DATA IN fibre cable. Connect the serial A port on the PC to a GPROC TTY port using the 9 to 25-way cable. Power the DRCU down and remove the wattmeter and dummy load from the Tx port. Reconnect the antenna lead to the Tx port. Power up the DRCU. At the CUST MMI prompt enter: unlock_device # dri a * 0 Where: # a * is: the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
6.
Remove the 9 to 25-way cable. The DRCU is now in call processing mode. Installation & Configuration: BSS Optimization 68P02901W43-J
216
31st Jul 01
GSM-100-423
Calibrating the DRCU, DRCUII and DRCU3 bay level offset tables
Introduction
Follow this procedure to calibrate the bay level offset tables to compensate for the losses or gains, due to preselectors and RF cabling, from the antenna inputs at the BTS to the DRCU, DRCUII or DRCU3 input. NOTE This procedure applies only to the DRCU, DRCUII and DRCU3. In this section DRCU is used to mean DRCU, DRCUII or DRCU3. Exceptions are identified by DRCUII or DRCU3 alternatives. The DCB prompt applies to the DRCU. The RCB prompt applies to the DRCUII. The SCB prompt applies to the DRCU3.
Test equipment
The following test equipment is required to carry out this procedure: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 50 ohm 50 W dummy load. A signal generator. 9 to 9-way cable. 9 to 25-way cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola cellular base stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
217
GSM-100-423
Commands
The following commands must be used to carry out this procedure: NOTE 1. The 0 used in the commands in this procedure is a zero. 2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands and may be entered in upper or lower case; the rest of the commands in this list are DRCU (emulator) commands and case is as shown. BSS MMI command lock_device unlock_device clear_cal_data DRCU emulator command SWAP C 0 EXEC C 0 SWAP P 0 EXEC P 0 SWAP E A CONFGR E A TEST SNDEQ 0 3C IQDC0 0 IQDCP 0 AIC OUT TS A CHAN # TS A ANT # CAL BAY @1/@2 CALCHK Function Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis. Function Swaps controller code between memories to check validity. Executes controller code currently stored in RAM. Swaps PA code between memories to check validity. Executes PA code currently stored in RAM. Swaps equalizer code between memories to check validity. Sends call processing calibration tables to DEQDSP. Places the DRCU into test mode. Emulates equalizer messaging. Queries equalizer for IQ absolute dc offset. Passes dc offset information to equallizer DSP. Disables automatic intermodulation compensation. Sets all timeslots to channel #. Sets all timeslots to antenna #. Calibrates the bay level receive equipment. Verifies calibration data.
218
31st Jul 01
GSM-100-423
Procedure
Proceed as follows:
Initial preparation
1. 2. Connect the 9 to 25-way cable from the PC serial A port to a GPROC TTY port. At the PC start the terminal emulator program. WARNING Failure to lock the cell could result in the BCCH transmitting into, and causing damage to the signal generator. The maintenance engineer could receive RF burns when connecting to the antenna socket. 3. Type: lock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
4.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 5. 6. 7. 8. If the DRCU is not connected to a Tx antenna, connect a dummy load to the Tx port of the DRCU under test. Connect the RF output of the signal generator to the DRCU Rx port. Disconnect the 9 to 25-way cable from the GPROC TTY port. Connect the serial A port on the PC to the CONT PRCSR port on the DRCU using the 9 to 9-way cable.

31st Jul 01
68P02901W43-J
219
GSM-100-423
Calibration setup
1. Input the entry level password to obtain the DCB/RCB/SCB prompt. NOTE DCB is the prompt for DRCU. RCB is the prompt for DRCUII. SCB is the prompt for DRCU3. For DRCU3, reset using the front panel switch, and at the SCB prompt enter the boot passwords one and two. 2. At the DCB/RCB/SCB prompt type: SWAP C 0 EXEC C 0 3. At the DCB/RCB/SCB prompt enter the password. NOTE For DRCU3, the entered password is password three. 4. At the DCB/RCB/SCB prompt type: SWAP P 0 EXEC P 0 SWAP E A TEST SNDEQ 0 3C IQDCO 0 IQDCP 0 AIC OUT 5. Set the signal generator to the first channel frequency (channel 04 = 890.801 MHz) at a level of 65.2 dBm. NOTE The Tx level of the signal generator must be set to allow for losses in the test leads used. It is VITAL that the signal generator and cables are correctly calibrated, and the RF cables are in good order. 6. If a receiver matrix is fitted, go to Calibration with a receive matrix.
220
31st Jul 01
GSM-100-423
Calibration with a sixway splitter

1. Connect the output of the signal generator to branch 1 of the antenna to be used (RX1A, RX2A or RX3A) for the DRCU under test. At the DCB/RCB/SCB prompt type the appropriate command for (RX1A, 2A & 3A): TS A ANT 1 (2) OR (3) 2. At the DCB/RCB/SCB prompt type: TS A CHAN # Where: # is: the channel number shown in Table 2-1.
CAL BAY @1 3. Repeat step 2 with the signal generator set to the appropriate frequency for all the following test frequencies: Table 2-1 Channel frequency listing Channel 04 12 20 28 36 44 52 60 4. Frequency (MHz) 890.801 892.401 894.001 895.601 897.201 898.801 900.401 902.001 Channel 68 76 84 92 100 108 116 122 Frequency (MHz) 903.601 905.201 906.801 908.401 910.001 911.601 913.201 914.401
Go to step 14 at the end of Calibration with a receive matrix.
Calibration with a receive matrix

1. 2. 3. Ensure that the DIP switches on the receiver matrix are set to output signal selection DRCU data controlled. Connect the output of the signal generator to RX1A. At the DCB/RCB/SCB prompt type: TS A ANT 1 4. At the DCB/RCB/SCB prompt type: TS A CHAN # Where: # is: the channel number shown in Table 2-1.
CAL BAY @1 5. 6. 7. Set the signal generator to the appropriate frequency and repeat step 4 for all test frequencies listed in Table 2-1. Connect the output of the signal generator to RX2A. At the DCB/RCB/SCB prompt type: TS A ANT 2

31st Jul 01
68P02901W43-J
221
GSM-100-423
8.
At the DCB/RCB/SCB prompt type: TS A CHAN # Where: # is: the channel number shown in Table 2-1.
CAL BAY @1 9. 10. 11. Set the signal generator to the appropriate frequency and repeat step 8 for all test frequencies listed in Table 2-1. Connect the output of the signal generator to RX3A. At the DCB/RCB/SCB prompt type: TS A ANT 3 12. At the DCB/RCB/SCB prompt type: TS A CHAN # Where: # is: the channel number shown in Table 2-1.
CAL BAY @1 13. 14. Set the signal generator to the appropriate frequency and repeat step 12 for all test frequencies listed in Table 2-1. Repeat steps 5 (under Bay level offset calibration) to 13 (under Calibration with a receive matrix) for branch 2 using connectors RX1B, RX2B and RX3B respectively at the top of the cabinet. Enter @2 instead of @1 in the CAL BAY command.
Stored bay level offset verification

1. To verify that the bay level offset values have been stored in EPROM use the read command with the required offset table location as an argument; for example: R E: 5391 53A0 in the case of Branch 1 DRCU antenna 1. Branch 1 Ante nna
1 2 3
DCB> DCB> DCB
DRCU R E:5391 53A0 R E:53C1 53D0 R E:53F1 5400

RCB> RCB> RCB>
DRCUII R E:538A 5399 R E:53BA 53C9 R E:53EA 53F9

SCB> SCB> SCB>
DRCU3 R E:538A 5399 R E:53BA 53C9 R E:53EA 53F9
Branch 2 Ante nna

1 2 3
DCB> DCB> DCB>
DRCU R E:5421 5430 R E:5451 5460 R E:5481 5490

RCB> RCB> RCB>
DRCUII R E:541A 5429 R E:544A 5459 R E:547A 5489

SCB> SCB> SCB>
DRCU3 R E:541A 5429 R E:544A 5459 R E:547A 5489
2.
If the bay level calibration is successful, each of the locations shown in the appropriate table, will contain valid offsets and must not contain the factory default of 80. The presence of 80, will result in error DRI 218 being reported when the unit is unlocked. Installation & Configuration: BSS Optimization 68P02901W43-J
222
31st Jul 01
GSM-100-423
3.
If the value 80 is present, it indicates that the bay level calibration was unsuccessful, and that it will need to be repeated, after checking the configuration and RF cables etc. At the DCB/RCB/SCB prompt type: CALCHK All the calibrated parameters for the DRCU are displayed.
4.
5.
To check the calibration valid bits are set correctly: If transceiver is... DRCU DRCUII DRCU3 Then type... DCB> R E: 5B1C RCB> R E: 5B15 SCB> R E: 5B15
If the reply is FFFFFF on a DRCU or FFFE00 on a DRCUII/DRCU3, the calibration valid bits are set correctly. NOTE The bits must be set, otherwise the bay level tables will not be used as offset, and a default value of 80 will be used. 6. To enable setting of the calibration valid bits on a DRCU at the DCB/RCB/SCB prompt type: WRENB E 7. To set the calibration valid bits at the DCB/RCB/SCB prompt: If transceiver is... DRCU DRCUII DRCU3 8. Then type... DCB> W E: 5B1C FFFFF RCB> W E: 5B15 FFFE00 SCB> W E: 5B15 FFFE00
To protect the calibration valid bits set on a DRCU at the DCB/RCB/SCB prompt type: WRPTC E
9.
To check if the calibration valid bits are set correctly: If transceiver is... DRCU DRCUII DRCU3 Then... DCB> R E: 5B1C RCB> R E: 5B15 SCB> R E: 5B15
If the reply is FFFFFF on a DRCU or FFFE00 on a DRCUII/DRCU3, the calibration valid bits are set correctly.

31st Jul 01
68P02901W43-J
223
GSM-100-423
Site restoration
1. 2. 3. Remove the 9 to 9-way cable. Connect the serial A port on the PC to a GPROC TTY port using the 9 to 25-way cable. Type: unlock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
4.
Remove the 9 to 25-way cable. The DRCU is now in call processing mode.
224
31st Jul 01
GSM-100-423
Calibrating SCU Tx power and VSWR check

Introduction
NOTE This procedure applies only to the SCU900 and SCU1800. TCUs can be converted to SCU use in a BTS cabinet, by operation of a switch on the TCU unit. The TCU can then be considered an SCU, with the procedure the same as for an SCU, except where stated. Ensure that a TCU is switched to SCU mode before connection to B2. (In TCU mode the B2 inner is at +12 V dc to power the DLNB in M-Cell equipment). Follow this procedure to set the predefined maximum transmitter output power at the top of the cabinet, and to ensure that antenna feeders and connectors are properly terminated. The objective of the VSWR check and output power calibration procedure is to ensure that antenna feeders and connectors are properly terminated and then set the pre-defined maximum transmitter output power at the top of the cabinet. When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures. These procedures aim to produce a radio that exhibits a flat frequency response over the full GSM band. In the case of the transmitter, this is performed by sharing out the channels over three detector groups (the detector being the device that maintains a steady output power level). In the field, the procedure for setting the transmit output power involves using a set of commands called Cell Site Power (CSPWR). During CSPWR the cabinet output power can be trimmed to account for any abnormalities that may occur between the SCU and the top of the cabinet. The offset is effectively subtracted from the requested power level, such that for whatever channel is selected, a steady output is maintained at the top of the cabinet. When the CSPWR command is typed at the SCP prompt, it effectively executes a small script containing the following commands: TS A CHAN 700 TS A CHAN 31 TS A TXP 00 MDLTR UC Set all timeslots to channel 700 (SCU1800). Set all timeslots to channel 31 (SCU900). Set all timeslots to full power. Turn the modulation off.
Prior to executing the CSPWR command, it assumes that the synthesizers are hopping (not locked) as is the case after the unit is powered up for the first time. To alter the power, typing U increments or typing D decrements the power setting byte. On completion, the command is exited and the appropriate power byte is saved to RAM. To specify a specific channel (instead of defaulting to channel 31 or 700), two extra commands must be entered prior to executing the CSPWR command, one to set the appropriate channel and the other to lock the synthesizer. By locking the synthesizer, the channel selection made in the CSPWR command will be ignored and the output is maintained at the frequency specified. To save to non-volatile memory, the SAVE CAL TX command must be used.

31st Jul 01
68P02901W43-J
225
GSM-100-423
Test equipment
The following equipment is needed to carry out this procedure: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter or equivalent, with 5 W and 50 W elements. A 50 ohm 50 W dummy load. A 9 to 9-way cable. A 9 to 25-way cable.
Commands
The following commands must be used to carry out this procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands and may be entered in upper or lower case; the rest of the commands in this list are all SCU (emulator) commands and case is as shown. BSS MMI command lock_device unlock_device clear_cal_data state SCU emulator command SWAP C 0 SWAP E A EXEC C 0 TEST CSPWR Function Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis. Displays the current status of devices or functions. Function Swaps SCP code between memories to check data. Swaps EQB code between memories to check data. Executes SCP code currently held in RAM. Places the SCU into test mode. Sets the cell site power level using the following controls: U Increases cell site power by 0.2 dB. D Decreases cell site power by 0.2 dB. ESC Exits the calibration session and stores the settings. TS A CHAN XX
Timeslot set up. Where: T = Timeslot No. or A = ALL. XX = ARFCN to tune timeslot to.
SYNTH N SAVE CAL TX
Locks the transmitted frequency on synthesizer n. Saves the calibration settings.
226
31st Jul 01
GSM-100-423
Procedure
Proceed as follows:
Initial preparation
1. 2. 3. 4. Connect the 9 to 25-way cable from the PC serial A port to a GPROC TTY port. At the PC start the terminal emulator program. At the CUST/MMI prompt, enter the password. Type: lock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). the DRI number on the antenna.
5.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 6. Connect the wattmeter, with 50 W element and dummy load, to the Tx port at the top of the cabinet. If an RTC is fitted, the relevant port must be tuned to the channel the RTC is set to. If external combiners are used connect the wattmeter, with 50 W element and dummy load, to the output port of the combiner. 7. 8. 9. Disconnect and remove the 9 to 25-way cable. Connect the 9 to 9-way cable from the PC serial A port to a CONT PRCSR port on the SCU. Reset the SCU under test using the front panel reset button.

31st Jul 01
68P02901W43-J
227
GSM-100-423
Tx forward power check

1. 2. Enter the boot passwords (different from the DRCU passwords). At the SCP prompt enter: SWAP C 0 EXEC C 0 .<LEVEL_3_PASSWORD> (different from the DRCU password) TEST 3. To select all timeslots and a particular channel, enter the following commands at the SCP prompt: TS A CHAN XXX SYNTH Y Where: A XXX Y NOTE When an RTC is fitted, the channel number must be the same as the one chosen for the RTC cavity connected to this SCU. 4. At the SCP prompt type: CSPWR 5. 6. Monitor and record the wattmeter reading (the forward output power). Press ESC. is: all the timeslots (TS). the specified channel number. the synthesizer number.
Tx reverse power check

1. 2. 3. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Type CSPWR. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 1 W or 5% of forward power. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 4. Press ESC.
228
31st Jul 01
GSM-100-423
Setting Tx output power

1. 2. 3. Replace the 5 W element in the wattmeter with a 50 W element and connect the meter in the forward direction. Type CSPWR. Type U or D to achieve measured power at the top of the cabinet: 42.05 dBm (16 W) for SCU1800, or 43 dBm (20 W) for SCU900. When combiners are used the full power may not be achieved. The acceptable measured power levels are tabulated below: Equipment fitted 1 stage combiner RTC Measured power (SCU900) 42.55 dBm (18 W) 42.75 dBm (18.8 W) Measured power (SCU1800) 39.0 dBm (8 W) 40 dBm (10 W)
An additional hybrid combiner can add a 3.2 dB loss. As U or D is entered, a message like the following example is displayed:
D P:43.8 dBm Cell Site Offset :1
The message indicates the SCU output power and offset value (one step = 0.2 dB). 4. 5. When the required level is achieved, press ESC. At the SCP prompt enter: SAVE CAL TX The cell site offset can be checked by reading its memory location: R F:15780 Repeat the forward and reverse output power checks and the setting up Tx output power, for all SCUs.
Site restoration
1. 2. 3. 4. 5. Remove the 9-way cable from the CNTRL PRSCR port and press the reset button on the SCU front panel. Connect serial A port on the PC to a GPROC TTY port using the 9 to 25-way cable. Power the SCU down and remove the wattmeter from the Tx port. Reconnect the antenna lead to the Tx port. Power up the SCU. At the customer MMI prompt enter: unlock_device # dri a * 0 state # dri a * 0 Where: # a * is: the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.

31st Jul 01
68P02901W43-J
229
GSM-100-423
6.
Remove the 9 to 25-way cable from the GPROC TTY port. The SCU is now in call processing mode.
230
31st Jul 01
GSM-100-423
Calibrating the SCU900/1800 bay level offset tables

Introduction
Follow this procedure to calibrate the bay level offset tables to compensate for the losses or gains due to preselectors and RF cabling from the antenna inputs at the BTS to the SCU900 or SCU1800 input. CAUTION Ensure that a TCU is switched to SCU mode before connection to B2. (In TCU mode, the RX2 inner is at +12 V dc to power the DLNB in M-Cell equipment.) NOTE This procedure applies only to the SCU900 and SCU1800. TCUs can be converted to SCU use in a BTS cabinet, by operation of a switch on the TCU unit. The TCU can then be considered an SCU, with the procedure the same as for an SCU, except where stated.
Test equipment
The following test equipment is required: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 50 ohm 50 W dummy load. A signal generator (0 to 2 GHz). 9-way to 9-way cable. 9-way to 25-way cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola cellular base stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
231
GSM-100-423
Commands
The following commands must be used to carry out the procedure: NOTE 1. The 0 used in the commands in this procedure is a zero. 2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands and may be entered in upper or lower case; the remainder of the commands in this list are all SCU (emulator) commands, input as shown. The first SCU password must be in upper case. BSS MMI command lock_device unlock_device clear_cal_data SCU emulator command SWAP C 0 EXEC C 0 SWAP E A CONFGR E A TEST CAL BAY @1/@2 EQTEST 0 IQDCP 0 AIC OUT TS A CHAN # TS A ANT # R F:XX YY SYNTH 1 SYNTH NRM SAVE CAL BAY BAYDONE @N Function Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis. Function Swaps DPC code from ROM to RAM and checks validity. Executes DPC code currently stored in RAM. Swaps EQB code from ROM to all four EQDSPs and checks validity. Sends call processing calibration tables to equaliser. Places the SCU/TCU into test mode. Calibrates the bay level receive equipment. Puts equalizer 0 into test mode and checks status. Passes the factory calibrated dc offset information stored in ROM to EQDSP 0. Disables automatic intermodulation compensation. Sets all timeslots to channel #. Sets all timeslots to antenna #. Reads flash memory bay level data held at addresses XX to YY. Stops synthesizer switching with synthesizer 1 permanently on. Enables synthesizer switching into normal working. Transfers bay level calibration data in RAM to ROM. Informs control processor that bay level calibration is valid for branch N and sets bay level flag.
232
31st Jul 01
GSM-100-423
Setting up procedure
The radio has to first be locked, a dummy load connected if no antenna, the SCU reset and set up for bay level calibration. Proceed as follows: 1. 2. Connect the 9-way to 25-way cable from the PC serial A port to a GPROC TTY port. At the PC start the terminal emulator program. WARNING Failure to lock the cell could result in the BCCH transmitting into, and causing damage to the signal generator. The maintenance engineer could receive RF burns when connecting to the antenna socket. 3. Type: lock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
4.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 5. 6. 7. 8. If a Tx antenna is not connected to the SCU under test connect a 50 ohm 50 W dummy load to the Tx port of the SCU under test. Remove the 9-way to 25-way cable from the PC serial A port to the GPROC TTY port. Connect the serial A port on the PC to the CNTRL PRCSR port on the SCU using the 9-way to 9-way cable. Reset the SCU using the front panel reset button.

31st Jul 01
68P02901W43-J
233
GSM-100-423
9. 10.
Enter the boot passwords. At the SCP prompt type: SWAP C 0 EXEC C 0 .<LEVEL_3_PASSWORD> (different from the (D)RCU password) SWAP E A CONFGR E A TEST AIC OUT EQTEST 0 IQDCP 0
Bay level calibration for branch1 RX1A

1. 2. Connect the output of the signal generator to branch 1 of the antenna port (RX1A, RX2A or RX3A at the top of the cabinet) for the SCU under test. Set the signal generator to the first channel test frequency shown in Table 2-2 or Table 2-3 at a level of 65.2 dBm. NOTE The Tx level of the signal generator must be set to allow for losses in the test leads used. It is VITAL that the signal generator and cables are correctly calibrated, and the RF cables are in good order. 3. At the SCP prompt type: TS A ANT 1 4. At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 2-2 or Table 2-3
5.
At the SCP prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM NOTE When the synthesizer is left unlocked, the bay level figure can vary as much as 1dB at certain frequencies. By locking the synthesizer (using commands SYNTH 1 and SYNTH NRM this variation can be reduced to 0.1 dB.
234
31st Jul 01
GSM-100-423
6.
Repeat steps 4 and 5 for each signal generator test frequency in Table 2-2 or Table 2-3. NOTE The BTS cabinets described in this chapter only support PGSM, and not EGSM.
7.
At the SCP prompt type: SAVE CAL BAY
This transfers the bay level calibration figures to non-volatile SCU memory. Table 2-2 GSM900 test frequencies Channel 03 11 19 27 35 43 51 59 Frequency (MHz) 890.601 892.201 893.801 895.401 897.001 898.601 900.201 901.801 Channel 67 75 83 91 99 107 115 123 Frequency (MHz) 903.401 905.001 906.601 908.201 909.801 911.401 913.001 914.601
Table 2-3 DCS1800 test frequencies Channel 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 Frequency (MHz) 1711.001 1712.601 1714.201 1715.801 1717.401 1719.001 1720.601 1722.201 1723.801 1725.401 1727.001 1728.601 1730.201 1731.801 1733.401 1735.001 1736.601 1738.201 Channel 708 716 724 732 740 748 756 764 772 780 788 796 804 812 820 828 836 844 Frequency (MHz) 1749.401 1751.001 1752.601 1754.201 1755.801 1757.401 1759.001 1760.601 1762.201 1763.801 1765.401 1767.001 1768.601 1770.201 1771.801 1773.401 1775.001 1776.601

31st Jul 01
68P02901W43-J
235
GSM-100-423
Table 2-3 DCS1800 test frequencies Channel 660 668 676 684 692 700 Frequency (MHz) 1739.801 1741.401 1743.001 1744.601 1746.201 1747.801 Channel 852 860 868 876 883 Frequency (MHz) 1778.201 1779.801 1781.401 1783.001 1784.401
Bay level repeat for RX2A

1. 2. 3. Connect the output of the signal generator to RX2A. Set the signal generator to the first channel test frequency shown in Table 2-2 or Table 2-3. At the SCP prompt type: TS A ANT 2 4. At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 2-2 or Table 2-3.
5.
At the SCP prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM
6. 7.
Repeat steps 4 and 5 for each signal generator test frequency in Table 2-2 or Table 2-3. At the SCP prompt type: SAVE CAL BAY
This transfers the bay level calibration figures to non-volatile SCU memory.
236
31st Jul 01
GSM-100-423

1. 2. 3. Connect the output of the signal generator to RX3A. Set the signal generator to the first channel test frequency shown in Table 2-2 or Table 2-3. At the SCP prompt type: TS A ANT 3 4. At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 2-2 or Table 2-3.
5.
At the SCP prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM
6. 7.
Repeat steps 4 and 5 for each signal generator test frequency in Table 2-2 or Table 2-3. At the SCP prompt type: SAVE CAL BAY
This transfers the bay level calibration figures to non-volatile SCU memory.
Branch completion
The BAYDONE command completes the procedure for a branch, by setting a flag to indicate the calibration figures are correct. Proceed as follows: 1. At the SCP prompt type: BAYDONE @1
Branch 2
Repeat the procedures Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A for branch 2 by using connectors RX1B, RX2B and RX3B respectively at the top of the cabinet. Enter @2 instead of @1 in the CAL BAY and BAYDONE commands.

31st Jul 01
68P02901W43-J
237
GSM-100-423
Checking calibration
1. To check that the bay level offset values have been stored in EPROM, use the read command with the required offset table location as an argument. The read command locations are shown in Table 2-4 and Table 2-5, for example: R F:153B6 153C5 in the case of an SCU900
As the SCU is used only in BTS cabinets, covering the GSM range, only the 16 locations per antenna per branch are relevant, as shown in Table 2-4. Table 2-4 SCU900 frequency offset addresses Antenna RX1A Antenna 1 Branch 1 RX2A Antenna 2 Branch 1 RX3A Antenna 3 Branch 1 RX1B Antenna 1 Branch 2 RX2B Antenna 2 Branch 2 RX3B Antenna 3 Branch 2 Locations F: 15386 15395 F: 153B6 153C5 F: 153E6 153F5 F: 15416 15425 F: 15446 15455 F: 15476 15485
The read command allows a maximum of 16 locations to be read at one time. For DCS1800, SCUs thus require using the read command three times per antenna per branch, as shown in Table 2-5. Table 2-5 DCS1800 frequency offset addresses Antenna First read RX1A Antenna 1 (A) RX2A Antenna 2 (A) RX3A Antenna 3 (A) RX1B Antenna 1 (B) RX2B Antenna 2 (B) RX3B Antenna 3 (B) 2. F: 15380 1538F F: 153B0 153BF F: 153E0 153EF F: 15410 1541F F: 15440 1544F F: 15470 1547F Locations Second read F: 15390 1539F F: 153C0 153CF F: 153F0 153FF F: 15420 1542F F: 15450 1545F F: 15480 1548F Third read F: 153A0 153AE F: 153D0 153DE F: 15400 1540E F: 15430 1543E F: 15460 1546E F: 15490 1549E
If the bay level calibration is successful, each appropriate table location will contain valid offsets and not the factory default of 80. The presence of 80 will result in error DRI 218 being reported when the unit is unlocked. NOTE Any value other than 80 is a valid offset, from 81 to FF, and 00 to 7F. Only the value 80 requires investigation.
3.
if the value 80 is present, it indicates that the bay level calibration was unsuccessful, and that it will need to be repeated after checking the configuration and RF cables. If the radio is suspected to be faulty, see next section Diagnostic check of the SCU. Installation & Configuration: BSS Optimization 68P02901W43-J
4.
238
31st Jul 01
GSM-100-423
Diagnostic check of the SCU

If it is suspected that a bay level calibration problem is caused by the SCU, then a diagnostic check can be made by performing a bay level calibration on the SCU alone. Proceed as follows: 1. Set the signal generator to 55 dBm plus lead loss. This will simulate a gain of 10 dB. 2. Connect directly to branch 1 or 2 on the SCU. CAUTION Ensure a TCU is switched to SCU mode before connection to RX2. In TCU mode the RX2 inner is at +12 V dc to power the DLNB in M-Cell equipment. A signal source may be damaged by taking +12 V dc in its RF output. 3. 4. Follow the bay level calibration procedure for each branch, Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A. Check the diagnostic offset values are within the range 97 (lower) and D3 (upper). NOTE The range 97 D3 used in step 4 applies to SCU diagnostic checks only, and should not be compared with the bay level calibration figures. If the values are correct, then the SCU is working correctly and any fault will probably be in the cabinet front end cables, cable connections or preselector modules. If the offsets are outside this range, the SCU is faulty and should be returned.
Restoration
After the bay level calibration procedure is completed, restore the site by the following: 1. 2. 3. 4. Remove the signal generator and dummy load and refit the site RF cables. Remove the 9-way to 9-way cable from the CNTRL PRSCR port on the SCU. Connect the 9-way to 25-way cable from the PC serial A port to a GPROC/GPROC2 TTY port. Press the reset button on the front panel of the SCU and type:. unlock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
BUSY
The SCU is now in the UNLOCKED 5.
state.
Remove the 9-way to 25-way cable from the GPROC/GPROC2 TTY port.

31st Jul 01
68P02901W43-J
239
Checking the database for devices and functions
GSM-100-423

Introduction
Follow this procedure to check which devices and functions are contained in the BSC/BTS database.
Test equipment
The following test equipment is required to carry out the procedure: S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9 to 25-way cable.
Commands
The following commands must be used to carry out the procedure: Command disp_site disp_equipment Function Displays the site number. Displays the active equipment at a specified site.
Procedure
To check the database for devices and functions: 1. 2. 3. 4. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a GPROC/GPROC2 TTY port using the 9 to 25-way cable. At the PC start the terminal emulator program. At the CUST MMI prompt type: disp_site The following message (from the GPROC/GPROC2) is displayed:
current site is #
where # = the number of the site logged into.
240
31st Jul 01
GSM-100-423
5.
Type: disp_equipment #
A complete list of the equipment and functions in the database is displayed, for example:
GPROC 0 0 0 GPROC 1 0 0 BSP DRI DRI MSI MMS MMS MTL OML GCLK KSW CAGE CAB SITE BTF RTF RTF RTF RTF RTF 0 0 0 0 0 0 0 1 0 1 0 0 1 0 0 1 1 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 2 0 0 3 0 0 0 1 0
6.
To check the MSI configuration type: disp_equipment 0 MSI 1 0 0 A message similar to the following example is displayed:
MSI identifier Cage number Slot number MSI type 1 0 16 0 (0 = MSI and 1 = XCDR)

31st Jul 01
68P02901W43-J
241
Checking the E1/T1 link
GSM-100-423

Introduction
Follow this procedure to verify the integrity of the E1/T1 links to the BSC/MSC.
Test equipment
The following test equipment is required: S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 25-way cable.
Command
The following command must be used to carry out the procedure: Command state Function Displays the status of specified devices or functions.
Procedure
To check the E1/T1 link: 1. 2. 3. 4. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a GPROC TTY port using the 9-way to 25-way cable. At the PC start the terminal emulator program. Contact the end point of the E1/T1 link to be tested (BSC/MSC) and request a loopback on the relevant distribution frame (DDF) port. NOTE Repeat for all MSIs and E1/T1 links. If the E1/T1 link has not been installed, perform this test at the digital distribution frame (DDF) in the site, or at the top of the cabinet if no DDF is fitted. 5. Determine the site number, equipment list and MMS configuration.
242
31st Jul 01
GSM-100-423
6.
At the CUST MMI prompt type: state <site #> MMS <MMS #> For example: state 0 MMS 1 0 0 The following message (from the GPROC) is displayed:
Status Information Administration state : Unlocked Operational state : Busy Reason code is : 0 Time of last transition : Wed Jan 5 01:43:13 1994 Other identification : 255 255 255 255 End of status report
If this display shows Unlocked and Busy, then the MSI port (MMS) T43 cabling and the E1/T1 link are all good. If the loop is removed and the command reentered, the result is Unlocked and Disabled. NOTE The MSI requires at least 20 seconds to register a change in status after these commands are entered. If the display continues to show Unlocked and Busy, this may be because: 1. The wrong connection is looped, if the cabling is direct. 2. The MMS may be terminated by a device generating a 2.048 Mbit/s link.

31st Jul 01
68P02901W43-J
243
Verifying PIX connections
GSM-100-423

Introduction
Follow this procedure to verify the PIX connections. This test can be carried out at a live site.
Test equipment
The following test equipment is required: S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 25-way cable. PIX test plugs A, B, and C.
Commands
The following command must be used to carry out the procedure: Command enable_alarm Function Enables alarm reporting for a specified site.
Procedure
Use the following procedure to verify PIX connections:
Preparation
1. 2. 3. 4. Ensure download has been completed. Connect the serial A port on the PC to the master GPROC/GPROC2 using the 9-way to 25-way cable. At the PC start the terminal emulator program. At the CUST MMI prompt enter the password.
Checking PIX connections

1. At the PC, type: enable_alarm # where # = site number. The system will respond with:
SITE ENABLE ALARM STATUS
Site enabled
2. 3.
Connect the PIX test plug C to the appropriate socket on top of the rack. All eight alarms are displayed. NOTE The states in this step depend on the database settings; whether a fault condition is indicated by closed loop or an open loop.
244
31st Jul 01
GSM-100-423
Site restoration
1. 2. Remove the test plug. The alarm display clears. NOTE The states in this step depend on the database settings; whether a fault condition is indicated by closed loop or an open loop.

31st Jul 01
68P02901W43-J
245
Integrating the transcoder
GSM-100-423

Introduction
Follow this procedure to ensure that all allocated Circuit Identification Codes (CICs) are carrying good quality voice traffic. NOTE Transcoders may be in the form of XCDR boards, or an enhanced version utilising a Generic Digital Signal Processor Board (GDP). If GDPs are used in XCDR slots as XCDRs, the procedure is the same as for XCDRs, except where stated.
Test equipment
The following test equipment is required: S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to- 25-way cable. A GSM mobile with a registered SIM card.
Commands
The following commands are required to carry out this procedure: Command disp_mms_ts_usage disp_channel fil_list fil_create fil_start fil_stop fil_delete Function Displays the timeslot usage on an MMS span. Displays the BSCMSC connectivity. Lists active filters. Creates a filter. Starts a filter. Stops a filter. Deletes filters.
246
31st Jul 01
GSM-100-423
Procedure
Before starting the transcoder integration procedure, consult the site specific documentation to determine the BSC/RXCDR configuration and cage slot allocation (conventionally, timeslots 00 and 16 on XCDR boards are not allocated to voice/traffic channels). Proceed as follows:
Displaying MMS timeslot usage

1. 2. At the operations and maintenance centre (OMC-R) man-machine interface (MMI), log in to the required base site controller (BSC). To display the circuit mapping, type: disp_mms_ts_usage X Y Z Where: X Y Z The following header message is displayed:
Start of Report: Site: X MMS: Y Z TS Usage Device ID Type Site CIC Group Group CIC State RTF State RTF TS TS
is: location 1st digit of MMS identifier 2nd digit of MMS identifier
Under each heading, information relevent to the site and MMS port will be displayed. 3. 4. Repeat step 2 for all MMSs. Log out from the BSC.
Displaying BSC-MSC connectivity

1. 2. Log on to the required RXCDR. To display all CEPT nailed connections, type: disp_channel The following message is an example response:
Incoming MMS id 6 1, timeslot: 2 group : 3 Outgoing MMS id 24 0, timeslot: 1 Incoming MMS id 6 1, timeslot: 2 group : 2 Outgoing MMS id 24 0, timeslot: 2 Incoming MMS id 6 1, timeslot: 2 group : 1 Outgoing MMS id 24 0, timeslot: 3 Incoming MMS id 6 1, timeslot: 2 group : 0 Outgoing MMS id 24 0, timeslot: 4 Incoming MMS id 6 1, timeslot: 3 group : 3 Outgoing MMS id 24 0, timeslot: 5 Incoming MMS id 6 1, timeslot: 3 group : 2 Outgoing MMS id 24 0, timeslot: 6 Incoming MMS id 6 1, timeslot: 3 group : 1 Outgoing MMS id 24 0, timeslot: 7 Incoming MMS id 6 1, timeslot: 3 group : 0 Outgoing MMS id 24 0, timeslot: 8

31st Jul 01
68P02901W43-J
247
GSM-100-423
3.
The information in the messages displayed in steps 2 and 2, together with BSC/RXCDR site documentation,contain the CIC mapping. Two examples are:
Circuit ID = 3 Group Number = 1 Timeslot Number = 2
Incoming MMS id 6 1, timeslot: 2 group : 1 Outgoing MMS id 24 0, timeslot: 3 Circuit ID = 91 Group Number = 2 Timeslot Number = 24
Incoming MMS id 6 1, timeslot: 24 group : 2 Outgoing MMS id 24 0, timeslot: 3
CIC test
1. 2. Log on to the required BSC. At the RAM EMON prompt type: fil list If any filters are shown delete them using the fil delete command. 3. Remotely log in to the GPROC running the LCF that supports the site under test using the rlogin command. Determine this using the disp_p <site number> command at the BSP. At the RAM EMON prompt type: fil create tag 10501h
4.
Filter 10501h is created.

A response will be returned with a filter id. 5. At the prompt type: fil start *
Filter * is started.
Where: 6. * is: filter id
Set up a mobile to land or land to mobile call and monitor the filter output. The following message is displayed:
FILTER: SRC: pid: 10 mbid: 0002 cpu: 0119 subsys: 01 tag: 00010501 len:0014 DEST: function: 0009 instance: 001b mbid: 0003 TIME: 96942.975s data:00.7b.60.00.0f.00.0d.01.0b.03.01.08.01.07.02.06.00.06.01.00.05
The last two bytes of the data displayed (in hexadecimal) indicate the CIC in use. Check the quality of the call and, if good, check off the CIC number on the checklist on the next page. If the quality is bad, note the CIC number and retest. The last two bytes in the example show a call on CIC 05 (hexadecimal). Repeat this step until all CICs have been tested. 7. At the RAM EMON prompt type: fil stop *
Filter * is stopped.
Where: * is: filter id
248
31st Jul 01
GSM-100-423
8.
At the RAM EMON prompt type: fil delete *
Filter * is deleted.
Where: 9. * is: filter id
At the RAM EMON prompt type: fil list If any filters are shown delete them using the fil delete command.
10. 11.
Log out of the BSC. Report the result of the integration and any anomalies to the OMC-R operator.

31st Jul 01
68P02901W43-J
249
GSM-100-423
CIC checklist
Check off good quality calls on the CIC checklist:
Slot no. 00 01 00 02 00 03 00 04 00 05 00 06 00 07 00 08 00 09
Slot no. 00 21 00 22 00 23 00 24 00 25 00 26 00 27 00 28 00 29
Slot no. 00 41 00 42 00 43 00 44 00 45 00 46 00 47 00 48 00 49
Slot no. 00 61 00 62 00 63 00 64 00 65 00 66 00 67 00 68 00 69
Slot no. 00 81 00 82 00 83 00 84 00 85 00 86 00 87 00 88 00 89
Slot no.
Slot no.
Slot no.
Slot no.
Slot no. 01 21 01 22 01 23 01 24 01 25 01 26 01 27 01 28 01 29
00 A1 00 C1 00 E1 01 01 00 A2 00 C2 00 E2 01 02 00 A3 00 C3 00 E3 01 03 00 A4 00 C4 00 E4 01 04 00 A5 00 C5 00 E5 01 05 00 A6 00 C6 00 E6 01 06 00 A7 00 C7 00 E7 01 07 00 A8 00 C8 00 E8 01 08 00 A9 00 C9 00 E9 01 09
00 0A 00 2A 00 4A 00 6A 00 8A 00 AA 00 CA 00 EA 01 0A 01 2A 00 0B 00 2B 00 4B 00 6B 00 8B 00 AB 00 CB 00 EB 01 0B 01 2B 00 0C 00 2C 00 4C 00 6C 00 8C 00 AC 00 CC 00 EC 01 0C 01 2C 00 0D 00 2D 00 4D 00 6D 00 8D 00 AD 00 CD 00 ED 01 0D 01 2D 00 0E 00 2E 00 4E 00 6E 00 8E 00 AE 00 CE 00 EE 01 0E 01 2E 00 0F 00 11 00 12 00 13 00 14 00 15 00 16 00 17 00 18 00 19 00 2F 00 31 00 32 00 33 00 34 00 35 00 36 00 37 00 38 00 39 00 4F 00 51 00 52 00 53 00 54 00 55 00 56 00 57 00 58 00 59 00 6F 00 71 00 72 00 73 00 74 00 75 00 76 00 77 00 78 00 79 00 8F 00 91 00 92 00 93 00 94 00 95 00 96 00 97 00 98 00 99 00 AF 00 CF 00 EF 01 0F 00 B1 00 D1 00 F1 00 B2 00 D2 00 F2 00 B3 00 D3 00 F3 00 B4 00 D4 00 F4 00 B5 00 D5 00 F5 00 B6 00 D6 00 F6 00 B7 00 D7 00 F7 00 B8 00 D8 00 F8 00 B9 00 D9 00 F9 01 11 01 12 01 13 01 14 01 15 01 16 01 17 01 18 01 19 01 2F 01 31 01 32 01 33 01 34 01 35 01 36 01 37 01 38 01 39
00 1A 00 3A 00 5A 00 7A 00 9A 00 BA 00 DA 00 FA 01 1A 01 3A 00 1B 00 3B 00 5B 00 7B 00 9B 00 BB 00 DB 00 FB 01 1B 01 3B 00 1C 00 3C 00 5C 00 7C 00 9C 00 BC 00 DC 00 FC 01 1C 01 3C 00 1D 00 3D 00 5D 00 7D 00 9D 00 BD 00 DD 00 FD 01 1D 01 3D 00 1E 00 3E 00 5E 00 7E 00 9E 00 BE 00 DE 00 FE 01 1E 01 3E 00 1F 00 3F 00 5F 00 7F 00 9F 00 BF 00 DF 00 FF 01 1F 01 3F
250
31st Jul 01
GSM-100-423
Calibrating the GCLK

Introduction
Follow this procedure to calibrate the GCLK in the field. The GCLK must be calibrated when either of the following occur: S S S More than one frame slip per hour is observed at the OMC-R. The GCLK calibration request alarm is observed at the OMC-R. The GCLK cannot phase lock, and the LTA values are near their limits. CAUTION The GCLK must be calibrated only by fully trained GSM qualified staff. Do not attempt this procedure under any circumstances unless the test equipment listed below is available.
Test equipment
The following test equipment is required: S S S S S S S An IBM-compatible personal computer (PC). A 9-way to 25-way cable. A rubidium clock standard with 1 or 10 MHz output frequency. Universal counter Hewlett Packard Model HP5385A or equivalent. Screened coaxial cable BNC to 2 mm multicontact AG connector. New calibration sticker(s). A non-ferrous tuning tool.
Commands
The following commands must be used to calibrate the GCLK: Command disp_equipment state disp_element phase_lock_gclk <location> chg_element phase_lock_gclk <flag> <location> clear_gclk_avgs <location> Function Displays the active equipment at a specified site. Displays the status of specified devices or functions. Shows the status of the phase lock function. <location> is the site id. Turns the phase lock function on or off, where <flag> is 0 for off and 1 for on, and <location> is the site id. Clears LTA values in memory for a specified GCLK.

31st Jul 01
68P02901W43-J
251
GSM-100-423
Procedure
Before attempting this procedure, record the board serial number, date of last calibration and present frequency on the calibration record shown at the end of this section. Remove the old calibration stickers from the GCLK front panels. Before starting the procedure, consult the site specific documentation to determine the BSC/BTS configuration and cage slot allocation. NOTE Prior to carrying out the following calibration procedure, allow a 30 minute warm-up period after switching on the GCLK to enable it to reach its operating temperature. Proceed as follows:
Preparation
1. 2. 3. 4. 5. 6. Log in to the required BSC, either at the BSC or via the OMC-R. Go to step 5 if all commands are to be made at the OMC-R MMI. Connect the serial A port on the PC to a GPROC/GPROC2 TTY port using the 9 to 25-way cable. Start the terminal emulator program at the PC. Connect the output from the 10 MHz standard to the reference input of the frequency counter and select external standard. Set the frequency gate time to 10 seconds and set the display to give 10 significant digits.
Clearing GCLK LTA values

1. Check to see if phase lock is on. At the OMC-R/BSC CUST MMI prompt type: disp_element phase_lock_gclk <location> Where: <location> is: 0 or bsc
This gives the status of phase lock at the site. 0 is shown for phase lock off and 1 is shown for phase lock on. 2. If phase lock is on, type: chg_element phase_lock_gclk 0 <location> This turns off the phase lock to the selected site. 3. Then type: disp_equipment <location> This gives the device id of the GCLKs. 4. Then type: state <location> GCLK <dev id> <dev id> <dev id> This displays the status for the GCLK. Installation & Configuration: BSS Optimization 68P02901W43-J
252
31st Jul 01
GSM-100-423
5.
Then type: clear_gclk_avgs <location> The system will respond with:

Enter the gclk_id:
Type in 0 or 1. This clears the LTA values for the specified GCLK.
Adjusting the GCLK frequency

1. 2. 3. Connect the frequency counter to the front panel 16.384 MHz connection of the GCLK. Connect the cable to the input port of the frequency counter and the jack plug end to the front panel of the GCLK 16.384 MHz output and ground respectively. Using a non-ferrous tuning tool, adjust the potentiometer labelled FREQ ADJUST on the GCLK to 16.384 MHz. The GSM specified tolerance is +/ 0.8 Hz, although it is desirable (and should be possible) to adjust the frequency more accurately than this. This reads as 16.384 000 00 on the frequency counter. Adjusting the potentiometer clockwise increases the frequency and anticlockwise decreases the frequency. To carry out calibration on the redundant GCLK repeat from step 3 in Clearing GCLK LTA values to step 3 in Adjusting the GCLK frequency. 4. If phase locking of the GCLK(s) at the site is required, type the following command: chg_element phase_lock_gclk 1 <location> This turns the phase lock on for the specified site. 5. Place a new calibration sticker, indicating the date of calibration, over the potentiometer labelled FREQ ADJUST on each calibrated GCLK.

31st Jul 01
68P02901W43-J
253
GSM-100-423
GCLK calibration record form

The GCLK calibration record form is shown below:
SITE NAME ........................................ SITE ID .............................................. TESTERS NAMES ..................................... .....................................
SERIAL NUMBER OF BOARD
DATE
DATE OF LAST CALIBRATION
FREQUENCY BEFORE CALIBRATION
254
31st Jul 01
GSM-100-423
Verifying ExCell alarms

Introduction
Follow these procedures to verify that the ExCell alarms function correctly.
Test equipment
The following test equipment is required to carry out the serial and alarm tests: S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 25-way cable. An approved smoke canister. Krone tool.
Commands
The following commands must be used to carry out the ExCell alarm tests: Command enable_alarm state Function Enables alarm reporting for a specified site. Displays the status of specified devices or functions.
Initial procedure
To verify ExCell alarms: 1. 2. 3. 4. 5. Ensure download has been completed. Connect the serial A port on the PC to the master GPROC/GPROC2 using the 9-way to 25-way cable. At the PC start the terminal emulator program. At the CUST MMI prompt enter the password. At the PC, type: enable_alarm 0 6. Check that PIX 0 is unlocked and busy. At the prompt, type: state 0 EAS 000 7. Check that PIX 1 is unlocked and busy. At the prompt, type: state 0 EAS 100

31st Jul 01
68P02901W43-J
255
GSM-100-423
The alarms
The following ExCell alarms are tested: S S S S S S S S S S S S S S S Smoke alarm. Overtemperature alarm. Door open alarm. Fan fail alarm. Mains fail alarm. Rectifier fail alarm. Low dc voltage alarm. Inverter fail alarm. Miniature circuit breaker trip alarm. Battery fault alarm. Comms PSU fail alarm. External alarm 0. External alarm 1. External alarm 2. External alarm 3.
Smoke alarm
To verify the ExCell smoke alarm: 1. Ensure that both the smoke sensors are not set (the red LED on each sensor is not lit). If one or both LEDs are lit, switch the cabinet control circuit breaker off then on again to reset the sensors. As directed by the instructions on the smoke canister, direct a jet of smoke at both sensors. When both sensors are active the following message is displayed:
EAS ALARM: 20 0 0 0:40:Optocoupler 1 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Smoke Alarm
2.
3.
Switch the cabinet control circuit breaker off then on again to reset the sensors. The following message is displayed:
EAS ALARM: 20 0 0 0:40:Optocoupler 1 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Clear Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO:
256
31st Jul 01
GSM-100-423
Overtemperature alarm
To verify the ExCell overtemperature alarm: 1. 2. Press the control override button. The heat management system (HMS) display should show a temperature of about 25 _C. Adjust the Adjust Test Temp control until the HMS display shows a temperature between 65 _C and 67 _C. The overtemperature sensor lamp should light and the following message should be displayed:
EAS ALARM: 20 0 0 0:41:Optocoupler 2 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Over Temperature
3.
Adjust the Adjust Test Temp control until the HMS display shows a temperature below 60 _C. The overtemperature sensor lamp should light and the following message should be displayed:
Door open alarm

To verify the ExCell door open alarm: 1. Close the cabinet doors. The following message should be displayed:
2.
Open any cabinet door. The following message should be displayed:

EAS ALARM: 20 0 0 0:42:Optocoupler 3 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Cabinet Door Open

31st Jul 01
68P02901W43-J
257
GSM-100-423
Fan fail alarm

To verify the ExCell fan fail alarm: 1. Switch off any of the RCU or BSC fans. The following message should be displayed:
EAS ALARM: 20 0 0 0:43:Optocoupler 4 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Fan Failure
2.
Switch the fan on again. The following message should be displayed:

Mains fail alarm

NOTE This alarm is active when the ac mains input to all the rectifiers is interrupted, with mains input to just one rectifier the alarm will remain inactive. To verify the ExCell mains fail alarm: 1. Switch off the mains supply to all rectifiers. The following message should be displayed:
EAS ALARM: 20 0 0 0:40:Optocoupler 1 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Mains Failure
2.
Reconnect the mains supply to all rectifiers. The following message should be displayed:
258
31st Jul 01
GSM-100-423
Rectifier fail alarm

NOTE This alarm is active when the ac mains input to a rectifier is interrupted. To verify the ExCell rectifier fail alarm: 1. Switch off the mains supply to rectifier 1. The following message should be displayed:
EAS ALARM: 20 0 0 0:41:Optocoupler 2 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Rectifier Failure
2.
Reconnect the mains suply to all rectifiers. The following message should be displayed:
Low dc voltage alarm

To verify the ExCell low dc voltage alarm: 1. Remove the alarms fuse on the PSU meter panel. The following message should be displayed:
EAS ALARM: 20 0 0 0:42:Optocoupler 3 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Low dc voltage
2.
Replace the fuse. The following message should be displayed:


31st Jul 01
68P02901W43-J
259
GSM-100-423
Inverter fail alarm

NOTE Carry out this test only if an inverter is fitted. To verify the ExCell inverter fail alarm: 1. Switch off the mains supply to the inverter. The following message should be displayed:
EAS ALARM: 20 0 0 0:43:Optocoupler 4 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Inverter Fail
2.
Reconnect the mains suply to the inverter. The following message should be displayed:
MCB trip alarm

To verify the ExCell miniature circuit breaker (MCB) trip alarm: 1. Manually trip any MCB associated with the PSU. The following message should be displayed:
EAS ALARM: 20 0 0 0:44:Optocoupler 5 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: MCB Tripped
2.
Reset the MCB. The following message should be displayed:

260
31st Jul 01
GSM-100-423
Battery fault alarm

To verify the ExCell battery fault alarm: 1. Remove any fuse from the front of the battery box. The following message should be displayed:
EAS ALARM: 20 0 0 0:45:Optocoupler 6 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Battery Fault
2.
Replace the fuse. The following message should be displayed:

Comms PSU fail alarm

To verify the ExCell comms PSU fail alarm: 1. Manually trip the MCB supplying the comms PSU module. The following message should be displayed:
EAS ALARM: 20 0 0 0:46:Optocoupler 7 SITE: 0 CAGE: 0 SLOT: 17 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: Comms. PSU Failure
2.
Reset the MCB. The following message should be displayed:


31st Jul 01
68P02901W43-J
261
GSM-100-423
External alarm 0
To vertify the ExCell external alarm 0: 1. Insert a Krone tool into position 1 of the top Krone connector. The following message should be displayed:
EAS ALARM: 20 0 0 0:44:Optocoupler 5 SITE: 0 CAGE: 0 SLOT: 16 FUNC: N/A Severity: Critical Category: Environment Date Alarm Type: Fault Management Initiated Clear ADDITIONAL INFO: External Alarm #0
2.
Remove the Krone tool. The following message should be displayed:

External alarm 1
To verify the ExCell external alarm 1: 1. Insert a Krone tool into position 2 of the top Krone connector. The following message should be displayed:
2.

262
31st Jul 01
GSM-100-423
External alarm 2
2.

External alarm 3
2.


31st Jul 01
68P02901W43-J
263
Identifying DRCU faults on site
GSM-100-423

Introduction
Follow these procedures to identify DRCU module faults without returning the unit to Motorola. These procedures are also available as a quick reference card (catalogue number 68P02900W39). Refer to the Test equipment, leads and plugs section earlier in this chapter for recommended test equipment.
Symptoms during normal operation

Go to the indicated procedure step for the following symptoms: For this symptom ... If the codes and instances are incorrect on the local maintenance terminal (LMT) If the DRCU goes to sleep If only the DRCU goes to sleep and the alarm LED lights briefly If code loads CEB/DCB/RCB/SCB, EQ, or PA fail If the DRCU resets If a DRI alarm indicates a DRCU failure If there are bad timeslots or if reception quality is poor Go to step ... P1 P2 P3 P3 P4 P4 P5
Symptoms during commissioning

Go to the indicated procedure step for the following symptoms: For this symptom ... If the transmitter output is high or low If the transmitter output is zero If the transmitter output is unchangeable If, after bay level calibration, some or all channels read 80H If, after bay level calibration, some or all channels marginal Go to step ... C1 C1 C2 C3 C4
264
31st Jul 01
GSM-100-423
Procedure during normal operation

To identify DRCU module faults during normal operation: Step P1 Action Lock the DRI. Check DRIX and fibre optic cable by substitution. Refit DRIX and fibre optic cable. Recheck the codes and instances on the LMT. If they are correct, continue. If they are not correct. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P2 Lock the DRI. Remove the fibre optic cables from the DRCU. Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. Manually reset the DRCU using the reset button. Check that the calibration checksums and operational code versions are correct. If they are not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are correct continue. Refit the fibre optic cables. Unlock the DRI. If the DRCU goes into or remains in sleep mode . . . . . . . If not continue. Run the failed test again. If the DRCU passes this time, continue. If not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C6 C6 C6 Go to step
C6

31st Jul 01
68P02901W43-J
265
GSM-100-423
Step P3
Action Lock the DRI. Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. Unlock the DRI and verify that the DRCU reset sequence is performed. Wait until the CEB/DCB/RCB/SCB> prompt has been displayed twice. At the PC enter the third level password. At the PC type the command ALARM_ALL. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If not allow the system to complete its configuration of the DRCU. If alarms are displayed If not continue. Lock the DRI. Manually reset the DRCU using the reset button. Check that the calibration checksums and operational code versions are correct. If they are not correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are correct continue. At the PC type: First level password Second level password SWAP C 0 EXEC C 0 Third level password SWAP E A SWAP P 0 EXEC P 0 TEST In test mode, watch the display for any alarms that might be generated. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are not, at the PC type ALARM_ALL. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If not, continue .............................
Go to step
C6
C6
C6
C6 C6
266
31st Jul 01
GSM-100-423
Step P4
Action Lock the DRI. Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. Manually reset the DRCU using the reset button. Check that the calibration checksums and operational code versions are correct. If they are not correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are correct continue. At the PC type: First level password Second level password SWAP C 0 EXEC C 0 Third level password SWAP E A SWAP P 0 EXEC P 0 TEST In test mode, watch the display for any alarms that might be generated. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are not, at the PC type ALARM_ALL. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If not continue.
Go to step
C6
C6 C6
P5
Lock the DRI. Carry out the bay level and cell site offset calibration again. If the calibration cannot be carried out . . . . . . . . . . . . . . . . If the calibrations can be carried out continue. Check the DRIM, DRIX, and fibre optic cables by substitution. Check the BSS code load is the latest version. If necessary, contact the Motorola local office to see if any FYI or CSB covers a similar failure . . . . . . . . . . . . . . . P7 C1 C4 P6
P6
Which calibration routine failed? If the transmitter power calibration is incorrect . . . . . . . . . If the bay level calibration is incorrect . . . . . . . . . . . . . . . . . Run the failed test again. If the DRCU passes continue. If not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P7
C6

31st Jul 01
68P02901W43-J
267
GSM-100-423
Procedure during commissioning

To identify DRCU module faults during commissioning: Step C1 Action Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. At the PC type the command ALARM_ALL. If alarms are displayed ............................. C6 If not continue. Remove power from the DRCU. Connect the combination of a 50 W dummy load and hybrid combiner through a power meter to the output of the PA module (make a note of all the losses). Apply power to the DRCU. At the PC type: First level password Second level password SWAP C 0 EXEC C 0 Third level password SWAP E A SWAP P 0 EXEC P 0 TEST In test mode watch the display for any alarms that might be generated. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are not, at the PC type ALARM_ALL. If alarms are displayed If not, at PC type: ACTIV P 0 TS A TX 0 Check the reading on the power meter (bearing in mind the losses noted above) is within the limits 48.5 to 60.5 W (46.85 to 47.85 dBm). If the power is within limits, the problem probably lies between the DRCU output connector and the top of the cabinet. If the power is not within limits . . . . . . . . . . . . . . . . . . . . . . . C6 ............................. C6 C6 Go to step
268
31st Jul 01
GSM-100-423
Step C2
Action Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. Manually reset the DRCU using the reset button. Check that the calibration checksums and code versions are correct. If they are not correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are correct continue. Check that the PA operation code is version PA_0040.BIN or later. If the code is correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If the code is not correct continue. Connect a 9 to 25-way cable from a second PC serial port A to the DRCU TTY port. Start the terminal emulator program. Unlock the DRI (PC2) and verify that the DRCU reset sequence is performed (PC1). Wait until the CEB/DCB/RCB/SCB> prompt has been displayed twice. At the PC enter the third level password. At the PC type the command ALARM_ALL. If alarms are displayed If not continue. At the prompt type: FM TEST HALT P 0 (The next two commands must be entered within five seconds of each other.) HALT C 0 TEST Pause briefly to check that the DRCU does not reset. At the prompt type: REVSWAP P U Wait for 50 seconds for code to be swapped from RAM to EEPROM. If the swap was unsuccessful, lock the DRI . . . . . . . . . . . . If the swap was successful continue. Lock the DRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .............................
Go to step
C6
C5
C6
C6 C5

31st Jul 01
68P02901W43-J
269
GSM-100-423
Step C3
Action Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. At the PC type ALARM_ALL. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If not continue. Rerun the bay level procedures for those channels that read 80H. If the channels are correct . . . . . . . . . . . . . . . . . . . . . . . . . . If not continue. At the CEB/DCB/RCB/SCB> prompt type: TS A CHAN Check that the displayed response has TS0 TS7 on the same channel. Use a channel frequency table to check that the signal generator is set up correctly. If the signal generator is not set up correctly . . . . . . . . . . . If the signal generator is set up correctly . . . . . . . . . . . . . .
Go to step
C6
C5
C5 C4
270
31st Jul 01
GSM-100-423
Step C4
Action Connect a 9 to 9-way cable from a PC serial port A to the DRCU TTY port. Start the terminal emulator program. At the PC type ALARM_ALL. If alarms are displayed .............................
Go to step
C6
If not continue. Remove power from the DRCU. Connect a coaxial cable from the signal generator to the DRCU Rx branch 1 input. Calculate the new signal generator output power using the formula: Revised output = splitter/preselector gain + cable loss + nominal generator output Where splitter/preselector gain is taken at 13.3 dBm and nominal generator output is 65.5 dBm. Apply power to the DRCU. Check that the calibration checksums and code versions are correct. If they are not correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are correct continue. At the PC type: First level password Second level password SWAP C 0 EXEC C 0 Third level password SWAP E A SWAP P 0 EXEC P 0 TEST In test mode watch the display for any alarms that might be generated. If alarms are displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If they are not, at the PC type ALARM_ALL. If alarms are displayed ............................. If they are not, rerun the bay level procedures using the revised signal generator output power calculated above (ignore the RX_MATRIX alarm). Repeat the bay level procedures for both branches. If the DRCU passes this time, continue If not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C6 6 C6 C6

31st Jul 01
68P02901W43-J
271
GSM-100-423
Step C5
Action Run the failed test again. If the DRCU passes this time, continue If not . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Go to step
C6
C6
Power the DRCU down in a controlled manner by halting each processor (HALT E A). Record all details of the fault including the procedures used. Return the DRCU for repair.
272
31st Jul 01
Chapter 3
M-Cell2/6 optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 3 M-Cell2/6 optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to M-Cell2/6 optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test lead calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating TCU output power and checking VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell site offsite calibration (Tx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting cellsite power M-Cell6 with CCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B VSWR and cellsite offset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR and cellsite offsite information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal TCU-B VSWR and cellsite power calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal VSWR information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating TCU-B transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B VSWR and cellsite power calibration for CCBs . . . . . . . . . . . . . . . . . . . . . . . . . . . CCB calibration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating M-Cell2/6 TCU900/1800/1900 bay level offset tables . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking radio, dummy load and TCU reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Silencing PLL_LK alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up TCU for Bay Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic check of TCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 32 32 32 33 33 36 36 37 37 38 39 39 310 311 312 313 314 317 319 319 320 320 321 322 322 324 324 325 326 327 329 329 331 335 337 337 337 337 339 340 341 342 349 350 350 351 352 354 355

31st Jul 01
68P02901W43-J
iii
GSM-100-423
Calibrating M-Cell2/6 TCU-B bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for bay level calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch 1 RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX3A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU-B diagnostic check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking serial connections and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the MCU (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to calibrate the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up for calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
356 356 356 357 358 361 365 366 366 367 368 370 371 372 372 372 372 373 373 375 375 375 375 375 376 377 377 377 378 378 378 379 379 379 379 380 381
iv
31st Jul 01
GSM-100-423
Introduction to M-Cell2/6 optimization
Introduction to M-Cell2/6 optimization

This chapter provides information required for the hardware optimization of M-Cell2 and M-Cell6 equipment. Before starting the hardware optimization, the equipment must be commissioned. Hardware optimization of the M-Cell2 and M-Cell6 equipment consists of the following procedures: S S S S S Checking the antenna VSWR and calibrating the transmit output power. Calibrating the bay level offset tables. Checking the database equipage. Checking the 2.048 Mbit link. Checking the serial connections, power supply module version and alarm status. CAUTION The M-Cell2 and M-Cell6 and all associated site equipment must be completely optimized before integrating the base site for operation.

31st Jul 01
68P02901W43-J
31
GSM-100-423

Introduction
This section provides information on the test equipment required for the Hardware Optimization procedures in this chapter. The GSM cellullar field installation tool kits listed in Chapter 1 may also be necessary. CAUTION Ensure that all test equipment associated with commissioning of Motorola cellular base stations is within calibration date.
Test equipment
Table 3-1 provides details of the test equipment required to perform the hardware optimization procedures provided in this chapter: Table 3-1 Hardware optimization equipment Quantity
1
Description IBM compatible 486 DX2 or DX4 portable Personal Computer (PC).
Comments The basic requirements are: S TFT colour screen. S S 170 Mbyte hard drive (minimum). Minimum 4 Mbyte RAM (minimum) or 8 Mbyte (recommended). 3.5 inch floppy drive. Serial port. CD-ROM drive (recommended). PCMCIA (Type 2) compatible slot. Windows 3.1 loaded and running in 386 enhanced mode. Battery power.
S S S S S
S 1
1 1 1 1 2 1 1
Signal generator Commercial terminal emulator software Digital multimeter 30 dB attenuator RF adaptor kit N to 7/16 inch adaptor N to N barrel adaptor
Up to 1 GHz. PC PLUS or similar software. Hewlett Packard E2378A or equivalent. 100 W minimum. RTLXQ98088 or equivalent.
RF wattmeter with 5 W, 10 W 25 W Bird model 43 or equivalent. and 50 W elements
32
31st Jul 01
GSM-100-423
Quantity
1 1
Description 2 metres of N to N male coaxial cable 4 metres of N to N male coaxial cable 9-way to 9-way cable 9-way to 25-way cable (TCU-B only)
Comments Must be calibrated. Must be calibrated. Compatible with PC to TTY port on TCU/MCU. EQCP/RSS cable, connecting PC to TCU-B test interface.
2 1
Test lead calibration

To minimize variations in test results, ensure that all appropriate test leads used in hardware optimization procedures are calibrated. CAUTION A recognized laboratory must calibrate all test equipment and associated test leads annually. Do not calibrate test equipment or test leads in the field.
Test leads
Connections for a TTY test lead
Figure 3-1 shows the possible connections for the test lead used in the hardware optimization procedures:
2 3 5 4 6 7 8
4 m LONG SCREENED CABLE TO PC COMMUNICATIONS PORT 9-WAY D-TYPE F
3 2 5
TO TCU/MCU CONNECTOR 9-WAY D-TYPE M
Figure 3-1 9-way to 9-way cable connections

31st Jul 01
68P02901W43-J
33
GSM-100-423
Connections for a TCU-B test lead

Figure 3-2 shows the possible connections for the test lead (3086240N01: EQCP/RSS cable, TCU-B) used in the TCU-B hardware optimization procedures:
2 3
3 2 6 5
EQCP PINS
RSS PINS
5
SELECTOR SWITCH 4 m SCREENED CABLE 9-WAY D-TYPE F CONNECTOR (TO PC COMMUNICATIONS PORT)
25-WAY D-TYPE M CONNECTOR (TO TCUB TTY INTERFACE PORT)
Connections for a PIX test lead

Table 3-2 shows pin out details to make a PIX test lead: Table 3-2 Test plug pin connections From PIN 1 2 3 4 5 6 7 8 20 21 22 23 24 25 26 27 To PIN
34
31st Jul 01
GSM-100-423
Table 3-2 Test plug pin connections From PIN 9 & 10 not used 11 NOTE When making the PIX test lead: Normally open (N/O) PIX inputs should be connected through a 50 ohm resistor. Normally closed (N/C) PIX inputs should be connected through a 50 kohm resistor. Details of N/O and N/C site inputs can be found in the equip_eas file in the site commissioning database. N/A 29 To PIN
Connections for a GCLK calibration test lead

Figure 3-3 shows the connections for test lead 3086144E01: Cable Assy, MCU Clock Calibration.
PIN NUMBER
3 2 1
Earth Pin 2 not used 8 kHz output 2 m COAXIAL CABLE TYPE RG178
3-WAY CONNECTOR (TO MCU, CAL. PORT)
50 OHM BNC CONNECTOR (TO FREQUENCY COUNTER)
Figure 3-3 3-way to BNC connection

31st Jul 01
68P02901W43-J
35
Calibrating TCU output power and checking VSWR
GSM-100-423

Cell site offsite calibration (Tx only)
The objective of the VSWR check and output power calibration procedure is to ensure that antenna feeders and connectors are properly terminated and then set the pre-defined maximum transmitter output power at the top of the cabinet. When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures. These procedures aim to produce a radio that exhibits a flat frequency response over the GSM band. In the case of the transmitter, this is performed by distributing the channels over three detector groups (the detector being the device that maintains a steady output power level). In the field, the procedure for setting the transmit output power involves using a set of commands called Cell Site Power (CSPWR). During CSPWR the cabinet output power can be trimmed to account for any abnormalities that may occur between the TCU and the top of the cabinet. The offset is effectively subtracted from the requested power level, such that for whatever channel is selected, a steady output is maintained at the top of the cabinet. Two methods for setting output transmit power are described in this section, one automatic and one manual:
Method 1 (automatic)
When the CSPWR command is typed at the SCP prompt, it effectively executes a small script containing the following commands: TS A CHAN 31 TS A CHAN 700 TS A TXP 00 MDLTR UC Set all timeslots to channel 31 (TCU900). Set all timeslots to channel 700 (TCU1800/1900). Set all timeslots to full power. Turn the modulation off.
Prior to executing the CSPWR command, it assumes that the synthesizers are hopping (not locked) as is the case after the unit is powered up for the first time. To alter the power, typing U increments or typing D decrements the power setting byte. On completion, the command is exited and the appropriate power byte is saved to RAM.
Method 2 (manual)
To specify a specific channel (instead of defaulting to channel 31 or 700), two extra commands must be entered prior to executing the CSPWR command, one to set the appropriate channel and the other to lock the synthesizer. By locking the synthesizer, the channel selection made in the CSPWR command will be ignored and the output is maintained at the frequency specified.
36
31st Jul 01
GSM-100-423
Test stages
There are four stages to the procedure: S S S S Preparing for test. Checking the VSWR. Calibrating the transmit output power. Restoring the site.
Test equipment
The following test equipment is required during the VSWR and output power calibration procedure: S S S S S S An IBM compatible personal computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter, or equivalent, with 5 W and 50 W elements. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section). 7/16 N-type adaptor. 50 Ohm/100 W power attenuator. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola cellular base stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
37
GSM-100-423
Commands
The following table lists the commands used during the VSWR and output power calibration procedure: NOTE 1. The 0 used in the commands in this procedure is a zero. 2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands and may be entered in upper or lower case; the rest of the commands in this list are all TCU (emulator) commands and case is as shown. BSS MMI command lock_device unlock_device clear_cal_data TCU emulator command SWAP Function Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis. Function Swaps the code from one memory storage device to another (eg RAM to ROM). It verifies that the source code contains valid code and that the destination is in the proper state. If either of these conditions are not met, an error is flagged. Executes the code currently in RAM (see swap command). XX Timeslot set up. Where: <T> = Timeslot No. or A = ALL XX = ARFCN to tune timeslot to. <nn> Timeslot set up. Where: <T> = Timeslot No. or A = ALL nn = Attenuation level from max. Places the TCU in test mode. Uses one synth for all timeslots. Restore synth to normal working mode. Cell Site Power. Allows the cell site power to be set to the maximum output power. Used with the CSPWR command to increase the power level by a factor of 0.2 dB. Used with the CSPWR command to decrease the power level by a factor of 0.2 dB. Used to exit the CSPWR command and store the resulting offset to RAM. Used to store the resulting offset in ROM. Changes the state of the requested processor from Active Standby to Call processing. Displays the current state of the code for the processor requested.
EXEC TS <T> CHAN
TS <T>
TXPWR
TEST SYNTH 1 SYNTH NRM CSPWR U D ESC (key) SAVE CAL TX ACTIV state
38
31st Jul 01
GSM-100-423
Test all antennas

Repeat the Prepare for test and Procedure 1 or Procedure 2 sequence for all antennas on site, both receive and transmit.
Preparing for test

To prepare for the VSWR check and output power calibration: 1. 2. 3. 4. Connect the 9-way to 9-way cable from the PC serial A port to the MCU MMI port. Start the terminal emulator program at the PC. Enter the password at the CUST/MMI prompt. Enter the command: lock_device # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
WARNING An RF hazard exists during DRI transmissions. As one antenna may be connected to a number of DRIs, the lock command must be repeated for all DRIs on the antenna being worked on before connecting the wattmeter. 5. Type: clear_cal_data # dri A * 0 NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 6. 7. 8. 9. 10. 11. Connect the wattmeter, with the 50 W element in series, with the Tx port at the top of the cabinet and the antenna. In the case of external high power duplexers, connect the wattmeter with 50 W element to the output port of the high power duplexer. Connect the 9-way to 9-way cable from the PC to the CNTRL PRCSR port on the TCU. Press the front panel RESET button to reset the TCU under test. Enter the boot code passwords. Continue with either Procedure 1 or Procedure 2.

31st Jul 01
68P02901W43-J
39
GSM-100-423
Procedure 1 (automatic)
Checking the VSWR
1. 2. Disconnect the antenna and connect a dummy load to the meter. Type the following commands at the SCP prompt: SWAP C 0 EXEC C 0 level_3_password TEST CSPWR 3. 4. 5. 6. Monitor and record the wattmeter reading (the forward output power). Press ESC. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Connect the power meter through to the antenna. WARNING The VSWR check requires full power to be transmitted through the antenna. Ensure all personnel are clear of the antenna. Do not carry out this VSWR test unless the antenna installation is complete.
CAUTION Minimize the time that the radio is powered up To reduce the possibility of interference with other users. 7. 8. Type CSPWR. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 1 W or 5% of forward power. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 9. Press ESC. NOTE The CSPWR command defaults to a midpoint channel number (normally 31 or 700), but if required, a manual process can be performed as shown in Procedure 2. 10. Reconnect antenna. Installation & Configuration: BSS Optimization 68P02901W43-J
310
31st Jul 01
GSM-100-423
Procedure 2 (manual)
Checking the VSWR
1. 2. Disconnect the antenna and connect a dummy load to the meter. Enter the following commands at the SCP prompt: SWAP C 0 EXEC C 0 level_3_password TEST 3. Enter the two following commands: TS A CHAN nnn SYNTH 1 where: A means all timeslots (TS). nnn means the specified channel number. 4. 5. 6. 7. Type CSPWR. Monitor and record the wattmeter reading (the forward output power). Press ESC. Type SYNTH NRM. NOTE Once the SYNTH 1 command has been executed, the CSPWR and ESC commands can be toggled between as many times as required. The channel will still remain on the one originally defined in step 3. Repeat steps 3 through 7 for the required number of channels. 8. 9. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Connect the power meter through to the antenna. WARNING The VSWR check requires full power to be transmitted through the antenna. Ensure all personnel are clear of the antenna. Do not carry out this VSWR test unless the antenna installation is complete. CAUTION Minimize the time that the radio is powered up To reduce the possibility of interference with other users. 10. 11. Type CSPWR. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 1 W or 5% of forward power. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector.

31st Jul 01
68P02901W43-J
311
GSM-100-423
12. 13.
Press ESC. Reconnect the antenna.
Calibrating the transmit output power

1. 2. 3. Disconnect the antenna and connect a dummy load to the meter. Replace the 5W element in the Wattmeter with a 50 W element and connect the meter in the forward direction. Enter the two following commands: TS A CHAN nnn SYNTH 1 Where: A means all timeslots (TS) nnn means the specified channel number. 4. Type CSPWR. The following message is displayed:
Hit U or D until desired max is measured then hit ESC, CTRL-Y or CTRL-C
5.
Enter U or D to achieve the appropriate value in Table 3-3: Table 3-3 Achievable TX RF power output TCU type Twin band pass filter, no duplexer TCU900 40 W (46 dBm) Not applicable Not applicable Achievable value No combining Not applicable 16 W (42.05 dBm) 32 W (45.05 dBm) One stage combining 20 W (43 dBm) 8 W (39.05 dBm) 16 W (42.05 dBm)
TCU1800/1900 High Power TCU1800/1900 All 6.
Or the customer-specified value at the top of the cabinet, taking cable losses into account.
As U or D is typed, a message similar to the following example, indicating the TCU output power and offset value, is displayed:
D P: 43.8 dBm Cell Site Offset: 1 When the required output level is achieved, press ESC
7.
At the SCP prompt, type SAVE CAL TX. NOTE The cell site offset can be checked by reading the memory location: R F:15780
8. 9.
Repeat steps 2 to 7 until all TCUs have been tested. Reconnect the antenna. Installation & Configuration: BSS Optimization 68P02901W43-J
312
31st Jul 01
GSM-100-423
Setting cellsite power M-Cell6 with CCB

The Cavity Combining Block (CCB) combines the output of up to three radios to a common output, and up to six radios by use of an additional CCB (extension). The CCB (extension) output is an input to the CCB (output) for a single-antenna system. Every transmitted frequency is attenuated by approximately 3.5 dB for a six cavity system and 2.7 dB for a three cavity system. The CCB is not available for M-Cell2. NOTE All CCB commands are issued via the TTY port on a TCU. An M-Cell6 can support one or two CCB modules. There is a minimum of one CCB control board. The CCB control board is located at the front of the CCB beneath a screw down cover. If redundancy of the CCB control board is provided, both CCB modules will be equipped with a CCB control board. The CCB has an address which is defined in the database using the equip_device comb command. The address can also be displayed by using the disp_equipment comb command. The CCB control board has a set of eight DIP switches which are used to provide the binary representation of the address defined in the database. If a single CCB control board is used, it must be in position 0, or the right side of the cabinet viewed from the front. If two CCB control boards are used, the one mounted on the right module (looking from the front) will normally be the master. If this unit fails, the redundant unit will automatically assume control. The initial main/standby relationship is defined from the power connection to the top panel of the M-Cell6 cabinet. The two CCB control boards receive power from different pins in the connector, this provides the main/ standby relationship. A fault or problem with the CCB control board is indicated by a red LED, which can be viewed from above. There is not a master/slave relationship as no CCB control board has any influence over the other. It is a main/standby relationship where each CCB control board is equally aware of what is happening with the CCB system, hence the ability for the standby CCB control board to take seamless control in the event of a problem with the main CCB control board. NOTE The CCB control board is sometimes referred to as the Transmit Antenna Transceiver Interface Control Board (TATI Control Board or TCB).

31st Jul 01
68P02901W43-J
313
GSM-100-423
Example:
If the combiner address is required to be 75, the DIP switches are set as in Table 3-4. Table 3-4 Switch settings for example of value 75 Switch On/off for value 75 Binary value of each switch NOTE S S If CCB control board redundancy is supported, the dip switches must be set the same on both CCB control boards. 255 (all on) is not a valid address. 8 off 128 7 on 64 6 off 32 5 off 16 4 on 8 3 off 4 2 on 2 1 on 1
The CCB control board is equipped with a green LED to indicate the presence of power.
Procedure
The following procedure details the necessary steps to perform the setting of the CSPWR on M-Cell6 sites when they are equipped with CCBs.
Setting the CSPWR

The radio on slot 0 can be used to control all the cavities in the CCB. 1. 2. Connect a PC to the TCU TTY port and put the radio into test mode. Issue the full reset command to the CCB. At the SCP prompt, type: SNDCMB 0A 02 <CCB control board address 00FE> <Cavity address> <Checksum> Where: 0A is the reset command. 02 is the byte count. CCB control board address is the address, in hex, set by the CCB control board DIP switches (see Table 3-4). Cavity address is the address, in hex, of the cavity to be reset (see Table 3-5). Checksum is the low byte of the sum of all other values. For example, to perform a reset of cavity 0, on a CCB with address 254 decimal, type: SNDCMB 0A 02 FE 01 0B The response should occur in under 12 seconds and begin with 09. The 09 indicates a reset response. If OK:
09 02 FE 00 0A
If not OK:
09 02 FE FF 08
NOTE The cavities may be tuned individually or as a group from a single command.
314
31st Jul 01
GSM-100-423
3.
The TCU radios use channel 31 as the default value associated with the CSPWR command. If a different channel is required, the following commands should be input with the radio in test mode: TS A CHAN nnn (where nnn represents the channel to use) SYNTH 1 CSPWR.
Tuning CCB cavities

To tune a CCB cavity use the following command: SNDCMB 02 <byte count> <CCB control board address> <cavity address> <Chan No. high byte> <Chan No. low byte> <Pwr_Lvl> <Chksum Lo> Multiple cavities may be tuned in a single command, but the channel spacing between cavities must be 800 kHz or four channels. For example: To tune the first cavity of the CCB with address 254 to channel 120 type: SNDCMB 02 05 FE 01 00 78 00 7E Where: 02 is the parameter download message ID. 05 is the number of bytes to follow. FE is the address 254 in hex. 01 is the cavity. 00 is the channel high byte. 78 is the channel low byte = 120. 00 is the power level always 00. 7E is the lowbyte of the checksum (02 + 05 + FE + 01 + 00 + 78 + 00). The cavities are addressed from a bitmap. The mapping follows the plan in Table 3-5: Table 3-5 Cavity bitmap MSB Bit 7 Bit 6 Bit 5 Bit 4 Cav 4 Bit 3 Cav 3 Bit 2 Cav 2 Bit 1 Cav 1 LSB Bit 0 Cav 0
Reserved Reserved Cav 5
The reserved bits are always set to zero. The channel number has a high and low byte as the CCB has the ability to handle EGSM frequencies. The power level value is always set to zero.

31st Jul 01
68P02901W43-J
315
GSM-100-423
The single command string, used to tune all cavities starting with channel 60 for cavity 0 and incrementing the channel number by 4 for subsequent cavities, and with the CCB having an address of 254, would have the following format: SNDCMB 02 14 FE 3F 00 3C 00 00 40 00 00 44 00 00 48 00 4C 40 00 00 50 00 F7 Where: 02 is the command to tune cavities. 14 is the number of bytes to follow excluding checksum. FE is the CCB control board address. 3F is the cavity bitmap (represents all 6 cavities). 00 is the channel high byte. 3C 40 44 48 4C 50 are the channel numbers low bytes. 00 is the power level per cavity. NOTE The sequence: channel high byte, channel low byte, power level repeats for each cavity until all cavities have been defined. The CCB responds within 7 seconds for a single cavity or within 14 seconds for multiple cavities with the message:
ID 01, parameter download confirm
316
31st Jul 01
GSM-100-423
Restoring the site

After all installed TCUs have been checked and calibrated, perform the following steps to restore the site. This is done in two stages: S S RF output power check. Returning the TCUs to call processing mode.
RF output power check

1. 2. 3. 4. Remove the 9-way to 9-way cable from the CNTRL PRSCR port and connect to the MCU MMI port. Connect a wattmeter fitted with a 50 W element and a dummy load to the TX port of the TCU to be tested. Press the reset button on the TCU front panel. Unlock the DRI under test using the following commands: unlock_device # dri a * 0 state # dri a * 0 Where: # a * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
This returns the TCU to the Unlocked Busy state (confirmed by the state command). 5. Via the MMI, determine whether maximum BTS power output is set on the database by typing: disp_element max_tx_bts X cell_number=a a a b b ccc dd Where: a b c d is: the mobile country code (MCC). the mobile network code (MNC). the location area code (LAC). the cell ID.
Observe the value displayed; zero indicates maximum transmit power. Each step decreases power by 2 dB. 6. Note the RF output reading on the wattmeter; it should be the same as the maximum power set up in step 5 of Calibrating the transmit output power in this section

31st Jul 01
68P02901W43-J
317
GSM-100-423
7.
Lock the TCU by typing: lock_device # dri a * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Repeat steps 2 to 7 for all TCUs.
Returning the TCUs to call processing mode

1. 2. Ensure the TX port of all TCUs tested is reconnected to its correct antenna feeder cable. Unlock all TCUs tested using the command detailed in step 4 of RF output power check. The command is to be entered for each TCU to be unlocked. 3. 4. Remove the 9-way to 9-way cable from the MCU MMI port. Inform the OMC the VSWR and cell site power calibration has been completed.
318
31st Jul 01
GSM-100-423
TCU-B VSWR and cellsite offset information

VSWR and cellsite offsite information
NOTE The TCU-B can only be used with BSS software release 1.5.1.6 onwards. There is no DCS1800/PCS1900 version of TCU-B. The TCU-B cannot be used as an SCU. The objective of the VSWR check and output power calibration procedure is to ensure that antenna feeders and connectors are properly terminated and then set the pre-defined maximum transmitter output power at the top of the cabinet. When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures. These procedures aim to produce a radio that exhibits a flat frequency response over the GSM band. In the case of the transmitter, this is performed by distributing the channels over three detector groups (the detector being the device that maintains a steady output power level). In the field, the procedure for setting the transmit output power involves using a set of commands called Cell Site Power (CSPWR). During CSPWR the user can trim the cabinet output power to account for any abnormalities that may occur between the TCU-B and the top of the cabinet. The offset is effectively subtracted from the requested power level, such that for whatever channel is selected, a steady output is maintained at the top of the cabinet. There are two sets of procedures available for checking VSWR and cell site power: S S Normal TCU-B VSWR and cellsite power calibration. TCU-B VSWR and cellsite power calibration for CCBs.
The Preparing for test procedure at the end of this section should be completed before attempting the VSWR and cellsite power calibration procedures.

31st Jul 01
68P02901W43-J
319
GSM-100-423
Test stages
Test equipment
The following test equipment is required during the VSWR and output power calibration procedure: S S S S S S S An IBM compatible personal computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter, or equivalent, with 5 W and 50 W Elements. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section). 9 to 25-way EQCP/RSS cable. 7/16 N-type adaptor. 50 Ohm/100 W power attenuator. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
320
31st Jul 01
GSM-100-423
Commands
The following table lists the commands for the VSWR and output power calibration procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. BSS MMI commands may be entered in upper or lower case. RSS MMI or TCU-B (emulator) commands must be entered in case as shown. BSS MMI command ins_device lock_device unlock_device clear_cal_data RSS MMI command tcu_clock 0 TCU-B TTY command TEST ACT C BBH ALARM OFF CSPWR HALT C TS <T> CHAN XXX Function Initializes the device, bringing it into service. Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis Function Stops the TCU-B hunting between link A and link B and forces the TCU-B to look only at link A. Function Places the TCU-B in test mode. Activates the Control Processor. Inhibits the BBH alarm. Cell Site Power. Allows the Cell Site power to be set to the maximum output power. Stops the Control Processor. Timeslot set up. Where: <T> = Timeslot No or A = ALL XXX = ARFCN to tune Timeslot to. Timeslot set up. Where: <T> = Timeslot No or A = ALL nn = Attenuation level from max. Used with the CSPWR command to increase the power level by a factor of 0.2dB. Used with the CSPWR command to decrease the power level by a factor of 0.2dB. Used to exit the CSPWR command and store the resulting offset to RAM. Write enables the FLASH EPROM. Used to store the resulting offset in FLASH EPROM. Write protects the FLASH EPROM. Reads Tx offset for FLASH EPROM. Reads Tx offset for RAM. Emulates Combiner Control Processor messaging
TS <T> TXPWR <nn>
U D ESC (key)or CTRL-Y or CTRL-C WRENB SAVE CAL TX WRPTC FR TX MR TX SNDCMB

31st Jul 01
68P02901W43-J
321
GSM-100-423
Test all antennas

VSWR checks ensure correct antenna matching and can prove the serviceability of the antenna. Repeat the procedures for all antennas on site, including receive antennas.
Preparing for test

To prepare for the VSWR check and output power calibration: 1. 2. 3. 4. If CCBs are fitted, set all DIP switches on the CCB control board to zero (this assists programming and checksum calculations). Connect the 9 to 9-way cable from the PC serial A port to MCU TTY port. At the PC start the terminal emulator program. At the MMI-RAM> prompt type: ins_device # dri A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The radio must be brought into service as there is no Flash EPROM storage of code at the radio control processor level. If a connection to the BSC is not available a PCMCIA commissioning card must be used. 5. Wait for the radio to finish initializing, then type lock_device # dri A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
WARNING An RF hazard exists during DRI transmissions. As one antenna may be connected to a number of DRIs, the lock command must be repeated for all DRIs on the antenna being worked on before connecting the wattmeter. NOTE For ease of calibration, all TCU-Bs in a cell should be initialized and then locked. Always lock the transceiver providing the BCCH last, as this prevents the BCCH being switched to alternate transceivers.
322
31st Jul 01
GSM-100-423
6.
Type: clear_cal_data # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 7. 8. Connect port COM1 on the PC to the TTY Interface port on the transceiver using the 9 to 25-way RSS cable. At the MMI-ROM prompt type: tcu_clock 0 9. Remove the 9 to 25-way RSS cable from the transceiver and replace it with the 9 to 25-way EQCP cable.

31st Jul 01
68P02901W43-J
323
Normal TCU-B VSWR and cellsite power calibration
GSM-100-423

Normal VSWR information
Two methods available for normal VSWR checking are described in this section; one automatic and one manual. The reason for the two methods is as follows:
VSWR Method 1 (automatic)

When typing the CSPWR command at the EQCP prompt, it effectively executes a small script containing the following commands: TS A CHAN 31 TS A CHAN 700 TS A TXP 00 MDLTR UC Set all timeslots to channel 31(TCU900 and TCU-B) Set all timeslots to channel 700(TCU1800/1900) Set all timeslots to full power Turn the modulation off
Prior to executing the CSPWR command, it assumes that the synthesizers are in normal mode (not locked), as is the case after the unit is powered up for the first time. NOTE Although embedded in the CSPWR script, the TS a CHAN 700 command is ignored by the TCU-B VSWR calibration procedure.
VSWR Method 2 (manual)

To allow a specific channel to be specified (instead of defaulting to channel 31 or 700) additional commands must be entered, rather than using the CSPWR command. One command sets the appropriate channel and the other switches the TCU-B output power on and off.
324
31st Jul 01
GSM-100-423

The first method for normal VSWR checking uses automatic channel selection. The CSPWR command automatically selects a midpoint channel number (channel 31 or 700), but if required a manual process can be performed as shown in method 2.
Checking the forward output power

To check the transmission path forward output power: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF CSPWR 3. 4. Monitor and record the wattmeter reading (the forward output power). Press ESC or CTRL-Y or CTRL-C.
Checking the reverse power

To check the transmission path reverse power: 1. 2. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up. 3. At the EQCP prompt type: CSPWR 4. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1W. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 5. 6. Press ESC or CTRL-Y or CTRL-C At the EQCP prompt type: HALT C

31st Jul 01
68P02901W43-J
325
GSM-100-423
7.
Remove the power meter and reconnect antenna.

The second method for normal VSWR checking allows the manual selection of a channel.
Checking the forward output power

To check the transmission path forward output power: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF 3. Enter the following command: TS A CHAN nnn Where: A nnn is: all timeslots (TS). the specified channel number.
4.
To switch the power on, enter the following command: TS A TXPWR 00 Where: A 00 is: all timeslots (TS). maximum output power
5. 6.
Monitor and record the wattmeter reading (the forward output power). To switch the power off, enter the following command: TS A TXPWR FF Where: A FF is: all timeslots (TS). zero output power
326
31st Jul 01
GSM-100-423
Checking the reverse power

To check the transmission path reverse power: 1. 2. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up. 3. To switch the power on, enter: TS A TXPWR 00 4. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1 W. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 5. To switch the power off, enter: TS A TXPWR FF 6. 7. Repeat steps 3 to 5 for the required number of channels. At the EQCP prompt type: HALT C 8. Remove the power meter and reconnect the antenna.
Calibrating TCU-B transmit output power

To calibrate TCU-B transmit output power: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF

31st Jul 01
68P02901W43-J
327
GSM-100-423
3.
At the EQCP prompt type: CSPWR The following message is displayed:

4.
Enter U or D to adjust the TCU-B Tx power to achieve the appropriate value, as detailed in Table 3-6: Table 3-6 Achievable Tx RF power output TCU type Twin band pass filter, no duplexer TCU-B All 40 W (46 dBm) Achievable value No combining Not applicable One stage combining 20 W (43 dBm)
5.
As U or D is typed, a message similar to the following example, indicating the TCU-B output power and offset value, is displayed:
D P: 43.8 dBm Cell Site Offset: 1
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C 6. At the EQCP prompt type: HALT C WRENB SAVE CAL TX WRPTC NOTE The cell site offset can be checked by reading the memory location: Use FR TX to verify writes to FLASH Use MR TX to verify writes to RAM 7. 8. 9. Repeat steps 1 to 6 until all transceivers have been calibrated. Remove the power meter and reconnect the antenna. Use the Restoring the site procedure to return the site to service.
328
31st Jul 01
GSM-100-423
TCU-B VSWR and cellsite power calibration for CCBs

CCB calibration information
The Cavity Combining Block (CCB) combines the output of up to three radios to a common output, and up to six radios by use of an additional CCB(extension). The CCB(extension) output is an input to the CCB(output) for a single-antenna system. Every transmitted frequency will be attenuated by approximately 3.5 dB for a six cavity system and 2.7 dB in a three cavity system. The CCB is not available for M-Cell2. NOTE All CCB commands are issued via the TTY port on a TCU-B. An M-Cell6 can support up to two CCB modules. There is a minimum of one CCB control board. The CCB control board is located at the front of the CCB beneath a screw down cover. If redundancy of the CCB control board is provided, both CCB modules will be equipped with a CCB control board. The CCB has an address which is defined in the database using the equip_device COMB command. The address can also be displayed by using the disp_equipment COMB command. The CCB control board has a set of eight DIP switches which are used to provide the binary representation of the address defined in the database. These switches have all been set to zero in the Preparing for test procedure. Once the cellsite power has been set the DIP switches should be returned to positions for the address defined in the database.
Example of DIP switch setting

If the combiner address is required to be 75 (hex 4B), the DIP switches will be set as Table 3-7. Table 3-7 Switch settings for example of value 75 Switch On/off for value 75 Binary value of each switch NOTE S S If CCB control board redundancy is supported, the dip switches must be set the same on both CCB control boards. 255 (all on) is not a valid address. 8 off 128 7 on 64 6 off 32 5 off 16 4 on 8 3 off 4 2 on 2 1 on 1

31st Jul 01
68P02901W43-J
329
GSM-100-423
CCB control board details

The CCB control board is equipped with a green LED to indicate the presence of power. If a single CCB control board is used it must be in position 0, or the right of the cabinet when viewed from the front. If two CCB control boards are used, the one mounted on the right, looking from the front, will normally be the master. If this unit fails, the redundant unit will automatically assume control. The initial main/standby relationship is defined from the power connection to the top panel of the M-Cell6 cabinet. The two CCB control boards receive power from different pins in the connector, this provides the main/ standby relationship. A fault or problem with the CCB control board is indicated by a red LED, which can be viewed from above. There is not a master/slave relationship as no CCB control board has any influence over the other. It is a main/standby relationship where each CCB control board is equally aware of what is happening with the CCB system, hence the ability for the standby CCB control board to take seamless control in the event of a problem with the main CCB control board. NOTE The CCB control board is sometimes referred to as the Transmit Antenna Transceiver Interface Control Board (TATI Control Board or TCB).
330
31st Jul 01
GSM-100-423
Calibration procedures
The procedures Tuning the CCB cavities, VSWR calibration procedure, Calibrating cellsite power and Parking the CCB cavities should be used for VSWR and cellsite calibration of M-Cell6 cabinets equiped with TCU-Bs and CCB RF combiners. NOTE The four calibration procedures should be completed sequentially, and without pause, for each radio. Failure to do so could result in the associated CCB being parked on the wrong channel.
Tuning the CCB cavities

The following procedure details the steps necessary to tune the cavities in preparation for the VSWR and cellsite power calibration. The TCU-B radios use channel 31 as the default value associated with the CSPWR command. The procedure should be performed on each radio in turn: 1. 2. 3. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. Connect a PC to the TCU-B TTY interface port. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF 4. Issue the full tuning command to the CCB. To tune cavity 0, at the EQCP prompt, type: SNDCMB 02 05 00 01 00 1F 00 27 Where: 02 is the parameter download message ID. 05 is the number of bytes to follow, excluding final checksum. 00 is the CCB address (as set on the DIP switches). 01 is the hex value of the address of the cavity to be tuned. (set for cavity 0) 00 is the channel high byte. 1F is the channel low byte (set for channel 31). 00 is the power level always 00. 27 is the low byte of the checksum (02 + 05 + 00 + 01 + 00 + 1F + 00).

31st Jul 01
68P02901W43-J
331
GSM-100-423
The response should occur in under 12 seconds and begin with 01. A typical response, if OK, is:
01 04 00 01 00 00 06
A typical failure response is:

F1 0B 00 A0,
followed by a repetition of the input bytes. Table 3-9 details the tuning commands for all possible cavities.
VSWR calibration procedure

To check the VSWR of the transmission path: 1. 2. 3. 4. 5. At the EQCP prompt type: CSPWR Monitor and record the wattmeter reading (the forward output power). Press ESC or CTRL-Y or CTRL-C Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up. 6. 7. At the EQCP prompt type: CSPWR Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1 W . If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 8. Press ESC or CTRL-Y or CTRL-C
Calibrating cellsite power

To calibrate the cellsite power: 1. At the EQCP prompt type: CSPWR The following message is displayed:
332
31st Jul 01
GSM-100-423
2.
Enter U or D to adjust the TCU-B Tx power to achieve the appropriate value, as detailed in Table 3-8: Table 3-8 Achievable Tx RF power output TCU type Twin band pass filter, no duplexer TCU-B All 40 W (46 dBm) Achievable value No combining Not applicable One stage combining 20 W (43 dBm)
3.
As U or D is typed, a message similar to the following example, indicating the TCU-B output power and offset value, is displayed:
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C 4. Save the transmit power calibration. At the EQCP prompt type: HALT C WRENB SAVE CAL TX WRPTC
Parking the CCB cavities

To prevent cavity interference park the cavity. To park cavity 0, at the EQCP prompt type: SNDCMB C2 02 00 01 C5 Where: C2 is the parameter download message ID. 02 is the number of bytes to follow, excluding final checksum. 00 is the CCB address (as set on the DIP switches). 01 is the hex value of the address of the cavity to be tuned. (set for cavity 0) C5 is the low byte of the checksum (C2 + 02 + 00 + 01).
Repeat for remaining cavities

Repeat the procedures Tuning the CCB cavities, VSWR calibration procedure, Calibrating cellsite power and Parking the CCB cavities until all transceivers have tuned the CCB cavity they are connected to and the TX output power has been calibrated. The cavity tuning and parking commands are detailed in Table 3-9 and Table 3-10

31st Jul 01
68P02901W43-J
333
GSM-100-423
Table 3-9 TCU-B CCB cavity tuning commands Cavity to be tuned 0 1 2 3 4 5 02 02 02 02 02 02 05 05 05 05 05 05 Cavity tuning command 00 00 00 00 00 00 01 02 04 08 10 20 00 00 00 00 00 00 1F 1F 1F 1F 1F 1F 00 00 00 00 00 00 27 28 2A 2E 36 46
Table 3-10 TCU-B CCB cavity parking commands Cavity to be parked 0 1 2 3 4 5 Cavity parking command C2 C2 C2 C2 C2 C2 02 02 02 02 02 02 00 00 00 00 00 00 01 02 04 08 10 20 C5 C6 C8 CC D4 E4
Remove the power meter and reconnect the antenna. Use the Restoring the site procedure to return the site to service.
334
31st Jul 01
GSM-100-423
Restoring the site

After all installed TCU-Bs have been checked and calibrated, perform the following steps to restore the site. Restoration of the site is done in two stages: S S RF output power check. Returning the TCU-Bs to call processing mode.

1. 2. 3. 4. 5. Remove the 9 to 25-way EQCP cable from the TTY port and connect a 9 to 9-way cable to the MCU MMI port. Disconnect the antenna and connect a dummy load and wattmeter fitted with a 50 W element to the TX output. Return the DIP switches on the CCB control boards to their original positions. Press the reset button on the front panel of the TCU-B under test. Unlock the DRI under test using the following commands: unlock_device # dri A * state # DRI A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
This forces the TCU-B to enter the Unlocked Busy state (confirmed by the state command). 6. 7. Monitor and record the wattmeter reading. Lock the TCU-B by entering: lock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Repeat steps 4 to 7 for all DRIs.

31st Jul 01
68P02901W43-J
335
GSM-100-423
Returning the TCU-Bs to call processing mode

1. 2. Remove the wattmeter and reconnect the antenna lead to the TX port. Unlock all DRIs tested using the command detailed in step 5 of RF output power check. The command is to be entered for each TCU-B to be unlocked. 3. 4. Remove the 9 to 9-way cable from the MCU MMI port. Inform the OMC the VSWR and cellsite power calibration has been completed.
336
31st Jul 01
GSM-100-423
Calibrating M-Cell2/6 TCU900/1800/1900 bay level offset tables

Introduction
Follow this procedure to calibrate the bay level offset tables to compensate for the losses or gains due to preselectors and RF cabling from the antenna inputs at the M-Cell2 or M-Cell6 to the TCU900, TCU1800, or TCU1900 input. NOTE This procedure applies only to the TCU900, TCU1800 and TCU1900. All units are factory calibrated. This procedure is thus necessary only if one of the following changes occur: S S S S A TCU is replaced. RF front end equipment is changed. The site is reconfigured. High power duplexers are fitted. NOTE The procedures contained in Calibrating M-Cell2/6 TCU900/1800/1900 bay level offset tables are to calibrate a single TCU. Repeat the procedures for all TCUs affected by the changes listed above.
Test equipment
The following test equipment is required: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 50 ohm 50 W dummy load. A signal generator (0 to 2 GHz). 9-way to 9-way cable. 9-way to 25-way RS232 cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
Commands
The following commands must be used to carry out the procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. The lock_device, unlock_device and clear_cal_data commands are BSS MMI commands and may be entered in upper or lower case. The remainder of the commands in this list are TCU (emulator) or TCU TSM port commands and must be input as shown. The first TCU password must be upper case.

31st Jul 01
68P02901W43-J
337
GSM-100-423
BSS MMI command lock_device unlock_device clear_cal_data TCU TTY command SWAP C 0 EXEC C 0 SWAP E A CONFGR E A TEST CAL BAY @1/@2 EQTEST 0 IQDCP 0 AIC OUT TS A CHAN # TS A ANT # R F:XX YY SYNTH 1 SYNTH NRM SAVE CAL BAY BAYDONE @N TCU TSM port command tcu_clock 0
Function Prevents the device being used Frees the device for further use Clears previously stored calibration data for a specified radio unit on a per DRI basis Function Swaps DPC code from ROM to RAM and checks validity Executes DPC code currently stored in RAM Swaps EQ code from ROM to all four EQDSPs and checks validity Sends call processing calibration tables to equaliser Places the TCU into test mode Calibrates the bay level receive equipment Puts equalizer 0 into test mode and checks status Passes the factory calibrated dc offset information stored in ROM to EQDSP 0 Disables automatic intermodulation compensation Sets all timeslots to channel # Sets all timeslots to antenna # Reads flash memory bay level data held at addresses XX to YY Stops synthesizer switching with synthesizer 1 permanently on Enables synthesizer switching into normal working Transfers Bay Level Calibration stored data in RAM to ROM Informs control processor that Bay Level Calibration is valid for branch N and sets bay level flag Function Stops the TCU hunting between fibre A and fibre B and forces the TCU to look only at fibre A.
338
31st Jul 01
GSM-100-423
Locking radio, dummy load and TCU reset

The radio has first to be locked, a dummy load connected if no antenna, and the TCU reset so that it is ready for Bay Level Calibration. Proceed as follows: NOTE The two receive cables must be connected to the TCU at all times, as the cable connecting the TCU RX IN 1 terminal carries signalling information to the IADU and the cable connecting the TCU RX IN 2 terminal carries power feed to the DLNB. 1. 2. Connect the 9-way to 9-way cable from the PC serial A port to MCU TTY port. At the PC start the terminal emulator program. WARNING Failure to lock the cell could result in the BCCH transmitting into, and causing damage to the signal generator. The maintenance engineer could receive RF burns when connecting to the antenna socket. 3. Type: lock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
4.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 5. If a Tx antenna is not connected to the TCU under test connect a 50 ohm 50 W dummy load to the Tx port of the TCU under test.

31st Jul 01
68P02901W43-J
339
GSM-100-423
6. 7.
Remove the 9-way to 9-way cable from the PC serial A port to MCU TTY port. Reset the TCU using the front panel reset button.
Silencing PLL_LK alarm

With the TCU in test mode, and no redundant MCU or FOX fibre pair present, there will be a PLL_LK alarm cycling on and off as the radio hunts between its fibre inputs for a reference. This may interfere with the CAL BAY @n (n=1,2) command. The following procedure forces the radio to lock to fibre A, stopping the alarm. NOTE If the BTS is equipped with a redundant MCU and both fibre pairs A and B are connected then this procedure may be omitted. 1. 2. 3. Connect a standard 9-way to 25-way RS232 cable from the PC serial A port to the TCU TSM port. Set up a terminal connection to this port at 9600 baud. At the ROM prompt type: tcu_clock 0 4. Remove the 9-way to 25-way cable from the PC serial A port to the TCU TSM port.
340
31st Jul 01
GSM-100-423
Setting up TCU for Bay Level

The TCU has to be set up to respond to bay level calibration. Proceed as follows: 1. 2. 3. Connect the 9-way to 9-way cable from the PC serial A port to CNTRL PRCSR port on the TCU. Enter the boot passwords. At the SCP prompt type: SWAP C 0 The system responds with the following:
Swap in completed O.K.
At the SCP prompt type: EXEC C 0 The system responds with the following:
The current state of the Control Processor is Active Standby. The last reset was caused by hardware.
4.
At the SCP prompt type: .<LEVEL_3_PASSWORD> (different from the RCU level 3 password) SWAP E A The system responds with the following:
Swap in completed O.K.
5.
At the SCP prompt type: CONFGR E A The system will respond with the following:
Equalizer #0 configuration successful Equalizer #1 configuration successful Equalizer #2 configuration successful Equalizer #3 configuration successful
6.
At the SCP prompt type: TEST AIC OUT EQTEST 0 The system responds with the following:
003D Equalizer is now in Test Mode
7.
At the SCP prompt type: IQDCP 0 The system responds with the following:
0057 Equalizer has been configured with the DC Offsets

31st Jul 01
68P02901W43-J
341
GSM-100-423
Bay level calibration for branch1 RX1A

Proceed as follows: 1. Connect the output of the signal generator to branch 1 of the antenna port at the top of the cabinet for the TCU under test as indicated in Table 3-11. NOTE As the IADU connects the TCU900 receive port to the receive antenna via the DLNB, and there are up to three DLNBs per cabinet, it is important to choose the correct number in the TS A ANT command. If RX path is via DLNB 0 then antenna is TS A ANT 1. If RX path is via DLNB 1 then antenna is TS A ANT 2. If RX path is via DLNB 2 then antenna is TS A ANT 3. See Examples with diagrams in later pages, for further explanation. The antenna number can also be found by using the disp_equipment # DRI A * 0 command. The number next to antenna_select is the antenna number. Table 3-11 Signal generator to TCU connection TCU frequency PGSM/EGSM900 Non duplexer configurations RX1 on relevant DLNB. Duplexer configurations ANTENNA/ANT port of medium or external highpower duplexer which is connected to RX1 on the DLNB.
DCS1800/PCS1900
A on the relevant ANTENNA/ANT port of duplexer which is LNA. connected to A on the LNA.
Any TCU within an M-Cell6 cabinet can be connected to any input signal. The IADU switches the outputs of up to three DLNBs to up to six TCUs. An IADU in one cabinet can be connected to an IADU in another cabinet via extension ports. 2. Set the signal generator at a level of 65.2 dBm, to the first channel test frequency shown in Table 3-12, Table 3-13 or Table 3-14. NOTE The Tx level of the signal generator must be set to allow for losses in the test leads used. It is VITAL that the signal generator and cables are correctly calibrated, and the RF cables are in good order. If signal generator connection is made at a location away from the top of the cabinet, make allowance for loss in the feeder cable to the antenna port at the top of the cabinet, by increasing the 65.2 dBm level. For example, if feeder cable loss is 4dBm, the signal generator should be set to 61.2 dBm. The High Power Duplexer should be considered part of the cabinet for this connection. 3. At the SCP prompt type: TS A ANT 1
342
31st Jul 01
GSM-100-423
4.
At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 3-12 , Table 3-13 or Table 3-14.
5.
At the SCP prompt type: SYNTH 1 CAL BAY @1 The system responds with the following:
0051 0005 28F4 Rx Bay Level Offset = F7
6.
At the SCP prompt type: SYNTH NRM NOTE When the synthesizer is left unlocked, the bay level figure can vary as much as 1dB at certain frequencies. By locking the synthesizer (using commands SYNTH 1 and SYNTH NRM this variation can be reduced to 0.1 dB.
7. 8.
Repeat steps 4 to 6 for each signal generator test frequency in Table 3-12, Table 3-13 or Table 3-14. At the SCP prompt type: SAVE CAL BAY The system responds with the following:
Transfer of Calibration Data to NonVolatile Storage Complete
This transfers the Bay Level Calibration figures to non-volatile TCU memory.

31st Jul 01
68P02901W43-J
343
GSM-100-423
Examples with diagrams

The following examples are intended to clarify how to identify antenna number for each TCU. Figure 3-4 shows a single M-Cell6 cabinet supporting a 2/2/2 configuration (3 cells with 2-carriers per cell).
Cell C
Cell B
Cell A
D L N B
0
I A D U
T C U
T C U
T C U
T C U
T C U
T C U
Antenna Select Number

Figure 3-4 M-Cell6 2/2/2 configuration (3 cells with 2 carriers per cell). For cell A the receive antennas are connected to DLNB 0; these antennas are known as antenna 1, so the timeslot command is TS A ANT 1. For cell B the receive antennas are connected to DLNB 1; these antennas are known as antenna 2, so the timeslot command is TS A ANT 2. For cell C the receive antennas are connected to DLNB 2; these antennas are known as antenna 3, so the timeslot command is TS A ANT 3.
344
31st Jul 01
GSM-100-423
Figure 3-5 shows two M-Cell6 cabinets supporting a 4/4/4 configuration (3 cells with 4 carriers per cell).
Cell C
Cell B
Cell A
Cabinet 2
Cabinet 1
D L N B
2 2
1 1 0
2 2
1 1
0 0
I A D U
T C U -
T C U
T C U
T C U
T C U
T C U
T C U
T C U
T C U
T C U
T C U
T C U

Figure 3-5 M-Cell6 4/4/4 configuration (3 cells with 4 carriers per cell). For cell A the receive antennas are connected to DLNB 0 in cabinet 1; these antennas are known as antenna 1, so the timeslot command is TS A ANT 1. For cell B the receive antennas are connected to DLNB 2 in cabinet 1 and extended to the DLNB 0 connector in cabinet 2 (by using the extender module). The cabinet 1 transceivers see the antennas as antenna 3 and require the TS A ANT 3 timeslot command, and the cabinet 2 transceivers see the antennas as antenna 1 and require the TS A ANT 1 timeslot command. For cell C the receive antennas are connected to DLNB 2 in cabinet 2; these antennas are known as antenna 3, so the timeslot command is TS A ANT 3.

31st Jul 01
68P02901W43-J
345
GSM-100-423
Table 3-12 GSM900 and EGSM900 test frequencies Channel 979 (see note) 987 (see note) 995 (see note) 1003 (see note) 1011 (see note) 1019 (see note) 03 11 19 27 35 NOTE Channels 979 to 1019 apply to Extended GSM only. Frequency (MHz) 881.001 882.601 884.201 885.801 887.401 889.001 890.601 892.201 893.801 895.401 897.001 Channel 43 51 59 67 75 83 91 99 107 115 123 Frequency (MHz) 898.601 900.201 901.801 903.401 905.001 906.601 908.201 909.801 911.401 913.001 914.601
346
31st Jul 01
GSM-100-423
Table 3-13 DCS1800 test frequencies Channel 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700 Frequency (MHz) 1711.001 1712.601 1714.201 1715.801 1717.401 1719.001 1720.601 1722.201 1723.801 1725.401 1727.001 1728.601 1730.201 1731.801 1733.401 1735.001 1736.601 1738.201 1739.801 1741.401 1743.001 1744.601 1746.201 1747.801 Channel 708 716 724 732 740 748 756 764 772 780 788 796 804 812 820 828 836 844 852 860 868 876 883 Frequency (MHz) 1749.401 1751.001 1752.601 1754.201 1755.801 1757.401 1759.001 1760.601 1762.201 1763.801 1765.401 1767.001 1768.601 1770.201 1771.801 1773.401 1775.001 1776.601 1778.201 1779.801 1781.401 1783.001 1784.401

31st Jul 01
68P02901W43-J
347
GSM-100-423
Table 3-14 PCS1900 test frequencies Channel 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 Frequency (MHz) 1851.001 1852.601 1854.201 1855.801 1857.401 1859.001 1860.601 1862.201 1863.801 1865.401 1867.001 1868.601 1870.201 1871.801 1873.401 1875.001 1876.601 1878.201 1879.801 Channel 668 676 684 692 700 708 716 724 732 740 748 756 764 772 780 788 796 804 Frequency (MHz) 1881.401 1883.001 1884.601 1886.201 1887.801 1889.401 1891.001 1892.601 1894.201 1895.801 1897.401 1899.001 1900.601 1902.201 1903.801 1905.401 1907.001 1908.601
348
31st Jul 01
GSM-100-423

Continue the bay level calibration procedure to the second antenna port as follows: NOTE It may not be possible to calibrate all three antennas because there may not be a DLNB or LNA fitted to every RX port ( see Examples with diagrams). 1. 2. 3. Connect the output of the signal generator to RX2A. Set the signal generator to the first channel test frequency shown in Table 3-12, Table 3-13 or Table 3-14. At the SCP prompt type: TS A ANT 2 4. At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 3-12, Table 3-13 or Table 3-14.
5.
6.
At the SCP prompt type: SYNTH NRM
7. 8.
Repeat steps 4 to 6 for each signal generator test frequency in Table 3-12, Table 3-13 or Table 3-14. At the SCP prompt type: SAVE CAL BAY The system responds with the following:

31st Jul 01
68P02901W43-J
349
GSM-100-423

Continue the Bay Level Calibration procedure to the third antenna port as follows: NOTE It may not be possible to calibrate all three antennas because there may not be a DLNB or LNA fitted to every RX port. 1. 2. 3. Connect the output of the signal generator to RX3A. Set the signal generator to the first channel test frequency shown in Table 3-12, Table 3-13 or Table 3-14. At the SCP prompt type: TS A ANT 3 4. At the SCP prompt type: TS A CHAN # Where: # is: the channel number as shown in Table 3-12, Table 3-13 or Table 3-14.
5.
6.
At the SCP prompt type: SYNTH NRM
7. 8.
Repeat steps 4 to 6 for each signal generator test frequency listed in Table 3-12, Table 3-13 or Table 3-14. At the SCP prompt type: SAVE CAL BAY The system responds with the following:
Branch completion
The BAYDONE command completes the procedure for a branch, by setting a flag to indicate the calibration figures are correct. Proceed as follows: 1. At the SCP prompt type: BAYDONE @1 The system responds with the following:
350
31st Jul 01
GSM-100-423
Branch 2
Repeat the procedures Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A for branch 2 by connector RX2 for TCU900 and connector B for TCU1800/TCU1900 at the top of the cabinet. Enter @2 instead of @1 in the cal bay and baydone commands. NOTE Only one branch calibration is required in the special case of an M-Cell2 dual antenna/shared radios (bow-tie). This is because each radio can be split in a bow-tie to either antenna, and one measured branch will provide accuracy to within the GSM specification.

31st Jul 01
68P02901W43-J
351
GSM-100-423
The following procedure should be followed to check the bay level calibration has been successful. 1. To verify that the bay level offset values have been stored in EPROM use the read command with the required offset table location as an argument, the read command locations are shown in Table 3-15 to Table 3-18 below, for example: R F:153B6 153C5 in the case of a TCU900
TCUs that cover only the GSM range, need only use the 16 locations per antenna per branch shown in Table 3-15 GSM900 frequency offset addresses. Table 3-15 GSM900 frequency offset addresses Antenna RX1A Antenna 1 Branch 1 RX2A Antenna 2 Branch 1 RX3A Antenna 3 Branch 1 RX1B Antenna 1 Branch 2 RX2B Antenna 2 Branch 2 RX3B Antenna 3 Branch 2 Locations F: 15386 15395 F: 153B6 153C5 F: 153E6 153F5 F: 15416 15425 F: 15446 15455 F: 15476 15485
TCUs that cover the EGSM range, store offsets at 22 locations in each memory area per antenna per branch. As the read command allows a maximum of 16 locations to be read at one time, each memory area has to use the read command twice, as shown in Table 3-16 EGSM900 frequency offset addresses. Table 3-16 EGSM900 frequency offset addresses Antenna Locations First read RX1A Antenna 1 Branch 1 RX2A Antenna 2 Branch 1 RX3A Antenna 3 Branch 1 RX1B Antenna 1 Branch 2 RX2B Antenna 2 Branch 2 RX3B Antenna 3 Branch 2 F: 15380 1538F F: 153B0 153BF F: 153E0 153EF F: 15410 1541F F: 15440 1544F F: 15470 1547F Second read F: 15390 15395 F: 153C0 153C5 F: 153F0 153F5 F: 15420 15425 F: 15450 15455 F: 15480 15485
NOTE The lowest 6 locations for each antenna apply to Extended GSM only.
352
31st Jul 01
GSM-100-423
DCS1800/PCS1900 TCUs require the read command to be used three times per antenna per branch, as shown in Table 3-17 and Table 3-18. Table 3-17 DCS1800 frequency offset addresses Antenna First read RX1A Antenna 1 (A) RX2A Antenna 2 (A) RX3A Antenna 3 (A) RX1B Antenna 1 (B) RX2B Antenna 2 (B) RX3B Antenna 3 (B) F: 15380 1538F F: 153B0 153BF F: 153E0 153EF F: 15410 1541F F: 15440 1544F F: 15470 1547F Locations Second read F: 15390 1539F F: 153C0 153CF F: 153F0 153FF F: 15420 1542F F: 15450 1545F F: 15480 1548F Third read F: 153A0 153AE F: 153D0 153DE F: 15400 1540E F: 15430 1543E F: 15460 1546E F: 15490 1549E
Table 3-18 PCS1900 frequency offset addresses Antenna First read RX1A Antenna 1 (A) RX2A Antenna 2 (A) RX3A Antenna 3 (A) RX1B Antenna 1 (B) RX2B Antenna 2 (B) RX3B Antenna 3 (B) 2. F: 15380 1538F F: 153B0 153BF F: 153E0 153EF F: 15410 1541F F: 15440 1544F F: 15470 1547F Locations Second read F: 15390 1539F F: 153C0 153CF F: 153F0 153FF F: 15420 1542F F: 15450 1545F F: 15480 1548F Third read F: 153A0 153A4 F: 153D0 153D4 F: 15400 15404 F: 15430 15434 F: 15460 15464 F: 15490 15494
If the bay level calibration is successful, each appropriate table location will contain valid offsets and not the factory default of 80. NOTE The presence of 80 will result in error alarm DRI 218: Invalid Transceiver Calibration Data being reported when the unit is unlocked. However, unused data columns in a site configuration may have value 80; no alarm will be reported as such table locations are inappropriate to the site.
The 6-column table has the following form: (Branch 1) Antenna 1 Antenna 2 NOTE Any value other than 80 is a valid offset, from 81 to FF, and 00 to 7F. Only the value 80 requires investigation. 3. If the value 80 is present, it indicates that the bay level calibration was unsuccessful, and that it will need to be repeated after checking the configuration and RF cables. If the radio is suspected to be faulty, see next section Diagnostic check of TCU. Antenna 3 Antenna 1 (Branch 2) Antenna 2 Antenna 3
4.

31st Jul 01
68P02901W43-J
353
GSM-100-423
Diagnostic check of TCU

If it is suspected that a bay level calibration problem is caused by the TCU, then a diagnostic check can be made by performing a bay level calibration on the TCU alone. Proceed as follows: 1. Set the signal generator to 55 dBm plus lead loss. This will simulate a gain of 10 dB. 2. Connect directly to branch 1 or 2 on the TCU. CAUTION Ensure a TCU is switched to SCU mode before connection to RX2. In TCU mode the RX2 inner is at +12 V dc to power the DLNB in M-Cell equipment. A signal source may be damaged by taking +12 V dc in its RF output. 3. Follow the Bay Level Calibration procedure for each branch, Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A. NOTE Ensure the mode switch is returned to the TCU position on completion of testing. 4. Check the diagnostic offset values are within the range 97 (lower) and D3 (upper). NOTE The range 97 D3 used in step 4 applies to TCU diagnostic checks only, and should not be compared with the bay level calibration figures. If the values are correct, then the TCU is working correctly and any fault will probably be in the cabinet front end cables, cable connections or LNA or DNLB. If the offsets are outside this range, the TCU is faulty and should be returned.
354
31st Jul 01
GSM-100-423
End procedure restoring site

After the bay level calibration procedure is completed, restore the site by the following: 1. 2. 3. 4. 5. Remove the signal generator and dummy load and refit the site RF cables. Remove the 9-way to 9-way cable from the CNTRL PRSCR port on the TCU. Connect the 9-way to 9-way cable from the PC serial A port to a MCU TTY port. Press the reset button on the front panel of the TCU. Type: unlock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
The TCU is now in the unlocked_busy state. 6. Type: disp_act_alarm # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, repeat the whole Bay Level Calibration procedure 7. Remove the 9-way to 9-way cable from the MCU TTY port.

31st Jul 01
68P02901W43-J
355
Calibrating M-Cell2/6 TCU-B bay level offset tables
GSM-100-423

Introduction
Follow this procedure to calibrate the bay level offset tables to compensate for the losses or gains due to preselectors and RF cabling from the antenna inputs at the M-Cell2 or M-Cell6 to the TCU-B input. NOTE This procedure applies only to the TCU-B. The TCU-B can only be used with software release 1.5.1.6 onwards. All units are factory calibrated. This procedure is thus necessary only if one of the following changes occur: S S S S A TCU-B is replaced. RF front end equipment is changed. The site is reconfigured. High power duplexers are fitted. NOTE The procedures contained in Calibrating M-Cell2/6 TCU-B bay level offset tables are to calibrate a single TCU-B. Repeat the procedures for all TCU-Bs affected by the changes listed above.
Test equipment
The following test equipment is required: S S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 50 ohm 50 W dummy load. A signal generator (0 to 2 GHz). 9-way to 9-way cable. 9-way to 25-way RS232 cable. 9-way to 25-way EQCP cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
356
31st Jul 01
GSM-100-423
Commands
The following table lists the commands for the bay level calibration procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. BSS MMI commands may be entered in upper or lower case. TCU-B emulator or RSS MMI commands must be entered as shown. The first transceiver password must be in upper case. BSS MMI command ins_device lock_device unlock_device clear_cal_data TCU-B emulator TTY command TEST BBH ALARM OFF CAL BAY @1/@2 AIC OUT ACT C TS A CHAN # TS A ANT # SYNTH 1 SYNTH NRM SAVE CAL BAY BAYDONE @N HALT C WRENB WRPTC FR BAY MR BAY RSS MMI command tcu_clock 0 Inhibits the BBH alarm Calibrates the bay level receive equipment Disables automatic intermodulation compensation Activates the Control Processor Sets all timeslots to channel # Sets all timeslots to antenna # Stops synthesizer switching with synthesizer 1 permanently on Enables synthesizer switching into normal working Transfers Bay Level Calibration stored data in RAM to FLASH EPROM Informs control processor that bay level calibration is valid for branch N and sets bay level flag Stops the Control Processor Write enables the FLASH EPROM Write protects the FLASH EPROM Reads cal bay offsets from FLASH EPROM Reads cal bay offsets from RAM Function Stops the TCU-B hunting between fibre A and fibre B and forces the TCU-B to look only at fibre A. Function Initializes the device, bringing it into service Prevents the device being used Frees the device for further use Clears previously stored calibration data for a specified radio unit on a per DRI basis Function Places the TCU-B into test mode

31st Jul 01
68P02901W43-J
357
GSM-100-423
Preparation for bay level calibration

The RF path has to be prepared for bay level calibration. The radio has to be reset and locked, a dummy load connected if no antenna and the alarms disabled. Proceed as follows: NOTE The two receive cables must be connected to the TCU-B at all times, as the cable connecting the TCU-B RX IN 1 terminal carries signalling information to the IADU and the cable connecting the TCU-B RX IN 2 terminal carries power feed to the DLNB. 1. 2. 3. Connect the 9-way to 9-way cable from the PC serial A port to MCU TTY port. At the PC start the terminal emulator program. At the MMI-RAM> prompt type: ins_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The radio must be brought into service as there is no Flash EPROM storage of code at the radio control processor level. If a connection to the BSC is not available a PCMCIA commissioning card must be used.
358
31st Jul 01
GSM-100-423
4.
Wait for the radio to finish initializing, then type: WARNING Failure to lock the cell could result in the BCCH transmitting into, and causing damage to the signal generator. The maintenance engineer could receive RF burns when connecting to the antenna socket. lock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE For ease of calibration, all TCU-Bs in a cell should be initialized and then locked. Always lock the transceiver providing the BCCH last as this prevents the BCCH being switched to alternate transceivers. 5. Type: clear_cal_data # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 6. 7. Connect port COM1 on the PC to the TTY Interface port on the radio using a 9-way to 25-way RS232 cable. At the MMI-ROM prompt type: tcu_clock 0 The system responds with the following:
WARNING: TCU must be reset to get connection to MCU.
NOTE Do not reset the TCU at this point. The reset is carried out on completion of the bay level calibration procedure, as detailed in section End procedure restoring site.

31st Jul 01
68P02901W43-J
359
GSM-100-423
8.
If a tx antenna is not conected to the radio under test, connect a 50 ohm 50 W dummy load to the Tx port of the radio under test. CAUTION Ensure that you have entered the tcu_clock 0 command at the RSS MMI-ROM 0000> prompt, as shown in step 7 before entering call processing to avoid EQCP instability at step 3 of Bay level calibration (next procedure).
9. 10.
Remove the 25 pin RSS connector from the radio and replace it with a 9 to 25-way EQCP cable. At the EQCP prompt type: .GSMFW At the EQCP prompt type: TEST The system responds with the following:
WARNING: The EQCP is now in test mode.
At the EQCP TEST prompt type: BBH ALARM OFF The system responds with the following:
The alarm reporting for the BBH connection is turned off
At the EQCP TEST prompt type: AIC OUT The system responds with the following:
The AIC pad for branch 1 is OUT. The AIC pad for branch 2 is OUT.
360
31st Jul 01
GSM-100-423
Bay level calibration for branch 1 RX1A

Proceed as follows: 1. Connect the output of the signal generator to branch 1 of the antenna port at the top of the M-Cell cabinet. NOTE As the IADU connects the TCU-B receive port to the receive antenna via the DLNB, and there are up to three DLNBs per cabinet, it is important to choose the correct number in the TS A ANT command. If RX path is via DLNB 0 then antenna is TS A ANT 1. If RX path is via DLNB 1 then antenna is TS A ANT 2. If RX path is via DLNB 2 then antenna is TS A ANT 3. See Examples with diagrams in later pages, for further explanation. The antenna number can also be found by using the disp_equipment # DRI A * 0 command. The number next to antenna_select is the antenna number. 2. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 3-19. Table 3-19 EGSM900 test frequency table Channel 979 987 995 1003 1011 1019 03 11 19 27 35 3. Frequency (MHz) 881.001 882.601 884.201 885.801 887.401 889.001 890.601 892.201 893.801 895.401 897.001 At the EQCP TEST prompt type: ACT C The system responds with the following:
The EQCP is in the Call Processing state Warning: After locking carrier down, enter TCU_CLOCK 0 command at RSS MMI-ROM 0000> prompt before entering Call Processing to avoid EQCP instability.
Channel 43 51 59 67 75 83 91 99 107 115 123
Frequency (MHz) 898.601 900.201 901.801 903.401 905.001 906.601 908.201 909.801 911.401 913.001 914.601
TS A ANT 1 The system responds with the following:

All timeslots are under user control.

31st Jul 01
68P02901W43-J
361
GSM-100-423
4.
At the EQCP TEST prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 3-19.
The system responds with the following:

The data for all timeslots has been changed.
5.
At the EQCP TEST prompt type: SYNTH 1 The system responds with the following:
Synthesizer 1 is enabled.
At the EQCP TEST prompt type: CAL BAY @1 The system responds with the following:
BAY LEVEL OFFSET = XX
Where
XX
= The hex value of the bay level reading.
At the EQCP TEST prompt type: SYNTH NRM The system responds with the following:
The system is under real time control.
6.
Set the signal generator to the next frequency and repeat steps 4 and 5 for all the test frequencies in Table 3-19.
362
31st Jul 01
GSM-100-423
Examples with diagrams

The following examples are intended to clarify how to identify antenna number for each transceiver. Figure 3-6 shows a single M-Cell6 cabinet supporting a 2/2/2 configuration (3 cells with 2-carriers per cell).
Cell C
Cell B
Cell A
D L N B
2 2
1 1
0 0
I A D U
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B

Figure 3-6 M-Cell6 2/2/2 configuration (3 cells with 2 carriers per cell). For cell A the receive antennas are connected to DLNB 0; these antennas are known as antenna 1, so the timeslot command is TS A ANT 1. For cell B the receive antennas are connected to DLNB 1; these antennas are known as antenna 2, so the timeslot command is TS A ANT 2. For cell C the receive antennas are connected to DLNB 2; these antennas are known as antenna 3, so the timeslot command is TS A ANT 3.

31st Jul 01
68P02901W43-J
363
GSM-100-423
Figure 3-7 shows two M-Cell6 cabinets supporting a 4/4/4 configuration (3 cells with 4 carriers per cell).
Cell C
Cell B
Cell A
Cabinet 2
Cabinet 1
D L N B
2 2
1 1 0
2 2
1 1
0 0
I A D U
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B
T C U B

Figure 3-7 M-Cell6 4/4/4 configuration (3 cells with 4 carriers per cell). For cell A the receive antennas are connected to DLNB 0 in cabinet 1; these antennas are known as antenna 1, so the timeslot command is TS A ANT 1. For cell B the receive antennas are connected to DLNB 2 in cabinet 1 and extended to the DLNB 0 connector in cabinet 2 (by using the extender module). The cabinet 1 transceivers see the antennas as antenna 3 and require the TS A ANT 3 timeslot command, and the cabinet 2 transceivers see the antennas as antenna 1 and require the TS A ANT 1 timeslot command. For cell C the receive antennas are connected to DLNB 2 in cabinet 2; these antennas are known as antenna 3, so the timeslot command is TS A ANT 3.
364
31st Jul 01
GSM-100-423

Continue the bay level calibration procedure for the second antenna port as follows: NOTE It may not be possible to calibrate all three antennas because there may not be a DLNB or LNA fitted to every RX port ( see Examples with diagrams). 1. 2. 3. Connect the output of the generator to RX2A. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 3-19. At the EQCP prompt type: TS A ANT 2 4. At the EQCP prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 3-19.
5.
At the EQCP prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM
6.

31st Jul 01
68P02901W43-J
365
GSM-100-423

Continue the bay level calibration procedure for the third antenna port as folows: NOTE It may not be possible to calibrate all three antennas because there may not be a DLNB or LNA fitted to every RX port ( see Examples with diagrams). 1. 2. 3. Connect the output of the generator to RX3A. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 3-19. At the EQCP prompt type: TS A ANT 3 4. At the EQCP prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown inTable 3-19.
5.
At the EQCP prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM
6.
Branch completion
To complete the bay level procedure for the branch: 1. At the EQCP TEST prompt type: BAYDONE @1 The system responds with the following:
BAY LEVEL CALIBRATION IS DONE
2.
At the EQCP TEST prompt type: HALT C The system responds with the following:
The EQCP is in the Active Standby state
3.
At the EQCP TEST prompt type: WRENB The system responds with the following:
Device OK. Flash is now write enabled.
366
31st Jul 01
GSM-100-423
4.
At the EQCP TEST prompt type: SAVE CAL BAY The system responds with the following:
Save Cal Completed.
5.
At the EQCP TEST prompt type: WRPTC The system responds with the following:
Flash is now write protected.
Branch 2
Repeat the procedures Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A for branch 2 by connecting to RX1B, RX2B and RX3B alternately. Enter @2 instead of @1 in the cal bay and baydone commands. NOTE Only one branch calibration is required in the special case of an M-Cell2 dual antenna/shared radios. This is because each radio can be split in a bow-tie to either antenna, and one measured branch will provide accuracy to within the GSM specification.

31st Jul 01
68P02901W43-J
367
GSM-100-423
The following procedure should be used to check the bay level calibration has been successful. 1. To verify that the bay level offset values have been stored in EPROM, use the read command with the required offset table location as an argument. FR BAY MR BAY To verify writes to FLASH To verify writes to RAM Table 3-20 TCU-B frequency offset addresses Bay Level Calibration Storage Branch 1 Valid Flag Branch 2 Valid Flag Branch 1 Checksum Branch 2 Checksum Bay Level Offsets For Branch 1 Antenna 1 Bay Level Offsets For Branch 1 Antenna 2 Bay Level Offsets For Branch 1 Antenna 3 Bay Level Offsets For Branch 2 Antenna 1 Bay Level Offsets For Branch 2 Antenna 2 Bay Level Offsets For Branch 2 Antenna 3 Flash Address A000700 A000703 A000706 A000709 A00070C A00074B A00074E A00078D A000790 A0007CF A0007D2 A000811 A000814 A000859 A00085C A000895
TCU-Bs cover the EGSM range and store offsets in 22 locations in each memory area per antenna per branch. NOTE Each location consists of three bytes. For example, the branch 1 valid flag data is stored in address locations A000700, A000701 and A000702. 2. The following is an example of the first line of the FLASH BAY LEVEL OFFSET table when using the FR BAY command, and a description of the fields displayed:
BR1 BR2 flag 000001 BR1 Cksum 000595 BR2 Cksum 000595 BL offset 000060 BL offset 000002 BL offset 000005 BL offset 000002
Address
A000700
000001
The remaining rows of the table contain BL offset values
368
31st Jul 01
GSM-100-423
3.
If the bay level calibration is successful, each appropriate table location will contain valid offsets, and not the factory default of 80. NOTE The presence of 80 will result in error alarm DRI 218: Invalid Transceiver Calibration Data being reported when the unit is unlocked. However, unused data columns in a site configuration may have value 80; no alarm will be reported as such table locations are inappropriate to the site.
4.
If the value 80 is present it indicates an unsuccessful calibration procedure or an uncalibrated antenna port. The calibration procedure will have to be repeated after checking the configuration and RF cables. NOTE Any value other than 80 is a valid offset, from 81 to FF, and 00 to 7F. Only the value 80 requires investigation.
5.
If the radio is suspected faulty, see section TCU-B diagnostic check.

31st Jul 01
68P02901W43-J
369
GSM-100-423

After the bay level calibration procedure is completed, restore the site by the following: 1. 2. 3. Remove the signal generator and dummy load and refit the site RF cables. Remove the 9-way to 25-way cable from the TTY INTERFACE port on the TCU-B. Connect the 9-way to 9-way cable from the PC serial A port to a MCU TTY port. CAUTION The following step must be carried out to initialize software and so ensure the TCU-B is correctly brought into service. 4. 5. Press the reset button on the front panel of the TCU-B. Type: unlock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
The TCU-B is now in the unlocked_busy state. 6. Type: disp_act_alarm # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, redo the whole Bay Level Calibration procedure 7. Remove the 9-way to 9-way cable from the MCU TTY port.
370
31st Jul 01
GSM-100-423
TCU-B diagnostic check

CAUTION The RX2 inner of the TCU-B is at +12 V dc and is used to power the DLNB in M-Cell equipment. Failure to follow this procedure accurately could result in damage to the signal generator. If it is suspected that a bay level calibration problem is caused by the TCU-B, then a diagnostic check can be made by performing a bay level calibration on the TCU-B alone. Proceed as follows: 1. Use a signal generator that: Can withstand +25 V dc applied to its output. or Has a dc block between the generator output and transceiver RX2 input. 2. Set the signal generator to 55 dBm plus lead loss. This will simulate a gain of 10 dB. 3. 4. 5. Connect directly to branch 1 or 2 on the TCU-B. Follow the Bay Level Calibration procedure for each branch, Bay level calibration branch 1 RX1A, Bay level repeat for RX2A and Bay level repeat for RX3A. Check the diagnosic offset values are within the range 97 (lower) and D3 (upper). NOTE The range 97 D3 used in step 5 applies to TCU-B diagnostic checks only, and should not be compared with the bay level calibration figures. If the values are correct, then the TCU-B is working correctly and any fault will probably be in the cabinet front end cables, cable connections or LNA or DNLB. If the offsets are outside this range, the TCU-B is faulty and should be returned.

31st Jul 01
68P02901W43-J
371
Checking the database equipage
GSM-100-423

Introduction
The database equipage checks determine what devices and functions have been equipped in the BSC/M-Cell2/M-Cell6 database. There are two stages to the procedure: S S Preparing for the test. Checking the database equipage.
Commands
The following commands are used during the procedure: NOTE The symbol 0 used in the commands in this procedure is a zero. S S disp_site disp_equipment
Test equipment
The following test equipment is required during the procedure: S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section). CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
372
31st Jul 01
GSM-100-423
Preparing for the test

To prepare for the database equipage checks: 1. 2. 3. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a MCU TTY port using the 9-way to 9-way cable. Start the terminal emulator program at the PC.

To check the database for devices and functions: 1. At the CUST MMI prompt type: disp_site The following message (from the MCU) is displayed:
current site is #
where # = the number of the site logged into. 2. At the CUST MMI prompt type: disp_equipment # where # = the number of the site logged into. A complete list of the equipment and functions in the database is displayed, for example:
GPROC GPROC BSP DRI DRI MSI MMS MMS GCLK KSW CAB SITE RTF RTF 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0

31st Jul 01
68P02901W43-J
373
GSM-100-423
3.
Check the MSI configuration by entering: disp_equipment # MSI 1 0 0 Where: # = site number. A message similar to the following example is displayed:
MSI identifier Cage number Slot number MSI type 1 0 16 0 (0 = MSI)
374
31st Jul 01
GSM-100-423
Checking the 2.048 Mbit/s link

Introduction
The 2.048 Mbit/s link checks verify the integrity of the 2.048 Mbit/s links back to the BSC/MSC. There are two stages to the procedure: S S Preparing for the test. Checking the 2.048 Mbit/s link.
Commands
The following command is used to carry out the procedure: S state
Test equipment
The 2.048 Mbit/s link checks require the following test equipment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section). CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

To set up the equipment to check the 2.048 Mbit/s links: 1. 2. 3. Make sure the site is in call processing mode. Connect the serial A port on the PC to an MCU TTY port using the 9-way to 9-way cable. Start the terminal emulator program at the PC.
The system and the hardware are set up to check the 2.048 Mbit/s links.

31st Jul 01
68P02901W43-J
375
GSM-100-423

To check the 2.048 Mbit/s link: 1. Contact the end point of the 2.048 Mbit/s you want to test, BSC/MSC, and request a loopback on the relevant Digital Distribution Frame (DDF) port. NOTE Repeat for all NIUs and 2 Mbit/s links. S If the 2.048 Mbit/s link has not been installed, perform this test at the DDF in the site. S 2. 3. If No DDF is fitted, do this test at the top of the cabinet
Ascertain the site number, equipment list and MMS configuration. At the CUST MMI prompt type: state # MMS * * * Where: # * * * For example, state 1 MMS 1 0 0 is: location dev/func id dev/func id dev/func id
The system displays the following message from the MCU:

STATUS INFORMATION Device: MMS 1 0 0 Administration state : Unlocked Operational state : Busy Reason code is : 0 Time of last transition : Wed Jan 5 01:43:13 1994 Related Device/Function: Assigned to: END OF STATUS REPORT
S S
If this display shows Unlocked and Busy, then the NIU port (MMS), T43, cabling and the 2.048 Mbit/s link are all good. If the loop is removed and the command re-entered, the result will be Unlocked and Disabled. NOTE The NIU requires a minimum of 20 seconds after receiving these commands before it registers a change in status. If the display continues to show Unlocked and Busy, this may be because: 1. The wrong connection is looped, if the cabling is direct. 2. The MMS may be terminated by a device generating a 2.048 Mbit/s link.
376
31st Jul 01
GSM-100-423
Checking serial connections and alarms

Introduction
The alarm tests check the serial connections and alarm status of M-Cell equipment. There are two stages to the procedure: S S Preparing for the test. Testing the PIX connections using the database external alarm system (EAS).
Test equipment
The serial and alarm tests require the following test equipment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
377
GSM-100-423
Commands
The following commands are used to test the PIX connections: S
enable_alarm

To prepare for the test: 1. 2. 3. 4. Make sure the software download has been completed. Connect the serial A port on the PC to the master MCU using the 9 to 25 way cable. Start the terminal emulator program at the PC. The system displays the CUST MMI prompt. Enter the password at the CUST MMI prompt. The equipment is set up for the test.
Testing the PIX connections

The PIX connections may be tested at a live site using the following test procedure: 1. 2. Apply suitable test plug to PIX input on cabinet top panel. Enter at the CUST MMI prompt on the PC: enable_alarm # where: # = site number. The system displays all 8 alarms. NOTE The display depends on the database settings, that is, whether a fault condition is indicated by a closed loop or an open loop. 3. Remove the test plug. The system clears the alarm display.
378
31st Jul 01
GSM-100-423
Calibrating the MCU (GCLK)

Introduction
This procedure explains how to calibrate the Oven Controlled Crystal Oscillator (OCXO) in the GCLK on the MCU in the M-Cell2 and M-Cell6 product at a BSS site. The calibration procedure is not applicable to the MCU-micro product.
When to calibrate the GCLK

The calibration procedure is to be used on the following occasions: S S When more than one frame slip per hour is observed at the OMC-R (typically more than 34/day). When ever calibration is required. (Display the active alarms for a site - if calibration is required, there will be an alarm stating this). CAUTION This procedure should only be carried out by by fully trained, GSM qualified personnel. Under NO circumstances should this procedure be undertaken, unless all the correct test equipment is readily available. NOTE S S S The command gclk_cal_mode used in this procedure should only be executed at the BTS where the calibration is being carried out. No call processing can occur involving the MCU during calibration mode. Allow a period of 30 minutes to elapse after switching the OCXO power on, to give sufficient time for the unit to reach operating temperature.
Test equipment required

The test equipment required to carry out the GCLK calibration is as follows: S S S S S An IBM compatible personal computer (PC). A 9 to 9 way TTY cable. Caesium or Rubidium clock standard with 1 or 10 MHz output frequency. Universal counter with external reference, for example, the Hewlett Packard model HP5385A or equivalent. BNC to 3way MCU test lead, part number 3086144E01

31st Jul 01
68P02901W43-J
379
GSM-100-423
Setting up for calibration

To prepare the MCU (GCLK) for calibration, carry out the following steps: 1. 2. 3. 4. 5. Connect the serial A port of the PC to the MCU TTY port using the 9-way to 9-way TTY cable. Start the terminal emulator program. Connect the output from the 10 MHz standard to the reference input of the frequency counter, select external standard. Set the frequency gate time to 10 seconds and the display to 10 significant digits. Connect the test cable extracting the 8 kHz output signal from the front of the MCU to the input of the counter. Pin 3 Earth (top pin) Pin 1 8 kHz signal (bottom pin) Figure 3-8 illustrates how the equipment is to be connected to the unit under calibration.
MCU TTY
MCU 8 kHz Out
8000.000000
10 MHz REFERENCE UNIVERSAL COUNTER
Figure 3-8 GCLK calibration - test connections
380
31st Jul 01
GSM-100-423
Test Procedure
CAUTION This procedure should only be carried out by by fully trained, GSM qualified personnel. Under NO circumstances should this procedure be undertaken, unless all the correct test equipment is readily available. NOTE S S No call processing can occur involving the MCU during calibration mode. The command gclk_cal_mode used in this procedure should only be executed at the BTS where the calibration is being carried out.
1.
At the MMIRAM 1015 prompt type: gclk_cal_mode The gclk_cal_mode command is used to tell the sync function and MCU software that a calibration is to be performed. NOTE The gclk_cal_mode command can only be executed at M-Cell sites, outside of sysgen mode. The command is NOT allowed on a Master MCU when a Standby MCU is available. The system will prompt for the following verification when the command is executed:
Site <Local site number> starting GCLK CALIBRATION MODE. If this is a single MCU site, the site will be down until calibration is complete. Are you sure (y=yes, n=no)?
If the user replies with anything other than y, the command is aborted. If the user replies y, the MCU will begin calibration mode. 2. The user will then be prompted with the following:
Frequency Counter Connected, Enter
when ready, or
to abort test.
If the user replies with anything other than y, the command is aborted, and the calibration mode exited. NOTE Allow a period of 30 minutes to elapse after switching the OCXO power on, to give sufficient time for the unit to reach operating temperature. 3. Adjust the OCXO control voltage using the +/ and 0 to 3 keys until the measured frequency is exactly 8000.000000 Hz on the frequency counter. The values entered here, change the frequency by varying degrees. For example: +0 will increase the output by a small amount. +1 will increase the frequency by approximately 10 times. +2 will increase the frequency by approximately 100 times. +3 will increase the frequency by approximately 1000 times.
The above values are not exact as every OCXO has a different gain, this method gives sufficient control to pull-in the frequency within a short time.

31st Jul 01
68P02901W43-J
381
GSM-100-423
4.
A typical sequence of numbers may look as follows:

Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >3 (7.99999898) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+3 (8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >0 (8.00000019 - 8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >2 (8.00000004) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+2 (8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >1 (8.00000018) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >2 (8.00000002 -8.00000003) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >1 (8.000000--) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+0 (8.000000-) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+0 (8.00000000)
5.
Save the results by typing s that is:

Enter a to abort, s to save, +(0..3) to inc, (0..3) to dec >s CAL OFFSET is 23654 DAC bits.
After calibration, the MCU applies a set of voltages to the DAC that feeds the OCXO, this requires the user to input the corresponding output frequency. This is because the OCXO frequency V voltage characteristic is not linear, and by taking readings across a range of DAC voltages, the MCU can make adjustments for non-linearity. 6. To calibrate the OCXO gain, enter the measured frequency value from the counter after the value has settled in response to the MMI prompts. NOTE When taking frequency measurements, ensure that a full gate period elapses from the time the new value is set to reading the counter. This wait may be up to seconds depending on the counter. A typical sequence of frequency measurements may be presented as follows:
Dac set to 1.0 volts, Enter Freq Value or a to abort > 7999.99853 Dac set to 2.0 volts, Enter Freq Value or a to abort > 7999.99915 Dac set to 3.0 volts, Enter Freq Value or a to abort > 7999.99969 Dac set to 4.0 volts, Enter Freq Value or a to abort > 8000.00020 Dac set to 5.0 volts, Enter Freq Value or a to abort > 8000.00070 Dac set to 6.0 volts, Enter Freq Value or a to abort > 8000.00122 Dac set to 7.0 volts, Enter Freq Value or a to abort > 8000.00176 Calibration Gain 3.865560e-01 SYNC>
This completes the calibration procedure. The MCU will now automatically reset. If the calibration is unsucessful the following message will be displayed:
Computed Gain > Max WILL RETRY GAIN
Repeat step 6 to calibrate the OCXO. If the unit fails 3 attempts to calibrate, the unit must be replaced. Installation & Configuration: BSS Optimization 68P02901W43-J
382
31st Jul 01
Chapter 4
Horizonmacro optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 4 Horizonmacro optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Horizonmacro optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test lead calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU VSWR and cellsite offset information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR and cellsite offsite information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test all antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal CTU VSWR and cellsite power calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal VSWR information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 1 (automatic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSWR Method 2 (manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating CTU transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU VSWR and cellsite power calibration for CCBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCB calibration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating Horizonmacro CTU bay level offset tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for bay level calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level calibration for branch 1 RX0A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for RX2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay level repeat for Rx1800 0A on 900 (Dualband) SURF . . . . . . . . . . . . . . . . . . Branch completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Branch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End procedure restoring site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the 2.048 Mbit/s link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 42 42 42 43 43 46 46 47 47 48 49 49 411 411 412 413 414 416 416 418 423 425 425 425 426 427 429 432 433 434 435 435 436 438 439 439 439 439 440 440 442 442 442 442 442 443

31st Jul 01
68P02901W43-J
iii
GSM-100-423
Checking serial connections and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the PIX connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the MCUF (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to calibrate the GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up for calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
444 444 444 445 445 445 446 446 446 446 447 448
iv
31st Jul 01
GSM-100-423
Horizonmacro optimization overview
Horizonmacro optimization overview

Introduction to optimization
This chapter provides information required for the hardware optimization of Horizonmacro equipment. Before starting the hardware optimization, the equipment must be commissioned. Hardware optimization of Horizonmacro equipment consists of the following procedures: S S S S S Checking the antenna VSWR and calibrating the transmit output power. Calibrating the bay level offset tables. Checking the database equipage. Checking the 2.048 Mbit link. Checking the serial connections, power supply module version and alarm status. CAUTION The Horizonmacro and all associated site equipment must be completely optimized before integrating the base site for operation.

31st Jul 01
68P02901W43-J
41
GSM-100-423

Introduction
This section provides information on the test equipment required for the Hardware Optimization procedures in this chapter. The GSM Cellullar Field Installation Tool Kits listed in Chapter 1 may also be necessary. CAUTION Ensure that all test equipment associated with commissioning of Motorola Cellular Base Stations is within calibration date.
Test equipment
Table 4-1 provides details of the test equipment required to perform the Hardware Optimization procedures provided in this chapter: Table 4-1 Hardware optimization equipment Quantity
1
Description PC
Comments To have a serial comms port for sending or configuring messages to the BSC and/or BTS Up to 2GHz PC PLUS or similar software Hewlett Packard E2378A or equivalent 100 W minimum RTLXQ98088 or equivalent
1
1 1 1 1 2 1 1 1 1
Signal generator Commercial terminal emulator software Digital multimeter 30dB attenuator RF adaptor kit N to 7/16 inch adaptor N to N barrel adaptor RF wattmeter with 5W, 10 W 25 W and 50 W elements 2 metres of N to N male coaxial cable 4 metres of N to N male coaxial cable 9-way to 9-way cable 9-way to 9-way cable (CTU only)
Bird model 43 or equivalent Must be calibrated Must be calibrated Compatible with PC to TTY port on CTU/MCUF EQCP/RSS cable, connecting PC to CTU TTY port
2 1
42
31st Jul 01
GSM-100-423
Test lead calibration

To minimize variations in test results, ensure that all appropriate test leads used in Hardware Optimization procedures are calibrated. CAUTION A recognized laboratory must calibrate all test equipment and associated test leads annually. Do not calibrate test equipment or test leads in the field.
Test leads
Connections for a TTY test lead
Figure 4-1 shows the connections for the test lead used in the hardware optimization procedures:
2 3 5 4 6 7 8
4 m LONG SCREENED CABLE TO PC COMMUNICATIONS PORT 9 WAY D-TYPE F
3 2 5
TO CTU CONNECTOR 9 WAY D-TYPE M

31st Jul 01
68P02901W43-J
43
GSM-100-423
Connections for a CTU test lead

Figure 4-2 shows the possible connections for the test lead (3086299N01: EQCP/RSS cable, CTU) used in the CTU Hardware Optimization procedures:
2 3
3 2 9 8
EQCP PINS
RSS PINS
5
SELECTOR SWITCH 4m SCREENED CABLE 9-WAY D-TYPE F CONNECTOR (TO PC COMMUNICATIONS PORT)
9-WAY D-TYPE M CONNECTOR (TO CTU TTY PORT)
Figure 4-2 9-way to 9-way cable connections NOTE TCU-B test lead 3086240N01 may alternatively be used instead of CTU test lead 3086299N01, but adapter (58C86540N01) must then be used to attach the 25-way cable connector to the 9-way CTU port.
44
31st Jul 01
GSM-100-423
Connections for a PIX test lead

Table 4-2 shows pin out details to make a PIX test lead: Table 4-2 Test plug pin connections From PIN 1 2 3 4 5 6 7 8 9 & 10 not used 11 NOTE When making the PIX test lead: Normally open (N/O) PIX inputs should be connected through a 50 ohm resistor. Normally closed (N/C) PIX inputs should be connected through a 50 kohm resistor. Details of N/O and N/C site inputs can be found in the equip_eas file in the site commissioning database 20 21 22 23 24 25 26 27 N/A 29 To PIN

31st Jul 01
68P02901W43-J
45
CTU VSWR and cellsite offset information
GSM-100-423

VSWR and cellsite offsite information
The objective of the VSWR check and output power calibration procedure is to ensure that antenna feeders and connectors are properly terminated and then set the pre-defined maximum transmitter output power at the top of the cabinet. When a radio is manufactured, it undergoes comprehensive transmit and receive calibration procedures. These procedures aim to produce a radio that exhibits a flat frequency response over the GSM band. In the case of the transmitter, this is performed by distributing the channels over three detector groups (the detector being the device that maintains a steady output power level). In the field, the procedure for setting the transmit output power involves using a set of commands called Cell Site Power (CSPWR). During CSPWR the user can trim the cabinet output power to account for any abnormalities that may occur between the CTU and the top of the cabinet. The offset is effectively subtracted from the requested power level, such that for whatever channel is selected, a steady output is maintained at the top of the cabinet. There are two sets of procedures available for checking VSWR and cell site power: S S Normal CTU VSWR and cellsite power calibration. CTU VSWR and cellsite power calibration for CCBs.
The Preparing for test procedure at the end of this section should be completed before attempting the VSWR and cellsite power calibration procedures.
46
31st Jul 01
GSM-100-423
Test stages
Test equipment
The following test equipment is required during the VSWR and output power calibration procedure: S S S S S S S An IBM compatible personal computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter, or equivalent, with 5 W and 50 W Elements. A 9-way to 9-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section). A 9-way to 9-way EQCP/RSS cable. A 7/16 N-type adaptor. A 50 ohm/100 W power attenuator. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
47
GSM-100-423
Commands
The following table lists the commands for the VSWR and output power calibration procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. BSS MMI commands may be entered in upper or lower case. All other commands must be entered in the case shown. BSS MMI command ins_device lock_device unlock_device clear_cal_data CTU command tcu_clock 0 CTU emulator command TEST ACT C BBH ALARM OFF CSPWR HALT C TS <T> CHAN XXX Function Initializes the device, bringing it into service. Prevents the device being used. Frees the device for further use. Clears previously stored calibration data for a specified radio unit on a per DRI basis Function Stops the CTU hunting between link A and link B and forces the CTU to look only at link A. Function Places the CTU in test mode. Activates the Control Processor. Inhibits the BBH alarm. Cell Site Power. Allows the Cell Site power to be set to the maximum output power. Stops the Control Processor. Timeslot set up. Where: <T> = Timeslot No or A = ALL XXX = ARFCN to tune Timeslot to. Timeslot set up. Where: <T> = Timeslot No or A = ALL nn = Attenuation level from max. Used with the CSPWR command to increase the power level by a factor of 0.2dB. Used with the CSPWR command to decrease the power level by a factor of 0.2dB. Used to exit the CSPWR command and store the resulting offset to RAM. Write enables the FLASH EPROM. Used to store the resulting offset in FLASH EPROM. Write protects the FLASH EPROM. Reads Tx offset for FLASH EPROM. Reads Tx offset for RAM. Emulates Combiner Control Processor messaging
TS <T> TXPWR <nn>
U D ESC (key)or CTRL-Y or CTRL-C WRENB SAVE CAL TX WRPTC FR TX MR TX SNDCMB
48
31st Jul 01
GSM-100-423
Test all antennas

VSWR checks ensure correct antenna matching and can prove the serviceability of the antenna. Repeat the procedures for all antennas on site, including receive antennas.
Preparing for test

To prepare for the VSWR check and output power calibration: 1. 2. 3. 4. If CCBs are fitted, set all DIP switches on the CCB control board to zero (this assists programming and checksum calculations). Connect the 9-way to 9-way cable from the PC serial A port to MCU TTY port. At the PC start the terminal emulator program. Change to Level 3 and at the MMI-RAM> prompt type: ins_device # dri A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The radio must be brought into service as there is no Flash EPROM storage of code at the radio control processor level. If a connection to the BSC is not available a PCMCIA commissioning card must be used. 5. Wait for the radio to finish initializing, then type lock_device # dri A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
WARNING An RF hazard exists during DRI transmissions. As one antenna may be connected to a number of DRIs, the lock command must be repeated for all DRIs on the antenna being worked on before connecting the wattmeter. NOTE For ease of calibration, all CTUs in a cell should be initialized and then locked. Always lock the transceiver providing the BCCH last, as this prevents the BCCH being switched to alternate transceivers.

31st Jul 01
68P02901W43-J
49
GSM-100-423
6.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 7. 8. Connect port COM1 on the PC to the TTY Interface port on the transceiver using the 9-way to 9-way RSS cable. At the MMI-ROM prompt type: tcu_clock 0 The system will respond with the following:
WARNING: TCU must be reset to get connection to MCU.
NOTE Do not reset the CTU at this point. The reset is carried out on completion of the CTU VSWR and cellsite power calibration procedure, as detailed in section Restoring the site. 9. Remove the 9-way to 9-way RSS cable from the transceiver and replace it with the 9-way to 9-way EQCP cable.
410
31st Jul 01
GSM-100-423
Normal CTU VSWR and cellsite power calibration

Normal VSWR information
Two methods available for normal VSWR checking are described in this section; one automatic and one manual. The reason for the two methods is as follows:

When typing the CSPWR command at the EQCP prompt, it effectively executes a small script containing the following commands: TS A CHAN 31 TS A CHAN 700 TS A TXP 00 MDLTR UC Set all timeslots to channel 31(CTU900) Set all timeslots to channel 700(CTU1800) Set all timeslots to full power Turn the modulation off
Prior to executing the CSPWR command, it assumes that the synthesizers are in normal mode (not locked), as is the case after the unit is powered up for the first time.

To allow a specific channel to be specified (instead of defaulting to channel 31 or 700) additional commands must be entered, rather than using the CSPWR command. One command sets the appropriate channel and the other switches the CTU output power on and off.

31st Jul 01
68P02901W43-J
411
GSM-100-423

The first method for normal VSWR checking uses automatic channel selection. The CSPWR command automatically selects a midpoint channel number (channel 31 or 700), but if required a manual process can be performed as shown in method 2.
Checking the VSWR

To check the VSWR of the transmission path: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF CSPWR 3. 4. 5. 6. Monitor and record the wattmeter reading (the forward output power). Press ESC or CTRL-Y or CTRL-C Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up. 7. At the EQCP TEST prompt type: CSPWR 8. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1W. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 9. 10. Press ESC or CTRL-Y or CTRL-C At the EQCP TEST prompt type: HALT C 11. Remove the power meter and reconnect antenna. Installation & Configuration: BSS Optimization 68P02901W43-J
412
31st Jul 01
GSM-100-423

The second method for normal VSWR checking allows the manual selection of a channel.
Checking the VSWR (FWD power check)

To check the VSWR of the transmission path through to the antenna: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF 3. Enter the following command: TS A CHAN nnn Where: A nnn 4. is: all timeslots (TS). the specified channel number.
To switch the power on, enter the following command: TS A TXPWR 00 Where: A 00 is: all timeslots (TS). maximum output power
5. 6.
Monitor and record the wattmeter reading (the forward output power). To switch the power off, enter the following command: TS A TXPWR FF Where: A FF is: all timeslots (TS). zero output power
Checking the VSWR (reverse power check)

1. 2. Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up.

31st Jul 01
68P02901W43-J
413
GSM-100-423
3.
To switch the power on, enter: TS A TXPWR 00
4.
Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1 W. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector.
5.
To switch the power off, enter: TS A TXPWR FF
6. 7.
Repeat the forward and reverse power checks for the required number of channels. At the EQCP TEST prompt type: HALT C
8.
Remove the power meter and reconnect the antenna.
Calibrating CTU transmit output power

NOTE Calibration is not required unless the desired configuration is different to the shipped configuration. To calibrate CTU transmit output power: 1. 2. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF 3. At the EQCP prompt type: CSPWR The following message is displayed:
414
31st Jul 01
GSM-100-423
4.
Enter U or D to adjust the CTU Tx power to achieve the appropriate value, as detailed in Table 4-3: Table 4-3 Achievable TX RF power output RF configuration Achievable value CTU900 Twin Duplexed Filter (TDF) 40 W (46.0 dBm) 20 W (43.0 dBm) 8.5 W (39.3 dBm) 20 W (43.0 dBm) CTU1800 32 W (45.1 dBm) 16 W (42.1 dBm) 7 W (38.5 dBm) 16 W (42.1 dBm)
Duplexed Combining bandpass Filter (DCF) Dual-stage Duplexed combining Filter (DDF) Cavity Combining Block All 5.
As U or D is typed, a message similar to the following example, indicating the CTU output power and offset value, is displayed:
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C 6. At the EQCP TEST prompt type: HALT C WRENB SAVE CAL TX WRPTC NOTE The cell site offset can be checked by reading the memory location: Use FR TX to verify writes to FLASH Use MR TX to verify writes to RAM 7. 8. 9. Repeat steps 1 to 6 until all transceivers have been calibrated. Remove the power meter and reconnect the antenna. Use the Restoring the site procedure to return the site to service.

31st Jul 01
68P02901W43-J
415
CTU VSWR and cellsite power calibration for CCBs
GSM-100-423

CCB calibration information
The Cavity Combining Block (CCB) combines the output of up to three radios to a common output, and up to six radios by use of an additional CCB(extension). The CCB(extension) output is an input to the CCB(output) for a single-antenna system. Every transmitted frequency will be attenuated by approximately 3.5 dB for a six cavity system and 2.7 dB in a three cavity system. NOTE All CCB commands are issued via the TTY port on a CTU. A Horizonmacro(indoor) can support up to two CCB modules. There is a minimum of one CCB control board. The CCB control board is located at the front of the CCB beneath a screw down cover. If redundancy of the CCB control board is provided, both CCB modules will be equipped with a CCB control board. The CCB has an address which is defined in the database using the equip_device COMB command. The address can also be displayed by using the disp_equipment COMB command. The CCB control board has a set of eight DIP switches which are used to provide the binary representation of the address defined in the database. These switches have all been set to zero in the Preparing for test procedure. Once the cellsite power has been set the DIP switches should be returned to positions for the address defined in the database.
Example of DIP switch setting

If the combiner address is required to be 75 (hex 4B), the DIP switches will be set as Table 4-4. Table 4-4 Switch settings for example of value 75 Switch On/off for value 75 Binary value of each switch NOTE S S If CCB control board redundancy is supported, the dip switches must be set the same on both CCB control boards. 255 (all on) is not a valid address. 8 off 128 7 on 64 6 off 32 5 off 16 4 on 8 3 off 4 2 on 2 1 on 1
416
31st Jul 01
GSM-100-423
CCB control board details

The CCB control board is equipped with a green LED to indicate the presence of power. If a single CCB control board is used it must be in position 0, or the right of the cabinet when viewed from the front. If two CCB control boards are used, the one mounted on the right, looking from the front, will normally be the master. If this unit fails, the redundant unit will automatically assume control. The initial main/standby relationship is defined from the power connection to the top panel of the cabinet. The two CCB control boards receive power from different pins in the connector, this provides the main/ standby relationship. A fault or problem with the CCB control board is indicated by a red LED, which can be viewed from above. There is not a master/slave relationship as no CCB control board has any influence over the other. It is a main/standby relationship where each CCB control board is equally aware of what is happening with the CCB system, hence the ability for the standby CCB control board to take seamless control in the event of a problem with the main CCB control board. NOTE The CCB control board is sometimes referred to as the Transmit Antenna Transceiver Interface Control Board (TATI Control Board or TCB).

31st Jul 01
68P02901W43-J
417
GSM-100-423
Calibration procedures
The procedures Tuning the CCB cavities, VSWR calibration procedure, Calibrating cellsite power and Parking the CCB cavities should be used for VSWR and cellsite calibration of Horizonmacro cabinets equipped with CTUs and CCB RF combiners. NOTE The four calibration procedures should be completed sequentially, and without pause, for each radio. Failure to do so could result in the associated CCB being parked on the wrong channel.
Tuning the CCB cavities

The following procedure details the steps necessary to tune the cavities in preparation for the VSWR and cellsite power calibration. The CTU radios use channel 31 as the default value associated with the CSPWR command. The procedure should be performed on each radio in turn: 1. 2. 3. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. Connect a PC to the CTU TTY interface port. At the EQCP prompt type: .GSMFW TEST ACT C BBH ALARM OFF 4. Issue the full tuning command to the CCB. To tune cavity 0, at the EQCP TEST prompt: For... CTU900 CTU1800 Where: 02 is the parameter download message ID. 05 is the number of bytes to follow, excluding final checksum. 00 is the CCB address (as set on the DIP switches). 01 is the hex value of the address of the cavity to be tuned. (set for cavity 0) 00 is the channel high byte for CTU900 (02 for CTU1800). 1F is the channel low byte for a CTU 900 set to channel 31 (BC for a CTU1800 set to channel 700). 00 is the power level always 00. 27 is the low byte of the checksum 02 + 05 + 00 + 01 + 00 + 1F + 00 for a CTU900 (C6 is the low byte of checksum 02 + 05 + 00 + 01 + 02 + BC + 00 for a CTU1800). Installation & Configuration: BSS Optimization 68P02901W43-J Type... SNDCMB 02 05 00 01 00 1F 00 27 SNDCMB 02 05 00 01 02 BC 00 C6
418
31st Jul 01
GSM-100-423
The response should occur in under 12 seconds and begin with 01. A typical response, if OK, is:
01 04 00 01 00 00 06
A typical failure response is:

F1 0B 00 A0
followed by a repetition of the input bytes.
Table 4-6 (CTU900) and Table 4-7 (CTU1800) details the tuning commands for all possible cavities.
VSWR calibration procedure

To check the VSWR of the transmission path: 1. At the EQCP TEST prompt type: CSPWR 2. 3. 4. 5. Monitor and record the wattmeter reading (the forward output power). Press ESC or CTRL-Y or CTRL-C Replace the 50 W element in the wattmeter with a 5 W element and reverse the direction on the power meter. Remove the dummy load and connect the power meter through to the antenna. WARNING Full power is transmitted during VSWR checks. Ensure all personnel are clear of the antenna. Do not carry out this check unless antenna installation is complete. CAUTION To reduce the possibility of interference with other users, minimize the time that the radio is powered up. 6. At the EQCP TEST prompt type: CSPWR 7. Monitor and record the reverse power reading indicated on the power meter. NOTE Readings should show reflected (reverse) power of no more than 5% of the forward power at the point of measurement, but less than 1 W. If the ratio of the forward and reverse readings is unacceptable, suspect an improper termination of the antenna feeder and connector. 8. Press ESC or CTRL-Y or CTRL-C

31st Jul 01
68P02901W43-J
419
GSM-100-423
Calibrating cellsite power

To calibrate the cellsite power: 1. At the MMI prompt type: CSPWR The following message is displayed:
2.
Enter U or D to adjust the CTU Tx power to achieve the appropriate value, as detailed in Table 4-5: Table 4-5 Achievable TX RF power output RF configuration Achievable value CTU900 Twin Duplexed Filter (TDF) 40 W (46.0 dBm) 20 W (43.0 dBm) 8.5 W (39.3 dBm) 20 W (43.0 dBm) CTU1800 32 W (45.1 dBm) 16 W (42.1 dBm) 7 W (38.5 dBm) 16 W (42.1 dBm)
Duplexed Combining bandpass Filter (DCF) Dual-stage Duplexed combining Filter (DDF) Cavity Combining Block All 3.
As U or D is typed, a message similar to the following example, indicating the CTU output power and offset value, is displayed:
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C 4. Save the transmit power calibration. At the EQCP TEST prompt type: HALT C WRENB SAVE CAL TX WRPTC
420
31st Jul 01
GSM-100-423
Parking the CCB cavities

To prevent cavity interference park the cavity. To park cavity 0, at the EQCP prompt type: SNDCMB C2 02 00 01 C5 Where: C2 is the park request message ID. 02 is the number of bytes to follow, excluding final checksum. 00 is the CCB address (as set on the DIP switches). 01 is the hex value of the address of the cavity to be tuned. (set for cavity 0) C5 is the low byte of the checksum (C2 + 02 + 00 + 01).
Repeat for remaining cavities

Repeat the procedures Tuning the CCB cavities, VSWR calibration procedure, Calibrating cellsite power and Parking the CCB cavities until all transceivers have tuned the CCB cavity they are connected to and the TX output power has been calibrated. The cavity tuning commands are detailed in Table 4-6 (CTU900) and Table 4-7 (CTU1800). The cavity parking commands are detailed in Table 4-8, and are the same for CTU900 and CTU1800. Table 4-6 CTU900 CCB cavity tuning commands Cavity to be tuned 0 1 2 3 4 5 02 02 02 02 02 02 05 05 05 05 05 05 Cavity tuning command 00 00 00 00 00 00 01 02 04 08 10 20 00 00 00 00 00 00 1F 1F 1F 1F 1F 1F 00 00 00 00 00 00 27 28 2A 2E 36 46
Table 4-7 CTU1800 CCB cavity tuning commands Cavity to be tuned 0 1 2 3 4 5 02 02 02 02 02 02 05 05 05 05 05 05 Cavity tuning command 00 00 00 00 00 00 01 02 04 08 10 20 02 02 02 02 02 02 BC BC BC BC BC BC 00 00 00 00 00 00 C6 C7 C9 CD D5 E5

31st Jul 01
68P02901W43-J
421
GSM-100-423
Table 4-8 CTU900 and CTU1800 CCB cavity parking commands Cavity to be parked 0 1 2 3 4 5 Cavity parking command C2 C2 C2 C2 C2 C2 02 02 02 02 02 02 00 00 00 00 00 00 01 02 04 08 10 20 C5 C6 C8 CC D4 E4
1. 2.
Remove the power meter and reconnect the antenna. Use the Restoring the site procedure to return the site to service.
422
31st Jul 01
GSM-100-423
Restoring the site

After all installed CTUs have been checked and calibrated, perform the following steps to restore the site: This is done in two stages: S S RF output power check. Returning the TCUs to call processing mode.

1. 2. 3. Disconnect antenna. Connect a dummy load to the meter and ensure the meter is fitted with a 50 W element. Connect the meter to the TX output. Return the DIP switches on the CCB control boards to their original positions. Remove the 9-way to 9-way EQCP cable from the TTY port and connect the 9-way to 9-way cable to the MCU MMI port. CAUTION The following step must be carried out to initialize software and so ensure the CTU is correctly brought into service. 4. 5. Press the reset button on the front panel of the CTU. Unlock the DRI under test using the following commands: unlock_device # dri A * state # DRI A * Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
This returns the CTU to the Unlocked_Busy state (confirmed by the state command). 6. 7. Monitor and record the wattmeter reading. This should be the same as the maximum power set up in step 3 of Calibrating cellsite power. Lock the CTU by entering: lock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Repeat steps 5 to 7 for all CTUs.

31st Jul 01
68P02901W43-J
423
GSM-100-423
Returning the CTUs to call processing mode

1. 2. 3. 4. Remove the wattmeter and reconnect the antenna lead to the TX port. Unlock all TCUs tested using the command detailed in step 5 of RF output power check. Remove the 9 to 9-way cable from the MCU MMI port. Inform the OMC the VSWR and cellsite power calibration has been completed.
424
31st Jul 01
GSM-100-423
Calibrating Horizonmacro CTU bay level offset tables

Introduction
Follow this procedure to calibrate the bay level offset tables to compensate for the losses or gains due to preselectors and RF cabling from the antenna inputs at the Horizonmacro to the CTU input. NOTE This procedure applies only to the CTU. The CTU can only be used with software release GSR4 onwards. All units are factory calibrated. This procedure is thus necessary only if one of the following changes occur: S S S S A CTU is replaced. RF front end equipment is changed. The site is reconfigured. High power duplexers are fitted. NOTE The procedures contained in Calibrating Horizonmacro CTU bay level offset tables are to calibrate a single CTU. Repeat the procedures for all CTUs affected by the changes listed above.
Test equipment
The following test equipment is required: S S S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 50 ohm 50 W dummy load. A signal generator (0 to 2 GHz). A 9-way to 9-way MCUF/CTU cable. A 9-way to 9-way EQCP/RSS CTU cable. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
425
GSM-100-423
Commands
The following table details the MMI commands that must be used to carry out the procedure: NOTE 1. The symbol 0 used in the commands in this procedure is a zero. 2. BSS MMI commands may be entered in upper or lower case. All other commands must be entered in the case shown below. CTU passwords are not case sensitive. BSS MMI command ins_device lock_device unlock_device clear_cal_data CTU TTY command TEST BBH ALARM OFF CAL BAY @1/@2 AIC OUT ACT C TS A CHAN # TS A ANT # SYNTH 1 SYNTH NRM SAVE CAL BAY BAYDONE @N HALT C WRENB WRPTC FR BAY MR BAY CTU command tcu_clock 0 Function Initializes the device, bringing it into service Prevents the device being used Frees the device for further use Clears previously stored calibration data for a specified radio unit on a per DRI basis Function Places the CTU into test mode Inhibits the BBH alarm Calibrates the bay level receive equipment Disables automatic intermodulation compensation Activates the Control Processor Sets all timeslots to channel # Sets all timeslots to antenna # Stops synthesizer switching with synthesizer 1 permanently on Enables synthesizer switching into normal working Transfers Bay Level Calibration stored data in RAM to FLASH EPROM Informs control processor that Bay Level Calibration is valid for branch N and sets bay level flag Stops the Control Processor Write enables the FLASH EPROM Write protects the FLASH EPROM Reads cal bay offsets from FLASH EPROM Reads cal bay offsets from RAM Function Stops the CTU hunting between fibre A and fibre B and forces the CTU to look only at fibre A.
426
31st Jul 01
GSM-100-423
Preparation for bay level calibration

The RF path has to be prepared for bay level calibration. The radio has to be reset and locked, a dummy load connected if no antenna and the alarms disabled. Proceed as follows: 1. 2. 3. Connect the 9-way to 9-way MCUF cable from the PC serial A port to MCUF TTY port. At the PC start the terminal emulator program. Change to Level 3 and at the MMI-RAM> prompt type: ins_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE The radio must be brought into service as there is no Flash EPROM storage of code at the radio control processor level. If a connection to the BSC is not available a PCMCIA commissioning card must be used. 4. Wait for the radio to finish initializing, then type: WARNING Failure to lock the cell could result in the BCCH transmitting into, and causing damage to the signal generator. The maintenance engineer could receive RF burns when connecting to the antenna socket. lock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
NOTE For ease of calibration, all CTUs in a cell should be initialized and then locked. Always lock the transceiver providing the BCCH last as this prevents the BCCH being switched to alternate transceivers.

31st Jul 01
68P02901W43-J
427
GSM-100-423
5.
NOTE The clear_cal_data command clears all calibration data out of the CM database. This is required to overide the preserve calibration feature, if enabled. 6. 7. Connect port COM1 on the PC to the TTY Interface port on the radio using the 9-way to 9-way EQCP/RSS cable. At the MMI-ROM prompt type: tcu_clock 0 The system responds with the following:
WARNING: CTU must be reset to get connection to MCU.
8.
If a tx antenna is not conected to the radio under test, connect a 50 ohm 50 W dummy load to the Tx port of the radio under test. CAUTION Ensure that you have entered the tcu_clock 0 command at the RSS MMI-ROM 0000> prompt, as shown in step 7 before entering call processing to avoid EQCP instability at step 3 of Bay level calibration (next procedure).
9. 10.
Switch the 9-way to 9-way EQCP/RSS cable from providing RSS connectivity to providing EQCP connectivity. At the EQCP prompt type: .GSMFW TEST The system responds with the following:
WARNING: The EQCP is now in test mode.
11.
At the EQCP TEST prompt type: BBH ALARM OFF The system responds with the following:
The alarm reporting for the BBH connection is turned off
12.
At the EQCP TEST prompt type: AIC OUT The system responds with the following:
The AIC pad for branch 1 is OUT. The AIC pad for branch 2 is OUT.
428
31st Jul 01
GSM-100-423
Bay level calibration for branch 1 RX0A

Proceed as follows: 1. Connect the output of the signal generator to branch 1 of the antenna port at the top of the Horizonmacro cabinet. NOTE It is important to choose the correct number in the TS If RX path is 0A or 0B of SURF then antenna is TS A If RX path is 1A or 1B of SURF then antenna is TS A If RX path is 2A or 2B of SURF then antenna is TS A A ANT command. ANT 1. ANT 2. ANT 3.
For 900 MHz dual band SURF, If RX path is 1800 0A or 1800 0B of SURF then antenna is TS A ANT 2. The antenna number can also be found by using the disp_equipment # DRI A * 0 command. The number next to antenna_select is the antenna number. 2. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 4-9 (EGSM900) or Table 4-10 (DCS1800) Table 4-9 EGSM900 test frequency table Channel 979 987 995 1003 1011 1019 03 11 19 27 35 Frequency (MHz) 881.001 882.601 884.201 885.801 887.401 889.001 890.601 892.201 893.801 895.401 897.001 Channel 43 51 59 67 75 83 91 99 107 115 123 Frequency (MHz) 898.601 900.201 901.801 903.401 905.001 906.601 908.201 909.801 911.401 913.001 914.601

31st Jul 01
68P02901W43-J
429
GSM-100-423
Table 4-10 DCS1800 test frequencies Channel 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700 3. Frequency (MHz) 1711.001 1712.601 1714.201 1715.801 1717.401 1719.001 1720.601 1722.201 1723.801 1725.401 1727.001 1728.601 1730.201 1731.801 1733.401 1735.001 1736.601 1738.201 1739.801 1741.401 1743.001 1744.601 1746.201 1747.801 Channel 708 716 724 732 740 748 756 764 772 780 788 796 804 812 820 828 836 844 852 860 868 876 883 Frequency (MHz) 1749.401 1751.001 1752.601 1754.201 1755.801 1757.401 1759.001 1760.601 1762.201 1763.801 1765.401 1767.001 1768.601 1770.201 1771.801 1773.401 1775.001 1776.601 1778.201 1779.801 1781.401 1783.001 1784.401
At the EQCP TEST prompt type: ACT C The system responds with the following:
The EQCP is in the Call Processing state Warning: After locking carrier down, enter CTU_CLOCK 0 command at RSS MMI-ROM 0000> prompt before entering Call Processing to avoid EQCP instability.
4.
At the EQCP TEST prompt type: TS A ANT 1 The system responds with the following:
All timeslots are under user control.
430
31st Jul 01
GSM-100-423
5.
At the EQCP TEST prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 4-9 or Table 4-10.
The system responds with the following:

The data for all timeslots has been changed.
6.
At the EQCP TEST prompt type: SYNTH 1 The system responds with the following:
Synthesizer 1 is enabled.
7.
At the EQCP TEST prompt type: CAL BAY @1 The system responds with the following:
BAY LEVEL OFFSET = XX
Where 8.
XX
= The hex value of the bay level reading.
At the EQCP TEST prompt type: SYNTH NRM The system responds with the following:
The system is under real time control.
9.
Set the signal generator to the next frequency and repeat steps 5 and 6 for all the test frequencies in Table 4-9 or Table 4-10.

31st Jul 01
68P02901W43-J
431
GSM-100-423

Continue the bay level calibration procedure for the second antenna port as follows: 1. 2. 3. Connect the output of the generator to RX1A. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 4-9 or Table 4-10. At the EQCP TEST prompt type: TS A ANT 2 4. At the EQCP TEST prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 4-9 or Table 4-10.
5.
At the EQCP TEST prompt type: SYNTH 1 CAL BAY @1 SYNTH NRM
6.
432
31st Jul 01
GSM-100-423

Continue the bay level calibration procedure for the third antenna port as follows: 1. 2. 3. Connect the output of the generator to RX2A. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 4-9 or Table 4-10. At the EQCP TEST prompt type: TS A ANT 3 4. At the EQCP TEST prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 4-9 or Table 4-10.
5.
6.

31st Jul 01
68P02901W43-J
433
GSM-100-423
Bay level repeat for Rx1800 0A on 900 (Dualband) SURF

For the 900 MHz dualband SURF modules, two additional antenna ports, 1800 0A and 1800 0B, are available for 1800 MHz use. Continue the bay level calibration procedure for the branch 1 1800 antenna port as follows: 1. 2. 3. Connect the output of the generator to RX1800 0A. Set the signal generator to provide 65.0 dBm at the antenna port and to the first channel test frequency shown in Table 4-10. At the EQCP TEST prompt type: TS A ANT 2 4. At the EQCP TEST prompt type: TS A CHAN # Where: # is: the channel number of the selected frequency, as shown in Table 4-10.
5.
6.
434
31st Jul 01
GSM-100-423
Branch completion
To complete the bay level procedure for the branch: 1. At the EQCP TEST prompt type: BAYDONE @1 The system responds with the following:
BAY LEVEL CALIBRATION IS DONE
2.
At the EQCP TEST prompt type: HALT C The system responds with the following:
The EQCP is in the Active Standby state
3.
At the EQCP TEST prompt type: WRENB The system responds with the following:
Device OK. Flash is now write enabled.
4.
At the EQCP TEST prompt type: SAVE CAL BAY The system responds with the following:
Save Cal Completed.
5.
At the EQCP TEST prompt type: WRPTC The system responds with the following:
Flash is now write protected.
Branch 2
Repeat the procedures Bay level calibration branch 1 RX0A, Bay level repeat for RX1A, Bay level repeat for RX2A and Bay level repeat for RX1800 0A for branch 2 by connecting to RX0B, RX1B, RX2B and RX1800 0B alternately. Enter @2 instead of @1 in the cal bay and baydone commands.

31st Jul 01
68P02901W43-J
435
GSM-100-423
The following procedure should be used to check the bay level calibration has been successful. 1. To verify that the bay level offset values have been stored in EPROM, use the read command with the required offset table location as an argument. FR BAY MR BAY To verify writes to FLASH To verify writes to RAM Table 4-11 CTU frequency offset addresses Bay Level Calibration Storage Branch 1 Valid Flag Branch 2 Valid Flag Branch 1 Checksum Branch 2 Checksum Bay Level Offsets For Branch 1 Antenna 1 Bay Level Offsets For Branch 1 Antenna 2 Bay Level Offsets For Branch 1 Antenna 3 Bay Level Offsets For Branch 2 Antenna 1 Bay Level Offsets For Branch 2 Antenna 2 Bay Level Offsets For Branch 2 Antenna 3 Flash Address A000700 A000703 A000706 A000709 A00070C A00074D A00074E A00078F A000790 A0007D1 A0007D2 A000813 A000814 A000855 A000856 A000897
CTU900s cover the EGSM range and store offsets in 22 locations in each memory area per antenna per branch. CTU1800s cover the DCS range and store offsets in 47 locations in each memory area per antenna per branch. NOTE Each location consists of three bytes. For example, the branch 1 valid flag data is stored in address locations A000700, A000701 and A000702. 2. The following is an example of the first line of the FLASH BAY LEVEL OFFSET table when using the FR BAY command, and a description of the fields displayed:
BR1 BR2 flag 000001 BR1 Cksum 000595 BR2 Cksum 000595 BL offset 000060 BL offset 000002 BL offset 000005 BL offset 000002
Address
A000700
000001
The remaining rows of the table contain BL offset values
436
31st Jul 01
GSM-100-423
3.
If the bay level calibration is successful, each appropriate table location will contain valid offsets, and not the factory default of 80. NOTE The presence of 80 will result in error alarm DRI 218: Invalid Transceiver Calibration Data being reported when the unit is unlocked. However, unused data columns in a site configuration may have value 80; no alarm will be reported as such table locations are inappropriate to the site.
4.
If the value 80 is present it indicates an unsuccessful calibration procedure or an uncalibrated antenna port. The calibration procedure will have to be repeated after checking the configuration and RF cables. NOTE Any value other than 80 is a valid offset, from 81 to FF, and 00 to 7F. Only the value 80 requires investigation.

31st Jul 01
68P02901W43-J
437
GSM-100-423

After the bay level calibration procedure is completed, restore the site by the following: 1. 2. 3. Remove the signal generator and dummy load and refit the site RF cables. Remove the 9-way to 9-way cable from the TTY INTERFACE port on the CTU. Connect the 9-way to 9-way cable from the PC serial A port to a MCUF TTY port. CAUTION The following step must be carried out to initialize software and so ensure the CTU is correctly brought into service. 4. 5. Press the reset button on the front panel of the CTU. Type: unlock_device # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
The CTU is now in the unlocked_busy state. 6. Type: disp_act_alarm # dri A * 0 Where: # A * is: the number of the site logged into. the antenna/relative cell number (0 to 5). DRI number on the antenna.
Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, redo the whole bay level calibration procedure 7. Remove the 9-way to 9-way cable from the MCUF TTY port.
438
31st Jul 01
GSM-100-423

Introduction
The database equipage checks determine what devices and functions have been equipped in the BSC/Horizonmacro database. There are two stages to the procedure: S S Preparing for the test. Checking the database equipage.
Commands
The following commands are used during the procedure: NOTE The symbol 0 used in the commands in this procedure is a zero. S S disp_site disp_equipment
Test equipment
The following test equipment is required during the procedure: S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in Figure 4-1 of the Test equipment, leads and plugs section). CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

31st Jul 01
68P02901W43-J
439
GSM-100-423

To prepare for the database equipage checks: 1. 2. 3. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a MCUF TTY port using the 9-way to 9-way cable. Start the terminal emulator program at the PC.

To check the database for devices and functions: 1. At the CUST MMI prompt type: disp_site The following message (from the MCU) is displayed:
current site is # where # = the number of the site logged into.
2.
At the CUST MMI prompt type: disp_equipment # where # = the number of the site logged into. A complete list of the equipment and functions in the database is displayed, for example:
GPROC GPROC BSP DRI DRI MSI MMS MMS GCLK KSW CAB SITE RTF RTF
0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
440
31st Jul 01
GSM-100-423
3.
To Check the MSI configuration at the CUST MMI prompt type: disp_equipment # MSI 1 0 0 Where: # = site number. A message similar to the following example is displayed:
MSI identifier 1 Cage number 0 Slot number 16 MSI type 0
(0 = MSI)

31st Jul 01
68P02901W43-J
441
GSM-100-423

Introduction
The 2.048 Mbit/s link checks verify the integrity of the 2.048 Mbit/s links back to the BSC/MSC. There are two stages to the procedure: S S Preparing for the test. Checking the 2.048 Mbit/s link.
Commands
The following command is used to carry out the procedure: S state
Test equipment
The 2.048 Mbit/s link checks require the following test equipment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in Figure 4-1 of the Test equipment, leads and plugs section). CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.

To set up the equipment to check the 2.048 Mbit/s links: 1. 2. 3. Make sure the site is in call processing mode. Connect the serial A port on the PC to an MCUF TTY port using the 9-way to 9-way cable. Start the terminal emulator program at the PC.
The system and the hardware are set up to check the 2.048 Mbit/s links.
442
31st Jul 01
GSM-100-423

To check the 2.048 Mbit/s link: 1. Contact the end point of the 2.048 Mbit/s you want to test, BSC/MSC, and request a loopback on the relevant Digital Distribution Frame (DDF) port. NOTE Repeat for all NIUs and 2 Mbit/s links. S If the 2.048 Mbit/s link has not been installed, perform this test at the DDF in the site. S 2. 3. If no DDF is fitted, do this test at the top of the cabinet
Ascertain the site number, equipment list and MMS configuration. At the CUST MMI prompt enter: state # MMS * * * Where: # * * * For example: state 1 MMS 1 0 0 is: location dev/func id dev/func id dev/func id
The system displays the following message from the MCU:

STATUS INFORMATION Device: MMS 1 0 0 Administration state : Unlocked Operational state : Busy Reason code is : 0 Time of last transition : Wed Jan 5 01:43:13 1994 Related Device/Function: Assigned to: END OF STATUS REPORT
If this display shows Unlocked and Busy, then the NIU port (MMS), T43, cabling and the 2.048 Mbit/s link are all good. If the loop is removed and the command re-entered, the result will be Unlocked and Disabled. NOTE The NIU requires a minimum of 20 seconds after receiving these commands before it registers a change in status. If the display continues to show Unlocked and Busy, this may be because: 1. The wrong connection is looped, if the cabling is direct. 2. The MMS may be terminated by a device generating a 2.048 Mbit/s link.

31st Jul 01
68P02901W43-J
443
GSM-100-423

Introduction
The alarm tests check the serial connections and alarm status of M-Cell equipment. There are two stages to the procedure: S S Preparing for the test. Testing the PIX connections using the database external alarm system (EAS).
Test equipment
The serial and alarm tests require the following test equipment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (a diagram of this cable is provided in Figure 4-1 of the Test equipment, leads and plugs section. CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory. Test equipment and test leads must not be calibrated in the field. Do not optimize Motorola Cellular Base Stations with test equipment that is beyond its calibration due date. Allow test equipment to warm up for 30 minutes before use.
444
31st Jul 01
GSM-100-423
Commands
The following commands are used to test the PIX connections: S enable_alarm

To prepare for the test: 1. 2. 3. 4. Make sure the software download has been completed. Connect the serial A port on the PC to the master MCUF using the 9-way to 9way cable. Start the terminal emulator program at the PC. The system displays the CUST MMI prompt. Enter the password at the CUST MMI prompt. The equipment is set up for the test.
Testing the PIX connections

The PIX connections may be tested at a live site using the following test procedure: 1. Apply suitable test plug to PIX input on cabinet top panel. NOTE Wait at least six seconds before continuing the testing. The time is required to allow polling to detect the presence of the test plug. 2. At the CUST MMI prompt type: enable_alarm # Where: # is: site number
The system displays all 8 alarms. NOTE The display depends on the database settings, that is, whether a fault condition is indicated by a closed loop or an open loop. 3. Remove the test plug. The system clears the alarm display.

31st Jul 01
68P02901W43-J
445
Calibrating the MCUF (GCLK)
GSM-100-423

Introduction
This procedure explains how to calibrate the Oven Controlled Crystal Oscillator (OCXO) in the GCLK on the MCUF in the Horizonmacro product at a BSS site.
When to calibrate the GCLK

The calibration procedure is to be used on the following occasions: S S When more than one frame slip per hour is observed at the OMC-R (typically more than 34/day). When ever calibration is required. (Display the active alarms for a site - if calibration is required, there will be an alarm stating this). CAUTION This procedure should only be carried out by by fully trained, GSM qualified personnel. Under NO circumstances should this procedure be undertaken, unless all the correct test equipment is readily available. NOTE S S S The command gclk_cal_mode used in this procedure should only be executed at the BTS where the calibration is being carried out. No call processing can occur involving the MCU during calibration mode. Allow a period of 30 minutes to elapse after switching the OCXO power on, to give sufficient time for the unit to reach operating temperature.
Test equipment required

The test equipment required to carry out the GCLK calibration is as follows: S S S S S An IBM compatible personal computer (PC). A 9-way to 9-way TTY cable. A Caesium or Rubidium clock standard with 1 or 10 MHz output frequency. A Universal counter with external reference, for example, the Hewlett Packard model HP5385A or equivalent. A BNC to 3-way MCU test lead, part number 3086144E01 (see Figure 3-3).
446
31st Jul 01
GSM-100-423
Setting up for calibration

To prepare the MCUF (GCLK) for calibration, carry out the following steps: 1. 2. 3. 4. 5. Connect the serial A port of the PC to the MCU TTY port using the 9-way to 9-way TTY cable. Start the terminal emulator program. Connect the output from the 10 MHz standard to the reference input of the frequency counter, select external standard. Set the frequency gate time to 10 seconds and the display to 10 significant digits. Connect the test cable extracting the 8 kHz output signal from the front of the MCUF to the input of the frequency counter. Pin 3 Earth (top pin) Pin 1 8 kHz signal (bottom pin) Figure 4-3 illustrates how the equipment is to be connected to the unit under calibration.
MCU TTY
MCU 8 kHz Out
8000.000000
10 MHz REFERENCE UNIVERSAL COUNTER
Figure 4-3 GCLK calibration - test connections

31st Jul 01
68P02901W43-J
447
GSM-100-423
Test Procedure
CAUTION This procedure should only be carried out by by fully trained, GSM qualified personnel. Under NO circumstances should this procedure be undertaken, unless all the correct test equipment is readily available. NOTE S S No call processing can occur involving the MCUF during calibration mode. The command gclk_cal_mode used in this procedure should only be executed at the BTS where the calibration is being carried out.
1.
At the MMIRAM 1015 prompt type: gclk_cal_mode The gclk_cal_mode command is used to tell the sync function and MCUF software that a calibration is to be performed. NOTE The gclk_cal_mode command can only be executed at Horizonmacro sites, outside of sysgen mode. The command is NOT allowed on a Master MCUF when a Standby MCUF is available. The system will prompt for the following verification when the command is executed:
Site <local site number> starting GCLK CALIBRATION MODE. If this is a single MCU site, the site will be down until calibration is complete. Are you sure (y=yes, n=no)? y
If the user replies with anything other than y, the command is aborted. If the user replies y, the MCUF will begin calibration mode. 2. The user will then be prompted with the following message displayed:
Frequency Counter Connected, Enter y when ready, or a to abort test
If the user replies with anything other than y, the command is aborted, and the calibration mode exited. NOTE Allow a period of 30 minutes to elapse after switching the OCXO power on, to give sufficient time for the unit to reach operating temperature. 3. Adjust the OCXO control voltage using the +/ and 0 to 3 keys until the measured frequency is exactly 8000,000000 Hz. The values entered here, change the frequency by varying degrees. For example: +0 will increase the output by a small amount. +1 will increase the frequency by approximately 10 times. +2 will increase the frequency by approximately 100 times. +3 will increase the frequency by approximately 1000 times.
The above values are not exact as every OCXO has a different gain, this method gives sufficient control to pull-in the frequency within a short time. Installation & Configuration: BSS Optimization 68P02901W43-J
448
31st Jul 01
GSM-100-423
4.
A typical sequence of numbers may look as follows:

Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >3 (7.99999898) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+3 (8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >0 (8.00000019 - 8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >2 (8.00000004) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+2 (8.00000020) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >1 (8.00000018) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >2 (8.00000002 -8.00000003) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >1 (8.000000--) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+0 (8.000000-) Enter a to abort. s to save, +(0..3) to inc, (0..3) to dec >+0 (8.00000000)
Save the results by typing s that is:

Enter a to abort, s to save, +(0..3) to inc, (0..3) to dec >s
A typical response to entering s is:

CAL OFFSET is 23654 DAC bits.
After calibration, the MCUF applies a set of voltages to the DAC that feeds the OCXO, this requires the user to input the corresponding output frequency. This is because the OCXO frequency V voltage characteristic is not linear, and by taking readings across a range of DAC voltages, the MCU can make adjustments for non-linearity. 5. To calibrate the OCXO, gain, enter the measured frequency value from the counter after the value has settled in response to the MMI prompts. NOTE When taking frequency measurements, ensure that a full gate period elapses from the time the new value is set to reading the counter. This wait may be up to seconds depending on the counter. A typical sequence of frequency measurements may be presented as follows:
Dac set to 1.0 volts, Enter Freq Value or a to abort > 7999.99853 Dac set to 2.0 volts, Enter Freq Value or a to abort > 7999.99915 Dac set to 3.0 volts, Enter Freq Value or a to abort > 7999.99969 Dac set to 4.0 volts, Enter Freq Value or a to abort > 8000.00020 Dac set to 5.0 volts, Enter Freq Value or a to abort > 8000.00070 Dac set to 6.0 volts, Enter Freq Value or a to abort > 8000.00122 Dac set to 7.0 volts, Enter Freq Value or a to abort > 8000.00176 Calibration Gain 3.865560e-01 SYNC>

31st Jul 01
68P02901W43-J
449
GSM-100-423
6.
On completion ensure that the Calibration Gain is between 0 and 1.5. Values other than this may indicate a poor OCXO, or an error in performing the procedure. The most common error is in reading the counter when locating the decimal point by eye. Calibration must be performed a second time if the Calibration Gain value is not in the range specified. If it fails the second time with the same or similar value, the OCXO, may be operating outside of the Motorola specification. If this occurs, the MCU is deemed faulty and should be replaced. Otherwise the calibration procedure is complete. NOTE The MCUF will be reset when the calibration is complete.
450
31st Jul 01
Chapter 5
Preserve calibration procedure

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 5 Preserve calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preserve transceiver calibration feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preserve calibration introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibration data overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the preserve feature at the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the preserve feature at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a transceiver using preserved data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsequent replacement of calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a transceiver using new data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the calibration data in CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 51 52 52 52 53 53 54 55 56

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Preserve transceiver calibration feature

Preserve calibration introduction
The preserve transceiver calibration feature uses commands to store, display and clear calibration data. This feature is used on busy systems where there is a need to replace a transceiver quickly and thus reduce system down time during peak hours. NOTE After the transceiver has been replaced, it will still be necessary to revisit the site at an off-peak period, to carry out bay level and CSPWR calibration to fully optimize the hardware. The calibration procedure for a specific transceiver is in the appropriate section in this manual. The preserve transceiver calibration feature applies only to BTS4/5/6, ExCell, TopCell, M-Cellt2, M-Cellt6 and Horizonmacro equipment.
Calibration data overview

Once activated with the store_cal_data command, the RX bay level data and the TX CSPWR offset data, referred to as calibration data, is copied from the RAM on the transceiver. This calibration data is stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid. When a transceiver is replaced, the calibration data stored in the CM database will be downloaded into the RAM of the replacement transceiver. The data will also be stored in the non-volatile transceiver memory if the new transceiver is a CTU, TCU, SCU or DRCU. NOTE Update of non-volatile transceiver memory from CM database does not occur for DRCUII or DRCU3. If the clear_cal_data command is used, both the CM database at the BSC and the local copy of the CM database at the BTS will be cleared of current calibration data for the specified transceiver. Data is then automatically copied from the RAM of a replacement transceiver, into the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid. NOTE If the store_cal_data is activated, there is no need to reactivate it, unless a new database is downloaded. Activation of this feature creates a prompt at the OMC-R to update the BSC CM database copies that it holds. A 218. DRI: Invalid Transceiver Calibration Data alarm stops the CM database being updated with calibration data.

31st Jul 01
68P02901W43-J
51
GSM-100-423
Test equipment
The following equipment is needed to carry out this procedure: S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 9-way cable (Horizon and M-Cell BTS only). A 9-way to 25-way cable (BTS4, 5, 6 and BSC only).
Commands
The following commands are required to carry out this procedure: BTS Command lock_device unlock_device OMC/BSC Command store_cal_data Function Prevents the device being used Enables the device to be used Function Stores calibration data for all transceivers into the master CM database at the BSC, which is then used to update the CM database copy at the BTS. When transceiver is locked: Displays calibration data in the CM database for the specified transceiver. When transceiver is unlocked: Displays calibration data in the RAM of the specified transceiver. clear_cal_data Clears calibration data in CM database at BSC and BTS for a specified transceiver.
disp_cal_data
NOTE If there is no RSL from the BTS to the BSC then the command will not be executed by the BSC, as the BSC has no knowledge of the command being entered. All calibration data will be stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid.
Activating the preserve feature at the OMC-R

Before starting the preserve calibration procedure, consult the site specific documentation to determine the BSC/BTS configuration and cage slot allocation. Proceed as follows: 1. 2. At the operations and maintenance centre (OMC-R) man-machine interface (MMI), log in to the required base site controller (BSC). To initiate the preserve feature type: store_cal_data <site_id> All calibration data will be stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid. Installation & Configuration: BSS Optimization 68P02901W43-J
52
31st Jul 01
GSM-100-423
Activating the preserve feature at the BSC

The preserve feature can be activated at the BSC as follows: 1. 2. 3. 4. Connect the 9-way to 25-way cable from the PC serial A port to a GPROC TTY port. At the PC start the terminal emulator program. At the CUST/MMI prompt, enter the appropriate change command and passwords. At the BSP MMI prompt type: store_cal_data all All calibration data will be stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid.
Replacing a transceiver using preserved data

To replace a transceiver using preserved calibration data, proceed as follows: 1. Lock the DRI of the transceiver to be replaced as follows: lock_device <location> DRI <device_id1> <device_id2> [<device_id3>] 2. 3. Replace the transceiver with the new transceiver. Unlock the DRI of the transceiver as follows: unlock_device <location> DRI <device_id1> <device_id2> [<device_id3>] The calibration data stored in the CM database will be downloaded into the RAM of the new transceiver. The data will also be stored into the non-volatile transceiver memory if the new transceiver is a CTU, TCU, SCU or DRCU. Update of non-volatile transceiver memory from CM database does not occur for DRCUII or DRCU3. NOTE After the transceiver has been replaced, it will still be necessary to revisit the site at an off-peak hour, to carry out bay level and CSPWR calibration to fully optimize the hardware.

31st Jul 01
68P02901W43-J
53
GSM-100-423
Subsequent replacement of calibration data

To replace the preserved calibration data with new calibration data, proceed as follows: 1. Lock the DRI of the transceiver as follows: lock_device <location> DRI <device_id1> <device_id2> [<device_id3>] 2. At the OMC or BSC, clear the previously stored calibration from the CM database for the specified transceiver: clear_cal_data <location> DRI <device_id1> <device_id2> [<device_id3>] 3. Confirm the data has been cleared from the CM database for the specified transceiver: disp_cal_data <location> DRI <device_id1> <device_id2> [<device_id3>] The response should be:
NO DATA AVAILABLE
4. 5.
Carry out bay level and CSPWR procedures, as described in the relevant section of this manual. Unlock the DRI of the transceiver as follows: unlock_device <location> DRI <device_id1> <device_id2> [<device_id3>]
This calibration data will be stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid.
54
31st Jul 01
GSM-100-423
Replacing a transceiver using new data

Replace a transceiver using immediate new calibration data as follows: 1. Lock the DRI of the transceiver to be replaced as follows: lock_device <location> DRI <device_id1> <device_id2> [<device_id3>] 2. At the OMC or BSC, clear the previously stored calibration from the CM database for the specified transceiver: clear_cal_data <location> DRI <device_id1> <device_id2> [<device_id3>] 3. Confirm the data has been cleared from the CM database for the specified transceiver: disp_cal_data <location> DRI <device_id1> <device_id2> [<device_id3>] The response should be:
NO DATA AVAILABLE
4. 5. 6.
Replace the transceiver with the new transceiver. Carry out bay level and CSPWR procedures, as described in the relevant section of this manual. Unlock the DRI of the transceiver as follows: unlock_device <location> DRI <device_id1> <device_id2> [<device_id3>]
This calibration data will be stored in the master CM database at the BSC, which is then used to update the CM database copy at the BTS only if the data is valid.

31st Jul 01
68P02901W43-J
55
GSM-100-423
Viewing the calibration data in CM database

View the current calibration data in the CM database as follows: 1. Lock the DRI of the transceiver to be checked: lock_device <location> DRI <device_id1> <device_id2> [<device_id3>] 2. Display the CM database calibration data. disp_cal_data <location> DRI <device_id> <device_id2> [<device_id3>] The response should be:
DRI ID: (device id1) (device id2) (device id3) Data read from CM database Calibration data (all values in hex) Transmit power offset = Receive system data: Antenna Number 1 2 3 4 5 6 (CSPWR offset)
Six columns of bay level offset calibration data will be displayed as explained below: Table 5-1 Explanation of offset calibration data presentation per row Column: is branch: and antenna: 1 1 1 2 1 2 3 1 3 4 2 1 5 2 2 6 2 3
The number of rows of offset calibration data are as follows: S S S S GSM900 16 values EGSM900 22 values DCS1800 47 values PCS1900 37 values
56
31st Jul 01
Chapter 6
M-Cellcity/M-Cellcity+ optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 6 M-Cellcity/M-Cellcity+ optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cellcity/M-Cellcity+ optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment and test leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCMCIA card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download from PCMCIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCMCIA download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking VSWR and output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the transmit output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCCH swap procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download from BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download Procedure with example results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site status check procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1/T1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fitting chassis bottom cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating an MCU-m GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 62 62 63 64 65 65 65 66 66 66 66 67 612 612 612 613 615 615 622 625 625 625 625 625 627 627 627 627 627 628 628 629 629 629 629

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Optimization overview
This chapter provides information required for the optimization of an M-Celltcity/M-Celltcity+ enclosure. NOTE It is likely that some equipment at the site may not be produced by Motorola. Examples of such equipment may include battery chargers, power supplies, and antennas. Refer to site specific documentation and the vendor instructions provided with non-Motorola equipment. Before starting the optimization, the site should be prepared and the equipment installed as detailed in the appropriate service manual GSM-201-020 Service Manual M-Cellcity and M-Cellcity+ and the site specific documentation. NOTE Whenever there is a reference to M-Cellcity, the procedure is also applicable to M-Cellcity+ except where stated. If the E1/T1 link is not active at the time an M-Cellcity is commissioned, it will not be possible to download code directly from the BSC. Optimization of an M-Cellcity enclosure consists of the following sections: Section Test equipment & test leads. Checking the E1/T1 link. Code download. Checking the VSWR and transmit output power. Checking the database equipage. Description Details of the equipment necessary to perform commissioning. This procedure verifies the integrity of the E1/T1 link back to the BSC. Downloading a BSS software load for testing purposes. This procedure verifies the transmitter output power is correct. Verifying that the just loaded software contains the necessary features and functions.

31st Jul 01
68P02901W43-J
61
Test equipment and test leads
GSM-100-423

Introduction
The test equipment listed in Table 6-1 is required to carry out the optimization tests in this chapter. The tool kits listed in the appropriate service manual GSM-201-020 Service Manual M-Cellcity and M-Cellcity+ may also be necessary. Calibrate all test leads before using them in the procedures given in this chapter. This minimizes variations in test results. CAUTION A recognised laboratory must calibrate all test equipment annually. Do not calibrate test equipment or test leads in the field. Ensure that all test equipment associated with optimization of Motorola Cellular Base Stations is within calibration date.
62
31st Jul 01
GSM-100-423
Test equipment
Table 6-1 Required optimization test equipment Quantity
1
Description IBM compatible 486 DX2 or DX4 portable Personal Computer (PC).
Comments The basic requirements are: S TFT colour screen. S S 170 Mbyte hard drive (minimum). Minimum 4 Mbyte RAM (minimum) or 8 Mbyte (recommended). 3.5 inch floppy drive. Serial port. CD-ROM drive (recommended). PCMCIA (Type 2) compatible slot. Windows 3.1 loaded and running in 386 enhanced mode. Battery power.
S S S S S
S
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 6 1
Signal generator Rubidium standard Frequency counter Commercial terminal emulator software Digital multimeter RF 50 ohm dummy load Transportable cellphone ESD protection kit RF adaptor kit N to 7/16 adaptor N to N adaptor RF wattmeter with 5W, 10 W, 25 W Bird model 43P or equivalent and 50 W elements 2 metre N to N male coaxial cable 4 metre N to N male coaxial cable 9-way to 37-way cable HIM-75 (Type 43) loop-back cables, 9 inches (23 cm) long HIM-120 loop-back plug Must be calibrated Must be calibrated TTY cable (See Figure 6-1 for pin connections) RTLXQ98088 or equivalent PC PLUS or similar software Hewlett Packard E2378A or equivalent 50 W minimum Minimum accuracy 1 x 1010

31st Jul 01
68P02901W43-J
63
GSM-100-423
Test cable
Pin connections for the 9-way to 37-way test cable referred to in Table 6-1 are detailed in Figure 6-1.
1 MMI_TXD 2 MMI_RXD 3 4 GROUND 5 6 7 8 9 (9-way)
1 2 3 4 5 6 7 8 | 37 (37-way) MMI_RXD MMI_TXD GROUND
Figure 6-1 9-way to 37-way cable pin connections
64
31st Jul 01
GSM-100-423
Code download
Code download
Introduction
For the purposes of testing, the M-Cellcity must be installed with system software. How far overall network installation has progressed will dictate the source of this software. At initial loading, or when new system software is distributed to the system, the system software is downloaded from the BSC. NOTE To perform a code download to an M-Cellcity, the BSC must be equipped with a CSFP facilty. Once the BSC has established connection, it will automatically download operational code. This procedure takes approximately 30 minutes. If the BSC is not yet able to perform this download process, the M-Cellcity enclosure is provided with software loaded on a PCMCIA card.
PCMCIA card
The MCU-m has a PCMCIA socket. A PCMCIA flash card containing data is permanently inserted. The use of a flash card containing operational code provides the following advantages: S S The time taken to download code from the BSC may be significantly shortened, since the BSC only downloads objects that are missing, corrupted or out of date. The MCU-m automatically saves its code on the PCMCIA flash card, which is non-volatile. The advantage of this is that in the event of a power failure leading to system shutdown, the code will not have to be downloaded again from the BSC and so the system may be restored to call processing status as quickly as possible. The M-Cellcity may be commissioned without the presence of an active E1/T1 link, if the necessary code is contained on the PCMCIA flash card.

31st Jul 01
68P02901W43-J
65
Code download from PCMCIA
GSM-100-423

Introduction
The PCMCIA downloads the code to the equipment in preparation for optimization of the M-Cellcity. This method requires a valid software load on a PCMCIA card and that the E1/T1 link is NOT connected.
Test equipment
The following test equipment is required to be connected before proceeding with the tests: S S S S An IBM compatible Personal Computer (PC). Terminal emulator software. A Bird model 43P (Thru-line) wattmeter, or equivalent, with 2.5W element. A 9-way to 37-way cable (a diagram of this cable is provided in the Test equipment, leads and plugs section).
Preparing for test

NOTE The ac-dc PSM must not be powered up during the following preparations. 1. Ensure the E1/T1 link is not connected. NOTE This connection will allow monitoring of the download sequence and at the end of a successful download allows input of MMI commands. 2. 3. 4. Connect the 9-way to 37-way cable from serial A port to the user TTY MCU-m port (37-way D-type located beside the HIM module). Connect the wattmeter, with 2.5W element in series with the antenna port and the antenna at the bottom of the cabinet. Follow the procedure detailed in PCMCIA download
66
31st Jul 01
GSM-100-423
PCMCIA download procedure

1. Switch on the ac-dc PSM and observe the download process. The following example log can be used as a guide.
!!! REBOOT !!! RSR=0xc0 PA12=0 PA11=1 Reset due to power reset Checking DRAM: 16 of 16 MB complete Motorola MCU Boot Software Version 1.4.0.6.5 15Jul96 Copyright 1996, Motorola Incorporated Board type is MCUmicro QUICC microcode revision 0x0082 PCMCIA: Intel Series 2+ Flash detected in socket 0 Turning caches on caches are ON taking PCMCIA version of object 2 taking PCMCIA version of object 12 taking PCMCIA version of object 13 taking PCMCIA version of object 32 taking PCMCIA version of object 34 taking PCMCIA version of object 36 taking PCMCIA version of object 48 taking PCMCIA version of object 49 taking PCMCIA version of object 50 taking PCMCIA version of object 51 taking PCMCIA version of object 52 taking PCMCIA version of object 63 taking PCMCIA version of object 67 taking PCMCIA version of object 68 taking PCMCIA version of object 70 taking PCMCIA version of object 71 taking PCMCIA version of object 72 taking PCMCIA version of object 75 taking PCMCIA version of object 76 taking PCMCIA version of object 77 taking PCMCIA version of object 79 taking PCMCIA version of object 97 taking PCMCIA version of object 112 taking PCMCIA version of object 113 taking PCMCIA version of object 145 taking PCMCIA version of object 160 taking PCMCIA version of object 162 taking PCMCIA version of object 163 taking PCMCIA version of object 164 taking PCMCIA version of object 165 taking PCMCIA version of object 166 taking PCMCIA version of object 177 taking PCMCIA version of object 200 taking PCMCIA version of object 201 taking PCMCIA version of object 202 MMIROM 0000 > MMIROM 0000 > y
2.
At the MMI prompt enter: chg_l This initiates a security level change.
MMI-ROM 1015 > chg_l Enter the password for security level you wish to access:
These are the standard level 2 and 3 passwords

Enter password for security level you wish to access: Current security level is 3

31st Jul 01
68P02901W43-J
67
GSM-100-423
3.
Once level 3 access is confirmed switch to the executive monitor (emon) by selecting keys Ctrl and N together. NOTE At security level 3 the executive monitor (emon) must be selected to view the download.
MCU:emon_1015 % MCU:emon_0000 % MIP: Starting Micro IP MIP: In slot 0 MIP: csfp_swap value is 0 MIP: Reset type is x4. MIP: Initializing Codeload structures MIP: Creating Mailboxes... MIP: Performing Hard Reset. MIP: Now master MCU... MIP: Starting to contact BSC. MIP: Establishing links to NIU frame 0, slot 0 MIP: Establishing links to NIU frame 1, slot 0 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 1, c0003120 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 3, c0003120
= =
MCU:emon_1015 % NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 1, Link Mailbox id = 1001 MIP: HDLC link connected on frame 0, slot 0 MIP: CPU assigned ok on frame 0, slot 0 MIP: Link state 2 MIP: Query of NIU successful on frame 0, slot 0 MIP: NIU configured ok on frame 0, slot 0 MIP: Establishing second RSL from MCU to the BSC over NIU frame 0, slot 0, span 1 MIP: Activated LAPD on frame 0, slot 0 MIP: NIU configured ok on frame 0, slot 0, span 1 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 5, = c0003120 MIP: SAP open ok on frame 0, slot 0 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 5, Link Mailbox id= 9001 MIP: HDLC link connected on frame 0, slot 0, span 1 MIP: Link state 2 MIP: Query of NIU successful on frame 0, slot 0, span 1 MIP: Activated LAPD on frame 0, slot 0, span 1 MIP: SAP open ok on frame 0, slot 0, span 1 MIP: Bad EXEC DLSP return code 1 MIP: HDLC link failed to connect on frame 1, slot 0 with code 5 MIP: Tag 0x00 indicates nv_write successful! MCU:emon_1015 % MCU:emon_1015 % MMIROM 1015 > MMIROM 1015 > set_s 1
At this point, the operator should use the set_s <X> command where X is the site id for the Mcellcity site equipped on the PCMCIA database. This will never be the value of 0 for Mcell products Setting subsystem to 2 for site 1 Process 0x95 (Temp CM) requested a selfinitiated soft reset !!! REBOOT !!! Reset due to selfinitiated soft reset PCMCIA: Intel Series 2+ Flash detected in socket 0 Turning caches on
68
31st Jul 01
GSM-100-423
caches are ON MMIROM 0000 > MMIROM 0000 > MMIRAM 1015 > Waiting for System Initialization to complete..... MMIRAM 1015 > chg_l Enter password for security level you wish to access: These are the standard level 2 and 3 passwords Enter password for security level you wish to access: Current security level is 3 MMIRAM 1015 > MCU:emon_1015 % MCU:emon_0000 % MIP: Starting Micro IP MIP: In slot 0 MIP: csfp_swap value is 0 MIP: Reset type is x2000000. MIP: Current seconds is 31. MIP: Soft reset count read is 0. MIP: Writing time 31, count 1. MIP: Initializing Codeload structures MIP: Creating Mailboxes... MIP: Performing Soft Reset. CM: DB size is = 2046040 CM: EXEC has just allocated DB space CM: Stored DB Checksum = 51a73f4 CM: Calculated DB Checksum = 51a73f4 CM: DB Validity: 0 CM: Send DB Status message to IP process. CM: DB Status response from IP = 0. CM: Site number 1, Subsystem 2 MIP: Starting creator MCU:emon_1015 % MIP: Tag 0x00 indicates nv_write successful! SAP CONFIGURED NG EXEC DLSP dl_message_con: Control mailbox opened for channel 7, = c0003120 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 7, Link Mailbox id = 1005 NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 7. HDLC/set_t2_timer: NO chnls ACTIVE, dev index is 3 mSM: POOL SIZE = 95552 SM: PORT DATABASE INITIALIZED SM: HASH TABLES INITIALIZED mSM: Redundant MSW is OOS <*><*><*> mSM & MSW(s) CONFIGURED <*><*><*> NG EXEC DLSP dl_message_con: Control mailbox opened for channel 30, c0003120 NG EXEC DLSP dl_message_con: Control mailbox opened c0003120 NG EXEC DLSP dl_message_con: Control mailbox opened c0003120 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for Mailbox id = 2017 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for Mailbox id = 2018 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for id= 1001 NG EXEC DLSP dl_message_con: Control mailbox opened c0003120 NG EXEC DLSP dl_message_con: Control mailbox opened c0003120 HDLC/set_t2_timer: NO chnls ACTIVE, dev index is 0 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for Mailbox id = 2017 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for Mailbox id = 2018 for channel 31, for channel 1, =
channel 30, Link channel 31, Link channel 1, Link Mailbox for channel 30, for channel 31, = =
channel 30, Link channel 31, Link

31st Jul 01
68P02901W43-J
69
GSM-100-423
MIP: MIP: MIP: MIP:
Starting codeload; getting list for cpu 0x2017. Starting codeload; getting list for cpu 0x2018. Sending download OK no objects to load to CA for CPU 0x2017 Sending download OK no objects to load to CA for CPU 0x2018
MMIRAM 1015 >disp_p <site no> Where <site no> is the site id of the mcellcity in the database. this will never be a value of 0 for Mcell products. PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped
NE:Not Equipped
CPU #
Processor name BTP 00 DRI 0 0 DRI 0 1
State BU EU EU
State reason NO REASON GCLK Not Warm GCLK Not Warm
Related device N/A N/A N/A
Related function N/A N/A N/A
1015 2017 2018
MCU:emon_1015 % SITE 0 initialization complete MMIRAM 1015 > Database display commands accepted. MMI-RAM 1015 > Initialization complete. All commands accepted. ***** The MIP will wait for Gclk warm up timer to elapse before proceeding***** ***** This is currently 30 minutes ***** MMI-RAM 1015 > MMIRAM 1015 >disp_p <site no> PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped
NE:Not Equipped
610
31st Jul 01
GSM-100-423
CPU #
Processor name BTP 00 DRI 0 0 (RTF 0 0) DRI 0 1 (RTF 0 1)
State BU BU EU
State reason NO REASON NO REASON NO REASON
Related device N/A N/A N/A
Related function N/A N/A N/A
1015 2017 2018
END OF STATUS REPORT MMI-RAM 1015 > MMI-RAM 1015 > Initialization complete. All commands accepted. MMI-RAM 1015 > MCU:emon_1015 % rlogin 2 2017h To see the initialization of the transceivers, use the rlogin command, e.g. rlogin <site id + 1> processor id RSS:emon_2017% dri_activate: recd DRI_ACT for dri 0 send_abis_dri_act: sending a RSS_ABIS_ACT for DRI 0 to Abis. send_ceb_activate: sending a ACTIVATE_REQ to CEB. send_dri_act_suc: sending a DRI_ACTIV_SUCCESS for DRI 0 to FM. send_chan_create: sending a CHAN_CREATE for DRI 0 to Layer 2. prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 7, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 6, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 5, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 4, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 3, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 2, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 1, type: TCH (full rate) prc_rss_msgs: recd INS_CONF: DRI 0, timeslot 0, type: BCCH - SDCCH/4 combined
NOTE This completes the PCMCIA download. Proceed with the Checking VSWR and output power, BCCH swap checks.

31st Jul 01
68P02901W43-J
611
Checking VSWR and output power
GSM-100-423

Introduction
The objective of the output power check is to verify the predefined maximum transmitter output power of an M-Cellcity enclosure.
Checking the transmit output power

The database is configured to emit full power on channel 60. To check the transmit output power: 1. 2. 3. Monitor and record the wattmeter reading (the forward power). Replace the 2.5 W element in the wattmeter with an element suitable for measuring 5 % of maximum power and reverse the direction on the power meter. Monitor and record the reverse power reading. NOTE If the ratio of the forward and reverse readings is unacceptable (>5%), suspect an improper termination of the antenna feeder and connector. 4. Steps 5, 6 and 7 cannot be performed unless the RSL is unlocked busy. CAUTION Changing frequencies in a live network can cause interference to adjacent sites. 5. 6. 7. For GSM frequencies repeat steps 1 to 3 for Channels 3 and 123. For EGSM frequencies repeat steps 1 to 3 for channels 3, 123, 987 and 1002. Enter the following command: chg_rtf_freq # <location><rtf_id1><rtf_id2> Where: # location rtf_id1 rtf_id2 An example of this command would be: chg_rtf_freq 59 1 0 0 This changes the frequency channel to 59 for RTF 0 0 at BTS 1. 8. 9. Repeat steps 1 to 7 for the second carrier by swapping the BCCH carrier, as described next in BCCH swap procedure. Switch off the ac power to the M-Cellcity. Installation & Configuration: BSS Optimization 68P02901W43-J is: Absolute Frequency Channel. 1 to 124 0 = bsc/ 1 to 50 = bts first device id. 0 to 5 second device id. 0 to 24
612
31st Jul 01
GSM-100-423
BCCH swap procedure

To carry out the test proceed as follows: 1. At the MMI-RAM 1015 prompt enter: disp_site This will give the site number. 2. At the MMIRAM 1015 prompt enter: disp_equip <site no> This will display the equipment at the specified site as follows:
MMI-RAM 1015 > CFSP 0 0 0 BTP 0 0 0 DRI 0 0 0 DRI 0 1 0 MSI 0 0 0 MMS 0 0 0 MMS 01 0 RSL 0 0 0 GCLK 0 0 0 CAB 0 0 0 SITE 0 0 0 PATH 0 0 0 RTF 0 0 0 RTF 0 1 0
3.
At the MMI-RAM 1015 prompt enter: LOCK <site no> dri 0 0 0
4.
When the command is accepted at the MMI-RAM 1015 prompt enter: disp_p 1 The processor status for location 1 will be displayed:
PROCESSOR STATUS FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related Device N/A N/A N/A
CPU# 1015 2017 2018
Processor
Name
State B U E L B U
Reason NO REASON NO REASON NO REASON
Related Device N/A N/A N/A
BTP 0 0 DRI 0 0 (RTF 0 0) DRI 0 1 (RTF 0 1)
END OF STATUS REPORT
Ensure that the RTF on carrier DRI 0 0 has moved to DRI 0 1.

31st Jul 01
68P02901W43-J
613
GSM-100-423
5.
At the MMIRAM 1015 prompt enter: UNLOCK <site no> dri 0 0 0
6.
When this command is accepted at the MMI-RAM prompt enter: Enter: LOCK<site no> dri 0 1 0
7.
When this command is accepted at the MMI-RAM prompt enter: Enter: disp_p 1 The proessor status information for location 1 will be displayed:
PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related Device N/A N/A N/A Related Function N/A N/A N/A
CPU # 1015 2017 2018
Processor Name BTP 0 0 DRI 0 0 (RTF 0 0) DRI 0 1 (RTF 0 1)
State B - U B - E E - L
Ensure that the RTF on carrier DRI 0 1 has moved to DRI 0 0 8.

At the MMI-RAM prompt enter:
UNLOCK<site no> dri 0 1 0 When this command is accepted, ensure that both DRIs are unlocked and busy. This completes the BCCH swap procedure.
614
31st Jul 01
GSM-100-423
Download from BSC
Download from BSC

Download Procedure with example results
1. 2. Connect the E1/T1 link to the euipment. Switch on the ac power to the M-Cellcity. Wait for the equipment to link to the BSC and verify that the normal download from the BSC takes place. NOTE The BSC will overwrite the data in the PCMCIA card when it attempts to perform a normal download function. A log of the BSC download is shown following and should be used as a guide NOTE The following will only be seen if there is an E1/T1 link to the BSC and the BSC holds a database for the M-Cellcity site. The download will take approximately 30 minutes.
!!! REBOOT !!! RSR =0xc0 PA12=0 PA11=1 Reset due to power reset Checking DRAM: 16 of 16 MB complete Motorola MCU Boot Software Version 1.4.0.6.5 15-Jul-96 Copyright 1996, Motorola Incorporated Board type is MCU-micro QUICC microcode revision 0x0082 PCMCIA: Socket 0 empty Turning caches on caches are ON MMIROM 0000 > MMIROM 0000 > y
3.
At the MMI prompt enter: chg_l This initiates a security level change.
MMIROM 1015 > chg_l Enter password for security level you wish to access:
These are the standard level 2 and 3 passwords

Enter password for security level you wish to access: Current security level is 3

31st Jul 01
68P02901W43-J
615
Download from BSC
GSM-100-423
4.
Once level 3 access is confirmed switch to the executive monitor (emon) by selecting keys Ctrl and N together. NOTE At security level 3 the executive monitor (emon) must be selected to view the download.
MCU:emon_1015 % MCU:emon_0000 % MIP: Starting Micro IP MIP: In slot 0 MIP: csfp_swap value is 0 MIP: Reset type is x4. MIP: Initializing Codeload structures MIP: Creating Mailboxes... MIP: Performing Hard Reset. MIP: Now master MCU... MIP: Starting to contact BSC. MIP: Establishing links to NIU frame 0, slot 0 MIP: Establishing links to NIU frame 1, slot 0 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 1, = c0003120 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 3, = c0003120 MCU:emon_1015 % NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 1, Link Mailbox id = 1001 MIP: HDLC link connected on frame 0, slot 0 MIP: CPU assigned ok on frame 0, slot 0 MIP: Link state 2 MIP: Query of NIU successful on frame 0, slot 0 MIP: NIU configured ok on frame 0, slot 0 MIP: Establishng second RSL from MCU to the BSC over NIU frame 0, slot 0, span 1 MIP: Activated LAPD on frame 0, slot 0 MIP: NIU configured ok on frame 0, slot 0, span 1 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 5, = c0003120 MIP: SAP open ok on frame 0, slot 0 NG EXEC_DLSP process_hdlc_msg: LINK ESTABLISHED for channel 5, Link Mailbox id= 9001 MIP: HDLC link connected on frame 0, slot 0, span 1 MIP: Link state 2 MIP: Query of NIU successful on frame 0, slot 0, span 1 MIP: Activated LAPD on frame 0, slot 0, span 1 MIP: SAP open ok on frame 0, slot 0, span 1 MIP: Sending CA polling message MIP: Bad EXEC DLSP return code 1 MIP: HDLC link failed to connect on frame 1, slot 0 with code 5 MIP: Tag 0x00 indicates nv_write successful! MIP: Received Subsystem State Query message. Subsystem = 2, level number 263e MIP: BSC-MCELL Code Downloading in Progress... MIP: Tag 0x00 indicates nv_write successful! MCU:emon_1015 % Load version information not present MCU:emon_1015 % Uncompressing MCU used objects MIP: Code Downloading complete
616
31st Jul 01
GSM-100-423
Download from BSC
MIP: Creating CM and MMI MIP: Disconnecting RSL NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 1. NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 5. MIP: Terminate HDLC frame 1 slot 0 received NG EXEC DLSP dl_message_disc: DL_DISCONNECT_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 1. MMIRAM 1015 > MMIRAM 1015 > MMI-RAM 1015 > Waiting for System Initialization to complete. MMI-RAM 1015 > Database display commands accepted. MMI-RAM 1015 > Initialization complete. All commands accepted. MMI-RAM 1015 > MMIRAM 1015 >chg_l Enter password for security level you wish to access:
These are the standard level 2 and level 3 passwords.

Enter password for security level you wish to access: Current security level is 3 MMI-RAM 1015 >
Once level 3 access is confirmed switch to the executive monitor (emon) by selecting keys Ctrl and N together.
MCU:emon_1015 % fore deleting mbox. Channel 3. MIP: Leaving RSL thread MIP: HDLC Link to the NIU disconnected successfully MIP: Leaving second RSL thread CM: CM: CM: CM: CM: CM: CM: DB size is 2046040 EXEC has just allocated DB space Stored DB Checksum =51a701d Calculated DB Checksum =51a701d DB Validity: 0 Send DB Status message to IP process DB status response from IP =11
CM: Set level number to x0 x0 x26 x3e per IP. CM: Site number 1, Subsystem 2 CM: Reassigning DB for the site. HDLC/sabm_timeout_func: Channel 3 not being established or SABMs are outstanding Skipping transmit of SABM. Channel state is 0 HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 1 MIP: Starting creator NG EXEC DLSP dl_message_con: Control mailbox opened for channel 2, =c0003120. NG EXEC DLSP dl_message_con: Control mailbox opened for channel 4, =c0003120 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 4, Link Mailbox id = 104 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 2, Link Mailbox id = 102 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 2 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 4 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 6, =c0003120. NG EXEC DLSP dl_message_con: Control mailbox opened for channel 7, =c0003120.

31st Jul 01
68P02901W43-J
617
Download from BSC
GSM-100-423
NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 7, Link Mailbox id = 107 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 6, Link Mailbox id = 106 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 6 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 7 HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 3 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 8, =c0003120. NG EXEC DLSP dl_message_con: Control mailbox opened for channel 9, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 9, Link Mailbox id = 109 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 8, Link Mailbox id = 108 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =8 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel = 9 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 14, =c0003120. NG EXEC DLSP dl_message_con: Control mailbox opened for channel 15, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 15, Link Mailbox id = 10f NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 14, Link Mailbox id = 10e NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =14 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =15 NG EXEC DLSP dl_message_con: Control mailbox opened for channel 20, =c0003120. NG EXEC DLSP dl_message_con: Control mailbox opened for channel 21, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 21, Link Mailbox id = 115 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 20, Link Mailbox id = 114 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =20 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =21 NG EXEC DLSP NG EXEC DLSP dl_message_con: Control mailbox opened for channel 31, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 31, Link Mailbox id = 11f NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 30, Link Mailbox id = 11e NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =30 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =31 SAP CONFIGURED NG EXEC DLSP dl_message_con: Control mailbox opened for channel 7, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 7, Link Mailbox id = 1005 NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =7 HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 3
618
31st Jul 01
GSM-100-423
Download from BSC
mSM: POOL SIZE = 95552 SM: PORT DATABASE INITIALISED SM: HASH TABLES INITIALISED mSM: Redundant MSW is OOS <*><*>mSM &MSW(s) CONFIGURED <*><*> NG EXEC dl_message_con: Control mailbox opened for channel 30, =c0003120. NG EXEC dl_message_con: Control mailbox opened for channel 31, =c0003120. NG EXEC dl_message_con: Control mailbox opened for channel 1, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 30, Link Mailbox id = 2017 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 31, Link Mailbox id = 2018 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 1, Link Mailbox id = 1001 NG EXEC dl_message_con: Control mailbox opened for channel 30, =c0003120. NG EXEC dl_message_con: Control mailbox opened for channel 31, =c0003120. NG EXEC DLSP dl_message_disc: DL_DISCONNECTP_REQ SUCCESSFUL. Waiting for confirm before deleting mbox. Channel =1 HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 0 HDLS/set_t2_timer: NO chnls ACTIVE, dev index is 1 NG EXEC dl_message_con: Control mailbox opened for channel 1, =c0003120. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 1, Link Mailbox id = 1001 CA >RSL | received link CONNECT Indication, site=0 NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 30, Link Mailbox id = 2017 MIP: Starting codeload; getting list for cpu 0x2017. NG EXEC DLSP process_hdlc_msg: LINK ESTABLISHED for channel 31, Link Mailbox id = 2018 MIP: Starting codeload; getting list for cpu 0x2018. MIP: Sending download OK no objects to CA for CPU 0x2017 MIP: Sending download OK no objects to CA for CPU 0x2018 SITE 0 initialization complete MCU:emon_1015 % MCU:emon_1015 %
NOTE Once site initialization is complete code objects can be viewed by entering o at the emon prompt.

31st Jul 01
68P02901W43-J
619
Download from BSC
GSM-100-423
5.
At the emon prompt type:

MCU:emon_1015 % o
Object Name 000 002 003 006 007 008 012 013 018 020 022 023 032 034 036 048 049 050 051 052 062 063 067 068 070 071 072 075 076 077 079 080 097 111 112 113 145 160 162 exec dbase null ec_com btask mcuboot rssboot options ex_disp ex_tty ex_ftr emon cp_rrsm cp_crm cp_cbs rs_cfm rs_ho rs_lyr1 rs_abis rrs_lyr2 mcu_dsp fm_msm ffm_rtrp fm_crtr fm_mvp fm_mca fm_sync fm_ftp fm_mmf fm_sap fm_fcp mip st_ssp mmi_rom om_mmi om_cm ex_tdsm uboot ccdsp
Version 04.00.06.05 00.00.03.fd 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.00.00. 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.5a 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 04.00.06.05 07.23.00.01 e0.01.03.00
Date 15-Jul-96 10-Jan 80 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 30-Jul-96 16-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 16-Jul-96 16-Jul-96 16-Jul-96 16-Jul-96 16-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 16-Jul-96 19-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 16-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 15-Jul-96 10-Jul-96 25-Jul-96
Time 17:45 08:40 17:45 17:51 17:53 18:03 14:09 02:39 17:50 17:46 17:50 17:48 16:13 15:48 15:15 01:30 01:36 01:46 01:26 01:50 17:56 20:53 20:54 20:16 21:12 10:37 09:59 20:43 20:49 20:59 20:22 18:01 01:53 18:03 23:58 22:27 17:21 15:02 16:27
Checksum 0x012e06b9 0x051ad904 0x0003450c 0x0018c166 0x0010e287 0x026312ec 0x0173c859 0x0002239a 0x00106313 0x00116d64 0x00109635 0x004cc384 0x00d81eac 0x0121d8e8 0x005eede2 0x00425c4b 0x005d8826 0x00ad05d0 0x007e1df2 0x0031ebab 0x00276e74 0x00851f35 0x0012f579 0x0011210d 0x0019a77a 0x0230ceac 0x003a77b6 0x013269c1 0x00396ff3 0x005c3ad7 0x0071b478 0x004b1e00 0x0010488c 0x0016205d 0x02577383 0x026702ad 0x001d00a5 0x000c634e 0x006f0a97
Size 0028654 02046040 00004024 00020451 00014853 00541226 00206403 00001144 00014317 00014888 00015118 00060259 00183994 00238273 00082377 00055194 00077849 00140093 00102699 00043973 00033334 00107633 00017236 00020349 00021747 00443092 00046659 00254001 00046977 00076969 00092863 00057774 00014060 00019705 00502329 00485032 00025044 00008557 00060084
S 1 1 2 2 2 1 1 1 2 2 2 2 2 2 2 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 1 2 2 1 1 1
Ty 09 03 09 09 09 09 12 04 09 09 09 09 05 05 05 07 07 07 07 07 09 09 06 06 09 09 09 05 05 05 17 09 05 09 05 05 06 13 13
Object Specific c8 00263e 0000 c8 c8 8f 8f a0
c8 c8 c8 c8 b8 b8 b8 b8 b8 b8 b8 b8 8f bf f8 f8 bf bf bf f8 b8 f8 bf c8 b8 8f f8 f8 f8 b80000 0000 b00001 0220
620
31st Jul 01
GSM-100-423
Download from BSC
Object Name 163 164 165 166 177 200 201 202 orac_os orac_eq TSM_FEP TSM_CC niu sync_fw SCP SEQ
Version 24.07.96.01 07.23.00.01 04.00.06.02 04.00.06.03 04.00.06.05 04.00.06.5a 04.00.06.04 04.00.06.02
Date 24-Jul-96 23-Jul-96 27-Mar-96 31-May-96 15-Jul-96 18-Jul-96 24-Jun-96 01-Feb-96
Time 16:13 14:56 17:59 11:26 10:03 18:15 09:35 14:55
Checksum 0x013e41a3 0x003650a7 0x00223596 0x003a2c9f 0x00ef3d12 0x00555515 0x00a644da 0x00168326
Size 00169637 00029550 00018752 00032152 00224870 00076843 00155539 00022446
S 1 1 1 1 1 1 1 1
Ty 15 15 16 16 10 10 08 08
Object Specific b7e401 0090 b70001 0900 b00401 0d00 b00400 0d00 bf0004 0d00 bf0002 0200 b80304 0900 b80302 0f00
Load version information not present MCU:emon_1015 % MCU:emon_1015 %
6.
At the emon prompt type: disp_p 1 This displays the processor status information for location 1.
PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related Device N/A N/A N/A Related Device N/A N/A N/A
CPU# 1015 2017 2018
Processor
Name
State B U E U E U
Reason NO REASON GCLK Not Warm GCLK Not Warm
BTP 0 0 DRI 0 0 DRI 0 1
***** The MIP will wait for Gclk warm up timer to elapse before proceeding***** ***** This is currently 30 minutes *****
MMI-RAM 1015 > MMI-RAM 1015 >

31st Jul 01
68P02901W43-J
621
Download from BSC
GSM-100-423
7.
At the MMI prompt type: disp_p 1 The processor status for location 1 will be displayed. Entering this command after 30 minutes confirms if the GCLK warm-up time has elapsed.
PROCESSOR STATUS FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related Device N/A N/A N/A Related Device N/A N/A N/A
CPU# 1015 2017 2018
Processor
Name
State B U B U B U
BTP 0 0 DRI 0 0 (RTF 0 0) DRI 0 1 (RTF 0 1)
MMI-RAM 1015 >
This completes the log of the download.
Site status check procedure

To check the site status once it is fully operational proceed as follows: 1. At the MMI prompt type: disp_bss High level information of all sites supported in the BSS is displayed.
OPER STATES: ADMIN STATES: D:Disabled L:Locked # of sectors 0 1 543 21 61713 (F111h) 4368 (1110h) 10 E:Enabled U:Unlcoked B:Busy E:Equipped NE:Not Equipped S:Shutdown
Site 0 1
Site Status B - U B - U
MCC
MNC
LAC
CI
622
31st Jul 01
GSM-100-423
Download from BSC
2.
At the MMI prompt type: disp_cell_status 1 The cell status for location 1 will be displayed:
Start of report for LOCATION 1: GSM CELL ID MCC 543 MNC 21 LAC (dec) (hex) 61713 f111h CI 1368 1110h
Status Reset in Prog SPI in Prog BSS BSSAP Prhb MSC BSSAP Prhb SPI/MSC SCCP Prhb Free SDCCH Free TCH/F Free TCH/H In Use SDCCH In Use TCH/F In Use TCH/H End of Report Barred No Yes Yes No N/A 3 15 0 1 0 0

31st Jul 01
68P02901W43-J
623
Download from BSC
GSM-100-423
3.
At the MMI prompt type: state 1 Device status information for location 1 is displayed.
PROCESSOR STATUS FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped S:Shutdown
Device CSFP 0 0 0 BTP 0 0 0 DRI 0 0 0 DRI 0 1 0 MSI 0 0 0 MMS 0 0 0 MMS 0 1 0
State D - U B - U B - U B - U B - U B - U D - U
State reason NO REASON NO REASON NO REASON NO REASON NO REASON NO REASON Synch Loss OSS Timer NO REASON GCLK in Set Freq. Mode NO REASON NO REASON NO REASON
Last transition related dd/mm hh:mm:ss Function 19/08 19/08 19/08 19/08 19/08 19/08 19/08 10:13:44 10:13:48 10:30:29 10:31:18 10:13:50 10:13:51 10:13:51 None None RTF 0 0 0 RTF 0 1 0 None None None
RSL 0 0 0 GCLK 0 0 0
B - U B - U
22/08 19/08
10:58:18 10:24:44
None None
CAB 0 0 0 SITE 0 0 0 PATH 0 0 0
B - U B - U B U
19/08 19/08 22/08
10:13:44 10:15:20 10:58:33
None None None
FUNCTION STATUS INFORMATION FOR LOCATION 1 OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped
Device RTF 0 0 0 RTF 0 1 0
State B E B - E
State reason NO REASON NO REASON
Last transition related dd/mm hh:mm:ss Function 19/08 19/08 10:30:09 10:31:04 DRI 0 0 0 DRI 0 0 0
624
31st Jul 01
GSM-100-423
Battery check
Battery check
Introduction
The objective of the battery check is to verify the serviceability of the battery in the event of an ac mains power supply failure. NOTE Before performing the battery test it is imperative that the battery is fully charged. The battery takes a minimum of 12 hours to fully charge.
Test equipment
The Battery check requires the following test equippment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 37-way cable (a diagram of this cable is provided in the Test equipment and test leads section).
Commands
The following command is to be used to carry out the procedure: Command state Function Displays the status of specified devices or functions.
Battery test
To test the battery proceed as follows: 1. 2. 3. Ensure the 9-way to 37-way cable from serial A port (on the PC) to the user TTY MCU-m port (37-way D-type located beside the HIM module) is connected Switch off the ac mains supply to the M-Cellcity. With the terminal emulater software running on the PC, at the MMI prompt enter: state # Where: # is: location id
An example of this command would be: state 1 Device status information for location 1 is displayed.
PROCESSOR STATUS FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped S:Shutdown

31st Jul 01
68P02901W43-J
625
Battery check
GSM-100-423
Device CSFP 0 0 0 BTP 0 0 0 DRI 0 0 0 DRI 0 1 0 MSI 0 0 0 MMS 0 0 0 MMS 0 1 0
State D - U B - U B - U B - U B - U B - U D - U
State reason NO REASON NO REASON NO REASON NO REASON NO REASON NO REASON Synch Loss OSS Timer NO REASON GCLK in Set Freq. Mode NO REASON NO REASON NO REASON
Last transition related dd/mm hh:mm:ss Function 19/08 19/08 19/08 19/08 19/08 19/08 19/08 10:13:44 10:13:48 10:30:29 10:31:18 10:13:50 10:13:51 10:13:51 None None RTF 0 0 0 RTF 0 1 0 None None None
RSL 0 0 0 GCLK 0 0 0
B - U B - U
22/08 19/08
10:58:18 10:24:44
None None
CAB 0 0 0 SITE 0 0 0 PATH 0 0 0
B - U B - U B U
19/08 19/08 22/08
10:13:44 10:15:20 10:58:33
None None None
FUNCTION STATUS INFORMATION FOR LOCATION 1 OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped
Device RTF 0 0 0 RTF 0 1 0
State B E B - E
State reason NO REASON NO REASON
Last transition related dd/mm hh:mm:ss Function 19/08 19/08 10:30:09 10:31:04 DRI 0 0 0 DRI 0 0 0
Ensure that responses that should be busy and unlocked are showing B - U. 4. 5. Switch on the ac mains supply. Disconnect the serial cable from the TTY port. This completes the test.
626
31st Jul 01
GSM-100-423

Introduction
The E1/T1 link checks verify the integrity of the E1/T1 link back to the BSC/MSC.
Test equipment
The E1/T1 link checks require the following test equipment: S S S An IBM compatible personal computer (PC). Terminal emulator software. A 9-way to 37 way-cable (a diagram of this cable is provided in the Test equipment and test leads section).
Commands
The following command is to be used to carry out the procedure: Command state Function Displays the status of specified devices or functions.

To set up the equipment to check the E1/T1 link: 1. 2. 3. Make sure the site is in call processing mode. Ensure the 9-way to 37-way cable from serial A port (on the PC) to the user TTY MCU-m port (37-way D-type located beside the HIM module) is connected. Start the terminal emulator program at the PC.
The system and the hardware are set up to check the E1/T1 link.

31st Jul 01
68P02901W43-J
627
GSM-100-423
Running the test

To check the E1/T1 links: 1. 2. 3. Contact the end point of the E1/T1 link to be tested (BSC/MSC) and request a loopback on the relevant Digital Distribution Frame (DDF) port. Determine the site number, equipment list and MMS configuration. At the CUST MMI prompt enter: state # MMS * * * Where: # * * * An example of this command would be: state 0 MMS 1 0 0 The system displays the following message from the MCU-m for location 0:
STATUS INFORMATION Device: MMS 1 0 0 Administration state : Unlocked Operational state : Busy Reason code is : NO REASON Time of last transition : Wed Jan 5 01:43:13 1994 Related Device/Function: NONE END OF STATUS REPORT
is: location dev/func id dev/func id dev/func id
If this display shows Unlocked and Busy, then the NIU-m port (MMS), HIM-75/HIM-120, cabling and the E1/T1 link are all good. If the loop is removed and the command re-entered, the result should be Unlocked and Disabled. NOTE The NIU-m requires a minimum of 20 seconds after receiving these commands before it registers a change in status.
Fitting chassis bottom cover

Having completed all necessary configuration checks fit the chassis bottom cover: 1. 2. 3. Using a clean, dry cloth, wipe out the inside of the chassis bottom cover to remove any excess moisture. Fit the chassis bottom cover onto the lower compartment, taking care not to damage to the gasket seal. Tighten the 11 M4 bolts around the edge of the chassis bottom cover.
628
31st Jul 01
GSM-100-423
Calibrating an MCU-m GCLK

Introduction
Follow this procedure for the M-Cellcity MCU-m to calibrate the GCLK.
Equipment
MCU-m GCLK calibration requires the following test equipment: S S S A 9-way to 37 way-cable (a diagram of this cable is provided in the Test equipment and test leads section). A frequency counter referenced to a 1.25 ppb (parts per billion) or better reference. A PC with terminal emulator software running.
Procedure
1. Ensure the 9-way to 37-way cable from serial A port (on the PC) to the user TTY MCU-m port (37-way D-type located beside the HIM module) is connected. At the PC running the terminal emulator software the prompt SYNC-MMI should appear. 2. 3. Connect the frequency counter to the 8 kHz (ref_125 ms) BNC connector of the MCU TTY cable. Attach a 10 MHz reference signal to the 10 MHz BNC input connector on the frequency counter. Allow the MCU-m to warm up for 30 minutes or the OCXO will not be stable. 4. If the module is reset for any reason, this restarts the module 30 minute counter. If this happens, type the following command to force the sync section into the warmed-up state:
SYNC-MMI>dwarm
5.
Type
SYNC-MMI>dcal 8000Hz source Connected, Enter y when ready, a to abort test>y
The frequency measured will be approximately but not exactly 8000.00000 Hz. 6. Adjust the OCXO control voltage by typing +3...+2...+1...+0...0...1...2...3 until the frequency is exactly 8000.00000 Hz:
Enter a to abort, s to save, +[0..3] to inc, [0..3] to dec>+2 Enter a to abort, s to save, +[0..3] to inc, [0..3] to dec>+1 Enter a to abort, s to save, +[0..3] to inc, [0..3] to dec>+1
NOTE These numbers as entered relate to orders of magnitude. For example, typing +3 causes an increase ten times bigger than that caused by typing +2. The entries +0 and 0 are both valid.

31st Jul 01
68P02901W43-J
629
GSM-100-423
7.
When the ref_125 ms frequency is exactly 8000.00000 Hz, specify save as follows:
Enter a to abort, s to save, +[0..3] to inc, [0..3] to dec>s
The calibration program sets the output frequencies to various different values and now requests that you type in the values of the output frequency at various points:
Dac set to 1.0 volts, Enter Freq value or a to abort>7999.99673 Dac set to 2.0 volts, Enter Freq value or a to abort>7999.99838 Dac set to 3.0 volts, Enter Freq value or a to abort>7999.99970 Dac set to 4.0 volts, Enter Freq value or a to abort>8000.00033 Dac set to 5.0 volts, Enter Freq value or a to abort>8000.00133 Dac set to 6.0 volts, Enter Freq value or a to abort>8000.00271 Dac set to 7.0 volts, Enter Freq value or a to abort>8000.00379 Calibration Gain 0.37345 SYNCMMI>
RETURN
This ends the calibration procedure.
630
31st Jul 01
Chapter 7
M-Cellaccess and Horizonoffice optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 7 M-Cellaccess and Horizonoffice optimization . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cellaccess and Horizonoffice optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to test equipment, leads and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 9-way cable (M-Cellaccess) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-way to 25-way cable (M-Cellaccess and Horizonoffice) . . . . . . . . . . . . . . . . . . . Test plugs for M-Cellaccess and Horizonoffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the dc power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the database for devices and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying PSM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calibrating the M-Cellaccess or Horizonoffice GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK calibration record form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
71 71 71 72 72 72 73 74 75 76 76 76 76 76 77 79 79 79 79 79 712 712 712 712 712 714 714 714 714 714 715 715 715 715 715 718 719 719 719 719 720 722

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423

Optimization overview
This chapter provides information required to optimize Motorola M-Celltaccess BSS equipment and Horizonoffice equipment For information about equipment not supplied by Motorola, for example battery chargers, power supplies and antennas, refer to the site specific documentation and the vendor instructions provided with the equipment. WARNING Hazardous voltages in excess of 50 V dc exist inside 48 V and 60 V cabinets. Use extreme caution when working on a cabinet with power applied. Remove all rings, watches and other jewellery.
Code download
At initial loading, or when new system software is distributed to the system, the system software is downloaded from the OMC-R. If a new load is required at a site, request a download from the OMC-R to that site. NOTE If the existing software detects a corrupted segment in the current load, it automatically requests a download from the OMC-R.

31st Jul 01
68P02901W43-J
71
GSM-100-423

Introduction to test equipment, leads and plugs
Various test equipment and test leads are required to carry out the optimization tests. Tools required for installation are listed in Chapter 1.
CAUTION All test equipment and test leads must be calibrated annually by a recognized laboratory, not in the field. Do not use test equipment that is beyond its due calibration date.
NOTE Allow test equipment to warm up for 30 minutes before use.
Requirements
Table 7-1 lists the equipment required for system optimization. Table 7-1: System optimization equipment Quantity 1 Item IBM-compatible personal computer (PC) with: At least a 386 processor. At least a 60 Mbit/s hard drive. At least 4 Mbit/s of RAM. PCMCIA type 2 slot. Frequency counter (1.25 parts per billion (ppb) or better reference. 10 digit display required. Some types can be used with rubidium standard for extra accuracy). Rubidium standard (minimum accuracy 1x1010). Commercial terminal emulator software (PC Plus or similar). Digital multimeter (HP E2378A or equivalent). Mobile phone. ESD protection kit. 9-way to 9-way cable (PC to PCU). 9-way to 25-way cable (PC to GPROC). Type 43 loopback cables 23 cm (9 in) long. BIB loopback plug. Test plugs A, B and C.
1 1 1 1 1 1 2 6 1 1 each
72
31st Jul 01
GSM-100-423
9-way to 9-way cable (M-Cellaccess)

The diagram shows the cable for PC to PCU connection:
2 3 5 4 6 7 8
4 m LONG SCREENED CABLE TO PC COMMUNICATIONS PORT 9-WAY D-TYPE FEMALE
3 2 7 5
TO PCU CONNECTOR 9-WAY D-TYPE MALE

31st Jul 01
68P02901W43-J
73
GSM-100-423
9-way to 25-way cable (M-Cellaccess and Horizonoffice)

The diagram shows the cable for PC to GPROC connection:
1 2 3 4 5 6 7 8 9
4 m LONG SCREENED CABLE 9-WAY D-TYPE FEMALE
8 3 2 20 7 6 4 5 22
25-WAY D-TYPE MALE
74
31st Jul 01
GSM-100-423
Test plugs for M-Cellaccess and Horizonoffice

Test plug A
The table lists the pin connections for test plug A: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Test plug B
The table lists the pin connections for test plug B: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Test plug C
The table lists the pin connections for test plug C: From pin
1 4 7 10 44 47 50 53
To pin
2 5 8 11 45 48 51 54
Connection
Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link Connect with a wire link

31st Jul 01
68P02901W43-J
75
GSM-100-423

Introduction
WARNING The person carrying out these tests must be accompanied by a second person acting in a safety capacity. The objective of the dc power supply tests is to verify that the main dc supply and power supply modules are operating.
Test equipment
No special test equipment is required to carry out the dc power supply tests.
Commands
No special software commands are required for the dc power supply tests.
Procedure
To carry out the dc power supply tests: 1. 2. 3. 4. Ensure that none of the full size modules, half size modules or power supply modules (IPSMs or EPSMs) are seated in their backplane connectors. Set all cabinet power supply circuit breakers to the OFF position. Apply power to the cabinet. Check that the cabinet fans are operating. If the fans are not operating: Step a. Action Check that dc power is connected to the cabinet (if not, suspect the dc power supply, the power cabling and the cabinet power input connections). Check the fan fuses and the dc power cabling to the fans. Correct the problem and repeat step 3 to step 5. NOTE The fans must be operating before IPSM/EPSMs can be switched on. 5. 6. 7. 8. Firmly seat all IPSMs/EPSMs in their backplane connectors. Set the circuit breaker for each IPSM/EPSM in turn to ON. Check that the green LED active indicator for the chosen IPSM/EPSM lights. Insert all processor cards into their backplane connectors. Insert all other modules into their backplane connectors. Installation & Configuration: BSS Optimization 68P02901W43-J
b. c.
76
31st Jul 01
GSM-100-423
Circuit breakers
The tables list the cabinet circuit breaker assignments:
48/60 V dc PCC cabinets (M-Cellaccess)

Table 7-2 Circuit breakers CB 11 10 9 8 7 6 5 4 3 2 1 Protects Not fitted IPSM2L IPSM1L IPSM0L IPSM2U IPSM1U IPSM0U Not used Not used Not used DAB
24 V dc PCC cabinets(M-Cellaccess)
Table 7-3 Circuit breakers CB 11 10 9 8 7 6 5 4 3 2 1 Protects Not fitted EPSM2L EPSM1L EPSM0L EPSM2U EPSM1U EPSM0U Not used Not used Not used DAB

31st Jul 01
68P02901W43-J
77
GSM-100-423
48/60 V dc Horizonoffice cabinet

Table 7-4 Circuit breakers CB 10 9 8 7 6 5 4 3 2 1 Protects Not fitted Not fitted Not fitted DAB HDSL CPB IPSM IPSM IPSM CPB
78
31st Jul 01
GSM-100-423

Introduction
Follow this procedure to check which devices and functions are contained in the BSC/BTS database. This procedure can be used by M-Cellaccess and Horizonoffice.
Test equipment
The following test equipment is required to carry out the procedure: S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 25-way cable.
Commands
The following commands must be used to carry out the procedure: Command disp-site disp-equipment state Function Displays the site number. Displays the active equipment at a specified site. Displays the status of specified devices or functions.
Procedure
To check the database for devices and functions: 1. 2. 3. 4. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a GPROC TTY port using the 9-way to 25-way cable. At the PC start the terminal emulator program. At the CUST MMI prompt type: disp_site The following message (from the GPROC) is displayed:
current site is #

31st Jul 01
68P02901W43-J
79
GSM-100-423
NOTE This is an example of M-Cellaccess database equipage. 5. Type: disp_equipment # Where: # is: location
A complete list of the equipment and functions in the database is displayed, for example:
GPROC GPROC BSP DRI DRI MSI MMS MMS MTL OML GCLK KSW CAGE CAB SITE BTF RTF RTF RTF RTF RTF 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 1 0 0 1 0 0 1 1 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 2 0 0 3 0 0 0 1 0
710
31st Jul 01
GSM-100-423
6.
To check the MSI configuration type: state # MSI * * * Where: # * * * An example of the command would be: state 0 MSI 1 0 0 A message similar to the following example is displayed:
MSI identifier Cage number Slot number MSI type 1 0 16 0 (0 = MSI and 1 = XCDR)

31st Jul 01
68P02901W43-J
711
Checking the E1 link
GSM-100-423

Introduction
Follow this procedure to verify the integrity of the E1 links to the BSC/MSC. This procedure can be used by M-Cellaccess and Horizonoffice.
Test equipment
Command
The following command must be used to carry out the procedure: Command state Function Displays the status of specified devices or functions.
Procedure
To check the E1 link: 1. 2. 3. 4. Ensure that the site is in call processing mode. Connect the serial A port on the PC to a GPROC TTY port using the 9-way to 25-way cable. At the PC start the terminal emulator program. Contact the end point of the E1 link to be tested (BSC/MSC) and request a loopback on the relevant distribution frame (DDF) port. NOTE Repeat for all MSIs and E1 links. If the E1 link has not been installed, perform this test at the digital distribution frame (DDF) in the site, or at the top of the cabinet if no DDF is fitted. 5. Determine the site number, equipment list and MMS configuration.
712
31st Jul 01
GSM-100-423
6.
At the CUST MMI prompt type: state # MMS * * * Where: # * * * For example: state 0 MMS 1 0 0 The following message (from the GPROC) is displayed:
Status Information Administration state : Unlocked Operational state : Busy Reason code is : 0 Time of last transition : Wed Jan 5 01:43:13 1994 Other identification : 255 255 255 255 End of status report
If this display shows Unlocked and Busy, then the MSI port (MMS) T43/BIB/HIM75/HIM-120 cabling and the E1 link are all good. If the loop is removed and the command reentered, the result is Unlocked and Disabled. NOTE The MSI requires at least 20 seconds to register a change in status after these commands are entered.

31st Jul 01
68P02901W43-J
713
Verifying PSM version
GSM-100-423
Verifying PSM version

Introduction
Follow this procedure to verify the PSM version. This procedure can be used by M-Cellaccess and Horizonoffice.
Test equipment
Commands
The following commands must be used to carry out the procedure: Command enable_alarm serial_cmd Function Enables alarm reporting for a specified site. RAM EMON query command.
Procedure
To check power supply module (PSM) version and alarm status: 1. At the RAM EMON prompt type: serial_cmd 080h 0 serial_cmd 081h 0 serial_cmd 082h 0 2. (for PSM 0) (for PSM 1) (for PSM 2)
The following message is displayed:

ss xx nv aa
Where: ss xx n v aa
is: slot address in hexadecimal (80, 81 or 82) irrelevant to this test version number (2, 3 or 4) cabinet supply voltage (8 = + 27 V, 9 = 48/60 V) an alarm code (03 = over-temp fail, 05 = input power fail, 06 = unit fail, 07 = no alarms)
714
31st Jul 01
GSM-100-423

Introduction
Follow this procedure to ensure that all allocated circuit identification codes (CICs) are carrying good quality voice traffic. This procedure can be used by M-Cellaccess and Horizonoffice. NOTE Transcoders may be in the form of XCDR boards, or an enhanced version utilising a Generic Digital Signal Processor Board (GDP). If you use GDPs in XCDR slots, as XCDRs, the procedure is the same as for XCDRs, except where stated.
Test equipment
The following test equipment is required: S S S S An IBM-compatible personal computer (PC). Terminal emulator software. A 9-way to 25-way cable. A GSM mobile with a registered SIM card.
Commands
The following commands are required to carry out this procedure: Command disp_mms_ts_usage disp_channel fil list fil create fil start fil stop fil delete Function Displays the timeslot usage on an MMS span. Displays the BSCMSC connectivity. Lists active filters. Creates a filter. Starts a filter. Stops a filter. Deletes filters.
Procedure
Before starting the transcoder integration procedure, consult the site specific documentation to determine the BSC/XCDR configuration and cage slot allocation (conventionally, timeslots 00 and 16 on XCDR boards are not allocated to voice/traffic channels). Proceed as follows:
Displaying circuit mapping

1. At the operations and maintenance centre (OMC) man-machine interface (MMI), log in to the required base site controller (BSC).

31st Jul 01
68P02901W43-J
715
GSM-100-423
2.
To display the circuit mapping, type: disp_mms_ts_usage X Y where X = MSI, Y = MSI port The following message is displayed:
Circuit ID = 1 Circuit ID = 2 Circuit ID = 3 Circuit ID = 4 Circuit ID = 5 Circuit ID = 6 Circuit ID = 7 Circuit ID = 8 Group Number = 3 Group Number = 2 Group Number = 1 Group Number = 0 Group Number = 3 Group Number = 2 Group Number = 1 Group Number = 0 Timeslot Number = 2 Timeslot Number = 2 Timeslot Number = 2 Timeslot Number = 2 Timeslot Number = 3 Timeslot Number = 3 Timeslot Number = 3 Timeslot Number = 3
3. 4.
Repeat step 2 for all MMSs. Log out from the BSC.
Displaying CEPT nailed connections

1. 2. Log on to the required XCDR. To display all CEPT nailed connections, type: disp_channel The following message is displayed:
Incoming MMS id 6 1, timeslot: 2 group : 3 Outgoing MMS id 24 0, timeslot: 1 Incoming MMS id 6 1, timeslot: 2 group : 2 Outgoing MMS id 24 0, timeslot: 2 Incoming MMS id 6 1, timeslot: 2 group : 1 Outgoing MMS id 24 0, timeslot: 3 Incoming MMS id 6 1, timeslot: 2 group : 0 Outgoing MMS id 24 0, timeslot: 4 Incoming MMS id 6 1, timeslot: 3 group : 3 Outgoing MMS id 24 0, timeslot: 5 Incoming MMS id 6 1, timeslot: 3 group : 2 Outgoing MMS id 24 0, timeslot: 6 Incoming MMS id 6 1, timeslot: 3 group : 1 Outgoing MMS id 24 0, timeslot: 7 Incoming MMS id 6 1, timeslot: 3 group : 0 Outgoing MMS id 24 0, timeslot: 8
3.
The information in the messages displayed in steps 2 and 2, together with BSC/XCDR site documentation,contain the CIC mapping. Two examples are:
Circuit ID = 3 Group Number = 1 Timeslot Number = 2
Incoming MMS id 6 1, timeslot: 2 group : 1 Outgoing MMS id 24 0, timeslot: 3 Circuit ID = 91 Group Number = 2 Timeslot Number = 24
Incoming MMS id 6 1, timeslot: 24 group : 2 Outgoing MMS id 24 0, timeslot: 3
716
31st Jul 01
GSM-100-423
4.
Log out from the XCDR.
Displaying and testing CICs

1. 2. Log on to the required BSC. At the RAM EMON prompt type: fil list If any filters are shown delete them using the fil delete command. 3. 4. Remotely log in to the GPROC running the LCF that supports the site under test using the rlogin command. At the prompt Type: fil create tag 10501h
Filter 10501h is created.

5. Type: fil start *
Filter * is started.
6. Set up a mobile to land or land to mobile call and monitor the filter output. The following message is displayed:
FILTER: SRC: pid: 10 mbid: 0002 cpu: 0119 subsys: 01 tag: 00010501 len:0014 DEST: function: 0009 instance: 001b mbid: 0003 TIME: 96942.975s data:00.7b.60.00.0f.00.0d.01.0b.03.01.08.01.07.02.06.00.06.01.00.05
The last two bytes of the data displayed (in hexadecimal) indicate the CIC in use. Check the quality of the call and, if good, check off the CIC number on the checklist on the next page. If the quality is bad, note the CIC number and retest. The last two bytes in the example show a call on CIC 05 (hexadecimal). Repeat this step until all CICs have been tested. 7. At the RAM EMON prompt type: fil stop *
Filter * is stopped.
8. At the RAM EMON prompt type: fil delete *
Filter * is deleted.
9. At the RAM EMON prompt type: fil list If any filters are shown delete them using the fil delete command. 10. 11. Log out of the BSC. Report the result of the integration and any anomalies to the OMC operator.

31st Jul 01
68P02901W43-J
717
GSM-100-423
CIC checklist
Check off good quality calls on the CIC checklist:
Slot no. 00 01 00 02 00 03 00 04 00 05 00 06 00 07 00 08 00 09
Slot no. 00 21 00 22 00 23 00 24 00 25 00 26 00 27 00 28 00 29
Slot no. 00 41 00 42 00 43 00 44 00 45 00 46 00 47 00 48 00 49
Slot no. 00 61 00 62 00 63 00 64 00 65 00 66 00 67 00 68 00 69
Slot no. 00 81 00 82 00 83 00 84 00 85 00 86 00 87 00 88 00 89
Slot no.
Slot no.
Slot no.
Slot no.
Slot no. 01 21 01 22 01 23 01 24 01 25 01 26 01 27 01 28 01 29
00 A1 00 C1 00 E1 01 01 00 A2 00 C2 00 E2 01 02 00 A3 00 C3 00 E3 01 03 00 A4 00 C4 00 E4 01 04 00 A5 00 C5 00 E5 01 05 00 A6 00 C6 00 E6 01 06 00 A7 00 C7 00 E7 01 07 00 A8 00 C8 00 E8 01 08 00 A9 00 C9 00 E9 01 09
00 0A 00 2A 00 4A 00 6A 00 8A 00 AA 00 CA 00 EA 01 0A 01 2A 00 0B 00 2B 00 4B 00 6B 00 8B 00 AB 00 CB 00 EB 01 0B 01 2B 00 0C 00 2C 00 4C 00 6C 00 8C 00 AC 00 CC 00 EC 01 0C 01 2C 00 0D 00 2D 00 4D 00 6D 00 8D 00 AD 00 CD 00 ED 01 0D 01 2D 00 0E 00 2E 00 4E 00 6E 00 8E 00 AE 00 CE 00 EE 01 0E 01 2E 00 0F 00 11 00 12 00 13 00 14 00 15 00 16 00 17 00 18 00 19 00 2F 00 31 00 32 00 33 00 34 00 35 00 36 00 37 00 38 00 39 00 4F 00 51 00 52 00 53 00 54 00 55 00 56 00 57 00 58 00 59 00 6F 00 71 00 72 00 73 00 74 00 75 00 76 00 77 00 78 00 79 00 8F 00 91 00 92 00 93 00 94 00 95 00 96 00 97 00 98 00 99 00 AF 00 CF 00 EF 01 0F 00 B1 00 D1 00 F1 00 B2 00 D2 00 F2 00 B3 00 D3 00 F3 00 B4 00 D4 00 F4 00 B5 00 D5 00 F5 00 B6 00 D6 00 F6 00 B7 00 D7 00 F7 00 B8 00 D8 00 F8 00 B9 00 D9 00 F9 01 11 01 12 01 13 01 14 01 15 01 16 01 17 01 18 01 19 01 2F 01 31 01 32 01 33 01 34 01 35 01 36 01 37 01 38 01 39
00 1A 00 3A 00 5A 00 7A 00 9A 00 BA 00 DA 00 FA 01 1A 01 3A 00 1B 00 3B 00 5B 00 7B 00 9B 00 BB 00 DB 00 FB 01 1B 01 3B 00 1C 00 3C 00 5C 00 7C 00 9C 00 BC 00 DC 00 FC 01 1C 01 3C 00 1D 00 3D 00 5D 00 7D 00 9D 00 BD 00 DD 00 FD 01 1D 01 3D 00 1E 00 3E 00 5E 00 7E 00 9E 00 BE 00 DE 00 FE 01 1E 01 3E 00 1F 00 3F 00 5F 00 7F 00 9F 00 BF 00 DF 00 FF 01 1F 01 3F
718
31st Jul 01
GSM-100-423
Calibrating the M-Cellaccess or Horizonoffice GCLK

Introduction
Follow this procedure to calibrate the GCLK in the field. The GCLK must be calibrated when more than one frame slip per hour is observed or when the GCLK is phase locked to the E1/T1 serial data stream and the system requests calibration. CAUTION The GCLK must be calibrated only by fully trained GSM qualified staff. Do not attempt this procedure under any circumstances unless the test equipment listed below is available.
Test equipment
The following test equipment is required: S S S S S S S An IBM-compatible personal computer (PC). A 9-way to 25-way cable. A Rubidium standard. A universal counter Hewlett Packard Model HP5385A or equivalent. A screened coaxial cable BNC to 2 mm multicontact AG connector. New calibration sticker(s). A non-ferrous tuning tool.
Commands
The following commands must be used to calibrate the GCLK: Command disp_equipment state disp_element phase_lock_gclk # chg_element phase_lock_gclk * # clear_gclk_avgs # * Function Displays the active equipment at a specified site. Displays the status of specified devices or functions. Shows the status of the phase lock function. # is the site id. Turns the phase lock function on or off, where * is the flag and is 0 for off and 1 for on, and # is the site id. Clears LTA values in memory for a specified GCLK. Where # is location and * is the gclk id.

31st Jul 01
68P02901W43-J
719
GSM-100-423
Procedure
Before attempting this procedure record the board serial number, date of last calibration and present frequency on the calibration record shown at the end of this section, and remove the old calibration stickers from the GCLK front panels. Consult the site specific documentation to determine the BSC/BTS configuration and cage slot allocation.
Test preparation
Proceed as follows: 1. 2. 3. 4. 5. 6. Log in to the required BSC, either at the BSC or via the OMC. If all commands are to be made at the OMC MMI, go to step 5. Connect the serial A port on the PC to a GPROC/GPROC2 TTY port using the 9 to 25-way cable. At the PC start the terminal emulator program. Connect the output from the 10 MHz standard to the reference input of the frequency counter, select external standard. Set the frequency gate time to 10 second and set the display to give 10 significant digits.
Phase-lock check
1. Check to see if phase lock is on, at the CUST MMI prompt type: disp_element phase_lock_gclk # Where: # is: location (0 to 100, or bsc)
This gives the status of phase lock at the site, 0 is shown for phase lock off and 1 is shown for phase lock on. 2. If phase lock is on, at the OMC/BSC CUST MMI prompt type: NOTE This command can only be made at the BSC or OMC. chg_element phase_lock_gclk 0 # Where: # is: location (0 to 100, or bsc)
This turns off the phase lock to the selected site.
Clearing Long Term Average (LTA) values

1. At the CUST MMI prompt type: disp_equipment # Where: # is: location (0 to 100, or bsc)
This gives the device id of the GCLKs. Installation & Configuration: BSS Optimization 68P02901W43-J
720
31st Jul 01
GSM-100-423
2.
At the OMC/BSC CUST MMI prompt type: state # GCLK * * * Where: # * * * This displays the status for the GCLK. is: location (0 to 100, or bsc) dev/func id dev/func id dev/func id
3.
At the OMC/BSC CUST MMI prompt type: NOTE This command can only be made at the BSC or OMC. clear_gclk_avgs # Where: # is: location (0 to 100, or bsc)
The system will respond with:

Enter the gclk_id:
Type in 0 or 1. This clears the LTA values for the specified GCLK.
GCLK frequency adjustment

1. 2. 3. Connect the frequency counter to the front panel 16.384 MHz connection of the GCLK. Connect the cable to the input port of the frequency counter and the jack plug end to the front panel of the GCLK 16.384 MHz output and ground respectively. Using a non-ferrous tuning tool, adjust the potentiometer labelled FREQ ADJUST on the GCLK to 16.384 MHz. The GSM specified tolerance is +/ 0.8 Hz, although it is desirable (and should be possible) to adjust the frequency more accurately than this. This reads as 16.384 000 00 on the frequency counter. Adjusting the potentiometer clockwise increases the frequency and anticlockwise decreases the frequency. Repeat step 1 to step 3 if the other GCLK is to be calibrated. 4. If phase locking of the GCLK(S) at the site is required type at the OMC or BSC: NOTE This command can only be made at the BSC or OMC. chg_element phase_lock_gclk 1 # Where: # is: location (0 to 100, or bsc)
This turns the phase lock on for the specified location. 5. Place a new calibration sticker, indicating the date of calibration, over the potentiometer labelled FREQ ADJUST on each calibrated GCLK.

31st Jul 01
68P02901W43-J
721
GSM-100-423
GCLK calibration record form

The GCLK calibration record form is shown below:
SITE NAME ........................................ SITE ID .............................................. TESTERS NAMES ..................................... .....................................
SERIAL NUMBER OF BOARD
DATE
DATE OF LAST CALIBRATION
FREQUENCY BEFORE CALIBRATION
722
31st Jul 01
Chapter 8
Base site integration

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 8 Base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reason for base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site using logging software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site without logging software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrating the base site with no connection to the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining channel/timeslot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra/inter-cell handover tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 81 82 82 82 82 82 83 84 85 85 85 85 85 86 87 88 88 88 88 88 89 810

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Introduction to base site integration
Introduction to base site integration

Reason for base site integration
Once a base site has been installed and its hardware optimized, the base site call handling qualities must be tested and all traffic channels available for call processing must be established. WARNING Hazardous voltages in excess of 50 V dc exist inside 48 V and 60 V cabinets. Use extreme caution when working on a cabinet with power applied. Remove all rings, watches and other jewellery.
In this chapter
This chapter details three ways of integrating a GSM base site: S S S When logging software such as LOMS is available. When logging software is not available. When the base site is not connected to a mobile switching centre (MSC). NOTE In this chapter transceiver is used to mean DRCU, DRCUII, DRCU3, SCU, TCU, TCU-B or CTU.

31st Jul 01
68P02901W43-J
81
Integrating the base site using logging software
GSM-100-423

Introduction
Follow this procedure to integrate a base site using logging software such as LOMS or TEMS.
Test equipment
The following test equipment is required when the base site is connected to an MSC: S S S S S An IBM-compatible personal computer (PC). Appropriate logging software such as LOMS or TEMS. The logging software must be compatible with the test mobile used. An interface cable to connect the test mobile to the PC. A suitable test mobile such as Orbitel 901 or Ericsson EH337 with a registered SIM card. Site integration forms.
Commands
No special commands are required.
Preparation for integration

To prepare for integration: 1. Contact the OMC and verify the frequencies and base station identity code (BSIC) allocated to the base site under test and ensure that the base site is active and transmitting. Ensure that both members of the team have: 3. 4. The base site landline telephone number. Each others test mobile telephone numbers.
2.
Position one member of the team at the base site. Connect the PC to the test mobile and start the logging software. Consult the software manufacturers user guide before using the logging software. Set the logging software to show: Serving cell. Serving and neighbouring cells. Dedicated channel. Radio environment.
82
31st Jul 01
GSM-100-423
5.
Open a log file before initiating any tests. The format for the log file filename is: 4 digit site id For example: 0037stre.LOG WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion. 4 character sitename.LOG
6.
Ensure that the engineer making the test calls (the mobile calling party) is stationed at least 1 km away from the base site(100 m from an M-Cellt site) and, on a sectored site, within the correct cell coverage area.
Obtaining channel/timeslot information

To obtain channel/timeslot information: 1. Using the serving cell and serving and neighbouring cell displays, ensure that: 2. 3. 4. The mobile is locked to sector A absolute radio frequency channel number (ARFCN). Sectors B and C ARFCNs and base station identity codes (BSIC) are displayed.
Note all sectors Rx levs on the site integration form. Set up a MS to land call. Using the dedicated channel display, note the following on the site integration form: ARFCN. Timeslot number. Subchannel number. Channel type. Channel mode.
5.
Using the radio environment display, note the following on the site integration form: Rx lev. Rx qual (in range 0 to 7, 0 = good 7 = bad). Timing advance (in range 0 to 2). Tx power (in range 0 to 15, 15 = minimum MS power).

31st Jul 01
68P02901W43-J
83
GSM-100-423
6.
Repeat steps 3 to 5 until all SD subchannels and TCH timeslots have been verified. NOTE Timeslot 0 of the BCCH carrier will not be allocated as a traffic channel. Timeslot 1 of the BCCH carrier may be configured as an SDCCH, in which case it will not be allocated as a traffic channel. Carrier 00 is on transceiver 0 (first transceiver in sector A or in omni-site). Carrier 01 is on transceiver 1 (second transceiver in sector A or in omni-site, or first transceiver in sector B). On sectors with more than one transceiver ensure that all transceiver timeslots are tested, non BCCH transceivers will be seen as next carrier in sequence.
7. 8. 9. 10.
If the cell has more than one transceiver carry out step 8 to step 10. If not, go to step 1. Request the OMC to take the transceiver with the BCCH carrier out of service. Check that the BCCH carrier is now available on another transceiver. Request the OMC to put the transceiver taken out of service in step 8 back into service.
Intra/inter-cell handover tests

To carry out handover tests: 1. Request the OMC to call the test mobile to verify correct cell allocation. WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion. 2. If the base site under test is sectored, continue the call made in step 1 while walking/driving into the next sector and verify that intra-cell handover is achieved and that the call is assigned to the correct carrier. Repeat step 1 to step 2 for all sectors. When all sectors have been tested, walk/drive in the opposite direction to ensure that handovers are correct to/from all cells. Make a call from the test mobile to the emergency operator and, where appropriate, request a record (for example a zone code). Note this on the site integration form. Make a call from the test mobile to the base site landline telephone, then walk/drive towards a neighbouring base site and verify, using the logging software, that an inter-cell handover is achieved. Once the handover has been achieved, walk/drive back towards the base site under test and verify that a handover is achieved. Verify that handovers are possible to all neighbouring sites. The OMC can supply ARFCN and BSIC of any neighbouring sites. When the test is complete, inform the OMC of any problems. Installation & Configuration: BSS Optimization 68P02901W43-J
3.
4.
5.
6. 7. 8.
84
31st Jul 01
GSM-100-423
Integrating the base site without logging software

Introduction
Follow this procedure to integrate a base site without using logging software.
Test equipment
The following test equipment is required when logging software is not available: S S S A test mobile with a registered SIM card. An engineering SIM card. Site integration forms.
Commands

To prepare for integration: 1. Contact the OMC and verify the frequencies and base station identity code (BSIC) allocated to the base site under test and ensure that the base site is active and transmitting. Ensure that both members of the team have: 3. The base site landline telephone number. Each others test mobile telephone numbers.
2.
Request the OMC to remotely log in (rlogin) to the base site under test and set: iir_mod 32 0Fch filter
4.
Position one member of the team at the base site. WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion.
5.
Ensure that the engineer making the test calls (the mobile calling party) is stationed at least 1 km away from the base site (100 m from an M-Cell site) and, on a sectored site, within the correct cell coverage area.

31st Jul 01
68P02901W43-J
85
GSM-100-423

To obtain channel/timeslot information: 1. 2. 3. 4. 5. 6. 7. Insert the engineering SIM card into the test mobile. Check that the MS can synchronize to the BCCH. Check that the frequency allocation is correct. Measure the signal strength of each BCCH carrier on the BTS. Replace the engineering SIM card with the registered SIM card. Set up a mobile to land call. Request the OMC to display and note: 8. Carrier number. Timeslot number. Subchannel number. Channel type.
Repeat step 6 and step 7 until all SD subchannels and TCH timeslots have been verified. NOTE Timeslot 0 of the BCCH carrier will not be allocated as a traffic channel. Timeslot 1 of the BCCH carrier may be configured as an SDCCH, in which case it will not be allocated as a traffic channel. Carrier 00 is on transceiver 0 (first transceiver in sector A or in omni-site) Carrier 01 is on transceiver 1 (second transceiver in sector A or in omni-site or first transceiver in sector B). On sectors with more than one transceiver ensure that all transceiver timeslots are tested, non BCCH transceivers will be seen as next carrier in sequence.
9. 10. 11. 12.
If the cell has more than one transceiver carry out steps 9 to 12. If not, go to step 1. Request the OMC to take the transceiver with the BCCH carrier out of service. Check that the BCCH carrier is now available on another transceiver. Request the OMC to put the transceiver taken out of service in step 10 back into service.
86
31st Jul 01
GSM-100-423

To carry out handover tests: 1. Request the OMC to call the test mobile to verify correct cell allocation. WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion. 2. If the base site under test is sectored, continue the call made in step 1 while walking/driving into the next sector and verify that intra-cell handover is achieved and that the call is assigned to the correct carrier. Repeat step 2 to step 2 for all sectors. On completion of the testing of all sectors, walk/drive in the reverse direction to ensure that handovers are correct to/from all cells. Make a call from the test mobile to the emergency operator and, where appropriate, request a record, for example, a zone code. Record this on the site integration form. If neighbour sites are available carry out step 6 to step 8. If not, go to step 9. Make a call from the test mobile to the base site landline telephone, the mobile calling party should then walk/drive toward a neighbouring base site and verify that an inter-cell handover is achieved. Use the engineering SIM card to verify neighbour site frequencies. Once the handover has been achieved, the mobile calling party should walk/drive back toward the base site under test and verify that a hand over is achieved. Request the OMC to remote login (rlogin) to the base site under test and set: iir_mod 32 00 10. On completion of the test, inform the OMC of any problems.
3.
4.
5. 6.
7. 8. 9.

31st Jul 01
68P02901W43-J
87
Integrating the base site with no connection to the MSC
GSM-100-423

Introduction
Follow this procedure to integrate a base site when the base site is not connected to a mobile switching centre (MSC).
Test equipment
The following test equipment is required when the base site is not connected to an MSC: S S S S A test mobile with a registered SIM card. An engineering SIM card. A Tekelec switch simulator. Site integration forms.
Commands

To prepare for integration: 1. Contact the OMC or BSC and verify the frequencies and base station identity code (BSIC) allocated to the base site under test and ensure that the base site is active and transmitting. Ensure that both members of the team have: 3. 4. The base site landline telephone number. Each others test mobile telephone numbers.
2.
Request the OMC to connect the E1/T1 lines from the BSC to a Tekelec so that the Tekelec can simulate the operation of an MSC. Request the OMC to remote login (rlogin) to the base site under test and set: iir_mod 32 0Fch
5.
Position one member of the team at the base site. WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion.
6.
Ensure that the engineer making the test calls (the mobile calling party) is stationed at least 1 km away from the base site (100 m from an M-Cell site) and, on a sectored site, within the correct cell coverage area.
88
31st Jul 01
GSM-100-423

To obtain channel/timeslot information: 1. 2. 3. 4. 5. 6. 7. Insert the engineering SIM card into the test mobile. Check that the MS can synchronize to the BCCH. Check that the frequency allocation is correct. Measure the signal strength of each BCCH carrier on the BTS. Replace the engineering SIM card with the registered SIM card. Set up a mobile to land call. Request the OMC to display and note: 8. Carrier number. Timeslot number. Subchannel number. Channel type.
Repeat step 6 and step 7 until all SD subchannels and TCH timeslots have been verified. NOTE Timeslot 0 of the BCCH carrier will not be allocated as a traffic channel. Timeslot 1 of the BCCH carrier may be configured as an SDCCH, in which case it will not be allocated as a traffic channel. Carrier 00 is on transceiver 0 (first transceiver in sector A or in omni-site) Carrier 01 is on transceiver 1 (second transceiver in sector A or in omni-site or first transceiver in sector B). On sectors with more than one transceiver ensure that all transceiver timeslots are tested, non BCCH transceivers will be seen as next carrier in sequence.
9. 10. 11. 12.
If the cell has more than one transceiver carry out step 10 to step 12. If not, go to step 1. Request the OMC to take the transceiver with the BCCH carrier out of service. Check that the BCCH carrier is now available on another transceiver. Request the OMC to put the transceiver taken out of service in step 10 back into service.

31st Jul 01
68P02901W43-J
89
GSM-100-423

To carry out handover tests: 1. Request the OMC to call the test mobile to verify correct cell allocation. WARNING Test calls must not be made by the driver of a motor vehicle while the vehicle is in motion. 2. If the base site under test is sectored, continue the call made in step 1 while walking/driving into the next sector and verify that intra-cell handover is achieved and that the call is assigned to the correct carrier. Repeat steps 2 to 2 for all sectors. On completion of the testing of all sectors, walk/drive in the reverse direction to ensure that handovers are correct to/from all cells. Make a call from the test mobile to the emergency operator and, where appropriate, request a record, for example, a zone code. Record this on the site integration form. If neighbour sites are available carry out steps 6 to 8. If not, go to step 9. Make a call from the test mobile to the base site landline telephone, the mobile calling party should then walk/drive toward a neighbouring base site and verify that an inter-cell handover is achieved. Use the engineering SIM card to verify neighbour site frequencies. Once the handover has been achieved, the mobile calling party should walk/drive back toward the base site under test and verify that a handover is achieved. Request the OMC to remote login (rlogin) to the base site under test and set: iir_mod 32 00 10. On completion of the test inform the OMC of any problems.
3.
4.
5. 6.
7. 8. 9.
810
31st Jul 01
Chapter 9
Channel numbers and frequencies

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 9 Channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channels and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PGSM channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended GSM channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCS1800 channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCS1900 channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
91 91 92 92 98 98 911 911 930 930

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Channels and frequencies
Channels and frequencies

Introduction
This chapter lists all channels and frequencies for each of the four channel types: S S S S PGSM EGSM The standard GSM frequency range. The extended GSM frequency range.
DCS1800 The standard 1800MHz frequency range. PCS1900 The higher frequency range allocated in countries such as the USA.

31st Jul 01
68P02901W43-J
91
PGSM channel numbers and frequencies
GSM-100-423

Channels
This section lists all the frequencies used in PGSM, with their channel numbers in both decimal and hexadecimal notation.
Channels 110
Table 9-1 shows the frequencies for PGSM channels 1 to 10. Table 9-1: PGSM channels 1 to 10 Channel number Decimal
1 2 3 4 5 6 7 8 9 10
Frequency (MHz) Receive

890.20 890.40 890.60 890.80 891.00 891.20 891.40 891.60 891.80 892.00
Hex.
01 02 03 04 05 06 07 08 09 0A
Transmit
935.20 935.40 935.60 935.80 936.00 936.20 936.40 936.60 936.80 937.00
Channels 1120
11 12 13 14 15 16 17 18 19 20

892.20 892.40 892.60 892.80 893.00 893.20 893.40 893.60 893.80 894.00
Hex.
0B 0C 0D 0E 0F 10 11 12 13 14
Transmit
937.20 937.40 937.60 937.80 938.00 938.20 938.40 938.60 938.80 939.00
92
31st Jul 01
GSM-100-423
Channels 2130
21 22 23 24 25 26 27 28 29 30

894.20 894.40 894.60 894.80 895.00 895.20 895.40 895.60 895.80 896.00
Hex.
15 16 17 18 19 1A 1B 1C 1D 1E
Transmit
939.20 939.40 939.60 939.80 940.00 940.20 940.40 940.60 940.80 941.00
Channels 3140
31 32 33 34 35 36 37 38 39 40

896.20 896.40 896.60 896.80 897.00 897.20 897.40 897.60 897.80 898.00
Hex.
1F 20 21 22 23 24 25 26 27 28
Transmit
941.20 941.40 941.60 941.80 942.00 942.20 942.40 942.60 942.80 943.00

31st Jul 01
68P02901W43-J
93
GSM-100-423
Channels 4150
41 42 43 44 45 46 47 48 49 50

898.20 898.40 898.60 898.80 899.00 899.20 899.40 899.60 899.80 900.00
Hex.
29 2A 2B 2C 2D 2E 2F 30 31 32
Transmit
943.20 943.40 943.60 943.80 944.00 944.20 944.40 944.60 944.80 945.00
Channels 5160
51 52 53 54 55 56 57 58 59 60

900.20 900.40 900.60 900.80 901.00 901.20 901.40 901.60 901.80 902.00
Hex.
33 34 35 36 37 38 39 3A 3B 3C
Transmit
945.20 945.40 945.60 945.80 946.00 946.20 946.40 946.60 946.80 947.00
94
31st Jul 01
GSM-100-423
Channels 6170
61 62 63 64 65 66 67 68 69 70

902.20 902.40 902.60 902.80 903.00 903.20 903.40 903.60 903.80 904.00
Hex.
3D 3E 3F 40 41 42 43 44 45 46
Transmit
947.20 947.40 947.60 947.80 948.00 948.20 948.40 948.60 948.80 949.00
Channels 7180
71 72 73 74 75 76 77 78 79 80

904.20 904.40 904.60 904.80 905.00 905.20 905.40 905.60 905.80 906.00
Hex.
47 48 49 4A 4B 4C 4D 4E 4F 50
Transmit
949.20 949.40 949.60 949.80 950.00 950.20 950.40 950.60 950.80 951.00

31st Jul 01
68P02901W43-J
95
GSM-100-423
Channels 8190
81 82 83 84 85 86 87 88 89 90

906.20 906.40 906.60 906.80 907.00 907.20 907.40 907.60 907.80 908.00
Hex.
51 52 53 54 55 56 57 58 59 5A
Transmit
951.20 951.40 951.60 951.80 952.00 952.20 952.40 952.60 952.80 953.00
Channels 91100
91 92 93 94 95 96 97 98 99 100

908.20 908.40 908.60 908.80 909.00 909.20 909.40 909.60 909.80 910.00
Hex.
5B 5C 5D 5E 5F 60 61 62 63 64
Transmit
953.20 953.40 953.60 953.80 954.00 954.20 954.40 954.60 954.80 955.00
96
31st Jul 01
GSM-100-423
Channels 101110
101 102 103 104 105 106 107 108 109 110

910.20 910.40 910.60 910.80 911.00 911.20 911.40 911.60 911.80 912.00
Hex.
65 66 67 68 69 6A 6B 6C 6D 6E
Transmit
955.20 955.40 955.60 955.80 956.00 956.20 956.40 956.60 956.80 957.00
Channels 111120
111 112 113 114 115 116 117 118 119 120

912.20 912.40 912.60 912.80 913.00 913.20 913.40 913.60 913.80 914.00
Hex.
6F 70 71 72 73 74 75 76 77 78
Transmit
957.20 957.40 957.60 957.80 958.00 958.20 958.40 958.60 958.80 959.00
Channels 121124
121 122 123 124

914.20 914.40 914.60 914.80
Hex.
79 7A 7B 7C
Transmit
959.20 959.40 959.60 959.80

31st Jul 01
68P02901W43-J
97
Extended GSM channel numbers and frequencies
GSM-100-423

Channels
This section lists all the extra frequencies used in Extended GSM (EGSM), with their channel numbers in both decimal and hexadecimal notation. EGSM also uses all frequencies listed in GSM channel numbers and frequencies.
Channels 975984
Table 9-14 shows the frequencies for EGSM channels 975 to 984. Table 9-14: EGSM channels 975 to 984 Channel number Decimal
975 976 977 978 979 980 981 982 983 984

880.20 880.40 880.60 880.80 881.00 881.20 881.40 881.60 881.80 882.00
Hex.
3CF 3D0 3D1 3D2 3D3 3D4 3D5 3D6 3D7 3D8
Transmit
925.20 925.40 925.60 925.80 926.00 926.20 926.40 926.60 926.80 927.00
Channels 985994
985 986 987 988 989 990 991 992 993 994

882.20 882.40 882.60 882.80 883.00 883.20 883.40 883.60 883.80 884.00
Hex.
3D9 3DA 3DB 3DC 3DD 3DE 3DF 3E0 3E1 3E2
Transmit
927.20 927.40 927.60 927.80 928.00 928.20 928.40 928.60 928.80 929.00
98
31st Jul 01
GSM-100-423
Channels 9951004
995 996 997 998 999 1000 1001 1002 1003 1004

884.20 884.40 884.60 884.80 885.00 885.20 885.40 885.60 885.80 886.00
Hex.
3E3 3E4 3E5 3E6 3E7 3E8 3E9 3EA 3EB 3EC
Transmit
929.20 929.40 929.60 929.80 930.00 930.20 930.40 930.60 930.80 931.00
Channels 10051014
1005 1006 1007 1008 1009 1010 1011 1012 1013 1014

886.20 886.40 886.60 886.80 887.00 887.20 887.40 887.60 887.80 888.00
Hex.
3ED 3EE 3EF 3F0 3F1 3F2 3F3 3F4 3F5 3F6
Transmit
931.20 931.40 931.60 931.80 932.00 932.20 932.40 932.60 932.80 933.00

31st Jul 01
68P02901W43-J
99
GSM-100-423
Channels 10150
1015 1016 1017 1018 1019 1020 1021 1022 1023 0

888.20 888.40 888.60 888.80 889.00 889.20 889.40 889.60 889.80 890.00
Hex.
3F7 3F8 3F9 3FA 3FB 3FC 3FD 3FE 3FF 0
Transmit
933.20 933.40 933.60 933.80 934.00 934.20 934.40 934.60 934.80 935.00
910
31st Jul 01
GSM-100-423
DCS1800 channel numbers and frequencies

Channels
This section lists the frequencies used in DCS1800, with their channel numbers in both decimal and hexadecimal notation.
Channels 512520
Table 9-19 shows the frequencies for DCS1800 channels 512 to 520. Table 9-19: DCS 1800 channels 512 to 520 Channel number Decimal
512 513 514 515 516 517 518 519 520

1710.2 1710.4 1710.6 1710.8 1711.0 1711.2 1711.4 1711.6 1711.8
Hex.
200 201 202 203 204 205 206 207 208
Transmit
1805.2 1805.4 1805.6 1805.8 1806.0 1806.2 1806.4 1806.6 1806.8
Channels 521530
521 522 523 524 525 526 527 528 529 530

1712.0 1712.2 1712.4 1712.6 1712.8 1713.0 1713.2 1713.4 1713.6 1713.8
Hex.
209 20A 20B 20C 20D 20E 20F 210 211 212
Transmit
1807.0 1807.2 1807.4 1807.6 1807.8 1808.0 1808.2 1808.4 1808.6 1808.8

31st Jul 01
68P02901W43-J
911
GSM-100-423
Channels 531540
531 532 533 534 535 536 537 538 539 540

1714.0 1714.2 1714.4 1714.6 1714.8 1715.0 1715.2 1715.4 1715.6 1715.8
Hex.
213 214 215 216 217 218 219 21A 21B 21C
Transmit
1809.0 1809.2 1809.4 1809.6 1809.8 1810.0 1810.2 1810.4 1810.6 1810.8
Channels 541550
541 542 543 544 545 546 547 548 549 550

1716.0 1716.2 1716.4 1716.6 1716.8 1717.0 1717.2 1717.4 1717.6 1717.8
Hex.
21D 21E 21F 220 221 222 223 224 225 226
Transmit
1811.0 1811.2 1811.4 1811.6 1811.8 1812.0 1812.2 1812.4 1812.6 1812.8
912
31st Jul 01
GSM-100-423
Channels 551560
551 552 553 554 555 556 557 558 559 560

1718.0 1718.2 1718.4 1718.6 1718.8 1719.0 1719.2 1719.4 1719.6 1719.8
Hex.
227 228 229 22A 22B 22C 22D 22E 22F 230
Transmit
1813.0 1813.2 1813.4 1813.6 1813.8 1814.0 1814.2 1814.4 1814.6 1814.8
Channels 561570
561 562 563 564 565 566 567 568 569 570

1720.0 1720.2 1720.4 1720.6 1720.8 1721.0 1721.2 1721.4 1721.6 1721.8
Hex.
231 232 233 234 235 236 237 238 239 23A
Transmit
1815.0 1815.2 1815.4 1815.6 1815.8 1816.0 1816.2 1816.4 1816.6 1816.8

31st Jul 01
68P02901W43-J
913
GSM-100-423
Channels 571580
571 572 573 574 575 576 577 578 579 580

1722.0 1722.2 1722.4 1722.6 1722.8 1723.0 1723.2 1723.4 1723.6 1723.8
Hex.
23B 23C 23D 23E 23F 240 241 242 243 244
Transmit
1817.0 1817.2 1817.4 1817.6 1817.8 1818.0 1818.2 1818.4 1818.6 1818.8
Channels 581590
581 582 583 584 585 586 587 588 589 590

1724.0 1724.2 1724.4 1724.6 1724.8 1725.0 1725.2 1725.4 1725.6 1725.8
Hex.
245 246 247 248 249 24A 24B 24C 24D 24E
Transmit
1819.0 1819.2 1819.4 1819.6 1819.8 1820.0 1820.2 1820.4 1820.6 1820.8
914
31st Jul 01
GSM-100-423
Channels 591600
591 592 593 594 595 596 597 598 599 600

1726.0 1726.2 1726.4 1726.6 1726.8 1727.0 1727.2 1727.4 1727.6 1727.8
Hex.
24F 250 251 252 253 254 255 256 257 258
Transmit
1821.0 1821.2 1821.4 1821.6 1821.8 1822.0 1822.2 1822.4 1822.6 1822.8
Channels 601610
601 602 603 604 605 606 607 608 609 610

1728.0 1728.2 1728.4 1728.6 1728.8 1729.0 1729.2 1729.4 1729.6 1729.8
Hex.
259 25A 25B 25C 25D 25E 25F 260 261 262
Transmit
1823.0 1823.2 1823.4 1823.6 1823.8 1824.0 1824.2 1824.4 1824.6 1824.8

31st Jul 01
68P02901W43-J
915
GSM-100-423
Channels 611620
611 612 613 614 615 616 617 618 619 620

1730.0 1730.2 1730.4 1730.6 1730.8 1731.0 1731.2 1731.4 1731.6 1731.8
Hex.
263 264 265 266 267 268 269 26A 26B 26C
Transmit
1825.0 1825.2 1825.4 1825.6 1825.8 1826.0 1826.2 1826.4 1826.6 1826.8
Channels 621630
621 622 623 624 625 626 627 628 629 630

1732.0 1732.2 1732.4 1732.6 1732.8 1733.0 1733.2 1733.4 1733.6 1733.8
Hex.
26D 26E 26F 270 271 272 273 274 275 276
Transmit
1827.0 1827.2 1827.4 1827.6 1827.8 1828.0 1828.2 1828.4 1828.6 1828.8
916
31st Jul 01
GSM-100-423
Channels 631640
631 632 633 634 635 636 637 638 639 640

1734.0 1734.2 1734.4 1734.6 1734.8 1735.0 1735.2 1735.4 1735.6 1735.8
Hex.
277 278 279 27A 27B 27C 27D 27E 27F 280
Transmit
1829.0 1829.2 1829.4 1829.6 1829.8 1830.0 1830.2 1830.4 1830.6 1830.8
Channels 641650
641 642 643 644 645 646 647 648 649 650

1736.0 1736.2 1736.4 1736.6 1736.8 1737.0 1737.2 1737.4 1737.6 1737.8
Hex.
281 282 283 284 285 286 287 288 289 28A
Transmit
1831.0 1831.2 1831.4 1831.6 1831.8 1832.0 1832.2 1832.4 1832.6 1832.8

31st Jul 01
68P02901W43-J
917
GSM-100-423
Channels 651660
651 652 653 654 655 656 657 658 659 660

1738.0 1738.2 1738.4 1738.6 1738.8 1739.0 1739.2 1739.4 1739.6 1739.8
Hex.
28B 28C 28D 28E 28F 290 291 292 293 294
Transmit
1833.0 1833.2 1833.4 1833.6 1833.8 1834.0 1834.2 1834.4 1834.6 1834.8
Channels 661670
661 662 663 664 665 666 667 668 669 670

1740.0 1740.2 1740.4 1740.6 1740.8 1741.0 1741.2 1741.4 1741.6 1741.8
Hex.
295 296 297 298 299 29A 29B 29C 29D 29E
Transmit
1835.0 1835.2 1835.4 1835.6 1835.8 1836.0 1836.2 1836.4 1836.6 1836.8
918
31st Jul 01
GSM-100-423
Channels 671680
671 672 673 674 675 676 677 678 679 680

1742.0 1742.2 1742.4 1742.6 1742.8 1743.0 1743.2 1743.4 1743.6 1743.8
Hex.
29F 2A0 2A1 2A2 2A3 2A4 2A5 2A6 2A7 2A8
Transmit
1837.0 1837.2 1837.4 1837.6 1837.8 1838.0 1838.2 1838.4 1838.6 1838.8
Channels 681690
681 682 683 684 685 686 687 688 689 690

1744.0 1744.2 1744.4 1744.6 1744.8 1745.0 1745.2 1745.4 1745.6 1745.8
Hex.
2A9 2AA 2AB 2AC 2AD 2AE 2AF 2B0 2B1 2B2
Transmit
1839.0 1839.2 1839.4 1839.6 1839.8 1840.0 1840.2 1840.4 1840.6 1840.8

31st Jul 01
68P02901W43-J
919
GSM-100-423
Channels 691700
691 692 693 694 695 696 697 698 699 700

1746.0 1746.2 1746.4 1746.6 1746.8 1747.0 1747.2 1747.4 1747.6 1747.8
Hex.
2B3 2B4 2B5 2B6 2B7 2B8 2B9 2BA 2BB 2BC
Transmit
1841.0 1841.2 1841.4 1841.6 1841.8 1842.0 1842.2 1842.4 1842.6 1842.8
Channels 701710
701 702 703 704 705 706 707 708 709 710

1748.0 1748.2 1748.4 1748.6 1748.8 1749.0 1749.2 1749.4 1749.6 1749.8
Hex.
2BD 2BE 2BF 2C0 2C1 2C2 2C3 2C4 2C5 2C6
Transmit
1843.0 1843.2 1843.4 1843.6 1843.8 1844.0 1844.2 1844.4 1844.6 1844.8
920
31st Jul 01
GSM-100-423
Channels 711720
711 712 713 714 715 716 717 718 719 720

1750.0 1750.2 1750.4 1750.6 1750.8 1751.0 1751.2 1751.4 1751.6 1751.8
Hex.
2C7 2C8 2C9 2CA 2CB 2CC 2CD 2CE 2CF 2D0
Transmit
1845.0 1845.2 1845.4 1845.6 1845.8 1846.0 1846.2 1846.4 1846.6 1846.8
Channels 721730
721 722 723 724 725 726 727 728 729 730

1752.0 1752.2 1752.4 1752.6 1752.8 1753.0 1753.2 1753.4 1753.6 1753.8
Hex.
2D1 2D2 2D3 2D4 2D5 2D6 2D7 2D8 2D9 2DA
Transmit
1847.0 1847.2 1847.4 1847.6 1847.8 1848.0 1848.2 1848.4 1848.6 1848.8

31st Jul 01
68P02901W43-J
921
GSM-100-423
Channels 731740
731 732 733 734 735 736 737 738 739 740

1754.0 1754.2 1754.4 1754.6 1754.8 1755.0 1755.2 1755.4 1755.6 1755.8
Hex.
2DB 2DC 2DD 2DE 2DF 2E0 2E1 2E2 2E3 2E4
Transmit
1849.0 1849.2 1849.4 1849.6 1849.8 1850.0 1850.2 1850.4 1850.6 1850.8
Channels 741750
741 742 743 744 745 746 747 748 749 750

1756.0 1756.2 1756.4 1756.6 1756.8 1757.0 1757.2 1757.4 1757.6 1757.8
Hex.
2E5 2E6 2E7 2E8 2E9 2EA 2EB 2EC 2ED 2EE
Transmit
1851.0 1851.2 1851.4 1851.6 1851.8 1852.0 1852.2 1852.4 1852.6 1852.8
922
31st Jul 01
GSM-100-423
Channels 751760
751 752 753 754 755 756 757 758 759 760

1758.0 1758.2 1758.4 1758.6 1758.8 1759.0 1759.2 1759.4 1759.6 1759.8
Hex.
2EF 2F0 2F1 2F2 2F3 2F4 2F5 2F6 2F7 2F8
Transmit
1853.0 1853.2 1853.4 1853.6 1853.8 1854.0 1854.2 1854.4 1854.6 1854.8
Channels 761770
761 762 763 764 765 766 767 768 769 770

1760.0 1760.2 1760.4 1760.6 1760.8 1761.0 1761.2 1761.4 1761.6 1761.8
Hex.
2F9 2FA 2FB 2FC 2FD 2FE 2FF 300 301 302
Transmit
1855.0 1855.2 1855.4 1855.6 1855.8 1856.0 1856.2 1856.4 1856.6 1856.8

31st Jul 01
68P02901W43-J
923
GSM-100-423
Channels 771780
771 772 773 774 775 776 777 778 779 780

1762.0 1762.2 1762.4 1762.6 1762.8 1763.0 1763.2 1763.4 1763.6 1763.8
Hex.
303 304 305 306 307 308 309 30A 30B 30C
Transmit
1857.0 1857.2 1857.4 1857.6 1857.8 1858.0 1858.2 1858.4 1858.6 1858.8
Channels 781790
781 782 783 784 785 786 787 788 789 790

1764.0 1764.2 1764.4 1764.6 1764.8 1765.0 1765.2 1765.4 1765.6 1765.8
Hex.
30D 30E 30F 310 311 312 313 314 315 316
Transmit
1859.0 1859.2 1859.4 1859.6 1859.8 1860.0 1860.2 1860.4 1860.6 1860.8
924
31st Jul 01
GSM-100-423
Channels 791800
791 792 793 794 795 796 797 798 799 800

1766.0 1766.2 1766.4 1766.6 1766.8 1767.0 1767.2 1767.4 1767.6 1767.8
Hex.
317 318 319 31A 31B 31C 31D 31E 31F 320
Transmit
1861.0 1861.2 1861.4 1861.6 1861.8 1862.0 1862.2 1862.4 1862.6 1862.8
Channels 801810
801 802 803 804 805 806 807 808 809 810

1768.0 1768.2 1768.4 1768.6 1768.8 1769.0 1769.2 1769.4 1769.6 1769.8
Hex.
321 322 323 324 325 326 327 328 329 32A
Transmit
1863.0 1863.2 1863.4 1863.6 1863.8 1864.0 1864.2 1864.4 1864.6 1864.8

31st Jul 01
68P02901W43-J
925
GSM-100-423
Channels 811820
811 812 813 814 815 816 817 818 819 820

1770.0 1770.2 1770.4 1770.6 1770.8 1771.0 1771.2 1771.4 1771.6 1771.8
Hex.
32B 32C 32D 32E 32F 330 331 332 333 334
Transmit
1865.0 1865.2 1865.4 1865.6 1865.8 1866.0 1866.2 1866.4 1866.6 1866.8
Channels 821830
821 822 823 824 825 826 827 828 829 830

1772.0 1772.2 1772.4 1772.6 1772.8 1773.0 1773.2 1773.4 1773.6 1773.8
Hex.
335 336 337 338 339 33A 33B 33C 33D 33E
Transmit
1867.0 1867.2 1867.4 1867.6 1867.8 1868.0 1868.2 1868.4 1868.6 1868.8
926
31st Jul 01
GSM-100-423
Channels 831840
831 832 833 834 835 836 837 838 839 840

1774.0 1774.2 1774.4 1774.6 1774.8 1775.0 1775.2 1775.4 1775.6 1775.8
Hex.
33F 340 341 342 343 344 345 346 347 348
Transmit
1869.0 1869.2 1869.4 1869.6 1869.8 1870.0 1870.2 1870.4 1870.6 1870.8
Channels 841850
841 842 843 844 845 846 847 848 849 850

1776.0 1776.2 1776.4 1776.6 1776.8 1777.0 1777.2 1777.4 1777.6 1777.8
Hex.
349 34A 34B 34C 34D 34E 34F 350 351 352
Transmit
1871.0 1871.2 1871.4 1871.6 1871.8 1872.0 1872.2 1872.4 1872.6 1872.8

31st Jul 01
68P02901W43-J
927
GSM-100-423
Channels 851860
851 852 853 854 855 856 857 858 859 860

1778.0 1778.2 1778.4 1778.6 1778.8 1779.0 1779.2 1779.4 1779.6 1779.8
Hex.
353 354 355 356 357 358 359 35A 35B 35C
Transmit
1873.0 1873.2 1873.4 1873.6 1873.8 1874.0 1874.2 1874.4 1874.6 1874.8
Channels 861870
861 862 863 864 865 866 867 868 869 870

1780.0 1780.2 1780.4 1780.6 1780.8 1781.0 1781.2 1781.4 1781.6 1781.8
Hex.
35D 35E 35F 360 361 362 363 364 365 366
Transmit
1875.0 1875.2 1875.4 1875.6 1875.8 1876.0 1876.2 1876.4 1876.6 1876.8
928
31st Jul 01
GSM-100-423
Channels 871880
871 872 873 874 875 876 877 878 879 880

1782.0 1782.2 1782.4 1782.6 1782.8 1783.0 1783.2 1783.4 1783.6 1783.8
Hex.
367 368 369 36A 36B 36C 36D 36E 36F 370
Transmit
1877.0 1877.2 1877.4 1877.6 1877.8 1878.0 1878.2 1878.4 1878.6 1878.8
Channels 881885
881 882 883 884 885

1784.0 1784.2 1784.4 1784.6 1784.8
Hex.
371 372 373 374 375
Transmit
1879.0 1879.2 1879.4 1879.6 1879.8

31st Jul 01
68P02901W43-J
929
PCS1900 channel numbers and frequencies
GSM-100-423

Channels
This section lists the frequencies used in PCS1900, with their channel numbers in both decimal and hexadecimal notation.
Channels 512520
Table 9-57 shows the frequencies for PCS1900 channels 512 to 520. Table 9-57: PCS 1900 channels 512 to 520 Channel number Decimal
512 513 514 515 516 517 518 519 520

1850.2 1850.4 1850.6 1850.8 1851.0 1851.2 1851.4 1851.6 1851.8
Hex.
200 201 202 203 204 205 206 207 208
Transmit
1930.2 1930.4 1930.6 1930.8 1931.0 1931.2 1931.4 1931.6 1931.8
Channels 521530
521 522 523 524 525 526 527 528 529 530

1852.0 1852.2 1852.4 1852.6 1852.8 1853.0 1853.2 1853.4 1853.6 1853.8
Hex.
209 20A 20B 20C 20D 20E 20F 210 211 212
Transmit
1932.0 1932.2 1932.4 1932.6 1932.8 1933.0 1933.2 1933.4 1933.6 1933.8
930
31st Jul 01
GSM-100-423
Channels 531540
531 532 533 534 535 536 537 538 539 540

1854.0 1854.2 1854.4 1854.6 1854.8 1855.0 1855.2 1855.4 1855.6 1855.8
Hex.
213 214 215 216 217 218 219 21A 21B 21C
Transmit
1934.0 1934.2 1934.4 1934.6 1934.8 1935.0 1935.2 1935.4 1935.6 1935.8
Channels 541550
541 542 543 544 545 546 547 548 549 550

1856.0 1856.2 1856.4 1856.6 1856.8 1857.0 1857.2 1857.4 1857.6 1857.8
Hex.
21D 21E 21F 220 221 222 223 224 225 226
Transmit
1936.0 1936.2 1936.4 1936.6 1936.8 1937.0 1937.2 1937.4 1937.6 1937.8

31st Jul 01
68P02901W43-J
931
GSM-100-423
Channels 551560
551 552 553 554 555 556 557 558 559 560

1858.0 1858.2 1858.4 1858.6 1858.8 1859.0 1859.2 1859.4 1859.6 1859.8
Hex.
227 228 229 22A 22B 22C 22D 22E 22F 230
Transmit
1938.0 1938.2 1938.4 1938.6 1938.8 1939.0 1939.2 1939.4 1939.6 1939.8
Channels 561570
561 562 563 564 565 566 567 568 569 570

1860.0 1860.2 1860.4 1860.6 1860.8 1861.0 1861.2 1861.4 1861.6 1861.8
Hex.
231 232 233 234 235 236 237 238 239 23A
Transmit
1940.0 1940.2 1940.4 1940.6 1940.8 1941.0 1941.2 1941.4 1941.6 1941.8
932
31st Jul 01
GSM-100-423
Channels 571580
571 572 573 574 575 576 577 578 579 580

1862.0 1862.2 1862.4 1862.6 1862.8 1863.0 1863.2 1863.4 1863.6 1863.8
Hex.
23B 23C 23D 23E 23F 240 241 242 243 244
Transmit
1942.0 1942.2 1942.4 1942.6 1942.8 1943.0 1943.2 1943.4 1943.6 1943.8
Channels 581590
581 582 583 584 585 586 587 588 589 590

1864.0 1864.2 1864.4 1864.6 1864.8 1865.0 1865.2 1865.4 1865.6 1865.8
Hex.
245 246 247 248 249 24A 24B 24C 24D 24E
Transmit
1944.0 1944.2 1944.4 1944.6 1944.8 1945.0 1945.2 1945.4 1945.6 1945.8

31st Jul 01
68P02901W43-J
933
GSM-100-423
Channels 591600
591 592 593 594 595 596 597 598 599 600

1866.0 1866.2 1866.4 1866.6 1866.8 1867.0 1867.2 1867.4 1867.6 1867.8
Hex.
24F 250 251 252 253 254 255 256 257 258
Transmit
1946.0 1946.2 1946.4 1946.6 1946.8 1947.0 1947.2 1947.4 1947.6 1947.8
Channels 601610
601 602 603 604 605 606 607 608 609 610

1868.0 1868.2 1868.4 1868.6 1868.8 1869.0 1869.2 1869.4 1869.6 1869.8
Hex.
259 25A 25B 25C 25D 25E 25F 260 261 262
Transmit
1948.0 1948.2 1948.4 1948.6 1948.8 1949.0 1949.2 1949.4 1949.6 1949.8
934
31st Jul 01
GSM-100-423
Channels 611620
611 612 613 614 615 616 617 618 619 620

1870.0 1870.2 1870.4 1870.6 1870.8 1871.0 1871.2 1871.4 1871.6 1871.8
Hex.
263 264 265 266 267 268 269 26A 26B 26C
Transmit
1950.0 1950.2 1950.4 1950.6 1950.8 1951.0 1951.2 1951.4 1951.6 1951.8
Channels 621630
621 622 623 624 625 626 627 628 629 630

1872.0 1872.2 1872.4 1872.6 1872.8 1873.0 1873.2 1873.4 1873.6 1873.8
Hex.
26D 26E 26F 270 271 272 273 274 275 276
Transmit
1952.0 1952.2 1952.4 1952.6 1952.8 1953.0 1953.2 1953.4 1953.6 1953.8

31st Jul 01
68P02901W43-J
935
GSM-100-423
Channels 631640
631 632 633 634 635 636 637 638 639 640

1874.0 1874.2 1874.4 1874.6 1874.8 1875.0 1875.2 1875.4 1875.6 1875.8
Hex.
277 278 279 27A 27B 27C 27D 27E 27F 280
Transmit
1954.0 1954.2 1954.4 1954.6 1954.8 1955.0 1955.2 1955.4 1955.6 1955.8
Channels 641650
641 642 643 644 645 646 647 648 649 650

1876.0 1876.2 1876.4 1876.6 1876.8 1877.0 1877.2 1877.4 1877.6 1877.8
Hex.
281 282 283 284 285 286 287 288 289 28A
Transmit
1956.0 1956.2 1956.4 1956.6 1956.8 1957.0 1957.2 1957.4 1957.6 1957.8
936
31st Jul 01
GSM-100-423
Channels 651660
651 652 653 654 655 656 657 658 659 660

1878.0 1878.2 1878.4 1878.6 1878.8 1879.0 1879.2 1879.4 1879.6 1879.8
Hex.
28B 28C 28D 28E 28F 290 291 292 293 294
Transmit
1958.0 1958.2 1958.4 1958.6 1958.8 1959.0 1959.2 1959.4 1959.6 1959.8
Channels 661670
661 662 663 664 665 666 667 668 669 670

1880.0 1880.2 1880.4 1880.6 1880.8 1881.0 1881.2 1881.4 1881.6 1881.8
Hex.
295 296 297 298 299 29A 29B 29C 29D 29E
Transmit
1960.0 1960.2 1960.4 1960.6 1960.8 1961.0 1961.2 1961.4 1961.6 1961.8

31st Jul 01
68P02901W43-J
937
GSM-100-423
Channels 671680
671 672 673 674 675 676 677 678 679 680

1882.0 1882.2 1882.4 1882.6 1882.8 1883.0 1883.2 1883.4 1883.6 1883.8
Hex.
29F 2A0 2A1 2A2 2A3 2A4 2A5 2A6 2A7 2A8
Transmit
1962.0 1962.2 1962.4 1962.6 1962.8 1963.0 1963.2 1963.4 1963.6 1963.8
Channels 681690
681 682 683 684 685 686 687 688 689 690

1884.0 1884.2 1884.4 1884.6 1884.8 1885.0 1885.2 1885.4 1885.6 1885.8
Hex.
2A9 2AA 2AB 2AC 2AD 2AE 2AF 2B0 2B1 2B2
Transmit
1964.0 1964.2 1964.4 1964.6 1964.8 1965.0 1965.2 1965.4 1965.6 1965.8
938
31st Jul 01
GSM-100-423
Channels 691700
691 692 693 694 695 696 697 698 699 700

1886.0 1886.2 1886.4 1886.6 1886.8 1887.0 1887.2 1887.4 1887.6 1887.8
Hex.
2B3 2B4 2B5 2B6 2B7 2B8 2B9 2BA 2BB 2BC
Transmit
1966.0 1966.2 1966.4 1966.6 1966.8 1967.0 1967.2 1967.4 1967.6 1967.8
Channels 701710
701 702 703 704 705 706 707 708 709 710

1888.0 1888.2 1888.4 1888.6 1888.8 1889.0 1889.2 1889.4 1889.6 1889.8
Hex.
2BD 2BE 2BF 2C0 2C1 2C2 2C3 2C4 2C5 2C6
Transmit
1968.0 1968.2 1968.4 1968.6 1968.8 1969.0 1969.2 1969.4 1969.6 1969.8

31st Jul 01
68P02901W43-J
939
GSM-100-423
Channels 711720
711 712 713 714 715 716 717 718 719 720

1890.0 1890.2 1890.4 1890.6 1890.8 1891.0 1891.2 1891.4 1891.6 1891.8
Hex.
2C7 2C8 2C9 2CA 2CB 2CC 2CD 2CE 2CF 2D0
Transmit
1970.0 1970.2 1970.4 1970.6 1970.8 1971.0 1971.2 1971.4 1971.6 1971.8
Channels 721730
721 722 723 724 725 726 727 728 729 730

1892.0 1892.2 1892.4 1892.6 1892.8 1893.0 1893.2 1893.4 1893.6 1893.8
Hex.
2D1 2D2 2D3 2D4 2D5 2D6 2D7 2D8 2D9 2DA
Transmit
1972.0 1972.2 1972.4 1972.6 1972.8 1973.0 1973.2 1973.4 1973.6 1973.8
940
31st Jul 01
GSM-100-423
Channels 731740
731 732 733 734 735 736 737 738 739 740

1894.0 1894.2 1894.4 1894.6 1894.8 1895.0 1895.2 1895.4 1895.6 1895.8
Hex.
2DB 2DC 2DD 2DE 2DF 2E0 2E1 2E2 2E3 2E4
Transmit
1974.0 1974.2 1974.4 1974.6 1974.8 1975.0 1975.2 1975.4 1975.6 1975.8
Channels 741750
741 742 743 744 745 746 747 748 749 750

1896.0 1896.2 1896.4 1896.6 1896.8 1897.0 1897.2 1897.4 1897.6 1897.8
Hex.
2E5 2E6 2E7 2E8 2E9 2EA 2EB 2EC 2ED 2EE
Transmit
1976.0 1976.2 1976.4 1976.6 1976.8 1977.0 1977.2 1977.4 1977.6 1977.8

31st Jul 01
68P02901W43-J
941
GSM-100-423
Channels 751760
751 752 753 754 755 756 757 758 759 760

1898.0 1898.2 1898.4 1898.6 1898.8 1899.0 1899.2 1899.4 1899.6 1899.8
Hex.
2EF 2F0 2F1 2F2 2F3 2F4 2F5 2F6 2F7 2F8
Transmit
1978.0 1978.2 1978.4 1978.6 1978.8 1979.0 1979.2 1979.4 1979.6 1979.8
Channels 761770
761 762 763 764 765 766 767 768 769 770

1900.0 1900.2 1900.4 1900.6 1900.8 1901.0 1901.2 1901.4 1901.6 1901.8
Hex.
2F9 2FA 2FB 2FC 2FD 2FE 2FF 300 301 302
Transmit
1980.0 1980.2 1980.4 1980.6 1980.8 1981.0 1981.2 1981.4 1981.6 1981.8
942
31st Jul 01
GSM-100-423
Channels 771780
771 772 773 774 775 776 777 778 779 780

1902.0 1902.2 1902.4 1902.6 1902.8 1903.0 1903.2 1903.4 1903.6 1903.8
Hex.
303 304 305 306 307 308 309 30A 30B 30C
Transmit
1982.0 1982.2 1982.4 1982.6 1982.8 1983.0 1983.2 1983.4 1983.6 1983.8
Channels 781790
781 782 783 784 785 786 787 788 789 790

1904.0 1904.2 1904.4 1904.6 1904.8 1905.0 1905.2 1905.4 1905.6 1905.8
Hex.
30D 30E 30F 310 311 312 313 314 315 316
Transmit
1984.0 1984.2 1984.4 1984.6 1984.8 1985.0 1985.2 1985.4 1985.6 1985.8

31st Jul 01
68P02901W43-J
943
GSM-100-423
Channels 791800
791 792 793 794 795 796 797 798 799 800

1906.0 1906.2 1906.4 1906.6 1906.8 1907.0 1907.2 1907.4 1907.6 1907.8
Hex.
317 318 319 31A 31B 31C 31D 31E 31F 320
Transmit
1986.0 1986.2 1986.4 1986.6 1986.8 1987.0 1987.2 1987.4 1987.6 1987.8
Channels 801810
801 802 803 804 805 806 807 808 809 810

1908.0 1908.2 1908.4 1908.6 1908.8 1909.0 1909.2 1909.4 1909.6 1909.8
Hex.
321 322 323 324 325 326 327 328 329 32A
Transmit
1988.0 1988.2 1988.4 1988.6 1988.8 1989.0 1989.2 1989.4 1989.6 1989.8
944
31st Jul 01
Chapter 10
Network optimization

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 10 Network optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network optimization chapter topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network optimization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stages in an optimization exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the drive test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . optimizing for worst case interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive test process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data collection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data collection process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FICS explained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification of test calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnosing drive test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysis of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High handover failure rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High set-up failure rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High dropped call rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No audio calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Noisy calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Poor quality of service calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High blocking cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio call faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean time between drops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive test report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementation of a drive test recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . Effects of a recommendation implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Residual defect investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
101 101 101 102 102 103 104 104 104 106 108 108 108 109 109 109 1010 1011 1011 1011 1012 1013 1014 1016 1016 1016 1016 1018 1019 1020 1020 1020 1021

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
Chapter overview
Chapter overview
Introduction
This chapter describes the process and procedures involved in the optimization of a network by drive testing. Within this chapter are details on how to carry out drive testing and guidance on analysing logs and resolving problems. Discussed are the techniques involved in the optimization of a macro-cellular system, however these could also apply to a micro-cellular system as well. The same techniques apply to any frequency band, although there will be significant differences in the RF propagation properties.
Network optimization chapter topics

The following network optimization topics are described in this chapter: S S S Drive testing the system. Diagnosing drive test results. Residual defect investigation.

31st Jul 01
68P02901W43-J
101
Network optimization overview
GSM-100-423

Optimization process overview
Optimization is the task of improving the call success rate for mobile subscribers. In a newly deployed network, problems will emerge. These will be due to any or all of the following: S S S The set-up of the database parameters. The installation of the equipment. The orientation of the antennas.
There will almost certainly be problems with congestion in busy parts of the network. As a network matures from an initial coverage priority to handling more subscribers, it will become clear that some of the original cells will have to be modified or removed from the network. The optimization of an entire network with hundreds or thousands of cells is a time-consuming and slow process, and can show little improvement in overall network quality in the short term. Drive testing and analysis of collected data are two stages of a practical method of optimizing a network by attacking the worst ten performing cells. Dealing with the worst ten cells in each optimization exercise, slowly resolves the problems and raises the overall quality of service available to subscribers. As the network expands each new cell integrated into the network is automatically assessed along with all the original cells. The overall performance of a network which has had little or no upgrading can also be improved by implementing newer features or operating practices.
102
31st Jul 01
GSM-100-423
Stages in an optimization exercise

The optimization process can be divided into the following stages: S Preparing for an optimization exercise from the OMC-R. This involves consultation with network operators to review their network administration procedures and feature implementation to determine where areas can be modified to increase efficiency and unnecessary diagnostic effort. See Preparing for optimization in Installation and Configuration: GSM System Configuration (GSM-100-403). S Checking, collecting and researching network information from the OMC-R. Details can be found in the manual Installation and Configuration: GSM System Configuration (GSM-100-403). Analysing, diagnosing and rectifying network problem areas from the OMC-R. Details can be found in the manual Installation and Configuration: GSM System Configuration (GSM-100-403). Drive testing, if required. Drive testing is a significant stage in optimizing a network. It is labour intensive, slow, and drive test teams cannot cover cells that are geographically widely separated. In these circumstances statistical analysis of the network from the OMC-R can be quicker, but in other circumstances drive testing may still be necessary. See sections in this chapter for further details. S Analysing and resolving any problem cells using data, logs and tick sheets collected during the drive tests. See sections in this chapter for further details.

31st Jul 01
68P02901W43-J
103
Drive testing the system
GSM-100-423

Introduction
Once the network optimization exercise has reached the stage of drive testing and network performance is still poor, then a drive test of the problem cells will be required. This involves: S S S S S S S S S Preparing for the drive test. Equipment lists. optimizing for worst case interference. Drive test process. Data collection overview. Personnel requirements. Data collection process. FICS. The classification of test calls.
Preparing for the drive test

Prior to the commencement of drive testing, certain system features must be set, and equipment for carrying out the drive test and collection of data must be organised.
System features
Prior to drive testing ensure: S S S S Base station power control feature is turned off. Directed retry feature is turned off. Congestion relief feature is turned off. All non-BCCH carriers are transmitting dummy bursts on all timeslots.
Equipment required for data collection/analysis

The following equipment is required for gathering and analyzing drive test data. S S S TEMS compatible mobile station (Ericsson models GH337, GH388 and GH688 with factory modified firmware). PC with TEMS mobile logging software and 2 serial ports. Colour printer.
104
31st Jul 01
GSM-100-423
Equipment/information required for Drive test

To carry out the drive test the following equipment and information is required. S A suitable number to ring is required to be available for the duration of the drive test. The number may be for a recorded announcement located at the MSC or PSTN, or to contact a third person at a land line phone. NOTE A recorded announcement such as weather or news can be used as long as it is 3 minutes or more in duration. Cordless or mobile phones should not be used for the landline contact. S Maps 1:10000 to 1:50000 in scale, of area to be tested, marked with longitude and latitude. BTS sites are to be identified on the maps, showing antenna direction. S A list of BCCH frequencies and BSICs for all BTS sites. The list must also contain BCCH frequencies and BSICs of BTSs from another equipment supplier, if this equipment borders the area under test. S S S A complete neighbour list for all BTSs in the area under test. Current database scripts for the sites that are to be optimized. Daily network performance statistics and information on outages that have affected the network over the past day must be collected from the OMC-R. Notice of planned outages should also be obtained to avoid time being wasted collecting data in areas with no service. S A second mobile for the drive test team. NOTE This phone should be from a rival network to maintain contact during outages, if the area under test is liable to no or poor service. S A suitable vehicle for the drive test team. The vehicle must be comfortable and capable of negotiating terrain within the test area. S S S GPS or other positioning system. Suitable power supplies/inverters to allow the use of data gathering equipment in the vehicle throughout the duration of the drive test. GSM recommendations 04.08, 05.08 and 08.08 are to be available. GSM recommendation 05.05 may be of use.

31st Jul 01
68P02901W43-J
105
GSM-100-423
Equipment lists
The following tables list the equipment required for drive testing, systems analysis and any necessary fault investigation. Table 10-1 lists the equipment required for drive testing. Table 10-1 Equipment required for drive testing
Equipment
Vehicle Laptop PC, Colour, 500Mb min HD Operating System 2nd Serial Port Vehicle Inverter 12Vdc to 240Vac 2nd Mobile Phone Ericsson Test Mobile (outdoor) Ericsson Test Mobile (outdoor) Mobile Logging Software Indoor Test Mobile 900Mhz Indoor Test Mobile 1800Mhz Global Positioning Hardware Global Positioning Software
Preferred
Minibus or MPV (ie Espace) Dell Latitude, any model MS Windows NT 4.0 Socket I/O PCMCIA Any Retail Alternative Network GH388 (900MHz) PH337 (1800MHz) Erisoft TEMS V96 Ericsson Pocket TEMS GH388 Ericsson Pocket TEMS PH337 Motorola PVT6 Oncore Rx Controller Any
Alternative
Toshiba 110CT upward MS Windows 3.11 or later None Known Any Retail Any Retail Orbitel Test Mobile Later Model Later Version Motorola 8900 in test mode Motorola 8900 in test mode Later Version Trimble 21426 + Card Trimble V4.24
Data Analysis Software Erisoft FICS Shell V96
106
31st Jul 01
GSM-100-423
Table 10-2 lists the equipment required for systems analysis.

Table 10-2 Equipment required for systems analysis
Equipment
Preferred
Alternative
HP Deskjet 1120 (A3 Paper) SUN Sparc 20 UNIX Netplan Later Version
Colour Plotter or Printer HP Designjet 650C upward Workstation Operating System SUN Ultra Sparc 1 UNIX
Data Analysis Software MSI PlaNet Data Analysis Software Erisoft FICS Shell V96
Table 10-3 lists the equipment required for problem investigation.

Table 10-3 Equipment required for problem investigation
Equipment
Network Protocol Analyser Spectrum Analyser Antenna System Laptop PC, Colour, 500Mb min HD Operating System 9/25 Way I/face cable (BSC/XCDR) Interface cable (BTS) Terminal Emulator Software
Preferred
Siemens K1103 Advantest U4342 Tracking Opt Bird T43 (VSWR only) Dell Latitude, any model MS Windows NT 4.0 Standard RS232 BTS H/W Model Specific Procomm +
Alternative
None Wavetek 4031 or 4032 Wiltron Sitemaster S331 Toshiba 110CT upward MS Windows 3.11 or later None None MS Hyperterminal

31st Jul 01
68P02901W43-J
107
GSM-100-423
Optimizing for worst case interference

During the drive testing phase of the optimization, downlink power control must be turned off. Once optimization is complete downlink power control can be reactivated. A feature at the OMC-R allows the operator to achieve this, configuring all non-BCCH carriers to transmit dummy bursts on all timeslots not carrying traffic. This will give a worst case interference environment in which optimization can be carried out. Information on how to enable this feature using the set_full_power command can be found in Technical Description: BSS Command Reference (GSM-100-321). This is useful if during optimization there is very little traffic currently on the network.
Drive test process

Drive testing provides the data necessary to optimize network performance. The 2 minute call method provides the means for investigating the performance of our systems, and optimizing networks. The 2 minute calls used as a standard, give a representation of traffic and can be used to measure performance of the network giving an indication of progress being made by optimization teams. With this method not only can interference and coverage issues be identified, but also signalling and other problems that are present can be discovered and their effects on system performance quantified. Data gathered can be used for the benchmarking of system performance. If this is the requirement, then in excess of 1000 calls will be required before data can be looked at with confidence. Consideration must be given to available time, goals and resources when looking at benchmarking. A significant picture can be built up with a much smaller sample, consisting of a minimum 200 calls. Drive test routes are best defined in consultation with the network operators, as they will have priority areas that require constant evaluation. Recommendations resulting from analysis of network optimization data must reflect the customers circumstances and goals, and wherever possible use existing hardware and features already in place. Drive tests are to be conducted by using mobiles in the same manner as they would be used by network subscribers. For instance, it is rare that a subscriber would have a car mounted mobile station, so this must not be used to carry out a drive test. If a roof mounted antenna is to be used then an attenuator should be used to simulate the in-car losses. Similarly if coverage of buildings is important within a city, then it will be necessary to do tests within a few key buildings.
Data collection overview

Data is collected by drive teams using TEMS mobiles. The TEMS mobile is a test mobile station combined with logging software that runs on a PC. The collecting of data will be carried out by a two man team, consisting of a driver and an operator. The drive testing task is very labour intensive and time consuming.
108
31st Jul 01
GSM-100-423
Personnel requirements
Optimizing a network in a large city environment will require a number of teams to speed up the process. Rural network optimization will again require multiple teams, however this time the need is to compensate for geographical dispersion. A number of personnel will also be required for data analysis. Data analysis consists of two stages: S S The generation of statistics to monitor network performance. The resolution of problems on the network once detected.
Problems resulting from localised interference will require system investigators to visit the problem area in person. Spectrum analysers will be used by the investigators to track extraneous interference.
Data collection process

A number of drive test teams will be collecting data, with each team required to make in excess of 175 calls per day. TEMS mobile stations equipped with the latest version of the software can make and terminate these calls automatically. This can lead to uncertainty as to whether a call was dropped or terminated normally. A call should: S S S Be 2 minutes (+/ 5 seconds) in duration. Have a minimum gap of 20 seconds in between it and the next call. Not be made for 20 seconds after a failed call has terminated
Drive test teams have the option of recording each call attempt made onto a tick sheet or processing the results wholly through FICS. An example tick sheet can be found in chapter 11 of this manual.
FICS explained
When using tick sheets to process call log data, errors are to be expected. File & Information Converting System (FICS) must be used to confirm the tick sheets, and identify calls that need further analysis. Calls are to be logged manually if the latest version of FICS is unavailable. An alternative to using tick sheets is to process the call log data direct through TEMS automatic logging and FICS. This eliminates tick sheet errors and makes the collection of data easier and more reliable. However, FICS is unable to differentiate noise during a call, so even with good signal strength if there is induced noise or no audio then it will go undetected. Taking this into account, the proportion of noisy calls and low audio calls is relatively low, and considering the volume of calls generated may have low impact on overall network quality. The ineffectiveness of FICS to identify no audio calls can be counteracted by running a message_send command for the transcoders. This will identify any faulty DSPs on transcoder boards at the site. Information on using the message_send command can be found in Technical Description: BSS Command Reference (GSM-100-321). NOTE This command will not help in identifying noisy calls, which will still go completely undetected.

31st Jul 01
68P02901W43-J
109
GSM-100-423
Report generation
A report can be generated showing call failure analysis when using FICS as opposed to tick sheets. This is done using the FICS .sta files, by summing all quality entries in the RxQual 0 to 4 bands inclusive, and using the resultant as a Q measure. An added benefit of this is that it will also give you any MSC related issues that would not normally be highlighted.
Classification of test calls

A call will fall into one of the categories defined below: S No service. A call will fall into this category if the mobile is saying No service or Select service before the send button is pressed. NOTE The RXLEV must be less than the criteria defined for C1 in GSM recommendation 05.08. S No set-up. If, after pushing send, the call does not proceed to audio it is categorised as no set-up. S No audio. This category applies when after a traffic channel has been assigned the audio connection is never made, or only appears after a handover. S Noisy call. A call is defined as noisy if there are more than 5 seconds of noise or breaks in the audio during the call. S S Dropped call. If a call terminates during a 2 minute test call it will be classed as a dropped call. Good call. A call that does not fit into any of the above criteria will be deemed to have been successful and classed a good call.
Tick sheets
When entering test call results onto a tick sheet, only one tick per call should be entered.
Log files
When using log files to record call information the log file names should be changed after every 10 calls. A suitable naming convention scheme, to ensure unique files, is to use the form xydmz.log. Here xy are the initials of the operator, dm are the day and month and z is a sequencing indicator, starting with a and progressing through the alphabet.
Archiving
All data should be archived at the end of the day. Archiving may be to Floppy disk, CD-ROM or any other suitable means which is convenient to the drive test team carrying out the work. Installation & Configuration: BSS Optimization 68P02901W43-J
1010
31st Jul 01
GSM-100-423
Diagnosing drive test results

Introduction
Once a drive test of the system is completed, the resultant data of test calls made must be analysed. This involves looking at: S S S S S S S S S S S S Analysis of data. High handover failure rates. High set-up failure rates. High dropped call rates. No audio calls. Noisy calls. Poor quality of service calls. High blocking cells. Audio call faults. Mean time between drops. Antenna system test procedure. Drive test recommendations.
Analysis of data
Call failures will be due to a number of different factors, so each failure must therefore be analysed. If a failure cannot be explained further assistance should be sought. Graphs are a useful way of showing the contribution each type of failure is making to the call success rate. Graphs can be used to show: S The percentage of failed calls. These calls will consist of dropped calls, no set-up calls, no service calls and no audio calls. S The contribution of different causes of failure to each failure category.
The graphs provide a useful means of analysis and give problem solving teams an idea of causes of the greatest number of failures. The failures can then be addressed on a priority basis, with the largest percentage of failures being rectified first. The results collected can be used for benchmarking the systems performance, as discussed in Drive test process. Doing this allows the progress of the system performance to be monitored. However, for the results to have any statistical significance a large number of calls will need to be made. Quoting the margin of error when presenting the results is necessary to explain the variance that will been seen in results from week to week.

31st Jul 01
68P02901W43-J
1011
GSM-100-423
High handover failure rates

High handover failure rates will probably be due to one or more of: S S S S S High neighbour interference. High source cell interference. Mobile on incorrect source cell. Mobile allocated incorrect or unexpected neighbour. Location area borders planned poorly. S Borders on road junctions or ridges. Borders on large water expanses.
Cell borders planned poorly. Borders on road junctions or ridges. Borders on large water expanses.
Database parameters. Power budget algorithms incorrectly specified. RxQual algorithms incorrectly specified. RxLev algorithms incorrectly specified. Timing advance algorithms incorrectly specified.
No dominant server. Neighbours being received at similar levels. Missing cell site.
1012
31st Jul 01
GSM-100-423
High set-up failure rates

High set-up failure rates will probably be due to one or more of: S No access to SDCCH. Mobile failed to send RACH. No UA received from BTS due to interference. Mobile access class barred. Mobile failed to carry out location update. Check HLR, VLR or links to them. SDCCH congestion. Result of location area boundaries being undesirable or insufficient SDCCHs available. S Failure before assignment of TCH. S Downlink disconnect message from MSC. Congestion on the A interface. No free TCHs available.
Failure after assignment of TCH. High interference on allocated TCH or timeslot. On site cabling faulty. Disconnect due to called party busy. PSTN congestion. No answer. Incorrectly dialled digits. Mobile on wrong cell. Rx path failure on non-BCCH carrier.

31st Jul 01
68P02901W43-J
1013
GSM-100-423
High dropped call rate

High dropped call rates will probably be due to one or more of the following.
Interference problems
Interference problems can be attributed to: S S Adjacent channel interference. Neighbouring cells causing interference.
Co-channel interference. Neighbouring cells on same frequency as source. Non neighbouring cells penetrating due to topology. Mobile elevated and receiving out of area signals. Antennas to high, causing interference and out of area originations.
S S
Uplink interference. Background interference.
Extraneous interference. Other mobile networks. Military communications. High power radio transmission stations. Proximity of ground based radar systems. Cordless telephones. Industrial electrical emissions. Illegal radio communication equipment.
Mobile to cell link problems

Link problems can be attributed to: S Link imbalance. Mobile transmitting to high. Mobile transmitting to low. BTS transmitting to high. BTS transmitting to low. Physical obstructions. Nearby microwave or high power radiating devices. Antennas positioned to close together. Transmit and receive antennas facing different directions. Transmit and receive antennas having different tilts. Transmit and receive antennas having different beam widths. Antenna feeder damage, corrosion or water ingress, or antenna radiating surfaces being contaminated. Installation & Configuration: BSS Optimization 68P02901W43-J
1014
31st Jul 01
GSM-100-423
Cell allocation problems

Cell allocation problems can be attributed to: S Drop on handover. S Mobile on incorrect source cell. Mobile allocated incorrect or unexpected neighbour.
Missing neighbour cell. Mobile on wrong source cell for location. Missing handover definition. Neighbour weaker than serving cell. Incorrect BSIC or frequency with respect to the neighbour list. Target cell congested. Frequency not sent in system information message.
Mobile on wrong cell. Missing neighbour. Incorrect antenna orientation. Antennas cross connected. Mobile handed-in to wrong cell from previous server. Optimum server out of service.
Wrong frequency. Cell is not on the correct frequency as detailed in the network plan. Cell is not on the correct frequency as detailed in the neighbour lists.
Cell out of service. Cell out of service, causing a coverage hole. Sleeping cell.
Signal and propagation problems.

Signal and propagation problems can be attributed to: S Low signal level. S S BTS transmission power too low. Radio signal propagation problems. Local cell out of service.
Ridges causing immediate signal loss before handover can be initiated. Narrow cell boundaries, mobile cannot handover in time.

31st Jul 01
68P02901W43-J
1015
GSM-100-423
No audio calls
No audio calls will probably be due to one or more of: S S Hardware problems in the transcoder circuitry. Software problems in the transcoder database.
Noisy calls
Noisy calls will probably be due to one or more of: S S Interference. Low signal level.
Poor quality of service calls

Poor quality calls will probably be due to one or more of: S S S Interference. Low signal level. No serving cell.
High blocking cells

Blocking cells can be attributed to:
SDCCH blocking
S No access to SDCCH. Mobile failed to send RACH. No UA received by MS due to interference. Mobile access class barred. Mobile failed to carry out location update. Check HLR, VLR or their respective links. Location update timer is too long for immobile MS. SDCCH congestion. Location area boundaries undesirable. Insufficient SDCCHs available. S Failure before assignment of TCH. S S Downlink disconnect message from MSC. Congestion on the A interface. No free TCHs available. Each location area should have similar paging loads. A location area with a high paging load needs to be reduced in size to relieve SDCCH blocking. A location area with a low paging load needs to be enlarged in size to reduce the overall number of location areas. Timer rr_t3111 should be set to 1200ms. Timer rr_t3212 needs to be the same as the MSC database implicit detach timer and should be similar across all cells. Installation & Configuration: BSS Optimization 68P02901W43-J
High paging loads.
Incorrect or inappropriate timer values.
1016
31st Jul 01
GSM-100-423
TCH blocking
S S S Handover margins not optimized. Power budget margins too high to move traffic to neighbouring cells. Cell too large. S S Antennas too high, pulling in out of area traffic. Antenna tilts to shallow, pulling in out of area traffic, maximum tilt is 12_.
Capacity limitation for sites suffering SDCCH and TCH blocking. Incorrect or inappropriate timer and parameter values. Timer rr_t3111 should be set to 1200ms. Parameter link_fail should be set to 3. Parameter radio_link_timeout should be set to 3 and timer rr_t3109 to 8000.
MTL blocking
S S S S S On site cabling faulty. Disconnect due to the called party being busy. PSTN congestion. No answer. Incorrectly dialled digits.

31st Jul 01
68P02901W43-J
1017
GSM-100-423
Audio call faults

The process of tracing faults associated with no audio or one way audio calls is exasperated by the way the circuits are allocated dynamically. With circuits being allocated dynamically it may take several attempts, by the person trying to trace the fault, before the faulty circuit is allocated again. This could result in other users on the system being allocated the faulty circuit when trying to make a call, whilst the faulty circuit is being traced. The most likely cause of audio fault on a circuit has been shown to be a faulty DSP on a transcoder board. The following procedure details how to check the DSPs, on a transcoder board, using the msg_send command.
Procedure preparation
Carry out the following procedure from a Local Maintenance Terminal (LMT) connected to the XCDR containing the suspect XCDR board. WARNING Calls being processed by the suspect transcoder board that are unaffected by the faulty DSP will be affected by this test procedure. The OMC-R must take the appropriate steps to route all calls away from the suspect board prior to commencement of the test. 1. Disable the suspect transcoder board using the front panel tri-state switch. This will bring up an alarm in the event window at the OMC-R. 2. 3. Connect the serial A port on the PC to a GPROC/GPROC2 TTY port using the 9-way to 25-way cable. Start the terminal emulator software on the PC
DSP check procedure

1. Type CTRL-n to enter the Executive Monitor (EMON), and at the prompt type: msg_send 75 4 74 7791h 2622h 9 x x x 4 3 1 2 3 4 Where: xxx is: XCDRs MSI number
Sending this message makes the Fault Translation Process (FTP) think the device is in-service, when it is actually disabled. 2. At the EMON prompt type: msg_send 4ah 50h 0 0 2371h 9 x x x 10 2 Where: xxx is: XCDRs MSI number
This message will generate a DSP check failure alarm. 3. Exit the Executive Monitor and at the MMI-RAM prompt type: disp_act_alarm # Where: # is: location id
A DSP check failed alarm should appear, upon receipt of the command in step 2. Installation & Configuration: BSS Optimization 68P02901W43-J
1018
31st Jul 01
GSM-100-423
4.
Type CTRL-n to enter the EMON, and at the prompt type: msg_send 4ah 50h 0 0 2371h 9 x x x 10 1 Where: xxx is: XCDRs MSI number
This message will clear the alarm. 5. Exit the EMON and at the MMI-RAM prompt type: disp_act_alarm # Where: # is: location id
The alarm generated in step 2 should now be cleared. To re-generate and clear the alarm repeat steps 2 to 5.
Restoration
1. Reset or replace the transcoder board as necessary. To replace the transcoder board follow the procedure detailed in Maintenance Information: BSC/RXCDR (GSM-100-533). 2. 3. Remove the 9-way to 25-way cable. Inform the OMC-R that the test is complete.
Mean time between drops

When making test calls the length of the call may need to be varied, depending on differing conditions. This is creates a problem when using test calls to benchmark a network, as the baseline criteria is variable. A metric has been devised to overcome this that does not require the rigid adherence of test call length to be 2 minutes. This method uses the probability of a drop, as a consequence of call length, for the baseline measurement. The mean time between drops is defined as: For call drive test metrics: Mean Time Between Drop = Length of Test Call Drop Call Percentage
For system statistics: Mean Time Between Drop = For example: S S S S S 2 minute calls, 1% drop = 200 minutes (MTBD) 2 minute calls, 2% drop = 100 minutes (MTBD) 2 minute calls, 10% drop = 20 minutes (MTBD) 30 second calls, 1% drop = 50 minutes (MTBD) 10 minute calls, 1% drop = 1000 minutes (MTBD) Length of Average Hold Time Drop Call Percentage

31st Jul 01
68P02901W43-J
1019
GSM-100-423
Drive test report

The result of a drive test is a report, which is generated by compiling all the relevant data gathered, in support of conclusions and recommendations which are to be made to the customer. The report must be delivered as part of a formal presentation, and as such must incorporate the official Motorola look and feel in accordance with Motorola policy. Each conclusion in the report is to have a supporting numbered recommendation related to it. A recommendation must describe the issue, recommended solution and the impact that carrying out the recommendation will have on the rest of the network. As much detail as possible is to be included to aid in the recommendations implementation. The report must also include legal content reflecting that it is a detailed report based on a survey and implies no warranty or commitment on the part of Motorola to carry out any of the recommendations within it. An example of the recommendation field report can be found in chapter 11.
Implementation of a drive test recommendation

It is recommended that the customer implements drive test recommendations. If the customer has a service agreement or has purchased the option of Motorola following through the action points, then the recommendations should be implemented in line with local agreements. It is beyond the scope of this document to explain the implementation of each recommendation.
Effects of a recommendation implemented

Any recommendation effected by Motorola is to be monitored and confirmation sought that its implementation cured the issue.
1020
31st Jul 01
GSM-100-423
Residual defect investigation

Any defects discovered during the optimization process that cannot be resolved are to be reported through the normal process for raising problem reports. It is recommended that defects discovered are fixed, however it is not within the scope of this document to identify procedures for the repair/replacement of faulty hardware.

31st Jul 01
68P02901W43-J
1021
GSM-100-423
1022
31st Jul 01
Chapter 11
Optimization results forms

31st Jul 01
68P02901W43-J
GSM-100-423
ii
31st Jul 01
GSM-100-423
Chapter 11 Optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS/BSC optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna reflected power tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRCU tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCU/TCU900/ TCU-B/CTU900 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCU/TCU1800/ CTU1800 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCU1900 tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loopback and RTC checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC/RXCDR optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1/T1 loopback (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1/T1 loopback (RXCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellaccess PCC optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loopback checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellaccess BSC/XCDR results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personnel details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC power supply tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 loopback (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 loopback (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site documentation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing optimization forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms in this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tick Sheet Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommendation Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feeder Information Proforma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive testing optimization tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tables in this section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
111 111 111 112 112 113 113 114 1110 1116 1128 1140 1141 1141 1141 1142 1142 1142 1143 1144 1145 1146 1146 1146 1147 1148 1148 1149 1150 1150 1150 1151 1152 1152 1153 1154 1155 1155 1155 1156 1157 1158 1160 1160 1160

31st Jul 01
68P02901W43-J
iii
GSM-100-423
iv
31st Jul 01
GSM-100-423
BTS/BSC optimization results forms

Introduction
Complete the forms in this section while optimizing the equipment. Photocopy them as necessary, but do not write on the originals. CAUTION EPSMs are for negative earth cabinets (+27 V). IPSMs are for positive earth cabinets (48 V).
The forms
The following forms are included: S S S S S S S S S S S S S Personnel details. DC power supply tests. Antenna reflected power tests. PIX tests. DRCU0 to DRCU5 tests. SCU900 0 to SCU900 5 tests. SCU1800 0 to SCU1800 5 tests. TCU1900 0 to TCU1900 5 tests. TCU-B 0 to TCU-B 5 tests. CTU900 0 to CTU900 5 tests. CTU1800 0 to CTU1800 5 tests. Loopback and RTC checks. Site documentation check.

31st Jul 01
68P02901W43-J
111
GSM-100-423
Personnel details
Cell Site Name Cell Site Number Date
............. ................................... ...................................
Engineers Name
...................................
Signature
...................................
Customer Representative
.............
Signature
...................................
DC power supply tests

Battery supply V PSU output V DC input to cabinet V
112
31st Jul 01
GSM-100-423
Antenna reflected power tests

Antenna Sector 1 Tx Rx 1 Rx 2 Sector 2 Tx Rx 1 Rx 2 Sector 3 Tx Rx 1 Rx 2 Omni Tx Rx 1 Rx 2 Channel Forward power Reverse power
PIX tests
Tick the boxes if all alarms show then clear.
PIX0/slot 15
PIX0/slot 16
PIX1/slot 17
PIX1/slot 18
NOTE BTS4 and BTS5 systems use slots 15 and 16 only. BTS6 systems use slots 16, 17, and 18 only.

31st Jul 01
68P02901W43-J
113
GSM-100-423
DRCU tests
DRCU 0 tests
Serial Number Slot Number 0
CSPWR Settings CSPWR P: dBm Cell Site Offset Hex O/P at DRCU PA Watts (on meter) Receive Bay Level Calibration Rx 1 Chan 4 12 20 28 36 44 52 60 68 76 84 92 100 108 116 122 Ant 1 Ant 2 Ant 3 Chan 4 12 20 28 36 44 52 60 68 76 84 92 100 108 116 122 Ant 1 Rx 2 Ant 2 Ant 3 (on meter) O/P at top of cabinet Watts O/P at top of cabinet Watts
Loss in test cable dB
114
31st Jul 01
GSM-100-423
DRCU 1 tests

31st Jul 01
68P02901W43-J
115
GSM-100-423
DRCU 2 tests
116
31st Jul 01
GSM-100-423
DRCU 3 tests

31st Jul 01
68P02901W43-J
117
GSM-100-423
DRCU 4 tests
118
31st Jul 01
GSM-100-423
DRCU 5 tests

31st Jul 01
68P02901W43-J
119
GSM-100-423
SCU/TCU900/ TCU-B/CTU900 tests

SCU/TCU900/TCU-B/CTU900 0 tests
CSPWR P: dBm
Cell Site Offset Hex O/P at SCU/TCU PA Watts (on meter) Rx 2
O/P at top of cabinet Watts O/P at top of cabinet Watts (on meter)
Loss in test cable dB Receive Bay Level Calibration Rx 1 Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019 Ant 1 Ant 2
Ant 3
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979
Ant 1
Ant 2
Ant 3
EGSM ONLY
987 995 1003 1011 1019
1110
31st Jul 01
GSM-100-423
CSPWR P: dBm
Cell Site Offset Hex O/P at SCU/TCU PA Watts (on meter)
Loss in test cable dB Receive Bay Level Calibration
Rx 1
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019
Ant 1
Ant 2
Ant 3
Rx 2
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979
Ant 1
Ant 2
Ant 3
EGSM ONLY
987 995 1003 1011 1019

31st Jul 01
68P02901W43-J
1111
GSM-100-423
CSPWR P: dBm
Rx 1
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019
Ant 1
Ant 2
Ant 3
Rx 2
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979
Ant 1
Ant 2
Ant 3
EGSM ONLY
987 995 1003 1011 1019
1112
31st Jul 01
GSM-100-423
CSPWR P: dBm
Rx 1
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019
Ant 1
Ant 2
Ant 3
Rx 2
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979
Ant 1
Ant 2
Ant 3
EGSM ONLY
987 995 1003 1011 1019

31st Jul 01
68P02901W43-J
1113
GSM-100-423
CSPWR P: dBm
Rx 1
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019
Ant 1
Ant 2
Ant 3
Rx 2
Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979
Ant 1
Ant 2
Ant 3
EGSM ONLY
987 995 1003 1011 1019
1114
31st Jul 01
GSM-100-423
CSPWR P: dBm
Cell Site Offset Hex O/P at SCU/TCU PA Watts (on meter) Ant 3 Rx 2 Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 EGSM ONLY 987 995 1003 1011 1019
O/P at top of cabinet Watts O/P at top of cabinet Watts (on meter) Ant 1 Ant 2 Ant 3
Loss in test cable dB Receive Bay Level Calibration Rx 1 Chan 3 11 19 27 35 43 51 59 67 75 83 91 99 107 115 123 979 987 995 1003 1011 1019 Ant 1 Ant 2

31st Jul 01
68P02901W43-J
1115
GSM-100-423
SCU/TCU1800/ CTU1800 tests

SCU/TCU1800/CTU1800 0 tests
CSPWR P: dBm
Receive Bay Level Calibration Rx 1 Chan 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700 Ant 1 Ant 2 Ant 3 Rx 2 Chan 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700
Ant 1
Ant 2
Ant 3
1116
31st Jul 01
GSM-100-423
Receive Bay Level Calibration (continued) Slot Number 0 Rx 1 Chan 708 716 724 732 740 748 756 764 772 780 788 796 804 812 820 828 836 844 852 860 868 876 883 Ant 1 Ant 2 Ant 3 Rx 2 Chan 708 716 724 732 740 748 756 764 772 780 788 796 804 812 820 828 836 844 852 860 868 876 883 Ant 1 Ant 2 Ant 3

31st Jul 01
68P02901W43-J
1117
GSM-100-423
CSPWR P: dBm
Receive Bay Level Calibration Rx 1 Chan 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700 Ant 1 Ant 2 Ant 3 Rx 2 Chan 516 524 532 540 548 556 564 572 580 588 596 604 612 620 628 636 644 652 660 668 676 684 692 700 Ant 1 Ant 2 Ant 3
1118
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1119
GSM-100-423
CSPWR P: dBm
1120
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1121
GSM-100-423
CSPWR P: dBm
1122
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1123
GSM-100-423
CSPWR P: dBm
1124
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1125
GSM-100-423
CSPWR P: dBm
1126
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1127
GSM-100-423
TCU1900 tests
TCU1900 0 tests
CSPWR P: dBm
Cell Site Offset Hex O/P at TCU1800 PA Watts (on meter)
1128
31st Jul 01
GSM-100-423
Receive Bay Level Calibration (continued) Slot Number 0 Rx 1 Chan 708 716 724 732 740 748 756 764 772 780 788 796 804 809 Ant 1 Ant 2 Ant 3 Rx 2 Chan 708 716 724 732 740 748 756 764 772 780 788 796 804 809 Ant 1 Ant 2 Ant 3

31st Jul 01
68P02901W43-J
1129
GSM-100-423
TCU1900 1 tests
CSPWR P: dBm
1130
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1131
GSM-100-423
TCU1900 2 tests
CSPWR P: dBm
1132
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1133
GSM-100-423
TCU1900 3 tests
CSPWR P: dBm
1134
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1135
GSM-100-423
TCU1900 4 tests
CSPWR P: dBm
1136
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1137
GSM-100-423
TCU1900 5 tests
CSPWR P: dBm
1138
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1139
GSM-100-423
Loopback and RTC checks

E1/T1 loopback BTS MS1 SLOT PORT 12/A 12/B 14/A 14/B 16/A 16/B Site documentation check
Tick box if the distribution frame (DDF) is wired as in the site documentation.
MS3 T43 BIB DDF SLOT PORT 13/A 13/B 15/A 15/B 17/A 17/B T43 BIB DDF
If not, list the changes below or on a separate sheet of paper.
1140
31st Jul 01
GSM-100-423
BSC/RXCDR optimization results forms

Introduction
Complete the forms in this section while optimizing the equipment. Photocopy them as necessary, but do not write on the originals. CAUTION EPSMs are for negative earth cabinets (+27 V). IPSMs are for positive earth cabinets (48 V).
The forms
The following forms are included: S S S S S S Personnel details. DC power supply tests. PIX tests. E1/T1 loopback BSC. E1/T1 Mbit/s loopback RXCDR. Site documentation check.

31st Jul 01
68P02901W43-J
1141
GSM-100-423
Personnel details
Cell Site Name Cell Site Number Date ............. ................................... ...................................
Engineers Name
...................................
Signature
...................................
.............
Signature
...................................

PIX tests
Tick the boxes if all alarms show then clear.
PIX0/slot 15
PIX0/slot 16
PIX1/slot 17
PIX1/slot 18
NOTE BTS4 and BTS5 systems use slots 15 and 16 only. BTS6 systems use slots 16, 17, and 18 only.
1142
31st Jul 01
GSM-100-423
E1/T1 loopback (BSC)

This is for maximum utilization. Checks can only be carried out if MSIs are equipped in the database. If the cables have not been installed to the distribution frame but the boards are equipped, then test loop to the T43 or BIB.
Upper shelf MS 4 SLOT PORT 13/A 13/B 15/A 15/B 17/A 17/B T43 BIB DDF MS 5 SLOT PORT 12/A 12/B 14/A 14/B 16/A 16/B T43 BIB DDF
MS 6 SLOT PORT 7/A 7/B 9/A 9/B 11/A 11/B Lower shelf MS 0 SLOT PORT 13/A 13/B 15/A 15/B 17/A 17/B T43 BIB DDF T43 BIB DDF
MS 7 SLOT PORT 6/A 6/B 8/A 8/B 10/A 10/B T43 BIB DDF

31st Jul 01
68P02901W43-J
1143
GSM-100-423
E1/T1 loopback (RXCDR)

This is for maximum utilization. Checks can only be carried out where MSIs or XCDRs are equipped in the database. If the cables have not been installed to the distribution frame but the boards are equipped, then test loop to the T43 or BIB.
Upper shelf MS 4 SLOT PORT 19/A 20/B 21/A 22/B 23/A 24/B MS 6 SLOT PORT 9/A 9/B 10/A 10/B 11/A 12/A T43 BIB DDF T43 BIB DDF MS 5 SLOT PORT 13/A 14/B 15/A 16/B 17/A 18/B MS 7 SLOT PORT 6/A 6/B 7/A 7/B 8/A 8/B T43 BIB DDF T43 BIB DDF
1144
31st Jul 01
GSM-100-423
Lower shelf MS 0 SLOT PORT 19/A 20/B 21/A 22/B 23/A 24/B MS 2 SLOT PORT 9/A 9/B 10/A 10/B 11/A 12/A T43 BIB DDF T43 BIB DDF MS 1 SLOT PORT 13/A 14/A 15/A 16/A 17/A 18/B MS 3 SLOT PORT 6/A 6/B 7/A 7/B 8/A 8/B T43 BIB DDF T43 BIB DDF
Site documentation check


31st Jul 01
68P02901W43-J
1145
M-Cellaccess PCC optimization results forms
GSM-100-423

Introduction
Complete the forms in this section while optimizing the equipment for M-Celltaccess. Photocopy them as necessary, but do not write on the originals.
The forms
The following forms are included: S S S S Personnel details. DC power supply tests. Loopback checks. Site documentation check.
1146
31st Jul 01
GSM-100-423
Personnel details
Cell Site Name Cell Site Number Date
............. ................................... ...................................
Engineers Name
...................................
Signature
...................................
.............
Signature
...................................

31st Jul 01
68P02901W43-J
1147
GSM-100-423

Loopback checks
E1/T1 loopback BSS MS1 SLOT PORT 14/A 14/B 16/A 16/B T43 DDF MS3 SLOT PORT 8/A 8/B 10/A 10/B T43 DDF
1148
31st Jul 01
GSM-100-423


31st Jul 01
68P02901W43-J
1149
M-Cellaccess BSC/XCDR results forms
GSM-100-423

Introduction
Complete the forms in this section while optimizing the M-Cellaccess equipment. Photocopy them as necessary, but do not write on the originals.
The forms
The following forms are included: S S S S S Personnel details. DC power supply tests. E1 loopback BSC. E1 loopback XCDR. Site documentation check.
1150
31st Jul 01
GSM-100-423
Personnel details
Cell Site Name Cell Site Number Date ............. ................................... ...................................
Engineers Name
...................................
Signature
...................................
.............
Signature
...................................

31st Jul 01
68P02901W43-J
1151
GSM-100-423

E1 loopback (BSC)
This is for maximum utilization. Checks can only be carried out if MSIs are equipped in the database. If the cables have not been installed to the distribution frame but the boards are equipped, then test loop to the T43.
Upper shelf MS 5 SLOT PORT 14/A 14/B 16/A 16/B Lower shelf MS 1 SLOT PORT 14/A 14/B 16/A 16/B T43 DDF MS 3 SLOT PORT 8/A 8/B 10/A 10/B T43 DDF T43 DDF MS 7 SLOT PORT 8/A 8/B 10/A 10/B T43 DDF
1152
31st Jul 01
GSM-100-423
E1 loopback (XCDR)
This is for maximum utilization. Checks can only be carried out where MSIs or XCDRs are equipped in the database. If the cables have not been installed to the distribution frame but the boards are equipped, then test loop to the T43.
Upper shelf MS 5 SLOT PORT 14/A 14/B T43 DDF MS 7 SLOT PORT 8/A 8/B 10/A 10/B Lower shelf MS 1 SLOT PORT 14/A 14/B T43 DDF MS 3 SLOT PORT 8/A 8/B 10/A 10/B T43 DDF T43 DDF

31st Jul 01
68P02901W43-J
1153
GSM-100-423

1154
31st Jul 01
GSM-100-423
Drive testing optimization forms

Introduction
Use the following forms as required when carrying out drive testing optimization. Photocopy the forms as necessary, but do not write on the originals.
Forms in this section

The forms included in this section are: S S S Tick sheet performa. Recommendation performa. Feeder information performa.

31st Jul 01
68P02901W43-J
1155
GSM-100-423
Tick Sheet Proforma

Time Location No service No set up No audio Noisy Drop Good Comments
File Name: 1 2 3 4 5 6 7 8 9 10
File Name: 1 2 3 4 5 6 7 8 9 10
1156
31st Jul 01
GSM-100-423
Recommendation Proforma
Equipment Type: BSS Database Title: RR_T3111=>1200 Description of issue: T3111 is currently set too long and will therefore hold SDCCH/TCH resource for longer than the minimum necessary to complete the channel release. Solution: Reduce the timer value Impact: Reduce congestion on TCH and SDCCH Recommendation Number: 24

31st Jul 01
68P02901W43-J
1157
GSM-100-423
Feeder Information Proforma

Item Aerial/Feeder System Information and Performance Data Record Date Signature Motorola Feeder Lable Customer
Antenna Type
Orientation
Mechanical Tilt
Resultant Tilt
Feeder LDF5:5 Cable Type 0
LDF5:5 0
LDF5:5 0
LDF5:5 0
LDF5:5 0
LDF5:5 0
Feeder VSWR R100
System VSWR R100
Measured Attenuation (mid band average dB) Feeder Length
Jumper Tail Type
1158
31st Jul 01
GSM-100-423
Item Feeder VSWR R100
Aerial/Feeder System Information and Performance Data Record
Date
Signature
Measured Attenuation (mid band average dB) Eq Jumper Length (m)
Ant Jumper Length (m)
Total Syst Attenuation (mid band average dB)

31st Jul 01
68P02901W43-J
1159
Drive testing optimization tables
GSM-100-423

Introduction
Use the following tables as required when carrying out drive testing optimization.
Tables in this section

The tables included in this section are: S S S S Feeder loss calculations table for LDF5-50 @ 960MHz. Return loss table for VSWR of 1.3 @ 960MHz. Return loss table for VSWR of 1.4 @ 960MHz. Return loss table for VSWR of 1.5 @ 960MHz.
Table 11-1 gives the loss calculation in dBs for lengths of LDF5-50A at the frequency of 960MHz. Table 11-1 Feeder loss calculations for LDF5-50 @ 960MHz
LDF5-50A Length (M) 1 2 3 4 5 10 15 20 25 30 35 40
dB atten.@ 960 MHz

0.042 0.084 0.126 0.168 0.21 0.42 0.63 0.84 1.05 1.26 1.47 1.68
LDF5-50A Length (M) 45 50 55 60 65 70 75 80 85 90 95 100
dB atten.@ 960 MHz

1.89 2.1 2.31 2.52 2.73 2.94 3.15 3.36 3.57 3.78 3.99 4.2
LDF5-50A Length (M) 105 110 115 120 125 130 135 140 145 150
dB atten.@ 960 MHz

4.41 4.62 4,83 5.04 5.25 5.46 5.67 5.88 6.09 6.3
1160
31st Jul 01
GSM-100-423
Table 11-2 gives the return loss in dBs for lengths of LDF5-50A with a VSWR of 1.3 at a frequency of 960MHz. Table 11-2 Return loss for VSWR of 1.3 @ 960MHz
LDF5-50A Length (M) 1 2 3 4 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130 135 140 145 150 dB P1 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 0.13 dB P2 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 17.6 dB P3 0.08 0.17 0.25 0.34 0.42 0.84 1.26 1.68 2.10 2.52 2.94 3.36 3.78 4.20 4.62 5.04 5.46 5.88 6.30 6.72 7.14 7.56 7.98 8.40 8.82 9.24 9.66 10.08 10.50 10.92 11.34 11.76 12.18 12.60 dB P4 17.52 17.43 17.35 17.26 17.18 16.76 16.34 15.92 15.50 15.08 14.66 14.24 13.82 13.40 12.98 12.56 12.14 11.72 11.30 10.88 10.46 10.04 9.62 9.20 8.78 8.36 7.94 7.52 7.10 6.68 6.26 5.84 5.42 5.00 coeff P5 0.13 0.13 0.14 0.14 0.14 0.15 0.15 0.16 0.17 0.18 0.18 0.19 0.20 0.21 0.22 0.24 0.25 0.26 0.27 0.29 0.30 0.31 0.33 0.35 0.36 0.38 0.40 0.42 0.44 0.46 0.49 0.51 0.54 0.56 coeff P6 0.23 0.23 0.24 0.24 0.24 0.25 0.25 0.26 0.27 0.28 0.28 0.29 0.30 0.31 0.32 0.34 0.35 0.36 0.37 0.39 0.40 0.41 0.43 0.45 0.46 0.48 0.50 0.52 0.54 0.56 0.59 0.61 0.64 0.66 coeff P7 0.16 0.16 0.16 0.17 0.17 0.17 0.18 0.18 0.19 0.19 0.20 0.21 0.21 0.22 0.23 0.23 0.24 0.25 0.26 0.27 0.28 0.29 0.30 0.31 0.32 0.34 0.35 0.36 0.38 0.39 0.41 0.43 0.45 0.46 dB Return loss 15.75 15.70 15.65 15.60 15.55 15.31 15.06 14.80 14.54 14.27 14.00 13.73 13.45 13.17 12.88 12.58 12.29 11.99 11.68 11.37 11.06 10.74 10.42 10.10 9.77 9.44 9.10 8.77 8.42 8.08 7.73 7.38 7.03 6.68 dB 5% of RL 14.96 14.91 14.87 14.82 14.78 14.54 14.30 14.06 13.81 13.56 13.30 13.04 12.78 12.51 12.23 11.95 11.67 11.39 11.10 10.80 10.51 10.20 9.90 9.59 9.28 8.97 8.65 8.33 8.00 7.68 7.35 7.02 6.68 6.34

31st Jul 01
68P02901W43-J
1161
GSM-100-423
1162
31st Jul 01
GSM-100-423

31st Jul 01
68P02901W43-J
1163
GSM-100-423
1164
31st Jul 01
Index

31st Jul 01
68P02901W43-J
I1
GSM-100-423
I2
31st Jul 01
GSM-100-423
Symbols
(D)RCU term, definition, 21
B
base site, integrating with logging software, 82 with no connection to the MSC, 88 without logging software, 85 bay level offset calibration CTU, 425 DRCU, 217 DRCU3, 217 DRCUII, 217 SCU900/1800, 231 TCUB, 356 TCU900/1800/1900, 337 bay level offset tables, results forms BSC/RXCDR, 1141 BTS/BSS/MCell, 111 BSC, optimization results forms, 1141 BSC/XCDR, results forms, MCellaccess, 1150 BTS, optimization results forms, 111
calibration, checking VSWR CTU, 46 DRCU, 211 DRCU3, 212 DRCUII, 212 SCU900/1800, 225 TCUB, 319 TCU900/1800/1900, 36 CCB cavity tuning, 315 channels DCS1800 frequencies, 911 EGSM frequencies, 98 GSM frequencies, 92 PCS1900 frequencies, 930 checking checking serial connections, MCell2/6, 377, 444 database devices and functions, 240, 372, 79 E1 link, 712 E1/T1 link, 242 MCell2/6, 375, 442 circuit breakers CU, 78 negative earth BSSC/RXCDR, 28 negative earth BTS, 27 PCC, 77 positive earth BSSC/RXCDR, 28 positive earth BTS, 27 code, downloading, 21, 71 CTU calibration bay level offset tables, 425 checking VSWR, 46 transmitter power output, 46
C
calibrating, GCLK, 251 MCell2/6, 379 MSCm, 629 record form, 254, 722 calibrating bay level offsets CTU, 425 DRCU, 217 DRCU3, 217 DRCUII, 217 SCU900/1800, 231 TCUB, 356 TCU900/1800/1900, 337 calibrating transmitter output power CTU, 46 DRCU, 211 DRCU3, 212 DRCUII, 212 SCU900/1800, 225 TCUB, 319 TCU900/1800/1900, 36
D
database, checking devices and functions, 240, 372, 79 DCS1800, channel frequencies, 911 downloading code, 21, 71 DRCU identifying faults, 264 preserve calibration feature, 51 DRCU calibration bay level offset tables, 217 checking VSWR, 211 transmitter output power, 211 DRCUII, identifying faults, 264 DRCU3, identifying faults, 264 DRCU3 calibration bay level offset tables, 217 checking VSWR, 212 transmitter output power, 212

31st Jul 01
68P02901W43-J
I3
GSM-100-423
DRCUII calibration bay level offset tables, 217 checking VSWR, 212 transmitter output power, 212 Drive testing audio call faults, 1018 call classification, 1010 data analysis, 1011 data collection overview, 108 data collection process, 109 diagnosing results, 1011 drive test report, 1020 dropped call rate, 1014 effects of recommendations, 1020 FICS, 109 handover failure rates, 1012 high blocking cells, 1016 implementation of recommendations, 1020 mean time between drops, 1019 no audio calls, 1016 noisy calls, 1016 optimization, 104 personnel requirements, 109 poor quality service calls, 1016 preparation, 104 process, 108 residual defect investigation, 1021 results forms, 1155 set up failure rates, 1013 tables, 1160
Excell alarms, verifying, 255 battery fault, 261 comms PSU fail, 261 door open, 257 external 0, 262 external 1, 262 external 2, 263 external 3, 263 fan fail, 258 inverter fail, 260 low dc voltage, 259 mains fail, 258 MCB trip, 260 over temperature, 257 rectifier fail, 259 smoke, 256
F
frequencies DCS1800 channels, 911 EGSM channels, 98 GSM channels, 92 PCS1900 channels, 930
G
GCLK, calibrating, 251 MCell2/6, 379, 446 MCellaccess, 719 MCellcity, 629 record form, 254, 722 GSM, channel frequencies, 92
H
Horizonmacro bay level offset calibration, 425 CTU, bay level offset calibration, 425
I E
E1 link, checking, 712 E1/T1 link, checking, 242 MCell2/6, 375, 442 MCellcity, 627 EGSM, channel frequencies, 98 integrating the base site with logging software, 82 with no connection to the MSC, 88 without logging software, 85 the transcoder, 246, 715
M
MCell2/6 bay level offset calibration, 337, 356 TCUB, bay level offset calibration, 356 TCU900/1800/1900, bay level offset calibration, 337
I4
31st Jul 01
GSM-100-423
MCellaccess GCLK, calibrating, 719 optimization, definition, 71 results forms BSC/XCDR, 1150 PCC, 1146 MCellcity commissioning carrier change, 613 check, battery, 625 check, E1/T1 link, 627 check, output power, 612 check, vswr, 612 downloading, code, 65 downloading, from PCMCIA, 66 GCLK calibration, 629 test equipment, hardware integration, 62
power circuit breakers CU, 78 negative earth BSSC/RXCDR, 28 negative earth BTS, 27 PCC, 77 positive earth BSSC/RXCDR, 28 positive earth BTS, 27 testing supply, 25, 76 verifying PSM version, 714 preserve calibration feature, 51
R
RCU, identifying faults, 264 RTC, tuning, 29 RXCDR, optimization results forms, 1141
N
network, optimization, 102 network optimization, stages, 103
S
SCU900/1800 identifying faults, 264 preserve calibration function, 51 SCU900/1800 calibration bay level offset tables, 231 checking VSWR, 225 transmitter power output, 225
O
optimization drive testing, 104 equipment for, 22, 72 network, 102 results forms BSC/RXCDR, 1141 BTS/BSS/MCell, 111 drive testing, 1155 tables, drive testing, 1160 test leads 9 to 9 way, 23, 73 9 to 25 way, 23, 74 test plugs A, 24, 75 B, 24, 75 C, 24, 75
T
TCUB calibration bay level offset tables, 356 checking VSWR, 319 transmitter power output, 319 TCU900/1800/1900, preserve calibration feature, 51 TCU900/1800/1900 calibration bay level offset tables, 337 checking VSWR, 36 transmitter output power, 36 Test equipment, hardware integration, 32, 42 test equipment 2.048 Mbit/s checks, MCellcity, 627 calibration, 22, 72 for optimization, 22, 72 integrating base site, without logging software, 85 integrating the base site no connection to the MSC, 88 with logging software, 82 test leads, for optimization 9 to 9 way, 23, 73 9 to 25 way, 23, 74
P
PCC, results forms, MCellaccess, 1146 PCS1900, channel frequencies, 930 PIX, verifying connections, 244

31st Jul 01
68P02901W43-J
I5
GSM-100-423
test plugs, for optimization A, 24, 75 B, 24, 75 C, 24, 75 testing, dc power supply, 25, 76 transcoder, integrating, 246, 715 transmitter output power calibration CTU, 46 DRCU, 211 DRCU3, 212 DRCUII, 212 SCU900/1800, 225 TCUB, 319 TCU900/1800/1900, 36 tuning the RTC, 29
VSWR, checking, MCellcity TCUm, 612 VSWR, checking CTU, 46 DRCU, 211 DRCU3, 212 DRCUII, 212 SCU900/1800, 225 TCUB, 319 TCU900/1800/1900, 36
V
verifying Excell alarms, 255 battery fault, 261 comms PSU fail, 261 door open, 257 external 0, 262 external 1, 262 external 2, 263 external 3, 263 fan fail, 258 inverter fail, 260 low dc voltage, 259 mains fail, 258 MCB trip, 260 over temperature, 257 rectifier fail, 259 smoke, 256 PSM version, 714
I6
31st Jul 01
CHAPTER 1 INTRODUCTION TO BSS OPTIMIZATION
CHAPTER 2 BTS 4/5/6 EXCELL TOPCELL & BSC OPTIMIZATION
CHAPTER 3 M-CELL 2/6 OPTIMIZATION
CHAPTER 4 HORIZONMACRO OPTIMIZATION
CHAPTER 5 PRESERVE CALIBRATION PROCEDURE
CHAPTER 6 M-CELLCITY/M-CELLCITY+ OPTIMIZATION
CHAPTER 7 ACCESS AND OFFICE OPTIMIZATION
CHAPTER 8 BASE SITE INTEGRATION
CHAPTER 9 CHANNEL NUMBERS AND FREQUENCIES
CHAPTER 10 NETWORK OPTIMIZATION
CHAPTER 11 OPTIMIZATION RESULTS FORMS
INDEX
BSS Optimization
GSR
Installation & Configuration GSM-100-423 GSM Software Release 5
68P02901W43-J
CHAPTER 6 M-CELLCITY/M-CELLCITY+ OPTIMIZATION
CHAPTER 7 ACCESS AND OFFICE OPTIMIZATION
CHAPTER 8 BASE SITE INTEGRATION
CHAPTER 9 CHANNEL NUMBERS AND FREQUENCIES
CHAPTER 10 NETWORK OPTIMIZATION
CHAPTER 11 OPTIMIZATION RESULTS FORMS
INDEX
BSS Optimization
GSR
68P02901W43-J
GSR
68P02901W43-J
BSS Optimization
BSS Optimization
Installation & Configuration
Positin mark for TED spine

CTU Calibration

Cargado por

Información del documento

Descripción original:

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

CTU Calibration

Cargado por

Copyright:

Formatos disponibles

GSM-100-423 GSM Software Release 5

Installation & Configuration BSS Optimization

E Motorola 19932001 All Rights Reserved Printed in the U.K.

Installation & Configuration: BSS Optimization

Copyrights, notices and trademarks

Installation & Configuration: BSS Optimization 68P02901W43-J

Chapter 1 Introduction to BSS optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 BTS4/5/6 ExCell TopCell & BSC optimization . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation & Configuration: BSS Optimization

Chapter 3 M-Cell2/6 optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation & Configuration: BSS Optimization

379 379 379 379 380 381

Chapter 4 Horizonmacro optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation & Configuration: BSS Optimization

Chapter 5 Preserve calibration procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6 M-Cellcity/M-Cellcity+ optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7 M-Cellaccess and Horizonoffice optimization . . . . . . . . . . . . . . . . . . . . . . . . .

Installation & Configuration: BSS Optimization

Chapter 8 Base site integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9 Channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCS1900 channel numbers and frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10 Network optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11 Optimization results forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation & Configuration: BSS Optimization

Installation & Configuration: BSS Optimization 68P02901W43-J

Issue status of this manual

Issue status of this manual

Resolution of Service Requests

Installation & Configuration: BSS Optimization

About this manual

Installation & Configuration: BSS Optimization 68P02901W43-J

Special key sequences

Installation & Configuration: BSS Optimization

First aid in case of electric shock

First aid in case of electric shock

Installation & Configuration: BSS Optimization 68P02901W43-J

Reporting safety issues

Reporting safety issues

Installation & Configuration: BSS Optimization

Warnings and cautions

Warnings and cautions

Example and format

Example and format

Installation & Configuration: BSS Optimization 68P02901W43-J

Installation & Configuration: BSS Optimization

Installation & Configuration: BSS Optimization 68P02901W43-J

Human exposure to radio frequency energy (PCS1900 only)

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposures

Power density (S)

Installation & Configuration: BSS Optimization

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposure ceilings

1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2

Installation & Configuration: BSS Optimization 68P02901W43-J

Human exposure to radio frequency energy (PCS1900 only)

Power density measurements

Installation & Configuration: BSS Optimization

Beryllium health and safety precautions

Beryllium health and safety precautions

Installation & Configuration: BSS Optimization 68P02901W43-J

Beryllium health and safety precautions

Product life cycle implications