BSS11

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
COURSE ADMINISTRATION BSS OVERVIEW BSSC CABINET HORIZONMACRO HORIZONMICRO/COMPACT

OPERATIONAL THEORY OPERATIONAL THEORY OPERATIONAL THEORY
CHAPTER 6 CHAPTER 7 CHAPTER 8 CHAPTER 9 CHAPTER 10
HORIZONOFFICE EQUIPMENT APPRECIATION BSS SOFTWARE BSS CUSTOMER MMI COURSE ASSESSMENT
OVERVIEW
GLOSSARY OF TERMS
Cellular Infrastructure Group
ISSUE 1 REVISION 2
BSS11
BASE STATION SYSTEMS – OPERATIONAL
THEORY
FOR TRAINING PURPOSES ONLY

ISSUE 1
REVISION 2
BSS11
BASE STATION
SYSTEMS –
OPERATIONAL
THEORY
FOR TRAINING
PURPOSES ONLY
BSS11
BASE STATION SYSTEMS –
OPERATIONAL THEORY
ISSUE 1 REVISION 2
BSS11
Base Station Systems –
Operational Theory
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000

All Rights Reserved
Printed in the U.K.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory i

ISSUE 1 REVISION 2
Copyrights, notices and trademarks
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
and MOTOROLA are trademarks of Motorola Inc.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through
X/Open Company Limited.
Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers
Incorporated.
X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology.
Looking Glass is a registered trademark of Visix Software Ltd.
OSF/Motif is a trademark of the Open Software Foundation.
Ethernet is a trademark of the Xerox Corporation.
Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd.
SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation.
IBM is a registered trademark of International Business Machines Corporation.
HP is a registered trademark of Hewlett Packard Inc.
ii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

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

ISSUE 1 REVISION 2
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1
Course Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Chapter 2
BSS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Network Switching System (NSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Operations and Maintenance System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Base Station System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Transcoder (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
RF Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Chapter 3
Base Station System Controller (BSSC) Cabinet Operational Theory . . . i
Transcoder (XCDR) Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Transcoder (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Transcoder Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
iv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Base Station Controller (BSC) Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Signalling Interface Interconnections (RXCDR/BSC/BTS) . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Transcoder Base Site Link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Base Station System Control (BSSC) Cabinet Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Cabinet types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
External features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
BSSC Cabinet Internal Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
BSU / RXU Shelf (up to two per cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Power Distribution Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Distribution Alarm Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Interconnect panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Switch settings (BSSC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Visual warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Fuses and LEDs (BSSC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25
Power Distribution Unit (PDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Input power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
BSSC2 Cabinet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Power supply modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Cabinet power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Integrated Power Supply Module (IPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Enhanced Power Supply Module (EPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
Shelf Internal Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Time Division Multiplexed (TDM) highway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Motorola Cellular Advanced Processor (MCAP) bus . . . . . . . . . . . . . . . . . . . . . . . 3–46
Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Serial bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Base Station Unit (BSU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
Base Station Unit Shelf Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
Base Station Unit (BSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory v

ISSUE 1 REVISION 2
Remote Transcoder Unit (RXU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50

Remote Transcoder Unit Shelf Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Remote Transcoder Unit (RXU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Bus Termination Card (BTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
The Generic Processor (GPROC) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–54
GPROC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–56
BTS and BSC GPROC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–58
RXCDR GPROC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–60
The Generic Processor (GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Brief description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Troubleshooting and diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
BTS and BSC GPROC2 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–66
GPROC2 task groups and device types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–66
RXCDR GPROC2 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–68
Type 43 interconnect board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
T43 connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–72
Balanced-line Interconnect Board (BIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
BIB connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–76
Multiple Serial Interface (MSI/MSI2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
MSI/MSI2 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
E1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
T1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
Transcoded environment (E1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–81
Transcoded environment (T1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–81
MC68000 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
Clock extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
Frame decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–84
Frame decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–84
E1/T1/JT1 line to TDM interface circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–86
vi BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
The Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Clock control/alarm logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Buffered test ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Reference oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference dividers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference fail detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
GCLK Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Closed loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94
GCLK Synchronization Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94
Transcoder Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
The Digital Signal Processor (DSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
Subrate multiplexer modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
Line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
MCAP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
TDM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
The Generic DSP Processor (GDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–102
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–102
The Parallel Interface Extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
PIX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
The Battery Backup Board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
BBBX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
LANX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Local LAN data switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–110
Extended LAN data switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–112
Bus arbiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–112
Redundant LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Shelf ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory vii

ISSUE 1 REVISION 2
Motorola Cellular Advanced Processor (MCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–116

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–116
MCAP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Address Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Dual Port Ram (DPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Downlink communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Uplink communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Time Division Multiplexed (TDM) Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
TDM Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
TDM Bus Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
The Kiloport Switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–126
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–126
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–126
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Timing reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Switchbound TDM interface structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Expansion switchbound highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–130
Timeslot Interchange (TSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–130
Three-Party Conference (TPC) memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Fixed/dynamic pattern registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Outbound selection MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Highway monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Watchdog timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Interrupt logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
Serial interface logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW in a BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW in a RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
BSSC Cabinet Extension and Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Remote (KSWXR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–138
Local (KSWXL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–138
Expansion (KSWXE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–140
The Clock Extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
CLKX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
Generic Clock (GCLK) Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–144
Appendix A
Student Exercise, Cabinet Inter-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . i
Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–1
Interconnection Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
PART A – KSW and GCLK Expansion/Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–4
PART B – Board Requirement and LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–8
viii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
LANX Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–10
Appendix B
Cabinet Inter-Connection Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Board Requirement and LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppB–3–4
Part B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppB–3–4
Chapter 4
Horizonmacro Operational Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
BSC–BTS Interconnection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
BSC–BTS Interconnection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Horizonmacro Indoor Introduction and Manual Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Overview of Horizonmacro Indoor and external view . . . . . . . . . . . . . . . . . . . . . . . 4–10
Overview of Horizonmacro Outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Overview of Horizonmacro 12 Carrier Outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Cabinet Structure of the Horizonmacro Indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Empty cabinet and SURF harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
SURF harness and cabinet attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Top panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Top panel description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Cage Backplane Interface panel harness Assembly (CBIA) . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA cage function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA backplane function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
CBIA harness function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Interface panel function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Cabinet Door and Hood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Hood function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Securing pins and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Stacking Bracket Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
Indoor temperature control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Overview of indoor temperature control system . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Temperature shutdown sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Cabinet restart after shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Indoor fan overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Fan operation and restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Filter sheet option and effect on fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Power Supply Modules (PSMs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Types of PSM and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
PSM location and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Circuit Breaker Module (CBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
Circuit Break Module (CBM) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
Operation of CBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory ix

ISSUE 1 REVISION 2
Outdoor cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48

Overview of structure description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
SURF harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
SURF harness detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
Top section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
Top section description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
Krone blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
Earth plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
Blank and expansion plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
Power supply enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Power supply enclosure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
Alarms interface board connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
TMS test switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–60
Customer equipment racking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–60
Outdoor cabinet doors and lid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Lid function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Horizonmacro outdoor temperature control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Temperature control overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Cabinet over temperature control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Temperature sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Thermal Management System (TMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–66
TMS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–66
Heat exchanger components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–68
TMS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–70
Horizonmacro outdoor power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
Power supply overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
Power distribution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
AC distribution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–74
DC power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–78
DC distribution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–78
DC distribution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
Customer equipment power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
Internal battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
External battery backup connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
Control and Alarm Board (CAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–82
Introduction to the CAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–82
CAB indicators and controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–84
CAB front panel fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–85
CAB control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–86
CAB alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–88
CAB additional functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–90
The Outdoor Power Supply Module (TOPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
TOPSM overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
TOPSM functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
LED display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Protection circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Thermal protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Control and alarm signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–98
x BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100

MicroBCU Power Supply Module (BPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100
Auxiliary equipment housing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Introduction to the auxiliary equipment housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Auxiliary equipment housing mechanical design . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Temperature control within the auxiliary equipment housing . . . . . . . . . . . . . . . . . . . . . . . 4–104
Temperature control equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
Operation of the temperature control equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
Auxiliary equipment housing as a battery box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
External alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
Function of the external alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
External alarms interface board connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
Horizonmacro 12 carrier outdoor enclosure structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Introduction to the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Enclosure description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Alarm Interface Module (AIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
Functional description of the AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
AIM connectors and switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
Primary ac terminal box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–114
Primary ac terminal box location and function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–114
Fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Introduction to the fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Fan tray description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Operation of the smoke detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–118
Enclosure lighting description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–118
Doors and hood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Operation of the door locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Hood function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–122
Hood operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–122
Cable entry to the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Cable entry overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Low level cable entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Optional high level cable entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–126
Optional cable shroud and termination bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–128
Overview of the power distribution equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–130
Operation of the power distribution equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–130
AC power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
AC distribution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
AC circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
DC circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–138
DC fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–138
The power control module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–140
Overview of the power control module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–140
Front panel controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–142
Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–144
Alarm inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–144
Alarm output signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–145
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xi

ISSUE 1 REVISION 2
The rectifier module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–146

The dc connector panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–148
Description of the dc connector panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–148
Internal battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–150
Overview of the internal battery backup system . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–150
Battery thermal charge compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–152
Horizonmacro digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
MCUF and NIU redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Full size and half size modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Overview locations and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Digital module and CTU connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–156
Main Control Unit with dual FMUX (MCUF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
MCUF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
Capability to replace MCU of M-Cell6 and M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
GPROC KSW and GLCK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
Front panel interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–160
Front panel switches and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–162
PIX and GPS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–162
DRAM, flash EPROM and code loading functions . . . . . . . . . . . . . . . . . . . . . . . . . . 4–164
ASIC functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–166
Sync block functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–168
Link to redundant MCUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–170
The Network Interface Unit (NIU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
Overview of NIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU command identity number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–174
Control processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–176
NIU/MCUF framing and clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–176
Distance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
Radio Signalling Links (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
T1 NIU need to set link type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Overview of T43/BIB-NIU connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
NIU to T43 mapping and command ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–181
Fibre Optic Mulitplexer (FMUX) module and FMUX function . . . . . . . . . . . . . . . . . . . . . . 4–184
Overview of FMUX module and internal MCUF FMUX . . . . . . . . . . . . . . . . . . . . . 4–184
FMUX Functional explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–186
Alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module replacement – effect on alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm collection from extension cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module display presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–190
xii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Horizonmacro RF Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–192

RF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–192
Receive RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
Transmit (Tx) RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
Rx/Tx single antenna duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
RF main component explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–196
RF loopback purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
RF loopback hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
RF loopback software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
Description of RF test modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
The Compact Transceiver Unit (CTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
Overview of CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
CTU internal boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
CTU connectors and reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–202
Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–202
CTU Tx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–204
CTU Rx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–206
CTU digital processing and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–208
CTU uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–212
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
Overview of frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
Synthesizer Frequency Hopping (SFH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
SFH example not through BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–216
SFH example hopping through BCCH carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–216
Base Band frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–218
The Sectorized Universal Receiver Front end (SURF) module . . . . . . . . . . . . . . . . . . . . 4–222
SURF module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–222
Functional description of 1800 SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–224
Functional description of 900 SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–226
Transmit (Tx) blocks overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Tx block overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Transmit block connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Blanking plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
Purpose of blanking plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
Purpose of feedthrough plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
The Hybrid Combining Unit (HCU) plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
HCU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
HCU connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
The Twin Duplexed Filter (TDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
Overview of TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
TDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
Dual band TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
Overview of Dual band TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
Dual band TDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
The Duplexed Combining bandpass Filter (DCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
DCF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
DCF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
The Dual-stage Duplexed combining Filter (DDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240
Overview of DDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240
DDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xiii

ISSUE 1 REVISION 2
The Cavity Combining Block (CCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242

CCB overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
CCB Control Board (TCB) and set switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
TCB and link redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
CCB configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–244
CCB functional description and diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–244
Appendix C
Suggested RF Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Suggested RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–1
Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–1
Configuration for omni 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–1
Configuration for omni 1 or 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–2
Configuration for sector 1/1 or 2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–5
Configuration for sector 1/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–6
Configuration for single cabinet sector 3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–6
Configuration for 2 cabinet sector 3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–7
Configuration for 2 cabinet sector 5/5 or 6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–8
Configuration for single cabinet sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 . . . . . . . . . . . . AppC–4–9
Configuration for 2 cabinet sector 2/2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–10
Configuration for 2 cabinet sector 3/3/3 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–11
Configuration for sector 5/5/5 or 6/6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–14
Configuration for sector 8/8/8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–15
Configuration for dual band 1/1/1-3/3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–16
Chapter 5
Horizonmicro/Horizoncompact Operational Theory . . . . . . . . . . . . . . . . . . . . i
Horizonmicro manual definition and introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Overview of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
BTS enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Overview of BTS enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Overview of booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
BTS power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of BTS power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of BTS Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Distribution board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
AC-DC Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
Alarms, warnings and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Optional Battery Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Description of battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Booster power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Overview of booster power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
AC power connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
xiv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Booster Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26

AC-DC BPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Heat management of BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Overview of BTS heat management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Module heaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Enclosure cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Overview of enclosure cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Airflow within the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32
Heat management of booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Overview of booster enclosure cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Overview of digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Radio Digital Interface System (RDIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Overview of RDIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Main Control Unit, micro (MCU-m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Overview of MCU-m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Processor functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
68LC060 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
QUICC32 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
PCMCIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Crosspoint switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Sync block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
MMI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Electronic board ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Electronic site ID and calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Olympus Radio Architecture Controller (ORAC) function . . . . . . . . . . . . . . . . . . . . . . . . . 5–48
Overview of ORAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–48
DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Overview of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Location of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Introduction to DINO/RHINO functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
Processing section of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
Reset switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Line interface framers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Radio signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
High bit-rate Digital Subscriber Line (HDSL) module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Overview of HDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Functional description of HDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Overview of line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Terminology for Tx and Rx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
Features of line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
HDSL link options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Overview of GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Location of GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xv

ISSUE 1 REVISION 2
RF modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–70
Dual Transceiver (DTRX) module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Overview of DTRX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Synthesizer section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–74
Receiver section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–76
Transmitter section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–78
Temperature detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
Overview of combiner isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–82
Isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–86
Overview of isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–86
Booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–90
System description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–90
Functional description of booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–92
Chapter 6
Horizonoffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Standard equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Optional equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Architecture of BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Horizonoffice hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Controller Unit Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Overview of power distribution unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Overview of fan cooling system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Overview of specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Torque values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
CU to RF head interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
RF head receiver sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
RF head transmitter output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
Frequency band characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
External features of CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–18
Internal features of CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20
Overview of interconnect panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22
HIB board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Overview of HIB board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Location of HIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Description of HIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Overview of E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Location of E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Description of CIM and BIM boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
xvi BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Base Shelf Unit (BSU) assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28

Overview of BSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
BSU numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
Ventilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–32
Backplane connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–32
HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–34
Overview of HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–34
HDSL connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–36
Power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
Overview of power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
IPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
Functional description of IPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–40
Power Distribution Unit (PDU) components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Overview of PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Input power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
The Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46
Purpose of DAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46
Fuses and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–48
Switch settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–50
Alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–50
Visual warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–52
Communicate alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–52
Cabinet Protection Board (CPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Purpose of Cabinet Protection Board (CPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Requirement of CPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Specifications of CPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56
Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56
Fan cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Location of fan cooling system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Requirements for fan cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Alarm processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Introduction to alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Requirements for CU alarm system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Controller power system alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Controller alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–62
Digital Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Full size boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Half size boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
HDSL modem boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–68
Introduction to HDSL modem boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–68
Purpose of GPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
Requirements of GPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
GPROC2 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xvii

ISSUE 1 REVISION 2
The Bus Termination Card (BTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72

Purpose of BTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72
Requirements of BTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72
Purpose of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Requirements of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Brief description of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Purpose of GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76
Requirements of GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76
The Multiple Serial Interface (MSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
Purpose of MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
Requirements of MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
The LANB Extender half size board (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Purpose of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Requirements of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Brief description of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
The Parallel Interface Extender (PIX) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82
Overview of PIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82
Requirements of PIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82
Purpose of BBBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84
Requirements of BBBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84
The Management Interface Extender (MIX) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Purpose of MIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Requirements of MIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
System clock and interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–88
The Line Terminal Unit (LTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
Purpose of LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
Requirements of LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
Controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
The Exchange office Management Unit (EMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Purpose of EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Requirements of EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
xviii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Overview of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
RF features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Multicarrier head mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Description of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
Physical description of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
Power system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–98
RF transceiver board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–100
RF Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–102
Connector pin-out details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
Main source supply input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
Battery input / output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
External alarm connector on RF PCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
HDSL connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
Multi head Sync Input connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–108
Multi head Sync Output connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–108
Chapter 7
Equipment Appreciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BSS Equipment Appreciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
BSC/XCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
The Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4
Chapter 8
BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Executive and Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
BSS Executive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Operating System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Process Isolation and Memory Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Flexible Interprocess Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Operations and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Functional Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
OMC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Man Machine Interface (MMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Configuration Management (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Configuration Management Database Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
Device and Function Dependancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
Performance Management (PM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16
Fault Management (FM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xix

ISSUE 1 REVISION 2
Central Authority (CA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
Central Authority Device States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Fault Detection and Handling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
BSS Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Fault reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Alarm Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Message formats: Standard Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Alarm Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
Initialization Process (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Initialization in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Initialization in RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
Call Processing at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Message Transfer Part L2 (MTP_L2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Message Transfer Part L3/SCCP Pre–processor . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Call Processing at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Cell Broadcast Scheduler (CBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Allocation Manager (AM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
Radio Subsystem (RSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
RSS Layer 1 Protocol (Layer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
RSS Configuration and Fault Management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Handover Detection and Power Control (HDPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Handover Decision Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
xx BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
Voice Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60
Chapter 9
BSS Customer MMI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
MMI Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Introduction to BSS MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Command Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
Command/Database Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Device and Function Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–10
The Emon Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Executive Monitor and Command List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Rlogin (Remote Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Chapter 10
Course Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
Course Assessment Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Answer Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
A ......................................................................... iv
B ......................................................................... vii
C ......................................................................... x
D ......................................................................... xv
E ......................................................................... xviii
F ......................................................................... xx
G ......................................................................... xxii
H ......................................................................... xxiv
I .......................................................................... xxv
K ......................................................................... xxvii
L ......................................................................... xxviii
M ......................................................................... xxx
N ......................................................................... xxxiv
O ......................................................................... xxxvi
P ......................................................................... xxxviii
Q ......................................................................... xli
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxi

ISSUE 1 REVISION 2
R ......................................................................... xlii
S ......................................................................... xlv
T ......................................................................... xlix
U ......................................................................... lii
V ......................................................................... liii
W ........................................................................ liv
X ......................................................................... lv
Z ......................................................................... lvi
xxii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2 General information
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals
are intended to support the delivery of Technical Education only and are not intended to
replace the use of Customer Product Documentation.
WARNING
Failure to comply with Motorola’s operation, installation and maintenance
instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
About this
manual
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory 1

General information ISSUE 1 REVISION 2
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top
of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
| Press the pipe symbol key.
CR or RETURN Press the Return (Enter) key. The Return key is
identified with the ↵ symbol on both the X terminal and
the SPARCstation keyboards. The SPARCstation
keyboard Return key is also identified with the word
Return.
2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

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

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

ISSUE 1 REVISION 2 Warnings and cautions
Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life,
physical injury, or ill health. This includes hazards introduced during maintenance, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format
WARNING
Do not look directly into fibre optic cables or optical data in/out connectors.
Laser radiation can come from either the data in/out connectors or
unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of
equipment within a system. However, this presents no danger to personnel.
Example and format
CAUTION
Do not use test equipment that is beyond its calibration due date when testing
Motorola base stations.

General warnings ISSUE 1 REVISION 2
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 customer’s failure to comply with these
requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.
Specific
warnings
Warnings particularly applicable to the equipment are positioned on the equipment and
within the text of this manual. These must be observed by all personnel at all times when
working with the equipment, as must any other warnings given in text, on the illustrations
and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single
phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas
where the ac mains power is present must not be approached until the warnings and
cautions in the text and on the equipment have been complied with.
To achieve isolation of the equipment from the ac supply, the mains input isolator must
be set to off and locked.
Within the United Kingdom (UK) regard must be paid to the requirements of the
Electricity at Work Regulations 1989. There may also be specific country legislation
which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment
when in operation. Ensure that all transmitters are switched off when any antenna
connections have to be changed. Do not key transmitters connected to unterminated
cavities or feeders.
Refer to the following standards:
S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.

ISSUE 1 REVISION 2 General warnings
Lifting
equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent
responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Do not ...
... substitute parts or modify equipment.
Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modification of equipment. Contact Motorola if in doubt to
ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material
Beryllium or its oxide Beryllia or both. These materials are especially hazardous if:
S Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
S The dust created by breakage of Beryllia is inhaled.
S Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.

Human exposure to radio frequency energy (PCS1900 only) ISSUE 1 REVISION 2
Human exposure to radio frequency energy (PCS1900 only)

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

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

ISSUE 1 REVISION 2 Human exposure to radio frequency energy (PCS1900 only)
Maximum
permitted
exposure
ceilings
Within the frequency range, the maximum permitted exposure ceiling for uncontrolled
environments is a power density (mW/cm2) that equals f/1500, where f is the frequency
expressed in MHz, and measurements are averaged over a period of 30 minutes. The
maximum permitted exposure ceiling for controlled environments, also expressed in
mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these
principles to the minimum and maximum frequencies for which this equipment is intended
to be used yields the following maximum permitted exposure levels:
Uncontrolled Environment Controlled Environment

1930MHz 1970MHz 1930MHz 1970MHz
Ceiling 1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be
assured at the frequency which produces the lowest exposure ceiling (among the
frequencies at which operation will occur).
Licensees must be able to certify to the FCC that their facilities meet the above ceilings.
Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating
compliance, but this equipment operates at power levels orders of magnitude higher, and
the exclusion is not applicable.
Whether a given installation meets the maximum permitted exposure ceilings depends, in
part, upon antenna type, antenna placement and the output power to which this
equipment is adjusted. The following example sets forth the distances from the antenna
to which access should be prevented in order to comply with the uncontrolled and
controlled environment exposure limits as set forth in the ANSI IEEE standards and
computed above.

Human exposure to radio frequency energy (PCS1900 only) ISSUE 1 REVISION 2
Example
calculation
For a base station with the following characteristics, what is the minimum distance from
the antenna necessary to meet the requirements of an uncontrolled environment?
Transmit frequency 1930MHz
Base station cabinet output power, P +39.0 dBm (8 watts)
Antenna feeder cable loss, CL 2.0dB
Antenna input power Pin P–CL = +39.0–2.0 = +37.0dB (5watts)
Antenna gain, G 16.4dBi (43.65)
Using the following relationship:
G + 4pr W
2
Pin
Where W is the maximum permissible power density in W/m2 and r is the safe distance
from the antenna in metres, the desired distance can be calculated as follows:
r+ ǸGPin + Ǹ 43.65 5 + 1.16m

4pW 4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from
mW/cm 2 to W/m2.
NOTE
The above result applies only in the direction of maximum radiation of the
antenna. Actual installations may employ antennas that have defined radiation
patterns and gains that differ from the example set forth above. The distances
calculated can vary depending on the actual antenna pattern and gain.
Power density
measurements
While installation calculations such as the above are useful and essential in planning and
design, validation that the operating facility using this equipment actually complies will
require making power density measurements. For information on measuring RF fields for
determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice
for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave,
IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be
purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn:
Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331,
(800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this
equipment are urged to consult these standards in determining whether a given
installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio
frequency radiation may depend not only on this equipment but also on whether the
environments being assessed are being affected by radio frequency fields from other
equipment, the effects of which may add to the level of exposure. Accordingly, the overall
exposure may be affected by radio frequency generating facilities that exist at the time
the licensee’s equipment is being installed or even by equipment installed later.
Therefore, the effects of any such facilities must be considered in site selection and in
determining whether a particular installation meets the FCC requirements.

ISSUE 1 REVISION 2 Beryllium health and safety precautions
Beryllium health and safety precautions
Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in
Oxygen.
With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium
compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive
within the component it presents no health risk whatsoever. However, if the component
should be broken open and the Beryllium Oxide, which is in the form of dust, released,
there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms
of Berylliosis are similar to Pneumonia and may be identified by all or any of the
following:
Mild poisoning causes fever, shortness of breath, and a cough that produces
yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous
membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty
with swallowing and breathing.
Severe poisoning causes chest pain and wheezing which may progress to severe
shortness of breath due to congestion of the lungs. Incubation period for lung symptoms
is 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.

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

implications
Motorola GSM and analogue equipment includes components containing Beryllium Oxide
(identified in text as appropriate and indicated by warning labels on the equipment).
These components require specific disposal measures as indicated in the preceding
(Disposal methods) paragraph. Motorola will arrange for the disposal of all such
hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange
for the most environmentally “friendly” disposal available at that time.

ISSUE 1 REVISION 2 General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola GSM manuals. Failure to comply with these
cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in
damage to the equipment. Motorola assumes no liability for the customer’s failure to
comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge.
Although the damage caused by static discharge may not be immediately apparent,
CMOS devices may be damaged in the long term due to static discharge caused by
mishandling. Wear an approved earth strap when adjusting or handling digital boards.
See Devices sensitive to static for further information.

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

ISSUE 1 REVISION 2 Motorola GSM manual set
Motorola GSM manual set
Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Category Name Catalogue

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

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

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

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

number number
GSM-001-103 System Information: BSS Equipment Planning 68P02900W21
GSM-002-103 System Information: DataGen 68P02900W22
GSM-005-103 System Information: Advance Operational 68P02900W25
Impact
GSM-008-403 Installation & Configuration: Expert Adviser 68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not
release dependent. The internal organization and makeup of service manual sets may
vary, they may consist of from one to four separate manuals, but they can all be ordered
using the overall catalogue number shown below:

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

ISSUE 1 REVISION 2 Motorola GSM manual set
Category number
The category number is used to identify the type and level of a manual. For example,
manuals with the category number GSM-100-2xx contain operating information.
Catalogue
number
The Motorola 68P catalogue number is used to order manuals.
Ordering
manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the catalogue number. Remember, specify
the manual issue required by quoting the correct suffix letter.

Motorola GSM manual set ISSUE 1 REVISION 2

Chapter 1
Course Administration

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 1
Course Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Chapter Objectives
Chapter Objectives
On completion of this chapter the student should be able to:
S Identify and explain procedures to be undertaken in accordance with course
administration policy.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory 1–1

Course Introduction ISSUE 1 REVISION 2
Course Introduction
Facility Entry and exit:
Control of movement whilst attending the Motorola training facility at Europark is by the
use of the pac tag system. A pac tag will be issued daily upon signing in at the front
security reception desk.
Fire Drill:
In the event of the fire alarm sounding all students are to proceed as instructed and
assemble at the front of the building, outside reception, on the grass verge.
Fire exit points/routes are displayed in reception and at the entrance of the classroom
corridor. Students are advised to familiarise themselves with this information.
Participant List:
All students are to complete the participant list as indicated. Correct spelling of the
student’s name is essential. It is from this list that the name of the student will be taken
for inclusion on the end of course certificate.
Next Of Kin Forms:

All overseas students are requested to complete a Next Of Kin form. This will be used in
the case of an emergency to contact a relative in the student’s home country.
Name Cards:
All students are to complete the name card found at the front of their course manuals,
and place it in a prominent position on their desk.
Toilets:
Toilets are located through the door at the base of the stairs to the rear of the front
security desk. Alternative toilets are at the top of the stairs behind the front security
desk.
Smoke Room:
The designated smoking room is located in the vicinity of the ground floor toilets through
the pac tag controlled door. Other than this location smoking is allowed nowhere on
Motorola premises. Students who wish to smoke outside must do so beyond the
perimeter fence.
Customer Care Administrator:

The customer care administrator at Europark is located in course reception, situated
through the double doors just to the right of Europark reception main entrance. Students
with administrative problems are to contact the customer care administrator.
It is not the job of the customer care administrator to book taxies or arrange
accommodation.
A taxi service can be contacted using the phone located at course reception.
Accommodation problems are to be directed to BTI in Glasgow (Tel: 8706074777).
1–2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2 Course Introduction
Student telephone: (Swindon Only)

The ONLY free phone students are permitted to use is the allocated student phone next
to the customer care administration reception desk; a pay phone also located in that
area.
The student phone should only be used in the case of personal emergency or for
important business calls.
Calls should be kept to a maximum of 5 minutes to allow other students to use the
phone.
The phone is electronically locked from making international calls at all times except
1200 – 1400 and 1500 – 1530 daily.
Mobile Phones:
Mobile phones are to be turned to silent (vibrate) mode, or switched off during lessons. If
a student has to make or receive a call they must leave the room to do so.
Student Badge:
A student badge will be issued on a daily basis whilst the student is attending a course at
Motorola. The front security desk at Europark main entrance reception will issue the
student badge.
The issued badge entitles the holder to:
S A free meal at lunchtime:
1 x soft drink.
1 x starter.
1 x main course.
1 x dessert.
S Free hot drinks from the restaurant vending machines throughout the day.
No confectionery can be obtained using the student badge.
Course Brochure:
A course brochure advertising all courses run by Motorola, Technical Education and
Documentation, is available on request.
Prerequisites:
All students attending this course should have attended CP02 – Introduction to Digital
Cellular.
Course Assessment:
The assessment paper, which is to be undertaken at the end of the course, is for
Motorola evaluation purposes only. Certificates will be issued regardless of the
assessment mark obtained.
Course Evaluation Form:

A course evaluation form is to be completed at the end of the course. Guidelines on how
to complete the form are to be followed rigidly, as the results will be scanned. The
instructor delivering the course will issue instructions on how to complete the evaluation
form correctly.

Course Introduction ISSUE 1 REVISION 2

Chapter 2
BSS Overview

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 2
BSS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GSM Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Network Switching System (NSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Operations and Maintenance System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Base Station System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Transcoder (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Base Station Controller (BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Interfacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
RF Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10

ISSUE 1 REVISION 2

Chapter Objectives
S Describe the various components that make up a Public Land Mobile Network
(PLMN), and explain their role within the network.
S Describe where in the PLMN the Base Station Subsystem resides, explaining the
simplified functional requirements of each component within it.

GSM Network Components ISSUE 1 REVISION 2
GSM Network Components

The following is a listing with a brief explanation of the major system components of the
GSM System.
Mobile Station
(MS)
The radio equipment and man-machine interface that a subscriber needs to access
PLMN services.
Base Station
System (BSS)
The fixed end of the radio interface that provides control and radio coverage functions for
one or more sites and their associated mobile stations. The BSS includes:
Base Transceiver Station (BTS) – The BTS cabinet is capable of operating as a BTS or
as a completely self-contained BSS with up to five RF carriers in a single cabinet. The
BTS is discussed in greater detail later in this course.
Base Station Controller (BSC) – The BSC cabinet is only used at BSC sites and
provides the required expansion capabilities to interface to the maximum number of
remote BTS’s allowed by the Motorola GSM BSS offering. The BSC can be a cabinet to
itself or as a function at other cabinets. The BSC is discussed in greater detail later in
this course.
Transcoder Function (XCDR) – Converts the signal from 64kbs A-law to 13kbit/s GSM
speech.
Network
Switching
System (NSS)
Mobile Switching Centre (MSC) – The telephone switching exchange for mobile
originated or terminated subscriber traffic.
Authentication Centre (AUC) – Generates and stores authentication parameters for

subscriber identification.
Equipment Identity Register (EIR) – The data base oriented processing network entity
that contains centralized data base information for validating mobile stations based on
their international mobile equipment identity.
Visitor Location Register (VLR) – The database oriented processing network entity that
temporarily contains information for subscribers roaming in a given location area.
Home Location Register (HLR) – The database oriented processing network entity that
contains the master data base of the subscribers to a PLMN.
Echo Canceller (EC) – Performs echo suppression for all voice circuits.
Interworking Function (IWF) – Performs data rate adaptation between Public Land
Mobile Network (PLMN) and other existing land networks.

ISSUE 1 REVISION 2 GSM Network Components
Operations and
Maintenance
System
Operations and Maintenance Centre (OMC) – A central network entity that controls
and monitors other network entities, including the quality of service provided by the
network. Two OMCs are used, OMC-R for the BSS monitoring and OMC-S for MSC
monitoring.
Network Management Centre (NMC) – Performs hierarchical regionalized network
management of the complete GSM system.

GSM Network Components ISSUE 1 REVISION 2
Base Station System Components
PSTN
NSS
AUC HLR IWF EIR EC VLR

MSC
VLR
MSC OMC–S NMC
NMS
BSS
XCDR OMC–R
XCDR BSC
BTS BSC BTS
BSS
BTS BTS
XCDR BSC
BSS
BTS BTS
BSS11_02_02

ISSUE 1 REVISION 2 Base Station System Components
Base Station System Components
Base Station
System (BSS)
The GSM Base Station System is the equipment found at a cell site. It comprises of a
combination of digital and RF equipment. The BSS provides the link between the mobile
equipment and the Mobile Services Switching Centre.
The BSS communicates with the Mobile Station over the digital air interface and with the
Mobile Services Switching Centre (MSC) via 2 Mbit/s links.
The BSS consists of three major hardware components:
1. The Transcoder (XCDR)
The Transcoder is used to reduce the data rate of signals from the Network Switching
System so that they can be efficiently sent over the air interface. Although the
Transcoder is considered to be a part of the BSS, it is very often located closer to the
MSC.
2. The Base Station Controller (BSC)
The BSC, as its name implies, provides the control for the BSS. The BSC
communicates directly with the MSC. The BSC may control single or multiple BTSs.
3. The Base Transceiver Station (BTS)
The BTS contains the RF components that provide the air interface for a particular cell.
This is the part of the GSM network which communicates with the mobile. The Antenna
is included as part of the BTS.

Base Station System Components ISSUE 1 REVISION 2
Base Station System (BSS)
Network Switching System
BSS
XCDR
BSC
BTS
BSS11_02_03

ISSUE 1 REVISION 2 Transcoder (XCDR)
Transcoder (XCDR)
The first task carried out by the BSS, on information coming from the MSC, is
‘Transcoding’. This converts the information from 64kbit/s PCM into 13kbit/s GSM
defined speech.
To do this the Transcoder needs to meet certain functional requirements. These can be
divided into three areas.
Interfacing
The serial links carrying the information from the Mobile Services Switching Centre
(MSC) to the Transcoder (XCDR) must meet the correct interface and termination points
at the XCDR.
Serial links carrying information leaving the XCDR, going to the Base Station Controller
(BSC), must again be interfaced correctly. Formatting of the information must also be
undertaken by the interface prior to placement onto the link.
Transcoding
The primary function of the Transcoder is to perform transcoding and data–rate adaption.
A Transcoder Rate Adaption Unit provides this function.
Switching
Speech and data information from a trunk circuit, coming into the Transcoder, must be
routed to the correct BSC. A unit called a Kiloport Switch provides for this function.
These functional requirements are performed under ‘processor control’. This gives the
flexibility to make changes with software variations.
A more detailed functional description of the XCDR will be given in chapter 3.

Transcoder (XCDR) ISSUE 1 REVISION 2
Transcoder Functional Requirements
MSC
E1 Links
XCDR 2.048Mbit/s
Control Interface Interface Interface Interface

Processor
64kbit/s PCM
TRAU TRAU TRAU TRAU
16kbit/s*
Switch
16kbit/s*
Interface Interface Interface Interface

E1 Links
2.048Mbit/s
BSC BSC
* 16kbit/s after the TRAU module will be

made up 13kbit/s speech/data information
+ 3kbit/s TRAU data.
BSS11_Ch2_04

ISSUE 1 REVISION 2 Base Station Controller (BSC)
Base Station Controller (BSC)

The BSC provides overall Base Station System control. Being at the centre of the BSS it
provides connectivity between the MSC and a number of BTS’s.
To fulfil the role of BSC, specific functional requirements need to be met. These can be
split into two areas.
Interfacing
The transcoded information coming over the E1 links from the XCDR must meet with the
correct interface and termination points at the BSC.
E1 links connecting the BSC to BTS’s under its control must also meet with correct
interface points. Information being placed onto the link must be correctly formatted by the
interface.
Switching
The BSC provides routing for transcoded speech and data, from the XCDR, to the BTS
covering the cell in which the Mobile Station (MS) is located. A unit called a Kiloport
Switch provides this function.
These functional requirements are performed under ‘processor control’. This gives the
flexibility to make changes with software variations.
A more detailed functional description of the BSC will be given in section 3.

Base Station Controller (BSC) ISSUE 1 REVISION 2
BSC Functional Requirements
XCDR
E1 Links
BSC 2.048Mbit/s
Control
Processor
16kbit/s
SWITCH
16kbit/s*
E1 Links
2.048Mbit/s
BTS BTS BTS BTS
BSS11_02_05

ISSUE 1 REVISION 2 Base Transceiver Station (BTS)
Base Transceiver Station (BTS)

The BTS provides the Base Station System with the radio link via which the MS
communicates with the network.
To provide this facility the BTS needs to meet certain functional requirements. These can
be divided into three areas.
Interfacing
Information from the BSC arrives at the BTS on E1 links. These links must be correctly
interfaced and terminated.
Switching
Speech and data arriving at the BTS needs to be routed to the correct MS. This is
achieved by kiloport switch functionality on a module at the BTS.
RF Equipment
The speech and data information is sent to the MS over a radio link. RF equipment at the
BTS provides this function.
A control processor oversees the operation of these functions. This permits changes
through variations in software.
A more detailed description of the functionality of the BTS will be given in chapter 4.

Base Transceiver Station (BTS) ISSUE 1 REVISION 2
BTS Functional Requirements
BSC
E1 Links
BTS 2.048Mbit/s
Control
Processor
Interface Interface
16kbit/s
SWITCH
RF RF RF RF
Equipment Equipment Equipment Equipment
MS
BSS11_02_06


Chapter 3
Base Station System Controller
(BSSC) Cabinet Operational
Theory

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 3
Base Station System Controller (BSSC) Cabinet Operational Theory . . . i
Transcoder (XCDR) Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Transcoder (XCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Terrestrial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Main Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Synchronizing clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Transcoder Static Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Base Station Controller (BSC) Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Signalling Interface Interconnections (RXCDR/BSC/BTS) . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Transcoder Base Site Link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Base Station System Control (BSSC) Cabinet Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Cabinet types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
External features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
BSSC Cabinet Internal Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
BSU / RXU Shelf (up to two per cabinet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Power Distribution Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Distribution Alarm Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Switch settings (BSSC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Visual warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Fuses and LEDs (BSSC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25
Power Distribution Unit (PDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Input power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
BSSC2 Cabinet Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Power supply modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Cabinet power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Integrated Power Supply Module (IPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38

ISSUE 1 REVISION 2
Enhanced Power Supply Module (EPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
Shelf Internal Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Time Division Multiplexed (TDM) highway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Motorola Cellular Advanced Processor (MCAP) bus . . . . . . . . . . . . . . . . . . . . . . . 3–46
Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Serial bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
Base Station Unit (BSU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
Base Station Unit Shelf Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
Base Station Unit (BSU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49
Remote Transcoder Unit (RXU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Remote Transcoder Unit Shelf Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Remote Transcoder Unit (RXU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Bus Termination Card (BTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
The Generic Processor (GPROC) Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–54
GPROC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–56
BTS and BSC GPROC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–58
RXCDR GPROC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–60
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Troubleshooting and diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
BTS and BSC GPROC2 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–66
GPROC2 task groups and device types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–66
RXCDR GPROC2 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–68
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
T43 connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–72
Balanced-line Interconnect Board (BIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
BIB connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–76

ISSUE 1 REVISION 2
Multiple Serial Interface (MSI/MSI2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
MSI/MSI2 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
E1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
T1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
Transcoded environment (E1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–81
Transcoded environment (T1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–81
MC68000 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
Frame decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–82
EPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–84
Frame decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–84
E1/T1/JT1 line to TDM interface circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–86
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Clock control/alarm logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Buffered test ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88
Reference oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference dividers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
Reference fail detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–90
GCLK Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Hold Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Set Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Closed loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94
GCLK Synchronization Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94
Transcoder Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
The Digital Signal Processor (DSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
Subrate multiplexer modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–98
Line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
MCAP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
TDM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–100
The Generic DSP Processor (GDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–102
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–102
The Parallel Interface Extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104
PIX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–104

ISSUE 1 REVISION 2

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
BBBX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–106
Local Area Network (LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
LANX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–108
Local LAN data switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–110
Extended LAN data switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–112
Bus arbiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–112
Redundant LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Shelf ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Motorola Cellular Advanced Processor (MCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–116
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–116
MCAP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Address Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–118
Dual Port Ram (DPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Downlink communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Uplink communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–120
Time Division Multiplexed (TDM) Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
TDM Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
TDM Bus Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–124
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–126
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–126
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Timing reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Switchbound TDM interface structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–128
Expansion switchbound highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–130
Timeslot Interchange (TSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–130
Three-Party Conference (TPC) memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Fixed/dynamic pattern registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Outbound selection MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Highway monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Watchdog timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–132
Interrupt logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
Serial interface logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW in a BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
KSW in a RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–134
BSSC Cabinet Extension and Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–136
Remote (KSWXR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–138
Local (KSWXL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–138
Expansion (KSWXE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–140

ISSUE 1 REVISION 2
The Clock Extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
CLKX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–142
Generic Clock (GCLK) Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–144

ISSUE 1 REVISION 2

Chapter Objectives
S Describe the generic functions of a Transcoder (XCDR).
S Describe the generic functions of a Base Station Controller (BSC).
S Identify and state the function of the XCDR, BSC and Base Transceiver Station
(BTS) signalling interconnections.
S Identify and state the function of the BSSC major subassemblies.
S Describe the configuration of the Base Station Unit (BSU) cage.
S State the function and describe the simplified principles of operation of the
following BSSC Field Replaceable Units (FRUs):
Generic Processor module (GPROC).
Multiple Serial Interface module (MSI).
Generic Clock module (GCLK).
Transcoder module (XCDR).
Generic Digital Processor module (GDP).
Parallel Interface Extender module (PIX).
Battery Back-up Board (BBBX).
S State the function and describe the simplified principles of operation of the BSSC
communications buses.
S Describe the use of the BSSC cabinet extension and expansion options.

Transcoder (XCDR) Functionality ISSUE 1 REVISION 2
Transcoder (XCDR) Functionality

The Transcoder (XCDR) is required to convert the speech or data output from the MSC
(64 kbit/s PCM), into the form specified by GSM specifications for transmission over the
air interface, that is, between the BSS and MS (13 kbit/s).
The 64 kbit/s Pulse Code Modulation (PCM) circuits from the MSC, if transmitted on the
air interface without modification, would occupy an excessive amount of radio bandwidth.
This would use the available radio spectrum inefficiently. The required bandwidth is
therefore reduced by processing the 64 kbit/s circuits so that the amount of information
required to transmit digitized voice falls to 13 Kbit/s. 3 kbit/s of TRAU data contains
information to control the channel coders and call status information such as is DTX on
or off during the call.
The Transcoding function may be located at the MSC, BSC, or BTS.
The TRAU data of 3 kbit/s is added to the 13 kbit/s channel leaving the Transcoding
function to form a gross traffic channel of 16 kbit/s which is transmitted over the
terrestrial interfaces to the BTS. At the BTS the TRAU data is removed and the 13 kbit/s
is processed to form a gross data rate of 22.8 kbit/s for transmission over the air
interface.
For data transmissions the data is not Transcoded but data rate adapted from 9.6 kbit/s
(4.8 kbit/s or 2.4 kbit/s may also be used) up to a gross rate of 16 kbit/s for transmission
over the terrestrial interfaces. Again this 16 kbit/s contains a 3 kbit/s TRAU.
As can be seen from the diagram opposite, although the reason for Transcoding is to
reduce the data rate over the air interface, the loading of the terrestrial links is also
reduced approximately on a 4:1 ratio.

ISSUE 1 REVISION 2 Transcoder (XCDR) Functionality
Transcoder Operation
64 kbit/s TS on E1 64 kbit/s TS on E1
16 0 16 0
M I E A
N J D B
MTL1 SYNC X W MTL1 C B A SYNC
O K G C T
P L H D
R
A
BSC N MSC
S
16 kbit/s TCH C 64 kbit/s TCH
2 bits per sub group O 8bits per sub group
D
16 0
E 16 0
R
U Q RESERVED
RESERVED
RESERVED
RESERVED
V R
MTL2 SYNC P O MTL2 J SYNC
W S
X T
BSS11_3_1

Transcoder (XCDR) ISSUE 1 REVISION 2
Transcoder (XCDR)
The function of the Transcoder is to interface the data link from the MSC to the mobile,
via the BSS.
Terrestrial
Interface
The Terrestrial interface provides the necessary connection to the network via a suitable
link. This interface provides the correct formatting and impedance matching to the
relevant physical link. The most common link types are 2.048Mbit/s E1 link or
1.544Mbit/s T1.
Main Control
Processor
This is the main processor of the site and can be split into two main areas:
S Site Control
This section is in control of the main processes and hardware to maintain the site
integrity. The main functions include internal data bus control and initialization of
the site at power up. It will also look after the environmental aspects of the site, for
example temperature levels.
S Operations and Maintenance
This process collects any faults or operational problems from within the
Transcoder site and report them back to the OMC. It will also report any errors on
the Transcoding boards to the BSC allowing the BSC to inform the MSC of the
faulty circuits. This is because there are no signaling links between the Transcoder
and the MSC. These statistics are used to monitor the network elements, including
details such as the performance of the radios in maintaining the links to the
mobiles, to the amount of processing power used.
Synchronizing
clock
As all the above processes need specific and accurate timing signals each XCDR will be
equipped with a clock to make sure everything is synchronized.
Transcoder Static
Switch
The switch module used in the XCDR to route call information is known as a Timeslot
Switch (TSW). The TSW is a static device, in that its port connections are fixed. This
provides a one to one physical mapping between the traffic channels on the MSC to
XCDR interface and traffic channels on the XCDR to BSC interface.

ISSUE 1 REVISION 2 Transcoder (XCDR)
Function of the Transcoder
MSC
Terrestrial Terrestrial Terrestrial Terrestrial

Synchronising
+ + + +
clock
Transcoding Transcoding Transcoding Transcoding
OMC
Ops +
Maintenance
c
Static Switch
l
o
Sitec
control
k

Main Control
Processor
BSS11_3_2

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

This is the main processor of the site and can be split into three main areas:
S Site Control
the site at power up. It also maintains the environmental aspects of the site, for
example temperature levels.
S Operations and Maintenance
As well as collecting details of any faults or operational problems from within the
whole BSS the Operations and Maintenance area collects performance statistics
and reports them to the controlling entity further up in the network (the OMC).
These statistics are used to monitor the network elements, everything from the
performance of the radios in maintaining the links to the MS, to the amount of
processing power used.
S Switch Manager
The switch manager will connect a mobile terrestrial circuit, allocated by the MSC
for a particular call, to the air interface channel allocated by the BSS. In this
respect it is in control of the dynamic switch ensuring that all calls and signaling
are put through to the correct place be it a control processor or ultimately the MS.
Information about which connections are made is received from the GSM call
processing software resident on the Link Control Processors (LCP).

ISSUE 1 REVISION 2 Base Station Controller (BSC) Functionality
Functions of a BSC

Synchronizing Interface Interface Interface Interface
clock
Ops +
Maint.
Site MSC Link MSC Link Dynamic Switch

Control Processing Processing
Switch GSM Call GSM Call

manager Processing Processing
Main Control Link Control Link Control Interface Interface Interface Interface
Processor Processor Processor
BSS11_3_3

Base Station Controller (BSC) ISSUE 1 REVISION 2
Base Station Controller (BSC)

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

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

The MSC link process, as the name suggests, controls the link back to the MSC from the
BSC, the Message Transfer Link (MTL). This process deals with the Layer 2 and Layer 3
messaging protocols required to interface with the MSC. The MTL carries messages
relating to call processing and operation status.
Note: Generally at the link processor only one of the processes are active at any one
time, either GSM call processing or MSC link processing.
Synchronizing clock
As all the above processes need specific and accurate timing signals each BSC will be
equipped with a clock to ensure they are synchronized.

ISSUE 1 REVISION 2 Base Station Controller (BSC)
Function of a BSC

Synchronizing Interface Interface Interface Interface
clock
Ops +
Maint.
Site MSC Link MSC Link Dynamic Switch

Control Processing Processing
Switch GSM Call GSM Call

manager Processing Processing
Main Control Link Control Link Control Interface Interface Interface Interface
Processor Processor Processor
BSS11_3_3

Signalling Interface Interconnections (RXCDR/BSC/BTS) ISSUE 1 REVISION 2
Signalling Interface Interconnections (RXCDR/BSC/BTS)

To enable each of the network entities to function correctly they must be able to pass
control and status messages to each other. This is done by using several signaling links.
Each of the signaling interfaces normally uses a single 64 kbit/s timeslot on the common
2 Mbit/s link carrier. Some interfaces support multiple timeslot configurations, i.e. more
than one timeslot may be configured to support the signal flow.
Message
Transfer Link
(MTL)
This link exists between the BSC and MSC. The MTL uses the C7 signalling system
including the BSS Application Part (BSSAP). This link provides all control information
between the BSC–MSC, MSC–MS including:
S Requests for initial connection.
S Any change in the attributes in call connection.
S Handling handovers.
Radio Signalling
Link (RSL)
This link exists between the BSC and the BTS. The RSL uses LAPD formatted signalling
and requires 1 x 64kbit/s timeslot or 1 x 16kbit/s channel. Each BTS site will require a
minimum of 1 LAPD signalling channel.
The link provides support for the call processing software at the BTS, allowing the BSC
to send and receive control information. Statistic collection and fault reporting are also
supported.
Transcoder Base
Site Link (XBL)
This is an optional link for control and communications between the RXCDR and BSC.
The XBL provides two-way communication between the master processor in the BSC
and the master processor in the RXCDR. A dedicated 64 kbit/s timeslot is used on the
E1/T1 line between the RXCDR and the BSC. The XBL enables the RXCDR to report
failed traffic circuits at the RXCDR to the BSC. The BSC performs different functions
depending on the type of fault the RXCDR reports:
If RXCDR traffic circuits fail, the BSC disables the circuits by sending blocking messages
to the MSC.
If there are internal RXCDR circuit faults, or faults that do not cause the loss of the serial
communications link, the BSC blocks the affected traffic circuits. For example, if a XCDR
board fails, the BSC blocks the 30 traffic channels associated with that XCDR board.

ISSUE 1 REVISION 2 Signalling Interface Interconnections (RXCDR/BSC/BTS)
Transcoder/BSC/BTS Interconnectivity
0 Sync
MSC 1 1x TFC 64 kbps
2 1x TFC 64 kbps
0 Sync
1 1x TFC 64 kbps 16 MTL BSC 2
OMC RXCDR
(C7) OMC
2 1x TFC 64 kbps
30
OML
Sync
16 MTL BSC 1 31
1
30
OML
Sync
2
31
31 2 1 0
(C7) (X.25)
Sync
31 30 1 0
0
1 OML 1 (X.25)
2 XBL
16 MTL BSC 1
CBC
30 4x TFC 16 kbps
31 4x TFC 16 kbps BSC2
BSC1 0 Sync 0 Sync

(LAPD) 1 RSL 1 OML 2
2 XBL
BTS
28 RTF 1 16 MTL BSC 2
29 RTF 1 (C7)
30 RTF 0 30 4x TFC 16 kbps
BSS11_3_4

Signalling Interface Interconnections (RXCDR/BSC/BTS) ISSUE 1 REVISION 2
Operations and
Maintenance
Link (OML)
This link is for control and communications between the BSS and OMC. OML links from
BSCs are normally nailed through the RXCDR, and OML links from the RXCDR are
direct to the OMC. The OML uses the X.25 protocol. The OMC uses the OML to:
S Load software.
S Load configuration parameters.
S Send messages to, and receive messages from the BSS.
S Collect statistics from BSS
S Fault / event management
Cell Broadcast
Link (CBL)
This link exists between the BSC and the Cell Broadcast Centre (CBC). The CBL uses
the LAPB/X25 protocol. The link is used to pass Short Message Service (SMS) cell
broadcast information from outside the GSM network to the BSC.

ISSUE 1 REVISION 2 Signalling Interface Interconnections (RXCDR/BSC/BTS)
Transcoder/BSC/BTS Interconnectivity
0 Sync
MSC 1 1x TFC 64 kbps
2 1x TFC 64 kbps
0 Sync
1 1x TFC 64 kbps 16 MTL BSC 2
OMC RXCDR
(C7) OMC
2 1x TFC 64 kbps
30
OML
Sync
16 MTL BSC 1 31
1
30
OML
Sync
2
31
31 2 1 0
(C7) (X.25)
Sync
31 30 1 0
0
1 OML 1 (X.25)
2 XBL
16 MTL BSC 1
CBC
30 4x TFC 16 kbps
31 4x TFC 16 kbps BSC2
BSC1 0 Sync 0 Sync

(LAPD) 1 RSL 1 OML 2
2 XBL
BTS
28 RTF 1 16 MTL BSC 2
29 RTF 1 (C7)
BSS11_3_4

Base Station System Control (BSSC) Cabinet Overview ISSUE 1 REVISION 2
Base Station System Control (BSSC) Cabinet Overview
Introduction
This chapter is a mechanical and electrical description of the base station system control
(BSSC) cabinet.
A BSSC cabinet can be configured as:
S A Base Station Controller (BSC) containing digital hardware modules configured to
control the radio subsystem.
S A Remote Transcoder (RXCDR) containing digital hardware modules configured to
provide an interface between the BSC and Mobile Switching Centre (MSC).
S A combination of the BSC and RXCDR functions.
The difference between the BSC and RXCDR configurations is in the complement of
digital modules on the backplane.
The information in this chapter applies to all three of the above configurations and, unless
otherwise indicated, to GSM, extended GSM (EGSM), DCS1800 and PCS1900 systems.
NOTE
The BSSC and BSSC2 cabinet are similar, the BSSC2 cabinet is described.
Where there are differences these are described in the text.
Cabinet types
The earlier BSSC cabinet is the same as the BSSC2 except in its handling of power
distribution and alarms.
The BSSC and BSSC2 cabinets can be powered by a positive earth (–48 V or –60 V) or
negative earth (+27 V) supply (this is requested by the customer and configured during
initial installation). The only difference in the cabinets is the inclusion of fan power
converters in the –48/–60 V versions of the BSSC to derive +27 V power for the cooling
fans.

ISSUE 1 REVISION 2 Base Station System Control (BSSC) Cabinet Overview
BSSC2 Cabinet – External View
Interconnect Panel
Intake Air V ents
Exhaust Air V ents
Door Hinges
Intake Air V ents
Exhaust Air V ents
BSS11_Ch3_05

Base Station System Control (BSSC) Cabinet Overview ISSUE 1 REVISION 2
Configuration
options
BSC configuration
The BSSC2 cabinet configured as a BSC contains at least one base station unit (BSU)
shelf assembly. This assembly is in the lower portion of the cabinet; the upper portion of
the cabinet can contain a second BSU configured either as a separate BSC or as an
expansion of the BSU on the lower shelf.
Transcoding can be performed at the BSC. In this case, the upper portion of the cabinet
contains a separate transcoder unit (RXU) shelf assembly instead of a second BSU.
The top shelf contains the power distribution unit (PDU) which consists of a distribution
alarm board and a dc circuit breaker panel.
RXCDR configuration
The BSSC2 cabinet configured as an RXCDR contains at least one RXU shelf assembly,
located in the lower portion of the cabinet. A second RXU can be located in the upper
portion of the cabinet. The top shelf contains the PDU, which consists of a distribution
alarm board and a dc circuit breaker panel.
BSU and RXU shelves

Each shelf in a cabinet can be configured as a separate network element.
The BSU and RXU shelf assemblies consist of:
S A backplane.
S Two vertical slot module shelves.
S A three compartment shelf.
The lower portion of the two vertical slot shelves holds 26 full size digital modules in slots
numbered L0 to L28. The upper portion of the shelf holds 28 half size digital modules in
slots numbered U0 to U28.
There are three compartments at the bottom of the BSU/RXU shelf assembly, with
slide-in mountings for power supply modules. The left compartment is for an optional
redundant power supply module.
External features
The cabinet door is hinged on the left side of the cabinet, and has four air vents with
grilles:
S Intake vents have air filters.
S Exhaust vents have exhaust fans fitted behind the vents.
All connections to the cabinet are at the interconnect panel, which is on top of the
cabinet. This panel also has feed-through tubes for routing fibre optic inter-cabinet
cables in and out of the cabinet. All cabinets are RF/EMI shielded.

ISSUE 1 REVISION 2 Base Station System Control (BSSC) Cabinet Overview
BSSC Cabinet – External View
Interconnect Panel
Intake Air V ents
Exhaust Air V ents
Door Hinges
Intake Air V ents
Exhaust Air V ents
BSS11_Ch3_05

BSSC Cabinet Internal Components ISSUE 1 REVISION 2
BSSC Cabinet Internal Components

The internal components of the BSSC cabinet include the following:
BSU / RXU Shelf

(up to two per
cabinet)
The function of these shelves is to house the main processing section of the BSC /
RXCDR. It is made up from several different sections:
S Half size modules
These cards are generally used for the shelf expansion / extension interfaces,
including interfaces for the LAN, data bus, synchronising clock.
S Full size cards
These cards run the main BSC / RXCDR software. These software processes
include the GSM call processing software, site control, operations and
maintenance etc. Also included amongst the full size cards are the switching
matrix and synchronising clock.
S Power Supply Modules
The PSMs convert the input voltage to the correct voltage for the shelf’s cards.
S Cooling Fans
These re-circulate the air across the processing cards and PSMs to maintain a
cool working temperature.
Power
Distribution
Board
This board provides protection in the form of circuit breakers for the shelves against
surges in the input voltage.
Distribution
Alarm Board
This board provides a method of the monitoring and reporting any alarms generated from
the BSSC cabinet

ISSUE 1 REVISION 2 BSSC Cabinet Internal Components
BSSC2 Internal View
Distribution Alarm Board (DAB)
Power Distribution Unit (PDU)
Half–size Digital Board Shelf
Full–size Digital Board Shelf Fans
Power Supply Modules
Half–Size Digital Board Shelf
Full–Size Digital Board Shelf
Power Supply Modules
Exterior Door Removed to Show Detail
BSS11_3_6

Interconnect panel ISSUE 1 REVISION 2
Interconnect panel
Location
The interconnect panel is on top of the cabinet.
Purpose
This panel provides connections for:
S DC input power.
S 2.048 Mbit/s line interconnect modules.
S Customer defined alarm equipment input and output.
S +27 V battery backup input for DRAM.
S +27 V power/alarm for external receiver multicoupler and external remotely
tuneable combiner (BTS only).
The interconnect panel has feed-through tubes for routing fibre optic intercabinet cables
into and out of the cabinet. Feed–through tubes do not compromise the cabinet’s EMC
screening, as the frequencies used are outside the waveguide cut off parameters.
The 2.048 Mbit/s line interconnection modules are:
S Type 43 interconnect boards (T43), used for unbalanced lines.
S Balanced-line interconnect boards (BIB), used for balanced lines.
Connectors
The table details the interconnect panel connectors for the BSSC2:
Connector Function Internal destination External destination
+27 V battery DRAM backup DAB connector PC4 and +27 V backup battery
backup battery BBBX connector PC2
MS0 to MS3 Multiple serial MS0 to MS3 connectors on E1/T1 circuits source
interface ports (up to lower BSU/RXU backplane or termination
six E1/T1 circuits at equi ment (via a T43
equipment
MS4 to MS7 each connector; six MS4 to MS7 connectors on or BIB)
Tx and six Rx upper BSU/RXU backplane
circuits)
PIX0 and PIX1 Customer alarm Front edge connector of PIX Customer alarm
input and output modules equipment
ports

ISSUE 1 REVISION 2 Interconnect panel
Interconnect Panel for BSSC2
Fibre optic cables

feed–through tube Fibre optic cables
MS4 MS5 MS6 MS7
feed–through tube
T43 T43 T43 T43

or or or or
BIB BIB BIB BIB Earth stud
+27 V battery
backup
PIX1 MS0 MS1 MS2 MS3
T43 VIN
PIX0 T43 T43 T43
+27 V DC
or or or or
BIB BIB BIB BIB
(+20 V to +30V)
OV
BSS11_Ch3_07

Distribution Alarm Board (DAB) ISSUE 1 REVISION 2
Distribution Alarm Board (DAB)
Purpose
The distribution alarm board (DAB):
S Distributes +27 V dc to units within the cabinet via 25 fuses.
S Monitors alarm lines.
S Passes individual alarms to the GPROC/GPROC2.
The DAB processes operational failure signals from:
S Ruptured fuses.
S The fan stall sense line from each cooling fan.
Two bi-coloured LEDs (D43 and D8) are mounted on the DAB to indicate both DAB and
cabinet-based faults. The other LEDs indicate fuse failures according to the tables in this
section. The DAB can be used in a BSSC2 cabinet.
Requirements
The DAB is fitted in the PDU shelf.
Switch settings
(BSSC2)
DAB switches S1 and S2 set the following configurations in the BSSC2:
Function Switch Position Setting

VSWR1 (Sector 1) S1 1 OFF
Spare S1 4 OFF
Battery backup O/P 2 S1 5 ON (OFF if fitted)
Battery backup O/P 1 S1 6 ON (OFF if fitted)
Battery backup I/P 2 S1 7 ON (OFF if fitted)
Battery backup I/P 1 S1 8 ON (OFF if fitted)
DRCU5 S2 1 OFF
DRCU2 S2 2 OFF
DRCU4 S2 3 OFF
DRCU1 S2 4 OFF
DRCU3 S2 5 OFF
DRCU0 S2 6 OFF
Spare S2 7 OFF
BBB ID S2 8 ON (if battery backup selected)

ISSUE 1 REVISION 2 Distribution Alarm Board (DAB)
DAB diagram
To backplane of Circuit breaker

cages (serial bus) monitor lines
F8 F9 F7 F4 F5 F6 F26 F21 F25 F22 F24 F23

LED LED OV
D43 D8
PC7
PC3
S2 LED LED LED LED LED LED LED LED LED LED LED LED
U4 D21 D23 D24 D27 D29 D31 D32 D33 D35 D37 D38 D41
PC4
PC5 PC6
LED LED LED LED LED LED LED LED LED LED
D22 D25 D26 D28 D30 F19 D34 D36 D39 D40 D42
PC2
S1
+27 V
F10 F11 F13 F12 F15 F14 F30 F29 F27 F28 F20 F18
BBBR for To backplane Power to fans Power to external

GPROC1 of cages (serial bus) equipment
BSS11_3_8.

Distribution Alarm Board (DAB) ISSUE 1 REVISION 2
Alarm functions
The DAB produces alarms for several different devices and modules:
S 25 fuses.
S Battery backup input and output alarms.
S Multicoupler.
S Six circuit breakers.
S Six fan alarms.
Each signal from the fuse alarms is at a nominal +27 V level and is brought to a TTL high
level. Under no-fault conditions, the TTL output is held at a high level. If one or more
fuses fail on the multicoupler fuse panel the TTL level is low.
The addressable asynchronous receiver/transmitter (AART) has eight status inputs,
which are multiplexed to obtain the required alarm functionality.
Visual warnings
Each +27 V (nominal) fuse protected branch circuit that powers cabinet equipment has a
corresponding LED indicator on the DAB. The LED lights if the fuse is ruptured by a fault
condition, and the associated alarm line goes low.
The DAB also provides visual warnings for alarms via two bi-coloured LEDs:
S D43 indicates any internal cabinet or multicoupler and combiner failure.
S D8 indicates a fuse failure on the DAB only.
Both LEDs are driven by the master GPROC/GPROC2 in response to alarms generated
by the DAB; red indicates an alarm, otherwise the LEDs remain green. If the master
GPROC/GPROC2 is not running then both LEDs default to red.
Communications
The DAB communicates with the master GPROC/GPROC2 via the serial bus link. The
master GPROC/GPROC2 always initiates connections, in which all modules respond
with status reports on the serial bus.
The DAB processes operational failure reports from the following:
S Ruptured fuses.
S Protected side of circuit breakers (except DPS circuit breakers, which are
monitored by the master GPROC/GPROC2 directly).
S Fan stall sense line from each cooling fan.
S Hardware failures reported directly to the DAB are individually sent to the master
GPROC/GPROC2 via the serial bus.
The serial bus circuitry is powered by the same +5 V that powers each digital card shelf.
The power supplies that provide this +5 V (as well as 12 V) deliver isolated outputs.
Thus all devices in the serial bus circuit have a return that is floating (digital) earth
relative to the cabinet (main) earth. However, many of the signals being alarmed are
referenced to cabinet earth.

ISSUE 1 REVISION 2 Distribution Alarm Board (DAB)
Fuses and LEDs

(BSSC2)
The table details the functions of the DAB fuses and LEDs used in the BSSC2:
Fuse Rating Power to LED

F4 0.5 A Not used D27
F12 4A Not used D28
F13 4A Not used D26
F14, F15 4A Not used D30
F18 2A Not used D42
F19 0.5 A DAB supply
F20 2A Not used D40
F21 2A Upper fan 5 D33
F24 2A Lower fan 2 D38
F27 2A Not used D36
F28 2A Not used D39

Power Distribution Unit (PDU) ISSUE 1 REVISION 2
Power Distribution Unit (PDU)
Overview
The power distribution unit (PDU) is located on the top shelf of the cabinet and:
S Distributes dc power throughout the cabinet.
S Provides an alarm interface.
It consists of a circuit breaker panel and one of the following:
S A distribution alarm board (DAB).
S A power alarm board (PAB).
S A power distribution board (PDB) with an alarm interface board (AIB).
Input power
DC input power is applied at the interconnection panel on top of the cabinet and is routed
to:
S The VIN bus bar.
S The earth (GND) bus bar in the PDU.
A second bus bar obtains +27 V power from:
S The power supply modules (PSMs) in the lower BSU or RXU in positive earth
(–48/–60 V) cabinets.
S The VIN and GND busbars via busbar links in negative earth (+27 V) cabinets.
Seven circuit breakers distribute power to units within the BSSC2 cabinet.
S CB1, at 30 A, provides +27 V power to the DAB.
S CB5 to CB10, at 60 A, provide power to the PSMs:
– In a positive earth cabinet, the circuit breakers supply –48/–60 V power to
the IPSMs.
– In a negative earth cabinet, the circuit breakers supply +27 V power to the
EPSMs.

ISSUE 1 REVISION 2 Power Distribution Unit (PDU)

BSSC2 Cabinet Cabling ISSUE 1 REVISION 2
BSSC2 Cabinet Cabling
Overview
This section contains the following cabinet cabling diagrams for a BSSC2 with a DAB
type PDU:
Diagram 1
BSSC2 cabinet (–48/–60 V) dc power and alarm cabling diagram (upper half).
Diagram 2
BSSC2 cabinet (–48/–60 V) dc power and alarm cabling diagram (lower half).
Diagram 3
BSSC2 cabinet (+27 V) dc power and alarm cabling diagram (upper half).
Diagram 4
BSSC2 cabinet (+27 V) dc power and alarm cabling diagram (lower half).

ISSUE 1 REVISION 2 BSSC2 Cabinet Cabling
Diagram 1 – BSSC2 cabinet (–48/–60 V) dc power and

alarm cabling (upper half)
INTERCONNECT PANEL OPT OPT
(TOP OF CABINET) FBR1 FBR0
MS4 MS5 MS6 MS7
BATT
PX1
PX0
BACKUP
ELCAP PANEL
MS0 MS1 MS2 MS3
VIN
0V
PDU FRAME
VIN BUS BAR
+27 V
BUS
BAR
PC7 0V DAB
PC3
PC5 GND
CB10
CIRCUIT 6 BUS
CB9
CB8
CB7
CB6
CB5
CB4
CB3
CB2
CB1
BREAKER PC4 BAR

PANEL (GBB)
PC2 PC6 GBB
+27V
PS28
PS18
PS28
PS18
PS8
PS8
AI0
UPPER
AI1 BSU/RXU BACKPLANE
AI2 MS0 MS1 MS2 MS3
BBBX
PC1
PC2
IPSM 2 –48/–60V IPSM 1 –48/–60V IPSM 0 –48/–60V
PS28 PS29 PS32 PS18 PS19 PS8 PS9
CHASSIS
GND
FAN 5 FAN 4 FAN 3

1 2 3 4 5 6
BSS11_Ch3_09

Diagram 2 (opposite)
BSSC2 cabinet (–48/–60 V) dc power and alarm cabling diagram (lower half).

Diagram 2 – BSSC2 cabinet (–48/–60 V) dc power and

alarm cabling (lower half)
1 2 3 4 5 6
AI0
LOWER
BSU/RXU BACKPLANE
AI1
AI2 MS4 MS5 MS6 MS7
BBBX
PC1
PC2
IPSM0 –48/–60
IPSM2 –48/–60 IPSM1 –48/–60 27 V OUT IPSM0 –48/–60V
PS29 PS28 PS32 PS19 PS18 PS51 PS50 PS9 PS8
CHASSIS
GND
FAN 2 FAN 1 FAN 0
BSS11_Ch3_10

Diagram 3 (opposite)
BSSC2 cabinet (+27 V) dc power and alarm cabling diagram (upper half).

Diagram 3 – BSSC2 cabinet (+27 V) dc power and alarm

cabling (upper half)
INTERCONNECT PANEL OPT OPT

(TOP OF CABINET) FBR1 FBR0
MS4 MS5 MS6 MS7
PX1
BATT
PX0
BACKUP
ELCAP PANEL
MS0 MS1 MS2 MS3
VIN
0V
PDU FRAME
VIN BUS BAR
+27 V PC7 0V
BUS DAB
BAR PC3
PC5 GND
6 BUS
PC4 BAR
(GBB)
CB10
CIRCUIT PC2 PC6

CB9
CB8
CB7
CB6
CB5
CB4
CB3
CB2
CB1
BREAKER GBB
PANEL +27V
PS28
PS18
PS28
PS18
PS8
PS8
AI0
BSU BACKPLANE
AI1
AI2 MS0 MS1 MS2 MS3
BBBX
PC1
PC2
EPSM2 +27V EPSM1 +27V EPSM0 +27V
CHASSIS
GND
FAN 5 FAN 4 FAN 3

1 2 3 4 5
BSS11_Ch3_11

Diagram 4
BSSC2 cabinet (+27 V) dc power and alarm cabling diagram (lower half).

Diagram 4 – BSSC2 cabinet (+27 V) dc power and alarm

cabling (lower half)
1 2 3 4 5
AI0

AI1
AI2 MS0 MS1 MS2 MS3
BBBX
PC1
PC2
EPSM2 +27V EPSM1 +27V EPSM0 +27V
CHASSIS
GND
FAN 2 FAN 1 FAN 0
BSS11_Ch3_12

Power supply modules ISSUE 1 REVISION 2
Power supply modules
Introduction
CAUTION
Ensure that the correct power supply module is fitted for the input used.
There are three compartments at the base of the BSU/RXU shelf assembly with slide-in
mountings for plug-in power supply modules (PSMs):
These cabinets ... Use this type of power supply ...

BSSC Digital power supply modules (DPSMs)
Positive earth BSSC2 Integrated power supply modules (IPSMs)
Negative earth BSSC2 Enhanced power supply modules (EPSMs)
The left compartment is for an optional redundant PSM. If the configuration of a particular
cabinet does not require a redundant PSM, a blanking plate is fitted over the
compartment. The redundant PSM must be compatible with the other cabinet power
units.
Cabinet power
requirements
The table shows the power requirements of the cabinet:
Supply Cabinet type

Earth Voltage BSSC2
Negative +27 V 90 A
Positive –48 V 50 A
–60 V 40 A

ISSUE 1 REVISION 2 Power supply modules

Integrated Power Supply Module (IPSM) ISSUE 1 REVISION 2
Integrated Power Supply Module (IPSM)
Overview
The Integrated Power Supply (IPS) system for each BSU or RXU in a positive earth
(–48 V/–60 V) system consists of up to three plug-in Integrated Power Supply Modules
(IPSMs). The IPSM can only be used in positive earth cabinets.
The IPSM is a switching type dc – dc power converter that converts the cabinet dc input
power to the following dc outputs:
S +27.5 V 5 % at 45 A (full-load current).
S +5 V 2 % at 87.5 A (full-load current).
S +12 V 5 % at 2.5 A (full-load current).
S –12 V 5 % at 2.5 A (full-load current).
The BSU or RXU backplane connects the outputs of each IPSM in parallel.
When three IPSMs are fitted in the IPS system, they load-share as follows:
S Two IPSMs provide sufficient power for a fully equipped BSU or RXU.
S The third IPSM provides n + 1 redundancy.
An IPSM in an alarm condition sends an alarm message to the GPROC/GPROC2 via the
serial bus.
Functional
description
Normal operation
During normal operation, the IPSMs equally share load current demand of the BSU or
RXU shelf modules:
S Half of the load current supplied by each IPSM in a two-IPSM system.
S One third of the load current supplied by each IPSM in a three-IPSM system.
Redundancy
Two IPSMs can provide adequate operating power for all modules in a BSU or RXU
shelf. A third IPSM can be added for redundancy.
When plugged into the backplane, all IPSM power outputs are connected in parallel, so
that the IPS system current capacity is twice that of the individual IPSM; any third IPSM
is redundant (n+1).
Power supply shutdown

During a shutdown condition caused by a faulty PSM, the output circuits of the
malfunctioning PSM are isolated from the backplane output line and the PSM alarm LED
is on. The malfunctioning PSM informs the GPROC/GPROC2 of the shutdown condition.

ISSUE 1 REVISION 2 Integrated Power Supply Module (IPSM)
View of the Integrated Power Supply Module (IPSM)
ACTIVE LED (GREEN) – ON WHEN

ALL OUTPUT VOLTAGES ARE
PRESENT AND WITHIN TOLERANCE
ALARM LED (RED) – ON WHEN ONE

OR MORE ALARM CONDITIONS
EXIST . OFF WHEN NO ALARM
CONDITION EXISTS.
25–PIN D–TYPE
CONNECTOR
(FEMALE) (REAR VIEW)
( 12V OUTPUT)
+27.5 V R TN
+27.5 V (OUTPUT)
+5 V C GND (CHASSIS GROUND)

+5 V V R TN (0 V INPUT)
RTN (GROUND FOR +5 V OUTPUT) V IN (–48 V/–60 V INPUT)
RTN (GROUND FOR +5 V OUTPUT)
BSS11_Ch3_15

Integrated Power Supply Module (IPSM) ISSUE 1 REVISION 2
Monitoring circuits
Parallel output connections allow each IPSM to sense its own output lines for:
S Output voltage regulation.
S Over-voltage protection to shut the IPSM down if the output voltage exceeds 1.2 to
1.3 times the rated output.
S Over-current protection to latch the power supply off (after a short delay for large
overloads) if the output current exceeds:
– 1.05 to 1.3 times the full-load rating of the +5 V output.
– 1.05 to 2 times the full-load rating of the +12 V and –12 V outputs.
The BSU or RXU shelf’s GPROC/GPROC2 monitors the status of each IPSM via a serial
alarm link on the backplane for:
S Loss of dc input voltage.
S Loss of output voltage.
S Overtemperature.
S Loss of serial link.
Circuit protection
Additional internal IPSM circuit protection includes:
S Input dc reverse polarity protection to prevent IPSM damage using an input series
diode that blocks reverse voltages.
S Thermal protection to send an alarm message to the GPROC/GPROC2 via the
serial port, then shut the IPSM down, if the IPSM ambient temperature exceeds a
safe level.
After an alarm condition has ceased, normal IPSM operation is automatically restored.
Serial link
The serial link carries the following information and flags an alarm if an unexpected state
or failure occurs:
Address Device location Revision IPSM Alarms
Slot 0 – 2 I/P Fail

O/P Fail
Overtemp
LED display
Two LEDs are mounted on the front of the IPSM to indicate the following:
S Active (Green): on when all output voltages are present and within specified limits.
S Alarm (Red): on when one or more alarm conditions exist.

ISSUE 1 REVISION 2 Integrated Power Supply Module (IPSM)
Functional Block Diagram of the IPSM
BACKPLANE CONNECTOR
VOUT (+5 V)
VOUT (+12 V)
VOUT (–12 V)
VOUT (+27.5 V)
GREEN POWER
LED CONVERTER
AND
RED SYSTEM
LED MONITOR INPUT FAIL
SERIAL LINK
OUTPUT FAIL
OVERTEMPERATURE
VIN (–48 V/–60 V)
BSS11_Ch3_16

Enhanced Power Supply Module (EPSM) ISSUE 1 REVISION 2
Enhanced Power Supply Module (EPSM)
Overview
The Enhanced Power Supply (EPS) system for each BSU in a negative earth (+27 V)
system consists of up to three plug-in Enhanced Power Supply Modules (EPSMs). The
EPSM can only be used in a negative earth cabinet.
The EPSM is a switching type dc - dc power converter that converts the cabinet dc input
S +5 V ( 2% at 85.5 A).
S 12 V ( 5% at 2.5 A).
The BSU or RXU backplane connects the outputs of each EPSM in parallel.
When three EPSMs are fitted in the EPS system, they load-share as follows:
S Two EPSMs provide sufficient power for a fully equipped BSU or RXU.
S The third EPSM (if fitted) provides n+1 redundancy.
An EPSM in an alarm condition sends an alarm message to the GPROC/GPROC2 via
the serial bus.
Functional
description
Normal operation
During normal operation, the EPSMs share the load current demand of the BSU or RXU
shelf modules:
S Half of the load current supplied by each EPSM in a two-EPSM system.
S One third of the load current supplied by each EPSM in a three-EPSM system.
Regulated dc power is applied to the backplane to power the BSU or RXU shelf modules.
Redundancy
Two Enhanced Power Supply Modules (EPSMs) can provide adequate operating power
for all modules in a BSU or RXU shelf. A third EPSM can be added for redundancy.
When plugged into the backplane, all EPSM power outputs are connected in parallel, so
that the EPS system current capacity is twice that of the individual EPSM; any third
EPSM is redundant (n+1).

During a shutdown condition caused by a faulty EPSM, the output circuits of the
malfunctioning EPSM are isolated from the backplane output line, and the EPSM alarm
LED is switched on. The malfunctioning EPSM informs the GPROC/GPROC2 of the
shutdown condition.

ISSUE 1 REVISION 2 Enhanced Power Supply Module (EPSM)
View of the Enhanced Power Supply Module (EPSM)
ACTIVE LED (GREEN) – ON WHEN ALL

OUTPUT VOLTAGES ARE PRESENT
AND WITHIN TOLERANCE.
ALARM LED (RED) – ON

WHEN 1 OR MORE ALARM
CONDITIONS EXIST. OFF
WHEN NO ALARM CONDITION
EXISTS.
25-PIN D-TYPE
CONNECTOR (REAR VIEW)
(FEMALE)
( 12V OUTPUT)
+5 V C GND (CHAS SIS GROUND)

+5 V V RTN (0 V INPUT)
RTN (GROUND FOR +5 V OUTPUT) V IN (+27 V INPUT)
RTN (GROUND FOR +5 V OUTPUT)
BSS11_Ch3_17

Enhanced Power Supply Module (EPSM) ISSUE 1 REVISION 2
Monitoring circuits
Parallel output connections allow each EPSM to sense its own output lines for:
S Over-voltage protection to shut the EPSM down if the output voltage exceeds 1.2
to 1.3 times the rated output.
– 1.15 to 1.5 times the full-load rating of the +5 V output.
– 1.15 to 2 times the full-load rating of the +12 V and –12 V outputs.
The BSU or RXU shelf’s GPROC/GPROC2 also monitors the status of each EPSM, via a
serial alarm link on the backplane, for:
S Overtemperature.
Circuit protection
Additional internal EPSM circuit protection includes:
S Input dc reverse polarity protection to prevent EPSM damage using an input series
diode to block reverse voltages.
S Thermal protection to send an alarm message to the GPROC/GPROC2 via the
serial port, and shut the EPSM down, if the EPSM ambient temperature exceeds a
safe level.
After an alarm condition has ceased, normal EPSM operation is automatically restored.
Serial link
The serial link carries the following information and flags an alarm if an unexpected state
or failure occurs:
Address Device location Revision EPSM Alarms
I/P Fail
Slot 0 – 2 O/P Fail
Overtemp
LED display
Two LEDs are mounted on the front of the EPSM to indicate the following:

ISSUE 1 REVISION 2 Enhanced Power Supply Module (EPSM)
Functional Block Diagram of the EPSM
BACKPLANE CONNECTOR
VOUT (+5 V)
VOUT (+12 V)
VOUT (–12 V)
GREEN POWER
LED CONVERTER
AND
RED SYSTEM
SERIAL LINK
OUTPUT FAIL
OVERTEMPERATURE
VIN (+27 V)
BSS11_Ch3_18

Shelf Internal Connections Overview ISSUE 1 REVISION 2
Shelf Internal Connections Overview

To process all the data required to make and maintain the call, each software process
and therefore digital card must be able to communicate which each other and to any
external entities such as the MSC or BTS. Each card has one or more connections to
one or more data buses to co-ordinate this data transfer. Each bus has differing functions
and can be summarised below:
Time Division
Multiplexed
(TDM) highway
This bus is used to pass call and signalling data from the BTS to the MSC and vice
versa. The TDM highway is split into two separate sections :
S Switchbound highway – Handles data routed towards the switch. Data is either
from an external source (via the E1/T1 interfaces) or is generated by the GPROCs
internally.
S Outbound highway – This is data that has been switched and is now being
routed out of the BSC/RXCDR (via the E1/T1 interfaces) or towards the internal
GPROCs.
The cards connected to the TDM highways are:
S GPROCs – Send and receive control data to/from external entities such as the
MSC (MTL) , BTS (RSL) , RXCDR (XBL), OMC (OML) and CBC (CBL).
S E1/T1 interfaces – MSI / XCDR / GDP boards. These cards interface the E1/T1
links to the TDM highway to make sure the data incoming an out going is in the
correct format.
S KSW – This board takes the data in from the Switchbound highway and switches it
to the correct section on the Outbound highway.
S Bus Terminator Card (BTC) – The Bus Terminator Card (BTC) provides the
terminations necessary for all of the signals on the BSU backplane and is required
due to the high speed buses contained in the backplanes. Two BTC cards are
required in each cage, one at each end, in order to guarantee the proper
termination characteristics. The maximum/minimum BTC in the BSU/RXU is two.
Motorola Cellular
Advanced
Processor
(MCAP) bus
The MCAP bus provides the GPROCs within the shelf to monitor and control all the other
full size cards, except other GPROCs.
Local Area
Network (LAN)
The LAN allows all GPROCs to communicate to each other via a dedicated high-speed
bus.
Serial bus
Interfaces the DAB, PSMs and the Half size cards to the GPROCs for control and
monitoring purposes.

ISSUE 1 REVISION 2 Shelf Internal Connections Overview
Shelf Interconnections Overview
Links to MSC or BTS

External Alarms To other cages
at the site
To 2nd Cage
for expansion
of KSW T43 / BIB
KSWX
EXP
PIX
DAB/PSMs
CLKX
LAN Half size cards
LANX
Serial Bus
GCLK
XCDR
GDP
GPROC
GPROC
MSI
KSW
Remote TDM Outbound

Highway
KSWX
RMT
Remote TDM Switchbound

Highway
To 2nd Cage for MCAP BUS

Extension TDM
Highway
BSS11_Ch3_20

Base Station Unit (BSU) Shelf ISSUE 1 REVISION 2
Base Station Unit (BSU) Shelf
Base Station Unit

Shelf Assembly
A Base Station Unit (BSU) shelf assembly consists of:
S A backplane.
S Two vertical-slot module shelves containing the required digital modules:
– The upper shelf holds half size digital modules.
– The lower shelf holds full size digital modules.
S A three-compartment shelf for the power supply modules.
Every cabinet must be fitted with the following digital cards:
S Two Bus Termination Cards (BTC).
S One Local Area Network Extender (LANX) module.
All other digital modules are optional, and their inclusion depends upon the cabinet
configuration.
Base Station Unit

(BSU)
Max number of full size boards – contained within in BSU.
2 x Kiloport Switch (KSW)
12 x Multiport Serial Interface (MSI)
2 x Generic Clock (GCLK)
8 x Generic Processor (GPROC)
6 x Full–Rate Transcoder (XCDR)
6 x Generic DSP Processor (GDP)
2 x Bus Terminator Card (BTC)
Max number of half size boards – contained within in BSU.
18 x Kiloport Switch Extender (KSWX)
6 x Clock Extender (CLKX)
2 x Local Area Network Extender (LANX)
2 x Parallel Interface Extender (PIX)
3 x Battery Backup Board (BBBX)

ISSUE 1 REVISION 2 Base Station Unit (BSU) Shelf
BSU shelf diagrams
BSU shelf
The diagram shows the BSU shelf slot assignment and backplane connectors:
AI0 KS0 DR5 DR4 DR3 DR2 DR1 DR0 KS1

AI1
MS0 MS1 MS2 MS3 GK0
ÏÏ
ÏÏÏÏ
AI2
ÏÏ
ÏÏÏÏ
CLKX A1 RMT KSWX B0
CLKX A2 RMT KSWX B1
CLKX B0 RMT KSWX B2
CLKX B1 RMT KSWX B3
CLKX B2 RMT KSWX B4

EXP KSWX B0
EXP KSWX B1
CLKX A0 EXP KSWX B2
LCL KSWX A
LCL KSWX B
ÏÏ
ÏÏÏÏ
KSWX A4
KSWX A3
KSWX A2
KSWX A1
KSWX A0
KSWX A2
KSWX A1
KSWX A0
ÏÏ
ÏÏÏÏ
LANX B
LANX A
SPARE
SPARE
DRIX 4
DRIX 3
DRIX 2
DRIX 1
DRIX 0
PIX 0
PIX 1
ÏÏ
ÏÏÏÏ
RMT
RMT
RMT
RMT
RMT
EXP
EXP
EXP
ÏÏ
ÏÏÏÏ
ÏÏ
U28 U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1 U0
ÏÏ
ÏÏ
MSI 10
MSI 11
MSI 6
MSI 0
MSI 1
MSI 2
MSI 3
MSI 4
MSI 5
MSI 7
MSI 8
MSI 9
ÏÏ
ÏÏ
DRI(M) 0 XCDR/GDP 10
XCDR/GDP 11
DRI(M) 2 XCDR/GDP 6
XCDR/GDP 0
XCDR/GDP 1
DRI(M) 4 XCDR/GDP 2
XCDR/GDP 3
DRI(M) 3 XCDR/GDP 4
XCDR/GDP 5
XCDR/GDP 7
DRI(M) 1 XCDR/GDP 8
XCDR/GDP 9
KSW/TSW B
GPROC 6
KSW/TSW A
GPROC 7
GPROC 5
GPROC 4
GPROC 3
GPROC 2
GPROC 1
GPROC 0
GCLK B
GCLK A
ÏÏ
BTC 0
BTC 1
spare
ÏÏ
ÏÏ
ÏÏ
L28 L27 L26
ÏÏ L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5 L3 L1 L0
BSU backplane connectors

S AI0 and AI1 are 10-pin headers.
S AI2 is a 4-pin power connector to the backup supply (BBBX).
S KS0 and KS1 are 20-pin headers and provide TTY access to serial ports for
KSW/TSW boards.
S DR0 to DR5 are 20-pin headers and provide TTY access to serial ports for
DRI/MSI boards.
S GK0 is a 9-pin D-type and provides a GCLK synchronization input.
S MS0 to MS3 are 37-pin D-types for connecting E1/T1 circuits.

Remote Transcoder Unit (RXU) Shelf ISSUE 1 REVISION 2
Remote Transcoder Unit (RXU) Shelf
Remote
Transcoder Unit
Shelf Assembly
A Remote Transcoder Unit (RXU) shelf assembly consists of:
S A backplane.
S Two vertical-slot module shelves containing the required digital modules:
– The upper shelf holds half size digital modules.
– The lower shelf holds full size digital modules.
S A three-compartment shelf for the power supply modules.
Every cabinet must be fitted with:
S Two Bus Termination Cards (BTC).
S One Local Area Network eXtender (LANX) module.
All other digital modules are optional, and their inclusion depends upon the cabinet
configuration.
Remote
Transcoder Unit
(RXU)
Max number of full-size boards – contained within the RXU.
2 x Kiloport Switch (KSW)
6 x Multiport Serial Interface (MSI)
2 x Generic Clock (GCLK)
2 x Generic Processor (GPROC)
16 x Full–rate Transcoder (XCDR)
16 x Generic DSP Processor (GDP)
2 x Bus Terminator Card (BTC)
Max number of half–size boards – contained within the RXU.
18 x Kiloport Switch Extender (KSWX)
6 x Clock Extender (CLKX)
2 x Local Area Network Extender (LANX)
2 x Parallel Interface Extender (PIX)
3 x Battery Backup Board (BBBX)

ISSUE 1 REVISION 2 Remote Transcoder Unit (RXU) Shelf
RXU Shelf
AI0 KS0 KS1
ÏÏ
ÏÏ
AI1 MS0 MS1 MS2 MS3
AI2
ÏÏ
ÏÏ
CLKX A1 RMT KSWX B0
CLKX A2 RMT KSWX B1
CLKX B0 RMT KSWX B2
CLKX B1 RMT KSWX B3
CLKX B2 RMT KSWX B4

EXP KSWX B0
EXP KSWX B1
CLKX A0 EXP KSWX B2

ÏÏ
ÏÏ
LCL KSWX A
LCL KSWX B
KSWX A4
KSWX A3
KSWX A2
KSWX A1
KSWX A0
KSWX A2
KSWX A1
KSWX A0
ÏÏ
ÏÏ
LANX B
LANX A
SPARE
SPARE
PIX 0
ÏÏ
ÏÏ PIX 1
RMT
RMT
RMT
RMT
RMT
ÏÏ
ÏÏ
EXP
EXP
EXP
U28
ÏÏ
U27 U26 U25 U24 U23 U22 U21 U20 U19 U18 U17 U16 U15 U14 U13 U12 U11 U10 U9 U8 U7 U6 U5 U4 U3 U2 U1 U0
ÏÏ
ÏÏ
MSI 0
MSI 1
MSI 2
MSI 3
MSI 4
ÏÏ
ÏÏ
XCDR/GDP 16
XCDR/GDP 10
XCDR/GDP 11
XCDR/GDP 13
XCDR/GDP 14
XCDR/GDP 15
XCDR/GDP 17
XCDR/GDP 18
KSW B / TSW B
KSW A / TSW A
XCDR/GDP 12
XCDR/GDP 6
XCDR/GDP 0
XCDR/GDP 1
XCDR/GDP 2
XCDR/GDP 3
XCDR/GDP 4
XCDR/GDP 5
XCDR/GDP 7
XCDR/GDP 8
XCDR/GDP 9
GPROC 1
GPROC 0
ÏÏ
GCLK B
GCLK A
BTC 0
BTC 1
ÏÏ
ÏÏ
ÏÏ
L28 L27 ÏÏ L26 L25 L24 L23 L22 L21 L20 L19 L18 L17 L16 L15 L14 L13 L12 L11 L10 L9 L8 L7 L6 L5 L3 L1 L0
S AI0 and AI1 are 10-pin headers.

S AI2 is a 4-pin power connector to the backup supply (BBBX).
S KS0 and KS1 provide TTY access to serial ports for KSWs/TSWs.
S MS0 to MS3 are 37-pin D-types for connecting E1/T1 lines.

Bus Termination Card (BTC) ISSUE 1 REVISION 2
Bus Termination Card (BTC)
Purpose
The Bus Termination Card (BTC) terminates the backplane to keep signals on a BSU or
RXU shelf at the proper TTL level.
The BTC terminates:
S Both MCAP buses.
S Both BSS serial buses.
S Both reference clocks.
S All TDM buses (Expansion, Remote and Local).
Requirements
Two BTC modules must be fitted in each BSU or RXU shelf, in slot L0 and slot L28, at all
times.
While a faulty BTC is being replaced, another BTC must be fitted in a KSW slot to
maintain the above requirement.

ISSUE 1 REVISION 2 Bus Termination Card (BTC)
The Bus Termination Card (BTC) Module
BACKPLANE
CONNECTOR
BSS11_Ch3_23

The Generic Processor (GPROC) Board ISSUE 1 REVISION 2
The Generic Processor (GPROC) Board

The Generic Processor (GPROC) module provides the processing power to control a
BSC, RXCDR or BTS.
GPROCs in a BSU or RXU exchange control signalling via several links:
S A token ring Local Area Network (LAN). The LAN can link processors in several
shelves via fibre optic cable.
S A Motorola Cellular Advanced Processor (MCAP) bus, which extends the
processor’s address, data and control buses to peripheral modules in the same
shelf.
S A serial bus, which communicates alarm information between GPROCs and
half-size modules. This serial bus extends to the PDU.
S The active Time Division Multiplex (TDM) highway.
The GPROC module fits into:
S Slots L18 to L25 in a BSU shelf assembly.
S Slot L25 and slot L26 in an RXU shelf assembly.
Each BSU/RXU requires at least one GPROC.
A GPROC must be fitted in slot L20 of BSU 0, and slot L24 of RXU 0, for use in
initialization.

ISSUE 1 REVISION 2 The Generic Processor (GPROC) Board
The Generic Processor (GPROC) Module
Alarm (red) LED

(normally off)
Backplane connector
active (Green) LED

(normally on)
Green LED on, red LED off =
processer running, no failures
Green LED off, red LED on =

processor halted, or in reset
Both LEDS on = processor

running, module is disabled or
other alarm
TTY Connector
Reset/disable switch up
(momentary) = reset
Middle = normal operaton (This optically isolated test port
Down = disable allows control of troubleshooting
and diagnostics.)
BSS11_Ch3_24

GPROC module
The GPROC module contains:
S A Motorola MC68030 16-bit processor operating at 25 MHz.
S The LAN processor, which is the interface between the GPROC and the token ring
LAN.
S The LAPD processor which, in conjunction with the TDM interface controller, is the
interface between the GPROC and the TDM highway.
The GPROC communicates with other full-size modules via the MCAP bus, and with
half-size modules (and modules not on the module shelf) via the BSS serial bus. There
are two other serial ports which are not currently used.
The LAPD processor and the TDM interface controller communicate via a high-speed
private bus. The private bus arbiter is the interface between the MC68030 address/data
bus and the high-speed private bus.
The parallel port controls output signals to the front panel LEDs, and receives input
signals (via the register ports) from the backplane. These contain:
S Shelf ID.
S Slot ID.
S Backplane type.
S Backplane revision level.
The GPROC module is equipped with 16 Mbytes of DRAM. There is also 512 kbytes of
EPROM (expandable to 1 Mbyte). The EPROM contains the bootstrap code.
A fully buffered TTY maintenance port is available on the front panel, to which a Personal
Computer (PC) can be connected. The TTY can be used for monitoring and controlling
software when performing maintenance or troubleshooting.
The maintenance port meets the requirements of the EIA RS232C and CCITT V.24
specifications.
The GPROC runs on-board self-diagnostics during initial power-up and on command
from the maintenance TTY.
Every GPROC is identical in terms of hardware; its function depends upon the software
loaded into it.
The processor functions for BTS and BSC applications are different from those for an
RXCDR application and are described separately in the following sections.

Functional Block Diagram of the GPROC
BACKPLANE CONNECTOR
BACKPLANE INFORMATION
REGISTER TO DRAM +5 V BATTERY

PORTS
BOARD DISTRIBUTION +5 V
ADDRESS/DATA BUS 52
MCAP BUS MCAP BUS A
INTERFACE
LOGIC
52
MCAP Bus B
} 2REDUNDANCY
FOR
RED LED PARALLEL

GREEN LED PORT
PRIVATE BUS
LAPD
PROCESSOR
PRIVATE BUS
PROCESSOR ARBITER 9
OUTBOUND TDM HWY A
MC68030
TDM 9
OUTBOUND TDM HWY B
} 2REDUNDANCY
FOR
INTERFACE 9
CONTROLLER SWITCHBOUND TDM HWY A
SYSTEM TIMING
9
SWITCHBOUND TDM HWY B
}
RESET/ WATCHDOG CONTROLLER
DISABLE TIMER PRIVATE BUS
(STC)
SWITCH
COUNTER/ REFERENCE CLKS (125 us, 60 ms,
TIMERs 6.12 s AND 16.384 MHz A & B)
MEMORY ARRAY 4
DRAM (16M BYTE ) TOKEN RING LAN A
TOKEN RING 1
EPROM (512 KBYTE TO 1 MBYTE) LAN LAN TOKEN RING CONTROL
(BOOTSTRAP CODE STORAGE) PROCESSOR INTERFACE 4 TOKEN RING LAN B
OR
FLASH EPROM (256 KBYTE TO 1 MBYTE)
REPROGRAMMABLE BOOTSTRAP CODE
STORAGE)
2
DRAM WITH BATTERY BACKUP LOGIC SERIAL LINE 1
NVRAM NON–VOLATILE RAM (32k bytes)
SERIAL
INTERFACE 2
SERIAL LINE 2
} NOT
USED
CURRENTLY
BUFFERED 2
TEST PORT RS232 OPTO– BSS SERIAL BUS A
25 PIN “D”
DRIVER ISOLATOR SERIAL
INTERFACE
SERIAL
BUS
2 BSS SERIAL BUS B } 2REDUNDANCY
FOR
CONNECTOR CONTROL 1 SERIAL A/B SELECT
GND
BSS11_Ch3_25

BTS and BSC

GPROC
functions
The GPROC performs the following processor functions:
S Fault Manager (FM).
S Configuration Manager (CM).
S Message Transfer Protocol (MTP).
S Signalling Connection Control Part (SCCP) State Machine (SSM).
S Radio Resource State Machine (RRSM).
S Cell Resource Machine (CRM).
S Switch Manager (SM).
S Connectionless Manager (CLM).
S Radio Subsystem (RSS).
S Operations and Maintenance System (OMS).
S Maintains a copy of the application code for collocated peripheral modules.

GPROC Device Table
GPROC device BSC BTS BSC/BTS

task groups task groups interface
Type 0 Base Site Control Base Transceiver Motorola
Processor (BSP) Processor (BTP) proprietary
Type1 Base Site Control Base Transceiver Motorola
Link Control Digital Radio Host
Function (LCF) Processor (DHP)
Operations and Radio System Link
Maintenance Processor (RSLP)
Processor (OMP)
NOTE
A code storage facility processor (CSFP) can also be equipped.
BSS11_Ch3_26

RXCDR GPROC
functions
The RXCDR GPROC processor functions are similar to the BSC and BTS GPROCs and
comprise:
These processor functions:
S Maintain the switch database for the KSWs and TSWs.
S Maintain a copy of the application code for collocated peripheral modules.
S Initialise the RXCDR network element.
S Maintain the configuration database.
S Communicate with other network elements via a 64 kbit/s LAPD serial data link.
S Communicate with the OMC via an X.25 link.
S Communicate with the local monitor via a man-machine interface (MMI).
S Communicate with collocated digital modules.
S Handle redundancy between duplicated modules.
S Control operational software downloads to digital highway modules such as MSIs,
KSWs, and XCDRs.
Fault manager
The RXCDR FM communicates with the BSS FM function via the optional Transcoder
BSC Link (XBL), a dedicated 64 kbit/s channel.
Switch manager
The SM:
S Makes connections between the terrestrial links on the A interface (MSC to BSS)
and the radio (traffic) channels on the air interface.
S Interacts with the call processing and fault management functions.
S Provides switching functionality for the BSS distributed within the BSC and BTS.
Configuration manager
The CM maintains and updates a configuration database which contains all parameters
and operational software currently in use.
Changes to the database are restricted to the highest level password protection, due to
the potential for down time caused by incorrect changes to the configuration database.


The Generic Processor (GPROC2) ISSUE 1 REVISION 2
The Generic Processor (GPROC2)
Purpose
The Generic Processor (GPROC2) module provides the processing power to control a
BSC, RXCDR or BTS. The GPROC2 cannot be used with software version less then
1500.
GPROC2s in a BSU or RXU exchange control signalling in several ways:
S A token ring Local Area Network (LAN). The LAN can link processors in several
shelves via fibre optic cable.
processor address, data and control buses to peripheral modules in the same
shelf.
S A serial bus, which communicates alarm information between GPROC2s and
half-size modules. This serial bus extends to the power distribution unit.
Requirements
The GPROC2 module fits into:
S Slots L18 to L25 in a BSU shelf assembly.
S Slot L25 and slot L26 in an RXU shelf assembly.
Each BSU/RXU requires at least one GPROC2.
A GPROC must be fitted in slot L20 or L24 in a BSC.
Brief description
The GPROC2 module contains:
S The LAN processors, which are the interface between the GPROC2 and the token
ring LAN.
S The COMM processor which, in conjunction with the TDM interface controller, is
the interface between the GPROC2 and the TDM highway.

ISSUE 1 REVISION 2 The Generic Processor (GPROC2)
The GPROC2 Module
ALARM (RED) LED

(NORMALLY OFF) BACKPLANE CONNECTOR
ACTIVE (GREEN) LED
(NORMALLY ON)
GREEN LED ON, RED LED OFF =
PROCESSOR RUNNING, NO FAILURES
GREEN LED OFF, RED LIGHT ON =
PROCESSOR HALTED, OR IN RESET
BOTH LEDS ON = PROCESSOR
RUNNING, MODULE IS DISABLED
OR OTHER ALARM
RESET/DISABLE SWITCH TTY CONNECTOR

UP (MOMENTARY) = RESET
MIDDLE = NORMAL OPERATION
(THIS OPTICALLY ISOLATED TEST
DOWN = DISABLE
PORT ALLOWS CONTROL OF
TROUBLESHOOTING AND
DIAGNOSTICS).
BSS11_Ch3_27

Communication
The GPROC2 communicates with other full-size modules via the MCAP bus, and with
half-size modules (and modules not on the module shelf) via the BSS serial bus.
S Shelf ID.
S Slot ID.
S Backplane type.
Memory
The GPROC2 module is equipped with 32 Mbytes of DRAM. There is also 1Mbyte of
EPROM. The EPROM contains the bootstrap code.
Troubleshooting
and diagnostics
A fully buffered TTY maintenance port is available on the front panel, to which a Personal
Computer (PC) can be connected. The TTY can be used for monitoring and controlling
software when performing maintenance or troubleshooting.
The maintenance port meets the requirements of the EIA RS232C and ITU–TSS V.24
specifications.
The GPROC2 runs on-board self-diagnostics during initial power-up and on command
from the maintenance TTY connection.
Software
Every GPROC2 is identical in terms of hardware; its function depends upon the software
loaded into it.
The processor functions for BTS and BSC applications are different from those for an
RXCDR application and are described separately in the following sections.

Block Diagram of the GPROC2
BACKPLANE CONNECTOR
LAN A
DRAM
RESET/ WATCHDOG TIMING LAPD
DISABLE TIMERS CONTROL PROC
SWITCH
BUS LAN A
SIZER PROC
LAN LAN A
INTERFACE
LAN B
LAN
PROCESSOR BUS
MC68040
33 MHz LAN B
PROC
DATA/ADDRESS LAN B
BUS DRAM
EXT CACHE
TDM TDM A
128 K
INTERFACE TDM B
PERIPHERAL
BUS
MAIN DRAM
(16 – 64 Mb)
EEPROM
NVRAM MCAP MCAP A
INTERFACE
MCAP A
SERIAL BUS SERIAL BUS A

TTY TEST
CONNECTOR CONTROLLER SERIAL BUS B

BTS and BSC

GPROC2
functions
The GPROC2 performs the following processor functions:
S Message Transfer Protocol (MTP).
S Signalling Connection Control Part (SCCP) State Machine (SSM).
S Cell Resource Machine (CRM).
S Connectionless Manager (CLM).
S Operations and Maintenance System (OMS).
S Maintains a copy of the application code for collocated peripheral modules.
GPROC2 task
groups and
device types
The processor functions can be grouped into six task groups depending on the software
loaded into a given GPROC2.
When a group of tasks is assigned to a GPROC2, it is considered to be a unique
GPROC2 device type. The exception to this is the Code Storage Facility Processor
(CSFP), which is not considered to be a unique device type.
The table shows the device types and task groups:

GPROC2 Device Types and Task Groups
GPROC device BSC BTS BSC/BTS

task groups task groups interface
Type1 Base Site Control Base Transceiver Motorola
Operations and Radio System Link
Maintenance Processor (RSLP)
Processor (OMP)
NOTE
A Code Storage Facility Processor (CSFP) can also be equipped.
BSS11_Ch3_29

RXCDR GPROC2
functions
The RXCDR GPROC2 processor functions are similar to the BSC and BTS GPROC2s
and comprise:
These processor functions:
S Maintain the switch database for the KSWs and TSWs.
S Maintain a copy of the application code for collocated peripheral modules.
S Initialize the RXCDR network element.
S Maintain the configuration database.
S Communicate with other network elements via a 64 kbit/s LAPD serial data link.
S Communicate with the OMC via an X.25 link.
S Communicate with the local monitor via a man-machine interface (MMI).
S Communicate with collocated digital modules.
S Handle redundancy between duplicated modules.
S Control operational software downloads to digital highway modules such as MSIs,
KSWs, and XCDRs.
Fault manager
The RXCDR FM communicates with the BSS FM function via the optional Transcoder
BSC Link (XBL), a dedicated 64 kbit/s channel.
Switch manager
The SM:
S Makes connections between the terrestrial links on the A interface (MSC to BSS)
and the radio (traffic) channels on the air interface.
S Interacts with the call processing and fault management functions.
S Provides switching functionality for the BSS distributed within the BSC and BTS.
Configuration manager
The CM maintains and updates a configuration database which contains all parameters
and operational software currently in use.
Changes to the database are restricted to the highest level password protection, due to
the potential for down time caused by incorrect changes to the configuration database.


Type 43 interconnect board ISSUE 1 REVISION 2
Type 43 interconnect board
Location
Plugs into the interconnect panel via a 37-pin D-type connector.
Purpose
The T43 interconnect board matches the impedance between the Pulse Code Modulation
(PCM) circuit lines and the BSU/RXU backplanes. The board interfaces up to six input
and six output unbalanced coaxial 75 ohm 2.048 Mbit/s lines to the external PCM circuit
lines through twelve type 43 coaxial connectors.
The T43 uses 12 transformers to provide impedance matching between the PCM circuit
lines and the Multiple Serial Interface (MSI) modules. Each transformer has a 1:1.25
turns ratio to match the external 75 ohm and backplane 120 ohm connections. Each
input and output is isolated from the backplane by up to 1500 V.
NOTE
Use the T43 for unbalanced lines.

ISSUE 1 REVISION 2 Type 43 interconnect board
The T43 Interconnect Board
J0
J8 J4
J14 J10
J16 J2
J13 J11
J7 J1
J17 J5
BSS11_Ch3_30

T43 connectors
The table details the T43 connectors:
D–Type
yp Function Coaxial D–Type
yp Function Coaxial
Pin no. Pin no. Pin no. Pin no.
J0-1 MSI_MEGA_Tx1+ J1 Centre J0-20 MSI_MEGA_Tx1– J1 Shield
(AC coupled to ground)
J0-2 MSI_MEGA_Rx1+ J2 Centre J0-21 MSI_MEGA_Rx1– J2 Shield
(Ground)
(Ground)
(Ground)
(Ground)
(Ground)
(Ground)
Connector J0 pins 3, 6, 9, 12, 15, 18, 19, 22, 25, 28, 31, 34, and 37 are not used


Balanced-line Interconnect Board (BIB) ISSUE 1 REVISION 2
Balanced-line Interconnect Board (BIB)
Location
Plugs into the interconnect board via two 37-pin D-type connectors.
Purpose
The Balanced-line Interconnect Board (BIB) matches the impedance between the Pulse
Code Modulation (PCM) circuit lines and the BSU backplanes. The board provides
interfaces for six input and six output balanced 120 ohm E1/T1 lines.
The board uses 12 transformers to match the impedance between the PCM circuit lines
and the Multiple Serial Interface (MSI) modules. Each transformer has a 1:1 turns ratio to
match the external and backplane 120 ohm connections.
NOTE
Use the BIB for balanced lines.

ISSUE 1 REVISION 2 Balanced-line Interconnect Board (BIB)
The Balanced-line Interconnect Board (BIB)
J1
J0
BSS11_Ch3_31

Balanced-line Interconnect Board (BIB) ISSUE 1 REVISION 2
BIB connectors
The table details the BIB connectors:
Pin no. Function Pin no. Pin no. Function Pin no.
J0–1 MSI_MEGA/EXT_MEGA J1–1 J0–20 MSI_MEGA/EXT_MEGA J1–20
_Tx1+ _Tx1–
_Rx1+ _Rx1–
J0–3 Ground J1–3 J0–22 Ground J1–22
_Tx4+ _Tx4–
_Rx4+ _Rx4–
_Tx2+ _Tx2–
_Rx2+ _Rx2–
_Tx5+ _Tx5–
_Rx5+ _Rx5–
_Tx3+ _Tx3–
_Rx3+ _Rx3–
_Tx6+ _Tx6–
_Rx6+ _Rx6–
J0–19 Ground J1–19

ISSUE 1 REVISION 2 Balanced-line Interconnect Board (BIB)
Diagram of the 6T43/BIB Connection

Example of BSU and RXU module to T43 or BIB connections.
BSU Backplane LOWER SHELF UPPER SHELF RXU Backplane
XCDR0
SLOT L24
MSI4 XCDR1
SLOT L13 SLOT L23
T43 T43
or or
MSI2 BIB BIB XCDR2
SLOT L22
SLOT L15
0 0 XCDR3
MSI0 MS0 MS4 SLOT L21
SLOT L17
XCDR4
SLOT L20
XCDR5
INTERCONNECT PANEL SLOT L19
(TOP OF CABINET)
XCDR6
SLOT L18
MSI5
SLOT L12 XCDR7
T43 T43 SLOT L17
or or
MSI3 BIB BIB XCDR8
SLOT L14 SLOT L16
1 1
MS1 MS5 XCDR9
MSI1 SLOT L15
SLOT L16
XCDR10
SLOT L14
XCDR11
MSI10 SLOT L13
SLOT L7
T43 T43
or or XCDR12
BIB BIB SLOT L12
MSI8
SLOT L9
XCDR13
2 2 SLOT L11
MSI6 MS2 MS6

SLOT L11 MSI0
SLOT L10
MSI1
SLOT L9
MSI11
SLOT L6
T43 T43
MSI2
or or SLOT L8
MSI9 BIB BIB
SLOT L8 MSI3
3 3 SLOT L7
MS3 MS7
MSI7 MSI4
SLOT L10 SLOT L6

Multiple Serial Interface (MSI/MSI2) ISSUE 1 REVISION 2
Multiple Serial Interface (MSI/MSI2)
Purpose
The Multiple Serial Interface (MSI/MSI2) module is the interface between the inter–site
communication lines and the TDM highway.
MSI/MSI2 module
The MSI module can drive two European 2.048 Mbit/s (E1) data lines.
The MSI2 module is a software configured board and has the following drive capability:
S North American 1.544 Mbit/s (T1).
S European 2.048 Mbit/s (E1).
S Japanese 1.544 Mbit/s (JT1).
One of the E1/T1/JT1 lines is referred to as group A, the other E1/T1/JT1 line is known
as group B.
The E1/T1/JT1 lines are connected at the interconnect panel via either:
S A Balanced-line Interconnect Board (BIB).
S Type 43 (T43) interconnect board.
The MSI/MSI2 can also extract the clock synchronization data from the E1/T1/JT1 line
data stream in order to phase lock the GCLK to the line.
An RS232 maintenance port, to which a Personal Computer (PC) can be connected for
testing and debugging, is provided at the top of the BSU or RXU shelf.
Terminology
One wire pair (balanced or unbalanced) equals one E1/T1/JT1 serial data stream.
Two E1/T1/JT1 serial data streams (transmit and receive) equal one E1/T1/JT1 line.
Requirements
The MSI/MSI2 module is fitted in:
S Slots L6 to L17 of the BSU shelf assembly.
S Slots L6 to L10 of the RXU shelf assembly.
An MSI, MSI2, XCDR or GDP must be located in at least one of the BSU locations below
for BSC initialization purposes.
S Shelf 0 slot 16 (Software communicates via either group A or group B)
S Shelf 0 slot 14 (Software communicates via group A)
S Shelf 1 (if second BSU in BSC) slot 16 (Software communicates via group A)
An RXU initialization uses slot 10 instead of slot 16, and slot 8 instead of slot 14.

ISSUE 1 REVISION 2 Multiple Serial Interface (MSI/MSI2)
The MSI2 Module
Backplane connector
Alarm (red) LED off
Active (green) LED

(normally on)
Reset/disable switch
up (momentary) = reset
middle = normal
down = disable
BSS11_Ch3_33

General features
The MSI converts signals from the E1 lines from serial format to the parallel format that
the TDM highway requires, and converts signals transmitted to the E1 lines from parallel
to serial. The MSI2 can carry out this function for T1 & JT1 lines in addition to E1 lines.
E1 Data
Each serial line can carry the following to and from the active TDM highway in the BSU:
S One 64 kbit/s timeslot for synchronization.
S One 64 kbit/s timeslot for control signalling.
S Thirty 64 kbit/s timeslots that can each be used as follows:
Traffic (four 16 kbit/s compressed voice/data channels each).
Additional control timeslots.
If all 30 timeslots are allocated to traffic, 120 traffic channels are possible.
T1 Data
S Twenty-four 64 kbit/s timeslots that can each be used as follows:
Traffic (four 16 kbit/s compressed voice/data channels each).
Additional control timeslots.
If all 24 timeslots are allocated to traffic, 96 traffic channels are possible.

Transcoded
environment (E1)
The MSI/MSI2 can support 240 x 16 kbit/s traffic timeslots in a transcoded environment,
as defined by GSM. To accomplish this, four 16 kbit/s timeslots are multiplexed into one
64 kbit/s timeslot, as shown in the following example:
30 64 kbit/s timeslots of a serial data stream
x 4 Submultiplexed 16 kbit/s traffic timeslots
x 2 E1 lines
= 240 16 kbit/s traffic timeslots
Transcoded
environment (T1)
The MSI2 can support 192 x 16 kbit/s traffic timeslots in a transcoded environment, as
defined by GSM. To accomplish this, four 16 kbit/s timeslots are multiplexed into one 64
kbit/s timeslot, as shown in the following example:
24 64 kbit/s timeslots of a serial data stream
x 4 Submultiplexed 16 kbit/s traffic timeslots
x 2 T1/JT1 lines
= 192 16 kbit/s traffic timeslots

Functional
description
Refer to the MSI block diagram at the end of this section.
MC68000
processor
A Motorola MC68000 processor, operating at 8 MHz, controls:
S The E1 line to TDM interface function.
S A multiplexer that selects the extracted clock to be routed to the GCLK.
The processor reports the following to the controlling GPROC on the MCAP bus:
S Extracted clock failures.
S Frame alignment errors.
S Multiframe alignment errors.
S Bipolar violations.
S CRC4 errors.
S Transmit or receive failures.
EPROM
The EPROM contains 128 kbytes of bootstrap program code. At power–up the bootstrap
program sends a request message to the GPROC to download the MSI’s operating
program into the SRAM. The SRAM also stores program variables, and can be
permanently saved in EEPROM.
Clock extraction
The clock extraction section extracts the E1 clocks, to which the entire site (either BTS or
BSC) can be synchronized. The two extracted clocks are routed to a multiplexer that
selects which clock signal (if any) is routed to the GCLK.
Frame decoding
The HDB3 and CRC4 decoding section performs frame decoding according to CCITT
recommendation G.704 for digital multiplex equipment.

Block Diagram of the Multiple Serial Interface (MSI)
BACKPLANE CONNECTOR
WATCHDOG RS232
TIMER DRIVERS TTY TEST PORT
MCAP BUS A
RED MCAP INTERFACE
LED
MCAP BUS B
MC6800 PROCESSOR
GREEN
LED EPROM SRAM EEPROM
RESET/
DISABLE
SWITCH CRC4 TDM TDM SWITCHBOUND HIGHWAY B
HDB3
DECODER INTERFACE
DECODER TDM SWITCHBOUND HIGHWAY A
CONTROL
RECEIVED
CLOCK
EXTRACTOR
2
LEVEL IMPEDANCE
CONVERTER RECEIVE
MATCHING
E1 LINE A
LEVEL CONVERTER 2
& E1/T1/JT1 LINE IMPEDANCE TRANSMIT
TRANSMITTER MATCHING
HDB3 CRC4 TDM TDM OUTBOUND HIGHWAY A

ENCODER ENCODER INTERFACE TDM OUTBOUND HIGHWAY B
MUX
EXTRACTED CLOCK REF
TDM TDM SWITCHBOUND HIGHWAY B

HDB3 CRC4
DECODER DECODER INTERFACE TDM SWITCHBOUND HIGHWAY A
RECEIVED
CLOCK
EXTRACTOR
LEVEL 2
IMPEDANCE RECEIVE
CONVERTER MATCHING
E1 LINE B
LEVEL CONVERTER 2

ENCODER ENCODER INTERFACE
TDM OUTBOUND HIGHWAY B
BSS11_Ch3_34

Functional
description
Refer to the MSI2 block diagram at the end of this section.
MC68302 processor
A Motorola MC68302 processor, operating at 16.384 MHz, controls:
S The E1/T1/JT1 line to TDM interface function.
S A multiplexer that selects the extracted clock signal to be routed to the GCLK.
The processor reports the following to the controlling GPROC/GPROC2 on the MCAP
bus:
S Extracted clock failures.
S Frame alignment errors.
S Multiframe alignment errors.
S Bit errors.
S Transmit or receive failures.
EPROM
The EPROM contains 64 kbytes of bootstrap program code memory, 256 kbytes of
nonvolatile operational code memory (Flash EPROM) and 128 kbytes of volatile program
and data memory (SRAM). At power-up the bootstrap program sends a request message
to the GPROC/GPROC2 to download the MSI2’s operating program into the SRAM.
Clock extraction
The clock extraction section extracts the E1/T1/JT1 clocks, to which the entire site (either
BTS or BSC) can be synchronized. In the case of T1/JT1, the extracted clock is fed
through a clock adaptor to convert the 1.544 MHz signal to a 2.048 MHz signal. The two
extracted clocks are routed to a multiplexer that selects which clock signal (if any) is
routed to the GCLK.
Frame decoding
The HDB3 (E1) and B8ZS (T1) decoding section performs frame decoding according to
CCITT recommendation G.704 for digital multiplex equipment.

Block Diagram of the Multiple Serial Interface 2 (MSI2)
BACKPLANE CONNECTOR
LINE INTERFACE A
T1, E1, OR JT1 RXA

LOCAL AND REMOTE LOOPBACK
COMMON 2M OR 1.5M EXTRACTED CLOCK
INTERFACE DATA
DATA
FUNCTIONS
TXA
DISTANCE
MEASURING
SWITCHING
LINE INTERFACE
EXTRACTED CLOCK STATUS/CONTROL
DATA TO GCLK
LINE INTERFACE B
DATA RXB
T1, E1, OR JT1
DATA LOCAL AND REMOTE LOOPBACK
2M OR 1.5M EXTRACTED CLOCK
DATA
TXB
EXTRACTED
CLOCK/
DISTANCE
INBOUND/OUTBOUND MEASURING
INTERFACE DATA
STATUS
CONTROL
TTY PORT
CONTROL
PROCESSOR
RESET 68302
SWITCH
BOOTSTRAP EPROM TDM INTERFACE SWITCHBOUND
SRAM TDM HIGHWAY
WATCHDOG TIMER TSA RAM
POWER/RESET
CIRCUIT OUTBOUND
LEDS BACKPLANE TDM HIGHWAY
TTY PORT
DRIVERS
FLASH EPROM RECEIVERS
PARALLEL I/O
SERIAL EEPROM
16.384 MHZ
REF 125
CLOCK AND REF 60
REFERENCE REF 6.12
GENERATION
TDM
STATUS
AND
CONTROL
EXTRACTED MESSAGE
CLOCK AND DPRAM BUS
DISTANCE DATA
MEASURING MCAP INTERFACE
CONTROL
MCAP CONTROL
REGISTERS
ADDRESS
+5 V, +12 V
AND –12 V

E1/T1/JT1 line to
TDM interface
circuits
There are two identical E1 line to TDM interface circuits on the MSI module and two
identical E1/T1/JT1 line to TDM interface circuits on the MSI2 module. This functional
description applies to both.
The TDM interface section converts incoming data from E1/T1/JT1 line from serial to
TDM parallel.
E1 lines are interleaved onto the TDM bus in groups of two and are spaced out by 32
timeslots. The sequence is as follows:
S Group A timeslot 0, group B timeslot 0.
..........
T1/JT1 lines are interleaved onto the TDM bus in groups of two and are spaced out by 24
timeslots. The sequence is as follows:
..........
Outgoing traffic data is converted from parallel to serial. The serial data is then sent to
the E1/T1/JT1 line transmitter which converts it to standard E1/T1/JT1 line levels.
E1/T1/JT1 data uses Alternate Mark Inversion (AMI) format and line encoding/error
checking can be used as given below:–
Line format Line Encoding Error Checking
E1 HDB3 CRC4
T1/JT1 B8ZS CRC6
After encoding, the data is routed to the loopback multiplexer and to a level converter.
The level converter converts from split-phase, TTL level unipolar to bipolar.
The table illustrates the E1/T1/JT1 line to TDM Interface circuit actions:
Stage Action
1 The system matches impedance and isolates the signal
2 The E1/T1/JT1 line receive signal is applied to a level converter
3 The level converter converts the signal from bipolar to split-phase TTL level
unipolar
4 The signal passes to the HDB3 decoder (E1) or B8ZS decoder (T1) and clock
extraction circuit
5 The signal goes through a crosspoint switch for:
S Diagnostic purposes.
S Distance measurements.
S Drop and insert feature utilization.
The “drop and insert” feature allows a timeslot coming in on group A, which is meant for
another BTS, to be routed back out on group B.


The Generic Clock (GCLK) ISSUE 1 REVISION 2
The Generic Clock (GCLK)
Purpose
The Generic Clock (GCLK) module generates all the timing reference signals that the
BSU or RXU requires. The master TDM clock is normally synthesized from a 16.384
MHz .05 ppm stable reference (temperature stabilized crystal oscillator) and a
2.048 MHz or 1.544 MHz clock recovered from one of the E1 or T1 lines.
Requirements
The GCLK module fits in slots L3 and L5 in the BSU and RXU shelf assemblies. The
module is two slots wide and covers L2/L3 and L4/L5.
There must be a GCLK module in slot L3 of all BSU and RXU shelf assemblies.
A second GCLK module in slot L5 provides n + 1 redundancy.
Mutually redundant GCLKs must reside in the same BSU or RXU.
Clock
control/alarm
logic
The clock control/alarm logic determines the GCLK’s master/slave status based on
module faults and GPROC commands, and reports the operational status to the
GPROC.
Buffered test
ports
Buffered test ports are supplied on the front of the GCLK module for test and
measurement of the input reference signal and output clock and reference signals. The
test jacks are recessed.

ISSUE 1 REVISION 2 The Generic Clock (GCLK)
The Generic Clock (GCLK) Module
BACKPLANE CONNECTOR
ALARM (RED) LED
(NORMALLY OFF)
ACTIVE (GREEN) LED
(MASTER ON)
E1/T1 In
16.384 MHz OUT
TEST 6.12 S OUT

PORTS 60mS OUT
125uS OUT
GROUND
RESET/DISABLE SWITCH FREQUENCY ADJUST
DOWN = DISABLE
LATER VERSIONS OF THE GCLK DO NOT HAVE THE 6.12 mS

AND 125 uS OUTPUTS ON THE FRONT PANEL.
BSS11_Ch3_36

Brief description
Refer to the functional block diagram at the end of this section.
The GCLK module generates all timing reference signals required by the BSS:
S 16.384 MHz TDM clock.
S 125 ms frame reference.
S 60 ms synchronization reference.
S 6.12 s superframe reference.
The GCLK is phase-locked to the recovered clock of a selected E1/T1 line from an MSI
or XCDR module. If the recovered clock signal is lost, and no long term average (LTA) is
available upon which to synchronise, then the GCLK free-runs, providing reference
stability better than 0.05 ppm. The module incorporates self-diagnostics to detect and
isolate board faults and to select a redundant board in the event of module failure.
When a redundant GCLK is present, the GCLKs operate in a master/slave configuration
with the slaved outputs synchronized to the master. If an error is detected, the clock
control circuit reverses the master/slave status of the two GCLKs. Fault status is
reported to the main processor via the MCAP bus.
Reference
oscillator
The reference oscillator uses a Phase Lock Loop (PLL) and a frequency multiplier to
synthesize 16.384 MHz from a E1/T1 line. The PLL consists of:
S A digital phase detector.
S A loop filter.
S A Voltage Controlled Crystal Oscillator (VCXO).
S A divide by eight loop divider.
If a fault is detected on the signal from both E1/T1 lines, the oscillator either uses the LTA
(if available) or free runs with stability being maintained by the VCXO.
Reference
dividers
The 125 ms, 60 ms, and 6.12 s reference dividers consist of cascaded programmable
binary counters to divide the input signal to the correct output frequency. The reference
dividers are synchronized to the master clock. The output of each reference counter is
routed to a multiplexer, which is used to switch the reference output from the master or
the slave GCLK. The output of each reference counter is also routed to the reference
encoder.
Reference
encoders
The reference encoder encodes the reference signals together while maintaining phase
relationships. The encoded clock signals are routed via the backplane to a CLKX to be
transmitted to other shelves at the site, via fibre optic cables.
Reference fail
detect
The reference fail detect circuit monitors the signal on the two E1/T1 lines. Failures are
reported to the clock control/alarm logic. In the event of a reference failure, the GCLK
either uses the LTA (if available) or selects the secondary E1/T1 line reference. In either
case an alarm is reported to the controlling GPROC via the MCAP bus.

Block Diagram of the Generic Clock (GCLK)
BACKPLANE CONNECTOR
16.384 MHz CLK FROM MATE GCLK

125 us REF FROM MATE GCLK
60 ms REF FROM MATE GCLK
6.12 s REF FROM MATE GCLK
ENCODED CLK IN
MUX
REFERENCE ENCODED CLK TO CLKX
ENCODER
ENCODED CLK TO MATE GCLK
MUX
TEST CONNECTOR 6.12 s 6.12 s REF TO BACKPLANE
6.12 s OUT REFERENCE
COUNTER
6.12 s REF TO MATE GCLK
TEST CONNECTOR MUX

60 ms 60 ms REF TO BACKPLANE
60 ms OUT REFERENCE
COUNTER
60 ms REF TO MATE GCLK
MUX
TEST CONNECTOR 125 us
125 us OUT 125 us REF TO BACKPLANE
REFERENCE
COUNTER
125 us REF TO MATE GCLK
MUX
16.384 MHz CLK TO BACKPLANE
TEST CONNECTOR
E1/T1 IN 16.384 MHz TO MATE GCLK
MUX E1/T1 CLOCK REF A
E1/T1 CLOCK REF B
TEST CONNECTOR REFERENCE
16.384 MHz OUT OSCILLATOR
REFERENCE
FAIL
DETECT
CLOCK MASTER/ MASTER/SLAVE

FAILURE SLAVE
RED LED DETECT CONTROL
GREEN LED
CLOCK CONTROL /
ALARM LOGIC OUTPUT ENABLE
RESET/DISABLE MCAP BUS A

SWITCH MCAP
INTERFACE MCAP BUS B
LATER VERSIONS OF THE GCLK DO

NOT HAVE THE 6.12 S, 60mS AND
4.24uS OUTPUTS ON THE FRONT
PANEL
BSS11_Ch3_37

GCLK Operating Modes ISSUE 1 REVISION 2
GCLK Operating Modes
Introduction
There are four modes that the GCLK board can operate in, these are: free run, hold
frequency, set frequency and closed loop. Each mode is explained below referring to the
diagram opposite.
Free Run
When a GCLK is inserted into the digital cage (or on power up) a 30 minute warm up
period is required for the Ovenised Crystal Oscillator (OCXO) to reach the correct
operating temperature, during this time the GCLK is in free run mode and the input to the
Digital to Analogue Converter (DAC) is set to 80(hex). The value 80(hex) cannot be
changed. The OCXO in free run mode will produce a clock output accurate to 0.05ppm.
Note:
The 30 minute warm up period is set by Motorola and cannot be changed.
Hold Frequency
The hold frequency mode is used to maintain a specific clock frequency in the event that
the 2.048MHz reference should fail. This mode uses the last 8 bit word output from the
Analogue to Digital Converter (ADC) to set the Digital to Analogue Converter (DAC). The
hold frequency mode is a transitional mode (typically 10 secs) until the set frequency
mode is activated by the software.
Set Frequency
The set frequency mode allows a GPROC to set the DAC to control the output of the
OCXO during loss of the El/T1reference signal (this is after the transitional hold
frequency mode).
One GPROC in the master cage will be responsible for the GCLK operation and will
monitor the input to the DAC during closed loop operation. In the event of reference
signal failure the GPROC will calculate a best value to set the DAC to maintain the
accuracy of the OCXO. This value is called the long term average and is calculated from
samples read from the GCLK via the MCAP interface. A sample is taken every 30
minutes, up to a total of 48 samples representing the previous 24 hours. When the 49th
sample is read it over-writes the 1st sample to maintain a total of 48.

ISSUE 1 REVISION 2 GCLK Operating Modes
GCLK Operating Modes
16.384 MHz
Phase
detector ADC DAC OCXO
Feedback LPF
output
signal Vin
Fin Conv.CS High
OS.IN priority
cell 16.384
Input signal OS.IN
DET MHz
2.048 MHz
Calibration
adjust Vref
8
256 kHz
80 (Hex) Read freq Set freq
EN Buffer latch latch
OEl OE OE
Control GPROC (MCP data bus)

Reference fail detect
To/From Master GPROC BSS11_Ch3_38

GCLK Operating Modes ISSUE 1 REVISION 2
Closed loop
The closed loop mode is provided to eliminate frame slips due to reference clock failure
and/or OCXO ageing. In this mode the 16.384MHz clock frequency will be exactly eight
times the mean frequency of the incoming reference clock. The reference clock source
must be accurate to +/–0.01 ppm.
When the GCLK is frequency locked the calibration and ageing of the OCXO can be
monitored using the Long Term Average (LTA). If the LTA is outside a database
predefined limit then an alarm will be raised, typically this alarm will allow the GCLK to
operate for another 30 days before re-calibration is required (10% upper/lower values of
LTA, as defined in the database). When in closed loop mode the loop is immune to line
breaks of less than 80 microseconds.
Due to this GCLK calibration will take place every 3–7 years.
Within the closed loop mode there are two sub modes or states:
S Acquiring frequency lock state
S Frequency lock state
The acquiring frequency lock state is the operating condition where the GCLK PLL output
is converging towards the long-term frequency of the El/T1 line. The time spent in this
state is dependant on the hardware revision level of the GCLK board, current build
boards will be in this state a maximum of 2 minutes, typically much less. Once this state
is reached (i.e. the output is within GSM specifications) the second sub state, frequency
lock state is activated.
This mode is again dependent on the GCLK hardware revision level (either 2 or 10
minutes), and is used to confirm that the GCLK output is stable within the GSM
specification for the set period (2/10 minutes).
GCLK
Synchronization
Configuration
To enable the use of an E1 link as a synchronisation reference it must be allocated a
priority. Priority allocation is from 1 to 255, with 255 being the highest. If the extracted
reference is given 0 it will not be used.
To ensure the extracted reference is only taken from higher order components in the
network, the E1 links providing connectivity to lower order components are given the
priority 0.

ISSUE 1 REVISION 2 GCLK Operating Modes
GCLK Synchronization Configuration
E1 Links
BSC MSI MSI MSI

GCLK Priority Priority Priority
250 251 253
GPROC
GPROC Dynamic Switch
Ops +Maint.
MSC link
Site control processing
GSM call MSI MSI MSI
Switch manager processing Priority Priority Priority
0 0 0
Main control Link control
processor processor
MSC E1 Links
To use the E1 as a reference
it must have a priority
All entities must be between 1 (low) and 255 (high).
synchronised with a RXCDR 0 the extracted clock is not used
higher level
BSC
BTS BTS
BSS11_Ch3_39.

Transcoder Board ISSUE 1 REVISION 2
Transcoder Board
Purpose
The Transcoder (XCDR) module:
S Interfaces an E1/T1 serial line to the internal cabinet TDM highway, which is in a
parallel format.
S Transcodes thirty 64 kbit/s channels into 120 compressed voice/data channels, in
accordance with the GSM recommendations:
– Channel zero of each E1/T1 line is reserved for synchronization.
– Channel sixteen is reserved for link control signalling.
If the BSC performs the transcoding function, XCDRs interface the BSU or RXU to the
MSC in place of MSI modules.
The XCDR transcodes the remaining 30 channels into 120 x 16 kbit/s compressed
channels. The synchronization and signalling channels and the 120 compressed
voice/data channels are applied to the active TDM highway in the BSU or RXU.
These channels can be placed in any of the 1024 channels on the TDM highway under
control of the GPROC/GPROC2.
Terminology
One wire pair (balanced or unbalanced) equals one E1/T1 serial data stream.
Two E1/T1 serial data streams (transmit and receive) equal one E1/T1 line.
Requirements
The XCDR module is fitted in:
S Slots L6 to L17 (but maximum 6 modules in total) in the BSU shelf assembly.
S Slots L6 to L24 (maximum 19 modules) in the RXU shelf assembly.
An MSI, MSI2, XCDR or GDP must be located in at least one of the BSU locations below
for BSC initialization purposes.
S Shelf 0 slot 16 (Software communicates via either group A or group B)
S Shelf 0 slot 14 (Software communicates via group A)
S Shelf 1 (if second BSU in BSC) slot 16 (Software communicates via group A)
An RXU initialization uses slot 10 instead of slot 16, and slot 8 instead of slot 14.
Brief description
Refer to the XCDR block diagram at the end of this section.
The XCDR module contains a digital signal processor (DSP) unit that performs:
S GSM-defined speech encoding.
S GSM-defined speech decoding.
S Submultiplexing functions.
The speech transcoder bi-directionally interfaces the 64 kbit/s E1/T1 line in the land
network to the 13 kbit/s vocoder format used on the air interface.
Signalling channels are passed straight through the transcoder.
Architecture
The XCDR module contains the following major systems:
S Processor system.
S DSP system.
S Line interface system.
S Switching system.
S MCAP interface system.
S TDM interface system.

ISSUE 1 REVISION 2 Transcoder Board
The Transcoder (XCDR) Module
BACKPLANE CONNECTOR
ALARM (RED) LED

(NORMALLY OFF)
ACTIVE (GREEN) LED
(NORMALLY ON)
RESET/DISABLE SWITCH
DOWN = DISABLE
BSS11_Ch_40

Processor
The main component of the processor system is the Microcontroller Unit (MCU), which:
S Controls and interfaces the five major systems (listed below) on the XCDR
module.
S Performs self-diagnostics and error monitoring.
Other components of the processor system are:
S A watchdog timer.
S 16 kbytes of RAM.
S 64 kbytes of EEPROM.
S 1 kbyte of dual port RAM.
S A power monitor circuit.
The watchdog timer is periodically strobed by the MCU; an alarm is generated if it is not
strobed before a pre-set timeout.
The Digital
Signal Processor
(DSP)
The DSP system consists of:
S 30 mask programmed DSP units.
S A subrate multiplexer.
S A serial port timing generator.
S A parallel host interface.
Each DSP unit has its own internal memory (2 kbytes of RAM and 12 kbytes of ROM)
and serial interface. The DSP units are arranged into four banks (three banks of eight
and one bank of six).
The serial port timing generator keeps all DSPs synchronized. The parallel host interface
is used to transfer status and control data between the MCU and DSP units.
Subrate
multiplexer
modes
The subrate multiplexer can operate in three modes. The following table lists the modes
and resulting functions:
Mode Functions
The DSP output is logically connected to its input, enabling a self
DSP loop back
test function.
Each DSP receives 16 bits of data:
16 kbytes The first 8 bits are from a 16 kbytes/s subrate channel from the
multiplexed TDM highway. Two bits at a time are expanded into PCM.
The last eight bits are from the E1/T1 line data stream. The PCM
is processed into 16 kbit/s TRAU frames.
Each DSP receives 16 bits of data:
64 kbytes The first eight bits are from the TDM bus, and are passed to the
non-multiplexed E1/T1 line.
The second eight bits are from the E1/T1 line, and are passed to
the TDM bus.

Block Diagram of the Transcoder (XCDR)
RECEIVED
CLOCK EXTRACTED CLOCK REF
EXTRACTOR
LEVEL 2
CONVERTER IMPEDANCE E1/T1 LINE A RECEIVE
CS61574 MATCHING
LEVEL
CONVERTER 2
E1/T1 IMPEDANCE E1/T1 LINE A TRANSMIT
FRAMER CRC4/HDB3
MT8979AP ENCODER
FRAMER CRC4/HDB3
MT8979AP DECODER
TDM OUTBOUND HIGHWAY A
TDM SWITCHBOUND HIGHWAY A
TDM
SWITCHING INTERFACE
SYSTEM
TDM SWITCHBOUND HIGHWAY B

CONTROL
GREEN
LED MCAP BUS A
MCAP BUS
RED INTERFACE
LED MCAP BUS B
MCU
MC68HC811E2
RESET/ POWER TTY TEST PORT
DISABLE MONITOR
SWITCH
CONTROL
CONTROL
WATCHDOG
TIMER
DSP UNIT 1
SUBRATE
MULTIPLEXER
DSP UNIT 2
DSP UNIT 3
SERIAL PORTING DSP UNIT 4

GENERATOR
BACKPLANE CONNECTOR
DSP UNIT 29
DSP UNIT 30
BSS11_Ch3_41

Line interface
The line interface system performs:
S Impedance matching.
S Secondary surge protection from high voltage transients (such as lightning strikes),
which may be transmitted along the E1/T1 lines.
The impedance matching circuit consists of isolation transformers and Zener diodes.
After impedance matching and isolation the E1/T1 line receive signal is applied to a level
converter that converts the signal from bipolar to split-phase TTL level unipolar.
After level conversion the received E1/T1 line data is sent to the clock extraction circuit
and a HDB3 decoder. The clock extraction section extracts the E1/T1 clock to which all
BSU/RXU shelves can be synchronized. The HDB3/CRC4 decoding section performs
frame decoding law CCITT recommendation G.704 for digital multiplex equipment. Traffic
is then routed to the switching system.
Switching
The switching system consist of two separate digital switches, each performing a
different function.
S The first switch has the E1/T1 line data stream and TDM data streams passing
through it.
S The second switch is used as an interface between the processor section and the
framer of the line interface system.
MCAP interface
The MCAP interface system supports two redundant MCAP buses to the XCDR. The
XCDR communicates with the GPROC in the same manner as all other full-size
modules.
TDM interface
The TDM interface system takes traffic data from the TDM bus and converts it from
parallel data to serial data. The serial data is then sent to the switching system.


The Generic DSP Processor (GDP) ISSUE 1 REVISION 2
The Generic DSP Processor (GDP)
Purpose
The Generic DSP Processor (GDP) module can be used as an enhanced XCDR, with
additional features, including Enhanced Full Rate (EFR) speech and uplink/downlink
audio volume control. The GDP DSP firmware is downloadable whereas the XCDR
DSP firmware is mask programmed.
The description in the following pages assumes the GDP is being used as an enhanced
XCDR.
NOTE
The GDP module can only be used with systems running GSR 3 or later
releases, as this contains the neccessary software support to allow operation.
In addition, for GRS3, GPROC2 must be fitted to the BSC as the master
processor (with redundant master and CSFP).
For a BSC which will operate the EFR speech option, all transcoder boards it
connects to must be GDP, not XCDR.
The GDP has two configured types, one for E1 serial line use and one for T1
serial line use. Each GDP type has a different framer/transceiver with
accompanying crystall oscillator, and two associated resistors. This means
that a GDP used for E1 serial line use cannot be used for T1, and a GDP used
for T1 serial line use cannot be used for E1.
The GDP module:

S Provides the transcoding interface to the MSC. The GDP module is located at the
RXCDR, or at a BSC where transcoding is integrated within the BSC.
S Interfaces an E1/T1 serial line to the internal cabinet TDM highway, which is in a
parallel format.
S Transcodes thirty E1(twenty-four T1) 64 kbit/s channels, inserting them as part of
120 E1 (96 T1) compressed voice/data channels, in accordance with the GSM
recommendations:
– Channel zero of each E1 line is reserved for synchronization.
– Channel sixteen of each E1 line is reserved for link control signalling.
– The 30 remaining E1 channels are transcoded.
Each GDP supports thirty compressed voice and data channels, using 15 DSPs. These
channels, and the synchronization and link control signalling channels, can be placed in
any of the 1024 channels on the TDM highway under control of the GPROC/GPROC2.
Terminology
One wire pair (balanced or unbalanced) equals one E1/T1 serial data stream.
Two E1/T1 serial data streams (transmit and receive) equal one E1/T1 line.

ISSUE 1 REVISION 2 The Generic DSP Processor (GDP)
Block Diagram of the GDP
RECEIVED
CLOCK EXTRACTED CLOCK REF
EXTRACTOR
2
E1/T1 LINE A RECEIVE
E1/T1 LINE
INTERFACE
2
E1/T1 LINE A TRANSMIT
ESSI DIGITAL
TEST CROSSPOINT TDM OUTBOUND HIGHWAY A
SWITCH
PORT
TDM
INTERFACE
TDM SWITCHBOUND HIGHWAY B
GREEN
LED MCAP BUS A
MCAP BUS
RED INTERFACE
LED MCAP BUS B
MCU
SUBSYSTEM
RESET/ POWER TTY TEST PORT
DISABLE MONITOR
SWITCH
SERIAL DATA SCI MUX

FORMATTERS
DSP SUBSYSTEM
BACKPLANE CONNECTOR
BSS11_CH3_42

The Parallel Interface Extender (PIX) ISSUE 1 REVISION 2
The Parallel Interface Extender (PIX)
Overview
Refer to the block diagram on the next page.
The Parallel Interface Extender (PIX) module provides:
S An input/output (I/O) interface for customer site equipment.
S The interface logic between the GPROC and external customer alarm devices
such as relays and switches.
S Eight optically isolated inputs and four relay outputs.
Requirements
PIX modules can be fitted in the following slots of a BSU or RXU shelf assembly:
S BSSC2 and BTS6: slots U16, U17 and U18.
S BSSC, BTS4 and BTS5: slots U15 and U16.
PIX module
The diagram shows a PIX module:
BACKPLANE CONNECTOR
ALARM (GREEN) LED

(ON = NO ALARMS)
(OFF = CUSTOMER ALARM DETECTED)
CONNECTOR IS CABLED TO TOP OF

CABINET FOR INTERCONNECT TO
CUSTOMER SITE EQUIPMENT BSS11_Ch3_42a

ISSUE 1 REVISION 2 The Parallel Interface Extender (PIX)
Block Diagram of the PIX
BACKPLANE CONNECTOR
62 PIN “D”
CONNECTOR
–12 V +12 V
SENSE S1 DC to DC
SURGE OPTO– CONVERTER
SENSE D1 PROTECTION COUPLER
SENSE S2 SURGE OPTO– +12 V

EARTH
SENSE S4 SURGE OPTO–

FROM
CUSTOMER SENSE S5 SURGE
EQUIPMENT OPTO–

SERIAL BUS
SENSE S7 SURGE TRANSCEIVER BSS SERIAL BUS A
OPTO–
SENSE D7 PROTECTION COUPLER BSS SERIAL BUS B

N. O. 1
N. C. 1 RELAY RELAY
COM 1 DRIVER
N. O. 2
TO N. C. 2 RELAY RELAY
CUSTOMER COM 2 DRIVER
EQUIPMENT N. O. 3
N. C. 3 RELAY RELAY
COM 3 DRIVER
N. O. 4
N. C. 4 RELAY RELAY
COM 4 DRIVER
GREEN
LED
BSS11_Ch3_43

The Battery Backup Board (BBBX) ISSUE 1 REVISION 2
The Battery Backup Board (BBBX)
Purpose
If the external supply fails, the Battery Backup Board (BBBX) provides a backup supply
of +5 V at 8 A. The BBBX can only be fitted in a BTS6 cabinet.
The +5 V DRAM battery backup supply maintains power to the:
S Optical circuit on the LANX module.
S DRAM memory located on the GPROC.
Normally, the PSMs supply +5 V DRAM voltage to the BSU or RXU backplane. If the
PSMs fail to deliver this due to cabinet input power failure or PSM failure, the BBBX
converts an external backup supply to a fused +5 V DRAM supply.
Requirements
The BBBX module is normally positioned in slots U16, U17 or U18 of the BSU or RXU
shelf assembly, but can be fitted in any spare half-size card slot.
All connections are made at the front of the module.
BBBX module
The following shows a BBBX module:
CONNECTOR PC1 IS CABLED TO AI2 ON THE

DIGITAL CAGE BACKPLANE
CONNECTOR PC2 IS CABLED TO TOP

OF CABINET FOR CONNECTION TO
PC4 ON THE DAB AND BATT BACKUP BSS11_Ch3_43a

ISSUE 1 REVISION 2 The Battery Backup Board (BBBX)
Block Diagram of the BBBX
4 PIN “AMP”
CONNECTOR
OUTPUT VOLTAGE
(+5 V @ 8 A)
9 PIN “D”
CONNECTOR
INPUT VOLTAGE SURGE BRIDGE DC to DC

(20 to 75 V @ 3.2 to 0.85 A) PROTECTION RECTIFIER CONVERTER
OVER VOLTAGE
OUTPUT GOOD
ALARM
INPUT GOOD SIGNALS OVER TEMPERATURE
BSS11_Ch3_44

Local Area Network (LAN) ISSUE 1 REVISION 2
Local Area Network (LAN)
Purpose
WARNING
Possible laser radiation when fibre optic cables are disconnected.
Do not look directly into beams with or without the use of any optical
aids. Radiation can come from either the data in/out connectors or
The Local Area Network Extender (LANX) module is required for each BSU or RXU
shelf. The LANX:
S Connects one of the LAN interfaces of each GPROC/GPROC2 in a BSU or RXU
shelf to the local shelf token ring LAN via the shelf backplane.
S Allows optical LAN extension from one BSU or RXU to another.
S Switches empty module slots or faulty GPROC/GPROC2s out of the LAN.
S Sets the cage (BSU or RXU shelf) ID.
S Performs on-board MCAP bus arbitration.
S Provides shelf active/standby redundant LAN control.
Shelf to shelf extension is via a LANX module in each shelf, interconnected with fibre
optic cabling.
The LANX supports up to eight GPROC/GPROC2s on the local LAN in one BSU or RXU
shelf.
Requirements
LANX modules must be fitted in slots U19 and U20 of the BSU or RXU shelf assembly at
all times.
A sixteen position (0 to F hex) rotary switch on the LANX module sets the BSU or RXU
LAN address (shelf ID number).
LANX module
The diagram shows a LANX module:
FIBRE OPTIC INPUT FROM ANOTHER LANX BACKPLANE CONNECTOR

IN ANOTHER SHELF AT THE SITE
FIBRE OPTIC OUTPUT TO ANOTHER LANX

IN ANOTHER SHELF AT THE SITE
ROTARY SWITCH
FOR SETTING SHELF ID NUMBER
BSS11_Ch3_44a

ISSUE 1 REVISION 2 Local Area Network (LAN)
BSS Local Area Network (LAN)
Loop (fibre optic)
GPROC
TX RX
0
LANX GPROC
7
GPROC GPROC
1 6
TOKEN
GPROC
5
GPROC
2
GPROC
GPROC 4
3
BSS11_Ch3_45

Brief description
Refer to the block diagram at the end of this section.
Each LANX receives LAN data from another shelf via optical fibre cables and:
1. Routes the LAN data to the first GPROC/GPROC2.
2. Receives the LAN data back from the first GPROC/GPROC2.
3. Routes the LAN data to the second GPROC/GPROC2.
4. Receives the LAN data back from the second GPROC/GPROC2.
And so on until all GPROC/GPROC2s in the shelf have received the LAN data.
The LAN data received back from the last GPROC/GPROC2 in the shelf is sent via fibre
optics to the next shelf (if LAN extension is used). If a GPROC/GPROC2 is not present in
the shelf or has failed, the LANX bypasses it and passes the LAN data to the next
GPROC/GPROC2.
Local LAN data

switching
Each GPROC/GPROC2 using the LANX uses the following signals to route LAN data:
S LAN DATA IN.
S LAN DATA OUT.
S INSERT.
GPROC/GPROC2 present
When the GPROC/GPROC2 is present and operating with no faults, the INSERT line is
logic 1, causing LANX multiplexers to switch the GPROC/GPROC2 signals as follows:
S LAN DATA OUT signal of this GPROC/GPROC2 is switched to the LAN DATA IN
signal of the next GPROC/GPROC2 slot. In the case of shelf extension, the LAN
DATA OUT signal of GPROC/GPROC2 7 is switched to the fibre optic transmitter
stage.
S LAN DATA OUT signal from the previous GPROC/GPROC2 slot is switched to the
LAN DATA IN signal of this GPROC/GPROC2. In the case of shelf extension, the
signal from the fibre optic receiver stage is switched to the LAN DATA IN signal of
GPROC/GPROC2 0.
GPROC/GPROC2 not present

If the GPROC/GPROC2 is not present or operating with faults, the INSERT line is logic 0
causing LANX multiplexers to switch the GPROC/GPROC2 signals as follows:
S LAN DATA OUT signal of this GPROC/GPROC2 is switched (looped back) to the
LAN DATA IN signal of the same GPROC/GPROC2.
S LAN DATA OUT signal of the previous GPROC/GPROC2 is switched to the LAN
DATA IN signal of the next GPROC/GPROC2.
This removes the GPROC/GPROC2 from the LAN ring, and subsequent LAN data
bypasses the GPROC/GPROC2.

LANX Requirements
BSSC BSSC
LANX A LANX B LANX A LANX B

CAGE 1 CAGE 3
LANX A LANX B LANX A LANX B

CAGE 0 CAGE 2
0
f 1
2
e 3
d 4
c 5
b 6
a
9 8 7
Rx Tx Rx Tx Rx Tx Rx Tx
LANX Cage 0 LANX Cage 1 LANX Cage 2 LANX Cage 3
Fibre Optic
BSS11_Ch3_46

Extended LAN
data switching
In configurations of more than one shelf, the LANX allows the local LAN data to be
extended to another shelf via optical fibre connected to a LANX in the other shelf.
Any of the GPROC/GPROC2s in the shelf controls local LAN data switching between
shelves. Control is via the serial bus connected to the LANX signal, LAN
LOCAL/EXTERNAL.
Logic 1
A logic 1 on the LAN LOCAL/EXTERNAL line causes multiplexers on the LANX to switch
signals as follows:
S LAN DATA IN signal of GPROC/GPROC2 7 is switched to the fibre optic
transmitter stage. The optical transmitter provides a Tx data signal, consisting of
the local LAN data of this shelf, which is transmitted via fibre optic to a LANX in
another shelf.
S Rx data signal from the fibre optic receiver stage is switched to the LAN DATA
OUT signal of GPROC/GPROC2 0.
Logic 0
A logic 0 on the LAN LOCAL/EXTERNAL line causes multiplexers on the LANX to switch
signals from LAN DATA IN signal of GPROC/GPROC2 7 is switched to the LAN DATA
OUT signal of GPROC/GPROC2 0.
This bypasses the LANX fibre optic transmitter and receiver stages consequently
disabling local LAN extension to another shelf.
Power loss
If the local LANX loses dc power, the Rx data signal from the fibre optic receiver stage is
switched (looped back) to the optical transmitter, providing a Tx data signal via fibre optic
to the LANX in another shelf.
Bus arbiter
The LANX bus arbiter decides which GPROC/GPROC2 is allowed to write data to the
MCAP bus via the LAN DATA IN line. Each GPROC/GPROC2, 0 to 7, can assert its
respective BUS REQUEST line. The bus arbiter starts by monitoring GPROC/GPROC2
0 slot.
If GPROC/GPROC2 0 has an active BUS REQUEST line, the bus arbiter asserts the
GPROC/GPROC2 0 BUS GRANT line. GPROC/GPROC2 0 seizes the MCAP bus and
writes data to the bus. When GPROC/GPROC2 0 has finished writing data to the MCAP
bus, it deactivates the BUS REQUEST line. This frees the bus and the bus arbiter
activates the BUS GRANT line of the next higher numbered GPROC/GPROC2 with an
active BUS REQUEST line.

LANX Extension (4 cages)
CAGE 0 BSU
SLOT
Rx
U20
LANX
A
Tx
CAGE 1 BSU
Fibre Optic Cable SLOT
U20
LANX
Rx
A
Tx CAGE 2 BSU
SLOT
U20
Rx LANX
A
Tx
CAGE 3 BSU
SLOT
Rx U20
LANX
A
Tx
BSS11_Ch3_47

Redundant LAN
If the redundant GPROC/GPROC2 LAN interface is used, a redundant LANX is required.
Each LANX has two serial bus interfaces for communications with the
GPROC/GPROC2. The selection of which LAN interface is to be used is determined by
the GPROC/GPROC2.
Shelf ID
The shelf ID is a unique hexadecimal number assigned to each BSU or RXU shelf. The
LANX is fitted with a 16-position (hexadecimal encoded) rotary switch, which defines the
shelf ID number of the shelf containing the LANX. The shelf ID is read by the
GPROC/GPROC2 via the serial bus interface. The ID number is used by the BSS
software when configuring the BSU or RXU.
No two shelves at a site can have the same shelf ID. When a redundant LANX is present
in a shelf, it must have the same ID number as the primary LANX.
The following rules apply:
S A BSU shelf in a BSC is numbered 0 to D (hexadecimal).
S A BSU shelf in a BTS is numbered F to 2 (hexadecimal).
Front panel
The front panel of the LANX incorporates:
S Rx fibre optic input connector. This connects to the Tx fibre optic output of a LANX
in another shelf.
S Tx fibre optic output connector. This connects to the Rx fibre optic input of a LANX
in another shelf.
S Rotary switch for setting the BSU/RXU shelf ID number.

Functional Block Diagram of the LANX Module
BACKPLANE CONNECTOR
ROTARY SELECT BSS SERIAL BUS A

SERIAL
SWITCH SHELF ID INTERFACE
NUMBER BSS SERIAL BUS B
Rx DATA FIBRE OPTIC

RECEIVER BUS ARBITER
LAN LOCAL/EXTERNAL
BUS GRANT 0
MUX
LAN DATA OUT 0
BUS REQUEST 0 GPROC
SLOT 0
LAN DATA IN 0
INSERT 0
BUS GRANT 1
MUX
LAN DATA OUT 1
GPROC
BUS REQUEST 1 SLOT 1
LAN DATA IN 1
INSERT 1
BUS GRANT 2
MUX
LAN DATA OUT 2
POWER FAIL GPROC
DETECT &
LAN LAN DATA IN 2
LOCAL/EXTERNAL
LOGIC INSERT 2
GPROC
DC INPUT SLOTS
POWER 3, 4, 5, 6
DISTRIBUTION
BUS GRANT 7
MUX
LAN DATA OUT 7
BUS REQUEST 7 GPROC
Tx DATA FIBRE OPTIC SLOT 7
TRANSMITTER LAN DATA IN 7
INSERT 7
BSS11_Ch3_48

Motorola Cellular Advanced Processor (MCAP) ISSUE 1 REVISION 2
Motorola Cellular Advanced Processor (MCAP)
Introduction
The MCAP is a parallel communications bus clocked at a rate of 16.384 MHz. It allows
one GPROC in the BSU or RXU cage to communicate with the following peripheral
boards:
1. Kiloport Switch (KSW)
2. Multiple Serial Interface (MSI)
3. Generic Clock (GCLK)
4. Transcoder (XCDR)
5. Generic Digital Signal Processor (GDP)
GPROCs communicate with each other via the LAN interface, whilst the MCAP bus is
used for comunications between the GPROCs and the peripheral boards.
In order to gain access to the MCAP bus, a GPROC must go through an arbitration
sequence carried out on the LANX. Each MCAP bus (A or B) has its own arbiter located
on a LANX (A or B) card.
There are effectively two buses on the backplane (A and B). One bus, A or B is active
and the other will be in standby mode, depending on the state of the system. The
operations of both buses are identical. The only distinction made will be active bus or
standby bus.
Within a BSC or RXCDR each cage will have one GPROC assigned as MCAP master.
This GPROC controls all communication to the peripheral boards and so will always be
granted use of the MCAP bus by the LANX card.
(In a non-M-Cell BTS there will be GPROCs assigned as DHPs (Digital Host Processor)
controlling DRIM (Digital Radio Interface) cards via the MCAP bus. In this case the
LANX will provide arbitration between the DHPs and the MCAP master GPROC).

ISSUE 1 REVISION 2 Motorola Cellular Advanced Processor (MCAP)
The Motorola Cellular Advanced Processor (MCAP)
Token Ring LAN between GPROC boards
BSP
GPROC
1 GPROC GPROC
MCAP 2 2
MASTER
Peripheral Peripheral Peripheral

Board Board Board
Peripheral Boards: GCLK, KSW, MSI, XCDR

Logical Association of GPROC Boards and Peripheral Boards
BSS11_Ch3_49

MCAP Communications ISSUE 1 REVISION 2
MCAP Communications
The GPROC communicates with peripheral boards (i.e. KSW, MSI, XCDR, etc.) via the
Motorola Cellular Advanced Processor Bus (MCAP Bus). The process on the GPROC
that controls this interaction is called the MCAP DLSP. The MCAP DLSP provides
multiple services to MCAP bus user processes. These services are:
S A high level interface between application processes on GPROCs and peripheral
boards connected to the MCAP bus.
S Managing code loading of the peripheral boards connected to the MCAP bus. The
term code loading refers to the collected actions of code downloading and code
uploading.
S Maintaining cage configuration with regard to the peripheral boards within the
cage. This information is based on the types of peripheral boards contained within
the cage.
S Overflow protection for MCAP message buffers.
S A routing facility for messages that flow between the application processes (on the
GPROCs) and the peripheral board firmware. MCAP DLSP is also responsible for
providing an error free communication path between the peripheral boards and
application software.
Since the MCAP bus is confined to one cage (not extendable), the MCAP DLSP is only
responsible for providing a communicating path between GPROCS and peripheral
boards that reside in the same cage. Application processes that need to communicate
with peripheral boards in different cages will have to use different MCAP DLSPs. An
MCAP DLSP may reside on any GPROC but there is only one active MCAP DLSP per
cage.
Address Area
Individual boards are addressed using a physical location system, where each of the
boards are assigned a 5 bit address related to its physical card slot position (ID) in the
cage plus 18 bits giving an address range of 256k locations for each board and an
additional bit to control selection of either MCAP A or MCAP B buses.
Data Area
The physical data width of the bus is 16 lines (2 bytes or word). However a separate line
from the bus master(s) allows the bus to support dynamic sizing i.e. the width of the bus
changes to correspond to the width of the data i.e 8 or 16 bits. A parity bit is also added
for error detection.

ISSUE 1 REVISION 2 MCAP Communications

Dual Port Ram (DPR) ISSUE 1 REVISION 2
Dual Port Ram (DPR)

Communication over the MCAP bus, between the GPROC and the peripheral boards, is
achieved via a buffer located in the MCAP interface known as the Dual Port Ram (DPR).
The 256K DPR is divided into 2 x 128k segments, one for downlink communication
(GPROC to peripheral board) and one for uplink communication (peripheral board to
GPROC).
The make up of the Dual Port Ram is shown below.
255k
Host Port
128–255k of DPR,
used for uplink
communication.
Peripheral board to
GPROC Data
128k
127k
Host Port
0–127k of DPR,
used for downlink
communication.
GPROC to peripheral boards.
Data
0k
BSS11_Ch3_49a
Downlink
communication
The initial communication process between GPROC and peripheral board is via the host
port, a location uppermost in the DPR downlink segment. This contains a message for
the receiving peripheral board’s control processor, indicating an area of memory in the
DPR containing data, placed there by the GPROC, destined for the peripheral board.
(The memory area the data is stored in is dependent upon the destination address.) A
message placed in the host port will cause an interrupt to be sent to the control
processor. Upon receipt of the interrupt the control processor determines the address of
the data to be read. Once the peripheral board has read the data it sends a message
acknowledgement to the host port. This in turn causes an interrupt to be sent to the
GPROC. Upon receipt of this interrupt the GPROC clears the area of the DPR containing
the data.
Uplink
communication
Communication in the uplink direction is the reverse of the downlink direction, utilising the
uplink segment of the DPR.

ISSUE 1 REVISION 2 Dual Port Ram (DPR)
GPROC to peripheral boards (Downlink) message flow

diagram
GPROC Peripheral
Board
DPR Control processor
Interface
1. GPROC places data into buffer area
of DPR and message into host port.
2. Message in host port causes

interrupt to be sent to destination
peripheral board control processor
3. Control processor decodes
message in host port and reads data
buffer area.
4. Once read the control proceesor
places a message acknowledgement
into the host port.
5. Message acknowledgement causes

an interrupt to be sent back to the
GPROC
6. GPROC releases the buffer area

of the DPR containing the data.
BSS11_Ch3_50

Dual Port Ram (DPR) ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Dual Port Ram (DPR)
Peripheral board to GPROC (uplink) message flow

diagram
GPROC Peripheral
Board
DPR Control processor
Interface
1. Control processor places data into
buffer area of DPR and message into
host port.
2. Message in host port causes interrupt

to be sent to GPROC.
3. GPROC decodes message in

host port and reads data buffer area.
4. Once read the GPROC places a

message acknowledgement into
the host port.
5. Message acknowledgement causes an

interrupt to be sent back to the Control
processor.
6. Control processor releases
the buffer area of the DPR containing
the data.
BSS11_Ch3_51

Time Division Multiplexed (TDM) Bus ISSUE 1 REVISION 2
Time Division Multiplexed (TDM) Bus

The Time Division Multiplexed (TDM) bus is an 8 bit parallel highway used to switch
traffic and signalling data within a site. The TDM highway allows GPROCs and peripheral
cards to interface to the 2.048Mbit/s E1 links connecting the network together.
A Kiloport Switch (KSW) board is in control of the TDM highways known as the
switch-bound and out-bound highways. Switch-bound identifies the highway going into
the KSW and out–bound, the highway going away from the KSW.
TDM Frame
Structure
The TDM frame consists of 1024 timeslots each of 122ns giving an overall frame
duration of 125 msec.
The TDM bus has a 8-bit wide data field and uses a 1-bit parity check enabling a data
rate of 64 kbit/s on each TDM timeslot.
The bus has 480 frames per TDM multiframe over 60 ms duration. The 60 ms TDM
multiframe is used for synchronisation of the TDM Highway and the air interface.
TDM Bus
Integrity
The TDM bus structure uses parity to check the bus integrity. The outbound TDM bus
(outbound with respect to the switch) uses even parity. Even parity causes a floating
bus with pull-up resistors to generate a parity alarm on the receiving expansion Interface
cards. Thus, if the switch or KSWX is removed from the shelf, a bus parity alarm is
generated on the expansion Interface cards. This parity alarm is one factor in
determining which TDM bus is active on any given expansion Interface card.
The switchbound TDM bus is also at even parity. The reason is the same; namely, a
floating bus (expansion Interface card pulled or not present) generates a parity alarm.
The KSW has the ability to change the expected parity sense to odd in order to induce
TDM bus parity alarms. This feature provides a means of checking the parity logic.

ISSUE 1 REVISION 2 Time Division Multiplexed (TDM) Bus
The Time Division Multiplexed (TDM) Bus
BSC
MSC 2 Mbit/s MSI

E1 link
Outbound
RXCDR highway
XCDR
KSW
Outbound Switchbound
highway highway
KSW
MSI
Switchbound
highway
2 Mbit/s
MSI BTS E1 link
BTS
BSS11_Ch3_53

The Kiloport Switch (KSW) ISSUE 1 REVISION 2
The Kiloport Switch (KSW)
Purpose
The Kiloport Switch (KSW) module is a time division digital switch, and:
S Performs timeslot interchange for the active TDM highway.
S Communicates with the controlling GPROC via the MCAP bus.
S At a BSC, routes the logical channels dynamically on a per-call basis.
See also the TSW section of this chapter, in which the timeslot switch (a sub equipped
version of the KSW) is described.
Requirements
The KSW module fits in the following slots in a BSU or RXU shelf assembly:
S L1 for TDM highway B.
S L27 for TDM highway A.

ISSUE 1 REVISION 2 The Kiloport Switch (KSW)
The Kiloport Switch (KSW) Module
BACKPLANE
CONNECTOR
ALARM (RED) LED

(NORMALLY OFF)
ACTIVE (GREEN) LED

(NORMALLY ON)
RESET/DISABLE SWITCH
DOWN = DISABLE
BSS11_Ch3_52

Architecture
Refer to the KSW block diagram on page 3–129.
A Motorola MC56001 digital signal processor (DSP) controls the KSW internally. The
DSP:
S Executes port connects between the switchbound TDM highway and the outbound
TDM highway.
S Controls the Timeslot Interchange (TSI) section via the connection RAM control
section.
S Performs on-line and off-line self diagnostics, including:
– Internal (KSW-related) tests.
– External (TDM bus-related) tests.
S Controls inbound and outbound multiplexers.
S Processes alarms.
S Updates the dynamic pattern registers.
The DSP communicates via the MCAP bus interface logic, the DSP data/address bus,
and the serial interface logic.
Timing reference
The timing reference section generates various clock signals, timeslot counts, and frame
counts required by other sections of the KSW.
The TDM counters section is an offset counter that adds a fixed offset to the master TDM
timeslot counter.
The GSM counters section contains four separate counters:
S GSM sub-timeslot counter.
S GSM sequence counter.
S GSM timeslot counter.
S GSM frame counter.
Switchbound
TDM interface
structure
The switchbound TDM highway interface consists of a series of multiplexers that are
used to select one of four switchbound highways (numbered 0 to 3). The DSP controls
the switchbound multiplexers via highway control logic.
Switchbound highway 0 and the outbound highway are split into local and remote parts.
Local
The local switchbound highway 0 and local outbound highways are active when the KSW
is communicating with highway interface modules in the same shelf.

Block Diagram of the Kiloport Switch (KSW) Module
BACKPLANE
CONNECTOR
SERIAL
INTERFACE TTY INTERFACE
LOGIC
52
MCAP BUS MCAP BUS A 2 FOR
INTERFACE
LOGIC
52
MCAP BUS B
} REDUNDANCY
OTHER KSW CIRCUITRY

MC56001
WATCHDOG 27 MHz
DISTRIBUTION TO
TIMER A CLOCK & REFERENCE
DSP TDM
DSP DATA/ADDRES
CLKS (16.384 MHz, 125 us,

COUNTERS TIMING
REFERENCE 60 ms, AND 6.12 s)
GSM LOGIC B CLOCK & REFERENCE
RESET/
COUNTERS CLKS (16.384 MHz, 125 us,
DISABLE INTERRUPT 60 ms, AND 6.12 s)
SWITCH LOGIC
REMOTE KSWX HWY

HIGHWAY INTERFACE CONTROL
CONTROL
RED LED
GREEN
LED
MUX LOCAL SWITCHBOUND HWY 0

DELAY
MUX
CONNECTION REMOTE SWITCHBOUND
DSP DATA/ADDRES
RAM CONTROL HWY 0
TIME SLOT
INTERCHANGE MUX EXPANSION SWITCHBOUND
(TSI) HWY 1
TIME SLOT
LOOP
BACK
INTERCHANGE
(TSI)
MUX EXPANSION SWITCHBOUND
TIME SLOT
INTERCHANGE HWY 2
(TSI)
FULL–RATE
SUB–RATE
SOURCE 0
SOURCE 1
TIME SLOT
INTERCHANGE
(TSI)
HWY 3
HIGHWAY
MONITOR
DELAY
MUX PARITY
GENERATOR EXPANSION OUTBOUND HWY
OUTBOUND SELECT MUX
LOOP
BACK
TSI MODE MUX

DELAY LOCAL OUTBOUND HWY
THIRD
PARTY REMOTE OUTBOUND HWY
CONFERENCE
MEMORY
FIXED/DYNAMIC
PATTERN PARITY HIGHWAY
REGISTERS GENERATOR MONITOR
+12 V
–12 V
OUTBOUND +5 V
CONTROL
RAM GND
BSS11_Ch3_54

Remote
The remote switchbound highway 0 and remote outbound highways are active when the
KSW is communicating with highway interface modules in remote shelves. This
effectively extends the TDM bus to multiple shelves. In the remote case, the KSW
sends and receives TDM data to and from a remote KSW Extender (KSWXR) in the
same shelf as the KSW.
The remote KSWXR communicates via fibre optic links with a local type KSWXL in the
remote shelf. Local switchbound highway 0 has a delay circuit which adds a fixed 12
timeslot delay. This delay is equal to the delay associated with the KSWX extension
operation, and keeps the local and remote switchbound highways in phase.
The modules on the TDM bus are:
S DRIM.
S MSI.
S XCDR.
S GPROC/GPROC2.
Expansion
switchbound
highways
Expansion switchbound highway 1, 2 and 3 data originates from highway interface
modules associated with other KSWs. These remote highway interface modules send
and receive data between their respective KSWs. Each KSW re-transmits data received
on its switchbound highway 0 (local or remote) to other KSWs via dedicated KSWXE fibre
optic links.
Data is received on switchbound highways 1, 2 and 3 of remote KSWs. This architecture
results in each KSW receiving data from all 1024 timeslots of all expansion highways
connected to the KSW and retransmitting that data on the 1024 timeslots associated with
its own highway interface modules to the other KSWs.
The DSP can write data to any of the four switchbound highways. This allows known
static data patterns to be inserted into any switchbound timeslot, and data can be looped
back to switchbound highway 0 from the TSI section, enabling self diagnostics. When the
KSW is performing self diagnostics, data is compared at two highway monitors, one
before the TSI section and one after the TSI section.
Timeslot
Interchange (TSI)
The TSI section is the main section of the KSW. It switches data from a given timeslot on
one of the four switchbound TDM highways to a given timeslot on the outbound TDM
highway. The TSI section consists of four independent TSI blocks operating in parallel to
support sub-rate switching. Each TSI block switches 16 kbit/s of data.

Block Diagram of 3 Interconnected KSWs
KSW
SWITCHBOUND LOCAL (1024 TSI OUTBOUND HIGHWAY (1024 PORTS)

PORTS)
EACH KSW ROUTES SWITCHBOUND DATA TO BOTH

THE TSI SECTION AND THE EXPANSION OUTBOUND EXPANSION OUTBOUND
HIGHWAY. HIGHWAY IS SENT TO
EACH KSWX E
BSU/RXU SHELF KSWX E
KSWX E
KSW
SWITCHBOUND LOCAL (1024 PORTS) TSI OUTBOUND HIGHWAY (1024 PORTS)
BSU/RXU SHELF
DATA FROM OTHER KSWs
IS SENT TO THE TSI
SECTION (1024 EACH)
KSWX E
TDM DATA IS SENT

TO/FROM KSWX E
KSW ETO KSWX E
KSW
SWITCHBOUND LOCAL (1024 PORTS) TSI OUTBOUND HIGHWAY (1024 PORTS)
ALL EXPANSION SWITCHBOUND DATA

IS SENT (ALONG WITH THE SWITCHBOUND
LOCAL) TO THE TSI FOR SWITCHING
TO THE OUTBOUND HIGHWAY
BSU/RXU SHELF KSWX E
FIBRE OPTIC CABLES KSWX E
BSS11_Ch3_54a

Three-Party
Conference
(TPC) memory
After traffic data leaves the TSIs, it is sent to either the TSI mode multiplexer, which
selects full-rate or sub-rate switching as required, or to the three party conference (TPC)
memory section. The TPC memory operates in real time allowing the KSW to support
any number of three party conference calls.
Fixed/dynamic
pattern registers
The fixed/dynamic pattern registers can generate fixed patterns and a variety of dynamic
patterns that generate tones, data sequences, or dynamic test patterns.
Outbound
selection MUX
The outbound selection multiplexer selects the correct source data to be sent to the
outbound highway. Although referred to as a multiplexer, this section does not contain a
physical multiplexer. Instead, multiplexing is implemented by connecting the outputs of all
the possible data sources together and selectively enabling one of these sources during
each timeslot.
After data is sent from the outbound selection multiplexer, a parity bit is added to the data
before it is placed on the outbound TDM highway. Output from the outbound multiplexer
is sent directly to the remote outbound highway, but data for the local outbound highway
is sent through a delay circuit to keep the remote and local outbound highways in phase.
This delay is 12 timeslots.
Highway monitor
The KSW has two highway monitor sections:
S The switchbound monitor logic which selectively monitors one of the four
switchbound TDM highways at the inputs of the TSI section.
S The outbound monitor logic which monitors the output of the outbound selection
mux.
The DSP uses these monitors for monitoring inbound and outbound data on any timeslot.
When used in conjunction with the various DSP controlled data sources and
fixed/dynamic pattern selection, these monitors allow the KSW to perform extensive self
diagnostics on the TSI section.
Watchdog timer
The watchdog timer ensures that the DSP is functioning normally. The DSP writes to a
memory address that resets the watchdog timer, ensuring that it does not time out. If the
DSP stops running, the watchdog timer times out and causes the red LED on the front
panel to illuminate. An interrupt is also generated and sent to the GPROC via the MCAP
bus. If a DSP fails, the TSI section of the KSW still switches data, but no new path
connections are implemented. This results in existing calls being held while the system is
reconfigured around the failed KSW.

Dynamic Switching
BSC BTS2
MMS0
MMS0
2Mbit/s link
MMS0
2Mbit/s link
0
KSW TSW
FAW FAW 0
MMS1
MMS1
MMS1
B 1 X D X X 1
2 B C X X 2
CE 3 3
4 4
DRIM
D 5 5
A 6 6
MMS0 MMS1 DRCU
31 31
2Mbit/s link Air interface
0 1 2 3 4 5 6 7
BTS1
MSI
FAW 0
1
2 D B C
3
X X X X 4 E
A X E X 5
TSW A
DRIM
6
Air interface
Note: This example shows
DRCU 0 1 2 3 4 5 6 7 E1 links only
31
BSS11_Ch3_55

Interrupt logic
The interrupt logic generates two interrupts to the DSP:
S Interrupt-A prompts the DSP to perform certain periodic tasks such as updating
the watchdog timer and the dynamic pattern registers.
S Interrupt-B, processes alarms such as clock and reference alarms, and parity
alarms.
Serial interface
logic
The serial interface logic supports the TTY interface. This interface is connected to a
dedicated backplane connector port. This port is a buffered RS232 type. The TTY can be
used to control the KSW, monitor KSW operation status, and support KSW diagnostics.
KSW switching
The usable switching capacity of each KSW depends on site hardware and software
configurations because certain modules require a number of ports for their own use. The
KSW is controlled by the local GPROC via the MCAP bus.
Each KSW can switch connections between 1024 inputs and 1024 outputs. However,
total switching capacity can be expanded by interconnecting up to three additional KSWs
via KSWXs.
In this configuration, each KSW has the ability to switch data between 2048 (2 x 1024),
3072 (3 x 1024) or 4096 (4 x 1024) 64 kbit/s input ports and its 1024 outbound ports.
Each KSW has access to all 2, 3 or 4 switchbound highways, although each KSW only
drives its own 1024 port outbound TDM highway.
KSW in a BSC
KSW switching at the BSC is variable. Physical channel mapping on the A interface is
performed for each call, and at every handover.
KSW in a RXCDR
KSW switching in an RXU shelf is fixed. It provides one to one physical mapping
between the traffic to and from the BSC and the traffic to and from the MSC.


BSSC Cabinet Extension and Expansion ISSUE 1 REVISION 2
BSSC Cabinet Extension and Expansion
Purpose
WARNING
The Kiloport Switch Extender (KSWX) module extends the 1024 ports of a KSW in one
BSU or RXU to the TDM highways in another BSU or RXU. It is used when the number
of required peripherals exceeds the capacity of a BSU or RXU shelf.
S A KSWX in expansion mode (KSWXE) connects the KSW to the KSW in a remote
BSU or RXU.
S A KSWX in remote transmit mode (KSWXR) accepts the highway data from a
KSW and sends it to a local receiver.
S A KSWX in local receive mode (KSWXL) accepts the highway data and drives the
TDM bus in the local BSU or RXU, and also provides a clock reference in
multishelf configurations.
Although a KSW is located in a particular BSU/RXU, it is logically connected to the TDM
bus in that BSU/RXU and to the TDM buses in up to 16 other shelves it may be driving.
For each BSU or RXU that a KSW/TSW is driving, two KSWXs are required; one acting
as a remote transmitter attached to the KSW/TSW, the other as a local receiver attached
to the TDM highway in the remote shelf.
NOTE
This description details how KSWX modules work with KSW modules.
However the description is also valid when a TSW is used (normally at a
BTS).
Requirements
The KSWX is fitted in slots U0 to U9 and slots U21 to U28 of the BSU or RXU shelf
assembly, with the following limitations:
S KSWX R must be fitted in slots U2 to U6 and U24 to U28.
S KSWX L must be fitted in slots U0 and U1.
S KSWX E must be fitted in slots U7 to U9 and U21 to U23.

ISSUE 1 REVISION 2 BSSC Cabinet Extension and Expansion
Blcok Diagram of the Kiloport Switch Extender (KSWX)

Module
BACKPLANE CONNECTOR
TDM BUS OUTBOUND (LCL)

INCOMING FIBRE OPTIC TAXI TDM
CAGE OR
FIBRE OPTIC RECEIVER RECEIVER INTERFACE
SYNCHRONIZER TDM BUS SWITCHBOUND
CABLE
(RMT, EXP)
WRITE
READ
OUTGOING FIBRE OPTIC TAXI TDM BUS SWITCHBOUND (LCL)
TDM OR
FIBRE OPTIC TRANSMITTER TRANSMITTER INTERFACE
CABLE TDM BUS OUTBOUND (RMT, EXP)
16.384 MHz CLOCK A

16.384 MHz CLOCK B
FRAME COUNTER
125 us REF A
R/W CONTROL 125 us REF B
CLOCK
8 MHz CLOCK CLK SELECT 60 ms REF A
DISTRIBUTION
60 ms REF B
6.12 s REF A
6.12 s REF B
DELAY
LINE 16.384 MHz FROM MATE KSWX
MUX
16.384 MHz TO BACKPLANE
CLOCK
FAIL MASTER/ MASTER REQUEST FROM MATE
DETECT SLAVE
CONTROL
INCOMING FIBRE OPTIC EDGE LOGIC MASTER REQUEST TO MATE
FIBRE OPTIC RECEIVER DETECTOR
CABLE
(CLKX)
MUX
DECODER 125 us REF TO BACKPLANE
REFERENCE MUX
STATE
DECODER 60 ms REF TO BACKPLANE
MUX
6.12 s REF TO BACKPLANE
ENCODED CLK FROM MATE

ENCODED CLK TO MATE
GREEN SERIAL INTERFACE

BSS SERIAL BUS A
LED MODULE ALARMS
& STATUS
RESET/ BSS SERIAL BUS B
DISABLE MODULE CONTROL
SWITCH
BSS11_Ch3_56

Remote (KSWXR)
Extends the TDM bus to a shelf with no KSW/TSW. This allows a KSW/TSW to switch
data to and from highway interface modules (MSIs and DRIMs) in a shelf with no
KSW/TSW. KSWXR modules are optically connected to KSWXL modules.
Local (KSWXL)
The KSWXL distributes the TDM bus within a shelf and this is received optically from a
KSWX R in another shelf, and distributes clock and reference signals received from a
CLKX. KSWXL modules are optically connected to CLKX modules and can also be
connected to KSWXR modules.

Highway Extension (Remote)
To/from extension cage 5

Cage 0 Fibre optic Cage 1

K K K K K cables
S S S S S K
Remote outbound S
W W W W W
X X X X X W
Remote switchbound X
4 3 2 1 0
0
Remote KSWX
Local Switchbound Local Switchbound
KSW
Local Outbound Local Outbound
BSS11_CH3_57

Expansion
(KSWXE)
Expands the TDM bus by up to four KSW/TSWs to expand switching capacity. KSWXE
modules are optically connected to other KSWXE modules.

Highway Expansion
To/from expansion cage 3

To/from expansion cage 2
Cage 0 Cage 1
Expansion Expansion
Expansion KSWX
Outbound K K K Outbound K K K
S S S S S S
W W W W W W
X X X X X X
Expansion
2 1 0 KSWX 2 1 0
EXP EXP
HWY 1 HWY 1
Local Switchbound Local Switchbound

KSW KSW
Local Outbound Local Outbound
BSS11_Ch3_58

The Clock Extender (CLKX) ISSUE 1 REVISION 2
The Clock Extender (CLKX)
Purpose
WARNING
Laser radiation could be emitted when fibre optic cables are
disconnected. Do not look directly into beams with or without the
use of any optical aids. Radiation can come from either the data
in/out connectors or unterminated fibre optic cables connected to
data in/out connectors.
The Clock Extender (CLKX) module optically distributes the clock and reference signals
generated by the GCLK in the parent shelf to all other shelves at a site.
The extended clock signals are received by a KSWXL in the remote BSU/RXU.
Requirements
The CLKX module is fitted in slots U2 to U7 of the BSU or RXU shelf assembly.
A maximum of six remote shelves can be supported.
CLKX module
The following shows a CLKX module:
BACKPLANE CONNECTOR
FIBRE OPTIC CLOCK

OUTPUTS TO LOCAL
KSWX s
BSS11_Ch3_58a

ISSUE 1 REVISION 2 The Clock Extender (CLKX)
The Clock Extender (CLKX)
Backplane connector
FIBRE OPTIC
DRIVER
TRANSMITTER CIRCUIT
FIBRE OPTIC
DRIVER
TRANSMITTER CIRCUIT
FIBRE OPTIC DRIVER

TRANSMITTER
CIRCUIT
Encoded Clock
References
FIBRE OPTIC (from GCLK)
DRIVER
TRANSMITTER CIRCUIT
FIBRE OPTIC DRIVER

TRANSMITTER CIRCUIT
FIBRE OPTIC DRIVER

TRANSMITTER CIRCUIT
BSS Serial Interface

BSS Serial
Registers Bus A
1. Revision level
2. Board type BSS Serial
3. Slot ID Bus B
BSS11_Ch3_59

Generic Clock (GCLK) Distribution ISSUE 1 REVISION 2
Generic Clock (GCLK) Distribution

In a multishelf site the encoded clock signals from the GCLK, in addition to being
distributed to the other shelves at the site via a CLKX and KSWX, must also be sent
back to the main shelf containing the GCLK. This is necessary to maintain site
synchronization integrity.
The fibre optic cables used to extend the encoded clock signals between shelves must
be of the same length in order to maintain synchronization at the site.

ISSUE 1 REVISION 2 Generic Clock (GCLK) Distribution
Generic Clock (GCLK) Distribution
16 MHz
Encoded clock 6.12 S
GCLK CLKX KSWX L 125 mS
60 mS
Backplane
Backplane
16 MHz
6.12 S
125 mS
KSWX L
60 mS
Shelf 1 Shelf 2
Backplane
Backplane
16 MHz 16 MHz
6.12 S 6.12 S
125 mS KSWX L KSWX L 125 mS
60 mS 60 mS
Shelf 3
Shelf 4
L = KSWX in the local mode Fibre optic cable
BSS11_Ch3_60.

Generic Clock (GCLK) Distribution ISSUE 1 REVISION 2

Appendix A
Student Exercise, Cabinet
Inter-Connection

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Appendix A
Student Exercise, Cabinet Inter-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . i
Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–1
Interconnection Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–2
PART A – KSW and GCLK Expansion/Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–4
PART B – Board Requirement and LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–8
LANX Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–10

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Pre-requisites
Pre-requisites
Before commencing the exercise in this section the student should have an
understanding of:
S All the BSS extension cards and their relevant positions.
S The requirements for both KSW expansion and extension.
S The requirements for GCLK extension.
S The requirements for LAN extension.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory AppA–3–1

Interconnection Exercise ISSUE 1 REVISION 2
Interconnection Exercise
The objective of the exercise is to give students practice in the planning of inter-cabinet
connections.
A. GCLK Extension
B. KSW Extension
C. KSW Expansion
D. LAN Extension
Equipment
A. 1 x BSSC cabinet equipped with 2 x BSU’s each with a single KSW in Slot L27.
The bottom BSU is equipped with a GCLK in Slot L5.
B. 1 x BSSC cabinet, equipped with 2 BSUs, no KSWs or GCLKs are fitted.
Site
Configuration
All the cabinets are to be located at one site, connected on the same Local Area Network
(LAN). The site will therefore be a 4 x BSU Base Station Controller (BSC).
AppA–3–2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2 Interconnection Exercise

PART A – KSW and GCLK Expansion/Extension ISSUE 1 REVISION 2
PART A – KSW and GCLK Expansion/Extension

Using the diagrams and tables provided, complete the following:
A. Draw all the inter-connecting fibre optic cables between the shelves to satisfy the
following conditions:
1. Extend the GCLK to all BSUs.
2. Expand the KSW within the first BSSC cabinet.
3. Extend the KSW function to the BSUs in the second BSSC cabinet from BSU 0.
4. Extend the LAN to all BSUs.
B. Fill in all the shelf tables with the board type, slot position number and the mode of
operation of the KSWX card.
Note:–
BSU 0 is equipped : 1 x KSW Slot L27
1 x GCLK Slot L5
BSU 1 is equipped : 1 x KSW Slot L27

BSU Upper Shelf Layout
RMT RMT RMT RMT RMT EXP EXP EXP LANX LANX PIX/ PIX/ PIX/ DRIX DRIX DRIX DRIX DRIX DRIX EXP EXP EXP RMT RMT RMT RMT RMT LCL LCL
KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX A B
BBBX BBBX BBBX 5 4 3 2 1 KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX
KEY:
A4 A3 A2 A1 A0 A2 A1 A0 B0 B1 B2 B0 B1 B2 B3 B4 A B
Rx
ISSUE 1 REVISION 2
CLKX CLKX CLKX CLKX CLKX CLKX

Rx Clock
EMOTOROLA LTD. 2000

A0 A1 A2 B0 B1 B2 KSWX CLKX
Tx
BSSC Cabinet 1
U28 BSU 1 U28 BSU 0 28 BSU 2
27
U27 U27 26
25
U26 U26 24
23
U25 U25 22
21
U24 20
U24
19
U23 18
U23
17
16
U22 U22
15
14
U21 U21
13
12
U20 U20 11
10
U19 U19 9
8
U18 U18 7
6
U17 U17 5
4
U16 U16 3
2
U15 U15 1
0
U14 U14
U13 28
U13 BSU 3
27
26
U12 U12
25
24
U11

U11 23
22
U10 U10 21
20
U9 U9
19
18
U8 U8 17
BSS11: Base Station Systems – Operational Theory

16
U7 U7 15
14
U6 U6 13
12
U5 U5 11
10
U4 U4 9
8
U3 U3 7
Note: Only upper cage slots shown here. Fill in card
6
U2 U2 5 types and fibre optic connections. Lower slot
4
U1 3 positions are assumed as stated in the exercise
U1
2
KSW and GCLK Expansion/Extension Cable Layout
U0 U0 1
information.
0
AppA–3–5
PART A – KSW and GCLK Expansion/Extension
BSS11_Ch3_AppA_01
PART A – KSW and GCLK Expansion/Extension ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 PART A – KSW and GCLK Expansion/Extension
KSW/GCLK Expansion/Extension
UpperĆShelf Equipage Tables:
BSU 0
BOARD TYPE SLOT No MODE
BSU Layout
BSU 1
BSU 2
BSU 3

PART B – Board Requirement and LAN Extension ISSUE 1 REVISION 2
PART B – Board Requirement and LAN Extension

Answer the following questions.
1. What is the minimum number of KSWX cards required for this configuration?
Answer........................................................
2. What is the minimum number of CLKX cards required?

Answer.......................................................
3. What is the required number of LANX cards when extending with FULL redundancy?
Answer.....................................................

ISSUE 1 REVISION 2 PART B – Board Requirement and LAN Extension

LANX Extender ISSUE 1 REVISION 2
LANX Extender
Using the diagrams and tables provided, complete the following:
A. Fill in the Rotary switch setting table indicating the LANX ID number.
Note:
The rotary switch settings are the same for the redundancy LANX.
B. Draw the inter-connection fibre optic cables showing Tx and Rx connections.
Note:
Only the working LAN is to be shown.

ISSUE 1 REVISION 2 LANX Extender
LANX – Rotary Switch Setting
Enter the setting in the relevant box in each cabinet.
BSU 1
BSU 0
BSSC
Cabinet No 1
BSU 3
BSU 2
BSSC
Cabinet No 2


ISSUE 1 REVISION 2 LANX Extender
LANX Extension
BSSC Cabinet 1
BSU 0 BSU 1
LANX LANX
BSSC Cabinet 2
BSU 2 BSU 3
LANX LANX
Note: Only 1 x LANX card per BSU shown.


Appendix B
Cabinet Inter-Connection Answers

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Appendix B
Cabinet Inter-Connection Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Board Requirement and LAN Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppB–3–4
Part B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppB–3–4

ISSUE 1 REVISION 2

B SU Upper Shelf Layout
RMT RMT RMT RMT RMT EXP EXP EXP LANX LANX PIX/ PIX/ PIX/ DRIX DRIX DRIX DRIX DRIX DRIX EXP EXP EXP RMT RMT RMT RMT RMT LCL LCL
KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX
A B
BBBX BBBX BBBX 543210 KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX KSWX KEY:
A4 A3 A2 A1 A0 A2 A1 A0 B0 B1 B2 B0 B1 B2 B3 B4 A B
Rx
CLKX CLKX CLKX CLKX CLKX CLKX Rx Clock
A0 A1 A2 B0 B1 B2 KSWX CLKX
Tx
ISSUE 1 REVISION 2
EMOTOROLA LTD. 2000

B SSC Cabinet 1
U28 BS U 1 U28 B SU 0 28 B SU 2
27
U27 U27 26
25
U26 U26 24
KSWX RMT A2 23
U25 U25 22
KSWX RMT A1 21
U24 KSWX RMT A0 20
U24
19
U23 18
U23
17
16
U22 U22
15
KSWX 14
U21 U21
13
EXP A0 12
U20 U20
11
10
U19 U19 9
8
U18 U18 7
6
U17 U17 5
4
U16 U16 3
2 KSWX
U15 U15 1
0
LCL A
U14 U14
U13 28
U13 B SU 3
27
26
U12 U12
25
24
U11 U11 23
22
U10 U10 21
20
U9 U9
19

18
U8 U8 17
16
U7 CLKX A0 U7 15
14
U6 U6 13
12
U5 U5
BSS11: Base Station Systems – Operational Theory

11
10
U4 U4 9
8
U3 U3 7
6
U2 U2 5
4
KSWX U1
KSWX 3
U1
LCL A LCL A 2
U0 U0 1 KSWX
0
LCL A
KSW and GCLK Expansion/Extension Cable Layout
AppB–3–1
BSS11_Ch3_AppB_01
ISSUE 1 REVISION 2
AppB–3–2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2
KSW/GCLK Expansion/Extension
Upper-Shelf Equipage Tables:
BSU 0
KSWX 1 LCL
KSWX 21 EXP
KSWX 24 RMT
KSWX 25 RMT
KSWX 26 RMT BSU Layout
CLKX 7 -
LAN 20 -
BSU 1
KSWX 1 LCL
KSWX 21 EXP
LAN 20 -
BSU 2
KSWX 1 LCL
LAN 20 -
BSU 3
KSWX 1 LCL
LAN 20 -
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory AppB–3–3

Board Requirement and LAN Extension ISSUE 1 REVISION 2
Board Requirement and LAN Extension
Part B
Answer the following questions.

1. What is the minimum number of KSWX cards required for this configuration?
Answer.........9..........................................
2. What is the minimum number of CLKX cards required?

Answer.........1..........................................
3. What is the required number of LANX cards when extending with FULL redundancy?
Answer.........8..........................................

ISSUE 1 REVISION 2 Board Requirement and LAN Extension
LANX – Rotary Switch Setting

Enter the setting in the relevant box in each cabinet.
BSU 1
BSU 0
BSSC
Cabinet No 1
BSU 3
BSU 2
BSSC
Cabinet No 2


ISSUE 1 REVISION 2 Board Requirement and LAN Extension
LANX Extension
BSSC Cabinet 1
BSU 0 BSU 1
LANX LANX
BSSC Cabinet 2
BSU 2 BSU 3
LANX LANX
Note: Only 1 x LANX card per BSU shown.


Chapter 4
Horizonmacro Operational Theory

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 4
Horizonmacro Operational Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
BSC–BTS Interconnection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
BSC–BTS Interconnection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Horizonmacro Indoor Introduction and Manual Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Overview of Horizonmacro Indoor and external view . . . . . . . . . . . . . . . . . . . . . . . 4–10
Overview of Horizonmacro Outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Overview of Horizonmacro 12 Carrier Outdoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Cabinet Structure of the Horizonmacro Indoor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Empty cabinet and SURF harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
SURF harness and cabinet attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Top panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Top panel description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Cage Backplane Interface panel harness Assembly (CBIA) . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA cage function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
CBIA backplane function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
CBIA harness function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Interface panel function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Cabinet Door and Hood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Hood function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Securing pins and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Stacking Bracket Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
Indoor temperature control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Overview of indoor temperature control system . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Temperature shutdown sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Indoor fan overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Fan operation and restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Filter sheet option and effect on fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Power Supply Modules (PSMs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Types of PSM and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
PSM location and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Circuit Breaker Module (CBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
Circuit Break Module (CBM) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
Operation of CBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–46
Outdoor cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Overview of structure description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
SURF harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
SURF harness detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50

ISSUE 1 REVISION 2
Top section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52

Top section description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
Krone blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
Earth plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
Blank and expansion plates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
Power supply enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Power supply enclosure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
Alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
Alarms interface board connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
TMS test switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–60
Customer equipment racking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–60
Outdoor cabinet doors and lid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Lid function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
Horizonmacro outdoor temperature control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Temperature control overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Cabinet over temperature control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Temperature sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
Thermal Management System (TMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–66
TMS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–66
Heat exchanger components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–68
TMS functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–70
Horizonmacro outdoor power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
Power supply overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
Power distribution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
AC distribution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–74
DC distribution overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–78
Customer equipment power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
Internal battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
External battery backup connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
Control and Alarm Board (CAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–82
Introduction to the CAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–82
CAB indicators and controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–84
CAB front panel fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–85
CAB control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–86
CAB alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–88
CAB additional functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–90
The Outdoor Power Supply Module (TOPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
TOPSM overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
TOPSM functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
LED display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Protection circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Thermal protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
Control and alarm signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–98

ISSUE 1 REVISION 2
Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100

MicroBCU Power Supply Module (BPSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100
Auxiliary equipment housing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Introduction to the auxiliary equipment housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Auxiliary equipment housing mechanical design . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Temperature control within the auxiliary equipment housing . . . . . . . . . . . . . . . . . . . . . . . 4–104
Temperature control equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
Operation of the temperature control equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
Auxiliary equipment housing as a battery box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–104
External alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
Function of the external alarms interface board . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
External alarms interface board connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–106
Horizonmacro 12 carrier outdoor enclosure structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Introduction to the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Enclosure description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–108
Alarm Interface Module (AIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
Functional description of the AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
AIM connectors and switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–112
Primary ac terminal box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–114
Primary ac terminal box location and function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–114
Fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Introduction to the fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Fan tray description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–116
Operation of the smoke detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–118
Enclosure lighting description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–118
Doors and hood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Door function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Operation of the door locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–120
Hood function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–122
Hood operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–122
Cable entry to the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Cable entry overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Low level cable entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–124
Optional high level cable entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–126
Optional cable shroud and termination bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–128
Overview of the power distribution equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–130
Operation of the power distribution equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–130
AC power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
AC distribution description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
AC circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–132
DC circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–138
DC fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–138
The power control module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–140
Overview of the power control module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–140
Front panel controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–142
Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–144
Alarm inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–144
Alarm output signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–145

ISSUE 1 REVISION 2
The rectifier module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–146

The dc connector panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–148
Description of the dc connector panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–148
Internal battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–150
Overview of the internal battery backup system . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–150
Battery thermal charge compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–152
Horizonmacro digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
MCUF and NIU redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Full size and half size modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Overview locations and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–154
Digital module and CTU connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–156
Main Control Unit with dual FMUX (MCUF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
MCUF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
Capability to replace MCU of M-Cell6 and M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
GPROC KSW and GLCK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–158
Front panel interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–160
Front panel switches and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–162
PIX and GPS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–162
DRAM, flash EPROM and code loading functions . . . . . . . . . . . . . . . . . . . . . . . . . . 4–164
ASIC functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–166
Sync block functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–168
Link to redundant MCUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–170
The Network Interface Unit (NIU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
Overview of NIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–172
NIU command identity number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–174
Control processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–176
NIU/MCUF framing and clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–176
Distance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
Radio Signalling Links (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
T1 NIU need to set link type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–178
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
Overview of T43/BIB-NIU connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–180
NIU to T43 mapping and command ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–181
Fibre Optic Mulitplexer (FMUX) module and FMUX function . . . . . . . . . . . . . . . . . . . . . . 4–184
Overview of FMUX module and internal MCUF FMUX . . . . . . . . . . . . . . . . . . . . . 4–184
FMUX Functional explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–186
Alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module replacement – effect on alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm collection from extension cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–188
Alarm module display presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–190

ISSUE 1 REVISION 2
Horizonmacro RF Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–192

RF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–192
Receive RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
Transmit (Tx) RF hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
Rx/Tx single antenna duplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–194
RF main component explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–196
RF loopback purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
RF loopback hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
RF loopback software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
Description of RF test modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–198
The Compact Transceiver Unit (CTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
Overview of CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
CTU internal boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–200
CTU connectors and reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–202
Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–202
CTU Tx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–204
CTU Rx function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–206
CTU digital processing and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–208
CTU uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–212
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
Overview of frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
Synthesizer Frequency Hopping (SFH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–214
SFH example not through BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–216
SFH example hopping through BCCH carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–216
Base Band frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–218
The Sectorized Universal Receiver Front end (SURF) module . . . . . . . . . . . . . . . . . . . . 4–222
SURF module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–222
Functional description of 1800 SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–224
Functional description of 900 SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–226
Transmit (Tx) blocks overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Tx block overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Transmit block connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–228
Blanking plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
Purpose of blanking plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
Purpose of feedthrough plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–230
The Hybrid Combining Unit (HCU) plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
HCU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
HCU connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–232
The Twin Duplexed Filter (TDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
Overview of TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
TDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–234
Dual band TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
Overview of Dual band TDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
Dual band TDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–236
The Duplexed Combining bandpass Filter (DCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
DCF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
DCF overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–238
The Dual-stage Duplexed combining Filter (DDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240
Overview of DDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240
DDF connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–240

ISSUE 1 REVISION 2
The Cavity Combining Block (CCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242

CCB overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
CCB Control Board (TCB) and set switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
TCB and link redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242
CCB configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–244
CCB functional description and diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–244

Chapter Objectives
S Describe the generic functions of a Base Transceiver Station (BTS) and state the
BSC to BTS connectivity.
S Identify and state the purpose of the Horizonmacro indoor cabinet.
S Describe the functions and simplified operation of the Horizonmacro indoor
cabinet.
S Describe the functions and simplified operation of the Horizonmacro outdoor
cabinet.
S Describe the functions and simplified operation of the Horizonmacro outdoor
auxiliary equipment housing and cable shroud.
S Describe the functions and simplified operation of the Horizonmacro 12 carrier
outdoor cabinet.
S Identify and describe the simplified operation of the Horizonmacro RF modules.

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

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

As the link between the BTS and MS needs to follow the GSM specifications it needs to
be controlled by a dedicated software section. This software controls the Layer 1
physical formatting of the air interface. This process includes configuring of the air
interface links for the GSM Time Division Multiple Access (TDMA) format, formatting the
data in each timeslot on that link, and also helps in controlling the paging and access
grant messages. It processes the signal strength and quality information from the radio
control software, passing it to the BSC. This information is used to make sure the
BTS-MS link is maintained at a good quality level or the MS is handed over to another
cell/BTS.
Static Switch
This section switches the channels containing traffic from the radio sections of the BTS
to the terrestrial connections section, thus connecting the air interface channel with the
rest of the network and eventually to another party. The static switch also routes any
control information sent from entities further up in the network to the correct controlling
software, usually the resident on the control processor. The static switch means that
once it has been initialized it will keep the switching matrix the same all the time, thus
keeping the same connections routed through.
Terrestrial Interface
The terrestrial interface provides the necessary connection to the network via a suitable
1.544Mbit/s T1 link.

Functions of a BTS
Terrestrial Terrestrial
Synchronizing Interface Interface
clock
Site
Control

GSM Call
Processing
GSM
Timeslot GSM Control Software GSM Control Software
Monitoring
Radio Control Software Radio Control Software
Control
Processor RX/TX Modules RX/TX Modules
BSS11_Ch4_01

Control Processor
The control processor is the main processor of the site and can be split into three main
areas:
S Site Control
the site at power up as well as reporting any faults or operational problems back to
the controlling BSC further up in the network.
S GSM Call Processing
Although the GSM control software looks after the link to MS from a very basic
level (i.e. Layer 1 process implementing the physical air interface link). The GSM
call processing’s role is that of call management. This process is used to interface
GSM control messaging from the BSC to the GSM control software and to activate
the allocated timeslot ready for the call to take place.
S GSM Timeslot Monitoring
The GSM timeslot monitoring process manages the air interface timeslot usage,
keeping a database of which timeslots are being used and for what purpose,
recording the interference levels on each idle timeslot, prioritizing them for future
use. Upon a request for a call, this process allocates the best available timeslot,
dependant on interference level.
Synchronizing clock
As all the above processes need specific and accurate timing signals, each BTS will be
equipped with a clock to make sure everything is synchronized.


BSC–BTS Interconnection Requirements ISSUE 1 REVISION 2
BSC–BTS Interconnection Requirements
Overview
The BSC–BTS interconnection is provided by 64kbit/s timeslots on 2 Mbit/s links. These
2 Mbit/s links are interfaced at the BSC by using the terrestrial interface boards.
Terrestrial interface boards can interface two independent 2 Mbit/s links with each 2
Mbit/s link, providing 31 usable 64 kbit/s timeslots. The first timeslot being used by the
interfaces to synchronize the link as well as provide basic error detection.
To calculate the required number of 64 kbit/s timeslots required between a BSC and BTS
site, the site must be viewed as consisting of its own equipment and also the equipment
at any sites that are connected to it. However, the amount of 64 kbit/s timeslots to a BTS
site must always be calculated so the interconnection feature can be planned.
In the GSM transmission system, the speech data between the BSC and BTS is encoded
into 16 kbit/s channels using the GSM defined format. As the E1 link utilizes 64 kbit/s
timeslots, using sub-rate multiplexing can be allocated up to 4 X 16 kbit/s channels per
timeslot. Each active radio will have, at a BTS site, an associated Receive / Transmit
Function (RTF) to send the speech data back to the BSC and the rest of the network.
Each RTF has data from 8 timeslots on the air interface. Therefore, it requires 2 x 64
kbit/s timeslots on the E1 link to support its traffic data.
The E1 link must also carry control informaton to and from a BTS site using a Radio
Signalling Link (RSL), as described in section 3. Each BTS site will require a minimum of
1 LAPD signalling link, utilising 1 x 64kbit/s timeslot or 1 x 16kbit/s channel.

ISSUE 1 REVISION 2 BSC–BTS Interconnection Requirements
BSC-BTS Interconnection Requirements
0 SYNC
To synchronise link
and provide error protection
1 RSL
2
To provide a signalling
link from BSC to BTS
3
E1 = 32 x 64 kbit/s
28 RTF1
29 RTF1 Traffic from/to the

BSC link. TCH is 16 kbit/s
4 x TCH per timeslot.
30 RTF0 2 per radio to give 8 tch
from the air interface
31 RTF0
BSS11_Ch4_02

BSC–BTS Interconnection Configuration ISSUE 1 REVISION 2
BSC–BTS Interconnection Configuration

In GSM each BTS connected to a BSC requires a minimum of 1 RSL and sufficient RTFs
for the radios located at the site. This remains a requirement even if the BTS is not
directly connected to the BSC; in the case of daisy chained BTSs for example. The total
number of E1 link timeslots containing information required by any BTS site must equal
timeslots containing information for that site, plus timeslots containing information for all
other sites connected to it.

ISSUE 1 REVISION 2 BSC–BTS Interconnection Configuration
BSC–BTS interconnection configuration
BSC BTS1 BTS2 BTS3
0 0 0 SYNC
SYNC SYNC
1 RSL1 1 1 RSL3
RSL2
24 RTF3
25 RTF3
26 RSL3
27 RTF2 27 RTF3
28 RTF2 28 RTF3
29 RSL2 29 RSL3
30 RTF1 30 RTF2 30 RTF3
31 RTF1 31 RTF2 31 RTF3
BSS11_Ch4_03

Horizonmacro Indoor Introduction and Manual Definition ISSUE 1 REVISION 2
Horizonmacro Indoor Introduction and Manual Definition
Overview of
Horizonmacro
Indoor and
external view
The Horizonmacro Indoor is a six carrier Base Transceiver Station (BTS) cabinet,
operating in GSM standard frequencies (GSM/EGSM900 and DCS1800).
This manual is for the indoor version of the equipment.
Indoor cabinets operate from either an isolated positive earth (–48 V dc), negative earth
(+27 V dc), or nominal 230 V ac single phase. Cooling is provided by circulation fans
located in the bottom of the unit.
This section is designed to give the reader a basic understanding of how components
interconnect.

ISSUE 1 REVISION 2 Horizonmacro Indoor Introduction and Manual Definition
External view of a standard cabinet with hood cover
BSS11_Ch4_04

Overview of Horizonmacro Outdoor ISSUE 1 REVISION 2
Overview of Horizonmacro Outdoor

The Horizonmacro outdoor is a six carrier Base Transceiver Station (BTS) cabinet,
operating in GSM standard frequencies (GSM/EGSM900 and DCS1800).
This manual is for the outdoor version of the equipment only.
Outdoor cabinets operate from nominal 110 V single phase or nominal 230 V, single or
three phase, ac supply. Cabinet temperature control is provided by a Thermal
Management System (TMS) located in the bottom of the unit.
This section is designed to give the reader a basic understanding of the equipment.

ISSUE 1 REVISION 2 Overview of Horizonmacro Outdoor
External view of Horizonmacro outdoor cabinet
BSS11_Ch4_05

Overview of Horizonmacro 12 Carrier Outdoor ISSUE 1 REVISION 2
Overview of Horizonmacro 12 Carrier Outdoor

This section is designed to give the reader a basic understanding of the Horizonmacro 12
carrier outdoor equipment.
The Horizonmacro 12 carrier outdoor is a one to twelve carrier Base Transceiver Station
(BTS), operating at GSM standard frequencies (GSM/EGSM900 and DCS1800). The
enclosure can contain either one (for six carrier) or two (for twelve carrier) Horizonmacro
indoor BTS cabinets.
The enclosure operates from a nominal 230 V, single phase or three phase ac supply.
Temperature control within the enclosure is provided by two Heat Management Systems
(HMS), one located on the inside of each enclosure door.

ISSUE 1 REVISION 2 Overview of Horizonmacro 12 Carrier Outdoor
External view of the Horizonmacro 12 carrier outdoor

enclosure
BSS11_Ch4_06

Cabinet Structure of the Horizonmacro Indoor ISSUE 1 REVISION 2
Cabinet Structure of the Horizonmacro Indoor

The BTS cabinet consists of a main cage and a top panel.
The main cage contains the following equipment:
S A micro Base Control Unit (mBCU), located in the lower right portion of the
cabinet. This contains master and optional redundant digital modules:
Fibre Optic Multiplexer (FMUX).
Main Control Unit with dual FMUX (MCUF).
Network Interface Units (NIUs), four in total.
An alarm board (no redundancy option).
One or two (for redundancy) mBCU Power Supply Modules (BPSMs).
S Up to three Power Supply Modules (PSMs) and one circuit breaker module
(CBM) in the upper right portion of the cabinet. The PSMs are load sharing, with
the third PSM providing optional redundancy.
S Up to six Compact Transceiver Units (CTUs), located in the left portion of the
cabinet.
S Fan modules placed in the bottom of the cabinet, two 2-Fan modules and
one 4-Fan module.
The top panel contains the following equipment:
S RF modules, comprising transmit (Tx) blocks, and a receive (Rx) module, the
Sectorized Universal Receiver Front-end (SURF).
S Interface panel for customer power and communications connectors.

ISSUE 1 REVISION 2 Cabinet Structure of the Horizonmacro Indoor
Filled cabinet view with maximum number of modules

installed
RF MODULES POWER SUPPLY AND

ONE SURF
(Rx) CIRCUIT BREAKER
THREE Tx BLOCKS
(DCFs SHOWN AS
EXAMPLE) THREE PSMs
CIRCUIT
BREAKER
MODULE (CBM)
SIX TRANSCEIVERS
(CTUs)
DC POWER IN
AC POWER IN
INTERFACE
PANEL
CONNECTORS
T43/BIB
DIGITAL
MODULES
ALARM BOARD
TWO 2-FANS. MCUF
TEMPERATURE FMUX/NIU/BPSM
CONTROL SYSTEM
ONE 4-FAN.
CABINET STRUCTURE
Further information is detailed in the later technical description chapters.

Empty cabinet and SURF harness ISSUE 1 REVISION 2
Empty cabinet and SURF harness
SURF harness
and cabinet
attachment
The SURF harness is fitted on the back wall of the cabinet, as shown in the diagram
opposite. The chassis of the SURF harness supports the SURF module.
The SURF harness provides:
S Three connectors to the SURF, for RF and power.
S One RF connector to each CTU, consisting of three inputs, one each for Rx1, Rx2
and RF loopback test. The RF connectors are free floating to ensure fitting of CTU
modules.
S One connector to the backplane, for power from the PSMs.

ISSUE 1 REVISION 2 Empty cabinet and SURF harness
Empty Horizonmacri Indoor cabinet view with installed

SURF harness
SURF HARNESS
EARTH CABLE FOR MAIN CAGE
For clarity, the SURF harness cables are not shown BSS11_Ch4_08

Empty cabinet and SURF harness ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Empty cabinet and SURF harness
SURF harness view with connectors indicated
SLOT FOR SURF

MODULE
Rx2 X 6
RF LOOPBACK X 6
Rx1 X 6
THREE CONNECTORS
TO SURF
POWER CONNECTOR TO
BACKPLANE
CTU5
CONNECTORS TO EACH
CTU
CTU0
Rx1
LOCATING PINS
RF LOOPBACK
TEST PORT
Rx2 BSS11_Ch4_09

Top panel ISSUE 1 REVISION 2
Top panel
Top panel
description
The top panel provides:
S A basket to hold up to three Tx blocks. This includes three holes to enable
connection of CTU Tx cables to the underside of each Tx block. The holes also
allow cooling of the Tx blocks from underneath.
S A slot for insertion of the SURF module.
S A location hole for the interface panel.
S An area for ventilation purposes above the PSMs.
S A hole for fibre optic extension cables from the MCUF FMUX to an FMUX of
another cabinet.

ISSUE 1 REVISION 2 Top panel
Top panel view with major features labelled
SLOT FOR SURF MODULE
LOCATION HOLE
FOR INTERFACE
PANEL
BASKET TO HOLD
THREE Tx BLOCKS
VENTILATION PANEL
HOLE FOR ONE Tx BLOCK (LOCATED ABOVE PSMs)
CTU CONNECTIONS CABLE HOLE FOR FIBRE
OPTIC EXTENSION CABLES
BSS11_Ch4_10

Cage Backplane Interface panel harness Assembly (CBIA) ISSUE 1 REVISION 2
Cage Backplane Interface panel harness Assembly (CBIA)
CBIA overview
The CBIA provides a platform for module installation and power and digital signal
interconnection to cabinet modules. The CBIA consists of:
S The main cage - providing compartments for fans, CTUs, digital modules, BPSMs,
PSMs and CBM. The digital modules and BPSMs are housed in an area called
the µBCU, which is physically part of the main cage.
S The backplane - which routes power and signals for all cage modules and power to
the SURF.
S The harness - which links the backplane to the interface panel.
S The interface panel - which contains T43/BIB and the required power and
communication connectors.
CBIA cage
function
The main cage holds modules and supports the backplane. Each compartment has
appropriate sliders for insertion of the modules. The diagram opposite shows the module
compartments of the cage.

ISSUE 1 REVISION 2 Cage Backplane Interface panel harness Assembly (CBIA)
CBIA cage function and diagram
MAIN CAGE
POWER SUPPLY MODULES
(PSMs)
CIRCUIT BREAKER MODULE
HALF SIZE DIGITAL

MODULES (FMUX,
FULL SIZE NIUs AND BPSM)
TRANSCEIVERS (CTUs) DIGITAL
MODULES
(MCUFs
AND
ALARM)
HALF SIZE DIGITAL
MODULES (FMUX,
NIUs AND BPSM)
2-FAN 2-FAN 4-FAN
HOLES IN BACK PANEL OF CAGE FOR

BACKPLANE FAN CONNECTORS BSS11_Ch4_11

CBIA backplane
function
The backplane is a multilayered printed circuit board with attached connectors on front
and back. The backplane:
S Routes power and digital signals throughout the cabinet.
S Provides connectors for the harness cables linking to the interface panel.
S Provides connectors for plug in modules.
S Provides power to the SURF harness, when the main cage is inserted into the
cabinet.
S Provides a connector for the door switch cable.
S Provides connectors for three heat sensors in the main cage above the CTUs.
The figure opposite shows the CBIA harness linking the interface panel and the
backplane at the rear of the main cage. Each backplane harness connector is identified.

Backplane and harness view including door switch and

heat sensors
INTERFACE
DOOR SWITCH
PANEL
NIU to T43/BIB
THREE HEAT
J21
SENSORS
DOOR SWITCH
CONNECTOR J55
EXTERNAL SIX CTU

ALARMS J23 CONNECTOR
RTC J32 HOLES FOR
SURF
ICS J26 HARNESS
POWER
GPS J22 PIX J25
CONNECTOR
FOR SURF
HARNESS
BSS11_Ch4_12

CBIA harness
function
The harness provides cables to link connectors on the backplane with connectors on the
underside of the interface panel.
Interface panel
function
The interface panel provides all connection points to the required power sources and
telecommunications links. All connectors are linked to the backplane via the CBIA
harness. Plastic connector covers, supplied by Motorola, keep unused connectors
protected from damage by static or foreign matter, and should be retained.

Locations of the interface panel connectors
T43/BIB DC POWER
INPUT
VENTILATION
GRID
GPS
CCB
AC POWER
PIX 0 SOCKET INPUT
PIX 1
ICS
EXTERNAL ALARMS BSS11_Ch4_13

Cabinet Door and Hood ISSUE 1 REVISION 2
Cabinet Door and Hood
Door function
The cabinet is fitted with a door and a hood. The hood can be replaced by an optional
stacking bracket.
The door has the following functions:
S Protects modules from damage.
S Ensures correct air ventilation.
S Provides EMC shielding.
The door has a ventilation grid with internal honeycomb grid, a vertical aluminium air
baffle, and a horizontal door stop bracket. The door stop bracket enables the door to
open to 95 or 130 degrees.
The lock is a trigger latch, opened (if unlocked) by pressing the middle button. There is
also a door alarm bracket, to depress the cabinet door switch.

ISSUE 1 REVISION 2 Cabinet Door and Hood
External and internal view of the cabinet door
EXTERNAL VIEW INTERNAL VIEW

DOOR STOP
BRACKET
DOOR ALARM
BRACKET
HONEYCOMB VERTICAL AIR

VENTILATION VENTILATION BAFFLE
GRID
TRIGGER
LATCH
Both sides of the cabinet door BSS11_Ch4_14

Cabinet Door and Hood ISSUE 1 REVISION 2
Hood function
The hood has the following functions:
S Protects cables and cabinet top.
S Allows easy transition to stacking bracket.
Securing pins
and removal
The hood is secured by four pins located on the cabinet. The pins are removed if the
hood is to be replaced by a stacking bracket.
The hood can be easily lifted off the cabinet by pulling on the top back lifting edge, as
shown in the diagram opposite.

ISSUE 1 REVISION 2 Cabinet Door and Hood
Top view of hood as seen from the front of the cabinet
TOP BACK
LIFTING EDGE

Stacking Bracket Function ISSUE 1 REVISION 2
Stacking Bracket Function

The stacking bracket has two prime functions:
S To enable a second cabinet to be stacked on top of the first cabinet.
S To contain CCBs in a dedicated optional CCB basket.
The stacking bracket is fixed to the top of the cabinet by eight M8 screws. If the stacking
bracket is replacing a hood, then the four hood securing pins must first be removed to
accommodate four of the stacking bracket screws. A second cabinet may be attached on
top of the stacking bracket by four M10 screws.
The CCB basket is fitted only if CCBs are required. The CCB basket is removable, to
enable access for SURF module replacement.

ISSUE 1 REVISION 2 Stacking Bracket Function
Stacking bracket with CCB basket installed
M10 HOLES (4) FOR TOP CABINET

ATTACHMENT (IF REQUIRED)
REAR OF
BRACKET
CCB BASKET
(IF REQUIRED)
M8 HOLES (8) FOR
DETACHABLE BOTTOM CABINET
CCB BASKET BAR ATTACHMENT.
BSS11_Ch4_16

Stacking Bracket Function ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Stacking Bracket Function
Two stacked Horizonmacro indoor cabinets with front

covers attached to the two stacking brackets
Stacking bracket
front cover
Stacking bracket
front cover
BSS11_Ch4_17

Indoor temperature control system ISSUE 1 REVISION 2
Indoor temperature control system
Overview of
indoor
temperature
control system
The cabinet temperature is kept within normal operational limits by fans. The fans draw
air from underneath the cabinet, and expel it through the door and top cabinet vents.
The speed of each fan is controlled by a heat sensor mounted on the fan hub.
If the cabinet overheats, a temperature sensor provides a warning. Dual sensors set at a
higher threshold temperature activate the cabinet PSMs shutdown. The cabinet is
restarted when the sensors are reset by a substantial fall in temperature.
CTUs also have:
S An internal 4 dB power reduction response to overheating.
S An internal total shutdown response to overheating.
Both the CTU responses provide a second layer of cabinet protection independent of the
cabinet heat sensors.
Temperature
shutdown
sensors
The three cabinet temperature sensors are located above the CTU compartment and
consist of the following:
S One 70 _C sensor provides a cabinet overtemperature alarm when the cabinet
temperature exceeds planned level. The alarm is processed by the alarm board
and MCUF, and sent to the OMC via the BSC.
S Two 85 _C sensors shut down the PSMs to protect the cabinet equipment from
heat damage. Both sensors must detect excess temperature for the shutdown to
take place; this reduces the risk of an unnecessary shutdown. No prior notification
of shutdown is given to the OMC, except for the original 70 _C sensor alarm. This
is because the MCUF and CTUs immediately lose power and functionality.
Cabinet restart
after shutdown
The cabinet is restarted when the two 85 _C temperature sensors reset at 55 _C. This
re-establishes an earth point for the PSM internal detectors connected to the cabinet
heat sensors, which then reactivate the PSM outputs. The MCUF then reboots as a
normal power up.

ISSUE 1 REVISION 2 Indoor temperature control system
The two types of indoor fan units
2-FAN
4-FAN
RESTART BUTTONS
(ONE PER FAN)
SLIDE LATCH FOR

MODULE REMOVAL
The 2 types of fan unit BSS11_Ch4_18

Indoor temperature control system ISSUE 1 REVISION 2
Indoor fan
overview
The indoor cabinet operating temperature is maintained by three sets of fans:
S One 4-fan unit (referred to as FAN0), located in front and beneath the digital
modules.
S Two identical 2-fan units, (referred to as FAN1 and FAN2), located beneath the
CTUs.
Fan operation
and restart
The fans run continuously, and respond to temperature changes to ensure adequate flow.
Each fan has a restart button, for use if a fan has stopped or cannot start. Each restart
button is marked FRONT or REAR to identify the appropriate fan.
Filter sheet
option and effect
on fans
Filters are an option and not essential in a clean environment. The single filter is
mounted under all the fan units. If clogged, fan airflow may be reduced, straining fan
motors and increasing fan noise.

ISSUE 1 REVISION 2 Indoor temperature control system

Power Supply Modules (PSMs) ISSUE 1 REVISION 2
Power Supply Modules (PSMs)
Types of PSM
and overview
There are two types of dc Power Supply Modules (PSMs):
S Nominal +27 V (negative earth input).
S Nominal –48 V (positive earth input).
There is one type of ac PSM:
S Nominal 230 V.
All PSMs have the same external appearance and are located in the same positions.
Different types are identified only by front panel labels.
The PSMs are fed from a backplane connector, and use pulse width modulation to
generate output supply. A front panel switch disables the output, reducing the input
current as shown in Table 4-1.
Table 4-1 Input currents for Power Supply Module

Type of PSM Output voltage Input current Input load when
full load full load output switch off
+27 V nominal dc +27 V 32 A 1A
–48 V nominal dc +27 V 18 A 0.5 A
230 V nominal ac +27 V 3.75 A 0.1 A
NOTE
There are several manufacturers of the PSMs. Each is fully compatible with
the same type of PSM of a different manufacturer.
PSM location and

redundancy
The PSMs are located above the digital cage and circuit breaker module. There are
three slots, two for maximum cabinet configuration, one for redundancy. Supply capability
is shown in Table 4-2. Note that only two CTUs are powered by the first PSM, because
of power required by the rest of the cabinet.
Table 4-2 Power Supply Module options

Number of Capability of supply
modules fitted
1 Complete operation of cabinet for up to two CTUs.
2 Complete operation of cabinet for up to six CTUs.
3 Redundancy and power load sharing (further enhancing
reliability by reducing temperature of operation).

ISSUE 1 REVISION 2 Power Supply Modules (PSMs)
Power Supply Module (PSM) view with LEDs identified
AIR VENTS ON
ENTIRE TOP AND
BOTTOM PANELS
GREEN LED
ACTIVE
RED LED
ALARM
OUTPUT DISABLE
SWITCH
M4 MODULE ATTACHMENT
SCREWS
PSM FRONT PANEL

BSS11_Ch4_19
Power Supply Module (PSM) LEDs function
Table 4–3 Power supply module LEDs function.

Green LED Red LED Indication
ACTIVE ALARM
OFF OFF 1. Cabinet power supply off, or
2. Output disable switch off, or
3. Module not connected.
ON OFF Normal operation.
OFF ON Alarm condition with module unable to supply power .
ON ON Internal problem (such as over temperature), but still
able to maintain supply.
BSS11_Ch4_19a

Power Supply Modules (PSMs) ISSUE 1 REVISION 2
Functional
description
The BCU Power Supply Module (BPSM) provides regulated dc power to the backplane
for BCU modules. Each BPSM can provide power for:
S One MCUF.
S One FMUX.
S Two NIUs.
S The alarm board (which also uses the redundant BPSM).
A second BPSM must be installed in the BCU, if additional redundant boards (MCUF,
two NIUs, and FMUX) are required.
Internal BPSM circuits monitor the +3.3 V, +5 V, +12 V and –12 V outputs for the
following purposes:
S Over-voltage protection - provides shutdown if output voltage exceeds 1.1 to 1.2
times the rated output.
S Over-current protection - maximum output current has the following limits:
– 1.1 to 1.8 times full load rating of +3.3 V output.
– 1.1 to 1.8 times full load rating of +5 V output.
– 1.25 to 2 times full load rating of +12 V and –12 V outputs.
Circuit protection
Additional internal circuitry protects the BPSM:
S Input dc reverse polarity protection, achieved by an input series diode.
S Thermal protection by automatic BPSM shutdown. Normal BPSM operation
resumes after BPSM temperature returns to a safe level.
S A 10 Amp fuse is located near the backplane connector.
LED display
An active (Green) LED mounted on the front of the BPSM is on when all output voltages
are present and within specified limits. A functional diagram is shown in NO TAG.

ISSUE 1 REVISION 2 Power Supply Modules (PSMs)
BCU Power Supply Module (BPSM) view
BACKPLANE CONNECTOR
GREEN LED
BSS11_Ch4_20
Functional block diagram of BPSM
BACKPLANE CONNECTOR
VOUT (+5 V)
VOUT (+12 V)
GREEN
LED POWER VOUT (–12 V)
CONVERTER AND
SYSTEM MONITOR VOUT (3.3 V)
VIN (+27 V)
BSS11_Ch4_20a

Circuit Breaker Module (CBM) ISSUE 1 REVISION 2
Circuit Breaker Module (CBM)
Circuit Break
Module (CBM)
overview
The CBM provides circuit protection and manual isolation for all parts of the cabinet,
except the PSMs. The CBM is located above the BCU and below the PSMs. The
honeycomb casing permits cabinet ventilation through the module.
The CBM is connected to the backplane, providing isolator switches and overload
protection for the equipment indicated in the diagram opposite.
Operation of
CBM
Power for each module is supplied via the appropriate circuit breaker switch. Overload of
any circuit results in appropriate front panel circuit breaker button tripping to the off (out)
position. The button can be pressed to the on (in) position when overload problem has
been corrected.
CTUs, BPSMs, CCBs, SURF and fans can be isolated by pressing and releasing the
appropriate button to the off (out) position. Power is restored by pushing the appropriate
button to the on (in) position.

ISSUE 1 REVISION 2 Circuit Breaker Module (CBM)
CBM view with circuit breaker buttons identified
BACKPLANE CONNECTOR
HANDLE-BAFFLE
SCREWS
7A
FANS
12 A
4A 2A 7A
6 CTUs (0 TO 5)
CCB (0 AND 1) SURF BPSMs (A AND B)
FRONT VIEW
BSS11_Ch4_21

Outdoor cabinet structure ISSUE 1 REVISION 2
Outdoor cabinet structure
Overview of
structure
description
The outdoor cabinet is shown on page 4-49. The cabinet is designed for minimum
maintenance and maximum ease of module replacement and has access only from the
front and top.
This chapter describes the cabinet structure and the inner connections to assist
understanding the cabinet functions. There should be no need to dismantle the cabinet
beyond Field Replaceable Unit (FRU) level.
The cabinet structure components are explained in the following sections:
SURF harness
The SURF harness shows connections between the SURF and the backplane and
transceivers. These are not normally visible in a fully equipped cabinet.
Top section
The top section holds the Tx blocks, the interface panel, the SURF module, the number 1
ac distribution box and an ac outlet socket.
Cage Backplane Interface panel harness Assembly (CBIA)

The CBIA describes the main cage backplane connections between modules, the
interface panel and the harness from the backplane to the Interface panel connectors.
These are not normally accessible in a fully equipped cabinet.
Power supply enclosure

This section shows the location of the Power Supply Unit (PSU) and the racking for
customer equipment.
Doors, lid and cable shrouds

These provide security and environmental protection. The doors and lid also assists in
correct thermal management.
Backplane
The cabinet is designed to enable all possible RF and digital module combinations to be
served by the same backplane. This removes need for any module-to-module cabling,
apart from the Tx cables from the transceivers to the Tx blocks, and external
attachments.

ISSUE 1 REVISION 2 Outdoor cabinet structure
Front view of the cabinet with maximum number of

modules installed
PSMs
DC CIRCUIT No2 AC
BREAKERS DISTRIBUTION
BOX
DIGITAL
CTUs TOPSMs INTERNAL TMS
MODULES
BATTERY
TRAY
The main components visible from the front are identified.

The doors and TMS front cover have been omitted for clarity. BSS11_Ch4_22a

SURF harness ISSUE 1 REVISION 2
SURF harness
SURF harness
detail
The SURF harness is fitted on the back wall of the cabinet. The chassis of the harness
supports the SURF module.
The SURF harness provides:
S Three connectors to the SURF, for RF and power.
S One RF connector to each CTU, consisting of three inputs, one each for Rx1, Rx2
and RF loopback test, as shown opposite. The RF connectors are free floating to
ensure fitting of CTU modules.
S One connector to the backplane, for power from the PSMs.

ISSUE 1 REVISION 2 SURF harness
Empty cabinet view with installed SURF harness
SURF HARNESS
BSS11_Ch4_23
The SURF harness cables have been removed for clarity.

Top section ISSUE 1 REVISION 2
Top section
Top section
description
The top section provides:
S A basket to hold up to three Tx blocks. This includes six holes to enable
connection of CTU Tx cables to the underside of each Tx block. The holes also
allow cooling of the Tx blocks from underneath.
S A slot for insertion of the SURF module.
S A location hole for the interface panel. The interface panel is positioned into the top
section from underneath and fixed from the top.
S Cable holes for fibre optic extension cables (from the MCUF FMUX to an FMUX of
another cabinet), and alarm cables.
S Earth plates fitted to the ends of the top wrap. The earth plate contains the RF
cabling, which allows the connection of external antennas to internal RF cabling, at
the cable entry side . A blank plate or expansion plate is fitted at the opposite end
of the top wrap.
S A panel for the power supply unit dc output and external battery cables.
S A location hole for the number 1 ac distribution box (the power supply input
connection and switching). The number 1 ac distribution box slots into the top
section from underneath.
S The top section also houses krone blocks and an ac outlet socket.
Krone blocks
Two krone blocks are mounted on the top panel as an interface for:
S Customer alarms.
S Customer communications.

ISSUE 1 REVISION 2 Top section
Top section of the cabinet with the major features labelled
LEFT EARTH PLATE

(RF CABLE OMITTED SURF MODULE
FOR CLARITY)
CABLE HOLE FOR FIBRE
OPTIC EXTENSION CABLES
INTERFACE PANEL CABLE GUIDE
PANEL FOR DC OUTPUT

AND EXTERNAL
BATTERY CABLES
CABLE GUIDE
THREE Tx
BLOCKS
KRONE BLOCKS
BLANK PLATE (RIGHT
EARTH PLATE OR
EXPANSION
NUMBER 1 AC AC OUTLET PLATE OPTIONAL)
DISTRIBUTION BOX SOCKET
BSS11_Ch4_24

Top section ISSUE 1 REVISION 2
Earth plates
An earth/connector plate is fitted to the cable entry side of the cabinet. The earth plate is
supplied with:
S Three N-type to 7/16 bulkhead cables, (for connection between earth plate and
SURF module).
S Three 7/16 to 7/16 bulkhead cables, (for connection between earth plate and Tx
block ANT connector).
The cabinet earth plate has the following functions:
S Provision of the main cabinet earth connection.
S Provision of a connection point for customer antennas.
S Weatherproof pass-through for: ac power, external battery and customer
communications cables.
Blank and
expansion plates
A blank or expansion plate is fitted to the opposite end of the cabinet. The expansion
plate provides:
S Weatherproof pass-through for: ac power, external battery and customer
communications cables.
S RF cable pass-through for multiple cabinet sites.
The expansion plate is supplied with the cable pass-throughs sealed by blanking plugs.
The plug must be removed from each pass-through before the it can be used.

ISSUE 1 REVISION 2 Top section
Cable entry side earth plate
DC IN
RX 1B EARTH STUD
RX 0B
RX 2A
RX 1A RX 2B
TX 2
AC IN
TX 1
TX 0
RX 0A
COMMS
BSS11_Ch4_25
Layout of the left earth/connector plate viewed from inside the top section
(the layout for the right plate is a mirror image of this). The six permanently
connected RF cables are omitted for clarity.
Right side expansion plate
RF PASS-THROUGH
FIVE CABLE GLAND
EARTH CABLE
PASS-THROUGH
BATTERY BACKUP CABLE

PASS-THROUGH
FIBRE OPTIC
EXTENSION CABLE
PASS-THROUGH
(not visible)
RUBBER
AC CABLE GLAND HOUSING
PASS-THROUGH
BSS11_Ch4_25a
Left side expansion plate is a mirror image of right side plate.

Power supply enclosure ISSUE 1 REVISION 2
Power supply enclosure
Power supply
enclosure
overview
The power supply enclosure contains:
S The Power Supply Unit (PSU), complete with up to three TOPSMs.
S An alarm interface board to connect PSU and TMS alarms.
S The door open alarm microswitch, located in the upper left corner.
S Six U height of standard 19 inch rack space for customer equipment.
Power supply
unit
The PSU contains:
S Up to three TOPSMs for input power conversion.
S Minimal battery backup.
S Circuit isolation and protection devices.
S A control and alarm board.

ISSUE 1 REVISION 2 Power supply enclosure
Isometric and front view of the power supply enclosure
DOOR OPEN ALARM

MICROSWITCH
CUSTOMER
EQUIPMENT
ÏÏÏÏÏÏÏ
RACKING
ÏÏÏÏÏÏÏ
ÏÏÏÏÏÏÏ
SPACE FOR
CUSTOMER
ÏÏÏÏÏÏÏ EQUIPMENT
ÏÏÏÏÏÏÏ
ALARMS
INTERFACE
BOARD
TOPSMs IN
PSU
BSS11_Ch4_26

Alarms interface
board
The alarms interface board provides a connection point for alarms generated by the
auxiliary equipment housing, PSU and TMS. The alarms are then routed to the external
alarm connector of the interface panel, with the exception of the TMS fan fail, which is
routed through the main cage backplane (fan 0 connector) to the alarm module.
The alarms interface board also houses the TMS test switches.
Alarms interface
board
connectors
The function of each alarms interface board connector is described below:
PL 1 Connects to the auxiliary equipment housing alarm outputs.

PL 2 Connects to the interface panel PIX 0 connector, to enable
remote initiation of battery tests.
PL 3 Connects to the interface panel external alarms connector.
PL 4 Connects to the PSU control interface board.
PL 5 Connects TMS test inputs and alarm outputs.
PL 6 Connects TMS fan alarm outputs to main cage backplane.
PL 7 Connector for smoke alarms (not in use).
PL 8 Connector for door microswitches.

Layout of the alarms interface board
PL8
PL1 PL2 PL3
TEST OVERRIDE
(SW1)
HEATER ON
(SW2)
INTERNAL FANS
(SW3)
EXTERNAL FANS
(SW4) PL4
PL5
BSS11_Ch4_27
PL7 PL6

TMS test
switches
Four TMS test switches are mounted on the alarms interface board. Operation of the
override switch causes the TMS control board to set the fans to minimum speed and the
heaters to off, regardless of environmental conditions. The override switch must be held
to enable further test steps. Subsequent operation of the individual fan switches will set
the corresponding fans to maximum speed.
Operation of the heater switch sets the heaters to on, indicated by the illumination of an
LED in the recirculation air return aperture of the power supply enclosure.
Customer
equipment
racking
Provision is made within the power supply enclosure for the fitting of customer specific
equipment, in 6 U of standard 19 inch equipment racking. Adjacent to the racking are
four 125W power outlets (– 55 V dc and earth), labelled COMMS 1 to COMMS 4. These
are supplied from individual 5 A dc circuit breakers on the outdoor PSU.

Interconnection diagram of the TMS push button test

switches
Pole
SW1 TEST
OVERRIDE
N/O
Pole Pole Pole
SW2 SW3 SW4
N/O N/O N/O

HEATER INTERNAL EXTERNAL
ON FANS FANS
PL5
11 13 15 9 10 12 14
BSS11_Ch4_28

Outdoor cabinet doors and lid ISSUE 1 REVISION 2
Outdoor cabinet doors and lid
Door function
The doors have the following functions:
S Provide physical security and environmental protection.
S Assist in correct thermal management by ducting return airflow.
S Provide EMC shielding.
The door wind stops enable the doors to to be latched open at the 90° or 120° position.
The power supply enclosure door, when closed, overlaps the radio enclosure door. The
doors also overlap the TMS front cover and the latches of the lid. The power supply
enclosure door therefore provides the single locking point for the cabinet and has the
striker for the door open alarm microswitch.
NOTE
When the Horizonmacro outdoor is delivered, the keys for the door are
contained in a plastic bag, fastened to the front grill of the TMS.
Lid function
The lid has the following functions:
S Provides physical security.
S Provides environmental protection.
The lid has a gas strut to assist in opening and a mechanical stay to limit movement
when open in windy conditions. The securing latches can only be accessed when the
cabinet doors are open.

ISSUE 1 REVISION 2 Outdoor cabinet doors and lid
Cabinet door views with major features labelled
WIND STOPS
RADIO ENCLOSURE
DOOR
ENVIRONMENTAL
SEAL
A5 DOCUMENT
POCKET AIR DUCTS
AIR DUCT
BRUSH SEALS
LOCKING LATCH
HANDLE
POWER SUPPLY
BSS11_Ch4_29
ENCLOSURE DOOR
View of cabinet lid
LID GAS STRUT
INSULATION
FOAM
TOP
SECTION
MECHANICAL
SECURING
STAY
LATCH CABINET
TOP WRAP
SECURING
LATCH ENVIRONMENTAL
SEAL BSS11_Ch4_30

Horizonmacro outdoor temperature control ISSUE 1 REVISION 2
Horizonmacro outdoor temperature control

Temperature
control overview
The Horizonmacro outdoor cabinet contains equipment that has to be maintained within
the operational temperature range, to ensure correct operation of the equipment and to
guard against premature failure of the individual components.
Cabinet over
temperature
control
Under overheat conditions, as the temperature rises above preset levels, temperature
sensors located in various areas within the cabinet provide alarms. A further increase in
temperature causes sensors, set at higher temperature thresholds, to initiate PSM or
cabinet shutdown. The cabinet is restarted when the sensors are reset by a substantial
fall in temperature.
TOPSMs and CTUs have their own internal total shutdown responses to overheating.
CTUs shutdown at 92 _C.
900 MHz CTUs also have an internal 4 dB power reduction shutdown response to
overheating, at 85 _C. 1800 MHz CTUs have a 0.6 dB cut back at 70 _C in addition to
the 4 dB power reduction at 85 _C.
Both the CTU and TOPSM shutdowns provide a second layer of cabinet protection,
independent of the cabinet heat sensors.
Temperature
sensors
Radio enclosure temperature sensors
Temperature sensors are located above the transceiver compartment (see Cage
backplane interface panel harness assembly ) and consist of the following:
S One 70 _C sensor, providing sensing for a cabinet overtemperature alarm when
the EMC enclosure temperature exceeds the preset level. The alarm is processed
by the alarm module and the MCUF, and sent on to the OMC, via the BSC.
S Two 85 _C sensors initiate shutdown of the PSMs to protect the cabinet equipment
from heat damage. Both sensors must detect excess temperature for the
shutdown to take place; this reduces the risk of an unnecessary shutdown due to
sensor failure. If a shutdown occurs, there is no prior notification to the OMC.
Power supply enclosure temperature sensors

The power supply enclosure temperature sensors are located on the control and alarm
board (see Outdoor PSU Control and Alarm Board (CAB)) and consist of the
following:
S One 70 _C sensor, providing sensing for a cabinet overtemperature alarm when
the non EMC enclosure temperature exceeds the planned level. The alarm is
generated by the control and alarm board, and passed as an external alarm to the
alarm module, where it is sent on to the OMC via the BSC. Operation of this
sensor will also reduce the TOPSM output voltage as described in Outdoor PSU
Control and Alarm Board (CAB).
S One 78 _C sensor, which initiates disconnection of the battery contactor, the
comms contactor and shutdown of the TOPSMs. This will shut down the BTS. If a
shutdown occurs, there is no prior notification to the OMC.

ISSUE 1 REVISION 2 Horizonmacro outdoor temperature control
TMS temperature sensors

The two TMS temperature sensors are located within the TMS unit (see Thermal
Management System (TMS) ), in the returned recirculation airflow from the EMC and
non EMC enclosures. They have the following functions:
S Either sensor provides sensing for the TMS overtemperature alarm when the TMS
returned recirculation air temperature exceeds 68_C. The alarm is generated by
the TMS control board, processed by the control and alarm board, and passed as
an external alarm to the alarm module, where it is sent on to the OMC via the
BSC.
S The TMS temperature sensors also provide the TMS control board with thermal
data used in controlling fan speed and heater operation.
Cabinet restart
after shutdown
The cabinet is restarted when the overtemperature condition initiating shutdown has
reset.
S The CAB re-enables the TOPSMs when the 78 _C temperature sensor has reset
at 60 _C.
S The two 85 _C temperature sensors reset at 55 _C. This re-establishes an earth
point for the PSM internal detectors connected to the cabinet heat sensors, which
then reactivate the PSM outputs.
The cabinet then restarts as a normal power up.

Thermal Management System (TMS) ISSUE 1 REVISION 2
Thermal Management System (TMS)
TMS overview
The equipment installed in the cabinet emits heat, which must be removed in order to
maintain the correct working temperature.
The Thermal Management System (TMS) unit maintains the cabinet internal temperature
within the operational range of the installed equipment, provided the external ambient
temperature is within the range of –40 °C to +50 °C.
An alarm is generated if the return air temperature from the BTS enclosures exceeds
68 °C.
The TMS unit contains:
S Two recuperators.
S Two ambient air fans (external fans).
S Two recirculation air fans (internal fans).
S Two ac electric heater elements.
S One TMS control board.
S Two temperature sensors.

ISSUE 1 REVISION 2 Thermal Management System (TMS)
Thermal Management System (TMS) unit view with

airflows indicated
RECUPERATORS
AMBIENT
AIR FAN RECIRCULATION
AIR FANS
LOCATION OF
KEY THE TMS
CONTROL BOARD
RECIRCULATION
AIRFLOW
AMBIENT
AIRFLOW
AMBIENT
AIR INLET
AMBIENT
AIR OUTLETS
Access panels and air ducts omitted for clarity

BSS11_4_31

Heat exchanger
components
The heat exchanger consists of the following items:
Recuperators
The recuperators are manufactured from a series of epoxy resin coated aluminium
sheets, sealed at alternate edges to form two sets of narrow air passages, one set for the
ambient air and one set for the recirculated air, but not allowing the air streams to mix.
Ambient air fans (external fans)

The two ambient air fans are located one on each side of the unit. The fans are of the
radial type with backward curved blades for maximum efficiency. The fan impeller is
direct driven by a –48 V dc motor with a solid state commutator. The fan contains its own
pulse width modulation (PWM) speed control circuitry.
Recirculation air fans (internal fans)

The recirculation air fans are located at the rear of the unit. The fans are of the same
type and operate the same way as the ambient air fans.
AC heater elements
The ac heater elements are located in the recirculation air inlet to the cabinet enclosures,
at the top of the unit. There are two individual heaters, each with its own high limit
thermostat attached.
TMS control board

The control board is located in the top right side of the TMS unit behind the cable well.
The control board has the following functions:
S Interpretation of thermal data from the TMS temperature sensors.
S Control of the speed of ambient and recirculation fans.
S Control of the operation of ac heater elements.
S Generation of TMS alarm signals.
S Configuration of heater elements for 230 V ac or 110 V ac input voltages.
Temperature sensors
The temperature sensors are located at the top of the TMS unit in the recirculation air
return aperture. The functions of the TMS temperature sensors are described in
Horizon macro outdoor temperature control in this chapter.

Heat exchanger functional diagram
Representation of the airflow paths through the Horizonmacro Outdoor cabinet
SIDE ELEVATION VIEW OF

RECIRCULATION AIRFLOW
THROUGH CABINET
Horizonmacro
outdoor
BTS CABINET CABINET
EQUIPMENT
HEATER
ELEMENT
KEY
RECIRCULATION
AIRFLOW
HEATER
FUNCTION LED
AMBIENT
AIRFLOW
RECIRCULATION
RECUPERATORS FAN
TMS UNIT
AMBIENT FAN
TMS
TEMPERATURE
HEATER
HEATER SENSOR
FUNCTION LED
ELEMENTS
PLAN VIEW OF AIRFLOW
THROUGH TMS UNIT
BSS11_Ch4_32

TMS functional
description
The TMS unit provides either cooling or heating to maintain the internal temperature of
the Horizonmacro outdoor BTS cabinet within the operational range of the installed
equipment. The TMS temperature sensors measure the temperature of the returned
recirculation air from the cabinet equipment enclosures.
Cooling
The TMS employs an indirect cooling system to protect the radio equipment against
atmospheric contaminants. Cooling is provided by recirculating air through two air to air
heat exchangers. Two separate airflow paths are driven through the two recuperators by
fans; the warmer air stream gives off heat to the colder air stream.
The TMS control board manages the speed of both sets of fans. The control board
initiates an increase in fan speed when either TMS temperature sensor detects an
increase in temperature, above a control threshold. A reduction in fan speed is only
achieved when both sensors detect a decrease in temperature below the control
threshold.
The recirculation air fans run continuously. As the temperature rises, the ambient air fans
start. A further temperature rise causes both fans ramp up to full speed.
The recirculation air fans run at 60% of full speed at all temperatures, up to 55 °C. Fan
speed increases linearly as the temperature rises, until it reaches full speed at 60 °C.
The ambient air fans are inhibited at temperatures below 40 °C and run at 60% of full
speed between 40 °C and 55 °C. Fan speed then increases linearly as the temperature
rises, until it reaches full speed at 60 °C.
Heating
At low temperatures and in cold start conditions, ac electric heaters are used to maintain
the cabinet internal temperature at operational levels. Only the recirculation air fans
operate when the TMS is heating the cabinet.
Heater element operation is managed by the TMS control board. The control board
switches the heaters on when either TMS temperature sensor detects a decrease in
temperature to below 10 °C, but only switches the heaters off when both TMS
temperature sensors detect a corresponding rise in temperature to above 20 °C.
Heater function is indicated by the illumination of an LED, mounted on the rear verical
wall at the top right of the recirculation air outlet aperture, below and in front of the power
supply enclosure.


Horizonmacro outdoor power supplies ISSUE 1 REVISION 2
Horizonmacro outdoor power supplies
Power supply
overview
The Horizonmacro outdoor power supplies consist of the following elements:
S The Power Supply Unit (PSU) containing:
– AC distribution and input ac supply connection.
– DC distribution and internal battery back-up.
– The power supply unit PSU Control and Alarm Board (CAB).
S The Outdoor Power Supply Modules (TOPSMs).
S The main cage Power Supply Modules (PSMs).
S The Circuit Breaker Module (CBM).
S The mBCU Power Supply Module (BPSM).
S Optional external battery back-up, housed in an AEH.
Power
distribution
overview
The power supply unit cage is the main power distribution assembly within the
Horizonmacro outdoor BTS cabinet.
The power distribution system consists of two main functional elements:
S Two ac distribution boxes and their associated cables.
S Six dc circuit breakers, two contactors, the multilayer busbar and dc cables.

ISSUE 1 REVISION 2 Horizonmacro outdoor power supplies
Power Supply Unit (PSU) cage and its associated

distribution boxes and cables
BSS11_4_33
Cabinet structure omitted for clarity

AC distribution
description
There are two ac distribution boxes and an ac power outlet socket associated with the
Horizonmacro outdoor PSU.
Number 1 ac distribution box

The number 1 ac distribution box is located in the top panel of the cabinet. It contains
circuit protective devices and a terminal block, and provides:
S The termination point for the incoming mains supply.
S A four pole 32 A main circuit breaker (also used as a switched disconnect for
external ac power supplies).
S A double pole 6 amp (30 mA) residual current circuit breaker with overcurrent
protection (RCBO) to supply the ac power outlet socket.
S The means of configuring the BTS to accept the following incoming ac supply
voltages:
– 230 V ac 50 Hz single phase and neutral.
– 230 V ac 50 Hz three phase and neutral (star configuration).
– 230 V ac 50 Hz three phase (delta configuration).
– 110 V ac 60 Hz single phase and neutral.
NOTE
When the Horizonmacro is supplied by 110 V single phase, the 4 pole main
circuit breaker is configured as two parallel pairs – one pair breaking the live
phase and one pair breaking the neutral. This provides circuit protection at a
total of 64 amps.

The number 2 ac distribution box is located in the upper right of the PSU and contains
circuit protective devices as follows:
S Three 20 amp double pole circuit breakers to supply The Outdoor Power Supply
Modules (TOPSMs).
S One 10 amp double pole circuit breaker to supply the Thermal Management
System (TMS) heaters.
Each double pole circuit breaker also acts as a switched disconnect for its respective
circuit, breaking both feed and return lines. The output of each circuit breaker is fed to its
load by discrete cables.

MAINS DISCONNECT AC SOCKET

4 POLE 32 A TYPE C 6 A 30mA
1 3 5 7 9 11
2 4 6 8 10 12
BSS11_Ch4_34
PSU 2 PSU 1 PSU 0 TMS

20 A TYPE B 20 A TYPE B 20 A TYPE B 10 A TYPE B
BSS11_Ch4_34a


AC distribution block diagram within the Horizonmacro

BTS cabinet
OUTLET SOCKET (ac)

INCOMING BOX
AC SUPPLY
NUMBER 2
DISTRIBUTION
BOX
HORIZONMACRO T T T
MAIN CAGE O O O
PLUG/SOCKET P P P
S S S
M M M
2 1 0
TMS TMS HEATERS
BSS11_4_35

DC power distribution ISSUE 1 REVISION 2
DC power distribution
DC distribution
overview
The regulated dc output of the TOPSM is distributed through the multilayer busbar to:
S The main cage PSMs.
S TMS fans.
S Customer specific equipment racking power outlets (COMMS 1 to 4).
S Internal battery backup.
S The connectors for optional external battery backup (located on the dc interface
panel, within the top panel enclosure).

ISSUE 1 REVISION 2 DC power distribution
The –55 V dc distribution block diagram
–55 V dc
PSM
TOPSM CTU
(DC/DC conv)
BATT CTU
TOPSM
CONTACTOR
COMMS CTU
TOPSM
EQUIPMENT
COMMS CTU
CONTACTOR
CTU
INTERNAL EXTERNAL
TMS FANS BATTERIES BATTERY CTU
CABINET
0 V dc
BSS11_Ch4_36

DC distribution
description
The main cage dc supply is routed from the left side of the multilayer busbar through the
dc interface panel to the main cage interface panel. Circuit protection for the main cage is
provided by the CBM and internal fusing in the PSMs.
The other circuits supplied from the multilayer busbar are protected by individual circuit
breakers. Six of the circuit breakers are mounted on the dc circuit breaker panel of the
outdoor PSU. The internal batteries have a separate 80 A circuit breaker, housed within
the battery mounting tray. The circuit breakers also function as switched disconnects for
their respective loads.
The PSU cage has two contactors as part of the dc distribution system. During periods of
battery back-up, the contactors will progressively disconnect battery loads as battery
voltage decreases, to prevent deep discharge of backup batteries. The operation of
these contactors is controlled by the control and alarm board.
Customer
equipment power
supplies
The four power outlets mounted adjacent to the customer equipment racks are supplied
from the multilayer busbar by individual 5 A circuit breakers.
Internal battery
backup
The internal battery tray, located at the lower right side of the PSU, holds four 12 V
batteries connected in series to provide a total output of 48 V dc, with a capacity of
15 Ah.
The internal batteries are protected by an 80 A circuit breaker, mounted on the battery
tray front panel. The circuit breaker also functions as a disconnect switch for the internal
batteries.
Battery voltage sensing leads are fed from the negative terminal of each battery to a four
way connector on the battery tray. This is connected to the Control and Alarm Board
(CAB). The sensed voltages are used by the battery capacity test and battery selector
switch functions of the CAB.
External battery
backup
connection
The external battery connection cables are routed from the left side of the multilayer
busbar to connectors on the dc interface panel. Circuit protection and disconnect
switching are provided by an 80 A circuit breaker mounted on the dc circuit breaker
panel.

Front view of the dc circuit breaker panel
EXT TMS COMMS COMMS COMMS COMMS

BATT FANS 1 2 3 4
80 A 10 A 5A 5A 5A 5A
BSS11_Ch4_37
View of the dc interface panel
EXTERNAL BATTERY
CONNECTORS
DC OUTPUT CABLES
BSS11_Ch4_37a

Control and Alarm Board (CAB) ISSUE 1 REVISION 2
Control and Alarm Board (CAB)
Introduction to
the CAB
The CAB is located in the outdoor PSU between the dc circuit breaker panel and the
number 2 ac distribution box. It provides the following functions:
S Control of TOPSM output voltage (voltage trim).
S TOPSM disable relay control.
S Control of battery and comms contactors:
– during cabinet power up.
– during Low Voltage Disconnect (LVD).
S Monitoring of battery voltage and temperature.
S Monitoring of TOPSM input and output failure signals.
S Monitoring of non EMC enclosure temperature.
S Monitoring of alarms from the cabinet, the TMS, and the auxiliary equipment
housing.
S Performing a battery charge capacity test on the internal batteries.
The CAB sources dc power from all of the following:
S The distributed dc regulated output of the TOPSMs.
S The TOPSM auxiliary output.
S The comms equipment side of the outdoor PSU comms contactor.

ISSUE 1 REVISION 2 Control and Alarm Board (CAB)
View of the Control and Alarm Board (CAB) and its front
panel
DIP SWITCHES
SW2 AND SW4
(see text)
BSS11_4_38
NOTE
There are two manufacturers of the CAB. Each is fully compatible with the
PSU, although circuit board layout may differ.

CAB indicators
and controls
Front panel indicators

S BATTERY CAPACITY (green).
– >15 mins.
– >10 mins.
– >5 mins.
One LED is lit, displaying result of last battery capacity test. The three LEDs flash
during the test and one illuminates to indicate test result.
S RADIO (green).
Normally illuminated, this LED indicates that the battery contactor is closed and
that radio loads are connected to the backup batteries, (where fitted).
S COMMS (green).
Normally illuminated, this LED indicates that the comms contactor is closed and
that customer comms loads are being supplied.
S CAB OT (red).
Normally unlit, this LED indicates a cabinet over temperature alarm state.
S EXT CAB OT (red).
Normally unlit, this LED indicates an auxiliary equipment housing over temperature
alarm state.
S SMOKE (red).
Normally unlit, this LED indicates a cabinet (optional) smoke detector alarm state.
NOTE
The smoke detector alarm functions are only activated by optional customer
supplied smoke detectors.
No provision has been made for the fixing of a smoke detector within the main
cabinet or the auxiliary equipment housing.
S EXT SMOKE ALM (red).

Normally unlit, this LED indicates an auxiliary equipment housing (optional) smoke
detector alarm state.
S STATUS (green).
Normally illuminated, this LED indicates that the cabinet is within normal operating
conditions, and will flash on and off when any alarm signal is present. The status
indicator will flash if either the battery or comms contactor is open.
NOTE
Opening the door triggers the door open alarm, causing the status LED to
flash. To check the true status, press the door microswitch to simulate closing
the door.

Front panel switches and buttons

Front panel switches and buttons are provided for the following:
S BATTERY TEST.
Initiates battery charge capacity test of internal batteries.
S Battery selector switch.
Connects two 4 mm sockets on front panel to internal batteries to allow monitoring
of battery condition.
S OVERRIDE.
Overrides disconnected enable signals to the TOPSMs for fault diagnosis.
S RESET.
Resets the CAB after an auxiliary equipment housing over temperature trip.
CAB front panel

fuses
The CAB front panel has three cartridge fuses, providing circuit protection for:
S Battery contactor (F1).
S Comms contactor (F2).
S Control and alarm board (F3).

CAB control
functions
The CAB has the following control functions:
S Voltage trim.
S TOPSM disable relay control.
S Control of contactors during power up.
S Low Voltage Disconnect (LVD).
S Over temperature trip.
S Smoke trip.
Voltage trim
The CAB generates the control signal voltage (V trim) used to regulate TOPSM output to
produce a temperature compensated battery charging voltage. The temperature sensor
is mounted on the CAB for internal batteries, and mounted in the auxiliary equipment
housing for external batteries. A dip switch on the CAB (SW2–8) is used to select either
internal or external battery temperature sensing.
TOPSM disable relay control

On detection of an over temperature trip alarm or a smoke alarm from the BTS cabinet,
the CAB energises the coil of the TOPSM disable relay, interrupting the enable in signal
and shutting down the TOPSM –55 V outputs. The TOPSM disable relay will remain
energized until the alarm condition has cleared and, in the case of a smoke alarm longer
than 30 seconds, the cabinet ac supply has been cycled or the CAB front panel reset
switch has been operated. Operation of the CAB front panel override switch will interrupt
this function, for a 30 second period, to allow fault diagnosis to be performed.
Control of contactors during power up

The CAB monitors the following signals during power up of the Horizonmacro cabinet:
S TOPSM auxiliary voltage within 9 to 15 V dc range
S Cabinet over temperature alarm.
S Cabinet smoke alarm.
If the alarm signals are inactive, the CAB will close the battery and comms contactors, to
supply customer communications equipment and charge the backup batteries.
If the CAB detects a cabinet over temperature or cabinet smoke alarm during power up,
then the TOPSM disable relay operates, as described in TOPSM disable relay control
in this section.

Low Voltage Disconnect (LVD)

The CAB constantly monitors battery voltage. During periods of back-up battery
operation, the CAB will progressively reduce the load to prevent deep discharge of the
batteries.
The CAB generates a low voltage disconnect imminent alarm when the battery terminal
voltage reaches –44 V. As the battery voltage level drops further, the CAB de-energizes
the battery contactor at –41 V, disconnecting the radios from the battery power. At
39.5 V, the comms contactor is de-energized to prevent extreme deep discharge of the
back up batteries.
The LVD threshold for the comms contactor is lower than that of the battery contactor, to
ensure customer communications equipment remains powered for as long as possible
after radio power has been lost.
NOTE
Once the comms contactor has opened the CAB will lose all power input
connections. CAB functions are only re-established when the ac supply is
restored to the cabinet. The cabinet then restarts as a normal power up.
Over temperature trip

The CAB generates a cabinet over temperature trip signal when both the 78 _C sensor
and the 70 _C sensor are active (see Horizon macro outdoor temperature control).
The cabinet over temperature trip signal disconnects the battery contactor, the comms
contactor, and disables the TOPSMs. This will shut down the BTS, and if a shutdown
occurs, there is no prior notification to the OMC other than the over temperature alarm.
The CAB re-enables the TOPSMs when both temperature sensors have reset at 60 _C.
The cabinet then restarts as a normal power up.
Smoke trip
NOTE
The following smoke trip functions have not been implemented in the main
cabinet or the auxiliary equipment housing.
The CAB generates smoke trip control signals after it has been in receipt of a smoke
alarm for 30 seconds.
S The Horizonmacro outdoor cabinet smoke trip signal disconnects the battery
contactor, the comms contactor and disables of the TOPSMs. The BTS will shut
down without prior notification to the OMC, other than the smoke alarm.
S A smoke trip signal from the auxiliary equipment housing initiates a remote
disconnection of the external batteries.
Once generated, the smoke trip control signals remain active until the input mains ac is
cycled, or the CAB front panel reset button is operated.

CAB alarm
functions
The CAB generates or processes the following alarms:
S Over temperature alarms:
– Power supply enclosure over temperature.
– TMS over temperature.
– TMS 2 over temperature (not used).
– Auxiliary equipment housing over temperature.
S Power supply alarms:
– TOPSM dc output fail.
– Mains input fail.
– Low voltage disconnect imminent.
S TMS fail alarms:
– TMS fail.
– TMS 2 fail (not used).
S Smoke alarms:
– Optional smoke detector.
– Optional auxiliary equipment housing smoke detector.
S Door open alarms:
– BTS cabinet door open.
– Auxiliary equipment housing door open.
Except for TOPSM dc output fail, the alarms originate at sensors which use voltage-free
contacts to indicate an alarm by going open contact.
The CAB sends the alarms through the alarms interface board and the interface panel as
external alarms to the digital alarm module. All alarms to this module indicate an alarm by
going open-circuit. The alarms are processed by the alarm module and MCUF, and sent
on to the OMC via the BSC.
Auxiliary equipment housing alarms can be inhibited using the SW 2 dip switches
mounted on the CAB pcb.
Over temperature alarms

The operation of the over temperature alarms associated with the CAB is described in
Horizon macro outdoor temperature control.
Power supply alarms

The TOPSM dc output fail and mains input fail alarm signals are generated by a single
changeover relay within each TOPSM.
S A single TOPSM alarm signal is interpreted by the CAB as a TOPSM dc output
fail.
S A fail signal from all installed TOPSMs is interpreted by the CAB as an ac supply
input fail.

TMS fail alarm

A TMS fail alarm is generated by the TMS control board when any fan or heater fails.
The alarm signal is routed to the CAB through the alarms interface panel. It is then
processed by the CAB and sent to the digital alarm module.
A separate fan fail signal, generated by the TMS control board, is fed to the digital alarm
module without processing by the CAB.
Smoke alarms
Smoke alarms originate at optional (customer supplied and fitted) smoke detectors. The
alarm is then processed by the CAB and sent to the digital alarm module. Dip switches
mounted on the CAB printed circuit board are used to inhibit the alarm signals when
smoke detectors are not fitted.
Door open alarms

The BTS cabinet door open alarm is generated by the CAB when the microswitch
mounted in the top left corner of the power supply enclosure is open circuit.
The auxiliary equipment housing door open alarm signal originates at a door mounted
microswitch, and is generated by the CAB when the microswitch mounted in the auxiliary
equipment housing is open circuit.

CAB additional
functions
The CAB also provides the following functions:
S Internal battery capacity test.
S Battery selector.
S Debug.
Internal battery capacity test

The CAB performs an internal battery capacity test when:
S CAB front panel BATTERY TEST push button switch is operated.
S Automated self-test carried out periodically.
S Initiated remotely from the OMC.
During the battery capacity test, the CAB sets the TOPSM outputs to –43 V by adjusting
the voltage trim signal so that the internal batteries supply the cabinet loads. The CAB
then monitors the time taken for the battery terminal voltage to drop to –44 V or times out
after 15 minutes. The CAB front panel battery capacity LEDs indicate the discharge time,
and a relay-generated signal is sent to the OMC. The LEDs and relays remain active
displaying the result of the last test conducted.
Remote initiation and reporting of the internal battery capacity test uses the site output
relay 1 contacts of PIX 0, to initiate the test, and site alarm inputs 1 to 3 to report the
results of the test.
> 5 mins PIX 0 site alarm input 3 short circuit.

>10 mins PIX 0 site alarm inputs 2 and 3 short circuit.
>15 mins PIX 0 site alarm inputs 1, 2 and 3 short circuit.
Internal battery capacity test cannot be initiated if there are system alarms active, the
door microswitch must be pressed to override the door open alarm. If an alarm occurs
during the test, the TOPSM is reset to its normal temperature compensated operating
voltage and the battery discharge test is interrupted. The CAB then responds to the
alarm signal as normal.
The dip switches SW 4 inhibit or set periodicity (between 1 and 30 days) of automated
internal battery capacity test, (default setting is inhibited).
NOTE
Pix 0 site alarms are connected to the CAB through PL2 of the alarms
interface board. PL2 is disconnected and tied back when supplied, if this
functionality is required PL2 must be connected to the alarms interface board.
The battery capacity test discharges the internal batteries to –44 Vdc. If an
external power supply failure occurrs immediately after the test, the battery
back up duration is reduced to approximately 3 minutes. The internal batteries
recharge to approximately 80 % capacity in less than one hour.

Battery selector test circuit
CONTROL BOARD
B28
5K1 f
+I e
C28
d
BLUE
–I c 1
B32
5K1
–48 V
b
A32 5K1 a
–36 V
DM
B31 f SOCKETS
5K1
–24 V
e
A31 5K1 d
–12 V
2
BLACK
c
A23,24,25 5K1 b
0V a
BSS11_Ch4_39

Battery selector
The battery selector switch connects two 4 mm DM sockets on the CAB front panel to
the internal batteries, to allow measurement of:
S Total battery voltage.
S Individual battery voltage.
S Battery current.
Debug
The CAB front panel LEDs can be remapped to indicate alarm status to assist in fault
finding, particularly before connection of the Horizonmacro site to the network. Operation
of a dip switch (SW 4–5) and resetting the CAB causes the front panel LEDs to illuminate
when the alarm is clear.

The expected DMM values for each position of the test

switch
Table 4-3 Battery selector switch test values

Test switch setting Reading Cell under test
a – 48 V dc All
b –12 V dc Cell 1
c –12 V dc Cell 2
d –12 V dc Cell 3
e –12 V dc Cell 4
f Battery charge All
current
The CAB front panel LEDs are remapped as shown
Table 4-4 Remapping of CAB front panel LEDs

Front panel LED Colour Debug function
15 mins Green Mains fail
10 mins Green TOPSM output
5 mins Green TOPSM auxiliary voltage
RADIO Green Not used
COMMS Green Not used
CAB OT Red Cabinet over temperature
EXT CAB OT Red External cabinet over temperature
SMOKE Red Smoke alarm
EXT SMOKE ALM Red External smoke alarm
STATUS Green Status

The Outdoor Power Supply Module (TOPSM) ISSUE 1 REVISION 2
The Outdoor Power Supply Module (TOPSM)
TOPSM overview
This section describes the TOPSM used in the Horizonmacro outdoor cabinets.
Three TOPSMs provide adequate operating power for all the modules within the base
station and full battery charging (including external extended battery backup). Under
normal operating conditions, two TOPSMs provide sufficient power to operate all BTS
modules and trickle charge the batteries and the third TOPSM then provides redundancy.
TOPSM
functional
description
The TOPSM system is a power factor-corrected, wide input, ac power supply module.
Each TOPSM is a switching type ac/dc power converter with the following regulated dc
output:
S –55 V at 23.5 A (maximum output current).
S 1200 W (nominal).
The outputs of each TOPSM are connected in parallel by the power supply cage. The
TOPSMs in the system actively share the load.
The regulated dc output is fed through the multilayer busbar to the interface panel and
the dc circuit breaker panel to power the base station.
LED display
There are four LEDs mounted on the front of the TOPSM, which indicate the following:
S I/P HEALTHY (yellow) - lit when the input voltage is present and within specified
limits (88 to 264 V ac).
S OVERVOLTAGE (red) - lit when the TOPSM has shut down due to an output
voltage in excess of –59.9 V dc.
S OVERCURRENT (red) - lit when the TOPSM is in current limit and delivering a
current in the range 22 A to 24 A. The LED is normally unlit, but when lit does not
necessarily indicate the existence of a fault as this may be due to recharging of the
batteries after an ac supply interruption.
S O/P HEALTHY (green) - lit when output voltage is present and within specified
limits (–39 to –59.9 V dc).

ISSUE 1 REVISION 2 The Outdoor Power Supply Module (TOPSM)
View of The Outdoor Power Supply Module (TOPSM)
BSS11_4_42

Monitoring
Internal
Internal TOPSM circuits monitor for the following:
S –55 V output voltage regulation.
S The –55 V output is also regulated to provide temperature compensation for the
float charging of the internal batteries (battery backup) in the range –52.88 V at
40 _C to –56.72 V at 0 _C.
S Over-voltage protection – provides shutdown if the output voltage exceeds
–59.9 V.
S Over-current protection – provides constant current limiting at 22 to 24 A, unless
output voltage drops below 39.6 V, when the output current will fold back to
between 3 and 8 A.
S Enable control of TOPSM from the control and alarm board.
External
The control and alarm board monitors common alarm signals generated by the
changeover relays fitted within the TOPSMs. The possible alarms are:
S Mains input fail - This alarm is active if all the fitted TOPSMs lose their input supply
or the input drops below their operating minimum value.
S DC output fail - This alarm is active if the output from one or more fitted TOPSMs
fails, or goes outside the preset tolerance level.
Alarm conditions generated by the TOPSM may be detected by one of the red LEDs
being lit, or by the dc output fail and mains input healthy LEDs being unlit.
Protection
circuits
Activation of the protection circuits causes the TOPSM to shut down. During a shutdown,
the output circuits of the malfunctioning TOPSM are isolated and its output healthy LED
is switched off. The malfunctioning TOPSM informs the control and alarm board of the
shutdown condition. An alarm signal is also activated and sent to the control and alarm
board if all TOPSMs detect loss of ac input voltage. After an alarm condition has ceased,
normal TOPSM operation is automatically restored.
Thermal
protection
The TOPSM is provided with additional internal thermal protection. If the ambient
temperature of the TOPSM exceeds a safe level then it shuts down, causing an alarm
message to be sent to the control and alarm board. Normal TOPSM operation resumes
after the temperature returns to a safe level.

Functional diagram of TOPSM
BACKPLANE CONNECTOR
VIN (88 V to 264 V)
VOUT ( 55 V)
ENABLE IN
RELAY 1 ON
ENABLE OUT RECTIFIER
PCB
INPUT F AIL
YELLOW I/P HEALTHY POWER CONTROL

LED CONVERTER AND
OUTPUT FAIL
AND ALARM
OVERVOL TAGE SYSTEM
RED MONITOR
LED
RED I/LIMIT
LED
CURRENT SHARE OTHER
O/P HEAL THY TOPSMs
GREEN
LED
VOLTAGE TRIM
CONTROL
AND
AUXILIARY SUPPL Y (12V) ALARM
BSS11_4_43

Control and
alarm signals
The following signals are associated with TOPSM control and alarms:
S Enable out.
An independent –55 V output from each TOPSM commoned together and
connected to the normally closed contacts of the disable relay (relay 1), on the
backplane of the power supply unit cage.
S Enable in.
This signal, fed from the normally closed contacts of the disable relay (relay 1) on
the backplane of the power supply unit cage, enables the TOPSM output (the relay
is operated by the the control and alarm board under fault conditions).
S Voltage trim.
A variable voltage signal, generated by the control and alarm board, used to
regulate the TOPSM output in order to produce a temperature compensated
battery charging voltage, to ensure that the internal or external batteries are not
overcharged.
S Current share
A signal representing the average current for the total system. Each TOPSM
compares its output current with the average current and adjusts its output voltage
so as to equalize its output current with the average system current.
S Auxiliary supply
A 12 V supply independent of the TOPSM output, but referenced to it, used to
power the control and alarm board circuitry when the TOPSM output is inhibited.
S Input healthy
The normally open contact of the isolated changeover relay used to indicate that
the input is within specification.
S Output healthy
The normally closed contact of the isolated changeover relay used to indicate that
the output is within specification.


Power Supply Module (PSM) ISSUE 1 REVISION 2
Power Supply Module (PSM)

The Power Supply Module (PSM) used in the Horizonmacro outdoor is the –48V (positive
earth) module. Details on this PSM are laid down inthe Horizonmacro indoor cabinet
section of the course manual.
MicroBCU Power
Supply Module
(BPSM)
The BPSM specifications are detailed inthe Horizonmacro indoor cabinet section of this
course manual.

ISSUE 1 REVISION 2 Power Supply Module (PSM)

Auxiliary equipment housing overview ISSUE 1 REVISION 2
Auxiliary equipment housing overview
Introduction to
the auxiliary
equipment
housing
The auxiliary equipment housing is an optional multi-purpose secure enclosure for use
with the Horizonmacro outdoor cabinet. It provides space for the installation of additional
equipment at the BTS site.
Auxiliary
equipment
housing
mechanical
design
The external design of the auxiliary equipment housing is based on that of the
Horizonmacro outdoor cabinet – the procedure for opening/closing the door and lid are
identical (except that there is only one lid catch on the auxiliary equipment housing).
The auxiliary equipment housing contains 23 U of standard equipment racking, with
shelving fitted as standard.
Additional equipment can include:
S External battery backup system.
S Customer supplied equipment.
Cable entry to the auxiliary equipment housing is through either side, dependant on site
configuration. The cables pass through the earth plates, fitted on both sides of the
housing. Internal connections are made through a power distribution box containing
circuit breakers, mounted on the inside of the lid.
This box also contains an external alarms interface board, which sends alarm signals to
the main cabinet.
Two pairs of Anderson connectors are fitted to the underside of the power distribution
box. The rear pair is for the dc power connection to the main cabinet. The front pair is for
an extension connection, either to another main cabinet, or to an additional auxiliary
equipment housing.

ISSUE 1 REVISION 2 Auxiliary equipment housing overview
External view of unequipped auxiliary equipment housing

with the lid open
POWER DISTRIBUTION
BOX
EXTERNAL ALARMS
CIRCUIT BREAKERS INTERFACE BOARD
(MOUNTED INSIDE POWER
DISTRIBUTION BOX)
DC POWER CONNECTORS
EARTH STUDS
BATTERY CABLES
ACCESS TO PL1,
PL2 AND PL3
EARTH PLATE
FRONT PANEL, CONTAINING

FAN ASSEMBLY
BSS11_Ch4_44

Temperature control within the auxiliary equipment housing ISSUE 1 REVISION 2
Temperature control within the auxiliary equipment housing
Temperature
control
equipment
The temperature within the auxiliary equipment housing is regulated by the following
equipment:
A fan, mounted in the lower front panel, to provide cooling.
Heater mats, fitted to the back panel and lower side panels, to provide heating.
Operation of the
temperature
control
equipment
The fan operates from a –48 V dc supply, connected through PL7 on the external alarms
interface board and protected by a 500 mA anti-surge fuse. The heater mats each
require –48 V dc, connected through PL8, PL9, PL10 and PL11 for heater mats 1 to 4
respectively on the external alarms interface board. The supply voltage to each mat is
protected by a 5 A fuse.
The fan operates at all temperatures. The heater mats operate the ambient temperature
is less than 12 °C (+/–3 °C).
The auxiliary equipment housing contains two temperature sensors, providing sensing for
an over temperature alarm and an over temperature trip control signal.
If the over temperature alarm sensor is triggered (cabinet temperature reaches 55 to
60 °C), this causes an alarm signal to be sent to the OMC via the CAB in the main
cabinet. If the over temperature trip sensor is triggered (cabinet temperature reaches
65 °C, +/–3 °C), the external alarms interface board disconnects the remote operation
circuit breakers, thus removing the supply to the main cabinet. When the temperature
drops to 5°C below the trip level, the external alarms interface board causes the circuit
breakers to close, thus restoring the supply to the main cabinet.
Auxiliary
equipment
housing as a
battery box
The most common application for the auxiliary equipment housing is to use it for battery
backup for the Horizonmacro outdoor cabinet, by fitting optional batteries.
Up to 16 x 6 V batteries can be mounted on four shelves. Each bank of eight batteries
must be wired in series to provide –48 V dc, and the two banks are normally wired in
parallel to provide increased backup duration. Alternatively, each of the two banks of
batteries can be independently connected to separate BTS cabinets.

ISSUE 1 REVISION 2 Temperature control within the auxiliary equipment housing
Auxiliary equipment housing with batteries installed
BSS11_4_45a

External alarms interface board ISSUE 1 REVISION 2
External alarms interface board
Function of the
external alarms
interface board
The external alarms interface board is mounted in the power distribution box, in the lid of
the auxiliary equipment housing. It has the following functions:
S Provides power to the temperature control equipment in the auxiliary equipment
housing.
S Relays alarm signals from the auxiliary equipment housing through the alarms
interface board in the Horizonmacro outdoor BTS cabinet to the CAB.
S Provides facilities to extend control and alarm functions to a second BTS cabinet
or auxiliary equipment housing.
External alarms
interface board
connections
Power, control and alarm signals are relayed through the external alarms interface board
as described below.
NOTE
Cables for connecting the heater mats, fan and control/alarm signals are
extended to the outside of the power distribution box.
Power connections
External power (–48 V dc) is connected to PL12, pins 1 and 2 on the interface board via
the rear pair of Anderson connectors on the bottom left side of the power distribution box.
If a second BTS cabinet is connected, the supply voltage is connected to PL12 pins 3
and 4 via the front pair of Anderson connectors. The fan is powered from PL7. The four
heater mats are individually connected to PL8, PL9, PL10 and PL11.
Control connections
Control signals to trip the circuit breakers in the event of an over temperature alarm
signal (temperature reaches 65 °C, +/–3 °C) or a low voltage supply signal (supply
voltage drops below 38 V dc).
Alarm connections
The following alarm signals are routed through the interface board to the CAB:
S Over temperature alarm signal (PL1, pins 5 and 6).
S Door open signal (PL4).

ISSUE 1 REVISION 2 External alarms interface board
Auxiliary equipment housing lid
External alarms interface board

(Mounted inside power distribution box)
BSS11_4_45c

Horizonmacro 12 carrier outdoor enclosure structure ISSUE 1 REVISION 2
Horizonmacro 12 carrier outdoor enclosure structure
Introduction to
the enclosure
This chapter provides information about the enclosure structure and its components. All
components, except the power distribution equipment, Heat Management System (HMS)
and indoor cabinet, are described here.
Enclosure
description
The Horizonmacro 12 carrier outdoor enclosure is essentially a metal box, with front
opening doors and hood for access. This provides a controlled environment for one or
two Horizonmacro indoor BTS cabinets in an outdoor location, through the use of a Heat
Management System (HMS).
Additional cooling for the power system is provided by two fan trays. One tray is mounted
at the base of each side of the enclosure, below the rectifier modules. These provide
cooling by blowing air directly over the chassis of each rectifier.
Cable entry to the enclosure is low level, through the left or right side of the base or from
beneath. An optional high level cable entry kit is available if high level cable entry is
required.
Internally, the enclosure can be conveniently divided into six functional areas for:
S AC supply and interface cabling.
S Battery backup.
S AC and dc power distribution (PDU B).
S Power distribution and customer equipment (PDU A).
S Horizonmacro cabinet (BTS 0).
S Horizonmacro cabinet (BTS 1).

ISSUE 1 REVISION 2 Horizonmacro 12 carrier outdoor enclosure structure
Functional areas within the enclosure
AC SUPPLY
AND
INTERFACE
CABLING HORIZONMACRO HORIZONMACRO
INDOOR CABINET MASTER INDOOR
(BTS 1) CABINET
(BTS 0)
BATTERY
BACKUP
AC AND DC POWER POWER DISTRIBUTION AND

DISTRIBUTION CUSTOMER EQUIPMENT
(PDU B) (PDU A)
BSS11_Ch4_46

Horizonmacro 12 carrier outdoor enclosure structure ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Horizonmacro 12 carrier outdoor enclosure structure
Internal view of the Horizonmacro 12 carrier outdoor

enclosure, showing components
NOTE
Only items in bold text, plus the doors (not shown in this figure), are
discussed in this chapter.
HORIZONMACRO
ALARM
HORIZONMACRO LIGHTS MASTER INDOOR
INTERFACE
INDOOR CABINET CABINET
MODULE
(BTS 1) (BTS 0)
PRIMARY AC
SMOKE
TERMINAL BOX
DETECTOR HOOD
AND
THERMOSTATS
ÏÏÏÏÏÏÏ
ÏÏÏÏÏÏÏ
ÏÏÏÏÏÏÏ
SPACE FOR
CUSTOMER
ÏÏÏÏÏÏÏ
EQUIPMENT
DC POWER RECTIFIERS
DISTRIBUTION
BACKUP UNIT FAN TRAY
BATTERIES FAN TRAY
(NOT VISIBLE) (NOT VISIBLE)
AC POWER HEATER
DISTRIBUTION
UNIT
RECTIFIERS
–48 V DC CONNECTOR
POWER PANEL (FOR CUSTOMER
CONTROL EQUIPMENT)
MODULE
BSS11_Ch4_47

Alarm Interface Module (AIM) ISSUE 1 REVISION 2
Alarm Interface Module (AIM)
Functional
description of
the AIM
The AIM provides the interface between alarms for equipment fitted as part of the
enclosure and the Horizonmacro master indoor cabinet. Alarm signals are relayed from
the BTS 0 ALARM connector on the AIM to the EXTERNAL ALARMS connector on the
interface panel on the top of the BTS. PIX0 and PIX1 connectors on the AIM connect to
the corresponding PIX connectors on the BTS interface panel.
The AIM also provides termination and line overvoltage protection for six 2 Mbit 120 ohm
twisted pair lines.
In addition to the above, the AIM provides the interface for alarm signals from the
optional ancillary cabinet.
AIM connectors
and switches
Detailed descriptions of the Alarm Interface Module connector pin-outs and dip-switch
settings can be found in chapter 2 of the Horizonmacro 12 carrier outdoor service
manual.

ISSUE 1 REVISION 2 Alarm Interface Module (AIM)
Interconnection block diagram for the Alarm Interface

Module (AIM)
SMOKE
DETECTOR
ENCLOSURE HOOD
THERMOSTATS CONTACT
LINE
TERMINATION J24 J23 J22 J21 J20 J19 J18 J17 J16 J15 J14
J25
THERMAL SENSORS
BTS 0 EXT. ALARMS 4
BTS 0 EXT. ALARMS 3
BTS 0 EXT. ALARMS 2
BTS 0 EXT. ALARMS 1

BTS 0 BIB
2 MBIT 2 MBIT 2 MBIT 2 MBIT 2 MBIT 2 MBIT 2 MBIT

UNIT
SMOKE ALARM
BTS 0 RELAY 4
BTS 0 RELAY 3
BTS 0 RELAY 2
BTS 0 RELAY 1
EARTH LINE 6 LINE 5 LINE 4 LINE 3 LINE2 LINE 1

HOOD SWITCH
J13
INTERFACE
(OPTIONAL)
J26
BTS 0
J12
ALARM 0
J27
BTS 0 PIX1
J11
J28
BTS 0 PIX0
J10
ANC. CAB. ALARM
OVERRIDE OVERRIDE
SW 1 SW 2
ALARM INTERFACE
J9
BATTERY ALARM
BATTERY ALARM
BTS 0 BTS 1 MODULE (AIM)
MASTER SLAVE
ANCILLARY
EXTERNAL
J8
INTERNAL
INTERNAL
BATTERY
CABINET
SENSOR
SYSTEM
POWER
EARTH
HMS 0
HMS 1
BTS 0
BTS 0
J7
DOOR 1
J1 J2 J3 J5 J6 J4 J41 J40
CONTACT
DOOR 2
CONTACT
POWER ANCILLARY
SYSTEM CABINET
HMS 0
HMS 1 EARTH
BAR
BSS11_Ch4_48

Primary ac terminal box ISSUE 1 REVISION 2
Primary ac terminal box
Primary ac
terminal box
location and
function
The primary ac terminal box is mounted vertically on the rear wall of the enclosure, on
the left side. It provides the connection point for the incoming ac supply to the equipment
contained in the enclosure.
From left to right, the terminals are designated as follows: earth connection to Principal
Ground Bar (PGB); earth (PE), linked to PGB terminal; neutral (N); phase 1 (L1); phase
2 (L2); phase 3 (L3).
If required, single phase operation is achieved by linking together the inputs to terminals
L1, L2 and L3 (the links are supplied).

ISSUE 1 REVISION 2 Primary ac terminal box
View of the primary ac terminal box housing six terminal

connectors
TO PGB
AC SUPPLY CABLE
INPUT
BSS11_Ch4_49

Fan tray ISSUE 1 REVISION 2
Fan tray
Introduction to
the fan tray
Two fan trays are mounted in the base of the Horizonmacro 12 carrier outdoor enclosure,
one on the left side (for PDU B), and one on the right side (for PDU A). The purpose of
the fan trays is to provide cooling for the rectifiers, which are mounted above them.
Fan tray
description
The left fan tray comprises two rows of three fans, and a control board. The right fan tray
comprises two rows of two fans. The fan trays are powered by –48 V dc and are
independently fused at the dc power distribution unit.
Each fan tray is linked to the “rectifier fail” alarm circuits on the power control module, so
a failure of one or more fans will be signalled to the AIM through the power control
module.

ISSUE 1 REVISION 2 Fan tray
View of the right fan tray used in the Horizonmacro 12

carrier outdoor enclosure
CONTROL BOARD
FAN
POWER
CONNECTOR
The left fan tray is similar but wider, to accommodate three fans in each row
BSS11_Ch4_50

Fan tray ISSUE 1 REVISION 2
Operation of the
smoke detector
A smoke detector is mounted vertically in the enclosure, behind the vertical support
bracing. Its function is to shut down the equipment in the event of smoke being detected
within the enclosure. It provides an alarm via the BTS approximately 30 seconds before
the system is shut down.
The smoke detector is powered by 24 V dc from the power control module. Once an
alarm condition is detected, the smoke detector sends a smoke alarm trip signal to the
AIM. The AIM forwards the signal to both BTS 0 and the power control module. On
receiving the signal, the power control module inhibits the operation of the rectifiers and
disables LVD A and LVD B, thus isolating the BTS cabinet(s) and the backup batteries.
The smoke alarm trip signal can only be cleared by removing and reapplying ac power, or
pressing the RESET button on the front of the power control module.
Enclosure
lighting
description
The Horizonmacro 12 carrier outdoor enclosure has two internal fluorescent tube lights
mounted in the roof panel, one on each side. The lights are powered by 230 V ac from
the AUXILIARIES circuit breaker on the ac power distribution unit, and each light
includes a 230 V Euro-type service outlet socket built into the left side of the tube holder.
Additionally, each light is activated by a proximity switch, so movement within the left or
right side of the enclosure causes the left or right light to switch on automatically.
A 3-position slider switch is mounted on the underside of each light fitting. This allows
each light to be manually switched on or off, or left in the automatic (proximity switch
controlled) position.
Under normal operating conditions, the AUXILIARIES circuit breaker should be left
switched on and the enclosure light switches should be in the automatic position.

ISSUE 1 REVISION 2 Fan tray

Doors and hood ISSUE 1 REVISION 2
Doors and hood
Door function
The doors have the following functions:
S Provide physical security and environmental protection.
S Assist in heat management due to a Heat Management System (HMS) being
mounted on the inside of each door.
S Provide EMC shielding.
The door stays enable the doors to to be latched open at the 90° or 120° position. Each
door is fitted with a striker for individual door open alarm microswitches.
Both doors overlap the lip of the hood. This means that the hood cannot be lifted unless
both doors are open.
Operation of the
door locks
The left and right door handles operate in a similar manner. Both doors have a spring
loaded locking handle and operate as follows:
1. Slide open the two lock protective covers.
2. Insert the key into the left lock and turn clockwise until the spring loaded handle
releases.
3. Turn the handle a quarter turn to the left to open the door.
4. Insert the key into the right lock and turn anticlockwise until the spring loaded
handle releases.
5. Turn the handle a quarter turn to the right to open the door.
6. Open both doors to the 90_ locking position.
NOTE
A door open alarm is generated if the equipment is active. This means that the
green STATUS OK LED on the front of the power control module will NOT be
illuminated when the doors are opened. The alarm can be cancelled by taping
down the door microswitches. The STATUS OK LED will then illuminate,
provided there are no other alarm conditions present.
7. To open the doors to 120_, lift up the middle of the door stays and open the doors
until they reach the limit of travel.
8. To close the doors, lift up the middle of the door stays, close doors firmly and turn
the handles a quarter turn to the right (for the left door) or left (for the right door)
and push until the handles are flush with the doors. The doors lock automatically.
NOTE
The key is not required to lock the enclosure. Turning the left handle back to
the vertical position when both doors are closed causes the doors to lock
automatically.

ISSUE 1 REVISION 2 Doors and hood
Location of components in the Horizonmacro 12 carrier

outdoor
HORIZONMACRO PRIMARY AC
INDOOR CABINET TERMINAL BOX
(BTS 1)
HORIZONMACRO
INDOOR CABINET
ALARM INTERFACE (BTS 0)
MODULE
RECTIFIERS
(HIDDEN)
BACKUP
BATTERIES
RECTIFIERS
HMS 1
FAN
POWER DC CONNECTOR
TRAY HEATER
CONTROL PANEL
MODULE 6 U SPACE FOR (HIDDEN)
CUSTOMER
EQUIPMENT
AC AND DC FAN
POWER TRAY
DISTRIBUTION (HIDDEN)
UNITS
BSS11_Ch4_51

Doors and hood ISSUE 1 REVISION 2
Hood function
The hood has the following functions:
S Provides physical security.
S Provides environmental protection.
Hood operation
The hood can only be opened and closed when the doors are open. A lip on the front
edge of the hood is overlapped by the top edge of the doors, thus preventing the hood
from being lifted while the doors are closed. Also, the hood is secured in the closed
position by four screws, which must be removed before the hood can be opened. These
screws must be refitted when the hood is closed.
A gas strut is fitted to either side of the hood to assist in opening and closing. A pull strap
is provided on the underside of the hood to assist in closing. Once the hood starts to
close, the gas struts ensure that the hood lowers gently to the closed position
A microswitch is fitted to the top lip of the enclosure, and is in contact with the hood when
the hood is in the closed position. This generates an alarm signal when the hood is
raised

ISSUE 1 REVISION 2 Doors and hood
View of the hood of the Horizonmacro 12 carrier outdoor
HOOD
GAS STRUT
PULL STRAP
GAS STRUT
ENVIRONMENTAL
SEAL
BSS11_Ch4_52

Cable entry to the enclosure ISSUE 1 REVISION 2
Cable entry to the enclosure
Cable entry
overview
Cable entry to the enclosure is normally low level or from beneath the enclosure,
depending on customer requirements. High level cable entry (on the left side only) is
possible using an optional high level cable entry kit. Each type of cable entry is catered
for in the enclosure design.
Low level cable

entry
Low level cable entry to the enclosure can be from either the left or right side of the base
of the enclosure.
Two blanking plates are fitted on each side of the base of the enclosure. Separate
power/comms and RF cable plates are supplied for fixing in position when the blanking
plates are removed. Only one power/comms plate is supplied, whereas four RF plates
(each split into two) are supplied. Two of the RF plates have a hole radius of 14.5 mm
and two have a radius of 20 mm, so that the most common RF cable sizes can be
accommodated.
For certain installation types (on a rooftop, for example), it may be possible to route the
cables into the enclosure from beneath. This diagram opposite shows an example of
how this might be achieved.

ISSUE 1 REVISION 2 Cable entry to the enclosure
Low level cable entry plates (right side shown)

RF PLA TE
(2 HALVES)
ENCLOSURE
EARTH STUD
How the low level cable

entry plates can be fitted
COMMS CABLE
HOLES (x 4)
POWER/COMMS POWER CABLE

PLATE HOLE
BSS11_Ch4_53
Cable entry from beneath the enclosure
ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ
ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ ACCESS PANELS ENCLOSURE
IN BATTERY MOUNTED ON
CABLES FED TO COMPARTMENT SUITABLE
ENCLOSURE SUPPORT
FROM BENEATH ROOF FRAME BSS11_Ch4_54

Optional high
level cable entry
High level cable entry is from the left side of the enclosure only. Three blanking plates are
fitted to the enclosure as standard. These are removed to enable the three cable entry
plates supplied in the optional high level hardware kit to be installed.
NOTE
Use of this kit also requires the optional high level feeder cable kits.
One power/comms plate and two RF cable plates are supplied in the kit, and each of
these may be installed in any of the three positions to suit the required configuration.
Each cable hole in the cable entry plate has a plug fitted. These plugs are removed as
required when the cables are installed.

Typical high level cable entry plate arrangement
POWER/COMMS
PLATE
RF PLATES
BSS11_Ch4_55

Optional cable
shroud and
termination
bracket
An optional cable shroud is available for use with the high level cable entry kit. The
purpose of the shroud is to provide additional environmental protection for the cables at
the point of entry to the enclosure.
An optional termination bracket is also available for use in conjunction with the shroud.

Optional cable shroud and termination bracket
TERMINATION
BRACKET
SHROUD
BSS11_Ch4_56
NOTE
The cable shroud and termination bracket are future options and are not
available for use with the equipment covered by this release of the manual.

Overview of the power distribution equipment ISSUE 1 REVISION 2
Overview of the power distribution equipment
Operation of the
power
distribution
equipment
Power distribution within the enclosure is handled by the equipment identified in
Table 4-5.
Table 4-5 Power distribution equipment within the enclosure

Rack Equipment
designation
PDU A Rectifier module (x 2)
DC connector panel (for customer equipment)
PDU B AC power distribution unit (2 panels)
DC power distribution unit
Power control module
Rectifier module (x 3 max.) – two plus one for system
redundancy
AC power distribution
Three phase or single phase ac input power is supplied through the primary ac terminal
box to the 4-pole circuit breaker (AC ISOLATION SWITCH) on the upper panel of the ac
Power Distribution Unit (PDU). This circuit breaker is the primary isolator for all the
equipment contained in the enclosure.
When the circuit breaker is closed, ac power is fed from the breaker to a mains filter and
then through MCBs or an RCBO to the following equipment:
S The rectifier modules in PDU A and PDU B.
S The enclosure heater (mounted in the base of PDU A), via a thermostat switch.
S The cabinet lights and built-in 230 V ac service outlet sockets.
S The 230 V service power outlets (AUX 1, AUX 2 and HEATER AUX) on the lower
ac power distribution panel.
DC power is derived from the rectifier modules and is fed through MCBs in the dc power
distribution unit to the following equipment:
S Horizonmacro indoor BTS 0.
S Horizonmacro indoor BTS 1.
S HMS 0.
S HMS 1.
S COMMS 0 to COMMS 3 (on the dc connector panel in PDU B).
DC power from the rectifiers is fed to the Low Voltage Disconnect (LVD) contactors, the
fan trays in PDU A and PDU B, and the power control module.

ISSUE 1 REVISION 2 Overview of the power distribution equipment
View of the power distribution equipment in PDU A and

PDU B
PDU B PDU A
DC POWER
DISTRIBUTION
UNIT
RECTIFIERS
AC POWER
POWER DISTRIBUTION
CONTROL UNIT
RECTIFIERS
MODULE –48 V DC CONNECTOR
PANEL (FOR CUSTOMER
EQUIPMENT)
BSS11_Ch4_57

AC power distribution ISSUE 1 REVISION 2
AC power distribution
AC distribution
description
The ac supply to the Horizonmacro 12 carrier outdoor may be either 230 V nominal three
phase (star configuration) or single phase. The ac power is supplied to the ac power
distribution unit from the primary ac distribution box (see Chapter 2) through a fixed
5-core three phase power cable (3P + N + E). For single phase operation, the three
phases are linked at their inputs to the primary ac distribution box (links are supplied).
The ac power distribution unit filters the incoming ac supply and provides the primary
power isolation, in the form of a 4-pole circuit breaker (labelled AC ISOLATION
SWITCH). The status of each phase of the ac supply is indicated by LEDs on the front
panel.
NOTE
For single phase operation, all LEDs will be lit when the ac supply is connected
or unlit when the ac supply is disconnected.
The ac supply power distribution unit supplies ac power directly to each rectifier module,
the heater, the lights and the 230 V service outlet sockets through single pole circuit
breakers on the front panel.
AC circuit
breakers
Table 4-6 shows details of the ac power distribution circuit breakers.
Table 4-6 AC circuit breakers

Phase Reference Function Rating Trip type
1 CB 1/1 Rectifier 0 16 A C
CB 1/2 Rectifier 1 16 A C
CB 2/2 Heater Int 10 A C
CB 2/3 Heater Aux 10 A C
CB 2/4 Enclosure and service auxiliaries 10 A RCBO
CB 3/2 Rectifier 4 16 A C

ISSUE 1 REVISION 2 AC power distribution
Detailed view of the ac power distribution unit front panel
AC ISOLATION SWITCH RECT 4 RECT 3 RECT 2 RECT 1 RECT 0 HEATERHEATER

CB1 CB3/2 CB3/1 CB2/1 CB1/2 CB1/1 INT AUX CB2/4
CB2/2 CB2/3
HEATER AUX
BSS11_Ch4_58

AC power distribution ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 AC power distribution
Simplified circuit diagram for the ac power distribution
CB 1/1
RECTIFIER
0
CB 1/2
RECTIFIER
1
CB 2/1
RECTIFIER
1 2 3 N E 2
CB 3/1
RECTIFIER
3
LINE FILTER CB 3/2
RECTIFIER
4
CB 2/2 THERMOSTAT
1 2 3 N E HEATER
CB 1 INT
1 CB 2/3
HEATER
2 AUX
CB 2/4
3
RCBO AUX 1
N
AUX 2
E
X1 X2 X3 XN CABINET
AUX
BSS11_Ch4_59

DC distribution
description
The –48 V dc output from the rectifiers is fed to the dc power distribution unit. This
provides circuit breaker or fuse protected –48 V dc power outlets to the two BTS
cabinets, the two HMS units, the dc connector panel in PDU A, the power control
module, and the fan trays. The dc power for the smoke detector (–24 V) is derived from
the power control module.
The dc supply to the BTS cabinets is fed through a low voltage disconnect contactor
(LVD A). The backup batteries are float charged through a second low voltage disconnect
contactor (LVD B).
The dc supply to the BTS cabinets is monitored through the power control module. LVD
A monitors the dc supply from the backup batteries to the BTSs and disconnects the dc
supply if the voltage level drops to 41 V (+/–0.25 V), thus preventing deep discharge of
the batteries. LVD B disconnects the batteries from the system if the voltage level drops
further to 39.5 V (+/–0.25 V). The control circuitry ensures that the contactors are only
reset when the ac supply is restored and the batteries have recharged to a safe level.
The status of the LVD contactors is displayed on the power control module front panel.
The front panel also contains switches which allow manual control of the contactors (see
The power control module section in this chapter for further information).

Detailed view of the dc power distribution unit front panel
ALM SUPPLY ALM SENSE

FS1 T2AH FS2 T2AH
LVD A LVD B
FS3 T2AH FS4 T2AH
FAN 1 FAN 2 CB A1 CB A0 CB B5 CB B4 CB B3 CB B2 CB B1 CB B0
FS5 T2AH FS6 T2AH
BSS11_Ch4_60

DC circuit
breakers
This table shows details of the dc power distribution circuit breakers.
Table 4-7 DC circuit breakers

Breaker bank / Reference Function Rating Trip type
DC bus
A CB A0 BTS 0 63 A Long delay
A CB A1 BTS 1 63 A Long delay
B CB B0 Comms 0 4A Long delay
B CB B4 HMS 0 10 A Motor start
B CB B5 HMS 1 10 A Motor start
DC fuses
A fuse panel is mounted on the dc power distribution unit front panel. The fuses protect
the circuits shown in Table 4-8.
Table 4-8 DC fuses

Fuse no. Circuit protected Rating / Type
FS 1 Power control module supply 2 A / HRC
FS 2 Power control module negative sense 2 A / HRC
FS3 LVD A supply 2 A / HRC
FS 4 LVD B supply 2 A / HRC
FS 5 Fan tray in PDU A 2 A / HRC
FS 6 Fan tray in PDU B 2 A / HRC

Simplified circuit diagram for the dc power distribution
LVD A
CB A0
–48 V DC BTS 0
CB A1
BTS 1
LVD A
0 V DC CONTROL CB B0
Comms 0
CB B1
RECTIFIER Comms 1
V TRIM CB B2
Comms 2
CB B3
Comms 3
CB B4
HMS 0
CB B5
LVD B HMS 1
BATTERY
LVD B
CONTROL BATTERY
RETURN
REFERENCE
(M8 stud for connection
to principal ground bar)
BATTERY
THERMAL CHARGE
THERMAL
COMPENSATION
SENSOR
BSS11_Ch4_61

The power control module ISSUE 1 REVISION 2
The power control module
Overview of the
power control
module
The power control module provides the following functions for the power distribution
system:
S Monitoring.
S Control.
S Alarms interface
The power control module monitors the ac and dc supply and takes appropriate action
should a fault condition occur. Faults are indicated on the module front panel by the
associated LED being unlit and alarm conditions are signalled to the alarm interface
module (see Chapter 2). A reset button is provided to reset the system and clear alarm
conditions.
The module automatically controls the operation of the LVD contactors, although these
can be controlled manually using the BYPASS switch. It also automatically controls the
battery float charge voltage (54.5 V at 20 °C), although this can also be adjusted
manually using the VOLT ADJ potentiometer.
In addition to the above, the power control module provides a 24 V dc supply required to
power the enclosure smoke alarm.

ISSUE 1 REVISION 2 The power control module
Detailed view of the power control module front panel
BSS11_Ch4_62

Front panel
controls and
indicators
Table 4-9 describes the controls and indicators on the power control module.
Table 4-9 Power control module front panel control and indicator functions
Legend Type Normal/ Function
Alarm
state
O.T. OK LED Green/Off Indicates whether the overtemperature
alarm is functioning correctly.
SMOKE OK LED Green/Off Indicates whether the smoke alarm is
functioning correctly.
LVD OK LED Green/Off Indicates whether both LVD units are
operational and the contactors are being
driven at the correct levels.
REC ATT LED Off/Red Indicates whether the REC ATT button
has been pressed and the equipment is in
the receiving attention state.
CONT OFF LED Off/Red Indicates whether the BATT ON/OFF
button has been pressed and the battery
contactor (LVD B) is off.
AC OK LED Green/Off Indicates whether ac power is present on
at least one phase.
STATUS OK LED Green/Off Indicates whether the equipment status is
ok, no alarms are present and the
equipment is not in the receiving attention
state.
BATT Button –/– Toggles LVD B on or off.
ON/OFF
REC ATT Button –/– Puts the equipment in the receiving
attention state. Any alarms present are
masked for maintenance purposes.
RESET Button –/– Resets the power control module.
VOLT ADJ. Pot. –/– This is used to adjust the nominal float
voltage level.
BYPASSED LED Off/Red Indicates whether the bypass switch has
been set to ON.
BCA ON LED Green/Off Indicates whether the BTS contactor (LVD
A) is on.
BCB ON LED Green/Off Indicates whether LVD B is on.
BYPASS ON If set to ON, automatic control of the
BYPASS OFF Switch –/– contactors is overridden and both are held
in the on position to enable the power
control module to be “hot swapped”.


Alarm
management
The power control module provides the connection between the power system alarms
and the alarm interface module (AIM) through a 25-way D-type connector. The alarm
signal cable connects between J1 on the power control module and J3 on the AIM.
The pinouts on J1 are shown inTable 4-10.
Table 4-10 J1: Power system alarms

Pin Signal description Pin Signal description
1 AC 1 fail 14 AC 1 fail return
2 Smoke alarm 15 Smoke alarm return
3 O/T shutdown 16 O/T shutdown return
4 ANC smoke alarm trip 17 ANC smoke alarm trip return
5 – 18 –
6 Low voltage alarm 19 Low voltage alarm return
7 Rectifier 1 fail 20 Rectifier 1 fail return
8 Rectifier 2 fail 21 Rectifier 2 fail return
9 BTS smoke alarm 22 BTS smoke alarm return
10 Temperature sensor 23 Temperature sensor return
11 – 24 Aux supply 0 V
12 – 25 –
13 Aux supply 24 V
Alarm inputs
The alarm input signals accepted by the power control module are described here.
Overtemperature shutdown
The overtemperature shutdown signal causes the power control module to inhibit the
rectifiers and disable both LVD contactors, thus removing all dc power to the BTS
cabinets and communications equipment. The signal causes the power control module to
generate an ANC smoke alarm trip signal.
The overtemperature alarm signal is generated if the temperature reaches 70 °C and
shutdown of the equipment occurs if the temperature rises further to 80 °C.
The overtemperature shutdown alarm can only be reset by removing and re-applying ac
power or pressing the recessed reset button on the front of the power control module.

Smoke alarm shutdown

The smoke alarm shutdown signal operates in a similar manner to the overtemperature
shutdown signal, except that there is a 30 second delay before dc power is removed.
This signal also causes the power control module to generate an ANC smoke alarm trip
signal.
Like the overtemperature shutdown alarm, the smoke alarm shutdown alarm can only be
reset by removing and re-applying ac power or pressing the recessed reset button on the
front of the power control module.
BTS disable
If the dc supply to the BTS has been disabled due to an ac power failure and low voltage
disconnect condition, the BTS will not restart if the temperature within the enclosure is
below the minimum specified for BTS operation.
The dc supply is restored automatically when the temperature reaches an acceptable
level.
Alarm output
signals
The alarm output signals generated by the power control module are described here.
AC 1 fail alarm
The power control module combines the ac status monitor signal from each rectifier and
provides a single “AC 1 fail” alarm signal if the ac supply fails.
Rectifier 1 fail alarm

The power control module provides a non critical “Rectifier 1 fail” alarm signal if one
rectifier or rectifier cooling fan fails.
Rectifier 2 fail alarm

The power control module provides a critical “Rectifier 2 fail” alarm signal if more than
one rectifier or rectifier cooling fan fails.
Low voltage alarm

The power control module provides a “Low voltage” alarm signal if the backup batteries
have discharged to a voltage level where low voltage disconnect of the BTS cabinet(s) is
imminent (voltage < 43.0 V, +/–0.25 V). This initiates a controlled shutdown of the
equipment. The BTS cabinet(s) are disconnected if the voltage falls to 41 V (+/–0.25 V),
and the batteries are disconnected at a voltage level of 39.5 V (+/–0.25 V).
ANC smoke alarm trip

The power control module provides a control signal to trip the circuit breakers in an
external equipment cabinet when an overtemperature shutdown or smoke alarm
shutdown signal has been received.

The rectifier module ISSUE 1 REVISION 2
The rectifier module

The specifications and functional description on the rectifier modules, used in the 12
carrier outdoor Horizonmacro, are detailed in the Horizonmacro outdoor section under
the title “The Outdoor Power Supply Module (TOPSM)”.

ISSUE 1 REVISION 2 The rectifier module
View of the rectifier module
BSS11_Ch4_63

The dc connector panel ISSUE 1 REVISION 2
The dc connector panel
Description of
the dc connector
panel
The dc connector panel is mounted in PDU A, to the right of the rectifiers. It provides four
–48 V dc sockets for customer communications equipment, which can be mounted in the
6 U of rack space available in PDU A.
Power for the dc connector panel is supplied from the dc power distribution unit. Power to
each connector on the panel is controlled via a separate MCB on the front of the dc
power distribution unit (COM 0 to COM 3).

ISSUE 1 REVISION 2 The dc connector panel
View of the dc connector panel
ESP BONDING POINT
ESP
COMMS 0
GND
0V
–48V
COMMS 1
GND
0V
–48V
COMMS 2
GND
0V
–48V
COMMS 3
GND
0V
–48V
BSS11_Ch4_64

Internal battery backup ISSUE 1 REVISION 2
Internal battery backup
Overview of the
internal battery
backup system
The left side of the Horizonmacro 12 carrier outdoor enclosure is fitted with a closed two
shelf compartment for backup batteries. Four 12 V monoblocs are installed in the
compartment and connected in series to provide a –48 V dc supply in the event of a
failure of the ac supply. The backup batteries can power 12 carriers under full load
conditions for up to 40 minutes.
The batteries are connected to the enclosure dc supply through an isolator switch
mounted on the top of the battery compartment and the LVD B contactor. The circuit
breaker enables the backup batteries to be isolated from the system for maintenance
purposes.

ISSUE 1 REVISION 2 Internal battery backup
View of the internal battery backup compartment
BATTERY ISOLATOR
SWITCH
BACKUP
BATTERIES
COMPARTMENT
COVER
BSS11_Ch4_65

Internal battery backup ISSUE 1 REVISION 2
Battery thermal
charge
compensation
A thermal probe is connected to the positive battery terminal on the right battery in the
upper shelf, via an M8 copper ring terminal. This provides thermal charge compensation
by monitoring the battery temperature and adjusting the rectifier battery charge voltage to
the optimal level, thus maximizing the charge rate and battery life, and minimizing battery
gas discharge.
The thermal compensation is set at 4 mV/cell/_C, but is voltage clamped at the values for
0 _C and 40 _C to prevent battery overcharge at temperature extremes.
The thermal probe connects to J5 on the AIM and the signal from it then passes to J1 on
the power control module via J3 on the AIM.

ISSUE 1 REVISION 2 Internal battery backup
Internal battery connections
+VE CONNECTION
(BLACK CABLE) TO
ISOLATOR SWITCH
–VE CONNECTION
(BLUE CABLE) TO
ISOLATOR SWITCH
THERMAL PROBE
CONNECTS HERE
BATTERY LINK
BATTERY LINK
BSS11_Ch4_66

Horizonmacro digital modules ISSUE 1 REVISION 2
Horizonmacro digital modules

MCUF and NIU
redundancy
The mBCU can:
S Support two MCUFs at a BTS site, one master, one slave (for redundancy).
S Enable Master MCUF failure to result in slave MCUF becoming master after reset.
S Enable OMC operator to initiate master/slave MCUF swap.
S Configure CTUs by the master MCUF.
All four NIUs operate from the master MCUF, but each pair of NIUs depend on a BPSM
for power. All NIUs configure to the master MCUF clock.
NOTE
When fitting a replacement redundant MCUF, care must be taken to ensure
firmware compatibility with the master MCUF. Firmware incompatibility may
result in a loss of communication between the two MCUFs so that the
redundant MCUF is not in a position to take control in the event of a failure of
the master MCUF.
Full size and half

size modules
Modules are full size and half size as shown in Table 4-11,
Table 4-11 Full size and half size digital modules

Full size modules Half size modules
Main Control Unit with dual FMUX (MCUF) Network interface unit (NIU)
Alarm module Fibre optic multiplexer (FMUX)
BPSM (µBCU Power Supply
Module)
Overview
locations and
redundancy
Digital modules provide the micro base control unit (µBCU) functionality for the BTS site.
They are located in the bottom right side of the cage, and are electronically
interconnected through the backplane. Fibre optic connections are at the front of the
appropriate modules.
Each digital module is assigned A or B, with one BPSM (µBCU Power Supply Module)
for A and one BPSM for B. The alarm module is not assigned to A or B, as it is supplied
by both BPSMs for redundancy.
The master MCUF is assigned to A, and the redundant MCUF to B, each with an
associated FMUX.
The four NIUs are used by the operational MCUF, but two NIUs are powered by BPSM A
and two NIUs by BPSM B.
All slots are annotated with the legend of the appropriate module and located as shown
in the diagram opposite.

ISSUE 1 REVISION 2 Horizonmacro digital modules
Digital module and BPSM locations
REDUNDANT (B) MCUF B FMUX NIU NIU BPSM

B0 B1
ALARM
MODULE
µBCU CAGE
ASSEMBLY
MASTER (A) MCUF A FMUX NIU NIU BPSM
A0 A1
BSS11_4_67

Horizonmacro digital modules ISSUE 1 REVISION 2
Digital module
and CTU
connections
The MCUF is connected to the CTUs in the same cabinet through the backplane.
Optional connection to CTUs in up to three additional cabinets (six CTUs per cabinet) is
by fibre optic links. FMUXs, two internal to the MCUF and one half size module, convert
the electronic data stream into a fibre optic signal. An FMUX module in each extension
cabinet converts the fibre optic signal back to electronic data stream, for transmission to
CTUs via the backplane.
The NIU modules convert signals for terrestrial E1 or T1 lines.

ISSUE 1 REVISION 2 Horizonmacro digital modules
Digital module and CTU connections
E1/T1 E1/T1
NIUA0 NIUA1 NIUB0 NIUB1
TO EXTENSION 2 TO EXTENSION
2 FMUX MCUF CABINET FOR SIX
CABINET FOR SIX
FMUX TRANSCEIVERS
TRANSCEIVERS
2 TO EXTENSION
FMUX
CABINET FOR SIX
TRANSCEIVERS
2
TRANSCEIVER
(CONNECTIONS VIA BACKPLANE)
2
TRANSCEIVER
2
TRANSCEIVER
2
TRANSCEIVER
2
TRANSCEIVER
2
TRANSCEIVER
BSS11_4_68

Main Control Unit with dual FMUX (MCUF) ISSUE 1 REVISION 2
Main Control Unit with dual FMUX (MCUF)
MCUF overview
The Main Control Unit with dual FMUX(MCUF) provides the site processing functions,
apart from RF functions of the transceiver. The MCUF also provides switching for up to
six network interfaces (via four NIUs) and up to 24 transceivers.
The cabinet may contain up to two MCUF modules, one for redundancy. Each site and
module has an electronic ID for remote identification.
The MCUF provides the following functions:
S Maintenance and operational/control processing.
S Call processing (for example resource management and switching of baseband
hopping data).
S Switching of traffic and control information.
S Timing reference and network/BTS master clock synchronization.
S The functionality of two FMUX (see FMUX module and FMUX function in this
chapter).
S Support of up to six transceivers via backplane in first cabinet and up to an
additional 18 transceivers via FMUX connections to other cabinets.
S Support of up to six E1 or T1 circuits, via NIU modules.
S Support of the CSFP function via the PCMCIA flash memory card.
Capability to
replace MCU of
M-Cell6 and
M-Cell2
The MCUF combines the MCU function of M-Cell6 with two FMUX modules. If the
MCUF is installed in an M-Cell6 or M-Cell2 the MCUF automatically reverts to the
functionality of an MCU. The internal FMUX devices no longer operate. In M-Cell2 the
reversion to MCU mode includes ability to directly connect to two transceivers by
modified use of the front panel FMUX fibre optic connections.
NOTE
This capability to use MCUF in M-Cell6 and M-Cell2 is only possible with
GSR4 software release or later.
GPROC KSW and

GLCK functions
The MCUF/MCU module combines functions of older generation equipment:
S The Code Storage Facility Processor (CSFP) and Base Transceiver Processor
(BTP) functions formerly achieved by Generic Processor boards (GPROCs).
S The Kiloport Switch (KSW).
S The Generic Clock (GCLK).

ISSUE 1 REVISION 2 Main Control Unit with dual FMUX (MCUF)
Main Control Unit with dual FMUX (MCUF) functional

diagram
SIGNAL CONNECTOR TO BACKPLANE
TTY 2
INTERFACE
BDM PORT 2
3 3
MAIN RS232 MMI
PROCESSORS GPS
4 4 PIX
V.28 OUTPUT
RED LED
GREEN LED
EXTERNAL
SITE ID
RESET AND
WARM RESET RESET
SWITCHES
CONTROL 16/32 MBYTE

DATA DRAM
PCMCIA
INTERFACE PCMCIA
ADDRESS FAST FLASH
EEPROM
SLOW FLASH
EEPROM
6
NIU
ASIC REDUNDANT
MCUF
SYNC GPS 1PPS

BLOCK EXTERNAL
CLOCK
FLASH
2 EPROM
DEBUG PORT
RAM EXTERNAL
FIBRE OPTIC 6 FMUX
CONNECTORS MODULE
CTU x 6 VIA
FMUX IN 6 6 CTU x 6
2
OTHER FMUX IN SAME
CABINETS CABINET
(OR TCU x 6 2 6
VIA FMUX IN FMUX
M-CELL6
CABINETS)
BSS11_Ch4_69

Front panel
interfaces
TTY interface
A standard TTY interface is provided on the front panel, of 9.6 kbit/s (8 bits, No parity, 1
stop bit (8 N 1)). A local maintenance terminal can be attached to this port to use the
Man Machine Interface (MMI) of the MCUF.
Debug and BDM ports

Two front panel ports are for Motorola factory and development use only:
S The debug port, consists of a TTY connection to the sync processor to access
sync firmware, together with other connections to the ASIC and main processors.
S The Background Debug Mode (BDM) port is used for low level debugging of the
main processors.
FMUX fibre optic connections

There are fibre optic connections from the MCUF internal FMUX modules. The fibre
optic connectors enable connection to FMUX modules in other cabinets for additional
transceivers.
CAL port
The CAL port on the front panel of the MCUF can be used to calibrate the sync block
clock via MMI commands. The 8 kHz reference output is used in GCLK calibration
procedure (see Installation & Configuration BSS Optimization (GSM-100-423) ).
PCMCIA Interface
The PCMCIA card is located on the front panel of the MCUF, and is used for:
S Code Storage Facility Processor (CSFP) memory.
S Rapid site initialization.
The PCMCIA socket is an industrial standard 68 pin single socket, fitted with an ejector.
The PCMCIA interface supports rev 2.1 type I and II cards.
The 20 Mbyte card can be write enabled, for upgrade of site information, or disabled to
protect card use for other sites or secure the site code.

View of the Main Control Unit with dual FMUX (MCUF)

module
PROCESSORS
INTERNAL BACKPLANE CONNECT ORS

FMUX FIBRE
OPTIC
CONNECTIONS
TTY MMI
DEBUG POR T
CAL POR T
OSCILLATOR
BDM POR T
PCMCIA
STATUS LEDS
(RED & GREEN)
PCMCIA
RESET BUTT ONS
EJECT
(FULL – REMOVES SOFTW ARE FROM MEMOR Y
BUTTON
CPU – RESETS MCUF CPU)
BSS11_4_70

Front panel
switches and
indicators
The front panel of the MCUF module has two reset switches as shown the previous
diagram:
S FULL is a hard reset (power up - removes software from the memory).
S CPU is a soft reset (this resets the MCUF main processors, but the software
remains in RAM).
A hard reset results in the software being reloaded to the DRAM in the same way as
normal power up.
NOTE
During the CPU (soft) reset, pressing CPU reset again will perform a hard
reset. Double pressing of the CPU reset thus has the same effect as a hard
reset.
The MCUF has two front panel LEDs as shown in the previous diagram:, one green and
one red, with indications as shown in Table 4-12.
CAUTION
When red and green LEDs are flashing, the boot code is downloading into
non-volatile memory for software upgrade. Power should not be removed, nor
the cabinet reset, until downloading has been completed, as this will corrupt
the non-volatile memory. If bootcode is corrupted, contact Motorola CNRC
requesting the bootcode restoration procedure and the appropriate bootcode
file.
Table 4-12 MCUF front panel LED indication

Red Green Status
Off Off Board not powered up or in rest cycle
Off On Normal operation
On Off Fault condition
Flashing Flashing Non-volatile memory bootcode upgrade
(Do not remove power nor reset – see CAUTION)
PIX and GPS

interfaces
The MCUF provides four PIX outputs, driven at V. 28 levels. The four PIX outputs,
routed to the cabinet alarm board, enable relay contact control of external customer
equipment.
The GPS interface to the processor section is an RS232 compatible port. The 1PPS
signal is provisioned in the same connector, at V. 28 levels. This signal is fed to the sync
block as a reference. The GPS feature is not currently supported.


DRAM, flash
EPROM and code
loading functions
DRAM
The 16 Mbyte DRAM provides operational code and data storage for the main
processors. There is also a SIMM socket in the circuit board, enabling the addition of a
further 16 Mbytes if required. After software initialization, the DRAM uses ECC
protection. Memory protection is provided by the main processors.
Fast flash EPROM

The fast flash 1 Mbyte bank (256k x 32) is used for bootcode and executive process
code. It has a fast access time (<75 ns) , enabling direct execution. The bootcode is
factory set, and reprogrammed only in major software upgrades.
Slow flash EPROM

The slow flash 0.5 Mbyte bank (256k x 16) is used for non-volatile data storage of
diagnostic data and module ID information.
Code loading
The boot and executive code, held in the fast flash EPROM, initiates the MCUF on power
up or reset. If a PCMCIA memory card is fitted, operational code may be obtained and
copied to the DRAM for execution. If no card or code is available, the operational code is
obtained from the BSC.
Before execution, the operational code held in DRAM is checked with code held at the
BSC. The BSC downloads any changed code objects to the DRAM.
After successful checking of the DRAM operational code, the code is executed, and the
PCMCIA memory card updated with any changed objects.
CSFP code loading

If a PCMCIA memory card is available, then a code storage facility processor (CSFP)
function can be supported. A new software load can be downloaded in background,
without any reduction in service, and stored on the PCMCIA card.
Once the complete load has been transferred to the PCMCIA card, a code swap can be
initiated. The site is reset and the new software brought into service (<10 minutes). As a
precaution, the old version is held on the PCMCIA card to support a roll back to the
original version if required.


ASIC
functionality
The Application Specific Integrated Circuit (ASIC) provides central switching capabilities
for the MCUF. It is capable of supporting up to 24 transceivers, together with up to six
network interfaces and two links to the on-board processors, one link to the sync
processor and a link to the redundant MCUF. The link to the sync processor is used for
code loading purposes only. The ASIC supports baseband hopping across the 24
transceiver links.
The ASIC provides interface features associated with the transceiver links, these include
synchronization features to allow for delay in the link to the transceivers, and the
necessary framing and encoding to support the link.
All of the serial links into the ASIC are internal lines (I lines), 125 ms framed, with 32
eight bit timeslots per frame.
ASIC transceiver link features

The ASIC interfaces to a maximum of 24 transceiver links. The ASIC can switch any
timeslot on any of the transceiver links to any timeslot on other links connected to the
ASIC; transceiver links, network links, MCUF redundancy link or processor links.
The ASIC provides the following features associated with the transceiver links:
S Link advance/delay compensation.
The ASIC will continually measure the round trip delay on each transceiver link to
calculate a timing advance for each link. The link advance is applied, and can be
adjusted, by the main processor via the processor parallel interface.
S BBH data switching.
BBH switching is performed automatically on any timeslot configured as BBH data.
A single timeslot from the transceiver is selected for BBH routeing information, and
defines which transceiver link (0-23) should be used for downlink.
S Timing reference insertion.
The ASIC receives timing pulses from the sync block and inserts the appropriate
bits into the transceiver downlink synchronization and framing timeslots. The sync
block will provide a version of the 6.12 s and 60 ms signals that is advanced by
125 ms for this purpose.
S Manchester coding/decoding.
The transceiver links are all Manchester coded/decoded by the ASIC. This
function can be switched on or off (default on) on a per link basis. The disable
feature is for applications outside of the MCUF module.
ASIC/network and processor link switching

The ASIC supports a maximum of six network links and two main processor links. The
data to/from these links can be switched to/from any timeslot on other links connected to
the ASIC.
The two links to the main processor allow it to route HDLC and other links to the
appropriate place:
S 24 HDLC timeslots for the BCF RSS channel to each transceiver.
S Four timeslots for NIU control channels (two local, two redundant).
S Sync processor code load channel.
S Two channels for RSL links.
S One HDLC channel occupying up to three timeslots to the redundant MCUF.


Sync block
functionality
The sync block is controlled via the parallel interface of the main processors. The sync
block is responsible for site synchronization functions. It generates all required local
references from a high stability local clock source. This clock source may also be locked
to the incoming network clocks.
The sync clock source is in the form of a crystal oscillator (OCXO) which warms up for
phase locking in 4 minutes, and achieves frequency stabilization in 15 minutes.
Site frame reference generation and re-timing includes:
S 2.048 MHz - For serial communications.
S 16.384 MHz - For FMUX communications.
S 125 ms - For NIU framing and transceiver framing.
S 60 ms- For transceiver GSM timing.
S 6.12 s - For GSM superframe.
The reference clocks available to the sync block are:
S Six network extracted clocks (E1/T1 source via NIUs). Any of the NIU modules
under control of the MCUF can extract a reference clock from an E1/T1 link and
pass to the Sync block.
S GPS. This feature is not currently available.
S CAL port. The CAL port can be used to calibrate the sync block clock via MMI
commands. The reference output provides a monitoring point.
S Redundant MCUF link.
Phase Lock Loop (PLL) operating modes

The PLL uses the selected reference signal as the loop reference clock. It includes an
OCXO accurate to 0.05 ppm, a phase comparator and a loop filter. The PLL has the
following operating modes:
S Warm-up
The PLL is open loop and using the calibration frequency, but the OCXO is not yet
warmed up.
S Set frequency
The PLL is open loop and using the calibration frequency, and the OCXO is
warmed up.
S Fast tune
Closed loop with wide filter for coarse locking to the reference (extracted from
network clock/GPS).
S Fine tune
Closed loop with narrow filter for accurate locking to the reference (extracted from
network clock/GPS).
When in fine tune closed loop mode, the accuracy is 0.01 ppm.


Sync block code load

The sync block controller has a dedicated 2.048 Mbit/s serial link into the ASIC enabling
a 64 kbit/s HDLC channel to the main processors for code loading.
The sync block includes 256 k of flash EPROM used to store:
S Boot code.
S Operational code.
The boot code, which cannot be altered, queries the main processors on the current
version of the sync operational code.
If the stored operational code is the correct version, the boot code will move the
operational code to RAM and execute the code.
If the query results in the need for new operational code, the sync processor will
download the operational code from the main processors via the ASIC to the RAM in the
sync block.
After a successful download, the boot code programmes the flash EPROM with the new
operational code and runs the operational code in RAM.
GSM counters
The following counters are provided:
S GSM frame incremented every 4.615 ms, range 0 - 1325.
S GSM superframe incremented every 6.12 s, range 0 - 2047.
Link to
redundant MCUF
The link to the redundant MCUF is similar to a transceiver link, but does not have the
BBH capability, or the link delay measurement and compensation facility. The 6.12 s,
and 60 ms signals, are inserted into timeslots 8 and 16.
When the MCUF is in slave mode, timeslot and E1/T1 clock information is extracted from
the MCUF link and passed to the sync block.
The main processor HDLC link to the redundant MCUF can be routed in any unused
timeslot(s) of this link.
The ASIC can switch any timeslot on the redundancy link to any timeslot on any of the
other links connected to it such as the transceiver links, network links, redundancy link or
processor links.


The Network Interface Unit (NIU) ISSUE 1 REVISION 2
The Network Interface Unit (NIU)
Overview of NIU
The Network Interface Unit (NIU) module provides two E1 or two T1 termination links to
the terrestrial network. The NIU E1/T1 outputs are connected to a T43 or BIB board,
depending on the impedance matching requirement of the customer terrestrial circuits.
There are two types of NIU board, one for E1, one for T1. The NIU layout is common to
both E1 and T1, the only differences being in the associated crystal oscillators and line
matching resistor values.
An on-board NIU control processor provides network interface configuration and
supervision, controlled by the MCUF.
NIU functionality
The NIU provides two E1/T1 interfaces into the network (link 0 and link 1) as well as
LAPD encoding/decoding and clock recovery from a selected E1/T1 link. The second
E1/T1 interface (link 1) is not used for NIUs placed in µBCU positions at NIU A1 and NIU
B1.
An NIU control processor provides network interface configuration and supervision,
controlled by the MCUF. The NIU control processor maintains two independent control
links in the redundant configuration (one to each MCUF), each using timeslot 0 of MCUF
link 0.
NIU locations
The cabinet may contain up to four NIU modules in the mBCU, as shown in NO TAG.
Two NIUs are located in the master (lower) part of the cage. Two NIUs are in the
redundant (upper) part of the cage, though these upper NIUs are also used for
non-redundant purposes.
An NIU in slot A0 of the mBCU supports two E1/T1 links.
An NIU in slot A1 of the mBCU supports one E1/T1 link.
An NIU in slot B0 of the mBCU supports two E1/T1 links.
An NIU in slot B1 of the mBCU supports one E1/T1 link.

ISSUE 1 REVISION 2 The Network Interface Unit (NIU)
Functional block diagram of the Network Interface Unit

(NIU)
BACKPLANE CONNECTORS
RS232
RESET CONNECTION
SWITCH RESET
RED LED BDM

CONTROL CONNECTION
GREEN LED
PROCESSOR
DATA
DRAM
ADDRESS
XTAL
FLASH
EEPROM REDUNDANT
ÏÏÏÏÏ
MCUF LINK 0
REDUNDANT
ÏÏÏÏÏ MCUF LINK 1
ÏÏÏÏÏ
ÏÏÏÏÏ
ÏÏÏÏÏ
MASTER MCUF
MUX LINK 0
ÏÏÏÏÏ
DEMUX
MASTER MCUF
ÏÏÏÏÏ
LINK 1
ÏÏÏÏÏ
ÏÏÏÏÏ
TIMESLOT NETWORK
MULTIPLEXER FRAMER LIU E1/T1 LINK 0
ÏÏÏÏÏ EXTRACTED
ÏÏÏÏÏ
CLOCK 0
ÏÏÏÏÏ
REF 6.12 s
REF 125 ms
ÏÏÏÏÏ
REF 2.048 MHz
ÏÏÏÏÏ
ÏÏÏÏÏ FRAMER
EXTRACTED
CLOCK 1
ÏÏÏÏÏ
LIU NETWORK
E1/T1 LINK 1
ÏÏÏÏÏ
BSS11_Ch4_71

NIU command
identity number
Each NIU is identified in the database by an identity number, from 0 to 3. Table 4-13
shows the NIU slots and equivalent identity number.
Table 4-13 NIU slot and equivalent command identity

NIU (MSI) identity number NIU slot
used in commands
0 A0
1 B0
2 A1
3 B1
The NIU status is indicated by the two front panel LEDs, one green and one red,
controlled by the on-board processor, as shown in Table 4-14:
Table 4-14 NIU LED Display

Red LED Green LED Status of NIU board
Off Off NIU not powered up or in reset cycle
Off On Normal operation
Flashing Flashing NIU undergoing system code download
On On NIU self testing following switch on or
reboot.
Red LED extinguishes after 20 seconds, or
after 50 seconds following a reboot due to
code download.

View of the Network Interface Unit (NUI) module and LEDs
BACKPLANE
CONNECTOR
NIU GREEN
LED
NIU RED
LED
RESET/DISABLE
SWITCH
BSS11_4_72

Control
processor
The control processor interfaces to timeslot 0 of link 0 from each connected MCUF.
The processor uses 512 kbytes of Flash EPROM for boot code. operational code storage
and module ID. Code is executed directly from the Flash EPROM. The boot code can
be overwritten under control of the MCUF, if required.
The processor also has an on-chip 1 Mbyte of DRAM.
TTY Ports
The processing section provides two TTY ports for Motorola debugging purposes only.
Resets
The processor is capable of soft resetting itself. The front panel reset causes a hard
reset of the entire board. Power-on also resets the processor.
The MCUF is able to reset the NIU via a message on the HDLC link.
NIU/MCUF
framing and
clocks
The control processor is supplied with a clock from an on-board crystal oscillator, which
has an output enable pad for test purposes. The framer devices also have their own
crystal oscillators on-board.
The framer devices provide the decoded and jitter attenuated receive data, for passing to
the MCUF.
The framer devices also extract a 2.048 MHz/1.544 MHz clock signal from an E1/T1 link,
which is then passed to the MCUF synchronization circuit. At the MCUF, this signal is
used to phase lock a local 16.384 MHz clock signal. Once phase locked, three reference
clock signals are provided for NIU use:
S REF 2.048 MHz clock signal.
S REF 6.12 s clock signal.
S REF 125 ms clock signal.
The NIU transmit and receive framing is controlled by this 125 ms reference pulse
received from the MCUF.


Distance
measurement
The NIU provides the ability to perform network distance delay measurement on either of
the two network links. Measurement can only be performed on one link at a time.
Three modes of operation are possible:
S Mode 1. A pattern is transmitted in a selected network timeslot and the
corresponding receive timeslot is monitored for its return. The delay is measured
to an accuracy of ± 488 ns. The pattern is transmitted on the 6.12 second
reference signal.
S Mode 2. The receive link is monitored for the pattern. When received the pattern
is transmitted back in the next frame. The time between receipt and transmission
of the pattern is measured to an accuracy of ± 488 ns.
S Mode 3. The receive link is monitored for the pattern. When it is detected a
strobe is generated for the MCUF sync block.
Radio Signalling
Links (RSL)
The Radio Signalling Links (RSL) to the BSC from the main processor on the MCUF are
64 kbit/s LAPD links. The LAPD encoding of this RSL data is performed on the NIU by
the NIU control processor.
The RSL links between the MCUF and NIU must be sent as follows:
S RSL link 1 is embedded in the NIU control link; that is, it will be in timeslot 0 of link
0 to the NIU. This link is important for initialization.
NOTE
When the NIU is on a network link to a BSC or another BTS, the RSL can be
placed on either link on any default timeslot other than zero.
S RSL link 2 is on a different timeslot from that used for the network connection
The NIU will support a maximum of two RSL links. The RSL links may both be on a
single network link or shared between the two network links.
The NIU hardware supports switching for 64 k and 16 k LAPD channels.
T1 NIU need to
set link type
T1 NIUs and E1 NIUs cannot be interchanged. A T1 link line consists of 24 timeslots as
opposed to 32 timeslots for an E1 link line. A T1 link generates specific T1 alarms,
referred to as Red alarms. A T1 NIU supports the same MSI type of device transitions
as an E1 NIU.
The OMC operator should set the link type or it will default the site to an E1 system. In
ROM it is set by a ROM-only MMI command. In RAM it is a database parameter set by
a chg_element command.
The RSL default timeslots are the same for a T1 NIU and an E1 NIU. The basic
mechanism for communicating and configuring is also the same.


Type 43 interconnect board
Location
Plugs into the interconnect panel through via a 37-pin D-type connector.
Purpose
The T43 interconnect board matches the impedance between the pulse code modulation
(PCM) circuit lines and the BSU/RXU backplanes. The board interfaces up to six input
and six output unbalanced coaxial 75 ohm 2.048 Mbit/s lines to the external PCM circuit
lines through twelve type 43 coaxial connectors.
The T43 uses 12 transformers to provide impedance matching between the PCM circuit
lines and the multiple serial interface (MSI) modules. Each transformer has a 1:1.25 turns
ratio to match the external 75 ohm and backplane 120 ohm connections. Each input and
output is isolated from the backplane by up to 1500 V.
NOTE
Use the T43 for unbalanced lines.
Purpose
The Balanced-line Interconnect Board (BIB) matches the impedance between the Pulse
Code Modulation (PCM) circuit lines and the BSU backplanes. The board provides
interfaces for six input and six output balanced 120 ohm E1/T1 lines.
The board uses 12 transformers to match the impedance between the PCM circuit lines
and the Multiple Serial Interface (MSI) modules. Each transformer has a 1:1 turns ratio to
match the external and backplane 120 ohm connections.
NOTE
Use the BIB for balanced lines.
Overview of
T43/BIB-NIU
connection
The NIU network interface (E1/T1) links connect to a single CIM (T43) or BIM (BIB)
board on top of the cabinet by a single backplane connector and cable.

The T43 interconnect board
J0
J8 J4
J14 J10
J16 J2
J13 J11
J7 J1
J17 J5
BSS11_Ch4_73
The Balanced-line Interconnect Board (BIB)
J1
J0
BSS11_Ch4_73a
NIU to T43
mapping and
command ID
One T43 or BIB board is connected to the mBCU. Only six network interfaces are used,
three pairs to the Master NIU modules, and three pairs to the Redundant NIU modules.
Each NIU is identified in the database by an identity number, from 0 to 3, as shown in the
final column of Table 4-15.
NOTE
The Redundant NIU modules are only redundant in the sense of being
supplied by a different BPSM, and can thus continue to operate if the Master
BPSM fails. All NIUs are available for separate use.
Table 4-15 defines the mapping from the T43/BIB connector to NIU boards.

Table 4-15 T43/BIB connector to NIU boards

T43 Network V37 way D type NIU Location NIU identity
Side connections (MSI)
Connector (BIB)
used in commands
J1 1,20 NIU A0 - Tx1 MSI(NIU) 0
J2 2,21 NIU A0 - Rx1
J7 7,26 NIU A0 - Tx2 MSI(NIU) 0
J8 8,27 NIU A0 - Rx2
J13 13,32 NIU A1 - Tx1 MSI(NIU) 2
J14 14,33 NIU A1 - Rx1
J4 4,23 NIU B0 - Tx1 MSI(NIU) 1
J5 5,24 NIU B0 - Rx1
J10 10,29 NIU B0 - Tx2 MSI(NIU) 1
J11 11,30 NIU B0 - Rx2
J16 16,35 NIU B1 - Tx1 MSI(NIU) 3
J17 17,36 NIU B1 - Rx1

Block diagram of T43/BIB connection to NIUs
J
1
2
NIU A0
7
8
13
14 NIU A1
T43/BIB
J
4
5
NIU B0
10
11
16
17 NIU B1
J0
BSS11_Ch4_74

Fibre Optic Mulitplexer (FMUX) module and FMUX function ISSUE 1 REVISION 2
Fibre Optic Mulitplexer (FMUX) module and FMUX function
Overview of
FMUX module
and internal
MCUF FMUX
The Fibre Optic Multiplexer (FMUX) module is required to multiplex six full duplex
transceiver links onto a single fibre link, and demultiplex a single fibre link to six full
duplex transceiver links. This enables six transceivers in a single extension cabinet
(either Horizonmacro or M-Cell6) to be linked to the main cabinet MCUF.
The equivalent function of two FMUX modules exists internally in the MCUF, enabling
two extension cabinets to be connected. An FMUX module is required for a third
extension cabinet. This enables a total of four cabinets to be joined together as one BTS
site. A single cabinet has no need for an FMUX, because the MCUF connects with the
cabinet CTUs through the backplane.
The FMUX has two modes of operation:
S Working in conjunction with the MCUF to multiplex transceiver links to/from an
extension cabinet.
S Operating in the extension cabinet to supply the transceivers in that cabinet.
Two FMUX modules may be fitted in the mBCU cage, one to the master MCUF, and one
to the slave MCUF. An extension cabinet only requires one FMUX to connect to six
transceivers within the cabinet, plus one redundant module.
Each FMUX fibre optic link is full duplex 16.384 Mbit/s. The FMUX optical link is capable
of driving up to 1 km.

ISSUE 1 REVISION 2 Fibre Optic Mulitplexer (FMUX) module and FMUX function
View of the Fibre Optic Multiplexer (FMUX) module
Fibre optic input

from another FMUX
in another cabinet
at the site
Backplane
connector
Fibre optic output

to another FMUX
in another cabinet
at the site
BSS11_4_75

Fibre Optic Mulitplexer (FMUX) module and FMUX function ISSUE 1 REVISION 2
FMUX Functional
explanation
The MCUF transmits and receives a 2.048 Mbit/s data stream link to each operational
transceiver. This is achieved by the backplane in the same cabinet, without using an
FMUX.
If the transceiver is in an extension cabinet, the FMUX combines the data stream with up
to five others, and then converts the electronic signal to fibre optic, for onward
transmission to the extension cabinet.
At the extension cabinet, another FMUX converts the fibre optic signal back to electronic
form, for transmission to the transceivers.
The multiplexer/demultiplexer can support up to six transceiver links. It uses a
16.384 Mbit/s Manchester encoded serial data link organized as 256 x eight bit timeslots
in a 125 ms frame. Manchester coding is used to detect errors, indicated at timeslot zero
for each transceiver, enabling error correction at the other FMUX.

ISSUE 1 REVISION 2 Fibre Optic Mulitplexer (FMUX) module and FMUX function
Functional block diagram for the FMUX
BACKPLANE CONNECTOR
Rx FIBRE OPTIC
DATA RECEIVER MANCHESTER
ENCODED
TO FMUX IN
ANOTHER
CABINET
MUX / 2:1 TO MCUF (IF

Tx/Rx 6
DEMUX SELECT MAIN
6 CABINET)
TO CTUs OR
TCUs (IF
EXTENSION
TO FMUX IN CABINET)
ANOTHER
CABINET
SELECT
Tx FIBRE OPTIC CONTROL
DATA TRANSMITTER (FROM MCUF)
BSS11_Ch4_76

Alarm module ISSUE 1 REVISION 2
Alarm module
Alarm module
overview
The alarm module provides equipment with an external alarm system to report
operational status. The alarm module:
S Collects all cabinet alarms (received from the backplane).
S Provides current sensing for 16 customer inputs, referred to as site alarms. These
inputs are provided by the PIX connectors PIX0 and PIX1.
S Controls up to four relay driven outputs linked to customer equipment.
(Changeover contacts 30 V 1 A maximum). These outputs are provided by the
PIX0 connector.
S Transmits alarm information to all CTUs in the same cabinet.
S Provides power, signal conditioning and multiplexing for GPS signals (8 V to 36 V
dc).
The alarm module is located in the mBCU adjacent to the MCUFs. The alarm module is
designed to ensure correct location.
Alarm module
functionality
The alarm module receives inputs from:
S Cabinet PSMs (identifying type, manufacturer and slot number).
S Environmental control devices.
S Customer defined alarms.
The alarm board receives these inputs, encodes them, and then passes the code word to
all CTUs in the cabinet via the backplane.
Alarm module
replacement –
effect on alarms
The alarm module can be replaced while the cabinet system is running (hot
replacement). This will temporarily interrupt alarms, with the OMC receiving an additional
alarm module out of service alarm, which automatically clears upon correct
insertion of the replacement module.
Alarm collection
from extension
cabinets
Extension cabinet alarms are sent from the extension cabinet alarm module to the
extension cabinet CTUs. The CTUs transmit the alarms to the main cabinet, by using
the normal FMUX connection, for transmission to the MCUF.

ISSUE 1 REVISION 2 Alarm module
View of the alarm module
BACKPLANE
CONNECTOR
5 LED PAIRS
BSS11_4_77

Alarm module ISSUE 1 REVISION 2
Alarm module
display
presentation
All alarms indicators are green when equipment is functioning correctly, and red when
equipment is faulty. The locations are shown in Table 4-16.
NOTE
Only five of the ten front panel LEDs are utilised in the Horizonmacro indoor
equipment. Others are utilised in the Horizonmacro outdoor.
LEDs marked red in Table 4-16 are on in alarm state, and off in normal
operation.
LEDs marked bicolour in Table 4-16 (fans) are green when all fans are
operating correctly, and red if one or more fans are faulty.
Table 4-16 Alarm module list

LED Light Equipment monitored by light
location Colour (Green = OK, Red = FAULT)
states
1 (top) red Not used in Horizonmacro indoor
2 red Not used in Horizonmacro indoor
3 red Door 1 – main cabinet door open alarm.
5 red Low voltage disconnect (LVD) alarm (battery
backup option).
6 bicolour Fan Tray 0 fully operational (4-fan tray).
10 (bottom) red Not used in Horizonmacro indoor

ISSUE 1 REVISION 2 Alarm module

Horizonmacro RF Modules ISSUE 1 REVISION 2
Horizonmacro RF Modules
RF overview
The RF equipment provides a transmit and receive path between the mobile station and
the cabinet transceiver.
RF modules described
The following equipment is described:
S Compact Transceiver Unit (CTU).
S Sectorized Universal Receiver Front-end (SURF) module (for receive path).
S Several types of transmit block (Tx block). Tx blocks are used for various
configurations of transmit path, depending on number of antennas, CTUs and
functionality, including potential shared receive path.
S Cavity combining block CCB, used to combine three CTU transmit paths in
conditions where Synthesizer Frequency Hopping (SFH) is not required. Two
CCBs can combine up to six CTU transmit paths on to a single Tx antenna.
RF general information and loopback test function

The following additional information is presented in this chapter:
S General definition of transmit and receive functions in this RF equipment detail
section.
S An RF overview and RF test function description in the next section.
S An explanation of frequency hopping in a section immediately after the CTU
section.
These descriptions are intended to assist the reader in understanding the information on
the RF modules.

ISSUE 1 REVISION 2 Horizonmacro RF Modules

Receive RF
hardware
Receiver RF hardware consists of the SURF module and optional Tx block receive path,
and the receive section of the CTU.
The SURF module provides bandpass filtering and low-noise amplification for up to three
sectors, with diversity receive antenna signals, together with switching to CTUs.
CTU Rx role
The CTU provides the following receive functions:
S Receiver tuning (on a timeslot basis) to any receive channel frequency.
S Demodulation and equalization of the receive channel signal.
S Measurement of the received signal strength indication (RSSI) and signal quality.
S Recovery of received data from the demodulated radio channel.
S Channel decoding of the received data and processing of the recovered signal.
Traffic data is passed on to the MCUF for routing to the MSC.
S Digital interface to the SURF module, which controls selection by the SURF switch
of the receive signals from the appropriate antenna.
S Comparison and processing of an additional receive path from a second antenna
input to support diversity.
Transmit (Tx) RF
hardware
Transmit RF hardware consists of Tx blocks in appropriate combinations to meet
requirements of antenna sharing for the transceivers.
CTU Tx role
The CTU provides the following transmit functions:
S Transmit tuning (on a timeslot basis) for generation of any transmit channel RF
frequency.
S Encoding transmit data output.
S Digital modulation of transmit data onto the transmit radio channel signal.
S Final RF power amplification and output power level control of the transmit radio
channel RF signal.
S When using a CCB, the output of control data to the CCB.
S Channel encoding of the data to be transmitted, interleaving signal and traffic
channel data, as defined by ETSI.
Rx/Tx single
antenna
duplexing
Duplexers allow a single antenna to be used for both transmit and receive operations.
Duplexers exist within several of the transmit blocks.


RF main
component
explanation
The RF equipment consists of three main blocks:
S The CTU.
S The SURF module.
S The Tx block or alternatively CCBs.
CTU
The CTU can receive two inputs, Rx1 and Rx2, from the SURF. These inputs are
converted into digital voice/data. The two Rx signals provide diversity of the Rx function
from the MS (uplink).
The CTU also generates a Tx data signal, translated from received digital voice/data,
which is transmitted by cable to the Tx block for antenna transmission to the MS
(downlink).
The third (middle) port provides an RF loopback test signal capability, for automatic
transmission of RF test signals to the SURF.
SURF module
The SURF module accepts up to three pairs of receive antenna inputs, and switches the
inputs to the appropriate CTUs under the control of the MCUF. There are two inputs to
each CTU for Rx diversity.
The SURF also contains loopback test circuitry, connecting with a test signal from each
CTU.
Tx block
There are up to three Tx blocks, each block serving two CTUs.
Tx blocks filter the transmit signal for the required Tx band. Tx blocks also use filters to
enable the Rx frequency signal to be passed to the SURF, if one antenna is used for both
Tx and Rx signals.
CCBs
Cavity combining blocks (CCBs) are an alternative to Tx blocks. CCBs combine up to
three CTU transmit paths. Two CCBs can combine up to six CTU transmit paths. CCBs
have no duplexing capability and must be connected to an antenna via an external high
power duplexer (HPD). CCBs cannot be used with SFH (see Frequency Hopping).

Functional block diagram showing the basic RF and

loopback/VSWR test functions
Rx ANTENNA
BRANCH 2
Tx ANTENNA
Rx ANTENNA (ALSO Rx IF Rx FILTER
BRANCH 1 Rx ANTENNA FOR CONNECTED TO SURF)
BRANCH 1 OR BRANCH 2
(BRANCH 2 SHOWN)
SURF
(ONE OF THREE
RECEIVE
SECTIONS
SHOWN)
Rx FILTER
Tx FILTER
SPLITTER
Tx BLOCK (ONE OF
UP TO THREE)
ONE CTU Tx INPUT
SHOWN
COMBINER
OF SIX CTU
SWITCH (CONTROLLED BY MCUF) LOOPBACKS
Tx
RF
Rx1 Rx2 LOOPBACK
CTU
(ONE OF SIX)
SPLITTER
FINAL STAGE PA
OF CTU Tx
Rx
DOWNCONVERTER
For clarity only one CTU, one TX block and one section of the SURF module are
shown. CCBs could be used instead of TX blocks, however these would only be
available for use with Horizonmacro indoor cabinets fitted with a stacking bracket.
BSS11_Ch4_78

RF loopback
purpose
The loopback test function is primarily used to identify faults when the RF system has
failed. The loopback test function enables a diagnostic capability at the OMC, by
creating a test signal to identify if the fault is either:
S Software (that the OMC can correct).
S Particular hardware (CTU or SURF).
The result is a reduction in site assessment visits, and avoidance of unnecessary visits
when hardware is functioning correctly.The RF loopback test feature available on the
Horizonmacro, is not available on previous generations of equipment. The RF loopback
hardware described requires software availability beyond initial GSR4.
RF loopback
hardware
The RF loopback test function is essentially a hardware capability built into the CTU and
the SURF. Software instructions activate the test hardware, to route test signals through
the RF system.
RF loopback
software
operation
When provided with suitable software, beyond initial GSR4, the OMC can operate the
loopback test functions, and receive the results of the tests.
Description of RF
test modes
The following description should be read in conjunction with the RF functional diagram.
The RF test capability described requires software availability beyond initial GSR4
The loopback test hardware picks up an attenuated signal by coupled link from the
normal CTU transmit signal.
The signal is mixed down to the receive band for testing the Rx functionality of the SURF
and CTU. Power to the loopback circuitry is automatically turned off when the radio is in
normal operation.
SURF test mode

The loopback signal is injected into the antenna receive path of the SURF by coupled
link. This tests the complete SURF and CTU Rx system path.
Test of CTU Rx circuitry

The loopback signal is injected directly internally into the Rx input of the CTU. This tests
the receive portion of the CTU.
VSWR test mode

The test signal, at Rx frequency, is injected into the antenna port through coupled link on
the SURF. Reflected power is monitored by the receive system to calculate VSWR.
Detection of a high VSWR may indicate the presence of a cable or antenna fault.


The Compact Transceiver Unit (CTU) ISSUE 1 REVISION 2
The Compact Transceiver Unit (CTU)
Overview of CTU
This section provides the technical description of the Compact Transceiver Unit (CTU).
NOTE
The CTU can only be used in the Horizonmacro.
The CTU:
S Generates the RF frequencies required to perform the transmit and receive
functions.
S Contains the digital circuits required for eight timeslots of channel equalization,
encoding and decoding, and transceiver control logic.
The CTU provides the air interface between a BSS and MSs, with the following features:
S Capability of diversity reception (input from two antennas) which improves the
quality reception in the presence of multipath fading and interference.
S Frequency change on a timeslot basis for frequency hopping and equipment
sharing.
S Transmit power control.
CTU Tx RF output specification

For Tx RF output, see Technical Description: GSM-205-323 Overview and
specifications .
Location and requirements

The CTU shelf assembly is adjacent to the mBCU cage assembly in the base of the
cabinet.
The cabinet can contain six CTUs. A minimum of one CTU must be fitted in each
cabinet.
CTU internal
boards
The CTU is a single Field Replaceable Unit (FRU), which contains:
S CTU transceiver (XCVR) board.
S Power Amplifier (PA) board.
S Power Supply Unit (PSU).

ISSUE 1 REVISION 2 The Compact Transceiver Unit (CTU)
Functional block diagram showing the CTU input/output
LOOPBACK RECEIVE
RF OUT (TO SURF)
XCVR BOARD
CHANNEL 1 RECEIVE RF IN
CHANNEL 2 RECEIVE RF IN
(FROM SURF) RSSI
I1 DATA
Rx
Q1 DATA
I2 DATA
Q2 DATA
Rx ALARMS
AGC DATA
Tx PA DETECTOR AND TEMPERATURE
READING (DIGITAL SIGNAL)
Tx SYNTH SEL
LOCK ALARMS
SYNTHESIZER
13 MHz REF IN
Rx SYNTH SEL
SYNTH DATA
DIGITAL
CONTROL AND
SIGNAL
PROCESSING
Tx CLK
Tx SYNC
Tx DATA (MODULATOR)
RF
Tx KEY LOOP
BACK
PWR CONTROL DATA
Tx
Tx ALARMS
2.048 Mbit/s DATA INPUT
AND 2.048 MHz CLOCK INPUT
Tx RAMP CONTROL
(MANCHESTER ENCODED
DATA FROM MCUF)
2.048 Mbit/s DATA OUTPUT

AND 2.048 MHz CLOCK OUTPUT TEMPERATURE
POWER
(MANCHESTER ENCODED CCB DATA AND PA
AMPLIFIER DETECTOR
DATA TO MCUF) BOARD (ANALOGUE
SIGNAL)
RF Tx
PSU ALARMS
OUTPUT
POWER SUPPLY UNIT
27 V FOR ALL BOARDS IN
CTU
BSS11_Ch4_79

CTU connectors
and reset
The TTY RS-232 serial port has three serial links onto the 9-way connector:
S Equalizer and Control Processor (EQCP).
S Channel Coder Control Processor (CCCP).
A test interface port on the CTU front panel provides access to critical test points for
factory alignment and maintenance.
Momentary operation of the reset push button generates a hard reset of the processor,
which initiates a normal power-up sequence. The CTU is then operational.
Table 5.2 shows the connector functions.
Table 4-17 CTU front panel connectors

Front panel legend Function Connection to
Tx OUT Transmitter RF output Tx Block
TTY INTERFACE Test access to processor Three RS-232s
TEST INTERFACE Factory use Test equipment
Alarm reporting
The CTU status is displayed, as LED indicators, on the front panel as detailed in
Table 4-18. Major sub-systems, such as synthesizers and RF amplifiers, are monitored,
with alarm signals as necessary.
Table 4-18 CTU front panel status indicators

Indicator LED When the LED is Then CTU
RADIO OFF Module off
STATUS
Flashing green Code required or being loaded
Solid green Normal operational mode
Flashing yellow Test mode
Solid yellow Radio inhibited
Solid red Alarm condition
Transmit (Tx) OFF Transmitter is off
STATUS
Solid yellow Transmitter is keyed on
RADIO Both LEDs fast Non-volatile memory bootcode
STATUS AND flashing upgrade
TRANSMIT (Do not remove power nor reset)
(Tx) STATUS
(see CAUTION)

View of CTU with main features identified
M4 MODULE ATTACHMENT BACKPLANE POWER AND

SCREW SIGNAL CONNECTOR
Tx OUT
CONNECTOR
Rx1
LOOPBACK
TEST PORT
TEST INTERFACE
Rx2
HANDLE
TTY INTERFACE
CONTROL
PROCESSOR
RADIO STATUS LED
MANUAL RESET
(RECESSED BUTTON)
Tx STATUS LED
SCREW
BSS11_Ch4_80

CTU Tx function
IQ modulator
The first diagram opposite is a functional diagram of the IQ modulator. IQ modulator
data for eight timeslot channels is applied to the modulator state machine. This data is
encoded, serial-to-parallel converted and split into quadrature components. The
quadrature components are D/A converted and applied to a quadrature modulator to
create a Gaussian Minimum Shift Keyed (GMSK) carrier at an Intermediate Frequency
(IF).
IF and exciter stages

The second diagram shows a functional diagram of the IF and exciter stages. The low
level modulated carrier is applied to a combination of analogue and digital attenuators for
RF power control. The power control data comes from the digital sections of the XCVR.
The output of the power control elements is further amplified by an exciter chain to drive
the power amplifier.
The GMSK modulated IF is filtered and applied to the input of a controlled gain amplifier
for transmitter pulse sloping (ramped). The ramped signal is filtered and then mixed with
the main transmitter injection and is upconverted to the final transmit channel frequency.
Power amplifier board

The third diagram opposite shows a functional diagram of the Power Amplifier (PA). The
PA board provides amplification and a forward power detector. The isolator protects the
PA board amplifiers. The detected output is used to adjust the final CTU RF power
output level by the digital sections of the XCVR.
The PA board consists of six functional blocks:
S RF power amplifier.
S RF forward power directional coupler.
S RF forward power detector.
S Temperature sensor.
S CCB control.
S RF loopback circuit.
The isolator performs two functions:
S Isolates multiple transmitters to reduce intermodulation distortion.
S Protects the RF power amplifier from possible damage resulting from load
mismatches.

CTU Tx function
IQ modulator functional diagram
DAC AMPLIFIER
MODULATOR
STATE
IQ MACHINE
MODULATOR
DATA DAC
BSS11_Ch4_81
IF and exciter functional diagram

EXCITER
MIXER
DISTRIBUTED GAIN AND
FILTER RAMPING FILTER
POWER CONTROL
BSS11_Ch4_82
Power amplifier board functional diagram
RF LOOPBACK
DIRECTIONAL DIRECTIONAL
RF POWER COUPLER
AMPLIFIERS COUPLER
ISOLATOR
RF OUTPUT
TEMPERATURE LOAD
SENSOR
RF FORWARD CCB
LOOPBACK DATA
POWER
DETECTOR INJECT
PA BOARD
BSS11_Ch4_82a

CTU Rx function
The receiver part of the CTU accepts two amplified and filtered receive antenna signals
from the SURF module. These two signals are applied to inputs (branch 1 and branch 2)
of the CTU transceiver board. The diagram opposite shows a CTU receiver functional
diagram for one branch.
The input from the SURF module is filtered, amplified and down converted to ensure the
signal level and frequency range are correct for the next stage.
RSSI data (applicable only to GPRS and RACH bursts) is used for automatic gain control
(AGC) to ensure signal strength is correct for the intermediate frequency (IF) stage.
The primary function of the IF is to filter and amplify the incoming signal.
The path is demodulated into quadrature signals and filtered by baseband analogue
filters. These signals are then digitized (I1/I2 data and Q1/Q2 data) and made available
to the equalizer for the purposes of receive synchronization and data recovery.

CTU receiver functional diagram for one branch
RSSI
ADC I DATA
Rx INPUT IF
ADC Q DATA
AGC DATA
BSS11_Ch4_83

CTU digital
processing and
control functions
The CTU digital processing and control function provides control and RF processing for
that CTU. These functions include:
S 2.048 Mbit/s links which interface with up to two MCUFs for redundancy.
S A software processing platform for the Radio SubSystem (RSS)
S A Digital Signal Processor (DSP) for radio control and channel equalization
(EQCP).
S A DSP for channel coding, data routeing, and baseband hopping (CCCP).
S Control of RF systems: diversity receiver, transmitter, and power amplifier.
S Alarm monitoring of internal devices and external cabinet elements.
S Control of external modules including CCBs, and SURF.
S Maintenance ports for processor TTY, test point sub system, and CTU test
connections.
2 Mbit/s TDM Links

The CTU interfaces to the redundant MCUF are by 2.048 Mbit/s links on the backplane
(or FMUX modules in extension cabinets). These links are Manchester encoded, thus
providing both clock and data in a single connection. The recovered clock provides a
frequency reference for the CTU. The Rx and Tx circuitry supports FMUX fibre optic
lengths of up to 1 km.
The TDM links are formatted into 32 x 64 kbit/s timeslots to provide:
S Downlink and uplink TRAU speech data.
S Downlink baseband hopping data to be routed to/from other CTUs.
S Cell site air interface synchronization.
S HDLC channel for control information between RSS and MCUF.
S Baseband routeing information to indicate source of downlink baseband hopping
data.
RSS processor
The RSS processor function communicates with:
S The MCUF via dedicated 64 kbit/s timeslots in the TDM link.
S The rest of the digital control functions by the peripheral communications interface
(PCI) bus.
S A dual port interface for communication with the CCCP.
A TTY interface is also provided for user support.
The RSS processor memory includes flash EPROM and 8 Mbytes of DRAM. Flash
EPROM is used for code storage.

CTU digital functional diagram
TPS
TRAU DATA
REDUNDANT TDM
INTERFACE CCCP DSP
2.048 Mb LINK
HDLC LINK PCI

BACKBONE
RSS
TTY TO ALL EQCP DSP
PROCESSING
PROCESSORS
Rx INTERFACE
CTU INTERFACE Tx INTERFACE
FUNCTION SYNTHESIZER INTERFACE
PA INTERFACE
BSS11_Ch4_84

EQCP processor
The EQCP processor handles all radio control functions and the channel equalizer
function. The EQCP controls the Rx and Tx function via the CTU control function on a
per timeslot basis. These EQCP functions include:
S Alarm management.
S Downlink burst building and modulator control.
S Transmitter power control.
S Synthesizer channel control.
S RF frequency hopping.
S Receiver front end and remote tune combiner control.
S Uplink synchronization and equalization.
S Diversity receiver control.
S Receiver Automatic Gain Control (AGC).
S Receive signal strength (RXLEV) calculation.
S Timing advance calculation.
S Support of front panel indicators.
The EQCP communicates with the rest of the digital control functions via the common
PCI bus interface. A TTY interface is provided for radio level calibration, system
monitoring, and CTU level test.
CCCP processor
The CCCP processor handles all the GSM specified layer 1 channel encoding and
decoding functions for speech and control data associated with the air interface. In
addition, it manages the routeing of TRAU frames and Baseband Hopping (BBH) data,
via the TDM interface, to and from the MCUF. The CCCP functions include:
S Uplink channel decoding.
S Downlink channel encoding.
S GSM specified encryption algorithms.
S Baseband frequency hopping.
S TRAU frame collection and synchronization.
S Alarms management.
The CCCP communicates with the rest of the digital control functions via the common
PCI bus interface. A dual port RAM (DPR) is also used in the downlink direction for
communications from RSS. In addition to the TDM function, a serial link is provided to
support uplink and downlink TRAU data.


CTU interface function

The CTU interface function provides the air interface timing and radio control circuitry
required for Rx (uplink) and Tx (downlink) control functions. A common PCI bus allows
all the processing elements including the RSS processor, EQCP, and CCCP to
communicate with the various CTU functions. The CTU interface includes:
S Master GSM air interface timing function.
S Independent Rx gain control interface for each diversity receiver branch.
S Baseband Rx data interface for each diversity receiver branch.
S Receiver front end and CCB control.
S Tx data interface including GMSK modulator which provides baseband data to the
transmitter.
S Tx and power amplifier power control interface.
S Rx and Tx frequency synthesizer control which supports RF frequency hopping.
S CTU and cabinet alarm data collection.
S Alarms sampling and multiplexing.
CTU
uplink/downlink
Downlink traffic data flow

Downlink TRAU data from the MCUF is received by the TDM function then routed to the
CCCP function where it is encoded (cyclic, block, and convolutional), interleaved, and
encrypted to GSM recommendations. Signalling messages are also received from the
RSS processor and encoded. These traffic and control messages are built into air
interface frames and then routed back to the MCUF via the TDM function for baseband
hopping. The CCCP calculates a BBH routeing word, which informs the MCUF of the
radio link to be the source of its post hopped data. The post hopped data is then once
again sent back down to the appropriate CTU where it is received by the TDM function
and passed to the EQCP function. The EQCP inserts midamble and guard bits to the
data bits and forwards the data on to the modulator for transmission. The EQCP also
programs the CTU for the correct RF channel and transmit power level for this
transmitted burst.
Uplink traffic data flow

Baseband uplink traffic and control data messages are received by the CTU interface
function and sent to the EQCP where they are equalized. The EQCP also calculates
timing advance and RXLEV information, which is forwarded to the RSS process. The
recovered data bits are forwarded into the CCCP process, where it is de-interleaved,
decoded, and decrypted into TRAU frames. Control messages are passed to the RSS
function, while TRAU frames are sent to the MCUF via the TDM interface.


Frequency hopping ISSUE 1 REVISION 2
Frequency hopping
Overview of
frequency
hopping
The CTU supports two types of frequency hopping, Synthesizer Frequency Hopping
(SFH) and Baseband Frequency Hopping (BBH). This section provides an explanation of
both types. In both cases, the MS switches channels after every transmit/receive
(Tx/Rx) burst pair. The difference between SFH and BBH is in the method by which
channel switching is achieved at the BTS.
Synthesizer
Frequency
Hopping (SFH)
SFH uses the frequency agility of the CTU to change Tx/Rx frequency on any Timeslot
(TS), without affecting other timeslots.
SFH can only be used with wideband combining.
With SFH, each TS is allocated a number of frequencies (max 64) over which to perform
the hopping. When determining the hardware requirement for CTUs using SFH the
following rules apply:
S A minimum of two CTUs are required per cell due to BCCH requirements.
Timeslot 0 of CTU 0 is used for the BCCH carrier as shown. CTU 0 cannot use
SFH. Only CTU 1 and additional CTUs can use SFH.
S Hopping through the BCCH carrier (using the BCCH carrier frequency as one of
the SFH frequencies) is permitted except for timeslot 0. However, the
corresponding timeslot for the BCCH CTU will be switched off for this period.

ISSUE 1 REVISION 2 Frequency hopping
Minimum SFH requirement
CTU 0 (BCCH) CTU 1(USED FOR SFH)
0 (BCCH) 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
BSS11_Ch4_85

SFH example not

through BCCH
CTU 0
In this example of SFH, CTU 0 provides the BCCH and cannot frequency hop. CTU 0
has to transmit at maximum cell site power to meet the BCCH requirement. Timeslots
are used as shown below:
S TS 0 = Combined BCCH TS (BCCH/CCCH/DCCH). Transmitted at maximum cell
site power.
S TS 1-7 = Traffic channels, all non-hopping. All traffic channels transmit at
maximum cell site power.
CTU 1 and additional CTUs

CTU 1 and any additional CTUs provide SFH traffic channels as shown below:
S TS 0-7 = Frequency hopping traffic channels. The frequency allocated to the
BCCH of CTU 0 cannot be used for frequency hopping purposes.
SFH example
hopping through
BCCH carrier
CTU 0
In this example of SFH, CTU 0 provides the BCCH and cannot frequency hop. CTU 0
has to transmit at maximum cell site power to meet the BCCH requirement. Timeslots
are used as shown below:
S TS 0 = Combined BCCH timeslot (BCCH/CCCH/DCCH). Transmitted at maximum
cell site power.
S TS 1-7 = Unused timeslots transmitting dummy bursts for BCCH. All channels
transmit at maximum cell site power.
CTU 1 and additional CTUs

CTU 1 and any additional CTUs provide SFH traffic channels as shown below:
S TS 0 = Frequency hopping traffic channel, but prevented from using BCCH
frequency.
S TS 1-7 =Frequency hopping traffic channels, using all available frequencies,
including BCCH.
When the SFH selects the BCCH frequency, the CTU transmits at maximum cell site
power and the corresponding TS on CTU 0 is switched off for this period.


Base Band
frequency
hopping
Base Band Hopping (BBH) requires all eight timeslots of the CTU Tx (downlink) at the
same frequency. In the Rx (uplink) direction, the frequency agility of the CTU is used to
change timeslot frequencies on a timeslot basis. The BCCH frequency is always
transmitted at maximum cell site power.
BBH can use either Tx blocks or CCB Tx combining equipment. The main reason for
using BBH instead of SFH is to enable frequency hopping when using CCBs, because
the mechanical tuning of CCBs is too slow for SFH.
The number of CTUs required to support BBH is as follows:
S Number of frequencies used = number of CTUs
In the figure opposite MSs A, B and C are using TS 5 of CTUs 0, 1 and 2 respectively.
If the MSs are using cyclic hopping across ARFCNs 10, 20, 30 (an example using EGSM
900), each MS must transmit a burst of information each TDMA frame (4.615 ms) on a
different frequency. The data for the burst is received by each CTU in turn (ARFCN 10,
20, 30), as shown in Table 4-19:
Table 4-19 BBH sequence example (EGSM 900)

Burst Sequence CTU 0 CTU 1 CTU 2
Steps Tx Rx Tx Rx Tx Rx
1 A10 A10 B20 B20 C30 C30
2 C10 A20 A20 B30 B30 C10
3 B10 A30 C20 B10 A30 C20
4 (same as 1) A10 A10 B20 B20 C30 C30
5 (same as 2) C10 A20 A20 B30 B30 C10
6 (same as 3) B10 A30 C20 B10 A30 C20
In the uplink direction the controlling CTU tunes TS 5 in accordance with the frequency
expected from the MS for that particular burst.

BBH example
CTU 0 (BCCH) CTU 1 CTU 2

ARFCH=10 ARFCH=20 ARFCH=30
CTU 0
AT MAX 0 0 0
POWER 1 1 1
2 2 2
3 3 3
4 4 4
5 A 5 B 5 C
6 6 6
7 7 7
BSS11_Ch4_86

Transmit
The transmit is described by the following, as shown in the diagram opposite:
1. Traffic data from the network is passed through the NIU to the MCUF. Within the
MCUF an ASIC switches the data to CTU 0 (the dedicated CTU for this particular
MS call example).
2. The CTU, having processed the data (channel coding, interleaving, encryption and
routeing information) then passes the data back to the ASIC.
3. The ASIC follows the BBH routeing information to direct the data to the next Tx
CTU in the sequence of Table 4-19.
NOTE
BBH differs from normal and SFH CTU Tx procedures, in that the data is
directed to CTUs in a cyclic sequence at stage 3. Without BBH, stage 3
always routes data to the original CTU.
Receive
Data from the MS is received by one CTU allocated to that MS (in this case CTU 0). The
CTU will synthesize hop to the Rx signal. This ensures that the handover and equalizers
within only one CTU will be connected to a particular MS.

Schematic of Base Band Hopping (BBH) example
Tx CYCLES
THROUGH CTU
SEQUENCE NIU
ASIC
MCUF
3
3 1
2
CTU2 CTU1 3 CTU0
BSS11_Ch4_87

The Sectorized Universal Receiver Front end (SURF) module ISSUE 1 REVISION 2
The Sectorized Universal Receiver Front end (SURF) module
SURF module
overview
The Sectorized Universal Receiver Front end (SURF) module is located in a vertical slot
at the rear of the cabinet top panel. Three connectors on the underside of the module
connect to the SURF harness which provides connectivity to up to six Compact
Transceiver Units (CTUs). Antenna connections are located on the top of the unit.
There are two types of SURF module:
S 1800 SURF
S 900 SURF (dual band)
The 1800 SURF contains three amplifier sections for connection to three pairs of receive
antenna inputs providing 1800 MHz reception. The 900 SURF contains three amplifier
sections for connection to three pairs of antennas providing 900 MHz reception and,
being dual band, a further amplifier section for connection to a pair of 1800 MHz receive
antennas.
Each amplifier section provides two receive outputs which may be directed to any of the
six CTUs, via the switch section. There are three connections to each CTU; Rx1, Rx2
and loopback test.
The two receive outputs from amplifier 0 are split and may be used as extensions to
other cabinets if required. These act as extended antenna connections from antenna 0.
The extension cables go to the receive antenna connection ports on the SURF of the
extension cabinet (which is able to respond to each amplified signal as if it were a normal
antenna input).

ISSUE 1 REVISION 2 The Sectorized Universal Receiver Front end (SURF) module
The Sectorized Universal Receiver Front end (SURF)

module
View of the 1800 SURF and 900 SURF modules with features identified
SIX N-TYPE RECEIVE ANTENNA CONNECTIONS

RX1800 (2 PER DLNB EQUIVALENT)
2B RX1800
1B RX1800
0B RX1800
2A RX1800 EXTENSION PORTS TO
1A
RX1800 OTHER CABINETS
0A
HANDLE FOR
MODULE
M6 MODULE REMOVAL
ATTACHMENT
SCREWS
1800 SURF
GUIDE RAIL FOR
INSERTION
3 CONNECTORS ON UNDERSIDE
TO SURF HARNESS
BSS11_Ch4_88
EIGHT N-TYPE RECEIVE ANTENNA CONNECTIONS

(2 PER DLNB EQUIVALENT)
RX900 1A
RX900 2A EXTENSION PORTS
RX900 0A TO OTHER CABINETS
HANDLE FOR
MODULE
REMOVAL
M6 MODULE
ATTACHMENT SCREWS
900 SURF GUIDE RAIL

FOR INSERTION
BSS11_Ch4_89
3 CONNECTORS ON
UNDERSIDE TO SURF
HARNESS

Functional
description of
1800 SURF
The 1800 SURF amplifies the antenna Rx signal, and attenuates the out-of-band signal
frequencies.
The six amplifier outputs are then routed by the switch to the appropriate CTUs.
Secondary amplifier outputs are used for connection to another cabinet, if required.
The RF loopback test function is described in RF overview and RF test function in
this chapter.

Functional block diagram of the 1800 SURF module
ANTENNA CONNECTIONS
ANT 2 ANT 1 ANT 0 TO NEXT
CABINET
ANTENNA
BR 2 BR 1 BR 2 BR 1 BR 2 BR 1 CONNECTIONS
SURF
RF LOOPBACK
SPLITTER
FILTER AND FILTER AND FILTER AND

AMPLIFIER 2 AMPLIFIER 1 AMPLIFIER 0
1800 1800 1800
DIGITAL SECTION AND POWER SUPPLY

LOOPBACK
CONTROL
D
C SWITCH
RF LOOPBACK
P Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 COMBINER
O
W
E
R
Rx1/Rx2/LOOPBACK CONNECTIONS TO SURF HARNESS

SIX CTUs VIA SURF HARNESS
BSS11_4_90

Functional
description of
900 SURF
The 900 SURF provides front end filtering, amplification, and matrix control of the RF
receive signal between the antenna and the CTU. The 900 SURF is capable of dual band
working, with three antenna pair connections providing 900 MHz reception, and one
antenna pair providing 1800 MHz reception. The dual band (DB) feature enables 900
CTUs to be mixed with 1800 CTUs in any combination, up to the maximum total of six
CTUs per cabinet.
The 900 SURF functional sections consist of loopback, filtering, amplification, splitting,
digital processing and power selection.
Each section is duplicated for the second diversity path except for the digital and dc
power section which is shared by the two diversity paths. There are four antenna pair
inputs (ANT 0, ANT 1, ANT 2 and ANT DB) for each of the two diversity branches
(Branch 1 and Branch 2). There are six outputs to the CTU for each of the two diversity
branches as well as one input from the CTU for the loopback (LPBK) signal. There is
also an output for an expansion cabinet for ANT 0 on each branch.
The software database must be configured at the OMC to accept 1800 CTUs and 900
CTUs in the appropriate cabinet locations.
Digital codes are transmitted from the 900 CTUs and 1800 CTUs to the digital section.
The digital codes are dissimilar in order that 900 or 1800 CTUs can be recognized and
appropriate switching can be made to required antenna for transmission and reception.
The digital and power supply section is also responsible for loopback switch control,
manual overrides, alarms and dc voltages.
The RF loopback test function is described in RF overview and RF test function in
this chapter.

Functional block diagram of the 900 SURF module
ANTENNA CONNECTIONS
ANT DB ANT 2 ANT 1 ANT 0 TO NEXT
CABINET
ANTENNA
CONNECTIONS
BR 2 BR 1 BR 2 BR 1 BR 2 BR 1 BR 2 BR 1
SURF
RF LOOPBACK
SPLITTER
FILTER AND FILTER AND FILTER AND FILTER AND

AMPLIFIER 3 AMPLIFIER 2 AMPLIFIER 1 AMPLIFIER 0
1800 900 900 900
DIGITAL SECTION AND POWER SUPPLY
LOOPBACK
CONTROL
D
C SWITCH
RF LOOPBACK
Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 Rx1 Rx2 COMBINER
P
O
W
E
R
Rx1/Rx2/LOOPBACK CONNECTIONS TO SURF HARNESS

SIX CTUs VIA SURF HARNESS
BSS11_4_91

Transmit (Tx) blocks overview ISSUE 1 REVISION 2
Transmit (Tx) blocks overview
Tx block
overview
Transmit (Tx) blocks are located in three positions in the basket above the CTUs. There
are four types of Transmit (Tx) blocks, three of which are available as 900 or 1800
variants, and one as a dual band (900/1800) variant.
CAUTION
Unused Tx block locations must be covered with a blanking plate for correct air
flow and EMI shielding.
S 900 (or 1800) TDF = Twin duplexed filter.

S Dual band TDF = Dual band twin duplexed filter.
S 900 (or 1800) DCF = Duplexed combining bandpass filter.
S 900 (or 1800) DDF = Dual-stage duplexed combining filter.
These Tx blocks are cooled by airflow underneath; the DDF has fins, the TDF, dual band
TDF and DCF do not have fins.
Three types of plate can be located in the basket, one as blanking plate and two to
interface CTU Tx cables:
S Blanking plate. This ensures proper air flow and EMI shielding for an unused
basket Tx Block location.
S Feedthrough plate. This converts two SMA connectors to two N-type
connectors, used for connecting Tx cables to CCBs or DDFs.
S Hybrid Combining Unit (HCU). This combines two SMA connectors to one
N-type, enabling two additional CTUs to be connected to a DDF.
One type of Tx unit is installed in the stacking bracket, and is connected to three CTUs:
S Cavity Combining Block (CCB)
Two CCBs are required for the six CTUs of a filled cabinet. The CCB has no duplexing
capability and, if a single Rx/Tx antenna is used, connection must be via an external high
power duplexer.
Transmit block
connectors
The transmit block connectors are of the following types:
S SMA connectors for cables to transceivers.
S 7/16 connectors to antennas.
S N-type duplex receive connectors, also used by HCU, CCB inputs and feedthrough
plate.
The SMA connectors are underneath the unit (for ease of connection to the CTUs), and
the other connectors on top.
NOTE
All unused SMA inputs to DCF, DDF and HCU modules must be fitted with 50
ohm load terminations.

ISSUE 1 REVISION 2 Transmit (Tx) blocks overview
View of the top panel and basket which holds the Tx

blocks
SLOT FOR SURF MODULE
LOCATION HOLE
FOR INTERFACE
PANEL
BASKET TO HOLD
THREE Tx BLOCKS
HOLE FOR ONE Tx BLOCK

CTU CONNECTIONS
BSS11_Ch4_92

Blanking plate ISSUE 1 REVISION 2
Blanking plate
Purpose of
blanking plate
The blanking plate is fitted in locations where a Tx block is not required. The blanking
plate ensures correct air flow through the cabinet.
The plate is attached to the base of the top panel basket using six M4 screws.
Purpose of
feedthrough
plate
The feedthrough plate converts the normal SMA connector from the CTU to an N-type
connector. Each feedthrough plate has a pair of these converters, one for each of two
CTUs. The top N-type connectors are used to connect with either a CCB, or at the
(optional) third Tx port on the top of a DDF Tx block.
The plate is attached to the base of the top panel basket using six M4 screws.

ISSUE 1 REVISION 2 Blanking plate
View of the a blanking plate
M4 HOLES FOR
ATTACHMENT
BSS11_Ch4_93
Top view of afeedthrough plate
M4 HOLES FOR
ATTACHMENT
N-TYPE
CONNECTORS FOR
CCBs OR DDFs
SMA CONNECTORS BENEATH

FROM CTUs BSS11_Ch4_94

The Hybrid Combining Unit (HCU) plate ISSUE 1 REVISION 2
The Hybrid Combining Unit (HCU) plate
HCU overview
The Hybrid Combining Unit (HCU) combines two CTU Tx.
There are six holes for attachment into the bottom of the Tx block basket.
HCU connectors
Each HCU connects to:
S The Tx outputs of two CTUs, using SMA connectors.
S A Tx input of a DDF, using an N-type connector.
NOTE
All unused SMA inputs to HCU modules must be fitted with 50 ohm load
terminations.

ISSUE 1 REVISION 2 The Hybrid Combining Unit (HCU) plate
View of the Hybrid Combining Unit (HCU) plate with

connectors identified
M4 HOLES FOR
ATTACHMENT
N-TYPE CONNECTOR TO DDF
SMA TRANSMIT CONNECTORS

BENEATH HCU MODULE FROM CTUs
BSS11_Ch4_95
HCU functional diagram
INPUT TO DDF
N-TYPE
CONNECTOR
HCU
3 dB TYPICAL
LOSS ACROSS
COMBINER LOAD
SMA
Tx Tx
CONNECTORS
FIRST CTU SECOND CTU
BSS11_Ch4_95a

The Twin Duplexed Filter (TDF) ISSUE 1 REVISION 2
The Twin Duplexed Filter (TDF)
Overview of TDF
The purpose of the Twin Duplexed Filter (TDF) Tx block is to enable each antenna to
serve one CTU for both Tx and Rx.
The TDF has two identical sections, each providing a single path from a CTU to a
separate antenna. There is no combining in the TDF.
The TDF is located in the basket above the CTUs, and attached to the top surface of the
top panel using two M6 screws.
TDF connectors
Each TDF connects to:
S The Tx outputs of two CTUs, using SMA connectors. The two connectors are
underneath the TDF.
S Two antennas, each for both Rx and Tx, using 7/16 connectors. These connectors
are on top of the TDF.
S The SURF, using two N-type connectors. These connectors are on top of the TDF.

ISSUE 1 REVISION 2 The Twin Duplexed Filter (TDF)
View of the Twin Duplexed Filter (TDF) Tx block with

connectors identified
HOLES FOR TOP PANEL

BASKET ATTACHMENT
N-TYPE CONNECTORS TO
SURF
7/16 CONNECTORS TO
ANTENNAS
TWO SMA Tx CONNECTORS

BENEATH TDF (FROM CTU)
BSS11_Ch4_96
TDF functional diagram

Tx TO Tx TO
ANTENNA Rx TO SURF ANTENNA
Rx TO SURF
Rx FROM
ANTENNA
Rx FROM
7/16 7/16 N-TYPE
ANTENNA
CONNECTOR CONNECTOR CONNECTOR
N-TYPE
CONNECTOR
TDF
Rx BANDPASS Rx BANDPASS
FILTER FILTER
1 dB TYPICAL
LOSS ACROSS
TDF
Tx BANDPASS Tx BANDPASS
FILTER FILTER
Tx Tx
SMA
CONNECTORS
BSS11_Ch4_97

Dual band TDF ISSUE 1 REVISION 2
Dual band TDF
Overview of Dual
band TDF
The purpose of the dual band twin duplexed filter (dual band TDF) Tx block is to enable
one 900 MHz antenna to serve one EGSM 900 CTU for both Tx and Rx, and an 1800
MHz antenna to serve one DCS 1800 CTU for both Tx and Rx.
The dual band TDF is essentially a TDF with one section providing a path for 900 MHz
signals and another section providing a path for 1800 MHz signals. There is no
combining in the dual band TDF.
The dual band TDF is located in the basket above the CTUs, and attached to the top
surface of the top panel using two M6 screws.
Dual band TDF

connectors
Each dual band TDF connects to:
S The Tx output of one 900 CTU and one 1800 CTU, using SMA connectors. The
two connectors are underneath the dual band TDF.
S One 900 MHz antenna and one 1800 MHz antenna. Each antenna is used for both
Rx and Tx, and each is connected to the dual band TDF using 7/16 connectors.
These connectors are on top of the dual band TDF.
S A SURF module with dual band capability. Two N-type connectors, located on top
of the dual band TDF, connect one receive path to the SURF’s 900 MHz input and
one receive path to the SURF’s 1800 MHz input.

ISSUE 1 REVISION 2 Dual band TDF
Dual band TDF Tx block with connectors identified
N-TYPE CONNECTOR TO
N-TYPE CONNECTOR TO 1800 MHz SURF CONNECTION
900 MHz SURF CONNECTION
7/16 CONNECTOR TO 7/16 CONNECTOR TO

900 MHz ANTENNA 1800 MHz ANTENNA
(ANT. EGSM 900) (ANT. DCS 1800)
SMA Tx CONNECTOR SMA Tx CONNECTOR

BENEATH DUAL BAND TDF BENEATH DUAL BAND TDF
(FROM 900 CTU) (FROM 1800 CTU)
BSS11_Ch4_98
Dual band TDF functional diagram

Tx TO 900 Rx TO 900 Tx TO 1800 Rx TO 1800
ANTENNA SURF ANTENNA SURF
Rx FROM Rx FROM
900 1800
ANTENNA 7/16 ANTENNA 7/16 N-TYPE
CONNECTOR N-TYPE CONNECTOR CONNECTOR
CONNECTOR
Dual
band
TDF
Rx BANDPASS Rx BANDPASS
FILTER FILTER
1 dB TYPICAL
LOSS ACROSS
DUAL BAND
TDF
Tx BANDPASS Tx BANDPASS
FILTER FILTER
Tx Tx
SMA
CONNECTORS
900 CTU 1800 CTU
BSS11_Ch4_99

The Duplexed Combining bandpass Filter (DCF) ISSUE 1 REVISION 2
The Duplexed Combining bandpass Filter (DCF)
DCF connectors
Each DCF connects to:
S The Tx outputs of two CTUs, using SMA connectors. The two connectors are
underneath the DCF.
S A single antenna for both Rx and Tx, using a 7/16 connector. This connector is on
top of the DCF.
S The SURF, using an N-type connector. This connector is on top of the DCF.
NOTE
All unused SMA inputs to DCF modules must be fitted with 50 ohm load
terminations.
DCF overview
The purpose of the Duplexed Combining bandpass Filter (DCF) Tx block is to enable
each antenna to serve two CTUs for both Tx and Rx.
The DCF combines two Tx inputs, dissipating half the power within an internal load.
The signal then passes through a bandpass filter and out to the antenna.
A receive bandpass filter passes only the Rx signal to the SURF module.
The DCF is located in the basket above the CTUs, and attached to the top surface of the

ISSUE 1 REVISION 2 The Duplexed Combining bandpass Filter (DCF)
View of the Duplexed Combining bandpass Filter (DCF)

with connectors identified
HOLE FOR TOP PANEL

BASKET ATTACHMENT
N-TYPE CONNECTOR TO
SURF
7/16 CONNECTOR TO
ANTENNA
HOLE FOR TOP PANEL

BASKET ATTACHMENT
TWO SMA Tx CONNECTORS

BENEATH DCF (FROM CTU) BSS11_Ch4_100
DCF functional diagram

Tx TO
ANTENNA Rx TO SURF
Rx FROM
ANTENNA 7/16 N-TYPE
CONNECTOR CONNECTOR
DCF
Rx BANDPASS
FILTER
4 dB TYPICAL
LOSS ACROSS
DCF
Tx BANDPASS
FILTER
LOAD
Tx SMA Tx
CONNECTORS
FIRST CTU SECOND CTU BSS11_Ch4_101

The Dual-stage Duplexed combining Filter (DDF) ISSUE 1 REVISION 2
The Dual-stage Duplexed combining Filter (DDF)
Overview of DDF
The Dual-stage Duplexed combining Filter (DDF) differs from the DCF in having a
second stage of combining to allow a third CTU Tx input. This third CTU Tx input is
connected to either:
S A feedthrough plate connector for a single additional CTU or
S An HCU plate connector for combining two additional CTUs.
The DDF is located in the basket above the CTUs, and attached to the top surface of the
DDF connectors
Each DDF connects to:
S The Tx outputs of three or four CTUs, using:
Two SMA connectors underneath the DDF.
An N-type connector on top of the DDF for connection to a feedthrough plate (for a
third CTU) or HCU plate (for combined third/fourth CTUs).
S A single antenna for both Rx and Tx, using a 7/16 connector. This connector is on
top of the DDF.
S The SURF, using an N-type connector. This connector is on top of the DDF.
NOTE
All unused SMA inputs to DDF modules must be fitted with 50 ohm load
terminations.

ISSUE 1 REVISION 2 The Dual-stage Duplexed combining Filter (DDF)
DDF Tx block wth connectors identified

HOLE FOR
TOP PANEL
N-TYPE BASKET
CONNECTOR TO ATTACHMENT
SURF
N-TYPE 7/16
CONNECTOR CONNECTOR
FROM CTU BY TO ANTENNA
FEEDTHROU
GH PLATE OR
HCU
HOLE FOR
TOP PANEL
BASKET
ATTACHMENT
COOLING
TWO SMA Tx FINS
CONNECTORS
BENEATH DDF BSS11_Ch4_102
(FROM CTU)
DDF functional diagram

Tx TO
THIRD (OR COMBINED ANTENNA Rx TO SURF
THIRD/FOURTH) CTU
Rx FROM
ANTENNA
N-TYPE 7/16 N-TYPE
CONNECTOR CONNECTOR CONNECTOR
Tx
LOAD
Rx BANDPASS
FILTER
7 dB TYPICAL
LOSS
ACROSS DDF
Tx BANDPASS
FILTER
LOAD
DDF
Tx Tx
SMA
CONNECTORS BSS11_Ch4_103

The Cavity Combining Block (CCB) ISSUE 1 REVISION 2
The Cavity Combining Block (CCB)
CCB overview
The Cavity Combining Block (CCB) has EGSM and DCS1800 variants. A CCB consists
of three independently tuneable cavity resonators, one per CTU.
The CCBs are fitted in the CCB basket in the stacking bracket. The basket can contain
up to two CCBs, one for three CTUs. The two CCBs cannot be in different cabinets
because of the short phasing lead connecting the two.
Configurations where five or more carriers per sector are required could utilize CCBs.
The recommended minimum channel spacing between cavities is 800 kHz.
There are two types of CCB:
S Master CCB with Band Pass Filter (BPF) and control board.
S Extension CCB, identical to the master CCB but without the BPF and only having a
control board if redundancy is required.
Unlike the Tx blocks, the CCB has no duplexing capability. If a single Rx/Tx antenna is
used then connection to the CCB must be via an external high power duplexer.
CCB Control
Board (TCB) and
set switch
The CCB control board is also known as the Transmit Antenna Transceiver Interface
(TATI) Control Board (TCB).
The CCB control board controls the interface to the CTU. This allows different vendor
CCBs to be installed without requiring amended CTU software.
The address of the control board is set manually using an 8 bit DIL switch, set by
Motorola. Data links are automatically set up.
TCB and link

redundancy
The redundant TCB has the ability to maintain the separated CCB, if the inter-CCB link
fails.

ISSUE 1 REVISION 2 The Cavity Combining Block (CCB)
EGSM900 CCBs with control boards fitted

NOTE
CCBs may vary slightly, depending on manufacturer and type.
EXTENSION CCB OUTPUT TO ANTENNA

MASTER CCB CONNECTOR ON BPF
SHORT CIRCUIT STUB
EXTENSION CCB BAND PASS FILTER

WITHOUT BPF (BPF)
CCB OUTPUT
3 Tx INPUTS TO BPF
CCB CONTROL BOARD BPF INPUT
(REDUNDANT) FROM CCB
PHASING MASTER CCB POWER

LEAD 3 Tx INPUTS WITH BPF LEAD TO
BOTH CCB
CCB CONTROL BOARD CONTROL
(MASTER) BOARDS
BSS11_Ch4_104
DCS1800 with control boards fitted
ANTENNA CONNECTOR
CCB CONTROL BOARDS BSS11_Ch4_105

CCB
configuration
The master CCB has a second output to enable the extension CCB to be connected.
The bandpass filter can then serve both CCBs in parallel. Any unused output is
terminated with a short circuit stub. The two configurations are shown the diagram
below.
TO ANTENNA
SHORT CIRCUIT STUB
MASTER BANDPASS
CCB FILTER
UP TO 3 RF INPUTS
TO ANTENNA
SHORT CIRCUIT STUB PHASE LEAD
EXTENSION MASTER BANDPASS

CCB CCB FILTER
UP TO 6 RF INPUTS
CCB functional
description and
diagram
The CCB has three independently tuneable cavity resonators, as shown in the diagram
opposite. The cavities are narrow band devices which pass transmit signals at the cavity
tuned (resonant) frequency. The three cavity outputs are coupled together.
The CCB cavities are tuned by software commands from the CCB control board. Control
data is sent from the CTU, via the coaxial cable, to the CCB. This data is separated from
the RF signal at the bias tee, and sent to the CCB control board. The CCB control board
then sends control signals through the control bus to the motor control of the CCB cavity
of the same transceiver.
CCB tuning change Time taken

One cavity retuned and verified 8 seconds
Three cavities retuned and verified 19 seconds

ISSUE 1 REVISION 2 The Cavity Combining Block (CCB)
Functional diagram of CCB1
ANTENNA
REDUNDANT CCB CONTROL BOARD
(TCB) ON OTHER CCB
INPUT FROM EXTENSION TRANSMIT BANDPASS

CCB (IF REQUIRED) OR FILTER (FITTED TO
SHORT CIRCUIT STUB MASTER CCB ONLY)
MOTOR MOTOR MOTOR
ÏÏ ÏÏÏ ÏÏÏ
CONTROL CONTROL CONTROL
ÏÏ CAVITY
ÏÏÏ CAVITY
ÏÏÏ CAVITY
ÏÏ ÏÏÏ ÏÏÏ
CCB CONTROL BOARD (TCB)
BIAS BIAS BIAS

TEE TEE TEE
INTERNAL PROCESSOR
DATA
DATA
DATA
POWER CONTROL BUS

CONNECTOR
Tx1 Tx2 Tx3
BSS11_Ch4_106


Appendix C
Suggested RF Configurations

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Appendix C
Suggested RF Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Suggested RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–1
Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–1
Configuration for sector 1/1 or 2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–5
Configuration for sector 1/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–6
Configuration for single cabinet sector 3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–6
Configuration for 2 cabinet sector 5/5 or 6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–8
Configuration for single cabinet sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 . . . . . . . . . . . . AppC–4–9
Configuration for 2 cabinet sector 3/3/3 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–11
Configuration for sector 5/5/5 or 6/6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–14
Configuration for sector 8/8/8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–15
Configuration for dual band 1/1/1-3/3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppC–4–16

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Suggested RF configurations
Suggested RF configurations
Overview of
configuration
diagrams
The following series of RF configuration diagrams show suggested ways of connecting
together Horizonmacro SURF and Tx blocks to meet different operational requirements.
The series of diagrams is by no means exhaustive, and numerous alternative
configurations may be adopted to achieve the same aim.
Each Horizonmacro cabinet is represented by a SURF module and three Tx blocks.
Interconnecting cables are identified by a label; N01, 2, 3 or 4. Antenna connecting
cables, not supplied as part of the Horizonmacro equipment, are shown in dotted lines.
With the exception of Figure 4-20, each diagram is applicable to either EGSM 900 or
DCS 1800 operation though the SURF module illustrated is an 1800 SURF. For EGSM
900 operation a 900 SURF (dual band) is required. Connections to the 900 SURF are
identified in the same way as those to the 1800 SURF, with two additional connectors
provided for dual band 1800 use.
Figure 4-20 shows one way of achieving dual band operation using two Horizonmacro
cabinets. An 1800 SURF is installed in one cabinet and a 900 SURF (dual band) in the
other.
Configuration for
omni 1
Figure 4-1 shows a suggested configuration, using one Horizonmacro cabinet, for omni 1
with twin duplexed filter.
2B 1B 0B 2A 1A 0A B A
RX RX RX RX RX RX EXT EXT
N01
RX RX
ANT ANT
BLANK BLANK TDF

2 1 0
Figure 4-1 Single cabinet omni 1 with TDF
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory AppC–4–1

Suggested RF configurations ISSUE 1 REVISION 2
Configuration for
omni 1 or 2
Figure 4-2 shows a suggested configuration, using a single Horizonmacro cabinet, for
omni 1 or omni 2 with duplexed combining bandpass filter.
2B 1B 0B 2A 1A 0A B A
N01
ANT
RX
BLANK BLANK DCF

2 1 0
Figure 4-2 Single cabinet omni 1 or 2 with DCF
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
If configured for... Then 50 ohm load required on

unused SMA input to...
omni 1 DCF 0
AppC–4–2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

Configuration for
omni 3 or 4
omni 3 or omni 4 with duplexed combining bandpass filter.
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX RX
BLANK DCF DCF

2 1 0
Figure 4-3 Single cabinet omni 3 or 4 with DCF

omni 3 DCF 1
Configuration for
omni 3
with dual stage duplexed combining filter.
2B 1B 0B 2A 1A 0A B A
N01
ANT
N02 RX
TX
FEED
BLANK THRU DDF
2 1 0
Figure 4-4 Single cabinet omni 3 with DDF

Configuration for
omni 4
omni 4 with dual stage duplexed combining filter and hybrid combining unit.
2B 1B 0B 2A 1A 0A B A
N01
ANT
TX N02 RX
TX
BLANK HCU DDF
2 1 0
Figure 4-5 Single cabinet omni 4 with DDF and HCU
Configuration for
omni 5 or 6
or 6 with dual stage duplexed combining filter and air combining.
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX N02 N02 RX
TX TX
FEED
DDF THRU DDF
2 1 0
Figure 4-6 Single cabinet omni 5 or 6 with DDF and air combining

omni 5 DDF 2

Configuration for
sector 1/1 or 2/2
sector 1/1 or 2/2 with duplexed combining bandpass filter.
SECTOR 1 SECTOR 2
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX RX
DCF BLANK DCF

2 1 0
Figure 4-7 Single cabinet sector 1/1 or 2/2 with DCF

sector 1/1 DCF 0 and DCF 2

Configuration for
sector 1/1
Figure 4-8 shows a suggested configuration, using one Horizonmacro cabinet, for sector
1/1 with twin duplexed filter.
SECTOR 2 SECTOR 1
2B 1B 0B 2A 1A 0A B A
N01 N01
RX RX
ANT ANT
BLANK BLANK TDF

2 1 0
Figure 4-8 Single cabinet sector 1/1 with TDF
Configuration for
single cabinet
sector 3/3
Figure 4-9 shows a suggested configuration, using one Horizonmacro cabinet, for sector
3/3 with dual stage duplexed combining filter.
SECTOR 1 SECTOR 2
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX N02 N02 RX
TX TX
FEED
DDF THRU DDF
2 1 0
Figure 4-9 Single cabinet sector 3/3 with DDF

Configuration for
2 cabinet sector
3/3
Figure 4-10 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 3/3 with dual stage duplexed combining filter.
SECTOR 1 SECTOR 2
2B 1B 0B 2A 1A 0A B A 2B 1B 0B 2A 1A 0A B A
RX RX RX RX RX RX EXT EXT RX RX RX RX RX RX EXT EXT
N01 N01
ANT ANT
N02 RX N02 RX
TX TX
FEED FEED
BLANK THRU DDF BLANK THRU DDF
2 1 0 2 1 0
Figure 4-10 Two cabinet sector 3/3 with DDF
Configuration for
2 cabinet sector
4/4
sector 4/4 with dual stage duplexed combining filter and hybrid combining unit.
SECTOR 1 SECTOR 2
N01 N01
ANT ANT
TX N02 RX TX N02 RX
TX TX
BLANK HCU DDF BLANK HCU DDF
2 1 0 2 1 0
Figure 4-11 Two cabinet sector 4/4 with DDF and HCU

Configuration for
2 cabinet sector
5/5 or 6/6
sector 5/5 or 6/6 with dual stage duplexed combining filter and air combining.
SECTOR 1 SECTOR 2
N01 N01 N01 N01
ANT ANT ANT ANT
RX N02 N02 RX RX N02 N02 RX

TX TX TX TX
FEED FEED
DDF THRU DDF DDF THRU DDF
2 1 0 2 1 0
Figure 4-12 Two cabinet sector 5/5 or 6/6 with DDF and air combining

sector 5/5 both DDF 2 modules

Configuration for
single cabinet
sector 1/1/1,
1/1/2, 1/2/2 or
2/2/2
sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 with duplexed combining bandpass filter.
SECTOR 3 SECTOR 2 SECTOR 1
2B 1B 0B 2A 1A 0A B A
N01 N01 N01
ANT ANT ANT
RX RX RX
DCF DCF DCF

2 1 0
Figure 4-13 Single cabinet sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 with DCF

Sector 1/1/1 DCF 0, 1 and 2
Sector 1/1/2 DCF 1 and 2
Sector 1/2/2 DCF 2

Configuration for
2 cabinet sector
2/2/2
sector 2/2/2 with duplexed combining bandpass filter.
N01 N01 N01
ANT ANT ANT
RX RX RX
BLANK DCF BLANK DCF BLANK DCF

2 1 0 2 0
Figure 4-14 Two cabinet sector 2/2/2 with DCF

Configuration for
2 cabinet sector
3/3/3 or 4/4/4
sector 3/3/3 or sector 4/4/4 with duplexed combining bandpass filter and air combining.
N01 N01 N01 N01 N01 N01
ANT ANT ANT ANT ANT ANT
RX RX RX RX RX RX
DCF DCF DCF DCF DCF DCF

2 1 0 2 1 0
CABINET 2 CABINET 1
N03
N03
Figure 4-15 Two cabinet sector 3/3/3 or sector 4/4/4 with DCF and air combining

sector 3/3/3 cabinet 1, DCF 1
cabinet 2, DCF 0 and DCF 2

Configuration for
2 cabinet sector
4/4/4
sector 4/4/4 with dual stage duplexed combining filter and hybrid combining unit.
N01 N01
ANT ANT ANT
TX N02 RX TX RX TX N02 RX
TX TX TX
HCU DDF HCU DDF HCU DDF

2 1 0 2 1 0
N04
N03
N03
Figure 4-16 Two cabinet sector 4/4/4 with DDF and HCU

Configuration for
3 cabinet sector
4/4/4
Figure 4-17 shows a suggested configuration, using three Horizonmacro cabinets, for
sector 4/4/4 with dual stage duplexed combining filter and hybrid combining unit.
N01 N01
ANT ANT
TX N02 RX TX N02 RX
TX TX
BLANK HCU DDF BLANK HCU DDF

2 1 0 2 1 0
2B 1B 0B 2A 1A 0A B A
N01
ANT
TX N02 RX
TX
BLANK HCU DDF

2 1 0
Figure 4-17 Three cabinet sector 4/4/4 with DDF and HCU

Configuration for
sector 5/5/5 or
6/6/6
Figure 4-18 shows a suggested configuration, using three Horizonmacro cabinets, for
sector 5/5/5 or sector 6/6/6 with dual stage duplexed combining filter and air combining.
N01 N01 N01 N01
ANT ANT ANT ANT
RX N02 N02 RX RX N02 N02 RX

TX TX TX TX
FEED FEED
DDF THRU DDF DDF THRU DDF
2 1 0 2 1 0
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX N02 N02 RX
TX TX
FEED
DDF THRU DDF
2 1 0
Figure 4-18 Sector 5/5/5 or sector 6/6/6 with DDF and air combining

sector 5/5/5 all DDF 2 modules

Configuration for
sector 8/8/8
Figure 4-19 shows a suggested configuration, using four Horizonmacro cabinets, for
sector 8/8/8 with dual stage duplexed combining filter, hybrid combining unit and air
combining.
N01 N01 N01 N01
ANT ANT ANT ANT
RX N02 TX RX RX TX N02 RX
TX TX TX TX
DDF HCU DDF DDF HCU DDF

2 1 0 2 1 0
N04
N03
N03
N03
N03
N01 N01
ANT ANT
N04
TX RX N02 TX TX N02 RX TX
TX TX
HCU DDF HCU HCU DDF HCU

2 1 0 2 1 0
N03
N03
Figure 4-19 Sector 8/8/8 with DDF, HCU and air combining

Configuration for
dual band
1/1/1-3/3/3
Figure 4-20 shows a suggested configuration, using two Horizonmacro cabinets, for dual
band sector 1/1/1–3/3/3 operation, where sector 1/1/1 is EGSM 900 and sector 3/3/3 is
DCS 1800. This dual band configuration requires one 1800 SURF and one 900 SURF
(dual band).
SECTOR 3
900
SECTOR 2
900
SECTOR 1
900
1800 1800
2B 1B 0B 2A 1A 0A B A
OB OA
RX RX RX RX RX RX RX RX EXT EXT
N01 N01 N01

N01
ANT RX RX RX RX
N01
RX
ANT ANT ANT ANT
900 1800
DUAL
1800 BAND 900
DCF TDF TDF
1800 1800 1800
2 1 0
2B 1B 0B 2A 1A 0A B A
N01 N01
ANT ANT
RX N02 N02 RX
TX TX
1800 FEED 1800

DDF THRU DDF
2 1 0
Figure 4-20 Two cabinet dual band sector 1/1/1-3/3/3
Unused SMA connectors must be fitted with 50 ohm terminating loads.

Chapter 5
Horizonmicro/Horizoncompact
Operational Theory

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 5
Horizonmicro/Horizoncompact Operational Theory . . . . . . . . . . . . . . . . . . . . i
Horizonmicro manual definition and introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Overview of equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
BTS enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Overview of BTS enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
BTS power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of BTS power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of BTS Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Distribution board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Overview of battery backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
AC-DC Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
Alarms, warnings and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Optional Battery Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Description of battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Booster power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Overview of booster power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
AC power connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Booster Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
AC-DC BPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Heat management of BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Overview of BTS heat management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Module heaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Enclosure cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Airflow within the enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32
Heat management of booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Overview of booster enclosure cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Overview of digital modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Radio Digital Interface System (RDIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Overview of RDIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Main Control Unit, micro (MCU-m) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Overview of MCU-m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Processor functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
68LC060 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
QUICC32 processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
PCMCIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Crosspoint switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Sync block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
MMI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Electronic board ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Electronic site ID and calibration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Olympus Radio Architecture Controller (ORAC) function . . . . . . . . . . . . . . . . . . . . . . . . . 5–48
Overview of ORAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–48

ISSUE 1 REVISION 2
DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Overview of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Location of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Introduction to DINO/RHINO functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
Processing section of DINO/RHINO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
Reset switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Line interface framers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Radio signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
High bit-rate Digital Subscriber Line (HDSL) module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Overview of HDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Functional description of HDSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–60
Line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Overview of line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Terminology for Tx and Rx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
Features of line termination modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
HDSL link options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Overview of GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Location of GPS receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
RF modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–70
Dual Transceiver (DTRX) module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Overview of DTRX module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Synthesizer section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–74
Receiver section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–76
Transmitter section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–78
Temperature detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
Overview of combiner isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–82
Isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–86
Overview of isolator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–86
Booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–90
System description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–90
Functional description of booster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–92

ISSUE 1 REVISION 2

Horizonmicro manual definition and introduction ISSUE 1 REVISION 2
Horizonmicro manual definition and introduction
Overview of
equipment
The Horizonmicro is a two carrier microcellular Base Transceiver Station (BTS) which
operates in all frequency bands that adopt the GSM standard (GSM900 and DCS1800).
It can be deployed in or out of doors, operated over a wide temperature range, and be
wall or pole mounted.
The Horizoncompact is a two carrier microcellular Base Transceiver Station (BTS) and
booster unit which operates in frequency bands that adopt the GSM standard
(EGSM900). The Horizoncompact looks identical to the Horizonmicro with covers fitted,
but has three RF outputs. The Horizoncompact booster consists of two transmitter
amplifiers, which when used with the Horizoncompact, boost a 1.2 Watt (+30.8 dBm) per
carrier BTS output (available at the booster input) to 10 Watts (+40 dBm) per carrier.
The Horizoncompact can be deployed in or out of doors, operated over a wide
temperature range, and be wall or pole mounted. The Horizonmicro serves as a micro
BTS, whilst the Horizoncompact with the booster serves to provide macro coverage.

ISSUE 1 REVISION 2 Horizonmicro manual definition and introduction
General view of a Horizonmicro
BSS11_Ch5_01

Horizonmicro manual definition and introduction ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Horizonmicro manual definition and introduction
General view of a Horizoncompact in typical configuration
RF CABLE RF CABLE
TO ANTENNA 2 TO ANTENNA 1
Horizoncompact
BOOSTER
RF CABLING
Horizoncompact
RS232
BTS
ALARM
LINK
BSS11_Ch5_01a

BTS enclosure ISSUE 1 REVISION 2
BTS enclosure
Overview of BTS
enclosure
The Horizonmicro/Horizoncompact is designed to be wall or pole mounted. A mounting
bracket is provided, and once this is in place, the complete Horizoncompact can easily be
installed onto the bracket. The Horizoncompact is provided with a moulded solar cover
which, when removed, allows access for maintenance purposes.
All input and output cables (for example, ac power, HDSL and E1/T1 lines) enter the
enclosure via the underside. The external RFcables may be routed from top or bottom of
the enclosure. All cables have specified routes between the enclosure body and each
connector.
The Horizoncompact has no duplexer or isolator/combiner module in the chassis. A
duplexer is found in the Horizoncompact booster for Tx2/Rx output and input. There are
two isolators, one in each transmit path from the Dual Transceiver (DTRX) module. The
outputs go directly to the Horizoncompact booster.
The following diagrams show the location of modules:

ISSUE 1 REVISION 2 BTS enclosure
Location of modules and components
AC-DC POWER
SUPPLY MODULE
RDIS MODULE
DTRX MODULE ANTENNA

(INCORPORATING THE DUPLEXER CONNECTOR
AND COMBINER/ISOLATOR MODULE)
BSS11_Ch5_02


Location of modules and components
FRONT VIEW
AC POWER SOCKET
AC-DC POWER
SUPPLY
MODULE
RDIS
MODULE
DTRX MODULE
RX CABLE
(INCORPORATING THE CONNECTOR
ISOLATOR MODULES) (External ‘N’ type
RF connector)
TX1 CABLE
CONNECTOR TX2 CABLE
MASTER CONNECTOR
(External ‘N’ type SLAVE
RF connector) (External ‘N’ type
RF connector)
BSS11_Ch5_03


Location of components and components
AC-DC APSM DISTRIBUTION BOARD
Internal front view
DINO/RHINO CLAMP HDSL MODULES

BATTERY
(OPTIONAL) BSS11_Ch5_04
Horizonmicro/Horizoncompact underside view (with

battery removed)
LINE TERMINATION MODULE

BATTERY MMI INTERFACE ALARMS CONNECTOR (RHINO SHOWN)
CONNECTOR FROM BOOSTER (SEE CHAPTER
(Horizoncompact only) NO TAG) BSS11_Ch5_05

Booster ISSUE 1 REVISION 2
Booster
Overview of
booster
The Horizoncompact booster is designed to be wall or pole mounted. A mounting
bracket is provided, and once this is in place, the complete Horizoncompact booster can
easily be installed onto the bracket. The Horizoncompact booster is provided with a
moulded cover which, when removed, allows access for maintenance purposes.
All cables enter via the underside of the unit.

ISSUE 1 REVISION 2 Booster
Horizoncompact booster with cover removed
AC POWER
SOCKET
ANT2
TX2
ALARMS
PLUG
RX
ANT1
TX1
BSS11_Ch5_06

BTS power supply system ISSUE 1 REVISION 2
BTS power supply system
Overview of BTS
power supply
system
The power supply system comprises:
S An ac-dc Power Supply Module (ac-dc PSM).
S A distribution board.
S Optional battery backup.
Overview of BTS
Power Supply
Module (PSM)
The Horizoncompact ac-dc Power Supply Module (PSM) provides all internal voltages
from single phase ac supply in the nominal range 88 V to 264 V, 66 Hz to 45 Hz.
The alarm signals relating to mains fail, low voltage disconnect imminent and power
supply over temperature are generated within the ac-dc PSM and fed to the MCU-m
section of RDIS.
Distribution
board
Functional description
The power supplies generated by the ac-dc PSM are distributed, via the distribution
board, and used by the various modules listed below. The power supply levels are all
controlled by the ac-dc PSM, and there are no adjustable parameters. An optional
battery provides an auxiliary power source in the event of ac supply failure.
Overview of
battery backup
The power system incorporates an optional battery backup power system in the event of
an ac supply failure. The battery is able to supply sufficient power (for a minimum of five
minutes) for the system to perform the necessary tasks prior to complete system power
down.

ISSUE 1 REVISION 2 BTS power supply system
Location of the BTS power supply system components
AC-DC PSM DISTRIBUTION BOARD
BATTERY
BATTERY
CABLE
BSS11_Ch5_07

BTS power supply system ISSUE 1 REVISION 2
Connections
The following block diagram shows the power supply interconnections between the
distribution board and the various modules.

ISSUE 1 REVISION 2 BTS power supply system
Power supply interconnections
+5 V, +8 V, +12 V, –12 V, +25 V

CONN4 TRX 1
RDIS
CONN5
+3.3 V, +5 V, +8 V,
+12 V, –12 V, +25 V
CONN3
(CONN4
on PSM)
DISTRIBUTION DTRX
BOARD
OPTIONAL
HDSL/DINO/RHINO +5 V
+25 V switched
BATTERY
CONN2
+5 V, +8 V, +12 V, –12 V, +25 V

CONN1
TRX 0
BSS11 Ch4 08

AC-DC Power Supply Module (PSM) ISSUE 1 REVISION 2
AC-DC Power Supply Module (PSM)

The ac-dc PSM is directly plugged into the Horizoncompact distribution board, and
provides:
S A total maximum output of 170 W of power.
S Discrete voltages.
S Alarms.
S An ac supply for the enclosure heaters.
The ac-dc PSM consists of:
S An ac-dc converter sub-module using an 88 to 264 V ac single phase input, with
power factor correction, converting it to a high line 360 V dc output.
S A dc-dc converter sub-module which takes the high line 360 V dc output of the
previous sub-module and converts it to a +25 V dc supply which is used as follows:
– Routed to the dc-dc converters.
– Float charges the 25 V battery.
The dc-dc converters each use the +25 V dc input to generate the +3.3 V,+5 V, +8 V,
+12 V, –12 V dc and –25 V outputs respectively for driving logic, interface and alarms.
The ac supply for the two equipment heaters is fuse protected and controlled by a
temperature dependent switch within the heaters.
The module has a Low Voltage Disconnect (LVD) relay which enables the ac-dc PSM to
disconnect the battery, once its terminal voltage has reached a minimum, to protect the
battery from being fully charged.

ISSUE 1 REVISION 2 AC-DC Power Supply Module (PSM)
Functional block diagram of the ac–dc PSM
AC-DC POWER SUPPLY MODULE
ALARM
SIGNALS
PL1
+3.3 V
AC EMC FILTER +3.3 V
INPUT WITH FUSE
POWER FACTOR
CORRECTED AC
to 360 V DC +5 V
+5 V
360 V DC to +25 V DC
+8 V
+8 V
CONN4
110 V AC/230 V AC
SWITCH
+12 V
+12 V
PL2
–12 V
–12 V
PL3
+25 V
LVD +25 V
RELAY
BSS11_Ch5_09

Alarms, warnings and shutdown ISSUE 1 REVISION 2
Alarms, warnings and shutdown

The following events are triggered by monitoring of the power supply system. Some of
the events may trigger alarms at the OMC. Reference should be made to the following
manual Maintenance Information: Alarm Handling at the OMC (GSM-100-501).
S Mains Fail (MF) alarm
An alarm is generated when the ac-dc converter input falls to within 65 to
78 V ac, at which time an MF alarm is generated.
All other power supplies remain active, generated by the battery backup (if
fitted).
S Low Voltage Disconnect Imminent (LVDI) warning
After an ac supply failure (ac-dc converter fail) the unit will continue to
function using the battery backup (if fitted).
During this time the +25 V output will be monitored and, if the output voltage
falls to within +20.5 V ±0.5 V dc, an LVDI warning will be generated.
S Battery Low Voltage Disconnect (Battery LVD) shutdown
If the output voltage continues to fall and reaches the range +18 V ±0.5 V
dc, a Battery LVD signal will be generated and the battery will be
disconnected from the load.
S Under Temperature (UT) inhibit
Temp 1 (T1) is the trip level temperature (0 °C, for under temperature).
When power is first applied, if T1 is below 0 °C, the heater mats will come
on, the output of the +3.3 V, +5 V, +8 V, +12 V and –12 V converters will not
be enabled until the temperature has exceeds 0 °C (trip level).
S Over Temperature (OT) alarm
Temp 2 (T2) is the trip level temperature (90 to 100 °C, typically 90 °C for
over temperature).
An alarm is generated when the temperature at the ac-dc PSM heatsink
reaches T2 –5 °C, typically 85 °C.
S Over temperature shutdown
If the temperature continues to rise and reaches T2, the ac-dc PSM is
shutdown.
After such a shutdown, the ac-dc PSM will only be allowed to reactivate
when a temperature of Temp 3 (T3) is reached (55 °C to 80 °C, typically 65
°C). A Hysterisis (H) of 20 °C is used to prevent oscillation between ac-dc
PSM shutdown and reactivation.
Reactivation is automatic, in both systems that have a battery and systems
that do not have a battery.

ISSUE 1 REVISION 2 Alarms, warnings and shutdown
The ac–dc PSM sense signal and interfaces
Connector Signal Remarks

PL1 AC input Single phase input, via EMC filter.
PL2 AC switched output RDIS heater supply.
PL3 AC switched output DTRX heater supply.
CONN4 +25 V switched Used to float charge the battery; and
output provides battery backup.
+3.3 V
+5 V
+8 V For distribution to the various modules.
+12 V
–12 V
+25 V
MF Fail Mains input failure (ac supply).
LVD Imminent When the +25 V unswitched supply
drops to 20.5 V, an alarm is signalled.
Over temperature Monitors the temperature of the ac–dc
(OT) alarm PSM.
BSS11_Ch5_10

Optional Battery Backup ISSUE 1 REVISION 2
Optional Battery Backup
Description of
battery
The standard battery pack is made up from eleven lead-acid 2 volt cells, enclosed in a
plastic case. The battery is sealed and needs no attention. Expected life of the battery
is approximately five years. The output is fused with a 20 amp blade fuse, accessible
from the top of the pack.
The battery is connected to the +25 V dc switched supply line, which under mains
healthy conditions will charge the battery pack.
The ac-dc PSM monitors the +25 V dc switched supply during battery backup conditions.
It generates an alarm when it reaches the Low Voltage Disconnect (LVD) imminent level,
at 20.5 V, and ultimately de-energizes the battery disconnect relay when the output
reaches 18 V.

ISSUE 1 REVISION 2 Optional Battery Backup
View of the battery pack
BLADE FUSE (20 AMP)
BSS11_Ch5_11

Booster power supply ISSUE 1 REVISION 2
Booster power supply
Overview of
booster power
supply
The booster power supply comprises:
S An ac-dc Booster Power Supply Module (BPSM) provides all internal voltages from
single phase ac supply in the nominal range 88 V to 264 V, 45 Hz to 66 Hz,
maximum output of 150 W.
S Two power outputs provide +12 V dc and +28 V dc.
AC power
connector
The ac power connections are as follows:
S 1 is the neutral cable, coloured blue or black.
S 2 is the live power cable, coloured brown or red.
WARNING
Local regulations may apply, for different power cable colours.
S EARTH (top socket) is the earth cable, coloured green and yellow.
S 3 is not used.

ISSUE 1 REVISION 2 Booster power supply
Location of the power supply socket connector from the

supply cable
POWER SOCKET
EARTH (GREEN AND
YELLOW)
NEUTRAL (BLUE OR
(NOT USED) BLACK)
(NOT USED) LIVE (BROWN OR RED)
LIVE (BROWN OR RED) AC POWER PLUG ON
AC POWER SOCKET Horizoncompact booster BSS11_Ch5_12
NOTE
The BPSU is located within the booster case and is not accessible.

Booster Power Supply ISSUE 1 REVISION 2
Booster Power Supply
AC-DC BPSM
The ac-dc BPSM provides:
S A total maximum output of 150 W of power.
S Discrete voltages.
The ac-dc PSM consists of:
S An ac-dc converter sub-module using an 88 to 264 V ac single phase input, with
power correction.
S An ac-dc invertor which generates the +12 V dc, +28V dc for driving the amplifiers.
The ac input is fused for live and neutral lines, then Electro Magnetic Compatibility (EMC)
filtered. The next stage consists of a rectifier and input current limiting. This is followed
by a power factor corrector stage. Finally, a current mode, Pulse Width Modulation
(PWM) controlled invertor stage produces the outputs.

ISSUE 1 REVISION 2 Booster Power Supply
Functional block diagram of the ac-dc BPSM
RECTIFIER POWER
INPUT INPUT FACTOR
FILTER CURRENT
V100-1 CORRECTOR
LIMITER
FUSE
L (2)
N (1)
FUSE
J100-4
TB13
CORRECTOR
CONTROL
INVERTOR OUTPUT
J301–1
J301–2 +28 V
J300–1
J300–2
J301–3
J301–4 0V
J300–3
J300–4
0V OUTPUT
+12 V
J300–S
J301–S
AUXILIARY +12 V
AUXILIARY
SUPPLY REGULATOR
PWM
CONTROL
BSS11_Ch5_13

Heat management of BTS ISSUE 1 REVISION 2
Heat management of BTS
Overview of BTS
heat
management
The heat management of the Horizoncompact is described under the following:
S Equipment heating.
Each of the RDIS and DTRX modules must be at a specified minimum
temperature. Equipment heating is controlled through heater mats. Once the
minimum temperature is reached, the ac-dc PSM will then produce the various
voltages required for the Horizoncompact to function.
S Enclosure cooling.
Natural convection removes the generated heat. Cooling is by ambient airflow
through the enclosure and across the finned heatsinks of the electronic and power
supply modules
CAUTION
Do not block vents of the enclosure.
Do not expose the unit to prolonged sunlight without the solar cover in place.
Do not expose the unit to high temperatures created by output vents from
other equipment.
Module heaters
To ensure correct operation of the RDIS and DTRX modules, two heater mats are
attached to the heatsink of each module. These heater mats are used in extreme cold
operating environments to bring the modules quickly to the specified working
temperature.
Each heater mat has two elements configured for either 110 V ac or 230 V ac. The
ac-dc PSM selects the appropriate element depending on the ac input.
All heater mats are fused via a current fuse next to the ac input of the ac-dc PSM. These
fuses cannot be replaced on site as this would invalidate the warrantee, the
Horizoncompact must be returned to Motorola for repair.
Each mat also has an over temperature thermal fuse on the mat. When this fuse has
ruptured, the appropriate mat must be replaced, by returning the Horizoncompact to
Motorola for repair.

ISSUE 1 REVISION 2 Heat management of BTS
Functional block diagram of the heater circuit
EMC FILTER AC-DC PSM

AC INPUT WITH FUSE SELECTING EITHER 110 V OR 230 V
HEATERS
HEATER HEATER
MATS MATS
RDIS DTRX
BSS11_Ch5_14

Enclosure cooling ISSUE 1 REVISION 2
Enclosure cooling
Overview of
enclosure
cooling
The modules have finned heatsinks, which are used to remove heat in the temperature
range of up to 50 by natural convection.

ISSUE 1 REVISION 2 Enclosure cooling
View of the finned heatsinks
BSS11_Ch5_15

Airflow within the enclosure ISSUE 1 REVISION 2
Airflow within the enclosure
Overview of
enclosure
cooling
Enclosure cooling is by natural convection only.
The ambient cooling airflow is channelled through the base of the enclosure, across the
front of each of the electronic and power supply modules, and vented through the top of
the enclosure.

ISSUE 1 REVISION 2 Airflow within the enclosure
Ambient cooling airflow through the enclosure
AIRFLOW 300 MM MINIMUM

DISTANCE
BEFORE
OBSTACLE
BUILDING
WALL
POWER SUPPLY
MODULE
SOLAR COVER
(ESSENTIAL FOR
PROTECTION
AGAINST SOLAR
HEATING)
WALL BRACKET
RDIS MODULE DTRX MODULE
BATTERY/
BLANK COVER 500 MM MINIMUM
DISTANCE
BEFORE
OBSTACLE BSS11_Ch4_16
BOTTOM ENTRY

Heat management of booster ISSUE 1 REVISION 2
Heat management of booster
Overview of
booster
enclosure
cooling
The heat management of the booster relies on natural convection of the generated heat.
Cooling is by ambient airflow across the finned heatsink.
CAUTION
Do not block vents of the enclosure.
Do not expose the unit to prolonged sunlight without the solar cover in place.
Do not expose the unit to excess temperature created by output vents from
other equipment.
Enclosure cooling
The rear of the booster enclosure has a finned heatsink. It is used to remove heat in the
temperature range of up to 50 by natural convection.

ISSUE 1 REVISION 2 Heat management of booster
The Horizoncompact booster heatsink
BSS11_Ch5_17

Digital modules ISSUE 1 REVISION 2
Digital modules
Overview of
digital modules
The digital modules within Horizoncompact consist of the following:
S Radio Digital Interface System (RDIS) module.
S DINO/RHINO module.
S High bit-rate Digital Subscriber Line (HDSL) module.
S Line termination modules.
RDIS
The RDIS is the main digital control module containing the main control unit, micro
(MCU-m) and the Olympus Radio Architecture Controller (ORAC). There are two
ORACs, each designed to support a single, dual-rate basic GSM RF carrier.
DINO/RHINO
The DINO/RHINO module provides the functionality required to interface with the
network. The DINO has both E1 and T1 variants. The RHINO supports E1 only.
High bit-rate Digital Subscriber Line (HDSL) module

The HDSL module enables E1 data rates to be transmitted as payloads shared over two
twisted-pair cables.
Line termination modules

To facilitate the customer options that require connection to an Horizoncompact and to
provide an EMC screen between the internal electronics and the environment, modules
are provided to interface with either the 2.048 Mbits/s (E1) or 1.544 Mbit/s (T1) links and
High bit-rate Digital Subscriber Line (HDSL) 135 ohm links.

ISSUE 1 REVISION 2 Digital modules

Radio Digital Interface System (RDIS) ISSUE 1 REVISION 2
Radio Digital Interface System (RDIS)
Overview of RDIS
The RDIS is the main digital control module in the Horizoncompact and can be split into
two main functions:
S Main Control Unit, micro (MCU-m).
S Olympus Radio Architecture Controller (ORAC).
The RDIS contains the functionality of one MCU-m and two ORACs.
The main site control functions for an Horizoncompact site are accommodated in the
RDIS. It provides a processing platform for the site control software; the main software
functions being:
S Call Processing (CP).
S Cell Resource Manager (CRM).
S Switching.
S Support of DTRX – connection is made to two ORACs.
The maximum number of carriers is limited to two and the RDIS is designed to drive both
carrier units directly. The MCU-m is customized to drive two ORACs.

ISSUE 1 REVISION 2 Radio Digital Interface System (RDIS)

Main Control Unit, micro (MCU-m) ISSUE 1 REVISION 2
Main Control Unit, micro (MCU-m)
Overview of
MCU-m
The Main Control Unit, micro (MCU-m) module provides the following functions:
S Control processing.
S Crosspoint switch.
S BTS master clock synchronization.
S Timing.
S RSS processing (for both ORACs).
The processing supports the BTS site processing and fault management, together with
BTS Call Processing (RRSM and CRM).
The crosspoint switch provides switching for the network interfaces and the two ORAC
functional blocks.
Processor
functionality
The MCU-m processing section provides a 68LC060 processor in companion mode with
a QUICC32. The QUICC32 is used to provide system integration and peripheral
functions, specifically, a 32 channel HDLC controller for the TCU BCF links.
The main processing section of the MCU-m currently supports 16 Mbytes of RAM.
The DRAM system implements an ECC system for high data integrity.
The boot up code is stored in a 1 Mbyte flash EPROM, a further 0.5 Mbytes of flash
EPROM is provided for non volatile data storage.
A Code Storage Facility Processor (CSFP) is supported via a PCMCIA interface. This
allows flash memory cards of various sizes to be fitted.
68LC060
processor
The 68LC060 has a clock operating speed of 50 MHz with a bus speed of 25 MHz (the
reduced bus speed is due to the use of the QUICC32 in companion mode).
The on-board Memory Management Unit (MMU) provides write protection of memory
areas, particularly program storage areas.

ISSUE 1 REVISION 2 Main Control Unit, micro (MCU-m)

QUICC32
processor
The QUICC32 processor is a pin compatible derivative of the 68360. There are minor
hardware changes and microcode changes which permit the Serial Communications
Channel (SCCI) to operate as a 32 channel HDLC controller, utilizing the CPM RISC
controller to perform the processing.
The QUICC32 processor operates at 25 MHz. This also defines the external bus speed
of the 68LC060 processor.
The on-board system integration features of the QUICC32 provide peripheral control
functions to support the 68LC060 processor.

Functional block diagram of the MCU–m module
SIGNAL CONNECTOR
SYSTEM
RESET AND RESET
MASTER LOGIC
PROCESSOR XTAL
WARM
RESET
(FROM PLL
DINO/RHINO) 1 1
RS232 MMI
CONTROL COMMS
BTP
(68LC060) DATA PROCESSOR
(QUICC32)
ADDRESS SITE
ID
BERR
ECC 16Mb
DRAM
PCMCIA
PCMCIA
INTERFACE FAST FLASH
(BOOTCODE &
EXECUTIVE)
SLOW FLASH
(SWFM)
DINO/RHINO
2 LINKS
2 ORAC 2
CROSSPOINT LINKS
SWITCH
GPS 1PPS
SYNC 2
EXTRACTED
CLOCKS
FROM
DINO/RHINO
BSS11_Ch5_18

PCMCIA
The loading and storage of software may be done via the PCMCIA interface.
The PCMCIA socket is an industry standard 68 pin single socket, accessible from the
underside of the enclosure, if the MMI cover plate is removed.
The PCMCIA interface is controlled using a Cirrus Logic PC card socket controller. The
PCMCIA interface is provided to support rev 2.1 type I cards.
Crosspoint
switch
This Application Specific Integrated Circuit (ASIC) provides central switching capabilities
for the MCU-m. It switches TDM links between two ORACs, two network interfaces and
two links to the processing section, and one link to the sync processor.
The ASIC also provides link interface features associated with the ORAC links, these
include synchronization features to allow for delay in the link to the ORAC, and the
necessary framing and encoding to support the link.
All of the serial links into the ASIC are E1, 125 ms frame, 32 eight bit timeslots per frame.
Sync block
The sync block is responsible for site synchronization functions. It generates all required
local references from a high stability local clock source, taking fifteen minutes to stabilize
from warm-up. This clock source may also be locked to the incoming network clocks.
The sync block provides the following reference pulses and reference clock:
S 16.384 MHz
S 125 ms
S 60 ms
S 6.12 s
The sync function is controlled by the main processing section via a parallel port.
The clock select block receives all of the possible sources of reference signal:
S Extracted clock from the DINO/RHINO.
One of the sources is selected as a reference and up to two others can be monitored and
prioritized as backup references, should the primary reference fail.
The sync block can also operate in free-running mode, using the OXCO.
NOTE
The OXCO requires calibration when the frame-slip alarm threshold is
exceeded. This should only occur a few times in the life of the equipment, due
to the slow aging characteristic of the OXCO.
The PLL uses the selected reference signal as the loop reference clock. It includes an
OCXO accurate to 0.05 ppm, a phase comparator and a loop filter.

Functional block diagram of the serial EEPROM memories
RDIS SITE
EEPROM
MCU–m
ORAC
EEPROM
ORAC0
DTRX
EEPROM ARBITRA TION
LOGIC
ORAC1
BSS11_Ch5_19

MMI interface
The main processing section is provided with a TTY interface to the QUICC32. This
interface does not support hardware handshaking. The serial ports support a baud rate
of 9.6 kbit/s (no parity, 1 stop bit, 8 bits per character).
Electronic board
ID
Electronic board ID is supported by the slow flash memory (non-volatile data memory).
This storage contains the following information:
S RDIS module serial number – 16 bytes.
S Kit number – 16 bytes.
S Description – 32 bytes.
Electronic site ID
and calibration
data
A programmable site ID feature is provided using a serial EPROM.
Memory system
The RDIS has on-board memory devices and associated circuitry. This is used to:
S Facilitate initialization of the ORAC and DTRX.
S Store site ID.
The memory system consists of three memory blocks and some arbitration logic as
shown in the functional diagram below.
The ORAC and DTRX memory contains calibration and information data associated with
the cabinet equipment.
The arbitration logic allows the exchange of the DTRX/ORAC memory information
between the two ORACs.
The MCU-m memory contains the site identification number and the kit number of the
board on which it is stored. This information can be read via the MCU-m at the TTY
plug.


Olympus Radio Architecture Controller (ORAC) function ISSUE 1 REVISION 2
Olympus Radio Architecture Controller (ORAC) function
Overview of
ORAC
Each ORAC is part of the RDIS, and is designed to support a single, dual-rate basic
GSM RF carrier.
Functional blocks
Each ORAC consists of the following functional blocks:
S ORAC System Controller And Router (OSCAR) processor.
The OSCAR processor performs the control functions for the OSCAR to MCU-m
interface, Channel Codec control, TTY link and PA control.
S Equalizer.
The equalizer performs channel equalisation for a single RF carrier.
S Channel Codec.
The channel coders perform:
– Channel coding/decoding
– Interleaving/de-interleaving
– Speech transcoding
S Interface Transceiver Control (ITC).
The ITC performs low level management of the DTRX:
– A/D Conversion
– Modulation/Demodulation Control
– Tx Power Control
– Synthesizer Interface
S Serial Communications Interface (SCI).
Slow serial interface for TTY and control
S Synchronous Serial Interface (SSI).
Fast serial interface for communication between DSPs
The functional blocks above are shown in the following diagram, the lines representing
the interfaces between the main processing sections of the module. The Channel Codec
blocks and equalizer block contain multiple processors.
TTY/SCI
Each processor has a TTY port available; for example the OSCAR, Channel Codecs and
Equalizer.

ISSUE 1 REVISION 2 Olympus Radio Architecture Controller (ORAC) function
Functional block diagram of the ORAC module
CHANNEL PRIVATE BUS

CODECS
SCI EQUALIZER
SCI SSI
SCI (MMI)
OSCAR TTY ROUTEING
INTERFACE UPLINK
CONTROL
BUS
BUS
SCI
PARALLEL BUS
(HOST INTERFACE) OSCAR ITC ASIC
From MCU-m PROCESSOR
SECTION
DTRX
MODULE
Tx 2 MBit/s TDM
TRAFFIC SSI LINK TDM DATA
INTERFACE To MCU-m
Rx SECTION
BSS11 Ch5 20

DINO/RHINO ISSUE 1 REVISION 2
DINO/RHINO
Overview of
DINO/RHINO
The DINO/RHINO module provides the functionality required to interface with the
network. This function is separated from the MCU-m section of RDIS due to the wide
variety of interfaces that can be provided. The DINO has both E1 and T1 variants. The
RHINO supports E1 only.
The MCU-m controls the DINO/RHINO provision of network interface configuration and
supervision.
Location of
DINO/RHINO
The DINO/RHINO module is fitted between the RDIS and DTRX modules.

ISSUE 1 REVISION 2 DINO/RHINO
Location of the optional DINO/RHINO module (which

incorporates the LIU) and HDSL modules
DINO/RHINO MODULE HDSL

(DRTX OMITTED FOR CLARITY) MODULES
BSS11_Ch5_21

Introduction to
DINO/RHINO
functionality
The DINO/RHINO supports the network termination (interface) of any two links, selected
under software control, either of these links may be E1 or HDSL, T1 links are also
supported.
Table 5-1 lists available termination options.
A local microcontroller is provided for network interface configuration and supervision.
This is controlled by the MCU-m and communicates with the DINO/RHINO
microcontroller via a HDLC link.
Table 5-1 Options for network termination

Termination type Line HDSL option supported
termination (135 ohm twisted pair)
RHINO (E1) 75 ohm Coax E1 Yes
DINO (E1) 120 ohm Twisted pair E1 Yes
DINO (T1) 100 ohm Twisted pair T1 No
NOTE
The HDSL modules do not have to be fitted to the DINO(E1)/RHINO(E1)
boards. The DINO/RHINO board will then function as E1 only.

Functional blocks in the DINO/RHINO
BOARD CONNECTORS
SYSTEM
RESET (S1)
XTAL
RESET J6
BDM
CONTROL
GREEN LED PROCESSOR
DATA
J2
DRAM DINO/RHINO
RXD
J12 ADDRESS DINO/RHINO
RS232
TXD
HDSL GND
HLI
LINK 0
FLASH EPROM
J7
J4
HDSL CONTROL
DINO/RHINO
MODULE
DATA/CLK RXD
DINO/RHINO
ÏÏÏÏÏ
TXD
DUART GND
STROBE
ÏÏÏÏÏ
J8 SYSTEM
CONTROL RESET
ÏÏÏÏÏ
HDSL DATA/CLK
MODULE
ÏÏÏÏÏ
2.048 MBIT/S
ÏÏÏÏÏ
MAIN
J13
LINK 0
ÏÏÏÏÏ
HDSL MUX
LINK 1 HLI DEMUX
ÏÏÏÏÏ
FRAMER
LINK 1
J11 (DINO)
ÏÏÏÏÏ
J14/15/16/17 (RHINO) DISTANCE
MEASURING, REF_6.12S
ÏÏÏÏÏ
NETWORK PATTERN REF_125mS
LIU
LINK 0 INSERT AND 2.048 MBIT/S
ÏÏÏÏÏ
DETECT
ÏÏÏÏÏ
STOP COUNTER
FRAMER
ÏÏÏÏÏ
ÏÏÏÏÏ
START
NETWORK
LIU
ÏÏÏÏÏ
LINK 1
ÏÏÏÏÏ
PROCESSOR BUS
MCU-m
RESET
J9 MASTER PROCESSOR SWITCH
WARM RESET (S2)
MMI MMI
CONNECTOR TTY
BOARD CONNECTORS
BSS11_Ch5_22

Processing
section of
DINO/RHINO
The processing section comprises a MC68360 microcontroller with 1 Mbytes DRAM and
512 kbytes flash EPROM. The processor provides integrated features such that it
requires little peripheral support. It communicates with the MCU-m via a HDLC link.
Flash EPROM
The flash EEPROM stores the following:
S Boot code.
S Operational code.
S Electronic ID.
The Boot code executes on reset performing various board level tests (DRAM test etc)
before transferring execution to the operational code.
The operational code will then allow the HDLC link to the MCU-m to be established. The
MCU-m may then request a code load of the DINO/RHINO to be performed.
Electronic ID
The electronic board ID stores the following information:
S Board serial number – 16 bytes.
S Board kit number – 16 bytes.
TTY port
The TTY connector (J2) on the DINO/RHINO is the master processor/MCU-m TTY port.
A TTY for debugging the DINO/RHINO is available on the RDIS test connector.
LED status
The system status is indicated by an LED, as follows:
Green LED Status

Off System power off
On System power on
Resets
The processor is capable of soft resetting itself. A local power-on reset circuit is
provided. This provides a local reset based on the power supply tolerance.
The MCU-m is able to reset the DINO/RHINO via a message on the HDLC link only.

View of a DINO/RHINO module
RDIS
CONNECTOR HDSL
MODULES
NETWORK
INTERFACE
MODULE
MASTER
PROCESSOR
WARM RESET
BUTTON (S2)
GREEN LED
SYSTEM RESET
BUTTON (S1) TTY CONNECTOR
(MMI OF RDIS)
LINE TERMINATION
MODULE BSS11_Ch5_23
External view of the TTY connector and switches on the

MMI cover plate
MMI COVER PLATE
POWER
INDICA TOR MMI
MASTER
SYSTEM
PROCESSOR
RESET
WARM RESET
SWITCH
SWITCH
BSS11_Ch5_24

Reset switches
There are two push button switches mounted on the DINO/RHINO board which provides
the following:
S System reset (S1)
When depressed briefly and then released, on board circuitry provides a timed
hard reset of the DINO/RHINO board and RDIS board.
S Master processor warm reset (S2)
When depressed briefly and then released, on board circuitry provides a warm
reset to the MCU-m section of the RDIS module.
The reset switches are located on the DINO/RHINO to provide better access to this
function when the system is fully configured in the chassis.
Line interface
framers
The framing devices provide analogue to digital conversions for encode/decode of the
E1/T1 interfaces, and for HDSL modules when fitted and selected by software (E1 only).
The framers provide the decoded and jitter attenuated receive data, for passing to the
MCU-m, plus a version of the data that has not been through the jitter buffer which can
be used on board the DINO/RHINO for distance measurement.
NOTE
Although distance measuring can be made operational, it is not a feature of
current software.
The framers provide a 2.048 MHz extracted clock, passed to the MCU-m. The transmit
and receive framing is controlled by a 125 ms reference pulse received from the MCU-m.
Radio signalling
links
The Radio Signalling Links (RSL) to the BSC from the main processor on the MCU-m are
64 kbit/s or 16 kbit/s LAPD links. The MCU-m does not perform the LAPD encoding of
the RSL link data. This is performed on the DINO/RHINO by the processor.
The DINO/RHINO supports a maximum of two RSL links. The RSL links may both be on
a single network link or shared between the two network links.
NOTE
When the DINO/RHINO is on a network link to a BSC, the RSL can be placed
on either line on any time slot other than zero.
The DINO/RHINO supports 64 kbit/s and 16 kbit/s LAPD channels.


HDSL interface
Control
The HDSL modules are controlled from the processor by an asynchronous serial data
stream. There are two separate control channels, one per HDSL module. The control
streams are sourced by a Dual Universal Asynchronous Receiver Transmitter (DUART)
device on the processor bus of the DINO/RHINO.
Clock and data

The HDSL module interfaces directly to the framer interface/framer devices. The HDSL
sourced data is selected as the input and output data path by the control processor.
Both clock and data are used in both transmit and receive directions.


High bit-rate Digital Subscriber Line (HDSL) module ISSUE 1 REVISION 2
High bit-rate Digital Subscriber Line (HDSL) module
Overview of
HDSL
The HDSL module enables E1 data rates to be transmitted as payloads shared over two
twisted-pair cables. These cables are generally unshielded standard telephone cables.
Functional
description of
HDSL
The HDSL data operates bi-directionally over each twisted-pair at approximately half the
overall E1 data rate.
The module processor performs such tasks as error monitoring and start-up
configuration. The processor also communicates with the DINO/RHINO processor via an
asynchronous control port.
The raw HDSL signals from the module are routed through the DINO/RHINO and then
translated at the HLI functional block (see DINO/RHINO functional block diagram in
previous section) into true HDSL level signals.

ISSUE 1 REVISION 2 High bit-rate Digital Subscriber Line (HDSL) module
Functional block diagram of the HDSL module
BIDIRECTIONAL
BALANCED LINE
ÇÇ
ÇÇ
ÇÇ
TO HLI
ÇÇ
BIDIRECTIONAL
ÇÇ
BALANCED LINE
TO HLI
ÇÇ
ANALOGUE
CLOCK DSP FRONT
ÇÇ
DATA END
HDSL
CLOCK ÇÇ
ÇÇ
FRAMER
DSP
ANALOGUE
FRONT
ÇÇ
DATA
END
ÇÇ
ÇÇ
ÇÇ
ÇÇ PROCESSOR
FLASH
ÇÇ
CONTROL NVRAM
ÇÇ BSS11_Ch4_25

Line termination modules ISSUE 1 REVISION 2
Line termination modules
Overview of line
termination
modules
To facilitate the customer options that require connection to an Horizoncompact, and to
provide an EMC screen between the internal electronics and the environment; the
following modules terminate (interface with) either the 2.048 Mbit/s (E1) or 1.544 Mbit/s
(T1) links and High bit-rate digital subscriber line (HDSL) 135 ohm links:
S DINO termination module - 120 ohm (DINO E1/HDSL module).
S DINO termination module - 100 ohm (DINO T1 module).
S RHINO termination module - 75 ohm (RHINO E1/HDSL module).

ISSUE 1 REVISION 2 Line termination modules
View of the DINO/RHINO connectors and location of the

line termination module
ALARMS CONNECTOR LINE TERMINATION MODULE

FROM BOOSTER (RHINO SHOWN)
DINO (E1/HDSL or T1(NO HDSL FUNCTION))
RHINO (E1/HDSL)
J11 J13 J12

J14 J15 J16 J17 J13 J12
DINO LABEL
PORT PIN PORT PIN INTERNAL INTERNAL
TX 1 & 6 TX 3 & 8 SLAVE MASTER
A B
ALARM RX 2 & 7 RX 4 & 9 HDSL OPTION
RHINO LABEL
INTERNAL INTERNAL
TX RX TX RX
SLAVE MASTER
A A B B
ALARM HDSL OPTION
BSS11_Ch5_26

Terminology for
Tx and Rx
The use of Tx and Rx as driver/receiver designators refer to the network as perceived by
the Horizoncompact enclosure:
S Tx indicates the Horizoncompact connection is driving into the network.
S Rx indicates the Horizoncompact connection is receiving from the network.
Features of line
termination
modules
The line termination modules provide:
S The impedance matching between the E1/T1 and HDSL circuit lines and the
DINO/RHINO module.
S An interface for:
– Up to two inputs and two outputs (120 ohm balanced (DINO) E1, 100 ohm
balanced (DINO) T1, or 75 ohm unbalanced (RHINO) E1) lines.
– Two HDSL 135 ohm looped pairs.
HDSL link
options
If an HDSL equipped version is purchased the links are automatically configured as
either E1 or HDSL via a combination of database settings and auto-detection
mechanisms.
A feature of GSR4 software and later releases, enables the setting of the master/slave
defaults to be changed by database settings for scenarios where the defaults are not
appropriate, such as a closed loop daisy chain. In this instance an external modem from
the Base Station Controller (BSC) cannot be a master but a slave. The slave modem on
the last Horizoncompact must be turned from into a master in order to communicate with
the BSC, see configuration example later in this section.
NOTE
Earlier software releases cannot access the above feature.
Links can be either E1 or HDSL, and can be mixed as appropriate within the network.
Conversion to/from E1 and HDSL can be performed either at a Horizoncompact or by
use of External HDSL modems, here are some examples of possible configurations:


E1 link connection to the BSC

In this configuration an E1 link is used from the Base Station Controller (BSC) to the first
Horizoncompact. Here the connection is made to the J11 port in the DINO board or to
one of the coaxial cable connectors (J14, J15, J16, or J17) on the RHINO board. From
the first Horizoncompact onwards HDSL links are used running from slave port (J13) to
master port (J12) in each Horizoncompact.
External Modem connection to the BSC

In this configuration a BSC connects to an external modem through an E1 link. A
connection is then made from the external modem slave port to the J12 master port on
the Horizoncompact DINO/RHINO. The J13 slave port of the Horizoncompact connects
to the next Horizoncompact J12 master port and so on, until the last Horizoncompact
port is connected.
External Modem connection to the BSC (Closed Loop)

This closed loop configuration uses external modems through an E1 link in order to
connected to the BSC. A connection is then made from the external modem slave port
to the J12 master port on the Horizoncompact DINO/RHINO. The J13 slave port of the
Horizoncompact connects to the next Horizoncompact J12 master port and so on, until
the last Horizoncompact port is connected.
The J13 slave port on the last Horizoncompact is then reconfigured, via software, to be a
master port. The reconfiguration of the J13 port on the last Horizoncompact allows the
loop to be closed via the use of an external HDSL modem.

Connections to the BSC

E1 link connection to the BSC
E1 LINK HDSL HDSL

S M S M
BSC Horizoncompact Horizoncompact Horizoncompact
M = MASTER S = SLAVE
BSS11_Ch5_27
NOTE
The remaining span on the last Horizoncompact could be used to perform a
closed loop configuration with a E1 link.
External modem connection to the BSC
E1 LINK HDSL HDSL HDSL

SLAVE M S M S M
EXTERNAL
MODEM Horizoncompact Horizoncompact Horizoncompact
BSC
M = MASTER S = SLAVE BSS11_Ch5_28
NOTE
Only Motorola approved External HDSL Modems must be used, see sales
guide.
External modem connection to the BSC (Closed Loop)
E1 LINK HDSL
SLAVE
E1 LINK HDSL HDSL HDSL

SLAVE M S M S M M
EXTERNAL
BSC MODEMS
Horizoncompact Horizoncompact Horizoncompact
M = MASTER S = SLAVE BSS11_Ch5_29
NOTE
Earlier software releases than GSR4 cannot access the above closed loop
configuration.

GPS receiver ISSUE 1 REVISION 2
GPS receiver
Overview of GPS
receiver
An optional GPS receiver may be provided for site synchronization functions.
When fitted, the GPS receiver is controlled by the MCU-m module.
Location of GPS
receiver
The GPS receiver module is located above the DINO/RHINO module and between the
RDIS and DTRX modules.

ISSUE 1 REVISION 2 GPS receiver
Location of the GPS receiver
GPS RECEIVER
(OPTIONAL) BSS11 Ch5 30

RF modules ISSUE 1 REVISION 2
RF modules
The RF modules in the Horizonmicro consist of:
S Dual Transceiver Module (DTRX)
S Duplexer
S Combiner/Isolator
The RF modules in the Horizoncompact consist of:
S Dual Transceiver Module (DTRX)
S Isolator modules

ISSUE 1 REVISION 2 RF modules
Location of the RF modules
DTRX MODULE
[INCORPORATING THE
DUPLEXER AND
COMBINER/ISOLATOR
MODULE]
BSS11_Ch5_31
AC-DC
FRONT POWER
VIEW SUPPLY
MODULE
RDIS
DUAL
MODULE
TRANSCEIVER
MODULE
(INCORPORATING
THE
ISOLATOR
MODULES) RX CABLE
CONNECTOR TX1 CABLE
(External ‘N’ type CONNECTOR
TX2 CABLE
RF connector) MASTER
CONNECTOR
(External ‘N’ type SLAVE
RF connector) (External ‘N’ type
RF connector)
BSS11_Ch5_32

Dual Transceiver (DTRX) module ISSUE 1 REVISION 2
Dual Transceiver (DTRX) module
Overview of
DTRX module
The DTRX module supports dual RF transceivers and can operate in both the primary
and extended GSM frequency bands.
The DTRX module supports Synthesizer Frequency Hopping (SHF) and dynamic power
control (but not for the BCCH carrier). The DTRX module does not support base band
hopping or receive spatial diversity.

ISSUE 1 REVISION 2 Dual Transceiver (DTRX) module

Synthesizer
section
Introduction
The synthesizer blocks are located with the Rx and Tx circuits and used for the RF and
IF frequency synthesis.
There are a total of 13 phase-lock loops required on the DTRX module, eight frequency
synthesizers and five phase-locked oscillators. The phase-locked oscillators are used for
the IF local oscillators. The master 13 MHz reference oscillator, is phase-locked to a
16.384 MHz reference supplied from the RDIS digital module; and together with digital
dividers, provides reference frequencies for all other PLLs. The subsystem supports
Synthesizer Frequency Hopping (SFH).
The phase-locked loops of the DTRX module are:
S 13 MHz master reference.
S Transmit RF frequency synthesizer (TXRFLO) x4.
S Transmit IF phase-locked oscillator (TXIFLO) x2.
S Receive RF frequency synthesizer (RXRFLO) x4.
S Receive IF phase-locked oscillator (RXIFLO) x2.
13 MHz reference distribution

The purpose of the reference distribution is to generate and distribute reference signals,
of the correct frequency and amplitude, to all the synthesizers and oscillators on the
DTRX module. A synchronizing 13 MHz clock is returned to the RDIS digital module.
RF synthesizers
The operation of the eight RF synthesizers supplying the Rx and Tx chains are identical.
They are combined in pairs to enable SFH. Whilst one of the pair of synthesizers is
providing the local oscillator the other is locking to the next channel in the frequency
hopping sequence.
IF oscillators
The four IF oscillators are basically the same but the transmit and receive synthesizers
use different reference frequencies and phase detector comparison frequencies.
Alarms
Synthesizer alarms are:
S Tx synthesizer lock alarm.
S Rx synthesizer lock alarm.
S 13 MHz synthesizer lock.

Synthesizer functional blocks
RF RXRFLO
INJECTION (Carrier 0)
13 MHz Reference PLL (A)
RF RXRFLO
PLL
(B)
RF TXRFLO
13 MHz Reference PLL
(A)
RF TXRFLO
PLL
16.348 MHz CLOCK REFERENCE (B)
(from RDIS) SYNTHESIZER
RF RXRFLO
13 MHz Reference PLL (A)
RF RXRFLO
PLL
(B)
13 MHz Reference
RF TXRFLO
(to RDIS) INJECTION (Carrier 1)
13 MHz Reference PLL
(A)
RF TXRFLO
PLL
(B)
DIVIDE
by 13 IF TXIFLO
INJECTION
1 MHz Reference PLO (Carrier 0)
IF TXIFLO
INJECTION
PLO (Carrier 1)
DIVIDE
by 5
IF
INJECTION
RXIFLO
PLO (Carrier 0)
200 kHz Reference
IF
INJECTION
RXIFLO
PLO (Carrier 1)
BSS11_Ch5_33

Receiver section
Introduction to the receiver

The receiver is a double conversion super-heterodyne which can operate in two modes;
linear and limiting. When the receiver is looking for call initiation from a mobile station on
a RACH it is switched to limiting mode as no estimate of signal strength is available to
set the AGC pads. In normal operation on a SDCCH or TCH the receiver operates in
linear mode. This allows the amplitude information to be retained which is required by
the channel equalizers.
Functional description of the receiver

The RF signal passes through a low noise amplifier stage and then through a splitter.
One arm feeds Carrier 0 whilst the other feeds Carrier 1. A bandpass filter provides
rejection to out-of-band blockers. The mixer down-converts the signal to an IF using a
low-side RXRFLO. A duplexer at the output of the mixer provides a wideband match to
the mixer to prevent reflections causing unwanted spurious signals. An AGC pad is
available at this point to reduce the dynamic range requirement for the IF strip.
Three SAW filters provide some channel filtering, reject the unwanted mixer components
and ease the 3rd order Intermodulation Products (IP3) requirements of the backend. The
IF signal is then amplified and split into two paths; one is the limited path, the other is the
linear path. The limited signal can be switched back into the main signal path.
During linear operation the magnitude of the baseband output (I+Q) is monitored to feed
back to the AGC algorithm, ensuring that the baseband output is maintained at the
required level. However, in limiting operation the magnitude of baseband output (I+Q)
does not reflect the incoming signal strength due to the operation of the hard limiter. The
signal strength can be derived, however, by monitoring the output of the limiters RSSI
port.
The dynamic range of the receiver is –104 dBm to –15 dBm. There is a switchable 40
dB pad (known as AGC7) at the front of the IF strip which reduces the compression of
the IF strip to an achievable level. The baseband output to the A/D converters is ideally
maintained at 1/2 full scale (2.5 V pk–pk or 12 dBm) using the AGC pads which are
controlled by the equalizer algorithm and set by AGC calibration. AGC7 effectively
reduces the dynamic range for the remainder of the receiver to –104 dBm to –55 dBm.
There is hence a remaining 49 dB of AGC requirement to be taken up in AGC0–6. This
is provided by a voltage variable amplifier which is controlled by a DAC from the AGC
word.
The active demodulator provides I & Q channel data at baseband by using RXIFLO from
the synthesizer at twice the required LO frequency. The baseband processing then filters
the demodulated signal to reject the adjacent channels and to band limit the noise power.
The signal is also amplified to the level required by the A/D converter. Also included is a
group delay equalizer which flattens the variation caused by the baseband filtering.

Functional block diagram showing the CARRIER 0

receiver path of the DTRX module
CARRIER 1 PATH
Rx_IN LPF TEMPERATURE Rx_TEMP_0
LNA LNA RXRFLO DETECTOR
1 2
DUPLEXER SAW
RF FILTER MIXER AMP AGC7 0/40 dB

1 1
RSSI_0
AGC
SAW SAW LIMIT/LOG
AMP
AMP
SWITCH
AMP AMP CAL AMP CAL
2 3 AGC 4 AGC
1a 1b
50
Ohms
I&Q
DEMOD I BRANCH
BPF I_0
90_
CAL Q_0
AGC
Q BRANCH
RXIFLO BASEBAND
PROCESSING
CARRIER 1 path being identical

BSS11_Ch5_34

Transmitter
section
Introduction to the transmitter

The transmitter section of the DTRX module takes in digital information from the RDIS
module, and oscillator and reference signals from the synthesizer section. It generates
the IF, mixes it with the LO and amplifies the resultant RF signal. The final RF signal is
fully modulated, filtered, power ramped and amplified.
In the Horizoncompact, each of the output signals from Tx1 and Tx2 are passed through
two separate isolators before being forwarded to the Horizoncompact booster for
amplification.
Functional description of the transmitter

The Transmitter (Tx) receives digital baseband information from the RDIS module and
converts it into a GMSK modulated signal. This modulated signal is mixed with the
TXIFLO input, up-converted to the first IF, 175 MHz, then passed through:
S An amplification and narrow band filtering stage to remove unwanted sidebands
(due to mixing of signals).
S A Voltage Variable Attenuator (VVA) which provides signal level adjustment under
control of the RDIS module (to compensate for power level changes).
S A Voltage Controlled Amplifier (VCA) which provides more than 45 dB of power
control (to ramp the signal up and down).
S An amplification and wideband filtering stage before being mixed with the TXRFLO
input and being up-converted to the final RF frequency.
After the second mixer, the signal is amplified and filtered before being passed through
the second VVA. The function of this VVA is the same as the first. It forms part of a
control loop in conjunction with the power detector. Both VVAs are also used to adjust
the power output of the system, to account for the duplexer and combiner/isolator
module.
The signal is further amplified and filtered before being passed through a Digital Switched
Attenuator (DSA). This attenuator provides up to 30 dB of attenuation in discrete 2 dB
steps, and used for static/dynamic power control. It is controlled by signals from the
RDIS module. An RF power amplifier (PA) module with two further stages of
amplification boosts the signal level up to approximately +31.5 dBm in the
Horizoncompact.
An RF power detector monitors the power output, giving a usable output over 35 dB of
range. The detector is temperature compensated. A temperature sensor is fitted to
allow the RDIS module to determine the temperature of the PA module, for thermal
protection.

Functional block diagram showing the CARRIER 0

transmitter path of the DTRX module
CLOCK TXIFLO Voltage Variable

NARROW Attenuator VCA
BAND
MDATA GMSK PASSIVE SAW VVA

7 MHz LPF BPF
MIXER
175 MHz
ENABLE
PWR_RAMP_0 DIVIDER
PWR_LEVEL_0
GAIN
BLOCK MIXER
SAW
BPF
BPF
BPF BPF VVA
AMPLIFIER AMPLIFIER
TXRFLO
TX_KEY
Digital
Switched RF PA
Attenuator Module
BPF DSA Tx_OUT_0
AMPLIFIER
RF POWER
DETECTOR FWD_PWR_0
DIGITAL CONTROL SIGNAL
TEMPERATURE
DETECTOR Tx_TEMP
CARRIER 1 transmitter path being identical BSS11_Ch5_35

Temperature
detectors
The purpose of the temperature detection is to allow the RDIS module to compensate for
the temperature response of the DTRX module.
The DTRX module is equipped with four temperature detectors. Two sensors are placed
to detect the ambient temperature of the receivers and two placed to detect the
temperature of the transmitter output stages.
The outputs of the four detectors are then multiplexed onto two analogue detector lines
selected by the TEMP_SEL control line (0 selects the transmitter and 1 selects the
receiver). All the temperature sensors are identical and share common switching and
signal connection circuitry.
TEMP_SEL is changed only on timeslot boundaries, and is sent with the AGC data
through a serial link back to the RDIS.

Functional block diagram of temperature detectors
TRANSMITTER
TEMPERATURE CARRIER 0 TEMP_SEL_0
DETECTOR
RECEIVER
TEMPERATURE CARRIER 0
DETECTOR
TEMP_DET_0
ANALOGUE
SWITCH
TRANSMITTER TEMP_DET_1
TEMPERATURE CARRIER 1
DETECTOR
RECEIVER
TEMPERATURE TEMP_SEL_1
CARRIER 1
DETECTOR
BSS11_Ch5_36

Overview of
combiner isolator
The duplexer switches Tx and Rx signals between a single antenna and the DTRX.
The Tx combiner/isolator module is used to combine the two Transmit signal outputs onto
the duplexer and hence to one antenna.

Location of the duplexer, combiner/isolator module and

DTRX board
DTRX BOARD
COMBINER/ISOLATOR
MODULE DUPLEXER
BSS11_Ch5_37


View of the duplexer and combiner/isolator modules
COMBINER/ISOLATOR
MODULE
DUPLEXER
BSS11_Ch5_38
The DTRX Rx/Tx interconnections in a dual carrier system
CARRIER 0
Tx Tx OUT
COMBINER/
ISOLATOR Tx
MODULE
Tx
DTRX
Tx/Rx ANTENNA CARRIER 1

COMBINED Tx Tx OUT
Ae Tx
DUPLEXER
COMBINED Rx Rx IN
Rx
BSS11_Ch4_39

Isolator ISSUE 1 REVISION 2
Isolator
Overview of
isolator
The isolators are high performance single stage directional TX power modules, used in
the Horizoncompact. Due to its electromagnetic properties it enables a low loss forward
path through to the Horizoncompact booster TX port and isolates in the reverse path.
This module provides isolation of multiple frequencies in the EGSM cellular telephone
Base Transceiver Station (BTS) to reduce intermodulation distortion. The isolator
reduces reverse intermodulation by absorbing the power of an interferer into its internal
load.
This module also prevents possible damage to the RF power amplifier resulting from load
mismatches.

ISSUE 1 REVISION 2 Isolator
Location of the isolators and DTRX board
DTRX BOARD
ISOLATOR MODULES
BSS11_Ch5_40

Isolator ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Isolator
View of the isolator module
BSS11_Ch5_41
The DTRX Rx/Tx interconnections in a dual carrier system
CARRIER 0
Tx Tx OUT
Tx Ae Tx AMP
ANTENNA ISOLATOR
FILTER MODULE
DTRX
CARRIER 1 Tx OUT
Tx/Rx Ae Tx Tx
ANTENNA AMP ISOLATOR
MODULE
DUPLEXER
Rx
Booster BTS
Rx IN
BSS11_Ch5_42

Booster
Overview of
booster
The Horizoncompact booster consists of two transmitter power amplifiers which, when
used with the Horizoncompact BTS, will boost a 1.2 Watt (+30.8 dBm) per carrier output
to 10 Watts (+40 dBm) per carrier. The booster is intended to be mounted close to the
Horizoncompact BTS and connected through three two metre RF cables. The booster
can be wall or pole mounted.
System
description
The Horizoncompact booster amplifies two independent RF carriers in the frequency
range of 925 to 960 MHz. Each TX input to the booster is a pulsed RF carrier. One of
these TX carriers could be used in frequency hopping mode.
When the downlink power control is employed in the associated Horizoncompact, the
peak amplitude of the pulsed RF carrier at the booster inputs can vary from +5 dBm to
+30.8 dBm.
The Horizoncompact booster gain remains constant when the RF input is reduced, so the
booster RF output power is correspondingly reduced.
The attenuation through the receive (ANT2 only) is less than 1.0 dB.
Alarms
The alarm board monitors the discrete outputs from both power amplifiers (PAs), PA1,
PA2 and the ac to dc converter. When either or both (PAs) fail or the ac to dc converter
fails, a signal is reported to the Horizoncompact via an RS-232C interface. The line driver
voltage levels are 12 volts maximum.
An encoded RS232 status signal is sent to the Horizoncompact BTS every minute.
Within the signal are fault indicators. After reception of five interrupts, the
Horizoncompact BTS interrogates this signal to determine whether the booster is
operational. No indicator is transmitted to the OMC if the Horizoncompact booster is
operating correctly. Only fault conditions are flagged.
If an error has occurred, then the type and nature of the error(s) is/are reported to the
OMC.
If the dc to dc converter fails within the booster, there will be a loss of power supply to the
alarm board and in the absence of battery backup, no messages will be transmitted to
the BTS.
The transmissions from the Horizoncompact booster contain unique identification codes
of the nature of failure, with expansion capability to detect a further four sub-failure
modes. The diagram opposite outlines an alarm interface functional diagram.
A description of the alarm codes sent to the BTS, (should a functionality failure occur at
power up or during normal operation), is provided in NO TAG.

Alarm codes sent to the BTS
Alarm codes
Alarm Description
MB PA Fail 1 Power amplifier failure 1
MB PA Fail 2 Power amplifier failure 2
MB Fail Occurs if booster is timed out
BSS11_Ch5_43
Functional block diagram outlining the alarm board

monitoring of the power amplifiers
PA 1 PA 2
POWER AMPLIFIERS
PA = POWER AMPLIFIER
SIGNAL
COND.
ALARM BOARD
MICROCONTROLLER
87C51
RS232 TX
I/F
RX
PUR
PUR = POWER UP RESET

BSS11_Ch5_44

Functional
description of
booster
Referencing the diagram opposite, pulsed signals originating from TX1 and TX2 are
under normal operation carried through relays. In the event of a failure in either or both
power amplifiers, a bypass mode is automatically enabled by the booster once failure is
detected. This feature enables switching a maximum of +41.25 dBm when RF power is
applied to the relay. One amplifier can remain operational whilst the other is in bypass
mode. Both carriers of the Horizoncompact remain operational in bypass mode.
From the switch the pulsed signal arrives at the attenuator and local heat sink. The
attenuator reduces a nominally 30.8 dBm by 8 dB to 22.8 dBm.
The pulsed signal is then passed to the linear Power Amplifiers (PAs) where they are
brought up to 40 dBm ( 1.25 dBm). A dc voltage of 28 volts derived from the power
supply drives the power amplifiers.
From the PAs, the pulsed signals are passed to the isolator. The isolator is a directional
power device, which due to its electromagnetic properties enables a low loss forward
path (0.3 dB) through to the next relay. The isolator prevents reverse intermodulation by
absorbing the power of an interferer into its internal load such that it does not reach the
power amplifier.
The pulsed signal is then passed through the second relay and onto the TX filter or
duplexer. From the filter or duplexer the signal is routed to the antennas.
Modulated RX signals arrive at antenna 2 and pass through the duplexer before passing
to the RX port.
The booster power supply unit has been described earlier.

Functional block diagram of the Horizoncompact booster

system
RELAY ATTENUATOR LINEAR PA ISOLATOR RELAY TX FILTER
TX1 ANT1
+ 28 V dc
BYPASS PATH
AC SUPPLY
AC/DC SUPPLY
AND
ALARMS
ALARMS BOARD
+ 28 V dc
RELAY ATTENUATOR ISOLATOR RELAY DUPLEXER
LINEAR PA
TX2 ANT2
BYPASS PATH
RX
BSS11_Ch5_45

Bypass
In case of failure of either or both PAs inside the booster, there is an ability to bypass the
amplifier which has failed. Bypass mode is automatically enabled by the booster once
the fault is detected. This feature requires that the booster internal RF relays are capable
of switching a maximum of +41.25 dBm, whilst the RF power is applied to the relay. Both
carriers of the Horizoncompact remain operational in bypass mode. If there is an ac fail
both relays bypass the amplifiers.
Overtemperature protection is required such that it is not latching and has sufficient
range to prevent rapid cycling of ON and OFF. There is no overtemperature signal
passed to the Horizoncompact.
Booster power supply unit

The Booster Power Supply Unit (BPSU) is mounted within the booster unit itself. It is an
ac to ac switch mode supply with standard universal voltage input capability (88 V to 264
V, 45 to 66 Hz).
Two dc voltage outputs are provided (12 V and 28 V) to a maximum total output of 130
Watts.

Bypass feature
RELAY ATTENUATOR LINEAR PA ISOLATOR RELAY TX FILTER
TX INPUT ANT
BYPASS PATH
BSS11_Ch5_46


View of the Horisoncompact with booster unit
RF CABLE RF CABLE
TO ANTENNA 2 TO ANTENNA 1
Horizoncompact
booster
TX2
RX
TX1
RS232
Horizoncompact
ALARM
BTS
LINK
BSS11_Ch5_47


Chapter 6
Horizonoffice

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 6
Horizonoffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Standard equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Optional equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Architecture of BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Horizonoffice hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Controller Unit Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Overview of power distribution unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Overview of specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Torque values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
CU to RF head interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
RF head receiver sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
RF head transmitter output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
Frequency band characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
External features of CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–18
Internal features of CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20
Overview of interconnect panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22
HIB board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Overview of HIB board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Location of HIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Description of HIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Overview of E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Location of E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Description of CIM and BIM boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Base Shelf Unit (BSU) assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
Overview of BSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
BSU numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
BSU shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
Ventilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–32
Backplane connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–32
HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–34
Overview of HDSL modem shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–34
HDSL connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–36
Power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
Overview of power supply system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
IPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
Functional description of IPSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–40
Power Distribution Unit (PDU) components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Overview of PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Input power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44
Circuit breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–44

ISSUE 1 REVISION 2
The Distribution Alarm Board (DAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46

Purpose of DAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46
Fuses and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–48
Switch settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–50
Alarm functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–50
Visual warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–52
Communicate alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–52
Cabinet Protection Board (CPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Purpose of Cabinet Protection Board (CPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Requirement of CPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Specifications of CPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56
Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56
Fan cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Location of fan cooling system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Requirements for fan cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–58
Alarm processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Introduction to alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Requirements for CU alarm system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Controller power system alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–60
Controller alarm details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–62
Digital Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Full size boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
Half size boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–66
HDSL modem boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–68
Introduction to HDSL modem boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–68
Purpose of GPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
Requirements of GPROC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
GPROC2 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–70
The Bus Termination Card (BTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72
Purpose of BTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72
Requirements of BTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72
Purpose of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Requirements of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Brief description of KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–74
Purpose of GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76
Requirements of GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76
The Multiple Serial Interface (MSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
Purpose of MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
Requirements of MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78
The LANB Extender half size board (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Purpose of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Requirements of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80
Brief description of LANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–80

ISSUE 1 REVISION 2
The Parallel Interface Extender (PIX) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82

Overview of PIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82
Requirements of PIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–82
Purpose of BBBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84
Requirements of BBBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84
The Management Interface Extender (MIX) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Purpose of MIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Requirements of MIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86
System clock and interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–88
The Line Terminal Unit (LTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
Purpose of LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
Requirements of LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–90
The Exchange office Management Unit (EMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Purpose of EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Requirements of EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Overview of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
RF features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Multicarrier head mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–94
Description of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
Physical description of RF head . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
Power system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–98
RF transceiver board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–100
RF Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–102
Connector pin-out details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
Main source supply input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
Battery input / output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–104
External alarm connector on RF PCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
HDSL connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
Multi head Sync Input connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–108
Multi head Sync Output connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–108

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Standard
equipment
The standard Horizonoffice BTS, comprises a Controller Unit (CU) which can control up
to 24 Radio Frequency units (RF heads) for in-building use. The RF single carrier heads
operate in all frequency bands that adopt the GSM standard (GSM900 and DCS1800).
The CU consists of a GSM Base-shelf Unit (BSU) and a High bit-rate Digital Subscriber
Line (HDSL) modem shelf for communications with the RF heads. In addition, the CU
contains fans and power supplies.
The standard CU cabinet is fitted with one Base Shelf Unit (BSU) card cage which is
fitted into the lower half of the cabinet. The BSU is organized into two tiers. The lower tier
contains full size boards. The upper tier contains half size boards.
The BSU is equipped with an Multiple Serial Interface (MSI) board, which provides either
dual E1 links for connection to the network, or dual E1 links to interface to the HDSL
modem shelf. The connection to the network is to a BSC or a daisy chain BTS.
The key objective for the CU is the use of in-building twisted-pair wiring as the means of
interconnect between the RF heads and the CU.
Connectivity between the CU and the BSC is over an E1 line.
Each E1 interface, which connects to an HDSL modem board, is able to communicate
with up to two RF heads via HDSL links.
An option is available for a CIM (T43) board for interfacing to a 75 ohm single ended
network, or a BIM (BIB) board for interfacing to a 120 ohm balanced network.
The 900 or 1800 MHz RF head is a single Field Replaceable Unit (FRU) capable of being
installed with minimal specialist handling equipment. The only access required is for
connection of power, communications link and, if required, external antenna. Each RF
head enclosure can be wall, pillar mounted, up to 1 km away from its CU cabinet. The
CU and RF heads are suited for indoor use only.
Optional
equipment
Optional equipment that can be ordered for the Horizonoffice consists of the following
two items:
S An external rectifier rack that is powered from the customers’ main ac power
source to provide the –48 V dc needed to supply the CU
S A battery backup pack to provide an emergency –48 V supply in the event of a
failure of the main ac or dc supplies

ISSUE 1 REVISION 2
General view of the Horizonoffice Controller Unit (CU)
ig.044.rh
BSS11_Ch6_01

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
RF head
ig.045.rh
BSS11_Ch6_02
.
Optional external –48 V dc rectifier unit
ig.072.rh
BSS11_Ch6_03

Architecture of BTS ISSUE 1 REVISION 2
Architecture of BTS
Horizonoffice
hardware
The hardware for the CU is based on base station architecture, but with the following
objectives:
S The CU uses a radio interface via an HDSL link using an HDSL modem and a
single pair link.
S An MSI board is used to route data from the Time Division Multiplex (TDM) bus
through the HDSL Line Terminal Unit (LTU) for routeing to the RF head.
S The CU supports up to 24 RF heads.

ISSUE 1 REVISION 2 Architecture of BTS
Diagram of internal architecture
EXTERNAL
BSC
2M E1 LINKS
TDM BUS
SERIAL BUS
UP 16M CLK A
TO
M 6 G G G M
M M OFF M K I
S P P C
S S S S X
I R R L
I n I I W O O K
C C 16M CLK B
MCAP BUS
MODEM RESETS
UP TO
12 OFF 2M E1 LINK 2M CLK
ÓÓÓÓÓ
HDSL RS 232 CONTROL LINK
MODEM
ÓÓÓÓÓ
(VIA FRONT PANEL
RACK
L L L
ÓÓÓÓÓ
L CONNECTORS)
T T T T E
ÓÓÓÓÓ
U U U U UNUSED M
SLOTS
ÓÓÓÓÓ
U
1 2 3 12
ÓÓÓÓÓ
TWISTED
PAIR B
HDSL MODEM
TWISTED
PAIR A RF HEADS
1 2 3 23
TRX
BOARD
RF HEAD 24
BSS11_Ch6_04
NOTE
The HDSL Interface Board (HIB) located on the EMC barrier between the LTU
and RF head twisted pair is not shown.

Controller Unit Enclosure ISSUE 1 REVISION 2
Controller Unit Enclosure

The Controller Unit (CU) enclosure consists of an aluminium cabinet. This houses the
following major components:
S BSU Shelf.
S HDSL modem shelf.
S Fans/power supplies.
BSU shelf
The BSU shelf provides the base control function for the CU supporting up to 24 RF
heads using HDSL communication links. The BSU is organized into two tiers. The lower
tier supports the equipage of full size boards whilst the upper tier supports the equipage
of half size boards.
Part 2 (Controller Unit) of this section gives a detailed description of the BSU shelf
HDSL modem
shelf
The HDSL modem shelf provides slots for 16 HDSL modem boards (LTUs) and one
modem management board (EMU). The LTUs provide HDSL processing and transport
capability, each being able to communicate with up to 2 RF heads. Loading and shelf
MMI functions are transferred over an RS–232 link to the GPROC2 MMI port via the MIX
board.
Part 2 (Controller Unit) of this section gives a detailed description of the HDSL modem
shelf.
Overview of
power
distribution unit
The Power Distribution Unit (PDU) is located on the top shelf of the cabinet and:
It consists of:
S A Distribution Alarm Board (DAB).
S A circuit breaker panel containing seven dc circuit breakers.
Overview of fan
cooling system
The cooling system, in conjunction with the correct use of shelf airflow deflectors,
provides adequate cooling for all cabinet equipment. The fan tray assembly contains
three fans; each fan has a fan stall sensor which is connected to alarm circuits in the
DAB through connector PC5.
Part 2 (Controller Unit) of this section gives a detailed description of power distribution
and fan cooling.

ISSUE 1 REVISION 2 Controller Unit Enclosure
Power system alarms and reporting
–48 V dc INPUT
SMOKE DETECTOR
(HIDDEN FROM VIEW)
CIRCUIT BREAKERS
DISTRIBUTION ALARM
BOARD
POWER SUPPLIES
The power system uses the standard BSS alarm reporting scheme, which includes visual
alarms. The CU supports up to 16 external alarm inputs and eight relay outputs (as pro-
vided by two standard PIX half size boards).
ig.046.rh
BSS11_Ch6_05

Specifications ISSUE 1 REVISION 2
Specifications
Overview of
specifications
The Horizonoffice specifications, including frequency band characteristics, are tabulated
in this chapter.
Environment
The environmental limits are shown in Table 6-1.
Table 6-1 Environmental limits

Environment Temperature Humidity
Operating –5 _C to +45 _C 5% to 95% non-condensing
Storage –45 _C to +70 _C 8% to 100% non-condensing
Dimensions
The dimensions are shown in Table 6-2.
Table 6-2 Dimensions

Height Width Depth
CU 1620 mm 710 mm 470 mm
RF head 210 mm (landscape) 315 mm (landscape) 98 mm
Rectifier unit 133 mm 482 mm 355 mm
Battery box 420 mm 710 mm 470 mm
Weights
The weight figures are shown in Table 6-3.
Table 6-3 Weights

Weight Comments
CU 138 kg (equipped with
redundancy)
24 RF head version
124 kg (no redundancy)
12 RF head version
133 kg (with redundancy)
12 RF head version
RF head 2.3 kg Without Battery Pack fitted
4.9 kg With Battery Pack fitted
Rectifier unit 13 kg
Battery box 60 kg Without batteries

ISSUE 1 REVISION 2 Specifications

Torque values
Table 6-4 provides torque values.
Table 6-4 Torque values

Screw/bolt size M4 M6 M8 M10
Value 2.2 3.4 5 10
NOTE
Values for M12 screws/bolts depend on local suppliers. Refer to manufacturer
data for correct torque values.
Power
requirements
The maximum current requirements are shown in Table 6-5.
Table 6-5 Power requirements

Supply voltage Maximum supply current range
CU Nominal –48 V dc if using an 21.2 A
in-house dc supply (Input tolerance (fully redundant plus 6 RF heads)
is in the range –40 V to –72 V dc)
24.0 A
(fully redundant plus 12 RF heads)
A supply voltage in the range 88 to
264 V ac (nominal 230 V ac) if using 27.3 A
the external rectifier option, (fully redundant plus 18 RF heads)
Motorola Part No. 01-86740N01 30.1 A
(fully redundant plus 24 RF heads)
RF 88 to 270 V ac 0.5 A
head 45 to 66 Hz (Includes Battery Pack charging)


Power
consumption
Table 6-6 shows the nominal and maximum power consumption figures for the CU
cabinet.
Table 6-6 CU cabinet power consumption

Nominal power consumption Maximum power consumption
676 W 846 W
(fully redundant plus 6 RF heads) (fully redundant plus 6 RF heads)
762 W 959 W
871 W 1091 W
957 W 1200 W
The power shown above is for the CU cabinet only. The RF heads are powered
individually from a local source, see Table 6-7.
Table 6-7 shows the nominal and maximum power consumption figures for the RF head.
Table 6-7 RF head power consumption

Nominal power consumption Maximum power consumption
GSM900 31 W 44 W
DCS1800 33 W 47 W
CU to RF head
interconnection
The CU to RF head interconnections are shown in Table 6-8.
Table 6-8 CU to RF head interconnections

Type Specification Maximum range
HDSL Twisted pair, minimum wire 1000 m
gauge 26 AWG
RF head receiver
sensitivity
The sensitivity of the receiver is –88 dBm GSM900 and –95 dBm DCS1800.
NOTE
The RF head receiver is designed to operate up to an Rx input power of –5
dBm (GSM) in a static environment.


RF head
transmitter
output
The specified maximum transmitter output power is +14dBm for GSM900 and +20dBm
for DCS1800.
NOTE
The RF unit supports transmitter power control over a range of 0–
12dB, in 2 dB steps.
Frequency band
characteristics
The RF head channels are duplex (transmit and receive) with the characteristics listed in
Table 6-9:
Table 6-9 Frequency band characteristics

GSM900 DCS1800
Transmit frequency band (MHz) 925 to 960 1805 to 1880
Receive frequency band (MHz) 880 to 915 1710 to 1785
Transmit/receive duplex separation 45 95
(MHz)
Channel width (kHz) 200 200
Number of channels 174 374
Transmit channel centre frequency Even 10ths of a MHz Even 10ths of a MHz
(MHz) from 935.2 to 959.8 from 1805.2 to
1879.8
Receive channel centre frequency Even 10ths of a MHz Even 10ths of a MHz
(MHz) from 890.2 to 914.8 from 1710.2 to
1784.8


External features
of CU
The cabinet door is hinged on the left side of the cabinet and has inlet and outlet air
vents in the door. The door incorporated a key lock.
All connections to the cabinet are on the interconnect panel, which is the cabinet top
panel. All cabinets are RF/EMI shielded.

External view of CU
ig.044.rh
BSS11_Ch6_06

Internal features
of CU
The CU contains the following elements.
Power distribution
The power distribution is located at the top of the CU and comprises –48 V dc and +27 V
dc circuit breaker distribution, Distribution Alarm Board (DAB) and Cabinet Protection
Board (CPB).
HDSL module
The upper most part of the CU cabinet contains the HDSL modem shelf. This shelf
accommodates up to 16 Line Termination Units (LTU) High bit-rate Digital Subscriber
Line (HDSL) boards.
NOTE
Only the first 12 LTU slots out of the 16 slots are utilized.
BSU cage
The BSU assembly consist of:
S A backplane.
S Two vertical slot shelves containing either full size or half size digital boards.
S A compartment for three Integrated Power Supplies (IPSMs).
Fan tray
The fan tray contains three axial fans.
The CU can tolerate a single fan failure within the tray.

View of CU top panel
MS 1 MS 0
PIX 0 BA
BACKUP
RF HEAD RF HEAD
23
HIB 1
13 11
HIB 0
1
EAR
24 14 2
15
16
12
3
4
CONNECT
17 5
PIX 1
18 6
19 7
20 8
21
22
9
10 –48 V dc
HIB 1 HIB 0 0 V dc
BSS11_ch6_07
Internal view of CU
CIRCUIT BREAKERS SMOKE DETECT OR

(HIDDEN FROM VIEW)
DISTRIBUTION ALARM
BOARD
CABINET PROTECTION
BOARD
HDSL MODEM CAGE
(HIDDEN FROM VIEW)
BASE SHELF UNIT
POWER SUPPLIES
AIR BAFFLE
THREE FANS
(BEHIND AIR BAFFLE)
ig.046.rh
BSS11_Ch6_internal view

Interconnect panel ISSUE 1 REVISION 2
Interconnect panel
Overview of
interconnect
panel
The interconnect panel is mounted on the top of the cabinet and provides connections
for:
S DC input power.
S HDSL line interconnect modules.
S Battery backup input for DRAM.
The E1 line interconnection boards are:
S T43 interconnect board 75 ohm or
S Balanced-line interconnect board – 120 ohm (BIB).

ISSUE 1 REVISION 2 Interconnect panel
Top interconnect panel layout
J13
J14
J17 J5
J16
MS 1 MS 0
J7
J8
J0
J11
J10
BATT
J1
J2
J4
PIX 0 BACKUP
RF HEAD RF HEAD
HIB 1 HIB 0
23 13 11 1
24 14 12 2
PIX 1 15
16
3
4
17 5
18 6
19 7
20 8
21 9
22 10
HIB 1 HIB 0
BSS11_ch6_top_interconnect
Top panel connectors
Top Panel Connectors

Connector Function Internal destination External
destination
Battery DRAM backup DAB connector PC4 and Backup battery or
Backup. battery. BBBX connector PC2. additional –48 V
dc supply.
MS0 (MS1 not Up to four E1 links. MS1 connector upon BSU BSC or daisy
used). backplane. chain BTS.
HIB0 and HIB1 Provides an HIB0 and HIB1 connectors RF heads.
interconnect and on the HDSL rack.
signal conditioning
for the HDSL signal
lines to the RF
heads.
PIX0 and PIX1 Alarm connectors. PIX0 and PIX1 connectors Customer
to BSU on PIX mating equipment.
connectors.
BSS11_Ch6_08

HIB board ISSUE 1 REVISION 2
HIB board
Overview of HIB
board
The HIB boards provide the external point of connection for the RF heads. HIB 0 feeds
RF heads 1 to 12 and HIB 1 feeds RF heads 13 to 24.
Location of HIB
The HIB interface module plugs into the top panel, through a 37 pin D-type connector.
Description of
HIB
The board has only passive components and a single board connects 12 RF heads to six
HDSL modem boards inside the cabinet. A full system requires two of these boards to
support 24 RF heads.
The HIB provides a 37 way 0.1” pitch female ‘standard’ D Type for internal connection.
The connection to the HDSL modem cards is via cabling within the CU cabinet.
The board features IDC connections for the cabling from the RF heads.
The HIB board accepts a range of diameters of copper loop cable, with a diameter of 0.4
mm as a minimum requirement.
The board is secured to the top panel by four cross head screws.

ISSUE 1 REVISION 2 HIB board
Diagram of HIB board with HDSL connector
22 10
21 9
20 8
19 7
18 6
17 5
16 4
15 3
14 24 2 12
13 23 1 11
HIB 1 HIB 0
HDSL CABLE
STANDARD RJ11 TELEPHONE

CONNECTOR TO FIT RF HEAD BSS11_Ch6_09

E1 interface ISSUE 1 REVISION 2
E1 interface
Overview of E1
interface
An interface module is provided to terminate the 2.048 Mbit/s (E1) links. It also provides
an EMC barrier between the internal electronics and the external environment.
Two types of interface module are available:
S CIM.
S BIM.
Location of E1
interface
The E1 interface module plugs into the top panel, through a 37 pin D-type connector.
Description of
CIM and BIM
boards
CIM (T43) board

A CIM board provides the impedance matching between the E1 circuit lines and the
BSU backplane.
The board provides an interface for up to six input and six output unbalanced coaxial 75
ohm E1 lines.
Twelve transformers are used on the board to provide impedance matching between the
E1 circuit lines and the Multiple Serial Interface (MSI) boards. Each transformer has a
1:1.25 turns ratio to match the external 75 ohm and backplane 120 ohm connections.
Connection is made using a 37 pin D-type connector to the interconnect panel and twelve
type 43 coaxial connectors to the external E1 circuit lines. The board is secured by four
cross head screws.
BIM (BIB) board

A BIM board provides the impedance matching between the E1 circuit lines and the BSU
backplane.
The board provides an interface for up to six input and six output balanced 120 ohm E1
lines.
Twelve transformers are used on the board to provide impedance matching between the
E1 circuit lines and the MSI boards. Each transformer has a 1:1 turns ratio to match the
external and backplane 120 ohm connections.
Connection is made using a 37 pin D-type connector to both the interconnect panel and
the external E1 circuit lines. The board is secured by four cross head screws.

ISSUE 1 REVISION 2 E1 interface
Diagram of line termination boards
J0
J8 J4
J14 J10
BIM (BIB)
CIM (T43) J16 J2 J1
J13 J11
BOARD
BOARD
J7 J1
J17 J5
J0
BSS11_ch6_10

Base Shelf Unit (BSU) assembly ISSUE 1 REVISION 2
Base Shelf Unit (BSU) assembly
Overview of BSU
A BSU assembly consists of:
S A backplane.
S Two vertical slot module shelves containing the required digital boards:
– The upper shelf holds half size digital boards.
– The lower shelf holds full size digital boards.
S A three-compartment shelf for the power supply boards.
BSU numbering
BSUs are numbered from F backwards using the sixteen position (0 to F hex) rotary
switch on the LANX board. This rotary switch sets the BSU LAN address.
BSU shelf
The BSU shelf provides the base control function for the CU. The shelf can manage up
to 24 RF heads. The BSU shelf interfaces to the LTUs. The BCU and LTU are
connected via E1 links. Each MSI board can communicate with up to four heads via two
LTUs.
A thermostat is located in the upper section of the cabinet and connected to the rear of
the lower section of the backplane. If the internal cabinet temperature reaches 70 oC,
the power supply will shut-down.
This thermal protection feature is in addition to the safety shut-down features provided by
the CPB.

ISSUE 1 REVISION 2 Base Shelf Unit (BSU) assembly
Diagram of BSU connectors
PART OF BSU BACKPLANE
AI0
KS0
AI1 MS0 TO HDSL SHELF)
AI2 DR5
DR4
MS1 (TO E1 LINKS)
DR3
DR2
MS2 (TO HDSL SHELF)
DR1
HALF SIZE DR0
BOARDS MS3
(NOT USED)
KS1
GK0
LANX
FULL SIZE
BOARDS
MIX
PIX
BBBX
BLANKING
PLATE
SOME BLANK
IPSM DISABLE
SENSE CONNECTOR
(CONNECTS TO TOP
PANEL THERMOSTAT) BSS11_Ch6_11

Shelf board fit

The table shows the board positions in a fully equipped BSU shelf assembly:
Table 6-10 Shelf board fit

Slot Half size boards Slot Full size boards
U0 Not used in this cabinet L0 BTC
U1 Not used in this cabinet L1 KSW (R)
U2 Not used in this cabinet L2 GCLB (B)
U3 Not used in this cabinet L3 GCLK (B)
U4 Not used in this cabinet L4 GCLK (A)
U5 Not used in this cabinet L5 GCLK (A)
U6 Not used in this cabinet L6 SPARE
U7 Not used in this cabinet L7 MSI RF (21 - 24)
U14 Not used in this cabinet L14 MSI 1
U15 L15 MSI RF (5 - 8)
BBBX
U16 L16 MSI 0
PIX 0
U17 PIX 1 L17 MSI RF (1 - 4)
U18 MIX 0 L18 SPARE
U19 LANX B L19 SPARE
U20 LANX A L20 GPROC2
U21 Not used in this cabinet L21 GPROC2
U24 Not used in this cabinet L24 GPROC2(R)
U27 Not used in this cabinet L27 KSW (A)
U28 Not used in this cabinet L28 BTC


Ventilation
Blanking plates are inserted in all unused full size board and power supply slots to assist
with the correct airflow and ventilation.
Backplane
connectors
Table 6-11 shows the function of each connector fitted at the top of the BSU backplane.
Table 6-11 Backplane connectors

Connector Function
AI0 Serial bus primary, to DAB.
AI1 Serial bus redundant, to DAB.
MS0 MSI connector, to interconnect with HDSL modem shelf.
MS1 Not used.
MS2 MSI connector, to interconnect with HDSL modem shelf.
MS3 Not used.


HDSL modem shelf ISSUE 1 REVISION 2
HDSL modem shelf
Overview of
HDSL modem
shelf
The HDSL modem shelf consists of:
S A backplane.
S A vertical shelf to hold LTUs and an exchange-rack management unit (EMU).
The HDSL modem shelf is capable of housing up to 16 LTUs. For the maximum
supported configuration, only twelve LTUs are required and one EMU. The LTUs provide
HDSL processing and transport capability. Each can communicate with up to two RF
heads via the HIB.
The LTU converts between the E1 formatted data from an MSI board, into HDSL
formatted data for two RF heads. The link is used to transport traffic and RSS data, plus
frequency and time reference information to a HDSL modem within the RF head.
The HDSL modem shelf is configured for a minimum amount of management support.
Upon power up or reset, the LTUs attempt to establish a connection with the far-end
modems located in the RF heads.

ISSUE 1 REVISION 2 HDSL modem shelf
Diagram of HDSL modem shelf
LTU BOARDS
EMU BOARD
BSS11_ch6_12

HDSL modem shelf ISSUE 1 REVISION 2
HDSL connectors
Table 6-12 shows the connectors on the upper shelf.
Table 6-12 HDSL connectors

Item Qty Function
D25F Data port connectors 16 Not used
10Base T port 1 Not used.
10Base 2 port 1 Not used.
EXT CLK (External Clock) 1 2 MHz clock reference for HDSL boards
(per G.703, paragraph 10).
D9F HDSL connectors 16 Connectors HDSL pairs to the HIB.
(12 used)
Five-position –48 V dc 1 Connects dc power to the shelf.
power-terminal strip
D25F RS-485 connector 1 Not used.
D25F alarm connector 1 Not used.
D15F 120-ohm G.703 16 Connets to the MSI E1 interface
(12 used) (balanced 120 ohm).
BNC 75-ohm G.703 In 16 Not used.

connectors
BC 75-ohn G.703 Out 16 Not used.
connectors
Protection switch module 8 Not used.
connectors

ISSUE 1 REVISION 2 HDSL modem shelf
HDSL modem shelf and pin connections
G.703 120 Ohm 15 Way D
S S S S S S S S S S S S S S S S
L L L L L L L L L L L L L L L L
O O O O O O O O O O O O O O O O
T T T T T T T T T T T T T T T T
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1
0 1 2 3 4 5 6
HDSL 9 Way D
N M M
O
T O A
P
D N
O E A
P
MODEMS U
L
M G
E
A
T
R
E
D
1 2 3 4 5 6 7 8 9 10 11 12 13–16
BSS11_Ch6_13
The connectors will be referred to in the following manner:

15 Way D: Jx(G703).[pin number] e.g. slot 7, pin 5 is J7(G703).5
9 way D: Jx(HDSL).[pin number] e.g. slot 7, pin 5 is J7(HDSL).5

Power supply system ISSUE 1 REVISION 2
Power supply system
Overview of
power supply
system
The CU –48 V dc input supply is routed via the input studs on the top panel to the Power
Distribution Unit (PDU). The PDU contains all the –48 V dc and +27 V dc distribution
circuit breakers.
The –48 V dc is routed to the Integrated Power Supply Modules (IPSM), the HDSL
modem shelf and the CPB. The +27 V dc, generated by the IPSMs, is routed to the
cabinet fans and DAB. An auxiliary +27 V dc is also fed to the CPB from the DAB.
The HDSL boards (LTUs and EMU) have on-board power converters which are powered
from the –48 V dc supplied from the PDU.
There are three compartments at the base of the BSU assembly for the IPSMs. The
IPSMs supply all the power for the full size and half size boards within the BSU cage.
IPSM
The Integrated Power Supply (IPS) system for each BSU in a positive earth (–48 V/–60 V
dc) system consists of up to three plug-in IPSMs.
The IPSM is a switching type dc – dc power converter that converts the cabinet dc input
S +27.5 V 5 % at 45 A (full load current).
S +5.1 V 2 % at 87.5 A (full load current).
S +12 V 5 % at 2.5 A (full load current).
S –12 V 5 % at 2.5 A (full load current).
The BSU backplane connects the outputs of each IPSM in parallel.
When three IPSMs are fitted in the IPS system, they load-share as follows:
S Two IPSMs provide sufficient power for a fully equipped BSU.
S The third IPSM provides n + 1 redundancy.
An IPSM in an alarm condition sends an alarm message to the master GPROC2 via the
serial bus.

ISSUE 1 REVISION 2 Power supply system
Location diagram of IPSMs
IPSMs
(REAR VIEW)
ACTIVE LED (GREEN) – ON
WHEN ALL OUTPUT
VOLTAGES ARE PRESENT
AND WITHIN TOLERANCE. 25-PIN D-TYPE
CONNECTOR
(FEMALE)
(FRONT VIEW)
+27.5 V RTN
ALARM LED (RED) – ON +27.5 V (OUTPUT)
WHEN ONE OR MORE C GND (CHASSIS GROUND)
ALARM CONDITIONS EXIST. V RTN (0 V INPUT)
OFF WHEN NO ALARM + 5 V RTN (GROUND FOR +5 V OUTPUT) V IN (–48 V/–60 V INPUT)
CONDITION EXISTS. + 5 V RTN (GROUND FOR +5 V OUTPUT)
BSS11_Ch6_14

Functional
description of
IPSM
The IPSM has six main functions.
S Normal operation.
S Redundancy.
S Power supply shutdown.
S Monitoring circuits.
S Circuit protection.
S LED displays.
Normal operation
When plugged into the backplane, all IPSM power outputs are connected in parallel.
During normal operation, the IPSMs equally share load current demand of the CU loads
(BSU boards, cabinet fans, DAB and CPB).
Redundancy
Two IPSMs can provide adequate operating power for all modules in a CU.
A third IPSM can be added for redundancy (n + 1 redundancy). For small configurations
one IPSM can provide adequate operating power, with a second added for redundancy.

In the event of a malfunction of an IPSM, the IPSM inhibits itself and will not cause the
other IPSMs to go out of service.
The malfunctioning IPSM illuminates its red alarm LED, and informs the GPROC2 of its
fault condition.
Monitoring circuits
Parallel output connections allow each IPSM to sense its own output lines for:
S Over-voltage protection to shut the IPSM down if the output voltage exceeds 1.2 to
1.3 times the rated output.
– 1.05 to 1.3 times the full load rating of the +5.1 V dc output.
– 1.05 to 2 times the full load rating of the +12 V dc and –12 V dc outputs.
The BSU shelf GPROC2 monitors the status of each IPSM via a serial alarm link on the
backplane for:
S Overtemperature.

IPSM diagram
BACKPLANE CONNECTOR
VOUT (+5 V)
VOUT (+12 V)
VOUT (–12 V)
VOUT (+27.5 V)
GREEN POWER
LED CONVERTER
AND
RED SYSTEM
SERIAL LINK
OUTPUT FAIL
OVERTEMPERATURE
VIN (–48 V/–60 V)
BSS11_Ch6_15

Circuit protection
Additional internal IPSM circuit protection includes:
S Input dc reverse polarity protection to prevent IPSM damage using an input series
diode that blocks reverse voltages.
S Thermal protection to send an alarm message to the GPROC via the serial port,
then shut the IPSM down, if the IPSM ambient temperature exceeds a safe level.
After an alarm condition has ceased, normal IPSM operation is automatically restored.
LED display
Two LEDs are mounted on the front of the IPSM to indicate the following:


Power Distribution Unit (PDU) components ISSUE 1 REVISION 2
Power Distribution Unit (PDU) components
Overview of PDU
The PDU is located on the top shelf of the cabinet and:
It consists of:
S A Distribution Alarm Board (DAB).
S A circuit breaker panel containing seven dc circuit breakers.
Input power
DC input power is applied at the interconnection panel on top of the cabinet and is routed
to:
S The VIN bus bar.
S The earth (GND) bus bar in the PDU.
A second bus bar obtains +27 V dc power from the integrated power supply modules
(IPSMs) in the lower BSU.
Circuit breakers
The seven circuit breakers distribute power to units within the cabinet.
S CB1 (60 A) provide the main input switch and power to the CPB.
S CB2 to CB4 (30A) provides –48/–60 V dc to the IPSMs in a positive earth cabinet.
S CB5 (1 A) provide –48 V dc to the CPB.
S CB6 (2 A) provide –48 V dc to the HDSL modems.
S CB7 (3 A) provide +27 V dc to the DAB.

ISSUE 1 REVISION 2 Power Distribution Unit (PDU) components

The Distribution Alarm Board (DAB) ISSUE 1 REVISION 2
The Distribution Alarm Board (DAB)
Purpose of DAB
The DAB:
S Distributes +27 V dc to units within the cabinet via 25 fuses (only four are used).
S Monitors alarm lines.
S Passes individual alarms to the master GPROC2.
The DAB processes operational failure signals from:
S Ruptured fuses.
S The fan stall sense line from each cooling fan.
Two bi-coloured LEDs (D43 and D8) are mounted on the DAB to indicate DAB and
cabinet-based faults. The other LEDs indicate fuse failures as shown in the tables in this
section.

ISSUE 1 REVISION 2 The Distribution Alarm Board (DAB)
DAB diagram
NOT NOT NOT NOT NOT NOT 0.5A NOT 0.5A NOT 0.5A 2.0A
USED USED USED USED USED USED FAN 0 USED FAN 1 USED FAN 2 CPB PWR
F26 F25 F24 F23
LED LED F8 F9 F7 F4 F5 F6 F26 F21 F25 F22 F24 F23

D43 D8 0V
PC7
PC3 S2 LED LED LED LED LED LED LED LED LED LED LED LED
U4 D21 D23 D24 D27 D29 D31 D32 D33 D35 D37 D38 D41
PC4
PC5 PC6
LED LED LED LED LED F19 LED LED LED LED LED
PC2 D22 D25 D26 D28 D30 D34 D36 D39 D40 D42
S1
+27 V F11 F10 F13 F12 F15 F14 F30 F29 F27 F28 F20 F18
0.5A
PAB SUPPLY
CABINET DAB FAIL

FAILURE NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
USED USED USED USED USED USED USED USED USED USED USED USED
DIAGRAM OF
DIL SWITCH
S2
SETTING
ACTUAL DIL
SWITCHES DISRIBUTION ALARM
WARNING BOARD LABEL
LEFT SIDE LIVE (DIL SWITCH SETTINGS)
TERMINALS
RIGHT S1
SIDE
DIAGRAM OF DIAGRAM OF
DIL SWITCH DIL SWITCH
ALARMS SETTING FOR
BATTERY BATTERY AND
NO ALARMS ALARMS
OR BATTERY
BACKUP
NOT USED BSS11_Ch6_DAB_diagram

Fuses and LEDs

Table 6-13 details the functions of the DAB fuses and LEDs used in the CU cabinet
version. A description of the ’not used’ fuses is included for completeness, see note
below.
Table 6-13 DAB fuses and LEDs

Fuse Rating Power to LED
F12 4A Not used D28
F13 4A Not used D26
F18 2A Not used D42
F19 0.5 A DAB supply no LED
F20 2A Not used D40
F21 2A Not used D33
F22 2A Not used D37
F23 2A CPB D41
F24 0.5 A Fan 2 D38
F25 0.5 A Fan 1 D35
F26 0.5 A Fan 0 D32
F27 2A Not used D36
F28 2A Not used D39
NOTE
If one of the ’not used’ fuses fails, then the DAB will report an alarm. See
category 523 for CU cabinet dc power distribution. The CU functionality will
not be effected by the active alarm. The necessary action would be to replace
the failed fuse and the alarm will be cleared.


Switch settings
DAB switches S1 and S2 set the following configurations in the CU:
Table 6-14 DAB switch settings

Function Switch Position Setting
Spare S1 4 OFF
Battery backup O/P 2 S1 5 ON
Battery backup O/P 1 S1 6 ON (Set to OFF when alarms
are enabled in BBBX)
Battery backup I/P 2 S1 7 ON
Battery backup I/P 1 S1 8 ON (Set to OFF when alarms
are enabled in BBBX)
DRCU5 S2 1 OFF
DRCU2 S2 2 OFF
DRCU4 S2 3 OFF
DRCU1 S2 4 OFF
DRCU3 S2 5 OFF
DRCU0 S2 6 OFF
Spare S2 7 OFF
BB ID S2 8 ON (Set to OFF when the
BBBX functionality is not
utilized)
Alarm functions
The DAB produces alarms for several different devices and modules:
NOTE
For this Horizonoffice configuration most of the DAB is not used.
S 25 fuses : the CU utilizes 4 off only.

S Six circuit breakers : these alarms are not applicable for the function of the CU.
S Six fan alarms : the CU utlizes 3 off only, with the three original fan alarms now
reused as CPB reporting alarms.
Each signal from the fuse alarms is at a nominal +27 V dc level and is brought to a TTL
high level. Under no-fault conditions, the TTL output is held at a high level.
The Addressable Asynchronous Receiver/Transmitter (AART) has eight status inputs,
which are routed to the master GPROC2, via the BSU backplane. These are multiplexed
to obtain the required alarm functionality.


Visual warnings
Each +27 V dc (nominal) fuse protected branch circuit that powers cabinet equipment
has a corresponding LED indicator on the DAB. The LED lights if the fuse is ruptured by
a fault condition, and the associated alarm line goes low.
The DAB also provides visual warnings for alarms via two bi-coloured LEDs:
S D43 indicates any internal cabinet failure.
S D8 indicates a fuse failure on the DAB only.
Both LEDs are driven by the master GPROC2 in response to alarms generated by the
DAB; red indicates an alarm, otherwise the LEDs remain green. If the master GPROC2
is not running then both LEDs default to red.
Communicate
alarms
The master GPROC2 polls the DAB for alarm status via the serial bus. The master
GPROC2 always initiates connections, in which all modules respond with status reports
on the serial bus.
The DAB indicates operational failure reports from the following:
S Ruptured fuses.
S Protected side of circuit breakers (except DPS circuit breakers, which are
monitored by the master GPROC2 directly).
S Fan stall sense line from each cooling fan.
S Hardware failures reported directly to the DAB are individually sent to the master
GPROC2 via the serial bus.
The serial bus circuitry is powered by + 5 V dc which powers the digital BSU. The power
supplies that provide this +5 V dc (as well as 12 V dc) deliver isolated outputs.
Thus all devices in the serial bus circuit have a return that is floating (digital) earth
relative to the cabinet (main) earth (all internal 0 volts are isolated from the incoming 0
volts which aids noise immunity). However, many of the alarm signals are referenced to
cabinet earth.


Cabinet Protection Board (CPB) ISSUE 1 REVISION 2
Cabinet Protection Board (CPB)
Purpose of
Cabinet
Protection Board
(CPB)
NOTE
A smoke detector is fitted within the Horizonoffice as it may be situated within
an office environment.
In many parts of the world, when a smoke detector is fitted the cost of
insurance is reduced.
The CPB provides the following:

S Alarms to the DAB.
S Senses the presence of smoke in the CU.
S Senses the overtemperature conditions within the CU.
S Interrupts the main input circuit breaker.
Requirement of
CPB
The CPB is fitted on the underside of the the top panel.
CPB connections
These are:
S PL1 –48 V dc supply and main circuit breaker trip coil connector (8 way).
S PL2 Smoke detector connector (6 way).
S PL3 Thermostats connector (4 way) .
S PL4 DAB connector (10 way).

ISSUE 1 REVISION 2 Cabinet Protection Board (CPB)
Cabinet Protection Board (CPB) diagram
M4 STANDOFF AND M4 SCREW POSITIONS
FRONT EDGE OF BOARD AS SEEN WHEN FITTED IN CU
L2 L3 D6
C47
DC/DC POWER
L1 MODULE PL3
PL1
C4 C46
Q10
C1 C3
D8
S1 PL4
PL2
F2 C2 U3 F1
D7
INDICATION LEDS INDICATION LEDS

see below for description see below for description
M4 SCREW M4 STANDOFF AND M4 SCREW POSITIONS
M4 STANDOFF CPB PLASTIC COVER LABEL
SW1
THERMOSTAT 1
THERMOSTAT 2
+27V PRESENT
–48v PRESENT
TEST
SMOKE FAIL
DETECTED
SMOKE
TRIP FAIL
ACTIVE
ACTIVE
SMOKE
M4 STANDOFF AND M4 SCREW POSITIONS

BSS11_Ch6_16

Cabinet Protection Board (CPB) ISSUE 1 REVISION 2
Specifications of
CPB
The specifications are divided into:
S Supply voltages
S Input to Output isolation
S Smoke trip delay
Supply voltages
The CPB is powered from the main cabinet –48 V dc supply via its own dedicated circuit
breaker. It is also powered from the 27 V dc supply derived from the DAB.
Protection
The CPB reports an alarm for the following conditions:
S Cabinet over temperature:
Internal cabinet over temperature sensed.
S Cabinet smoke detection:
Internal cabinet smoke detected.
S Cabinet protection fail:
loss of –48 V dc supply CPB.
loss of connection to main input circuit breaker trip coil.
The CPB performs a cabinet power shutdown for the following conditions:
S Cabinet over temperature sensed.
S Cabinet smoke detected.
Smoke alarm and trip

If the CPB detects an active signal from the smoke detector, the CPB sends a smoke
alarm signal to the DAB. A nine second timer period, allows the alarm to be reported at
the Operations and Maintenance Centre (OMC), prior to the CPB shutting down the
cabinet power.
The power to the system will remain off and will require manual resetting of the circuit
breaker to get the system back on.
Over-temperature alarm and trip

If the CPB detects an active signal from one of the two cabinet thermostats, the CPB
sends a “cabinet over temperature alarm” to the DAB. If the CPB then detects an active
signal from the second thermostat, in addition to the first, the CPB will trip the main
circuit breaker thus shutting down the cabinet power.
The power to the system will remain off and will require manual resetting of the circuit
breaker to get the system back on.

ISSUE 1 REVISION 2 Cabinet Protection Board (CPB)

Fan cooling ISSUE 1 REVISION 2
Fan cooling
Overview of fan
cooling system
The cooling system, in conjunction with the correct use of shelf airflow deflectors,
provides adequate cooling for all cabinet equipment. The fan tray assembly contains
three fans; each fan has a fan stall sensor which is connected to alarm circuits in the
DAB through connector PC5.
Location of fan
cooling system
The fan tray assembly is mounted directly below the BSU shelf assembly.
Requirements for
fan cooling
Power for the fans is derived from the +27 V dc busbar and is routed to the +27 dc V
terminal on the DAB, then from connector PC9 on the DAB to the fans.

ISSUE 1 REVISION 2 Fan cooling

Alarm processing ISSUE 1 REVISION 2
Alarm processing
Introduction to
alarms
This section describes the Horizonoffice CU alarms. The alarms generated are based
upon those handled by the DAB, plus an additional three new alarms. The CU alarm list
consists of:
S Active DAB alarms (a subset of the standard DAB alarm list).
S IPSM alarms via BCUP
S ‘New” CPB based alarms
S External Alarms Interface
Requirements for
CU alarm system
The CU system utilizes the existing ‘Internal Alarm System (IAS)’, ‘External Alarm
System (EAS)’ and Base station Control Unit Power supply system (BCUP) alarm
systems. In addition, three new alarms are incorporated to allow the cabinet to feature
two M-Cell based protection systems:
S Cabinet overtemperature - alarm and shutdown.
S Smoke detected - alarm and shutdown.
S Cabinet protection system fail.
Controller power
system alarms
The cabinet alarms supported are based upon those available via the DAB. The overall
cabinet still reports IPSMs (cabinet power supplies) alarms via the BCUP serial bus
within the BSU digital board cage.
Up to sixteen ‘EAS’ inputs and eight ‘EAS’ outputs, are available for customer
use, with the use of two ‘PIX’ boards located within the 3U high section of the
digital board cage.

ISSUE 1 REVISION 2 Alarm processing
CU DAB alarm table

Table 6-15 defines the alarms reported via the DAB, when used in the CU.
Table 6-15 CU DAB alarms

A2 S7 S6 S5 S4 S3 S2 S1 S0
A0 MSB 1 1
Bits 0 1 1 1 1 1
000 NO 27 V dc NO Battery 27 V dc LS Fan NO NO
D0 ALARM DAB ALARM Backup DAB 0 F26 ALARM ALARM
Supply Outputs Supply
F19 F19
001 NO 27 V dc NO Battery NO LS Fan NO NO
D1 ALARM DAB ALARM Backup ALARM 1 F25 ALARM ALARM
Supply Outputs
F19
010 NO 27 V dc Cabinet Battery NO LS Fan NO NO
D2 ALARM DAB Protection Backup ALARM 2 F24 ALARM ALARM
Supply System Outputs
F19 Fail
(was fan
5 Alarm)
011 D3 NO 27 V dc Smoke Battery NO NO NO NO
ALARM DAB Detected Backup ALARM ALARM ALARM ALARM
Supply (was fan Outputs
F19 4 Alarm)
100 D4 NO 27 V dc Cabinet Battery NO NO NO NO
ALARM DAB Over Backup ALARM ALARM ALARM ALARM
Supply Temp Outputs
F19 Alarm
(was Fan
3 Alarm)
101 NO 27 V dc Fan 2 Battery NO NO NO NO
D5 ALARM DAB Alarm Backup ALARM ALARM ALARM ALARM
Supply Outputs
F19
110 D6 NO 27 V dc Fan 0 Battery NO NO NO NO
ALARM DAB Alarm Backup ALARM ALARM ALARM ALARM
Supply Outputs
F19
111 NO 27 V dc Fan 1 Battery NO Battery NO NO
D7 ALARM DAB Alarm Backup ALARM Backup ALARM ALARM
Supply Outputs Input
F19
BSS11_Ch6_17
& BSS11_Ch6_18
The S0 to S7 and A2 and A0 bits relate to ‘multiplexer’ coding of the alarm bits upon the DAB, and
permits the GPROC 2 to decode the information and report the appropriate alarm to the OMC.

Controller alarm
details
Details of the three new alarms are given below.
Cabinet over temperature

This alarm is generated when the overtemperature thermostat “T2” reaches its set point
at +65 oC.
A +70 oC set-point thermostat, “T3” removes power from the BSU, by disabling the
IPSMs. A third thermostat, “T1”, with set-point at +80 oC, causes the CPB to remove all
power from the CU cabinet
The ‘overtemperature’ shutdown sequence is outlined in Table 6-16.
Table 6-16 Over temperature shutdown sequence

No Alarm Description
1 Overtemperature condition Generated by the CPB and ’T2’.
detected
“Cabinet Over Temperature”
T2 = +65 oC When the cabinet overtemperature alarm is
activated, the cabinet is running in an excess
ambient temperature condition.
If the excessive ambient condition further
deteriorates the cabinet power system shuts
down.
2 Overtemperature condition This condition disables the IPSMs, via ’T3’,

detected - IPSM Inhibit level and their enable line.
T3 = +70 oC The IPSMs inhibit their outputs so all power to
the BSU card cage is removed, so effectively
the site will shut down.
3 Overtemperature condition - This condition is initiated by the CPB plus ’T1’

trip level and ’T2’.
T1 = +80 oC The power system opens the main input ECB.
This action removes the –48 V dc input supply
to the IPSMs and the HDSL modem shelf.
4 None A site visit is required in order to reset the main
input ECB.
The ECB should only be reset once the cause of the overtemperature conditions
have been found and rectified.
The power system will keep the input ECB closed until the shutdown thermostat
’T1’ has cooled to its reset temperature level.

Diagram of CU cabinet
CABINET PROTECTION
–48Vdc INPUT
BOARD (CPB)
SMOKE DETECT OR
INPUT ECBs (NOT SHOWN)
THERMOST ATS :
”T1”, ”T2” AND ”T3”
DAB
HDSL MODEM RACK
3U DIGITAL CAGE
STANDARD BSU
DIGITAL CAGE 6U DIGITAL CAGE
IPSMs
FAN TRAY
(3 FAN UNITS)
BSS11_ch6_19

Cabinet smoke detected

This alarm is generated when the cabinet power system detects smoke within the
cabinet.
The shutdown sequence is outlined in Table 6-17.
Table 6-17 Smoke detected shutdown sequence

No Alarm Description
1 Smoke detected - alarm level Once smoke is detected, the alarm is
“Smoke Detected” activated.
2 Smoke detected After a delay of approximately nine seconds,

the power system opens the main input ECB.
This action removes the –48 V dc input supply

to the IPSMs and the HDSL modem shelf, so
that all the power is lost within the cabinet.
3 None A site visit is required in order to reset the main

input ECB.
The ECB should only be reset once the cause of the smoke detection has
been found and rectified.
Cabinet protection system fail

This alarm is generated when there is a failure upon the CPB which performs the
overtemperature alarm/trip and smoke detection alarm/trip functions within the cabinet.


Digital Modules ISSUE 1 REVISION 2
Digital Modules
Introduction
This part of section 6 describes the digital modules used in the controller unit (CU). In
this chapter digital modules will be referred to as digital boards.
The digital boards fit into the Base Shelf Unit (BSU) and HDSL modem shelf, described
earlier in this section.
Full size boards

Full size boards fit into slots in the card cage of a BSU. In the BSU, the slots are
numbered, right to left, from L0 to L28.
The following sections describe the full size boards that can be mounted in a BSU. The
quantity fitted depends upon the specific configuration of the BSU and HDSL modem
shelf.
The following full size boards are mounted in a BSU shelf:
S Generic Processor (GPROC2).
S Bus Terminator Card (BTC).
S Kiloport Switch (KSW).
S Generic Clock (GCLK).
S Multiple Serial Interface (MSI).
A brief overview of the boards’ functionality will be given in this section, as full size
boards were described fully in section 3.
Half size boards

Half size digital boards provide interface extension for the full size boards, enabling unit
interconnection.
The boards fit into slots in the upper card cage of a BSU shelf. The slots are numbered,
right to left, from U0 to U28.
The following half size boards are mounted in a BSU shelf:
S Battery Backup Board (BBBX).
S Local Area Network Extender (LANX).
S Management Interface Extender (MIX).
S Parallel Interface Extender (PIX).
A brief overview of the LANX, PIX and BBBX will be given in this section as they were
fully described in section 3. The MIX board functionality will be covered extensively.

ISSUE 1 REVISION 2 Digital Modules
Diagram of BSU connectors
PART OF BSU BACKPLANE
AI0
KS0
AI1 MS0 TO HDSL SHELF)
AI2 DR5
DR4
MS1 (TO E1 LINKS)
DR3
DR2
MS2 (TO HDSL SHELF)
DR1
HALF SIZE DR0
BOARDS MS3
(NOT USED)
KS1
GK0
LANX
FULL SIZE
BOARDS
MIX
PIX
BBBX
BLANKING
PLATE
SOME BLANK
IPSM DISABLE
SENSE CONNECTOR
(CONNECTS TO TOP
PANEL THERMOSTAT)
BSS11_Ch6_20

HDSL modem boards ISSUE 1 REVISION 2
HDSL modem boards
Introduction to
HDSL modem
boards
There are two types of board within the HDSL modem shelf.
S The LTU LIne Terminal Unit (LTU) is an European Telecommunication Standard
Institute (ETSI) compliant High bit-rate Digital Subscriber Line (HDSL) card.
S The EMU-830 is an Exchange Office Management Unit (EMU). The EMU-830
provides fault, alarm, configuration and performance management of HDSL circuits
deployed.
In the HDSL modem shelf, the slots are numbered left to right, 1 to 16, EMU.

ISSUE 1 REVISION 2 HDSL modem boards
Diagram of HDSL modem shelf
16 NMC 75 OHM G.703 16D25F DATA PORT

IN CONNECTORS CONNECTORS
16 D15F OHM G.703 D25F RS–485

CONNECTORS CONNECTOR
D25 ALARM
EXTERNAL CONNECTOR
CLOCK PORT
(EXT CLK)
16 BNC 75 OHM G.703
OUT CONNECTORS
16 D9F HDSL
CONNECTORS 10Base2 PORT
10BaseT PORT
FIVE POSITION –48V
dc POWER TERMINAL
STRIP
EIGHT PROTECTION SWITCH
MODULE CONNECTORS
EMU
ig.054.
rh
BSS11_CH6_21

The Generic Processor (GPROC2)

Purpose of
GPROC2
The GPROC2 board provides the processing power to control a BSC, RXCDR or BTS.
The GPROC2 cannot be used with software loads prior to GSR2.
GPROC2s in a BSU exchange control signalling in several ways:
S A token ring LAN. The LAN can link processors in several shelves via fibre optic
cable.
processor address, data and control buses to peripheral modules in the same
shelf.
S A serial bus, which communicates alarm information between GPROC2s and half
size boards. This serial bus extends to the power distribution unit.
Requirements of
GPROC2
The GPROC2 board fits into:
Slots L19 to L25 in a BSU shelf assembly.
Each BSU requires at least one GPROC2.
GPROC2 board
Brief description
The GPROC2 board contains:
S The LAN processors, which are the interface between the GPROC2 and the token
ring LAN.
S The COMM processor which, in conjunction with the TDM interface controller, is
the interface between the GPROC2 and the TDM highway.
Communication
The GPROC2 communicates with other full size boards via the MCAP bus, and with half
size modules (and modules not on the BSU shelf) via the BSS serial bus.
S Shelf ID.
S Slot ID.
S Backplane type.

GPROC2 block diagram
BACKPLANE CONNECTOR
LAN A
DRAM
RESET/ WATCHDOG TIMING LAPD
DISABLE TIMERS CONTROL PROC
SWITCH
BUS LAN A
SIZER PROC
LAN LAN A
INTERFACE
LAN B
LAN
PROCESSOR BUS
MC68040
33 MHz LAN B
PROC
DATA/ADDRESS LAN B
BUS DRAM
EXT CACHE
TDM TDM A
128 K
INTERFACE TDM B
PERIPHERAL
BUS
MAIN DRAM
(16 – 64 Mb)
EEPROM
NVRAM MCAP MCAP A
INTERFACE
MCAP A
SERIAL BUS SERIAL BUS A

TTY TEST
CONNECTOR CONTROLLER SERIAL BUS B
BSS11_Ch6_22

The Bus Termination Card (BTC) ISSUE 1 REVISION 2
The Bus Termination Card (BTC)
Purpose of BTC
The BTC terminates the backplane to keep signals on a BSU at the proper TTL level.
The BTC terminates:
S Both MCAP buses.
S Both reference clocks.
S All TDM buses (Expansion, Remote and Local).
Requirements of
BTC
Two BTC boards must be fitted in the BSU shelf, in slot L0 and slot L28, at all times.
While a faulty BTC is being replaced, another BTC must be fitted in a KSW slot to
maintain the above requirement.

ISSUE 1 REVISION 2 The Bus Termination Card (BTC)
BTC board
BACKPLANE
CONNECT OR
BSS11_ch6_23

The Kiloport Switch (KSW)
Purpose of KSW
The KSW board is a time division digital switch, and:
S Performs timeslot interchange for the active TDM highway.
S Communicates with the controlling GPROC2 via the MCAP bus.
S At a BSC, routes the logical channels dynamically on a per-call basis.
Requirements of
KSW
The KSW module fits in the following slots in a BSU shelf assembly:
S L27 for TDM highway A.
S L01 for redundancy (TDM highway B).
Brief description
of KSW
Refer to the KSW block diagram at the end of this section.
A Motorola MC56001 Digital Signal Processor (DSP) controls the KSW internally. The
DSP:
S Executes port connects between the switchbound TDM highway and the outbound
TDM highway.
S Controls the Timeslot Interchange (TSI) section via the connection RAM control
section.
S Performs on-line and off-line self diagnostics, including:
– Internal (KSW-related) tests.
– External (TDM bus-related) tests.
S Controls inbound and outbound multiplexers.
S Processes alarms.
S Updates the dynamic pattern registers.
The DSP communicates via the MCAP bus interface logic, the DSP data/address bus,
and the serial interface logic.

KSW block diagram
BACKPLANE
CONNECTOR
SERIAL
INTERFACE
LOGIC TTY INTERFACE
52
MCAP BUS MCAP BUS A 2 FOR
INTERFACE
LOGIC
52
MCAP BUS B
} REDUNDANCY
OTHER KSW CIRCUITRY

MC56001
WATCHDOG 27 MHz
DISTRIBUTION TO
TIMER TDM A CLOCK & REFERENCE
DSP DATA/ADDRES
DSP CLKS (16.384 MHz, 125 us,
COUNTERS TIMING
REFERENCE 60 ms, AND 6.12 s)
RESET/ GSM LOGIC B CLOCK & REFERENCE
DISABLE COUNTERS CLKS (16.384 MHz, 125 us,
INTERRUPT
SWITCH LOGIC 60 ms, AND 6.12 s)
REMOTE KSWX HWY

HIGHWAY INTERFACE CONTROL
CONTROL
RED LED
GREEN
LED
MUX LOCAL SWITCHBOUND HWY 0

DELAY
MUX
CONNECTION REMOTE SWITCHBOUND
DSP DATA/ADDRES
RAM CONTROL HWY 0
TIME SLOT
INTERCHANGE MUX EXPANSION SWITCHBOUND
(TSI) HWY 1
TIME SLOT
LOOP
BACK
INTERCHANGE
(TSI)
TIME SLOT
INTERCHANGE HWY 2
(TSI)
FULL–RATE
SUB–RATE
SOURCE 0
SOURCE 1
TIME SLOT
INTERCHANGE
(TSI)
HWY 3
HIGHWAY
MONITOR
DELAY
MUX PARITY
GENERATOR EXPANSION OUTBOUND HWY
OUTBOUND SELECT MUX
LOOP
BACK
TSI MODE MUX

DELAY LOCAL OUTBOUND HWY
THIRD
PARTY REMOTE OUTBOUND HWY
CONFERENCE
MEMORY
FIXED/DYNAMIC
PATTERN PARITY HIGHWAY
REGISTERS GENERATOR MONITOR
+12 V
–12 V
OUTBOUND +5 V
CONTROL
RAM GND
BSS11_Ch6_24

The Generic Clock (GCLK)
Purpose of GCLK
The BSU is equipped with the GCLK board. This provides the network and site
synchronisation for the BCU shelf and to the HDSL modem shelf. The master TDM clock
is normally synthesized from a 16.384 MHz .05 ppm stable reference (temperature
stabilized crystal oscillator) either free running or locked to a 2.048 MHz clock recovered
from one of the E1 lines.
Requirements of
GCLK
The GCLK board fits in slots L3 and L5 in the BSU shelf assemblies. The module is two
slots wide and covers L2/L3 and L4/L5.
There must be a GCLK board in either slot L3 or L5.
A second GCLK board in slot L5 provides n + 1 redundancy.
Brief description
Refer to the functional block NO TAG at the end of this section.
The GCLK board generates all timing reference signals required by the CU:
S 16.384 MHz TDM clock.
S 125 ms frame reference.

S 60 ms synchronization reference.
S 6.12 s superframe reference.
The GCLK is phase-locked to the recovered clock of a selected E1 line from an MSI
board. If the recovered clock signal is lost, and no Long Term Average (LTA) is available
upon which to synchronize, then the GCLK free-runs, providing reference stability better
than 0.05 ppm. The module incorporates self-diagnostics to detect and isolate board
faults and to select a redundant board in the event of module failure.
When a redundant GCLK is present, the GCLKs operate in a master/slave configuration
with the slaved outputs synchronized to the master. If an error is detected, the clock
control circuit reverses the master/slave status of the two GCLKs. Fault status is
reported to the main processor via the MCAP bus.

GCLK block diagram
BACKPLANE CONNECTOR
16.384 MHz CLK FROM MATE GCLK

125 us REF FROM MATE GCLK
60 ms REF FROM MATE GCLK
6.12 s REF FROM MATE GCLK
ENCODED CLK IN
MUX
REFERENCE ENCODED CLK TO CLKX
ENCODER
ENCODED CLK TO MATE GCLK
MUX
TEST CONNECTOR 6.12 s 6.12 s REF TO BACKPLANE
6.12 s OUT REFERENCE
COUNTER
6.12 s REF TO MATE GCLK
TEST CONNECTOR MUX

60 ms 60 ms REF TO BACKPLANE
60 ms OUT REFERENCE
COUNTER
60 ms REF TO MATE GCLK
MUX
TEST CONNECTOR 125 us
125 us OUT 125 us REF TO BACKPLANE
REFERENCE
COUNTER
125 us REF TO MATE GCLK
MUX
16.384 MHz CLK TO BACKPLANE
TEST CONNECTOR
E1/T1 IN 16.384 MHz TO MATE GCLK
MUX E1/T1 CLOCK REF A
E1/T1 CLOCK REF B
TEST CONNECTOR REFERENCE
16.384 MHz OUT OSCILLATOR
REFERENCE
FAIL
DETECT
CLOCK MASTER/ MASTER/SLAVE

FAILURE SLAVE
RED LED DETECT CONTROL
GREEN LED
CLOCK CONTROL /
ALARM LOGIC OUTPUT ENABLE
RESET/DISABLE MCAP BUS A

SWITCH MCAP
INTERFACE MCAP BUS B
BSS11_Ch6_25

The Multiple Serial Interface (MSI) ISSUE 1 REVISION 2
The Multiple Serial Interface (MSI)

Purpose of MSI
The MSI drives two separate interface lines to and from the TDM bus.
MSI module
The MSI can drive two European 2.048 Mbit/s (E1) data lines.
One of the E1 lines is referred to as group A, the other E1 line is known as group B.
The E1 lines can come from either:
S Type 43 interconnect module (T43), (also known as a CIM).
S Balance-line Interconnect Module (BIM), (also known as a BIB).
The MSI can also extract the clock synchronization from the E1 line data stream.
An RS-232 maintenance port, to which a Personal Computer (PC) can be connected for
testing and debugging, is provided at the top of the BSU shelf.
Terminology
One wire pair (balanced or unbalanced) equals one E1 serial data stream.
Two E1 serial data streams (transmit and receive) equal one E1 line.
Requirements of
MSI
The MSI board is fitted in:
S Slots L7 to L17 of the BSU shelf assembly.
BTS initialization
An MSI must be located in at least one of the BSU locations below for BTS initialization
purposes:
S Six MSI slots (odd numbered 7, 9, 11, 13, 15 and 17) have been allocated to
interface to the HDSL modems.
S Two MSI slots (14 and 16) have been allocated to interface to the network via the
T43 or BIB board.
Brief description
The MSI converts signals from the E1 lines from serial format to the parallel format that
the TDM highway requires, and converts signals transmitted to the E1 lines from parallel
to serial. The MSI also provides surge protection and frame alignment.
S One 64 kbit/s channel for synchronization.
S One 64 kbit/s channel for control signalling.
S Thirty 64 kbit/s channels that can each be used as follows:
– Traffic (four 16 kbit/s compressed voice/data channels each).
– Additional control channels.
These channels can be placed in any of the 1024 channels on the TDM highway under
the control of the GPROC2.

ISSUE 1 REVISION 2 The Multiple Serial Interface (MSI)
MSI block diagram

BACKPLANE CONNECTOR
WATCHDOG RS232
TIMER DRIVERS TTY TEST PORT
MCAP BUS A
RED MCAP INTERFACE
LED
MCAP BUS B
MC6800 PROCESSOR
GREEN
LED EPROM SRAM EEPROM
RESET/
DISABLE
SWITCH CRC4 TDM TDM SWITCHBOUND HIGHWAY B
HDB3
DECODER DECODER INTERFACE
CONTROL
RECEIVED
CLOCK
EXTRACTOR
2
LEVEL IMPEDANCE
CONVERTER RECEIVE
MATCHING
E1 LINE A
(HDSL TO/FROM
LEVEL CONVERTER 2 RF HEADS)
& E1/T1/JT1 LINE IMPEDANCE
TRANSMIT

ENCODER ENCODER INTERFACE TDM OUTBOUND HIGHWAY B
MUX
EXTRACTED CLOCK REF
TDM TDM SWITCHBOUND HIGHWAY B

HDB3 CRC4
DECODER DECODER INTERFACE TDM SWITCHBOUND HIGHWAY A
RECEIVED
CLOCK
EXTRACTOR
LEVEL 2
IMPEDANCE RECEIVE
CONVERTER MATCHING
E1 LINE B
(HDSL TO/FROM
LEVEL CONVERTER 2 RF HEADS)

ENCODER ENCODER INTERFACE
BSS11_Ch6_26

The LANB Extender half size board (LANX) ISSUE 1 REVISION 2
The LANB Extender half size board (LANX)
Purpose of LANX
WARNING
The LANX:
S Connects one of the LAN interfaces of each GPROC2 in a BSU shelf to the local
shelf token ring LAN via the shelf backplane.
S Switches empty module slots or faulty GPROC2s out of the LAN.
S Sets the cage (BSU) ID.
S Performs on-board MCAP bus arbitration.
S Provides shelf active/standby redundant LAN control.
Shelf to shelf extension is via a LANX module in each shelf, interconnected with fibre
optic cabling.
The LANX supports up to eight GPROC2s on the local LAN in one BSU shelf.
Requirements of
LANX
LANX modules must be fitted in slots U19 and U20 of the BSU at all times.
A sixteen position (0 to F hex) rotary switch on the LANX module sets the BSU LAN
address (shelf ID number). The Horizonoffice uses the F hex position.
Brief description
of LANX
Refer to the block diagram at the end of this section.
Each LANX receives LAN data from another shelf via optical fibre cables and:
S Routes the LAN data to the first GPROC2.
S Receives the LAN data back from the first GPROC2.
S Routes the LAN data to the second GPROC2.
S Receives the LAN data back from the second GPROC2.
And so on until all GPROC2s in the shelf have received the LAN data.
If a GPROC2 is not present in the shelf or has failed, the LANX by-passes it and passes
the LAN data to the next GPROC2.

ISSUE 1 REVISION 2 The LANB Extender half size board (LANX)
LANX block diagram
BACKPLANE CONNECTOR
ROTARY SELECT BSS SERIAL BUS A

SERIAL
SWITCH SHELF ID INTERFACE
NUMBER BSS SERIAL BUS B
Rx DATA FIBRE OPTIC

RECEIVER BUS ARBITER
LAN LOCAL/EXTERNAL
BUS GRANT 0
MUX
LAN DATA OUT 0
BUS REQUEST 0 GPROC
SLOT 0
LAN DATA IN 0
INSERT 0
BUS GRANT 1
MUX
LAN DATA OUT 1
GPROC
LAN DATA IN 1
INSERT 1
BUS GRANT 2
MUX
LAN DATA OUT 2
POWER FAIL GPROC
DETECT &
LAN LAN DATA IN 2
LOCAL/EXTERNAL
LOGIC INSERT 2
GPROC
DC INPUT SLOTS
POWER 3, 4, 5, 6
DISTRIBUTION
BUS GRANT 7
MUX
LAN DATA OUT 7
BUS REQUEST 7 GPROC
Tx DATA FIBRE OPTIC SLOT 7
TRANSMITTER LAN DATA IN 7
INSERT 7
BSS11_Ch6_27

The Parallel Interface Extender (PIX) board ISSUE 1 REVISION 2
The Parallel Interface Extender (PIX) board
Overview of PIX
The PIX board provides:
S An Input/Output (I/O) interface for customer site equipment.
S The interface logic between the GPROC2 and external customer alarm devices
such as relays and switches.
S Eight optically isolated inputs and four relay outputs.
A block diagram of the PIX is shown opposite.
Requirements of
PIX
The PIX board can be normally be fitted in slots U16 and U17 of a BSU.

ISSUE 1 REVISION 2 The Parallel Interface Extender (PIX) board
PIX block diagram
BACKPLANE CONNECTOR
62 PIN “D”
CONNECTOR
–12 V +12 V
SENSE S1 DC to DC
SURGE OPTO– CONVERTER

EARTH

FROM
CUSTOMER SENSE S5 SURGE
EQUIPMENT OPTO–

SERIAL BUS
SENSE S7 SURGE TRANSCEIVER BSS SERIAL BUS A
OPTO–
SENSE D7 PROTECTION COUPLER BSS SERIAL BUS B

N. O. 1
N. C. 1 RELAY RELAY
COM 1 DRIVER
N. O. 2
TO N. C. 2 RELAY RELAY
CUSTOMER COM 2 DRIVER
EQUIPMENT N. O. 3
N. C. 3 RELAY RELAY
COM 3 DRIVER
N. O. 4
N. C. 4 RELAY RELAY
COM 4 DRIVER
GREEN
LED
BSS11_Ch6_28

The Battery Backup Board (BBBX) ISSUE 1 REVISION 2
The Battery Backup Board (BBBX)
Purpose of BBBX
If the main supply fails, the BBBX provides a backup supply of +5 V at 8 A.
The +5 V DRAM battery backup supply maintains power to the:
S Optical circuit on the LANX module.
S DRAM memory located on the GPROC2.
Normally, the IPSMs supply +5 V DRAM voltage to the BSU backplane. If the IPSMs fail
to deliver this due to cabinet input power failure or PSM failure, the BBBX converts an
external backup supply to a fused +5 V DRAM supply.
Requirements of
BBBX
The BBBX board is normally positioned slot U15 of the BSU but can be fitted in any
spare half size board slot.
All connections are made at the front of the module.

ISSUE 1 REVISION 2 The Battery Backup Board (BBBX)
BBBX block diagram
4 PIN ”AMP”
CONNECT OR
OUTPUT VOL TAGE

(+5 V AT 8 A)
9 PIN ”D”
CONNECT OR
INPUT VOL TAGE SURGE BRIDGE

PROTECTION DC to DC
(20 TO 75 V AT 3.2 RECTIFIER
CONVER TER
TO 0.85 A)
OVER VOL TAGE
OUTPUT GOOD ALARM OVER
INPUT GOOD SIGNALS TEMPERA TURE
BSS11_Ch6_29

The Management Interface Extender (MIX) board ISSUE 1 REVISION 2
The Management Interface Extender (MIX) board
Purpose of MIX
The MIX board interfaces between the GPROC2 and the HDSL shelf to provide a
buffered communication link, an EMU reset signal and a system clock derived from
GCLK to the modem shelf.
Requirements of
MIX
The MIX board fits normally in slot U18 of the BSU shelf assembly.
Interfaces
There are three external interfaces RS-232 (serial management data to/from EMU), TTL
(serial management data to/from GPROC2 via backplane) and G703 (system clock to
EMU). These interfaces are defined below.
RS-232
The MIX board provides an interface between the secondary serial bus TTL signals on
the backplane (from GPROC2) and the RS-232 signals on the EMU. This interface
permits the GPROC2 to manage the LTUs, update their code version if required, and
also supports a hard reset signal for the EMU. The pin allocation of the RS-232 cable is
shown Table 6-18.
Table 6-18 RS-232 pin connectors

Pin Signal Direction Description
2 RXD I Receive data
3 TXD O Transmit data
6 DSR I Data set ready
4 DTR O Data terminal ready
5 GND – Ground
9 HDSL_reset_n O EMU-830 hard reset (not RS232) level
Backplane
The connector is of the standard Teradyne 180 way staged pin type, as used on all BSU
half size boards.
The MIX board supports secondary serial buses at TTL levels from two GPROC2 slots
(L20 and L24). Only the bus that connects to the slot containing the BTP GPROC2 will
be active. The BTP GPROC2 tell MIX via the standard serial bus which of the secondary
serial buses to use.

ISSUE 1 REVISION 2 The Management Interface Extender (MIX) board
Diagram of MIX board
J2 (NOT USED)
ÄÄÄÄÄ
REF 1 (CLK)
ÄÄÄÄÄBAR CODES
BACKPLANE
REF 3 (RS-232) CONNECTOR
BSS11_Ch6_30

The Management Interface Extender (MIX) board ISSUE 1 REVISION 2
System clock
and interface
This consists of the logic function and the interface.
Logic
The MIX board provides a system 2.048 MHz clock derived from GCLK. At power-up,
the MIX card selects whichever 16.384 MHz clock is available (it defaults to A if both are
available).
If both clocks are available, the GPROC2 has the ability via the standard serial bus to
force the selection of the 16.384 MHz clock on the MIX, however the MIX board
automatically swaps the clock source if the selected clock fails.
A signal is provided via the secondary serial bus to GPROC2 identifying the current 16
MHz backplane clock in use on the MIX board.
Interface
The MIX is compliant with G.703, paragraph 10.
The interface is capable of driving a 5 m 75 ohm cable.
Functional
description
The MIX provides two secondary serial buses for communication between the site control
base transceiver processor (BTP) GPROC2 and the HDSL modem shelf. The MIX is
informed by the BTP GPROC2 via the standard serial bus controller which of the
secondary serial buses to use. This functional area is also responsible for informing
GPROC2 on the board ID, revision level and which backplane clock is currently being
used.
The actual multiplexing/demultiplexing (MUX/deMUX) is performed by the secondary
serial bus MUX and I/O buffers, and the process for selecting the backplane clock to be
used, is performed by the system clock. The backplane clock is selected by GPROC2
via the standard serial bus, but block B also monitors that clock and will auto-swap if it
fails.
The selected backplane clock is divided to 2.048 MHz and routed to the interface section.
The interface section comprises of interface transceivers/drivers. The system clock

interface converts the TTL level 2.048MHz clock into a signal compliant with G.703. The
remaining components of are level converters and connectors.

ISSUE 1 REVISION 2 The Management Interface Extender (MIX) board
Block diagram of a MIX module
STANDARD RS–232 POR T

SERIAL BUS INTERF ACE
DSR
SER.DA T–A TxD
B SER.DA T–B STANDARD RxD
A SER.SELA SERIAL BUS
C CONTROLLER DTR
K
SLOT ID RESET
P
L
A CONTROL AND
N STATUS
E
SECONDAR Y
RESET
SERIAL BUS
C
(FROM GPROC2
O
SLOT L20)
N
N SECONDARY
E SERIAL BUS
C SECONDAR Y
MUX AND I/O
T SERIAL BUS
(FROM GPROC2 BUFFERS
O
R SLOT L24) SYSTEM
CLOCK
INTERF ACE
CLK16.A
CLK16.B SYSTEM CLOCK 2.048 MHz
RESET
BSS11_Ch6_31

The Line Terminal Unit (LTU) ISSUE 1 REVISION 2
The Line Terminal Unit (LTU)

Purpose of LTU
The LTU is an European Telecommunication Standard Institute (ETSI) compliant high
HDSL board.
The LTU drives HDSL data over two twisted pair cables to communicate with two RF
heads. Data is transmitted at 1168 kbit/s to each RF head.
Requirements of
LTU
The LTU board fits into:
S Slots 1 to 12.
Controls and
indicators
Table 6-19 outlines the controls and indicators on the front panel of the LTU-830.
Table 6-19 Controls and indicators
Item Parameter Function
Mode
HDSL loop 1 SYNC LED Steady green HDSL loop is ready to transmit
HDSL loop 2 SYNC LED and receive data.
Blinking green HDSL loop acquisition is in
progress.
HDSL loop 1 ALM LED Steady red Loss of sync word (LOSW).
HDSL loop 2 ALM LED
Pulsing red Pulses for every ES received.
I/F ALM LED Blinking red Loss of frame alignment or Alarm

Indication Signal (AIS) received at
G.703 port.
Steady red Loss of Signal at G.703 port.
NOTE
The PROT SW LED shown above is not used.
The LOC and REM loop back buttons shown above cause the LTU to enter a
diagnostic loopback mode. The LTU remains in this mode for twenty minutes
unless the button is again depressed terminating the diagnostic mode.
This function is not supported by Horizonoffice. Consequently neither of these

buttons should be pressed as the communication to the RF head would be
interrupted during loopback.
V.24 (D9F) connector

The connector is not used in Horizonoffice.

ISSUE 1 REVISION 2 The Line Terminal Unit (LTU)
LTU board
PAIRGAIN
SYNC
1
ALM
HDSL LEDs
SYNC
2
ALM
ALM I/F
PROT
SW
LOC
LOOPBACK LEDs
REM
V24 (R2-232) CONNECTOR V24
BAR CODE LABEL

BAR CODE LABEL
WARRANTY CONTROL
NUMBER LABEL
MOTOROLA
LTU
BSS11_Ch6_32

The Exchange office Management Unit (EMU) ISSUE 1 REVISION 2
The Exchange office Management Unit (EMU)
Purpose of EMU
The EMU-830 is an Exchange office Management Unit (EMU). The EMU-830 provides
fault, alarm, configuration and performance management of HDSL circuits deployed.
The EMU is managed by a GPROC2.
Requirements of
EMU
The EMU-830 board fits into the extreme right slot of the HDSL shelf (labelled EMU).
S The extreme right slot of the HDSL shelf (labelled EMU).
Every HDSL rack requires one EMU-830 board.
Controls and
indicators
Table 6-20 Controls and indicators
Item Parameter Function
Mode
POWER LED Green Indicates power to the EMU-80.
FAIL LED Red Indicates system failure*
EXT COMM LED Green Indicates when data is being
transmitted to a managment
station.
CRITICAL ALM LED Red Function not used.
MAJOR ALM LED Yellow Function not used.
MINOR ALM LED Yellow Function not used.
ACO LED Green Function not used.
ACO switch Function not used.
RESET switch Resets the EMU-830 hardware.
* It is normal for the FAIL LED to illuminate briefly when power is
initially applied to the EMU-830.
Alarms
The alarms are managed by software and the LEDs are for indication only.
The EMU-830 constantly monitors each of the LTU boards for alarm conditions.

ISSUE 1 REVISION 2 The Exchange office Management Unit (EMU)
EMU board
PAIRGAIN
POWER
FAIL SYSTEM – STATUS LEDs
EXT COMM
CRITICAL
MAJOR ALM ALM ALARMs – LEDs
MINOR
ACO ALARM CUTOFF LED AND

RESET SWITCH SWITCH
RESET
V24 (R2-232) CONNECTOR
BAR CODE LABELS

V24
WARRANTY CONTROL
NUMBER LABEL
EMU-830
BSS11_Ch6_33

RF head ISSUE 1 REVISION 2
RF head
Overview of RF
head
This chapter describes the physical and functional operation of the RF head. All
descriptions are presented with block diagrams.
RF features
Each RF head provides a single carrier and is a single Field Replaceable Unit (FRU).
RF head
The key technical features are:
S Single carrier, Class P1 BTS.
S Integrated RF, control, equalisation, channel coding, PSU and communications.
S HDSL interface to the controller.
S Integrated power supply.
S Fixed internal antenna.
S Optional battery back up.
External
interfaces
The unit has ten external interfaces:
S AC power input.
S HDSL communications port.
S Multi head sync input.
S Multi head sync output.
S External alarm connections.
S Battery Pack port.
S Duplexed antenna connector (factory connected to internal antenna, optionally
connect to external antenna).
S DC power input (AC/DC output is factory fitted to this port).
S Field diagnostic ‘Test Port’.
S RF Transceiver ‘Status’ LED
Multicarrier head
mode
The Horizonoffice allows up to four RF heads to operate in a single logical cell. This is
accomplished by connecting the RF heads together, using the sync link cables provided.
The sync link cable passes a timing reference from the master RF head to the slave RF
heads.
The RF heads are set to operate in multicarrier mode by configuring the database.
For further details refer to the installation section of this Service Manual (Category 423).

ISSUE 1 REVISION 2 RF head
View of RF head, with access and appearance covers

fitted
BSS11_Ch6_34

Description of RF
head
The description is subdivided into:
S Physical.
S Power.
S RF transceiver board.
Physical
description of RF
head
The RF head is designed for wall and pillar mounting. The RF head is provided with two
moulded access covers and an aesthetic cover panel which should be fitted once the
head is secured in place. Once the two moulded access covers are removed, there is
sufficient access for installation and maintenance.
Pillar mounting is facilitated by the use of an additional bracket.
All input and output interconnections are via ‘breakout’ on the top/bottom of the access
cover or via the rear when mounted to a hollow wall.
The diagram opposite shows the location of the various modules making up the RF head.
The constituent parts are detailed below.
S The RF transceiver board which provides all RF functions (RX,TX,SYNTH and
loopback) and digital processing/control (capable of running CP,EQ,CC and FEP).
The RF transceiver board is frequency sensitive, being available for a GSM900
variant, or a DCS1800 variant.
S The DC-DC converter board which produces the primary power rails from a single
input voltage supplied by the AC-DC converter or battery. Additionally it has
control circuits to switch to battery back-up and provides charging power. It has
the connectors and interface circuitry for the HDSL input fitted and acts as a
carrier for the HDSL modem card.
S An AC-DC converter that can convert a wide range AC voltage inputs to the
DC-DC converter primary input voltage.
S An HDSL modem controller (mounted on the DC-DC converter).
S An internal antenna connected to the duplexed RF port. The antenna is frequency
sensitive, configured for GSM900 or DCS1800.
S An optional back-up battery.
S A metal chassis which provides an EMC enclosure within which the DC-DC, RF
transceiver and HDSL boards are mounted, and mounting points for the internal
antenna .
S A two piece plastic housing, provides mounting for the metal EMC enclosure,
AC-DC converter, battery, cable ducting and unit mounting points (non field
maintainable).
S An aesthetic cover, made up of three pieces fitting over the complete unit.

Diagram of RF head components
CLIP-ON COVER
CLIP-ON COVER
TEST PORT REMOVED
CONNECTOR (PL3)
SYNC IN
SYNC OUT
HDSL PORT
ALARMS
PORT (J5)
DC INPUT (PL1)
LED INDICATOR
BATTERY
AC/DC CONVERTER CONNECTOR (PL2)
WITHIN CLIP-ON COVER ANTENNA IN
ANTENNA OUT
MCX TO MCX CABLE

FRONT COVER AC/DC CONVERTER AND CONNECTORS
LOCATION
(OR OPTIONAL
(FACTORY FITTED TO
BATTERY PACK) ANTENNA PORTS FOR
INTERNAL AERIAL)
DC CABLE
PATH
BATTERY PACK
BSS11_Ch6_35

Power system
The RF head power system comprises the AC/DC unit, the DC/DC and HDSL Board and
when fitted, a battery pack.
Diagram of RF head power system

Opposite is a block diagram of the overall RF Head power system, showing power rails
and signal link paths.
The ac/dc is a Class II, 40 W, +25 V dc output unit, with a wide ac mains input range.
The nominal running current, from the ac/dc is 1.1 amps, with an additional 0.5 amps
allocated for when the battery pack is fitted and in its maximum charging mode. The
ac/dc features output power limit, output over-voltage and thermal shutdown functions.
The DC/DC and HDSL board generates the supply voltages for the RF transceiver board.
The typical loading on the DC/DC and HDSL board is shown in Table 6-21.
Table 6-21 Output voltage and system load

Output voltage Typical Current Typical current
GSM900 DCS1800
+ 6.5 V dc 1A 1.1 A
– 6.5 V dc 45 mA 45 mA
+ 5 V dc 650 mA 650 mA
+ 3.3 V dc 1.5 A 1.5 A
One half of the board carries the dc/dc converter section, the other half carries the HDSL
interface, HDSL modem and RF head synchronism circuitry.

RF head unit functional blocks
RF HEAD UNIT
+ 6.5 V dc AND – 6.5 V dc

DC/DC CONVERTERS Tx/Rx
+ 5 V dc PORT
+ 3.3 V dc
CONTROL RF TRANSCEIVER
AC / DC AND BOARD
ALARMS
CONVERTER
Input_Fail
BATTERY PACK LVD AND HDSL MODEM
PSS O/T INTERFACE
(WITH INTERNAL FUSE)
AC MAINS
POWER RAILS SIGNAL LINKS
BSS11_Ch6_36

RF transceiver
board
The RF transceiver board contains a number of functional parts, as follows:
S Duplexer, this provides filtering and combination of RX/TX signals.
S Loopback (this provides a self test of RF functionality).
S Transmitter (this provides a baseband modulation, up conversion and RF
amplification section).
S Receiver (this provides amplification and RF down conversion to I/Q baseband
digitization).
S Synthesizer (this provides the source of down/up conversion frequencies for
RX/TX).
S DSP section (this provides call processing, equalization, channel coding, radio
control, modem link support and alarm processing functions).
Description of RF transceiver board

The RF head is a single carrier which supports the operation of GSM. The frequency
band of operation for GSM is factory preset.
The frequency accuracy of the 13 MHz reference synthesizer locks the HDSL modem to
ensure that long term transmitter frequency accuracy is better than 0.05 ppm.
NOTE
Long term frequency accuracy is dependent on the CU reference oscillator.
The RF head is fitted with a single internal duplexed Rx/Tx antenna.
NOTE
The internal antenna is not accessible.
The internal antenna is connected to the RF transceiver board via a short MCX, male, to
MCX cable, male. The RF transceiver MCX port is also used as the test reference point.
The RF head is a one (1) carrier, non-redundant, and non-expandable unit.
The RF head does not require field calibration, nor the use of a bay level offset. The
power level output can only be reduced in steps of 2 dB, through transmitter power
control, set via the system data.
Alarms are reported to the DSP section. The RF head provides a number of alarm
functions related to the ‘RF’, ‘Digital’ and ‘Power System’ sections of the unit. The
‘Power System’ alarms are as follows :
S ‘Input Low‘ alarm : indicates when the ac mains has been lost or the failure of the
ac/dc unit.
S ‘Low Voltage Disconnect Imminent’ : indicates when the battery pack has almost
reached its ‘disconnect point’, at which the RF head will power down.
S ‘PSU Over Temperature’ : indicates that the power system has detected an
‘overtemperature’ condition. If this continues, the power system will initiate a
power down.

RF transceiver block diagram
ANTENNA INTERFACE
RF TRANSCEIVER BOARD
RF FUNCTIONS
DUPLEXER
LOOPBACK TEMP
DETECTOR
TRANSMITTER SYNTHESIZER RECEIVER
TEST
DSP SECTION CONNECTOR
BSS11_Ch6_37

S ‘External Alarm’ : this is an externally accessible ‘input’ alarm, designed to be

connected to ‘zero-volt’ contacts. This alarm is ‘flagged’ when the input circuit
detects a ‘closed or short-circuit’ across its input terminals. This alarm is not
designated for “safety critical” use.
WARNING
The ‘External Alarm’ input, available via the ‘alarms connector’, can only be
used with ‘volt-free’ contacts. For example, by using the Normally-Open
(N/O) or Normally-Closed (N/C) contacts of a relay. This is to ensure there
are no 0V dc or Ground loops induced in the Horizonoffice RF Head or the
equipment providing the alarm source.
The alarms which are reported to the digital (DSP) section are in turn reported to higher
levels.
The RF head is equipped with a temperature detector that provides both alarm
generation and thermal compensation.
RF Loopback
The RF head can implement a loopback test function, in which the transmitter output
signal is converted into the receiver Intermediate Frequency (IF), via a switchable
receiver Voltage Controlled Oscillator (VCO).
The loopback function is controlled from the DSP section and includes a register to select
the mode of operation. There are three modes of operation, these are Normal (i.e.
Traffic Channel (TCH) operation), Loopback and Listen.
NOTE
Loopback tests all active RF section elements but does not test the RF
filtering.
When the RF loopback is active, no more than the preceding two timeslots and the
following two timeslots are muted to allow the synthesizer to retune,
The sensitivity of the receiver and power output are given in the Technical Description,
Category 323 Specifications, of this Service Manual.


Connector
pin-out details
This section outlines the pin-out details for the RF head. The diagram opposite shows
the RF head ports. Table 6-22 to Table 6-24 and the diagrams on page 99 and 101
detail the pin-out connections and their respective connectors.
Main source
supply input
Table 6-22 illustrates the main source supply input PL1 (from the ac/dc converter) pin-out
details. This is a six way right-angle plug with polarization and retention.
Table 6-22 Main source supply input pin-out connections

Pin Function
1 + 25 V dc
2 0 V return
3 Functional earth
4 Spare
5 + 25 V dc
6 0 V return
Battery input /
output
Table 6-23 illustrates the battery input / output connector PL2 pin-outs (from the battery
pack). This is an eight way plug, with polarization and retention.
Table 6-23 Battery input / output pin-out connections

Pin Function
1 + 25 V dc nominal feed (switched)
2 0 V return
3 Battery power request
4 Alarm 1 (battery present)
5 Alarm 2 (battery charging)
6 Alarm 3 (battery good)
7 Alarm 4 (low voltage disconnect imminent)
8 + 5 V dc ‘logic’ enable feed (max 50 mA)

PL1 and 2 plug pin-outs
PIN 4
PIN 6 PIN 2
(VIEW ONTO MATING END)
PIN 5 PIN 1
PIN 3
PCB RETENTS
PIN 6 PIN 4
PIN 8
PIN 2
PIN 1
PIN 7
PIN 5 PIN 3
PCB RETENTS BSS11_Ch6_38

External alarm
connector on RF
PCB
The external alarm connector (J5) on the RF digital Printed Circuit Board (PCB) is a four
way plug with polarization and retention. Table 6-24 lists the pin-out functions.
Table 6-24 RF transceiver external alarm pin-out functions

Pin Function
1 Shield GND
2 Ext alarm 1
3 GND (signal return)
4 Buffer clock output
HDSL connector
Table 6-25 illustrates the HDSLport (J1) connector pin-outs. J1 is a RJ11 socket with six
contacts. The mating half uses a 6/4 RJ11 plug, where only the center four terminal ways
are loaded. See Making the HDSL cable, and the Installation and Configuration section.
Table 6-25 HDSL Port pin-out connections

Pin Function
1&2 none
3 EXT_TIP1
4 EXT_RING1
5&6 none

Connector pin-outs
PIN 4
PIN 2
PIN 1
PIN 3
BSS11_Ch6_39
J1 plug pin-outs
PCB
Pin1 BSS11_Ch6_40

Multi head Sync

Input connector
Table 6-26 illustrates the Multi head connector (J6) pin-outs. This is a RJ45 socket with
eight contaacts.
Table 6-26 Multi head Sync Input pin-out connections

Pin Function
1 clk_sync_rx_b
2 clk_sync_rx_a
3 to 8 none
Multi head Sync

Output
connector
Table 6-28 illustrates the Multi head connector (J5) pin-outs. This is a RJ45 socket with
eight contacts.
Table 6-27 Multi head Sync Output pin-out connections

Pin Function
1 clk_sync_rx_a
2 clk_sync_rx_b
3 to 8 none

J6 and J5 plug pin-outs
Pin 1
PCB
Pin 1
PCB BSS11_Ch6_41


Chapter 7
Equipment Appreciation

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 7
Equipment Appreciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BSS Equipment Appreciation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
BSC/XCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
The Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4

ISSUE 1 REVISION 2

Chapter Objectives
At the end of this chapter the student should be able to:
S Participate in a visit/demonstration of the various BSS equipment.

BSS Equipment Appreciation ISSUE 1 REVISION 2
BSS Equipment Appreciation
Introduction
This section of BSS11 will allow students to gain a physical appreciation of the varied
BSS equipments studied throughout the course.
BSC/XCDR
All students are to participate in a visit to an equipment room, led by their course
instructor.
The equipments to be observed are BSSC2 cabinets and associated hardware modules
internal to the cabinet:
GPROC.
GCLK.
TSW/KSW.
MSI.
KSWX.
GCLKX.
LANX.
BBBX.
PIX.
BTC.
In addition to the slot in modules other areas of a cabinet that can be viewed are the
DAB, PSMs, PDU and the BSU and RXU shelves.
Students are to use the time to consolidate their theory knowledge on the BSSC2
equipment.

ISSUE 1 REVISION 2 BSS Equipment Appreciation
Internal view of the BSSC2 cabinet
POWER DISTRIBUTION UNIT

(PDU)
HALF-SIZE DIGITAL
BOARD SHELF
FULL-SIZE DIGITAL
BOARD SHELF FANS
POWER SUPPLY
MODULES
HALF-SIZE DIGITAL
BOARD SHELF
FULL-SIZE DIGITAL
BOARD SHELF
POWER SUPPLY
MODULES
EXTERIOR DOORS REMOVED TO SHOW DETAIL
BSS11_Ch7_01

The Base Transceiver Station (BTS) ISSUE 1 REVISION 2
The Base Transceiver Station (BTS)

All students are to participate in a visit to an equipment room, led by their course
instructor.
Equipments to be observed are the BTS equipments in the Horizon family:
Horizonmacro Indoor.
Horizonmacro Outdoor.
Horizonmicro.
Horizonoffice.
Students are to use the time to consolidate their theory knowledge on the equipments.

ISSUE 1 REVISION 2 The Base Transceiver Station (BTS)
External view of a closed Horizonmacro indoor cabinet

with hood cover
BSS11_Ch7_02
Horizonmacro cabinet with door open and hood removed.
BSS11_Ch7_03


External view of a standard Horizonmacro outdoor cabinet
BSS11_Ch7_04


Horizonmicro
BSS11_Ch7_05


General view of the Horizonoffice equipment
RF HEAD
CONTROLLER UNIT
BSS11_Ch7_
06


Chapter 8
BSS Software

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 8
BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BSS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Executive and Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
BSS Executive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Operating System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Process Isolation and Memory Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Flexible Interprocess Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Operations and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Functional Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
OMC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Man Machine Interface (MMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Configuration Management (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Configuration Management Database Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
Device and Function Dependancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–14
Performance Management (PM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–16
Fault Management (FM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18
Central Authority (CA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
Central Authority Device States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Fault Detection and Handling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24
BSS Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Fault reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Alarm Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Alarm Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Message formats: Standard Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Alarm Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
Initialization Process (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Initialization in ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
Initialization in RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38

ISSUE 1 REVISION 2
Call Processing at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40

Message Transfer Part L2 (MTP_L2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Message Transfer Part L3/SCCP Pre–processor . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
Call Processing at the BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Cell Broadcast Scheduler (CBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
Allocation Manager (AM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–44
Radio Subsystem (RSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
RSS Layer 1 Protocol (Layer 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
RSS Configuration and Fault Management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . 8–48
Handover Detection and Power Control (HDPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–50
Handover Decision Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–52
Motorola Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–54
Call Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–56
Voice Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58
Intra BSS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–60

ISSUE 1 REVISION 2 BSS Software
BSS Software
Objectives
S Identify the major sections of the BSS software.
– BSS executive/operating
– BSS operations and maintenance
– Radio Subsystem (RSS)
– Call Processing (CP)
S Identify the Motorola software configuration.
S State the basic GSM call and handover sequences.

Software architecture ISSUE 1 REVISION 2
Software architecture
Overview
The BSS software is composed of many processes, which carry out specific functions
within the BSS. These processes will be distributed among the GPROCs at the site
according to the configuration given in the database.
At initialisation the different processes are downloaded to the site as code objects, this is
part of the initialisation process permanently stored in the boot ROM. A code object is a
binary file that can be built into an application process by the operating system, which
runs on the GPROC boards. Each GPROC will be loaded with a complete set of the
code objects for the type of site (i.e. RXCDR, BSC or BTS). However not all the objects
will be started as applications. Which objects are started will depend on what functions
are being supported by each GPROC. For instance a BSP (master GPROC) will run
different processes to a Link Control Function (LCF).
In addition to the code objects required by the GPROCs there are code objects
downloaded for the peripheral devices (KSW, MSI, XCDR and GDP). These devices will
receive their code from a GPROC via the MCAP bus at initialisation or whenever that
device is brought into service.
The operating system is called the Executive and is responsible for running the
application processes, passing of messages between application processes, the
hardware interfaces to the application processes and memory management. This
architecture means that in a lot of cases application processes are not aware of the
physical location of the other processes they communicate with and because of this
functions can move without any adverse affect on other processes (e.g. a LCF could be
moved from one GPROC to another at a BSC without adversely affecting processes
communicating with that function).

ISSUE 1 REVISION 2 Software architecture
BSS Software
Code object files
Code object files

can create
a system process
All GPROCs at the same site downloaded with all

code object files BSS11_Ch8_01

Software architecture ISSUE 1 REVISION 2
The BSS software can be split into five main functional areas. Each functional area is
made up of a number of application processes.
The five main functional areas are:
1. Executive and protocol
2. Fault Management (FM)
3. Operations and maintenance
4. Call Processing (CP)
5. Radio Subsystem (RSS) (only found at the BTS)
Data Link Service Process (DLSP)

Interface (INT)
Man Machine Interface (MMI)
Executive and
Protocol
The Executive is the operating system of the GPROC, however it is made up of several
processes to provide different functions for the application processes.
For example the MCAP Data Link Service Process (DLSP) is an executive process that
provides the application processes with an interface to the MCAP bus for communication
with the peripheral cards.
The EXEC DLSP provides a similar function for communications between GPROCs via
the LAN or across a Radio Signal Link (RSL) (i.e. a message sent to or from the BSC
and BTS).
The TTY DLSP provides an interface to the serial bus for the local maintenance terminal
and for remote logins from the OMC.
These are a small selection of the processes that make up the Executive function.

ISSUE 1 REVISION 2 Software architecture
BSS SYSTEM
SOF TWARE
EXECUTIVE/ OPERATIONS CALL

FAULT RADIO
OPERATING AND PROCESSING
MANAGEMENT SUBSYSTEM
SYSTEM MAINTENANCE
MCAP DLSP CENTRAL CONFIGURATION CELL RESOURCE LAYER 1 INT

AUTHORITY MANAGEMENT MANAGER
TTY DLSP LAYER 2 INT
FAULT MMI SCCP STATE
EXEC DLSP TRANSLATION MACHINE HAND OVER
PROCESS AGENT AND POWER
RADIO CONTROL
SWITCH CENTRAL RESOURCE
MANAGER STATISTICS STATE MACHINE ABIS INT
PROCESS
CONFIGURATION
AND FAULT
MANAGEMENT
Note: Not all processes are shown here.
BSS11_Ch8_02

BSS Executive ISSUE 1 REVISION 2
BSS Executive
Operating
System Structure
The BSS Executive software running on each of the Generic Processor (GPROC) boards
creates the operating system for the application processes to run on. As part of this it
uses process isolation and memory protection with flexible interprocess communication.
Process Isolation
and Memory
Protection
The Executive utilises a memory management unit to isolate the memory used by each
application process from every other application process. It is therefore impossible for
one process to write into the memory area of another process.
The memory management unit gives each application process an area of memory
dedicated to that process. Allocation of memory is dynamic and these memory areas are
created and destroyed as required by the software.
A supervisor is created at the base of each of the memory areas allocated to the
application processes. The supervisor contains functions that allow the application
process to talk with the Executive and so pass messages to other processes via the
Executive. All communication to and from the application process must go through the
supervisor.
Flexible
Interprocess
Communication
The Executive supports a flexible message routing system for passing messages
between application processes and provides five modes of addressing.
S Physical
S Logical
S Active subsystem
S Active cage
S Active link
The differences in these modes of addressing are beyond the scope of this course,
however the different modes give the routing mechanism flexibility.
In order to support each mode of addressing the Executive requires a set of routing
tables, which contain information on where to route messages for each process in the
BSS. These tables are created and updated by the central authority and the router
process at initialisation and whenever changes are made to the configuration of the BSS.

ISSUE 1 REVISION 2 BSS Executive
BSS Operating Systems Overview
CA
APPLICATION
ROUTER
PROCESS
SUPERVISOR
ROUTER EXEC
TABLES ROUTER
EXECUTIVE
CA: Central Authority BSS11_CH8_03

Operations and Maintenance ISSUE 1 REVISION 2
Operations and Maintenance
Functional
Areas
Operations and maintenance consists of the following functional areas:
1. OMC interface
2. Man Machine Interface (MMI)
3. Configuration Management (CM)
4. Performance Management (PM)
OMC Interface
The Operations and Maintenance Link (OML) provides the connection between the
OMC-R and the BSC and supports communications for the four main functions of the
OMC, which are:
Download of code Download of the code objects and the database object
Upload of code Upload of statistics, database and code objects
Event reporting Reporting events and alarm information
Remote login
and configuration Access to the site MMI for diagnostics
The four main functions relate to unique X.25 addresses at the OMC and are routed to
different functional areas within the OMC. Usually there will be two X.25 addresses for
download, two for event reporting, one for upload and one for remote login.
The RXCDR or BSC have only one X.25 address and so all communications to and from
the OMC go through the X.25 packet link protocol and the agent process.
The X.25 PLP deals with the layer 3 processing of the X.25 packets and passes data to
and from the agent. The agent is responsible for routing the data to and from the correct
processes within the BSS. It can be thought of as a funnel through which all
communications with the OMC are passed.

ISSUE 1 REVISION 2 Operations and Maintenance
Operations and Maintenance – OMC Interface
S Switched virtual circuits support:
- Alarms/events reporting
- Remote Login
- Downloads (code loads/configuration

changes)
- Uploads (database, statistics)
S Machine (OMC) Ć to Ć Machine (BSC)
S X25 - 64 kbit/s
BSS11_Ch8_04

Man Machine Interface (MMI) ISSUE 1 REVISION 2
Man Machine Interface (MMI)
Overview
The MMI process provides an interface between the human operator and the software
applications to enter commands for controlling devices, displaying information and
configuring the system. The MMI can receive commands from the local maintenance
terminal or via a remote login from the OMC. The MMI process checks each command
for syntax before forwarding to the relevant processes for processing.
The MMI process provides three levels of access by the operator for security.
S Level 1 Monitor commands only
S Level 2 All MMI commands supported
S Level 3 Motorola engineers only. (Provides access to restricted
command library for specialist diagnostics)
For descriptions of all the MMI commands refer to the BSS Command Reference Manual
68P02901W23 in the Customer Documentation Set.

ISSUE 1 REVISION 2 Man Machine Interface (MMI)
Operations and Maintenance
MMI is available at:

S OMCR
S All BSS sites
Remote log in available:
S BSC to any BTS site
S From one MMI process to another at the same site
S From BTS to controlling BSC
MMI process interfaces with TTY DLSP.
MMI process interfaces with Serial DLSP at MĆCell

BTS(s).
BSS11_Ch8_05

Configuration Management (CM) ISSUE 1 REVISION 2
Configuration Management (CM)
Overview
The CM software is responsible for maintaining and updating the configuration
management database at the BSC. This database holds all the configuration information
for the BSC and all the BTS sites under its control. The Remote Transcoder (RXCDR) is
considered as a separate network entity and has its own configuration database. The
database is downloaded as an object file and contains site parameters such as carrier
frequencies, site configuration, handover thresholds, device functionality and timing
information.
At the BSC the database is copied across all active GPROCs and all processes have
access to the database. Similarly, at the BTS all processes can read the database.
However only at the BSC may changes be made and only by the master GPROC which
has write access as well as read.
If there are any changes to be made to the database, the new information is written into
the master database via the CM process. Once the changes have been made the CM
and Central Authority (CA) check that the changes are valid before broadcasting the
changes to all other GPROCs. If the changes are invalid then they are deleted from the
master copy.
If the database changes are required by one or more BTS sites then the master CM
process will forward the changes to the CM master at each site via the RSL. Database
level numbers are used to track changes and provide control. Once a database has
been changed, the changes will be reflected at the OMC terminals, however, it should be
uploaded to the OMC in order to update the database object held there. If the database
object is not uploaded and the site was reset the OMC would download the old copy and
the changes will be lost.

ISSUE 1 REVISION 2 Configuration Management (CM)
Configuration Management Overview
Read only
All Other Processes
CM
DATABASE
CM Process
Read/Write
BSC
GPROC GPROC GPROC
Process A Process Y
Process C
Process B Process Z
slave CM process slave CM process slave CM process
Database Database Database

Copy Copy Copy
LAN
MASTER CM
PROCESS
Master
Database
GPROC
BSS11_Ch8_06

Configuration Management Database Dependencies ISSUE 1 REVISION 2
Configuration Management Database Dependencies
Device and
Function
Dependancies
The following chart shows device and function dependencies. Due to system
requirements some devices and functions can only be equipped after other specific
devices have been equipped. For example, before a Message Transfer Link (MTL) can
be equipped there must be a Multiple Serial Interface (MSI) board equipped in the
database to take the MTL device.
Database Build Example:
EQUIP SITE
EQUIP CABINET
EQUIP CAGE
CHANGE ELEMENT (SITE CONFIGURATION)
EQUIP DEVICES
CHANGE ELEMENT (TIMERS)
ADD CIRCUITS
KSW CONFIGURATION

ISSUE 1 REVISION 2 Configuration Management Database Dependencies
Device and Function Dependence – BSC
BSC
SITE
CABINET
CAGE
EAS GCLK BSP GPROC CSFP KSW MSI
LCF OMF XBL MTL OML CBL
BSS11_Ch8_07

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

ISSUE 1 REVISION 2 Performance Management (PM)
Performance Management
OMCR
X25
OMCR
BSC
AGENT
COUP
CENTRAL STATISTICS
PROCESS (CSP)
BTS
Remote BTS Remote BTS Remote BTS
SSP SSP SSP
DSF DSF DSF DSF DSF DSF
BSS11_Ch8_08

Fault Management (FM) ISSUE 1 REVISION 2
Fault Management (FM)
Overview
The FM system can be split into two main areas, the fault detection, alarm handling and
reporting and the Central Authority (CA), although the CA is also involved in fault
handling.
S Fault detection and handling
S Central Authority
The FM software is designed to operate on a site basis and it has responsibility for
maintaining the site integrity in response to any fault/alarm indications that may occur
with the hardware or the software and operator initiated configuration/state changes.
The fault detection and handling system is tasked with detecting any alarms and deciding
on any hardware/software re-configurations required.
The CA, under direction of the fault detection and handling system is then responsible for
carrying out reconfigurations and state changes. This may include, taking hardware out
of service and bringing in other hardware or the creation/deletion of software processes.

ISSUE 1 REVISION 2 Fault Management (FM)
Fault Management
Fault Detection Central Authority

and Handling System
Hardware/Software reconfigurations
on per site/LAN basis
BSS11_Ch8_09

Central Authority (CA) ISSUE 1 REVISION 2
Central Authority (CA)
Overview
At site initialization the CA is one of the first processes created by the operating system.
Its first task is to query the configuration database to obtain site configuration and device
equipage. The CA is then responsible for creating all the necessary software processes
on the GPROCs as well as downloading and bringing “into service” all the peripheral
boards and devices. On completion of site initialization, the CA works as an independent
process and maintains a dynamic database to keep track of all the device function and
software process states.
The CA supervises all state changes at the site although this can be in response to MMI
commands issued from the local maintenance terminal, an OMC remote login or initiated
by the fault detection and handling processes in response to a fault/alarm condition. In
all cases the CA will update the dynamic database to show the new state and this will
also be reported to the OMC as an alarm/event.
Configuration changes may affect the routing tables used by the operating system
throughout the site or possibly the BSS. In these cases the CA will initiate an update of
the routing tables by the various routing processes in the site or BSS. This allows the
software to reconfigure dynamically to any changes made.
At the BSC and RXCDR the CA is also involved along with the fault handling processes
with the selection of the reference clock source for the GCLK.

ISSUE 1 REVISION 2 Central Authority (CA)
Central Authority Functions
A) Site Initialization
1) Queries for database for site

configuration and equipage
2) Downloading software to the hardware
3) Create software on GPROCS
4) Creating routing tables
5) Creating state tables
B) Initiate and Direct Configuration Changes
1) Hardware
2) Software
3) Updating router
4) Updating state tables

BSS11_Ch8_10

Central Authority Device States ISSUE 1 REVISION 2
Central Authority Device States
Overview
Each device in the system has a device state that is reported to the Central Authority
(CA) and consists of two parts:
C. Administrative (lock, unlock, not equipped)
D. Operational (enabled, disabled, shutting down, busy)
The administrative part is generally under the control of the operator by using MMI
commands at the OMC or LMT. The operational states indicate the state from the
viewpoint of the software.
It is a combination of these two conditions which will determine if a device can/cannot be
used/operated within the system.
The flowchart gives an idea of how the device states are used in the system.
Not equipped The device may be physically in the system but has not
been entered into the configuration database and
therefore cannot be used by the software.
Locked enabled The device is available for use but has been made
unusable by the system operator using the lock
command from the MMI. If it was intended to replace a
board such as an MSI this should be the state before
physically removing it from the cage.
Unlocked enabled The device is ready for use but at this time is not
performing any function. It can be thought of as being in
standby.
Unlocked busy The device is in use and operating correctly.
Busy shutting down Operator has decided to take the device out of service in
a controlled way. The device will continue with the tasks
that it has active but will not take on any new tasks.
When all the active tasks have been completely the
device will be idle.
Unlocked disabled The device has been taken out of service by the fault
management processes possibly in response to an
alarm condition on the device or an associated device.
Locked disabled The device is taken out of service by the fault
management processes and has been locked by the
operator, possibly in preparation for replacement.

ISSUE 1 REVISION 2 Central Authority Device States
Device States Flow Chart
NOT EQUIPPED
LOCKED ENABLED
UNLOCKED ENABLED
UNLOCKED BUSY
FAULT OCCURS BUSY SHUTTING DOWN
UNLOCKED DISABLE LOCKED ENABLED
FAULT OCCURS
LOCKED DISABLED
BSS11_Ch8_11

Fault Detection and Handling System ISSUE 1 REVISION 2
Fault Detection and Handling System
Introduction
The fault detection and handling system is based around three processes
1. Fault Collection Process (FCP)
The FCP exists on every GPROC in a site. It collects alarm reports from all processes
on the GPROC where it is active and also any other devices that the GPROC is
associated with. For example the peripheral boards will raise alarms to the GPROC
controlling the MCAP bus. FCP will acknowledge receipt of each alarm to the alarmed
process/device and generates an alarm message, which it sends on to the Fault
Translation Process.
2. Fault Translation Process (FTP)
The FTP exists only on the site master. FCPs throughout the site send alarm information
to FTP whose task is to diagnose the problem and decide the action to take in each
case. FTP holds a table of fault scenarios and the action to be taken in each case. Once
a course of action has been decided FTP will request the CA to carry out the required
state change. For example, reset the alarmed device. In addition FTP will send the
alarm message to the OMC. FTP keeps a record of all active alarm conditions in a table
called the active alarms list. The active alarms list can be retrieved at the MMI with the
command “disp_act_alarms #” where # is the site number.
3. System Audit Process (SAP)
The SAP exists on every GPROC in a site. The SAP periodically performs a local audit
where it checks the BSS software and forwards any faults found to the fault collection
process for normal fault management processing. The SAP can also be set up to
perform audits on the hardware in the site. The system operator from the MMI controls
this and may set the audit to be scheduled in different ways.
S Continuously at a set interval, e.g. every hour.
S Once at a specific time (e.g. at a specific time every 24 hours).
S At set intervals in a specific time range e.g. every 15 minutes between 0300 –
0400 hours each day.
There are two types of hardware audit:
S Cage – Audits the hardware in the cage where the audit is scheduled.
S Site – Audits the hardware in the site where the audit is scheduled.
Note:
In some cases the SAP will be invoked by the FTP in order to obtain more information on
a fault condition.

ISSUE 1 REVISION 2 Fault Detection and Handling System
Fault Translation Process
OMC
O&M CENTRAL
MMI AUTHORITY
Fault Translation Process TABLE OF FAULT

(FTP) SCENARIOS AND
ACTIONS
Fault Collection
Process (FCP)
BSS devices
HARDWARE/SOFTWARE
BSS11_Ch8_12

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

ISSUE 1 REVISION 2 BSS Alarm Categories
BSS Alarm Categories
1) Intermittent Alarms
2) FM Initiated Clear (FMIC)
3) Operator Initiated Clear (OIC)

BSS11_Ch8_13

Alarm Message Format ISSUE 1 REVISION 2
Alarm Message Format
Introduction
Alarm messages contain information to help the system operator analyse the fault
condition in order to take appropriate action to fix the problem. Alarm messages should
be analysed by using the ‘Alarm Handling at the OMC’ manual 68P02901W26. However
all alarms follow the same basic format.
Message
formats:
Standard Alarm
The format shown is a standard alarm message. The asterisk (*) preceding each line
indicates that this output is not a response to operator action, it has been generated by
the software.
<alarm code> Number representing the type of alarm
<alarm Description> Text describing the specific alarm
<severity> Critical, Major, Minor, Warning, Clear, Investigate
<device type> e.g. KSW, BSP, MSI etc…
<device id> Device identity made up of the 1st, 2nd and 3rd elements
<(subtype)> Subtype of the device (e.g. MSI, XCDR or GDP)
<site> Which site the device is located at
<cage> Which cage the device is located in
<slot> Which slot the device is located in
<date> The date the alarm occurred
<time> The time the alarm occurred
<alarm type> Intermittent, FMIC or OIC
<hardware version> Hardware version of the device
<additional info> Refer to the alarms manual

ISSUE 1 REVISION 2 Alarm Message Format
Standard Alarm Message Format
*Device Alarm ĆĆTag(hex): <config tag>

*
*(<Alarm code>) <alarm description>
*ĆĆSeverity: <severity> Category: <category>
*ĆĆ<device type><device id><(subtype)>[<function id>]
*ĆĆSite:<site> Cage:<cage> Slot:<slot>
*ĆĆTime:<date><time>
*ĆĆAlarm Type:<alarm type> Number of Suppressed
Alarms: <suppressed>
*ĆĆFRU KIT Number: <kit number>
*ĆĆHardware Version Number(hex): <hardware version>
*ĆĆAdditional Info:<additional info>
Example:
*Device Alarm ĆĆ Tag(hex): 01800001

*
*(242) Device(s) OOS due to action on this device
*ĆĆSeverity: INVESTIGATE Category: EQUIPMENT
*ĆĆMSI 1 0 0 (MSI)
*ĆĆSite: 1 Cage: 15 Slot:16
*ĆĆTime: Wed 25/3/1998 13:51:51:000
*ĆĆAlarm Type: Fault Management Initiated Clear
*ĆĆFRU KIT Number: hvn= 4
*ĆĆHardware Version Number(hex): 04
BSS11_Ch8_14

Alarm Message Format ISSUE 1 REVISION 2
Alarm Severity
This field is a text string that indicates the severity of the alarm condition. Refer to the
alarm manual for a more complete definition of the six possible strings:
S Critical Site out of service
S Major Site partially out of service
S Minor Repair required but no loss of service
S Warning Maintenance required
S Clear Condition cleared
S Investigate Unable to assign severity, check it out!
Alarm Category
This field indicates the general category of system operation affected by the alarm.
Refer to the alarm manual for a more complete definition of the six possible strings:
S Communication E1 link failure
S Quality of service Slow call setup
S Processing Firmware problem on a peripheral card
S Equipment Radio failure
S Environment Customer defined alarm (PIX)
S SWFM notice GPROC software fault

ISSUE 1 REVISION 2 Alarm Message Format
Severity:
Critical
Major
Minor
Warning
Clear
Investigate
Category:
Communication
Quality of service
Processing
Equipment
Environment
SWFM notice
BSS11_Ch8_15

Switch Manager (SM) ISSUE 1 REVISION 2
Switch Manager (SM)
Introduction
The SM exists on the master GPROC only. It is responsible for controlling the TDM
highway switch connection made on the KSW. At the BSC the SM is responsible for
mapping the logical channels (Circuit Identity Codes) on the A interface to the channels
on the A-bis interface on a per call basis. Dynamic switching at 16kbps enables call setup
and handovers at the BSC.
At the RXCDR and BTS switching is static therefore the SM at these sites will make
connections at initialisation which will remain unchanged for the duration of operation or
the network is re-configured.

ISSUE 1 REVISION 2 Switch Manager (SM)
Operations and Maintenance – Switch Manager
SM – BSC/RXCDR
Static Switching – RXCDR (16 kbit/s)
Dynamic Switching – BSC (16 kbit/s)
BSS11_Ch8_16

Initialization Process (IP) ISSUE 1 REVISION 2
Initialization Process (IP)
Overview
The Executive is responsible for starting the initialization of the GPROC, using the IP
stored in EEPROM.
The IP has no knowledge of the database therefore it works with default values for site
configuration, such as a master GPROC in slot 20 or 24 of the first cage. Default
positions for the OML to the OMC:
BSC OML defaults

1st default cage 0 slot 16 MMS 0 timeslot 1
2nd default cage 0 slot 16 MMS 1 timeslot 1
3rd default cage 0 slot 14 MMS 0 timeslot 1
4th default cage 1 slot 16 MMS 0 timeslot 1
RXCDR OML defaults

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

ISSUE 1 REVISION 2 Initialization Process (IP)
Initialization Process in ROM
Reboot
Establish LAN
Bring GPROCs
on to LAN
Select master GPROC
Check
if there is
enough N
equipment for
a download
of code
Connect Is a Jump
to OMC Y download N
to
within required? RAM
6 mins
Y
N
Download code
N Is there
code
in RAM?
Cross load code
to all GPROC’s
Y
BSS11_Ch8_17

Initialization in RAM ISSUE 1 REVISION 2
Initialization in RAM
Overview
Once the system has moved to RAM the IP starts again but this time it executes from
RAM. The move to RAM causes the LAN to deactivate therefore the first task is to
re-establish the LAN.
When the LAN is up and running the IP checks to see if a valid database exists on any of
the GPROCs. If a database exists the IP co-ordinates a crossload to all GPROcs.
If no database is available (it is not necessary to download a database from the OMC)
the IP waits for 45 seconds before re-booting the site and starting the initialization
process again.
A system operator has this time to enter a MMI command called ‘sysgen_mode on’. This
tells IP that a database script file is going to be provided. A database script file contains
all the necessary information to allow the master GPROC to build a database object.
The IP then re-initializes the site and goes through the IP process as describe so far.
When it gets to this point the second time it stops and waits for the script to be provided.
The script is uploaded to the GPROC via the TTY interface from the Local Maintenance
Terminal (LMT). Once the script has been uploaded the system operator enters the
command “sysgen off” to return the site to normal operation. At this point the CM and
CA processes check that the database provided is sane. If for any reason the database
is invalid the IP will remain in sysgen mode (indicated by the MMI prompt) and waits for
corrections to be made with MMI commands or a new script to be entered. A report of
why the script failed is provided to aid correction.
When sysgen is successful the IP crossloads the new database object to all GPROCs
and IP initiates the CA process which then takes control. The CA then configures the
site according to the database and takes it into call processing mode. At the BSC the CA
will then work on bringing the BTS sites into operation.

ISSUE 1 REVISION 2 Initialization in RAM
Initialization Process
RAM
Re-establish LAN
Does a Y
database
exist?
N Do all
GPROCs have Y
Inform user a sysgen the same
is required database?
N
Has
N sysgen
mode been
Reboot started within XLoad Initialize CA continue
45 seconds bootup
Ask user to reset site
Sysgen
mode
BSS11_Ch8_18

Call Processing (CP) ISSUE 1 REVISION 2
Call Processing (CP)
Overview
The purpose of CP is controlling communications between the MSC, BSC, BTS and MS.
CP and the Radio Subsystem (RSS) interact to control call set-up and clearing,
handovers, encryption and movement of Direct Transfer Application Part (DTAP)
messages between the MSC and MS.
In the Motorola software architecture the call processing system has been split into two
parts. One part is executed at the BSC the other at the BTS. This is a departure from
the normal architecture that distributes the call processing functions only at the BSC.
With the Motorola structure the BTS takes some of the CP functions along with all of the
RSS functions.
CP at the BSC
S Connectionless Manager (CLM)
S Message Transfer Part L3 (MTPL3)
S SCCP pre-Processor (SCCP)
S SCCP State Machine (SSM)
CP at the BTS
S Radio Resource State Machine (RRSM)
S Cell Resource Manager (CRM)
S Cell Broadcast Scheduler (CBS)
S Radio Channel Interface (RCI)
The SSM at the BSC, manages the SCCP interface to the MSC. The RRSM manages
the radio resource interface to the RSS. The division of the call processing state
machine into two levels allows each state machine to handle common procedures at its
own level without knowing the background for the specific request.
For example, if the SSM sends a release radio channel to the RRSM, the RRSM can
invoke the normal radio channel release procedure without knowing if the channel is
being released because of a Clear Command from the MSC, a break in the SCCP
connection, or O & M intervention. Similarly, if the SSM receives a radio channel
released message from the RRSM, it proceeds in the same manner regardless of
whether this message was generated as a result of a timer expiry or a radio channel link
error. The advantage of this is a reduction in the amount of signalling required between
the BSC and BTS for call processing.

ISSUE 1 REVISION 2 Call Processing (CP)
Call Processing
S Collection of layer 3 Protocols
S Functions
Call setĆup/clearing
Message transfer (DTAP/BSSMAP)
Control handovers
CP RSS Interface
Encryption
Two state machines for CP.
S CPBSC CLM
MTPL3
SCCP
SSM
SM
AM
S CPBTS RRSM/RCI
CRM
CBS
RCI
AM
BSS11_CH8_19

Call Processing at the BSC ISSUE 1 REVISION 2
Call Processing at the BSC
Message
Transfer Part L2
(MTP_L2)
The MTP_L2 process is responsible for the data link layer operations (layer 2 processing)
of the MTL link at the BSC. It terminates the C7 signalling on the LCF GPROC
controlling the MTL link at the BSC and provides error detection and flow control for the
link.
Message
Transfer Part
L3/SCCP
Pre–processor
The MTP_L3 process also executes on the LCF GPROC controlling the MTL link and is
responsible for maintaining the signalling link between the BSC and MSC. As part of the
MTP_L3 process there is a function called the SCCP Pre-processor responsible for
determining the type of messages being passed (DTAP/BSSMAP) and routing the
messages internally at the BSC.
SCCP State
Machine (SSM)
The SSM executes on LCF GPROCs controlling RSLs to BTS sites. The SSM process
is responsible for call set-up, maintenance, release and the primary control of handovers.
A handover evaluator process is part of the SSM process and is responsible for
determining the target BTS for a handover. The SSM also provides a call trace facilility
within the BSS.
Connectionless
Manager (CLM)
The CLM executes on the master GPROC (BSP) at the BSC and is responsible for
connectionless signalling procedures on the MTL link to and from the MSC.
Connectionless procedures are all procedures that are needed to maintain operation
between the BSS and the MSC that are not directly connected with calls. Examples are
circuit blocking, reset of circuits, global reset and signalling point inaccessible.

ISSUE 1 REVISION 2 Call Processing at the BSC
Call Processing at the BSC
To MSC
LCF
MTP L2
17
MTP L3
16
33
LCF
To BTS SSM
HO
EVALUATOR
BSP
CLM
35 AM
SM 64
BSS11_Ch8_20

Call Processing at the BTS ISSUE 1 REVISION 2
Call Processing at the BTS
Introduction
The following call processing functions all execute on the master processor at the BTS
and will not be found active at the BSC.
Radio Resource
State Machine
(RRSM)
RRSM is responsible for maintaining the state of the radio channels allocated to calls at
the BTS. This involves channel requests for call set-up, maintenance and release on call
termination.
Radio Channel
Interface (RCI)
The RCI provides an interface between Radio Subsystem processes and CP. Calls are
tracked within CP by a unique identifier called the SCCP reference number, however
within the RSS calls are tracked by a Radio Channel Identifier (RCI). The RCI process
provides a mapping function for SCCP references to RCIs.
Cell Resource
Manager (CRM)
The CRM is responsible for managing the allocation of radio resources within the BTS
site. Upon request for a radio channel, CRM determines what radio resources to use
based on how the cell is being used, loading on the cell and interference levels on the
available resources. CRM also takes care of intra-cell handovers, dynamic configuration
of traffic channels to SDCCH and generation of SCCP reference numbers at call set-up.
Cell Broadcast
Scheduler (CBS)
The CBS is responsible for Short Message Service Cell Broadcast message scheduling.
The Cell Broadcast Centre (CBC) sends messages and scheduling information to the
BSC and this is forwarded to the CBS at the BTS. The CBS works with the CRM and
RRSM to ensure SMSCB messages are sent out.
Both CBC and OMC can send messages for broadcasting but CBC messages will take
priority over OMC messages.

ISSUE 1 REVISION 2 Call Processing at the BTS
Call Processing at the BTS

BSS11_Ch8_21

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

ISSUE 1 REVISION 2 Allocation Manager (AM)
Call Processing Allocation Manager

BSS11_Ch8_22

Radio Subsystem (RSS) ISSUE 1 REVISION 2
Radio Subsystem (RSS)
Overview
The RSS is a collection of application processes responsible for managing the radio
hardware at the BTS. The RSS consists of five processes:
1. RSS A-bis Interface
2. RSS Layer 2 Protocol
3. RSS Layer 1 Protocol
4. RSS configuration and fault management
5. Handover detection and power control
RSS A-bis Interface (A-bis)

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

Layer 2 provides the data link layer processing of the air interface signalling link. Direct
Transfer and Application Part (DTAP) and system information messages for the MS are
formatted by Layer 2 for the LAPDm protocol used on the air interface. Similarly DTAP
and system messages received from the MS are converted back from LAPDm to a
format suitable for their destination. Error detection and flow control on the air interface
signalling link are performed as part of the Layer 2 function.

ISSUE 1 REVISION 2 Radio Subsystem (RSS)
Radio Subsystem (RSS)
S Software interface procedures between BSS

RF hardware and Mobile Station (MS)
S Each subsystem is contained within its

respective TCU
BSS11_Ch8_23

RSS Layer 1 Protocol (Layer 1) ISSUE 1 REVISION 2
RSS Layer 1 Protocol (Layer 1)

The Layer 1 process interfaces the software processes in the RSS to the hardware
interface to the radio hardware. The functions of Layer 1 are:
S Download of firmware to the radio hardware.
S Message link between RSS to the hardware.
S Reports on communication problems between the RSS and radio hardware to the
Fault Collection Process (FCP).
S Maintains a database for CRM regarding multiple pages, immediate assignments
and immediate assignment rejects.
S Translates downlink messages received from Layer 2 into a format suitable for
transfer to the radio hardware.
S Translates uplink messages received from the radio hardware into Layer 2
messages.
S Obtaining timer information for non-synchronised handovers.
RSS
Configuration
and Fault
Management
(CFM)
The CFM process controls initialisation of the RSS and supervises codeload and
configuration of the radio hardware. CFM takes responsibility for configuration changes
during operation and reporting of alarms from the radio hardware.

ISSUE 1 REVISION 2 RSS Layer 1 Protocol (Layer 1)
Radio Subsystem
To call processing
To fault management
DHP
AĆbis
CFM
Layer 2
HDPC
Layer 1
To the radio hardware BSS11_Ch8_24

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

ISSUE 1 REVISION 2 Handover Detection and Power Control (HDPC)
Handover Detection and Power Control (HDPC)
Functions
D Controls transmission power of

MS
D Controls the timing advance of

MS
D Controls the transmission power

of the BSS
D Determine the need for handover

(intra_BSS and inter_BSS)
D Monitors the interference level on idle

channels
D Detects loss of SACCH messages

(conserving resources)
BSS11_Ch8_25

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

ISSUE 1 REVISION 2 Handover Decision Criteria
Handover Decision Criteria
S Receive quality
S Receive signal strength
S Interference
S Distance
S Power budget
Target Cell Priority
S List of candidate
S Priority
S Interference level
BSS11_Ch8_26

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

ISSUE 1 REVISION 2 Motorola Systems
Motorola System

Radio Cell
Resource Resource Allocation
State Manager Manager
Machine
Radio
Channel
Interface

Radio D D D Radio

Subsystem
Subsystem

D D D
BSS11_Ch8_27

Call Establishment ISSUE 1 REVISION 2
Call Establishment
Description
The following description covers the interprocess communication to place an MS on a
DCCH and have the MS in communication with the MSC.
1. The MS accesses the system with a Random Access Burst (RAB) on the
BCCH.
2 The RSS passes the request onto the RRSM via the RCI in the form of a
Channel Required message.
3. RRSM asks the CRM to assign a SDCCH channel and the CRM
responds.
4. RRSM tells the RSS which DCCH the MS is to go to and the RSS
activates that channel. When channel activated, the RSS informs the
RRSM.
5. The RRSM then tells the MS via the RSS on an Access Granted
Channel (AGCH), which DCCH the MS is to move to.
6. The MS moves to the DCCH and establishes two way communication
with its allocated BTS. The MS forwards CM Service Request, telling
the RRSM what the MS wants to do. Is it –
– responding to a page from the MSC?

– doing a location update?
– IMSI deregistration?
– wanting to establish a call?
– trying to salvage an established call?
7. The RRSM forwards the CM service request up to the SCCP State

Machine (SSM).
8. The SSM then has to request the MSC to handle the call.
Radio Sub-System (RSS)
Radio Resource State Machine (RRSM)
Cell Resource Manager (CRM)
SCCP State Machine (SSM)
Message Transfer Port (MTP)

ISSUE 1 REVISION 2 Call Establishment
Call Establishment
BTS FUNCTIONS
RRSM/
Mobile RSS CRM RCI
Random access
Channel required
Channel required
Channel assigned Choose

DCCH
SDCCH channel activation
Base site
checks
Channel activation acknowledgement
out channel BSC FUNCTIONS
Immediate assign command
SSM MTP
AGCH
Mobile moves to DCCH
Establish indication CM service requirement
MS power control
Power control
Initial Layer 3 Info CM service req
Complete
Layer 3
information
MSC
MSC
requested
to handle
call
BSS11_Ch8_28

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

ISSUE 1 REVISION 2 Voice Channel Assignment
Traffic Channel Assignment
BTS FUNCTIONS BSC FUNCTIONS

MSC
DTI Request
assignment
Assign TFC Initiate assignment

channel
request

Channel assigned
MS
Physical context req timing
advance
Physical context confirm obtained
Channel activation from
DCCH
Channel activation Ack
Assignment command
Channel info to MS
MS
moves to
TFC Establish indication
MS
Channel on new
Data Indication Assign Com channel
Deallocate DCCH
Assignment successful
Connect
radio Connection req
channel to
terrestrial Switch resp
channel
Assign complete
Assign complete
BSS11_Ch8_29

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

ISSUE 1 REVISION 2 Intra BSS Handover
Intra BSS Handover
SOURCE BTS BSC

Handover detection procedure
Handover recognised

TARGET BTS

Request for channel
Channel
assigned
+ activated
Handover allocation
Initiate handover
MS
moves Handover Command
to new
channel
MS access
Handover
Phys info detected
Handover detected
Make
connection
Handover successful MSC
inform
Release radio channel
BSS11_Ch8_30

Intra BSS Handover ISSUE 1 REVISION 2

Chapter 9
BSS Customer MMI Overview

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 9
BSS Customer MMI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
MMI Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Introduction to BSS MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Command Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
Command/Database Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Device and Function Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–10
The Emon Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Executive Monitor and Command List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Rlogin (Remote Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Emon and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Objectives
Objectives
At the end of this section the student should be able to describe the capabilities of the
Customer MMI, and describe the following MMI command types:
S Maintenance.
S System Change Control (Configuration Management).
S Call Processing.
S Miscellaneous.
State the purpose of the EMON and the restrictions on its use and identify the following
procedures with regard to EMON:
S Security
S Rlogin.
S Initialization

MMI Structure ISSUE 1 REVISION 2
MMI Structure
Introduction to
BSS MMI
In order to access the MMI commands at the base site a PC must be connected via an
RS–232 cable to the TTY connector of the GPROC. Once the initial software has been
downloaded from the OMC the MMI command language becomes available via this
connection.
The MMI has been developed to provide an interface between the maintainer and the
BSS processing.
Note:
The TTY port is configured to meet the requirements of the EIA RS232C and CCITT V.24
specifications.

ISSUE 1 REVISION 2 MMI Structure
PC–GPROC Interconnection
PC MCUF
9-9 way cable pin out

Security ISSUE 1 REVISION 2
Security
The BSS system is divided into three different levels of security. The diagram opposite
shows how the different levels overlap each other.
Security level one

These represent the basic commands that are available to the first level maintainer.
Security level two represents all of the commands available to the customer.
Security level two

These commands are more sensitive than security level one commands in terms of
possible damage caused (e.g. take an entire BSC out of service).
Security level three

This level is completely hidden from the first level maintainer or customer. Motorola only
has access to this level. The first level maintainer or customer will not be allowed to use
security level three.
Security level three provides access to the Executive Monitor (ROM/RAM:EMON).
The password for security Level 2 can be changed by the customer, as can the level 3
password if the “Optional Level 3 Password’’ feature is purchased.
The command to change the security level is:
chg_level
The user will then be prompted for the passwords for each level.
To move into the Executive Monitor, move to security level three and press ‘Control N’ on
the keyboard.

ISSUE 1 REVISION 2 Security
Different levels of security
First level maintainer

Customer
Level 1
High security (allows Level 2

access to the
Executive Monitor)
Level 3
BSS11_9_1

Command Categories ISSUE 1 REVISION 2
Command Categories
Each available command within the BSS MMI command language falls into one of five
categories. They are as follows:
Maintenance (Fault Management Database)

Purpose of Fault Management commands:
S Display the administrative state of devices.
S Display the administrative state of functions.
S Modify the administrative state of devices.
S Modify the administrative state of functions.
S Enable, modify, disable, and display alarms.
System Change Control (Configuration Management database)

Purpose of Configuration Management commands:
S Configure the Base Station System.
S Modify the CM database.
S Populate the database during SYSGEN.
S Display information from the CM database.
Call Processing (Database)

Purpose of Call Processing commands:
S Trace the progress of a specified call via random trace (by call rate).
S Trace the progress of a specified call via random trace (by SCCP connection
number).
S Report call processing data.
Statistics (Central Statistics Processing Database)

Purpose of Statistics commands:
S Enable/disable statistics.
S Display/modify statistics for devices or cells.
S Modify statistics time Interval for system.
S Monitor active (enabled) statistics for system.
S Report statistics data.
Miscellaneous Commands
Purpose of Miscellaneous commands:
S Begin/end a SYSGEN session.
S Reset the entire BSS.
S Clear database contents.
S Display/modify time function (time–stamp).
S Display version of a software load.
S Perform miscellaneous procedures (display DTE link address, ROM checksum,
etc).

ISSUE 1 REVISION 2 Command Categories
Command categories
D Maintenance
(Fault Management Database)
D System Change Control

(Configuration Management Database)
D Call Processing
(Database)
D Statistics
(Central Statistics Processing Database)
D Miscellaneous Commands

Command/Database Parameter Types ISSUE 1 REVISION 2
Command/Database Parameter Types

MMI commands and database parameters are classified on the basis of whether or not a
user action is required to enter the command or change the value of the database
parameter.
TYPE A
No special user action is required to enter a Type A command or change a Type A
database.
TYPE B
Special conditions must exist in the system when entering a Type B command or
changing a Type B database parameter. The special conditions are included in the
Operator Actions listing of each command and database parameter description.

ISSUE 1 REVISION 2 Command/Database Parameter Types
Command/Database Parameter Types
D Type A No special user action

D Type B Special conditions Exist (Refer to W23)

Device and Function Dependencies ISSUE 1 REVISION 2
Device and Function Dependencies

The following chart shows device and function dependencies. Due to system
dependencies, some devices and functions can only be equipped after other specific
devices have been equipped. For example, before a BTF can be equipped, a GPROC
must be equipped. A device or function at a lower level can only be equipped if the
device above it has been equipped.

ISSUE 1 REVISION 2 Device and Function Dependencies
Device and Function Dependences
BSC
SITE
CABINET
CAGE
EAS GCLK BSP GPROC CSFP KSW MSI
LCF OMF XBL MTL OML CBL

The Emon Prompt ISSUE 1 REVISION 2
The Emon Prompt

The Emon (Executive monitor) prompt is the main access point for debugging the BSS
system. From this prompt you can gain access to the whole system as well as issue all of
the Emon commands.
Executive
Monitor and
Command List
Once at the Emon prompt the commands available to the user can be divided into the
following categories:
S Statistics.
S Virtual memory.
S Debugging.
S Timer.
S System.
S Analysis.
Emon and
Security
To gain access to the Emon the user must be at security level 3. This level of security
ensures only those users who are allowed to access this level may gain access to the
Executive monitor.
Emon and Rlogin

(Remote Login)
One command available to the user at the Emon prompt is Rlogin (Remote Login). This
command allows the user to login to any connected BTS from a BSC, from a BTS back
to the parent BSC, or from one GPROC to another at the same site. Once the user is
remotely logged into a site commands can be executed as though they were logged in
directly to that site.
Emon and
Initialization
During the Initialization process, progress of the site boot–up can be monitored by
entering the Executive monitor. Once at the Emon prompt the terminal screen will scroll
up the page giving detailed information on the current state of the site.
The Executive monitor can be entered by pressing the keys Ctrl + N.

Chapter 10
Course Assessment

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2
Chapter 10
Course Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
Course Assessment Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Answer Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2

ISSUE 1 REVISION 2

ISSUE 1 REVISION 2 Objectives
Objectives
On completion of this section the student should be able to:
S Complete a multiple choice option assessment paper covering the technical
content of this training course.

Course Assessment Completion ISSUE 1 REVISION 2
Course Assessment Completion

The end of course assessment paper will be issued by the instructor on the final
afternoon of the course.
The assessment will last for 1 hour and is NOT a pass/fail assessment, the results being
for statistical purposes only.
Upon completion of the paper the instructor will go through the correct answers to the
questions posed.
Students are not to mark the assessment paper; answers are to be given on the answer
grid provided.
Answer Grid
On the answer grid students are to fill in details as required at the top of the grid:
S Course number.
S Date.
S Student name.
S Student ID.
The test paper number can be found on the top of the assessment paper.
The correct answer to a question is to be indicated by filling in the appropriate oval
completely.
E.g. If the answer to question 1 is multiple-choice answer C, oval C needs to be filled in
to indicate this:
A B C D
Q1
If the first choice of answer is incorrect, place a cross over the first choice and fill in the
appropriate oval for what is thought to be the correct answer.
E.g. If answer C is thought to be incorrect and answer A correct, a cross needs to be
placed over answer C and the oval for answer A filled in:
A B C D
Q2

ISSUE 1 REVISION 2 Course Assessment Completion

Course Assessment Completion ISSUE 1 REVISION 2

Glossary of Terms

ISSUE 1 REVISION 2

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

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

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

A ISSUE 1 REVISION 2
AUT(H) AUThentication.
AUTO AUTOmatic mode.

ISSUE 1 REVISION 2 B
B Interface Interface between MSC and VLR.

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

B ISSUE 1 REVISION 2
BS Basic Service (group).

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

ISSUE 1 REVISION 2 B
BTS Base Transceiver Station. A network component in the GSM

PLMN which serves one cell, and is controlled by a BSC.
The BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory ix

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

ISSUE 1 REVISION 2 C
CCH Council for Communications Harmonization (referred to in

GSM Recommendations).
CCIT Comité Consultatif International Télégraphique et
Téléphonique. This term has been superceded by ITU–TSS
(International Telecommunications Union –
Telecommunications Sector).
CCM Current Call Meter.
CCP Capability/Configuration Parameter.
CCPE Control Channel Protocol Entity.
CCS Hundred call-seconds. The unit in which amounts of
telephone traffic are measured. A single call lasting one
hundred seconds is one CCS. See also erlang.
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab – cron job file).
CDR Call Detail Records.
CDUR Chargeable DURation.
CEB Control Equalizer Board (BTS).
CED Called station identifier.
CEIR Central Equipment Identity Register.
Cell By GSM definition, a cell is an RF coverage area. At an
omni-site, cell is synonymous with site; at a sectored site, cell
is synonymous with sector. This differs from analogue
systems where cell is taken to mean the same thing as site.
(See below).
1 Cell =
1 Sector
Omni Site 6-Sector Site

1-Cell Site or
(1 BTS) 6-Cell Site
(6 BTSs)
CEND End of charge point.

CEPT Conférence des administrations Européennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor.
CF Conversion Facility.
CF all Call Forwarding services.
CFB Call Forwarding on mobile subscriber Busy supplementary
service.
CFC Conditional Call Forward.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xi

CFNRc Call Forwarding on mobile subscriber Not Reachable

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

ISSUE 1 REVISION 2 C
Coincident Cell A cell which has a co-located neighbour whose cell boundary
follows the boundary of the said cell. The coincident cell has
a different frequency type, but the same BSIC, as that of the
neighbour cell.
COLP COnnected Line Identification Presentation supplementary
service.
COLR COnnected Line Identification Restriction supplementary
service.
CODEX Manufacturer’s name for a type of multiplexer and packet
switch commonly installed at the Motorola OMC-R.
COM Code Object Manager.
COM COMplete.
COMB Combiner.
CONNACK CONNect ACKnowledgement.
COMM, Comms COMMunications.
CommsLink Communications Link. (2Mbit/s)
CONF CONFerence circuit.
CONFIG CONFIGuration Control Program.
CP Call Processing.
CPU Central Processing Unit.
C/R Command/Response field bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity).
CRC Cyclic Redundancy Check (3 bit).
CRE Call RE-establishment procedure.
CREF Connection REFused (Part of SCCP network connectivity).
CRM Cell Resource Manager.
CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed
modem used to interwork 300 to 2400 bit/s data services
under V.22bis, V.23, or V.21 standards. High speed modem
used to interwork 1200 to 9600 bit/s data services under
V.22bis, V.32, or V.29/V.27ter/V.21 standards.
CRT Cathode Ray Tube (video display terminal).
CSFP Code Storage Facility Processor (at BSC and BTS).
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network.
CT Call Transfer supplementary service.
CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool).
CTR Common Technical Regulation.
CTS Clear to Send. Method of flow control (RS232 Interface).
CTU Compact Transceiver Unit (M-Cellhorizon radio).
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xiii

CUG Closed User Group supplementary service.

Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service.
xiv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

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

D ISSUE 1 REVISION 2
DHP Digital Host Processor.

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

ISSUE 1 REVISION 2 D
DRI Digital Radio Interface. Provides encoding/decoding and

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

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

ISSUE 1 REVISION 2 E
EPSM Enhanced Power Supply Module (+27 V).

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

F ISSUE 1 REVISION 2
F Interface Interface between MSC and EIR.

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

ISSUE 1 REVISION 2 F
FRU Field Replaceable Unit.

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

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

ISSUE 1 REVISION 2 G
GSR GSM Software Release.

GT Global Title.
GTE Generic Table Editor. The Motorola procedure which allows
users to display and edit MCDF input files.
Guard period Period at the beginning and end of timeslot during which MS
transmission is attenuated.
GUI Graphical User Interface.
GUI client A computer used to display a GUI from an OMC-R GUI
application which is beingbrun on a GUI server.
GUI server A computer used to serve the OMC-R GUI application
process running locally (on its processor) to other computers
(Gui clients or other MMI processors).
GWY GateWaY (MSC/LR) interface to PSTN.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxiii

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

ISSUE 1 REVISION 2 I
I Information frames (RLP).

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

I ISSUE 1 REVISION 2
INS Intelligent Network Service.

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

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

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

ISSUE 1 REVISION 2 L
Location area An area in which a mobile station may move freely without
updating the location register. A location area may comprise
one or several base station areas.
LPC Linear Predictive Code.
LPLMN Local PLMN.
LR Location Register. The GSM functional unit where MS
location information is stored. The HLR and VLR are location
registers.
LSSU Link Stations Signalling Unit (Part of MTP transport system).
LSTR Listener Side Tone Rating.
LTA Long Term Average. The value required in a BTS’s GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
LU Local Units.
LU Location Update.
LV Length and Value.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxix

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

ISSUE 1 REVISION 2 M
ME Mobile Equipment. Equipment intended to access a set of

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

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

ISSUE 1 REVISION 2 M
MTP Message Transfer Part.

MTTR Mean Time To Repair.
Multiframe Two types of multiframe are defined in the system: a
26-frame multiframe with a period of 120 ms and a 51-frame
multiframe with a period of 3060/13 ms.
MU Mark Up.
MUMS Multi User Mobile Station.
MUX Multiplexer.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxxiii

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

ISSUE 1 REVISION 2 N
NRZ Non Return to Zero.

NSAP Network Service Access Point.
NSP Network Service Provider.
NSS Network Status Summary.
NT Network Termination.
NT Non Transparent.
NTAAB New Type Approval Advisory Board.
NUA Network User Access.
NUI Network User Identification.
NUP National User Part (of signalling system No. 7).
NV NonVolatile.
NVRAM Non-Volatile Random Access Memory.
nW Nano-Watt (10–9).
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxxv

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

ISSUE 1 REVISION 2 O
OSF/MOTIF Open Software Foundation Motif. The basis of the GUI used
for the Motorola OMC-R MMI.
OSS Operator Services System.
Overlap Overlap sending means that digits are sent from one system
to another as soon as they are received by the sending
system. A system using ~ will not wait until it has received all
digits of a call before it starts to send the digits to the next
system. This is the opposite of en bloc sending where all
digits for a given call are sent at one time.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xxxvii

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

ISSUE 1 REVISION 2 P
PID Process IDentifier/Process ID.

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

P ISSUE 1 REVISION 2
PSPDN Packet Switched Public Data Network. Public data

communications network. x.25 links required for NE to OMC
communications will probably be carried by PSPDN.
PSTN Public Switched Telephone Network. The UK land line
telephone network.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTO Public Telecommunications Operator.
PUCT Price per Unit Currency Table.
PVC Permanent Virtual Circuit.
PW Pass Word.
PWR Power.
PXPDN Private eXchange Public Data Network.
xl BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2 Q
Q
QA Q (Interface) – Adapter.
Q3 Interface between NMC and GSM network.
Q-adapter Used to connect MEs and SEs to TMN (GSM Rec. 12.00).
QAF Q-Adapter Function.
QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to
TDM switch highway (see MSI).
QIC Quarter Inch Cartridge (Data storage format).
QOS Quality Of Service.
Quiescent mode IDS intermediate state before shutdown.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xli

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

ISSUE 1 REVISION 2 R
RFC, RFCH Radio Frequency Channel. A partition of the system RF

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

R ISSUE 1 REVISION 2
RSZI Regional Subscription Zone Identity.

RTC Remotely Tuneable Channel Combiner.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function.
RTF Receive Transmit Functions.
RTS Request to Send. Method of flow control (RS232 Interface).
RU Rack Unit.
Run level System processor operating mode.
Rx Receive(r).
RXCDR Remote Transcoder.
RXF Receive Function (of the RTF).
RXLEV-D Received signal level downlink.
RXLEV-U Received signal level uplink.
RXQUAL-D Received signal quality downlink.
RXQUAL-U Received signal quality uplink.
RXU Remote Transcoder Unit. The shelf which houses the
remote transcoder modules in a BSSC cabinet at a remote
transcoder site.
xliv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

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

S ISSUE 1 REVISION 2
SDL Specification Description Language.

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

ISSUE 1 REVISION 2 S
SME Short Message Entity.

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

S ISSUE 1 REVISION 2
SSS Switching SubSystem (comprising the MSC and the LRs).

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

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

T ISSUE 1 REVISION 2
TDMA Time Division Multiple Access.

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

ISSUE 1 REVISION 2 T
TS TeleService.
TS TimeSlot (see Timeslot).
TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech & Data Interface.
TSC Training Sequence Code.
TSI TimeSlot Interchange.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSW Timeslot SWitch.
TTCN Tree and Tabular Combined Notation.
TTL Transistor to Transistor Logic.
TTY TeleTYpe (refers to any terminal).
TU Traffic Unit.
TUP Telephone User Part (SS7).
TV Type and Value.
Tx Transmit(ter).
TXF Transmit Function (of the RTF).
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter.
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory li

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

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

W ISSUE 1 REVISION 2
W
WAN Wide Area Network.
WPA Wrong Password Attempts (counter).
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network
management purposes.
WSF Work Station Function block.
WWW World Wide Web.
liv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

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

Z ISSUE 1 REVISION 2
Z
ZC Zone Code
lvi BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2 Z
EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory lvii

Z ISSUE 1 REVISION 2
lviii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

BSS11

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS11

Uploaded by

Copyright:

Available Formats

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5

COURSE ADMINISTRATION BSS OVERVIEW BSSC CABINET HORIZONMACRO HORIZONMICRO/COMPACT

FOR TRAINING PURPOSES ONLY

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

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory i

FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

and MOTOROLA are trademarks of Motorola Inc.

ii BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

FOR TRAINING PURPOSES ONLY

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

iv BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Base Station Controller (BSC) Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory v

FOR TRAINING PURPOSES ONLY

Remote Transcoder Unit (RXU) Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50

vi BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

The Generic Clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–88

FOR TRAINING PURPOSES ONLY

Motorola Cellular Advanced Processor (MCAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–116

FOR TRAINING PURPOSES ONLY

LANX Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AppA–3–10

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory ix

FOR TRAINING PURPOSES ONLY

Outdoor cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48

x BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Power Supply Module (PSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xi

FOR TRAINING PURPOSES ONLY

The rectifier module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–146

FOR TRAINING PURPOSES ONLY

Horizonmacro RF Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–192

FOR TRAINING PURPOSES ONLY

The Cavity Combining Block (CCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–242

FOR TRAINING PURPOSES ONLY

Booster Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory xv

FOR TRAINING PURPOSES ONLY

FOR TRAINING PURPOSES ONLY

Base Shelf Unit (BSU) assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28

FOR TRAINING PURPOSES ONLY

The Bus Termination Card (BTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–72

FOR TRAINING PURPOSES ONLY

FOR TRAINING PURPOSES ONLY

Central Authority (CA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20

xx BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

Voice Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–58

FOR TRAINING PURPOSES ONLY

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory 1

FOR TRAINING PURPOSES ONLY

Special key sequences

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

2 BSS11: Base Station Systems – Operational Theory EMOTOROLA LTD. 2000

FOR TRAINING PURPOSES ONLY

First aid in case of electric shock

EMOTOROLA LTD. 2000 BSS11: Base Station Systems – Operational Theory 3

FOR TRAINING PURPOSES ONLY

Reporting safety issues