Bss 101

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4
GPRS NETWORK OVERVIEW CPCI OVERVIEW CPX8216 CAGE CPCI DIGITAL CARD
Cellular Infrastructure Group
VERSION1 REVISION 0
BSS101GSR5.1
MODULE 1: INTRODUCTION TO PCI CAGE
MODULE 3: PCU OPERATIONS AND
MAINTENANCE
FOR TRAINING PURPOSES ONLY
VERSION1
REVISION 0
BSS101GSR5.1
MODULE 1:
INTRODUCTION TO
PCI CAGE
MODULE 3: PCU
OPERATIONS AND
MAINTENANCE
FOR TRAINING
PURPOSES ONLY
BSS101GSR5.1
MODULE 1: INTRODUCTION TO PCI
CAGE
MODULE 3: PCU OPERATIONS AND
MAINTENANCE
VERSION1 REVISION 0
BSS101GSR5.1
Module 1: Introduction to PCI Cage
Module 3: PCU Operations and
Maintenance
Motorola 1993 to 2000

All Rights Reserved
Printed in the U.K.
MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage i

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

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

VERSION1 REVISION 0
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
MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage iii

VERSION1 REVISION 0
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
Module 1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter 1
GPRS Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter 1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
GPRS Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The GPRS Support Node Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
OMC–G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
GPRS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
GPRS Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Simplified Protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
GPRS Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Coding Scheme Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
GPRS 52 Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Control Channel Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Chapter 2
CPCI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
The Peripheral Component Interconnect Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
PCI Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Memory IO and Configuration Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
DEVSEL/IDSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Configuration Space Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Device Functions and Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Device Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Configuration Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
PCI Bus components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
PCI Expandability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Arbitration and Error signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Subtractive decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
iv BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

