bss101

CHAPTER 2CPCI OVERVIEW

CHAPTER 3CPX8216 CAGE

CHAPTER 4CPCI DIGITAL CARD

CHAPTER 1GPRS NETWORK OVERVIEW

Cellular Infrastructure Group

BSS101GSR5.1MODULE 1: INTRODUCTION TO PCI CAGE

MODULE 3: PCU OPERATIONS ANDMAINTENANCE

FOR TRAINING PURPOSES ONLY

VERSION1 REVISION 0

FOR TRAININGPURPOSES ONLY

VERSION1REVISION 0

BSS101GSR5.1MODULE 1:

INTRODUCTION TOPCI CAGE

MODULE 3: PCUOPERATIONS AND

MAINTENANCE

BSS101GSR5.1MODULE 1: INTRODUCTION TO PCI

CAGEMODULE 3: PCU OPERATIONS AND

MAINTENANCE

�MOTOROLA LTD. 2000 BSS101GSR5.1: Module 1: Introduction to PCI CageModule 3: PCU Operations and Maintenance


i

VERSION1 REVISION 0

BSS101GSR5.1Module 1: Introduction to PCI Cage

Module 3: PCU Operations andMaintenance

� Motorola 1993 to 2000All Rights ReservedPrinted in the U.K.

VERSION1 REVISION 0

�MOTOROLA LTD. 2000BSS101GSR5.1: Module 1: Introduction to PCI CageModule 3: PCU Operations and Maintenance


ii

Copyrights, notices and trademarks

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computerprograms stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola certain exclusive rights for copyright computer programs, including theexclusive right to copy or reproduce in any form the copyright computer program. Accordingly, anycopyright Motorola computer programs contained in the Motorola products described in this documentmay 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 byimplication, estoppel or otherwise, any license under the copyrights, patents or patent applications ofMotorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a licenseagreement 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 bylaw. No part of the software or documentation may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any language or computer language, in any form or by anymeans, without prior written permission of Motorola.

AccuracyWhile reasonable efforts have been made to assure the accuracy of this document, Motorolaassumes no liability resulting from any inaccuracies or omissions in this document, or from the useof the information obtained herein. Motorola reserves the right to make changes to any productsdescribed herein to improve reliability, function, or design, and reserves the right to revise thisdocument and to make changes from time to time in content hereof with no obligation to notify anyperson of revisions or changes. Motorola does not assume any liability arising out of the applicationor use of any product or circuit described herein; neither does it convey license under its patentrights of others.

Trademarks

and MOTOROLA are trademarks of Motorola Inc.UNIX is a registered trademark in the United States and other countries, licensed exclusively throughX/Open Company Limited.Tandem , Integrity , Integrity S2 , and Non-Stop-UX are trademarks of Tandem ComputersIncorporated.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.

VERSION1 REVISION 0



iii

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

VERSION1 REVISION 0



iv

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 1GPRS 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme Rates 1–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS 52 Multiframe 1–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Structure 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2CPCI 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



v

Chapter 3CPX8216 Cage i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Objectives 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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 4CPCI Digital Cards i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 Objectives 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

VERSION1 REVISION 0



vi

Alarm Module 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm module overview 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Panel LED’s 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm board Operation 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

VERSION1 REVISION 0 General information



1

General information

Important notice

If this manual was obtained when you attended a Motorola training course, it will not beupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then corrections will be supplied automatically by Motorola in the form ofGeneral Manual Revisions (GMRs).

Purpose

Motorola Global System for Mobile Communications (GSM) Technical Education manualsare intended to support the delivery of Technical Education only and are not intended toreplace the use of Customer Product Documentation.

Failure to comply with Motorola’s operation, installation and maintenanceinstructions may, in exceptional circumstances, lead to serious injury or death.

WARNING

These manuals are not intended to replace the system and equipment training offered byMotorola, although they can be used to supplement and enhance the knowledge gainedthrough such training.

About thismanual

VERSION1 REVISION 0General information



2

Cross references

Throughout this manual, cross references are made to the chapter numbers and sectionnames. The section name cross references are printed bold in text.

This manual is divided into uniquely identified and numbered chapters that, in turn, aredivided into sections. Sections are not numbered, but are individually named at the topof each page, and are listed in the table of contents.

Text conventions

The following conventions are used in the Motorola GSM manuals to represent keyboardinput 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 environmentalvariables 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 isidentified with the ↵ symbol on both the X terminal andthe SPARCstation keyboards. The SPARCstationkeyboard Return key is also identified with the wordReturn.

VERSION1 REVISION 0 First aid in case of electric shock



3

First aid in case of electric shock

Warning

Do not touch the victim with your bare hands until the electric circuit isbroken.Switch off. If this is not possible, protect yourself with dry insulatingmaterial and pull or push the victim clear of the conductor.

WARNING

Artificialrespiration

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, coverthe wound with a dry dressing.

3. Do not apply oil or grease in any form.

VERSION1 REVISION 0Reporting safety issues



4

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) andfollow 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



5

Warnings and cautions

Introduction

The following describes how warnings and cautions are used in this manual and in allmanuals 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, forexample, the use of adhesives and solvents, as well as those inherent in the equipment.

Example and format

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 orunterminated fibre optic cables connected to data in/out connectors.

WARNING

Cautions

Definition

A caution means that there is a possibility of damage to systems, or individual items ofequipment within a system. However, this presents no danger to personnel.

Example and format

Do not use test equipment that is beyond its calibration due date when testingMotorola base stations.

CAUTION

VERSION1 REVISION 0General warnings



6

General warnings

Introduction

Observe the following warnings during all phases of operation, installation andmaintenance of the equipment described in the Motorola GSM manuals. Failure tocomply with these warnings, or with specific warnings elsewhere in the Motorola GSMmanuals, violates safety standards of design, manufacture and intended use of theequipment. Motorola assumes no liability for the customer’s failure to comply with theserequirements.

Warning labelsPersonnel working with or operating Motorola equipment must comply with any warninglabels fitted to the equipment. Warning labels must not be removed, painted over orobscured in any way.

Specificwarnings

Warnings particularly applicable to the equipment are positioned on the equipment andwithin the text of this manual. These must be observed by all personnel at all times whenworking with the equipment, as must any other warnings given in text, on the illustrationsand on the equipment.

High voltageCertain Motorola equipment operates from a dangerous high voltage of 230 V ac singlephase or 415 V ac three phase mains which is potentially lethal. Therefore, the areaswhere the ac mains power is present must not be approached until the warnings andcautions 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 mustbe set to off and locked.

Within the United Kingdom (UK) regard must be paid to the requirements of theElectricity at Work Regulations 1989. There may also be specific country legislationwhich need to be complied with, depending on where the equipment is used.

RF radiationHigh RF potentials and electromagnetic fields are present in the base station equipmentwhen in operation. Ensure that all transmitters are switched off when any antennaconnections have to be changed. Do not key transmitters connected to unterminatedcavities or feeders.

Refer to the following standards:

� ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.

� CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields HighFrequency (10kHz to 300GHz).

Laser radiationDo not look directly into fibre optic cables or optical data in/out connectors. Laserradiation can come from either the data in/out connectors or unterminated fibre opticcables connected to data in/out connectors.

VERSION1 REVISION 0 General warnings



7

Liftingequipment

When dismantling heavy assemblies, or removing or replacing equipment, the competentresponsible person must ensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations. When equipments have to bemanhandled, reference must be made to the Manual Handling of Loads Regulations1992 (UK) or to the relevant manual handling of loads legislation for the country in whichthe equipment is used.

Do not ...... substitute parts or modify equipment.

Because of the danger of introducing additional hazards, do not install substitute parts orperform any unauthorized modification of equipment. Contact Motorola if in doubt toensure 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 materialBeryllium or its oxide Beryllia or both. These materials are especially hazardous if:

� Beryllium materials are absorbed into the body tissues through the skin, mouth, ora 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.

VERSION1 REVISION 0Human exposure to radio frequency energy (PCS1900 only)



8

Human exposure to radio frequency energy (PCS1900 only)

IntroductionThis equipment is designed to generate and radiate radio frequency (RF) energy. Itshould be installed and maintained only by trained technicians. Licensees of the FederalCommunications Commission (FCC) using this equipment are responsible for insuringthat its installation and operation comply with FCC regulations designed to limit humanexposure to RF radiation in accordance with the American National Standards InstituteIEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to HumanExposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.

DefinitionsThis standard establishes two sets of maximum permitted exposure limits, one forcontrolled environments and another, that allows less exposure, for uncontrolledenvironments. These terms are defined by the standard, as follows:

Uncontrolled environmentUncontrolled environments are locations where there is the exposure of individuals whohave no knowledge or control of their exposure. The exposures may occur in livingquarters or workplaces where there are no expectations that the exposure levels mayexceed those shown for uncontrolled environments in the table of maximum permittedexposure ceilings.

Controlled environment

Controlled environments are locations where there is exposure that may be incurred bypersons who are aware of the potential for exposure as a concomitant of employment, byother cognizant persons, or as the incidental result of transient passage through areaswhere analysis shows the exposure levels may be above those shown for uncontrolledenvironments but do not exceed the values shown for controlled environments in thetable of maximum permitted exposure ceilings.

Maximumpermittedexposures

The maximum permitted exposures prescribed by the standard are set in terms ofdifferent parameters of effects, depending on the frequency generated by the equipmentin question. At the frequency range of this Personal Communication System equipment,1930-1970MHz, the maximum permitted exposure levels are set in terms of powerdensity, whose definition and relationship to electric field and magnetic field strengths aredescribed by the standard as follows:

Power density (S)Power per unit area normal to the direction of propagation, usually expressed in units ofwatts per square metre (W/m2) or, for convenience, units such as milliwatts per squarecentimetre (mW/cm2). For plane waves, power density, electric field strength (E) andmagnetic field strength (H) are related by the impedance of free space, 377 ohms. Inparticular,

� ��

��

where E and H are expressed in units of V/m and A/m, respectively, and S in units ofW/m2. Although many survey instruments indicate power density units, the actualquantities measured are E or E2 or H or H2.

VERSION1 REVISION 0 Human exposure to radio frequency energy (PCS1900 only)



9

Maximumpermittedexposureceilings

Within the frequency range, the maximum permitted exposure ceiling for uncontrolledenvironments is a power density (mW/cm2) that equals f/1500, where f is the frequencyexpressed in MHz, and measurements are averaged over a period of 30 minutes. Themaximum permitted exposure ceiling for controlled environments, also expressed inmW/cm2, is f/300 where measurements are averaged over 6 minutes. Applying theseprinciples to the minimum and maximum frequencies for which this equipment is intendedto be used yields the following maximum permitted exposure levels:

Uncontrolled Environment Controlled Environment

1930MHz 1970MHz 1930MHz 1970MHz

Ceiling 1.287mW/cm2 1.313mW/cm2 6.433mW/cm2 6.567mW/cm2

