Motorola BSS Planning Guide

For:rrobot Printed on:Thu, Aug 3, 2000 02:44:08 From book:68P02900W21-G-UK-GA Document:tabs 1 Last saved on:Thu, Aug 3, 2000 02:44:07
Document:tabs 2 Last saved on:Thu, Aug 3, 2000 02:44:07 Document:tabs 3 Last saved on:Thu, Aug 3, 2000 02:44:07 Document:cover Last saved on:Thu, Aug 3, 2000 02:43:59 Document:cover (back) Last saved on:Thu, Aug 3, 2000 02:44:00 Document:spine1 Last saved on:Thu, Aug 3, 2000 02:43:59 Document:spine1 (back) Last saved on:Thu, Aug 3, 2000 02:44:00 Document:spine2 Last saved on:Thu, Aug 3, 2000 02:43:59 Document:spine2 (back) Last saved on:Thu, Aug 3, 2000 02:44:00 Document:insidecover-legal Last saved on:Thu, Aug 3, 2000 02:44:00 Document:toc Last saved on:Thu, Aug 3, 2000 02:44:05 ( ...)
CHAPTER 1 INTRODUCTION
CHAPTER 2 TRANSMISSION SYSTEMS
CHAPTER 3 BSS CELL PLANNING
CHAPTER 4 BTS PLANNING STEPS AND RULES
CHAPTER 5 BSC PLANNING STEPS AND RULES
CHAPTER 6 RXCDR PLANNING STEPS AND RULES
CHAPTER 7 OMC-R PLANNING STEPS AND RULES
CHAPTER 8 PLANNING EXERCISE
CHAPTER 9 STANDARD CONFIGURATIONS
CHAPTER 10 PREVIOUS BSC PLANNING STEPS AND RULES
CHAPTER 11 PREVIOUS BTS PLANNING
INDEX
Cellular Infrastructure Group
GSM-001-103
SYSTEM INFORMATION BSS EQUIPMENT PLANNING SOFTWARE RELEASE 1.6.1.3

68P02900W21-G
GSM-001-103
SYSTEM INFORMATION BSS EQUIPMENT PLANNING

SOFTWARE RELEASE 1.6.1.3
68P02900W21-G
SYSTEM INFORMATION BSS EQUIPMENT PLANNING
GSM-001-103
System Information BSS Equipment Planning
E Motorola 1993 - 2000 All Rights Reserved Printed in the U.K.
14th Apr 00
System Information: BSS Equipment Planning 68P02900W21-G
GSM-001-103
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
and MOTOROLA are registered trademarks of Motorola Inc. M-Cell and Taskfinder are trademarks of Motorola Inc. All other brands and corporate names are trademarks of their respective owners.
ii
14th Apr 00
GSM-001-103
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 2 4 5 6 7 9 12 14 15 16 19 20
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio channel units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features that affect planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Short message service, cell broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU for GPRS upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial information required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 12 12 12 13 13 14 14 16 16 16 16 17 17 18 19 19 19 111
Chapter 2 Transmission systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnecting the BSC and BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 22 22 23 23 23
14th Apr 00
iii
GSM-001-103
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggregate Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF path fault containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DYNET new device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency call handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Signalling Link (RSL) planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration and compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended BTS concentration planning guidelines . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managed HDSL on micro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General HDSL guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24 24 25 26 26 29 213 215 218 219 219 219 221 222 224 225 226 232 232 233 235 241 241 242 244 245 247
Chapter 3 BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GSM900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The DCS1800 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The PCS1900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absolute radio frequency channel capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modulation techniques and channel spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grade of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS control channel RF provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of CCCH per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of SDCCH per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
i
31 31 32 33 33 34 34 35 36 36 37 38 38 39 310 310 311 311 311 313 313 313 318 320 322
14th Apr 00
GSM-001-103
The GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview the GPRS planning process introduction . . . . . . . . . . . . . . . . . . . . . . . . . Determination of expected load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network planning flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network traffic estimation and key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS network traffic estimation and key concepts . . . . . . . . . . Introduction to the GPRS network traffic estimation and key concepts . . . . . . . . Dynamic timeslot mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier timeslot allocation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS timeslot allocation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provisioning the network with switchable timeslots . . . . . . . . . . . . . . . . . . . . . . . . . Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Air interface planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS air interface planning process structure . . . . . . . . . . . . . . Introduction to the GPRS air interface planning process . . . . . . . . . . . . . . . . . . . . Air interface throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: throughput estimation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: throughput estimation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput estimation process: step 3 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput estimation process: step 4 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation effects on GSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to decibels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fresnel zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio refractive index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental effects on propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multipath propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM900 path loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path loss GSM900 vs DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency re-use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to re-use patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier/ Interference (C/I) ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other sources of interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectorization of sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overcoming adverse propagation effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error protection and detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel coding for enhanced full rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping logical channels onto the TDMA frame structure . . . . . . . . . . . . . . . . . . . Voice Activity Detection VAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuous Transmission DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Most demanding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
324 324 325 325 326 327 328 328 329 332 334 337 339 343 345 345 346 351 352 353 356 357 359 359 360 361 362 366 369 382 383 384 384 385 388 389 389 390 390 392 394 396 397 398 399 3105 3105 3106 3108 3108 3108 3109 3110 3111
14th Apr 00
GSM-001-103
The microcellular solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layered Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3112 3112 3113 3114 3115
Chapter 4 BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro and Horizoncompact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment (CTU/TCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU/TCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Micro base control unit (mBCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . mBCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network interface unit (NIU) and site connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main control unit, with dual FMUX (MCUF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCUF planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main control unit (MCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
i
41 41 42 42 43 44 44 44 44 45 45 46 46 46 46 48 48 48 49 410 410 410 411 411 411 411 412 412 412 412 413 413 413 414 415 415 415 415 416 416 416 416
14th Apr 00
GSM-001-103
Cabinet interconnection (FOX/FMUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FOX/FMUX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network expansion using Macro/Micro/Picocell BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mixed site utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interface modules (HIM-75, HIM-120) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIM-75/HIM-120 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
417 417 417 418 419 419 419 419 420 420 420 420 421 421 421 422 422 422 422
Chapter 5 BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System capacity summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of introduction to BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU-to-SGSN interface planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS PCU provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS link provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 52 52 53 54 54 55 55 56 57 57 59 510 511 512 512 512 512 515 523 524 524 524 525 533 534
14th Apr 00
vii
GSM-001-103
Determining the RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS-BSC E1 links (Abis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . . LCF GPROC2 provisioning for GPRS signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions for transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
538 538 538 538 539 539 550 551 552 553 556 556 556 557 558 560 560 561 561 561 562 562 564 564 564 565 565 566 566 566 567 568 569 569 569 570 571 571 571 572 573 573 573 573 574 574 574 574 576 576 576 576
14th Apr 00
GSM-001-103
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
577 577 577 577 578 578 578 578 579 579 579 579 580 580 580 580 581 581 581 581 582 582 582 582 583 583
Chapter 6 RXCDR planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote transcoder planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR to BSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR to MSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 62 62 63 64 64 65 65 66 66 66 66 67 67 67 67 68 68 68 69
14th Apr 00
ix
GSM-001-103
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of RXU shelves and BSSC cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
610 610 610 611 612 612 612 612 613 613 613 613 614 614 614 614 615 615 615 615 616 616 616 616 617 617 617 617 618 618 618 618 619 619 619 619 620 620 620 620 621 621 621 621 622 622
Chapter 7 OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Authorized OMC-R configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6560 planning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC-R server and workstation composition . . . . . . . . . . . . . . . . . . . . .
x
i
71 71 71 71 72 73 76
14th Apr 00
GSM-001-103
Chapter 8 Planning exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for BTS 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for BTS 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter combining requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the GPRS PCU . . . . . . . . . . . . . . . . . . . . . . . . Calculations using alternative call models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters used in calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of CCCHs per cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of SDCCHs per cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of GPROC2s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 82 82 83 83 85 85 86 86 86 87 89 89 89 89 89 810 812 812 814 815 815 815 815 815 815 816 816 816 816 816 816 816 817 818 818 820 825 825 825 827 828 829
Chapter 9 Standard configuration descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
91 91
14th Apr 00
xi
GSM-001-103
Standard configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with 24 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with full redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell configurations (M-Cellaccess) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two site cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One cabinet configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one Horizonmacro cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one M-Cell6 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one M-Cell2 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with two Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with two M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with three Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with three M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with four Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with four M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellarenamacro enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell RF configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellarena enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92 92 93 93 94 95 96 96 98 910 910 911 912 913 913 914 915 915 916 917 917 918 919 919 920 935 998 9107 9108 9108
Chapter 10 Previous BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . . Assigning BTSs to LCFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii
i
101 101 102 102 103 104 104 105 105 107 108 109 1010 1010 1010 1010 1011 1011 1012 1013 1014
14th Apr 00
GSM-001-103
Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR2 and earlier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1015 1015 1015 1016 1017 1019 1020 1021 1021 1021 1022 1023 1026 1026 1026 1027 1027 1028 1029 1029 1029 1030 1031 1032 1032 1032 1033 1034 1034 1034 1035 1036 1036 1036 1036 1037 1037 1037 1037 1039 1039 1039 1039 1040 1040 1040 1040 1041 1041 1041 1041
14th Apr 00
xiii
GSM-001-103
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1042 1042 1042 1042 1043 1043 1043 1043 1044 1044 1044 1044 1045 1045 1045 1045 1046 1046
Chapter 11 Previous generation BTS planning and equipment descriptions . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculations for determining BTS GPROC, GPROC2 requirements . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call processing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS shelf configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for typical call mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for border location area call mix . . . . . . . . . . . . . . . . . . . . . . . BTS equipment cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types EG, FG and BTS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types AG, BG and DG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Rx signals between multiple cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . RFE planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combiner shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combining equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combiner shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
i
111 111 112 112 113 114 114 114 116 116 117 117 117 118 119 1110 1111 1112 1113 1113 1113 1114 1114 1114 1114 1115 1116 1117 1117 1117 1118 1118
14th Apr 00
GSM-001-103
Duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplexer planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot switch (TSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local area extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital radio interface extender (DRIX3c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1119 1119 1119 1119 1120 1120 1120 1120 1121 1121 1121 1121 1122 1122 1122 1123 1124 1124 1124 1124 1125 1125 1125 1125 1126 1126 1126 1126 1127 1127 1127 1127 1128 1128 1128 1128 1129 1129 1129 1129 1130 1130 1130 1130 1131 1131 1131 1131
14th Apr 00
xv
GSM-001-103
Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TopCell BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU without diversity . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, five DRCU/SCUs with combining . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, six DRCU/SCUs with combining and diversity . . . . . . . . . . . . . . . Single cabinet, multiple antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, multiple antennas with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, four DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, ten DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, multiple antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Six sector configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sixsector BTS6 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1132 1132 1132 1132 1133 1133 1133 1133 1134 1134 1135 1135 1136 1137 1137 1139 1140 1142 1145 1147 1149 1149 1151 1153 1154 1156
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I1
xvi
14th Apr 00
GSM-001-103
Issue status of this manual
Issue status of this manual

Introduction
The following shows the issue status of this manual since it was first released.
Version information
The following lists the versions of this manual in order of manual issue: Manual issue O A B C D E F G Date of issue 30th Jun 94 19th Dec 94 30th Nov 95 17th Dec 96 16th Jun 97 2nd Mar 98 1st Dec 98 15th Apr 00 Original issue Issue A Issue B Issue C Issue D (also supersedes 68P02900W31-B) Issue E includes GSM Software Release 3 Issue F includes GSM Software Release 4 Issue G includes GSM Software Release 4.1 (1.6.1.3) Remarks
Resolution of Service Requests

The following Service Requests are now resolved in this manual: Service Request N/A GMR Number N/A Remarks
14th Apr 00
General information
GSM-001-103
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) manuals are intended to instruct and assist personnel in the operation, installation and maintenance of the Motorola GSM equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
About this manual

The manual contains information about planning a GSM network; using the Horizon range, BSC/RXCDR, Scaleable OMC equipments and the GPRS Packet Control Unit. The information in this manual will help you to: S S S S S S S S S S S S S S
2
Identify the main effects of propagation on GSM frequencies. Calculate the power budget to balance a cellular system. Identify sources of interference. Understand the importance of the carrier to interference ratio. Determine the viable frequency re-use scheme. Understand the impact of microcellular equipment. Calculate the required number of traffic channels per cell. Calculate the required number of CCCHs per cell. Calculate the required number of SDCCHs per cell. Determine the hardware requirements for the Horizon range of equipment. Understand the network topology as utilized within a GSM network. Determine the BSC hardware requirements for a given GSM network plan. Determine the XCDR hardware requirements for a given GSM network plan. Produce a BSS sub-system plan for a network, given various system parameters. System Information: BSS Equipment Planning 68P02900W21-G
14th Apr 00
GSM-001-103
General information
Cross references
Throughout this manual, cross references are made to the chapter numbers and section names. The section name cross references are printed bold in text. This manual is divided into uniquely identified and numbered chapters that, in turn, are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CRTLc ALTf | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return (Enter) key. The Return key is identified with the symbol on both the X terminal and the SPARCstation keyboards. The SPARCstation keyboard Return key is also identified with the word Return.
14th Apr 00
First aid in case of electric shock
GSM-001-103
First aid in case of electric shock

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

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: 1. 2. 3. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM Customer Network Resolution Centre +44 (0)1793 565444 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.
4.
14th Apr 00
Warnings and cautions
GSM-001-103
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its calibration due date when testing Motorola base stations.
14th Apr 00
GSM-001-103
General warnings
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
14th Apr 00
General warnings
GSM-001-103
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipments have to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Do not ...
... substitute parts or modify equipment. Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S Beryllium materials are absorbed into the body tissues through the skin, mouth, or a wound. The dust created by breakage of Beryllia is inhaled. Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
14th Apr 00
GSM-001-103
Human exposure to radio frequency energy (PCS1900 only)

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

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

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

Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.
10
14th Apr 00
GSM-001-103
Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4pr W Pin
2
1930MHz +39.0 dBm (8 watts) 2.0dB PCL = +39.02.0 = +37.0dB (5watts) 16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+ GPin + 4pW 43.65 5 + 1.16m 4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.
Power density measurements

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

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 2-20 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.
12
14th Apr 00
GSM-001-103
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon as possible.
Handling procedures
Removal of components from printed circuit boards (PCBs) is to take place only at Motorola approved repair centres. The removal station will be equipped with extraction equipment and all other protective equipment necessary for the safe removal of components containing Beryllium Oxide. If during removal a component is accidently opened, the Beryllium Oxide dust is to be wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool used to collect the paste is also to be placed in the container. The container is then to be sealed and labelled. A suitable respirator is to be worn at all times during this operation. Components which are successfully removed are to be placed in a separate bag, sealed and labelled.
Disposal methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as hazardous waste. All components must be removed where possible from boards and put into sealed bags labelled Beryllium Oxide components. These bags must be given to the safety and environmental adviser for disposal. Under no circumstances are boards or components containing Beryllium Oxide to be put into the general waste skips or incinerated.
Product life cycle implications

Motorola GSM and analogue equipment includes components containing Beryllium Oxide (identified in text as appropriate and indicated by warning labels on the equipment). These components require specific disposal measures as indicated in the preceding (Disposal methods) paragraph. Motorola will arrange for the disposal of all such hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange for the most environmentally friendly disposal available at that time.
14th Apr 00
13
General cautions
GSM-001-103
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.
14
14th Apr 00
GSM-001-103
Devices sensitive to static
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads shorted together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced observe the following precautions when handling the replacement: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14th Apr 00
15
Motorola GSM manual set
GSM-001-103

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

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

The following are related Motorola GSM manuals: Classification number GSM-001-103 GSM-002-103 GSM-002-703 GSM-005-103 GSM-008-403 GSM-008-703 GSM-006-202 GSM-006-413 GSM-006-712 Name System Information: BSS Equipment Planning . . . . System Information: DataGen . . . . . . . . . . . . . . . . . . Software Release Notes: DataGen . . . . . . . . . . . . . . System Information: GSM Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: Network Health Analyst Software Release Notes: Network Health Analyst . Operating Information: OMC-R System Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: OSI Clean Install . . . . . Software Release Notes: OMC-R OSI System . . . . Order number 68P02900W21 68P02900W22 68P02900W76 68P02900W25 68P02900W36 68P02900W77 68P02901W10 68P02901W39 68P02901W70
16
14th Apr 00
GSM-001-103
Generic GPRS manuals

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

The following are related Motorola GPRS manuals: GPRS-001-103 GPRS-005-103 System Information: GPRS Equipment Planning . . 68P02903W02 System Information: GSN Advance Operational Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38
14th Apr 00
17
GSM-001-103
BSS service manuals

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

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

Instructions
When a GMR is inserted in this manual, the amendment record below must be filled in to record the insertion. Retain the pink instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Incorporated by (signature)
Date
20
14th Apr 00
Chapter 1
Introduction
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio channel units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features that affect planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Short message service, cell broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU for GPRS upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial information required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 12 12 12 13 13 14 14 16 16 16 16 17 17 18 19 19 19 111
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction to BSS planning
This chapter provides an overview of this manual and the various elements of a BSS and the BSS planning methodology. This chapter contains: S S Manual overview. BSS equipment overview. S S An overview of the BSS system architecture. An overview of the BSS system components.
BSS features. A description of those BSS features that can affect BSS planning.
BSS planning overview. A list of the information required before planning can begin. An overview of the BSS planning methodology.
14th Apr 00
11
Manual overview
GSM-001-103
Manual overview
Introduction
The manual contains information about planning a GSM network; utilizing a combination of BTS and M-Cell BTS equipment.
Contents
The manual contains the following chapters: S Chapter 1: Introduction This chapter provides an overview of the various elements of a BSS and the BSS planning methodology. S S Chapter 2: Transmission systems This chapter provides an overview of the transmission systems used in GSM. Chapter 3: BSS cell planning This chapter states the requirements and procedures used in producing a BSS cell site plan. S Chapter 4: BTS planning steps and rules This chapter provides the planning steps and rules for the BTS, including ExCell, TopCell and the M-Cell range of equipments. S S Chapter 5: BSC planning steps and rules This chapter provides the planning steps and rules for the BSC. Chapter 6: RXCDR planning steps and rules This chapter provides the planning steps and rules for the RXCDR. S S Chapter 7: OMC-R planning steps and rules This chapter provides the planning steps and rules for the OMC-R. Chapter 8: Planning exercise This chapter provides a planning exercise designed to illustrate the use of the rules and formulae provided in Chapter 3, Chapter 4, Chapter 5, Chapter 6, and Chapter 7. S Chapter 9: Standard configuration descriptions This chapter provides diagrams of the logical interconnections of the components in various standard BSS and BTS site configurations, including Horizonmacro and the M-Cell range. S Chapter 10: Previous BSC planning steps and rules This chapter (included for reference only) provides the planning steps and rules for the BSC up to software release GSR3. S Chapter 11: Previous generation BTS planning steps and rules This chapter (included for reference only) provides the planning steps and rules for the BSC up to software release GSR3.
12
14th Apr 00
GSM-001-103
BSS equipment overview

System architecture
The architecture of the Motorola Base Station System (BSS) is extremely versatile, and allows many possible configurations for a given system. The BSS is a combination of digital and RF equipment that communicates with the Mobile Switching Centre (MSC), the Operations and Maintenance Centre Radio (OMC-R), and the Mobile Stations (MS) as shown in Figure 1-1.
OMCR MSC LRs A INTERFACE
RXCDR
BSS
O&M
PCU
BSC
BSS
ABIS INTERFACE
BTS 1
BTS 5
BTS 8
...
BTS n
BTS 2
BTS 6
BTS 3
BTS 7
BTS 4
AIR INTERFACE MS MS
...
MS
MS
...
NOTE: 1. THE OMC-R CAN BE LINKED THROUGH THE RXCDR AND/OR TO THE BSS/BSC DIRECT. 2. THE EXAMPLE OF MULTIPLE MSs CONNECTED TO BTS 4 AND BTS 7, CAN BE ASSUMED TO BE CONNECTED TO ALL OTHER BTSs SHOWN.
Figure 1-1 BSS block diagram
14th Apr 00
13
GSM-001-103
System components
The BSS can be divided into a Base Site Controller (BSC), and one or more Base Transceiver Station (BTS). These can be in-building BTS cabinets or externally located ExCell, TopCell, M-Cell cabinets or M-Cell enclosures. The Transcoder (XCDR) or Generic Digital Processor (GDP) provides 4:1 multiplexing of the traffic and can be located at the BSC or between the BSC and MSC. When the XCDR/GDP is located at the MSC it reduces the number of communication links to the BSC. When transcoding is not performed at the BSC, the XCDR is referred to as a remote transcoder (RXCDR). The RXCDR is part of the BSS but may serve more than one BSS.
Radio channel units

In the Motorola BTS product line, the radio transmit and receive functions are provided as listed in Table 1-1: NOTE With the exception of the TCU, which is backwardly compatible by switching from TCU to SCU on the front panel, all other radio channel units are only compatible with the equipment listed. Table 1-1 Radio channel unit usage Radio channel unit Diversity Radio Channel Unit (DRCU) Slim Channel Unit (SCU) Transceiver Control Unit (TCU) Picocell Control Unit (PCU) RF Head Transceiver Control Unit, micro (TCU-m) Dual Transceiver Module (DTRX) Compact Transceiver Unit (CTU) Where used ... BTS4, BTS5, BTS6, TopCell, ExCell BTS4, BTS5, BTS6, TopCell, ExCell M-Cell6, M-Cell2, BTS6 M-Cellaccess Horizonoffice M-Cellmicro, M-Cellcity and M-Cellcity+ M-Cellarena and M-Cellarena macro Horizonmacro
DRCU/SCU
Planning rules for the DRCU and SCU are provided in Chapter 11 of this manual. The receivers can support receive diversity.
TCU
Description and planning rules for the TCU is provided in Chapter 4 of this manual. The receivers can support receive diversity.
14
14th Apr 00
GSM-001-103
TCU-m
In M-Cellmicro, M-Cellcity and M-Cellcity+ the radio transmit and receive functions are provided by a pair of Transceiver Control Unit, micro (TCU-m). Description and planning rules for the TCU-m are provided in Chapter 10, Chapter 16, and Chapter 4 of this manual. The receivers do not support receive diversity.
DTRX
In M-Cellarena and M-Cellarena macro the radio transmit and receive functions are provided by a Dual Transceiver Module (DTRX). Description and planning rules for the DTRX are provided in Chapter 10 and Chapter 4 of this manual. The receivers do not support receive diversity.
PCU
Description and planning rules for the PCU is provided in Chapter 11 and Chapter 4 of this manual. The receivers can support receive diversity.
CTU
Description and planning rules for the CTU is provided in Chapter 9 and Chapter 4 of this manual. The receivers can support receive diversity.
14th Apr 00
15
BSS features
GSM-001-103
BSS features
Features that affect planning
This section provides a description of the software features that might affect the required equipment, and that should be taken into consideration before planning actual equipment. Check with the appropriate Motorola sales office regarding software availability with respect to these features. S S S S S Diversity. Frequency hopping. Short message, cell broadcast. Code storage facility processor. Packet Control Unit (PCU) for General Packet Data Service (GPRS) upgrade.
Diversity
Diversity reception (spatial diversity) at the BTS is obtained by supplying two uncorrelated receive signals to the DRCU/SCU/TCUs. Each DRCU/SCU/TCU includes two receivers, which independently process the two received signals and combine the results to produce an output. This results in improved receiver performance when multipath propagation is significant and in improved interference protection. Two Rx antennas are required for each sector. Equivalent overlapping antenna patterns, and sufficient physical separation between the two antennas are required to obtain the necessary de-correlation.
Frequency hopping
There are two methods of providing frequency hopping: synthesizer hopping and baseband hopping. Each method has different hardware requirements. The main differences are: S S Synthesizer hopping requires the use of wideband (hybrid) combiners for transmit combining, while baseband hopping does not. Baseband hopping requires the use of one DRCU/SCU/TCU for each allocated frequency, while synthesizer hopping does not.
16
14th Apr 00
GSM-001-103
BSS features
Synthesizer hopping
Synthesizer hopping uses the frequency agility of the DRCU/SCU/TCU to change frequencies on a timeslot basis for both receive and transmit. The DRCU/SCU/TCU calculates the next frequency and re-programs its synthesizer to move to the new frequency. There are three important points to note when using this method of providing frequency hopping: S S S Hybrid combining must be used; cavity combining is not allowed when using synthesizer hopping. The output power available with the use of the hybrid combiners must be consistent with coverage requirements. It is only necessary to provide as many DRCU/SCU/TCUs as required by the traffic. Note that one DRCU/SCU/TCU in each sector must be on a fixed frequency to provide the BCCH carrier.
Baseband hopping
For baseband hopping each DRCU/SCU/TCU operates on preset frequencies in the transmit direction. Baseband signals for a particular call are switched to a different DRCU/SCU/TCU at each TDM frame in order to achieve frequency hopping. There are three important points to note when using this method of providing frequency hopping: S S S The number of DRCU/SCU/TCUs must be equal to the number of transmit (or receive) frequencies required. Use of either remote tuning combiners or hybrid combiners is acceptable. Frequency redefinition procedures were incomplete in the Phase 1 GSM specifications; this is addressed in the Phase 2 GSM procedures, but at this time there are no Phase 2 MSs capable of implementing this. Consequently, calls could be dropped, if a single DRCU/SCU/TCU fails, due to the inability to inform the MSs.
Short message service, cell broadcast

The Short Message Service, Cell Broadcast (SMS CB) feature, is a means of unilaterally transmitting data to MSs on a per cell basis. This feature is provided, by a Cell Broadcast Channel (CBCH). The data originates from either a Cell Broadcast Centre (CBC) or OMC-R (operator-defined messages may be entered using the appropriate MMI command). The CBC or OMC-R downloads cell broadcast messages to the BSC, together with indications of the repetition rate, and the number of broadcasts required per message. The BSC transmits these updates to the appropriate BTSs, which will then ensure that the message is transmitted as requested.
Code storage facility processor

Beginning with software release 1.3.0.0, the BSS supports a GPROC acting as the Code Storage Facility Processor (CSFP). The CSFP allows pre-loading of a new software release while the BSS is operational. When M-Cell BTSs are connected to the BSC, a CSFP is required at the BSC and a second CSFP should be equipped for redundancy as required. NOTE If GPROC2 is used this feature will not require additional hardware.
14th Apr 00
17
BSS features
GSM-001-103
PCU for GPRS upgrade

GPRS introduces packet data services (with GSR4.1) and GPRS planning is fundamentally different from the planning of circuit swtiched networks. One of the fundamental reasons for the difference, is that a GPRS network allows the queing of data traffic instead of blocking a call when a circuit is unavailble. Consequently, the use of Erlang B tables for estimating the number of trunks or timeslots required, is not a valid planning approach for the GPRS packet data provisioning process.
18
14th Apr 00
GSM-001-103
BSS planning overview

Introduction
A brief overview of the planning process is provided in this section.
Initial information required

The information required, before planning can begin, can be categorized into three main areas: S S S Traffic model and capacity calculations. Category of service. Site planning.
Traffic model and capacity calculations

The following information is required to calculate the capacity required: S S S S S S S S S S S S Traffic information (Erlangs/BTS) over desired service area. Average traffic per site. Call duration. Number of handovers per call. Ratio of location updates to calls. Ratio of total pages sent to time in seconds (pages per second). Ratio of intra-BSC handovers to all handovers. Number of TCHs. Ratio of SDCCHs to TCHs. Link utilization (for C7 MSC to BSS links). SMS utilization (both cell broadcast and point to point). Expected (applied and effective) GPRS load.
14th Apr 00
19
GSM-001-103
Category of service
The following information is required to decide what category of service is required: S Category of service area urban, suburban, or rural: S S S Cell configuration in each category, sector against omni. Frequency re-use scheme to meet traffic and C/I requirements. Number of RF carriers in cell/sector to support traffic.
Grade of service of the trunks between MSC/BSC, typically Erlang B at 1%. Grade of service of the traffic channels (TCH) between MS and BTS, typically Erlang B at 2%. Cell grid plan, a function of: Desired grade of service or acceptable level of blockage. Typical cell radio link budget. Results of field tests.
Site planning
The following information is required to plan each site. S S S S Where the BSC and BTSs will be located. Local restrictions affecting antenna heights, equipment shelters, and so on. Number of sites required (RF planning issues). Re-use plan (frequency planning) omni or sector: S S S Spectrum availability. Number of RF carrier frequencies available. Antenna type(s) and gain specification.
Diversity requirement. Diversity doubles the number of Rx antennas and associated equipment. Redundancy level requirements, determined for each item. Supply voltage.
110
14th Apr 00
GSM-001-103
Planning methodology
A GSM digital cellular system is usually made up of several BSSs. The planning cycle begins with defining the BSS cell, followed by the BTS(s), then the BSC(s), and finally the RXCDR(s). The text that follows provides a brief check-list of the steps in planning a BSS: 1. 2. Choose the configuration, omni or sectored and the frequency re-use scheme that satisfies traffic, interference and growth requirements. Plan all BTS sites first: 3. Use an appropriate RF planning tool to determine the geographical location of sites on and the RF parameters of the chosen terrain. Determine which equipment affecting features are required at each site. For example, diversity or frequency hopping. Plan the RF equipment portion and cabinets for each BTS site. Plan the digital equipment portion for each BTS site.
Plan the BSCs after the BTS sites are configured and determine: Sites for each BSC. Which BTSs are connected to which BSC. How the BTSs are connected to the BSCs. Traffic requirements for the BSCs. Digital equipment for each BSC site. Shelf/cabinets and power requirements for each BSC.
4.
Plan the remote transcoder (RXCDR) requirements and, if required, subsequent hardware implementation.
14th Apr 00
111
GSM-001-103
112
14th Apr 00
Chapter 2
Transmission systems
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 2 Transmission systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnecting the BSC and BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggregate Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF path fault containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DYNET new device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency call handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Signalling Link (RSL) planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration and compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended BTS concentration planning guidelines . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managed HDSL on micro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General HDSL guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 22 22 23 23 23 24 24 25 26 26 29 213 215 218 219 219 219 221 222 224 225 226 232 232 233 235 241 241 242 244 245 247
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides diagrams of the logical interconnections and descriptions of BSS interconnections. This chapter contains: S S S BSS interfaces. BSC to BTS interconnection rules. Network topology: S S Star connection. Daisy chain connection. Aggregate Abis. 16 kbit/s RSL. 16 kbit/s XBL.
BTS concentration. Managed HDSL on micro BTS: Integrated HDSL interface. Microcell system planning. Picocell system planning.
14th Apr 00
21
BSS interfaces
GSM-001-103
BSS interfaces
Introduction
Figure 2-1 and Table 2-1 indicate the type of interface, rate(s) and transmission systems used to convey information around the various parts of the BSS system.
OMC-R
OML
X.25 (LAPB)
Gb OPTION B
MSC
Air interface Abis interface
MS
(LAPDm)
BTS
RSL (LAPD)
BSC
A interface MTL (C7), XBL (LAPD) OML (X.25)
RXCDR SGSN
GDS Gb OPTION A
PCU
Gb OPTION C X.25 (LAPB)
CBL
CBC
Figure 2-1 BSS interfaces
Table 2-1 BSS interfaces Interface Air From/To MS BTS Signalling by ... RACH, SDCCH, SACCH, FACCH E1/T1 links Abis (Mobis) A A BTS BSC BSS MSC RXCDR BSC MSC OMC-R MSC CBC Gb GDS PCU SGSN PCU BSC
14th Apr 00
Rate
Using ... LAPDm
RSL MTL (OML, CBL) XBL OML (X.25) CBL (X.25)
16/64 kbit/s 64 kbit/s 16/64 kbit/s 64 kbit/s 64 kbit/s
LAPD C7 LAPD LAPB LAPB
22
GSM-001-103
Interconnecting the BSC and BTSs
Interconnecting the BSC and BTSs

Introduction
Network topology is specified in terms of the path(s) between the BSC and the BTS sites. A path is determined by which E1 or T1 circuits, and possible intervening BTS sites are used to provide the connection. Transcoding may be carried out at the BSC or RXCDR.
Interconnection rules
The following rules must be observed when interconnecting a BSC and BTSs: S S S S The BSC may share MSI boards between BTSs. When there are two or more E1 or T1 circuits, at least two MSIs are recommended for redundancy. A minimum of one MSI is required at each BTS. There is a maximum of 8, and minimum of 1, signalling links per BTS6 site, each requiring one 64 kbit/s timeslot on a E1 or T1 circuit. The maximum number of carrier units is determined by available E1 or T1 circuit capacity. A carrier unit will require two 64 kbit/s timeslots on a E1 or T1 circuit. In a redundant connection, each carrier unit requires two 64 kbit/s timeslots on two different E1 or T1 circuits. At the BSC, one E1 or T1 circuit is required to connect to a daisy chain. If the connection is a closed loop daisy chain, two E1 or T1 circuits are required. To provide redundancy, the two E1 or T1 circuits should be terminated on different MSIs. In a closed loop daisy chain the primary RSLs for all BTS sites should be routed in the same direction with the secondary RSLs routed in the opposite direction. The primary RSL at each BTS site in the daisy chain should always be equipped on the multiple serial interface link (MMS) equipped in CAGE 15 slot 16 port A. The secondary RSL at each BTS site should be equipped on the MMS equipped in either cage 15 slot 16 port B or cage 15 slot 14 port A or cage 14 slot 16 port A.
The following rules must be observed when interconnecting InCell and M-Cell equipment: S S S Reconfigure the InCell BTS to have integral sector(s) in the cabinet. Install M-Cell cabinet(s) to serve the remaining sector(s). Daisy chain the M-Cell E1/T1 links to the BSC.
14th Apr 00
23
Network topology
GSM-001-103
Network topology
Introduction
The user can specify what traffic is to use a specific path. Any direct route between any two adjacent sites in a network may consist of one or more E1 or T1 circuits. Figure 2-2 shows a possible network topology. Each BTS site in the network must obey the following maximum restrictions: S S S S S S S S S S Ten serial interfaces supported at a BTS6. Six serial interfaces supported at an M-Cell6 BTS. Four serial interfaces supported at an M-Cell2 BTS. Two serial interfaces supported at an M-Cellcity / M-Cellcity+ BTS. Two serial interfaces supported at an M-Cellarena / M-Cellarena macro BTS. Six serial interfaces supported at an M-Cellaccess BTS. Six serial interfaces supported at a Horizonmacro. Ten BTS(s) in a path, including the terminating BTS for E1 circuit connection or eight BTS(s) in a path, including the terminating BTS for T1 circuit connection. Eight signalling links per BTS6 site. Four signalling links per M-Cell BTS site (maximum of two per path).
An alternative path may be reserved for voice/data traffic in the case of path failure. This is known as a redundant path, and is used to provide voice/data redundancy, that is loop redundancy The presence of multiple paths does not imply redundancy. Each signalling link has a single path. When redundant paths exist, redundant signal links are required, and the signalling is load shared over these links. In the case of a path failure, the traffic may be rerouted, but the signalling link(s) go out of service, and the load is carried on the redundant link(s).
BSC
BTS 10
BTS 1
BTS 5
BTS 2
BTS 6
BTS 11
BTS 3
BTS 7
BTS 9
BTS 4
BTS 8
Figure 2-2 Possible network topology
24
14th Apr 00
GSM-001-103
Network topology
Star connection
A star connection is defined by installing E1 or T1 circuits between each BTS site and the BSC, as shown in Figure 2-3. A star connection may require more MSI cards at the BSC than daisy chaining for the same number of BTS sites. The star connection will allow for a greater number of carrier units per BTS site. An E1 circuit provides for 15 carriers plus one signalling link. A T1 circuit provides for 11 carriers plus 1 or 2 signalling links.
BTS 3 BTS 2 BTS 4
BTS 1
BSC
BTS 5
MSC BTS 7 BTS 9 BTS 8
Figure 2-3 Star connection
14th Apr 00
25
Network topology
GSM-001-103
Daisy chain connection

Daisy chaining multiple BTS sites together can better utilize the 64 kbit/s timeslots of one E1 or T1 circuit from the BSC. Daisy chaining the sites together provides for the efficient utilization of the E1 or T1 circuit for interconnecting smaller sites back to the BSC. The daisy chain may be open ended or closed looped back to the BSC as shown in Figure 2-4. The closed loop version provides for redundancy while the open ended does not. Note that longer daisy chains (five or more sites) may not meet the suggested round trip delay.
BTS 3 BTS 2
DAISY CHAIN CLOSED LOOP
BTS 4 BTS 10
BRANCH OF THE DAISY CHAIN
BTS 1
BTS 6
BSC
BTS 5
MSC
DAISY CHAIN CLOSED LOOP
BTS 11 BTS 7
SINGLE MEMBER DAISY CHAIN, A STAR
BTS 9
BTS 8
Figure 2-4 Closed loop and open ended daisy chains
Daisy chain planning

The introduction of multiple E1 or T1 circuits and branches increases the complexity of the network topology. Since the network can have multiple E1 or T1 circuits, branches, multiple paths over the same E1 or T1 circuit, and closed loop interconnections, each E1 or T1 circuit should be individually planned.
26
14th Apr 00
GSM-001-103
Network topology
Simple daisy chain

A daisy chain with no branches and a single E1 or T1 circuit between each of the BTSs is referred to as a simple daisy chain, a simple daisy chain is shown in Figure 2-5. The maximum capacity supported in this connection is limited by the capacity of the connection between the BSC and the first BTS in the chain.
Tx
Rx
Tx
Rx
BSC
Rx Tx
BTS 1
Rx Tx Rx
BTS 2
Tx
Tx
Rx Tx
Rx
USED IN CLOSED LOOP CONNECTION ONLY
BTS 3
Rx Tx
BTS 4
... ... ... ...

Tx Rx Rx Tx
BTS X
Figure 2-5 Simple daisy chain The capacity of a closed loop single E1 or T1 circuit daisy chain is the same as that for an open ended daisy chain. The closed loop daisy chain has redundant signalling links for each BTS, although they transverse the chain in opposite directions back to the BSC. Maximum carrier capacity of the chain, with one signal link per BTS site is given by: n+ for E1 links n+ for T1 links. Where: n b is: the number of carriers. the number of BTS sites in the chain. 24 b 2 31 b 2
The results should be rounded down to the nearest integer.
Example
A single E1 circuit daisy chain with three BTSs, the maximum capacity of the chain is given by: 31 3 + 14 carriers 2 A single T1 circuit daisy chain with three BTSs, the maximum capacity of the chain is is given by: 24 3 + 10 carriers 2 These carriers can be distributed between the three sites. If the loop is closed, the BSC has additional signalling links, although the same number of carriers are supported.
14th Apr 00
27
Network topology
GSM-001-103
Daisy chain with branch BTS site

The addition of a branch BTS site (BTS Y), as shown in Figure 2-6, affects the capacity of the links between the BSC and the site from which the branch originates as these are used for the path to the branched site.
Tx
Rx
Tx
Rx
BSC
Rx Tx
BTS 1
Rx Tx
BTS 2
Rx Tx
Tx
Rx Tx
Rx
Tx
Rx
BTS 3
Rx Tx
BTS 4
Rx Tx
BTS X
USED IN CLOSED LOOP CONNECTION ONLY
Rx
BTS Y
Tx
Figure 2-6 Daisy chain with branch A branch may have multiple BTS sites on it. A branch may be closed, in which case there would be redundant signalling links on different E1 or T1 circuits. In a closed loop, which requires redundant signalling links for each BTS site, with an open branch, the E1 or T1 circuit to the branch needs to carry redundant signalling links.
28
14th Apr 00
GSM-001-103
Network topology
Aggregate Abis
This is an option designed to allow greater flexibility when network planning. It can also help reduce leasing costs of E1/T1 links by optimizing the link usage over the greatest distance between a BSC and BTS. This is achieved by the introduction of third party multiplexer equipment enabled by Motorola software. This equipment allows timeslots on one E1/T1 link to be multiplexed to more than one BTS. Therefore if the situation arises where several single carrier BTSs would each require their own dedicated E1/T1 link, greatly under utilizing each link capacity. Now providing the geographical locations of the sites and distances of the E1/T1 links work out advantageously, it is possible to send all the traffic channels for every site initially over one E1/T1 link to the third party multiplexer and then distribute them over much shorter distances to the required sites. Providing the distance between the BSC and the multiplexer site is sufficiently large this should result in significant leasing cost savings over the original configuration. Below are two diagrams illustrating the before (Figure 2-7) and after (Figure 2-8) scenarios.
BSC
5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED
BTS
TWO CARRIER ONE RSL
BTS
TWO CARRIER ONE RSL 5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED
BTS
TWO CARRIER ONE RSL
Figure 2-7 Typical low capacity BSC/BTS configuration
14th Apr 00
29
Network topology
GSM-001-103
BSC
MORE EFFICIENT USE OF LONGEST E1/T1 LINK
TWO CARRIER ONE RSL 5x64 kbit/s TIMESLOTS USED 26x64 kbit/s TIMESLOTS UNUSED E1/T1 MULTIPLEXER 10x64 kbit/s TIMESLOTS USED 21x64 kbit/s TIMESLOTS UNUSED
BTS
TWO CARRIER ONE RSL
BTS
BTS
TWO CARRIER ONE RSL
BTS
TWO CARRIER ONE RSL
Figure 2-8 Example using a switching network Another advantage of introducing the multiplexer is the improvement in the timeslot mapping onto the Abis interface. Currently they are allocated from timeslot 1 upwards for RSLs and timeslot 31 downwards for the RTF traffic channels. Most link providers lease timeslots in contiguous blocks (that is, no gaps between timeslots). Under the existing timeslot allocation scheme it often means leasing a whole E1/T1 link for a few timeslots. There is a new algorithm for allocating timeslots on the Abis interface. This is only used on the links connected directly to the new aggregate service, on the other links the existing algorithm for allocating timeslots is used. Under the new software the timeslots are allocated from timeslot 1 upwards, The RSLs allocated first and the RTF timeslots next with each site being equipped consecutively, thus allowing contiguous blocks of timeslots to be leased. It is important that the sites are equipped in the order that they will be presented, also that the RSLs are equipped first on a per site basis to coincide with the default timeslots for the software downloads to the BTSs. Figure 2-9 is an example of timeslot allocation in a network using an aggregate service, with links to the aggregate service and links by-passing it.
210
14th Apr 00
GSM-001-103
Network topology
NEW ALGORITHM 1 2 3 4 5 RSL1 RTF1 RTF1 RTF2 RTF2 6 7 8 9 10 11 12 13 14 15 RSL2 RTF3 RTF3 RTF4 RTF4 RSL3 RTF5 RTF5 RTF6 RTF6 16 17 18 19 20 RSL4 RTF7 RTF7 RTF8 RTF8
BSC
ORIGINAL ALGORITHM 1 31 30 29 28 RSL3 RTF5 RTF5 RTF6 RTF6
ALLOCATION UNAFFECTED
ALLOCATION AFFECTED NEW ALGORITHM 1 2 3 4 5 E1/T1 MULTIPLEXER ALLOCATION AFFECTED RSL3 RTF5 RTF5 RTF6 RTF6 6 7 8 9 10 RSL4 RTF7 RTF7 RTF8 RTF8
ALLOCATION AFFECTED
BTS 1
TWO CARRIER ONE RSL 1 2 3 4 5 RSL1 RTF1 RTF1 RTF2 RTF2
BTS 3
ORIGINAL ALGORITHM
NEW ALGORITHM 1 2 3 4 5 RSL2 RTF3 RTF3 RTF4 RTF4 ALLOCATION AFFECTED
NEW ALGORITHM
1 31 30 29 28
RSL4 RTF7 RTF7 RTF8 RTF8
ALLOCATION UNAFFECTED
BTS 2
BTS 4
Figure 2-9 Timeslot allocation using new and old algorithms Similar problems can be encountered when equipping redundant RSL devices onto paths containing aggregate services. Because of the new way of allocating timeslots when connecting to a aggregate service from timeslot 1 upwards there is no way of reserving the default download RSL timeslot. This gives rise to the situation where the default RSL timeslot has already been allocated to another device, RTF for example. To avoid this happening the primary and redundant RSLs can be equipped first (in an order that results in the correct allocation of default RSL timeslots), or reserve the default download RSL timeslot so that it may be allocated correctly when the primary or redundant RSL is equipped. If it is envisaged to expand the site in future to preserve blocks of contiguous timeslots on the links, it is possible to reserve the timeslots needed for the expansion so that they can be made free in the future.
14th Apr 00
211
Network topology
GSM-001-103
Alarm reporting
This feature has an impact on the alarm reporting for the E1/T1 links. If the link is connected to a third party switching network and is taken out of service, the BTS will report the local alarm, but the remote alarm will only go to the third party aggregate service supporting the E1/T1 link. There may also be a case where the internal links within the E1/T1 switching network fail, causing the RSL to go out of service with no link alarms generated by GSM network entities (BTS, BSC). In these cases it is the responsibility of the third party aggregate service provider to inform the users of the link outage. The only indication of failure is the RSL state change to out of service. Figure 2-10 shows a possible network configuration using several switching networks.
BSC
E1/T1 MULTIPLEXER
E1/T1 MULTIPLEXER
BTS
BTS
BTS
BTS
BTS
BTS
BTS
BTS
E1/T1 MULTIPLEXER
E1/T1 MULTIPLEXER
BTS
BTS
BTS
BTS
Figure 2-10 Alternative network configuration with E1/T1 switching network
Restrictions/limitations
The ability to nail path timeslots along a link containing an E1/T1 switching network is supported. The user is still able to reserve, nail and free timeslots. The maximum number of sites within a path is ten, for E1/T1 networks. Even though it is a pseudo site, the aggregate service is counted as a site in the path. Hence the number of BTSs that can be present in a path is reduce from ten to nine. GCLK synchronization functions, but any BTS sites connected downlink from a switching network will synchronize to it and not the uplink GSM network entity (BTS, BSC).
212
14th Apr 00
GSM-001-103
Network topology
RTF path fault containment

Each radio at a BTS requires a receive/transmit function enabled which tells it various operating parameters to use. These include the ARFCN, type of carrier and primary/secondary path among others. It is the path that is of concern here. An RTF may be assigned different paths. The path is the route which the two 64 kbit/s timeslots assigned to the radio from the E1/T1 link, take to get to and from the BTS/BSC. Each RTF can be assigned a different path for its two timeslots, even RTFs that are in the same cell. One path is designated the primary the other the secondary. In the event of the primary path failing, the RTF would choose secondary path and the carrier would remain in call processing. At present, if all the paths to one RTF fail, the whole cell will be taken out of call processing, regardless if there are other radios/RTFs with serviceable paths in the same cell. This feature allows the cell to remain in call processing if the failure of all paths to one RTF occurs, as described in the previous paragraphs. Any call in progress on the failed path would be handed over to the remaining RTFs in the same cell, if there were available timeslots. If there were not enough available timeslots, the call would be released. Also the timeslots on the radio of the failed path would be barred from traffic until the path was re-established, but any SDCCHs on the carrier would remain active. If all paths to all RTFs in an active cell have failed and there is still an active RSL, then the cell will be barred from traffic.
Advantages
By using this feature, and removing any redundant paths that would normally be equipped to manage path failure, the customer could save on timeslot usage. Figure 2-11 shows the conventional redundant set-up, requiring in this case four extra timeslots to provide for redundant paths. Figure 2-12 shows the configuration using the new software, which if one RTF path fails will allow call processing to continue via the other path, though with reduced capacity. This configuration only requires four timeslots instead of eight for Figure 2-11. The customer has to weigh up the cost saving advantages of the new software against the reduced capacity in the event of failure of a RTF path.
14th Apr 00
213
Network topology
GSM-001-103
BSC
RTF1 EQUIPPED ON PATH 1 (2 TIMESLOTS) RTF1 EQUIPPED ON PATH 2 (2 TIMESLOTS)
BTS 3
BTS 1
RTF2 EQUIPPED ON PATH 1 (2 TIMESLOTS)
BTS 2
Figure 2-11 A configuration with a BTS equipped with two redundant RTFs
BSC
BTS 3
BTS 1
BTS 2
Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs
214
14th Apr 00
GSM-001-103
Network topology
16 kbit/s RSL
The purpose of the 16 kbit/s RSL is to reduce the transmission costs between the BSC and BTS (Abis interface) for single carrier sites in particular. At present, a single carrier BTS requires three E1/T1 64 kbit/s timeslots; one for the 64 kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslots dedicated 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 the two 64 kbit/s timeslots the reason is that, in the case of a single carrier site, the carrier will be the BCCH carrier and the air interface timeslot zero of the BCCH carrier is reserved 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 the Abis interface to the dedicated radio for transmission. Due to this the traffic channel on the Abis interface corresponding to the timeslot zero on the air interface is unused and available to bear signalling traffic. This results in one 16 kbit/s sub-channel unused on the Abis interface, a waste of resources. With the introduction of the 16 kbit/s RSL it is possible to place it on this unused sub-channel because the RSL is not transmitting on the air interface. The advantage is that it frees up one 64 kbit/s timeslot on the Abis interface reducing the requirement to serve a single carrier system to only two 64 kbit/s timeslots. This operates with M-Cell BTSs and InCell BTSs using KSW switching. Figure 2-13 (Fullyequipped RTF) and Figure 2-14 (Sub-equipped RTF) show the eight types of RTF which are possible using the above options. They are shown in Table 2-2: Table 2-2 RTF types Type 1 2 3 4 5 6 7 8 Options A fullyequipped BCCH RTF with an associated 16 kbit/s RSL. A fullyequipped BCCH RTF with no associated 16 kbit/s RSL. A fullyequipped non-BCCH RTF with an associated 16 kbit/s RSL. A fullyequipped non-BCCH RTF with no associated 16 kbit/s RSL. A sub-equipped BCCH RTF with an associated 16 kbit/s RSL. A sub-equipped BCCH RTF with no associated 16 kbit/s RSL. A sub-equipped non-BCCH RTF with an associated 16 kbit/s RSL. A sub-equipped non-BCCH RTF with no associated 16 kbit/s RSL.
14th Apr 00
215
Network topology
GSM-001-103
Fully equipped RTF
FULLY EQUIPPED RTF
BCCH
NON-BCCH
16 kbit/s BTS only ASSOCIATED 16 kbit/s RSL NO ASSOCIATED 16 kbit/s RSL
Configuration Timeslot X Timeslot Y
KEY
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 voice traffic. Figure 2-13 Fullyequipped RTF
216
14th Apr 00
GSM-001-103
Network topology
Sub-equipped RTF
SUB-EQUIPPED RTF
BCCH
NON-BCCH
Configuration Timeslot X Timeslot Y
KEY
16 kbit/s sub-channel used for 16 kbit/s RSL. 16 kbit/s sub-channel available for voice traffic. Figure 2-14 Sub-equipped RTF
Planning constraints
The following RSL planning constraints apply: S S S S S S S S S S S S A BTS shall support either 16 kbit/s RSLs or 64 kbit/s RSLs, not both. A BSC shall support both 16 kbit/s and 64 kbit/s RSLs. A BSU based BTS shall support up to eight 16 kbit/s RSLs. Up to two 16 kbit/s RSLs shall be supported by M-Cellmicro, M-Cellcity, and M-Cellarena. Up to six 16 kbit/s RSLs shall be supported by M-Cell6. Up to four 16 kbit/s RSLs shall be supported by M-Cell2. The BTS and BSC shall support a mix of both fully equipped and sub-equipped RTFs. A ROM download will be carried out over a 64 kbit/s RSL, even at a site designated a 16 kbit/s RSL. A CSFP download shall utilize a 16 kbit/s RSL at a 16 kbit/s designated site. A KSW must be used at an InCell BTS where a 16 kbit/s RSL is equipped. The 16 kbit/s RSL shall only be able to be configured on CCITT sub-channel three of a 64 kbit/s E1/T1 timeslot for BSU based sites. An associated 16 kbit/s RSL shall be supported on redundant RTF paths where one exists on the primary path.
14th Apr 00
217
Network topology
GSM-001-103
16 kbit/s XBL
The 16 kbit/s XBL has been introduced to provide a lower cost solution to the customer by reducing the interconnect costs between an RXCDR and BSC. This is achieved by reducing the XBL data rate from its current 64 kbit/s to 16 kbit/s. This frees three 16 kbit/s sub-channels on the E1/T1 64 kbit/s timeslot to enable them to be used as TCHs. The maximum number of XBLs able to be configured between a single BSC and RXCDR remains the same as before, at two, with a total number of XBLs to an RXCDR of ten. There is no restriction on which timeslot an XBL can be configured. It will be possible to select a rate of 16 kbit/s or 64 kbit/s on an XBL basis, so it would be possible to have two different rates at the same BSC to RXCDR, although this would not be considered a typical configuration. As a result of the introduction of the 16 kbit/s RSL there will be no reduction in processing capacity of the BSC or RXCDR.
BSC
XBL
XBL
BSC
XBL
XBL
BSC
XBL
XBL
RXCDR
BSC
XBL
XBL
BSC
XBL
XBL
MAXIMUM OF TWO XBLs BETWEEN THE BSC AND XCDR OF EITHER 64 kbit/s OR 16 kbit/s ON THE E1/T1 LINK. MAXIMUM OF TEN XBLs PER RXCDR.
Figure 2-15 16 kbit/s XBL utilization
218
14th Apr 00
GSM-001-103
BTS concentration
BTS concentration
Introduction
The BTS Concentration feature is intended to reduce the number of BTSBSC terrestrial backhaul resources that are planned on the E1/T1 link between the BTS and BSC. This new feature is made possible by dynamically allocating terrestrial backhaul resources for the BTS radio channels, referred to as radio transmit function (RTF) resources, instead of making static assignments on a one for one basis. With this new feature, it will be very common to deploy more BTS carrier equipment (RTFs), for coverage purposes, than deployed terrestrial backhaul resources. This new planning approach takes advantage of the trunking efficiencies gained by sharing terrestrial backhaul resources among multiple BTS RTFs. It is expected that this feature will be particularly useful for in-building systems. Prior to the introduction of this feature, terrestrial backhaul resources were statically allocated when RTFs were equipped. This feature preserves the existing mechanism (static allocation), but allows the operator the choice, on a per BTS site basis, of whether to use the existing mechanism, or the new dynamic allocation method. The BTS Concentration feature is particularly useful when a large BTS daisy chain configuration is planned. For a daisy chain network configuration using E1s, there can be up to ten BTS sites connected together in a serial fashion to a serving BSC. The BTS Concentration feature will greatly increase the terrestrial backhaul trunking efficiency in this large network configuration by allocating E1/T1 16 kbit/s backhaul resources over the entire daisy chain complex instead of allocating resources on a per BTS site basis. The BTS Concentration feature introduces a new device referred to as the DYNET device. The control of the DYNET device enables a network operator to configure the dynamic allocation of terrestrial backhaul resources from the BSC to BTSs. Additionally, the process of creating a DYNET will cause automatic E1/T1 PATH assignments to be made, where a PATH identifies the network topology of BSC to specific BTS connections. The DYNET is more fully described in a section to follow.
Key terms
Key networking concepts and terms used in the following sections are: network traffic load expressed in Erlangs, network blocking expressed as grade of service (GOS), and Network traffic modeling using the Erlang B formula. The concepts and terms that will be used to describe the BTS Concentration feature are defined below. Table 2-3 BTS Concentration concepts and rules Terminology BTS Concentration Feature Definition This is a software feature that can be installed on BTSs supporting switching of 16 kbit/s backhaul resources. It enables the terrestrial backhaul to be most efficiently planned by Dynamically Allocating these resources and requires a significant software component to be installed on the BSC. A BTS site may have one or more BTS Cells collocated at the same site. The radio signalling link (RSL) planning is performed on a per BTS site basis. This is either an E1 or a T1 communication link between the BTS site and the BSC. Additionally, this communication link could be a daisy chain through multiple BTS sites connected to a serving BSC.
BTS site
BTSBSC E1/T1
14th Apr 00
219
BTS concentration
GSM-001-103
Common pool
DYamic NETwork (DYNET) Device
Dynamic Allocation
Erlang
Erlang B
Grade of Service (GOS)
PATH devices
Radio Signalling Link (RSL)
Radio Transmit Function (RTF) Reserved Allocation
Reserve pool
The common pool refers to the pool of resources that are available for unrestricted assignment on the BTSBSC E1/T1 link to any cell or site requesting terrestrial backhaul resources. This is a new device created for the BTS Concentration feature. A DYNET device is used to specify the BTS sites sharing of dynamic resources and how they are interconnected. When a DYNET is equipped, using the equip command, the PATH devices for the BTSs that support dynamic allocation are also equipped. See the DYNET section for more details. This is the way the BTS Concentration feature allocates terrestrial backhaul between the BSC and BTS site on an as needed basis. The Erlang is a measure of traffic loading; (for example, the percentage of time that a resource (channel or link) is busy). One Erlang represents 3600 call-seconds in a one hour time period. This is equivalent to one call holding a circuit for one hour. Typically a cellular call is held in the range of 120 seconds. A 120 second hold time would correspond to 33 milli-Erlangs (0.033 Erlangs). Erlang B refers to the call model used to determine the number of circuits required in order to satisfy a given GOS and call load measured in Erlangs. The formula is based on a call arrival rate with a Poisson probability distribution. The GOS is specified in percent. A 1% GOS means that, on average, 1 call out of 100 calls will be blocked, often referred to as a 1% blocking rate. Typically, a 1% GOS is a desirable terrestrial backhaul design goal. This term refers to the E1/T1 connectivity from the BSC to the BTS site or multiple BTS sites in the case of a BTS daisy chain. This is the signalling link between the BSC and BTS. It can be allocated 16 kbit/s or 64 kbit/s resources over the E1/T1. Each BTS site has at least one 16 kbit/s or 64 kbit/s RSL, and more than one can be allocated per BTS up to a maximum number specified by each individual BTS product. An RTF corresponds to one BTS carrier which can support up to a quantity of eight 16 kbit/s backhaul resources. The BTS Concentration feature permits the Reserved Allocation of terrestrial backhaul resources. For example, in a daisy chain of BTS sites, each cell in a BTS site can have a reserved number of terrestrial backhaul resources that cannot be allocated to the other BTS cells or to other BTS sites in the daisy chain. The reserved pool is a term used to describe the number of available terrestrial backhaul resources that can be used by a specific BTS cell and cannot be dynamically allocated to another cell.
220
14th Apr 00
GSM-001-103
BTS concentration
Static Allocation
Subrate switching Terrestrial Backhaul
Timeslot (TS) 64 kbit/s
Traffic Channel (TCH) 16 kbit/s
Transcoder Rate Adaptation Unit (TRAU)
Prior to the introduction of the BTS Concentration feature, the allocation of resources over the BTSBSC E1/T1 link was by the use of the Static Allocation. Static Allocation permits up to eight (sixteen with redundancy) terrestrial backhaul resources to be assigned directly to one BTS RTF resource. Subrate switching is the capability to switch 16 kbit/s backhaul resources. The term terrestrial backhaul is used in the description of the BTS Concentration feature to describe the resources that are available over the BTSBSC E1/T1 link or Abis Interface. An E1 link is comprised of 32 64 kbit/s time slots, of which up to 31 can be allocated to voice traffic and to RSL signaling channels. A T1 can be allocated with up to 24 64 kbit/s time slots. Each E1/T1 time slot can carry up to 4 calls at 16 kbit/s per traffic channel. When terrestrial backhaul is used in the more general sense, the term additionally refers to the E1/T1 links between the BSC and RXCDR and to the links between the RXCDR and the MSC. A timeslot is one 64 kbit/s channel on an E1 or T1 as provided by terrestrial backhaul. A timeslot can carry up to 4 16 kbit/s traffic channels. The term TCH refers to the BTS radio air interface traffic channel. The bandwidth required to carry one cellular call over the terrestrial backhaul, in support of the TCH, is 16 kbit/s. The TRAU corresponds to one transcoding hardware unit per traffic channel. The TRAU hardware unit processes TRAU frames from the BSS and performs the bidirectional conversion to PCM frames for transmission to the MSC. TRAU hardware allocation is not performed by the BSC as part of the dynamic allocation of terrestrial backhaul resources. Instead, TRAU allocation is performed when the MSC allocates a link from the MSC to the RXCDR, then to the BSC for a specific call.
DYNET new device

DYNET description
To support the functionality of this feature, a new device has been added, the DYNET device. A DYNET device is used to specify the BTSs sharing dynamic resources and how they are interconnected. This device exists as a construct to specify a BTS network and does not exist as a managed device. A DYNET may be equipped or unequipped, but may not be locked, unlocked, or shut down. If third party timeslot multiplexer sites, or marker sites, are used, they may be included in the definition of a DYNET. All DYNETs that share the same first identifier must have exactly the same BTSs, or marker sites, in the same order. These DYNETs must also have different links used by the BTSs that use dynamic allocation within a BTS network. These limitations allow multiple link BTS networks to be defined for sharing purposes, whilst limiting the configuration to simplify sharing.
14th Apr 00
221
BTS concentration
GSM-001-103
Equipping DYNETs and PATHs

When a DYNET is equipped, using the equip command, the PATH devices for the BTSs that support dynamic allocation are also equipped. PATH devices are not automatically equipped for BTSs that do not support dynamic allocation. A PATH equipped for a non closed loop daisy chain has a second identifier equal to the second identifier of the DYNET multiplied by two. In the case of a closed loop daisy chain, an additional PATH device is equipped automatically. This has a second identifier one greater than the second identifier of the first automatically equipped PATH device. NOTE The indentifiers of the PATHS automatically equipped when a DYNET is equipped are not allowed to be used when equipping the PATH device. The amount of resources reserved for dynamic allocation is set to zero timeslots when the DYNET is initially equipped.
Equipping RSLs
RSLs for BTS sites that support dynamic allocation must be equipped to the automatically equipped PATHs associated with the DYNET.
Blocking considerations
Dynamic allocation allows greater RF Channel capacity to be equipped (RTFs) than there are terrestrial backhaul resources, whether at a BTS site, or within a BTS dynamic network. This allows RTF equipage for coverage purposes rather than for network capacity purposes. Additionally, the dynamic allocation method allows terrestrial backhaul resource capacity to move dynamically between radio units in the same network based upon traffic considerations. The system planner needs to be aware that if enough users try to gain access to a system planned with many more RTFs than terrestrial backhaul resources, some of the call attempts will be blocked because of the limited number of terrestrial backhaul resources.
Blocking control
The BTS Concentration feature provides a facility to reserve terrestrial backhaul resources on a per BTS cell basis along with the dynamic allocation of these resources. This reservation capability can be used to ensure that any given BTS cell has some E1/T1 resources available independent of the other BTS cells or other BTS site traffic loads, thereby providing a guaranteed method of blocking control. However, the best use of terrestrial backhaul resources is obtained by statistically planning the network, using the dynamic allocation method to achieve a low blocking probability (a good GOS).
222
14th Apr 00
GSM-001-103
BTS concentration
Reserved allocation algorithm

The feature allows reserved resources to be allocated to specific cells. In configuring a network with BTS concentration, a pool of terrestrial backhaul resources must be set aside for dynamically allocating to the relevant cells/BTS sites. This pool is called the dynamic pool in the following discussion. In addition, the feature allows each cell to specify an amount of reserved resources, which are taken (dynamically allocated) from the dynamic pool. Once a number of resources are reserved for a cell, these resources are allocated specifically to the cell and, therefore, are not available for sharing. To facilitate this discussion from the planning perspective, imagine that there is a common pool that holds the remaining resources in the dynamic pool after resources are reserved for specific cells. Figure 2-16 shows what the dynamic pool of terrestrial backhaul resources consists of from the planning perspective: a common pool and n reserved pools, one for each BTS site. Each reserved pool consists of the resources associated with a 16 kbit/s RSL timeslot as well as any additional resources that are specifically reserved on a per cell basis. The 16 kbit/s RSL timeslot-associated resources are shared among the cells at the BTS site, but cannot be shared with other BTS sites. The reserved pool of an individual BTS site can be set to zero. For each 16 kbit/s RSL, there will always be three resources available for reserved allocation among cells at the same site. If there are two 16 kbit/s RSL, six reserved resources are available, and so on. However, 16 kbit/s RSLs equipped for redundancy do not provide any reserved resources. For example, if there are six 16 kbit/s RSLs and three of which are for redundancy, a total of nine RSL associated resources are available to be included in the reserved pool. When a new call arrives to a cell, the BSC always first allocates a resource from the reserved pool of the corresponding BTS site. Specifically, it will first attempt to allocate a RSLassociated resource. If none is available, it allocates a resource from the additional resources specifically reserved for the cell. If all reserved resources are depleted, the BSC then allocates a resource from the common pool. If again no resource is available in the common pool, the call is blocked. If the BTS site is assigned a 64 kbit/s RSL instead of a 16 kbit/s RSL, then there are no RSL timeslot-associated resources available for dynamic allocation.
14th Apr 00
223
BTS concentration
GSM-001-103
Emergency call handling
COMMON POOL BTS site n Cell 1 additional reserved resources BTS site 1 RESERVED POOL BTS site n Cell 2 additional reserved resources BTS site 2 RESERVED POOL BTS site n Cell 3 additional reserved resources
BTS site n RESERVED POOL
RSLassociated reserved resources (Quantity = 0, 3, 6..)
Figure 2-16 A dynamic pool of terrestrial backhaul resources
With BTS Concentration, emergency calls take precedence over non-emergency calls in the allocation of terrestrial backhaul resources. The emergency calls precedence in backhaul resource allocation is independent of whether Emergency Call Pre-emption (ECP) is on or off. If no terrestrial backhaul resources are available when an emergency call requests a resource, the oldest existing non-emergency call is terminated in order to provide the needed resource. In addition, emergency calls take precedence over reserved resources allocated to specific cells. Emergency calls use whatever free terrestrial backhaul resource becomes available first. The BSC will pre-empt non-emergency calls in the same cell. The BSC next pre-empts non-emergency calls at the site. Finally, the BSC will terminate non-emergency calls from other sites within the same DYNET. If all available terrestrial backhaul resources are in use by emergency calls or if no terrestrial backhaul resources are available, then the new emergency call is blocked.
224
14th Apr 00
GSM-001-103
BTS concentration
Radio Signalling Link (RSL) planning

When a BTS daisy chain is configured during the configuration management phase, the operator has to equip each BTS site in the daisy chain at least one 64 kbit/s timeslot for RSL use. This is necessary so that when a BTS site is initialized it can communicate with the BSC at 64 kbit/s. After the initialization process concludes, the BTS site can then be allocated this 64 kbit/s E1/T1 timeslot as one 16 kbit/s RSL and three 16 kbit/s terrestrial backhaul resources. These three 16 kbit/s resources are always considered part of a reserved resources on a per site basis and can be used by any cell within a site. These three RSL associated resources may not be shared from one BTS site to another. A site always allocates RSL associated 16 kbit/s resources before allocating other reserved resources or before requesting allocation from the common pool of resources. Alternatively, the BTS site can continue to use this 64 kbit/s E1/T1 timeslot as one 64 kbit/s RSL. When the RSL is used as a 64 kbit/s signalling link, there are no RSL associated resources to be used as reserved resources at the site.
14th Apr 00
225
BTS concentration
GSM-001-103
Network topologies
BTS Concentration does not support all possible network topologies. Dynamic allocation is limited to spoke, daisy chain, and closed loop daisy chain network configurations. The following figures illustrate the network configurations to which these terms apply.
BSC
BTS 1
Figure 2-17 Spoke configuration
BSC
BTS 1
BTS 2
BTS 3
Figure 2-18 Daisy chain configuration
BSC
BTS 1
BTS 2
BTS 3
Figure 2-19 Closed loop daisy chain configuration
226
14th Apr 00
GSM-001-103
BTS concentration
Links between BTSs

Even with dynamic allocation, greater bandwidth than that provided by a single link may be required. To provide this, networks following the configurations shown in Figure 2-20, Figure 2-21, and Figure 2-22 and may have one to three links between each BTSBSC or BTSBTS pair in the configuration. The same number of links must be specified between each pair to maintain the simplicity needed to provide dynamic allocation. The following figures illustrate configurations with multiple links between BTSs.
BSC
BTS 1
Figure 2-20 Spoke configuration with three links
BSC
BTS 1
BTS 2
BTS 3
Figure 2-21 Daisy chain configuration with two links
BSC
BTS 1
BTS 2
BTS 3
Figure 2-22 Closed loop daisy chain configuration with three links This feature allows BTSs within a configuration to use the existing allocation mechanism. Such BTSs continue to reserve terrestrial backhaul resources when RTFs are equipped. Capacity in a network configuration is reserved for use for dynamic allocation by the BTSs that use dynamic allocation. This capacity forms the pool from which terrestrial backhaul resources are allocated.
14th Apr 00
227
BTS concentration
GSM-001-103
Third party multiplexer equipment

This feature supports the use of third party multiplexer equipment within a network configuration. Such equipment defines a terrestrial network outside of the knowledge of the BSS. To the BSS, this terrestrial network appears as a timeslot multiplexer site (also known as a marker site) within the BSS configuration. The following example illustrates the use of third party multiplexer equipment in a closed loop configuration.
BSC
THIRD PARTY MULTIPLEXER EQUIPMENT
THIRD PARTY MULTIPLEXER EQUIPMENT
BTS 1
BTS 2
BTS 3
Figure 2-23 Closed loop daisy chain configuration with third party multiplexer
Nailed paths
It may be required to declare additional paths to a BTS that uses dynamic allocation for nail connection purposes. This feature supports this functionality.
BSC
BTS 1
BTS 2
BTS 3
Additional path definition
Figure 2-24 Extra path definition for nailed connections Figure 2-24 shows a closed loop daisy chain with an additional path (shown as a dashed line) to BTS 2. No BSS managed resources can be placed on this additional path, it exists solely as a convenience for defining nailed connections.
228
14th Apr 00
GSM-001-103
BTS concentration

Additional functionality introduced allows the RTF to be used for non TCH channels when the path(s) for the RTF are not available, leaving the cell for the RTF in service. However, the cell is still taken out of service when all RTFs in the cell lose their paths to the BSC. A dynamic allocation site may use any of the path(s) to the site that appear in the dynamic allocation network definition. If all of these path(s) are out of service, a dynamic allocation site cannot be allocated any terrestrial backhaul resources. Hence, the cell(s) at this site are taken out of service under these conditions. Additional paths to dynamic allocation sites, as described previously, may be declared as a convenience. Since these paths are not used for terrestrial backhaul resources, their state does not influence the state of the cells at a dynamic allocation site.
14th Apr 00
229
BTS concentration
GSM-001-103
Allocating and freeing terrestrial backhaul resources

This feature attempts to minimize the BTS interaction needed to allocate or free a terrestrial backhaul resource. The terrestrial backhaul resources are initially a set of nailed connections throughout a BTS network. When a resource is allocated to a BTS, that BTS breaks its nailed connection. A connection to the TCH is made in place of the nailed connection. When the resource is freed, the BTS re-establishes the nailed connection. No change in connections is required at any other BTS in the BTS network.
BSC
BTS 1
BTS 2
BTS 3
Figure 2-25 Terrestrial backhaul resource nailed connection before a call
BSC
BTS 1
BTS 2
BTS 3
Figure 2-26 Terrestrial backhaul resource connections during a call Figure 2-26 shows a resource allocated to BTS 2. BTS 2 connects the resource to the TCH using one of the two possible paths to the BSC. BTS 2 changes the connection if the path being used fails during the call. BTS 2 connects the unused path to the Abis idle tone.
230
14th Apr 00
GSM-001-103
BTS concentration
Redundancy
This feature does not support the use of closed loop daisy chains for additional capacity when all links are available. This feature treats the closed loop nature of the closed loop daisy chain as existing for purposes of redundancy. Such a design ensures that no calls are dropped when a link becomes unavailable in a closed loop configuration. This design also simplifies the tracking of terrestrial backhaul resources. (See Figure 2-27.)
Call 2 BSC
Call 1
BTS 1
BTS 2
BTS 3
Figure 2-27 Using redundancy for extra capacity before failure
Failed link BSC
Call 1
BTS 1
BTS 2
BTS 3
Figure 2-28 Using redundancy for extra capacity after failure For the purposes of this feature, the configuration shown in Figure 2-27 is considered a closed loop daisy chain configuration.
BSC
BTS 1
Figure 2-29 Closed loop daisy chain configuration with 1 BTS The closed loop daisy chain has the potential to use the same resource in both portions of the loop. For example, in Figure 2-28, both BTS 1 and BTS 3 could be using the same resource. BTS 1 could use the resource on the link between the BSC and BTS 1. BTS 3 could use the resource on the link between the BSC and BTS 3. If either link fails, one of the calls is no longer able to use the resource.
14th Apr 00
231
BTS concentration
GSM-001-103
Performance issue
The use of satellites to carry links introduces an additional 600 millisecond one way delay to messages sent on the links. Dynamic allocation requires a BTS to BSC request and a BSC to BTS response. These messages incur an 1.2 second delay beyond the normal transmit and queuing delay times. These delay times affect call setup and handover delay times, especially if retransmission of the request/reply scenario is necessary due to message loss. This feature addresses this problem by adding an operator specified parameter that provides the retry time for dynamic allocation requests. For non-satellite systems, the retry time should be set to its minimum value. For satellite systems, the retry should be set to 1.2 seconds plus the minimum retry value. The minimum retry time chosen is 150 milliseconds to account for transmit and queuing delay times (for 16 kbit/s links, longer retry time is recommended to avoid excessive retries).
Configuration and compatibility issues

The BTS Concentration feature is supported for BSS GSR4 software releases onwards on BTS4, BTS5, BTS6, ExCell and TopCell (with TSW) and in-building picocellular system products. BTS products that support subrate switching (switching of 16 kbit/s terrestrial backhaul resources) are essential for the feature. While the feature operates on 16 kbit/s switching, it can coexist with 64 kbit/s static switching in a mixed setup. The BTS Concentration feature allows up to three E1/T1s to be allocated between the BSC and BTS site as terrestrial backhaul resources. This rule applies to all BTS products that support the BTS Concentration feature. The maximum BTS daisy chain length served by one BSC is 10 BTS sites. The BTS Concentration feature limits call congestion handling and priority call handling to radio resource call management. The existing functionality for call congestion handling, priority call handling, and emergency call handling allocates radio resources dynamically. Hence, the BTS Concentration feature interacts with these existing call handling methods because the new feature dynamically allocates terrestrial backhaul resources. The handling of emergency calls is discussed at length in the Emergency call handling section.
232
14th Apr 00
GSM-001-103
BTS concentration
Recommended BTS concentration planning guidelines

This section recommends some planning guidelines for planning the BTS Concentration feature and discusses some uses for the reserved allocation algorithm of the feature. Applications of the guidelines are illustrated by the examples in the next section. The BTS Concentration feature allows terrestrial backhaul resources to be shared among multiple BTS sites and cells (as if the resources are allocated to a common resource pool for sharing). In addition, a number of resources can be optionally reserved for specific BTS cells. It is recommended that network planning favours sharing resources and that the reserved allocation be used more sparingly, unless reserved resources are available by default due to the use of 16 kbit/s RSL (see the Radio Signalling Link Planning section in this chapter). This strategy will allow more efficient use of the terrestrial backhaul resources.
Guideline 1
For a common pool of terrestrial backhaul resources that is to be shared among a number of cells with different GOSs, enough resources should be allocated to meet the most stringent GOS among all relevant cells. This guideline addresses the case when a daisy chain is planned and not all of the BTSs in the daisy chain need to have the same GOS. For example, in a daisy chain of three BTS sites the planning objective may be to plan BTS 1 with a 1% GOS, BTS 2 with a 2% GOS, and BTS 3 with a 1% GOS. However, when the BTS Concentration feature allows terrestrial backhaul resources to be shared among these three BTS sites, only one GOS may be used for the purposes of planning the resources. Therefore, Guideline 1 recommends that the best GOS needed in the daisy chain, that is 1% over 2%, be specified when planning. Guideline 1 is used in the first example in the following section.
Guideline 2
Due to trunking efficiency, resources are more efficiently utilized if allocated to the common pool than if reserved for individual cells. Therefore, share the resources among cells by putting as many of them in the common pool as possible. The exception to this guideline is when reserved resources are available by default; those 16 kbit/s circuits that are associated with the same timeslot (on E1 or T1) with the 16 kbit/s RSL/s. In this case, follow Guideline 3 to estimate the overflow traffic from the default reserved resources and then to determine the required number of resources in the common pool for meeting the most stringent GOS. Reserved allocation is intended only as a safeguard mechanism, as implemented in the BTS Concentration feature. Therefore, Guideline 2 recommends that the dynamic allocation from the common pool be used almost exclusively in order to minimize the required terrestrial backhaul resources.
14th Apr 00
233
BTS concentration
GSM-001-103
Guideline 3
If resources are reserved for specific cells (either by default or by design), the traffic overflowed from the reserved resources are handled by the resources in the common pool. The size of the common pool for meeting a certain GOS can be determined using the following steps: 1. 2. 3. 4. Use the Erlang B model to determine the blocking probability of the reserved resources, given the offered traffic load at each cell. The traffic overflowed from reserved resources is simply the product of the expected traffic load and the blocking probability of the reserved resources. Sum the traffic overflowed from all cells. Use the Erlang B model again to determine the number of resources needed to be in the common pool, in order to handle the total overflow traffic at the most stringent GOS requirement among all cells (according to Guideline 1).
Although the call arrival process at the resources might not be Poisson, the use of Erlang B model in steps 1 and 4 are reasonable approximations and has been verified in simulations. The application of these steps is illustrated in Examples 1 and 2 in next section.
Uses of Reserved Allocation Algorithm

The following are a few possible applications of the Reserved Allocation Algorithm, which allows the operators to reserve resources for specific BTS cells: S If there is insufficient knowledge of the traffic load on the individual BTS sites of a recently deployed network, resources may be allocated to reserved pools until some traffic statistics can be accumulated. As a transition strategy for moving from the static allocation planning method to the dynamic allocation of terrestrial backhaul resources out of a common resource pool, the BTS Concentration feature can be added to an existing network and then planned by allocating resources to only the reserved pools resulting in no effective change in the planned terrestrial backhaul resources. A follow-up planning process can later be taken to take advantage of dynamic allocation of terrestrial backhaul resources out of a common resource pool. Suppose in an existing system with BTS concentration, better GOSs are deemed necessary for some specific and important cells, but for whatever reason it is not feasible to immediately deploy more terrestrial backhaul resources to the common pool to achieve the required GOSs. A possible strategy might be to re-allocate some resources from the common pool to the reserved pools of the important cells to improve their GOSs. However, as a trade-off, reducing the size of the common pool will result in worst GOS for the other cells that rely on the common pool. Nonetheless, the more extensive use of the reserved pool could be considered a transition strategy until more terrestrial backhaul resources become available.
234
14th Apr 00
GSM-001-103
BTS concentration
Examples
The following examples provide a better understanding for how the guidelines in the previous section might be applied when planning a network with the BTS Concentration feature. The first two examples, Examples 1 and 2, demonstrate the trunking efficiency gained by the BTS Concentration feature as well as the use of Guidelines 1, 2, and 3. Additionally, Guideline 2 is applied by limiting the use of reserved facilities to only those reserved facilities that are planned as part of the RSL 64 kbit/s timeslot. The third example, Example 3, demonstrates the case when a combination of reserved resources and call loading causes blocking to occur at a particular cell, even though there is still some terrestrial backhaul resource available. All examples are worked using the Erlang B formula/model.
Example 1
The number of required 16 kbit/s terrestrial backhaul resources between the BSC and BTS or daisy chain of BTSs depends on the amount of traffic (in Erlangs) expected at each BTS cell/site and the blocking probability for the resources. (A new call is blocked when all resources have been allocated to other on-going calls.) This example illustrates how planning can be carried out. The DYNET in Figure 2-28 is used in the examples and each BTS site is assumed to have only one cell. Suppose 3 Erlangs of traffic is expected to come through the cell in BTS 1, 2 Erlangs through BTS 2, and 5 Erlangs through BTS 3. NOTE It is important not to confuse the blocking at the terrestrial backhaul resources with the blocking at the channels over the air (TCHs) and the blocking at the links between a MSC and a BSC. If choosing to share the pool of terrestrial backhaul resources freely among all BTSs, and to allow an 1% blocking probability for these resources, a total of 18 resources are needed to handle the 10 Erlangs of expected traffic, according to Erlang B formula. However, to reserve some resources for each BTS site, to provide the required blocking probability, calculate the required number of resources for each BTS site. Assume that the desired blocking probabilities for the terrestrial backhaul resources are 1%, 2% and 1% for BTS 1, BTS 2 and BTS 3, respectively. Again, using the Erlang B formula, reserve eight resources to handle the 3 Erlangs of expected traffic through BTS 1 with 1% blocking. Also reserve six resources to handle the 2 Erlangs through BTS 2 at 2% blocking. Finally, 11 resources are needed at BTS 3 to handle the 5 Erlangs at 1%. Therefore, 25 resources in total are needed. Table 2-4 summarizes these key results.
14th Apr 00
235
BTS concentration
GSM-001-103
BTS 1 2 3 Total (100% reserved) Total (100% common) NOTE
Table 2-4 Summary of required resources Expected Traffic Blocking Probability Required number of (Erlangs) (GOS) resources 3 1% 8 2 2% 6 5 1% 11 10 25
10
1%
18
The expected traffic refers to the amount of traffic arriving at the backhaul resources. Since the limited number of TCHs gives rise to another level of blocking (GOS), the traffic expected at the backhaul resources is in general smaller than the traffic generated by the subscribers. For example, with 1% blocking at the TCHs, on average only 99% of the traffic make it to the backhaul resources. Therefore, the expected or offered traffic at the backhaul resources is the product of the expected traffic from the subscribers and (1 blocking probability). Note that when the 100% reserved planning approach is used, more resources (25 instead of 18) are required and, in addition, BTS 2 is planned at a higher blocking (a worse GOS). This example demonstrates the power of trunking efficiency and the reason why allocation to the common pool should be favoured over allocation to the reserved pool when planning terrestrial backhaul resources for individual BTS sites or cells. Reserving terrestrial backhaul resources for individual cells, however, does isolate the cell from the statistical traffic fluctuation of other cells. When other cells experience higher call arrivals than average, a cell with its own n reserved terrestrial backhaul resources will never be in a situation where all its calls are blocked. The cell is guaranteed that it has at least n ongoing calls before a new call is blocked. The tradeoff, however, is that a greater number of terrestrial backhaul resources are necessary. As described in the Radio Signalling Link Planning section in this chapter, some reserved resources may exist by default if 16 kbit/s RSLs are used at the BTS site. The 16 kbit/s backhaul resources associated with the same timeslot on the E1/T1 as the 16 kbit/s RSL are considered reserved resources for all cells in the BTS site. Suppose each of the BTS 1 and BTS 2 in this example uses one 16 kbit/s RSL and, therefore, each has three backhaul resources available by default. Follow Guideline 3 to determine the number of resources needed in this situation: 1. For BTS 1, given that it has three reserved resources and 3 Erlangs of offered traffic, the calculated blocking probability for the resources is 0.35. Similarly, for BTS 2, three reserved resources handling 2 Erlangs gives a blocking probability of 0.21. The traffic overflowed from the reserved resources is 3 x 0.35 = 1.04 Erlangs for BTS 1 and is 2 x 0.21 = 0.42 Erlangs for BTS 2. The total traffic to be handled by the common pool is, therefore, the sum of the overflow traffic from BTS 1 and BTS 2 and the 5 Erlangs from BTS 3. The sum turns out to be 6.46 Erlangs System Information: BSS Equipment Planning 68P02900W21-G
14th Apr 00
2. 3.
236
GSM-001-103
BTS concentration
4.
Using the Erlang B model, the calculated common pool needs to have 13 backhaul resources in order to meet the 1% GOS.
As a result, a total of 19 resources are needed in this case. Although this approach requires one more resource than the 100% common allocation approach, six of the resources are available by default. Only 13 additional resources are really needed. In summary, it has been demonstrated that the 100% reserved approach resulted in less efficient use of resources and, therefore, required the most number of resources to meet the design requirements. The 100% common approach resulted in the most efficient utilization of resources. However, if reserved resources are readily available, using the planning approach given in Guideline 3 can make use of them and reduce the number of additional resources needed to be provisioned. (See Table 2-5.) Table 2-5 Summary of common pool planning when BTSs 1 and 2 have reserved resources BTS Offered traffic (Erlangs) 3 2 5 Number of reserved resources 3 3 0 Blocking probability for reserved 0.35 0.21 Overflowed traffic from reserved (Erlangs) 1.04 0.42 5 6.46 Number of resources needed in common pool to meet 1% GOS = 13 Therefore, the total number of resources, including reserved = 19
1 2 3
14th Apr 00
237
BTS concentration
GSM-001-103
Example 2
As Example 2 demonstrates, the trunking efficiency gain by the BTS Concentration feature can be rather significant. To show the advantage in a large system, this example looks into the planning of BTS Concentration for a daisy chain of 10 single-cell BTS sites. The following table summarizes the expected amount of traffic at the backhaul resources and the GOS requirement associated with each cell. Table 2-6 Summary of traffic and GOS requirements Expected Traffic Blocking Probability Required number of (Erlangs) (GOS) resources 5 1% 11 10 1% 18 15 1% 24 20 1% 30 25 1% 36 30 1% 42 35 1% 47 40 1% 53 50 1% 64 60 1% 75 290 400
BTS 1 2 3 4 5 6 7 8 9 10 Total (100% reserved) Total (100% common)
290
1%
314
Table 2-6 also shows the results of the 100% reserved and 100% common planning approaches (the rightmost column). The total traffic load of the 10 BTS sites is 290 Erlangs. If each BTS resource allocation is planned as in the static allocation or 100% reserved methods (resources are actually reserved for the cell in the corresponding BTS site, since they are reserved on a per-cell basis), the resources that need to be planned over the terrestrial backhaul are 400. However, if the resource allocation is performed over all 10 BTS sites, the number of required terrestrial backhaul resources drops to 314, a saving of 86 resources. The saving of 86 resources is significant because, without it, the daisy chain would have required 400 resources (using the 100% reserved approach) and would not be able to fit into three E1 links, the most a DYNET can have. Note that three E1 links together can provide only 372 (= 3 x 31 x 4) 16 kbit/s channels, and, inevitably, some of which will be allocated for 16 and 64 kbit/s RSLs. The 100% common approach of planning BTS Concentration reduces the number of required resources and makes it possible to offer 1% blocking to the entire daisy chain with three E1 links. To expand this example further, assume that each BTS site has some default reserved backhaul resources ranging from 1 to 3 (see Table 2-4). Following Guideline 3, the calculation in Table 2-7 shows that about a total of 272 Erlangs of traffic will be overflowed to the common pool. Therefore, the common pool needs 295 additional resources in order to provide an 1% GOS, making a total of 315 backhaul resources in this scenario.
238
14th Apr 00
GSM-001-103
BTS concentration
Table 2-7 Summary of common pool planning when BTSs have reserved resources BTS Offered traffic (Erlangs) 5 10 15 20 25 30 35 40 50 60 Number of reserved resources 3 3 3 2 2 2 2 1 1 1 Blocking probability for reserved 0.53 0.73 0.81 0.90 0.92 0.94 0.94 0.98 0.98 0.98 Overflowed traffic from reserved (Erlangs) 2.65 7.32 12.21 18.10 23.08 28.07 33.06 39.02 49.02 59.02 271.54 Number of resources needed in common pool to meet 1% GOS = 295 Therefore, the total number of resources, including reserved = 315
1 2 3 4 5 6 7 8 9 10
14th Apr 00
239
BTS concentration
GSM-001-103
Example 3
This example uses a call blocking situation in a three-cell BTS site to illustrate the operation of the BTS Concentration feature. First, the assumptions about the configuration and the state of the three-cell BTS site: S There are 24 terrestrial backhaul resources (that is six timeslots) in the dynamic pool, 12 of which are in the common pool for assignment to any of the three cells and the other 12 are reserved as illustrated in Table 2-7. All RSLs are 64 kbit/s and, hence, no RSL associated resources. Cell 1 has three calls in progress and all three calls are counted against Cell 1 reserved pool. Cell 1 cannot take any more new calls without getting resource allocation from the common pool. Cell 2 has 17 calls in progress, five of which are counted against Cell 2 reserved pool and 12 were counted against the common pool. As a result, the common pool is depleted. Cell 3 has three calls in progress, and all three calls are counted against Cell 3 reserved pool. Cell 3 has the reserved pool capacity to take one more call before needing resources from the common pool.
S S
Suppose a new call arrives to Cell 1. Since resources in both Cell 1 reserved pool and the common pool are in use, the new call attempt will be blocked. This blocking occurs even though there is one available resource in the dynamic pool. This remaining resource can only be allocated to Cell 3 since it has not used up its reserved pool. (See Table 2-8.) Table 2-8 Blocking activity Calls in Reserved Pool Progress resources 3 3 17 5 3 4
BTS 1 2 3
New Call Attempt X
Resources used out of common pool 0 12 0
240
14th Apr 00
GSM-001-103
Managed HDSL on micro BTS

Introduction
This new feature brings the benefits of full OMC Management to those products that support integrated HDSL technology. Specifically, it allows remote configuration, status, control, and quality of service information to be handled by the OMC. External HDSL modems configured as slave devices may also be managed by the same mechanism as long as they are connected to an integrated master HDSL port. This feature enables such an HDSL link to be managed entirely from the OMC. Following introduction of this feature, the initial basic version of the product will no longer be supported. NOTE To ensure compatibility, external modems should be sourced from Motorola.
14th Apr 00
241
GSM-001-103
Integrated HDSL interface

HDSL cable selection
The cabling needs to comply with the following selection guidelines: S S S S S S S Correct number of pairs for an application. Each Tip and Ring pair must be of a twisted construction. The Tip and Ring must not be mixed between the pairs, that is, Tip1 must not be used as a pair with Ring2. Either unshielded twisted pair (UTP) or shielded twisted pair (STP) may be used. The cable gauge should be between 0.4mm and 0.91mm (AWG 26 to AWG19). Attenuation at 260 kHz should be less than 10.5 dB/km. Cable runs should be limited to a length depending on the product.
Some types of cable are known to perform suitably in HDSL applications, provided they are correctly installed and the guidelines for selection and installation are observed. Recommendations for types of cable follow: S Unshielded twisted pair S BT CW1308 and equivalents. Category 3 UTP. Category 4 UTP. Category 5 UTP.
Shielded twisted pair Category 3 STP. Category 4 STP. Category 5 STP.
The performance of some types of cable is known to be unacceptable for HDSL applications. The following cable types should be avoided: S S Twisted quad cable is unsuitable for use in HDSL applications and must not be used. Drop wire that consists of two parallel conductors with supporting steel cable. This will work with HDSL but because it is not twisted, it provides little immunity from noise, and is therefore not recommended. Information cable is typically of non-twisted, multicore construction, for example ribbon cable. Its use is not recommended.
242
14th Apr 00
GSM-001-103
HDSL cable installation

If cabling does not exist between two end sites, guidelines follow for the installation of cable, that must meet the selection guidelines given above: S S S S S S S The conductor pair(s) should be connected point-to-point only, not point to multipoint. The use of different gauges of cable in one link should be avoided. Bridge taps in the cable run should be avoided. Loading coils in the cable run must be removed. The isolation between Tip and Ring should be greater than 1 M ohm (at SELV voltage levels). The isolation between Tip and earth should be greater than 1 M ohm (at SELV voltage levels). The isolation between Ring and earth should be greater than 1 M ohm (at SELV voltage levels).
HDSL range
HDSL range is affected by many factors which should be taken into account when planning the system. S S S Picocell systems should have distances of less than 1 km due to the link quality requirements of these systems. Microcell systems can have longer distances, typically 2 km or so, because of their different link error requirements. The following factors will reduce the available distances: Bridge gaps add unwanted loads on to the cables. Gauge changes add unwanted signal reflections. Small gauge cables increase the signal attenuations. Other noise sources.
HDSL is specified not to affect other digital subscriber link systems and voice traffic. NOTE However, standard E1 traffic will affect, and be affected by, HDSL systems running in the same cable binder, if unshielded from each other.
14th Apr 00
243
GSM-001-103
General HDSL guidelines

Conversion of E1 to HDSL at a site away from the BSC requires either an external modem or a microsite. It may be better to utilize the microsite to do this conversion, if possible.
E1 LINK HDSL
SLAVE EXTERNAL MODEM
Horizon micro or Horizoncompact
BSC
E1 LINK
E1 LINK
HDSL
HDSL
E1 LINK
BTS
Horizon micro Horizon micro or Horizoncompact or Horizoncompact HDSL
E1 LINK
HDSL
HDSL
M-Cell 6
M =
MASTER
S = SLAVE
Microcell BTS have a maximum of two 2.048 Mbit/s links. If the HDSL equipped version is purchased the links are automatically configured as either E1 or HDSL via a combination of database settings and auto-detection mechanisms. The setting of master/slave defaults can be changed by database settings for those scenarios, such as a closed loop daisy chain, where the defaults are not appropriate.
244
14th Apr 00
GSM-001-103
Microcell system planning

Network configurations from the BSC can be a combination of daisy chain and star. Links can be either E1 or HDSL, and can be mixed as appropriate within the network.
Daisy chain
Here a BSC connected to an external modem which then connects from its slave port to the master port of the Horizonmicro or Horizoncompact. The slave port of the M-Cellarena or M-Cellarena macro connects to the next M-Cellarena or M-Cellarena macro master port and so on, until the last M-Cellarena or M-Cellarena macro port is connected.
BSC
E1 LINK
SLAVE
HDSL
HDSL
HDSL
EXTERNAL MODEM
M =
MASTER
S = SLAVE
Star configuration
Here a BSC is again connected to an external modem which then connects from its slave port to the master port of a Horizonmicro or Horizoncompact. In this configuration an external modem is used every time a link to a Horizonmicro or Horizoncompact is used, hence the star formation.
E1 LINK
SLAVE
HDSL
EXTERNAL MODEM
BSC
E1 LINK
HDSL
E1 LINK
HDSL
M =
MASTER
14th Apr 00
245
GSM-001-103
E1 link
Here the an E1 link is used from the BSC to the first Horizonmicro or Horizoncompact, from there onwards HDSL links are used running from master to slave in each Horizonmicro or Horizoncompact; or conversion can be at any BTS, in either direction.
E1 LINK S
HDSL
HDSL
BSC
M = MASTER S = SLAVE
246
14th Apr 00
GSM-001-103
Picocell system planning

The Picocell (M-Cellaccess) system comprises a cabinet housing a maximum of two site controllers which can each control up to six single remote RF heads which operates in all frequency bands that adopt the GSM standard (GSM900 and DCS1800). The considerations for Picocell planning are: S S S S S Links are all point to point. Run from site controller to the remote RF head. Frequency bands must not be mixed on the same site controller. Can be either optical of HDSL. If HDSL, two twisted pairs of wires for each RF head. NOTE No daisy chaining of RF heads is allowed.
PCC CABINET
SITE B
RF HEAD RF HEAD SITE CONTROLLER RF HEAD RF HEAD RF HEAD RF HEAD
RF HEAD RF HEAD SITE CONTROLLER RF HEAD RF HEAD RF HEAD RF HEAD SITE A
14th Apr 00
247
GSM-001-103
248
14th Apr 00
Chapter 3
BSS cell planning
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 3 BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GSM900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The DCS1800 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The PCS1900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absolute radio frequency channel capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modulation techniques and channel spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grade of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS control channel RF provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of CCCH per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of SDCCH per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the GPRS planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview the GPRS planning process introduction . . . . . . . . . . . . . . . . . . . . . . . . . Determination of expected load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network planning flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS network traffic estimation and key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS network traffic estimation and key concepts . . . . . . . . . . Introduction to the GPRS network traffic estimation and key concepts . . . . . . . . Dynamic timeslot mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier timeslot allocation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS timeslot allocation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provisioning the network with switchable timeslots . . . . . . . . . . . . . . . . . . . . . . . . . Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Air interface planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the GPRS air interface planning process structure . . . . . . . . . . . . . . Introduction to the GPRS air interface planning process . . . . . . . . . . . . . . . . . . . . Air interface throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: throughput estimation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: throughput estimation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput estimation process: step 3 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput estimation process: step 4 (optional) . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 32 33 33 34 34 35 36 36 37 38 38 39 310 310 311 311 311 313 313 313 318 320 322 324 324 325 325 326 327 328 328 329 332 334 337 339 343 345 345 346 351 352 353 356 357
14th Apr 00
iii
GSM-001-103
Propagation effects on GSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to decibels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fresnel zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio refractive index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental effects on propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multipath propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM900 path loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path loss GSM900 vs DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency re-use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to re-use patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier/ Interference (C/I) ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other sources of interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectorization of sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overcoming adverse propagation effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error protection and detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel coding for enhanced full rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping logical channels onto the TDMA frame structure . . . . . . . . . . . . . . . . . . . Voice Activity Detection VAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuous Transmission DTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Most demanding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The microcellular solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layered Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
359 359 360 361 362 366 369 382 383 384 384 385 388 389 389 390 390 392 394 396 397 398 399 3105 3105 3106 3108 3108 3108 3109 3110 3111 3112 3112 3113 3114 3115
iv
14th Apr 00
GSM-001-103
BSS cell planning
BSS cell planning

Planning requirements
W hen planning a mobile telephone system, the aim is to create a communications network that fulfils the following requirements: S S S S Provides the desired capacity. Offers good frequency efficiency. Implemented at low cost. High grade of service.
These requirements, when analyzed, actually conflict with one another. Therefore the operating network is always a solution achieved through compromise. The cost of different network configurations can vary considerably. From an engineering point of view it would be worth while using the most frequency efficient solutions despite their high cost, but a mobile telephone network is so huge an investment that the financial factors are always going to limit the possibilities. The effect of limited funds is particularly obvious when the first stage of the network is being built. Consequently, economical planning is a condition for giving the best possible service from the start. The use of the GSM900, EGSM, and DCS1800 frequency bands, create many propagation based problems. Because the channel characteristics are not fixed, they present design challenges and impairments that must be dealt with to protect MS telephone users from experiencing excessively varying signal level and lack of voice quality. It is important to be able to predict the RF path loss between the BTS and the MS within the coverage area in different types of environment. To do this it is necessary to have knowledge of the transmitter and receiver antenna heights, the nature of the environment and the terrain variations.
14th Apr 00
31
BSS cell planning
GSM-001-103
Planning factors
When planning the network there are a number of major factors which must be considered to enable the overall system requirements to be met. 1. 2. Planning tools. GSM frequency spectrum: Modulation techniques and channel spacing. 3. Traffic capacity: Unit of measure and grade of service. 4. Capacity calculations: Typical call parameters. 5. Control channel calculations: Number of CCCH per BTS cell. Number of SDCCH per BTS cell. Control channel configurations. 6. 7. GPRS effective load. Propagation effects on GSM frequencies: Introduction to decibels. Fresnel zone Radio refractive index. Environmental effects on propagation. Multipath propagation. Free space loss. Plane earth loss. Antenna gain. Clutter factor. Power budget and system balance. 8. Frequency re-use: Re-use patterns. Carrier to interference ratio. Co-channel interference. Adjacent channel interference. Sectorization of sites. 9. Overcoming adverse propagation effects: Frequency/baseband/synthesizer hopping. Block and diagonal interleaving. Directional antennas, sectorization. Uplink and downlink power control. Discontinued transmissions. Receive diversity. Equalization. 10. Subscriber environment: Environment. Future planning. 11.
32
The microcellular solution. System Information: BSS Equipment Planning 68P02900W21-G

14th Apr 00
GSM-001-103
Planning tools
Planning tools
Introduction
In order to predict the signal strength in a cell area it would be necessary to make many calculations, at regular intervals, from the BTS. The smaller the interval the more accurate the propagation model. Also the calculations would need to be performed at regular distances along each radial arm from the BTS, to map the signal strength as a function of distance from the BTS. The result, is the necessity to perform hundreds of calculations for each cell. This would be time consuming in practice, but for the intervention of the software planning tool. This can be fed with all the details of the cell, such as: S S S Type of terrain. Environment. Heights of antennas.
It can perform the necessary number of calculations needed to give an accurate picture of the propagation paths of the cell. Several planning tools are available on the market, such as Netplan or planet, and it is up to the users to choose the tool(s) which suit them best. After calculation and implementation of the cell, the figures should then be checked by practical measurements. This is because, with all the variable factors in propagation modelling, an accuracy of 80% would be considered excellent.
14th Apr 00
33
GSM frequency spectrum
GSM-001-103

The GSM900 frequency spectrum
The original GSM frequency spectrum was allocated in 1979. This consisted of two sub-bands 25 MHz wide. The frequency range is: S S Uplink range Downlink range 890 MHz 915 MHz. 935 MHz 960 MHz.
It is usual for the uplink frequencies mobiles transmit to the BTS to be on the lowest frequency band . This is because there is a lower free space path loss for lower frequencies. This is more advantageous to the mobile as it has a reduced transmit output power capability compared to the BTS. The two bands are divided into channels, a channel from each band is then paired with one of the pair allocated for uplink and one for the downlink. Each sub-band is divided into 124 channels, these are then given a number known as the Absolute Radio Frequency Channel Number (ARFCN). So a mobile allocated an ARFCN will have one frequency to transmit on and one to receive on. The frequency spacing between the pair is always 45 MHz for GSM. The spacing between individual channels is 200 kHz and at the beginning of each range is a guard band. It can be calculated that this will leave 124 ARFCNs for allocation to the various network operators. These ARFCNs are numbered 1 to 124 inclusive To provide for future network expansion more frequencies were allocated to GSM as they became available. An extra 10 MHz was added on to the two GSM bands and this became known as Extended GSM (EGSM). The EGSM frequency range is: S S Uplink range Downlink range 880 MHz 915 MHz. 925 MHz 960 MHz.
This allows another 50 ARFCNs to be used bringing the total to 174. These additional ARFCNs are numbered 975 to 1023 inclusive. One thing to note is that original Phase 1 MSs can only work with the original GSM frequency range and it requires a Phase 2 MS to take advantage of the extra ARFCNs. As the operator cannot guarantee that his network will have a significant number of Phase 2 MS, care must be taken when using EGSM frequencies not to make holes in the network for Phase 1 MSs.
34
14th Apr 00
GSM-001-103
The DCS1800 frequency spectrum

As GSM evolved it was decided to apply the technology to the Personal Communications Networks. This required changes to the air interface to modify the frequency range over which it operates. The modified frequency range is: S S Uplink range Downlink range 1710 MHz 1785 MHz. 1805 MHz 1880 MHz.
This provides 374 ARFCNs with a frequency separation of 95 MHz between uplink and downlink frequencies. In the UK these ARFCNs have been shared out between the four network operators, refer to Figure 3-1. Two of these, Orange and One to One operate exclusively in the DCS1800 range while the other two, Vodafone and Cellnet have been allocated DCS1800 channels on top of their GSM900 networks. ARFCNs are numbered from 512 to 885 inclusive The portion at the top of the band is used by Digital enhanced Cordless telephony (DECT). Uplink
1785MHz DECT 1781.5MHz 1876.5MHz 1880MHz DECT
Downlink
Orange
Orange
One 2 One
One 2 One
1721.5MHz
1816.5MHz
Vodafone/Cellnet 1710MHz 1805MHz
Vodafone/Cellnet
Figure 3-1 UK network operators
14th Apr 00
35
GSM-001-103
The PCS1900 frequency spectrum

This is another adaptation of GSM into the 1900 MHz band. It is used in the United States where the Federal Communications Commission has divided the band into 300 ARFCNs and issued licences to various operators to implement GSM networks. The frequency separation is 80 MHz. The frequency range is : S S Uplink range Downlink range 1850 MHz 1910 MHz. 1930 MHz 1990 MHz.
Absolute radio frequency channel capacity

Each RF carrier supports eight time division multiplexed physical channels and each of these is capable of supporting speech or signalling information. The maximum number of RF carriers at any one BTS site is 24 for M-Cell6 and 25 for BTS6. Therefore the maximum number of physical channels available at a BTS site is 24 x 8 = 192, for M-Cell6 and 25 x 8 = 200, for BTS6.
0 1 2 3 4 5 6 7
BTS
Maximum 24 carriers for M-Cell6 Maximum 25 carriers for BTS6
Figure 3-2 Eight TDMA timeslots per RF carrier
36
14th Apr 00
GSM-001-103
Modulation techniques and channel spacing

The modulation technique used in GSM is Gaussian minimum shift keying. This works by shaping the data to be modulated with a Gaussian filter. The filter removes some of the harmonics from the data square wave producing a more rounded shape. When this is applied to a phase modulator the result is a modified envelope shape at the output of the modulator. The bandwidth of this envelope is narrower than that of a comparable one produced from non-filtered data. With each modulating carrier occupying a narrower bandwidth, more efficient use can be made of the overall bandwidth available. The bandwidth allocated to each carrier frequency in GSM is 200 kHz. The actual bandwidth occupied by a transmitted GSM carrier is far greater than 200 kHz, even with Gaussian filtering. The signal therefore overlaps into surrounding frequencies, as illustrated in Figure 3-3. If two carriers from the same or adjacent cells are allocated adjacent frequencies or channel numbers they will interfere with each other because of the described overlapping. This interference is unwanted signal noise. All noise is cumulative, so starting with a large amount by using adjacent channels our wanted signal will soon deteriorate below the required quality standard. For this reason adjacent frequencies should never be allocated to carriers in the same or adjacent cells. Figure 3-3 illustrates the fact that the actual bandwidth of a GMSK modulated signal is considerably wider than the 200 kHz channel spacing specified by GSM. At the channel overlap point the signal strength of the adjacent channel is only 10 dB below that of the wanted signal. While this just falls within the minimum carrier to interference ratio of 9 dB, it is not insignificant and must be planned around so that allocation of adjacent frequencies in adjacent cells never occurs. One other consideration about channel spacing that must be considered is when using combiners. If a cavity combining block is used the frequencies for combining must be separated by at least three ARFCNs otherwise it could cause intermodulation products and spurious frequency generation. These could interfere with other carriers further away in the radio spectrum, possibly in adjacent cells, so they would not necessarily be a problem to the home cell so the source of interference becomes more difficult to locate.
10 dB POINT
CHANNEL 1 dBs
0 10 20 30 40 50 60 70
CHANNEL 2
CHANNEL 3
200 kHz
Figure 3-3 Modulation techniques and channel spacing
14th Apr 00
37
Traffic capacity
GSM-001-103
Traffic capacity
Dimensioning
One of the most important steps in cellular planning is system dimensioning. To dimension a system correctly and hence all the supporting infrastructure, some idea of the projected usage of the system must be obtained (for example; the number of people wishing to simultaneously use the system). This means traffic engineering. Consider a cell with N voice channels, the cell is therefore capable of carrying N individual simultaneous calls. The traffic flow can be defined as the average number of concurrent calls carried in the cell. The unit of traffic intensity is the Erlang, traffic defined in this way can be thought of as a measure of the voice load carried by the cell. The maximum carried traffic in a cell is N Erlangs, which occurs when there is a call on each voice channel all of the time. If during a time period T (seconds), a channel carries traffic is busy for t (seconds), then the average carried traffic, in Erlangs, is t/T. The total traffic carried by the cell is the sum of the traffic carried by each channel. The mean call holding time is the average time a channel is serving a call.
38
14th Apr 00
GSM-001-103
Traffic capacity
Channel blocking
The standard model used to dimension a system is the Erlang B model, which models the number of traffic channels or trunks required or a given grade of service and given offered traffic. There will be times when a call request is made and all channels or trunks are in use, this call is then blocked. The probability of this happening is the grade of service of the cell. If blocking occurs then the carried traffic will be less than the offered traffic. If a call is blocked, the caller may try again within a short interval. Repeated call attempts of this type increase the offered traffic above the level if there had been an absence of blocking. Because of this effect the notion of offered traffic is somewhat confused, however, if the blocking probability is small, it is reasonable to ignore the effect of repeated call attempts and assume that blocked calls are abandoned. The number of calls handled during a 24 hour period varies considerably with time. The figure opposite shows the type of traffic load that might be expected on a typical call. There are usually two peaks during week days, although the pattern can change from day to day. Across the typical day the variation is such that a onehour period shows greater usage than any other. From the hour with the least traffic to the hour with the greatest traffic, the variation can exceed 100:1. To add to these fairly regular variations, there can also be unpredictable peaks caused by a wide variety of events (for example; the weather, natural disasters, conventions, sports events). In addition to this, system growth must also be taken into account. There are a set of common definitions to describe this busy hour traffic loading. Busy Hour: The busy hour is a continuous period during which traffic volume or number of call attempts is the greatest. Peak Busy Hour: The busy hour each day it is not usually the same over a number of days. Time Constant Busy Hour: The onehour period starting at the same time each day for which the average traffic volume or call attempts count is greatest over the days under consideration. Busy Season Busy Hour: The engineering period where the grade of service criteria is applied for the busiest clock hour of the busiest weeks of the year. Average Busy Season Busy Hour: The average busy season busy hour is used for trunk groups and always has a grade of service criteria applied. For example, for the Average Busy Season Busy Hour load, a call requiring a circuit in a trunk group should not encounter All Trunks Busy (ATB) no more than 1% of the time. Peak loads are of more concern than average loads when engineering traffic routes and switching equipment.
14th Apr 00
39
Traffic capacity
GSM-001-103
Traffic flow
If mobile traffic is defined as the aggregate number of MS calls (C) in a cell with regard to the duration of the calls (T) as well as their number, then traffic flow (A) can be defined as: Traffic Flow (A) = C x T Where: C T is: the calling rate per hour. the average holding time per call.
Suppose an average hold time of 1.5 minutes is assumed and the calling rate in the Busy Hour is 120, then the traffic flow would be 120 x 1.5 = 180 call-minutes or 3 call hours. One Erlang of traffic intensity on one traffic channel means a continuous occupancy of that particular traffic channel. Considering a group of traffic channels, the traffic intensity in Erlangs is the number of call-seconds per second or the number of call-hours per hour. As an example; if there were a group of 10 traffic channels which had a call intensity of 5 Erlangs, then half of the circuits would be busy at the time of measurement.
Grade of service
One measure of the quality of service is how many times a subscriber is unsuccessful in setting up a call (blocking). Blocking data states what grade of service is required and is given as a percentage of the time that the subscriber is unable to make a call. Typical blocking for the MSBSC link is 2% with 1% being acceptable on the BSCMSC link. There is a direct relationship between the grade of service required and the number of channels. The customers desired grade of service has a direct affect on the number of channels needed in the network.
310
14th Apr 00
GSM-001-103
Capacity calculations
Introduction
This section provides information on how to determine the number of control channels required at a BTS. This information is required for the sizing of the links to the BSC, and is required when calculating the exact configuration of the BSC required to support a given BSS.
Typical call parameters

The number of control channels and GPROC2s required at a BTS depend on a set of call parameters; typical call parameters for BTS planning are given in Table 3-1. Table 3-1 Typical parameters for BTS call planning Parameter Call duration Ratio of SMSs per call Ratio of location updates to calls: non-border location area Ratio of location updates to calls: border location area Ratio of IMSI detaches to calls Location update factor: non-border location area (see below) Location update factor: border location area (see below) Number of handovers per call Paging Rate in pages per second Time duration for location update Time duration for SMSs Time duration for call set-ups Guard time for SDCCHs Assumed Value T = 120 seconds S = 0.1 l=2 l=7 Id = 0 L=2 L=7 H = 2.5 P=3 TL = 4 seconds TSMS = 6 seconds TC = 5 seconds Tg = 4 seconds
14th Apr 00
311
GSM-001-103
Table 3-1 Typical parameters for BTS call planning Parameter Probability of blocking for TCHs Probability of blocking for SDCCHs Assumed Value PB-TCH < 2% PB-SDCCH < 1%
The location update factor (L) is a function of the ratio of location updates to calls (I), the ratio of IMSI detaches to calls (Id) and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically Id = 0 (that is IMSI detach is disabled) as in the first formula given below. When IMSI detach is enabled, the second or third of the formulas given below should be used. The type of IMSI detach used is a function of the MSC. If IMSI detach is disabled: L=I If IMSI detach type 1 is enabled: L = I + 0.2 * I d If IMSI detach type 2 is enabled: L = I + 0.5 * I d
312
14th Apr 00
GSM-001-103
Control channel calculations

Introduction
There are four types of air interface control channels, they are: S S S S S Broadcast control channel (BCCH). Common control channel (CCCH). Standalone dedicated control channel (SDCCH). Cell broadcast channel (CBCH), which uses one SDCCH.
There are three configurations of control channels, each occupies one radio timeslot: A combined control channel. One BCCH plus three CCCH plus four SDCCH. or S A non-combined control channel. One BCCH plus nine CCCH (no SDCCH). plus S An SDCCH control channel. Eight SDCCH. Each sector/cell requires a BCCH, so one of the configurations is always required. The number of air interface control channels required for a site, is dependent on the: S S S S S Number of pages. Location updates. Short message services. Call loading. Setup time.
Only the number of pages and access grants affects the CCCH. The other information uses the SDCCH.
GPRS control channel RF provisioning

Control channels can be equipped to a GPRS carrier or to a circuit switched GSM carrier to support GPRS traffic channels. If the control channel timeslot(s) are assigned to a GPRS carrier, this reduces the number of available GPRS timeslots from eight to a smaller number in direct proportion to the number used as control channels. Alternatively, by equipping the control channels to the circuit switched GSM carrier, all eight timeslots on the GPRS carrier remain available for use as GPRS timeslots. The network planner needs to combine the GSM circuit switched signalling requirements with the GPRS signalling requirements in order to plan the appropriate level of control channel support. This planning guide provides the planning rules that enable the network
14th Apr 00
313
GSM-001-103
planner to evaluate whether a combined BCCH can be used, or if a non-combined BCCH is required. The decision to use a non-combined BCCH is a function of the combined GPRS and GSM signalling load on the PAGCH ,and on the number of SDCCH channels required to support the GSM circuit switched traffic. The use of a combined BCCH is desirable because it may permit the use of only one timeslot on a carrier that is used for signalling. A combined BCCH can offer 4 more SDCCH blocks for use by the GSM circuit switched signalling traffic. If more than an average of three CCCH blocks, or more than four SDCCH blocks, is required to handle the signalling load, more control channel timeslots are required. The planning approach for GPRS/GSM control channel provisioning is to determine whether a combined BCCH is possible, given the combined GPRS and GSM load on the CCCH control channel. When more than three CCCH blocks and less than nine CCCH blocks are required to handle the combined load, the use of a combined BCCH is not possible. When more than nine CCCH blocks are needed, one or more timeslots are required to handle the CCCH signalling. In this case, it may be advantageous to use a combined BCCH again, depending on the CCCH and SDCCH load. The determination of how many CCCH and SDCCH blocks are required to support the circuit switched GSM traffic is deferred to the network planning that is performed with the aid of the relevant planning information for GSM. The network planning that is performed using the planning information determines how many CCCH and SDCCH blocks are required, and subsequently how many timeslots in total are required, to support the CCCH and SDCCH signalling load. The downlink control channels are: FCCH, SCH, BCCH, PAGCH. The Paging Access Grant CHannel (PAGCH) consists of paging messages and access grant messages. The downlink control channel load is determined by evaluating the combined GSM circuit switched signalling traffic load and the GPRS signalling traffic load on the PAGCH. The uplink control channel is the Random Access CHannel (RACH). It is assumed that by adequate provisioning of the downlink portion of the Common Control CHannel (CCCH), the uplink portion is implicitly provisioned with sufficient capacity. The provisioning of the Paging Access Grant CHannel (PAGCH) is estimated by calculating the combined load from the GPRS pages, GSM pages, GPRS access grant messages, and GSM access grant messages. The calculation is performed by adding the estimated GPRS and GSM paging blocks for the BTS cell to the estimated number of GPRS and GSM access grant blocks for the BTS cell, and dividing that sum by the CCCH utilization factor. Equation 19 should be evaluated to determine whether the number of PAGCHs is greater than three. If the evaluation is greater than three, three CCCH blocks are not sufficient: a non-combined BCCH must be used, independent of the number of SDCCH channels that are calculated as part of the BSS GSM circuit switched planning. If more than nine CCCH blocks are needed, more non-combined timeslots may be required. Example control channel configurations are shown in Table 3-2.
314
14th Apr 00
GSM-001-103
Table 3-2 Control channel configurations Timeslot 0 1 BCCH + 3 CCCH + 4 SDCCH Other timeslots N x 8 SDCCH Comment One combined BCCH. The other timeslot may or may not be required depending on the support of circuit switched traffic, where the value of N can be >=0. Non-combined BCCH. The value of N is >=1. Non-combined BCCH. This is an example of one extra timeslot of CCCHs added in support of GPRS traffic. The value of N is >= 1.
1 BCCH + 9 CCCH 1 BCCH + 9 CCCH
N x 8 SDCCH N x 8 SDCCH, 9 CCCH
The number of GPRS and GSM paging blocks are summed together in Equation 20.
Equation 19
N PAGCH + (NPCH ) NAGCH) UCCCH Each term in the above equation is determined as per Equation 21 and Equation 22. Where: NPAGCH is: The average number of paging / Access Grant blocks rounded up to an integer. The average number of paging blocks required at a cell. The average number of Access Grant blocks required at a cell. This is a utilization factor based on the percentage of the CCCH bandwidth that can be reliably used. A typical value for UCCCH is 30%.
NPCH
NAGCH
UCCCH
The number of GPRS and GSM paging blocks are summed together in Equation 20.
14th Apr 00
315
GSM-001-103
Equation 20
N PCH + NPCH_GPRS ) NPCH_GSM Each term in the above equation is determined as per Equation 21 and Equation 22. Where: NPCH is: The average number of paging blocks in support of GPRS and GSM traffic required at a cell. The average number of paging blocks in support of GPRS traffic. The average number of paging blocks in support of GSM traffic.
NPCH_GPRS
NPCH_GSM
Equation 21
N PCH_GPRS + GPRS_Page_Rate (1.5 * 4.25) Where: NPCH_GPRS is: The average number of paging blocks in support of GPRS traffic required at a cell. The number of GPRS pages transmitted to a BTS cell per second.
GPRS_Page_Rate
Equation 22
N PCH_GSM + GSM_Page_Rate (1.5 * 4.25) Where: NPCH_GSM is: The average number of paging blocks in support of GSM traffic required at a cell. The number of GSM pages transmitted to a BTS cell per second.
GSM_Page_Rate
Where the denominator factor of 1.5 in Equation 21 and Equation 22 reflects that one page can be used for an average of 1.5 mobiles. The factor of 4.25 is the number of paging messages per second supported by one CCCH block. The factors of 1.5 in Equation 21 and in Equation 22 take into account the paging message packing efficiency experienced at the cell. The number of GPRS and GSM access grant channel blocks is summed in Equation 23.
316
14th Apr 00
GSM-001-103
Equation 23
N AGCH + NAGCH_GPRS ) NAGCH_GSM Where: NAGCH is: The average number of access grant blocks required at a cell. The average number of GPRS access grant blocks required at a cell. The average number of GSM access grant blocks required at a cell.
NAGCH_GPRS
NAGCH_GSM
Each term in Equation 23 above is determined by Equation 24 and Equation 25 respectively.
Equation 24
N AGCH_GPRS + Where: (lBURST_GPRS) (4.25) is: The number of GPRS access grant blocks required at a cell. This number includes all downlink bursts per second in support of all uplink and downlink GPRS temporary data flow (TBF) originations. GPRS data traffic includes all SMS traffic carried by the GPRS infrastructure. Additionally, this factor includes routeing area updates and cell updates.
NAGCH_GPRS
lBURST_GPRS
Before the GPRS network is operational, the above values in Equation 24 must be determined by the operator. Once the network is operational, these values can be obtained by inspecting the BSS busy hour statistics.
Equation 25
N AGCH_GSM + lCALL_GSM ) lL_GSM ) lS_GSM 1.5 * 4.25
The factors in the above Equation 25 are defined as follows. Where: NAGCH_GSM CALL_GSM L_GSM S_GSM is: The average number of GSM access grant blocks required at a cell. The call arrival rate per second. The location update rate per second. The number of SMS messages per second.
14th Apr 00
317
GSM-001-103
Number of CCCH per BTS cell

The following factors should be considered when calculating the number of CCCH per BTS cell: S The CCCH channels comprise the paging and access grant channel (PAGCH) in the downlink, and the random access channel (RACH) in the uplink. The PAGCH is subdivided into access grant channel (AGCH) and paging channel (PCH). If the CCCH has a low traffic requirement, the CCCH can share its timeslot with SDCCHs (combined BCCH). If the CCCH carries a high traffic a non-combined BCCH must be used: Combined BCCH (with four SDCCH). Number of CCCH blocks = 3. Number of CCCH blocks reserved for AGCH ag_blks_res is 0 to 2. Number of CCCH blocks available for PCH/AGCH is 3 to 1. Non combined BCCH. Number of CCCH blocks = 9. Number of CCCH blocks reserved for AGCH ag_blks_res is 0 to 7. Number of CCCH blocks available for PCH is 9 to 2. S When a non-combined BCCH is used, it is possible to add additional CCCH control channels (in addition to the mandatory BCCH on timeslot 0). These additional CCCH control channels are added, in order, on timeslots 2, 4, and 6 of the BCCH carrier. Thus creating cells with 18, 27, and 36 CCCH blocks. These configurations would only be required for very high capacity cells or in large location areas with a large number of pages. Each CCCH block can carry one message. The message capacity of each CCCH block is 4.25 messages/second. The AGCH is used to send immediate assignment and immediate assignment reject messages. Each AGCH immediate assignment message can convey channel assignments for up to two MSs. Each AGCH immediate assignment reject message can reject channel requests from up to four MSs. The PCH is used to send paging messages. Each PCH paging message can contain pages for up to four MSs using TMSI or two MSs using IMSI. If no paging messages are to be sent in a particular CCCH block, then an immediate assignment/immediate assignment reject message can be sent instead. The current Motorola BSS implementation applies the following priority (highest to lowest) for downlink CCCH messages: Paging message (if not reserved for AGCH). Immediate assignment message. Immediate assignment reject message.
S S
Thus, for example, if for a particular PAGCH sub-channel there are always paging messages (that is high paging load) waiting to be sent, no immediate assignment or immediate assignment reject messages will be sent on that PAGCH sub-channel. Hence the option to reserve CCCH channels for AGCH.
318
14th Apr 00
GSM-001-103
S S
It can normally be assumed that sufficient capacity exists on the uplink CCCH (RACH) once the downlink CCCH (PAGCH) is correctly dimensioned. A number of other parameters may be used to configure the CCCH channels. Some of these are: Number of paging groups. Each MS is a member of only one paging group and only needs to listen to the PCH sub-channel corresponding to that group. Paging group size is a trade off between MS idle-mode battery life and speed of access (for example, a lot of paging groups, means the MS need only listen very occasionally to the PCH but as a consequence it takes longer to Page that MS resulting in slower call setup as perceived by a PSTN calling party). Number of repetitions for MSs attempting to access the network on the RACH. Time MS must wait between repetitions on the RACH.
Precise determination of the CCCH requirements may be difficult; however, a number of statistics can be collected (for example ACCESS_PER_PCH, ACCESS_PER_AGCH by the BSS and these may be used to determine the CCCH loading and hence perform adjustments.
Calculate the number of CCCHs per BTS cell

The following planning actions are required: S Determine the number of CCCHs per BTS. The average number of blocks required to support AGCH and PCH is given by: N PAGCH = (NAGCH + N PCH) 1 UCCCH
The average number of blocks required to support AGCH only is given by: N AGCH + lAGCH 1 2 < 4.25
The average number of blocks required to support TMSI paging only is given by: N PCH + P 4 < 4.25
The average number of blocks required to support IMSI paging only is given by: N PCH + The access grant rate is given by: l AGCH + lcall ) lL ) lS Where: UCCCH lAGCH P lcall lL lS is: the CCCH utilization. the access grant rate (per second). the paging rate per second. the call arrival rate per second. the location update rate per second. the number of SMSs per second. P 2 < 4.25
14th Apr 00
319
GSM-001-103
Number of SDCCH per BTS cell

Determining the SDCCH requirement is an important part of the planning process. The SDCCH is where a large portion of call setup messaging takes place. As the number of calls taking place in a BTS increases, greater demand is placed on the control channel for call setup. The following factors should be considered when calculating the number of SDCCH per BTS cell: S To determine the required number of SDCCHs for a given number of TCHs per sector, the call, location update, and SMS (point to point) rates must be determined. Refer to the equations below for information on calculating these rates. Once these rates are determined, the required number of SDCCHs for the given number of TCHs can be determined. Refer to the equations below for information on calculating the required number of SDCCHs. S The rates for SMS are for the SMSs taking place over an SDCCH. For MSs involved in a call, the SMS may take place over the TCH, and may not require the use of an SDCCH. Calculating the number of SDCCHs required is necessary for each cell at a BTS site. The equation below for NSDCCH is used to determine the average number of SDCCHs. The number of Erlangs, e, is the number of Erlangs supported by a given sector based on the number of TCHs in that sector. To determine the number Erlangs support by a sector use Erlangs B. Use Erlang B to determine the required number of SDCCHs necessary to support the desired grade of service. The number of location updates will be higher for sites located on the borders of location areas, as compared to inner sites of a location area. See Figure 3-4.
S S
BORDER BTS =
INNER BTS =
LOCATION AREA
Figure 3-4 Location area diagram

320
14th Apr 00
GSM-001-103
Calculate the number of SDCCHs per BTS cell

The following planning actions are required: S Determine the number of SDCCHs per BTS. The average number of SDCCHs is given by: N SDCCH = lcall < T c ) lLU < T L ) T g ) l S < T S ) T g The call rate (calls per hour) is given by: l call = e T The location update rate (LU per hour) is given by: l LU = L < e T The SMS rate (SMS per hour) is given by: lS = S < e T Where: NSDCCH lcall Tc lLU TL Tg lS TS e T L S is: the average number of SDCCHs. the call arrival rate per second. the time duration for call setup. the location update rate. the time duration of location updates. the guard time for SDCCH. the number of SMSs per second. the time duration of SMS (short message service setup). the number of Erlangs per cell. the average call length in seconds. the ratio of location updates to calls. the ratio of SMSs to calls.
14th Apr 00
321
GSM-001-103
Control channel configurations

Table 3-3 and Table 3-4 give typical control channel configurations based on the typical BTS planning parameters given in Table 3-1.
Control channel configurations for non-border location area

Table 3-3 is for the non-border location area cell, where the ratio of location updates to calls is 2. Table 3-3 SDCCH planning for typical parameters (non-border location area) Number of RTFs RTF 1 2 3 4 5 6 7 8 9 10 11 12 NOTE The CBCH reduces the number of SDCCHs by one and may require another channel. Number of TCHs TCH 7 14 22 30 38 45 53 61 69 77 Number of Erlangs El 2.94 8.20 14.9 21.9 29.2 35.6 43.1 50.6 58.2 65.8 Number of SDCCHs SDCCH 4 8 8 12 12 16 16 20 20 20 Timeslot utilization Timeslot 0 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 3 CCCH + 4 SDCCH 8 SDCCH 8 SDCCH 8 SDCCH 8 SDCCH 2 x 8 SDCCH 2 x 8 SDCCH 2 x 8 SDCCH 2 x 8 SDCCH 2 x 8 SDCCH Other timeslots
322
14th Apr 00
GSM-001-103
Control channel configurations for border location area

Table 3-4 is for the border location area cell, where the ratio of location updates to calls is 7. Table 3-4 SDCCH planning for typical parameters (border location area) Number of RTFs 1 2 3 4 5 6 7 8 9 10 Number of TCHs 6 14 21 29 36 44 51 59 66 74 Number of Erlangs 2.28 8.20 14.0 21.0 27.3 34.7 41.2 48.7 55.3 62.8 Number of SDCCHs 8 12 16 20 24 28 36 36 40 44 Timeslot utilization Timeslot 0 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 3 CCCH + 4 SDCCH 1 BCCH + 9 CCCH 1 BCCH + 3 CCCH + 4 SDCCH Other timeslots 8 SDCCH 8 SDCCH 2 x 8 SDCCH 2 x 8 SDCCH 3 x 8 SDCCH 3 x 8 SDCCH 4 x 8 SDCCH 4 x 8 SDCCH 5 x 8 SDCCH 5 x 8 SDCCH
14th Apr 00
323
The GPRS planning process
GSM-001-103
The GPRS planning process

Overview of the GPRS planning process
The GPRS planning process documentation has the following structure: S S S Introduction to the planning process. GPRS network traffic estimation and key concepts. Air interface planning process.
324
14th Apr 00
GSM-001-103
Introduction to the GPRS planning process

Overview the GPRS planning process introduction
The Introduction to the GPRS planning process has the following structure: S S Determination of expected load or overload. Network planning flow.
14th Apr 00
325
GSM-001-103
Determination of expected load

The planning process begins by determining the expected GPRS load (applied load) to the system. The next step is to determine the effective load to the system by weighting the applied load by network operating parameters. These parameters consist of the expected BLock Error Rate (BLER) based on the cell RF plan, the protocol overhead (GPRS protocol stack, that is TCP/IP, LLC, SNDCP, RLC/MAC), the expected advantage from V.42bis compression and TCP/IP header compression, and the multislot operation of the mobiles and infrastructure. The effective load at a cell is used to determine the number of GPRS timeslots required to provision a cell. The provisioning process can be performed for a uniform load distribution across all cells in the network or on an individual cell basis for varying GPRS cell loads. The number of GPRS timeslots is the key piece of information that drives the BSS provisioning process in support of GPRS. The planning process also uses network generated statistics, available after initial deployment, for replanning a network. The statistics fall into two categories: PCU specific statistics, and GSN (SGSN + GGSN) statistics. In a later section of this document, all of the statistics collected from the GPRS infrastructure are listed. The statistics that are expected to be useful for network replanning are identified. In this planning document, the statistics used for planning purposes are grouped into four categories: Stats_A, Stats_B, Stats_C, and Stats_D, as indicated in Figure 3-5.
ENTER USER PROFILE (APPLIED LOAD) BSS/PCU/GSN STATS_A
BSS/PCU/GSN STATS_B
CALCULATE BLER AND PROTOCOL OVERHEAD IMPACT ON APPLIED LOAD
BSS/PCU
CONFIGURE INFRASTRUCTURE
GSN STATS_C
BSS/PCU STATS_D
GSN (SGSN, GGSN, OMC-G)
Figure 3-5 GPRS network planning flowchart

326
14th Apr 00
GSM-001-103
Network planning flow

The remaining chapters of the planning guide are presented in support of the GPRS network planning flowchart (Figure 3-5). The network planning flow is as follows: S GPRS network traffic estimation and key concepts: This text is intended to introduce the key concepts involved in planning a network. Because GPRS introduces the concept of a switchable timeslot that can be shared by both the GSM circuit switched infrastructure and by the GPRS infrastructure, much of the following text is dedicated to the discussion of this topic. Customer inputs to the planning process: This chapter provides a table of inputs that can serve as a guide in the planning process. In subsequent planning sections, references are made to parameters in this table of inputs. A key piece of information that is needed for the planning process is the RF cell plan. This subsection discusses the impact of different cell plans on the GPRS provisioning process, and how to use this information in order to determine the number of GPRS timeslots that are required on a per cell basis. BSS planning: The hardware and communication link provisioning rules are detailed in this section based on the number of timeslots required. The number of timeslots is determined from the applied cell load requirements (cell throughput) that are provided by the network planner. GSN complex planning: The hardware and communication links are determined in this section. GPRS network statistics for network replanning: The statistics collected by the BSS and GSN are listed in tabular form, and the statistics that could be valuable for network replanning are identified. Planning examples: A planning example is provided for both the BSS and GSN portions of the GPRS infrastructure. Recommended planning guidelines: Based on the network planning rules, a few recommended planning guidelines are provided in this section.
S S
S S
14th Apr 00
327
GPRS network traffic estimation and key concepts
GSM-001-103

Overview of the GPRS network traffic estimation and key concepts
The GPRS network traffic estimation and key concepts section has the following structure: S S S S S S Introduction to the GPRS network traffic estimation and key concepts. Dynamic timeslot mode switching. Carrier timeslot allocation examples. BSS timeslot allocation methods. Provisioning the network with switchable timeslots. Recommendation.
328
14th Apr 00
GSM-001-103
Introduction to the GPRS network traffic estimation and key concepts

The GPRS network planning is fundamentally different from the planning of circuit switched networks. One of the fundamental reasons for the difference is that a GPRS network allows the queuing of data traffic instead of blocking a call when a circuit is unavailable. Consequently, the use of Erlang B tables for estimating the number of trunks or timeslots required is not a valid planning approach for the GPRS packet data provisioning process. The GPRS traffic estimation process starts by looking at the per cell GPRS data traffic profile such as fleet management communications, email communications, web browsing, and large file transfers. Once a typical data traffic profile mix is determined, the required network throughput per cell can be calculated as measured in kbits per second. The desired network throughput per cell is used to calculate the number of GPRS timeslots required to support this throughput on a per-cell basis. The estimated GPRS network delay is derived based on computer modeling of the delay between the Um interface and the Gi interface. The results are provided in the planning guide. The network delay can be used to determine the mean or average time it takes to transfer a file of arbitrary length. In order to simulate the delay, the following factors are considered: traffic load per cell, mean packet size, number of available GPRS carrier timeslots, distribution of CS-1 and CS-2 rate utilization, distribution of Mobile Station (MS) multislot operation (1,2,3, or 4), and BLER.
Use of timeslots
The use of timeslots on a GPRS carrier is different from how they are used in the GSM circuit switched case. In circuit switched mode, an MS is either in the idle mode or dedicated mode. In the dedicated mode, a circuit is assigned through the infrastructure whether or not a subscriber is transporting voice or data. In the Idle mode, the network knows where the MS is, but there is no circuit assigned. In the GPRS mode, a subscriber uses the infrastructure timeslots for carrying data only when there is data to be sent. However, the GPRS subscriber can be attached and not sending data and this still presents a load to the GSN portion of the GRPS system, and must be accounted for when provisioning the GPRS infrastructure, that is, in state 2 as explained below. The GPRS mobile states and conditions for transferring between states are provided in Table 3-5 and shown in Figure 3-6 in order to specify when infrastructure resources are being used to transfer data. The comment column specifies what the load on the infrastructure equipment is for that state and only in state 3 does the infrastructure equipment actually carry user data. The infrastructure equipment is planned such that many more MSs can be attached to the GPRS network, that is in state 2, than there is bandwidth available to simultaneously transfer data. One of the more significant input decisions for the network planning process is to determine and specify how many of the attached MSs are actively transmitting data in the Ready state 3. In the Standby state 2, no data is being transferred but the MS is using network resources to notify the network of its location. The infrastructure has equipment limits as to how many MSs can be in state 2. When the MS is in state 1, the only required infrastructure equipment support is the storage of MS records in the HLR. Network provisioning requires planning for traffic channels and for signalling channels also referred to as control channels. The BSS GSR 4.1 release combines the circuit switched and GPRS control channels together as BCCH/CCCH. This planning guide provides a planning procedure in a later section for determining the BCCH/CCCH control channel capacity needed.
14th Apr 00
329
GSM-001-103
Table 3-5 MM State Model of MS Present state # 1 Present state IDLE Next state READY(3) Condition for state transfer GPRS Attach Comments (Present state) Subscriber is not monitored by the infrastructure, that is not attached to GPRS MM, and therefore does not load the system other than the HLR records. Subscriber is attached to GPRS MM and is being actively monitored by the infrastructure, that is MS and SGSN establish MM context for subscriber IMSI, but no data transmission occurs in this state. Data transmission through the infrastructure occurs in the Ready state The ready timer (T3314) default time is 32 seconds. The timer value can be modified during the signalling process by MS request. 2-60 sec. in 2 sec. increments or 61-1800 sec. in 60 sec. increments.
STANDBY
READY(3)
PDU Transmission
READY
IDLE(1)
GPRS Detach
READY
STANDBY(2)
Ready timer expiry or force to Standby (The network or the MS can send a GMM signalling message to invoke force to Standby.)
330
14th Apr 00
GSM-001-103
IDLE
IDLE
GPRS Attach
GPRS Detach
GPRS Attach
GPRS Detach or Cancel Location
STANDBY timer expiry
READY STANDBY timer expiry or Cancel Location PDU transmission READY timer expiry PDU reception or READY timer expiry Force to STANDBY or or Force to STANDBY READY Abnormal RLC condition
STANDBY
STANDBY
MM State Model of MS
MM State Model of SGSN
Figure 3-6 MM state models for MS and SGSN
14th Apr 00
331
GSM-001-103
Dynamic timeslot mode switching

This section proposes a network planning approach when utilizing dynamic timeslot mode switching of timeslots on a GPRS carrier. The radio interface resources can be shared dynamically between the GSM circuit switched services and GPRS data services as a function of service load and operator preference. The timeslots on a GPRS carrier can be reserved for GPRS use, for circuit switched use only, or allocated as switchable. Motorola uses the term switchable to describe a timeslot that can be dynamically allocated for GPRS Data service or for circuit switched service. The timeslot allocation is performed such that the GPRS reserved timeslots are allocated for GPRS use before switchable timeslots. GSM circuit switched timeslots are allocated to the circuit switched calls before switchable timeslots. The switchable timeslots are allocated with priority given to circuit switched calls. Motorola has a BSS feature called Concentration at BTS. This feature enables the terrestrial backhaul resources to be dynamically assigned over the E1 links between the BSC and BTS. The terrestrial backhaul resources are managed and allocated in increments of 16 kbit/s. When the concentration-at-BTS feature is enabled, it is important to have a sufficient level of terrestrial backhaul resources provisioned. This feature has the concept of reserved and switchable BSC-to-BTS resources. This concentration-at-BTS feature allows the network planner to allocate dedicated or reserved backing pools to reserved GPRS timeslots so that there is a guaranteed level of terrestrial backing available to GPRS traffic. It is recommended that the reserved backing pool is made large enough to serve the expected busy hour GPRS traffic demands on a per BTS site basis. It is possible for the circuit switched portion of the network to be assigned all of the switchable terrestrial backing under high-load conditions and, in effect, block GPRS access to the switchable timeslots at the BTS. In addition, the reserved GPRS pool of backing resources can be taken by the circuit switched portion of the network when BSC-to-BTS E1 outages occur, and when emergency pre-emption type of calls occur and cannot be served with the pool of non-reserved resources. The concentration-at-BTS feature does not take the last switchable backhaul timeslot until all of the GPRS traffic has be transmitted, in the case when there are no provisioned reserved GPRS timeslots at the cell site. Provisioning rules for the concentration-at-BTS feature are described in the planning information.
332
14th Apr 00
GSM-001-103
Background and discussion

The initial Motorola BSS GPRS infrastructure product permits up to one carrier per cell to be provisioned as a GPRS carrier. The GPRS carrier can also be the BCCH/CCCH carrier. Alternatively, the GPRS carrier can be specified to use all eight timeslots for GPRS traffic and one of the GSM circuit switched carriers in the cell can be designated as the BCCH/CCCH carrier. The GPRS carrier can be provisioned to carry a mix of circuit switched traffic and GPRS traffic. There are three provisioning choices: S S S Reserved GPRS timeslots allocated only for GPRS use. Switchable timeslots dynamically allocated for either GSM circuit switched traffic or GPRS traffic (designated as switchable timeslots by Motorola). Remaining GPRS carrier timeslots, if any, only for circuit switched use.
The BSS supports a user definable number of GPRS timeslots and reserved GPRS timeslots. The BSS calculates the number of switchable timeslots by taking the number of operator allocated GPRS timeslots minus the number of operator allocated reserved GPRS timeslots. The number of circuit switched timeslots on a non-BCCH GPRS carrier is equal to eight timeslots minus the number of GPRS timeslots, that is GPRS timeslots include reserved plus switchable timeslots. The network planner may have some of the following network planning goals in mind when trying to determine when to use reserved timeslots versus and when to use switchable: S S S Use reserved timeslots to guarantee a minimum GPRS quality of service. Use switchable timeslots to provide low circuit mode blocking and high GPRS throughput when the voice busy hour and the GPRS busy hour do not coincide. Use switchable timeslots to provide higher GPRS throughput without increasing the circuit switched blocking rate. If all the GPRS carrier timeslots are provisioned as switchable, the last available timeslot is not given to a circuit switched call until transmission of all the GPRS traffic on that last timeslot is completed. Therefore, there is a circuit switched blocking on that last timeslot until the timeslot becomes free. S S Use switchable timeslots to provide some GPRS service coverage in low GPRS traffic volume areas. Use switchable timeslots to provide extra circuit switched capacity in spectrum limited areas.
In order to make the decision on how to best allocate reserved and switchable timeslots, the network planner needs to have a good idea of the traffic level for both services. The proposal in this planning guide is to drive the allocation of switchable timeslots and reserved GPRS timeslots from a circuit switched point of view. Start by looking at the circuit switched grade of service objectives and the busy hour traffic level, as measured in Erlangs. Once the circuit switched information is known, the potential impact on switchable timeslots can be analysed. The GPRS quality of service can be planned by counting the number of available reserved GPRS timeslots, and by evaluating the expected utilization of the switchable timeslots by the circuit switched portion of the network during the GPRS busy hour.
14th Apr 00
333
GSM-001-103
Carrier timeslot allocation examples

The following two-carrier configuration examples explore different ways a two-carrier system may provision switchable and reserved GPRS timeslots. All blank timeslots in the following figures are available only for circuit switched traffic use. The BSS starts the reserved GPRS timeslot allocation at the top of the carrier (timeslot 7), and then allocates the switchable timeslots, followed by circuit-switched-use-only timeslots. When GPRS and GSM signalling requirements are added together to be served by a two-carrier cell, it is highly likely that one timeslot will be used for BCCH and another timeslot allocated as an SDCCH timeslot. Therefore, the following examples A to example E assume that there is an extra timeslot allocated as an SDCCH timeslot (SD) for GSM signalling purposes. In Example A, Figure 3-7, only four timeslots are used for GPRS on carrier 1; two are reserved GPRS timeslots (R), and two are switchable timeslots (S). One timeslot is used for BCCH (B) and another timeslot for SDCCH (SD), and two timeslots for circuitswitched-only use (blank). In Example B, Figure 3-8, the GPRS signalling information is carried on the BCCH (B) of carrier 1 and SDCCH GSM signalling on a separate timeslot (SD). A separate carrier (carrier 2) is used to carry the GPRS data traffic. In this example, three timeslots are reserved GPRS timeslots and two are switchable. The remaining three timeslots on the second carrier are for circuit-switched-only use(blank). In Example C, Figure 3-9, all GPRS timeslots are configured as switchable timeslots on the BCCH carrier 1 and no reserved GPRS timeslots are configured. Again, one timeslot is assigned for SDCCH signalling use. In Example D, Figure 3-10, all GPRS timeslots are configured as switchable timeslots on the non-BCCH carrier, carrier 2. In Example E, Figure 3-11, all eight GPRS timeslots are configured as reserved timeslots on the non-BCCH carrier, carrier 2.
334
14th Apr 00
GSM-001-103
Timeslot allocation for examples A and B

B: BCCH/CCCH timeslot for GPRS/GSM signalling SD: SDCCH timeslot for GSM signalling R: Reserved GPRS timeslot S: Switchable timeslot Blank: Circuit-switched-use-only timeslots Figure 3-7 provides a timeslot allocation example A.
CARRIER 1 B SD S S R R
TS0
CARRIER 2 (CIRCUIT SWITCHED ONLY)
Figure 3-7 Example A Figure 3-8 provides a timeslot allocation example B.

CARRIER 1 (CIRCUIT SWITCHED ONLY) B SD
TS0
CARRIER 2 S S R R R
Figure 3-8 Example B
14th Apr 00
335
GSM-001-103
Timeslot allocation for examples C, D, and E

B: BCCH/CCCH for GPRS/GSM signalling SD: SDCCH for GSM signalling R: Reserved PDCH S: Switchable PDCH Blank: Circuit-switched-use-only timeslots Figure 3-9 provides a timeslot allocation example C.
CARRIER 1 B SD S S S S
TS0
CARRIER 2 (CIRCUIT SWITCHED ONLY)
Figure 3-9 Example C Figure 3-10 provides a timeslot allocation example D.

TS0
CARRIER 2 S S S S S
Figure 3-10 Example D Figure 3-11 provides a timeslot allocation example E.

TS0
CARRIER 2 R R R R R R R R
Figure 3-11 Example E

336
14th Apr 00
GSM-001-103
BSS timeslot allocation methods

The BSS algorithm that is used in order to determine allocation of switchable timeslots gives priority to circuit switched calls. Consequently, if a switchable timeslot is being used by a GPRS mobile and a circuit switched call is requested after all other circuit switched timeslots are used, the BSS takes the timeslot away from the GPRS mobile and gives it to the circuit switched mobile. The switchable timeslot can be re-allocated back to the GPRS mobile when the circuit switched call ends. The number of reserved GPRS timeslots can be changed by the operator in order to guarantee a minimum number of dedicated GPRS timeslots at all times. The operator provisions the GPRS carrier by selecting the number of timeslots that are allocated as reserved and switchable, and not by specifically assigning timeslots on the GPRS carrier. Motorola has implemented an idle circuit switched parameter that enables the operator to strongly favour circuit switched calls from a network provisioning perspective. By setting the idle parameter to 0, this capability is essentially turned off. The use of the idle circuit switched parameter is as follows. When a circuit switched call ends on a switchable GPRS timeslot and the number of idle circuit switched timeslots is greater than an operator settable threshold, the BSS re-allocates the borrowed timeslot for GPRS service. When the number of idle timeslots is less than or equal to a programmable threshold, the BSS does not allocate the timeslot back for GPRS service, even if it is the last available timeslot for GPRS traffic. If the BSS needs to use the last switchable timeslot in a cell for a circuit switched call when all of the timeslots are allocated as switchable, re-allocation of the timeslot to circuit switched must wait until there is no GPRS traffic in the cell. There is no GPRS traffic in the cell when all of the GPRS uplink and downlink BSS infrastructure queues are empty. At this point, the BSS can re-allocate the last switchable timeslot back as a circuit switched timeslot. If one or more timeslots in a cell are allocated as reserved, the last switchable timeslot is allocated immediately on demand for a circuit switched call. Multislot mobile operation requires that contiguous timeslots are available. The BSSl takes the lowest numbered switchable timeslot in such a manner as to maintain contiguous GPRS timeslots for multislot GPRS operation. The BSS attempts to allocate as many timeslots as requested in multislot mode, and then backoff from that number as timeslots are not available. For example, suppose that timeslots 3 and 4 are switchable, and timeslots 5,6, and 7 are GPRS reserved (see Figure 3-12). When the BSS needs to re-allocate a switchable timeslot from GPRS mode to circuit switched mode, the BSS assigns timeslot 3 before it assigns timeslot 4 for circuit switched mode.
14th Apr 00
337
GSM-001-103
Timeslot allocation for Figure 3-12

B: BCCH/CCCH for GPRS/GSM signalling SD: SDCCH for GSM signalling R: Reserved PDCH S: Switchable PDCH Blank: Circuit-switched-use-only timeslots Figure 3-12 provides a timeslot allocation with reserved and switchable timeslots.
TS0
TS7
Figure 3-12 GPRS carrier with reserved and switchable timeslots If the Emergency Call Pre-emption feature is enabled, the BSS selects the air timeslot that carries the emergency call from the following list: (most preferable listed first) 1. 2. 3. 4. Idle circuit switched. Idle or in-service switchable GPRS timeslot (from lowest to highest). In-service circuit switched. Idle or in-service reserved GPRS timeslot (from lowest to highest).
338
14th Apr 00
GSM-001-103
Provisioning the network with switchable timeslots

Provisioning the network with switchable timeslots can offer flexibility in the provisioning process for combining circuit switched and GPRS service. This flexibility is in the form of additional available network capacity to both the circuit switched and GPRS subscribers, but not simultaneously. Because the BSS favours circuit switched use of the switchable timeslots, the network planner should examine the demand for switchable timeslots during the circuit switched busy hour and during the GPRS busy hour. Normally the operator provisions the circuit switched radio resource for a particular Grade Of Service (GOS) such as 2%. This means that 2 out of 100 circuit switched calls are blocked during the busy hour. If the operator chooses to use the new switchable timeslot capability, it is now possible to share some GPRS carrier timeslots between the circuit switched calls and the GPRS calls. During the circuit switched busy hour, the circuit switched use of these switchable timeslots may dominate their use. The circuit switched side of the network has priority use of the switchable timeslots, and attempts to provide a better grade of service as a result of the switchable timeslots being available. The example in Table 3-6 assumes that the planning is being performed for a cell that has two carriers. The first carrier is for circuit-switched-only use as shown in Table 3-6. The second carrier is a GPRS carrier; all eight timeslots are configured as switchable as shown in Figure 3-13. The table was created using the Erlang B formula in order to determine how many circuit switched timeslots are required for a given grade of service. The table covers the range of 2 Erlangs to 9 Erlangs of circuit switched traffic in order to show the full utilization of two carriers for circuit switched calls. The purpose of the table is to show how the circuit switched side of the network allocates switchable timeslots during the circuit switched busy hour in an attempt to provide the best possible GOS, assumed to be 0.1% for the purposes of this example. The comments column in the table is used to discuss what is happening to the availability of switchable timeslots for GPRS data use as the circuit switched traffic increases, as measured in Erlangs. This example does show some Erlang traffic levels that cannot be adequately served by two carriers at the stated grade of service listed in the tables. This occurs at the 7 and 8 Erlang levels for 0.1% GOS. In these cases, all of the switchable timeslots are used up on the second carrier in an attempt to reach a 0.1% GOS. For the 9 Erlang traffic level, 2 carriers is not enough to serve the circuit switched traffic at a 2% GOS. This would indicate a need for a second circuit switched carrier, in addition to the first circuit switched carrier and the GPRS carrier.
14th Apr 00
339
GSM-001-103
Timeslot allocation for

B: BCCH/CCCH for GPRS/GSM signalling SD: SDCCH for GSM signalling R: Reserved PDCH S: Switchable TCH Blank: Circuit-switched-use-only timeslots Assumptions: 2 Carrier site. Figure 3-13 shows one circuit switched carrier with one BCCH/CCCH timeslot, one SDCCH timeslot, and six TCH timeslots.
SD
TS0
TS7
Figure 3-13 1 circuit switched carrier with 1 BCCH/CCCH timeslot, 1 SDCCH timeslot and 6 TCH timeslots Figure 3-14 shows one GPRS carrier with all timeslots (eight TCHs) designated as switchable.
TS0
TS7
Figure 3-14 One GPRS carrier with all timeslots (eight TCHs) designated as switchable Table 3-6 shows part of the switchable timeslot utilization.
340
14th Apr 00
GSM-001-103
Table 3-6 Switchable timeslot utilization (part A) GOS Planned circuit switched Erlangs/cell Total number of circuit switched timeslots required including switchable 6 Number of switchable timeslots necessary to provide GOS Comments
2%
During off busy hour time periods, the GPRS carrier most likely carries only GPRS traffic. Therefore, GPRS network planning should be performed assuming there are 8 timeslots available for GPRS traffic. During circuit switched busy hour at least 2 of the switchable timeslots are occasionally used by the circuit switch side of the network in an attempt to provide the best possible GOS - assumed to be on the order of 0.1%. During the circuit switched busy hour, 2 of the switchable timeslots are occasionally used by the circuit switch side of the network in an attempt to provide the 2% GOS. During the circuit switched busy hour, 4 of the switchable timeslots are occasionally used by the circuit switch side of the network in an attempt to provide the best possible GOS - assumed to be on the order of 0.1%.
0.1%
2%
0.1%
10
2% 0.1% 2% 0.1%
4 4 5 5
9 12 10 14
3 6 4 8 All of the switchable timeslots are occasionally used to satisfy the 0.1% GOS.
Table 3-7 shows more switchable timeslot utilization.
14th Apr 00
341
GSM-001-103
Table 3-7 Switchable timeslot utilization (part B) GOS Planned circuit switched Erlangs/cell Total number of circuit switched timeslots required including switchable 12 15 Number of switchable timeslots necessary to provide GOS Comments
2% 0.1%
6 6
6 9 There are not enough switchable timeslots to reach 0.1% GOS.
2% 0.1%
7 7
13 17
7 11 There are not enough switchable timeslots to reach 0.1% GOS. All of the switchable timeslots are occasionally used to satisfy the 2% GOS. There are not enough switchable timeslots to reach 0.1% GOS. There are not enough switchable timeslots to reach 2% GOS There are not enough switchable timeslots to reach 0.1% GOS.
2%
14
0.1%
18
12
2%
15
0.1%
20
14
342
14th Apr 00
GSM-001-103
Recommendation
The following recommendation is offered when using switchable timeslots. It is important to determine the GOS objectives for circuit switched traffic and QoS objectives for GPRS traffic prior to selecting the number of switchable timeslots to deploy. During the circuit-switched-busy-hour, potentially all switchable timeslots are occasionally used by the circuit switched calls. The circuit switched timeslot allocation mechanism continues to assign switchable timeslots as circuit switched timeslots as the circuit switched traffic continues to increase. Therefore, if there is a minimum capacity requirement for GPRS services, the network planner should plan the GPRS carrier with enough reserved timeslots in order to handle the expected GPRS data traffic. This ensures that there is a minimum guaranteed network capacity for the GPRS data traffic during the circuit switched busy hour. During the circuit-switched-off-busy-hours, the switchable timeslots could be considered as available for use by the GPRS network. Therefore, in the circuit switched off busy hours potentially all switchable timeslots could be available for the GPRS network traffic. The BSS call statistics should be inspected to determine the actual use of the switchable timeslots by the circuit switched services. The circuit-switched-busy-hour and the GPRS-busy-hour should be monitored to see if they overlap when switchable timeslots are in use. If the busy hours overlap, an adjustment may be needed to the number of reserved timeslots allocated to the GPRS portion of the network in order to guarantee a minimum GPRS quality of service as measured by GPRS throughput and delay. Furthermore, one or more circuit switched carriers may need to be added to the cell being planned or replanned so that the switchable timeslots are not required in order to offer the desired circuit switched grade of service. In conclusion, assume switchable timeslots are occasionally unavailable for GPRS traffic during the circuit switched portion of the network busy hour. Provision enough reserved timeslots for GPRS traffic during the circuit switched busy hour to meet the desired minimum GPRS quality of service objectives, as measured by GPRS data throughput. The following step-wise process is proposed when determining how best to allocate GPRS carrier timeslots.
Assumptions
The process assumptions are: S S S S A GPRS carrier can be added to a cell in addition to circuit switched carriers. A circuit switched carrier can be used to provide the control channels (BCCH/CCCH/SDCCH) on one or more timeslots as needed. The number of circuit switched timeslots are determined as part of the BSS planning effort prior to the GPRS planning effort. When the concentration-at-BTS feature is enabled, a sufficient pool of reserved backing resources is provisioned in support of the number of reserved GPRS timeslots in order to meet the GPRS QoS objectives.
Step 1
Determine how many reserved GPRS timeslots are needed on a per-cell basis in order to satisfy a GPRS throughput QoS. The GPRS reserved timeslots should equal the sum of the active and standby timeslots that are allocated to a carrier.
Step 2
If there are any timeslots left on the GPRS carrier after step 1, consider using them as switchable timeslots. The use of switchable timeslots can potentially offer increased capacity to both the GPRS and circuit switched traffic if the traffic is staggered in time.
14th Apr 00
343
GSM-001-103
Step 3
If there is a need to use some timeslots on the GPRS carrier to satisfy the circuit switched GOS objectives and the timeslot requirement overlaps with the number of reserved GPRS timeslots, consider adding another circuit switched carrier to the cell.
Step 4
After deploying the GPRS carrier, review the network statistics listed in the Network statistics section on a continuous basis in order to determine whether the reserved GPRS timeslots, switchable GPRS timeslots, and circuit switched timeslots are truly serving the GOS and QoS objectives. As previously discussed, the use of switchable timeslots can offer network capacity advantages to both circuit switched traffic and GPRS traffic as long as the demand for these timeslots is staggered in time.
344
14th Apr 00
GSM-001-103
GPRS Air interface planning process

Overview of the GPRS air interface planning process structure
The air interface planning process is documented as follows: S S S S S S Introduction to the air interface planning process. Air interface interface throughput. Throughput estimation process: step 1. Throughput estimation process: step 2. Throughput estimation process: step 3. Throughput estimation process: step 4.
14th Apr 00
345
GSM-001-103
Introduction to the GPRS air interface planning process

The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13. If network values are not available at the time a network is planned, typical or recommended values are provided where appropriate. The minimum values are given for the maximum capacity of a minimum system, and the typical values are used as standard model parameters. Table 3-8 Air interface planning inputs (part A) Variable CS rate ratio, CS-1/CS-2 Minimum value Approx. 0 % Typical value 10% Maximum value 100 % Assumptions/ variable use CS rate ratio is determined by the Cell plan, mean TBF size and use of Acknowledge mode. Refer to cell plan tables: Table 3-14, Table 3-15 and Table 3-16. A ratio of 1 means there is no compression and a ratio of 4 is the theoretical maximum, which is most likely never realized. Most users see a compression advantage in the range of 2-to-3 over the air interface between the MS and the SGSN. The compression ratio is used in Equation 3.
V.42 bis compression ratio
2.5
The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13.
346
14th Apr 00
GSM-001-103
Table 3-9 Air interface planning inputs (part B) Variable BLER 0 Minimum value Typical value 10% Maximum value 100% Assumptions/ variable use The BLock Error Rate (BLER) is largely determined by the cell RF plan. The typical value is an average rate. There are separate BLERs for CS-1 and CS-2 rates that are RF plan specific. This is the File Transit Delay (FTD) objective measured in seconds from the Um interface to the Gi interface. The minimum delay is the approximate delay for a RLC block of 23 bytes or less, which is the minimum system limit with only one user on the system. The FTD value is determined by Equation 4. This number can represent reserved and/or switchable timeslots as explained from Figure 3-7 to Figure 3-14. This is the number of timeslots simultaneously in use with N+1 redundancy. This number is used to calculate the number of PRP and PICP boards to equip at the PCU using the PCU planning rules tabled in Chapter 5.
FTD
0.7 second
3 seconds for a 3 kbyte file, subject to network load and multislot operation.
File size dependent
The number of GPRS timeslots per cell
Network dependent
Number of active 30 GPRS timeslots per PCU with redundancy
Network dependent
240
14th Apr 00
347
GSM-001-103
Table 3-10 Air interface planning inputs (part C) Variable Number of GPRS users monitored at the PCU with redundancy Minimum value 90 Typical value Network dependent Maximum value 720 Assumptions/ variable use This is the number of mobiles that can be monitored in addition to the mobiles actually using timeslots. This value reflects N+1 redundancy. This number reflects the coverage capability of the PCU. This is the number of timeslots simultaneously in use without N+1 redundancy. This number is used to calculate the number of PRP and PICP boards to equip at the PCU using the PCU planning rules tabled in Chapter 5. This is the number of mobiles that can be monitored in addition to the mobiles actually using timeslots without N+1 redundancy. This number reflects the coverage capability of the PCU.
Number of active 30 GPRS timeslots per PCU without redundancy
Network dependent
270
Number of GPRS users monitored at the PCU without redundancy
90
Network dependent
810
348
14th Apr 00
GSM-001-103
Table 3-11 Air interface planning inputs (part D) Variable Mean LLC PDU packet size (bytes) Minimum value 20 Typical value 435 Maximum value 1,580 Assumptions/ variable use This parameter is used in determining the cell and subscriber throughput capacities. This parameter is the expected GPRS load of a subscriber. This figure should include the SMS traffic carried as GPRS data.
Data traffic /subscriber (peak)
98 kbytes/hour
No maximum limit other than what the network is provisioned to support.
14th Apr 00
349
GSM-001-103
The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13. Table 3-12 Air interface planning inputs (part E) Variable Total number of 0 GPRS pages per attached subscriber Minimum value 0.6 Typical value Maximum value No maximum limit other than what the network is provisioned to support. Assumptions/ variable use This effects the signalling traffic load over the SGSN-to-PCU (Gb) interface, the PCU-to-BSC interface(GSL), and the BSC-to-BTS interface(RSL). The GPRS paging traffic must be added to the circuit switched signalling traffic at the BSC in order to determine the total signalling traffic between the BSC and reporting BTSs. This parameter is also used to determine the GPRS load on the CCCH. This number is used to determine the provisioning of the control channels (CCCH provisioning). This establishes how many PCUs are required per OMC-R serving area. The size of the PCU is determined from the GPRS subscriber profile. (Provision 1 PCU per BSC.)
Number of data transfers per hour per subscriber
No maximum limit other than what the network is provisioned to support Network dependent 64
Number of BSCs 1 supporting GPRS per OMC-R serving area
350
14th Apr 00
GSM-001-103
Table 3-13 Air interface planning inputs (part F) Variable Equipment redundancy (BSS PCU & GSN) E1 redundancy Minimum value No Typical value Maximum value Yes Assumptions/ variable use More equipment can be deployed when redundancy is desired. Extra E1 lines are deployed for GSL, GDS, GBL, and Gi links when redundancy is desired. The extra E1 lines provide logical redundancy because the traffic is load shared over the redundant links.
No
Yes
Air interface throughput

The GPRS data throughput estimation process given in this planning guide is based upon the Poisson process for determining the GPRS mobile packet transfer arrivals to the network and for determining the size of GPRS data packets generated or received by the GPRS mobiles. A number of wired LAN/WAN traffic studies have shown that packet interarrival rates are not exponentially distributed. Recent work argues that LAN traffic is much better modelled using statistically self-similar processes instead of Poisson or Markovian processes. Self-similar traffic pattern means the interarrival rates appear the same regardless of the timescale at which it is viewed (in contrast to Poisson process, which tends to be smoothed around the mean in a larger time scale). The exact nature of wireless GPRS traffic pattern is not known due to lack of field data. In order to minimize the negative impact of underestimating the nature of the GPRS traffic, it is proposed in this planning guide to limit the mean GPRS cell loading value to 50% of the system capacity. Using this cell loading factor has the following advantages: S S Cell overloading due to the bursty nature of GPRS traffic is minimized. The variance in file transit delay over the Um-to-Gi interface is minimized such that the delay can be considered a constant value for the purposes of calculating the time to transfer a file of arbitrary size.
LAN/WAN wireline studies have also shown that even when statistically valid studies are performed, the results come out very different in follow-up studies. It turns out that web traffic patterns are very difficult to predict accurately and, therefore, it is highly recommended that the network planner makes routine use of the GPRS network statistics.
About the steps

The following steps 1 and 2 are used for dimensioning the system. Step 1 needs to be performed prior to step 2 in order to calculate the number of GPRS timeslots that should be provisioned on a per cell basis. Steps 3 and 4 are optional. These steps are included in this section so that an over-the-air file transfer time can be calculated for any size file. The results from steps 3 and 4 are dependent upon the choices made in steps 1 and 2.
14th Apr 00
351
GSM-001-103
Step 1: throughput estimation process

Choose a cell plan in order to determine the expected BLER and percentage of time data is transferred at the CS-1 rate and at the CS-2 rate. The cell plan that is chosen for GPRS may be determined by the plan currently in use for the GSM circuit switched portion of the network. However, it may be necessary to change an existing cell plan used for GSM circuit switched in order to get better BLER performance for the GPRS portion of the network. After the cell plan is chosen, the network planner can move on to step 2. The PCU dynamically selects the best CS-1 or CS-2 rate in order to maximize the GPRS data throughput on a per mobile basis. The CS-1 and CS-2 rate selection is performed periodically during the TBF. Simulations were performed (see Impact of the Radio Interface on GPRS System Dimensioning a Simulation Study, Draft 0.1 of June 1999) for two typical frequency hopping cell configurations; results for a 1x3 cell reuse pattern with 2/6 hopping are shown in Table 3-14 (which is hopping on 2 carriers over 6 frequencies) and results for a 1x1 cell reuse pattern with 2/18 hopping are shown in Table 3-15 (which is hopping on 2 carriers over 18 frequencies). Results for a non-hopping cell configuration with a TU-3 model is shown in Table 3-17 provide a chart of the cell coverage area and cell C/I performance for the non-hopping case. The following tables were created, based on the simulations, in order to indicate the percentage of the time the CS-2 rate would be chosen over the CS-1 rate and at what mean BLER. The simulation results indicate that the higher data rate of the CS-2 more than offsets its higher BLER rate in the majority of the cell coverage area, resulting in the CS-2 rate being chosen most of the time. Reviewing the following tables it can be seen that under good cell C/I conditions, better throughput may be obtained by provisioning the GPRS timeslots on the BCCH carrier as indicated by Table 3-16. Table 3-14 1 x 3 2/6 hopping Parameter % Rate chosen % Mean BLER 10 50 Table 3-15 1 x 1 2/18 hopping Parameter % Rate chosen % Mean BLER 10 56 CS-1 rate 90 14 CS-2 rate CS-1 rate 90 20 CS-2 rate
Table 3-16 Nonhopping TU-3 model Parameter % Rate chosen % Mean BLER 0 10 CS-1 rate 100 3 CS-2 rate
Table 3-17 provides the cell C/I performance, as measured in dBs, as a function of cell area coverage for the TU-3 model.
352
14th Apr 00
GSM-001-103
Table 3-17 Cell coverage versus carrier-to-interface (C/I) % cell coverage C/I 90 12 80 16 70 18 60 20 50 22 40 24
The cell plans assume a regular cell reuse pattern for the geographic layout and for the allocation of frequencies. The computer simulation generated the above cell plan using a typical urban 3 kph model, a propagation law with a Radius (R) exponent of -3.7 and a shadowing function standard deviation of 5 db. If non-regular patterns are used, a specific simulation study may be required to match the particular cell characteristics. The simulation process is outside the scope of this planning guide and the network planner should contact Motorola for additional simulation results.
Step 2: throughput estimation process

Step 2 determines the number of GPRS timeslots that need to be provisioned on a per cell basis. Timeslot provisioning is based on the expected per-cell mean GPRS traffic load, as measured in kbit/s. The GPRS traffic load includes all SMS traffic routed through the GSN. The SMS traffic is handled by the GPRS infrastructure in the same manner as all other GPRS traffic originating from the PDN. The cell BLER and CS rate characteristics chosen in step 1 provide the needed information for evaluating the following Equation 1.
Equation 1
No_PDCH_TS + Roundup Mean_trf_ld (Denom_1) * TBF_SETUP_REL_FACTOR
NOTE Equation 1 is based on the DL traffic load and it is assumed that the DL provisioning would be sufficient to handle UL traffic, without additional provisioning.
14th Apr 00
353
GSM-001-103
Equation 2
Denom_1 + %CS1 3 * (1 * CS1BLER) * 9.05 * 1 * 100 23 ) %CS2 3 * (1 * CS2BLER) * 13.4 * 1 * 100 33 * Mean_ld_f 100
Where: Mean_trf_ld
is: The mean traffic load, as measured in kbit/s, is defined at the LLC layer therefore all the higher layer protocol overheads (for example, TCP, UDP, IP, SNDCP, LLC) are encapsulated in this load figure. Denominator 1 is used in Equation 1. The number of timeslots per cell, maximum 8. The percent of time data transmission occurs using the CS-1 coding scheme. The mean BLER rate for CS-1. The percent of time data transmission occurs using the CS-2 coding scheme. The mean BLER rate for CS-2. The CS-1 RLC/MAC overhead percentage, that is 20 bytes payload. The CS-2 RLC/MAC overhead percentage, that is 30 bytes payload.
Denom_1 PDCH %CS1 CS1BLER %C2S CS2BLER 3/23 3/33
354
14th Apr 00
GSM-001-103
Mean_ld_f
The mean load factor for the number of active timeslots to provision at a cell. The recommended value is 50% of the number GPRS timeslots provisioned at a cell. TBF SETUP and Release Factor. The recommended value 0.45. This factor is an interim solution whilst the Overlapping TPF feature is being completed.
TBF SETUP REL factor
The number of PDCH timeslots calculated in Equation 1 includes the number of active timeslots and the number of standby timeslots. The Mean_load_factor of 50% determines the ratio of active timeslots to standby timeslots. For example, if Equation 1 evaluated to 8 timeslots, 4 timeslots would be counted as active timeslots and 4 timeslots as standby timeslots. It is important to differentiate between the required number of active timeslots and the required number of standby timeslots because it directly effects the provisioning of the communication links and the PCU hardware. The active timeslots are timeslots that are simultaneously carrying data. The standby timeslots are timeslots that are being monitored by the PCU for an uplink or downlink timeslot request. A request on a standby timeslot for an active timeslot is granted for an active timeslot as soon as one becomes available at the PCU. For example, when the PCU is provisioned to handle 30 active timeslots and all of them are in use, at least one of these 30 active timeslots must become available in order to move a standby timeslot to active state. The use of active timeslots and standby timeslots enables several cells to share the PCU resource. While one cell is experiencing a high load condition, using all eight GPRS timeslots for instance, another cell operating below its mean load averages out the GPRS traffic load at the PCU. The E1s between the BTS and BSC must be provisioned to handle the number of timeslots calculated in Equation 1 because all of the timeslots can become active under high load conditions.
14th Apr 00
355
GSM-001-103
Throughput estimation process: step 3 (optional)

Step 3 is optional, and the results can be used in optional step 4. Step 3 is intended to be used as an aid in determining the size of a file that is to be transferred as an LLC PDU from the mobile to the SGSN, by using Equation 3. The file size consists of the application file to be transferred, which includes any application-related overhead. In addition to the application file, there is transport and network layer protocol overhead, TCP and IP. Finally, there is GPRS Link Layer Control (LLC) and SubNetwork Convergence (SNDCP) protocol overhead. The application file plus all of the protocol overhead summed together makes up the one or more LLC_PDU frames that constitute the file to be transferred. The percentage of protocol overhead depends on the transport layer used, such as TCP or UDP. For example, the TCP/IP protocol overhead is 40 bytes when TCP/IP header compression is not used. When TCP/IP header compression is used, the TCP/IP header can be reduced to 5 bytes from 40 bytes after the first LLC frame is transferred. The use of header compression continues for as long as the IP address remains the same. Figure 3-15 illustrates the typical LLC_PDU frame with the user application payload and all of the protocol overhead combined for the case of no TCP/IP header compression.
7 LLC
2 SNDCP
20 IP
20 TCP APPLICATION
4 CRC
64 BYTES<L<1580 BYTES
Figure 3-15 LLC PDU layout If V.42bis application data compression is used, the effective file size for transmission is reduced by the data compression factor which can range from 1 to 4. Typically, V.42bis yields a 2.5 compression advantage on a text file, and close to no compression advantage (factor=1) on image files and very short files.
356
14th Apr 00
GSM-001-103
Equation 3
File_size_LLC + Appln Appln ) roundup * protocol_overhead V.42bis_factor V.42bis_factor * LLC_payload
Where:
File_size_LLC
is:
The files size in bytes to be transferred measured at the LLC layer. The user application data file size measured in bytes. The maximum LLC PDU payload of 1527 bytes. The protocol overhead for TCP/IP/SNDCP/LLC/CRC is 53 bytes without header compression and 18 bytes with header compression. Application data compression is over the range of 1 to 4, a typical value is equal to 2.5.
Appln LLC_payload protocol_overhead
V.42bis_factor
Example
A 3 kbytes application file transfer requires the following number of bytes to be transferred at the LLC_PDU layer: Application= 3 kbytes Assume V.42bis_factor = 1, that is no application data compression No header compression: File_size_LLC = 3000 + roundup (3000/1527) x 53 = 3106 bytes With header compression: The first LLC_PDU the header is not compressed, and all subsequent LLC_PDUs are compressed. For this size file of 3000 bytes, only 2 LLC_PDU transmissions are required so the File_size_LLC is: File_size_LLC = 3000 + 53+18 = 3071 bytes
Throughput estimation process: step 4 (optional)

The network planner can use step 4 to determine how long it takes to transfer a file of an arbitrary size over the Um-to-Gi interface. The application file is segmented into LLC PDU frames as illustrated previously. The File Transit Delay (FTD) is calculated in Equation 4 by using the following information: total number of RLC blocks of the file, BLER, number of timeslots used during the transfer, and mean RLC Transit Delay (RTD) value. Equation 4 does not include the effects of acknowledgement messages. The reason is that the largest effect is in the uplink direction, and it is expected that the downlink direction will dominate the cell traffic. The DL sends an acknowledgement message on an as-needed basis, whereas the uplink generates an acknowledgement message every 2 out of 12 RLC_Blocks. It is expected that the downlink acknowledgement messages will not significantly effect the file transit delay in the downlink direction.
14th Apr 00
357
GSM-001-103
Equation 4
FTD + RTD ) RLC_Blocks * 0.02 * (1 ) CSBLER) mslot
Where:
FTD RTD
is:
The file transit delay measured in seconds. This is the transit delay time from the Um interface to the Gi interface for a file size of only 1 RLC/MAC block of data. RTD is estimated to be 0.9 seconds when system running at 50% capacity. This parameter will be updated when field test data is available. This is the total number of RLC blocks of the file. This can be calculated by dividing file_size_LLC by the corresponding RLC data size of 20 bytes for CS-1 and 30 bytes for CS-2. This is the mobile multislot operating mode; the value can be from 1 to 4. This is the BLER for the specific CS rate. The value is specified in decimal form. Typical values range form 0.1 to 0.2.
RLC_Blocks
mslot CSBLER
The RTD parameter is directly correlated to the system utilization and the mean packet size. When the cell approaches its throughput capacity limit, the RTD value increases dramatically, and the infrastructure starts to drop packets. Simulation data indicates that when traffic load is minimal, the RTD value is at a minimum limit of 0.7 seconds. At a cell throughput capacity of 50%, the RTD increases to 0.9 seconds. It is recommended that cell throughput provisioning be performed at the mean cell capacity level of 50%. Provisioning for a mean cell throughput greater than 50% greatly increases the likelihood of dropped packets, and RTD values of over 2.6 seconds can occur. The assumptions used in the simulation to determine the RTD value at a mean cell throughput level of 50% are: 25% of the cell traffic at the CS-1 rate and 75% of the cell traffic at the CS-2 rate, BLER 10%, mobiles multislot distribution 1:2:3:4 = 20:50:20:10, 8 PDCH, DL, mean LLC_PDU packet size of 435 bytes. For example, a 3 kbyte application file transit time at the CS-2 rate, using one timeslot, BLER = 10%, and no header or V.42 bis compression is: 3 Kbyte file transit time over Um-to-Gi interface = 0.9 + Roundup (3106/30) x 0.02 x 1.1 / 1 = 3.2 seconds Where: File_size_LLC is: = 3106 bytes (as calculated in the previous example) = 30 bytes = 0.02 seconds = 1.1 =1
14th Apr 00
CS-2 payload Air time for one RLC/MAC block (1+CSBLER) Multislot operation
358
GSM-001-103
Propagation effects on GSM frequencies

Propagation production
Most of the methods used to predict propagation over irregular terrain are actually terrain based, since they are designed to compute the diffraction loss and free space loss based upon the path profile between the transmitter and the receiver. A widely used technique in the United Kingdom is the prediction method used by the Joint Radio Committee of the Nationalized Power Industries (JRC). This method utilizes a computerized topographical map in a data base, providing some 800,000 height reference points at 0.5 km intervals covering the whole of the UK. The computer predicts the received signal level by constructing the ground path profile between the transmitter and receiver using the data base. The computer then tests the path profile for a line of sight path and whether Fresnel-zone clearance is obtained over the path. The free space and plane earth propagation losses are calculated and the higher value is chosen. If the line of sight and Fresnel-zone clearance test fails, then the programme evaluates the loss caused by any obstructions and grades them into single or multiple diffraction edges. However, this method fails to take any buildings into account when performing its calculation, the calculations are totally based upon the terrain features. Although the use of topographical based calculations are useful when designing mobile communication systems, most mobile systems are centred around urban environments. In these urban environments, the path between transmitter and the receiver maybe blocked by a number of obstacles (for example; buildings), so it is necessary to resort to approximate methods of calculating diffraction losses since exact calculations for each obstacle then become extremely difficult.
14th Apr 00
359
GSM-001-103
Introduction to decibels
Decibels are used to express power output levels, receiver input levels and path losses. The reason they are used is to simplify the calculations used when planning radio systems. Any number maybe expressed as a decibel (dB). The only requirement is that the original description and scale of unity is appended to the dB, so indicating a value which can be used when adding , subtracting, or converting dBs. For example for a given power of 1 mW it may be expressed as 0 dBmW, the mW refers to the fact that the original scale of measurement was in thousandths of a watt. For a power of 1 W the equivalent in dBs is 0 dBW. The decibel scale is logarithmic and this allows very large or very small numbers to be more easily expressed and calculated. For example take a power of 20 watts transmitted from a BTS which was .000000001 W at the receiver. It is very difficult to accurately express the total power loss in a simple way. By converting both figures to decibels referenced to 1 mW, 20 W becomes 32 dBmW and .000000001 W is 60 dBmW. The path loss can now be expressed as 92 dBmW. Multiplication and division also become easier when using dBs. For figures expressed as dBs to multiply them together simply add the db figures together. This is the equivalent in decimal of multiplying. For division simply take one dB figure from the other. Another example is for every doubling of power figures the increase in dBs is 3 dB and for every halving of power the decrease is 3 dB. Table 3-18 gives examples of dB conversions. Table 3-18 dBmW and dBW to Power conversion dBmW + 59 + 56 + 53 + 50 + 49 + 46 + 43 + 40 + 39 + 36 + 33 + 30 + 27 + 24 + 21 + 20 + 17 + 14 + 11 + 10 dBW 29 26 23 20 19 16 13 10 9 6 3 0 3 6 9 10 13 16 19 20 Power 800 W 400 W 200 W 100 W 80 W 40 W 20 W 10 W 8W 4W 2W 1W 500 mW 250 mW 125 mW 100 mW 50 mW 25 mW 12.5 mW 10 mW
14th Apr 00
dBmW +7 +4 +1 0 3 6 9 10 20 30 40 50 60 70 80 90 100 103 106
dBW 23 26 29 30 33 36 39 40 50 60 70 80 90 100 110 120 130 133 136
Power 5 mW 2.5 mW 1.25 mW 1 mW 0.5 mW 0.25 mW 0.125 mW 0.1 mW 0.01 mW 1 mW 0.1 mW 0.01 mW 1 nW 0.1 nW 0.01 nW 1 pW 0.1 pW 0.01 pW 0.001 pW
360
GSM-001-103
Fresnel zone
The Fresnel (pronounced Fresnel) actually consists of several different zones, each one forming an ellipsoid around the major axis of the direct propagation path. Each zone describes a specific area depending on the wavelength of the signal frequency. If a signal from that zone is reflected of an obstacle which protrudes into the zone, it means that a reflected signal as well as the direct path signal will arrive at the receiver. Radio waves reflected in the first Fresnel zone will arrive at the receiver out of phase with those taking the direct path and so combine destructively. This results in a very low received signal strength. It is important when planning a cell to consider all the radio paths for obstacles which may produce reflections from the first Fresnel zone because if they exist it is like planning permanent areas of no coverage in certain parts of the cell. In order to calculate wether or not this condition exists the radius of the first Fresnel zone at the point where the object is suspected of intruding into the zone must be calculated. The formula, illustrated in Figure 3-16, is as follows: F1 + Where: F1 d1 d2 l d is: d1 < d2 < l d
the first Fresnel zone. distance from Tx antenna to the obstacle. distance from Rx antenna to the obstacle. wavelength of the carrier wave. total path length.
Once the cell coverage has been calculated the radio path can be checked for any objects intruding into the first Fresnel zone. Ideally the link should be planned for no intrusions but in some cases they are unavoidable. If that is the case then the next best clearance for the first Fresnel zone is 0.6 of the radius. When siting a BTS on top of a building care must be taken with the positioning and height of the antenna to ensure that the roof edge of the building does not intrude into the first Fresnel zone.
FREQUENCY = 900 MHz WAVELENGTH = 30 cm
F1 d
d1
d2
Figure 3-16 First Fresnel zone radius calculation
14th Apr 00
361
GSM-001-103
Radio refractive index

It is important when planning a cell or microwave radio link to have an understanding of the effects changes in the Radio Refractive Index (RRI) can have on microwave communications, also what causes these changes. RRI measurements provide planners with information on how much a radio wave will be refracted by the atmosphere at various heights above sea level. Refraction, Figure 3-17, is the changing of direction of propagation of the radio wave as it passes from a more dense layer of the atmosphere to a less dense layer, which is usual as one increases in height above sea level. It also occurs when passing from a less dense layer to a dense layer. This may also occur under certain conditions even at higher altitudes.
REFRACTION OCCURS AS THE RADIO WAVE PASSES THROUGH LAYERS OF DIFFERENT ATMOSPHERIC DENSITY
EARTH
Figure 3-17 Refraction The main effect to cell planners is that changes in the RRI can increase or decrease the cell radius depending on conditions prevailing at the time. The RRI is normally referenced to a value n at sea level. The value will vary with seasons and location but for the UK the mean value is 1.00034. This figure is very cumbersome to work with so convention has converted n to N. Where: N is: (n1) x 10 to the power of 6.
The value of N now becomes 340 units for the UK. The actual seasonal and global variations are only a few 10 s of units at sea level. The value of N is influenced by the following : S The proportion of principle gasses in the atmosphere such as nitrogen, oxygen, carbon dioxide, and rare gasses. These maintain a near constant relationship as height is increased so although they affect the RRI the affect does not vary. The quantity of water vapour in the atmosphere. This is extremely variable and has significant effects on the RRI. Finally the temperature, pressure, and water vapour pressure have major effects on the RRI.
S S
All the above will either increase or decrease the RRI depending on local conditions, resulting in more or less refraction of a radio wave. Typically though for a well mixed atmosphere the RRI will fall by 40 N units per 1 km increase in height above sea level.
362
14th Apr 00
GSM-001-103
Measurement of the RRI

There are two main ways of measuring the RRI at any moment in time. Firstly by use of Radio Sonds. This is an instrument which is released into the atmosphere, normally attached to a balloon. As it rises it measures the temperature, pressure, and humidity. These are transmitted back to the ground station with a suitable reference value. The measurements of pressure are made every 35 m, humidity every 25 m, and temperature every 10 m. These together provide a relatively crude picture of what the value of the RRI is over a range of heights. The second method is a more serious means of measuring the RRI. It uses fast response devises called refractometers. These maybe carried by a balloon , aircraft, or be spaced apart on a high tower. These instruments are based upon the change in resonant frequency of a cavity with partially open ends caused by the change in RRI of air passing through the cavity. This gives a finer measurement showing variations in the RRI over height differences of a little over one meter. This is illustrated by the graph in Figure 3-18. The aircraft mounted refractometer can give a detailed study over several paths and heights.
HEIGHT (km)
340
RRI (N)
Figure 3-18 Measurement of the RRI
14th Apr 00
363
GSM-001-103
Effects of deviations from the normal lapse rate

The lapse rate of 40 N per km is based on clear sky readings with good atmosphere mixing. Normally a radio system is calibrated during these conditions and the height alignment in the case of a microwave point to point link is determined. It is easier to see the effects on a microwave point to point system when examining the effects of uneven variations of the RRI. Figure 3-19A shows an exaggerated curved radio path between two antennas under normal conditions. The signal is refracted by the atmosphere and arrives at the receiving antenna. Figure 3-19B illustrates the condition known as super refraction where the radio waves are not diffracted enough. This occurs when the lapse rate is less than 40 N per km. Under these conditions the main signal path will miss the receive antenna. Similar effects on a cell would increase the cell size as the radio waves would be propagated further resulting in co-channel and adjacent channel interference. The second effect is where the RRI increases greater than 40 N per km. This results in the path being refracted too much and not arriving at the receive antenna. This condition is known as sub-refraction. While this will not cause any interference as with super refraction, it could result in areas of no coverage. See Figure 3-19C. The last effect is known as ducting and occurs when the refraction of the radio wave produces a path which matches the curvature of the Earth. If this happens radio waves are propagated over far greater distances than normal and can produce interference in places not normally subjected to any.
EARTH
NORMAL REFRACTION
EARTH
SUPER REFRACTION
EARTH
SUB-REFRACTION
Figure 3-19 Effects on a microwave system

364
14th Apr 00
GSM-001-103
Events which can modify the clear sky lapse rate

There are four main events which can modify the clear sky lapse rate and they are as follows:
Radiation nights
This is the result of a very sunny day followed by clear skies overnight. The Earth absorbs heat during the day and the air temperature rises. After sunset the Earth radiates heat into the atmosphere and its surface temperature drops. This heat loss is not replaced resulting in air closer to the surface cooling faster than air higher up. This condition causes a temperature inversion and the RRI profile no longer has a uniform lapse rate. This effect will only occur overland and not water as water temperature variations are over a longer period of time.
Advection effects
This effect is caused by high pressure weather fronts moving from land to the sea or other large expanses of water. The result is warm air from the high pressure front covering the relatively cool air of the water. When this combination is then blown back over land a temperature inversion is caused by the trapped cool air. It will persist until the air mass strikes high ground where the increase in height will mix and dissipate the inversion.
Subsidence
This occurs again in a high pressure system this time overland when air descending from high altitude is heated by compression as it descends. This heated air then spreads over the cooler air below. This type of temperature inversion normally occurs at an altitude of 1 km but may occasionally drop to 100 m where it cause severe disruption to radio signals.
Frontal systems
This happens when a cold front approaching an area forces a wedge of cold air under the warmer air causing a temperature inversion. These disturbances tend to be short lived as the cold front usually dissipate quickly. Although those described above are the four main causes of RRI deviations, local pressure, humidity and temperature conditions could well give rise to events which will affect the RRI.
14th Apr 00
365
GSM-001-103
Environmental effects on propagation

At the frequency range used for GSM it is important to consider the effects that objects in the path of the radio wave will have on it. As the wave length is approximately 30 cm for GSM900 and 15 cm for GSM1800, most objects in the path will have some effect on the signal. Such things as vehicles, buildings, office fittings even people and animals will all affect the radio wave in one way or another. The main effects can be summarized as follows: S S S S S Attenuation. Reflection. Scattering. Diffraction. Polarization changes.
Attenuation
This will be caused by any object obstructing the wave path causing absorption of the signal. The effects are quite significant at GSM frequencies but still depend on the type of materials and dimensions of the object in relation to the wavelength used. Buildings, trees and people will all cause the signal to be attenuated by varying degrees.
INCOMING WAVE OBJECT ABSORBS THE ENERGY IN THE RADIO WAVE OUTGOING WAVE ATTENUATED BY THE OBJECT
Figure 3-20 Attenuation
Reflection
This is caused when the radio wave strikes a relatively smooth conducting surface. The wave is reflected at the same angle at which it arrived. The strength of the reflected signal depends on how well the reflector conducts. The greater the conductivity the stronger the reflected wave. This explains why sea water is a better reflector than sand.
INCIDENT WAVE REFLECTED WAVE
EQUAL ANGLES SMOOTH SURFACE, SUCH AS WATER, VERY REFLECTIVE
AMOUNT OF REFLECTION DEPENDS ON CONDUCTIVITY OF THE SURFACE
Figure 3-21 Reflection

366
14th Apr 00
GSM-001-103
Scattering
This occurs when a wave reflects of a rough surface. The rougher the surface and the relationship between the size of the objects and the wave length will determine the amount of scattering that occurs.
INCIDENT WAVE ENERGY IS SCATTERED ROUGH STONY GROUND
Figure 3-22 Scattering
Diffraction
Diffraction is where a radio wave is bent off its normal path. This happens when the radio wave passes over an edge, such as that of a building roof or at street level that of a corner of a building. The amount of diffraction that takes place increases as the frequency used is increased. Diffraction can be a good thing as it allows radio signals to reach areas where they would not normally be propagated.
SIDE VIEW
EXPECTED PATH
SHADOW AREA
DIFFRACTED WAVE
PLAN VIEW
DIFFRACTED WAVE GIVING COVERAGE AROUND THE CORNER
MICRO BTS AT STREET LEVEL
DIFFRACTED WAVE GIVING COVERAGE AROUND THE CORNER
Figure 3-23 Diffraction
14th Apr 00
367
GSM-001-103
Polarization changes
This can happen any time with any of the above effects of due to atmospheric conditions and geomagnetic effects such as the solar wind striking the earths atmosphere. These polarisation changes mean that a signal may arrive at the receiver with a different polarisation than that which the antenna has been designed to accept. If this occurs the received signal will be greatly attenuated by the antenna.
ELECTRICAL PART OF WAVE VERTICALLY POLARIZED ELECTRICAL PART OF WAVE HORIZONTALLY POLARIZED (CHANGED BY ELECTRICAL STORM) ELECTRICAL STORM
Tx
Figure 3-24 Polarization
368
Rx
14th Apr 00
GSM-001-103
Multipath propagation
Rayleigh and Rician fading
As a result of the propagation effects on the transmitted signal the receiver will pick up the same signal which has been reflected from many different objects resulting in what is known as multipath reception. The signals arriving from the different paths will all have travelled different distances and will therefore arrive at the receiver at different times with different signal strengths. Because of the reception time difference the signals may or may not be in phase with each other. The result is that some will combine constructively resulting in a gain of signal strength while others will combine destructively resulting in a loss of signal strength. The receiving antenna does not have to be moved very far for the signal strength to vary by many tens of dBs. For GSM900 a move of just 15 cm or half a wavelength will suffice to observe a change in signal strength. This effect is known as multipath fading. It is typically experienced in urban areas where there are lots of buildings and the only signals received are from reflections and refractions of the original signal.
14th Apr 00
369
GSM-001-103
Rayleigh environment
This type of environment has been described by Rayleigh. He analysed the signal strength along a path with a moving receiver and plotted a graph of the typical signal strength measured due to multipath fading. The plot is specifically for non line of sight, Figure 3-25, and is known as Rayleigh distribution, Figure 3-26.
Rx
Tx
Figure 3-25 Propagation effect Rayleigh fading environment

SIGNAL STRENGTH
THRESHOLD
DEEP NULLS 1/2 WAVELENGTH
DISTANCE
Figure 3-26 Rayleigh distribution
370
14th Apr 00
GSM-001-103
Rician environment
Where the signal path is predominantly line of sight, Figure 3-27, with insignificant reflections of refractions arriving at the receiver, this is know as Rician distribution, Figure 3-28. There are still fades in signal strength but they rarely dip below the threshold below which they will not be processed by the receiver.
Rx
Tx
Figure 3-27 Propagation effect Rician environment

SIGNAL STRENGTH
THRESHOLD
DISTANCE
Figure 3-28 Rician distribution Comparison of DCS1800 and GSM900: From a pure frequency point of view it would be true to say that DCS1800 generally has more fades than GSM900. However, they are usually less pronounced.
14th Apr 00
371
GSM-001-103
Receive signal strength

A moving vehicle in an urban environment seldom has a direct line of sight path to the base station. The propagation path contains many obstacles in the form of buildings, other structures and even other vehicles. Because there is no unique propagation path between transmitter and receiver, the instantaneous field strength at the MS and BTS exhibits a highly variable structure. The received signal at the mobile is the net result of many waves that arrive via multiple paths formed by diffraction and scattering. The amplitudes, phase and angle of arrival of the waves are random and the short term statistics of the resultant signal envelope approximate a Rayleigh distribution. Should a microcell be employed, where part of a cell coverage area be predominantly line of sight then Rician distribution will be exhibited.
Free space loss

This is the lose of signal strength that occurs as the radio waves are propagated through free space. Free space is defined as the condition where there are no sources of reflection in the signal path. This is impossible to achieve in reality but it does give a good starting point for all propagation loss calculations. Equally important in establishing path losses is the effect that the devices radiating the signal have on the signal itself. As a basis for the calculation it is assumed the device is an isotopic radiator. This is a theoretical pin point antenna which radiates equally in every direction. If the device was placed in the middle of a sphere it would illuminated the entire inner surface with an equal field strength. In order to find out what the power is covering the sphere, the following formula used: P+ Where: Pt d is: Pt 4 p < d2
the input power to the isotopic antenna. the distance from the radiator to the surface of the sphere.
This formula illustrates the inverse square law that the power decreases with the square of the distance. In order to work out the power received at a normal antenna the affective aperture (Ae) of the receiving antenna must be calculated.
2 Ae + l 4 p
The actual received power can be calculated as follows: Pr + P < Ae Now if P is substituted with the formula for the power received over the inner surface of a sphere and Ae with its formula the result is: Pr +
2 Pt < l 2 4 p<d 4 p
372
14th Apr 00
GSM-001-103
Free space path loss

This is the ratio of the actual received power to the transmitted power from an isotopic radiator and can be calculated by the formula: 20 log 4 p<d l
Logs are used to to make the figures more manageable. Note that the formula is dependant on distance and frequency. The higher the frequency the shorter the wavelength and therefore the greater the path loss. The formula above is based on units measured in metres. To make the formula more convenient it can be modified to use kilometre and megahertz for the distance and frequency. It becomes: Free space loss Where: d f is: + 32 ) 20 log d ) 20 log f dBs the distance in km. the frequency in MHz.
Plane earth loss

The free space loss as stated was based solely on a theoretical model and is of no use by itself when calculating the path loss in a multipath environment. To provide a more realistic model, the earth in its role as a reflector of signals must be taken into account. When calculating the plane earth loss the model assumes that the signal arriving at the receiver consists of a direct path component and a reflective path component. Together these are often called the space wave. The formula for calculating the plane earth loss is: L + 20 log d2 h1 < h2 dBs
This takes into account the different antenna heights at the transmitter and receiver. Although this is still a simple representation of path loss. When this formula is used is implies the inverse fourth law as opposed to the inverse square law. So for every doubling of distance there is a 12 dB loss instead of 6 db with the free space loss calculation. The final factors in path loss are the ground characteristics. These will increase the path loss even further depending on the type of terrain, refer to Figure 3-29. The ground characteristics can be divided into three groups: 1. 2. 3. Excellent ground. For example sea water, this provides the least attenuation so a lower path loss. Good ground. For example rich agricultural land, moist loamy lowland and forests. Poor ground. For example Industrial or Urban areas, rocky land. These give the highest losses and are typically found when planning Urban cells.
14th Apr 00
373
GSM-001-103
Tx
FREE SPACE LOSS d
Rx
PATH LOSS INCREASES 6dB FOR A DOUBLING OF d.
Tx
Rx h1
2
h2
PLANE EARTH LOSS INCLUDES ONE EARTH REFLECTOR. PATH LOSS INCREASES 12dB FOR A DOUBLING OF d.
Tx
Rx h1
3
h2
PLANE EARTH + CORRECTION FACTOR FOR TYPE OF TERRAIN. PATH LOSS INCREASES 12dB FOR A DOUBLING OF d + A FACTOR FOR TYPE OF TERRAIN.
Figure 3-29 Plane earth loss
374
14th Apr 00
GSM-001-103
Clutter factor
The propagation of the RF signal in an urban area is influenced by the nature of the surrounding urban environment. An urban area can then be placed into two sub categories; the built up area and the suburban area. The built up area contains tall buildings, office blocks, and highrise residential tower blocks, whilst a suburban area contains residential houses, playing fields and parks as the main features. Problems may arise in placing areas into one of these two categories, so two parameters are utilised, a land usage factor describing the percentage of the area covered by buildings and a degree of urbanization factor describing the percentage of buildings above storeys in the area. B(db) + 20 ) Where: B F L H K U is: F ) 0.18L * 0.34H ) K 40 the clutter factor in dBs. the frequency of RF signal. the percentage of land within 500m square occupied by buildings. the difference in height between the squares containing the transmitter and receiver. 0.094U 5.9 the percentage of L occupied by buildings above 4 storeys.
A good base station site should be high enough to clear all the surrounding obstacles in the immediate vicinity. However, it should be pointed out that employing high antennas increases the coverage area of the base station. However, it will also have adverse effects on channel re-use distances because of the increased possibility of co-channel interference.
Antenna gain
The additional gain provided by an antenna can be used to enhance the distance that the radio wave is transmitted. Antenna gain is measured against an isotopic radiator. Any antenna has a gain over an isotopic radiator because in practice it is impossible to radiate the power equally in all directions. This means that in some directions the radiated power will be concentrated. This concentration or focusing of power is what enables the radio waves to travel further than those that if it were possible were radiated from an isotopic radiator. See Figure 3-30.
ISOTOPIC RADIATOR (A SPHERICAL PATTERN) VERTICAL DIPOLE RADIATION PATTERN (SIDE VIEW)
TRANSMITTER
Figure 3-30 Focusing of power
14th Apr 00
375
GSM-001-103
The gain of a directional antenna is measured by comparing the signal strength of a carrier emitted from an isotopic antenna and the directional antenna. First the power of the isotopic radiator is increased so that both receive levels are the same. The emitted powers required to achieve that are then compared for both antennas. The difference is a measure of gain experienced by the directional antenna. It will always have some gain when compared to an isotopic radiator. See example in Figure 3-31.
10 W
MEASUREMENT POINT
MEASUREMENT POINT
1000 W
TRANSMITTER
Figure 3-31 Measurement of gain In this example to achieve a balanced receive level the isotopic radiator must have an input power of 1000 W as opposed to the directional antenna which only requires 10 W. The gain of the directional antenna is 100 or 20 dBi. Where: i is: for isotopic.
The more directional the antenna is made the more gain it will experience. This is apparent when sectorizing cells . Each sectored cell will require less transmit power than the equivalent range omni cell due to the gain of its directional antenna, typically 14 to 17 dBi. The gain is also present in the receive path though in all cases the gain decreases as the frequency increases. That is why the uplink mobile to BTS frequency is usually the lowest part of the frequency range. This gives a slight gain advantage to the lower power mobile transmitter.
376
14th Apr 00
GSM-001-103
Propagation in buildings
With the increased use of hand portable equipment in mobile cellular systems combined with the increased availability of cordless telephones, it has become essential to study RF propagation into and within buildings. When calculating the propagation loss inside a building, Figure 3-32, a building loss factor is added to the RF path loss. This building loss factor is included in the model to account for the increase in attenuation of the received signal when the mobile is moved from outside to inside a building. This is fine if all users stood next to the walls of the building when making calls, but this does not happen, so the internal distance through which the signal must pass which has to be considered. Due to the internal construction of a building, the signal may suffer form spatial variations caused by the design of the interior of the building. The building loss tends to be defined as the difference in the median field intensity at the adjacent area just outside the building and the field intensity at a location on the main floor of the building. This location can be anywhere on the main floor. This produces a building median field intensity figure which is then used for plotting cell coverage areas and grade of service. When considering coverage in tall buildings, coverage is being considered throughout the building, if any floors of that building are above the height of the transmitting antenna a path gain will be experienced.
TRANSMITTER
WdBm XdBm
XdBm = SIGNAL STRENGTH OUTSIDE BUILDING WdBm = SIGNAL STRENGTH INSIDE BUILDING BUILDING INSERTION LOSS (dBm) = X W = BdBm
GAIN
TRANSMITTER
REFERENCE POINT
Figure 3-32 In building propagation
14th Apr 00
377
GSM-001-103
The Okumura method

In the early 1960s a Japanese engineer named Okumura carried out a series of detailed propagation tests for land mobile radio services at various different frequencies. The frequencies were 200 MHz in the VHF band and 453, 922, 1310, 1430, and 1920 MHz in the UHF band. The results were statistically analyzed and described for distance and frequency dependencies of median field strength, location variabilities and antenna height gain factors for the base and mobile stations in urban, suburban, and open areas over quasi-smooth terrain. The correction factors corresponding to various terrain parameters for irregular terrain, such as rolling hills, isolated mountain areas, general sloped terrain, and mixed land/sea path were defined by Okumura. As a result of these tests carried out primarily in the Tokyo area, a method for predicting field strength and service area for a given terrain of a land mobile radio system was defined. The Okumura method is valid for the frequency range of 150 to 2000 MHz, for distances between the base station and the mobile stations of 1 to 100 km, with base station effective antenna heights of 30 to 100m. The results of the median field strength at the stated frequencies were displayed graphically. Different graphs were drawn for each of the test frequencies in each of the terrain environments (for example; urban, suburban, hilly terrain) Also shown on these graphs were the various antenna heights used at the test transmitter base stations. The graphs show the median field strength in relation to the distance in km from the site. As this is a graphical representation of results it does not transfer easily into a computer environment. However, the results provided by Okumura are the basis on which path loss prediction equations have been formulated. The most important work has been carried out by another Japanese engineer named Hata. Hata has taken Okumuras graphical results and derived an equation to calculate the path loss in various environments. These equations have been modified to take into account the differences between the Japanese terrain and the type of terrain experienced in Western Europe.
378
14th Apr 00
GSM-001-103
110
922 MHz
100 h.= 320 m h.= 220 m 90
X X X
Free Space
h.= 140 m h.= 45m h.= 3 m
ERP FIELD STRENGTH (dB rel. 1 uV/m) FOR 1 kW
80
70
X X
60
X X X X X
50
40
X X X X X X X
30
20
X X
X X X X X
10
10
0.6
5 LOG SCALE
10
20
30
40
50
60
70
80
90
100
LINEAR SCALE DISTANCE (km)
PROPAGATION GRAPH FOR 922 MHz
Figure 3-33 Okumura propagation graphs
14th Apr 00
379
GSM-001-103
Hatas propagation formula

Hata used the information contained in Okumuras propagation loss report of the early 1960s, which presented its results graphically, to define a series of empirical formulas to allow propagation prediction to be done on computers. The propagation loss in an urban area can be presented as a simple formula of: A ) B log 10R Where: A B R is: the frequency. the antenna height function. the distance from the transmitter.
Hata using this basic formula which is applicable to radio systems is the UHF and VHF frequency ranges, added an error factor to the basic formula to produce a series of equations to predict path loss. To facilitate this action Hata has set a series of limitations which must be observed when using this empirical calculation method: Where: Frequency range (fc) Distance (R) Base station antenna height (hb) Vehicular antenna height (hm) is: 100 1500 MHz 1 20 km 30 200 M 1 10 M
Hata defined three basic formulas based upon three defined types of coverage area; urban, suburban and open. It should be noted that Hatas formula predicts the actual path loss, not the final signal strength at the receiver. Urban Area: Lp = 69.55 + 26.16 log10fc 13.82.log10hb a (hm)# + (44.9 6.66. log10hb).log10R dB Where: # is: Correction factor for vehicular station antenna height.
Medium Small City: a(hm) = (1.1 . log10fc 0.7).hm (1.56.log10fc 0.8) Large City: a(hm) = 3.2 (log10 11.75 hm)2 4.97 Where: Suburban Area: Lps = Lp [Urban Area] 2.[log10 (f/28)]2 5.4 dB Rural Area: Lpr = Lp [Urban Area] 4.78.(log10fc)2 + 18.33.log10fc 40.94 dB fc is: >400 MHz.
380
14th Apr 00
GSM-001-103
Power budget and system balance

In any twoway radio system the radio path losses and equipment output powers must be taken into account for both directions. This is especially true in a mobile network where there are different characteristics for the uplink and downlink paths. These include receive path diversity gain in the uplink only, the possibility of mast head amplifiers in the uplink path, the output power capability of the mobile is a lot less than that of the BTS and the sensitivity of the BTS receiver is usually better than the mobiles. If these differences are not considered it is possible that the BTS will have a service area far greater than that which the mobile will be able to use due to its limited output power. Therefore the path losses and output powers in the uplink and downlink must be carefully calculated to achieve a system balance. One where the power required of the mobile to achieve a given range is equitable to the range offered by the power transmitted by the BTS. The output powers of the BTS and mobile are unlikely to be the same for any given distances due to the differences in uplink and downlink path losses and gains as described above. Once the area of coverage for a site has been decided the calculations for the power budget can be made. The system balance is then calculated which will decide the output powers of the BTS and mobile to provide acceptable quality calls in the area of coverage of the BTS. The BTS power level must never be increased above the calculated level for system balance. Although this seems a simple way to increase coverage, the system balance will be different and the mobile may not be able to make a call in the new coverage area. To increase the cell coverage, an acceptable way is to increase the gain of the antenna. This will affect both the uplink and downlink therefore maintaining system balance. Where separate antennas are used for transmit and receive they must be of similar gain. If the cell size is to be reduced then this is not a problem as the BTS power can be altered and the mobiles output power is adaptive all the time. There is a statistic in the BTS that checks the path balance every 480 ms for each call in progress. The latest uplink and downlink figures reported along with the actual mobile and BTS transmit powers are used in a formula to give an indication of the path balance.
14th Apr 00
381
GSM-001-103
GSM900 path loss

Figure 3-34 and Figure 3-35 compare the path losses at different heights for the BTS antenna and different locations of the mobile subscriber between one and 100 km cell radius.
220 210 200 190 PATH LOSS (dB) 180 170 160 150 140 130 120 110 100 90 1 10 CELL RADIUS (km) 100
RURAL (OPEN) RURAL (QUASI OPEN) URBAN INDOOR URBAN SUBURBAN
Figure 3-34 BTS antenna height of 50 m, MS height of 1.5 m (GSM900)
220 210 200 190 PATH LOSS (dB) 180 170 160 150 140 130 120 110 100 90 1 10 CELL RADIUS (km) 100
RURAL (OPEN) RURAL (QUASI OPEN) URBAN INDOOR URBAN SUBURBAN
Figure 3-35 BTS antenna height of 100 m, MS height of 1.5 m (GSM900)

382
14th Apr 00
GSM-001-103
Path loss GSM900 vs DCS1800

Figure 3-36 illustrates the greater path loss experienced by the higher DCS1800 frequency range compared to the GSM900 band. The cell size is typical of that found in urban or suburban locations. The difference in path loss for the GSM900 band at 0.2 km compared with 3 km is 40 dB, a resultant loss factor of 10,000 compared to the measurement at 0.2 km.
170
160
DCS1800 (METROPOLITAN CENTRES)
150 PATH LOSS (dB)
140
130
GSM900
120
DCS1800 (MEDIUM SIZED CITIES AND SUBURBAN CENTRES)
110
100 0.1 0.3 CELL RADIUS (km) 1.0 3.0
Figure 3-36 Path loss vs cell radius for small cells
14th Apr 00
383
Frequency re-use
GSM-001-103
Frequency re-use
Introduction to re-use patterns
The network planner designs the cellular network around the available carriers or frequency channels. The frequency channels will be allocated to the network provider from the GSM, EGSM, or DCS1800 band as shown below:
GSM EGSM = Tx 935 960 MHz Rx 890 915 MHz = Tx 925 960 MHz Rx 880 915 MHz 124 RF carriers 174 RF carriers 374 RF carriers
DCS1800 = Tx 1805 1880 MHz Rx 1710 1785 MHz
Within this range of frequencies only a finite number of channels may be allocated to the planner. The number of channels will not necessarily cover the full frequency spectrum and there has to be great care taken when selecting/allocating the channels. Installing a greater number of cells will provide greater spectral efficiency with more frequency re-use of available frequencies. However, a balance must be struck between spectral efficiency and all the costs of the cell. The size of cells will also indicate how the frequency spectrum is used. Maximum cell radius is determined in part by the output power of the mobile subscriber (MS) (and therefore, its range) and interference caused by adjacent cells. Remember that the output power of the MS is limited in both the GSM900 and DCS1800 systems. Therefore to plan a balanced transmit and receive radio path the planner must make use of the path loss and thus the link budget. The effective range of a cell will vary according to location, and can be as much as 35 km in rural areas and as little as 1 km in a dense urban environment.
CARRIER F 33 INTERFERING CARRIER F 33
RECEIVE SIGNAL LEVEL
75dBm
100dBm SERVING BTS DISTANCE
INTERFERING BTS
MOBILE POSITION
Figure 3-37 Frequency re-use

384
14th Apr 00
GSM-001-103
Frequency re-use
Re-use pattern
The total number of radio frequencies allocated is split into a number of channel groups or sets. These channel groups are assigned on a per cell basis in a regular pattern which repeats across all of the cells. Thus, each channel set may be re-used many times throughout the coverage area, giving rise to a particular re-use pattern (for example; 7 cell re-use pattern, Figure 3-38).
EACH USING CHANNEL SETS
3 4 5 3 1 2 1
2 7 6 4 7 5 3 1 6 2
4 7 3 4 5 1 5
1 6 2 7 6
7 CELL RE-USE
Figure 3-38 7 cell re-use pattern Clearly, as the number of channel sets increases, the number of available channels per cell reduces and therefore the system capacity falls. However, as the number of channel sets increases, the distance between co-channel cells also increases, thus the interference reduces. Selecting the optimum number of channel sets is therefore a compromise between quality and capacity.
14th Apr 00
385
Frequency re-use
GSM-001-103
4 site 3 cell re-use pattern

Due to this increase in frequency robustness within GSM, different re-use frequency patterns can be adopted, which gives an overall greater frequency efficiency. The most common re-use pattern is 4 site with 3 cells. With the available frequency allocation divided into 12 channels sets numbered a13, b13, c13, and d13. The re-use pattern is arranged so that the minimum re-use distance between cells is at least 2 to 1. The other main advantage of this re-use pattern is if a new cell is required to be inserted in the network, then there is always a frequency channel set available which will not cause any adjacent channel interference.
c1 c2 d1 d2 b1 b2 b3 a2 c1 c2 c3 d2 b1 b2 b3 a2 a3 NEW CELL CAN USE d13 FREQ ALLOCATION a1 d3 b2 b3 b1 d1 a3 c2 c3 d2 d3 d1 c1 a1 d3 b2 b3 a2 a3 a1 b1 c3 d2 d3 d1
EXAMPLE b1 b2 a1 a2 a3 c2 c3 c1 b3 a2
Figure 3-39 4 site 3 cell re-use pattern
386
14th Apr 00
GSM-001-103
Frequency re-use
2 site 6 cell re-use pattern

Another solution to possible network operators capacity problems may be an even higher frequency re-use pattern. The re-use pattern, shown in Figure 3-40, uses a 2 site 6 cell re-use. Therefore: 2 sites repeated each with 6 cells = 2 x 6 = 12 groups. If the operator has only 24 carriers allocated for their use, they are still in a position to use 2 carriers per cell. However this may be extremely difficult and may not be possible to implement. It also may not be possible due to the current network configuration. However, the subscribers per km ratio would be improved.
a1 a6 b1 b6 b5 b4 a4 a5 a6 a1 a3 a2 b2 b3 b6 b1 b2 a5 a4 b5 b4 b3 a2 a3
60 SECTORS
Figure 3-40 2 site 6 cell re-use pattern
14th Apr 00
387
Frequency re-use
GSM-001-103
Carrier/ Interference (C/I) ratio

When a channel is re-used there is a risk of co-channel interference which is where other base stations are transmitting on the same frequency. As the number of channel sets increases the number of available channels per cell reduces and therefore capacity reduces. But the interference level will also reduce, increasing the quality of service. The capacity of any one cell is limited by the interference that can be tolerated for a given grade of service. A number of other factors, apart from the capacity, effect the interference level: S S S S S Power control (both BTS and MS). Hardware techniques. Frequency hopping (if applied). Sectorization. Discontinuous transmission (DTX).
Carrier/Interference measurements taken at different locations within the coverage of a cell can be compared to a previously defined acceptable criterion. For instance, the criterion for the C/I ratio maybe set at 8 dB with the expectation that the C/I measurements will be better than that figure, for 90% of cases (C/I90). For a given re-use pattern, the predicted C/I ratio related to the D/R ratio can be determined, to give overall system comparison. For example: GSM System : 9dB + C + 7.94 I
(D R)4 + 7.94 6 (D) 4 + 47.66 R
Therefore Thus
D + 4 47.66 + 2.62 R
C/
(2 CELLS USING THE SAME BCCH FREQUENCY) D I CAN BE RELATED TO /R
BS R
MS
BS
DISTANCE BETWEEN CELLS
D
ANALOGUE SYSTEM D/R = 4.4 GSM SYSTEM D/R= 2.62
Figure 3-41 Carrier interference measurements

388
14th Apr 00
GSM-001-103
Frequency re-use
Other sources of interference

Adjacent Channel Interference: This type of interference is characterised by unwanted signals from other frequency channels spilling over or injecting energy into the channel of interest. With this type of interference being influenced by the spacing of RF channels, its effect can be reduced by increasing the frequency spacing of the channels. However, this will have the adverse effect of reducing the number of channels available for use within the system. The base station and the mobile stations receiver selectivity can also be designed to reduce the adjacent channel interference. Environmental Noise: This type of interference can also provide another source of potential interference. The intensity of this environmental noise is related to local conditions and can vary from insignificance to levels which can completely dominate all other sources of noise and interference. There are also several other factors which have to be taken into consideration. The interfering co-channel signals in given cell would normally arise from a number of surrounding cells not just one. What effect will directional antennas have when employed? Finally, if receiver diversity is to be used, what type and how is implementation to be achieved?
Sectorization of sites
As cell sizes are reduced, the propagation laws indicate that the levels of carrier interference tend to increase. In a omni cell, co-channel interference will be received from six surrounding cells all using the same channel sets. Therefore, one way of significantly cutting the level of interference is to use several directional antennas at the base stations, with each antenna radiating a sector of the cell, with a separate channel set. Sectorization increases the number of traffic channels available at a cell site which means more traffic channels available for subscribers to use. Also by installing more capacity at the same site there is a significant reduction in the overall implementation and operating costs experienced by the network operator. By using sectorized antennas, sectorization allows the use of geographically smaller cells and a tighter more economic re-use of the available frequency spectrum. This results in better network performance to the subscriber and a greater spectrum efficiency. The use of sectorized antennas allows better control of any RF interference which results in a higher call quality and an improved call reliability. More importantly for the network designer sectorization extends and enhances the cells ability to provide the in-building coverage that is assumed by the hand portable subscriber. Sectorization provides the flexibility to meet uneven subscriber distribution by allowing if required an uneven distribution of traffic resources across the cells on a particular site. This allows a more efficient use of both the infrastructure hardware and the available channel resources. Finally, with the addition of diversity techniques an improved sensitivity and increased interference immunity are experienced in a dense urban environment.
14th Apr 00
389
Overcoming adverse propagation effects
GSM-001-103

Hardware techniques
Multipath fading is responsible for more than just deep fades in the signal strength. The multipath signals are all arriving at different times and the demodulator will attempt to recover all of the time dispersed signals. This leads to an overlapping situation where each signal path influences the other, making the original data very hard to distinguish. The example opposite shows three component paths of the original signal which after demodulation should give three examples of the original data. This is not the case in reality as the output will be the result of the combination of the three inputs. As is shown in the diagram the output is very different making it difficult to decide wether the data should represent a 1 or a 0. This problem is known as inter symbol interference (ISI) and is made worse by the fact that the output from the demodulator is rarely a square wave. The sharp edges are normally rounded off so that when time dispersed signals are combined it makes it difficult to distinguish the original signal state. Another factor which makes things even more difficult is that the modulation technique Gaussian minimum shift keying, itself introduces a certain amount of ISI. Although this is a known distortion and can under normal conditions be filtered out, when it is added to the ISI distortion caused by the time delayed multipath signals it makes recovery of the original data that much harder.
Frequency hopping
Frequency hopping is a feature that can be implemented on the air interface, (for example; the radio path to the MS), to help overcome the effects of multipath fading. GSM recommends only one type of frequency hopping, baseband hopping; but the Motorola BSS will support an additional type of frequency hopping called synthesizer hopping.
Baseband hopping
Baseband Hopping is used when a base station has several DRCU/TCUs available. The data flow is simply routed in the baseband to various DRCU/TCUs, each of which operates on a fixed frequency, in accordance with the assigned hopping sequence. The different DRCU/TCUs will receive a specific individual timeslot in each TDMA frame containing information destined for different MSs. There are important points to note when using this method of providing frequency hopping. S S S There is a need to provide as many DRCU/TCUs as the number of allocated frequencies. The use of remote tuning combiners, cavity combining blocks or hybrid combiners is acceptable in BTS6 applications. Within M-Cell equipment applications the use of either combining bandpass filter/hybrid or cavity combining block is acceptable.
390
14th Apr 00
GSM-001-103
Synthesizer hopping
Synthesizer hopping uses the frequency agility of the DRCU/TCU to change frequencies on a timeslot basis for both transmit and receive. The SCB in the DRCU and the digital processing and control board in the TCU calculates the next frequency and programmes one of the pair of Tx and Rx synthesizers to go to the calculated frequency. As the DRCU/TCU uses a pair of synthesizers for both transmit and receive, as one pair of synthesizers is being used the other pair are returning. There are important points to note when using synthesizer hopping: S Instead of providing as many DRCU/TCUs as the number of allocated frequencies, there is only a need to provide as many DRCU/TCUs as determined by traffic plus one for the BCCH carrier. The output power available with the use of hybrid combiners must be consistent with coverage requirements.
Therefore as a general rule, cells with a small number of carriers will make good candidates for synthesizer hopping, whilst cells with many carriers will be good candidates for baseband hopping. There is also the other rule. There can only be one type of hopping on a BTS site, not a combination of the two.
14th Apr 00
391
GSM-001-103
Error protection and detection

To protect the logical channels from transmission errors introduced by the radio path, many different coding schemes are used. Figure 3-43 illustrates the coding process for speech, control and data channels; the sequence is very complex. The coding and interleaving schemes depend on the type of logical channel to be encoded. All logical channels require some form of convolutional encoding, but since protection needs are different, the code rates may also differ. The coding protection schemes,shown in Figure 3-42, are:
Speech channel encoding

The speech information for one 20 ms speech block is divided over eight GSM bursts. This ensures that if bursts are lost due to interference over the air interface the speech can still be reproduced.
Common control channel encoding

20 ms of information over the air will carry four bursts of control information, for example BCCH. This enables the bursts to be inserted into one TDMA multiframe.
Data channel encoding

The data information is spread over 22 bursts. This is because every bit of data information is very important. Therefore, when the data is reconstructed at the receiver, if a burst is lost, only a very small proportion of the 20 ms block of data will be lost. The error encoding mechanisms should then enable the missing data to be reconstructed.
20 ms INFORMATION BLOCK 0.577 ms INFORMATION BURSTS
SPEECH (260 BITS)
SPEECH (8 BURSTS)
CONTROL (184 BITS)
ENCODING
INTERLEAVING
CONTROL (4 BURSTS)
DATA (240 BITS)
DATA (22 BURSTS)
Figure 3-42 The coding process
392
14th Apr 00
GSM-001-103
EFR SPEECH FRAME 244 BITS
FR SPEECH FRAME 244 BITS
BCCH, PCH, AGCH, SDCCH, FACCH, SACCH, CBCH 184 BITS
DATA TRAFFIC 9.6/4.8/2.4 k N0 BITS
RACH + SCH P0 BITS
CYCLIC CODE + REPETITION IN: 244 OUT: 260
FIRECODE + TAIL IN: 184 OUT: 228
ADD IN TAIL IN: N0 BITS OUT: N1 BITS
CYCLIC CODE + TAIL IN: P0 BITS OUT: P1 BITS
CLASS 1a CYCLIC CODE + TAIL IN: 260 OUT: 267
CONVOLUTION CODE IN: 267 BITS OUT: 456 BITS
CONVOLUTION CODE IN: 248 BITS OUT: 456 BITS
CONVOLUTION CODE + PUNCTURE IN: N1 BITS OUT: 456 BITS
CONVOLUTION CODE IN: P1 BITS OUT: 2 x P1 BITS
TCH/2.4 RE-ORDERING & PARTITIONING + STEALING FLAG IN: 456 BITS OUT: 8 SUB-BLOCKS
DIAGONAL INTERLEAVING + STEALING FLAG IN: BLOCKS OF 456 BITS OUT: 22 SUB-BLOCKS
BLOCK DIAGONAL INTERLEAVING IN: 8 BLOCKS OUT: PAIRS OF BLOCKS
BLOCK RECTANGULAR INTERLEAVING IN: 8 SUB-BLOCKS OUT: PAIRS OF SUB-BLOCKS
8 x TCH FR (BURSTS) 8 x TCH EFR (BURSTS) 8 x FACCH/TCH (BURSTS) 8 x TCH 2-4 kBIT/S (BURSTS)
4 x BCCH, PCH, AGCH 4 x SDCCH, SACCH 4 x CBCH (BURSTS)
1 x RACH 1 x SCH (BURST)
19 x TCH 9.6 kBIT/S (BURST)
Figure 3-43 Error protection and detection
14th Apr 00
393
GSM-001-103
Speech channel encoding

The BTS receives transcoded speech over the Abis interface from the BSC. At this point the speech is organized into its individual logical channels by the BTS. These logical channels of information are then channel coded before being transmitted over the air interface. The transcoded speech information is received in frames, each containing 260 bits. The speech bits are grouped into three classes of sensitivity to errors, depending on their importance to the intelligibility of speech.
Class 1a
Three parity bits are derived from the 50 Class 1a bits. Transmission errors within these bits are catastrophic to speech intelligibility, therefore, the speech decoder is able to detect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the whole block is usually ignored.
Class 1b
The 132 Class 1b bits are not parity checked, but are fed together with the Class 1a and parity bits to a convolutional encoder. Four tail bits are added which set the registers in the receiver to a known state for decoding purposes.
394
14th Apr 00
GSM-001-103
Class 2
The 78 least sensitive bits are not protected at all. The resulting 456 bit block is then interleaved before being sent over the air interface. NOTE Over the Abis link, when using full rate speech vocoding, 260 bits are transmitted in 20 ms equalling a transmission rate of 13 kbit/s. If enhanced full rate is used then 244 bits are transmitted over the Abis link for each 20 ms sample. The EFR frame is treated to some preliminary coding to build it up to 260 bits before being applied to the same channel coding as full rate. The encoded speech now occupies 456 bits, but is still transmitted in 20 ms thus raising the transmission rate to 22.8 kbit/s. 260 BITS
CLASS 1a 50 BITS CLASS 1b 132 BITS CLASS 2 78 BITS TAIL BITS 50 3 132 4
PARITY CHECK
CONVOLUTIONAL CODE
378
78
456 BITS Figure 3-44 Speech channel encoding
14th Apr 00
395
GSM-001-103
Channel coding for enhanced full rate

The transcoding for enhanced full rate produces 20 ms speech frames of 244 bits for channel coding on the air interface. After passing through a preliminary stage which adds 16 bits to make the frame up to 260 bits the EFR speech frame is treated to the same channel coding as full rate. The additional 16 bits correspond to an 8 bit CRC which is generated from the 50 Class 1a bits plus the 15 most important Class 1b bits and 8 repetition bits corresponding to 4 selected bits in the original EFR frame of 244 bits.
Preliminary channel coding for EFR

EFR Speech Frame S S S S 50 Class 1a + 124 Class 1b + 70 Class 2 = 244 bits
Preliminary Coding 8 bit CRC generated from 50 Class 1a + 15 Class 1b added to Class 1b bits 8 repetition bits added to Class 2 bits
Output from preliminary coding 50 Class 1a + 132 Class 1b + 78 Class 2 = 260 bits
EFR frame of 260 bits passed on for similar channel coding as Full Rate. 244 BITS
CLASS 1a 50 BITS CLASS 1b 124 BITS CLASS 2 70 BITS
8 BIT CRC ADDED TO CLASS 1b BITS
8 REPETITION BITS ADDED TO CLASS 2 BITS
CLASS 1a 50 BITS
CLASS 1b 132 BITS
CLASS 2 78 BITS
260 BITS Figure 3-45 Preliminary coding for enhanced full rate speech
396
14th Apr 00
GSM-001-103
Control channel encoding

Figure 3-46 shows the principle of the error protection for the control channels. This scheme is used for all the logical signalling channels, the synchronization channel (SCH) and the random access burst (RACH). The diagram applies to SCH and RACH, but with different numbers. When control information is received by the BTS it is received as a block of 184 bits. These bits are first protected with a cyclic block code of a class known as a Fire Code. This is particularly suitable for the detection and correction of burst errors, as it uses 40 parity bits. Before the convolutional encoding, four tail bits are added which set the registers in the receiver to a known state for decoding purposes. The output from the encoding process for each block of 184 bits of signalling data is 456 bits, exactly the same as for speech. The resulting 456 bit block is then interleaved before being sent over the air interface. 184 BITS
184
PARITY BITS
FIRE CODE
TAIL BITS
184
40
CONVOLUTIONAL CODE
456
456 BITS
Figure 3-46 Control channel coding
14th Apr 00
397
GSM-001-103
Data channel encoding

Figure 3-47 shows the principle of the error protection for the 9.6 kbit/s data channel. The other data channels at rates of 4.8 kbit/s and 2.4 kbit/s are encoded slightly differently, but the principle is the same. Data channels are encoded using a convolutional code only. With the 9.6 kbit/s data some coded bits need to be removed (punctuated) before interleaving, so that like the speech and control channels they contain 456 bits every 20 ms. The data traffic channels require a higher net rate (net rate means the bit rate before coding bits have been added) than their actual transmission rate. For example, the 9.6 kbit/s service will require 12 kbit/s, because status signals (such as the RS-232 DTR (data terminal ready)) have to be transmitted as well. The output from the encoding process for each block of 240 bits of data traffic is 456 bits, exactly the same as for speech and control. The resulting 456 bit block is then interleaved before being sent over the air interface. NOTE Over the PCM link 240 bits were transmitted in 20 ms equalling a transmission rate of 12 kbit/s. 9.6 kbit/s raw data and 2.4 kbit/s signalling information. The encoded control information now occupies 456 bits but is still transmitted in 20 ms thus raising the transmission rate to 22.8 kbit/s. DATA CHANNEL 9.6 kbit/s 240 BITS
240 TAIL BITS
240
CONVOLUTIONAL CODE
488
PUNCTUATE
456
456 BITS Figure 3-47 Data channel encoding

398
14th Apr 00
GSM-001-103
Mapping logical channels onto the TDMA frame structure

Interleaving
Having encoded, or error protected the logical channel, the next step is to build its bitstream into bursts that can then be transmitted within the TDMA frame structure. It is at this stage that the process of interleaving is carried out. Interleaving spreads the content of one traffic block across several TDMA timeslots. The following interleaving depths are used: S S S Speech 8 blocks Control 4 blocks Data 22 blocks
This process is an important one, for it safeguards the data in the harsh air interface radio environment. Because of interference, noise, or physical interruption of the radio path, bursts may be destroyed or corrupted as they travel between MS and BTS, a figure of 1020% is quite normal. The purpose of interleaving is to ensure that only some of the data from each traffic block is contained within each burst. By this means, when a burst is not correctly received, the loss does not affect overall transmission quality because the error correction techniques are able to interpolate for the missing data. If the system worked by simply having one traffic block per burst, then it would be unable to do this and transmission quality would suffer. It is interleaving that is largely responsible for the robustness of the GSM air interface, enabling it to withstand significant noise and interference and maintain the quality of service presented to the subscriber. Table 3-19 Interleaving TRAU Frame Type Speech Control Data NOTE TRAU = Transcoder Rate Adaption Unit Number of GSM Bursts spread over 8 4 22
14th Apr 00
399
GSM-001-103
Diagonal interleaving speech

Figure 3-48 illustrates, in a simplified form, the principle of the interleaving process applied to a full-rate speech channel. The diagram shows a sequence of speech blocks after the encoding process previously described, all from the same subscriber conversation. Each block contains 456 bits, these blocks are then divided into eight blocks each containing 57 bits. Each block will only contain bits from even bit positions or bits from odd bit positions. The GSM burst will now be produced using these blocks of speech bits. The first four blocks will be placed in the even bit positions of the first four bursts. The last four blocks will be placed in the odd bit positions of the next four bursts. As each burst contains 114 traffic carrying bits, it is in fact shared by two speech blocks. Each block will share four bursts with the block preceding it, and four with the block that succeeds it, as shown. In the diagram block 5 shares the first four bursts with block 4 and the second four bursts with block 6.
20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS
BITS 4, 12, 20, 28 ..... 452
BITS 0, 8, 16, 24 ..... 448
BITS 0, 8, 16, 24 ..... 448
MAPPED TO ODD BITS OF BURST
MAPPED TO EVEN BITS OF BURST
MAPPED TO EVEN BITS OF BURST
BITS 4, 12, 20, 28 ..... 452 MAPPED TO ODD BITS OF BURST
012345678 .... 113
3100

012345678 .... 113
Figure 3-48 Diagonal interleafing speech
14th Apr 00
GSM-001-103
Transmission speech
Each burst will be transmitted in the designated timeslot of eight consecutive TDMA frames, providing the interleaving depth of eight. Table 3-20 shows how the 456 bits resulting from a 20 ms speech sample are distributed over eight normal bursts. It is important to remember that each timeslot on this carrier may be occupied by a different channel combination: traffic, broadcast, dedicated or combined. NOTE Note that FACCH, because it steals speech bursts from a subscriber channel, experiences the same kind of interleaving as the speech data that it replaces (interleaving depth = 8). The FACCH will steal a 456 bit block and be interleaved with the speech. Each burst containing a FACCH block of information will have the appropriate stealing flag set. Table 3-20 Distribution of 456 bits from one 20 ms speech sample Distribution 0 8 16 17 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 ..........................448 41 ..........................449 42 ..........................450 43 ..........................451 44 ..........................452 45 ..........................453 46 ..........................454 47 ..........................455 Burst even bits of burst N even bits of burst N + 1 even bits of burst N + 2 even bits of burst N + 3 odd bits of burst N + 4 odd bits of burst N + 5 odd bits of burst N + 6 odd bits of burst N + 7
1 9
2 10 18 3 11 19 4 12 20 5 13 21 6 14 22 7 15 23
14th Apr 00
3101
GSM-001-103
Rectangular interleaving control

Figure 3-49 illustrates, in a simplified form, the principle of rectangular interleaving. This is applied to most control channels. The diagram shows a sequence of control blocks after the encoding process previously described. Each block contains 456 bits, these blocks are then divided into four blocks each containing 114 bits. Each block will only contain bits for even or odd bit positions. The GSM burst will be produced using these blocks of control.
Transmission control
Each burst will be transmitted in the designated timeslot of four consecutive TDMA frames, providing the interleaving depth of four. The control information is not diagonally interleaved as are speech and data. This is because only a limited amount of control information is sent every multiframe. If the control information was diagonally interleaved, the receiver would not be capable of decoding a control message until at least two multiframes were received. This would be too long a delay.
CONTROL BLOCKS
456 BITS
114 BITS EVEN
114 BITS
114 BITS EVEN
114 BITS ODD
ODD
BURSTS
FRAME 1
FRAME 2
TDMA FRAMES Figure 3-49 Rectangular interleaving control
3102

0 1 2 3 4 5 6 7
FRAME 3
14th Apr 00
GSM-001-103
Diagonal interleaving data

Figure 3-50 illustrates, in a simplified form, diagonal interleaving applied to a 9.6 kbit/s data channel. The diagram shows a sequence of data blocks after the encoding process previously described, all from the same subscriber. Each block contains 456 bits, these blocks are divided into four blocks each containing 114 bits. These blocks are then interleaved together. The first 6 bits from the first block are placed in the first burst. The first 6 bits from the second block will be placed in the second burst and so on. Each 114 bit block is spread across 19 bursts and the total 456 block will be spread across 22 bursts. Data channels are said to have an interleaving depth of 22, although this is sometimes also referred to as an interleaving depth of 19.
14th Apr 00
3103
GSM-001-103
Transmission data
The data bits are spread over a large number of bursts, to ensure that the data is protected. Therefore, if a burst is lost, only a very small amount of data from one data block will actually be lost. Due to the error protection mechanisms used, the lost data has a higher chance of being reproduced at the receiver. This wide interleaving depth, although providing a high resilience to error, does introduce a time delay in the transmission of the data. If data transmission is slightly delayed, it will not effect the reception quality, whereas with speech, if a delay were introduced this could be detected by the subscriber. This is why speech uses a shorter interleaving depth.
DATA BLOCKS
456 BITS
114 BITS
114 BITS
114 BITS
114 BITS
114
114
114
114
FIRST 6 BITS
FIRST 6 BITS
FIRST 6 BITS
FIRST 6 BITS
LAST 6 BITS
LAST 6 BITS
LAST 6 BITS
LAST 6 BITS
3104

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Figure 3-50 Diagonal interleaving data
14th Apr 00
GSM-001-103
Voice Activity Detection VAD

VAD is a mechanism whereby the source transmitter equipment identifies the presence or absence of speech. VAD implementation is effected in speech mode by encoding the speech pattern silences at a rate of 500 bit/s rather than the full 13 kbit/s. This results in a data transmission rate for background noise, known as comfort noise, which is regenerated in the receiver. Without comfort noise the total silence between the speech would be considered to be disturbing by the listener.
Discontinuous Transmission DTX

DTX increases the efficiency of the system through a decrease in the possible radio transmission interference level. It does this by ensuring that the MS does not transmit unnecessary message data. DTX can be implemented, as necessary, on a call by call basis. The effects will be most noticeable in communications between two MS. DTX in its most extreme form, when implemented at the MS can also result in considerable power saving. If the MS does not transmit during silences there is a reduction in the overall power output requirement. The implementation of DTX is very much at the discretion of the network provider and there are different specifications applied for different types of channel usage. DTX is implemented over a SACCH multiframe (480 ms). During this time, of the possible 104 frames, only the 4 SACCH frames and 8 Silence Descriptor (SID) frames are transmitted.
26 FRAME MULTIFRAME 5259
S A C C H 0
S A C C H
4 x SACCH 26 FRAME MULTIFRAMES (120 ms) 8 x SILENCE DESCRIPTOR (SID)
Figure 3-51 SACCH Multiframe (480 ms)
14th Apr 00

SID
S A C C H
S A C C H 103
3105
GSM-001-103
Receive diversity
In its simplest case, multipath fading arises from destructive interference between two transmission paths. The deepest instantaneous fade occurring at the frequency for which the effective path length difference is an odd multiple of half wavelengths. If two receive antennas are mounted a defined distance apart, then it follows that the probability of them simultaneously experiencing maximum fade depth at a given frequency is very much less than for the single antenna situation. There are three ways of utilizing this concept: S S S The receiver can be switched between the two RF receive paths provided two antennas. The RF signals from two receive paths can be phase aligned and summed. The phasing can be made so as to minimize the distortion arising from the multipath transmission.
Each of the methods has advantages and disadvantages. In the case of the switched configuration, its simply chooses the better of the two RF signals which is switched through to the receiver circuitry. Phase alignment has the advantage of being a continuously optimized arrangement in terms of signal level, but phase alignment diversity does not minimize distortion. The Motorola DRCU/TCU uses this diversity concept. The distortion minimizing approach, whilst being an attractive concept, has not yet been implemented in a form that works over the full fading range capabilities of the receivers and therefore has to switch back to phase alignment at low signal levels. This means a rather complex control system is required. It must be emphasized that diversity will not usually have any significant effect on the mean depression component of fading, but the use of phase alignment diversity can help increase the mean signal level received. NOTE Remember in microcellular applications that the M-Cellcity and M-Cellarena does not support spatial diversity.
MOBILE
PATH LENGTH IN WAVE LENGTHS
ANTENNAS (approx 10 wave lengths) SPACE BETWEEN
METHODS OF UTILIZATION: a. b. c. SWITCHED. PHASE ALIGNED AND SUMMED. PHASE ALIGNED WITH MINIMUM DISTORTION.
BTS
Figure 3-52 Receive diversity

3106
14th Apr 00
GSM-001-103
Equalization
As mentioned in multipath fading, in most urban areas the only signals received are multipath. If nothing was done to try and counter the effects of (Inter Symbol Interference) ISI caused by the time dispersed signals, the Bit Error Rate (BER) of the demodulated signal would be far too high, giving a very poor quality signal, unacceptable to the subscriber. To counter this a circuit called an equalizer is built into the receiver. The equalizer uses a known bit pattern inserted into every normal burst transmitted, called the training sequence code. This allows the equaliser to assess and modify the effects of the multipath component, resulting in a far cleaner less distorted signal. Without this equalizer the quality of the circuit would be unacceptable for the majority of time.
Training sequence code

The training sequence code, Figure 3-53, is used so that the demodulator can estimate the most probable sequence of modulated data. As the training sequence is a known pattern, this enables the receiver to estimate the distortion ISI on the signal due to propagation effects, especially multipath reception. The receiver must be able to cope with two multipaths of equal power received at an interval of up to 16 microseconds. If the two multipaths are 16 micro seconds delayed then this would be approximately equivalent to 5bit periods. There are 32 combinations possible when two 5bit binary signals are combined. As the transmitted training sequence is known at the receiver, it is possible to compare the actual multipath signal received with all 32 possible combinations reproduced in the receiver. From this comparison the most likely combination can be chosen and the filters set to remove the multipath element from the received signal. The multipath element can be of benefit, once it has been identified, as it can then be recombined with the wanted signal in a constructive way to give a greater received signal strength. Once the filters have been set, they can be used to filter the random speech data as it is assumed they will have suffered from the same multipath interference as the training sequence code. The multipath delay is calculated on a burst by burst basis, as it is constantly changing.
Signal from shortest path
Signal from delayed path
Figure 3-53 Training sequence code
14th Apr 00

3 bits
3107
Subscriber environment
GSM-001-103
Subscriber hardware
System quality, (for example; voice quality) system access and grade of service, as perceived by the customer, are the most significant factors in the success of a cellular network. The everyday subscriber neither knows or really cares about the high level of technology incorporated into a cellular network. However, they do care about the quality of their calls. What the network designer must remember is that it is the subscriber who chooses the type of equipment they wish to use on the network. It is up to the network provider to satisfy the subscriber whatever they choose. The output power of the mobile subscriber is limited in a GSM system to a maximum of 8 W for a mobile and a minimum of 0.8 W for a hand portable. For a DCS1800 system, the mobile subscriber is restricted to a maximum of 1 W and a minimum of 250 mW hand portable.
Environment
Not only does the network designer have to plan for the subscribers choice of phone, the designer has to plan for the subscribers choice as to where they wish to use that phone. Initially when only the mobile unit was available, system coverage and hence subscriber use was limited to on street, high density urban or low capacity rural coverage areas. During the early stages of cellular system implementation the major concern was trying to provide system coverage inside tunnels. However, with the advances in technology the hand portable subscriber unit is now firmly established. With this introduction came new problems for the network designer. The portable subscriber unit provides the user far more freedom of use but the subscriber still expected exactly the same service. The subscriber now wants quality service from the system at any location. This location can be on a street, or any floor of a building whether it be the basement or the penthouse and even in lifts, refer to Figure 3-54. Thus greater freedom of use for the subscriber gives the network designer even greater problems when designing and implementing a cellular system.
URBAN/CITY ENVIRONMENTS
RURAL AREAS
BUILDINGS
LIFTS
Figure 3-54 The subscriber environment

3108

TUNNELS
14th Apr 00
GSM-001-103
Distribution
Not only do network designers have to identify the types of subscriber that use the cellular network now and in the future, but at what location these subscribers are attempting to use their phones. Dense urban environments require an entirely different design approach, due to considerations mentioned earlier in this chapter, than the approach being used to design coverage for a sparsely populated rural environment. Road and rail networks have subscribers moving at high speed, so this must be accounted for when planning the interaction between network entities whilst the subscriber is using the network. Even in urban areas, the network designer must be aware that traffic is not necessarily evenly distributed. An urban area may contain sub-areas of uneven distribution such as a business or industrial district, and may have to plan for a seasonal increase of traffic due to, say, a convention centre. It is vitally important that the traffic distribution is known and understood prior to network design, to ensure that a successful quality network is implemented.
HIGH SPEED MOBILES (RAILWAYS)
RURAL
URBAN
BUSINESS AREAS 40% ROAD/RAIL NETWORK EXHIBITIONS INDUSTRIAL 20% RESIDENTIAL 30% 10%
SUBSCRIBERS DISTRIBUTION CHANGES ON A HOURLY BASIS
Figure 3-55 Subscriber distribution
14th Apr 00
3109
GSM-001-103
Most demanding
The network designer must ensure that the network is designed to ensure a quality service for the most demanding subscriber. This is the hand portable subscriber. The hand portable now represents the vast majority of all new subscriber units introduced into cellular networks. So clearly the network operators, and hence the network designers, must recognise this. Before commencing network design based around hand portable coverage, the network designer must first understand the limitations of the hand portable unit and secondly, what the hand portable actually requires from the network. The hand portable phone is a small lightweight unit which is easy to carry and has the ability to be used from any location. The ability of the unit to be used at any location means that the network must be designed with the provision of good in-building coverage as an essential element. To further complicate the network designers job, these hand portable units have a low output power: S S 0.8 W to 8 W for GSM900. 0.25 W to 1 W for DCS1800.
So the distance at which these units can be used from a cell is constrained by RF propagation limitations. For practical purposes, the actual transmit power of the hand portable should be kept as low as possible during operation. This helps not only from an interference point of view, but this also helps to extend the available talk time of the subscriber unit, which is limited by battery life.
3110
14th Apr 00
GSM-001-103
Future planning
Normal practice in network planning is to choose one point of a well know re-use model as a starting point. Even at this early stage the model must be improved because any true traffic density does not follow the homogeneous pattern assumed in any theoretical models. Smallsized heavy traffic concentrations are characteristic of the real traffic distributions. Another well known traffic characteristic feature is the fast descent in the density of traffic when leaving city areas. It is uneconomical to build the whole network using a standard cell size, it becomes necessary to use cells of varying sizes. Connecting areas with different cell sizes brings about new problems. In principle it is possible to use cells of different size side by side, but without careful consideration this may lead to a wasteful frequency plan. This is due to the fact that the re-use distance of larger cells is greater than that of smaller cells. The situation is often that the borders are so close to the high density areas that the longer re-use distances mean decreased capacity. Another solution, offering better frequency efficiency, is to enlarge the cell size gradually from small cells into larger cells. In most cases the traffic concentrations are so close to each other that the expansion cannot be completed before it is time to start approaching the next concentration, by gradually decreasing the cell size. This is why the practical network is not a regular cluster composition, but a group of directional cells of varying size. Besides this need for cells of different size, the unevenness of the traffic distribution also cause problems in frequency planning. Theoretical frequency division methods applicable to homogenous clusters cannot be used. It is quite rare that two or more neighbouring cells need the same amount of channels. It must always be kept in mind that the values calculated for future traffic distribution are only crude estimates and that the real traffic distribution always deviates from these estimates. In consequence, the network plan should be flexible enough to allow for rearrangement of the network to meet the real traffic needs.
Conclusion
In conclusion there are no general rules for radio network planning. It is a work of experimenting and reiterating. By comparing different alternatives, the network designers should find a plan that both fulfils the given requirements and keeps within practical limitations. When making network plans, the designers should always remember that every location in a network has its own conditions, and all local problems must be tackled and solved on a individual basis.
14th Apr 00
3111
The microcellular solution
GSM-001-103

Layered Architecture
The basic term layered architecture is used in the microcellular context to explain how macrocells overlay microcells. It is worth noting that when talking of the traffic capacity of a microcell it is additional capacity to that of the macrocell in the areas of microcellular coverage. The traditional cell architecture design, Figure 3-56, ensures that, as far as possible, the cell gives almost total coverage for all the MSs within its area.
TOP VIEW
SIDE VIEW
3112

MACROCELL
MICROCELL A MICROCELL B
MACROCELL
MICROCELL A
MICROCELL B
Figure 3-56 Layered architecture
14th Apr 00
GSM-001-103
Combined cell architecture

A combined cell architecture system, Figure 3-57, is a multi-layer system of macrocells and microcells. The simplest implementation contains two layers. The bulk of the capacity in a combined cell architecture is provided by the microcells. Combined cell systems can be implemented into other vendors networks. Macrocells: Implemented specifically to cater for the fast-moving MSs and to provide a fallback service in the case of coverage holes and pockets of interference in the microcell layer. Macrocells form an umbrella over the smaller microcells. Microcells: Microcells handle the traffic from slow-moving MSs. The microcells can give contiguous coverage over the required areas of heavy subscriber traffic. Picocells: Low cost installation by using in-building fibre optics or telephone wiring with a HDSL modem, easily expanded to meet capacity requirements. Efficient use of the frequency spectrum due to low power radios causing low interference to external networks. Higher quality speech compared with external illumination of the building due to improved uplink quality.
UNDERLAYED MICROCELL (COULD BE A DIFFERENT VENDOR)
CONTIGUOUS COVERAGE OVER AREAS OF HIGH SLOW MOVING TRAFFIC DENSITY OVERLAYED MACROCELLS
Figure 3-57 Combined cell architecture
14th Apr 00
3113
GSM-001-103
Combined cell architecture structure

A combined cell architecture employs cells of different sizes overlaid to provide contiguous coverage. This structure is shown in Figure 3-58. Some points to note: S S S S Macrocell and microcell networks may be operated as individual systems. The macrocell network is more dominant as it handles the greater amount of traffic. Microcells can be underlayed into existing networks. Picocells can be introduced as a third layer or as part of the second layer.
LINK TO IMPLEMENT MICROCELLS AS A SEPARATE SYSTEM ALTERNATIVE SYSTEM (MICROCELLS CONTROLLED BY THE SAME BSC AS MACROCELLS)
MSC BSC A
SYSTEM 2 MICROCELL BSC B SYSTEM 1 MACROCELL BTS 1 BTS 2 BTS 5
BTS 3
BTS 4 MICROCELL COVERAGE
PICOCELL
MACROCELL COVERAGE
SYSTEM 1= OVERLAY SYSTEM SYSTEM 2= UNDERLAY SYSTEM
Figure 3-58 Combined cell architecture structure
3114
14th Apr 00
GSM-001-103
Expansion solution
As the GSM network evolves and matures its traffic loading will increase as the number of subscribers grow. Eventually a network will reach a point of traffic saturation. The use of microcells can provide high traffic capacity in localised areas. The expansion of a BTS site past its original designed capacity can be a costly exercise and the frequency re-use implications need to be planned carefully (co-channel and adjacent channel interference). The use of microcells can alleviate the increase in congestion, the microcells could be stand-alone cells to cover traffic hotpots or a contiguous cover of cells in a combined architecture. The increased coverage will give greater customer satisfaction.
14th Apr 00
3115
GSM-001-103
3116
14th Apr 00
Chapter 4
BTS planning steps and rules
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 4 BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro and Horizoncompact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment (CTU/TCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTU/TCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Micro base control unit (mBCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . mBCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network interface unit (NIU) and site connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main control unit, with dual FMUX (MCUF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCUF planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main control unit (MCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet interconnection (FOX/FMUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FOX/FMUX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 42 42 43 44 44 44 44 45 45 46 46 46 46 48 48 48 49 410 410 410 411 411 411 411 412 412 412 412 413 413 413 414 415 415 415 415 416 416 416 416 417 417 417 418
14th Apr 00
iii
GSM-001-103
Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network expansion using Macro/Micro/Picocell BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mixed site utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interface modules (HIM-75, HIM-120) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIM-75/HIM-120 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
419 419 419 419 420 420 420 420 421 421 421 422 422 422 422
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides the planning steps and rules for the BTS, including Macrocell, Microcell and Picocell. The planning steps and rules for the BSC are in Chapter 5, and remote transcoder (RXCDR) are in Chapter 6 of this manual. This chapter contains: S S BTS planning overview: Macrocell and Microcell planning overview: S Planning rules for Macrocell cabinets. Planning rules for Microcell enclosures. Planning rules for receive configurations. Planning rules for transmit configurations. Planning rules for antenna configurations. Planning rules for the carrier equipment. Planning rules for the micro base control unit. Planning rules for the network interface unit and E1/T1 link interfaces. Planning rules for the main control unit, with dual FMUX (MCUF). Planning rules for the main control unit (MCU). Planning rules for cabinet interconnection. Planning rules for power requirements. Planning rules for network expansion using Macrocell and Microcell BTS.
Picocell planning overview: Planning rules for PCC cabinets. Line interface modules (HIM-75, HIM-120)
14th Apr 00
41
BTS planning overview
GSM-001-103

Introduction
To plan the equipage of a BTS site certain information must be known. The major items include: S S S S The number of cells controlled by the site. The number of carriers required. The number of standby carriers per cell. The output power per cell. The required output power must be known to ensure that the selected combining method and antenna configuration provides sufficient output power. Alternatives include changing combiner types or using more than one transmitting antenna. Duplexers may be used to reduce the amount of cabling and the number of antennas. S S S The antenna configuration for each cell. The cabinet/enclosure types to be used. Future growth potential. It is useful to know about potential future growth of the site in order to make intelligent trade offs between fewer cabinet/enclosures initially and ease of growth later. S Whether or not there are equipment shelters at the site. Macro/Micro/Picocell6 outdoor equipments should be included in the BTS planning for locations where there are no equipment shelters. Macro/Micro/Picocell2 should be included where rooftop mounting or distributed RF coverage is required or where space and access are restricted. To plan the equipage of a PCC cabinet (M-Cellaccess) certain information must be known. The major items include: S S S S S S S S The traffic load to be handled. The number of PCU enclosures to be controlled. The physical interconnection of the PCU enclosures to the PCC cabinet. The use of optical or HDSL links. The use or otherwise of the collocated BSC option. The use or otherwise of the GDP/XCDR option. The use of E1 or T1 links. The use of balanced or unbalanced E1.
42
14th Apr 00
GSM-001-103
Outline of planning steps

Macrocell and Microcell BTS sites
The information required for planning an Macro/Microcell BTS site is outlined in the following list: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Determine if the site is indoor or outdoor. Number of Macrocell cabinets required, refer to the section Macrocell cabinets in this chapter. Number of Microcell enclosures required, refer to the section Microcell enclosures in this chapter. The receiver configuration, refer to the section Receiver configurations in this chapter. The transmit configuration, refer to the section Transmit configurations in this chapter. The antenna configuration, refer to the section Antenna configurations in this chapter. The amount of carrier equipment required, refer to the section Carrier equipment in this chapter. The number of micro base control units required, refer to the section Micro base control units in this chapter. The number of network interface units required, refer to the section Network interface unit and site interconnection in this chapter. The number of E1/T1 links required, refer to the section Network interface unit and site interconnection in this chapter. The number of main control units required, refer to the section Main control unit in this chapter. The number of FOX and FMUX boards required, refer to the section Cabinet interconnection in this chapter. The power supply requirements, refer to the section Power requirements in this chapter.
Picocell site
The information required for planning a Picocell (Macro/Micro/Picocellaccess) site is outlined in this chapter.
14th Apr 00
43
Macrocell cabinets
GSM-001-103
Macrocell cabinets
Horizonmicro
An Horizonmicro cabinet can support six carriers (CTUs). Expansion beyond six carriers requires additional cabinets. An Horizonmicro HMS offers the following options: S S Fans that circulate ambient air through the cabinet, for both indoor and outdoor units. An outdoor unit for ambient temperatures up to 50 _C, for outdoor cabinets only.
M-Cell6
The M Cell6 cabinet can support six carriers (TCUs). Expansion beyond six carriers requires additional cabinets. Outdoor cell sites are provided with an ancillary cabinet and a side cabinet. The M-Cell6 HMS offers the following options: S S S Fans that circulate ambient air through the cabinet, for both indoor and outdoor units. A heat exchanger for ambient temperatures up to 45 _C, for outdoor cabinets only. An air conditioning unit for ambient temperatures up to 55 _C, for outdoor cabinets only.
M-Cell2
An M-Cell2 cabinet can support two carriers (TCUs). Expansion beyond two carriers requires additional cabinets. The M-Cell2 outdoor cabinet accommodates all the elements in an indoor cabinet, in addition, limited accommodation for LTUs and battery backup is provided. Cooling is provided by a fan within the cabinet. Unlike M-Cell6 outdoor cabinets where the antenna terminations are in a side cabinet, M-Cell2 terminations are on the main cabinet. The M-Cell2 HMS offers the following options: S S S Fans that circulate ambient air through the cabinet, for both indoor and outdoor units. A heat exchanger for ambient temperatures up to 45 _C, for outdoor cabinets only. An air conditioning unit for ambient temperatures up to 55 _C, for outdoor cabinets only.
44
14th Apr 00
GSM-001-103
Microcell enclosures
Microcell enclosures
Horizonmicro and Horizoncompact
The Horizonmicro is an integrated cell sites with a common design for indoor and outdoor operation. The single unit is offered as a two-carrier cell. The Horizoncompact is an integrated cell sites with a common design for indoor and outdoor operation and consists of: S S One unit, similar to M-Cellarena, is a two-carrier cell with combining. The other unit is an RF booster, with duplexing, delivering 10 W at each attenna.
Horizonmicro and Horizoncompact are specified for wall or pole mounting and the following factors should be considered when planning the mounting for an Horizonmicro and Horizoncompact are: S S They may be fixed to walls of concrete, brickwork, stonework, dense aggregate blockwork, reconstituted stone with or without rendering, and to a suitable pole. The wall fixings should be: Fischer Nylon Wall Plugs Type S with hex headed coach screws, stainless A4 or Fischer Sleeve Anchor Type FSA or equivalent fixings. The fixings should not penetrate more than 70 mm nor less than 50 mm. The uppermost wall fixings should have 600 mm of solid construction above them.
S S
14th Apr 00
45
Receive configurations
GSM-001-103
Introduction
The receiver equipment provides the termination and distribution of the received signals from the Rx antennas. Receiver equipment is required for each Rx signal in every cabinet or enclosure in which it is used. Each Rx antenna must terminate on a single cabinet or enclosure. If the signal needs to go to multiple cabinets it will be distributed from the first cabinet. NOTE Horizonmicro is two carrier only and are combined to a single antenna. Horizoncompact is two carrier only, with two antennas.
Planning considerations
The factors affecting planning for GSM900 and DCS1800 M-Cell BTSs are provided in this section.
GSM900
The following factors should be considered when planning the GSM900 receive equipment: S S S S Horizonmicro BTSs require one SURF for each cabinet. Receive antennas can be extended across Horizonmicro cabinets by using the SURF expansion ports to feed a SURF in another cabinet. M-Cell2 and M-Cell6 BTSs require one DLNB for each sector. Receive antennas can be extended across M-Cell6 cabinets by using the IADU expansion ports to feed an IADU in another cabinet.
GSM1800
The following factors should be considered when planning the DCS1800 receive equipment: S S S M-Cell2 and M-Cell6 BTSs require one LNA for each sector. Receive antennas can be extended across M-Cell6 cabinets by using the LNA expansion ports to feed an LNA in another cabinet. Horizon BTS.
Receiver planning actions

The following planning actions are required: 1. 2. 3.
46
Determine the number of cells. Determine number of cells which have CTU/TCUs in more than one cabinet. Determine the number of Rx antennas per cell supported in each cabinet. System Information: BSS Equipment Planning 68P02900W21-G
14th Apr 00
GSM-001-103
4.
Determine the type and quantity of receive equipment required.
14th Apr 00
47
Transmit configurations
GSM-001-103
Introduction
The transmit equipment provides bandpass filtering and signal combining for the BTS cabinets. A TxBPF is required for each antenna. NOTE Horizonmicro is two carrier only and are combined to a single antenna. Horizoncompact is two carrier only, with two antennas.
The factors affecting planning for GSM900 and DCS1800 M-Cell BTSs are provided in this section.
GSM900
The transmit configuration listed in Table 4-1 are available for GSM900 equipment. Table 4-1 Transmit configurations GSM900 Number of Carriers 1 2 Cabinet Transmit Configurations Wide Band Combining 1 CBF 1 CBF Cabinet Transmit Configurations Cavity Combining Not available Not available Notes M-Cell2 and M-Cell6 M-Cell2 and M-Cell6
2 CBF plus 1 medium power duplexer (an extra duplexer is required for 2 antennas) 1 CCB output or one 3 input CBF 2 CBF plus 1 medium power duplexer (an extra duplexer is required for 2 antennas) 1 CCB output + or 1 CCB extension one 3 input CBF and one Hybrid combining block(HCOMB) One CBF and one 3 input CBF Two 3 input CBF and one non-HCOMB (load block) NOTE 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension
M-Cell6 only
M-Cell6 only
5 6
M-Cell6 only M-Cell6 only
A CCB output includes a TxBPF, a CCB, extension does not.
48
14th Apr 00
GSM-001-103
DCS1800
The transmit configuration listed in Table 4-2 are available for DCS1800 equipment. Table 4-2 Transmit configurations DCS1800 Number of Carriers 1 1 2 2 3 3 4 4 5 5 6 6 Cabinet Transmit Configurations Wide Band Combining 1 DCF or TCF 1 TxBPF 1 DCF 1 Hybrid combiner plus 1 TxBPF 2 DCF or 1 DDF 2 Hybrid combiner plus 1 TxBPF 1 DDF and HCU 2 Hybrid combiner plus 1 TxBPF 2 DDF and Air 3 Hybrid combiner plus 1 TxBPF 2 DDF and Air 4 Hybrid combiner plus 1 TxBPF NOTE A CCB output includes a TxBPF, a CCB, extension does not. Cabinet Transmit Configurations Cavity Combining Not available Not available 1 CCB output 1 CCB output 1 CCB output 1 CCB output 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension 1 CCB output + 1 CCB extension Notes Horizonmicro only M-Cell2 and M-Cell6 Horizonmicro only M-Cell2 and M-Cell6 Horizonmicro only M-Cell6 only Horizonmicro only M-Cell6 only Horizonmicro only M-Cell6 only Horizonmicro only M-Cell6 only
Transmit planning actions

Determine the transmit equipment required.
14th Apr 00
49
Antenna configurations
GSM-001-103
Antenna configurations
The following factors should be considered when planning the antenna configuration: S S S S Omni, one sector, two sector, three sector (either 120_ or 60_), or six sector (two cabinets are needed). Share existing antenna(s) or new/separate antenna(s). Diversity considerations. Antenna type: Gain. Size. Bandwidth. Appearance. Mounting.
Antenna planning actions

Determine the antenna configuration.
410
14th Apr 00
GSM-001-103
Carrier equipment (CTU/TCU)
Carrier equipment (CTU/TCU)

Introduction
The carrier equipment kit, for Horizonmicro consists of a CTU. The carrier equipment kit, for M-Cell2 and M-Cell6 consists of a TCU.
The following factors should be considered when planning carrier equipment: S S S The number of carriers should be based on traffic considerations. Plan for future growth. Allowance must be made for BCCH and SDCCH control channels. Information about how to determine the number of control channels required is in the Control channel calculations section in Chapter 3, BSS cell planning in this manual. S S Normally, one CTU/TCU is required to provide each RF carrier. Include redundancy requirements; redundancy can be achieved by installing excess capacity in the form of additional carrier equipment kits.
CTU/TCU planning actions

Determine the number of CTU/TCUs required.
14th Apr 00
411
Micro base control unit (mBCU)
GSM-001-103
Micro base control unit (mBCU)

Introduction
The mBCU is the Macro/Microcell implementation of a BTS site controller.
The following factors should be considered when planning the mBCU complement: S Horizonmicro Each Horizonmicro cabinet requires one mBCU cage. The mBCU cage can be equipped for redundancy and/or additional E1/T1 link capacity. S M-Cell6 Each M-Cell6 cabinet requires one mBCU cage. Two mBCU cages can be equipped for redundancy and/or additional E1/T1 link capacity. S M-Cell2 The first M-Cell2 cabinet requires one mBCU2 cage. Two mBCU2 cages can be equipped for redundancy and/or additional E1/T1 link capacity. Additional cabinets do not require mBCU2 cages.
mBCU planning actions

Determine the number of mBCUs required.
412
14th Apr 00
GSM-001-103
Network interface unit (NIU) and site connection

Introduction
The NIU provides the interface for the Macro/Microcell BTS to the terrestrial network. NOTE Horizonmicro and Horizoncompact are fitted with a single NIU-m only.
The following factors should be considered when planning the NIU complement: S S S S S S S The first NIU in a mBCU cage can interface two E1/T1 links. The second NIU in a mBCU cage in an M-Cell6 cabinet can interface one E1/T1 link. Each E1/T1 link provides 31(E1) or 24 (T1) usable 64 kbit/s links. A minimum of one NIU is required for each BTS site. One NIU can support two MCUFs (Horizonmacro) or two MCUs (M-Cell6). The NIU feeds the active MCUF/MCU. To calculate the number of 64 kbit/s links required, view the site as consisting of its own equipment, and that of other sites which are connected to it by the drop and insert (daisy chain) method. Two 64 kbit/s links are required for each active CTU/TCU. A 64 kbit/s link is required for every RSL (LAPD signalling channel) to the site. In the drop and insert (daisy chain) configuration, every site will require its own 64 kbit/s link for signalling.
S S S
Redundancy for the NIU module depends on the number of redundant E1/T1 links running to the site. Plan for a maximum of two NIUs per mBCU cage for Horizonmicro and M-Cell6 cabinets (three E1 or T1 links). Plan for a maximum of one NIU per mBCU2 cage for M-Cell2 cabinets (two E1 or T1 links).
14th Apr 00
413
GSM-001-103
The minimum number of NIUs and mBCU cages required for a given number of E1/T1 links to a single M-Cell cabinet is shown in Table 4-3. Table 4-3 Site connection requirements Number of E1/T1 links 1 2 3 3 4 5 6 Minimum number of NIU required 1 1 2 2 2 3 4 Number of mBCU cages required 1 1 1 2 2 2 2 Notes
Horizonmicro, M-Cell2 and M-Cell6 Horizonmicro, M-Cell2 and M-Cell6 Horizonmicro and M-Cell6 M-Cell2 and M-Cell6 M-Cell2 and M-Cell6 M-Cell6 only M-Cell6 only
E1 link interfaces
For driving a balanced 120 ohms 3 V (peak pulse) line use a BIB. For driving a single ended 75 ohms 2.37 V (peak pulse) line use a T43.
T1 link interfaces
For driving a balanced 110 ohms 3 V (peak pulse) line use a BIB.
NIU planning actions

Determine the number of NIUs required.
414
14th Apr 00
GSM-001-103
Main control unit, with dual FMUX (MCUF)
Main control unit, with dual FMUX (MCUF)

Introduction
The MCUF provides the main site control functions for a Horizonmicro BTS site.
The following factors should be considered when planning the MCUF complement: S S S Only the first cabinet requires an MCUF. An optional (PCMCIA) memory card may be installed for non-volatile code storage. For redundancy add a second MCUF in the first cabinet.
MCUF planning actions

Determine the number of MCUFs required.
14th Apr 00
415
Main control unit (MCU)
GSM-001-103
Main control unit (MCU)

Introduction
The MCU provides the main site control functions for M-Cell6 and M-Cell2 BTS sites.
The following factors should be considered when planning the MCU complement: S S S Only the first cabinet requires an MCU. An optional (PCMCIA) memory card may be installed for non-volatile code storage. For redundancy add a second mBCU cage and MCU in the first cabinet.
MCU planning actions

Determine the number of MCUs required.
416
14th Apr 00
GSM-001-103
Cabinet interconnection (FOX/FMUX)

Introduction
Horizonmicro
The FMUX multiplexes and demultiplexes electrical connections between a MCUF and up to six CTUs.
M-Cell6 and M-Cell2

The FOX provides the bidirectional electrical to optical interface between a MCU or FMUX and up to six TCUs. The FMUX multiplexes and demultiplexes electrical connections for up to six TCUs onto a single fibre optic connection operating at the rate of 16.384 Mbit/s.
Horizonmacro
The following factors should be considered when planning the FMUX complement, refer to Table 4 4: Table 4-4 FMUX complement Cabinet 1 2 3 4 S S S Master None None 1 2 1 1 1 1 1 1 Extender 1 Extender 2 Extender 3
An FMUX is not required in the Master cabinet, for two cabinet configurations. Each additional Horizonmicro cabinet requires one FMUX plus one FMUX in the Master cabinet. Redundancy requires duplication of an FMUX and associated MCUFs.
M-Cell6 and M-Cell2

The following factors should be considered when planning the FOX/FMUX complement: S S S A FOX board is required for more than two TCUs. Each additional M-Cell6 cabinet requires a minimum of one FOX and FMUX plus one FMUX in the first cabinet. Redundancy requires duplication of all FOX and FMUX boards and associated MCU and mBCU cages.
14th Apr 00
417
GSM-001-103
FOX/FMUX planning actions

Horizonmicro
Determine the number of FMUXs required.
M-Cell6 and M-Cell2

Determine the number of FOX/FMUXs required.
418
14th Apr 00
GSM-001-103
Power requirements
Power requirements
Introduction
Macrocell cabinets and Microcell enclosures can operate from a variety of power supplies.
The following factors should be considered when planning the power supply requirements: S Horizonmicro The Horizonmicro BTS cabinet can be configured to operate from either a +27 V dc or 48 V/60 V dc power source or 110 V/230 V ac, indoor and outdoor. S M-Cell6 The M-Cell6 BTS cabinet can be configured to operate from either a +27 V dc or 48 V/60 V dc power source (indoor) or 230 V/110 V ac. S M-Cell2 The M-Cell2 BTS cabinet can be configured to operate from either a +27 V dc or 230 V/110 V ac power source. S M-Cellcity and M-Cellcity+ The M-Cellcity and M-Cellcity+ BTS enclosures operates from a 88 to 265 V ac power source. S Horizonmicro and Horizoncompact The Horizonmicro and Horizoncompact enclosures operates from a 88 to 265 V ac power source.
Power planning actions

Determine the power supply required.
14th Apr 00
419
Network expansion using Macro/Micro/Picocell BTS
GSM-001-103
Network expansion using Macro/Micro/Picocell BTS

Introduction
An existing network with previous generations of Motorola equipment such as BTS4, BTS5, BTS6, TopCell, or ExCell may be expanded using Macro/Micro/Picocell. The Network topology can be any of those specified in Chapter 2 of this manual. An Macro/Micro/Picocell BTS may occupy any position in a network. Macro/Micro/Picocell BTSs may be collocated with previous generation equipment but cannot be operated as a single site with such equipment.
Expansion considerations
The following factors should be considered when expanding an existing network using Macro/Micro/Picocell BTS cabinets: S S S An Macro/Micro/Picocell BTS cannot share a cell with a BTS4, BTS5, BTS6, TopCell, or ExCell. The rules governing the number of NIUs required at the Macro/Micro/Picocell BTS are given in Table 4-3 of this chapter. The rules governing the number of MSIs required at the BSC are given in the Multiple serial interface (MSI, MSI-2)section of Chapter 5.
Mixed site utilization

To upgrade sites utilizing previous generations of Motorola equipment such as BTS5, BTS4, BTS6, TopCell, or ExCell, proceed in the following manner: 1. 2. Sites with previous generation equipment should be expanded with the appropriate modules until the cabinets are full. To further expand a previous generation site, the equipment in the previous generation cabinet must be re-configured so that it serves a complete set of sectors in the target configuration. An Macro/Micro/Picocell site should then be added to the site to serve the remaining sectors. The Macro/Micro/Picocell site should then be connected into the network by daisy chaining it to the existing site. Customers who have not purchased the daisy chaining feature should order the free of charge feature M-Cell InCell Interworking, SWVN2460, to obtain a suitable licence for upgrading.
3. 4. 5.
Example
To upgrade a BTS6 2/2/2 to a 3/3/3. Re-configure the BTS6 to a 3/3, order an M-Cell Omni 3 and install it to serve the third sector.
420
14th Apr 00
GSM-001-103
PCC cabinet
PCC cabinet
Introduction
Each PCC cabinet (M-Cellaccess) can support up to two sites (one cage = one site); and up to a maximum of six carriers (PCU enclosures) per site. If a mix of 900 MHz and 1800 MHz equipments are required, then one shelf must be used for each frequency. To assist in the planning of an M-Cellaccess site refer to Chapter 11, Picocell equipment descriptions. Collocated BSC and XCDR/GDP options can be planned for the lower BSU shelf only, refer to Chapter 5, BSC planning steps and rules and Chapter 6, RXCDR planning steps and rules.
Cabinet planning actions

The following planning actions are required: S S S Determine the number of sites required. Determine the mix of frequencies. Determine the method of PCU/PCC interconnection.
14th Apr 00
421
Line interface modules (HIM-75, HIM-120)
GSM-001-103
Line interface modules (HIM-75, HIM-120)

Introduction
The line interface modules, HDSL interface module, 75 ohm (HIM-75), and HDSL interface module, 120 ohm (HIM-120), provide impedance matching for E1, T1 and HDSL links.
The following factors should be considered when planning the line interface complement: S S S S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line use a HIM-120. To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line use a HIM-75. Each HIM-75/HIM-120 can interface four E1/T1 links to specific slots on one shelf. Up to three HIM-75s or HIM-120s per shelf can be mounted on a PCC cabinet. A maximum of four E1/T1 links can be connected to a BSU shelf. A maximum of six HDSL links can be connected to a BSU shelf. A PCC cabinet with two BSU shelves can interface eight E1/T1 and 12 HDSL links.
HIM-75/HIM-120 planning actions

The following planning actions are required: S S Determine the number to be deployed. Determine the number of HIM-75s or HIM-120s required. Minimum number of HIM75s or HIM120s = Number of PCUs 2
422
14th Apr 00
Chapter 5
BSC planning steps and rules
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 5 BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System capacity summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of introduction to BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU-to-SGSN interface planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS PCU provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS link provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS-BSC E1 links (Abis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . . LCF GPROC2 provisioning for GPRS signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 52 52 53 54 54 55 55 56 57 57 59 510 511 512 512 512 512 515 523 524 524 524 525 533 534 538 538 538 538 539 539 550 551 552 553 556 556 556 557 558 560 560
14th Apr 00
iii
GSM-001-103
Generic processor (GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions for transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
561 561 561 562 562 564 564 564 565 565 566 566 566 567 568 569 569 569 570 571 571 571 572 573 573 573 573 574 574 574 574 576 576 576 576 577 577 577 577 578 578 578 578 579 579 579 579 580 580 580 580
14th Apr 00
GSM-001-103
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
581 581 581 581 582 582 582 582 583 583
14th Apr 00
GSM-001-103
vi
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides the planning steps and rules for the BSC. The planning steps and rules for the BTS are in Chapter 4 of this manual. This chapter contains: S S S BSC planning overview. GPRS planning. Capacity calculations. S Determining the required BSS signalling link capacities. Determine the number of RSLs required. Determine the number of MTLs required. BSC GPROC functions and types. Traffic models.
BSC planning. Planning rules for BSC to BTS links (E1/T1). Planning rules for BSC to BTS links (RSL). Planning rules for BSC to MSC links (MTL). Planning rules for the digital modules. Planning rules for the digital shelf power supply.
14th Apr 00
51
BSC planning overview
GSM-001-103

Introduction
To plan the equipage of a BSC certain information must be known. The major items include: S S S S S S S S S S S S The number of BTS sites to be controlled. The number of RF carriers (RTF) at each BTS site. The number of TCHs at each site. The total number of TCHs under the BSC. The number of cells controlled from each BTS site should not exceed the maximum per BSC detailed in Table 5-1. The physical interconnection of the BTS sites to the BSC. The location of the XCDR function. The path for the OML links to the OMC. The use of E1 or T1 links. The use of balanced or unbalanced E1. The traffic load to be handled (also take future growth into consideration). The number of MSC to BSC trunks.
52
14th Apr 00
GSM-001-103

Planning a BSC involves the following steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. Plan the number of E1 or T1 links between the BSC and BTS site(s), refer to the section Determine the required BSS signalling link capacities in this chapter. Plan the number of RSL links between the BSC and BTS site(s), refer to the section Determine the RSLs required in this chapter. Plan the number of MTL links between the BSC and MSC, refer to the section Determine the number of MTLs required in this chapter. Plan the number of GPROCs required, refer to the section Generic processor (GPROC2) in this chapter. Plan the number of XCDR/GDPs required, refer to the section Transcoding in this chapter. Plan the number of MSI/MSI-2s required, refer to the section Multiple serial interface (MSI, MSI-2) in this chapter. Plan the number of KSWs and timeslots required, refer to the section Kiloport switch (KSW) in this chapter. Plan the number of BSU shelves, refer to the section BSU shelves in this chapter. Plan the number of KSWXs required, refer to the section Kiloport switch extender (KSWX) in this chapter. Plan the number of GCLKs required, refer to the section Generic clock (GCLK) in this chapter. Plan the number of CLKXs required, refer to the section Clock extender (CLKX) in this chapter. Plan the number of LANXs required, refer to the section LAN extender (LANX) in this chapter. Plan the number of PIXs required, refer to the section Parallel interface extender (PIX) in this chapter. Plan the number of BIB or T43s required, refer to the section Line interfaces (BIB, T43) in this chapter. Plan the power requirements, refer to the section Digital shelf power supply in this chapter. Plan the number of BBBXs required, refer to the section Battery backup board (BBBX) in this chapter. Verify the planning process, refer to the section Verify the number of BSU shelves and BSSC cabinets in this chapter.
14th Apr 00
53
GSM-001-103
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC, GPROC2) and the throughput capacities of its data links, determines the number of supported traffic channels (TCHs). These capacities are limited by the ability of the processors, and links to handle the signalling information associated with these TCHs. This section provides information on how to calculate processor requirements, signalling link capacities and BSC processing capacities. This section describes: S S S S S Traffic models. The required BSS signalling link capacities. BSC GPROC functions and types. The number of GPROCs required. A summary of BSC maximum capacities.
54
14th Apr 00
GSM-001-103
BSC system capacity
BSC system capacity

System capacity summary
Table 5-1 provides a summary of BSC maximum capacities. Table 5-1 Capacity Item BTS sites BTSs (cells) Active RF carriers DRIs RSLs MMSs PATHs DHPs Trunks (see note below) C7 links T1 or E1 links Maximum Busy Hour Call attempts 960 16 72 38,000 1.4.x.x 40 90 120 GSR2 40 90 120 210 80 72 80 161 960 16 72 38,000 GSR3 40 126 255 381 80 102 80 296 1680 16 96 50,400 GSR4 100 250 384 634 250 128 250 232 1920 16 102 57,600 GSR4.1 100 250 384 634 250 128 250 232 1920 16 102 57,600
NOTE If two of the E1 links between the RXCDR and BSC are reserved for redundancy, the number of effective trunks (at GSR4) become 1680; which can support 1650 Erlangs of traffic at 1% blocking. GPROC2 in GSR2 causes no change in capacity. At GSR3/GSR4, GPROC2 becomes mandatory for site controller.
14th Apr 00
55
BSC system capacity
GSM-001-103
Scaleable BSC
With the launch of the Scaleable BSC in GSR4, Motorola is moving to a position where the diverse requirements of network operators in terms of BSC size are addressed by a single platform that can be efficiently configured in small, medium or large models. For existing customers the move to a Scaleable BSC is enabled through the migration of the processing boards within the BSC to use the GPROC2 throughout. BSSs targeted at small, medium, or large networks are efficiently addressed by the Scaleable BSC where minimal incremental hardware is required to be added as the networks grow. Being able to expand capacity within a BSC is appealing from an operational viewpoint because there is less time and effort involved than compared with having to move sites from one BSC to another, or even from one OMC to another. Put into context, the BSC capacity prior to GSR3 supports in the order of 40 sites of three sectors and one carrier per sector; or alternatively, 20 sites of three sectors and two carriers per sector. At GSR3, the capacity increased to allow the operator to move to support in the order of 40 sites of three sectors and two carriers per sector. At GSR4, the capacity increased to allow the operator to move to support in the order of 64 sites of three sectors and two carriers per sector. The Scaleable BSC also offers a substantial advantage for microcellular deployment where a single BSC is able to support up to 100 microcellular BTSs, each equipped with two carriers per site. The Scaleable BSC capacity is enabled because of the increased processing performance and memory of the GPROC2. The maximum capacity is increased as shown in Table 5-1. This increased capacity is achieved through the deployment of GPROC2s for each function at the BSC, including base station processor (BSP) and link control function (LCF).
56
14th Apr 00
GSM-001-103
Determining the required BSS signalling link capacities

BSC signalling traffic model
For a GSM system the throughput of network entities, including sub-components, depends upon the assumed traffic model used in the network design or operation. Traffic models are fundamental to a number of planning actions. The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends on its ability to process information transported through signalling links connecting it to the other network elements. These elements include MSC, BTSs, and the OMC-R. Depending on its device type and BSC configuration, a GPROC may be controlling signalling links to one or more other network elements. A capacity figure can be stated for each GPROC device type in terms of a static capacity such as the number of physical signalling links supported, and a dynamic capacity such as processing throughput. In general telephony environments, processing and link throughput capacities can be stated in terms of the offered call load. To apply this for the GSM BSC, all signalling information to be processed by the BSC, is related to the offered call load (the amount of traffic offered/generated by subscribers). When calls are blocked due to all trunks or all TCHs busy, most of the signalling associated with call setup and clearing still takes place, even though few or no trunk resources are utilized. Therefore, the offered call load (which includes the blocked calls) should be used in planning the signalling resources (for example; MTLs and RSLs). In the case where the BSC has more than enough trunks to handle the offered traffic, adequate signalling resources should be planned to handle the potential carried traffic. The trunk count can be used as an approximate Erlang value for the potential carried load. As a result, the signalling links and processing requirements should be able to handle the greater of the following: S S The offered load. The potential carried load.
To determine the link and processing requirements of the BSC, the number of trunks or the offered call load in Erlangs (whichever is greater) should be used. BSC capacity planning requires a model that associates the signalling generated from all the pertinent GSM procedures: call setup and clearing, handover, location updating, and paging, to the offered call load. To establish the relationship between all the procedures, the traffic model expresses processing requirements for these procedures as ratios to the number of call attempts processed. The rate at which call attempts are processed is a function of the offered call load and the average call hold time. Figure 5-1 graphically depicts various factors that should be taken into account when planning a BSS.
14th Apr 00
57
GSM-001-103
MSC TRANSCODER
A INTERFACE (TERRESTRIAL LINKS) C7 SIGNALLING LINKS X.25 CONTROL LINK* REQUIRED TRUNKS
WITH SUBMULTIPLEXING TRANSCODING AT MSC 1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK 1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK* 1 x 64 kbit/s CIRCUIT/ XBL 1 x 64 kbit/s CIRCUIT/4 TRUNKS WITHOUT SUBMULTIPLEXING TRANSCODING AT BSC 1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK 1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK* 1 x 64 kbit/s CIRCUIT/TRUNK
THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED FROM THE # OF TRUNKS REQUIRED TO CARRY THE SUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS, TYPICALLY USING 1% BLOCKING) FROM ALL BTSs PLUS THE # OF C7 SIGNALLING LINKS PLUS (IF APPLICABLE*) THE # OF X.25 LINKS (USUALLY ONE PER BSC) PLUS THE # OF XBL LINKS BSC
MOTOROLA BSC/BTS INTERFACE NON-BLOCKING 1 x 64 kbit/s CIRCUIT/LAPD SIGNALLING LINK 2 x 64 kbit/s CIRCUITS/DRCU/SCU
THE # OF TCHs REQUIRED (USING TYPICALLY 2% BLOCKING) TO CARRY SUBSCRIBER TRAFFIC THE TCHs PLUS THE REQUIRED SIGNALLING TSs DIVIDED BY EIGHT DETERMINES THE CARRIERS REQUIRED (ON A BTS/SECTOR BASIS) BTS
AIR INTERFACE TCHs AND SIGNALLING TSs TYPICALLY 2% BLOCKING
TRANSCODING MUST BE LOCATED AT THE BSC, OR BETWEEN THE BSC AND MSC TCH TS * = TRAFFIC CHANNEL = TIMESLOT X.25 MAY BE PASSED TO RXCDR OR MSC SITE
AIR INTERFACE (TRAFFIC IN ERLANGS)
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT HARDWARE FOR THE A AND BSC TO BTS INTERFACE.
Figure 5-1 BSS planning diagram
58
14th Apr 00
GSM-001-103
Typical parameter values

The parameters required to calculate BSC processing and signalling link capacities are listed in Table 5-2 with their typical values. Two methods for determining capacity are given. The first method is based on the typical call parameters given in Table 5-2 and simplifies planning to lookup tables, or simple formulae indicated in standard traffic model planning steps. When the call parameters being planned for differ significantly from the standard traffic model given in Table 5-2 in this case more complex formulae must be used as indicated in non-standard traffic model planning steps. Table 5-2 Typical call parameters Busy hour peak signalling traffic model Call duration Ratio of SMSs per call Number of handovers per call Ratio of location updates to calls Ratio of IMSI detaches to calls Location update factor Paging rate in pages per second Ratio of intra-BSC handovers to all handovers Percent link utilization (MSC to BSS) for GPROC2 Percent link utilization (BSC to BTS) Blocking for TCHs Blocking for MSCBSS Trunks Parameter reference T = 120 seconds S = 0.1 H = 2.5
l=2
I =0 L=2 P=3 i = 0.6 U (MSC BSS) = 0.20 U (BSC BTS) = 0.25 PBTCHs = 2% PBTrunks = 1%
The location update factor (L) is a function of the ratio of location updates to calls (l), the ratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSI detach is disabled) as in the first formula given below. When IMSI detach is enabled, the second or third of the formulas given below should be used. The type of IMSI detach used is a function of the MSC. If IMSI detach is disabled: L=I If IMSI detach type 1 is enabled: L = I + 0.2 * I If IMSI detach type 2 is enabled: L = I + 0.5 * I
14th Apr 00
59
GSM-001-103
Table 5-3 Other parameters used in determining GPROC and link requirements Busy hour peak signalling traffic model Number of MSC BSC trunks Number of BTSs per BSS Number of cells per BSS Pages per call N B C PPC = P * (T/N) Parameter reference
Assumptions used in capacity calculations

To calculate link and processing capacity values, certain signalling message sequence patterns and message sizes have been assumed for the various procedures included in the signalling traffic model. New capacity values may have to be calculated if the actual message patterns and message sizes differ significantly from those assumed. The assumptions used for the capacity calculations in this manual are summarized below. The number of uplink and downlink messages with the respective average message sizes (not including link protocol overhead) for each procedure are provided in Table 5-4.
Table 5-4 Procedure capacities Procedure Call setup and clearing Handover, incoming and outgoing Location update SMS-P to P (see note below) IMSI detach (type 1) IMSI detach (type 2) Paging MSC to BSC link 5 downlink messages with average size of 30 bytes 6 uplink messages with average size of 26 bytes 4 downlink messages with average size of 37 bytes 5 uplink messages with average size of 38 bytes 5 downlink messages with average size of 30 bytes 6 uplink messages with average size of 26 bytes 7 downlink messages with average size of 30 bytes 7 uplink messages with average size of 42 bytes 1 downlink messages with average size of 30 bytes 1 uplink messages with average size of 42 bytes 3 downlink messages with average size of 30 bytes 3 uplink messages with average size of 26 bytes 1 downlink message with average size of 30 bytes
NOTE The actual number and size of messages required by SMS depend on the implementation of the SMS service centre. The numbers given are estimates for a typical implementation. These numbers may vary.
An additional assumption, which is made in determining the values listed in Table 5-4, is that the procedures not included in the traffic model are considered to have negligible effect.
510
14th Apr 00
GSM-001-103
Link capacities
The level of link utilization is largely a matter of choice of the system designer. A design that has more links running at a lower message rate can have the advantage of offering better fault tolerance, since the failure of any one link affects less signalling traffic. Reconfiguration around the fault could be less disruptive. Such a design could offer reduced queueing delays for signalling messages. A design that utilizes fewer links at a higher message rate, reduces the number of 64 kbit/s circuits required for signalling, and potentially reduces the number of resources (processors, data ports) required in the MSC. It is recommended that the C7 links be designed to operate at no more than 20% link utilization when the MTL is running on a GPROC; and no more than 35% utilization when the MTL is running on a GPROC2. However, before use of the 35% utilization for GPROC2, it is imperative that the operator verifies that the MSC vendor can also support 35% utilization at the MSC end, if not, only 20% link utilization should be used for GPROC2. If higher link utilizations are used, the controlling GPROCs (LCFMTLs) may become overloaded. C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from the failed link to be redistributed among the remaining functioning links. A C7 link set officially has at least two and at most 16 links. The failure of links, for any reason, cause the signalling to be shared across the remaining members of the link set. Therefore, the design must plan for reserve link and processing capacity to support a certain number of failed signalling links.
14th Apr 00
511
BSS planning for GPRS
GSM-001-103

Overview of introduction to BSS planning for GPRS
The BSS planning chapter has the following structure: S S Introduction to BSS planning. PCU-to-SGSN interface planning.
Introduction to BSS planning for GPRS

The BSS planning process for GPRS may involve adding additional BSS equipment and software to the BSS, in addition to the Packet Control Unit (PCU) hardware and software. The extent of the additional BSS equipment depends on the amount of traffic expected to be carried over the GPRS portion of the network. Chapter 3 is intended to provide the network planner with the rules to determine the number of GPRS timeslots that are to be provisioned at the BTS, subsequently provisioned in PCU hardware, and provisioned with communication links. The BSS planning process in this document focuses on the provisioning of the PCU hardware within the BSS. A BSS planning example provided in a later chapter of this guide. Its purpose is to unite the information presented in the entire document from a planning perspective.
Feature compatibility
Alarms consolidation
No additional BSS or GPRS network planning is required. PCU device alarms impact only PCU functional unit severity, and not the cell functional unit severities. Therefore, the impact is to the following PCU devices: DPROC and PCU System Processor (PSP).
BSC-BTS dynamic allocation

No additional BSS or GPRS network planning is required. The Dynamic Allocation feature specifies how the BSC configures and shares the terrestrial backing between the GPRS data traffic and the Circuit Switched (CS) traffic. The terrestrial backing, between the BTS and BSC, must have enough capacity to carry the radio timeslots assigned to both GPRS and circuit switched. If there is not enough capacity, either because there are not enough physical channels, the BSC allocates the backing to CS first. The remaining capacity is assigned to GPRS (reserved GPRS timeslots first, and then to switchable GPRS timeslots). Any terrestrial backing resources not used by circuit switched calls are allocated for switchable use. However, circuit switched calls can take resources away from the switchable pool when traffic demands require more terrestrial capacity. Terrestrial resources available in the switchable pool are available for GPRS traffic use. The BSC may reassign GPRS switchable or reserved backing to CS if backing is required for emergency circuit switched calls. In this case, the backing is reassigned so that the remaining GPRS radio timeslots within a carrier are contiguous.
512
14th Apr 00
GSM-001-103
Circuit error rate monitor

No circuit error rate monitor support is provided by the GPRS feature.
Circuit switched (voice or data) calls

The addition of GPRS to a GSM network impacts the traffic and signalling handling network capability for GSM voice and circuit data traffic. Additional loading on the BSS elements, due to the GPRS traffic, may require additional BSS equipment and interface circuits to be added. There are three classes of mobile devices, which permit non-simultaneous attachment to the circuit switched and packet data channels. This means that the BSS does not need to be provisioned to simultaneously handle the call processing and signalling for both circuit switched traffic and GPRS packet data services on a per-subscriber basis. The BSS treats class A mobiles like class B mobiles. Therefore, the BSS portion of the network supports the simultaneous attachment, activation, and monitoring of circuit switched and packet data services. Simultaneous GPRS and circuit switched traffic is not supported. The mobile user can make and/or receive calls on either of the two services sequentially, but not simultaneously. The selection of the appropriate service is performed automatically.
Concentric cells
GPRS timeslots are available in the outer zone carriers.
Congestion relief
No additional BSS or GPRS network planning is required. Congestion relief considers switchable GPRS timeslots as idle TCHs.
Cell resource manager dynamic reconfiguration

No additional BSS or GPRS network planning is required. The Cell Resource Manager (CRM) dynamic reconfiguration feature can use the switchable GPRS timeslots, but it cannot reconfigure the reserved GPRS timeslots under any circumstances.
Directed retry
No additional BSS or GPRS network planning is required. The BSC uses directed retry to relieve cell congestion by redistributing traffic across cells. For the GPRS traffic portion of the BSS, the BSC treats switchable GPRS timeslots like idle TCHs.
14th Apr 00
513
GSM-001-103
Emergency call pre-emption

No additional BSS or GPRS network planning is required. The BSS will be able to configure any GPRS timeslot to carry out emegency calls. Should an emergency call be made within a cell with a GPRS carrier, the BSS will select the air timeslot that will carry it from the following: S S Idle TCH. Switchable GPRS timeslot (from lowest to highest).
If the Emergency Call Pre-emption feature is enabled, the BSS will select the air timeslot that will carry the emergency call, from the following list in the following order: A. B. C. D. Idle Tch. Switchable GPRS timeslot (from lowest to highest). In-use TCH. Reserved GPRS timeslot (from lowest to highest)
Emergency TCH channels will never be pre-empted.
Extended range cells

No additional BSS or GPRS network planning is required. The extended range cell feature extends the range of a GSM 900 MHz mobile to 35 kilometres. This range extension is not supported for GPRS.
Frequency hopping and redefinition

The GSM radio uses slow frequency hopping to improve data reliability and to increase the number of active users. The GPRS timeslots assigned to the uplink and downlink channels must have the same frequency parameters. GPRS may have a different timeslot activity factor to voice, and thereby causes the cell C/I performance to change from a GSM-only system. The frequency redefinition feature extends the GSM 4.08 capabilities to GPRS.
Global reset
No additional BSS or GPRS network planning is required. The global reset procedure initializes the BSS and MSC in the event of a failure. A global reset does not affect any resources assigned to GPRS.
Integrated M-Cell HDSL interface

No additional BSS or GPRS network planning is required other than to plan for the GDS link. The PCU does not support a high bit-rate subscriber line (HDSL) between the PCU and the BSC. However, the BSC can use an MSI board (with HDSL capabilities) to terminate a GDS link to the PCU if an E1 is used for the connection.
Multiband handovers
No additional BSS or GPRS network planning is required. The BSC treats switchable GPRS timeslots like idle TCHs in the case of multiband handovers.
514
14th Apr 00
GSM-001-103
Over the air flow control for circuit switched

No additional BSS or GPRS network planning is required. The BSC treats switchable GPRS timeslots like idle TCHs in the case of over-the-air Flow Control for the circuit switched mobiles feature.

The BSC may use a switchable GPRS timeslot for a Cell Broadcast CHannel (CBCH) or a Slow Dedicated Command CHannel (SDCCH). The Radio Transceiver Function (RTF) path fault feature converts TCHs to SDCCH when an RTF path fault occurs. The RTF path feature may also convert switchable GPRS timeslots that are TCH barred, to SDCCH. The converted GPRS timeslots are returned to GPRS after the original RTF path fault is cleared.
SMS cell broadcast

The CBCH can reside on a switchable GPRS timeslot. Therefore, switchable GPRS timeslots may be reconfigured as SDCCHs. However, GPRS reserved timeslots cannot be reconfigured as SDCCHs.
SD Placement prioritization
A GPRS carrier cannot be configured so that the sum of the number of SDCCHs allowed and the number of GPRS timeslots, exceed the capacity of the carrier.
BSS statistics
The BSC and PCU collect the statistics listed in Table 5-5 to Table 5-11. The PCU forwards the statistics that it collects, via the BSC, to the OMC-R for collection and network performance review. The following table lists all of the statistics collected, their definition, and the recommended uses of these statistics for the purposes of evaluating and adjusting the BSS portion of the network. NOTE This version of the BSS Equipmemt Planning precedes commercial deployment. After GPRS systems have been deployed and statistics generated, the following table will be updated with recommended threshold values to use in the system replanning process.
The planning flowchart in the beginning of this planning guide has grouped the use of infrastructure statistics into the following categories for network planning purposes: Stats_A: user profile Stats_B: BLER and protocol overhead impact Stats_C: configure GSN Stats_D: configure BSS/PCU
14th Apr 00
515
GSM-001-103
Table 5-5 BSS statistics (part A) PCU statistic GBL_LINK_INS Definition Recommended use
The PCU starts this Statistic used for GBL statistic each time the performance. GBL becomes INS and stops the statistic each time the GBL is no longer INS on a per GBL basis. The time available is reported in milliseconds. The PCU starts this statistic each time the GBL goes OOS and stops the statistic when the GBL comes INS on a per GBL basis. The time unavailable is reported in milliseconds. The BSS increments this statistic when the AGCH/PCH/RACH channel type is accessed for GPRS usage on a per cell basis. Statistic used for GBL performance.
GBL_UNAVAILABLE
GPRS_ACCESS_PER_AGCH
Stats_D Use to configure CCCH and carrier timeslots. This statistic is used in Equation 23 (see Chap 3) for the value of BURST_GPRS.
516
14th Apr 00
GSM-001-103
Table 5-6 BSS statistics (part B) PCU statistic GPRS_ACCESS_PER_PCH Definition The BSS increments this statistic when the AGCH/PCH/RACH channel type is accessed for GPRS usage on a per-cell basis. The BSS increments this statistic when the AGCH/PCH/RACH channel type is accessed for GPRS usage on a per-cell basis. The BSS increments this statistic in order to count the number of channel or resource request messages received on a per-cell basis. The BSS increments this statistic in order to count the number of channel or resource request messages rejected on a per-cell basis. The PCU measures the number of megabits of data information transmitted on the GBL uplink over a given period of time. The PCU calculates this instantaneous throughput by dividing the number of megabits transmitted by the time interval. The time interval, gbl_ul_thrput_time_perio d, is programmable. The PCU filters this statistic by computing a moving average of the instantaneous throughput. The number of instantaneous throughput samples, num_gbl_ul_thrput_samp les, used to compute the moving average is programmable. This statistic is measured on a per GBL basis. Recommended use Stats_D Use to configure CCCH and carrier timeslots. This statistic is used in Equation 24 (see Chap 3) for the value of No_GPRS_Pages. Stats_D Use to configure carrier timeslots.
GPRS_ACCESS_PER_RACH
CHANNEL_REQS_REC
Stats_D Use to configure carrier timeslots.
CHANNEL_REQS_REJECT
Stats_D
GBL_UL_DATA_THRPUT
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed.
14th Apr 00
517
GSM-001-103
Table 5-7 BSS statistics (part C) PCU statistic GBL_DL_DATA_THRPUT Definition The PCU measures the number of megabits of data information received on the GBL downlink over a given period of time. The PCU calculates this instantaneous throughput by dividing the number of megabits received by the time interval. The time interval, gbl_dl_thrput_time_perio d, is programmable. The PCU filters this statistic by computing a moving average of the instantaneous throughput. The number of instantaneous throughput samples, num_gbl_dl_thrput_samp les, used to compute the moving average is programmable. This statistic is measured on a per GBL basis. This statistic counts the number of times a request to flush the data buffers in the PCU. This statistic is measured on a per BSS basis. Recommended use Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed.
GBL_FLUSH_REQS
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed. Threshold value to be supplied after commercial deployment. Stats_D Use to configure CCCH. This static may be used in Equation 17 (see Chap 5) if the location area equals the routeing area.
GBL_PAGING_REQS
This statistics counts the number of paging requests received by the PCU. This statistic is reported on a per-BSS basis.
518
14th Apr 00
GSM-001-103
Table 5-8 BSS statistics (part D) PCU statistic GBL_FLOW_CNTL_SENT Definition This statistic counts the number of flow control messages that are sent over the GBL within a programmable period of time, bssgp_fc_period_c. This statistic is measured on a per-cell basis. This statistic counts the number of data blocks received by the PCU for each QoS level and coding scheme combination. This provides eight statistics: QoS level 1 to 4 for coding schemes CS-1 and CS-2. The count is rounded to the nearest 100 blocks. The statistics are provided on a per-cell basis. This statistic counts the number of data blocks transmitted by the PCU for each QoS level and coding scheme combination. This provides eight (8) statistics: QoS level 1 to 4 for coding schemes CS-1 and CS-2. The count is rounded to the nearest 100 blocks. The statistics are provided on a per-cell basis. Recommended use Stats_A, Stats_D Use to determine if adequate number of links and equipment are deployed and if there are link outage problems. Threshold value to be supplied after commercial deployment. Stats_A, Stats_B, Stats_D Use to determine whether adequate number of links and equipment are deployed. Also use to see if cell C/I performance is as expected. The C/I effects BLER, which in turn effects use of the higher CS-2 rate. Stats_A, Stats_B, Stats_D Use to determine whether adequate number of links and equipment are deployed. Also use to see if cell C/I performance is as expected. The C/I effects BLER, which in turn effects use of the higher CS-2 rate. Stats_A, Stats_D Use to determine whether adequate number of links, equipment and carrier timeslots are deployed. Stats_A, Stats_D Use to determine whether adequate number of links equipment, and carrier timeslots are deployed.
AIR_UL_DATA_BLKS
AIR_DL_DATA_BLKS
TOTAL_AIR_UL_AVAILABLE_BW This statistic counts the number of RLC data blocks available for uplink transfer at the PCU. This statistic is on a per-cell basis. TOTAL_AIR_DL_AVAILABLE_BW This statistic counts the number of RLC data blocks available for downlink transfer at the PCU. This statistic is on a per-cell basis.
14th Apr 00
519
GSM-001-103
Table 5-9 BSS statistics (part E) PCU statistic GBL_DL_DATA_THRPUT_HIST Definition This provides a histogram of the total downlink data throughput over the GBL interface. The histogram is created on a per-GBL basis. Recommended use Stats_A, Stats_D Use to determine whether adequate number of links, equipment, and carrier timeslots are deployed. This statistic may be used in Equation 1 (see Chap 3) for Mean_traffic_load. Stats_A, Stats_D Use to determine whether adequate number of links, equipment, and carrier timeslots are deployed. This statistic may be used in Equation 1 (see Chap 3) for Mean_traffic_load. Stats_A, Stats_D Use to determine whether adequate number of carrier timeslots and equipment are deployed. Threshold value to be supplied after commercial deployment. Stats_A, Stats_D Use to determine whether adequate number of carrier timeslots and equipment are deployed. Threshold value to be supplied after commercial deployment.
GBL_UL_DATA_THRPUT_HIST
This provides a histogram of the total uplink data throughput over the GBL interface. The histogram is created on a per-GBL basis.
MS_CLASS_1_10_REQ
This statistic counts the number of requests received for each mobile class at the PCU. This statistic has the same number of bins as there are mobile classes, class 1 through 10. Each bin is in units of 10 requests, and is measured on a per-cell basis. This statistic counts the number of requests received for each mobile class at the PCU. This statistic has the same number of bins as there are mobile classes, class 11 through 20. Each bin is in units of 10 requests, and is measured on a per-cell basis.
MS_CLASS_11_20_REQ
520
14th Apr 00
GSM-001-103
Table 5-10 BSS statistics (part F) PCU statistic MS_CLASS_21_29_REQ Definition This statistic counts the number of requests received for each mobile class at the PCU. This statistic has the same number of bins as there are mobile classes, class 21 through 29. Each bin is in units of 10 requests, and is measured on a per-cell basis. This statistic counts the amount of time, rounded to the nearest deci-second (0.1 sec), that simultaneous uplink data channels are assigned to a mobile. This statistic has eight bins for 1 channel, 2 channels, etc. up to 8 channels simultaneously assigned. This statistic is on a per-cell basis. This statistic counts the amount of time, rounded to the nearest deci-second (0.1 sec), that simultaneous downlink data channels are assigned to a mobile. This statistic has eight bins. Each bin represents a number of channels in simultaneous use. This statistic is on a per-cell basis. This statistic counts the number of times that a data channel is switched to a circuit switched traffic channel. This statistic is on a per-cell basis. Recommended use Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed Threshold value to be supplied after commercial deployment.
UL_CH_ASGN_DURATION
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed. Threshold value to be supplied after commercial deployment.
DL_CH_ASGN_DURATION
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed. Threshold value to be supplied after commercial deployment.
GPRS_CHANNELS_SWITCHED
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed This metric enables the network planner to see if GPRS performance is being effected due to over use of the switchable timeslots by the GSM circuit switched part of the network.
14th Apr 00
521
GSM-001-103
Table 5-11 BSS statistics (part G) PCU statistic GPRS_DYNET_FAILURES Definition This is a count of four different sources of a terrestrial backing failure. 1) Terrestrial resource for a reserved GPRS timeslot is not provided when requested. 2) Terrestrial backing is stolen from switchable timeslots. 3) Terrestrial backing is taken from reserved timeslots. 4) When converting a switchable GPRS timeslot from packet to circuit mode, a terrestrial backing is unavailable. This statistic creates a histogram of queue time periods measuring requests for switchable timeslot terrestrial backing. Each bin corresponds to a range of queue lengths of time. The maximum, minimum, and average queue time lengths are also included in this histogram. The statistic is pegged on a periodic basis. This histogram is on a per-dynet-group basis. The statistic computes a histogram of the time that the number of requests for backing of switchable timeslots that were in the queue. Each bin of the histogram corresponds to a range of queue lengths. When this statistic is pegged, the bin corresponding to the length of the queue is incremented by one. The statistic is pegged on a periodic basis. The maximum and minimum queue lengths and the average queue length is also reported. Recommended use Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed. This metric enables the network planner to see if GPRS performance is being effected due to over use of the switchable timeslots by the GSM circuit switched part of the network. Threshold value to be supplied after commercial deployment.
GPRS_DYNET_SWI_REQS
Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed. This metric enables the network planner to see if GPRS performance is being effected due to over use of the switchable timeslots. Threshold value to be supplied after commercial deployment. Stats_A, Stats_D Use to determine whether adequate number of links and equipment are deployed This metric enables the network planner to see if GPRS performance is being effected due to over use of the switchable timeslots. Threshold value to be supplied after commercial deployment.
GPRS_DYNET_RES_REQS
522
14th Apr 00
GSM-001-103
PCU-to-SGSN interface planning

The PCU-to-SGSN interface is referred to as the Gb Interface. The Gb Interface connects the BSS PCU to the GPRS SGSN. Motorola supports three Gb Interface options (options A, B, and C), as shown in Figure 5-2. The Remote TransCoDeR (RXCDR) can be used as a E1 switching interface between the PCU and SGSN, as shown in option A. Alternatively, the BSC can be used as an E1 switching interface, as shown in option B. Option C is the case where there is no BSS E1 switching element between the PCU and SGSN. When an RXCDR or BSC is used as a E1 switching element, as shown in option A and option B, respectively, additional equipment provisioning of these network elements may be required in order to support the PCU E1 interfaces, in accordance with the provisioning rules for adding E1 interfaces to the RXCDR and BSC network elements. The BSS Gb interface alternatives are illustrated in Figure 5-2.
MSC
A INTERFACE RXCDR Gb OPTION A
Gb OPTION B OMC-R BSC FOR OPTION A and B
PCU Gb OPTION C
BTS1
BTSn
Figure 5-2 Gb interface alternatives
14th Apr 00
523
GPRS upgrade provisioning rules
GSM-001-103

Overview of provisioning rules
The Provisioning rules have the following structure: S S S S BSS upgrade provisioning rules. PCU provisioning rules. Link provisioning rules. BTS-BSC E1 links (Abis).
BSS upgrade provisioning rules

Table 5-12 identifies the BSS network elements that may require upgrading. Consult the relevant planning information for the chassis-level planning rules covering the BSC, BTS, OMC-R, and RXCDR. The PCU expansion rules are provided in the next section. Table 5-12 BSS upgrade in support of GPRS Equipment BSC Additional element Chassis (optional) Replace DRCU with DRCU2/3 BSS upgrade Add KSWs, LCF GPROC2s, MSIs per BSC as needed in support of the Gb, GDS TRAU, GDS LAPD (GSL), RSL, BSC-BTS traffic carrying E1 links. Provision with DRCU2/3 or later version radios. Follow BTS provisioning rules for the number of radios required at the BTS and other supporting boards, including DHP processor boards, as necessary. The same carrier dimensioning rules can be used for a GPRS carrier as for a circuit switched carrier. (The TSW must be replaced with the KSW when GPRS support of the BSC-BTS dynamic allocation feature is enabled.) One per 64 BSS network elements, with any mix of circuit or packet (GPRS) channels supported; software in support of the PCU. Add KSWs, GPROC2s, MSIs per RXCDR as needed to support the Gb interface shown as option A in Figure 5-2.
BTS (BTS4, BTS5, BTS6, ExCell, TopCell)
OMC-R
Software upgrade for GPRS support Chassis (optional)
RXCDR
524
14th Apr 00
GSM-001-103
GPRS PCU provisioning rules

There is one PCU per BSS. The PCU planning process determines the type and number of DPROC boards to populate in the PCU. The PCU provisioning rules provided in the following Table 5-13 to Table 5-15 use the number of GPRS timeslots as the planning rule input. The estimation process for determining the number of GPRS timeslots is provided in a previous chapter of the document. The BSC-to-PCU E1 links should not go through any network elements. The E1 links should meet the ITU-T Recommendation G.703. This recommendation includes an E1 length specification. Refer to Recommendation G.703, Physical/Electrical Characteristics of Hierarchical Digital Networks, Sept. 1991, for further detail.
E1 Interface provisioning
The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. The PCU is connected directly to the BSC E1 interfaces and the BSC is configured to provide the E1 master clock. If the PCU attaches to a GSN that does not have a master clock source, an interface piece of equipment, such as a Digital Cross Connect switch (DACs) that does have a master clock source, should be used. The Motorola BSC and RXCDR equipment can be used in place of a DACs for this purpose.
14th Apr 00
525
GSM-001-103
Table 5-13 PCU planning rules (part A) Rule number 1 2 3 4 5 6 7 8 Element Air filter Alarm board Bridge board Circuit breakers cPCI enclosure (16 slot) Fan/power supply unit GDS TRAU E1 GDS TRAU E1 Planning rule 1 per fan/power supply. Maximum of 3 per PCU. 1 per PCU. An MPROC board requires one bridge board. 1 main circuit breaker per PCU. 1 per BSS. 3 per cPCI shelf, providing N+1 hot-swap redundancy. Minimum of 2 units required. Up to 124 active timeslots is permitted on one TRAU_Type_GDS E1. One TRAU_Type_GDS E1 can carry up to 124 Active timeslots or 124 standby timeslots or any combination of active and standby timeslots. A TRAU_Type_GDS E1 carrying 124 standby timeslots requires more than one PRP for standby timeslot processing. The load balancing software distributes the load evenly between PRPs. For example, if there are two PRPs in the system, each PRP processes 62 standby timeslots. The BSC GPROC2 LCF needs to terminate 12 LAPD channels in the case when a maximum number of LAPD-Type links are provisioned at the PCU. The GSL traffic is load balanced over all GSLs. The first E1 carries up to six LAPD links and the second E1 up to another six LAPD links. For LAPD-Type GDS resiliency, two E1s are recommended to be used regardless of the number of LAPD channels required. For example, if only one channel is required to carry the expected signalling load, two E1s with one LAPD channel per E1 should be used. The MPROC load balancing software distributes the load evenly between the two LAPD channels.
GDS TRAU E1
10
GPROC2 LCF
11
GSL LAPD (GSL) E1
The PCU provisioning rules are provided in the following Table 5-13 to Table 5-15.
526
14th Apr 00
GSM-001-103
Table 5-14 PCU planning rules (part B) Rule number 12 13 Element MPROC board PCU cabinet Planning rule The PCU cPCI shelf requires one MPROC. Up to three PCU cPCI shelves per cabinet may be provisioned. Each PCU shelf is dedicated to one BSC. There are no PCU-to-PCU inter-connects within the cabinet. The maximum number of active timeslots per PCU is 240 in the fully redundant configuration, as shown in Figure 5-3. The maximum number of standby timeslots per PCU is 720 in the fully redundant configuration, as shown in Figure 5-3. There may be up to four Gb E1s per PCU. There may be up to nine GDS TRAU-Type GDS E1 links per PCU. The PICP boards can terminate the following links: GDS TRAU-Type GDS links, GDS LAPD-Type GDS links, and Gb links. One PICP board is required per four TRAU-Type GDS E1s. This is a per E1 specification independent of the number of timeslots being carried on the individual E1s. Four TRAU-Type GDS E1s can carry a maximum of (4 x 124) 496 active timeslots, standby timeslots, or any combination of the two. However, the PCU limits the number of PRP boards that can be used on the cPCI shelf to 10; so this restriction limits the number of active timeslots that can be processed to 300. The PCU can support up to three PICP boards. A PICP board has two PMC modules. N+1 board redundancy is supported. TRAU-Type GDS, LAPD-Type GDS (GSL), Gb E1 links cannot share a PMC module. Only one TRAU-Type GDS per PMC module on a PRP board is allowed. The other E1 termination on the PMC module cannot be used. Up to two Gb E1 links per PMC module is allowed. PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module, but cannot terminate GDS LAPD E1s or Gb E1 links. Up to 30 active and 90 standby timeslots can be terminated on one PRP.
14
PCU cPCI shelf
15
PCU cPCI shelf
16 17 18
PCU Gb E1 PCU GDS E1 PICP board
19
PICP board
20 21 22 23 24
PICP board PICP board PICP board PMC module PMC module
25 26
PMC module PRP board
27
PRP board
The PCU provisioning rules are provided in the following Table 5-13 to Table 5-15.
14th Apr 00
527
GSM-001-103
Table 5-15 PCU planning rules (part C) Rule number 28 Element PRP board Planning rule The active timeslots and standby timeslots are managed by load balancing software which limits the number of active timeslots to 30 for each PRP. Therefore, one E1 carrying 124 active timeslots can supply up to five PRPs with active timeslots. The software load balances, in this case, such that four of the PRPs receives 25 active timeslots and the fifth receives 24. Note that the actual distribution of timeslots may be slightly different from that shown in this example depending on cell configurations. That is, all timeslots for a single cell must terminate on a single PRP, which can lead to slight imbalances when multiple timeslots are configured per cell. 29 PRP board The PCU can support up to 10 PRP boards. When 10 PRP boards are populated, there are only two slots available for PICP boards, thereby limiting PICP redundancy, Gb link redundancy, LAPD-Type GDS redundancy, and TRAU-Type GDS link redundancy. A PRP board has one PMC module. N+1 board redundancy is supported. A transition module is required per PRP and PICP board.
30 31 32
PRP board PRP board Transition module
528
14th Apr 00
GSM-001-103
Figure 5-3 shows the PCU layout.
CARD SLOT 1
CARD SLOT 11
MPROC
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
D P R O C
ALARM MODULE
PSU/FAN CARD SLOT 11
PSU/FAN
PSU/FAN CARD SLOT 1
TRANSITION MODULE
H T T T T T T S MMMMM MC
T T T T T MMMMM
I O
POWER DISTRIBUTION MODULE
Figure 5-3 PCU physical layout
14th Apr 00
529
GSM-001-103
DPROC (PICP or PRP use)

DPROC board slots can be used for either PICP or PRP purposes. Each DPROC has an E1 transition module mounted in the rear of the shelf directly behind it. A DPROC may be configured as a PICP with zero, one, or two E1 PMC modules, and with PICP software. The DPROC may be configured as a PRP with zero or one E1 PMC modules, and with PRP software. The PICP provisioned boards should be populated from left to right. For system availability reasons, PICPs should be evenly distributed between the two backplanes within the PCU shelf. The left and right backplanes are connected together through the bridge board located behind the MPROC processor board. Therefore, the first PICP would occupy board slot 1, PICP two would occupy board slot 11, PICP three would be in slot 2, and PICP four in slot 12. PRP provisioning should also be performed in a similar fashion, alternating provisioned boards between the left and right backplanes.
MPROC
The MPROC board takes the equivalent of two board slots of space. An MPROC has a bridge board in the rear of the shelf directly behind it. The redundant MPROC is identified with an R. The bridge board associated with the MPROC is also a redundant board.
AUX
There are four bays on the right side of the shelf that may be used for auxiliary equipment such as tape drives, CD-ROM drives, and hard disks. The PCU is configured without any auxiliary equipment and this area of the shelf is covered with blank panels.
Alarm panel
This panel is located above the DPROCs and MPROC, and has front access.
Fan/power supplies
There are three separate fan/power supplies modules. They are located in the bottom of the shelf. Replacement is from the front.
Air filter
There is an air filter that is mounted in front of each fan/power supply unit, and is replaceable from the front. Replace each air filter every 12 months.
PCU cabinet
The PCU shelf mounts in a cabinet that can hold up to three PCU shelves. Each PCU is connected to only one BSC; so one PCU cabinet can serve up to three BSCs. Each cabinet is pre-wired with a panel in the rear of the cabinet for the desired E1 termination type, balanced 120-ohm, or unbalanced 75-ohm terminations with 1500-volt lightning protection per E1.
N+1 equipment redundancy supported

The following N+1 equipment redundancy is supported: S S S N+1 PICP and PRP board redundancy. 2 PS/FAN units non-redundant, 3 PS/FAN unit redundant. 1 MPROC/bridge board pair non-redundant, 2 MPROC/bridge board pairs redundant (requires future software release, redundant configuration not available in GSR 4.1). E1 redundancy requires the provisioning of the redundant hardware with active E1 links. The E1 redundancy is available for GSL, GDS, and GBL links. Load balancing is performed across the GDS, GSL, and GBL E1 links so that if a link should fail, the existing load is redistributed to the other links. System Information: BSS Equipment Planning 68P02900W21-G
14th Apr 00
530
GSM-001-103
System increments
The PCU may be upgraded for additional capacity, by one PRP board and by one PICP board at a time. This upgrade must adhere to the PCIP to GDS TRAU E1 ratio rule, of one PICP board per four GDS TRAU E1 links.
Maximum configuration
Table 5-16 provides the maximum BSS network parameter values in support of GPRS per BSS network element. Table 5-16 Maximum BSS network parameter values in support of GPRS (part A) Network element BSS(BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (PCU) Network parameter GPRS carriers per cell Timeslots per carrier Users per timeslot Users per carrier Timeslots per active user DL Timeslots per active user UL Switchable GPRS timeslots per carrier Reserved GPRS timeslots per carrier Active air interface timeslots 1 8 1 8 6 4 8 8 240 redundant, per Figure 5-4. Maximum value
Table 5-17 and Table 5-18 provide the maximum BSS network parameter values in support of GPRS per BSS network element. Table 5-17 Maximum BSS network parameter values in support of GPRS (part B) Network element BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (BTS) BSS (PCU) BSS (PCU) Network parameter GPRS carriers per cell Time slots per carrier Users per time slot Users per carrier Time slots per active user DL Time slots per active user UL Switchable GPRS time slots per carrier Reserved GPRS time slots per carrier Active air interface time slots Monitored air interface timeslots 1 8 1 8 6 4 8 8 240 redundant, see Figure 5-4 720 redundant, see Figure 5-4. Maximum value
14th Apr 00
531
GSM-001-103
Network element BSS (PCU) BSS (PCU) PCU (PRP DPROC)
Network parameter Active air interface timeslots Monitored air interface timeslots GDS link processing
Maximum value 300 non-redundant, see Figure 5-5. 810 non-redundant, see Figure 5-5. 30 active users, 90 standby timeslots. This is equivalent to 30 active TimeSlots (TSs) with one TS/ user. For multislot operation, fewer users are supported. For example, if each user is allocated 2 TSs, only 15 active users are supported per PRP. The standby timeslots are monitored for service request, but not carrying traffic. Up to 4 E1s per PICP DPROC. 1 Gb E1 to carry frame relay channellized or non-channellized GPRS traffic per 150 active CS-1 or CS-2 timeslots deployed over the BSC-to-PCU interface. The Gb E1 carries both data and signalling traffic between the PCU and SGSN. 3 10 250 100
PCU (PICP DPROC) PCU (PICP DPROC)
BSC-PCU E1 interface PCU-SGSN (Gb) interface
PCU PCU PCU PCU GSL E1 links
Max PICP DPROCs Max PRP DPROCs Number of cells supported Number of BTS sites supported
Max physical E1s between 2 BSC & PCU (one primary E1 and one redundant) Max per E1 link (corresponds to a quantity of six 64 kbit/s LAPD channels) Max per PCU Max per PCU Max on one bearer Link Max 6
LAPD-Type GDS (GSL) links
TRAU-Type GDS links (E1s) GBL links (E1s) Gb PVCs Gb Frame Relay frame octet size
9 4 318 1600 bytes
532
14th Apr 00
GSM-001-103
GPRS link provisioning rules

The following text provides the rules for provisioning the PCU and BSC links in support of GPRS. The typical call parameters used in the link defining equations are detailed in Table 5-18. Table 5-18 Typical call parameters Parameter PgMsgSize Mean_TBF_Rate ImmAssignMsgSize No_GPRS_TS_Site Mean_LLC_PDU_size GPRS_Page_Rate_Max LAPD_Utilization RSL_Rate Code_load rate Cell_update rate Msg_sw_ts_chg rate Status_queries rate No_Active_ts Mslot_Util_factor 400 bits. 1 TBF per sec based on transmission time for 2 435byte LLC PDUs at the CS-1 rate. 400 bits. 24 GPRS timeslots (3-sector site, 1 GPRS carrier per sector). 3.48 kbits. 12 pages per second per site. 0.25. 16 kbit/s for 16 kbit/s RSLs and 64 kbit/s for 64 kbit/s RSLs. 0 kbit/s. 0 kbit/s, approximately. 0 kbit/s, approximately. 0 kbit/s, approximately. 0 to 300 per PCU. 0.5, ratio of mean number active timeslots on a GPRS carrier to total number of provisioned GPRS timeslots on a carrier. 1 second. 0.1, use decimal form. 720 kbits maximum message size based on maximally configured PCU. 360 seconds, minimum measurement interval. CS-1 = 9.05 kbit/s, CS-2= 13.4 kbit/s. 0.16, decimal form. 0.1, decimal form. 1.984 Mbit/s. Value
Mean_TBF_duration %TBF_pg Stat_Msg_size Stat_meas_interval CS_rate %GBL_protocol_ovhd %RLC/MAC_ovhd GBL_E1_BW
14th Apr 00
533
GSM-001-103
Redundancy planning
For redundant PCU operation, the PCU should be planned such that there are N+1 boards provisioned as shown in Figure 5-4. That is, only eight PRP boards and two PICP boards are required to handle the expected maximum GPRS traffic load. The ninth PRP board and third PICP board offer the N+1 hardware redundancy. The third PICP board provides redundancy for the software processes that run on the first two PICP boards. For a fully configured PCU with eight GDS TRAU E1s, at least two PICP boards are required in order to provide enough processing capability. The GDS TRAU E1 link redundancy is obtained with the N+1 PRP board. The GSL E1 link redundancy is obtained by provisioning a second GSL E1 on the second PICP. One PICP is required per four GDS TRAU E1 links. The PCU load-balances across the GDS TRAU and LAPD GSL links. If a PRP or PICP board fails, the PCU automatically re-distributes the load to the other boards in-service. Two Gb E1s are required to handle the traffic for a fully configured PCU. Gb E1 link resiliency is obtained by adding an additional two Gb E1s and load balancing across all of the Gb E1s. The PRP and PICP (DPROC) boards are hot swappable, so that when a board failure is detected, a replacement board may be inserted without disrupting ongoing GPRS traffic on the other boards. The DPROC must be locked before removal, and unlocked following board insertion. The PRP and PICP boards have associated transition module boards not shown in the figures below. There is an associated redundant transition module board with each redundant PRP and PICP board. The PCU shelf hardware allows for N+1 MPROC board redundancy. This N+1 redundancy capability is subject to MPROC redundancy software availability. The MPROC board(s) and the MPROC bridge boards are not shown in the figure below, but the redundant MPROC has an associated redundant bridge board. The PCU shelf comes with N+1 power supply/fan redundancy. The power supplies are hot swappable. The power supply/fan units are not shown in figures below. The PCU architecture offers the network planner a considerable degree of provisioning flexibility. Figure 5-4 and Figure 5-5 demonstrate this flexibility where the provisioning goals may range from full redundancy (Figure 5-4) to maximum coverage (Figure 5-5). Table 5-19 summarizes the provisioning goals demonstrated with Figure 5-4 and Figure 5-5.
534
14th Apr 00
GSM-001-103
PCU HARDWARE BSC GDS 30 TS ACTIVE 90 TS STANDBY PMC PRP1 SGSN
GDS 30 TS ACTIVE 90 TS STANDBY
PMC
PRP2
TO GDS 30 TS ACTIVE 90 TS STANDBY REDUNDANT GDS 30 TS ACTIVE 90 TS STANDBY PMC PRP8
PMC
PRP9 REDUNDANT
GSL 6 LAPD TS REDUNDANT GSL 6 LAPD TS
PMC PMC
PICP1
GBL GBL PMC PMC GBL GBL PMC PMC PICP3 REDUNDANT PICP2 REDUNDANT GBLs
Figure 5-4 Goal: maximum throughput and coverage with a fully redundant configuration
14th Apr 00
535
GSM-001-103
PCU HARDWARE BSC GDS 30 TS ACTIVE 90 TS STANDBY PMC PRP1 SGSN
PMC
PRP2
TO GDS 30 TS ACTIVE 90 TS STANDBY PMC PRP8
PMC
PRP9
GSL 6 LAPD TS
PMC PMC
PICP1
REDUNDANT GSL 6 LAPD TS
GBL GBL PMC PMC GBL GBL PMC PMC PICP3 PICP2 REDUNDANT GBLs
Figure 5-5 Goal: maximum throughput and coverage, full redundant not required Refer to Table 5-11 for a matrix of provisioning goals achieved with this instance of PCU provisioning.
536
14th Apr 00
GSM-001-103
Table 5-19 PCU provisioning goals Metric Goal Maximum coverage with redundant configuration; see Figure 5-4. 240 720 960 Maximum coverage, redundancy not required; see Figure 5-5. 270 810 1080
No. active timeslots No. standby timeslots Total number of provisioned timeslots at a BSS is the sum of the number of active timeslots with the number of standby timeslots. No. PRPs No. PICPs No. TRAU-Type GDS E1s No. LAPD-Type GDS (GSL) E1s No. Gb E1s PRP board redundancy PICP board redundancy GDS TRAU timed E1 redundancy GSL E1 redundancy Gb E1 redundancy
9 3 9 2 4 Yes Yes Yes Yes Yes
9 3 9 2 4 No No No Yes Yes
14th Apr 00
537
Determining the RSLs required
GSM-001-103

Introduction
Each BTS site which is connected directly to the BSC, including the first site in a daisy chain, must be considered individually. Once individual RSL requirements are calculated the total number of LCFs can be determined for the BSC.
The following factors should be considered when planning the provision of RSL (LAPD signalling) links from the BSC to BTS sites: S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTS site. One link can support multiple collocated cells. As the system grows, additional signalling links may be required. Refer to the section Determining the required BSS signalling link capacities in this chapter to determine the number of RSL links required. If closed loop daisy chains are used, each site requires an RSL in both directions. The provision of additional RSL links for redundancy.
S S
Standard traffic model

The number of BSC to BTS signalling links (RSL) must be determined for each BTS. This number depends on the number of TCHs at the BTS. Table 5-20 gives the number of RSLs required for a BTS to support the given number of TCHs. These numbers are based on the typical call parameters given in the standard traffic model column of Table 5-2. If the call parameters differ significantly from the standard traffic model, use the formulae for the non-standard traffic model. Table 5-20 Number of BSC to BTS signalling links n = number of TCHs at the BTS n <= 30 30 < n <= 60 60 < n <= 90 90 < n <= 120 120 < n <= 150 150 < n <= 180 180 < n <= 210 210 < n <= 240 NOTE A BTS shall support either 64 kbit/s RSLs or 16 kbit/s RSLs, but not both. Number of 64 kbit/s RSLs 1 1 1 1 2 2 2 2 Number of 16 kbit/s RSLs 1 2 3 4 5 6 7 8
538
14th Apr 00
GSM-001-103
Non-standard traffic model

If the call parameters differ significantly from those given in Table 5-2, use the following formula to determine the required number of 64 kbit/s RSLs (rounded up to the next nearest integer). N BSC*BTS + (n * (95 ) 67 * S ) 35 * H ) 25 * L)) ) 6*P (1000 * U * T) (1000 * U)
If the call parameters differ significantly from those given in Table 5-2, use the following formula to determine the required number of 16 kbit/s RSLs (rounded up to the next nearest integer). N BSC*BTS + Where: (n * (95 ) 67 * S ) 35 * H ) 25 * L)) ) 6*P *4 (1000 * U * T) (1000 * U) is: the number of MSC to BSC signalling links. the number of TCHs at the BTS site. the ratio of SMSs to calls. the number of handovers per call. the location update factor. the percent link utilization (for example 0.20). the average call duration. the paging rate in pages per second.
NBSC to BTS n S H L U T P
BTS-BSC E1 links (Abis)

Traffic (GPRS timeslots)
E1 line capacity should be added from the BTS to the BSC in direct proportion to the number of timeslots that are added for GPRS timeslot provisioning. Each GPRS timeslot corresponds to 16 Kbit/s of E1 bandwidth, or one quarter of one 64 timeslot on an E1. The additional GPRS traffic may be accommodated with the existing E1 lines carrying circuit switched traffic. This provisioning step requires the network planner to look at the current E1 provisioning at each BTS site in order to determine whether additional E1 line capacity should be added.
Signalling (RSL)
The RSL signalling link provisioning has a contribution from the GSM circuit switched portion of the network and from the GPRS portion. The equation for determining the number of RSL links for the combined signalling load is as follows.
Equation 5
RSL GPRS)GSM + RSLGPRS ) RSLGSM Equation 5 is evaluated for 16 kbit/s RSLs or for 64 kbps RSLs. The interface between the BTS and BSC does not permit mixing the two RSL rates.
14th Apr 00
539
GSM-001-103
Where:
RSLGPRS+GSM
is:
The combined number of RSL signalling links on a per BTS site basis operating at a 16 kbit/s RSL rate or at a 64 kbit/s RSL rate. This is the number of RSL signalling links required to serve the GPRS portion of the network at 16 kbit/s or at 64 kbit/s. This is the number of RSL signalling links required to serve the GPRS portion of the network at 16 kbit/s or at 64 kbit/s.
RSLGPRS
RSLGSM
Equation 8
IMM_ASSIGN GPRS + No_GPRS_TS_Site * Mean_TBF_Rate * ImmAssignMsgSize Where: IMM_ASSIGN GPRS is: The Immediate assignment message bit rate, in Kbps per BTS site. This is the number of active GPRS timeslots for the BTS site. This is the mean rate of TBFs per second for the BTS site. This is the size of the immediate assignment messages measured in bits.
No_GPRS_TS_Site
Mean_TBF_Rate
ImmAssignMsgSize
540
14th Apr 00
GSM-001-103
Equation 6
RSL GPRS + Where: P GPRS ) IMM_ASSIGN GPRS RSL_Rate * LAPD_Utilization is: This is the number of RSL signalling links required to serve the GPRS portion of the network. This is the number of GPRS page bits generated per BTS site per second. The immediate assignment message bit rate, in kbps per BTS site This is the RSL channel rate that is to be used. It should match the rate used for the GSM RSL messages, either16 kbit/s or 64 kbit/s. This is the utilization factor for the RSL LAPD messaging, typically a value of 0.25 is used.
RSLGPRS
PGPRS
IMM_ASSIGN GPRS
RSL_Rate
LAPD_Utilization
Equation 7
P GPRS + PgMsgSize * GPRS_Page_Rate_Max Where: PGPRS is: This is the number of GPRS page bits generated per BTS site per second. This is the size of the paging message measured in bits per page message. This is the GPRS paging rate on a per BTS site basis measured in page messages per second.
PgMsgSize
GPRS_Page_Rate_Max
Determine the contribution from the existing or planned GSM circuit switched RSLs. RSLs are deployed as 16 kbit/s signalling links or as 64 kbit/s signalling links. The number of RSLs to deploy for a given GSM circuit switched traffic load is defined earlier in the text. The following equations are provided in order to calculate the correct level of RSL provisioning for the 16 kbit/s and 64 kbit/s RSL signalling channel rates. For the GSM circuit switched call model, evaluate the following Equation 9 when 64 kbit/s RSL signalling links are used.
14th Apr 00
541
GSM-001-103
Equation 9
RSL GSM + RSLGSM_64Kbps + n * (95 ) 67 * S ) 35 * H ) 25 * L) ) 6*P 1000 * U * T 1000 * U
Evaluate the following Equation 10 when 16 Kbps RSL signalling links are used.
Equation 10
RSL GSM + RSLGSM_16Kbps + n * (95 ) 67 * S ) 35 * H ) 25 * L) ) 6*P *4 1000 * U * T 1000 * U
The variables in Equation 9 and Equation 10 above are defined as follows: Where: n S H L U T P is: The number of TCHs for the BTS site. The ratio of SMSs to calls. The number of handovers per call. The location update factor. The percent link utilization (for example 0.25). The average call duration in seconds. The paging rate in pages per second.
BSC-PCU
E1 links connect the BSC to the PCU. The E1 length (or BSC to PCU distance) complies with G.703 recommendations and does not support any equipment, including a repeater in between.
BSC-PCU: traffic (GDS TRAU)

Typically, one E1 is provisioned per PCU PRP circuit board to carry GDS TRAU. Each E1 can support up to 124 timeslots that can be a mix of active and standby timeslots. The E1 can carry traffic originating from several different cells. The allocation of timeslots on the E1 is managed by the infrastructure. Each cell can contribute GPRS traffic for up to 8 timeslots.
BSC-PCU: signalling (GDS LAPD GSL)

The PCU requires one E1 in order to carry GSL signalling, and a second E1 for redundancy. The PCU can support up to six primary GSL 64 kbit/s timeslots and six redundant. Each 64 kbit/s timeslot is one LAPD channel. Provisioned GSL timeslots are load balanced over two E1 links, as the mechanism for providing resiliency against link failures. It is recommended that two GSL E1 links are provisioned for resiliency purposes, even when the GSL is lightly loaded. Each GSL message consists of three parts: LAPD protocol, BSS executive header protocol, and the application message carrying actual signalling information. The LAPD and BSS protocol portion can be considered messaging overhead. Therefore, the actual usable bandwidth per E1 timeslot for GSL signalling is 60 kbit/s. The calculation for the required number of GSL links is as per Equation 11.
542
14th Apr 00
GSM-001-103
Equation 11
No_GSL_TS + Where: No_GSL_TS Num_1 60Kbps * LAPD_Utilization is: This is the number of 64 kbit/s LAPD GSL timeslots to provision. The numerator for Equation 11. See Equation 12. This is the LAPD utilization factor, typically on the order of 0.25.
Num_1
LAPD_Utilization
Equation 12
Num_1 + Code_load ) Cell_update ) Msg_sw_ts_chg ) Status_Queries ) No_Imm_Assign ) GPRS_Page ) Stat_msg
Where:
Num_1 Code_load
is:
The numerator for Equation 11. The PCU code load rate from the BSC to the PCU. Typically this value is equal to zero because the code load occurs only when the PCU is out of service. Periodic cell list update rate to the BSC from the PCU. This traffic is negligible, and can be considered equal to zero. PCU message rate generated due to switchable timeslot changes. This traffic is negligible, and can be considered equal to zero. PCU status query rate from the BSC and OMC. This traffic is negligible, and can be considered equal to zero.
Cell_update
Msg_sw_ts_chg
Status_queries
14th Apr 00
543
GSM-001-103
Equation 13
n
No_Imm_Assign + SIMM_ASSIGN GPRSi

i+1
Where:
No_Imm_Assign
is:
This is the rate of immediate assignment message Kbps per-BSS site (see equation 8) This is the number of BTSs per BSS.
Equation 14
n
1 GPRS_Page + 0.0001 * PgMsgSize * SP GPRSi PgMsgSize

i+1
Where:
GPRS_Page
is:
The GPRS page traffic measured in kbit/s per BSS basis. This is the number of GPRS page bits generated per BTS site per second. (See Equation 7) This is the size of a page message measured in bits per page message. number of BTS per BSS
PGPRS
PgMsgSize
544
14th Apr 00
GSM-001-103
Equation 15
Stat_msg + Stat_msg_size Stat_meas_interval Where: Stat_msg is: This is the PCU generated statistics message rate measured in bits per second. The size of a PCU statistics message measured in bits. This is the interval of time between PCU statistics message transfers to the BSC. This value is measured in seconds.
Stat_msg_size
Stat_meas_interval
The average bandwidth use of a GSL 64 kbit/s LAPD in support of Stat_msg transfers is much lower than 64 kbit/s. However, when a transfer occurs, it is possible to occupy the timeslot for the duration of the Stat_msg transfer which, for a maximally-configured PCU, could be of the order of 12 seconds. Therefore, it is recommended that an extra GSL timeslot is allocated in support of this periodic burst transfer condition when Equation 15 evaluates to one. This prevents the potential blocking of paging messages during the interval of time the Stat_msg transfers occur. When GSL N+1 redundancy is provisioned, there is no need for an extra timeslot.
PCU-SGSN: traffic and signalling (Gb)

The traffic and signalling is carried over the same E1 on the Gb Link (GBL). The number of required 64 kbit/s Gb link timeslots can be calculated using Equation 16. Each E1 can carry up to 31 timeslots. When fewer than 31 timeslots are needed on an E1, specifying a fractional E1 may be more cost effective. Table 5-21 may be used to look up the number of E1 links to use for a given number of timeslots. Table 5-21 Timeslots-E1s Number of timeslots (No_GBL_TS) 1-31 32-62 63-93 94-124 1 2 3 4 Number of E1s
14th Apr 00
545
GSM-001-103
Equation 16
Im Where: No_GBL_TS + No_GBL_TS Reqd_GBL_BW 64, 000 is: This is the number of timeslots to provision on the GBL E1 between the PCU and SGSN. This value can be used to specify a fractional E1. This parameter is defined by Equation 17, and represents the required bandwidth (bps) for GPRS data transmission over a GBL interface between the PCU and SGSN after all of the protocol and signalling overhead is accounted for.
Reqd_zsGBL_BW
Equation 17
Reqd_GBL_BW + [No_Active_ts * CS_rate * (1 ) %GBL_protocol_ovhd) * (1 * %RLC MAC_ovhd)] ) [PgMsgSize * GPRS_Page_Rate_Max * No_BTS_sites]
Where:
Reqd_GBL_BW
is:
This parameter is the numerator for Equation 16. It represents the required bandwidth (bps) for GPRS data transmission over the GBL interface between the PCU and SGSN after all of the protocol and signalling overhead is accounted for. This is the number of active timeslots on a per-BSS basis. CS_rate is the CS rate measured in bits per second. This should be a weighted value over the CS-1 and CS-2 rates. The weighting factor is determined by the percentage of time the CS-1 rate is used and the CS-2 rate is used. Typically, the network chooses the CS-2 rate approximately 90% of the time, and CS-1 rate 10% of the time, thereby giving a weighted value of approximately 13 kbit/s.
14th Apr 00
No_Active_ts
CS_rate
546
GSM-001-103
Where:
Reqd_GBL_BW
is:
This parameter is the numerator for Equation 16. It represents the required bandwidth (bps) for GPRS data transmission over the GBL interface between the PCU and SGSN after all of the protocol and signalling overhead is accounted for. This is the percentage protocol overhead on the GBL link expressed as a decimal number. The is the percentage protocol overhead of the RLC/MAC protocol layer removed at the PCU prior to relaying the PDU over the Gb link. This is the size of the page messages sent from the SGSN to the PCU over the Gb link. This message size is expressed in bits. This is the maximum page rate expected over the Gb link from the SGSN to the PCU. This value is expressed in pages per second per BTS site. This is the number of BTS sites served by the SGSN module for the attached PCU. Note that an SGSN module can serve more than one PCU.
%GBL_Protocol_ovhd
%RLC/MAC_ovhd
PgMsgSize
GPRS_Page_Rate_Max
No_BTS_sites
Frame relay parameter values

The network planner needs to specify the values for the following three frame relay interface parameters: S S S Committed Information Rate (CIR). Committed Burst Rate (Bc). Burst Excess Rate (Be).
These frame relay parameter values are determined as detailed in the following text.
14th Apr 00
547
GSM-001-103
Committed information rate

The recommended Committed Information Rate (CIR) value per each NS-VC should be greater than, or equal to, 50 percent of the cumulative information rate of the active timeslots routed to a single NS-VC by the PCU. The Motorola PCU distributes the use of all the NS-VCs by the subscribers evenly in a round-robin manner. The round-robin algorithm continuously assigns subscribers to the next NS-VC in a sequential manner when a subscriber PDP context is established. If an NS-VC becomes unavailable, it is skipped over, and the next available NS-VC in the round-robin is used. This is the BSSGP feature that inherently provides load sharing over all available NS-VCs. The load sharing capability over multiple Gb links is provided by the BSSGP high-level protocol layer, which results in link resiliency. The recommended CIR value per each PVC should be greater than, or equal to, half the cumulative information rate of the active timeslots routed to a single NS-VC. This mapping is actually determined as a mean load, evenly distributed over all of the available NS-VCs as next described. The mean busy hour load of each cell may require one to four active timeslots, based on the recommended BSS provisioning rules. The BSS planning rules recommend that the mean traffic load of a cell should not exceed four active timeslots per cell. The number of standby timeslots planned at each cell should equal the number of planned active timeslots. The standby timeslots, when used as active timeslots, enable a cell to handle the peak or burst characteristic of packet data traffic. Over many cells, it is expected that the PCU will handle the traffic throughput equal to the number of active timeslots planned for the busy hour traffic load. The recommended frame relay network CIR value is calculated by dividing the bandwidth required to serve half the number of active timeslots for all the cells served by the PCU by the number of NS-VCs provisioned between the PCU and SGSN over the Gb interface.
548
14th Apr 00
GSM-001-103
Equation 18
n
CIR_Value +
F * S[(Num_Act) * (%CS1) * 9.05 ) (Num * Act) * (%CS2) * 13.4]i Num_NSVC

i
+1 is: Committed Information rate per NS VC (PVC) The number of sites served by the PCU The number of Active Timeslots per site The number of provisioned NSVC per PCU. The recommended number is between 2 and 31 per each provisioned E1 GBL CIR provisioning factor equal to 0.5 100%CS2 100%CS1
Where:
CIR Value n Num_Active TS Num_NSVC
F %CS1 %CS2
Note: Always, (CS1%) + (CS2%) = 100% By using half the number of active timeslots in the CIR calculation, the load of all the active timeslots is served by the combination of the CIR and Bc frame relay network rated capacity. It should be noted that this strategy makes use of the overload carrying capacity of the frame relay network when more than half of the planned active timeslots are in use. When a cell uses some of its standby timeslots as active timeslots, other cells must use fewer of their active timeslots in order for the overall PCU Gb interface bandwidth allocation to be within configured frame relay network interface parameter (CIR, Bc, Be) values. The BSS attempts to utilize as many active timeslots as are supported in PCU hardware and in communication links.
Committed burst rate (Bc)

The Bc is the maximum amount of data (in bits) that the network agrees to transfer, under normal conditions, during a time interval Tc. The Bc value should be configured such that if one of the provisioned E1 links fails, the remaining E1 links can carry the load of the failed link, by operating in the Bc region. For example, with three E1 links are provisioned, if any one of the three should fail, the other two should have the capacity to carry the load of the failed link on the remaining two links, by operating in the Bc region.
Burst excess rate (Be)

The Be is the maximum amount of uncommitted data (in bits) in excess of Bc that a frame relay network can attempt to deliver, during a time interval Tc. The network treats Be data as dicard eligible.
14th Apr 00
549
GSM-001-103
BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links may be added, if required. N+ Where: N nTCH L16 L64 NOTE Refer to Chapter 2, in this manual, for a discussion on TCH planning for the BTS Concentration feature. This formula includes both L16 and L64 to provide necessary number of RSLs. As above, either L16 or L64 RSL can be used, but not both, to a single BTS. is: [(nTCH + L16) / 4] + L64 31 the minimum number of E1 links required (rounded up to an integer). the number of traffic channels at the BTS. the number of 16 kbit/s RSLs (LAPD links). the number of 64 kbit/s RSLs (LAPD links).
BSC-PCU: traffic (GDS TRAU)

Typically, one E1 is provisioned per PCU PRP circuit board to carry GDS TRAU. Each E1 can support up to 124 timeslots that can be a mix of active and standby timeslots. The E1 can carry traffic originating from several different cells. The allocation of timeslots on the E1 is managed by the infrastructure. Each cell can contribute GPRS traffic for up to 8 timeslots.
550
14th Apr 00
GSM-001-103
BSC to BTS T1 interconnect planning actions

Determine the number of T1 links required to connect to a BTS. Redundant links may be added, if required. N+ Where: N nTCH L16 L64 NOTE Refer to Chapter 2, in this manual, for a discussion on TCH planning for the BTS Concentration feature. This formula includes both L16 and L64 to provide necessary number of RSLs. As above, either L16 or L64 RSL can be used, but not both, to a single BTS. is: [(nTCH + L16) / 4] + L64 24 the minimum number of T1 links required (rounded up to an integer). the number of traffic channels at the BTS. the number of 16 kbit/s RSLs (LAPD links). the number of 64 kbit/s RSLs (LAPD links).
14th Apr 00
551
GSM-001-103
Calculate the number of LCFs for RSL processing

LCFs for BSC to BTS links and Layer 3 call processing
There are three steps needed to determine the number of LCF GPROCs required to support the BSC to BTS signalling links (RSL) and layer 3 call processing. 1. 2. 3. Calculate the number of LCFs required to support the RSLs. Calculate the number of LCFs required to support the layer 3 call processing. The larger of the numbers calculated in steps 1 and 2 is the number of LCFs required to support the RSLs signalling links and layer 3 call processing.
Step 1
Determine the number of LCFs required to support RSLs. G RSL + Where: GRSL R B is: (R ) 2 * B) 120
the number of LCFs required to support the BSC to BTS signalling links (RSL). the number RTFs (radio carriers). the number of BTS sites.
Step 2
Determine the number of GPROCs required to support the layer 3 call processing. There are two methods for calculating this number. The first is used when the call parameters are similar to those listed in Table 5-2. The second method is to be used when call parameters differ significantly from those listed in Table 5-2.

G L3 + Where: GL3 n B C is: n ) B ) C * 1 440 15 35 2.5 the number of LCF GPROC2s required to support the layer 3 call processing. the number of TCH at the BSC. the number of BTS sites. the number of cells.
552
14th Apr 00
GSM-001-103

If the call parameters differ significantly from those given in Table 5-2, the alternative formula given below should be used to determine the recommended number of LCFs. G L3 + n * (1 ) 0.7 * S ) 0.5 * H * (1 * 0.3 * i) ) 0.5 * L) ) (0.006 ) 0.02 * P) * B ) C * 1 (11.3 * T) 35 2.5 Where: GL3 n S H i L T P B C NOTE Formula 2 has been calculated using 70% mean utilization of GPROC2. is: the number of LCF GPROC2s required to support the layer 3 call processing. the number of TCHs under the BSC. the ratio of SMSs to calls. the number of handovers per call. the ratio of intra-BSC handovers to all handovers. the location update factor. the average call duration. the paging rate in pages per second. the number of BTS sites. the number of cells.
Step 3
The number of LCFs required is the greater of GRSL and GL3.
LCF GPROC2 provisioning for GPRS signalling

The BSC supports the RSL and layer 3 signalling on the LCF GPROC2 for the GSM circuit switched traffic. The LCF GPROC2 also supports RSL signalling in support of the GPRS signalling traffic. The RSL signalling traffic is carried on 16 kbit/s or on 64 kbit/s timeslot increments over E1 links from the BSC to the BTSs. The provisioning rules for the GSM circuit switched traffic signalling are available in the planning information. This GPRS planning guide provides the LCF GPROC2 provisioning rules for the GPRS portion of RSL signalling that is presented to the BSC from the PCU on the GDS LAPD GSL link(s). The LCF GPROC2 can simultaneously handle signalling traffic from both the GSM and GPRS portions of the network. It is possible to calculate the GPRS portion of the signalling load for the LCF GPROC2 in fractional increments. The GPRS LCF GPROC2 requirements can be directly added to the GSM requirements in order to determine the total number of LCF GPROC2s to equip at a BSC. The MSC can send GSM alerting pages to a GPRS mobile that operates in class A or class B modes. The significance of this is that GPRS mobile stations capable of class A and B operation create a larger population of GSM capable mobile stations that should be considered when provisioning the LCF GPROC2. The planning information should be used for this provisioning. The number of LCF GPROC2s to equip in support of the GPRS signalling load is calculated by using the GL3 formula, previously outlined in step 2, with the appropriate terms set equal to zero. The resulting equation is shown in the following Equation 26.
14th Apr 00
553
GSM-001-103
Equation 26
G L3_GPRS + Where:
G N GPRS *T GPRS_PF GPRS
) (0.006 ) 0.02 * P GPRS) * (B RA_GPRS) ) 2.5 is:
GRPS 35
GL3_GPRS
Number of LCF GPROC2s to handle GPRS related RSL signalling traffic. Number of active GPRS timeslots served at the BSC. GPROC2 GPRS performance factor for RSL processing. Mean duration of a TBF in seconds. Paging rate in pages per second. Number of BTS sites under a BSC. Number of cells under a BSC.
NGPRS
GGPRS_PF
TGPRS PGPRS BRA_GPRS CGPRS
The value for NGPRS is determined using the following MIN function.
Equation 27
N GPRS + MIN[No_PRP_boards * 30, No_GPRS_ts * Mslot_Util_factor] Where: NGPRS is: Number of active GPRS timeslots served at the BSC. Number of PRP boards in the PCU. Number of GPRS timeslots in all of the BTS cells served by the BSC. This is the ratio of the mean number of active timeslots on a GPRS carrier to the total number of provisioned GPRS timeslots on a carrier.
No_PRP_boards No_GPRS_ts
Mslot_Util_factor
Using the figures in the following table, it can be determined that six LCF GPROC2s may be required for a maximally configured PCU.
554
14th Apr 00
GSM-001-103
Table 5-22 Typical values for GPRS LCF GPROC2 provisioning Parameter NGPRS GGPRS_PF TGPRS Value 30 to 300 is the range for the number of active timeslots provisioned at one PCU. 100. 1 second, corresponds to the duration of time to transmit two mean length LLC PDUs at the CS-2 rate. 12, for a fully configured redundant PCU with a 10% paging load based on a mean number of active timeslots equal to 120. 1 to 100 for the number of BTS sites under a BSC. 1 to 250 for the number of cells in a BSC routeing area. 0.5. This number can range from 1 to 10. This number can range from 1 to 300.
PGPRS
BRA_GPRS CGPRS Mslot_Util_factor No_PRP_boards No_GPRS_ts
14th Apr 00
555
Determining the number of MTLs required
GSM-001-103

Introduction
MTLs carry signalling traffic between the MSC and BSC. The number of required MTLs depends upon the BSS configuration size and traffic model. MTLs are carried on E1 or T1 links between the MSC and BSC, which are also used for traffic.
The following factors should be considered when planning the links from the BSC to MSC: S Determine traffic requirements for the BSC. Traffic may be determined using either of the following methods: or Total the traffic potential of each BTS under the BSC; determined by the number of TCHs available, the number of TCHs required or the subscriber potential. Multiply the number of subscribers expected to use the BSC by the average traffic per subscriber.
Determine the number of trunks to support the traffic requirements of the BSC using Erlang B tables at the required blocking rate.
556
14th Apr 00
GSM-001-103

The number of MSC to BSC signalling links (MTL) required depends on the desired link utilization, the type and capacity of the GPROCs controlling the MTLs. C7 uses a 4 bit number, the Signalling Link Selection (SLS), generated by the upper layer to load share message traffic among the in-service links of a link set. When the number of in-service links is not a power of 2, some links may experience a higher load than others. The number of MTLs is a function of the number of MSC to BSC trunks or the offered call load. Table 5-23 give the recommended minimum number of MSC to BSC signalling links based on the typical call parameters given in Table 5-2. The value for N is the greater of the following: S S The offered call load (in Erlangs) from all the BTSs controlled by the BSC. The potential carried load (approximately equal to the number of MSC to BSC trunks).
The offered call load for a BSS is the sum of the offered call load from all of the cells of the BSS. The offered call load at a cell is a function of the number TCHs and blocking. As blocking increases the offered call load increase. For example, for a cell with 15 TCHs and 2% blocking, the offered call load is 9.01 Erlangs. Table 5-23 Number of MSC to BSC signalling links N = the number of MSC to BSC Trunks or the offered load from the BTSs (whichever i greater) ( hi h is t ) N <= 145 145< N <=290 290 < N <= 385 385 < N <= 580 580 < N <= 775 775 < N <= 1160 1160 < N <= 1892 NOTE The capacities shown are based on the standard traffic model shown in Table 5-2. It is recommended that the C7 links be designed to operate at no more than 20% link utilization when the MTL is running on a GPROC, and no more than 35% utilization when the MTL is running on a GPROC2. However, before use of the 35% utilization of GPROC2, it is imperative that the operator verifies that the MSC vendor can also support 35% utilization at the MSC end, if not, then only 20% link utilization should be used for GPROC2. Minimum number of MTLs 1 2 3 4 6 8 16 Recommended number of MTLs 2 3 4 5 7 9 16
(each MTL at <= 20% link utilization)
14th Apr 00
557
GSM-001-103

If the call parameters differ significantly from those given in Table 5-2, the following procedure is used to determine the required number of MSC to BSC signalling links: 1. Use the formula given below to determine the maximum number of Erlangs supported by a C7 signalling link (nllink). nl link + 2. (1000 * U * T) ((67 ) 47 * S ) 31 * H * (1 * 0.8 * i) ) 25 * L) ) 14 * P PC)
Use the formula given below to determine the maximum number of Erlangs supported by a GPROC2 (LCFMTL) supporting a C7 signalling link (nlLCFMTL). 2.5 * (3.6 * T) ((1 ) 0.7 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.5 * L) ) P PC * (0.01 * B ) 0.05))
nl LCF*MTL + 3. 4.
The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is the smaller of the two numbers from Steps 1 and 2. Since the signalling traffic is uniformly distributed over 16 logical links, and these logical links will be assigned to the MTLs (physical links). We need to first determine the amount of traffic each logical link holds (nllogical): nl logical + N 16
5.
Next we need to determine the number of logical links each MTL (physical link) can handle (nlog-per-MTL): n log*per*MTL + ROUND DOWN nl min nl logical
6.
Finally, the number of required MTLs (mtls) is: mtls + ROUND UP 16 n log*per*MTL ) R v 16
NOTE mtls should not exceed 16. Formula 2 has been calculated using 70% mean utilization of GPROC2.
558
14th Apr 00
GSM-001-103
Where:
U T S H i L PPC B mtls ROUND UP ROUND DOWN N
is:
the percent link utilization (for example 0.20). the average call duration. the ratio of SMSs to calls. the number of handovers per call. the ratio of intra-BSC handovers to all handovers. the location update factor. the number of pages per call. the number of BTSs supported by the BSC. the number of MSC to BSC signalling links (MTL). rounding up to the next integer. rounding down to the next integer. the greater of either the offered traffic load or potential carried traffic load (approximately equal to the number of MSC to BSC trunks). the number of MTLs for redundancy.
14th Apr 00
559
GSM-001-103
Calculate the number of LCFs for MTL processing

The purpose of the LCF GPROC2 is to support the functions of MSC link protocol, layer 3 call processing, and the BTS link protocol. It is recommended that an LCF supports either 2 MTLs or 1 to 30 BTSs, with up to 31 RSLs and layer 3 call processing. NOTE It is not recommended that an LCF support both an MTL and BSC to BTS signalling links.
LCFs for MSC to BSC links

Since one LCF GPROC2 can support two MTLs, the number of required LCF is: N LCF + ROUND UP MTLs 2
However, if the traffic model does not conform to the standard model: N LCF + mtls, otherwise: N LCF + ROUND UP Where: NLCF ROUND UP mtls nllink nlLCF-MTL is: mtls 2 if 2 < nl link u nl LCF*MTL
the number of LCF GPROC2s required. rounding up to the next integer. calculated in the previous section. calculated in the previous section. calculated in the previous section.
MSC to BSC signalling over a satellite link

The BSC supports preventative cyclic retransmission (PCR) to interface to the MSC over a satellite link. PCR retransmits unacknowledged messages when there are no new messages to be sent. This puts an additional processing load on the GPROC2 (LCFMTLs) controlling the C7 signalling links. It is recommended that when PCR is used, that the number of MTLs (and thus the number of LCFMTLs) be doubled from the number normally required.
560
14th Apr 00
GSM-001-103
Generic processor (GPROC2)

Introduction
The generic processor (GPROC2) is used throughout the Motorola BSS as a generic control processor board. GPROC2s are assigned functions and are then known by their function names. This section describes the BSC GPROC types and their functions. The BSC configuration type and GPROC device type, are essential factors for BSC planning.
GPROC2 functions and types

The GPROC2 is the basic building block of a distributed architecture. The GPROC2 provides the processing platform for the BSC. By using multiple GPROC2s software tasks can be distributed across GPROC2s to provide greater capacity. The set of tasks that a GPROC2 is assigned, depends upon the configuration and capacity requirements of the BSC. Although every GPROC2 is similar from a hardware standpoint, when a group of tasks are assigned to a GPROC2, it is considered to be a unique GPROC2 device type or function in the BSC configuration management scheme. There are a limited number of defined task groupings in the BSC, which result in the naming of four unique GPROC2 device types for the BSC. The processing requirement of a particular BSC determines the selection and quantity of each GPROC2 device type. The possible general task groupings or functions for assignment to GPROC2s are: S S S S S S S S S BSC common control functions. OMC communications OML (X.25) including statistic gathering. MSC link protocol (C7). BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD). Cell broadcast centre link (CBL).
The defined GPROC2 devices and functions for the BSC are: Base Site Control Processor (BSP). Link Control Function (LCF). Operations and Maintenance Function (OMF). Code Storage Facility Processor (CSFP).
At a combined BSC BTS site the BTF and DHP are additional GPROC2 function and type in the network element.
14th Apr 00
561
GSM-001-103
BSC types
The BSC is configured as one of two types; the type is determined by the GPROCs present. S BSC type 1 Master GPROC2. Running the base site control processor (BSP) and carrying out operations and maintenance functionalities. Link control processor (LCF). Running the radio signalling link (RSL) and layer 3 processing or MTL (C7 signalling link) communications links. S BSC type 2 Master GPROC. Running the BSP. LCF. OMF. Running the O&M, including statistics collection, and OML link (X.25 control links to the OMC-R).
The following factors should be considered when planning the GPROC complement: S Each BSC requires: S One master GPROC2 (BSP). One OMF (if it is a type 2 BSC). A number of LCFs for MTLs, see Link control processor below. LCFs to support the RSL and control of the BTSs.
Optional GPROCs Include: One redundant master GPROC2 (BSP). At least one redundant pool GPROC (covers LCFs). An optional dedicated CSFP.
S S S
A maximum of eight GPROCs can be supported in a BSU shelf. The master GPROC slot (20) in the first shelf should always be populated to enable communication with the OMC-R. For redundancy each BSC should be equipped with a redundant BSP controller and an additional GPROC to provide redundancy for the signalling LCFs. Where multiple shelves exist, each shelf should have a minimum of two GPROCs to provide redundancy within that shelf. System Information: BSS Equipment Planning 68P02900W21-G
14th Apr 00
562
GSM-001-103
Link control function

The following factors should be considered when planning the number of LCFs: S S S MTLs are handled by dedicated LCFs. GPROC2s can handle up to two MTLs. For RSL handling the maximum number of carriers that can be supported by an LCF depends on the number of BTSs controlled by that LCF. The sum of 2 x (the number of BTSs) and the number of carriers cannot exceed 120 for a GPROC2 LCF.
The planning rules for LCFs exclusively using GPROC2 are: S S A single GPROC2 will support two MTLs each working at 20% link utilization. A single GPROC2 will support up to 31 BTS sites and 31 RSLs, limited to the following calculation: 2 * rsls ) carriers v 120 Where carriers = the total number of radios for the BTS site(s). NOTE Combining MTL and RSL processing on a single GPROC2 is not recommended. There is a limit of 30 carriers in a single site (M-Cell6 has a limit of 24 carriers). S S The link utilization of an RSL should not exceed 25%. Up to 17 LCFs can be equipped. NOTE In some cases the software will allow maximums greater than the planning guide, to allow ease of capacity expansion in future releases, but it is not supported with this software release. S A maximum of 31 BTS sites can be controlled by a single LCF. All RSLs (LAPD links) for the BTSs will terminate on the same GPROC2, so if return loops are used the maximum number of BTS sites will be 15 (if GPROC_slots = 31). If the GPROC_slots is set to 16 then at most 15 RSLs may exist which would support up to seven BTS sites. NOTE The number of serial links per GPROC2 must be determined for each site. The current values are 16 or 32 with 16 being the default value. One link is reserved for each board (GPROC test purposes) so the number of available serial links is either 15 or 31.
14th Apr 00
563
GSM-001-103
GPROC2 planning actions

Determine the number of GPROC2s required. N GPROC2 + 2B ) L ) C ) R Where: NGPROC2 B L C R NOTE If dedicated GPROC2s are required for either the CSFP or OMF functions then they should be provisioned separately. is: the total number of GPROC2s required. the number of BSP GPROCs (2B for redundancy). the number of LCF GPROC2s. the number of CSFP GPROCs. the number of pool GPROC2s (for redundancy).
Cell broadcast link

The cell broadcast link (CBL) connects the BSC to the cell broadcast centre. For typical applications (less than ten messages per second), this link can exist on the same LCF as that used to control BTSs. The CBL should not be controlled by a LCFMTL (a GPROC controlling an MTL).
OMF GPROC required

The BSC type 2 configuration offloads many of the O&M functions and control of the interface to the OMC-R from the BSP. One of the major functions off loaded from the BSP is the central statistics process. When determining the total number of statistics, consider the number of instances of that statistic. N ST + (ECS < C) ) (T CS < n) ) SX25LAPD (L ) X ) B) Where: NST ECS C Tcs n SX25LAPD L X B NOTE The formula assumes that the same cell and channel statistics are enabled across all cells. is: the total number of statistics. the number of enabled cell statistics the number of cells. the number of traffic enabled channel statistics. the number of traffic channels. the number of X.25/LAPD statistics. the number of RSLs. the number of OMLs. the number of XBLs
564
14th Apr 00
GSM-001-103

The BSS supports a GPROC acting as the code storage facility processor (CSFP). The CSFP allows pre-loading of a new software release while the BSS is operational. If a dedicated GPROC is to exist for the CSFP, an additional GPROC will be required. When M-Cell BTSs are connected to the BSC, a dedicated CSFP is required at the BSC and a second dedicated CSFP should be equipped for redundancy. The BSS supports a method whereby a dedicated CSFP GPROC is not required. This method is called configure CSFP and works as follows: The system can borrow certain devices and temporarily convert them into a CSFP, and when the CSFP functionality is no longer needed the device can be converted back into its previous device. The devices the system can borrow are a redundant BSP/BTP or a pooled GPROC2. This functionality allows an operator who already has either a redundant BSP/BTP or a pooled GPROC2 in service to execute a command from the OMC-R to borrow the device and convert it into a CSFP. The operator can then download the new software load or database and execute a CSFP swap. Once the swap has been completed and verified as successful, the operator can return the CSFP back to the previous redundant or pooled device type via a separate command from the OMC-R. See the Technical Description: BSS/RXCDR (GSM-100-323A) or Service Manual: BSC/RXCDR (GSM-100-030) for more details.
GPROC redundancy
BSP redundancy
The failure of the BSP GPROC2 will cause a system outage. If the BSC is equipped with a redundant BSP GPROC2, the system will restart under the control of the redundant BSP GPROC2s. If the BSC is not equipped with a redundant BSP and the BSP GPROC2 were to fail, the BSC would be inoperable.
Pooled GPROC2s for LCF and OMF redundancy

The BSS supports pooled GPROC2s for LCF and OMF redundancy. By equipping additional GPROC2s for spares, if an LCF or the OMF GPROC2 were to fail, the system software will automatically activate a spare GPROC2 from the GPROC2 pool to replace the failed GPROC2.
14th Apr 00
565
Transcoding
GSM-001-103
Transcoding
Introduction
Transcoding reduces the number of cellular subscriber voice/data trunks required by a factor of four. If transcoding takes place at the switch using a RXCDR, the number of links between the RXCDR and the BSC is reduced to approximately one quarter of the number of links between the RXCDR and the MSC. The capacity of one BSU shelf is 12 MSI slots, six of which may contain a transcoder (XCDR) or generic DSP processor (GDP); this limitation is due to power constraints. An RXU shelf can support up to 16 GDP/XCDRs or GDPs and typically provides a better solution of the transcoding function for larger commercial systems. Refer to the section Remote transcoder planning overview in Chapter 6.
GDP/XCDR planning considerations

The following factors should be considered when planning the GDP/XCDR complement: S A GDP/XCDR can process 30 voice channels (GDP-E1/XCDR) or 24 voice channels (GDP-T1), will support enhanced full rate speech, uplink/downlink volume control and is capable of terminating one E1 or T1 link from the MSC. The master MSI slot(s) should always be populated to enable communication with OMC-R. The master MSI slot may contain a GDP/XCDR, if the OML goes through the MSC. The A interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1 links; whereas an XCDR can only terminate E1 links (refer to T1 conversions below). NOTE The fitting of a GDP in place of an XCDR does not effect the planning calculations for E1 links. For T1 links an MSI-2 is not required.
566
14th Apr 00
GSM-001-103
Transcoding
T1 conversion
T1 to E1 conversion is needed for XCDR, but not for GDP. When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done in one of two ways. In either case the conversion may be part of an existing network element or a standalone network element which would appear as a RXCDR.
Without KSW switching

A single MSI-2 can be programmed to be E1 on one port and T1 on the other. This is the simplest method, but uses at most 23 of the transcoding circuits on the XCDR. This method has no impact on the TDM bus ports, but does require MSI slots. This method requires the number of GDP/XCDRs and additional MSI-2s to be equal to the number of T1 links.
With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1 circuits may be done. This uses the ability of the KSW to switch between groups using nailed connections. Although more efficient in XCDR utilization, this method may cause additional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2s needed for T1 to E1 conversion is: m= Where: m T E is: T+E 2
the number of MSI-2s required for T1 to E1 conversion. the number of T1 circuits required. the number of E1 circuits required.
14th Apr 00
567
Transcoding
GSM-001-103
Planning actions for transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the number of E1 or T1 links for the A interface. This text should be read in conjunction with the BSS planning diagram Figure 5-1.
Using E1 links
The minimum number of E1 links required is the greater of two calculations that follow (fractional values should be rounded up to the next integer value). N= T 30 N= Where: N C X T is: C+ X+ T 31
the minimum number of E1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC-R) through the MSC. the number of trunks between the MSC and the BSC.
Using T1 links
The minimum number of T1 links required is the greater of two calculations that follow (fractional values should be rounded up to the next integer value). N= T 23 N= Where: N C X T is: C+ X+ T 24
the minimum number of T1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC-R) through the MSC. the number of trunks between the MSC and the BSC.
568
14th Apr 00
GSM-001-103
Multiple serial interface (MSI, MSI-2)

Introduction
A multiple serial interface provides the interface for the links between a BSSC cabinet and other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI can interface only E1 links, an MSI-2 can interface both E1 and T1 links, but not simultaneously.
The following factors should be considered when planning the transcoder complement: S S Each MSI can interface two E1 links. Each MSI-2 can interface two T1 links. NOTE Although the MSI-2 is configurable to support either E1 or T1 on each of its two ports, it is not recommended for E1 systems. S S S S Each E1 link provides 31 usable 64 kbit/s channels. Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2. Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links connected to the site. The master MSI slot(s) should always be populated to enable communication with OMC-R. If the OML links go directly to the MSC the master slot should be filled with an GDP/XCDR, otherwise the slot should be filled with an MSI/MSI-2 which terminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 links do not need to go directly to the OMC-R, they may go to another network element for concentration.
14th Apr 00
569
GSM-001-103
MSI/MSI-2 planning actions

The following formulae assume local transcoding. Refer to Chapter RXCDR planning steps and rules for MSI planning formulae for remote transcoding.
With E1 links
Determine the number of MSIs required. M= B 2 Where: M B is: the number of MSIs required. the number of BSC to BTS links.
With T1 links
Determine the number of MSI-2s required. M = B)m 2 Where: M B m is: the number of MSI/MSI-2s required. the number of BSC to BTS links. the number of MSI/MSI-2s used for T1 to E1 conversion.
570
14th Apr 00
GSM-001-103
Kiloport switch (KSW)

Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the BSC.
The following factors should be considered when planning the KSW complement: S S A minimum of one KSW is required for each BSC site. The KSW capacity of one thousand and twenty four 64 kbit/s ports can be expanded by adding up to three additional KSWs, giving a total switching capacity of four thousand and ninety six 64 kbit/s ports of which, eight timeslots are reserved by the system for test purposes and are not available for use. For planning purposes assume fourteen MSI maximum per KSW. Each MSI may be replace with four GDP/XCDRs. Using twelve MSIs per KSW may reduce the number of shelves required at a cost of additional KSWs. For example, a BSC with 28 MSIs could be housed in three shelves with three KSW modules or four shelves with two KSW modules. Verify that each KSW uses fewer than 1016 ports. There are three devices in a BSC that require TDM timeslots. They are: GPROC = 16 Timeslots. GPROC2 = 32 (or 16) Timeslots. GDP or XCDR = 16 Timeslots. MSI/MSI-2 = 64 Timeslots. The number of TDM timeslots is given by. N = (G * n) + (R * 16) + (M * 64) Where: N G n R M is: the number of timeslots required. the number of GPROC2s. 16 or 32 (depending on the value of the gproc_slots database parameter). the number of GDP/XCDRs. the number of MSI/MSI-2s (do not count MSI-2s which are doing on board E1 to T1 conversion, when determining TDM bandwidth).
S S
For redundancy, duplicate all KSWs. NOTE Any BSC site which contains a DRIM has 352 timeslots allocated to DRIMs irrespective of the number of DRIMs equipped.
14th Apr 00
571
GSM-001-103
KSW planning actions

Determine the number of KSWs required: N= Where: N G n R M is: (G * n) + (R * 16) + (M * 64) (1016) the number of KSWs required. the number of GPROC2s. 16 or 32 (depending on the value of the gproc_slots database parameter). the number of GDP/XCDRs. the number of MSI/MSI-2s (do not count MSI-2s which are doing on board E1 to T1 conversion).
572
14th Apr 00
GSM-001-103
BSU shelves
BSU shelves
Introduction
The number of BSU shelves is normally a function of the number of GPROC/GPROC2, MSI/MSI-2s and GDP/XCDRs required.
The following factors should be considered when planning the number of BSU shelves: S S Each BSU shelf supports up to eight GPROCs or GPROC2s, if the number of these exceed the number of slots available an additional BSU shelf is required. Each shelf is allocated to a single KSW and extension shelves are differentiated by the presence of the KSW; extension shelves are those which do not contain a primary KSW. A BSU shelf can support up to 12 MSI/MSI-2 boards. A BSU shelf can support up to six GDP/XCDRs boards. (reducing appropriately, the number of MSI/MSI-2 boards).
S S
BSU shelf planning actions

Determine the number of BSU shelves required. The number of BSU shelves required is the greater of three calculations that follow (fractional values should be rounded up to the next integer value). Bs = G 8 Bs = M+ R 12
Bs = R 6 Where: Bs G M R is: the minimum number of BSU shelves required. the number of GPROC/GPROC2s. the number of MSI/MSI-2s. the number of GDP/XCDRs.
NOTE The number of shelves may be larger if an attempt to reduce the number of KSWs is made. The number of shelves (cages) = 134 The number of cabinets = 170 There is a database limitation of 50 cabinets/shelves. M-Cell sites do not require a cage to be equipped, only a cabinet.
14th Apr 00
573
Kiloport switch extender (KSWX)
GSM-001-103

Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element grows beyond a single shelf.
The following factors should be considered when planning the KSWX complement: S S For redundancy, duplicate all KSWX boards (requires redundant KSW). KSWXs are used in three modes: KSWX E (Expansion) are required to interconnect the KSWs for sites with multiple KSWs. KSWX R (Remote) are required in shelves with KSWs to drive the TDM highway in shelves that do not have KSWs. KSWX L (Local) are used in shelves that have KSWs to drive the clock bus in that shelf and in shelves that do not not KSWs to drive both the local TDM highway and the clock bus in that shelf.
S S
Five of the redundant KSWX slots are also CLKX slots. The maximum number of KSWX slots per shelf is 18, nine per KSW.
KSWX planning actions

The number of KSWXs required is the sum of the KSWXE, KSWXL and KSWXR. N KX + NKXE ) NKXR ) NKXL N KXE + K < (K * 1) N KXR + SE N KXL + K ) S E Where: NKX NKXE NKXR NKXL K SE NOTE Ensure that SE = 0 for extension shelves and 1 for expansion shelves. is: the number of KSWX required. the number of KSWXE. the number of KSWXR. the number of KSWXL. the number of non-redundant KSWs. the number of extension/expansion shelves.
574
14th Apr 00
GSM-001-103
For example:
Table 5-24 KSWX (non-redundant) Extension shelves 0 1 2 3 4 KSW (non redundant) 1 1 3 5 7 9 2 4 6 8 10 12 3 9 11 13 15 17 4 16 18 20 22 24
Table 5-25 KSWX (redundant) Extension shelves 0 1 2 3 4 KSW (redundant) 1 2 6 10 14 18 2 8 12 16 20 24 3 18 22 26 30 34 4 32 36 40 44 48
14th Apr 00
575
Generic clock (GCLK)
GSM-001-103

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a BSU.
The following factors should be considered when planning the GCLK complement: S S S One GCLK is required at each BSC. The maximum number of GCLK slots per shelf is two. For redundancy add a second GCLK at each BSC in the same shelf as the first GCLK.
GCLK planning actions

Determine the number of GCLKs required. GCLKs = 1 + 1 redundant.
576
14th Apr 00
GSM-001-103
Clock extender (CLKX)

Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one BSU.
The following factors should be considered when planning the CLKX complement: S S S One CLKX is required in the first BSU shelf, which contains the GCLK, when expansion beyond the shelf occurs. Each CLKX can supply the GCLK signals to six shelves. There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension only allows fourteen shelves in a single network element). The maximum number of CLKX slots per shelf is six. NOTE The CLKX uses six of the redundant KSWX slots. S S With a CLKX, a KSWXL is required to distribute the clocks in the master and each of the expansion/extension cages. For redundancy, duplicate each CLKX (requires a redundant GCLK).
CLKX planning actions

Determine the number of CLKXs required. N CLKX + ROUND UP Where: NCLKX ROUND UP E RF is: E * (1 ) R ) F 6
the number of CLKX required. rounding up to the next integer. the number of expansion/expension shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
14th Apr 00
577
LAN extender (LANX)
GSM-001-103
LAN extender (LANX)

Introduction
The local area network extender (LANX) provides a LAN interconnection for communications between all GPROCs at a site.
The following factors should be considered when planning the LANX complement: S S S One LANX is supplied in each shelf. For full redundancy add one LANX for each shelf. The LANX can support a maximum network size of 14 shelves.
LANX planning actions

Determine the number of LANXs required. N LANX + NBSU * (1 ) R F) Where: NLANX NBSU RF is: the number of LANX required. the number of BSU shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
BSU 14
578
14th Apr 00
GSM-001-103
Parallel interface extender (PIX)

Introduction
The parallel interface extender (PIX) provides eight inputs and four outputs for site alarms.
The following factors should be considered when planning the PIX complement: S S The maximum number of PIX board slots per shelf is two. The maximum number of PIX board slots per site is eight.
PIX planning actions

Choose the number of PIXs required. PIX 2 * number of BSUs. or PIX 8.
14th Apr 00
579
Line interfaces (BIB, T43)
GSM-001-103

Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide impedance matching for E1 and T1 links.
The following factors should be considered when planning the line interface complement: S S S S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line use a BIB. To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line use a T43 Board (T43). Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf. Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet A maximum of 24 E1/T1 links can be connected to a BSU shelf. A BSSC2 cabinet with two BSU shelves can interface 48 E1/T1 links.
BIB/T43 planning actions

The following planning actions are required: S S Determine the number and type of link (E1 or T1) to be driven. Determine the number of BIBs or T43s required. Number of MSIs Number of E1/T1 links = 3 6
Minimum number of BIBs or T43s =
580
14th Apr 00
GSM-001-103
Digital shelf power supply

Introduction
A BSSC cabinet can be supplied to operate from either a +27 V dc or 48/60 V dc power source.
The following factors should be considered when planning the PSU complement: S S S S Two DPSMs are required for each shelf in the BSSC. Two IPSMs are required for each shelf in the BSSC2 (48/60 V dc). Two EPSMs are required for each shelf in the BSSC2 (+27 V dc). For redundancy, add one DPSM, IPSM, or EPSM for each shelf.
Power supply planning actions

Determine the number of PSUs required. PSUs = 2 * Number of BSUs + R F * Number of BSUs Where: RF is: Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
14th Apr 00
581
Battery backup board (BBBX)
GSM-001-103

Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an external battery to maintain power to the GPROC2 DRAM and the optical circuitry on the LANX in the event of a mains power failure.
The following factors should be considered when planning the BBBX complement: S One BBBX is required per shelf; if the battery backup option is to be used.
BBBX planning actions

Determine the number of BBBXs required. BBBX = number of BSUs for battery backup (recommended). BBBX = 0 if no battery backup required.
582
14th Apr 00
GSM-001-103
Verify the number of BSU shelves and BSSC2 cabinets

Verification
After planning is complete, verify that: S S S S S S S S S S S The number of shelves is greater than one eighth the number of GPROC2 modules. Each non-redundant KSW has its own shelf. Each extension shelf supports extension of a single KSW. The number of KSWX, LANX, CLKX, and GPROC2s is correct. The number of MSI/MSI-2 and GDP/XCDR 12 * number of shelves. The number of GDP/XCDR 6 * number of shelves. The number of BTS sites 100 The number of BTS cells 250 RSLs. 250 Carriers. 384 Erlangs. 1892 If necessary, add extra BSU shelves. Each BSSC2 cabinet supports two BSU shelves.
14th Apr 00
583
GSM-001-103
584
14th Apr 00
Chapter 6
RXCDR planning steps and rules
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 6 RXCDR planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote transcoder planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR to BSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR to MSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 62 62 63 64 64 65 65 66 66 66 66 67 67 67 67 68 68 68 69 610 610 610 611 612 612 612 612 613 613 613 613 614 614 614 614 615 615 615 615 616 616 616 616 617 617 617 617
14th Apr 00
iii
GSM-001-103
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of RXU shelves and BSSC cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
618 618 618 618 619 619 619 619 620 620 620 620 621 621 621 621 622 622
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides the planning steps and rules for the RXCDR. This chapter contains: S S RXCDR planning overview. RXCDR planning. Planning rules for RXCDR to BSC links. Planning rules for RXCDR to MSC links. Planning rules for the digital modules. Planning rules for the digital shelf power supply.
14th Apr 00
61
Remote transcoder planning overview
GSM-001-103

Introduction
To plan the equipage of an RXCDR, certain information must be known. The major items include: S S S S S S The BSC traffic requirements. The number of trunks (including redundancy) from the MSC. Each RXCDR may support multiple BSCs. The sum of the MSI/MSI-2s and the XCDR/GDPs for each BSC define the number of slots required at the RXCDR. The use of E1 or T1 links. The use of balanced or unbalanced E1.
62
14th Apr 00
GSM-001-103

Planning a RXCDR involves the following steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. Plan the number of links between the XCDR and BSC site(s), refer to the section RXCDR to BSC links in this chapter. Plan the number of E1 or T1 links between the RXCDR and MSC site(s), refer to the section RXCDR to MSC links in this chapter. Plan the number of GPROCs required, refer to the section Generic processor (GPROC, GPROC2) in this chapter.
Plan the number of GDP/XCDRs required, refer to the section Transcoding

in this chapter.
Plan the number of MSI/MSI-2s required, refer to the section Multiple serial
interface (MSI, MSI-2) in this chapter. Plan the number of KSWs and timeslots required, refer to the section Kiloport switch (KSW) in this chapter. Plan the number of RXU shelves, refer to the section RXU shelves in this chapter. Plan the number of KSWXs required, refer to the section Kiloport switch extender (KSWX) in this chapter. Plan the number of GCLKs required, refer to the section Generic clock (GCLK) in this chapter. Plan the number of CLKXs required, refer to the section Clock extender (CLKX) in this chapter. Plan the number of LANXs required, refer to the section LAN extender (LANX) in this chapter. Plan the number of PIXs required, refer to the section Parallel interface extender (PIX) in this chapter. Plan the number of BIB or T43s required, refer to the section Line interfaces (BIB, T43) in this chapter. Plan the power requirements, refer to the section Digital shelf power supply in this chapter. Plan the number of BBBXs required, refer to the section Battery backup board (BBBX) in this chapter. Verify the planning process, refer to the section Verify the number of RXU shelves and BSSC cabinets in this chapter.
14th Apr 00
63
RXCDR to BSC links
GSM-001-103
RXCDR to BSC links

Introduction
The number of E1 or T1 links between the RXCDR and the BSCs is the number required to support the A interface from the RXCDR to the BSC. This text should be read in conjunction with the BSS planning diagram, Figure 6-1.
MSC TRANSCODER

64
14th Apr 00
GSM-001-103
RXCDR to BSC links
E1 interconnect planning actions

Determine the number of E1 links required. N= Where: N C X B64 T B16 NOTE Each E1 link carries up to 120 trunks with a signalling link or 124 trunks without a signalling link. Redundant E1 links carrying extra trunks may be added. C + X + B64 + (T + B16) / 4 31 is: the minimum number of E1 links required. the number of C7 signalling links to the MSC. the number of OML links (X.25 control links to the OMC) through the RXCDR. the number of 64 kbit/s XBL links. the number of trunks between the MSC and the BSC. the number of 16 kbit/s XBL links.
T1 interconnect planning actions

Determine the number of T1 links required. N= Where: N C X B64 T B16 NOTE Each T1 link carries up to 92 trunks with a signalling link or 96 trunks without a signalling link. Redundant E1 links carrying extra trunks may be added. C + X + B64 + (T + B16) / 4 24 is: the minimum number of T1 links required. the number of C7 signalling links to the MSC. the number of OML links (X.25 control links to the OMC) through the RXCDR. the number of 64 kbit/s XBL links. the number of trunks between the MSC and the BSC. the number of 16 kbit/s XBL links.
14th Apr 00
65
RXCDR to MSC links
GSM-001-103
RXCDR to MSC links

Introduction
The number of E1 or T1 links between the RXCDR and the MSC is the number required to support the A interface from the RXCDR to the MSC.
E1 interconnect planning actions

Determine the number of E1 links required. The minimum number of E1 links required is the greater of two calculations that follow (fractional values should be rounded up to the next integer value). N= Where: N C X T is: C+ X+T 31
the minimum number of E1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC) through the MSC. the number of trunks between the MSC and the BSC.
T1 interconnect planning actions

Determine the number of T1 links required. N= Where: N C X T is: C+ X+T 24
the minimum number of T1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC) through the MSC. the number of trunks between the MSC and the BSC.
66
14th Apr 00
GSM-001-103
Generic processor (GPROC, GPROC2)

Introduction
Generic processors (GPROC, GPROC2) are used throughout the Motorola BSS as a generic control processor.
The following factors, for GPROCs at the RXCDR, should be considered when planning the GPROC, GPROC2 complement: S S Each shelf requires at least one GPROC, GPROC2; plus one for redundancy. A maximum of two GPROC, GPROC2s per shelf are supported.
GPROC planning actions

An RXCDR should have: S S S One BSP GPROC or GPROC2 per shelf. One BSP GPROC or GPROC2 for redundancy. One optional CSFP.
The factors described in the planning considerations section should be taken into account in this planning. NOTE In a transcoder either GPROC or GPROC2 can be used.
14th Apr 00
67
Transcoding
GSM-001-103
Transcoding
Introduction
Transcoders (XCDR) provide the interface for the E1 (or converted T1) links between the MSC and the BSC. The XCDR performs the transcoding/rate adaption function which converts the information on the trunks to 16 kbit/s. Figure 6-2 shows sub-multiplexing and speech transcoding at the RXCDR. S S Each Trunk requires a quarter (1/4th) of a 64 kbit/s circuit between the RXCDR and BSC. Each control link (RSL, OML,XBL,C7) requires one 64 kbit/s circuit. (RSL and XBL have the option of using 16 kbit/s circuits)
RXCDR M S C X K M C S S D W I R / M S I 2
BSC M S I / M S I 2 K S W M S I / M S I 2
M-CELL BTS N I U M C U T C U
ONE RF CARRIER
64 kbit/s ALAW TRUNKS
4 TRUNKS PER 64 kbit/s CIRCUIT
64 kbit/s 4 TCHs
THE XCDR TRANSCODES 64 kbit/s ALAW PCM TO/FROM 13 kbit/s MAPPED ONTO 16 kbit/s, AND SUBMULTIPLEXES 4 TRUNKS TO/FROM 1 X 64 kbit/s CIRCUIT.
THE KSW SUBRATE SWITCHES 16 kbit/s TIMESLOTS.
8 x 22.8 kbit/s TIMESLOTS THE TCU ENCODES/DECODES 13 kbit/s TO/FROM 22.8 kbit/s FOR 8 TIMESLOTS, AND SUBMULTIPLEXES 4 (13 kbit/s MAPPED ON 16 kbit/s) TIMESLOTS ONTO 1 x 64 kbit/s CIRCUIT, OR THE OTHER WAY AROUND. .
Figure 6-2 Sub-multiplexing and speech transcoding at the RXCDR

68
14th Apr 00
GSM-001-103
Transcoding
T1 conversion
T1 to E1 conversion is needed for XCDR, but not for GDP. When required MSI-2s can be used to provide T1 to E1 conversion. This can be done in one of two ways. In either case the conversion may be part of an existing network element or a standalone network element which would appear as a RXCDR.

A single MSI-2 can be programmed to be E1 on one port and T1 on the other. This is the simplest method but uses at most 23 of the transcoding circuits on the XCDR. This method has no impact on the TDM bus ports, but does require MSI slots. This method requires the number of GDP/XCDRs and additional MSI-2s to be equal to the number of T1 links.
With KSW switching

For better utilization of the GDP/XCDRs a mapping of five T1 circuits onto four E1 circuits may be done. This uses the ability of the KSW to switch between groups using nailed connections. Although more efficient in XCDR utilization, this method may cause additional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2s needed for T1 to E1 conversion is: m= Where: m T E is: T+E 2
14th Apr 00
69
GSM-001-103

Introduction
A multiple serial interface provides the interface for the links between a RXCDR site and other network entities, RXCDR to OMC-R and RXCDR to BSC. An MSI can interface only E1 links, an MSI-2 can interface both E1 and T1 links.
The following factors should be considered when planning the transcoder complement: S S Each MSI can interface two E1 links. Each MSI-2 can interface two E1/T1 links. NOTE Although the MSI-2 is configurable to support either E1 or T1 on each of its two ports, it is not required for E1 systems. S S S S Each E1 link provides 31 usable 64 kbit/s channels. Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2. Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links connected to the site. When one remote transcoder site is supporting multiple BSCs, each BSC requires its own E1 interface(s) as follows: The number of MSI/MSI-2s should be equal to half the number of RXCDR to BSC E1 or T1 links. Redundancy requires additional links and MSI/MSI-2s. If the OMLs (X.25 links) do not go through the MSC, a dedicated E1 or T1 link (half an MSI/MSI-2) is required for the X.25 links to the OMC. At least one MSI/MSI-2 is required for every eight GDP/XCDR modules. Additional MSI/MSI-2s will be used if the links are not fully occupied. If the XCDR is using all 30 ports in a T1 network, use one MSI-2 for approximately every ten GDPs. Additional E1 or T1 links may be required to concentrate X.25 links from other network entities. Each BSC may use one to four 64 kbit/s or 16 kbit/s channels for XBL fault management communications. Reference should be made to Technical Description: BSS/RXCDR (GSM-100-323A) or Service Manual: BSC/RXCDR (GSM-100-030) for more details.
The master MSI slot(s) should always be populated to enable communication with OMC-R. If the OML links go directly to the MSC, the master slot should be filled with an XCDR, otherwise the slot should be filled with an MSI/MSI-2 which terminates the E1/T1 link caring the OML link to the OMC-R. These E1/T1 links do not need to go directly to the OMC-R, they may go to another network element for concentration.
610
14th Apr 00
GSM-001-103
MSI planning actions

With E1 links
Determine the number of MSI or MSI-2s required. N MSI + Where: NMSI NBSC is: NBSC 2
the number of MSIs required. the number of E1 links required. (as N calculated in RXCDR to BSC links in this chapter)
With T1 links
If MSI-2s are used, T1 to E1 conversion is not needed. Therefore the number of MSI-2s required is: N MSI + Where: NMSI NBSC is: NBSC 2
the number of MSIs required. the number of E1 links required. (as N calculated in RXCDR to BSC links in this chapter)
If MSIs are used, conversion becomes necessary. Therefore the number of MSIs required is: N MSI + Where: NMSI NBSC is: NBSC )m 2
the number of MSIs required. the number of E1 links required. (as N calculated in RXCDR to BSC links in this chapter) the number of MSI-2s used for T1 to E1 conversion.
14th Apr 00
611
GSM-001-103

Introduction
The kiloport switch (KSW) provides digital switching for the TDM highway of the RXU.
The following factors should be considered when planning the kiloport switch complement: S S A minimum of one KSW is required for each RXU site. The KSW capacity of one thousand and twenty four 64 kbit/s ports or four thousand and ninety six 16 kbit/s ports can be expanded by adding up to three additional KSWs, giving a total switching capacity of four thousand and ninety six 64 kbit/s ports or sixteen thousand three hundred and eighty four 16 kbit/s ports. One KSW can provide switching for two fully occupied shelves with 16 GDP/XCDRs and up to three MSI/MSI-2s each. If more than one XCDR is exchanged for an MSI/MSI-2s, each shelf will require its own KSW. For redundancy, duplicate all KSWs. Verify that each KSW uses fewer than 1016 ports. There are three devices in a RXCDR that require TDM timeslots. They are: GPROC = 16 Timeslots. GPROC2 = 32 (or 16) Timeslots. GDP or XCDR = 16 Timeslots. MSI/MSI-2 = 64 Timeslots.
S S

The following planning actions are required: S Determine the number of KSWs required. N= Where: N G n R M is: (G * n) + (R * 16) + (M * 64) (1016) the number of KSWs required. the number of GPROC/GPROC2s. 16 or 32 (depending on the value of the GPROC_slot database parameter). the number of GDP/XCDRs. the number of MSI/MSI-2s (do not count MSI-2s which are doing on board E1 to T1 conversion).
612
14th Apr 00
GSM-001-103
RXU shelves
RXU shelves
Introduction
The number of RXU shelves is normally a function of the number of MSI/MSI-2s and GDP/XCDRs required.
The following factors should be considered when planning the number of RXU shelves: S Each shelf is allocated to a single KSW and shelves are differentiated by the presence of the KSW; extension shelves are those which do not contain a primary KSW. Two shelves each equipped with three MSI/MSI-2s and 16 GDP/XCDRs can be served by a single KSW. If each shelf has five MSI/MSI-2s with 14 GDP/XCDRs the KSW can serve only one shelf, and two KSWs will be required.
RXU shelf planning actions

Determine the number of RXU shelves required. R X + max M 5 Where: Rx M R is: , R 16
the minimum number of RXU shelves required. the number of MSI/MSI-2s. the number of GDP/XCDRs.
14th Apr 00
613
GSM-001-103

Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a RXU to other RXUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element grows beyond a single shelf.
S S
Five of the redundant KSWX slots are also CLKX slots. The maximum number of KSWX slots per shelf is 18, 9 per KSW.

The number of KSWXs required is the sum of the KSWXE, KSWXL, and KSWXR. N KX + NKXE ) NKXR ) NKXL N KXE + K < (K * 1) N KXR + SE N KXL + K ) S E Where: NKX NKXE NKXR NKXL K SE NOTE Ensure that SE = 0 for extension shelves and 1 for expansion shelves. is: the number of KSWX required. the number of KSWXE. the number of KSWXR. the number of KSWXL. the number of non-redundant KSWs. the number of extension/expansion shelves.
614
14th Apr 00
GSM-001-103

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a RXU.
The following factors should be considered when planning the GCLK complement: S S S One GCLK is required at each RXCDR. A second GCLK is optionally requested for redundancy. Both GCLKs must reside in the same shelf of the RXCDR.

14th Apr 00
615
GSM-001-103

Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one RXU.
The following factors should be considered when planning the CLKX complement: S S S One CLKX is required in the first RXU shelf, which contains the GCLK, when expansion beyond the shelf occurs. Each CLKX can supply the GCLK signals to six shelves. There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension only allows fourteen shelves in a single network element). The maximum number of CLKX slots per shelf is six. NOTE The CLKX uses six of the redundant KSWX slots. S S With a CLKX, a KSWXL is required to distribute the clocks in the master and each of the expansion/extension cages. For redundancy, duplicate each CLKX (requires a redundant GCLK).

Determine the number of CLKXs required. N CLKX + ROUND UP Where: NCLKX ROUND UP E RF is: E * (1 ) R ) F 6
the number of CLKX required. rounding up to the next integer. the number of shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
616
14th Apr 00
GSM-001-103
LAN extender (LANX)
LAN extender (LANX)

Introduction

Determine the number of LANXs required. N LANX + NRXU * (1 ) R F) Where: NLANX NRXU RF is: the number of LANX required. the number of RXU shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
RXU 14
14th Apr 00
617
GSM-001-103

Introduction

Determine the number of PIXs required. PIX 2 * number of RXUs. or PIX 8.
618
14th Apr 00
GSM-001-103

Introduction
The following factors should be considered when planning the line interface complement: S S S S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line use a BIB. To match a single ended 75 ohm 2.37 V (peak pulse) line use a T43 Board (T43). Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf. All E1/T1 links must be terminated, including the links which are fully contained in the cabinet, for example, between RXU and BSU or links used for T1 to E1 conversion. Up to four BIBs or T43s per shelf can be mounted on a BSSC cabinet A maximum of 24 E1/T1 links can be connected to a RXU shelf. A BSSC cabinet with two RXU shelves can interface 48 E1/T1 links.

The following planning actions are required: S S Determine the number and type of link (E1 or T1) to be driven. Determine the number of BIBs or T43s required. Minimum number of BIBs or T43s = Number of E1/T1 links 6
14th Apr 00
619
GSM-001-103

Introduction
The following factors should be considered when planning the PSM complement: S S S S Two DPSMs are required for each shelf in the BSSC/RXCDR. Two IPSMs are required for each shelf in the BSSC2/RXCDR (48/60 V dc). Two EPSMs are required for each shelf in the BSSC2/RXCDR (+27 V dc). For redundancy, add one DPSM, IPSM or EPSM for each shelf.

Determine the number of PSMs required. PSUs = 2 * Number of BSUs + R F * Number of BSUs Where: RF is: Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
620
14th Apr 00
GSM-001-103

Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an external battery to maintain power to the GPROC DRAM and the optical circuitry on the LANX in the event of a mains power failure.
The following factors should be considered when planning the BBBX complement: S One BBBX is required per shelf.

14th Apr 00
621
Verify the number of RXU shelves and BSSC cabinets
GSM-001-103
Verify the number of RXU shelves and BSSC cabinets

Verification
After planning is complete, verify that: S S S Each non-redundant KSW has its own shelf. Each extension shelf supports extension of a single KSW. The number of KSWX, LANX, CLKX, and GPROCs is correct.
If necessary, add extra RXU shelves. Each BSSC cabinet supports two RXU shelves.
622
14th Apr 00
Chapter 7
OMC-R planning steps and rules
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 7 OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Authorized OMC-R configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6560 planning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC-R server and workstation composition . . . . . . . . . . . . . . . . . . . . .
i
71 71 71 71 72 73 76
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
Authorized OMC-R configurations

Introduction
The purpose of this chapter is to enable the customer to correctly select the items that constitutes an OMC-R Scaleable system, depending on their current configuration.
Terminology
In order to avoid confusion, certain terms used are described. These are not mutually exclusive and may be combined.
Expansion
This is where the system size is increased, usually to improve capacity (for example, from low-end to high-end).
Upgrade
This is where the software is upgraded (for example, GSR3 to GSR4). There may be an associated hardware upgrade at the same time.
Capacity
The OMC-R is capable of supporting the following: Table 7-1 Capacities OMC-R Low-end High-end TCH < 5,000 > 5,000 NE 16 120
In calculating the capacity of the OMC-R; whichever limit is reached first (traffic channel (TCH) or network element (NE)) will determine the size of the OMC-R.
14th Apr 00
71
GSM-001-103

Planning an OMC-R configuration involves the following steps: 1. 2. 3. 4. 5. 6. 7. Select the appropriate server. Select the appropriate level of initial program load (IPL) software. Select the ancillaries according to the country of use. Choose the appropriate data communications interface. Select the quantities of optional items required. Ensure that the order quantities are correct according to the product structure. Expand software maintenance program, as required.
Assumptions
Certain assumptions have been made which may not reflect the actual circumstances for each configuration. the assumptions made are as follows: S A Low-end to High-end hardware expansion configuration will require the IPLs to be at Low-end, as a minimum. NOTE 1. 2. 3. The server at GSR4 will include the MIB functionality. The Codex 6560 is now known as 6560 Multi Protocol Router (MPR). The 6560 MPR is software configurable for either 75 ohms or 120 ohms.
72
14th Apr 00
GSM-001-103
Example
Table 7-2 is an example of an order for a Low-end system, with two MMIs as an option, using UK server country kit, a new 6560 MPR, an OMC-R Map 1 and an IPL of 2,500 TCH. Table 7-2 Example order Order number SWDN5025 SWDN5027 SWDN5028 SWDN5029 SWLN3602 SWDN5039 SWDN4894 SWLN3567 SWDN5051 SWDN4740 EUR8880 Equipment Server hardware, Low-end OMC-R Scaleable IPL 0 499 TCH OMC-R Scaleable IPL 500 1000 TCH OMC-R Scaleable IPL 1000 2500 TCH MMI workstation hardware Thinnet ethernet adapter kit Sunlink HSI interface 6560 MPR (30 timeslots) Server country kit (modem, keyboard, power cord) OMC-R Map 1 OMC-R Quantity 1 1 1 1 2 1 1 1 1 1 1
6560 planning rules

NOTE Consult your Product Manager or Motorola local office regarding the available options. The 6560 configuration has been standardized as much as possible so that it forms the basic building block for datacomms. In order to expand the datacomms capability; multiply 6560s are connected in a ring. In addition a couple of simple optional items have been added. Each 6560 can support only 30 timeslots. Figure 7-1 and Figure 7-2 shows the various standard configurations and interconnection of multiple 6560s. The connections between the HSIs and the 6560s vary according to quantity. The 6560s are connected in a ring using ports 1 and 3. Any of the E1 timeslots can be patched to any connected 256 kbit/s HSI port. NOTE Each 6560 can only support 30 timeslots across its two E1 ports.
14th Apr 00
73
GSM-001-103
SINGLE 6560
Port 3
HSI 1
High-end OMC-R
HSI 2
6560
Port 1
30 T/S 2 x E1
DUAL 6560
HSI 1
6560
60 T/S 4 x E1
High-end OMC-R
HSI 2
6560
3 x 6560
6560
HSI 1
High-end OMC-R
HSI 2
6560
90 T/S 6 x E1
6560
Figure 7-1 6560 MPR configurations (Part 1)
74
14th Apr 00
GSM-001-103
4 x 6560
6560
HSI 1
6560
120 T/S 8 x E1
High-end OMC-R
HSI 2
6560
6560
5 x 6560
6560
HSI 1
6560
High-end OMC-R
HSI 2
6560
150 T/S 10 x E1
6560
6560
Figure 7-2 6560 MPR configurations (Part 2)
14th Apr 00
75
GSM-001-103
Scaleable OMC-R server and workstation composition

Table 7-3 lists the various elements and quantities of the Low-end and High-end Scaleable OMC-R configurations. Table 7-3 Scaleable OMC-R server composition Standard (mandatory) Server hardware Low-end OMC-R (must be ordered) Sun scaleable IPLs (either additive to the required capacity or full capacity) Sunlink HSI interface and cables (varies according to packet switch) Server country kit (as appropriate for country of use) Low-end (Qty) 1 1 1+ 1 1 High-end (Qty) 1 1 1+ 2 1
Table 7-4 lists the various optional elements and quantities of the Low-end and High-end Scaleable OMC-R configurations. Table 7-4 Scaleable OMC-R options Options Expansion kit Low-end to High-end TCH expansion kit (Hardware only) MMI workstations MMI workstation hardware MMI workstation software (as above) MMI workstation country kit (as appropriate for country of use) MMI workstation remote operation kit Map OMC-R Map (Details required from customer) 1 1 1 Up to 4 1 per 1 per 1 per 1 per N/A Up to 10 1 per 1 per 1 per 1 per Low-end (Qty) High-end (Qty)
76
14th Apr 00
Chapter 8
Planning exercise
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 8 Planning exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Order creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for BTS 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for BTS 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter combining requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the hardware requirements for the GPRS PCU . . . . . . . . . . . . . . . . . . . . . . . . Calculations using alternative call models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters used in calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of CCCHs per cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of SDCCHs per cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of GPROC2s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 82 82 83 83 85 85 86 86 86 87 89 89 89 89 89 810 812 812 814 815 815 815 815 815 815 816 816 816 816 816 816 816 817 818 818 820 825 825 825 827 828 829
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter is a planning exercise designed to illustrate the use of the rules and formulae provided in Chapter 3, BSS cell planning; Chapter 4, BTS planning steps and rules; Chapter 5, BSC planning steps and rules; Chapter 6, RXCDR planning steps and rules and Chapter 7, OMC-R planning steps and rules. The tables of required equipment in this chapter list only the major Motorola supplied items. Equipment not covered in these examples includes: cable, external power supplies and air conditioning equipment. Consult the appropriate Motorola local office for assistance in ensuring that all necessary items are purchased. This chapter contains: S S S S S Order creation. The initial requirements for the planning exercise using the standard call model. A planning exercise using the standard call model. A planning exercise using alternative call models. Determining the hardware requirements for the GPRS PCU.
14th Apr 00
81
Order creation
GSM-001-103
Order creation
Introduction
The following BTS and OMC-R examples are compiled using Tables referenced in the GSM Ordering Manual (68P02900W20). Determine if the site is to operate in an EGSM900 network or a DCS1800 network. Answer the following four questions and refer to the appropriate group of reference tables
Question What type of environment is required? Is a Macrocell product required?
Options Indoor Outdoor Horizonmacro M-Cell6 (indoor) M-Cell6 (indoor) M-Cell6 (indoor) M-Cell6 (outdoor) M-Cell6 (outdoor) M-Cell6 (outdoor) Horizonmicro M-Cell2 (indoor) M-Cell2 (indoor) M-Cell2 (outdoor) M-Cell2 (outdoor)
Frequency
Table reference
1800 900 1800 Dual 900 1800 Dual 900 900 1800 900 1800 900/1800 900/1800
Information available in next issue Table 1 to Table 28 Table 101 to Table 124 Table 195 to Table 212 Table 29 to Table 48 Table 125 to Table 144 Table 213 to Table 225 Table 49 to Table 51 Table 55 to Table 77 Table 145 to Table 169 Table 78 to Table 100 Table 170 to Table 194 Table 263 to Table 267 Table 274 to Table 281
Is a Microcell product required? Is a Wireless enterprise product required?
Horizonmicro M-Cellaccess
82
14th Apr 00
GSM-001-103
Initial requirements
Requirements
In the area of interest, a demand analysis has identified the requirement for 11 BTSs with the busy hour Erlang requirement shown in column two of Table 8-1. Column three of Table 3-3 or Table 3-4 (depending on position in location area) in the Capacity calculations section of Chapter 3 provides the maximum Erlang capacity for a given number of carriers at 2% blocking. Column one of the same tables lists the number of carriers (RTF) required; column three of Table 8-1 lists this information. If other blocking factors at the air interface are required, the number of Erlangs for column three of Table 3-3 or Table 3-4 in the Capacity calculations section of Chapter 3 can be found by reference to standard Erlang B tables for the number of traffic channels in column two of Table 3-3 or Table 3-4 in the Capacity calculations section of Chapter 3 at the required blocking factor. Table 8-1 Busy hour demand and number of carriers BTS No 1 2 3 4 5 6 7 8 9 10 11 Total Erlangs 6 5 2 5 14 10 5 2 5 20/20/20 5 119 Antenna configuration Omni 2 Omni 2 Omni 1 Omni 2 Omni 3 Omni 3 Omni 2 Omni 1 Omni 2 Sector 4/4/4 Omni 2 32 carriers
14th Apr 00
83
GSM-001-103
By reference to a frequency planning tool it is possible to assign adequate frequencies to support the BTS antenna configurations of Table 8-1. Based on this, initial planning of the network gives the topology shown in Figure 8-1.
RXCDR MSC
BSC OMC-R BTS 10 BTS 1 BTS 5
BTS 2
BTS 6
BTS 11
BTS 3
BTS 7
BTS 9
BTS 4
BTS 8
Figure 8-1 Network topology
84
14th Apr 00
GSM-001-103
The exercise
The exercise
Introduction
In order to illustrate the planning steps, the hardware requirement for BTS 2 and BTS 10 will be calculated, followed by the calculation to produce the hardware requirement for the BSC, RXCDR, and the OMC-R. Where parameters are required for the database generation they are noted. The calculations for the hardware capacity use the standard call model given in: S S S S S Chapter 3: Chapter 4: Chapter 5: Chapter 6: Chapter 7: BSS cell planning. BTS planning steps and rules. BSC planning steps and rules. RXCDR planning steps and rules. OMC-R planning steps and rules.
14th Apr 00
85
Determine the hardware requirements for BTS 2
GSM-001-103

Introduction
From Figure 8-1 and Table 8-1 it can be seen that BTS 2 is required to have two RF carriers in an omni configuration to carry a peak demand of five Erlangs.
Cabinet
From the site requirements and the potential future expansion it can be determined that this site should be built using an M-Cell6 indoor cabinet. Reference should be made to the Motorola local office.
Main site number

Reference to Table 8-2 indicates that the appropriate order number for an M-Cell6 Omni 2 GSM900 is SWUF2941.
Interface option
Reference to Table 8-2 indicates that, for an E1 120 ohm interface, order number SWLN2923 is required.
Power redundancy
Reference to Table 8-3 indicates that, for a one cabinet site, order number SWLN2910 is required.
Duplexing
Only two antennas will be used on this site, so we need to specify duplexing. Reference to Table 8-3 indicates that, for a one cabinet site, order number SWLF2650 is required. This duplexer will be fitted on the top panel of the site cabinet.
Digital redundancy
It is not considered that the purpose of this site justifies the expense of digital redundancy.
Alarm inputs
More that eight alarm inputs are not required, so nothing is needed here.
Memory
Requirement is to have non-volatile code storage and the ability to download code in background mode. Reference to Table 8-3 indicates that, for a one cabinet site, order number SWLN4839 is required.
Database option
Reference to Table 8-3 indicates that, for a database, order number EUR8888 is required.
86
14th Apr 00
GSM-001-103
Summary
The equipment required, and an example of customer order creation for an M-Cell6 outdoor (900 MHz) configuration, to implement BTS 2 is listed in Table 8-2 and Table 8-3. Table 8-2 Customer ordering guide 900 MHz (M-Cell6 indoor) Question Voltage used Compulsory +27 V dc 48/60 V dc 110/240 V ac 1 2 3 1 2 3 4 5 6 7 8 How many cabinets are required for the RF configuration? 1 2 3 4 CBF (Hybrid) CCB (Cavity) 3 I/P CBF Air T43 (E1) (75 ohm) BIB (E1) (120 ohm) BIB (T1) (120 ohm) n n n n Table reference Selection
How many cells are required?
How many carriers are required per cell? (RF configuration)
4 to 11
SWUF2941
What type of combining is required?
What line interface is required?
12
SWLN2923
14th Apr 00
87
GSM-001-103
Table 8-3 Customer ordering guide 900 MHz (M-Cell6 indoor) Question Is link redundancy required? Is digital redundancy required? Is power redundancy required? Is duplexing required? Is a high power duplexer shelf and/or external rack required? Options Yes No Yes No Yes No Yes No Yes No n n 14 n n n 15 16 to 20 21 n 22 n n n 23 24 SWLN4839 EUR8888 SWPN2910 SWLF2650 Table reference 13 Selection
Are 16 way alarm inputs Yes required? No Is a memory card required? Is database required? (Provided by local office) Is ac battery backup required? Select ac battery box options? Is 48 V power supply module (APSM) required? Yes No Yes No Yes No Yes No Yes No
25 n 26 n 27 n 28 n
Is Comms power supply Yes module (CPSM) No required?
88
14th Apr 00
GSM-001-103

Introduction
From Figure 8-1 and Table 8-1 it can be seen that BTS 10 is required to have 12 RF carriers in a sector 4/4/4 configuration to carry a peak demand of 20 Erlangs per sector.
Cabinet
From the site requirements and the potential future expansion it can be determined that this site will be contained in two or three Horizonmacro cabinets.
Receiver requirements
A two cabinet solution and a three cabinet solution are provided below.
Two cabinet solution

Each cabinet will have four carriers of a sector plus two carriers of a shared sector. Two SURF modules will support the four carriers in each sector. The shared sector will be supported by inter-connecting the SURF in the Master cabinet to the SURF in the Extender cabinet.
Three cabinet solution

Each cabinet will be dedicated to a sector, allowing for easy expansion.
Transmitter combining requirements

A two cabinet solution and a three cabinet solution are provided below.
Two cabinet solution

Each sector requires two DCF modules. The shared sector will have one DCF modules in the Master cabinet and the other DCF in the Extender cabinet.
Three cabinet solution

Each cabinet will be dedicated to a sector which requires one DDF and HCU modules.
14th Apr 00
89
GSM-001-103
Summary
The equipment required, and an example of customer order creation for a two cabinet Horizonmicro indoor (1800 MHz) configuration, to implement BTS 10 is listed in Table 8-4 and Table 8-5. Table 8-4 Customer ordering guide 1800 MHz (Horizonmicro indoor) Question Voltage used Compulsory +27 V dc 48/60 V dc 240 V ac 1 2 3 1 2 3 4 5 6 7 8 How many cabinets are required for the RF configuration? 1 2 3 4 DCF (Hybrid) DCF & Air TDF DDF DDF & HCU DDF, HCU & Air DDF & Air What line interface is required? T43 (E1) (75 ohm) BIB (E1) (120 ohm) n n Table reference Selection
How many cells are required?
How many carriers are required per cell? (RF configuration)
What type of combining is required?
NOTE The Horizonmicro product ordering information will become available in the next issue of this manual.
810
14th Apr 00
GSM-001-103
Table 8-5 Customer ordering guide 1800 MHz (Horizonmicro indoor) Question Is digital redundancy required? Is power redundancy required? Options Yes No Yes No n n Table reference Selection
n n n n n n n
Is an extra line interface Yes required? No Are 16way alarm inputs required? Is a memory card required? Is a stacking bracket required? Is battery backup required? Is database required? (Provided by local office) NOTE Yes No Yes No Yes No Yes No Yes No
The Horizonmicro product ordering information will become available in the next issue of this manual.
14th Apr 00
811
Determine the hardware requirements for the BSC
GSM-001-103

Introduction
From Figure 8-1 and Table 8-1 it can be seen that this BSC controls 11 BTSs with 32 carriers in 13 cells to carry a peak demand of 119 Erlangs.
BSC to BTS Links

Reference to Figure 8-1 shows that the number of links connected from the BTS to the BSC is four.
BSC to MSC Links

Reference to standard Erlang B tables shows that 119 Erlangs at 1% blocking requires 138 traffic channels. One OML link, one XBL link and one C7 signalling link are required. The number of trunks required is given by: ((1 ) 1) ) (1 ) 1) ) (1 ) 1) ) (138 4)) 31 + 1.3 This value should be rounded up to 2.
Transcoder requirement
None required, remote transcoding.
MSI requirement
Minimum number of MSIs required is given by: (4 ) 2) 2 + 3
Line interface
Depending on the interface standard (balanced or unbalanced) used, one BIB or one T43 is adequate for three MSIs.
GPROC2 requirement
GPROC function requirements are listed in Table 8-6. Table 8-6 GPROC2s required at the BSC Function BSP LCFs for MTLs LCFs for RSLs Optional GPROC requirements Redundant BSP, CSFP Redundant LCP Total GPROC2s NOTE The notation n + m means that n items are required plus m for redundancy. 1 1 3+2 Number required 1 1 1
812
14th Apr 00
GSM-001-103
KSW requirement
Device timeslot requirements are listed in Table 8-7. Table 8-7 BSC timeslot requirements Device GPROC2s XCDR MSI Total timeslots Number required 5*32 = 160 None 3*64 = 192 352
Therefore the BSC can be accommodated in one BSU shelf and one KSW is required.
KSWX requirement
The BSC is contained in one shelf so there is no requirement for a KSWX.
GCLK requirement
One GCLK per BSC is required plus one for redundancy.
CLKX requirement
The BSC is contained in one shelf so there is no requirement for a CLKX.
PIX requirement
The number of PIX boards required depends on the number of external alarms that are required. Use one for this example.
BBBX requirement
One BBBX is required in each shelf.
LANX requirement
An adequate number of LANXs are provided for non redundant operation. A redundant LAN requires one additional LANX per cabinet.
Power supply
Depending on the power supply voltage two EPSM plus one for redundancy or two IPSM plus one for redundancy will be required.
14th Apr 00
813
GSM-001-103
Summary
The equipment required to implement the BSC is listed in Table 8-8. Table 8-8 Equipment required for the BSC Equipment BSSC2 cabinet BSU shelf MSI BIB or T43 GPROC2 KSW GCLK PIX (provides up to 8 external alarms) BBBX LANX EPSM/IPSM (+27 V) (48 V) NOTE The notation n + m means that n items are required plus m for redundancy. Order Number SW1037 SWLN4653 SLN7134 SWLN4024/SWLN4025 SGLN4293 SLN7131 SLN7130 SLN7135 SWLN4101 SLN7138 SWLN4100/SWPN1021 SWLN4098/SWPN1020 Number required 1 1 3 1 3+2 1+1 1+1 1 1 1 2+1
814
14th Apr 00
GSM-001-103
Determine the hardware requirements for the RXCDR

MSI requirements
It is necessary to provide enough MSIs to communicate on the links to the BSC, for E1 links the traffic connection comes directly from the transcoder card.
Links to the BSC

From the calculation in the Section BSC to MSC links above it can be seen that there are two links to the BSC.
Links to the OMC-R

From the topology, see Figure 8-1, it can be seen that a link to the OMC-R from the RXCDR must be provided.
Number of MSIs required

From the foregoing it can be seen that three E1 links are required. The number of MSI cards is given by: 3 2 + 1.5 This value should be rounded up to 2.
Transcoder requirement
From the calculation in the Section BSC to MSC links above it can be seen that 138 traffic channels and two C7 links are required. The number of transcoder cards is given by: 138 30 + 5 This applies to either XCDR or GDP cards.
Link interface
From the MSI requirements it can be seen that two E1 links to the BSC and one to the OMC-R are required. From the Transcoder requirements it can be seen that a further five E1 links are required. A total of eight E1 links are required. The number of BIB/T43s is given by: 8 6 + 1.3 This value should be rounded up to 2.
GPROC2 requirement
One GPROC2 is required, plus one for redundancy.
KSW requirement
From the number of MSIs, transcoders and E1 links it can be seen that the total number of timeslots is given by: 2 * 16 ) 5 * 16 ) 2 * 64 + 240 One KSW is required, plus one for redundancy.
14th Apr 00
815
GSM-001-103
KSWX requirement
The RXU is contained in one shelf so there is no requirement for a KSWX.
GCLK requirement
One GCLK is required plus one for redundancy.
CLKX requirement
The RXU is contained in one shelf so there is no requirement for a CLKX.
PIX requirement
The number of PIX boards required depends on the number of external alarms that are required. Use one for this example.
BBBX requirement
One BBBX is required in each shelf.
LANX requirement
An adequate number of LANXs are provided for non redundant operation. A redundant LAN requires one additional LANX per cabinet.
Power supply
Depending on the power supply voltage two EPSM plus one for redundancy or two IPSM plus one for redundancy will be required.
816
14th Apr 00
GSM-001-103
Summary
The equipment required to implement the RXCDR is listed in Table 8-9. Table 8-9 Equipment required for the RXCDR Equipment BSSC2 cabinet RXU shelf MSI XCDR/GDP-E1 BIB or T43 GPROC2 KSW GCLK PIX (provides up to 8 external alarms) BBBX LANX EPSM/IPSM (+27 V) (48 V) NOTE The notation n + m means that n items are required plus m for redundancy. Order Number SW1037 SWLN2195 SLN7134 SLN7803/SWLN4485 SWLN4024/SWLN4025 SGLN4293 SLN7131 SLN7130 SLN7135 SWLN4101 SLN7138 SWLN4100/SWPN1021 SWLN4098/SWPN1020 Number required 1 1 2 5 2 1+1 1+1 1+1 1 1 1 2+1
14th Apr 00
817
Determine the hardware requirements for the OMC-R
GSM-001-103

OMC-R example
The following is an example of customer order creation for an OMC-R system configuration. S Basic configuration items: Low-end. Low-end server hardware. Sunlink HSI interface to 6560. OMC-R. OMC-R server country kit (UK)
Optional items: Map 1. Local MMI workstation. MMI workstation country kit (UK). 6560 MPR (30).
Table 8-10 Customer ordering guide for the OMC-R Question How many traffic channels (TCH) are required? Compulsory Software Hardware Low-end High-end Select keyboard, power cord and modem as required? Country specific kit n n n Table reference 301/302 Selection SWDN5035
303 304 305 306 307
SWDN5025 SWDN4894
GPDOMCX3507 GPDOMCX317 SWDN5051
818
14th Apr 00
GSM-001-103
Table 8-11 Customer ordering guide for the OMC-R Question Are Local workstations required? Are Remote workstations required? Select MMI keyboard and power cord. Options Yes No Yes No Country specific kit n n Table reference 308 309 n n n n 310 311 312 313 314 n n 315 SWDN4740 GPDOMCX3507 GPDOMCX317 SWDN5050 GPDOMCX317 Selection SWLN3602
Is a Multi Protocol Yes Router (MPR) required? No Select MPR power cord. Are optional items for MPR required? Are Maps required? Yes No Yes No 1 3 6 Yes No Yes No
Is third party documentation required? Are any optional software features required?
316 n 317 n
14th Apr 00
819
Determine the hardware requirements for the GPRS PCU
GSM-001-103

This section provides an example of the PCU hardware provisioning process and the link provisioning process associated with adding a PCU to the BSC as shown in Figure 8-2. For the provisioning of the BSC hardware, the network planner should follow the relevent planning rules for adding additional E1 interface hardware in support of the GDS and GSL links. The provisioning of the SGSN hardware is described by the example in the next section. GDS BSC 1 to 9 E1s GSL 1 to 4 E1s 1 or 2 E1s GSM + GPRS E1s PCU GBL SGSN
BTS
Figure 8-2 PCU equipment and link planning The network planner would use the following process in order to provision a BSS with 10 sites consisting of 20 cells with one GPRS carrier per cell.
Step 1: choose a cell RF plan

Use the 1 x 3 2/6 and 1 x 1 2/18 hopping tables, in Chapter 3, to determine what the values to use for CS rate and BLER for the chosen cell RF plan. For this example, use for the 1x3 2/6 hopping RF plan.
Step 2: determine number of GPRS carrier timeslots

Use Equation 1 (see Chap 3) to determine the number of GPRS timeslots that are required on a per cell basis. In order to use Equation 1, the network planner should have the expected cell load in kbit/s. For this example, assume each cell is being planned to handle 30 kbit/s. Equation 1 evaluates to 5.8 timeslots; so provision 6 timeslots. Therefore, the mean load is handled by 3 active timeslots, and 3 timeslots are considered standby timeslots.
820
14th Apr 00
GSM-001-103
Step 3: calculate the number of GDS E1 links

For this calculation, a conservative provisioning approach would be to provision one GDS TRAU E1 per PRP board. Each PRP board can process 30 active timeslots and 90 monitored timeslots. Using the number of mean PDCHs =3 from step 2, the number of PRPs required to serve 20 cells is: (3 active timeslots per Cell) * (20 cells per BSC) / (30 active timeslots per PRP) = 2 PRPs. These 2 PRPs have more than enough capacity to handle the additional 3 standby timeslots per cell. Using the conservative provisioning rule of one GDS TRAU E1 per PRP, we would provision 2 GDS TRAU E1s. Refer to Chapter 3 for the PCU provisioning rules. A more aggressive GDS TRAU E1 provisioning approach can be taken where 60 Active and 64 Standby timeslots are provisioned on only one GDS TRAU E1. The PCU load balancing software would distribute the load over the two PRP boards. The advantage of the more aggressive provisioning approach is that one less E1 would need to be provisioned at the BSC. The disadvantage is that if the one GDS TRAU E1 were to fail, 100% of the PCU service would be lost.
Step 4: calculate the PCU hardware to support the PCU traffic of 60 active timeslots and 2 GDS E1s
For the calculation bear the following in mind: Qty 2 PRP boards, 1 PRP board per GDS E1 link. Qty 1 PICP board, 1 PICP board per 4 GDS TRAU links (2 links provisioned). Qty 1 MPROC board, 1 MPROC board per PCU shelf. Qty 1 PCU shelf with alarm board and 3 power supply/Fan assemblies, 1 PCU shelf per 9 PRP boards. Qty 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.
Step 5: calculate the number of GBL links

The number of GBL E1 links is directly related to the number of active timeslots, being provisioned between the BSC and the PCU. In this example 60 active timeslots are required. One GBL E1 can carry the equivalent of 150 active timeslots. This figure includes the GBL signalling traffic and the GPRS packet data traffic including protocol overhead. Therefore, the number of GBL E1 links required is: (60 active BSC-PCU timeslots)/ (150 active timeslots per GBL E1) = 0.4 E1s. This answer would be rounded up to 1 E1 without redundancy unless a fractional E1 is available for use. If a fractional E1 is available, it is not necessary to round up to the nearest integer value for the number of E1s to specify.
Step 6: calculate the number of GSL links:

Use Equation 11 (see Chap 5) to calculate how many 64kbits/sGSL links are required. For this example, the number of active timeslots is 60. Evaluating Equation 11 and the supporting expressions results in two 64 kbit/s GSL links being required, after rounding up to the nearest integer value. The significant intermediate values that are used to evaluate Equation 11 are shown in Table 8-12.
14th Apr 00
821
GSM-001-103
Table 8-12 Significant intermediate values to evaluate Equation 11 Equation Equation 11 Equation 13 Equation 14 Equation 15 Parameter No_GSL_TS= 15,200/15000 No_Imm_Assign= 12,000 GPRS_Page= 1,200 Stat_msg= 2,000 Location Chapter 5 Chapter 5 Chapter 5 Chapter 5
Step 7: recalculate the number of PICP boards required

Now that the number of GDS, GBL, and GSL E1 links have been calculated, make sure that there are a sufficient number of PICP boards to cover the GBL and GSL E1 links, and to satisfy the 1-to-4 ratio of GDS TRAU E1s to PICP boards. The PCU hardware calculation in step 4 calculated the number of PICP boards based only on the ratio of PICP boards to PRP boards. This step takes into account the number of E1 links terminated on the PICP boards for the GBL and GSL E1 links. A PICP board can terminate both GBL and GSL links on the board, but not on the same PMC module. Each PICP has two PMC modules. In step 5 it was determined that 1 E1 link is required for the GBL. Each PICP can terminate up to 4 GBL links. Therefore, 1/4 of a PICP is required for the GBL E1 links. In step 6 it was determined that 1 E1 link is required for the GSL. Each PICP can terminate up to 2 E1 GSL links and up to 12 GSL 64 kbit/s timeslots distributed over two E1s. Note that there is a limit of 2 GSL E1s per PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link. Reviewing the GBL and GSL E1 link requirements, we can see that one PICP is sufficient to handle the link provisioning requirements.
Step 8: calculate the increased data traffic load on the E1s between the BSC and BTSs
It is assumed that the GPRS traffic is in addition to the existing circuit switched traffic. In step 2 it was determined that 6 timeslots would be required for the combined active plus standby GPRS timeslot traffic on a per cell basis. The active plus standby timeslots should be allocated as reserved. Therefore, 12 more16 kbits/stimeslots are required on a per-BTS-site basis, 2 cells per site, in order to carry the GPRS traffic. A decision can be made at this stage of the provisioning process on how to allocate the GPRS carrier timeslots. That is, they are reserved or switchable. If GSM circuit switched statistics are available, they could be reviewed to aid in this decision. Refer to the section in the planning guide that discusses the tradeoffs of using reserved and switchable timeslots. Since a whole carrier of 8 timeslots was added to each BTS cell in support of GPRS, it might be advantageous to configure the E1 to carry the traffic for the additional 2 timeslots. If these two timeslots are provisioned as switchable, both GPRS and GSM circuit switched traffic could benefit from this additional capacity.
822
14th Apr 00
GSM-001-103
Step 9: calculate the increased signalling traffic load (RSL load) on the E1s between the BSC and BTSs:
The BTS combines the additional signalling load for the GPRS data traffic with the existing circuit switched traffic load. This results in an additional load on the existing RSL links between each BTS and the BSC. The additional load on the RSL for GPRS is based on the evaluation of Equation 6 (see Chap 5) and supporting equations. For 60 active timeslots, two 64 kbit/s RSL channels would be required, after rounding up to the nearest integer value to support the GPRS portion of the network. The network planner should calculate the RSL load for the GSM circuit switched portion of the network, and then add the the GSM number of RSLs to the GPRS requirements in order to determine the total number of RSL links to provision per Equation 6. The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the GPRS calculation.
Step 10: calculate the increased load due to GPRS traffic on the common control channel at each BTS cell
NOTE Equations 19 to 25 will be found in Chapter 3. Use Equation 19 (see Chap 3) for this calculation. The BTS combines the additional control channel load for the GPRS data traffic with the existing circuit switched traffic load onto the Common Control CHannel (CCCH). The network planner needs the expected paging rate and the access grant rate in order to calculate the number CCCH blocks needed to support the additional GPRS traffic load. This calculation should be performed using the guidelines given in the GPRS control channel provisioning section of the planning guide. Use Equation 21 (see Chap 3) to determine the paging load, and use Equation 24 (see Chap 3) to determine the access grant load. Substituting the value 1.5 (No_GPRS_Pages) for the number of pages per second per cell and the value 3 (burst_GPRS) for the number of bursts per second per cell, evaluates to 2.9 CCCH blocks required in support of GPRS. This most likely means that the network planner cannot use a combined BCCH. The GSM circuit switched signalling load is in addition to the 2.9 CCCH blocks required for GPRS.
Step 11: BSC provisioning impact

The BSC may require additional hardware in order to support the addition of the GPRS network traffic. For BSC provisioning rules, the relevant planning rules should be consulted. The BSC may require more E1 terminations in support of the additional E1 links to the PCU and in support of the additional GPRS traffic over the BTS-to-BSC interface. In this example, two E1s were added for the GDS links and one E1 added for the GSL link. The BSC LCF GPROC2 processor load is increased by the volume of GPRS signalling traffic. The BSS planning rule for LCF provisioning in Equation 26 (see Chap 5) should be used. Scaling the paging load of a maximally-configured PCU by 25 % would give 3 pages/second to use as the PGPRS value. Substituting the other values into Equation 26 the answer is 0.7 LCF GPROC2. The network planner may choose to add an additional LCF GPROC2, or to examine the GSM circuit switched provisioning to see whether an existing LCF GPROC2 could handle this additional load.
14th Apr 00
823
GSM-001-103
Step 12: BTS provisioning impact

The BTS requires one carrier per cell to be provisioned as a GPRS carrier. Adding a GPRS carrier to a cell may require that another DHP processor board is added to the BTS. The relevant planning rules should be consulted in order to provision the BTS hardware, including the addition of DHP processor board to the BTS.
Step 13: OMC-R provisioning impact

The OMC-R is impacted primarily through the additional statistics generated by the PCU. The BSC merges the PCU statistics with the rest of the BSS statistics for uploading to the OMC-R over the 64kbits/s X.25 link. No change in this link provisioning is required.
824
14th Apr 00
GSM-001-103
Calculations using alternative call models

Introduction
This section is provided to assist users for whom the planning models given in Chapter 4, Chapter 5 and Chapter 6 are inappropriate. Where this is the case, the various planning tables that are used in the example above will not be correct and the actual values will need to be derived using the formulae given in Chapters 4, 5, and 6. These necessary calculations are demonstrated below.
Parameters used in calculations

It is assumed that the BSS consists of a BSC supporting 360 MSC to BSC trunks, with 420 TCHs (minus the channels required for control channels) distributed among 31 remote BTSs. Each BTS is an omni cell with four CTU/TCUs each containing 32 TCHs (minus the channels required for control channels). The signalling traffic from each BTS is assumed to be identical. Calculations will be made for the number of: S S S S S CCCHs required per BTS cell. SDCCHs required per BTS cell. MSC to BSC links required. BSC to BTS links required. GPROCs required in the BSC.
Redundancy is not considered in the calculations. The sample signalling traffic model parameters that will be used for the example are given in Table 8-13.
14th Apr 00
825
GSM-001-103
Table 8-13 Parameters for planning example Parameter Call duration Ratio of SMSs per call Ratio of handovers per call Ratio of location updates to calls Ratio of IMSI detaches to calls Location update factor: non-border location area Paging rate per second Ratio of intra-BSC handovers to all handovers Number of BTSs Number of cells (sectors) Number of TCHs Percent link utilization Number of radio carriers Number of MSC to BSC trunks Number of traffic channels per cell Time duration for location updates Time duration for SMSs Time duration for call set ups Guard time for SDCCHs Probability of blocking for TCHs Probability of blocking for SDCCHs CCCH utilization Assumed Value T = 120 seconds S = 0.1 H = 2.5 l=2
I =0
L=2 P=3 i = 0.6 B = 10 C = 30 n = 480 U = 20% R = 60 N = 360 n/C = 16 TL = 4 seconds TS = 6 seconds TC = 5 seconds Tg = 4 seconds PBTCH < 2% PBSDCCH < 1% UCCCH = 0.33
826
14th Apr 00
GSM-001-103
Determine the number of CCCHs per cell

The text that follows should be read in conjunction with the material in the Control channel calculations section of Chapter 3. To determine the number of CCCHs per cell proceed as follows. Using the formulae provided in the Control channel calculations section of Chapter 3 the following values can be calculated. From the Erlang B tables the number of Erlangs, e, supported by 16 TCHs with a grade of service (GOS) of 2% is 9.83. From Table 8-13, the average call hold time, T, is 120 s, so the call arrival rate is given by: l call + e T + 9.83 120 + 0.082 From Table 8-13, the ratio of location updates to calls, L is 2 so the location update rate is given by: l LU + L < e T + 2 < 0.082 + 0.164 From Table 8-13, the ratio of SMSs to calls, S is 0.1 so the SMS rate is given by: l S + S < e T + 0.1 < 0.082 + 0.0082 Then the access grant rate is given by: l AGCH + lcall ) lLU ) lSMS + 0.082 ) 0.164 ) 0.0082 + 0.254 From Table 8-13, the paging rate, P, is 3 so the average number of CCCH blocks required to support paging only is given by: N PCH + 3 P + + 0.0299 (4 < 4.25) (4 < 4.25)
The average number of CCCH blocks required to support AGCH only is given by: N AGCH + l AGCH + 0.254 + 0.049 (2 < 4.25) (2 < 4.25)
Using a CCCH utilization figure, UCCCH, of 0.33, the average number of CCCH blocks required to support both PCH and AGCH is given by: N PAGCH + NAGCH ) NPCH (0.0299 ) 0.049) + + 0.239 0.33 UCCCH
Assuming a 1% blocking, the Erlang B tables show that three CCCHs are required. This can be supported by a combined BCCH with three CCCHs. No CCCH should be reserved for AGCH only, since the probability of PCH overload would be significantly increased; NPCH = 0.0299 so: 0.0299 0.33 + 0.091 .
14th Apr 00
827
GSM-001-103
Determine the number of SDCCHs per cell

The text that follows should be read in conjunction with the material in the Control channel calculations section of Chapter 3. To determine the number of SDCCHs per cell proceed as follows. Using the values calculated in the last section and from Table 8-13, The average number of SDCCH, NSDCCH, is given by: N SDCCH = lcall < T c ) lLU < T L ) T g ) l S < T S ) T g + 0.082 < 5 ) 0.164 < (4 ) 4) ) 0.0082 < (6 ) 4) + 1.77 The number of SDCCHs to support an average number of busy SDCCHs of 1.77 with less than 1% blocking as determined by the use of Erlang B tables. When PB < 1% the required number of SDCCHs is six. The nearest number of SDCCH blocks available is eight. This configuration can be realized with two control channel timeslots per cell, one combined BCCH with three CCCHs and a timeslot of eight SDCCHs.
828
14th Apr 00
GSM-001-103
Determine the number of GPROC2s

The following text should be read in conjunction with the material in the Capacity calculation section of Chapter 5. To determine the number of SDCCHs per cell, proceed as follows:
GPROC2s for MSC to BSC signalling

One MTL is required, and this can be handled by a single GPROC2.
GPROCs for layer 3 call processing and BSC to BTS signalling links
There are three steps needed to determine the number of LCP GPROC2s required to support the BSC to BTS signalling links (RSL) and layer 3 call processing: 1. 2. 3. Calculate the number of LCPs required to support the RSLs. Calculate the number of GPROC2s required to support the layer 3 call processing. The larger of the numbers calculated in steps 1 and 2 is the number of LCPs required to support the RTLs signalling links and layer 3 call processing.
Step 1
Determine the number of LCPs required to support RSLs. The GPROC2 formula will be used. G RSL + (R ) 2 * B) (60 ) 2 * 10) + + 0.66 120 120
Step 2
Determine the number of GPROC2s required to support the layer 3 call processing. N L3 + n ) B ) C * 1 + 480 ) 10 ) 30 * 1 + 2.6 + 1.04 440 15 35 2.5 2.5 2.5 440 15 35
Step 3
Take the greater of these two numbers (1.04) and round it up to 2.
Additional LCP GPROC2s for redundancy

It is recommended that an additional GPROC2 exists to act as a redundant LCP. Therefore the total number of GPROC2s required as LCPs is given by: 1 (for the MSC to BCS signalling links) + 2 (for the BTSs) + 1 (for redundancy) = 4
Total number of GPROC2s at the BSC

A GPROC2 is required for the BSP and it is recommended that an additional GPROC2 exists as the redundant BSP. So the total number of GPROC2s required at the BSC is given by: 2 (for BSP and redundant BSP) + 4 (for the LCPs) = 6 Redundancy and CSFP requirements are additional to this.
14th Apr 00
829
GSM-001-103
830
14th Apr 00
Chapter 9
Standard configuration descriptions
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 9 Standard configuration descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with 24 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with full redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell configurations (M-Cellaccess) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two site cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . One cabinet configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one Horizonmacro cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one M-Cell6 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with one M-Cell2 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with two Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with two M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with three Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with three M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with four Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell BTS with four M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macrocell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellarenamacro enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell RF configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cellarena enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
91 91 92 92 93 93 94 95 96 96 98 910 910 911 912 913 913 914 915 915 916 917 917 918 919 919 920 935 998 9107 9108 9108
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides diagrams of the logical interconnections of the components in various standard BSS and BTS site configurations, Picocell, Horizonmacro, and M-Cell. This chapter contains: S S S Typical BSS configurations. Picocell configurations (M-Cellaccess). One cabinet configurations. S Horizonmacro M-Cell6. M-Cell2.
Two cabinet configurations. Horizonmacro M-Cell6.
Three cabinet configurations. Horizonmacro M-Cell6.
Four cabinet configurations. Horizonmacro M-Cell6.
Macrocell RF configurations. Horizonmacro M-Cell6. M-Cell2. Horizoncompact
Microcell RF configuration. Horizonmicro.
14th Apr 00
91
Standard configurations
GSM-001-103
Standard configurations
Introduction
The examples in this section are shown with individual antennas for transmit and receive signals. If individual antennas are not used, duplexers will be required. However, duplexers can result in performance degradation. For carrier redundancy the RF carrier equipment should be duplicated for each BTS. The diagrams that follow are not intended to imply the maximum capacity nor a typical configuration using that specific equipment. Rather, they are meant to highlight the configurations that, within the constraints of the BSS architecture, are feasible when the Macrocell hardware is deployed in a mBCU controlled BTS. The diagrams also show possible cabinet boundaries. Cabinet designs, however, allow for a number of different arrangements of the same configuration. Rather than showing redundancy for all M-Cell BTS configurations, the control redundancy is depicted only for one Horizonmacro, one M-Cell6, and one M-Cell2 cabinet diagram, see Figure 9-8, Figure 9-9, and Figure 9-10.
92
14th Apr 00
GSM-001-103
Typical BSS configurations

BSC with 24 BTS
The digital module configuration for a BSC controlling 24 BTSs is shown in Figure 9-1.
DUAL IEEE LAN DUAL SERIAL BUS PIX BTC GPROC 0
LANX A
LANX B
BSU SHELF 1
DUAL MCAP BUS GPROC 3 KSW A GCLK
GPROC 1
GPROC 2
GCLK REDUNDANT A
DUAL TDM HIGHWAY BUS RMT KSWX A LCL KSWX A CLKX LCL KSWX B
CLKX
BTC
MSI 0
MSI 1
MSI 2
MSI 7
2 Mbit/s LINKS
BTS 1
FIBRE OPTIC LINKS
BTS 2
BTS 3
BTS 12
MSC/RXCDR
2.048 Mbit/s LINK INTERFACES FROM/TO MSC AND TO/FROM BTS SITES BTS 13
BTS 14
BTS15,16
BTS 23, 24 2 Mbit/s LINKS
DUAL SERIAL BUS LCL KSWX A LCL KSWX B RMT KSWX B BTC MSI 0 MSI 1 MSI 2 MSI 6 A B DUAL TDM HIGHWAY BUS BTC GPROC 0 GPROC 1 GPROC 2 KSW B REDUNDANT LANX A DUAL IEEE LAN LANX B DUAL MCAP BUS
BSU SHELF 2 BSSC CABINET
Figure 9-1 BSC controlling 24 BTS
14th Apr 00
93
GSM-001-103
BSC with full redundancy

The digital module configuration for a fully redundant BSC controlling 34 BTS is shown in Figure 9-2.
BSU SHELF 1
DUAL MCAP BUS GPROC 0 GPROC 1 GPROC 2 GPROC 3 KSW A KSW B GCLK A GCLK B A DUAL TDM HIGHWAY BUS B EXP KSWX A EXP KSWX B
DUAL IEEE LAN DUAL SERIAL BUS PIX BTC
LANX A
LANX B
REDUNDANT
CLKX
LCL KSWX A
CLKX
LCL KSWX B
BTC
MSI 0
MSI 1
MSI 2
MSI 9
2 Mbit/s LINKS
BTS 1
BTS 2
BTS 3
BTS 16,17
FIBRE OPTIC LINKS
MSC
2.048 Mbit/s LINK INTERFACES FROM/TO MSC AND TO/FROM BTS SITES BTS 18 BTS 19 BTS 20 BTS 33,34
2 Mbit/s LINKS
EXP EXP KSWX A KSWX B
LCL KSWX A
LCL KSWX B
BTC
MSI 0
MSI 1
MSI 2
MSI 9
A
DUAL TDM HIGHWAY BUS
B
BTC GPROC 0 GPROC 1 GPROC 2 GPROC 3 KSW A KSW B REDUNDANT DUAL SERIAL BUS DUAL IEEE LAN LANX A LANX B DUAL MCAP BUS
BSU SHELF 2 BSSC CABINET
Figure 9-2 Fully redundant BSC controlling 34 BTS
94
14th Apr 00
GSM-001-103
Transcoder
The digital module configuration for a BSSC cabinet equipped to provide transcoding is shown in Figure 9-3.
DUAL IEEE 802.5 LAN DUAL SERIAL BUS BTC GPROC 0 GPROC 1 KSW A GCLK
RXU SHELF 1
LANX A LANX B DUAL MCAP BUS GCLK REDUNDANT DUAL TDM HIGHWAY BUS B
RMT KSWX A
CLK X
LCL KSWX A
CLKX
LCL KSWX B
BTC
MSI 0
MSI 1
XCDR 0
XCDR 15
FIBRE OPTIC LINKS
2.048 Mbit/s LINK INTERFACES FROM/TO BSCS
2.048 Mbit/s LINK INTERFACES FROM/TO MSC
LCL KSWX A
LCL KSWX B
RMT KSWX B
BTC
MSI 0
MSI 1
XCDR 0
XCDR 15 A
DUAL TDM HIGHWAY BUS B BTC GPROC 0 GPROC 1 KSW B REDUNDANT DUAL SERIAL BUS LANX A LANX B
DUAL MCAP BUS
DUAL IEEE LAN
RXU SHELF 2 REMOTE TRANSCODER CABINET
Figure 9-3 BSSC cabinet equipped to provide transcoding
14th Apr 00
95
Picocell configurations (M-Cellaccess)
GSM-001-103

Single site
Optical fibre links
The digital module and RF configuration for a PCC cabinet with six PCUs (RF carriers) and optical fibre links is shown in Figure 9-4.
TO/FROM TRANSMIT/RECEIVE ANTENNA
P C U 1
P C U 2
P C U 3
P C U 4
P C U 5
P C U 6
ONE RF CARRIER CONSISTS OF ONE DRIM, DRIX AND PCU
PCC CABINET BSU SHELF

FIBRE OPTIC LINKS
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
DUAL MCAP BUS DUAL TDM HIGHWAY BUS A B
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
BSC
Figure 9-4 Single BTS site with six PCUs using optical fibre links
96
14th Apr 00
GSM-001-103
HDSL links
The digital module and RF configuration for a PCC cabinet with six PCUs (RF carriers) and HDSL links is shown in Figure 9-5.
TO/FROM TRANSMIT/RECEIVE ANTENNA
P C U 1
P C U 2
P C U 3
P C U 4
P C U 5
P C U 6
ONE RF CARRIER CONSISTS OF ONE DRIM, HRIX AND PCU
PCC CABINET
HIM-75/HIM-120
HIM-75/HIM-120
HIM-75/HIM-120
TOP OF CABINET
LOWER BSU SHELF
HRIX 1
HRIX 2
HRIX 3
HRIX 4
HRIX 5
HRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
BSC
Figure 9-5 Single BTS site with six PCUs using HDSL links
14th Apr 00
97
GSM-001-103
Two site cabinet

Optical fibre links
The digital module and RF configuration for a PCC cabinet with 12 PCUs (RF carriers) and optical fibre links is shown in Figure 9-6.
PCU 1 to 6
PCU 7 to 12
FIBRE OPTIC LINKS
FIBRE OPTIC LINKS
PCC CABINET
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
UPPER BSU SHELF
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LOWER BSU SHELF
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
BSC
Figure 9-6 Two BTS site with 12 PCUs using optical fibre links
98
14th Apr 00
GSM-001-103
HDSL links
The digital module and RF configuration for a PCC cabinet with 12 PCUs (RF carriers) and HDSL links is shown in Figure 9-7.
PCU 1/2
PCU 3/4
PCU 5/6
PCU 7/8
PCU 9/10
PCU 11/12
HIM-75/HIM-120
HIM-75/HIM-120
HIM-75/HIM-120
HIM-75/HIM-120
HIM-75/HIM-120
HIM-75/HIM-120
TOP OF CABINET
HRIX 1
HRIX 2
HRIX 3
HRIX 4
HRIX 5
HRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
UPPER BSU SHELF PCC CABINET
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
HRIX 1
HRIX 2
HRIX 3
HRIX 4
HRIX 5
HRIX 6
DUAL SERIAL BUS
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LOWER BSU SHELF
LINKS FROM/TO BSC
DUAL IEEE 802.5 LAN
LANX A
BSC
Figure 9-7 Two BTS site with 12 PCUs using HDSL links
14th Apr 00
99
One cabinet configurations
GSM-001-103

Macrocell BTS with one Horizonmacro cabinet
The configuration shown in Figure 9-8 is an example of a one-cabinet Horizonmacro. This configuration supports six carriers.
mBCU
N I U N I U
MCUF
MCUF
(FOR REDUNDANCY)
12
12
C T U 2
C T U 2
C T U 2 2
C T U 2
C T U
C T U 2
Horizonmacro
CABINET
Figure 9-8 Macrocell BTS with one Horizonmacro cabinet
910
14th Apr 00
GSM-001-103
Macrocell BTS with one M-Cell6 cabinet

The configuration shown in Figure 9-9 is an example of a one-cabinet M-Cell6 BTS. This configuration supports six carriers.
N I U
mBCU
N I U
mBCU
MCU
MCU
12
12
F O X
F O X
(FOR REDUNDANCY)
12
12
2 T C U
2 T C U
2 T C U
T C U 2
T C U
T C U
M-CELL6 BTS CABINET
Figure 9-9 M-Cell BTS with one M-Cell6 cabinet
14th Apr 00
911
GSM-001-103
Macrocell BTS with one M-Cell2 cabinet

The configuration shown in Figure 9-10 is an example of a one-cabinet M-Cell2 BTS. This configuration supports two carriers.
N I U
mBCU
N I U
mBCU
MCU
MCU
(FOR REDUNDANCY)
2 T C U
T C U
M-CELL2 CABINET
Figure 9-10 Macrocell BTS with one M-Cell2 cabinet
912
14th Apr 00
GSM-001-103
Two cabinet configuration

Macrocell BTS with two Horizonmacro cabinets
The configuration shown in Figure 9-11 is an example of a two cabinet Horizonmacro. This configuration supports 12 carriers. The MCUF interface to the CTUs in the second cabinet, through an FMUX in the second cabinet.
N I U mBCU
Horizonmacro
CABINET
MCUF
12 2 2 2 2 2 2
C T U
C T U
C T U
C T U
C T U
C T U
Horizonmacro 2 Cabinet
C T U
mBCU 12 F M U X
C T U
C T U
C T U
C T U
C T U
Figure 9-11 Macrocell BTS with two Horizonmacro cabinets
14th Apr 00
913
GSM-001-103
Macrocell BTS with two M-Cell6 cabinets

The configuration shown in Figure 9-12 is an example of a two cabinet M-Cell6 BTS. This configuration supports 12 carriers. The MCUs interface to the TCUs through the FOX or the FMUX/FOX.
N I U mBCU
M-CELL6 BTS CABINET
MCU
12
F M U X
12 F O X 12 2 2 2 2 2 2 T C U
T C U
T C U
T C U
T C U
T C U
M-CELL6 BTS CABINET
12 2 2 2 2 2 2 T C U mBCU F O X F M U X
T C U
T C U
T C U
T C U
T C U
Figure 9-12 Macrocell BTS with two M-Cell6 cabinets
914
14th Apr 00
GSM-001-103
Three cabinet configuration

Macrocell BTS with three Horizonmacro cabinets
The configuration shown in Figure 9-13 is an example of a three cabinet Horizonmacro. This configuration supports 18 carriers. The MCUFs interface to the CTUs in the other cabinets through the FMUXs.
N I U mBCU
Horizonmacro
CABINET
2 MCUF 2
12 2 2 2 2 2 2
C T U
C T U
C T U
C T U
C T U
C T U
Horizonmacro2
CABINET
C T U
12 2 2 2 2 2 mBCU F M U X
C T U
C T U
C T U
C T U
C T U
Horizonmacro
CABINET
2 2 2 2 2 2 C T U C T U C T U
12 mBCU F M U X
C T U
C T U
C T U
Figure 9-13 Macrocell BTS with three Horizonmacro cabinets
14th Apr 00
915
GSM-001-103
Macrocell BTS with three M-Cell2 cabinets

The configuration shown in Figure 9-14 is an example of a three cabinet M-Cell2 BTS. This configuration supports six carriers.
mBCU
M-CELL2 CABINET
N I U
MCU
12
F O X
12 2 2 T C U
T C U
M-CELL2 CABINET
2 2
T C U
T C U
M-CELL2 CABINET
2 2
T C U
T C U
Figure 9-14 Macrocell BTS with three M-Cell2 cabinets
916
14th Apr 00
GSM-001-103
Four cabinet configuration

Macrocell BTS with four Horizonmacro cabinets
The configuration shown in Figure 9-15 is an example of a four cabinet Horizonmacro. This configuration supports 24 carriers. The MCUFs interface to the CTUs in the other cabinets through the FMUXs.
mBCU 12 F M U X 2
N I U
Horizonmacro
CABINET
MCUF
12 2 2 2 2 2 2
C T U
C T U
C T U
C T U
C T U
C T U
12
Horizonmacro2
CABINET
C T U
mBCU F M U X
C T U
C T U
C T U
C T U
C T U
Horizonmacro
CABINET
12 2 2 2 2 2 mBCU F M U X
C T U
C T U
C T U
C T U
C T U
C T U
Horizonmacro
CABINET
2 2 2 2 2 2 C T U C T U C T U
12 mBCU F M U X
C T U
C T U
C T U
Figure 9-15 Macrocell BTS with four Horizonmacro cabinets
14th Apr 00
917
GSM-001-103
Macrocell BTS with four M-Cell6 cabinets

The configuration shown in Figure 9-16 is an example of a four cabinet M-Cell6 BTS. This configuration supports 24 carriers. The MCUs interface to the TCUs through the FOX or the FMUX/FOX.
N I U mBCU 12 F M U X 2
M-CELL6 BTS CABINET
MCU
12
F M U X
12 F O X 12 2 2 2 2 2 2 T C U 12 F M U X 2
T C U
T C U
T C U
T C U
T C U
M-CELL6 BTS CABINET
12 2 2 2 2 2 2 T C U mBCU F O X F M U X
T C U
T C U
T C U
T C U
T C U
M-CELL6 BTS CABINET
12 2 2 2 2 2 2 T C U mBCU F O X F M U X
T C U
T C U
T C U
T C U
T C U
M-CELL6 BTS CABINET
12 2 2 2 2 2 2 T C U mBCU F O X F M U X
T C U
T C U
T C U
T C U
T C U
Figure 9-16 Macrocell BTS with four M-Cell6 cabinets
918
14th Apr 00
GSM-001-103
Macrocell RF configurations
Overview of configuration diagrams
The Horizonmacro cabinets are presented as follows: S S Horizonmacro single cabinet. Horizonmacro multiple cabinets.
The following series of Horizonmacro RF configuration diagrams show suggested ways of connecting together Horizonmacro SURF and Tx blocks to meet different operational requirements. The series of diagrams is by no means exhaustive, and numerous alternative configurations may be adopted to achieve the same aim. Each diagram is applicable to either EGSM 900 or DCS 1800 operation though the SURF module illustrated is an 1800 SURF. For EGSM 900 operation a 900 SURF (dual band) is required. Connections to the 900 SURF are identified in the same way as those to the 1800 SURF, with two additional connectors provided for dual band 1800 use. The M-Cell cabinets/enclosures are presented as follows: S S S S S M-Cell6 single cabinet. M-Cell6 multiple cabinets. M-Cell2 single cabinet. M-Cellarena macro enclosures. Horizonmacro cabinets.
14th Apr 00
919
GSM-001-103
Horizonmacro cabinets
[DCS1800] 4 carrier Omni, with duplexed hybrid and air combining
A single cabinet, four CTU configuration with duplexed hybrid and air combining, is shown in Figure 9-17. Table 9-1 provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA Tx/Rx ANTENNA
B2 1 0 A 2 1 0
B A
SURF
DCF
DCF
C T U A B
C T U A B
C T U A B
C T U A B
Horizonmacro CABINET
Figure 9-17 [GSM1800] 4 carrier Omni with duplexed hybrid and air combining
920
14th Apr 00
GSM-001-103
Table 9-1 Equipment required for single cabinet, four CTU configuration with duplexed hybrid and air combining Quantity 2 1 4 Antennas Horizonmacro cabinet CTU Receiver 1 SURF Transmitter/receiver 2 DCF Unit
14th Apr 00
921
GSM-001-103
[DCS1800] 6 carrier Omni, with duplexed dual-stage hybrid and air combining
A single cabinet, six CTU configuration with duplexed dual-stage hybrid and air combining, is shown in Figure 9-18. Table 9-2 provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA Tx/Rx ANTENNA
B2 1 0 A 2 1 0
B A
SURF FEED THROUGH
DDF
DDF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
Figure 9-18 [GSM1800] 6 carrier Omni with duplexed dual-stage hybrid and air combining
922
14th Apr 00
GSM-001-103
Table 9-2 Equipment required for single cabinet, six CTU configuration with duplexed dual-stage hybrid and air combining Quantity 2 1 6 Antennas Horizonmacro cabinet CTU Receiver 1 SURF Transmitter/eceiver 2 1 DDF Feed through, with two through connectors Unit
14th Apr 00
923
GSM-001-103
[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining

A single cabinet, six CTU configuration with duplexed dual-stage hybrid combining, is shown in Figure 9-19. Table 9-3 provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2)
B2 1 0 A 2 1 0
B A
SURF FEED THROUGH
DDF
DDF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
Figure 9-19 [GSM1800] 2 sector (3/3) with duplexed dual-stage hybrid combining
924
14th Apr 00
GSM-001-103
Table 9-3 Equipment required for single cabinet, six CTU configuration with duplexed dual-stage hybrid combining Quantity 4 1 6 Antennas Horizonmacro cabinet CTU Receiver 1 SURF Transmitter/receiver 2 1 DDF Feed through, with two through connectors Unit
14th Apr 00
925
GSM-001-103
[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and air combining
A multiple cabinet, 12 CTU configuration with duplexed dual-stage hybrid and air combining, is shown in Figure 9-20. Table 9-4 provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 2)
B2 1 0 A 2 1 0
B A
B2 1 0 A 2 1 0
B A
SURF
SURF
FEED THROUGH
FEED THROUGH
DDF
DDF
DDF
DDF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B A B
C T U
C T U A B
C T U A B
EXTENDER Horizonmacro CABINET
MASTER Horizonmacro CABINET
Figure 9-20 [GSM1800] 2 sector (6/6) with duplexed dual-stage hybrid and air combining
926
14th Apr 00
GSM-001-103
Table 9-4 Equipment required for multiple cabinet, 12 CTU configuration with duplexed dual-stage hybrid and air combining Quantity 4 2 12 Antennas Horizonmacro cabinets CTU Receiver 2 SURF Transmitter/eceiver 4 2 DDF Feed through, with two through connectors Unit
14th Apr 00
927
GSM-001-103
[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining

A single cabinet, six CTU configuration with duplexed hybrid combining, is shown in . provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNAS (SECTOR 3) Rx Rx ANTENNAS ANTENNAS (SECTOR 2) (SECTOR 1)
B2 1 0 A 2 1 0
B A
SURF
DCF
DCF
DCF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
Figure 9-21 [GSM1800] 3 sector (2/2/2) with duplexed hybrid combining
928
14th Apr 00
GSM-001-103
Table 9-5 Equipment required for single cabinet, six CTU configuration with duplexed hybrid combining Quantity 6 1 6 Antennas Horizonmacro cabinet CTU Receiver 1 SURF Transmitter/receiver 3 DCF Unit
14th Apr 00
929
GSM-001-103
[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining

A multiple cabinet, 12 CTU configuration with duplexed hybrid and air combining, is shown in . provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
B2 1 0 A 2 1 0
B A
B2 1 0 A 2 1 0
B A
SURF
SURF
DCF
DCF
DCF
DCF
DCF
DCF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B A B
C T U
C T U A B
C T U A B
EXTENDER Horizonmacro CABINET
Figure 9-22 [GSM1800] 3 sector (4/4/4) with duplexed hybrid and air conditioning
930
14th Apr 00
GSM-001-103
Table 9-6 Equipment required for multiple cabinet, 12 CTU configuration with duplexed hybrid and air combining Quantity 6 2 12 Antennas 1999macroBTS cabinets CTU Transmitter/receiver 2 6 SURF DCF Unit
14th Apr 00
931
GSM-001-103
[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and air combining
A four cabinet, 24 CTU configuration with duplexed dual-stage hybrid and air combining, is shown in . provides a summary of the equipment required for this configuration. The following rules apply: S S In an Horizonmacro cabinet, a maximum of six CTUs can be accommodated. An external equipment cabinet is not necessary.
TO EXTENDER 1 Horizon macro CABINET
Tx/Rx ANTENNA (SECTOR 3)
SURF B Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 1) SURF A0
B2 1 0 A 2 1 0
B A
B2 1 0 A 2 1 0
B A
SURF
SURF
HCU DDF DDF
HCU DDF
HCU
C T U A B
C T U
C T U
C T U A B
C T U
C T U A B
C T U A B
C T U A B
C T U A B A B
C T U
C T U A B
C T U A B
A B
A B
A B
EXTENDER 3 Horizonmacro CABINET
Figure 9-23 [GSM1800] 3 sector (8/8/8) with duplexed dual-stage hybrid and air combining (Part 1)
932
14th Apr 00
GSM-001-103
TO EXTENDER 2 Horizon macro CABINET
SURF B0 SURF A
B2 1 0 A 2 1 0
B A
B2 1 0 A 2 1 0
B A
SURF
SURF
HCU DDF
HCU DDF
HCU DDF
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B
C T U A B A B
C T U
C T U A B
C T U A B
Figure 9-24 [GSM1800] 3 sector (8/8/8) with duplexed dual-stage hybrid and air combining
14th Apr 00
933
GSM-001-103
Table 9-7 Equipment required for four cabinet, 24 CTU configuration with duplexed dual-stage hybrid and air combining Quantity 6 4 24 Antennas Horizonmacro cabinets CTU Transmitter 6 Hybrid combiner unit (HCU) Receiver 4 SURF Transmitter/receiver 6 DDF Unit
934
14th Apr 00
GSM-001-103
M-Cell6 cabinets
[GSM900] 3 carrier Omni, with hybrid combining and diversity

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 9-25. Table 9-8 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA Rx ANTENNAS
DLNB
RF INPUT RF LOAD
IADU
NonHCOMB
3-INPUT CBF
4 4
T C U A B
T C U A B
T C U A B
MCell6 BTS CABINET
Figure 9-25 [GSM900] 3 carrier Omni with hybrid combining and diversity
14th Apr 00
935
GSM-001-103
Table 9-8 Equipment required for single cabinet, four TCU configuration with hybrid combining and diversity Quantity 3 1 3 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 1 DLNB Unit
936
14th Apr 00
GSM-001-103
[GSM900] 3 carrier Omni, with hybrid combining, diversity, and mediumpower duplexer
Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
DLNB
RF INPUT RF LOAD
IADU
NonHCOMB
3-INPUT CBF
4 4
T C U A B
T C U A B
T C U A B
MCell6 BTS CABINET
14th Apr 00
937
GSM-001-103
Table 9-9 Equipment required for single cabinet, four TCU configuration with hybrid combining, diversity, and mediumpower duplexer Quantity 2 1 3 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 1 DLNB Transmitter/receiver 1 mediumpower duplexer Unit
938
14th Apr 00
GSM-001-103
[GSM900] 4 carrier Omni, with hybrid combining and diversity

DLNB
RF INPUT RF LOAD
IADU
HCOMB
3-INPUT CBF
4 4
T C U A B
T C U A B
T C U A B
T C U A B
MCell6 BTS CABINET
14th Apr 00
939
GSM-001-103
Table 9-10 Equipment required for single cabinet, four TCU configuration with hybrid combining and diversity Quantity 3 1 4 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 3-input CBF Hybrid combining block (HCOMB) Receiver 1 DLNB Unit
940
14th Apr 00
GSM-001-103
[GSM900] 4 carrier Omni, with hybrid combining, diversity, and mediumpower duplexer
A single cabinet, four TCU configuration with hybrid combining, diversity, and mediumpower duplexer, is shown in Figure 9-28. Table 9-11 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
DUPLEXER
DLNB
RF INPUT RF LOAD
IADU
HCOMB
3-INPUT CBF
4 4
T C U A B
T C U A B
T C U A B
T C U A B
MCell6 BTS CABINET
Figure 9-28 [GSM900] 4 carrier Omni with hybrid combining, diversity, and mediumpower duplexer
14th Apr 00
941
GSM-001-103
Table 9-11 Equipment required for single cabinet, four TCU configuration with hybrid combining, diversity, and mediumpower duplexer Quantity 2 1 4 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 3-input CBF Hybrid combining block (HCOMB) Receiver 1 DLNB Transmitter/receiver 1 mediumpower duplexer Unit
942
14th Apr 00
GSM-001-103
[GSM900] 6 carrier Omni, with cavity combining and diversity

A single cabinet, six TCU configuration with cavity combining and diversity, is shown in Figure 9-29. Table 9-12 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
DLNB CCB CCB
(EXTENSION)
(OUTPUT)
IADU
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
MCell6 BTS CABINET
Figure 9-29 [GSM900] 6 carrier Omni with cavity combining and diversity
14th Apr 00
943
GSM-001-103
Table 9-12 Equipment required for single cabinet, six TCU configuration with cavity combining and diversity Quantity 3 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 CCB (Output) CCB (Extension) Receiver 1 DLNB Unit
944
14th Apr 00
GSM-001-103
[GSM900] 6 carrier Omni, with cavity combining, diversity, and highpower duplexer
A single cabinet, six TCU configuration with cavity combining, diversity, and highpower duplexer, is shown in Figure 9-30. Table 9-13 provides a summary of the equipment required for this configuration. The following rules apply: S S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. In an M-Cell6 side cabinet, a maximum of three highpower duplexers can be accommodated. An external equipment rack/cabinet is required, for a highpower duplexer, in an indoor installation.
Rx ANTENNA Tx/Rx ANTENNA
DLNB
IADU
ANT
Rx
Tx CCB (EXTENSION) CCB (OUTPUT) highpower duplexer
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
M-Cell6 SIDE CABINET
Figure 9-30 [GSM900] 6 carrier Omni with cavity combining, diversity, and highpower duplexer
14th Apr 00
945
GSM-001-103
Table 9-13 Equipment required for single cabinet, six TCU configuration with cavity combining, diversity, and highpower duplexer Quantity 2 1 1 6 Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU Transmitter 1 1 CCB (Output) CCB (Extension) Receiver 1 DLNB Transmitter/receiver 1 highpower duplexer Unit
946
14th Apr 00
GSM-001-103
[GSM900] 8 carrier Omni, with combining and diversity

A multiple cabinet, eight TCU configuration with combining and diversity, is shown in Figure 9-31. Table 9-14 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA
Tx/Rx ANTENNA
Rx ANTENNA
DUPLEXER Rx EXT BLOCK DLNB
IADU
IADU
CBF
CCB (EXTENSION) CCB (OUTPUT)
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
EXTENDER M-Cell6 BTS CABINET
MASTER M-Cell6 BTS CABINET
Figure 9-31 [GSM900] 8 carrier Omni with combining and diversity
14th Apr 00
947
GSM-001-103
Table 9-14 Equipment required for multiple cabinet, 8 TCU configuration with combining and diversity Quantity 3 2 8 Antennas M-Cell6 BTS cabinet TCU Transmitter 1 1 1 CBF CCB (Output) CCB (Extension) Receiver 1 1 DLNB Rx extension block Transmitter/receiver 1 mediumpower duplexer Unit
948
14th Apr 00
GSM-001-103
[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 9-32. Table 9-15 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)
DLNB
DLNB
IADU
RF INPUT RF LOAD RF INPUT RF LOAD
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-32 [GSM900] 2 sector (3/3), with hybrid combining and diversity
14th Apr 00
949
GSM-001-103
Table 9-15 Equipment required for single cabinet, six TCU configuration with hybrid combining and diversity Quantity 6 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 2 1 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 2 DLNB Unit
950
14th Apr 00
GSM-001-103
[GSM900] 2 sector (3/3), with hybrid combining, diversity, and mediumpower duplexers
A single cabinet, six TCU configuration with hybrid combining, diversity, and mediumpower duplexers, is shown in Figure 9-33. Table 9-16 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)
DUPLEXER
DUPLEXER DLNB DLNB
IADU
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-33 [GSM900] 2 sector (3/3), with hybrid combining, diversity, and mediumpower duplexer
14th Apr 00
951
GSM-001-103
Table 9-16 Equipment required for single cabinet, six TCU configuration with combining, diversity, and mediumpower duplexer Quantity 4 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 2 1 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 2 DLNB Transmitter/receiver 2 mediumpower duplexer Unit
952
14th Apr 00
GSM-001-103
[GSM900] 3 sector (2/2/2), with combining and diversity

A single cabinet, six TCU configuration with combining and diversity, is shown in Figure 9-34. Table 9-17 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)
DLNB
DLNB
DLNB
IADU
CBF
CBF
CBF
6 6
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-34 [GSM900] 3 sector (2/2/2), with combining and diversity
14th Apr 00
953
GSM-001-103
Table 9-17 Equipment required for single cabinet, six TCU configuration with combining and diversityprogress on the W01 or W21 Quantity 9 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 CBF Receiver 3 DLNB Unit
954
14th Apr 00
GSM-001-103
[GSM900] 3 sector (2/2/2), with cavity combining, diversity, and mediumpower duplexers
A single cabinet, six TCU configuration with cavity combining, diversity, and mediumpower duplexers, is shown in Figure 9-35. Table 9-18 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 3) Rx ANTENNA (SECTOR 2) Rx ANTENNA (SECTOR 1)
DUPLEXER DUPLEXER DUPLEXER DLNB DLNB DLNB
IADU
CBF
CBF
CBF
6 6
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-35 [GSM900] 3 sector (2/2/2), with combining, diversity, and mediumpower duplexer
14th Apr 00
955
GSM-001-103
Table 9-18 Equipment required for single cabinet, six TCU configuration with combining, diversity, and mediumpower duplexer Quantity 6 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 CBF Receiver 3 DLNB Transmitter/receiver 3 mediumpower duplexer Unit
956
14th Apr 00
GSM-001-103
[GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexer (3 antenna per sector)
A multiple cabinet, 12 TCU configuration with air combining, diversity, and mediumpower duplexer, is shown in Figure 9-36. Table 9-19 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx Tx Tx/Rx ANTENNA ANTENNA ANTENNA (SECTOR 3) (SECTOR 3) (SECTOR 2) Rx Tx Tx/Rx Tx ANTENNA ANTENNA ANTENNA ANTENNA (SECTOR 2) (SECTOR 1) (SECTOR 1) (SECTOR 2) Rx ANTENNA (SECTOR 1)
Rx ANTENNA (SECTOR 2)
DUPLEXER
DLNB
Rx EXT BLOCK
DUPLEXER
DUPLEXER
DLNB
DLNB
IADU IADU
CBF2
CBF1
CBF0
CBF2
CBF1
CBF0
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
Figure 9-36 [GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexer (3 antenna per sector)
14th Apr 00
957
GSM-001-103
Table 9-19 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity, and mediumpower duplexer (3 antenna per sector) Quantity 9 2 12 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 CBF Receiver 3 1 DLNB Rx extension block Transmitter/receiver 3 mediumpower duplexer Unit
958
14th Apr 00
GSM-001-103
[GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexer (2 antenna per sector)
A multiple cabinet, 12 TCU configuration with air combining, diversity, and mediumpower duplexer, is shown in Figure 9-37. Table 9-20 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
DUPLEXER
DUPLEXER
DUPLEXER
DLNB
Rx EXT BLOCK
DUPLEXER
DUPLEXER
DUPLEXER DLNB
DLNB
IADU IADU
CBF2
CBF1
CBF0
CBF2
CBF1
CBF0
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
Figure 9-37 [GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexer (2 antenna per sector)
14th Apr 00
959
GSM-001-103
Table 9-20 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity, and mediumpower duplexer (2 antenna per sector) Quantity 6 2 12 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 CBF Receiver 3 1 DLNB Rx extension block Transmitter/receiver 6 mediumpower duplexer Unit
960
14th Apr 00
GSM-001-103
[GSM900] 3 sector (4/4/4), with cavity combining and diversity

A multiple cabinet, 12 TCU configuration with cavity combining and diversity, is shown in Figure 9-38. Table 9-21 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA (SECTOR 1) Rx ANTENNAS (SECTOR 1)
DLNB
IADU
(EXTENSION)
CCB
(OUTPUT)
CCB
T C U A B
T C U A B
T C U A B
T C U A B
MASTER M-Cell6 CABINET Extender 1 and Extender 2 M-Cell6 cabinets configured similar to the Master cabinet for Sectors 2 and 3.
Figure 9-38 [GSM900] 3 sector (4/4/4), with cavity combining and diversity
14th Apr 00
961
GSM-001-103
Table 9-21 Equipment required for multiple cabinet, 12 TCU configuration with hybrid combining and diversity Quantity 6 3 12 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 3 CCB (Output) CCB (Extension) Receiver 3 DLNB Unit
962
14th Apr 00
GSM-001-103
[GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining and diversity
A multiple cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity, is shown in Figure 9-39. Table 9-22 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Rx ANTENNA (SECTOR 3) Tx ANTENNA (SECTOR 3) Rx Tx ANTENNA ANTENNA (SECTOR 1) (SECTOR 2) Rx ANTENNA (SECTOR 1)
RF INPUT RF LOAD
Tx ANTENNA (SECTOR 2)
DLNB
Rx EXT BLOCK
DLNB
DLNB
IADU IADU
6 RF INPUT RF LOAD RF INPUT RF LOAD
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
Figure 9-39 [GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining and diversity
14th Apr 00
963
GSM-001-103
Table 9-22 Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, hybrid combining, diversity, and mediumpower duplexer Quantity 9 2 12 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 3 3-input CBF Hybrid combiner module (HCOMB) Receiver 3 1 DLNB Rx extension block Unit
964
14th Apr 00
GSM-001-103
[GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity, and mediumpower duplexer
A multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexer, is shown in Figure 9-40. Table 9-23 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx & Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)
RF INPUT RF LOAD
DUPLEXER
DLNB
Rx EXT BLOCK
DUPLEXER
DUPLEXER DLNB
DLNB
IADU IADU
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
Figure 9-40 [GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity, and mediumpower duplexer
14th Apr 00
965
GSM-001-103
Table 9-23 Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexer Quantity 6 2 12 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 3 3-input CBF Hybrid combiner module (HCOMB) Receiver 3 1 DLNB Rx extension block Transmitter/receiver 3 mediumpower duplexer Unit
966
14th Apr 00
GSM-001-103
[GSM900] 3 sector (5/5/5), with 3-input CBF, air combining, diversity, and mediumpower duplexers (3 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexers, is shown in Figure 9-41. Table 9-24 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)
DUPLEXER DLNB
IADU
RF INPUT RF LOAD
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
Extender 1 and Extender 2 M-Cell6 cabinets configured similar to the Master cabinet for Sectors 2 and 3.
Figure 9-41 [GSM900] 3 sector (5/5/5), with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector)
14th Apr 00
967
GSM-001-103
Table 9-24 Equipment required for three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector) Quantity 9 3 15 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 3 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 3 DLNB Transmitter/receiver 3 mediumpower duplexer Unit
968
14th Apr 00
GSM-001-103
[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity, and mediumpower duplexers (2 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexers, is shown in Figure 9-42. Table 9-25 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1)
DUPLEXER
DUPLEXER DLNB
RF INPUT RF LOAD
IADU
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
Figure 9-42 [GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector)
14th Apr 00
969
GSM-001-103
Table 9-25 Equipment required for three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector) Quantity 6 3 15 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 3 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 3 DLNB Transmitter/receiver 6 mediumpower duplexer Unit
970
14th Apr 00
GSM-001-103
[GSM900] 3 sector (6/6/6), with cavity combining, diversity, and highpower duplexer
A multiple cabinet, 18 TCU configuration with cavity combining, diversity, and highpower duplexers, is shown in Figure 9-43. Table 9-26 provides a summary of the equipment required for this configuration. The following rules apply: S S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. In an M-Cell6 side cabinet, a maximum of three highpower duplexers can be accommodated. An external equipment rack/cabinet is required, for a highpower duplexer, in an indoor installation.
Rx ANTENNA Tx/Rx ANTENNA
DLNB
IADU
ANT
Rx
Tx CCB (EXTENSION) CCB (OUTPUT)
highpower duplexer
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 SIDE CABINET
Extender 1 and Extender 2 M-Cell6 cabinets configured similar to the Master cabinet for Sectors 2 and 3. Each extender cabinet terminates in a highpower duplexer in the side cabinet.
Figure 9-43 [GSM900] 3 sector (6/6/6), with cavity combining, diversity, and highpower duplexer
14th Apr 00
971
GSM-001-103
Table 9-26 Equipment required for three RF cabinets, 18 TCU configuration with cavity combining, diversity, and highpower duplexer Quantity 6 3 1 18 Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU Transmitter 3 3 CCB (Output) CCB (Extension) Receiver 3 DLNB Transmitter/receiver 3 highpower duplexer Unit
972
14th Apr 00
GSM-001-103
[GSM900] 3 sector (6/6/6), with 3-input CBF, air combining, diversity, and mediumpower duplexers (3 antenna per sector)
A three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexers, is shown in Figure 9-44. Table 9-27 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 1) Rx ANTENNA (SECTOR 1)
DUPLEXER DLNB
IADU
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
14th Apr 00
973
GSM-001-103
Table 9-27 Equipment required for three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector) Quantity 9 3 18 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 3 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 3 DLNB Transmitter/receiver 3 mediumpower duplexer Unit
974
14th Apr 00
GSM-001-103
[GSM900] 3 sector (6/6/6), with 3-input CBF, combining, diversity, and mediumpower duplexers (2 antenna per sector)
A three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexers, is shown in Figure 9-45. Table 9-28 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 1)
DUPLEXER
DUPLEXER DLNB
IADU
3-INPUT CBF
NonHCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
14th Apr 00
975
GSM-001-103
Table 9-28 Equipment required for three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector) Quantity 6 3 18 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 3 3-input CBF Non-hybrid combiner (Non-HCOMB) Receiver 3 DLNB Transmitter/receiver 6 mediumpower duplexer Unit
976
14th Apr 00
GSM-001-103
14th Apr 00
977
GSM-001-103
[GSM900] 3 sector (8/8/8), with cavity combining and diversity

A four cabinet, 24 TCU configuration with cavity combining, diversity, and mediumpower duplexers, is shown in Figure 9-46/ Figure 9-47. Table 9-29 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1)
DLNB 0 IN EXTENDER 2 M-Cell6 BTS CABINET DLNB 0 IN EXTENDER 1 M-Cell6 BTS CABINET DLNB 0 IN EXTENDER 3 M-Cell6 BTS CABINET IADU IN EXTENDER 2 M-Cell6 BTS CABINET IADU IN EXTENDER 1 M-Cell6 BTS CABINET IADU IN EXTENDER 3 M-Cell6 BTS CABINET
DUPLEXER 2
DUPLEXER 1
DUPLEXER 0
Rx REV Rx REV Rx REV BLOCK 2 BLOCK 1 BLOCK 0
IADU
CBF 2
CBF 1
CBF 0
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
978
14th Apr 00
GSM-001-103
TO MASTER M-Cell 6 BTS CABINET
DUPLEXER 2 DUPLEXER 1 DUPLEXER 0 Rx REV BLOCK 2 Rx REV BLOCK 1 Rx REV BLOCK 0
DLNB
IADU
CCB (EXTENSION)
CCB (OUTPUT)
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
EXTENDER 1 M-Cell6 BTS CABINET
Extender 2 and Extender 3 M-Cell6 cabinets configured similar to the Extender 1 cabinet for Sectors 2 and 3.
14th Apr 00
979
GSM-001-103
Table 9-29 Equipment required for four RF cabinets, 24 TCU configuration with cavity combining and diversity Quantity 9 4 24 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 3 3 CCB (Output) CCB (Extension) CBF Receiver 3 3 DLNB Rx extender block Transmitter/receiver 3 mediumpower duplexer Unit
980
14th Apr 00
GSM-001-103
14th Apr 00
981
GSM-001-103
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and duplexing

A multiple cabinet, 24 TCU configuration with cavity combining, diversity and both high and mediumpower duplexers, is shown in Figure 9-48/ Figure 9-49. Table 9-30 provides a summary of the equipment required for this configuration. The following rules apply: S S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. In an M-Cell6 side cabinet, a maximum of three highpower duplexers can be accommodated. An external equipment rack/cabinet is required, for a highpower duplexer, in an indoor installation.
DLNB 0 IN EXTENDER 2 M-Cell6 BTS CABINET DLNB 0 IN EXTENDER 1 M-Cell6 BTS CABINET DLNB 0 IN EXTENDER 3 M-Cell6 BTS CABINET IADU IN EXTENDER 2 M-Cell6 BTS CABINET IADU IN EXTENDER 1 M-Cell6 BTS CABINET IADU IN EXTENDER 3 M-Cell6 BTS CABINET
DUPLEXER 2
DUPLEXER 1
DUPLEXER 0
Rx REV Rx REV Rx REV BLOCK 2 BLOCK 1 BLOCK 0
IADU
CBF 2
CBF 1
CBF 0
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
Figure 9-48 [GSM900] 3 sector (8/8/8), with cavity combining, diversity and both high and mediumpower duplexers
982
14th Apr 00
GSM-001-103
TO MASTER M-Cell 6 BTS CABINET
DUPLEXER 2 DUPLEXER 1 DUPLEXER 0 Rx REV BLOCK 2 Rx REV BLOCK 1 Rx REV BLOCK 0
Tx/Rx Tx/Rx Tx/Rx ANTENNA ANTENNA ANTENNA (SECTOR 3) (SECTOR 2) (SECTOR 1)
EXTENDER 2 M-Cell6 BTS CABINET EXTENDER 1 M-Cell6 BTS CABINET
EXTENDER 2 M-Cell6 BTS CABINET EXTENDER 1 M-Cell6 BTS CABINET
DLNB
IADU
ANT
Rx 6 6 Tx CCB (EXTENSION) CCB (OUTPUT) ANT
Rx
Tx
ANT
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
Rx
Tx
highpower duplexerS EXTENDER 1 M-Cell6 BTS CABINET M-Cell6 SIDE CABINET
Extender 2 and Extender 3 M-Cell6 cabinets configured similar to the Extender 1 cabinet for Sectors 2 and 3. The Master, Extender 1 and Extender 2 cabinets terminate in a highpower duplexer in the side cabinet.
Figure 9-49 [GSM900] 3 sector (8/8/8), with cavity combining, diversity and both high and mediumpower duplexers
14th Apr 00
983
GSM-001-103
Table 9-30 Equipment required for four RF cabinets, 24 TCU configuration with cavity combining, diversity and both high and mediumpower duplexers Quantity 6 4 1 24 Antennas M-Cell6 BTS cabinet M-Cell6 side cabinet TCU Transmitter 3 3 3 CCB (Output) CCB (Extension) CBF Receiver 3 3 DLNB Rx extender block Transmitter/receiver 3 3 highpower duplexer mediumpower duplexer Unit
984
14th Apr 00
GSM-001-103
14th Apr 00
985
GSM-001-103
[GSM900] 3 sector (8/8/8), with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector)
A four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexer, is shown in Figure 9-50/ Figure 9-51. Table 9-31 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
TO EXTENDER 1 M-Cell 6 BTS CABINET
IADU
Tx ANTENNA (SECTOR 3) RF INPUT RF LOAD
Rx EXT BLOCK
DUPLEXER
DLNB
Rx EXT BLOCK
IADU IADU
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
986
14th Apr 00
GSM-001-103
Rx EXT BLOCK
RF INPUT RF LOAD
DLNB
Rx EXT BLOCK
DUPLEXER
DUPLEXER
DLNB
IADU IADU
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
14th Apr 00
987
GSM-001-103
Table 9-31 Equipment required for four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, and mediumpower duplexers (3 antenna per sector) Quantity 9 4 24 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 6 3-input CBF Hybrid combiner module (HCOMB) Receiver 3 3 DLNB Rx extension block Transmitter/receiver 3 mediumpower duplexer Unit
988
14th Apr 00
GSM-001-103
14th Apr 00
989
GSM-001-103
[GSM900] 3 sector (8/8/8), with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector)
A four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexer, is shown in Figure 9-52/ Figure 9-53. Table 9-32 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 3) TO EXTENDER 1 M-Cell 6 BTS CABINET
DUPLEXER IADU
RF INPUT RF LOAD
DUPLEXER
Rx EXT BLOCK
DUPLEXER
DLNB
Rx EXT BLOCK
IADU IADU
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
990
14th Apr 00
GSM-001-103
DUPLEXER Rx REV BLOCK 1
RF INPUT RF LOAD
DUPLEXER
DUPLEXER
DUPLEXER
DLNB
Rx EXT BLOCK
DUPLEXER
DLNB
IADU IADU
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
HCOMB
3-INPUT CBF
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B A B
T C U
T C U A B
T C U A B
14th Apr 00
991
GSM-001-103
Table 9-32 Equipment required for four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector) Quantity 6 4 24 Antennas M-Cell6 BTS cabinet TCU Transmitter 6 6 3-input CBF Hybrid combiner module (HCOMB) Receiver 3 3 DLNB Rx extension block Transmitter/receiver 6 mediumpower duplexer Unit
992
14th Apr 00
GSM-001-103
14th Apr 00
993
GSM-001-103
[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 9-54. Table 9-33 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA (SECTOR 1) Tx ANTENNA (SECTOR 2) Tx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)
LNA
LNA
LNA
TxBPF
TxBPF
TxBPF
HYBRID
HYBRID
HYBRID
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-54 [DCS1800] 3 sector (2/2/2), with hybrid combining and diversity
994
14th Apr 00
GSM-001-103
Table 9-33 Equipment required for single cabinet, six TCU configuration with hybrid combining and diversity Quantity 9 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 3 TxBPF Hybrid combiner Receiver 3 LNA Unit
14th Apr 00
995
GSM-001-103
[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and mediumpower duplexer
A single cabinet, six TCU configuration with hybrid combining, diversity, and mediumpower duplexers, is shown in Figure 9-55. Table 9-34 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx/Rx ANTENNA (SECTOR 1) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 3) Rx ANTENNAS (SECTOR 1) Rx ANTENNAS (SECTOR 2) Rx ANTENNAS (SECTOR 3)
DUPLEXER
DUPLEXER
DUPLEXER
LNA
LNA
LNA
HYBRID
HYBRID
HYBRID
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
T C U A B
M-Cell6 BTS CABINET
Figure 9-55 [DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and mediumpower duplexers
996
14th Apr 00
GSM-001-103
Table 9-34 Equipment required for single cabinet, six TCU configuration with hybrid combining, diversity, and mediumpower duplexers Quantity 6 1 6 Antennas M-Cell6 BTS cabinet TCU Transmitter 3 Hybrid combiner Receiver 3 LNA Transmitter/receiver 3 mediumpower duplexer Unit
14th Apr 00
997
GSM-001-103
M-Cell2 cabinets
[GSM900] 2 carrier, single sector, with hybrid combining and diversity

A single cabinet, two TCU configuration with hybrid combining and diversity, is shown in Figure 9-56. Table 9-35 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated. An external equipment cabinet is not necessary.
DLNB
CBF
T C U A B
T C U A B
M-Cell2 BTS CABINET
Figure 9-56 [GSM900] 2 carrier, single sector, with hybrid combining and diversity
998
14th Apr 00
GSM-001-103
Table 9-35 Equipment required for single cabinet, two TCU configuration with hybrid combining and diversity Quantity 3 1 2 Antennas M-Cell2 BTS cabinet TCU Transmitter 1 CBF Receiver 1 DLNB Unit
14th Apr 00
999
GSM-001-103
[GSM900] 2 carrier, single sector, with hybrid combining, diversity, and mediumpower duplexer
A single cabinet, two TCU configuration with hybrid combining, diversity, and mediumpower duplexer, is shown in Figure 9-57. Table 9-36 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated. An external equipment cabinet is not necessary.
DUPLEXER
DLNB
CBF
T C U A B
T C U A B
M-Cell2 BTS CABINET
Figure 9-57 [GSM900] 2 carrier, single sector, with hybrid combining, diversity, and mediumpower duplexer
9100
14th Apr 00
GSM-001-103
Table 9-36 Equipment required for single cabinet, two TCU configuration with hybrid combining, diversity, and mediumpower duplexer Quantity 2 1 2 Antennas M-Cell2 BTS cabinet TCU Transmitter 1 CBF Receiver 1 DLNB Transmitter/receiver 1 mediumpower duplexer Unit
14th Apr 00
9101
GSM-001-103
[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 9-58. Table 9-37 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA Tx ANTENNA Rx ANTENNAS Rx ANTENNAS
DLNB
DLNB
CBF
CBF
T C U A B
T C U A B
M-Cell2 BTS CABINET
Figure 9-58 [GSM900] 2 sectors (1 carrier per sector), with diversity
9102
14th Apr 00
GSM-001-103
Table 9-37 Equipment required for single cabinet, two TCU configuration with diversity Quantity 6 1 2 Antennas M-Cell2 BTS cabinet TCU Transmitter 2 CBF Receiver 2 DLNB Unit
14th Apr 00
9103
GSM-001-103
[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU configuration with air combining and diversity, is shown in Figure 9-59. Table 9-38 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER LNA
TxBPF
T C U A B
T C U A B
M-Cell2 BTS CABINET
Figure 9-59 [DCS1800] 2 carrier, single sector, with air combining and diversity
9104
14th Apr 00
GSM-001-103
Table 9-38 Equipment required for single cabinet, two TCU configuration without diversity Quantity 3 1 2 Antennas M-Cell2 BTS cabinet TCU Transmitter 1 TxBPF Receiver 1 LNA Transmitter/receiver 1 mediumpower duplexer Unit
14th Apr 00
9105
GSM-001-103
[DCS1800] 2 sectors, with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 9-60. Table 9-39 provides a summary of the equipment required for this configuration. The following rules apply: S S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated. An external equipment cabinet is not necessary.
Tx ANTENNA Tx ANTENNA Rx ANTENNAS Rx ANTENNAS
LNA
LNA
TxBPF
TxBPF
T C U A B
T C U A B
M-Cell2 BTS CABINET
Figure 9-60 [DCS1800] 2 sectors, with diversity
9106
14th Apr 00
GSM-001-103
Table 9-39 Equipment required for single cabinet, two TCU configuration without diversity Quantity 6 1 2 Antennas M-Cell2 BTS cabinet TCU Transmitter 2 TxBPF Receiver 2 LNA Unit
M-Cellarena macro enclosure

[GSM900/DCS1800] 2 carrier
A single BTS enclosure, double TRX configuration, with boosted output (in a separate enclosure), two antennas are provided.
14th Apr 00
9107
Microcell RF configuration
GSM-001-103
Microcell RF configuration
M-Cellarena enclosure
[GSM900/DCS1800] 2 carrier
A single BTS enclosure, double TRX configuration, single antenna is provided.
9108
14th Apr 00
Chapter 10
Previous BSC planning steps and rules
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 10 Previous BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . . Assigning BTSs to LCFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR2 and earlier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
101 101 102 102 103 104 104 105 105 107 108 109 1010 1010 1010 1010 1011 1011 1012 1013 1014 1015 1015 1015 1016 1017 1019 1020 1021 1021 1021 1022 1023 1026 1026 1026 1027 1027 1028 1029 1029 1029 1030 1031 1032 1032 1032 1033
14th Apr 00
iii
GSM-001-103
Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1034 1034 1034 1035 1036 1036 1036 1036 1037 1037 1037 1037 1039 1039 1039 1039 1040 1040 1040 1040 1041 1041 1041 1041 1042 1042 1042 1042 1043 1043 1043 1043 1044 1044 1044 1044 1045 1045 1045 1045 1046 1046
iv
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter provides the planning steps and rules for the previous generation BSC equipment. The planning steps and rules for the previous generation BTS equipment are in Chapter 11 of this manual. This chapter contains: S S BSC planning overview. Capacity calculations. S Determining the required BSS signalling link capacities. Determine the number of RSLs required. Determine the number of MTLs required. BSC GPROC functions and types.
BSC planning. Planning rules for BSC to BTS links (E1/T1). Planning rules for BSC to BTS links (RSL). Planning rules for BSC to MSC links (MTL). Planning rules for the digital modules. Planning rules for the digital shelf power supply.
14th Apr 00
101
GSM-001-103

Introduction
To plan the equipage of a BSC certain information must be known. The major items include: S S S S S S S S S S S S The number of BTS sites to be controlled. The number of RF carriers (RTF) at each BTS site. The number of TCHs at each site. The total number of TCHs under the BSC. The number of cells controlled from each BSC site should not exceed the maximum per BSC given in the BSC system capacity section of Chapter 5. The physical interconnection of the BTS sites to the BSC. The location of the XCDR function. The path for the OML links to the OMC. The use of E1 or T1 links. The use of balanced or unbalanced E1. The traffic load to be handled (also take future growth into consideration). The number of MSC to BSC trunks.
102
14th Apr 00
GSM-001-103

Planning a BSC involves the following steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. Plan the number of E1 or T1 links between the BSC and BTS site(s), refer to the section Determine the required BSS signalling link capacities in this chapter. Plan the number of RSL links between the BSC and BTS site(s), refer to the section Determine the number of RSLs required in this chapter. Plan the number of MTL links between the BSC and MSC, refer to the section Determine the number of MTLs required in this chapter. Plan the number of GPROCs required, refer to the section Generic processor (GPROC, GPROC2) in this chapter. Plan the number of XCDR/GDPs required, refer to the section Transcoding in this chapter. Plan the number of MSI/MSI-2s required, refer to the section Multiple serial interface (MSI, MSI-2) in this chapter. Plan the number of KSWs and timeslots required, refer to the section Kiloport switch (KSW) in this chapter. Plan the number of BSU shelves, refer to the section BSU shelves in this chapter. Plan the number of KSWXs required, refer to the section Kiloport switch extender (KSWX) in this chapter. Plan the number of GCLKs required, refer to the section Generic clock (GCLK) in this chapter. Plan the number of CLKXs required, refer to the section Clock extender (CLKX) in this chapter. Plan the number of LANXs required, refer to the section LAN extender (LANX) in this chapter. Plan the number of PIXs required, refer to the section Parallel interface extender (PIX) in this chapter. Plan the number of BIB or T43s required, refer to the section Line interfaces (BIB, T43) in this chapter. Plan the power requirements, refer to the section Digital shelf power supply in this chapter. Plan the number of BBBXs required, refer to the section Battery backup board (BBBX) in this chapter. Verify the planning process, refer to the section Verify the number of BSU shelves and BSSC cabinets in this chapter.
14th Apr 00
103
GSM-001-103
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC, GPROC2) and the throughput capacities of its data links, determines the number of supported traffic channels (TCHs). These capacities are limited by the ability of the processors, and links to handle the signalling information associated with these TCHs. This section provides information on how to calculate processor requirements, signalling link capacities and BSC processing capacities. This section describes: S S S S Traffic models. The required BSS signalling link capacities. BSC GPROC functions and types. The number of GPROCs required.
104
14th Apr 00
GSM-001-103

BSC signalling traffic model
For a GSM system the throughput of network entities, including sub-components, depends upon the assumed traffic model used in the network design or operation. Traffic models are fundamental to a number of planning actions. The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends on its ability to process information transported through signalling links connecting it to the other network elements. These elements include MSC, BTSs, and the OMC-R. Depending on its device type and BSC configuration, a GPROC may be controlling signalling links to one or more other network elements. A capacity figure can be stated for each GPROC device type in terms of a static capacity such as the number of physical signalling links supported, and a dynamic capacity such as processing throughput. In general telephony environments, processing and link throughput capacities can be stated in terms of the offered call load. To apply this for the GSM BSC, all signalling information to be processed by the BSC, is related to the offered call load (the amount of traffic offered/generated by subscribers). When calls are blocked due to all trunks or all TCHs busy, most of the signalling associated with call setup and clearing still takes place, even though few or no trunk resources are utilized. Therefore, the offered call load (which includes the blocked calls) should be used in planning the signalling resources (for example; MTLs and RSLs). In the case where the BSC has more than enough trunks to handle the offered traffic, adequate signalling resources should be planned to handle the potential carried traffic. The trunk count can be used as an approximate Erlang value for the potential carried load. As a result, the signalling links and processing requirements should be able to handle the greater of the following: S S The offered load. The potential carried load.
To determine the link and processing requirements of the BSC, the number of trunks or the offered call load in Erlangs (whichever is greater) should be used. BSC capacity planning requires a model that associates the signalling generated from all the pertinent GSM procedures: call setup and clearing, handover, location updating and paging, to the offered call load. To establish the relationship between all the procedures, the traffic model expresses processing requirements for these procedures as ratios to the number of call attempts processed. The rate at which call attempts are processed is a function of the offered call load and the average call hold time. Figure 10-1 graphically depicts various factors that should be taken into account when planning a BSS.
14th Apr 00
105
GSM-001-103
MSC TRANSCODER
106
14th Apr 00
GSM-001-103
Typical parameter values

The parameters required to calculate BSC processing and signalling link capacities are listed in Table 10-1 with their typical values. Two methods for determining capacity are given. The first method is based on the typical call parameters given in Table 10-1 and simplifies planning to lookup tables, or simple formulae indicated in standard traffic model planning steps. When the call parameters being planned for differ significantly from the standard traffic model given in Table 10-1 in this case more complex formulae must be used as indicated in non-standard traffic model planning steps. Table 10-1 Typical call parameters Busy hour peak signalling traffic model Call duration Ratio of SMSs per call Number of handovers per call Ratio of location updates to calls Ratio of IMSI detaches to calls Location update factor Paging rate in pages per second Ratio of intra-BSC handovers to all handovers Percent link utilization (MSC to BSS) Percent link utilization (BSC to BTS) Blocking for TCHs Blocking for MSCBSS Trunks Parameter reference T = 120 seconds S = 0.1 H = 2.5
l=2
I =0 L=2 P=3 i = 0.6 U (MSC BSS) = 0.20 U (BSC BTS) = 0.25 PBTCHs = 2% PBTrunks = 1%
The location update factor (L) is a function of the ratio of location updates to calls (l), the ratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSI detach is disabled) as in the first formula given below. When IMSI detach is enabled, the second or third of the formulas given below should be used. The type of IMSI detach used is a function of the MSC. If IMSI detach is disabled: L=I If IMSI detach type 1 is enabled: L = I + 0.2 * I If IMSI detach type 2 is enabled: L = I + 0.5 * I
14th Apr 00
107
GSM-001-103
Table 10-2 Other parameters used in determining GPROC and link requirements Busy hour peak signalling traffic model Number of MSC BSC trunks Number of BTSs per BSS Number of cells per BSS Pages per call N B C PPC = P * (T/N) Parameter reference
Assumptions used in capacity calculations

To calculate link and processing capacity values, certain signalling message sequence patterns and message sizes have been assumed for the various procedures included in the signalling traffic model. New capacity values may have to be calculated if the actual message patterns and message sizes differ significantly from those assumed. The assumptions used for the capacity calculations in this manual are summarized below. The number of uplink and downlink messages with the respective average message sizes (not including link protocol overhead) for each procedure are provided in Table 10-3. Table 10-3 Procedure capacities Procedure Call setup and clearing Handover, incoming and outgoing Location update SMS-P to P (see note below) IMSI detach (type 1) IMSI detach (type 2) Paging MSC to BSC link 5 downlink messages with average size of 30 bytes 6 uplink messages with average size of 26 bytes 4 downlink messages with average size of 37 bytes 5 uplink messages with average size of 38 bytes 5 downlink messages with average size of 30 bytes 6 uplink messages with average size of 26 bytes 7 downlink messages with average size of 30 bytes 7 uplink messages with average size of 42 bytes 1 downlink messages with average size of 30 bytes 1 uplink messages with average size of 42 bytes 3 downlink messages with average size of 30 bytes 3 uplink messages with average size of 26 bytes 1 downlink message with average size of 30 bytes
NOTE The actual number and size of messages required by SMS depend on the implementation of the SMS service centre. The numbers given are estimates for a typical implementation. These numbers may vary.
An additional assumption, which is made in determining the values listed in Table 10-3, is that the procedures not included in the traffic model are considered to have negligible effect.
108
14th Apr 00
GSM-001-103
Link capacities
The level of link utilization is largely a matter of choice of the system designer. A design that has more links running at a lower message rate can have the advantage of offering better fault tolerance since the failure of any one link affects less signalling traffic. Reconfiguration around the fault could be less disruptive. Such a design could offer reduced queueing delays for signalling messages. A design that utilizes fewer links at a higher message rate, reduces the number of 64 kbit/s circuits required for signalling, and potentially reduces the number of resources (processors, data ports) required in the MSC. It is recommended that the C7 links be designed to operate at no more than 20% link utilization. If higher link utilizations are used, the controlling GPROCs (LCFMTLs) may become overloaded. C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from the failed link to be redistributed among the remaining functioning links. A C7 link set officially has at least two and at most 16 links. The failure of links, for any reason, cause the signalling to be shared across the remaining members of the link set. Therefore, the design must plan for reserve link and processing capacity to support a certain number of failed signalling links.
14th Apr 00
109
GSM-001-103

Introduction
Each BTS site which is connected directly to the BSC, including the first site in a daisy chain, must be considered individually. Once individual RSL requirements are calculated the total number of LCFs can be determined for the BSC.
The following factors should be considered when planning the provision of RSL (LAPD signalling) links from the BSC to BTS sites: S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTS site. One link can support multiple collocated cells. As the system grows, additional signalling links may be required. Refer to the section Determining the required BSS signalling link capacities in this chapter to determine the number of RSL links required. If closed loop daisy chains are used, each site requires an RSL in both directions. The provision of additional RSL links for redundancy.
S S

The number of BSC to BTS signalling links (RSL) must be determined for each BTS. This number depends on the number of TCHs at the BTS. Table 10-4 gives the number of RSLs required for a BTS to support the given number of TCHs. These numbers are based on the typical call parameters given in the standard traffic model column of Table 10-1. If the call parameters differ significantly from the standard traffic model, use the formulae for the non-standard traffic model. Table 10-4 Number of BSC to BTS signalling links n = number of TCHs at the BTS n <= 30 30 < n <= 60 60 < n <= 90 90 < n <= 120 120 < n <= 150 150 < n <= 180 180 < n <= 210 210 < n <= 240 NOTE A BTS shall support either 64 kbit/s RSLs or 16 kbit/s RSLs, but not both. Number of 64 kbit/s RSLs 1 1 1 1 2 2 2 2 Number of 16 kbit/s RSLs 1 2 3 4 5 6 7 8
1010
14th Apr 00
GSM-001-103

If the call parameters differ significantly from those given in Table 10-1, use the following formula to determine the required number of 64 kbit/s RSLs (rounded up to the next nearest integer). N BSC*BTS + (n * (95 ) 67 * S ) 35 * H ) 25 * L)) ) 6*P (1000 * U * T) (1000 * U)
If the call parameters differ significantly from those given in Table 5-2, use the following formula to determine the required number of 16 kbit/s RSLs (rounded up to the next nearest integer). N BSC*BTS + Where: (n * (95 ) 67 * S ) 35 * H ) 25 * L)) ) 6*P *4 (1000 * U) (1000 * U * T) is: the number of MSC to BSC signalling links. the number of TCHs at the BTS site. the ratio of SMSs to calls. the number of handover per call. the location update factor. the percent link utilization (0.25). the average call duration. the paging rate in pages per second.
NBSC to BTS n S H L U T P
BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links may be added, if required. N+ Where: N nTCH L16 L64 NOTE This formula includes both L16 and L64 to provide necessary number of RSLs. As above, either L16 or L64 RSL can be used, but not both, to a single BTS. is: [(nTCH + L16) / 4] + L64 31 the minimum number of E1 links required (rounded up to an integer). the number of traffic channels at the BTS. the number of 16 kbit/s RSLs (LAPD links). the number of 64 kbit/s RSLs (LAPD links).
14th Apr 00
1011
GSM-001-103
BSC to BTS T1 interconnect planning actions

Determine the number of T1 links required to connect to a BTS. Redundant links may be added, if required. N+ Where: N nTCH L16 L64 NOTE This formula includes both L16 and L64 to provide necessary number of RSLs. As above, either L16 or L64 RSL can be used, but not both, to a single BTS. is: [(nTCH + L16) / 4] + L64 24 the minimum number of T1 links required (rounded up to an integer). the number of traffic channels at the BTS. the number of 16 kbit/s RSLs (LAPD links). the number of 64 kbit/s RSLs (LAPD links).
1012
14th Apr 00
GSM-001-103
Calculate the number of LCFs for RSL processing

LCFs for BSC to BTS links and Layer 3 call processing
There are three steps needed to determine the number of LCF GPROCs required to support the BSC to BTS signalling links (RSL) and layer 3 call processing. 1. 2. 3. Calculate the number of LCFs required to support the RSLs. Calculate the number of LCFs required to support the layer 3 call processing. The larger of the numbers calculated in steps 1 and 2 is the number of LCFs required to support the RSLs signalling links and layer 3 call processing.
Step 1
Determine the number of LCFs required to support RSLs. There are two equations; one for release GSR3; and one for GSR2 and 1.4.x.x. For GSR3 using only GPROC2. G RSL + (R ) 2 * B) 120 (R ) 2 * B) 40
For GSR2 and 1.4.x.x, or GSR3 using GPROC. G RSL + Where: GRSL R B is:
the number of LCFs required to support the BSC to BTS signalling links (RSL). the number RTFs (radio carriers). the number of BTS sites.
Step 2
The second step is to determine the number of GPROCs required to support the layer 3 call processing. There are two methods for calculating this number. The first is used when the call parameters are similar to those listed in Table 10-1. The second method is to be used when call parameters differ significantly from those listed in Table 10-1.

For a GPROC2: G L3 + For a GPROC: G L3 + n ) B ) C 440 15 35 Where: GL3 n B C is: the number of LCF GPROCs or LCF GPROC2s required to support the layer 3 call processing. the number of TCH under the BSC. the number of BTS sites. the number of cells. n ) B ) C * 1 440 15 35 2.5
14th Apr 00
1013
GSM-001-103

If the call parameters differ significantly from those given in Table 10-1, the alternative formula given below should be used to determine the recommended number of LCFs. For a GPROC2: G L3 + n * (1 ) 0.7 * S ) 0.5 * H * (1 * 0.3 * i) ) 0.5 * L) ) (0.006 ) 0.02 * P) * B ) C * 1 (11.3 * T) 2.5 35 For a GPROC: G L3 + (n * (1 ) 0.7 * S ) 0.5 * H * (1 * 0.3 * i) ) 0.5 * L)) ) (0.006 ) 0.02 * P) * B ) C (11.3 * T) 35 Where: GL3 n S H i L T P B C is: the number of LCF GPROCs or LCF GPROC2s required to support the layer 3 call processing. the number of TCHs under the BSC. the ratio of SMSs to calls. the number of handover per call. the ratio of intra-BSC handover to all handover. the location update factor. the average call duration. the paging rate in pages per second. the number of BTS sites. the number of cells.
Step 3
The number of LCFs required is the greater of GRSL and GL3.
Assigning BTSs to LCFs

The BTSs must be assigned to the LCFs in such a way as to not overload any one LCF. Verify that the following conditions are met for each LCF: For a GPROC2: 2 * (number of RSLs) + number of carriers supported is NOT greater 120 for GSR3. For a GPROC: 2 * (number of RSLs) + number of carriers supported is NOT greater than 40. NOTE If these conditions are exceeded, one or more additional processors will be needed to share the load.
1014
14th Apr 00
GSM-001-103

Introduction
MTLs carry signalling traffic between the MSC and BSC. The number of required MTLs depends upon the BSS configuration size and traffic model. MTLs are carried on E1 or T1 links between the MSC and BSC, which are also used for traffic.
The following factors should be considered when planning the links from the BSC to MSC: S Determine traffic requirements for the BSC. Traffic may be determined using either of the following methods: or Sum the traffic potential of each BTS under the BSC; determined by the number of TCHs available, the number of TCHs required or the subscriber potential. Multiply the number of subscribers expected to use the BSC by the average traffic per subscriber.
Determine the number of trunks to support the traffic requirements of the BSC using Erlang B tables at the required blocking rate.
14th Apr 00
1015
GSM-001-103

The number of MSC to BSC signalling links (MTL) required depends on the desired link utilization, the type and capacity of the GPROCs controlling the MTLs. C7 uses a 4 bit number, the Signalling Link Selection (SLS) generated by the upper layer to load share message traffic among the in service links of a link set. When the number of in service links is not a power of 2, some links may experience a higher load than others. The number of MTLs is a function of the number of MSC to BSC trunks or the offered call load. Table 10-5 gives the recommended minimum number of MSC to BSC signalling links based on the typical call parameters given in Table 10-1. The value for N is the greater of the following: S S The offered call load (in Erlangs) from all the BTSs controlled by the BSC whichever is greater. The potential carried load (approximately equal to the number of MSC to BSC trunks).
The offered call load for a BSS is the sum of the offered call load from all of the cells of the BSS. The offered call load at a cell is a function of the number TCHs and blocking. As blocking increases the offered call load increase. For example, for a cell with 15 TCHs and 2% blocking, the offered call load is 9.01 Erlangs. Table 10-5 Number of MSC to BSC signalling links N = the number of MSC to BSC Trunks or the offered load from the BTSs (whichever i th greatest) ( hi h is the t t) N <= 145 145< N <=290 290 < N <= 385 385 < N <= 580 580 < N <= 775 775 < N <= 1160 1160 < N <= 1375 NOTE The capacities shown are based on the standard traffic model shown in Table 10-1. Minimum number of MTLs 1 2 3 4 6 8 16 Recommended number of MTLs 2 3 4 5 7 9 16
(each MTL at <= 20% link utilization)
1016
14th Apr 00
GSM-001-103

If the call parameters differ significantly from those given in Table 10-1, the following procedure is used to determine the required number of MSC to BSC signalling links: 1. Use the formula given below to determine the maximum number of Erlangs supported by a C7 signalling link (nllink). nl link + 2. (1000 * U * T) ((67 ) 47 * S ) 31 * H * (1 * 0.8 * i) ) 25 * L) ) 14 * P PC)
Use the formula given below to determine the maximum number of Erlangs supported by a GPROC or GPROC2 (LCFMTL) supporting a C7 signalling link (nlLCFMTL).
For a BSC with a mix of GPROC and GPROC2: nl LCF*MTL + 3.6 * T ((1 ) 0.7 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.5 * L) ) P PC * (0.01 * B ) 0.05))
For a BSC with only GPROC2: nl LCF*MTL + 3. 4. 2.5 * (3.6 * T) ((1 ) 0.7 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.5 * L) ) P PC * (0.01 * B ) 0.05))
The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is the smaller of the two numbers from Steps 1 and 2. Since the signalling traffic is uniformly distributed over 16 logical links, and these logical links will be assigned to the MTLs (physical links). We need to first determine the amount of traffic each logical link holds (nllogical): nl logical + N 16
5.
Next we need to determine the number of logical links each MTL (physical link) can handle (nlog-per-MTL): n log*per*MTL + ROUND DOWN nl min nl logical
6.
Finally, the number of required MTLs (mtls) is: mtls + ROUND UP 16 n log*per*MTL ) R v 16
NOTE mtls should not exceed 16
14th Apr 00
1017
GSM-001-103
Where:
U T S H i L PPC B mtls ROUNDUP N
is:
the percent link utilization (0.25). the average call duration. the ratio of SMSs to calls. the number of handover per call. the ratio of intra-BSC handover to all handover. the location update factor. the number of pages per call. the number of BTSs supported by the BSC. the number of MSC to BSC signalling links (MTL). to the power of. rounding up to the next integer. the greater of either the offered traffic load or potential traffic load carried (approximately equal to the number of MSC to BSC trunks).
1018
14th Apr 00
GSM-001-103
Calculate the number of LCFs for MTL processing

The purpose of the LCF GPROC or LCF GPROC2 device type is to support the functions of MSC link protocol, layer 3 call processing, and the BTS link protocol. It is recommended that an LCF GPROC supports either an MTL or one to eight BTSs, with up to 15 RSLs and layer 3 call processing; and that an LCF GPROC2 supports either two MTLs or one to 15 BTSs (GSR3), with up to 31 RSLs and layer 3 call processing. NOTE It is not recommended that an LCF support both an MTL and BSC to BTS signalling links. The higher capacities available with GPROC2 are only achieved if GPROC2s are the only processor type in use in a GSR3 system. If GPROC is also used then GPROC planning formulae should be used, even for GPROC2.
LCFs for MSC to BSC links

Since one LCF GPROC can support one MTL, the number of required LCF is the same as the number of required MTLs (MSC to BSC links) obtained from Table 10-1 or from mtls calculated in the non-standard traffic model from the previous section. For GPROC2, if the number of required MTLs is obtained from Table 10-1 the number of LCF is: N LCF + ROUNDUP MTLs 2 However, if the traffic model does not conform to the standard model: N LCF + mtls, otherwise: N LCF + ROUND UP Where: NLCF ROUND UP mtls nllink nlLCF-MTL is: mtls 2 if 2 < nl link u nl LCF*MTL
the number of LCF GPROC2s required. rounding up to the next integer. calculated in the previous section. calculated in the previous section. calculated in the previous section.
14th Apr 00
1019
GSM-001-103
MSC to BSC signalling over a satellite link

The BSC supports preventative cyclic retransmission (PCR) to interface to the MSC over a satellite link. PCR retransmits unacknowledged messages when there are no new messages to be sent. This puts an additional processing load on the GPROCs (LCFMTLs) controlling the C7 signalling links. It is recommended that when PCR is used, that the number of MTLs (and thus the number of LCFMTLs) be doubled from the number normally required.
1020
14th Apr 00
GSM-001-103

Introduction
The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as a generic control processor board. GPROCs are assigned functions and are then known by their function names. This section describes the BSC GPROC types and their functions. The BSC configuration type and GPROC device type, are essential factors for BSC planning.
GPROC functions and types

There are two GPROC hardware types, GPROC and GPROC2. GPROC2 is needed, in GSR3, for master processor functionality. The GPROC is the basic building block of a distributed architecture. The GPROC provides the processing platform for the BSC. By using multiple GPROCs software tasks can be distributed across GPROCs to provide greater capacity. The set of tasks that a GPROC is assigned, depends upon the configuration and capacity requirements of the BSC. Although every GPROC is similar from a hardware standpoint, when a group of tasks are assigned to a GPROC, it is considered to be a unique GPROC device type or function in the BSC configuration management scheme. There are a limited number of defined task groupings in the BSC, which result in the naming of four unique GPROC device types for the BSC. The processing requirement of a particular BSC determines the selection and quantity of each GPROC device type. The possible general task groupings or functions for assignment to GPROCs are: S S S S S S S S S BSC common control functions. OMC communications OML (X.25) including statistic gathering. MSC link protocol (C7). BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD). Cell broadcast centre link (CBL).
The defined GPROC devices and functions for the BSC are: Base Site Control Processor (BSP). Link Control Function (LCF). Operations and Maintenance Function (OMF). Code Storage Facility Processor (CSFP).
At a combined BSC BTS site the BTF and DHP are additional GPROC function and type in the network element. NOTE Prior to GSR3 a separate OMF was needed if OML traffic exeeded a defined threshold. With GSR3 and GPROC2 the use of a separate OMF becomes optional.
14th Apr 00
1021
GSM-001-103
BSC types
The BSC is configured as one of two types; the type is determined by the GPROCs present. NOTE With GSR3, and the use of GPROC2s, BSC type 1 is the only configuration required. S BSC type 0 Master GPROC. Running the BSP. NOTE BSC type 0 is not recommended for operating BSC. Beginning with release 1.4.0.x, BSC type 0 is not supported. S BSC type 1 Master GPROC. Running the base site control processor (BSP) and carring out operations and maintenance functionalities. Link control function (LCF). Running the radio signalling link (RSL) and layer 3 processing or MTL (C7 signalling link) communications links. S BSC type 2 Master GPROC. Running the BSP. LCF. OMF. Running the O&M, including statistics collection, and OML link (X.25 control links to the OMC-R). The number of serial links per GPROC must be determined for each site. The current values are either 8 or 16, with 16 being the default value. One link is reserved for each module, so the number of available serial links is either 7 or 15.
1022
14th Apr 00
GSM-001-103
The following factors should be considered when planning the GPROC complement: S Each BSC requires: S One master GPROC or GPROC2 (BSP). One OMF (if it is a type 2 BSC). A number of LCFs for MTLs, see Link control processor below. LCFs to support the RSL and control of the BTSs.
Optional GPROCs Include: One redundant master GPROC or GPROC2 (BSP). At least one redundant pool GPROC (can cover LCFs, OMF, and BTF). An optional dedicated CSFP.
S S S
A maximum of eight GPROCs can be supported in a BSU shelf. The master GPROC slot (20) in the first shelf should always be populated to enable communication with the OMC-R. For redundancy each BSC should be equipped with a redundant BSP and an additional GPROC to provide redundancy for the signalling LCFs. Where multiple shelves exist, each shelf should have a minimum of two GPROCs to provide redundancy within that shelf.
14th Apr 00
1023
GSM-001-103
Link control function, using GPROC2 exclusively (GSR3 only)

The planning rules for LCFs exclusively using GPROC2 are: S S A single GPROC2 will support two MTLs, each working at 20% link utilization. A single GPROC2 will support up to 15 BTS sites and 31 RSLs, limited to the following calculation: 2 * rsls ) carriers v 120 Where carriers = the total number of radios for the BTS site(s). NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limit of 24 carriers). S S The link utilization of an RSL should not exceed 25%. Up to 17 LCFs can be equipped. NOTE 1. If both GPROC2 and GPROC are used in the same BSC then the GPROC maximums apply to GPROC2. That is, the GPROC2s can handle only as much traffic as a GPROC. 2. In some cases the software will allow maximums greater than the planning guide, to allow ease of capacity expansion in future releases, but it is not supported with this software release. 3. Combining MTL and RSL processing on a single GPROC2 is not recommended. S A maximum of 15 BTS sites can be controlled by a single LCF. All RSLs (LAPD links) for the BTSs must terminate on the same GPROC2, so if return loops are used the maximum number of BTS sites will be 15 (if GPROC_slot parameter = 31). If the GPROC_slot parameter is set to 16 then at most 15 RSLs may exist which would support up to seven BTS sites. NOTE The number of serial links per GPROC must be determined for each site, the current values are either: For GPROC2; 16 or 32, with 16 being the default value. For GPROC; 8 or 16, with 16 being the default value. One link is reserved for each board (GPROC test purposes) so the number of available serial links is either 15 or 31 for GPROC2, and is 7 or 15 for GPROC. When GPROC2s are not used exclusively, the LCF planning rules using GPROCs in the next section should be used.
1024
14th Apr 00
GSM-001-103
Link control function, using GPROC

LCF planning rules using GPROC are: S S A single GPROC will support a single MTL working at 20% link utilization. A single GPROC will support up to 8 BTS sites and 15 RSLs, limited to the following calculation: 2 * rsls ) carriers v 40 Where carriers = the total number of radios for the BTS site(s). NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limit of 24 carriers). S S The link utilization of an RSL should not exceed 25%. Up to 17 LCFs can be equipped. NOTE Combining MTL and RSL processing on a single GPROC is not recommended. S A maximum of 8 BTS sites can be controlled by a single LCF. All RSLs (LAPD links) for the BTSs must terminate on the same GPROC, so if return loops are used the maximum number of BTS sites will be seven (if GPROC_slot parameter =16). If the GPROC_slot parameter is set to 8 then at most 7 RSLs may exist which would support up to 3 BTS sites. NOTE The number of serial links per GPROC must be determined for each site. For GPROC the valid values are: Eight or 16 (default). One link is reserved for each board (GPROCtest purposes) so that the number of available serial links is either 7 or 15.
14th Apr 00
1025
GSM-001-103
GPROC planning actions (GSR3)

Determine the number of GPROC or GPROC2s required. N GPROC2 + 2B ) L ) C ) R Where: NGPROC2 B L C R is: the total number of GPROC or GPROC2s required. the number of BSP GPROC or GPROC2s (2B for redundancy). the number of LCF GPROC or GPROC2s. the number of CSFP GPROC or GPROC2s. the number of pool GPROC or GPROC2s (for redundancy).
NOTE If dedicated GPROC or GPROC2s are required for either the CSFP or OMF functions then they should be provisioned separately.
GPROC planning actions (GSR2 and earlier)

Determine the number of GPROCs required. N GPROC + 2B ) L ) C ) O ) R Where: NGPROC B L C O R is: the total number of GPROCs required. the number of BSP GPROCs (2B for redundancy). the number of LCF GPROCs. the number of CSFP GPROCs. OMF GPROCs. the number of pool GPROCs (for redundancy).
Cell broadcast link

The cell broadcast link (CBL) connects the BSC to the cell broadcast centre. For typical applications (less than ten messages per second), this link can exist on the same LCF as that used to control BTSs. The CBL should not be controlled by a LCFMTL (a GPROC controlling an MTL).
1026
14th Apr 00
GSM-001-103
OMF GPROC required

The BSC type 2 configuration offloads many of the O&M functions and control of the interface to the OMC-R from the BSP. One of the major functions off loaded from the BSP is the central statistics process. When determining the total number of statistics, consider the number of instances of that statistic. N ST + (ECS < C) ) (T CS < n) ) SX25LAPD (L ) X ) B) Where: NST ECS C Tcs n SX25LAPD L X B is: the total number of statistics. the number of enabled cell statistics the number of cells. the number of traffic enabled channel statistics. the number of traffic channels. the number of X.25/LAPD statistics. the number of RSLs. the number of OMLs. the number of XBLs
NOTE The formula assumes that the same cell and channel statistics are enabled across all cells.

The BSS supports a GPROC acting as the code storage facility processor (CSFP). The CSFP allows pre-loading of a new software release while the BSS is operational. If a dedicated GPROC is to exist for the CSFP, an additional GPROC will be required. When M-Cell BTSs are connected to the BSC, a dedicated CSFP is required at the BSC and a second dedicated CSFP should be equipped for redundancy. The BSS supports a method whereby a dedicated CSFP GPROC is not required. This method is called configure CSFP and works as follows: The system can borrow certain devices and temporarily convert them into a CSFP, and when the CSFP functionality is no longer needed the device can be converted back into its previous device. The devices the system can borrow are a redundant BSP/BTP or a pooled GPROC. This functionality allows an operator who already has either a redundant BSP/BTP or a pooled GPROC in service to execute a command from the OMC-R to borrow the device and convert it into a CSFP. The operator can then download the new software load or database and execute a CSFP swap. Once the swap has been completed and verified as successful, the operator can return the CSFP back to the previous redundant or pooled device type via a separate command from the OMC-R. See the Technical Description: BSS/RXCDR (GSM-100-323A) or Service Manual: BSC/RXCDR (GSM-100-030) for more details.
14th Apr 00
1027
GSM-001-103
GPROC redundancy
BSP redundancy
The failure of the BSP GPROC will cause a system outage. If the BSC is equipped with a redundant BSP GPROC, then the system will restart under the control of the redundant BSP GPROC. If the BSC is not equipped with a redundant BSP and the BSP GPROC were to fail, the BSC would be inoperable.
Pooled GPROCs for LCF and OMF redundany

The BSS supports pooled GPROCs for LCF and OMF redundancy. By equipping additional GPROCs for spares, if an LCF or the OMF GPROC were to fail, the system software will automatically activate a spare GPROC from the GPROC pool to replace the failed GPROC.
1028
14th Apr 00
GSM-001-103
Transcoding
Transcoding
Introduction
Transcoding reduces the number of cellular subscriber voice/data trunks required by a factor of four. If transcoding takes place at the switch using a RXCDR, the number of links between the RXCDR and the BSC is reduced to approximately one quarter of the number of links between the RXCDR and the MSC. The capacity of one BSU shelf is 12 MSI slots, six of which may contain a transcoder (XCDR) or generic DSP processor (GDP); this limitation is due to power constraints. The capacity of one RXU shelf can support up to 16 GDP/XCDRs or GDPs and typically provides a better solution of the transcoding function for larger commercial systems. Refer to the section Remote transcoder planning overview in Chapter 6.

14th Apr 00
1029
Transcoding
GSM-001-103
T1 conversion
T1 to E1 conversion is needed for XCDR, but not for GDP. When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done in one of two ways. In either case the conversion may be part of an existing network element or a standalone network element which would appear as a RXCDR.

A single MSI-2 can be programmed to be E1 on one port and T1 on the other. This is the simplest method, but uses at most 24 of the transcoding circuits on the XCDR. This method has no impact on the TDM bus ports, but does require MSI slots. This method requires the number of GDP/XCDRs and additional MSI-2s to be equal to the number of T1 links.
With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1 circuits may be done. This uses the ability of the KSW to switch between groups using nailed connections. Although more efficient in XCDR utilization, this method may cause additional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2s needed for T1 to E1 conversion is: m= Where: m T E is: T+E 2
1030
14th Apr 00
GSM-001-103
Transcoding
Planning actions transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the number of E1 or T1 links for the A interface. This text should be read in conjunction with the BSS planning diagram Figure 10-1.
Using E1 links
The minimum number of E1 links required is the greater of two calculations that follow (fractional values should be rounded up to the next integer value). N= T 30 N= Where: N C X T is: C+ X+ T 31
the minimum number of E1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC) through the MSC. the number of trunks between the MSC and the BSC.
Using T1 links
The minimum number of T1 links required is the greater of two calculations that follow (fractional values should be rounded up to the next integer value). N= T 23 N= Where: N C X T is: C+ X+ T 24
the minimum number of T1 links required. the number of MTL links (C7 signalling links) to the MSC. the number of OML links (X.25 control links to the OMC) through the MSC. the number of trunks between the MSC and the BSC.
14th Apr 00
1031
GSM-001-103

Introduction
A multiple serial interface provides the interface for the links between a BSSC cabinet and other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI can interface only E1 links, an MSI-2 can interface both E1 and T1 links, but not simultaneously.
The following factors should be considered when planning the transcoder complement: S S Each MSI can interface two E1 links. Each MSI-2 can interface two T1 links. NOTE Although the MSI-2 is configurable to support either E1 or T1 on each of its two ports, it is not recommended for E1 systems. S S S S Each E1 link provides 31 usable 64 kbit/s channels. Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2. Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links connected to the site. The master MSI slot(s) should always be populated to enable communication with OMC-R. If the OML links go directly to the MSC the master slot should be filled with an GDP/XCDR, otherwise the slot should be filled with an MSI/MSI-2 which terminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 links do not need to go directly to the OMC-R, they may go to another network element for concentration.
1032
14th Apr 00
GSM-001-103

The following formulae assume local transcoding. Refer to the Multiple serial interface (MSI, MSI-2) section of Chapter 6 RXCDR planning steps and rules for MSI planning formulae for remote transcoding.
With E1 links
Determine the number of MSIs required. M= B 2 Where: M B is: the number of MSIs required. the number of BSC to BTS links.
With T1 links
Determine the number of MSI-2s required. M = B)m 2 Where: M B m is: the number of MSI/MSI-2s required. the number of BSC to BTS links. the number of MSI/MSI-2s used for T1 to E1 conversion.
14th Apr 00
1033
GSM-001-103

Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the BSC.
The following factors should be considered when planning the KSW complement: S S A minimum of one KSW is required for each BSC site. The KSW capacity of 1,024 64 kbit/s ports can be expanded by adding up to three additional KSWs, giving a total switching capacity of 4, 096 64 kbit/s ports of which, eight timeslots are reserved by the system for test purposes and are not available for use. For planning purposes assume fourteen MSI maximum per KSW. Each MSI may be replace with four GDP/XCDRs. Using twelve MSIs per KSW may reduce the number of shelves required at a cost of additional KSWs. For example, a BSC with 28 MSIs could be housed in three shelves with three KSW modules or four shelves with two KSW modules. Verify that each KSW uses fewer than 1016 ports. There are three devices in a BSC that require TDM timeslots. They are: GPROC = 16 Timeslots. GPROC2 = 32 (or 16) Timeslots. GDP or XCDR = 16 Timeslots. MSI/MSI-2 = 64 Timeslots. The number of TDM timeslots is given by. N = (G * n) + (R * 16) + (M * 64) Where: N G n R M is: the number of timeslots required. the number of GPROC/GPROC2s. 16 or 32 (depending on the value of the GPROC_slot database parameter). the number of GDP/XCDRs. the number of MSI/MSI-2s (do not count MSI-2s which are doing on board E1 to T1 conversion, when determining TDM bandwidth).
S S
For redundancy, duplicate all KSWs. NOTE Any BSC site which contains a DRIM has 352 timeslots allocated to DRIMs irrespective of the number of DRIMs equipped.
1034
14th Apr 00
GSM-001-103

Determine the number of KSWs required: N= Where: N G n R M is: (G * n) + (R * 16) + (M * 64) (1016) the number of KSWs required. the number of GPROC/GPROC2s. 16 or 32 (depending on the value of the GPROC_slot database parameter). the number of GDP/XCDRs. the number of MSI/MSI-2s (do not count MSI-2s which are doing on board E1 to T1 conversion).
14th Apr 00
1035
BSU shelves
GSM-001-103
BSU shelves
Introduction
The number of BSU shelves is normally a function of the number of GPROC/GPROC2, MSI/MSI-2s, and GDP/XCDRs required.
The following factors should be considered when planning the number of BSU shelves: S S Each BSU shelf supports up to eight GPROCs or GPROC2s, if the number of these exceed the number of slots available an additional BSU shelf is required. Each shelf is allocated to a single KSW and extension shelves are differentiated by the presence of the KSW; extension shelves are those which do not contain a primary KSW. A BSU shelf can support up to 12 MSI/MSI-2 boards. A BSU shelf can support up to six GDP/XCDRs boards. (reducing appropriately, the number of MSI/MSI-2 boards).
S S
BSU shelf planning actions

Determine the number of BSU shelves required. The number of BSU shelves required is the greater of three calculations that follow (fractional values should be rounded up to the next integer value). Bs = G 8 Bs = M+ R 12
Bs = R 6 Where: Bs G M R is: the minimum number of BSU shelves required. the number of GPROC/GPROC2s. the number of MSI/MSI-2s. the number of GDP/XCDRs.
NOTE The number of shelves may be larger if an attempt to reduce the number of KSWs is made. For GSR3 the number of shelves (cages) = 94 For GSR3 the number of cabinets = 90 There is a database limitation of 50 cabinets/shelves. M-Cell sites do not require a cage to be equipped, only a cabinet.
1036
14th Apr 00
GSM-001-103

Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element grows beyond a single shelf.
S S
Five of the redundant KSWX slots are also CLKX slots. The maximum number of KSWX slots per shelf is 18, 9 per KSW.

The number of KSWXs required is the sum of the KSWXE, KSWXL and KSWXR. N KX + NKXE ) NKXR ) NKXL N KXE + K < (K * 1) N KXR + SE N KXL + K ) S E Where: NKX NKXE NKXR NKXL K SE NOTE Ensure that SE = 0 for extension shelves and 1 for expansion shelves. is: the number of KSWX required. the number of KSWXE. the number of KSWXR. the number of KSWXL. the number of non-redundant KSWs. the number of extension selves.
14th Apr 00
1037
GSM-001-103
For example
Table 10-6 KSWX (non-redundant) Extension shelves 0 1 2 3 4 KSW (non redundant) 1 1 3 5 7 9 2 4 6 8 10 12 3 9 11 13 15 17 4 16 18 20 22 24
Table 10-7 KSWX (redundant) Extension shelves 0 1 2 3 4 KSW (redundant) 1 2 6 10 14 18 2 8 12 16 20 24 3 18 22 26 30 34 4 32 36 40 44 48
1038
14th Apr 00
GSM-001-103

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a BSU.
The following factors should be considered when planning the GCLK complement: S S S One GCLK is required at each BSC. The maximum number of GCLK slots per shelf is two. For redundancy add a second GCLK at each site in the same cabinet as the first GCLK.

14th Apr 00
1039
GSM-001-103

Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one BSU.
The following factors should be considered when planning the CLKX complement: S S S S One CLKX is required in the first BSU shelf, which contains the GCLK, when expansion beyond the shelf occurs. Each CLKX can supply the GCLK signals to six shelves. There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves (LAN extension only allows 14 shelves in a single network element). The maximum number of CLKX slots per shelf is six. NOTE The CLKX uses six of the redundant KSWX slots. S S With a CLKX, a KSWXL is required to distribute the clocks in the master and each of the expansion/extension cages. For redundancy, duplicate each CLKX (requires a redundant GCLK).

Determine the number of CLKXs required. N CLKX + ROUNDUP E * (1 ) RF) 6 Where: NCLKX ROUNDUP E RF is: the number of CLKX required. rounding up to the next integer. the number of expansion/expension shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
1040
14th Apr 00
GSM-001-103
LAN extender (LANX)
LAN extender (LANX)

Introduction

Determine the number of LANXs required. N LANX + NBSU * (1 ) R F) Where: NLANX NBSU RF is: the number of LANX required. the number of BSU shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
BSU 14
14th Apr 00
1041
GSM-001-103

Introduction

Choose the number of PIXs required. PIX 2 * number of BSUs. or PIX 8.
1042
14th Apr 00
GSM-001-103

Introduction
The following factors should be considered when planning the line interface complement: S S S S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line use a BIB. To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line use a T43 Board (T43). Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf. Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet A maximum of 24 E1/T1 links can be connected to a BSU shelf. A BSSC2 cabinet with two BSU shelves can interface 48 E1/T1 links.

The following planning actions are required: S S Determine the number and type of link (E1 or T1) to be driven. Determine the number of BIBs or T43s required. Number of MSIs Number of E1/T1 links = 3 6
Minimum number of BIBs or T43s =
14th Apr 00
1043
GSM-001-103

Introduction
The following factors should be considered when planning the PSU complement: S S S S Two DPSMs are required for each shelf in the BSSC. Two IPSMs are required for each shelf in the BSSC2 (48/60 V dc). Two EPSMs are required for each shelf in the BSSC2 (+27 V dc). For redundancy, add one DPSM, IPSM, or EPSM for each shelf.

Determine the number of PSUs required. PSUs = 2 * Number of BSUs + R F * Number of BSUs Where: RF is: Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
1044
14th Apr 00
GSM-001-103

Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an external battery to maintain power to the GPROC DRAM and the optical circuitry on the LANX in the event of a mains power failure.
The following factors should be considered when planning the BBBX complement: S One BBBX is required per shelf; if the battery backup option is to be used.

14th Apr 00
1045
GSM-001-103

Verification
After planning is complete, verify that: S S S S S S S S S S S The number of shelves is greater than one eighth the number of GPROC (or GPROC2) modules. Each non-redundant KSW has its own shelf. Each extension shelf supports extension of a single KSW. The number of KSWX, LANX, CLKX, and GPROCs is correct. The number of MSI/MSI-2 and GDP/XCDR 12 * number of shelves. The number of GDP/XCDR 6 * number of shelves. The number of BTS sites 40. The number of BTS cells 126. RSLs 80. Carriers 255. Erlangs 1375. If necessary, add extra BSU shelves. Each BSSC2 cabinet supports two BSU shelves.
1046
14th Apr 00
Chapter 11
Previous generation BTS planning and equipment descriptions
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
Chapter 11 Previous generation BTS planning and equipment descriptions . . . . . . . .

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculations for determining BTS GPROC, GPROC2 requirements . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call processing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS shelf configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for typical call mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for border location area call mix . . . . . . . . . . . . . . . . . . . . . . . BTS equipment cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types EG, FG and BTS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types AG, BG and DG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Rx signals between multiple cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . RFE planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combiner shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combining equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combiner shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplexer planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
111 111 112 112 113 114 114 114 116 116 117 117 117 118 119 1110 1111 1112 1113 1113 1113 1114 1114 1114 1114 1115 1116 1117 1117 1117 1118 1118 1119 1119 1119 1119 1120 1120 1120 1120 1121 1121 1121 1121 1122 1122 1122 1123
14th Apr 00
iii
GSM-001-103
Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot switch (TSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local area extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital radio interface extender (DRIX3c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TopCell BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU without diversity . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, five DRCU/SCUs with combining . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, six DRCU/SCUs with combining and diversity . . . . . . . . . . . . . . . Single cabinet, multiple antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, multiple antennas with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
1124 1124 1124 1124 1125 1125 1125 1125 1126 1126 1126 1126 1127 1127 1127 1127 1128 1128 1128 1128 1129 1129 1129 1129 1130 1130 1130 1130 1131 1131 1131 1131 1132 1132 1132 1132 1133 1133 1133 1133 1134 1134 1135 1135 1136 1137 1137 1139 1140 1142 1145 1147
14th Apr 00
GSM-001-103
Multiple cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, four DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, ten DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, multiple antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Six sector configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sixsector BTS6 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1149 1149 1151 1153 1154 1156
14th Apr 00
GSM-001-103
vi
14th Apr 00
GSM-001-103
Chapter overview
Chapter overview
Introduction
This chapter (included for reference only) is divided into two sections and describes: S S BTS planning steps and rules. BTS RF configurations.
14th Apr 00
111
GSM-001-103

Introduction
This section provides the planning steps and rules for the BTS, including ExCell and TopCell. This chapter contains: S S S BTS planning overview: Capacity calculations for the number of control channels required. Capacity calculations for the number of GPROCs required. Planning rules for BTS cabinets. Planning rules for the receiver front end. Planning rules for the transmit combiner shelf. Planning rules for the carrier equipment. Planning rules for the line interconnections. Planning rules for the digital modules. Planning rules for the digital shelf power supply.
112
14th Apr 00
GSM-001-103

BTS site
The steps required to plan a BTS site (including ExCell and TopCell sites) are listed below: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. Determine if the site has equipment shelters. Determine the number of BTS cabinets required, refer to the section BTS cabinets in this chapter. Determine the receiver front end configuration, refer to the section Receiver front end in this chapter. Determine the transmit combining configuration, refer to the section Transmit combiner shelf in this chapter. Determine the number of bandpass filters required, refer to the section Duplexer in this chapter. Determine the antenna configuration, refer to the section Duplexer in this chapter. Determine the amount of carrier equipment required, refer to the section Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX) in this chapter. Determine the number of E1/T1 line interfaces required, refer to the section Line interface (BIB, T43) in this chapter. Determine the number of MSIs required, refer to the section Multiple serial interfaces (MSI, MSI-2) in this chapter. Determine the number of GPROC, GPROC2s required, refer to the section Generic processor (GPROC, GPROC2) in this chapter. Determine the number of TSWs required, refer to the section Timeslot switch (TSW) in this chapter. Determine the number of KSWXs required, refer to the section Kiloport switch extender (KSWX) in this chapter. Determine the number of GCLKs required, refer to the section Generic clock (GCLK) in this chapter. Determine the number of CLKXs required, refer to the section Clock extender (CLKX) in this chapter. Determine the number of LANXs required, refer to the section LAN extender (LANX) in this chapter. Determine the number of PIXs required, refer to the section Parallel interface extender (PIX) in this chapter. Determine the number of DRIX3cs required, refer to the section Digital radio interface extender (DRIX3c) in this chapter. Determine the number of BBBXs boards required, refer to the section Battery backup board (BBBX) in this chapter. Determine the power requirements, refer to the section Digital shelf power supply in this chapter.
14th Apr 00
113
GSM-001-103
Introduction
This section provides information on how to determine the number of control channels and the number of GPROC, GPROC2s required at a BTS. This information is required for the sizing of the links to the BSC, and is required when calculating the exact configuration of the BSC required to support a given BSS.
Typical call parameters

The number of control channels and GPROC, GPROC2s required at a BTS depend on a set of call parameters; typical call parameters for BTS planning are given in Table 11-1. Table 11-1 Typical parameters for BTS call planning Parameter Call duration Ratio of SMSs per call Ratio of location updates to calls: non-border location area Ratio of location updates to calls: border location area Ratio of IMSI detaches to calls Location update factor: non-border location area (see below) Location update factor: border location area (see below) Number of handovers per call Paging Rate in pages per second Time duration for location update Time duration for SMSs Time duration for call setups Guard time for SDCCHs Assumed Value T = 120 seconds S = 0.1 l=2 l=7 Id = 0 L=2 L=7 H = 2.5 P=3 TL = 4 seconds TSMS = 6 seconds TC = 5 seconds Tg = 4 seconds
114
14th Apr 00
GSM-001-103
Table 11-1 Typical parameters for BTS call planning Parameter Probability of blocking for TCHs Probability of blocking for SDCCHs Assumed Value PB-TCH < 2% PB-SDCCH < 1%
The location update factor (L) is a function of the ratio of location updates to calls (I), the ratio of IMSI detaches to calls (Id) and whether the short message sequence (type 1) or long message sequence (type 2) is used for IMSI detach; typically Id = 0 (that is IMSI detach is disabled) as in the first formula given below. When IMSI detach is enabled, the second or third of the formulas given below should be used. The type of IMSI detach used is a function of the MSC. If IMSI detached is disabled: L=I If IMSI detach type 1 is enabled: L = I + 0.2 * I d If IMSI detach type 2 is enabled: L = I + 0.5 * I d
14th Apr 00
115
GSM-001-103

Introduction
There are four types of air interface control channels, they are: S S S S S S S Broadcast control channel (BCCH). Common control channel (CCCH). Standalone dedicated control channel (SDCCH). Cell broadcast channel (CBCH), which uses one SDCCH.
There are three configurations of control channels, each occupies one radio timeslot: A combined control channel. One BCCH plus three CCCH plus four SDCCH. A non-combined control channel. One BCCH plus nine CCCH (no SDCCH). An SDCCH control channel. Eight SDCCH. Each sector/cell requires a BCCH, so at least one of the first two configurations is always required. The number of air interface control channels required for a site, is dependent on the: S S S S S Number of pages. Location updates. Short message services. Call loading. Setup time.
Only the number of pages and access grants affects the CCCH. The other information uses the SDCCH.
116
14th Apr 00
GSM-001-103
Calculations for determining BTS GPROC, GPROC2 requirements
Introduction
This section discusses the basic planning dependencies for determining the number of GPROC, GPROC2s required for a BTS site. Some background information regarding the call processing functions at the BTS is also provided.
Call processing functions

Three major call processing functions exist at a BTS. These are: S S S Cell resource manager (CRM). Radio resource state machine (RRSM). Radio subsystem (RSS).
The CRM and RRSM are associated with the call processing function for the entire BTS site. The BTS site supports a single instance of the CRM and RRSM and multiple instances of RSS. An instance of RSS controls a number of RTFs. Each instance of RSS only performs call processing for its assigned, individual, or group of digital radio interfaces (DRIMs). A DRIM is controlled by one instance of RSS, and must reside in the same shelf as the GPROC, GPROC2 running the instance of RSS. A DRIM provides the processor interface to one DRCU/SCU/TCU. The DRIM, DRIX, and DRCU/SCU/TCU are viewed as providing one carrier by the GPROC, GPROC2. For a remote BTS site, that is a site that is remote from the BSC, the base transceiver processor (BTP), undertakes the master operations and maintenance (O&M) function for the site, together with the CRM and RRSM functions. The term BTP refers to the GPROC, GPROC2 performing the CRM and RRSM functions. The term digital host processor (DHP) refers to the GPROC, GPROC2 performing the call processing function of RSS. When the BTS is colocated with the BSC, the CRM and RRSM functions are performed by the BTF. The same planning rules apply to a BTF as the BTP.
14th Apr 00
117
GSM-001-103
GPROC, GPROC2 management

This section discusses topics associated with the GPROC, GPROC2. These are the max_dris parameter, the reassign command, and redundancy considerations.
Maximum number of DRIMs

The max_dris parameter defines the maximum number of DRIMs that may be controlled from the BTP or DHP. The parameter can be changed on an individual BTP or DHP basis. When the sum of max_dris for all BTPs and DHPs in a shelf is less than the number of DRIMs in the shelf, only the number of DRIMs equivalent to the sum of max_dris will come into service. For example, if a shelf has five DRIMs with two DHPs (and no BTP), and assuming that the max_dris parameter is set to 2, for both the DHPs (giving a total of four), then only four of the DRIMs will come into service, and will be able to support active RTFs. For the purposes of redundancy, when equipping additional DHPs in a BTS shelf, the max_dris parameter for each DHP must be set to take account if a DHP fails. This means that the sum of max_dris must still be equal to, or greater than, the number of DRIMs equipped in the specific shelf after the failure of a GPROC, GPROC2 in the shelf.
Control of DRIM loading

The system software attempts to balance the DRIM process load across the GPROC, GPROC2s in a shelf. Unbalanced conditions can arise where certain GPROC, GPROC2s are heavily loaded, while others are lightly loaded. The DRIM process load can be redistributed using the reassign command. The reassign command allows the moving of DRIM control from one GPROC, GPROC2 to another: one DHP to another DHP, the BTP to a DHP, DHP to the BTP. The GPROC, GPROC2s must be in the same shelf as the DRIM. When a site has been reset, the system will revert to the original pre-reset allocation of DRIMs to GPROC, GPROC2s. During execution of the reassign command, the DRIM and RTF supported by the DRIM is momentarily taken out of service.
Redundancy considerations
A BTS should always be configured with sufficient redundancy such that a single GPROC, GPROC2 failure will not: S S S Degrade system performance. Reduce capacity. Cause the BTS site to become inoperative.
Each BTS site should be equipped with a redundant BTP, since failure of the BTP will result in an inoperative BTS. An additional DHP should be equipped in each BTS shelf already containing a DHP. This redundant DHP will allow for a DHP to fail in any shelf and not cause the other GPROC, GPROC2s in that shelf to become overloaded or a RTF to become inoperable. If a DHP were to fail, and the sum of the max_dris for the remaining DHP(s) was less than the number of DRIMs, some RTF(s) would become inoperative. Under these conditions, if there were only a single DHP in a shelf, all RTFs using DRIMs in that shelf would be inoperative. If a DHP were to fail in the shelf with the BTP and the BTP was controlling a number of RTFs less than its max_dris setting, the BTP will take control of the RTF(s) that were controlled by the failed DHP, up to a number of RTFs equivalent to its max_dris setting. Where the number of DHPs is greater than the number of RTFs, some DHPs will remain in an idle condition.
118
14th Apr 00
GSM-001-103
GPROC, GPROC2 planning

The number of GPROC, GPROC2s required at a given BTS site is dependent on carrier and channel configuration together with the projected call mix at the BTS. The projected call mix must be done on an individual BTS basis. When determining the required number of GPROC, GPROC2s for a given BTS shelf, the call mix associated with the cells supported by the RTFs in the shelf, must be used.
BTS type 0
A BTS type 0 only supports one active GPROC, which is referred to as the BTP. Although a second BTP may exist to meet redundancy requirements, only one may be active at any given time. For the typical call mix a type 0 BTS supports up to two RTFs. For a BTS with more than three RTFs then a type 1 BTS should be used. For the border location area call mix a type 0 BTS supports up to two RTFs. If the call parameters differ significantly from those given in Table 3-1 then the formula given below should be used.
BTS type 1
A BTS type 1 supports multiple active GPROC, GPROC2s. The RRSM and CRM functions reside on the BTP, in addition to an optional instance of the RSS. A BTS type 1 also supports DHPs. The number of RTFs a BTP can control depends on the total number of RTFs at the BTS site. Table 11-2 gives the max_dris setting (the number of RTFs a BTP can control) for the BTP for the typical and border location area call mix for a given number of RTFs and Erlangs for a BTS. If the call parameters differ significantly from those given in Table 3-1, the formula given below should be used. If the formula gives two RTFs per DHP, then the border location area call mix rules should be used. If the formula gives one RTF per DHP, then the BTP may control one RTF for BTS sites of less than three RTFs. Table 11-2 Maximum number of Erlangs supported by the BTP max_dris value val e for BTP 0 1 2 Typical call mix Maximum RTFs 30 22 14 Maximum Erlangs 200 140 80 Location area border call mix Maximum RTFs 20 15 10 Maximum Erlangs 120 85 50
14th Apr 00
119
GSM-001-103
Call mixes
The factors that determine call mixes are highly site dependent. The main factors being the ratio of location updates to calls and call hold time. Those BTSs that contain cells on the edge of location areas, will have a greater loading of location updates. This impacts the number of required DHPs and control channel configurations and the maximum number of RTFs supported by a BTS site. An RTF is controlled by one DHP or the BTP. For the typical call mix a DHP supports up to three RTFs and for the border location area call mix a DHP supports up to two RTFs. If the call parameters differ significantly from those given in Table 3-1, the formula given here should be used to determined the maximum number of RTFs a DHP or the BTP should control; the result should be rounded down to an integer value. N RTF + 0.8 0.2 + (1 + 1.4 < L + 0.9 < S + 0.5 < H) / T is: the maximum number of RTFs supported per DHP (type 0 BTS). the location update factor. the ratio of SMSs per call. the number of handovers per call. the average call duration.
Where:
NRTF L S H T
BTS shelf configurations

The number of RTFs supported by a DHP and the BTP must be determined before determining the BTS shelf configurations. The sections Shelf configurations for typical call mix and Shelf configurations for border location area call mix respectively, provide recommended shelf configurations for the normal call mixes given in Table 11-3 and Table 11-4, and border location area call mixes given in Table 11-5 and Table 11-6. The number of RTFs referred to in these sections is the number of active RTFs. Inactive, or standby carriers do not utilize GPROC, GPROC2 resources. The numbers given are the number of GPROC, GPROC2s required with and without redundancy. For redundancy the number of GPROC, GPROC2s given is the number required such that no single GPROC, GPROC2 failure will cause a loss of RTFs or capacity. See redundancy considerations below for more details on GPROC, GPROC2 redundancy.
Command max_dris
The max_dris setting for the DHP should be the same as the number of RTFs per DHP. For the BTP the max_dris setting should be the value from Table 11-3, Table 11-4, Table 11-5 and Table 11-6; or from the formula given above.
Redundant GPROC, GPROC2s

For redundancy the BTP should be duplicated. The letter R next to the max_dris number in the following tables indicates that this DHP is optional and only required for redundancy.
1110
14th Apr 00
GSM-001-103
Shelf configurations for typical call mix

Table 11-3 and Table 11-4 give the recommended number of GPROC, GPROC2s and max_dris values for the first shelf and the other shelves, respectively for a BTS with the typical call mix parameters. The BTP is duplicated when redundancy (R) is specified. Table 11-3 Recommended BTP/DHP configurations and max_dris values for the first shelf of a BTS (three RTFs per DHP) Number of RTFs BTP max_dris values DHP1 DHP 2 DHP 3 Total GPROCs Without redundancy 1 3 3 3(R) 3(R) With 7 to 14 RTFs at BTS site 2 35 6 2 2 2 3 3 3 3(R) 3 3(R) 1 2 3 2 4 5 2 3 With redundancy 2 4 5
With 6 or fewer RTFs at BTS site 12 35 6 2 2 2
With 15 to 22 RTFs at BTS site 1 24 56 1 1 1 3 3 3 3(R) 3 3(R) 1 2 3 2 4 5
With more than 22 RTFs at BTS site 13 46 0 0 3 3 3(R) 3 3(R) 1 2 2 3
Table 11-4 Other shelves (three RTFs per DHP) Number of RTFs 13 36 DHP 1 3 3 max_dris values DHP 2 3(R) 3 3(R) DHP 3 DHP 4 N/A N/A Total GPROCs Without redundancy 1 2 With redundancy 2 3
14th Apr 00
1111
GSM-001-103
Shelf configurations for border location area call mix

Table 11-5 and Table 11-6 give the recommended number of GPROC, GPROC2s and max_dris values for the first shelf and the other shelves, respectively for a BTS with the border location area call mix parameters. The BTP is duplicated when redundancy (R) is specified. Table 11-5 Recommended BTP/DHP configurations and max_dris values for the first shelf of a BTS (three RTFs per DHP) Number of RTFs BTP max_dris values DHP1 DHP2 DHP3 DHP 4 Total GPROCs Without redundancy 1 2 2 2(R) 2 2(R) 2 3 With redundancy 2 4 5
With 10 or fewer RTFs at BTS site 12 34 56 2 2 2
With 15 or fewer RTFs at BTS site 1 23 45 6 1 1 1 1 2 2 2 2(R) 2 2 2(R) 2 2(R) 1 2 3 4 2 4 5 6
With 20 or fewer RTFs at BTS site 12 34 46 0 0 0 2 2 2 2(R) 2 2 2(R) 2 2(R) 2 3 4 4 5 6
Table 11-6 Other shelves (three RTFs per DHP) Number of RTFs 13 34 56 DHP1 2 2 2 max_dris values DHP 2 2(R) 2 2 2(R) 2 2(R) DHP 3 DHP 4 Total GPROCs Without redundancy 1 2 3 With redundancy 2 3 4
1112
14th Apr 00
GSM-001-103
BTS equipment cabinets
BTS equipment cabinets

Introduction
Each BTS6 cabinet can support up to six cells and six carriers, earlier cabinets supported fewer carriers. The minimum number of cabinets required can be determined by dividing the total number of carriers by six. Keeping all the carrier equipment in a cell in the minimum number of cabinets makes interconnection simpler. However, consider a three cell site with two carriers per cell. This fits well in a single cabinet. When this site needs to expand, an additional cabinet must be added and at least one cell needs to move to the second cabinet. A three cell site which will grow to four carriers per cell can be accommodated in two BTS cabinets, if the cell which is split between cabinets can use hybrid combining. If a remotely tuneable combiner (RTC) is to be housed in an external equipment cabinet, a third BTS cabinet may provide a better alternative as well as room to expand later.
Cabinet planning actions

The following planning actions are required: S S Determine if ExCell or TopCell cabinets are required. Determine the number of cabinets required and number of cells to be supported by each cabinet.
14th Apr 00
1113
Receiver front end
GSM-001-103
Receiver front end

Introduction
The receiver front end (RFE) provides the termination and distribution of the received signals from the Rx antennas. RFE equipment is required for each Rx signal in every cabinet in which it is used. Each Rx antenna must terminate on a single cabinet. It will normally be one of the BTS cabinets but it may be the external equipment cabinet. If the signal needs to go to multiple cabinets it will be distributed from the first cabinet. For RFE planning purposes include inactive RF carriers in the number of carriers considered.
RFE in cabinet types EG, FG and BTS6

Cabinet types EG, FG, BTS6 come equipped with a DPP shelf which has the capacity to hold up to three modules of the following types: S Dual path preselector (DPP) modules. One DPP is required for every two Rx signals. and/or S Single path preselector (SPP) modules. One SPP is required for each Rx signal. and/or S Passive splitter modules. One passive splitter is required for every two Rx signals (may be fed from an unused output of a DPP or from the expansion port of a DPP2 in the cabinet terminating the Rx antenna). Each module has the ability to distribute the Rx signal to six DRCU/SCU/TCUs in the cabinet.
RFE in cabinet types AG, BG and DG

Cabinet types AG, BG, DG come equipped with a preselector shelf which has the capacity to hold up to three preselectors each with its own 6-way splitter. If more than three Rx antennas need to be terminated, a second preselector shelf is required. This second shelf displaces Tx equipment. One Preselector with 6-way splitter is required for each Rx signal. The splitter/preselector shelf can be removed from the BG and DG cabinets and a DPP shelf fitted.
1114
14th Apr 00
GSM-001-103
Receiver front end
Distributing Rx signals between multiple cabinets

When one Rx signal is feeding multiple cabinets additional equipment and cabling is required. There are several options which depend primarily on other equipment at the site, the number of cabinets to which the signal must be brought, and the number of DRCU/SCU/TCUs in each of the cabinets. Care must be taken to ensure that the BTS cabinet has enough RF ports for the termination and expansion of the Rx signals. This is only a potential issue when diversity is used. In order to terminate the Rx antenna on a BTS cabinet when the cells DRCU/SCU/TCUs are spread across multiple cabinets, check the number of Rx ports on the cabinet and the availability of RFE outputs not being used for carriers in the cabinet. Without using the Tx ports and combiner coupler ports there is a total of six Rx ports available. The six ports allow for up to three cells with diversity and without extension. If there are three cells with diversity supported in the cabinet, any cell which has DRCU/SCU/TCUs in other cabinets must have the Rx antenna terminated on the other cabinet. The cabinet which terminates the Rx antenna should provide the input to all other cabinets supporting the cell. If the cell is spread across three or more cabinets, ensure that there are cabinet Rx ports and available RFE outputs for each cabinet.
Single cabinet rules

The following rules apply for a cabinet to be able to support the Rx termination and extension when the cabinet supports: S S S Single cell. Rx ports exist. Must have a DPP2 or fewer than six DRCU/SCU/TCUs. Two cell. Ability to extend only one cell if diversity is used. Splitter port(s) exist. Three cell. No ability to extend, if diversity is used. Splitter port(s) exist.
Distribution methods
There are three methods of distributing Rx signals between cabinets: S BTS Cabinet with DPP2 The DPP2 has an additional test/extender port which may be used to drive a passive splitter in the DPP slot in an adjacent BTS cabinet. S BTS Cabinet without DPP2 Unused splitter outputs may be used for extension to an adjacent cabinet. Each output requires a 6 dB attenuator to feed the preselector/DPP/SPP in the adjacent BTS cabinet. S Receiver multicoupler When the Rx antenna distribution is to a large number of cabinets, a GSM receiver multicoupler can be equipped in an external equipment cabinet at the site. One of the four types of multicoupler extender is required on each active multicoupler output. A multicoupler should be installed in an external equipment cabinet.
14th Apr 00
1115
Receiver front end
GSM-001-103
RFE planning actions

The following planning actions are required: 1. 2. 3. Determine the number of cells. Determine number of cells which have DRCU/SCU/TCUs in more than one cabinet. Determine the number of Rx antennas per cell supported in each cabinet. A cell without diversity requires one Rx antenna. A cell with diversity requires two Rx antennas. 4. Determine the type and quantity of RFE equipment required.
1116
14th Apr 00
GSM-001-103
Transmit combiner shelf

Introduction
The transmit combiner shelf is mounted directly above the upper bank of fans. If a second preselector shelf is equipped, the Tx combining must be done externally. Transmit RF signals to be combined inside a BTS cabinet can come either from DRCU/SCU/TCUs within the cabinet or from a second BTS cabinet. A BTS cabinet has six Tx ports and two combiner coupling ports.
Transmit combining equipment

The following equipment may be mounted on the transmit combiner shelf: S Up to five hybrid combiner modules. A hybrid combiner combines two inputs into one antenna, five combiners will combine six inputs. Unused ports must be terminated with a suitable load. or S One remotely tuneable combiner. A RTC combines up to five inputs (four for a four cavity combiner) into one antenna. The channels to which RTC cavities are tuned, must be separated by 800 kHz. With a phasing harness, up to ten channels (eight for four-cavity combiners) may be combined together into one antenna. The cavities of an RTC do not have to be connected to a single antenna. and S Up to three transmit bandpass filters. A Tx BPF is a mandatory requirement for every transmitting antenna. If an RTC or more than four hybrid combiners are installed, a maximum of two Tx BPFs can be accommodated, allowing two cells to be serviced. or S Up to two cavity combining blocks (CCB). A CCB (output) combines up to three inputs into one antenna. The channels to which CCB cavities are tuned, must be separated by X kHz. A CCB (extention) enables up to six inputs into one antenna.
14th Apr 00
1117
GSM-001-103
The following factors should be considered when planning the combining equipment: S S When there is only one carrier for each sector, combining is not required. When two or more DRCU/SCU/TCUs are combined on to one antenna, the required power output must be known in order to determine the type of combiner to be used. There is a greater than 3 dB power loss through each hybrid combiner stage. With all cavities of an RTC connected to one antenna, the maximum signal loss for any one input is approximately 3 dB. All combining may be done in an external equipment cabinet if desired, this reduces heat generated in the BTS cabinet. CAUTION The remotely tuneable combiner and multicoupler have not been EMC tested for use in the external equipment rack. Since the end of 1995 these items have not been available for use in this configuration within the European Union.
S S S
Transmit combiner shelf planning actions

The following planning actions are required: 1. 2. 3. Determine the number of cells required. Determine the output power required. Determine the number and type (hybrid or remotely tuneable) of combiners required.
1118
14th Apr 00
GSM-001-103
Duplexer
Duplexer
Introduction
If a single antenna is shared between a Tx and an Rx, a duplexer must be fitted. Performance may be degraded and the use of separate Tx and Rx antennas is recommended.
The following factors should be considered when planning combined antennas: S S S S S S A duplexer can be installed in an ExCell cabinet. A duplexer can be fitted to a TopCell cabinet. A duplexer cannot be fitted into a BTS4, BTS5, or BTS6 cabinet. Duplexers may be installed in an external equipment cabinet. The inter-modulation performance may be degraded due to the use of common antenna/feeder, putting the receiver at risk. Duplexers have approximately a 0.5 dB loss in both transmit and receive directions.
Duplexer planning actions

The following planning actions are required: 1. 2. Determine if a common antenna is to be used for Tx and Rx. If common antennas are to be used for Tx and Rx, determine the number of duplexers required. An external equipment cabinet will be required when duplexers are used with BTS4, BTS5, or BTS6 cabinets.
14th Apr 00
1119
Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)
GSM-001-103
Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)

Introduction
A carrier equipment kit consists of: S For BTS; a DRCU/SCU/TCU, DRIM, and DRIX.
Together these three units provide a single RF carrier, which can be referred to as an RTF.
The following factors should be considered when planning carrier equipment: S S S The number of carriers should be based on traffic considerations. Plan for future growth. Allowance must be made for BCCH and SDCCH control channels. Information about how to determine the number of control channels required is in the section Control channel calculations in this chapter. S S Normally, one carrier equipment kit is required to provide each RF carrier. Include redundancy requirements; redundancy can be achieved by installing excess capacity in the form of additional carrier equipment kits.
Carrier equipment planning actions

The following planning actions are required: 1. 2. 3. Determine the number of carriers required. Make an allowance for redundancy. Determine the number of carrier equipment kits required.
1120
14th Apr 00
GSM-001-103

Introduction
The line interfaces, balanced line interface board (BIB) and T43 board (T43), provide impedance matching for E1 and T1 links.
The following factors should be considered when planning the line interface complement: S S S S S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V (peak pulse) line use a BIB. To match a single ended 75 ohm 2.37 V (peak pulse) line use a T43 Board (T43). Each BIB or or T43 can interface six E1/T1 links. The BTS cabinet can interface up to twelve bidirectional E1/T1 links using two BIBs (six links connected to each board). The BTS cabinet can interface up to twelve bidirectional E1 links using two T43 boards (six links connected to each board).

The following planning actions are required: 1. 2. Determine the number and type of link (E1 or T1) to be driven. Determine the number of BIBs or T43s required. Number of BIBs or T43s = NOTE Refer to the TS Concentration section in Chapter 2 for the planning consideration of the BTS Concentration feature. Number of MSIs Number of E1/T1 links = 3 6
14th Apr 00
1121
GSM-001-103

Introduction
A multiple serial interface provides the interface between a BTS cabinet and the links from the BSC. An MSI can interface only E1 links, an MSI-2 can interface both E1 and T1 links.
The following factors should be considered when planning the MSI complement: S To calculate the required number of 64 kbit/s channels, the site must be viewed as consisting of its own equipment and that of other sites which are connected to it by the drop and insert method. Two 64 kbit/s channels are required for each active RTF. A 64 kbit/s channel is required for every RSL (LAPD signalling channel) to the site. In the drop and insert configuration, every site requires its own RSL for signalling. With closed loop, two RSLs are required per site, one in each direction. More information can be found in the Multiple serial interface (MSI, MSI-2) Chapter 15, Previous BTS planning steps and rules. S S S S S S S S S S Each MSI can interface two E1 links. Each MSI-2 can interface two E1/T1 links. Each E1 link provides 31 usable 64 kbit/s channels. Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2. A minimum of one MSI/MSI-2 is required for each BTS site. Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links connected to the site. Plan for a maximum of ten MSIs in each BTS site (with no BSC). Plan for a maximum of eight MSIs or ten MSI-2s for each KSW/TSW. The master MSI slot of the first shelf should always be populated to enable communication with the BSC. Refer to Table 11-7 for the number of traffic channels (TCH) per radio signalling link (RSL).
1122
14th Apr 00
GSM-001-103
Table 11-7 Number of BSC to BTS signalling links n = number of TCHs at the BTS n <= 30 30 < n <= 60 60 < n <= 90 90 < n <= 120 120 < n <= 150 150 < n <= 180 180 < n <= 210 210 < n <= 240 NOTE A BTS shall support either 64 kbit/s RSLs or 16 kbit/s RSLs, but not both. Number of 64 kbit/s RSLs 1 1 1 1 2 2 2 2 Number of 16 kbit/s RSLs 1 2 3 4 5 6 7 8

The following planning actions are required: 1. 2. Determine the number and type of link (E1 or T1) to be interfaced. Determine, M, the number of MSIs or MSI-2s required. M= Number of E1/T1 links 2
14th Apr 00
1123
GSM-001-103

Introduction
The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as a generic control processor.
The following factors should be considered when planning the GPROC, GPROC2 complement: S S S S At least one GPROC, GPROC2 is required for each digital shelf. If more than one cabinet is used, the first cabinet requires a minimum of two active GPROCs to support the additional cabinets. Additional GPROC, GPROC2s may be required to cope with additional load. The master GPROC, GPROC2 slot of the BSU shelf should always be populated to enable communication with the BSC.
GPROC, GPROC2 planning actions

Determine the number of GPROC, GPROC2s required. Use the information to be found in the section Calculations for determining BTS GPROC, GPROC2 requirements in this chapter.
1124
14th Apr 00
GSM-001-103
Timeslot switch (TSW)
Timeslot switch (TSW)

Introduction
The timeslot switch (TSW) provides digital switching on the TDM highway of the BTS. The TSW is designed for use in BTSs, although the KSW can continue to be used. It should be borne in mind that the KSW provides all the TSW functionality plus subrate switching and third-party conference functionality, but at an increased cost.
The following factors should be considered when planning the TSW complement: S S S S S A minimum of one TSW is required for each BTS site. In a BTS, one TSW can support up to eight MSIs or ten MSI-2s. As a site grows beyond 25 DRCU/SCU/TCUs, an additional TSW will be required for switch expansion. All DRIMs which support RTFs in a cell must be on a single TDM bus controlled by the same TSW. For redundancy, duplicate all TSW boards.
TSW planning actions

Determine the number of TSWs required.
14th Apr 00
1125
GSM-001-103

Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUs and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is required whenever a network element grows beyond a single shelf. Although not required in a single BTS cabinet configuration, if expansion to multiple cabinets is expected, equipping the KSWX (and CLKX) will allow for easier expansion.
The following factors should be considered when planning the KSWX complement: S S For redundancy, duplicate all KSWX boards (requires redundant KSW/TSW). KSWXs are used in three modes: KSWX E (Expansion) are required to interconnect the KSWs for sites with multiple KSWs. KSWX R (Remote) are required in shelves with KSWs to drive the TDM highway in shelves that do not have KSWs. KSWX L (Local) are used in shelves that have KSWs to drive the clock bus in that shelf and in shelves that do not not KSWs to drive both the local TDM highway and the clock bus in that shelf.
S S
Five of the redundant KSWX slots are also CLKX slots. The maximum number of KSWX slots per shelf is 18, 9 per KSW/TSW.

The number of KSWXs required is the sum of the KSWXE, KSWXL, and KSWXR. N KX + NKXE ) NKXR ) NKXL N KXE + K < (K * 1) N KXR + SE N KXL + K ) S E Where: NKX NKXE NKXR NKXL K SE NOTE Ensure that SE = 0 for extension shelves and 1 for expansion shelves. is: the number of KSWX required. the number of KSWXE. the number of KSWXR. the number of KSWXL. the number of non-redundant KSWs. the number of extension/expansion shelves.
1126
14th Apr 00
GSM-001-103

Introduction
The generic clock (GCLK) generates all the timing reference signals required by a BTS.
The following factors should be considered when planning the GCLK complement: S S One GCLK is required at each BTS site. For redundancy add a second GCLK at each site in the same cabinet as the first GCLK.

14th Apr 00
1127
GSM-001-103

Introduction
A clock extender (CLKX) provides expansion of GCLK timing to more than one BSU. Although not required in a single BTS cabinet configuration; if expansion to multiple cabinets is expected, equipping the CLKX (and KSWX) will allow for easier expansion later.
The following factors should be considered when planning the KSWX complement: S S One CLKX is required if expansion is planned. For redundancy, duplicate each CLKX (requires a redundant GCLK).

Determine the number of CLKXs required. N CLKX + ROUNDUP Where: NCLKX ROUNDUP E RF is: E < (1 ) R ) F 6
the number of CLKX required. rounding up to the next integer. the number of expansion/expension shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
NOTE Each BTS cabinet has one BSU shelf.
1128
14th Apr 00
GSM-001-103
Local area extender (LANX)
Local area extender (LANX)

Introduction
The local area network extender (LANX) provides a LAN interconnection for communications between all GPROC, GPROC2s at a site.

Determine the number of LANXs required. N LANX + NBSU < (1 ) R F) Where: NLANX NBSU RF is: the number of LANX required. the number of BSU shelves. Redundancy factor (1 if redundancy required (recommended). 0 for no redundancy).
BSU 14
14th Apr 00
1129
GSM-001-103

Introduction

Determine the number of PIXs required. PIX 2 * number of BSUs. or PIX 8.
1130
14th Apr 00
GSM-001-103
Digital radio interface extender (DRIX3c)
Digital radio interface extender (DRIX3c)

Introduction
The Digital radio interface extender (DRIX3c) provides the electrical-optical interface for the downlink (Tx) data and the optical-electrical interface for the uplink (Rx) data between the DRCU/SCU/TCU/PCU and the DRIM.
The following factors should be considered when planning the DRIX3c complement: S S The maximum number of DRIX3c board slots per shelf is six. The maximum number of DRIX3c board slots per site is six.
DRIX planning actions

Determine the number of DRIX3cs required.
14th Apr 00
1131
GSM-001-103

Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an external battery. It maintains power to the GPROC, GPROC2 DRAM and the optical circuitry on the LANX, in the event of a mains power failure.
The following factors should be considered when planning the BBBX complement: S One BBBX is required in each shelf.

1132
14th Apr 00
GSM-001-103

Introduction
A BTS and PCC cabinet can be supplied to operate from either a +27 V dc or 48/60 V dc power source.
The following factors should be considered when planning the power supply module (PSM) complement: S The +27 V dc BTS4/BTS5 cabinet option includes two digital power supply modules (DPSM) required to power the BSU shelf. An additional DPSM may be equipped for redundancy. The 48/60 V dc BTS4 cabinet option includes the two DPSMs required to power the BSU shelf, and a power converter unit for the DRCU/SCU/TCUs. An additional DPSM may be added for redundancy. The power converter unit is required to supply +27 V dc to the DRCU/SCU/TCUs, and includes three dc/dc converter modules housed in the fifth DRCU/SCU slot. A fourth converter module can be ordered separately to provide redundancy. S The BTS6 cabinet power supplies, required to power both the digital shelf and DRCU/SCU/TCUs, are provided: In a +27 V dc cabinet, by one enhanced power supply module (EPSM) per three DRCU/SCU/TCUs (two EPSM for a six DRCU/SCU fit). A third EPSM can be fitted for redundancy. In a 48/60 V dc cabinet, by one integrated power supply module (IPSM) per three DRCU/SCU/TCUs (two IPSM for a six DRCU/SCU fit). A third IPSM can be fitted for redundancy. NOTE The EPSM and IPSM fitted to a BTS6 cabinet are not interchangeable with the DPSM fitted to BTS4 and BTS5 cabinets. S ExCell operates internally from +27 V dc and contains up to three EPSMs. ExCell also contains a battery backup facility. A 48/60 V dc supply is available for customer supplied communications equipment. TopCell operates internally from +27 V dc and uses the EPSM. Battery backup is provided for each cabinet. A 48/60 V dc supply is available for customer-supplied communications equipment.

Determine the number of PSMs required.
14th Apr 00
1133
BTS RF configurations
GSM-001-103
BTS RF configurations
Introduction
This section provides diagrams of the logical interconnections of the RF components in various standard BTS site configurations, including ExCell and TopCell. This chapter contains: S S S Typical BTS configurations. Single cabinet RF configurations. Multiple cabinet RF configurations.
1134
14th Apr 00
GSM-001-103
Typical BTS configurations

BTS configuration
The digital module and RF configuration for a BTS cabinet with four RF carriers and hybrid combining is shown in Figure 11-1.
BTS CABINET RF EQUIPMENT
TO TRANSMIT ANTENNA Tx BPF
FROM RECEIVE ANTENNA
HYBRID HYBRID HYBRID
PRESELECTOR/6-WAY SPLITTER OR DUAL PATH PRESELECTOR
DRCU/SCUs
ONE RF CARRIER CONSISTS OF ONE DRIM, DRIX AND DRCU/SCU
BSU SHELF
FIBRE OPTIC LINKS
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DUAL SERIAL BUS
PIX
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
BTC
GCLK
GCLK
KSW A
KSW B REDUNDANT
MSI
MSI DUAL IEEE 802.5 LAN
GPROC
GPROC
GPROC
REDUNDANT
LINKS FROM/TO BSC
LANX A
LANX B
BSC
Figure 11-1 Single BTS or ExCell site with four RF carriers using hybrid combining
14th Apr 00
1135
GSM-001-103
TopCell BTS configuration

The digital module and RF configuration for a TopCell BTS cabinet with six RF carriers and hybrid combining is shown in Figure 11-2. TopCell supports a maximum of six carriers.
Tx Rx Tx Rx Tx Rx
TRU1
Tx BPF DPP
TRU2
Tx BPF DPP
TRU3
Tx BPF DPP
HYBRID
HYBRID
HYBRID
DRCU/ SCUs
DRCU/ SCUs
DRCU/ SCUs
TDU
FIBRE OPTIC LINKS
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
A B DUAL TDM HIGHWAY BUS BTC GCLK KSW MSI DUAL MCAP BUS DUAL IEEE 802.5 LAN LANX A LANX B GPROC GPROC GPROC
LINKS FROM/TO BSC
BSC
Figure 11-2 TopCell with six RF carriers using hybrid combiners
1136
14th Apr 00
GSM-001-103
Single cabinet RF configurations

Single cabinet, single DRCU/SCU without diversity
A single cabinet, single DRCU/SCU configuration is shown in Figure 11-3. Table 11-8 provides a summary of the equipment required for this configuration. The following rules apply: S S S As only one DRCU/SCU is used a combiner is not required. One dual path preselector is required for the receive signal entering the cabinet. An external equipment cabinet is not necessary.
Tx Rx
DUAL PATH PRESELECTOR
Tx BPF
DRCU/SCU
BTS CABINET
Figure 11-3 Single cabinet, single DRCU/SCU configuration without diversity
14th Apr 00
1137
GSM-001-103
Table 11-8 Equipment required for single cabinet, single DRCU/SCU configuration Quantity 2 1 1 Antennas BTS cabinet DRCU/SCU Transmitter 1 Bandpass filter Receiver 1 Dual path preselector Unit
1138
14th Apr 00
GSM-001-103
Single cabinet, single DRCU/SCU with diversity

A single cabinet, single DRCU/SCU configuration with diversity is shown in Figure 11-4. Table 11-9 provides a summary of the equipment required for this configuration. The following rules apply: S S S As only one DRCU/SCU is used a combiner is not required. One dual path preselector is required for every two receive signals entering the cabinet. An external equipment cabinet is not necessary.
Tx Rx Rx
Tx BPF
DRCU/SCU
BTS CABINET
Figure 11-4 Single cabinet, single DRCU/SCU configuration with diversity
14th Apr 00
1139
GSM-001-103
Table 11-9 Equipment required for single cabinet, single DRCU/SCU configuration with diversity Quantity 3 1 1 Antennas BTS cabinet DRCU/SCU Transmitter 1 Bandpass filter Receiver 1 Dual path preselector Unit
Single cabinet, five DRCU/SCUs with combining

A single cabinet, five DRCU/SCU configuration with remotely tuneable or hybrid combining but without diversity is shown in Figure 11-5. Table 11-10 provides a summary of the equipment required for this configuration. The following rules apply: S S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can be accommodated. If operation from a negative power supply voltage is required, only four DRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will be occupied by the dc/dc converters. If, when using hybrid combining, there are unequal levels of loss, the output power for the BTS (sector) is that of the DRCU/SCU with the greatest loss. The other DRCU/SCUs should be adjusted to lower their output to provide the same output power level. An external equipment cabinet is not necessary.
1140
14th Apr 00
GSM-001-103
Tx
Rx
DUAL PATH PRESELECTOR Tx BPF
HYBRID COMBINERS Tx BPF REMOTELY TUNEABLE COMBINER HYBRID
HYBRID
HYBRID
HYBRID
DRCU/SCUs
BTS CABINET
Figure 11-5 Single cabinet, five DRCU/SCU configuration with remotely tuneable or hybrid combining and without diversity
14th Apr 00
1141
GSM-001-103
Table 11-10 Equipment required for single cabinet, five DRCU/SCU configuration with remotely tuneable or hybrid combining Quantity 2 1 5 Antennas BTS cabinet DRCU/SCU Transmitter 1 4 or 1 Remotely tuneable combiner Receiver 1 Dual path preselector Bandpass filter Hybrid combiner Unit
Single cabinet, six DRCU/SCUs with combining and diversity

A single cabinet, six DRCU/SCU configuration with remotely tuneable or hybrid combining is shown in Figure 11-6. Table 11-11 provides a summary of the equipment required for this configuration. The following rules apply: S S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can be accommodated. If operation from a negative power supply voltage is required, only four DRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will be occupied by the dc/dc converters. If, when using hybrid combining, there are unequal levels of loss, the output power for the BTS (sector) is that of the DRCU/SCU with the greatest loss. The other DRCU/SCUs should be adjusted to lower their output to provide the same output power level. An external equipment cabinet is not necessary.
1142
14th Apr 00
GSM-001-103
Tx
Rx
Rx
Tx BPF
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
DRCU/SCUs
BTS CABINET
Figure 11-6 Single cabinet, six DRCU/SCU configuration with diversity and remotely tuneable or hybrid combining
14th Apr 00
1143
GSM-001-103
Table 11-11 Equipment required for single cabinet, six DRCU/SCU configuration with diversity and remotely tuneable or hybrid combining Quantity 3 1 6 Antennas BTS cabinet DRCU/SCU Transmitter 1 5 or 1 1 Remotely tuneable combiner Hybrid combiner Receiver 1 Dual path preselector Bandpass filter Hybrid combiner Unit
1144
14th Apr 00
GSM-001-103
Single cabinet, multiple antennas

A single cabinet, multiple antenna configuration is shown in Figure 11-7. Table 11-12 provides a summary of the equipment required for this configuration. The following rules apply: S S If only one DRCU/SCU is used per carrier, combining is not required. An external equipment cabinet is not necessary.
Tx Tx Tx Rx Rx Rx
Tx BPFs
DUAL PATH PRESELECTORS
DRCU/ SCUs BTS CABINET
Figure 11-7 Single cabinet, multiple antenna (three sector minimum) configuration
14th Apr 00
1145
GSM-001-103
Table 11-12 Equipment required for single cabinet, multiple antenna configuration Quantity 6 1 3 Antennas BTS cabinet DRCU/SCU Transmitter 3 Bandpass filter Receiver 2 Dual path preselector Unit
1146
14th Apr 00
GSM-001-103
Single cabinet, multiple antennas with diversity

A single cabinet, multiple antenna configuration with diversity is shown in Figure 11-8; this configuration provides for three sectors. Table 11-13 provides a summary of the equipment required for this configuration. The following rules apply: S S S A maximum of six receive signals, two per DRCU/SCU, are allowed per BTS cabinet. If only one DRCU/SCU is used per carrier, combining is not required. An external equipment cabinet is not necessary.
Tx Tx Tx Rx Rx Rx Rx Rx Rx
Tx BPF
DRCU/SCUs
BTS CABINET
Figure 11-8 Single cabinet multiple antenna configuration with diversity
14th Apr 00
1147
GSM-001-103
Table 11-13 Equipment required for single cabinet, multiple antenna configuration with diversity Quantity 9 1 3 Antennas BTS cabinet DRCU/SCU Transmitter 3 Bandpass filter Receiver 3 Dual path preselector Unit
1148
14th Apr 00
GSM-001-103
Multiple cabinet RF configurations

Multiple cabinet, single antenna, four DRCU/SCUs
A multiple cabinet, single antenna configuration without diversity is shown in Figure 11-9. This configuration provides eight carriers on one antenna using hybrid combiners. Table 11-14 provides a summary of the equipment required for this configuration. The following rules apply: S DRCU/SCUs can be connected to the combiners in any order. The transmit power of a DRCU/SCU at the top of the cabinet depends on the number of combiner levels it goes through. Each level of hybrid combining results in a loss of up to 3.2 dB of carrier power. The antenna feed to cabinet 2 originates from the test (unused) 6-way splitter port in cabinet 1. An inline attenuator is required to ensure specified performance. This configuration may not be implemented using ExCell. An external equipment cabinet is not necessary.
Rx ATTENUATOR Tx
S S S
Tx BPF
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
DRCU/SCUs
DRCU/SCUs
BTS CABINET 1
BTS CABINET 2
Figure 11-9 Multiple cabinet, single antenna, four DRCU/SCU configuration
14th Apr 00
1149
GSM-001-103
Table 11-14 Equipment required for multiple cabinet, single antenna four DRCU/SCU configuration Quantity 2 2 8 Antennas BTS cabinet DRCU/SCU Transmitter 7 1 Hybrid combiners Bandpass filter Receiver 1 2 Attenuator Dual path preselector Unit
1150
14th Apr 00
GSM-001-103
Multiple cabinet, single antenna, ten DRCU/SCUs

A multiple cabinet, single antenna configuration is shown in Figure 11-10. This configuration provides ten carriers on one antenna using hybrid combiners. Table 11-15 provides a summary of the equipment required for this configuration. The following rules apply: S S S S S If one site/sector requires ten carriers, this configuration provides the best solution from the point of view of output power. If the antenna feed to cabinet 2 originates from the auxiliary port on the rear of the DPP2 in cabinet 1, a passive splitter is required to ensure specified performance. If the antenna feed to cabinet 2 originates from a DPP or a preselector in cabinet 1, an Rx extender is required to ensure specified performance. This configuration may not be implemented using ExCell. An external equipment cabinet is not necessary.
Rx ANTENNA Tx ANTENNA
Tx BPF PASSIVE SPLITTER DPP2 REMOTELY TUNEABLE COMBINER REMOTELY TUNEABLE COMBINER PHASING HARNESS DPP2
DRCU/ SCUs
DRCU/ SCUs
BTS CABINET 1
BTS CABINET 2
Figure 11-10 Multiple cabinet, single antenna, ten DRCU/SCU configuration using remotely tuneable combiners
14th Apr 00
1151
GSM-001-103
Table 11-15 Equipment required for multiple cabinet, single antenna ten DRCU/SCU configuration using remotely tuneable combiners Quantity 2 2 10 Antennas BTS cabinet DRCU/SCU Transmitter 2 1 1 Remotely tuneable combiners Phasing harness Bandpass filter Receiver 1 2 Passive splitter Dual path preselector 2 Unit
1152
14th Apr 00
GSM-001-103
Multiple cabinet, multiple antenna

A multiple cabinet, multiple antenna configuration is shown in Figure 11-11. This configuration represents the minimum amount of equipment that will provide for six sectors. Table 11-16 provides a summary of the equipment required for this configuration. The following rules apply: S S S If only one DRCU/SCU is used per sector, a combiner is not required. This configuration may not be implemented using ExCell. An external equipment cabinet is not necessary.
Tx Tx Tx Rx Rx Rx Rx Rx Rx Tx Tx Tx
Tx BPF
Tx BPF
DRCU/SCUs
DRCU/SCUs
BTS CABINET 1
BTS CABINET 2
Figure 11-11 Multiple cabinet, multiple antenna (six sector minimum) configuration
Table 11-16 Equipment required for multiple cabinet, multiple antenna configuration Quantity 12 2 6 Antennas BTS cabinet DRCU/SCU Transmitter 6 Bandpass filter Receiver 4 Dual path preselector Unit
14th Apr 00
1153
GSM-001-103
Six sector configuration

A fourcabinet sixsector configuration is shown in Figure 11-12; this configuration provides for three sectors. Table 11-17 provides a summary of the equipment required for this configuration. The following rules apply: S S The site configuration can make a difference to the equipment required. When a receiver multicoupler is used, a multicoupler extender must also be used. One of four types is used depending on the number of cabinets the signal is routed to. The multicoupler may not be required for all sectors, if this is the case, the antennas connects directly to the BTS cabinet preselectors and bypasses the multicoupler. The large multicoupler extender could be replaced by three 6 dB splitters. In this configuration, while DRCU/SCUs 3, 8, 13, 1618 meet the Motorola-stated top of cabinet output power specification, DRCU/SCUs 1, 2, 4, 5, 6,7, 9, 1012, 14, and 15 do not because of two levels of hybrid combining. The site does not meet the specification and the DRCU/SCUs with the higher available transmit power would have their power reduced. The remotely tuneable combiner and multicoupler have not been EMC tested for use in the external equipment rack. Since the end of 1995 these items have not been available for use in this configuration within the European Union. This configuration may not be implemented using ExCell or TopCell. An external equipment cabinet is required.
S S
S S
1154
14th Apr 00
GSM-001-103
Tx
Tx
Tx
Rx
Rx
Rx
Rx
Rx
Rx
Tx
Tx
Tx
EXTERNAL EQUIPMENT CABINET
MULTICOUPLER
LARGE MULTICOUPLER EXTENDER
2 3 4
6 7 8 9 1 0
1 1 1 1 2 3
1 1 4 5
1 1 6 7
1 8
BTS CABINET 1
BTS CABINET 2
BTS CABINET 3
BTS CABINET 4
Figure 11-12 Fourcabinet sixsector configuration
Table 11-17 Equipment required for a four cabinet, six sector configuration Quantity 12 4 1 18 Antennas BTS cabinet External equipment cabinet DRCU/SCU Transmitter 6 12 Bandpass filter Hybrid combiners Receiver 5 1 1 Dual path preselector Multicoupler Multicoupler extender Unit
14th Apr 00
1155
GSM-001-103
Sixsector BTS6 configuration

A sixsector configuration using BTS6s is shown in Figure 11-13; this configuration provides for three sectors with only three cabinets. Table 11-18 provides a summary of the equipment required for this configuration. The following rules apply: S S The site configuration can make a difference to the equipment required. In this configuration, while DRCU/SCUs 3, 4, 9, 10, 15, and 16 meet the Motorola-stated top of cabinet output power specification DRCU/SCUs 1, 2, 5, 6, 7, 8, 11, 12, 13, 14, 17, and 18 do not because of two levels of hybrid combining. Therefore, the site does not meet the specification and the DRCU/SCUs with the higher available transmit power would have their power reduced. This configuration may not be implemented using ExCell or TopCell. An external equipment cabinet is not necessary.
Tx Tx Rx Rx Tx Tx Rx Rx Tx Tx Rx Rx
S S
1 0
1 1
1 2
1 3
1 4
1 5
1 6
1 7
1 8
BTS CABINET 1
BTS CABINET 2
BTS CABINET 3
Figure 11-13 Multiple cabinet, sixsector BTS6 (three carriers per sector) configuration
Table 11-18 Equipment required for multiple cabinet, sixsector BTS6 configuration Quantity 12 3 18 Antennas BTS cabinet DRCU/SCU Transmitter 6 12 Bandpass filter Hybrid combiners Receiver 3 Dual path preselector Unit
1156
14th Apr 00
Index
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
A
air filter, 530 air flow control, circuit switched, 515 air interface planning process, 346 throughput, 351 alarm, panel, 530 alarms, consolidation, 512 allocation method, BSS timeslots, 337 antenna configuration planning, 410 assigning BTSs to LCFs, 1014 assumptions, process, 343 assumptions used in capacity calculations, 510, 108 authorized MCell configurations, order creation, 82 AUX, 530
B
baseband hopping, 17 battery backup (BBBX) planning, 582, 621, 1045, 1132 BSC, provisioning impact, 823 BSC capacity calculations Number of LCF GPROCs required, 560 number of LCF GPROCs required at a BSC, 560 BSC GPROC functions, GPROC types, 561, 1021 BSC planning battery backup (BBBX) planning, 582, 1045 BSC to BTS link planning, 538, 1010 BSC to MSC link planning, 556, 1015 BSU shelves, 573, 1036 clock extender (CLKX) planning, 577, 1040 digital shelf power supply planning, 581, 1044 generic clock (GCLK) planning, 576, 1039 generic processor (GPROC, GPROC2) planning, 1021 generic processor (GPROC2) planning, 561 kiloport switch (KSW) planning, 571, 1034 kiloport switch extender (KSWX) planning, 574, 1037 line interface (BIB, T43) planning, 580, 1043 local area network extender (LANX) planning, 578, 1041 multiple serial interface (MSI, MSI2) planning, 569, 1032 parallel interface extender (PIX) planning, 579, 1042 transcoder planning, 566, 1029 T1 conversion, 567, 1030 BSC planning overview, 102 outline of planning steps, 53, 103 BSC system capacity, scaleable BSC, 56 BSC to BTS link planning, 538, 1010 E1 links, 550, 1011 T1 links, 551, 1012
14th Apr 00
iii
GSM-001-103
BSC to BTS singalling link capacity, 538, 1010 BSC to MSC link planning, 556, 1015 transcoding at the BSC, 568, 1031 E1 links, 568, 1031 T1 links, 568, 1031 BSC to RXCDR link planning. See BSC to BTS link planning BSC types, 562, 1022 BSC capacity calculations Number of LCF GPROCs required, 1019 number of LCF GPROCs required at a BSC, 1019 BSC/RXCDR capacity calculations, 54, 104 assigning BTSs to LCFs, 1014 BSC GPROC functions cell broadcast link, 564, 1026 code storage facility processor, 565, 1027 GPROC redundancy, 1028 GPROC types, 561, 1021 BSC GPROC redundancy, 565 BSS signalling link capacities, 57, 105 assumptions used in capacity calculations, 510, 108 BSC to BTS signalling link (RSL), 538, 1010 MSC to BSC signalling over a satellite link, 560, 1020 MSC to BSC sinalling link (MTL), 556, 1015 typical call parameters, 59, 107 number of LCF GPROCs required at a BSC LCFs for BSC to BTS links and Layer 3 call processing, 552, 1013 LCFs for MSC to BSC links, 560, 1019 BSC-PCU signalling, 542 traffic, 542, 550 BSS planning, 327 planning introduction, 512 statistics, 515 BSS equipment overview system architecture, 13 system components, 14 BSS features, 16 code storage facility processor, 17 diversity, 16 frequency hopping, 16 baseband hopping, 17 synthesizer hopping, 17 short message service, cell broadcast, 17 BSS planning overview, 19 initial information required, 19 planning methodology, 111 BSS signalling link capacities, 57, 105 assumptions used in capacity calculations, 510, 108 BSC to BTS singalling link (RSL), 538, 1010 MSC to BSC singalling link (MTL), 556, 1015 MSC to BSC signalling over a satellite link, 560, 1020 typical call parameters, 59, 107
iv
14th Apr 00
GSM-001-103
BSS standard configurations, 92 BTS configurations PCC with 12 PCU (RF carriers) and HDSL links, 99 PCC with 12 PCU (RF carriers) and optical fibre links, 98 PCC with six PCU (RF carriers) and HDSL links, 97 PCC with six PCU (RF carriers) and optical fibre links, 96 multiple cabinet RF configurations, 1149 four cabinet six sector configuration, 1154 four DRCU/SCUs with a single antenna, 1149 multiple antennas, 1153 ten DRCU/SCUs with a single antenna, 1151 three cabinet (BTS6) six sector configuration, 1156 picocell configurations, 96 single cabinet RF configurations, 1137 five DRCU/SCUs with combining, 1140 multiple antennas, 1145 multiple antennas and diversity, 1147 single DRCU/SCU, 1137 single DRCU/SCU with diversity, 1139 six DRCU/SCUs with combining, 1142 typical BSS configurations, 93 BSC with 24 BTSs, 93 BSC with full redundancy, 94 transcoder, 95 typical BTS configurations, 1135 BTS with four RF carriers, 1135 TopCell with six RF carriers, 1136 BSS timeslots, allocation method, 337 BSS upgrade, provisioning rules, 524 BSU shelves, 573, 1036 BTS, provisioning impact, 824 BTS cabinet planning, 44, 1113 BTS capacity calculations, 311, 114 BTS GPROC requirements, 117 control channel calculations, 313, 116 calculate the number of CCCH, 319 calculate the number of SDCCH, 321 control channel configurations, 322 factors affecting the number of CCCH, 318 factors affecting the number of SDCCH, 320 typical call parameters, 311, 114 BTS enclosure planning, 45 BTS GPROC requirements, 117
14th Apr 00
GSM-001-103
BTS planning antenna configuration planning, 410 cabinet interconnection (FOX/FMUX), 417 cabinet planning, 44, 1113 1999macroBTS, 44 MCell2, 44 MCell6, 44 carrier equipment planning, 411, 1120 clock extender (CLKX) planning, 1128 digital radio interface extender (DRIX) planning, 1131 duplexer planning, 1119 enclosure planning, 45 MCellarena, 45 MCellarena macro, 45 kiloport switch extender (KSWX) planning, 1126 line interface (BIB, T43) planning, 414 main control unit (MCU), 416 main control unit, with dual FMUX (MCUF), 415 micro base control unit, 412 network interface unit (NIU), 413 parallel interface extender (PIX) planning, 1130 power supply planning, 419 receive configuration planning, 46 receiver front end planning, 1114 distributing signals between cabinets, 1115 transmit combiner shelf planning, 1117 transmit configuration planning, 48 BTS planning overview, 42 outline of planning steps, 43, 113 BTS standard configurations, 92 four cabinet RF configuration, 913, 917 four cabinet Horizonmacro configuration, 915, 917 four cabinet MCell6 configuration, 918 single cabinet RF configurations, 910 single Horizonmacro configuration, 910 single MCell2 configuration, 912 single MCell6 configuration, 911 three cabinet RF configuration, 915 three cabinet MCell2 configuration, 916 two cabinet RF configuration two cabinet Horizonmacro configuration, 913 two cabinet MCell6 configuration, 914 BTS to BSC link planning. See BSC to BTS link planning BTS-BSC (abis), E1 links, 539 burst excess, rate, 549
C
cabinet, PCU, 530 cabinet interconnection (FOX/FMUX), 417 calculating the number of CCCH, 319 calculating the number of SDCCH, 321
vi
14th Apr 00
GSM-001-103
calculation GBL links, 821 GDS E1 links, 821 GSL links, 821 increased data traffic load, 822 increased GPRS traffic load, 823 increased signalling traffic load, 823 PCU hardware support, 821 carrier equipment planning, 411, 1120 carrier timeslot allocation examples, 334 examples A and B, 335 examples C, D, and E, 336 cell broadcast, SMS, 515 cell broadcast link, 564, 1026 cell planning channel coding for enhanced full rate, 396 control channel encoding, 397 data channel encoding, 398 discontinuous transmission, 3105 environmental effects on propagation, 366 error protection and detection, 392 frequency reuse, 384 freznel zone, 361 GSM frequency spectrum, 34 hardware and software techniques to overcome propagation effects, 390 introduction, 31 introduction to decibels, 360 mapping logical channels onto the TDMA frame structure, 399 multipath propagation, 369 planning factors, 32 planning tools, 33 propagation effects on GSM frequencies, 359 radio refractive index, 362 speech channel encoding, 394 subscriber environment, 3108 the expansion solution, 3115 voice activity detection, 3105 cell resource manager, dynamic reconfiguration, 513 circuit error rate, monitor, 513 circuit switched air flow control, 515 calls, 513 clock extender (CLKX) planning, 577, 616, 1040, 1128 code storage facility processor, 17, 565, 1027 committed burst, rate, 549 committed information, rate, 548 common antenna for Tx and Rx. See duplexer planning compatibility, features, 512 concentration, at BTS, 512 concentric cells, 513
14th Apr 00
vii
GSM-001-103
congestion relief, 513 control channel calculations, 313, 116 calculate the number of CCCH, 319 calculate the number of SDCCH, 321 control channel configurations, 322 factors affecting the number of CCCH, 318 factors affecting the number of SDCCH, 320 control channel configurations, 322 customer inputs, planning process, 327
D
daisy chain connection, 26 daisy chain planning, 26 determination expected load, 326 GPRS carrier timeslots, 820 digital radio interface extender (DRIX) planning, 1131 digital shelf power supply planning, 581, 620, 1044, 1133 directed retry, 513 distributing receive signals between cabinets, 1115 diversity, 16 DPROC, PICP or PRP, 530 duplexer planning, 1119 dynamic reconfiguration, cell resource manager, 513 dynamic timeslots, mode switching, 332
E
E1 links, BTS-BSC (Abis), 539 emergency call, pre-emption, 514 equipment planning MCell configurations, MCell2 cabinets, 9100 Macrocell configurations Horizonmacro cabinets, 920 MCell6 cabinets, 937 Microcell configurations MCellarena enclosure, 9110 MCellarena macro enclosure, 9109 estimation, network traffic, 327 examples carrier timeslot allocation, 334 planning, 327 examples A and B, carrier timeslot allocation, 335 examples C, D, and E, carrier timeslot allocation, 336 expected load, determination, 326
viii
14th Apr 00
GSM-001-103
extended range cells, 514
F
factors affecting the number of CCCH, 318 factors affecting the number of SDCCH, 320 fan/power supplies, 530 fault containment, RTF path, 515 features, compatibility, 512 four cabinet Horizonmacro configuration, 915, 917 four cabinet MCell6 configuration, 918 frame relay, parameter values, 547 frequency hopping, 514 redefinition, 514 frequency hopping, 16 baseband hopping, 17 synthesizer hopping, 17
G
GBL links, calculation, 821 GDS E1 links, calculation, 821 GDS LAPD GSL, 542 GDS TRAU, 542, 550 generic clock (GCLK) planning, 576, 615, 1039, 1127 generic processor (GPROC, GPROC2) planning, 1021, 1124 generic processor (GPROC) planning, 67 generic processor (GPROC2) planning, 561 global reset, 514 GPROC functions and types, 561, 1021 GPROC redundancy at the BSC, 565 GPRS, key concepts, 327 GPRS carrier timeslots, determination, 820 GPRS control channel, RF provisioning, 313 GPRS network, statistics for replanning, 327 GPRS signalling, LCF GPROC2 provisioning, 553 GPRS timeslots, traffic, 539 GSL links, calculation, 821 GSN, planning, 327
H
handovers, multiband, 514
14th Apr 00
ix
GSM-001-103
HDSL interface, integrated M-Cell, 514
I
increased data traffic load, calculation, 822 increased GPRS traffic load, calculation, 823 increased signalling traffic load, calculation, 823 integrated HDSL interface HDSL cable installation, 242 HDSL cable selection, 242 HDSL range, 242 integrated M-Cell, HDSL interface, 514 interconnecting BTSs and the BSC. See interconnecting the BSC and BTSs interconnecting the BSC and BTSs, 23 interconnection rules, 23 network topology, 24 daisy chain connection, 26 daisy chain planning, 26 star connection, 25 interconnecting the InCell and MCell equipment, interconnection rules, 23 interface planning, PCU-to-SSGN, 523 introduction key concepts, 329 network traffic estimation, 329
K
key concepts GPRS, 327 introduction, 329 overview, 328 kiloport switch (KSW) planning, 571, 612, 1034 kiloport switch extender (KSWX) planning, 574, 614, 1037, 1126
L
LCF GPROC2 provisioning, GPRS signalling, 553 LCFs for BSC to BTS links and Layer 3 call processing, 552, 1013 line interface (BIB, T43) planning, 414, 580, 619, 1043, 1121 line interface module (HIM75, HIM120) planning, 422 local area network extender (LANX) planning, 578, 617, 1041, 1129
M
MCell power supply planning, 419
x
14th Apr 00
GSM-001-103
Macrocell configurations 1999macroBTS cabinet [DCS1800] 2 sector (3/3), with duplexed dualstage hybrid combining, 924 [DCS1800] 2 sector (6/6), with duplexed dualstage hybrid and air combining, 926 [DCS1800] 3 sector (2/2/2), with duplexed hybrid combining, 928 [DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining, 930 [DCS1800] 3 sector (8/8/8), with duplexed dualstage hybrid and air combining, 932 [DCS1800] 4 carrier Omni, with duplexed hybrid and air combining, 920 [DCS1800] 6 carrier Omni, with duplexed dualstage hybrid and air combining, 922 MCell2 cabinet [DCS1800] 2 carrier, single sector, with air combining and diversity, 9106 [DCS1800] 2 sectors, with diversity, 9108 [GSM900] 2 carrier, single sector, with hybrid combining and diversity, 9100 [GSM900] 2 carrier, single sector, with hybrid combining, diversity and medium power duplexer, 9102 [GSM900] 2 sectors (1 carrier per sector), with diversity, 9104 MCell6 cabinet [DCS1800] 3 sector (2/2/2), with hybrid combining and diversity, 996 [DCS1800] 3 sector (2/2/2), with hybrid combining, diversity and medium power duplexers, 998 [GSM900] 2 sector (3/3), with hybrid combining and diversity, 951 [GSM900] 2 sector (3/3), with hybrid combining, diversity and medium power duplexer, 953 [GSM900] 3 carrier Omni, with hybrid combining and diversity, 937 [GSM900] 3 carrier Omni, with hybrid combining, diversity and medium power dulplexer, 939 [GSM900] 3 sector (2/2/2), with combining and diversity, 955 [GSM900] 3 sector (2/2/2), with hybrid combining, diversity and medium power duplexer, 957 [GSM900] 3 sector (4/4/4), with air combining, diversity and medium power duplexer, 967 [GSM900] 3 sector (4/4/4), with air combining, diversity and medium power duplexer (3 antenna per sector), 959 [GSM900] 3 sector (4/4/4), with cavity combining and diversity, 963 [GSM900] 3 sector (4/4/4), with hybrid combining and diversity, 965 [GSM900] 3 sector (4/4/4), with hybrid combining, diversity and medium power duplexer (2 antenna per sector), 961 [GSM900] 3 sector (4/4/4), with hybrid combining, diversity and medium power duplexer (3 antenna per sector), 988 [GSM900] 3 sector (5/5/5), with 3input CBF, air combining, diversity and medium power duplexer (3 antenna per sector), 969 [GSM900] 3 sector (5/5/5), with 3input CBF, combining, diversity and medium power duplexer(2 antenna per sector), 971 [GSM900] 3 sector (6/6/6), with 3input CBF, air combining, diversity and medium power duplexer (3 antenna per sector), 975 [GSM900] 3 sector (6/6/6), with 3input CBF, combining, diversity and medium power duplexer (2 antenna per sector), 977 [GSM900] 3 sector (6/6/6), with cavity combining, diversity and high power duplexer, 973 [GSM900] 3 sector (8/8/8), with cavity combining, diversity and both high and medium power duplexers, 984 [GSM900] 3 sector (8/8/8), with cavity combining, diversity and medium power duplexer, 980 [GSM900] 3 sector (8/8/8), with combining, diversity and medium power duplexer (2 antenna per sector), 992 [GSM900] 4 carrier Omni, with hybrid combining and diversity, 941 [GSM900] 4 carrier Omni, with hybrid combining, diversity and medium power duplexer, 943 [GSM900] 6 carrier Omni, with cavity combining and diversity, 945 [GSM900] 6 carrier Omni, with cavity combining, diversity and high power duplexer, 947 [GSM900] 8 carrier Omni, with combining and diversity, 949 Macrocell standard configurations, RF configurations, 919 main control unit (MCU), 416 main control unit, with dual FMUX (MCUF), 415 Managed HDSL on micro BTS, 241
14th Apr 00
xi
GSM-001-103
maximum configuration, 531 micro base control unit, 412 Microcell configurations MCellarena enclosure, [GSM900/DCS1800] 2 carrier, 9110 MCellarena macro enclosure, [GSM900/DCS1800] 2 carrier, 9109 Microcell standard configurations, RF configurations, 9110 microcell system planning daisy chain, 245 E1 link, 245 star configuration, 245 mode switching, dynamic timeslots, 332 MPROC, 530 MSC to BSC link planning. See BSC to MSC link planning MSC to BSC signalling link capacity, 556, 1015 MSC to BSC signalling over a satellite link, 560, 1020 MSC to RXCDR link planning. See RXCDR to MSC link planning MTL capacity. See MSC to BSC signalling link capacity multiband, handovers, 514 multiple cabinet, multiple antenna configuration, 1153 multiple cabinet, single antenna, four DRCU/SCU configuration, 1149 multiple cabinet, single antenna, ten DRCU/SCU configuration, 1151 multiple serial interface (MSI, MSI2) planning, 569, 610, 1032, 1122
N
N+1 equipment, redundancy supported, 530 network, planning process, 327 network expansion using MCell BTS, 420 network interconnection rules, 23 network interface unit (NIU), 413 network planning, aggregate Abis, 29 network provisioning, switchable timeslots, 339 network topology daisy chain connection, 26 daisy chain planning, 26 star connection, 25 network traffic, estimation, 327 network traffic estimation background, 333 introduction, 329 overview, 328 Number of LCF GPROCs required, 560, 1019 number of LCF GPROCs required at a BSC, 560, 1019 LCFs for BSC to BTS links and Layer 3 call processing, 552, 1013 LCFs for MSC to BSC links, 560, 1019
xii
14th Apr 00
GSM-001-103
number of LCFs for MSC to BSC links, 560, 1019 number of LCFs required for the RSLs. See number of LCFs required for the RSLs; Number of LCFs to support the BSC to BTS signalling links
O
OMC-R, provisioning impact, 824 order creation, OMCR example, 818 overview key concepts, 328 network traffic estimation, 328 planning process, 324 provisioning rules, 524
P
parallel interface extender (PIX) planning, 579, 618, 1042, 1130 parameter values, frame relay, 547 PCC cabinet planning, 421 PCC planning battery backup (BBBX) planning, 1132 cabinet planning, 421 digital shelf power supply planning, 1133 generic clock (GCLK) planning, 1127 generic processor (GPROC, GPROC2) planning, 1124 line interface (BIB, T43) planning, 1121 line interface module (HIM75, HIM120) planning, 422 local area network extender (LANX) planning, 1129 multiple serial interface (MSI, MSI2) planning, 1122 timeslot switch (TSW) planning, 1125 PCU cabinet, 530 provisioning rules, 525 PCU hardware support, calculation, 821 PCU-SGSN, traffic and signalling, 545 PCU-to-SSGN, interface planning, 523 PICP boards, recalculation, 822 planning BSS, 327 examples, 327 GSN, 327 recommended guidelines, 327 redundancy, 534
14th Apr 00
xiii
GSM-001-103
planning exercise, 81 calculations using alternative call models, 825 determine the number of CCCHs per cell, 827 determine the number of GPROC2s, 829 determine the number of SDCCHs per cell, 828 parameters used, 825 determine the BTS 10 hardware requirements, 89 determine the BTS 2 hardware requirements, 86 determine the BTS hardware requirements, 812 determine the OMCR hardware requirements, 818 determine the RXCDR hardware requirements, 815 initial requirements, 83 introduction to the exercise, 85 planning introduction, BSS, 512 planning methodology, 111 planning process air interface, 346 customer inputs, 327 network, 327 overview, 324 pre-emption, emergency call, 514 process, assumptions, 343 provisioning impact BSC, 823 BTS, 824 OMC-R, 824 provisioning rules BSS upgrade, 524 overview, 524 PCU, 525
R
rate burst excess, 549 committed burst, 549 committed information, 548 recalculation, PICP boards, 822 receive configuration planning, 46 receiver front end planning, 1114 distributing signals between cabinets, 1115 recommendation, 343 recommended guidelines, planning, 327 redundancy, planning, 534
xiv
14th Apr 00
GSM-001-103
remote trancoder planning battery backup (BBBX) planning, 621 clock extender (CLKX) planning, 616 digital shelf power supply planning, 620 generic clock (GCLK) planning, 615 generic processor (GPROC) planning, 67 kiloport switch (KSW) planning, 612 kiloport switch extender (KSWX) planning, 614 line interface (BIB, T43) planning, 619 local area network extender (LANX) planning, 617 multiple serial interface (MSI, MSI2) planning, 610 parallel interface extender (PIX) planning, 618 RXCDR to BSC link planning, 64 RXCDR to MSC link planning, 66 RXU shelves, 613 transcoder planning, 68 T1 conversion, 69 remote transcoder planning overview, 62 outline of planning steps, 63 RF plan, choice, 820 RF provisioning, GPRS control channel, 313 RSL, signalling, 539 RSL capacity. See BSC to BTS singalling link capacity RTF path, fault containment, 515 RXCDR to BSC link planning, 64 16 k XBL links, 218 E1 links, 65 T1 links, 65 RXCDR to MSC link planning, 66 E1 links, 66 T1 links, 66 RXU shelves, 613
S
scaleable BSC, 56 scaleable OMCR options, 76 outline of planning steps, 72 server composition, 76 workstation composition, 76 short message service, cell broadcast, 17 signalling BSC-PCU, 542 RSL, 539 single cabinet configuration with multiple antennas and diversity, 1147 single cabinet, five DRCU/SCU configuration with combining, 1140 single cabinet, multiple antenna configuration, 1145 single cabinet, single DRCU/SCU configuration, 1137
14th Apr 00
xv
GSM-001-103
single cabinet, single DRCU/SCU configuration with diversity, 1139 single cabinet, six DRCU/SCU configuration with combining, 1142 single Horizonmacro configuration, 910 single MCell2 configuration, 912 single MCell6 configuration, 911 six sector BTS6 configuration, 1156 six sector configuration, 1154 SMS, cell broadcast, 515 star connection, 25 statistics, BSS, 515 statistics for replanning, GPRS network, 327 supported redundancy, N+1 equipment, 530 switchable timeslots, network provisioning, 339 synthesizer hopping, 17 system architecture, 13 system components, 14
T
T1 conversion, 567, 69, 1030 three cabinet MCell2 configuration, 916 throughput, air interface, 351 throughput estimation step 1, 352 step 2, 353 step 3, 356 step 4, 357 timeslot allocation, Figure 311, 338 timeslot switch (TSW) planning, 1125 timeslots, use, 329 traffic BSC-PCU, 542, 550 GPRS timeslots, 539 traffic and signalling, PCU-SGSN, 545 transcoder (XCDR, GDP) planning, 566, 68, 1029 transmit combiner shelf planning, 1117 transmit configuration planning, 48 two cabinet Horizonmacro configuration, 913 two cabinet MCell6 configuration, 914 typical call parameters for BSS planning, 59, 107 typical call parameters for BTS planning, 311, 114
U
use, timeslots, 329
xvi
14th Apr 00
GSM-001-103
14th Apr 00
xvii

Motorola BSS Planning Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Motorola BSS Planning Guide

Uploaded by

Copyright:

Available Formats

For:rrobot Printed on:Thu, Aug 3, 2000 02:44:08 From book:68P02900W21-G-UK-GA Document:tabs 1 Last saved on:Thu, Aug 3, 2000 02:44:07

CHAPTER 2 TRANSMISSION SYSTEMS

CHAPTER 3 BSS CELL PLANNING

CHAPTER 4 BTS PLANNING STEPS AND RULES

CHAPTER 5 BSC PLANNING STEPS AND RULES

CHAPTER 6 RXCDR PLANNING STEPS AND RULES

CHAPTER 7 OMC-R PLANNING STEPS AND RULES

CHAPTER 8 PLANNING EXERCISE

CHAPTER 9 STANDARD CONFIGURATIONS

CHAPTER 10 PREVIOUS BSC PLANNING STEPS AND RULES

CHAPTER 11 PREVIOUS BTS PLANNING

Cellular Infrastructure Group

SYSTEM INFORMATION BSS EQUIPMENT PLANNING SOFTWARE RELEASE 1.6.1.3

SYSTEM INFORMATION BSS EQUIPMENT PLANNING

SYSTEM INFORMATION BSS EQUIPMENT PLANNING

System Information BSS Equipment Planning

E Motorola 1993 - 2000 All Rights Reserved Printed in the U.K.

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Copyrights, notices and trademarks

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 2 Transmission systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 3 BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

3112 3112 3113 3114 3115

Chapter 4 BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 5 BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 6 RXCDR planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 7 OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 8 Planning exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9 Standard configuration descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 10 Previous BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Chapter 11 Previous generation BTS planning and equipment descriptions . . . . . . . .

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

System Information: BSS Equipment Planning 68P02900W21-G

SOFTWARE RELEASE 1.6.1.3

Issue status of this manual

Issue status of this manual