VERSION1 REVISION 0
Chapter 3
CPX8216 Cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
CPCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
CPX8216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
System Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Slot Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
System Processor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
The Simplex Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
The Active/Passive Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
The Active/Active or Load-Sharing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
2N Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
N+1 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Power Supplies/Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Heartbeat and Checkpoint Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Heartbeat Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Checkpoint Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Switching Service to the Passive SSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Hot Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
The Hot Swap Controller/Bridge (HSC) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Hot Swap Control Status Register (CSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Board Insertion and Extraction Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Staged Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
BD_SEL# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
ENUM# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
The Hot Swap Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Compact PCI Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Bus Connectors/ Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
CompactPCI Signal Additions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
IDSEL Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
REQ#/GNT# Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30
PCI Clock Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30
Replacing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Condition for Replacing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
ESD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Removing a Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Installing a Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34
Non Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34
Chapter 4
CPCI Digital Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
MCP 750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
MCP 750 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Peripheral Mezzanine Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Hot Swap Controller/Bridge Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bridge board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage v

VERSION1 REVISION 0
Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

Alarm module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Alarm Panel LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Alarm board Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
vi BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

VERSION1 REVISION 0 General information
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals
are intended to support the delivery of Technical Education only and are not intended to
replace the use of Customer Product Documentation.
WARNING
Failure to comply with 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
MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 1

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

Special key sequences are represented as follows:
CTRL-c 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 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

VERSION1 REVISION 0 First aid in case of electric shock
First aid in case of electric shock
Warning
WARNING
Do not touch the victim with your bare hands until the electric circuit is
broken.
Switch off. If this is not possible, protect yourself with dry insulating
material and pull or push the victim clear of the conductor.
Artificial
respiration
In the event of an electric shock it may be necessary to carry out artificial respiration.
Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration,
carry out the following:
1. 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 VERSION1 REVISION 0
Reporting safety issues
Introduction
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1. 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.

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

General warnings VERSION1 REVISION 0
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola GSM manuals. Failure to
comply with these warnings, or with specific warnings elsewhere in the Motorola GSM
manuals, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the 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:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.

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

Human exposure to radio frequency energy (PCS1900 only) VERSION1 REVISION 0
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,

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.

VERSION1 REVISION 0 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) VERSION1 REVISION 0
Example
calculation
For a base station with the following characteristics, what is the minimum distance from
the antenna necessary to meet the requirements of an uncontrolled environment?
Transmit frequency 1930MHz
Base station cabinet output power, P +39.0dBm (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:

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:

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.

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

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

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

VERSION1 REVISION 0 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 VERSION1 REVISION 0
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

VERSION1 REVISION 0 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 VERSION1 REVISION 0

VERSION1 REVISION 0 Module 1 Objectives
Module 1 Objectives
At the end of this module the student will be able to:
State the basic operation of GPRS.
State the operation of the PCI Bus.
Identify the components of the CPX8216 cage.
State the operation of common (PCU and SGSN) digital modules.

Module 1 Objectives VERSION1 REVISION 0

Chapter 1
GPRS Network Overview

VERSION1 REVISION 0

VERSION1 REVISION 0
Chapter 1
GPRS Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GPRS Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The GPRS Support Node Complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
OMC–G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
The Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
GPRS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
GPRS Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Simplified Protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
GPRS Coding Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
GPRS 52 Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Control Channel Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12

VERSION1 REVISION 0

VERSION1 REVISION 0 Chapter 1 Objectives
Chapter 1 Objectives
At the end of this chapter the student will be able to:
Explain the components of a GPRS network.
State the name and basic function of the GPRS Interfaces.
State the name and basic function of the GPRS protocols.
Explain the basic operation of the Air Interface with respect to GPRS.
MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 1–1

GPRS Network Overview VERSION1 REVISION 0
GPRS Network Overview

The diagram opposite shows a simplified General Packet Radio Service (GPRS)
network. Each network component is illustrated once, however, many of the components
will occur several times throughout a network.
The principal network component groups are:
The GPRS
Support Node
Complex
The GPRS Support Node Complex is the main element in the GPRS infrastructure. It is a
high performance, broadband packet switching node that provides connection and
interworking with various data networks, mobility management and delivery of data
packets to mobile stations. The GSN Network is made of the following component
groups.
CommHub – The CommHub is the central connection point for the components in
a GPRS system. It provides LAN connectivity between GPRS components through
Ethernet and WAN connectivity to data networks outside the GPRS system.
ISS – The Integrated Support Services provides GPRS system components with
the current time, domain name translation and network information.
GGSN – The Gateway GPRS Support Node provides network access to external
hosts so they can communicate with MSs. It also decapsulates and forwards
external data networks packets to the appropriate data network.
SGSN – The Serving GPRS Support Node detects and tracks GPRS MSs in its
service area and provides a reliable, secure data channel as the MS moves
between cells.
OMC–G
The OMC-G enables operators to use an NT graphical user interface (GUI) when
managing the GPRS components. System operators use the OMC–G to configure and
monitor system components and view performance data.
The Base Station

System (BSS)
The Base Station System provides the radio frequency link between the GPRS network
infrastructure and mobile subscribers throughout the operational area. A BSS consists of
three components:
Base Station Controller (BSC)
Base Station Transceiver (BTS)
Packet Control Unit (PCU) – The Packet Control Unit (PCU) performs radio
functions and GPRS network functions. It has interfaces to the OMC-R, BSC and
the SGSN.
The Mobile
Station (MS)
The MSs can belong to three classes A, B or C. The class determines whether GPRS
and Circuit Switched services can be carried out at the same time or not. The mobiles
are also divided into multislot classes that determine the mobile capability of sending and
receiving over multiple slots in a TDMA frame.
1–2 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

VERSION1 REVISION 0 GPRS Network Overview
GPRS network entities
BSC RXCDR MSC
PCU
BTS
Frame Relay
SGSN
CommHub
Internet
Router
Gi
GGSN
ISS
BSS101_Mod1_Ch1_01

GPRS Interfaces VERSION1 REVISION 0
GPRS Interfaces
GPRS has introduced new interfaces. These are listed below:
Gn – GPRS Support Node back bone network – This interface connects the SGSN
and GGSN entities together using TCP/IP (note this is a private TCP/IP network).
Gb – BSS to Serving GPRS Support node – This Interface uses Frame relay and
the connection may go through a 3rd party supplier.
Gr – SGSN to HLR connection – A C7 signalling link.
Gp – GGSN to another PLMN used for roaming between GPRS networks.
Gs – SGSN to MSC signalling link (A C7 signalling link).
Gi – External Interface to connect the GPRS network to a Public Data Network i.e.
the Internet.
The Gb link uses Frame Relay as a data link mechanism – this may well be point to point
or could utilize the existing infrastructure of a Frame Relay provider.
The TCP/IP backbone (the Gn interface) connects the GSN entities together in the
Motorola Solution – this is implemented using the Communications Hub which supports
virtual LAN connections. The diagram opposite shows the logical connections of the GSN
entities.

VERSION1 REVISION 0 GPRS Interfaces
Interfaces in a GSM/GPRS System
A
MSC
BTS
Abis BSC
GDS
(Motorola)
BTS Gs
PCU HLR
Gb
Frame Relay
Gr
TCP/IP Backbone
SGSN SGSN
Gn Gn
Gn
GGSN Gi
Gp PDN
To another
PLMN
BSS101_Mod1_Ch1_02

GPRS Protocols VERSION1 REVISION 0
GPRS Protocols
Simplified
Protocol stack
GPRS has been designed to carry packet data protocols from a public data network to a
mobile user. The Protocol stack can be simplified into 3 layers. When viewed in this
manner the GPRS system looks very similar to a computer network protocol stack (i.e. a
TCP/IP stack).
As can be seen from Figure 1 the simplified protocol stack makes GPRS look like a
conventional IP stack. The big difference lies mainly at Layer 2.
In a conventional TCP/IP stack the IP sits on top of Layer 2 which would typically be
Ethernet. In the Motorola GPRS system we do use Ethernet at the GSN but this should
not be thought of as the Layer 2 entity. Instead it is only a small subsection of this.
GPRS could then be considered as a Layer 2 mechanism to transport a packet data
protocol such as IP across a mobile network infrastructure to a mobile user.
Layer 3 at the GGSN

At the top of the GGSN stack we have IP. The IP datagrams come from a host on a
network that the GGSN is connected to (via routers), though it is shown at the top of the
GGSN stack.
Layer 2 between SGSN and GGSN

At Layer 2 of the GGSN or the SGSN we have several protocols. These exist to provide
a moving data connection (don’t forget the end user is mobile, unlike static users
connected to a telephone line) and also to hide the IP datagrams so that we can
transport the data in an IP datagram for distribution over the GSN network.
Layer 2 between MS and SGSN

The Layer 2 protocols between the MS and the SGSN serve to transfer reliable data over
the air interface.
Layer 1 Between MS and GGSN

The Layer 1 interface is perhaps the only layer beneath IP that truly is Layer 1. From the
mobile to BSS we have the air interface a radio link. From the BSS we have a WAN link
to the SGSN and from SGSN to GGSN we have an Ethernet (in most Motorola systems).

VERSION1 REVISION 0 GPRS Protocols
Simplified Network Protocol Stack
Layer 3 Layer 3
IP IP
Layer 2 Layer 2 Layer 2 Layer 2 Layer 2 Layer 2
SNDCP and LLC RLC/ and BSSGP SNDCP GTP and GTP and
and RLC/MAC MAC and Network and LLC TCP/UDP TCP/UDP
and BSSGP and IP and IP
and Network
Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1
GSM RF GSM RF E1 E1
MS BSS SGSN GGSN
BSS101_Mod1_Ch1_03

GPRS Coding
Schemes
In a GPRS network, there are several channel–coding schemes defined to operate over
the air interface and provide varying data rates to the end–user. In general, as the
mobile experiences better RF conditions, the coding scheme in use can be changed
automatically by the PCU to afford higher throughput. Essentially the differences
between coding schemes determine the amount of protection provided to the data. The
channel coding schemes in GPRS are referred to as CS–1, CS–2, CS–3, and CS–4.
Due to the degree to which the data is coded as the coding scheme changes, the radio
properties experienced by the mobile station will dictate how efficient a given coding
scheme is. When there is not much coding on the data (i.e. CS–3 and CS–4), a given
block will generally not be received correctly in poor RF environments. It is the PCU’s
responsibility to calculate which coding scheme should be used. This decision is based
upon:
Downlink signal and interference level information provided by the MS
during channel quality reports, sent with the downlink packet ack/nack.
Uplink Rx signal level sampled by the BTS
Uplink Interference level on idle blocks sampled by the BTS
When the coding scheme is calculated for uplink data transfers, the information provided
to the PCU by the channel coders within the BTS, are combined to define the C/I (Carrier
to Interference) ratio for the given mobile station.
The data rates for the GPRS coding schemes are as follows:
Coding Scheme
Rates
Channel Coding Scheme Throughput Convolutional
(Per TS) Coding Rate
CS–1 9.05 Kbps 1/2

CS–2 13.5 Kbps 2/3
CS–3 15.6 Kbps 3/4
CS–4 21.4 Kbps 1

GPRS Coding Schemes
CS4
CS3
CS2
CS1
Sys102_1_14
Coding Scheme
Rates
Channel Coding Scheme Throughput Convolutional Coding Rate

(Per TS)
CS–1 9.05 Kbps 1/2
CS–2 13.5 Kbps 2/3
CS–3 15.6 Kbps 3/4
CS–4 21.4 Kbps 1

GPRS 52
Multiframe
The 52 frame structure shown opposite is a new frame. Its structure is totally
different from the existing 51 and 26 frame structures.
The 52 Multiframe does not have a rigid structure. Essentially the different
channels are identified by message type. The Multiframe can carry control
channels or data channels.
CONTROL CHANNELS TRAFFIC CHANNELS

PBCCH PDTCH
PPCH PACCH
PAGCH
PNCH

52 Multiframe Structure
0
1
2
3
4
B0 5
B1 6
B2 7
4 frames
I 8 TS
B3
B4
B5
I I = Idle frame
B6
B7
B8 B(n) = 4 frame radio block
I
B9
B10
B11
I
BSS101_Mod1_Ch1_05

Control Channel
Structure
GPRS uses one or more timeslots per call known as Packet Data Channel
(PDCH). PDCHs are physical channels which consist of various logical
channels.
Packet Common Control Channel (PCCH) – comprises logical channels for common
control signalling of packet data.
Packet Random Access Channel (PRACH) – Ul only.
Uplink only, mapped on to the PDCH or the PACH. Used by the MS to initiate uplink
transfer, e.g. sending data or paging response.
Packet Paging Channel (PPCH) – downlink only
PPCH is used to page an MS prior to downlink transfer.
Packet Access Grant Channel (PAGCH) – downlink only
PAGCH used in packet transfer establishment phase to send resource assignment to an
MS prior to packet transfer.
Note: Resource Assignment for a downlink assignment can be sent on the PACCH if the
MS is currently involved in a Packet Transfer.
Packet Broadcast Control Channel (PBCCH) – downlink only
PBCCH broadcasts Packet Data specific information if the PBCCH is not allocated then
the BCCH is used to broadcast Packet Data Specific Information.

Control Channel Structure
CCH
CCCH BCCH
RACH PCH/AGCH CBCH
PCCH
PBCCH
PCCH
PRACH PPCH PAGCH PNCH
BSS101_Mod1_Ch1_06


Chapter 2
CPCI Overview

VERSION1 REVISION 0

VERSION1 REVISION 0
Chapter 2
CPCI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
The Peripheral Component Interconnect Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
PCI Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Memory IO and Configuration Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
DEVSEL/IDSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Configuration Space Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Device Functions and Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Device Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Configuration Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
PCI Bus components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
PCI Expandability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Arbitration and Error signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Subtractive decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20

VERSION1 REVISION 0

State the operation of the PCI Bus.
State the difference between Memory I/0 and Configuration space.
Identify PCI Bus Components.
Explain the needs and operation of PCI Bridging.

The Peripheral Component Interconnect Bus VERSION1 REVISION 0
The Peripheral Component Interconnect Bus
History
Peripheral Component Interconnect (PCI) was originally developed in 1992 by Intel to
support the x86 CPU architecture for personal computers.
They had maintained separate I/O addressing/memory addressing throughout their
processor range. The PCI specification was then a natural progression.
The PCI specification maintains the separation of memory and I/O addressing – that is
system I/O space and system memory space.
Various bodies exist to maintain and develop the PCI standards; PICMG developed the
CompactPCI specification, which was first released on November of 1995.
CPCI evolved from PCI (signalling is a superset of PCI). In the PC the backplane is
active with CPU and memory, CPCI made the backplane passive (as well as defining
new signals and mechanical factors).

VERSION1 REVISION 0 The Peripheral Component Interconnect Bus
CPCI Evolution
CPU
Memory
PCI Card PCI Card
Motherboard
Standard PC (active backplane)
Memory
CPU
Backplane
CPCI (passive backplane)
BSS101_Mod1_Ch2_1a

PCI Bus
A PCI bus is used to connect together PCi compatible devices. This could be a processor
board, chip, graphics card or single board computer. The PCI bus can be found on the
processor boards used in the Motorola GPRS solution as well as in the CPCI cages of
the PCU and the SGSN.
PCI addressing
PCI maintains three separate spaces:
1. PCI memory space – up to 4Gb addressable with 32 or 64 bit data transfers.
2. PCI I/O space – up to 4Gb addressable with 32 or 64 bit data transfers.
3. PCI configuration space – access to PCI configuration header by bus, device and
function numbers.
Addressing is achieved by using the address bus (which is also the data bus) and the
Command/Byte Enable bus (C/BE bus). The C/BE bus issues 4 bit commands to
determine if the address is IO, memory or configuration.
Command type C/BE 3 C/BE 2 C/BE 1 C/BE 0

I/O read 0 0 1 0
I/O write 0 0 1 1
Mem read 0 1 1 0
Mem write 0 1 1 1

PCI Addressing
Command type C/BE 3 C/BE 2 C/BE 1 C/BE 0

I/O read 0 0 1 0
I/O write 0 0 1 1
Mem read 0 1 1 0
Mem write 0 1 1 1
4 bit C/BE bus
PCI Device
BSS101_Mod1_Ch2_1

Command Codes
The command codes on the C/BE bus are presented on the bus at the same time that
the address is placed onto the address/data bus.
The device can then distinguish what the address bus is referring to. There are many
other command codes than those shown previously. These would include the 0000
command code. This is used for interrupt acknowledgement. Should a device issue an
Interrupt then this command is returned indicating that the host is responding to the
Interrupt to which the interrupting device would respond with an Interrupting vector.
The A/D bus and C/BE bus in this example (opposite) are on the backplane and the
device is on a PCI card.

C/BE Bus
CPCI Card
A/D bus C/BE bus
PCI
Device
Address I/O write
BSS101_Mod1_Ch2_2

Memory IO and Configuration Access VERSION1 REVISION 0
Memory IO and Configuration Access
DEVSEL/IDSEL
For memory and IO transactions the C/BE bus determines what type of access is
required, for example, IO read, mem write etc. All of the devices on the bus will read the
address to determine if the data is for them. Once the device has determined that it is the
subject of the data transfer then it will assert DEVSEL (Device Select). DEVSEL is
control line connected to each device on the PCI bus.
If device 0 recognises the address as its own then device 0 asserts the DEVSEL line.
For configuration transactions each device is selected by the IDSEL (Identity Select).
In this case, the host has selected Device 0 by IDSEL. As each device has its own
configuration register and the system needs to differentiate between them. During the
address phase of the A/D bus the C/BE identifies the configuration space and whether
read or write. During data phase of the A/D bus C/BE indicates a 4-byte transfer. The
connections IDSEL and DEVSEL vary with the manufacturer’s system design.

VERSION1 REVISION 0 Memory IO and Configuration Access
Memory IO and Configuration Access
CPCI Card CPCI Card
Device 0 Device 1 Device 2

DEVSEL
Address and Data
C/BE
CPCI Card
IDSEL Device 0 Device 1 Device 2
Address and Data

C/BE
BSS101_Mod1_Ch2_3

Memory IO and Configuration Access VERSION1 REVISION 0
Configuration
Space
Transactions
During configuration space transfers the A/D lines are grouped and have specific
functions as listed below;
Address lines Description

AD 1 to 0 00 = Type 0 config transaction i.e. targeting a
PCI Bus device
01 = Type 1 config transaction i.e. targeting
device on the other side of a PCI bridge
AD 7 to 2 Indicate target config double word (offset in
config header)
AD 10 to 8 Indicate target function number within device
AD 31 to 11 Can be used to drive IDSEL but depends on
implementation
Therefore if the PCI host needed to configure a device that was on the other side of a
bridge then it would set AD 1:0 to 01. The Host can therefore distinguish between local
PCI and a remote PCI bus for configuration purposes.

VERSION1 REVISION 0 Memory IO and Configuration Access
Configuration space addressing
Part of PCI Bus CPCI Card

AD 1 to 0
AD 7 to 2
Host
AD 10 to 8 (Also Device)
AD 31 to 11
BSS101_Mod1_Ch2_4
Address lines Description
AD 1 to 0 00 = Type 0 config transaction i.e. targeting a PCI Bus device
01 = Type 1 config transaction i.e. targeting device on the

other side of a PCI bridge
AD 7 to 2 Indicate target config double word (offset in config header)
AD 10 to 8 Indicate target function number within device
AD 31 to 11 Can be used to drive IDSEL but depends on implementation

Device Functions and Headers VERSION1 REVISION 0
Device Functions and Headers
Device
Functions
A PCI device offers an electrical load to the PCI Bus i.e. an IC.
A PCI device could have up to eight different functions running. These are logical
devices. The device must have a minimum of one logical function running. Each function
must also have its own configuration header so the host processor can uniquely
configure a PCI device function.
The first function in a PCI device is labelled function 0 and the last is labelled function 7.
Configuration
Header
The configuration header is a set of registers that contain configuration parameters for
that function. The host processor can change these registers when the C/BE bus issues
the correct commands. Each function on a device must have its own set of these
registers.
Up to 256 registers are addressable within the Configuration header. PCI defines some of
the registers the others are for use by the function. If a function requires more than 256
registers then one register in the header could be set up to point to another 256 registers.

VERSION1 REVISION 0 Device Functions and Headers
PCI device functions
A PCI device offers an PCI device

electrical load to the PCI Function 0
Bus i.e. an IC
Function 1
Function 2
Function 3
Configuration registers
1 per device function Function 4
Function 5
Function 6
Function 7
Multiple devices on a card

BSS101_Mod1_Ch2_5

PCI Bus components

There are various components to the PCI Bus system. We have a Host processor on the
bus that needs to communicate with peripheral cards. It may be that the number of
peripherals required means that not all cards can fit onto the PCI bus. It must be
remembered that the PCI bus could address many cards on one bus but the number is
usually limited to no more than 10 due to electrical loading. The PCI cage used in the
Motorola GPRS solution houses up to eight cards per PCI bus.
If more cards are required then another PCI bus is used and the two are connected
together by a bridge. Many PCI busses can be cascaded together in this fashion. It must
be remembered that some of the PCI busses may be on a device card and the card itself
could have a bridge built into it to communicate with the Host.
The real definition of a device on a PCI bus is one that offers one electrical load onto the
bus.
Some PCI component terms:
Host Controls the PCI local bus
Device A unit attached to the PCI bus offering an electrical load
PCI Bridge connects together two PCI buses enabling more peripheral cards to
communicate with the host than can fit onto one PCI bus
Initiator A device that begins bus transactions (this used to be referred to as the
bus master)
Agent Any Initiator or Target
Target A device responding to an Initiator (this used to be referred to as the
slave)
PCI local bus A 32 bit Address/ Data bus, which can optionally extended to 64 bits. In
64–bit mode, four additional C/BE lines are needed along with two
handshake and parity lines.

PCI bus components
i.e. SSP
Host processor
PCI Local bus
Host
PCI to PCI bridge
PCI Local Bus, 32 bit A/D Bus i.e. Backplane
i.e. HSC/Bridge
PCI Bridge
BSS101_Mod1_Ch2_6

PCI
Expandability
The PCI local bus was designed to be expandable. It is possible to connect together
256 local buses using PCI to PCI bridges. Each Bridge creates a new PCI bus
where a full complement of devices can be attached.
Each bus is numbered sequentially by the operating software. Each PCI local bus could
address 32 different devices. This is however limited to 10 due to electrical loading; (a
possible 2 x 8 PCI cards could be fitted in the Motorola CPCI cage).

PCI Bridging
System Slot Processor

PCI to Local Bus 01
PCI to PCI Bridge
Backplane PCI to Local Bus 02
Non-System Slot Processor
PCI to PCI Bridge
PCI Local Bus 03
BSS101_Mod1_Ch2_7

Arbitration and Error signals
Arbitration
In order to avoid collision on the shared PCI bus the control of the bus must go through
arbitration.
A device activates the REQ line (there is a REQ line from each device to the bus arbiter).
When the bus arbiter decides to let the device use the bus, the arbiter activates the GNT,
(grant) line. The device must however wait until for current bus transactions on the bus
are completed before taking control of the bus i.e. becoming bus master.
Error Signals
If an error is detected in received data, (i.e. Target write, Initiator read) the device issues
a PERR (Parity error). Targets have PERR output and Initiators have PERR output and
Input.
System error SERR. All devices have a SERR output. It is asserted when;
There is a parity error during address phase
There is a parity error on data phase during a special cycle
Non parity error problems
Critical System failures

Arbitration and error signals
Non-System Slot Processor System Slot Processor

Backplane
REQ
PCI Device PCI Bus
Arbiter
GNT
Arbitration
Error signals PERR and SERR
BSS101_Mod1_Ch2_8

Subtractive
decoding
PCI uses subtractive decoding to allow connection to an ISA bus. An ISA bus
cannot be addressed via PCI so a PCI to ISA bridge is required. The bridge acts
as a subtractive decoder.
There are two methods of decoding positive and subtractive:
Positive – Where a device recognises the address on the A/D bus and responds
with DEVSEL
Subtractive – Where a device claims the transaction because no one else has.
The bridge acting as a subtractive decoder will issue the DEVSEL on behalf of the ISA
bus/device which cannot.

Subtractive Decoding
System Slot Processor
PCI to Local Bus
DEVSEL
Subtractive decoding PCI to ISA bridge
ISA Bus
BSS101_Mod1_Ch2_9


Chapter 3
CPX8216 Cage

VERSION1 REVISION 0

VERSION1 REVISION 0
Chapter 3
CPX8216 Cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
CPCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
CPX8216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
System Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Slot Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
System Processor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
The Simplex Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
The Active/Passive Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
The Active/Active or Load-Sharing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
2N Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
N+1 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Power Supplies/Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Heartbeat and Checkpoint Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Heartbeat Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Checkpoint Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Switching Service to the Passive SSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Hot Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
The Hot Swap Controller/Bridge (HSC) Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Hot Swap Control Status Register (CSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Board Insertion and Extraction Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Staged Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
BD_SEL# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
ENUM# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
The Hot Swap Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Compact PCI Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Bus Connectors/ Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
CompactPCI Signal Additions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
IDSEL Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
REQ#/GNT# Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30
PCI Clock Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30
Replacing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Condition for Replacing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
ESD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Removing a Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Installing a Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34
Non Hot Swap Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34

VERSION1 REVISION 0

Identify the CPX8216 cage and components.
State the configurations of the CPX8216 cage.
State the operation of the Power Supplies and cooling system.
Explain the operation of the CPU complex.
Explain the operation of the Hot swapping process.
State the operation of CPCI backplane.
Install a hot swap module.

CPCI VERSION1 REVISION 0
CPCI
CPX8216
The CPX8216 system is compliant with the CompactPCI Hot Swap Specification
developed by the PCI Industrial Computers Manufacturing Group (PICMG). The system
allows the use of I/O modules that are not hot swappable, but the system must be
powered off when such modules are inserted and extracted. The CPX8216 features the
ability to hot swap system and non-system processor boards.
System Layout
The CPX8216 is a 16-slot, high-availability CompactPCI system with two separate 6-slot
CompactPCI I/O domains and the capability to contain redundant CPU modules and
redundant Hot-Swap Controller (HSC) modules. It is possible to configure the system as
a simplex, high I/O system containing a single CPU–HSC pair. Even as a simplex
system, the CPX8216 still provides improved availability through redundant power
supplies and the control/monitoring capabilities of the HSC.
The CPX8216 standard system consists of two 8-slot subsystems, or domains, each with
two slots for the host processor and six slots for non-host CompactPCI boards, (i.e. the
I/O domains). The HSC board mounts in the rear of the chassis, behind the secondary
CPU slot.

VERSION1 REVISION 0 CPCI
CPX 8216 Cage
ALARM MODULE DIGITAL

MODULES
(transition module
and bridge)
DIGITAL
MODULES
POWER
DISTRIBUTION
MODULE
(not visible)
CPCI CHASSIS
FAN/POWER SUPPLY
SLEDS
BSS101_Mod1_Ch3_01

Slot Numbering
Slot numbering starts at the top left corner as viewed from the front of the cage.
Logical slot numbers are used in the nomenclature to define the physical outline of a
connector on a bus segment.
System Layout
There is a system slot processor (SSP) slot for each of the two independent I/O
domains. Each system processor has direct access to its local bus through an onboard
PCI-to-PCI (P2P) bridge. Each domain is also capable of supporting a Hot Swap
Controller (HSC) module that contains its own P2P bridge. Thus, in a fully redundant
configuration, there are two bridges that have access to each of the I/O buses — one
associated with the SSP and one with the HSC. Only one of the bridges may be active at
a time.
In a redundant configuration, the CPU in the left system slot of a domain A, SSP A, is
associated with the HSC in the right HSC slot in Domain B bus, HSC A (note that HSC A
actually sits on the Domain B bus). There is a local connection between each SSP-HSC
pair that allows the SSP in one domain to control the other domain through its HSC. This
architecture is illustrated in the following figure.
In addition to providing bridges to the remote I/O buses, the HSC provides the services
necessary to hot swap I/O and SSP boards and also controls the system alarm panel,
fans, and power supplies.
System slot processor

The System Slot board provides arbitration, clock distribution, and reset functions for all
boards on the segment. The System Slot is responsible for performing system
initialization by managing each local board’s IDSEL signal. Physically, the System Slot
may be located at any position in the backplane. The slots allocated for the system slot
processors are located in slots 7 and 9 of the Motorola CPX8216 CPCI cage.

System Layout
Transition modules for rear IO Transition modules for rear IO
H H
S S
C C
B A Rear card
locations
PCI Bus PCI Bus Backplane
Front card
locations
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Non system slots System slots Non system slots
Domain A Domain B
BSS101_Mod1_Ch3_02

System
Configurations
The CPX8216 is a flexible system that allows for multiple configurations of processor
control, I/O redundancy, and peripheral configurations.
System
Processor
Configurations
There are three possible processor/control configurations:
A simplex system containing a single SSP-HSC pair controlling both I/O domains
An active/passive configuration similar to the simplex configuration, but providing a
warm backup for both the SSP and the HSC
An active/active or load–sharing configuration in which each SSP runs a single
domain while also serving as a backup to the other SSP
The Simplex
Configuration
Because of the flexible nature of the CPX8216, it is possible to configure it with different
levels of redundancy and availability. For applications which do not require the benefits of
full high availability, it is possible to configure the CPX8216 as a simplex, 16-slot system.
This configuration provides the benefits of redundant power supplies and the system
monitoring capabilities of the fully redundant configuration.

The Simplex Configuration
H
S
C
A
PCI Bus PCI Bus
S S S S S S S S S S S S S
L L L L L L S L L L L L L
O O O O O O P O O O O O O
T T T T T T A T T T T T T
Domain A Domain B
BSS101_Mod1_Ch3_03

The
Active/Passive
Configuration
In the active/passive configuration, one SSP manages all twelve I/O slots, much like
in the simplex configuration. In addition, the second SSP serves as a warm standby,
ready to run the system in case of a failure on the active system.
The Active/Active
or Load-Sharing
Configuration
The Active /Active configuration is the same as the Active / Passive configuration in
terms of hardware. Though the operation of the host processors is different.
In the load sharing or Active/Active configuration, each SSP manages six of the twelve
I/O slots, much like a dual 8-slot system with the added benefit of one SSP being able to
control all twelve I/O slots if the other SSP fails. It is important in a load-sharing
configuration to note that the total critical activity does not exceed the capabilities of a
single SSP, because either one of the SSPs must be ready to take over the load carried
by the other.

The Active/Passive Configurations
Passive SSP/HSC Active SSP/HSC
H H
S S
C C
B A
PCI Bus PCI Bus
S S S S S S S S S S S S S S
L L L L L L S S L L L L L L
O O O O O O P P O O O O O O
T T T T T T A B T T T T T T
Domain A Domain B
BSS101_Mod1_Ch3_04

Redundancy
The CPX8216 contains 2 independent 8-slot CompactPCI buses. One slot in each bus is
dedicated to a system processor, and another is needed for the HSC. This leaves six
slots on each bus to support I/O devices or non-system processors. One possible
configuration is to use the CPX8216 as a high I/O CompactPCI system with redundant
SSPs. With this configuration, it is possible to run twelve independent I/O modules within
a CPX8216 system. Applications requiring dense processing power could use all twelve
I/O slots to support non–system processors.
Such a system would be protected against a SSP or HSC fault, but it would be
vulnerable to data losses if any of the I/O modules or non-system processor modules
were to fail. In systems handling critical data, it is possible to implement a 2N or an N+1
I/O redundancy strategy that allows the level of service to be continued in the event that
a module fails.
2N Redundancy
In the case of a 2N-redundant system, each I/O module or non–system processor
module is matched with an identical module on the other bus. The paired modules can be
configured in an active/passive arrangement or a load-sharing arrangement in which
each carries half of the load of a single module.
N+1 Redundancy
In an N+1 arrangement, multiple modules are backed up by a single spare. For example,
a single passive non-system processor module can be used to back up five others.

Redundancy
2N redundant system Active/Active or load share
H H
S S
C C
B A
PCI Bus PCI Bus

P P P P P P P P P P P P
r r r r r r r r r r r r
o o o o o o o o o o o o
c c c c c c c c c c c c
e e e e e e e e e e e e
s s s s s s s s s s s s
s s s s s s s s s s s s
o o o o o o S S o o o o o o
r r r r r r S S r r r r r r
1 2 3 4 5 6 P P 1 2 3 4 5 6
a a a a a a A B b b b b b b
Active processors Standby / load sharing

processors
Domain A Domain B
BSS101_Mod1_Ch3_05
N+1 redundancy
H H
S S
C C
B A
PCI Bus PCI Bus

P P P P P B P P P P P B
r r r r r A r r r r r A
o o o o o C o o o o o C
c c c c c c c c c c K
e e e e e K e e e e e
s s s s s s s s s s
s s s s s U s s s s s U
o o o o o P S S o o o o o P
r r r r r r r r r r
S S
1 2 3 4 5 P P 6 7 8 9 1
a a a a a A B a a a a 0
a
Active processors Active processors
Domain A Domain B
BSS101_Mod1_Ch3_05a Back up passive
processors

Power Supply
The fans on the power supplies provide the forced air cooling for the cage. Only two fans
are necessary for adequate system cooling with the third fan providing N+1 cooling
redundancy.
The power distribution panel is located in the rear of the chassis below the transition
module card cage. The panel distributes Ac or DC input power to the system power
supplies. There are two versions of power distribution power supply; AC, and dual input
DC.
Power Supply O/P

Voltage Regulation Minimum Load Maximum Load
+5 V 3% 0.5A 40.0A
+3.3 V 3% 0.5A 40.0A
–12 V 5% 0.3A 8.0A
+12 V 5% 0.3A 4.0A
Power Supply Requirements

Nominal Voltage Voltage Supply Range Maximum Supply Current
Wide ranging ac single 88 to 260 V ac 4.3 amps @ 270 V ac
phase 8.9 amps @ 110 V ac
110 to 230 (nominal) 47 to 63 Hz
50 to 60 Hz
–48/60 V dc –36 to –72 V dc 2.5 amps @ –48 V dc
(positive earth)

Power Supply Sled Units
BSS101_Mod1_Ch3_06

Power
Supplies/Fans
The CPX8216 system requires a minimum of two power/fan units. The Power Supply and
Fan (PSF) unit contains a 350W power supply and a 5” tube axial fan, (fan only units are
available but not available in the Motorola GPRS solution).
5.0 inch tube axial fans together in a sheet metal housing. The system can contain a third
power supply/fan unit as part of an N+1 strategy, meaning that the system can continue
providing service if one of the units fail. These modules are hot swappable and available
for DC and AC supply.
Peripheral bays
It is possible to connect peripherals to the PCI cage. However in the Motorola
implementation no peripherals will be connected to the cage in this manner.

Cage Cooling
Front Boards Rear Boards

(SSP & I/O) (Transition)
Side-to-Side Side-to-Side
Plenum Plenum
Baffle
Filter
BSS101_Mod1_Ch3_07

The SSP Complex

The SSP complex in a CPX8216 cage consists of two SSP modules and their Hot Swap
Controllers. The SSP modules as well as containing processors RAM etc also contain
the following:
Ethernet controller
Serial Comms link
PCI to PCI bridge to local PCI bus
Local PCI bus connection to the Hot Swap Controller in the other domain
The Ethernet and serial connections provide a mechanism for the two SSPs to exchange
data and to maintain a loosely coupled relationship by passing heartbeat and checkpoint
protocols.
The PCI to PCI bridge enables connection to the local PCI bus in that domain for data
transfer between the SSP and cards on the bus.
The Local PCI bus connection to the Hot Swap Controller enables the system slot
processor to control the PCI bus in the other domain.
The HSC module contains the following:
Local PCI bus connection to the System slot processor in the other domain
PCI to PCI bridge to local PCI bus

SSP Complex
Ethernet
Serial link
System slot processor A HSC A HSC B System slot processor B
Special Backplane
PCI Interconnects
(Private PCI bus)
Domain A PCI local bus
Domain B PCI local bus
BSS101_Mod1_Ch3_08

Heartbeat and Checkpoint Protocols VERSION1 REVISION 0
Heartbeat and Checkpoint Protocols
Heartbeat
Protocol
The heartbeat protocol is similar to a watchdog timer. In an active/passive configuration,
the active SSP sends a periodic message to the passive SSP to signal that it is alive
(and presumably well). The passive SSP responds with a simple acknowledgment.
The heartbeat signal can be passed through the Ethernet connection or through the
serial communications link as a secondary channel. Either physical channel can be
chosen to be the primary heartbeat channel, with occasional “beats” being sent through
the secondary channel to check for latent faults on that channel.
If the secondary SSP fails to receive a heartbeat on the primary channel, then it
assumes that the primary link has failed and switches to the secondary channel. When
the active SSP fails to receive acknowledgments on the primary link, it begins to send the
heartbeat message on the secondary channel. If the passive SSP does not receive a
beat on the secondary channel, then it will assume the active SSP has failed, and it will
become the active SSP.
Checkpoint
Protocol
The checkpoint protocol allows for a block of memory to be copied from an active
resource to the corresponding passive resource. It provides a snapshot of the application
or system program state data. This means that in the event of an active SSP failure, the
passive SSP is able to begin service in nearly the same state as the state the active SSP
failed in. The checkpoint protocol uses the same physical links as the heartbeat protocol.
Switching
Service to the
Passive SSP
The switchover from one SSP to another is initiated by the passive SSP when there is an
indication that there is something wrong with the active SSP – such as a failed heartbeat
protocol. The passive side notifies the active side that it is about to begin a switchover
process. If the active side agrees to the switchover, then the two sides coordinate the
hand-off and no bus signals, clocks, or devices should be corrupted. If the active system
fails to cooperate with the takeover attempt, then we must assume that bus signals,
clocks, and devices attached to the bus may be corrupted. It is also possible for the
passive SSP to power–on reset the active SSP and takes control.

VERSION1 REVISION 0 Heartbeat and Checkpoint Protocols
Heartbeat and Checkpoint Protocols
Heartbeat Protocol Checkpoint Protocol
Ethernet/ Ethernet/
TextSSP
Active serial TextSSP
Active serial
link link
Block of memory Shopping list

TICK (program state, Meat
Passive SSP data etc) Bread Passive SSP
Milk
Active SSP
Active SSP
NO TICK
Passive SSP assumes

control of the PCI Becomes Active SSP
buses in both Ok, Get next item from
domains. shopping list
Becomes Active SSP i.e. Bread
BSS101_Mod1_Ch3_09
BSS101_Mod1_Ch3_09a

Hot Swapping VERSION1 REVISION 0
Hot Swapping
The Hot Swap

Controller/Bridge
(HSC) Module
The HSC connects to the SSP module through a local PCI bus.
The HSC contains a PCI-to-PCI bridge and a Hot Swap Controller.
The functionality provided by the HSC is at the heart of the High Availability CPX8216
System. The primary functions of the HSC include:
Providing a bridge between the two eight-slot CompactPCI buses so that they can
be managed by a single SSP module
Maintaining a Control Status Register which contains information on the status of
each module
Controlling power and resets to each module through radial connections
Monitoring and controlling peripherals, including power and fan sleds, board and
system LED’s, and alarms
The board is programmed by the system through configuration space for both the PCI
bridge and the HSC. The HSC has a register entry for each device in the cage regardless
of Domain as well as power supplies and peripheral bays if they were installed. However
only the HSC that owns domain A will control the power supplies as it is domain A that
becomes the master during power up.
Hot Swap Control

Status Register
(CSR)
The CPX8216 supports hot swap CompactPCI cards with the standard control status
register defined by the PICMG Hot Swap Specification. The register is visible in PCI
configuration space and provides hot swap control and status bits: INS and EXT. The
INS signal is set when ENUM# is asserted by a board being inserted into the system.
The EXT signal is asserted when ENUM# is asserted by an operator triggering the
micro-switch in the board handles. The host also uses these bits to acknowledge and
de-assert ENUM#.

VERSION1 REVISION 0 Hot Swapping
Hot Swap Controller
HSC
Private PCI bus
PCI
Module
PCI backplane
controller
control signals
(resets etc)
Private PCI to
System processor
PCI
module
Status
register
PCI to PCI bridge

Peripheral
control
PCI bus to cage

backplane
BSS101_Mod1_Ch3_10

Board Insertion and Extraction Features VERSION1 REVISION 0
Board Insertion and Extraction Features

The PICMG specification details software and hardware features, in order to support hot
swapping of I/O boards. Hardware features include:
Staged pins that control voltages when inserting or extracting boards
BD_SEL#, HEALTHY#, and ENUM# signals
Hot swap control status register (on HSC)
Staged Pins
The PICMG CompactPCI hot swap specification provides for three separate pin lengths
in order to control the insertion and extraction voltages and to notify the system when
boards are inserted or extracted. The longest pins, which include VCC pins and GND
pins, are the first to mate during the insertion process and the last to break contact
during extraction. These pins are used to supply power to pre-charge the PCI interface
signals to a neutral state before they contact the bus. This pre–charging serves to
minimize the capacitive effects of the board as it makes or breaks contact with the bus.
The medium–length pins carry PCI and other signal traffic. The shortest pins are used to
assert signals, including BD_SEL#. During insertion, the BD_SEL# signal enables the
board to attach to the local PCI bus. On extraction, it causes the board to disconnect
both logically and electrically from the PCI bus, before the bus pins physically break
contact with the bus.
BD_SEL#
BD_SEL# is asserted by one of the pins that mate last on insertion and break first on
extraction. On insertion, the signal tells the board to connect to the PCI bus. On
extraction this pin breaks first, causing the board to disconnect both logically and
electrically from the PCI bus before the PCI bus pins physically break contact with the
bus.
ENUM#
An ENUM interrupt is generated when a board is hot inserted into the CPX8216 chassis,
or when an operator trips the board microswitch by raising its ejector handles. The signal
informs the active SSP that the status of a board has changed. The SSP then identifies
the board by polling the INSert and EXTract bits in all of the boards’ Control Status
Registers.

VERSION1 REVISION 0 Board Insertion and Extraction Features
Staged Pins
VCC
These longest pins pre–
charge the PCI pins
GND
PCI traffic
Signal traffic
BD_SEL# being the short

pin disconnects/connects BD_SEL#
from/to the backplane last
BSS101_Mod1_Ch3_11

The Hot Swap

Process
PICMG divided the complete hot swap process into physical, hardware and software
connection processes. These processes are formally broken down further into a group of
transitional states
When inserting a board, it goes through all states from P0 to S3. Conversely, a board
transitions from S3 to P0 before being extracted. During normal operation, no states are
skipped. If a board is extracted whilst in a software connection state, (other than S0) a
software to crash is likely. However the CompactPCI bus, from a purely electrical point of
view, will not be disrupted enough to cause logic levels to be violated.
Certain states are overlapping. For example, when the board is fully seated (completed
P1), but has not yet started the hardware connection process (H0), it said to be in the
P1/H0 state. Similarly, one can speak of a board being in the H2/S0 state.
P0 – The board is physically separate from the system
P1 – The board is fully seated, but not powered, and not active on the PCI bus. All
pins are connected.
H0 – The board is not active on the PCI bus. This state is equivalent to P1.
H1 – The board has powered up and has sufficiently initialized to connect to the
PCI bus.
H2 – The board is powered, and enabled for access by a PCI bus transaction
(normally by the host) in PCI configuration space only. The board configuration
space is not yet initialized.
S0 – The Software Connection Process has not been initiated. The board’s
configuration space registers are accessible but not yet initialized.
S1 – The board is configured by the system. The system has initialized the board’s
PCI configuration space registers with I/O space, memory space, interrupts and
PCI bus numbers. The board is ready to be accessed by a device driver, but no
drivers are loaded at this time.
S2 – The necessary supporting software (drivers, etc.) have been loaded. The
board is ready for use by the OS and/or the application, but no operation involving
the board is active or pending.
S3 – The board is active. Software operations are either active or pending.

Connection States
Physical Hardware Software

Connection Connection Connection
States States states
P0 P1
H0 H1 H2
S0 S1 S2 S3
BSS101_Mod1_Ch3_12

Compact PCI
Backplane
CompactPCI defines a backplane environment that has up to eight boards, as per the
Motorola CPCI cage domain. One slot, the System Slot, provides the clocking,
arbitration, configuration, and interrupt processing for the other seven slots. Backplanes
provide separate power planes for 3.3V, 5V, and ground.
Transition Modules
Each slot in each domain has direct connections through the backplane to its respective
transition module. The CPX8216 cage supports transition modules, which allows I/O
connectivity from the rear of the cage rather than the front. Connection to PMC modules
can then be made at the rear of the cage by use of the appropriate transition module. It is
possible to use a generic transition module on which two PMC Interface modules
(specific to the PMC card) can be mounted.

Sample PCI Card and Connectors
Chassis Backplane
I/O card Transition

module
Processor Transition
Module Module
BSS101_Mod1_Ch3_13

Bus Connectors/
Signals
CompactPCI bus segments bus all signals in all slots within the segment except the slot
specific signals: CLK, REQ# and GNT#. Each logical slot also has a unique
IDSEL signal connected to one of the upper A/D signals for decoding.
J1 Connector – CompactPCI board connector J1 is used for the 32-bit PCI signals.
32–bit boards always use this connector. Use of the J2 connector is optional.
J2 Connector – J2 can be used for 64-bit PCI transfers or for rear-panel I/O. J2 is used
on System Slot boards to provide arbitration and clock signals for peripheral boards.
J3 through J5 Connectors – J3 through J5 are available in 6U systems for application
use. Applications include rear-panel I/O, bused signals or custom use.
CompactPCI
Signal Additions
CompactPCI defines some additional signals beyond the PCI specification. These signals
are Push Button Reset (PRST#), Power Supply Status (DEG#, FAL#), System Slot
Identification (SYSEN#) and System Enumeration (ENUM#) these are supported in the
CPX8216 CPCI cage.
IDSEL
Assignment
The PCI signal IDSEL is used to provide unique access to each logical slot for
configuration purposes. By connecting one of the address lines AD31 through AD25 to
each board’s IDSEL pin (P1, B9), a unique address for each board is provided during
configuration cycles.

Pin Layout of J1 J2 Connector in System Slot (7,9)
POS Row Z Row A Row B Row C Row D Row E Row F
22 GND GA4 GA3 GA2 GA1 GA0 GND

21
20
GND
GND
CLK16
CLK15
GND
GND
RSV
RSV
RSV
GND
RSV
RSV
GND J
19 GND GND GND RSV RSV RSV GND
18 GND _BRSVP2A1 _BRSVP2B1 _BRSVP2C1 GND _BRSVP2E18 GND 2
8 8 8
17 GND _BRSVP2A1 GND _PRST# _REQ16# GNT16# GND
7
16 GND _BRSVP2A1 _BRSVP2B1 _DEG# GND _BRSVP2E16 GND
6 6
15 GND _BRSVP2A1 GND _FAL# REQ15# GNT15# GND
5
14 GND _AD[35] _AD[34] _AD[33] GND _AD[32] GND
13 GND _AD[38] GND VIO _AD[37] _AD[36] GND
5 GND _C/BE[5]# GND VIO C/BE[4]# _PAR64 GND
4 GND VIO _BRSVP2B4 _C/BE[7]# GND _C/BE[6] GND
3 GND CLK4 GND GNT3# REQ4# GNT4# GND
2 GND CLK2 CLK3 _SYSEN# GNT2# REQ3# GND
1 GND CLK1 GND REQ11# GNT1# REQ2# GND
25 GND 5V A _REQ64# _ENUM# 3.3V 5V GND
24 GND _AD[1] 5V VIO _AD[0] _ACK64# GND J
23 GND 3.3V _AD[4] _AD[3] 5V _AD[2] GND
22
21
GND
GND
_AD[7]
3.3V
GND
_AD[9]
3.3V
_AD[8]
_AD[6]
_M66EN
_AD[5]
_C/BE[0]#
GND
GND
1
19 GND 3.3V _AD[15] _AD[14] GND _AD[13] GND
18 GND _SERR# GND 3.3V _PAR _C/BE[1] GND
17 GND 3.3V _SDONE _SBO# GND _PERR# GND
16 GND _DEVSEL# GND VIO _STOP# _LOCK# GND
15 GND 3.3V _FRAME# _IRDY# BD _SEL[n]# _TRDY# GND
14 Key Area
13
12
11 GND _AD[18} _AD[17] _AD[16] GND _C/BE[2]# GND
10 GND _AD[21] GND 3.3V _AD[20] _AD[19] GND
9 GND _C/BE[3] _IDSEL _AD[23] GND _AD[22] GND
6 GND (REQ#) GND 3.3V (CLK) _AD[31] GND
5 GND _BRSVP1A5 _BRSVP1B5 RST[N]# GND (GNT#) GND
4 GND _BRSVP1A HLTY[N]# VIO _INTP _INTS GND
4
3 GND _INTA# _INTB# _INTC# 5V _INTD# GND
2 GND TCK 5V TMS TDO TDI GND
1 GND 5V plus-minus 12V TRST# +12V 5V GND
BSS101_Mod1_Ch3_14

REQ#/GNT#
Assignment
The System Slot interfaces to seven pairs of REQ/GNT pins called REQ0-REQ6 and
GNT0-GNT6. Each board slot interfaces to one pair of REQ/GNT signals using pins
called REQ and GNT. The System Slot on either backplane segment supports the full
complement of REQ/GNT signals.
PCI Clock
Distribution
The System Slot board provides clock signals for all PCI peripherals in the system,
including devices on the System Slot board. Peripheral boards are provided clock signals
via the CompactPCI backplane.

Pin Layout of J1 J2 connector in System Slot (7,9)
POS Row Z Row A Row B Row C Row D Row E Row F
22 GND GA4 GA3 GA2 GA1 GA0 GND

21
20
GND
GND
CLK16
CLK15
GND
GND
RSV
RSV
RSV
GND
RSV
RSV
GND
J
19 GND GND GND RSV RSV RSV GND
18 GND _BRSVP2A1 _BRSVP2B1 _BRSVP2C1 GND _BRSVP2E18 GND 2
8 8 8
17 GND _BRSVP2A1 GND _PRST# _REQ16# GNT16# GND
7
16 GND _BRSVP2A1 _BRSVP2B1 _DEG# GND _BRSVP2E16 GND
6 6
15 GND _BRSVP2A1 GND _FAL# REQ15# GNT15# GND
5
5 GND _C/BE[5]# GND VIO C/BE[4]# _PAR64 GND
4 GND VIO _BRSVP2B4 _C/BE[7]# GND _C/BE[6] GND
3 GND CLK4 GND GNT3# REQ4# GNT4# GND
2 GND CLK2 CLK3 _SYSEN# GNT2# REQ3# GND
1 GND CLK1 GND REQ11# GNT1# REQ2# GND
25 GND 5V A _REQ64# _ENUM# 3.3V 5V GND
24 GND _AD[1] 5V VIO _AD[0] _ACK64# GND J
23 GND 3.3V _AD[4] _AD[3] 5V _AD[2] GND
22
21
GND
GND
_AD[7]
3.3V
GND
_AD[9]
3.3V
_AD[8]
_AD[6]
_M66EN
_AD[5]
_C/BE[0]#
GND
GND
1
20 GND _AD[12] GND VIO _AD[1 1] _AD[10] GND
19 GND 3.3V _AD[15] _AD[14] GND _AD[13] GND
18 GND _SERR# GND 3.3V _PAR _C/BE[1] GND
17 GND 3.3V _SDONE _SBO# GND _PERR# GND
16 GND _DEVSEL# GND VIO _STOP# _LOCK# GND
15 GND 3.3V _FRAME# _IRDY# BD _SEL[n]# _TRDY# GND
14 Key Area
13
12
11 GND _AD[18} _AD[17] _AD[16] GND _C/BE[2]# GND
10 GND _AD[21] GND 3.3V _AD[20] _AD[19] GND
9 GND _C/BE[3] _IDSEL _AD[23] GND _AD[22] GND
6 GND (REQ#) GND 3.3V (CLK) _AD[31] GND
5 GND _BRSVP1A5 _BRSVP1B5 RST[N]# GND (GNT#) GND
4 GND _BRSVP1A HLTY[N]# VIO _INTP _INTS GND
4
3 GND _INTA# _INTB# _INTC# 5V _INTD# GND
2 GND TCK 5V TMS TDO TDI GND
1 GND 5V plus-minus 12V TRST# +12V 5V GND
BSS101_Mod1_Ch3_15

Replacing Modules VERSION1 REVISION 0
Replacing Modules
Condition for
Replacing
Modules
Replacing a digital module will interrupt traffic interfacing through the removed module.
The replacement of a module can only take place after the module is taken out of
service.
Hot swap modules can be removed and refitted without removing the system power.
Make sure that the board manufacturer identifies the module as hot swap capable.
ESD
Handling modules and peripherals can result in static damage.
Use a grounded wrist strap, static-dissipating work surface, and anti-static bags when
handling and storing components.
An earthing wrist strap must be worn when handling electronic modules, including the
System slot processors and non-system slot processors, Transition modules and PCI to
PCI bridge modules.
ESD earthing connection points are provided:
Adjacent to the right fan/power supply sled.
Above and to the left of the rear card cage.
Removing a Hot
Swap Module
To remove a hot swap digital module perform the following steps:
First ensure that the module has been taken out of service.
Disconnect any interface cables from the connectors on the face of the module.
Loosen the two captive screws, (one at each end of the module).
Press the ejector levers outward. This partially unseats the module from the
backplane connectors. DO NOT pull the module from the slot at this point.
Make sure the blue LED on the front of the hot swap module is lit before beginning
to withdraw the module from the chassis. Once lit, the module can be removed.
Pull the module from the chassis.

VERSION1 REVISION 0 Replacing Modules
Diagram of Removing a Hot Swap Module
BSS101_Mod1_Ch3_16

Installing a Hot
Swap Module
To fit a Hot-Swap Module perform the following steps:
Visually check for any bent or damaged pins.
Press the ejector levers outward. Insert the board by holding the ejector levers do
not insert the board by pushing on the faceplate of the board.
Slide the module slowly into the slot until the ejector levers contact the chassis
rails.
Use the ejector levers to seat the board in the slot by closing the levers towards
one another until they are in the horizontal locked position.
Secure the board by tightening the captive screws at the top and bottom of the
panel.
Reconnect any interface cables to the connectors on the face of the module.
Non Hot Swap

Module
If a unit is not Hot Swap then removal and replacement of the board should only be done
when the power to the CPCI cage has been removed. The electrical status of the PCI
bus cannot be otherwise guaranteed and damage may occur to the card and bus.
Otherwise the replacement would be the same as the Hot Swap modules, (except for the
blue LED). Once the card is installed and secure, power can be re-applied to the cage.

VERSION1 REVISION 0 Replacing Modules
Diagram of Installing a Hot Swap Module
BSS101_Mod1_Ch3_17


Chapter 4
CPCI Digital Cards

VERSION1 REVISION 0

VERSION1 REVISION 0
Chapter 4
CPCI Digital Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
MCP 750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
MCP 750 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Peripheral Mezzanine Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Hot Swap Controller/Bridge Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Bridge board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Alarm module overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Alarm Panel LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Alarm board Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12

VERSION1 REVISION 0

State the operation of the MCP750.
State the operation of Mezzanine modules.
State the operation of HSC Bridge.
State the operation of Alarm module.

MCP 750 VERSION1 REVISION 0
MCP 750
The MCP750 is the Motorola System slot processor used in the PCU and the SGSN.
Board Mounted Connectors

Debug Connector
Memory Mezzanine Card connections
PCI Mezzanine Card – PMC Slot with front panel I/O and rear panel user I/O connections
Front Panel I/O

Dual USB ports on front and back panels
Ethernet 10BaseT/100BaseTx on RJ–45 on front panel
COM1 on front panel, DB9
Status LED’s
RESET and ABORT switches
Rear Panel I/O

IDE Expansion on back panel
CompactPCI J1/J2 – CompactPCI Bus
CompactPCI J4/J5
CompactPCI User I/O J3
Local Bus expansion J4
User I/O J5
Dual USB ports on front and back panels
COM2 port on back panel
COM3 and COM4 SYNC/ASYNC on back panel
Compact (IDE) FLASH/DRAM

The Compact FLASH memory card mounts on the MCP750 baseboard, under the
RAM300 memory mezzanine.
RAM300 Card
The RAM300 DRAM mezzanine card mounts on top of the MCP750 base board.
PCI Mezzanine Card (PMC)

PCI mezzanine card (PMC) modules mount beside the RAM300 mezzanine on top of the
MCP750 baseboard. Usually used for I/O (it could be another processor!).
Transition Module
The transition module plugs into the rear of the CompactPCI backplane. It provides rear
panel I/O and other features. Some special features may place certain requirements on
the backplane, such as providing a full set of connectors on both sides.

VERSION1 REVISION 0 MCP 750
Diagram of MCP 750
BSS101_Mod1_Ch4_1

MCP 750 Features VERSION1 REVISION 0
MCP 750 Features

Falcon Memory Controller
The Falcon memory controller consists of two identical Falcon ASICs controlling 144-bit
wide DRAM. Each device controls 64-bits of data and an additional 8-bits of ECC check
word. The ECC protection allows correction of single bit errors in a 64–bit field, and
detection of 2–bit errors.
Falcon also controls two banks of FLASH memory and system registers that provide
board configuration information. FLASH and system registers are not ECC protected.
Configuration NVRAM is located on the ISA bus and is not controlled by the Falcon
chipset.
Raven MPC-to-PCI Bridge

The Raven ASIC bridges the PowerPC host bus with the PCI bus. It provides four
memory–mapping windows in each direction between the buses. The Raven contains the
Multi–Processor Interrupt Controller (MPIC) used for routing interrupts from board
devices to the processor.
Peripheral Bus Controller (PBC)

The PBC is a commercial off–the–shelf device providing ISA, IDE, and USB access from
the PCI bus. PBC (PCI Peripheral Bus Controller)
This bridge is a VT82C586 from VIA Technologies. This bridge is the South Bridge part of
chipsets made for various Pentium processors.
PCI–to–PCI Bridge
The 21154 PCI to PCI bridge connects the on–board PCI bus with the CompactPCI
backplane. This bridge uses standard transparent bridging technology as specified by the
PCI Special Interest Group.
Arbitration
MPC bus arbitration and PCI bus arbitration is handled by hardware on the board.
Ethernet
10BaseT/100BaseTx automatically selected. In the PCU this port is for use with web
based MMI.
Super I/O
Provides two asynchronous serial ports, keyboard, mouse, floppy drive, and parallel port.
The device is a PC87307 from National Semiconductor. This device is used in many
Pentium based systems.

VERSION1 REVISION 0 MCP 750 Features
Block Diagram of MCP 750
DEBUG CONNECTOR FLASH / DRAM EXPANSION CONNECTORS
66MHz MPC604 PROCESSOR BUS FLASH

1MB
L2 CACHE
256K–1M MEMORY
CONTROLLER
FALCON CHIPSET SYSTEM
REGISTERS
PROCESSOR
MPC750
RESET
CONTROL
RAVEN ASIC
BRIDGE CLOCK
32/64–BIT PMC SLOT
ARBITRATION
CONTROL GENERATOR
33MHz 32/64–BIT PCI LOCAL BUS
ETHERNET PBC PCI–PCI BRIDGE

DEC21140 VT82C586B DEC21154
ETHERNET
SROM
10BT/ AT24C04
100BTX
Front Panel I/O
ISA
USB1
IDE
REGÕS
USB0
ISA
USB
33MHz 32/64–BIT PCI BUS
RTC/
NVRAM/
33MHz 32 BIT
WD
SERIAL USB
MK48T559
SUPER I/O
PC87307
ESCC CIO
85230 Z8536
FRONT PANEL
FLOPPY DISK
PMC SLOT
KEYBOARD
2 SYNC/ASYNC
PARALLEL
Compact
MOUSE
SERIAL
FLASH
USER I/O J3 & J5 J4 J1 / J2
BSS101_Mod1_Ch4_2

Peripheral Mezzanine Card VERSION1 REVISION 0
Peripheral Mezzanine Card

The Peripheral Mezzanine Card, (PMC) is a daughter board which sits on a main
processor board in the either the PCU or the SGSN. The Processor boards used in the
CPCI cages are capable of having 2 PMC modules mounted on them.
Mezzanine cards provide the flexibility to add a variety of I/O functions to the host
computer board. This means E1 links can be added into the system.
The basic mezzanine card width is 75 mm by 150 mm deep with a 10 mm stacking
height above the host based PCB.
Several standards are used to specify the mezzanine cards. The parent standard, called
Common Mezzanine Card (CMC), IEEE P1386, defines the complete mechanics for both
the mezzanine cards and the host’s mechanical interface.
Two mezzanine card sizes are defined:
Single: 75 mm by 150 mm
Double: 150 mm by 150 mm
The PMC used to mount onto the Host processors in the PCU or SGSN are of the Single
type and the actual size is:
Width: 148.8 mm Depth 74mm Height 10mm

VERSION1 REVISION 0 Peripheral Mezzanine Card
PCI Mezzanine Card
BSS101_Mod1_Ch4_3a
PCI Mezzanine Card Location
J
5
PMC
Module
J
4
J Connection
3 for rear I/O
2 x E1 Links &
J Console ports
2
PMC
Module
J
1
BSS101_Mod1_Ch4_3b

Hot Swap Controller/Bridge Module VERSION1 REVISION 0
Hot Swap Controller/Bridge Module
Bridge
The Bridge known as the HSC/Bridge allows a system slot processor to be linked to a
separate bus. This enables PCI domain expansion. The HSC/Bridge and system slot
processor are paired boards.
Bridge board
The HSC/Bridge board allows the redundant operation of the system host PROC board,
and gives the host PROC access to all boards in the system.
HSC
It supports control of hotswap for all boards and a communication link between bridge
boards to allow check pointing and heartbeat messages between system slot processor
boards. This allows migration to a fully hot swap, redundant high availability system,
including hot standby/load sharing between system slot processors in the future if
required.

VERSION1 REVISION 0 Hot Swap Controller/Bridge Module
Diagram of HSC/Bridge Module
BSS101_Mod1_Ch4_6

Alarm Module VERSION1 REVISION 0
Alarm Module
Alarm module
overview
The Alarm module provides LED’s and alarms for the system. The purpose of the
separate alarm board is to provide a standard appearance for the LED’s without relying
on individual boards. The Alarm board runs across the top of the chassis. In addition to In
Service/Out of Service LED indicators for all sixteen slots, the alarm board contains
LED’s for system status (System in Service/Component out of Service/System out of
Service) and for the three standard Telco levels (Critical/Major/Minor). The three Telco
alarms are also signalled through a dry contact relay and available through a RJ–45
connector.
It is powered and controlled from each of the two Hot Swap Controllers within the
system. Normally, only two of the three-slot status LED’s are visible – the third is
covered by the alarm board overlay.
The module is a field replaceable unit (FRU). The module is hot swappable and is
mounted on the front of the system chassis, a ribbon cable connects the alarm module to
the backplane.
Alarm Panel
LED’s
Bits in the Hot Swap Controller’s register control the alarm panel LED’s. The system
software sets the bits in the register. This allows the alarms and LED’s to be tailored for
the Motorola GPRS solution for alarm event reporting.
The table below provides the colour and standard nomenclature for the LED’s on the
alarm panel.
Alarm LED Colour Description

Controller Board Slot Status Green In Service
Yellow N/A (or Out of Service)
Red Out of Service
System
y Status Green System In Service
Yellow Component Out of service
Red System Out of Service
Telco Status Yellow Minor
Red Major
Red Critical

VERSION1 REVISION 0 Alarm Module
Alarm panel LEDs
SYSTEM SYSTEM COMPONENT TELCO ALARM

COMPONENT MINOR MAJOR CRITICAL
STATUS IN SERVICE OUT OF SERVICE STATUS CONNECTION
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BSS101_Mod1_Ch4_8

Alarm board
Operation
The Alarm board is under control of one of the HSC. As such it is an extension of the
HSC register set. The address of the alarm register will be an offset from the base
address of the HSC. The setting and clearing of alarms and LED’s are under software
control and by the act of the system writing to the correct registers in the HSC the
appropriate alarm / LED will be activated on the Alarm board.
The alarm board connects to the HSC via a serial link. The serial link consists of a clock,
data input, data output and a frame signal. The frame signal is used to indicate that data
is active. The clock runs at 16 kHz. The link is duplex and serial up / down information is
transferred at the same time.
The PLD acts as 2 state machines. One for Domain A and One for Domain B. The two
state machines operate independently from one another. Domain logic controls the LED’s
for slots 1 to 8 and Domain B logic controls the LED’s for slots 9 to 16. Domain A also
controls the system status LED’s.

VERSION1 REVISION 0 Alarm Module
Alarm Board Block Diagram
Telco
System
Relays
Alarm
LED’s
Conn
Digital Inputs
ALARM
PLD System LED’s
Slot 1 LED’s
PWR A REG
Domain A
PWR B
Logic Slot 2 LED’s
GND
HSC IFC CONN
Clock and Data A
Slot 6 LED’s
Clock and Data B Slot 11 LED’s
Domain B
Logic
Slot 16 LED’s
BSS101_Mod1_Ch4_9


CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
PCU IN GPRS PCU HARDWARE DIGITAL CARDS FOR PCU PCU SOFTWARE PCU INSTALLATION
PROCESSES

VERSION 1 REVISION 0
BSS101/GSR5.1
Module 3: PCU Operations and
Maintenance
Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000

All Rights Reserved
Printed in the U.K.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance i

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 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

Module 3 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter 1
PCU in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
GPRS Data Stream (GDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Radio Link Control /Media access Control (RLC/MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
RLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
MAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Timeslot allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Hierarchical position of the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Functionality of the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Chapter 2
PCU Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
PCU Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Static frame cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Swing frame cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Swing frame functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Introduction to specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Safety, EMC and environmental requirement specifications . . . . . . . . . . . . . . . . . 2–8
Environmental limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Access control specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Physical dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Cabinet input power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Power consumption (ac and dc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Introduction to E1 interface connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
E1 interface panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Chapter 3
Digital Cards for PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
MPROC (Master Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
HSC/Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Digital Processor DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Packet Interface Control Processor (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Packet Resource Processor (PRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
DPROC (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance iii

DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
PCI to PCI Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Ethernet Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
PMC slots 1and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Front Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
NIB (Network Interface Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
NIB overview (E1 PMC module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
I/O through the Backplane: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
RAM/ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
PCI Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Transition module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
E1 transition module functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Chapter 4
PCU Software Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Packet Interface Control Processor (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Functional Units (FU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Frame relay FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GB FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
LAPD FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
TRAU FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
STATUS FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
I/O FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Packet Resource Processor (PRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Packet scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Access Grant, Sys Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
RLC seg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
PRP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Uplink Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Timeslot Resource Shifter (TRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
PCU System Processor (PSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
GB FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Gateway manager FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
I/O FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
PSP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Base Station Sub–System Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Gb Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Gb Router (GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Gateway Transmit Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Network Service Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Flow Control Buffer Manager (FBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
iv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

Fault detection and handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20

System Audit Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
PCU Central Authority (pCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Chapter 5
PCU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
PCU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Installing the PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Introduction to cabinet installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Adjusting cabinet feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Top supporting bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Mounting the PCU in a cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Options for mounting the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Safety considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Fitting the cable guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Fitting a PCU into a cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Mounting a PCU in a static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Mounting a PCU in a swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Fitting E1 interface panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
E1 interface panel options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Static frame cabinet E1 interface panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Swing frame cabinet E1 interface panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Swing frame cabinet E1 interface panel procedures . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Connecting the E1 cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
T43 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
BIB connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Connecting the digital interface cable loom to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Introduction to digital loom connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
GDS links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Gb links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Default GSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Digital cable connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
Static frame cabinet digital cable connection procedure . . . . . . . . . . . . . . . . . . . . . 5–18
Swing frame cabinet digital cable connection procedures . . . . . . . . . . . . . . . . . . . 5–18
Fitting power input switches and mounting panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Power input switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Power input switching options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet ac option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet dc option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Swing frame cabinet option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Fitting ac power input switches to static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Fitting dc power input switches to static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Swing frame cabinet power input switch mounting panel . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Fitting power input switches to swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . 5–26
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance v

Swing frame power input cable routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28

Earthing and transient protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Site earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Transient protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Cabinet earth bar connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32
Connecting external dc power cables to the cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Connection procedure for supplied dc power cable . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Connecting external ac power cables to the cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
External ac cable routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Connection procedure for ac detachable power supply cord/appliance coupler . 5–36
Connecting to external power source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Connecting dc power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Connecting ac Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Powering up the Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Power up procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Routine maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Cleaning fan filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Post maintenance return to service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Field replaceable units (FRUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
A ......................................................................... iv
B ......................................................................... vii
C ......................................................................... x
D ......................................................................... xiv
E ......................................................................... xvii
F ......................................................................... xix
G ......................................................................... xxi
H ......................................................................... xxiii
I .......................................................................... xxiv
K ......................................................................... xxvi
L ......................................................................... xxvii
M ......................................................................... xxix
N ......................................................................... xxxiii
O ......................................................................... xxxv
P ......................................................................... xxxvii
Q ......................................................................... xl
R ......................................................................... xli
S ......................................................................... xliv
T ......................................................................... xlviii
U ......................................................................... li
V ......................................................................... lii
vi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

W . ....................................................................... liii
X ......................................................................... liv
Z ......................................................................... lv
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance vii

viii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 Module 3 Objectives
Module 3 Objectives
At the end of this module the student will be able to:
State the operation of the PCU in GPRS
Identify the cabinet components
State the operation of the PCU specific digital modules
State the operation of the PCU software
Install a PCU

Module 3 Objectives VERSION 1 REVISION 0

Chapter 1
PCU in GPRS


Chapter 1
PCU in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
GPRS Data Stream (GDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Radio Link Control /Media access Control (RLC/MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
RLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
MAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Timeslot allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Hierarchical position of the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Functionality of the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10


VERSION 1 REVISION 0 Chapter 1 Objectives
State the function of the PCU in GPRS
State the function of the RLC /MAC block
Show how data is routed through GPRS
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance 1–1

Packet Control Unit (PCU) VERSION 1 REVISION 0
Packet Control Unit (PCU)

The new BSS functionality for GPRS mainly resides at the Packet Controller Unit (PCU).
The PCU includes the handling of frame relay, Network Services Signalling, BSSGP
signalling, routing of signalling messages, Radio Link Control (RLC) and Media Access
Control (MAC) preload and transferring of user data.
User data is routed to the PCU via the CCU uplink from the BTS to the BSC and then
over E1 to the PCU. At the PCU the RLC Blocks are reformulated in Logical Link Control
(LLC) frames and forwarded to the SGSN.
BSSGP signalling and NS signalling shall occur between the PCU and the SGSN using
frame relay protocol. There is also signalling between existing functional process at the
BSC such as the BSP and the PCU via the E1 Span, as well as between the PCU and
Channel Coders.
GPRS Data
Stream (GDS)
The GPRS Data Stream device refers to the traffic route between the PCU and the BSC.
This is a E1 connection between a BSC MMS and a PCU MMS. The GPRS Data
Stream (GDS) may or may not have an associated GPRS Signalling Link (GSL).
A maximum of 12 GDSs may be equipped and to allow default connectivity for code
download for the PCU a GDS must be equipped and GSL equipped to the GDS (LAPD)
of either:
Timeslot 1 of link 0 of an E1–PMC Module in PMC Socket 1 of a PICP in Slot 1
Timeslot 1 of link 0 of an E1–PMC module in PMC Socket 1 of a PICP in Slot 2
1–2 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 Packet Control Unit (PCU)
GPRS Data Stream
SGSN
NS – SIG
BSSGP SIG
GSL
BSC PCU
GDS
RSL
RTF
BTS
BSS101_M3Ch1_1

Radio Link Control /Media access Control (RLC/MAC) VERSION 1 REVISION 0
Radio Link Control /Media access Control (RLC/MAC)

RLC/MAC is the layer 2 Protocol that operates between the MS and the BSS. RLC/MAC
Protocol is a subset of Radio Resources.
The RLC/MAC protocol can operate in two modes, acknowledged and unacknowledged.
RLC
The RLC function defines the procedures for segmentation of LLC PDUs when the entity
is sending and re–assembly of LLC PDUs when the entity is receiving. When operating in
acknowledged mode the RLC function provides the Backward Error Correction function
for selective re–transmission of RLC/MAC blocks. Acknowledged mode also preserves
the order of the higher layer PDUs provided to RLC.
MAC
The MAC function defines the procedure that enables multiple mobile stations to share a
common transmission medium, which may consist of several physical channels. For
example, when two mobiles are utilising the same frequency and timeslot for data
transfer. The MAC function provides the facility for a mobile to use several physical
channels in parallel. For example, a mobile uses one frequency but two timeslots within
the same TDMA frame. MAC also provides contention resolution for mobile originating
access and queuing/ scheduling of access requests for mobile terminated access.

VERSION 1 REVISION 0 Radio Link Control /Media access Control (RLC/MAC)
Radio Link Control (RLC)
LLC LLC
RLC RLC
MAC MAC
Physical Physical
Layer Layer
FH Information Field FCS

LLC
BH Info Field BCS BH Info Field BCS BH Info Field BCS RLC/MAC
Normal Normal Normal Normal Physical

Burst Burst Burst Burst Layer
BSS101_M3Ch1_2

Timeslot allocation VERSION 1 REVISION 0
Timeslot allocation
With the introduction of GPRS, the configuration of Air Interface timeslots has changed.
The BTS must deal with formatting the Trau data received from the PCU into normal
burst for transmission over the Air interface, (including the correct coding scheme!)
In GSM voice traffic, for every Air interface timeslot there are resources for backhaul to
the BSC. This is also the case for GPRS though the link now exists between the BTS
and PCU, for the air interface timeslots designated as GPRS.
The Air Interface timeslots now have two further configurations. In standard GSM, the
timeslots can be configured as BCCH, SDCCH or TCH. For GPRS, timeslots can be
reserved for use only by GPRS, (RES). Timeslots can also be switchable with GSM voice
traffic always taking priority (SW). This should not pose a problem for GPRS mobiles as
mobiles in current data transfer could be allocated new resources on a different GPRS
timeslot or fewer resources, multiplexing GPRS mobiles onto the same air timeslots.

VERSION 1 REVISION 0 Timeslot allocation
Timeslot configuration examples
Example A Example B Example C

0 BCCH TCH BCCH SW BCCH SW
1 TCH TCH TCH SW TCH SW
2 TCH TCH TCH SW TCH SW
3 SW TCH TCH RES TCH SW
4 SW TCH TCH RES TCH SW
5 RES TCH TCH RES TCH SW
BCCH CARRIER BCCH CARRIER BCCH CARRIER

CARRIER 2 CARRIER 2 CARRIER 2
BSS101_M3Ch1_3

Hierarchical position of the PCU VERSION 1 REVISION 0
Hierarchical position of the PCU

The PCU attaches onto a BSC and is associated only with one BSC. The PCU therefore
serves many BTSs.
The BSC regards the PCU as a remote BTS in terms of Database equipage. It should be
remembered however that for GPRS the PCU is as important as a BSC is for GSM.
The PCU will receive its code download from the BSC, i.e. it is under control from the
OMC–R. All statistics from the PCU will be reported to the OMC–R and NOT the
OMC–G.
Although the PCU is completely different hardware from Motorola BTSs, the interface will
be familiar to engineers with experience of them. Note however, that that the PCU does
not support a customer MMI only EMON. This can be accessed via RLOGIN or via a
TTY cable.
If web based MMI is supported, this can be used to extend the MMI prompt of the BSC to
a remote user connected into the Ethernet port of the PCU PSP.

VERSION 1 REVISION 0 Hierarchical position of the PCU
Hierarchical position of the PCU
BSC Site Device Equipage Hierarchy

BSC SITE
BTS SITE PCU
CAB
CELL CAGE
COMB KSW GCLK BSP BTP GPROC CSFP DHP EAS MSI
MMS*
LCF OMF BTF XBL MTL OML CBL GSL*

DRI
PAT H
16Kbps RSL 64Kbps RSL
RTF Associated RTF

*Indicates auto–equipped device
BSS101_M3Ch1_5

Functionality of the PCU VERSION 1 REVISION 0
Functionality of the PCU

A mobile sends some data that is destined for some far away server on the WWW. First
of all the data is sent over the air Interface to the BTS. The BTS sends the data in TRAU
frames to the BSC. The BSC switches these TRAU frames to the PCU. The PCU
terminates these particular GDS links on a PICP.
The PICP also terminates the GSL signalling links between the PCU and the BSC. The
PRP board can also terminate GDS links though the number of links is reduced because
of the signal processing that the PRP must carry out.
From the PICP board the data is routed over the PCU backplane, (the CPCI bus) to the
correct PRP board were the data is processed and formatted, (reconstitutes the LLC
frames from the RLC / MAC blocks).
From the PRP the data is sent to the appropriate PICP that handles the PCU/ SGSN link,
the Gb interface. The PICP sends the data using Frame Relay to the SGSN that can
then route the data through the GGSN and out into the WWW.

VERSION 1 REVISION 0 Functionality of the PCU
PCU Connectivity
PCU
SGSN
E1 PICP E1 PRP PSP PICP E1
PMC 860 PMC PMC
750 750 750 750
PCI Bus
E1 E1 E1
TRANSITION TRANSITION TRANSITION
MODULE MODULE MODULE
E1: FRAME E1: GDS (TRAU) E1: GDS

RELA Y (Gb LINK) (LAPD) & (TRAU)
BSC
TDM Bus
E1: CIRCUIT
SWITCHED
E1: CIRCUIT
SWITCHED
BTS BTS
AIR AIR GPRS

INTERFACE INTERFACE GPRS DA T A SIGNALING
(LAPD)
(TRAU)
MS MS
PHYSICAL
LA YERS
BSS101_M3Ch1_6

Functionality of the PCU VERSION 1 REVISION 0

Chapter 2
PCU Hardware


Chapter 2
PCU Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
PCU Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Static frame cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Swing frame cabinet structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Swing frame functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Introduction to specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Safety, EMC and environmental requirement specifications . . . . . . . . . . . . . . . . . 2–8
Environmental limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Access control specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Physical dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Cabinet input power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Power consumption (ac and dc) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
E1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Introduction to E1 interface connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
E1 interface panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18


Identify the PCU cabinet types
State the specifications for the PCU
Identify the E1 interface panel

PCU Cabinets VERSION 1 REVISION 0
PCU Cabinets
The PCU can be housed in one of two cabinet types. The static frame cabinet and the
swing frame cabinet.
The static frame cabinet can accomodate up to three PCUs and is only suited to
installations where rear access is available.
The swing frame cabinet can accomodate up to three PCUs and is suited to installations
where rear access is not available (i.e. installed against a wall).

VERSION 1 REVISION 0 PCU Cabinets
PCU Cabinet
SWING FRAME
STATIC FRAME
BSS101_M3Ch2_1

Static frame cabinet VERSION 1 REVISION 0
Static frame cabinet
Static frame
cabinet structure
The static frame cabinet has front and rear access doors, hinged on the left side of the
door. Additional access to the cabinet interior may be gained by opening quarter panels
in the cabinet sides.
Internally the static frame cabinet contains:
Standard 19 inch racking with pre-installed runners to mount up to three PCUs.
A horizontally mounted E1 interface panel for each PCU.
An A4 document pocket on the inside of the door.
Remote power switching provided by:
– A power input distribution mounting bracket with one remote ac power input
switching panel for each PCU.
or
– Up to two remote dc power input switch and cable assemblies, on power
input mounting panels, fitted to the front left racking member, adjacent to
each PCU.
Data cable and power cable entry can be from either the top or bottom of the cabinet,
with top entry recommended for data cables and bottom entry recommended for power
cables. Data and power cables are kept separated by using different entry points.
NOTE
This cabinet has a deeper footprint than the swing fame cabinet and is suitable
for direct side by side installation. Static frame cabinets may be bolted together
as a suite and are also capable of being bolted to the GSN cabinet suite.

VERSION 1 REVISION 0 Static frame cabinet
PCU static frame cabinet
BSS101_M3Ch2_2

Swing frame cabinet VERSION 1 REVISION 0
Swing frame cabinet

Swing frame
cabinet structure
The swing frame cabinet has front and rear access doors, the front door is hinged on the
left side of the door, the rear can be configured hinged on either left or right. Additional
access to the cabinet interior may be gained by opening quarter panels in the cabinet
sides.
The purpose of the swing frame is to allow access to the rear of the PCU when rear
access to the cabinet is not available
Internally the swing frame cabinet contains:
Three movable frames, each capable of supporting one PCU.
An E1 interface panel for each PCU.
One power input mounting panel for each PCU with:
– A single remote ac power input switch and cable assembly. or
– Two remote dc power input switch and cable assemblies.
Data cable and power cable entry can be from either the top or bottom of the cabinet,
with top entry recommended for data cables and bottom entry recommended for power
cables. Data and power cables are kept separated by using different entry points and
routeing.
NOTE
This cabinet is not suitable for bolting to adjacent cabinets as a suite, but may
be installed side by side with cabinets of the same depth or less. The swing
frame cabinet has a wider footprint than the static frame cabinet.
Swing frame
functional
description
WARNING
The swing frame cabinet must be bolted to the floor or supported by a wall
bracket at the top.
Operation of a populated swing frame in an unsecured cabinet presents a
danger of toppling.
Only one swing frame is to be open at any given time, the spare swing frame
key should be removed from the equipment and stored in a secure location.
The swing frames are secured in the closed position by locks, one lock on each frame.
Only one key is used with each cabinet and is captive in the swing frame lock when
unlocked. This is to ensure only one frame at a time can be open. The key must be
removed from the lock before the cabinet door can be closed.
Each swing frame rotates about the right front corner to allow access to the rear of the
PCU. A stay rod is used to hold the opened frame in one of the following three positions:
Stage 1 at 90 only used when floor space is very limited, allows minimum access
to E1 interface panel and rear of PCU.
Stage 2 at 135 normally used when floor space is restricted, allows greatly
improved access to E1 interface panel and rear of PCU.
Stage 3 at 180 used when floor space is not a major consideration, allows
maximum access to the E1 interface panel and rear of PCU.
To allow a swing frame to open to stages 2 and 3 the right front quarter panel must be
open.

VERSION 1 REVISION 0 Swing frame cabinet
PCU Swing frame cabinet
BSS101__M3Ch2_3

Specifications VERSION 1 REVISION 0
Specifications
Introduction to
specifications
The PCU and associated cabinet specifications are included in this section.
Safety, EMC and

environmental
requirement
specifications
Table 1-1 shows the safety, EMC, and environmental requirement specifications,
complied with by the PCU equipment.
Table 1-1 Requirement specifications complied with

Safety EMC Environmental
EN 60950, EN41003, ETS 300 342-2, ETS 300 019-1-3, class 3.2
IEC 950 EN 50081-1, EN 50082-2
Environmental
limits
The environmental levels for the PCU are the standard ETSI classes applicable to BTS
equipment. The PCU will be collocated with BSC hardware already in the field, which
may be in remote locations.
Table 1-2 shows the environmental limits for operation and storage of the PCU
equipment.
Table 1-2 Environmental limits

Environment Temperature Relative Humidity
Operating –5 C to + 45 C. 5 to 95 % relative humidity, at 30 C.
Storage –45 C to +70 C. Up to 93% relative humidity, at 30 C.
Transportation –40C to +70 C Up to 93% relative humidity, at 30 C.
Access control
specifications
Unauthorized access to the PCU equipment and associated cabinets must be prevented.
The PCU must only be Installed in a location where personnel access can be controlled.

VERSION 1 REVISION 0 Specifications
Specifications
Requirement specification complied with

Safety EMC Environmental
EN 60950, EN41003, ETS 300 342-2, ETS 300 019-1-3, class 3.2
IEC 950 EN 50081-1, EN 50082-2
Environmental limits
Environment Temperature Relative Humidity
Operating –5 C to + 45 C. 5 to 95 % relative humidity, at 30 C.
Storage –45 C to +70 C. Up to 93% relative humidity, at 30 C.
Transportation –40C to +70 C Up to 93% relative humidity, at 30 C.

Physical
dimensions
The dimensions of cabinets are shown in Table 1-3:
Table 1-3 Cabinet dimensions

Cabinet type Height Width Depth
GPRS PCU static frame cabinet 1900 mm 600 mm 875 mm
GPRS PCU swing frame cabinet 2000 mm 800 mm 675 mm
Weights
The equipment weights for available configurations are shown in Table 1-4.
Table 1-4 Equipment weights

Static frame cabinet Swing frame cabinet
Fully populated
PCU 31.85 kg 31.85 kg
Empty cabinet 138 kg 165.7 kg
With one PCU 169.85 kg 197.2 kg
With two PCUs 201.7 kg 228.7 kg
With three PCUs 233.55 kg 260.55 kg

Specifications
Cabinet dimensions
Cabinet type Height Width Depth
GPRS PCU static frame cabinet 1900 mm 600 mm 875 mm
GPRS PCU swing frame cabinet 2000 mm 800 mm 675 mm
Equipment weights
Static frame cabinet Swing frame cabinet
Fully populated
PCU 31.85 kg 31.85 kg
Empty cabinet 138 kg 165.7 kg
With one PCU 169.85 kg 197.2 kg
With two PCUs 201.7 kg 228.7 kg
With three PCUs 233.55 kg 260.55 kg

Cabinet input
power
requirements
WARNING
All cabinets and supply cables must be protected by an external fuse or circuit
breaker.
Table 1-5 shows the power supply requirements of the two types of PCU power systems.
Table 1-5 Power supply requirements

Nominal voltage Voltage supply range Maximum supply current
Wide ranging ac 88 to 260 V ac 4.5 amps per PCU
(single phase) 47 to 63 Hz @ 230 V ac
110 to 230 (nominal) 8.9 amps per PCU
50 to 60 Hz @ 110 V ac
–48/60 V dc –36 to –72 V dc 20.5 amp per PCU
(positive earth) @ –48 V dc
NOTE
Voltage transients must be less than 35 V peak amplitude (never below 0 V).
Ripple and noise must be less than 200 mV p-p (30 mV rms) over 10 Hz to
14 MHz. Voltage application stabilization must be within the specified range in
less than 1 second.
Power
consumption
(ac and dc)
Table 1-6 shows the power consumption of the GPRS cabinet.
Table 1-6 Power consumption

Maximum power
consumption
One PCU 984 watts
Two PCUs 1986 watts
Three PCUs 2952 watts

Power requirements
Power supply requirements

Nominal voltage Voltage supply range Maximum supply current
Wide ranging ac 88 to 260 V ac 4.5 amps per PCU
(single phase) 47 to 63 Hz @ 230 V ac
110 to 230 (nominal) 8.9 amps per PCU
50 to 60 Hz @ 110 V ac
–48/60 V dc –36 to –72 V dc 20.5 amp per PCU
(positive earth) @ –48 V dc
NOTE
Voltage transients must be less than 35 V peak amplitude (never below 0 V).
Ripple and noise must be less than 200 mV p-p (30 mV rms) over 10 Hz to
14 MHz. Voltage application stabilization must be within the specified range in
less than 1 second.
Power consumption
Maximum power
consumption
One PCU 984 watts
Two PCUs 1986 watts
Three PCUs 2952 watts

E1 interface VERSION 1 REVISION 0
E1 interface
Introduction to
E1 interface
connections
There is one E1 interface panel for each PCU populating a cabinet. In the static frame
cabinet the E1 interface panels are mounted horizontally behind each PCU, and are
accessed through the rear door. In the swing frame cabinet the E1 interface panels are
mounted vertically, to the left of each installed PCU, and fixed to the cabinet rear racking
inside the cabinet, (the swing frame must be open to provide access to the panels).
The figure opposite shows the position of the lower E1 interface panels in both cabinet
types.

VERSION 1 REVISION 0 E1 interface
E1 interface panel
STATIC FRAME
CABINET (REAR)
E1 interface panel
SWING FRAME
BSS101_M3_ch2_7 CABINET (FRONT)

E1 interface VERSION 1 REVISION 0
E1 interface
panels
The E1 interface panel allows for the connection of up to twenty–four 75ohm or 120 ohm
E1 lines.
The panel comprises:
Four front mounted T43/BIB board assemblies.
Four front mounted RJ45 connector panels, each containing 6 eight way RJ45
connectors.
Each T43/BIB panel is wired to the adjacent RJ45 connector panel at the rear of the
interface panel.
The following customer options are available:
PCU 75 Ohm E1 Interface, T43, for type 43 coaxial connections.
PCU 120 Ohm E1 Interface, BIB, for 120 ohm twisted pairs.

VERSION 1 REVISION 0 E1 interface
E1 interface panel
SIX WAY RJ45

CONNECTORS
T43/BIB BOARD
ASSEMBLIES
BSS101_E1 interface panel

PCU VERSION 1 REVISION 0
PCU
The PCU is a CPX8216 CPCI chassis. Up to three of the CPX8216 chassis can be
mounted in a cabinet. With the Interface panel the PCU is a self-contained unit and
requires no other components for the CPX8216 to operate as a PCU.
The card are re–named as follows:
System slot processor is now called the MPROC
Non-system slot processor is now called a DPROC
The HSC/bridge is now called the PCI to PCI Bridge (PPB)
The PMC is called the Network Interface Board (NIB)

VERSION 1 REVISION 0 PCU
View of the PCU
ALARM MODULE DIGITAL

MODULES
(transition module
and HSC bridge)
DIGITAL
MODULES
(MPROC and
DPROC)
POWER
DISTRIBUTION
MODULE
(not visible)
CPCI CHASSIS
FAN/POWER SUPPLY
SLEDS
BSS101_M3_Ch2_9

PCU VERSION 1 REVISION 0

Chapter 3
Digital Cards for PCU


Chapter 3
Digital Cards for PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
MPROC (Master Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
HSC/Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Digital Processor DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Packet Interface Control Processor (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Packet Resource Processor (PRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
DPROC (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
PCI to PCI Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Ethernet Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
PMC slots 1and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Front Panel Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
NIB (Network Interface Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
NIB overview (E1 PMC module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
I/O through the Backplane: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
RAM/ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
PCI Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Transition module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
E1 transition module functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18


State the operation of the DPROC
State the operation of the NIB
State the operation of the transition module

MPROC (Master Processor) VERSION 1 REVISION 0
MPROC (Master Processor)

The MPROC is the system slot processor using the MCP750 processor board. The term
MPROC should be used when referring to the system slot processor in the PCU.
The MPROC is responsible for bus arbitration and CPCI clock generation. The MPROC
runs BSSGP protocol functions and is the PCU System Processor, (PSP). This is similar
to the Motorola BSC, Master GPROC that is known as the BSP.
Only one PSP may be equipped per PCU . i.e. the CPX8216 chassis is operating in
simplex mode.
The MPROC has one PMC socket which is not used in the PCU.
HSC/Bridge
The HSC/Bridge card is the standard bridge card used in the CPX8216 chassis. This
card with the MPROC forms the CPU complex and work together as a pair. The
HSC/Bridge allows the second domain of the PCU to be used for further I/O boards
(Digital Processors (DPROCs)). This gives greater flexibility and more connectivity /
processing power in the PCU.

VERSION 1 REVISION 0 MPROC (Master Processor)
MPROC and HSC/Bridge
MPROC
The system slot processor
PCU System processor
Only one equipped per PCU
HSC/Bridge
Standard Bridge card
Allows both domains to be used for I/O boards (DPROCs)
BSS101_Mod3_Ch3_01a

Digital Processor DPROC VERSION 1 REVISION 0
Digital Processor DPROC
The DPROC boards are non–system slot processors, (I/O boards).They have two PMC
sockets (as opposed to the MPROC one socket) which are used for connecting E1 links
to the PCU for the GDS and GSL to the BSC and the Gb link to the SGSN.
The DPROC can have one of two software functions.
Packet Interface
Control
Processor (PICP)
The PICP board is used for connectivity to the BSC and SGSN. Can support two NIBs
(Network Interface Boards) for terminating GDS links and Gb links. Note: if a NIB is
terminating a Gb link, then the second port can only be used for Gb links.
Packet Resource
Processor (PRP)
Performs Air Interface scheduling and performs almost all GPRS related signaling. From
GSR5.1 onwards, both sockets on a PRP. can house PMC modules. Each of these can
terminate one E1 link.

VERSION 1 REVISION 0 Digital Processor DPROC
DPROC naming
Non-system slot
CPCI defined
processor
DPROC Motorola hardware defined
PICP PRP Motorola software defined
BSS101_M3Ch3_1

DPROC VERSION 1 REVISION 0
DPROC
DPROC (PICP)
The DPROC (PICP) is used for all network interfacing functions to the outside world such
as the SGSN and BSC. The PICP has up to two interface modules installed. Data
to/from these interfaces pass through the on–board processor. This processor has
different functions dependent on the interface type, but includes features such as packet
routing on an incoming SGSN link, packet scheduling to an outgoing SGSN link.
This board is a PCI slave board. The PICP routes data received from the SGSN or BSC
to the appropriate PRP board.
The DPROC is a high–performance processor.
128 Mb DRAM
376 MHz 750 Power PC processor
It supports two PMC modules that are used to house the E1 SGSN/BSC interfaces.

VERSION 1 REVISION 0 DPROC
Diagram of DPROC
BSS101_M3Ch3_5

DPROC VERSION 1 REVISION 0
DPROC
The DPROC is a high–performance single–slot PowerPC based platform providing a
32–bit CompactPCI bus interface. The CompactPCI bus interface device is directly
connected to the local PCI bus.
Features
Power PC processor (PPC)
Shared memory implemented via a memory module
Boot and User flash
Watchdog timers
Peripheral CompactPCI bus interface
Ethernet interface available via the front panel
On–board real–time clock with on–board battery backup
2 RS–232 compatible serial I/O ports
2 PMC slots with user I/Os available at the CompactPCI connectors J4 and J5
The PPC bus works in Big endian mode and all other buses are Little endian.
Front–panel interfaces
The front panel of the PPC/PowerCoreCPCI–6750 provides
Ethernet interface for 10Base–T or 100Base–Tx
Two serial I/O. console ports, for download and for data communication.
PCI to PCI Bridge

The PCI–to–PCI Bridge provides a high–performance interface between the local PCI
bus and the CPCI bus. The primary side of the bridge is connected to the CPCI bus, the
secondary side of the PCI–to–PCI bridge is connected to the local PCI bus. Both buses
are 32–bit wide and run up to 33 MHz.
Ethernet
Controller
The Ethernet interface 10Base–T or 100Base–TX is available at the front panel via an
8–pin RJ–45 connector.
PMC slots 1and 2

The DPROC provides two PMC slots for installing compliant PMC modules. The PCI
bus, a high–speed local bus, connects different high–speed I/O cards with the DPROC.
Both PMC slots support 32–bit data bus width with a frequency of 33 MHz. PMC slot 1
and PMC slot 2 have each 64 user I/O signals. These signals are available on
connectors J4 and J5.
Switches
There are switches on the board used for configuration purposes, these switches are
factory set and should not be altered, to do so can render the DPROC inoperative.

VERSION 1 REVISION 0 DPROC
Diagram of DPROC
Serial interfaces Serial interfaces

Serial
I/O ports ISA bus C
Memory
o
module(s) Watchdog RTC/ m
timers NVRAM p
F User flash a
R CIO c
O Boot flash t
PPC-to- P
N Serial ID
PPC bus PCI bridge PCI bus C
T PROM
MPC106 I
(Grackle)
P
PCI-to-ISA I/O
A PowerPC L2 bridge
N CPU cache
E
L PMC I/O
PMC module (slot 2)
PMC I/O
PMC module (slot 1) AUI Ethernet
Ethernet
controller MII Ethernet
C
10–Base T or 100–Base TX Interface o
adapter m
p
PCI-to-PCI a
PCI bus CompactPCI bus
bridge c
t
P
C
I
BSS101_Mod3_Ch3_06

Front Panel Description VERSION 1 REVISION 0
Front Panel Description

RESET– Mechanical reset key: When enabled and toggled it instantaneously affects the
board by generating a reset. A reset of all on–board I/O devices and the CPU is
performed when the reset key is pushed to the active position. To avoid unintentional
reset, the reset key is recessed in the front panel.
ABORT– Mechanical abort key: When enabled and toggled it affects the board by
generating a non–maskable interrupt (NMI) request via the PCI–to–ISA bridge. This
allows an abort of the current program, to trigger a self–test, or to start a maintenance
program. To avoid unintentional abort, the abort key is recessed in the front panel.
LED R– RUN/RESET LED indicating the board status:
– green: normal operation
– red: reset is active
LED T– Test LED: For factory test. Off during normal operation.
LED U 1– User LED 1: Software programmable by the CIO counter/timer and parallel I/O
unit. Bits 0 and 1 of port C are used. Possible status: green, red, or off.
LED U 2– User LED 2: Software programmable by the CIO counter/timer and parallel I/O
unit. Bits 2 and 3 of port C are used. Possible status: green, red, or off.
100Base–Tx 10Base–T ETHERNET– An 8–pin RJ–45 connector for the interfaces
100Base–Tx or 10Base–T Ether–net including 2 LEDs:
– The green LED stays lit while the Ethernet is linked.
– The red LED stays lit while the Ethernet is active.
Serial Ports– A double 9–pin MicroD–Sub connector for 2 serial ports
Hot–swap switch –The Hot–swap switch is integrated into the lower handle. When the
handle is opened during normal operation the interrupt signal ENUM# is asserted on the
CPCI backplane. This interrupt indicates that the board state is about to change i.e.
insertion of a new board or the pending removal of a board.

VERSION 1 REVISION 0 Front Panel Description
DPROC front panel
PMC2
PMC1
Reset
Abort
U1
R U2
Base T
Serial 1 Serial 2
BSS101_M3Ch3_7

NIB (Network Interface Board) VERSION 1 REVISION 0
NIB (Network Interface Board)
NIB overview (E1

PMC module)
The NIB is a PMC using a Power PC processor. The NIB connects onto the local PCI
bus of its host processor (the DPROC) through a PCI to PCI Bridge IC.
The NIB performs all of the physical layer termination of the E1 link to the SGSN. The
module also supports the termination of the Frame Relay layer 2 protocol and passes
received data packets to its host board processor.
The E1 interfaces to the BSC provides for physical connection of all GPRS data channels
into and out of the BSC, allowing the BSC to switch the channels to the appropriate BTS.
These links also carry the GSL (GPRS Signaling Link) between the PCU and BSC. The
GSL can be multiple 64k timeslots. It is used to manage and control the PCU/BSC
system.

VERSION 1 REVISION 0 NIB (Network Interface Board)
NIB
BSS101_M3Ch3_8

NIB (Network Interface Board) VERSION 1 REVISION 0
I/O through the

Backplane:
One major feature PMCs have over regular PCI cards is the capability to route I/O
through the host to the backplane, for rear I/O.
The PMC will only ever have the rear I/O configuration in the PCU configuration.
One connector position (P14) is specified to support rear panel I/O. Hosts like
CompactPCI route I/O signals from the mezzanine card P14 connector to the rear
backplane connector(s).
The PMC is hardware configured for front or rear I/O at time of manufacture and cannot
be subsequently changed. As well as the lack of the connectors at the front component
changes are also made to route the E1 links through P14.
The PMC architecture does not modify the CPCI electrical, logical and software
interfaces. PCI interface is used “as is”. The complete functionality of a CPCI card can be
maintained, except for the mechanical form factor.
CPU
The PMC has a dedicated RISC processor the Motorola PowerQUICC with 32 bit internal
architecture. It has an internal data cache and Instruction cache of 4 KB each.
RAM/ROM
The PMC can have 32 bit wide 4 / 8 or 16 Mbytes of RAM. It also has a socket for Flash
(ROM) memory of up to 512K in size.
I/O
The PMC card has 2 ports configured for E1 link lines. This is factory defined because
the board is fitted with either E1 controllers or T1 controllers (only E1 implemented in
Motorola GPRS). The PMC will only ever be configured as E1. The controller is a
transceiver and converts the logic signals going to and from the main processor.
PCI Bus
The bus controller controls the interface between the PMC and the PCI bus i./e. bridging
between them. It provides an asynchronous operation between local and external PCI
busses up to 33.33MHz
The PMC will physically interface to the E1 connection via transition modules on the
backplane of the PCI cage. It achieves this by connecting to the PCI bus through the
Host processor card.

VERSION 1 REVISION 0 NIB (Network Interface Board)
Peripheral Mezzanine Card (PMC)
PCI Bus
32 bit local 32 bit 33 MHz
bus
512K ROM DRAM
2K PCI Controller
P
EEPROM 1
1
E1 128 byte serial

Controller
CPU
EEPROM
MPC860MH
E1
Controller Rear
P
1
4 2 x E1 Link
BSS101_Mod1_Ch4_4

Transition module VERSION 1 REVISION 0
Transition module
The transition module provides the cage slot with rear I/O. The transition module works
with the PMC module via the PMC host. The PMC and transition modules come as a
pair. The transition module enables IO connectors like RJ45 to be used in connecting to
the PMC module which otherwise would not be capable of accepting such connectors.

VERSION 1 REVISION 0 Transition module
Transition Module
Connector
P5
Connector
P4
E1 PORT 2B
Isolating E1 PORT 2A
transformers
E1 PORT 1B
E1 PORT 1A
CON 2
DLD2
NOT USED
CON 1
REAR FACE
DLD1
NOT USED BSS101_M3Ch3_9

E1 transition
module
functional
description
The transition module provides NIB connectivity through the following interfaces:
TM/cSpan-FMI interface:
The TM/cSpan-FM local bus connects through the PCU backplane on cPCI
connectors P4 and P5 to the network interface boards (NIB), in slot one and slot
two, respectively.
E1 interfaces:
There are four E1 interfaces, each with common mode choke noise filtering;
isolating transformers (1500 V rms isolation); and self resetting, positive
temperature coefficient, over current protection. These interfaces use shielded
RJ45 connectors. This four wire balanced interface is then routed to connectors P4
and P5.
EIA-232:
There are four EIA-232 serial communication ports each with overvoltage
protection and shielded RJ45 connectors with ferrite filtering.

VERSION 1 REVISION 0 Transition module
E1 transition module functional diagram
NIB 1 DPROC NIB 2
P4 P5
Protection
Transformers
Protection
Protection CM choke
NIB 2 E1 Ports
NIB 1 EIA–232 (2 links)
Ports
TRANSITION NIB 1 E1 Ports
NIB 2 EIA–232
Ports MODULE (2 links)
BSS101_Mod3_Ch3_10


Chapter 4
PCU Software Processes


Chapter 4
PCU Software Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Packet Interface Control Processor (PICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Functional Units (FU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Frame relay FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
GB FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
LAPD FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
TRAU FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
STATUS FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
I/O FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Packet Resource Processor (PRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Packet scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Access Grant, Sys Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
RLC seg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
PRP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Uplink Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Timeslot Resource Shifter (TRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
PCU System Processor (PSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
GB FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Gateway manager FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
I/O FU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
PSP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Base Station Sub–System Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Gb Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Gb Router (GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Gateway Transmit Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Network Service Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Flow Control Buffer Manager (FBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Fault detection and handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
System Audit Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
PCU Central Authority (pCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28


Identify the software components of the PSP
Identify the software components of the PRP
Identify the software components of the PICP
State the operation of the Fault management system
State the operation of Configuration management and the Central Authority
State the Initialisation process of the PCU

Packet Interface Control Processor (PICP) VERSION 1 REVISION 0
Packet Interface Control Processor (PICP)

The Packet Interface Control Processor (PICP) is a function residing on a DPROC
(non–system slot processor). The PICP is made up of functional units.
Functional Units
(FU)
A functional unit does not necessarily represent a software process. It is used to describe
a group of processes that can be treated as one entity. The processes are grouped
together as they would share a similar purpose or interface. The functional unit may act
as a single process or separate processes. A single functional unit may reside on one
processor (i.e. DPROC) or may be distributed over several processes.
Frame relay FU
The Frame relay functional unit on the PICP is used to support the Frame Relay
connection from the PCU to the SGSN. Over this link signalling data and traffic data are
passed. The Frame Relay FU maintains the permanent virtual circuit connections.
GB FU
The GB functional unit determines what type of LLC frame has been passed over the GB
link. The LLC will be either;
User data
SGSN–MS signalling
BSSGP signalling
Once the GB FU has decided what type of LLC frame it is, the data is then passed to the
appropriate processor.
The GB FU also contains the following;
Paging routeing – to route signalling for paging messages from SGSN to the appropriate
cell
Flushing routeing – to route flushing messages of queued SDUs for MSs to the
appropriate cell.
Flow control routeing – to route flow control messages of downlink traffic, (flow control
includes the queuing of MS packets based on priority queues.

VERSION 1 REVISION 0 Packet Interface Control Processor (PICP)
PICP
PRP PSP
PSP PICP
Status
TRS GB F.U. Status F.U. FR F.U. Status F.U.
F.U.
Packet
Scheduler I/O F.U. I/O F.U. I/O F.U.
Uplink GB F.U.
AccesGrant Downlink
SYS Inf GWM F.U. Page Routeing
Paging
RLC Seg BMS Flushing Routeing
pCM
Flow TA & PC Flow Control
Control pCA Routeing
pSSP pSM
pFTP/pFCP
pSAP
LAPD TRAU
Cell balancer F.U. F.U.
BSS101_Mod3_Ch4_01

Packet Interface Control Processor (PICP) VERSION 1 REVISION 0
LAPD FU
The LAPD functional unit is used for synchronization of the LAPD link over the GSL
between the PCU and the BSC.
TRAU FU
The TRAU functional unit is used for synchronization and handling of the PCU frames
between the PCU and the BSC.
STATUS FU
The PICP STATUS functional unit is used for debugging mechanisms. It also generates
the display of alarms and can monitor messages being passed between processes.
I/O FU
The I/O functional unit routes messages between the functional units on the PICP and
functional units on the PSP.

VERSION 1 REVISION 0 Packet Interface Control Processor (PICP)
PICP
PRP PSP
PSP PICP
Status
F.U.
Packet
Uplink GB F.U.
AccesGrant Downlink
Paging
pCM
pSSP pSM
pFTP/pFCP
pSAP
LAPD TRAU
BSS101_Mod3_Ch4_01

Packet Resource Processor (PRP) VERSION 1 REVISION 0
Packet Resource Processor (PRP)

The Packet Resource Processor (PRP) is where all of the radio related processing takes
place. The PRP performs all of the RLC / MAC processing, air interface scheduling and
frame synchronization on the BTS facing channels. The following functional units provide
this functionality:
Packet scheduler
The Packet scheduler handles the scheduling of uplink and downlink packets for the Um
interface. This is done on a per call basis. The packet scheduler will assign the number
of timeslots and the number of blocks that a mobile may use in accordance with the MS
Quality of Service record.
Access Grant,
Sys Info
This functional unit deals with channel request by replying with Immediate Assignment.
The unit is also responsible for the relaying the paging messages received from the
SGSN.
RLC seg
This functional Unit is responsible for LLC segmentation into RLC / MAC blocks in
accordance to the coding scheme being used. The unit also reassembles RLC / MAC
blocks into LLC frames for uplink PDCH. A part of this unit carries out the timing advance
and power control for GPRS mobiles.
PRP Status
The unit will observe signalling messages between processes and functional units. The
unit also contains functions that can initiate status commands to display generation of
alarms and debugging commands.
I/O
The I/O unit provides routing between the functional units and between processors.
Uplink Downlink
The Uplink Downlink unit routes RLC / MAC blocks to and from the Channel Coder Unit
(CCU).

VERSION 1 REVISION 0 Packet Resource Processor (PRP)
PRP
PRP PSP
PSP PICP
Status
F.U.
Packet
Uplink GB F.U.
AccesGrant Downlink
Paging
pCM
pSSP pSM
pFTP/pFCP
pSAP
LAPD TRAU
BSS101_Mod3_Ch4_01

Packet Resource Processor (PRP) VERSION 1 REVISION 0
Timeslot
Resource Shifter
(TRS)
This unit is responsible for monitoring GPRS timeslots allowing them to become active.
The TRS will allow only 30 timeslots to be GPRS active whilst 90 timeslots are inactive.
When a current timeslot in a cell becomes inactive i.e. no GPRS users then a timeslot in
another cell which was inactive can be brought into the active state to help increase data
throughput. The TRS will manage this
Flow control
This unit works in conjunction with the SGSN to control the flow of data down to a
particular mobile. The flow control will operate on a per call basis and will be affected by
the quality of service that the mobile supports and the current data throughput. The flow
control unit therefore works closely with the Packet scheduler.

VERSION 1 REVISION 0 Packet Resource Processor (PRP)
PRP
PRP PSP
PSP PICP
Status
F.U.
Packet
Uplink GB F.U.
AccesGrant Downlink
Paging
pCM
pSSP pSM
pFTP/pFCP
pSAP
LAPD TRAU
BSS101_Mod3_Ch4_01

PCU System Processor (PSP) VERSION 1 REVISION 0
PCU System Processor (PSP)

The PCU System Processor (PSP) resides on the MPROC (system slot processor). The
PSP is responsible for PCI bus arbitration and clock generation. The PSP contains
BSSGP functions. Only one PCU System Processor (PSP) may be equipped at a PCU.
The PSP has the following functional units:
GB FU
The separate GB functional unit at the PSP handles blocking/unblocking and reset.
Gateway
manager FU
The Gateway Manager functional unit (GWM) handles the following functions:
PCU Central Authority – pCA. Code loading of objects during initialization and
reset. Board initialization and startup for software processes.
PCU Configuration management process –pCM. Handling database information
and changing affected functional units. Works in conjunction with pCA, CA and
CM.
PCU Fault Translation Process, PCU Fault Collection Process –pFTP, pFCP. Fault
management functions (i.e. fault detection, fault recovery, etc). Alarm Collection
and Relaying.
PCU Site statistics process – Collection of statistics from functional units and
forwarding to the CSP, (Central Statistics Process) on the GPROC.
PCU System Audit Procedure process supported on the MPROC as well as the
DPROCs that contain a local process.
Cell Balancer –Cell resource sharing (that is balancing of cells) across equipped
PRPs. If a PRP outage occurs the Cell balancer will attempt to move the cell to
another PRP. Collection of cell list for BSC–BTS Dynamic Allocation purposes
PCU Switch Manager pSM. The pSM maintains data paths within the PCU and
communicates with the SM at the BSC for Rci to GDS 16K mapping.
The PCU GWM acts as the interface to the BSC FM, SM, IP, CM, MMI, CP, Statistics
process, CSP as well as RSS.
I/O FU
An I/O functional unit is created on the PSP for communication with the functional units
at the PRP and PICP.
PSP Status
The unit will observe signalling messages between processes and functional units. The
unit also contains functions that can initiate status commands to display generation of
alarms and debugging commands.

VERSION 1 REVISION 0 PCU System Processor (PSP)
PSP
PRP PSP
PSP PICP
Status
F.U.
Packet
Uplink GB F.U.
AccesGrant Downlink
Paging
pCM
pSSP pSM
pFTP/pFCP
pSAP
LAPD TRAU
BSS101_Mod3_Ch4_01

Base Station Sub–System Management Server. VERSION 1 REVISION 0
Base Station Sub–System Management Server.

The BMS shall reside on the PSP of the PCU. The BMS shall contain 3 servers, HTTP,
MMI, and EMON.
The HTTP server will establish a session to a remote host, using an Ethernet connection
to download the subsequent applet.
The MMI server will send a message to the TTY DLSP process in the BSC, over the
GDS LAPD (GSL), to inform of the presence or non–presence of an MMI connection.
The EMON server will do this to inform of the presence or non–presence of an EMON
connection. There can be only one MMI and one EMON connection running concurrently,
although both can conceivably be running on the same host.
The MMI server will manage the transmission of MMI strings between an end user and
the TTY DLSP process in the BSC. The TTY DLSP process will interact with the MMI
process in the BSC.
The EMON server will manage the transmission of EMON strings between an end user
and the TTY DLSP. The TTY DLSP process will interact with the monitor process.
In both of these cases the Web based MMI process extends the MMI socket on the BSC
out to the PCU and eventually the end user.

VERSION 1 REVISION 0 Base Station Sub–System Management Server.
Base Station Sub–System Management Server
browser
mmi MMI
strings Server mmi
mmi
strings
emon EMON emon tty

strings Server strings disp
events
gui HTTP monitor

Server
BMS
applet:
mmi emon
pcu
bsc
BSS101_Mod3_Ch4_02

Gb Functional Unit VERSION 1 REVISION 0
Gb Functional Unit
The Gb functional unit is divided into the following processes:
Gb Manager (GBM)
Gb Router (GR)
Gateway Transmit Manager (GTM)
Network Service Test (NST)
Flow Control Buffer Manager (FBM)
GBM
The GB Manager manages BSSGP Virtual Circuit (BVC) (cell) and NS–VC (PVC)
management procedures. The Gb Manager (GBM) maintains internal tables monitoring
the state of BVCs and NS–VCs and the mapping between them. The GBM is
responsible for the monitoring of the Gbl link status and generating the appropriate
alarms. The GBM will inform the Gateway Manager (GWM) of any change in GBL
status.
The GBM manages the BVC and NS–VC block, reset and unblock procedures. It shall
generate the appropriate alarms. The FR functional unit at the Packet Control Unit
(PCU) shall detect when the last GBL goes out of service and reports it to the GBM,
which in turn reports the event to the pFTP and informs the pFCP to generate an alarm.
The GBM is also responsible for sending Radio Status messages to the SGSN (i.e. BTS
not MS) and the handling of Routing Area (RA) capability procedures.
Gb Router (GR)
The Gb Router (GR) validates and routes downlink PDUs. The GR routes the downlink
PDUs to the appropriate Flow Control Buffer Manager (FBM) which will pass the PDU to
the air functional units for transmission over the air.
The GR is also responsible for the routing of paging messages to the appropriate Paging
function on a Packet Resource Processor.
Gateway
Transmit
Manager
The Gateway Transmit Manager (GTM) gathers and transmits uplink PDUs on the
correct NS–VC. The air functional unit concatenates the uplink Logical Link Control
(LLC) frame and the load sharing function chooses the appropriate NS–VC from the
NS–VC group serving the BSSGP Virtual Circuit Identifier (BVCI) for transmission by the
GbFu to the SGSN. The GTM gathers the PDUs from the various cells and passes them
to the FR functional unit for transmission over a given DLCI and Gbl.

VERSION 1 REVISION 0 Gb Functional Unit
Gb Functional Unit
NST
GB Router
GB Manager
Gateway
Transmit
Manager Flow Control
Buffer Manager
BSS101_M3Chh4_3

Network Service Test VERSION 1 REVISION 0
Network Service Test

The Network Service Test (NST) periodically tests NS–VCs to see if they are alive. The
NST also sends test messages on each alive NS–VC and responds to test messages
from the SGSN by sending back an acknowledgement on the same NS–VC.
Flow Control
Buffer Manager
(FBM)
The Flow Control Buffer Manager ensures that opened downlink LLC frames are
transmitted over the air within their delay class limitations. The FBM performs flow
control using either XON/XOFF or the ‘leaky bucket’ algorithm. When using the ‘leaky
bucket’ algorithm the configurable parameters of the maximum size of the downlink buffer
and maximum data rate the SGSN can transmit data to the mobiles will govern the
algorithm. The FBM will send at a configurable interval flow control messages to the
SGDN to govern the downlink data transfer.
The FBM is also responsible for the flushing of a mobile LLC PDUs from a cell queue for
that mobile and informing the packet scheduler to delete the mobiles context for that cell.

VERSION 1 REVISION 0 Network Service Test
NST
Periodic testing of NSVCs
FBM
Ensure queued dl LLC frames transmitted within their delay class
Flushing of LLC frames

Fault Management VERSION 1 REVISION 0
Fault Management
The Fault Management software at the Packet Control Unit (PCU) may be split into two
main areas; the fault detection and handling system and the Central Authority (pCA).
The Fault Management software is responsible for the detection of any alarms and
deciding upon any hardware /software reconfiguration in response to these alarms.
The PCU Central Authority, under the direction of the fault handling and detection
system, is responsible for carrying out the reconfiguration.

VERSION 1 REVISION 0 Fault Management
Fault management
Fault detection
Central Authority
and handlng
BSS101_M3Ch4_5

Fault detection and handling VERSION 1 REVISION 0
Fault detection and handling

This area of Operations and Maintenance is responsible for the detection, collection,
reporting and deciding actions to be taken if faults appear in the Packet Control Unit
(PCU).
The system is based around three processes:
1. The Fault Collection Process (pFCP)
This process exists at every DPROC at a site. It collects alarm reports from all processes
that exist on its particular DPROC. This process automatically acknowledges receipt of
an alarm and then passes all alarms indications up to the fault translation process.
2. Fault Translation Process (pFTP)
This process exists on the PCU System Processor (PSP) as part of the GWM functional
unit, and works with various processes to keep the integrity of the site. All alarms at the
PCU are reported to the pFTP. The pFTP forwards alarms to the Agent at the BSC and
generates messages to the pCA for device transitions, as needed, based on faults
reported.
3. System Audit Process (pSAP)
The System Audit Process exists on every DPROC at a site. This process periodically
audits the PCU software and any faults found are forwarded to the Fault Translation
Process via the Fault Collection Process.

VERSION 1 REVISION 0 Fault detection and handling
Fault translation process
Agent pFTP pCA
pFCP
PCU
Devices
BSS101_M3Ch4_6

System Audit Process VERSION 1 REVISION 0
System Audit Process

The Packet Control Unit (PCU) System Audit Process follows much the same
architecture as the BSS. A Site System Audit Process (pSSAP) resides on the PCU
System Processor (PSP) as part of the Gateway Manager (GWM) functional unit. The
PSP performs the audits of the PCU and communicates directly with the BSC MMI and
SAP.
The DPROCs contain a local process responsible for auditing the DPROC upon which it
resides.
The SAP will detect faulty/degrading hardware and software through the use of audit
tests and if a failure is detected it is reported to the pfTP.
There are three types of System Audit Process:
Site System Audit Process – one per site and will result in an audit of all available
hardware in the PCU.
Cage System Audit Process – has the same functionality as the Site System Audit
Process. This has been provided for future multi cage PCUs.
Device System Audit Process – responsible for auditing the device on which it
resides.
The System Operator can turn the audit functionality ON/OFF on a device, cage or per
site basis. The System Operator can modify the audit schedules for a specific device or
cage, e.g. device audit.

VERSION 1 REVISION 0 System Audit Process
System audit process
Three types of Audit Process
– Site System Audit Process (pSSAP)
– Cage System Audit Process (pCSAP)
– Device Audit Process
BSS101_Mod3_Ch4_07

Configuration Management VERSION 1 REVISION 0
Configuration Management
The Configuration Management (CM) Software is responsible for managing and updating
the main configuration database at either a BSC, BTS or PCU. This database is
downloaded as an object file and contains all the site parameters such as site
configuration and device functionality distribution.
The CM process at the BSC communicates with the pCM process in the same manner
as a remote BTS. If database changes are listed as at the PCU then the BSC CM will
forward the changes to the PCU Configuration Management (pCM). There is no MMI
functionality at the PCU so the pCM has reduced functionality compared to the CM at the
BSC.
The pCM process resides on the PCU System Processor (PSP) as part of the Gateway
Manager functional unit. The pCM receives the CM database object from the BSC. After
translation the database object is stored on compact flash on the PSP. The translated
object is cross–loaded to the DPROC boards equipped in the database with code objects
at initialisation.

VERSION 1 REVISION 0 Configuration Management
Configuration management
BSC CM BSC
Master Database
Compact Flash Memory
MASTER
PSP pCM
DATABASE
Slave pCM Slave pCM

Database Database
Copy Copy
DPROC DPROC
BSS101_M3Ch4_9

PCU Central Authority (pCA) VERSION 1 REVISION 0
PCU Central Authority (pCA)

On site initialisation, the central authority (pCA) process is created and queries the
database to obtain site configuration and device equipage data. The central authority is
then responsible for creating all the necessary software processes on the DPROCS, as
well as downloading and ”bringing into service” all peripheral boards and devices. On
completion of site initialisation, the pCA then works as an independent process with a
dynamic database keeping track of the state of all devices and software functions on its
site.
If a fault indication occurs at the site and the fault detection and handling system decides
that a device or software identity must be taken out of service, then it is the pCA that will
perform this task. If the fault detection and handling system decides to bring another
device or software entity into service, in response to that alarm indication then it is the
pCA that will supervise the downloading/initialisation of the device or software entity. It
may be the case that the system operator wishes to remove or insert a device from
service with a MMI command, it is the pCA that carries out the action.
In both of the above cases, once the reconfiguration has occurred, the pCA will update
the device state of each entity in its dynamic database.
However, if the site is re–initialised the pCA process is lost and the device states are
erased. The pCA is then created by the initialisation process, the pCA reads the
database and the initialisation procedure starts again.
The pCA is responsible for informing the router process when software processes are
created, destroyed or moved. This allows the router process to modify the router tables
which are used by the executive to support the ”flexible interprocess communications”
feature.

VERSION 1 REVISION 0 PCU Central Authority (pCA)
PCU Central Authority functions
A. Site Initialisation
1. Queries for database for site configuration and equipage

2. Downloading software to the hardware
3. Create software on DPROCs
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

Initial Configuration VERSION 1 REVISION 0
Initial Configuration
1. To begin Initialization, the BSC IP will instruct the BSC Exec DISP to bring up the
GSL as specified in the database. On the PCU at the PCU System Processor
(PSP) an IP (pIP) and EXEC DLSP bring up the other side of the default GSL.
2. Once communication is established the BSC IP queries the pIP for the set of
objects currently residing at the PCU to determine which new objects require
sending. The required set are transferred from the BSC to the PCU. The
database is included in this transfer.
3. The PSP, once the download is complete, will determine which card is in each slot
of the PCU and download the appropriate objects and database information to
each DPROC and PMC. The database is stored in non–volatile memory at the
PSP.
4. The PSP now distributes the configured number of cells in the database across the
PRPs. It also creates router tables of cell to router and distributes this table to all
boards to allow communications.
5. The Gateway Manager (GWM) now initiates process startup at the PRPs and
PICPs
6. The GBL interface is now initialised as the GSL is brought into service. The PSP
now indicates to the BSC CA that the PCU is enabled and registers for calls.

VERSION 1 REVISION 0 Initial Configuration
PCU Initialization
pIP + BSC IP bring up default GSL
BSC IP queries PCU pIP for set of objects
BSC IP download objects if required
pIP downloads appropriate object to each DPROC + PMC
PSP distributes configured cells across PRPs
GWM starts up PRPs + PICPs
GBL initialized + GBL brought into service
PSP indicates PCU enabled + registers for cells
BSS101_M3Ch4_11

Initial Configuration VERSION 1 REVISION 0

Chapter 5
PCU Installation


Chapter 5
PCU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
PCU Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Installing the PCU cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Introduction to cabinet installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Adjusting cabinet feet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Top supporting bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Mounting the PCU in a cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Options for mounting the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Safety considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Fitting the cable guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Fitting a PCU into a cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Mounting a PCU in a static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Mounting a PCU in a swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Fitting E1 interface panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
E1 interface panel options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Static frame cabinet E1 interface panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Swing frame cabinet E1 interface panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Swing frame cabinet E1 interface panel procedures . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Connecting the E1 cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
T43 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
BIB connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Connecting the digital interface cable loom to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Introduction to digital loom connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
GDS links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Gb links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Default GSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Digital cable connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
Static frame cabinet digital cable connection procedure . . . . . . . . . . . . . . . . . . . . . 5–18
Swing frame cabinet digital cable connection procedures . . . . . . . . . . . . . . . . . . . 5–18
Fitting power input switches and mounting panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Power input switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Power input switching options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet ac option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet dc option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Swing frame cabinet option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Static frame cabinet power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Fitting ac power input switches to static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22
Fitting dc power input switches to static frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Swing frame cabinet power input switch mounting panel . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Fitting power input switches to swing frame cabinet . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Swing frame power input cable routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–28
Earthing and transient protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Site earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Transient protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Cabinet earth bar connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32

Connecting external dc power cables to the cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–34

Connection procedure for supplied dc power cable . . . . . . . . . . . . . . . . . . . . . . . . . 5–34
Connecting external ac power cables to the cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
External ac cable routeing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
Connection procedure for ac detachable power supply cord/appliance coupler . 5–36
Connecting to external power source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Connecting dc power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Connecting ac Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Powering up the Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Power up procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Routine maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Cleaning fan filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Post maintenance return to service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Field replaceable units (FRUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42

Install the cable guide
Install a PCU Chassis into a cabinet
Install the cabling required for the PCU
State the power up procedure of the PCU
State the maintenance and FRU procedures for the PCU

PCU Installation VERSION 1 REVISION 0
PCU Installation
Installation comprises the following:
Equipment delivery and unpacking
Cabinet assembly
Cabinet access procedures
Installing the PCU cabinet
Mounting the PCU in a cabinet
Fitting E1 interface panels
Connecting the digital interface cable loom to the PCU
Fitting power input switches and mounting panels
Earthing and transient protection
Connecting earth and bonding cables
Connecting external dc power cables to the cabinet
Connecting external ac power cables to the cabinet
Connecting to external power source
This information should only be used as a guide for detailed and up to date information
the engineer should refer to the Service manual.

VERSION 1 REVISION 0 PCU Installation
PCU Installation
Equipment delivery and unpacking

Cabinet assembly
Cabinet access procedures
Connecting earth and bonding cables

Installing the PCU cabinet VERSION 1 REVISION 0
Introduction to
cabinet
installation
The cabinet can be mounted on a smooth concrete floor, or other strong supportive
cavity construction. The swing frame cabinet requires four M10 floor mounting anchor
bolts, or if the floor is not suitable, the bracing bracket supplied with the equipment, must
be fitted. Motorola recommend that the static frame cabinet be also bolted to the floor.
If the cabinet is not stabilised there is a danger that it may topple, particularly with a
swing frame cabinet when the swing frames are rotated.
The swing frame cabinet must be stabilised by bolting to the floor, (or by fitting the
supporting bracket to the top of the cabinet).
There are two possibilities for PCU installation.
PCU swing frame cabinet.
PCU static frame cabinet.
Adjusting
cabinet feet
To attest the levelling feet on a static frame cabinet.
1. Open front and rear doors of cabinet, and locate the levelling feet.
2. Loosen the locknut on the levelling foot, located underneath cabinet frame, using a
19–mm open–ended spanner.
3. Use a flat bladed screwdriver to adjust the levelling foot.
4. Tighten the locknut.

VERSION 1 REVISION 0 Installing the PCU cabinet
Static and swing frame cabinet floor fixing
4 by M10 clearance
holes
875 mm 764
reference mm
55.5 496 mm
mm
51
mm 600 mm
reference
STATIC FRAME CABINET

TEMPLATE
675 mm 582 4 by M10 clearance

reference mm holes
46.5
mm
696 mm
52
mm 800 mm
reference
SWING FRAME CABINET

TEMPLATE BSS101_M3Ch5_3

Top supporting bracket VERSION 1 REVISION 0
Top supporting bracket

Alternatively, to secure a swing frame cabinet by fitting a supporting bracket, between the
top of the cabinet and a wall:
1. Using the supporting bracket as a template mark the position of the holes, on the
selected wall, 1925 mm above the floor.
2. Select a suitable hexagonal head M8 fastener to secure the supporting bracket to
the wall, in accordance with local site requirements as determined by a structural
engineer.
Wear safety glasses and a dust mask when drilling holes.
3. Drill the two marked holes, if necessary, and secure supporting bracket to the
wall.
Tighten the M10 fastener until the bracket is a tight sliding fit against the wall.
Raise the bracket as high as the slots will allow.
4. Position the cabinet with the rear side against the wall, and lower bracket over
rear of top frame.
5. Tighten the M8 fasteners, using an open–ended spanner.

VERSION 1 REVISION 0 Top supporting bracket
Top supporting bracket
SLIDE BRACKET
DOWN
SUPPORTING
BRACKET
M8 FASTENER
SLOTS
CABINET TOP FRAME

REAR SECTION
BSS101_M3Ch5_3

Mounting the PCU in a cabinet VERSION 1 REVISION 0
Options for
mounting the
PCU
The two mounting options available for the PCU are in the:
Static frame cabinet.
Swing frame cabinet.
Up to three PCUs can be mounted in either option, with unpopulated positions concealed
by aesthetic bay panels. Swing frame cabinets also have a rear blanking plates fitted in
unpopulated positions.
Safety
considerations
In order to minimise the risk of toppling, all PCU cabinets must be populated starting at
the bottom of the cabinet. Up to three PCUs can be mounted per cabinet.
Each fully populated PCU weighs up to 32 kg. Observe correct lifting precautions when
handling PCUs.
Lifting equipment must be used unless there are sufficient personnel to ensure that
health and safety regulations are not breached.
To ensure correct cooling in the cabinet and to prevent re–circulation of warm air, rear
blanking panels must be fitted to unpopulated PCU mounting positions in swing frame
cabinets.
Fitting the cable

guide
The cable guide should be fitted before mounting the PCU in the cabinet.
To fit the cable guide:
1. Remove and retain the four screws securing the PCU power distribution module.
DO NOT remove the power distribution module.
2. Secure the cable guide to the PCU by fitting to the power distribution module with
the four previously retained screws.
3. Repeat for each PCU to be mounted in the cabinet.

VERSION 1 REVISION 0 Mounting the PCU in a cabinet
Cable guide
BSS101_M3Ch5_4

Fitting a PCU into a cabinet VERSION 1 REVISION 0
Fitting a PCU into a cabinet

PCU cabinets must be populated starting at the bottom of the cabinet and working up.
Two people should perform the following steps to avoid personal injury or damage to the
equipment.
Mounting the PCU in the top position is difficult due to the height of the lift.
Use lifting equipment unless there are sufficient personnel to ensure that health and
safety regulations are not breached.
Mounting a PCU
in a static frame
cabinet
To mount the PCU in a static frame cabinet:
1. Remove the aesthetic bay panel from the PCU mounting position, if necessary.
2. Fit the cable guide as described previously in Fitting the cable guide
3. Place the PCU onto the runners of the lowest available position and slide it into
the cabinet.
4. Secure the PCU to the rack using eight M6 torx screws, and tighten to the torque
specified in the service manual
5. Repeat steps 1 to 4 for each remaining PCU to be installed.
6. Ensure aesthetic bay panels are fitted in all unpopulated PCU mounting positions.
Mounting a PCU
in a swing frame
cabinet
To mount the PCU in a swing frame cabinet:
Attempting to mount a PCU into a free swinging frame could cause injury and/or damage
to the equipment. Ensure the swing frame is closed and locked before mounting the
PCU.
To prevent re-circulation of warm air in the swing frame cabinet and ensure correct
cooling of PCU equipment, rear blanking plates must be fitted to any unpopulated PCU
mounting position.
1. Remove the aesthetic bay panel and rear blanking plate from the PCU mounting
position, if necessary.
2. Fit the cable guide.
3. Place the PCU onto the lowest shelf available and slide it into the cabinet.
4. Secure the PCU to the rack using eight M6 Torx screws, and tighten to the torque
specified in the service manual.
5. Repeat steps 1 to 4 for each remaining PCU to be installed.
6. Remove the transit screw from the upper front left corner of each populated
swing frame.
7. Ensure aesthetic bay panels and rear blanking plates are fitted in all unpopulated
PCU mounting positions.

VERSION 1 REVISION 0 Fitting a PCU into a cabinet
Installing the PCU into a cabinet
BSS101_M3Ch5_5

Fitting E1 interface panels VERSION 1 REVISION 0

There is one E1 interface panel for each PCU.
E1 interface
panel options
The PCU E1 interface panel consists of three T43/BIB board assemblies and three 6 way
RJ45 connectors on a mounting panel, with space left for a future upgrade to four boards
and connectors.
In the static frame cabinet the E1 interface panels are mounted horizontally behind each
PCU, and are accessed through the rear door.
Static frame
cabinet E1
interface panel
To fit E1 interface panels in a static frame cabinet PCU:
1. Open the cabinet rear door.
2. Position the E1 power input mounting panel on the frame of the cabinet.
3. Secure the E1 interface panel using four M6 Torx screws, and tighten to the
torque specified in service manual
4. Repeat steps 1 and 3 for all PCUs.
Swing frame
cabinet E1
interface panel
In the swing frame cabinet the E1 interface panels are mounted vertically, to the left of
each installed PCU, and fixed to the cabinet rear racking inside the cabinet. The PCU
swing frame must be open to provide access to the E1 interface panels.
Swing frame
cabinet E1
interface panel
procedures
To fit E1 interface panels in a swing frame cabinet PCU:
1. Unlock and open the swing frame.
2. Position the E1 power input mounting panel on the frame of the cabinet.
3. Secure the E1 interface panel using four M6 Torx screws, and tighten to the
torque specified in the service manual.
4. Close and lock the swing frame.
5. Repeat steps 1 to 4 for all PCUs.

VERSION 1 REVISION 0 Fitting E1 interface panels
E1 interface panels
SIX WAY RJ45

CONNECTORS
T43/BIB
BOARD
ASSEMBLIES
PCU E1 interface panel

E1 interface
panels
Rear view of PCU static frame

cabinet, showing E1 interf
panels
E1 interface
panels
Position of E1 interface panels

in a swing frame cabinet
BSS101_M3Ch5_6

Connecting the E1 cables VERSION 1 REVISION 0
Connecting the E1 cables
T43 connections
Connection is made using a 37–pin D–type connector to the interface panel and twelve
type 43 coaxial connectors to the external E1/T1 circuit lines.
BIB connections
Connection is made using a 37–pin D–type connector to both the interface panel and the
external PCM circuit lines.

VERSION 1 REVISION 0 Connecting the E1 cables
E1 connections
J0
Type 43 interconnect board (T43)
J8 J4
J14 J10
J16 J2
J13 J11
J7 J1
J5
J17
BSS101_M3Ch5_7
Table 3-1 T43 interconnections

T43/BIB function Coaxial connector number RJ45
Tx 1/Rx 1 J1/J2 1
Tx 2/Rx 2 J4/J5 2
Tx 3/Rx 3 J7/J8 3
Tx 4/Rx 4 J10/J11 4
Tx 5/Rx 5 J13/J14 5
Tx 6/Rx 6 J16/J19 6
T17
Balanced-line interconnect board (BIB)
T7 T8 T14 T16
T4 T5 J1 T11 T13
T10
T1 T2
J0
BSS101_M3Ch5_8
Table 3-2 BIB interconnections

T43/BIB function Connector J1 pin number RJ45
Tx 1 1(+ve)/ 20 (–ve) 1
Rx 1 2(+ve)/ 21 (–ve)
Tx 2 4(+ve)/ 23 (–ve) 2
Rx 2 5(+ve)/ 24 (–ve)
Tx 3 7(+ve)/ 26 (–ve) 3
Rx 3 8(+ve)/ 27 (–ve)
Tx 4 10(+ve)/ 29 (–ve) 4
Rx 4 11(+ve)/ 30 (–ve)
Tx 5 13(+ve)/ 32 (–ve) 5
Rx 5 14(+ve)/ 33 (–ve)
Tx 6 16(+ve)/ 35 (–ve) 6
Rx 6 17(+ve)/ 36 (–ve)

Connecting the digital interface cable loom to the PCU VERSION 1 REVISION 0
Introduction to
digital loom
connection
The digital interface cable connects three types of digital signal to the PCU:
The GPRS data stream (LAPD protocol), GPRS signalling link (GSL), to the BSC.
The GPRS data stream (TRAU protocol), GDS (TRAU), to the BSC.
The Gb link (GBL) to the SGSN.
The GSL, the GDS (TRAU) and the Gb interface connect through DPROC transition
modules to PCI mezzanine cards (PMC).
E1 cables from the BSC, carrying GSL are connected through transition module ports to
one of the two PMCs, mounted on a PICP configured DPROC.
GDS links
E1 cables from the BSC, carrying GDS (TRAU), can be connected to:
The other PMC as the GSL and/or:
To the PMC mounted on PRP configured DPROCs
Gb links
The Gb links are connected through transition module ports to, (Each Gb link can carry
30 time slots):
The other PMC mounted on the same PICP configured DPROC as the GSL, or
To either PMC on a separate PICP DPROC.
Default GSL
The connection for GSL E1 links to the BSC for software download is:
Default, PCU slot one (rear), PMC socket one, Transition module port 1A (link 0)
time slot 1.
Secondary option, PCU slot two (rear), PMC socket one, Transition module port
1A (link 0) time slot 1.
A PMC module with Gb links cannot interface GDS or GSL.
Only one GDS (TRAU) link can be connected to each PRP mounted PMC card.
The routeing for the digital interface cable loom is dependent on the cabinet type.
Shown opposite is a minimum configuration, for maximum configurations refer to service
manual.

VERSION 1 REVISION 0 Connecting the digital interface cable loom to the PCU
Digital cable connection minimum configuration

Table 1–3 provides E1 interface connection information, for maximum card
configuration with coding schemes 1, 2, 3 & 4:
Table 1–3 E1 interface connection (maximum configuration)
T43/BIB T43/BIB Function RJ45 Cable TM location
board Ident ident and port
1 Tx 1, Rx 1 (GSL link) E1 A1 cPCI 1 Card 1 Port 1A
Tx 2, Rx 2 (GSL link) E1 A2 cPCI 2 Card 2 Port 1A
Tx 3, Rx 3 (Gb link) E1 A3 cPCI 3 Card 1 Port 2A
2 Tx 1, Rx 1 (GDS TRAU) E1 B1 cPCI 7 Card 4 Port 1A
Tx 2, Rx 2 (GDS TRAU) E1 B2 cPCI 8 Card 4 Port 2A
3 Tx 1, Rx 1 (GDS TRAU) E1 C1 cPCI 13 Card 11 Port 1A
Tx 2, Rx 2 (GDS TRAU) E1 C2 cPCI 14 Card 11 Port 2A
4 Tx 1, Rx 1 (GDS TRAU) E1 D1 cPCI 19 Card 14 Port 1A
Tx 2, Rx 2 (GDS TRAU) E1 D2 cPCI 20 Card 14 Port 2A
Tx 6, Rx 6 (GDS TRAU) E1 D6 cPCI 24 Card 16 Port 2A BSS101_M3Ch5_9
REAR VIEW OF
E1 CPX 8216 PORT
TRANSITION MODULE
INTERFACE 2B
PANEL
PORT
2A
PORT
1B
PORT
1A
REAR OF CHASSIS
BSS101_M3Ch5_10
DIGITAL INTERFACE CABLE

Digital cable connections VERSION 1 REVISION 0
Digital cable connections
Static frame
cabinet digital
cable connection
procedure
To fit the digital interface cable loom in a static frame cabinet:
1. Connect the digital interface cable loom to the appropriate RJ 45 connector on
the E1 interface board
2. Route the cable loom around the cabinet, from the E1 interface panel down the
cabinet rail and through the cable tidy brackets mounted behind and below the PCU,
securing to the cabinet rail and brackets using cable ties.
3. Extract individual cables from the loom trough the cable tidy brackets, at the
appropriate point, and loop across to the upper section of the PCU cable guide and
secure with cable ties.
4. Connect the individual cables of the digital interface cable loom to the appropriate
ports on the DPROC cards in the PCU chassis.
5. Repeat steps 1 to 4 until all installed PCUs have been connected.
Swing frame
cabinet digital
cable connection
procedures
1. Unlock, open and secure the swing frame.
2. Connect the digital interface cable loom to the appropriate locations on the E1
interface board.
3. Route the cable loom around the cabinet, as subsequently described in service
manual Use cable ties to secure the cable loom to the cabinet frame and rails,
the cable tray and the PCU cable guide.
4. Connect the individual cables of the digital interface cable loom to the appropriate
ports on the DPROC cards in the PCU chassis.
6. Repeat steps 1 to 5 until all PCUs have been connected.
For further details on routeing the digital cable loom refer to service manual.

VERSION 1 REVISION 0 Digital cable connections
Static Frame Cabinet Digital Cable Connection Procedure

Cabinet
rail
E1
Interface
panel
Cable
tidy
brackets PCU cable
guide BSS101_Mod3_Ch5_11a
Swing Frame Cabinet Digital Cable Connection Procedure
VIEW OF
E1 INTERFACE TRANSITION
PANEL MODULE
I/O ports
PORT
2B
PORT
PORT
2A
T43/BI 6 way 1B
B RJ45s
boards PORT
1A
Cable
tray
PCU cable
guide
PCU shelf
Swing cable
frame channel
rail entry
BSS101_M3Ch5_11

Fitting power input switches and mounting panels VERSION 1 REVISION 0

Power input
switching
Fitting ac power input switches to static frame cabinet.
Fitting dc power input switches to static frame cabinet.
Fitting power input switches to swing frame cabinet.
Swing frame power input cable routeing.
Power input
switching
options
PCUs are supplied with power input switch and cable assemblies relevant to the input
power requirements of the PCU. Two options are available,
dc power input switch and cable assembly.
ac power input switch and cable assembly.
Static frame
cabinet ac option
The ac power input switch and cable assemblies for a static frame cabinet are mounted
on a power distribution mounting bracket fitted to the frame of the cabinet. The mounting
bracket is located in the rear of the cabinet, near floor level, and is accessed through the
rear door.
Static frame
cabinet dc option
The dc power input switch and cable assemblies for a static frame cabinet are mounted
on power input switch mounting panels fitted to the rear left frame of the cabinet. These
mounting panels are located in the rear of the cabinet, adjacent to the PCU, and are
accessed through the rear door.
Swing frame
cabinet option
The power input switch and cable assemblies are fitted to power input switch mounting
panels and secured to the frame of the cabinet. The panels are located to the left of the
swing frames at the front of the cabinet. A dc mounting has cut outs for two dc power
input switching panels and an ac mounting has a single cut out.
Static frame
cabinet power
distribution
In the static frame cabinet the ac power input switch and cable assemblies are mounted
on a power distribution mounting bracket behind the lower PCU, and are accessed
through the rear door. The length of the cable assembly attached to an ac power input
switch is dependent upon the position of the associated PCU within the cabinet. The
cables are routed through the cabinet along the left vertical cabinet rail and secured with
cable ties.

VERSION 1 REVISION 0 Fitting power input switches and mounting panels
PCU power input switching panels
1 1
0 0
dc power input switch and cable ac power input switch and cable
assembly front panel assembly front panel
BSS101_M3Ch5_12

Fitting ac power input switches to static frame cabinet VERSION 1 REVISION 0
Fitting ac power input switches to static frame cabinet

To fit ac power input switch and cable assemblies in a static frame PCU cabinet:
1. Select the power input switch and cable assembly with the longest cable for the
top PCU.
2. Fit the ac power input switch front panel to the left most available position on the
power distribution mounting bracket, feeding the cable through the rear of the
panel.
3. Secure the power input switch front panel using two M6 Torx screws, and tighten
to the torque specified in the service manual.
4. Retain the assorted spring clips and pillars for use in Connecting external ac
power cables to cabinet
5. Route the cable up the left vertical cabinet rail, securing with the supplied cable
ties.
6. Select the power input switch and cable assembly with the medium length cable
assembly for the middle PCU.
7. Repeat steps 2 to 5 to fit the switch and cable assembly.
8. Select the power input switch and cable assembly with the shortest length cable
assembly for the bottom PCU.
9. Repeat steps 2 to 5 to fit the switch and cable assembly.

VERSION 1 REVISION 0 Fitting ac power input switches to static frame cabinet
PCU static frame ac power distribution mounting bracket
Cabinet rail
ac Power distribution
mounting bracket
BSS101_M3Ch5_13

Fitting dc power input switches to static frame cabinet VERSION 1 REVISION 0
Fitting dc power input switches to static frame cabinet

To fit dc power input switch and cable assemblies in a static frame PCU cabinet:
1. Open the rear door of the cabinet.
2. Fit the power input mounting panel to the left side cabinet racking member, using
four M6 screws.
3. Fit the power input switch and cable assembly to the power input mounting panel.
to the torque specified in service manual.
5. Route the power cable from the back of the switch mounting panel across the
rear of the PCU along the lower part of the cable guide to the appropriate socket
on the PCU power distribution module, and secure with cable ties.
6. Connect the three pin plug to the Amp type socket on the PCU power distribution
module.
7. Repeat step 3 to step 6 for the second power input switch and cable assembly.
8. Repeat step 2 to step 7 for each installed PCU.

VERSION 1 REVISION 0 Fitting dc power input switches to static frame cabinet
Static frame (rear view) cabinet dc switch mounting
Static frame
dc switch
mounting panel
Cable guide
BSS101_M3Ch5_14

Swing frame cabinet power input switch mounting panel VERSION 1 REVISION 0
Swing frame cabinet power input switch mounting panel

There is one power input switch mounting panel for each PCU. In the swing frame
cabinet the switch mounting panels are fitted to the cabinet frame at the left of each
swing frame.
Fitting power
input switches to
swing frame
cabinet
To fit power input switch and cable assemblies in a swing frame PCU cabinet:
1. Unlock and open the swing frame. Secure in the maximum open position.
2. Fit the power input mounting panel to the studs on the left side cabinet frame.
3. Secure the power input mounting panel using 10 mm nuts, and tighten to the
torque specified in the service manual.
4. Fit the power input switch and cable assembly to the power input mounting panel.
to the torque specified in the service manual.
6. If ac installation, retain the assorted spring clips and pillars for use in Connecting
external ac power cables to cabinet.
7. Route the power input cable around the cabinet as subsequently described in the
service manual.
8. Connect the three pin plug to the socket on the PCU power distribution module,
(Amp type on dc or IEC 320 on ac). Cabling should be routed as described to
enable correct operation of the swing frame and prevent cable damage.
9. Repeat steps 4 to 8 for the second power input switch and cable assembly if
installing a dc PCU.
11. Repeat steps 1 to 10 for each installed PCU.

VERSION 1 REVISION 0 Swing frame cabinet power input switch mounting panel
Power input mounting panels in a swing frame cabinet
Power input mounting panels,

ac option with single cut out
shown.
(The third panel and mounting
is hidden by the open swing
frame)
BSS101_M3Ch5_15

Swing frame power input cable routeing VERSION 1 REVISION 0
Swing frame power input cable routeing

The diagram opposite shows an ac power input cable, two dc cables would be used in a
dc cabinet, with the dc connections to the PCU being made through the two circular
holes in the rear cable mounting bracket.
The routeing is identical for all PCUs mounted in swing frame cabinets.
To route the power input cable in a swing frame cabinet refer service manual and:
1. Lay the power cable along the left side cabinet rail towards the rear, and secure
with cable ties.
2. Route the cable across to the right side of the cabinet in the front cable tray, and
3. Lay the power cable along the right side cabinet rail towards the front and pass
through the swing frame vertical rail cable entry hole.
4. Pass the power cable through the narrow section, nearest the PCU, of the PCU
shelf integral cable channel.
5. Ensure that there is sufficient slack in the cable at rail entry point to allow proper
pivoting of the swing frame, without causing damage to the cable. Secure the
power cable to the right side cabinet rail with cable ties.
6. Route the power cable across the rear of the PCU along the lower part of the
cable guide to the appropriate socket on the PCU power distribution module, and

VERSION 1 REVISION 0 Swing frame power input cable routeing
Swing frame power input cable routeing
PCU cable
guide
PCU shelf
Power input cable channel
switch
1
0
Swing frame
Cable tray rail entry
BSS101_M3Ch5_16

Earthing and transient protection VERSION 1 REVISION 0
Site earthing
Refer to the Grounding guidelines for cellular radio installations 68P81150E62, for
detailed earthing information.
Each cabinet must be earthed separately and not daisy chained together.
The PCU site equipment must be earthed (in the same common earth point as its
power source).
Provision should be made for routeing earthing lines into the site and to the cabinet
before beginning the installation of the system cabinets.
There is an earthing bar located in each cabinet.
Refer to the site–specific documentation for detailed site earthing information.
Each component within the cabinet must have supplementary earth bonding
connections to the cabinet earth bar.
The cabinet earth bar must be electrically connected to the master earth bar.
Transient
protection
All E1/T1 lines connected to Motorola equipment have secondary transient protection as
part of the BIB or T43 board. Ensure that the receive and transmit antenna connections
to the building are fed through coaxial electromagnetic protection (EMP) devices.

VERSION 1 REVISION 0 Earthing and transient protection
Static frame ac cabinet earth bonding

CPX8216
CPX8216
Connect to “Master /
External” Earth Bar via
top and / or bottom of
CPX8216 cabinet earth bar
Power input
switching
panels
Operational & Safety Earth,

via 3–core power supply cord
Supplementary Earth Bond BSS101_M3Ch5_17
Static frame dc cabinet earth bonding

REAR VIEW
CPX8216
CPX8216
Inlet Connect to ªMaster /
Sockets Externalº Earth Bar via
top and / or bottom of
Safety earth with

optional dc adaptor kit
Operational & Safety earth connected Supplementary Earth

from 3-core power supply cord connection via cabinet
via cabinet earth bar earth bar BSS101_M3Ch5_17

Cabinet earth bar connection VERSION 1 REVISION 0
Cabinet earth bar connection

The cabinet earth connection bar must be connected to a suitable external earth
connection and then the PCU Chassis earths must be connected to the cabinet earth
connection bar. This must be carried out before connecting the input power supply
cables.
To connect cabinet earths:
1. Use the installed 10 mm 2 core cross sectional area cable from the cabinet earth
bar to connect to the chassis earth point at the rear of each installed PCU.
2. Use the installed 6 mm 2 core cross sectional area cable from the cabinet earth
bar to connect to the earth stud on the rear of the power distribution mounting
bracket (ac static frame cabinet). Or connect to the earth stud on the rear of each
power input switch mounting panel (dc static frame cabinet and swing frame
cabinet).
3. Using the installed 6 mm 2 core cross sectional area cable from the cabinet earth
bar connect to the earth stud on each E1 interface panel.
4. Using 10 mm 2 core cross sectional area cable connect the cabinet earth bar to a
suitable external earth point.

VERSION 1 REVISION 0 Cabinet earth bar connection
Swing frame cabinet earth bonding
Safety earth
optional dc
adaptor kit
CPX8216
CPX8216
Connect to “Master /
Inlet External” Earth Bar via
Sockets top and / or bottom of
3–core power supply cord (inc operational & Safety

Earth)
Safety earth with

optional dc adaptor kit
Supplementary Earth
Bond BSS101_M3Ch5_18

Connecting external dc power cables to the cabinet VERSION 1 REVISION 0

In a static frame cabinet the external dc supply cables are routed from the sockets on the
front panels of the dc switches through the side of the dc switch mounting panel. The dc
cables are then routed inside the rear left rack member, to the selected cabinet cable
entry point (top or bottom), and secured with cable ties.
In a swingframe cabinet the external supply cables are routed from the sockets on the
front panels of the power input switches behind the power input mounting panels. The
supply cables are then routed along the left side cabinet structure, to the selected cabinet
cable entry point (top or bottom), and secured with cable ties.
Observe the following rules:
The negative (–48 V) power cable is blue.
The positive (0 V) return cable is black.
The earth cable is yellow/green
The dc version of the PCU has dual power supply input, the second input to provide
redundancy. The two dc power supply cables for each PCU are to be connected to
separate power sources.
Connection
procedure for
supplied dc
power cable
Do not make dc input power connections to the external dc power source at this time.
Connecting to external power source is the final installation procedure.
To connect supplied dc power supply cable:
1. Connect supplied dc power cable to socket on front panel of power input switch
and cable assembly.
2. Route the supplied dc power cable through cabinet, securing inside cabinet rear
left racking member with cable ties (static frame) or secured to cabinet left side
structure (swing frame), to the cabinet cable entry point.
3. Route cable to the power source using a cable trough or conduit.
4. Repeat steps 1 to 3 for each dc power input switch installed in the cabinet.
Note: power cable supplied is 10 metres long, if longer cable required use Motorola cable
kit (length of cable is limited to cable diameter).

VERSION 1 REVISION 0 Connecting external dc power cables to the cabinet
Connection procedure for supplied dc power cable
1. Connect supplied dc power cable to socket on front panel of

power input switch and cable assembly.
2. Route the supplied dc power cable through cabinet, securing

inside cabinet rear left racking member with cable ties (static
frame) or secured to cabinet left side structure (swing frame),
to the cabinet cable entry point.
3. Route cable to the power source using a cable trough or

conduit.
4. Repeat steps 1 to 3 for each dc power input switch installed in

the cabinet.

Connecting external ac power cables to the cabinet VERSION 1 REVISION 0

External cable routeing.
Introduction to ac detachable power supply cord/appliance coupler.
Connection procedure for ac detachable power supply cord/appliance coupler.
Take note of local legislation!
External ac cable
routeing
An adequate means should be provided for routeing cables from the power source to the
equipment, such as a cable trough or conduit.
The current–carrying capacity of an ac cable for continuous service is affected by all of
the following factors (reference IEC 364):
Ambient temperature.
Grouping.
Partial or total enclosure in thermal insulating material.
Frequency.
Static frame external ac supply cables are routed from the sockets on the front panels of
the ac switches, along the cabinet rails, secured by cable ties, to the selected cabinet
cable entry point (top or bottom).
In a swingframe cabinet the external supply cables are routed from the sockets on the
front panels of the power input switches behind the power input mounting panels. The
supply cables are then routed along the left side cabinet structure, to the selected cabinet
cable entry point (top or bottom), and secured with cable ties.
Connection
procedure for ac
detachable
power supply
cord/appliance
coupler
Do not make ac input power connections to the external ac power source at this time.
Connecting to power source is the final installation procedure.
To connect an ac detachable power supply cord/appliance coupler:
1. Connect external ac connector to IEC 320 socket on front panel of power input
switch and cable assembly.
2. Select appropriate length of spring clip and pillars, retained from Fitting power
input switches and mounting panels, to secure IEC 320 plug of power supply
cord/appliance coupler.
3. Fit selected pillars and spring clip to ac power input switch front pansl.
4. Route cable through cabinet to selected cable entry point, securing to cabinet
structure with cable ties.
6. Repeat step 1 to step 5 for each ac power input switch installed in the cabinet.

VERSION 1 REVISION 0 Connecting external ac power cables to the cabinet
Connection procedure for ac detachable power supply

cord/appliance coupler
1. Connect external ac connector to IEC 320 socket on front panel of power

input switch and cable assembly.
2. Select appropriate length of spring clip and pillars, retained from Fitting
power input switches and mounting panels, to secure IEC 320 plug of
power supply cord/appliance coupler.
3. Fit selected pillars and spring clip to ac power input switch front panels.
4. Route cable through cabinet to selected cable entry point, securing to

cabinet structure with cable ties.
6. Repeat step 1 to step 5 for each ac power input switch installed in the
cabinet.

Connecting to external power source VERSION 1 REVISION 0

At this point, ensure that:
The cabinet is not already connected to the external ac or dc power source.
The internal power cabling is connected.
The power cabling for connection to the external source is connected to the
cabinet and routed to the selected entry point.
The cabinet earth bar is connected to the main installation earth.
All PCU equipment supplementary bonding cables have been installed within the
cabinet.
Connecting dc
power
1. Turn off the external dc power source.
2. Use a digital voltmeter to ensure that power is not present.
3. Connect the earth lead of the supplied dc power cable, or dc adaptor cable
assembly, to the earth terminal of the external dc power source. See service manual.
4. Connect the positive lead of the supplied dc power cable, or dc adaptor cable
assembly, to the positive terminal of the external dc power source. See service manual.
5. Connect the negative lead of the supplied dc power cable, or dc adaptor cable
assembly, to the negative terminal of the external dc power source. See service manual.
Connecting ac
Power
1. Ensure the external power source is switched off.
3. Connect the plug end of ac detachable power supply cord/appliance coupler to
selected external power source outlet.

VERSION 1 REVISION 0 Connecting to external power source
Connecting dc power
1. Turn off the external dc power source.
3. Connect the earth lead of the supplied dc power cable, or dc adaptor

cable assembly, to the earth terminal of the external dc power source.
See service manual.
4. Connect the positive lead of the supplied dc power cable, or dc adaptor

cable assembly, to the positive terminal of the external dc power source.
See service manual.
5. Connect the negative lead of the supplied dc power cable, or dc adaptor

cable assembly, to the negative terminal of the external dc power source.
See service manual.
Connecting ac Power
1. Ensure the external power source is switched off.
3. Connect the plug end of ac detachable power supply cord/appliance

coupler to selected external power source outlet.

Powering up the Cabinet VERSION 1 REVISION 0
Powering up the Cabinet

This procedure assumes all previous procedures have been completed.
Ensure correct power supply sleds are fitted to match the supply source voltage.
Ensure that there is no obstruction to ventilation around the cabinet.
Power up
procedure
The following procedure should be carried out to power up the cabinet:
1. Ensure that each PCU power input module switch is in the off position.
2. Ensure that each power supply inlet switching panel switch is in the off position.
3. Ensure that each detachable power supply cord/appliance coupler has been
connected to the external power source.
4. Set the external power source isolation switch to on.
5. Ensure that any switched protective device is set to on.
6. Set each power supply inlet switching panel switch to on.
7. Set each PCU power input module switch to on.
8. Ensure that all PCU chassis cooling fans are operating and all installed cards
power up.
9. Inform the OMC–R that the PCU has been powered up.

VERSION 1 REVISION 0 Powering up the Cabinet
Power up procedure
1. Ensure that each PCU power input module switch is in the off position.
2. Ensure that each power supply inlet switching panel switch is in the off
position.
3. Ensure that each detachable power supply cord/appliance coupler has

been connected to the external power source.
4. Set the external power source isolation switch to on.
5. Ensure that any switched protective device is set to on.
6. Set each power supply inlet switching panel switch to on.
7. Set each PCU power input module switch to on.
8. Ensure that all PCU chassis cooling fans are operating and all installed
cards power up.
9. Inform the OMC–R that the PCU has been powered up.

Routine maintenance VERSION 1 REVISION 0
Routine maintenance
Cleaning fan
filters
When pulling the filter away from the fan resistance will be felt. This indicates that the fan
is functioning correctly.
To replace the fan filters
1. Pull the filter and filter frame away from the fan.
2. Remove the filter from the frame.
3. Insert a clean filter into the frame and refit to the fan.
To clean the fan filters:
1. Remove the dirty filter to a location were it is to be cleaned.
2. Wash the filter in warm soapy water and rinse thoroughly.
Do not wring the filter. Wringing may tear the material.
3. Gently squeeze the water out of the filter, and allow the filter to dry.
4. Inspect the filter for splits and holes. If the filter is damaged, discard it in
accordance with local guidelines. Undamaged filters are to be stored for re–use.
Post
maintenance
return to service
After any maintenance is completed, restore the PCU and cabinet to operational state
and notify the OMC–R of PCU availability.
Field replaceable
units (FRUs)
FRU list
The following is a list of FRUs in the PCU and associated cabinets:
The PCU power input module.
The power supply sleds.
The fans.
The alarm module.
The digital modules: MPROC, DPROC, PPB and transition modules
The E1 interface panel.
The T43/BIB assembly.
The input power switching panel.

VERSION 1 REVISION 0 Routine maintenance
Routine Maintenance
To replace the fan filters

1. Pull the filter and filter frame away from the fan.
2. Remove the filter from the frame.
3. Insert a clean filter into the frame and refit to the fan.
FRU list
• The PCU power input module.

• The power supply sleds.
• The fans.
• The alarm module.
• The digital modules: MPROC, DPROC, HSC/Bridge and transition
modules
• The E1 interface panel.
• The T43/BIB assembly.
• The input power switching panel.

Routine maintenance VERSION 1 REVISION 0

VERSION 1 REVISION 0 Glossary of Terms
Glossary of Terms

Glossary of Terms VERSION 1 REVISION 0

VERSION 1 REVISION 0 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 VERSION 1 REVISION 0
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.

VERSION 1 REVISION 0 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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance v

A VERSION 1 REVISION 0
AUT(H) AUThentication.
AUTO AUTOmatic mode.
vi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 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 BCU Power Supply Module.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance vii

B VERSION 1 REVISION 0
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.
viii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance ix

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

VERSION 1 REVISION 0 C
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.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service.
CFNRy Call Forwarding on No Reply supplementary service.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xi

C VERSION 1 REVISION 0
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.
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.
xii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 C
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).
CUG Closed User Group supplementary service.
Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xiii

D VERSION 1 REVISION 0
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.
xiv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 D
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xv

D VERSION 1 REVISION 0
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.
xvi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 E
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xvii

E VERSION 1 REVISION 0
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.
xviii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 F
F Interface Interface between MSC and EIR.

FA Fax Adaptor.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACCH Fast Associated Control Channel. A GSM dedicated control
channel which is associated with a TCH and carries control
information after a call is set up (see SDCCH).
FACCH/F Fast Associated Control Channel/Full rate.
FACCH/H Fast Associated Control Channel/Half rate.
FB Frequency correction Burst (see Frequency correction burst).
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).
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xix

F VERSION 1 REVISION 0
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.
xx BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 G
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxi

G VERSION 1 REVISION 0
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.
xxii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 H
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxiii

I VERSION 1 REVISION 0
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.
xxiv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 I
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxv

K VERSION 1 REVISION 0
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.
xxvi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 L
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxvii

L VERSION 1 REVISION 0
Location area An area in which a mobile station may move freely without
updating the location register. A location area may comprise
one or several base station areas.
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.
xxviii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 M
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).
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxix

M VERSION 1 REVISION 0
ME Mobile Equipment. Equipment intended to access a set of

GSM PLMN and/or DCS telecommunication services, but
which does not contain subscriber related information.
Services may be accessed while the equipment, capable of
surface movement within the GSM system area, is in motion
or during halts at unspecified points.
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).
s micro-second (10–6).
BCU 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.
xxx BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 M
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).
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxxi

M VERSION 1 REVISION 0
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.
xxxii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 N
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxxiii

N VERSION 1 REVISION 0
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).
xxxiv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 O
O
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxxv

O VERSION 1 REVISION 0
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.
xxxvi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 P
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxxvii

P VERSION 1 REVISION 0
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.
xxxviii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 P
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xxxix

Q VERSION 1 REVISION 0
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.
xl BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 R
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xli

R VERSION 1 REVISION 0
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.
xlii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 R
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xliii

S VERSION 1 REVISION 0
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.
xliv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 S
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xlv

S VERSION 1 REVISION 0
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.
xlvi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 S
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xlvii

T VERSION 1 REVISION 0
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.
xlviii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 T
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance xlix

T VERSION 1 REVISION 0
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.
l BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

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

V VERSION 1 REVISION 0
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.
lii BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 W
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.
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance liii

X VERSION 1 REVISION 0
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.
liv BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

VERSION 1 REVISION 0 Z
Z
ZC Zone Code
MOTOROLA LTD. 2000 BSS101/GSR5.1: Module 3: PCU Operations and Maintenance lv

Z VERSION 1 REVISION 0
lvi BSS101/GSR5.1: Module 3: PCU Operations and Maintenance MOTOROLA LTD. 2000

Bss 101

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Bss 101

Caricato da

Copyright:

Formati disponibili

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4

Motorola 1993 to 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage i

Copyrights, notices and trademarks

and MOTOROLA are trademarks of Motorola Inc.

ii BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage iii

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

iv BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage v

Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10

vi BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 1

Special key sequences

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

2 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

First aid in case of electric shock

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 3

Reporting safety issues

4 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

Warnings and cautions

Example and format

Example and format

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 5

6 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 7

Human exposure to radio frequency energy (PCS1900 only)

Power density (S)

8 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

Uncontrolled Environment Controlled Environment

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 9

    

10 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

Beryllium health and safety precautions

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 11

Product life cycle

12 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 13

Devices sensitive to static

14 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

Motorola GSM manual set

Category Name Catalogue

Category Name Catalogue

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 15

Category Name Catalogue

Category Name Catalogue

Category Name Catalogue

16 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 17

18 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage i

ii BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

GPRS Network Overview

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage i

ii BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage iii

iv BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI Cage 1–1

GPRS Network Overview

The Base Station

1–2 BSS101GSR5.1: Module 1: Introduction to PCI Cage MOTOROLA LTD. 2000

GPRS network entities