motorola bss

CHAPTER 2SITE CONFIGURATION

CHAPTER 3CELLS

CHAPTER 4DEVICE/FUNCTION

EQUIPAGE

GLOSSARYCHAPTER 1BSS REVIEW

APPENDIX BHEXADECIMAL/DECIMAL

CONVERSION CHART

APPENDIX CSACCH MULTIFRAMES

APPENDIX DDATABASE SCRIPTBUILDING CHARTS

APPENDIX EADD_CELL COMMAND

PROMPTS

APPENDIX AGSM CHANNEL FREQUENCY

TABLE

APPENDIX FTYPICAL BSS SCRIPT

Cellular Infrastructure Group

SYS02BSS DATABASE

FOR TRAINING PURPOSES ONLY

ISSUE 11 REVISION 4

FOR TRAININGPURPOSES ONLY

ISSUE 11REVISION 4

SYS02BSS DATABASE

SYS02BSS DATABASE

�MOTOROLA LTD. 2000 SYS02: BSS Database


i

ISSUE 11 REVISION 4

SYS02BSS Database

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

ISSUE 11 REVISION 4

�MOTOROLA LTD. 2000SYS02: BSS Database


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.

ISSUE 11 REVISION 4



iii

General information 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important notice 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



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

Chapter 1BSS Review i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Review 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM Air Interface 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bursts 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance and Power Control 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM Control Channels 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mapping Logical Channels onto the TDMA Frame Structure 1–8. . . . . . . . . . . . . . . . . . . . . . Bursts 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 51-frame Control Channel Multiframe – BCCH/CCCH 1–10. . . . . . . . . . . . . . . . . .

Multiframes and Timing 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 51-frame Control Channel Multiframe – BCCH/CCCH 1–12. . . . . . . . . . . . . . . . . . The 102-frame Dedicated Control Channel Multiframe – SDCCH and SACCH 1–14. The 102-frame Control Channel Multiframe – Combined Structure 1–16. . . . . . . . . . .

Multiframes and Timing 1–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 26-frame Traffic Channel Multiframe 1–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Activity – Transmit and Receive Timeslots 1–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Architecture 1–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC Initialisation Process 1–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initialisation Process 1–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Management (CM) 1–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CM Database Distribution 1–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CM Database and Central Authority Interaction 1–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Change Site Database 1–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Change Remote BTS Database 1–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Database Level Numbers 1–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Radio Subsystem 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



v

BSS Configuration and Fault Management Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 1 Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 2 Protocol 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS A-bis Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Detection and Power Control 1–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Processing 1–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP L3/SCCP Preprocessor 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager (CLM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP State Machine (SSM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Comparison GSM and Motorola Systems 1–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2Site Configuration i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Configuration 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a BSS 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Base Station System (BSS) 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Base Transceiver Station (BTS) 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoder 2–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command/Database Parameter Types 2–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site/Cab/Cage Numbering Scheme 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Type 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cabinet Configuration 2–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cage Equipage 2–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . equip <site number> CAGE 2–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoder Location 2–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC Types 2–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Types 2–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC/ BTS Types 2–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPROC Slots 2–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Loss Alarms 2–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Synchronization 2–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slip Loss Alarms 2–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BER Loss Alarms 2–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BER Monitoring Periods 2–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N Bit 2–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrated M-Cell HDSL interface 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



vi

Physical interface 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL Monitoring Period 2–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL SNR 2–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL Loss of Sync Word 2–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration Exercises 2–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Configuration Exercise 1 2–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Configuration Exercise 2 2–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3Cells i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cells 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Identity 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location Area Codes 3–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Line 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defaults 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frequency Type 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Station Identity Code (BSIC) 3–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PLMN Allowed 3–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Transmit Power – Access 3–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Selection/Reselection – C1 3–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BCCH Reselection 3–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Reselection C2 3–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Temporary_offset 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Penalty_time 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cell_bar_qualify 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C2 Reselection Exercise 3–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Control Channel (CCCH) Configuration 3–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Control Channel (CCCH) Block Configuration 3–30. . . . . . . . . . . . . . . . . . . . . . . . . .

MS Paging 3–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Extended Paging 3–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Periodic Updates/rr_t3212 3–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Attach/Detach 3–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Access 3–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Emergency Call Access 3–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Requests 3–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Wait Indication 3–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Establishment 3–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rr_t3101 3–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Allocation by Interference Band 3–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Threshold 3–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



vii

Channel Allocation by Interference Band 3–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assignment of Resources 3–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Queue Management 3–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH Queuing 3–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Reconfiguration 3–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preferred Number of SDCCH 3–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Allocation 3–62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Reconfiguration 3–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Measurement Reporting for Handovers and Power Control 3–66. . . . . . . . . . . . . . . . . . . . . . .

BA – Indication 3–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BA Indicator 3–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signal Strength Measurements 3–70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signal Quality Reporting – RXQUAL 3–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Processing and Threshold Comparisons 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements Reported by MS on SACCH 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements Performed by RSS 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Threshold Comparison Process – Power Control 3–76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power Control 3–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS 3–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS 3–80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXQUAL 3–82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover – RXQUAL, RXLEV 3–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover – Interference 3–86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Power Control 3–88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS – Maximum Power 3–88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Power Control 3–90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rapid MS Power Down 3–92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Optimized Power Control 3–96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Optimized Power Control Algorithms 3–98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discontinuous Transmission 3–100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Evaluation 3–102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers Allowed 3–104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Access – handovers 3–106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers – Interference 3–108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Budget Handover 3–110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance – MS Maximum Range 3–112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover–MS Maximum Range 3–114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers 3–116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming Handovers 3–116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handovers 3–118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-Cell Handovers 3–118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH Resources Reporting 3–120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



viii

Preferred Target Cell 3–122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Reporting 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Evaluating 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Rejection 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Power Level 3–126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculated Handover Power Level 3–128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 3–128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Default Information 3–130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Initiation 3–132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rr_t3103 3–132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Channel Establishment 3–134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RSS Link Fail 3–136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Revival 3–138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loss of Radio Link 3–140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timers rr_t3109 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Failure 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Failure 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timers rr_t3109, rr_ t3111 3–144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Channel Release 3–144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rf_chan_rel_ack 3–146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Re-establishment 3–148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CRM Timers 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dealloc_inact 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ho_ack 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Exercise 3–152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Cell 3–152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add_cell Working Area 3–155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4Device/Function Equipage i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device/Function Equipage 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device and Function Dependency – In-Cell 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device and Function Dependency – M-Cell 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Kilo-Port Switch 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

KSW Extension/Expansion 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

KSW Configuration 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic Clock (GCLK) 4–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Site Processor (BSP) 4–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Code Storage Facility Processor (CSFP) 4–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Transceiver Processor (BTP) 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital Host Processor 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic Processor Equipage 4–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage of GPROC Functions 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Transceiver Function (BTF) 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



ix

Link Control Function (LCF) 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Function (OMF) 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface 4–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface – In-Cell 4–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface – M-Cell 4–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy Group 4–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF Identifier 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell ID 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna Identity 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combiner Identity 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cavity Number 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity flag 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typical Examples 4–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Tuneable Combiner (RTC) 4–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiport Serial Interface (MSI) 4–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-Cell 4–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell 4–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Path 4–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Path Equipage Exercise 4–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16 KBIT/S RSL 4–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RTF Types 4–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Receive Transmit Function (RTF) 4–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Signalling Link (RSL) 4–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Parameters 4–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Transfer Link (MTL) 4–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operations and Maintenance Link (OML) 4–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Broadcast Link (CBL) 4–70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage Exercise 4–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Details 4–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary of Terms Glos–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Numbers Glos–ii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— A — Glos–ii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— B — Glos–iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— C — Glos–v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— D — Glos–viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— E — Glos–x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— F — Glos–xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— G — Glos–xiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— H — Glos–xv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— I — Glos–xvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— K — Glos–xvii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— L — Glos–xviii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



x

— M — Glos–xix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— N — Glos–xxi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— O — Glos–xxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— P — Glos–xxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— Q — Glos–xxvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— R — Glos–xxvi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— S — Glos–xxviii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— T — Glos–xxxi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— U — Glos–xxxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— V — Glos–xxxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— W — Glos–xxxiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

— X — Glos–xxxiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix AGSM Channel Frequency Table App A–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix BHexadecimal/Decimal Conversion Chart App B–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix CSACCH Multiframes App C–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix DDatabase Script Building Charts App D–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix Eadd_cell Command Prompts App E–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix FTypical BSS Script App F–i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Answers Answers–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C2 Reselection Exercise Answers–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ADD_CELL Working Area Answers–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ADD_CELL Working Area... Answers–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ADD_CELL Working Area... Answers–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHANGE_ELEMENT Working Area Answers–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage Exercise Answers Answers–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage Exercise Answers . . . Answers–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage Exercise Answers . . . Answers–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Path Equipage Exercise Answers Answers–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4General 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.

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Reporting 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.

ISSUE 11 REVISION 4 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

ISSUE 11 REVISION 4General 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.

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Human 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.

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Human 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.

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Beryllium 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.

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Devices 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.

ISSUE 11 REVISION 4 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

ISSUE 11 REVISION 4Motorola 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

ISSUE 11 REVISION 4 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.

ISSUE 11 REVISION 4Motorola GSM manual set



18



i

Chapter 1

BSS Review

ISSUE 11 REVISION 4



ii

ISSUE 11 REVISION 4



iii

Chapter 1BSS Review i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Review 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Objectives 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM Air Interface 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bursts 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance and Power Control 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM Control Channels 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCCH Group 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mapping Logical Channels onto the TDMA Frame Structure 1–8. . . . . . . . . . . . . . . . . . . . . . Bursts 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 51-frame Control Channel Multiframe – BCCH/CCCH 1–10. . . . . . . . . . . . . . . . . .

Multiframes and Timing 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 51-frame Control Channel Multiframe – BCCH/CCCH 1–12. . . . . . . . . . . . . . . . . . The 102-frame Dedicated Control Channel Multiframe – SDCCH and SACCH 1–14. The 102-frame Control Channel Multiframe – Combined Structure 1–16. . . . . . . . . . .

Multiframes and Timing 1–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The 26-frame Traffic Channel Multiframe 1–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile Activity – Transmit and Receive Timeslots 1–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Architecture 1–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC Initialisation Process 1–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initialisation Process 1–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Management (CM) 1–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CM Database Distribution 1–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CM Database and Central Authority Interaction 1–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Change Site Database 1–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Change Remote BTS Database 1–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Database Level Numbers 1–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Radio Subsystem 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Configuration and Fault Management Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 1 Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layer 2 Protocol 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS A-bis Interface 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Detection and Power Control 1–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Processing 1–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP L3/SCCP Preprocessor 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager (CLM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP State Machine (SSM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) 1–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



iv

Comparison GSM and Motorola Systems 1–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4 BSS Review



1–1

BSS Review

Objectives

On completion of this chapter the student will be able to:

� Air Interface

1. Explain the Air Interface Structure.

2. State the functions of the BCCH, CCCH and DCCH.

3. MS Activity.

4. Timing Advance and Power Control.

� Software review

Describe the download and Initialization Process.

1. Explain how the database is distributed within a BSS.

2. State the software processes involved and how they support databasemodification.

3. Explain the function of each call processing software function and the RadioSubsystem.

4. Explain the difference between Mbis and GSM defined Abis and state theadvantages.

ISSUE 11 REVISION 4GSM Air Interface



1–2

GSM Air Interface

Bursts

Each carrier frequency used in GSM is divided into 8 independent timeslots and intoeach of these timeslots a burst is placed. The diagram shows the general form of a GSMburst.

The receiver can only receive the burst and decode it if it is received within the timeslotdesignated for it. The timing, therefore, must be extremely accurate but the structuredoes allow for a small margin of error by incorporating a ‘guard period’ as shown in thediagram. To be precise, the timeslot is 0.577ms long, whereas the burst is slightlyshorter at 0.546ms. Eight bursts occupy one Time Division Multiple Access (TDMA)frame.

The ‘‘flag-bits” are set when the frame has been ‘stolen’ by the Fast Associated ControlChannel (FACCH). The ‘‘training sequence” is used by the receiver’s equaliser as itestimates the transfer characteristic of the physical path between the Base Station (BSS)and the mobile (MS).

ISSUE 11 REVISION 4 GSM Air Interface



1–3

GSM Burst and TDMA Frame

� � � � � � � ��

��

��

��

��

��

��

��

��

��

��

�

ISSUE 11 REVISION 4Timing Advance and Power Control



1–4

Timing Advance and Power ControlTo simplify the design of the mobile, the GSM Recommendations specify an offset ofthree time-slots between the BSS and MS timing thus avoiding the necessity for themobile to transmit and receive simultaneously. The facing diagram illustrates this.

However, the synchronisation of a TDMA system is critical because bursts have to betransmitted and received within the “real-time” time slots allotted to them. The further theMS is from the BSS then, obviously, the longer it will take for the bursts to travel thedistance between them. The GSM BSS caters for this problem by instructing the MS toadvance its timing (i.e. transmit earlier) to compensate for the increased propagationdelay.

This advance is then superimposed upon the 3 time-slot nominal offset, as shown.

‘‘Power Control” allows the operator to not only compensate for the distance from MS toBSS as regards timing, but can also cause the BSS and MS to adjust their power outputto take account of the path loss. The closer the MS is to the BSS, the less the power itand the BSS will be required to transmit. This feature saves radio battery power at theMS, and helps to reduce co-channel and adjacent channel interference.

Note:

GSM Recommendations state that uplink power control is mandatory, whereas downlinkpower control is optional.

ISSUE 11 REVISION 4 Timing Advance and Power Control



1–5

Timing Advance

� � � � � � � �

��

� � � � � � � �

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4GSM Control Channels



1–6

GSM Control ChannelsThese are: Broadcast Control Channel (BCCH).

Common Control Channel (CCCH).Dedicated Control Channel (DCCH).

BCCH Group

The Broadcast Control Channels (BCCH) are downlink only (BSS to MS) and comprisethe following:

� BCCH system information broadcasts allow the MS to correctly camp onto a cell’stransmission. These messages also contain information concerning idleneighbours.

� The Synchronisation Channel (SCH) carries information for frame synchronisationand includes the BSIC.

� The Frequency Control Channel (FCCH) provides information for carriersynchronisation.

CCCH Group

The Common Control Channel Group is bi-directional ie, it works in both uplink anddownlink directions.

� Random Access Channel (RACH) is the “uplink” used by MSs to gain access tothe system.

� Paging Channel (PCH) and Access Granted Channel (AGCH) operate in the“downlink” direction. The AGCH is used to assign resources to the MS, usually aStandalone Dedicated Control Channel (SDCCH), although a TCH can beassigned in this way. The PCH is used by the system to page a MS. The PCHand AGCH are never used at the same time.

DCCH Group

Dedicated Control Channels (DCCH) are assigned to a single MS to allow point to pointsignalling transactions.

� Standalone Dedicated Control Channel (SDCCH) which supports the transfer ofData to and from the MS during call setup, location updating and Short MessageService (SMS).

� Associated Control Channel (ACCH). This consists of slow ACCH which is usedfor system information, radio link measurements and power control messages.Fast ACCH is used to pass “event” type messages e.g. handover and disconnectcommands. Both FACCH and SACCH operate in uplink and downlink directions.

ISSUE 11 REVISION 4 GSM Control Channels



1–7

Control Channels

SYS02_1_13b

LOGICALCHANNELS

DEDICATEDCHANNELS

COMMONCHANNELS

TRAFFICCHANNELS

BROADCASTCHANNELS

COMMONCONTROLCHANNELS

DEDICATEDCONTROLCHANNELS

FCCH BCCHSCH AGCHRACHPCH FACCHSACCHSDCCH TCH/HTCH/F

ISSUE 11 REVISION 4Mapping Logical Channels onto the TDMA Frame Structure



1–8

Mapping Logical Channels onto the TDMA Frame Structure

Bursts

The diagram shows the five types of burst employed in the GSM air-interface and showsthat all bursts, of whatever type, have to be timed so that they are received within theappropriate timeslot of the TDMA frame. The ‘‘burst” is the sequence of bits transmittedby the BSS or MS – the ‘‘timeslot” is the discrete period of real time within which it mustarrive in order to be correctly decoded by the receiver.

Each burst is enclosed by tail bits to indicate the beginning and the end of each burst.The guard period is provided because it is required for the MSs that transmission beattenuated for the period between bursts with the necessary ramp up and down.

1. Normal Burst:

� Carries speech, data and control information within encrypted bits.

� Training sequence is a set pattern of bits as defined by GSM Recommendations05.02.

2. Frequency Correction Burst:

� This burst is equivalent to an unmodulated carrier with a 67.7 KHz frequencyoffset, above the nominal carrier frequency.

� Used as a reference point by the BTSs to mark timeslot zero for the mobiles.

3. Synchronization Burst:

� Synchronization sequence is as defined by GSM Recommendations 05.02

� Encrypted bits identifies the BSIC and the Reduced Frame Number, as defined byGSM Recommendations 04.08.

4. Dummy Burst:

� Should any remaining timeslots on the BCCH carrier be in an idle state then theBTS will transmit a series of dummy bursts to maintain the required BCCH powerlevel.

5. Access Burst (Channel Request):

� The burst is of much shorter duration than the other types. The increased guardperiod is necessary because the timing advance necessary for transmission to theBTS is unknown when the MS is in an idle state.

� Synchronisation Sequence is a set state as defined by GSM Recommendations05.02.

� Encrypted bits identify the “cause value” and the random reference as defined byGSM Recommendations 04.08.

ISSUE 11 REVISION 4 Mapping Logical Channels onto the TDMA Frame Structure



1–9

GSM Burst Types

� � � � � � � ��

��

��

��

� ��

��

��

�

� �

�

� �

�

�

��

�(",1*.$#��'.- �,!'('(%��$+/$("$ �(",1*.$#��'.-��

��

��

��

�

��

�'0$#��'.-

��

�

��

�

��

��

�(",1*.$#��'.-

��

��

�

�1("&,)('-!.')(��$+/$("$

�

�

�

� �

�

��

�'0$#��'.- �,!'('(%��$+/$("$��

�

�'0$#��'.-

��

��

�

��

�1("&,)('-!.')(��$+/$("$

�

�(",1*.$#��'.-

��'.��/,!.')(-

�

��

� �

ISSUE 11 REVISION 4Multiframes and Timing



1–10

Multiframes and Timing

The 51-frameControl ChannelMultiframe –BCCH/CCCH

The 51-frame structure used for control channels is considerably more complex than the26-frame structure used for the traffic channels and occurs in several forms, dependingon the type of control channel and the system operator’s requirements.

ISSUE 11 REVISION 4 Multiframes and Timing



1–11

51-Frame Multiframe – Control Channel

��

� � � � � � � � � � � � � �

��

�

� � � � � � �

��

��

��

��

��

� ��

��

��




1–12


The 51-frameControl ChannelMultiframe –BCCH/CCCH

The BCCH/CCCH 51-frame structure illustrated on the opposite page will apply totimeslot 0 of each TDMA frame on the ‘BCCH carrier’ (the RF carrier frequency to whichBCCH is assigned on a per cell basis). In the diagram, each vertical step represents onerepetition of the timeslot (= one TDMA frame), with the first repetition (numbered 0) at thebottom.

Looking at the uplink (MS–BSS) direction, all timeslot 0s are allocated to RACH. This isfairly obvious because RACH is the only control channel in the BCCH/CCCH group whichworks in the uplink direction. In the downlink direction (BSS–MS), the arrangement ismore complex Starting at frame 0 of the 51-frame structure, the first timeslot 0 isoccupied by a frequency correction burst (‘F’ in the diagram), the second by asynchronisation burst (‘S’) and then the following four repetitions of timeslot 0 by BCCHSystem Information data (B) in frames 2–5. The following four repetitions of timeslot 0 inframes 6–9 are allocated to CCCH traffic (C) – that is, to either PCH (mobile pagingchannel) or AGCH (access grant channel). Then follows, in timeslot 0 of frames 10 and11, a repeat of the frequency and synchronising bursts (F and S), four further CCCHbursts (C) and so on ..... Note that the last timeslot 0 in the sequence (the fifty-firstframe – frame 50) is idle where the BTS will transmit a dummy burst.




1–13

BCCH/CCCH Multiframe

��

�

��

��

��

��

ÈÈÈÈÈÈÈÈÈÈ

� ��

��

��

��

��

�

��

��

��

�

��

�

�!( �� "��

��

�� !��

�� $!��%&�

�� $�#'� �)�

�� ) ��

�� !��! �

��




1–14


The 102-frameDedicatedControl ChannelMultiframe –SDCCH andSACCH

The diagram shows the 51-frame structure used to accommodate 8 SDCCHs although,as it takes two repetitions of the multiframe to complete the entire sequence, it may bemore logical to think of it as a 102-frame structure! This structure will be used on aphysical channel selected by the system software – it is not placed in a timeslot or on anRF carrier specifically defined by GSM Recommendations.

Note that the 8 SACCHs (shaded) are associated with the 8 SDCCHs. It is important toremember that each SDCCH has an SACCH just like a traffic channel.




1–15

DCCH Multiframe

��

��

��

��

�

��

��

�

��

��

ÈÈÈÈÈ�

�

��

��

��

��

�

��

��

��

�

��

�

� $�� !��

��

��



��

ÈÈÈÈ�

ÈÈÈÈÈÈÈÈ

ÈÈÈÈÈÈÈÈ�

�

�

�

��

��

��

��

��

�

��

��

�

��

ÈÈÈÈ�

ÈÈÈÈÈÈÈÈ

ÈÈÈÈÈÈÈÈ�

�

��

��

��

��

��

��

��

�

��

��

�

��

��

��

��

��

�

��

��

�

�

��

ÈÈÈÈ�

��

�

ÈÈÈÈÈÈÈÈ

ÈÈÈÈÈÈÈÈ

��

��

�� #��

�� "" ��#��

��




1–16


The 102-frameControl ChannelMultiframe –CombinedStructure

The structure illustrated can be used where traffic density is low – perhaps in a rural areain cells with few RF carriers and only light traffic. Again, as it takes two repetitions of the51-frame multiframe to complete the sequence, this is really a 102-frame structure.

In this case, all the control channel types (with the exception of the ‘frame-stealer’FACCH) can share the BCCH carrier timeslot 0. In this configuration more SDCCH canstill be configured in the cell, albeit in other timeslots, however no more CCCH can bedefined.




1–17

Combined Multiframe

��

�� !�" �

�� %"��&'�

�� %�$(�!�*�

�� *!��

�� " "!�

�� '��

�� &&"��'��

��

��

�

��

�

�

��

��

��

��

��

��

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ


��

��

��

ÈÈÈÈÈÈÈÈ

�

�

��

��

��

�

�

�")!��!� �#��!��

�

��

�

�

��

��

��

��

��

��

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ


��

��

��


�


��

��


��

��

��

��

�

��

��

��

�

�


��

��


��

��

��

��

��

��

��

��

��

��




1–18

Multiframes and TimingThere are eight timeslots within each TDMA frame, enabling eight physical channels toshare a single physical resource – the RF carrier. In turn, each physical channel may beshared by a number of logical control or traffic channels.

In order to understand how a single physical channel is shared by various logicalchannels, it is necessary to introduce the GSM multiframe structures that make itpossible.

The 26-frameTraffic ChannelMultiframe

The illustration opposite shows the time relationship between timeslot, TDMA frame, andthe 26-frame multiframe. Some of the times shown are approximate numbers as theGSM Recommendations actually state the exact values as fractions rather than indecimal form (eg. the exact duration of a timeslot is 15/26ms).

Note that frame 12 (the 13th frame in the 26 frame sequence) is used by the SlowAssociated Control Channel (SACCH) which carries link control information to and fromthe mobile and base station. Also note that frame 25 is depicted as idle. The reasonwhy this frame is called idle is because uplink and downlink transmissions are temporarilysuspended. The MS, during this period, will go into ’search mode’ in an effort tointerrogate a neighbouring Base Transceiver Identity Code (BSIC).




1–19

26-Frame Multiframe

��

��

�

��

��

��

��

��

��

��

��

��

� � � � � � � � ��

ISSUE 11 REVISION 4Mobile Activity – Transmit and Receive Timeslots



1–20

Mobile Activity – Transmit and Receive TimeslotsAs the mobile only transmits or receives its own physical channel (normally containingTCH and SACCH) for one-eighth of the time, it uses the remaining time to monitor theBCCH frequency of adjacent cells. It completes this process every 480ms, or four26-TCH multiframes. The message that it sends to the BSS (on SACCH, uplink)contains the Receive Signal Strength Indication (RSSI) of the adjacent cells, plus that ofthe link from the BSS itself and also an indication of the quality of the current connection.This quality measurement is somewhat similar to a bit-error rate test. Just as the MScompletes one series of measurements, it completes sending the previous series to theBSS and starts to send the latest series: thus the processes of compilation andtransmission form a continuous cycle.

ISSUE 11 REVISION 4 Mobile Activity – Transmit and Receive Timeslots



1–21

MS activity

SYS02_MSactivity

NeighbourServing

Mobile retunesand listens toNeighbour celland retunes to

MobileRetunes

Mobile Transmits

Mobile ReceivesA

BD

C

1 5 6 7 0 1 2 3 4 5 6430 2 7

1 5 6 7 0 1 2 3 4 5 6430 2 7

TDMA

Downlink

Uplink

Sample

1ms 2ms

A B C D

serving cell

ISSUE 11 REVISION 4Software Architecture



1–22

Software ArchitectureThe BSS software is made up of a number of different files called code objects.

These files are downloaded into a site by various means.

All the processors resident in a cabinet receive all the downloaded code object files,which are stored in the RAM memory.

Each code object file has the capability of becoming a system application process, butwith certain exceptions – the first being the database, the second is the executive, andthe third being the object list.

The applications created on individual processors is decided by the fault managementsoftware during the initialisation of the site.

ISSUE 11 REVISION 4 Software Architecture



1–23

BSS Software

� ��

��

��

� ��

��

��

ISSUE 11 REVISION 4BSC Initialisation Process



1–24

BSC Initialisation ProcessThe BSC executive process is responsible for starting the initialisation of the GPROC,using the initialisation process (IP), which is stored on Flash eeprom.

1. The GPROC starts off in the ROM exec monitor mode. In this mode the IP has no database to work with. Therefore it works with default values written into the IP. At this stage the master GPROC may or may not have code, this will be determined by checking the object list if available.

2. The IP first initialises the LAN, so that any GPROCs may talk to one another. On LAN initialisation, the GPROC audits the LAN to ascertain how many GPROCs there are on the LAN.

3. The IP then decides which GPROC is to become the master. (The master GPROC is normally a GPROC in the slot defined in the IP)

4. The IP then tests KSWs, MSI, and XCDR boards which are defined in the IP.

5. Then the IP must determine whether any code exists on the ANY GPROC.

6. If code exists on a GPROC which is not the master, the Master GPROC will arrange to load all other GPROCS from that code source, provided the code is the same as the code held at the OMC. This is determined once the object list that is received from the OMC is compared against the stored object list.

7. If no code exists on the Master GPROC, download the code from an available source.The code sources are:

a) if site is a BSC > from OMCb) if site is a BTS > from BSC

8. When the Master GPROC has received all the required code, the IP on the Master GPROC will cross-load all the other GPROCS on the LAN.

9. Once the Master GPROC has received confirmation from the other GPROCS that the cross-load has been successful, a message is broadcast to all GPROCS to go to RAM exec monitor.

ISSUE 11 REVISION 4 BSC Initialisation Process



1–25

Initialisation Process

��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

��

��

� ��

� ��

ISSUE 11 REVISION 4Initialisation Process



1–26

Initialisation ProcessOnce in RAM the first check that is made is for a valid database, this is carried out bycalculating a checksum based on the stored database and comparing this against thestored checksum. Although apparently correct, there may be level number differenceswhich will cause the download of a new database.

Now in RAM the IP once again initialises the LAN, because when moving from ROMEMON to RAM EMON the LAN deactivates.

If no database exists, then the IP waits 45 seconds before ‘rebooting’ the site andstarting the initialisation process again.

A system operator has this time period to enter the MMI Command Sysgen on. This tellsthe IP software that a database is going to be provided. The IP will re-initialise the siteand go through the IP from the start, but will stop at this point. The system operator canthen provide a database. Once the database has been provided, the operator usesanother MMI command, Sysgen off, and the master GPROC will then cross-load thisnew database to each GPROC on the LAN.

On completion of database crossloading to all GPROCs, the IP initiates the CentralAuthority (CA) process. When this happens it is the CA process that now looks after theinitialisation of the site. The IP performs one more task if the site is a BSC – it helps theCentral Authority to ‘bring up’ the remote BTSs. The CA informs each BTS site its sitenumber then each BTS is downloaded by the BSC. The database contains informationrelating to the entire BSS and is downloaded in its entirety.

Each BTS site will follow a similar IP, however these will differ between In-Cell andM-Cell. The major exception being that unlike the BSC, a BTS has to set up its signallinglink to the BSC and not the OMC. This link is called the Radio Signalling Link (RSL) andused for the download process.

Once the BTS has been downloaded from the BSC including the BSS database it willactivate that part of database relevant to it.

ISSUE 11 REVISION 4 Initialisation Process



1–27

Initialisation Process

��

� ��

� ��

� ��

��

� ��

� ��

��

��

ISSUE 11 REVISION 4Configuration Management (CM)



1–28

Configuration Management (CM)

Overview

The Configuration Management (CM) software is responsible for managing and updatingthe main configuration database at either a BSC or a BTS. This is the database that isdownloaded as an object file in the download code. In this database is held all the siteparameters such as carrier frequencies, site configuration, surrounding site informationand handover parameters. Also stored in this database is device functionality anddistribution as well as all timing information for the site.

All application processes have access to this database but their access is read only. Ifthe CM database is required to be changed, the CM process performs this task. Thisprocess has both read/write access to the CM Database.

ISSUE 11 REVISION 4 Configuration Management (CM)



1–29

Configuration Management Overview

��

��

��

��

ËËËËËËËËËËËËËËËË

ËËËËËËËËËËËË

ËËËËËËËËËËËËËËËËËËËË

��

��

ISSUE 11 REVISION 4CM Database Distribution



1–30

CM Database DistributionThe CM database is distributed across all active GPROCs on any particular LAN. On theLAN, one GPROC is designated to have the master CM database and hence the CMapplication process is also present on this GPROC.

If there are to be any changes to the CM database, the new information is written into themaster CM database via the CM application process. Once the CM database haschecked with other system processes, and is happy that the changes are usable, themaster CM database then broadcasts these changes to all CM databases of all GPROCson its particular LAN. If the CM process is at the BSC, this process will also broadcastany changes to each BTS site.

ISSUE 11 REVISION 4 CM Database Distribution



1–31

CM Database Distribution

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4CM Database and Central Authority Interaction



1–32

CM Database and Central Authority Interaction

To Change SiteDatabase

When outside of Sysgen mode any changes that are to be made to the CM databasehave first to be checked and approved by the CA. This is done to ensure that the desiredchanges are possible given the state of the devices in the system.

1. Changes to database downloaded to MMI process from OMCR.

2. The changes are downloaded to the CM process from the MMI process.

3. The CM process writes the changes into the CM database.

4. The CM process transfers the proposed changes to the CA.

5. The CA replies as to whether the desired changes are possible. (Yes orNo).

6. If the CA answers ‘yes’, the CM process then broadcasts the changes to all the CM databases of GPROCs on its site. If the answer is ‘no’, the CM process instructs the CM database to erase the changes.

7. The CM process uploads the outcome of the operation to the MMI process, i.e. changes possible or not possible.

8. Operation outcome uploaded to the OMCR.

With the release of GSR3 (1.5.1.0) all database change commands will only be allowedat the BSC. At times it is necessary to update the database while visiting a site. Thiscan be done using rlogin to set up a remote login to a GPROC at the BSC from the BTS.This then allows MMI commands to be entered from the BTS as though from the BSC.

ISSUE 11 REVISION 4 CM Database and Central Authority Interaction

MOTOROLA LTD. 2000 SYS02: BSS Database


1–33

To Change Site Database

��

��

��

��

��

��

��

��

��

��

��

��

� �

��

�

� �

�

�

�

�

��

��

��

��

��

��

ISSUE 11 REVISION 4CM Database and CA Interaction



1–34

CM Database and CA Interaction

To ChangeRemote BTSDatabase

The process for changing elements of the database outside of Sysgen at a remote BTSis basically similar to the process of changing a single site database.

1. The OMCR downloads the proposed changes to the BSC MMI process.

2. The BSC MMI downloads the changes to the BSC CM process.

3. The BSC CM process then writes the proposed changes into the BSC master CM database. The BSC CM process also sends the proposed changes to the BTS CM process.

4. The BTS CM process then writes the changes into the BTS master CM database.

5. The BTS CM process sends the proposed changes to the CA for the BTS site.

6. The CA replies yes or no to changes.

7. The BTS CM process tells the BSC CM Process yes or no as to whether changes possible.

8. If answer from CA is yes, both CM processes now broadcast database changes to all CM databases on their respective LANs.

9. BSC CM process then tells BSC MMI the outcome of the operation, i.e. whether changes have been completed or not.

10. BSC MMI uploads the operation outcome up to the OMCR.

ISSUE 11 REVISION 4 CM Database and CA Interaction

MOTOROLA LTD. 2000 SYS02: BSS Database


1–35

To change Remote Database

��

��

��

��

��

��

��

��

� �

�

�

�

�

��

��

��

��

��

��

��

��

��

��

�

�

�

��

��

��

��

� �

�

�

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Database Level Numbers



1–36

Database Level NumbersSubsequent changes to a database during call processing can be made from the OMCusing a number of input mechanisms, these are TTY, Forms, Batch and Detailed view. Inany case the update is sent to the required entities using the procedure outline in theprevious pages.

The whole database for a BSS is stored in every entity of the BSS, the BSC for examplewill initially have the same database as each BTS. Subsequent changes during callprocessing will cause a disparity between databases held in different entities. If, forexample four consecutive changes are made to the database of BTS 3 using forms atthe OMC. The level number for BTS 3 at the BSC will be incremented by four, likewisethe level number at BTS 3 will also be incremented by four. Even though the database atBTS 3 has changed the alterations are not passed on to BTS 1 or 2, they will still havethe old database for BTS 3 in store. Certain changes to a BTS database may be copiedto other BTS’s, these changes will be necessary for the correct operation of the handoverprocedure.

In the example shown opposite four changes have been made to the database of BTS 3and one change has been made to the database of BTS 2. For each change made to anindividual site the database level number is incremented on a site basis, for each changemade to a BSS database the level number of the BSC is incremented.

If these changes are made using TTY, Batch, Forms or Detailed View at the OMC thechanges are made in the BSS as discussed but are not copied to the master databaseheld by the OMC. Hence any changes made to the BSS database should be followed atsome stage with a database upload to renew the database in the OMC. If this procedureis not carried out, upon a BSC reset, the OMC could potentially download an olddatabase not current with any recent changes that have been made. As the OMC isdeemed the master entity the BSC would abandon any database it held and implementthe one being held and subsequently downloaded by the OMC.

ISSUE 11 REVISION 4 Database Level Numbers



1–37

Database Level Numbers

��

��

��

��

��

�

��

��

��

��

��

��

�

��

��

��

�

��

��

��

�

��

��

��

��

��

��

��

ISSUE 11 REVISION 4BSS Radio Subsystem



1–38

BSS Radio Subsystem

Overview

The Radio Subsystem (RSS) is a collection of application processes whose purpose is tomanage the BSS RF hardware and the radio link to the MSs. The RSS functions includethe Layer 2 interface to the MS LAPDm and radio link control including the handoverdetection and power control process.

The RSS portion of the BSS implements the interconnection between the applicationlayer (Layer 3) and the physical channel hardware (layer 1). Currently one instance ofRSS has the messaging capability to handle six carriers, although an instance of RSSwould normally handle Layer 2 control for only 2 or 3 DRIMs, depending on the trafficmodel in use. RSS runs on a single or multiple GPROCs which must be physicallylocated in the same cage as the Digital Radio Interface boards it controls.

The RSS is comprised of five components:

1. RSS configuration and fault management

2. Layer 1 Interface

3. Layer 2 Protocol

4. RSS A-bis interface

5. Handover detection and power control

ISSUE 11 REVISION 4 BSS Radio Subsystem



1–39

Radio Subsystem (RSS)

� ��

��

� ��

��

ISSUE 11 REVISION 4BSS Configuration and Fault Management Interface



1–40

BSS Configuration and Fault Management Interface

Overview

This process controls the configuration of its related DRCUs, and is the interface to theBTS fault management system. With regard to configuration, this process is responsiblefor informing the hardware as to its configuration, and instructing the DRCU as to theusage of each timeslot (e.g. BCCH, SDCCH 8 channel or TCH/FS). The process alsohas the responsibility of downloading the DRIM board during the initialisation of the basesite, as well as the loading and configuration of the DRCU before call processing isachieved.

The collection of alarm and error messages is also the responsibility of this process. Thealarm and error indications are then forwarded to the Fault Collection Process (FCP) ofthe GPROC on which the RSS functionality exists.

Layer 1 Interface

The Layer 1 process translates the message protocol used in the GPROC into themessage protocol used by the DRIM. Also, the addressing used by the higher systemlayers must be translated into the actual memory location addressing used by the DRIM.

This process stacks paging messages and access granted messages until the relevanttimeslot appears on the control channels.

Layer 2 Protocol

This process is responsible for translating any signalling information for the MS receivedfrom the MSC into GSM signalling used on the air interface on a per timeslot basis. Thisprocess handles all LAPDm protocol messaging for the MS.

The Layer 2 is responsible for setting up the link to the MS, over the air interface, tosupport the SMS data transfer, irrespective of whether the SMS is MS originated or MSterminated.

RSS A-bisInterface

This process is responsible for the translating of all messages generated inside the RSSinto A-bis format messages for transmission to any Layer 3 application processes. Anymessages received by this process are verified to make sure they are complete.

If the system becomes overloaded by traffic, the RSS A-bis Interface intercepts anyrandom access messages and automatically gives a ‘no access’ message back to theMS. This action is undertaken in response to commands from the call processingsoftware. When traffic becomes lower, RSS A-bis Interface allows random accessmessages to proceed to call processing software.

ISSUE 11 REVISION 4 BSS Configuration and Fault Management Interface



1–41

Radio Subsystem (RSS)

��

��

��

� ��

��

��

��

��

RSS

ISSUE 11 REVISION 4Handover Detection and Power Control



1–42

Handover Detection and Power ControlThis process has by far the most functions to fulfil inside the RSS. It controls thetransmission power of the MS (uplink) and also the transmission power of its related TCU(downlink) on a per timeslot basis. The object is to keep both the MS and the TCU on thelowest possible transmission power to help reduce interference between system users.This process is also responsible for calculating the MS’s timing advance to keep themobile inside its allocated timeslot.

The handover detection and power control process takes responsibility for initiating thehandover process for a MS. It decides when the handover is necessary, i.e. the MS is onmaximum power but the received level at the BSS is still too low or the MS is onmaximum timing advance. It follows the handover procedure as suggested in GSMRecommendation 5.08 plus a number of special Motorola algorithms can beimplemented.

When TCHs are idle, this process monitors the ambient noise in the receive slot period.After processing, the average noise level per TCH is passed to call processing.

Once a call to a MS has been established, if a MS leaves the system without terminatingthe call, the system will waste its resources if the MS channel remains in operation. Toreduce this, the handover detection and power control process monitors the SACCHmessages from all MS on its busy TCHs. If a number of consecutive SACCH messagesfrom a particular MS fail to appear, the process informs call processing software to closedown the resources allocated to that MS.

All messaging to and from the handover detection and power control process are in theA-bis format. Therefore the location of this process is in theory interchangeable,depending upon which A-bis format is chosen.

ISSUE 11 REVISION 4 Handover Detection and Power Control



1–43

Handover Detection and Power Control

��

� ��

� ��

� ��

� ��

� ��

� ��

��

ISSUE 11 REVISION 4Call Processing



1–44

Call Processing

Overview

BSS call processing is a collection of Layer 3 application processes whose purpose is todeal with the high level control of MS calls.

The call processing software is responsible for the call setup and clearing of allMS-originated calls, as well as Mobile Switching Centre (MSC)-originated MS pages. TheBSS software undertakes all encryption tasks for the system, only over-the-air interface,all messages on the system terrestrial links are in ‘plain language’.

Once a MS is established on a channel, be it a traffic channel or control channel, allsignalling between the MS and the MSC are transparent to the BSS software. All theBSS software undertakes is to maintain the channel to the MS, whilst passing on anysignalling to the MS. The BSS software does not track the identity of a MS.

The decision to handover is made by CP and it chooses the target cell in response to thechoices provided by the RSS. The BSS controls all intra-cell and intra-BSS handovers,whilst in an inter-BSS handover, the BSS informs the MSC of the MS’s choices of targetcells and the MSC controls the MS’s transfer to the new cell. In an intra-cell andintra-BSS handover, the MS will remain on the same terrestrial trunk connection to theMSC.

ISSUE 11 REVISION 4 Call Processing



1–45

Call Processing

� ��

��

� ��

� ��

� ��

� ��

��




1–46

Call Processing

MTP L3/SCCPPreprocessor

This process handles the protocol adaption of messages when transmitting or receivingmessages on the A interface. It also determines which process each message isdestined for by interrogating the message header, it then addresses the messageaccordingly.

ConnectionlessManager (CLM)

The CLM deals with the global control of a BSS. This process deals with thenon-connection orientated portion of the C7 signalling.

SCCP StateMachine (SSM)

The Signalling Control Connection Part State Machine (SSM) is responsible for handlingall the connection orientated portion of the C7 Signalling.

The SCCP State Machine is responsible for co-ordinating all intra-BSS and intra-cellhandovers. It makes sure that the target cell is informed of the handover request andensures that a radio channel is allocated to the mobile station. This process generates allthe required messaging/signalling to co-ordinate a handover, it will also inform the MSCwhen this procedure has been completed . The SCCP State Machine informs the sourcecell of a successful handover in order that radio resources can be deallocated.

Switch Manager(SM)

The function of the SM is to connect a MS’s terrestrial trunk from the MSC (designatedby the MSC), to the radio channel given to a MS by the cell resource manager in theBSS software.




1–47

Call Processing – Flow Chart

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

� ��

��




1–48

Cell ResourceManager (CRM)

The CRM is responsible for the allocation of radio channels in response to either a MSaccessing the system or the MSC paging a MS. The CRM keeps a dynamic databaseconcerning the state of each of its channels, and uses the interference informationprovided by the RSS to allocate the best available resource.

When the traffic loading on a BTS site or cell becomes too heavy, the CRM can instigateflow control. The CRM tells the A-bis Interface in the RSS software to block any furtherRandom Access requests from MS on that cell or site. When traffic load reduces, thisflow control will be removed.

Radio ResourceState Machine(RRSM)

The Radio Resource State Machine (RRSM) is the call processing software entityresponsible for the initiation and maintenance of physical connections.

This process is responsible for the activation of the radio channels sourced from theCRM. When a MS no longer requires a radio channel, the RRSM is responsible forclosing the channel down.

Radio ChannelInterface (RCI)

The RCI process changes the address of a MS used in the RSS into the address usedby the Layer 3 call processing processes.

The RSS addresses MS by using its channel number, whilst the Layer 3 Call Processingprocesses address messages for a MS using the SCCP reference number.

These processes can be located dependant on which form of A-bis is chosen. UnderMotorola systems these reside at the BTS cabinet.




1–49

Radio Channel Allocation

SYS02_1_radio_channel

BSC MTL

LCFBSP

CLM

SM

MTPL2

MTPL3SCCP PRE PRO

SSMHO

EVAL

LCF MTPL2

MTPL3SCCP PRE PRO

SSMHO

EVAL

LCF MTPL2

MTPL3SCCP PRE PRO

SSMHO

EVAL

In–CellBTS

In–CellBTS

M–CellBTS

BTP

RSS

DHP

RSS

DHP

CRMRCI

RRSM

RSS

DHP

RSS

DHP

BTPCRM

RCIRRSM

RSS

DHP

MCU

RSS

TCU

CRMRCI

RRSM

ISSUE 11 REVISION 4Comparison GSM and Motorola Systems



1–50

Comparison GSM and Motorola SystemsUnder the GSM defined system, most of the ‘intelligence’ of the BSS is kept at the BSC.All handover decisions, allocation of TCHs and monitoring of active radio channels isdone at the BSC itself. This means that a great deal of control messaging/signalling mustpass between the BTS and the BSC along the A-bis interface, the greatest overheadbeing MS uplink measurement reports.

Due to the large amount of signalling/message transfer, there is a large requirement forRadio Signalling Link (RSL) timeslots between the BSC and BTS.

These RSL timeslots utilise the Link Access Protocol Data Layer 2 protocol to carry thesignalling and BTS control messages. Each LAPD signalling link will occupy a complete64 Kbit/second timeslot on the A-bis Interface.

ISSUE 11 REVISION 4 Comparison GSM and Motorola Systems



1–51

GSM System

��

� ��

��

��

��

��

��

��

� ��

� ��

��

��

��

� ��

��

� ��

��

��

� ��

��

� ��

��

��

��

��

��

��

��

��




1–52

Comparison GSM and Motorola SystemsUsing the Motorola system, the control of the radio and terrestrial circuits are splitbetween the BSC and the BTS. The BSC retains the processes which controls theterrestrial links up to the MSC and the final decision process concerning handovers.Whilst the BTS now has all the processes whose job is to monitor and control the radiochannels. The Motorola application generally needs 1 RSL per BTS site.

This reduction in dedicated A-bis links is achieved because far fewer controlmessages/signalling is required between the BSC and the essentially more intelligentBTS. Using less 2MB timeslots for signalling allows more TCH channels and hencemore economic use of the BSC–BTS link.

ISSUE 11 REVISION 4 Comparison GSM and Motorola Systems



1–53

Motorola System

��

��

��

��

��

� ��

� ��

��

��

��

� ��

��

� ��

��

��

� ��

��

� ��

��

��

��

��

��

��

��

��

��

��

��

��




1–54



i

Chapter 2

Site Configuration

ISSUE 11 REVISION 4



ii

ISSUE 11 REVISION 4



iii

Chapter 2Site Configuration i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a BSS 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Base Station System (BSS) 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Base Transceiver Station (BTS) 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoder 2–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command/Database Parameter Types 2–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site/Cab/Cage Numbering Scheme 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Type 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cabinet Configuration 2–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cage Equipage 2–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . equip <site number> CAGE 2–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoder Location 2–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC Types 2–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Types 2–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC/ BTS Types 2–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPROC Slots 2–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Loss Alarms 2–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Synchronization 2–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slip Loss Alarms 2–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BER Loss Alarms 2–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BER Monitoring Periods 2–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

N Bit 2–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrated M-Cell HDSL interface 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraints 2–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Physical interface 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data 2–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL Monitoring Period 2–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL SNR 2–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HDSL Loss of Sync Word 2–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Site Configuration Exercises 2–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Configuration Exercise 1 2–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Configuration Exercise 2 2–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



iv

ISSUE 11 REVISION 4 Site Configuration



2–1

Site Configuration

Objectives


� Describe the device/function interdependency with the database structure.

� Describe typical BSS configuration and terrestrial traffic and signalling links.

� Equip and understand the database fields associated with site configuration.

ISSUE 11 REVISION 4Configuring a BSS



2–2

Configuring a BSSThe flowchart on the facing page details the sequence of building a database script, theorder and content of such a script will change depending on its function, RXCDR, BSS,BSC, BTS or Path.

Appendix 6 shows a more detailed flow chart for each script type.

ISSUE 11 REVISION 4 Configuring a BSS



2–3

General Database Script

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4The Base Station System (BSS)



2–4

The Base Station System (BSS)A BSS can be divided into three functions, the BSC, the BTS and the XCDR.

The BSC is the digital control function which performs the following:

1. Controls all associated Base Transceiver Stations (BTS).

2. Performs call processing

3. Supports operations and maintenance

4. Supports the interface between the BSS and Mobile Switching Centre (MSC).

5. Supports the interface between the BSC and BTS.

The BSC and BTS function can be combined in a single In-Cell cabinet to form astandalone BSS, can be co-located with its associated BTSs or the BSC can be remotelylocated from the BTSs.

The BaseTransceiverStation (BTS)

The BTS provides the Radio Frequency (RF) equipment that supports the radio path tothe mobile station (MS) and the digital control functions to support it.

ISSUE 11 REVISION 4 The Base Station System (BSS)



2–5

BSC Site Configuration

��

��

��

��

��

��

��

��

��

��

��

��

�!��

��

��

��

��

��

ISSUE 11 REVISION 4Transcoder



2–6

TranscoderThe transcoder (XCDR) is the digital signal processing equipment that performs GSMdefined speech encoding and decoding. That transcoding function can be performedwithin the BSC or remotely, normally at the MSC location.

ISSUE 11 REVISION 4 Transcoder



2–7

Transcoding

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Command/Database Parameter Types



2–8

Command/Database Parameter TypesMMI commands and database parameters are classified on the basis of whether or not auser action is required to enter the command or change the value of the databaseparameter.

Type A

No special user action is required to enter a Type A command or change a Type Adatabase parameter.

Type B

Special conditions must exist in the system when entering a Type B command orchanging a Type B database parameter. The special conditions are included in theOperator Actions listing of each command and database parameter description.

ISSUE 11 REVISION 4 Command/Database Parameter Types



2–9

Command Types

� ��

� ��

� ��

� ��

��

ISSUE 11 REVISION 4Site/Cab/Cage Numbering Scheme



2–10

Site/Cab/Cage Numbering SchemeMotorola have developed a conventional numbering scheme that must be adhered to inthe equipage of a SITE, CABINET and CAGE. Cage references are only for In-Cellstations, cages cannot be explicitly equipped at M-Cell sites.

The following table specifies this convention

SITE/CAB/CAGE NUMBERING CHART

��

��

��

� � ��

��

Shown opposite are some typical examples of this scheme.

ISSUE 11 REVISION 4 Site/Cab/Cage Numbering Scheme



2–11

Site Equipage

��

��

� �

� �

��

��

��

��

� �

��

��

��

� �

��

��

��

� �

��

��

��

��

� �

��

��

� �

��

��

��

ISSUE 11 REVISION 4Site Configuration



2–12

Site ConfigurationThe first line in a database script will equip the site, this is carried out by using the equipcommand. After entering the first line further prompts will appear:

equip <0 or bsc> SITE

1st prompt (identifier):

This prompt specifies the unique identifier for the site.

Additional prompts for BTS sites only:

2nd promp (BSP/LCF):

This field denotes whether a BSP or LCF is supporting RSLs for the specified BTS site.

3rd prompt (BSP/LCF):

This field denotes the unique identifier of the BSP or LCF supporting the RSLs (callprocessing) for the specified BTS site.

4th prompt (RSL Rate):

This prompt specifies the RSL rate to be implemented at this rate. The prompt isdisplayed only if the site is remote and the 16k RSL option is enabled.

5th prompt (Dynamic Allocation):

This prompt only appears if:

� The dynamic allocation feature is unrestricted.

� The site being equipped is a standalone BTS

ISSUE 11 REVISION 4 Site Configuration



2–13

Site Configuration

�'+ &��)��%(��

� �$*�(�*�� $* � ��* %$��

�� * %$�"�&(%#&*)��%(��%$",�

� �$*�(�*��*,&��%��%(��

� �$*�(�*�� $* � �(�%(��$*�(��+$�* %$��%(��

��

� � ��

� �$*�(��*��%(��

� �%�)�*��) *��+)��,$�# ��""%��* %$�%��*�((�)*( �"

��! $��(�)%+(��)�

��,�)

��$%

ISSUE 11 REVISION 4Site Type



2–14

Site TypeThe BSS is very flexible and can have many configurations consisting of three elements;

1. Base Station Controller (BSC)

2. Base Transceiver Station (BTS)

3. Transcoding

The BSC and BTS functions can be in different locations, at the same location or evenwithin the same cabinet.

ISSUE 11 REVISION 4 Site Type



2–15

Site Type

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Site Type



2–16

Site TypeThe main processing within the BSC and BTS is performed by modules called GenericProcessors (GPROCS). The GPROCs within a BSS have to be able to communicatewith one another for BSS control, signalling and software downloading.

If the BSC and BTS are in the same location then communication is via an I.EEE 802.5Local Area Network (LAN). If the BSC and BTS are in separate locations thencommunication must be via the LAPD signalling link on the 2.048 Mbit/s links.

The site type parameter also determines other site related features. If the site type is 1i.e. a standalone BSC, then timeslots on the TDM highway of that site will not beallocated to digital radio interface boards as they will only be found at a BSS or BTS.

A BSC fm_site_type 0 can be equipped with cells because it is co-located with a BTSbut with a BSC fm_site_type 1 this is not possible.

ISSUE 11 REVISION 4 Site Type



2–17

Site Type

� ��"��!�"��"# ��

� �� "��

�� !"��

�� !"��

��

ISSUE 11 REVISION 4Cabinet Configuration



2–18

Cabinet ConfigurationThe second device to be equipped in any BSC, RXCDR, BSS ot BTS database will bethe cabinet.

equip <site number> CAB

1st prompt (identifier):

This prompt specifies the unique identifier fo the cabinet.

2nd prompt (cabinet type)

An integer code or equivalent test string is used to specify the cabinet type beingequipped, this is necessary for the IAS to process and accurately report alarms.

In the case of entering 15 or “M_Cellcity”, 16 or “M_Cellarena” and 20 or“M_Cellarena_Macro the following prompt will appear:

Is an internal HDSL modem present: Yes/No

In the case of entering 15 or “M_Cellcity”, 16 or “M_Cellarena” the following prompt willappear:

Is an internal integrated antenna present: Yes/No

These two prompts are only relevent to the M-Cellcity product. In the case of remoteM-Cell cabinets (those having no MCU) integers 12 and 13 should be specifieddepending on cabinet type

3rd prompt (frequency type):

An integer code, or unique text string is used to specifiy the frequency ranges used withinthe specified cabinet.

ISSUE 11 REVISION 4 Cabinet Configuration



2–19

Cabinet Configuration

!(,$'��*$+!�&,%�!)��

� !&+!)�+#!��$ !&+$"$!)*��

� !&+!)�+#!��$&!+�+-'!��

0 – bts4d_48V1 – bts4d_27V2 – bssc_48V3 – bssc_27V4 – bts_dab5 – bssc_dab6 – excell_47 – excell_68 – topcell9 – bts_5

10 – m_cell_211 – m_cell_612 – tcu_213 – tcu_614 – m_cell_micro15 – m_cellcity16 – m_cellarena17 – horizonoffice18 – horizonmacro19 – horizonmacro_ext20 – M-Cellarena_macro

� !&+!)�+#!�")!(,!&�-�+-'!��

��

��

��

��

� ��

� ��

��

��

� ��

ISSUE 11 REVISION 4Cage Equipage



2–20

Cage EquipageEquipage of cages at a site is not as straightforward as that for cabinets and sites. Thereare five parameters that need to be entered when equipping a cage.

equip <sitenumber> CAGE

1st prompt (identifier)

Up to 16 cages can be equipped at any one site being numbered from 0–15. Valididentifiers for a BSC cage are 0–13, the first two BSC cages being number 0 and anotherID number respectively. If there is only one BSC cage it must be numbered 0 or 1.

Valid BTS identifiers for cages are 2–15. The first BTS at a site must be numbered either15 or 14, conventionally 15.

The cage ID allocated must be equal to the switch setting on the LANX board in thatcage.

2nd prompt (KSW pair)

Up to four pairs of KSWs (0–3) can be equipped at a site. This parameter identifieswhich pair manages that particular cage and therefore, which TDM highway the cage isbeing served by. This field must equal the first i.d. of the KSW equipage, the Highwaysupported by the KSW.

3rd/4th prompts (KSW Extension)

It is possible to extend a TDM highway driven by a particular KSW/TSW to a number ofextension cages. If redundancy has been implemented then each TDM highway hasassociated with it a pair of KSWs. The next two parameters identify which KSWX(R)(slot position) in the parent connects the cage to the source active and redundant KSW.These two parameters are optional and are only required if the cage being equipped is anextension (child) cage. A cage backplane diagram is at page 41 of section 1.2. The 0–4code being used signifies the A0–A4 or B0–B4 KSWX(R) slots being used in the parentshelf

5th prompt (cabinet)

This parameter defines the cabinet in which the cage belongs.

6th prompt (ias)

This is an optional parameter and is necessary to specify whether the cage has aconnection to the Internal Alarm System (IAS) equipment (PAB, DAB etc ...). In mostcases the answer will be “yes”, the exception to this being a BSSC cabinet where 2cages can be fitted, only one of which having the IAS connection.

Note:

This device is not explicitly equipped at M-Cell sites. It is automatically equipped whenthe first Base Transceiver Process (BTP) at a site is entered.

ISSUE 11 REVISION 4 Cage Equipage



2–21

Cage Equipage

��!+/%*�-%.!�(/'�!,��

� �(.!,�.$!�% !(.%"%!,�"),�.$!��#! ��

��

��

� �(.!,�.$!��*�%,�.$�.�'�(�#!-�.$!��#!��

� �(.!,�.$!��)((!�.%(#��#!�.)��"),��

� �(.!,�.$!��)((!�.%(#��#!�.)��"),��

� �(.!,�.$!��%(!.�.)�0$%�$�.$!��#!��!&)(#-��

� �-��(�� )((!�.! ��!-��)

ISSUE 11 REVISION 4Transcoder Location



2–22

Transcoder LocationThe transcoding function is to convert a 64 kbps TCH to a gross channel rate of 16 kbps.This is necessary to minimise the required amount of RF bandwidth when the traffic datais digitally modulated and transmitted across the air interface.

Transcoding as a function can theoretically take place either remotely (normally at theMSC), at the BSC or BTS. Currently Motorola only support the first two options.

After transcoding has taken place it is possible to subrate multiplex four 16 kbps trafficchannels into one 64 kbps timeslot thus quadrupling the traffic channel capacity of a2.048 Mbit/s resulting in increased efficiency.

The BSS database only has to include the location of the transcoding function.

ISSUE 11 REVISION 4 Transcoder Location



2–23

Transcoder Location

��$��"��"

�

�

�

�

�

�

�

��$��"��"

��

��#�#!��"� ��!�� #� ��

� ��!��"� ��!�� #��%

��!��"� �� %

ISSUE 11 REVISION 4BSC Types



2–24

BSC TypesGPROCS are software machines. Their functionality is dependant upon the size or typeof site. On small size sites all of the necessary software processes to support that sitecan run on one GPROC.

That GPROC becomes a certain processor type depending on whether it is at a BSC orBTS.

As the site increases in size the software processes necessary to support the sitebecome too large to reside on one GPROC so some of those processes are moved ontoanother GPROC creating other processor types. The site will then become anotherBSC/BTS type.

The smallest BSC type is a BSC Type 0. In a BSC type 0 all of the necessary softwareprocesses to support that BSC can run on one GPROC known as the Base StationProcessor (BSP). The actual software processes required is dependant on whetherMotorola defined A-bis or GSM A-bis is being used. The examples shown are Motoroladefined A-bis.

BSP – Base Station processorCLM – Connectionless managerSM – Switch ManagerMTP – Message Transfer PartSSM – Signalling Connection Control Part State MachineOMS – Operations and Maintenance System

A RXCDR (fm_site_type= 3) will always be a bsc_type 0.

ISSUE 11 REVISION 4 BSC Types



2–25

BSC Type 0 – Single GPROC

��

��

��

��

��

��

ISSUE 11 REVISION 4BSC Types



2–26

BSC TypesAs the loading on the BSC increases, more processing will be required to support thesignalling coming into and going out of the BSC. The software processes that supportthis is the Message Transfer Part (MTP) and the Signalling Connection Control PartState Machine (SSM). These two processes are removed from the BSP and placed ontoa new device type called a Link Control Function (LCF). This is now a BSC Type 1.

The largest type of BSC is a type 2. As the amount of signalling is increased this can becatered for by adding additional LCFs. The bottle neck will now probably be the BSP. Toreduce the load on the BSP the Operations and Maintenance System is placed on itsown processor type, the Operations and Maintenance Processor (OMP).

ISSUE 11 REVISION 4 BSC Types



2–27

BSC Type 1

��

�

��

��

�

��

��

��

��

��

�

��

��

� ��

��

�

��

ISSUE 11 REVISION 4BTS Types



2–28

BTS TypesThere are three types of BTS, types 0, 1 and 2. The smallest is a type 0 where all of thesoftware processes required to support the BTS are resident on one GPROC called theBase Transceiver Processor (BTP).

As the BTS grows the RF equipment will require the most processing so the relevantsoftware process, the Radio Subsystem (RSS), is moved from the BTP and placed on anew processor type, the Digital Radio Host Processor (DHP). This is a BTS type 1.

If the BTS is to grow further, a layer 3 process called the Radio Resource State Machineis moved onto a new processor type called the Radio Signalling Link Processor (RSLP)as that process can be allocated on an individual cell basis whereas the Cell ResourceManager (CRM) controls a number of cells and therefore remains on the main processor.A BTS type 2 presently does not exist in the Motorola BTS software.

This parameter is not necessary at an M-Cell site.

ISSUE 11 REVISION 4 BTS Types



2–29

BTS Types

��

��

�

�

��

��

��

��

��

�

�

RSS�

� �

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4BSC/ BTS Types



2–30

BSC/ BTS TypesIf the incorrect site type is entered in the database problems will arise during theinitialisation process. The site will be downloaded as normal, but on configuration,discrepancies will arise in the database.

If for example a BTS site was configured as a type 1 instead of 0 on configuration it willexpect to find GPROCs to become Digital Host Processors (DHP) which may notphysically be either there or equipped in the database. Therefore, configuration of thesite will not take place.

ISSUE 11 REVISION 4 BSC/ BTS Types



2–31

BSC/BTS types

� ��$��#��$& ��

� ��$��$#�$& ��

��$�"�!%�"��$��'��#�$��

� � ��$& ��

� ��$& ��

� ��$& ��

ISSUE 11 REVISION 4GPROC Slots



2–32

GPROC SlotsData, primarily traffic, will be coming into and going out of the BSS on the 2.048 Mbit/slinks. All downlink traffic data going into the transcoder function will be serial PCM at 64kbps and after the transcoding function will be at 16 kbps. On entering the BSSequipment it is converted from serial to parallel and routed within the equipment via theTDM highway.

The TDM highway is interfaced by all full sized boards with the exception of the GenericClocks. All boards are allocated timeslots during which to take the data off and forputting the data on. The Kiloport Switch (KSW) provides the timeslot interchangefunction.

The Generic Processor (GPROC) boards need to interface to the TDM highway fortransmitting information between the BSC and MSC (SS#7), all control and managementinformation from the OMC including software downloads (X.25) and all signalling betweenBSC GPROCs and BTS GPROCs (LAPD) must go over the 2.048 Mbit/s links. The onlyway that the GPROCs can interface to this signalling data is via the TDM highway. TheGPROC is able to support up to thirty two 64 kbps serial channels, however GPROC 1will only support 8 or 16, GPROC 2 will support16 and 32 timeslots.

ISSUE 11 REVISION 4 GPROC Slots



2–33

GPROC Slots

� ��

� ��

ISSUE 11 REVISION 4Site Synchronisation



2–34

Site SynchronisationFor site synchronisation each site will have two Generic Clock (GCLK) modules.

All terrestrial circuits interfacing to a site will do so on standard 2.048 Mbit/s PCM linksand the GCLK is able to derive its reference from these links or alternatively free run incase of reference failure.

The GCLK enables the site to synchronise to the 2.048 Mbit/s links so that frame andmultiframe alignment can be achieved.

Synchronisation loss thresholds can be set on both an hourly and daily basis so thatwhen these thresholds are reached an alarm message can be generated by theMSI/XCDR card to the FM.

Both of these periods are chronological, i.e. if an alarm condition has been reached in thefirst 10 minutes of an hour, that alarm is then locked out until the next chronological hourbegins.

The parameter sync_loss_oos provides an upper limit of sync loss alarms, uponreading this threshold the XCDR/MSI will notify the FM which in turn will take the MMSout of service. This threshold works on a daily basis.

If an MMS has been taken out of service as a result of the sync_loss_oos thresholdbeing reached, the FM will not put it back in service until the sync_loss_restore timehas expired. For this timer to activate no sync loss alarms must occur, a single syncalarm will reset it.

ISSUE 11 REVISION 4 Site Synchronisation



2–35

Sync Loss

� ��

�"�'#�"%�!��%*)

��"�'#�)�'�(��%"�

'��

� ��"�#�$)�(+$��"%((�� "+��%�� *")��

� ��"�#�$)�(+$��"%((��%*'"+��%�� *")��

� ��"�#�$)�(+$��"%((�%%(��%�� *")��

��*#��'�%��"�'#��%$� ) %$( ��$��)%��

� ��"�#�$)�(+$��"%((�'�()%'��%�� *")��

�� $)��'��#��&�' %�(� ��$��)%��

ISSUE 11 REVISION 4Remote Loss Alarms



2–36

Remote Loss AlarmsAs previously mentioned the MSI/XCDR can track sync alarms from its own transmit byreceipt of the remote flag from the distant end.

This flag allows the monitoring of restore sync losses in much the same way as the syncloss parameters on the previous page.

ISSUE 11 REVISION 4 Remote Loss Alarms



2–37

Remote Loss Alarms

� ��$�"�� $�� ##��&�� %�$��

� ��$�"�� $�� ##�� %"�&�� %�$��

� ��$�"�� $�� ##� #�� %�$��

��%��"� ��"�# ��$ ��

� ��$�"�� $�� ##�"�#$ "�� %�$��

��$��"��!�"� �#� ��$ ��

ISSUE 11 REVISION 4Site Synchronization



2–38

Site SynchronizationThe four parameters shown opposite are interrelated. The sync_time_oos fieldindicates the permitted time that the receive leg of the 2MB link can have a prolongedsynchronization alarm. When this time is exceeded the MSI/XCDR card will inform theFM. The FM will initiate the MMS into a state of unlocked/disabled.

The sync_time_restore field indicates the length of time that the receive leg of a 2MBlink must maintain synchronization before the MSI/XCDR card will inform the FM. TheFM will activate the MMS to a state of unlocked/enabled.

Immediately a synchronization alarm occurs on the receive leg of a 2MB the MSI/XCDRcard will set the remote alarm flag (timeslot 0) on the transmit leg. At the distant end, onreceipt of this alarm condition, the remote timer starts, if no clear indication is receivedbefore the remote_time_oos expires then the MSI/XCDR will inform the FaultManagement (FM). The FM will initiate a state of unlocked/disabled for the MMS. Theremote_time_restore field sets the time that a remote alarm flag must be in a clearcondition before the MSI/XCDR notifies the FM. The FM will activate the MMS to a stateof unlock/enabled.

ISSUE 11 REVISION 4 Site Synchronization



2–39

Site Synchronization

Rx

RxTx

Direction of Traffic

Direction of Traffic

Txremote_time_oosremote_time_retore

sync_time_oossync_time_restore

sync_time_oossync_time_restore

Remote flag

remote_time_oos

remote_time_restore

Remote flag

Rx

RxTx

Tx

� �� !��

� �� !��

� ��

� ��

��

��

ISSUE 11 REVISION 4Slip Loss Alarms



2–40

Slip Loss AlarmsThe MSI/XCDR contains an elastic 2 frame buffer to account for slip loss, if this lossexceeds the size of the buffer a TDM frame will be lost as the buffer resets, each timethe buffer resets, a slip loss alarm is generated. Each slip loss alarm is counted andsubject to similar thresholds mentioned.

ISSUE 11 REVISION 4 Slip Loss Alarms



2–41

Slip Loss Alarms

� �� %��$��"��!$$��'��!�� &�%��

� �� %�$��"��!$$��!&#�'��!�� &�%��

� �� %�$��"��!$$�!!$��!� ��&�%��

��&��#�!��$��"��!$$��#�$ �� %!��

� �� %�$��"��!$$�#�$%!#��!�� &�%��

�� %��#��"�#�!�$� �� %!��

ISSUE 11 REVISION 4BER Loss Alarms



2–42

BER Loss AlarmsBit Error Rates (BER) are constantly being checked by an MSI/XCDR card, the periodover which they are assessed for out of service purposes is controlled byber_oos_mon_period .

An alarm will be generated when the daily and hourly thresholds for BER are exceeded.

ISSUE 11 REVISION 4 BER Loss Alarms



2–43

BER Loss Alarms

� ��!�� #��

� ��!�� "��#��

�� !�

��

��!��

ISSUE 11 REVISION 4BER Monitoring Periods



2–44

BER Monitoring PeriodsThe MSI/XCDR card monitors the Bit error rate of the incoming 2MB, the BER can bedetermined using the fixed bits of the Frame Alignment Word and Frame Data Word.The fixed Bits do not alter and therefore are ideal to calculate BER.

The ber_oos_mon_period is the period that an in-service MMS must exceed the setBER rate before it is taken out of service. The BER rate is set in firmware at 10e–3.

The ber_restore_mon_period is the amount of time an out of service MMS mustexceed the set BER rate before it can be put back in service. The location for both ofthese periods can be set individually for each site but more usually is set to ‘all’ to includeevery site in the BSS.

ISSUE 11 REVISION 4 BER Monitoring Periods



2–45

BER Monitoring

��

��"��

� � � � � � � �

� ��

��

�� !�

��

��

��!�

� � � � � � � �

��"��

��

��

�#��

��

� ��

��/4)2/%4,0/%-�53%+)

.0(,*7$6%-5)-0'%4,0/�&)2$003$.0/$1)2,0( ��

��3)'0/(3

�)*%5-4��

.0(,*7$6%-5)-0'%4,0/�&)2$2)3402)$.0/$1)2,0(��

��,/4)+)2��.��1)2,0(3�

��

�)*%5-4��

ISSUE 11 REVISION 4N Bit



2–46

N BitIt is possible to set an extra remote alarm bit, the n bit. The bit which is used for thispurpose is bit 4 of the frame data word. The actual use of this bit is specified by thecustomer but the bit must be enabled using the modify_value command. Again this bitcan be enabled for all sites using the ‘all’ location index, although any in-service MMSswill not use it until they are reset.

ISSUE 11 REVISION 4 N Bit



2–47

N Bit

��

��

� � � � � � � �

��

��

��

#%�! *�)�"(��"%��'!%$�$�!'��

�� !&��"��

��$��"��

ISSUE 11 REVISION 4Integrated M-Cell HDSL interface



2–48

Integrated M-Cell HDSL interfaceThe implementation of this optional feature introduces a High bit-rate Digital SubscriberLine (HDSL) interface into the Motorola BSS product line. HDSL is a data transmissionmechanism which supports duplex high speed digital communication (at E1 rates) on oneor more unshielded twisted pair lines.

Configurations

The HDSL interface introduced is supported on 16 (one twisted pair/loop) and 32 (twotwisted pair/loops) 64kbit/s timeslots and can be configured in the following ways:

� By attaching external HDSL modems to the MSI of a BSC or collocated BSS site,where the site is connected to an integrated HDSL Network Interface Unit (NIU),as shown opposite.

� Between integrated HDSL NIUs at M-Cell sites, as shown fig 3.

Requirements

� An integrated HDSL NIU is able to contain up to a maximum of two HDSLmodems, one per span. An HDSL modem is required at both ends of the HDSLinterface, one end must be designated the master, the other the slave.

Functionality

� Implementation of this feature also provides the following new functionality tosupport an integrated HDSL interface:

� HDSL link management at an M-Cell site.

� HDSL alarms which report problems on, and monitor the quality of, the HDSLinterface (E1 alarms which currently exist are still supported as it is an E1 signalbeing passed over the HDSL interface). HDSL alarms, for both master and slave,are only reported by the HDSL modem which has been designated the master onthe HDSL link.

� An HDSL NIU enables HDSL and E1 links to be mixed on the same HDSL NIU.

Constraints

� The following constraints are applicable:

� An HDSL NIU is only valid in slot 0 of a card frame. If a card frame supports anHDSL NIU, an additional HDSL NIU cannot be equipped in slot 1.

� An HDSL link can be considered as a transport mechanism for the E1 link, thussupporting all E1 alarms and configuration parameters.

� The configuration of an HDSL interface using external HDSL modems is notsupported by this feature.

ISSUE 11 REVISION 4 Integrated M-Cell HDSL interface



2–49

External modem at a BSC connected to an integratedHDSL NIU

Fig1

��

��

ÏÏÏÏÏÏÏÏÏÏÏ

��

ÏÏÏÏÏÏÏÏÏ

�

ÏÏÏÏÏÏÏÏÏÏÏÏ

ÏÏÏÏ

ÏÏÏÏÏÏÏÏÏÏÏÏ�

ÏÏÏ��


��

��

ÏÏÏÏÏÏÏÏ

��

��

��

External modem at an M-Cell site connected to anintegrated HDSL NIU

Fig 2


ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ�

ÏÏÏÏÏÏ

��


��

��

ÏÏÏÏÏÏÏÏ

��

��

��

��

��


ÏÏÏÏ

��

ÏÏÏÏÏÏ

�

��

ISSUE 11 REVISION 4Physical interface



2–50

Physical interface

General

With the implementation of this feature, the following physical interface conditions andrestrictions apply:

� The HDSL interface is supported on a minimum of one or a maximum of twounshielded twisted pair carriers.

� The HDSL NIU can be unequipped and re-equipped to change the number of64kbit/s timeslots supported on a span.

� An HDSL interface supports a minimum of 16 64kbit/s timeslots, bearing in mindthat only 15 of these timeslots are available for use. Timeslot 0 is the E1synchronisation timeslot and is unavailable for traffic.

� An HDSL interface supports a maximum of 32 64kbit/s timeslots, bearing in mindthat only 31 of these timeslots are available for use. Timeslot 0 is the E1synchronisation timeslot and is unavailable for traffic.

� The M-Cellcity+ and M-Cellarena support a maximum of two HDSL interfaces on asingle HDSL NIU.

� MMS clock extraction is supported on HDSL links.

� Daisy Chaining between M-Cell BTSs with HDSL NIUs is supported by thisfeature.

� Daisy Chaining between an M-Cell BTS supporting HDSL NIUs and a BSC,collocated BSS, or M-Cell BTSs with remote modems is also supported by thisfeature.

Data

With the implementation of this feature, the following initialization and configuration dataconditions and restrictions apply:

� Initialization data required to configure the HDSL NIU interface at site initializationis stored in MCU flash memory. If a redundant MCU is present, the HDSL settingsstored on the master MCU will be used.

� The default status of the local HDSL NIU is set to:

� HDSL (master) on MMS0, HDSL (slave) on MMS1.

� At installation, the operator must set all external modems to be in the slaveconfiguration. The BSS software expects this configuration.

� Configuration data required by the HDSL NIU interface is provided by the M-CellBTS at the master end of the interface. Configuration data required by the externalHDSL modem is provided by the M-Cell BTS at the master end of the interface.

Note:

The slave configuration data is stored at the master modem.

ISSUE 11 REVISION 4 Physical interface



2–51

HDSL interface between integrated HDSL NIU’s

Fig 3

HDSL

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ

�

��


ÏÏÏÏ

�


ÏÏÏÏ

�

ÏÏÏÏÏÏ��

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ

��

��

ÏÏÏÏÏÏÏÏ��

��


��

��

�

ISSUE 11 REVISION 4HDSL Monitoring Period



2–52

HDSL Monitoring Periodhdsl_oos_mon_period sets the time monitoring period to ascertain on OOS condition.

hdsl_00s_restore_period sets the time monitoring period for expiry of an OOS condition.

ISSUE 11 REVISION 4 HDSL Monitoring Period



2–53

HDSL Monitoring Period

� ��%�$��#��"�� !��!��

��!��

� ��%�$��#��"�� !�� !"� ��

��!��

�� "�� !��"�� !��!�

��"��!"��!��!�

��#�"� �� !��!��

�� !�� !"� ��

ISSUE 11 REVISION 4HDSL SNR



2–54

HDSL SNRThese parameters set the alarm thresholds for signal to noise ratio on the HDSL link.Also, if the signal to noise ratio of the HDSL link goes below hdsl_snr_oos then the linkwill be taken out of service.

The link will only be brought into service if the signal to noise ratio is above thehdsl_snr_restore value.

For the hdsl_snr_hourly alarm, if the snr level drops below the hdsl_snr_hourlythreshold for an accumulated period of hdsl_snr_hourly_mon_period within a given 60minute period, an hourly alarm is generated.

For the hdsl_snr_daily alarm. If the snr drops below the hdsl_snr_daily threshold foran accumulated period of hdsl_snr_daily_mon_period within a given 24 hour period, adaily alarm is generated

ISSUE 11 REVISION 4 HDSL SNR



2–55

HDSL Signal to Noise Ratio

� ��$��#��#�"�� %"�'�� $� ��

� ��$��#��#�"��'�� $� ��

� ��$��#��#�"� #�� $� ��

� ��$��#��#�"�"�#$ "�� $� ��

�� $��"��"�!"�#��$��$�"�#� ��#��

��#$�!#

�"�� $ ��

��%�$�&��%�#� �� "��#��#�"�� %"�'

� �� "��#��#�"��'

�� "��#��#�"� #

� �� "��#��#�"�"�#$ "�

� ��$��#��#�"��'�� !�"� �� $� ��

� ��$��#��#�"�� %"�'�� !�"� �� $� ��

�� $��"��#�� #��

��%�$�&��%�#��#��

ISSUE 11 REVISION 4HDSL Loss of Sync Word



2–56

HDSL Loss of Sync Wordhdsl_losw_oos specifies the loss of sync word out of service threshold period.

hdsl_losw_restore specifies the loss of sync word restoral period.

These parameters may only be changed at an M-Cell site. If changed, all mastermodems at the local M-Cell are affected. All slave modem alarm thresholds are identicalto the master modem alarm thresholds.

ISSUE 11 REVISION 4 HDSL Loss of Sync Word



2–57

HDSL Loss of Sync Word

� ��!��

� ��!��

� ��

��

��

ISSUE 11 REVISION 4Site Configuration Exercises



2–58

Site Configuration Exercises

SiteConfigurationExercise 1

The following exercise will give the student the opportunity to practice the theorypresented in this section. The page opposite gives a diagramatic representation of atypical BSC site, only showing the equipment necessary to allow the student to build thisfirst part of the the database. Blank parameters are also available to populate therequired database fields.

The BSC site consists of one BSSC dab cabinet utilising both cages. There are multipleworking GPROC 2s at this site all having a maximum number of TDM highway slots.

If a prolonged synchronisation alarm of 10 seconds is suffered by any 2MB terminated atsite 0 then FM should remove the link from service. If synchronization is established formore than 5 seconds the 2MB should be restored to service. The remote values shouldbe consistent with the receive synchronization parameters.

If any 2MB at site 0 should lose sync more than 20 times in a 24 hour period the FMshould remove the link from service. If no synchronization alarms occur for a period of 5seconds then the 2MB should be restored to service. The alarms associated withsynchronization losses should be triggered at 5 alarms hourly and 15 alarms daily. Theremote values should be consistent with the receive synchronization loss parameters.

Only 20 slip loses should be allowed within any 24 hour period before FM removes theaffected 2MB from service. Before FM restores the 2MB to traffic there should be no sliplosses for at least 1 minute. Slip loss conditions should generate alarms when theyexceed the following period thresholds, 2 per hour and 15 per day.

Bit error rate alarms should be generated at 10e–4 on an hourly basis and 10e–6 on adaily basis.

The network uses the PGSM band.

ISSUE 11 REVISION 4 Site Configuration Exercises



2–59

Site Configuration Exercise Number 1

� ��

� ��

�%)�$��'��

�� !�"(��!�'�(��(*$�

�%)�$��

�%)�$��

�%)�$��

�� !�"(��'��(*$�

�� !�"(��$&#��' #('

�� !�"(�'*"��(�!��##'

�� !�"(�'*"��(�!��&�'(#&�

�� !�"(�&�!#(��(�!��##'

�� !�"(�&�!#(��(�!��&�'(#&�

�� !�"(�'*"�� #''�##'

�� !�"(�'*"�� #''�&�'(#&�

�� !�"(�'*"�� #''�� *

�� !�"(�'*"�� #''��#)& *

�� !�"(�&�!#(�� #''�##'

�� !�"(�&�!#(�� #''�&�'(#&�

�� !�"(�&�!#(�� #''�� *

�� !�"(�&�!#(�� #''��#)& *

�� !�"(�' �$� #''�##'

�� !�"(�' �$� #''�&�'(#&�

�� !�"(�' �$� #''�� *

�� !�"(�' �$� #''��#)& *

�� !�"(��&� #''�� *

�� !�"(��&� #''��#)& *

CABINET 0CAGE 1

CABINET 0CAGE 0

U1

KSWX

KSWX

KSWX

U25 U24

KSW

L27




2–60

SiteConfigurationExercise 2

Site 12 consists of a 12 carrier M-Cell6 site using the EGSM and 1800DCS RFequipment. The Radio Signalling Link for site 12 is processed by LCF number 2 at theBSC.

If a prolonged synchronisation alarm of 10 seconds is suffered by any 2MB terminated atsite 12 then FM should remove the link from service. If synchronization is established formore than 5 seconds the 2MB should be restored to service. The remote values shouldbe consistent with the receive synchronization parameters.

If any 2MB at site 12 should lose sync more than 20 times in a 24 hour period the FMshould remove the link from service. If no synchronization alarms occur for a period of 5seconds then the 2MB should be restored to service. The alarms associated withsynchronization losses should be triggered at 5 alarms hourly and 15 alarms daily. Theremote values should be consistent with the receive synchronization loss parameters.

Only 20 slip loses should be allowed within any 24 hour period before FM removes theaffected 2MB from service. Before FM restores the 2MB to traffic there should be no sliplosses for at least 1 minute. Slip loss conditions should generate alarms when theyexceed the following period thresholds, 2 per hour and 15 per day.

Bit error rate alarms should be generated at 10e–4 on an hourly basis and 10e–6 on adaily basis.

ISSUE 11 REVISION 4 Site Configuration Exercises



2–61

Site Configuration Exercise Number 2

� ��

� ��

�� %)�$��'��

�%)�$��

�%)�$��

�� !�"(��('�(*$�

�� !�"(�'*"��(�!��##'

�� !�"(�'*"��(�!��&�'(#&�

�� !�"(�&�!#(��(�!��##'

�� !�"(�&�!#(��(�!��&�'(#&�

�� !�"(�'*"�� #''�##'

�� !�"(�'*"�� #''�&�'(#&�

�� !�"(�'*"�� #''�� *

�� !�"(�'*"�� #''��#)& *

�� !�"(�&�!#(�� #''�##'

�� !�"(�&�!#(�� #''�&�'(#&�

�� !�"(�&�!#(�� #''�� *

�� !�"(�&�!#(�� #''��#)& *

�� !�"(�' �$� #''�##'

�� !�"(�' �$� #''�&�'(#&�

�� !�"(�' �$� #''�� *

�� !�"(�' �$� #''��#)& *

�� !�"(��&� #''�� *

�� !�"(��&� #''��#)& *




2–62



i

Chapter 3

Cells

ISSUE 11 REVISION 4



ii

ISSUE 11 REVISION 4



iii

Chapter 3Cells i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cells 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Identity 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location Area Codes 3–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Line 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defaults 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frequency Type 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Station Identity Code (BSIC) 3–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PLMN Allowed 3–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Transmit Power – Access 3–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Selection/Reselection – C1 3–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BCCH Reselection 3–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Reselection C2 3–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Temporary_offset 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Penalty_time 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cell_bar_qualify 3–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C2 Reselection Exercise 3–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Control Channel (CCCH) Configuration 3–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Control Channel (CCCH) Block Configuration 3–30. . . . . . . . . . . . . . . . . . . . . . . . . .

MS Paging 3–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Extended Paging 3–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Periodic Updates/rr_t3212 3–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Attach/Detach 3–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Access 3–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Emergency Call Access 3–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Requests 3–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Wait Indication 3–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signalling Establishment 3–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rr_t3101 3–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Allocation by Interference Band 3–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Threshold 3–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Allocation by Interference Band 3–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assignment of Resources 3–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Queue Management 3–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH Queuing 3–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Channel Reconfiguration 3–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preferred Number of SDCCH 3–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Allocation 3–62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Reconfiguration 3–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Measurement Reporting for Handovers and Power Control 3–66. . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



iv

BA – Indication 3–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BA Indicator 3–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signal Strength Measurements 3–70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Signal Quality Reporting – RXQUAL 3–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS Processing and Threshold Comparisons 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements Reported by MS on SACCH 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements Performed by RSS 3–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Threshold Comparison Process – Power Control 3–76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power Control 3–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS 3–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS 3–80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXQUAL 3–82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover – RXQUAL, RXLEV 3–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover – Interference 3–86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MS Power Control 3–88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS – Maximum Power 3–88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS Power Control 3–90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rapid MS Power Down 3–92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Optimized Power Control 3–96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Optimized Power Control Algorithms 3–98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discontinuous Transmission 3–100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Evaluation 3–102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers Allowed 3–104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SDCCH Access – handovers 3–106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers – Interference 3–108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Budget Handover 3–110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timing Advance – MS Maximum Range 3–112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover–MS Maximum Range 3–114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handovers 3–116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming Handovers 3–116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handovers 3–118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-Cell Handovers 3–118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TCH Resources Reporting 3–120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preferred Target Cell 3–122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Reporting 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Evaluating 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Rejection 3–124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Power Level 3–126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculated Handover Power Level 3–128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 3–128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Default Information 3–130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Initiation 3–132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rr_t3103 3–132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



v

Handover Channel Establishment 3–134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RSS Link Fail 3–136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Revival 3–138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loss of Radio Link 3–140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timers rr_t3109 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Failure 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Failure 3–142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timers rr_t3109, rr_ t3111 3–144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Channel Release 3–144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rf_chan_rel_ack 3–146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Re-establishment 3–148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CRM Timers 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dealloc_inact 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ho_ack 3–150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Exercise 3–152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Cell 3–152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add_cell Working Area 3–155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



vi

ISSUE 11 REVISION 4 Cells



3–1

Cells

Objectives


� Equip and understand the database fields associated with adding a cell.

ISSUE 11 REVISION 4Cells



3–2

CellsThe flexibility of the BSS equipment enables each BTS site to support up to six cells.One site could consist of a single In-Cell cabinet, ExCell or Top-Cell base Stationsupporting up to three cells. The M-Cell range of BTS equipment supports one cell withthe exception of M-Cell6 which can support upto three cells per cabinet.

Each cell within the site will be allocated its own Broadcast Control Channel (BCCH),Common Control Channel (CCCH) and Dedicated Control Channel (DCCH) and haveother database set parameters unique to that cell even though more than one cell canexist at the same site.

Cells are configured using the add_cell command (see Section 3.2). The chg_elementor chg_cell_element commands (see Section 3.3) are used to change the settings of anumber of parameters that are automatically assigned default values.

ISSUE 11 REVISION 4 Cells



3–3

Cells

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Cell Identity



3–4

Cell IdentityEach GSM system has to be distinguishable from other GSM systems by the MS. Thisis achieved by a series of codes that identify the country, network, area of the networkand finally the actual cell. This information is being transmitted by the BCCH of eachcell. When in the idle mode the MS selects the BCCH of the strongest cell and monitorsthe information.

Each GSM subscriber will have a Subscriber Identity Module (SIM) and on that card willbe the International Mobile Subscriber Identity number (IMSI). Part of that numbercorresponds to the country and network code of the system that the card is subscribedto. This information is used when the subscriber tries to gain access to both its own andother Public Land Mobile Networks (PLMN).

ISSUE 11 REVISION 4 Cell Identity



3–5

Cell Identification

��

��

� ��

� ��

� ��

��

��

��

��

��

ISSUE 11 REVISION 4Location Area Codes



3–6

Location Area CodesThe Mobile Country Code (MCC) is a three digit number that identifies the country towhich the system belongs. Two octets are dedicated to the MCC, octet A for the first twodigits, the first four bits of octet B for the third digit and the last four bits of Octet B areset to 1’s.

Some countries may have more than one GSM system so the MCC will be common toeach. To identify the particular system within the country that a GSM cell belongs toeach country has been allocated two Mobile Network Codes (MNC). If there are morethan two systems within a particular country then an MNC can be borrowed from anothercountry.

Mobiles have to periodically inform the system as to where they are within the system.These are called Location Updates. The system has to know the whereabouts of aparticular MS so that resources in a particular part of the system can page the MS toinform it of an incoming call. If the whereabouts of the MS was unknown then systemwide paging would have to take place which is inefficient.

Location updates may occur periodically after a set period of time and when a MS movesfrom one area to the system to another. The only way a MS can detect that it haschanged areas is by reading the Location Area Code (LAC) that is transmitted on theBCCH of each cell.

Two octets are allocated for the LAC giving it a range of 0 – 65535.

Octets F and G are to identify the cell in a particular location area. As two octets areallocated for this purpose then the Cell Identity (CI) range is 0–65535.

The MCC, MNC, LAC and CI together provide the cell global identification.

ISSUE 11 REVISION 4 Location Area Codes



3–7

Location Area Identity

� � � � � � � �

� � � � � � � �

� � � � � � � �

� � � � � � � �

� � � � � � � �

� � � � � � � �

� � � � � � � �

� � � � � � �

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Command Line



3–8

Command LineA cell is added to a site by using the add_cell command. It must be qualified with thecell global identification followed by the site number, and optionally a cell name.

Defaults

After the add_cell command is invoked a series of prompts will be presented where thedatabase parameters describing the cell are entered.

� If a database parameter has a default value this may be engaged by simplypressing return.

� If a database parameter has a default value and a value outside of the parametersvalid range is entered then the default value will be used.

� If the parameter does not have a default value and an out of range value isentered the add_cell command will terminate.

� If a parameter does not have a default, failure to enter a value in that field will alsoresult in the termination of the add_cell command.

ISSUE 11 REVISION 4 Command Line



3–9

Command Line

� ��

��

��

$��#��$

� ��

�� !"� ��

��

"#'� ��

��'&�*$ ��

�#'%�'� ��

�*�'��

��*&�'/ ��

�('!��('! ��

�,�%/ ��

�-.�#, ��

��'(' ��

��,"�*%�'�+ ��

�(*.�/ ��

�(*,-!�% ��

��,�* ��

�)�#' ��

�.��' ��

�.#,0�*%�'� ��

��

�'#,��#'!�(& ��

�(-,"�� *#��

ISSUE 11 REVISION 4Frequency Type



3–10

Frequency TypeThe parameter supports the multiband environment. It enables the operator to define thefrequency type on a per cell basis thereby determining the single frequency bandcapability of a cell in operation.

ISSUE 11 REVISION 4 Frequency Type



3–11

Frequency Type

� �!� �#&��

�� !� $��&�#&��#��"��

�!��!&��

�� !� $��&�#&��#��"��

�%#��

�� !� $��&�#&��#��"��

��

�� !� $��&�#&��#��"��

��

ISSUE 11 REVISION 4Base Station Identity Code (BSIC)



3–12

Base Station Identity Code (BSIC)Every cell has a BSIC that allow an MS to distinguish between different neighbouringcells. The BSIC is encoded on the SCH and is one octet in length. It consists of theNetwork Colour Code (NCC) and Base Station Colour Code (BCC).

The BSIC may be reused but it is important that neighbour cells do not share the sameBSIC and BCCH RF carrier.

ISSUE 11 REVISION 4 Base Station Identity Code (BSIC)



3–13

Base Station Identity Code (BSIC)

8

0

� ��

��

��

��

� � � � � � � �

��

��

��

0 1 2 3 4 5 6 7��

7

6

5

4

3

2

10

16

24

32

40

48

56

08

10

18

20

28

30

38

19

17

25

33

41

49

57

7F

17

1F

27

2F

37

3F

715

23

31

39

47

55

63

6E

16

1E

26

2E

36

3E

614

22

30

38

46

54

62

5D

15

1D

25

2D

35

3D

513

21

29

37

45

53

61

4C

14

1C

24

2C

34

3C

412

20

28

36

44

52

60

3B

13

1B

23

2B

33

3B

311

19

27

35

43

51

59

2A

12

1A

22

2A

32

3A

210

18

26

34

42

50

58

19

11

19

21

29

31

39

� ��

ISSUE 11 REVISION 4PLMN Allowed



3–14

PLMN AllowedWhen an MS is active on an SDCCH or TCH it will start its measurement reportingprocess. Before being allocated the SDCCH/TCH it will have been camped on a BCCHreceiving system information. This information would have contained a list of BCCHfrequencies that the MS was to monitor as part of its measurement reporting process.What the MS must do is measure the Rx level for each BCCH carrier, process it and thenforward the best six reports to the BSS where it can be used for handover purposes.

In a cellular system radio channels must be reused to support the total number ofsubscriber active on the system. Before the MS processes the Rx measurement takenon a particular BCCH frequency it must identify that the one it is measuring is the correctone and not an interferer. Each BCCH will be allocated a Base Station Identity Code(BSIC) the first part of which consists of the Network Colour Code. The MS must decodeBSIC periodically to prove that the BCCH is the correct one and not one from aneighbouring PLMN. The ncc_of_plmn_allowed defines the first part of the BSIC ofBCCHs on which measurement reporting can take place.

ISSUE 11 REVISION 4 PLMN Allowed



3–15

PLMN Allowed

��

�6453,$

�,0.$0'

�3$0&(

�3((&(

�&(.$0'

�(5+(3.$0'4

�$0��$3,01

�165+��)3,&$

��

�(.*,6/

�(0/$3-

�$.5$

�2$,0

�8,5;(3.$0'

!$5,&$0

��

�5$.:

�,(&+5(045(,0

�696/%163*

�8('(0

�63-(:

�

��

�:2364

�(3/$0:

�3(.$0'

�10$&1

�138$:

�1356*$.

"6*14.$7,$

�� 0&&#1)#2./0#$..18('��

��))+�

��

��

�

��

�

��

��

��

�

��

��

�

��

�

��

ISSUE 11 REVISION 4MS Transmit Power – Access



3–16

MS Transmit Power – AccessBecause of the nature of cellular systems the output power of MS and BSS should bekept as low as possible to minimise the effects of introducing interference into thesystem and maximising the battery life duration of the portable MS. Power control of theMS and BSS is a function of the BSS. Before the BSS can control the output power ofthe MS the MS must have accessed the cell so that the BSS has a reference signalstrength to use.

When accessing a cell on the RACH and before receiving the first power commandduring communication on a SDCCH or TCH the MS must use the power level defined byin the ms_txpwr_max_cch field in the database or the maximum transmit power of theMS as defined by its power class, whichever is the lower.

ISSUE 11 REVISION 4 MS Transmit Power – Access



3–17

MS Access Power Output

� ��

� ��

��

�

�

�

��

� ��

��

��

��

�

�

�

��

ISSUE 11 REVISION 4Cell Selection/Reselection – C1



3–18

Cell Selection/Reselection – C1The MS, when not in the process of making a call, will camp on the most suitable BCCHassuming the MS is switched on, contains a SIM card and is in the system coveragearea.

Whilst in this idle state the MS receives a list of neighbour cell frequencies broadcast onthe BCCH of the serving cell.

The MS will tune to each of these frequencies in turn, gain synchronisation and check thefollowing information towards a possible cell reselection.

1. Correct PLMN2. Cell bar3. Location area4. P1 & P2 (C1 parameters)

Assuming the first two of these criteria are met the major factor used by the MS for cellreselection is the perceived transmission quality between the MS and the potential cellknown as C1.

One of the major factors used by the MS for cell selection is the perceived transmissionquality between the MS and the potential cell known as C1. The criterion on which C1 iscalculated takes into account the RXLEV of the BCCH, the maximum output power ofMS and other cell specific parameters.

C1= (A – Max. (B, 0))

A= RXLEV Average – P1B= P2 – Max O/P Power of MSP1 and P2 are the cell specific parametersP1= rxlev_access_min which determines the min RXLEV required for the MS to accessthe system.P2= ms_txpwr_max_cch which determines the maximum output power at which the MScan access the system.

The MS will only select cells of positive C1 and when a choice between cells of the samelocation area has to be made the cell of best C1 is chosen.

In the formula ‘A’ determines the down downlink path, and ‘B’, the uplink. To reach apositive C1 value ‘A’ must be positive, this will indicate that the received downlink poweris greater than the minimum required for that cell. If the value for ‘B’ falls negative, thisindicates that the mobile is more than capable of meeting the required access power, inthis case a value of 0 is used instead. A positive value for ‘B’ indicates a poorer uplinkpath.

The following statement summarises this calculation:

‘A’= + value –> Good downlink path– value –> Poor downlink path

‘B’= – value –> Good uplink path+ value –> Poorer uplink path

ISSUE 11 REVISION 4 Cell Selection/Reselection – C1



3–19

Cell Selection/Reselection

�� 0��

�� 0&!.��.!+�#!�*�

�� *��0��)/!+�)"��

� *��+0&!.��!,,�'%(��

� ��

��

��

�

�

�

��

*�',�-0*/+�'�0��$��

� ")+��

�� '

�� '

�

�

�� '

")+��

�� '

�� '

�

�

�� '

ISSUE 11 REVISION 4BCCH Reselection



3–20

BCCH ReselectionWhen considering BCCH reselection from one cell to another with the same location areathe value of C1 for potential cell must be greater than that for the source cell. When thepotential cell is in another location area then the value of C1 must be greater than that ofthe source cell by a database set parameter, the cell_reselect_hysteresis field.

ISSUE 11 REVISION 4 BCCH Reselection



3–21

BCCH Reselection

� ��

� ��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Cell Reselection C2



3–22

Cell Reselection C2C2 is an option GSM feature which can only be used for cell reselection, it can beenabled or disabled on a cell basis. If C2 parameters are not being broadcast the C1process is used for reselection. The formula below shows that C2 is firmly based on theoriginal C1 calculation.

C2= C1 + cell_reselect_offset – temporary offset * H (penalty_time –T)

(for penalty_time <31)

H= 0 if T > penalty_time

H= 1 if T < penalty_time

C2= C1 – cell_reselect_offset

(for penalty_time= 31)

Whilst idle the mobile will maintain a list of the strongest 6 neighbours being monitoredfrom the idle ba list. This will be constantly updated and reselection parameters regularlychecked. At least every 5 seconds the ms will calculate C2 for the server and C2 forneighbours, if the C2 for the best neighbour exceeds that of the server for a period of 5seconds then reselection will take place. If the neighbour is in a different location areathen cell_reselect_hysteresis is also considered for the same period.

The parameters affecting C2 are broadcast on BCCH system information to an idlemobile and are described below:

cell_reselect_param_ind

This parameter is used by CRM to determine if C2 parameters should be broadcasted ornot. In any case, this field will be broadcasted and read by the MS as the PI bit. Aphase 2 MS will read the C2 parameters, if present, and use them for reselection. Aphase 1 MS is not capable of using C2 parameters, the C1 algorithm will be used forreselection.

cell_reselect_offset

An integer code specifies the cell_reselect_offset in dBs. This offset could be eitherpositive or negative depending on the value of penalty_time .

ISSUE 11 REVISION 4 Cell Reselection C2



3–23

Cell Reselection C2

��"�#��$� ��#�$�$��! "�"'� ��#�$��

�� "�!��$'�$��$��#��&��%��

��!��$'�$��

��≤�!��$'�$��

� ��"�#��$� ��#�$

�� "�!��$'�$��

� ��"�#��$�!�"��

�� !�"��$�"#��"��$ ��" ��#$��

��!�"��$�"#��"�� $�$ ��" ��#$��

� ��"�#��$� ��#�$��

� ��$��"�� "�� #�$

��

��

��

��

��

��

ISSUE 11 REVISION 4Cell Reselection C2



3–24

Temporary_offset

This negative temporary_offset is imposed only for the duration of the penalty time, andis then disregarded.

Penalty_time

Penalty_time is the duration for which the negative temporary_offset is considered,and is compared with Time T in the algorithm. Time T is the length of time the MS hasmaintained the neighbour in its top six measured cells. If penalty_time is set to 31 thetemporary_offset is ignored and the cell_reselect_offset becomes constantly negative.

cell_bar_qualify

cell_bar_qualify is used only in cell selection to prioritize a cell as being “normal” or“low” priority. The MS will always select cells with normal priority providing their C1calculation is greater than zero. Only if a “normal” priority cell cannot be found will a“low” priority cell (providing C1 > 0) be selected.

ISSUE 11 REVISION 4 Cell Reselection C2



3–25

Cell Reselection C2

��""�(�)�"��*�%��)�*�*�#&%(�(.�%��)�*��

��%(�&�$�"*.�*!#��*��)��,�"+��

��!��&�$�"*.�*!#�

��!��≤�&�$�"*.�*!#�

��""�(�)�"��*�%��)�*

��%(�&�$�"*.�*!#��

� *�#&%(�(.�%��)�*��

�� !$*� �(��%��%(��)�%��)�%��)�*

��

��

��

��

��

��

��

��!$�!$!*.

� &�$�"*.�*!#��

� !$*� �(��%��%(��)��&�(!%�)

��)��

�� )��

��

��

��

��)��

��#&%(�(.�%��)�*�! $%(��

��""�(�)�"��*�%��)�*�!)�$� �*!,�

� ��""��(�'+�"!�.��

��%(#�"

��%-

ISSUE 11 REVISION 4C2 Reselection Exercise



3–26

C2 Reselection ExerciseThe parameters and levels specified on the facing page are typical values experiencedby a mobile in the reselection process. Use these values to determine whether themobile will reselect to the neighbour cell. The mobile has been in the server well overone hour, and the best neighbour has been in the top six measured cells for exactly 4minutes.

��

��-&("!%��&+*��!()*�

�� (.#�,��))�$!%��

��

� �� $)�*.'-(�$�.��

� ��

��

��

��

�� (.#�,��))�$!%��

��

� �� $)�*.'-(�$�.��

� ��

��

��

��

��)�(,�(��%�!� �&+(��##�(�)�#��*� /)*�(�)!)

ISSUE 11 REVISION 4 C2 Reselection Exercise



3–27

C2 Reselection Example

� ��

��!� ��

17,'5"#%%'22"-+.��

-2"37061"-#7"%%*�

%',,"1'2','%3"0#1#-"+.&� �

%',,"1'2','%3"/((2'3� �

�'-0/1#18"/((2'3� �

�'.#,38"3+-'�

� ��

��!� ��

17,'5"#%%'22"-+.� ��

-2"37061"-#7"%%*� �

%',,"1'2','%3"0#1#-"+.&� �

%',,"1'2','%3"/((2'3� �

�'-0/1#18"/((2'3� �

�'.#,38"3+-'� ��

� �7,'5��5'1#)'

�'15+.)��&�-

�'23�.'+)*$/41��&�-

� %',,"1'2','%3"*823'1'2+2��

� �/$+,'�0/6'1�%,#22��6�� &�-�

ISSUE 11 REVISION 4Common Control Channel (CCCH) Configuration



3–28

Common Control Channel (CCCH) ConfigurationUp to four timeslots on the BCCH carrier can be used for the CCCH. Each timeslotforming a subchannel and each subchannel being divided into subgroups.

ccch_conf is a parameter which is broadcast on system information messages to an idlemobile it is one of three parameters used by the MS, to determine its paging group

The ccch_conf field determines the configuration of the CCCH on the BCCH carrier. Itmust be consistent with the sdcch_preferred value in order to correctly assign combinedor non-combined multiframes.

ISSUE 11 REVISION 4 Common Control Channel (CCCH) Configuration



3–29

Common Control Channel (CCCH) Configuration

� ��! ��

��! � ��$"�� "��!��

��

� ��#��"�!#��

� ��#��"�!#��

� ��#��"�!#"��

��#��"�!#"��

�#��"�!#"��

ISSUE 11 REVISION 4Common Control Channel (CCCH) Block Configuration



3–30

Common Control Channel (CCCH) Block ConfigurationOn the non combined BCCH/CCCH multiframe, there are nine CCCH blocks. In thedownlink direction these blocks must serve the paging and access granted functions andmust be configured accordingly.

On the combined multiframe structure the number of blocks available is reduced to threebecause it now supports four SDCCH/SACCH.

The bs_ag_blks_res field sets the number of blocks reserved for access grant per 51TDMA multiframe. Therefore the number of paging blocks available are reduced by thenumber of blocks reserved for access grant messages. The choice of value will bedetermined by the consideration of the ratio of MS originated to MS terminated calls.

This parameter is broadcast on BCCH system information messages to an idle MS and isused by the MS to determine its paging group.

ISSUE 11 REVISION 4 Common Control Channel (CCCH) Block Configuration



3–31

CCCH Block Configuration

� �-��$��('-�,"-��

� �.)�",�+#��(+ '-

��(+ '-�,"-",/"!�#+,� %� +*#��

��(+ '-�,"-",/"!�#+,� %� +*#��

�+)�&*"!��(+ '-��(+ '��(+ '-

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4MS Paging



3–32

MS PagingAn MS is required to receive and analyse the paging messages on its paging group.

If the paging message uses the TMSI number, then four pages can be packed into onepaging group, which takes four consecutive bursts in timeslot 0 to transmit. If IMSI isused the number of MSs that can be paged in one message is only two.

The field bs_pa_mfrms indicates the number of 51 frame multiframes betweentransmission of paging messages to MS of the same group.

Therefore, the total number of paging groups per control channel is the total number ofCCCH blocks per timeslot, minus the bs_ag_blks_res multiplied by the bs_pa_mfrmsfield. MS are normally required to monitor every nth block where n equals the number ofavailable blocks in total.

This parameter is broadcast on BCCH System Information messages and is one of thefields used by an idle mobile along with ccch_conf , bs_ag_blks_res and the IMSInumber of the MS, to determine its paging group (formula in GSM 5.02).

ISSUE 11 REVISION 4 MS Paging



3–33

Transmission of Paging Messages

� �(�&��#�'#(��

�� #*") �'�#�(

��#*") �'�#�(

�

�

�

��#*") �'�#�(

�+�#&"�

��%$��

�(��"!(�'�(� �

�(�&��#�'#(� �

�

�

�

�

�

�

��

��

��#�

��

��

��

��

��

��

��

�

��

��

��

��

��

��

�

�

��

��

��

�

�

�

�

�

�

��

��

�

��

��

��

��

��

��

��

��

�

ISSUE 11 REVISION 4Extended Paging



3–34

Extended PagingIf there are more than four pages for a particular subgroup then the fifth through eightpages can be packed into the next but one paging subgroup if extended paging ispermitted. The MS is informed by the “page mode” flag in the paging message thatextended paging has been dynamically activated. The MS will then switch on andinterrogate the next-but-one paging group ahead. Extended paging can be deactivatedby disabling this flag in the add_cell .

Any more than eight pages for a particular subgroup would not be broadcast until thereappearance of that paging subgroup.

ISSUE 11 REVISION 4 Extended Paging



3–35

MS Paging

� ��

��

��

TMSI

TMSI

TMSI

TMSI

BUFFER

3

2

SF

1

BCCH

SF SYS02_3_MS_Paging

ISSUE 11 REVISION 4Periodic Updates/rr_t3212



3–36

Periodic Updates/rr_t3212As well as performing location updates due to geographical boundaries it can beimplemented on time basis by setting rr_t3212 which governs the MS periodic locationupdate procedure. rr_t3212 starts when mobility management service or when mobilitymanagement signalling is terminated and stops when mobility management service orsignalling is initiated. A value of 0 decihours indicates an infinite timeout value.

ISSUE 11 REVISION 4 Periodic Updates/rr_t3212



3–37

Timers t3212

� ��

��

��

��

ISSUE 11 REVISION 4Attach/Detach



3–38

Attach/DetachA database field can be used to invoke system attach/detach procedures. These areused to inform the PLMN that the MS has become active on the system or has beendeactivated either due to it being turned off or because the SIM card has been removed.

If an MS is either switched off or the SIM card is removed, assuming that theattach_detach field is set to 1, then the MS will invoke detach procedure and send anIMSI detach indication message to the PLMN. The PLMN will then be aware that the MSis inactive and will not allocate resources to that MS for paging purposes.

On insertion of the SIM and/or switching the MS on it will camp onto a BCCH and readthe System Information messages. Assuming the attach/detach procedures are requiredand the Location Area Identification (LAI) being sent on the BCCH is the same as thatstored in the MS as being its last LAI then the MS will generate an location update typeIMSI attach indication message.

If the LAI being received by the MS is different to that stored in its memory as being thelast known LAI then the MS will perform a location update.

ISSUE 11 REVISION 4 Attach/Detach



3–39

Attach/Detach

�� 11 "&�#$1 "&��

� � #'0 !*$#

��$, !*$#

��

��

� ��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

�-!'*$

*$ 3$0

�$14-/)

�-!'*$�/$(-',0

,$14-/)�',�1&$

0 +$�*-" 1'-,

/$

�-!'*$�/$(-',0

,$14-/)�',� �

#'%%$/$,1�

*-" 1'-,� /$

01-/$#��

��

01-/$#��

��

01-/$#��

��

�-" 1'-,�2.# 1$��

�11 "&��5.$

ISSUE 11 REVISION 4Cell Access



3–40

Cell AccessCell bar information is transmitted within system information messages to an idle MS.The network operator, via MMI, is able to completely bar access to all normal subscribersin a particular cell, using the cell_bar_access_switch field. Barring may beimplemented when a BTS is not functioning correctly, when new cells have beenintroduced into the network and being tested or when a cell is being reserved forhandover purposes only. When the cell is barred by the operator and system info reflectsthis, normal MSs will not attempt to access the cell. Users of test phones may employ a‘mask’ to override the MS’s usual action upon detecting the bar. These test MSs will beable to make calls, which will not be rejected by the BSS. Pages will still be transmittedin cells which are barred and therefore test MS will be able to receive calls. However,existing calls may be handed over to a cell which is barred, when the MS completes thecall in this barred cell, then re-selection will be attempted.

Cell barring is an all or nothing situation. By using the cell_bar_access_class fieldaccess to a cell can be limited to particular classes of MS. All SIMs are allocated one often access classes, referred to as access classes 0–9. There are five additional classes11–15 which are normally reserved for emergency services, VIPs etc. Class 10, in termsof a subscriber class does not exist, and indeed no subscriber will have it allocated. Thecell_bar_access_class field does not stop any MS from camping on a cell but willrestrict access to those classes indicated on the BCCH and could be used to cope withabnormally high traffic load or emergency situations. In the case of class 10 it isunimportant which value 0 or 1 it is assigned in this bit map as this value is overwritten bythe “emergency_class_switch ” also broadcasted to the MS.

When a cell is barred from access normal MSs will not be able to select this cell even if ithas the best signal. The MS will select the second best cell.

ISSUE 11 REVISION 4 Cell Access



3–41

Cell Access

� ��!��

� ��

��

� ��

� ��"��

��

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

��

��

�

��

��

�

�

��

�

�

�

��

�

��

�"��

��

��

��

� � � �

�"��

��

ISSUE 11 REVISION 4Emergency Call Access



3–42

Emergency Call AccessThe cell_bar_access_class field in the database is mapped onto the cells BCCHsystem information and informs all MS camped onto that cell which classes of MS arepermitted to access it. Part of the BCCH system information messages contains theemergency_class_switch field informing the MS that either all MS are permitted tomake emergency call or only those belonging to MS classes 11–15.

ISSUE 11 REVISION 4 Emergency Call Access



3–43

Emergency Call Access

� ��

� ��

��

��

��

ISSUE 11 REVISION 4Channel Requests



3–44

Channel RequestsAn MS requests resources from a cell by transmitting an “access burst” containing the“channel request” message. The access burst has to be scheduled so that it istransmitted during a frame that has been configured as a RACH. This scheduling isperformed with the aid of a calculated wait period.

After the first channel request has been sent without reply, the next one is sent after await period, made up of a random number of RACH slots. This wait period is in the set(S, S+1 . . . S+T –1), where T is a value dependent on tx_integer (broadcast on BCCHsystem information) and S is a preset number dependent on the value of T andmultiframe type. The table opposite shows these values which are in the firmware of theMS.

Channel requests will only be repeated upto M+1 times where M is equal to max_retran ,broadcast on BCCH system information. After the last channel request T3126 is startedin the MS, on expiry the channel request procedure will be aborted.

ISSUE 11 REVISION 4 Channel Requests



3–45

Channel Requests

:(/7�4,5/3+

!(2+31�9(08,�/2

",7��"��"��"�#��

�" �#"��!� $�"#

��!� $�"#

��!� $�"#

��!� $�"#

��!� $�"#

�,:�:(/7�4,5/3+

#��

��!#

� 7;'/27,.,5��

9(0/+�5(2.,��73�

� �

�

� �

� �

��!��"��#"�

��<��

��

��

��

��

��

��

��

��

%��$��"

�

��

#

� 1(;'5,75(2��

9(0/+�5(2.,��73��

��& �!,75(2

�!,75(2

��!,75(2

� ��!,75(2

�,-(807��

��/27,.,5�*3+,�-35�281),5

��3-�5,75(261/66/326

ISSUE 11 REVISION 4Wait Indication



3–46

Wait IndicationWhen a MS gains access to a cell with an access burst it is requesting radio resources toperform one of the following functions:

1. Responding to a paging message.

2. Emergency call.

3. User request (making a call, location update, etc.)

4. Trying to salvage an established call.

If there is not radio resources available the network may send the MS an “ImmediateAssignment Reject message” in unacknowledged mode on the Common ControlChannel. The message will contain the request reference and a wait indication. Onreceipt of the “Immediate Assignment Reject” message the MS will start an internal timer(T3122) with the indicated value taken from the “wait indication information element”contained within the “Immediate Assignment Reject” message and returns to idle mode.The MS is not permitted to make a new attempt to establish a radio resource connectionin the same cell until T3122 expires.

The wait_indication_parameters is set in the BSS database and is the value that theMS will use to set T3122.

ISSUE 11 REVISION 4 Wait Indication



3–47

Wait Indication

��##�!��&*�()

� ��

��

�""��)�� ((��#"�#)�� )

��)��#��)�$#��(

��

��##�!��&*�()

� ��

��

��

�� +��)��#��)�$#�%�'�"�)�'(��

��"��#�(��$#�(��

��

��

��

��)(�)�"�'��$'��(

�#��'�)*'#(�)$��!��"$��

��,%�'�(

ISSUE 11 REVISION 4Signalling Establishment



3–48

Signalling Establishment

rr_t3101

An MS will request radio resources by sending a channel request message on theRACH. The PLMN will inform the MS via the AGCH as to what resources have beenallocated and will start timer rr_t3101.

Once the main signalling link between MS and PLMN is established rr_t3101 will bestopped. If rr_t310 1 expires before the signalling link is established the newly allocatedresources will be released and the channel request message forgotten.

rr_t3101 must be set to value higher than the time necessary to set up the signalling linkbetween MS and PLMN.

ISSUE 11 REVISION 4 Signalling Establishment



3–49

Signalling Establishment

��

��

��

,,�.��

��

��

,,�.��

��

��

� !&%�#(#)#*.�,,�.��

� �')#�'*�)'(('-#!+*"-

� ('"�, *%#��.+��

�#$ /(.�0 (/#��

ISSUE 11 REVISION 4Channel Allocation by Interference Band



3–50

Channel Allocation by Interference BandThe Cell Resource Manager (CRM) is the BSS radio channel database and isresponsible for allocating a radio channel of the right type when requested.

The CRM will search and allocate channels on a best channel available to worst channelavailable basis.

All idle radio channels are monitored for noise interference by the Handover Detectionand Power Control (HDPC) process in the Radio Subsystem Software (RSS). Thismonitoring leads to a number of samples which are in turn averaged by the HDPC. Afteraveraging, each idle channel will be allocated an interfere band, the HDPC then informsthe CRM of which band each idle channel falls into. The CRM uses this to ensure thatthe best radio channel available is allocated first.

The five interference bands are based on absolute noise level values of each carrier atfive different Rx levels, interference band 0 being the lowest Rx level (therefore the betterchannel) and interference band 4 being the highest Rx level and therefore the worstchannel.

The CRM will automatically allocate channels on a best to worst basis, this parameterdoes not actually control this feature. This parameter is not supported.

ISSUE 11 REVISION 4 Channel Allocation by Interference Band



3–51

Channel Allocation by Interference Band

� ��

��

�

�

�

��

� ��

��

�

�

�

��

ISSUE 11 REVISION 4Channel Allocation by Interference Band



3–52

Threshold

When attempting to allocate a radio channel the CRM must assign an SCCP number tothe request. Although part of this number is similar for each channel at a BTS, there isalso a unique part which is allocated by the CRM on a random basis. The thresholdparameter determines the maximum number of attempts the CRM will make to allocatethis unique part. If this number of attempts is exceeded then the call request will bedropped and a Software Fault Management (SWFM) will be generated.

ISSUE 11 REVISION 4 Channel Allocation by Interference Band



3–53

Channel Allocation by Interference Band

� ��

��

��

INFORMATION ELEMENT IDENTIFIER

CELL IDENTITY

EMBIT

MTL NUMBER RSL NUMBERMSB

RSL NUMBERLSB

RANDOM NUMBERS

SYS02_3_Info_Element

ISSUE 11 REVISION 4Assignment of Resources



3–54

Assignment of ResourcesWhen an MS requires the network to set up a call, the initial request for resources is sentas an access burst on the RACH. Acknowledgement of the request will be sent via theAGCH and the MS will then be allocated an SDCCH. Whilst on the SDCCHauthentication and validation of the subscriber and the setting of encryption normallytakes place.

If all SDCCHs are busy and SDCCH reconfiguration has reached a maximum, or is notenabled then the operator is left with two choices. Either the initial request for resourcesfrom the MS is rejected or it can be immediately assigned a TCH to carry out the SDCCHprocess. In the case that resources are immediately assigned, a TCH in the GSM900band will be allocated, EGSM frequencies will not be used. The immediate assignmentoption is indicated in the immediate_assign_mode field in add_cell .

ISSUE 11 REVISION 4 Assignment of Resources



3–55

Assignment of Resources

� ��"��!!��#�"��

�� "��$��

��#�!"

�� "��$��#!��

ISSUE 11 REVISION 4Queue Management



3–56

Queue ManagementA MS requests radio resources via the Random Access Channel (RACH). It does so bysending an access burst containing a “channel request” message. Assuming resourcesare available the MS will be assigned one of a number of Standalone Dedicated ControlChannels (SDCCH) where the remainder of call set up procedures will take place prior tobeing allocated a Traffic Channel (TCH).

It may occur that once the MS has finished on the SDCCH there may not be a TCHavailable at that particular moment. The system is able to place the MS in a queuealong with other MS awaiting assignment of a TCH.

The length of the queue is dependent upon the value set in thequeue_management_information field of the BSS database. The range of this fieldrepresents the arithmetic sum of the number of MS that can wait in a queue for theassignment of a TCH or SDCCH. A value of 0 must be entered if queuing is notpermitted. A MS could obviously not wait for an indefinite time in this queue,bss_map_t11 controls the maximum time the MS will wait before the request is dropped.

This parameter is used by the Cell Resource Manager (CRM), and must be aligned tothe value entered in the MSC.

This parameter must be greater that or equal to the sum ofmax_q_length_full_rate_channel and max_q_length_sdcch .

SDCCH Queuing

Channel requests cannot be queued, either an SDCCH is available or not. However,MSC originating, SDCCH handover requests can be queued, this parameter controls thelength of that queue. This parameter is more usually set to 0 as MSC SDCCH handoverrequests are not common.

ISSUE 11 REVISION 4 Queue Management



3–57

TCH Queueing

� �#�#��"�� "��

� ��#�#��"�� ""��

�� #�� ""��"��#�#�

��#�"��

Half Rate/Full Rate TCH Queue

� ��$��"��#�� "��

� ��#�#��"�� ""��

�� #�� ""��"��#�#�

��#�"��

SDCCH Queuing

� ��$��"��!��

� ��

ISSUE 11 REVISION 4Channel Reconfiguration



3–58

Channel ReconfigurationOn initialisation the CRM ensures that each air interface timeslot is configured as perfields set in the database.

Once the BSS is call processing the CRM is capable of dynamic channel reconfiguration.That is, the CRM is capable of changing the mix of channel configuration. If a highproportion of SDCCHs are in use and more SDCCH requests are received the CRM isable to reconfigure a TCH timeslot into SDCCHs.

In the example shown timeslot 0 of carrier 0 is configured to include FCCH, SCH, BCCH,CCCH, 4 SDCCH with 4 SACCH. Another timeslot on that carrier is configured as a fullrate TCH with FACCH and SACCH. The CRM is able to reconfigure the TCH timeslotinto 8 SDCCH + 8 SACCH giving this particular cell 12 SDCCH at the expense of oneTCH timeslot.

The channel_reconfiguration_switch field in the BSS database specifies whether theCRM may or may not perform dynamic channel reconfiguration.

ISSUE 11 REVISION 4 Channel Reconfiguration



3–59

Channel Reconfiguration

� � � � � �

�� )�%��'&��&#+#�$#*�+#'&

�#%�*$'+��

�#%�*$'+��

� � � � � �

�� )�%�� +�)�)��'& #!,)�+#'&

�#%�*$'+��

�#%�*$'+��

�� "�&&�$�)��'& #!,)�+#'&�*-#+�"��

� �� '& #!,)�+#'&�&'+�(�)%#++��

�� '& #!,)�+#'&�(�)%#++��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4Preferred Number of SDCCH



3–60

Preferred Number of SDCCHOn initialisation the CRM is informed of the number_sdcchs_preferred field in thedatabase which will control the number of SDCCHs that will be configured in a particularcell. The number of SDCCHs is dependent upon the configuration of timeslot 0 on theBCCH carrier, whether it supports 4 SDCCHs or whether all SDCCHs are on their owntimeslot at 8 SDCCHs per timeslot.

ISSUE 11 REVISION 4 Preferred Number of SDCCH



3–61

Preferred Number of SDCCH’s

� �%��"�#��#�!"��""��

� �%��"� ��#

� ��%�$��"��

� �&� ��%�$��"��

ISSUE 11 REVISION 4SDCCH Allocation



3–62

SDCCH AllocationThe number_sdcchs_preferred field (as discussed previously) also sets the minimumnumber of SDCCHs that the reconfiguration algorithm tries to maintain. When channelreconfiguration is enabled (channel_reconfiguration_switch=1 ) the CRM will attemptto maintain the preferred number of SDCCHs for allocation and may reconfigure idleTCHs to SDCCHs before all SDCCHs are busy and, when the demand falls, reconfigurethe SDCCHs back to TCHs. The number of available SDCCHs after reconfiguration willnever exceed max_number_of_sdcchs.

ISSUE 11 REVISION 4 SDCCH Allocation



3–63

Maximum Number of SDCCH’s

� ��$��#�� !��!��

� �#�� !

��#�"��

��%��#�"��

ISSUE 11 REVISION 4SDCCH Reconfiguration



3–64

SDCCH ReconfigurationThe “sdcch_need_high_water_mark ” and “sdcch_need_low_water_mark ” are usedby the reconfiguration algorithm to trigger the reconfiguration process. The highwatermark determines the number of free SDCCHs remaining before TCH to SDCCHreconfiguration should occur. tch_full_need_low_water_mark also has an effect onsuch a reconfiguration to ensure that some idle traffic channels will still be left after theconversion. The SDCCH low watermark determines the number of free SDCCHs beforethe SDCCHs obtained by previous reconfiguration can be converted back to TCHs. Thedynamic reconfiguration algorithm is shown below.

The low and high watermarks are only in effect if the channel_reconfiguration_switchis enabled.

Conditions for TCH to SDCCH Reconfiguration to occur

1. Number of SDCCHs after reconfiguration must not exceed max_number_ofsdcch .

2. Idle number of free SDCCHs must be lower than sdcch_need_high_water_mark .

3. Current number of idle TCHs must be greater thantch_full_need_low_water_mark.

Conditions for SDCCH to TCH Reconfiguration to occur

1. Total number of SDCCHs after the reconfiguration must not be lower thannumber_sdcch_preferred .

2. Present number of free SDCCHs must be greater than thesdcch_need_low_water_mark .

A dependency written into this feature is:–

1. sdch_need_low_water_mark � number_sdcch_preferred

ISSUE 11 REVISION 4 SDCCH Reconfiguration



3–65

SDCCH Reconfiguration

��

��

� � � � � � � ��

�-�#%��%��*

��

��

��

��

��

� *��"�'��"#!"�.�+�)�&�)$�� ,%+��

� *��"�'��%(.�.�+�)�&�)$�� ,%+��

� �,&��)�( �*��"*� )��

� � � � � � � ��

��*�#'�,*�

�� ()�

)��(' #!,)�+#('

�� ()�

)��(' #!,)�+#('

ISSUE 11 REVISION 4Measurement Reporting for Handovers and Power Control



3–66

Measurement Reporting for Handovers and Power ControlEach cell in the PLMN will have its own dedicated BCCH. The BCCH will becontinuously transmitted at a constant power output and any idle timeslots on the BCCHcarrier will be filled with dummy bursts.

The MS is provided with a list of neighbour BCCH carriers to which it must retune forsignal strength measurement reporting.

Cellular systems depend upon the reusing of RF channels available to support themaximum number of subscribers with the frequency band allocated. It is therefore veryimportant that the MS has some mean of determining that the BCCH carrier it ismeasuring actually belongs to the cell intended and not another cell using the samecarrier frequency. The BCCH multiframe contains the SCH in which is contained theBSIC. The MS therefore not only has to measure the received signal strength of BCCHcarriers but must also demodulate the SCH on the BCCH carriers and decode the BSICas often as possible and as a minimum at least once every 10 seconds.

If during the measurement process the MS detects BCCH carriers among the sixstrongest, whose BCCHs are not currently being assessed but are on the neighbour listthe MS will then as a matter of priority attempt to decode their BSICs. If after a period of5 seconds it has not managed to decode the BSICs it will revert to confirming existingBSICs.

If the BSIC of a surrounding cell cannot be demodulated or indicates that the cell is partof another PLMN then all signal strength measurements for that BCCH will be discarded.If decoding of a BSIC is not achieved after three successive attempts it will beconsidered lost and any existing signal signal strength measurement will be discarded.

The MS maintain a list of the six strongest BCCH carriers. If one of those BCCH carriersis found to be no longer one of the six strongest the information collected on that BCCHwill be retained for at least 10 seconds. This is in case a handover is initiated to that cellsoon after reporting procedures on that cell have stopped but requiring timing and BSICinformation gathered on it.

ISSUE 11 REVISION 4 Measurement Reporting for Handovers and Power Control



3–67

Measurement Reporting

� ��

� ��

� ��

� ��

� ��

ISSUE 11 REVISION 4BA – Indication



3–68

BA – Indication

BA Indicator

A neighbour list (BA List) is included in system information message type 2 to an idle MSand system information type 5 to a MS in traffic. Each of these lists is qualified by aba_indication bit. This is important in the case of a MS in traffic as the BA list isconveyed in sys info 5 by use of a bit map. When the MS sends a measurement reportthe frequency of the neighbour being reported is conveyed by its position in the bit mapof the last received system information 5 message. If a neighbour is added or indeeddeleted, the bit map in system 5 would be altered, and therefore the reported neighbourmeasurements need to be qualified as using the old or the new list (bit map).

This qualification is specified by use of the ba_indication which will automatically togglebetween 0 and 1 to indicate a different list. This ba_indication is returned in the uplinkmeasurement report to validate which list was being used at the time of measurement.

There are two distinct ba_ind elements, ba_ind_sacch (system information 5, MS intraffic) and ba_ind_bcch (system information 2, MS idle). Neither of these indicatorscan be set by the operator. The ba_ind_sacch will toggle automatically if a neighbour isadded or deleted, although the ba_ind_bcch remains fixed.

The ba_alloc_proc field provides an alternate method of handling the processing ofNeighbour measurements reported by the MS, when there is a change made to theneighbour list. Once the list has been changed the alternate method will cause theHDPC to ignore any subsequent reports having the old ba_ind_sacch value. All storedaverages based on previously received neighbour measurement reports are alsodiscarded. The HDPC shall resume processing of measurements only when the MSbegins to use the new ba_ind_sacch value. When a 0 is entered in this field thisreinitialization is disabled, the HDPC will process remaining measurement reports despitethe ba_ind_sacch not yet having toggled, it will also retain previous reports as normal.

ISSUE 11 REVISION 4 BA – Indication



3–69

BA Indication

� ��

� ��

��

SYS02_3_Neighbour_Cells

Neighbour Cells Description IEI octet 1

octet 2

octet 3

octet 17

8 1234567

Bit127

Bit113

Bit114

Bit115

Bit116

Bit117

Bit118

Bit119

Bit001

Bit002

Bit003

Bit004

Bit005

Bit006

Bit007

Bit008

Bit120

Bit128

Bit121

Bit122

Bit123

Bit124

BA–IND

EXT–IND

ISSUE 11 REVISION 4Signal Strength Measurements



3–70

Signal Strength MeasurementsRadio link measurements are used in the handover and RF power control processes. AnRSS directed handover is defined as a change of channel either because of degradationof quality of the current serving cell (BER and SSI) the availability of another channel thatwill provide the same or better quality radio link using a lower transmit power output(power budget) or to prevent an MS from exceeding the cells boundaries.

Both MS and RSS are reporting the signal strength at their receiver input. The MS ismeasuring the signal strength in the channel downlink direction and that of neighbourBCCH. The RSS is measuring the signal strength in the channel uplink direction.

The reported parameters are averaged out by the RSS and MS using measurementsamples taken during 480mS blocks. During the averaging process, samples takenduring a previous 480mS block are discarded, but the averages are retained by the RSS.

When assigned a TCH, SDCCH or camped on a BCCH the MS shall measure the signalstrength of:

1. The BCCH carriers as indicated in the BCCH Allocation (BA).

2. On all bursts of the TCH or SDCCH channel it is on including SACCH bursts. Iffrequency hopping is supported using the BCCH carrier then measurement of thatcarrier is dependent upon the PWRC field.

The RSS shall measure the signal strength of:

1. Any TCH or SDCCH that has been assigned to an MS including the SACCH.

The RXLEV value will be within the range of 0–63 depending on the signal strengthmeasurements

ISSUE 11 REVISION 4 Signal Strength Measurements



3–71

Signal Strength Measurements

��

� �$'%&!+/,

��

� ��

�� *%$

�� ,$ .$,�.& *��#�)

�� #�)

�

�

�

�� .+��#�)

�� .+��#�)

�� $--�.& *��#�)

��

�$'%&!+/,��

��

��

��

��

��

��

� ��

�$'%&!+/,�"$((

�$'%&!+/,�"$((

�$,0'*%�"$((

ISSUE 11 REVISION 4Signal Quality Reporting – RXQUAL



3–72

Signal Quality Reporting – RXQUALThe RSS measures the quality of the TCH/SDCCH in the uplink direction and the MS inthe downlink direction.

The RXQUAL values are produced during 480mS blocks and as with the signal strengthmeasurements, those measurements taken during previous 480mS blocks are discarded.

Eight levels of RXQUAL are defined.

ISSUE 11 REVISION 4 Signal Quality Reporting – RXQUAL



3–73

Quality Measurements

��

� �,2+)'+(��

�!#',��1"�3/0$*��

� �-)'+(��

� ��!+%$

�� $//�0&!+��

��

� ��

� ��

��

��

� ��

�� .$!0$.�0&!+��

��

ISSUE 11 REVISION 4BSS Processing and Threshold Comparisons



3–74

BSS Processing and Threshold ComparisonsFor the purpose of handovers and power control the BSS will be continuously processingthe following information.

MeasurementsReported by MSon SACCH

1. Downlink receive signal strength (RXLEV)

2. Downlink quality (RXQUAL)

3. Downlink surrounding cell RXLEV (neighbour BCCH)

MeasurementsPerformed byRSS

1. Uplink RXLEV

2. Uplink RXQUAL

3. MS–BS Distance (Timing Advance)

4. Interference levels in idle timeslots

The RSS will produce a new processed value for each of the measurements shownabove every 480mS (SACCH multiframe)

ISSUE 11 REVISION 4 BSS Processing and Threshold Comparisons



3–75

BSS Processing and Threshold Comparisons

��! "$��(��

� � '��&��$"��$�

� � '�� %��$(

� � '��%"" %��

��"� "��(��

� �!��&��$"��$�

� �!�� %��$(

� ��#$��

� �$�"��"��&��#��$��#� $#

� �" ��##��%��&�"(��

ISSUE 11 REVISION 4Threshold Comparison Process – Power Control



3–76

Threshold Comparison Process – Power ControlThe MS and BSS are continuously providing Received Signal Strength Indications (RSSI)on the radio resource allocated. The MS is measuring the RSSI in the downlink directionwhich is proportional to the BSS transmit output power and the BSS is measuring theRSSI in the uplink direction being proportional to the MS transmit output power.

These measurements are averaged by the RSS and this value is then used for powercontrol purposes. Thresholds are set in the database and if a number of averagedvalues produced by the BSS exceed these thresholds then the power output of the BSSor MS will be increased or decreased.

The number of averaged values to be considered in the decision process can be set indatabase.

ISSUE 11 REVISION 4 Threshold Comparison Process – Power Control



3–77

MS/BSS Power Control

��

��

��

� ��

��

��

ISSUE 11 REVISION 4Power Control



3–78

Power Control

BSS

The MS provides averaged RSSI measurement samples on the downlink radio path tothe RSS. The RSS then performs its own averaging and these values are comparedagainst the power control thresholds. All, or a proportion of the averaged values beingconsidered must exceed the threshold value before any action will be taken.

The proportion of averaged values that must exceed the threshold is determined by twodatabase fields, decision_1_n1 and decision_1_p1 for increasing the output power anddecision_1_n2 and decision_1_p2 for decreasing the output power. The “n”parameters represent the number of previously averaged values to be considered andthe “p” parameters are the proportion of those averages that must exceed the thresholdvalue. If “p” and “n” were set to the same value then all averaged values considered bythe RSS must exceed the threshold value.

Two threshold values are required, one to determine when the BSS output power levelshould be increased and another to determine when the BSS output power level shouldbe decreased. These thresholds are set in the l_rxlev_dl_p (power increase required)and u_rxlev_dl_p (power decrease required).

ISSUE 11 REVISION 4 Power Control



3–79

Power Control – BSS

� ��"(��&��!� ��

� %�"(��&��!� ��

��$ ��

� ��#� ��

� ��#� ��!��

� ��#� ��

� ��#� ��!��

��&�"��#

� ��!�� ! '�"��"��#�

� ��!�� ! '�"��"��#�

� !� %$� ��&�"��#��%#$��(��$�"�#� ��

��"�#� ��

� �!�"�# �

0

10

20

30

40

–110dBm

–100dBm

–90dBm

–85dBm

–80dBm

–75dBm

–70dBm

Threshold Value Signal Strength

l_rxlev_dl_p= 25

u_rxlev_dl_p= 35

.

.

.63 –47dBm




3–80

Power Control

MS

The RSS measures the uplink signal strength received from the MS. The RSS thenaverages these samples and the averaged values are compared against the powercontrol thresholds. All, or a proportion of the averaged values being considered mustexceed the threshold value before any action will be taken.

The same database fields as used in BSS power control are used to determine whatproportion of averaged values must exceed the threshold before increasing or decreasingits output power.

Two threshold values are required, one to determine when the MS output power shouldbe increased and another to determine when it should be decreased. These thresholdsare set in the l_rxlev_ul_p and u_rxlev_ul_p fields.




3–81

Power Control – MS

� ��#)��'�&��"� ��

� &�#)��'�&��"� ��

�� %!��

� ��$�! ��

� ��$�! ��"��

� ��$�! ��

� ��$�! ��"��

��'�#��$

� ��"�� "!(�#�� #��$�

� ��"�� "!(�#��#��$�

� "�!&%�!�� '�#��$��&$%��)��%�#�$�!��

��#�$�!��

�!�"�#�$!

0

10

20

30

40

–110dBm

–100dBm

–90dBm

–85dBm

–80dBm

–75dBm

–70dBm

ThresholdValue

Signal Strength

l_rxlev_ul_p= 20

u_rxlev_ul_p= 30

.

.

.63 –47dBm




3–82

Power Control

RXQUAL

The MS and RSS not only provide measurements for the RXLEV of the uplink anddownlink radio paths but also measure the quality of these paths. The RXQUALmeasurements are averaged by the RSS and compared against upper and lowerthresholds set in the database. If all or a proportion of the averaged values beingconsidered exceed the threshold value then the power output of the MS and BSS can beadjusted accordingly.




3–83

Power Control RXQUAL

� #�)/(,�#�,#�'��

� #�)/(,�#��#�'��

� ,�)/(,�#�,#�'��

� ,�)/(,�#��#�'��

��*+�'*�&��

� ��"*"&%��%��

� ��"*"&%��'��

� ��"*"&%��%��

� ��"*"&%��'��

��-�)� �*

� %��'� �'&.�)�"%�)��*�

� %��'�� '&.�)��)��*�

� '�&,+�&��%��-�)� �*�$,*+��/��+!)�*!&#�

�

�

�

��

��

��

��

��

��#,� �**,$��

,�)/(,�#�,#�'��

,�)/(,�#��#�'��

�!)�*!&#�

�&$'�)"*&%

#�)/(,�#�,#�'��

#�)/(,�#��#�'��

ISSUE 11 REVISION 4Handover – RXQUAL, RXLEV



3–84

Handover – RXQUAL, RXLEVRXQUAL and RXLEV measurements are also used to support handovers. If an MS ismoving out of a cells coverage area then RXLEV and RXQUAL measurements will causethe BSS and MS to increase their power output. This process will continue until the MSreaches its maximum permitted output power and then a handover will be required.

The handover thresholds are set in the fields l_rxlev_ul_h , l_rxlev_dl_h , l_rxqual_ul_hand l_rxqual_dl_h . The number of averaged values that must exceed there thresholdsare determined by a similar process to that used for power control.

ISSUE 11 REVISION 4 Handover – RXQUAL, RXLEV



3–85

Handover – RXLEV, RXQUAL

� *!05*%4!3*!(��

� *!05*%4!$*!(��

� ��2-� �$�+�

� *!05/3"*!3*!(��

� *!05/3"*!$*!(��

� ��12%.1�-&��

� $%#)1)-,!!,��

� $%#)1)-,!!.��

� $%#)1)-,!!,��

� $%#)1)-,!!.��

��4%0"'%1

� ,��.��

� ,��.��

�(0%1(-*$

�-+."0)1-,

Threshold Value RXQUAL (ASSUMED)

�

�

�

��

��

��

��

*!05/3"*!3*!(��

*!05/3"*!$*!(��

3!05/3"*!3*�$*!.�

*!05/3"*!3*�$*!.��

� �

Threshold Value RXLEV

0

10

20

30

40

–110 dBm

–100 dBm

–90 dBm

–80 dBm

–70 dBm...63 –47 dBm

l_rxlev_ul/dl_p=25

l_rxlev_ul_h= 12l_rxlev_dl_h= 12

u_rxlev_ul/dl_p=35

ISSUE 11 REVISION 4Handover – Interference



3–86

Handover – InterferenceRXLEV measurements are used to support handovers due to interference if enabled.

The processes involved are identical to that for other handover types in that the RXLEVmeasurements are averaged and then compared to a threshold value.

ISSUE 11 REVISION 4 Handover – Interference



3–87

Handover – Interference

� /�,1&"0�/&�%$��

� /�,1&"0�!&�%$��

� �� .)��!�'�

� !" %-%)(��(��

� !" %-%)(��*��

� ��0",�#"-

�$,"-$)&!

�)'*�,%-)(

�

�

��

��

� �

��

�$,"-$)&!��&/" ��

&�,1+/�&�/&�$��

&�,1+/�&�!&�$��

� ��

0

10

20

30

40

–110dBm

–100dBm

–90dBm

–80dBm

–70dBm

Threshold Value RXLEV

u_rxlev_ul_ih= 20u_rxlev_dl_ih= 20

.

.

.63 –47dBm

ISSUE 11 REVISION 4MS Power Control



3–88

MS Power ControlThe nature of a cellular system requires that the output power of the BSS and MS shouldbe set as low as possible. With the limited resource of the RF spectrum cellular systemsdepend upon the reuse of RF channels. The re-use distance between these channelsdepends mainly upon the subscriber density in a particular area, the greater the densitythe shorter the re-use distance. By keeping the MS and BSS at the minimum acceptablepower output it reduces the chances of interference, particularly co-channel.

Another benefit of effective power control is that the battery life of handportable isextended, thus maximising available talktime.

Power Control Algorithms

At present two power control algorithms are available, the standard Motorola algorithmand an alternate algorithm. The algorithm to be used for both uplink and downlink powercontrol must be specified by decision_alg_num

A number of fields control MS adaptive power:

ms_power_control_allowed

Enables or disables uplink power control, if disabled the MS shall use the value specifiedin max_tx_ms or its maximum power output whichever is the lower. Adaptive uplinkpower is a GSM requirement.

ms_p_con_interval

Determines the minimum time interval between successive power control changecommands. Uplink power control voting is suspended whilst this timer is running.

ms_p_con_ack

When the MS is sent a new power control instruction, it will implement the instruction andthen echo this change back in the L1 part of the uplink sacch message. Only when thistimer has expired or ordered power control = echoed power control willms_p_con_interval begin. This parameter is only effective whendecision_alg_number=1.

pow_inc_step_size_ul

Sets the step sizes for uplink and downlink power increases.

pow_red_step_size_ul

sets the step sizes for uplink and downlink power decreases.

MS – MaximumPower

The RSS is responsible for the power control of MS. It is measuring the signal strengthand quality of the uplink radio path, averaging the measurements and comparing them tothe threshold values.

The max_tx_ms sets the maximum MS output power and the MS will not be told by theRSS increase its power to a level above that set in this field.

ISSUE 11 REVISION 4 MS Power Control



3–89

MS Power Control

� !�%-%*)��'#�)/(�!,��

� ��*.*,*'��'#

��'.!,)�.!��'#

� (-�+*1!,��*).,*'��''*1! ��

� ��*1!,��*).,*'��%-��'!

��*1!,��*).,*'��)��'!

� (-�+��*)��%).!,0�'��

� ��-��$�(/'.%",�(!-

��-��$�(/'.%",�(!-

�

�

�

�� -��$�(/'.%",�(!-

� (-�+��*)��&��

� ��-��$�(/'.%",�(!-

��-��$�(/'.%",�(!-

�

�

�

�� -��$�(/'.%",�(!-

� �*1�%)��-.!+�-%4!�/'

� ��

� �*1�,! �-.!+�-%4!�/'

� ��

MS Maximum Power

� (�2�.2�(-��

�� * �0�'/!-�*)'3�

��!0!)�0�'/!-�*)'3�

ISSUE 11 REVISION 4BTS Power Control



3–90

BTS Power ControlPower control of the BTS is optional. If it is to be supported thebts_power_control_allowed field must be enabled (set to 1). When enabled the BSSmay use up to 15 steps of power control levels with the same step sizes and tolerancesas defined for MS of power class 1.

bts_p_con_interval

Determines the minimum time interval between successive power control changes.Downlink power control voting is suspended whilst this timer is running.

bts_p_control_ack

Determines the maximum time the HDPC will wait for an acknowledgement from theDRIM card that the power control instructor has been carried out. Only when this timerhas expired or ordered BTS power= actual BTS power (acknowledge returned), willbts_p_con_interval begin. This parameter is only effective whendecision_alg_number=1 .

BTS – MAXIMUM POWER

The max_tx_bts field determines the maximum output power for a base stationtransmitter by setting the level at which the maximum power output available can beattenuated. This parameter can be used to tailor the cell size. The BCCH output poweris equal to max_tx_bts .

pow_inc_step_size_dl

Sets the step size for downlink power increases.

pow_red_step_size_dl

Sets the step size for downlink power decreases.

ISSUE 11 REVISION 4 BTS Power Control



3–91

BTS Power Control

� �'&�$#*�%��#"'%# �� #*��

� ��&��

��"��

� �'&�$��#"��"'�%)� � ��

� ��&��!( '��%�!�&

��&��!( '��%�!�&

�

�

�

��&��!( '��%�!�&

� �'&�$��#"��

� ��&�� #��&

��&�� #��&

��&�� #��&

�

�

�

��&�� #��&

� !�+�'+��'&� ��

� &'�$&�#��&�#��''�"(�'�#"��%#!��!�

�"��#%��!��"�'��&��#��

� $#*��"��&'�$�&�,��

� ��

��

�

�

��

� $#*�%��&'�$�&�,��

� ��

��

ISSUE 11 REVISION 4Rapid MS Power Down



3–92

Rapid MS Power DownRF Problems can exist when a MS initially begins a call, transmitting a power level that istoo high in relation to the proximity of the BTS antenna system. These problems includeintermodulation and uplink interference to other carriers and cells especially in amicrocellular environment where distributed antennas and leaky feeders are frequentlyemployed.

The rapid power down feature can be employed to decrease the MS transmit power to anacceptable perceived level, as seen by the BTS, this desired level will probably beconfigured to be in the middle of the power box. This mechanism can be made to workmuch faster than the normal power control algorithm and indeed is independent of theusual pow_dec_step_size normally employed.

The rapid power down algorithm is quite simple and relies on a number of parameters setin add_cell . The feature is triggered by the strength of the received power level asperceived by the BTS. This power level, ul_rxlev , as measured by the BTS is anaverage that is made up of a number of previously received reports. The number ofreports necessary and hence the speed of the initiation of this feature is controlled byrpd_period . The RSS will perform rapid power down when the perceived power levelexceeds rpd_trigger . The formula simply calculates the necessary attenuation toreduce the MSs output power to the desired perceived level. If the outcome of thecalculation is below the minimum (15) then the minimum value is used.

It should be remembered that an MS utilises 15 power control steps as ordered by theBTS. Each step being 2 dB of attenuation from the maximum. Class two MSs can onlyuse a maximum of 2 (39 dBm) and class four MSs a maximum of 5 (33 dBm).

The worked example opposite should help with the understanding of this algorithm.

ISSUE 11 REVISION 4 Rapid MS Power Down



3–93

Rapid MS Power Down

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ

#�' &��$

" ��

0'.2+)1'0+'-

()/*.)(�+)1)+

+'.2+)1'0+'-

� �

� �

��

��

��

�!�"&�% ��(�,��!��%� �!�� (�,

��(�,

�

�

��(�,

�� "��

� �� %� ��$��# ��"��%� ��$��#�' &��$��" �� !�"�

�&��

��

� �� %� ��$��(�,�

��

��

��!�"

��

ISSUE 11 REVISION 4Rapid MS Power Down



3–94

Rapid MS Power Down

rapid_pwr_down

This parameter will enable/disable this feature. This feature will always be active, it is notjust for the initial setting up of the call. It will essentially work independently of normalpower control. After a power down instruction has resulted from this featurems_p_con_interval will be enforced, preventing any further action until expiry.ms_p_con_interval , will however be overridden if the lower rxlev or rxqual thresholdsare exceeded, this will recover the ms from being in the situation where the orderedpower level is actually too low.

rpd_period

The averaging and voting mechanisms employed by the normal power control algorithmare not utilised by this feature. No voting will occur and the hreqave value will effectivelybe rpd_period . This is the number of previously received uplink reports from layer one,which are used to make up the ul_rxlev average value.

rpd_trigger

This feature will not be initiated until the perceived uplink power level (ul_rxlev ) exceedsthe value of rpd_trigger .

rpd_offset

The value of rpd_offset is used in the calculation, and is the difference between thetrigger value and the desired power level.

ISSUE 11 REVISION 4 Rapid MS Power Down



3–95

Rapid MS Power Down

� ! �� $!��$��

� ��

��

� ! �� !��

� �� !��"

� ! ��#!��!� ��

� ��#��

� ! ��"�#� ��

� ��

ISSUE 11 REVISION 4Optimized Power Control



3–96

Optimized Power ControlThis feature gives the operator more flexibility in that the BSS can now administer uniquestep sizes for MS (UL) and BTS (DL) power control. This is done by creating twoincrement and two decrement step size elements for both uplink and downlink direction.Further enhancements to this feature also allows the BSS to dynamically change theincrement and decrement step sizes based on current power levels and the proximity tothe defined upper and lower power thresholds.

The calculations are shown over page and use the database parameters shownopposite.

ISSUE 11 REVISION 4 Optimized Power Control



3–97

Optimized Power Control

� �!��

�� !� ��

��

� ��

��

� �!��

�� !�� !��

� ��

ISSUE 11 REVISION 4Optimized Power Control Algorithms



3–98

Optimized Power Control AlgorithmsThe algorithms used for the optimized power control feature are shown opposite. Thesewill only be used if the dyn_step_adj flag is enabled.

ISSUE 11 REVISION 4 Optimized Power Control Algorithms



3–99

Optimized Power Control

�+ ��"!)�$�� $��%��'��&!��!)��(��

��

��

)��$��

�� &�! �!��&��$!' �� '"�!��

(��'��&!�&�� $�%&��'�&�"��!��

** � ��

�+ ��"!)�$�� $��%��'��&!�"!!$�#'��&+

��

��

��

)��$��

�� &�! �!��&��$!' �� '"�!��

(��'��&!�&�� $�%&��'�&�"��!��

** � ��

�+ ��"!)�$�$��'�&�! ��'��&!��!!��#'��&+

��

��

��

��

)��$��

��!) � � �� &�! �!��&��$!' �� !) �!��

��(��'��&!�&�� &�%&��'�&�"��!��

** � ��

ISSUE 11 REVISION 4Discontinuous Transmission



3–100

Discontinuous TransmissionDiscontinuous transmission (DTX) is a feature available mainly on handportables MSwhich maximises the battery life of handportables by disabling the transmit function whenthe subscriber is not speaking during a call and will help to reduce interference.

There are three options that can be set in the dtx_required field;

1. MS may use DTX

2. MS will use DTX

3. MS will not use DTX

ISSUE 11 REVISION 4 Discontinuous Transmission



3–101

Discontinuous Transmission

� ��

� ��

��

��

ISSUE 11 REVISION 4Handover Evaluation



3–102

Handover EvaluationThe cause value contained within the handover recognised message will affect theevaluation process in the BSC. The handover evaluator in the SSM will determine theneed for either an internal or external handover upon analysis of the “qualified targets”within the message. The SSM will be supporting a number of RRSM’s and hence couldpossibly be receiving multiple handover recognised messages in quick successionduring busy periods. These messages are queued and are dealt with in the priorityshown opposite.

ISSUE 11 REVISION 4 Handover Evaluation



3–103

Handover Evaluation

�� "

�� "

��

�� !��"

�� !��

��

�� !��

��

� ��!��

ISSUE 11 REVISION 4Handovers Allowed



3–104

Handovers AllowedThere are a number of reasons as to why an MS may need to be handed over from onechannel to another. These include RXLEV uplink/downlink and RXQUAL uplink/downlink.

Before a handover can take place either due to the quality or strength of the signal thattype of handover must first be enabled in the database.

ISSUE 11 REVISION 4 Handovers Allowed



3–105

Handovers Allowed

� ��

� ��

� ��

� ��

� ��

��

ISSUE 11 REVISION 4SDCCH Access – handovers



3–106

SDCCH Access – handoversAn MS is allocated an SDCCH to carry out the call set up procedures including,authentication, validation of equipment and subscriber, the setting of encryption and theallocation of a TCH if required. An SDCCH is also used for SMS delivery and locationupdating.

It is possible that an MS utilising an SDCCH slot may have the need to perform an inter-or intra-cell handover. This “need” will be calculated by the HDPC algorithms usinguplink calculations and SACCH reports in the normal way. SDCCH handovers arepermitted by the setting of the sdcch_ho flag. This handover though, will only occur ifthe MS has occupied the SDCCH for at least the period set in sdcch_timer_ho .External SDCCH handovers have to be enabled by the MSC, not all MSCs support thisfeature.

ISSUE 11 REVISION 4 SDCCH Access – handovers



3–107

SDCCH Handover

� !��

� ��$� ��!��

� ��$� ��

��$� ��%�!��"��

� !��"��

� ��#�"�� !

��#�"�� !

�

�

�

�

��#�"�� !

ISSUE 11 REVISION 4Handovers – Interference



3–108

Handovers – InterferenceIf the RXQUAL of either the uplink or downlink reaches the threshold that would normallycause a handover but the RXLEV is at a value higher that the threshold requiring a powerincrease then a handover may be initiated due to interference, if theinterfer_ho_allowed field is enabled. This type of handover would be intra-cell.

ISSUE 11 REVISION 4 Handovers – Interference



3–109

Handover – Interference

� ��

� ��

��

ISSUE 11 REVISION 4Handovers – Interference



3–110

Power BudgetHandover

A field in the database determines whether the use of the power budget assessmentprocess for handover purposes can be used or not.

If an MS on an allocated resource during its measurement reporting process seesanother channel that would provide an equal or better quality radio link requiring a loweroutput power then a handover may be initiated. Handovers due to power budget ensurethat the MS is always linked to the cell with the minimum path loss even though thequality and level thresholds, may not have been exceeded.

The pwr_handover_allowed field enables/disables power budget handover. If enabledfor each established radio link and neighbour BCCHs, defined in the BCCH allocation,the BSS will use the following to determine whether a handover is required.

1. Maximum uplink power permitted on serving and adjacent cells

2. Serving RXLEV downlink (adapted)

3. Neighbour RXLEV downlink

4. MS maximum power allowed

5. Handover margin

ISSUE 11 REVISION 4 Handovers – Interference



3–111

Power Budget Handover

� ��

� ��

��

ISSUE 11 REVISION 4Timing Advance – MS Maximum Range



3–112

Timing Advance – MS Maximum RangeThe RSS is able to instruct the MS to advance its timing to compensate for thepropagation delay incurred on the uplink radio path. Even though the RF signal istravelling at the speed of light the nature of the TDMA timing could make any delaycritical. The Training Sequence Code (TSC) position in the TDMA timeslot is constantlymonitored and the BSS software calculates by how much the MS timing needs to beadvanced to keep it centralised. The timing advance setting is then transmitted to theMS on the downlink SACCH.

The interval between timing advance changes is determined by thetiming_advance_period field.

ISSUE 11 REVISION 4 Timing Advance – MS Maximum Range



3–113

Timing Advance – MS Maximum Range

� ��

� ��

��

�

�

�

�

�

�

��

ISSUE 11 REVISION 4Handover–MS Maximum Range



3–114

Handover–MS Maximum RangeBefore a handover can be initiated due to the MS approaching its maximum range thems_distance_allowed field must be set to 1 (enabled).

The maximum timing advance setting can compensate for a distance 34.892 km over 63steps. The ms_max_range field can be set to any one of these 63 steps effectivelydetermining the cells radius. As it is the RSS calculating the timing advance, it will beaware of the MS approaching its maximum range and if all or a proportion of timingadvance averaged values exceed the ms_max_range field a “handover recognised”message will be generated.

ms_max_range is also used by the PRSM to reject (ignore) channel requests fromdistant mobiles. This feature is invoked by enabling chg_elementpoor_initial_assignment .

decision_1_n8 and decision_1_p8 are the voting parameters used to trigger a distancehandover.

ISSUE 11 REVISION 4 Handover–MS Maximum Range



3–115

Handover – MS Maximum Range

� ��!��

� � ��

� ��

��

� ��"��

� ��

��

� ��

� ��

� ��

ISSUE 11 REVISION 4Handovers



3–116

Handovers

IncomingHandovers

Incoming handovers to a cell can be enabled/disabled, regardless of cell barring, usingthe en_incom_ho flag. en_incom_ho is a per cell CRM Element and if set to 0 willreject any handover requests.

ISSUE 11 REVISION 4 Handovers



3–117

Incoming Handovers

� ��

� ��

��

��

ISSUE 11 REVISION 4Handovers



3–118

Intra-CellHandovers

Intra-cell handovers is an optional feature in the GSM system and would normally only berequired if an MS is on a radio channel that is subjected to co-channel interference. Poorsignal strength measurements taken on the original radio channel would not normally beimproved by performing intra-cell handovers as the signal strength of all radio channelswithin that cell would be similar. Intra cell handovers can occur through quality althoughinterference problems will generally be the cause.

Three options are specified for this database field:

0 – “Not performed by BSS”. An intra_cell ho may still be performed but it will be controlled by the MSC. The handover required message will be sent to the MSC and may contain the server as a potential candidate along with the other targets specified by RSS.

1– ”Performed by BSS if applicable”. Only if RSS specifies the cause value in the ‘ho_recognised’ message as being one of qual or interfer, then an intra_cell ho may be attempted. If the cause value is qual then the intra_cell ho is only attempted when other targets are exhausted. If the cause value is “interfer” then the intra_cell ho is attempted first and only if that fails will the specified targets be tried.

2– “Not permitted” An intra_cell ho will not be performed by the BSS and a “handover required” message will not be despatched to the MSC in respect of this handover.

Inter-CellHandovers

Handovers fall into one of two categories, either “internal” or “external”. Internalhandovers exist between two cells controlled by the same BSC. External handovers willtake place between two cells connected to different BSCs. In all cases externalhandovers will be controlled by the MSC. Internal handovers may be dealt with by theBSC or indeed referred to the MSC, this flag will determine the controlling entity.

0 – The contol of internal inter-cell handovers is disabled at the BSC, all internal handovers will be treated the same as external ones in that a handover required message will be despatched to the MSC.

1 – The control of internal inter-cell handovers is enabled in BSC.

2 – The control of internal inter-cell handovers is disabled at the BSC. These handovers will not be executed by the MSC either as the BSC will not format the handover required message in repect of them. External handovers will be executed in the normal way.

3 – The execution of internal and external inter-cell handovers is disabled at the BSC. These handovers will not be executed by the MSC either as the BSC will not format the handover required message in repect of them.

ISSUE 11 REVISION 4 Handovers



3–119

Inter/Intra-cell Handovers

� �� !��"��

� �� $��

��$��

��

��

� �� !��"��

� �� $��

�� $��

��

��

�# ��

��

�# ��

ISSUE 11 REVISION 4TCH Resources Reporting



3–120

TCH Resources ReportingThe number of dedicated traffic channels in use within a BSS may be useful informationfor the MSC to enable it for instance to balance the traffic between cells. The number ofTCHs currently allocated can be indicated to the MSC with a BSSMAP RESOURCEINDICATION MESSAGE. The message can be sent in various cases controlled by theMSC and solicited with BSSMAP RESOURCE REQUEST MESSAGE. One of thesecases is spontaneous mode which is the sending of information when certain conditionsare met. These conditions are set in database high and low watermark fields for full ratechannels.

When the number of available TCH rises to the high watermark values or falls to the lowwatermark values the MSC will be informed if the resource request message has beenreceived from the MSC indicating spontaneous mode.

ISSUE 11 REVISION 4 TCH Resources Reporting



3–121

TCH Resource Reporting

� �� "� �!�# ��"��$�"� ��

� �� "� �!�# ��"��$�$�"� ��

� �#�� !

��

ISSUE 11 REVISION 4Preferred Target Cell



3–122

Preferred Target CellA MS is continually monitoring the signal strength of neighbour BCCHs, generatingmeasurement reports and transmitting them to the BSS. The MS is able to monitor up to32 BCCHs for handover purposes, the BSS has got to be able to detect when ahandover is required and then evaluate the measurement data provided by the MS toprovide a list of preferred cells that the MS should be handed over to.

The requirement for handover is detected by the Radio SubSystem associated with thecell. The RSS is processing the measurements provided by the MS and when theparameters are met for handover a “handover recognised” message is sent to theSignalling Connection Control Part State Machine (SSM) at the BSC. Included as part ofthe “handover recognised” message is a list (up to 32) of target cells that meet therequired criteria. The list of target cells is given in order of predicted best performance.

The list is evaluated by the BSC and it is determined whether an intra- or inter-BSShandover is required. If an intra-BSS handover is required then it will be controlled by theBSC, if the handover is to a cell in a different BSS then the MSC will control it.

In the case of an inter BSS handover a “handover required” message is transmitted fromthe BSC to MSC. Contained in this message is a list of preferred cells, the number ofwhich being determined by the number_of_preferred_cells field.

ISSUE 11 REVISION 4 Preferred Target Cell



3–123

Preferred Target Cells

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

� (/'�!,�)"�*,!"!,,! ��!&&-��

�� '�1�(/'�!,�)"�.�,#!.��!&&-��)(.�%(! �%(�.$!�

2$�( )0!,�,!+/%,! ��'!--�#!�

��

��

��

��

��

ISSUE 11 REVISION 4Handover Reporting



3–124

Handover ReportingThe handover detection and power control process in the RSS software is responsible fordetecting the need for a connection to be handed over to another cell. When all therelevant criteria have been met this process will generate a handover recognisedmessage which will be sent to the SSM for evaluation. This message will contain acause value, expressing the reason why this handover is necessary, and also a numberof “qualified neighbours.” Although this message is processed by the SSM it is actuallytransmitted via the RRSM to pick up relevant connection identities. When the messageis sent the HDPC starts the handover_recognized_period timer for that connection.Whilst this timer is running the handover triggering mechanism, which initially producedthe recognised message, is inhibited, hence whilst this timer is running another handoverrecognised message for this connection could not be generated. In most circumstancesthis timer would not expire as a handover will have been executed and the connection willbe deleted from that cell. If the timer were allowed to expire then the handover triggeringmechanism will begin again for that connection.

HandoverEvaluating

Upon receipt of the handover recognised message the handover evaluator in the SSMwill, upon examination of the neighbours, determine if an external or internal handover isnecessary. Should the handover be external then the SSM will generate a handoverrequired message which will be sent to the MSC, this message is very similar to thehandover recognised message. When this message is sent the SSM will start GSMtimer T7 (BSSMAP_t7), whilst this timer is running no more handover requiredmessages will sent with reference to same connection. When this timer expires the SSMmay generate another message, but only if a new handover recognised message hasbeen received from the HDPC. This timer is not a repetition timer, the same handoverrequired message will not simply be repeated. This functionality is important as in thiselapsed time the cause for handover may have changed along with the number ofqualified neighbours.

HandoverRejection

The element handover_required_reject_switch may effect the above process. If set toon the handover required message will only contain the external neighbour specified inthe handover recognised message, any internal neighbours will not be included. If theMSC is unable to hand the connection over, possibly because of congestion orsubscription reasons it will send the BSC a handover required reject message. The SSMwill then re-examine the handover recognised message and attempt to commit aninternal handover. If the handover_required_reject_switch is off the BSC will includeall the neighbours specified in the handover recognised message in the the handoverrequired message. In this case the MSC will not return the handover required rejectmessage in the case of failure.

Note:

This parameter is set in chg_element.

ISSUE 11 REVISION 4 Handover Reporting



3–125

Handover Reporting

��

�)"�$��

��

�� !(�$�$��!� �%��

�� !(�$�$��!� �%��"�$�!�

�� !(�$��%�! �"$!��%%�%

� ��&��

�� !(�$�$��!� �%��

�� &!��

�� '�&��$��%

��'�&��

Handover Reporting

��

�)"�$��

�

�� !(�$�$�#'�$��

�� !(�$�$��!� �%��

�� !(�$�$�#'�$��

��

�� !(�$�$��!� �%��

��

�� &!��%

��'�&��

ISSUE 11 REVISION 4Handover Power Level



3–126

Handover Power LevelThe power level the MS must use to access the target cell is included in the handovercommand. This power level, along with other Layer 3 information regarding the newchannel such as channel type, frequency, slot etc will be provided by the target cell. Thepower level to be used for all incoming handovers is the add_cell elementhandover_power_level . This level is used for all inter_cell handovers, external andinternal.

ISSUE 11 REVISION 4 Handover Power Level



3–127

Handover Power Level

handover_power_level= <*>

* = GSM9002 – 39 dBm...19 – 5 dBm

* = DCS1800 and PCS19000 – 30 dBm

1 – 28 dBm2 – 26 dBm...15 – 0 dBm

ISSUE 11 REVISION 4Calculated Handover Power Level



3–128

Calculated Handover Power Level

Overview

When a mobile hands over into a new cell, its first transmission into the new cell istransmitted at a certain level.

This level can be fixed by the handover_power_level parameter, but this level is oftenfairly high, resulting in immediate power control activity to reduce the mobile’s transmitpower.

Instead, the mobile can be instructed to use a calculated level that lies inside the powercontrol window right from the start. This facility is set up using theuse_derived_ho_power parameter and uses the following formula:

Handover power level= min (C+(A–B), D, P)

where: A= max_tx_bts of the target cell

B= rxlev_dl from the target cell

C= ��

� = centre of the target cells uplink power

window

D= max_tx_ms of the target cell

P= power class of the mobile

This facility is only supported for intra_BSS handovers.

ISSUE 11 REVISION 4 Calculated Handover Power Level



3–129

Calculated Handover Power Level

%#��"�&�� ! '�"��

� ��%#�� &�"�! '�"��&��

��%#��%��$�� &�"��&��

�� &�"��&��

'��"� � ��(�$(��$#� ��$�"��$��

�� "(��&��" ��$�"��$��

��

��

��$"�� $�"��$��#�%!��! '�"�

'�� '

�� (�$(��#� ��$�"��$��

�� ! '�"��##� ��

ISSUE 11 REVISION 4Calculated Handover Power Level



3–130

Handover DefaultInformation

The handover default parameters found in add_cell are GSM parameters which specifydatabase fields for a handover to an ‘unknown’ cell. A handover to an unknown cell, onewhich is not specified in the BA list, is not possible using Motorola’s infrastructure.Motorola uses these parameters for a similar purpose to default handover fields notspecified in add_neighbor .

None of the default parameters are used in the case of an external handover, ms_txpwr_max_cell , ho_margin_cell and rxlev_min_cell must be specified in theadd_neighbor command.

For an internal handover however, ho_margin_cell and rxlev_min_cell can beoptionally specified in add_neighbor . If they are not specified in add_neighbor thedefault parameters in add_cell will be used. ms_txpwr_max_def will never be used foreither case internal or external handovers. The uplink parameter used in the handoverdecision process is max_tx_ms of the neighbour, in the case of an internal orms_txpwr_max_cch of the neighbour (found in the add_neighbor command) in thecase of external.

ISSUE 11 REVISION 4 Calculated Handover Power Level



3–131

Handover Default Information

� #(�),&+'�#�,��

� ��

��

� %�#�'�!$��

� � �)%��

� ',"�*�#!$��

� ��#

��#

��#

�

�

��#

ISSUE 11 REVISION 4Handover Initiation



3–132

Handover Initiation

rr_t3103

The handover procedure is initiated by the network sending a “handover command”message to the MS. The “handover command” message contains information regardingthe target TCH, initial power setting to access the target cell, necessary signallingprocedures and a handover reference.

On sending the initiate handover message to the source RRSM, the SSM begins timerrr_t3103 . In the normal chain of events, this timer should never be allowed to expire. Itis guarding the receipt of either the unsuccessful handover message from the sourceRRSM or the handover successful message from the target RRSM. The receipt of eitherof these messages will stop the timer. If this timer is allowed to expire then a clearrequest will be sent to the MSC in a bid to clear the connection. It should be noted thatfurther timers in the source and target RRSMs are also guarding the receipt of similarmessages from the MS. Should these timers expire without the receipt of the handovercomplete (target RRSM) or handover failure (source RRSM), then the RRSM in eachcase will release the channel and inform the SSM, these messages also have the effectof stopping rr_t3103 .

ISSUE 11 REVISION 4 Handover Initiation



3–133

rr_t3103

��

��

��"�#)�%��#!!�"�

��"�#)�%�� (%�

�"�'��'��"�#)�%

�"&(��&&�( ��"�#)�%

�*$�%��

%%�'��

%%�'��

%%�'��

��

�*$�%��

��"�#)�%��#!$ �'�

��"�#)�%�&(��&&�(

� %%�'��

��!� �&��#"�&

�� %�"��'#��

��( '�)� (��

��

��

��

��

ISSUE 11 REVISION 4Handover Channel Establishment



3–134

Handover Channel EstablishmentAn MS that has just handed over to a new traffic channel sends a number of “handoveraccess” messages to provide the RSS with the RF characteristics necessary to calculatetiming advance. The RSS having calculated the timing advance and power control sendsthis information in the form of a “physical information” message to the MS.

When sending the “physical information” message timer rr_t3105 is started. If rr_t3105expires before correct response from the MS has been received rr_t3105 is reset andthe “physical information” message is repeated. This process is repeated a number oftimes until either the MS correctly responds or the maximum number of repetitions (NY1)is reached.

If the maximum number of repetitions is reached the newly allocated channels arereleased and the handover abandoned.

ISSUE 11 REVISION 4 Handover Channel Establishment



3–135

Handover Channel Establishment

SYS02_3_Handover_Channel

MS RSS (S) RRSM (S) SSM

ho_cmdho_cmd

RSS(t)

RRSM(t)

ho_detect received

ho_succho_cmplt

Establish indication

ho_detection

ho_access

ho_access

ho_access

ho_cmplt

ho_access

UA

SABM

Phys info

initiate handover

� ��

� ��

��

� ��

� ��

��

��

ISSUE 11 REVISION 4RSS Link Fail



3–136

RSS Link FailIf an MS, established on a radio resource, is lost for whatever reason the RSS must havea means of detecting its loss. If not then the resources that had been allocated wouldcontinue to support an MS that is no longer there and would not be made available forother MS.

To maximise the efficient use of resources the RSS is able to monitor the receipt ofSACCH from the MS. If SACCH is not received for a database determined period of timethen the MS is assumed to be lost and the allocated resources are then made availablefor other MS.

The link_fail parameter sets the maximum value of a counter(s). If the RSS is unable todecode a SACCH message S is decreased by one. If the RSS successfully decodes aSACCH message S is increased by two. In either case S should be equal to or morethan the value set in the radio_link_timeout field.

ISSUE 11 REVISION 4 RSS Link Fail



3–137

RSS Uplink Failure Detection

� &$'%�#�$& ��

� ��

��

�

�

�

��

�(+'*")��

�

�

�

�

�

��

�" (!"!

�(*�!" (!"!

ISSUE 11 REVISION 4RSS Link Fail



3–138

Radio LinkRevival

The full_pwr_rfloss field enables or disables the ability of the RSS to instruct the MSand BSS to go to maximum output power in an attempt to save the link before it is timedout. This feature is triggered by the link_fail counter reaching the lower thresholdlink_about_to_fail .

ISSUE 11 REVISION 4 RSS Link Fail



3–139

Radio Link Revival

� �&��"!'�#�#��!$$��

� � ��$��

��

� �� !&%�%!��

� ��

��

�

�

�

��

ISSUE 11 REVISION 4Loss of Radio Link



3–140

Loss of Radio LinkThe criteria for radio link failure by an MS is based on the radio link counter(S). If the MSis unable to decode a SACCH message S is decreased by 1. In the case of a successfulreception S is increased by 2.

The maximum value of S is set in the radio_link_timeout field. If S reaches 0 thenradio link failure is assumed and the MS will abort the radio resource connection.

The radio_link_timeout parameter is transmitted on the BCCH of each cell and is usedby the MS to set T100, it is applicable once the MS is on a SDCCH or TCH.

In the example opposite the field has been set to 0. (4 SACCH messages).

��

��"��

�� !��

�� !��!��

ISSUE 11 REVISION 4 Loss of Radio Link



3–141

Radio Link Timeout

� "��!�� #��!$#��

� ��

��

�

�

�

��

SYS02_3_radio_link

link_fail

link_about_to_fail

full_pwr_rfloss

radio_link_timeout

ISSUE 11 REVISION 4Timers rr_t3109



3–142

Timers rr_t3109rr_t3109 is started when a lower layer failure is detected by the network or in the channelrelease procedure. Its purpose is to release the channel for further use.

Uplink Failure

In order to monitor both uplink and downlink radio paths both the MS and BSS willmonitor the appearance of SACCH messages. Should an uplink failure occur and thethreshold of lost SACCH messages is reached (link_fail parameter) the BSS will activaterr_t3109 . In addition to this the BSS will no longer transmit SACCH messages to theMS. The MS will now no longer receive SACCH messages and its own threshold of lostSACCHs, T100 (set to radio_link_timeout ) will eventually be reached.

When T100 has expired the MS will return to the idle mode and monitor the cell BCCH.The BSS will also release the channel resources but only after rr_t3109 expires whichwill be after T100.

Downlink Failure

A downlink fail will follow the same pattern, T100 will expire in the MS and SACCHs willno longer be sent uplink. Lack of SACCHs will cause link_fail to exceed at the BSS andsubsequently cause rr_t3109 to activate and eventually expire.

rr_t3109 must be set to higher value than T100 as it is used by the system when lowerlink failure is detected. T100 should therefore expire before rr_t3109 ensuring that thesystem holds on to radio link long enough for the MS to release it. If not, it will bepossible to have two on the same TCH.

ISSUE 11 REVISION 4 Timers rr_t3109



3–143

Link Failure

��

$

��

��

�� "%��

�"�� $�� %$�

��

�(��

�

��$%"��$ ��

��$#�� "�""�$��

$ ��(!�"�� "�

$�"��$��

"�# %"��#

""�$��"%��

��(��

""�$��$�&�$��

��"�� $�� %$�

��$�&�$��

�

��$

� '��

��$�&�$��

ISSUE 11 REVISION 4Timers rr_t3109, rr_ t3111



3–144

Timers rr_t3109, rr_ t3111

Normal ChannelRelease

The system initiates the release of a channel by sending a channel release message tothe MS and will start an internal timer rr_t3109, coincidentally SACCH messages aredeactivated. On receipt of the channel release, the MS will start an internal timer (t3110)and disconnect the main signalling link by sending a Layer 2 disconnect frame. Whent3110 times out or when the signalling is disconnect confirmed on receipt of a layer 2numbered acknowledgement, the MS deactivates all RF links and returns to BCCH idlemode.

On the system side, when the Layer 2 disc is received the BSS will stop rr_t3109 andstart rr_t3111 . When rr_t3111 has expired all RF links are terminated and are then freeto be allocated to other MS. The purpose of rr_t3111 is to allow time for the disconnectframe to be acknowledged with a Unnumbered Acknowledgement (UA) frame and toprotect the channel in case the acknowledge frame is lost. Additionally, as rr_t3111 runsfor a shorter time than rr_t3109, the channel is able to be re–assigned far quicker.

If rr_t3109 times out all RF channels will be deactivated and are then free to be allocatedto other MSs. The value of rr_t3109 should always be greater than t3110 so that there isa high probability of normal termination.

N.B. The value of rr_t3111 must be set to a value equal to the value of rr_t3110 .

ISSUE 11 REVISION 4 Timers rr_t3109, rr_ t3111



3–145

Normal Channel Release

SYS02_3_normal_channel

t3110 rr_t3109

SACCH DEACTIVATED

MM

MS

MM

BSS

CHANNEL RELEASE

rr_t3111

MS BSS

BCCH

t3110Layer 2

MS

Layer 2

BSS

t3110 rr_t3109Layer 2

MS

Layer 2

BSS

DISCONNECT

FRAME

rr_t3111

UA

Stopped onreceipt ofdisc

Activatedon receiptof disc

Stopped on receiptof disc

Radio resourcesreleased onrr_t3111 expiry

� ��

��

��

��

� ��

��

��

��

��

ISSUE 11 REVISION 4CRM Timers



3–146

CRM Timers

rf_chan_rel_ack

During the channel release procedure to end a call, the CRM sends an “RF channelrelease” message to RSS, at this point the timer is started. Once the RSS has releasedthe physical circuit it will send an “RF channel release acknowledge” message to theRRSM, which is then forwarded to the CRM. When CRM receives this message thechannel can be marked as available and can be allocated to another subscriber. If thetimer is allowed to expire the channel will be marked as available anyway.

ISSUE 11 REVISION 4 CRM Timers



3–147

CRM Timers

!��!��

��

��!��"�

��!��"��

��!��"��!��%��

��#��!��"��&��#��' �!�

��&��!��"��!��

��"��"

��!��#��

��$�#�%��$��"�

ISSUE 11 REVISION 4Call Re-establishment



3–148

Call Re-establishmentIn the event of a radio link failure, a feature of GSM is call re-establishment.

If a radio link has failed, due to an MS passing through a tunnel for example, the MS willsample the received signal strength of BCCH carriers including the original serving cell,average the measurements taken and then select the cell having the highest average.Assuming that the selected cell is one of the home PLMN cell or one supporting roaming,the cell is not barred and the reestablish_allowed field is set to 0 (call re-establishpermitted) then the MS will attempt to re-establish the call.

If the MS is unsuccessful on the selected cell it may attempt the same process on fiveother cells offering the highest received signal strength measurement. If stillunsuccessful re-establishment will be aborted.

ISSUE 11 REVISION 4 Call Re-establishment



3–149

Call Re-establishment

� ��

� ��

��

ISSUE 11 REVISION 4CRM Timers



3–150

CRM TimersIn addition to rr_t3109 , rr_t3111 and rr_t3212 there are two other timers needed by theCRM on a per cell basis. Their function is as described below:

dealloc_inact

When an “error indication” is received from RSS to indicate a fatal error at Layer 2 thistimer is started. If the call is to be dropped the RRSM will return a “deallocate inactivedch” to the CRM which will in turn release the channel. If the CRM does not receive a“deallocate inactive dch” it will assume the RRSM has recovered the connection and willnot release the channel.

ho_ack

This timer is used during the intra_cell handover procedure when the serving timeslotgoes Out Of Service (OOS). It is started when the CRM sends an “internal handoverassignment” message to the RRSM specifying the target channel to be used. Afterfurther messaging between the RRSM and SSM to switchover the terrestrial trunk in theBSC, the RRSM will return an acknowledgment to the CRM. If the timer is allowed toexpire and no acknowledgment is received the CRM re-marks the newly assignedchannel as free and available for further allocation to another subscriber.

ISSUE 11 REVISION 4 CRM Timers



3–151

CRM Timers

��!!$��#��(��

��

��&&$&

��!!$��(��#��(�*��

��"�&��,%�&�'

�$##��(�$#��'�"��#(��#��

�#(�&#�!��#�$*�&��''��#"�#(

�#(�&#�!��#�$*�&��''��#"�#(��

��

�$��

�&&$&��#��(�$#��)'��

��"�&��,%�&�'

��##�!�+�!!��"�& ��'��&��

��"�!!�'��$#�'

��!��&�#��($��

��)!(�*�!)��#$#�

��"�!!�'��$#�'

��!��&�#��($��

��)!(�*�!)��#$#�

ISSUE 11 REVISION 4Cell Exercise



3–152

Cell Exercise

Adding a Cell

1. The two cells being equipped are part of the Swiss PLMN, both in Location Area255 and are numbered 1 and 2 at site 1.

2. The two cells use the EGSM frequency band.

3. If resources requested by an MS are not available, then it must, on receipt of an“immediate assignment reject” message wait 3 seconds on cell 1 and 10 secondson cell 2 before reattempting.

4. No form of queuing is permitted on either cell.

5. Channel reconfiguration is permitted.

6. The preferred number of SDCCHs is 8 for both cells

7. The maximum number of SDCCHs for cell 1 is 24 and for cell 2 is 32.

8. In both cells, if there are just 2 free SDCCHs available then reconfiguration fromTCH to SDCCH should occur. To allow this reconfiguration 5 or more trafficchannels should be idle.

9. In both cells, if 14 free SDCCH’s are available then reconfiguration from SDCCH toTCH should occur.

10. A total of 9 CCCH blocks are available of which four are reserved for AGCH on cell1 and 3 on cell 2.

11. Normal paging is in operation and there will be an interval of approximately onesecond between transmission of paging messages to MSs of the same group.

12. The CRM will allocate channels on a best-to-worst basis, each channel beingplaced in one of five interference bands ranging from an absolute noise level of–85 dBm, –90 dBm, –95 dBm, –100 and –105 dBm.

13. The CRM will attempt to allocate an SCCP reference number up to eight times forcell 1 and seven times for cell 2.

14. Access to either cell is not restricted in anyway.

15. An MS, when first accessing either cell, will do so at a power level of 37 dBm.

16. The MSC must be informed when the number of full rate channels available risesto eight or drops to two.

17. DTX will not be used on cell 1 and may be used on cell 2.

18. Attach/detach is not supported on either cell.

19. A roaming agreement exists between the Swiss PLMN (NCC of 1), both Italiansystems and both French systems. Cell 1 is positioned on the border facing Italyand cell 2 is located on the border facing France.

20. If an MS receives no response to a “channel request” message it may repeat therequest up to five times on both cells.

21. On detection of a lower layer failure and during the channel release procedure thesystem will hold onto a channel for 15.5 seconds for cell 1 and 100 seconds for cell2.

22. During normal channel release once the main signalling link has been terminatedand the BSS receives a disconnect frame from the MS the RF link will beterminated after 7.68 seconds for cell 1 and 5 seconds for cell 2.

ISSUE 11 REVISION 4 Cell Exercise



3–153

23. Periodic updates are not supported on either cell.

24. If on request an SDCCH is not available then the channel request is to be dropped.

25. If an MS is required to handover into both of these cells, it should send handoveraccess bursts at a power level of 43 dBm.

26. If the MS is unable to decode a SACCH message for approximately 12 secondsthen it will assume radio link failure and abort the radio resource connection.

27. Call re-establishment is allowed on cell 1 and not allowed on cell 2.

28. When considering cell reselection to another location area the target cells C1 orC2 must be 4dB higher than that of the server for cell 1 and 2dB higher than thatof the server for cell 2.

29. The MS receive level must be at least –106 dBm from cell 1 and – 95 dBm fromcell 2 before attempting to access.

30. When allocated a hopped TCH which includes the BCCH carrier, measurementreporting of the BCCH frequency should be carried out on cell 1 and should not becarried out on cell 2.

31. Intra- and Inter-cell handovers are permitted and can, if applicable, be controlledby the BSC.

32. The maximum number of target cells to be specified in a “handover required”message will be 6 for both cell 1 and 2.

33. After a handover_recognised message has been generated the handover triggermechanism will be inhibited for approximately 4 seconds.

34. If resources are not available at a target cell for handovers from cell 1 then thesource BSC must be informed by the switch. For handovers from cell 2 the BSCneed not be informed.

35. If the network does not receive either a “handover complete” message on the newchannel, a failure message on the old channel or the MS re-establishing the callafter the MS has been told to handover from cell 1 for 4.1 seconds and from cell 2for 1.5 seconds then the source channel will be released and all references to thatMS cleared.

36. If after requesting radio resources the signalling link is not established in 1.7seconds for cell 1 and 1.5 seconds for cell 2 the allocated resources will bereleased and the channel request message ignored.

37. MS power control is allowed, the minimum time between power control ordersbeing approximately 10 seconds for cell 1 and 6 seconds for cell 2. The maximumMS output power that the MS will be told to go to is 39 dBm. Power incrementswill be 6 dB steps and will be reduced in 4 dB steps for uplink and downlink.

38. BTS power control is allowed and the maximum output power for cell 1 will be 39dBm and for cell 2, 43 dBm.

39. The minimum interval between BTS power changes is approximately 2 seconds forcell 1 and 1 second for cell 2.

40. For handover, timing advance and power control functions 66% of 12 averagedvalues must exceed the set threshold for cell 1 and 75% of 8 averaged values forcell 2.

41. The thresholds for BSS power control are–90 dBm and –75 dBm for cell 1 and

–104 dBm and –95 dBm for cell 2.




3–154

42. The thresholds for MS power control are –90 dBm and –75 dBm for cell 1 and–104 dBm and –95 dBm for cell 2.

43. The threshold for handovers due to RXLEV in both the uplink and downlinkdirections are –100 dBm for cell 1 and –98 dBm for cell 2.

44. The lower threshold for power control in both the uplink and downlink direction dueto RXQUAL is a BER 13.5% for cell 1 and 16% for cell 2.

45. The thresholds for handovers due to interference are a BER of 10% and a RXLEVof –95 dBm for cell 1 and a BER of 10% with a RXLEV of –95 dBm for cell 2 ineither the uplink or downlink direction.

46. Handovers due to power budget are not allowed.

47. Default values for RXLEV minimum if not known by source BSS are –100 dBm forcell 1 and – 95 dBm for cell 2.

48. Default value for MS maximum power in a target cell if not know by source BSSare 39 dBm for both cell 1 and 2.

49. The default values for the handover margin is 16 dB for cell 1 and cell 2.

50. Handovers due to RXLEV, RXQUAL, interference and timing advance allowed.

51. Cell 1 should have a maximum timing advance of 50 and cell 2, 40.

52. The minimum interval between timing advance changes for cell 1 is 4.8 secondsfor cell 2 in 2.88 seconds.

53. If the RSS does not decode consecutive SACCH bursts on any link to an MS for aperiod 12 seconds on both cells, the link will be assumed to be lost. When theRSS has failed to decode consecutive SACCH bursts for a period of 8 seconds thedownlink and uplink power shall be increased to the cell maximum for both cells.

54. The BCC for cell 1 is 2 (decimal) and for cell 2 is 3 (decimal).

55. The RSS will check the loading of the RACH for cell 1 every 31 seconds and forcell 2 every 37.66 seconds.

56. The RSS will check the loading of the RACH slots, when an overload condition hasbeen flagged in the previous period, every 40 seconds for cell 1 and every 47seconds for cell 2.

57. If after successfully handing over the MS does not acknowledge the receipt of aphysical information message within 60 ms for cell 1 and 20 mS for cell 2 thephysical information message can be retransmitted, upto a maximum of 20 timesfor cell 1 and 30 times for cell 2.

58. If the neighbour list is changed dynamically from the OMC, subsequentmeasurement reports using the old BA list shall still be processed by the HDPC inthe normal way for both cells.

59. A mobile shall be allowed to handover whilst in dedicated mode on an SDCCH, butonly after it has been on the sdcch for 3 seconds on cell 1 and 2 seconds on cell 2.

60. Both cells shall employ the rapid pwr down feature. The feature will be initiated onno less than 4 reports and trigger at –60 dBm. The desired BTS rxlev after powerdown should be –80 dBm.

61. Both cell 1 and 2 shall be considered “normal” priority cells.

62. The cell reselect offset for cell 2 should be –4dB.

63. The cell reselect offset for cell 1 should be +2dB. The temporary offset should be20dBs for 3 minutes.




3–155

Add_cellWorking Area

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��




3–156

��

��

��


��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��




3–157

��

��

��

��

� ��

��

� ��

� ��


��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��




3–158

chg_elementWorking Area

��

��

��"�� "��

��"�� "��

�� !�� !��

��

��"�� "��

�� !!�� !!��

�� !�� !��

��

��

��

��

�� !�� !��

��

��

��

��

��

��

��

��

��

��

��

��#�� #��

��

��

��



i

Chapter 4

Device/Function Equipage

ISSUE 11 REVISION 4



ii

ISSUE 11 REVISION 4



iii

Chapter 4Device/Function Equipage i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device/Function Equipage 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device and Function Dependency – In-Cell 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device and Function Dependency – M-Cell 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Kilo-Port Switch 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

KSW Extension/Expansion 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

KSW Configuration 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic Clock (GCLK) 4–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Site Processor (BSP) 4–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Code Storage Facility Processor (CSFP) 4–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base Transceiver Processor (BTP) 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital Host Processor 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic Processor Equipage 4–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage of GPROC Functions 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Transceiver Function (BTF) 4–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Link Control Function (LCF) 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Function (OMF) 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface 4–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface – In-Cell 4–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital Radio Interface – M-Cell 4–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy Group 4–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF Identifier 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell ID 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna Identity 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combiner Identity 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cavity Number 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity flag 4–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typical Examples 4–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote Tuneable Combiner (RTC) 4–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiport Serial Interface (MSI) 4–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-Cell 4–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell 4–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Path 4–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Path Equipage Exercise 4–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16 KBIT/S RSL 4–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RTF Types 4–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Receive Transmit Function (RTF) 4–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Signalling Link (RSL) 4–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Parameters 4–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Transfer Link (MTL) 4–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4



iv

Operations and Maintenance Link (OML) 4–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell Broadcast Link (CBL) 4–70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Equipage Exercise 4–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site Details 4–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ISSUE 11 REVISION 4 Device/Function Equipage



4–1

Device/Function Equipage

Objectives


� State and understand the dependency of one device on another device/function.

� Understand and implement the MMI involved with the equipping ofdevice/functions.

ISSUE 11 REVISION 4Device and Function Dependency – In-Cell



4–2

Device and Function Dependency – In-CellSome devices/functions are dependent upon other devices having already beenequipped to support them. For example, before a Receive Transmit Function (RTF) canbe equipped a Digital Radio Interface Extended Memory (DRIM) must be equipped tosupport it. The chart opposite shows the device and equipment hierarchy for non M-Cellsystems

ISSUE 11 REVISION 4 Device and Function Dependency – In-Cell



4–3

Device and Function Dependency – In-Cell

� �

��

��

��

��

��

��

��

�� !� ��

��

��

� ��!��

��!� ��

ISSUE 11 REVISION 4Device and Function Dependency – M-Cell



4–4

Device and Function Dependency – M-CellAs with In-Cell sites a logical order exists with respect to equipping devices and functionsin the CM. It is logical for example that an NIU be equipped before a path statement, asthe path statement will nominate certain NIUs for its traffic route. The chart oppositeshows the dependency chart in respect of M-Cell systems.

ISSUE 11 REVISION 4 Device and Function Dependency – M-Cell



4–5

Device and Function Dependency – M-Cell

��

��

��

��

��

� �� #�"��

�""!��#��

�� #�"��

��

��

ISSUE 11 REVISION 4Kilo-Port Switch



4–6

Kilo-Port SwitchTo equip a KSW/TSW the following command must be entered:

equip (site number) KSW

The site number identifies the site in which the KSW is to be equipped. Valid entries are0 (or BSC) to 50. This device cannot be equipped at an M-Cell site. After the initialcommand a series of identifiers must be added.

1st prompt (highway)

This prompt specifies which highway is being managed by this KSW/TSW. Highwaynumber 0 is conventionally used first. The system will not display this prompt forHorizonoffice BTS. Will automatically set this to ‘0’ for Horizonoffice BTS.

2nd prompt (identifier)

This figure specifies the unique first identifier of this KSW/TSW. If set to 0 the boardmust be fitted in card slot L27, if set to 1 the board should be fitted in card slot L1.

3rd prompt (cage)

This figure specifies the cage where the KSW has been fitted. The system willautomatically set this to 15 for Horizonoffice BTS. This prompt will not be displayed forHorizonoffice BTS.

4th prompt (DRIMs)

The highway can be optionally configured to serve DRIM cards by the use of this flag, if“yes” is entered then 352 highway timeslots are reserved for DRIM card service. Thesystem will set this value to ‘no’ for Horizonoffice BTS. The system will not display thisprompt for Horizonoffice BTS. This prompt will not appear for RXCDR sites.

ISSUE 11 REVISION 4 Kilo-Port Switch



4–7

KSW Equipage

��%)�$��'�(��")!��&��

� �"(�&�$#&(�#"�#��*�+�!�"��

� �"(�&�(��"(��&��#&��

� �"(�&�(��")!��&� ��

��

��

��

� ��'�� #*��#"��*�+�!�"��+�(��'��+�'�"#

ISSUE 11 REVISION 4KSW Extension/Expansion



4–8

KSW Extension/ExpansionAs the TDM highway function uses timeslot allocation, depending on the size of the siteone TDM highway may not be sufficient to support the digital boards or may be sufficientto support a number of cages.

A single KSW (1 TDM highway) can be extended to five digital cages although extensiondoes not increase the TDM Highway capacity. It is simply the sharing of the availabletimeslots over a number of digital cages.

In a large site 1 TDM highway may not be sufficient to meet the timeslot allocationrequirement of the digital boards. To overcome this the TDM highway can be expandedby interconnecting up to four KSWs. This would increase the number of timeslots from1024 to up to 4096 which is the maximum expansion configuration. When expandedeach KSW has access to any of the input ports of interconnected KSW but can onlyoutput to its own 1024 ports.

Extension and expansion is achieved by the use of Kiloport Switch Extender boards. Anadditional KSW can be equipped for redundancy, giving 4 KSW pairs when maximumexpansion is implemented.

ISSUE 11 REVISION 4 KSW Extension/Expansion



4–9

KSWX Configuration diagram showing extension andexpansion for 2 KSWs

��

� ��

�!� �� " ��

� � � � �

��

� ��

� � ��

�!� ��

" ��

��

�

��

��

��

�� "��

ISSUE 11 REVISION 4KSW Configuration



4–10

KSW Configuration

Overview

When maximum expansion is implemented at a site, four KSW pairs are required with fullredundancy.

Each active KSW has to be able to interface to each of the other three active KSWs viaKSWX EXP cards, as well as placing data onto its local highway. Shown opposite is aschematic diagram showing full expansion, the cards shown as A0, A1, and A2 areexpansion slot positions 21, 22, 23 of the upper shelf and are filled with KSWX cards.The interconnection between these cards is provided by optical fibre. Each of the fourhighways is provided by a single KSW, redundancy is not shown.

ISS

UE

11 RE

VIS

ION

4K

SW

Configuration

�M

OTO

RO

LA LT

D. 2000

SY

S02: B

SS

Database

FO

R T

RA

ININ

G P

UR

PO

SE

S O

NLY

4–11

KS

W E

xpansion

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4KSW Configuration



4–12

The chg_ksw_ config field is used to determine the Switch managers viewpoint of theKSW configuration, specifically the mapping of the TDM highway numbers for a particularKSW pair and is used to equip the Switch Managers database.

Each KSW pair must be informed which highway is being received on which KSWX (A0,A1 or A2) in the upper shelf. The following table is essential:

��

� � ��

� ��

� ��

� ��

Shown opposite is an example using the schematic on the previous page. Take KSWpair 2, physically in cage 3 of the site. H/W 0 is received on KSWX A0, using the table,gives a value of 1. H/W 1 is received on KSWX A1, using the table gives a value of 2.H/W 2 is not received by a KSWX card, the KSW in cage 3 is providing this highway,using the table gives a value of 0 H/W 3 is received on KSWX A2, using the table gives avalue of 3.

ISSUE 11 REVISION 4 KSW Configuration



4–13

KSW Configuration

��

��

��

��

��

��

ISSUE 11 REVISION 4Generic Clock (GCLK)



4–14

Generic Clock (GCLK)GCLKs are equipped on a site basis and its functionality can be extended to other cagesvia clock extender boards. One GCLK must be equipped per site and two if redundancyis to be implemented. This device may not be explicitly equipped at M-Cell sites, it isautomatically equipped with the first BTP. The command to equip an In-Cell GCLK is asfollows:

equip <site number> GCLK

Device ID

This field specifies the unique identifier for the GCLK, the card identified as 0 must befitted in card slot 5 and identifier 1 must be fitted in card slot 3.

Cage number

The parameter identifies the cage in which the GCLK is fitted.

CLKX prompts (In-cell sites only)

The three CLKX prompts are used to indicate whether GCLK extension is used at thissite, and if so which CLKXs support it. This is important, as slots U5, U6 and U7 cansupport either CLKX or KSWX cards, and if the same slot is specified for two cards thenthe CM must reject the equipage.

ISSUE 11 REVISION 4 Generic Clock (GCLK)



4–15

GCLK Equipage

�$(�#��&�'��!( ��%��

� �!'�%�'��)��!'��'�"!��"%�'��

� �!'�%�'��!( ��%��

� �&� ��&�"'��#%�&�!'��&�"%��"

� �&� ��&�"'��#%�&�!'��&�"%��"

� �&� ��&�"'��#%�&�!'��&�"%��"

ISSUE 11 REVISION 4Base Site Processor (BSP)



4–16

Base Site Processor (BSP)The BSP is the master processor type at a BSC and also at a RXCDR. Its functionalityis dependant upon the BSC type, at the smallest BSC it will carry out all processingrequired, then as the BSS grows in functionality certain software entities migrate awayfrom BSP and use other processor types which must be created. To equip a BSP thefollowing command must be used:

equip (site number) BSP


This prompt gives the BSP its unique identifier, a maximum of two BSPs can beequipped at any one site, the second being redundant.

2nd prompt (cage)

This identifies the cage in which the BSP is to be equipped.

3rd prompt (slot)

Valid card slots are 20/24 for a BSU cage and 25/26 for an RXU cage.

4th prompt (MTLs)

This field allows the FM to load MTLs onto the specified BSP. At a BSC or BSS(fm_site_type 0 or 1), when the bsc_type=1 this prompt will not appear, the MTPsoftware in these cases will appear in multiple instances on LCFs. At a BSC or BSSwhere the bsc_type=0 then this prompt will appear and must be answered with a one. Atan RXCDR, (fm_site_type=3), this prompt will not appear, after all a RXCDR will neverprocess an MTL.

ISSUE 11 REVISION 4 Base Site Processor (BSP)



4–17

Base Site Processor Equipage

��'+!&��%(��)� ��

� �$*�(�* ��!��$*!�!�(� ��

� �$*�(�* ��$+#��(� ��

� �$*�(�* ��)"%*�$+#��( ��

��

� �$*�(�* ��#�-!#+#��)�* !)��#�.�#�$��

�%$".��%(��#�)!*��*.&��%(��, �$��)��*.&��

ISSUE 11 REVISION 4Code Storage Facility Processor (CSFP)



4–18

Code Storage Facility Processor (CSFP)The Code Storage Facility Processor (CSFP) is a GPROC device which facilitates thepropagating of new software instances with reduced system downtime. A softwareinstance is a complete set of software and firmware objects including the databaseobject.

New software loads can be downloaded from OMC to BSC and consequently BSC toBTS, without a CSFP this download will result in system downtime whilst the BSC orBTS is in ROM utilising the IP. This system downtime is dependent on link throughput(number of OMLs) and system topology (number and connection of BTSs). If used, theCSFP will reduce this system down time as the download can take place to the BSC orBTS whilst the system is on-line and call processing.

After the software has been downloaded to all entities in the BSS a special BSS reset isperformed for the activation of the new software instance. Since the new softwareinstance exists locally, network outage time is drastically reduced.

The CSFP feature also provides optional CSFP fallback. As previously described a newsoftware instance is distributed to all CSFPs in a BSS. After the reset, all non-CSFPGPROCs begin executing the new software load, while the fallback CSFP retains the oldsoftware load.

At M-Cell sites, this device cannot be explicitly equipped. It is automatically equipped withthe first BTP.

To equip a CSFP the following command must be used:

equip (site number) CSFP

1st prompt (identification)

This parameter identifies the CSFP within site 0 only. At sites 1–50 the prompt will notappear.

2nd prompt (cage)

This field identifies the cage in which the GPROC acting as the CSFP has been fitted.

3rd prompt (slot)

This field identifies the cage slot position in which the GPROC acting as the CSFP hasbeen fitted.

ISSUE 11 REVISION 4 Code Storage Facility Processor (CSFP)



4–19

CSFP Equipage

��&* %��( )��#*"��'��

� �#)�'�)�� #) � �'� ��

�$#!+�%'$"%)��)�( )��

� �#)�'�)��#*"��'�

��

��

��

��

� �#)�'�)��(!$)�#*"��'� ��

��

ISSUE 11 REVISION 4Base Transceiver Processor (BTP)



4–20

Base Transceiver Processor (BTP)The BTP is the master processor at a BTS. Its load and functionality is dependant uponthe BTS type, at the smallest BTS it will carry out all the processing required. As moreprocessing power is required at a site software entities will appear in multiple instanceson other designated processors. To equip a BTP the following command must be used:

equip <site number> BTP

1st prompt (identifier/card frame)

This prompt gives the BTP its unique identifier, a maximum of two BTPs can be equippedat any one site, the second being redundant. In M-Cell products this prompt identifies thecard frame in which the MCU is being equipped. In the case of M-Cell this prompt mustbe answered 0 first in the CM. 0 is the valid entry for M-Cellmicro.

2nd prompt (cage)

This identifies the cage in which the BSP is to be equipped. Not prompted for M-Cellproducts.

3rd prompt (slot)

Valid slot ranges are 20/24 for cage 15 and 20 for cage 14. Not prompted for M-Cellproducts.

4th prompt (DRIMs)

This prompt specifies the maximum number of DRIMs that the CA will allow the BTP tosupport. Not prompted for M-Cell products.

Digital HostProcessor

The DHP will be required to support one instance of the RSS function at a BTS type 1.This device cannot be equipped at an M-Cell site.

equip <site number> DHP

1st prompt (cage)

This prompt acts as the 1st identifier for the DHP and defines the cage where the DHP isfitted. The system will automatically set this value to 15 for Horizonoffice BTS.

2nd prompt (identifier)

This prompt gives the DHP its unique identifier in the specified cage.

3rd prompt (slot)

Valid slot ranges are 18–25.

4th prompt (DRIMs)

This prompt specifies the maximum number of DRIMs that the CA will allow the DHP tosupport.

ISSUE 11 REVISION 4 Base Transceiver Processor (BTP)



4–21

Base Transceiver Processor (BTP)

��(,"'��*"+��%,$��)��

� �%+�)�+!��"��%+"�"�)�� %/��##�

��)��)�$��/��##�

� �%+�)�+!�� %,$��)��

� �%+�)�+!��*#&+�%,$��)��

��

� �%+�)�+!��$�-"$,$��*�*,''&)+��.�+!"*��

��

Digital Host Processor (DHP)

��(,"'��*"+��%,$��)��

� �%+�)�+!�� %,$��)��&)�+!"*��

� �%+�)�+!��,%"(,��%,$��)�"%�+!��

� �%+�)�+!��*#&+�%,$��)��

� �%+�)�+!��$�-"$,$�%,$��)�&��*�*,''&)+��.�+!"*��

ISSUE 11 REVISION 4Generic Processor Equipage



4–22

Generic Processor EquipageDepending on the site type certain software processes and functions will have to becreated to support the site functionality. When a function such as an LCF, OMF or BTFis to be equipped then a GPROC platform must be equipped in advance to support it. Inthe case of a processor such as a BSP or BTP the GPROC platform does not have to bepreviously equipped, see the dependency table at the beginning of this section. Thisdevice cannot be equipped at an M-Cell site.

To equip a GPROC the following command must be entered:

equip (site number) GPROC


This prompt specifies the unique identifier of the GPROC.

2nd prompt (cage)

This figure specifies the cage where the GPROC has been fitted. Automatically set to‘15’ for Horizonoffice BTS. This prompt will not appear for Horizonoffice BTS.

3rd prompt (slot)

This figure denotes the card slot location of the GPROC being equipped.

ISSUE 11 REVISION 4 Generic Processor Equipage



4–23

GPROC Equipage

��%)�$��'�(��")!��&��

� �"(�&�(��"(��&��

� �"(�&�(��")!��&��

��

��

��

��

� �"(�&�(��' #(�")!��&��

��

��

��

��

ISSUE 11 REVISION 4Equipage of GPROC Functions



4–24

Equipage of GPROC Functions

Base TransceiverFunction (BTF)

The main processor type at a BSC is the BSP and at a BTS is a BTP. As both processortypes are responsible for the main control of a site there is a lot of common functionalitybetween them.

If a site consists of standalone BSS then there is no requirements for both a BSP andBTP. A BSS consists of a colocated BSC and BTS. One major difference at a BSC isthat the KSW is dynamic and requires its own software process called the SwitchManager to control it. The Switch Manager must run on a BSP which will be the mainprocessor type at a standalone BSS.

However, what the BSP does not have is any RF functionality which is required at a BTS.A function is created called the BTF which will run on a equipped GPROC at a colocatedBSS.

To equip a BTF the following command must be used:

equip bsc BTF

prompt 1 (DRIMs)

This prompt specifies the maximum number of DRIMs that the CA will allow the BTF tosupport.

ISSUE 11 REVISION 4 Equipage of GPROC Functions



4–25

BTF Equipage

��

� ��!�� "��

ISSUE 11 REVISION 4Link Control Function (LCF)



4–26

Link Control Function (LCF)The BSC has interface signalling information to and from the MSC and BTS sites. In asmall BSS (BSC type 0) all the signalling can be processed by the BSP but as the size ofthe BSS increases the processing involved will become too much for the one processorand Link Control Processors (LCPs) are then necessary to take the load, for this reasonLCFs can only be equipped at BSC site type 1 or 2.

LCPs are assigned the LCF which is equipped in the database. As with the BTF it is notnecessary to specify a particular GPROC to be assigned the LCF. A GPROC has to beequipped at the site and functionality is distributed on initialisation. To equip an LCF thefollowing command must be used:

equip (Specify a DRI in a network from the OMC-R Navigation Tree).

unequip (Delete a DRI from a network at the OMC-R Navigation Tree).

prompt 1 (identifier)

This field specifies the LCF identification (0–24)

prompt 2 (MTLs)

This prompt specifies the maximum number of MTLs that the LCF can manage.

The value 2 can only be entered for a GPROC2.

prompt 3 (CBLs)

This field specifies the maximum number of Cell Broadcast Links (CBLs) that the LCFcan manage.

Operations andMaintenanceFunction (OMF)

This GPROC device can only be equipped at a BSC type 2. When a BSC type 2 isspecified it causes the software controlling both the XBL and OML to migrate to theavailable OMF. To equip an OMF the following command must be used:

equip (0 or bsc) OMF

(there are no prompts.)

ISSUE 11 REVISION 4 Link Control Function (LCF)



4–27

LCF Equipage

��&*�%��$'��(��

� �#)�'�)��*#�)�$#��#)��'��$'�)��

� �#)�'�)��#*"��'�$��(�)�� #�"�#��

��(�$#!,�+�!��$'��

� �#)�'�)��#*"��'�$�� !!��'$��()��# (�� (��)�� #�"�#��

OMF Equipage

��&*�%��$'��(��

��$�%'$"%)(��

ISSUE 11 REVISION 4Digital Radio Interface



4–28

Digital Radio InterfaceIn-Cell and M-Cell system hardware differs at the Digital Radio Interface. In-Cell systemsutilises the DRIM, DRIX and DRCU/SCU combination, whereas M-Cell utilises theTranceiver Control Unit (TCU) and possibly the FOX and FMUX. This difference isreflected in the equip dri command.

The DRIM provides the interface between the digital and RF domains. It performs thefollowing function:

1. Logical to physical channel mapping.

2. Interleaving/deinterleaving

3. channel coding/decoding

4. Base band hopping

5. Encryption function

6. Supports control/signalling between processor and DRCU

ISSUE 11 REVISION 4 Digital Radio Interface



4–29

Digital Radio Interface

� ��

� ��

� ��

� ��

� ��

� ��

ISSUE 11 REVISION 4Digital Radio Interface – In-Cell



4–30

Digital Radio Interface – In-Cell

Redundancy Group

Current software provides RTF\DRIM redundancy, in order for this feature to functioncorrectly DRIMs belonging to the same cell (connected to the same antenna) aregrouped together using this first identifier called the redundancy group. If an RTF isfunctioning on a DRIM\DRCU that goes faulty, it will automatically move to aDRIM\DRCU that is redundant (if present), this move will only take place if the firstidentifier (redundancy group) of the faulty DRIM\DRCU is the same as thespare\redundant DRIM\DRCU. This first identifier is also matched by that of the RTF. Ifit is the BCCH RTF that is functioning on a DRIM\DRCU that goes faulty, this RTF willmove to a DRIM\DRCU in the same redundancy group (unless the cell has only onecarrier) replacing a non-BCCH RTF if necessary. The second identifier uniquely identifiesthe DRIM within its redundancy group.

cabinet id

This field identifies the cabinet in which the DRIM is fitted. Range 0–15.

DRIM type

This field identifies the DRIM type in use. For an In-Cell system the only allowableresponse is 0 or the text string ‘drim’.

Cage

This identifies the cage in which the DRIM is fitted. This prompt is only presented in theDRI board type is DRIM.

slot

This field identifies the card slot number in which the DRIM is fitted. This prompt is onlypresented if the DRI board type is DRIM.

TRU id

This parameter is only necessary when equipping a DRIM in a Topcell Data Unit (TDU).It is optional and can be replaced by a carriage return or alternatively a zero, for non TDUcages. The range available is 0–6, to identify up to 6 TRU’s. This prompt will only bepresented if the DRI board type is DRIM. This prompt will only be presented if the DRIboard type is DRIM.

ISSUE 11 REVISION 4 Digital Radio Interface – In-Cell



4–31

DRIM Equipage

� �&* %��( )��#*"��'��

�#)�'�)��()��#��#��

�#)�'�)�� #�)� ��#) � �' ��

�#)�'�)��$�'��)+%� ��$'� #)��'��$��

�#)�'�)��#*"��' ��

��

�#)�'�)��(!$)�#*"��' ��

�#)�'�)�� #) � �' ��

Typical Arrangement

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

��

�

�

�

�

ISSUE 11 REVISION 4Digital Radio Interface In-Cell



4–32

Digital Radio Interface In-Cell

RTF Identifier

An RTF contains the frequency information for a particular cell and is equipped as afunction after the DRIM. This first part of the identifier determines which group of RTFsthat the DRIM must use to obtain its frequency information. A DRIM belonging to aparticular redundancy group will automatically use an RTF from the same group, andtherefore, this field is optional. The second part of the field completes the RTFidentification and identifies a particular RTF within a group of RTFs. RTFs are identifiedin an identical way to the DRIMs.

This prompt is optional and a value should only be added if equipment sharing (futurefeature) is implemented.

ISSUE 11 REVISION 4 Digital Radio Interface In-Cell



4–33

DRIM Equipage

� ��

��

� ��

� ��

ISSUE 11 REVISION 4Digital Radio Interface In-Cell



4–34

Cell id

This prompt requires the cell identity or the cell name that the DRIM is serving.

Ant id

This parameter is used to engage the correct bay level offset tables calibrated by thefield engineer when the radio was commissioned. These calibrations are usually storedin the 1st antenna memory area and hence this field is normally set to 1.

Combiner id

This optional parameter describes the RTC being used by the DRIM. The first part of theidentification specifies the unique identification of the RTC as previously equipped in thedatabase. The second part of the identification specifies the combiner processor in use.Each combiner has two processors (0 and 1), id 0 should always be specified at present,in current loads this has no effect.

Cavity Number

Only if the ‘Combiner id’ above has been entered will the MMI prompt for the cavitynumber. Each RTC has 5 cavities (0–4) clearly labelled in hardware. The cavity in useby this DRIM/DRCU should be entered in this field.

Diversity flag

This field specifies the use of diversity within the radio.

fm_cell_type

The field will nominate which receive coaxial connectors are in use in the diversitysummation. This feature is not supported at present.

Only certain combinations of the above two flags may be configured, they can be seen inthe table opposite.

When a DRCU is not in diversity mode the bottom connector (branch 1) should be usedas the coaxial input, fm_cell_type can be set to a 0, 1 or 2 in all cases the input to thisconnector will be processed.

ISSUE 11 REVISION 4 Digital Radio Interface In-Cell



4–35

DRIM Equipage

� �&+�)�+"��$$��."�)��+"��((��)* ��$$

��$$�&�%�

� �&+�)��&+�&&��*�$��+�&,%��)� ')�+"#*��$$ ��

� �&+�)��*+��&��&��#� ��

� �&+�)��-#+/�&,%��) ��

� �&+�)��#-�)*#+/� $�!� ')�+"#*��

��#-�)*#+/��#*��$��

��#-�)*#+/��&��$��

� �&+�)�+"�� %��$$�+/(�

��'&0�#-�)*#+/�%'��

��,$$��#-�)*#+/

�#-�)*#+/� $�! ��

� � � �

��

��

ISSUE 11 REVISION 4Digital Radio Interface – M-Cell



4–36

Digital Radio Interface – M-Cell

RedundancyGroup

Current software provides RTF/TCU redundancy, in order for this feature to functioncorrectly TCUs belonging to the same cell (connected to the same antenna) are groupedtogether using this first identifier called the redundancy group. If an RTF is functioningon a TCU that goes faulty, it will automatically move to a TCU that is redundant (ifpresent), this move will only take place if the first identifier (redundancy group) of thefaulty TCU is the same as the spare\redundant TCU. This first identifier is also matchedby that of the RTF. If it is the BCCH RTF that is functioning on a TCU that goes faulty,this RTF will move to a TCU in the same redundancy group (unless the cell has only onecarrier) replacing a non-BCCH RTF if necessary. The second identifier uniquely identifiesthe TCU within its redundancy group.

Cabinet id

This field identifies the cabinet in which the TCU is fitted. This entry will directly matchthat entered in the equip cabinet command.

FOX / FMUX connection

The response to this and the next prompt will specify the method of connection to theMCU. A number of alternatives exist for this field. The first, ‘fox ’ indicates that the TCUis connected via one of the fox ports in the master card frame (the one supporting theMCU). Three further alternatives exist to describe the fmux to fmux connection in thecase of a remoted cage. The fmux specified being the one in the master cage, thisdirectly correlates to the shelf map numbering. The last alternative is ‘direct ’, thisindicates that the TCU is connected to one of the ports on the MCU front panel. Textstrings or integer codes can be entered in response to this prompt. In the case of anM-Cellmicro, M-Cellcity, M-Cellarena this prompt should be answered with ‘direct ’ or 4.

FOX Port

The FOX card has 6 optical interfaces, each one being physically numbered on the frontpanel. The TCU being equipped may be connected to one of these ports, the number ofthe port is entered in this field. Again there is a direct correlation between the databaseentry and the front panel labelling. In an M-cell6 cabinet the TCU would normally beconnected to the FOX.

The port number entered here could also be referring to one of the 2 ports (0 and 1) onthe front panel of the MCU. For this to be the case the previous prompt must be enteredas ‘direct ’. For an M-cell micro TRX0 is referred to as port 0 and TRX1 is referred to asport 1.

ISSUE 11 REVISION 4 Digital Radio Interface – M-Cell



4–37

TCU Equipage

� �#'�"��%�&�� '��$��

� � &�$�&��%&��

� � &�$�&�� &�� &��$� ��

� � &�$�&��!�$��&!�(��&��%��! ��&��

��!$��!)

��!$��')�

��!$��')�

��!$��')�

�!$��$��&

� � &�$�&��"!$&�&!�(��&��%��! ��&��

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

TCU

��

��

��

��

��

��

��

��

��

�

� ��




4–38

RTF Identifier

An RTF contains the frequency information for a particular cell and is equipped as afunction after the DRIM. This first part of the identifier determines which group of RTFsthat the DRIM must use to obtain its frequency information. A DRIM belonging to aparticular redundancy group will automatically use an RTF from the same group, andtherefore, this field is optional. The second part of the field completes the RTFidentification and identifies a particular RTF within a group of RTFs. RTFs are identifiedin an identical way to the DRIMs.

This prompt is optional and a value should only be entered if equipment sharing (futurefeature) is implemented.

Cell ID

This prompt requires the cell identity or the cell name that the TCU is serving.

Antenna Identity

This enables two different mechanisms to correctly operate within the receiver RFsub-system. Firstly, this parameter points to the bay level offset antenna memory area tobe engaged by the TCU. These offsets will have been calibrated when the TCUhardware was initially commissioned.

The second use for this entry is only meaningful when an Integrated Antenna DistributionUnit (IADU) is in use (M-cell6). This entry points to the DLNB connection point on theIADU which is to be connected through to the TCU. The TCU will communicate thisparameter to the IADU for the correct switch to be enabled.

Shown opposite is a typical example of a 4/4/4 configuration. Given the antenna settingsat the bottom of the diagram, the internal switching of the IADU is shown. The thirdDiversity Low Noise Block (DLNB) port on the IADU can be used to extend the receivesignal to an IADU in a different cabinet, the internal IADU connections to make theextension port effective are enabled by dip switch settings on the IADU itself. Diversityconnections can be seen as ghosted lines in the diagram.




4–39

TCU Equipage

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

� �

�

�

�

�

�

�

�

�

�

�

� � � ��

�$)�$$��"��)��*#��'

� �$)�'�) ��()��$��$��!��

� �$)�'�) ��""�!��+ �'��) ��&&��'(� �""�!��""�$�#�

� �$)�'�) ��$)�$$��(�"��)�$*#��'�%��) !(��""��




4–40

CombinerIdentity

This optional parameter describes which TCB is in use by the specified TCU. The TCBnominated must be previously enabled in the CM (equip COMB ). The second part ofthis identification specifies the combiner processor to be used, although at present thisentry is meaningless and should be set to zero.

Cavity Number

Only if the combiner id (above) has been entered will the MMI prompt for the cavitynumber. Each CCB has 3 cavities, each being physically numbered from right to left(0–5), this field points to the cavity in use by this TCU.

Diversity flag

This field specifies the use of diversity within the radio.

fm cell type

The field will nominate which receive coaxial connectors are in use in the diversitysummation. This feature is not supported at present.

Only certain combinations of the above two flags may be configured, they can be seen inthe table opposite.

When a DRCU is not in diversity mode the bottom connector (branch 1) should be usedas the coaxial input, fm_cell_type can be set to a 0, 1 or 2 in all cases the input to thisconnector will be processed.




4–41

TCU Equipage

� ��#�!��"#��

� ��#�!��%�#&��$��!��

� ��#�!�#��%�!"�#&��!�#��"� ��

� ��#�!�#��#& ��

�%�!"�#&��

� � � �

��

��

ISSUE 11 REVISION 4Typical Examples



4–42

Typical Examples

In-cell with RTC In-cell without RTC

equip 12 dri equip 12 dri0 1 id 0 1 id0 cab 0 cabdrim type drim type15 cage 15 cage9 slot 9 slot<CR> TRU <CR> TRU<CR> RTF <CR> RTF2 3 4 1 0 368 39 cell 2 3 4 1 0 368 39 cell1 ant 1 ant0 0 comb <CR> comb1 cav 1 div1 div 4 cell type4 cell type

M-cell6 with CCB M-cell2 (without CCB)(standalone 6 carrier omni) (standalone 2 carrier omni)

equip 12 dri equip 12 dri0 1 id 0 1 id0 cab 0 cabfox FOX/FMUX 4 FOX/FMUX1 port 1 port<CR> RTF <CR> RTF2 3 4 1 0 368 39 cell 2 3 4 1 0 368 39 cell1 ant 1 ant0 0 comb <CR> comb1 cav 1 div1 div 4 cell type4 cell type

ISSUE 11 REVISION 4 Typical Examples



4–43

Typical DRI �+�!$ �'

�",��

��(�� (�#)(��

�%)�$�� %)�$��

��

� �

�&�! �&�!

��

� �

��

��

��

� �

��

� �

� �

�

�,�� *�(�� ,�� *�(�#)(��

�'(�"�,� #"��&&��&� �'(�"�,� #"��"�(�

�%)�$�� %)�$��

��

� �

�#+ �

� �

��

��

� �

��

� �

� �

�

ISSUE 11 REVISION 4Remote Tuneable Combiner (RTC)



4–44

Remote Tuneable Combiner (RTC)The RTC must be equipped before the DRIM card, in the case of In-Cell. Thisdependency is equally correct for M-Cell sites where the TCB must be equipped beforethe TCUs. The command is as follows:

equip<site number>COMB

prompt 1 (identifier)

This first prompt uniquely identifies the TCB within the site.

prompt 2 (address)

This field provides the TCB address, which must be equal to the hardware addressstraps on the TCB itself. Essentially all TCBs at the same site could have the sameaddress, the only use for this address is when one TCU is controlling two TCBs, this maybe the case in equipment sharing (a future feature).

prompt 3 (controlling DRIM)

All control and status messages for a TCB module will be passed via a TCU. This fieldspecifies the controlling TCU.

prompt 4 (standby DRIM)

For redundancy purposes a standby controlling TCU can be specified, although this fieldis optional.

This command should only be entered once per cabinet, even though two TCBs may befitted. A TCB is designed to control the tuning activities of up to 6 cavities (2 CCBs) Asecond TCB may be fitted but is merely redundant and acts as a hot standby. If twoTCBs are fitted into the same cabinet they should both be given the same physicaladdress.

ISSUE 11 REVISION 4 Remote Tuneable Combiner (RTC)



4–45

COMB Equipage

�� #��!�"��#��

� ��"� �� !"�� "��

� ��"� �� !! ��

� ��"� �"��" ��

� ��"� �!"��$��

��"��

ISSUE 11 REVISION 4Multiport Serial Interface (MSI)



4–46

Multiport Serial Interface (MSI)The equip command associated with an MSI can equip a number of 2Mb terminationmodules namely the MSI, XCDR, MSI2 and the NIU. Both the MSI and NIU modules arecapable of terminating 2 x 2Mb links, where as a XCDR performs the GSM TRAUfunction and can only terminate one E1 2Mb link. The MSI2 module is capable ofterminating either two E1 links or two T1 links. It can also be configured to terminate oneE1 (span A) and one T1 (span B), with E1 to T1 conversion within the module itself, thiswill be necessary in T1 systems as the XCDR module is exclusively E1. The MSI card isonly capable of terminating two E1 links, whereas the NIU is capable of terminating twoE1 links or two T1 links. chg_element land_layer1_mode is the database commandwhich will enable either a T1 or E1 network to function, it is written on a BSS basis, ie alltermination modules within the network will terminate in the same L1 mode.

The prompts associated with the equip MSI command are dependant upon the type ofsite, M-Cell or In-Cell.

In-Cell

Identifier

The field specifies a unique identifier on site basis

Cage

This prompt specifies the cage in which the termination card is fitted.

Slot

The field specifies the slot in which the module is fitted, restrictions exist depending upondefault positions and cage type (BSU and RXU)

Type

The field specifies the module type fitted, MSI, XCDR or E1/T1 converter.

Protocol type MMS 0

This prompt only appears if the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timslots supported on MMS 0

This prompt only appears is the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl and the protocol type is HDSL.

ISSUE 11 REVISION 4 Multiport Serial Interface (MSI)



4–47

MSI/XCDR Equipage

�*6�#((

#-1',��/'0#�*1) #.��

� �*0#.�0&#��'"#*0'$'#.� ��

��

��

� �*0#.�0&#�!�%#�*1) #.��

� �*0#.�0&#�/(+0�*1) #.�� /��

��04,#��

��04,#��

� �*0#.�0&#��04,#� ��

��

��

��)/'�#30�&"/(

��1*'0�

��+.'5+*��+*(4�

��)/'��!+*2

� �*0#.��,.+0+!+(�04,#� ��+.��

� �*0#.�*1) #.�+$�0')#/(+0/�

/1,,+.0#"�+*�� +.��

� �*0#.��,.+0+!+(�04,#� ��+.��

� �*0#.�*1) #.�+$�0')#/(+0/�

/1,,+.0#"�+*�� +.��

ISSUE 11 REVISION 4Multiport Serial Interface (MSI)



4–48

M-Cell

Identifier

Valid identifiers are dependent on site type, either M-Cell6/2 or M-Cellmicro/M-Cellcity.Only identifier 0 is valid at an M-Cellmicro/M-Cellcity.

Card frame

Two card frames exist in an M-Cell6 and an M-Cell2 and hence the identifies 0 and 1.Only identifier 0 is valid at an M-Cellmicro/M-Cellcity.

Slot

This field identifies the card slot in which the NIU is fitted. 0 is the only possible value forM-Cell2 and M-Cellmicro/M-Cellcity.

Type

This field states what type of module is used, NIU, NIU with integrated HDSL modem,NIU with external HDSL modem.

Protocol type MMS 0

This field only appears if the integrated M-Cell HDSL feature is enabled and the msi_typeis niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timeslots supported on MMS 0

This prompt only appears is the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Modem setting on MMS 0

This prompt only appears if the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl.

Protocol type MMS 1

This field only appears if the integrated M-Cell HDSL feature is enabled and the msi_typeis niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Timslots supported on MMS 1

This prompt only appears is the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl, niu_ext_hdsl or msi_ext_hdsl.

Modem setting on MMS 1

This prompt only appears if the integrated M-Cell HDSL feature is enabled and themsi_type is niu_hdsl.

��

��

��

��

��

��

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

�

� �

'�)!�'�4"-��(*!"�� '�)!�'�4"-��(*!"��

��

ISSUE 11 REVISION 4 Multiport Serial Interface (MSI)



4–49

MSI/XCDR Equipage�5�"''

",0&+��.&/"�)0(�"-��

� �)/"-�/%"��&!")/&#&"- ��5�"''�

��5�"''�

��5�"''��5�"''��

� �)/"-�/%"�� -!�#-�("�&)

2%& %�/%"��"3&./. ��

� �)/"-�/%"��.'*/�)0(�"- ��

� �)/"-�/%"��/4+" ��

�� )&0�"3/�%!.' �5�"''�

�� )&0 �5�"''�

�� )&0�%!.' �5�"''��

�� )&0�"3/�%!.' �5�"''��

� �)/"-��+-*/* *'�/4+" ��*-��

� �)/"-�)0(�"-�*#�/&(".'*/.�

.0++*-/"!�*)�� *-��

� �)/"-��(*!"(�."//&)$ ��./"-�*-�.'�1"

� �)/"-��+-*/* *'�/4+" ��*-��

� �)/"-�)0(�"-�*#�/&(".'*/.�

.0++*-/"!�*)�� *-��

� �)/"-��(*!"(�."//&)$ � ��./"-�*-�.'�1"

ISSUE 11 REVISION 4Path



4–50

PathThe specific transmission route which traffic and signalling will take from a BTS, perhapsvia intermediate BTSs, to the BSC is largely determined by the software. To enable thisto occur “Paths” have to be built using the available MSI cards and port numbers througheach BTS, starting from the BSC. The path command is very simple and is as follows:

equip 0 PATH

Prompt 1 (Terminating site ID)

This is the ID of the BTS site terminating the path.

Prompt 2 (Unique Path ID)

Each BTS site can have upto 10 unique paths, conventionally, numbering of paths startat 0.

Prompt 3 (BSC MSI ID)

This is the ID of the terminating MSI card and MMS port at the BSC.

Prompt 4 (Site ID)

This is the identity of the next BTS site in the chain.

If the aggregate A-bis feature is enabled the system will accept ts_switch as the site Id.If is ts_switch is used, the system will not prompt for upstream MSI, upstream MMS,downstream MSI and downstream MMS identifiers.

Prompt 5 (Upstream MSI ID)

This is the identity of the MSI card and MMS port at the first BTS in the chain, facingupstream towards the BSC.

Prompt 6 (Downstream MSI ID)

This is the identity of the MSI card and MMS port at the first BTS in the chain, facingdownstream towards the terminating site.

A path can proceed through a number of BTS sites before reaching its terminating BTS.To that end, the last three parameters are repeated for each intermediate site.

ISSUE 11 REVISION 4 Path



4–51

Path Equipage

�� !*.$)� ��(+��,��-#

�

� !'-!+�-#!�-!+&$'�-$'"��

� !'-!+�-#!�.'$*.!��

� !'-!+�-#!��(+��

� !'-!+�-#!��(+�-,�,/$-�#

� !'-!+�-#!�.),-+!�&��

��(+��

��

��(+��('��0�!%%�

��(+��0�!%%��

��(+��0�!%%��

��(+��0�!%%��$�+(�

� !'-!+�-#!� (/',-+!�&��

��(+��

��

��(+��('��0�!%%�

��(+��0�!%%��

��(+��0�!%%��

��(+��0�!%%��$�+(�

�!)!�-

ISSUE 11 REVISION 4Path Equipage Exercise



4–52

Path Equipage ExerciseThe diagram opposite contains the information necessary to equip 2 paths to BTS site16. Use the working area below to equip both paths, path 0 should be made theshortest.

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4 Path Equipage Exercise



4–53

Path Equipage Exercise

��

��

��

�

�

�

�

��

��

��

��

��

��

��

��

��

��

��

��

��

�

�

�

ISSUE 11 REVISION 416 KBIT/S RSL



4–54

16 KBIT/S RSLThe purpose of the 16 kbit/s RSL is to reduce the interconnection costs between theBSC and BTS (A-bis interface) for single carrier sites in particular.

At present, a single carrier BTS requires three E1/T1 64 kbit/s timeslots; one for the 64kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslotsdedicated to the traffic channels can accommodate eight traffic channels normally.

In the case of a single carrier site, it is not possible to use all eight traffic channels of thetwo 64 kbit/s timeslots. The reason is that, in the case of a single carrier site, the carrierwill be the BCCH carrier, and the air interface timeslot zero of the BCCH carrier isreserved for BCCH information. This information is generated at the BTS not the BSC.The TSW at the BTS routes the traffic channels from the two specified timeslots on theA-bis interface to the dedicated radio for transmission.

Due to this the traffic channel on the A-bis interface corresponding to the timeslot zero onthe air interface cannot be used because if it was, the information mapped from the A-bisinterface would interfere with the BCCH information. This results in one 16 kbit/ssub-channel unused on the A-bis interface, a waste of resources.

With the introduction of the 16 kbit/s RSL it is possible to place it on this unusedsub-channel because the RSL is not transmitting on the air interface. The advantage isthat it frees up one 64 kbit/s timeslot on the A-bis interface reducing the requirement toonly two 64 kbit/s timeslots. This operates with M-Cell BTSs and In-Cell BTSs usingKSW switching.

ISSUE 11 REVISION 4 16 KBIT/S RSL



4–55

Fully equipped RTF

NOASSOCIATED16 kbit/s RSL

ASSOCIATED16 kbit/s RSL

NON-BCCH

FULLY EQUIPPED RTF



BCCH

Timeslot X

Timeslot Y

��

Configuration 1 2 3 4

16 kbit/s sub-channel unavailable for use.16 kbit/s sub-channel used for 16 kbit/s RSL.16 kbit/s sub-channel available for voicetraffic.

16 kbit/sBTS only

16 kbit/sBTS only

ISSUE 11 REVISION 4RTF Types



4–56

RTF Types

�("� �"%�! $

� ��&��(��#&�""�� '�%�� $$!��%��%�$��

��&��(��#&�""�� '�%�� !��$$!��%��%�$��

��&��(��#&�""�� ! � �� '�%�� $$!��%��%�$��

��&��(��#&�""�� ! � �� '�%�� !��$$!��%��%�$��

��$&�)�#&�""�� '�%�� $$!��%��%�$��

��$&�)�#&�""�� '�%�� !��$$!��%��%�$��

��$&�)�#&�""�� ! ) �� '�%�� $$!��%��%�$��

��$&�)�#&�""�� ! ) �� '�%�� !��$$!��%��%�$��

�

�

�

�

�

ISSUE 11 REVISION 4 RTF Types



4–57

Sub-equipped RTF



NON-BCCH

SUB-EQUIPPED RTF



BCCH

Timeslot X

Timeslot Y

��

Configuration

16 kbit/s sub-channel used for 16 kbit/s RSL.16 kbit/s sub-channel available for voice traffic.

16 kbit/sBTS only

16 kbit/sBTS only

5 6 7 8

ISSUE 11 REVISION 4Receive Transmit Function (RTF)



4–58

Receive Transmit Function (RTF)A RTF is assigned to a DRIM/TCU, by the CA, providing it with the necessary RFchannel information.

Capacity of carrier

This field specifies whether the capacity of the RTF if full or sub. This prompt will notdisplay if the RTF is equipped to a BTS using dynamic allocation.

Carrier type

This field specifies whether this RTF supports a BCCH or non-BCCH carrier.

First and second identifier

An RTF is assigned to one of 6 redundancy groups (1st id). A BTS site is able to supportsix cells (each cell having its own allocated DRIMs and RTFs). An RTF is automaticallyassigned to a DRIM of the same redundancy group. This second identifier is used toidentify a particular RTF within a redundancy group.

Primary path

This field identifies which path is to be used for the 2 x 64kbs timeslots resulting from thisRTF. This prompt is only presented for RTFs at remote BTS sites. This prompt will notdisplay if the RTF is equipped to a BTS using dynamic allocation.

Optional prompts for 16 kbit RSL

Should the site employ a 16 kbit/s RSL, additional prompts will appear. This prompt willnot display if the RTF is equipped to a BTS using dynamic allocation.

Secondary path

This field identifies which optional secondary path will support the traffic from this RTF,should the primary path fail. This prompt is only presented for RTFs at remote BTS sites.This prompt will not display if the RTF is equipped to a BTS using dynamic allocation.

Cell id/name

An RTF is dedicated to a particular cell, this identity should be the same as thatnominated in the DRIM/TCU equippage for the same redundancy group.

Frequency

This field allocates the GSM radio channel number and therefore the downlink and uplinkfrequencies. The channels which maybe specified are as follows:

GSM 900 BCCH 1–124NON_BCCH 1–124

SM 900 (Extended) BCCH_ 1–124NON_BCCH 0, 1–124,

975–1023

DCS 1800 BCCH 512–885NON_BCCH 512–885

PCS 1900 BCCH 512–810NON_BCCH 512–810

ISSUE 11 REVISION 4 Receive Transmit Function (RTF)



4–59

RTF Equipage

��$/3(.��1(2$�,3+!$0��

� $,2$0�" . "(25�-%�" 00($0��-0��

� $,2$0�25.$�-%�" 00($0��!""'�-0�,-,�!""'

� $,2$0�2'$��12� ,#��,#��#��

� $,2$0�2'$�.0(+ 05�3,(/3$��#��

� $,2$0�2'$�-.2(-, *��,#�(#$,2(%($0�%-0�2'$� 11-"( 2$#

��

� $,2$0�2'$��,#�(#$,2(%($0�%-0�2'$� 11-"( 2$#��

� $,2$0�2'$�-.2(-, *�1$"-,# 05�3,(/3$��#��

� $,2$0�2'$��"$**�2-�4'("'�2'(1�" 00($0�(1� 11(&,$#�

"$**�(#�"$**�, +$

� $,2$0�" 00($0� !1-*32$�0 #(-�%0$/3$,"5�"' ,,$*�

��

��

��

��

�,*5�.0-+.2$#�%-0

1(2$�$/3(..$#�4(2'

��)!(2�1��

��-0(6-,��




4–60

Frequency Hopping Indicator (FHI)

This field is required for frequency hopping MS allocation per slot, Hopping SequenceNumber (HSN) and hopping mode form a frequency hopping system. It is then possibleto allocate a frequency hopping system on a carrier and timeslot basis. Each frequencyhopping system is allocated a Frequency Hopping Indicator (FHI). It is then possiblewhen equipping an RTF to allocate an FHI to each of the eight timeslots. All 8 FHIs areentered on a single line with one space separating each value. A value of 0–3 indicatesthe defined slot will hop using the specified hopping system. A value of 255 indicates thatthe slot will not hop. A value of 255 must be entered in the case of M-Cellmicro sites. Thedefault for this prompt is 255, but a restriction exists in that either no entry is made or all8 entries are made, nothing in between.

Training Sequence Code (TSC)

The TSC is a fixed pattern of 26 bits that forms the centre part of both normal anddummy bursts. It supports a number of functions:

1. Used for timing advance calculations

2. Used as a channel identifier

3. Used for equalisation purposes

The TSC is equipped on a TDMA timeslot basis. A GSM Recommendation (Rec 5.02)specifies that the TSC of timeslot 0 of the BCCH carrier should be equal to the BCC ofthe cell. All 8 TSCs are entered on a single line rather like the FHIs above.

KSW pair

All traffic channel data will be passed via the KSW in the BSS. The KSW will interfaceTraffic Channels (TCH) data being received from an MSI/XCDR and perform theinterchange function to route that data to the correct DRIM and TCH data received froma DRIM will be routed to an MSI/XCDR via the KSW. On an RTF basis the KSW pairassigned to support that RTF must be equipped. This parameter will not appear in thecase of M-Cell sites.

Cell zone

This prompt only appears for non-BCCH carriers and only if the concentric cells feature isunrestricted 0= Outer, 1 = Inner zone.




4–61

RTF Equipage

� ��

��

� ��

� ��

� ��




4–62

TRX transmit power reduction

This parameter is only prompted for non-BCCH carriers when concentric cells feature isenabled and the cell_zone=1. This element is only used by the BSS if the inner zonealgorithm is set to power_based.

Extended range

This prompt only appears if the extended range feature is unrestricted. The extendedrange timeslots maybe configured on outer zone carriers if the concentric cell feature isunrestricted. Extended range timeslots are not configurable for inner zone timeslots.

SDCCH load

This prompt specifies the maximum number of SDCCH/8 timeslots configurable percarrier. If Concentric Cells feature is unrestricted then the system displays this promptfor outer zone carriers (cell_zone= 0) only.

SDCCH placement priority

This prompt is used to specify the priority of a carrier in configuring SDCCHs. Theprompt only appears if sdcch_load is greater than zero.

Channel allocation priority

This prompt specifies the priority of a carrier when utilising the radio channel(SDCCH/TCH) allocation algorithm.The radio channel timeslot is allocated primarily oninterfer band. If two timeslots have the same interfer band, then the timeslot will beallocated based on its channel allocation priority.




4–63

RTF Equipage

� �"(�&�(&+�$#*�&�&��)�(�#" ��

��!

�!)'(��&��(�&�(��"�#& �

�%)� �(#�!�+�(+��('��

(��""�&�-#"��

��!

��

��'�$�&�!�(�&��'�#" , ��!

$&#!$(�� -#"��

�

�

��.��!

� �"(�&�(��")!��&�#�� ) (��

�+(�"��&�"��(�!�' #('

� #*��

� �"(�&�'�� #��

� �"(�&�'��$ ��!�"(�$&�#&�(, ��

��'(

�� #*�'(

� �"(�&��""� �� #��(�#"�$&�#&�(, ��

��'(

�� #*�'(

ISSUE 11 REVISION 4Radio Signalling Link (RSL)



4–64

Radio Signalling Link (RSL)The RSL is the LAPD 64 kbps timeslot between the BTS and BSC to support BSC–BTSsignalling.

First device ID

This identifies the site number associated with the RSL.

Second device ID

This identifies a particular RSL associated with the site.

Path ID

Identifies the unique path ID.

OptionalParameters

LAPD T200 timer

This is the maximum time the LAPD (Layer 2) transmitter will wait for anacknowledgement before making a retransmission.

LAPD N200

This is the maximum number of retransmissions a transmitter will make.

LAPD K

This is the maximum number of unacknowledged Information frames a transmitter willallow before holding up transmission.

ISSUE 11 REVISION 4 Radio Signalling Link (RSL)



4–65

RSL Equipage

� �'+!&��%(��

� �$*�(�* ��)*��,!��%(�* ��!*��

� �$*�(�* ��$��,!��%(�* ��

� �$*�(�* ��+$!'+��&�* ��

�&*!%$�"��(�#�*�()

� �$*�(�* �� *!#�(�,�"+��%(�* !)��,!��

�#)��,�"+�)�!$�#+"*!&"�)�%��

� �$*�(�* �� ,�"+��%(�* !)��,!��

� �$*�(�* �� ,�"+��%(�* !)��,!��

ISSUE 11 REVISION 4Message Transfer Link (MTL)



4–66

Message Transfer Link (MTL)The MTL is the 64 kbps PCM timeslot that is used to convey C7 Signalling informationbetween MSC and BSC.


Identifies a specific MTL associated with a site.

2nd prompt (MSI)

Specifies the first identifiers of the MSI/XCDR to which the MTL is associated.

3rd prompt (PORT)

Specifies the second identifier of MMS to which the MTL is associated ie the MSI/XCDRport.

4th prompt (timeslot)

Specifies which of the thirty two 64 kbps is to be assigned the MTL, conventionallytimeslot 16 is always used.

ISSUE 11 REVISION 4 Message Transfer Link (MTL)



4–67

MTL Equipage

��!�� !��

� � �� "��

� � ��

� � ��

� � �� #��

ISSUE 11 REVISION 4Operations and Maintenance Link (OML)



4–68

Operations and Maintenance Link (OML)The OML is the X.25 64 kbps timeslot between the BSC and OMC to support the remoteOperation and Maintenance function of the OMC.


Identifies a particular OML.

2nd prompt (MSI/XCDR)

Identifies the MSI/XCDR board supporting the OML. For initialisation purposes the OMLis defaulted to timeslot 1 of a port associated with an MSI in slot 16 or 14 of cage 0 or 16in cage 1.

3rd prompt (port)

Identifies a particular port on a XCDR/MSI board.


Identifies the 64 kbps timeslot to which the OML has been allocated.

ISSUE 11 REVISION 4 Operations and Maintenance Link (OML)



4–69

OML Equipage

�%)�$��'�(��")!��&��

� �"(�&�(��*��#&�(��

� �"(�&�(��&'(��'�&�$(�#"��#&�(��'��

��

� �"(�&�(��'��#"��'�&�$(�#"��#&�(��'��

� �"(�&�(�!�' #(�#"��+��&��(��'��*��$$��&'� ��

��

ISSUE 11 REVISION 4Cell Broadcast Link (CBL)



4–70

Cell Broadcast Link (CBL)This bi-directional data link, the CBL, will allow communications between the BSS andthe Cell Broadcast Centre (CBC). The link will activate an underlying connection with anX.25 network and establish a switch virtual circuit with the CBC. The CBC is responsiblefor downloading cell broadcast messages to the BSC, together with an indication of therepetition rate and the number of broadcasts per message. The BSC will in turn interpretthese messages and transmit each request to the appropriate BTSs.

The CBL feature is purchasable and will only support a single 64 kbs, non-redundant linkusing LAPB as the Layer 2 protocol. DTE addresses need to be configured via MMI inorder for the X.121 connection to be made. In addition to the X.121 address, operatornames must also be specified. These are included in t he N-connect message used toestablish the SVC and must be consistent at both ends. The device will reside upon thethe LCF for both type 1 and type 2 BSC sites. The link is not supported at a bsc type 0.

The CBL can be connected directly from the X.25 network into the BSC via a 2MB linkAlternatively it may be connected via a 64kbs cross connect in the RXCDR.

The database command and prompts necessary to configure a CBL are as follows:

equip 0/bsc CBL


Identifies the CBL, allows one of ID 0.

2nd prompt (MSI/XCDR)

Identifies the MSI/XCDR board supporting the CBL.

3rd prompt (port)

Identifies the MSI/XCDR port.


Identifies the 64kbs timeslot the CBL has been allocated.

5th prompt (BSS operator)

This field specifies the BSS operator’s name. This field must be entered between doublequotes.

6th prompt (CBC operator)

This field specifies the CBC operator’s name. This field must be entered between doublequotes.

ISSUE 11 REVISION 4 Cell Broadcast Link (CBL)



4–71

Cell Broadcast Link

��

��

��

� �

��

��

�%)�$��'��

� �"(�&�(��*��#&�(��

� �"(�&�(��&'(��"(��&��#&�(��'��*��

� �"(�&�(��'��#"��"(��&��#&�(��'��*��

� �"(�&�(��(�!�' #(�#"��+��&��(��'��*��$$��&'� ��

��

� �"(�&�(�� #$�&�(#&��,��&��(�&'�

� �"(�&�(�� #$�&�(#&��,��&��(�&'�

ISSUE 11 REVISION 4Equipage Exercise



4–72

Equipage ExerciseUsing the following information and answer sheets provided, fill in the necessary detailsto equip each function and device.

Site Details

1. This BTS site supports 2 cells and is a BTS site type 1.

2. There are two paths equipped to the site 0 and 1, 0 being the primary path for alltraffic and signalling.

3. The RSL used is full 64 kbit/s

4. No hopping is performed at the site.

5. All equipment identities follow convention.

6. The following information is necessary when equipping an RSL

LapD T200 timer= 2500N200 timer= 3k value=7

ISSUE 11 REVISION 4 Equipage Exercise



4–73

Equipage Exercise

��

��"$��!��&�#$�%'� "��

��

��$� %� �$�"%��

�� ##��#

��

��

��

��( ��

��

��"$��!��&�#$�%'� "��

��

��$� %� �$�"%��

��##��#

�

�

�

�

�

�

�

�

�

�

�

�

ISSUE 11 REVISION 4Equipage Exercise



4–74

ISSUE 11 REVISION 4 Equipage Exercise



4–75

SITE 12 BSU

































��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏ

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ







�� #%��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

� �

� �

� �

��

��

��

� �

� �

��

� �

��

��

��

&$!%"

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��


�� #%��


�� #%��

��

ÏÏÏÏÏÏÏÏÏ

��

ISSUE 11 REVISION 4



4–76

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



4–77

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



4–78

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



4–79

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



4–80

ISSUE 11 REVISION 4



Glos–i

Glossary of Terms

ISSUE 11 REVISION 4Numbers



Glos–ii

Numbers# Number.

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

4GL Fourth Generation Language.

— A —A interface Interface between MSC and BSS.

A3 Authentication algorithm that produces SRES, using RAND and Ki.

A5 Stream cipher algorithm, residing on an MS, that produces ciphertext outof plaintext, using Kc.

A8 Ciphering key generating algorithm that produces Kc using RAND and Ki.

AB Access Burst.

AB Alarm Board (generic term refering to both AB2 and AB6).

A-bis interface Interface between BSC and BTS. Motorola offers a GSM standard and a unique Motorola A-bis interface. The Motorola interface reduces the amount of message traffic and thus the number of 2 Mbit/s lines requiredbetween BSC and BTS.

ABR Answer Bid Ratio.

AC Access Class (C0 to C15).

AC Application Context.

AC Alternating Current

ACC Automatic Congestion Control.

ACCH Associated Control Channel.

ACK ACKnowledgement.

ACM Address Complete Message.

ACSE Associated Control Service Element.

ACU Antenna Combining Unit.

A/D Analogue to Digital (converter).

ADCCP Advanced Communications Control Protocol.

ADM ADMinistration processor.

ADMIN ADMINistration.

ADN Abbreviated Dialling Number.

ADPCM Adaptive Differential Pulse Coded Modulation.

AE Application Entity.

ISSUE 11 REVISION 4 — A —



Glos–iii

AEF Additional Elementary Functions.

AFC Automatic Frequency Control.

AFN Absolute Frame Number.

AGC Automatic Gain Control.

AGCH Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH.

Ai Action indicator.

AI Artificial Intelligence.

AIB Alarm Interface Board.

Air interface The radio link between the BTS and the MS.

ALT Accelerated Life Testing

AM Amplitude Modulation.

AMA Automatic Message Accounting (processor).

AM/MP Cell broadcast MS terminated message. A message broadcast to all MS’s in a cell.

ANSI American National Standards Institute.

AOC Automatic Output Control.

AP Application Process.

APSM AC Power Supply Module

ARFCN Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number.

ARQ Automatic ReQuest for retransmission.

ARP Address Resolution Protocol.

ASCE Association Control Service Element. An ASE which provides an AP withthe means to establish and control an association with an AP in a remoteNE. Maps directly onto the Presentation layer (OMC).

ASE Application Service Element (OMC)

ASE Application Specific Entity (TCAP).

ASN.1 Abstract Syntax Notation One.

ASP Alarm and Status Panel.

ASR Answer Seizure Ratio.

ATB All Trunks Busy.

ATI Antenna Transceiver interface.

ATT (flag) Attach.

ATTS Automatic Trunk Testing Subsystem.

AU Access Unit.

AUC AUthentication Centre. A GSM network entity which provides the functionality for verifying the identity of an MS when requested by the system. Often a part of the HLR.

AUT(H) Authentication.

AUTO AUTOmatic mode.

ISSUE 11 REVISION 4— B —



Glos–iv

— B —BA BCCH Allocation. The radio frequency channels allocated in a cell for

BCCH transmission.

BBH Base Band Hopping.

BCC BTS Colour Code.

BCCH Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis.

BCD Binary Coded Decimal.

BCF Base station Control Function. The GSM term for the digital control circuitry which controls the BTS. In Motorola cell sites this is a normally a BCU which includes DRI modules and is located in the BTS cabinet.

BCIE Bearer Capability Information Element.

BCU Base station Control Unit. A functional entity of the BSS which provides the base control function at a BTS site. The term no longer applies to a type of shelf (see BSC and BSU).

BER Bit Error Ratio. A measure of signal quality in the GSM system.

BES Business Exchange Services.

BFI Bad Frame Indication.

BHCA Busy Hour Call Attempt.

BIB Balanced-line Interconnect Board. Provides interface to 12 balanced (6-pair) 120-ohm (37-pin D-type connector) lines for 2 Mbit/s circuits (See also T43).

BLLNG BiLLiNG.

bit/s Bits per second (bps).

Bm Traffic Channel (full rate).

BN Bit Number. Number which identifies the position of a particular bit periodwithin a timeslot.

BPF Bandpass Filter.

BPSM BCU Power Supply Module.

BRI Basic Rate Interface.

BS Basic Service (group).

BS Bearer Service. A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. The PLMN connection type used to support a bearer service may be identical to that used to support other types of telecommunication service.

BSC Base Station Controller. A network component in the GSM PLMN which has the digital control function of controlling all BTSs. The BSC can be located within a single BTS cabinet (forming a BSS) but is more often located remotely and controls several BTSs (see BCF, BCU, and BSU).

BSG Basic Service Group.

ISSUE 11 REVISION 4 — C —



Glos–v

BSIC Base Tranceiver Station Identity Code. A block of code, consisting of the GSM PLMN colour code and a base station colour code. One Base Station can have several Base Station Colour Codes.

BSIC-NCELL BSIC of an adjacent cell.

BSP Base Site control Processor.

BSS Base Station System. The system of base station equipment (tranceivers, controllers and so on) which is viewed by the MSC through a single interface as defined by the GSM 08 series of recommendations, as being the entity responsible for communicating with MSs in a certain area. The radio equipment of a BSS may cover one or more cells. A BSS may consist of one or more base stations. If an internal interface is implemented according to the GSM 08.5x series of recommendations, then the BSS consists of one BSC and several BTSs.

BSSAP BSS Application Part (of signalling system No. 7) (DTAP + BSSMAP).

BSSC Base Station System Control cabinet. The cabinet which houses one or two BSU shelves at a BSC or one or two RXU shelves at a remote transcoder.

BSSMAP Base Station System Management Application Part.

BSSOMAP BSS Operation and Maintenance Application Part (of signalling system No. 7).

BSU Base Station Unit shelf. The shelf which houses the digital control modules for the BTS (p/o BTS cabinet) or BSC (p/o BSSC cabinet).

BT British Telecom

BT Bus Terminator.

BTC Bus Terminator Card.

BTCU Backwards Compatible Transceiver Control Unit

BTP Base Transceiver Processor

BTS Base Transceiver Station. A network component in the GSM PLMN which serves one cell, and is controlled by a BSC. The BTS contains oneor more Tranceivers (TRXs).

Burst A period of modulated carrier less than one timeslot. The physical content of a timeslot.

— C —C7 CCITT Signalling System #7 (SS7).

CA Cell Allocation. The radio frequency channels allocated to a particular cell.

CA Central Authority.

CAI Charge Advice Information.

CB Circuit Breaker.

CBC Cell Broadcast Centre.

CBCH Cell Broadcast CHannel.

ISSUE 11 REVISION 4— C —



Glos–vi

CBF Combined Bandpass Filter.

CBL Cell Broadcast Link

CBSMS Cell Broadcast Short Message Service.

CC Country Code.

CC Call Control.

CCB Cavity Combining Block.

CCCH Common Control Channels. A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH.

CCCH_GROUP Group of MSs in idle mode.

CCD Common Channel Distributor.

CCDSP Channel Coding Digital Signal Processor.

CCF Conditional Call Forwarding.

CCH Control channel. Control channels are channels which carry system management messages.

CCH Council for Communications Harmonization (referred to in GSM Recommendations).

CCITT Comité Consultatif International Télégraphique et Téléphonique.

CCPE Control Channel Protocol Entity.

CCS Hundred call-seconds. The unit in which amounts of telephone trafficare measured. A single call lasting one hundred seconds is oneCCS. See also erlang.

Cct Circuit.

CCU Channel Coder Unit.

CDB Control Driver Board.

CDR Call Detail Records.

CEB Control Equalizer Board (BTS).

Cell By GSM definition, a cell is an RF coverage area. At an omni-site,cell is synonymous with site; at a sectored site, cell is synonymouswith sector. This differs from analogue systems where cell is taken tomean the same thing as site. (See Figure 1).

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4 — C —



Glos–vii

Definition of GSM cell, sector, and site

CEPT Conférence des administrations Européén des Postes et Télécommunications.

CF Conversion Facility.

CF All Call Forwarding services.

CFC Conditional Call Forward.

Channel A means of one-way transmission. A defined sequence of periods (for example, timeslots) in a TDMA system; a defined frequency band in an FDMA system; a defined sequence of periods and frequency bands in a frequency hopped system.

CHV Card Holder Verification.

CKSN Ciphering Key Sequence Number.

C/I, CIR Carrier to Interference ratio.

CI Cell Identity. A block of code which identifies a cell within a location area.

CI CUG Index.

Ciphertext Unintelligible data produced through the use of encipherment.

CKSN Ciphering Key Sequence Number.

CLI Calling Line Identity.

CLK Clock.

CLKX Clock Extender half size board. The fibre optic link that distributes GCLKto boards in system (p/o BSS etc).

CLM Connectionless Manager.

CLR CLeaR.

CPSM Comms Power Supply Module.

CM Configuration Management. An OMC application.

CM Connection Management.

CMD Command.

CMM Channel Mode Modify.

CMIP Common Management Information Protocol.

CMISE Common Management Information Service Element. An ASE which provides a means to transfer management information via CMIP messages with another NE over an association established by ASCE using ROSE (OMC).

CMR Cellular Manual Revision.

CODEX Manufacturer’s name for a type of multiplexer and packet switch commonly installed at the Motorola OMC-R.

COM Code Object Manager.

COM Complete.

ISSUE 11 REVISION 4— D —



Glos–viii

COMM, comms COMMunications.

CONF CONFerence circuit.

CONFIG CONFIGuration Control Program.

CP Call Processing.

CPU Central Processing Unit.

C/R Command/Response field bit.

CR Carriage Return (RETURN).

CRC Cyclic Redundancy Check (3 bit).

CRE Call RE-establishment procedure.

CRM Cell Resource Machine/Manager.

CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed modem usedto interwork 300 to 2400 bit/s data services under V.22bis, V.23, or V.21 standards. High speed modem used to interwork 1200 to 9600 bit/s data services under V.22bis, V.32, or V.29/V.27ter/V.21 standards.

CRT Cathode Ray Tube (video display terminal).

CSFP Code Storage Facility Processor.

CSP Central Statistics Process. The statistics process in the BSC.

CSPDN Circuit Switched Public Data Network.

CT Channel Tester.

CUG Closed User Group supplementary service.

— D —D/A Digital to Analogue (converter).

DAN Digital Announcer (for recorded announcements on MSC).

DAS Data Acquisition System.

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 Channels. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and

SACCH.

DCE Data Circuit terminating Equipment.

DCF Data Communications Function.

ISSUE 11 REVISION 4 — D —



Glos–ix

DCN Data Communications Network. A DCN connects Network Elements withinternal mediation functions or mediation devices to the Operations Systems.

DCS Digital Communication/Cellular System. A non-GSM cellular phone network using digital techniques similar to those used in GSM but operating on different frequencies.

DDS Direct Digital Synthesis.

DEQB Diversity Equalizer Board.

DET Detach.

DFE Decision Feedback Equalizer.

DHP Digital Host Processor.

DIA Drum Intercept Announcer.

DIQ Diversity In phase and Quadrature phase.

DIR Device Interface Routine.

DISC DISConnect.

DL Data Link (layer).

DLCI Data Link Connection Identifier.

DLD Data Link Discriminator.

DLNB Diversity Low Noise Block.

DLSP Data Link Service Process

Dm Control Channel (ISDN terminology applied to mobile service).

DMA Deferred Maintenance Alarm. An alarm report level; an immediate or deferred response is required (see also PMA).

DMA Direct Memory Access

DMX Distributed Electronic Mobile Exchange (Motorola’s networked EMX family).

DN Directory Number.

DNIC Data Network Identifier.

Downlink Physical link from the BTS towards the MS (BTS transmits, MS receives).

DP Dial/Dialled Pulse.

DPC Destination Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) destination point of the message.

DPC Digital Processing and Control.

DPNSS Digital Private Network Signalling System (BT standard for PABX interface).

DPP Dual path preselector.

DPSM Digital Power Supply Module.

ISSUE 11 REVISION 4— E —



Glos–x

DRAM Dynamic Random Access Memory.

DRC Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF).

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

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

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

DRIM Digital Radio Interface extended Memory. A DRI with extra memory.

DRIX DRI Extender half size board. Fibre optic link from DRI to BCU (p/oBSS).

DRX, DRx Discontinuous Reception. A means of saving battery power (for example in hand-portable units) by periodically and automatically switching the MS receiver on and off.

DS-2 German term for 2 Mbit/s line (PCM interface).

DSE Data Switching Exchange.

DSP Digital Signal Processor.

DSS1 Digital Subscriber Signalling No 1.

DSSI Diversity Signal Strength Indication.

DTAP Direct Transfer Application Part.

DTE Data Terminal Equipment.

DTF Digital Trunk Frame.

DTI Digital Trunk Interface.

DTMF Dual Tone Multi-Frequency (tone signalling type).

DTX, DTx Discontinuous Transmission. A means of saving battery power (for example in hand-portable units) and reducing interference by automatically switching the transmitter off when no speech or data are tobe sent.

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

— E —E See Erlang.

E1 CEPT 2.048 Mbit/s-1 standard 32 timeslot link.

EA External Alarms.

EAS External Alarm System.

Eb/No Energy per Bit/Noise floor.

ISSUE 11 REVISION 4 — E —



Glos–xi

EBSG Elementary Basic Service Group.

EC Echo Canceller.

EC European Commission.

ECB Provides echo cancelling for telephone trunks for 30 channels (EC).

ECID The Motorola European Cellular Infrastructure Division.

ECM Error Correction Mode (facsimile).

Ec/No Ratio of energy per modulating bit to the noise spectral density.

EEPROM Electrically Erasable Programmable Read Only Memory.

EGSM Extended GSM.

EGSM Extened Global System for Mobile Communications.

EIR Equipment Identity Register.

EIRP Effective Isotropic Radiated Power.

EIRP Equipment Identity Register Procedure.

EM Event Management. An OMC application.

EMC Electro Magnetic Compatibility.

EMF Electro Motive Force.

EMI Electro Magnetic Interference.

EMX Electronic Mobile Exchange (Motorola’s MSC family).

EN European Norm(e)

en bloc Fr. — all at once (a CCITT #7 Digital Transmission scheme); En bloc sending means that digits are sent from one system to another ~ (that is,all the digits for a given call are sent at the same time as a group). ~ sending is the opposite of overlap sending. A system using ~ sending will wait until it has collected all the digits for a given call before it attempts to send digits to the next system. All the digits are then sent asa group.

EOT End of Tape.

Erlang International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 ccs. In the US this is also known as a traffic unit (TU).

EPROM Erasable Programmable Read Only Memory.

EPSM Exhancec power supply module.

EQB Equalizer Board. Control circuit for equalization for 8 time slots each withequalizing circuitry and a DSP (p/o RCU).

EQ DSP Equalizer Digitizer Signal Processor.

ERP Effective Radiated Power.

ESP Electro-static Point.

ESQL Embedded SQL (Structured Query Language). An RDBMS programming

ISSUE 11 REVISION 4— F —



Glos–xii

interface language.

E-TACS Extended TACS (analogue cellular system, extended).

ETR ETSI Technical Report.

ETS European Telecommunication Standard.

ETSI European Telecommunications Standards Institute.

ETX End of Transmission.

EU European Union.

EXEC Executive Process.

— F —FA Fax Adaptor.

FA Full Allocation.

FA Functional Area.

FAC Final Assembly Mode.

FACCH Fast Associated Control Channel. A GSM dedicated control channel which is associated with a TCH and carries control information after a call is set up (see SDCCH).

FACCH/F Full rate Fast Associated Control Channel.

FACCH/H Half rate Fast Associated Control Channel.

FB Frequency correction Burst (see Frequency correction burst).

FCCH Frequency Correction Channel. A GSM broadcast control channel which carries information for frequency correction of the mobile (MS).

FCP Fault Collection Process (in BTS).

FCS Frame Check Sequence.

FD Full Rate Data.

FDMA Frequency Division Multiple Access.

FEC Forward Error Correction.

FEP Front End Processor.

FER Frame Erasure Ratio.

FFS, FS For Further Study.

FHI Frequency Hopping Indicator.

FIR Finite Impulse Response (filter type).

FK Foreign Key. A database column attribute; the foreign key indicates an index into another table.

FM Fault Management (at OMC).

FM Frequency Modulation.

FMUX Fibre Multiplexer Board.

FN Frame Number. Identifies the position of a particular TDMA frame within a hyperframe.

FOA First Office Application.

FPCU Fan power conversion unit.

FOX Fibre Optic Extender board

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

ISSUE 11 REVISION 4 — F —



Glos–xiii

Frequency Period of RF carrier less than one timeslot whose modulation bit streamcorrection allows frequency correction to be performed easily within an MS.burst

FRU Field replacement unit.

FS Frequency Synchronization.

FS Full rate speech.

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

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

FTP Fault Translation Process (in BTS).

FTP File Transfer Program

FW Firmware.

ISSUE 11 REVISION 4— G —



Glos–xiv

— G —Gateway MSC An MSC that provides an entry point into the GSM PLMN from another

network or service. A gateway MSC is also an interrogating node for incoming PLMN calls.

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

GF Ground fixed.

GHz Giga-Hertz (109).

GMB GSM Multiplexer Board (p/o BSC).

GMR GSM Manual Revision.

GMSC Gateway Mobile services Switching Centre (see Gateway MSC).

GMSK Gaussian Minimum Shift Keying. The modulation technique used inGSM.

GND Ground

GOS Grade of Service.

GPA GSM PLMN Area.

GPC General Protocol Converter.

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

GPS Global Positioning by Satellite.

GSA GSM Service Area. The area in which an MS can be reached by a fixed subscriber, without the subscriber’s knowledge of the location of the MS. A GSA may include the areas served by several GSM PLMNs.

GSA GSM System Area. The group of GSM PLMN areas accessible by GSM MS’s.

GSM Groupe Spécial Mobile (the committee).

GSM Global System for Mobile communications (the system).

GT Global Title.

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

GUI Graphical User Interface.

GWY GateWaY (MSC/LR) interface to PSTN.

ISSUE 11 REVISION 4 — H —



Glos–xv

— H —H-M “Human-Machine” Terminals.

HAD, HAP HLR Authentication Distributor.

Handover The action of switching a call in progress from one radio channel to another radio channel. Handover allows established calls to continue by switching them to another radio resource, as when an MS moves from one BTS area to another. Handovers may take place between the following GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.

HDLC High level Data Link Controller.

HDSL High bit rate Digital Subscriber Line.

HLC High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal.

HLR Home Location Register. The LR where the current location and all subscriber parameters of an MS are permanently stored.

HMS Heat Management System. The system that provides environmental control of the components inside the ExCell cabinet.

HO HandOver. The action of switching a call in progress from one radio channel to another radio channel. Handover allows established calls to continue by switching them to another radio resource, for example, whenMS’s move from one base station area to another.

HPU Hand Portable Unit.

HR Half Rate. Refers to a type of data channel that will double the current GSM air interface capacity to 16 simultaneous calls per carrier (see also FR – Full Rate).

HS HandSet.

HSM HLR Subscriber Management.

HSN Hopping Sequence Number.

HW Hardware.

Hyperframe 2048 superframes. The longest recurrent time period of the frame structure.

ISSUE 11 REVISION 4— I —



Glos–xvi

— I —I Information (frames).

IA5 International Alphanumeric 5.

IADU Integrated Antenna Distribution Unit.

IAM Initial Address Message.

IAS Internal Alarm System.

IC Integrated Circuit.

IC Interlock Code (closed user group supplementary service).

ICB Incoming Calls Barred.

ICM In-Call Modification.

ICMP Internet Control Message Protocol.

ID, id Identification/Identity.

IDN Integrated Digital Network.

IE Signalling Information Element.

IEC Internet electrotechnical commission.

IEEE Institute of Electrical and Electronic Engineers.

IEI Information Element Identifier.

IF Intermediate Frequency.

IFAM Initial and Final Address Message.

IM InterModulation.

IMACS Intelligent Monitor And Control System.

IMEI International Mobile station Equipment Identity. Electronic serial number that uniquely identifies the MS as a piece or assembly of equipment. TheIMEI is sent by the MS along with request for service.

IMM IMMediate assignment message.

IMSI International Mobile Subscriber Identity. Published mobile number (prior to ISDN) (see also MSISDN) that uniquely identifies the subscription. It can serve as a key to derive subscriber information such as directory number(s) from the HLR.

IN Intelligent Network.

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

INS IN Service.

INS Intelligent Network Service.

Interworking The general term used to describe the inter-operation of networks, services, supplementary services and so on. See also IWF.

I/O Input/Output.

ISSUE 11 REVISION 4 — K —



Glos–xvii

IP Initialisation Process.

IP Internet Protocol.

IPC Inter-Process Communication.

IP, INP INtermodulation Products.

IPR Intellectual Property.

IPSM Integrated PSM.

ISC International Switching Centre.

ISDN Integrated Services Digital Network. An integrated services network that provides digital connections between user-network interfaces.

ISO International Standards Organisation.

ISQL Informix Structured Query Language.

ISUP ISDN User Part (of signalling system No. 7).

ITC Information Transfer Capability.

ITU International telecommunication union

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

IWMSC InterWorking MSC.

IWU InterWorking Unit.

— K —k kilo (103).

K Constraint length of the convolutional code.

Kb Kilo-bit.

kbit/s, kbps kilo-bit per second.

Kc Ciphering key. A sequence of symbols that controls the operation of encipherment and decipherment.

kHz kilo-Hertz (103).

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

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

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

kW kilo-Watt.

ISSUE 11 REVISION 4— L —



Glos–xviii

— L —L1 Layer 1.

L2ML Layer 2 Management Link.

L2R Layer 2 Relay function. A function of an MS and IWF that adapts a user’s known layer2 protocol LAPB onto RLP for transmission between the MT and IWF.

L2R BOP L2R Bit Orientated Protocol.

L2R COP L2R Character Orientated Protocol.

L3 Layer 3.

LA Location Area. An area in which an MS may move freely without updating the location register. An LA may comprise one or several base station areas.

LAC Location Area Code.

LAI Location Area Identification (identity). The information indicating the location area in which a cell is located.

LAN Local Area Network.

LANX LAN Extender half size board. Fibre optic distribution of LAN to/from other cabinets (p/o BSS etc).

LAPB Link Access Procedure “B” (balanced) channel (of CCITT Rec. X.25).

LAPD Link Access Procedure “D” (data) channel.

LAPDm Link Access Procedure “Dm” (mobile “D”) channel.

LC Inductor Capacitor (type of filter).

LCF Link Control Function.

LCP Link Control Processor.

LE Local Exchange.

LED Light Emitting Diode.

LF Line Feed.

LI Length Indicator.

LI Line Identity.

LLC Lower Layer Compatibility. The LLC can carry information defining the lower layer characteristics of the terminal.

Lm Traffic channel (half rate).

LMS Least Mean Square.

LMSI Local Mobile Station Identity. A unique identity temporarily allocated to visiting mobile subscribers in order to speed up the search for subscriberdata in the VLR, when the MSRN allocation is done on a per cell basis.

Location area An area in which a mobile station may move freely without updating the location register. A location area may comprise one or several base station areas.

ISSUE 11 REVISION 4 — M —



Glos–xix

LPC Linear Predictive Code.

LR Location Register. The GSM functional unit where MS location information is stored. The HLR and VLR are location registers.

LTA Long Term Average. The value required in a BTS’s GCLK frequency register to produce a 16.384 Mhz clock.

LTE Local Terminal Emulator.

LTP Long Term Predictive.

LTU Line terminating unit.

LV Length and Value.

LVD Low voltage disconnect.

— M —M Mega (106).

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

MA Mobile Allocation. The radio frequency channels allocated to an MS for use in its frequency hopping sequence.

MAC Medium Access Control.

MACN Mobile Allocation Channel Number.

MAF Mobile Additional Function.

MAI Mobile Allocation Index.

MAIDT Mean Accumulated Intrinsic Down Time.

MAINT MAINTenance.

MAIO Mobile Allocation Index Offset.

MAP Mobile Application Part (of signalling system No. 7). The inter-networkingsignalling between MSCs and LRs and EIRs.

MAPP Mobile Application Part Processor.

MCAP Motorola Cellular Advanced Processor.

MCC Mobile Country Code.

MCU Main control unit.

MCU-m Main control unit micro (used in M-cellmicro)

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

ME Maintenance Entity (GSM Rec. 12.00).

ISSUE 11 REVISION 4— M —



Glos–xx

ME Mobile Equipment. Equipment intended to access a set of GSM PLMN and/or DCS telecommunication services, but which does not contain subscriber related information. Services may be accessed while the equipment, capable of surface movement within the GSM system area, is in motion or during halts at unspecified points.

MEF Maintenance Entity Function (GSM Rec. 12.00).

MF MultiFrame.

MF Multi-Frequency (tone signalling type)

MF MultiFunction block.

MGMT Management.

MGR Manager.

MHS Message Handling System.

MHS Mobile Handling Service.

MHz Mega-Hertz (106).

MI Maintenance Information.

MIB Management Information Base. A Motorola OMC-R database. There is aCM MIB and an EM MIB.

MIC Mobile Interface Controller.

MIT Management Information Tree. Name of a file on the Motorola OMC-R.

MM Mobility Management.

MME Mobile Management Entity.

MMI Man Machine Interface. The method in which the user interfaces with thesoftware to request a function or change parameters.

MML Man Machine Language. The tool of MMI.

MMS Multiple Serial Interface Link.

MNC Mobile Network Code.

MNT MaiNTenance.

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

MPX MultiPleXed.

MRN Mobile Roaming Number.

MS Mobile Station. The GSM subscriber unit.

MSC Mobile services Switching Centre.

ISSUE 11 REVISION 4 — N —



Glos–xxi

MSCM Mobile Station Class Mark.

MSCU Mobile Station Control Unit.

msec millisecond (.001 second).

MSI Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS).

MSIN Mobile Station Identification Number.

MSISDN Mobile Station International ISDN Number. Published mobile number (see also IMSI). Uniquely defines the mobile station as an ISDN terminal.It consists of three parts: the Country Code (CC), the National Destination Code (NDC) and the Subscriber Number (SN).

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

MSU Message Signal Unit. A signal unit containing a service information octet and a signalling information field which is retransmitted by the signalling link control, if it is received in error.

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

MT (0,1,2) Mobile Termination. The part of the MS which terminates the radio transmission to and from the network and adapts terminal equipment (TE) capabilities to those of the radio transmission. MT0 is mobile termination with no support for terminal, MT1 is mobile termination with support for an S-type interface and MT2 is mobile termination with support for an R-type interface.

MTM Mobile-To-Mobile (call).

MTP Message Transfer Part.

MT/PP Mobile Terminated Point-to-Point messages.

MTBF Mean Time Between Failures.

MTL Message Transfer Link.

MTL MTP Transport Layer Link (A-Interface).

MTP Message Transfer Part.

MTTR Mean Time To Repair.

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

MUMS Multi User Mobile Station.

MUX Multiplexer.

— N —NB Normal Burst (see Normal burst).

NCC Network (PLMN) Colour Code.

NCELL Neighbouring (or current serving) Cell.

ISSUE 11 REVISION 4— N —



Glos–xxii

ND No Duplicates. A database column attribute meaning the column contains unique values (used only with indexed columns).

NDC National Destination Code.

NDUB Network Determined User Busy.

NE Network Element (Network Entity).

NEF Network Element Function block.

NF Network Function.

NI Network Interface.

NIC Network Independent Clocking.

NIU Network interface unit.

NLK Network LinK processor(s).

Nm Newton metres.

NM Network Management (manager). NM is all activities which control, monitor and record the use and the performance of resources of a telecommunications network in order to provide telecommunication services to customers/users at a certain level of quality.

NMASE Network management application service element.

NMC Network Management Centre. The NMC node of the GSM TMN providesglobal and centralised GSM PLMN monitoring and control, by being at the top of the TMN hierarchy and linked to subordinate OMC nodes.

NMSI National Mobile Station Identification number.

NMT Nordic Mobile Telephone system.

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

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

NPI Number Plan Identifier.

NPSM Negative power supply module.

NRZ Non Return to Zero.

NSAP Network Service Access Point.

NSP Network Service Provider.

NT Network Termination.

NT Non Transparent.

NTU Network terminating unit.

NUA Network User Access.

NUI Network User Identification.

NUP National User Part (of signalling system No. 7).

NVRAM Non-Volatile Random Access Memory.

nW Nano-Watt (10–9).

N/W NetWork

ISSUE 11 REVISION 4 — O —



Glos–xxiii

— O —O&M Operations and Maintenance.

OACSU Off-Air Call SetUp. The procedure in which a telecommunication connection is being established whilst the RF link between the MS and the BTS is not occupied.

OCB Outgoing Calls Barred within the closed user group.

OFL % OverFlow.

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

OMC Operations and Maintenance Centre. The OMC node of the GSM TMN provides dynamic O&M monitoring and control of the PLMN nodes operating in the geographical area controlled by the specific OMC.

OMCR Operations and Maintenance Centre — Radio Part.

OMCS Operations and Maintenance Centre — Switch Part.

OML Operations and Maintenance Link.

OMP Operation and Maintenance Processor.

OMS Operation and Maintenance System (BSC–OMC).

OMSS Operation and Maintenance SubSystem.

OOS Out Of Service.

OPC Originating Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) origination point of the message.

ORAC Olympus radio architecture control board (part of TCU-m)

OS Operating System.

OSI Open Systems Interconnection

OSF Operation Systems Function block.

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

OSS Operator Services System.

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

ISSUE 11 REVISION 4— P —



Glos–xxiv

— P —PA Power Amplifier.

PAB Power Alarm Board.

PABX Private Automatic Branch eXchange.

PAD Packet Assembler/Disassembler facility.

Paging The procedure by which a GSM PLMN fixed infrastructure attempts to reach an MS within its location area, before any other network-initiated procedure can take place.

PATH CEPT 2 Mbit/s route through the BSS network.

PBX Private Branch eXchange.

PC Personal Computer.

PC Power converter

PCH Paging CHannel. A GSM common control channel used to send paging messages to the MSs.

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

PCMCIA Personal computer memory card industry association (PC cards).

PCN Personal Communications Network.

PCR Preventative Cyclic Retransmission. A form of error correction suitable for use on links with long transmission delays, such as satellite links.

PCU Power converter unit.

PCS Personal communications system.

pd Potential difference.

PD Protocol Discriminator.

PD Public Data.

PDB Power Distribution Board.

PDF Power Distribution Frame (MSC/LR).

PDN Packet Data Network.

PDU Power Distribution Unit

PDU Protected Data Unit.

PEDC Pan European Digital Cellular.

PH Packet Handler.

PH PHysical (layer).

PHI Packet Handler Interface.

PID Process IDentifier.

PI Presentation Indicator.

PIM PCM Interface Module (MSC).

ISSUE 11 REVISION 4 — P —



Glos–xxv

PIN Personal Identification Number.

PIX Parallel Interface Extender half size board. Customer alarm interface (p/o BSS).

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

Plaintext Unciphered data

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

PLMN Public Land Mobile Network. The mobile communications network.

PM Performance Management. An OMC application.

PM-UI Performance Management User Interface.

PMA Prompt Maintenance Alarm. An alarm report level; immediate action is necessary (see also DMA).

PMS Pseudo MMS.

PMUX PCM MUltipleXer.

PN Permanent Nucleus (of GSM).

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.

ppm Parts per million (x 10–6).

PPS Pulses per second.

PPSM Positive power supply module.

PRI Primary rate interface.

PROM Programmable Read Only Memory.

PSAP Presentation Services Access Point.

PSM Power supply module

PSPDN Public Switched Packet Data Network. Public data communications network. X.25 links required for NE to OMC communications will probably be carried by PSPDN.

PSTN Public Switched Telephone Network. The UK landline telephone network.

PSU Power supply unit.

PSW Pure Sine Wave.

PTO Public Telecommunications Operator.

PVC Permanent Virtual Circuit.

PWR Power.

PXPDN Private eXchange Packet Data Network.

ISSUE 11 REVISION 4— Q —



Glos–xxvi

— Q —Q-adapter Used to connect MEs and SEs to TMN (GSM Rec. 12.00).

QAF Q-Adapter Function Block.

QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to TDM switchhighway (see MSI).

QOS Quality Of Service.

— R —RAB Random Access Burst.

RACCH Random Access Control CHannel. A GSM common control channel used to originate a call or respond to a page.

RACH Random Access CHannel.

RAM Random Access Memory.

RAND RANDom number.

RAx Rate Adaptation.

RBCU Remote BTS control unit.

RBDS Remote BSS Diagnostic System (a discontinued Motorola diagnostic facility).

RBER Residual Bit Error Ratio.

RBTS Remote Base Tranceiver Station

RCB Radio Control Board (p/o DRCU).

RCI Radio Channel Interface

RCP Radio Control Processor.

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

RCVR Receiver.

RDBMS Relational Database Management System.

RDB Requirements database.

RDN Relative Distinguished Name. A series of RDN form a unique identifier, the distinguished name, for a particular network element.

REC, Rec. RECommendation.

REL RELease.

RELP Residual Excited Linear Predictive.

RELP-LTP RELP Long Term Prediction. A name for GSM full rate (see full rate).

REQ REQuest.

RES Radio equipment and systems

RF Radio Frequency.

ISSUE 11 REVISION 4 — R —



Glos–xxvii

RFC, RFCH Radio Frequency Channel. A partition of the system RF spectrum allocation with a defined bandwidth and centre frequency.

RFE Receiver Front End (shelf).

RFEB Receiver Front End Board (p/o DRCU II).

RFI Radio Frequency Interference.

RFN Reduced TDMA Frame Number.

RISC Reduced Instruction Set Computer.

RLP Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22.

rms Root Mean Square (value).

RMSU Remote Mobile Switching Unit.

ROM Read Only Memory.

ROSE Remote Operations Service Element. An ASE which carries a message between devices over an association established by ASCE (a CCITT specification for O & M) (OMC).

Roundtrip Time period between transmit and receive instant of a timeslot in the propagation BTS, determined by the response behaviour of the MS and the MS to delay BTS distance.

RPE Regular Pulse Excited.

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

RPR Read Privilege Required. Access to the column is allowed only for privileged accounts.

RR Radio Resource management.

RR Receive Ready (frame).

RRSM Radio Resource State Machine.

RSE Radio System Entity.

RSL Radio Signalling Link.

RSLF Radio System Link Function.

RSS Radio SubSystem (replaced by BSS).

RSSI Received Signal Strength Indication.

RTC Remotely Tuneable Channel Combiner.

RTE Remote Terminal Emulator.

RU Rack Unit.

Rx Receive(r).

RXCDR Remote Transcoder.

RXLEV-D Received signal level downlink.

RXLEV-U Received signal level uplink.

RXQUAL-D Received signal quality downlink.

RXQUAL-U Received signal quality uplink.

RXU Remote Transcoder Unit. The shelf which houses the remote transcodermodules in a BSSC cabinet at a remote transcoder site.

ISSUE 11 REVISION 4— S —



Glos–xxviii

— S —SABM Set Asynchronous Balanced Mode. A message which establishes the

signalling link over the air interface.

SACCH Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements.

SAGE A brand of trunk test equipment.

SAP Service Access Point. In the reference model for OSI, SAPs of a layer are defined as gates through which services are offered to an adjacent higher layer.

SAP System Audits Process.

SAPI Service Access Point Indicator (identifier).

SAW Surface Acoustic Wave.

SB Synchronization Burst (see Synchronization burst).

SC Service Centre (used for Short Message Service).

SC Service Code.

SCCA System Change Control Administration. Software module which allows full or partial software download to the NE (OMC).

SCCP Signalling Connection Control Part.

SCEG Speech Coding Experts Group (of GSM).

SCH Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations.

SCI Status Control Interface.

SCIP Serial Communication Interface Processor.

SCM Status Control Manager.

SCN Sub-Channel Number. One of the parameters defining a particular physical channel in a BS.

SCP Service Control Point (an intelligent network entity).

SCU Slim carrier unit.

SDCCH Stand-alone Dedicated Control CHannel. A GSM control channel where the majority of call setup occurs. Used for MS to BTS communications before MS assigned to TCH.

SDH Synchronous digital hierarchy.

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

SE Support Entity (GSM Rec. 12.00).

SEF Support Entity Function (GSM Rec.12.00).

SFH Slow Frequency Hopping.

SFRAS System feature requirements and architecture specification.

SI Screening Indicator.

ISSUE 11 REVISION 4 — S —



Glos–xxix

SI Service Interworking.

SID SIlence Descriptor.

SIF Signal Information Field. The bits of a message signal unit that carry information for a certain user transaction; the SIF always contains a label.

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

SIO Service Information Octet. Eight bits contained in a message signal unit, comprising the service indicator and sub-service field.

SITE BSC, BTS or collocated BSC-BTS site.

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

SK Secondary Key. A database column attribute, the secondary key indicates an additional index and/or usage as a composite key.

SLNK Serial Link.

SLTM Signalling Link Test Message.

SM Switch Manager.

SMAE System Management Application Entity (CCITT Q795, ISO 9596).

SME Short Message Entity.

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.

SN Subscriber Number.

SND SeND.

SNDR SeNDeR.

SNR Serial Number.

SOA Suppress Outgoing Access.

SP Service Provider. The organisation through which the subscriber obtains GSM telecommunications services. This may be a network operator or possibly a separate body.

SP Signalling Point.

SP Special Product.

SPC Signalling Point Code.

SPC Suppress Preferential (closed user group).

ISSUE 11 REVISION 4— S —



Glos–xxx

SPI Signalling Point Inaccessible.

SQL Structured Query Language.

SRD Service Request Distributor.

SRES Signed RESponse (authentication).

SS7, SS#7 CCITT Signalling System No. 7 (alias C7).

SS Supplementary Service. A modification of, or a supplement to, a basic telecommunication service.

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

SSC Supplementary Service Control string.

SSF Subservice Field. The level 3 field containing the network indicator and two spare bits.

SSM SCCP State Machine.

SSP Service Switching Point (an intelligent network element).

SSP SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18).

SSS Switching SubSystem (comprising the MSC and the LRs)

STAN Statistical ANalysis (processor).

STAT STATistics.

stats Statistics.

STC System Timing Controller.

STP Signalling Transfer Point.

Superframe 51 traffic/associated control multiframes or 26 broadcast/common controlmultiframes (period 6.12s).

SVC Switch Virtual Circuit.

SVM SerVice Manager.

SW Software.

SWFM SoftWare Fault Management.

SynchronizationPeriod of RF carrier less than one timeslot whose modulation bit streamburst carries information for the MS to synchronize its frame to that of the

received signal.

SYS SYStem.

SYSGEN SYStem GENeration. the Motorola procedure for loading a configuration database into a BTS.

ISSUE 11 REVISION 4 — T —



Glos–xxxi

— T —T1 ANSI 1.555 Mbit/s standard 24 timeslot link.

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

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

TA Timing Advance.

TAC Type Approval Code.

TACS Total Access Communications System (European analogue cellular system).

TAF Terminal Adaptation Function.

TATI Transmit antenna transceiver interface.

TBD To Be Determined.

TC Transaction Capabilities.

TC shelf Transmit combiner shelf.

TCAP Transaction Capabilities Application Part (of signalling system No. 7).

TCH Traffic CHannel. GSM logical channels which carry either encoded speech or user data. A Traffic channel can be one of the following: TCH/F (full rate TCH), TCH/F2.4 (full rate TCH at < 2.4kbit/s), TCH/F4.8 (full rate TCH at 4.8kbit/s), TCH/F9.6 (full rate TCH at 9.6kbit/s), TCH/FS(full rate speech TCH), TCH/H (half rate TCH), TCH/H2.4 (half rate TCH at 2.4kbit/s), TCH/H4.8 (half rate TCH at 4.8kbit/s) or TCH/HS (half rate speech TCH).

TCI Tranceiver Control Interface.

TCP/IP Transmission Control Protocol/Internet Protocol.

TCU Transceiver control unit.

TCU-m Transceiver control unit micro (combination of ORAC and RF boards).

TDM Time Division Multiplexing.

TDMA Time Division Multiple Access.

TDU Topcell Data Unit

TE Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user.

Tei Terminal endpoint identifier.

TEI Terminal Equipment Identity.

TEMP TEMPorary.

TEST TEST control processor.

TFA Transfer Allowed.

TFP Transfer Prohibited.

TFTP Trivial File Transfer Protocol.

ISSUE 11 REVISION 4— T —



Glos–xxxii

TI Transaction Identifier.

Timeslot The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots.

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

TM Traffic Manager.

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

TMM Traffic Metering and Measuring.

TMN Telecommunications Management Network. The implementation of the Network Management functionality required for the PLMN is in terms of physical entities which together constitute the TMN.

TMSI Temporary Mobile Subscriber Identity. A unique identity temporarily allocated by the MSC to a visiting mobile subscriber to process a call. May be changed between calls and even during a call, to preserve subscriber confidentiality.

TN Timeslot Number.

Traffic Channels which carry users’ speech or data (see also TCH).channels

Traffic unit Equivalent to an erlang.

Training Sequence of modulating bits employed to facilitate timing recovery sequence and channel equalisation in the receiver.

TRAU Transcoder Rate Adaption Unit.

TRX TRansceiver(s). A network component which can serve full duplex communication on 8 full-rate traffic channels according to specification GSM 05.02. If Slow Frequency Hopping (SFH) is not used, then the TRXserves the communication on one RF carrier.

TS Telecommunications standard.

TS Teleservice.

TS TimeSlot (see Timeslot).

TSA TimeSlot Acquisition.

TSDA Tranceiver Speech & Data Interface.

TSC Training Sequence Code.

TSI Time Slot Interchange.

TSM Transceiver station manager board (part of TCV).

TTL Transistor to Transistor Logic.

TTY TeleTYpe (refers to any terminal).

TU Traffic Unit.

TUP Telephone User Part (of signalling system No. 7).

Tx Transmit(ter)

ISSUE 11 REVISION 4 — U —



Glos–xxxiii

— U —

�S micro-second (10–6).

UA Unnumbered Acknowledgment. A message sent from the MS to the BSSto acknowledge release of radio resources when a call is being cleared.

UDP User Datagram Protocol.

UDUB User Determined User Busy.

UHF Ultra High Frequency.

UI Unnumbered Information frame.

Um Air interface (User part modified).

UMTS Universal Mobile Telecommunication System.

UPD Up to Date.

Uplink Physical link from the MS towards the BTS (MS transmits, BTS receives).

Useful part of That part of the burst used by the demodulator; differs from the full burstburst because of the � bit shift of the I and Q parts of the GMSK signal.

USSD Unstructured SS Data.

— V —VA Vitirbi Algorithm (used in channel equalizers).

VAD Voice Activity Detection. A process used to identify presence or absenceof speech data bits. VAD is used with DTX.

VCO Voltage Controlled Oscillator.

VLR Visitor Location Register. A GSM network element which provides a temporary register for subscriber information for a visiting subscriber. Often a part of the MSC.

VLSI Very Large Scale Integration (in ICs).

VOX Voice Operated Transmission.

VSP Vehicular Speaker Phone.

VSWR Voltage Standing Wave Ratio.

— W —WPA Wrong Password Attempts (counter).

WS Work Station. The remote device via which O&M personnel execute input and output transactions for network management purposes.

WSF Work Station Function block.

ISSUE 11 REVISION 4— X —



Glos–xxxiv

— X —X.25 CCITT specification and protocols for public packet-switched networks

(see PSPDN).

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

XBL Transcoder to BSS Link. The communications link between the Transcoder (XCDR) and the BSS.

XCB Tranceiver Control Board (p/o tranceiver).

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

XID Exchange Identifier.

ISSUE 11 REVISION 4



App A–i

Appendix A

GSM Channel Frequency Table

ISSUE 11 REVISION 4



App A–ii

��

��

123456789

10111213141516171819202122232425262728293031323334353637383940

0102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F202122232425262728

890.20890.40890.60890.80891.00891.20891.40891.60891.80892.00892.20892.40892.60892.80893.00893.20893.40893.60893.80894.00894.20894.40894.60894.80895.00895.20895.40895.60895.80896.00896.20896.40896.60896.80897.00897.20897.40897.60897.80898.00

935.20935.40935.60935.80936.00936.20936.40936.60936.80937.00937.20937.40937.60937.80938.00938.20938.40938.60938.80939.00939.20939.40939.60939.80940.00940.20940.40940.60940.80941.00941.20941.40941.60941.80942.00942.20942.40942.60942.80943.00

ISSUE 11 REVISION 4



App A–iii

��

��

41424344454647484950515253545556575859606162636465666768697071727374757677787980

292A2B2C2D2E2F303132333435363738393A3B3C3D3E3F404142434445464748494A4B4C4D4E4F50

898.20898.40898.60898.80899.00899.20899.40899.60899.80900.00900.20900.40900.60900.80901.00901.20901.40901.60901.80902.00902.20902.40902.60902.80903.00903.20903.40903.60903.80904.00904.20904.40904.60904.80905.00905.20905.40905.60905.80906.00

943.20943.40943.60943.80944.00944.20944.40944.60944.80945.00945.20945.40945.60945.80946.00946.20946.40946.60946.80947.00947.20947.40947.60947.80948.00948.20948.40948.60948.80949.00949.20949.40949.60949.80950.00950.20950.40950.60950.80951.00

ISSUE 11 REVISION 4



App A–iv

��

��

81828384858687888990919293949596979899

100101102103104105106207208109110111112113114115116117118119120121122123124

5152535455565758595A5B5C5D5E5F606162636465666768696A6B6C6D6E6F707172737475767778797A7B7C

906.20906.40906.60906.80907.00907.20907.40907.60907.80908.00908.20908.40908.60908.80909.00909.20909.40909.60909.80910.00910.20910.40910.60910.80911.00911.20911.40911.60911.80912.00912.20912.40912.60912.80913.00913.20913.40913.60913.80914.00914.20914.40914.60914.80

951.20951.40951.60951.80952.00952.20952.40952.60952.80953.00953.20953.40953.60953.80954.00954.20954.40954.60954.80955.00955.20955.40955.60955.80956.00956.20956.40956.60956.80957.00957.20957.40957.60957.80958.00958.20958.40958.60958.80959.00959.20959.40959.60959.80

ISSUE 11 REVISION 4



App B–i

Appendix B

Hexadecimal/Decimal Conversion Chart

ISSUE 11 REVISION 4



App B–ii

Channel Channel Channel

Hexadecimal�� Hexadecimal�� Hexadecimal��

1 12 23 34 45 56 67 78 89 910 A11 B12 C13 D14 E15 F16 1017 1118 1219 1320 1421 1522 1623 1724 1825 1926 1A27 1B28 1C29 1D30 1E31 1F32 2033 2134 2235 2336 2437 2538 2639 2740 2841 2942 2A43 2B44 2C45 2D46 2E47 2F48 3049 3150 3251 3352 3453 3554 3655 37

56 3857 3958 3A59 3B60 3C61 3D62 3E63 3F64 4065 4166 4267 4368 4469 4570 4671 4772 4873 4974 4A75 4B76 4C77 4D78 4E79 4F80 5081 5182 5283 5384 5485 5586 5687 5788 5889 5990 5A91 5B92 5C93 5D94 5E95 5F96 6097 6198 6299 63100 64101 65102 66103 67104 68105 69106 6A107 6B108 6C109 6D110 6E

111 6F112 70113 71114 72115 73116 74117 75118 76119 77120 78121 79122 7A123 7B124 7C125 7D126 7E127 7F128 80129 81130 82131 83132 84133 85134 86135 87136 88137 89138 8A139 8B140 8C141 8D142 8E143 8F144 90145 91146 92147 93148 94149 95150 96151 97152 98153 99154 9A155 9B156 9C157 9D158 9E159 9F160 A0161 A1162 A2163 A3164 A4165 A5

ISSUE 11 REVISION 4



App B–iii

Channel Channel Channel

Hexadecimal�� Hexadecimal�� Hexadecimal��

166 A6167 A7168 A8169 A9170 AA171 AB172 AC173 AD174 AE175 AF176 B0177 B1178 B2179 B3180 B4181 B5182 B6183 B7184 B8185 B9186 BA

226 E2227 E3228 E4229 E5230 E6231 E7232 E8233 E9234 EA235 EB236 EC237 ED238 EE239 EF240 F0241 F1242 F2243 F3244 F4245 F5246 F6247 F7248 F8249 F9250 FA251 FB252 FC253 FD254 FE255 FF

187 BB188 BC189 BD190 BE191 BF192 C0193 C1194 C2195 C3

196 C4197 C5198 C6199 C7200 C8201 C9202 CA203 CB204 CC205 CD206 CE207 CF208 D0209 D1210 D2211 D3212 D4213 D5214 D6215 D7216 D8217 D9218 DA219 DB220 DC221 DD222 DE223 DF224 E0225 E1

ISSUE 11 REVISION 4



App B–iv

ISSUE 11 REVISION 4



App C–i

Appendix C

SACCH Multiframes

ISSUE 11 REVISION 4



App C–ii

Several parameters in the BSS database are configured in multiples of SACCHmultiframes. This Appendix provides the user with conversion between SACCHmultiframes and seconds for one’s better understanding.

Note: SACCHs may be associated with either traffic channels (TCH) or stand-alonededicated control channels (SDCCHs). So the user must decide if the SDCCH he isconsidering is associated with either TCHs or SDCCHs. When a SACCH is associatedwith SDCCH, the SACCH multiframe has a repeat length of 102 TDMA frames; when aSACCH is associated with TCH, the SACCH multiframe has a repeat length of 104TDMA frames.

SA assoc, with SDCCHSA assoc, with TCH#mf seconds #mf seconds

1 0.0471 1 0.4802 0.942 2 0.9604 1.883 4 1.9206 2.825 6 2.8808 3.767 8 3.84110 4.708 10 4.80112 5.650 12 5.76114 6.592 14 6.72116 7.533 16 7.68118 8.475 18 8.64120 9.417 20 9.60122 10.358 22 10.56124 11.300 24 11.52226 12.242 26 12.48228 13.183 28 13.44230 14.125 30 14.40232 15.067 32 15.36234 16.008 34 16.32236 16.950 36 17.28238 17.892 38 18.24240 18.833 40 19.20342 19.775 42 20.16344 20.717 44 21.12346 21.658 46 22.08348 22.600 48 23.04350 23.542 50 24.00352 24.483 52 24.96354 25.425 54 25.92356 26.367 56 26.88458 27.308 58 27.84460 28.250 60 28.80462 29.192 62 29.76464 30.133 64 30.724

ISSUE 11 REVISION 4



App D–i

Appendix D

Database Script Building Charts

ISSUE 11 REVISION 4



App D–ii

BSC

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



App D–iii

RXCDR

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



App D–iv

BSS

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



App D–v

BTS

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4



App D–vi

PATH

� ��

� ��

� ��

��

ISSUE 11 REVISION 4



App E–i

Appendix E

add_cell Command Prompts

ISSUE 11 REVISION 4



App E–ii

Table 4-1 add_cell command prompts

Prompt Input Range Default

Enter the Frequency Type: freq_type=x 1 (pgsm)

2 (egsm)

4 (dcs1800)

8 (pcs1900)

Use numeric valuesor text string.

None

Enter BSS identity code: bsic=x 0 to 63 None

Enter wait indication parameters: wait_indication_parameters=x 0 to 255 5

Enter common control channelconfiguration:

ccch_conf=x 0, 1, 2, 4, 6 0

Enter blocks reserved for access grant: bs_ag_blks_res=x 0 to 7 0

Enter multiframes between transmissions ofpaging messages:

bs_pa_mfrms=x 0 to 7 0

Enter extended paging active: extended_paging_active=x 0 or 1 0

Enter number of SDCCHs preferred: number_sdcchs_preferred=x 0 to 44(if ccch_conf=1)

8 to 48(if ccch_conf�1)

8

Enter enable incoming handover: en_incom_ho=x 0 or 1 1

Enter intra cell handover allowed: intra_cell_handover_allowed=x 0 to 2 1

Enter inter cell handover allowed: inter_cell_handover_allowed=x 0 to 3 1

Enter number of preferred cells: number_of_preferred_cells=x 1 to 16 16

Enter handover margin default: ho_margin_def=x –63 to 63 8

Enter handover recognized period: handover_recognized_period=x 2 to 64 2

Enter uplink rxqual handover allowed: ul_rxqual_ho_allowed=x 0 or 1 1

Enter downlink rxqual handover allowed: dl_rxqual_ho_allowed=x 0 or 1 1

Enter uplink rxlev handover allowed ul_rxlev_ho_allowed=x 0 or 1 1

Enter downlink rxlev handover allowed: dl_rxlev_ho_allowed=x 0 or 1 1

Enter alternate flag for SDCCH handover: sdcch_ho=x 0 or 1 1

Enter alternate SDCCH handover timervalue:

sdcch_timer_ho=x 1 to 31 1

Enter interference handover allowed: interfer_ho_allowed=x 0 or 1 1

Enter power handover allowed: pwr_handover_allowed=x 0 or 1 1

Enter MS distance allowed: ms_distance_allowed=x 0 or 1 0

Enter alternate flag for MS power controlprocessing

mspwr_alg=x 0 or 1 0

Enter handover power level: handover_power_level=x 2 to 19 None

ISSUE 11 REVISION 4



App E–iii


Prompt DefaultRangeInput

Enter power control indicator for hoppingthrough BCCH:

pwrc=x 0 or 1 1

. . . continued

Enter interference measurement averagingperiod (intave):

intave=x 1 to 31 8

Enter timing advance period: timing_advance_period 1 to 31 4

Enter MS power control period: ms_p_con_interval=x 0 to 31 2

Enter MS timeout for MS power control: ms_p_con_ack=x 0 to 31 2

Enter MS power control allowed: ms_power_control_allowed=x 0 or 1 1

Enter BTS power control interval: bts_p_con_interval=x 0 to 31 2

Enter BTS timeout for BTS power control: bts_p_con_ack=x 0 to 31 1

Enter BTS power control allowed: bts_power_control_allowed=x 0 or 1(0 for M-Cellmicro)

0

Enter power increment step size: pow_inc_step_size=x 2 to 4, 6 EVEN 2

Enter power reduction step size: pow_red_step_size=x 2 to 4 EVEN 2

Enter maximum BTS transmit power: max_tx_bts=x 0 to 21(0 to 6 forM-Cellmicro)

0

Enter maximum transmit MS: max_tx_ms=x 5 to 39 (GSM900)

0 to 30 (DCS1800and PCS1900)

See Note , below.

39

30

Note:

The range of values for max_tx_ms is system-dependent:

Odd values in the range of 5 – 39 for GSM900 (PGSM and EGSM).

Even values in the range of 0 – 30 for DCS1800 and PCS1900.

Enter receive level minimum default: rxlev_min_def=x 0 to 63 15

Enter MS transmit power maximum default: ms_txpwr_max_def=x 5 to 39 (GSM900)

0 to 30 (DCS1800and PCS1900)

See Note , above

39

30

Enter decision algorithm number: decision_alg_num=x 0 to 31 0

Enter decision alg 1 dl rxlev avg h: decision_1_dl_rxlev_av_h=x 0 to 3 0

Enter decision alg 1 dl rxlev avg ih: decision_1_dl_rxlev_av_ih=x 0 to 3 0

Enter decision alg 1 dl rxlev avg p: decision_1_dl_rxlev_av_p=x 0 to 3 0

Enter decision alg 1 dl rxqual avg h: decision_1_dl_rxqual_av_h=x 0 to 3 0

Enter decision alg 1 dl rxqual avg p: decision_1_dl_rxqual_av_p=x 0 to 3 0

Enter decision alg 1 n1: decision_1_n1=x 1 to 31 1


ISSUE 11 REVISION 4



App E–iv






Enter RSS decision alg 1 n6: decision_1_n6=x 1 to 31 1

. . . continued



Enter decision alg 1 ncell rxlev avg h calc: decision_1_ncell_rxlev_av_h_calc=x

0 to 3 0

Enter decision alg 1 p1: decision_1_p1=x 1 to 31 1








Enter decision alg 1 power budget rxlev: decision_1_p_bgt_rxlev_av_h=x 0 to 3 0

Enter decision alg 1 timing advance alg: decision_1_tim_adv_av_alg=x 0 to 3 0

Enter decision alg 1 ul rxlev avg h: decision_1_ul_rxlev_av_h=x 0 to 3 0

Enter decision alg 1 ul rxlev avg ih: decision_1_ul_rxlev_av_ih=x 0 to 3 0

Enter decision alg 1 ul rxlev avg p: decision_1_ul_rxlev_av_p=x 0 to 3 0

Enter decision alg 1 ul rxqual avg h: decision_1_ul_rxqual_av_h=x 0 to 3 0

Enter decision alg 1 ul rxqual avg p: decision_1_ul_rxqual_av_p=x 0 to 3 0

Enter quality band processing allowed: alt_qual_proc=x 0 or 1 0

Enter power control threshold l_rxqual_ul_p: l_rxqual_ul_p=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

226 BERor4 QBand

Enter power control threshold l_rxqual_dl_p: l_rxqual_dl_p=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

226 BERor4 QBand

Enter power control thresholdu_rxqual_ul_p:

u_rxqual_ul_p=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

28 BERor1 QBand

ISSUE 11 REVISION 4



App E–v



Enter power control thresholdu_rxqual_dl_p:

u_rxqual_dl_p=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

28 BERor1 QBand

Enter handover threshold l_rxqual_ul_h: l_rxqual_ul_h=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

453 BERor5 QBand

Enter handover threshold l_rxqual_dl_h: l_rxqual_dl_h=x If alt_qual_proc = 0,0 to 1810If alt_qual_proc = 1,0 to 7

453 BERor5 QBand

. . . continued

Enter handover threshold l_rxlev_ul_h: l_rxlev_ul_h=x 0 to 63 None

Enter handover threshold l_rxlev_dl_h: l_rxlev_dl_h=x 0 to 63 None

Enter handover threshold u_rxlev_ul_ih: u_rxlev_ul_ih=x 0 to 63 None

Enter handover threshold u_rxlev_dl_ih: u_rxlev_dl_ih=x 0 to 63 None

Enter handover threshold mobile maxrange:

ms_max_range=x 0 to 63 None

Enter power control threshold l_rxlev_ul_p: l_rxlev_ul_p=x 0 to 63 None

Enter power control threshold l_rxlev_dl_p: l_rxlev_dl_p=x 0 to 63 None

Enter power control threshold u_rxlev_ul_p: u_rxlev_ul_p=x 0 to 63 None

Enter power control threshold u_rxlev_dl_p: u_rxlev_dl_p=x 0 to 63 None

Enter alternate flag for neighbor cellprocess:

ncell_proc=x 0 or 1 None

Enter alternate flag for missing report: missing_rpt=x 0 or 1 None

Enter alternate flag for BA allocatingprocess:

ba_alloc_proc=x 0 or 1 None

Enter RSS link fail: link_fail=x 0 to 15 4

Enter link about to fail: link_about_to_fail=x 0 to 15 2

Enter alternate flag for full power RF loss: full_pwr_rfloss=x 0 or 1 0

Enter cell bar access switch: cell_bar_access_switch=x 0 or 1 0

Enter cell bar access class: cell_bar_access_class=x 0 toffff(hexadecimal)

0

Enter emergency class switch: emergency_class_switch=x 0 or 1 0

Enter report resource TCH full high watermark:

report_resource_tch_f_high_water_mark=x

0 to 255 None

Enter report resource TCH full low watermark:

report_resource_tch_f_low_water_mark=x

0 to 255 None

ISSUE 11 REVISION 4



App E–vi



Note:

The value for report_resource_tch_f_high_ water_mark must be set less than the value forreport_resource_tch_f_low_water_mark. The system will reject the add_cell command if thereport_resource_tch_f_high_ water_mark is greater than the report_resource_tch_f_low_water_mark.

Enter receive level access minimum: rxlev_access_min=x 0 to 63 None

Enter uplink dtx preference: dtx_required=x 0 to 2 2

Enter IMSI attach detach: attach_detach=x 0 or 1 0

Enter NCC of PLMN allowed: ncc_of_plmn_allowed=x 0 to 255 255

Enter maximum retransmissions on RACH: max_retran=x 0 to 3 0

Enter maximum mobile transmit power onCCCH:

ms_txpwr_max_cch=x 2 to 19 2

Enter tx_integer for RACH retransmitspacing:

tx_integer=x 0 to 15 4

Enter radio link timeout: radio_link_timeout=x 0 to 15 4

Enter MS reestablish allowed: reestablish_allowed=x 0 or 1 0

. . . continued

Enter cell reselect hysteresis: cell_reselect_hysteresis=x 0 to 7 None

Enter C2 cell reselection parameterindicator:

cell_reselect_param_ind=x 0 or 1 0

Enter C2 cell bar qualify: cell_bar_qualify=x 0 or 1 0

Enter C2 cell reselection offset: cell_reselect_offset=x 0 to 63 0

Enter C2 temporary offset: temporary_offset=x 0 to 7 0

Enter C2 penalty time: penalty_time=x 0 to 31 0

Enter rapid power down procedure active: rapid_pwr_down=x 0 or 1 0

Enter rapid power down trigger threshold: rpd_trigger=x 0 to 63 45

Enter rapid power down level offset: rpd_offset=x 0 to 63 8

Enter rapid power down averaging period: rpd_period=x 1 to 32 2

ISSUE 11 REVISION 4



App F–i

Appendix F

Typical BSS Script

ISSUE 11 REVISION 4



App F–ii

# BSC No. 1 Answers# 1.6.0.0 (GSR 4)

freq_types_allowed 7

equip 0 SITE0

chg_element fm_site_type 1 0

equip 0 CAB035

equip 0 CAGE00

0yes

chg_element transcoder_location 0 0chg_element gproc_slots 32 0chg_element bsc_type 1 0

chg_element ber_loss_daily 4 0chg_element ber_loss_hourly 6 0chg_element remote_loss_daily 20 0chg_element remote_loss_hourly 16 0chg_element remote_loss_oos 511 0chg_element remote_loss_restore 10 0chg_element remote_time_oos 500 0chg_element remote_time_restore 500 0chg_element slip_loss_daily 10 0chg_element slip_loss_hourly 4 0chg_element slip_loss_oos 255 0chg_element slip_loss_restore 10 0chg_element sync_loss_daily 20 0chg_element sync_loss_hourly 16 0chg_element sync_loss_oos 511 0chg_element sync_time_oos 90 0chg_element sync_time_restore 30 0

equip 0 KSW000no

equip 0 KSW010no

equip 0 BSP0

ISSUE 11 REVISION 4



App F–iii

020

equip 0 CSFP0018

equip 0 GPROC1019

equip 0 GPROC3021

equip 0 GPROC4022

equip 0 LCF000

equip 0 LCF100

equip 0 LCF211

equip 0 MSI10160

equip 0 MSI20150

equip 0 MSI30140

equip 0 MSI40130

ISSUE 11 REVISION 4



App F–iv

equip 0 GCLK00nonono


# XBL to BSC 1

equip bsc XBL0641025250037

equip 0 MTL01016

equip 0 OML0101

equip 0 CBL0108“sys03test””cbctest”

# TIMER CONFIGURATION

chg_element SS7_L3_T1 850 0chg_element SS7_L3_T2 1350 0chg_element SS7_L3_T12 1150 0chg_element SS7_L3_T13 1150 0chg_element SS7_L3_T14 2500 0chg_element SS7_L3_T17 1150 0chg_element SS7_L3_T22 270000 0chg_element SS7_L3_T23 270000 0chg_element SS7_SLT_T1 8000 0chg_element SS7_L3_T4 850 0chg_element SS7_L3_T5 850 0chg_element SS7_L2_T1 45000 0

ISSUE 11 REVISION 4



App F–v

chg_element SS7_L2_T2 77000 0chg_element SS7_L2_T3 1250 0chg_element SS7_L2_T4 500 0chg_element SS7_L2_T5 100 0chg_element SS7_L2_T6 4500 0chg_element SS7_L2_T7 1250 0chg_element SCCP_TCONN_EST 30000 0chg_element CLEAR_COMMAND 30000 0chg_element RADIO_CHAN_RELEASED 30000 0chg_element CIPHERING_SUCCESSFUL 30000 0chg_element HO_SUCCESSFUL 4100 0chg_element HO_ALLOCATION 30000 0chg_element SCCP_RELEASED 30000 0chg_element ASSIGN_SUCCESSFUL 4100 0chg_element BSC_AUDIT 30001 0chg_element SM_AUDIT_RESPONSE 30000 0chg_element SCCP_TIAS 420000 0chg_element SCCP_TIAR 900000 0chg_element BSSMAP_T7 10000 0chg_element BSC_AUDIT_RESPONSE 30000 0chg_element BSSMAP_TQHO 30000 0chg_element HO_REQUEST 30000 0chg_element EXT_HO_ALLOCATION 30000 0chg_element SCCP_TREL 15000 0chg_element BSSMAP_T20 30000 0chg_element BSSMAP_T19 30000 0chg_element BSSMAP_T1 20000 0chg_element BSSMAP_T13 1000 0chg_element BSSMAP_T4 20000 0chg_element CIRCUIT_RESET_ACK 70000 0chg_element SPI 10000 0chg_element START_ACK 20000 0

# EQUIP CIRCUITS

equip 0 CIC5 to 151 020

equip 0 CIC17 to 231 043

# MISCELLANEOUS

chg_element wait_for_reselection 240 0modify_value 0 mms_priority 255 mms 1 0chg_element clk_src_fail_reset_period 24 0 chg_element lta_alarm_range 10 0chg_element phase_lock_gclk 1 0

chg_element mb_preference 0 0chg_element dpc 33 0chg_element opc 15 0chg_element ni 2 0

ISSUE 11 REVISION 4



App F–vi

chg_element stat_interval 60 0chg_element option_alg_a5_1 1 0chg_element option_alg_a5_2 1 0chg_a5_alg_pr 1 2 0chg_element option_emergency_preempt 1 0

chg_ksw_config 0 0 0 1 2 3

chg_eas_alarm 1 2 ”High Temperature”chg_eas_alarm 2 2 ”Low Temperature”chg_eas_alarm 3 2 ”Door Intruder Alarm”chg_eas_alarm 4 2 ”Burglar Alarm”chg_eas_alarm 5 2 ”Window Intruder Alarm”

equip 0 SITE1LCF064no

equip 1 CAB09pgsm

equip 1 CAGE150

0yes

# SITE CONFIGURATIONchg_element bts_type 1 1chg_element gproc_slots 16 1

# MMS THRESHOLDS DEFAULTED

# SMS OPTIONSchg_element sms_dl_allowed 1 1chg_element sms_ul_allowed 1 1chg_element sms_tch_chan 2 1

add_cell 2 3 4 1 1 368 39 1frequency_type = pgsmbsic = 16wait_indication_parameters = 20ccch_conf = 2bs_ag_blks_res = 1bs_pa_mfrms = 1extended_paging_active = 1number_sdcchs_preferred = 8en_incom_ho = 1intra_cell_handover_allowed = 1inter_cell_handover_allowed = 1number_of_preferred_cells = 6ho_margin_def = 8handover_recognized_period = 12ul_rxqual_ho_allowed = 1

ISSUE 11 REVISION 4



App F–vii

dl_rxqual_ho_allowed = 1ul_rxlev_ho_allowed = 1dl_rxlev_ho_allowed = 1sdcch_ho = 0sdcch_timer_ho = 1interfer_ho_allowed = 1pwr_handover_allowed = 1ms_distance_allowed = 0mspwr_alg = 0handover_power_level = 6pwrc = 1intave = 3timing_advance_period = 6ms_p_con_interval = 2ms_p_con_ack = 2ms_power_control_allowed = 1bts_p_con_interval = 4bts_p_con_ack = 2bts_power_control_allowed = 0pow_inc_step_size_ul = 6pow_inc_step_size_dl = 6pow_red_step_size_ul = 4pow_red_step_size_dl = 4dyn_step_adj = 0dyn_step_adj_fmpr = 10max_tx_bts = 0max_tx_ms = 33rxlev_min_def = 0ms_txpwr_max_def = 33decision_alg_num = 0decision_1_dl_rxlev_av_h = 0decision_1_dl_rxlev_av_ih = 0decision_1_dl_rxlev_av_p = 0decision_1_dl_rxqual_av_h = 0decision_1_dl_rxqual_av_p = 0decision_1_n1 = 4decision_1_n2 = 4decision_1_n3 = 2decision_1_n4 = 2decision_1_n5 = 4decision_1_n6 = 2decision_1_n7 = 2decision_1_n8 = 2decision_1_ncell_rxlev_av_h_calc = 0decision_1_p1 = 3decision_1_p2 = 3decision_1_p3 = 2decision_1_p4 = 2decision_1_p5 = 3decision_1_p6 = 2decision_1_p7 = 2decision_1_p8 = 1decision_1_p_bgt_rxlev_av_h = 0decision_1_tim_adv_av_alg = 0decision_1_ul_rxlev_av_h = 0decision_1_ul_rxlev_av_ih = 0decision_1_ul_rxlev_av_p = 0

ISSUE 11 REVISION 4



App F–viii

decision_1_ul_rxqual_av_h = 0decision_1_ul_rxqual_av_p = 0alt_qual_proc = 0l_rxqual_ul_p = 1800l_rxqual_dl_p = 1800u_rxqual_ul_p = 0u_rxqual_dl_p = 0l_rxqual_ul_h = 900l_rxqual_dl_h = 400l_rxlev_ul_h = 5l_rxlev_dl_h = 10u_rxlev_ul_ih = 35u_rxlev_dl_ih = 63ms_max_range = 63l_rxlev_ul_p = 20l_rxlev_dl_p = 25u_rxlev_ul_p = 30u_rxlev_dl_p = 35missing_rpt = 1ba_alloc_proc = 0link_fail = 2link_about_to_fail = 1full_pwr_rfloss = 1cell_bar_access_switch = 0cell_bar_access_class = 0emergency_class_switch = 0report_resource_tch_f_high_water_mark = 1report_resource_tch_f_low_water_mark = 5rxlev_access_min = 0dtx_required = 2attach_detach = 0ncc_of_plmn_allowed = 68max_retran = 3ms_txpwr_max_cch = 5tx_integer = 12radio_link_timeout = 2reestablish_allowed = 1cell_reselect_hysteresis = 2cell_reselect_param_ind = 0cell_bar_qualify = 0cell_reselect_offset = 0temporary_offset = 0penalty_time = 0rapid_pwr_down = 1rpd_trigger = 45rpd_offset = 12rpd_period = 2

chg_cell_element queue_management_information 0 2 3 4 1 1 368 39 chg_cell_element max_q_length_sdcch 0 2 3 4 1 1 368 39 chg_cell_element channel_reconfiguration_switch 1 2 3 4 1 1 368 39 chg_cell_element max_number_of_sdcchs 32 2 3 4 1 1 368 39 chg_cell_element sdcch_need_low_water_mark 12 2 3 4 1 1 368 39 chg_cell_element sdcch_need_high_water_mark 2 2 3 4 1 1 368 39 chg_cell_element tch_full_need_low_water_mark 5 2 3 4 1 1 368 39 chg_cell_element rr_t3109 12000 2 3 4 1 1 368 39 chg_cell_element rr_t3111_tch 1500 2 3 4 1 1 368 39

ISSUE 11 REVISION 4



App F–ix

chg_cell_element rr_t3212 0 2 3 4 1 1 368 39 chg_cell_element dealloc_inact 10000 2 3 4 1 1 368 39 chg_cell_element ho_ack 10000 2 3 4 1 1 368 39 chg_cell_element rf_chan_rel_ack 20000 2 3 4 1 1 368 39 chg_element handover_required_reject_switch 0 0 cell_number=2 3 4 1 1 368 39chg_cell_element rr_t3103 4100 2 3 4 1 1 368 39 chg_cell_element rr_t3101 1700 2 3 4 1 1 368 39 chg_cell_element interfer_bands,0 0 2 3 4 1 1 368 39 chg_cell_element interfer_bands,1 8 2 3 4 1 1 368 39 chg_cell_element interfer_bands,2 13 2 3 4 1 1 368 39 chg_cell_element interfer_bands,3 18 2 3 4 1 1 368 39 chg_cell_element interfer_bands,4 25 2 3 4 1 1 368 39 chg_cell_element rach_load_period 5 2 3 4 1 1 368 39 chg_cell_element ccch_load_period 5 2 3 4 1 1 368 39 chg_cell_element rr_ny1_rep 10 2 3 4 1 1 368 39

# AVERAGING ALGORITHM CONFIGURATIONchg_act_alg_data surround_cell 2 3 4 1 1 368 39 0 0 8,0chg_act_alg_data surround_cell 2 3 4 1 1 368 39 0 0 1,1chg_act_alg_data rel_tim_adv 2 3 4 1 1 368 39 0 0 4,0chg_act_alg_data rel_tim_adv 2 3 4 1 1 368 39 0 0 2,1chg_act_alg_data rxlev_dl_ho 2 3 4 1 1 368 39 0 0 8,0chg_act_alg_data rxlev_dl_ho 2 3 4 1 1 368 39 0 0 4,1chg_act_alg_data rxlev_dl_pc 2 3 4 1 1 368 39 0 0 8,0chg_act_alg_data rxlev_dl_pc 2 3 4 1 1 368 39 0 0 4,1chg_act_alg_data rxlev_ul_ho 2 3 4 1 1 368 39 0 0 8,0chg_act_alg_data rxlev_ul_ho 2 3 4 1 1 368 39 0 0 4,1chg_act_alg_data rxlev_ul_pc 2 3 4 1 1 368 39 0 0 8,0chg_act_alg_data rxlev_ul_pc 2 3 4 1 1 368 39 0 0 4,1chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,0chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,1chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 0,3chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 0,4chg_act_alg_data rxqual_dl_ho 2 3 4 1 1 368 39 0 0 2,6chg_act_alg_data rxqual_dl_pc 2 3 4 1 1 368 39 0 0 2,0chg_act_alg_data rxqual_dl_pc 2 3 4 1 1 368 39 0 0 2,1chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 2,0chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 2,1chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 0,3chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 0,4chg_act_alg_data rxqual_ul_ho 2 3 4 1 1 368 39 0 0 4,6chg_act_alg_data rxqual_ul_pc 2 3 4 1 1 368 39 0 0 2,0chg_act_alg_data rxqual_ul_pc 2 3 4 1 1 368 39 0 0 2,1

# DEVICE\FUNCTION EQUIPAGE

equip 1 KSW0015yes

equip 1 BTP015203

equip 1 DHP

ISSUE 11 REVISION 4



App F–x

152223

equip 1 DHP151243


equip 1 MSI115160

equip 1 MSI315140

equip 1 COMB02550 00 1

equip 1 EAS015161 1 1 10 0 0 1 0 0 0 11 2 3 4 81 2 3 4 6 7 8 9

equip 1 DRI0 00drim157

2 3 4 1 1 368 3910 0014

equip 1 DRI

ISSUE 11 REVISION 4



App F–xi

0 10drim159

2 3 4 1 1 368 3910 0114


2 3 4 1 1 368 3910 0214


2 3 4 1 1 368 3910 03

1

4

equip 1 DRI

0 4

0

drim1515

2 3 4 1 1 368 3910 0414

# TIMERS DEFAULTED

ISSUE 11 REVISION 4



App F–xii

chg_element wait_for_reselection 240 1chg_element clk_src_fail_reset_period 24 1 chg_element lta_alarm_range 10 1

chg_element carriers_ins_pwr_fail 2 1chg_element carrier_disable_time 300 1

chg_element tch_flow_control 1 1 cell_number=2 3 4 1 1 368 39 chg_element tch_busy_norm_threshold 85 1chg_element tch_busy_critical_threshold 95 1

chg_element rf_res_ind_period 20 1

chg_element cbch_enabled 1 1 cell_number=2 3 4 1 1 368 39

chg_smscb_msg 0 200 3 1023 1 2 cell_number=2 3 4 1 1 368 39 MOTOROLA GSM

chg_smscb_msg 1 200 3 1022 1 2 cell_number=2 3 4 1 1 368 39 FREE CALLS TODAY

# PATHS# Path 0,Site 1

equip 0 path103 011 0# Path 1,Site 1

equip 0 path112 030 00 120 00 113 0

# RSL’s Site 1

equip 0 RSL100250037

equip 0 RSL1

ISSUE 11 REVISION 4



App F–xiii

11250037

# RTFs# RTF’s, Site 1

equip 1 RTFFULLBCCH0 0012 3 4 1 1 368 3965255 255 255 255 255 255 255 2550 0 0 0 0 0 0 000

equip 1 RTFFULLNON_BCCH0 1012 3 4 1 1 368 3955255 255 255 255 255 255 255 2550 0 0 0 0 0 0 0000

# MMS Priorities

modify_value 1 mms_priority 250 mms 1 0 modify_value 1 mms_priority 0 mms 3 0 modify_value 2 mms_priority 250 mms 0 1 modify_value 2 mms_priority 0 mms 0 0 modify_value 3 mms_priority 250 mms 0 0 modify_value 3 mms_priority 249 mms 0 1

# Enable GCLK sync

chg_element phase_lock_gclk 1 1 chg_element phase_lock_gclk 1 2 chg_element phase_lock_gclk 1 3

# LINK PARAMETERS

modify_value all nbit 0 MMSmodify_value all ber_oos_mon_period 50 MMSmodify_value all ber_restore_mon_period 1800 MMS

# NEIGHBOUR DEFINITIONS

add_neighbor 2 3 4 1 1 368 36 2 3 4 1 1 368 37 internal 1

ISSUE 11 REVISION 4



App F–xiv

ISSUE 11 REVISION 4



Answers–1

Answers

ISSUE 11 REVISION 4



Answers–2

ISSUE 11 REVISION 4



Answers–3

Answers Site configuration Exercise – Number 1

� ��

� ��

�� (,"'��*��

�

�! ��#�$�%+��$�*"+��+-'��

�(,"'��

�

�

�(,"'��

�

�

��

��

�

-�*

�(,"'��

�

�

�

��

�

%&

�! ��#�$�%+��*��+-'��

�! ��#�$�%+� ')&��*#&+*��

�! ��#�$�%+�*-%��+"$��&&*��

�! ��#�$�%+�*-%��+"$��)�*+&)��

�! ��#�$�%+�)�$&+��+"$��&&*��

�! ��#�$�%+�)�$&+��+"$��)�*+&)��

�! ��#�$�%+�*-%��#&**�&&*��

�! ��#�$�%+�*-%��#&**�)�*+&)��

�! ��#�$�%+�*-%��#&**��"#-��

�! ��#�$�%+�*-%��#&**�!&,)#-��

�! ��#�$�%+�)�$&+��#&**�&&*��

�! ��#�$�%+�)�$&+��#&**�)�*+&)��

�! ��#�$�%+�)�$&+��#&**��"#-��

�! ��#�$�%+�)�$&+��#&**�!&,)#-��

�! ��#�$�%+�*#"'�#&**�&&*��

�! ��#�$�%+�*#"'�#&**�)�*+&)��

�! ��#�$�%+�*#"'�#&**��"#-��

�! ��#�$�%+�*#"'�#&**�!&,)#-��

�! ��#�$�%+��)�#&**��"#-��

�! ��#�$�%+��)�#&**�!&,)#-��

ISSUE 11 REVISION 4



Answers–4

ISSUE 11 REVISION 4



Answers–5

Answers Site configuration Exercise – Number 2

� ��

� ��

�� (,"'��*��

��

��

�

�

�&

�(,"'��

�

��

�

�(,"'��

�

��

�! ��#�$�%+�*-%��+"$��&&*��

�! ��#�$�%+�*-%��+"$��)�*+&)��

�! ��#�$�%+�)�$&+��+"$��&&*��

�! ��#�$�%+�)�$&+��+"$��)�*+&)��

�! ��#�$�%+�*-%��#&**�&&*��

�! ��#�$�%+�*-%��#&**�)�*+&)��

�! ��#�$�%+�*-%��#&**��"#-��

�! ��#�$�%+�*-%��#&**�!&,)#-��

�! ��#�$�%+�)�$&+��#&**�&&*��

�! ��#�$�%+�)�$&+��#&**�)�*+&)��

�! ��#�$�%+�)�$&+��#&**��"#-��

�! ��#�$�%+�)�$&+��#&**�!&,)#-��

�! ��#�$�%+�*#"'�#&**�&&*��

�! ��#�$�%+�*#"'�#&**�)�*+&)��

�! ��#�$�%+�*#"'�#&**��"#-��

�! ��#�$�%+�*#"'�#&**�!&,)#-��

�! ��#�$�%+��)�#&**��"#-��

�! ��#�$�%+��)�#&**�!&,)#-��




Answers–6

C2 Reselection ExerciseThe parameters and levels specified on the facing page are typical values experiencedby a mobile in the reselection process. Use these values to determine whether themobile will reselect to the neighbour cell. The mobile has been in the server well overone hour, and the best neighbour has been in the top six measured cells for exactly 4minutes.

ISSUE 11 REVISION 4 C2 Reselection Exercise



Answers–7

Working Area

��

A= Rxlev Av – P1 (P1= rxlev_access_min= (–90) dBm)

A= (–70) – (–90) = 20 dBm

B= P2 – Max RF Power of MS (P2=ms_txpwr_max_cch= dBm)

B= 33 – 39 = (–6) dBm

C1= 20 – 0 = 20 dBm

C2= 20 + 6 = 26 dBm

��

A= Rxlev Av – P1 (P1= rxlev_access_min= (–90) dBm)

A= (–63) – (–90) = 27 dBm

B= P2 – Max RF Power of MS (P2=ms_txpwr_max_cch= dBm)

B= 41 – 39 = 2 dBm

C1= 27 – 2 = 25 dBm

C2= 25 + 4 – 10 = 19 dBm

FOR RESELECTION

C2 (server) < C2 (neighbour) – cell_reselect_hysteresis

C2 server= 26C2 Neighbour= 19C2 Neighbour – cell_reselect_hysteresis= 15 ∴ No reselection




Answers–8

ISSUE 11 REVISION 4 ADD_CELL Working Area



Answers–9

ADD_CELL Working Area��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4ADD_CELL Working Area



Answers–10

��

��

ISSUE 11 REVISION 4 ADD_CELL Working Area...



Answers–11

ADD_CELL Working Area...

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

� ��

��

��

ISSUE 11 REVISION 4ADD_CELL Working Area...



Answers–12

��

��

ISSUE 11 REVISION 4 ADD_CELL Working Area...



Answers–13

ADD_CELL Working Area...��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ISSUE 11 REVISION 4CHANGE_ELEMENT Working Area



Answers–14

CHANGE_ELEMENT Working Area��

��

��"�� "��

��"�� "��

�� !�� !��

��

��"�� "��

�� !!�� !!��

�� !�� !��

� ��!!�� !!��

��

��

��

��

�� !�� !��

��

��

��

��

��

��

��

��

��

��

��#�� #��

��

��

��

ISSUE 11 REVISION 4 Equipage Exercise Answers



Answers–15

Equipage Exercise Answersequip 12 KSW

0

0

15

yes

equip 12 BTP

0

15

20

3

equip 12 DHP

15

0

25

3

equip 12 GCLK

0

15

equip 12 MSI

1

15

16

0

equip 0 RSL

12

0

0

2500

3

7

ISSUE 11 REVISION 4Equipage Exercise Answers . . .



Answers–16

Equipage Exercise Answers . . .equip 12 DRI

0 0

0

drim

15

7

<CR>

<CR>

2 3 4 0 1 10724 52

1

<CR>

1

4

equip 12 DRI

0 1

0

drim

15

9

<CR>

<CR>

2 3 4 0 1 10724 52

1

<CR>

1

4

equip 12 DRI

1 0

0

drim

15

11

<CR>

<CR>

2 3 4 0 1 10724 54

1

<CR>

1

4

ISSUE 11 REVISION 4 Equipage Exercise Answers . . .



Answers–17

Equipage Exercise Answers . . .equip 12 RTF

bcch

0 0

0

1

2 3 4 0 1 10724 52

48

255 255 255 255 255 255 255 255

3 3 3 3 3 3 3 3

0

equip 12 RTF

non_bcch

0 1

0

1

2 3 4 0 1 10724 52

64

255 255 255 255 255 255 255 255

3 3 3 3 3 3 3 3

0

equip 12 RTF

bcch

1 0

0

1

2 3 4 0 1 10724 54

53

255 255 255 255 255 255 255 255

3 3 3 3 3 3 3 3

ISSUE 11 REVISION 4Path Equipage Exercise Answers



Answers–18

Path Equipage Exercise Answers

��

��

��

��

��

��

��

��

��

��

��

��

motorola bss

Documents