If you plan to operate the equipment at more than one frequency, compliance should beassured at the frequency which produces the lowest exposure ceiling (among thefrequencies 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 demonstratingcompliance, but this equipment operates at power levels orders of magnitude higher, andthe exclusion is not applicable.

Whether a given installation meets the maximum permitted exposure ceilings depends, inpart, upon antenna type, antenna placement and the output power to which thisequipment is adjusted. The following example sets forth the distances from the antennato which access should be prevented in order to comply with the uncontrolled andcontrolled environment exposure limits as set forth in the ANSI IEEE standards andcomputed above.

VERSION1 REVISION 0Human exposure to radio frequency energy (PCS1900 only)



10

Examplecalculation

For a base station with the following characteristics, what is the minimum distance fromthe 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 distancefrom 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 frommW/cm2 to W/m2.

The above result applies only in the direction of maximum radiation of theantenna. Actual installations may employ antennas that have defined radiationpatterns and gains that differ from the example set forth above. The distancescalculated can vary depending on the actual antenna pattern and gain.

NOTE

Power densitymeasurements

While installation calculations such as the above are useful and essential in planning anddesign, validation that the operating facility using this equipment actually complies willrequire making power density measurements. For information on measuring RF fields fordetermining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practicefor 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 bepurchased 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 thisequipment are urged to consult these standards in determining whether a giveninstallation complies with the applicable limits.

Other equipmentWhether a given installation meets ANSI standards for human exposure to radiofrequency radiation may depend not only on this equipment but also on whether theenvironments being assessed are being affected by radio frequency fields from otherequipment, the effects of which may add to the level of exposure. Accordingly, the overallexposure may be affected by radio frequency generating facilities that exist at the timethe 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 indetermining whether a particular installation meets the FCC requirements.

VERSION1 REVISION 0 Beryllium health and safety precautions



11

Beryllium health and safety precautions

Introduction

Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly inOxygen.

With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Berylliumcompounds and Beryllium metal are potentially highly toxic.

Health issues

Beryllium Oxide is used within some components as an electrical insulator. Captivewithin the component it presents no health risk whatsoever. However, if the componentshould 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 symptomsof Berylliosis are similar to Pneumonia and may be identified by all or any of thefollowing:

Mild poisoning causes fever, shortness of breath, and a cough that producesyellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucousmembranes of the nose, throat, and chest with discomfort, possibly pain, and difficultywith swallowing and breathing.

Severe poisoning causes chest pain and wheezing which may progress to severeshortness of breath due to congestion of the lungs. Incubation period for lung symptomsis 2–20 days.

Exposure to moderately high concentrations of Beryllium in air may produce a veryserious condition of the lungs. The injured person may become blue, feverish with rapidbreathing and raised pulse rate. Recovery is usual but may take several months. Therehave been deaths in the acute stage.

Chronic response. This condition is more truly a general one although the lungs aremainly affected. There may be lesions in the kidneys and the skin. Certain featuressupport the view that the condition is allergic. There is no relationship between thedegree of exposure and the severity of response and there is usually a time lag of up to10 years between exposure and the onset of the illness. Both sexes are equallysusceptible. The onset of the illness is insidious but only a small number of exposedpersons develop this reaction.

First aid

Seek immediate medical assistance. The casualty should be removed immediately fromthe exposure area and placed in a fresh air environment with breathing supported withOxygen where required. Any contaminated clothing should be removed. The casualtyshould be kept warm and at rest until medical aid arrives.

VERSION1 REVISION 0Beryllium health and safety precautions



12

Skin contact

Possible irritation and redness at the contact area. Persistent itching and blisterformations can occur which usually resolve on removal from exposure.

First aid

Wash area thoroughly with soap and water. If skin is broken seek immediate medicalassistance.

Eye contact

May cause severe irritation, redness and swelling of eyelid(s) and inflammation of themucous membranes of the eyes.

First aid

Flush eyes with running water for at least 15 minutes. Seek medical assistance as soonas possible.

Handlingprocedures

Removal of components from printed circuit boards (PCBs) is to take place only atMotorola approved repair centres.

The removal station will be equipped with extraction equipment and all other protectiveequipment necessary for the safe removal of components containing Beryllium Oxide.

If during removal a component is accidently opened, the Beryllium Oxide dust is to bewetted into a paste and put into a container with a spatula or similar tool. Thespatula/tool used to collect the paste is also to be placed in the container. The containeris then to be sealed and labelled. A suitable respirator is to be worn at all times duringthis operation.

Components which are successfully removed are to be placed in a separate bag, sealedand labelled.

Disposalmethods

Beryllium Oxide or components containing Beryllium Oxide are to be treated ashazardous waste. All components must be removed where possible from boards and putinto sealed bags labelled Beryllium Oxide components. These bags must be given to thesafety and environmental adviser for disposal.

Under no circumstances are boards or components containing Beryllium Oxide to be putinto the general waste skips or incinerated.

Product life cycleimplications

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 suchhazardous waste as part of its Total Customer Satisfaction philosophy and will arrangefor the most environmentally “friendly” disposal available at that time.

VERSION1 REVISION 0 General cautions



13

General cautions

Introduction

Observe the following cautions during operation, installation and maintenance of theequipment described in the Motorola GSM manuals. Failure to comply with thesecautions or with specific cautions elsewhere in the Motorola GSM manuals may result indamage to the equipment. Motorola assumes no liability for the customer’s failure tocomply with these requirements.

Caution labels

Personnel working with or operating Motorola equipment must comply with any cautionlabels fitted to the equipment. Caution labels must not be removed, painted over orobscured in any way.

Specific cautions

Cautions particularly applicable to the equipment are positioned within the text of thismanual. These must be observed by all personnel at all times when working with theequipment, as must any other cautions given in text, on the illustrations and on theequipment.

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 bymishandling. Wear an approved earth strap when adjusting or handling digital boards.

See Devices sensitive to static for further information.

VERSION1 REVISION 0Devices sensitive to static



14

Devices sensitive to static

Introduction

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer ofinsulation that is susceptible to damage from electrostatic charge. Such a charge appliedto the leads of the device could cause irreparable damage.

These charges can be built up on nylon overalls, by friction, by pushing the hands intohigh insulation packing material or by use of unearthed soldering irons.

MOS devices are normally despatched from the manufacturers with the leads shortedtogether, for example, by metal foil eyelets, wire strapping, or by inserting the leads intoconductive plastic foam. Provided the leads are shorted it is safe to handle the device.

Special handlingtechniques

In the event of one of these devices having to be replaced observe the followingprecautions 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 toreplace 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 cottonoverall is preferable.

� If possible work on an earthed metal surface. Wipe insulated plastic work surfaceswith an anti-static cloth before starting the operation.

� All metal tools should be used and when not in use they should be placed on anearthed surface.

� Take care when removing components connected to electrostatic sensitivedevices. These components may be providing protection to the device.

When mounted onto printed circuit boards (PCBs), MOS devices are normally lesssusceptible to electrostatic damage. However PCBs should be handled with care,preferably by their edges and not by their tracks and pins, they should be transferreddirectly from their packing to the equipment (or the other way around) and never leftexposed on the workbench.

VERSION1 REVISION 0 Motorola GSM manual set



15

Motorola GSM manual set

Introduction

The following manuals provide the information needed to operate, install and maintain theMotorola GSM equipment.

Generic manuals

The following are the generic manuals in the GSM manual set, these manuals arerelease dependent:

Categorynumber

Name Cataloguenumber

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 CommandReference

68P02901W23

GSM-100-403 Installation & Configuration: GSM SystemConfiguration

68P02901W17

GSM-100-423 Installation & Configuration: BSS Optimization 68P02901W43

GSM-100-501 Maintenance Information: Alarm Handling atthe OMC

68P02901W26

GSM-100-521 Maintenance Information: Device StateTransitions

68P02901W57

GSM-100-523 Maintenance Information: BSS FieldTroubleshooting

68P02901W51

GSM-100-503 Maintenance Information: GSM StatisticsApplication

68P02901W56

GSM-100-721 Software Release Notes: BSS/RXCDR 68P02901W72

Tandem OMC

The following Tandem OMC manuals are part of the GSM manual set for systemsdeploying Tandem S300 and 1475:

Categorynumber


GSM-100-202 Operating Information: OMC SystemAdministration

68P02901W13

GSM-100-712 Software Release Notes: OMC System 68P02901W71

VERSION1 REVISION 0Motorola GSM manual set



16

Scaleable OMC

The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals inthe GSM manual set:

Categorynumber


GSM-100-202 Operating Information: Scaleable OMC SystemAdministration

68P02901W19

GSM-100-413 Installation & Configuration: Scaleable OMCClean Install

68P02901W47

GSM-100-712 Software Release Notes: Scaleable OMCSystem

68P02901W74

Related manuals

The following are related Motorola GSM manuals:

Categorynumber


GSM-001-103 System Information: BSS Equipment Planning 68P02900W21

GSM-002-103 System Information: DataGen 68P02900W22

GSM-005-103 System Information: Advance OperationalImpact

68P02900W25

GSM-008-403 Installation & Configuration: Expert Adviser 68P02900W36

Service manuals

The following are the service manuals in the GSM manual set, these manuals are notrelease dependent. The internal organization and makeup of service manual sets mayvary, they may consist of from one to four separate manuals, but they can all be orderedusing the overall catalogue number shown below:

Categorynumber


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



17

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.

Cataloguenumber

The Motorola 68P catalogue number is used to order manuals.

Orderingmanuals

All orders for Motorola manuals must be placed with your Motorola Local Office orRepresentative. Manuals are ordered using the catalogue number. Remember, specifythe manual issue required by quoting the correct suffix letter.

VERSION1 REVISION 0Motorola GSM manual set



18

VERSION1 REVISION 0 Module 1 Objectives



i

Module 1 ObjectivesAt 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.

VERSION1 REVISION 0Module 1 Objectives



ii



i

Chapter 1

GPRS Network Overview

VERSION1 REVISION 0



ii

VERSION1 REVISION 0



iii

Chapter 1GPRS 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme Rates 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coding Scheme Rates 1–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS 52 Multiframe 1–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Structure 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

VERSION1 REVISION 0



iv

VERSION1 REVISION 0 Chapter 1 Objectives



1–1

Chapter 1 ObjectivesAt 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.

VERSION1 REVISION 0GPRS Network Overview



1–2

GPRS Network OverviewThe diagram opposite shows a simplified General Packet Radio Service (GPRS)network. Each network component is illustrated once, however, many of the componentswill occur several times throughout a network.

The principal network component groups are:

The GPRSSupport NodeComplex

The GPRS Support Node Complex is the main element in the GPRS infrastructure. It is ahigh performance, broadband packet switching node that provides connection andinterworking with various data networks, mobility management and delivery of datapackets to mobile stations. The GSN Network is made of the following componentgroups.

� CommHub – The CommHub is the central connection point for the components ina GPRS system. It provides LAN connectivity between GPRS components throughEthernet and WAN connectivity to data networks outside the GPRS system.

� ISS – The Integrated Support Services provides GPRS system components withthe current time, domain name translation and network information.

� GGSN – The Gateway GPRS Support Node provides network access to externalhosts so they can communicate with MSs. It also decapsulates and forwardsexternal data networks packets to the appropriate data network.

� SGSN – The Serving GPRS Support Node detects and tracks GPRS MSs in itsservice area and provides a reliable, secure data channel as the MS movesbetween cells.

OMC–GThe OMC-G enables operators to use an NT graphical user interface (GUI) whenmanaging the GPRS components. System operators use the OMC–G to configure andmonitor system components and view performance data.

The Base StationSystem (BSS)

The Base Station System provides the radio frequency link between the GPRS networkinfrastructure and mobile subscribers throughout the operational area. A BSS consists ofthree components:

� Base Station Controller (BSC)

� Base Station Transceiver (BTS)

� Packet Control Unit (PCU) – The Packet Control Unit (PCU) performs radiofunctions and GPRS network functions. It has interfaces to the OMC-R, BSC andthe SGSN.

The MobileStation (MS)

The MSs can belong to three classes A, B or C. The class determines whether GPRSand Circuit Switched services can be carried out at the same time or not. The mobilesare also divided into multislot classes that determine the mobile capability of sending andreceiving over multiple slots in a TDMA frame.

VERSION1 REVISION 0 GPRS Network Overview



1–3

GPRS network entities

Internet

Gi

Frame Relay

RXCDR MSC

PCU

BSC

BTS

SGSN

GGSNISS

Router

Com

mH

ub

BSS101_Mod1_Ch1_01

VERSION1 REVISION 0GPRS Interfaces



1–4

GPRS InterfacesGPRS has introduced new interfaces. These are listed below:

� Gn – GPRS Support Node back bone network – This interface connects the SGSNand 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 andthe 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 pointor could utilize the existing infrastructure of a Frame Relay provider.

The TCP/IP backbone (the Gn interface) connects the GSN entities together in theMotorola Solution – this is implemented using the Communications Hub which supportsvirtual LAN connections. The diagram opposite shows the logical connections of the GSNentities.

VERSION1 REVISION 0 GPRS Interfaces



1–5

Interfaces in a GSM/GPRS System

Frame Relay

TCP/IP Backbone

PDNTo another

PLMN

A

AbisGDS

(Motorola)

Gr

GsGb

Gn

Gn

Gn

Gp Gi

MSC

PCU

SGSN

BTS

GGSN

BSC

SGSN

BTSHLR

BSS101_Mod1_Ch1_02

VERSION1 REVISION 0GPRS Protocols



1–6

GPRS Protocols

SimplifiedProtocol stack

GPRS has been designed to carry packet data protocols from a public data network to amobile user. The Protocol stack can be simplified into 3 layers. When viewed in thismanner the GPRS system looks very similar to a computer network protocol stack (i.e. aTCP/IP stack).

As can be seen from Figure 1 the simplified protocol stack makes GPRS look like aconventional 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 beEthernet. In the Motorola GPRS system we do use Ethernet at the GSN but this shouldnot 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 dataprotocol 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 anetwork that the GGSN is connected to (via routers), though it is shown at the top of theGGSN stack.

Layer 2 between SGSN and GGSN

At Layer 2 of the GGSN or the SGSN we have several protocols. These exist to providea moving data connection (don’t forget the end user is mobile, unlike static usersconnected to a telephone line) and also to hide the IP datagrams so that we cantransport 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 overthe 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 themobile to BSS we have the air interface a radio link. From the BSS we have a WAN linkto the SGSN and from SGSN to GGSN we have an Ethernet (in most Motorola systems).

VERSION1 REVISION 0 GPRS Protocols



1–7

Simplified Network Protocol Stack

Layer 3

IP

Layer 2

SNDCP and LLCand RLC/MAC

Layer 1

GSM RF

Layer 2

RLC/MAC

Layer 1

GSM RF

Layer 2

and BSSGPand Network

Layer 1

E1

Layer 2

SNDCPand LLC

and BSSGPand Network

Layer 2

GTP andTCP/UDP

and IP

Layer 1

E1

Layer 1

Layer 1

Layer 3

IP

Layer 2

GTP andTCP/UDP

and IP

MS BSS SGSN GGSN

BSS101_Mod1_Ch1_03




1–8

GPRS CodingSchemes

In a GPRS network, there are several channel–coding schemes defined to operate overthe air interface and provide varying data rates to the end–user. In general, as themobile experiences better RF conditions, the coding scheme in use can be changedautomatically by the PCU to afford higher throughput. Essentially the differencesbetween coding schemes determine the amount of protection provided to the data. Thechannel 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 radioproperties experienced by the mobile station will dictate how efficient a given codingscheme is. When there is not much coding on the data (i.e. CS–3 and CS–4), a givenblock will generally not be received correctly in poor RF environments. It is the PCU’sresponsibility to calculate which coding scheme should be used. This decision is basedupon:

Downlink signal and interference level information provided by the MSduring 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 providedto the PCU by the channel coders within the BTS, are combined to define the C/I (Carrierto Interference) ratio for the given mobile station.

The data rates for the GPRS coding schemes are as follows:

Coding SchemeRates

Channel Coding Scheme Throughput

(Per TS)

ConvolutionalCoding 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




1–9

GPRS Coding Schemes

Sys102_1_14

CS4

CS1

CS2

CS3

Coding SchemeRates

Channel Coding Scheme Throughput

(Per TS)

Convolutional 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




1–10

GPRS 52Multiframe

The 52 frame structure shown opposite is a new frame. Its structure is totallydifferent from the existing 51 and 26 frame structures.

The 52 Multiframe does not have a rigid structure. Essentially the differentchannels are identified by message type. The Multiframe can carry controlchannels or data channels.

CONTROL CHANNELS TRAFFIC CHANNELS

PBCCH PDTCH

PPCH PACCH

PAGCH

PNCH




1–11

52 Multiframe Structure

BSS101_Mod1_Ch1_05

B0B1B2

B3B4B5

B6B7B8

B9B10B11

I

I

I

I

I = Idle frame

B(n) = 4 frame radio block

4 frames8 TS

0

1

2

3

4

5

6

7




1–12

Control ChannelStructure

GPRS uses one or more timeslots per call known as Packet Data Channel(PDCH). PDCHs are physical channels which consist of various logicalchannels.

Packet Common Control Channel (PCCH) – comprises logical channels for commoncontrol 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 uplinktransfer, 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 anMS prior to packet transfer.

Note: Resource Assignment for a downlink assignment can be sent on the PACCH if theMS 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 thenthe BCCH is used to broadcast Packet Data Specific Information.




1–13

Control Channel Structure

CCH

CCCH BCCH

RACH PCH/AGCH

PCCH

PBCCH

PCCH

PRACH PAGCH PNCHPPCH

BSS101_Mod1_Ch1_06

CBCH




1–14



i

Chapter 2

CPCI Overview

VERSION1 REVISION 0



ii

VERSION1 REVISION 0



iii

Chapter 2CPCI 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



iv




2–1


� 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.

VERSION1 REVISION 0The Peripheral Component Interconnect Bus



2–2

The Peripheral Component Interconnect Bus

History

Peripheral Component Interconnect (PCI) was originally developed in 1992 by Intel tosupport the x86 CPU architecture for personal computers.

They had maintained separate I/O addressing/memory addressing throughout theirprocessor range. The PCI specification was then a natural progression.

The PCI specification maintains the separation of memory and I/O addressing – that issystem I/O space and system memory space.

Various bodies exist to maintain and develop the PCI standards; PICMG developed theCompactPCI specification, which was first released on November of 1995.

CPCI evolved from PCI (signalling is a superset of PCI). In the PC the backplane isactive with CPU and memory, CPCI made the backplane passive (as well as definingnew signals and mechanical factors).

VERSION1 REVISION 0 The Peripheral Component Interconnect Bus



2–3

CPCI Evolution

BSS101_Mod1_Ch2_1a

Standard PC (active backplane)

PCI Card PCI Card

CPU

Memory

Motherboard

CPCI (passive backplane)

Memory

CPU

Backplane




2–4

PCI Bus

A PCI bus is used to connect together PCi compatible devices. This could be a processorboard, chip, graphics card or single board computer. The PCI bus can be found on theprocessor boards used in the Motorola GPRS solution as well as in the CPCI cages ofthe 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 andfunction numbers.

Addressing is achieved by using the address bus (which is also the data bus) and theCommand/Byte Enable bus (C/BE bus). The C/BE bus issues 4 bit commands todetermine if the address is IO, memory or configuration.

Command type C/BE 3 C/BE 2 C/BE 1 C/BE 0I/O read 0 0 1 0I/O write 0 0 1 1Mem read 0 1 1 0Mem write 0 1 1 1




2–5

PCI Addressing

Command type C/BE 3 C/BE 2 C/BE 1 C/BE 0I/O read 0 0 1 0I/O write 0 0 1 1Mem read 0 1 1 0Mem write 0 1 1 1

PCI Device

4 bit C/BE bus

BSS101_Mod1_Ch2_1




2–6

Command Codes

The command codes on the C/BE bus are presented on the bus at the same time thatthe address is placed onto the address/data bus.

The device can then distinguish what the address bus is referring to. There are manyother command codes than those shown previously. These would include the 0000command code. This is used for interrupt acknowledgement. Should a device issue anInterrupt then this command is returned indicating that the host is responding to theInterrupt 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 thedevice is on a PCI card.




2–7

C/BE Bus

BSS101_Mod1_Ch2_2

Address

A/D bus C/BE bus

I/O write

CPCI Card

PCIDevice

VERSION1 REVISION 0Memory IO and Configuration Access



2–8

Memory IO and Configuration Access

DEVSEL/IDSEL

For memory and IO transactions the C/BE bus determines what type of access isrequired, for example, IO read, mem write etc. All of the devices on the bus will read theaddress to determine if the data is for them. Once the device has determined that it is thesubject of the data transfer then it will assert DEVSEL (Device Select). DEVSEL iscontrol 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 ownconfiguration register and the system needs to differentiate between them. During theaddress phase of the A/D bus the C/BE identifies the configuration space and whetherread or write. During data phase of the A/D bus C/BE indicates a 4-byte transfer. Theconnections IDSEL and DEVSEL vary with the manufacturer’s system design.

VERSION1 REVISION 0 Memory IO and Configuration Access



2–9

Memory IO and Configuration Access

C/BE

DEVSEL

Address and Data

C/BE

IDSEL

BSS101_Mod1_Ch2_3

Device 0 Device 1 Device 2

Device 0 Device 1 Device 2

CPCI Card CPCI Card

CPCI Card

Address and Data

VERSION1 REVISION 0Memory IO and Configuration Access



2–10

ConfigurationSpaceTransactions

During configuration space transfers the A/D lines are grouped and have specificfunctions as listed below;

Address lines DescriptionAD 1 to 0 00 = Type 0 config transaction i.e. targeting a

PCI Bus device01 = Type 1 config transaction i.e. targetingdevice on the other side of a PCI bridge

AD 7 to 2 Indicate target config double word (offset inconfig header)

AD 10 to 8 Indicate target function number within deviceAD 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 abridge then it would set AD 1:0 to 01. The Host can therefore distinguish between localPCI and a remote PCI bus for configuration purposes.

VERSION1 REVISION 0 Memory IO and Configuration Access



2–11

Configuration space addressing

BSS101_Mod1_Ch2_4

AD 1 to 0

AD 7 to 2

AD 10 to 8

AD 31 to 11

Host(Also Device)

CPCI CardPart of PCI Bus

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 theother 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

VERSION1 REVISION 0Device Functions and Headers



2–12

Device Functions and Headers

DeviceFunctions

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 logicaldevices. The device must have a minimum of one logical function running. Each functionmust also have its own configuration header so the host processor can uniquelyconfigure a PCI device function.

The first function in a PCI device is labelled function 0 and the last is labelled function 7.

ConfigurationHeader

The configuration header is a set of registers that contain configuration parameters forthat function. The host processor can change these registers when the C/BE bus issuesthe correct commands. Each function on a device must have its own set of theseregisters.

Up to 256 registers are addressable within the Configuration header. PCI defines some ofthe registers the others are for use by the function. If a function requires more than 256registers then one register in the header could be set up to point to another 256 registers.

VERSION1 REVISION 0 Device Functions and Headers



2–13

PCI device functions

Configuration registers1 per device function

BSS101_Mod1_Ch2_5

Function 0

Function 2

Function 4

Function 6

Function 1

Function 3

Function 5

Function 7

PCI device

Multiple devices on a card

A PCI device offers anelectrical load to the PCIBus i.e. an IC




2–14

PCI Bus components

There are various components to the PCI Bus system. We have a Host processor on thebus that needs to communicate with peripheral cards. It may be that the number ofperipherals required means that not all cards can fit onto the PCI bus. It must beremembered that the PCI bus could address many cards on one bus but the number isusually limited to no more than 10 due to electrical loading. The PCI cage used in theMotorola 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 connectedtogether by a bridge. Many PCI busses can be cascaded together in this fashion. It mustbe remembered that some of the PCI busses may be on a device card and the card itselfcould 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 thebus.

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 thebus 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.




2–15

PCI bus components

PCI Local Bus, 32 bit A/D Bus i.e. Backplane

BSS101_Mod1_Ch2_6

PCI Bridge

PCI Local bus

HostPCI to PCI bridge

Host processor

i.e. SSP

i.e. HSC/Bridge




2–16

PCIExpandability

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 buswhere a full complement of devices can be attached.

Each bus is numbered sequentially by the operating software. Each PCI local bus couldaddress 32 different devices. This is however limited to 10 due to electrical loading; (apossible 2 x 8 PCI cards could be fitted in the Motorola CPCI cage).




2–17

PCI Bridging

PCI to Local Bus 02

PCI to Local Bus 01

PCI to PCI Bridge

BSS101_Mod1_Ch2_7

PCI Local Bus 03

PCI to PCI Bridge

System Slot Processor

Non-System Slot Processor

Backplane




2–18

Arbitration and Error signals

Arbitration

In order to avoid collision on the shared PCI bus the control of the bus must go througharbitration.

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 busare 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 issuesa PERR (Parity error). Targets have PERR output and Initiators have PERR output andInput.

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




2–19

Arbitration and error signals

PCI Device PCI BusArbiter

REQ

GNT

Arbitration

Error signals PERR and SERR

BSS101_Mod1_Ch2_8

Non-System Slot Processor System Slot Processor

Backplane




2–20

Subtractivedecoding

PCI uses subtractive decoding to allow connection to an ISA bus. An ISA buscannot be addressed via PCI so a PCI to ISA bridge is required. The bridge actsas 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 respondswith 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 ISAbus/device which cannot.




2–21

Subtractive Decoding

BSS101_Mod1_Ch2_9

DEVSEL

PCI to Local Bus

ISA Bus

Subtractive decoding PCI to ISA bridge

System Slot Processor




2–22



i

Chapter 3

CPX8216 Cage

VERSION1 REVISION 0



ii

VERSION1 REVISION 0



iii

Chapter 3CPX8216 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



iv




3–1


� 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.

VERSION1 REVISION 0CPCI



3–2

CPCI

CPX8216

The CPX8216 system is compliant with the CompactPCI Hot Swap Specificationdeveloped by the PCI Industrial Computers Manufacturing Group (PICMG). The systemallows the use of I/O modules that are not hot swappable, but the system must bepowered off when such modules are inserted and extracted. The CPX8216 features theability 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-slotCompactPCI I/O domains and the capability to contain redundant CPU modules andredundant Hot-Swap Controller (HSC) modules. It is possible to configure the system asa simplex, high I/O system containing a single CPU–HSC pair. Even as a simplexsystem, the CPX8216 still provides improved availability through redundant powersupplies and the control/monitoring capabilities of the HSC.

The CPX8216 standard system consists of two 8-slot subsystems, or domains, each withtwo slots for the host processor and six slots for non-host CompactPCI boards, (i.e. theI/O domains). The HSC board mounts in the rear of the chassis, behind the secondaryCPU slot.

VERSION1 REVISION 0 CPCI



3–3

CPX 8216 Cage

CPCI CHASSIS

ALARM MODULE

DIGITALMODULES

FAN/POWER SUPPLYSLEDS

POWERDISTRIBUTION

MODULE(not visible)

DIGITALMODULES

(transition moduleand bridge)

BSS101_Mod1_Ch3_01




3–4

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 aconnector on a bus segment.

System Layout

There is a system slot processor (SSP) slot for each of the two independent I/Odomains. Each system processor has direct access to its local bus through an onboardPCI-to-PCI (P2P) bridge. Each domain is also capable of supporting a Hot SwapController (HSC) module that contains its own P2P bridge. Thus, in a fully redundantconfiguration, there are two bridges that have access to each of the I/O buses — oneassociated with the SSP and one with the HSC. Only one of the bridges may be active ata time.

In a redundant configuration, the CPU in the left system slot of a domain A, SSP A, isassociated with the HSC in the right HSC slot in Domain B bus, HSC A (note that HSC Aactually sits on the Domain B bus). There is a local connection between each SSP-HSCpair that allows the SSP in one domain to control the other domain through its HSC. Thisarchitecture is illustrated in the following figure.

In addition to providing bridges to the remote I/O buses, the HSC provides the servicesnecessary 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 allboards on the segment. The System Slot is responsible for performing systeminitialization by managing each local board’s IDSEL signal. Physically, the System Slotmay be located at any position in the backplane. The slots allocated for the system slotprocessors are located in slots 7 and 9 of the Motorola CPX8216 CPCI cage.




3–5

System Layout

BSS101_Mod1_Ch3_02

Front cardlocations

Rear cardlocations

PCI Bus PCI Bus

Non system slots Non system slotsSystem slots

1

HSCA

HSCB

Transition modules for rear IO Transition modules for rear IO

Domain A Domain B

Backplane

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16




3–6

SystemConfigurations

The CPX8216 is a flexible system that allows for multiple configurations of processorcontrol, I/O redundancy, and peripheral configurations.

SystemProcessorConfigurations

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 awarm backup for both the SSP and the HSC

� An active/active or load–sharing configuration in which each SSP runs a singledomain while also serving as a backup to the other SSP

The SimplexConfiguration

Because of the flexible nature of the CPX8216, it is possible to configure it with differentlevels of redundancy and availability. For applications which do not require the benefits offull 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 systemmonitoring capabilities of the fully redundant configuration.




3–7

The Simplex Configuration

BSS101_Mod1_Ch3_03

PCI Bus PCI Bus

HSCA

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SSPA

Domain A Domain B




3–8

TheActive/PassiveConfiguration

In the active/passive configuration, one SSP manages all twelve I/O slots, much likein 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/Activeor Load-SharingConfiguration

The Active /Active configuration is the same as the Active / Passive configuration interms 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 twelveI/O slots, much like a dual 8-slot system with the added benefit of one SSP being able tocontrol all twelve I/O slots if the other SSP fails. It is important in a load-sharingconfiguration to note that the total critical activity does not exceed the capabilities of asingle SSP, because either one of the SSPs must be ready to take over the load carriedby the other.




3–9

The Active/Passive Configurations

BSS101_Mod1_Ch3_04

SSPB

PCI Bus PCI Bus

HSCA

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SLOT

SSPA

Domain A Domain B

HSCB

Passive SSP/HSC Active SSP/HSC




3–10

Redundancy

The CPX8216 contains 2 independent 8-slot CompactPCI buses. One slot in each bus isdedicated to a system processor, and another is needed for the HSC. This leaves sixslots on each bus to support I/O devices or non-system processors. One possibleconfiguration is to use the CPX8216 as a high I/O CompactPCI system with redundantSSPs. With this configuration, it is possible to run twelve independent I/O modules withina CPX8216 system. Applications requiring dense processing power could use all twelveI/O slots to support non–system processors.

Such a system would be protected against a SSP or HSC fault, but it would bevulnerable to data losses if any of the I/O modules or non-system processor moduleswere to fail. In systems handling critical data, it is possible to implement a 2N or an N+1I/O redundancy strategy that allows the level of service to be continued in the event thata module fails.

2N Redundancy

In the case of a 2N-redundant system, each I/O module or non–system processormodule is matched with an identical module on the other bus. The paired modules can beconfigured in an active/passive arrangement or a load-sharing arrangement in whicheach 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.




3–11

Redundancy

BSS101_Mod1_Ch3_05

SSPB

PCI Bus PCI Bus

HSCA

Processor

1a

SSPA

Domain A Domain B

HSCB

Processor

2a

Processor

3a

Processor

4a

Processor

5a

Processor

6a

Processor

1b

Processor

2b

Processor

3b

Processor

4b

Processor

5b

Processor

6b

Active processors Standby / load sharingprocessors

2N redundant system Active/Active or load share

BSS101_Mod1_Ch3_05a

SSPB

PCI Bus PCI Bus

HSCA

SSPA

Domain A Domain B

HSCB

Processor

1a

Processor

2a

Processor

3a

Processor

4a

BACK

UP

Processor

5a

Processor

6a

Processor

7a

Processor

8a

Processor

9a

Processor

10a

BACK

UP

Back up passiveprocessors

Active processors Active processors

N+1 redundancy




3–12

Power Supply

The fans on the power supplies provide the forced air cooling for the cage. Only two fansare necessary for adequate system cooling with the third fan providing N+1 coolingredundancy.

The power distribution panel is located in the rear of the chassis below the transitionmodule card cage. The panel distributes Ac or DC input power to the system powersupplies. There are two versions of power distribution power supply; AC, and dual inputDC.

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 singlephase

110 to 230 (nominal)

50 to 60 Hz

88 to 260 V ac

47 to 63 Hz

4.3 amps @ 270 V ac

8.9 amps @ 110 V ac

–48/60 V dc

(positive earth)

–36 to –72 V dc 2.5 amps @ –48 V dc




3–13

Power Supply Sled Units

BSS101_Mod1_Ch3_06




3–14

PowerSupplies/Fans

The CPX8216 system requires a minimum of two power/fan units. The Power Supply andFan (PSF) unit contains a 350W power supply and a 5” tube axial fan, (fan only units areavailable 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 thirdpower supply/fan unit as part of an N+1 strategy, meaning that the system can continueproviding service if one of the units fail. These modules are hot swappable and availablefor DC and AC supply.

Peripheral bays

It is possible to connect peripherals to the PCI cage. However in the Motorolaimplementation no peripherals will be connected to the cage in this manner.




3–15

Cage Cooling

BSS101_Mod1_Ch3_07

Rear Boards(Transition)

Front Boards(SSP & I/O)

Side-to-SidePlenum

Baffle

Side-to-SidePlenum

Filter




3–16

The SSP Complex

The SSP complex in a CPX8216 cage consists of two SSP modules and their Hot SwapControllers. The SSP modules as well as containing processors RAM etc also containthe 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 exchangedata and to maintain a loosely coupled relationship by passing heartbeat and checkpointprotocols.

The PCI to PCI bridge enables connection to the local PCI bus in that domain for datatransfer between the SSP and cards on the bus.

The Local PCI bus connection to the Hot Swap Controller enables the system slotprocessor 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




3–17

SSP Complex

BSS101_Mod1_Ch3_08

Domain B PCI local bus

Domain A PCI local bus

Ethernet

Serial link

Special BackplanePCI Interconnects(Private PCI bus)

HSC ASystem slot processor A HSC B System slot processor B

VERSION1 REVISION 0Heartbeat and Checkpoint Protocols



3–18

Heartbeat and Checkpoint Protocols

HeartbeatProtocol

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 theserial communications link as a secondary channel. Either physical channel can bechosen to be the primary heartbeat channel, with occasional “beats” being sent throughthe secondary channel to check for latent faults on that channel.

If the secondary SSP fails to receive a heartbeat on the primary channel, then itassumes that the primary link has failed and switches to the secondary channel. Whenthe active SSP fails to receive acknowledgments on the primary link, it begins to send theheartbeat message on the secondary channel. If the passive SSP does not receive abeat on the secondary channel, then it will assume the active SSP has failed, and it willbecome the active SSP.

CheckpointProtocol

The checkpoint protocol allows for a block of memory to be copied from an activeresource to the corresponding passive resource. It provides a snapshot of the applicationor system program state data. This means that in the event of an active SSP failure, thepassive SSP is able to begin service in nearly the same state as the state the active SSPfailed in. The checkpoint protocol uses the same physical links as the heartbeat protocol.

SwitchingService to thePassive SSP

The switchover from one SSP to another is initiated by the passive SSP when there is anindication that there is something wrong with the active SSP – such as a failed heartbeatprotocol. The passive side notifies the active side that it is about to begin a switchoverprocess. If the active side agrees to the switchover, then the two sides coordinate thehand-off and no bus signals, clocks, or devices should be corrupted. If the active systemfails 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 thepassive SSP to power–on reset the active SSP and takes control.

VERSION1 REVISION 0 Heartbeat and Checkpoint Protocols



3–19

Heartbeat and Checkpoint Protocols

BSS101_Mod1_Ch3_09

Ethernet/seriallink

TICK

NO TICK

Block of memory(program state,data etc)

TextActive SSP TextActive SSP

Shopping listMeatBreadMilk

Ethernet/seriallink

Heartbeat Protocol Checkpoint Protocol

Active SSPActive SSP

Becomes Active SSPOk, Get next item from

shopping listi.e. Bread

Passive SSP Passive SSP

Passive SSP assumescontrol of the PCI

buses in bothdomains.

Becomes Active SSP

BSS101_Mod1_Ch3_09a

VERSION1 REVISION 0Hot Swapping



3–20

Hot Swapping

The Hot SwapController/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 CPX8216System. The primary functions of the HSC include:

� Providing a bridge between the two eight-slot CompactPCI buses so that they canbe managed by a single SSP module

� Maintaining a Control Status Register which contains information on the status ofeach module

� Controlling power and resets to each module through radial connections

� Monitoring and controlling peripherals, including power and fan sleds, board andsystem LED’s, and alarms

The board is programmed by the system through configuration space for both the PCIbridge and the HSC. The HSC has a register entry for each device in the cage regardlessof Domain as well as power supplies and peripheral bays if they were installed. Howeveronly the HSC that owns domain A will control the power supplies as it is domain A thatbecomes the master during power up.

Hot Swap ControlStatus Register(CSR)

The CPX8216 supports hot swap CompactPCI cards with the standard control statusregister defined by the PICMG Hot Swap Specification. The register is visible in PCIconfiguration space and provides hot swap control and status bits: INS and EXT. TheINS 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 themicro-switch in the board handles. The host also uses these bits to acknowledge andde-assert ENUM#.

VERSION1 REVISION 0 Hot Swapping



3–21

Hot Swap Controller

BSS101_Mod1_Ch3_10

Private PCI to

System processor

HSC

PCI bus to cage

backplane

Private PCI bus

PCI

module

Status

register

PCI to PCI bridge

PCIModule

controller

(resets etc)

PCI backplane

control signals

Peripheral

control

VERSION1 REVISION 0Board Insertion and Extraction Features



3–22

Board Insertion and Extraction FeaturesThe PICMG specification details software and hardware features, in order to support hotswapping 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 lengthsin order to control the insertion and extraction voltages and to notify the system whenboards are inserted or extracted. The longest pins, which include VCC pins and GNDpins, are the first to mate during the insertion process and the last to break contactduring extraction. These pins are used to supply power to pre-charge the PCI interfacesignals to a neutral state before they contact the bus. This pre–charging serves tominimize 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 toassert signals, including BD_SEL#. During insertion, the BD_SEL# signal enables theboard to attach to the local PCI bus. On extraction, it causes the board to disconnectboth logically and electrically from the PCI bus, before the bus pins physically breakcontact with the bus.

BD_SEL#

BD_SEL# is asserted by one of the pins that mate last on insertion and break first onextraction. On insertion, the signal tells the board to connect to the PCI bus. Onextraction this pin breaks first, causing the board to disconnect both logically andelectrically from the PCI bus before the PCI bus pins physically break contact with thebus.

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 signalinforms the active SSP that the status of a board has changed. The SSP then identifiesthe board by polling the INSert and EXTract bits in all of the boards’ Control StatusRegisters.

VERSION1 REVISION 0 Board Insertion and Extraction Features



3–23

Staged Pins

BSS101_Mod1_Ch3_11

GND

VCCThese longest pins pre–charge the PCI pins

PCI traffic

Signal traffic

BD_SEL#BD_SEL# being the shortpin disconnects/connectsfrom/to the backplane last




3–24

The Hot SwapProcess

PICMG divided the complete hot swap process into physical, hardware and softwareconnection processes. These processes are formally broken down further into a group oftransitional states

When inserting a board, it goes through all states from P0 to S3. Conversely, a boardtransitions from S3 to P0 before being extracted. During normal operation, no states areskipped. If a board is extracted whilst in a software connection state, (other than S0) asoftware to crash is likely. However the CompactPCI bus, from a purely electrical point ofview, will not be disrupted enough to cause logic levels to be violated.

Certain states are overlapping. For example, when the board is fully seated (completedP1), but has not yet started the hardware connection process (H0), it said to be in theP1/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. Allpins 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 thePCI 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 configurationspace is not yet initialized.

� S0 – The Software Connection Process has not been initiated. The board’sconfiguration space registers are accessible but not yet initialized.

� S1 – The board is configured by the system. The system has initialized the board’sPCI configuration space registers with I/O space, memory space, interrupts andPCI bus numbers. The board is ready to be accessed by a device driver, but nodrivers are loaded at this time.

� S2 – The necessary supporting software (drivers, etc.) have been loaded. Theboard is ready for use by the OS and/or the application, but no operation involvingthe board is active or pending.

� S3 – The board is active. Software operations are either active or pending.




3–25

Connection States

BSS101_Mod1_Ch3_12

PhysicalConnectionStates

HardwareConnectionStates

SoftwareConnectionstates

P0 P1

H0 H2

S1 S2 S3

H1

S0




3–26

Compact PCIBackplane

CompactPCI defines a backplane environment that has up to eight boards, as per theMotorola CPCI cage domain. One slot, the System Slot, provides the clocking,arbitration, configuration, and interrupt processing for the other seven slots. Backplanesprovide separate power planes for 3.3V, 5V, and ground.

Transition Modules

Each slot in each domain has direct connections through the backplane to its respectivetransition module. The CPX8216 cage supports transition modules, which allows I/Oconnectivity from the rear of the cage rather than the front. Connection to PMC modulescan then be made at the rear of the cage by use of the appropriate transition module. It ispossible to use a generic transition module on which two PMC Interface modules(specific to the PMC card) can be mounted.




3–27

Sample PCI Card and Connectors

BSS101_Mod1_Ch3_13

I/O card Transitionmodule

Chassis Backplane

ProcessorModule

TransitionModule




3–28

Bus Connectors/Signals

CompactPCI bus segments bus all signals in all slots within the segment except the slotspecific 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 usedon 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 applicationuse. Applications include rear-panel I/O, bused signals or custom use.

CompactPCISignal Additions

CompactPCI defines some additional signals beyond the PCI specification. These signalsare Push Button Reset (PRST#), Power Supply Status (DEG#, FAL#), System SlotIdentification (SYSEN#) and System Enumeration (ENUM#) these are supported in theCPX8216 CPCI cage.

IDSELAssignment

The PCI signal IDSEL is used to provide unique access to each logical slot forconfiguration purposes. By connecting one of the address lines AD31 through AD25 toeach board’s IDSEL pin (P1, B9), a unique address for each board is provided duringconfiguration cycles.




3–29

Pin Layout of J1 J2 Connector in System Slot (7,9)

BSS101_Mod1_Ch3_14

POS Row Z Row A Row B Row C Row D Row E Row F

22 GND GA4 GA3 GA2 GA1 GA0 GND21 GND CLK16 GND RSV RSV RSV GND20 GND CLK15 GND RSV GND RSV19 GND GND GND RSV RSV RSV GND18 GND _BRSVP2A1

8_BRSVP2B18

_BRSVP2C18

GND _BRSVP2E18 GND

17 GND _BRSVP2A17

GND _PRST# _REQ16# GNT16# GND

16 GND _BRSVP2A16

_BRSVP2B16

_DEG# GND _BRSVP2E16 GND

15 GND _BRSVP2A15

GND _FAL# REQ15# GNT15# GND

14 GND _AD[35] _AD[34] _AD[33] GND _AD[32] GND13 GND _AD[38] GND VIO _AD[37] _AD[36] GND12 GND _AD[42] _AD[41] _AD[40] GND _AD[39] GND11 GND _AD[45] GND VIO _AD[44] _AD[43] GND10 GND _AD[49] _AD[48] _AD[47] GND _AD[46] GND9 GND _AD[52] GND VIO _AD[51] _AD[50] GND8 GND _AD[56] _AD[55] _AD[54] GND _AD[53] GND7 GND _AD[59] GND VIO _AD[58] _AD[57] GND6 GND _AD[63] _AD[62] _AD[61] GND _AD[60] GND5 GND _C/BE[5]# GND VIO C/BE[4]# _PAR64 GND4 GND VIO _BRSVP2B4 _C/BE[7]# GND _C/BE[6] GND3 GND CLK4 GND GNT3# REQ4# GNT4# GND2 GND CLK2 CLK3 _SYSEN# GNT2# REQ3# GND1 GND CLK1 GND REQ11# GNT1# REQ2# GND

J2

25 GND 5V A _REQ64# _ENUM# 3.3V 5V GND24 GND _AD[1] 5V VIO _AD[0] _ACK64# GND23 GND 3.3V _AD[4] _AD[3] 5V _AD[2] GND22 GND _AD[7] GND 3.3V _AD[6] _AD[5] GND21 GND 3.3V _AD[9] _AD[8] _M66EN _C/BE[0]# GND20 GND _AD[12] GND VIO _AD[11] _AD[10] GND19 GND 3.3V _AD[15] _AD[14] GND _AD[13] GND18 GND _SERR# GND 3.3V _PAR _C/BE[1] GND17 GND 3.3V _SDONE _SBO# GND _PERR# GND16 GND _DEVSEL# GND VIO _STOP# _LOCK# GND15 GND 3.3V _FRAME# _IRDY# BD _SEL[n]# _TRDY# GND141312

Key Area

11 GND _AD[18} _AD[17] _AD[16] GND _C/BE[2]# GND10 GND _AD[21] GND 3.3V _AD[20] _AD[19] GND9 GND _C/BE[3] _IDSEL _AD[23] GND _AD[22] GND8 GND _AD[26] GND VIO _AD[25] _AD[24] GND7 GND _AD[30] _AD[29] _AD[28] GND _AD[27] GND6 GND (REQ#) GND 3.3V (CLK) _AD[31] GND5 GND _BRSVP1A5 _BRSVP1B5 RST[N]# GND (GNT#) GND4 GND _BRSVP1A

4HLTY[N]# VIO _INTP _INTS GND

3 GND _INTA# _INTB# _INTC# 5V _INTD# GND2 GND TCK 5V TMS TDO TDI GND1 GND 5V plus-minus 12V TRST# +12V 5V GND

J1




3–30

REQ#/GNT#Assignment

The System Slot interfaces to seven pairs of REQ/GNT pins called REQ0-REQ6 andGNT0-GNT6. Each board slot interfaces to one pair of REQ/GNT signals using pinscalled REQ and GNT. The System Slot on either backplane segment supports the fullcomplement of REQ/GNT signals.

PCI ClockDistribution

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 signalsvia the CompactPCI backplane.




3–31

Pin Layout of J1 J2 connector in System Slot (7,9)

BSS101_Mod1_Ch3_15

POS Row Z Row A Row B Row C Row D Row E Row F

22 GND GA4 GA3 GA2 GA1 GA0 GND

21 GND CLK16 GND RSV RSV RSV GND

20 GND CLK15 GND RSV GND RSV

19 GND GND GND RSV RSV RSV GND

18 GND _BRSVP2A18

_BRSVP2B18

_BRSVP2C18

GND _BRSVP2E18 GND

17 GND _BRSVP2A17

GND _PRST# _REQ16# GNT16# GND

16 GND _BRSVP2A16

_BRSVP2B16

_DEG# GND _BRSVP2E16 GND

15 GND _BRSVP2A15

GND _FAL# REQ15# GNT15# GND

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

J2

25 GND 5V A _REQ64# _ENUM# 3.3V 5V GND

24 GND _AD[1] 5V VIO _AD[0] _ACK64# GND

23 GND 3.3V _AD[4] _AD[3] 5V _AD[2] GND

22 GND _AD[7] GND 3.3V _AD[6] _AD[5] GND

21 GND 3.3V _AD[9] _AD[8] _M66EN _C/BE[0]# 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

13

12

Key Area

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 _BRSVP1A4

HLTY[N]# VIO _INTP _INTS GND

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

J1

VERSION1 REVISION 0Replacing Modules



3–32

Replacing Modules

Condition forReplacingModules

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 ofservice.

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 whenhandling and storing components.

An earthing wrist strap must be worn when handling electronic modules, including theSystem slot processors and non-system slot processors, Transition modules and PCI toPCI 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 HotSwap 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 thebackplane 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 beginningto withdraw the module from the chassis. Once lit, the module can be removed.

� Pull the module from the chassis.

VERSION1 REVISION 0 Replacing Modules



3–33

Diagram of Removing a Hot Swap Module

BSS101_Mod1_Ch3_16




3–34

Installing a HotSwap 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 donot insert the board by pushing on the faceplate of the board.

� Slide the module slowly into the slot until the ejector levers contact the chassisrails.

� Use the ejector levers to seat the board in the slot by closing the levers towardsone another until they are in the horizontal locked position.

� Secure the board by tightening the captive screws at the top and bottom of thepanel.

� Reconnect any interface cables to the connectors on the face of the module.

Non Hot SwapModule

If a unit is not Hot Swap then removal and replacement of the board should only be donewhen the power to the CPCI cage has been removed. The electrical status of the PCIbus 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 theblue LED). Once the card is installed and secure, power can be re-applied to the cage.

VERSION1 REVISION 0 Replacing Modules



3–35

Diagram of Installing a Hot Swap Module

BSS101_Mod1_Ch3_17




3–36



i

Chapter 4

CPCI Digital Cards

VERSION1 REVISION 0



ii

VERSION1 REVISION 0



iii

Chapter 4CPCI 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



iv




4–1


� State the operation of the MCP750.

� State the operation of Mezzanine modules.

� State the operation of HSC Bridge.

� State the operation of Alarm module.

VERSION1 REVISION 0MCP 750



4–2

MCP 750The 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 theRAM300 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 theMCP750 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 rearpanel I/O and other features. Some special features may place certain requirements onthe backplane, such as providing a full set of connectors on both sides.

VERSION1 REVISION 0 MCP 750



4–3

Diagram of MCP 750

BSS101_Mod1_Ch4_1

VERSION1 REVISION 0MCP 750 Features



4–4

MCP 750 Features

Falcon Memory Controller

The Falcon memory controller consists of two identical Falcon ASICs controlling 144-bitwide DRAM. Each device controls 64-bits of data and an additional 8-bits of ECC checkword. The ECC protection allows correction of single bit errors in a 64–bit field, anddetection of 2–bit errors.

Falcon also controls two banks of FLASH memory and system registers that provideboard configuration information. FLASH and system registers are not ECC protected.

Configuration NVRAM is located on the ISA bus and is not controlled by the Falconchipset.

Raven MPC-to-PCI Bridge

The Raven ASIC bridges the PowerPC host bus with the PCI bus. It provides fourmemory–mapping windows in each direction between the buses. The Raven contains theMulti–Processor Interrupt Controller (MPIC) used for routing interrupts from boarddevices to the processor.

Peripheral Bus Controller (PBC)

The PBC is a commercial off–the–shelf device providing ISA, IDE, and USB access fromthe PCI bus. PBC (PCI Peripheral Bus Controller)

This bridge is a VT82C586 from VIA Technologies. This bridge is the South Bridge part ofchipsets made for various Pentium processors.

PCI–to–PCI Bridge

The 21154 PCI to PCI bridge connects the on–board PCI bus with the CompactPCIbackplane. This bridge uses standard transparent bridging technology as specified by thePCI 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 webbased 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 manyPentium based systems.

VERSION1 REVISION 0 MCP 750 Features



4–5

Block Diagram of MCP 750

BSS101_Mod1_Ch4_2

SYSTEMREGISTERS

PM

C S

LOT

FLASH / DRAM EXPANSION CONNECTORSDEBUG CONNECTOR

L2 CACHE256K–1M

FLASH1MB

RAVEN ASICBRIDGE

MEMORY

FALCON CHIPSET

32/6

4–B

IT P

MC

SLO

T

PBCVT82C586B

ETHERNETDEC21140

10BT/

USER I/O J3 & J5 J1 / J2

SUPER I/OPC87307

ESCC85230

CIOZ8536S

ER

IAL

ET

HE

RN

ET

PAR

ALL

EL

SE

RIA

L

FR

ON

T P

AN

EL

66M

Hz

MP

C60

4 P

RO

CE

SS

OR

BU

S

PROCESSORMPC750

CLOCKGENERATOR

PCI–PCI BRIDGEDEC21154

RESETCONTROL

ARBITRATIONCONTROL

J4

33MHz 32/64–BIT PCI LOCAL BUS

33M

Hz

32/6

4–B

IT P

CI B

US

100BTX

US

BU

SB

CONTROLLER

KE

YB

OA

RD

MO

US

E

FLO

PP

Y D

ISK

2 S

YN

C/A

SY

NC

US

B0

US

B1

Fro

nt P

anel

I/O

IDE

RTC/

MK48T559

ISAREGÕS

NVRAM/WD

ISA

SROMAT24C04

CompactFLASH

33M

Hz

32 B

IT

VERSION1 REVISION 0Peripheral Mezzanine Card



4–6

Peripheral Mezzanine CardThe Peripheral Mezzanine Card, (PMC) is a daughter board which sits on a mainprocessor board in the either the PCU or the SGSN. The Processor boards used in theCPCI 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 hostcomputer 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 stackingheight above the host based PCB.

Several standards are used to specify the mezzanine cards. The parent standard, calledCommon Mezzanine Card (CMC), IEEE P1386, defines the complete mechanics for boththe 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 Singletype and the actual size is:

Width: 148.8 mm Depth 74mm Height 10mm

VERSION1 REVISION 0 Peripheral Mezzanine Card



4–7

PCI Mezzanine Card

BSS101_Mod1_Ch4_3a

PCI Mezzanine Card Location

BSS101_Mod1_Ch4_3b

Connectionfor rear I/O

J1

J5

J4

J3

J2

PMCModule

PMCModule

2 x E1 Links &Console ports

VERSION1 REVISION 0Hot Swap Controller/Bridge Module



4–8

Hot Swap Controller/Bridge Module

Bridge

The Bridge known as the HSC/Bridge allows a system slot processor to be linked to aseparate bus. This enables PCI domain expansion. The HSC/Bridge and system slotprocessor 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 bridgeboards to allow check pointing and heartbeat messages between system slot processorboards. This allows migration to a fully hot swap, redundant high availability system,including hot standby/load sharing between system slot processors in the future ifrequired.

VERSION1 REVISION 0 Hot Swap Controller/Bridge Module



4–9

Diagram of HSC/Bridge Module

BSS101_Mod1_Ch4_6

VERSION1 REVISION 0Alarm Module



4–10

Alarm Module

Alarm moduleoverview

The Alarm module provides LED’s and alarms for the system. The purpose of theseparate alarm board is to provide a standard appearance for the LED’s without relyingon individual boards. The Alarm board runs across the top of the chassis. In addition to InService/Out of Service LED indicators for all sixteen slots, the alarm board containsLED’s for system status (System in Service/Component out of Service/System out ofService) and for the three standard Telco levels (Critical/Major/Minor). The three Telcoalarms are also signalled through a dry contact relay and available through a RJ–45connector.

It is powered and controlled from each of the two Hot Swap Controllers within thesystem. Normally, only two of the three-slot status LED’s are visible – the third iscovered by the alarm board overlay.

The module is a field replaceable unit (FRU). The module is hot swappable and ismounted on the front of the system chassis, a ribbon cable connects the alarm module tothe backplane.

Alarm PanelLED’s

Bits in the Hot Swap Controller’s register control the alarm panel LED’s. The systemsoftware sets the bits in the register. This allows the alarms and LED’s to be tailored forthe Motorola GPRS solution for alarm event reporting.

The table below provides the colour and standard nomenclature for the LED’s on thealarm panel.

Alarm LED Colour DescriptionController Board Slot Status Green In Service

Yellow N/A (or Out of Service)Red Out of Service

System Status Green System In ServiceyYellow Component Out of serviceRed System Out of Service

Telco Status Yellow MinorRed MajorRed Critical

VERSION1 REVISION 0 Alarm Module



4–11

Alarm panel LEDs

1 2 3 4 5 6 7 8 9 10 11 12 13 15 1614

SYSTEMSTATUS

SYSTEMIN SERVICE

COMPONENTCOMPONENT

OUT OF SERVICETELCOSTATUS

CRITICALMAJORMINORALARM

CONNECTION

BSS101_Mod1_Ch4_8




4–12

Alarm boardOperation

The Alarm board is under control of one of the HSC. As such it is an extension of theHSC register set. The address of the alarm register will be an offset from the baseaddress of the HSC. The setting and clearing of alarms and LED’s are under softwarecontrol and by the act of the system writing to the correct registers in the HSC theappropriate 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 datais active. The clock runs at 16 kHz. The link is duplex and serial up / down information istransferred at the same time.

The PLD acts as 2 state machines. One for Domain A and One for Domain B. The twostate machines operate independently from one another. Domain logic controls the LED’sfor slots 1 to 8 and Domain B logic controls the LED’s for slots 9 to 16. Domain A alsocontrols the system status LED’s.

VERSION1 REVISION 0 Alarm Module



4–13

Alarm Board Block Diagram

BSS101_Mod1_Ch4_9

System LED’s

Slot 1 LED’s

Slot 2 LED’s

Slot 6 LED’s

Slot 11 LED’s

Slot 16 LED’s

ALARMPLD

Domain ALogic

Domain BLogic

TelcoRelaysLED’s

SystemAlarmConn

PWR APWR B

HS

C IF

C C

ON

N

GND

REG

Digital Inputs

Clock and Data A

Clock and Data B




4–14

CHAPTER 2PCU HARDWARE

CHAPTER 3DIGITAL CARDS FOR PCU

CHAPTER 4PCU SOFTWARE

PROCESSES

CHAPTER 5PCU INSTALLATION

CHAPTER 1PCU IN GPRS

��

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


i

VERSION 1 REVISION 0

BSS101/GSR5.1Module 3: PCU Operations and

Maintenance

� Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000All Rights ReservedPrinted in the U.K.


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


ii

Copyrights, notices and trademarks

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computerprograms stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola certain exclusive rights for copyright computer programs, including theexclusive right to copy or reproduce in any form the copyright computer program. Accordingly, anycopyright Motorola computer programs contained in the Motorola products described in this documentmay 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 byimplication, estoppel or otherwise, any license under the copyrights, patents or patent applications ofMotorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a licenseagreement 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 bylaw. No part of the software or documentation may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any language or computer language, in any form or by anymeans, without prior written permission of Motorola.

AccuracyWhile reasonable efforts have been made to assure the accuracy of this document, Motorolaassumes no liability resulting from any inaccuracies or omissions in this document, or from the useof the information obtained herein. Motorola reserves the right to make changes to any productsdescribed herein to improve reliability, function, or design, and reserves the right to revise thisdocument and to make changes from time to time in content hereof with no obligation to notify anyperson of revisions or changes. Motorola does not assume any liability arising out of the applicationor use of any product or circuit described herein; neither does it convey license under its patentrights of others.

Trademarks

and MOTOROLA are trademarks of Motorola Inc.UNIX is a registered trademark in the United States and other countries, licensed exclusively throughX/Open Company Limited.Tandem , Integrity , Integrity S2 , and Non-Stop-UX are trademarks of Tandem ComputersIncorporated.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.




iii

Module 3 Objectives i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1PCU 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 2PCU 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 3Digital 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv

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




v

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 5PCU 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. . . . . . . . . . . . . . . . . . . . . . . .




vi

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




vii

W liii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

X liv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Z lv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




viii

VERSION 1 REVISION 0 Module 3 Objectives



i

Module 3 ObjectivesAt 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

VERSION 1 REVISION 0Module 3 Objectives



ii



i

Chapter 1

PCU in GPRS




ii




iii

Chapter 1PCU 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv

VERSION 1 REVISION 0 Chapter 1 Objectives



1–1


� State the function of the PCU in GPRS

� State the function of the RLC /MAC block

� Show how data is routed through GPRS

VERSION 1 REVISION 0Packet Control Unit (PCU)



1–2

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, BSSGPsignalling, routing of signalling messages, Radio Link Control (RLC) and Media AccessControl (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 thenover 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 usingframe relay protocol. There is also signalling between existing functional process at theBSC such as the BSP and the PCU via the E1 Span, as well as between the PCU andChannel Coders.

GPRS DataStream (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 DataStream (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 codedownload 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

VERSION 1 REVISION 0 Packet Control Unit (PCU)



1–3

GPRS Data Stream

BSS101_M3Ch1_1

SGSN

NS – SIGBSSGP SIG

GSL

GDS

RTFRSL

PCUBSC

BTS

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



1–4

Radio Link Control /Media access Control (RLC/MAC)RLC/MAC is the layer 2 Protocol that operates between the MS and the BSS. RLC/MACProtocol 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 entityis sending and re–assembly of LLC PDUs when the entity is receiving. When operating inacknowledged mode the RLC function provides the Backward Error Correction functionfor selective re–transmission of RLC/MAC blocks. Acknowledged mode also preservesthe order of the higher layer PDUs provided to RLC.

MAC

The MAC function defines the procedure that enables multiple mobile stations to share acommon transmission medium, which may consist of several physical channels. Forexample, when two mobiles are utilising the same frequency and timeslot for datatransfer. The MAC function provides the facility for a mobile to use several physicalchannels in parallel. For example, a mobile uses one frequency but two timeslots withinthe same TDMA frame. MAC also provides contention resolution for mobile originatingaccess and queuing/ scheduling of access requests for mobile terminated access.

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



1–5

Radio Link Control (RLC)

NormalBurst

BSS101_M3Ch1_2

LLC

RLC/MAC

PhysicalLayer

NormalBurst

NormalBurst

NormalBurst

BH BH BHBCS BCS BCSInfo Field Info Field Info Field

Information FieldFH FCS

LLC

RLC

MAC

PhysicalLayer

LLC

RLC

MAC

PhysicalLayer

VERSION 1 REVISION 0Timeslot allocation



1–6

Timeslot allocationWith 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 normalburst 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 tothe BSC. This is also the case for GPRS though the link now exists between the BTSand PCU, for the air interface timeslots designated as GPRS.

The Air Interface timeslots now have two further configurations. In standard GSM, thetimeslots can be configured as BCCH, SDCCH or TCH. For GPRS, timeslots can bereserved for use only by GPRS, (RES). Timeslots can also be switchable with GSM voicetraffic always taking priority (SW). This should not pose a problem for GPRS mobiles asmobiles in current data transfer could be allocated new resources on a different GPRStimeslot or fewer resources, multiplexing GPRS mobiles onto the same air timeslots.

VERSION 1 REVISION 0 Timeslot allocation



1–7

Timeslot configuration examples

BSS101_M3Ch1_3

0

1

2

3

4

5

6

7

Example A Example B Example C

BCCH

CARRIER

CARRIER

2BCCH

CARRIER

CARRIER

2BCCH

CARRIER

CARRIER

2

SW

SW

SW

SW

SW

SW

SW

SW

TCH

TCH

TCH

TCH

TCH

TCH

TCH

BCCHSW

SW

SW

RES

RES

RES

RES

RES

TCH

TCH

TCH

TCH

TCH

TCH

TCH

BCCHTCH

TCH

TCH

TCH

TCH

TCH

TCH

TCH

TCH

TCH

SW

SW

RES

RES

RES

BCCH

VERSION 1 REVISION 0Hierarchical position of the PCU



1–8

Hierarchical position of the PCUThe PCU attaches onto a BSC and is associated only with one BSC. The PCU thereforeserves many BTSs.

The BSC regards the PCU as a remote BTS in terms of Database equipage. It should beremembered 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 theOMC–R. All statistics from the PCU will be reported to the OMC–R and NOT theOMC–G.

Although the PCU is completely different hardware from Motorola BTSs, the interface willbe familiar to engineers with experience of them. Note however, that that the PCU doesnot support a customer MMI only EMON. This can be accessed via RLOGIN or via aTTY cable.

If web based MMI is supported, this can be used to extend the MMI prompt of the BSC toa remote user connected into the Ethernet port of the PCU PSP.

VERSION 1 REVISION 0 Hierarchical position of the PCU



1–9

Hierarchical position of the PCU

BSS101_M3Ch1_5

BSC SITE

BTS SITE PCU

CAGE

COMB KSW GCLK BSP BTP CSFP DHP EAS

LCF OMF BTF XBL MTL OML CBL GSL*

RTF Associated RTF

64Kbps RSL

*Indicates auto–equipped device

CAB

MSI

MMS*

GPROC

DRI

HPAT

16Kbps RSL

CELL

BSC Site Device Equipage Hierarchy

VERSION 1 REVISION 0Functionality of the PCU



1–10

Functionality of the PCUA mobile sends some data that is destined for some far away server on the WWW. Firstof all the data is sent over the air Interface to the BTS. The BTS sends the data in TRAUframes to the BSC. The BSC switches these TRAU frames to the PCU. The PCUterminates these particular GDS links on a PICP.

The PICP also terminates the GSL signalling links between the PCU and the BSC. ThePRP board can also terminate GDS links though the number of links is reduced becauseof 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 thecorrect PRP board were the data is processed and formatted, (reconstitutes the LLCframes 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 canthen route the data through the GGSN and out into the WWW.

VERSION 1 REVISION 0 Functionality of the PCU



1–11

PCU Connectivity

BSS101_M3Ch1_6

E1: CIRCUIT

SWITCHED

PICP PICP

750

860

SGSNPCU

BSC

BTS

AIRINTERFACE

MS

E1: CIRCUIT

SWITCHED

E1: FRAME

RELAY (Gb LINK)

750750

PRP

TDM Bus

PCI Bus

GPRS DA T A

(TRAU)

E1

PMC

E1

PMC

E1

PMC

750

GPRS

SIGNALING

(LAPD)

PSP

PHYSICAL

LA YERS

BTS

E1

TRANSITION

MODULE

E1

TRANSITION

MODULE

E1

TRANSITION

MODULE

E1: GDS (TRAU) E1: GDS

(LAPD) & (TRAU)

AIRINTERFACE

MS

VERSION 1 REVISION 0Functionality of the PCU



1–12



i

Chapter 2

PCU Hardware




ii




iii

Chapter 2PCU 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv




2–1


� Identify the PCU cabinet types

� State the specifications for the PCU

� Identify the E1 interface panel

VERSION 1 REVISION 0PCU Cabinets



2–2

PCU CabinetsThe PCU can be housed in one of two cabinet types. The static frame cabinet and theswing frame cabinet.

The static frame cabinet can accomodate up to three PCUs and is only suited toinstallations where rear access is available.

The swing frame cabinet can accomodate up to three PCUs and is suited to installationswhere rear access is not available (i.e. installed against a wall).

VERSION 1 REVISION 0 PCU Cabinets



2–3

PCU Cabinet

STATIC FRAME

SWING FRAME

BSS101_M3Ch2_1

VERSION 1 REVISION 0Static frame cabinet



2–4

Static frame cabinet

Static framecabinet structure

The static frame cabinet has front and rear access doors, hinged on the left side of thedoor. Additional access to the cabinet interior may be gained by opening quarter panelsin 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 inputswitching panel for each PCU.

or

– Up to two remote dc power input switch and cable assemblies, on powerinput mounting panels, fitted to the front left racking member, adjacent toeach 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 powercables. Data and power cables are kept separated by using different entry points.

This cabinet has a deeper footprint than the swing fame cabinet and is suitablefor direct side by side installation. Static frame cabinets may be bolted togetheras a suite and are also capable of being bolted to the GSN cabinet suite.

NOTE

VERSION 1 REVISION 0 Static frame cabinet



2–5

PCU static frame cabinet

BSS101_M3Ch2_2

VERSION 1 REVISION 0Swing frame cabinet



2–6

Swing frame cabinet

Swing framecabinet structure

The swing frame cabinet has front and rear access doors, the front door is hinged on theleft side of the door, the rear can be configured hinged on either left or right. Additionalaccess to the cabinet interior may be gained by opening quarter panels in the cabinetsides.

The purpose of the swing frame is to allow access to the rear of the PCU when rearaccess 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 powercables. Data and power cables are kept separated by using different entry points androuteing.

This cabinet is not suitable for bolting to adjacent cabinets as a suite, but maybe installed side by side with cabinets of the same depth or less. The swingframe cabinet has a wider footprint than the static frame cabinet.

NOTE

Swing framefunctionaldescription

The swing frame cabinet must be bolted to the floor or supported by a wallbracket at the top.Operation of a populated swing frame in an unsecured cabinet presents adanger of toppling.Only one swing frame is to be open at any given time, the spare swing framekey should be removed from the equipment and stored in a secure location.

WARNING

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 whenunlocked. This is to ensure only one frame at a time can be open. The key must beremoved 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 thePCU. 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 beopen.

VERSION 1 REVISION 0 Swing frame cabinet



2–7

PCU Swing frame cabinet

BSS101__M3Ch2_3

VERSION 1 REVISION 0Specifications



2–8

Specifications

Introduction tospecifications

The PCU and associated cabinet specifications are included in this section.

Safety, EMC andenvironmentalrequirementspecifications

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,IEC 950

ETS 300 342-2,EN 50081-1, EN 50082-2

ETS 300 019-1-3, class 3.2

Environmentallimits

The environmental levels for the PCU are the standard ETSI classes applicable to BTSequipment. The PCU will be collocated with BSC hardware already in the field, whichmay be in remote locations.

Table 1-2 shows the environmental limits for operation and storage of the PCUequipment.

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 –40�C to +70 �C Up to 93% relative humidity, at 30 �C.

Access controlspecifications

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



2–9

Specifications

Requirement specification complied with

Safety EMC Environmental

EN 60950, EN41003,IEC 950

ETS 300 342-2,EN 50081-1, EN 50082-2

ETS 300 019-1-3, class 3.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 –40�C to +70 �C Up to 93% relative humidity, at 30 �C.




2–10

Physicaldimensions

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 populatedPCU 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




2–11

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 populatedPCU 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




2–12

Cabinet inputpowerrequirements

All cabinets and supply cables must be protected by an external fuse or circuitbreaker.

WARNING

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(single phase)

110 to 230 (nominal)50 to 60 Hz

88 to 260 V ac47 to 63 Hz

4.5 amps per PCU@ 230 V ac


–48/60 V dc(positive earth)

–36 to –72 V dc 20.5 amp per PCU@ –48 V dc

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 to14 MHz. Voltage application stabilization must be within the specified range inless than 1 second.

NOTE

Powerconsumption(ac and dc)

Table 1-6 shows the power consumption of the GPRS cabinet.

Table 1-6 Power consumption

Maximum powerconsumption

One PCU 984 watts

Two PCUs 1986 watts

Three PCUs 2952 watts




2–13

Power requirements

Power supply requirements

Nominal voltage Voltage supply range Maximum supply current

Wide ranging ac(single phase)

110 to 230 (nominal)50 to 60 Hz

88 to 260 V ac47 to 63 Hz



–48/60 V dc(positive earth)

–36 to –72 V dc 20.5 amp per PCU@ –48 V dc

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 to14 MHz. Voltage application stabilization must be within the specified range inless than 1 second.

NOTE

Power consumption

Maximum powerconsumption

One PCU 984 watts

Two PCUs 1986 watts

Three PCUs 2952 watts

VERSION 1 REVISION 0E1 interface



2–14

E1 interface

Introduction toE1 interfaceconnections

There is one E1 interface panel for each PCU populating a cabinet. In the static framecabinet the E1 interface panels are mounted horizontally behind each PCU, and areaccessed through the rear door. In the swing frame cabinet the E1 interface panels aremounted vertically, to the left of each installed PCU, and fixed to the cabinet rear rackinginside 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 cabinettypes.

VERSION 1 REVISION 0 E1 interface



2–15

E1 interface panel

SWING FRAMECABINET (FRONT)

STATIC FRAMECABINET (REAR)

E1 interface panel

BSS101_M3_ch2_7

VERSION 1 REVISION 0E1 interface



2–16

E1 interfacepanels

The E1 interface panel allows for the connection of up to twenty–four 75ohm or 120 ohmE1 lines.

The panel comprises:

� Four front mounted T43/BIB board assemblies.

� Four front mounted RJ45 connector panels, each containing 6 eight way RJ45connectors.

Each T43/BIB panel is wired to the adjacent RJ45 connector panel at the rear of theinterface 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



2–17

E1 interface panel

BSS101_E1 interface panel

T43/BIB BOARDASSEMBLIES

SIX WAY RJ45CONNECTORS

VERSION 1 REVISION 0PCU



2–18

PCUThe PCU is a CPX8216 CPCI chassis. Up to three of the CPX8216 chassis can bemounted in a cabinet. With the Interface panel the PCU is a self-contained unit andrequires 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



2–19

View of the PCU

CPCI CHASSIS

ALARM MODULE

DIGITALMODULES

(MPROC andDPROC)

FAN/POWER SUPPLYSLEDS

POWERDISTRIBUTION

MODULE(not visible)

DIGITALMODULES

(transition moduleand HSC bridge)

BSS101_M3_Ch2_9

VERSION 1 REVISION 0PCU



2–20



i

Chapter 3

Digital Cards for PCU




ii




iii

Chapter 3Digital 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv




3–1


� State the operation of the DPROC

� State the operation of the NIB

� State the operation of the transition module

VERSION 1 REVISION 0MPROC (Master Processor)



3–2

MPROC (Master Processor)The MPROC is the system slot processor using the MCP750 processor board. The termMPROC 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 MPROCruns BSSGP protocol functions and is the PCU System Processor, (PSP). This is similarto 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 insimplex 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. Thiscard with the MPROC forms the CPU complex and work together as a pair. TheHSC/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)



3–3

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

VERSION 1 REVISION 0Digital Processor DPROC



3–4

Digital Processor DPROC

The DPROC boards are non–system slot processors, (I/O boards).They have two PMCsockets (as opposed to the MPROC one socket) which are used for connecting E1 linksto 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 InterfaceControlProcessor (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 isterminating a Gb link, then the second port can only be used for Gb links.

Packet ResourceProcessor (PRP)

Performs Air Interface scheduling and performs almost all GPRS related signaling. FromGSR5.1 onwards, both sockets on a PRP. can house PMC modules. Each of these canterminate one E1 link.

VERSION 1 REVISION 0 Digital Processor DPROC



3–5

DPROC naming

BSS101_M3Ch3_1

Non-system slotprocessor

PICP PRP

DPROC

CPCI defined

Motorola hardware defined

Motorola software defined

VERSION 1 REVISION 0DPROC



3–6

DPROC

DPROC (PICP)

The DPROC (PICP) is used for all network interfacing functions to the outside world suchas the SGSN and BSC. The PICP has up to two interface modules installed. Datato/from these interfaces pass through the on–board processor. This processor hasdifferent functions dependent on the interface type, but includes features such as packetrouting 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 BSCto 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



3–7

Diagram of DPROC

BSS101_M3Ch3_5

VERSION 1 REVISION 0DPROC



3–8

DPROCThe DPROC is a high–performance single–slot PowerPC based platform providing a32–bit CompactPCI bus interface. The CompactPCI bus interface device is directlyconnected 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 PCIbus and the CPCI bus. The primary side of the bridge is connected to the CPCI bus, thesecondary side of the PCI–to–PCI bridge is connected to the local PCI bus. Both busesare 32–bit wide and run up to 33 MHz.

EthernetController

The Ethernet interface 10Base–T or 100Base–TX is available at the front panel via an8–pin RJ–45 connector.

PMC slots 1and 2The DPROC provides two PMC slots for installing compliant PMC modules. The PCIbus, 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 1and PMC slot 2 have each 64 user I/O signals. These signals are available onconnectors J4 and J5.

Switches

There are switches on the board used for configuration purposes, these switches arefactory set and should not be altered, to do so can render the DPROC inoperative.

VERSION 1 REVISION 0 DPROC



3–9

Diagram of DPROC

BSS101_Mod3_Ch3_06

Serial interfaces Serial interfaces

Memorymodule(s)

SerialI/O ports

L2cache

PPC-to-PCI bridgeMPC106(Grackle)

PowerPCCPU

Boot flash

User flash

RTC/NVRAM

PCI-to-ISAbridge

Serial IDPROM

CIO

Watchdogtimers

FRONT PANEL

CompactPCI

I/O

CompactPCI

PCI busPPC bus

PMC module (slot 2)

PMC module (slot 1)

10–Base T or 100–Base TX Interfaceadapter

PCI bus CompactPCI busPCI-to-PCIbridge

ISA bus

PMC I/O

PMC I/OAUI EthernetMII Ethernet

Ethernetcontroller

VERSION 1 REVISION 0Front Panel Description



3–10

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 isperformed when the reset key is pushed to the active position. To avoid unintentionalreset, the reset key is recessed in the front panel.

� ABORT– Mechanical abort key: When enabled and toggled it affects the board bygenerating a non–maskable interrupt (NMI) request via the PCI–to–ISA bridge. Thisallows an abort of the current program, to trigger a self–test, or to start a maintenanceprogram. 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/Ounit. 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/Ounit. 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 interfaces100Base–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 thehandle is opened during normal operation the interrupt signal ENUM# is asserted on theCPCI 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



3–11

DPROC front panel

BSS101_M3Ch3_7

Serial 2Serial 1

Base T

R

U1

U2

T

Reset

Abort

PMC1

PMC2

VERSION 1 REVISION 0NIB (Network Interface Board)



3–12

NIB (Network Interface Board)

NIB overview (E1PMC module)

The NIB is a PMC using a Power PC processor. The NIB connects onto the local PCIbus 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. Themodule also supports the termination of the Frame Relay layer 2 protocol and passesreceived data packets to its host board processor.

The E1 interfaces to the BSC provides for physical connection of all GPRS data channelsinto 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. TheGSL can be multiple 64k timeslots. It is used to manage and control the PCU/BSCsystem.

VERSION 1 REVISION 0 NIB (Network Interface Board)



3–13

NIB

BSS101_M3Ch3_8

VERSION 1 REVISION 0NIB (Network Interface Board)



3–14

I/O through theBackplane:

One major feature PMCs have over regular PCI cards is the capability to route I/Othrough 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 likeCompactPCI route I/O signals from the mezzanine card P14 connector to the rearbackplane connector(s).

The PMC is hardware configured for front or rear I/O at time of manufacture and cannotbe subsequently changed. As well as the lack of the connectors at the front componentchanges are also made to route the E1 links through P14.

The PMC architecture does not modify the CPCI electrical, logical and softwareinterfaces. PCI interface is used “as is”. The complete functionality of a CPCI card can bemaintained, except for the mechanical form factor.

CPU

The PMC has a dedicated RISC processor the Motorola PowerQUICC with 32 bit internalarchitecture. 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 becausethe board is fitted with either E1 controllers or T1 controllers (only E1 implemented inMotorola GPRS). The PMC will only ever be configured as E1. The controller is atransceiver 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. bridgingbetween them. It provides an asynchronous operation between local and external PCIbusses up to 33.33MHz

The PMC will physically interface to the E1 connection via transition modules on thebackplane of the PCI cage. It achieves this by connecting to the PCI bus through theHost processor card.

VERSION 1 REVISION 0 NIB (Network Interface Board)



3–15

Peripheral Mezzanine Card (PMC)

BSS101_Mod1_Ch4_4

PCI Bus32 bit 33 MHz

Rear

2 x E1 Link

512K ROM DRAM

2KEEPROM

PCI Controller

32 bit localbus

CPUMPC860MH

E1Controller

E1Controller

128 byte serial

EEPROM

P14

P11

VERSION 1 REVISION 0Transition module



3–16

Transition moduleThe transition module provides the cage slot with rear I/O. The transition module workswith the PMC module via the PMC host. The PMC and transition modules come as apair. The transition module enables IO connectors like RJ45 to be used in connecting tothe PMC module which otherwise would not be capable of accepting such connectors.

VERSION 1 REVISION 0 Transition module



3–17

Transition Module

REAR FACEDLD1

NOT USED

Isolatingtransformers

DLD2NOT USED

E1 PORT 2A

E1 PORT 1A

E1 PORT 2B

CON 2

CON 1

ConnectorP5

ConnectorP4

E1 PORT 1B

BSS101_M3Ch3_9




3–18

E1 transitionmodulefunctionaldescription

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 cPCIconnectors P4 and P5 to the network interface boards (NIB), in slot one and slottwo, respectively.

� E1 interfaces:

There are four E1 interfaces, each with common mode choke noise filtering;isolating transformers (1500 V rms isolation); and self resetting, positivetemperature coefficient, over current protection. These interfaces use shieldedRJ45 connectors. This four wire balanced interface is then routed to connectors P4and P5.

� EIA-232:

There are four EIA-232 serial communication ports each with overvoltageprotection and shielded RJ45 connectors with ferrite filtering.

VERSION 1 REVISION 0 Transition module



3–19

E1 transition module functional diagram

BSS101_Mod3_Ch3_10

NIB 1 E1 Ports(2 links)

NIB 2NIB 1

TRANSITIONMODULE

NIB 2 E1 Ports(2 links)NIB 1 EIA–232

Ports

NIB 2 EIA–232Ports

Protection

Transformers

Protection

Protection

CM choke

P5P4

DPROC




3–20



i

Chapter 4

PCU Software Processes




ii




iii

Chapter 4PCU 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv




4–1


� 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

VERSION 1 REVISION 0Packet Interface Control Processor (PICP)



4–2

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 describea group of processes that can be treated as one entity. The processes are groupedtogether as they would share a similar purpose or interface. The functional unit may actas a single process or separate processes. A single functional unit may reside on oneprocessor (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 Relayconnection from the PCU to the SGSN. Over this link signalling data and traffic data arepassed. 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 GBlink. 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 theappropriate processor.

The GB FU also contains the following;

Paging routeing – to route signalling for paging messages from SGSN to the appropriatecell

Flushing routeing – to route flushing messages of queued SDUs for MSs to theappropriate cell.

Flow control routeing – to route flow control messages of downlink traffic, (flow controlincludes the queuing of MS packets based on priority queues.

VERSION 1 REVISION 0 Packet Interface Control Processor (PICP)



4–3

PICP

BSS101_Mod3_Ch4_01

PRP PSP

StatusF.U.

TRS

PacketScheduler

AccesGrantSYS InfPaging

UplinkDownlink

RLC Seg

TA & PCFlowControl

I/O F.U. I/O F.U.

GB F.U. Status F.U.

pFTP/pFCP

GWM F.U.

pCApSSP

pCM

pSM

pSAP

FR F.U. Status F.U.

GB F.U.

Page Routeing

Flushing Routeing

Flow ControlRouteing

LAPDF.U.

TRAUF.U.

I/O F.U.

PSP PICP

Cell balancer

BMS

VERSION 1 REVISION 0Packet Interface Control Processor (PICP)



4–4

LAPD FU

The LAPD functional unit is used for synchronization of the LAPD link over the GSLbetween the PCU and the BSC.

TRAU FU

The TRAU functional unit is used for synchronization and handling of the PCU framesbetween the PCU and the BSC.

STATUS FU

The PICP STATUS functional unit is used for debugging mechanisms. It also generatesthe 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 andfunctional units on the PSP.

VERSION 1 REVISION 0 Packet Interface Control Processor (PICP)



4–5

PICP

BSS101_Mod3_Ch4_01

PRP PSP

StatusF.U.

TRS

PacketScheduler


UplinkDownlink

RLC Seg

TA & PCFlowControl

I/O F.U. I/O F.U.

GB F.U. Status F.U.

pFTP/pFCP

GWM F.U.

pCApSSP

pCM

pSM

pSAP

FR F.U. Status F.U.

GB F.U.

Page Routeing

Flushing Routeing


LAPDF.U.

TRAUF.U.

I/O F.U.

PSP PICP

Cell balancer

BMS

VERSION 1 REVISION 0Packet Resource Processor (PRP)



4–6

Packet Resource Processor (PRP)The Packet Resource Processor (PRP) is where all of the radio related processing takesplace. The PRP performs all of the RLC / MAC processing, air interface scheduling andframe synchronization on the BTS facing channels. The following functional units providethis functionality:

Packet scheduler

The Packet scheduler handles the scheduling of uplink and downlink packets for the Uminterface. This is done on a per call basis. The packet scheduler will assign the numberof timeslots and the number of blocks that a mobile may use in accordance with the MSQuality 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 theSGSN.

RLC seg

This functional Unit is responsible for LLC segmentation into RLC / MAC blocks inaccordance to the coding scheme being used. The unit also reassembles RLC / MACblocks into LLC frames for uplink PDCH. A part of this unit carries out the timing advanceand power control for GPRS mobiles.

PRP Status

The unit will observe signalling messages between processes and functional units. Theunit also contains functions that can initiate status commands to display generation ofalarms 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)



4–7

PRP

BSS101_Mod3_Ch4_01

PRP PSP

StatusF.U.

TRS

PacketScheduler


UplinkDownlink

RLC Seg

TA & PCFlowControl

I/O F.U. I/O F.U.

GB F.U. Status F.U.

pFTP/pFCP

GWM F.U.

pCApSSP

pCM

pSM

pSAP

FR F.U. Status F.U.

GB F.U.

Page Routeing

Flushing Routeing


LAPDF.U.

TRAUF.U.

I/O F.U.

PSP PICP

Cell balancer

BMS

VERSION 1 REVISION 0Packet Resource Processor (PRP)



4–8

TimeslotResource 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 inanother cell which was inactive can be brought into the active state to help increase datathroughput. The TRS will manage this

Flow control

This unit works in conjunction with the SGSN to control the flow of data down to aparticular mobile. The flow control will operate on a per call basis and will be affected bythe quality of service that the mobile supports and the current data throughput. The flowcontrol unit therefore works closely with the Packet scheduler.

VERSION 1 REVISION 0 Packet Resource Processor (PRP)



4–9

PRP

BSS101_Mod3_Ch4_01

PRP PSP

StatusF.U.

TRS

PacketScheduler


UplinkDownlink

RLC Seg

TA & PCFlowControl

I/O F.U. I/O F.U.

GB F.U. Status F.U.

pFTP/pFCP

GWM F.U.

pCApSSP

pCM

pSM

pSAP

FR F.U. Status F.U.

GB F.U.

Page Routeing

Flushing Routeing


LAPDF.U.

TRAUF.U.

I/O F.U.

PSP PICP

Cell balancer

BMS

VERSION 1 REVISION 0PCU System Processor (PSP)



4–10

PCU System Processor (PSP)The PCU System Processor (PSP) resides on the MPROC (system slot processor). ThePSP is responsible for PCI bus arbitration and clock generation. The PSP containsBSSGP 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.

Gatewaymanager FU

The Gateway Manager functional unit (GWM) handles the following functions:

� PCU Central Authority – pCA. Code loading of objects during initialization andreset. Board initialization and startup for software processes.

� PCU Configuration management process –pCM. Handling database informationand changing affected functional units. Works in conjunction with pCA, CA andCM.

� PCU Fault Translation Process, PCU Fault Collection Process –pFTP, pFCP. Faultmanagement functions (i.e. fault detection, fault recovery, etc). Alarm Collectionand Relaying.

� PCU Site statistics process – Collection of statistics from functional units andforwarding to the CSP, (Central Statistics Process) on the GPROC.

� PCU System Audit Procedure process supported on the MPROC as well as theDPROCs that contain a local process.

� Cell Balancer –Cell resource sharing (that is balancing of cells) across equippedPRPs. If a PRP outage occurs the Cell balancer will attempt to move the cell toanother PRP. Collection of cell list for BSC–BTS Dynamic Allocation purposes

� PCU Switch Manager pSM. The pSM maintains data paths within the PCU andcommunicates 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, Statisticsprocess, CSP as well as RSS.

I/O FU

An I/O functional unit is created on the PSP for communication with the functional unitsat the PRP and PICP.

PSP Status

The unit will observe signalling messages between processes and functional units. Theunit also contains functions that can initiate status commands to display generation ofalarms and debugging commands.

VERSION 1 REVISION 0 PCU System Processor (PSP)



4–11

PSP

BSS101_Mod3_Ch4_01

PRP PSP

StatusF.U.

TRS

PacketScheduler


UplinkDownlink

RLC Seg

TA & PCFlowControl

I/O F.U. I/O F.U.

GB F.U. Status F.U.

pFTP/pFCP

GWM F.U.

pCApSSP

pCM

pSM

pSAP

FR F.U. Status F.U.

GB F.U.

Page Routeing

Flushing Routeing


LAPDF.U.

TRAUF.U.

I/O F.U.

PSP PICP

Cell balancer

BMS

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



4–12

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 connectionto download the subsequent applet.

The MMI server will send a message to the TTY DLSP process in the BSC, over theGDS 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 EMONconnection. 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 andthe TTY DLSP process in the BSC. The TTY DLSP process will interact with the MMIprocess in the BSC.

The EMON server will manage the transmission of EMON strings between an end userand 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 BSCout to the PCU and eventually the end user.

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



4–13

Base Station Sub–System Management Server

BSS101_Mod3_Ch4_02

mmi

tty disp

monitor

events

gui

browser

bsc

emon strings

mmi strings

emon strings

mmi strings

MMI Server

HTTP Server

EMON Server

BMS

pcu

applet:mmi emon

VERSION 1 REVISION 0Gb Functional Unit



4–14

Gb Functional UnitThe 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 monitoringthe state of BVCs and NS–VCs and the mapping between them. The GBM isresponsible for the monitoring of the Gbl link status and generating the appropriatealarms. The GBM will inform the Gateway Manager (GWM) of any change in GBLstatus.

The GBM manages the BVC and NS–VC block, reset and unblock procedures. It shallgenerate 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. BTSnot 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 downlinkPDUs to the appropriate Flow Control Buffer Manager (FBM) which will pass the PDU tothe air functional units for transmission over the air.

The GR is also responsible for the routing of paging messages to the appropriate Pagingfunction on a Packet Resource Processor.

GatewayTransmitManager

The Gateway Transmit Manager (GTM) gathers and transmits uplink PDUs on thecorrect 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 theNS–VC group serving the BSSGP Virtual Circuit Identifier (BVCI) for transmission by theGbFu to the SGSN. The GTM gathers the PDUs from the various cells and passes themto the FR functional unit for transmission over a given DLCI and Gbl.

VERSION 1 REVISION 0 Gb Functional Unit



4–15

Gb Functional Unit

BSS101_M3Chh4_3

Flow ControlBuffer Manager

GatewayTransmitManager

GB Router

GB Manager

NST

VERSION 1 REVISION 0Network Service Test



4–16

Network Service TestThe Network Service Test (NST) periodically tests NS–VCs to see if they are alive. TheNST also sends test messages on each alive NS–VC and responds to test messagesfrom the SGSN by sending back an acknowledgement on the same NS–VC.

Flow ControlBuffer Manager(FBM)

The Flow Control Buffer Manager ensures that opened downlink LLC frames aretransmitted over the air within their delay class limitations. The FBM performs flowcontrol using either XON/XOFF or the ‘leaky bucket’ algorithm. When using the ‘leakybucket’ algorithm the configurable parameters of the maximum size of the downlink bufferand maximum data rate the SGSN can transmit data to the mobiles will govern thealgorithm. The FBM will send at a configurable interval flow control messages to theSGDN to govern the downlink data transfer.

The FBM is also responsible for the flushing of a mobile LLC PDUs from a cell queue forthat mobile and informing the packet scheduler to delete the mobiles context for that cell.

VERSION 1 REVISION 0 Network Service Test



4–17

NST

Periodic testing of NSVCs

Ensure queued dl LLC frames transmitted within their delay class

Flushing of LLC frames

FBM

VERSION 1 REVISION 0Fault Management



4–18

Fault ManagementThe Fault Management software at the Packet Control Unit (PCU) may be split into twomain areas; the fault detection and handling system and the Central Authority (pCA).The Fault Management software is responsible for the detection of any alarms anddeciding upon any hardware /software reconfiguration in response to these alarms.

The PCU Central Authority, under the direction of the fault handling and detectionsystem, is responsible for carrying out the reconfiguration.

VERSION 1 REVISION 0 Fault Management



4–19

Fault management

BSS101_M3Ch4_5

Fault detectionand handlng

Central Authority

VERSION 1 REVISION 0Fault detection and handling



4–20

Fault detection and handlingThis 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 processesthat exist on its particular DPROC. This process automatically acknowledges receipt ofan 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 functionalunit, and works with various processes to keep the integrity of the site. All alarms at thePCU are reported to the pFTP. The pFTP forwards alarms to the Agent at the BSC andgenerates messages to the pCA for device transitions, as needed, based on faultsreported.

3. System Audit Process (pSAP)

The System Audit Process exists on every DPROC at a site. This process periodicallyaudits the PCU software and any faults found are forwarded to the Fault TranslationProcess via the Fault Collection Process.

VERSION 1 REVISION 0 Fault detection and handling



4–21

Fault translation process

BSS101_M3Ch4_6

PCUDevices

pFTP

pFCP

pCAAgent

VERSION 1 REVISION 0System Audit Process



4–22

System Audit ProcessThe Packet Control Unit (PCU) System Audit Process follows much the samearchitecture as the BSS. A Site System Audit Process (pSSAP) resides on the PCUSystem Processor (PSP) as part of the Gateway Manager (GWM) functional unit. ThePSP performs the audits of the PCU and communicates directly with the BSC MMI andSAP.

The DPROCs contain a local process responsible for auditing the DPROC upon which itresides.

The SAP will detect faulty/degrading hardware and software through the use of audittests 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 availablehardware in the PCU.

� Cage System Audit Process – has the same functionality as the Site System AuditProcess. This has been provided for future multi cage PCUs.

� Device System Audit Process – responsible for auditing the device on which itresides.

The System Operator can turn the audit functionality ON/OFF on a device, cage or persite basis. The System Operator can modify the audit schedules for a specific device orcage, e.g. device audit.

VERSION 1 REVISION 0 System Audit Process



4–23

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

VERSION 1 REVISION 0Configuration Management



4–24

Configuration ManagementThe Configuration Management (CM) Software is responsible for managing and updatingthe main configuration database at either a BSC, BTS or PCU. This database isdownloaded as an object file and contains all the site parameters such as siteconfiguration and device functionality distribution.

The CM process at the BSC communicates with the pCM process in the same manneras a remote BTS. If database changes are listed as at the PCU then the BSC CM willforward the changes to the PCU Configuration Management (pCM). There is no MMIfunctionality at the PCU so the pCM has reduced functionality compared to the CM at theBSC.

The pCM process resides on the PCU System Processor (PSP) as part of the GatewayManager functional unit. The pCM receives the CM database object from the BSC. Aftertranslation the database object is stored on compact flash on the PSP. The translatedobject is cross–loaded to the DPROC boards equipped in the database with code objectsat initialisation.

VERSION 1 REVISION 0 Configuration Management



4–25

Configuration management

BSS101_M3Ch4_9

Slave pCMSlave pCM

DatabaseCopy

DatabaseCopy

DPROC DPROC

PSP pCM MASTERDATABASE

BSCBSC CM

Compact Flash Memory

Master Database

VERSION 1 REVISION 0PCU Central Authority (pCA)



4–26

PCU Central Authority (pCA)On site initialisation, the central authority (pCA) process is created and queries thedatabase to obtain site configuration and device equipage data. The central authority isthen responsible for creating all the necessary software processes on the DPROCS, aswell as downloading and ”bringing into service” all peripheral boards and devices. Oncompletion of site initialisation, the pCA then works as an independent process with adynamic database keeping track of the state of all devices and software functions on itssite.

If a fault indication occurs at the site and the fault detection and handling system decidesthat a device or software identity must be taken out of service, then it is the pCA that willperform this task. If the fault detection and handling system decides to bring anotherdevice or software entity into service, in response to that alarm indication then it is thepCA that will supervise the downloading/initialisation of the device or software entity. Itmay be the case that the system operator wishes to remove or insert a device fromservice 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 updatethe 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 areerased. The pCA is then created by the initialisation process, the pCA reads thedatabase and the initialisation procedure starts again.

The pCA is responsible for informing the router process when software processes arecreated, destroyed or moved. This allows the router process to modify the router tableswhich are used by the executive to support the ”flexible interprocess communications”feature.

VERSION 1 REVISION 0 PCU Central Authority (pCA)



4–27

PCU Central Authority functions

A. Site Initialisation

1. Queries for database for site configuration and equipage2. Downloading software to the hardware3. Create software on DPROCs4. Creating routing tables5. Creating state tables

B. Initiate and Direct Configuration Changes

1. Hardware2. Software3. Updating Router4. Updating state tables

VERSION 1 REVISION 0Initial Configuration



4–28

Initial Configuration1. 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 ofobjects currently residing at the PCU to determine which new objects requiresending. The required set are transferred from the BSC to the PCU. Thedatabase is included in this transfer.

3. The PSP, once the download is complete, will determine which card is in each slotof the PCU and download the appropriate objects and database information toeach DPROC and PMC. The database is stored in non–volatile memory at thePSP.

4. The PSP now distributes the configured number of cells in the database across thePRPs. It also creates router tables of cell to router and distributes this table to allboards to allow communications.

5. The Gateway Manager (GWM) now initiates process startup at the PRPs andPICPs

6. The GBL interface is now initialised as the GSL is brought into service. The PSPnow indicates to the BSC CA that the PCU is enabled and registers for calls.

VERSION 1 REVISION 0 Initial Configuration



4–29

PCU Initialization

BSS101_M3Ch4_11

pIP downloads appropriate object to each DPROC + PMC

pIP + BSC IP bring up default GSL

BSC IP queries PCU pIP for set of objects

BSC IP download objects if required

PSP distributes configured cells across PRPs

GWM starts up PRPs + PICPs

GBL initialized + GBL brought into service

PSP indicates PCU enabled + registers for cells

VERSION 1 REVISION 0Initial Configuration



4–30



i

Chapter 5

PCU Installation




ii




iii

Chapter 5PCU 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




iv

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




5–1


� 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

VERSION 1 REVISION 0PCU Installation



5–2

PCU InstallationInstallation 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 informationthe engineer should refer to the Service manual.

VERSION 1 REVISION 0 PCU Installation



5–3

PCU Installation

� 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

VERSION 1 REVISION 0Installing the PCU cabinet



5–4

Installing the PCU cabinet

Introduction tocabinetinstallation

The cabinet can be mounted on a smooth concrete floor, or other strong supportivecavity construction. The swing frame cabinet requires four M10 floor mounting anchorbolts, or if the floor is not suitable, the bracing bracket supplied with the equipment, mustbe 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 aswing frame cabinet when the swing frames are rotated.

The swing frame cabinet must be stabilised by bolting to the floor, (or by fitting thesupporting bracket to the top of the cabinet).

There are two possibilities for PCU installation.

� PCU swing frame cabinet.

� PCU static frame cabinet.

Adjustingcabinet 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 a19–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



5–5

Static and swing frame cabinet floor fixing

875 mmreference

764mm

4 by M10 clearanceholes

600 mmreference

496 mm

51mm

55.5mm

696 mm

800 mmreference

52mm

582mm

675 mmreference

46.5mm

STATIC FRAME CABINETTEMPLATE

SWING FRAME CABINETTEMPLATE

4 by M10 clearanceholes

BSS101_M3Ch5_3

VERSION 1 REVISION 0Top supporting bracket



5–6

Top supporting bracketAlternatively, to secure a swing frame cabinet by fitting a supporting bracket, between thetop 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 tothe 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



5–7

Top supporting bracket

M8 FASTENERSLOTS

SLIDE BRACKETDOWN

SUPPORTINGBRACKET

CABINET TOP FRAMEREAR SECTION

BSS101_M3Ch5_3

VERSION 1 REVISION 0Mounting the PCU in a cabinet



5–8

Mounting the PCU in a cabinet

Options formounting thePCU

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 concealedby aesthetic bay panels. Swing frame cabinets also have a rear blanking plates fitted inunpopulated positions.

Safetyconsiderations

In order to minimise the risk of toppling, all PCU cabinets must be populated starting atthe 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 whenhandling PCUs.

Lifting equipment must be used unless there are sufficient personnel to ensure thathealth and safety regulations are not breached.

To ensure correct cooling in the cabinet and to prevent re–circulation of warm air, rearblanking panels must be fitted to unpopulated PCU mounting positions in swing framecabinets.

Fitting the cableguide

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 withthe 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



5–9

Cable guide

BSS101_M3Ch5_4

VERSION 1 REVISION 0Fitting a PCU into a cabinet



5–10

Fitting a PCU into a cabinetPCU 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 theequipment.

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 andsafety regulations are not breached.

Mounting a PCUin a static framecabinet

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 PCUin a swing framecabinet

To mount the PCU in a swing frame cabinet:

Attempting to mount a PCU into a free swinging frame could cause injury and/or damageto the equipment. Ensure the swing frame is closed and locked before mounting thePCU.

To prevent re-circulation of warm air in the swing frame cabinet and ensure correctcooling of PCU equipment, rear blanking plates must be fitted to any unpopulated PCUmounting 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 torquespecified 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



5–11

Installing the PCU into a cabinet

BSS101_M3Ch5_5

VERSION 1 REVISION 0Fitting E1 interface panels



5–12

Fitting E1 interface panelsThere is one E1 interface panel for each PCU.

E1 interfacepanel options

The PCU E1 interface panel consists of three T43/BIB board assemblies and three 6 wayRJ45 connectors on a mounting panel, with space left for a future upgrade to four boardsand connectors.

In the static frame cabinet the E1 interface panels are mounted horizontally behind eachPCU, and are accessed through the rear door.

Static framecabinet E1interface 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 framecabinet E1interface panel

In the swing frame cabinet the E1 interface panels are mounted vertically, to the left ofeach installed PCU, and fixed to the cabinet rear racking inside the cabinet. The PCUswing frame must be open to provide access to the E1 interface panels.

Swing framecabinet E1interface panelprocedures

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



5–13

E1 interface panels

BSS101_M3Ch5_6

E1 interfacepanels

Rear view of PCU static framecabinet, showing E1 interfpanels

T43/BIBBOARD

ASSEMBLIES

SIX WAY RJ45CONNECTORS

PCU E1 interface panel

E1 interfacepanels

Position of E1 interface panelsin a swing frame cabinet

VERSION 1 REVISION 0Connecting the E1 cables



5–14

Connecting the E1 cables

T43 connections

Connection is made using a 37–pin D–type connector to the interface panel and twelvetype 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 theexternal PCM circuit lines.

VERSION 1 REVISION 0 Connecting the E1 cables



5–15

E1 connections

J0

J1

J2

J5

J4

J7

J8

J10

J13 J11

J14

J16

J17

Type 43 interconnect board (T43)

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

J0

J1

T2T1

T5T4

T7 T8

T10

T13T11

T14 T16

T17Balanced-line interconnect board (BIB)

BSS101_M3Ch5_8

Table 3-2 BIB interconnections

T43/BIB function Connector J1 pin number RJ45

Tx 1Rx 1

1(+ve)/ 20 (–ve)2(+ve)/ 21 (–ve)

1

Tx 2Rx 2

4(+ve)/ 23 (–ve)5(+ve)/ 24 (–ve)

2

Tx 3Rx 3

7(+ve)/ 26 (–ve)8(+ve)/ 27 (–ve)

3

Tx 4Rx 4

10(+ve)/ 29 (–ve)11(+ve)/ 30 (–ve)

4

Tx 5Rx 5

13(+ve)/ 32 (–ve)14(+ve)/ 33 (–ve)

5

Tx 6Rx 6

16(+ve)/ 35 (–ve)17(+ve)/ 36 (–ve)

6

VERSION 1 REVISION 0Connecting the digital interface cable loom to the PCU



5–16

Connecting the digital interface cable loom to the PCU

Introduction todigital loomconnection

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 transitionmodules to PCI mezzanine cards (PMC).

E1 cables from the BSC, carrying GSL are connected through transition module ports toone 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 carry30 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 port1A (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 servicemanual.

VERSION 1 REVISION 0 Connecting the digital interface cable loom to the PCU



5–17

Digital cable connection minimum configuration

BSS101_M3Ch5_9

Table 1–3 provides E1 interface connection information, for maximum cardconfiguration with coding schemes 1, 2, 3 & 4:

Table 1–3 E1 interface connection (maximum configuration)T43/BIBboard

T43/BIBIdent

Function RJ45 Cableident

TM locationand port

1 Tx 1, Rx 1 (GSL link) E1 A1 cPCI 1 Card 1 Port 1ATx 2, Rx 2 (GSL link) E1 A2 cPCI 2 Card 2 Port 1ATx 3, Rx 3 (Gb link) E1 A3 cPCI 3 Card 1 Port 2ATx 4, Rx 4 (Gb link) E1 A4 cPCI 4 Card 2 Port 2ATx 5, Rx 5 (Gb link) E1 A5 cPCI 5 Card 3 Port 1ATx 6, Rx 6 (Gb link) E1 A6 cPCI 6 Card 3 Port 2A

2 Tx 1, Rx 1 (GDS TRAU) E1 B1 cPCI 7 Card 4 Port 1ATx 2, Rx 2 (GDS TRAU) E1 B2 cPCI 8 Card 4 Port 2ATx 3, Rx 3 (GDS TRAU) E1 B3 cPCI 9 Card 5 Port 1ATx 4, Rx 4 (GDS TRAU) E1 B4 cPCI 10 Card 5 Port 2ATx 5, Rx 5 (GDS TRAU) E1 B5 cPCI 11 Card 6 Port 1ATx 6, Rx 6 (GDS TRAU) E1 B6 cPCI 12 Card 6 Port 2A

3 Tx 1, Rx 1 (GDS TRAU) E1 C1 cPCI 13 Card 11 Port 1ATx 2, Rx 2 (GDS TRAU) E1 C2 cPCI 14 Card 11 Port 2ATx 3, Rx 3 (GDS TRAU) E1 C3 cPCI 15 Card 12 Port 1ATx 4, Rx 4 (GDS TRAU) E1 C4 cPCI 16 Card 12 Port 2ATx 5, Rx 5 (GDS TRAU) E1 C5 cPCI 17 Card 13 Port 1ATx 6, Rx 6 (GDS TRAU) E1 C6 cPCI 18 Card 13 Port 2A

4 Tx 1, Rx 1 (GDS TRAU) E1 D1 cPCI 19 Card 14 Port 1ATx 2, Rx 2 (GDS TRAU) E1 D2 cPCI 20 Card 14 Port 2ATx 3, Rx 3 (GDS TRAU) E1 D3 cPCI 21 Card 15 Port 1ATx 4, Rx 4 (GDS TRAU) E1 D4 cPCI 22 Card 15 Port 2ATx 5, Rx 5 (GDS TRAU) E1 D5 cPCI 23 Card 16 Port 1ATx 6, Rx 6 (GDS TRAU) E1 D6 cPCI 24 Card 16 Port 2A

REAR OF CHASSIS

DIGITAL INTERFACE CABLE

E1INTERFACE

PANEL

REAR VIEW OFTRANSITION MODULECPX 8216

PORT1A

PORT1B

PORT2A

PORT2B

BSS101_M3Ch5_10

VERSION 1 REVISION 0Digital cable connections



5–18

Digital cable connections

Static framecabinet digitalcable connectionprocedure

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 onthe E1 interface board

2. Route the cable loom around the cabinet, from the E1 interface panel down thecabinet 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 theappropriate point, and loop across to the upper section of the PCU cable guide andsecure with cable ties.

4. Connect the individual cables of the digital interface cable loom to the appropriateports on the DPROC cards in the PCU chassis.

5. Repeat steps 1 to 4 until all installed PCUs have been connected.

Swing framecabinet digitalcable connectionprocedures

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 appropriateports 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



5–19

Static Frame Cabinet Digital Cable Connection Procedure

E1Interfacepanel

PCU cableguide

Cabinetrail

Cabletidybrackets

BSS101_Mod3_Ch5_11a

Swing Frame Cabinet Digital Cable Connection Procedure

BSS101_M3Ch5_11

Cabletray

PCU cableguide

Swingframe rail entry

PCU shelfcablechannel

E1 INTERFACEPANEL

T43/BIBboards

6 wayRJ45s

PORT1A

PORT2B

PORT2A PORT

1B

VIEW OFTRANSITIONMODULE

I/O ports

VERSION 1 REVISION 0Fitting power input switches and mounting panels



5–20

Fitting power input switches and mounting panels

Power inputswitching

� 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 inputswitchingoptions

PCUs are supplied with power input switch and cable assemblies relevant to the inputpower requirements of the PCU. Two options are available,

� dc power input switch and cable assembly.

� ac power input switch and cable assembly.

Static framecabinet ac option

The ac power input switch and cable assemblies for a static frame cabinet are mountedon a power distribution mounting bracket fitted to the frame of the cabinet. The mountingbracket is located in the rear of the cabinet, near floor level, and is accessed through therear door.

Static framecabinet dc option

The dc power input switch and cable assemblies for a static frame cabinet are mountedon power input switch mounting panels fitted to the rear left frame of the cabinet. Thesemounting panels are located in the rear of the cabinet, adjacent to the PCU, and areaccessed through the rear door.

Swing framecabinet option

The power input switch and cable assemblies are fitted to power input switch mountingpanels and secured to the frame of the cabinet. The panels are located to the left of theswing frames at the front of the cabinet. A dc mounting has cut outs for two dc powerinput switching panels and an ac mounting has a single cut out.

Static framecabinet powerdistribution

In the static frame cabinet the ac power input switch and cable assemblies are mountedon a power distribution mounting bracket behind the lower PCU, and are accessedthrough the rear door. The length of the cable assembly attached to an ac power inputswitch is dependent upon the position of the associated PCU within the cabinet. Thecables are routed through the cabinet along the left vertical cabinet rail and secured withcable ties.

VERSION 1 REVISION 0 Fitting power input switches and mounting panels



5–21

PCU power input switching panels

BSS101_M3Ch5_12

1

0

1

0

dc power input switch and cableassembly front panel

ac power input switch and cableassembly front panel

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



5–22

Fitting ac power input switches to static frame cabinetTo 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 thetop 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



5–23

PCU static frame ac power distribution mounting bracket

ac Power distributionmounting bracket

Cabinet rail

BSS101_M3Ch5_13

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



5–24

Fitting dc power input switches to static frame cabinetTo 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.

4. Secure the power input switch front panel using two M6 Torx screws, and tighten 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



5–25

Static frame (rear view) cabinet dc switch mounting

Static framedc switchmounting panel

Cable guide

BSS101_M3Ch5_14

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



5–26

Swing frame cabinet power input switch mounting panelThere is one power input switch mounting panel for each PCU. In the swing framecabinet the switch mounting panels are fitted to the cabinet frame at the left of eachswing frame.

Fitting powerinput switches toswing framecabinet

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.

5. Secure the power input switch front panel using two M6 Torx screws, and tighten 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



5–27

Power input mounting panels in a swing frame cabinet

Power input mounting panels,ac option with single cut outshown.(The third panel and mountingis hidden by the open swingframe)

BSS101_M3Ch5_15

VERSION 1 REVISION 0Swing frame power input cable routeing



5–28

Swing frame power input cable routeingThe diagram opposite shows an ac power input cable, two dc cables would be used in adc cabinet, with the dc connections to the PCU being made through the two circularholes 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 secure with cable ties.

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 secure with cable ties.

VERSION 1 REVISION 0 Swing frame power input cable routeing



5–29

Swing frame power input cable routeing

Cable tray

Power inputswitch

PCU shelfcable channel

Swing framerail entry

PCU cableguide

10

BSS101_M3Ch5_16

VERSION 1 REVISION 0Earthing and transient protection



5–30

Earthing and transient protection

Site earthing

Refer to the Grounding guidelines for cellular radio installations 68P81150E62, fordetailed 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 itspower source).

� Provision should be made for routeing earthing lines into the site and to the cabinetbefore 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 bondingconnections to the cabinet earth bar.

� The cabinet earth bar must be electrically connected to the master earth bar.

Transientprotection

All E1/T1 lines connected to Motorola equipment have secondary transient protection aspart of the BIB or T43 board. Ensure that the receive and transmit antenna connectionsto the building are fed through coaxial electromagnetic protection (EMP) devices.

VERSION 1 REVISION 0 Earthing and transient protection



5–31

Static frame ac cabinet earth bonding

Connect to “Master /External” Earth Bar viatop and / or bottom ofcabinet earth bar

CPX8216

CPX8216

CPX8216

Power inputswitchingpanels

Operational & Safety Earth,via 3–core power supply cord

Supplementary Earth Bond BSS101_M3Ch5_17

Static frame dc cabinet earth bonding

Safety earth withoptional dc adaptor kit

InletSockets

Operational & Safety earth connectedfrom 3-core power supply cord via cabinet earth bar

Supplementary Earthconnection via cabinetearth bar

Connect to ªMaster /Externalº Earth Bar viatop and / or bottom ofcabinet earth bar

CPX8216

REAR VIEW

CPX8216

CPX8216

BSS101_M3Ch5_17

VERSION 1 REVISION 0Cabinet earth bar connection



5–32

Cabinet earth bar connectionThe cabinet earth connection bar must be connected to a suitable external earthconnection and then the PCU Chassis earths must be connected to the cabinet earthconnection bar. This must be carried out before connecting the input power supplycables.

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 eachpower 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 earthbar 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 asuitable external earth point.

VERSION 1 REVISION 0 Cabinet earth bar connection



5–33

Swing frame cabinet earth bonding

CPX8216

InletSockets

3–core power supply cord (inc operational & SafetyEarth)

Supplementary EarthBond

Connect to “Master /External” Earth Bar viatop and / or bottom ofcabinet earth bar

CPX8216

CPX8216

Safety earthoptional dcadaptor kit

Safety earth withoptional dc adaptor kit

BSS101_M3Ch5_18

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



5–34

Connecting external dc power cables to the cabinetIn a static frame cabinet the external dc supply cables are routed from the sockets on thefront panels of the dc switches through the side of the dc switch mounting panel. The dccables are then routed inside the rear left rack member, to the selected cabinet cableentry point (top or bottom), and secured with cable ties.

In a swingframe cabinet the external supply cables are routed from the sockets on thefront panels of the power input switches behind the power input mounting panels. Thesupply cables are then routed along the left side cabinet structure, to the selected cabinetcable entry point (top or bottom), and secured with cable ties.

Observe the following rules:

� The negative (–48 V) power cable is blu e.

� The positive (0 V) return cable is blac k.

� The earth cable is yellow/green

The dc version of the PCU has dual power supply input, the second input to provideredundancy. The two dc power supply cables for each PCU are to be connected toseparate power sources.

Connectionprocedure forsupplied dcpower 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 cablekit (length of cable is limited to cable diameter).

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



5–35

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.


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

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



5–36

Connecting external ac power cables to the cabinet� 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 cablerouteing

An adequate means should be provided for routeing cables from the power source to theequipment, such as a cable trough or conduit.

The current–carrying capacity of an ac cable for continuous service is affected by all ofthe 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 ofthe ac switches, along the cabinet rails, secured by cable ties, to the selected cabinetcable entry point (top or bottom).

In a swingframe cabinet the external supply cables are routed from the sockets on thefront panels of the power input switches behind the power input mounting panels. Thesupply cables are then routed along the left side cabinet structure, to the selected cabinetcable entry point (top or bottom), and secured with cable ties.

Connectionprocedure for acdetachablepower supplycord/appliancecoupler

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



5–37

Connection procedure for ac detachable power supplycord/appliance coupler

1. Connect external ac connector to IEC 320 socket on front panel of powerinput 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.

VERSION 1 REVISION 0Connecting to external power source



5–38

Connecting to external power sourceAt 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 thecabinet 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 thecabinet.

Connecting dcpower

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 cableassembly, 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 cableassembly, 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 cableassembly, to the negative terminal of the external dc power source. See service manual.

Connecting acPower

1. Ensure the external power source is switched off.


3. Connect the plug end of ac detachable power supply cord/appliance coupler toselected external power source outlet.

VERSION 1 REVISION 0 Connecting to external power source



5–39

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.

VERSION 1 REVISION 0Powering up the Cabinet



5–40

Powering up the CabinetThis 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 upprocedure

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 beenconnected 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 cardspower up.

9. Inform the OMC–R that the PCU has been powered up.

VERSION 1 REVISION 0 Powering up the Cabinet



5–41

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.

VERSION 1 REVISION 0Routine maintenance



5–42

Routine maintenance

Cleaning fanfilters

When pulling the filter away from the fan resistance will be felt. This indicates that the fanis 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.

Postmaintenancereturn to service

After any maintenance is completed, restore the PCU and cabinet to operational stateand notify the OMC–R of PCU availability.

Field replaceableunits (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



5–43

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.

VERSION 1 REVISION 0Routine maintenance



5–44

VERSION 1 REVISION 0 Glossary of Terms



i

Glossary of Terms

VERSION 1 REVISION 0Glossary of Terms



ii

VERSION 1 REVISION 0 Numbers



iii

Numbers# Number.

2 Mbit/s link As used in this manual set, the term applies to the European4-wire 2.048 Mbit/s digital line or link which can carry 30A-law PCM channels or 120 16 kbit/s GSM channels.

4GL 4th Generation Language.

VERSION 1 REVISION 0A



iv

AA interface Interface between MSC and BSS.

A3 Authentication algorithm that produces SRES, using RANDand Ki.

A38 A single algorithm performing the function of A3 and A8.

A5 Stream cipher algorithm, residing on an MS, that producesciphertext out of plaintext, using Kc.

A8 Ciphering key generating algorithm that produces Kc usingRAND and Ki.

AB Access Burst.

Abis interface Interface between a remote BSC and BTS. Motorola offers aGSM standard and a unique Motorola Abis interface. TheMotorola interface reduces the amount of message traffic andthus the number of 2 Mbit/s lines required between BSC andBTS.

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 BTSequipment.

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



v

AET Active Events Table. Alarms and events are sent to theEvents Log in the GUI. Different operators will have differentsubscription lists. All alarms and events are sent to the AETbefore 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 channelused 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 messagebroadcast 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 integerwhich defines the absolute RF channel number.

ARQ Automatic ReQuest for retransmission.

ARP Address Resolution Protocol.

ASCE Association Control Service Element. An ASE whichprovides an AP with the means to establish and control anassociation with an AP in a remote NE. Maps directly ontothe 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 providesthe functionality for verifying the identity of an MS whenrequested by the system. Often a part of the HLR.

VERSION 1 REVISION 0A



vi

AUT(H) AUThentication.

AUTO AUTOmatic mode.

VERSION 1 REVISION 0 B



vii

B

B Interface Interface between MSC and VLR.

BA BCCH Allocation. The radio frequency channels allocated in acell 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 tobroadcast general information about a BTS site on a per cellor sector basis.

BCD Binary Coded Decimal.

BCF Base station Control Function. The GSM term for the digitalcontrol circuitry which controls the BTS. In Motorola cell sitesthis is a normally a BCU which includes DRI modules and islocated in the BTS cabinet.

BCIE Bearer Capability Information Element.

BCU Base station Control Unit. A functional entity of the BSSwhich provides the base control function at a BTS site. Theterm 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 GSMsystem.

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 12balanced (6-pair) 120 ohm (37-pin D-type connector) lines for2 Mbit/s circuits (See also T43).

BIC–Roam Barring of All Incoming Calls when Roaming outside theHome 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, databasesand 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 aparticular bit period within a timeslot.

BPF Bandpass Filter.

BPSM �BCU Power Supply Module.

VERSION 1 REVISION 0B



viii

BS Basic Service (group).

BS Bearer Service. A type of telecommunication service thatprovides the capability for the transmission of signalsbetween user-network interfaces. The PLMN connection typeused to support a bearer service may be identical to that usedto support other types of telecommunication service.

BSC Base Station Controller. A network component in the GSMPLMN which has the digital control function of controlling allBTSs. The BSC can be located within a single BTS cabinet(forming a BSS) but is more often located remotely andcontrols 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 stationcolour code. One Base Station can have several BaseStation 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 theMSC through a single interface as defined by the GSM 08series of recommendations, as being the entity responsiblefor communicating with MSs in a certain area. The radioequipment of a BSS may cover one or more cells. A BSSmay consist of one or more base stations. If an internalinterface is implemented according to the GSM 08.5x seriesof recommendations, then the BSS consists of one BSC andseveral BTSs.

BSSAP BSS Application Part (of Signalling System No. 7) (DTAP +BSSMAP).

BSSC Base Station System Control cabinet. The cabinet whichhouses one or two BSU shelves at a BSC or one or two RXUshelves at a remote transcoder.

BSSMAP Base Station System Management Application Part (6-8).

BSSOMAP BSS Operation and Maintenance Application Part (ofSignalling System No. 7).

BSU Base Station Unit shelf. The shelf which houses the digitalcontrol modules for the BTS (p/o BTS cabinet) or BSC (p/oBSSC 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 basictask groups within the GPROC.

VERSION 1 REVISION 0 B



ix

BTS Base Transceiver Station. A network component in the GSMPLMN 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. Thephysical content of a timeslot.

VERSION 1 REVISION 0C



x

CC Conditional.

C Interface Interface between MSC and HLR/AUC.

C7 ITU-TSS Signalling System 7 (sometimes referred to as S7 orSS#7).

CA Cell Allocation. The radio frequency channels allocated to aparticular cell.

CA Central Authority.

CAB Cabinet.

CADM Country ADMinistration. The Motorola procedure used withinDataGen to create new country and network files in theDataGen 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. Thereare two types of CCB, CCB (Output) and CCB (Extension).These, with up to two CCB Control cards, may comprise theTATI. The second card may be used for redundancy.

CCBS Completion of Calls to Busy Subscriber supplementaryservice.

CCCH Common Control CHannels. A class of GSM controlchannels used to control paging and grant access. IncludesAGCH, 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 carrysystem management messages.

CCH Council for Communications Harmonization (referred to inGSM Recommendations).

VERSION 1 REVISION 0 C



xi

CCIT Comité Consultatif International Télégraphique etTé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 oftelephone traffic are measured. A single call lasting onehundred 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 anomni-site, cell is synonymous with site; at a sectored site, cellis synonymous with sector. This differs from analoguesystems where cell is taken to mean the same thing as site.(See below).

Omni Site1-Cell Site

(1 BTS)

6-Sector Siteor

6-Cell Site(6 BTSs)

1 Cell =1 Sector

CEND End of charge point.

CEPT Conférence des administrations Européennes des Postes etTelecommunications.

CERM Circuit Error Rate Monitor.

CF Conversion Facility.

CF all Call Forwarding services.

CFB Call Forwarding on mobile subscriber Busy supplementaryservice.

CFC Conditional Call Forward.

CFNRc Call Forwarding on mobile subscriber Not Reachablesupplementary service.

CFNRy Call Forwarding on No Reply supplementary service.

VERSION 1 REVISION 0C



xii

CFU Call Forwarding Unconditional supplementary service.

Channel A means of one-way transmission. A defined sequence ofperiods (for example, timeslots) in a TDMA system; a definedfrequency band in an FDMA system; a defined sequence ofperiods 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 alocation 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 supplementaryservice.

CLIR Calling Line Identification Restriction supplementary service.

CLK Clock.

CLKX Clock Extender half size board. The fibre optic link thatdistributes 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 ASEwhich provides a means to transfer management informationvia CMIP messages with another NE over an associationestablished 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 sameplace.

Coincident Cell A cell which has a co-located neighbour whose cell boundaryfollows the boundary of the said cell. The coincident cell hasa different frequency type, but the same BSIC, as that of theneighbour cell.

COLP COnnected Line Identification Presentation supplementaryservice.

VERSION 1 REVISION 0 C



xiii

COLR COnnected Line Identification Restriction supplementaryservice.

CODEX Manufacturer’s name for a type of multiplexer and packetswitch 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 speedmodem used to interwork 300 to 2400 bit/s data servicesunder V.22bis, V.23, or V.21 standards. High speed modemused to interwork 1200 to 9600 bit/s data services underV.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.

VERSION 1 REVISION 0D



xiv

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 objectconfiguration 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 controlchannels 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 inHorizonmacro).

DCN Data Communications Network. A DCN connects NetworkElements with internal mediation functions or mediationdevices to the Operations Systems.

DC PSM DC Power Supply Module.

DCS1800 Digital Cellular System at 1800 MHz. A cellular phonenetwork using digital techniques similar to those used in GSM900, but operating on frequencies of 1710 – 1785 MHz and1805 – 1880 MHz.

DDF Dual-stage Duplexed combining Filter. (Used inHorizonmacro).

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.

VERSION 1 REVISION 0 D



xv

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; animmediate or deferred response is required (see also PMA).

DMA Direct Memory Access.

DMR Digital Mobile Radio.

DMX Distributed Electronic Mobile Exchange (Motorola’snetworked 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 signallingmessage 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 forPABX 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 protocolconversion between PLMN and destination network for 8circuits (p/o IWF).

DRCU Diversity Radio Channel Unit. Contains transceiver, digitalcontrol circuits, and power supply (p/o BSS) (see RCU).

(D)RCU Generic term for radio channel unit. May be standard RCU ordiversity radio channel unit DRCU.

VERSION 1 REVISION 0D



xvi

DRI Digital Radio Interface. Provides encoding/decoding andencryption/decryption for radio channel (p/o BSS).

DRIM Digital Radio Interface extended Memory. A DRI with extramemory.

DRIX DRI Extender half size board. Fibre optic link from DRI toBCU (p/o BSS).

DRX, DRx Discontinuous reception (mechanism). A means of savingbattery power (for example in hand-portable units) byperiodically and automatically switching the MS receiver onand 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 (RS232Interface).

DTRX Dual Transceiver Module. (Radio used in M-Cellarena andM-Cellarenamacro).

DTX, DTx Discontinuous Transmission (mechanism). A means ofsaving battery power (for example in hand-portable units) andreducing interference by automatically switching thetransmitter off when no speech or data are to be sent.

Dummy burst A period of carrier less than one timeslot whose modulation isa defined sequence that carries no useful information. Adummy burst fills a timeslot with an RF signal when noinformation is to be delivered to a channel.

DYNET DYnamic NETwork. Used to specify BTSs sharing dynamicresources.

VERSION 1 REVISION 0 E



xvii

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 voicecircuits.

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 spectraldensity.

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 systemto another ~ (that is, all the digits for a given call are sent atthe same time as a group). ~ sending is the opposite ofoverlap sending. A system using ~ sending will wait until ithas collected all the digits for a given call before it attempts tosend digits to the next system. All the digits are then sent asa group.

EOT End of Tape.

EPROM Erasable Programmable Read Only Memory.

VERSION 1 REVISION 0E



xviii

EPSM Enhanced Power Supply Module (+27 V).

EQB Equalizer Board. Control circuit for equalization for 8 timeslots 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 asthe ratio of time a facility is occupied to the time it is availablefor occupancy. One erlang is equal to 36 CCS. In the USthis 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 RDBMSprogramming 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.

VERSION 1 REVISION 0 F



xix

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 controlchannel which is associated with a TCH and carries controlinformation 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 controlchannel which carries information for frequency correction ofthe 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 keyindicates 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 TDMAframe within a hyperframe.

FOA First Office Application.

FOX Fibre Optic eXtender.

FR Full Rate. Refers to the current capacity of a data channel onthe GSM air interface, that is, 8 simultaneous calls per carrier(see also HR – Half Rate).

VERSION 1 REVISION 0F



xx

FRU Field Replaceable Unit.

Frequency correction Period of RF carrier less than one timeslot whose modulationbit stream allows frequency correction to be performed easilywithin an MS burst.

FS Frequency Synchronization.

FSL Free Space Loss. The decrease in the strength of a radiosignal as it travels between a transmitter and receiver. TheFSL is a function of the frequency of the radio signal and thedistance the radio signal has travelled from the point source.

FSN Forward Sequence Number.

FTAM File Transfer, Access, and Management. An ASE whichprovides a means to transfer information from file to file(OMC).

ftn forwarded-to number.

FTP Fault Translation Process (in BTS).

FTP File Transfer Protocol.

VERSION 1 REVISION 0 G



xxi

GG Interface Interface between VLR and VLR.

Gateway MSC An MSC that provides an entry point into the GSM PLMNfrom another network or service. A gateway MSC is also aninterrogating node for incoming PLMN calls.

GB, Gbyte Gigabyte.

GBIC Gigabit Interface Converter.

GCLK Generic Clock board. System clock source, one per site (p/oBSS, BTS, BSC, IWF, RXCDR).

GCR Group Call Register.

GDP Generic DSP Processor board. Interchangeable with the XCDRboard.

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 auser’s primary group.

GMB GSM Multiplexer Board (p/o BSC).

GMR GSM Manual Revision.

GMSC Gateway Mobile-services Switching Centre (see GatewayMSC).

GMSK Gaussian Minimum Shift Keying. The modulation techniqueused in GSM.

GND GrouND.

GOS Grade of Service.

GPA GSM PLMN Area.

GPC General Protocol Converter.

GPROC Generic Processor board. GSM generic processor board: a68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF,RXCDR).

GPROC2 Generic Processor board. GSM generic processor board: a68040 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 reachedby a fixed subscriber, without the subscriber’s knowledge ofthe location of the MS. A GSA may include the areas servedby several GSM PLMNs.

GSA GSM System Area. The group of GSM PLMN areasaccessible 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.

VERSION 1 REVISION 0G



xxii

GSR GSM Software Release.

GT Global Title.

GTE Generic Table Editor. The Motorola procedure which allowsusers to display and edit MCDF input files.

Guard period Period at the beginning and end of timeslot during which MStransmission is attenuated.

GUI Graphical User Interface.

GUI client A computer used to display a GUI from an OMC-R GUIapplication which is beingbrun on a GUI server.

GUI server A computer used to serve the OMC-R GUI applicationprocess running locally (on its processor) to other computers(Gui clients or other MMI processors).

GWY GateWaY (MSC/LR) interface to PSTN.

VERSION 1 REVISION 0 H



xxiii

HH 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 fromone radio channel to another radio channel. Handover allowsestablished calls to continue by switching them to anotherradio resource, as when an MS moves from one BTS area toanother. Handovers may take place between the followingGSM 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 informationdefining the higher layer characteristics of a teleservice activeon the terminal.

HLR Home Location Register. The LR where the current locationand all subscriber parameters of an MS are permanentlystored.

HMS Heat Management System. The system that providesenvironmental 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 doublethe current GSM air interface capacity to 16 simultaneouscalls 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 theframe structure.

VERSION 1 REVISION 0I



xxiv

I

I Information frames (RLP).

IA Incomming Access (closed user group (CUG) SS(supplementary service)).

IA5 International Alphanumeric 5.

IADU Integrated Antenna Distribution Unit. (The IADU is theequivalent 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 databasemanagement 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. Electronicserial number that uniquely identifies the MS as a piece orassembly of equipment. The IMEI is sent by the MS alongwith request for service.

IMM IMMediate assignment message.

IMSI International Mobile Subscriber Identity. Published mobilenumber (prior to ISDN) (see also MSISDN) that uniquelyidentifies the subscription. It can serve as a key to derivesubscriber information such as directory number(s) from theHLR.

IN Intelligent Network.

IN Interrogating Node. A switching node that interrogates anHLR, to route a call for an MS to the visited MSC.

INS IN Service.

VERSION 1 REVISION 0 I



xxv

INS Intelligent Network Service.

InterAlg Interference Algorithm. A single interference algorithm in acell.

Interworking The general term used to describe the inter-operation ofnetworks, services, supplementary services and so on. Seealso 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 servicesnetwork that provides digital connections betweenuser-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 – TelecommunicationsSector.

IWF InterWorking Function. A network functional entity whichprovides network interworking, service interworking,supplementary service interworking or signalling interworking.It may be a part of one or more logical or physical entities in aGSM PLMN.

IWMSC InterWorking MSC.

IWU InterWorking Unit.

VERSION 1 REVISION 0K



xxvi

Kk 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 theoperation of encipherment and decipherment.

kHz kilo-Hertz (103).

Ki Individual subscriber authentication Key (p/o authenticationprocess of AUC).

KIO A class of processor.

KSW Kiloport SWitch board. TDM timeslot interchanger to connectcalls (p/o BSS).

KSWX KSW Expander half size board. Fibre optic distribution ofTDM bus (p/o BSS).

kW kilo-Watt.

VERSION 1 REVISION 0 L



xxvii

LL1 Layer 1.

L2ML Layer 2 Management Link.

L2R Layer 2 Relay function. A function of an MS and IWF thatadapts a user’s known layer2 protocol LAPB onto RLP fortransmission 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 freelywithout updating the location register. An LA may compriseone or several base station areas.

LAC Location Area Code.

LAI Location Area Identity. The information indicating the locationarea in which a cell is located.

LAN Local Area Network.

LANX LAN Extender half size board. Fibre optic distribution of LANto/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 informationdefining 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 temporarilyallocated to visiting mobile subscribers in order to speed upthe search for subscriber data in the VLR, when the MSRNallocation is done on a per cell basis.

LMT Local Maintenance Terminal.

LNA Low Noise Amplifier.

LND Last Number Dialled.

VERSION 1 REVISION 0L



xxviii

Location area An area in which a mobile station may move freely withoutupdating the location register. A location area may compriseone or several base station areas.

LPC Linear Predictive Code.

LPLMN Local PLMN.

LR Location Register. The GSM functional unit where MSlocation information is stored. The HLR and VLR are locationregisters.

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 GCLKfrequency 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.

VERSION 1 REVISION 0 M



xxix

MM Mandatory.

M Mega (106).

M-Cell Motorola Cell.

M&TS Maintenance and Troubleshooting. Functional area ofNetwork Management software which (1) collects anddisplays alarms, (2) collects and displays Software/Hardwareerrors, and (3) activates test diagnostics at the NEs (OMC).

MA Mobile Allocation. The radio frequency channels allocated toan 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 mountedaway 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). Theinter-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 simpledata 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 MicroControl 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). Alsoreferred to as the Micro Control Unit in software.

MCUm The software subtype representation of the Field ReplaceableUnit (FRU) for the MCU-m.

MD Mediation Device.

MDL (mobile) Management (entity) - Data Link (layer).

ME Maintenance Entity (GSM Rec. 12.00).

VERSION 1 REVISION 0M



xxx

ME Mobile Equipment. Equipment intended to access a set ofGSM PLMN and/or DCS telecommunication services, butwhich does not contain subscriber related information.Services may be accessed while the equipment, capable ofsurface movement within the GSM system area, is in motionor 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-Rdatabase. There is a CM MIB and an EM MIB.

MIC Mobile Interface Controller.

Microcell A cell in which the base station antenna is generally mountedbelow rooftop level. Radio wave propagation is by diffractionand scattering around buildings, the main propagation iswithin street canyons.

min minute(s).

�s micro-second (10–6).

�BCU Micro Base Control Unit.

MIT Management Information Tree. Name of a file on theMotorola 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 userinterfaces with the software to request a function or changeparameters.

MMI client A machine configured to use the OMC-R software from anMMI server.

MMI processor MMI client/MMI server.

MMI server A computer which has its own local copy of the OMC-Rsoftware. It can run the OMC-R software for MMI clients tomount.

MML Man Machine Language. The tool of MMI.

MMS Multiple Serial Interface Link. (see also 2Mbit/s link)

MNC Mobile Network Code.

MNT MaiNTenance.

VERSION 1 REVISION 0 M



xxxi

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 two2 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 mobilenumber (see also IMSI). Uniquely defines the mobile stationas an ISDN terminal. It consists of three parts: the CountryCode (CC), the National Destination Code (NDC) and theSubscriber Number (SN).

MSRN Mobile Station Roaming Number. A number assigned by theMSC to service and track a visiting subscriber.

MSU Message Signal Unit (Part of MTP transport system). Asignal unit containing a service information octet and asignalling information field which is retransmitted by thesignalling link control, if it is received in error.

MT Mobile Terminated. Describes a call or short messagedestined for an MS.

MT (0, 1, 2) Mobile Termination. The part of the MS which terminates theradio transmission to and from the network and adaptsterminal equipment (TE) capabilities to those of the radiotransmission. MT0 is mobile termination with no support forterminal, MT1 is mobile termination with support for an S-typeinterface and MT2 is mobile termination with support for anR-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).

VERSION 1 REVISION 0M



xxxii

MTP Message Transfer Part.

MTTR Mean Time To Repair.

Multiframe Two types of multiframe are defined in the system: a26-frame multiframe with a period of 120 ms and a 51-framemultiframe with a period of 3060/13 ms.

MU Mark Up.

MUMS Multi User Mobile Station.

MUX Multiplexer.

VERSION 1 REVISION 0 N



xxxiii

NN/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 thecolumn contains unique values (used only with indexedcolumns).

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 ofnetwork information for example hostnames, IP addressesand 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 whichcontrol, monitor and record the use and the performance ofresources of a telecommunications network in order toprovide telecommunication services to customers/users at acertain level of quality.

NMASE Network Management Application Service Element.

NMC Network Management Centre. The NMC node of the GSMTMN provides global and centralised GSM PLMN monitoringand control, by being at the top of the TMN hierarchy andlinked to subordinate OMC nodes.

NMSI National Mobile Station Identification number.

NMT Nordic Mobile Telephone system.

NN No Nulls. A database column attribute meaning the columnmust contain a value in all rows.

Normal burst A period of modulated carrier less than a timeslot.

NPI Number Plan Identifier.

VERSION 1 REVISION 0N



xxxiv

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).

VERSION 1 REVISION 0 O



xxxv

O

O Optional.

OA Outgoing Access (CUG SS).

O&M Operations and Maintenance.

OASCU Off-Air-Call-Set-Up. The procedure in which atelecommunication connection is being established whilst theRF 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 modifyand carry out Radio Frequency planning on multiple BSSbinary files.

OLR Overall Loudness Rating.

OMAP Operations and Maintenance Application Part (of signallingsystem No. 7) (was OAMP).

OMC Operations and Maintenance Centre. The OMC node of theGSM TMN provides dynamic O&M monitoring and control ofthe PLMN nodes operating in the geographical areacontrolled 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 signallingmessage 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.

VERSION 1 REVISION 0O



xxxvi

OSF/MOTIF Open Software Foundation Motif. The basis of the GUI usedfor the Motorola OMC-R MMI.

OSS Operator Services System.

Overlap Overlap sending means that digits are sent from one systemto another as soon as they are received by the sendingsystem. A system using ~ will not wait until it has received alldigits of a call before it starts to send the digits to the nextsystem. This is the opposite of en bloc sending where alldigits for a given call are sent at one time.

VERSION 1 REVISION 0 P



xxxvii

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 infrastructureattempts to reach an MS within its location area, before anyother 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 tosend paging messages to the MSs.

PCHN Paging Channel Network.

PCHN Physical Channel.

PCM Pulse Code Modulation (see also 2 Mbit/s link which is thephysical bearer of PCM).

PCN Personal Communications Network.

PCR Preventative Cyclic Retransmission. A form of errorcorrection suitable for use on links with long transmissiondelays, 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 abuilding.

PICS Protocol Implementation Conformance Statement.

VERSION 1 REVISION 0P



xxxviii

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 alarminterface (p/o BSS).

PIXT Protocol Implementation eXtra information for Testing.

PK Primary Key. A database column attribute, the primary key isa not-null, non-duplicate index.

Plaintext Unciphered data.

PlaNET Frequency planning tool.

PLL Phase Lock Loop (refers to phase locking the GCLK in theBTS).

PLMN Public Land Mobile Network. The mobile communicationsnetwork.

PM Performance Management. An OMC application.

PM-UI Performance Management User Interface.

PMA Prompt Maintenance Alarm. An alarm report level; immediateaction 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 aco-located neighbour whose cell boundary follows theboundary of the said cell. The primary cell has a preferredband 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.

VERSION 1 REVISION 0 P



xxxix

PSPDN Packet Switched Public Data Network. Public datacommunications network. x.25 links required for NE to OMCcommunications will probably be carried by PSPDN.

PSTN Public Switched Telephone Network. The UK land linetelephone 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.

VERSION 1 REVISION 0Q



xl

QQA 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 toTDM switch highway (see MSI).

QIC Quarter Inch Cartridge (Data storage format).

QOS Quality Of Service.

Quiescent mode IDS intermediate state before shutdown.

VERSION 1 REVISION 0 R



xli

RR Value of reduction of the MS transmitted RF power relative to

the maximum allowed output power of the highest powerclass of MS (A).

RA RAndom mode request information field.

RAB Random Access Burst.

RACCH Random Access Control CHannel. A GSM common controlchannel 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 Motoroladiagnostic 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 controlcircuits, 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 uniqueidentifier, the distinguished name, for a particular networkelement.

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 (seefull rate).

resync Resynchronize/resynchronization.

REQ REQuest.

Revgen A Motorola DataGen utility for producing an MMI script from abinary object database.

RF Radio Frequency.

VERSION 1 REVISION 0R



xlii

RFC, RFCH Radio Frequency Channel. A partition of the system RFspectrum allocation with a defined bandwidth and centrefrequency.

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 userdata 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 carriesa message between devices over an association establishedby ASCE (a CCITT specification for O & M) (OMC).

Roundtrip Time period between transmit and receive instant of atimeslot in the BTS, propagation determined by the responsebehaviour of the MS and the MS to BTS delay distance.

RPE Regular Pulse Excited.

RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSMdigital speech coding scheme.

RPOA Recognised Private Operating Agency.

RPR Read Privilege Required. Access to the column is allowedonly 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.

VERSION 1 REVISION 0 R



xliii

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 theremote transcoder modules in a BSSC cabinet at a remotetranscoder site.

VERSION 1 REVISION 0S



xliv

SS/W SoftWare.

SABM Set Asynchronous Balanced Mode. A message whichestablishes the signalling link over the air interface.

SABME SABM Extended.

SACCH Slow Associated Control CHannel. A GSM control channelused by the MS for reporting RSSI and signal qualitymeasurements.

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, SAPsof a layer are defined as gates through which services areoffered 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 modulewhich 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 channelused to carry information for frame synchronization of MSsand 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 aparticular 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 controlchannel where the majority of call setup occurs. Used forMS to BTS communications before MS assigned to TCH.

VERSION 1 REVISION 0 S



xlv

SDL Specification Description Language.

SDT SDL Developement Tool.

SDU Service Data Unit.

SDR Special Drawing Rights (an international “basket” currency forbilling).

SE Support Entity (GSM Rec. 12.00).

Secondary Cell A cell which is not optimized in the network and has aco-located neighbour whose cell boundary follows theboundary of the said cell. The secondary cell has a preferredband 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 unitthat carry information for a certain user transaction; the SIFalways contains a label.

SIM Subscriber Identity Module. Removable module which isinserted into a mobile equipment; it is considered as part ofthe MS. It contains security related information (IMSI, Ki,PIN), other subscriber related information and the algorithmsA3 and A8.

SIMM Single Inline Memory module.

SIMM System Integrated Memory Module.

SIO Service Information Octet. Eight bits contained in a messagesignal unit, comprising the service indicator and sub-servicefield.

SITE BSC, BTS or collocated BSC-BTS site.

SIX Serial Interface eXtender. Converts interface levels to TTLlevels. Used to extend 2 serial ports from GPROC to externaldevices (RS232, RS422, and fibre optics).

SK Secondary Key. A database column attribute, the secondarykey indicates an additional index and/or usage as acomposite 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, ISO9596).

SMCB Short Message Cell Broadcast.

VERSION 1 REVISION 0S



xlvi

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 thesubscriber obtains GSM telecommunications services. Thismay 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 supplementto, a basic telecommunication service.

SS System Simulator.

SSA SCCP messages, Subsystem-allowed (see CCITT Q.712para 1.15).

SSAP Site System Audits Processor.

SSC Supplementary Service Control string.

SSF Subservice Field. The level 3 field containing the networkindicator 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.712para 1.18).

SSP SubSystem Prohibited message.

VERSION 1 REVISION 0 S



xlvii

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 26broadcast/common control multiframes (period 6.12s).

Super user User account that can access all files, regardless ofprotection settings, and control all user accounts.

SURF Sectorized Universal Receiver Front-end (Used inHorizonmacro).

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 modulationbit stream carries information for the MS to synchronize itsframe to that of the received signal.

SYS SYStem.

SYSGEN SYStem GENeration. The Motorola procedure for loading aconfiguration database into a BTS.

VERSION 1 REVISION 0T



xlviii

TT Timer.

T Transparent.

T Type only.

T43 Type 43 Interconnect Board. Provides interface to 12unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for2 Mbit/s circuits (See BIB).

TA Terminal Adaptor. A physical entity in the MS providingterminal adaptation functions (see GSM 04.02).

TA Timing Advance.

TAC Type Approval Code.

TACS Total Access Communications System (European analoguecellular system).

TAF Terminal Adaptation Function.

TATI Transmit Antenna Transceiver Interface. The TATI consistsof RF combining equipments, either Hybrid or CavityCombining. (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 SignallingSystem No. 7).

TCB TATI Control Board.

TCH Traffic CHannel. GSM logical channels which carry eitherencoded speech or user data.

TCH/F A full rate TCH.

TCH/F2.4 A full rate TCH at � 2.4 kbit/s.

TCH/F4.8 A full rate TCH at 4.8 kbit/s.

TCH/F9.6 A full rate TCH at 9.6 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.

VERSION 1 REVISION 0 T



xlix

TDMA Time Division Multiple Access.

TDU TopCell Digital Unit.

TE Terminal Equipment. Equipment that provides the functionsnecessary for the operation of the access protocols by theuser.

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 bitsare sent over the air. Each RF carrier is divided into 8timeslots.

Timing advance A signal sent by the BTS to the MS. It enables the MS toadvance the timing of its transmission to the BTS so as tocompensate for propagation delay.

TLV Type, Length and Value.

TM Traffic Manager.

TMI TDM Modem Interface board. Provides analogue interfacefrom IWF to modems for 16 circuits (p/o IWF).

TMM Traffic Metering and Measuring.

TMN Telecommunications Management Network. Theimplementation of the Network Management functionalityrequired for the PLMN is in terms of physical entities whichtogether constitute the TMN.

TMSI Temporary Mobile Subscriber Identity. A unique identitytemporarily allocated by the MSC to a visiting mobilesubscriber to process a call. May be changed between callsand 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 timingrecovery and channel equalization in the receiver.

TRAU Transcoder Rate Adaption Unit.

TRU TopCell Radio unit.

TRX Transceiver(s). A network component which can serve fullduplex communication on 8 full-rate traffic channels accordingto specification GSM 05.02. If Slow Frequency Hopping(SFH) is not used, then the TRX serves the communicationon one RF carrier.

TS Technical Specification.

VERSION 1 REVISION 0T



l

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 theMS_TXPWR_REQUEST and MS_TXPWR_CONFparameters.

TxBPF Transmit Bandpass Filter.

VERSION 1 REVISION 0 U



li

UUA Unnumbered Acknowledgment. A message sent from the

MS to the BSS to acknowledge release of radio resourceswhen 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 theuser.

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 fromthe full burst because of the bit shift of the I and Q parts ofthe GMSK signal.

USSD Unstructured Supplementary Service Data.

UUS User-to-User Signalling supplementary service.

VERSION 1 REVISION 0V



lii

VV Value only.

VA Viterbi Algorithm (used in channel equalizers).

VAD Voice Activity Detection. A process used to identify presenceor 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 whichprovides a temporary register for subscriber information for avisiting 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.

VERSION 1 REVISION 0 W



liii

WWAN Wide Area Network.

WPA Wrong Password Attempts (counter).

WS Work Station. The remote device via which O&M personnelexecute input and output transactions for networkmanagement purposes.

WSF Work Station Function block.

WWW World Wide Web.

VERSION 1 REVISION 0X



liv

XX.25 CCITT specification and protocols for public packet-switched

networks (see PSPDN).

X.25 link A communications link which conforms to X.25 specificationsand uses X.25 protocol (NE to OMC links).

XBL Transcoder to BSS Link. The carrier communications linkbetween the Transcoder (XCDR) and the BSS.

XCB Transceiver Control Board (p/o Transceiver).

XCDR Full-rate Transcoder. Provides speech transcoding and 4:1submultiplexing (p/o BSS, BSC or XCDR).

XCDR board The circuit board required to perform speech transcoding atthe 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.

VERSION 1 REVISION 0 Z



lv

ZZC Zone Code

VERSION 1 REVISION 0Z



lvi

bss101

Documents