Beruflich Dokumente
Kultur Dokumente
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
INDEX
GSM-001-103
GSM-001-103
68P02900W21-G
GSM-001-103
14th Apr 00
GSM-001-103
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
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
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
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
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
i
71 71 71 71 72 73 76
14th Apr 00
GSM-001-103
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
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
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
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
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
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.
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.
14th Apr 00
GSM-001-103
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
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
GSM-001-103
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.
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.
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
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.
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
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.
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
GSM-001-103
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.
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
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
GSM-001-103
16
14th Apr 00
GSM-001-103
14th Apr 00
17
GSM-001-103
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
GSM-001-103
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
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.
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.
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.
14th Apr 00
17
BSS features
GSM-001-103
18
14th Apr 00
GSM-001-103
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
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
RXCDR SGSN
GDS Gb OPTION A
PCU
CBL
CBC
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
22
GSM-001-103
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
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 1
BSC
BTS 5
14th Apr 00
25
Network topology
GSM-001-103
BTS 3 BTS 2
DAISY CHAIN CLOSED LOOP
BTS 4 BTS 10
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
26
14th Apr 00
GSM-001-103
Network topology
Tx
Rx
Tx
Rx
BSC
Rx Tx
BTS 1
Rx Tx Rx
BTS 2
Tx
Tx
Rx Tx
Rx
BTS 3
Rx Tx
BTS 4
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
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
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
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
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
14th Apr 00
29
Network topology
GSM-001-103
BSC
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
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 31 30 29 28
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
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
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
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
BCCH
NON-BCCH
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
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.
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
Dynamic Allocation
Erlang
Erlang B
PATH devices
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
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.
14th Apr 00
221
BTS concentration
GSM-001-103
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
14th Apr 00
223
BTS concentration
GSM-001-103
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
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
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
BSC
BTS 1
BTS 2
BTS 3
BSC
BTS 1
BTS 2
BTS 3
226
14th Apr 00
GSM-001-103
BTS concentration
BSC
BTS 1
BSC
BTS 1
BTS 2
BTS 3
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
BSC
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
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
14th Apr 00
229
BTS concentration
GSM-001-103
BSC
BTS 1
BTS 2
BTS 3
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
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).
232
14th Apr 00
GSM-001-103
BTS concentration
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.
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
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
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
240
14th Apr 00
GSM-001-103
14th Apr 00
241
GSM-001-103
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.
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 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
BSC
E1 LINK
E1 LINK
HDSL
HDSL
E1 LINK
BTS
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
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
PCC CABINET
SITE B
14th Apr 00
247
GSM-001-103
248
14th Apr 00
Chapter 3
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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
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
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
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-001-103
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
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
14th Apr 00
35
GSM-001-103
BTS
36
14th Apr 00
GSM-001-103
CHANNEL 1 dBs
0 10 20 30 40 50 60 70
CHANNEL 2
CHANNEL 3
200 kHz
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
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.
14th Apr 00
311
Capacity calculations
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
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.
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.
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
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
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.
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
S S
BORDER BTS =
INNER BTS =
LOCATION AREA
14th Apr 00
GSM-001-103
14th Apr 00
321
GSM-001-103
322
14th Apr 00
GSM-001-103
14th Apr 00
323
GSM-001-103
324
14th Apr 00
GSM-001-103
14th Apr 00
325
GSM-001-103
BSS/PCU/GSN STATS_B
BSS/PCU
CONFIGURE INFRASTRUCTURE
GSN STATS_C
BSS/PCU STATS_D
14th Apr 00
GSM-001-103
S S
S S
14th Apr 00
327
GSM-001-103
328
14th Apr 00
GSM-001-103
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
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
14th Apr 00
331
GSM-001-103
332
14th Apr 00
GSM-001-103
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
334
14th Apr 00
GSM-001-103
TS0
TS0
CARRIER 2 S S R R R
14th Apr 00
335
GSM-001-103
TS0
TS0
CARRIER 2 S S S S S
TS0
CARRIER 2 R R R R R R R R
14th Apr 00
GSM-001-103
14th Apr 00
337
GSM-001-103
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
14th Apr 00
339
GSM-001-103
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.
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
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
14th Apr 00
345
GSM-001-103
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.
Network dependent
Network dependent
240
The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13.
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.
Network dependent
270
90
Network dependent
810
The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13.
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.
98 kbytes/hour
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.)
No maximum limit other than what the network is provisioned to support Network dependent 64
The air interface planning process uses the range of values listed in Table 3-8 to Table 3-13.
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
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.
14th Apr 00
351
GSM-001-103
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.
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.
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.
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
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.
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
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
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
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
14th Apr 00
361
GSM-001-103
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
HEIGHT (km)
340
RRI (N)
14th Apr 00
363
GSM-001-103
EARTH
NORMAL REFRACTION
EARTH
SUPER REFRACTION
EARTH
SUB-REFRACTION
14th Apr 00
GSM-001-103
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
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
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
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
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
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
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
THRESHOLD
DISTANCE
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
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
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
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.
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
Rx
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.
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
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
14th Apr 00
377
GSM-001-103
378
14th Apr 00
GSM-001-103
110
922 MHz
100 h.= 320 m h.= 220 m 90
X X X
Free Space
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
14th Apr 00
379
GSM-001-103
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
14th Apr 00
381
GSM-001-103
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
14th Apr 00
GSM-001-103
170
160
140
130
GSM900
120
DCS1800 (MEDIUM SIZED CITIES AND SUBURBAN CENTRES)
110
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
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
75dBm
INTERFERING BTS
MOBILE POSITION
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
EXAMPLE b1 b2 a1 a2 a3 c2 c3 c1 b3 a2
386
14th Apr 00
GSM-001-103
Frequency re-use
60 SECTORS
14th Apr 00
387
Frequency re-use
GSM-001-103
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
Therefore Thus
D + 4 47.66 + 2.62 R
C/
BS R
MS
BS
D
ANALOGUE SYSTEM D/R = 4.4 GSM SYSTEM D/R= 2.62
14th Apr 00
GSM-001-103
Frequency re-use
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
GSM-001-103
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
SPEECH (8 BURSTS)
ENCODING
INTERLEAVING
CONTROL (4 BURSTS)
392
14th Apr 00
GSM-001-103
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
8 x TCH FR (BURSTS) 8 x TCH EFR (BURSTS) 8 x FACCH/TCH (BURSTS) 8 x TCH 2-4 kBIT/S (BURSTS)
14th Apr 00
393
GSM-001-103
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
14th Apr 00
395
GSM-001-103
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
CLASS 1a 50 BITS
CLASS 2 78 BITS
260 BITS Figure 3-45 Preliminary coding for enhanced full rate speech
396
14th Apr 00
GSM-001-103
184
PARITY BITS
FIRE CODE
TAIL BITS
184
40
CONVOLUTIONAL CODE
456
456 BITS
14th Apr 00
397
GSM-001-103
240
CONVOLUTIONAL CODE
488
PUNCTUATE
456
14th Apr 00
GSM-001-103
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
3100
012345678 .... 113
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
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
ODD
BURSTS
FRAME 1
FRAME 2
3102
0 1 2 3 4 5 6 7
FRAME 3
14th Apr 00
GSM-001-103
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
14th Apr 00
GSM-001-103
S A C C H 0
S A C C H
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
METHODS OF UTILIZATION: a. b. c. SWITCHED. PHASE ALIGNED AND SUMMED. PHASE ALIGNED WITH MINIMUM DISTORTION.
BTS
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.
14th Apr 00
3 bits
3107
Subscriber environment
GSM-001-103
Subscriber environment
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
TUNNELS
14th Apr 00
GSM-001-103
Subscriber environment
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%
14th Apr 00
3109
Subscriber environment
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
Subscriber environment
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
GSM-001-103
TOP VIEW
SIDE VIEW
3112
MACROCELL
MICROCELL A MICROCELL B
MACROCELL
MICROCELL A
MICROCELL B
14th Apr 00
GSM-001-103
CONTIGUOUS COVERAGE OVER AREAS OF HIGH SLOW MOVING TRAFFIC DENSITY OVERLAYED MACROCELLS
14th Apr 00
3113
GSM-001-103
MSC BSC A
BTS 3
PICOCELL
MACROCELL COVERAGE
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
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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
GSM-001-103
42
14th Apr 00
GSM-001-103
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
Receive configurations
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.
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
Receive configurations
4.
14th Apr 00
47
Transmit configurations
GSM-001-103
Transmit configurations
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.
Planning considerations
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
48
14th Apr 00
GSM-001-103
Transmit configurations
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
14th Apr 00
49
Antenna configurations
GSM-001-103
Antenna configurations
Planning considerations
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.
410
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
411
GSM-001-103
Planning considerations
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.
412
14th Apr 00
GSM-001-103
Planning considerations
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.
414
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
415
GSM-001-103
Planning considerations
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.
416
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
417
GSM-001-103
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.
Planning considerations
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.
14th Apr 00
419
GSM-001-103
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.
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.
14th Apr 00
421
GSM-001-103
Planning considerations
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.
422
14th Apr 00
Chapter 5
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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
GSM-001-103
52
14th Apr 00
GSM-001-103
14th Apr 00
53
Capacity calculations
GSM-001-103
Capacity calculations
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
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
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
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
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT HARDWARE FOR THE A AND BSC TO BTS INTERFACE.
58
14th Apr 00
GSM-001-103
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
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
GSM-001-103
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).
14th Apr 00
GSM-001-103
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.
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
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)
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.
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
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
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 Gb OPTION C
BTS1
BTSn
14th Apr 00
523
GSM-001-103
OMC-R
RXCDR
524
14th Apr 00
GSM-001-103
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
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
15
16 17 18
19
PICP board
20 21 22 23 24
PICP board PICP board PICP board PMC module PMC module
25 26
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
528
14th Apr 00
GSM-001-103
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
TRANSITION MODULE
H T T T T T T S MMMMM MC
T T T T T MMMMM
I O
14th Apr 00
529
GSM-001-103
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.
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 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
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
TRAU-Type GDS links (E1s) GBL links (E1s) Gb PVCs Gb Frame Relay frame octet size
532
14th Apr 00
GSM-001-103
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
PMC
PRP2
PMC
PRP9 REDUNDANT
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
PMC
PRP2
PMC
PRP9
GSL 6 LAPD TS
PMC PMC
PICP1
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 No No No Yes Yes
14th Apr 00
537
GSM-001-103
Planning considerations
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
538
14th Apr 00
GSM-001-103
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
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.
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
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
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.
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
These frame relay parameter values are determined as detailed in the following text.
14th Apr 00
547
GSM-001-103
548
14th Apr 00
GSM-001-103
Equation 18
n
CIR_Value +
+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:
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.
14th Apr 00
549
GSM-001-103
550
14th Apr 00
GSM-001-103
14th Apr 00
551
GSM-001-103
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.
552
14th Apr 00
GSM-001-103
Step 3
The number of LCFs required is the greater of GRSL and GL3.
14th Apr 00
553
GSM-001-103
Equation 26
G L3_GPRS + Where:
G N GPRS *T GPRS_PF GPRS
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
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
14th Apr 00
555
GSM-001-103
Planning considerations
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 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
14th Apr 00
557
GSM-001-103
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:
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
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.
560
14th Apr 00
GSM-001-103
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).
Planning considerations
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
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
564
14th Apr 00
GSM-001-103
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.
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.
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.
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
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
Planning considerations
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
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
Planning considerations
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
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.
Planning considerations
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
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
GSM-001-103
Planning considerations
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.
574
14th Apr 00
GSM-001-103
For example:
14th Apr 00
575
GSM-001-103
Planning considerations
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.
576
14th Apr 00
GSM-001-103
Planning considerations
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).
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
GSM-001-103
Planning considerations
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.
BSU 14
578
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
579
GSM-001-103
Planning considerations
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.
580
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
581
GSM-001-103
Planning considerations
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.
582
14th Apr 00
GSM-001-103
14th Apr 00
583
GSM-001-103
584
14th Apr 00
Chapter 6
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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
GSM-001-103
62
14th Apr 00
GSM-001-103
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
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
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT HARDWARE FOR THE A AND BSC TO BTS INTERFACE.
14th Apr 00
GSM-001-103
14th Apr 00
65
GSM-001-103
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.
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
Planning considerations
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.
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 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.
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. .
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.
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
69
GSM-001-103
Planning considerations
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
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
Planning considerations
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
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.
Planning considerations
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.
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
Planning considerations
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, 9 per KSW.
614
14th Apr 00
GSM-001-103
Planning considerations
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
Planning considerations
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).
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
Planning considerations
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.
RXU 14
14th Apr 00
617
GSM-001-103
Planning considerations
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.
618
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
619
GSM-001-103
Planning considerations
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.
620
14th Apr 00
GSM-001-103
Planning considerations
The following factors should be considered when planning the BBBX complement: S One BBBX is required per shelf.
14th Apr 00
621
GSM-001-103
If necessary, add extra RXU shelves. Each BSSC cabinet supports two RXU shelves.
622
14th Apr 00
Chapter 7
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
i
71 71 71 71 72 73 76
14th Apr 00
iii
GSM-001-103
iv
14th Apr 00
GSM-001-103
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
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
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
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
14th Apr 00
75
GSM-001-103
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
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
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
Horizonmicro M-Cellaccess
82
14th Apr 00
GSM-001-103
Initial requirements
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
Initial requirements
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
BTS 2
BTS 6
BTS 11
BTS 3
BTS 7
BTS 9
BTS 4
BTS 8
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
GSM-001-103
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.
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
4 to 11
SWUF2941
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
88
14th Apr 00
GSM-001-103
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.
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
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
GSM-001-103
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
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
GSM-001-103
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
SWDN5025 SWDN4894
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
GSM-001-103
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.
820
14th Apr 00
GSM-001-103
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.
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 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.
14th Apr 00
823
GSM-001-103
824
14th Apr 00
GSM-001-103
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
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
828
14th Apr 00
GSM-001-103
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.
14th Apr 00
829
GSM-001-103
830
14th Apr 00
Chapter 9
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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.
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
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
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
14th Apr 00
93
GSM-001-103
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
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
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
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
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
14th Apr 00
95
GSM-001-103
P C U 1
P C U 2
P C U 3
P C U 4
P C U 5
P C U 6
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
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
PCC CABINET
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
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LANX A
BSC
Figure 9-5 Single BTS site with six PCUs using HDSL links
14th Apr 00
97
GSM-001-103
PCU 1 to 6
PCU 7 to 12
PCC CABINET
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LANX A
DRIX 1
DRIX 2
DRIX 3
DRIX 4
DRIX 5
DRIX 6
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
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
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LANX A
HRIX 1
HRIX 2
HRIX 3
HRIX 4
HRIX 5
HRIX 6
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
DRIM 5
DRIM 6
BTC
GCLK
TSW A
MSI
GPROC
GPROC
GPROC
LANX A
BSC
Figure 9-7 Two BTS site with 12 PCUs using HDSL links
14th Apr 00
99
GSM-001-103
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
910
14th Apr 00
GSM-001-103
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
14th Apr 00
911
GSM-001-103
N I U
mBCU
N I U
mBCU
MCU
MCU
(FOR REDUNDANCY)
2 T C U
T C U
M-CELL2 CABINET
912
14th Apr 00
GSM-001-103
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
14th Apr 00
913
GSM-001-103
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
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
914
14th Apr 00
GSM-001-103
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
14th Apr 00
915
GSM-001-103
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
916
14th Apr 00
GSM-001-103
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
14th Apr 00
917
GSM-001-103
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
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
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
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
918
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
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
Macrocell RF configurations
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
Macrocell RF configurations
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
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
Horizonmacro CABINET
Figure 9-18 [GSM1800] 6 carrier Omni with duplexed dual-stage hybrid and air combining
922
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
B2 1 0 A 2 1 0
B A
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
Horizonmacro CABINET
Figure 9-19 [GSM1800] 2 sector (3/3) with duplexed dual-stage hybrid combining
924
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
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
Figure 9-20 [GSM1800] 2 sector (6/6) with duplexed dual-stage hybrid and air combining
926
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
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
Horizonmacro CABINET
928
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
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
Figure 9-22 [GSM1800] 3 sector (4/4/4) with duplexed hybrid and air conditioning
930
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
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
B2 1 0 A 2 1 0
B A
B2 1 0 A 2 1 0
B A
SURF
SURF
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
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
Macrocell RF configurations
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
Macrocell RF configurations
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
Macrocell RF configurations
M-Cell6 cabinets
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
Figure 9-25 [GSM900] 3 carrier Omni with hybrid combining and diversity
14th Apr 00
935
Macrocell RF configurations
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
Macrocell RF configurations
[GSM900] 3 carrier Omni, with hybrid combining, diversity, and mediumpower duplexer
A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 9-26. Table 9-9 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 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
Figure 9-26 [GSM900] 3 carrier Omni with hybrid combining and diversity
14th Apr 00
937
Macrocell RF configurations
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
Macrocell RF configurations
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
Figure 9-27 [GSM900] 4 carrier Omni with hybrid combining and diversity
14th Apr 00
939
Macrocell RF configurations
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
Macrocell RF configurations
[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.
Tx/Rx ANTENNA Rx ANTENNA
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
Figure 9-28 [GSM900] 4 carrier Omni with hybrid combining, diversity, and mediumpower duplexer
14th Apr 00
941
Macrocell RF configurations
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
Macrocell RF configurations
(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
Figure 9-29 [GSM900] 6 carrier Omni with cavity combining and diversity
14th Apr 00
943
Macrocell RF configurations
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
Macrocell RF configurations
[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
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-30 [GSM900] 6 carrier Omni with cavity combining, diversity, and highpower duplexer
14th Apr 00
945
Macrocell RF configurations
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
Macrocell RF configurations
Tx ANTENNA
Tx/Rx ANTENNA
Rx ANTENNA
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
14th Apr 00
947
Macrocell RF configurations
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
Macrocell RF configurations
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
Figure 9-32 [GSM900] 2 sector (3/3), with hybrid combining and diversity
14th Apr 00
949
Macrocell RF configurations
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
Macrocell RF configurations
[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
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
Figure 9-33 [GSM900] 2 sector (3/3), with hybrid combining, diversity, and mediumpower duplexer
14th Apr 00
951
Macrocell RF configurations
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
Macrocell RF configurations
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
14th Apr 00
953
Macrocell RF configurations
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
Macrocell RF configurations
[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)
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
Figure 9-35 [GSM900] 3 sector (2/2/2), with combining, diversity, and mediumpower duplexer
14th Apr 00
955
Macrocell RF configurations
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
Macrocell RF configurations
[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
Macrocell RF configurations
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
Macrocell RF configurations
[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.
Tx/Rx ANTENNA (SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 2) Tx/Rx ANTENNA (SECTOR 1)
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
Macrocell RF configurations
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
Macrocell RF configurations
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
Macrocell RF configurations
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
Macrocell RF configurations
[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
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
Macrocell RF configurations
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
Macrocell RF configurations
[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)
Rx ANTENNA (SECTOR 3)
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
Macrocell RF configurations
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
Macrocell RF configurations
[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
Macrocell RF configurations
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
Macrocell RF configurations
[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
Extender 1 and Extender 2 M-Cell6 cabinets configured similar to the Master cabinet for Sectors 2 and 3.
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
Macrocell RF configurations
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
Macrocell RF configurations
[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
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
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
Macrocell RF configurations
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
Macrocell RF configurations
[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
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
Extender 1 and Extender 2 M-Cell6 cabinets configured similar to the Master cabinet for Sectors 2 and 3.
Figure 9-44 [GSM900] 3 sector (6/6/6), with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector)
14th Apr 00
973
Macrocell RF configurations
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
Macrocell RF configurations
[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
RF INPUT RF LOAD 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
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-45 [GSM900] 3 sector (6/6/6), with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector)
14th Apr 00
975
Macrocell RF configurations
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
Macrocell RF configurations
14th Apr 00
977
Macrocell RF configurations
GSM-001-103
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
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-46 [GSM900] 3 sector (8/8/8), with cavity combining and diversity
978
14th Apr 00
GSM-001-103
Macrocell RF configurations
Rx ANTENNA (SECTOR 1)
Tx ANTENNA (SECTOR 1)
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 2 and Extender 3 M-Cell6 cabinets configured similar to the Extender 1 cabinet for Sectors 2 and 3.
Figure 9-47 [GSM900] 3 sector (8/8/8), with cavity combining and diversity
14th Apr 00
979
Macrocell RF configurations
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
Macrocell RF configurations
14th Apr 00
981
Macrocell RF configurations
GSM-001-103
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
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
Macrocell RF configurations
DLNB
IADU
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
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
Macrocell RF configurations
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
Macrocell RF configurations
14th Apr 00
985
Macrocell RF configurations
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 2)
Rx ANTENNA (SECTOR 3)
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
Figure 9-50 [GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector)
986
14th Apr 00
GSM-001-103
Macrocell RF configurations
Rx EXT BLOCK
Rx ANTENNA (SECTOR 2)
RF INPUT RF LOAD
Tx ANTENNA (SECTOR 1)
Rx ANTENNA (SECTOR 1)
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
Figure 9-51 [GSM900] 3 sector (8/8/8), with 3-input CBF, air combining, diversity, and mediumpower duplexer (3 antenna per sector)
14th Apr 00
987
Macrocell RF configurations
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
Macrocell RF configurations
14th Apr 00
989
Macrocell RF configurations
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
Figure 9-52 [GSM900] 3 sector (8/8/8), with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector)
990
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Figure 9-53 [GSM900] 3 sector (8/8/8), with 3-input CBF, combining, diversity, and mediumpower duplexer (2 antenna per sector)
14th Apr 00
991
Macrocell RF configurations
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
Macrocell RF configurations
14th Apr 00
993
Macrocell RF configurations
GSM-001-103
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
Figure 9-54 [DCS1800] 3 sector (2/2/2), with hybrid combining and diversity
994
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
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
Figure 9-55 [DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and mediumpower duplexers
996
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
M-Cell2 cabinets
DLNB
CBF
T C U A B
T C U A B
Figure 9-56 [GSM900] 2 carrier, single sector, with hybrid combining and diversity
998
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
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.
Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
DLNB
CBF
T C U A B
T C U A B
Figure 9-57 [GSM900] 2 carrier, single sector, with hybrid combining, diversity, and mediumpower duplexer
9100
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
DLNB
DLNB
CBF
CBF
T C U A B
T C U A B
9102
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
DUPLEXER LNA
TxBPF
T C U A B
T C U A B
Figure 9-59 [DCS1800] 2 carrier, single sector, with air combining and diversity
9104
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
Macrocell RF configurations
GSM-001-103
LNA
LNA
TxBPF
TxBPF
T C U A B
T C U A B
9106
14th Apr 00
GSM-001-103
Macrocell RF configurations
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
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
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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
102
14th Apr 00
GSM-001-103
14th Apr 00
103
Capacity calculations
GSM-001-103
Capacity calculations
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
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
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
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT HARDWARE FOR THE A AND BSC TO BTS INTERFACE.
106
14th Apr 00
GSM-001-103
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
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
Planning considerations
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
1010
14th Apr 00
GSM-001-103
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
14th Apr 00
1011
GSM-001-103
1012
14th Apr 00
GSM-001-103
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.
14th Apr 00
1013
GSM-001-103
Step 3
The number of LCFs required is the greater of GRSL and GL3.
1014
14th Apr 00
GSM-001-103
Planning considerations
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 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
1016
14th Apr 00
GSM-001-103
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
14th Apr 00
1017
GSM-001-103
Where:
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
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
1020
14th Apr 00
GSM-001-103
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
Planning considerations
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
14th Apr 00
GSM-001-103
14th Apr 00
1025
GSM-001-103
NOTE If dedicated GPROC or GPROC2s are required for either the CSFP or OMF functions then they should be provisioned separately.
1026
14th Apr 00
GSM-001-103
NOTE The formula assumes that the same cell and channel statistics are enabled across all cells.
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.
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.
the number of MSI-2s required for T1 to E1 conversion. the number of T1 circuits required. the number of E1 circuits required.
1030
14th Apr 00
GSM-001-103
Transcoding
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
Planning considerations
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
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
Planning considerations
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
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.
Planning considerations
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
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
Planning considerations
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, 9 per KSW.
14th Apr 00
1037
GSM-001-103
For example
1038
14th Apr 00
GSM-001-103
Planning considerations
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
Planning considerations
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).
1040
14th Apr 00
GSM-001-103
Planning considerations
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.
BSU 14
14th Apr 00
1041
GSM-001-103
Planning considerations
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.
1042
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
1043
GSM-001-103
Planning considerations
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.
1044
14th Apr 00
GSM-001-103
Planning considerations
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
1046
14th Apr 00
Chapter 11
14th Apr 00
GSM-001-103
ii
14th Apr 00
GSM-001-103
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
112
14th Apr 00
GSM-001-103
14th Apr 00
113
Capacity calculations
GSM-001-103
Capacity calculations
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.
114
14th Apr 00
GSM-001-103
Capacity calculations
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
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
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.
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
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
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
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.
1110
14th Apr 00
GSM-001-103
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
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
14th Apr 00
1113
GSM-001-103
1114
14th Apr 00
GSM-001-103
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
GSM-001-103
1116
14th Apr 00
GSM-001-103
14th Apr 00
1117
GSM-001-103
Planning considerations
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
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.
Planning considerations
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.
14th Apr 00
1119
GSM-001-103
Together these three units provide a single RF carrier, which can be referred to as an RTF.
Planning considerations
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.
1120
14th Apr 00
GSM-001-103
Planning considerations
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).
14th Apr 00
1121
GSM-001-103
Planning considerations
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
14th Apr 00
1123
GSM-001-103
Planning considerations
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.
1124
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
1125
GSM-001-103
Planning considerations
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.
1126
14th Apr 00
GSM-001-103
Planning considerations
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
Planning considerations
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).
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).
1128
14th Apr 00
GSM-001-103
Planning considerations
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.
BSU 14
14th Apr 00
1129
GSM-001-103
Planning considerations
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.
1130
14th Apr 00
GSM-001-103
Planning considerations
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.
14th Apr 00
1131
GSM-001-103
Planning considerations
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
Planning considerations
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.
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
DRCU/SCUs
ONE RF CARRIER CONSISTS OF ONE DRIM, DRIX AND DRCU/SCU
BSU SHELF
DRIX 1
DRIX 2
DRIX 3
DRIX 4
PIX
BTC
DRIM 1
DRIM 2
DRIM 3
DRIM 4
BTC
GCLK
GCLK
KSW A
KSW B REDUNDANT
MSI
GPROC
GPROC
GPROC
REDUNDANT
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
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
BSC
1136
14th Apr 00
GSM-001-103
Tx BPF
DRCU/SCU
BTS CABINET
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
Tx BPF
DRCU/SCU
BTS CABINET
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
1140
14th Apr 00
GSM-001-103
Tx
Rx
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
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
Tx BPFs
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
Tx BPF
DRCU/SCUs
BTS CABINET
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
S S S
Tx BPF
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
HYBRID
DRCU/SCUs
DRCU/SCUs
BTS CABINET 1
BTS CABINET 2
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
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
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
S S
S S
1154
14th Apr 00
GSM-001-103
Tx
Tx
Tx
Rx
Rx
Rx
Rx
Rx
Rx
Tx
Tx
Tx
MULTICOUPLER
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
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
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
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
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