bss equipment planning

CHAPTER 2TRANSMISSION SYSTEMS

CHAPTER 3BSS CELL PLANNING

CHAPTER 4BTS PLANNING STEPS AND

RULES

CHAPTER 5BSC PLANNING STEPS AND

RULES

CHAPTER 1 INTRODUCTION TO

PLANNING

CHAPTER 7PCU UPGRADE FOR THE

BSS

CHAPTER 8BSC PLANNING STEPS AND

RULES FOR LCS

CHAPTER 9PLANNING EXERCISE

CHAPTER 10LOCATION AREA

PLANNING

CHAPTER 6 RXCDR PLANNING STEPS

AND RULES

CHAPTER 12STANDARD BSS & HORIZON

BTS CONFIGURATIONS

CHAPTER 13M-CELL BTS

CONFIGURATIONS

CHAPTER 14PREVIOUS GENERATIONBSC PLANNING STEPS

CHAPTER 15EQUIPMENT DESCRIPTIONS

FOR PRE M-CELL BTSs

CHAPTER 11CALL MODEL PARAMETERS

SYSTEM INFORMATIONBSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 6 (Horizon II)

GSR6 (Horizon II)

GMR-01

68P02900W21-M

SYSTEM INFORMATIONBSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 6 (Horizon II) GS

R6

(Ho

rizo

nII

)

GM

R-0

1

68P

0290

0W21

-M

30 Sep 2003

System Information: BSS Equipment Planning

68P02900W21-M

GMR-01GMR Page 1

Manual RevisionGMR-01

30 Sep 200368P02900W21-M

Motorola manualaffected

Incorporate this GMR only in the manual number and version listed below:

68P02900W21-M SYSTEM INFORMATION: BSS EQUIPMENT PLANNINGSoftware Release GSR6 (Horizon II)

Problem reports

This revision provides a fix to the following problem reports:

No new Service Requests fixed in this revision.

Reason forrevision

This revision provides additional and updated information as follows:

Chap. 2: Page 2-5: Explanatory note added.

Chap. 3: Page 3-77: Minor change to text.

Page 3-87: RACH_Arrivals equation modified.

Page 3-80: Parameter �P� changed to �PGSM� and parameter CBTS added.

Chap. 4: Page 4-13: CTU2 usage clarified and restrictions explained for whenCTU2s replace CTUs in Horizonmacro.

Page 4-24: Note added.

Chap. 5: Page 5-5: Incorrect section referenced � was RSLs, now GSLs.

Page 5-8: Text clarified.

Page 5-11: Parameter P changed to PGSM and parameter CBTS added.

Page 5-12: Parameter P changed to PGSM in Table 5-3.

Page 5-20: Parameter C changed to CBTS in equations.

Page 5-21: Definition of C changed to CBTS.

Page 5-22: BSC to BTS E1 interconnect planning actions updated.

Page 5-24: Parameter P changed to PGSM in equation and correspondingparameter definition updated.

Page 5-38: Note deleted.

Page 5-40: Corrections made to LCF planning.

Page 5-41: Calculation for equipping OMF GPROC2 removed (equippingrecommended, so equation no longer required).

Page 5-47: Text clarified for local/remote transcoding.

GSR6 (Horizon II)

30 Sep 2003GMR Page 2


GMR-0168P02900W21-M

Chap. 7: Page 7-16: Text clarified for E1 PMC modules.

Page 7-18: Additional planning consideration added for PMC module.

Page 7-29: Note added.

Chap. 8: Page 8-10: Minor change to header and text.

Chap. 9: Page 9-19: Parameter CBTS defined.

Page 9-21 & 9-33: Parameter P changed to PGSM in text.

Page 9-22, 9-23, 9-24, 9-34, 9-35: Parameter P changed to PGSM inequations.

Page 9-23 & 9-34: Parameter C changed to CBTS in equations.

Page 9-23 & 9-34: NBSC�BTS equation and subsequent calculationsupdated.

Page 9-31: Parameter C changed to CBTS.

Page 9-37: �E6� in equation corrected to �E/6�.

Chap. 11: Page 11-4: Parameter P changed to PGSM and parameter CBTS added.

Page 11-9: Parameter P changed to PGSM in text and equation.

Page 11-10: Parameter P changed to PGSM in equations.

Page 11-12: Parameter P changed to PGSM in text and equations.

Chap. 12: Page 12-17: Figure 12-12 modified.

Page 12-23: Figure 12-18 and supporting text modified to reflect Rxdiversity only.

Action

Remove and replace pages in the Manual as follows:

Remove Insert

All pages between the clear acetatefront sheet and the blank backingsheet, remove from binder.

All pages of the GMR between thefront sheet and the blank backingsheet, insert into binder.

Obsolete pages

Destroy all obsolete pages. Do not destroy this page.

Completion

On completion of the Manual Revision, insert this Manual Revision sheet in the front orback of the manual, for future reference.

30 Sep 2003


68P02900W21-M

GMR-01i

Software Release GSR6 (Horizon II)

System InformationBSS Equipment Planning

E Motorola 1994 - 2003All Rights ReservedPrinted in the UK.

GSR6 (Horizon II)

30 Sep 2003ii


GMR-0168P02900W21-M

Copyrights, notices and trademarks

CopyrightsThe Motorola products described in this document may include copyrighted Motorola computerprograms stored in semiconductor memories or other media. Laws in the United States and othercountries preserve for Motorola certain exclusive rights for copyright computer programs, including theexclusive right to copy or reproduce in any form the copyright computer program. Accordingly, anycopyright Motorola computer programs contained in the Motorola products described in this documentmay not be copied or reproduced in any manner without the express written permission of Motorola.Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or byimplication, estoppel or otherwise, any license under the copyrights, patents or patent applications ofMotorola, except for the rights that arise by operation of law in the sale of a product.

RestrictionsThe software described in this document is the property of Motorola. It is furnished under a licenseagreement and may be used and/or disclosed only in accordance with the terms of the agreement.Software and documentation are copyright materials. Making unauthorized copies is prohibited bylaw. No part of the software or documentation may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any language or computer language, in any form or by anymeans, without prior written permission of Motorola.

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

Trademarks

and MOTOROLA are registered trademarks of Motorola Inc. Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.All other brands and corporate names are trademarks of their respective owners.

.

.

.

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01iii

Contents

Issue status of this manual 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General information 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reporting safety issues 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warnings and cautions 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General warnings 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General cautions 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Devices sensitive to static 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola manual sets 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GMR amendment 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GMR amendment record 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1Introduction to planning 1�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 1�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning 1�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Manual overview 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 1�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS equipment overview 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System architecture 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System components 1�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiver units 1�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS features 1�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features that affect planning 1�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diversity 1�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency hopping 1�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Short message service, cell broadcast 1�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor 1�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU for GPRS upgrade 1�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS planning overview 1�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 1�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial information required 1�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning methodology 1�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Acronyms 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acronym list 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2Transmission systems 2�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 2�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS interfaces 2�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interconnecting the BSC and BTSs 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interconnection rules 2�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003iv


GMR-0168P02900W21-M

Network topology 2�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Star connection 2�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain connection 2�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daisy chain planning 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aggregate Abis 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTF path fault containment 2�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s RSL 2�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 kbit/s XBL 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic allocation of RXCDR to BSC circuits (DARBC) 2�21 . . . . . . . . . . . . . . . . . . . .

BTS concentration 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key terms 2�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DYNET 2�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking considerations 2�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio signalling link (RSL) planning 2�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network topologies 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance issues 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration and compatibility issues 2�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended BTS concentration planning guidelines 2�35 . . . . . . . . . . . . . . . . . . . . . Examples 2�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS concentration resource optimization for handovers (BCROH) 2�43 . . . . . . . . . . . BCROH description 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managed HDSL on micro BTSs 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 2�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated HDSL interface 2�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General HDSL guidelines 2�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microcell system planning 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell system planning 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3BSS cell planning 3�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS cell planning 3�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS planning requirements 3�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning factors 3�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Planning tools 3�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 3�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM frequency spectrum 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GSM900 frequency spectrum 3�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The DCS1800 frequency spectrum 3�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absolute radio frequency channel capacity 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modulation techniques and channel spacing 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Traffic capacity 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensioning 3�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel blocking 3�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Traffic flow 3�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grade of service 3�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Propagation effects on GSM frequencies 3�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Propagation production 3�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decibels 3�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fresnel zone 3�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio refractive index (RRI) 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental effects on propagation 3�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multipath propagation 3�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM900 path loss 3�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Path loss GSM900 vs DCS1800 3�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01v

Frequency re-use 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to re-use patterns 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-use pattern 3�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier/ Interference (C/I) ratio 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other sources of interference 3�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectorization of sites 3�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overcoming adverse propagation effects 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware techniques 3�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error protection and detection 3�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM speech channel encoding 3�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM speech channel coding for enhanced full rate 3�50 . . . . . . . . . . . . . . . . . . . . . . . . GSM control channel encoding 3�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM circuit-switched data channel encoding 3�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping logical channels onto the TDMA frame structure 3�53 . . . . . . . . . . . . . . . . . . . GPRS channel coding schemes 3�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 kbit/s TRAU 3�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice activity detection (VAD) 3�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuous transmission (DTX) 3�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive diversity 3�63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Subscriber environment 3�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber hardware 3�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment 3�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution 3�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hand portable subscribers 3�67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future planning 3�68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The microcellular solution 3�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layered architecture 3�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture 3�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined cell architecture structure 3�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion solution 3�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frequency planning 3�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to frequency planning 3�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules for synthesizer frequency hopping (SFH) 3�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules for baseband hopping (BBH) 3�76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2G�3G handovers using inter-radio access technology 3�77 . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to 2G�3G handovers 3�77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2G�3G handover description 3�77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Impact of 2G�3G handovers on GSM 3�78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System considerations 3�79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call model parameters for capacity calculations 3�80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 3�80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters 3�80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Control channel calculations 3�82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 3�82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 3�83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of CCCHs per BTS cell 3�85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of SDCCHs per BTS cell 3�90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control channel configurations 3�92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GPRS traffic planning 3�94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determination of expected load 3�94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network planning flow 3�94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003vi


GMR-0168P02900W21-M

GPRS network traffic estimation and key concepts 3�95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the GPRS network traffic estimation and key concepts 3�95 . . . . . . . . Dynamic timeslot mode switching 3�99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier timeslot allocation examples 3�102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS timeslot allocation methods 3�106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provisioning the network with switchable timeslots 3�108 . . . . . . . . . . . . . . . . . . . . . . . . . Recommendation for switchable timeslot usage 3�112 . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot allocation process on carriers with GPRS traffic 3�113 . . . . . . . . . . . . . . . . . . .

GPRS air interface planning process 3�114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the GPRS air interface planning process 3�114 . . . . . . . . . . . . . . . . . . . . Estimating the air interface traffic throughput 3�115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS data rates 3�124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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


BTS planning overview 4�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 4�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Macrocell cabinets 4�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizon II macro 4�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmacro 4�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizoncompact and Horizoncompact2 4�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 4�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Microcell enclosures 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro and Horizonmicro2 4�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Receive configurations 4�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver planning actions 4�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transmit configurations 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit planning actions 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Antenna configurations 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna planning actions 4�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier equipment (transceiver unit) 4�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions when using CTU2s in Horizonmacro BTSs 4�13 . . . . . . . . . . . . . . . . . . . . . CTU/CTU2 power supply considerations 4�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiver planning actions 4�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Micro base control unit (microBCU) 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MicroBCU planning actions 4�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01vii

Network interface unit (NIU) and site connection 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIU planning actions 4�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS main control unit 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations � Horizon II macro as expansion cabinet 4�21 . . . . . . . . . . . . Planning actions 4�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cabinet interconnection 4�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations � Horizon II macro as master cabinet 4�23 . . . . . . . . . . . . . . . XMUX/FMUX/FOX planning actions 4�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site expansion board planning actions (Horizon II macro only) 4�24 . . . . . . . . . . . . . . .

External power requirements 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power planning actions 4�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network expansion using macro/micro/picocell BTSs 4�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion considerations 4�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mixed site utilization 4�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCC cabinet 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions 4�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Line interface modules (HIM-75, HIM-120) 4�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 4�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 4�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIM-75/HIM-120 planning actions 4�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DRI/Combiner operability components 4�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRI and combiner relationship 4�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5BSC planning steps and rules 5�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter overview 5�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 5�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC planning overview 5�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 5�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Capacity calculations 5�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote transcoding 5�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC system capacity 5�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System capacity summary 5�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable BSC 5�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced BSC capacity option 5�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the required BSS signalling link capacities 5�9 . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model 5�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values 5�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations 5�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities 5�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003viii


GMR-0168P02900W21-M

Determining the number of RSLs required 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of RSLs 5�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 5�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 5�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions 5�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions 5�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of LCF-GPROC2s for RSL processing 5�24 . . . . . . . . . . . . .

Determining the number of MTLs required 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 5�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 5�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing 5�33 . . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link 5�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the number of XBLs required 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of XBLs 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 5�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non standard traffic model 5�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the number of GSLs required 5�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic processor (GPROC2) 5�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 functions and types 5�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types 5�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 planning actions 5�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link 5�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC2 required 5�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor 5�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 redundancy 5�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoding 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations 5�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion 5�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions for transcoding at the BSC 5�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiple serial interface (MSI, MSI-2) 5�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI/MSI-2 planning actions 5�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Kiloport switch (KSW) 5�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW planning actions 5�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSU shelves 5�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions 5�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01ix

Kiloport switch extender (KSWX) 5�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX planning actions 5�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic clock (GCLK) 5�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK planning actions 5�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clock extender (CLKX) 5�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX planning actions 5�55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local area network extender (LANX) 5�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions 5�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Parallel interface extender (PIX) 5�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX planning actions 5�57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Line interface boards (BIB, T43) 5�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions 5�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Digital shelf power supply 5�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply planning actions 5�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Battery backup board (BBBX) 5�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 5�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX planning actions 5�60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Non volatile memory (NVM) board 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Considerations 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NVM planning actions 5�61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verify the number of BSU shelves and BSSC2 cabinets 5�62 . . . . . . . . . . . . . . . . . . . . . . . . . . Verification 5�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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


Remote transcoder planning overview 6�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 6�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RXCDR to BSC connectivity 6�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity 6�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003x


GMR-0168P02900W21-M

RXCDR to BSC links 6�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions 6�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions 6�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RXCDR to MSC links 6�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interconnect planning actions 6�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 interconnect planning actions 6�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic processor (GPROC2) 6�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 6�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions 6�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoding 6�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR/GDP planning considerations 6�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion 6�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions for transcoding at the RXCDR 6�13 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiple serial interface (MSI, MSI-2) 6�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 6�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI planning actions 6�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


RXU shelves 6�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 6�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXU shelf planning actions 6�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




LAN extender (LANX) 6�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 6�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions 6�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xi

Line interfaces (BIB, T43) 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIB/T43 planning actions 6�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Non volatile memory (NVM) board 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Considerations 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NVM planning actions 6�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verify the number of RXU shelves and BSSC cabinets 6�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . Verification 6�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7PCU upgrade for the BSS 7�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter overview 7�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 7�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS planning for GPRS 7�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS planning for GPRS 7�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU to SGSN interface planning 7�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature compatibility 7�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS upgrade to support GPRS 7�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS upgrade provisioning rules 7�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum BSS configuration 7�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU hardware layout 7�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU shelf (cPCI) 7�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 7�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPROC board 7�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations (PSP use) 7�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DPROC board 7�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations (PICP or PRP use) 7�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PMC module 7�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 7�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transition module 7�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 7�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU equipment redundancy and provisioning goals 7�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for N + 1 equipment redundancy 7�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU redundancy planning 7�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the PCU 7�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xii


GMR-0168P02900W21-M

E1 link provisioning for GPRS 7�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E1 interface provisioning 7�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 7�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCU � SGSN: traffic and signalling planning 7�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 7�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb entities 7�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General planning guidelines 7�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific planning guidelines 7�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Gb signalling overhead 7�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the net Gb load 7�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb link timeslots 7�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame relay parameter values 7�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS � PCU hardware planning example for GPRS 7�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS � PCU hardware planning 7�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS � PCU planning example 7�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8BSC planning steps and rules for LCS 8�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 8�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to LCS planning 8�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LCS description 8�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCS overview 8�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The positioning mechanism 8�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System architecture 8�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of BSC planning for LCS 8�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to LCS provisioning 8�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 8�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Capacity calculations 8�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the required BSS signalling link capacities 8�12 . . . . . . . . . . . . . . . . . . . . . . . . . . BSC LCS signalling traffic model 8�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values 8�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations 8�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities 8�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the number of RSLs required 8�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 8�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of RSLs 8�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 8�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 8�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions 8�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions 8�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine the number of LCFs for RSL processing 8�19 . . . . . . . . . . . . . . . . . . . . . . . .

Determining the number of MTLs required 8�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 8�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 8�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 8�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing 8�26 . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions for transcoding at the BSC 8�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xiii

Determining the number of LMTLs required 8�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 8�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the number of LMTLs 8�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic processor (GPROC2) for LCS 8�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 8�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 functions and types 8�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 8�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9Planning exercise 9�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 9�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the planning exercise 9�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initial requirements 9�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements 9�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network topology 9�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The exercise 9�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 9�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determine the hardware requirements for BTS B 9�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 9�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet 9�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary 9�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determine the hardware requirements for BTS K 9�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 9�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet 9�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver requirements 9�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter combining requirements 9�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary 9�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determine the hardware requirements for the BSC 9�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 9�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary 9�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determine the hardware requirements for the RXCDR 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI requirements 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder requirement 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link interface 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC2 requirement 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSW requirement 9�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KSWX requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCLK requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKX requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIX requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BBBX requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX requirement 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power supply 9�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary 9�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculations using alternative call models 9�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 9�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning example 1 9�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning example 2 9�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xiv


GMR-0168P02900W21-M

A planning example of BSS support for LCS provisioning 9�42 . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the LCS planning example 9�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values 9�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCS planning example calculations 9�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10Location area planning 10�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location area planning overview 10�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to location area planning 10�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location area planning considerations 10�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location area planning calculations 10�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example procedure 10�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11Deriving call model parameters from network statistics 11�1 . . . . . . . . . . . . . . .

Chapter overview 11�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to deriving call model parameters 11�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deriving call model parameters from network statistics 11�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard call model parameters 11�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call duration (T) 11�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ratio of SMSs per call (S) 11�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ratio of handovers per call (H) 11�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ratio of intra BSS handovers to all handovers (i) 11�7 . . . . . . . . . . . . . . . . . . . . . . . . . . Ratio of location updates per call (I) 11�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ratio of IMSI detaches per call (I) 11�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location update factor (L) 11�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging rate (PGSM) 11�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pages per call (PPC) 11�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample statistic calculations 11�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12Standard BSS and Horizon BTS configurations 12�1 . . . . . . . . . . . . . . . . . . . . . . .

Chapter overview 12�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS/BTS equipment covered 12�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard configurations 12�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to standard configurations 12�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typical BSS configurations 12�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with 24 BTSs 12�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC with full redundancy 12�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder 12�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Single cabinet BTS configurations 12�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet Horizon II macro BTS 12�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet Horizonmacro BTS 12�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Two cabinet BTS configurations 12�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two cabinet Horizon II macro BTS 12�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two cabinet Horizonmacro BTS 12�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Three cabinet BTS configurations 12�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three cabinet Horizon II macro BTS 12�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three cabinet Horizonmacro BTS 12�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xv

Four cabinet BTS configurations 12�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four cabinet Horizon II macro BTS 12�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four cabinet Horizonmacro BTS 12�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Horizon macrocell RF configurations 12�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of configuration diagrams 12�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizon II macro cabinets 12�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [DCS1800] 4 or 8 carrier omni with HCUs and air combining 12�17 . . . . . . . . . . . . . . . . [DCS1800] 6 or 12 carrier omni with DHUs 12�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [DCS1800] 2 sector 3/3 or 6/6 with DHUs 12�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining 12�20 . . . . . . . [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs 12�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining 12�22 . . . . [DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity 12�23 . . . . . . . . . . . . . . . . . . . Horizonmacro cabinets 12�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizoncompact2 12�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Microcell RF configurations 12�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Horizonmicro2 12�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Horizon II macro cabinets to Horizonmacro cabinets 12�40 . . . . . . . . . . . . . . . . . . Connection overview 12�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility issues 12�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of mixed cabinet configurations 12�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using CTU2s in Horizonmacro cabinets 12�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Horizon II macro cabinets to M-Cell6 cabinets 12�48 . . . . . . . . . . . . . . . . . . . . . . . . Connection overview 12�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility issues 12�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900 MHz BTSs 12�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1800 MHz BTSs 12�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 13M-Cell BTS configurations 13�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter overview 13�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cell equipment covered 13�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard M-Cell configurations 13�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to standard M-Cell configurations 13�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Picocell (M-Cellaccess) configurations 13�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single site 13�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two site cabinet 13�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Single cabinet BTS configurations 13�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet M-Cell6 BTS 13�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet M-Cell2 BTS 13�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Two cabinet BTS configuration 13�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two cabinet M-Cell6 BTS 13�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Three cabinet BTS configuration 13�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three cabinet M-Cell2 BTS 13�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Four cabinet BTS configuration 13�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Four cabinet M-Cell6 BTS 13�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M-Cell RF configurations 13�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of M-Cell configuration diagrams 13�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell6 cabinets 13�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . M-Cell2 cabinets 13�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xvi


GMR-0168P02900W21-M

Chapter 14Previous generation BSC planning steps and rules 14�1 . . . . . . . . . . . . . . . . . . .


BSC planning overview 14�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 14�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Capacity calculations 14�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the required BSS signalling link capacities 14�7 . . . . . . . . . . . . . . . . . . . . . . . . . . BSC signalling traffic model 14�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical parameter values 14�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assumptions used in capacity calculations 14�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link capacities 14�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the RSLs required 14�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 14�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 14�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 14�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS E1 interconnect planning actions 14�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC to BTS T1 interconnect planning actions 14�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for RSL processing 14�15 . . . . . . . . . . . . . . . . . . . . . . . . . Assigning BTSs to LCFs 14�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining the number of MTLs required 14�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 14�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard traffic model 14�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-standard traffic model 14�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate the number of LCFs for MTL processing 14�21 . . . . . . . . . . . . . . . . . . . . . . . . . MSC to BSC signalling over a satellite link 14�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generic processor (GPROC, GPROC2) 14�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC functions and types 14�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC types 14�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 14�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR3) 14�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC planning actions (GSR2 and earlier) 14�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell broadcast link 14�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMF GPROC required 14�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Code storage facility processor 14�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC redundancy 14�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcoding 14�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDP/XCDR planning considerations 14�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 conversion 14�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning actions transcoding at the BSC 14�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xvii


BSU shelves 14�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 14�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSU shelf planning actions 14�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




LAN extender (LANX) 14�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 14�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 14�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions 14�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Verify the number of BSU shelves and BSSC2 cabinets 14�46 . . . . . . . . . . . . . . . . . . . . . . . . . . Verification 14�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 15Planning and equipment descriptions for pre M-Cell BTSs 15�1 . . . . . . . . . . . . . Chapter overview 15�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 15�3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTS planning steps and rules 15�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline of planning steps 15�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xviii


GMR-0168P02900W21-M

Capacity calculations 15�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical call parameters 15�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Control channel calculations 15�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calculations for determining BTS GPROC, GPROC2 requirements 15�8 . . . . . . . . . . . . . . . . Introduction 15�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call processing functions 15�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 management 15�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning 15�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS shelf configurations 15�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for typical call mix 15�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shelf configurations for border location area call mix 15�13 . . . . . . . . . . . . . . . . . . . . . . .

BTS equipment cabinets 15�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabinet planning actions 15�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Receiver front end 15�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types EG, FG and BTS6 15�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFE in cabinet types AG, BG and DG 15�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributing Rx signals between multiple cabinets 15�16 . . . . . . . . . . . . . . . . . . . . . . . . . . RFE planning actions 15�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transmit combiner shelf 15�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combining equipment 15�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit combiner shelf planning actions 15�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Duplexer 15�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplexer planning actions 15�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX) 15�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier equipment planning actions 15�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Generic processor (GPROC, GPROC2) 15�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPROC, GPROC2 planning actions 15�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Timeslot switch (TSW) 15�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSW planning actions 15�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xix




Local area extender (LANX) 15�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LANX planning actions 15�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Digital radio interface extender (DRIX3c) 15�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning considerations 15�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRIX planning actions 15�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



BTS RF configurations 15�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction 15�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typical BTS configurations 15�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS configuration 15�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TopCell BTS configuration 15�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Single cabinet RF configurations 15�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU without diversity 15�38 . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, single DRCU/SCU with diversity 15�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, five DRCU/SCUs with combining 15�40 . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, six DRCU/SCUs with combining and diversity 15�42 . . . . . . . . . . . . . . . Single cabinet, multiple antennas 15�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single cabinet, multiple antennas with diversity 15�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiple cabinet RF configurations 15�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, four DRCU/SCUs 15�46 . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, single antenna, ten DRCU/SCUs 15�48 . . . . . . . . . . . . . . . . . . . . . . . . . Multiple cabinet, multiple antenna 15�50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Six sector configuration 15�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Six sector BTS6 configuration 15�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xx


GMR-0168P02900W21-M

Index I�1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxi

List of Figures

Figure 1-1 BSS block diagram 1�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-1 BSS interfaces 2�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-2 Possible network topology 2�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-3 Star connection 2�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-4 Closed loop and open ended daisy chains 2�8 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-5 Simple daisy chain 2�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-6 Daisy chain with branch 2�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-7 Typical low capacity BSC/BTS configuration 2�11 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-8 Example using a switching network 2�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-9 Timeslot allocation using new and old algorithms 2�13 . . . . . . . . . . . . . . . . . . . . . .

Figure 2-10 Alternative network configuration with E1/T1 switching network 2�14 . . . . . . . .

Figure 2-11 A configuration with a BTS equipped with two redundant RTFs 2�16 . . . . . . . .

Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs 2�16 . . . .

Figure 2-13 Fully equipped RTF 2�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-14 Sub-equipped RTF 2�19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-15 XBL utilization 2�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-16 A dynamic pool of terrestrial backhaul resources 2�27 . . . . . . . . . . . . . . . . . . . . .

Figure 2-17 Spoke configuration 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-18 Daisy chain configuration 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-19 Closed loop daisy chain configuration 2�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-20 Spoke configuration with three links 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-21 Daisy chain configuration with two links 2�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-22 Closed loop daisy chain configuration with three links 2�29 . . . . . . . . . . . . . . . . .

Figure 2-23 Closed loop daisy chain configuration with third party multiplexer 2�30 . . . . . . .

Figure 2-24 Extra path definition for nailed connections 2�31 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-25 Terrestrial backhaul resource nailed connection before a call 2�32 . . . . . . . . . .

Figure 2-26 Terrestrial backhaul resource connections during a call 2�32 . . . . . . . . . . . . . . .

Figure 2-27 Using redundancy for extra capacity before failure 2�33 . . . . . . . . . . . . . . . . . . .

Figure 2-28 Using redundancy for extra capacity after failure 2�33 . . . . . . . . . . . . . . . . . . . . .

Figure 2-29 BSC controlled intra cell handover 2�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-30 BSC controlled inter cell handover 2�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-31 Method 1 (override_intra_bss_pre_transfer is enabled) 2�45 . . . . . . . . . . . . . . .

Figure 2-32 Method 2 (override_intra_bss_pre_transfer is disabled) 2�46 . . . . . . . . . . . . . . .

Figure 2-33 Conversion of E1 to HDSL links by modem and microsite 2�50 . . . . . . . . . . . . .

Figure 2-34 Microcell daisy chain network configuration 2�51 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-35 Microcell star network configuration 2�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-36 Microcell configuration using E1/HDSL links 2�52 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-37 M-Cellaccess picocell system 2�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xxii


GMR-0168P02900W21-M

Figure 3-1 UK network operators 3�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-2 Eight TDMA timeslots per RF carrier 3�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-3 Modulation techniques and channel spacing 3�9 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-4 First Fresnel zone radius calculation 3�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-5 Refraction 3�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-6 Measurement of the RRI 3�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-7 Refraction effects on a microwave system 3�18 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-8 Attenuation 3�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-9 Reflection 3�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-10 Scattering 3�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-11 Diffraction 3�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-12 Polarization 3�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-13 Propagation effect � Rayleigh fading environment 3�24 . . . . . . . . . . . . . . . . . . . .

Figure 3-14 Rayleigh distribution 3�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-15 Propagation effect � Rician environment 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-16 Rician distribution 3�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-17 Plane earth loss 3�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-18 Focusing of power 3�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-19 Measurement of gain 3�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-20 In building propagation 3�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-21 Okumura propagation graphs 3�33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-22 BTS antenna height of 50 m, MS height of 1.5 m (GSM900) 3�36 . . . . . . . . . . .

Figure 3-23 BTS antenna height of 100 m, MS height of 1.5 m (GSM900) 3�36 . . . . . . . . . .

Figure 3-24 Path loss vs cell radius for small cells 3�37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-25 Adjacent cell interference 3�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-26 7 cell re-use pattern 3�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-27 4 site � 3 cell re-use pattern 3�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-28 2 site � 6 cell re-use pattern 3�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-29 Carrier interference measurements 3�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-30 The coding process 3�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-31 Error protection and detection 3�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-32 Speech channel encoding 3�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-33 Preliminary coding for enhanced full rate speech 3�50 . . . . . . . . . . . . . . . . . . . . .

Figure 3-34 Control channel coding 3�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-35 Data channel encoding 3�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-36 Diagonal interleaving � speech 3�54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-37 Rectangular interleaving � control 3�56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-38 Diagonal interleaving � CS data 3�58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-39 GPRS channel coding scheme 1 (CS1) 3�59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxiii




Figure 3-43 SACCH multiframe (480 ms) 3�62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-44 Receive diversity 3�63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-45 Training sequence code 3�64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-46 The subscriber environment 3�65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-47 Subscriber distribution 3�66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-48 Layered architecture 3�69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-49 Combined cell architecture 3�70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-50 Combined cell architecture structure 3�71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-51 Separating BCCH and TCH bands 3�72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-52 Band usage for macrocells with microcells 3�72 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-53 Frequency split for TCH re-use planning example 3�74 . . . . . . . . . . . . . . . . . . . .

Figure 3-54 Avoiding co-channel and adjacent channel interference 3�75 . . . . . . . . . . . . . . .

Figure 3-55 BBH frequency spectrum allocation 3�76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-56 GSM and UMTS system nodes and interfaces 3�79 . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-57 Location area diagram 3�90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-58 MM state models for MS and SGSN 3�98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-59 Carrier with reserved and switchable GPRS timeslots 3�107 . . . . . . . . . . . . . . . .

Figure 3-60 1 circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots 3�109

Figure 3-61 One carrier, all timeslots (8 TCHs) designated as switchable 3�109 . . . . . . . . . .

Figure 3-62 LLC_PDU frame layout 3�120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-1 DRI and combiner relationship 4�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-1 BSS planning diagram 5�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-1 BSS planning diagram 6�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-2 Sub-multiplexing and speech transcoding at the RXCDR 6�11 . . . . . . . . . . . . . . .

Figure 7-1 Gb interface alternatives 7�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-2 PCU shelf layout 7�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-3 Goal: maximum throughput and coverage, fully redundant configuration 7�21 . .

Figure 7-4 Goal: maximum throughput and coverage, full redundancy not required 7�22 . .

Figure 7-5 Frame relay parameters 7�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-6 PCU equipment and link planning 7�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8-1 Generic LCS logical architecture 8�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8-2 NSS-based architecture 8�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8-3 BSS-based architecture 8�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9-1 Network topology 9�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10-1 Four BSCs in one LAC 10�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10-2 Four BSCs divided into two LACs 10�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xxiv


GMR-0168P02900W21-M

Figure 12-1 BSC controlling 24 BTSs 12�5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-2 Fully redundant BSC controlling 34 BTSs 12�6 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-3 BSSC cabinet equipped to provide transcoding 12�7 . . . . . . . . . . . . . . . . . . . . . .

Figure 12-4 Macrocell BTS with one Horizon II macro cabinet 12�8 . . . . . . . . . . . . . . . . . . . .

Figure 12-5 Macrocell BTS with one Horizonmacro cabinet 12�9 . . . . . . . . . . . . . . . . . . . . . .

Figure 12-6 Macrocell BTS with two Horizon II macro cabinets 12�10 . . . . . . . . . . . . . . . . . . .

Figure 12-7 Macrocell BTS with two Horizonmacro cabinets 12�11 . . . . . . . . . . . . . . . . . . . . . .

Figure 12-8 Macrocell BTS with three Horizon II macro cabinets 12�12 . . . . . . . . . . . . . . . . . .

Figure 12-9 Macrocell BTS with three Horizonmacro cabinets 12�13 . . . . . . . . . . . . . . . . . . . .

Figure 12-10 Macrocell BTS with four Horizon II macro cabinets 12�14 . . . . . . . . . . . . . . . . . .

Figure 12-11 Macrocell BTS with four Horizonmacro cabinets 12�15 . . . . . . . . . . . . . . . . . . . .

Figure 12-12 [DCS1800] 4 or 8 carrier omni with HCUs and air combining 12�17 . . . . . . . . .

Figure 12-13 [DCS1800] 6 or 12 carrier omni with DHUs 12�18 . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-14 [DCS1800] 2 sector 3/3 or 6/6 with DHUs 12�19 . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-15 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining 12�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-16 [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs 12�21 . . . . . . . . . . . . . . . . . . . . . .

Figure 12-17 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining 12�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-18 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and and 4 branch Rx diversity 12�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-19 4 carrier omni, duplexed hybrid and air combining 12�25 . . . . . . . . . . . . . . . . . . .

Figure 12-20 6 carrier omni, duplexed dual-stage hybrid and air combining 12�26 . . . . . . . . .

Figure 12-21 2 sector (3/3), duplexed dual-stage hybrid combining 12�27 . . . . . . . . . . . . . . . .

Figure 12-22 2 sector (6/6), duplexed dual-stage hybrid and air combining 12�28 . . . . . . . . .

Figure 12-23 3 sector (2/2/2), duplexed hybrid combining 12�29 . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-24 3 sector (4/4/4), duplexed hybrid and air combining 12�30 . . . . . . . . . . . . . . . . .

Figure 12-25 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1) 12�31

Figure 12-26 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2) 12�32

Figure 12-27 Horizoncompact2 single BTS system 12�34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-28 Horizoncompact2 two BTS system 12�35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-29 Horizoncompact2 three BTS system 12�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-30 Horizonmicro2 single BTS system 12�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-31 Horizonmicro2 two BTS system 12�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-32 Horizonmicro2 three BTS system 12�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-33 Sector 4/4 configuration with Horizon II macro and Horizonmacro cabinets 12�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-34 Sector 6/6 configuration with Horizon II macro and Horizonmacro cabinets 12�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-35 Sector 2/2/2 configuration (Horizon II macro as master cabinet) 12�43 . . . . . . .

Figure 12-36 Sector 2/2/2 configuration (Horizonmacro as master cabinet) 12�44 . . . . . . . . .

Figure 12-37 Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabinets 12�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxv

Figure 12-38 Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabinets 12�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12-39 Horizonmacro cabinet configuration using CTUs and CTU2s 12�47 . . . . . . . . .

Figure 12-40 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections 12�49 . . . .

Figure 12-41 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections 12�50 . .

Figure 13-1 Single BTS site with 6 PCUs using fibre optic links 13�5 . . . . . . . . . . . . . . . . . . .

Figure 13-2 Single BTS site with 6 PCUs using HDSL links 13�6 . . . . . . . . . . . . . . . . . . . . . .

Figure 13-3 Two BTS site with 12 PCUs using optical fibre links 13�8 . . . . . . . . . . . . . . . . . .

Figure 13-4 Two BTS site with 12 PCUs using HDSL links 13�9 . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-5 Single cabinet M-Cell6 BTS 13�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-6 Single cabinet M-Cell2 BTS 13�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-7 Two cabinet M-Cell6 BTS 13�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-8 Three cabinet M-Cell2 BTS 13�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-9 Four cabinet M-Cell6 BTS 13�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-10 3 carrier omni, hybrid combining 13�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-11 3 carrier omni, hybrid combining, medium power duplexer 13�17 . . . . . . . . . . . .

Figure 13-12 4 carrier omni, hybrid combining 13�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-13 4 carrier omni, hybrid combining, medium power duplexer 13�19 . . . . . . . . . . .

Figure 13-14 6 carrier omni, cavity combining 13�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-15 6 carrier omni, cavity combining, high power duplexer 13�21 . . . . . . . . . . . . . . .

Figure 13-16 8 carrier omni, combining 13�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-17 2 sector (3/3), hybrid combining 13�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-18 2 sector (3/3), hybrid combining, medium power duplexers 13�25 . . . . . . . . . . .

Figure 13-19 3 sector (2/2/2), combining 13�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-20 3 sector (2/2/2), combining, medium power duplexers 13�27 . . . . . . . . . . . . . . .

Figure 13-21 3 sector (4/4/4), air combining, medium power duplexers 13�28 . . . . . . . . . . . .

Figure 13-22 3 sector (4/4/4), air combining, medium power duplexers 13�29 . . . . . . . . . . . .

Figure 13-23 3 sector (4/4/4), cavity combining 13�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-24 3 sector (4/4/4), 3-input CBF, hybrid combining 13�31 . . . . . . . . . . . . . . . . . . . . .

Figure 13-25 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers 13�33 .


Figure 13-27 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers 13�35 . . . .

Figure 13-28 3 sector (6/6/6), cavity combining, high power duplexers 13�36 . . . . . . . . . . . . .


Figure 13-30 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers 13�38 . . . .

Figure 13-31 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1) 13�39 . .

Figure 13-32 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2) 13�40 . .

Figure 13-33 3 sector (8/8/8), cavity combining, high and medium power duplexers(Part 1) 13�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-34 3 sector (8/8/8), cavity combining, high and medium power duplexers(Part 2) 13�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xxvi


GMR-0168P02900W21-M

Figure 13-35 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers(Part 1) 13�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-36 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers(Part 2) 13�44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-37 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers(Part 1) 13�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-38 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers(Part 2) 13�46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-39 3 sector (2/2/2), hybrid combining 13�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-40 3 sector (2/2/2), hybrid combining, medium power duplexers 13�48 . . . . . . . . .

Figure 13-41 2 carrier, single sector, hybrid combining 13�49 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-42 2 carrier, single sector, hybrid combining, medium power duplexer 13�50 . . . .

Figure 13-43 2 sectors (1 carrier per sector) 13�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-44 2 carrier, single sector, air combining 13�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-45 2 sectors 13�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 14-1 BSS planning diagram 14�8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-1 Single BTS or ExCell site with 4 RF carriers using hybrid combining 15�36 . . . .

Figure 15-2 TopCell with 6 RF carriers using hybrid combiners 15�37 . . . . . . . . . . . . . . . . . . .

Figure 15-3 Single cabinet, one DRCU/SCU, no diversity 15�38 . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-4 Single cabinet, one DRCU/SCU, diversity 15�39 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-5 Single cabinet, 5 DRCU/SCUs, remotely tuneable or hybrid combining,no diversity 15�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-6 Single cabinet, 6 DRCU/SCUs, remotely tuneable or hybridcombining, diversity 15�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-7 Single cabinet, multiple antenna (3 sector minimum) configuration 15�44 . . . . .

Figure 15-8 Single cabinet multiple antenna configuration, diversity 15�45 . . . . . . . . . . . . . . .

Figure 15-9 Multiple cabinet, single antenna, 4 DRCU/SCUs 15�46 . . . . . . . . . . . . . . . . . . . . .

Figure 15-10 Multiple cabinet, single antenna, 10 DRCU/SCUs, remotelytuneable combiners 15�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-11 Multiple cabinet, multiple antenna (6 sector minimum) configuration 15�50 . . .

Figure 15-12 Four cabinet six sector configuration 15�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15-13 Multiple cabinet, 6 sector BTS6 (3 carriers per sector) configuration 15�53 . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxvii

List of Tables

Table 1-1 Transceiver unit usage 1�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 1-2 Acronym list 1�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-1 BSS interfaces 2�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-2 RTF types 2�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-3 Summary of required resources 2�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-4 Summary of common pool planning when BTS 1 and 2 have reservedresources 2�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-5 Summary of traffic and GOS requirements 2�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-6 Summary of common pool planning when BTSs have reserved resources 2�41 .

Table 2-7 Blocking activity 2�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-1 dBm and dBW to power conversion 3�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-2 Interleaving 3�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-3 Distribution of 456 bits from one 20 ms speech sample 3�55 . . . . . . . . . . . . . . . . .

Table 3-4 Coding parameters for GPRS coding schemes 3�61 . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-5 Frequency and parameter setting plan 3�74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-6 Typical parameters for BTS call planning 3�80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-7 Control channel configurations 3�89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-8 SDCCH planning for typical parameters (non-border location area) 3�92 . . . . . . .

Table 3-9 SDCCH planning for typical parameters (border location area) 3�93 . . . . . . . . . . .

Table 3-10 MM state model of MS 3�97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-11 Options for use_bcch_for_gprs element 3�100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-12 Switchable timeslot utilization 3�110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-13 Air interface planning inputs 3�114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-14 1 x 3 2/6 hopping 3�116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-15 1 x 1 2/18 hopping 3�116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-16 Non-hopping TU-3 model 3�116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-17 Cell coverage versus carrier to interface (C/I) 3�117 . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-18 GPRS data rates (kbit/s) with UDP 3�125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3-19 GPRS data rates (kbit/s) with TCP 3�126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-1 Transmit configurations 4�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-2 CTU/CTU2 power requirements in Horizonmacro and Horizon II macro cabinets 4�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4-3 Site connection requirements for M-Cell2 and M-Cell6 4�18 . . . . . . . . . . . . . . . . . .

Table 4-4 Horizon II macro XMUX expansion requirements 4�22 . . . . . . . . . . . . . . . . . . . . . .

Table 4-5 Horizonmacro FMUX expansion requirements 4�23 . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-1 BSC maximum capacities 5�7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-2 Typical call parameters 5�11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-3 Other parameters used in determining GPROC and link requirements 5�12 . . . .

Table 5-4 Procedure capacities (MSC � BSC) 5�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xxviii


GMR-0168P02900W21-M

Table 5-5 Procedure capacities (BSC � BTS) 5�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-6 Procedure capacities (BSC � RXCDR) 5�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-7 BTS support for 16 kbit/s RSLs 5�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-8 Number of BSC to BTS signalling links 5�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-9 Typical values for GPRS LCF GPROC2 provisioning 5�26 . . . . . . . . . . . . . . . . . . .

Table 5-10 Number of MSC and BSC signalling links (20% utilization) 5�29 . . . . . . . . . . . . .

Table 5-11 Number of MSC and BSC signalling links (40% utilization) 5�30 . . . . . . . . . . . . .

Table 5-12 Number of BSC to RXCDR signalling links 5�34 . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-13 KSWX (non-redundant) 5�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5-14 KSWX (redundant) 5�53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-1 KSWX (non-redundant) 6�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 6-2 KSWX (redundant) 6�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 7-1 BSS upgrade in support of GPRS 7�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 7-2 Maximum BSS network parameter values in support of GPRS (part A) 7�10 . . .

Table 7-3 Maximum BSS network parameter values in support of GPRS (part B) 7�11 . . .

Table 7-4 Maximum BSS network parameter values in support of GPRS (part C) 7�12 . . .

Table 7-5 PCU provisioning goals 7�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 7-6 Gb entities and identifiers 7�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 7-7 Signalling overhead per GMM signaling procedure 7�27 . . . . . . . . . . . . . . . . . . . . .

Table 7-8 Overhead on each downlink GMM/SM message 7�27 . . . . . . . . . . . . . . . . . . . . . . .

Table 7-9 PDU data transfer overhead on each downlink GMM/SM message 7�28 . . . . . . .

Table 8-1 Typical call parameters 8�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-2 Other parameters used in determining GPROC and link requirements 8�13 . . . .

Table 8-3 LCS procedure capacities 8�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-4 Number of BSC to BTS signalling links � LCS supported 8�16 . . . . . . . . . . . . . . . .

Table 8-5 Number of MSC and BSC signalling links(NSS-based LCS at 20% utilization) 8�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-6 Number of MSC and BSC signalling links(BSS-based LCS at 20% utilization) 8�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-7 Number of MSC and BSC signalling links(NSS-based LCS at 40% utilization) 8�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-8 Number of MSC and BSC signalling links(BSS-based LCS at 40% utilization) 8�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 9-1 Busy hour demand and number of carriers 9�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 9-2 Customer ordering guide 900 MHz (M-Cell6 indoor) 9�8 . . . . . . . . . . . . . . . . . . . .

Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor) 9�9 . . . . . . . . . . . . . . . . . . . .

Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor) 9�11 . . . . . . . . . . .

Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor) 9�12 . . . . . . . . . . .

Table 9-6 GPROC2s required at the BSC 9�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 9-7 BSC timeslot requirements 9�14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 9-8 Equipment required for the BSC 9�15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxix

Table 9-9 Equipment required for the RXCDR 9�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 9-10 Typical LCS call model parameters 9�42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 11-1 Typical parameters for BTS call planning 11�4 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 11-2 Sample statistics 11�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-1 Equipment required for 4 or 8 carrier omni with HCUs and air combining 12�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-2 Equipment required for 6 or 12 carrier omni with DHUs 12�18 . . . . . . . . . . . . . . . .

Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs 12�19 . . . . . . . . . . . . . . . . .

Table 12-4 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining 12�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs 12�21 . . . . . . . . . . . . . .

Table 12-6 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining 12�22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity 12�23 . . . .

Table 12-8 Equipment required for single cabinet, four CTU configuration,duplexed hybrid and air combining 12�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-9 Equipment required for single cabinet, six CTU configuration,duplexed dual-stage hybrid and air combining 12�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-10 Equipment required for single cabinet, six CTU configuration,duplexed dual-stage hybrid combining 12�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-11 Equipment required for dual cabinet, 12 CTU configuration,duplexed dual-stage hybrid and air combining 12�28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-12 Equipment required for single cabinet, six CTU configuration,duplexed hybrid combining 12�29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-13 Equipment required for dual cabinet, 12 CTU configurationduplexed hybrid and air combining 12�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 12-14 Equipment required for four cabinet, 24 CTU configuration,duplexed dual-stage hybrid and air combining 12�32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-1 Equipment required for single cabinet, 4 TCU configuration with hybridcombining and diversity 13�16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-2 Equipment required for single cabinet, 4 TCU configuration with hybridcombining, diversity and medium power duplexer 13�17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Table 13-5 Equipment required for single cabinet, 6 TCU configuration with cavitycombining and diversity 13�20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-6 Equipment required for single cabinet, 6 TCU configuration with cavitycombining, diversity and high power duplexer 13�21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-7 Equipment required for multiple cabinet, 8 TCU configuration withcombining and diversity 13�23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Table 13-9 Equipment required for single cabinet, 6 TCU configuration withcombining, diversity and medium power duplexer 13�25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-10 Equipment required for single cabinet, 6 TCU configuration withcombining and diversity 13�26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003xxx


GMR-0168P02900W21-M

Table 13-11 Equipment required for single cabinet, 6 TCU configuration withcombining, diversity and medium power duplexers 13�27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-12 Equipment required for dual cabinet, 12 TCU configuration with aircombining, diversity and medium power duplexers (3 antenna per sector) 13�28 . . . . . . . . . .

Table 13-13 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (2 antenna per sector) 13�29 . . . . . . . . . .

Table 13-14 Equipment required for multiple cabinet, 12 TCU configuration with hybridcombining and diversity 13�30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-15 Equipment required for dual cabinet, 12 TCU configuration with 3-inputCBF, hybrid combining and diversity 13�31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-16 Equipment required for multiple cabinet, 12 TCU configuration with3-input CBF, air combining, diversity and medium power duplexers 13�33 . . . . . . . . . . . . . . . .

Table 13-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-inputCBF, air combining, diversity and medium power duplexers (3 antennas/sector) 13�34 . . . . .

Table 13-18 Equipment required for 3 cabinets, 15 TCU configuration with 3-inputCBF, combining, diversity and medium power duplexers (2 antennas/sector) 13�35 . . . . . . . .

Table 13-19 Equipment required for 3 RF cabinets, 18 TCU configuration withcavity combining, diversity and high power duplexers 13�36 . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Table 13-21 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector) 13�38 . . . . . . .

Table 13-22 Equipment required for 4 RF cabinets, 24 TCU configuration with cavitycombining, diversity and medium power duplexers 13�40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-23 Equipment required for 4 RF cabinets, 24 TCU configuration with cavitycombining, diversity and both high and medium power duplexers 13�42 . . . . . . . . . . . . . . . . . .


Table 13-25 Equipment required for 4 cabinets, 24 TCU configuration with 3-inputCBF, combining, diversity and medium power duplexers (2 antennas/sector) 13�46 . . . . . . . .


Table 13-27 Equipment required for single cabinet, 6 TCU configuration with hybridcombining, diversity and medium power duplexers 13�48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Table 13-30 Equipment required for single cabinet, 2 TCU configuration withdiversity 13�51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-31 Equipment required for single cabinet, 2 TCU configuration with aircombining and diversity 13�52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 13-32 Equipment required for single cabinet, 2 TCU configuration with diversity 13�53

Table 14-1 Typical call parameters 14�9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 14-2 Other parameters used in determining GPROC and link requirements 14�10 . . .

Table 14-3 Procedure capacities 14�10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 14-4 Number of BSC to BTS signalling links 14�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 14-5 Number of MSC to BSC signalling links 14�18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01xxxi

Table 14-6 KSWX (non-redundant) 14�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 14-7 KSWX (redundant) 14�38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-1 Typical parameters for BTS call planning 15�6 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-2 Maximum number of Erlangs supported by the BTP 15�10 . . . . . . . . . . . . . . . . . . .

Table 15-3 Recommended BTP/DHP configurations and max_dris values for thefirst shelf of a BTS (3 RTFs per DHP) 15�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-4 Other shelves (3 RTFs per DHP) 15�12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-5 Recommended BTP/DHP configurations and max_dris values for the firstshelf of a BTS (3 RTFs per DHP) 15�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-6 Other shelves (3 RTFs per DHP) 15�13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-7 Number of BSC to BTS signalling links 15�24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-8 Equipment required for single cabinet, single DRCU/SCU configuration 15�38 . .

Table 15-9 Equipment required for single cabinet, single DRCU/SCU configuration withdiversity 15�39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-10 Equipment required for single cabinet, 5 DRCU/SCU configuration withremotely tuneable or hybrid combining 15�41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-11 Equipment required for single cabinet, 6 DRCU/SCU configuration withdiversity and remotely tuneable or hybrid combining 15�43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-12 Equipment required for single cabinet, multiple antenna configuration 15�44 . .

Table 15-13 Equipment required for single cabinet, multiple antenna configuration withdiversity 15�45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-14 Equipment required for multiple cabinet, single antenna 4 DRCU/SCUconfiguration 15�47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-15 Equipment required for multiple cabinet, single antenna 10 DRCU/SCUconfiguration using remotely tuneable combiners 15�49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 15-16 Equipment required for multiple cabinet, multiple antenna configuration 15�50 .

Table 15-17 Equipment required for a four cabinet, six sector configuration 15�52 . . . . . . . . .

Table 15-18 Equipment required for multiple cabinet, 6 sector BTS6 configuration 15�53 . . .

GSR6 (Horizon II)

30 Sep 2003xxxii


GMR-0168P02900W21-M

GSR6 (Horizon II) Issue status of this manual

30 Sep 2003


68P02900W21-M

GMR-011

Issue status of this manual

Introduction

The following shows the issue status of this manual since it was first released.

Version information

The following table lists the versions of this manual in order of manual issue:

Manualissue

Date ofissue

Remarks

O 03 Oct 1994 Original issue � Software release 1.2.2.x

A 30 Dec 1994 Issue A � Software release 1.2.3.x

B 01 Sep 1995 Issue B � Software release 1.3.0.x

C 31 May 1996 Issue C � Software release 1.4.0.x

D 28 Mar 1997 Issue D � (also supercedes 68P02900W31-B)

E 29 Aug 1997 Issue E � includes GSM Software Release 3

F 27 Apr 1998 Issue F � includes GSM Software Release 4

G 15 Apr 2000 Issue G � includes GSM Software Release 4.1(1.6.1.3)

H 27 Feb 2001 Issue H � includes GSM Software Release 5

J 15 Aug 2001 Issue J � includes GSM Software Release 5.1

K 15 Apr 2002 Issue K � includes GSM Software Release 6

L Not issued

M 13 Mar 2003 Issue M � includes GSM Software Release 6(Horizon II)

Resolution of Service Requests

The following Service Requests are now resolved in this manual:

ServiceRequest

GMRNumber

Remarks

N/A N/A

GSR6 (Horizon II)General information

30 Sep 20032


GMR-0168P02900W21-M

General information

Important notice

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

Purpose

Motorola cellular communications manuals are intended to instruct and assist personnelin the operation, installation and maintenance of the Motorola cellular infrastructureequipment and ancillary devices. It is recommended that all personnel engaged in suchactivities be properly trained by Motorola.

WARNING Failure to comply with Motorola�s operation, installation andmaintenance instructions may, in exceptional circumstances,lead to serious injury or death.

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

About this manual

The information in this manual will help users to:

S Identify the main effects of propagation on GSM frequencies.

S Calculate the power budget to balance a cellular system.

S Identify sources of interference.

S Understand the importance of the carrier to interference ratio.

S Determine the viable frequency re-use scheme.

S Understand the impact of microcellular equipment.

S Calculate the required number of traffic channels per cell.

S Calculate the required number of CCCHs per cell.

S Calculate the required number of SDCCHs per cell.

S Determine the hardware requirements for the Horizon II macro, Horizon andM-Cell range of equipment.

S Understand the network topology as utilized within a GSM network.

S Determine the BSC hardware requirements for a given GSM network plan.

S Determine the XCDR hardware requirements for a given GSM network plan.

S Determine the LCS requirements for a given GSM network plan.

S Produce a BSS sub-system plan for a network, given various system parameters.

GSR6 (Horizon II) General information

30 Sep 2003


68P02900W21-M

GMR-013

Feature referencesMost of the manuals in the set, of which this manual is part, are revised to accommodatefeatures released at Motorola General System Releases (GSRn) or GPRS Support Node(GSNn) releases. In these manuals, new and amended features are tagged to help usersto assess the impact on installed networks. The tags are the appropriate MotorolaRoadmap DataBase (RDB) numbers or Research and Development Prioritization (RDP)numbers. The tags include index references which are listed in the manual Index. TheIndex includes the entry feature which is followed by a list of the RDB or RDP numbersfor the released features, with page references and hot links in electronic copy.

The tags have the format: {nnnn} or {nnnnn}

Where: . is: .

. {nnnn} . the RDB number

. {nnnnn} . the RDP number

The tags are positioned in text as follows:

New and amended feature information Tag position in text

New sentence/s or new or amended text. Immediately before the affected text.

Complete new blocks of text as follows:

S Full sections under a main heading

S Full paragraphs under subheadings

Immediately after the headings as follows:

S Main heading

S Subheading

New or amended complete Figures andTables

After the Figure or Table number andbefore the title text.

Warning, Caution and Note boxes. Immediately before the affected text in thebox.

General command syntax, operator inputor displays (in special fonts).

On a separate line immediately above theaffected item.

For a list of Roadmap numbers and the RDB or RDP numbers of the features included inthis software release, refer to the manual System Information: Overview(68P02901W01), or to the manual System Information: GPRS Overview(68P02903W01).

Data encryptionIn order to avoid electronic eavesdropping, data passing between certain elements in theGSM and GPRS network is encrypted. In order to comply with the export and importrequirements of particular countries, this encryption occurs at different levels asindividually standardised, or may not be present at all in some parts of the network inwhich it is normally implemented. The manual set, of which this manual is a part, coversencryption as if fully implemented. Because the rules differ in individual countries,limitations on the encryption included in the particular software being delivered, arecovered in the Release Notes that accompany the individual software release.

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

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

GSR6 (Horizon II)General information

30 Sep 20034


GMR-0168P02900W21-M

Text conventions

The following conventions are used in the Motorola cellular infrastructure manuals torepresent 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, andenvironmental variables that appear on the screen are shown likethis.

Special key sequences

Special key sequences are represented as follows:

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

ALT�f Press the Alt and f keys at the same time.

| Press the pipe symbol key.

CR or RETURN Press the Return key.

GSR6 (Horizon II) Reporting safety issues

30 Sep 2003


68P02900W21-M

GMR-015

Reporting safety issues

Introduction

Whenever a safety issue arises, carry out the following procedure in all instances.Ensure that all site personnel are familiar with this procedure.

Procedure

Whenever a safety issue arises:

1. Make the equipment concerned safe, for example by removing power.

2. Make no further attempt to adjust or rectify the equipment.

3. Report the problem directly to the Customer Network Resolution Centre, Swindon+44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with awritten report by fax, Swindon +44 (0)1793 430987 or China +86 1068423633 (fax).

4. Collect evidence from the equipment under the guidance of the Customer NetworkResolution Centre.

GSR6 (Horizon II)Warnings and cautions

30 Sep 20036


GMR-0168P02900W21-M

Warnings and cautions

Introduction

The following describes how warnings and cautions are used in this manual and in allmanuals of this Motorola manual set.

Warnings

Definition of Warning

A warning is used to alert the reader to possible hazards that could cause loss of life,physical injury, or ill health. This includes hazards introduced during maintenance, forexample, the use of adhesives and solvents, as well as those inherent in the equipment.

Example and format

WARNING Do not look directly into fibre optic cables or data in/outconnectors. Laser radiation can come from either the data in/outconnectors or unterminated fibre optic cables connected to datain/out connectors.

Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these warnings,or with specific warnings elsewhere in the Motorola manuals, or on the equipmentitself, violates safety standards of design, manufacture and intended use of theequipment. Motorola assumes no liability for the customer�s failure to complywith these requirements.

Cautions

Definition of Caution

A caution means that there is a possibility of damage to systems, software or individualitems of equipment within a system. However, this presents no danger to personnel.

Example and format

CAUTION Do not use test equipment that is beyond its due calibration date;arrange for calibration to be carried out.

GSR6 (Horizon II) General warnings

30 Sep 2003


68P02900W21-M

GMR-017

General warnings

Introduction

Observe the following specific warnings during all phases of operation, installation andmaintenance of the equipment described in the Motorola manuals:

S Potentially hazardous voltage

S Electric shock

S RF radiation

S Laser radiation

S Heavy equipment

S Parts substitution

S Battery supplies

S Lithium batteries

Failure to comply with these warnings, or with specific warnings elsewhere in theMotorola manuals, violates safety standards of design, manufacture and intended use ofthe equipment. Motorola assumes no liability for the customer�s failure to comply withthese requirements.

Warning labels

Warnings particularly applicable to the equipment are positioned on the equipment.Personnel working with or operating Motorola equipment must comply with any warninglabels fitted to the equipment. Warning labels must not be removed, painted over orobscured in any way.

GSR6 (Horizon II)General warnings

30 Sep 20038


GMR-0168P02900W21-M

Specific warnings

Specific warnings used throughout the GSM manual set are shown below, and will beincorporated into procedures as applicable.

These must be observed by all personnel at all times when working with the equipment,as must any other warnings given in text, in the illustrations and on the equipment.

Potentially hazardous voltage

WARNING This equipment operates from a hazardous voltage of 230 Vac single phase or 415 V ac three phase supply. To achieveisolation of the equipment from the ac supply, the ac inputisolator must be set to off and locked.

When working with electrical equipment, reference must be made to the Electricity atWork Regulations 1989 (UK), or to the relevant electricity at work legislation for thecountry in which the equipment is used.

NOTE Motorola GSM equipment does not utilise high voltages.

Electric shock

WARNING Do not touch the victim with your bare hands until theelectric circuit is broken.Switch off. If this is not possible, protect yourself with dryinsulating material and pull or push the victim clear of theconductor.ALWAYS send for trained first aid or medical assistanceIMMEDIATELY.

In cases of low voltage electric shock (including public supply voltages), serious injuriesand even death, may result. Direct electrical contact can stun a casualty causingbreathing, and even the heart, to stop. It can also cause skin burns at the points of entryand exit of the current.

In the event of an electric shock it may be necessary to carry out artificial respiration.ALWAYS send for trained first aid or medical assistance IMMEDIATELY.

If the casualty is also suffering from burns, flood the affected area with cold water to cool,until trained first aid or medical assistance arrives.

RF radiation

WARNING High RF potentials and electromagnetic fields are present inthis equipment when in operation. Ensure that alltransmitters are switched off when any antenna connectionshave to be changed. Do not key transmitters connected tounterminated cavities or feeders.

Relevant standards (USA and EC), to which regard should be paid when working with RFequipment are:

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

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

GSR6 (Horizon II) General warnings

30 Sep 2003


68P02900W21-M

GMR-019

Laser radiation

WARNING Do not look directly into fibre optic cables or optical datain/out connectors. Laser radiation can come from either thedata in/out connectors or unterminated fibre optic cablesconnected to data in/out connectors.

Lifting equipment

WARNING When dismantling heavy assemblies, or removing orreplacing equipment, a competent responsible person mustensure that adequate lifting facilities are available. Whereprovided, lifting frames must be used for these operations.

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

Parts substitution

WARNING Do not install substitute parts or perform any unauthorizedmodification of equipment, because of the danger ofintroducing additional hazards. Contact Motorola if in doubtto ensure that safety features are maintained.

Battery supplies

WARNING Do not wear earth straps when working with standby batterysupplies.

Lithium batteries

WARNING Lithium batteries, if subjected to mistreatment, may burstand ignite. Defective lithium batteries must not be removedor replaced. Any boards containing defective lithiumbatteries must be returned to Motorola for repair.

Contact your local Motorola office for how to return defective lithium batteries.

GSR6 (Horizon II)General cautions

30 Sep 200310


GMR-0168P02900W21-M

General cautions

Introduction

Observe the following cautions during operation, installation and maintenance of theequipment described in the Motorola manuals. Failure to comply with these cautions orwith specific cautions elsewhere in the Motorola manuals may result in damage to theequipment. Motorola assumes no liability for the customer�s failure to comply with theserequirements.

Caution labels

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

Specific cautions

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

Fibre optics

CAUTION Fibre optic cables must not be bent in a radius of less than30 mm.

Static discharge

CAUTION Motorola equipment contains CMOS devices. These metaloxide semiconductor (MOS) devices are susceptible todamage from electrostatic charge. See the section Devicessensitve to static in the preface of this manual for furtherinformation.

GSR6 (Horizon II) Devices sensitive to static

30 Sep 2003


68P02900W21-M

GMR-0111

Devices sensitive to static

Introduction

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

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

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

Special handling techniques

In the event of one of these devices having to be replaced, observe the followingprecautions when handling the replacement:

S Always wear an earth strap which must be connected to the electrostatic point(ESP) on the equipment.

S Leave the short circuit on the leads until the last moment. It may be necessary toreplace the conductive foam by a piece of wire to enable the device to be fitted.

S Do not wear outer clothing made of nylon or similar man made material. A cottonoverall is preferable.

S If possible work on an earthed metal surface or anti-static mat. Wipe insulatedplastic work surfaces with an anti-static cloth before starting the operation.

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

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

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

GSR6 (Horizon II)Motorola manual sets

30 Sep 200312


GMR-0168P02900W21-M

Motorola manual sets

Introduction

The following manuals provide the information needed to operate, install and maintain theMotorola equipment. CD-ROMs are available, with full navigation, for GSM, and GPRSmanual sets.Each CD-ROM includes all manuals related to a specified main GSM or GPRS softwarerelease, together with current versions of appropriate hardware manuals. A snapshotcopy of online documentation is also included, though it will not be updated in line withsubsequent point releases.The CD-ROM does not include Release Notes or documentation supporting specialistproducts such as MARS or COP.

Printed hard copy

Electronic, as fully navigable PDF files on:

S On the Motorola service web.

(https://mynetworksupport.motorola.com/index.asp).

S CD-ROM library produced in support of a major system software release.

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

The CD-ROM does not include Release Notes or documentation supportingspecialist products such as MARS or COP.

Ordering manuals

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

All orders for Motorola manuals must be placed with your Motorola Local Office orRepresentative. Manuals are ordered using the order (catalogue) number.

GSR6 (Horizon II) GMR amendment

30 Sep 2003


68P02900W21-M

GMR-0113

GMR amendment

Introduction to GMRs

Changes to a manual that occur after the printing date are incorporated into the manualusing General Manual Revisions (GMRs). GMRs are issued to correct Motorola manualsas and when required. A GMR has the same identity as the target manual. Each GMR isidentified by a number in a sequence that starts at 01 for each manual at each issue.

GMR availability

GMRs are published as follows:

S Printed hard copy - Complete replacement content or loose leaf pages withamendment list.

� Remove and replace pages in this manual, as detailed on the GMRinstruction sheet.

S Motorola service web - Updated at the same time as hard copies.

S CD-ROM - Updated periodically as required.

GSR6 (Horizon II)GMR amendment record

30 Sep 200314


GMR-0168P02900W21-M

GMR amendment record

GMR instructions

When a GMR is inserted in this manual, the amendment record below is completed torecord the GMR. Retain the instruction sheet that accompanies each GMR and insert itin a suitable place in this manual for future reference.

Amendment record

Record the insertion of GMRs in this manual in the following table:

GMR number Incorporated by (signature) Date

01 Incorporated (this GMR) 30 Sep 2003

02 . .

03 . .

04 . .

05 . .

06 . .

07 . .

08 . .

09 . .

10 . .

11 . .

12 . .

13 . .

14 . .

15 . .

16 . .

17 . .

18 . .

19 . .

20 . .

21 . .

22 . .

23 . .

24 . .

25 . .

30 Sep 2003


68P02900W21-M

GMR-011�1

Chapter 1

Introduction to planning

GSR6 (Horizon II)

30 Sep 20031�2


GMR-0168P02900W21-M

GSR6 (Horizon II) Chapter overview

30 Sep 2003


68P02900W21-M

GMR-011�3

Chapter overview

Introduction to BSS planning

This chapter provides an overview of this manual and the various elements of a BSS andthe BSS planning methodology. This chapter contains:

S Manual overview.

S BSS equipment overview.

� An overview of the BSS system architecture.

� An overview of the BSS system components.

S BSS features.

� A description of those BSS features that can affect BSS planning.

S BSS planning overview.

� A list of the information required before planning can begin.

� An overview of the BSS planning methodology.

S List of acronyms.

NOTE OMC-R planning is beyond the scope of this manual.For information on installing a new GSR6 (Horizon II) OMC-R,refer to 68P02901W47, Installation and Configuration: OMC-RClean Install. For information on upgrading an existing GSR5OMC-R to GSR6 (Horizon II) , refer to 68P02901W74, SoftwareRelease Notes: OMC-R System.There is no direct hardware or software upgrade path fromGSR4/GSR4.1 to GSR6 (Horizon II) . If this is required, GSR5must be installed first.

GSR6 (Horizon II)Manual overview

30 Sep 20031�4


GMR-0168P02900W21-M

Manual overview

Introduction

The manual contains information about planning a GSM network; utilizing a combinationof Horizon and M-Cell BTS equipment.

Contents

The manual contains the following chapters:

S Chapter 1: Introduction

Provides an overview of the various elements of a BSS and the BSS planningmethodology.

S Chapter 2: Transmission systems

This chapter provides an overview of the transmission systems used in GSM.

S Chapter 3: BSS cell planning

States the requirements and procedures used in producing a BSS cell site plan.

S Chapter 4: BTS planning steps and rules

Provides the planning steps and rules for the BTS, covering the Horizon andM-Cell range of equipments.

S Chapter 5: BSC planning steps and rules

Provides the planning steps and rules for the BSC.

S Chapter 6: RXCDR planning steps and rules

Provides the planning steps and rules for the RXCDR.

S Chapter 7: PCU upgrade for the BSS.

Provides information for the PCU upgrade to the BSS.

S Chapter 8: BSC planning steps and rules for LCS

Provides the planning steps and rules for the BSC when supporting locationservices.

S Chapter 9: Planning exercise

Provides a planning exercise designed to illustrate the use of the rules andformulae provided in Chapter 3, 4, 5, 6 7 and 8.

S Chapter 10: Location area planning

Provides the planning steps and rules for location area planning.

S Chapter 11: Deriving call model parameters from network statistics

Provides the planning steps and rules for deriving call model parameters fromnetwork statistics collected at the OMC-R.

GSR6 (Horizon II) Manual overview

30 Sep 2003


68P02900W21-M

GMR-011�5

S Chapter 12: Standard BSS and Horizon BTS configurations

Provides diagrams of the logical interconnections of the components in variousstandard BSS and Horizon BTS site configurations.

S Chapter 13: M-Cell BTS configurations

Provides diagrams of the logical interconnections of the components in variousM-Cell BTS site configurations.

S Chapter 14: Previous generation BSC planning steps and rules

This chapter (included for reference only) provides the planning steps and rulesfor the BSC up to software release GSR3.

S Chapter 15: Planning and equipment descriptions for pre M-Cell BTSs

This chapter (included for reference only) provides the planning steps and rulesfor pre M-Cell BTS equipment.

NOTE Chapters 14 and 15 are included only for reference purposesand will not be updated in current or future releases of thismanual.

GSR6 (Horizon II)BSS equipment overview

30 Sep 20031�6


GMR-0168P02900W21-M

BSS equipment overview

System architecture

The architecture of the Motorola Base Station System (BSS) is extremely versatile, andallows many possible configurations for a given system. The BSS is a combination ofdigital and RF equipment that communicates with the Mobile Switching Centre (MSC),the Operations and Maintenance Centre Radio (OMC-R), and the Mobile Stations (MS)as shown in Figure 1-1.

Figure 1-1 BSS block diagram

BSC

BTS 1 BTS 5 BTS n

BSS

. . .

MSCLRs

OMC-RA INTERFACE

O & M

MS . . .

AIR INTERFACE

ABIS INTERFACE

BTS 8

BTS 2

BTS 3

BTS 4

BTS 6

BTS 7

BSSRXCDR

. . .

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.

PCU

MS MS MS

GSR6 (Horizon II) BSS equipment overview

30 Sep 2003


68P02900W21-M

GMR-011�7

System components

The BSS can be divided into a Base Station Controller (BSC), and one or more BaseTransceiver Stations (BTSs). These can be in-building or externally located Horizon,M-Cell, ExCell, or TopCell BTS cabinets or enclosures.

The Transcoder (XCDR) or Generic Digital Processor (GDP) provides 4:1 multiplexing ofthe traffic and can be located at the BSC or between the BSC and MSC. When theXCDR/GDP is located at the MSC it reduces the number of communication links to theBSC. When transcoding is not performed at the BSC, the XCDR is referred to as aremote transcoder (RXCDR). The RXCDR is part of the BSS but may serve more thanone BSS.

Transceiver units

In the Motorola BTS product line, the radio transmit and receive functions are providedas listed in Table 1-1:

Table 1-1 Transceiver unit usage

Transceiver unit Where used ...

Compact Transceiver Unit 2 (CTU2) Horizon II macro, Horizonmacro (withlimitations � see CTU2 below)

Compact Transceiver Unit (CTU) Horizonmacro

Dual Transceiver Module (DTRX) Horizonmicro, Horizonmicro2,Horizoncompact and Horizoncompact2

Transceiver Control Unit (TCU) M-Cell6, M-Cell2, BTS6

Transceiver Control Unit (TCU-B) M-Cell6, M-Cell2

Transceiver Control Unit, micro (TCU-m) M-Cellmicro, M-Cellcity and M-Cellcity+

Picocell Control Unit (PCU) M-Cellaccess

Diversity Radio Channel Unit (DRCU) BTS4, BTS5, BTS6, TopCell, ExCell

Slim Channel Unit (SCU) BTS4, BTS5, BTS6, TopCell, ExCell

NOTE With the exception of the TCU, which is backwards compatibleby switching from TCU to SCU on the front panel, all othertransceiver units are only compatible with the equipment listed.

GSR6 (Horizon II)BSS equipment overview

30 Sep 20031�8


GMR-0168P02900W21-M

CTU2

In Horizon II macro, the transceiver functions are provided by the CTU2, which can beconfigured to operate in single or double density mode.

This CTU2 can also be used by Horizonmacro as a CTU replacement with restrictions(see note below). Depending on the number of CTU/CTU2s in the Horizonmacro cabinet,there are output power restrictions that may require a mandatory 3rd power supplyinstalled in the Horizonmacro cabinet. This may impact the battery hold-up module inac-powered cabinets, as the location for the 3rd power supply may mean the batteryhold-up module may have to be removed, and an external battery backup unit added. Inthe case where three power supplies are required, there will be no available slots for theredundant power supply.

Description and planning rules for the CTU2 are provided in Chapter 4 of this manual.Configuration diagrams are shown in Chapter 12. The receivers can support receivediversity.

NOTE CTU2s do not support the use of CCBs. A CTU2 cannot be CCBequipped and will not act as a full replacement/swap for theCTU. The CTU2 will only act as a CTU replacement in thenon-controller/standby controller mode. Refer to the Motorolaon-line ordering guide for details.When installed in Horizonmacro, the CTU2 only supportsbaseband hopping in single density mode.

CTU

In Horizonmacro, the transceiver functions are provided by the CTU. Description andplanning rules for the CTU are provided in Chapter 4 of this manual. Configurationdiagrams are shown in Chapter 12. The receivers can support receive diversity.

DTRX

In Horizonmicro, Horizonmicro2, Horizoncompact and Horizoncompact2, the transceiverfunctions are provided by the dual transceiver module (DTRX). System planning isdescribed in Chapter 2 and configuration diagrams are shown in Chapter 12. Thereceivers do not support receive diversity.

TCU/TCU-B

In M-Cell6, M-Cell2 and BTS6, the transceiver functions are provided by the TCU orTCU-B (not BTS6). Description and planning rules for the TCU/TCU-B are provided inChapter 4 of this manual. Configuration diagrams are shown in Chapter 13. Thereceivers can support receive diversity.

TCU-m

In M-Cellmicro, M-Cellcity and M-Cellcity+ the transceiver functions are provided by apair of TCU-ms. The receivers do not support receive diversity.

GSR6 (Horizon II) BSS equipment overview

30 Sep 2003


68P02900W21-M

GMR-011�9

PCU

In M-Cellaccess, the transceiver functions are provided by the PCU. System planning isdescribed in Chapter 2 and configuration diagrams are shown in Chapter 13. Thereceivers can support receive diversity.

NOTE Do not confuse the PCU in M-Cellaccess with the PCU (PacketControl Unit) hardware that is required for GPRS support.

DRCU/SCU

In BTS4, BTS5, BTS6, TopCell and ExCell, the the transceiver functions are provided bythe DRCU/SCU. Planning rules for the DRCU and SCU are provided in Chapter 14 andconfiguration diagrams are shown in Chapter 15. The receivers can support receivediversity.

GSR6 (Horizon II)BSS features

30 Sep 20031�10


GMR-0168P02900W21-M

BSS features

Features that affect planning

This section provides a description of the software features that might affect the requiredequipment, and that should be taken into consideration before planning actualequipment. Check with the appropriate Motorola sales office regarding softwareavailability with respect to these features.

S Diversity.

S Frequency hopping.

S Short message, cell broadcast.

S Code storage facility processor.

S Packet Control Unit (PCU) for General Packet Data Service (GPRS) upgrade.

Diversity

Diversity reception (spatial diversity) at the BTS is obtained by supplying twouncorrelated receive signals to the transceiver. Each transceiver unit includes tworeceivers, which independently process the two received signals and combine the resultsto produce an output. This results in improved receiver performance when multipathpropagation 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 thenecessary de-correlation.

Frequency hopping

There are two methods of providing frequency hopping: synthesizer hopping andbaseband hopping. Each method has different hardware requirements.

The main differences are:

S Synthesizer hopping requires the use of wideband (hybrid) combiners for transmitcombining, while baseband hopping does not.

S Baseband hopping requires the use of one transceiver for each allocatedfrequency, while synthesizer hopping does not.

GSR6 (Horizon II) BSS features

30 Sep 2003


68P02900W21-M

GMR-011�11

Synthesizer hopping

Synthesizer hopping uses the frequency agility of the transceiver to change frequencieson a timeslot basis for both receive and transmit. The transceiver calculates the nextfrequency and re-programs its synthesizer to move to the new frequency. There are threeimportant points to note when using this method of providing frequency hopping:

S Hybrid combining must be used; cavity combining is not allowed when usingsynthesizer hopping.

S The output power available with the use of the hybrid combiners must beconsistent with coverage requirements.

S It is only necessary to provide as many transceivers as required by the traffic. Notethat one transceiver in each sector must be on a fixed frequency to provide theBCCH carrier.

Baseband hopping

For baseband hopping each transceiver operates on preset frequencies in the transmitdirection. Baseband signals for a particular call are switched to a different transceiver ateach TDM frame in order to achieve frequency hopping. There are three important pointsto note when using this method of providing frequency hopping:

S The number of transceivers must be equal to the number of transmit (or receive)frequencies required.

S Use of either remote tuning combiners or hybrid combiners is acceptable.

S Frequency redefinition procedures were incomplete in the Phase 1 GSMspecifications; this is addressed in the Phase 2 GSM procedures, but at this timethere are no Phase 2 MSs capable of implementing this. Consequently, calls couldbe dropped, if a single transceiver fails, due to the inability to inform the MSs.

Short message service, cell broadcast

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

Code storage facility processor

Beginning with software release 1.3.0.0, the BSS supports a GPROC acting as the CodeStorage Facility Processor (CSFP). The CSFP allows pre-loading of a new softwarerelease while the BSS is operational. When BTSs are connected to the BSC, a CSFP isrequired at the BSC and a second CSFP should be equipped for redundancy as required.

NOTE If GPROC2 is used this feature will not require additionalhardware.

GSR6 (Horizon II)BSS features

30 Sep 20031�12


GMR-0168P02900W21-M

PCU for GPRS upgrade

The PCU hardware provides GPRS functionality, and is considered as part of the BSSequipment.

GPRS introduced packet data services (from GSR4.1 onwards) and GPRS planning isfundamentally different from the planning of circuit-switched networks. One of thefundamental reasons for the difference, is that a GPRS network allows the queueing ofdata traffic instead of blocking a call when a circuit is unavailable. Consequently, the useof Erlang B tables for estimating the number of trunks or timeslots required, is not a validplanning approach for the GPRS packet data provisioning process.

GSR6 (Horizon II) BSS planning overview

30 Sep 2003


68P02900W21-M

GMR-011�13

BSS planning overview

Introduction

A brief overview of the planning process is provided in this section.

Initial information required

The information required before planning can begin can be categorized into three mainareas:

S Traffic model and capacity calculations.

S Category of service.

S Site planning.

Traffic model and capacity calculations

The following information is required to calculate the capacity required:

S Traffic information (Erlangs/BTS) over desired service area.

S Average traffic per site.

S Call duration.

S Number of handovers per call.

S Ratio of location updates to calls.

S Ratio of total pages sent to time in seconds (pages per second).

S Ratio of intra-BSC handovers to all handovers.

S Number of TCHs.

S Ratio of SDCCHs to TCHs.

S Link utilization (for C7 MSC to BSS links).

S SMS utilization (both cell broadcast and point to point).

S Expected (applied and effective) GPRS load.

GSR6 (Horizon II)BSS planning overview

30 Sep 20031�14


GMR-0168P02900W21-M

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:

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

S Grade of service of the trunks between MSC/BSC, typically Erlang B at 1%.

S Grade of service of the traffic channels (TCH) between MS and BTS, typicallyErlang B at 2%.

S 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 Where the BSC and BTSs will be located.

S Local restrictions affecting antenna heights, equipment shelters, and so on.

S Number of sites required (RF planning issues).

S Re-use plan (frequency planning) omni or sector:

� Spectrum availability.

� Number of RF carrier frequencies available.

� Antenna type(s) and gain specification.

S Diversity requirement. Diversity doubles the number of Rx antennas andassociated equipment.

S Redundancy level requirements, determined for each item.

S Supply voltage.

GSR6 (Horizon II) BSS planning overview

30 Sep 2003


68P02900W21-M

GMR-011�15

Planning methodology

A GSM digital cellular system is usually made up of several BSSs. The planning cyclebegins with defining the BSS cell, followed by the BTS(s), then the BSC(s), and finallythe RXCDR(s).

The text that follows provides a brief checklist of the steps in planning a BSS:

1. Choose the configuration, omni or sectored and the frequency re-use scheme thatsatisfies traffic, interference and growth requirements.

2. Plan all BTS sites first:

� Use an appropriate RF planning tool to determine the geographical locationof sites on and the RF parameters of the chosen terrain.

� Determine which equipment affecting features are required at each site. Forexample, diversity or frequency hopping.

� Plan the RF equipment portion and cabinets for each BTS site.

� Plan the digital equipment portion for each BTS site.

3. 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, subsequenthardware implementation.

GSR6 (Horizon II)Acronyms

30 Sep 20031�16


GMR-0168P02900W21-M

Acronyms

Acronym listTable 1-2 contains a list of acronyms as used in this manual.

Table 1-2 Acronym list

Acronym Meaning

AGCH Access grant channel

A-GPS Assisted GPS

ARFCN Absolute radio frequency channel number

ARQ Automatic repeat request

ATB All trunks busy

BBBX Battery backup board

BBH Baseband hopping

BCCH Broadcast control channel

BCROH BTS concentration resource optimization for handovers

BCS Block check sequence

BCU Base controller unit

BER Bit error rate

BHCA Busy hour call attempts

BIB Balanced line interface board

BLER Block error rate

BSC Base station controller

BSP Base station processor

BSS Base station system

BSSC(2) Base station system control (2)

BSU Base station unit

BTC Bus termination card

BTF Base transceiver function

BTP Base transceiver processor

BTS Base transceiver station

BVC(I) BSSGP virtual circuit (identifier)

C/I Carrier to interference ratio

CBC Cell broadcast centre

CBF Combining bandpass filter

CBL Cell broadcast centre link

CCB Cavity combining block

CCCH Common control channel

CDMA Code division multiple access

GSR6 (Horizon II) Acronyms

30 Sep 2003


68P02900W21-M

GMR-011�17

Acronym Meaning

CIC Circuit identity code

CIR Committed information rate

CLKX Clock extender

CN Core network

CP Call processing

cPCI Compact PCI

CPU Central processing unit

CRC Cyclic redundancy check

CS(n) Channel coding scheme (number)

CSFP Code storage facility processor

CTU Compact transceiver unit

CTU2 Compact transceiver unit 2

DARBC Dynamic allocation of RXCDR to BSC circuits

dB Decibel

DCF Duplexed combining bandpass filter

DDF Dual stage duplexed combining filter

DCS Digital cellular system

DECT Digital enhanced cordless telephony

DHU Dual hybrid combiner unit

DL Downlink

DLCI Data link connection identifier

DLNB Dual low noise block

DPROC Data processor

(D)RAM (Dynamic) random access memory

DRCU Diversity radio control unit

DRI Digital radio interface

DRIM Digital radio interface module

DRX Discontinuous reception

DSP Digital signal processor

DTE Data terminal equipment

DTRX Dual transceiver module

DTX Discontinuous transmission

DUP Duplexer

DYNET Dynamic network

e Erlang

E1 32 channel 2.048 Mbps span line

EFR Enhanced full rate


30 Sep 20031�18


GMR-0168P02900W21-M

Acronym Meaning

(E)GSM (Enhanced) global system for mobile communication

E-OTD Enhanced observed time difference

FACCH Fast access control channel

FEC Forward error correction

FHI Frequency hopping index

FM Fault management

FMUX Fibre optic multiplexer (Horizonmacro)

FN Frame number

FOX Fibre optic multiplexer (M-Cell)

FR Frame relay

FTD File transit delay

FTP File transfer protocol

GBL (or GbL) Gb link

GCLK Generic clock

GDP Generic digital processor

GDS GPRS data stream

GGSN Gateway GPRS support node

GMLC Gateway mobile location centre

GMM GPRS mobility management

GMSK Gaussian minimum shift keying

GOS Grade of service

GPROC(2) Generic processor (2)

GPRS General packet radio system

GPS Global positioning by satellite

GSN GPRS support node

GSR GSM software release

HCOMB Hybrid combiner

HCU Hybrid combining unit

HDLC High level data link control

HDSL High bit rate digital subscriber line

HIISC Horizon II macro site controller

HSC Hot swap controller

HSN Hopping sequence number

IADU Integrated antenna distribution unit

IMSI International mobile subscriber identity

INS In service

IP Internet protocol


30 Sep 2003


68P02900W21-M

GMR-011�19

Acronym Meaning

IPL Initial program load

ISDN Integrated services digital network

ISI Inter symbol interference

ISP Internet service provider

KSW(X) Kiloport switch (extender)

LAC Location area code

LAN(X) Local area network (extender)

LAPB Link access protocol balanced

LAPD Link access protocol data

LCF Link control function

LCS Location services

LLC Logical link control

LMTL Location service MTL

LMU Location measurement unit

LNA Low noise amplifier

MA(IO) Mobile allocation (index offset)

MAC Medium access control

MAP Mobile application part

MBR Maximum bit rate

MCAP Motorola cellular advanced processor bus

MCU Main control unit

MCUF Main control unit with dual FMUX

MIB Management information base

MLC Mobile location centre

MMI Man machine interface

MPROC Master processor

MS Mobile station

MSC Mobile switching centre

MSI(-2) Multiple serial interface (2)

MTL MTP transport layer link

MTP Message transfer part

NE Network element

NIU Network interface unit

NSE(I) Network service entity (identifier)

NSP Network support program

NSS Network subsystem

NSVC(I) Network service layer virtual circuit (identifier)


30 Sep 20031�20


GMR-0168P02900W21-M

Acronym Meaning

NTP Network time protocol

NVM Non volatile memory

O&M Operations and maintenance

OLM Off line MIB

OMC-R Operations and maintenance centre � radio

OMF Operations and maintenance function

OML Operations and maintenance link

OOS Out of service

PACCH Packet associated control channel

PAGCH Packet access grant channel

PBCCH Packet broadcast control channel

PCC Picocell cluster controller

PCCCH Packet common control channel

PCH Paging channel

PCI Peripheral component interconnect

PCM Pulse code modulation

PCMCIA Personal computer memory card international association

PCR Preventive cyclic retransmission

PCS Personal communication system

PCU Packet control unit or Picocell control unit (M-Cellaccess)

PDCCH Packet dedicated control channel

PDCH Packet data channel

PDN Packet data network

PDP Packet data protocol

PDTCH Packet data traffic channel

PDU Protocol data unit

PICP Packet interface control processor

PIX Parallel interface extender

PLMN Public land mobile network

PMC PCI mezzanine card

PNCH Packet notification channel

PPCH Packet paging channel

PPP Point to point protocol

PRACH Packet random access channel

PSM Power supply module

PSTN Public switched telephone network

PSU Power supply unit


30 Sep 2003


68P02900W21-M

GMR-011�21

Acronym Meaning

PTCCH/D Packet timing advance control channel / downlink

PTCCH/U Packet timing advance control channel / uplink

PTP Point to point

PVC Permanent virtual circuit

QOS (or QoS) Quality of service

RACH Random access channel

RAM Random access memory

RAN Radio access network

RAT Radio access technology

RAU Routeing area update

RDB Requirements database

RF Radio frequency

RLC Radio link control

ROM Read only memory

RRI Radio refractive index

RSL Radio signalling link

RTD RLC transit delay

RTF Radio transceiver function

RX (or Rx) Receive

RXCDR Remote transcoder

RXU Remote transcoder unit

SACCH Slow access control channel

SCC Serial channel controller

SCCP SS7 signalling connection control part

SCH Synchronization channel

SCM Status control manager

SCU Slim channel unit

SDCCH Stand alone dedicated control channel

SFH Synthesizer frequency hopping

SGSN Serving GPRS support node

SID Silence descriptor

SLS Signalling link selection

SM Session management

SMLC Serving MLC

SMS Short message service

SNDCP Sub network dependent convergence protocol

SS7 CCITT signalling system number 7


30 Sep 20031�22


GMR-0168P02900W21-M

Acronym Meaning

STP Shielded twisted pair

SURF Sectorized universal receiver front end (Horizonmacro)

SURF2 Sectorized universal receiver front end 2 (Horizon II macro)

TBF Temporary block flow

TCCH Timing access control channel

TCH Traffic channel

TCP Transmission control protocol

TCU Transceiver control unit

TDM Time division multiplexing

TDMA Time division multiple access

TMSI Temporary mobile subscriber identity

TOA Time of arrival

TRAU Transcoder rate adaptation unit

TS Timeslot

TSW Timeslot switch

TX (or Tx) Transmit

UE User equipment

UL Uplink

UMTS Universal mobile telecommunication system

USF Uplink state flag

UTP Unshielded twisted pair

UTRAN UMTS radio access network

VAD Voice activity detection

WAN Wide area network

WAP Wireless access protocol

XBL Transcoder to BSS link

XCDR Transcoder board

XMUX Expansion multiplexer (Horizon II macro)

30 Sep 2003


68P02900W21-M

GMR-012�1

Chapter 2

Transmission systems

GSR6 (Horizon II)

30 Sep 20032�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-012�3

Chapter overview

Introduction

This chapter provides diagrams of the logical interconnections and descriptions of BSSinterconnections.

This chapter contains:

S BSS interfaces.

S BSC to BTS interconnection rules.

S Network topology:

� Star connection.

� Daisy chain connection.

� Aggregate Abis.

� 16 kbit/s RSL.

� 16 kbit/s XBL.

� Dynamic Allocation of RXCDR to BSC Circuits (DARBC).

S BTS concentration.

S Managed HDSL on micro BTS:

� Integrated HDSL interface.

� Microcell system planning.

� Picocell system planning.

GSR6 (Horizon II)BSS interfaces

30 Sep 20032�4


GMR-0168P02900W21-M

BSS interfaces

Introduction

Figure 2-1 and Table 2-1 indicate the type of interface, rate(s) and transmission systemsused to convey information around the various parts of the BSS system.

Figure 2-1 BSS interfaces

BTS BSC RXCDR

CBC

OMC-R

MS

MSC

Abis interface A interfaceAir interface

X.25(LAPB)

X.25(LAPB)OML

CBL

MTL (C7), XBL (LAPD)OML (X.25)

RSL (LAPD)(LAPDm)

PCU

GDS

Gb OPTION C

Gb OPTION B

SGSN

Gb OPTION A

Table 2-1 BSS interfaces

Interface From/To Signalling by ... Rate Using ...

Air MS � BTS RACH, SDCCH,SACCH, FACCH

LAPDm

E1/T1 links

Abis (Mobis) BTS � BSC RSL 16/64 kbit/s LAPD

A BSS � MSC MTL (OML, CBL) 64 kbit/s C7

A RXCDR � BSC XBL 16/64 kbit/s LAPD

MSC � OMC-R OML (X.25) 64 kbit/s LAPB

MSC � CBC CBL (X.25) 64 kbit/s LAPB

Gb PCU � SGSN GBL E1 FrameRelay

GDS PCU � BSC GSL 64 kbits/s LAPD

GSR6 (Horizon II) Interconnecting the BSC and BTSs

30 Sep 2003


68P02900W21-M

GMR-012�5

Interconnecting the BSC and BTSs

Introduction

Network topology is specified in terms of the path(s) between the BSC and the BTSsites. A path is determined by which E1 or T1 circuits, and possible intervening BTS sitesare used to provide the connection. Transcoding may be carried out at the BSC orRXCDR.

Interconnection rules

The following rules must be observed when interconnecting a BSC and BTSs:

S The BSC may share MSI boards between BTSs. When there are two or more E1or T1 circuits, at least two MSIs are recommended for redundancy.

S A minimum of one MSI is required at each BTS.

S There is a maximum of 8, and minimum of 1, signalling links per BTS6 site, eachrequiring one 64 kbit/s timeslot on a E1 or T1 circuit.

S The maximum number of carrier units is determined by available E1 or T1 circuitcapacity. A carrier unit will require two 64 kbit/s timeslots on a E1 or T1 circuit. In aredundant connection, each carrier unit requires two 64 kbit/s timeslots on twodifferent E1 or T1 circuits.

S At the BSC, one E1 or T1 circuit is required to connect to a daisy chain. If theconnection is a closed loop daisy chain, two E1 or T1 circuits are required. Toprovide redundancy, the two E1 or T1 circuits should be terminated on differentMSIs.

S In a closed loop daisy chain the primary RSLs for all BTS sites should be routed inthe same direction with the secondary RSLs routed in the opposite direction. Theprimary RSL at each BTS site in the daisy chain should always be equipped on themultiple serial interface link (MMS) equipped in CAGE 15 slot 16 port A. Thesecondary RSL at each BTS site should be equipped on the MMS equipped ineither cage 15 slot 16 port B or cage 15 slot 14 port A or cage 14 slot 16 port A.

NOTE When discussing the BSC or RXCDR, �cage� is a legacy termused in BSS commands that has been replaced by �shelf� in thismanual. i.e. Cage and shelf mean the same thing.

S Additional bandwidth is required to support GPRS traffic using CS3/CS4 codingschemes (CS3 and CS4 require GSR5.1 or higher). Each timeslot, on a CS3/CS4capable carrier, will require 32 kbit/s for a total of four 64 kbit/s timeslots on the E1or T1 circuit, irrespective of the speech coding.

The following rules must be observed when interconnecting InCell and M-Cell equipment:

S Reconfigure the InCell BTS to have integral sector(s) in the cabinet.

S Install M-Cell cabinet(s) to serve the remaining sector(s).

S Daisy chain the M-Cell E1/T1 links to the BSC.

GSR6 (Horizon II)Network topology

30 Sep 20032�6


GMR-0168P02900W21-M

Network topology

IntroductionThe user can specify what traffic is to use a specific path. Any direct route between anytwo adjacent sites in a network may consist of one or more E1 or T1 circuits. Figure 2-2shows a possible network topology.

Figure 2-2 Possible network topology

BSC

BTS 2

BTS 3

BTS 4

BTS 10

BTS 11

BTS 5

BTS 6

BTS 7 BTS 9

BTS 8

BTS 1

Each BTS site in the network must obey the following maximum restrictions:

S Six serial interfaces supported at a Horizon II macro BTS.

S Six serial interfaces supported at a Horizonmacro BTS.

S Two serial interfaces supported at a Horizonmicro2 / Horizoncompact2 BTS.

S Six serial interfaces supported at an M-Cell6 BTS.

S Four serial interfaces supported at an M-Cell2 BTS.

S Two serial interfaces supported at an M-Cellcity / M-Cellcity+ BTS.

S Six serial interfaces supported at an M-Cellaccess BTS.

S Ten serial interfaces supported at a BTS6.

S Ten BTS(s) in a path, including the terminating BTS for E1 circuit connection oreight BTS(s) in a path, including the terminating BTS for T1 circuit connection.

S One RSL signalling link per Horizon II macro or Horizonmacro BTS site.

S Four RSL signalling links per M-Cell BTS site (maximum of two per path).

S Eight signalling links per BTS6 site.

An alternative path may be reserved for voice/data traffic in the case of path failure. Thisis known as a redundant path, and is used to provide voice/data redundancy, that is loopredundancy. The presence of multiple paths does not imply redundancy.

Each signalling link has a single path. When redundant paths exist, redundant signal linksare required, and the signalling is load shared over these links. In the case of a pathfailure, the traffic may be rerouted, but the signalling link(s) go out of service, and theload is carried on the redundant link(s).

GSR6 (Horizon II) Network topology

30 Sep 2003


68P02900W21-M

GMR-012�7

Star connection

A star connection is defined by installing E1 or T1 circuits between each BTS site and theBSC, as shown in Figure 2-3.

Figure 2-3 Star connection

BTS 1

BTS 2BTS 3

BTS 4

BTS 5

BTS 9

BTS 7

BTS 8

MSC

BSC

A star connection may require more MSI cards at the BSC than daisy chaining for thesame number of BTS sites. The star connection will allow for a greater number of carrierunits per BTS site.

An E1 circuit provides for 15 carriers plus one signalling link. A T1 circuit provides for 11carriers plus 1 or 2 signalling links.


30 Sep 20032�8


GMR-0168P02900W21-M

Daisy chain connection

Daisy chaining multiple BTS sites together can better utilize the 64 kbit/s timeslots of oneE1 or T1 circuit from the BSC. Daisy chaining the sites together provides for the efficientutilization of the E1 or T1 circuit for interconnecting smaller sites back to the BSC.

The daisy chain may be open ended or closed looped back to the BSC as shown in Figure 2-4.

Figure 2-4 Closed loop and open ended daisy chains

BTS 1

BTS 2

BTS 3

BTS 4

BTS 5

BTS 9BTS 7

BTS 8

MSC

BSC

BTS 10

BTS 6

BTS 11

BRANCH OF THEDAISY CHAIN

DAISY CHAINCLOSED LOOP

DAISY CHAINCLOSED LOOP

SINGLE MEMBERDAISY CHAIN, A STAR

The closed loop version provides for redundancy while the open ended does not. Notethat longer daisy chains (five or more sites) may not meet the suggested round trip delay.


30 Sep 2003


68P02900W21-M

GMR-012�9

Daisy chain planning

The introduction of multiple E1 or T1 circuits and branches increases the complexity ofthe network topology. Since the network can have multiple E1 or T1 circuits, branches,multiple paths over the same E1 or T1 circuit, and closed loop interconnections, each E1or T1 circuit should be individually planned.

Simple daisy chain

A daisy chain with no branches and a single E1 or T1 circuit between each of the BTSs isreferred to as a simple daisy chain. The maximum capacity supported in this connectionis limited by the capacity of the connection between the BSC and the first BTS in thechain. A simple daisy chain is shown in Figure 2-5.

Figure 2-5 Simple daisy chain

......... ...

BSC BTS 1 BTS 2

BTS 3 BTS 4

RxTx

Rx

Tx Rx

Tx

RxTx

TxRx TxRxRx

Tx

TxRx

BTS X

RxTx

TxRx

USED IN CLOSED LOOPCONNECTION ONLY

The capacity of a closed loop single E1 or T1 circuit daisy chain is the same as that foran open ended daisy chain. The closed loop daisy chain has redundant signalling linksfor 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 �31 � b

2for E1 links

n �24 � b

2for T1 links.

Where: n is: the number of carriers.

b the number of BTS sites in the chain.

The results should be rounded down to the nearest integer.


30 Sep 20032�10


GMR-0168P02900W21-M

Example

A single E1 circuit daisy chain with three BTSs, the maximum capacity of the chain isgiven by:

31 � 32

� 14 carriers

A single T1 circuit daisy chain with three BTSs, the maximum capacity of the chain is isgiven by:

24 � 32

� 10 carriers

These carriers can be distributed between the three sites. If the loop is closed, the BSChas additional signalling links, although the same number of carriers are supported.

Daisy chain with branch BTS site

The addition of a branch BTS site (BTS Y), as shown in Figure 2-6, affects the capacityof the links between the BSC and the site from which the branch originates as these areused for the path to the branched site.

Figure 2-6 Daisy chain with branch

BSC BTS 1 BTS 2

BTS 3 BTS 4

RxTx

Rx

Tx Rx

Tx

RxTx

TxRx TxRxRx

Tx

TxRx

BTS X

RxTx

TxRx

USED IN CLOSED LOOPCONNECTION ONLY

BTS Y

Rx

Tx

A branch may have multiple BTS sites on it. A branch may be closed, in which casethere 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 E1or T1 circuit to the branch needs to carry redundant signalling links.


30 Sep 2003


68P02900W21-M

GMR-012�11

Aggregate Abis

This is an option designed to allow greater flexibility when network planning. It can alsohelp reduce leasing costs of E1/T1 links by optimizing the link usage over the greatestdistance between a BSC and BTS.

This is achieved by the introduction of third party multiplexer equipment enabled byMotorola software. This equipment allows timeslots on one E1/T1 link to be multiplexedto more than one BTS. Therefore, if the situation arises where several single carrierBTSs would each require their own dedicated E1/T1 link, greatly under utilizing each linkcapacity.

Now, providing the geographical locations of the sites and distances of the E1/T1 linkswork out advantageously, it is possible to send all the traffic channels for every siteinitially over one E1/T1 link to the third party multiplexer and then distribute them overmuch shorter distances to the required sites.

Providing the distance between the BSC and the multiplexer site is sufficiently large, thisshould result in significant leasing cost savings over the original configuration. Below aretwo diagrams illustrating the before (Figure 2-7) and after (Figure 2-8) scenarios.

Figure 2-7 Typical low capacity BSC/BTS configuration

BSC

5x64 kbit/s TIMESLOTS USED

BTS

26x64 kbit/s TIMESLOTS UNUSED

TWO CARRIERONE RSL

BTS

TWO CARRIERONE RSL

BTS

TWO CARRIERONE RSL

5x64 kbit/s TIMESLOTS USED26x64 kbit/s TIMESLOTS UNUSED



30 Sep 20032�12


GMR-0168P02900W21-M

Figure 2-8 Example using a switching network

BSC

5x64 kbit/s TIMESLOTS USED

BTS

26x64 kbit/s TIMESLOTS UNUSED

TWO CARRIERONE RSL

BTS

TWO CARRIERONE RSL

BTS

TWO CARRIERONE RSL



E1/T1MULTIPLEXER


BTS

TWO CARRIERONE RSL


MORE EFFICIENT USE OFLONGEST E1/T1 LINK

Another advantage of introducing the multiplexer is the improvement in the timeslotmapping onto the Abis interface.

Currently they are allocated from timeslot 1 upwards for RSLs and timeslot 31downwards for the RTF traffic channels. Most link providers lease timeslots in contiguousblocks (that is, no gaps between timeslots). Under the existing timeslot allocation schemeit often means leasing a whole E1/T1 link for a few timeslots. There is a new algorithmfor allocating timeslots on the Abis interface. This is only used on the links connecteddirectly to the new aggregate service; the existing algorithm for allocating timeslots isused on the other links.

Under the new software the timeslots are allocated from timeslot 1 upwards. The RSLsare allocated first and the RTF timeslots next, with each site being equippedconsecutively, 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, alsothat the RSLs are equipped first on a per site basis to coincide with the default timeslotsfor the software downloads to the BTSs.


30 Sep 2003


68P02900W21-M

GMR-012�13

Figure 2-9 is an example of timeslot allocation in a network using an aggregate service,with links to the aggregate service and links bypassing it.

Figure 2-9 Timeslot allocation using new and old algorithms

BSC

BTS 2

ORIGINALALGORITHM

BTS 3

NEWALGORITHM

BTS 1

TWO CARRIERONE RSL

E1/T1MULTIPLEXER

BTS 4

ALLOCATIONUNAFFECTED

ORIGINALALGORITHM

ALLOCATIONUNAFFECTED

NEW ALGORITHM

ALLOCATIONAFFECTED

NEWALGORITHM

ALLOCATION AFFECTED

ALLOCATIONAFFECTED

12345

RSL1RTF1RTF1RTF2RTF2

1112131415


12345

RSL1RTF1RTF1RTF2RTF2 1

2345


6789

10


131302928


12345


131302928


1617181920


6789

10


ALLOCATION AFFECTED

NEW ALGORITHM

Similar problems can be encountered when equipping redundant RSL devices onto pathscontaining aggregate services. Because of the new way of allocating timeslots whenconnecting to a aggregate service from timeslot 1 upwards, there is no way of reservingthe default download RSL timeslot. This gives rise to the situation where the default RSLtimeslot has already been allocated to another device, RTF for example.

To avoid this happening, the primary and redundant RSLs can be equipped first (in anorder that results in the correct allocation of default RSL timeslots), or reserve the defaultdownload RSL timeslot so that it may be allocated correctly when the primary orredundant RSL is equipped.

If it is envisaged to expand the site in future to preserve blocks of contiguous timeslotson the links, it is possible to reserve the timeslots needed for the expansion so that theycan be made free in the future.


30 Sep 20032�14


GMR-0168P02900W21-M

Alarm reporting

This feature has an impact on the alarm reporting for the E1/T1 links. If the link isconnected to a third party switching network and is taken out of service, the BTS willreport the local alarm, but the remote alarm will only go to the third party aggregateservice 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 networkentities (BTS, BSC). In these cases it is the responsibility of the third party aggregateservice provider to inform the users of the link outage. The only indication of failure is theRSL state change to out of service.

Figure 2-10 shows a possible network configuration using several switching networks.

Figure 2-10 Alternative network configuration with E1/T1 switching network

BSC

E1/T1MULTIPLEXER

BTS

BTS

BTS

BTS

E1/T1MULTIPLEXER

E1/T1MULTIPLEXER

E1/T1MULTIPLEXER

BTS BTS

BTS BTS

BTS BTS

BTS BTS

Restrictions/limitations

The ability to nail path timeslots along a link containing an E1/T1 switching network issupported. 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 isa pseudo site, the aggregate service is counted as a site in the path. Hence the numberof BTSs that can be present in a path is reduced from ten to nine.

GCLK synchronization functions, but any BTS sites connected downlink from a switchingnetwork will synchronize to it and not the uplink GSM network entity (BTS, BSC).


30 Sep 2003


68P02900W21-M

GMR-012�15

RTF path fault containment

Each transceiver at a BTS requires a receive/transmit function enabled which tells itvarious operating parameters to use. These include the ARFCN, type of carrier, andprimary/secondary path, among others. It is the path that is of concern here. An RTFmay be assigned different paths. The path is the route which the two 64 kbit/s timeslotsassigned to the transceiver from the E1/T1 link, take to get to and from the BTS/BSC.Each RTF can be assigned a different path for its two timeslots, even RTFs that are inthe same cell.

One path is designated the primary, the other the secondary. In the event of the primarypath failing, the RTF chooses the secondary path and the carrier remains in callprocessing. At present, if all the paths to one RTF fail, the whole cell is taken out of callprocessing, regardless of whether there are other transceivers/RTFs with serviceablepaths in the same cell.

This feature allows the cell to remain in call processing if the failure of all paths to oneRTF occurs, as described in the previous paragraphs. Any call in progress on the failedpath is handed over to the remaining RTFs in the same cell, if there are availabletimeslots. If there are not enough available timeslots, the call is released. Also, thetimeslots on the transceiver of the failed path are barred from traffic until the path isre-established, but any SDCCHs on the carrier remain active.

If all paths to all RTFs in an active cell have failed and there is still an active RSL, thenthe cell is barred from traffic.

Advantages

By using this feature, and removing any redundant paths that would normally beequipped to manage path failure, the customer could save on timeslot usage. Figure 2-11shows the conventional redundant set-up, requiring in this case four extra timeslots toprovide 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 ofeight for Figure 2-11. The customer has to weigh up the cost saving advantages of thenew software against the reduced capacity in the event of failure of a RTF path.


30 Sep 20032�16


GMR-0168P02900W21-M

Figure 2-11 A configuration with a BTS equipped with two redundant RTFs

RTF1 EQUIPPEDON PATH 1

(2 TIMESLOTS)


(2 TIMESLOTS)


(2 TIMESLOTS)


(2 TIMESLOTS)

BTS 3 BTS 1

BSC

BTS 2

Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs


(2 TIMESLOTS)


(2 TIMESLOTS)

BTS 3 BTS 1

BSC

BTS 2


30 Sep 2003


68P02900W21-M

GMR-012�17

16 kbit/s RSL

The 16 kbit/s RSL (introduced at GSR3) reduces the transmission costs between theBSC and BTS (Abis interface) for single carrier sites in particular.

Prior to this, a single carrier BTS required three E1/T1 64 kbit/s timeslots; one for the64 kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslotsdedicated to the traffic channels can accommodate eight traffic channels normally.

In the case of a single carrier site; it was not possible to use all eight traffic channels ofthe two 64 kbit/s timeslots. The reason is that, in the case of a single carrier site, thecarrier is the BCCH carrier and the air interface timeslot 0 of the BCCH carrier isreserved for BCCH information. This information is generated at the BTS not the BSC.The TSW at the BTS routes the traffic channels from the two specified timeslots on theAbis interface to the dedicated transceiver for transmission.

Due to this, the traffic channel on the Abis interface corresponding to the timeslot 0 onthe air interface is unused and available to bear signalling traffic. This results in one16 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 unusedsub-channel because the RSL is not transmitting on the air interface. The advantage isthat it frees up one 64 kbit/s timeslot on the Abis interface, reducing the requirement toserve a single carrier system to only two 64 kbit/s timeslots. This operates with HorizonBTSs and InCell BTSs using KSW switching.

Figure 2-13 (fully-equipped RTF) and Figure 2-14 (sub-equipped RTF) show the eighttypes of RTF which are possible using the previously described options. They are listedin Table 2-2.

Table 2-2 RTF types

Type Options

1 A fully equipped BCCH RTF with an associated 16 kbit/s RSL.

2 A fully equipped BCCH RTF with no associated 16 kbit/s RSL.

3 A fully equipped non-BCCH RTF with an associated 16 kbit/s RSL.

4 A fully equipped non-BCCH RTF with no associated 16 kbit/s RSL.

5 A sub-equipped BCCH RTF with an associated 16 kbit/s RSL.

6 A sub-equipped BCCH RTF with no associated 16 kbit/s RSL.

7 A sub-equipped non-BCCH RTF with an associated 16 kbit/s RSL.

8 A sub-equipped non-BCCH RTF with no associated 16 kbit/s RSL.


30 Sep 20032�18


GMR-0168P02900W21-M

Fully equipped RTF

Figure 2-13 Fully equipped RTF

NOASSOCIATED16 kbit/s RSL

ASSOCIATED16 kbit/s RSL

NON-BCCH

FULLY EQUIPPED RTF



BCCH

Timeslot X

Timeslot Y

KEY

Configuration 1 2 3 4

16 kbit/s sub-channel unavailable for use.16 kbit/s sub-channel used for 16 kbit/s RSL.16 kbit/s sub-channel available for voice traffic.

16 kbit/sBTS only

16 kbit/sBTS only


30 Sep 2003


68P02900W21-M

GMR-012�19

Sub-equipped RTF

Figure 2-14 Sub-equipped RTF



NON-BCCH

SUB-EQUIPPED RTF



BCCH

Timeslot X

Timeslot Y

KEY

Configuration

16 kbit/s sub-channel used for 16 kbit/s RSL.16 kbit/s sub-channel available for voice traffic.

16 kbit/sBTS only

16 kbit/sBTS only

5 6 7 8

Planning constraintsThe following RSL planning constraints apply:

S A BTS supports either 16 kbit/s RSLs or 64 kbit/s RSLs, not both.

S A BSC supports both 16 kbit/s and 64 kbit/s RSLs.

S A BSU based BTS supports up to eight 16 kbit/s RSLs.

S Up to six 16 kbit/s RSLs are supported by Horizon II macro and Horizonmacro.

S Up to two 16 kbit/s RSLs are supported by Horizonmicro2 / Horizoncompact2.

S Up to six 16 kbit/s RSLs are supported by M-Cell6.

S Up to four 16 kbit/s RSLs are supported by M-Cell2.

S Up to two 16 kbit/s RSLs are supported by M-Cellmicro and M-Cellcity.

S The BTS and BSC supports a mix of both fully equipped and sub-equipped RTFs.

S A ROM download is carried out over a 64 kbit/s RSL, even at a site designated a16 kbit/s RSL.

S A CSFP download utilizes a 16 kbit/s RSL at a 16 kbit/s designated site.

S A KSW must be used at an InCell BTS where a 16 kbit/s RSL is equipped.

S The 16 kbit/s RSL is only able to be configured on CCITT sub-channel 3 of a64 kbit/s E1/T1 timeslot for BSU based sites.

S An associated 16 kbit/s RSL is supported on redundant RTF paths where oneexists on the primary path.


30 Sep 20032�20


GMR-0168P02900W21-M

16 kbit/s XBL

The 16 kbit/s XBL (introduced at GSR3) provides a lower cost solution to the customerby 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. Thisfrees three 16 kbit/s sub-channels on the E1/T1 64 kbit/s timeslot to enable them to beused as TCHs. A BSC may interconnect with up to nine RXCDRs and vice-versa. Up to18 XBL links total may be deployed in any configuration. There is no restriction on whichtimeslot 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 bepossible to have two different rates at the same BSC to RXCDR, although this would notbe considered a typical configuration. As a result of the introduction of the 16 kbit/s RSLthere is no reduction in processing capacity of the BSC or RXCDR.

Figure 2-15 demonstrates XBL utilization.

Figure 2-15 XBL utilization

BSC 1

BSC 2

BSC 8

BSC 9

BSC 3 RXCDR

XBL XBL

XBL XBL

XBL XBL

XBL XBL

XBL XBL

MAXIMUM OF TWO XBLs BETWEEN THE BSC AND XCDR OF EITHER 64 kbit/s OR 16 kbit/sON THE E1/T1 LINK.

MAXIMUM OF NINE BSCs CONNECTED TO AN RXCDR OR VICE VERSA.


30 Sep 2003


68P02900W21-M

GMR-012�21

Dynamic allocation of RXCDR to BSC circuits (DARBC)

The dynamic allocation of RXCDR to BSC circuits feature introduces fault managementfor call traffic on the BSC to RXCDR interface (referred to as the Ater interface) bymanaging the individual 16 kbit/s channels (called Ater channels) on this interface. Inaddition, this feature provides for validation of the CIC and Ater channel provisioningbetween the BSC and RXCDR to ensure that calls are placed on the correct circuitbetween the BSC and the MSC. Without this feature in place, no fault management ofthe Ater channels would be possible, and all Ater and CIC information must be manuallyverified by the operator, resulting in a higher O&M cost for the Motorola BSS.

From GSR5 onwards, an operator has the option to operate either in the auto-connectmode or in the backwards compatibility mode. These modes are managed on a perAXCDR basis.

Auto-connect mode

This is an operator selectable mode which refers to a BSC in which Ater channels areallocated and released dynamically as resources are provisioned, unprovisioned orduring handling of fault condition. Auto-connect mode provides the fault tolerancetogether with the call processing efficiency of backwards compatibility mode. This is therecommended mode of operation for the BSC.

Backwards compatibility mode

This is an operator selectable mode which refers to a BSC and/or RXCDR in which Aterchannels and CICs are statically switch connected. This mode does not provide any faulttolerance and CIC validations, and is intended only to provide an upgrade path. Onceboth BSC and RXCDR are upgraded, the use of auto�connect mode is recommended.

NOTE When upgrading the network and the BSC is being upgradedbefore the RXCDR, backwards compatibility mode must be usedfor the corresponding AXCDR.

Prior to introduction of this feature, all Ater channels were statically assigned and use ofXBL links was not mandatory. From GSR5, should an operator decide to use theauto-connect, it becomes imperative to equip XBL links on the RXCDR and BSC. Ifno XBLs are equipped, and the AXCDR is operating in the auto-connect mode, all CICsat the BSC associated with that AXCDR will be blocked and no call traffic will go to thatAXCDR.

GSR6 (Horizon II)BTS concentration

30 Sep 20032�22


GMR-0168P02900W21-M

BTS concentration

Introduction

The BTS concentration feature (introduced at GSR4) reduces the number of BTS�BSCterrestrial backhaul resources that are planned on the E1/T1 link between the BTS andBSC. This feature is made possible by dynamically allocating terrestrial backhaulresources for the BTS transceiver channels, referred to as radio transmit function (RTF)resources, instead of making static assignments on a one for one basis.

With this feature, it is common to deploy more BTS carrier equipment (RTFs), forcoverage purposes, than deployed terrestrial backhaul resources. This planningapproach takes advantage of the trunking efficiencies gained by sharing terrestrialbackhaul resources among multiple BTS RTFs. This feature is particularly useful forin-building systems.

Prior to the introduction of BTS concentration, terrestrial backhaul resources werestatically allocated when RTFs were equipped. This feature preserves the existingmechanism (static allocation), but allows the operator the choice, on a per BTS sitebasis, 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 chainconfiguration is planned. For a daisy chain network configuration using E1s, there can beup to ten BTS sites connected together in a serial fashion to a serving BSC. The BTSconcentration feature greatly increases the terrestrial backhaul trunking efficiency in thislarge network configuration by allocating E1/T1 16 kbit/s backhaul resources over theentire 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 DYNETdevice. The control of the DYNET device enables a network operator to configure thedynamic 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 bemade, where a PATH identifies the network topology of BSC to specific BTS connections.The DYNET is more fully described later in this chapter.

GSR6 (Horizon II) BTS concentration

30 Sep 2003


68P02900W21-M

GMR-012�23

Key terms

Key networking concepts and terms used in the following sections are: network trafficload expressed in Erlangs, network blocking expressed as grade of service (GOS), andNetwork traffic modeling using the Erlang B formula. The concepts and terms that will beused to describe the BTS Concentration feature are defined in the following text.

BTS concentration concepts and rules

The terminology and definitions are:

S BTS concentration feature

This is a software feature that can be installed on BTSs supporting switching of16 kbit/s backhaul resources. It enables the terrestrial backhaul to be mostefficiently planned by dynamically allocating these resources and requires asignificant software component to be installed on the BSC.

S BTS site

A BTS site may have one or more BTS cells at the same site. The radio signallinglink (RSL) planning is performed on a per BTS site basis.

S BTS�BSC E1/T1

This is either an E1 or a T1 communication link between the BTS site and theBSC. Additionally, this communication link could be a daisy chain through multipleBTS sites connected to a serving BSC.

S Common pool

The common pool refers to the pool of resources that are available for unrestrictedassignment on the BTS�BSC E1/T1 link to any cell or site requesting terrestrialbackhaul resources.

S DYamic NETwork (DYNET) device

This is a new device created for the BTS concentration feature. A DYNET deviceis used to specify the BTS sites sharing of dynamic resources and how they areinterconnected. When a DYNET is equipped, using the equip command, thePATH devices for the BTSs that support dynamic allocation are also equipped. Seethe DYNET section for more details.

S Dynamic allocation

This is the way the BTS concentration feature allocates terrestrial backhaulbetween the BSC and BTS site on an as needed basis.

S Erlang

The Erlang is a measure of traffic loading; (for example, the percentage of timethat a resource (channel or link) is busy). One Erlang represents 3600 call secondsin a one hour time period. This is equivalent to one call holding a circuit for onehour. Typically a cellular call is held in the range of 120 seconds. A 120 secondhold time would correspond to 33 milli-Erlangs (0.033 Erlangs).

S Erlang B

Erlang B refers to the call model used to determine the number of circuits requiredin order to satisfy a given GOS and call load measured in Erlangs. The formula isbased on a call arrival rate with a Poisson probability distribution.


30 Sep 20032�24


GMR-0168P02900W21-M

S Grade of Service (GOS)

The GOS is specified in percent. A 1% GOS means that, on average, 1 call out of100 calls will be blocked, often referred to as a 1% blocking rate. Typically, a 1%GOS is a desirable terrestrial backhaul design goal.

S PATH devices

This term refers to the E1/T1 connectivity from the BSC to the BTS site or multipleBTS sites in the case of a BTS daisy chain.

S Radio Signalling Link (RSL)

This is the signalling link between the BSC and BTS. It can be allocated 16 kbit/sor 64 kbit/s resources over the E1/T1. Each BTS site has at least one 16 kbit/s or64 kbit/s RSL, and more than one can be allocated per BTS up to a maximumnumber specified by each individual BTS product.

S Radio Transmit Function (RTF)

An RTF corresponds to one BTS carrier which can support up to 8 x 16 kbit/sbackhaul resources.

S Reserved allocation

The BTS concentration feature permits the reserved allocation of terrestrialbackhaul resources. For example, in a daisy chain of BTS sites, each cell in a BTSsite can have a reserved number of terrestrial backhaul resources that cannot beallocated to the other BTS cells or to other BTS sites in the daisy chain.

S Reserve pool

The reserve pool is a term used to describe the number of available terrestrialbackhaul resources that can be used by a specific BTS cell and cannot bedynamically allocated to another cell.

S Static allocation

Prior to the introduction of the BTS concentration feature, the allocation ofresources over the BTS�BSC E1/T1 link was by static allocation. Static allocationpermits up to 8 (16 with redundancy) terrestrial backhaul resources to be assigneddirectly to one BTS RTF resource.

S Subrate switching

Subrate switching is the capability to switch 16 kbit/s backhaul resources.

S Terrestrial backhaul

The term terrestrial backhaul is used in the description of the BTS concentrationfeature to describe the resources that are available over the BTS�BSC E1/T1 linkor Abis Interface. An E1 link comprises 32 x 64 kbit/s timeslots, of which up to 31can be allocated to voice traffic and to RSL signaling channels. A T1 can beallocated with up to 24 x 64 kbit/s timeslots. Each E1/T1 time slot can carry up tofour calls at 16 kbit/s per traffic channel. When terrestrial backhaul is used in themore general sense, the term additionally refers to the E1/T1 links between theBSC and RXCDR and to the links between the RXCDR and the MSC.

S Timeslot (TS) 64 kbit/s

A timeslot is one 64 kbit/s channel on an E1 or T1 as provided by terrestrialbackhaul. A timeslot can carry up to four 16 kbit/s traffic channels.


30 Sep 2003


68P02900W21-M

GMR-012�25

S Traffic CHannel (TCH) 16 kbit/s

The term TCH refers to the BTS radio air interface traffic channel. The bandwidthrequired to carry one cellular call over the terrestrial backhaul, in support of theTCH, is 16 kbit/s.

S Transcoder Rate Adaption Unit (TRAU)

The TRAU corresponds to one transcoding hardware unit per traffic channel. TheTRAU hardware unit processes TRAU frames from the BSS and performs thebidirectional conversion to PCM frames for transmission to the MSC.

TRAU hardware allocation is not performed by the BSC as part of the dynamicallocation of terrestrial backhaul resources. Instead, TRAU allocation is performedwhen the MSC allocates a link from the MSC to the RXCDR, then to the BSC for aspecific call.

DYNET

DYNET description

To support the functionality of this feature, the DYNET device has been added. A DYNETdevice is used to specify the BTSs sharing dynamic resources and how they areinterconnected. This device exists as a construct to specify a BTS network and does notexist as a managed device. A DYNET may be equipped or unequipped, but may not belocked, unlocked, or shut down. If third party timeslot multiplexer sites, or marker sites,are used, they may be included in the definition of a DYNET.

All DYNETs that share the same first identifier must have exactly the same BTSs, ormarker sites, in the same order. These DYNETs must also have different links used bythe BTSs that use dynamic allocation within a BTS network. These limitations allowmultiple link BTS networks to be defined for sharing purposes, whilst limiting theconfiguration to simplify sharing.

Equipping DYNETs and PATHs

When a DYNET is equipped, using the equip command, the PATH devices for the BTSsthat support dynamic allocation are also equipped. PATH devices are not automaticallyequipped for BTSs that do not support dynamic allocation. A PATH equipped for a nonclosed loop daisy chain has a second identifier equal to the second identifier of theDYNET multiplied by two. In the case of a closed loop daisy chain, an additional PATHdevice is equipped automatically. This has a second identifier that is one greater than thesecond identifier of the first automatically equipped PATH device.

NOTE The indentifiers of the PATHS automatically equipped when aDYNET is equipped are not allowed to be used when equippingthe PATH device.

The amount of resources reserved for dynamic allocation is set to zero timeslots whenthe DYNET is initially equipped.

Equipping RSLs

RSLs for BTS sites that support dynamic allocation must be equipped to theautomatically equipped PATHs associated with the DYNET.


30 Sep 20032�26


GMR-0168P02900W21-M

Blocking considerations

Dynamic allocation allows greater RF channel capacity to be equipped (RTFs) than thereare terrestrial backhaul resources, whether at a BTS site, or within a BTS dynamicnetwork. This allows RTF equipage for coverage purposes rather than for networkcapacity purposes. Additionally, the dynamic allocation method allows terrestrial backhaulresource capacity to move dynamically between radio units in the same network basedupon traffic considerations. The system planner needs to be aware that if enough userstry to gain access to a system planned with many more RTFs than terrestrial backhaulresources, some of the call attempts will be blocked because of the limited number ofterrestrial backhaul resources.

Blocking control

The BTS concentration feature provides a facility to reserve terrestrial backhaulresources 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 someE1/T1 resources available independent of the other BTS cells or other BTS site trafficloads, thereby providing a guaranteed method of blocking control. However, the best useof terrestrial backhaul resources is obtained by statistically planning the network, usingthe dynamic allocation method to achieve a low blocking probability (a good GOS).

Reserved allocation algorithm

The feature allows reserved resources to be allocated to specific cells. In configuring anetwork with BTS concentration, a pool of terrestrial backhaul resources must be setaside for dynamically allocating to the relevant cells/BTS sites. This pool is called thedynamic pool in the following discussion. In addition, the feature allows each cell tospecify an amount of reserved resources, which are taken (dynamically allocated) fromthe dynamic pool. Once a number of resources are reserved for a cell, these resourcesare allocated specifically to the cell and, therefore, are not available for sharing.

To facilitate this discussion from the planning perspective, imagine that there is acommon pool that holds the remaining resources in the dynamic pool after resourcesare reserved for specific cells. Figure 2-16 shows what the dynamic pool of terrestrialbackhaul resources consists of from the planning perspective: a common pool and nreserved pools, one for each BTS site.

Each reserved pool consists of the resources associated with a 16 kbit/s RSL timeslot aswell as any additional resources that are specifically reserved on a per cell basis. The16 kbit/s RSL timeslot-associated resources are shared among the cells at the BTS site,but cannot be shared with other BTS sites. The reserved pool of an individual BTS sitecan be set to zero. For each 16 kbit/s RSL, there will always be three resources availablefor reserved allocation among cells at the same site. If there are two 16 kbit/s RSL, sixreserved resources are available, and so on. However, 16 kbit/s RSLs equipped forredundancy do not provide any reserved resources. For example, if there are six16 kbit/s RSLs and three of which are for redundancy, a total of nine RSL associatedresources are available to be included in the reserved pool.

When a new call arrives to a cell, the BSC always first allocates a resource from thereserved pool of the corresponding BTS site. Specifically, it will first attempt to allocate anRSL-associated resource. If none is available, it allocates a resource from the additionalresources specifically reserved for the cell. If all reserved resources are depleted, theBSC then allocates a resource from the common pool. If again no resource is available inthe common pool, the call is blocked.

If the BTS site is assigned a 64 kbit/s RSL instead of a 16 kbit/s RSL, then there are noRSL timeslot-associated resources available for dynamic allocation.


30 Sep 2003


68P02900W21-M

GMR-012�27

Figure 2-16 A dynamic pool of terrestrial backhaul resources

BTS site 1 RESERVED POOL

COMMON POOL

BTS site n Cell 1 additionalreserved resources

RSL�associated reservedresources (Quantity = 0,

3, 6..)

BTS site 2 RESERVED POOL

BTS site n RESERVED POOL



Emergency call handling

With BTS concentration, emergency calls take precedence over non-emergency calls inthe allocation of terrestrial backhaul resources. The emergency calls precedence inbackhaul resource allocation is independent of whether Emergency Call Pre-emption(ECP) is on or off. If no terrestrial backhaul resources are available when an emergencycall requests a resource, the oldest existing non-emergency call is terminated in order toprovide the needed resource. In addition, emergency calls take precedence overreserved resources allocated to specific cells. Emergency calls use whatever freeterrestrial backhaul resource becomes available first. The BSC will pre-emptnon-emergency calls in the same cell. The BSC next pre-empts non-emergency calls atthe site. Finally, the BSC will terminate non-emergency calls from other sites within thesame DYNET. If all available terrestrial backhaul resources are in use by emergency callsor if no terrestrial backhaul resources are available, then the new emergency call isblocked.

Radio signalling link (RSL) planning

When a BTS daisy chain is configured during the configuration management phase, theoperator has to equip each BTS site in the daisy chain with at least one 64 kbit/s timeslotfor RSL use. This is necessary so that when a BTS site is initialized it can communicatewith the BSC at 64 kbit/s. After the initialization process concludes, the BTS site can thenbe allocated this 64 kbit/s E1/T1 timeslot as one 16 kbit/s RSL and three 16 kbit/sterrestrial backhaul resources. These three 16 kbit/s resources are always consideredpart of a reserved resources on a per site basis and can be used by any cell within a site.These three RSL associated resources may not be shared from one BTS site to another.A site always allocates RSL associated 16 kbit/s resources before allocating otherreserved resources or before requesting allocation from the common pool of resources.

Alternatively, the BTS site can continue to use this 64 kbit/s E1/T1 timeslot as one64 kbit/s RSL. When the RSL is used as a 64 kbit/s signalling link, there are no RSLassociated resources to be used as reserved resources at the site.


30 Sep 20032�28


GMR-0168P02900W21-M

Network topologies

BTS concentration does not support all possible network topologies. Dynamic allocationis limited to spoke, daisy chain, and closed loop daisy chain network configurations.

Figure 2-17, Figure 2-18 and Figure 2-19 illustrate the network configurations to whichthese terms apply.

Figure 2-17 Spoke configuration

BSC BTS 1

Figure 2-18 Daisy chain configuration

BSC

BTS 1 BTS 2 BTS 3

Figure 2-19 Closed loop daisy chain configuration

BSC

BTS 1 BTS 2 BTS 3


30 Sep 2003


68P02900W21-M

GMR-012�29

Links between BTSs

Even with dynamic allocation, greater bandwidth than that provided by a single link maybe required. To provide this, networks following the configurations shown in Figure 2-20,Figure 2-21 and Figure 2-22 may have one to three links between each BTS�BSC orBTS�BTS pair in the configuration. The same number of links must be specified betweeneach pair to maintain the simplicity needed to provide dynamic allocation.

Figure 2-20 Spoke configuration with three links

BSC BTS 1

Figure 2-21 Daisy chain configuration with two links

BSC

BTS 1 BTS 2 BTS 3

Figure 2-22 Closed loop daisy chain configuration with three links

BSC

BTS 1 BTS 2 BTS 3

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 theBTSs that use dynamic allocation. This capacity forms the pool from which terrestrialbackhaul resources are allocated.


30 Sep 20032�30


GMR-0168P02900W21-M

Third party multiplexer equipment

This feature supports the use of third party multiplexer equipment within a networkconfiguration. Such equipment defines a terrestrial network outside of the knowledge ofthe BSS. To the BSS, this terrestrial network appears as a timeslot multiplexer site (alsoknown as a marker site) within the BSS configuration.

Figure 2-23 illustrates the use of third party multiplexer equipment in a closed loopconfiguration.

Figure 2-23 Closed loop daisy chain configuration with third party multiplexer

BSC

BTS 1 BTS 2 BTS 3

THIRD PARTYMULTIPLEXEREQUIPMENT

THIRD PARTYMULTIPLEXEREQUIPMENT

Nailed paths

It may be required to declare additional paths to a BTS that uses dynamic allocation fornail connection purposes. This feature supports this functionality.

Figure 2-24 shows a closed loop daisy chain with an additional path (shown as a dashedline) to BTS 2. No BSS managed resources can be placed on this additional path, itexists solely as a convenience for defining nailed connections.


30 Sep 2003


68P02900W21-M

GMR-012�31

Figure 2-24 Extra path definition for nailed connections

BSC

BTS 1 BTS 2 BTS 3

Additional path definition


Additional functionality introduced allows the RTF to be used for non TCH channels whenthe path(s) for the RTF are not available, leaving the cell for the RTF in service. However,the cell is still taken out of service when all RTFs in the cell lose their paths to the BSC. Adynamic allocation site may use any of the path(s) to the site that appear in the dynamicallocation network definition. If all of these path(s) are out of service, a dynamic allocationsite cannot be allocated any terrestrial backhaul resources. Hence, the cell(s) at this siteare taken out of service under these conditions.

Additional paths to dynamic allocation sites, as described previously, may be declared asa convenience. Since these paths are not used for terrestrial backhaul resources, theirstate does not influence the state of the cells at a dynamic allocation site.


30 Sep 20032�32


GMR-0168P02900W21-M

Allocating and freeing terrestrial backhaul resources

This feature attempts to minimize the BTS interaction needed to allocate or free aterrestrial backhaul resource. The terrestrial backhaul resources are initially a set ofnailed connections throughout a BTS network (see Figure 2-25).

Figure 2-25 Terrestrial backhaul resource nailed connection before a call

BSC

BTS 1 BTS 2 BTS 3

When a resource is allocated to a BTS, that BTS breaks its nailed connection. Aconnection to the TCH is made in place of the nailed connection. When the resource isfreed, the BTS re-establishes the nailed connection. No change in connections isrequired at any other BTS in the BTS network.

Figure 2-26 shows a resource allocated to BTS 2. BTS 2 connects the resource to theTCH using one of the two possible paths to the BSC. BTS 2 changes the connection ifthe path being used fails during the call. BTS 2 connects the unused path to the Abis idletone.

Figure 2-26 Terrestrial backhaul resource connections during a call

BSC

BTS 1 BTS 2 BTS 3


30 Sep 2003


68P02900W21-M

GMR-012�33

Redundancy

This feature does not support the use of closed loop daisy chains for additional capacitywhen all links are available. This feature treats the closed loop nature of the closed loopdaisy chain as existing for purposes of redundancy. Such a design ensures that no callsare dropped when a link becomes unavailable in a closed loop configuration. This designalso simplifies the tracking of terrestrial backhaul resources.

For the purposes of this feature, the configuration shown in Figure 2-27 is considered aclosed loop daisy chain configuration.

Figure 2-27 Using redundancy for extra capacity before failure

BSC

BTS 1 BTS 2 BTS 3

Call 1

Call 2

The closed loop daisy chain has the potential to use the same resource in both parts ofthe loop. For example, in Figure 2-28, both BTS 1 and BTS 3 could be using the sameresource. BTS 1 could use the resource on the link between the BSC and BTS 1. BTS 3could use the resource on the link between the BSC and BTS 3. If either link fails, one ofthe calls is no longer able to use the resource.

Figure 2-28 Using redundancy for extra capacity after failure

BSC

BTS 1 BTS 2 BTS 3

Call 1

Failed link


30 Sep 20032�34


GMR-0168P02900W21-M

Performance issues

The use of satellites to carry links introduces an additional 600 millisecond one way delayto messages sent on the links. Dynamic allocation requires a BTS to BSC request and aBSC to BTS response. These messages incur a 1.2 second delay beyond the normaltransmit and queuing delay times. These delay times affect call setup and handoverdelay times, especially if retransmission of the request/reply scenario is necessary due tomessage loss.

This feature addresses this problem by adding an operator specified parameter thatprovides the retry time for dynamic allocation requests. For non-satellite systems, theretry time should be set to its minimum value. For satellite systems, the retry should beset to 1.2 seconds plus the minimum retry value. The minimum retry time chosen is 150milliseconds to account for transmit and queuing delay times (for 16 kbit/s links, a longerretry time is recommended to avoid excessive retries).

Configuration and compatibility issues

The BTS concentration feature is supported for BSS GSR4 software releases onwardson BTS4, BTS5, BTS6, ExCell and TopCell (with TSW) and in-building picocellularsystem products. BTS products that support subrate switching (switching of 16 kbit/sterrestrial backhaul resources) are essential for the feature. While the feature operateson 16 kbit/s switching, it can coexist with 64 kbit/s static switching in a mixed setup.

NOTE The BTS concentration feature is not supported on later BTSequipment, such as M-Cell or Horizonmacro.

The BTS concentration feature allows up to three E1/T1s to be allocated between theBSC and BTS site as terrestrial backhaul resources. This rule applies to all BTS productsthat support the BTS concentration feature. The maximum BTS daisy chain lengthserved by one BSC is 10 BTS sites.

The BTS concentration feature limits call congestion handling and priority call handling toradio resource call management. The existing functionality for call congestion handling,priority call handling, and emergency call handling allocates radio resources dynamically.Hence, the BTS concentration feature interacts with these existing call handling methodsbecause the new feature dynamically allocates terrestrial backhaul resources. Thehandling of emergency calls is discussed in the Emergency call handling section of thischapter.


30 Sep 2003


68P02900W21-M

GMR-012�35

Recommended BTS concentration planning guidelines

This section recommends some planning guidelines for planning the BTS concentrationfeature and discusses some uses for the reserved allocation algorithm of the feature.Applications of the guidelines are illustrated by the examples in the next section.

The BTS concentration feature allows terrestrial backhaul resources to be shared amongmultiple BTS sites and cells (as if the resources are allocated to a common resource poolfor sharing). In addition, a number of resources can be optionally reserved for specificBTS cells. It is recommended that network planning favours sharing resources and thatthe reserved allocation is used more sparingly, unless reserved resources are availableby default due to the use of 16 kbit/s RSL (see the Radio Signalling Link Planningsection in this chapter). This strategy allows more efficient use of the terrestrial backhaulresources.

Guideline 1

For a common pool of terrestrial backhaul resources that is to be shared among anumber of cells with different GOSs, enough resources should be allocated to meet themost stringent GOS among all relevant cells.

This guideline addresses the case when a daisy chain is planned and not all of the BTSsin the daisy chain need to have the same GOS. For example, in a daisy chain of threeBTS 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 beshared among these three BTS sites, only one GOS may be used for the purposes ofplanning the resources. Therefore, Guideline 1 recommends that the best GOS neededin 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 thecommon pool than if reserved for individual cells. Therefore, share the resources amongcells 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 the16 kbit/s RSL/s. In this case, follow Guideline 3 to estimate the overflow traffic from thedefault reserved resources and then to determine the required number of resources inthe common pool for meeting the most stringent GOS.

Reserved allocation is intended only as a safeguard mechanism, as implemented in theBTS concentration feature. Therefore, Guideline 2 recommends that the dynamicallocation from the common pool be used almost exclusively in order to minimize therequired terrestrial backhaul resources.


30 Sep 20032�36


GMR-0168P02900W21-M

Guideline 3

If resources are reserved for specific cells (either by default or by design), the trafficoverflowed from the reserved resources are handled by the resources in the commonpool. The size of the common pool for meeting a certain GOS can be determined usingthe following steps:

1. Use the Erlang B model to determine the blocking probability of the reservedresources, given the offered traffic load at each cell.

2. The traffic overflowed from reserved resources is simply the product of theexpected traffic load and the blocking probability of the reserved resources.

3. Sum the traffic overflowed from all cells.

4. Use the Erlang B model again to determine the number of resources needed to bein the common pool, in order to handle the total overflow traffic at the moststringent GOS requirement among all cells (according to Guideline 1).

Although the call arrival process at the resources might not be Poisson, the use of ErlangB model in steps 1 and 4 are reasonable approximations and has been verified insimulations.

The application of these steps is illustrated in examples 1 and 2 in the Examples sectionof this chapter.

Uses of reserved allocation algorithm

The following are a few possible applications of the reserved allocation algorithm, whichallows the operators to reserve resources for specific BTS cells:

S If there is insufficient knowledge of the traffic load on the individual BTS sites of arecently deployed network, resources may be allocated to reserved pools untilsome traffic statistics can be accumulated.

S As a transition strategy for moving from the static allocation planning method to thedynamic allocation of terrestrial backhaul resources out of a common resourcepool, the BTS concentration feature can be added to an existing network and thenplanned by allocating resources to only the reserved pools resulting in no effectivechange in the planned terrestrial backhaul resources. A follow-up planning processcan later be taken to take advantage of dynamic allocation of terrestrial backhaulresources out of a common resource pool.

S Suppose in an existing system with BTS concentration, better GOSs are deemednecessary for some specific and important cells, but for whatever reason it is notfeasible to immediately deploy more terrestrial backhaul resources to the commonpool to achieve the required GOSs.

A possible strategy might be to re-allocate some resources from the common poolto the reserved pools of the important cells to improve their GOSs. However, as atrade-off, reducing the size of the common pool will result in worst GOS for theother cells that rely on the common pool. Nonetheless, the more extensive use ofthe reserved pool could be considered a transition strategy until more terrestrialbackhaul resources become available.


30 Sep 2003


68P02900W21-M

GMR-012�37

Examples

The following examples provide a better understanding for how the guidelines in theprevious section might be applied when planning a network with the BTS concentrationfeature.

The first two examples, Examples 1 and 2, demonstrate the trunking efficiency gainedby 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 thosereserved 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 reservedresources and call loading causes blocking to occur at a particular cell, even thoughthere is still some terrestrial backhaul resource available.

All examples are worked using the Erlang B formula/model.


30 Sep 20032�38


GMR-0168P02900W21-M

Example 1

The number of required 16 kbit/s terrestrial backhaul resources between the BSC andBTS or daisy chain of BTSs depends on the amount of traffic (in Erlangs) expected ateach BTS cell/site and the blocking probability for the resources. (A new call is blockedwhen all resources have been allocated to other on-going calls.) This example illustrateshow planning can be carried out. The DYNET in Figure 2-28 is used in the examples andeach BTS site is assumed to have only one cell. Suppose 3 Erlangs of traffic is expectedto come through the cell in BTS 1, 2 Erlangs through BTS 2, and 5 Erlangs throughBTS 3.

NOTE It is important not to confuse the blocking at the terrestrialbackhaul 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, andto allow an 1% blocking probability for these resources, a total of 18 resources areneeded to handle the 10 Erlangs of offered traffic, according to Erlang B formula.

However, to reserve some resources for each BTS site to provide the required blockingprobability, calculate the required number of resources for each BTS site. Assume thatthe desired blocking probabilities for the terrestrial backhaul resources are 1%, 2% and1% for BTS 1, BTS 2 and BTS 3, respectively. Again, using the Erlang B formula,reserve eight resources to handle the 3 Erlangs of offered 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-3 summarizes these key results.

Table 2-3 Summary of required resources

BTS Offered traffic(Erlangs)

Blockingprobability (GOS)

Required numberof resources

1 3 1% 8

2 2 2% 6

3 5 1% 11

Total (100% reserved) 10 25

Total (100% common) 10 1% 18

NOTE The offered traffic refers to the amount of traffic arriving at thebackhaul resources. Since the limited number of TCHs gives riseto another level of blocking (GOS), the traffic offered at thebackhaul resources is in general smaller than the trafficgenerated by the subscribers. For example, with 1% blocking atthe TCHs, on average only 99% of the traffic make it to thebackhaul resources. Therefore, the offered (also known asexpected) traffic at the backhaul resources is the product of theoffered traffic from the subscribers and (1 � blocking probability).


30 Sep 2003


68P02900W21-M

GMR-012�39

Note that when the 100% reserved planning approach is used, more resources (25instead of 18) are required and, in addition, BTS 2 is planned at a higher blocking (aworse GOS). This example demonstrates the power of trunking efficiency and the reasonwhy allocation to the common pool should be favoured over allocation to the reservedpool when planning terrestrial backhaul resources for individual BTS sites or cells.

Reserving terrestrial backhaul resources for individual cells, however, does isolate thecell from the statistical traffic fluctuation of other cells. When other cells experiencehigher call arrivals than average, a cell with its own n reserved terrestrial backhaulresources will never be in a situation where all its calls are blocked. The cell isguaranteed 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, somereserved resources may exist by default if 16 kbit/s RSLs are used at the BTS site. The16 kbit/s backhaul resources associated with the same timeslot on the E1/T1 as the16 kbit/s RSL are considered reserved resources for all cells in the BTS site. SupposeBTS 1 and BTS 2 in this example both use one 16 kbit/s RSL and, therefore, each hasthree backhaul resources available by default. Follow Guideline 3 to determine thenumber of resources needed in this situation:

1. For BTS 1, given that it has three reserved resources and 3 Erlangs of offeredtraffic, the calculated blocking probability for the resources is 0.35. Similarly, forBTS 2, three reserved resources handling 2 Erlangs gives a blocking probability of0.21.

2. The traffic overflowed from the reserved resources is 3 x 0.35 = 1.04 Erlangs forBTS 1 and is 2 x 0.21 = 0.42 Erlangs for BTS 2.

3. The total traffic to be handled by the common pool is, therefore, the sum of theoverflow traffic from BTS 1 and BTS 2 and the 5 Erlangs from BTS 3. The sumturns out to be 6.46 Erlangs.

4. Using the Erlang B model, the calculated common pool needs to have 13 backhaulresources in order to meet the 1% GOS.

As a result, a total of 19 resources are needed in this case. Although this approachrequires one more resource than the 100% common allocation approach, six of theresources are available by default. Only 13 additional resources are really needed.

In summary, it has been demonstrated that the 100% reserved approach resulted in lessefficient use of resources and, therefore, required the most number of resources to meetthe design requirements. The 100% common approach resulted in the most efficientutilization of resources. However, if reserved resources are readily available, using theplanning approach given in Guideline 3 can make use of them and reduce the number ofadditional resources needed to be provisioned (see Table 2-4).

Table 2-4 Summary of common pool planning when BTS 1 and 2 have reservedresources

BTS Offeredtraffic

(Erlangs)

Number ofreserved

resources

Blockingprobability

for reserved

Overflowed trafficfrom reserved

(Erlangs)

1 3 3 0.35 1.04

2 2 3 0.21 0.42

3 5 0 � 5

Total = 6.46

Number of resources needed in common pool to meet 1% GOS = 13.

Therefore, the total number of resources, including reserved = 19.


30 Sep 20032�40


GMR-0168P02900W21-M

Example 2

As Example 2 demonstrates, the trunking efficiency gain by the BTS concentrationfeature can be rather significant. To show the advantage in a large system, this examplelooks into the planning of BTS concentration for a daisy chain of 10 single cell BTS sites.Table 2-5 summarizes the offered amount of traffic at the backhaul resources and theGOS requirement associated with each cell.

Table 2-5 Summary of traffic and GOS requirements

BTS Offered traffic(Erlangs)

Blockingprobability (GOS)

Required numberof resources

1 5 1% 11

2 10 1% 18

3 15 1% 24

4 20 1% 30

5 25 1% 36

6 30 1% 42

7 35 1% 47

8 40 1% 53

9 50 1% 64

10 60 1% 75

Total (100% reserved) 290 400

Total (100% common) 290 1% 314

Table 2-5 also shows the results of the 100% reserved and 100% common planningapproaches (the rightmost column). The total traffic load of the 10 BTS sites is290 Erlangs. If each BTS resource allocation is planned as in the static allocation or100% reserved methods (resources are actually reserved for the cell in thecorresponding BTS site, since they are reserved on a per cell basis), the resources thatneed to be planned over the terrestrial backhaul are 400. However, if the resourceallocation is performed over all 10 BTS sites, the number of required terrestrial backhaulresources drops to 314, a saving of 86 resources.

The saving of 86 resources is significant because, without it, the daisy chain would haverequired 400 resources (using the 100% reserved approach) and would not be able to fitinto three E1 links, the most a DYNET can have. Note that three E1 links together canprovide only 372 (= 3 x 31 x 4) 16 kbit/s channels, and, inevitably, some of which will beallocated for 16 and 64 kbit/s RSLs. The 100% common approach of planning BTSconcentration reduces the number of required resources and makes it possible to offer1% blocking to the entire daisy chain with three E1 links.

To expand this example further, assume that each BTS site has some default reservedbackhaul resources ranging from 1 to 3 (see Table 2-3). Following Guideline 3, thecalculation in Table 2-6 shows that about a total of 272 Erlangs of traffic will beoverflowed to the common pool. Therefore, the common pool needs 295 additionalresources in order to provide an 1% GOS, making a total of 315 backhaul resources inthis scenario.


30 Sep 2003


68P02900W21-M

GMR-012�41

Table 2-6 Summary of common pool planning when BTSs have reserved resources

BTS Offeredtraffic

(Erlangs)

Number ofreserved

resources

Blockingprobability

for reserved

Overflowed trafficfrom reserved

(Erlangs)

1 5 3 0.53 2.65

2 10 3 0.73 7.32

3 15 3 0.81 12.21

4 20 2 0.90 18.10

5 25 2 0.92 23.08

6 30 2 0.94 28.07

7 35 2 0.94 33.06

8 40 1 0.98 39.02

9 50 1 0.98 49.02

10 60 1 0.98 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.


30 Sep 20032�42


GMR-0168P02900W21-M

Example 3

This example uses a call blocking situation in a three cell BTS site to illustrate theoperation of BTS concentration. First, the assumptions about the configuration and thestate of the three cell BTS site:

S There are 24 terrestrial backhaul resources (that is six timeslots) in the dynamicpool, 12 of which are in the common pool for assignment to any of the three cellsand the other 12 are reserved as illustrated in Table 2-6.

S All RSLs are 64 kbit/s and, hence, no RSL associated resources.

S Cell 1 has three calls in progress and all three calls are counted against cell 1reserved pool. Cell 1 cannot take any more new calls without getting resourceallocation from the common pool.

S Cell 2 has 17 calls in progress, five of which are counted against cell 2 reservedpool and 12 were counted against the common pool. As a result, the common poolis depleted.

S Cell 3 has three calls in progress, and all three calls are counted against cell 3reserved pool. Cell 3 has the reserved pool capacity to take one more call beforeneeding resources from the common pool.

Suppose a new call arrives to cell 1. Since resources in both cell 1 reserved pool and thecommon pool are in use, the new call attempt will be blocked. This blocking occurs eventhough there is one available resource in the dynamic pool. This remaining resource canonly be allocated to cell 3 since it has not used up its reserved pool (see Table 2-7).

Table 2-7 Blocking activity

BTS New callattempt

Calls inprogress

Reserved poolresources

Resources used outof common pool

1 X 3 3 0

2 17 5 12

3 3 4 0


30 Sep 2003


68P02900W21-M

GMR-012�43

BTS concentration resource optimization for handovers (BCROH)

The BCROH (introduced at GSR5) optimises the terrestrial backhaul between a BSC andBTS during handovers when BTS concentration is applied. Previously when a handoveroccurred, a new circuit for the destination radio channel was always allocated betweenthe BSC and the BTS. The BCROH however, means that if the source and destinationBTS in a handover are the same then a new circuit is not allocated and the existingcircuit is re-used for the radio destination channel.

BCROH description

For the BCROH to operate, BTS concentration (dynamic allocation of BSC to BTScircuits) must be employed. It can, therefore, only be used in conjunction with the BTSequipment that supports BTS concentration.

This reduces the number of resources, (that is, 16 kbit/s backhaul) required when intracell handovers or inter cell handovers (within the same site) occur and are controlled bythe BSC. This means that in these handover scenarios, the switch connections for thevoice traffic from the radio channel to the MSC are no longer made at the BSC during thehandover. The BTS to MSC path remains constant and the BTS must simply move theswitch connection of the Abis circuit from the source radio channel to the destinationradio channel.

Figure 2-29 illustrates BSC controlled intra cell handover (cell A to cell A )with BTSconcentration and BCROH enabled.

Figure 2-29 BSC controlled intra cell handover

BSC

BTS

Radio Channel

In this case the dynamically assigned channelbetween BTS and BSC is re-used for thedestination path. The BTS moves the Abisconnection from the source radio channel to thedestination radio channel.

Mobile is handed over to a new frequency

A

Radio Channel

B

Cell A


30 Sep 20032�44


GMR-0168P02900W21-M

Figure 2-30 illustrates BSC controlled inter cell handover (cell A to cell B) with BTSconcentration and BCROH enabled.

Figure 2-30 BSC controlled inter cell handover

BTS

Cell A Cell B

In this case the dynamically assignedchannel between BTS and BSC is re-usedfor the destination path. The BTS moves theAbis connection from the source radiochannel to the destination radio channel.

BSC

BCROH cannot be applied when:

S If the handover (H/O) is controlled by the MSC, then the BSC BTS link cannotre-use the same resource because a new signalling connection control part SCCPconnection is made. Even if the H/O is intra cell (cell A to cell A) or inter cell (cell Ato cell B) within the same site the resource cannot be reused (when H/O is MSCcontrolled rather than BSC controlled).

S The handover is intra BSC but inter BTS.

The BCROH allows two methods of connecting the radio channel to the Abis (linkbetween a remote BSC and BTS) channel.

NOTE By making the switch connection at the BTS, the connection ismade sooner than a connection made at the BSC, thereforereducing the audio hole.

The database parameter override_intra_bss_pre_transfer indicates whether theconnection is made in two steps or not.


30 Sep 2003


68P02900W21-M

GMR-012�45

Method 1

NOTE This is when the override_intra_bss_pre_transferparameter is enabled.

When the destination channel receives HO detect, the BTS connects the existingAbis circuit to the new destination channel. The connection between the Abiscircuit and the source channel is broken, they are now disconnected (seeFigure 2-31).

Figure 2-31 Method 1 (override_intra_bss_pre_transfer is enabled)

Destination channel

receives HO detect

Abis Abis

SourceChannel

DestinationChannel

SourceChannel

DestinationChannel


30 Sep 20032�46


GMR-0168P02900W21-M

Method 2

NOTE This is when the override_intra_bss_pre_transferparameter is disabled.

S A two step process. When a backing resource is requested for a new channel, thedownlink Abis channel is connected to a destination channel. Then when thedestination channel receives HO detect, the BTS connects the uplink Abis channelto the new destination channel and the Abis circuit and source channel aredisconnected (see Figure 2-32).

Figure 2-32 Method 2 (override_intra_bss_pre_transfer is disabled)

Backing resource isrequested for new

Abis Abis

SourceChannel

DestinationChannel

SourceChannel

DestinationChannel

BTS BTSchannel

Abis

SourceChannel

BTS

DestinationChannel

Destination channelreceives HO detect

STEP 1

STEP 2

GSR6 (Horizon II) Managed HDSL on micro BTSs

30 Sep 2003


68P02900W21-M

GMR-012�47

Managed HDSL on micro BTSs

Introduction

Managed HDSL brings the benefits of full OMC-R management to those products thatsupport integrated HDSL technology. Specifically, it allows remote configuration, status,control, and quality of service information to be handled by the OMC-R. External HDSLmodems configured as slave devices may also be managed by the same mechanism aslong as they are connected to an integrated master HDSL port.

This enables such an HDSL link to be managed entirely from the OMC-R. Followingintroduction of this feature, the initial basic version of the product will no longer besupported.

NOTE Horizonmicro2 microcell BTSs (and Horizoncompact2macrocell BTSs) shipped after 31st December 2001 arenot fitted with an internal HDSL modem. A suitableexternal HDSL modem must be used if a HDSL link to theBSC is required for these BTSs.The local Motorola office can provide assistance prior topurchasing a HDSL modem for this purpose.

GSR6 (Horizon II)Managed HDSL on micro BTSs

30 Sep 20032�48


GMR-0168P02900W21-M

Integrated HDSL interface

HDSL cable selection

The cabling needs to comply with the following selection guidelines:

S Correct number of pairs for an application.

S Each tip and ring pair must be of a twisted construction.

S The tip and ring must not be mixed between the pairs, that is, tip1 must not beused as a pair with ring 2.

S Either unshielded twisted pair (UTP) or shielded twisted pair (STP) may be used.

S The cable gauge should be between 0.4 mm and 0.91 mm (AWG 26 to AWG 19).

S Attenuation at 260 kHz should be less than 10.5 dB/km.

S Cable runs should be limited to a length depending on the product.

Some types of cable are known to perform suitably in HDSL applications, provided theyare correctly installed and the guidelines for selection and installation are observed.Recommendations for types of cable follow:

S Unshielded twisted pair

� BT CW1308 and equivalents.

� Category 3 UTP.

� Category 4 UTP.

� Category 5 UTP.

S Shielded twisted pair

� Category 3 STP.

� Category 4 STP.

� Category 5 STP.

The performance of some types of cable is known to be unacceptable for HDSLapplications. The following cable types should be avoided:

S Twisted quad cable is unsuitable for use in HDSL applications and must not beused.

S Drop wire that consists of two parallel conductors with supporting steel cable. Thiswill work with HDSL but because it is not twisted, it provides little immunity fromnoise, and is therefore not recommended.

S Information cable is typically of non-twisted, multicore construction, for exampleribbon cable. Its use is not recommended.


30 Sep 2003


68P02900W21-M

GMR-012�49

HDSL cable installation

If cabling does not exist between two end sites, guidelines follow for the installation ofcable, that must meet the selection guidelines given above:

S The conductor pair(s) should be connected point-to-point only, not point tomultipoint.

S The use of different gauges of cable in one link should be avoided.

S Bridge taps in the cable run should be avoided.

S Loading coils in the cable run must be removed.

S The isolation between tip and ring should be greater than 1 Mohm (at SELVvoltage levels).

S The isolation between tip and earth should be greater than 1 Mohm (at SELVvoltage levels).

S The isolation between ring and earth should be greater than 1 Mohm (at SELVvoltage levels).

HDSL range

HDSL range is affected by many factors which should be taken into account whenplanning the system.

S Picocell systems should have distances of less than 1 km due to the link qualityrequirements of these systems.

S Microcell systems can have longer distances, typically 2 km or so, because of theirdifferent link error requirements.

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

NOTE However, standard E1 traffic will affect (and be affected by)HDSL systems running in the same cable binder, if unshieldedfrom each other.


30 Sep 20032�50


GMR-0168P02900W21-M

General HDSL guidelines

Conversion of E1 to HDSL at a site away from the BSC requires either an externalmodem or a microsite. It may be better to utilize the microsite to do this conversion, ifpossible (see Figure 2-33).

Figure 2-33 Conversion of E1 to HDSL links by modem and microsite

BSC

EXTERNALMODEM

M

M = MASTER S = SLAVE

EXTERNALMODEM

E1 LINK HDSL

HDSL

HDSL

E1 LINK

E1 LINK

Horizonmacro

SLAVE

MSLAVE

S M S M M

M SM SHDSL

HDSL

HDSL

E1 LINK

E1 LINK

BTS

Horizonmicro2

Horizonmicro2 Horizonmicro2 Horizonmicro2


Microcell BTSs have a maximum of two 2.048 Mbit/s links. If the HDSL equipped versionis purchased (not available for Horizonmicro2 after December 2001), the links areautomatically configured as either E1 or HDSL via a combination of database settingsand auto-detection mechanisms. The setting of master/slave defaults can be changed bydatabase settings for those scenarios, such as a closed loop daisy chain, where thedefaults are not appropriate.


30 Sep 2003


68P02900W21-M

GMR-012�51

Microcell system planning

Network configurations from the BSC can be a combination of daisy chain and star.

Links can be either E1 or HDSL, and can be mixed as appropriate within the network.

Daisy chain

Figure 2-34 shows a BSC connected to an external modem which then connects from itsslave port to the master port of the Horizonmicro2. The slave port of the Horizonmicro2connects to the next Horizonmicro2 master port and so on, until the last Horizonmicro2port is connected.

Figure 2-34 Microcell daisy chain network configuration


EXTERNALMODEM

HDSLMSLAVE MS MSBSC

HDSL HDSLE1 LINK


Star configuration

Figure 2-35 shows a BSC which is again connected to an external modem, which thenconnects from its slave port to the master port of a Horizonmicro2. In this configurationan external modem is used every time a link to a Horizonmicro2 is used, hence the starformation.

Figure 2-35 Microcell star network configuration

BSC

EXTERNALMODEM

M

M = MASTER

EXTERNALMODEM

M

EXTERNALMODEM

MSLAVE

E1 LINK HDSL

HDSL

HDSL

E1 LINK

E1 LINK

SLAVE

SLAVE

Horizonmicro2

Horizonmicro2

Horizonmicro2


30 Sep 20032�52


GMR-0168P02900W21-M

E1 link

In Figure 2-36 an E1 link is used from the BSC to the first Horizonmicro2. From thereonwards HDSL links are used running from master to slave in each Horizonmicro2, orconversion can be at any BTS, in either direction.

Figure 2-36 Microcell configuration using E1/HDSL links


M S MS

BSC

E1 LINK HDSLHDSL



30 Sep 2003


68P02900W21-M

GMR-012�53

Picocell system planning

M-Cellaccess

The M-Cellaccess picocell system comprises a cabinet housing a maximum of two sitecontrollers (see Figure 2-37). These can each control up to six single carrier PicocellControl Units (PCUs) which operate in all frequency bands that adopt the GSM standard(GSM900 and DCS1800).

Figure 2-37 M-Cellaccess picocell system

PCU

BSU

PCC CABINET SITE B

SITE A

BSU

PCU

PCU

PCU

PCU

PCU

PCU

PCU

PCU

PCU

PCU

PCU

The considerations for M-Cellaccess picocell planning are:

S Links are all point to point.

S Run from site controller to the remote RF head.

S Frequency bands must not be mixed on the same site controller.

S Can be either optical of HDSL.

S If HDSL, two twisted pairs of wires for each RF head.

NOTE Daisy chaining of RF heads is not allowed.


30 Sep 20032�54


GMR-0168P02900W21-M

30 Sep 2003


68P02900W21-M

GMR-013�1

Chapter 3

BSS cell planning

GSR6 (Horizon II)

30 Sep 20033�2


GMR-0168P02900W21-M

GSR6 (Horizon II) BSS cell planning

30 Sep 2003


68P02900W21-M

GMR-013�3

BSS cell planning

BSS planning requirements

When planning a mobile telephone system, the aim is to create a communicationsnetwork that fulfils the following requirements:

S Provides the desired capacity.

S Offers good frequency efficiency.

S Implemented at low cost.

S High grade of service.

These requirements, when analyzed, actually conflict with one another. Therefore theoperating network is always a solution achieved through compromise.

The cost of different network configurations can vary considerably. From an engineeringpoint of view it would be worth while using the most frequency efficient solutions despitetheir high cost, but a mobile telephone network is so huge an investment that thefinancial factors are always going to limit the possibilities. The effect of limited funds isparticularly 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, EGSM900 and DCS1800 frequency bands create manypropagation based problems. Because the channel characteristics are not fixed, theypresent design challenges and impairments that must be dealt with to protect MStelephone users from experiencing excessively varying signal levels and lack of voicequality.

It is important to be able to predict the RF path loss between the BTS and the MS withinthe coverage area in different types of environment. To do this it is necessary to haveknowledge of the transmitter and receiver antenna heights, the nature of the environmentand the terrain variations.

GSR6 (Horizon II)BSS cell planning

30 Sep 20033�4


GMR-0168P02900W21-M

Planning factors

When planning a network there are a number of major factors which must be consideredto enable the overall system requirements to be met:

S Using available planning tools.

S Modulation techniques and channel spacing in the GSM frequency spectrum.

S Traffic capacity.

S Propagation effects on GSM frequencies.

S Frequency re-use.

S Overcoming adverse propagation effects.

S The subscriber environment.

S Using a microcellular solution.

S Frequency planning.

S 2G to 3G handovers.

S Making capacity calculations.

S Making control channel calculations.

S Planning for GPRS traffic.

S Estimating GPRS network traffic.

S Planning the GPRS air interface.

GSR6 (Horizon II) Planning tools

30 Sep 2003


68P02900W21-M

GMR-013�5

Planning tools

Introduction

In order to predict the signal strength in a cell area it would be necessary to make manycalculations, at regular intervals, from the BTS. The smaller the interval the moreaccurate the propagation model. Also the calculations would need to be performed atregular distances along each radial arm from the BTS, to map the signal strength as afunction of distance from the BTS.

The result, is the necessity to perform hundreds of calculations for each cell. This wouldbe 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 Type of terrain.

S Environment.

S Heights of antennas.

It can perform the necessary number of calculations needed to give an accurate pictureof the propagation paths of the cell.

Several planning tools are available on the market, such as Netplan or Planet, and it isup 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 bypractical measurements. This is because, with all the variable factors in propagationmodelling, an accuracy of 80% would be considered excellent.

GSR6 (Horizon II)GSM frequency spectrum

30 Sep 20033�6


GMR-0168P02900W21-M

GSM frequency spectrum

The GSM900 frequency spectrum

The original GSM frequency spectrum was allocated in 1979. This consisted of twosub-bands 25 MHz wide. The frequency range is:

Uplink range 890 MHz to 915 MHz.

Downlink range 935 MHz to 960 MHz.

It is usual for the uplink frequencies � mobiles transmitting to the BTS � to be on thelowest frequency band . This is because there is a lower free space path loss for lowerfrequencies. This is more advantageous to the mobile as it has a reduced transmit outputpower capability compared to the BTS.

The two bands are divided into channels, a channel from each band is then paired withone of the pair allocated for uplink and one for the downlink. Each sub-band is dividedinto 124 channels, these are then given a number known as the Absolute RadioFrequency Channel Number (ARFCN). So a mobile allocated an ARFCN will have onefrequency to transmit on and one to receive on. The frequency spacing between the pairis always 45 MHz for GSM. The spacing between individual channels is 200 kHz and atthe beginning of each range is a guard band. It can be calculated that this will leave 124ARFCNs for allocation to the various network operators. These ARFCNs are numbered 1to 124 inclusive

To provide for future network expansion more frequencies were allocated to GSM as theybecame available. An extra 10 MHz was added on to the two GSM bands and thisbecame known as Extended GSM (EGSM). The EGSM frequency range is:

Uplink range 880 MHz � 915 MHz.

Downlink range 925 MHz � 960 MHz.

This allows another 50 ARFCNs to be used, bringing the total to 174. These additionalARFCNs are numbered 975 to 1023 inclusive.

One thing to note is that original Phase 1 MSs can only work with the original GSMfrequency 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 ofPhase 2 MS, care must be taken when using EGSM frequencies not to make holes in thenetwork for Phase 1 MSs.

GSR6 (Horizon II) GSM frequency spectrum

30 Sep 2003


68P02900W21-M

GMR-013�7

The DCS1800 frequency spectrum

As GSM evolved it was decided to apply the technology to the Personal CommunicationsNetworks. This required changes to the air interface to modify the frequency range overwhich it operates. The modified frequency range is:

Uplink range 1710 MHz � 1785 MHz.

Downlink range 1805 MHz � 1880 MHz.

This provides 374 ARFCNs with a frequency separation of 95 MHz between uplink anddownlink frequencies.

In the UK these ARFCNs have been shared out between the four network operators (seeFigure 3-1). Two of these, Orange and One to One operate exclusively in the DCS1800range while the other two, Vodafone and Cellnet have been allocated DCS1800channels on top of their GSM900 networks. ARFCNs are numbered from 512 to 885inclusive

The part at the top of the band is used by Digital Enhanced Cordless Telephony (DECT).

Figure 3-1 UK network operators

DECT

Orange

One � 2 � One

Vodafone/Cellnet

DownlinkUplink

1785MHz

1781.5MHz

1721.5MHz

1710MHz

1880MHz

1876.5MHz

1816.5MHz

1805MHz

DECT

Orange

One � 2 � One

Vodafone/Cellnet

GSR6 (Horizon II)GSM frequency spectrum

30 Sep 20033�8


GMR-0168P02900W21-M

Absolute radio frequency channel capacity

Each RF carrier supports eight time division multiplexed physical channels and each ofthese is capable of supporting speech or signalling information (see Figure 3-2).

The maximum number of RF carriers at any one BTS site is 24 for Horizon II macro,Horizonmacro and M-Cell6, and 25 for BTS6. Therefore the maximum number ofphysical channels available at a BTS site is 24 x 8 = 192 for Horizon II macro,Horizonmacro and M-Cell6, and 25 x 8 = 200 for BTS6.

Figure 3-2 Eight TDMA timeslots per RF carrier

BTS Maximum 24 carriers forHorizonmacro and M-Cell6

Maximum 25 carriers for BTS6

72 410 653

GSR6 (Horizon II) GSM frequency spectrum

30 Sep 2003


68P02900W21-M

GMR-013�9

Modulation techniques and channel spacing

The modulation technique used in GSM is Gaussian minimum shift keying (GMSK). Thisworks by shaping the data to be modulated with a Gaussian filter. The filter removessome of the harmonics from the data square wave producing a more rounded shape.When this is applied to a phase modulator the result is a modified envelope shape at theoutput of the modulator. The bandwidth of this envelope is narrower than that of acomparable one produced from non-filtered data. With each modulating carrier occupyinga narrower bandwidth, more efficient use can be made of the overall bandwidth available.

The bandwidth allocated to each carrier frequency in GSM is 200 kHz. The actualbandwidth occupied by a transmitted GSM carrier is far greater than 200 kHz, even withGaussian filtering. The signal therefore overlaps into surrounding frequencies, asillustrated in Figure 3-3.

Figure 3-3 Modulation techniques and channel spacing

CHANNEL 1 CHANNEL 2 CHANNEL 3

200 kHz

�10 dB POINT

0

�10

�20

�30

�40

�50�60

�70

dB

If two carriers from the same or adjacent cells are allocated adjacent frequencies orchannel numbers they will interfere with each other because of the describedoverlapping. This interference is unwanted signal noise. All noise is cumulative, sostarting with a large amount by using adjacent channels our wanted signal will soondeteriorate below the required quality standard. For this reason adjacent frequenciesshould never be allocated to carriers in the same or adjacent cells.

Figure 3-3 illustrates the fact that the actual bandwidth of a GMSK modulated signal isconsiderably wider than the 200 kHz channel spacing specified by GSM. At the channeloverlap point the signal strength of the adjacent channel is only �10 dB below that of thewanted signal. While this just falls within the minimum carrier to interference ratio of 9 dB,it is not insignificant and must be planned around so that allocation of adjacentfrequencies in adjacent cells never occurs.

One other consideration about channel spacing that must be considered is when usingcombiners. If a cavity combining block is used, the frequencies for combining must beseparated by at least three ARFCNs otherwise it could cause intermodulation productsand spurious frequency generation. These could interfere with other carriers further awayin the radio spectrum, possibly in adjacent cells, so they would not necessarily be aproblem to the home cell so the source of interference becomes more difficult to locate.

GSR6 (Horizon II)Traffic capacity

30 Sep 20033�10


GMR-0168P02900W21-M

Traffic capacity

Dimensioning

One of the most important steps in cellular planning is system dimensioning. Todimension a system correctly and hence all the supporting infrastructure, some idea ofthe projected usage of the system must be obtained (for example, the number of peoplewishing to use the system simultaneously). This means traffic engineering.

Consider a cell with N voice channels; the cell is therefore capable of carrying Nindividual simultaneous calls. The traffic flow can be defined as the average number ofconcurrent calls carried in the cell. The unit of traffic intensity is the Erlang; traffic definedin this way can be thought of as a measure of the voice load carried by the cell. Themaximum carried traffic in a cell is N Erlangs, which occurs when there is a call on eachvoice channel all of the time.

If during a time period T (seconds), a channel carries traffic is busy for t (seconds), thenthe average carried traffic, in Erlangs, is t/T. The total traffic carried by the cell is the sumof the traffic carried by each channel. The mean call holding time is the average time achannel is serving a call.

GSR6 (Horizon II) Traffic capacity

30 Sep 2003


68P02900W21-M

GMR-013�11

Channel blocking

The standard model used to dimension a system is the Erlang B model, which modelsthe number of traffic channels or trunks required or a given grade of service and givenoffered traffic. There will be times when a call request is made and all channels or trunksare in use, this call is then blocked. The probability of this happening is the grade ofservice of the cell. If blocking occurs then the carried traffic will be less than the offeredtraffic. 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 hadbeen an absence of blocking. Because of this effect the notion of offered traffic issomewhat confused, however, if the blocking probability is small, it is reasonable toignore 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. Thereare usually two peaks during week days, although the pattern can change from day today. Across the typical day the variation is such that a one hour period shows greaterusage than any other. From the hour with the least traffic to the hour with the greatesttraffic, the variation can exceed 100:1.

To add to these fairly regular variations, there can also be unpredictable peaks caused bya wide variety of events (for example; the weather, natural disasters, conventions, sportsevents). In addition to this, system growth must also be taken into account. There are aset of common definitions to describe this busy hour traffic loading.

Busy Hour: The busy hour is a continuous period during which traffic volume or numberof call attempts is the greatest.

Peak Busy Hour: The busy hour each day it is not usually the same over a number ofdays.

Time Constant Busy Hour: The one hour period starting at the same time each day forwhich the average traffic volume or call attempts count is greatest over the days underconsideration.

Busy Season Busy Hour: The engineering period where the grade of service criteria isapplied 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 fortrunk groups and always has a grade of service criteria applied. For example, for theAverage Busy Season Busy Hour load, a call requiring a circuit in a trunk group shouldnot 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 andswitching equipment.

GSR6 (Horizon II)Traffic capacity

30 Sep 20033�12


GMR-0168P02900W21-M

Traffic flow

If mobile traffic is defined as the aggregate number of MS calls (C) in a cell with regard tothe duration of the calls (T) as well as their number, then traffic flow (A) can be definedas:

Traffic Flow (A) = C x T

Where: C is: the calling rate per hour.

T the average holding time per call.

Suppose an average hold time of 1.5 minutes is assumed and the calling rate in the busyhour 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 ofthat particular traffic channel.

Considering a group of traffic channels, the traffic intensity in Erlangs is the number ofcall-seconds per second or the number of call-hours per hour. As an example; if therewere a group of 10 traffic channels which had a call intensity of 5 Erlangs, then half of thecircuits 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 insetting up a call (blocking). Blocking data states what grade of service is required and isgiven as a percentage of the time that the subscriber is unable to make a call. Typicalblocking for the MS�BSC link is 2% with 1% being acceptable on the BSC�MSC link.There is a direct relationship between the grade of service required and the number ofchannels. The customers desired grade of service has a direct effect on the number ofchannels needed in the network.

GSR6 (Horizon II) Propagation effects on GSM frequencies

30 Sep 2003


68P02900W21-M

GMR-013�13

Propagation effects on GSM frequencies

Propagation production

Most of the methods used to predict propagation over irregular terrain are actually terrainbased, since they are designed to compute the diffraction loss and free space loss basedupon the path profile between the transmitter and the receiver. A widely used techniquein the United Kingdom is the prediction method used by the Joint Radio Committee (JRC)of the Nationalized Power Industries. This method utilizes a computerized topographicalmap in a data base, providing some 800,000 height reference points at 0.5 km intervalscovering the whole of the UK. The computer predicts the received signal level byconstructing the ground path profile between the transmitter and receiver using the database. The computer then tests the path profile for a line of sight path and whetherFresnel zone clearance is obtained over the path. The free space and plane earthpropagation losses are calculated and the higher value is chosen. If the line of sight andFresnel-zone clearance test fails, then the programme evaluates the loss caused by anyobstructions and grades them into single or multiple diffraction edges. However, thismethod fails to take any buildings into account when performing its calculation, thecalculations are totally based upon the terrain features.

Although the use of topographical based calculations are useful when designing mobilecommunication systems, most mobile systems are centred around urban environments.In these urban environments, the path between transmitter and the receiver maybeblocked by a number of obstacles (buildings for example), so it is necessary to resort toapproximate methods of calculating diffraction losses since exact calculations for eachobstacle then become extremely difficult.

GSR6 (Horizon II)Propagation effects on GSM frequencies

30 Sep 20033�14


GMR-0168P02900W21-M

DecibelsThe decibel (dB) is used to express power output levels, receiver input levels and pathlosses and enables calculations used when planning radio systems to be simplified. Anynumber may be expressed as a decibel. The only requirement is that the originaldescription and unit scale is appended to the dB, so indicating a value which can be usedwhen adding, subtracting, or converting decibels.

For example, for a given power of 1 mW it may be expressed as 0 dBm, the m refers tothe fact that the original scale of measurement was in thousandths of a watt (milliwatts).For a power of 1 W the equivalent in dB is 0 dBW.

The decibel scale is logarithmic and this allows very large or very small numbers to bemore easily expressed and calculated. For example take a power of 20 watts transmittedfrom a BTS which was .000000001 W at the receiver. It is very difficult to accuratelyexpress the total power loss in a simple way. By converting both figures to decibelsreferenced to 1 mW, 20 W becomes 32 dBm and .000000001 W is �60 dBm. The pathloss can now be expressed as 92 dBm.

Multiplication and division also become easier when using decibels. Multiplication simplyrequires adding the dB figures together, while division simply requires subtracting one dBfigure from the other. Another example is for every doubling of power figures, theincrease is 3 dB and for every halving of power the decrease is 3 dB. Table 3-1 givesexamples of dB conversions.

The basic equation used to derive power (dB) from power (W) is:

N dB = 10 x log10(PL/RPL)

Where: NPLRPL

is: the required power level in dB.the power level being converted.the reference power level.

Table 3-1 dBm and dBW to power conversion

dBm dBW Power dBm dBW Power dBm dBW Power

+59 29 800 W + 24 �6 250 mW �9 �39 0.125 mW

+56 26 400 W + 21 �9 125 mW �10 �40 0.1 mW

+53 23 200 W + 20 �10 100 mW �20 �50 0.01 mW

+50 20 100 W +17 �13 50 mW �30 �60 1 mW

+49 19 80 W +14 �16 25 mW �40 �70 0.1 mW

+46 16 40 W +11 �19 12.5 mW �50 �80 0.01 mW

+43 13 20 W +10 �20 10 mW �60 �90 1 nW

+40 10 10 W +7 �23 5 mW �70 �100 0.1 nW

+39 9 8 W +4 �26 2.5 mW �80 �110 0.01 nW

+36 6 4 W +1 �29 1.25 mW �90 �120 1 pW

+33 3 2 W 0 ** �30 1 mW �100 �130 0.1 pW

+30 0 * 1 W �3 �33 0.5 mW �110 �140 0.01 pW

+27 �3 500 mW �6 �36 0.25 mW �120 �150 0.001 pW

***

1 W reference value.1 mW reference value.

Note that the reference value is normally measured across a 50 ohm non reactive load.


30 Sep 2003


68P02900W21-M

GMR-013�15

Fresnel zone

The Fresnel zone actually consists of several different zones, each one forming anellipsoid around the major axis of the direct propagation path. Each zone describes aspecific area depending on the wavelength of the signal frequency. If a signal from thatzone is reflected of an obstacle which protrudes into the zone, it means that a reflectedsignal as well as the direct path signal will arrive at the receiver. Radio waves reflected inthe first Fresnel zone will arrive at the receiver out of phase with those taking the directpath and so combine destructively. This results in a very low received signal strength. Itis important when planning a cell to consider all the radio paths for obstacles which mayproduce reflections from the first Fresnel zone because if they exist it is like planningpermanent areas of no coverage in certain parts of the cell.

In order to calculate whether or not this condition exists, the radius of the first Fresnelzone at the point where the object is suspected of intruding into the zone must becalculated. The formula, illustrated in Figure 3-4, is as follows:

F1 � d1 � d2� � ld

Where: F1 is: the first Fresnel zone.

d1 distance from Tx antenna to the obstacle.

d2 distance from Rx antenna to the obstacle.

l wavelength of the carrier wave.

d total path length.

Figure 3-4 First Fresnel zone radius calculation

d1 d2

d

FREQUENCY = 900 MHzWAVELENGTH = 30 cm

F1

Once the cell coverage has been calculated the radio path can be checked for anyobjects 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 bestclearance 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 andheight of the antenna to ensure that the roof edge of the building does not intrude into thefirst Fresnel zone.


30 Sep 20033�16


GMR-0168P02900W21-M

Radio refractive index (RRI)It is important when planning a cell or microwave radio link to have an understanding ofthe effects changes in the RRI can have on microwave communications, also whatcauses these changes.

RRI measurements provide planners with information on how much a radio wave will berefracted by the atmosphere at various heights above sea level. Refraction (seeFigure 3-5) is the changing of direction of propagation of the radio wave as it passes froma more dense layer of the atmosphere to a less dense layer, which is usual as oneincreases in height above sea level. It also occurs when passing from a less dense layerto a more dense layer. This may also occur under certain conditions, even at higheraltitudes.

Figure 3-5 Refraction

REFRACTION OCCURS AS THE RADIO WAVE PASSES THROUGHLAYERS OF DIFFERENT ATMOSPHERIC DENSITY

EARTH

The main effect to cell planners is that changes in the RRI can increase or decrease thecell 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 seasonsand location but for the UK the mean value is 1.00034. This figure is very cumbersome towork with so convention has converted n to N.

Where: N is: (n�1) x 106.

The value of N now becomes 340 units for the UK. The actual seasonal and globalvariations are only a few tens of units at sea level.

The value of N is influenced by the following:

S The proportion of principal gasses in the atmosphere such as nitrogen, oxygen,carbon dioxide, and rare gasses. These maintain a near constant relationship asheight is increased so although they affect the RRI the affect does not vary.

S The quantity of water vapour in the atmosphere. This is extremely variable and hassignificant effects on the RRI.

S Finally the temperature, pressure, and water vapour pressure have major effectson the RRI.

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 mixedatmosphere the RRI will fall by 40 N units per 1 km increase in height above sea level.


30 Sep 2003


68P02900W21-M

GMR-013�17

Measurement of the RRI

There are two main ways of measuring the RRI at any moment in time. Firstly by use ofRadio Sonds. This is an instrument which is released into the atmosphere, normallyattached to a balloon. As it rises it measures the temperature, pressure and humidity.These are transmitted back to the ground station with a suitable reference value. Themeasurements of pressure are made every 35 m, humidity every 25 m, and temperatureevery 10 m. These together provide a relatively crude picture of what the value of theRRI is over a range of heights.

The second method is a more sophisticated means of measuring the RRI. It uses fastresponse devices called refractometers. These may be carried by a balloon , aircraft, orbe spaced apart on a high tower. These instruments are based upon the change inresonant frequency of a cavity with partially open ends caused by the change in RRI ofair passing through the cavity. This gives a finer measurement showing variations in theRRI over height differences of a little over one metre. This is illustrated by the graph inFigure 3-6. The aircraft mounted refractometer can give a detailed study over severalpaths and heights.

Figure 3-6 Measurement of the RRI

RRI (N)

340

HEIGHT (km)

1

0


30 Sep 20033�18


GMR-0168P02900W21-M

Effects of deviations from the normal lapse rate

The lapse rate of 40 N per km is based on clear sky readings with good atmospheremixing. Normally a radio system is calibrated during these conditions and the heightalignment in the case of a microwave point to point link is determined.

It is easier to see the effects on a microwave point to point system when examining theeffects of uneven variations of the RRI. Figure 3-7A shows an exaggerated curved radiopath between two antennas under normal conditions. The signal is refracted by theatmosphere and arrives at the receiving antenna.

Figure 3-7B illustrates the condition known as super refraction. This is where the RRIincreases greater than 40 N per km. This results in the path being refracted too muchand not arriving at the receive antenna. While this will not cause any interference (as withsub refraction) it could result in areas of no coverage.

Figure 3-7C illustrates the condition known as sub refraction, where the radio waves arenot diffracted enough. This occurs when the lapse rate is less than 40 N per km. Underthese conditions the main signal path will miss the receive antenna. Similar effects on acell would increase the cell size as the radio waves would be propagated further resultingin co-channel and adjacent channel interference.

Figure 3-7 Refraction effects on a microwave system

NORMAL REFRACTIONEARTH

SUPER REFRACTION

SUB-REFRACTION

A

C

B

EARTH

EARTH

The last effect is known as ducting and occurs when the refraction of the radio waveproduces a path which matches the curvature of the Earth. If this happens radio wavesare propagated over far greater distances than normal and can produce interference inplaces not normally subjected to any.


30 Sep 2003


68P02900W21-M

GMR-013�19

Events which can modify the clear sky lapse rate

There are four main events which can modify the clear sky lapse rate and they are asfollows:

S Radiation nights

This is the result of a very sunny day followed by clear skies overnight. The Earthabsorbs heat during the day and the air temperature rises. After sunset the Earthradiates heat into the atmosphere and its surface temperature drops. This heat loss isnot replaced resulting in air closer to the surface cooling faster than air higher up. Thiscondition causes a temperature inversion and the RRI profile no longer has a uniformlapse rate. This effect will only occur overland and not water as water temperaturevariations are over a longer period of time.

S Advection effects

This effect is caused by high pressure weather fronts moving from land to the sea orother large expanses of water. The result is warm air from the high pressure frontcovering the relatively cool air of the water. When this combination is then blown backover land a temperature inversion is caused by the trapped cool air. It will persist until theair mass strikes high ground where the increase in height will mix and dissipate theinversion.

S Subsidence

This occurs again in a high pressure system this time overland when air descending fromhigh altitude is heated by compression as it descends. This heated air then spreads overthe cooler air below. This type of temperature inversion normally occurs at an altitude of1 km but may occasionally drop to 100 m where it cause severe disruption to radiosignals.

S Frontal systems

This happens when a cold front approaching an area forces a wedge of cold air under thewarmer air causing a temperature inversion. These disturbances tend to be short lived asthe cold front usually dissipate quickly.

Although those described above are the four main causes of RRI deviations, localpressure, humidity and temperature conditions could well give rise to events which willaffect the RRI.


30 Sep 20033�20


GMR-0168P02900W21-M

Environmental effects on propagation At the frequency range used for GSM it is important to consider the effects that objectsin the path of the radio wave will have on it. As the wave length is approximately 30 cmfor GSM900 and 15 cm for DCS1800, most objects in the path will have some effect onthe signal. Such things as vehicles, buildings, office fittings even people and animals willall affect the radio wave in one way or another.

The main effects can be summarized as follows:

S Attenuation.

S Reflection.

S Scattering.

S Diffraction.

S Polarization changes.

Attenuation

This is caused by any object obstructing the wave path causing absorption of the signal(see Figure 3-8). The effects are quite significant at GSM frequencies but still depend onthe 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.

Figure 3-8 Attenuation

OBJECTABSORBS

THEENERGYIN THERADIOWAVE

OUTGOING WAVEATTENUATED BY THE OBJECT

INCOMING WAVE

Reflection

This is caused when the radio wave strikes a relatively smooth conducting surface. Thewave is reflected at the same angle at which it arrived (see Figure 3-9). The strength ofthe reflected signal depends on how well the reflector conducts. The greater theconductivity the stronger the reflected wave. This explains why sea water is a betterreflector than sand.

Figure 3-9 Reflection

INCIDENT WAVE

EQUAL ANGLES

REFLECTED WAVE

AMOUNT OF REFLECTION DEPENDS ONCONDUCTIVITY OF THE SURFACE

SMOOTH SURFACE, SUCH AS WATER,VERY REFLECTIVE


30 Sep 2003


68P02900W21-M

GMR-013�21

ScatteringThis occurs when a wave reflects of a rough surface (see Figure 3-10). The rougher thesurface and the relationship between the size of the objects and the wave length willdetermine the amount of scattering that occurs.

Figure 3-10 Scattering

ROUGH STONY GROUND

INCIDENT WAVEENERGY IS

SCATTERED

Diffraction

Diffraction is where a radio wave is bent off its normal path. This happens when the radiowave passes over an edge, such as that of a building roof or at street level that of acorner of a building (see Figure 3-11). The amount of diffraction that takes placeincreases as the frequency used is increased.

Diffraction can be a good thing as it allows radio signals to reach areas where they wouldnot normally be propagated.

Figure 3-11 Diffraction

PLAN VIEW

MICRO BTS ATSTREET LEVEL

DIFFRACTED WAVE GIVINGCOVERAGE AROUND THE CORNER

DIFFRACTED WAVE GIVINGCOVERAGE AROUND THE CORNER

SIDE VIEW

EXPECTED PATH

DIFFRACTEDWAVE

SHADOWAREA


30 Sep 20033�22


GMR-0168P02900W21-M

Polarization changes

This can happen any time with any of the above effects of due to atmospheric conditionsand geomagnetic effects such as the solar wind striking the earths atmosphere. Thesepolarisation changes mean that a signal may arrive at the receiver with a differentpolarisation than that which the antenna has been designed to accept. If this occurs thereceived signal will be greatly attenuated by the antenna.

Figure 3-12 shows the effects of polarization on a transmitted signal.

Figure 3-12 Polarization

ELECTRICAL PART OF WAVEVERTICALLY POLARIZED

ÎÎÎÎÎÎ

ÎÎÎÎÎÎ

ÎÎÎÎÎÎ

ÎÎÎÎÎÎ

ÎÎÎÎÎÎ

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

ELECTRICAL PART OF WAVEHORIZONTALLY POLARIZED

(CHANGED BY ELECTRICAL STORM)

ELECTRICAL STORM

Tx Rx


30 Sep 2003


68P02900W21-M

GMR-013�23

Multipath propagation

Rayleigh and Rician fading

As a result of the propagation effects on the transmitted signal, the receiver will pick upthe same signal which has been reflected from many different objects resulting in what isknown as multipath reception. The signals arriving from the different paths will all havetravelled different distances and will therefore arrive at the receiver at different times withdifferent signal strengths. Because of the reception time difference the signals may ormay not be in phase with each other. The result is that some will combine constructivelyresulting in a gain of signal strength while others will combine destructively resulting in aloss of signal strength.

The receiving antenna does not have to be moved very far for the signal strength to varyby many tens of decibels. For GSM900, a move of just 15 cm or half a wavelength willsuffice to observe a change in signal strength. This effect is known as multipath fading. Itis typically experienced in urban areas where there are lots of buildings and the onlysignals received are from reflections and refractions of the original signal.


30 Sep 20033�24


GMR-0168P02900W21-M

Rayleigh environment

This type of environment has been described by Rayleigh. He analysed the signalstrength along a path with a moving receiver and plotted a graph of the typical signalstrength measured due to multipath fading. The plot is specifically for non line of sight(see Figure 3-13) and is known as Rayleigh distribution (see Figure 3-14).

Figure 3-13 Propagation effect � Rayleigh fading environment

Rx

Tx

Figure 3-14 Rayleigh distribution

SIGNALSTRENGTH

DEEP NULLS � 1/2 WAVELENGTH

THRESHOLD

DISTANCE


30 Sep 2003


68P02900W21-M

GMR-013�25

Rician environment

Where the signal path is predominantly line of sight (see Figure 3-15) with insignificantreflections or diffractions arriving at the receiver, this is know as Rician distribution (seeFigure 3-16). There are still fades in signal strength but they rarely dip below thethreshold below which they will not be processed by the receiver.

Figure 3-15 Propagation effect � Rician environment

Rx

Tx

Figure 3-16 Rician distribution

SIGNALSTRENGTH

THRESHOLD

DISTANCE

Comparison of DCS1800 and GSM900

From a pure frequency point of view it would be true to say that DCS1800 generally hasmore fades than GSM900. However, they are usually less pronounced.


30 Sep 20033�26


GMR-0168P02900W21-M

Receive signal strength

A moving vehicle in an urban environment seldom has a direct line of sight path to thebase station. The propagation path contains many obstacles in the form of buildings,other structures and even other vehicles. Because there is no unique propagation pathbetween transmitter and receiver, the instantaneous field strength at the MS and BTSexhibits a highly variable structure.

The received signal at the mobile is the net result of many waves that arrive via multiplepaths formed by diffraction and scattering. The amplitudes, phase and angle of arrival ofthe waves are random and the short term statistics of the resultant signal envelopeapproximate a Rayleigh distribution.

Should a microcell be employed where part of a cell coverage area is predominantly lineof sight, then Rician distribution will be exhibited.

Free space loss

This is the loss of signal strength that occurs as the radio waves are propagated throughfree space. Free space is defined as the condition where there are no sources ofreflection in the signal path. This is impossible to achieve in reality but it does give a goodstarting point for all propagation loss calculations.

Equally important in establishing path losses is the effect that the devices radiating thesignal have on the signal itself. As a basis for the calculation it is assumed the device isan isotropic radiator. This is a theoretical pin point antenna which radiates equally inevery direction. If the device was placed in the middle of a sphere it would illuminated theentire inner surface with an equal field strength.

In order to find out what the power is covering the sphere, the following formula is used:

P � Pt4 p� d2

Where: Pt is: the input power to the isotropic antenna.

d the distance from the radiator to thesurface of the sphere.

This formula illustrates the inverse square law that the power decreases with the squareof the distance.

In order to work out the power received at a normal antenna, the effective aperture (Ae)of the receiving antenna must be calculated.

Ae � l2

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 asphere and Ae with its formula, the result is:

Pr � � Pt4 p� d2

�� l2

4 p


30 Sep 2003


68P02900W21-M

GMR-013�27

Free space path loss

This is the ratio of the actual received power to the transmitted power from an isotropicradiator and can be calculated by the formula:

Free space loss in dB � 20 log �4 p� dl�

Logs are used to to make the figures more manageable. Note that the formula isdependant on distance and frequency. The higher the frequency the shorter thewavelength, and therefore the greater the path loss.

The formula above is based on units measured in metres. To make the formula moreconvenient, it can be modified to use kilometre and megahertz for the distance andfrequency. It becomes:

Free space loss � 32 � 20 log d � 20 log f dB

Where: d is: the distance in km.

f the frequency in MHz.

Plane earth loss

The free space loss as stated is based solely on a theoretical model and is of no use byitself when calculating the path loss in a multipath environment. To provide a morerealistic model, the earth in its role as a reflector of signals must be taken into account.When calculating the plane earth loss the model assumes that the signal arriving at thereceiver consists of a direct path component and a reflective path component. Togetherthese are often called the space wave.

The formula for calculating the plane earth loss is:

L � 20 log � d2

h1 � h2� dB

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 isimplies the inverse fourth law as opposed to the inverse square law. So, for everydoubling of distance there is a 12 dB loss instead of 6 dB, as with the free space losscalculation.

The final factors in path loss are the ground characteristics. These will increase the pathloss even further depending on the type of terrain (refer to Figure 3-17). The earthcharacteristics can be divided into three groups:

1. Excellent earth. For example sea water, this provides the least attenuation, so alower path loss.

2. Good earth. For example rich agricultural land, moist loamy lowland and forests.

3. Poor earth. For example industrial or urban areas, rocky land. These give thehighest losses and are typically found when planning urban cells.


30 Sep 20033�28


GMR-0168P02900W21-M

Figure 3-17 illustrates plane earth loss, taking all factors into account.

Figure 3-17 Plane earth loss

PATH LOSS INCREASES 6 dB FOR A DOUBLING OF d.

1d

FREE SPACE LOSSTx Rx

PLANE EARTH LOSS INCLUDES ONE EARTH REFLECTOR.PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d.

2

d

Tx

Rx

h1

h2

PLANE EARTH + CORRECTION FACTOR FOR TYPE OF TERRAIN.PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d + A FACTORFOR TYPE OF TERRAIN.

3

d

Tx

Rx

h1

h2


30 Sep 2003


68P02900W21-M

GMR-013�29

Clutter factor

The propagation of the RF signal in an urban area is influenced by the nature of thesurrounding urban environment. An urban area can then be placed into two subcategories; the built up area and the suburban area. The built up area contains tallbuildings, office blocks, and high-rise residential tower blocks, whilst a suburban areacontains residential houses, playing fields and parks as the main features. Problems mayarise in placing areas into one of these two categories, so two parameters are utilized, aland usage factor describing the percentage of the area covered by buildings and adegree of urbanization factor, describing the percentage of buildings above storeys in thearea.

B(dB) � 20 � � F40�� 0.18L � 0.34H � K

Where: B(dB) is: the clutter factor in dB.

F the frequency of RF signal.

L the percentage of land within 500 m square occupiedby buildings.

H the difference in height between the squares containingthe transmitter and receiver.

K 0.094U � 5.9

U the percentage of L occupied by buildings above fourstoreys.

A good base station site should be high enough to clear all the surrounding obstacles inthe immediate vicinity. However, it should be pointed out that although employing highantennas increases the coverage area of the base station, this can also have adverseeffects on channel re-use distances because of the increased possibility of co-channelinterference.

Antenna gain

The additional gain provided by an antenna can be used to enhance the distance that theradio wave is transmitted. Antenna gain is measured against an isotropic radiator. Anyantenna has a gain over an isotropic radiator because in practice it is impossible toradiate the power equally in all directions. This means that in some directions theradiated power will be concentrated. This concentration, or focusing of power, is whatenables the radio waves to travel further than those that if it were possible were radiatedfrom an isotropic radiator. See Figure 3-18.

Figure 3-18 Focusing of power

ISOTROPIC RADIATOR(A SPHERICAL PATTERN)

VERTICAL DIPOLE RADIATION PATTERN(SIDE VIEW)

TRANSMITTER


30 Sep 20033�30


GMR-0168P02900W21-M

Measuring antenna gain

The gain of a directional antenna is measured by comparing the signal strength of acarrier emitted from an isotropic antenna and the directional antenna. First the power ofthe isotropic radiator is increased so that both receive levels are the same. The emittedpowers required to achieve that are then compared for both antennas. The difference is ameasure of gain experienced by the directional antenna. It will always have some gainwhen compared to an isotropic radiator. See example in Figure 3-19.

Figure 3-19 Measurement of gain

10 W

MEASUREMENT POINT

TRANSMITTER

1000 W

MEASUREMENT POINT

In this example, to achieve a balanced receive level the isotropic radiator must have aninput 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 isotropic.

The more directional the antenna is made then the more gain it will experience. This isapparent when sectorizing cells. Each sectored cell will require less transmit power thanthe equivalent range omni cell due to the gain of its directional antenna, typically 14 dBito 17 dBi.

The gain is also present in the receive path, though in all cases the gain decreases asthe frequency increases. This is why the uplink mobile to BTS frequency is usually thelowest part of the frequency range. This gives a slight gain advantage to the lower powermobile transmitter.


30 Sep 2003


68P02900W21-M

GMR-013�31

Propagation in buildingsWith the increased use of hand portable equipment in mobile cellular systems, combinedwith the increased availability of cordless telephones, it has become essential to studyRF propagation into and within buildings.

When calculating the propagation loss inside a building (see Figure 3-20) a building lossfactor is added to the RF path loss. This building loss factor is included in the model toaccount for the increase in attenuation of the received signal when the mobile is movedfrom outside to inside a building. This is fine if all users stand next to the walls of thebuilding when making calls, but this does not happen, so the internal distance throughwhich the signal must pass which has to be considered. Due to the internal constructionof a building, the signal may suffer from spatial variations caused by the design of theinterior of the building.

Figure 3-20 In building propagation

X dBmW dBm

X dBm = SIGNAL STRENGTH OUTSIDE BUILDING

W dBm = SIGNAL STRENGTH INSIDE BUILDING

BUILDING INSERTION LOSS (dBm) = X �W = B dBm

TRANSMITTER

GAIN

REFERENCE POINT

TRANSMITTER

The building loss tends to be defined as the difference in the median field intensity at theadjacent area just outside the building and the field intensity at a location on the mainfloor 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 plottingcell coverage areas and grade of service.

When considering coverage in tall buildings, coverage is being considered throughout thebuilding, if any floors of that building are above the height of the transmitting antenna apath gain will be experienced.


30 Sep 20033�32


GMR-0168P02900W21-M

The Okumura method

In the early 1960s, a Japanese engineer named Okumura carried out a series of detailedpropagation tests for land mobile radio services at various different frequencies. Thefrequencies were 200 MHz in the VHF band and 453 MHz, 922 MHz, 1310 MHz,1430 MHz, and 1920 MHz in the UHF band. The results were statistically analyzed anddescribed for distance and frequency dependencies of median field strength, locationvariabilities and antenna height gain factors for the base and mobile stations in urban,suburban, and open areas over quasi-smooth terrain.

The correction factors corresponding to various terrain parameters for irregular terrain,such as rolling hills, isolated mountain areas, general sloped terrain, and mixed land/seapath were defined by Okumura.

As a result of these tests, carried out primarily in the Tokyo area, a method for predictingfield strength and service area for a given terrain of a land mobile radio system wasdefined. The Okumura method is valid for the frequency range of 150 to 2000 MHz, fordistances between the base station and the mobile stations of 1 to 100 km, with basestation effective antenna heights of 30 to 100 m.

The results of the median field strength at the stated frequencies were displayedgraphically (see Figure 3-21). Different graphs were drawn for each of the testfrequencies in each of the terrain environments (for example; urban, suburban, hillyterrain) Also shown on these graphs were the various antenna heights used at the testtransmitter base stations. The graphs show the median field strength in relation to thedistance in km from the site.

As this is a graphical representation of results, it does not transfer easily into a computerenvironment. However, the results provided by Okumura are the basis on which path lossprediction equations have been formulated. The most important work has been carriedout by another Japanese engineer named Hata. Hata has taken Okumura�s graphicalresults and derived an equation to calculate the path loss in various environments. Theseequations have been modified to take into account the differences between the Japaneseterrain and the type of terrain experienced in Western Europe.


30 Sep 2003


68P02900W21-M

GMR-013�33

Figure 3-21 Okumura propagation graphs

1 2 3 7 10 20 30 40 50 60 70 80 90 1000.6

�10

0

10

20

30

40

50

60

70

80

90

100

110

Free Space

X

XXX X

XXX X

XXX

XXXX

X XX

X

X

XX

X

LOG SCALELINEAR SCALE

DISTANCE (km)

922 MHz

h.= 320 m

h.= 3 m

X

PROPAGATION GRAPH FOR 922 MHz

5

h.= 220 m

h.= 140 m

h.= 45m

FIELD

STR

ENGTH

(dB re

l. 1 uV

/m) F

OR 1 kW ERP


30 Sep 20033�34


GMR-0168P02900W21-M

Hata�s propagation formula

Hata used the information contained in Okumura�s propagation loss report of the early1960�s, which presented its results graphically, to define a series of empirical formulas toallow propagation prediction to be done on computers. The propagation loss in an urbanarea can be presented as a simple formula of:

A + B log 10R

Where: A is: the frequency.

B the antenna height function.

R the distance from the transmitter.

Using this basic formula, which is applicable to radio systems is the UHF and VHFfrequency ranges, Hata added an error factor to the basic formula to produce a series ofequations to predict path loss. To facilitate this action, Hata has set a series of limitationswhich must be observed when using this empirical calculation method:

Where: Frequency range (fc) is: 100 � 1500 MHz

Distance (R) 1 � 20 km

Base station antenna height (hb) 30 � 200 m

Vehicular antenna height (hm) 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 Hata�s formula predicts the actual pathloss, 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: the 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: fc is: > 400 MHz.

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


30 Sep 2003


68P02900W21-M

GMR-013�35

Power budget and system balance

In any two-way radio system, the radio path losses and equipment output powers mustbe taken into account for both directions. This is especially true in a mobile network,where there are different characteristics for the uplink and downlink paths. These includereceive path diversity gain in the uplink only, the possibility of mast head amplifiers in theuplink path, the output power capability of the mobile is a lot less than that of the BTS,and the sensitivity of the BTS receiver is usually better than that of the mobile.

If these differences are not considered, it is possible that the BTS will have a servicearea far greater than that which the mobile will be able to use due to its limited outputpower. Therefore the path losses and output powers in the uplink and downlink must becarefully calculated to achieve a system balance. One where the power required of themobile to achieve a given range is equitable to the range offered by the powertransmitted by the BTS. The output powers of the BTS and mobile are unlikely to be thesame for any given distances due to the differences in uplink and downlink path lossesand gains as described above.

Once the area of coverage for a site has been decided, the calculations for the powerbudget can be made. The system balance is then calculated which will decide the outputpowers of the BTS and mobile to provide acceptable quality calls in the area of coverageof the BTS. The BTS power level must never be increased above the calculated level forsystem balance. Although this seems a simple way to increase coverage, the systembalance will be different and the mobile may not be able to make a call in the newcoverage area.

To increase the cell coverage, an acceptable way is to increase the gain of the antenna.This will affect both the uplink and downlink therefore maintaining system balance.Where separate antennas are used for transmit and receive they must be of similar gain.If the cell size is to be reduced, then this is not a problem as the BTS power can bealtered and the mobile�s output power is adaptive all the time.

There is a statistic in the BTS that checks the path balance every 480 ms for each call inprogress. The latest uplink and downlink figures reported along with the actual mobileand BTS transmit powers are used in a formula to give an indication of the path balance.


30 Sep 20033�36


GMR-0168P02900W21-M

GSM900 path loss

Figure 3-22 and Figure 3-23 compare the path losses at different heights for the BTSantenna and different locations of the mobile subscriber between 1 km and 100 km cellradius.

Figure 3-22 BTS antenna height of 50 m, MS height of 1.5 m (GSM900)

CELL RADIUS (km)

1 10 100

PA

TH

LO

SS

(dB

)

90

100

110

120

130

140

150

160

170

180

190

200

210

220

URBAN INDOOR

URBAN

SUBURBAN

RURAL (OPEN)

RURAL (QUASI OPEN)

Figure 3-23 BTS antenna height of 100 m, MS height of 1.5 m (GSM900)

CELL RADIUS (km)

1 10 100

PA

TH

LO

SS

(dB

)

90

100

110

120

130

140

150

160

170

180

190

200

210

220

URBAN INDOOR

URBAN

SUBURBAN

RURAL (OPEN)

RURAL (QUASI OPEN)


30 Sep 2003


68P02900W21-M

GMR-013�37

Path loss GSM900 vs DCS1800

Figure 3-24 illustrates the greater path loss experienced by the higher DCS1800frequency range compared to the GSM900 band. The cell size is typical of that found inurban or suburban locations. The difference in path loss for the GSM900 band at 0.2 kmcompared with 3 km is 40 dB, a resultant loss factor of 10,000 compared to themeasurement at 0.2 km.

Figure 3-24 Path loss vs cell radius for small cells

CELL RADIUS (km)

0.1 1.0 3.0

PA

TH

LO

SS

(dB

)

100

110

120

130

140

150

160

170

GSM900

0.3

DCS1800(MEDIUM SIZED CITIES AND

SUBURBAN CENTRES)

DCS1800(METROPOLITAN CENTRES)

GSR6 (Horizon II)Frequency re-use

30 Sep 20033�38


GMR-0168P02900W21-M

Frequency re-use

Introduction to re-use patterns

The network planner designs the cellular network around the available carriers orfrequency channels. The frequency channels are allocated to the network provider fromthe GSM/EGSM900 and DCS1800 bands as shown below:

Frequency Band Tx Range Rx Range No. RF Carriers

GSM900 935 � 960 MHz 890 � 915 MHz 124

EGSM900 925 � 960 MHz 880 � 915 MHz 174

DCS1800 1805 � 1880 MHz 1710 � 1785 MHz 374

Within this range of frequencies only a finite number of channels may be allocated to theplanner. The number of channels will not necessarily cover the full frequency spectrumand there has to be great care taken when selecting/allocating the channels.

Installing a greater number of cells will provide greater spectral efficiency with morefrequency re-use of available frequencies. However, a balance must be struck betweenspectral efficiency and all the costs of the cell. The size of cells will also indicate how thefrequency spectrum is used. Maximum cell radius is determined in part by the outputpower of the mobile subscriber (MS) (and therefore, its range) and interference causedby adjacent cells (see Figure 3-25).

Remember that the output power of the MS is limited in all frequency bands. Therefore toplan a balanced transmit and receive radio path, the planner must make use of the pathloss and thus the link budget.

The effective range of a cell will vary according to location, and can be as much as 35 kmin rural areas and as little as 1 km in a dense urban environment.

Figure 3-25 Adjacent cell interference

CARRIERF 33

INTERFERING CARRIERF 33

DISTANCE

RECEIVESIGNALLEVEL

SERVING BTS INTERFERING BTS

MOBILE POSITION

� 75dBm

� 100dBm

GSR6 (Horizon II) Frequency re-use

30 Sep 2003


68P02900W21-M

GMR-013�39

Re-use pattern

The total number of radio frequencies allocated is split into a number of channel groupsor sets. These channel groups are assigned on a per cell basis in a regular pattern whichrepeats across all of the cells. Thus, each channel set may be re-used many timesthroughout the coverage area, giving rise to a particular re-use pattern (7 cell re-usepattern, for example, shown in Figure 3-26).

Figure 3-26 7 cell re-use pattern

6

2

7

7 CELL RE-USE

3

4 1

5

EACH USINGCHANNEL SETS

1

1

1

1

2

2

2

3

3

3

4

4

4 5

5

5

6

6

6

7

7

7

Clearly, as the number of channel sets increases, the number of available channels percell reduces and therefore the system capacity falls. However, as the number of channelsets increases, the distance between co-channel cells also increases, thus theinterference reduces. Selecting the optimum number of channel sets is therefore acompromise between quality and capacity.


30 Sep 20033�40


GMR-0168P02900W21-M

4 site � 3 cell re-use pattern

Due to the increase in frequency robustness within GSM, different re-use frequencypatterns can be adopted which gives an overall greater frequency efficiency.

The most common re-use pattern is 4 site with 3 cells (see Figure 3-27). With theavailable frequency allocation divided into 12 channels sets numbered a1�3, b1�3, c1�3,and d1�3. The re-use pattern is arranged so that the minimum re-use distance betweencells is at least 2 to 1.

Figure 3-27 4 site � 3 cell re-use pattern

b1

b3

b2

d3

c2

c1

c3

a2

d2

d1

a1

a3

EXAMPLE

NEW CELL CANUSE d1�3 FREQ

ALLOCATION

a1

a1

a1

a2

a2

a3

a3

a3

a2

b1

b1 b1

b1

b2

b2b2

b2

b3

b3b3

b3

c1c1

c1

c2

c2

c2

c3

c3

c3

d1 d1

d1

d2d2

d2

d3

d3 d3

a2

The other main advantage of this re-use pattern is if a new cell is required to be insertedin the network, then there is always a frequency channel set available which will notcause any adjacent channel interference.


30 Sep 2003


68P02900W21-M

GMR-013�41

2 site � 6 cell re-use pattern

Another solution to possible network operator capacity problems may be an even higherfrequency re-use pattern. The re-use pattern, shown in Figure 3-28, uses a 2 site � 6 cellre-use.

Figure 3-28 2 site � 6 cell re-use pattern

b6b1

b4

b2

b3b5b6

b5

b2

b4

b3b1

a6a1

a4

a2

a3a5

a5a4

a1

a3

a2a6

60° SECTORS

Therefore, 2 sites repeated each with 6 cells = 2 x 6 = 12 groups.

If the operator has only 24 carriers allocated for their use, they are still in a position touse 2 carriers per cell. However this may be extremely difficult and may not be possibleto implement. It also may not be possible due to the current network configuration.However, the subscribers per km ratio would be improved.


30 Sep 20033�42


GMR-0168P02900W21-M

Carrier/ Interference (C/I) ratio

When a channel is re-used there is a risk of co-channel interference, which is whereother base stations are transmitting on the same frequency.

As the number of channel sets increases, the number of available channels per cellreduces and therefore capacity reduces. But the interference level will also reduce,increasing the quality of service.

The capacity of any one cell is limited by the interference that can be tolerated for a givengrade of service. A number of other factors, apart from the capacity, affect theinterference level:

S Power control (both BTS and MS).

S Hardware techniques.

S Frequency hopping (if applied).

S Sectorization.

S Discontinuous transmission (DTX).

Carrier/Interference measurements taken at different locations within the coverage of acell can be compared to a previously defined acceptable criterion. For instance, thecriterion for the C/I ratio maybe set at 8 dB, with the expectation that the C/Imeasurements 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 bedetermined (see Figure 3-29) to give overall system comparison.

Figure 3-29 Carrier interference measurements

GSM system : 9dB �CI�� 7.94

�(D�R)4

6� 7.94

Therefore (DR

)4 � 47.66

Thus �DR�� 47.664� � 2.62

MS

BS BSR

DISTANCE BETWEEN CELLS

D

C/I CAN BE RELATED TO D/R(2 CELLS USING THE SAME BCCH FREQUENCY)

ANALOGUE SYSTEM D/R = 4.4GSM SYSTEM D/R= 2.62


30 Sep 2003


68P02900W21-M

GMR-013�43

Other sources of interference

Adjacent Channel Interference: This type of interference is characterized by unwantedsignals from other frequency channels spilling over or injecting energy into the channel ofinterest.

With this type of interference being influenced by the spacing of RF channels, its effectcan be reduced by increasing the frequency spacing of the channels. However, this willhave the adverse effect of reducing the number of channels available for use within thesystem.

The base station and the mobile stations receiver selectivity can also be designed toreduce the adjacent channel interference.

Environmental Noise: This type of interference can also provide another source ofpotential interference. The intensity of this environmental noise is related to localconditions and can vary from insignificant to levels which can completely dominate allother sources of noise and interference.

There are also several other factors which have to be taken into consideration. Theinterfering co-channel signals in a given cell would normally arise from a number ofsurrounding cells, not just one.

What effect will directional antennas have when employed?

Finally, if receiver diversity is to be used, what type and how is implementation to beachieved?

Sectorization of sites

As cell sizes are reduced, the propagation laws indicate that the levels of carrierinterference tend to increase. In a omni cell, co-channel interference will be received fromsix surrounding cells, all using the same channel sets. Therefore, one way of significantlycutting the level of interference is to use several directional antennas at the basestations, 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 whichmeans more traffic channels available for subscribers to use. Also, by installing morecapacity at the same site, there is a significant reduction in the overall implementationand operating costs experienced by the network operator.

By using sectorized antennas, sectorization allows the use of geographically smaller cellsand a tighter more economic re-use of the available frequency spectrum. This results inbetter network performance to the subscriber and a greater spectrum efficiency.

The use of sectorized antennas allows better control of any RF interference which resultsin a higher call quality and an improved call reliability. More importantly for the networkdesigner, sectorization extends and enhances the cells ability to provide the in-buildingcoverage that is assumed by the hand portable subscriber.

Sectorization provides the flexibility to meet uneven subscriber distribution by allowing, ifrequired, 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 availablechannel resources.

Finally, with the addition of diversity techniques, an improved sensitivity and increasedinterference immunity are experienced in a dense urban environment.

GSR6 (Horizon II)Overcoming adverse propagation effects

30 Sep 20033�44


GMR-0168P02900W21-M

Overcoming adverse propagation effects

Hardware techniques

Multipath fading is responsible for more than just deep fades in the signal strength. Themultipath signals are all arriving at different times and the demodulator will attempt torecover all of the time dispersed signals. This leads to an overlapping situation whereeach signal path influences the other, making the original data very hard to distinguish.This problem is known as inter symbol interference (ISI) and is made worse by the factthat the output from the demodulator is rarely a square wave. The sharp edges arenormally rounded off so that when time dispersed signals are combined it makes itdifficult to distinguish the original signal state.

Another factor which makes things even more difficult is that the modulation techniqueGaussian minimum shift keying, itself introduces a certain amount of ISI. Although this isa known distortion and can under normal conditions be filtered out, when it is added tothe ISI distortion caused by the time delayed multipath signals, it makes recovery of theoriginal data that much harder.

Frequency hopping

Frequency hopping is a feature that can be implemented on the air interface (the radiopath to the MS, for example) to help overcome the effects of multipath fading. GSMrecommends only one type of frequency hopping � baseband hopping; but theMotorola BSS will support an additional type of frequency hopping, called synthesizerhopping .

Baseband hopping

Baseband hopping is used when a base station has several transceivers available. Thedata flow is simply routed in the baseband to various transceivers, each of whichoperates on a fixed frequency, in accordance with the assigned hopping sequence. Thedifferent transceivers will receive a specific individual timeslot in each TDMA framecontaining information destined for different MSs.

There are important points to note when using this method of providing frequencyhopping:

S There is a need to provide as many transceivers as the number of allocatedfrequencies.

S Within Horizon II macro equipment applications, the use of any type of Tx block(DUP, HCU, DHU) is acceptable.

NOTE CCBs cannot be used with Horizon II macro equipment. Also, ifHorizon II macro CTU2s are used in Horizonmacro equipmentand are controlled by a MCUF, baseband hopping is onlysupported when the CTU2s are used in single density mode.

S Within Horizonmacro equipment applications, the use of any type of Tx block (TDF,DCF, DDF) or cavity combining blocks (CCBs) is acceptable.

S Within M-Cell equipment applications, the use of either combining bandpassfilter/hybrid or cavity combining blocks is acceptable.

S The use of remote tuning combiners, cavity combining blocks or hybrid combinersis acceptable in BTS6 equipment applications.

GSR6 (Horizon II) Overcoming adverse propagation effects

30 Sep 2003


68P02900W21-M

GMR-013�45

Synthesizer hopping

Synthesizer hopping uses the frequency agility of the transceiver to change frequencieson a timeslot basis for both transmit and receive. The transceiver board in the CTU, thedigital processing and control board in the TCU and the SCB in the DRCU calculates thenext frequency and programmes one of the pair of Tx and Rx synthesizers to go to thecalculated frequency. As the transceiver uses a pair of synthesizers for both transmit andreceive, as one pair of synthesizers is being used the other pair are retuning.

There are important points to note when using synthesizer hopping:

S Instead of providing as many transceivers as the number of allocated frequencies,there is only a need to provide as many transceivers as determined by traffic plusone for the BCCH carrier.

S The output power available with the use of hybrid combiners must be consistentwith coverage requirements.

S CCBs cannot be used for synthesizer hopping (mechanical tuning is too slow).

Therefore as a general rule, cells with a small number of carriers will make goodcandidates for synthesizer hopping, whilst cells with many carriers will be goodcandidates for baseband hopping.

There is also one other rule: there can only be one type of hopping at a BTS site, nota combination of the two.


30 Sep 20033�46


GMR-0168P02900W21-M

Error protection and detection

To protect the logical channels from transmission errors introduced by the radio path,many different coding schemes are used.

The coding and interleaving schemes depend on the type of logical channel to beencoded. All logical channels require some form of convolutional encoding, but sinceprotection needs are different, the code rates may also differ.

The coding protection schemes, shown in Figure 3-30, are:

S Speech channel encoding.

S Common control channel encoding.

S Data channel encoding.

Figure 3-30 The coding process

20 msINFORMATION

BLOCK

SPEECH (260 BITS)

CONTROL (184 BITS)

DATA (240 BITS)

ENCODING INTERLEAVING

0.577 msINFORMATION

BURSTS

SPEECH (8 BURSTS)

CONTROL (4 BURSTS)

DATA (22 BURSTS)

Speech channel encoding

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

Common control channel encoding

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

Data channel encoding

The data information is spread over 22 bursts. This is because every bit of datainformation is very important. Therefore, when the data is reconstructed at the receiver, ifa burst is lost, only a very small proportion of the 20 ms block of data will be lost. Theerror encoding mechanisms should then enable the missing data to be reconstructed.


30 Sep 2003


68P02900W21-M

GMR-013�47

Figure 3-31 illustrates the coding process for speech, control and data channels; thesequence is very complex.

Figure 3-31 Error protection and detection

EFR SPEECHFRAME

244 BITS

TCH/2.4

FR SPEECHFRAME

244 BITS

BCCH, PCH, AGCH, SDCCH,FACCH, SACCH, CBCH

184 BITS

DATA TRAFFIC9.6/4.8/2.4 k

N0 BITS

RACH + SCHP0 BITS

CYCLIC CODE+ REPETITION

IN: 244OUT: 260

CLASS 1aCYCLIC CODE

+ TAILIN: 260

OUT: 267

FIRECODE + TAILIN: 184

OUT: 228

ADD IN TAILIN: N0 BITS

OUT: N1 BITS

CYCLIC CODE + TAILIN: P0 BITS

OUT: P1 BITS

CONVOLUTION CODEIN: P1 BITS

OUT: 2 x P1 BITS

CONVOLUTION CODE+ PUNCTURE

IN: N1 BITSOUT: 456 BITS

CONVOLUTION CODEIN: 248 BITS

OUT: 456 BITS

CONVOLUTION CODEIN: 267 BITS

OUT: 456 BITS

RE-ORDERING & PARTITIONING+ STEALING FLAG

IN: 456 BITSOUT: 8 SUB-BLOCKS DIAGONAL INTERLEAVING +

STEALING FLAGIN: BLOCKS OF 456 BITS

OUT: 22 SUB-BLOCKS

BLOCK DIAGONALINTERLEAVINGIN: 8 BLOCKS

OUT: PAIRS OF BLOCKS

BLOCK RECTANGULARINTERLEAVING

IN: 8 SUB-BLOCKSOUT: PAIRS OF SUB-BLOCKS

19 x TCH 9.6 kBIT/S (BURST)

1 x RACH1 x SCH (BURST)

8 x TCH FR (BURSTS)8 x TCH EFR (BURSTS)8 x FACCH/TCH (BURSTS)8 x TCH 2-4 kBIT/S (BURSTS)

4 x BCCH, PCH, AGCH4 x SDCCH, SACCH4 x CBCH (BURSTS)


30 Sep 20033�48


GMR-0168P02900W21-M

GSM speech channel encoding

The BTS receives transcoded speech over the Abis interface from the BSC. At this pointthe speech is organized into its individual logical channels by the BTS. These logicalchannels of information are then channel coded before being transmitted over the airinterface.

The transcoded speech information is received in frames, each containing 260 bits. Thespeech bits are grouped into three classes of sensitivity to errors, depending on theirimportance to the intelligibility of speech.

Class 1a

Three parity bits are derived from the 50 Class 1a bits. Transmission errors within thesebits are catastrophic to speech intelligibility, therefore, the speech decoder is able todetect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, thewhole block is usually ignored.

Class 1b

The 132 Class 1b bits are not parity checked, but are fed together with the Class 1a andparity bits to a convolutional encoder. Four tail bits are added which set the registers inthe receiver to a known state for decoding purposes.


30 Sep 2003


68P02900W21-M

GMR-013�49

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, 260bits are transmitted in 20 ms equalling a transmission rate of13 kbit/s. If enhanced full rate is used then 244 bits aretransmitted over the Abis link for each 20 ms sample. The EFRframe is treated to some preliminary coding to build it up to 260bits 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 raisingthe transmission rate to 22.8 kbit/s.

Figure 3-32 shows a diagrammatic representation of speech channel encoding.

Figure 3-32 Speech channel encoding

CLASS 1a CLASS 1b CLASS 250 BITS 132 BITS 78 BITS

50 3 132 4

PARITYCHECK

TAILBITS

CONVOLUTIONAL CODE

378 78

456 BITS

260 BITS


30 Sep 20033�50


GMR-0168P02900W21-M

GSM speech channel coding for enhanced full rate

The transcoding for enhanced full rate produces 20 ms speech frames of 244 bits forchannel coding on the air interface. After passing through a preliminary stage which adds16 bits to make the frame up to 260 bits the EFR speech frame is treated to the samechannel coding as full rate.

The additional 16 bits correspond to an 8 bit CRC which is generated from the 50Class 1a bits plus the 15 most important Class 1b bits and 8 repetition bits correspondingto 4 selected bits in the original EFR frame of 244 bits.

Preliminary channel coding for EFR

EFR speech frame:

S 50 Class 1a + 124 Class 1b + 70 Class 2 = 244 bits.

Preliminary coding:

S Add 8 bits CRC generated from 50 Class 1a + 15 most important Class 1b bits toClass 1b bits.

S Add 8 repetition bits to Class 2 bits.

Output from preliminary coding:

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

Figure 3-33 shows a diagrammatic representation of preliminary coding for enhanced fullrate speech.

Figure 3-33 Preliminary coding for enhanced full rate speech

244 BITS

CLASS 1a50 BITS

CLASS 1b124 BITS

CLASS 270 BITS

CLASS 1a50 BITS

CLASS 278 BITS

CLASS 1b132 BITS

8 BIT CRC ADDED TOCLASS 1b BITS

8REPETITIONBITS ADDEDTO CLASS 2

BITS

260 BITS


30 Sep 2003


68P02900W21-M

GMR-013�51

GSM control channel encoding

Figure 3-34 shows the principle of the error protection for the control channels. Thisscheme is used for all the logical signalling channels, the synchronization channel (SCH)and the random access burst (RACH). The diagram applies to SCH and RACH, but withdifferent numbers.

Figure 3-34 Control channel coding

184

184

4

FIRE CODE TAIL BITS

CONVOLUTIONAL CODE

456

40

PARITY BITS

456 BITS

184 BITS

When control information is received by the BTS it is received as a block of 184 bits.These bits are first protected with a cyclic block code of a class known as a Fire Code.This is particularly suitable for the detection and correction of burst errors, as it uses 40parity bits. Before the convolutional encoding, four tail bits are added which set theregisters in the receiver to a known state for decoding purposes.

The output from the encoding process for each block of 184 bits of signalling data is 456bits, exactly the same as for speech. The resulting 456 bit block is then interleavedbefore being sent over the air interface.


30 Sep 20033�52


GMR-0168P02900W21-M

GSM circuit-switched data channel encoding

Figure 3-35 shows the principle of the error protection for the 9.6 kbit/s data channel. Theother data channels at rates of 4.8 kbit/s and 2.4 kbit/s are encoded slightly differently,but the principle is the same.

Figure 3-35 Data channel encoding

CONVOLUTIONAL CODE

488

PUNCTUATE

456

DATA CHANNEL 9.6 kbit/s

240

4

TAILBITS

240 BITS

456 BITS

240

Data channels are encoded using a convolutional code only. With the 9.6 kbit/s datasome coded bits need to be removed (punctuated) before interleaving, so that like thespeech and control channels, they contain 456 bits every 20 ms.

The data traffic channels require a higher net rate than their actual transmission rate (netrate means the bit rate before coding bits have been added). For example, the 9.6 kbit/sservice will require 12 kbit/s, because status signals (such as the RS-232 DTR (dataterminal ready)) have to be transmitted as well.

The output from the encoding process for each block of 240 bits of data traffic is 456 bits,exactly the same as for speech and control. The resulting 456 bit block is theninterleaved before being sent over the air interface.

NOTE Over the PCM link 240 bits were transmitted in 20 ms, equallinga transmission rate of 12 kbit/s. 9.6 kbit/s raw data and 2.4 kbit/ssignalling information.

The encoded control information now occupies 456 bits but is still transmitted in 20 msthus raising the transmission rate to 22.8 kbit/s.


30 Sep 2003


68P02900W21-M

GMR-013�53

Mapping logical channels onto the TDMA frame structure

Interleaving

Having encoded or error protected the logical channel, the next step is to build itsbitstream into bursts that can then be transmitted within the TDMA frame structure. It isat this stage that the process of interleaving is carried out. Interleaving spreads thecontent of one traffic block across several TDMA timeslots. The following interleavingdepths are used:

S Speech � 8 blocks.

S Control � 4 blocks.

S Data � 22 blocks.

This process is an important one, for it safeguards the data in the harsh air interfaceradio environment.

Because of interference, noise, or physical interruption of the radio path, bursts may bedestroyed or corrupted as they travel between MS and BTS, a figure of 10�20% is quitenormal. The purpose of interleaving is to ensure that only some of the data from eachtraffic block is contained within each burst. By this means, when a burst is not correctlyreceived, the loss does not affect overall transmission quality because the errorcorrection techniques are able to interpolate for the missing data. If the system workedby simply having one traffic block per burst, then it would be unable to do this andtransmission quality would suffer.

It is interleaving (summarized in Table 3-2) that is largely responsible for the robustnessof the GSM air interface, enabling it to withstand significant noise and interference andmaintain the quality of service presented to the subscriber.

Table 3-2 Interleaving

TRAU frame type Number of GSM bursts the trafficblock is spread over

Speech 8

Control 4

CS data 22


30 Sep 20033�54


GMR-0168P02900W21-M

Diagonal interleaving � speech

Figure 3-36 illustrates, in a simplified form, the principle of the interleaving processapplied to a full-rate speech channel.

Figure 3-36 Diagonal interleaving � speech

20 ms SPEECH SAMPLE 456 BITS

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍÍÍÍÍ

MAPPED TO ODD BITSOF BURST

BITS 4, 12, 20, 28 ..... 452

ÍÍÍÍÍÍ

20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS

BITS 0, 8, 16, 24 ..... 448

MAPPED TO EVEN BITSOF BURST

BITS 0, 8, 16, 24 ..... 448

MAPPED TO EVEN BITSOF BURST

MAPPED TO ODD BITSOF BURST

BITS 4, 12, 20, 28 ..... 452

012345678 .... 113 012345678 .... 113

The diagram shows a sequence of speech blocks after the encoding process previouslydescribed, all from the same subscriber conversation. Each block contains 456 bits,these blocks are then divided into eight blocks each containing 57 bits. Each block willonly contain bits from even bit positions or bits from odd bit positions.

The GSM burst will now be produced using these blocks of speech bits.

The first four blocks will be placed in the even bit positions of the first four bursts. Thelast four blocks will be placed in the odd bit positions of the next four bursts.

As each burst contains 114 traffic carrying bits, it is in fact shared by two speech blocks.Each block will share four bursts with the block preceding it, and four with the block thatsucceeds it, as shown. In the diagram block 5 shares the first four bursts with block 4and the second four bursts with block 6.


30 Sep 2003


68P02900W21-M

GMR-013�55

Transmission � speech

Each burst will be transmitted in the designated timeslot of eight consecutive TDMAframes, providing the interleaving depth of eight.

Table 3-3 shows how the 456 bits resulting from a 20 ms speech sample are distributedover eight normal bursts.

Table 3-3 Distribution of 456 bits from one 20 ms speech sample

Distribution Burst

0 8 16 24 32 40 ..........................448 even bits of burst N

1 9 17 25 33 41 ..........................449 even bits of burst N + 1



4 12 20 28 36 44 ..........................452 odd bits of burst N + 4




It is important to remember that each timeslot on this carrier may be occupied by adifferent channel combination: traffic, broadcast, dedicated or combined.

NOTE Note that FACCH, because it steals speech bursts from asubscriber channel, experiences the same kind of interleaving asthe speech data that it replaces (interleaving depth = 8).

The FACCH will steal a 456 bit block and be interleaved with the speech. Each burstcontaining a FACCH block of information will have the appropriate stealing flag set.


30 Sep 20033�56


GMR-0168P02900W21-M

Rectangular interleaving � control

Figure 3-37 illustrates, in a simplified form, the principle of rectangular interleaving. Thisis applied to most control channels.

Figure 3-37 Rectangular interleaving � control

FRAME 1

54

654321

ÍÍÍ

ÍÍÍ

ÍÍÍ

ÍÍÍ

ÍÍÍ

ÍÍÍ

ÍÍÍ

ÍÍÍ

6

FRAME 2 FRAME 3

456 BITS

BURSTS

TDMA FRAMES

CONTROLBLOCKS

30 1 2 4 5 6 730 1 2 4 5 6 730 1 2 4 5 6 7

114BITS

114BITS

114BITS

114BITS

ODDEVENODDEVEN

The diagram shows a sequence of control blocks after the encoding process previouslydescribed. Each block contains 456 bits, these blocks are then divided into four blockseach containing 114 bits. Each block will only contain bits for even or odd bit positions.

The GSM burst will be produced using these blocks of control.

Transmission � control

Each burst will be transmitted in the designated timeslot of four consecutive TDMAframes, providing the interleaving depth of four.

The control information is not diagonally interleaved as are speech and data. This isbecause only a limited amount of control information is sent every multiframe. If thecontrol information was diagonally interleaved, the receiver would not be capable ofdecoding a control message until at least two multiframes were received. This would betoo long a delay.


30 Sep 2003


68P02900W21-M

GMR-013�57

Diagonal interleaving � CS data

Figure 3-38 illustrates, in a simplified form, diagonal interleaving applied to a 9.6 kbit/sdata channel.

The diagram shows a sequence of data blocks after the encoding process previouslydescribed, all from the same subscriber. Each block contains 456 bits, these blocks aredivided into four blocks each containing 114 bits. These blocks are then interleavedtogether.

The first 6 bits from the first block are placed in the first burst. The first 6 bits from thesecond block will be placed in the second burst and so on. Each 114 bit block is spreadacross 19 bursts and the total 456 block will be spread across 22 bursts.

Data channels are said to have an interleaving depth of 22, although this is sometimesalso referred to as an interleaving depth of 19.


30 Sep 20033�58


GMR-0168P02900W21-M

Transmission � CS data

The data bits are spread over a large number of bursts, to ensure that the data isprotected. Therefore, if a burst is lost, only a very small amount of data from one datablock will actually be lost. Due to the error protection mechanisms used, the lost data hasa higher chance of being reproduced at the receiver.

This wide interleaving depth, although providing a high resilience to error, does introducea time delay in the transmission of the data. If data transmission is slightly delayed, it willnot effect the reception quality, whereas with speech, if a delay were introduced thiscould be detected by the subscriber. This is why speech uses a shorter interleavingdepth.

Figure 3-38 shows a diagrammatic representation of diagonal interleaving for CS data.

Figure 3-38 Diagonal interleaving � CS data

ÍÍ

5

654321

456 BITS

DATABLOCKS

ÍÍ

ÍÍ

ÍÍ

ÍÍ

ÍÍ

ÍÍÍÍÍÍ

114

ÍÍÍÍÍÍ

ÍÍ

ÍÍÍÍ

ÍÍÍÍ

ÍÍÍÍÍÍ

ÍÍ

ÍÍÍÍ

ÍÍ

ÍÍ

114 114114

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

114BITS

114BITS

114BITS

114BITS

LAST6

BITS

LAST6

BITS

LAST6

BITS

LAST6

BITS

FIRST6

BITS

FIRST6

BITS

FIRST6

BITS

FIRST6

BITS


30 Sep 2003


68P02900W21-M

GMR-013�59

GPRS channel coding schemesFour different coding schemes have been defined for GPRS. These are described below.

Channel coding scheme 1 (CS1)

CS1 is a channel coding scheme (see Figure 3-39), defined for the radio blocks carryingRLC data blocks, that consists of a half rate convolutional code for FEC and a 40 bit firecode for BCS. The radio block using CS1 contains 181 data bits, excluding the USF andBCS. CS1 provides a user data rate of 9.05 kbit/s.

Figure 3-39 GPRS channel coding scheme 1 (CS1)

Header and Data (181 bits) BCSUSF

4 tail bits½ convolutional coding

3 40

228 bits

456 bits6


CS2 (see Figure 3-40) uses a punctured version of the same half rate convolutional codeas CS1 for FEC and a 16-bit CRC for BCS. The radio block using CS2 contains 268 databits, excluding the USF and BCS. CS2 provides a user data rate of 13.4 kbit/s.




6 16

294 bits

588 bits

12

12

456 bits

Puncturing(132 bits)


30 Sep 20033�60


GMR-0168P02900W21-M


CS3 (see Figure 3-41) uses another punctured version of the same half rateconvolutional code as CS1 for FEC and a 16-bit CRC for BCS. The radio block usingCS3 contains 312 data bits, excluding the USF and BCS. CS3 provides a user data rateof 15.6 kbit/s.




6 16

338 bits

676 bits12

12

456 bits

Puncturing(220 bits)


CS4 (see Figure 3-42) is a coding scheme that has no coding for error correction andhas a 16-bit CRC for BCS. The radio block using CS4 contains 428 data bits, excludingthe USF and BCS. CS4 provides a user data rate of 21.4 kbit/s.


BCS

456 bits

Header and Data (428 bits)USF

No Coding

12 16

456 bits

12


30 Sep 2003


68P02900W21-M

GMR-013�61

All control channels except for the PRACH use CS1. Two types of packet random accessburst may be transmitted on the PRACH: an 8 information bits random access burst, oran 11 information bits random access burst (called the extended packet random accessburst). The mobile must support both random access burst types.

GPRS traffic channels may use scheme CS1, CS2, CS3 or CS4. This allows the codingscheme to be dynamically adapted to the channel conditions and thereby maximisingthroughput and optimising the performance.

NOTE Coding schemes CS3 and CS4 are not used prior to GSR5.1.

USF is the Uplink State Flag, which is transmitted on the downlink and is an invitation toa MS to transmit. The BCS is Block Check Sequence, which is used for the detection oferrors and subsequent Automatic Repeat Request (ARQ).

Table 3-4 summarizes the coding parameters for the GPRS coding schemes.

Table 3-4 Coding parameters for GPRS coding schemes

Scheme Coderate

USF Pre-codedUSF

Radioblocksexcl.USFandBCS

BCS Tail Codedbits

Punc-turedbits

Datarate

kbit/s

CS1 1/2 3 3 181 40 4 456 0 9.05

CS2 2/3 3 6 268 16 4 588 132 13.4

CS3 3/4 3 6 312 16 4 676 220 15.6

CS4 1 3 12 428 16 � 456 0 21.4

32 kbit/s TRAU

In the BSS architecture, the link which the GPRS data traverses from the channel codersin the BTS to the PCU is currently implemented using 16 kbit/s TRAU-like links. Theselinks are carried over sub-rate switched E1 timeslots which have some signalling includedto ensure the link is synchronized between the channel coders and the PCU. However,Table 3-4 shows that there is not enough bandwidth available on a 16 kbit/s link to carryCS3 and CS4, therefore the 32 kbit/s TRAU is required.

The method used is to combine two component 16 kbit/s TRAU channels to create a32 kbit/s TRAU channel. The two 16 kbit/s channels are referred to as the left and rightchannels. The left channel is the primary channel which is currently used for all GPRStraffic. The right (or auxiliary) channel is used for the larger CS3 and CS4 GPRSTRAU-like frames.

NOTE Only one 16 kbit/s timeslot (CIC) is used between the BSC andRXCDR for a CS call, therefore termination is necessary.


30 Sep 20033�62


GMR-0168P02900W21-M

Voice activity detection (VAD)

VAD is a mechanism whereby the source transmitter equipment identifies the presenceor absence of speech.

VAD implementation is effected in speech mode by encoding the speech pattern silencesat a rate of 500 bit/s rather than the full 13 kbit/s. This results in a data transmission ratefor background noise, known as comfort noise, which is regenerated in the receiver.

Without comfort noise the total silence between the speech would be considered to bedisturbing by the listener.

Discontinuous transmission (DTX)

DTX increases the efficiency of the system through a decrease in the possible radiotransmission interference level. It does this by ensuring that the MS and BTS do nottransmit unnecessary message data (ie background noise when user is not speaking).Instead, background noise information is measured and periodically transmitted to theother user, where it is played back to generate an agreeable sounding �comfort noise�.DTX can be implemented, as necessary, on a call by call basis. The effects will be mostnoticeable in communications between two MSs.

DTX in its most extreme form, when implemented at the MS can also result inconsiderable power saving. If the MS does not transmit during silences there is areduction in the overall power output requirement.

The implementation of DTX is very much at the discretion of the network provider andthere are different specifications applied for different types of channel usage.

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-43.During this time, of the possible 104 frames, only the 4 SACCH frames and 8 SilenceDescriptor (SID) frames are transmitted.

Figure 3-43 SACCH multiframe (480 ms)

SACCH

ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ

SACCH

SACCH

SACCH

SACCH

SACCH

0 103

4 x SACCH 26 FRAME MULTIFRAMES (120 ms)

8 x SILENCE DESCRIPTOR (SID)

26 FRAME MULTIFRAME 52�59

SID

SID


30 Sep 2003


68P02900W21-M

GMR-013�63

Receive diversity

In its simplest case, multipath fading arises from destructive interference between twotransmission paths. The deepest instantaneous fade occurring at the frequency for whichthe 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 theprobability of them simultaneously experiencing maximum fade depth at a givenfrequency is very much less than for the single antenna situation.

There are three ways of utilizing this concept:

S The receiver can be switched between the two RF receive paths provided twoantennas.

S The RF signals from two receive paths can be phase aligned and summed.

S The phasing can be made so as to minimize the distortion arising from themultipath transmission.

Each of the methods has advantages and disadvantages.

In the case of the switched configuration, it simply chooses the better of the two RFsignals which is switched through to the receiver circuitry.

Phase alignment has the advantage of being a continuously optimized arrangement interms of signal level, but phase alignment diversity does not minimize distortion. TheMotorola transceivers use this diversity concept.

The distortion minimizing approach, whilst being an attractive concept, has not yet beenimplemented in a form that works over the full fading range capabilities of the receiversand therefore has to switch back to phase alignment at low signal levels. This means arather complex control system is required.

It must be emphasized that diversity will not usually have any significant effect on themean depression component of fading, but the use of phase alignment diversity can helpincrease the mean signal level received.

NOTE Remember in microcellular applications that the M-Cellcity andHorizonmicro / Horizonmicro2 do not support spatial diversity.

Figure 3-44 Receive diversity

PATH LENGTHIN WAVELENGTHS

MOBILE

ANTENNAS(approx 10 wavelengths)

SPACE BETWEEN

BTS

METHODS OF UTILIZATION:

a. SWITCHED.b. PHASE ALIGNED AND SUMMED.c. PHASE ALIGNED WITH MINIMUM DISTORTION.


30 Sep 20033�64


GMR-0168P02900W21-M

Equalization

As mentioned in multipath fading, in most urban areas the only signals received aremultipath. 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 demodulatedsignal would be far too high, giving a very poor quality signal, unacceptable to thesubscriber. 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 equalizer to assess and modify theeffects 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 ofthe time.

Training sequence code

The training sequence code (see Figure 3-45) is used so that the demodulator canestimate the most probable sequence of modulated data. As the training sequence is aknown pattern, this enables the receiver to estimate the distortion ISI on the signal due topropagation effects, especially multipath reception.

The receiver must be able to cope with two multipaths of equal power received at aninterval of up to 16 microseconds. If the two multipaths are 16 microseconds delayedthen this would be approximately equivalent to 5-bit periods. There are 32 combinationspossible when two 5-bit binary signals are combined. As the transmitted trainingsequence is known at the receiver, it is possible to compare the actual multipath signalreceived with all 32 possible combinations reproduced in the receiver. From thiscomparison the most likely combination can be chosen and the filters set to remove themultipath element from the received signal.

The multipath element can be of benefit once it has been identified, as it can then berecombined with the wanted signal in a constructive way to give a greater received signalstrength. Once the filters have been set, they can be used to filter the random speechdata as it is assumed they will have suffered from the same multipath interference as thetraining sequence code. The multipath delay is calculated on a burst by burst basis, as itis constantly changing.

Figure 3-45 Training sequence code

Signal from shortest path

Signal from delayed path

3 bits

GSR6 (Horizon II) Subscriber environment

30 Sep 2003


68P02900W21-M

GMR-013�65

Subscriber environment

Subscriber hardwareSystem quality (voice quality, for example), system access and grade of service, asperceived by the customer, are the most significant factors in the success of a cellularnetwork. The everyday subscriber neither knows or really cares about the high level oftechnology incorporated into a cellular network. However, they do care about the qualityof their calls.

What the network designer must remember is that it is the subscriber who chooses thetype of equipment they wish to use on the network. It is up to the network provider tosatisfy the subscriber, whatever they choose.

The output power of the mobile subscriber is limited in a GSM system to a maximum of8 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 handportable.

EnvironmentNot only does the network designer have to plan for the subscribers choice of phone, thedesigner 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 subscriberuse 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 tryingto provide system coverage inside tunnels.

However, with the advances in technology the hand portable subscriber unit is now firmlyestablished. With this introduction came new problems for the network designer. Theportable subscriber unit provides the user far more freedom of use but the subscriber stillexpected exactly the same service. The subscriber now wants quality service from thesystem at any location. This location can be on a street, or any floor of a building whetherit be the basement or the penthouse and even in lifts (see Figure 3-46). Thus greaterfreedom of use for the subscriber gives the network designer even greater problemswhen designing and implementing a cellular system.

Figure 3-46 The subscriber environment

URBAN/CITYENVIRONMENTS

BUILDINGS

LIFTS

RURAL AREAS

TUNNELS

GSR6 (Horizon II)Subscriber environment

30 Sep 20033�66


GMR-0168P02900W21-M

Distribution

Not only do network designers have to identify the types of subscriber that use thecellular network now and in the future, but at what location these subscribers areattempting to use their phones.

Dense urban environments require an entirely different design approach, due toconsiderations mentioned earlier in this chapter, than the approach used to designcoverage for a sparsely populated rural environment.

Road and rail networks have subscribers moving at high speed, so this must beaccounted for when planning the interaction between network entities whilst thesubscriber is using the network. Even in urban areas, the network designer must beaware that traffic is not necessarily evenly distributed. As Figure 3-47 illustrates, anurban area may contain sub-areas of uneven distribution such as a business or industrialdistrict, and may have to plan for a seasonal increase of traffic due to, say, a conventioncentre. It is vitally important that the traffic distribution is known and understood prior tonetwork design, to ensure that a successful quality network is implemented.

Figure 3-47 Subscriber distribution

RURAL

URBAN

ROAD/RAILNETWORK

40%

20%

10%

EXHIBITIONS

BUSINESS AREAS

INDUSTRIAL

30%RESIDENTIAL

HIGH SPEED MOBILES(RAILWAYS)

SUBSCRIBERS DISTRIBUTION CHANGES ON A HOURLY BASIS

GSR6 (Horizon II) Subscriber environment

30 Sep 2003


68P02900W21-M

GMR-013�67

Hand portable subscribers

The network designer must ensure that the network is designed to ensure a qualityservice for the most demanding subscriber. This is the hand portable subscriber. Thehand portable now represents the vast majority of all new subscriber units introduced intocellular networks. So clearly the network operators, and hence the network designers,must recognise this.

Before commencing network design based around hand portable coverage, the networkdesigner 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 theability to be used from any location. The ability of the unit to be used at any locationmeans that the network must be designed with the provision of good in-building coverageas an essential element.

To further complicate the network designers job, these hand portable units have a lowoutput power. For example:

S 0.8 W to 8 W for GSM900.

S 0.25 W to 1 W for DCS1800.

So the distance at which these units can be used from a cell is constrained by RFpropagation limitations.

For practical purposes, the actual transmit power of the hand portable should be kept aslow 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 limitedby battery life.

GSR6 (Horizon II)Subscriber environment

30 Sep 20033�68


GMR-0168P02900W21-M

Future planning

Normal practice in network planning is to choose one point of a well know re-use modelas a starting point. Even at this early stage, the model must be improved because anytrue traffic density does not follow the homogeneous pattern assumed in any theoreticalmodels.

Small-sized heavy traffic concentrations are characteristic of the real traffic distributions.Another well known traffic characteristic feature is the fast descent in the density of trafficwhen leaving city areas. It is uneconomical to build the whole network using a standardcell size, it becomes necessary to use cells of varying sizes.

Connecting areas with different cell sizes brings about new problems. In principle it ispossible to use cells of different size side by side, but without careful consideration thismay lead to a wasteful frequency plan. This is due to the fact that the re-use distance oflarger cells is greater than that of smaller cells. The situation is often that the borders areso close to the high density areas that the longer re-use distances mean decreasedcapacity. Another solution, offering better frequency efficiency, is to enlarge the cell sizegradually from small cells into larger cells.

In most cases, the traffic concentrations are so close to each other that the expansioncannot be completed before it is time to start approaching the next concentration, bygradually decreasing the cell size. This is why the practical network is not a regularcluster composition, but a group of directional cells of varying size.

Besides this need for cells of different size, the unevenness of the traffic distribution alsocauses problems in frequency planning. Theoretical frequency division methodsapplicable to homogenous clusters cannot be used. It is quite rare that two or moreneighbouring cells need the same amount of channels. It must always be kept in mindthat the values calculated for future traffic distribution are only crude estimates and thatthe real traffic distribution always deviates from these estimates. In consequence, thenetwork plan should be flexible enough to allow for rearrangement of the network to meetthe real traffic needs.

Conclusion

In conclusion, there are no fixed rules for radio network planning. It is a case ofexperimenting and reiterating. By comparing different alternatives, the network designersshould find a plan that both fulfils the given requirements and keeps within practicallimitations. When making network plans, the designers should always remember thatevery location in a network has its own conditions, and all local problems must be tackledand solved on an individual basis.

GSR6 (Horizon II) The microcellular solution

30 Sep 2003


68P02900W21-M

GMR-013�69

The microcellular solution

Layered architecture

The basic term layered architecture is used in the microcellular context to explain howmacrocells overlay microcells. It is worth noting that when talking of the traffic capacity ofa microcell it is additional capacity to that of the macrocell in the areas of microcellularcoverage.

The traditional cell architecture design, Figure 3-48, ensures that, as far as possible, thecell gives almost total coverage for all the MSs within its area.

Figure 3-48 Layered architecture

MICROCELL A MICROCELL B

TOP VIEW

MACROCELL

MICROCELL A MICROCELL B

SIDE VIEW MACROCELL

GSR6 (Horizon II)The microcellular solution

30 Sep 20033�70


GMR-0168P02900W21-M

Combined cell architecture

A combined cell architecture system, as illustrated in Figure 3-49, is a multi-layer systemof macrocells and microcells. The simplest implementation contains two layers. The bulkof the capacity in a combined cell architecture is provided by the microcells. Combinedcell systems can be implemented into other vendors networks.

Figure 3-49 Combined cell architecture

UNDERLAYED MICROCELL(COULD BE A DIFFERENT VENDOR)

OVERLAYED MACROCELLS

CONTIGUOUS COVERAGE OVER AREAS OFHIGH SLOW MOVING TRAFFIC DENSITY

Macrocells: Implemented specifically to cater for the fast-moving MSs and to provide afallback service in the case of coverage holes and pockets of interference in the microcelllayer. Macrocells form an umbrella over the smaller microcells.

Microcells: Microcells handle the traffic from slow-moving MSs. The microcells can givecontiguous coverage over the required areas of heavy subscriber traffic.

Picocells: Low cost installation by using in-building fibre optics or telephone wiring witha HDSL modem, easily expanded to meet capacity requirements. Efficient use of thefrequency spectrum due to low power transceivers causing low interference to externalnetworks. Higher quality speech compared with external illumination of the building dueto improved uplink quality.

GSR6 (Horizon II) The microcellular solution

30 Sep 2003


68P02900W21-M

GMR-013�71

Combined cell architecture structureA combined cell architecture employs cells of different sizes overlaid to providecontiguous coverage. This structure is shown in Figure 3-50.

Figure 3-50 Combined cell architecture structure

SYSTEM 1= OVERLAY SYSTEMSYSTEM 2= UNDERLAY SYSTEM

MACROCELL COVERAGE

MICROCELLCOVERAGE

BSC B

BTS 1

BSC A

MSC

PICOCELL

BTS 2

BTS 3 BTS 4

BTS 5SYSTEM 1MACROCELL

SYSTEM 2MICROCELL

LINK TO IMPLEMENT MICROCELLS AS A SEPARATE SYSTEM

ALTERNATIVE SYSTEM (MICROCELLS CONTROLLED BY THE SAME BSC AS MACROCELLS)

Some points to note:

S Macrocell and microcell networks may be operated as individual systems.

S The macrocell network is more dominant as it handles the greater amount oftraffic.

S Microcells can be underlayed into existing networks.

S Picocells can be introduced as a third layer or as part of the second layer.

Expansion solutionAs the GSM network evolves and matures its traffic loading will increase as the numberof subscribers grow. Eventually a network will reach a point of traffic saturation. The useof microcells can provide high traffic capacity in localised areas.

The expansion of a BTS site past its original designed capacity can be a costly exerciseand the frequency re-use implications need to be planned carefully (co-channel andadjacent channel interference). The use of microcells can alleviate the increase incongestion, the microcells could be stand-alone cells to cover traffic hotspots or acontiguous cover of cells in a combined architecture. The increased coverage will givegreater customer satisfaction.

GSR6 (Horizon II)Frequency planning

30 Sep 20033�72


GMR-0168P02900W21-M

Frequency planning

Introduction to frequency planning

The ultimate goal of frequency planning in a GSM network is attaining and maintainingthe highest possible C/I ratio everywhere within the network coverage area. A generalrequirement is at least 12 dB C/I, allowing tolerance in signal fading above the 9dBspecification of GSM.

The actual plan of a real network is a function of its operating environment (geography,RF, etc.) and there is no universal textbook plan that suits every network. Nevertheless,some practical guidelines gathered from experience can help to reduce the planningcycle time.

Rules for synthesizer frequency hopping (SFH)

As the BCCH carrier is not hopping, it is strongly recommended to separate bands forBCCH and TCH, as shown in Figure 3-51.

Figure 3-51 Separating BCCH and TCH bands

n channels m channels

Guard Band

BCCH TCH

This has the benefits of:

S Making planning simpler.

S Better control of interference.

If microcells are included in the frequency plan, the band usage shown in Figure 3-52 issuggested.

Figure 3-52 Band usage for macrocells with microcells

Macro BCCH

Micro TCH

Micro Macro TCH

(SFH)BCCH

GSR6 (Horizon II) Frequency planning

30 Sep 2003


68P02900W21-M

GMR-013�73

Practical rules for TCH 1x3 re-use pattern

S BCCH re-use plan: 4x3 or 5x3, depending on the bandwidth available andoperating environment.

S Divide the dedicated band for TCH into 3 groups with an equal number offrequencies (N). These frequencies will be the ARFCN equipped in the MA list of ahopping system (FHI).

S Use an equal number of frequencies in all cells within the hopping area. Theallocation of frequencies to each sector is recommended to be in a regular orcontinuous sequence (see planning example).

S The number of frequencies (N) in each group is determined by the design loadingfactor (or carrier-to-frequency ratio). A theoretical maximum of 50% is permitted in1x3 SFH. Any value higher than 50% would practically result unacceptable quality.Some commonly used loading factors (sometimes termed as fractional loadfactors) are 40%, 33%, 25%, etc.

As a general guideline,

N �(highest non BCCH transceiver count in a cell)

(loading factor)

S No more than 48 frequencies in a cell with multiple carriers with GPRS timeslots.

S Use the same HSN for sectors within the same site. Use different HSNs fordifferent sites. This will help to randomize the co-channel interference levelbetween the sites.

S Use different MAIOs to control adjacent channel interference between the sectorswithin a site

NOTE Mobile Allocation (MA) is the set of frequencies that themobile/BTS is allowed to hop over. Two timeslots on the sametransceiver of a cell may be configured to operate on differentMAs. MA is the subset of the total allocated spectrum for theGSM operator and the maximum number of frequencies in a MAlist is limited to 64 by GSM recommendations.Mobile Allocation Index Offset (MAIO) is an integer offset thatdetermines which frequency within the MA will be the operatingfrequency. If there are N frequencies in the MA list, then MAIO ={0, 1, 2, … N�1}.Hopping Sequence Number (HSN) is an integer parameter thatdetermines how the frequencies within the MA list are arranged.There are 64 HSNs defined by GSM. HSN = 0 sets a cyclicalhopping sequence where the frequencies within the MA list arerepeated in a cyclical manner.HSN = 1 to 63 provides a pseudo random hopping sequence.The pseudo random pattern repeats itself after everyhyperframe, which is equal to 2,715,648 (26 x 51 x 2048) TDMAframes, or about 3 hours 28 minutes and 54 seconds.Motorola defines a Frequency Hopping Indicator (FHI) that ismade up of the above three GSM defined parameters. Up to 4different FHIs can be defined for a cell in a Motorola BSS andevery timeslot on a transceiver can be independently assignedone of the defined FHI. MAI is an integer that points to thefrequency within a MA list, where MAI = 0 and MAI = N�1 beingthe lowest and highest frequencies in the MA list of Nfrequencies. MAI is a function of the TDMA frame number (FN),HSN and MAIO of a frequency hopping system.


30 Sep 20033�74


GMR-0168P02900W21-M

TCH re-use planning example

S Bandwidth: 10 MHz.

S Site configuration: Mix of 2-2-2, 3-3-3 and 4-4-4.

S Loading factor: 33%.

S Environment: Multi layer (micro and macro co-exist).

The spectrum is split as shown in Figure 3-53.

Figure 3-53 Frequency split for TCH re-use planning example

Macro BCCH

Micro TCH

Micro Macro TCH

(SFH)

12 channels 27 channels

8 channels

BCCH

A total of 49 channels are available and the first and last one are reserved as guardbands. Thus, there are 47 usable channels. 12 channels are used in the BCCH layer witha 4x3 re-use pattern.

Based on 33% loading and a 4-4-4 configuration, N is calculated as N = 3 / 0.33 = 9hopping frequencies per cell. Thus, a total of 27 channels are required for the hoppingTCH layer. The remaining 8 channels are used in the micro layer as BCCH.

One of the possible frequency and parameter setting plans are outlined in Table 3-5.

Table 3-5 Frequency and parameter setting plan

ARFCN HSN MAIO

Sector A 21, 24, 27, 30,33, 36, 39, 42, 45

Any from{1, 2, … 63}

0, 2, 4

Sector B 22, 25, 28, 31,34, 37, 40, 43, 46

Same as above 1, 3, 5

Sector C 23, 26, 29, 32,35, 38, 41, 44, 47

Same as above 0, 2, 4

The above MAIO setting will avoid all possible adjacent channel interference amongsectors within the same site. The interference (co or adjacent channel) between sites willstill exist but it is reduced by the randomization effect of the different HSNs.

GSR6 (Horizon II) Frequency planning

30 Sep 2003


68P02900W21-M

GMR-013�75

Practical rules for TCH 1x1 re-use pattern

S 1x1 is usually practical in rural area of low traffic density, where the averageoccupancy of the hopping frequencies is low. With careful planning, it can be usedin high traffic areas as well.

S BCCH re-use plan: 4X3 or 5X3, depending on the bandwidth available andoperating environment.

S The allocation of TCH frequencies to each sector is recommended to be in aregular or continuous sequence.

S Use different HSNs to reduce interference (co and adjacent channel) between thesites.

S Use the same HSNs for all carriers within a site and use MAIOs to avoid adjacentand co�channel interference between the carriers. Repeated or adjacent MAIOsare not to be used within the same site to avoid co-channel and adjacent channelinterference respectively.

S A maximum loading factor of 1/6 or 16.7% is inherent in a continuous sequence offrequency allocation. Since adjacent MAIOs are restricted, the maximum numberof MAIOs permitted is:

Max MAIOs � 12

* (Total allocated channels)

S In a 3 cell site configuration, the logical maximum loading factor is 1/6 or 16.7%.

Figure 3-54 illustrates how co-channel and adjacent channel interference can be avoided.

Figure 3-54 Avoiding co-channel and adjacent channel interference

Different MAIOs toavoid co-channel

interference

Non adjacent MAIOs toavoid adjacent channel

interference

HSN = 1HSN = 1

HSN = 1


30 Sep 20033�76


GMR-0168P02900W21-M

Rules for baseband hopping (BBH)

All the rules outlined for SFH are generally applicable to BBH. As the BCCH is in thehopping frequency list, a dedicated band separated from TCH may not be essential.

An example of frequency spectrum allocation is shown in Figure 3-55.

Figure 3-55 BBH frequency spectrum allocation

BBH channels and micro TCH

Micro BCCH

GSR6 (Horizon II) 2G�3G handovers using inter-radio access technology

30 Sep 2003


68P02900W21-M

GMR-013�77

2G�3G handovers using inter-radio access technology

Introduction to 2G�3G handoversAn optional feature, introduced at GSR6, is support for handovers between differentRadio Access Technology (RAT) networks in the circuit switched domain. The RAT canbe either GSM (2G) or the Universal Mobile Telecommunication System (UMTS) (3G).

UMTS is beyond the scope of this manual and only its handover interaction with GSM isdescribed here. For further information on UMTS, refer to System Information: UMTSEquipment Planning, 68P02905W22.

2G�3G handover descriptionThe 2G�3G handover feature supports handovers between different RAT networks. TheRAT can be either 2G (GSM) or 3G (UMTS).

Current evolving 3G UMTS networks will soon allow operators to provide UMTScoverage along with GSM/GPRS coverage in their networks.

This feature enables a multi-RAT MS (a mobile station that can function in multiple RadioAccess Networks (RANs)) to handover between a GSM RAN and a 3G RAN (UMTSRadio Access Network (UTRAN)). To accomplish this, support is needed from the MS,core network elements (MSC) and GSM/UMTS network elements.

The GSM BSS support for this feature includes:

S 2G (GSM) to 3G (UMTS-FDD) cell reselection in idle mode.

S 3G (UMTS-FDD) to 2G (GSM) handover in active mode and cell reselection in idlemode.

Restrictions

There is currently an upper limit of 16 FDD UTRAN neighbours in the GSM/GPRSsystem.

ImplementationBSS changes allow 2G (GSM) to 3G (UMTS) cell reselection in GSM idle mode, and 3Gto 2G handovers in circuit-switched dedicated mode.

The BSS Inter-RAT handover GSM function is an option that must be unrestricted byMotorola. It also requires unrestricting on site by the user with the inter_rat_enabledparameter.

A future feature (not yet implemented) will contain BSS changes to allow 2G�3Ghandovers in circuit-switched dedicated mode.

With the arrival of UMTS systems, there are likely to be small UMTS coverage areaswithin larger GSM coverage areas. In such environments the call would drop when aUMTS subscriber goes out of a UMTS coverage area and into a GSM coverage area.

Congestion in the smaller UMTS areas could become a problem when the traffic in theUMTS coverage area is high. A GSM subscriber may wish to access a service withspecific QoS characteristic (for example, very high bit rate data service) that may not besupported in the GSM system.

To avoid these problems the operator may wish to configure their network such thathandover and cell reselection between UMTS and GSM is possible. The GSM BSSinter-RAT handover function provides a solution to these problems by allowing amulti-RAT MS to perform cell reselection while in idle mode, and to hand over while indedicated mode from a UMTS FDD mode cell to a GSM cell.

GSR6 (Horizon II)2G�3G handovers using inter-radio access technology

30 Sep 20033�78


GMR-0168P02900W21-M

Impact of 2G�3G handovers on GSM

Aspects of the GSM BSS system that are affected by this function are:

S Air interface

S Abis interface

S A-interface

S BSS database

S System architecture

Air interface

The BSS inter-RAT handover function introduces the system information message:SYSTEM INFORMATION 2quater. The existing SI2ter, SI3, SI13 and the HANDOVERCOMMAND messages will be updated to allow a multi-RAT MS to performmeasurements on UMTS Frequency Division Duplex (FDD) neighbour cells for thepurpose of cell reselection. The CLASSMARK UPDATE message is updated to supportthe MS revision level (2) multi-RAT MS.

CCDSP firmware has been updated to store multiple instances of the SI2ter andSI2quater messages.

Abis interface

The Abis Interface supports changes to the A-interface required for messages passedfrom the BSC to the BTS.

A-interface

The HANDOVER REQUEST message sent from the MSC is updated with a new servingarea identifier within the cell identifier (serving). This indicates that the handoveroriginates from a UMTS network. This interface also provides support for the InformationInterface Equipment (IE) at the handing over BSS to that at the receiving BSS. Thiscontainer can contain a number of User Equipment (UE) specific IEs relating to thecapabilities of the multi-RAT MS.

BSS database

The BSS database is updated to allow the provisioning of UTRAN cells to be specified asneighbours of existing GSM cells. The database also supports the configuration of newparameters associated with the messaging to the multi-RAT MS.

GSR6 (Horizon II) 2G�3G handovers using inter-radio access technology

30 Sep 2003


68P02900W21-M

GMR-013�79

System architectureshows the system architecture for the GSM BSS inter-RAT handover feature.

Figure 3-56 GSM and UMTS system nodes and interfaces

GSM Core Network(MSC/GSN)

BSS

BSC

GSM/GPRS UTRAN

UMTS Core Network(3G MSC/SGSN)

PCU

BTS BTS

Abis

Multi-RAT MS

Iub

Node B

RNS RNS

RNC RNC

Node B

Iur

Iub

E-Interface

Gn-Interface

Um

Gb-InterfaceA-Interface Iu-Cs-Interface

Iu-Ps--Interface

Uu

System considerationsExisting 2G core network (CN) nodes must be able to interact with the 3G CN nodesthrough MAP procedures defined on the E-interface between a 2G CN node and 3G CNnode.

The GSM BSS inter-RAT handover feature does not support:

S Cell reselection to UTRAN TDD neighbour cells or CDMA2000 neighbour cells.

S Dedicated call handover procedures from GSM to UMTS.

S Extended measurement reporting.

S Enhanced measurement reporting.

S The sending of a UMTS frequency list as part of the RR-CHANNEL RELEASEmessage.

S Blind search.

S The sending of SI2quater on extended BCCH.

S The BSS restricts the maximum number of UTRAN neighbours per GSM cell to16.

S Statistics are not be supported by the BSS for this feature.

S The OMC-R interface only supports UTRAN neighbour cells which have a uniqueRNC-id and cell id combination within the BSS database.

GSR6 (Horizon II)Call model parameters for capacity calculations

30 Sep 20033�80


GMR-0168P02900W21-M

Call model parameters for capacity calculations

Introduction

This section provides information on how to determine the number of control channelsrequired at a BTS.

This information is required for the sizing of the links to the BSC, and is required whencalculating the exact configuration of the BSC required to support a given BSS.

Typical call parameters

The number of control channels required at a BTS depend on a set of call parameters;typical call parameters for BTS planning are given in Table 3-6.

Table 3-6 Typical parameters for BTS call planning

Busy hour peak signalling traffic model Parameter reference

Call duration T = 120 seconds

Ratio of SMSs per call S = 0.1

Number of handovers per call (see Note) H = 2.5

Ratio of location updates to calls l = 2

Ratio of IMSI detaches to calls I = 0

Location update factor (see below) L = 2

GSM circuit-switched paging rate in pages per second PGSM = 3

Ratio of intra-BSC handovers to all handovers (see Note) i = 0.6

Ratio of LCSs per call Lcs = 0.2

Mobile terminated LCS ratio LRMT = 0.95

Mobile originated LCS ratio LRMO = 0.05

Percent link utilization (MSC to BSS) for GPROC2 U (MSC � BSS) = 0.20

Percent link utilization (BSC to BTS) U (BSC � BTS) = 0.25

Percent link utilization (BSC to RXCDR) UBSC�RXCDR = 0.4

Blocking for TCHs PB�TCHs = 2%

Blocking for MSC�BSS trunks PB�Trunks = 1%

Number of cells per BTS CBTS = 3

(continued)

GSR6 (Horizon II) Call model parameters for capacity calculations

30 Sep 2003


68P02900W21-M

GMR-013�81

Table 3-6 Typical parameters for BTS call planning (continued)


GPRS parameters

Average packet size (bytes) PKSIZE = 270

Traffic per sub/BH (kbytes/hr) � Uplink ULRATE = 30

Traffic per sub/BH (kbytes/hr) � Downlink DLRATE = 65

Average sessions per subscriber (per BH) Avg_Sessions_per_sub = 3

PS attach/detach rate (per sub/BH) PSATT/DETACH = 0.6

PDP context activation/deactivation (per sub/BH) PDPACT/DEACT = 1

Routeing area update RAU = 1.4

GPRS paging rate in pages per second PGPRS = 3

Coding scheme rates (CS1 to CS4) CS1 = 9.05 kbit/sCS2 = 13.4 kbit/sCS3 = 15.6 kbit/sCS4 = 21.4 kbit/s

NOTE These include 2G�3G handovers.

Location update factor (L)

The location update factor (L) is a function of the ratio of location updates to calls (I), theratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) orlong message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSIdetach is disabled) as in the first formula given below. When IMSI detach is enabled, thesecond or third of the formulas given below should be used. The type of IMSI detachused 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


L = I + 0.5 * I

GSR6 (Horizon II)Control channel calculations

30 Sep 20033�82


GMR-0168P02900W21-M

Control channel calculations

Introduction

There are four types of air interface control channels, they are:

S Broadcast Control CHannel (BCCH).

S Common Control CHannel (CCCH).

S Standalone Dedicated Control CHannel (SDCCH).

S Cell Broadcast CHannel (CBCH), which uses one SDCCH.

GPRS defines several new radio channels and packet data traffic channels.

S Packet Common Control CHannels (PCCCHs).

NOTE PCCCHs are not supported in the current GPRS release. AsPCCCH is not allocated, the information for packet switchedoperation is transmitted on the CCCH.

The following channels are mapped onto PCCCH:

� Packet Access Grant CHannel (PAGCH)Downlink only, mapped on AGCH or PDCH. Used to allocate one or severalPDTCHs.

� Packet Broadcast Control CHannel (PBCCH)Downlink only, mapped BCCH or PDCH.

� Packet Notification CHannel (PNCH)Downlink only. Used to notify the MS of a PTM-M. This is not used in thefirst GPRS release.

� Packet Paging CHannelDownlink only, mapped on PDCH or CCCH. This is used to page the MS.

� Packet Random Access CHannel (PRACH)Uplink only. This is used to allow request allocation of one or severalPDTCHs, in either uplink or downlink directions.

S Packet Data Traffic CHannel (PDTCH)

A PDTCH corresponds to the resource allocated to a single MS on one physicalchannel for user data transmission.

S Packet Dedicated Control CHannels (PDCCHs)

� Packet Associated Control CHannel (PACCH)The PACCH is bi-directional.

� Packet Timing advance Control CHannel (PTCCH/U)Uplink channel, used to transmit random access bursts. The transceiveruses these bursts to estimate the timing advance for an MS when it is intransfer state.

� Packet Timing advance Control CHannel (PTCCH/D)Downlink channel, used to transmit timing advance updates to several MSsat the same time.

GSR6 (Horizon II) Control channel calculations

30 Sep 2003


68P02900W21-M

GMR-013�83

Planning considerations

There are three configurations of control channels, each occupies one radio timeslot:

S A combined control channel.

One BCCH plus three CCCHs plus four SDCCHs.

or

S A non-combined control channel.

One BCCH plus nine CCCHs (no SDCCHs).

plus

S An SDCCH control channel.

Eight SDCCHs.

The network planner needs to combine the GSM circuit-switched signalling requirementswith the GPRS signalling requirements in order to plan the appropriate level of controlchannel support. This planning guide provides the planning rules that enable the networkplanner to evaluate whether a combined BCCH can be used, or if a non-combined BCCHis required. The decision to use a non-combined BCCH is a function of the combinedGPRS and GSM signalling load on the PAGCH, and on the number of SDCCH channelsrequired to support the GSM circuit-switched traffic.

The use of a combined BCCH is desirable because it may permit the use of only onetimeslot on a carrier that is used for signalling. A combined BCCH can offer four moreSDCCH blocks for use by the GSM circuit-switched signalling traffic. If more than anaverage of three CCCH blocks, or more than four SDCCH blocks, are required to handlethe signalling load, more control channel timeslots are required.

The planning approach for GPRS/GSM control channel provisioning is to determinewhether a combined BCCH is possible, given the combined GPRS and GSM load on theCCCH control channel. When more than three and less than nine CCCH blocks arerequired 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 tohandle the CCCH signalling. In this case, it may be advantageous to use a combinedBCCH again, depending on the CCCH and SDCCH load.

The determination of how many CCCH and SDCCH blocks are required to support thecircuit-switched GSM traffic is deferred to the network planning that is performed with theaid of the relevant planning information for GSM. The network planning that is performedusing the planning information determines how many CCCH and SDCCH blocks arerequired, and subsequently how many timeslots in total, are required to support theCCCH and SDCCH signalling load.

Downlink control channels

The downlink control channels are FCCH, SCH, BCCH and PAGCH. The PAGCHconsists of paging messages and access grant messages. The downlink control channelload is determined by evaluating the combined GSM circuit-switched signalling trafficload and the GPRS signalling traffic load on the PAGCH.

Uplink control channel

The uplink control channel is the random access channel (RACH). It is assumed that byadequate provisioning of the downlink part of the CCCH, the uplink part is implicitlyprovisioned with sufficient capacity.


30 Sep 20033�84


GMR-0168P02900W21-M

Air interface control channel dependencies

The number of air interface control channels required for a site is dependent on:

S Number of pages.

S Location updates.

S Short message services.

S Call loading.

S Set-up time.

Only the number of pages and access grants affect the CCCH. The other informationuses the SDCCH.


30 Sep 2003


68P02900W21-M

GMR-013�85

Number of CCCHs per BTS cell

The following factors should be considered when calculating the number of CCCHs perBTS cell:

S The CCCH channels comprise the paging and access grant channel (PAGCH) inthe downlink, and the random access channel (RACH) in the uplink. The PAGCHis subdivided into access grant channel (AGCH) and paging channel (PCH).

S If the CCCH has a low traffic requirement, the CCCH can share its timeslot withSDCCHs (combined BCCH). If the CCCH carries a high traffic, a non-combinedBCCH must be used:

� Combined BCCH (with four SDCCHs).

Number of CCCH blocks = 3.

Number of CCCH blocks reserved for AGCH ag_blks_res is 0 to 2.

Number of CCCH blocks available for PCH/AGCH is 3 to 1.

� Non-combined BCCH

Number of CCCH blocks = 9.

Number of CCCH blocks reserved for AGCH ag_blks_res is 0 to 7.

Number of CCCH blocks available for PCH is 9 to 2.

S When a non-combined BCCH is used, it is possible to add additional CCCH controlchannels (in addition to the mandatory BCCH on timeslot 0). These additionalCCCH control channels are added, in order, on timeslots 2, 4, and 6 of the BCCHcarrier, thus creating cells with 18, 27, and 36 CCCH blocks. These configurationswould only be required for very high capacity cells or in large location areas with alarge number of pages.

S Each CCCH block can carry one message. The message capacity of each CCCHblock is 4.25 messages/second.

S The AGCH is used to send immediate assignment and immediate assignmentreject messages for GSM and GPRS MSs. Each AGCH immediate assignmentmessage can convey channel assignments for up to two MSs. Each AGCHimmediate assignment reject message can reject channel requests from up to fourMSs.

S The PCH is used to send GSM and GPRS paging messages. Each PCH pagingmessage can contain pages for up to four MSs using TMSI or two MSs usingIMSI. If no paging messages are to be sent in a particular CCCH block, then animmediate assignment/immediate assignment reject message can be sent instead.

The current Motorola BSS implementation applies the following priority (highest tolowest) for downlink CCCH messages:

� Paging message (if not reserved for AGCH).

� Immediate assignment message.

� Immediate assignment reject message.

Thus, for example, if for a particular PAGCH sub-channel there are always pagingmessages (that is high paging load) waiting to be sent, no immediate assignmentor immediate assignment reject messages will be sent on that PAGCHsub-channel. Hence the option to reserve CCCH channels for AGCH.


30 Sep 20033�86


GMR-0168P02900W21-M

S It can normally be assumed that sufficient capacity exists on the uplink CCCH(RACH) once the downlink CCCH (PAGCH) is correctly dimensioned.

S 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 groupand only needs to listen to the PCH sub-channel corresponding to thatgroup. Paging group size is a trade off between MS idle-mode battery lifeand speed of access (for example, a lot of paging groups, means the MSneed only listen very occasionally to the PCH, but as a consequence it takeslonger to page that MS, resulting in slower call set-up as perceived by aPSTN calling party).

� Number of repetitions for MSs attempting to access the network on theRACH.

� Time MS must wait between repetitions on the RACH.

S Precise determination of the CCCH requirements may be difficult. However, anumber of statistics can be collected (for example ACCESS_PER_PCH,ACCESS_PER_AGCH) by the BSS and these may be used to determine theCCCH loading and hence perform adjustments.

Calculate the number of CCCHs per BTS cell

The provisioning of the PAGCH is estimated by calculating the combined load from theGPRS pages, GSM pages, GPRS access grant messages and GSM access grantmessages. The calculation is performed by adding the estimated GPRS and GSM pagingblocks for the BTS cell to the estimated number of GPRS and GSM access grant blocksfor the BTS cell, and dividing that sum by the CCCH utilization factor. The blocking factorand Erlang B table are then used to provide the number of CCCHs required.

NOTE Introducing the GPRS feature into a cell may cause noticeabledelays for paging in that cell. Similarly, a cell in a heavy pagingenvironment may be unable to support GPRS unless the pagingparameters for that cell are updated. Motorola advises operatorsto re-check the NPAGCH and NPCH equations provided here whenadding GPRS to a cell.


30 Sep 2003


68P02900W21-M

GMR-013�87

The following planning actions are required:

S Determine the number of CCCHs per BTS.

The average number of blocks required to support AGCH and PCH is given by:

NPAGCH = (NAGCH + NPCH) 1UCCCH

The average number of blocks required to support AGCH only is given by:

NAGCH � NAGCH_GSM � NAGCH_GPRS

The average number of blocks required to support AGCH for GSM traffic is givenby:

NAGCH_GSM �lAGCH

2 * 4.25

The average number of blocks required to support AGCH for GPRS traffic is givenby:

NAGCH_GPRS �RACH_Arrivals_per_sec * 1.1

4.25

Where:

RACH_Arrivals_per_sec �GPRS_Users * Avg_Sessions_per_user

3600

The access grant rate is given by:

lAGCH � lcall � lL � lS � lLCS

The call rate (calls per hour) is given by:

lcall �eT

The location update rate (LU per hour) is given by:

lL � L * eT

The SMS rate (SMSs per hour) is given by:

lS � S * eT

The LCS rate (LCSs per hour) is given by:

lLCS � LCS * eT

The average number of blocks required to support PCH only is given by:

NPCH � NPCH_GPRS � NPCH_GSM

The average number of blocks required to support GSM CS traffic TMSI pagingonly is given by:

NPCH_GSM �PGSM * (1 � LCS * LRMT)

4 * 4.25


30 Sep 20033�88


GMR-0168P02900W21-M

The average number of blocks required to support GSM CS traffic IMSI pagingonly is given by:

NPCH_GSM �PGSM * (1 � LCS * LRMT)

2 * 4.25

The number of paging blocks required at a cell to support GPRS is given by:

NPCH_GPRS �RACH_Arrivals_per_sec * 1.2

4.25


30 Sep 2003


68P02900W21-M

GMR-013�89

Where: UCCCH is: the CCCH utilization.

lAGCH the access grant rate (persecond).

GPRS_Users the number of GPRS users on acell.

Avg_Sessions_per_user the average number of sessionsoriginated by user (this includesthe sessions for signalling).

P the paging rate per second.

lcall the call arrival rate per second.

lL the location update rate persecond.

lS the number of SMSs per second.

e the number of Erlangs per cell.

T the average call length, inseconds.

PGSM the number of GSM circuitswitched traffic pages transmittedto a BTS cell per second.

PGPRS the number of GPRS pagestransmitted to a BTS cell persecond.

Table 3-7 Control channel configurations

Timeslot 0 Other timeslots Notes

1 BCCH + 3 CCCH+ 4 SDCCH

N x 8 SDCCH One combined BCCH. The other timeslotmay or may not be required, depending onthe support of circuit-switched trafficwhere the value of N can be >= 0.

1 BCCH + 9 CCCH N x 8 SDCCH Non-combined BCCH. The value of N is>= 1.

1 BCCH + 9 CCCH N x 8 SDCCH,9 CCCH

Non-combined BCCH. This is an exampleof one extra timeslot of CCCHs added insupport of GPRS traffic. The value of N is>= 1.


30 Sep 20033�90


GMR-0168P02900W21-M

Number of SDCCHs per BTS cellDetermining the SDCCH requirement is an important part of the planning process. TheSDCCH is where a large portion of call set-up messaging takes place. As the number ofcalls taking place in a BTS increases, greater demand is placed on the control channelfor call set-up.

The following factors should be considered when calculating the number of SDCCH perBTS cell:

S To determine the required number of SDCCHs for a given number of TCHs percell, the call, location update, and SMS (point to point) rates must be determined.

Refer to the equations below for information on calculating these rates. Oncethese rates are determined, the required number of SDCCHs for the given numberof TCHs can be determined. Refer to the equations below for information oncalculating the required number of SDCCHs.

S The rates for SMS are for the SMSs taking place over an SDCCH. For MSsinvolved in a call, the SMS may take place over the TCH, and may not require theuse of an SDCCH.

S Calculating the number of SDCCHs required is necessary for each cell at a BTSsite.

S The equation below for NSDCCH is used to determine the average number ofSDCCHs.

S There is a limit of 44 or 48 SDCCHs (depending on whether control channels arecombined or not) per cell. This may limit the number of supportable TCHs within acell.

S A change in the call model may also affect the number of SDCCHs (andsupportable TCHs) required. The formula should then be used to calculate thenumber of SDCCHs needed.

S The Number of Erlangs in Table 3-8 and Table 3-9 is the number of Erlangssupported by a given cell, based on the number of TCHs in that cell. To determinethe number of Erlangs supported by a cell, use Erlang B.

S The call arrival rate is derived from the number of Erlangs (Erlangs divided by callduration).

S Use Erlang B (on the value of NSDCCH) to determine the required number ofSDCCHs necessary to support the desired grade of service.

S The number of location updates will be higher for sites located on the borders oflocation areas, as compared to inner sites of a location area. See Figure 3-57.

Figure 3-57 Location area diagram

LOCATION AREA

BORDER BTS =

INNER BTS =


30 Sep 2003


68P02900W21-M

GMR-013�91

Calculate the number of SDCCHs per BTS cell


S Determine the number of SDCCHs per BTS cell.

The average number of SDCCHs is given by:

NSDCCH = lcall * Tc � lLU * �TL � Tg�� lS * �TS � Tg�� lLCS * �TLCS � Tg�

Where: NSDCCH is: the average number of SDCCHs.

lcall the call arrival rate per second.

Tc the time duration for call set-up.

lLU the location update rate.

TL the time duration of location updates.

Tg the guard time for SDCCH.

lS the number of SMSs per second.

TS the time duration of SMS (short message serviceset-up).

lLCS the number of LCSs per second.

TLCS the time duration of LCS (location serviceset�up).


30 Sep 20033�92


GMR-0168P02900W21-M

Control channel configurations

Table 3-8 and Table 3-9 give typical control channel configurations based on the typicalBTS planning parameters given in Table 3-6.

Control channel configurations for non-border location area

Table 3-8 is for the non-border location area cell, where the ratio of location updates tocalls is 2.

Table 3-8 SDCCH planning for typical parameters (non-border location area)

Numberof

Numberof

Numberof

Numberof

Timeslot utilizationof

RTFsof

TCHsof

Erlangsof

SDCCHs Timeslot 0 Other timeslots

1 7 2.94 4 1 BCCH + 3 CCCH+ 4 SDCCH

2 14 8.20 8 1 BCCH + 9 CCCH 8 SDCCH

3 22 14.9 8 1 BCCH + 9 CCCH 8 SDCCH

4 30 21.9 12 1 BCCH + 3 CCCH+ 4 SDCCH

8 SDCCH

5 38 29.2 12 1 BCCH + 3 CCCH+ 4 SDCCH

8 SDCCH

6 45 35.6 16 1 BCCH + 9 CCCH 2 x 8 SDCCH

7 53 43.1 16 1 BCCH + 9 CCCH 2 x 8 SDCCH

8 60 49.6 20 1 BCCH + 9 CCCH 3 x 8 SDCCH

9 68 57.23 20 1 BCCH + 9 CCCH 3 x 8 SDCCH

10 76 64.9 20 1 BCCH + 9 CCCH 3 x 8 SDCCH

NOTE The CBCH reduces the number of SDCCHs by one and mayrequire another channel.


30 Sep 2003


68P02900W21-M

GMR-013�93

Control channel configurations for border location area

Table 3-9 is for the border location area cell, where the ratio of location updates to calls is7.

Table 3-9 SDCCH planning for typical parameters (border location area)

Numberof

Numberof

Numberof

Numberof

Timeslot utilizationof

RTFsof

TCHsof

Erlangsof

SDCCHs Timeslot 0 Other timeslots

1 6 2.28 8 1 BCCH + 9 CCCH 8 SDCCH

2 14 8.20 12 1 BCCH + 3 CCCH+ 4 SDCCH

8 SDCCH

3 21 14.0 16 1 BCCH + 9 CCCH 2 x 8 SDCCH

4 29 21.04 20 1 BCCH + 3 CCCH+ 4 SDCCH

2 x 8 SDCCH

5 36 27.3 24 1 BCCH + 9 CCCH 3 x 8 SDCCH

6 44 33.8 28 1 BCCH + 9 CCCH 4 x 8 SDCCH

7 51 41.2 36 1 BCCH + 9 CCCH 5 x 8 SDCCH

8 59 47.88 36 1 BCCH + 9 CCCH 5 x 8 SDCCH

9 66 55.3 40 1 BCCH + 9 CCCH 5 x 8 SDCCH

10 74 62.8 44 1 BCCH + 9 CCCH 6 x 8 SDCCH

NOTE There is a limit of 44 or 48 SDCCHs (depending on whethercontrol channels are combined or not) per cell.

GSR6 (Horizon II)GPRS traffic planning

30 Sep 20033�94


GMR-0168P02900W21-M

GPRS traffic planning

Determination of expected load

The planning process begins by determining the expected GPRS load (applied load) tothe system. The next step is to determine the effective load to the system by weightingthe applied load by network operating parameters. These parameters consist of theexpected BLock Error Rate (BLER) based on the cell RF plan, the protocol overhead(GPRS protocol stack, that is TCP/IP, LLC, SNDCP, RLC/MAC), the expected advantagefrom V.42bis compression and TCP/IP header compression, and the multislot operationof the mobiles and infrastructure.

The effective load at a cell is used to determine the number of GPRS timeslots requiredto provision a cell. The provisioning process can be performed for a uniform loaddistribution across all cells in the network or on an individual cell basis for varying GPRScell loads. The number of GPRS timeslots is the key piece of information that drives theBSS provisioning process in support of GPRS.

The planning process also uses network generated statistics, available after initialdeployment, for replanning a network. The statistics fall into two categories: PCU specificstatistics, and GSN (SGSN + GGSN) statistics.

Network planning flow

The remaining sections of this chapter are presented in support of the GPRS networkplanning:

S GPRS network traffic estimation and key concepts

This text is intended to introduce the key concepts involved in planning a network.Because GPRS introduces the concept of a switchable timeslot that can be sharedby both the GSM circuit-switched infrastructure and by the GPRS infrastructure,much of the following text is dedicated to the discussion of this topic.

S Air interface inputs to the planning process

This provides a table of inputs that can serve as a guide in the planning process.In subsequent planning sections, references are made to parameters in this tableof inputs. A key piece of information that is needed for the planning process is theRF cell plan. This subsection discusses the impact of different cell plans on theGPRS provisioning process, and how to use this information in order to determinethe number of GPRS timeslots that are required on a per cell basis.

GSR6 (Horizon II) GPRS network traffic estimation and key concepts

30 Sep 2003


68P02900W21-M

GMR-013�95

GPRS network traffic estimation and key concepts

Introduction to the GPRS network traffic estimation and key concepts

The GPRS network planning is fundamentally different from the planning of circuitswitched networks. One of the fundamental reasons for the difference is that a GPRSnetwork allows the queuing of data traffic instead of blocking a call when a circuit isunavailable. Consequently, the use of Erlang B tables for estimating the number of trunksor timeslots required is not a valid planning approach for the GPRS packet dataprovisioning process.

The GPRS traffic estimation process starts by looking at the per cell GPRS data trafficprofile such as fleet management communications, E-mail communications, webbrowsing, and large file transfers. Once a typical data traffic profile mix is determined, therequired network throughput per cell can be calculated as measured in kbits per second.The desired network throughput per cell is used to calculate the number of GPRStimeslots required to support this throughput on a per cell basis.

The estimated GPRS network delay is derived based on computer modelling of the delaybetween the Um interface and the Gi interface. The results are provided in this planningguide. The network delay can be used to determine the mean or average time it takes totransfer a file of arbitrary length. In order to simulate the delay, the following factors areconsidered:

S Traffic load per cell.

S Mean packet size.

S Number of available GPRS timeslots.

S Distribution of CS1, CS2, CS3 and CS4 rate utilization.

S Distribution of Mobile Station (MS) multislot operation (1, 2, 3 or 4).

S BLER.

GSR6 (Horizon II)GPRS network traffic estimation and key concepts

30 Sep 20033�96


GMR-0168P02900W21-M

Use of timeslots

The use of timeslots for GPRS traffic is different from how they are used in the GSMcircuit-switched case. In circuit-switched mode, an MS is either in idle mode or dedicatedmode. In dedicated mode, a circuit is assigned through the infrastructure, whether or nota subscriber is transporting voice or data. In idle mode, the network knows where the MSis, but there is no circuit assigned. In GPRS mode, a subscriber uses the infrastructuretimeslots for carrying data only when there is data to be sent. However, the GPRSsubscriber can be attached and not sending data, and this still presents a load to theGSN part of the GPRS system, which must be accounted for when provisioning theGPRS infrastructure, that is, in state 2 as explained below.

The GPRS mobile states and conditions for transferring between states are provided inTable 3-10 and shown in Figure 3-58 in order to specify when infrastructure resourcesare being used to transfer data. The comment column specifies what the load is on theinfrastructure equipment for that state, and only in state 3 does the infrastructureequipment actually carry user data.

The infrastructure equipment is planned such that many more MSs can be attached tothe GPRS network, that is in state 2, than there is bandwidth available to simultaneouslytransfer data. One of the more significant input decisions for the network planningprocess is to determine and specify how many of the attached MSs are activelytransmitting data in the Ready state 3. In the Standby state 2, no data is beingtransferred 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 theMS is in state 1, the only required infrastructure equipment support is the storage of MSrecords 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 (or higher) combines thecircuit-switched and GPRS control channels together as BCCH/CCCH. This chapterprovides planning information for determining the BCCH/CCCH control channel capacityneeded.


30 Sep 2003


68P02900W21-M

GMR-013�97

Table 3-10 MM state model of MS

Presentstate #

Presentstate

Next state Condition forstate transfer

Comments(present state)

1 IDLE READY(3) GPRS Attach Subscriber is notmonitored by theinfrastructure, that is notattached to GPRS MM,and therefore does notload the system otherthan the HLR records.

2 STANDBY READY(3) PDU Transmission Subscriber is attached toGPRS MM and is beingactively monitored by theinfrastructure, that is MSand SGSN establish MMcontext for subscriberIMSI, but no datatransmission occurs inthis state.

3 READY IDLE(1) GPRS Detach Data transmissionthrough the infrastructureoccurs in the Ready state

3 READY STANDBY(2) Ready timer expiry

or

force to Standby

(The network or theMS can send aGMM signallingmessage to invokeforce to Standby.)

The ready timer (T3314)default time is 32seconds. The timer valuecan be modified duringthe signalling process byMS request.

2 � 60 s in 2 s increments

or

61 � 1800 s in 60 sincrements.


30 Sep 20033�98


GMR-0168P02900W21-M

The MS and SGSN state models are illustrated in Figure 3-58.

Figure 3-58 MM state models for MS and SGSN

orCancel Location

GPRS Attach

READY timer expiryorForce to STANDBY

STANDBY timerexpiry

GPRS Detach GPRS Attach

PDU reception

GPRS Detachor

Cancel Location

MM State Model of MS MM State Model of SGSN

IDLE

READY

STANDBY

IDLE

READY

STANDBY

READY timer expiryorForce to STANDBYorAbnormal RLC condition

STANDBY timer expiry

PDU transmission


30 Sep 2003


68P02900W21-M

GMR-013�99

Dynamic timeslot mode switching

This section proposes a network planning approach when utilizing dynamic timeslotmode switching of timeslots on a carrier with GPRS timeslots. The radio interfaceresources can be shared dynamically between the GSM circuit-switched services andGPRS data services as a function of service load and operator preference.

The timeslots on any carrier can be reserved for GPRS use, for circuit-switched useonly, or allocated as switchable. Motorola uses the term switchable to describe atimeslot that can be dynamically allocated for GPRS data service or for circuit-switchedservice.

The timeslot allocation is performed such that the GPRS reserved timeslots are allocatedfor GPRS use before switchable timeslots. GSM circuit-switched timeslots are allocatedto the circuit-switched calls before switchable timeslots. The switchable timeslots areallocated with priority given to circuit-switched calls.

Motorola has a BSS feature called Concentration at BTS. This feature enables theterrestrial backhaul resources to be dynamically assigned over the E1 links between theBSC and BTS. The terrestrial backhaul resources are managed and allocated inincrements of 16 kbit/s.

When the concentration at BTS feature is enabled, it is important to have a sufficientlevel of terrestrial backhaul resources provisioned. This feature has the concept ofreserved and switchable BSC to BTS resources. This concentration at BTS featureallows the network planner to allocate dedicated or reserved backing pools to reservedGPRS timeslots, so that there is a guaranteed level of terrestrial backing available toGPRS traffic. It is recommended that the reserved backing pool is made large enough toserve the expected busy hour GPRS traffic demands on a per BTS site basis.

It is possible for the circuit-switched part of the network to be assigned all of theswitchable terrestrial backing under high load conditions and, in effect, block GPRSaccess to the switchable timeslots at the BTS. In addition, the reserved GPRS pool ofbacking resources can be taken by the circuit-switched part of the network when BSC toBTS E1 outages occur, and when emergency pre-emption type of calls occur and cannotbe served with the pool of non-reserved resources. The concentration at BTS featuredoes not take the last switchable backhaul timeslot until all of the GPRS traffic has beentransmitted, in the case when there are no provisioned reserved GPRS timeslots at thecell site. Provisioning rules for the concentration at BTS feature are described in Chapter2.


30 Sep 20033�100


GMR-0168P02900W21-M

Background and discussion

From GSR6 onwards, multiple carriers per cell can be configured with GPRS timeslots bythe operator for GPRS traffic handling capability. By doing so, it can meet the expandingbase of GPRS subscribers and enhance performance, that is, increase data throughput.

There are two options to configure GPRS timeslots on multiple carriers per cell:

1. Configure for performance.

This is the network default option. Configure for performance provides the networkwith the capability to configure all the reserved and switchable GPRS timeslots in acell contiguously to maximize performance. The contiguous GPRS timeslotsconfigured on a carrier in a cell provide ease in scheduling packet data and thecapability to service multiple timeslot GPRS mobiles.

2. Operator specified.

This provides the customer with the flexibility to configure reserve and switchableGPRS timeslots on a per carrier basis in a cell.

The carrier with GPRS timeslots can also be the BCCH/CCCH carrier or not, which isdetermined by the use_bcch_for_gprs element. See Table 3-11.

Table 3-11 Options for use_bcch_for_gprs element

Value of use_bcch_for_gprs Configuration

0 Do not use BCCH carrier for GPRStimeslots.

1 No preference.

2 Use BCCH carrier for GPRS.

The BSS supports a minimum of zero to a maximum of 30 GPRS timeslots per cell. Thesum of reserved and switchable GPRS timeslots should not exceed 30.

When configuring timeslots in a cell, carriers with 32K TRAU enabled with higher prioritywhen configuring GPRS timeslots. The only exception to this rule is when theuse_bcch_for_gprs elements is set to 2, in which case the BCCH carrier will be the firstcarrier in the cell configured with GPRS timeslots.

Reserved GPRS timeslots are placed above the switchable GPRS timeslots on the airinterface TDMA frame.

The GPRS carriers can be provisioned to carry a mix of circuit-switched traffic and GPRStraffic. There are three provisioning choices combined with timeslot configuration optionsselected above:

• Reserved GPRS timeslots allocated only for GPRS use.

• Switchable timeslots dynamically allocated for either GSM circuit-switched traffic orGPRS traffic (designated as switchable timeslots by Motorola).

• Remaining timeslots on the carrier with GPRS timeslots, if any, only forcircuit-switched use.


30 Sep 2003


68P02900W21-M

GMR-013�101

Planning Goals � reserved vs switchable timeslots

The network planner may have some of the following network planning goals in mindwhen trying to determine when to use reserved timeslots versus when to useswitchable timeslots:

S Use reserved timeslots to guarantee a minimum GPRS quality of service.

S Use switchable timeslots to provide low circuit mode blocking and high GPRSthroughput when the voice busy hour and the GPRS busy hour do not coincide.

S Use switchable timeslots to provide higher GPRS throughput without increasingthe circuit-switched blocking rate.

If all the GPRS timeslots are provisioned as switchable, the last available timeslotis not given to a circuit-switched call until transmission of all the GPRS traffic onthat last timeslot is completed. Therefore, there is a circuit-switched blocking onthat last timeslot on the cell until the timeslot becomes free.

S Use switchable timeslots to provide some GPRS service coverage in low GPRStraffic volume areas.

S Use switchable timeslots to provide extra circuit-switched capacity in spectrumlimited areas.

In order to make the decision on how to best allocate reserved and switchabletimeslots, the network planner needs to have a good idea of the traffic level for bothservices. The proposal in this planning guide is to drive the allocation of switchabletimeslots 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 hourtraffic level, as measured in Erlangs. Once the circuit-switched information is known, thepotential impact on switchable timeslots can be analysed. The GPRS quality of servicecan be planned by counting the number of available reserved GPRS timeslots, and byevaluating the expected utilization of the switchable timeslots by the circuit-switchedpart of the network during the GPRS busy hour.


30 Sep 20033�102


GMR-0168P02900W21-M

Carrier timeslot allocation examples

The following configuration examples explore different ways to configure timeslots in acell.

In the examples, the following annotations are used:

B = BCCH/CCCH timeslot for GPRS/GSM signalling.

SD = SDCCH timeslot for GSM signalling.

R = Reserved GPRS timeslot.

S = Switchable timeslot.

T = Circuit-switched use only timeslots.

NOTE When two carriers meet the same configuration criteria(non-BCCH 32K, for example), the carrier with the higher carrierID is used first (for GPRS).

Example 1

There are 15 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 5 carriercell and the use_bcch_for_gprs = 2. The GPRS timeslots are configured contiguouslyfor performance which means allocating as many GPRS timeslots as possible (up to 8)on non�BCCH carriers.

In this example, the BCCH carrier is required to be used as the first carrier for equippingGPRS timeslots due to use_bcch_for_gprs being set to 2. After the BCCH carrier hasbeen allocated, the BTS first chooses non-BCCH carriers with 32K TRAU enabled to beused for GPRS traffic and allocates as many GPRS timeslots as possible (up to 8).

Reserved GPRS timeslots are allocated before switchable GPRS timeslots, as describedpreviously.

Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 16K B SD R R R R R R

Non-BCCH 32K S S S S R R R R

Non-BCCH 32K S S S S S S S S

Non-BCCH 16K T T T T T S S S

Non-BCCH 16K T T T T T T T T


30 Sep 2003


68P02900W21-M

GMR-013�103

Example 2

There are 15 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 5 carriercell and the use_bcch_for_gprs = 1. The GPRS timeslots are configured contiguouslyfor performance.

In this example, the BCCH carrier is not preferred to be used as the first carrier forGPRS traffic due to use_bcch_for_gprs being set to 1. So TS2 to TS7 on the BCCHcarrier is allocated to circuit switch TCH only. Then the BTS first chooses non-BCCHcarriers with 32K TRAU enabled to be used for GPRS traffic and allocates as manyGPRS timeslots as possible (up to 8).



BCCH 16K B SD T T T T T T

Non-BCCH 32K R R R R R R R R

Non-BCCH 32K S S S S S S R R

Non-BCCH 16K T S S S S S S S

Non-BCCH 16K T T T T T T S S

Example 3

There are 14 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 5 carriercell. The use_bcch_for_gprs = 0, max_gprs_ts_carrier= 6, and min_gprs_ts_carrier= 2. The GPRS timeslots are configured as �operator specified�.

In this example, the BCCH carrier is not permitted to be used as the carrier for GPRStraffic due to use_bcch_for_gprs being set to 0. So TS2 to TS7 on the BCCH carrier isallocated to circuit switch TCH only. Then the BTS first chooses non-BCCH carriers with32K TRAU enabled to be used for GPRS traffic and allocates as many GPRS timeslotsas possible on these carriers. GPRS timeslots allocated on each carrier are in the rangebetween min_gprs_ts_carrier and max_gprs_ts_carrier.




Non-BCCH 32K T T R R R R R R

Non-BCCH 32K T T S S R R R R

Non-BCCH 16K T T S S S S S S



30 Sep 20033�104


GMR-0168P02900W21-M

Example 4

There are 14 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 6 carriercell. The use_bcch_for_gprs = 0, max_gprs_ts_carrier= 6, and min_gprs_ts_carrier= 2. The GPRS timeslots are configured as �operator specified�.





Non-BCCH 32K T T R R R R R R

Non-BCCH 32K T T S S R R R R




Example 5

There are 8 switchable GPRS timeslots and 4 reserved GPRS timeslots in a 5 carrier celland the use_bcch_for_gprs = 2, max_gprs_ts_carrier= 4, and min_gprs_ts_carrier= 2. The GPRS timeslots are configured as �operator specified�. The BCCH carrier has32K TRAU enabled.

In this example, the BCCH carrier is required to be used as the first carrier for equippingGPRS timeslots due to use_bcch_for_gprs being set to 2 and the GPRS timeslotsallocated on the BCCH carrier must be between the min_gprs_ts_carrier andmax_gprs_ts_carrier values. Then the BTS chooses non-BCCH carriers with 32KTRAU enabled to be used for GPRS traffic and allocates as many GPRS timeslots aspossible on these carriers. GPRS timeslots allocated on each carrier are in the rangebetween min_gprs_ts_carrier and max_gprs_ts_carrier. For the remaining carriers,the GPRS timeslots allocated on each must also be in the range betweenmin_gprs_ts_carrier and max_gprs_ts_carrier.



BCCH 32K B SD T T R R R R

Non-BCCH 32K T T T T S S S S





30 Sep 2003


68P02900W21-M

GMR-013�105

Example 6

There are 8 switchable GPRS timeslots and 4 reserved GPRS timeslots in a 5 carrier celland the use_bcch_for_gprs = 0, max_gprs_ts_carrier= 4, and min_gprs_ts_carrier =2. The GPRS timeslots are configured as �operator specified�.





Non-BCCH 32K T T T T R R R R




Example 7

There are 15 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 5 carriercell and the use_bcch_for_gprs = 2. The GPRS timeslots are configured contiguouslyfor performance, which means allocating as many GPRS timeslots as possible (up to 8)on non-BCCH carriers. The BCCH carrier has 32K TRAU enabled.

In this example, the BCCH carrier is required to be used as the first carrier for equippingGPRS timeslots due to use_bcch_for_gprs being set to 2. After the BCCH carrier hasbeen allocated, the BTS first chooses non-BCCH carriers with 32K TRAU enabled to beused for GPRS traffic and allocates as many GPRS timeslots as possible (up to 8) onthese carriers.



BCCH 32K B SD R R R R R R

Non-BCCH 32K S S S S R R R R

Non-BCCH 32K S S S S S S S S

Non-BCCH 16K T T T T T S S S



30 Sep 20033�106


GMR-0168P02900W21-M

BSS timeslot allocation methods

The BSS algorithm that is used in order to determine allocation of switchable timeslotsgives priority to circuit-switched calls. Consequently, if a switchable timeslot is being usedby a GPRS mobile and a circuit-switched call is requested after all other circuit switchedtimeslots are used, the BSS takes the timeslot away from the GPRS mobile and gives itto the circuit-switched mobile, except when the switchable timeslot to be stolen is the lastGPRS timeslot in the cell and the protect_last_ts element is enabled.

The switchable timeslot is re-allocated back to the GPRS mobile when the circuitswitched call ends. The number of reserved GPRS timeslots can be changed by theoperator in order to guarantee a minimum number of dedicated GPRS timeslots at alltimes. The operator provisions the GPRS timeslots on a carrier by selecting the numberof timeslots that are allocated as reserved and switchable, and not by specificallyassigning timeslots on the carrier.

Motorola has implemented an idle circuit-switched parameter that enables the operator tostrongly favour circuit-switched calls from a network provisioning perspective. By settingthe idle parameter to 0, this capability is essentially turned off.

The use of the idle circuit-switched parameter is as follows:

When a circuit-switched call ends on a switchable GPRS timeslot and the number of idlecircuit-switched timeslots is greater than an operator defined threshold, the BSSre-allocates the borrowed timeslot for GPRS service. When the number of idle timeslotsis less than or equal to a programmable threshold, the BSS does not allocate the timeslotback for GPRS service, even if it is the last available timeslot for GPRS traffic.

Stolen timeslots

A switchable timeslot can be �stolen� at any time for use by a CS call, except when theswitchable timeslot to be stolen is the last GPRS timeslot in the cell and theprotect_last_ts element is enabled.

When a switchable timeslot needs to be stolen for use by a CS call, the switchabletimeslot to be stolen is the last GPRS timeslot in the cell, and the protect_last_tselement is enabled, the timeslot will only be stolen if there is no data transfer active orqueued for the timeslot.

If there are any reserved GPRS timeslots in the cell, the switchable timeslots are notprotected from being stolen for use by circuit-switched calls.

The BSS supports dynamic switching between switchable timeslots and circuit-switchedtimeslots and vice versa.

Switchable GPRS timeslots are stolen starting with the lowest numbered GPRS timesloton a carrier to maintain continuous GPRS timeslots.

The BSS selects which switchable GPRS timeslot is stolen based on the following:

S 16K carrier with the least number of available SW GPRS timeslots (the carrierdoes not contain RES GPRS timeslots).

S 16K carrier with the least number of available SW GPRS timeslots (the carriercontains RES GPRS timeslots).

S 32K carrier with the least number of available SW GPRS timeslots (the carrierdoes not contain RES GPRS timeslots).

S 32K carrier with the least number of available SW GPRS timeslots (the carriercontains RES GPRS timeslots).


30 Sep 2003


68P02900W21-M

GMR-013�107

Contiguous timeslots

Multislot mobile operation requires that contiguous timeslots are available. The BSStakes the lowest numbered switchable timeslot in such a manner as to maintaincontiguous GPRS timeslots for multislot GPRS operation. The BSS attempts to allocateas many timeslots as requested in multislot mode, and then backoff from that number astimeslots are not available. For example, suppose that timeslots 3 and 4 are switchable,and timeslots 5,6, and 7 are GPRS reserved (see Figure 3-59). When the BSS needs tore-allocate a switchable timeslot from GPRS mode to circuit-switched mode, the BSSassigns timeslot 3 before it assigns timeslot 4 for circuit-switched mode.

Figure 3-59 provides a timeslot allocation with reserved and switchable timeslots.

Figure 3-59 Carrier with reserved and switchable GPRS timeslots

R R RS

TS0

S

TS7

R: Reserved PDCH.S: Switchable PDCH.Blank: Circuit-switched use only timeslots.

If the emergency call pre-emption feature is enabled, the BSS selects the air timeslotthat carries the emergency call from the following list (most preferable listed first):

1. Idle circuit-switched.

2. Idle or in-service switchable GPRS timeslot (from lowest to highest).

3. In-service circuit-switched.

4. Idle or in-service reserved GPRS timeslot (from lowest to highest).


30 Sep 20033�108


GMR-0168P02900W21-M

Provisioning the network with switchable timeslots

Provisioning the network with switchable timeslots can offer flexibility in the provisioningprocess for combining circuit-switched and GPRS service. This flexibility is in the form ofadditional available network capacity to both the circuit-switched and GPRS subscribers,but not simultaneously. Because the BSS favours circuit-switched use of the switchabletimeslots, the network planner should examine the demand for switchable timeslotsduring the circuit-switched busy hour and during the GPRS busy hour.

Normally, the operator provisions the circuit-switched radio resource for a particularGrade Of Service (GOS), such as 2%. This means that 2 out of 100 circuit-switched callsare blocked during the busy hour. If the operator chooses to use the new switchabletimeslot capability, it is now possible to share some GPRS timeslots between thecircuit-switched calls and the GPRS calls.

During the circuit-switched busy hour, the circuit-switched use of these switchabletimeslots may dominate their use. The circuit-switched side of the network has priorityuse of the switchable timeslots, and attempts to provide a better grade of service as aresult of the switchable timeslots being available.

The example in Table 3-12 assumes that the planning is being performed for a cell thathas two carriers. The first carrier is for circuit-switched only use as shown in Figure 3-60.The second carrier is a carrier with GPRS timeslots; all eight timeslots are configured asswitchable, as shown in Figure 3-61.

The table was created using the Erlang B formula in order to determine how many circuitswitched timeslots are required for a given grade of service. The table covers the rangeof 2 Erlangs to 9 Erlangs of circuit-switched traffic in order to show the full utilization oftwo carriers for circuit-switched calls. The purpose of the table is to show how the circuitswitched side of the network allocates switchable timeslots during the circuit-switchedbusy hour in an attempt to provide the best possible GOS, assumed to be 0.1% for thepurposes of this example.

The comments column in the table is used to discuss what is happening to the availabilityof switchable timeslots for GPRS data use as the circuit-switched traffic increases, asmeasured in Erlangs.

This example does show some Erlang traffic levels that cannot be adequately served bytwo carriers at the stated grade of service listed in the tables. This occurs at the 7 and 8Erlang levels for 0.1% GOS. In these cases, all of the switchable timeslots are used upon the second carrier in an attempt to reach a 0.1% GOS. For the 9 Erlang traffic level, 2carriers is not enough to serve the circuit-switched traffic at a 2% GOS. This wouldindicate a need for a second circuit-switched carrier, in addition to the first circuitswitched carrier and the carrier with GPRS timeslots.


30 Sep 2003


68P02900W21-M

GMR-013�109

Timeslot allocation for 2 carrier site (1 circuit-switched + 1 GPRS)

Figure 3-60 shows one circuit-switched carrier with one BCCH/CCCH timeslot, oneSDCCH timeslot, and six TCH timeslots.

Figure 3-60 1 circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots

TS0 TS7

B SD

B: BCCH/CCCH for GPRS/GSM signalling.SD: SDCCH for GSM signalling.Blank: Circuit-switched use only timeslots.

Figure 3-61 shows one carrier for GPRS traffic with all timeslots (8 TCHs) designated asswitchable.

Figure 3-61 One carrier, all timeslots (8 TCHs) designated as switchable

S S SS

TS0

S

TS7

S S S

S: Switchable TCH.


30 Sep 20033�110


GMR-0168P02900W21-M

Table 3-12 shows the switchable timeslot utilization.

Table 3-12 Switchable timeslot utilization

GOS Plannedcircuit

switchedErlangs/cell

Totalnumber of

circuitswitchedtimeslotsrequired,including

switchable

Number ofswitchabletimeslotsnecessaryto provide

GOS

Comments

2% 2 6 0 Outside busy hour timeperiods, the carrier mostlikely carries only GPRStraffic. Therefore, GPRSnetwork planning shouldbe performed, assumingthere are 8 timeslotsavailable for GPRS traffic.

0.1% 2 8 2 During circuit-switchedbusy hour, at least 2 of theswitchable timeslots areoccasionally used by thecircuit-switched side of thenetwork in an attempt toprovide the best possibleGOS � assumed to be inthe order of 0.1%.

2% 3 8 2 During the circuit-switchedbusy hour, 2 of theswitchable timeslots areoccasionally used by thecircuit-switched side of thenetwork in an attempt toprovide the 2% GOS.

0.1% 3 10 4 During the circuit-switchedbusy hour, 4 of theswitchable timeslots areoccasionally used by thecircuit-switched side of thenetwork in an attempt toprovide the best possibleGOS � assumed to be inthe order of 0.1%.

2% 4 9 3

0.1% 4 12 6

2% 5 10 4

0.1% 5 14 8 All of the switchabletimeslots are occasionallyused to provide the 0.1%GOS.

(continued)


30 Sep 2003


68P02900W21-M

GMR-013�111

GOS Plannedcircuit

switchedErlangs/cell

Totalnumber of

circuitswitchedtimeslotsrequired,including

switchable

Number ofswitchabletimeslotsnecessaryto provide

GOS

Comments

2% 6 12 6

0.1% 6 15 9 There are not enoughswitchable timeslots toprovide the 0.1% GOS.

2% 7 13 7


2% 8 14 8 All of the switchabletimeslots are occasionallyused to provide the 2%GOS.


2% 9 15 9 There are not enoughswitchable timeslots toprovide the 2% GOS



30 Sep 20033�112


GMR-0168P02900W21-M

Recommendation for switchable timeslot usage

The following recommendation is offered when using switchable timeslots. It is importantto determine the GOS objectives for circuit-switched traffic and QoS objectives for GPRStraffic prior to selecting the number of switchable timeslots to deploy.

During the circuit-switched busy hour, potentially all switchable timeslots are occasionallyused by the circuit-switched calls. The circuit-switched timeslot allocation mechanismcontinues to assign switchable timeslots as circuit-switched timeslots as thecircuit-switched traffic continues to increase. Therefore, if there is a minimum capacityrequirement for GPRS services, the network planner should plan the carrier with enoughreserved timeslots in order to handle the expected GPRS data traffic. This ensures thatthere is a minimum guaranteed network capacity for the GPRS data traffic during thecircuit-switched busy hour.

During the circuit-switched off busy hours, the switchable timeslots could be consideredas available for use by the GPRS network. Therefore, in the circuit-switched off busyhours, 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 switchabletimeslots by the circuit-switched services.

The circuit-switched busy hour and the GPRS busy hour should be monitored to see ifthey overlap when switchable timeslots are in use. If the busy hours overlap, anadjustment may be needed to the number of reserved timeslots allocated to the GPRSportion of the network in order to guarantee a minimum GPRS quality of service asmeasured by GPRS throughput and delay. Furthermore, one or more circuit-switchedcarriers may need to be added to the cell being planned or replanned so that theswitchable timeslots are not required in order to offer the desired circuit-switched gradeof service.

In conclusion, assume switchable timeslots are occasionally unavailable for GPRS trafficduring the circuit-switched portion of the network busy hour. Provision enough reservedtimeslots for GPRS traffic during the circuit-switched busy hour to meet the desiredminimum GPRS quality of service objectives, as measured by GPRS data throughput.


30 Sep 2003


68P02900W21-M

GMR-013�113

Timeslot allocation process on carriers with GPRS traffic

The following process is proposed when determining how best to allocate GPRStimeslots.

Step 1: Estimate reserved timeslot requirements

Determine how many reserved GPRS timeslots are needed on a per cell basis in order tosatisfy a GPRS throughput QoS. The GPRS reserved timeslots should equal the sum ofthe active and standby timeslots that are allocated to a carrier.

Step 2: Allocate switchable timeslots

Determine how many reserved GPRS timeslots are needed on a per cell basis. The useof switchable timeslots can potentially offer increased capacity to both the GPRS andcircuit�switched traffic if the traffic is staggered in time.

Step 3: Add an extra circuit-switched carrier

If there is a need to use some timeslots on the carrier with only GPRS timeslots to satisfythe circuit switched GOS objectives and the timeslot requirement overlaps with thenumber of reserved GPRS timeslots, consider adding another circuit-switched carrier tothe cell.

Step 4: Monitor network statistics

After deploying the GPRS timeslots on the cell, review the collected network statistics ona continuous basis in order to determine whether the reserved GPRS timeslots,switchable GPRS timeslots, and circuit-switched timeslots are truly serving the GOS andQoS objectives. As previously discussed, the use of switchable timeslots can offernetwork capacity advantages to both circuit-switched traffic and GPRS traffic as long asthe demand for these timeslots is staggered in time.

GSR6 (Horizon II)GPRS air interface planning process

30 Sep 20033�114


GMR-0168P02900W21-M

GPRS air interface planning process

Introduction to the GPRS air interface planning process

The air interface planning process uses the range of values listed in Table 3-13. Ifnetwork values are not available at the time a network is planned, typical orrecommended values are provided where appropriate. The minimum values are given forthe maximum capacity of a minimum system, and the typical values are used asstandard model parameters.

Table 3-13 Air interface planning inputs

Variable Minimumvalue

Typicalvalue

Maximumvalue

Assumptions/ variableuse

CS1

CS2

CS3

CS4

0 %

0 %

0 %

0 %

10%

50%

20%

20%

100 %

100 %

100 %

100 %

Coding schemepercentages aredetermined by the cellplan, mean TBF size anduse of Acknowledgemode. Refer to cell planTable 3-14, Table 3-15 andTable 3-16.

After the initial launch, theoperator needs to collectthe percentage of timeeach CS is used for all thecells with GPRS capability,and to adjust the systemplanning accordingly as anongoing optimizationprocess.

V.42 biscompression

ratio

1 2.5 4 A ratio of 1 means there isno compression and a ratioof 4 is the theoreticalmaximum, which is mostlikely never realized. Mostusers see a compressionadvantage in the range of 2to 3 over the air interfacebetween the MS and theSGSN.

BLER 0 10% 100% The BLock Error Rate(BLER) is largelydetermined by the cell RFplan. The typical value isan average rate. There areseparate BLERs for thevarious coding schemesthat are RF plan specific.

GSR6 (Horizon II) GPRS air interface planning process

30 Sep 2003


68P02900W21-M

GMR-013�115

Estimating the air interface traffic throughput

The GPRS data throughput estimation process given in this chapter is based upon thePoisson process for determining the GPRS mobile packet transfer arrivals to the networkand for determining the size of GPRS data packets generated or received by the GPRSmobiles.

A number of wired LAN/WAN traffic studies have shown that packet interarrival rates arenot exponentially distributed. Recent work argues that LAN traffic is much bettermodelled using statistically self-similar processes instead of Poisson or Markovianprocesses. Self-similar traffic pattern means the interarrival rates appear the same,regardless of the timescale at which it is viewed (in contrast to Poisson process, whichtends to be smoothed around the mean in a larger timescale). The exact nature ofwireless GPRS traffic pattern is not known due to lack of field data.

In order to minimize the negative impact of under-estimating the nature of the GPRStraffic, it is proposed in this planning guide to limit the mean GPRS cell loading value to50% of the system capacity. Using this cell loading factor has the following advantages:

S Cell overloading due to the bursty nature of GPRS traffic is minimized.

S The variance in file transit delay over the Um to Gi interface is minimized such thatthe delay can be considered a constant value for the purposes of calculating thetime to transfer a file of arbitrary size.

LAN/WAN wireline studies have also shown that even when statistically valid studies areperformed, the results come out very different in follow-up studies. It turns out that webtraffic patterns are very difficult to predict accurately and, therefore, it is highlyrecommended that the network planner makes routine use of the GPRS networkstatistics.

About the steps

The following steps 1 and 2 are used for dimensioning the system. Step 1 needs to beperformed prior to step 2 in order to calculate the number of GPRS timeslots that shouldbe provisioned on a per cell basis.

Steps 3 and 4 are optional. These steps are included in this section so that an over theair file transfer time can be calculated for any size file. The results from steps 3 and 4depend on the choices made in steps 1 and 2.


30 Sep 20033�116


GMR-0168P02900W21-M

Step 1: Choose a cell plan

Choose a cell plan in order to determine the expected BLER and percentage of time datais transferred at the CS1, CS2, CS3 and CS4 rate. The cell plan that is chosen for GPRSmay be determined by the plan currently in use for the GSM circuit-switched part of thenetwork. However, it may be necessary to change an existing cell plan used for GSMcircuit-switched in order to get better BLER performance for the GPRS part of thenetwork.

After the cell plan is chosen, the network planner can move on to step 2.

The PCU dynamically selects the best CS rate in order to maximize the GPRS datathroughput on a per mobile basis. The CS rate selection is performed periodically duringthe temporary block flow (TBF).

When planning frequency, it is required that there are no more than 48 frequencies in acell with multiple carriers supporting GPRS timeslots.

Simulations have been performed for two typical frequency hopping cell configurations.Results for a 1x3 cell reuse pattern with 2/6 hopping are shown in Table 3-14 (which ishopping on 2 carriers over 6 frequencies), and results for a 1x1 cell reuse pattern with2/18 hopping are shown in Table 3-15 (which is hopping on 2 carriers over 18frequencies).

Results for a non-hopping cell configuration with a TU-3 model is shown in Table 3-16,providing a chart of the cell coverage area and cell C/I performance for the non-hoppingcase. The following tables were created, based on the simulations, in order to indicatethe percentage of the time a particular CS rate would be chosen over another CS rateand at what mean BLER. The simulation results indicate that the higher data rate of theCS4 more than offsets its higher BLER rate in the majority of the cell coverage area,resulting in the CS4 rate being chosen most of the time.

Reviewing the following tables will show that under good cell C/I conditions, betterthroughput may be obtained by provisioning the GPRS timeslots on the BCCH carrier, asindicated by Table 3-17.

Table 3-14 1 x 3 2/6 hopping

Parameter CS1 rate CS2 rate CS3 rate CS4 rate

% Rate chosen 10 12 10 68

% Mean BLER 50 31 22 8

Table 3-15 1 x 1 2/18 hopping



% Mean BLER 56 37 27 10

Table 3-16 Non-hopping TU-3 model



% Mean BLER 65 59 41 3

Table 3-17 provides the cell C/I performance, as measured in dB, as a function of cellarea coverage for the TU-3 model.


30 Sep 2003


68P02900W21-M

GMR-013�117

Table 3-17 Cell coverage versus carrier to interface (C/I)

% cell coverage 90 80 70 60 50 40

C/I 12 16 18 20 22 24

The cell plans assume a regular cell reuse pattern for the geographic layout and for theallocation of frequencies. The computer simulation generated the above cell plan using atypical urban 3 kph model, a propagation law with a Radius (R) exponent of �3.7 and ashadowing function standard deviation of 5 dB.

NOTE The numbers shown in the above tables are for referencepurposes only. The operator should collect the usage figures ofeach CS at all GPRS-enabled sites after the system launch andadjust the planning accordingly.The collection of CS usage information should be considered aspart of the ongoing system optimization process.

If non-regular patterns are used, a specific simulation study may be required to match theparticular cell characteristics. The simulation process is outside the scope of this planningguide and the network planner should contact Motorola for additional simulation results.

Step 2: Estimate timeslot provisioning requirements

Step 2 determines the number of GPRS timeslots that need to be provisioned on a percell basis. Timeslot provisioning is based on the expected per cell mean GPRS trafficload, as measured in kbit/s. The GPRS traffic load includes all SMS traffic routed throughthe GSN. The SMS traffic is handled by the GPRS infrastructure in the same manner asall other GPRS traffic originating from the PDN. The cell BLER and CS ratecharacteristics chosen in step 1 provide the needed information for evaluating thefollowing equation:

No_PDCH_TS � Roundup� Mean_traffic_loadTS_Data_Rate * Mean_load_factor

�

NOTE The above equation is based on the DL traffic load and it isassumed that the DL provisioning would be sufficient to handleUL traffic, without additional provisioning.

Mean_traffic_load for each cell can be calculated using the following formula:

Mean_traffic_load �

(Avg_Sessions_per_sub * Data_per_sub_per_session * GPRS_sub_per_cell)3600


30 Sep 20033�118


GMR-0168P02900W21-M

Where:

TS_Data_Rate � �%CS1100

* (1 � CS1BLER) * 9.05 * �1 � 323�� %CS2

100* (1 � CS2BLER) * 13.4 * �1 � 3

33��

� �%CS3100

* (1 � CS3BLER) * 15.6 * �1 � 339�� %CS4

100* (1 � CS4BLER) * 21.4 * �1 � 3

53��

and: Mean_traffic_load is: the mean traffic load, as measuredin kbit/s, is defined at the LLC layer,therefore all the higher layer protocoloverheads (for example, TCP, UDP,IP, SNDCP, LLC) are encapsulatedin this load figure.

No_PDCH_TS the number of timeslots per cell,maximum 8.

%CS1 the percentage of time datatransmission occurs using the CS1coding scheme.

CS1BLER the mean BLER rate for CS1.







3/23 the CS1 RLC/MAC overheadpercentage, that is 20 bytes payload.




Mean_load_factor the mean load factor for the numberof active timeslots to provision at acell. The recommended value is 0.5(50%) of the number of GPRStimeslots provisioned at the cell.

Avg_Sessions_per_sub the number of average datasessions originated by a MS in a cellin a busy hour.

Data_per_sub_per_session the amount of data transmitted by aMS in kbits per session.

GPRS_subs_per_cell the number of GPRS subscribersunder a cell in a busy hour.


30 Sep 2003


68P02900W21-M

GMR-013�119

Number of timeslots

The number of PDCH timeslots calculated in step 2 denotes the number of timeslots thatneed to be provisioned on the cell to carry the mean traffic load on the cell. TheMean_load_factor of 50% has been applied to the traffic load to account for any surges inthe data traffic and to carry packet switched signalling traffic.

It is important to differentiate between the required number of timeslots processed at anyinstance in time and the total provisioned timeslots because it directly affects theprovisioning of the communication links and the PCU hardware. The active timeslots aretimeslots that are simultaneously carrying data being processed by the PRP on the PCUat any instance in time. From GSR6, however, it is possible to originate PS calls on eachof the 1080 timeslots simultaneously. The PCU will rapidly multiplex all the timeslots witha maximum of 270 timeslots at any instance in time. For example, if there are MSs oneach of 1080 timeslots provisioned on the air interface, the PCU will process timeslots in4 sets of 270 timeslots, with switching between sets occurring every block period.

Hence, unlike in pre-GSR6 releases where sessions could only be originated on 270timeslots (assuming that all 9 PRPs are configured on the PCU) at any instance and theother timeslots behaved as standby timeslots, from GSR6 onwards all timeslots canpotentially carry traffic. However, the throughput offered by PCU still stands at 270 TS,which essentially means that there will be degradation in the data rates experienced bythe user when the PCU is loaded with data sessions on more than 270 timeslots.

The use of timeslots processed at any instance and total provisioned timeslots enablesseveral cells to share the PCU resource. While one cell is experiencing a high loadcondition, using all eight GPRS timeslots for instance, another cell operating below itsmean load averages out the GPRS traffic load at the PCU.

The E1s between the BTS and BSC must be provisioned to handle the number oftimeslots calculated above because all of the timeslots can become active under highload conditions.


30 Sep 20033�120


GMR-0168P02900W21-M

Step 3 (optional): Calculate the optimum file size

Step 3 is optional, and the results can be used in optional step 4. Step 3 is intended to beused as an aid in determining the size of a file that is to be transferred as an LLC PDUfrom the mobile to the SGSN.

The file size consists of the application file to be transferred, which includes anyapplication-related overhead. In addition to the application file, there is transport andnetwork layer protocol overhead, TCP and IP. Finally, there is GPRS link layer control(LLC) and sub network convergence (SNDCP) protocol overhead. The application fileplus all of the protocol overhead summed together makes up the one or more LLC_PDUframes that constitute the file to be transferred.

The percentage of protocol overhead depends on the transport layer used, such as TCPor UDP. For example, the TCP/IP protocol overhead is 40 bytes when TCP/IP headercompression is not used. When TCP/IP header compression is used, the TCP/IP headercan be reduced to 5 bytes from 40 bytes after the first LLC frame is transferred. The useof header compression continues for as long as the IP address remains the same.

Figure 3-62 illustrates a typical LLC_PDU frame with the user application payload and allof the protocol overhead combined for the case of no TCP/IP header compression.

Figure 3-62 LLC_PDU frame layout

4207 2 20

LLC SNDCP IP TCP APPLICATION CRC

64 BYTES < L < 1580 BYTES

If V.42bis application data compression is used, the effective file size for transmission isreduced by the data compression factor which can range from 1 to 4. Typically, V.42bisyields a 2.5 compression advantage on a text file, and close to no compressionadvantage (factor = 1) on image files and very short files:

File_size_LLC �

ApplnV.42bis_factor

� roundup� ApplnV.42bis_factor * LLC_payload

� * protocol_overhead

Where: File_size_LLC is: The file size in bytes to betransferred, measured at the LLClayer.

Appln The user application data file size,measured in bytes.

LLC_payload The maximum LLC PDU payload of1527 bytes.

protocol_overhead The protocol overhead forTCP/IP/SNDCP/LLC/CRC is53 bytes without headercompression, and 18 bytes withheader compression.

V.42bis_factor Application data compression isover the range of 1 to 4, a typicalvalue is equal to 2.5.


30 Sep 2003


68P02900W21-M

GMR-013�121

Step 3 example calculation

A 3 kbyte application file transfer requires the following number of bytes to be transferredat 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 header is not compressed, and all subsequent LLC_PDUs arecompressed. For this size file of 3000 bytes, only 2 LLC_PDU transmissions are requiredso the File_size_LLC is:

File_size_LLC = 3000 + 53+18 = 3071 bytes


30 Sep 20033�122


GMR-0168P02900W21-M

Step 4 (optional): Calculate file transit times

The network planner can use step 4 to determine how long it takes to transfer a file of anarbitrary size over the Um to Gi interface. The application file is segmented into LLC PDUframes as illustrated previously. The File Transit Delay (FTD) is calculated using thefollowing information: total number of RLC blocks of the file, BLER, number of timeslotsused during the transfer, and mean RLC Transit Delay (RTD) value:

FTD � RTD � RLC_Blocks * 0.02 * (1 � CSBLER)mslot

Where: FTD is: the file transit delay measured in seconds.

RTD the transit delay time from the Um interface tothe Gi interface for a file size of only oneRLC/MAC block of data. RTD is estimated to be0.9 s when the system running at 50% capacity.This parameter will be updated when field testdata is available.

RLC_Blocks the total number of RLC blocks of the file. Thiscan be calculated by dividing file_size_LLC bythe corresponding RLC data size of 20 bytes forCS1, 30 bytes for CS2, 36 bytes for CS3 and50 bytes for CS4.

mslot the mobile multislot operating mode; the valuecan be from 1 to 4.

CSBLER the BLER for the specific CS rate. The value isspecified in decimal form. Typical values rangeform 0.1 to 0.2.

The above equation does not include the effects of acknowledgement messages. Thereason is that the largest effect is in the uplink direction, and it is expected that thedownlink direction will dominate the cell traffic. The DL sends an acknowledgementmessage on an as-needed basis, whereas the uplink generates an acknowledgementmessage every 2 out of 12 RLC_Blocks. It is expected that the downlinkacknowledgement messages will not significantly effect the file transit delay in thedownlink direction.

The RTD parameter is directly correlated to the system utilization and the mean packetsize. When the cell approaches its throughput capacity limit, the RTD value increasesdramatically, and the infrastructure starts to drop packets. Simulation data indicates thatwhen traffic load is minimal, the RTD value is at a minimum limit of 0.7 seconds. At a cellthroughput capacity of 50%, the RTD increases to 0.9 seconds. It is recommended thatcell throughput provisioning be performed at the mean cell capacity level of 50%.Provisioning for a mean cell throughput greater than 50% greatly increases the likelihoodof dropped packets, and RTD values of over 2.6 seconds can occur. The assumptionsused in the simulation to determine the RTD value at a mean cell throughput level of 50%are: 25% of the cell traffic at the CS1 rate and 75% of the cell traffic at the CS2 rate,BLER 10%, mobiles multislot distribution 1:2:3:4 = 20:50:20:10, 8 PDCH, DL, meanLLC_PDU packet size of 435 bytes.


30 Sep 2003


68P02900W21-M

GMR-013�123

Step 4 example calculation

A 3 kbyte application file transit time at the CS2 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) * 0.02 * 1.1 / 1 = 3.2 seconds

Where: File_size_LLC is: = 3106 bytes(as calculated in the previousexample).

CS2 payload = 30 bytes.

Air time for one RLC/MACblock

= 0.02 seconds.

(1 + CSBLER) = 1.1.

Multislot operation = 1.


30 Sep 20033�124


GMR-0168P02900W21-M

GPRS data rates

NOTE This information is provided for reference only. It may be used tocalculated timeslot data rates at each layer, if required.These are purely theoretical calculated values, based on theprotocol overheads at each layer. They do not necessarilyrepresent the data rates that the system can support.

Table 3-18 and Table 3-19 provide the data rates by application at each layer in theGPRS stack. The following assumptions have been made to arrive at the numbers:

S Mean IP packet size of approximately 300 bytes.

S LLC in unacknowledged mode.

S V42.bis data compression is disabled (if V42.bis is enabled, the data rate is highlyvariable depending on data contents).

S Data is for standard downlink and dynamic allocation uplink (fixed allocation uplink~ 2% lower data rate).

S For this analysis, the impact of overhead messaging (local area update, forexample) is considered insignificant.

S Increased efficiencies gained from lowered overhead as a result of using highernumbers of timeslots has not been calculated for this analysis.

S C/I for each coding scheme is sufficient to support error free transport.

In Table 3-18 and Table 3-19:

H/C = Header compression.

TS = Timeslot.

CSn = Coding scheme n, where n = 1 to 4.


30 Sep 2003


68P02900W21-M

GMR-013�125

Table 3-18 GPRS data rates (kbit/s) with UDP

ProtocolStack

CS1, 1 TS CS1, 2 TS CS1, 3 TS CS1, 4 TS

No H/C H/C No H/C H/C No H/C H/C No H/C H/C

App. user rate 6.242 6.62 12.484 13.238 18.726 19.856 24.968 26.473

UDP 6.43 6.82 12.86 13.63 19.29 20.45 25.72 27.27

IP user rate 6.9 13.8 20.7 27.6

SNDCP 6.94 13.88 20.82 27.76

LLC 7.08 14.16 21.24 28.32

RLC/MAC 9.05 18.1 27.15 36.2

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 9.662 10.236 19.724 20.876 28.986 30.71 38.648 40.948

UDP 9.95 10.54 19.9 21.08 29.85 31.63 39.8 42.17

IP user rate 10.67 21.34 32.01 42.68

SNDCP 10.75 21.5 32.25 43.0

LLC 10.96 21.92 32.88 43.84

RLC/MAC 13.4 26.8 40.2 53.6

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 11.42 12.11 22.84 24.213 34.26 36.322 45.68 48.434

UDP 11.76 12.47 23.52 24.94 35.28 37.41 47.04 49.87

IP user rate 12.62 25.24 37.86 50.48

SNDCP 12.7 25.4 38.1 50.8

LLC 12.96 25.92 38.88 51.84

RLC/MAC 15.6 31.2 46.8 62.4

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 15.99 16.952 31.98 33.896 47.97 50.85 63.96 67.796

UDP 16.47 17.46 32.94 34.92 49.41 52.37 65.88 69.83

IP user rate 17.67 35.34 53.01 70.68

SNDCP 17.79 35.58 53.37 71.16

LLC 18.15 36.3 54.45 72.6

RLC/MAC 21.4 42.8 64.2 85.6

Physical layer 33.86 67.72 101.58 135.44


30 Sep 20033�126


GMR-0168P02900W21-M

Table 3-19 GPRS data rates (kbit/s) with TCP

ProtocolStack



App. user rate 5.96 6.32 11.92 12.64 17.88 18.96 23.84 25.28

TCP 6.43 6.82 12.86 13.63 19.29 20.45 25.72 27.27

IP user rate 6.9 13.8 20.7 27.6

SNDCP 6.94 13.88 20.82 27.76

LLC 7.08 14.16 21.24 28.32

RLC/MAC 9.05 18.1 27.15 36.2

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 9.23 9.78 18.46 19.56 27.69 29.34 36.92 39.12

TCP 9.95 10.54 19.9 21.08 29.85 31.63 39.8 42.17

IP user rate 10.67 21.34 32.01 42.68

SNDCP 10.75 21.5 32.25 43.0

LLC 10.96 21.92 32.88 43.84

RLC/MAC 13.4 26.8 40.2 53.6

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 10.91 11.57 21.82 23.13 32.73 34.70 43.64 46.27

TCP 11.76 12.47 23.52 24.94 35.28 37.41 47.04 49.87

IP user rate 12.62 25.24 37.86 50.48

SNDCP 12.7 25.4 38.1 50.8

LLC 12.96 25.92 38.88 51.84

RLC/MAC 15.6 31.2 46.8 62.4

Physical layer 33.86 67.72 101.58 135.44

ProtocolStack



App. user rate 15.27 16.19 30.54 32.37 45.81 48.56 61.08 64.74

TCP 16.47 17.46 32.94 34.92 49.41 52.37 65.88 69.83

IP user rate 17.67 35.34 53.01 70.68

SNDCP 17.79 35.58 53.37 71.16

LLC 18.15 36.3 54.45 72.6

RLC/MAC 21.4 42.8 64.2 85.6

Physical layer 33.86 67.72 101.58 135.44

30 Sep 2003


68P02900W21-M

GMR-014�1

Chapter 4

BTS planning steps and rules

GSR6 (Horizon II)

30 Sep 20034�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-014�3

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, andremote transcoder (RXCDR) are in Chapter 6 of this manual. This chapter contains:

S BTS planning overview:

� Outline of planning steps.

S Macrocell and microcell planning overview:

� 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 Horizon II macro site controller (HIISC).

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

S Picocell planning overview:

� Planning rules for PCC cabinets.

� Line interface modules (HIM-75, HIM-120).

GSR6 (Horizon II)BTS planning overview

30 Sep 20034�4


GMR-0168P02900W21-M

BTS planning overview

Introduction

To plan the equipage of a BTS site certain information must be known. The major itemsinclude:

S The number of cells controlled by the site.

S The number of carriers required.

S The number of standby carriers per cell.

S The output power per cell.

The required output power must be known to ensure that the selected combiningmethod and antenna configuration provides sufficient output power. Alternativesinclude changing combiner types or using more than one transmitting antenna.Duplexers may be used to reduce the amount of cabling and the number ofantennas.

S The antenna configuration for each cell.

S The cabinet/enclosure types to be used.

S Future growth potential.

It is useful to know about potential future growth of the site in order to makeintelligent trade offs between fewer cabinets/enclosures initially and ease ofexpansion later.

S Whether or not there are equipment shelters at the site.

Macro/micro/picocell outdoor equipments should be included in the BTS planningfor locations where there are no equipment shelters. Macro/micro/picocell shouldbe included where rooftop mounting or distributed RF coverage is required orwhere space and access are restricted.

To plan the equipage of a PCC cabinet (M-Cellaccess) certain information must beknown. The major items include:

S The traffic load to be handled.

S The number of PCU enclosures to be controlled.

S The physical interconnection of the PCU enclosures to the PCC cabinet.

S The use of optical or HDSL links.

S The use or otherwise of the GDP/XCDR option.

S The use of E1 or T1 links.

S The use of balanced or unbalanced E1.

GSR6 (Horizon II) BTS planning overview

30 Sep 2003


68P02900W21-M

GMR-014�5

Outline of planning steps

Macrocell and microcell BTS sites

The information required for planning a macro/microcell BTS site is outlined in thefollowing list and is provided in this chapter:

1. Determine if the site is indoor or outdoor.

2. Number of macrocell cabinets required, refer to the section Macrocell cabinets.

3. Number of microcell enclosures required, refer to the section Microcellenclosures.

4. The receiver configuration, refer to the section Receiver configurations.

5. The transmit configuration, refer to the section Transmit configurations.

6. The antenna configuration, refer to the section Antenna configurations.

7. The amount of carrier equipment required, refer to the section Carrier equipment.

8. The number of micro base control units required, refer to the section Micro basecontrol units.

9. The number of network interface units required, refer to the section Networkinterface unit and site interconnection.

10. The number of E1/T1 links required, refer to the section Network interface unitand site interconnection.

11. The number of main control units required, refer to the section Main control unit.

12. The number of FOX and FMUX boards required, refer to the section Cabinetinterconnection.

13. The external power supply requirements, refer to the section External powerrequirements.

Picocell site

The information required for planning a picocell (macro/micro/picocell) site is outlined inthis chapter.

GSR6 (Horizon II)Macrocell cabinets

30 Sep 20034�6


GMR-0168P02900W21-M

Macrocell cabinets

Horizon II macro

Horizon II macro is the next generation replacement for Horizonmacro. From a capacityperspective, Horizon II macro and Horizonmacro are identical and support the samenumbers of carriers, RSLs and E1s. The Horizon II macro supports equipping of 4 RSLsper E1, reducing the amount of E1 spans needed at a site that requires more than 2RSLs. Horizonmacro and M-Cell BTSs currently support 2 RSLs per E1.

A Horizon II macro cabinet (currently available as indoor only) can support 12 carrierswhen populated fully with 6 CTU2s, used in double density mode, or six carriers whenthe 6 CTU2s are used in single density mode. Expansion beyond the maximum 12carriers per cabinet requires additional cabinets, and maximum RF carriers supported perHorizon II macro site controller (HIISC) is 24.

NOTE The Horizon II macro does not support the use of CCBs.

Horizonmacro

A Horizonmacro cabinet (indoor or outdoor) can support six carriers (CTUs). Expansionbeyond six carriers requires additional cabinets. The Horizonmacro 12 carrier outdoor is,in effect, an outdoor enclosure which can accommodate either one or two indoor cabinetsfor six or 12 carrier operation.

NOTE CCBs cannot be used with the Horizonmacro indoor cabinet ifthe cabinet is to be installed in the 12 carrier outdoor enclosure.

All Horizonmacro cabinets/enclosures incorporate heat management systems. TheHorizonmacro outdoor can operate at ambient temperatures up to 50 _C. TheHorizonmacro 12 carrier outdoor can operate at ambient temperatures up to 45 _C.

Horizoncompact and Horizoncompact2

The Horizoncompact / Horizoncompact2 is an integrated cell site, designed primarily foroutdoor operation and consists of:

S The BTS unit. This is similar to Horizonmicro / Horizonmicro2 and is a two-carriercell with combining.

S The booster unit. This incorporates two Tx amplifiers, delivering 10 W (nominal) ateach antenna.

The BTS can be wall or pole-mounted. The wall may be concrete, brickwork, stonework,dense aggregate blockwork, or reconstituted stone, with or without rendering.

Cooling is by natural convection, and the unit can operate at ambient temperatures up to50 _C.

NOTE The main difference between the Horizoncompact and theHorizoncompact2 is that the latter can be expanded to supportan additional two BTSs (requires GSR5 or later software).For the purposes of this document, future references toHorizoncompact2 also include Horizoncompact unlessspecifically stated otherwise.

GSR6 (Horizon II) Macrocell cabinets

30 Sep 2003


68P02900W21-M

GMR-014�7

M-Cell6

The M�Cell6 cabinet can support six carriers (TCUs). Expansion beyond six carriersrequires additional cabinets. Outdoor cell sites are provided with an ancillary cabinetand a side cabinet.

The M-Cell6 HMS offers the following options:

S Fans that circulate ambient air through the cabinet, for both indoor and outdoorunits.

S A heat exchanger for ambient temperatures up to 45 _C, for outdoor cabinets only.

S An air conditioning unit for ambient temperatures up to 55 _C, for outdoor cabinetsonly.

M-Cell2

An M-Cell2 cabinet can support two carriers (TCUs). Expansion beyond two carriersrequires additional cabinets.

The M-Cell2 outdoor cabinet accommodates all the elements in an indoor cabinet, inaddition, limited accommodation for LTUs and battery backup is provided. Cooling isprovided 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 Fans that circulate ambient air through the cabinet, for both indoor and outdoorunits.

S A heat exchanger for ambient temperatures up to 45 _C, for outdoor cabinets only.

S An air conditioning unit for ambient temperatures up to 55 _C, for outdoor cabinetsonly.

GSR6 (Horizon II)Microcell enclosures

30 Sep 20034�8


GMR-0168P02900W21-M

Microcell enclosures

Horizonmicro and Horizonmicro2

The Horizonmicro / Horizonmicro2 is an integrated cell site, designed primarily foroutdoor operation and consists of a single small two carrier BTS unit.

The Horizonmicro / Horizonmicro2 can be wall or pole-mounted. The wall may beconcrete, brickwork, stonework, dense aggregate blockwork, or reconstituted stone, withor without rendering.

Cooling is by natural convection, and the unit can operate at ambient temperatures up to50 _C.

NOTE The main difference between the Horizonmicro and theHorizonmicro2 is that the latter can be expanded to support anadditional two BTSs (requires GSR5 software).For the purposes of this document, future references toHorizonmicro2 also include Horizonmicro unless specificallystated otherwise.

GSR6 (Horizon II) Receive configurations

30 Sep 2003


68P02900W21-M

GMR-014�9

Receive configurations

Introduction

The receiver equipment provides the termination and distribution of the received signalsfrom the Rx antennas. Receiver equipment is required for each Rx signal in every cabinetor enclosure in which it is used. Each Rx antenna must terminate on a single cabinet orenclosure. If the signal needs to go to multiple cabinets it will be distributed from the firstcabinet.

NOTE Horizonmicro2 is two carrier only, combined to a single antenna.Horizoncompact2 is two carrier only, with two antennas. Twoversions of the Horizonmicro2 and Horizoncompact2 BTSs areavailable. One version can operate on GSM900 frequencies andthe other can operate on DCS1800 frequencies.


The factors affecting planning for GSM900 and DCS1800 BTSs are provided in thissection.

GSM900

The following factors should be considered when planning the GSM900 receiveequipment:

S Horizon II macro BTSs require one 900 MHz SURF2 for each cabinet. Currently,the SURF2 is not dual band and only supports 900/1800 Mhz capability inseparate cabinets. A second (optional) 900 MHz SURF2 can be installed toprovide 4 branch diversity.

Receive antennas can be extended across Horizon II macro cabinets by using the900 SURF2 expansion ports to feed a SURF2 in another cabinet.

S Horizonmacro BTSs require one 900 MHz SURF for each cabinet. This has dualband (900/1800 Mhz) capability.

Receive antennas can be extended across Horizonmacro cabinets by using the900 SURF expansion ports to feed a SURF in another cabinet.

S M-Cell2 and M-Cell6 BTSs require one DLNB for each sector.

Receive antennas can be extended across M-Cell6 cabinets by using the IADUexpansion ports to feed an IADU in another cabinet.

GSR6 (Horizon II)Receive configurations

30 Sep 20034�10


GMR-0168P02900W21-M

DCS1800

The following factors should be considered when planning the DCS1800 receiveequipment:

S Horizon II macro BTSs require one 1800 MHz SURF2 for each cabinet. Currently,the SURF2 is not dual band and only supports 900/1800 Mhz capability inseparate cabinets. A second (optional) 1800 MHz SURF2 can be installed toprovide 4 branch diversity.

Receive antennas can be extended across Horizon II macro cabinets by using the1800 SURF2 expansion ports to feed a SURF2 in another cabinet.

S Horizonmacro BTSs require one 1800 MHz SURF for each cabinet.

Receive antennas can be extended across Horizonmacro cabinets by using the1800 SURF expansion ports to feed a SURF in another cabinet.

NOTE Two types of 1800 SURF are available. One is 1800 MHz singleband and the other is 1800/900 MHz dual band.

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 LNAexpansion ports to feed a LNA in another cabinet.

Receiver planning actions


1. Determine the number of cells.

2. Determine the number of cells which have CTU2s/CTUs/TCUs in more than onecabinet.

3. Determine the number of Rx antennas per cell supported in each cabinet.

4. Determine the type and quantity of receive equipment required.

NOTE When using CTU2s in double density mode, both carriers needto be in the same sector and can be individually reset. Droppingone carrier does not affect the second CTU2 carrier.

GSR6 (Horizon II) Transmit configurations

30 Sep 2003


68P02900W21-M

GMR-014�11

Transmit configurations

IntroductionThe transmit equipment provides bandpass filtering and signal combining for the BTScabinets. The CTU2 used in Horizon II macro can be configured to use a single highpower carrier (single density mode) or two lower power carriers (double density mode).For M-Cell2 and M-Cell6 cabinets, a TxBPF is required for each antenna.

NOTE Horizonmicro2 is two carrier only, combined to a single antenna.Horizoncompact2 is two carrier only, with two antennas.

Planning considerationsThe transmit configurations available for Horizon II macro, Horizonmacro, M-Cell2 andM-Cell6 BTSs are listed in Table 4-1.

Table 4-1 Transmit configurations

Numberof

CarriersBTS Type

Cabinet Transmit Configurations

Wide Band Combining

Cabinet Transmit Configurations

Cavity Combining

1 M-Cell2 and M-Cell6 1 TxBPF Not available

1 Horizonmacro 1 DCF or 1 TDF Not available

1 or 2 Horizon II macro 1 DUP Not available

2 M-Cell2 and M-Cell6 1 HCOMB + 1 TxBPF 1 CCB output

2 Horizonmacro 1 DCF 1 CCB output

3 M-Cell6 2 HCOMB + 1 TxBPF 1 CCB output

3 Horizonmacro 2 DCF or 1 DDF 1 CCB output

3 or 4 Horizon II macro 1 DUP + 1 HCU or2 DUP and Air CCBs not supported

4 M-Cell6 2 HCOMB + 1 TxBPF 1 CCB output +1 CCB extension

4 Horizonmacro 1 DDF + 1 HCU 1 CCB output +1 CCB extension

5 M-Cell6 3 HCOMB + 1 TxBPF 1 CCB output + 1 CCB extension

5 Horizonmacro 2 DDF and Air 1 CCB output +1 CCB extension

6 M-Cell6 4 HCOMB + 1 TxBPF 1 CCB output +1 CCB extension

6 Horizonmacro 2 DDF and Air 1 CCB output +1 CCB extension

6 Horizon II macro 1 DUP + 1 DHU or2 DUP + 1 HCU and Air CCBs not supported

NOTE A CCB output includes a TxBPF; a CCB extension does not.

Transmit planning actionsDetermine the transmit equipment required.

GSR6 (Horizon II)Antenna configurations

30 Sep 20034�12


GMR-0168P02900W21-M

Antenna configurations


The following factors should be considered when planning the antenna configuration:

S Omni, one sector, two sector, three sector (either 120_ or 60_), or six sector (twocabinets are needed).

S Share existing antenna(s) or new/separate antenna(s).

S Diversity considerations.

S Antenna type:

� Gain.

� Size.

� Bandwidth.

� Appearance.

� Mounting.

Antenna planning actions

Determine the antenna configuration.

GSR6 (Horizon II) Carrier equipment (transceiver unit)

30 Sep 2003


68P02900W21-M

GMR-014�13

Carrier equipment (transceiver unit)

Introduction

The transceiver unit for Horizon II macro is a CTU2. This can be configured to operate insingle density (single carrier) or double density (2 carrier) mode. The CTU2 can also beused as a CTU replacement (subject to restrictions) in a Horizonmacro indoor cabinet,but NOT an outdoor cabinet.

The transceiver unit for Horizonmacro is a CTU. This will eventually be phased out andreplaced by the CTU2, as used in the Horizon II macro.

The Motorola on-line ordering guide provides rules relating to replacement of a CTU witha CTU2.

The transceiver unit for Horizonmicro2 and Horizoncompact2 is a DTRX.

The transceiver unit for M-Cell2 and M-Cell6 is either a TCU or a TCU-B. The TCU-B is adevelopment of the original TCU and can be used as a direct replacement for the TCU,but note the following differences:

S The TCU-B only supports GSM/EGSM900.

S The TCU-B cannot be used as a SCU (in pre M-Cell equipment).

References to TCU in the text include TCU-B, except where stated otherwise.

Restrictions when using CTU2s in Horizonmacro BTSs

The following restrictions apply when CTU2s are used to replace CTUs in HorizonmacroBTSs:

S CTU2s cannot be used in Horizonmacro outdoor BTSs.

S CTU2s cannot be used in Horizonmacro indoor BTSs that are powered from 110 Vac.

S BBH is only supported in single density mode when CTU2s are used inHorizonmacro indoor BTSs.

S CCBs are not supported when CTU2s are used in Horizonmacro indoor BTSs.

S RF power output from the CTU2s is reduced.

S Fully populated Horizonmacro cabinets that contain two or more CTU2s requirethree PSUs. PSU redundancy will not be available in these configurations.

GSR6 (Horizon II)Carrier equipment (transceiver unit)

30 Sep 20034�14


GMR-0168P02900W21-M

CTU/CTU2 power supply considerations

Under normal circumstances, the Horizonmacro only requires two power supply modules(PSMs) to power six CTUs and the third PSM slot can be used either for a redundantPSM or for an optional hold-up battery module (in ac-powered systems).

These power supply requirements change if CTU2s are used in the Horizonmacrocabinet. Depending on the number of CTU2s used, it may be necessary to install a thirdPSM, thus losing the internal battery backup facility. In such cases where battery backupis required, an external battery backup unit (BBS) will need to be added instead. Also, incases where a third (redundant) PSM is already installed, redundancy will be lost.

Table 4-2 lists the CTU/CTU2 combinations and power supply requirements inHorizonmacro and Horizon II macro cabinets.

Table 4-2 CTU/CTU2 power requirements in Horizonmacro and Horizon II macro cabinets

Horizonmacro Horizon II macro

No. ofCTUs

No. ofCTU2s

No. of powersupplies required

No. ofCTU2s

No. of powersupplies required

6 0 2 6 3

5 1 3 5 3

4 1 2 4 3

3 1 2 3 2

2 1 2 2 2

1 1 1 1 1

0 1 1

4 2 3

3 2 2

2 2 2

1 2 2

0 2 2

3 3 3

2 3 3

1 3 2

0 3 2

2 4 3

1 4 3

0 4 2

1 5 3

0 5 3

0 6 3

NOTE The Horizon II macro always has a spare fourth power supplyslot available for either a redundant power supply or for a hold-upbattery module (in ac-powered cabinets).

GSR6 (Horizon II) Carrier equipment (transceiver unit)

30 Sep 2003


68P02900W21-M

GMR-014�15


The following factors should be considered when planning carrier equipment:

S The number of carriers should be based on traffic considerations.

S Plan for future growth.

S Allowance must be made for BCCH and SDCCH control channels.

Information about how to determine the number of control channels required is inthe Control channel calculations section in Chapter 3, BSS cell planning in thismanual.

S One transceiver unit is required to provide each RF carrier. However, with theintroduction of the CTU2 this is no longer true. The CTU2 is capable of single anddouble density operation; one CTU2 can support one RF carrier or be configuredto support two RF carriers.

S Include redundancy requirements. Redundancy can be achieved by installingexcess capacity in the form of additional transceiver units.

S Plan the number of power supplies required in accordance with the number oftransceivers required.

Transceiver planning actions

Determine the number of transceivers required.

Determine the number of power supplies required to power the transceivers.

GSR6 (Horizon II)Micro base control unit (microBCU)

30 Sep 20034�16


GMR-0168P02900W21-M

Micro base control unit (microBCU)

Introduction

The microBCU (or mBCU) is the macro/microcell implementation of a BTS site controller.


The following factors should be considered when planning the mBCU complement:

S Horizon II macro

The Horizon II macro is similar to the Horizonmacro in that it has a built-in digitalmodule shelf. However, unlike Horizonmacro, the NIU is integrated on the HIISC(the equivalent of the Horizonmacro MCUF) and external FMUXs and BPSMs arenot required.

The digital module shelf can be equipped for redundancy and/or additional E1/T1link capacity with the addition of a redundant HIISC.

S Horizonmacro

Each Horizonmacro cabinet has a built-in digital module shelf. This provides theHorizonmacro equivalent of M-Cell6 mBCU cage functionality.

The digital module shelf can be equipped for redundancy and/or additional E1/T1link capacity with the addition of a redundant MCUF, NIU, FMUX and BPSM.

S M-Cell6

Each M-Cell6 cabinet requires one mBCU cage.

Two mBCU cages can be equipped for redundancy and/or additional E1/T1 linkcapacity with the addition of a redundant MCU, NIU and FOX/FMUX.

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

Additional cabinets do not require mBCU2 cages.

MicroBCU planning actions

For M-Cell equipment, determine the number of mBCUs required.

GSR6 (Horizon II) Network interface unit (NIU) and site connection

30 Sep 2003


68P02900W21-M

GMR-014�17

Network interface unit (NIU) and site connection

Introduction

The NIU provides the interface for the Horizon II macro, Horizonmacro or M-Cell2/6 BTSto the terrestrial network.

NOTE M-Cellcity and M-Cellcity+ are fitted with a single NIU-m only.The equivalent modules in Horizoncompact2 and Horizonmicro2are RHINO/DINO.


Depending on the BTS equipment installed, the following factors should be consideredwhen planning the NIU complement:

Horizon II macro

S NIU functionality is integrated into the HIISC. From a functional standpoint, theIntegrated NIU functions the same as the standalone NIU with the exception thatsupport for 4 RSL links per E1 and a maximum of 6 E1s is now supported inHorizon II macro.

S A minimum of one HIISC (with integrated NIU functionality) is required in themaster cabinet for each Horizon II macro BTS site.

S In a master cabinet, redundancy for the NIU functionality depends on a redundantHIISC. If a redundant HIISC is installed, a redundant site expansion board is alsorequired. Slave Horizon II macro cabinets connected to the master cabinet alsorequire redundant site expansion boards and redundant XMUXs.

NOTE The integrated NIU within the redundant HIISC has connectivityto all the E1 links for that site through the use of relays andswitches. The redundant HIISC can be switched automatically tobecome the main HIISC, taking over all duties of the main HIISC(including controlling all E1 links at that site) through a BTSreset.

GSR6 (Horizon II)Network interface unit (NIU) and site connection

30 Sep 20034�18


GMR-0168P02900W21-M

Horizonmacro and M-Cell

S The first NIU in a digital module shelf (Horizonmacro) or mBCU cage (M-Cell6) caninterface two E1/T1 links.

S The second NIU in a digital module shelf or mBCU cage can interface one E1/T1link.

S Each E1/T1 link provides 31 (E1) or 24 (T1) usable 64 kbit/s links.

S A minimum of one NIU is required for each BTS site.

S One NIU can support two MCUFs (Horizonmacro) or two MCUs (M-Cell6).

S The NIU feeds the active MCUF/MCU.

S To calculate the number of 64 kbit/s links required, view the site as consisting of itsown equipment, and that of other sites which are connected to it by the drop andinsert (daisy chain) method.

� Two 64 kbit/s links are required for each active transceiver.

� A 64 kbit/s link is required for every RSL (LAPD signalling channel) to thesite. In the drop and insert (daisy chain) configuration, every site will requireits own 64 kbit/s link for signalling.

S Redundancy for the NIU module depends on the number of redundant E1/T1 linksrunning to the site.

S Plan for a maximum of two NIUs per digital module shelf or mBCU cage (three E1or T1 links).

S Plan for a maximum of one NIU per mBCU2 cage for M-Cell2 cabinets (two E1 orT1 links).

The minimum number of NIUs and mBCU cages required for a given number of E1/T1links to a single M-Cell cabinet is shown in Table 4-3.

Table 4-3 Site connection requirements for M-Cell2 and M-Cell6

Number ofE1/T1 links

Minimumnumber of NIU

required

Number ofmBCU cages

required

Notes

1 1 1 M-Cell2 and M-Cell6


3 2 1 M-Cell6



5 3 2 M-Cell6 only

6 4 2 M-Cell6 only

NOTE Only one digital module shelf is installed in the Horizon II macroand Horizonmacro.

GSR6 (Horizon II) Network interface unit (NIU) and site connection

30 Sep 2003


68P02900W21-M

GMR-014�19

E1 link interfaces

For driving a balanced 120 ohm 3 V (peak pulse) line use a BIB.

For driving a single ended 75 ohm 2.37 V (peak pulse) line use a T43.

T1 link interfaces

For driving a balanced 110 ohm 3 V (peak pulse) line use a BIB.

NIU planning actions

Determine the number of NIUs required.

GSR6 (Horizon II)BTS main control unit

30 Sep 20034�20


GMR-0168P02900W21-M

BTS main control unit

Introduction

The main control unit provides the main site control functions for a BTS. The main controlunit used depends on the BTS equipment:

S Horizon II macro uses a Horizon II macro site controller (HIISC).

S Horizonmacro uses a main control unit with dual FMUX (MCUF).

S M-Cell6 and M-Cell2 use a main control unit (MCU).

NOTE The HIISC can only be used in Horizon II macro. The MCUF isbackwards compatible with the MCU and can be used in M-Cell6and M-Cell2 BTSs.


Horizon II macro

The following factors should be considered when planning the HIISC complement for aHorizon II macro site:

S Only the master Horizon II macro cabinet requires a HIISC.

S For redundancy, add a second HIISC in the digital module shelf of the mastercabinet. This also provides redundancy for the NIU and XMUX as well, since theyare integrated in the HIISC.

NOTE This redundancy configuration also requires a redundant siteexpansion board in all Horizon II macro cabinets at sites wheremore than one cabinet is installed.

Horizonmacro

The following factors should be considered when planning the MCUF complement for aHorizonmacro site:

S Only the master cabinet requires a MCUF.

S An optional 20 Mbyte PCMCIA memory card may be installed for non-volatile codestorage.

S For redundancy, add a second MCUF in the digital module shelf of the mastercabinet.

M-Cell6 and M-Cell2

The following factors should be considered when planning the MCU complement for aM-Cell6 or M-Cell2 site:

S Only the master cabinet requires a MCU.

S An optional 20 Mbyte PCMCIA memory card may be installed for non-volatile codestorage.

S For redundancy, add a second mBCU cage and MCU in the master cabinet.

GSR6 (Horizon II) BTS main control unit

30 Sep 2003


68P02900W21-M

GMR-014�21

Planning considerations � Horizon II macro as expansion cabinet

This information describes the factors that need to be taken into account ifHorizon II macro cabinets are used to expand existing Horizonmacro or M-Cell6 sites.

NOTE Horizon II macro expansion from Horizonmacro or M-Cell6 BTSsrequires GSR6 (Horizon II) or later.

Horizon II macro slave BTS planning considerations

S A XMUX is required instead of a HIISC in the slave cabinet.

S A site expansion board is required.

S If redundancy is required, a redundant XMUX and redundant site expansion boardmust be installed.

Horizonmacro master BTS planning considerations

S Only the master cabinet requires an MCUF.

S A 20 Mbyte PCMCIA memory card running CSFP must be installed in the MCUFto accommodate the use of the CTU2 transceiver from a code storage standpoint.If the site is equipped with a redundant MCUF, the PCMCIA is also mandatory forthe redundant MCUF.

M-Cell6 master BTS planning considerations

NOTE Due to expansion limitations, M-Cell2 BTSs cannot be used withHorizon II macro (or Horizonmacro) cabinets.

S Only the master cabinet requires an MCU.

S A 20 Mbyte PCMCIA memory card running CSFP must be installed in the MCU toaccommodate the use of the CTU2 transceiver from a code storage standpoint. Ifthe site is equipped with a redundant MCU, the PCMCIA is also mandatory for theredundant MCU.

S The master cabinet must have a FMUX installed to communicate with theHorizon II macro BTS.

Planning actions

Horizon II macro

Determine the number of HIISCs required.

Horizonmacro

Determine the number and configuration of MCUFs required.

M-Cell6 and M-Cell2

Determine the number and configuration of MCUs required.

GSR6 (Horizon II)Cabinet interconnection

30 Sep 20034�22


GMR-0168P02900W21-M

Cabinet interconnection

Introduction

Horizon II macro

The XMUX multiplexes and demultiplexes full duplex transceiver links between a siteexpansion board and up to six CTU2s in a Horizon II macro expansion cabinet.

Horizonmacro

The FMUX multiplexes and demultiplexes full duplex transceiver links between a MCUFand up to six CTUs.

M-Cell6 and M-Cell2

The FOX provides the bidirectional electrical to optical interface between an MCU orFMUX and up to six TCUs.

The FMUX multiplexes and demultiplexes electrical connections for up to six TCUs ontoa single fibre optic connection operating at the rate of 16.384 Mbit/s.


Horizon II macro

The following factors should be considered when planning the XMUX complement:

S A XMUX is required in each Horizon II macro expansion cabinet.

S The master Horizon II macro cabinet does not require a XMUX as a triple XMUX isintegrated on the HIISC.

S A site expansion board (unique to Horizon II macro) is required for the master andevery expansion cabinet in the Horizon II macro BTS site when expansion isrequired (see Table 4-4).

S Redundancy requires duplication of the HIISC in the master cabinet and allXMUXs and site expansion boards.

Table 4-4 Horizon II macro XMUX expansion requirements

Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) None

2 1 site expansionboard only

1 XMUX +1 site

expansionboard


1 XMUX +1 site

expansionboard

1 XMUX +1 site

expansionboard


1 XMUX +1 site

expansionboard

1 XMUX +1 site

expansionboard

1 XMUX +1 site

expansionboard

GSR6 (Horizon II) Cabinet interconnection

30 Sep 2003


68P02900W21-M

GMR-014�23

Horizonmacro

The following factors should be considered when planning the FMUX complement:

S An FMUX is not required in the master cabinet for two or three cabinetconfigurations (see Table 4-5).

S A fourth Horizonmacro cabinet requires one FMUX plus one FMUX in the mastercabinet (see Table 4-5).

S Redundancy requires duplication of an FMUX and associated MCUF.

Table 4-5 Horizonmacro FMUX expansion requirements

Cabinet Master Extender 1 Extender 2 Extender 3

1 (master) None

2 None 1

3 None 1 1

4 1 1 1 1

M-Cell6 and M-Cell2

The following factors should be considered when planning the FOX/FMUX complement:

S A FOX board is required for more than two TCUs.

S Each additional M-Cell6 cabinet requires a minimum of one FOX and FMUX plusone FMUX in the first cabinet.

S Redundancy requires duplication of all FOX and FMUX boards and associatedMCU and mBCU cages.

Planning considerations � Horizon II macro as master cabinet

NOTE Due to expansion limitations, M-Cell2 BTSs cannot be used withHorizon II macro cabinets.

The following factors should be considered when planning to use a Horizon II macro as amaster cabinet with Horizonmacro or M-Cell6 expansion cabinets:

S GSR6 (Horizon II) is required in the network.

S A site expansion board is required in the Horizon II macro master cabinet.

S A XMUX is not required in the Horizon II macro master cabinet.

S Each Horizonmacro or M-Cell6 slave cabinet must contain a FMUX (replaces theMCUF/MCU).

S For redundancy, the master Horizon II macro cabinet requires an additional HIISCand site expansion board; each Horizonmacro slave cabinet requires an additionalFMUX, and each M-Cell6 slave cabinet requires an additional FMUX and FOX.

GSR6 (Horizon II)Cabinet interconnection

30 Sep 20034�24


GMR-0168P02900W21-M

XMUX/FMUX/FOX planning actions

Horizon II macro

Determine the number of XMUXs required (applies to expansion cabinets only).

Horizonmacro

Determine the number of FMUXs required.

M-Cell6 and M-Cell2

Determine the number of FOX/FMUXs required.

NOTE M-Cell2 BTSs are not supported as an expansion toHorizon II macro or Horizonmacro cabinets.

Site expansion board planning actions (Horizon II macro only)

If more than one cabinet is to be used at a site, determine the number of site expansionboards required.

GSR6 (Horizon II) External power requirements

30 Sep 2003


68P02900W21-M

GMR-014�25

External power requirements

Introduction

Macrocell cabinets and Microcell enclosures can operate from a variety of powersupplies.


The following factors should be considered when planning the power supplyrequirements:

S Horizon II macro

Horizon II macro power requirements are determined by the BTS cabinet type:

Indoor: +27 V dc, �48 V dc, 230 V ac

NOTE An outdoor version of the Horizon II macro is not currentlyavailable.

S Horizonmacro

Horizonmacro power requirements are determined by the BTS cabinet type:

Indoor: +27 V dc, �48 V dc, 230 V ac.Outdoor: 110 V ac single phase, 230 V ac single/3-phase.12 carrier outdoor: 230 V ac single/3-phase.

NOTE Only �48 V dc indoor cabinets can be installed in the 12 carrieroutdoor.

S Horizonmicro2 and Horizoncompact2

The Horizonmicro2 and Horizoncompact2 enclosures operate from a 88 to 265 Vac power source.

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 or230 V/110 V ac power source.

S M-Cellcity and M-Cellcity+

The M-Cellcity and M-Cellcity+ BTS enclosures operate from a 88 to 265 V acpower source.

Power planning actions

Determine the power supply required.

GSR6 (Horizon II)Network expansion using macro/micro/picocell BTSs

30 Sep 20034�26


GMR-0168P02900W21-M

Network expansion using macro/micro/picocell BTSs

Introduction

An existing network with previous generations of Motorola equipment such as BTS4,BTS5, BTS6, TopCell, or ExCell may be expanded using macro/micro/picocell. TheNetwork topology can be any of those specified in Chapter 2 of this manual. Amacro/micro/picocell BTS may occupy any position in a network.

Expansion considerations

The following factors should be considered when expanding an existing network usingmacro/micro/picocell BTS cabinets:

S A macro/micro/picocell BTS cannot share a cell with a BTS4, BTS5, BTS6,TopCell, or ExCell.

S The rules governing the number of NIUs required at the macro/micro/picocell BTSare given in Table 4-3 of this chapter.

S The rules governing the number of MSIs required at the BSC are given in theMultiple serial interface (MSI, MSI-2) section of Chapter 6.

Mixed site utilization

To upgrade sites utilizing previous generations of Motorola equipment such as BTS5,BTS4, BTS6, TopCell, or ExCell, proceed in the following manner:

1. Sites with previous generation equipment should be expanded with the appropriatemodules until the cabinets are full.

2. To further expand a previous generation site, the equipment in the previousgeneration cabinet must be re-configured so that it serves a complete set ofsectors in the target configuration.

3. A macro site should then be added to the site to serve the remaining sectors.

4. The macro site should then be connected into the network by daisy chaining it tothe existing site.

5. Customers who have not purchased the daisy chaining feature should order thefree of charge feature M-Cell � InCell Interworking, SWVN2460, to obtain asuitable licence for upgrading.

Example

To upgrade a BTS6 2/2/2 to a 3/3/3, reconfigure the BTS6 to a 3/3, order an M-Cell omni3 and install it to serve the third sector.

GSR6 (Horizon II) PCC cabinet

30 Sep 2003


68P02900W21-M

GMR-014�27

PCC cabinet

Introduction

Each PCC cabinet (M-Cellaccess) can support up to two sites (one cage = one site); andup 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 beused for each frequency.

XCDR/GDP options can be planned for the lower BSU shelf only, refer to Chapter 5, BSCplanning steps and rules and Chapter 6, RXCDR planning steps and rules.

Cabinet planning actions


S Determine the number of sites required.

S Determine the mix of frequencies.

S Determine the method of PCU/PCC interconnection.

GSR6 (Horizon II)Line interface modules (HIM-75, HIM-120)

30 Sep 20034�28


GMR-0168P02900W21-M

Line interface modules (HIM-75, HIM-120)

Introduction

The line interface modules, HDSL interface module, 75 ohm (HIM-75), and HDSLinterface module, 120 ohm (HIM-120), provide impedance matching for E1, T1 andHDSL links.


The following factors should be considered when planning the line interface complement:

S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T11.544 Mbit/s) 3 V (peak pulse) line use a HIM-120.

S To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peakpulse) line use a HIM-75.

S Each HIM-75/HIM-120 can interface four E1/T1 links to specific slots on one shelf.

S 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 12HDSL links.

HIM-75/HIM-120 planning actions


S Determine the number to be deployed.

S Determine the number of HIM-75s or HIM-120s required.

Minimum number of HIM�75s or HIM�120s = Number of PCUs

2

GSR6 (Horizon II) DRI/Combiner operability components

30 Sep 2003


68P02900W21-M

GMR-014�29

DRI/Combiner operability components

Overview

This enhancement improves the operability of the Digital Radio Interface (DRI) andcombiner devices by increasing the flexibility with which these devices can be equipped,unequipped, and re-equipped.

This feature is achieved by specifying the DRI role in system combining when equippingthe DRI.

DRI and combiner relationship

Figure 4-1 illustrates the pre-GSR5 and GSR5 onwards DRI and combiner relationship.

Figure 4-1 DRI and combiner relationship

PRE-GSR5 CONFIGURATION

COMB 0 0 COMB 0 1

DRI 0 0 DRI 0 1

Primary Combiner proc Secondary Combiner proc

Controlling DRI Standby DRI

COMB 0

GSR5 ONWARDS CONFIGURATION

DRI 0 0 DRI 0 1

First controllingDRI

Second controllingDRI

GSR6 (Horizon II)DRI/Combiner operability components

30 Sep 20034�30


GMR-0168P02900W21-M

30 Sep 2003


68P02900W21-M

GMR-015�1

Chapter 5

BSC planning steps and rules

GSR6 (Horizon II)

30 Sep 20035�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-015�3

Chapter overview

Introduction

This chapter provides the planning steps and rules for the BSC. The planning steps andrules for the BTS are in Chapter 4 of this manual. This chapter contains:

S BSC planning overview.

S Capacity calculations for standard and non-standard traffic models, including:

� Determining the required BSS signalling link capacities.

� Determining the number of RSLs required.

� Determining the number of MTLs required.

� Determining the number of XBLs required.

� Determining the number of GSLs required.

� BSC GPROC functions and types.

� Transcoding at the BSC.

S Planning rules for BSC hardware.

GSR6 (Horizon II)BSC planning overview

30 Sep 20035�4


GMR-0168P02900W21-M

BSC planning overview

Introduction

To plan the equipage of a BSC certain information must be known. The major itemsinclude:

S The number of BTS sites to be controlled.

S The number of RF carriers (RTF) at each BTS site.

S The number of TCHs and PDCHs at each site.

S The total number of TCHs and PDCHs under the BSC.

S The number of cells controlled from each BTS site should not exceed themaximum per BSC detailed in Table 5-1.

S The physical interconnection of the BTS sites to the BSC.

S The location of the XCDR function.

S The path for the OML links to the OMC-R.



S The traffic load to be handled (also take future growth into consideration).

S The number of MSC to BSC trunks.

GSR6 (Horizon II) BSC planning overview

30 Sep 2003


68P02900W21-M

GMR-015�5


Planning a BSC involves the following steps, which are all described in detail in thischapter:

1. Plan the number of RSL links between the BSC and BTS site(s) Refer to thesection Determine the RSLs required.

2. Plan the number of E1 or T1 links between the BSC and BTS site(s). Refer to thesection BSC to BTS E1 interconnect planning actions or BSC to BTS T1interconnect planning actions in this chapter.

3. Plan the number of MTL links between the BSC and MSC. Refer to the sectionDetermine the number of MTLs required.

4. Plan the number of XBL links required between the BSC and AXCDR. Refer to thesection Determining the number of XBLs required.

5. Plan the number of GSL links required between the BSC and the PCU. Refer toDetermining the number of GSLs required.

6. Plan the number of GPROC2s required. Refer to the section Generic processor(GPROC2).

7. Plan the number of XCDR/GDPs required. Refer to the section Transcoding.

8. Plan the number of MSI/MSI-2s required. Refer to the section Multiple serialinterface (MSI, MSI-2.

9. Plan the number of KSWs and timeslots required. Refer to the section Kiloportswitch (KSW).

10. Plan the number of BSU shelves. Refer to the section BSU shelves.

11. Plan the number of KSWXs required. Refer to the section Kiloport switchextender (KSWX).

12. Plan the number of GCLKs required. Refer to the section Generic clock (GCLK).

13. Plan the number of CLKXs required. Refer to the section Clock extender (CLKX).

14. Plan the number of LANXs required. Refer to the section LAN extender (LANX).

15. Plan the number of PIXs required. Refer to the section Parallel interfaceextender (PIX.

16. Plan the number of BIB or T43s required. Refer to the section Line interfaces(BIB, T43).

17. Plan the power requirements. Refer to the section Digital shelf power supply.

18. Plan the number of BBBXs required. Refer to the section Battery backup board(BBBX).

19. Decide whether an NVM board is required. Refer to the section Non volatilememory (NVM) board.

20. Verify the planning process. Refer to the section Verify the number of BSUshelves and BSSC cabinets.

GSR6 (Horizon II)Capacity calculations

30 Sep 20035�6


GMR-0168P02900W21-M

Capacity calculations

Introduction

The throughput capacities of the BSC processing elements (for example, GPROC,GPROC2) and the throughput capacities of its data links, determine the number ofsupported traffic channels (TCHs). These capacities are limited by the ability of theprocessors, and links to handle the signalling information associated with these TCHs.

This section provides information on how to calculate processor requirements, signallinglink capacities and BSC processing capacities. This section describes:

S A summary of BSC maximum capacities.

S The required BSS signalling link capacities.

S Traffic models.

S BSC GPROC functions and types.

S The number of GPROCs required.

Remote transcoding

When the transcoding function resides outside of the BSC cabinet, in the RXCDR, it ispossible to have multiple RXCDRs connected to a single BSC, and vice-versa. This isespecially useful for two reasons:

1. In certain configurations the RXCDR call (CIC) capacity may be greater than thatof a BSC.

2. A failure of a RXCDR or communication line will not result in a complete failure ofthe BSC to handle calls.

Each BSC may connect to up to nine RXCDRs, and vice-versa. The level of connectivitymay be constrained by the number of XBLs that can be supported, there is a limit of 18at each BSC and RXCDR (see Determining the number of XBLs required later in thischapter).

The level of connectivity is determined by the operator, Excess RXCDR capacity shouldnot be wasted, nor should larger BSCs be connected only to one RXCDR. One guidelineis to have each BSC connect to four RXCDRs. System size, capacity, and cost are majorinfluences on the chosen configuration.

GSR6 (Horizon II) BSC system capacity

30 Sep 2003


68P02900W21-M

GMR-015�7

BSC system capacity

System capacity summary

Table 5-1 provides a summary of BSC maximum capacities.

Table 5-1 BSC maximum capacities

Capacity

Item GSR2 GSR3 GSR4 GSR4.1 GSR5 GSR5.1 GSR6

BTS sites 40 40 100 100 100 100 100

BTSs (cells) 90 126 250 250 250 250 250

Active RF carriers 120 255 384 384 384 384 384 *

DRIs 210 381 634 634 634 634 634

RSLs 80 80 250 250 250 250 250

GSLs � � � 12 12 12 12

MMSs 72 102 128 128 128 128 128

PATHs 80 80 250 250 250 250 250

DHPs 161 296 232 232 232 232 232

LCFs 17 17 17 17 25 25 25

Trunks (see notebelow)

960 1680 1920 1920 2400 2400 2400 *

C7 links 16 16 16 16 16 16 16

T1 or E1 links 72 96 102 102 102 102 102

Maximum busyhour call attempts

38,000 50,400 57,600 57,600 72,000 72,000 90,000

* Can be increased to 512 carriers and 3200 trunks if the optional enhanced BSC capacity feature is enabled.

Notes

The capacities represent the BSS capacities for GSM circuit-switched traffic. If theGPRS traffic is carried on the BSS, the GSM circuit-switched traffic handling capacityreduces in direct proportion to the timeslots configured for GPRS traffic.

The maximum Busy Hour Call Attempts (BHCA) is computed for the standard callmodel. The actual value depends on the average call duration on a network.

Planning is a multi-variate problem. When planning a BSC, any limit given in Table 5-1should not be exceeded for the GSR version used. The first element to reach its limitsets the capacity of the BSC. For example, when dimensioning a BSC with a specificnon-standard call model, there is possibility that the LCF or C7 limit will be reachedbefore the Erlang limit is reached.

GSR6 (Horizon II)BSC system capacity

30 Sep 20035�8


GMR-0168P02900W21-M

Scaleable BSC

With the launch of the scaleable BSC, Motorola moved to a position where the diverserequirements of network operators in terms of BSC size are addressed by a singleplatform that can be efficiently configured in small, medium or large models.

From GSR4 onwards, for existing customers the move to a scaleable BSC is enabledthrough the migration of the processing boards within the BSC to use the GPROC2throughout. BSSs targeted at small, medium, or large networks are efficiently addressedby the scaleable BSC where minimal incremental hardware is required to be added asthe networks grow.

Being able to expand capacity within a BSC is appealing from an operational viewpointbecause there is less time and effort involved than compared with having to move sitesfrom one BSC to another, or even from one OMC-R to another.

Put into context, the BSC capacity prior to GSR3 supports in the order of 40 sites ofthree sectors and one carrier per sector; or alternatively, 20 sites of three sectors andtwo carriers per sector. At GSR3, the capacity increased to allow the operator to move tosupport in the order of 40 sites of three sectors and two carriers per sector. At GSR4, thecapacity increased to allow the operator to move to support in the order of 64 sites ofthree sectors and two carriers per sector.

The scaleable BSC also offers a substantial advantage for microcellular deploymentwhere a single BSC is able to support up to 100 microcellular BTSs, each equipped withtwo carriers per site.

The scaleable BSC capacity is enabled because of the increased processingperformance and memory of the GPROC2. The maximum capacity is increased asshown in Table 5-1.

This increased capacity is achieved through the deployment of GPROC2s for eachfunction at the BSC, including base station processor (BSP) and link control function(LCF).

Enhanced BSC capacity option

This feature is introduced at GSR6 as a restrictable option. If the feature is restricted, theBSC supports the normal BSC maximum capacity of 384 RF carriers and 2400 trunks(see Table 5-1). If the feature is unrestricted, the BSC maximum capacity is increased to512 carriers and 3200 trunks.

Specific hardware upgrades are required by the BSS to support implementation if thisoptional new feature is to be used:

S GPROCs at the RXCDR must be replaced with GPROC2s.

S BTP processors at InCell BTSs must be replaced with GPROC2s.

NOTE Replacing BTPs with GPROC2s at InCell BTSs is mandatory forGSR6 (even if the enhanced BSC capacity feature is restricted).

GSR6 (Horizon II) Determining the required BSS signalling link capacities

30 Sep 2003


68P02900W21-M

GMR-015�9

Determining the required BSS signalling link capacities

BSC signalling traffic model

For a GSM system the throughput of network entities, including sub-components,depends upon the assumed traffic model used in the network design or operation. Trafficmodels are fundamental to a number of planning actions.

The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends onits ability to process information transported through signalling links connecting it to theother network elements. These elements include MSC, BTSs, and the OMC-R.Depending on its device type and BSC configuration, a GPROC may be controllingsignalling links to one or more other network elements. A capacity figure can be statedfor each GPROC device type in terms of a static capacity such as the number of physicalsignalling links supported, and a dynamic capacity such as processing throughput.

In general telephony environments, processing and link throughput capacities can bestated in terms of the offered call load. To apply this for the GSM BSC, all signallinginformation to be processed by the BSC, is related to the offered call load (the amount oftraffic offered/generated by subscribers). When calls are blocked due to all trunks or allTCHs busy, most of the signalling associated with call setup and clearing still takes place,even though few or no trunk resources are utilized. Therefore, the offered call load (whichincludes the blocked calls) should be used in planning the signalling resources (forexample; MTLs and RSLs).

In the case where the BSC has more than enough trunks to handle the offered traffic,adequate signalling resources should be planned to handle the potential carried traffic.The trunk count can be used as an approximate Erlang value for the potential carriedload.

As a result, the signalling links and processing requirements should be able tohandle the greater of the following:

S The offered load.

S The potential carried load.

To determine the link and processing requirements of the BSC, the number of trunks orthe offered call load in Erlangs (whichever is greater) should be used.

BSC capacity planning requires a model that associates the signalling generated from allthe pertinent GSM procedures: call setup and clearing, handover, location updating, andpaging, 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 thenumber of call attempts processed. The rate at which call attempts are processed is afunction of the offered call load and the average call hold time.

NOTE A standard traffic model can be assumed when initially planninga network. However, once the network is running, it isabsolutely critical to continuously monitor and measure the realcall parameters (described in Chapter 11) from the live networkto ascertain the true network call model.Future planning should then be based on this actual (nonstandard) call model instead of the standard call model. Paststudies have shown that the actual call model in some networksdiffers considerably from the standard call model, and this has adirect impact on dimensioning requirements.

Figure 5-1 graphically depicts various factors that should be taken into account whenplanning a BSS.

GSR6 (Horizon II)Determining the required BSS signalling link capacities

30 Sep 20035�10


GMR-0168P02900W21-M

Figure 5-1 BSS planning diagram

MSC

A INTERFACE (TERRESTRIAL LINKS)�C7 SIGNALLING LINKS�X.25 CONTROL LINK *�REQUIRED TRUNKS

WITH SUBMULTIPLEXING TRANSCODING AT MSC1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK *1 x 64 KBIT/S CIRCUIT/ XBL1 x 64 KBIT/S CIRCUIT/4 TRUNKS

WITHOUT SUBMULTIPLEXING TRANSCODING AT BSC1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK*1 x 64 KBIT/S CIRCUIT/TRUNK

1 x 64 KBIT/S OF 1 x 16 KBIT/S RTF CIRCUIT/LAPDSIGNALLING LINK2 x 64 KBIT/S CIRCUITS/RTF1 x 16 KBIT/S GSL CIRCUITS/TIMESLOT

MOTOROLA BSC/BTS INTERFACENON-BLOCKING

AIR INTERFACE�TCHs, PDCHs AND SIGNALLING TSs�TYPICALLY 2% BLOCKING FOR CS TRAFFIC

TRANSCODING MUST BE LOCATED AT THEBSC, OR BETWEEN THE BSC AND MSC

TCH = TRAFFIC CHANNELTS = TIMESLOT* X.25 MAY BE PASSED TO RXCDR

OR MSC SITE** GDS�TRAU AND GSL ARE

CARRIED ON SEPARATE LINKS

THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINEDFROM THE # OF TRUNKS REQUIRED TO CARRY THESUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS,TYPICALLY USING 1% BLOCKING) FROM ALL BTSs

� PLUS �THE # OF GDS TRAU LINKS (DETERMINED FROM THENUMBER OF GPRS TIMESLOTS UNDER A BSC)

� PLUS �THE # OF C7 SIGNALLING LINKS

� PLUS � (IF APPLICABLE*)THE # OF X.25 LINKS (USUALLY ONE PER BSC)

� PLUS �THE # OF XBL LINKS

� PLUS �THE # OF GSL LINKS

THE # OF TCHs REQUIRED (USING TYPICALLY 2%BLOCKING) TO CARRY SUBSCRIBER TRAFFIC.THE TCHs PLUS THE REQUIRED SIGNALLING TSsDIVIDED BY EIGHT DETERMINES THE CARRIERSREQUIRED (ON A BTS/SECTOR BASIS)

TRANSCODER

BSC

BTS

AIR INTERFACE(TRAFFIC IN ERLANGS)

USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECTHARDWARE FOR THE �A� AND �BSC TO BTS� INTERFACE.

BSC TO PCUGDS�TRAUCIRCUITS

THE # OF GSLsTHE # OF GBLs

PCUGBL

GDS INTERFACE **� GDS TRAU CHANNELS� GSL LINKS

1 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTFOR CS1 AND CS22 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTSFOR CS3 AND CS41 x 64 KBIT/S GSL LINK


30 Sep 2003


68P02900W21-M

GMR-015�11

Typical parameter values

The parameters required to calculate BSC processing and signalling link capacities arelisted in Table 5-2 with their typical values.

Two methods for determining capacity are given. The first method is based on the typicalcall parameters given in Table 5-2 and simplifies planning to lookup tables, or simpleformulae indicated in Standard traffic model planning steps. When the call parametersbeing planned for differ significantly from the standard traffic model, more complexformulae must be used as indicated in Non-standard traffic model planning steps.

Table 5-2 Typical call parameters
















GPRS parameters












30 Sep 20035�12


GMR-0168P02900W21-M

Location update factor

The location update factor (L) is a function of the ratio of location updates to calls (l), theratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) orlong message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSIdetach is disabled) as in the first formula given below. When IMSI detach is enabled, thesecond or third of the formulas given below should be used. The type of IMSI detachused is a function of the MSC.


L = I


L = I + 0.2 * I


L = I + 0.5 * I

Other parameters

Other parameters used in determining GPROC and link requirements are listed inTable 5-3.

Table 5-3 Other parameters used in determining GPROC and link requirements


Number of MSC � BSC trunks N

Number of BTSs per BSS B

Number of cells per BSS C

Pages per call PPC = PGSM * (T/N)


30 Sep 2003


68P02900W21-M

GMR-015�13

Assumptions used in capacity calculations

Signalling message sequence and size assumptions

To calculate link and processing capacity values, certain signalling message sequencepatterns and message sizes have been assumed for the various procedures included inthe signalling traffic model. New capacity values may have to be calculated if the actualmessage patterns and message sizes differ significantly from those assumed. Theassumptions used for the capacity calculations in this manual are summarized below.The number of uplink and downlink messages with the respective average messagesizes (not including link protocol overhead) for each procedure are provided in Table 5-4,Table 5-5 and Table 5-6.

Table 5-4 Procedure capacities (MSC � BSC)

Procedure MSC to BSC link

Call setup and clearing 12 downlink messages with average size of 30 bytes11 uplink messages with average size of 26 bytes

Handover, incoming andoutgoing

5 downlink messages with average size of 33 bytes7 uplink messages with average size of 24 bytes

Location update 7 downlink messages with average size of 22 bytes7 uplink messages with average size of 27 bytes

SMS-P to P (see note below)


IMSI detach (type 1) 1 downlink messages with average size of 30 bytes1 uplink messages with average size of 42 bytes


Paging 1 downlink message with average size of 30 bytes

NOTE The actual number and size of messages required by SMSdepend on the implementation of the SMS service centre. Thenumbers given are estimates for a typical implementation. Thesenumbers may vary.


30 Sep 20035�14


GMR-0168P02900W21-M

Table 5-5 Procedure capacities (BSC � BTS)

Procedure BSC to BTS link





SMS-P to P 7 downlink messages with average size of 42 bytes7 uplink messages with average size of 42 bytes

Paging 1 downlink message. Message size depends on thenumber of cells to be paged on a site.

For a 3 cell site, message size for CS paging = 24 bytes.

One phase access 1 downlink message with average size of 21 bytes1 uplink message with average size of 21 bytes

Enhanced one phasemessages

2 downlink messages of 20 bytes and 1 byte respectively2 uplink messages with an average size of 4 bytes

NOTE From GSR6 onwards, the BSS software uses a new smallmessage header (compact header) for delivering messagesbetween the BSC/PCU and the BTS. The new message headercontains the minimum information necessary to deliver themessages between the processes. The size of the new messageheader is 8 bytes, as compared to 28 bytes in pre GSR6releases. This reduces the signalling link utilization between theBSC�BTS and BSC�PCU.

Table 5-6 Procedure capacities (BSC � RXCDR)

Procedure BSC to RXCDR link

XBL for new call 1 downlink message with average size of 41 bytes1 uplink message with average size of 41 bytes

An additional assumption, which is made in determining the values listed in the abovetables, is that the procedures not included in the traffic model are considered to have anegligible effect.

NOTE Supplementary Service (SS) messaging has not been taken intoaccount. This could contribute a significant signalling overhead insome networks.


30 Sep 2003


68P02900W21-M

GMR-015�15

Paging assumptions

In calculating the average DL message size for paging, it is assumed that paging is byLAC (or LAI) only. Paging by LAC only is the recommended method. Paging by LACand cell ID is not necessary and has two major disadvantages:

S The paging method is controlled by the MSC and is signalled to the BSC throughthe setting of the Cell Identification Discriminator in the BSSMAP paging message.The BSC can determine from its Configuration Management database which cellsneed to be paged from the location area code only. Therefore, the MSC does notneed to send a list of each individual cell identity. Paging by LAC and Cell ID willincrease the length of the BSSMAP paging considerably and will alsosignificantly increase the C7 signalling load between the MSC and BSC.

S Paging by LAC only reduces the possibility of paging channel overload on the airinterface caused by any database mismatches between the BSC and MSC. If theBSC receives a cell identity in the paging message from the MSC that does notexist in its Configuration Management database, it defaults to paging all cells in theBSS for safety reasons. This can cause overload of the paging channel on theradio interface.

Link capacities

The level of link utilization is largely a matter of choice of the system designer. A designthat has more links running at a lower message rate can have the advantage of offeringbetter 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 offerreduced queueing delays for signalling messages. A design that utilizes fewer links at ahigher message rate, reduces the number of 64 kbit/s circuits required for signalling, andpotentially reduces the number of resources (processors, data ports) required in theMSC. 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 40% utilizationwhen the MTL is running on a GPROC2. However, before use of the 40% utilization forGPROC2, it is imperative that the operator verifies that the MSC vendor can also support40% utilization at the MSC end; if not, only 20% link utilization should be used forGPROC2.

If higher link utilizations are used, the controlling GPROCs (LCF�MTLs) may becomeoverloaded.

NOTE Overloading GPROCs can cause the BSC to becomeunstable. Links must be monitored closely to ensure that linkutilization does not exceed the maximum.If link utilization is regularly approaching the maximum, additionalcapacity should be added to reduce the possibility of overloadingthe GPROCs.

C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from thefailed link to be redistributed among the remaining functioning links. A C7 link set officiallyhas at least two and at most 16 links. The failure of links, for any reason, cause thesignalling to be shared across the remaining members of the link set. Therefore, thedesign must plan for reserve link and processing capacity to support a certain number offailed signalling links.

GSR6 (Horizon II)Determining the number of RSLs required

30 Sep 20035�16


GMR-0168P02900W21-M

Determining the number of RSLs required

Introduction

Each BTS site which is connected directly to the BSC, including the first site in a daisychain, must be considered individually. Once individual RSL requirements are calculatedthe total number of LCFs can be determined for the BSC.


The following factors should be considered when planning the provision of RSL (LAPDsignalling) links from the BSC to BTS sites:

S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTSsite. One link can support multiple collocated cells. As the system grows,additional signalling links may be required. Refer to the section Determining therequired BSS signalling link capacities in this chapter to determine the numberof RSL links required.

S If closed loop daisy chains are used, each site requires a RSL in both directions.

S The provision of additional RSL links for redundancy.

S The number of 16 kbit/s RSL links is limited, depending on the platform. See16 kbit/s RSL in Chapter 2 for further details. 64 kbit/s RSLs must be used whenallowable numbers are exceeded.

Table 5-7 lists the number of 16 kbit/s RSLs supported on each BTS platform.

Table 5-7 BTS support for 16 kbit/s RSLs

BTS Platform No. of 16 kbit/sRSLs Supported

A BSU-based BTS 8

Horizon II macro and Horizonmacro 6

Horizonmicro2 / Horizoncompact2 2

M-Cell6 6

M-Cell2 4

M-Cellmicro and M-Cellcity 2

NOTE Horizon II macro BTSs support 4 x RSLs per E1, whereasHorizonmacro and M-Cell BTSs only support 2 x RSLs per E1.This should be taken into consideration when determining thenumber of E1s required to support the calculated RSLs per site.

GSR6 (Horizon II) Determining the number of RSLs required

30 Sep 2003


68P02900W21-M

GMR-015�17

Determining the number of RSLs

The RSL signalling link provisioning has a contribution from the GSM circuit-switchedpart of the network and from the GPRS part. The equation for determining the number ofRSL links for the combined signalling load is as follows:

RSLGPRS�GSM � RSLGPRS � RSLGSM

This is evaluated for 16 kbit/s RSLs or for 64 kbit/s RSLs. The interface between the BTSand BSC does not permit mixing the two RSL rates.

Where: RSLGPRS+GSM is: The combined number of RSLsignalling links on a per BTS sitebasis operating at a 16 kbit/s RSLrate or at a 64 kbit/s RSL rate.

RSLGPRS This is the number of RSLsignalling links required to servethe GPRS part of the network at16 kbit/s or at 64 kbit/s.

RSLGSM This is the number of RSLsignalling links required to servethe GSM part of the network at16 kbit/s or at 64 kbit/s.


30 Sep 20035�18


GMR-0168P02900W21-M

Standard traffic model

The number of BSC to BTS signalling links (RSLs) must be determined for each BTS.This number depends on the number of TCHs and PDCHs at the BTS. Table 5-8 givesthe number of RSLs required (rounded up integer value) for a BTS to support the givennumber of TCHs and PDCHs, based on the typical call parameters given in the standardtraffic model column of Table 5-2. If the call parameters differ significantly from thestandard traffic model, use the formulae for the non-standard traffic model.

Table 5-8 Number of BSC to BTS signalling links

With Enhanced One Phase With One Phase Access

#TCHs/BTS

(n)

#PDCHs/BTS

(Ngprs)

# 64 kbit/sRSLs

# 16 kbit/sRSLs

# 64 kbit/sRSLs

# 16 kbit/sRSLs

<= 30 0 1 1 1 1

15 1 2 1 2

30 1 2 1 2

31 to 60 0 1 2 1 2

15 1 3 1 3

30 1 3 1 3

45 1 3 1 3

60 1 3 1 3

61 to 90 0 1 3 1 3

15 1 4 1 4

30 1 4 1 4

45 1 4 1 4

60 1 4 1 4

75 1 4 1 4

90 1 4 1 4

91 to 120 0 1 4 1 4

15 2 5 2 5

30 2 5 2 5

45 2 5 2 5

60 2 5 2 5

75 2 5 2 5

90 2 5 2 5

(continued)


30 Sep 2003


68P02900W21-M

GMR-015�19

With Enhanced One Phase With One Phase Access

#TCHs/BTS

(n)

#PDCHs/BTS

(Ngprs)

# 64 kbit/sRSLs

# 16 kbit/sRSLs

# 64 kbit/sRSLs

# 16 kbit/sRSLs

121 to 150 0 2 5 2 5

15 2 5 2 5

30 2 5 2 5

45 2 5 2 5

60 2 5 2 5

151 to 180 0 2 5 2 5

15 2 6 2 6

30 2 6 2 6

45 2 6 2 6

60 2 6 2 6

NOTE The RSL calculations assume PGPRS = 0 for cells in which Ngprs= 0. This may not necessarily be true. If the BSC has GPRStimeslots, even if the cells do not have traffic channelsconfigured as PDCHs, it may have paging traffic.RACH_Arrivals/sec figures have been calculated assumingAvg_Sessions_per_user is as in the call model table.GPRS_Users_BTS has been calculated based on the number oftimeslots configured on the cell.A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, butnot both.


30 Sep 20035�20


GMR-0168P02900W21-M

Non-standard traffic model

64 kbit/s RSLs

If the call parameters differ significantly from those given in Table 5-2, use the followingformula to determine the required number of 64 kbit/s RSLs.

RSLGSM@64k �

n * (49 � 50 * S � 32 * H � 20 * L)1000 * U * T

�(27 � 3 * CBTS) * PGSM

8000 * U

The RSL traffic load for GPRS depends on the access mechanism used on the airinterface. From GSR6 onwards, Motorola BSCs allow use of one phase access or aMotorola proprietary enhanced one phase mechanism.

With one phase access

RSLGPRS@64k �

(32 � CBTS) * PGPRS

8000 * U�

RACH_Arrivals�sec * 41000 * U

�RACH_Arrivals�sec * 5 * 0.3

1000 * U

With enhanced one phase

RSLGPRS@64k �

(32 � CBTS) * PGPRS

8000 * U�



1000 * U

Therefore:

RSL(GSM�GPRS)@64k � Round up(RSLGSM@64k � RSLGPRS@64k)

16 kbit/s RSLs

If the call parameters differ significantly from those given in Table 5-2, use the followingformula to determine the required number of 16 kbit/s RSLs.

RSLGSM@16k �

�n * (49 � 50 * S � 32 * H � 20 * L)1000 * U * T

�(27 � 3 * CBTS) * PGSM

8000 * U� * 4


RSLGPRS@16k �

�(32 � CBTS) * PGPRS

8000 * U�



1000 * U� * 4


RSLGPRS@16k �

�(32 � CBTS) * PGPRS

8000 * U�



1000 * U� * 4

Therefore:

RSL(GSM�GPRS)@16k � Round up(RSLGSM@16k � RSLGPRS@16k)


30 Sep 2003


68P02900W21-M

GMR-015�21

RACH arrivals

The number of RACH arrivals per second is roughly calculated as follows:

RACH_Arrivals�sec �GPRS_Users_BTS * Avg_Sessions_per_user

3600

In the above equations:

RSLGSM + GPRS is: the number of BSC to BTS signallinglinks.

n the number of TCHs at the BTS site.

S the ratio of SMSs to calls.

H the number of handovers per call.

L the location update factor.

U the percent link utilization (for example0.20).

T the average call duration.

PGSM the GSM paging rate in pages persecond.

PGPRS the GPRS paging rate in pages persecond.

CBTS the number of cells at the BTS.

RACH_Arrivals/sec the number of RACH arrivals persecond per BTS.

GPRS_Users_BTS the number of GPRS users on the BTS.

Avg_Sessions_per_user the average number of sessions peruser in a busy hour. This includes thesessions required for signalling (attach,detach, PDP context activation/deactivation, routeing area updates,etc.).

NOTE RACH/sec depends on the traffic profile on the network. For thesame amount of data transferred in per user in a busy hour, if thetraffic is predominantly WAP then the number of RACH arrivalswill be very high compared to when the data traffic ispredominantly FTP transfers. The traffic profile needs to becalculated based on applications running on the network.With the introduction of the Interleaving TBF feature in GSR6, itis expected that the sessions arrival rate in each cell maypotentially be higher than for previous GSRs. With interleavingTBFs it is possible to have multiple MSs on each timeslot.Customers should take this fact into account when estimating thesessions for the above formula.


30 Sep 20035�22


GMR-0168P02900W21-M

BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links may beadded, if required.

Use the following equation to determine the impact of different coding schemes oninterconnect planning:

NBSC�BTS �{(nCGPRS * 4) � (nGGPRS * 2) � (L16�4)} � L64

31

Where: NBSC�BTS is: the minimum number of E1 links required(rounded up to an integer).

nCGPRS the number of carriers with GPRS CS3 and CS4enabled.

nGGPRS the number of carriers with GPRS CS1 and CS2enabled and GSM voice only carriers.

L16 the number of 16 kbit/s RSLs (LAPD links).


NOTE Refer to Chapter 2 in this manual, for a discussion on TCHplanning for the BTS concentration feature.This formula includes both L16 and L64 to provide the necessarynumber of RSLs. As above, either L16 or L64 RSL can be used,but not both, to a single BTS.

Backhaul requirements

The backhaul requirements for the different coding schemes and configurations aredefined as follows:

16 kbit/s: GSM voice only carriers.

Carriers with only GPRS CS1 and CS2 enabled.

32 kbit/s: Carriers with GPRS CS1, CS2, CS3 and CS4 enabled.

BSC to BTS E1 interconnect planning example

Assume a 3 sector BTS with 8 carriers per sector. Each sector has 4 carriers of GSMvoice, 1 carrier with GPRS CS1 and CS2, and 3 carriers of GPRS CS1, CS2, CS3 andCS4.

The number of E1s required is calculated as follows:

{(9 * 4) � (15 * 2) � 0} � 131

� 3

In this example, 3 E1s are required to backhaul this BTS to the BSC. To find the totalnumber of E1s required for a BSC, all of the individual BTSs backhaul requirements needto be calculated and then added together. The network configuration would need to beexamined to determine if backhaul from multiple BTSs could be multiplexed on a singleE1. Examples of this type of capability would be if the BTSs are daisy-chained, or if thenetwork uses cross-connect equipment between BTSs and BSCs.


30 Sep 2003


68P02900W21-M

GMR-015�23

BSC to BTS T1 interconnect planning actions

Determine the number of T1 links required to connect to a BTS. Redundant links may beadded, if required.

NOTE GPRS is not currently supported over a T1 interface.

Use the following equation:

NBSC�BTS �[(nTCH + L16) / 4] + L64

24

Where: NBSC-BTS is: the minimum number of T1 links required(rounded up to an integer).

nTCH the number of GSM traffic channels at the BTS.



NOTE Refer to Chapter 2 in this manual, for a discussion on TCHplanning for the BTS concentration feature.This formula includes both L16 and L64 to provide the necessarynumber of RSLs. As above, either L16 or L64 RSL can be used,but not both, to a single BTS.


30 Sep 20035�24


GMR-0168P02900W21-M

Determining the number of LCF-GPROC2s for RSL processing

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 callparameters are similar to those listed in Table 5-2 (standard traffic model). The secondmethod is used when the call parameters differ significantly from those listed in Table 5-2(non-standard traffic model).


Use the formula:

GL3 � n1060

� B160

� C120

Where: GL3 is: the number of LCF GPROC2s required to support thelayer 3 call processing.

n the number of TCHs at the BSC.

B the number of BTS sites.

C the number of cells.


If the call parameters differ significantly from those given in Table 5-2, the alternativeformula given below should be used to determine the recommended number of LCFs.

GL3 �

�n * (1 � 0.35 * S � 0.34 * H * (1 � 0.4 * i) � 0.32 * L)(19.6 * T)

� (0.00075 * PGSM � 0.004) * B � C120�


n the number of TCHs under the BSC.



i the ratio of intra-BSC handovers to all handovers.



PGSM the GSM paging rate in pages per second.



NOTE Having calculated the LCF-GPROC2s for RSLs, ensure that thetraffic is evenly distributed across the LCFs. This may be difficultin cases where large sites are being used, and in such casesadditional LCFs may be required. Alternatively, use the aboveformula for traffic channels on each LCF. If the calculated valueexceeds 1, the sites should be redistributed on the otheravailable LCFs, or additional LCFs should be equipped.


30 Sep 2003


68P02900W21-M

GMR-015�25

The LCF GPROC2 can simultaneously handle signalling traffic from both the GSM andGPRS parts of the network. It is possible to calculate the GPRS part of the signallingload for the LCF GPROC2 in fractional increments. The GPRS LCF GPROC2requirements can be directly added to the GSM requirements in order to determine thetotal number of LCF GPROC2s to equip at a BSC.

The MSC can send GSM alerting pages to a GPRS mobile that operates in class A orclass B modes. The significance of this is that GPRS mobile stations capable of class Aand B operation create a larger population of GSM capable mobile stations that shouldbe considered when provisioning the LCF GPROC2.

The planning information provided here should be used for this provisioning.

GL3_GPRS �

NGPRSGGPRS_PF*TGPRS

� (0.006 � 0.02 * PGPRS) * (BRA_GPRS) �CGRPS

35

2.5

Where: GL3_GPRS is: Number of LCF GPROC2s tohandle GPRS related RSLsignalling traffic.

NGPRS Number of active GPRS timeslotsserved at the BSC.

GGPRS_PF GPROC2 GPRS performancefactor for RSL processing.

TGPRS Mean duration of a TBF inseconds.

PGPRS Paging rate in pages per second.

BRA_GPRS Number of BTS sites under a BSC.

CGPRS Number of cells under a BSC.

The value for NGPRS is determined using the following equation:

NGPRS � MIN[No_PRP_boards * 30, No_GPRS_ts * Mslot_Util_factor]

Where: NGPRS is: Number of active GPRS timeslotsserved at the BSC.

No_PRP_boards Number of PRP boards in the PCU.

No_GPRS_ts Number of GPRS timeslots in all ofthe BTS cells served by the BSC.

Mslot_Util_factor This is the ratio of the meannumber of active timeslots on aGPRS carrier to the total number ofprovisioned GPRS timeslots on acarrier.


30 Sep 20035�26


GMR-0168P02900W21-M

Using the figures in Table 5-9, it can be determined that six LCF GPROC2s may berequired for a maximally configured PCU.

Table 5-9 Typical values for GPRS LCF GPROC2 provisioning

Parameter Value

NGPRS 30 to 270 is the range for the number of active timeslotsprovisioned at one PCU.

GGPRS_PF 100.

TGPRS 1 second, corresponds to the duration of time to transmit twomean length LLC PDUs at the CS2 rate.

PGPRS 12, for a fully configured redundant PCU with a 10% pagingload based on a mean number of active timeslots equal to120.

BRA_GPRS 1 to 100 for the number of BTS sites under a BSC.

CGPRS 1 to 250 for the number of cells in a BSC routeing area.

Mslot_Util_factor 0.5.

No_PRP_boards This number can range from 1 to 10.

No_GPRS_ts This number can range from 1 to 270.

GSR6 (Horizon II) Determining the number of MTLs required

30 Sep 2003


68P02900W21-M

GMR-015�27

Determining the number of MTLs required

Introduction

MTLs carry signalling traffic between the MSC and BSC. The number of required MTLsdepends upon the BSS configuration size and traffic model. MTLs are carried on E1 orT1 links between the MSC and BSC, which are also used for traffic.


The following factors should be considered when planning the links from the BSC toMSC:

S Determine traffic requirements for the BSC. Traffic may be determined using eitherof the following methods:

� Multiply the number of subscribers expected to use the BSC by the averagetraffic per subscriber.

or

� Total the traffic potential of each BTS under the BSC; determined by thenumber of TCHs available, the number of TCHs required or the subscriberpotential.

S Determine the number of trunks to support the traffic requirements of the BSCusing Erlang B tables at the required blocking rate.

S Determine the MTL loadshare granularity to be used for the BSC. MTL loadsharegranularity determines the number of logical links that will be mapped onto thephysical links. Setting the mtl_loadshare_granularity database element to 1 resultsin a more even distribution of traffic across the MTL links. This feature allows amore gradual increase in the number of MTLs required with the increased trafficload on the BSC.

For example, with an increase in the number of MSC�BSC trunks from 1560 to 1600,with 20% link utilization, the number of MTLs required for a BSC goes up from 8 to 16, ifusing a granularity of 0. When using a granularity of 1, only 10 MTLs will be required.This results from the enhanced load sharing of MTLs and illustrates the differencebetween setting the load share granularity to 0 and 1 respectively. Table 5-10 andTable 5-11 illustrate the difference between setting the loadshare granularity to 0 and 1.

NOTE These calculations are for the MTLs required from the BSSperspective, using the BSS planning rules. If the MSC vendorsupplies their own planning rules for a given configuration, themore conservative MTL provisioning figures should be used. Ifthe MSC vendor does not provide the planning rules for theMTLs required in a downlink direction, then use a load sharegranularity of 0 to be conservative in MTL provisioning.Load sharing of MTLs in the downlink direction depends on themechanism used by the MSC to load share the signalling linksfrom the MSC to BSC.

GSR6 (Horizon II)Determining the number of MTLs required

30 Sep 20035�28


GMR-0168P02900W21-M


The number of MSC to BSC signalling links (MTL) required depends on the desired linkutilization, the type and capacity of the GPROCs controlling the MTLs and the MTLloadshare granularity. The BSS software distributes call signalling traffic across 16 or 64logical links, which are then evenly spread across the active MTLs.

CCITT C7 uses a 4 bit number, the Signalling Link Selection (SLS), generated by theupper layer to load share message traffic among the in-service links of a link set. Whenthe number of in-service links is not a power of 2, some links may experience a higherload than others. From GSR5 release onwards, the BSS supports distribution ofsignalling in the uplink direction, over 64 logical links. The BSS evenly distributes the 64logical links over the active MTLs.

The number of MTLs is a function of the number of MSC to BSC trunks or the offeredcall load and signalling for the call load. Table 5-10 and Table 5-11 give the recommendedminimum number of MSC to BSC signalling links based on the typical call parameters,detailed in Table 5-2. The value for N is the greater of the following:

S The offered call load (in Erlangs) from all the BTSs controlled by the BSC.

S The potential carried load (approximately equal to the number of MSC to BSCtrunks).

The offered call load for a BSS is the sum of the offered call load from all of the cells ofthe BSS. The offered call load at a cell is a function of the number of TCHs and blocking.As blocking increases the offered call load increase. For example, for a cell with 15 TCHsand 2% blocking, the offered call load is 9.01 Erlangs.

NOTE Before setting the load share granularity to 1, it is recommendedthat confirmation is gained from the Motorola local contact, orlocal office, that the switch is compatible with the load sharegranularity set to 1.


30 Sep 2003


68P02900W21-M

GMR-015�29

Table 5-10 and Table 5-11 show how to estimate the number of MTLs to be used for theBSC, with 20% and 40% link utilization, respectively.

Table 5-10 Number of MSC and BSC signalling links (20% utilization)

N = the greater ofnumber of MSC-BSC

No. of MTLs with 16logical links


number of MSC-BSCtrunks or the offeredload from the BTSs

Minimumrequired

Recommended Minimumrequired

Recommended

N <= 180 1 2 1 2

180< N <=380 2 3 2 3

380 < N <= 520 3 4 3 4

520 < N <= 780 4 5 4 5

780 < N <= 960 6 7 5 6

960< N <= 1040 6 7 6 7

1040< N <= 1120 8 9 6 7

1120< N <= 1240 8 9 7 8

1240< N <= 1560 8 9 8 9

1560< N <= 1780 16 16 10 11

1780< N <= 2080 16 16 11 12

2080< N <=2480 16 16 13 16

2480< N <=3200 16 16 16 16


30 Sep 20035�30


GMR-0168P02900W21-M

Table 5-11 Number of MSC and BSC signalling links (40% utilization)




number of MSC-BSCtrunks or the offeredload from the BTSs

Minimumrequired


Recommended

N <= 380 1 2 1 2

380< N <=780 2 3 2 3

780 < N <= 1040 3 4 3 4

1040 < N <= 1120 4 5 3 4

1120 < N <= 1560 4 5 4 5

1560< N <= 1920 6 7 5 6

1920< N <= 2080 6 7 6 7

2080< N <= 2260 8 9 6 7

2260< N <= 2480 8 9 7 8

2480< N <= 3120 8 9 8 9

3120< N <= 3200 16 16 10 11

NOTE The capacities shown in Table 5-10 and Table 5-11 are based onthe standard traffic model shown in Table 5-2.It is recommended that the C7 links be designed to operate at nomore than 20% link utilization when the MTL is running on aGPROC, and no more than 40% utilization when the MTL isrunning on a GPROC2. However, before using MTLs with 40%utilization, it is imperative that the operator verifies if the MSCvendor can also support 40% utilization at the MSC end. If not,then only 20% link utilization should be used for GPROC2.From GSR4 onwards, GPROC2 is the only GPROC type that issupported on the BSC.


30 Sep 2003


68P02900W21-M

GMR-015�31


If the call parameters differ significantly from those given in Table 5-2, the followingprocedure is used to determine the required number of MSC to BSC signalling links:

1. Use the formula detailed below to determine the maximum number of Erlangssupported by a C7 signalling link (nlink).

nlink �(1000 * U * T)

(40 � 47 * S � 22 * H * (1 � 0.8 * i) � 24 * L � 9 * PPC)

2. Use the formula detailed below to determine the maximum number of Erlangssupported by a GPROC2 (LCF�MTL) supporting a C7 signalling link (nlLCF�MTL).

nlLCF�MTL �(20 * T)

(1 � 0.16 * S � 0.5 * H * (1 � 0.6 * i) � 0.42 * L � PPC * (0.005 * B � 0.05))

3. The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is thesmaller of the two numbers from steps 1 and 2.

nlmin � MIN(nlink, nlLCF_MTL)

4. Signalling over the A�interface is uniformly distributed over a number of logicallinks. The number of logical links is defined on the BSC by database parametermtl_loadshare_granularity = 0 or 1, which corresponds to 16 or 64 logical links,respectively, over which the MTL signalling is load shared. Hence, the total amountof traffic that a logical link would hold, is calculated as:

Nlogical � NNg

5. Next we need to determine the number of logical links each MTL (physical link)can handle (nlog-per-mtl):

nlog_per_mtl � round down � nlmin

Nlogical�

6. Finally, the number of required MTLs (mtls) is:

mtls � round up � Ngnlog_per_mtl

�� R � 16

NOTE mtls should not exceed 16 per BSC.The formula in step 2 has been calculated using 70% meanutilization of GPROC2.Field experience suggests it is good practice to maintain themean utilization of GPROCs at or below 70%.Taking LCS into consideration, C7 is also used for LCS signallingbetween the BSC and MSC and LCS signalling between BCSand SMLC if BSS based LCS architecture is supported. Refer toChapter 8, Determining the required BSS signalling linkcapacities.


30 Sep 20035�32


GMR-0168P02900W21-M

Where: U is: the percent link utilization (for example 0.20).

T call hold time.

S the ratio of SMSs per call.


i the ratio of intra-BSC handovers to allhandovers.


PPC the number of pages per call.

B the number of BTSs supported by the BSC.

mtls the number of MTLs required

round up round up to the next integer.

round down round down to the next integer.

MIN the minimum of two values.

Ng the number of logical links (16 or 64).

R the number of redundant MTLs.


30 Sep 2003


68P02900W21-M

GMR-015�33

Calculate the number of LCFs for MTL processing

The purpose of the LCF GPROC2 is to support the functions of MSC link protocol,layer 3 call processing, and the BTS link protocol. It is recommended that an LCFsupports either 2 MTLs or 1 to 30 BTSs, with up to 31 RSLs and layer 3 call processing.

NOTE It is not recommended that an LCF supports both an MTL andBSC to BTS signalling links.

LCFs for MSC to BSC links

Since one LCF GPROC2 can support two MTLs, the number of required LCFs is:

NLCF � ROUND UP �mtls2�

However, if the traffic model does not conform to the standard model:

if 2 * nlink � nlLCF�MTL, then NLCF � mtls

otherwise:


Where: NLCF is: the number of LCF GPROC2s required.

ROUND UP rounding up to the next integer.

mtls calculated in the previous section.

nlink calculated in the previous section.

nlLCF-MTL calculated in the previous section.

MSC to BSC signalling over a satellite link

The BSC supports Preventive Cyclic Retransmission (PCR) to interface to the MSC overa satellite link. PCR retransmits unacknowledged messages when there are no newmessages to be sent. This puts an additional processing load on the GPROC2(LCF�MTLs) controlling the C7 signalling links. It is recommended that when PCR isused, that the number of MTLs (and thus the number of LCF�MTLs) be doubled from thenumber normally required.

GSR6 (Horizon II)Determining the number of XBLs required

30 Sep 20035�34


GMR-0168P02900W21-M

Determining the number of XBLs required

IntroductionXBLs carry the signaling traffic between the BSC and RXCDR. The number of XBL linksrequired depends upon the number of CICs and/or the number of Ater interfacechannels.

Planning considerationsThe following factors need to be considered when planning the number of XBL links fromthe BSC to the RXCDR:

S Determine the traffic requirements of the BSC and/or the number of trunks (CICs)used between the BSC and RXCDR.

S Determine the mode (backward compatibility or auto-connect/ enhanced autoconnect) in which the BSC and RXCDR operate. See Chapter 2 for a descriptionof the modes.

S A maximum of 18 XBLs (64 kbit/s or 16 kbit/s) can be configured for aBSC/RXCDR.

S A BSC can connect to a maximum of 9 RXCDRs and vice-versa.

Determining the number of XBLsThe calculations below should be performed for every connected RXCDR.

The number of XBL links depends on the number of trunks on the BSC-RXCDR interfaceand whether or not the auto-connect mode or enhanced auto-connect mode is enabled atthe RXCDR/BSC. Table 5-12 details the minimum number of XBLs required to supportthe given number of trunks between the BSC and RXCDR, with auto-connect mode orenhanced auto-connect mode.

Table 5-12 Number of BSC to RXCDR signalling links

N = number ofMSC to BSC

trunks

No redundancy With redundancy

Number of64 kbit/s

XBLs

Number of16 kbit/s

XBLs

Number of64 kbit/s

XBLs

Number of16 kbit/s

XBLs

N < 1200 1 4 2 8

1200 < N < 2400 2 8 4 16

2400 < N < 3200 3 11 6 22 *

* This exceeds the 18 XBL limit and is therefore not a valid configuration.

It is recommended that the XBL link utilization does not exceed 40%. This allows a link todouble it�s capacity (to 80%) under fault conditions (in some configurations). Above 80%utilization, queueing delays could become substantial. Although both auto-connect modeand enhanced auto-connect mode apply a load, it is the enhanced auto-connect modeload that can vary depending on system configuration. When operating in this mode, theXBL link utilization should be monitored to determine if additional capacity is required.The number of XBL links as shown above is a minimum number that are required,regardless of measured utilization. This is due to peak usage requirements during startup and reconfigurations due to faults and maintenance.

XBL link utilization is a network statistic, calculated on a per XBL basis.

GSR6 (Horizon II) Determining the number of XBLs required

30 Sep 2003


68P02900W21-M

GMR-015�35


The minimum number of XBL links required as given in Table 5-12 were verified using astandard set of call parameters. These are given in Table 5-2.

Non standard traffic model

If the call parameters differ significantly from those given in Table 5-2, use the followingformula to determine the required number of 64 kbit/s XBLs (rounded up to the nextinteger):

XBL � N * 5.11000 * UXBL * T

Use the following formula to determine the required number of 16 kbit/s XBLs (roundedup to the next integer):

XBL � � N * 5.11000 * UXBL * T

� * 4

Where: XBL is: the number of BSC to RXCDR signalling links.

N the number of MSC�BSC trunks.

UXBL the percent link utilization for XBLs (for example0.40).

T The average call duration in seconds.

GSR6 (Horizon II)Determining the number of GSLs required

30 Sep 20035�36


GMR-0168P02900W21-M

Determining the number of GSLs required


The PCU requires one E1 in order to carry GSL signalling, and a second E1 forredundancy. The PCU can support up to six primary GSL 64 kbit/s timeslots and sixredundant. Each 64 kbit/s timeslot is one LAPD channel. Provisioned GSL timeslots areload-balanced over two E1 links, as the mechanism for providing resiliency against linkfailures. It is recommended that two GSL E1 links are provisioned for resiliencepurposes, even when the GSL is lightly loaded.

Each GSL message consists of three parts: LAPD protocol, BSS executive headerprotocol, and the application message carrying actual signalling information. The LAPDand BSS protocol parts can be considered messaging overhead. Also, in a similarmanner to RSL, the GSL traffic depends on the access mechanism used on the Airinterface. The calculation for the required number of GSL links is as shown below.

With the introduction of one phase access, there is additional loading on the RSL andGSL due to enhanced one phase messaging and immediate assignment messages forUL TBF setups.


GSL �6 * PGPRS � Total_RACH�sec * 4 � Total_RACH�sec * 1.5

1000 * U


GSL �6 * PGPRS � Total_RACH�sec * 6 � Total_RACH�sec * 1.5

1000 * U

Therefore:

Total_RACH�sec �GPRS_subs_per_PCU * Avg_session_per_subs

3600

Where: GSL is: the number of 64 kbit/s LAPD GSLtimeslots to provision.

PGPRS the GPRS paging rate in pages persecond.

Total_RACH/sec the sum of all RACH arrivals on theBSC.

U the link utilization, typically 0.25.

GPRS_subs_per_PCU the total GPRS users under a PCUin the busy hour.

Avg_session_per_subss the average number of sessionsper subscriber in a busy hour (thisincludes sessions for signalling).

GSR6 (Horizon II) Determining the number of GSLs required

30 Sep 2003


68P02900W21-M

GMR-015�37

Load balancing

The GSL traffic is load balanced over all GSLs. The first E1 carries up to six LAPD linksand the second E1 up to another six. For LAPD-type GDS resiliency, two E1s arerecommended, regardless of the number of LAPD channels required.

NOTE All available GSL timeslots are used to enable fast synchronizedPCU software downloads. This reduces the PCU softwaredownload time considerably.

For example, if only one channel is required to carry the expected signalling load, twoE1s with one LAPD channel per E1 should be used. The MPROC load balancingsoftware distributes the load evenly between the two LAPD channels.

GSR6 (Horizon II)Generic processor (GPROC2)

30 Sep 20035�38


GMR-0168P02900W21-M

Generic processor (GPROC2)

Introduction

The generic processor (GPROC2) is a direct replacement for the original GPROC and isused throughout the Motorola BSS as a generic control processor board. GPROC2s areassigned functions and are then known by their function names.

This section describes the BSC GPROC types and their functions. The BSCconfiguration type and GPROC device type are essential factors for BSC planning.

From GSR4 onwards, GPROC2s must be installed in all the slots at the BSC.

GPROC2 functions and types

The GPROC2 is the basic building block of a distributed architecture. The GPROC2provides the processing platform for the BSC. By using multiple GPROC2s, softwaretasks can be distributed across GPROC2s to provide greater capacity. The set of tasksthat a GPROC2 is assigned, depends upon the configuration and capacity requirementsof the BSC. Although every GPROC2 is similar from a hardware standpoint, when agroup of tasks are assigned to a GPROC2, it is considered to be a unique GPROC2device type or function in the BSC configuration management scheme.

There are a limited number of defined task groupings in the BSC, which result in thenaming of four unique GPROC2 device types for the BSC. The processing requirementof a particular BSC determines the selection and quantity of each GPROC2 device type.

The possible general task groupings or functions for assignment to GPROC2s are:

S BSC common control functions.

S OMC-R communications � OML (X.25) including statistics gathering.

S MSC link protocol (C7).

S BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD).

S Cell broadcast centre link (CBL).

The defined GPROC2 devices and functions for the BSC are:

S Base Site Control Processor (BSP).

S Link Control Function (LCF).

S Operations and Maintenance Function (OMF).

S Code Storage Facility Processor (CSFP).

At a combined BSC BTS site, the BTF and DHP are additional GPROC2 function andtype in the network element.

GSR6 (Horizon II) Generic processor (GPROC2)

30 Sep 2003


68P02900W21-M

GMR-015�39

BSC types

The BSC is configured as one of two types; the type is determined by the GPROCspresent.

S BSC type 1

� Master GPROC2.

Running the base site control processor (BSP) and carrying out operationsand maintenance functionalities.

� Link control processor (LCF).

Running the radio signalling link (RSL) and layer 3 processing or MTL (C7signalling link) communications links. It also runs the GSLs for GPRSsignalling between the BSC and PCU.

S BSC type 2

� Master GPROC2.

Running the BSP.

� LCF.

� OMF.

Running the O&M, including statistics collection, and OML link (X.25 controllinks to the OMC-R).


The following factors should be considered when planning the GPROC2 complement:

S Each BSC requires:

� One master GPROC2 (BSP).

� One OMF (if it is a type 2 BSC).

� A number of LCFs for MTLs, see Link control function below.

� LCFs to support the RSL and control of the BTSs.

� LCFs to support the GSLs for GPRS signalling between the BSC and PCU.

S Optional GPROCs Include:

� One redundant master GPROC2 (BSP).

� At least one redundant pool GPROC2 (covers LCFs).

� An optional dedicated CSFP.

S A maximum of eight GPROC2s can be supported in a BSU shelf.

S The master GPROC slot (20) in the first shelf should always be populated toenable communication with the OMC-R.

S For redundancy, each BSC should be equipped with a redundant BSP controllerand an additional GPROC2 to provide redundancy for the signalling LCFs. Wheremultiple shelves exist, each shelf should have a minimum of two GPROC2s toprovide redundancy within that shelf.


30 Sep 20035�40


GMR-0168P02900W21-M

Link control function

The following factors should be considered when planning the number of LCFs:

S MTLs are handled by dedicated LCFs.

S GPROC2s can handle up to two MTLs.

S A single GPROC LCF can handle up to 800 active calls if thessm_critical_overload_threshold is set to 100. The default value is 80,meaning that the 641st non-emergency call will be rejected (80% x 800 = 640active calls).

NOTE Refer to Technical Description: BSS Command Reference(68P02901W23 ) for further details.

S For optimum performance, GSL handling should be distributed among the LCFsthat terminate RSLs. (See Load balancing in the previous section.)

NOTE Combining MTL and RSL processing on a single GPROC2 is notrecommended.

The planning rules for LCFs using GPROC2s are:

S A single GPROC2 will support two MTLs each working at 20% link utilization.However, if the link utilisation is higher, the actual number of MTLs supported perLCF depends on the Erlangs supported per LCF and MTL for that particular callmodel.

S If any LCF does not satisfy the above criteria, either rebalancing of sites on theavailable LCF GPROC2s at the BSC is required or additional LCF GPROC2s mayneed to be equipped at the BSC to handle the traffic load.

S The link utilization of a RSL should not exceed 25%.

S A single GPROC2 can support up to 12 GSLs. This is set by the GPROCmax_gsls parameter.

S Up to 25 LCFs can be supported.

S A maximum of 31 BTS sites can be controlled by a single LCF. All RSLs (LAPDlinks) for the BTSs will terminate on the same GPROC2, so if return loops areused the maximum number of BTS sites will be 15 (if GPROC_slots = 31). IfGPROC_slots is set to 16 then at most 15 RSLs may exist which would supportup to seven BTS sites.

NOTE The number of serial links per GPROC2 must be determined foreach site. The current values are 16 or 32 with 16 being thedefault value. One link is reserved for each board (for GPROCtest purposes) so the number of available serial links is either 15or 31. However, when the links are running at high load, theGPROC2 may experience some performance problems whenterminating 31 links. Hence, the use of more than 15 links perboard is not recommended.

GSR6 (Horizon II) Generic processor (GPROC2)

30 Sep 2003


68P02900W21-M

GMR-015�41

GPROC2 planning actionsDetermine the number of GPROC2s required.

NGPROC2 � 2B � L � C � R

Where: NGPROC2 is: the total number of GPROC2s required.

B the number of BSP GPROC2s (2B for redundancy).

L the number of LCF GPROC2s.

C the number of CSFP GPROC2s.

R the number of pool GPROC2s (for redundancy).

NOTE If dedicated GPROC2s are required for either the CSFP or OMFfunctions then they should be provisioned separately.

Cell broadcast linkThe cell broadcast link (CBL) connects the BSC to the cell broadcast centre. For typicalapplications (less than ten messages per second), this link can exist on the same LCF asthat used to control BTSs. The CBL should not be controlled by a LCF�MTL (a GPROC2controlling an MTL).

OMF GPROC2 requiredThe BSC type 2 configuration offloads many of the O&M functions and control of theinterface to the OMC-R from the BSP. One of the major functions offloaded from the BSPis the central statistics process.

From GSR5 onwards, it is strongly recommended to equip an OMF.

Code storage facility processorThe BSS supports a GPROC2 acting as the code storage facility processor (CSFP). TheCSFP allows pre-loading of a new software release while the BSS is operational.

If a dedicated GPROC2 is to exist for the CSFP, an additional GPROC2 will be required.

When Horizon II macro, Horizonmacro or M-Cell BTSs are connected to the BSC, adedicated CSFP is required at the BSC and a second dedicated CSFP should beequipped for redundancy.

The BSS supports a method whereby a dedicated CSFP GPROC2 is not required. Thismethod is called configure CSFP and works as follows:

The system can borrow certain devices and temporarily convert them into a CSFP, andwhen the CSFP functionality is no longer needed the device can be converted back intoits previous device. The devices the system can borrow are a redundant BSP/BTP or apooled GPROC2.

This functionality allows an operator who already has either a redundant BSP/BTP or apooled GPROC2 in service to execute a command from the OMC-R to borrow the deviceand convert it into a CSFP. The operator can then download the new software load ordatabase and execute a CSFP swap. Once the swap has been completed and verifiedas successful, the operator can return the CSFP back to the previous redundant orpooled device type via a separate command from the OMC-R.

See Service Manual: BSC/RXCDR (68P02901W38) for more details.


30 Sep 20035�42


GMR-0168P02900W21-M

GPROC2 redundancy

BSP redundancy

The failure of the BSP GPROC2 will cause a system outage. If the BSC is equipped witha redundant BSP GPROC2, the system will restart under the control of the redundantBSP GPROC2s. If the BSC is not equipped with a redundant BSP and the BSPGPROC2 were to fail, the BSC would be inoperable.

Pooled GPROC2s for LCF and OMF redundancy

The BSS supports pooled GPROC2s for LCF and OMF redundancy. By equippingadditional GPROC2s for spares, if an LCF or the OMF GPROC2 were to fail, the systemsoftware will automatically activate a spare GPROC2 from the GPROC2 pool to replacethe failed GPROC2.

GSR6 (Horizon II) Transcoding

30 Sep 2003


68P02900W21-M

GMR-015�43

Transcoding

Introduction

Transcoding reduces the number of cellular subscriber voice/data trunks required by afactor of four. If transcoding takes place at the switch using a RXCDR, the number oflinks between the RXCDR and the BSC is reduced to approximately one quarter of thenumber 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 (GDP); this limitation is due to power constraints. An RXU shelfcan support up to 16 GDP/XCDRs or GDPs and typically provides a better solution of thetranscoding function for larger commercial systems. Refer to the section Remotetranscoder planning overview in Chapter 6.

GDP/XCDR planning considerations

The following factors should be considered when planning the GDP/XCDR complement:

S The GDP board consists of 15 DSPs, each of which is capable of supporting thetranscoding function for two circuits of full rate (FR) and enhanced full rate (EFR)and phase 2 data service. So a GDP can process 30 voice channels on E1 or 24voice channels on T1, will support full rate, enhanced full rate speech,uplink/downlink volume control and is capable of terminating one E1 or T1 linkfrom the MSC.

S A XCDR can process 30 voice channels on E1, can support full rate speech(enhanced full rate is not supported), uplink/downlink volume control, and iscapable of terminating one E1 link from the MSC.

S The master MSI slot(s) should always be populated to enable communication withOMC-R. The master MSI slot may contain a GDP/XCDR, if the OML goes throughthe MSC.

S The A-interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1links; whereas an XCDR can only terminate E1 links (refer to T1 conversionsbelow).

NOTE The fitting of a GDP in place of an XCDR does not affect theplanning calculations for E1 links. For T1 links an MSI-2 is notrequired.

GSR6 (Horizon II)Transcoding

30 Sep 20035�44


GMR-0168P02900W21-M

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 inone of two ways. In either case, the conversion may be part of an existing networkelement or a standalone network element which would appear as an RXCDR.

Without KSW switching

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

With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1circuits may be done. This uses the ability of the KSW to switch between groups usingnailed connections. Although more efficient in XCDR utilization, this method may causeadditional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2sneeded for T1 to E1 conversion is:

m = T + E

2

Where: m is: the number of MSI-2s required for T1 to E1 conversion.

T the number of T1 circuits required.

E the number of E1 circuits required.


30 Sep 2003


68P02900W21-M

GMR-015�45

Planning actions for transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the numberof E1 or T1 links for the A-interface. This text should be read in conjunction with the BSSplanning diagram, Figure 5-1.

Using E1 links

The minimum number of E1 links required for the A-interface is the greater of the twocalculations that follow (fractional values should be rounded up to the next integer value).

N = T30

N = C + X + T

31

Where: N is: the minimum number of E1 links required.

C the number of MTL links (C7 signalling links) to theMSC.

X the number of OML links (X.25 control links to theOMC-R) through the MSC.

T the number of trunks between the MSC and the BSC.

Each GDP/XCDR card can terminate one E1 link.

Using T1 links

The minimum number of T1 links required for the A-interface is the greater of the twocalculations that follow (fractional values should be rounded up to the next integer value).

N = T23

N = C + X + T

24

Where: N is: the minimum number of T1 links required.

C the number of MTL links (C7 signalling links) to theMSC.

X the number of OML links (X.25 control links to theOMC-R) through the MSC.

T the number of trunks between the MSC and the BSC.

Each GDP card can terminate one T1 link (see T1 conversion above for XCDR).

GSR6 (Horizon II)Multiple serial interface (MSI, MSI-2)

30 Sep 20035�46


GMR-0168P02900W21-M

Multiple serial interface (MSI, MSI-2)

Introduction

A multiple serial interface provides the interface for the links between a BSSC cabinetand other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI caninterface only E1 links, an MSI-2 can interface both E1 and T1 links, but notsimultaneously.


The following factors should be considered when planning the transcoder complement:

S Each MSI can interface two E1 links.

S Each MSI-2 can interface two T1 links.

NOTE Although the MSI-2 is configurable to support either E1 or T1 oneach of its two ports, it is not recommended for E1 systems.

S Each E1 link provides 31 usable 64 kbit/s channels.

S Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2.

S Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1links connected to the site.

S The master MSI slot(s) should always be populated to enable communication withOMC-R.

If the OML links go directly to the MSC, the master slot should be filled with aXCDR/GDP, otherwise the slot should be filled with an MSI/MSI-2 whichterminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 linksdo not need to go directly to the OMC-R, they may go to another network elementfor concentration.

GSR6 (Horizon II) Multiple serial interface (MSI, MSI-2)

30 Sep 2003


68P02900W21-M

GMR-015�47

MSI/MSI-2 planning actions

If local transcoding is used then the NBSC�RXCDR element in the following equations canbe ignored, otherwise refer to Chapter 6 RXCDR planning steps and rules for thedetermination of the NBSC�RXCDR element.

With E1 links

Determine the number of MSIs required.

NMSI ��SNBSC�BTSi � NBSC�RXCDR � NGDS�TRAU � NGSL�E1

�2

With T1 links

Determine the number of MSI-2s required.

NMSI ��SNBSC�BTSi � NBSC�RXCDR � NGDS�TRAU � NGSL�E1

�2

� m

Where: NBSC�BTSi is: the number of links between the BSC and the�ith� BTS.

NBSC�RXCDR the number of links from the BSC to theRXCDRs (remote transcoding only).

NGDS�TRAU the number of links from the BSC to the PCUcarrying GDS TRAU traffic (refer to Chapter 7).

NGSL�E1 the number of links between the BSC and thePCU carrying GSL signalling links.

m the number of MSI/MSI-2s used for T1 to E1conversion.

GSR6 (Horizon II)Kiloport switch (KSW)

30 Sep 20035�48


GMR-0168P02900W21-M

Kiloport switch (KSW)

Introduction

The kiloport switch (KSW) card provides digital switching for the TDM highway of theBSC.


The following factors should be considered when planning the KSW complement:

S A minimum of one KSW is required for each BSC site.

S The KSW capacity of 1024 x 64 kbit/s or 4096 x 16 kbit/s ports can be expandedby adding up to three additional KSWs, giving a total switching capacity of 4096 x64 kbit/s or 16384 x 16 kbit/s ports, of which 8 x 64 kbit/s timeslots are reserved bythe system for test purposes and are not available for use.

S Using 12 MSIs per KSW may reduce the number of shelves required at a cost ofadditional KSWs. For example, a BSC with 28 MSIs could be housed in threeshelves with three KSW modules, or four shelves with two KSW modules.

S All configurations are dependent upon timeslot usage, as described below.

S For redundancy, duplicate all KSWs.

S Verify that each KSW uses no more than 1016 ports. The devices in a BSC thatrequire TDM timeslots 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 is: the number of timeslots required.

G the number of GPROC2s.

n 16 or 32 (depending on the value of the gproc_slotsdatabase parameter).

R the number of GDP/XCDRs.

M the number of MSI/MSI-2s (do not count MSI-2s whichare doing on-board E1 to T1 conversion, whendetermining TDM bandwidth).

NOTE Any BSC site which contains a DRIM has 352 timeslots allocatedto DRIMs, irrespective of the number of DRIMs equipped.

GSR6 (Horizon II) Kiloport switch (KSW)

30 Sep 2003


68P02900W21-M

GMR-015�49

KSW planning actions

Calculate the minimum number of KSWs required per BSC:

N = (G * n) + (R * 16) + (M * 64)

(1016)

Where: N is: the number of KSWs required.


n 16 or 32 (depending on the value of the gproc_slotsdatabase parameter).


M the number of MSI/MSI-2s (do not count MSI-2s whichare doing on-board E1 to T1 conversion).

Each KSW has to serve the boards in its shelf plus the boards of any extension shelfconnected to its shelf by its TDM highway of 1016 available timeslots.

In case of multiple expansion shelves, the TDM highways of each shelf do not merge intoa common unique TDM highway across all shelves. That is, a KSW in one cage cannotserve boards in other expansion shelves.

For example, in the case of a BSC consisting of two shelves each having 32 unusedtimeslots per KSW free, an additional MSI board CANNOT be added even if a MSI slot isfree at each shelf. (But one GPROC2 per shelf can be added if one GPROC slot pershelf is free.)

GSR6 (Horizon II)BSU shelves

30 Sep 20035�50


GMR-0168P02900W21-M

BSU shelves

Introduction

The number of BSU shelves is normally a function of the number of GPROC2s,MSI/MSI-2s and XCDR/GDPs required.


The following factors should be considered when planning the number of BSU shelves:

S Each BSU shelf supports up to eight GPROC2s. If the number of these exceedsthe number of slots available, an additional BSU shelf is required.

S Each expansion shelf is allocated to a single KSW and extension shelves aredifferentiated by the presence of the KSW. Extension shelves are those which donot contain a primary KSW. Shelves containing a KSW are called expansionshelves.

S An extension shelf extends the TDM highway. It is constrained to the samenumber of (aggregate) timeslots as the shelf containing the KSW.

S An expansion shelf adds an additional TDM highway. It increases the number oftimeslots to that of the additional KSW.

S The following capacities depend on timeslot usage. See Kiloport switch (KSW)for information on how to determine timeslot usage.

� A BSU shelf can support up to 12 MSI/MSI-2 boards.

� A BSU shelf can support up to six XCDR/GDP boards (reducing the numberof MSI/MSI-2 boards appropriately).

GSR6 (Horizon II) BSU shelves

30 Sep 2003


68P02900W21-M

GMR-015�51

BSU shelf planning actions

Determine the number of BSU shelves required.

The number of BSU shelves required is the greater of the three following calculations(fractional values should be rounded up to the next integer value):

Bs = G8

Bs = M + R

12

Bs = R6

Verify that the timeslot usage requirements are met for each shelf, as given in thefollowing equation:

(G * n) � (R * 16) � (M * 64) �� 1016

If they are not, the configuration of MSI, GPROC and GDP boards may be adjusted, oran additional cage or cages may be required.

Where: Bs is: the minimum number of BSU shelves required.


M the number of MSI/MSI-2s.

R the number of XCDR/GDPs.

n 16 or 32 (depending on the value of thegproc_slots database parameter).

NOTE The number of shelves may be larger if an attempt to reduce thenumber of KSWs is made.The maximum number of shelves (cages) at a site = 16.The maximum number of cabinets at a site = 16.Horizon and M-Cell sites do not require a cage to be equipped,only a cabinet.

NOTE Although the BSC can support a maximum of 56 MSI/MSI-2sand each of up to 4 BSU shelves can support 12 MSIs, it is NOTthe case that adding one extension shelf will provide theadditional capacity for the extra 8 MSIs.Each extension shelf only supports 2 MSIs, due to a restrictionon the KSW. Therefore, to achieve the BSC limit for MSIs willrequire an additional 4 BSU extension shelves (4 x 2 = 8 MSIs).

GSR6 (Horizon II)Kiloport switch extender (KSWX)

30 Sep 20035�52


GMR-0168P02900W21-M

Kiloport switch extender (KSWX)

Introduction

The KSWX extends the TDM highway of a BSU to other BSUs and supplies clock signalsto all shelves in multi-shelf configurations. The KSWX is required whenever a networkelement expands beyond a single shelf.


The following factors should be considered when planning the KSWX complement:

S KSWXs are not required in a single shelf configuration (that is, when expansion orextension is not required).

S For redundancy, duplicate all KSWX boards (requires redundant KSW).

S KSWXs are used in three modes:

� KSWXE (Expansion) are required to interconnect the KSWs for sites withmultiple KSWs.

� KSWXR (Remote) are required in shelves with KSWs to drive the TDMhighway in shelves that do not have KSWs.

� KSWXL (Local) are used in shelves that have KSWs to drive the clock bus inthat shelf and in shelves that do not have KSWs to drive both the local TDMhighway and the clock bus in that shelf.

S Five of the redundant KSWX slots are also CLKX slots.

S The maximum number of KSWX slots per shelf is 18, nine per KSW.

KSWX planning actions

The number of KSWXs required is the sum of the KSWXE, KSWXL and KSWXR:

NKX � NKXE � NKXR � NKXL

NKXE � K * (K � 1)

NKXR � SE

NKXL � K � SE

Where: NKX is: the number of KSWXs required.

NKXE the number of KSWXE.

NKXR the number of KSWXR.

NKXL the number of KSWXL.

K the number of non-redundant KSWs.

SE the number of extension shelves.

GSR6 (Horizon II) Kiloport switch extender (KSWX)

30 Sep 2003


68P02900W21-M

GMR-015�53

For example:

Table 5-13 KSWX (non-redundant)

Extensionh l

KSW (non redundant)shelves

1 2 3 4

0 0 4 9 16

1 3 6 11 18

2 5 8 13 20

3 7 10 15 22

4 9 12 17 24

Table 5-14 KSWX (redundant)

Extensionshelves

KSW (redundant)shelves

1 2 3 4

0 0 8 18 32

1 6 12 22 36

2 10 16 26 40

3 14 20 30 44

4 18 24 34 48

GSR6 (Horizon II)Generic clock (GCLK)

30 Sep 20035�54


GMR-0168P02900W21-M

Generic clock (GCLK)

Introduction

The GCLK generates all the timing reference signals required by a BSU.


The following factors should be considered when planning the GCLK complement:

S One GCLK is required at each BSC.

S The maximum number of GCLK slots per shelf is two.

S For redundancy, add a second GCLK at each BSC in the same shelf as the firstGCLK.

GCLK planning actions

Determine the number of GCLKs required.

GCLKs = 1 + 1 redundant.

GSR6 (Horizon II) Clock extender (CLKX)

30 Sep 2003


68P02900W21-M

GMR-015�55

Clock extender (CLKX)

Introduction

A CLKX board provides expansion of GCLK timing to more than one BSU.


The following factors should be considered when planning the CLKX complement:

S One CLKX is required in the first BSU shelf which contains the GCLK whenexpansion beyond the shelf occurs.

S Each CLKX can supply the GCLK signals to six shelves.

S There are three CLKX slots for each GCLK, allowing each GCLK to support up to18 shelves (LAN extension only allows fourteen shelves in a single networkelement).

S The maximum number of CLKX slots per shelf is six.

NOTE The CLKX uses six of the redundant KSWX slots.

S With a CLKX, a KSWXL is required to distribute the clocks in the master and eachof the expansion/extension cages.

S For redundancy, duplicate each CLKX (requires a redundant GCLK).

CLKX planning actions

Determine the number of CLKXs required.

NCLKX � ROUND UP �E6� * (1 � RF)

Where: NCLKX is: the number of CLKX required.


E the number of expansion/extension shelves.

RF Redundancy factor(1 if redundancy is required (recommended),0 for no redundancy).

GSR6 (Horizon II)Local area network extender (LANX)

30 Sep 20035�56


GMR-0168P02900W21-M

Local area network extender (LANX)

Introduction

The LANX provides a LAN interconnection for communications between all GPROC2s ata site.


The following factors should be considered when planning the LANX complement:

S One LANX is supplied in each shelf.

S For full redundancy add one LANX for each shelf.

S The LANX can support a maximum network size of 14 shelves.

LANX planning actions

Determine the number of LANXs required.

NLANX � NBSU * (1 � RF)

Where: NLANX is: the number of LANX required.

NBSU the number of BSU shelves.

RF Redundancy factor(1 if redundancy is required (recommended),0 for no redundancy).

BSU � 14

GSR6 (Horizon II) Parallel interface extender (PIX)

30 Sep 2003


68P02900W21-M

GMR-015�57

Parallel interface extender (PIX)

Introduction

The PIX board provides eight inputs and four outputs for site alarms.


The following factors should be considered when planning the PIX complement:

S The maximum number of PIX board slots per shelf is two.

S The maximum number of PIX board slots per site is eight.

PIX planning actions

Choose the number of PIXs required.

PIX � 2 * number of BSUs.

or

PIX � 8.

GSR6 (Horizon II)Line interface boards (BIB, T43)

30 Sep 20035�58


GMR-0168P02900W21-M

Line interface boards (BIB, T43)

Introduction

The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provideimpedance matching for E1 and T1 links.



S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T11.544 Mbit/s) 3 V (peak pulse) line use a BIB.

S To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peakpulse) line use a T43 Board (T43).

S Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf.

S Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet.

� A maximum of 24 E1/T1 links can be connected to a BSU shelf.

� A BSSC2 cabinet with two BSU shelves can interface 48 E1/T1 links.

BIB/T43 planning actions


S Determine the number and type of link (E1 or T1) to be driven.

S Determine the number of BIBs or T43s required.

Minimum number of BIBs or T43s = Number of MSIs

3 =

Number of E1/T1 links6

GSR6 (Horizon II) Digital shelf power supply

30 Sep 2003


68P02900W21-M

GMR-015�59

Digital shelf power supply

Introduction

A BSSC cabinet can be supplied to operate from either a +27 V dc or �48 V/�60 V dcpower source.


The following factors should be considered when planning the PSU complement:

S Two DPSMs are required for each shelf in the BSSC.

S Two IPSMs are required for each shelf in the BSSC2 (�48 V/�60 V dc).

S Two EPSMs are required for each shelf in the BSSC2 (+27 V dc).

S For redundancy, add one DPSM, IPSM, or EPSM for each shelf.

Power supply planning actions

Determine the number of PSUs required.

PSUs = 2 * Number of BSUs + RF * Number of BSUs

Where: RF is: Redundancy factor(1 if redundancy is required (recommended),0 for no redundancy).

GSR6 (Horizon II)Battery backup board (BBBX)

30 Sep 20035�60


GMR-0168P02900W21-M

Battery backup board (BBBX)

Introduction

The BBBX provides a backup supply of +5 V dc at 8 A from an external battery tomaintain power to the GPROC2 DRAM and the optical circuitry on the LANX in the eventof a power supply failure.


The following factors should be considered when planning the BBBX complement:

S One BBBX is required per shelf, if the battery backup option is to be used.

BBBX planning actions

Determine the number of BBBXs required.

BBBX = number of BSUs for battery backup (recommended).

BBBX = 0 if no battery backup required.

GSR6 (Horizon II) Non volatile memory (NVM) board

30 Sep 2003


68P02900W21-M

GMR-015�61

Non volatile memory (NVM) board

Introduction

The optional non volatile memory board provides the BSC with an improved recoveryfacility following a total power loss. With the NVM board installed, data is retrieved fromthe NVM board rather than from the OMC-R during recovery from a total power loss.

Planning Considerations

The following factors should be considered when planning the NVM complement:

S Only one NVM board can be installed at the BSC.

S The NVM board uses slot 26 in the BSU shelf 0 (master) of the BSC, which is anunused slot.

S The appropriate software required to support the NVM board must be loaded atthe OMC-R and downloaded to the BSC.

NVM planning actions

The NVM board is optional.

GSR6 (Horizon II)Verify the number of BSU shelves and BSSC2 cabinets

30 Sep 20035�62


GMR-0168P02900W21-M

Verify the number of BSU shelves and BSSC2 cabinets

Verification

After planning is complete, verify that:

S The number of shelves is greater than one eighth the number of GPROC2modules.

S Each non-redundant KSW has its own shelf.

S Each extension shelf supports extension of a single KSW.

S The number of KSWXs, LANXs, CLKXs, and GPROC2s is correct.

S The number of MSI/MSI-2s and GDP/XCDRs

� 12 * number of shelves.

S The number of GDP/XCDRs


S The number of BTS sites

� 100

S The number of BTS cells

� 250

S RSLs.

� 250

S Carriers.

� 384

S LCFs

� 25

S Erlangs.

� 3000

If necessary, add extra BSU shelves. Each BSSC2 cabinet supports two BSU shelves.

30 Sep 2003


68P02900W21-M

GMR-016�1

Chapter 6

RXCDR planning steps and rules

GSR6 (Horizon II)

30 Sep 20036�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-016�3

Chapter overview

Introduction

This chapter provides the planning steps and rules for the RXCDR. This chaptercontains:

S RXCDR planning overview.

S RXCDR planning:

� Planning rules for RXCDR to BSC links.

� Planning rules for RXCDR to MSC links.

� Transcoding at the RXCDR.

S Planning rules for RXCDR hardware.

GSR6 (Horizon II)Remote transcoder planning overview

30 Sep 20036�4


GMR-0168P02900W21-M

Remote transcoder planning overview

Introduction

To plan the equipage of an RXCDR, certain information must be known. The major itemsinclude:

S The BSC traffic requirements.

S The number of trunks (including redundancy) from the MSC.

S Each RXCDR may support multiple BSCs.

S The sum of the MSI/MSI-2s and the XCDR/GDPs for each BSC define the numberof slots required at the RXCDR.



GSR6 (Horizon II) Remote transcoder planning overview

30 Sep 2003


68P02900W21-M

GMR-016�5


Planning a RXCDR involves the following steps, which are all described in detail in thischapter:

1. Plan the number of links between the XCDR and BSC site(s), refer to the sectionRXCDR to BSC links.

2. Plan the number of E1 or T1 links between the RXCDR and MSC site(s), refer tothe section RXCDR to MSC links.

3. Plan the number of GPROCs required, refer to the section Generic processor(GPROC, GPROC2).

4. Plan the number of XCDR/GDPs required, refer to the section Transcoding.

5. Plan the number of MSI/MSI-2s required, refer to the section Multiple serialinterface (MSI, MSI-2).

6. Plan the number of KSWs and timeslots required, refer to the section Kiloportswitch (KSW).

7. Plan the number of RXU shelves, refer to the section RXU shelves.

8. Plan the number of KSWXs required, refer to the section Kiloport switchextender (KSWX).

9. Plan the number of GCLKs required, refer to the section Generic clock (GCLK).

10. Plan the number of CLKXs required, refer to the section Clock extender (CLKX).

11. Plan the number of LANXs required, refer to the section LAN extender (LANX).

12. Plan the number of PIXs required, refer to the section Parallel interface extender(PIX).

13. Plan the number of BIB or T43s required, refer to the section Line interfaces(BIB, T43).

14. Plan the power requirements, refer to the section Digital shelf power supply.

15. Plan the number of BBBXs required, refer to the section Battery backup board(BBBX).

16. Decide whether an NVM board is required, refer to the section Non volatilememory (NVM) board.

17. Verify the planning process, refer to the section Verify the number of RXUshelves and BSSC cabinets.

GSR6 (Horizon II)RXCDR to BSC connectivity

30 Sep 20036�6


GMR-0168P02900W21-M

RXCDR to BSC connectivity

Introduction

It is possible to have multiple RXCDRs connected to a single BSC, and vice-versa. Thisis especially useful for two primary reasons:

1. In certain configurations the RXCDR call (CIC) capacity may be greater than thatof a BSC.

2. A failure of a RXCDR, or communication line will not result in a complete failure ofthe BSC to handle calls.

Capacity

The level of connectivity between RXCDRs and BSCs may be constrained by thenumber of XBLs that can be supported. There is a limit of 18 at each BSC and RXCDR(see Determining the number of XBLs required in Chapter 5).

The level of connectivity is determined by the operator, Excess RXCDR capacity shouldnot be wasted, nor should larger BSCs be connected only to one RXCDR. One guidelineis to have each BSC connect to four RXCDRs. System size, capacity, and cost are majorinfluences on the chosen configuration.

GSR6 (Horizon II) RXCDR to BSC links

30 Sep 2003


68P02900W21-M

GMR-016�7

RXCDR to BSC links

IntroductionThe number of E1 or T1 links between the RXCDR and the BSCs is the number requiredto support the A-interface from the RXCDR to the BSC.

The number of links between the RXCDR and the BSC is reduced to approximately onequarter of the number of links between the RXCDR and the MSC when 16 kbit/sbackhaul is used.

This text should be read in conjunction with the BSS planning diagram, Figure 6-1.


MSC

A INTERFACE (TERRESTRIAL LINKS)�C7 SIGNALLING LINKS�X.25 CONTROL LINK *�REQUIRED TRUNKS

WITH SUBMULTIPLEXING TRANSCODING AT MSC1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK *1 x 64 KBIT/S CIRCUIT/ XBL1 x 64 KBIT/S CIRCUIT/4 TRUNKS

WITHOUT SUBMULTIPLEXING TRANSCODING AT BSC1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK*1 x 64 KBIT/S CIRCUIT/TRUNK

1 x 64 KBIT/S OF 1 x 16 KBIT/S RTF CIRCUIT/LAPDSIGNALLING LINK2 x 64 KBIT/S CIRCUITS/RTF1 x 16 KBIT/S GSL CIRCUITS/TIMESLOT


AIR INTERFACE�TCHs, PDCHs AND SIGNALLING TSs�TYPICALLY 2% BLOCKING FOR CS TRAFFIC

TRANSCODING MUST BE LOCATED AT THEBSC, OR BETWEEN THE BSC AND MSC.

THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINEDFROM THE # OF TRUNKS REQUIRED TO CARRY THESUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS,TYPICALLY USING 1% BLOCKING) FROM ALL BTSs

� PLUS �THE # OF GDS TRAU LINKS (DETERMINED FROM THENUMBER OF GPRS TIMESLOTS UNDER A BSC)




� PLUS �THE # OF GSL LINKS

THE # OF TCHs REQUIRED (USING TYPICALLY 2%BLOCKING) TO CARRY SUBSCRIBER TRAFFIC.THE TCHs PLUS THE REQUIRED SIGNALLING TSsDIVIDED BY EIGHT DETERMINES THE CARRIERSREQUIRED (ON A BTS/SECTOR BASIS)

TRANSCODER

BSC

BTS



BSC TO PCUGDS�TRAUCIRCUITS

THE # OF GSLsTHE # OF GBLs

PCUGBL

GDS INTERFACE **� GDS TRAU CHANNELS� GSL LINKS

1 x 16 KBIT/S CIRCUIT /GPRS TIMESLOT1 x 64 KBIT/S GSL LINK


OR MSC SITE** GDS�TRAU AND GSL ARE

CARRIED ON SEPARATE LINKS

1 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTFOR CS1 AND CS22 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTSFOR CS3 AND CS41 x 64 KBIT/S GSL LINK

GSR6 (Horizon II)RXCDR to BSC links

30 Sep 20036�8


GMR-0168P02900W21-M

E1 interconnect planning actions

Determine the number of E1 links required.

NBSC�RXCDR �C + X + B64 + (T + B16) / 4

31

Where: NBSC-RXCDR is: the minimum number of E1 links required.

C the number of C7 signalling links to the MSC.

X the number of OML links (X.25 control links tothe OMC-R) through the RXCDR.

B64 the number of 64 kbit/s XBL links.

T the number of trunks between the MSC and theBSC (see Figure 6-1).


NOTE Each E1 link carries up to 120 trunks with a signalling link or 124trunks without a signalling link. Redundant E1 links carrying extratrunks may be added.

T1 interconnect planning actions

Determine the number of T1 links required.

NBSC�RXCDR �C + X + B64 + (T + B16) / 4

24

Where: NBSC-RXCDR is: the minimum number of T1 links required.

C the number of C7 signalling links to the MSC.

X the number of OML links (X.25 control links tothe OMC-R) through the RXCDR.




NOTE Each T1 link carries up to 92 trunks with a signalling link or 96trunks without a signalling link. Redundant T1 links carrying extratrunks may be added.

GSR6 (Horizon II) RXCDR to MSC links

30 Sep 2003


68P02900W21-M

GMR-016�9

RXCDR to MSC links

Introduction

The number of E1 or T1 links between the RXCDR and the MSC is the number requiredto support the A-interface from the RXCDR to the MSC.

E1 interconnect planning actions

Determine the number of E1 links required.

The minimum number of E1 links required for the A-interface is the greater of the twocalculations that follow (fractional values should be rounded up to the next integer value).

NRXCDR�MSC � T30

NRXCDR�MSC �C + X + T

31

Where: NRXCDR-MSC is: the minimum number of E1 links required.

C the number of MTL links (C7 signalling links) tothe MSC.

X the number of OML links (X.25 control links tothe OMC-R) through the MSC.


T1 interconnect planning actions

Determine the number of T1 links required.

NRXCDR�MSC �C + X + T

24

Where: NRXCDR-MSC is: the minimum number of T1 links required.





30 Sep 20036�10


GMR-0168P02900W21-M

Generic processor (GPROC2)

Introduction

Generic processor (GPROC) boards are used throughout the Motorola BSS as a controlprocessor.


The following factors should be considered when planning the generic processor boardsat the RXCDR:

S Each shelf requires at least one GPROC board, plus one for redundancy.

S A maximum of two processor boards per shelf are supported.

NOTE From GSR6 onwards, GPROC2s are mandatory at the masterand standby BSP slots in cage 0.

GPROC planning actions

A RXCDR should have:

S One GPROC per shelf.

S One GPROC for redundancy.

S One optional CSFP.

The factors described in the planning considerations section should be taken intoaccount in this planning.


30 Sep 2003


68P02900W21-M

GMR-016�11

Transcoding

Introduction

Transcoders (XCDR/GDPs) provide the interface for the E1 (or converted T1) linksbetween the MSC and the BSC. The XCDR/GDP performs the transcoding/rateadaptation function which compresses the information on the trunks by a factor of four(16 kbit/s).

Figure 6-2 shows sub-multiplexing and speech transcoding at the RXCDR.

S Each trunk requires a quarter (1/4th) of a 64 kbit/s circuit between the RXCDR andBSC.

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

Figure 6-2 Sub-multiplexing and speech transcoding at the RXCDR

RXCDR

ONE RFCARRIERK

SW

MSI/MSI2 HIISC

MSI/MSI2

KSW

XCDR/GDP

MSC

8 x 22.8 kbit/sTIMESLOTSTHE CTU2 ENCODES/DECODES

13 kbit/s TO/FROM 22.8 kbit/s FOR 8TIMESLOTS, AND SUBMULTIPLEXES 4

(13 kbit/s MAPPED ON 16 kbit/s)TIMESLOTS ONTO 1 x 64 kbit/s CIRCUIT,

OR THE OTHER WAY AROUND.

64 kbit/s 4 TCHs

THE KSW SUBRATESWITCHES 16 kbit/s

TIMESLOTS.THE XCDR/GDP TRANSCODES 64 kbit/sA�LAW PCM TO/ FROM 13 kbit/sMAPPED ONTO 16 kbit/s, ANDSUBMULTIPLEXES 4 TRUNKS

TO/FROM 1 x 64 kbit/s CIRCUIT.

64 kbit/sA�LAWTRUNKS

MSI/MSI2

CTU2

NIU

4 TRUNKS PER64 kbit/s CIRCUIT

BSC Horizon II macro BTS

NOTE In Figure 6-2, the CTU2 is shown operating in single densitymode (one carrier), although it can also operate in double densitymode (two carriers).


30 Sep 20036�12


GMR-0168P02900W21-M

XCDR/GDP planning considerations

The following factors should be considered when planning the XCDR/GDP complement:

S A XCDR/GDP can process 30 voice channels (XCDR/GDP-E1) or 24 voicechannels (GDP-T1), will support enhanced full rate speech, uplink/downlink volumecontrol and is capable of terminating one E1 or T1 link from the MSC.

S XCDRs and GDPs can co-exist in a cage.

S The master MSI slot(s) should always be populated to enable communication withOMC-R. The master MSI slot may contain a XCDR/GDP, if the OML goes throughthe MSC.

S The A-interface must terminate on the XCDR/GDP. A GDP can terminate T1 or E1links; whereas an XCDR can only terminate E1 links (refer to T1 conversionsbelow).

S Slot 24 (XCDR 0) in the RXU cage 0 (master) will be lost if an optional NVM boardis required.

T1 conversion


When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done inone of two ways. In either case the conversion may be part of an existing networkelement or a standalone network element which would appear as a RXCDR.


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

With KSW switching

For better utilization of the GDP/XCDRs a mapping of five T1 circuits onto four E1circuits may be done. This uses the ability of the KSW to switch between groups usingnailed connections. Although more efficient in XCDR utilization, this method may causeadditional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2sneeded for T1 to E1 conversion is:

m = T + E

2





30 Sep 2003


68P02900W21-M

GMR-016�13

Planning actions for transcoding at the RXCDR

The number of transcoders at the RXCDR is proportional to the number of E1 or T1 linksbetween the RXCDR and the MSC.

Using E1 links

Each XCDR/GDP can terminate one E1 link.

Using T1 links

Each GDP card can terminate one T1 link. See T1 conversion (described previously) forXCDR.


30 Sep 20036�14


GMR-0168P02900W21-M


Introduction

A multiple serial interface provides the interface for the links between a RXCDR site andother network entities, RXCDR to OMC-R and RXCDR to BSC. A MSI can interface onlyE1 links, an MSI-2 can interface both E1 and T1 links.




S Each MSI-2 can interface two E1/T1 links.





S When one remote transcoder site is supporting multiple BSCs, each BSC requiresits own E1 interface(s) as follows:

� The number of MSI/MSI-2s should be equal to half the number of RXCDR toBSC 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 T1link (half an MSI/MSI-2) is required for the X.25 links to the OMC-R.

� At least one MSI/MSI-2 is required for every eight XCDR/GDP 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 forapproximately every ten GDPs.

� Additional E1 or T1 links may be required to concentrate X.25 links fromother network entities.

� Each BSC may use one to four 64 kbit/s or 16 kbit/s channels for XBL faultmanagement communications. Refer to Service Manual: BSC/RXCDR(68P02901W38) for more details.


If the OML links go directly to the MSC, the master slot should be filled with aXCDR/GDP, otherwise the slot should be filled with an MSI/MSI-2 whichterminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 linksdo not need to go directly to the OMC-R, they may go to another network elementfor concentration.


30 Sep 2003


68P02900W21-M

GMR-016�15

MSI planning actions

With E1 links

Determine the number of MSI or MSI-2s required.

NMSI �NBSC�RXCDR

2

Where: NMSI is: the number of MSIs required.

NBSC-RXCDR the number of E1 links required(as N calculated in RXCDR to BSC links in thischapter).

With T1 links

If MSI-2s are used, T1 to E1 conversion is not needed. Therefore the number of MSI-2srequired is:


2



If MSIs are used, conversion becomes necessary. Therefore the number of MSIsrequired is:


2� m



m the number of MSI-2s used for T1 to E1conversion.


30 Sep 20036�16


GMR-0168P02900W21-M


Introduction

The KSW provides digital switching for the TDM highway of the RXU.



S A minimum of one KSW is required for each RXU site.

S The KSW capacity of 1024 x 64 kbit/s or 4096 x 16 kbit/s ports can be expandedby adding up to three additional KSWs, giving a total switching capacity of 4096 x64 kbit/s or 16384 x 16 kbit/s ports, of which 8 x 64 kbit/s timeslots are reserved bythe system for test purposes and are not available for use.


S Verify that each KSW uses no more than 1016 ports. The devices in a RXCDRthat require TDM timeslots are:






N = (G * n) + (R * 16) + (M * 64)



n 16 or 32 (depending on the value of thegproc_slots database parameter).


M the number of MSI/MSI-2s (do not count MSI-2swhich are doing on-board E1 to T1 conversion,when determining TDM bandwidth).


30 Sep 2003


68P02900W21-M

GMR-016�17



S Determine the number of KSWs required.

N = (G * n) + (R * 16) + (M * 64)

(1016)


G the number of GPROC2s (or GPROCs).

n 16 or 32 (depending on the value of theGPROC_slot database parameter).


M the number of MSI/MSI-2s (do not count MSI-2swhich are doing on-board E1 to T1 conversion).

Each KSW has to serve the boards in its shelf plus the boards of any extension shelfconnected to its shelf by its TDM highway of 1016 available timeslots.

In case of multiple expansion shelves, the TDM highways of each shelf do not merge intoa common unique TDM highway across all shelves. That is, a KSW in one cage cannotserve boards in other expansion shelves.

For example, in the case of a BSC consisting of two shelves each having 32 unusedtimeslots per KSW free, an additional MSI board CANNOT be added even if a MSI slot isfree at each shelf. (But one GPROC2 per shelf can be added if one GPROC slot pershelf is free.)

GSR6 (Horizon II)RXU shelves

30 Sep 20036�18


GMR-0168P02900W21-M

RXU shelves

Introduction

The number of RXU shelves is normally a function of the number of MSI/MSI2s andXCDR/GDPs required.


The following factors should be considered when planning the number of RXU shelves:

S Each expansion shelf is allocated to a single KSW and shelves are differentiatedby the presence of the KSW. Extension shelves are those which do not contain aprimary KSW. Shelves containing a KSW are called expansion shelves.

S An extension shelf extends the TDM highway. It is constrained to the samenumber of (aggregate) timeslots as the shelf containing the KSW.

S An expansion shelf adds an additional TDM highway. It increases the number oftimeslots to that of the additional KSW.

S The number of devices that can be served by a KSW is governed by the TDMtimeslot allocation required for each device. This is discussed previously in theKSW Planning considerations. The number and type of shelves can then bedetermined from the devices required.

For example:

Two shelves, each equipped with three MSI/MSI-2s and 16 XCDR/GDPs, canbe served by a single KSW.

If each shelf has five MSI/MSI-2s with 14 XCDR/GDPs, the KSW can serveonly one shelf, and two KSWs will be required.

S The existing RXU shelf has connectivity for up to five MSI/MSI-2s (2 x E1connections). The remaining 14 slots have one E1 connection. All slots may beused for XCDR/GDPs and MSI/MSI-2s.

S An NVM board cannot be installed if all the XCDR slots in the RXU cage 0(master) are required.

RXU shelf planning actions

Determine the number of RXU shelves required (fractional values should be rounded upto the next integer):

RX � max�M5

, (R � NNVM)�16�Where: Rx is: the minimum number of RXU shelves required.



NNVM the number of optional NVM boards (0 or 1).


30 Sep 2003


68P02900W21-M

GMR-016�19


Introduction

The KSWX extends the TDM highway of a RXU to other RXUs and supplies clocksignals to all shelves in multi-shelf configurations. The KSWX is required whenever anetwork element grows beyond a single shelf.



S KSWXs are not required in a single shelf configuration (that is, when expansion orextension is not required).





� KSWXL (Local) are used in shelves that have KSWs to drive the clock bus inthat shelf and in shelves that do not have KSWs to drive both the local TDMhighway and the clock bus in that shelf.


S The maximum number of KSWX slots per shelf is 18, nine per KSW.


The number of KSWXs required is the sum of the KSWXE, KSWXL, and KSWXR.


NKXE � K * (K � 1)

NKXR � SE

NKXL � K � SE

Where: NKX is: the number of KSWX required.





SE the number of extension shelves.


30 Sep 20036�20


GMR-0168P02900W21-M

For example:


Extensionh l


1 2 3 4

0 0 4 9 16

1 3 6 11 18

2 5 8 13 20

3 7 10 15 22

4 9 12 17 24


Extensionshelves


1 2 3 4

0 0 8 18 32

1 6 12 22 36

2 10 16 26 40

3 14 20 30 44

4 18 24 34 48

GSR6 (Horizon II) Generic clock (GCLK)

30 Sep 2003


68P02900W21-M

GMR-016�21


Introduction

The GCLK generates all the timing reference signals required by a RXU.



S One GCLK is required at each RXCDR.

S A second GCLK is optionally requested for redundancy.

S Both GCLKs must reside in the same shelf of the RXCDR.



GCLKs = 1 + 1 redundant

GSR6 (Horizon II)Clock extender (CLKX)

30 Sep 20036�22


GMR-0168P02900W21-M


Introduction

A CLKX board provides expansion of GCLK timing to more than one RXU.



S One CLKX is required in the first RXU shelf, which contains the GCLK, whenexpansion beyond the shelf occurs.


S There are three CLKX slots for each GCLK, allowing each GCLK to support up to18 shelves (LAN extension only allows fourteen shelves in a single networkelement).






Determine the number of CLKXs required:

NCLKX � ROUND UP �E6� * (1 � RF)



E the number of shelves.

RF Redundancy factor(1 if redundancy required (recommended),0 for no redundancy).

GSR6 (Horizon II) LAN extender (LANX)

30 Sep 2003


68P02900W21-M

GMR-016�23

LAN extender (LANX)

Introduction

The LANX provides a LAN interconnection for communications between all GPROC2s ata site.








NLANX � NRXU * (1 � RF)


NRXU the number of RXU shelves.

RF Redundancy factor(1 if redundancy required (recommended).0 for no redundancy).

RXU � 14

GSR6 (Horizon II)Parallel interface extender (PIX)

30 Sep 20036�24


GMR-0168P02900W21-M


Introduction

The PIX provides eight inputs and four outputs for site alarms.






Determine the number of PIXs required.

PIX � 2 * number of RXUs

or

PIX � 8

GSR6 (Horizon II) Line interfaces (BIB, T43)

30 Sep 2003


68P02900W21-M

GMR-016�25

Line interfaces (BIB, T43)

Introduction




S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544Mbit/s) 3 V (peak pulse) line use a BIB.

S To match a single-ended 75 ohm 2.37 V (peak pulse) line use a T43 Board (T43).


S All E1/T1 links must be terminated, including the links which are fully contained inthe cabinet, for example, between RXU and BSU or links used for T1 to E1conversion.

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




S Calculate the number of Ei/T1s to be terminated for each shelf.

S Determine the number of BIBs or T43s required per shelf.

Minimum number of BIBs or T43s required per shelf = Number of E1/T1 links

6

S Sum up across all shelves for the total.

GSR6 (Horizon II)Digital shelf power supply

30 Sep 20036�26


GMR-0168P02900W21-M


Introduction

A BSSC cabinet can be supplied to operate from either a +27 V dc or �48/�60 V dcpower source.


The following factors should be considered when planning the PSM complement:

S Two DPSMs are required for each shelf in the BSSC/RXCDR.

S Two IPSMs are required for each shelf in the BSSC2/RXCDR (�48/�60 V dc).

S Two EPSMs are required for each shelf in the BSSC2/RXCDR (+27 V dc).

S For redundancy, add one DPSM, IPSM or EPSM for each shelf.


Determine the number of PSMs required.

PSMs = 2 * Number of RXUs + RF * Number of RXUs

Where: RF is: Redundancy factor(1 if redundancy required (recommended),0 for no redundancy).

GSR6 (Horizon II) Battery backup board (BBBX)

30 Sep 2003


68P02900W21-M

GMR-016�27


Introduction

The BBBX provides a backup supply of +5 V dc at 8 A from an external battery tomaintain power to the GPROC DRAM and the optical circuitry on the LANX in the eventof a mains power failure.



S One BBBX is required per shelf.



BBBX = number of RXUs for battery backup (recommended).


GSR6 (Horizon II)Non volatile memory (NVM) board

30 Sep 20036�28


GMR-0168P02900W21-M

Non volatile memory (NVM) board

Introduction

The non volatile memory board provides the Remote Transcoder with an improvedrecovery facility following a total power loss. With the NVM board installed, data isretrieved from the NVM board rather than from the OMC-R during recovery from a totalpower loss.

Planning Considerations

The following factors should be considered when planning the NVM complement:

S Only one NVM board can be installed at the RXCDR.

S The NVM board uses slot 24 on the RXU shelf 0 (master) of the RXCDR. In thecase that a XCDR board is already occupying that slot, the XCDR board andassociated interface cabling can be moved from slot 24 to the spare slot. If thereare no spare slots, then the XCDR board occupying slot 24 must be removed toaccommodate the NVM board, with a subsequent reduction in capacity of theRXCDR.

S The appropriate software required to support the NVM board must be loaded atthe OMC-R and downloaded to the RXCDR.

NVM planning actions

The NVM board is optional.

GSR6 (Horizon II) Verify the number of RXU shelves and BSSC cabinets

30 Sep 2003


68P02900W21-M

GMR-016�29

Verify the number of RXU shelves and BSSC cabinets

Verification




S The number of KSWXs, LANXs, CLKXs, and GPROC2s is correct.

If necessary, add extra RXU shelves. Each BSSC cabinet supports two RXU shelves.

GSR6 (Horizon II)Verify the number of RXU shelves and BSSC cabinets

30 Sep 20036�30


GMR-0168P02900W21-M

30 Sep 2003


68P02900W21-M

GMR-017�1

Chapter 7

PCU upgrade for the BSS

GSR6 (Horizon II)

30 Sep 20037�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-017�3

Chapter overview

Introduction

This chapter provides the following information for the PCU upgrade to the BSS tosupport GPRS:

S BSS planning for GPRS.

S BSS upgrade to support GPRS.

S PCU hardware information.

S PCU equipment redundancy and provisioning goals.

S E1 link provisioning for GPRS.

S PCU to SGSN traffic and signalling planning.

S BSS � PCU planning example for GPRS.

GSR6 (Horizon II)BSS planning for GPRS

30 Sep 20037�4


GMR-0168P02900W21-M

BSS planning for GPRS

Introduction to BSS planning for GPRS

The BSS planning process for GPRS may involve adding additional BSS equipment andsoftware to the BSS, in addition to the PCU hardware and software. The extent of theadditional BSS equipment depends on the amount of traffic expected to be carried overthe GPRS part of the network and the coding schemes used on the air interface.

The section GPRS network traffic estimation and key concepts in Chapter 3 isintended to provide the network planner with the rules to determine the number of GPRStimeslots that are to be provisioned at the BTS, subsequently provisioned in PCUhardware, and provisioned with communication links.

The BSS planning process described here focuses on the provisioning of the PCUhardware within the BSS. A BSS planning example is provided at the end of this chapter(see BSS planning example. Its purpose is to unite the information presented in theentire document from a planning perspective.

GSR6 (Horizon II) BSS planning for GPRS

30 Sep 2003


68P02900W21-M

GMR-017�5

PCU to SGSN interface planning

The PCU to SGSN interface is referred to as the Gb Interface. The Gb interfaceconnects the BSS PCU to the GPRS SGSN. Motorola supports three Gb interfaceoptions (options A, B, and C), as shown in Figure 7-1.

Figure 7-1 Gb interface alternatives

MSC

RXCDR

OMC-R

PCU

BSC

BTS1 BTSn

Gb OPTION A

Gb OPTION B

Gb OPTION C

A INTERFACE

FOR OPTION Aand B

The RXCDR can be used as an E1 switching interface between the PCU and SGSN, asshown in option A.

Alternatively, the BSC can be used as an E1 switching interface, as shown in option B.

Option C is the case where there is no BSS E1 switching element between the PCU andSGSN.

The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. ThePCU is connected directly to the BSC E1 interfaces and the BSC is configured to providethe E1 master clock. If the PCU is connected to a GSN that does not have a masterclock source, some interface equipment that does have a master clock source (such as aDACs) should be used. The Motorola BSC and RXCDR equipment can be used in placeof a DACs for this purpose.

When an RXCDR or BSC is used as a E1 switching element, as shown in option A andoption B, respectively, additional equipment provisioning of these network elements maybe required in order to support the PCU E1 interfaces, in accordance with theprovisioning rules for adding E1 interfaces to the RXCDR and BSC network elements.


30 Sep 20037�6


GMR-0168P02900W21-M

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 functionalunit severities. Therefore, the impact is to the following PCU devices: DPROC and PCUSystem Processor (PSP).

BSC-BTS dynamic allocation


The dynamic allocation feature specifies how the BSC configures and shares theterrestrial backing between the GPRS data traffic and the Circuit-Switched (CS) traffic.The terrestrial backing, between the BTS and BSC, must have enough capacity to carrythe radio timeslots assigned to both GPRS and circuit switched. If there is not enoughcapacity, because there are not enough physical channels, the BSC allocates thebacking to CS first. The remaining capacity is assigned to GPRS (reserved GPRStimeslots first, and then to switchable GPRS timeslots).

Any terrestrial backing resources not used by circuit-switched calls are allocated forswitchable use. However, circuit-switched calls can take resources away from theswitchable pool when traffic demands require more terrestrial capacity. Terrestrialresources available in the switchable pool are available for GPRS traffic use.

The BSC may reassign GPRS switchable or reserved backing to CS if backing isrequired for emergency circuit-switched calls. In this case, the backing is reassigned sothat the remaining GPRS radio timeslots within a carrier are contiguous.

The CS3/CS4 feature, which requires 32 kbit/s bandwidth on backhaul, has beendesigned to work mutually exclusively with this feature.

Circuit error rate monitor

No circuit error rate monitor support is provided by the GPRS feature.

Circuit-switched (voice or data) calls

The addition of GPRS to a GSM network impacts the traffic and signalling handlingnetwork capability for GSM voice and circuit data traffic. Additional loading on the BSSelements, due to the GPRS traffic, may require additional BSS equipment and interfacecircuits to be added.

There are three classes of mobile devices, which permit non-simultaneous attachment tothe circuit-switched and packet data channels. This means that the BSS does not needto be provisioned to simultaneously handle the call processing and signalling for bothcircuit-switched traffic and GPRS packet data services on a per subscriber basis. TheBSS treats class A mobiles like class B mobiles. Therefore, the BSS part of the networksupports the simultaneous attachment, activation, and monitoring of circuit-switched andpacket data services. Simultaneous GPRS and circuit-switched traffic is not supported.The mobile user can make and/or receive calls on either of the two services sequentially,but not simultaneously. The selection of the appropriate service is performedautomatically.

Concentric cells

GPRS timeslots are available in the outer zone carriers.

GSR6 (Horizon II) BSS planning for GPRS

30 Sep 2003


68P02900W21-M

GMR-017�7

Congestion relief


Congestion relief considers switchable GPRS timeslots as idle TCHs.

Cell resource manager dynamic reconfiguration


The Cell Resource Manager (CRM) dynamic reconfiguration feature can use theswitchable GPRS timeslots, but it cannot reconfigure the reserved GPRS timeslots underany circumstances.

Directed retry


The BSC uses directed retry to relieve cell congestion by redistributing traffic acrosscells. For the GPRS traffic part of the BSS, the BSC treats switchable GPRS timeslotslike idle TCHs.

Emergency call pre-emption


The BSS will be able to configure any GPRS timeslot to carry out emergency calls.Should an emergency call be made within a cell with a GPRS carrier, the BSS will selectthe air timeslot that will carry it from the following:

S Idle TCH.

S Switchable GPRS timeslot (from lowest to highest).

If the emergency call pre-emption feature is enabled, the BSS will select the air timeslotthat will carry the emergency call, from the following list in the following order:

A. Idle TCH.

B. Switchable GPRS timeslot (from lowest to highest).

C. In-use TCH.

D. Reserved GPRS timeslot (from lowest to highest).

Emergency TCH channels will never be pre-empted.

Extended range cells


The extended range cell feature extends the range of a GSM 900 MHz mobile to35 kilometres. This range extension is not supported for GPRS.

Frequency hopping and redefinition

The GSM radio uses slow frequency hopping to improve data reliability and to increasethe number of active users. The GPRS timeslots assigned to the uplink and downlinkchannels must have the same frequency parameters. GPRS may have a differenttimeslot activity factor to voice, and thereby causes the cell C/I performance to changefrom a GSM-only system.

The frequency redefinition feature extends the GSM 4.08 capabilities to GPRS.


30 Sep 20037�8


GMR-0168P02900W21-M

Global reset


The global reset procedure initializes the BSS and MSC in the event of a failure. A globalreset does not affect any resources assigned to GPRS.

Integrated Horizon HDSL interface

No additional BSS or GPRS network planning is required other than to plan for the GDSlink.

The PCU does not support a high bit-rate subscriber line (HDSL) between the PCU andthe BSC. However, the BSC can use an MSI board (with HDSL capabilities) to terminatea GDS link to the PCU if an E1 is used for the connection.

Multiband handovers


The BSC treats switchable GPRS timeslots like idle TCHs in the case of multibandhandovers.

Over the air flow control for circuit-switched mobiles


The BSC treats switchable GPRS timeslots like idle TCHs in the case of over the air flowcontrol for the circuit-switched mobiles feature.


The BSC may use a switchable GPRS timeslot for a Cell Broadcast CHannel (CBCH) ora Slow Dedicated Command CHannel (SDCCH).

The RTF path fault feature converts TCHs to SDCCH when an RTF path fault occurs.The RTF path feature may also convert switchable GPRS timeslots that are TCH barred,to SDCCH. The converted GPRS timeslots are returned to GPRS after the original RTFpath fault is cleared.

SMS cell broadcast

The CBCH can reside on a switchable GPRS timeslot. Therefore, switchable GPRStimeslots may be reconfigured as SDCCHs. However, GPRS reserved timeslots cannotbe reconfigured as SDCCHs.

SD placement prioritization

A GPRS carrier cannot be configured so that the sum of the number of SDCCHs allowedand the number of GPRS timeslots, exceed the capacity of the carrier.

GSR6 (Horizon II) BSS upgrade to support GPRS

30 Sep 2003


68P02900W21-M

GMR-017�9

BSS upgrade to support GPRS

BSS upgrade provisioning rules

Table 7-1 identifies the BSS network elements that may require upgrading to supportGPRS. Consult the relevant planning information for the chassis-level planning rulescovering the BSC, BTS and RXCDR.

The PCU provisioning rules are described later in this chapter.

Table 7-1 BSS upgrade in support of GPRS

Equipment Additionalelement

BSS upgrade

BSC Chassis(optional)

Add KSWs, LCF GPROC2s, MSIs per BSC as neededin support of the Gb, GDS TRAU, GDS LAPD (GSL),RSL, BSC-BTS traffic carrying E1 links.

BTS (BTS4,BTS5, BTS6,ExCell,TopCell)

ReplaceDRCU withDRCU2/3

Provision with DRCU2/3 or later version transceivers.Follow BTS provisioning rules for the number oftransceivers required at the BTS and other supportingboards, including DHP processor boards, asnecessary. The same carrier dimensioning rules can beused for a GPRS carrier as for a circuit-switchedcarrier. (The TSW must be replaced with the KSWwhen GPRS support of the BSC-BTS dynamicallocation feature is enabled.)

OMC-R(see Note)

Softwareupgrade forGPRSsupport

One per 64 BSS network elements, with any mix ofcircuit or packet (GPRS) channels supported; softwarein support of the PCU.

RXCDR Chassis(optional)

Add KSWs, GPROC2s, MSIs per RXCDR as neededto support the Gb interface shown as option A inFigure 7-1.

NOTE OMC-R planning steps and rules are beyond the scope of thismanual.

GSR6 (Horizon II)BSS upgrade to support GPRS

30 Sep 20037�10


GMR-0168P02900W21-M

Maximum BSS configuration

Table 7-2, Table 7-3 and Table 7-4 provide the maximum BSS network parameter valuesin support of GPRS per BSS network element.

Table 7-2 Maximum BSS network parameter values in support of GPRS (part A)

NetworkElement

Network Parameter Maximum Value

BSS (BTS) GPRS carriers per cell 12

BSS (BTS) Timeslots per carrier 8

BSS (BTS) TBF per cell UL 120

BSS (BTS) TBF per cell DL 120

BSS (BTS) Users per timeslot in eachdirection

4

BSS (BTS) Timeslots per active user DL 4

BSS (BTS) Timeslots per active user UL 1

BSS (BTS) Switchable GPRS timeslotsper carrier

8

BSS (BTS) Reserved GPRS timeslots percarrier

8

BSS (BTS) Switchable GPRS timeslotsper cell

30

BSS (BTS) Reserved GPRS timeslots percell

30

BSS (PCU) Air interface timeslotsprocessed at any instance intime (with redundancy)

240, see Figure 7-3.

BSS (PCU) Total air interface timeslots(with redundancy) *


BSS (PCU) Air interface timeslotsprocessed at any instance intime


BSS (PCU) Total air interface timeslots * 1080, see Figure 7-4.

BSS (PCU) Max. TBF per PCU � UL 1080

BSS (PCU) Max. TBF per PCU � DL 1080

NOTE * From release GSR6 onwards, all 1080 timeslots under a PCUcan support traffic, unlike in previous releases where only 270timeslots could be used to originate traffic at any instance intime. All additional calls attempts were blocked. This is nowpossible because of rapid multiplexing of four sets of 30timeslots by the PRP. The data throughput, however, is stilllimited to 30 timeslots per PRP and 270 per PCU innon-redundant configuration.

GSR6 (Horizon II) BSS upgrade to support GPRS

30 Sep 2003


68P02900W21-M

GMR-017�11

Table 7-3 Maximum BSS network parameter values in support of GPRS (part B)

NetworkElement


PCU(PRP DPROC)

Air interface timeslotsprocessing per PRP

30 at any instance in time;120 total timeslots.

PCU(PICP DPROC)

GDS TRAU E1 interfacehandled per PICP

6, if every TRAU-type GDS E1handles 124×16 kbit/s timeslots.Actually, the PICP number is tied

with total timeslots number a PICPprocessor can support. In other

words, one PICP board is requiredper 744×16 kbit/s timeslots.

6, if every TRAU-type GDS E1handles 62x32 kbit/s timeslots. Thatis, 372×32 kbit/s timeslots per PICP.

PCU(PICP DPROC)

PCU-SGSN (Gb) interface 1 Gb E1 to carry frame relaychannellized or non channellizedGPRS traffic per 150 active CS

timeslots deployed over the BSC toPCU interface. The Gb E1 carries

both data and signalling trafficbetween the PCU and SGSN.

PCU Max. PSP MPROCs 2 (for redundancy)

1 (no redundancy)

PCU Max. PICP DPROCs 3

PCU Max. PRP DPROCs 9

PCU Number of cells supported 250

PCU Number of BTS sitessupported

100

GSL E1 links Max. physical E1s betweenBSC & PCU (one primary E1and one redundant)

2

LAPD-typeGDS (GSL)links

Max. per E1 link (correspondsto a quantity of six 64 kbit/sLAPD channels)

6

TRAU-typeGDS links(E1s)

Max. per PCU 18

GSR6 (Horizon II)BSS upgrade to support GPRS

30 Sep 20037�12


GMR-0168P02900W21-M

Table 7-4 Maximum BSS network parameter values in support of GPRS (part C)

NetworkElement


GBL links (E1s) Max. per PCU 4

Gb PVCs Max. on one bearer Link 318

T43 boards Max. per PCU 4

Cableharnesses

To connect 4 x T43 sites 2

Gb frame relayframe octet size

Max. 1600 bytes

NOTE The total number of air interface timeslots supported by the PCUis affected by the fact that all of the timeslots of a cell areallocated to the same PRP board. Allocation of a portion of theGPRS timeslots for a cell to one PRP and another portion of theGPRS timeslots of the same cell to a different PRP is notsupported. This fragmentation of the cells across PRP boardsmay result in not all GPRS timeslots for a cell being assigned toa PRP and may even result in not all cells being assigned to aPRP. When planning the BSS, if the number of GPRS timeslotsin the BSS does not exceed max_GPRS TSg, all GPRStimeslots of all cells will be assigned to a PRP.max_GPRS TSg = nPRP * 120 � (max_GPRS TS_cell � 1)Where:max_GPRS TSg = maximum number of GPRS timeslots perPCU guaranteed to be assigned to a PRP.nPRP = number of PRP boards in the PCU.max_GPRS_TS_cell = number of GPRS timeslots in the cell inthe BSS with the most GPRS timeslots.Note that there are special cases where 120 timeslots areguaranteed to be assigned per PRP board. These special casesare where all the cells in the BSS with GPRS timeslots have thesame number of GPRS timeslots and the number of GPRStimeslots is 1, 2, 3, 4, 5, 6, 7 or 8 timeslots.

E1 cable requirements for a fully configured PCU

The PCU cabinet contains an interconnection panel which contains up to 4 x T43 boards.To support a maximum of 24 E1s for a fully configured PCU, 4 x T43 boards need to bepopulated.

Before GSR6, a cable harness is staged with the PCU containing 18 E1 RJ45 to RJ45cables.

Under GSR6, a second cable harness needs to be caged to hold an extra 6 E1 RJ45 toRJ45 cables.

GSR6 (Horizon II) PCU hardware layout

30 Sep 2003


68P02900W21-M

GMR-017�13

PCU hardware layoutThere is one PCU per BSS. Figure 7-2 shows the PCU shelf layout.

Figure 7-2 PCU shelf layout

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DPROC

DEFAULT LAPDLINKS TO BSC

MPROC A

MPROC B

1 2 3 4 5 6 11 12 13 14 15 167 98 10

DEFAULT LAPDLINK TO BSC

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DPROC

TM

DEFAULT LAPDLINK TO BSC

MPROC

A

TM

16 15 14 13 12 11 6 5 4 3 2 110 89 7

DEFAULT LAPDLINKS TO BSC

MPROC

B

TM

HSC

A

HSC

B

NOTE Any two of the three available default LAPD link slots may beused.

GSR6 (Horizon II)PCU shelf (cPCI)

30 Sep 20037�14


GMR-0168P02900W21-M

PCU shelf (cPCI)

Introduction

The PCU cabinet can hold up to three PCU (cPCI) shelves. Each PCU is connected toonly one BSC, so one PCU cabinet can serve up to three BSCs. There are no PCU toPCU interconnects within the cabinet.

Each cabinet is pre-wired with a panel in the rear of the cabinet for the desired E1termination type, balanced 120 ohm, or unbalanced 75 ohm terminations with 1500 voltlightning protection per E1.


The following factors should be considered when planning the cPCI complement:

S The maximum number of timeslots that can be processed at any instance in timeper PCU is 240 in the fully redundant configuration (see Figure 7-2).

S The maximum number of total timeslots that can be provisioned per PCU is 960 inthe fully redundant configuration (see Figure 7-2).

S 3 fan/power supply units per cPCI shelf provide N+1 hot-swap redundancy. Aminimum of 2 units required.

S 1 air filter per fan/power supply unit is required. (Maximum of 3 per PCU.)

S Each PCU cPCI shelf requires two MPROC boards for redundancy. MPROCredundancy is not required for normal PCU operation, but is necessary for thePCU to achieve high availability.

S Each MPROC board requires one bridge board and one transition module for aredundant MPROC configuration, or if the Web MMI feature is enabled.

S 1 alarm board per PCU is required.

S 1 main circuit breaker panel per PCU is required.

S There are four bays on the right side of the shelf that may be used for auxiliaryequipment such as tape drives, CD-ROM drives, and hard disks. The PCU isconfigured without any auxiliary equipment and this area of the shelf is coveredwith blank panels.

NOTE Additional T43 modules and interconnect cables are required forthe PCU cage to support 18 GDS TRAU links.

GSR6 (Horizon II) MPROC board

30 Sep 2003


68P02900W21-M

GMR-017�15

MPROC board

Introduction

The PCU planning process determines the type and number of MPROC boards topopulate in the PCU. The PCU provisioning requirements take the MPROC redundancysolution into consideration.

Planning considerations (PSP use)

The MPROC board is used for PSP purposes. The PSP is the PCU system processor,which is a master GPROC system processor board. The PSP controls compact PCI bussynchronization and arbitration. It also performs centralized configuration and faulthandling for the PCU site.

If MPROC redundancy is required, each PCU cPCI shelf requires two MPROC cards(boards). The MPROC redundancy flag specified during the equipping of the PCU shouldbe enabled. The MPROC cards should be inserted in slot 7 and 9 (see Figure 7-2). AMPROC (PSP 0) card is inserted into slot 7 and the other MPROC (PSP 1) is insertedinto slot 9. MPROC (PSP 0) in slot 7 is paired with a hot swap controller/bridge module inslot 10 and MPROC (PSP 1) in slot 9 is paired with a hot swap controller/bridge module(HSC) in slot 8.

If no redundancy is required, only one MPROC card should be inserted in either slot 7 or9 of the PCU cage. The MPROC redundancy flag specified during the equipping of thePCU should be disabled. The MPROC (PSP 0) in slot 7 is paired with a hot swapcontroller/bridge module in slot 10 or MPROC (PSP 1) in slot 9 is paired with a hot swapcontroller/bridge module (HSC) in slot 8. If both MPROCs are present but redundancy isnot desired or the equip flag is disabled, the MPROC in slot 7 is the primary MPROC andis responsible for powering off the MPROC in slot 9. In this case, the MPROC in slot 9 isconsidered transparent.

For a non redundant solution, no inter-MPROC connection (RS232 or Ethernet) isrequired.

The MPROC card is a Motorola MCP750HA microprocessor board with a TMCP700transition module.

GSR6 (Horizon II)DPROC board

30 Sep 20037�16


GMR-0168P02900W21-M

DPROC board

Introduction

The PCU planning process determines the type and number of DPROC boards topopulate in the PCU. The PCU provisioning requirements use the number of GPRStimeslots as the planning rule input. The estimation process for determining the numberof GPRS timeslots is provided in GPRS network traffic estimation and key conceptsin Chapter 3.

Planning considerations (PICP or PRP use)

DPROC board slots can be used for either PICP or PRP purposes. Each DPROC has anE1 transition module mounted in the rear of the shelf directly behind it.

A DPROC may be configured as a PICP with zero, one, or two E1 PMC modules, andwith PICP software. The DPROC may be configured as a PRP with either one or two E1PMC modules, and with PRP software.

The PICP provisioned boards should be populated from left to right. For systemavailability reasons, PICPs should be evenly distributed between the two backplaneswithin the PCU shelf. The left and right backplanes are connected together through thebridge board located behind the MPROC processor board. Therefore, the first PICPwould occupy board slot 1, PICP 2 would occupy board slot 11, PICP 3 would be in slot2, and PICP 4 in slot 12.

PRP provisioning should also be performed in a similar fashion, alternating provisionedboards between the left and right backplanes.

PICP board

The following factors should be considered when planning the PICP board complement:

S The PCU can support up to three PICP boards.

S A PICP board has two PMC modules.

S The PICP boards can terminate the following links: GDS TRAU-type GDS links,GDS LAPD-Type GDS links, and Gb links.

S One PICP board is required per six TRAU-type GDS E1s if every TRAU-type GDSE1 handles 124 x 16 kbit/s timeslots. Actually, the PICP number is tied with thetotal timeslots number a PICP processor can support. In other words, one PICPboard is required per 744 × 16 kbit/s timeslots or 372 × 32 kbit/s timeslots.

S N+1 board redundancy is supported.

GSR6 (Horizon II) DPROC board

30 Sep 2003


68P02900W21-M

GMR-017�17

PRP board

The following factors should be considered when planning the PRP board complement:

S The PCU can support up to 9 PRP boards. When 9 PRP boards are populated,there are only three slots available for PICP boards, thereby limiting PICPredundancy, Gb link redundancy, LAPD-Type GDS redundancy, and TRAU-typeGDS link redundancy.

S PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module, butcannot terminate GDS LAPD E1s or Gb E1 links.

S Up to 120 timeslots can be terminated on one PRP.

S The timeslots are managed by load balancing software which limits the number oftimeslots processed at any instance to 30 for each PRP. Therefore, one E1carrying 124 active timeslots can supply up to five PRPs with active timeslots. Thesoftware load balances, in this case, such that four of the PRPs receives 25 activetimeslots and the fifth receives 24.

NOTE The actual distribution of timeslots may be slightly different fromthat shown here depending on cell configurations. That is, alltimeslots for a single cell must terminate on a single PRP, whichcan lead to slight imbalances when multiple timeslots areconfigured per cell.

S A PRP board has up to two PMC modules.

S N+1 board redundancy is supported.

GSR6 (Horizon II)PMC module

30 Sep 20037�18


GMR-0168P02900W21-M

PMC module

Introduction

The number of PMC modules installed depends on the number of PICP and PRPconfigured boards in the PCU.


The following factors should be considered when planning the PMC complement:

S Each PRP board may require one PMC module.

S Each PICP board has two PMC modules.

S TRAU-type GDS, LAPD-type GDS (GSL), Gb E1 links cannot share a PMCmodule.

S Only one TRAU-type GDS per PMC module on a PRP board is allowed. The otherE1 termination on the PMC module cannot be used.

S Each PMC processor in the PCU is capable of processing 124 x 16 kbit/s TRAUchannels or 62 x 32 kbit/s TRAU channels.

S Up to two Gb E1 links per PMC module are allowed.

S Up to two LAPD-type GDS E1 links per PMC module are allowed.

GSR6 (Horizon II) Transition module

30 Sep 2003


68P02900W21-M

GMR-017�19

Transition module

Introduction

The number of transition modules installed depends on the number of PICP and PRPconfigured boards in the PCU.


The following factors should be considered when planning the number of transitionmodules required:

S One transition module is required per PRP board.

S One transition module is required per PICP board.

GSR6 (Horizon II)PCU equipment redundancy and provisioning goals

30 Sep 20037�20


GMR-0168P02900W21-M

PCU equipment redundancy and provisioning goals

Support for N + 1 equipment redundancy

The following N+1 equipment redundancy is supported:

S N+1 PICP and PRP board redundancy.

S 2 PS/FAN units non-redundant, 3 PS/FAN unit redundant.

S 1 MPROC/bridge board pair non-redundant, 2 MPROC/bridge board pairsredundant.

S E1 redundancy requires the provisioning of the redundant hardware with active E1links. The E1 redundancy is available for GSL, GDS, and GBL links. Loadbalancing is performed across the GDS, GSL, and GBL E1 links so that if a linkshould fail, the existing load is redistributed to the other links.

PCU redundancy planning

For redundant PCU operation, the PCU should be planned such that there are N+1boards provisioned as shown in Figure 7-3. That is, only eight PRP boards and two PICPboards are required to handle the expected maximum GPRS traffic load. The ninth PRPboard and third PICP board offer the N+1 hardware redundancy. The third PICP boardprovides redundancy for the software processes that run on the first two PICP boards.For a fully configured PCU with nine GDS TRAU E1s, at least two PICP boards arerequired in order to provide enough processing capability.

The GDS TRAU E1 link redundancy is obtained with the N+1 PRP board. The GSL E1link redundancy is obtained by provisioning a second GSL E1 on the second PICP. OnePICP is required per six GDS TRAU E1 links. The PCU load-balances across the GDSTRAU and LAPD GSL links. If a PRP or PICP board fails, the PCU automaticallyre-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 linkresiliency is obtained by adding an additional two Gb E1s and load balancing across all ofthe Gb E1s.

The PRP and PICP (DPROC) boards are hot swappable, so that when a board failure isdetected, a replacement board may be inserted without disrupting ongoing GPRS trafficon the other boards. The DPROC must be locked before removal, and unlocked followingboard insertion. The PRP and PICP boards have associated transition module boards notshown in the figures below. There is an associated redundant transition module boardwith each redundant PRP and PICP board.

The PCU shelf hardware allows for N+1 MPROC board redundancy. This N+1redundancy capability is subject to MPROC redundancy software availability. TheMPROC board(s) and the MPROC bridge boards are not shown in the figure below, butthe redundant MPROC has an associated redundant bridge board.

The PCU shelf comes with N+1 power supply/fan redundancy. The power supplies arehot swappable. The power supply/fan units are not shown in figures below.

The PCU architecture offers the network planner a considerable degree of provisioningflexibility. Figure 7-3 and Figure 7-4 demonstrate this flexibility where the provisioninggoals may range from full redundancy (Figure 7-3) to maximum coverage (Figure 7-4).

Table 7-5 summarizes the provisioning goals demonstrated with Figure 7-3 andFigure 7-4.

GSR6 (Horizon II) PCU equipment redundancy and provisioning goals

30 Sep 2003


68P02900W21-M

GMR-017�21

Figure 7-3 Goal: maximum throughput and coverage, fully redundant configuration

PMC

PCU HARDWARE

PMC

PMC

PMC

PMC

PMC

PMC

PMC

PMC

PMC

PRP9REDUNDANT

PICP1

PICP2

PICP3REDUNDANT

GDS

GDS

GDS

REDUNDANTGDS

GSL

REDUNDANTGSL

GBL

GBL

REDUNDANTGBL

6 LAPD TS

6 LAPD TS

BSC SGSN

TO

124 @ 16k / GDS TRAUCHANNELS

REDUNDANTGBL

PMCGDS

PMCGDS

PMCGDS

PMC

REDUNDANTGDS

PRP1

120 TS MAX.30 TS MAX.

ACTIVE

PRP2


ACTIVE

PRP8


ACTIVE


ACTIVE

GSR6 (Horizon II)PCU equipment redundancy and provisioning goals

30 Sep 20037�22


GMR-0168P02900W21-M

Figure 7-4 Goal: maximum throughput and coverage, full redundancy not required

PMC

PCU HARDWARE

PMC

PMC

PMC

PMC

PMC

PMC

PRP1

PICP1

PICP2

GDS

GDS

GDS

GSL

REDUNDANTGSL

GBL

GBL

REDUNDANTGBLs

6 LAPD TS

6 LAPD TS

BSC SGSN120 TS MAX.30 TS MAX.

ACTIVE

TO

124 @ 16k / GDS TRAUCHANNELS

PMCGDS

PMCGDS

PMCGDS

PRP2


ACTIVE

PRP9


ACTIVE

Refer to Table 7-5 for a matrix of provisioning goals achieved with this instance of PCUprovisioning.

NOTE Figure 7-4 shows18 GDSs, as required for CS3/CS4. Only 9GDSs are required for CS1/CS2.

GSR6 (Horizon II) PCU equipment redundancy and provisioning goals

30 Sep 2003


68P02900W21-M

GMR-017�23

Table 7-5 PCU provisioning goals

Metric Goal

Maximum coverage withredundant configuration;

see Figure 7-3.

Maximum coverage,redundancy not required;

see Figure 7-4.

Number of timeslotsprocessed at any instance intime

240 270

Total number of provisionedtimeslots at a BSS

960 1080

No. MPROCs 2 1

No. PRPs 8 9

No. PICPs 3 3

No. TRAU-Type GDS E1s 18 18

No. LAPD-Type GDS (GSL)E1s

2 2

No. Gb E1s 4 4

MPROC board redundancy Yes No

PRP board redundancy Yes No

PICP board redundancy Yes No

GDS TRAU E1 redundancy Yes No

GSL E1 redundancy Yes Yes

Gb E1 redundancy Yes Yes

Upgrading the PCU

The PCU may be upgraded for additional capacity, by one PRP board and by one PICPboard at a time. This upgrade must adhere to the PICP to GDS TRAU E1 ratio rule, ofone PICP board per six GDS TRAU E1 links if every TRAU-type GDS E1 handles 124 x16 kbit/s timeslots. Actually, the PICP number is tied with the total timeslots number aPICP processor can support. In other words, one PICP board is required per 744 x16 kbit/s timeslots or 372 x 32 kbit/s timeslots.

GSR6 (Horizon II)E1 link provisioning for GPRS

30 Sep 20037�24


GMR-0168P02900W21-M

E1 link provisioning for GPRS

E1 interface provisioning

The BSC to PCU E1 links should not go through any network elements. The E1 linksshould meet the ITU-T Recommendation G.703. This recommendation includes an E1length specification.

The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. ThePCU is connected directly to the BSC E1 interfaces and the BSC is configured to providethe E1 master clock. If the PCU attaches to a GSN that does not have a master clocksource, 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 RXCDRequipment can be used in place of a DACs for this purpose.


The following factors should be considered when planning the E1 interfaces and links:

GDS TRAU E1

S Up to 124 x 16 kbit/s or 62 x 32 kbit/s active timeslots are permitted on oneTRAU-type GDS E1.

S One TRAU-type GDS E1 can carry up to 124 x 16 kbit/s timeslots.

PCU GDS E1

S There may be up to 18 GDS TRAU-type GDS E1 links per PCU.

GSL LAPD (GSL) E1

S The GSL traffic is load balanced over all GSLs. The first E1 carries up to six LAPDlinks and the second E1 up to another six. For LAPD-type GDS resiliency, two E1sare recommended, regardless of the number of LAPD channels required. Forexample, if only one channel is required to carry the expected signalling load, twoE1s with one LAPD channel per E1 should be used. The MPROC load balancingsoftware distributes the load evenly between the two LAPD channels.

GPROC2 LCF

S The GPROC2 LCF available at the BSC needs to terminate 12 LAPD channels inthe case when a maximum number of LAPD-type links are provisioned at the PCU.The LAPD links are distributed on the LCF automatically, based on the capacityavailable on the LCFs.

PCU Gb E1

S There may be up to four Gb E1s per PCU.

GSR6 (Horizon II) PCU � SGSN: traffic and signalling planning

30 Sep 2003


68P02900W21-M

GMR-017�25

PCU � SGSN: traffic and signalling planning

Introduction

The PCU is connected to the SGSN through the Gb interface as a Data TerminalEquipment (DTE). The physical Gb connection can be established in two ways:

S Point-to-point frame relay connection, with DACs.

S Through the frame relay network.

E1 links are used in both cases.

Gb entities

This section describes the Gb entities and illustrates the mapping of GPRS cells usingeither the point-to-point frame relay connection (PTP FR) or frame relay network.

Table 7-6 provides a description of the Gb entities and identifiers. A further discussion onhow these should be selected is given later in this chapter.

Table 7-6 Gb entities and identifiers

Gb Entity and Identifier Description

E1 The physical link contains 32 timeslots. One is reservedfor E1 signalling. Each timeslot uses a rate of 64 kbit/s.

Frame relay bearer channel(FR BC)

The bearer channel allows the frame relay protocol tomap its resources to the E1 layer.

Permanent virtual circuit(PVC)

A frame relay virtual circuit. This allows the packetswitched FR network to act as a circuit-switchednetwork by guaranteeing an information rate and timedelay for a specific PVC.

Data link connectionidentifier (DLCI)

A unique number assigned to a PVC end point in aframe relay network.

Network service entity (NSE) An instance of the NS layer. Typically, one NSE is usedfor each PCU being served by a SGSN. The NSE hassignificance across the network, and is therefore thesame at the SGSN and PCU.

Network service entityidentifier (NSEI)

Uniquely identifies a NSE.

Network service virtualcircuit (NSVC)

A logical circuit that connects the NSE peers betweenthe SGSN and PCU. The NSVC has significance acrossthe network. Therefore, it is configured identically at theSGSN and PCU.

Network service virtualcircuit identifier (NSVCI)

Uniquely identifies a NSVC. There is a one-to-onemapping between the NSVCI and DLCI.

BSSGP virtual circuit (BVC) A logical circuit that connects the BSSGP peersbetween the BSS and SGSN. This has significanceacross the Gb interface, but is only configured in thePCU. The PCU contains one point-to-point BVC per anactively serving cell.

BSSGP virtual circuitidentifier (BVCI)

Uniquely identifies a BVC.

GSR6 (Horizon II)PCU � SGSN: traffic and signalling planning

30 Sep 20037�26


GMR-0168P02900W21-M

General planning guidelines

These are the general planning guidelines:

S There can be more than one BVC per NSE/PCU/BSS.

S There is one point-to-point BVCI per cell, statically configured at the PCU anddynamically configured at the SGSN.

S There are multiple NSVCs serving one NSE.

S There is a one-to-one mapping between NSVCIs and DLCIs.

S Multiple DLCIs can share the same bearer channel, and therefore the sametimeslot grouping. A bearer channel can be mapped between one and 31 DS0s,depending on the throughput needed for that particular link.

S The DLCI has local significance only, while the NSVCI has significance across thenetwork.

S One E1 can be fractionalized into several bearer channels.

Specific planning guidelines

Motorola deploys one NSEI per PCU, and one PCU per BSS. This might not be the casewith other vendors, who may use more than one PCU per BSS.


30 Sep 2003


68P02900W21-M

GMR-017�27

The Gb signalling overheadThis section describes the Gb protocol signalling overhead. The signalling overhead andthe Gb link capacity limitations must be considered in each Gb link plan.

Gb protocol signalling overheadTable 7-7 shows the corresponding uplink and downlink overhead on the Gb link perGPRS mobility management (GMM) signalling procedure, broken down by layer.

Table 7-7 Signalling overhead per GMM signaling procedure

Procedure Message number and Size

Attach/Detach with ciphering 5 uplink messages, average message size 16 bytes.4 downlink messages, average message size 15 bytes.

Inter/Intra RAU 2 uplink messages, average message size 24 bytes.1 downlink message, message size 45 bytes.

PDP activate/deactivate 2 uplink messages, average message size 15 bytes.2 downlink messages, average message size 15 bytes.

Paging 1 downlink message, message size 21 bytes.

Since the Gb link is full duplex, we are concerned only with the maximum of either theuplink (UL) or the downlink (DL). Since most traffic models assume the majority of datatransfer is in the downlink direction, only the downlink control messaging is considered.

Table 7-8 shows the overhead required on all GPRS mobility management/sessionmanagement messages (GMM/SM).

Table 7-8 Overhead on each downlink GMM/SM message

Layer Field Byte Count

LLC Address

Control

CRC

1

2

3

BSSGP PDU type

TLLI

QoS profile

Lifetime

Priority

DRX

Old TLLI

IMSI

Alignment

Bits radio access capability

1

6

5

4

3 (optional)

4 (optional)

6 (optional)

10

5

10

NS Spare

PDU type

BVCI

1

1

2

Frame relay Header 2

Total signalling overhead 66 bytes

Therefore, in the DL direction, the following protocol requirements per signalling messageare applied:

GMM_Signalling_Requirement = Overhead + Message_Contents


30 Sep 20037�28


GMR-0168P02900W21-M

Data overhead

Table 7-9 shows the corresponding UL and DL overhead on the Gb link per PDU datatransfer for the UL and DL.

Table 7-9 PDU data transfer overhead on each downlink GMM/SM message

Layer Field Byte Count

SNDCP Header 4

LLC Address

Control

CRC

1

3 (typical value for thisvariable, max = 36)

3

BSSGP PDU type

TLLI

QoS profile

Lifetime

Priority

DRX

Old TLLI

IMSI

Alignment

Bits radio access capability

1

6

5

4

3

4

6 (optional)

10

5

10

NS Spare

PDU type

BVCI

1

1

2

Frame Relay Header 2

Total Data Overhead 71 bytes


30 Sep 2003


68P02900W21-M

GMR-017�29

Determine the net Gb loadConsider the network equipment, traffic model and protocol overheads to determine thenet load that must be delivered to each PCU served by the SGSN.

Base formulaeUse the following base formulae to determine the load expected on the Gb interface:

�Signalling_Data_Rate (bytes�s) �

(324 * PSAttach�Detach � 111 * RAU � 162 * PDPAct�Deact) *Subscribers_per_PCU

3600� 87 * PGPRS

User_Data_Rate (bytes�s) �

�Subscribers_per_PCU * Data_per_Subscriber * 1000 * (1 � 71PKSIZE

)�3600

Therefore:

Total_Data_Rate (bytes�s) � Signalling_Data_Rate � User_Data_Rate

NOTE When the value of the Signalling_Data_Rate component issubstituted in the above equation, most scenarios will show aninsignificant impact on the Total_Data_Rate. Therefore, theSignalling_Data_Rate can usually be ignored.

Where: Total_Data_Rate is: defined by the equation above, andrepresents the required bandwidth(bps) for GPRS data transmissionover a GBL interface between thePCU and SGSN after all of theprotocol and signalling overhead isaccounted for.

Signalling_Data_Rate the required rate (bytes/s) forGPRS signalling transmission overa GBL interface between the PCUand SGSN after all of the protocol.

User_Data_Rate the required rate (bytes/s) forGPRS user application data over aGBL interface between the PCUand SGSN after all of the protocol.

PSATTACH/DETACH the detach rate per sub/BH.

RAU the periodic, Intra and inter routeingarea update rate per sub/BH.

PDPACT/DEACT the PDP context activation/deactivation rate per sub/busyhour.

PGPRS the GPRS paging rate (persecond).

PKSIZE the average packet size, in bytes.

Subscribers_per_PCU the average number of subscriberssupported on a PCU.

Data_per_Subscriber the data traffic per subscriber in abusy hour (kbytes per busy hour).


30 Sep 20037�30


GMR-0168P02900W21-M

Gb link timeslots

The traffic and signalling is carried over the same E1 on the Gb link (GBL). The numberof required 64 kbit/s Gb link timeslots can be calculated using the equation given below.Each E1 can carry up to 31 timeslots. When fewer than 31 timeslots are needed on anE1, specifying a fractional E1 may be more cost effective.

No_GBL_TS � Total_Data_Rate8000 * UGBL

NPCU�SGSN � No_GBL_TS31

Where: No_GBL_TS is: the number of timeslots to provisionon the GBL E1 between the PCUand SGSN. This value can be usedto specify a fractional E1.

Total_Data_Rate defined by the equation in theprevious section, and representsthe required bandwidth (bps) forGPRS data transmission over aGBL interface between the PCUand SGSN after all of the protocoland signalling overhead isaccounted for.

UGBL the link utilization.

NPCU�SGSN the E1 link between the PCU andSGSN.


30 Sep 2003


68P02900W21-M

GMR-017�31

Frame relay parameter values

The network planner needs to specify the values for the following three frame relayinterface parameters:

S Committed Information Rate (CIR).

S Committed Burst Rate (Bc).

S Burst Excess Rate (Be).

These frame relay parameter values are determined as described in the following textand illustrated in Figure 7-5.

Figure 7-5 Frame relay parameters


30 Sep 20037�32


GMR-0168P02900W21-M

Committed information rate (CIR)

The recommended cumulative CIR value for NSVC should be greater than, or equal to,50% of the cumulative information rate of the active timeslots on the PCU. The MotorolaPCU distributes the use of all the NSVCs by the subscribers evenly in a round-robinmanner. The round-robin algorithm continuously assigns subscribers to the next NSVC ina sequential manner when a subscriber PDP context is established. If an NSVCbecomes unavailable, it is skipped over, and the next available NSVC in the round-robinis used. This is the BSSGP feature that inherently provides load sharing over all availableNSVCs. The load sharing capability over multiple Gb links is provided by the BSSGPhigh level protocol layer, which results in link resiliency.

The recommended cumulative CIR value for all PVCs should be greater than, or equalto, half the cumulative information rate of the active timeslots routed to the NSVC. Thismapping is actually determined as a mean load, evenly distributed over all of theavailable NSVCs as next described.

Over many cells, it is expected that the PCU will handle the traffic throughput equal to thenumber of timeslots planned for the busy hour traffic load.

The recommended frame relay network CIR value is calculated as follows:

CIR_Value � F * Total_Data_Rate * 8Num_NSVC

Where: CIR_Value is: the committed Information rate per NSVC(PVC).

F the CIR provisioning factor, equal to 0.5.

Total_Data_Rate defined in the earlier section Determine thenet Gb load, and represents the requiredbandwidth (bps) for GPRS data transmissionover a GBL interface between the PCU andSGSN after all of the protocol and signallingoverhead is accounted for.

Num_NSVC the number of provisioned NSVCs per PCU.

By using half the number of timeslots in the CIR calculation, the load of all the timeslotsis served by the combination of the CIR and Bc frame relay network rated capacity. Itshould be noted that this strategy makes use of the overload carrying capacity of theframe relay network when more than half of the planned timeslots are in use.

When a cell uses all of its provisioned timeslots as active timeslots (that is, timeslotsbeing processed by the PCU at that instance in time), other cells must use fewer of theirtimeslots being processed in order for the overall PCU Gb interface bandwidth allocationto be within configured frame relay network interface parameter (CIR, Bc, Be) values.The BSS attempts to utilize as many timeslots as are supported in PCU hardware and incommunication links simultaneously.


30 Sep 2003


68P02900W21-M

GMR-017�33

Committed burst rate (Bc)

The Bc is the maximum amount of data (in bits) that the network agrees to transfer,under normal conditions, during a time interval Tc.

The Bc value should be configured such that if one of the provisioned E1 links fails, theremaining E1 links can carry the load of the failed link, by operating in the Bc region. Forexample, with three E1 links provisioned, if any one of the three should fail, the other twoshould have the capacity to carry the load of the failed link on the remaining two links, byoperating in the Bc region.

Burst excess rate (Be)

The Be is the maximum amount of uncommitted data (in bits) in excess of Bc that aframe relay network can attempt to deliver, during a time interval Tc. The network treatsBe data as discard eligible.

GSR6 (Horizon II)BSS � PCU hardware planning example for GPRS

30 Sep 20037�34


GMR-0168P02900W21-M

BSS � PCU hardware planning example for GPRS

Introduction to BSS � PCU hardware planning

This section provides an example of the PCU hardware provisioning process and the linkprovisioning process associated with adding a PCU to the BSC as shown in Figure 7-6.For the provisioning of the BSC hardware, the network planner should follow the relevantplanning rules for adding additional E1 interface hardware in support of the GDS andGSL links.

The provisioning of the SGSN hardware is not covered in this planning guide.

Figure 7-6 PCU equipment and link planning

BSC PCU SGSN

BTS

GDS

GBLGSL

GSM + GPRS E1s

1 to 4 E1s1 or 2 E1s

1 to 18 E1s

GSR6 (Horizon II) BSS � PCU hardware planning example for GPRS

30 Sep 2003


68P02900W21-M

GMR-017�35

BSS � PCU planning example

Use this example to provision a BSS with 10 sites consisting of 20 cells with one GPRScarrier per cell with the following GPRS call model:

Average packet size (bytes) PKSIZE = 270Traffic per sub/BH (kbytes/hr) � uplink ULRATE = 30Traffic per sub/BH (kbytes/hr) � downlink Data_rate_per_sub = 65PS attach/detach rate (per sub/BH) PSATT/DETACH = 0.5PDP context activation/deactivation (per sub/BH) PDPACT/DEACT = 0.5Routeing area update RAU = 1.5GPRS paging rate in pages per second PGPRS = 3GPRS users per cell 250Average sessions per user per hour 5

Step 1: Choose a cell RF plan

Use the 1 x 3 2/6 and 1 x 1 2/18 hopping tables (Table 3-14 and Table 3-15 inChapter 3) to determine what the values to use for CS rate and BLER for thechosen cell RF plan. For this example, use for the 1x3 2/6 hopping RF plan.

Step 2: Determine number of GPRS carrier timeslots

Use the equation below to determine the number of GPRS timeslots that arerequired on a per cell basis. In order to use this equation, the network plannershould have the expected cell load in kbit/s.

Mean_traffic_load (kbit�s) �GPRS_Users * Data_rate_per_sub * 8

3600

� 250 * 65 * 83600

36 kbit�s

No_PDCH_TS � Roundup � Mean_traffic_loadTS_Data_Rate * Mean_load_factor

�No_PDCH_TS � 36

12.68 * 0.5� 6

Therefore, provision 6 timeslots on the cell.


30 Sep 20037�36


GMR-0168P02900W21-M

Step 3: Calculate the number of GDS E1 links

Compute the number of GDS TRAU E1 channels required for the air interfacetimeslots required to carry the traffic. Remember, each CS1/CS2 timeslot requires16K TRAU channel and CS3/CS4 timeslots requires 32K TRAU on GDS TRAUinterface. Also, CS3/CS4 is enabled on a carrier hence all the GPRS timeslots forthat carrier would require 32K TRAU. For this case it can calculated that 2 GDSTRAU E1s are required.

Total GDS E1s �20 Cells * 6 TS�Cell * 32k�TS

31 * 64k� 2 E1s

Each PRP board can process 30 active timeslots at any given time for a total of120 timeslots. Assuming that we need to provide coverage to at least half of thetimeslots at any instance, the number of mean PDCHs = 3 from step 2, thenumber of PRPs required to serve 20 cells is:

(3 active timeslots per cell) * (20 cells per BSC)(30 active timeslots per PRP)

� 2 PRPs

These 2 PRPs have more than enough capacity to handle the additional 3 standbytimeslots per cell. Using the conservative provisioning rule of one GDS TRAU E1per PRP, we would provision 2 GDS TRAU E1s.

Refer to the appropriate section of this chapter for the PCU provisioning rules. Amore aggressive GDS TRAU E1 provisioning approach can be taken where 60active and 64 standby timeslots are provisioned on only one GDS TRAU E1. ThePCU load-balancing software would distribute the load over the two PRP boards.

The advantage of the more aggressive provisioning approach is that one less E1(if CS1 or CS2 is used) would need to be provisioned at the BSC. Thedisadvantage is that if the one GDS TRAU E1 were to fail, 100% of the PCUservice would be lost.

Step 4: Calculate the PCU hardware to support the PCU traffic

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

� Qty 1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy).

� Qty 1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1PCU shelf per 9 PRP boards.

� Qty 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.


30 Sep 2003


68P02900W21-M

GMR-017�37

Step 5: Calculate the number of GBL links

The number of GBL E1 links is directly related to the number of active timeslots,being provisioned between the BSC and the PCU.

Option 1

In this example 60 active timeslots are required. One GBL E1 can carry theequivalent of 150 active timeslots. This figure includes the GBL signalling trafficand the GPRS packet data traffic including protocol overhead. Therefore, thenumber of GBL E1 links required is:

60 active BSC � PCU timeslots150 active timeslots per GBL E1

� 0.4 E1s

This answer would be rounded up to 1 E1 without redundancy unless a fractionalE1 is available for use. If a fractional E1 is available, it is not necessary to roundup to the nearest integer value for the number of E1s to specify.

Option 2

Using the standard traffic model and Gb formulae:

Signalling_Data_Rate �

(324 * PSATTACH�DETACH � 111 * RAU � 162 * PDPACT�DEACT) * GPRS_Users_PCU

3600� 87 * PGPRS

� (324 * 0.5 � 111 * 1.5 � 162 * 0.5) * 250 * 203600

� 87 * 12 � 1612 bytes�s

User_Data_Rate �

(GPRS_Users_PCU * Data_rate_per_sub * 1000)3600

* �1 � 71PKSIZE

�� (250 * 20 * 65 * 1000)

3600* �1 � 71

270� � 114017 bytes�s

No_GBL_TS �

Total_Data_Rate8000 * UGBL

� 1612 � 1140178000 * 0.25

� 57.8

NPCU�SGSN �

No_GBL_TS31

� 57.831

� 1.86

Hence, 2 Gb links need to be provisioned.


30 Sep 20037�38


GMR-0168P02900W21-M

Step 6: Calculate the number of GSL links

Use the following equation to calculate how many 64 kbits/s GSL links arerequired. For this example, the number of users on a PCU is 5000. Evaluating thisequation and the supporting expressions results in one 64 kbit/s GSL link beingrequired, assuming that enhanced one phase is enabled, after rounding up to thenearest integer value (but not including redundancy).

Total_RACH�sec � 5000 * (5 � 1.5 � 0.5 � 0.5)3600

� 10.38 per second

No_GSL_TS � ROUND UP �(6 * 3) � (10.38 * 6) � (10.38 * 1.5)1000 * 0.25

� � 1

NOTE Refer to Determining the number of GSLs required inChapter 5 for further details on the above equation.

Step 7: Recalculate the number of PICP boards required

Now that the number of GDS, GBL, and GSL E1 links have been calculated, makesure that there are a sufficient number of PICP boards to cover the GBL and GSLE1 links, and to satisfy the 1:6 ratio of GDS TRAU E1s to PICP boards. The PCUhardware calculation in step 4 calculated the number of PICP boards based onlyon the ratio of PICP boards to PRP boards. This step takes into account thenumber of E1 links terminated on the PICP boards for the GBL and GSL E1 links.A PICP board can terminate both GBL and GSL links on the board, but not on thesame PMC module. Each PICP has two PMC modules.

In step 5 it was determined that 2 E1 links are required for the GBL. Each PICPcan terminate up to 4 GBL links. Therefore, 2/4 (1/2) of a PICP is required for theGBL E1 links.

In step 6 it was determined that 1 E1 link is required for the GSL (redundant GSLnot provided for). Each PICP can terminate up to 2 E1 GSL links and up to 12 GSL64 kbit/s timeslots distributed over two E1s. Note that there is a limit of 2 GSL E1sper PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link.

Reviewing the GBL and GSL E1 link requirements, we can see that one PICP issufficient to handle the link provisioning requirements.

Step 8: Calculate the increased data traffic load on the E1s betweenthe BSC and BTSs

It is assumed that the GPRS traffic is in addition to the existing circuit-switchedtraffic. In step 2 it was determined that 6 timeslots would be required for the GPRStimeslot traffic on a per cell basis. Therefore, twelve more 16 kbits/s timeslots(CS1/CS2) or 32 kbit/s timeslots (CS3/CS4) 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 toallocate the GPRS carrier timeslots. That is, they are reserved or switchable. IfGSM circuit-switched statistics are available, they could be reviewed to aid in thisdecision. Refer to Dynamic timeslot mode switching in Chapter 3.


30 Sep 2003


68P02900W21-M

GMR-017�39

Step 9: Calculate the increased signalling traffic load (RSL load) onthe E1s between the BSC and BTSs

The BTS combines the additional signalling load for the GPRS data traffic with theexisting circuit-switched traffic load. This results in an additional load on theexisting RSL links between each BTS and the BSC.

The additional load on the RSL for GPRS is based on the evaluation of thefollowing equation and other supporting equations (see Determining the numberof RSLs in Chapter 5). For 6 timeslots per cell, approximately 0.23 RSL channelswould be required.


The network planner should calculate the RSL load for the GSM circuit-switchedpart of the network, and then add the the GSM number of RSLs to the GPRSrequirements in order to determine the total number of RSL links to provision perthe above equation. The GSM RSL calculation should be performed with 64 kbit/sRSL in order to be consistent with the GPRS calculation.

Step 10: Calculate the increased load due to GPRS traffic on thecommon control channel at each BTS cell

Use the following equation:

NPAGCH = (NAGCH + NPCH) 1UCCCH

The BTS combines the additional control channel load for the GPRS data trafficwith the existing circuit-switched traffic load onto the CCCH. The network plannerneeds the expected paging rate and the access grant rate in order to calculate thenumber CCCH blocks needed to support the additional GPRS traffic load. Thiscalculation should be performed using the guidelines given in the Control channelcalculations section of Chapter 3.

Step 11: BSC provisioning impact

The BSC may require additional hardware in order to support the addition of theGPRS network traffic. For BSC provisioning, the planning rules given in Chapter 5should be consulted.

The BSC may require more E1 terminations in support of the additional E1 links tothe PCU and in support of the additional GPRS traffic over the BTS to BSCinterface. In this example, two E1s were added for the GDS links and one E1added for the GSL link.

The BSC LCF GPROC2 processor load is increased by the volume of GPRSsignalling traffic. The BSS planning rule for LCF provisioning in the followingequation should be used.

GL3_GPRS �

NGPRSGGPRS_PF*TGPRS

� (0.006 � 0.02 * PGPRS) * (BRA_GPRS) �CGRPS

35

2.5

Substituting the other values into the equation, the result is 1.45 LCF GPROC2.

The network planner may choose to add an additional LCF GPROC2, or toexamine the GSM circuit-switched provisioning to see whether an existing LCFGPROC2 could handle this additional load.


30 Sep 20037�40


GMR-0168P02900W21-M

Step 12: BTS provisioning impact

GPRS has no impact on the hardware provisioning of an M-Cell or Horizon BTS.

Step 13: OMC-R provisioning impact

The OMC-R is impacted primarily through the additional statistics generated by thePCU. The BSC merges the PCU statistics with the rest of the BSS statistics foruploading to the OMC-R over the 64 kbits/s X.25 link. No change in this linkprovisioning is required.

30 Sep 2003


68P02900W21-M

GMR-018�1

Chapter 8

BSC planning steps and rules for

LCS

GSR6 (Horizon II)

30 Sep 20038�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-018�3

Chapter overview

Introduction to LCS planning

This chapter provides the planning steps and rules for the BSC when supporting LCS.Only those equipments affected by LCS are covered in this chapter; for those notaffected, refer to Chapter 5.


S LCS overview.

S BSC planning for LCS overview.

S Capacity calculations.

� Determining the required BSS signalling link capacities with LCS.

� Determine the number of RSLs required with LCS.

� Determine the number of MTLs required for LCS.

� Determine the number of location service MTLs (LMTLs) required betweenBSC and SMLC.

� BSC GPROC functions and types with LCS.

� Traffic models with LCS.

S 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 BSC to SMLC links (LMTL).

GSR6 (Horizon II)LCS description

30 Sep 20038�4


GMR-0168P02900W21-M

LCS description

LCS overview

Location services (LCS) provides a set of capabilities that determine location estimatesof mobile stations and makes that information available to location applications.Applications requesting location estimates from LCS can be located in the MS, thenetwork, or external to the PLMN. LCS is not classified as a supplementary service andcan be subscribed to without subscribing to a basic telecommunication service. LCS isapplicable to any target MS, whether or not the MS supports LCS, but with restrictions onchoice of positioning method or notification of a location request to the MS user whenLCS or individual positioning methods respectively are not supported by the MS.

LCS utilizes one or more positioning mechanisms in order to determine the location of amobile station. Positioning a MS involves two main steps:

S Signal measurements

S Location estimate computation based on the measured signals.

Location service requests can be divided into three categories:

Mobile originating location request (MO�LR)

Any location request from a client MS to the LCS server made over the GSM airinterface. While an MO�LR could be used to request the location of another MS, itsprimary purpose is to obtain an estimate of the client MS�s own location, either for theclient MS itself or for another LCS client designated by the MS.

Mobile terminating location request (MT�LR)

Any location request from a LCS client where the client is treated as being external to thePLMN to which the location request is made.

Network induced location request (NI�LR)

Any location request for a target MS from a client that can be considered to lie inside anyof the PLMN entities currently serving the target MS. In this case, the LCS client is alsowithin the LCS server. Examples of a NI�LR include a location request needed forsupplementary services, for emergency call origination and by O&M in a visited PLMN.

GSR6 (Horizon II) LCS description

30 Sep 2003


68P02900W21-M

GMR-018�5

The positioning mechanism

The following positioning mechanisms have been standardized:

S Network based uplink time of arrival.

S Enhanced observed time difference.

S Assisted GPS.

In addition, timing advance can be used in conjunction with cell ID as a method thatprovides a rough, low quality location estimate.

Timing advance (TA)

The TA is based on the existing TA parameter. The TA value is known for the servingBTS. To obtain TA values in case the MS is in idle mode a special call, not noticed by theGSM subscriber (no ringing tone), is set up. The cell ID of the serving cell and the TA isreturned as the result of the TA.

The TA is used to assist all positioning mechanisms and as a fall-back procedure.

No additional Location Measurement Unit (LMU) is required.

Time of arrival (TOA) positioning mechanism

The uplink TOA positioning method is based on measuring the TOA of a known signalsent from the mobile and received at three or more measurement units. The knownsignal is the access bursts generated by having the mobile perform an asynchronoushandover. The method requires additional measurement unit (LMU) hardware in thenetwork at the geographical vicinity of the mobile to be positioned to accurately measurethe TOA of the bursts. Since the geographical coordinates of the measurement units areknown, the mobile position can be calculated via hyperbolic triangulation. This methodwill work with existing mobiles without any modification

Enhanced observed time difference (E-OTD) positioning mechanism

The E-OTD method is based on measurements in the MS of the E-OTD of arrival ofbursts of nearby pairs of BTSs. For E-OTD measurement synchronization, normal anddummy bursts are used. When the transmission frames of BTSs are not synchronized,the network needs to measure the relative or absolute time differences (RTDs or ATDs)between them. To obtain accurate triangulation, E-OTD measurements and, fornon-synchronized BTSs, RTD or ATD measurements are needed for at least threedistinct pairs of geographically dispersed BTSs. Based on the measured E-OTD valuesthe location of MS can be calculated either in the network or in the MS itself, if all theneeded information is available in the MS.

NOTE E-OTD is not supported in GSR6 (Horizon II) .


30 Sep 20038�6


GMR-0168P02900W21-M

Assisted global positioning system (A-GPS) positioning mechanism

The basic idea of A-GPS is to establish a GPS reference network (or a wide area differentialGPS network) whose receivers have clear views of the sky and can operate continuously.This reference network is also connected with the GSM network. At the request of aMS-based or network-based application, the assistance data from the reference network istransmitted to the MS to increase performance of the GPS sensor. For classification, whenthe position is calculated at the network, it is called a mobile assisted solution. When theposition is calculated at the handset, it is called a mobile based solution.

If implemented properly, the A-GPS method should be able to:

1. Reduce the sensor start up time.

2. Increase the sensor sensitivity.

3. Consume less handset power than conventional GPS does. Additional assisteddata, such as differential GPS corrections, approximate handset location or cellbase station location and others, can be transmitted to improve the locationaccuracy and decrease acquisition time.

NOTE A-GPS is not supported in GSR6 (Horizon II) .

System architecture

Figure 8-1 shows the LCS architecture.

Figure 8-1 Generic LCS logical architecture

gsmSCF

MSBTS(LMU

Type B)MSC/VLR

HLR

SMLC

GatewayMLC

ExternalLCS Client

GatewayMLC

Other PLMN

UmLs

BSCAAbis

Lb

LpCBC SMLC

LMUType A

Abis

LMUType A

Lg

Lc

Lh

Le

Lg

BSS

The BSS is involved in the handling of various positioning procedures. The BSS needs tobe modified to support:

S New LCS messages on the A-interface or Lb interface.

S New LCS messages on the Abis interface and Um interface.


30 Sep 2003


68P02900W21-M

GMR-018�7

LCS client

The LCS client is outside the scope of this standard.

GMLC

The gateway mobile location centre (GMLC) contains functionality required to supportLCS. In one PLMN there may be more than one GMLC.

The GMLC is the first node an external LCS client accesses in a GSM PLMN (that is, theLe reference point is supported by the GMLC). The GMLC may request routeinginformation from the HLR via the Lh interface. After performing registration authorization,it sends positioning requests to and receives final location estimates from the VMSCthrough the Lg interface.

SMLC

The serving mobile location centre (SMLC) contains functionality required to supportLCS. In one PLMN there may be more than one SMLC.

The SMLC manages the overall co-ordination and scheduling of resources required toperform positioning of a mobile. It also calculates the final location estimate andaccuracy.

Two types of SMLC are possible:

S NSS based SMLC � supports the Ls interface, see Figure 8-1.

S BSS based SMLC � supports the Lb interface see Figure 8-2.

An NSS based SMLC supports positioning of a target MS via signalling on the Lsinterface to the visited MSC. A BSS-based SMLC supports positioning via signalling onthe Lb interface to the BSC serving the target MS. Both types of SMLC may support theLp interface to enable access to information and resources owned by another SMLC.

The SMLC controls a number of LMUs for the purpose of obtaining radio interfacemeasurements to locate or help locate MS subscribers in the area that it serves. TheSMLC is administered with the capabilities and types of measurement produced by eachof its LMUs. Signalling between a NSS-based SMLC and LMU is transferred via the MSCserving the LMU using the Ls interface and either the Um interface for a Type A LMU orthe Abis interface for a Type B LMU. Signalling between a BSS based SMLC and LMU istransferred via the BSC that serves or controls the LMU using the Lb interface and eitherthe Um interface for a Type A LMU or the Abis interface for a Type B LMU.

For LCS, when a cell broadcast centre (CBC) is associated with a BSC, the SMLC mayinterface to a CBC in order to broadcast assistance data using existing cell broadcastcapabilities. The SMLC behaves as a user, cell broadcast entity, to the CBC.

MS

The MS may be involved in the various positioning procedures.


30 Sep 20038�8


GMR-0168P02900W21-M

LMUA LMU makes radio measurements to support one or more positioning methods. Thesemeasurements fall into one of two categories:

S Location measurements specific to one MS used to compute the location of thisMS.

S Assistance measurements specific to all MSs in a certain geographic area.

All location and assistance measurements obtained by an LMU are supplied to aparticular SMLC associated with the LMU. Instructions concerning the timing, the natureand any periodicity of these measurements are either provided by the SMLC or arepre-administered in the LMU.

Two types of LMU are defined:

S Type A LMU: accessed over the normal GSM air interface.

S Type B LMU: accessed over the Abis interface.

MSCThe MSC contains functionality responsible for MS subscription authorization andmanaging call-related and non call-related positioning requests of GSM LCS. The MSC isaccessible to the GMLC through the Lg interface and the SMLC via the Ls interface.

HLRThe HLR contains LCS subscription data and routing information. The HLR is accessiblefrom the GMLC through the Lh interface. For roaming MSs, the HLR may be in adifferent PLMN that the current SMLC.

The system architecture is differentiated by which network entity the SMLC is connectedto. When SMLC is connected to a MSC, the system architecture is referred as anNSS-based LCS architecture; otherwise, a BSS based LCS architecture when SMLC isconnected to a BSC.

NSS-based LCS architectureIn this architecture (see Figure 8-2), the SMLC is connected to a MSC instead of a BSC.The MSC acts as relay point for LCS signalling between the SMLC and BSC.

Figure 8-2 NSS-based architecture

BTS

Other PLMN

LMUHLR

GatewayMLC

GPSServing

MLC

OMC�L

BSC MSC

Ls

ExternalLCS Clients

ExternalLCS Clients

GatewayMLC

Lh

Le

Lg

Le

Locationcapablemobile

LMU: Location measurement unitMLC: Mobile location centre


30 Sep 2003


68P02900W21-M

GMR-018�9

BSS-based LCS architecture

In this architecture (see Figure 8-3), the SMLC is connected to a BSC instead of a MSC.The LCS signalling between the SMLC and BSC goes directly between these twoentities.

Figure 8-3 BSS-based architecture

BTS

Other PLMN

LMUHLR

GatewayMLC

GPSServing

MLC

OMC�L

BSC MSC

Lb

ExternalLCS Clients

ExternalLCS Clients

GatewayMLC

Lh

Le

Lg

Le

Locationcapablemobile

LMU: Location measurement unitMLC: Mobile location centre

GSR6 (Horizon II)Overview of BSC planning for LCS

30 Sep 20038�10


GMR-0168P02900W21-M

Overview of BSC planning for LCS

Introduction to LCS provisioning

From GSR6 onwards, the Motorola BSS provides the interfaces, protocols andmessages to support the GSM standards-based LCS architecture and Cell-ID and timingadvance (TA) positioning technology.

In GSR6, the BSS supports the network sub-system (NSS) based serving mobilelocation centre (SMLC) architecture or the BSS-based SMLC architecture.

The BSS supports new LCS signalling for all supported positioning technologies:

S New LCS signalling messages on the A-interface or Lb interface.

S New LCS signalling messages on the Mobis interface and Um interface.

The provisioning rules and steps for BSS equipment only support Cell-ID and the TApositioning method for LCS will be provided for NSS-based and BSS-based LCSarchitecture respectively in the following sections.

To plan the equipage of a BSC supporting LCS, certain information must be known. Inaddition to those factors covered in BSC planning overview, Introduction in Chapter 5,the following factors also must be known:

S The LCS traffic load to be handled (also take future growth into consideration).


In addition to the planning steps given in Chapter 5, planning a BSC that supports LCSalso involves the following steps, which result from Chapter 5:

1. Determine the LCS architecture a BSS will support. That is, the BSS will supporteither a NSS-based LCS architecture or a BSS-based LCS architecture, but notboth.

2. Plan the number of E1 or T1 links between the BSC and BTS site(s). Refer to thesection Determine the required BSS signalling link capacities in this chapter.

3. Plan the number of RSL links between the BSC and BTS site(s) based on the LCSarchitecture supported. Refer to the section Determine the RSLs required in thischapter.

4. Plan the number of MTL links between the BSC and the MSC based on the LCSarchitecture supported. Refer to the section Determine the number of MTLsrequired in this chapter.

5. Plan the number of LMTL links required between the BSC and the SMLC for BSSbased LCS architecture. Refer to Determine the number of LMTLs required inthis chapter. If the BSS only supports NSS-based LCS architecture, this stepshould be skipped.

6. Plan the number of GPROC2s required with support of LCS. Refer to the sectionGeneric processor (GPROC2) in this chapter.

7. Verify the planning process with support of LCS. Refer to the section Verify thenumber of BSU shelves and BSSC cabinets in Chapter 5.

GSR6 (Horizon II) Capacity calculations

30 Sep 2003


68P02900W21-M

GMR-018�11


Introduction

In addition to the capacity calculations in Chapter 5, the additional traffic load resultingfrom LCS needs to be taken into consideration in the capacity calculations.

This section provides information on how to calculate processor requirements, signallinglink capacities and BSC processing capacities for LCS. When equipping the BSS,equipage results in this chapter need to be combined with the results given in Chapter 5.

This section describes:


S Traffic models for LCS.




30 Sep 20038�12


GMR-0168P02900W21-M


BSC LCS signalling traffic model

Besides the factors described in Determining the required BSS signaling linkcapacity in Chapter 5 and Figure 5-1, LCS needs to be taken into account whenplanning a BSS.

S MTL link provisioning to support LCS signaling between the MSC and BSC foreither NSS-based LCS architecture or BSS-based LCS architecture, but not both.

S LMTL links provisioning if for BSS-based LCS architecture only.

S RSL links provisioning with LCS supported.


The parameters required to calculate BSC processing and signalling link capacities arelisted in Table 8-1 and Table 8-2 with their typical values.








Location update factor L = 2

GSM circuit-switched paging rate in pages per second P = 3


Ratio of LCSs per call LCS = 0.2


Mobile originated LCS ratio LRMO = 0.05






(continued)


30 Sep 2003


68P02900W21-M

GMR-018�13

GPRS parameters















Pages per call PPC = P * (T/N)


30 Sep 20038�14


GMR-0168P02900W21-M


Signalling message sequence and size assumptions

Refer to Chapter 5 for the signalling message sequence and size assumptions.

The number of uplink and downlink messages with the respective average messagesizes for each procedure are provided in Table 8-3.

Table 8-3 LCS procedure capacities

MSC to BSC link including protocol headerLCS request and response

(NSS-based architecture)

7 downlink messages with average size of 29 bytes

6 uplink messages with average size of 28 bytes

LCS request and response

(BSS-based architecture)



SMLC to BSC link including protocol headerLCS request and response 5 downlink messages with average size of 29 bytes


BSC to BTS linkLCS request and response

(NSS-based architecture)



LCS request and response

(BSS-based architecture)



An additional assumption, which is made in determining the values listed above inTable 8-3, is that the procedures not included in the traffic model are considered to havenegligible effect.

Paging assumptions

Refer to Chapter 5, Paging assumptions.

Link capacities

Refer to Chapter 5, Link capacities.

Take care that LCS signalling between MSC and BSC, and BSC and SMLC are allprovided for by C7 links. The total number of MTLs, and/or LMTLs should not exceed 16.


30 Sep 2003


68P02900W21-M

GMR-018�15

Determining the number of RSLs required

Introduction

In this section, the RSL number with LCS supported is calculated for the GSM circuitswitched part.

LCS signalling has no impact on GPRS RSL.


Refers to Chapter 5, RSL planning considerations.

Determining the number of RSLs

The number of BSC to BTS signalling links (RSL) must be determined for each BTS.

The RSL signalling link provisioning has a contribution from the GSM circuit-switchedpart of the network and from the GPRS part. LCS is included in the GSM circuit-switchedpart. LCS signalling has no impact on RSLGPRS. RSLGPRS refers to Chapter 5,Determining the number of RSLs.

The equation for determining the number of RSL links for the combined signalling load isas follows:


This is evaluated for 16 kbit/s RSLs or for 64 kbit/s RSLs. The interface between the BTSand BSC does not permit mixing the two RSL rates.

Where: RSLGPRS+GSM is: The combined number of RSLsignalling links on a per BTS sitebasis operating at a 16 kbit/s RSLrate or at a 64 kbit/s RSL rate.

RSLGPRS This is the number of RSLsignalling links required to servethe GPRS part of the network at16 kbit/s or at 64 kbit/s.

RSLGSM This is the number of RSLsignalling links required to servethe GPRS part of the network at16 kbit/s or at 64 kbit/s.


30 Sep 20038�16


GMR-0168P02900W21-M


The number of BSC to BTS signalling links (RSL) must be determined for each BTS.This number depends on the number of TCHs and PDCHs at the BTS. Table 8-4 givesthe number of RSLs required (rounded up integer value) for a BTS to support the givennumber of TCHs and PDCHs, based on the typical call parameters given in the standardtraffic model column of Table 8-1. If the call parameters differ significantly from thestandard traffic model, use the formulae for the non-standard traffic model.

For NSS-based or BSS-based LCS architecture, there is no difference when calculatingRSL provisioning from the Abis point of view.

Table 8-4 Number of BSC to BTS signalling links � LCS supported

With Enhanced OnePhase

With One Phase Access

#TCHs/BTS

(n)

#PDCHs/BTS

(Ngprs)

# 64 kbit/sRSLs

# 16 kbit/sRSLs

# 64 kbit/sRSLs

# 16 kbit/sRSLs

< = 30 0 1 1 1 1

15 1 2 1 2

30 1 2 1 2

31 to 60 0 1 2 1 2

15 1 3 1 3

30 1 3 1 3

45 1 3 1 3

60 1 3 1 3

61 to 90 0 1 3 1 3

15 1 4 1 4

30 1 4 1 4

45 1 4 1 4

60 1 4 1 4

75 1 4 1 4

90 1 4 1 4

91 to 120 0 1 4 1 4

15 2 5 1 4

30 2 5 2 5

45 2 5 2 5

60 2 5 2 5

75 2 5 2 5

90 2 5 2 5

60 1 4 1 4

(continued)


30 Sep 2003


68P02900W21-M

GMR-018�17

With Enhanced OnePhase

With One Phase Access

#TCHs/BTS

(n)

#PDCHs/BTS

(Ngprs)

# 64 kbit/sRSLs

# 16 kbit/sRSLs

# 64 kbit/sRSLs

# 16 kbit/sRSLs

121 to 150 0 2 5 2 5

15 2 6 2 6

30 2 6 2 6

45 2 6 2 6

60 2 6 2 6

151 to 180 0 2 5 2 5

15 2 6 2 6

30 2 6 2 6

45 2 7 2 6

60 2 7 2 7

NOTE The RSL calculations assume PGPRS = 0 for cells in which Ngprs= 0. This may not necessarily be true. If the BSC has GPRStimeslots, even if the cells do not have traffic channelsconfigured as PDCHs, it may have paging traffic.RACH_Arrivals/sec figures have been calculated assumingAvg_Sessions_per_user is as in the call model table.GPRS_Users_BTS has been calculated based on the number oftimeslots configured on the cell.A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, butnot both.


30 Sep 20038�18


GMR-0168P02900W21-M


Use the following formula to determine the required number of 64 kbit/s RSLs for CSsignalling with LCS supported. Sum up the result with the RSLGPRS@64k and round up tothe next integer to get the total 64kbit/s RSLs.

RSLGSM@64k �

n * (49 � 50 * S � 32 * H � 20 * L � 24 * LCS)1000 * U * T

�(27 � 3 * C) * PGSM * (1 � LCS)

8000 * U

64 kbit/s RSLs for GPRS signalling refers to Chapter 5, Determining the RSL numberrequired.

If the call parameters differ significantly from those given in Table 8-1, use the followingformula to determine the required number of 16 kbit/s RSLs for CS signalling with LCSsupported. Sum up the result with the RSLGPRS@16k and round up to the next integer toget the total 16kbit/s RSLs.

RSLGSM@16k �

�n * (49 � 50 * S � 32 * H � 20 * L � 24 * LCS)1000 * U * T

�(27 � 3 * C) * PGSM * (1 � LCS)

8000 * U� * 4

16 kbit/s RSLs for GPRS signalling refers to Chapter 5, Determining the RSL numberrequired.

Where: RSLGSM is: the number of BSC to BTS signalling links forGSM.

N the number of TCHs at the BTS site.Lcs the ratio of LCSs to callsS the ratio of SMSs to calls.H the number of handovers per call.L the location update factor.U the percent link utilization (for example 0.20).T the average call duration.PGSM the GSM paging rate in pages per second.

NOTE A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, butnot both.


Refer to Chapter 5, BSC to BTS E1 interconnect planning actions.


Refer to Chapter 5, BSC to BTS T1 interconnect planning actions.


30 Sep 2003


68P02900W21-M

GMR-018�19

Determine the number of LCFs for RSL processing

Determine the number of GPROC2s required to support the layer 3 call processing.There are two methods for calculating this number. The first is to be used when the callparameters are similar to those listed in Table 8-1 (standard traffic model). The secondmethod is to be used when call parameters differ significantly from those listed inTable 8-1.


GL3 � n1060

� B160

* (1 � 0.45 * LCS) � C120

Where: GL3 is: the number of LCF GPROC2s required to supportthe layer 3 call processing.

n the number of TCHs at the BSC.B the number of BTS sites.Lcs the ratio of LCSs to calls (0.2).C the number of cells.

NOTE As an approximation, the LCS procedure will not exceed 45% ofprocessor resources compared with CS calls and may beupdated by statistics results from performance simulations.



GL3 �

�n * (1 � 0.35 * S � 0.34 * H * (1 � 0.4 * i) � 0.32 * L � 0.45 * LCS)

(19.6 * T)� (0.004 � 0.00075 * PGSM * (1 � LCS)) * B �

C120�


N the number of TCHs under the BSC.Lcs the ratio of LCSs to calls (0.2).S the ratio of SMSs to calls.H the number of handovers per call.i the ratio of intra-BSC handovers to all handovers.L the location update factor.T the average call duration.PGSM the paging rate in pages per second.B the number of BTS sites.C the number of cells.

The planning information GL3_GPRS provided in Chapter 5 should be combined with thisprovisioning.


30 Sep 20038�20


GMR-0168P02900W21-M


Introduction

MTLs carry signalling traffic between the MSC and the BSC for circuit-switched call andLCS signalling. The number of required MTLs depends upon the BSS configuration sizeand traffic model. MTLs are carried on E1 or T1 links between the MSC and BSC, whichare also used for traffic.


In addition to those considerations described in Determining the number of MTLsrequired in Chapter 5, the following factors should be considered when planning the LCSsignalling links from the BSC to MSC:

S Determine the LCS architecture supported by the BSC. The BSC may supporteither NSS-based LCS architecture or BSS-based LCS architecture, but not both.

S Determine the LCS traffic requirements for the BSC. The traffic may be determinedusing the following method:

� Multiply the number of subscribers expected to use the BSC by the averageLCS traffic per subscriber.

S Total number of MTLs and/or LMTL (if BSS-based LCS architecture is supported).This should not exceed 16, which is the total number of C7 links.

NOTE These calculations are for the MTLs required from the BSSperspective, using the BSS planning rules. If the MSC vendorsupplies their own planning rules for a given configuration, themore conservative MTL provisioning figures should be used. Ifthe MSC vendor does not provide the planning rules for theMTLs required in a downlink direction, then use a load sharegranularity of 0 to be conservative in MTL provisioning.Load sharing of MTLs in the downlink direction depends on themechanism used by the MSC to load share the signalling linksfrom the MSC to BSC.


30 Sep 2003


68P02900W21-M

GMR-018�21


The required number of MSC to BSC signalling links (MTLs) depends on the desired linkutilization, the type and capacity of the GPROCs controlling the MTLs and the MTLloadshare granularity. The BSS software distributes call signalling traffic across 16 or 64logical links, which are then evenly spread across the active MTLs.

CCITT C7 uses a 4-bit number, the signalling link selection (SLS), generated by theupper layer to load share message traffic among the in-service links of a link set. Whenthe number of in-service links is not a power of 2, some links may experience a higherload than others. From GSR5 release onwards, the BSS supports distribution ofsignalling in the uplink direction, over 64 logical links. The BSS evenly distributes the 64logical links over the active MTLs.

The number of MTLs is a function of the number of MSC to BSC trunks or the offeredcall load and signalling for the call load. Table 8-5 to Table 8-8 give the recommendedminimum number of MSC to BSC signalling links based on the typical call parameters,detailed in Table 8-1. The value for N is the greater of the following:

S The offered call load (in Erlangs) from all the BTSs controlled by the BSC.


The offered call load for a BSS is the sum of the offered call load from all of the cells ofthe BSS. The offered call load at a cell is a function of the number of TCHs and blocking.As blocking increases the offered call load increase. For example, for a cell with 15 TCHsand 2% blocking, the offered call load is 9.01 Erlangs.

NOTE Before setting the load share granularity to 1, it is recommendedthat confirmation is gained from the Motorola local contact, orlocal office, that the switch is compatible with the load sharegranularity set to 1.


30 Sep 20038�22


GMR-0168P02900W21-M

Table 8-5 to Table 8-8 show how to estimate the number of MTLs to be used for the BSC,with 20% and 40% link utilization, respectively.

Table 8-5 Number of MSC and BSC signalling links(NSS-based LCS at 20% utilization)




number of MSC-BSCtrunks or the offered load

from the BTSsMinimumrequired


Recommended

N <= 160 1 2 1 2

160 < N <= 360 2 3 2 3

360 < N <= 480 3 4 3 4

480 < N <= 560 4 5 3 4

560 < N <= 760 4 5 4 5

760 < N <= 920 6 7 5 6

920 < N <= 1000 6 8 6 7

1000 < N <= 1080 8 9 6 7

1080 < N <= 1200 8 9 7 8

1200 < N <= 1520 8 9 8 9

1520 < N <= 1720 16 16 10 11

1720 < N <= 2000 16 16 11 12

2000 < N <= 2400 16 16 13 14

2400 <N <= 3000 16 16 16 16


30 Sep 2003


68P02900W21-M

GMR-018�23

Table 8-6 Number of MSC and BSC signalling links(BSS-based LCS at 20% utilization)







Recommended

N <= 160 1 2 1 2

160 < N <= 360 2 3 2 3

360 < N <= 480 3 4 3 4

480 < N <= 520 4 5 3 4

520 < N <= 760 4 5 4 5

760 < N <= 920 6 7 5 6

920 < N <= 1000 6 8 6 7

1000 < N <= 1080 8 9 6 7

1080 < N <= 1200 8 9 7 8

1200 < N <= 1520 8 9 8 9

1520 < N <= 1720 16 16 10 11

1720 < N <= 2000 16 16 11 12

2000 < N <= 2400 16 16 13 14

2400 <N <= 3000 16 16 16 16

Table 8-7 Number of MSC and BSC signalling links(NSS-based LCS at 40% utilization)







Recommended

N <= 360 1 2 1 2

360 <N <= 760 2 3 2 3

760 < N <= 1000 3 4 3 4

1000 < N <= 1080 4 5 3 4

1080 < N <= 1520 4 5 4 5

1520 < N <= 1840 6 7 5 6

1840 < N <= 2000 6 7 6 7

2000 < N <= 2200 8 9 6 7

2200 < N <= 2400 8 9 7 8

2400 < N <= 3040 8 9 8 9

3040 < N <= 3200 16 16 10 11


30 Sep 20038�24


GMR-0168P02900W21-M

Table 8-8 Number of MSC and BSC signalling links(BSS-based LCS at 40% utilization)







Recommended

N <= 360 1 2 1 2

360 <N <= 760 2 3 2 3

760 < N <= 1000 3 4 3 4

1000 < N <= 1080 4 5 3 4

1080 < N <= 1480 4 5 4 5

1480 < N <= 1840 6 7 5 6

1840 < N <= 2000 6 7 6 7

2000 < N <= 2200 8 9 6 7

2200 < N <= 2400 8 9 7 8

2400 < N <= 3000 8 9 8 9

3000 < N <= 3200 16 16 10 11

NOTE The capacities shown in Table 8-5 to Table 8-8 are based on thestandard traffic model shown in Table 8-1.It is recommended that the C7 links be designed to operate at nomore than 20% link utilization when the MTL is running on aGPROC, and no more than 40% utilization when the MTL isrunning on a GPROC2. However, before use of the 40%utilization of GPROC2, it is imperative that the operator verifiesthat the MSC vendor can also support 40% utilization at the MSCend, if not, then only 20% link utilization should be used forGPROC2.


30 Sep 2003


68P02900W21-M

GMR-018�25

Non-standard traffic modelIf the call parameters differ significantly from those given in Table 8-1, the followingprocedure is used to determine the required number of MSC to BSC signalling links:

1. Use the formula detailed below to determine the maximum number of Erlangssupported by a C7 signalling link (nlink).

nlink_bss �

(1000 * U * T)(40 � 47 * S � 22 * H * (1 � 0.8 * i) � 24 * L � 31 * LCS) � 9 * PPC * (1 � LCS)

nlink_nss �


2. Use the formula detailed below to determine the maximum number of Erlangssupported by a GPROC2 (LCF�MTL) supporting a C7 signalling link (nlLCF�MTL).

nlLCF�MTL �

(20 * T)(1 � 0.16 * S � 0.5 * H * (1 � 0.6 * i) � 0.42 * L � 0.45 * LCS) � PPC * (0.005 * B � 0.05) * (1 � LCS)

3. The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is thesmaller of the two numbers from Steps 1 and 2.

nlmin � MIN (nlink, nlLCF_MTL)

4. Signalling over the A�interface is uniformly distributed over a number of logicallinks. The number of logical links is defined on the BSC by database parametermtl_loadshare_granularity = 0 or 1, which corresponds to 16 or 64 logical links,respectively, over which the MTL signalling is load shared. Hence, the total amountof traffic that a logical link would hold, is calculated as:

Nlogical � NNg

Where Ng= 16 or 64.

5. Next we need to determine the number of logical links each MTL (physical link)can handle (nlog�per�mtl):


Nlogical�



�� R � 16

NOTE mtls should not exceed 16 per BSC.The formula in step 2 has been calculated using 70% meanutilization of GPROC2.Field experience suggests it is good practice to maintain themean utilization of GPROCs at or below 70%.All GPROCs should function normally up to 100% utilization.Beyond this, inter-process communication will start to slow downdue to queueing of internal BSS messages, thus impacting onsystem performance.


30 Sep 20038�26


GMR-0168P02900W21-M


The purpose of the LCF GPROC2 is to support the functions of MSC link protocol,layer 3 call processing, and the BTS link protocol. It is recommended that an LCFsupports either 2 MTLs or 1 to 30 BTSs, with up to 31 RSLs and layer 3 call processing.

NOTE It is not recommended that an LCF supports both an MTL andBSC to BTS signalling links.


Since one LCF GPROC2 can support two MTLs, the number of required LCF is:


However, if the traffic model does not conform to the standard model, below formula willbe used:

if 2 * nlink � nlLCF�MTL, then NLCF � mtls

otherwise:





nlink calculated in the previous section.


Planning actions for transcoding at the BSC

Refer to Chapter 5.

GSR6 (Horizon II) Determining the number of LMTLs required

30 Sep 2003


68P02900W21-M

GMR-018�27

Determining the number of LMTLs required

Introduction

LMTLs carry the LCS signaling traffic between the BSC and the SMLC. This is onlyapplicable for BSS-based LCS architecture.

The number of required LMTLs depends upon the BSS configuration size and trafficmodel. LMTLs are carried on E1 or T1 links between the SMLC and BSC.


The following factors need to be considered when planning the number of LMTL linksfrom the BSC to the SMLC:

S Determine the LCS traffic requirements of the BSC.

S A BSC can only connect to one SMLC.

Determining the number of LMTLs

Traffic model

The number of required LMTLs depends upon the BSS configuration size and trafficmodel.

See Table 8-1 and Table 8-3.

LMTL number

Use the following formula to determine the required number of 64 kbit/s LMTLs (roundedup to the next integer):

LMTL � ROUND UP �LCS_BSC_Rate * 191000 * UBSC_SMLC

�

Where: LMTL is: the number of BSC to SMLC signallinglinks.

LCS_BSC_Rate requests number per BSC per second.UBSC_SMLC the percentage of the link utilization.ROUND UP rounding up to the next integer.

GSR6 (Horizon II)Generic processor (GPROC2) for LCS

30 Sep 20038�28


GMR-0168P02900W21-M

Generic processor (GPROC2) for LCS

Introduction

Refer to Chapter 5.

GPROC2 functions and types

Besides the possible general task groupings or functions for assignment to GPROC2s inChapter 5, the GPROC2 can also support:

S MSC link protocol (C7) with LCS supported.

S SMLC link protocol for LCS (LMTL).

The defined GPROC2 devices and functions for the BSC are specified in Chapter 5.


Besides those factors considered and specified in Chapter 5, when planning theGPROC2 complement each BSC also requires:

S The number of LCFs to support LMTLs for BSS-based LCS architecture.

Link control function

Combined with what specified in Chapter 5, the following factors should be consideredwhen planning the number of LCFs:

S LMTLs are handled by dedicated LCFs for BSS-based LCS architecture.

S One dedicated LCS LCF GPROC2 is needed to support the SMLC link protocol forLCS.

The planning rules for LCFs exclusively using GPROC2 are:

S A single GPROC2 will support up to 31 BTS sites and 31 RSLs, limited to thefollowing calculation:

2 * rsls � carriers � 120

Where carriers = the total number of radios for the BTS site(s).

nLCF * (21 � 14 * S � 14 * H � 9 * L � 11 * LCS)T

� P � PGPRS ��i�1

n

[RACH�sec] * 4.6 � 500

Where nLCF = the number of TCHs on the sites under a LCFandn = the total number of sites on the LCF.

If any LCF does not satisfy the above criteria, either rebalancing of sites on the availableLCF�GPROC2s at the BSC is required or additional LCF�GPROC2s may need to beequipped at the BSC to handle the traffic load.

NOTE It is not recommended that a LCF supports both an LMTL andBSC to BTS signalling links.

30 Sep 2003


68P02900W21-M

GMR-019�1

Chapter 9

Planning exercise

GSR6 (Horizon II)

30 Sep 20039�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-019�3

Chapter overview

Introduction to the planning exercise

This chapter contains planning exercises designed to illustrate the use of the rules andformulae provided in earlier chapters.

The tables of required equipment in this chapter list only the major Motorola supplieditems. Equipment not covered in these examples includes: cable, external power suppliesand air conditioning equipment. Consult the appropriate Motorola local office forassistance in ensuring that all necessary items are purchased.


S The initial requirements for the planning exercise using the standard call model.

S A planning exercise using the standard call model.

S A planning exercise using alternative call models.

S A planning exercise for when LCS is used.

GSR6 (Horizon II)Initial requirements

30 Sep 20039�4


GMR-0168P02900W21-M

Initial requirements

Requirements

In the area of interest, a demand analysis has identified the requirement for 11 BTSs withthe busy hour Erlang requirement shown in column two of Table 9-1.

Column three of Table 3-8 or Table 3-9 (depending on position in location area) in theControl channel configurations section of Chapter 3 provides the maximum Erlangcapacity for a given number of carriers at 2% blocking. Column one of the same tableslists the number of carriers (RTF) required; column three of Table 9-1 lists thisinformation.

If other blocking factors at the air interface are required, the number of Erlangs forcolumn three of Table 3-8 or Table 3-9 in the Control channel configurations section ofChapter 3 can be found by reference to standard Erlang B tables for the number of trafficchannels in column two of Table 3-8 or Table 3-9 in the Control channel configurationssection of Chapter 3 at the required blocking factor.

Table 9-1 Busy hour demand and number of carriers

BTS identification Erlangs Antenna configuration

A 6 Omni 2

B 5 Omni 2

C 2 Omni 1

D 5 Omni 2

E 14 Omni 3

F 10 Omni 3

G 5 Omni 2

H 2 Omni 1

J 5 Omni 2

K 20/20/20 Sector 4/4/4

L 5 Omni 2

Total 119 32 carriers

GSR6 (Horizon II) Initial requirements

30 Sep 2003


68P02900W21-M

GMR-019�5

Network topology

Using a frequency planning tool it is possible to assign adequate frequencies to supportthe BTS antenna configurations of Table 9-1. Based on this, initial planning of thenetwork gives the topology shown in Figure 9-1.

Figure 9-1 Network topology

BSC

BTS B

BTS C

BTS D

BTS K

BTS L

BTS E

BTS F

BTS G BTS J

BTS H

BTS A

RXCDR MSC

OMC-R

GSR6 (Horizon II)The exercise

30 Sep 20039�6


GMR-0168P02900W21-M

The exercise

Introduction

In order to illustrate the planning steps, the individual hardware requirements for BTS Band BTS K will be calculated, followed by the calculation to produce the hardwarerequirements for the BSC, and RXCDR. Where parameters are required for the databasegeneration they are noted.

The calculations for the hardware capacity use the standard call model given in Chapter3 and Chapter 5.

GSR6 (Horizon II) Determine the hardware requirements for BTS B

30 Sep 2003


68P02900W21-M

GMR-019�7

Determine the hardware requirements for BTS B

Introduction

From Figure 9-1 and Table 9-1 it can be seen that BTS B requires two RF carriers in anomni configuration to carry a peak demand of five Erlangs.

Cabinet

From the site requirements and the potential future expansion it can be determined thatthis site should be built using an M-Cell6 indoor cabinet. For the cabinet and any of thefollowing items, contact the Motorola local office if part numbers are required.

Main site number

Contact the Motorola local office if part numbers are required.

Interface option


Power redundancy


Duplexing

Only two antennas will be used on this site, so we need to specify duplexing. Contact theMotorola local office if part numbers are required.

Digital redundancy

It is not considered that the purpose of this site justifies the expense of digitalredundancy.

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 inbackground mode. Contact the Motorola local office if part numbers are required.

Database option


GSR6 (Horizon II)Determine the hardware requirements for BTS B

30 Sep 20039�8


GMR-0168P02900W21-M

Summary

The equipment required, and an example of customer order creation for an M-Cell6indoor (900 MHz) configuration, to implement BTS B is listed in Table 9-2 and Table 9-3.

Table 9-2 Customer ordering guide 900 MHz (M-Cell6 indoor)

Question Compulsory

Voltage used +27 V dc

�48 V/60 V dc

110/240 V ac

How many cells are required? 1

2

3

How many carriers are required per cell? (RF configuration) 1

2

3

4

5

6

7

8

How many cabinets are required for the RF configuration? 1

2

3

4

What type of combining is required? CBF (Hybrid)

CCB (Cavity)

3 I/P CBF

Air

What line interface is required? T43 (E1)(75 ohm)

BIB (E1)(120 ohm)

BIB (T1)(120 ohm)

GSR6 (Horizon II) Determine the hardware requirements for BTS B

30 Sep 2003


68P02900W21-M

GMR-019�9

Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor)

Question Options

Is link redundancy required? Yes

No

Is digital redundancy required? Yes

No

Is power redundancy required? Yes

No

Is duplexing required? Yes

No

Is a high power duplexer shelf and/or external rack required? Yes

No

Are 16-way alarm inputs required? Yes

No

Is a memory card required? Yes

No

Is database required?(Provided by local office)

Yes

No

Is ac battery backup required? Yes

No

Select ac battery box options? Yes

No

Is �48 V power supply module (APSM) required? Yes

No

Is comms power supply module (CPSM) required? Yes

No

GSR6 (Horizon II)Determine the hardware requirements for BTS K

30 Sep 20039�10


GMR-0168P02900W21-M

Determine the hardware requirements for BTS K

Introduction

From Figure 9-1 and Table 9-1 it can be seen that BTS K requires 12 RF carriers in asector 4/4/4 configuration to carry a peak demand of 20 Erlangs per sector.

Cabinet

From the site requirements and the potential future expansion it can be determined thatthis site will be contained in two or three Horizonmacro cabinets.

Alternatively, the site can be contained in a single Horizon II macro indoor cabinet.

Receiver requirements

A single Horizon II macro cabinet solution, a two cabinet Horizonmacro solution and athree cabinet Horizonmacro solution are provided below.

Single cabinet Horizon II macro solution

The single cabinet will contain six CTU2 transceivers, operating in pairs and in dualcarrier mode to provide the 3 sector 4/4/4 configuration required.

Two cabinet Horizonmacro solution

Each cabinet will have four carriers of a sector plus two carriers of a shared sector. TwoSURF modules will support the four carriers in each sector. The shared sector will besupported by interconnecting the SURF in the master cabinet to the SURF in theextender cabinet.

Three cabinet Horizonmacro solution

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

Transmitter combining requirements

A one, two, and three cabinet solution are provided below.

Single cabinet Horizon II macro solution

Each sector requires two DUPs, one for each CTU2.

Two cabinet Horizonmacro solution

Each sector requires two DCF modules. The shared sector will have one DCF module inthe master cabinet and the other DCF in the extender cabinet.

Three cabinet Horizonmacro solution

Each cabinet will be dedicated to a sector, which requires one DDF and HCU modules.

GSR6 (Horizon II) Determine the hardware requirements for BTS K

30 Sep 2003


68P02900W21-M

GMR-019�11

Summary

The equipment required, and an example of customer order creation for a single cabinetHorizon II macro indoor (1800 MHz) configuration, to implement BTS K is listed inTable 9-4 and Table 9-5.

Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor)

Question Compulsory n

Voltage used +27 V dc

�48 V/60 V dc

240 V ac n

How many cells are required? 1

2

3 n

How many carriers are required per cell? (RF configuration) 1

2

3

4

5

6

7

8

n

One carrier (single density) or two carriers (double density)required per CTU2?

1

2 n

How many cabinets are required for the RF configuration? 1

2

3

4

n

What type of combining is required? DUP & Air

DUP & HCU

DUP & DHU

DUP, HCU &Air

DUP, DHU &Air

DUP,HCU,DHU & Air

n

What line interface is required? T43 (E1)(75 ohm)

BIB (E1)(120 ohm)

n

GSR6 (Horizon II)Determine the hardware requirements for BTS K

30 Sep 20039�12


GMR-0168P02900W21-M

Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor)

Question Options n

Is digital redundancy required? Yes

No

n

Is power redundancy required? Yes

No n

Is an extra line interface required? Yes

No n

Are 16-way alarm inputs required? Yes

No n

Is a compact flash (memory) card required? Yes

No

n

Is a stacking bracket required? Yes

No n

Is battery backup required? Yes

No n

Is database required?(Provided by local office)

Yes

No

n

GSR6 (Horizon II) Determine the hardware requirements for the BSC

30 Sep 2003


68P02900W21-M

GMR-019�13

Determine the hardware requirements for the BSC

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

BSC to BTS links

Figure 9-1 shows that the number of links connected from the BTSs to the BSC is four.

BSC to MSC links

Reference to standard Erlang B tables shows that 119 Erlangs at 1% blocking requires138 traffic channels.

One OML link, one XBL link and one C7 signalling link are required. The number oftrunks required is given by:

[(1 � 1) � (1 � 1) � (1 � 1) � (138�4)]�31 � 1.3

This value should be rounded up to 2.

Transcoder requirement

None required, remote transcoding.

MSI requirement

Minimum number of MSIs required is given by:

(4 � 2)�2 � 3

Line interface

Depending on the interface standard (balanced or unbalanced) used, one BIB or one T43is adequate for three MSIs.

GPROC2 requirement

GPROC function requirements are listed in Table 9-6.

Table 9-6 GPROC2s required at the BSC

Function Number required

BSP 1

LCFs for MTLs 1

LCFs for RSLs 1

Optional GPROC requirements

Redundant BSP, CSFP 1

Redundant LCP 1

Total GPROC2s 3+2

NOTE The notation n + m means that n items are required plus m forredundancy.

GSR6 (Horizon II)Determine the hardware requirements for the BSC

30 Sep 20039�14


GMR-0168P02900W21-M

KSW requirement

Device timeslot requirements are listed in Table 9-7.

Table 9-7 BSC timeslot requirements

Device Number required

GPROC2s 5*32 = 160

XCDR None

MSI 3*64 = 192

Total timeslots 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 arerequired. 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 redundantLAN requires one additional LANX per cabinet.

Power supply

Depending on the power supply voltage, two EPSM plus one for redundancy or twoIPSM plus one for redundancy will be required.

GSR6 (Horizon II) Determine the hardware requirements for the BSC

30 Sep 2003


68P02900W21-M

GMR-019�15

Summary

The equipment required to implement the BSC is listed in Table 9-8.

Table 9-8 Equipment required for the BSC

Equipment Number required

BSSC2 cabinet 1

BSU shelf 1

MSI 3

BIB or T43 1

GPROC2 3+2

KSW 1+1

GCLK 1+1

PIX (provides up to 8 external alarms) 1

BBBX 1

LANX 1

EPSM/IPSM (+27 V)

(�48 V)

2+1


GSR6 (Horizon II)Determine the hardware requirements for the RXCDR

30 Sep 20039�16


GMR-0168P02900W21-M

Determine the hardware requirements for the RXCDR

MSI requirementsIt is necessary to provide enough MSIs to communicate on the links to the BSC, for E1links the traffic connection comes directly from the transcoder card.

Links to the BSCFrom the calculation in the previous section BSC to MSC links, it can be seen that thereare two links to the BSC.

Links to the OMC-RFrom the topology (see Figure 9-1) it can be seen that a link to the OMC-R from theRXCDR must be provided.

Number of MSIs requiredFrom the foregoing it can be seen that three E1 links are required.

The number of MSI cards is given by:

3�2 � 1.5


Transcoder requirementFrom the calculation in the previous section BSC to MSC links, it can be seen that 138traffic 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.

XCDR and GDP cards may be mixed within a shelf.

Link interfaceFrom the MSI requirements it can be seen that two E1 links to the BSC and one to theOMC-R are required. From the transcoder requirements it can be seen that a further fiveE1 links are required. A total of eight E1 links are required.

The number of BIB/T43s is given by:

8�6 � 1.3


GPROC2 requirementOne GPROC2 is required, plus one for redundancy.

KSW requirementFrom the number of MSIs, transcoders and E1 links, it can be seen that the total numberof timeslots is given by:

2 * 16 � 5 * 16 � 2 * 64 � 240

One KSW is required, plus one for redundancy.

GSR6 (Horizon II) Determine the hardware requirements for the RXCDR

30 Sep 2003


68P02900W21-M

GMR-019�17

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 arerequired. 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 redundantLAN requires one additional LANX per cabinet.

Power supply

Depending on the power supply voltage, two EPSMs plus one for redundancy or twoIPSMs plus one for redundancy will be required.

GSR6 (Horizon II)Determine the hardware requirements for the RXCDR

30 Sep 20039�18


GMR-0168P02900W21-M

Summary

The equipment required to implement the RXCDR is listed in Table 9-9.

Table 9-9 Equipment required for the RXCDR

Equipment Number required

BSSC2 cabinet 1

RXU shelf 1

MSI 2

XCDR/GDP-E1 5

BIB or T43 2

GPROC2 1+1

KSW 1+1

GCLK 1+1

PIX (provides up to 8 external alarms) 1

BBBX 1

LANX 1

EPSM/IPSM (+27 V)

(�48 V)

2+1


GSR6 (Horizon II) Calculations using alternative call models

30 Sep 2003


68P02900W21-M

GMR-019�19

Calculations using alternative call models

Introduction

This section is provided to assist users for whom the planning models given in Chapter 4,Chapter 5 and Chapter 6 are inappropriate. Where this is the case, the various planningtables that are used in the previous example in this chapter will not be correct and theactual values will need to be derived using the formulae given in Chapters 3, 5, and 6.These necessary calculations are demonstrated in the following examples.

Planning example 1

Dimension a network with following requirements:

S GSM software release = GSR6 (Horizon II) .

S Number of sites 4/4/4 sites (BTS: M-Cell6) = 28.

S Number of omni 2 sites (BTS: M-Cell2) = 2.

Call model

S Call duration T = 75 s.

S Ratio of SMSs per call S = 0.1.

S Ratio of location updates per call = 2.

S Ratio of IMSI detaches per call I d = 0.2 (type 2).

S Location update factor L = 2 + 0.5 * 0.2 = 2.1.

S No. of handovers per call H = 2.

S Ratio of intra�BSC handovers to all handovers i = 0.5.

S Paging rate P = 10 pages per second.

S MTL link utilization = 35% (0.35).

S RSL link utilization U = 25% (0.25).

S CCCH utilization = 33%.

S Probability of blocking TCH PB�TCH < 2%.

S Probability of blocking SDCCH PB�SDCCH < 1%.

S Probability of blocking on A-interface < 1%.

S Number of BTS sites B = 28 +2 = 30.

S Number of cells per BSS C = 28 * 3 + 2 = 86

S Number of cells per BTS CBTS = 3.

S GSM paging rate in pages per second PGSM = 10.

S GPRS paging rate in pages per second PGPRS = 3.

S Mean_TBF_Rate = 1.

S Number of GPRS timeslots NGPRS= 0.

GSR6 (Horizon II)Calculations using alternative call models

30 Sep 20039�20


GMR-0168P02900W21-M

Other considerations

S Line interface type = E1.

S Network termination option = T43.

S Power voltage option = �48/�60 V dc.

S Type of combining used = hybrid (CBF).

S Dedicated CSFP = YES.

S CSFP redundancy = NO.

S Redundancy for all other modules = YES.

S MTL links redundancy = YES.

S RSL link redundancy = NO.

S Coding schemes CS3 and CS4 used = NO.

S BTS connectivity = star configuration.

S IMSI/TMSI paging = TMSI.

S MTL load balancing granularity = 16.

GSR6 (Horizon II) limitations

S Max. BTS sites = 100.

S Max. BTS cells = 250.

S Active RF carriers = 512.

S Trunks = 3000.

S C7 links = 16.


30 Sep 2003


68P02900W21-M

GMR-019�21

Step 1 : Cell planning � control channel calculations

From Erlang B tables, the number of Erlangs supported by 32 TCHs with grade ofservice (GOS) of 2% is 23.72 Erlangs and the number of Erlangs supported by 16 TCHs(2 carrier cell) with GOS of 2%, is 9.83 Erlangs.

Total Erlangs offered by a 4/4/4 BTS = 3 * 23.72 = 71.06 Erlangs.

Total Erlangs offered by an omni 2 BTS = 9.83 Erlangs.

4 carrier cell � determining the number of CCCHs

Call arrival rate:

lcall � e�T � 23.72�75 � 0.316

Ratio of SMSs to call:

ls � S * e�T � 0 * 23.72�75 � 0.032

Ratio of location updates to calls:

lLU � L * e�T � 2.1 * 23.72�75 � 0.664

Access grant rate is given by:

lAGCH � lcall � lS � lL � 1.012

From the call model parameters, paging rate PGSM, is 10, so the average numberof CCCH blocks required to support paging only is:

NPCH � PGSM�(4 * 4.25) � 10�(4 * 4.25) � 0.588

The average number of CCCH blocks required to support AGCH only is given by:

NAGCH_GSM � lAGCH�(2 * 4.25) � 1.012�(2 * 4.25) � 0.119

Using a CCCH utilisation figure, UCCCH, of 0.33, the average number of CCCHblock required to support both PCH and AGCH is given by:

NPAGCH � (NAGCH � NPCH)�UCCCH � (0.119 � 0.588)�0.33 � 2.143

Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. Thiscan be supported using a non-combined BCCH with 9 CCCH timeslots. It isrecommended to reserve 2 CCCH block for access grant messages.

4 carrier cell � determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call modelparameters, the average number of SDCCHs, NSDCCH is given by formulaedetailed in Chapter 3 as:

NSDCCH � lcall * TC � lLU * (TL � Tg) � ls * (TS � Tg)

� 0.316 * 5 � 0.664 * (4 � 4) � 0.032 * (6 � 4) � 7.211

The number of SDCCHs to support an average number of busy SDCCHs of 7.211with less that 1% blocking as determined by use of Erlang B tables, is 14. Hence,the number of timeslots required to carry SDCCH signalling traffic is 2, with eachtimeslot offering 8 SDCCHs.


30 Sep 20039�22


GMR-0168P02900W21-M

4 carrier cell � determining the number of TCHs

The total number of signalling timeslots required for a 4 carrier configuration withthe given call model parameters is 3 (1 non-combined BCCH timeslot with 9CCCHs and 2 timeslots with 8 SDCCHs each).

Hence, the number of traffic channels per 4 carrier cell = 32 � 3 = 29

Omni 2 cell � determining the number of CCCHs

Call arrival rate:

lcall � e�T � 9.83�75 � 0.131


lS * e�T � 0.1 * 9.83�75 � 0.013


lLU � L * e�T � 2.1 * 9.83�75 � 0.275



From the call model parameters paging rate PGSM, is 10, so the average numberof CCCH blocks required to support paging only is:

NPCH � PGSM�(4 * 4.25) � 10�(4 * 4.25) � 0.588


NAGCH � lAGCH_GSM�(2 * 4.25) � 0.419�(2 * 4.25) � 0.049

Using a CCCH utilisation figure, UCCCH, of 0.33, the average number of CCCHblock required to support both PCH and AGCH is given by:


Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. Thiscan be supported using a non-combined BCCH timeslot with 9 CCCH blocks. It isrecommended to reserve 2 CCCH blocks for access grant messages.

Omni 2 cell � determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call modelparameters, the average number of SDCCHs, NSDCCH is given by formuladetailed in Chapter 3:


� 0.131 * 5 � 0.275 * (4 � 4) � 0.013 * (6 � 4) � 2.988

The number of SDCCHs to support an average number of busy SDCCHs of 2.988with less than1% blocking as determined by use of Erlang B tables is approx. 8.The number of timeslots required to carry SDCCH signalling traffic is 1.

Omni 2 cell � determining the number of TCHs

The total number of signalling timeslots required for a 4 carrier configuration withthe given call model parameters is 3 (1 non-combined timeslot BCCH with 9CCCHs and 2 timeslots with 8 SDCCHs each).

Therefore, the number of traffic channels per 2 carrier cell = 16 � 2 = 14

Hence, traffic offered by a 4 carrier cell is the 21.04 Erlangs (29 channels at 2%GOS) and that by a 2 carrier cell is 8.2 Erlangs (14 channels at 2 % GOS).Carried Erlangs for the cells are 20.62 and 8.04, respectively.


30 Sep 2003


68P02900W21-M

GMR-019�23

Step 2 : BSS planning � determining the number of RSLs

The number of 64 kbits/sec RSLs required is given by :

RSLGSM�GPRS@64k �

n * (95 � 67 * S � 35 * H � 25 * L)1000 * U * T �

(47 � 3 * CBTS) * PGSM � (52 � CBTS) * PGPRS8000 * U �

6 * Mean_TBF_Rate * NGPRS1000 * U

Where, n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS):


29 * 3 * (95 � 67 * 0.1 � 35 * 2 � 25 * 2.1)1000 * 0.25 * 75

�(47 � 3 * 3) * 10 � (52 � 3) * 3

8000 * 0.25� 6 * 0

1000 * 0.25 = 1.40

The number of RSLs required per 4/4/4 site is 2 and that for an omni 2 site is 1(calculated in similar way).

BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by:


31

(CS3 and CS4 are not used.)

Number of E1 links required between each 4/4/4 BTS and BSC:

� {(0 * 4) � (12 * 2) � 0} � 231

1

Number of E1 links required between each omni 2 BTS and BSC:

� {(0 * 4) � (2 * 2) � 0} � 131

1

Hence, only one E1 interconnect is required between each BTS and BSC for thegiven site configurations (provided they are in star configurations), giving a total of30 E1 links.


Number of LCF-RSLs required if given by:

GL3 �

�n * (1 � 0.35 * S � 0.34 * H * (1 � 0.4 * i) � 0.32 * L)(19.6 * T)

� (0.00075 * PGSM � 0.004) * B � C120�

Where n is the number of TCHs under a BSC:

�2464 * (1 � 0.35 * 0.1 � 0.34 * 2 * (1 � 0.4 * 0.5) � 0.32 * 2.1)(19.6 * 75)

� (0.00075 * 10 � 0.004) * 30 � 86120�

The number of LCFs for RSL processing is 5.


30 Sep 20039�24


GMR-0168P02900W21-M

Determining the number of MTLs

Total Erlangs offered by the BSC with 28 sites with 4/4/4 configuration and 2 omni2 site

� 28 * 3 * 21.04 � 2 * 8.04 � 1784 Erlangs

Total Erlangs carried by the BSC with 28 sites with 4/4/4 configuration and 2 omni2 site

� 28 * 3 * 20.62 � 2 * 8.04 � 1748 Erlangs

The number of trunks required to carry traffic on the A-interface with less than 1%blocking is 1812; check that the figure is within limits.

Number of pages per call:

Ppc � PGSM * T�N � 10 * 75�1812 � 0.42

Using the call model parameters the number of MTLs can be calculated usingformulae detailed in Chapter 5.

Maximum number of Erlangs supported by a C7 link is given by:

nlink �(1000 * U * T)

(40 � 47 * S � 22 * H * (1 � 0.8 * i) � 24 * L � 9 * PPC)

nlink �(1000 * 0.25 * 75)

(40 � 47 * 0.1 � 22 * 2 * (1 � 0.8 * 0.5) � 24 * 2.1 � 9 * 0.42)

= 150 Erlangs.

Maximum number of Erlangs supported by GPROC2 supporting a C7 signallinglink is given by:


(1 � 0.16 * S � 0.5 * H * (1 � 0.6 * i) � 0.42 * L � PPC * (0.005 * B � 0.05))

nlLCF�MTL �(20 * 75)

(1 � 0.16 * 0.1 � 0.5 * 2 * (1 � 0.6 * 0.5) � 0.42 * 2.1 � 0.42 * (0.005 * 30 � 0.05))

= 560 Erlangs.

Hence:

� nlmin � min(nlink, nlLCF�MTL) � 150 Erlangs

Amount of traffic (or number of trunks) each logical link will hold:

Nlogical � 1812�16 � 113.25

using a MTL load sharing granularity of 16.

The number of logical links each MTL can handle:

nlog_per_mtl � round down � 150113.25

� 1

The number of required MTLs:

mtls � round up �161�� 16

Check that the figure is within limits.

Determining the number of LCFs for MTL processing

Using the formula detailed in Chapter 5, since:

2 * nlink � nlLCF�MTL

NLCF � ROUND UP �162�� 8


30 Sep 2003


68P02900W21-M

GMR-019�25

XBL requirements

Referring to Table 5-12 in Chapter 5,

Number of XBLs required = 2.

GPROC requirements

Number of GPROC2s required for MTL processing = 8.

Number of GPROC2s required for RSL processing = 5.

Total number of LCF GPROC2s required = 13; check that the figure is withinlimits.

Number of BSP GPROCs (with redundancy) = 2.

Number of CSFP GPROC2s = 1.

Total number of GPROC2s for BSC= 17 (16 +1 for redundancy).

MSI requirements

Each MSI interfaces two E1 links.

Number of E1 links required at the BSC for interconnecting with RXCDR is:

(16 � 2 � 2 � 1812�4)�31 16

Hence number of MSIs required for BSC to RXCDR interface = 8.

Each BTS site in this example requires one E1 interconnect. Hence the number ofMSIs required for BTSs, is 30/2 = 15.

Total number of MSIs required at the BSC = 23.

KSW requirements

Number of TDM timeslots is given by:

N � (G * n) � (M * 64) � (R * 16)

Where G is the number of GPROC2s; M is the number of MSIs, and R is thenumber of XCDR/GDPs at the BSC:

N � 17 * 32 � 23 * 64 � 2016

Each KSW provides 1016 TDM timeslots. Hence, 2 non-redundant KSWs wouldbe required for this configuration. For redundancy, an additional 2 KSWs arerequired.

Total KSWs required (with redundancy) = 4.

BSU shelves

The number of BSU shelves required is the greater of the two calculations (sincewe have no local transcoding):

NBSU � G�8 � 17�8 3 BSU shelves

NBSU � (M � R)�12 � 23�12 2 BSU shelves

Ensure the following is true for each shelf:

N � (G * n) � (M * 64) � (R * 16) � 1016

Therefore, 3 BSU shelves are required to accommodate all the hardware neededfor this configuration.


30 Sep 20039�26


GMR-0168P02900W21-M

KSWX requirements

KSWX extends the TDM highway of a BSU to other BSUs and supplies clocksignals to all shelves in the multi-shelf configuration. KSWX maybe used inexpansion, remote and local modes. We require 3 BSU shelves with 4 nonredundant KSWs, which implies we shall have 2 expansion shelves and 1extension shelf.

Number of KSWX required is sum of KSWXE, KSWXR, and KSWXL .


NKXE = K*(K�1) = 2 *1 = 2 ( K is the number of non-redundant KSWs).

NKXR = SE = 1 ( SE is the number of extension shelves).

NKXL = K + SE = 3.

NK X = 2 + 1 + 3 = 6.

Therefore, the number of KSWX required (with redundancy) = 12.

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU.One GLCK is required at each BSC.

Number of GCLKs required (with redundancy) = 2.

CLKX requirements

Provides expansion of GCLK timing to more than one BSU. The number ofCLKXs required is given by:

NCLKX � ROUND UP(E�6) * (1 � RF)

Where E is the number of expansion/extension shelves and RF is the redundancyfactor:

NCLKX � ROUND UP(3�6) * (1 � 1) � 1

The number of CLKXs required (with redundancy) = 2.

LANX requirements

NLANX � NBSU * (1 � RF) � 3 * 2 � 6

Where RF it the redundancy factor.

Total number of LANXs required (with redundancy) = 6.

PIX requirements

PIX provides eight inputs and four outputs for site alarms:

PIX � 2 * NUMBER of BSUs � 6

Line interfaces

Number of T43s � Number of MSIs�3 � 23�3 8

The number of T43 boards required is 8.


30 Sep 2003


68P02900W21-M

GMR-019�27

Digital power supply requirements

Number of PSUs required is given by:

PSUs � NBSU * (2 � RF)

PSUs � 3 * (2 � 1) � 9

One redundant PSU is required for each BSU shelf, hence total number of PSUsrequired is 12.

BBBX requirements (optional)

BBBX � Number of BSUs for battery backup (recommended) � 3

Non volatile memory (NVM) board for BSC (optional)

NVM � 0 or 1


30 Sep 20039�28


GMR-0168P02900W21-M

Step 3 : RXCDR planning

Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharingand redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRsso that the signalling traffic and voice traffic is equally distributed over 2 RXCDRs, eachRXCDR would be dimensioned using the rules in the following text.

Determining the number of RXCDR to MSC links

Number of RXCDR to MSC links is given by:

NRXCDR�MSC � (C � X � T)�31

Where:

C is the number of MTL links required.X is the number of OML links required.T is the number of trunks between MSC and BSC.

NRXCDR�MSC � (16 � 2 � 1812)�31 � 60

Each XCDR card terminates one E1 interconnect, hence, number ofnon-redundant XCDR cards required is 60.

MSI requirements for RXCDR

As calculated in MSI requirements, the number of BSC�RXCDR links is 16 andeach MSI card interfaces 2 E1 links. Hence, 8 MSI cards are required on theRXCDR.

RXU shelves

The number of RXU shelves required is given by (assumes NVM board fitted):

NRXU � max�M�5, (R � NNVM)�16� � max(8�5, 61�16) 4


N � (G * n) � (M * 64) � (R * 16) � 1016

Hence, 4 RXU shelves are required to equip 58 XCDR cards and 8 MSI cards.

GPROC2 requirements for RXCDR

Each shelf should have minimum of one GPROC2. Hence, 4 non-redundantGPROC2s are required. If the operator chooses to use redundancy 8 GPROC2swould be required.

KSW requirements for RXCDR

The number of TDM slots required for GPROC2s, MSIs and XCDRs is given by:

TDM timeslots required � G * n � R * 16 � M * 64

TDM timeslots required � 8 * 32 � 8 * 64 � 60 * 16 � 1728

Each KSW provides1016 timeslots on the TDM highway, hence, 2 non-redundantKSWs are required for the RXCDR with this configuration.


30 Sep 2003


68P02900W21-M

GMR-019�29

KSWX requirements for RXCDR

Number of KSWXs required is sum of KSWXE, KSWXR, and KSWXL. We require4 RXU shelves with 2 non-redundant KSWs, which implies we shall have 1expansion shelf and 2 extension shelves.


NKXE � K * (K � 1) � 2 * 1 � 2

K is the number of non-redundant KSWs.

NKXR � SE � 2

SE is the number of extension shelves.

NKXL � K � SE � 4

NKX � 2 � 2 � 4 � 8

The number of KSWXs (with redundancy) = 16.

GCLK requirements

The generic clock generates all the timing reference signals required by an RXU.One GLCK is required at each RXCDR.


CLKX requirements

Provides expansion of GCLK timing to more than one RXU.


Where:

E is the number of expansion/extension shelves.

RF is the redundancy factor.

NCLKX � ROUND UP(4�6) � 1

The number of redundant CLKXs required is 2.

LANX requirements

Number of LANXs required is given by:

NLANX � NRXU * (1 � RF) � 4 * 2 � 8


Total number of LANXs required with redundancy = 8.

PIX requirements


PIX � 2 * Number of RXUs � 8

Hence, 8 PIX cards are required for the RXCDRs.


30 Sep 20039�30


GMR-0168P02900W21-M

Line interfaces

Number of T43s � Number of E1s�6 � (60 � 15)�6 13



PSUs � 2 * RXUs � 8

One redundant PSU is required for each RXU shelf, hence total number of PSUsrequired of is 12.


BBBX � Number of BSUs for battery backup (recommended) � 4

Non volatile memory (NVM) board for RXCDR (optional)

NVM � 1 (in this example)


30 Sep 2003


68P02900W21-M

GMR-019�31

Planning example 2

Dimension a network with following requirements:S GSM software release = GSR6 (Horizon II) .

S Number of sites 2/2/2 sites (BTS: M-Cell6) = 55.

S Number of omni 2 sites (BTS: M-Cell2) = 5.

Call modelS Call duration T = 100 s.

S Ratio of SMSs per call S = 0.12.

S Ratio of location updates per call = 2.4.

S Ratio of IMSI detaches per call I d = 0.2 (type 2).

S Location update factor L = 2.4 + 0.5 * 0.2 = 2.5.

S No. of handovers per call H = 2.6.

S Ratio of intra-BSC handovers to all handovers i = 0.6.

S Paging rate per second P = 8 pages per second.

S MTL link utilization = 35% (0.35).

S RSL link utilization U = 25% (0.25).

S CCCH utilization = 33%.

S Probability of blocking TCH PB�TCH < 2%.

S Probability of blocking SDCCH PB�SDCCH < 1%.


S Number of BTS sites B = 55 + 5 = 60.

S Number of cells at the BTS CBTS = 3.

S GSM paging rate in pages per second PGSM = 10.

S GPRS paging rate in pages per second PGPRS = 3.

S Mean_TBF_Rate = 1.

S Number of GPRS timeslots NGPRS = 0.

Other considerationsS Line interface type = E1.

S Network termination option = T43.

S Power voltage option = �48/�60 V dc.

S Type of combining used = Hybrid (CBF).

S Dedicated CSFP = YES.

S CSFP redundancy = NO.

S Redundancy for all other modules = YES.

S MTL links redundancy = YES.

S RSL link redundancy = NO.

S Coding schemes CS3 and CS4 used = NO.

S BTS connectivity = Star configuration.

S IMSI/TMSI paging = TMSI.

S MTL load balancing granularity = 64.

S NVM board fitted at RXCDR.


30 Sep 20039�32


GMR-0168P02900W21-M

GSR6 (Horizon II) limitations

S Max. BTS sites = 100.

S Max. BTS cells = 250.

S Active RF carriers = 512.

S Trunks = 3000.

S C7 links = 16.


30 Sep 2003


68P02900W21-M

GMR-019�33

Step 1 : Cell planning � control channel calculationsFrom Erlang B tables, the number of Erlangs supported by 16 TCHs (2 carrier cell) withGOS of 2% is 9.83 Erlangs.

Total Erlangs offered by a 2/2/2 BTS = 3 * 9.83 = 29.49 Erlangs.

Total Erlangs offered by an omni 2 BTS = 9.83 Erlangs.

2 carrier cell � determining the number of CCCHs

Call arrival rate:

lcall � e�T � 9.83�100 � 0.0983


lS � S * e�T � 0.12 * 9.83�100 � 0.012


lLU � L * e�T � 2.5 * 9.83�100 � 0.246



From the call model parameters, the paging rate PGSM is 8, so the averagenumber of CCCH blocks required to support paging only is:

NPCH � PGSM�(4 * 4.25) � 8�(4 * 4.25) � 0.471


NAGCH � lAGCH_GSM�(2 * 4.25) � 0.356�(2 * 4.25) � 0.042

Using a CCCH utilisation figure (UCCCH) of 0.33, the average number of CCCHblock required to support both PCH and AGCH is given by:


Assuming 1% blocking, the Erlang B tables show that 6 CCCHs are required. Thiscan be supported using a non-combined BCCH with 9 CCCH timeslots. It isrecommended to reserve 3 CCCH blocks for access grant messages.

Determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call modelparameters, the average number of SDCCHs, NSDCCH, is given by the formulamentioned in Chapter 3:


� 0.098 * 5 � 0.246 * (4 � 4) � 0.012 * (6 � 4) � 2.575

The number of SDCCHs to support an average number of busy SDCCHs of 2.575with less that 1% blocking as determined by use of Erlang B tables is 8. Hence,the number of timeslots required to carry SDCCH signalling traffic is 1 with thetimeslot offering 8 SDCCHs.

Determining the number of TCHs

Total number of signalling timeslots required for a 2 carrier configuration with thegiven call model parameters is 2 (1 non-combined BCCH timeslot with 9 CCCHsand 1 timeslot with 8 SDCCHs each).

Therefore, the number of traffic channels per 2 carrier cell = 16 � 2 = 14.

Hence, traffic offered by a 2-carrier cell is 8.2 Erlangs (14 channels at 2 % GOS).Carried Erlangs for the cells is 8.04 Erlangs.


30 Sep 20039�34


GMR-0168P02900W21-M

Step 2 : BSS planning � determining the number of RSLs

The number of 64 kbits/sec RSLs required with the given by:


n * (95 � 67 * S � 35 * H � 25 * L)1000 * U * T

�(47 � 3 * CBTS) * PGSM � (52 � CBTS) * PGPRS

8000 * U�

6 * Mean_TBF_Rate * NGPRS1000 * U

Where n is the number of TCHs under the BTS. Hence, for a 2/2/2 site (no GPRS):


14 * 3 * (95 � 67 * 0.12 � 35 * 2.6 � 25 * 2.5)1000 * 0.25 * 100

�(47 � 3 * 3) * 10 � (52 � 3) * 3

8000 * 0.25� 6 * 0

1000 * 0.25

� 0.79

The number of RSLs required per 2/2/2 site is 1 and for an omni 2 site also is 1(calculated in a similar way).

BSC to BTS E1 interconnect planning

Number of E1 links required between a BSC and BTS is given by:


31

(CS3 and CS4 are not used.)

Number of E1 links required between each 2/2/2 BTS and BSC:

� {(0 * 4) � (6 * 2) � 0} � 131

1

Number of E1 links required between each omni 2 BTS and BSC:

� {(0 * 4) � (2 * 2) � 0} � 131

1

Hence, only one E1 interconnect is required between each BTS and BSC for thegiven site configurations (provided they are in star configurations), giving a total of60 E1 links.


Number of LCF�RSLs required if given by:

GL3 �

�n * (1 � 0.35 * S � 0.34 * H * (1 � 0.4 * i) � 0.32 * L)(19.6 * T)

� (0.00075 * PGSM � 0.004) * B � C120�

Where, n is the number of TCHs under a BSC:

�2380 * (1 � 0.35 * 1.12 � 0.34 * 2.6 * (1 � 0.4 * 0.6) � 0.32 * 2.5)(19.6 * 100)

� (0.00075 * 8 � 0.004) * 60 � 170120�

The number of LCFs for RSL processing is 6.


30 Sep 2003


68P02900W21-M

GMR-019�35

Determining the number of MTLs

Total Erlangs offered by the BSC with 55 sites with 2/2/2 configuration and 5 omni2 sites:

� 55 * 3 * 8.2 � 5 * 8.2 � 1394 Erlangs

Total Erlangs carried by the BSC with 55 sites with 2/2/2 configuration and 5 omni2 site:

� 55 * 3 * 8.04 � 5 * 8.04 � 1366.8 Erlangs

The number of trunks required to carry traffic on the A-interface with less than 1%blocking is 1423. Check figure is within limits.

Number of pages per call:

Ppc � PGSM * T�N � 8 * 100�1423 � 0.57

Using the call model parameters, the number of MTLs can be calculated usingformulae mentioned in Chapter 5 of this manual.

Maximum number of Erlangs supported by a C7 link is given by:

nlink �(1000 * U * T)

(40 � 47 * S � 22 * H * (1 � 0.8 * i) � 24 * L � 9 * PPC)

nlink �(1000 * 0.25 * 100)

(40 � 47 * 0.12 � 22 * 2.6 * (1 � 0.8 * 0.6) � 24 * 2.5 � 9 * 0.57)

� 178 Erlangs

Maximum number of Erlangs supported by GPROC2 supporting a C7 signallinglink is given by:


(1 � 0.16 * S � 0.5 * H * (1 � 0.6 * i) � 0.42 * L � PPC * (0.005 * B � 0.05))

nlLCF�MTL �(20 * 100)

(1 � 0.16 * 0.12 � 0.5 * 2.6 * (1 � 0.6 * 0.6) � 0.42 * 2.5 � 0.57 * (0.005 * 60 � 0.05))

� 646 Erlangs

Hence:nlmin � min(nlink , nlLCF�MTL) � 178 Erlangs

Amount of traffic (or number of trunks) each logical link will hold:

Nlogical � 1423�64 � 22.23

using a MTL load sharing granularity of 64.

The number of logical links each MTL can handle:

nlog_per_mtl � round down(178�22.23) 8

The number of required MTLs:

mtls � round up(64�8) � 8

Check this figure is within limits.

Determining the number of LCFs for MTL processing

Using the formula mentioned in Chapter 5, since:

2 * nlink � nlLCF�MTL

NLCF � ROUND UP �82�� 4


30 Sep 20039�36


GMR-0168P02900W21-M

XBL requirements

Referring to Table 5-12 in Chapter 5,

Number of XBLs required = 2.

GPROC requirements

Number of GPROC2s required for MTL processing = 4.

Number of GPROC2s required for RSL processing = 5.

Total number of LCF GPROC2s required = 9. Check this figure is within limits.

Number of BSP GPROCs (with redundancy) = 2.

Number of CSFP GPROC2s = 1.

Total number of GPROC2s for BSC = 13 (12 +1 for redundancy).

MSI requirements

Each MSI interfaces two E1 links.

Number of E1 links required at the BSC for interconnecting with the RXCDR is:

(8 � 2 � 2 � 1423�4)�31 12

without redundancy.

Hence the number of MSIs required for BSC to RXCDR interface = 6.

Each BTS site in this example requires one E1 interconnect. Hence the number ofMSIs required for BTSs is 60/2 = 30.

Total number of MSIs required at the BSC = 36.

KSW requirements

Number of TDM timeslots is given by:

N � (G * n) � (M * 64) � (R * 16)

Where G is the number of GPROC2s; M is the number of MSIs, and R is thenumber of GDP/XCDRs in the BSC.

N � 13 * 32 � 36 * 64 � 2720

Each KSW provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs wouldbe required for this configuration. For redundancy, 3 additional KSWs are required.

Total KSWs required (with redundancy) = 6.

BSU shelves

The number of BSU shelves required is the greater of the two calculations (sincewe have no local transcoding):

NBSUG�8 � 13�8 2 BSU shelves

NBSU(M� R)�12 � 36�12 3 BSU shelves


N � (G * n) � (M * 64) � (R * 16) � 1016

Therefore, 3 BSU shelves are required to accommodate all the hardware neededfor this configuration.


30 Sep 2003


68P02900W21-M

GMR-019�37

KSWX requirements

KSWX extends the TDM highway of a BSU to other BSUs and supplies clocksignals to all shelves in the multi-shelf configuration. The KSWX maybe used inexpansion, remote and local modes. We require 3 BSU shelves with 3 master/redundant KSWs, which implies 2 expansion shelves.

Number of KSWXs required is sum of KSWXE, KSWXR, and KSWXL:


NKX = NKXE + NKXR + NKXL.

NKXE = K*(K�1) = 3 *2 = 6 ( K is the number of non-redundant KSWs).

NKXR = SE = 0 ( SE is the number of extension shelves).

NKXL = K + SE = 3.

NK X = 6 + 0 + 3 = 9.

The number of KSWX required (with redundancy) = 18.

GCLK requirements

The generic clock generates all the timing reference signals required by a BSU.One GLCK is required at each BSC.


CLKX requirements

Provides expansion of GCLK timing to more than one BSU. Number of CLKXsrequired is given by:


Where E is the number of expansion/extension shelves and RF is the redundancyfactor.

NCLKX � ROUND UP(3�6) * (1 � 1) � 2

The number of CLKX required (with redundancy) = 2.

LANX requirements

NLANX � NBSU * (1 � RF) � 3 * 2 � 6

Where, RF it the redundancy factor.

Total number of LANXs required (with redundancy) = 6.

PIX requirements


PIX � Number of BSUs � 6

Line interfaces

Number of T43s � Number of MSIs�3 � 36�3 12



30 Sep 20039�38


GMR-0168P02900W21-M


The number of PSUs required is given by:

PSUs � NBSU * (2 � RF)

PSUs � 3 * (2 � 1) � 9

One redundant PSU is required for each BSU shelf, hence total number of PSUsrequired is 9.


BBBX = Number of BSUs for battery backup (recommended) = 3.

Non volatile memory (NVM) board for BSC (optional)

NVM � 0 or 1


30 Sep 2003


68P02900W21-M

GMR-019�39

Step 3 : RXCDR planning

Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharingand redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRsso that the signalling traffic and voice traffic is equally distributed over 2 RXCDRs, eachRXCDR would be dimensioned using the rules in the following text.

Determining the number of RXCDR to MSC links

Number of RXCDR to MSC links is given by:

NRXCDR�MSC � (C � X � T)�31

Where:

C is the number of MTL links required.

X is the number of OML links required.

T is the number of trunks between MSC and BSC.

NRXCDR�MSC � (16 � 2 � 1423)�31 � 47

Each XCDR card terminates one E1 interconnect.

Hence, the number of non-redundant XCDR cards required is 47.

MSI Requirements for RXCDR

As calculated in MSI requirements, the number of BSC�RXCDR links is 12.Each MSI card interfaces 2 E1 Links, hence, 6 MSI cards are required on theRXCDR.

RXU shelves

The number of RXU shelves required is given by (assumes an NVM board isfitted):

NRXU � max(M�5, (R � NNVM)�16) � max(6�5, (47 � 1)�16) 3


N � (G * n) � (M * 64) � (R * 16) � 1016

Hence, 3 RXU shelves are required to equip 47 XCDR cards and 6 MSI cards.

GPROC2 requirements for RXCDR

Each shelf should have minimum of one GPROC2. Hence, 3 non-redundantGPROC2s are required. If the operator chooses to use redundancy 6 GPROC2swould be required.

KSW requirements for RXCDR

Number of TDM slots required for the GPROC2s, MSIs and XCDRs is given by:

TDM timeslots required � G * n � M * 64 � R * 16

TDM timeslots required � 6 * 32 � 6 * 64 � 47 * 16 � 1328

Each KSW provides1016 timeslots on the TDM highway, hence, 2 non-redundantKSWs are required for RXCDR with this configuration.


30 Sep 20039�40


GMR-0168P02900W21-M

KSWX requirements for RXCDR

The number of KSWXs required is the sum of KSWXE, KSWXR, and KSWXL. Theabove calculations imply 1 expansion and 1 extension shelf are required.


NKXE � K * (K � 1) � 2 * 1 � 2

K is the number of non-redundant KSWs.

NKXR � SE � 1

SE is the number of extension shelves.

NKXL � K � SE � 3

NKX � 2 � 1 � 3 � 6

The number of KSWXs (with redundancy) = 12.

GCLK requirements

The generic clock generates all the timing reference signals required by an RXU.One GLCK is required at each RXCDR.


CLKX requirements

Provides expansion of GCLK timing to more than one RXU:


Where:

E is the number of expansion/extension shelves.

RF is the redundancy factor.

NCLKX � ROUND UP(2�6) * (1 � 1) � 2

The number of redundant CLKXs required is 2.

LANX requirements

Number of LANXs required is given by:

NLANX � NRXU * (1 � RF) � 3 * 2 � 6


Total number of LANXs required with redundancy = 6.

PIX requirements


PIX � 2 * Number of RXUs � 6

Hence, 6 PIX cards are required for RXCDR.


30 Sep 2003


68P02900W21-M

GMR-019�41

Line interfaces

Number of T43s � Number of E1s�6 � (47 � 12)�6 10



PSUs � 2 * RXUs � 6

One redundant PSU is required for each RXU shelf, hence total number of PSUsrequired is 9.


BBBX = Number of BSUs for battery backup (recommended) = 3.

Non volatile memory (NVM) board for RXCDR (optional)

NVM � 1 (in this example)

GSR6 (Horizon II)A planning example of BSS support for LCS provisioning

30 Sep 20039�42


GMR-0168P02900W21-M

A planning example of BSS support for LCS provisioning

Introduction to the LCS planning example

A planning example for when LCS is used is provided here. This example is based oninformation provided in Chapter 8.


Use this example to plan the equipment of a BSC supporting a traffic model with theparameters listed in Table 9-10 and their typical values. This indicates a largeconfiguration with 64 sites/BSC, 3 cells/BTS and 2 carriers/cell.

Table 9-10 Typical LCS call model parameters

Parameter Value

Maximum trunks between MSC and BSC N=3000

Number of BTSs per BSS 28 4*4*4 sites and 2 omni 2 sites

Number of cells per BSS 28*3+2

Call duration T = 75 s

Call rate [call/sub/BH] Call_Sub_Rate = 1

LCS penetration rate [%] Lcs = 5%

LCS request rate2: [req/sec/BSC] LCS_BSC_Rate = 2

Link utilization factor UMSC_BSC 0.35

Link utilization factor U BSC_BTS 0.25

GSR6 (Horizon II) A planning example of BSS support for LCS provisioning

30 Sep 2003


68P02900W21-M

GMR-019�43

LCS planning example calculations

Step 1: Determine LCS architectureBSS�based LCS architecture will be supported.

Step 2: Calculate MTLs (actually needed trucks number is 1812)

nlink_bss �


=

(1000 * 0.35 * 75)(40 � 47 * 0.1 � 22 * 2.5 * (1 � 0.8 * 0.6) � 24 * 2 � 31 * 0.05) � 9 * 0.124 * (1 � 0.05)

= 151.486

nlLCF�MTL �

(20 * T)(1 � 0.16 * S � 0.5 * H * (1 � 0.6 * i) � 0.42 * L � 0.45 * LCS) � PPC * (0.005 * B � 0.05) * (1 � LCS)

=

(20 * 75)(1 � 0.16 * 0.1 � 0.5 * 2.5 * (1 � 0.6 * 0.6) � 0.42 * 2 � 0.45 * 0.05) � 0.124 * (0.005 * 56 � 0.05) * (1 � 0.05)

= 559.268

nlmin � MIN (nlink, nlLCF_MTL) � 151.468

Nlogical � NNg

� 181264

� 2831


Nlogical� � 5

Finally, the number of required MTLs with 64 logical links is:


� � 13

Step 3: Calculate MTL LCFs

NLCF_MTL �132

� 6

Step 4: Calculate RSLsAccording to Chapter 3, TCHs per BTS is 29*3. Then,

RSLGSM@64k �

n * (49 � 50 * S � 32 * H � 20 * L � LCS * 24)1000 * U * T

�(27 � 3 * C) * PGSM * (1 � LCS)

8000 * U

=

87 * (49 � 50 * 0.1 � 32 * 2.5 � 20 * 2 � 0.05 * 24)1000 * 0.25 * 120

� (27 � 3 * 3) * 3 * (1 � 0.05)8000 * 0.25

= 0.87

GSR6 (Horizon II)A planning example of BSS support for LCS provisioning

30 Sep 20039�44


GMR-0168P02900W21-M

Step 5: Calculate RSL LCFs

GL3 �

�n * (1 � 0.35 * S � 0.34 * H * (1 � 0.4 * i) � 0.32 * L � 0.45 * LCS)

(19.6 * T)� (0.004 � 0.00075 * PGSM * (1 � LCS)) * B �

C120�

=

�3000 * (1 � 0.35 * 0.1 � 0.34 * 2.5 * (1 � 0.4 * 0.6) � 0.32 * 2 � 0.45 * 0.05)

(19.6 * 120)� (0.004 � 0.00075 * 1.05 * 3) * 30 �

86120�

= 3.90

So the RSL LCFs number is 4.

Step 5: Calculate LMTLs

LMTL � ROUND UP �LCS_BSC_Rate * 191000 * UBSC_SMLC

�� ROUND UP � 2 * 19

1000 * 0.2�

= 1

Step 6: Calculate LMTL LCFs

NLCF_LSL = 1.

30 Sep 2003


68P02900W21-M

GMR-0110�1

Chapter 10

Location area planning

GSR6 (Horizon II)

30 Sep 200310�2


GMR-0168P02900W21-M

GSR6 (Horizon II) Location area planning overview

30 Sep 2003


68P02900W21-M

GMR-0110�3

Location area planning overview

Introduction to location area planning

This chapter provides, by example, a description of location area planning. This exerciseshould be undertaken by each operator to optimize the network configurations based onthe paging load on the BSC.

Location area planning considerations

Prior to the GSR4 BSS software release, the traffic handled by the BSC was limited bythe number of BTSs and carriers that could be handled by the BSC. Increasing BSCcapacities have an impact on some of the call model parameters, especially the pagingload on the BSC.

Since an MS is paged in a location area, paging rate depends on the number and size ofBSCs in that location area. If there are too many BSCs in a location area, each with largenumber of BTS sites and high traffic handling capacity, it results in high paging load oneach of the BSCs in that location area. This leads to more hardware (GPROC2�LCFs)having to be equipped on each BSC. It might be considered prudent at this stage tobreak up the location area to have fewer of BSCs and consequently, less paging load.Increasing the number of location areas however, would increase the number of locationupdates on the cells bordering the location area. More SDCCHs have to be provisionedfor this increased signalling on the border cells and hence, fewer channels are availablefor traffic.

A well planned network should have similar paging loads in each location area. A verysmall paging load would suggest that the location area is too small and could becombined with neighbouring location areas, minimising location update activity andreducing use of SDCCH resources. A paging load too close to the theoretical maximumpaging load (calculated using the number of PCHs used and if mobile is paged usingIMSI or TMSI) would suggest that the location area is too large and should be split intomultiple location areas, to avoid paging overload and the need for extra hardware.

This exercise should be undertaken by each operator to optimise the networkconfigurations based on the paging load on the BSC. This topic is explained further, withan example, in the following text.

GSR6 (Horizon II)Location area planning calculations

30 Sep 200310�4


GMR-0168P02900W21-M

Location area planning calculations

Example procedure

Assume a network with four BSCs under a location area (see Figure 10-1) each withfollowing call model parameters:

S Call duration T = 90 s.

S No. of SMSs per call S = 0.05.

S No. of location updates per call = 2.

S IMSI detaches per call Id = 0.2 (type 2).

S Location update factor = 2 + 0.5*0.2 = 2.1.

S No. of handovers per call H = 2.

S Number of intra�BSC handovers to all handovers i = 0.4.

S MTL link utilisation = 20%.

S RSL link utilisation = 25%.

S CCCH utilisation = 33%.

S Probability of blocking TCH P B�TCH < 2%.

S Probability of blocking SDCCH P B�SDCCH < 1%.


S Paging repetition = 1.2.

S Ratio of incoming calls to total call = 0.25.

Further assume that each of the BSC handles about 1200 Erlangs (48 sites with 2/2/2configurations and 2 sites with omni 2 configuration) of traffic.

Figure 10-1 Four BSCs in one LAC

ig.069.rh

MSC

BSC BSC BSC BSC

LAC=1

GSR6 (Horizon II) Location area planning calculations

30 Sep 2003


68P02900W21-M

GMR-0110�5

The paging rate in the location area can be calculated by:

P � paging_repitition * % of incoming calls * total calls in the LA �

1.2 * 0.25 * (1200 � 1200 � 1200 � 1200)�60 � 24 pages per second

Now, calculate the number of GPROC LCF�RSLs required with this paging load usingthe formula detailed in Chapter 5:

(2044 * (1 � 0.42 * 0.05 � 0.45 * 2 * (1 � 0.4 * 0.4) � 0.36 * 2.1))�(23.2 * 90) �

(0.00072 * 24 � 0.004) * 50 � 148�120 � 4.77

The number of GPROC2s required for RSL is 5.

Since most of the cells in the BSC are non-border cells, the location updates per cell isaround 2. Based on this figure, calculate the number of SDCCHs required for each cell.

From Erlang B tables, number of Erlangs supported by 16 TCHs (2 carrier cell) with GOSof 2% is 9.83 Erlangs.

Using the formulae for control channel calculations, as provided in Chapter 3:

Call arrival rate:

lcall � e�T � 9.83�60 � 0.164


lS � S * e�T � 0.05 * 9.83�60 � 0.008


lLU � L * e�T � 2.1 * 9.83�60 � 0.344

The average number of SDCCHs, NSDCCH is given by:

NSDCCH � lcall * TC � lLU * (TL � Tg) � lS * (TS � Tg)

� 0.164 * 5 � 0.344 * (4 � 4) � 0.008 * (6 � 4) � 3.653

The number of SDCCHs to support an average number of busy SDCCHs of 2.435, withless that 1% blocking as determined by use of Erlang B tables, is 7. Hence the number oftimeslots required to carry SDCCH signalling traffic is 1 with each timeslot offering 8SDCCHs.

Now, use the same call model parameters and divide the location area so that eachlocation area contains two BSCs (see Figure 10-2). Dividing the location area into twolocation areas increase the location updates on the border cells. Assume that 25% of thecells under a BSC become border cells (a conservative estimate) and the number oflocation updates per call go up to 6 on cells on the location area border. The averagenumber of location updates per call for the BSC would approximately equal 3 (0.25*6 +0.75*2).

GSR6 (Horizon II)Location area planning calculations

30 Sep 200310�6


GMR-0168P02900W21-M

Figure 10-2 Four BSCs divided into two LACs

ig.068.rh

MSC

BSC BSC BSC BSC

LAC = 1 LAC = 2

Location update factor:

L � 3 � 0.5 * 0.2 � 3.1

Since the location area now has two BSCs, the paging rate is given by:

Paging Rate � 1.2 * 0.25 * (1200 � 1200)�60 � 12 pages�second

The number of LCF�GPROC2s required for RSL (using the formula) = 4.70 = 5.

Call arrival rate:

lcall � e�T � 9.83�60 � 0.164


lS � S * e�T � 0.05 * 9.83�60 � 0.008


lLU � L * e�T � 6.1 * 9.83�60 � 0.999

The average number of SDCCHs for border cells, NSDCCH is given by :

NSDCCH � lcall * TC � lLU * (TL � Tg) � lS * (TS � Tg)

� 0.164 * 5 � 0.999 * (4 � 4) � 0.008 * (6 � 4) � 8.895

The number of SDCCHs to support an average number of busy SDCCHs of 5.93 withless than 1% blocking as determined by use of Erlang B tables, is 13. Hence the numberof timeslots required to carry SDCCH signalling traffic is 2, with each timeslot offering 8SDCCHs.

If the network planner is careful enough to divide the location area such that not toomuch traffic crosses the border of the location area (resulting in a lower number oflocation updates), even less resources might be required of the air interface for locationupdate signalling.

30 Sep 2003


68P02900W21-M

GMR-0111�1

Chapter 11

Deriving call model parameters

from network statistics

GSR6 (Horizon II)

30 Sep 200311�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-0111�3

Chapter overview

Introduction to deriving call model parameters

This chapter describes the derivation of call model parameter values from the GSMnetwork statistics collected at the OMC-R. Most of the calculations used for equipmentplanning use the standard call model parameters. Each network behaves uniquely, andoperators must compute their own set of call model parameter values for a network,based on the performance statistics collected at the OMC-R. This will help optimize theconfigurations on a network.

All the statistics used for determining the call model parameters must be collected duringbusy hours and averaged over a reasonable period of time (three months or more).

The call model parameters calculated should be averaged over the entire network or atthe BSC level for equipment dimensioning purposes. This would give more scope ofaveraging out the load from the network entities.

GSR6 (Horizon II)Deriving call model parameters from network statistics

30 Sep 200311�4


GMR-0168P02900W21-M

Deriving call model parameters from network statistics

Standard call model parameters

Table 11-1 lists the standard call model parameters.











Ratio of LCSs per call Lcs = 0.2


Mobile orginated LCS ratio LRMO = 0.05







GPRS parameters










GSR6 (Horizon II) Deriving call model parameters from network statistics

30 Sep 2003


68P02900W21-M

GMR-0111�5


L is a function of l, I and whether short message sequence (type 1) or long messagesequence (type 2) is used for IMSI detach. Typically I = 0 (disabled), but when it is enabled:

Type 1: L = I + 0.2 * IType 2: L = I + 0.5 * I

Call duration (T)

Average call duration for a network may be derived from the statisticsBUSY_TCH_MEAN and TOTAL_CALLS using the following formula:

T �

�Ni�1

(BUSY_TCH_MEAN) * stat_interval_in_sec

�Ni�1

(TOTAL_CALLS � ASSIGNMENT_REDIRECTION)

Where: N is: the number of cells under theBSC.

BUSY_TCH_MEAN the average number of busy TCHsin the cell and is updated eachtime an allocation or de-allocationof a TCH occurs. It provides amean value indicating the averagenumber of TCHs in use. The timerecorded for a TCH in use includesthe guard time (T3111), which isthe time allowed between ending acall and being allowed to startanother call.

TOTAL_CALLS the number of circuit oriented callsthat are originated in the cell. It ispegged only once per connectionat the time of the first successfulTCH assignment procedure.Subsequent channel changes arenot counted.

ASSIGNMENT_REDIRECTION the total number of assignmentsthat were redirected to anothercell, due to redirected retryhandover procedure, multibandband re-assignment procedure, orhandover during assignmentprocedure.

stat_interval_in_sec the interval in which statistics arecollected. It is 3600 if the statisticinterval is one hour and 1800 if thestatistic interval is 30 minutes.

Call duration (T) in the above formula is calculated for one cell and should be calculatedas an average of call durations of all the BSCs in the network.

NOTE The ASSIGNMENT_REDIRECTION statistic is only availablefrom software release GSR5 onwards.


30 Sep 200311�6


GMR-0168P02900W21-M

Ratio of SMSs per call (S)

The number of SMSs per call, may be calculated using the SMS related statisticsparameters in the following formula:

S �

�Ni�1

(SMS_NO_BCAST_MSG � SMS_INT_ON_SDCCH � SMS_INIT_ON_TCH)

�Ni�1



SMS_NO_BCAST_MSG the number of times a message isbroadcast on the CBCH.

SMS_INIT_ON_SDCCH the number of times an SMStransaction occurred on a SDCCH.

SMS_INIT_ON_TCH the number of times an SMStransaction occurred on a TCH.


The ratio of SMSs per call must be averaged over all the BSCs in the network.


30 Sep 2003


68P02900W21-M

GMR-0111�7

Ratio of handovers per call (H)

Handovers may be inter-BSS, intra-BSS or intra-cell. Therefore, the number ofhandovers per call may be calculated using the following formula:

H �

�Ni�1

(out_inter_bss_req_to_msc � out_intra_bss_ho_atmp � intra_cell_ho_atmp)

�Ni�1



out_inter_bss_req_to_msc the number of outgoing inter-BSShandover requests to the MSC.

out_intra_bss_ho_atmpt the number of times assignmentcommand is sent to an MS toinitiate an outgoing intra-BSShandover attempt.

intra_cell_ho_atmpt the number of times anassignment command is sent to anMS to initiate an intra-cellhandover attempt.


H should be averaged over all the BSCs in the network.

NOTE The TOTAL_CALLS parameter is the count of the totalcircuit-switched calls in a cell. It should be summed for all thecells in the BSC, when used in the previous formula.

Ratio of intra BSS handovers to all handovers (i)

Using the statistics previously detailed, this ratio can be calculated for a cell as follows:

i �

�Ni�1

(out_intra_bss_ho_atmpt � intra_cell_ho_atmp)

�Ni�1

out_inter_bss_req_to_mac � out_intra_bss_ho_atmpt � intra_cell_ho_atmp)


i should be averaged over all the cells in the network.


30 Sep 200311�8


GMR-0168P02900W21-M

Ratio of location updates per call (I)

The ratio of location updates per call, for a cell, may be calculated using the followingformula:

I �

�Ni�1

OK_ACC_PROC[location update]

�Ni�1



OK_ACC_PROC[location_update] counts the number of MSrequests for location updates.

ASSIGNMENT_REDIRECTION counts the total number ofassignments that wereredirected to another cell, due toredirected retry handoverprocedure, multiband bandre-assignment procedure, orhandover during assignmentprocedure.

I ratio should be averaged over all the BSCs in the network.

Ratio of IMSI detaches per call (I)

IMSI detaches is 0 if disabled. If enabled, it may be calculated per cell as follows:

I �

�Ni�1

OK_ACC_PROC[imsi_detach]

�Ni�1



OK_ACC_PROC[imsi_detach] counts the number of MSrequests for IMSI detach.

ASSIGNMENT_REDIRECTION counts the total number ofassignments that wereredirected to another cell, due toredirected retry handoverprocedure, multiband bandre-assignment procedure, orhandover during assignmentprocedure.

I should be averaged over all the BSCs in the network.


30 Sep 2003


68P02900W21-M

GMR-0111�9


The location update factor is calculated using the ration of location updates per call (l)and the ratio of IMSI detaches per call (I). For networks with IMSI detach disabled, thelocation update factor equals the ratio of location updates per call (l).

If IMSI detach is enabled, then depending on whether short message sequence (type 1)or long message sequence (type 2) is used, L may be calculated as:

S L = l (IMSI detach disabled, i.e. I = 0 )

S L = l + 0.2* I (type 1)

S L = l + 0.5* I (type 2)

IMSI detach types have to do with the way the MSC clears the connection with the BSSafter receiving the IMSI detach. When using IMSI detach type 1, the MSC clears theSCCP connection, a clearing procedure that involves only one uplink (average size of42 bytes) and one downlink message (average size of 30 bytes). When using IMSIdetach type 2, the MSC sends the CLEAR COMMAND and the BSS sends CLEARCOMPLETE, etc., which involves three uplink (average size of 26 bytes) and threedownlink messages (average size of 30 bytes). A location update procedure itself takesfive downlink messages (average size of 30 bytes) and six uplink messages (averagesize of 26 bytes).

Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number ofmessages as a location update and a IMSI detach (type 2) takes 6/11 (approximately0.5) of the messages of a location update.

Paging rate (PGSM)

PAGE_REQ_FROM_MSC counts the number of paging messages received by the BSSfrom the MSC during the statistics time interval. The paging message is then sent to theBSS in an attempt to locate a particular MS. Each message refers to only one MS. TheBSS In turn will transmit a paging message over the PCH, which may include identitiesfor more than one MS (two MSs if paged using IMSI and four if using TMSI).

An MS is paged in a location area, which may encompass multiple BSCs. It might alsobe possible to have multiple location areas within a BSC. The paging rate, therefore,would be a summation of the paging messages sent to each location area in a BSC,averaged over the interval period. Since PAGE_REQ_FROM_MSC is kept on a per cellbasis, the value of this counter for any cell in that location area for a given statisticsinterval, would denote the pages in the location area in that statistics interval time.

PGSM �

�Ni�1

(PAGE_REQ_FROM_MSC)

stat_interval_in_seconds [ith location area in BSC]

Where: PAGE_REQ_FROM_MSC is: the number of paging messagesreceived from the MSC by theBSS. This statistic is peggedwhen a paging message isreceived pertaining to the cell inwhich the MS is paged.


30 Sep 200311�10


GMR-0168P02900W21-M

Pages per call (PPC)

Pages per call for a BSC may be calculated as:

Ppc �

�Ni�1

PAGE_REQ_FROM_MSC

�Ni�1


Where: N is: the number of cells under the BSC.

Alternatively, pages per call may be calculated using the formula:

Ppc � PGSM * T�N

Where: N is: the number of MSC�BSC trunks.

T the call duration, in seconds.

Or:

Ppc � PGSM * T�e

Where: e is: the BSC Erlang.

Sample statistic calculations

Table 11-2 shows a sample of statistics collected for one BTS in the BSC for a one hourinterval.

Table 11-2 Sample statistics

Statistic Parameter Cell 1 Cell 2 Cell 3

BUSY_TCH_MEAN 9.25 14.94 24.12

TOTAL_CALLS 571 927 1407

SMS_NO_BCAST_MSG 0 0 0

SMS_INIT_ON_SDCCH 0 15 5

SMS_INIT_ON_TCH 0 2 0

out_inter_bss_req_to_msc 531 1214 141

out_intra_bss_ho_atmpt 512 747 1844

intra_cell_ho_atmpt 0 0 0

OK_ACC_PROC[location_update] 746 1056 268

OK_ACC_PROC[imsi_detach] 28 49 76

PAGE_REQ_FROM_MSC 43696 43696 43696

ASSIGNMENT_REDIRECTION 0 0 0

Using the formulae detailed in the previous sections, call model parameters can becalculated as follows:


30 Sep 2003


68P02900W21-M

GMR-0111�11

Call duration (T)Call duration is given by:

T �

�Ni�1

BUSY_TCH_MEAN * stat_interval_in_sec

�Ni�1

(TOTAL_CALLS_ � ASSIGNMENT_REDIRECTION

T=(9.25+14.94+24.12)*3600/(571+927+1407) + 0 + 0 + 0

The average call duration for this BSC = 59.86.

Likewise, call durations for all the cells in the BSC can be calculated. The call durationvalue used for dimensioning purposes should be the average of call durations over all theBSCs in the network.

No. of SMSs per call (S)

The number of SMSs per call is given by:

S �

�Ni�1

(SMS_NO_BCAST_MSG � SMS_INIT_ON_SDCCH � SMS_INIT_ON_TCH)

�Ni�1

TOTAL_CALLS � ASSIGNMENT_REDIRECTION

S = [(0+0+0)+(0+15+2)+(0+5+0)]/(571+927+1407)=0.0075

Ratio of handovers per call (H)The ratio of handovers per call is given by:

H �

�Ni�1

(out_inter_bss_req_to_msc � out_intra_bss_ho_atmpt � intra_cell_ho_atmpt)

�Ni�1


H=[(531+512+0)+(1214+747+0)+(141+1844+0)] / (571+927+1407+0+0+0)=1.717

Ratio of intra-BSS handovers to all handovers (i)Using the statistics previously detailed, this ratio can be calculated for a BSS as follows:

i �

�Ni�1

(out_intra_bss_ho_atmpt � intra_cell_ho_atmp)

�Ni�1

(out_inter_bss_req_to_msc_ � out_intra_bss_ho_atmpt_ � intra_cell_ho_atmpt)

[(512+0)+(747+0)+(1844+0)] / [(531+512+0)+(1214+747+0)+(141+1844+0)]=0.562

Number of location updates per call (l)Location updates per call may be calculated as:

l �

�Ni�1

(OK_ACC_PROC[location_update])

�Ni�1


l = (746+1056+268) / (571+927+1407) + 0 + 0 + 0 = 0.712


30 Sep 200311�12


GMR-0168P02900W21-M

IMSI detaches per call (I)

The number of IMSI detaches per call is given by:

I �

�Ni�1

(OK_ACC_PROC[imsi_detach])

�Ni�1


I = (28+49+76) / (571+927+1407 +0 +0 + 0) = 0.052


The location update is given by:

L � l � 0.5 * I

L = 0.712 + 0.5 * 0.052 = 0.738

Paging Rate (PGSM) for a BSC

The paging rate for a BSC (with multiple location areas) can be calculated as:

PGSM �SI (PAGE_REQ_FROM_MSC)

stat_interval_in_seconds[ith location area]

Since, in this case the BSC has only one location area, PGSM is given by:

PGSM � 43696�3600 � 12.13 pages per second

All call model parameters should be calculated by taking an average over all the BSCs inthe entire network.

This example illustrates the computation of call model parameters from the networkstatistics obtained from the OMC-R. As previously mentioned, It is recommended thatstatistics collected at busy hours over a long period of time (a couple of months) are usedfor all calculation purposes.

30 Sep 2003


68P02900W21-M

GMR-0112�1

Chapter 12

Standard BSS and Horizon BTS

configurations

GSR6 (Horizon II)

30 Sep 200312�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-0112�3

Chapter overview

BSS/BTS equipment covered

This chapter provides diagrams of the logical interconnections of the components invarious standard BSS and Horizon BTS site configurations, for macrocell and microcellsystems. Typical RF configurations are also provided.

Older generation (M-Cell) BTS site / RF configurations are provided in Chapter 13.

This chapter contains the following information:

S Typical BSS configurations.

S Single cabinet BTS configurations.

� One cabinet Horizon II macro configurations.

� One cabinet Horizonmacro configurations.

S Two cabinet BTS configurations.

� Two cabinet Horizon II macro configurations.

� Two cabinet Horizonmacro configurations.

S Three cabinet BTS configurations.

� Three cabinet Horizon II macro configurations.

� Three cabinet Horizonmacro configurations.

S Four cabinet BTS configurations.

� Four cabinet Horizon II macro configurations.

� Four cabinet Horizonmacro configurations.

S Horizon macrocell RF configurations.

S Horizon microcell RF configurations.

S Connecting Horizon II macro BTSs to Horizonmacro BTSs.

S Connecting Horizon II macro BTSs to M-Cell6 BTSs.

GSR6 (Horizon II)Standard configurations

30 Sep 200312�4


GMR-0168P02900W21-M

Standard configurations

Introduction to standard configurations

The examples in this section are shown with individual antennas for transmit and receivesignals. Duplexers will be required if individual antennas are not used. 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 typicalconfiguration using that specific equipment. Rather, they are meant to highlight theconfigurations that, within the constraints of the BSS architecture, are feasible when themacrocell hardware is deployed in a digital equipment shelf controlled BTS. Thediagrams also show possible cabinet boundaries. Cabinet designs, however, allow for anumber of different arrangements of the same configuration.

Rather than showing redundancy for all Horizon II macro/Horizonmacro BTSconfigurations, the control redundancy is depicted only for one Horizon II macro/Horizonmacro cabinet diagram (see Figure 12-4 and Figure 12-5).

GSR6 (Horizon II) Typical BSS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�5

Typical BSS configurations

BSC with 24 BTSs

The digital module configuration for a BSC controlling 24 BTSs is shown in Figure 12-1.

Figure 12-1 BSC controlling 24 BTSs

2 Mbit/s LINKS

2 Mbit/s LINKS

DUAL SERIAL BUSDUAL MCAP BUS

DUAL MCAP BUS

DUAL SERIAL BUS

BSU SHELF 1

GPROC0

DUAL IEEE LAN

DUAL TDM HIGHWAY BUS

MSI0

BTS 1

MSI1

BTS 2

MSI2

BTS 3

MSI7

BTS 12

RMTKSWX

A

GPROC3

GPROC1

GCLK

CLKX

BSSC CABINET

LCLKSWX

B

LCLKSWX

B

BTC

BTC

BTC

BSU SHELF 2

GPROC2

MSI2

MSI1

MSI0

MSI6

LCLKSWX

A

KSWB

REDUNDANT

GCLK

REDUNDANT

FIBRE OPTIC LINKS

KSWA

CLKXLCL

KSWXA

BTC

A

B

PIX

A

B

RMTKSWX

B

MSC/RXCDR

BTS15,16BTS 14BTS 13

DUAL IEEE LAN


LANXA

LANXB

LANX A

GPROC2

BTS 23, 24

GPROC 1

GPROC 0

LANX B

2.048 Mbit/s LINK INTERFACESFROM/TO MSC AND TO/FROM BTS

SITES

GSR6 (Horizon II)Typical BSS configurations

30 Sep 200312�6


GMR-0168P02900W21-M

BSC with full redundancy

The digital module configuration for a fully redundant BSC controlling 34 BTSs is shownin Figure 12-2.

Figure 12-2 Fully redundant BSC controlling 34 BTSs

DUAL MCAP BUS

BSU SHELF 1

BSSC CABINET

BSU SHELF 2DUAL IEEE LAN


MSI 0

MSI1

MSI2

MSI9

BTS 16,17

EXPKSWX

A

GCLK A

CLKXLCL

KSWXB

BTC

MSC

BTS 33,34

KSWA

KSWB

REDUNDANT

CLKX LCLKSWX

A

A

B

PIX

A

B

KSWA

KSWB

REDUNDANT

BTS 2 BTS 3BTS 1

BTS 18 BTS 20BTS 19


GPROC0

BTC

LANX B

LANX A

GPROC3BTC

LANX A

LANX B

DUAL SERIAL BUS

DUAL SERIAL BUS

GPROC1

GPROC 2

GPROC 3

GCLK B

EXPKSWX

B

EXPKSWX A

EXPKSWX

B

LCLKSWX

A

LCLKSWX

BBTC MSI

0MSI

1MSI

2MSI

9

GPROC2

GPROC1

GPROC0

2.048 Mbit/s LINK INTERFACESFROM/TO MSC AND TO/FROM BTS

SITES

FIBRE OPTIC LINKS

2 Mbit/s LINKS

2 Mbit/s LINKS

DUAL IEEE LAN

DUAL MCAP BUS

GSR6 (Horizon II) Typical BSS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�7

Transcoder

The digital module configuration for a BSSC cabinet equipped to provide transcoding isshown in Figure 12-3.

Figure 12-3 BSSC cabinet equipped to provide transcoding


DUAL SERIAL BUS

RXU SHELF 1

MSI0

MSI1

XCDR0

XCDR15

RMTKSWX

A

GCLK

CLKX

REMOTE TRANSCODER CABINET

LCLKSWX

BBTC

BTC

RXU SHELF 2

LCLKSWX

A

KSWB

REDUNDANT

GCLK

REDUNDANT

FIBRE OPTIC LINKS

KSWA

CLKX

LCLKSWX

A

A

B

A

B

RMTKSWX

BXCDR

15

BTC

BTC MSI0

MSI1

XCDR0

DUAL IEEE 802.5 LAN

GPROC0

LANX A

LANXA

GPROC 0

LANX B

GPROC1

DUAL MCAP BUS


DUAL IEEE LAN

LCLKSWX

B

GPROC1

LANX B

2.048 Mbit/s LINKINTERFACES FROM/TO

BSCS

2.048 Mbit/s LINKINTERFACES FROM/TO

MSC

DUAL MCAP BUS

DUAL SERIAL BUS

GSR6 (Horizon II)Single cabinet BTS configurations

30 Sep 200312�8


GMR-0168P02900W21-M

Single cabinet BTS configurations

Single cabinet Horizon II macro BTS

The configuration shown in Figure 12-4 is an example of a one-cabinet Horizon II macro.This configuration supports six carriers in single density mode or 12 carriers in doubledensity mode.

Figure 12-4 Macrocell BTS with one Horizon II macro cabinet

(FORREDUNDANCY)

HIISC

22

22

22

22

22

22

12

12

CTU2

CTU2

CTU2

CTU2

CTU2

CTU2

Horizon II macroCABINET

INTEGRATEDNIU

HIISC

INTEGRATEDNIU

GSR6 (Horizon II) Single cabinet BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�9

Single cabinet Horizonmacro BTS

The configuration shown in Figure 12-5 is an example of a one-cabinet Horizonmacro.This configuration supports six carriers.

Figure 12-5 Macrocell BTS with one Horizonmacro cabinet

(FORREDUNDANCY)

MCUF

NIU

22

MCUF

NIU

DIGITAL EQUIPMENT SHELF

22

22

22

22

22

12 12

CTU

CTU

CTU

CTU

CTU

CTU

HorizonmacroCABINET

NOTE If CTUs are replaced with CTU2s from the Horizon II macro, themaster (and redundant) MCUF must have a 20 Mbyte PCMCIAcard installed running CSFP to accommodate the added memoryrequirements of the GSR6 (Horizon II) objects. Also, the CTU2only supports baseband hopping in single density mode wheninstalled in Horizonmacro.

GSR6 (Horizon II)Two cabinet BTS configurations

30 Sep 200312�10


GMR-0168P02900W21-M

Two cabinet BTS configurations

Two cabinet Horizon II macro BTS

The configuration shown in Figure 12-6 is an example of a two cabinet Horizon II macro.This configuration supports 12 carriers in single density mode and 24 carriers in doubledensity mode. The HIISC interfaces to the CTU2s in the second (slave) cabinet throughsite expansion boards in both cabinets (connected via fibre optic cables) and an XMUXreplaces the HIISC in the second cabinet.

The site expansion board is optional equipment in the master BTS and is only requiredwhen site expansion is required.

Figure 12-6 Macrocell BTS with two Horizon II macro cabinets

HIISC

12

2

12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2

Horizon II macro MASTER CABINET

Horizon II macro SLAVE CABINET

INTEGRATEDXMUX

SITEEXPANSION

BOARD

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2

SITEEXPANSION

BOARD

CONNECTION VIA BACKPLANE

NOTE If a redundant HIISC is installed in the master cabinet, redundantsite expansion boards must be installed in the master and slavecabinets and a redundant XMUX must be installed in each slavecabinet.

GSR6 (Horizon II) Two cabinet BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�11

Two cabinet Horizonmacro BTS

The configuration shown in Figure 12-7 is an example of a two cabinet Horizonmacro.This configuration supports 12 carriers. The MCUF interfaces to the CTUs in the secondcabinet through an FMUX in the second cabinet.

Figure 12-7 Macrocell BTS with two Horizonmacro cabinets

MCUF

NIU

12

2

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET

HorizonmacroCABINET


DIGITALEQUIPMENT

SHELF


GSR6 (Horizon II)Three cabinet BTS configurations

30 Sep 200312�12


GMR-0168P02900W21-M

Three cabinet BTS configurations

Three cabinet Horizon II macro BTS

The configuration shown in Figure 12-8 is an example of a three cabinetHorizon II macro. As with a two cabinet configuration, the HIISC interfaces to the CTU2sin the slave cabinets through site expansion boards in all cabinets (connected via fibreoptic cables) and an XMUX replaces the HIISC in each of the slave cabinets.

Figure 12-8 Macrocell BTS with three Horizon II macro cabinets

HIISC

12

2

12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2



INTEGRATEDXMUX

SITEEXPANSION

BOARD

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2

SITEEXPANSION

BOARD

12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2


SITEEXPANSION

BOARD

2



GSR6 (Horizon II) Three cabinet BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�13

Three cabinet Horizonmacro BTS

The configuration shown in Figure 12-9 is an example of a three cabinet Horizonmacro.This configuration supports 18 carriers. The MCUF interfaces to the CTUs in the othercabinets through the FMUXs.

Figure 12-9 Macrocell BTS with three Horizonmacro cabinets

MCUF

NIU

12

2

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET

HorizonmacroCABINET


DIGITALEQUIPMENT

SHELF

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET DIGITAL

EQUIPMENTSHELF

2


GSR6 (Horizon II)Four cabinet BTS configurations

30 Sep 200312�14


GMR-0168P02900W21-M

Four cabinet BTS configurations

Four cabinet Horizon II macro BTS

The configuration shown in Figure 12-10 is an example of a four cabinetHorizon II macro. As with a two cabinet configuration, the HIISC interfaces to the CTU2sin the slave cabinets through site expansion boards in all cabinets (connected via fibreoptic cables) and an XMUX replaces the HIISC in each of the slave cabinets.

Figure 12-10 Macrocell BTS with four Horizon II macro cabinets

HIISC

12

2

12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2



INTEGRATEDXMUX

SITEEXPANSION

BOARD

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2

SITEEXPANSION

BOARD

12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2


SITEEXPANSION

BOARD

2


12

XMUX

CTU2

CTU2

CTU2

2222 22

CTU2

CTU2

CTU2


SITEEXPANSION

BOARD

2


GSR6 (Horizon II) Four cabinet BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0112�15

Four cabinet Horizonmacro BTS

The configuration shown in Figure 12-11 is an example of a four cabinet Horizonmacro.This configuration supports 24 carriers. The MCUF interfaces to the CTUs in the othercabinets through the FMUXs. An additional FMUX is required in the main cabinet tosupport the third extension cabinet.

Figure 12-11 Macrocell BTS with four Horizonmacro cabinets

MCUF

NIU

12

2

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET

HorizonmacroCABINET


DIGITALEQUIPMENT

SHELF

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET

DIGITALEQUIPMENT

SHELF

2

12

FMUX

CTU

CTU

CTU

2222 22

CTU

CTU

CTU

HorizonmacroCABINET

DIGITALEQUIPMENT

SHELF

FMUX

12

2


GSR6 (Horizon II)Horizon macrocell RF configurations

30 Sep 200312�16


GMR-0168P02900W21-M

Horizon macrocell RF configurations

Overview of configuration diagrams

The Horizon macrocell BTS cabinets/enclosures are presented as follows:

S Horizon II macro cabinets.

S Horizonmacro cabinets.

S Horizoncompact2 enclosures.

Horizon II macro cabinets

The following series of Horizon II macro RF configuration diagrams show suggestedways of connecting together Horizon II macro SURF2 and Tx blocks to meet differentoperational requirements. The series of diagrams is by no means exhaustive, andnumerous alternative configurations may be adopted to achieve the same aim.

Each diagram is applicable to either EGSM900 or DCS1800 operation, though theSURF2 module illustrated is a 1800 MHz SURF2. For EGSM900 operation a 900 MHzSURF2 is required.

Two SURF2s can be installed in the Horizon II macro cabinet (see Figure 12-18), inwhich case they must be of the same type (900 and 1800 SURF2s cannot be mixed inthe same cabinet). Dual band operation in a single cabinet is not supported.

Rules for equipping Horizon II macro cabinets

The following rules apply when equipping any Horizon II macro cabinet for theconfigurations shown in Figure 12-12 to Figure 12-18:

S A maximum of six CTU2s can be accommodated.

S All CTU2s in the cabinet must operate at the same frequency (either 900 MHz or1800 MHz.

S When operating in double density mode, both CTU2 carriers must be in the samesector.

S An external equipment cabinet is not required.

GSR6 (Horizon II) Horizon macrocell RF configurations

30 Sep 2003


68P02900W21-M

GMR-0112�17

[DCS1800] 4 or 8 carrier omni with HCUs and air combining

Figure 12-12 shows a single cabinet, four CTU2 configuration with duplexers, hybridcombiner units and air combining. Table 12-1 provides a summary of the equipmentrequired for this configuration.

Figure 12-12 [DCS1800] 4 or 8 carrier omni with HCUs and air combining

EXPRX2B

0

DUP

RXHCU

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

1

BLANK

4

BLANK

5

0

CTU2

1

EMPTY

234

EMPTY

5

CTU2CTU2

2

DUP

RXHCU

ANT

3

CTU2

Horizon II macro CABINET

SURF2

Tx/RxANTENNA

Tx/RxANTENNA

Table 12-1 Equipment required for 4 or 8 carrier omni with HCUs and air combining

Quantity Unit

2 Antennas

1 Horizon II macro cabinet

4 CTU2

Receiver

1 SURF2

Transmitter/receiver

2 DUP

2 HCU


30 Sep 200312�18


GMR-0168P02900W21-M

[DCS1800] 6 or 12 carrier omni with DHUs

Figure 12-13 shows a single cabinet, six CTU2 configuration with duplexers and dualhybrid combiner units. Table 12-2 provides a summary of the equipment required for thisconfiguration.

Figure 12-13 [DCS1800] 6 or 12 carrier omni with DHUs

2345


Tx/RxANTENNA

Tx/RxANTENNA

EXPRX2B

0

DUP

RX

DHU

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

1

BLANK

2

0

CTU2

12345

CTU2CTU2

3

DUP

RX

DHU

ANT

45

CTU2CTU2CTU2

BLANK

SURF2

Table 12-2 Equipment required for 6 or 12 carrier omni with DHUs

Quantity Unit

2 Antennas


6 CTU2

Receiver

1 SURF2


2 DUP

2 DHU


30 Sep 2003


68P02900W21-M

GMR-0112�19

[DCS1800] 2 sector 3/3 or 6/6 with DHUs

Figure 12-14 shows a single cabinet, six CTU2 configuration with duplexers and dualhybrid combiner units. Table 12-3 provides a summary of the equipment required for thisconfiguration.

Figure 12-14 [DCS1800] 2 sector 3/3 or 6/6 with DHUs

2345


RxANTENNA

Tx/RxANTENNA

012345

SURF2

EXPRX2B

0

DUP

RX

DHU

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

1

BLANK

2

0

CTU2

12345

SECTOR 1

CTU2CTU2

3

DUP

RX

DHU

ANT

45

CTU2CTU2CTU2

BLANK

SECTOR 2

RxANTENNA

Tx/RxANTENNA

Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs

Quantity Unit

4 Antennas


6 CTU2

Receiver

1 SURF2


2 DUP

2 DHU


30 Sep 200312�20


GMR-0168P02900W21-M

[DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combiningFigure 12-15 shows a two cabinet configuration, each cabinet containing four CTU2s withduplexers, hybrid combiner units and air combining. Table 12-4 provides a summary ofthe equipment required for this configuration.

Figure 12-15 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

SECTOR 2

CTU2CTU2CTU2 CTU2

EXPRX2B

0

DUP

RX

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

12

0

CTU2

12345

CTU2CTU2

45

CTU2 EMPTYEMPTY

BLANK

HCU

BLANK

EMPTYEMPTY

HIISCSITE EXPANSION

BOARDXMUXSITE EXPANSION

BOARD

Fibre Optic Link (x2)

DUP

RX

ANT

3 0

DUP

RX

ANT

1245

HCU

BLANKDUP

RX

ANT

3

BLANK

HCU HCU

SECTOR 1

Horizon II macroMASTER CABINET

Horizon II macroSLAVE CABINET

SURF2 SURF2

Tx/Rx ANTENNAS Tx/Rx ANTENNAS

Table 12-4 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining

Quantity Unit

4 Antennas


8 CTU2

Receiver

2 SURF2


4 DUP

4 HCU


30 Sep 2003


68P02900W21-M

GMR-0112�21

[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs

Figure 12-16 shows a single cabinet, six CTU2 configuration with duplexers and hybridcombiner units. Table 12-5 provides a summary of the equipment required for thisconfiguration.

Figure 12-16 [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs


RxANTENNA

Tx/RxANTENNA

SURF2

RxANTENNA

Tx/RxANTENNA

EXPRX2B

0

DUP

RX

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

2

0

CTU2

12345

SECTOR 1

1

CTU2

SECTOR 3

DUP

RX

ANT

CTU2

SECTOR 2

35

CTU2

4

DUP

RX

ANT

CTU2CTU2

HCUHCU HCU

Tx/RxANTENNA

RxANTENNA

Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs

Quantity Unit

6 Antennas


6 CTU2

Receiver

1 SURF2


3 DUP

3 HCU


30 Sep 200312�22


GMR-0168P02900W21-M

[DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combiningFigure 12-17 shows a two cabinet configuration, each cabinet containing six CTU2s withduplexers, hybrid combiner units and air combining. Table 12-6 provides a summary ofthe equipment required for this configuration.

Figure 12-17 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining

012345012345

HIISCSITE EXPANSION

BOARDXMUXSITE EXPANSION

BOARD


Horizon II macroMASTER CABINET

Horizon II macroSLAVE CABINET

SURF2 SURF2

Tx/Rx ANTENNAS

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

SECTOR 3

CTU2CTU2CTU2 CTU2

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

5 3

HCU

SECTOR 2

CTU2 CTU2

DUP

RX

ANT

4

DUP

RX

ANT

0

SECTOR 1

DUP

RX

ANT

2 1

HCU

CTU2CTU2CTU2 CTU2

5 3

HCU

CTU2 CTU2

DUP

RX

ANT

4

DUP

RX

ANT

0

DUP

RX

ANT

2 1

HCU HCUHCU

Tx/Rx ANTENNAS Tx/Rx ANTENNAS

Table 12-6 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining

Quantity Unit

6 Antennas


12 CTU2

Receiver

2 SURF2


6 DUP

6 HCU


30 Sep 2003


68P02900W21-M

GMR-0112�23

[DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity

Figure 12-18 shows a single cabinet, six CTU2 configuration for 4 branch Rx diversitywith duplexers and air combining. Table 12-7 provides a summary of the equipmentrequired for this configuration.

Figure 12-18 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and and 4 branch Rx diversity


SURF2

SECTOR 1SECTOR 3 SECTOR 2

EXPRX2B

0

DUP

RX

ANT

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

2

0

CTU2

12345

1

DUP

RX

ANT

CTU2

DUP

RX

ANT

CTU2

3

DUP

RX

ANT

5

CTU2

4

DUP

RX

ANT

CTU2

DUP

RX

ANT

CTU2

EXPRX2C

RX1C

RX0C C D

RX0D

RX1D

RX2D

EXP

SURF2

Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity

Quantity Unit

12 Antennas


6 CTU2

Receiver

2 SURF2


6 DUP


30 Sep 200312�24


GMR-0168P02900W21-M

Horizonmacro cabinets

The following series of Horizonmacro RF configuration diagrams show suggested waysof connecting together Horizonmacro SURF and Tx blocks to meet different operationalrequirements. The series of diagrams is by no means exhaustive, and numerousalternative configurations may be adopted to achieve the same aim.

Each diagram is applicable to either EGSM900 or DCS1800 operation, though the SURFmodule illustrated is a single band 1800 SURF. For EGSM900 operation a 900 SURF(dual band) is required. Connections to the 900 SURF are identified in the same way asthose to the 1800 SURF, with two additional connectors provided for dual band 1800 use.

A dual band 1800 SURF is also available which has two additional connectors providedfor dual band 900 use.

Rules for equipping Horizonmacro cabinets

The following rules apply when equipping any Horizonmacro cabinet for theconfigurations shown in Figure 12-19 to Figure 12-26:

S A maximum of six CTUs can be accommodated.

S An external equipment cabinet is not required.


30 Sep 2003


68P02900W21-M

GMR-0112�25

[DCS1800] 4 carrier omni, with duplexed hybrid and air combining

Figure 12-19 shows a single cabinet, four CTU configuration with duplexed hybrid and aircombining. Table 12-8 provides a summary of the equipment required for thisconfiguration.

Figure 12-19 4 carrier omni, duplexed hybrid and air combining

DCF

CTU

AB

CTU

AB

CTU

AB

CTU

AB

SURF

B

Tx/RxANTENNA

Horizonmacro CABINET

Tx/RxANTENNA

1 02B A A1 02

DCF

A B

Table 12-8 Equipment required for single cabinet, four CTU configuration,duplexed hybrid and air combining

Quantity Unit

2 Antennas

1 Horizonmacro cabinet

4 CTU

Receiver

1 SURF


2 DCF


30 Sep 200312�26


GMR-0168P02900W21-M

[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and aircombining

Figure 12-20 shows a single cabinet, six CTU configuration with duplexed dual-stagehybrid and air combining. Table 12-9 provides a summary of the equipment required forthis configuration.

Figure 12-20 6 carrier omni, duplexed dual-stage hybrid and air combining

B1 02B A A1 02

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

A B

Tx/RxANTENNA

Tx/RxANTENNA


DDF

SURF

FEEDTHROUGHDDF

Table 12-9 Equipment required for single cabinet, six CTU configuration,duplexed dual-stage hybrid and air combining

Quantity Unit

2 Antennas


6 CTU

Receiver

1 SURF


2 DDF

1 Feed through, with two through connectors


30 Sep 2003


68P02900W21-M

GMR-0112�27

[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining

Figure 12-21 shows a single cabinet, six CTU configuration with duplexed dual-stagehybrid combining. Table 12-10 provides a summary of the equipment required for thisconfiguration.

Figure 12-21 2 sector (3/3), duplexed dual-stage hybrid combining

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

A

Tx/RxANTENNA

RxANTENNA

B B

RxANTENNA

Tx/RxANTENNA

(SECTOR 1) (SECTOR 2) (SECTOR 2)(SECTOR 1)


A

DDF

SURF

B1 02B A A1 02

FEEDTHROUGH

DDF

Table 12-10 Equipment required for single cabinet, six CTU configuration,duplexed dual-stage hybrid combining

Quantity Unit

4 Antennas


6 CTU

Receiver

1 SURF


2 DDF



30 Sep 200312�28


GMR-0168P02900W21-M

[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and aircombining

Figure 12-22 shows a dual cabinet, 12 CTU configuration with duplexed dual-stagehybrid and air combining. Table 12-11 provides a summary of the equipment required forthis configuration.

Figure 12-22 2 sector (6/6), duplexed dual-stage hybrid and air combining

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

EXTENDER Horizonmacro CABINET

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

MASTER Horizonmacro CABINET

Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 1)

Tx/RxANTENNA

(SECTOR 1)

DDF DDF DDF

FEEDTHROUGH

DDF

SURF

B1 02B A A1 02

SURF

B1 02B A A1 02

A B BA

FEEDTHROUGH

Table 12-11 Equipment required for dual cabinet, 12 CTU configuration,duplexed dual-stage hybrid and air combining

Quantity Unit

4 Antennas

2 Horizonmacro cabinets

12 CTU

Receiver

2 SURF


4 DDF



30 Sep 2003


68P02900W21-M

GMR-0112�29

[DCS1800] 3 sector (2/2/2), with duplexed hybrid combiningFigure 12-23 shows a single cabinet, six CTU configuration with duplexed hybridcombining. Table 12-12 provides a summary of the equipment required for thisconfiguration.

Figure 12-23 3 sector (2/2/2), duplexed hybrid combining

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

AB

Tx/RxANTENNA

RxANTENNAS

AB

RxANTENNAS

AB

RxANTENNAS

Tx/RxANTENNA

Tx/RxANTENNA

(SECTOR 2) (SECTOR 1)(SECTOR 3) (SECTOR 2)(SECTOR 3) (SECTOR 1)


DCF

SURF

B1 02B A A1 02

DCFDCF

Table 12-12 Equipment required for single cabinet, six CTU configuration,duplexed hybrid combining

Quantity Unit

6 Antennas


6 CTU

Receiver

1 SURF


3 DCF


30 Sep 200312�30


GMR-0168P02900W21-M

[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combiningFigure 12-24 shows a dual cabinet, 12 CTU configuration with duplexed hybrid and aircombining. Table 12-13 provides a summary of the equipment required for thisconfiguration.

Figure 12-24 3 sector (4/4/4), duplexed hybrid and air combining

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

EXTENDER Horizonmacro CABINET

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB


Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 1)

Tx/RxANTENNA

(SECTOR 3)

Tx/RxANTENNA

(SECTOR 1)

DCF DCF DCF DCF DCF DCF

SURF

B1 02B A A1 02

SURF

B1 02B A A1 02

A B BAAB

Table 12-13 Equipment required for dual cabinet, 12 CTU configurationduplexed hybrid and air combining

Quantity Unit

6 Antennas

2 Horizonmacro BTS cabinets

12 CTU


2 SURF

6 DCF


30 Sep 2003


68P02900W21-M

GMR-0112�31

[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and aircombining

Figure 12-25 and Figure 12-26 show a four cabinet, 24 CTU configuration with duplexeddual-stage hybrid and air combining. Table 12-14 provides a summary of the equipmentrequired for this configuration.

Figure 12-25 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1)

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

EXTENDER 3 HorizonmacroCABINET

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

EXTENDER 2 HorizonmacroCABINET

TOEXTENDER 1Horizonmacro

CABINETSURF B0

SURF

B1 02B A A1 02

SURF

B1 02B A A1 02

A

Tx/RxANTENNA

B

Tx/RxANTENNA

Tx/RxANTENNA

(SECTOR 1)(SECTOR 3) (SECTOR 3)

A

DDF

HCU

SURF EXT A

HCU

DDF

HCU

DDF


30 Sep 200312�32


GMR-0168P02900W21-M

Figure 12-26 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2)

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

EXTENDER 1 Horizonmacro CABINET

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB

CTU

AB


Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 1)

TO EXTENDER 2Horizonmacro CABINET

SURF A0SURF EXT B

SURF

B1 02B A A1 02

SURF

B1 02B A A1 02

DDF

HCU HCU

DDF

BAB

DDF

HCU

Table 12-14 Equipment required for four cabinet, 24 CTU configuration,duplexed dual-stage hybrid and air combining

Quantity Unit

6 Antennas

4 Horizonmacro cabinets

24 CTU

Transmitter

6 Hybrid combiner unit (HCU)

Receiver

4 SURF


6 DDF


30 Sep 2003


68P02900W21-M

GMR-0112�33

Horizoncompact2

The Horizoncompact2 BTS system comprises a BTS enclosure and a booster enclosure.One or two additional Horizoncompact2 BTS systems may be added as slaves to providea two or three BTS site.

NOTE Expansion of a single Horizoncompact2 site is only supportedfrom GSR5 software onwards.

The Horizoncompact2 BTS system supports the following site configurations usingGSM900 or DCS1800 BTSs:

S 1 BTS site

Omni site � one or two carriers in a single cell.

S 2 BTS site

Omni site � up to four carriers in a single cell.

Two sector site, two carriers per cell.

S 3 BTS site

Omni site � up to six carriers in a single cell.

Two sector site, two/four carriers per cell.

Three sector site, two carriers per cell.

The following dual band cell configurations are supported when GSM900 and DCS1800Horizoncompact2 BTSs are used:

S 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800carriers.

S 3 BTS cell: Two BTSs with a total of four GSM900 carriers and one BTS with twoDCS1800 carriers

or

Two BTSs with a total of four DCS1800 carriers and one BTS with two GSM900carriers.


30 Sep 200312�34


GMR-0168P02900W21-M

[GSM900/DCS1800] Horizoncompact2 single BTS system

Figure 12-27 shows the configuration for a single Horizoncompact2 BTS system.

Figure 12-27 Horizoncompact2 single BTS system

Tx1Tx2

Rx

Horizoncompact2 BTS

Tx1 OUT

DINO / RHINO DTRX

ISOLATORMODULE

ISOLATORMODULE

Tx2 OUTRx IN

Horizoncompact2 BOOSTER

AMP AMP

DUPLEXERRx Tx

Tx1/RxANTENNA

Tx2ANTENNA

FILTERTx

ANT ANT


30 Sep 2003


68P02900W21-M

GMR-0112�35

[GSM900/DCS1800] Horizoncompact2 two BTS system

Figure 12-28 shows the configuration for a two Horizoncompact2 BTS system using fibreoptic cables. An HDSL option is available which allows the BTSs to be connectedthrough HDSL links. Refer to Figure 12-27 for internal connections within the BTS andbooster.

Figure 12-28 Horizoncompact2 two BTS system

FIBRE OPTIC LINK

Horizoncompact2 SLAVE BTS

DINO / RHINO


Tx1/RxANTENNA

Tx2ANTENNA

Horizoncompact2 MASTER BTS

DINO / RHINO


Tx1/RxANTENNA

Tx2ANTENNA


30 Sep 200312�36


GMR-0168P02900W21-M

[GSM900/DCS1800] Horizoncompact2 three BTS system

Figure 12-29 shows the configuration for a three Horizoncompact2 BTS system usingfibre optic cables. An HDSL option is available which allows the BTSs to be connectedthrough HDSL links. Refer to Figure 12-27 for internal connections within the BTS andbooster.

Figure 12-29 Horizoncompact2 three BTS system

FIBRE OPTIC LINK


DINO / RHINO


Tx1/RxANTENNA

Tx2ANTENNA

Horizoncompact2 MASTER BTS

DINO / RHINO


Tx1/RxANTENNA

Tx2ANTENNA


DINO / RHINO


Tx1/RxANTENNA

Tx2ANTENNA

FIBRE OPTIC LINK

GSR6 (Horizon II) Microcell RF configurations

30 Sep 2003


68P02900W21-M

GMR-0112�37

Microcell RF configurations

Horizonmicro2

The Horizonmicro2 BTS is similar to the Horizoncompact2, but does not include (orsupport) a booster enclosure. One or two additional Horizonmicro2 BTSs may be addedas slaves to provide a two or three BTS site.

NOTE Expansion of a single Horizonmicro2 site is only supported fromGSR5 software onwards.

The Horizonmicro2 BTS supports the following site configurations using GSM900 orDCS1800 BTSs:

S 1 BTS site

Omni site � one or two carriers in a single cell.

S 2 BTS site

Omni site � up to four carriers in a single cell.

Two sector site, two carriers per cell.

S 3 BTS site

Omni site � up to six carriers in a single cell.

Two sector site, two/four carriers per cell.

Three sector site, two carriers per cell.

The following dual band cell configurations are supported when GSM900 and DCS1800Horizonmicro2 BTSs are used:

S 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800carriers.

S 3 BTS cell: Two BTSs with a total of four GSM900 carriers and one BTS with twoDCS1800 carriers

or

Two BTSs with a total of four DCS1800 carriers and one BTS with two GSM900carriers.

GSR6 (Horizon II)Microcell RF configurations

30 Sep 200312�38


GMR-0168P02900W21-M

[GSM900/DCS1800] Horizonmicro2 single BTS system

Figure 12-30 shows the configuration for a single Horizonmicro2 BTS system.

Figure 12-30 Horizonmicro2 single BTS system

Horizonmicro2 BTS

Tx1 OUT

DINO / RHINO DTRX

COMBINER/ISOLATORMODULE

Tx2 OUTRx IN

DUPLEXERRx Tx

Tx1/Tx2/RxANTENNA

ANT

Tx Tx Tx

[GSM900/DCS1800] Horizonmicro2 two BTS system

Figure 12-31 shows the configuration for a two Horizonmicro2 BTS system using fibreoptic cables. An HDSL option is available which allows the BTSs to be connectedthrough HDSL links. Refer to Figure 12-30 for internal connections within the BTS.

Figure 12-31 Horizonmicro2 two BTS system

FIBRE OPTIC LINK

Horizonmicro2 MASTER BTS

DINO / RHINO

Tx1/Tx2/RxANTENNA

Horizonmicro2 SLAVE BTS

DINO / RHINO

Tx1/Tx2/RxANTENNA

GSR6 (Horizon II) Microcell RF configurations

30 Sep 2003


68P02900W21-M

GMR-0112�39

[GSM900/DCS1800] Horizonmicro2 three BTS system

Figure 12-32 shows the configuration for a three Horizonmicro2 BTS system using fibreoptic cables. An HDSL option is available which allows the BTSs to be connectedthrough HDSL links. Refer to Figure 12-30 for internal connections within the BTS.

Figure 12-32 Horizonmicro2 three BTS system

FIBRE OPTIC LINK

Horizonmicro2 MASTER BTS

DINO / RHINO

Tx1/Tx2/RxANTENNA


DINO / RHINO

Tx1/Tx2/RxANTENNA


DINO / RHINO

Tx1/Tx2/RxANTENNA

FIBRE OPTIC LINK

GSR6 (Horizon II)Connecting Horizon II macro cabinets to Horizonmacro cabinets

30 Sep 200312�40


GMR-0168P02900W21-M

Connecting Horizon II macro cabinets to Horizonmacro cabinets

Connection overview

This section provides examples of how previous generation Horizonmacro BTSequipment can be connected to the latest generation Horizon II macro BTS equipment.

Compatibility issues

The following points must be taken into account when connecting Horizon II macrocabinets to Horizonmacro cabinets:

S Although the Horizon II macro equipment is totally compatible with Horizonmacroequipment, the CTU2 is the only module that can be used in either cabinet.

S When CTU2s are used in Horizonmacro, baseband hopping is only supported insingle density mode.

S In cases where the Horizonmacro BTS is the master cabinet and the MCUF is themaster site controller, the MCUF must have a 20 Mbyte PCMCIA card installedrunning CSFP to accommodate the added memory requirements of the GSR6(Horizon II) objects.

GSR6 (Horizon II) Connecting Horizon II macro cabinets to Horizonmacro cabinets

30 Sep 2003


68P02900W21-M

GMR-0112�41

Examples of mixed cabinet configurations

Figure 12-33 to Figure 12-38 are examples of possible configurations for mixedHorizon II macro and Horizonmacro cabinets.

Sector 4/4 configuration using two cabinets

Figure 12-33 shows a suggested configuration for sector 4/4, using oneHorizon II macro cabinet with duplexers and one Horizonmacro cabinet.

Figure 12-33 Sector 4/4 configuration with Horizon II macro and Horizonmacro cabinets

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2 CTU2EMPTYEMPTY

Horizon II macromaster cabinet

HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANKDUP

RX

ANT

3

BLANK

SECTOR 1

2B 1B 0B 2A 1A 0A B A

BLANK

EXT

DCF DCF

SECTOR 2

FMUX

Horizonmacroslave cabinet

BLANK

1

BLANK

EMPTY EMPTY

12345 0

4

SURFSURF2


30 Sep 200312�42


GMR-0168P02900W21-M

Sector 6/6 configuration using two cabinets

Figure 12-34 shows a suggested configuration for sector 6/6, using oneHorizon II macro cabinet with duplexers and hybrid combiner units and oneHorizonmacro cabinet.

Figure 12-34 Sector 6/6 configuration with Horizon II macro and Horizonmacro cabinets

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2 CTU2EMPTYEMPTY


HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

245

BLANKDUP

RX

ANT

3

BLANK

SECTOR 1

2B 1B 0B 2A 1A 0A B A

DDF

EXT

DDF

SECTOR 2

FMUX


1

EMPTY

12345 0

HCU

ÄLOAD

CTU2

HCU

F�THRU

SURFSURF2


30 Sep 2003


68P02900W21-M

GMR-0112�43

Sector 2/2/2 configuration using two cabinets

Figure 12-35 and Figure 12-36 show a suggested configuration for sector 2/2/2,using one Horizon II macro cabinet with duplexer and one Horizonmacrocabinet. In Figure 12-35 the Horizon II macro is the master cabinet, whereas inFigure 12-36 the Horizonmacro is the master cabinet.

Figure 12-35 Sector 2/2/2 configuration (Horizon II macro as master cabinet)

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2EMPTYEMPTY


HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANK

3

BLANK

SECTOR 1

2B 1B 0B 2A 1A 0A B A

BLANK

EXT

DCF DCF

SECTOR 2

FMUX


BLANK

1

BLANK

EMPTY EMPTY

12345 0

BLANK

EMPTY

SECTOR 3

4

SURFSURF2


30 Sep 200312�44


GMR-0168P02900W21-M

Figure 12-36 Sector 2/2/2 configuration (Horizonmacro as master cabinet)

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2EMPTYEMPTY

Horizon II macroslave cabinet

XMUXSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANK

3

BLANK

SECTOR 3

2B 1B 0B 2A 1A 0A B A

BLANK

EXT

DCF DCF

SECTOR 1

MCUF

Horizonmacromaster cabinet

BLANK

1

BLANK

EMPTY EMPTY

12345 0

BLANK

EMPTY

SECTOR 2

4

SURFSURF2


30 Sep 2003


68P02900W21-M

GMR-0112�45


Figure 12-37 shows a suggested configuration for sector 4/4/4, using oneHorizon II macro cabinet with duplexers and one Horizonmacro cabinet.

Figure 12-37 Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabinets

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2 CTU2EMPTYEMPTY


HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANKDUP

RX

ANT

3

BLANK

SECTOR 1

2B 1B 0B 2A 1A 0A B A

BLANK

EXT

DCF DCF

SECTOR 3

FMUX


12345 0

CTU2 CTU2

DUP

RX

ANT

4 1

DUP

RX

ANT

SECTOR 2

SURFSURF2


30 Sep 200312�46


GMR-0168P02900W21-M


Figure 12-38 shows a suggested configuration for sector 6/6/6, using oneHorizon II macro cabinet with duplexers and dual hybrid combiner units and oneHorizonmacro cabinet.

Figure 12-38 Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabinets



SECTOR 1

2B 1B 0B 2A 1A 0A B A

DDF

EXT

DDF

SECTOR 3

FMUX


12345 0

F�THRU

SECTOR 2

SURF

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2CTU2CTU2 CTU2

HIISCSITE EXPANSION

BOARD

DUP

RX

ANT

3

CTU2 CTU2

4

DUP

RX

ANT

01

BLANK

5

BLANK

2DHUDHU


30 Sep 2003


68P02900W21-M

GMR-0112�47

Using CTU2s in Horizonmacro cabinets

Figure 12-39 shows an example of a configuration with CTU2s (operating insingle density mode) installed in a Horizonmacro cabinet.

Figure 12-39 Horizonmacro cabinet configuration using CTUs and CTU2s

2B 1B 0B 2A 1A 0A B A

DCF

EXT

DCF

SECTOR 2

MCUF

Horizonmacro cabinet

12345 0

CTU2CTU2

DCF

SECTOR 3 SECTOR 1

SURF

GSR6 (Horizon II)Connecting Horizon II macro cabinets to M-Cell6 cabinets

30 Sep 200312�48


GMR-0168P02900W21-M

Connecting Horizon II macro cabinets to M-Cell6 cabinets

Connection overview

This section provides examples of how older generation M-Cell6 BTS equipment can beconnected to the latest generation Horizon II macro BTS equipment.

NOTE M-Cell2 BTS cabinets cannot be connected to Horizon II macroBTS cabinets.

Compatibility issues

The following points must be taken into account when connecting Horizon II macrocabinets to M-Cell6 cabinets:

S Although the Horizon II macro equipment is totally compatible with M-Cell6equipment, none of the Horizon II macro components can be used in the M-Cell6.

S In cases where the M-Cell6 BTS is the master cabinet and the MCU is the mastersite controller, the MCU must have a 20 Mbyte PCMCIA card installed runningCSFP to accommodate the added memory requirements of the GSR6 (Horizon II)objects.

S The M-Cell6 must have a FMUX installed to communicate with theHorizon II macro cabinet.

S When DCS1800 cabinets are connected, connections between theHorizon II macro SURF2 and the M-Cell6 LNAs must include �13 dB attenuators.

GSR6 (Horizon II) Connecting Horizon II macro cabinets to M-Cell6 cabinets

30 Sep 2003


68P02900W21-M

GMR-0112�49

900 MHz BTSs

Figure 12-40 shows how a 900 MHz Horizon II macro BTS cabinet may be connected toa 900 MHz M-Cell6 BTS cabinet to create a 2 sector (4/4) configuration.

Figure 12-40 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections

TCU

TCU

TCU

TCU

CBF0CBF1BLANK

DU

PLE

XE

RIADU

DLNB

DU

PLE

XE

R

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2 CTU2EMPTYEMPTY


HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANKDUP

RX

ANT

3

BLANK

SECTOR 1

BLANK

1

BLANK

EMPTY EMPTY

4

SURF2

M-Cell6slave cabinet

FMUX

SECTOR 2

GSR6 (Horizon II)Connecting Horizon II macro cabinets to M-Cell6 cabinets

30 Sep 200312�50


GMR-0168P02900W21-M

1800 MHz BTSs

Figure 12-41 shows how an 1800 MHz Horizon II macro BTS cabinet may be connectedto an 1800 MHz M-Cell6 BTS cabinet to create a 2 sector (4/4) configuration.

Figure 12-41 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections

TCU

TCU

TCU

TCU

CBF0CBF1BLANK

DU

PLE

XE

RLNA

DU

PLE

XE

R

EXPRX2B

RX1B

RX0B B A

RX0A

RX1A

RX2A

EXP

012345

CTU2 CTU2EMPTYEMPTY


HIISCSITE EXPANSION

BOARD


0

DUP

RX

ANT

25

BLANKDUP

RX

ANT

3

BLANK

SECTOR 1

BLANK

1

BLANK

EMPTY EMPTY

4

SURF2

M-Cell6slave cabinet

FMUX

SECTOR 2

30 Sep 2003


68P02900W21-M

GMR-0113�1

Chapter 13

M-Cell BTS configurations

GSR6 (Horizon II)

30 Sep 200313�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-0113�3

Chapter overview

M-Cell equipment covered

This chapter is included for reference purposes. It provides diagrams of the logicalinterconnections of the components in older generation M-Cell BTS equipment andtypical RF configurations.

Examples of how M-Cell equipment may be connected to current generation Horizonequipment are contained in Chapter 12.


S Picocell (M-Cellaccess) configurations.

S M-Cell6 and M-Cell2 one cabinet configurations.

S M-Cell6 two cabinet configurations.

S M-Cell2 three cabinet configurations.

S M-Cell6 four cabinet configurations.

S RF configurations.

� M-Cell6.

� M-Cell2.

GSR6 (Horizon II)Standard M-Cell configurations

30 Sep 200313�4


GMR-0168P02900W21-M

Standard M-Cell configurations

Introduction to standard M-Cell configurations

The examples in this section are shown with individual antennas for transmit and receivesignals. Duplexers will be required if individual antennas are not used. 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 typicalconfiguration using that specific equipment. Rather, they are meant to highlight theconfigurations that, within the constraints of the BSS architecture, are feasible when themacrocell hardware is deployed in an M-Cell BTS. The diagrams also show possiblecabinet boundaries. Cabinet designs, however, allow for a number of differentarrangements of the same configuration.

NOTE For typical BSS configurations, refer to Figure 12-1 andFigure 12-2 in Chapter 12.

Rather than showing redundancy for all M-Cell BTS configurations, the controlredundancy is depicted only for one M-Cell6, and one M-Cell2 cabinet diagram (seeFigure 13-5 and Figure 13-6).

GSR6 (Horizon II) Picocell (M-Cellaccess) configurations

30 Sep 2003


68P02900W21-M

GMR-0113�5

Picocell (M-Cellaccess) configurations

Single site

Fibre optic links

The digital module and RF configuration for a PCC cabinet with six PCUs (RF carriers)and fibre optic links is shown in Figure 13-1.

Figure 13-1 Single BTS site with 6 PCUs using fibre optic links

DUAL SERIAL BUS

DUAL MCAP BUS

TO/FROM TRANSMIT/RECEIVE ANTENNA

BSC

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

DRIX4

DRIX3

DRIX2

DRIX1

DUAL IEEE802.5 LAN

PCC CABINET

PCU1

GCLK TSWA


ONE RF CARRIERCONSISTS OF ONEDRIM, DRIX AND PCU

BTC

LANXA

A

B

BSU SHELF FIBRE OPTIC LINKS

GPROCGPROC GPROC

PCU2

PCU3

PCU4

DRIM5

DRIM6

DRIX6

DRIX5

PCU5

PCU6

LINKS FROM/TO BSC

GSR6 (Horizon II)Picocell (M-Cellaccess) configurations

30 Sep 200313�6


GMR-0168P02900W21-M

HDSL links

The digital module and RF configuration for a PCC cabinet with six PCUs (RF carriers)and HDSL links is shown in Figure 13-2.

Figure 13-2 Single BTS site with 6 PCUs using HDSL links

DUAL SERIAL BUS

DUAL MCAP BUS

TO/FROM TRANSMIT/RECEIVE ANTENNA

BSC

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

HRIX4

HRIX3

HRIX2

HRIX1

DUAL IEEE802.5 LAN

PCC CABINET

PCU1

GCLK TSWA


ONE RF CARRIERCONSISTS OF ONEDRIM, HRIX AND PCU

BTC

LANXA

A

B

LOWER BSU SHELF

GPROCGPROC GPROC

PCU2

PCU3

PCU4

DRIM5

DRIM6

HRIX6

HRIX5

PCU5

PCU6

LINKS FROM/TO BSC

TOP OF CABINET

HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120


30 Sep 2003


68P02900W21-M

GMR-0113�7

Two site cabinet

Fibre optic links

The digital module and RF configuration for a PCC cabinet with 12 PCUs (RF carriers)and fibre optic links is shown in Figure 13-3.

GSR6 (Horizon II)Picocell (M-Cellaccess) configurations

30 Sep 200313�8


GMR-0168P02900W21-M

Figure 13-3 Two BTS site with 12 PCUs using optical fibre links

FIBRE OPTIC LINKS

DUAL SERIAL BUS

DUAL MCAP BUS

BSC

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

DRIX4

DRIX3

DRIX2

DRIX1

DUAL IEEE802.5 LAN

PCC CABINET

GCLK TSWA


BTC

LANXA

A

B

LOWER BSU SHELF

GPROCGPROC GPROC

DRIM5

DRIM6

DRIX6

DRIX5

LINKS FROM/TO BSC

DUAL SERIAL BUS

DUAL MCAP BUS

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

DRIX4

DRIX3

DRIX2

DRIX1

DUAL IEEE802.5 LAN

GCLK TSWA


BTC

LANXA

A

B

UPPER BSU SHELF

GPROCGPROC GPROC

DRIM5

DRIM6

DRIX6

DRIX5

LINKS FROM/TO BSC

FIBRE OPTIC LINKS

PCU 1 to 6 PCU 7 to 12

HDSL links

The digital module and RF configuration for a PCC cabinet with 12 PCUs (RF carriers)and HDSL links is shown in Figure 13-4.


30 Sep 2003


68P02900W21-M

GMR-0113�9

Figure 13-4 Two BTS site with 12 PCUs using HDSL links

DUAL SERIAL BUS

DUAL MCAP BUS

BSC

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

HRIX4

HRIX3

HRIX2

HRIX1

DUAL IEEE802.5 LAN

PCC CABINET

GCLK TSWA


BTC

LANXA

A

B

LOWER BSU SHELF

GPROCGPROC GPROC

DRIM5

DRIM6

HRIX6

HRIX5

LINKS FROM/TO BSC

TOP OFCABINET

DUAL SERIAL BUS

DUAL MCAP BUS

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

HRIX4

HRIX3

HRIX2

HRIX1

DUAL IEEE802.5 LAN

GCLK TSWA


BTC

LANXA

A

B

GPROCGPROC GPROC

DRIM5

DRIM6

HRIX6

HRIX5

LINKS FROM/TO BSCUPPER BSU SHELF

PCU 9/10PCU 7/8PCU 5/6PCU 3/4PCU 1/2

HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120

PCU 11/12

GSR6 (Horizon II)Single cabinet BTS configurations

30 Sep 200313�10


GMR-0168P02900W21-M

Single cabinet BTS configurations

Single cabinet M-Cell6 BTS

The configuration shown in Figure 13-5 is an example of a single cabinet M-Cell6 BTS.This configuration supports six carriers.

Figure 13-5 Single cabinet M-Cell6 BTS

(FORREDUNDANCY)

M-CELL6 BTS CABINET

MCU

NIU

mBCU

TCU

TCU

22

MCU

NIU

mBCU

22

TCU

TCU

22

22

TCU

TCU

22

22

FOX

12

FOX

12

12 12

GSR6 (Horizon II) Single cabinet BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0113�11

Single cabinet M-Cell2 BTS

The configuration shown in Figure 13-6 is an example of a single cabinet M-Cell2 BTS.This configuration supports two carriers.

Figure 13-6 Single cabinet M-Cell2 BTS

(FORREDUNDANCY)

M-CELL2 CABINET

MCU

NIU

mBCU

TCU

TCU

22

MCU

NIU

mBCU

22

GSR6 (Horizon II)Two cabinet BTS configuration

30 Sep 200313�12


GMR-0168P02900W21-M

Two cabinet BTS configuration

Two cabinet M-Cell6 BTS

The configuration shown in Figure 13-7 is an example of a two cabinet M-Cell6 BTS. Thisconfiguration supports 12 carriers. The MCUs interface to the TCUs through the FOX orthe FMUX/FOX.

Figure 13-7 Two cabinet M-Cell6 BTS

M-CELL6 BTS CABINET

M-CELL6BTS CABINET

MCU

TCU

TCU

TCU

TCU

TCU

TCU

NIU

FMUX

FOX

2222 2

12

212

12

2

mBCU

TCU

TCU

TCU

TCU

TCU

TCU

2222 22

12

FMUX

FOX

mBCU

GSR6 (Horizon II) Three cabinet BTS configuration

30 Sep 2003


68P02900W21-M

GMR-0113�13

Three cabinet BTS configuration

Three cabinet M-Cell2 BTS

The configuration shown in Figure 13-8 is an example of a three cabinet M-Cell2 BTS.This configuration supports six carriers.

Figure 13-8 Three cabinet M-Cell2 BTS

M-CELL2 CABINET

M-CELL2 CABINET

M-CELL2 CABINET

44

MCU

NIU

FOX

12

mBCU

12

TCU

TCU

TCU

TCU

TCU

TCU

22

2

2

2

2

GSR6 (Horizon II)Four cabinet BTS configuration

30 Sep 200313�14


GMR-0168P02900W21-M

Four cabinet BTS configuration

Four cabinet M-Cell6 BTS

The configuration shown in Figure 13-9 is an example of a four cabinet M-Cell6 BTS.This configuration supports 24 carriers. The MCUs interface to the TCUs through theFOX or the FMUX/FOX.

Figure 13-9 Four cabinet M-Cell6 BTS

FMUX

M-CELL6 BTS CABINET

M-CELL6BTS CABINET

MCU

TCU

TCU

TCU

TCU

TCU

TCU

NIU

FMUX

FMUX

FOX

2222 2

12

2

2

2

12

12

12

12

2

mBCU

TCU

TCU

TCU

TCU

TCU

TCU

2222 22

TCU

TCU

TCU

TCU

TCU

TCU

2222 22

12

FMUX

TCU

TCU

TCU

TCU

TCU

TCU

2222 22

M-CELL6 BTS CABINET

M-CELL6 BTS CABINET

FOX

mBCU

FMUX

FOX

mBCU

12

12

FMUX

FOX

mBCU

GSR6 (Horizon II) M-Cell RF configurations

30 Sep 2003


68P02900W21-M

GMR-0113�15

M-Cell RF configurations

Overview of M-Cell configuration diagrams

The M-Cell BTS cabinets are presented as follows:

S M-Cell6 single cabinet.

S M-Cell6 multiple cabinets.

S M-Cell2 single cabinet.

Rules for equipping M-Cell cabinets

The following rules apply when equipping an M-Cell cabinet for the configurations shownin Figure 13-10 to Figure 13-45:

S In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated.

S In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated.

S An external equipment cabinet is not required, unless specifically stated in the textaccompanying the configuration diagram.

S In an M-Cell6 side cabinet, a maximum of three high power duplexers can beaccommodated.

GSR6 (Horizon II)M-Cell RF configurations

30 Sep 200313�16


GMR-0168P02900W21-M

M-Cell6 cabinetsNOTE DIversity is assumed in all figures, unless stated otherwise.

[GSM900] 3 carrier omni, with hybrid combining and diversityA single cabinet, four TCU configuration with hybrid combining and diversity, is shown inFigure 13-10. Table 13-1 provides a summary of the equipment required for thisconfiguration.

Figure 13-10 3 carrier omni, hybrid combining

3-INPUTCBF

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

A B

4 4

Tx ANTENNA Rx ANTENNAS

M-Cell6 BTS CABINET

RF INPUT

RF LOAD

Non-HCOMB

Table 13-1 Equipment required for single cabinet, 4 TCU configuration with hybridcombining and diversity

Quantity Unit

3 Antennas

1 M-Cell6 BTS cabinet

3 TCU

Transmitter

1 3-input CBF

1 Non-hybrid combiner (Non-HCOMB)

Receiver

1 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�17

[GSM900] 3 carrier omni, with hybrid combining, diversity, andmedium power duplexer

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown inFigure 13-11. Table 13-2 provides a summary of the equipment required for thisconfiguration.

Figure 13-11 3 carrier omni, hybrid combining, medium power duplexer

3-INPUTCBF

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

4 4

Tx/Rx ANTENNA Rx ANTENNA

M-Cell6 BTS CABINET

RF INPUT

RF LOAD

DUPLEXER

Non-HCOMB

Table 13-2 Equipment required for single cabinet, 4 TCU configuration with hybridcombining, diversity and medium power duplexer

Quantity Unit

2 Antennas


3 TCU

Transmitter

1 3-input CBF


Receiver

1 DLNB


1 Medium power duplexer


30 Sep 200313�18


GMR-0168P02900W21-M

[GSM900] 4 carrier omni, with hybrid combining and diversityA single cabinet, four TCU configuration with hybrid combining and diversity, is shown inFigure 13-12. Table 13-3 provides a summary of the equipment required for thisconfiguration.

Figure 13-12 4 carrier omni, hybrid combining

3-INPUTCBF

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

A B

4 4


M-Cell6 BTS CABINET

HCOMB

RF INPUT

RF LOAD


Quantity Unit

3 Antennas


4 TCU

Transmitter

1 3-input CBF

1 Hybrid combining block (HCOMB)

Receiver

1 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�19

[GSM900] 4 carrier omni, with hybrid combining, diversity, andmedium power duplexer

A single cabinet, four TCU configuration with hybrid combining, diversity, and mediumpower duplexer, is shown in Figure 13-13. Table 13-4 provides a summary of theequipment required for this configuration.

Figure 13-13 4 carrier omni, hybrid combining, medium power duplexer

3-INPUTCBF

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

4 4

Rx ANTENNA

M-Cell6 BTS CABINET

HCOMB

RF INPUT

RF LOAD

Tx/Rx ANTENNA

DUPLEXER


Quantity Unit

2 Antennas


4 TCU

Transmitter

1 3-input CBF

1 Hybrid combining block (HCOMB)

Receiver

1 DLNB




30 Sep 200313�20


GMR-0168P02900W21-M

[GSM900] 6 carrier omni, with cavity combining and diversityA single cabinet, six TCU configuration with cavity combining and diversity, is shown inFigure 13-14. Table 13-5 provides a summary of the equipment required for thisconfiguration.

Figure 13-14 6 carrier omni, cavity combining

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

CCB(EXTENSION)

CCB(OUTPUT)

A B

6 6


M-Cell6 BTS CABINET

Table 13-5 Equipment required for single cabinet, 6 TCU configuration with cavitycombining and diversity

Quantity Unit

3 Antennas


6 TCU

Transmitter

1 CCB (Output)

1 CCB (Extension)

Receiver

1 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�21

[GSM900] 6 carrier omni, with cavity combining, diversity, and highpower duplexerA single cabinet, six TCU configuration with cavity combining, diversity, and high powerduplexer, is shown in Figure 13-15. Table 13-6 provides a summary of the equipmentrequired for this configuration.

An external equipment rack/cabinet is required for a high power duplexer in an indoorinstallation.

Figure 13-15 6 carrier omni, cavity combining, high power duplexer

IADU

DLNB

AB

66

RxANTENNA

Tx/RxANTENNA

Tx

Rx

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

CCB(OUTPUT)

CCB(EXTENSION)

ANT

M-Cell6 BTS CABINET M-Cell6 SIDE CABINET

HIGH POWERDUPLEXER

Table 13-6 Equipment required for single cabinet, 6 TCU configuration with cavitycombining, diversity and high power duplexer

Quantity Unit

2 Antennas


1 M-Cell6 side cabinet

6 TCU

Transmitter

1 CCB (Output)

1 CCB (Extension)

Receiver

1 DLNB


1 High power duplexer


30 Sep 200313�22


GMR-0168P02900W21-M

[GSM900] 8 carrier omni, with combining and diversity

A dual cabinet, eight TCU configuration with combining and diversity, is shown inFigure 13-16. Table 13-7 provides a summary of the equipment required for thisconfiguration.


30 Sep 2003


68P02900W21-M

GMR-0113�23

Figure 13-16 8 carrier omni, combining

IADU

DLNB

A B

66

RxANTENNA

TxANTENNA

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

CCB(OUTPUT)

CCB(EXTENSION)

MASTER M-Cell6 BTS CABINET

IADU

2 2

TCU

AB

TCU

AB

EXTENDER M-Cell6 BTS CABINET

Tx/RxANTENNA

CBF

DUPLEXERRx EXTBLOCK

Table 13-7 Equipment required for multiple cabinet, 8 TCU configuration withcombining and diversity

Quantity Unit

3 Antennas


8 TCU

Transmitter

1 CBF

1 CCB (Output)

1 CCB (Extension)

Receiver

1 DLNB

1 Rx extension block




30 Sep 200313�24


GMR-0168P02900W21-M

[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown inFigure 13-17. Table 13-8 provides a summary of the equipment required for thisconfiguration.

Figure 13-17 2 sector (3/3), hybrid combining

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

A

6 6

TxANTENNA

RxANTENNA

DLNB

B

DLNB

B

RxANTENNA

TxANTENNA

(SECTOR 2) (SECTOR 1) (SECTOR 2) (SECTOR 1)

M-Cell6 BTS CABINET

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOADRF LOAD

RF INPUT

A

Non-HCOMB


Quantity Unit

6 Antennas


6 TCU

Transmitter

2 3-input CBF


Receiver

2 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�25

[GSM900] 2 sector (3/3), with hybrid combining, diversity, andmedium power duplexersA single cabinet, six TCU configuration with hybrid combining, diversity, and mediumpower duplexers, is shown in Figure 13-18. Table 13-9 provides a summary of theequipment required for this configuration.

Figure 13-18 2 sector (3/3), hybrid combining, medium power duplexers

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

A

6 6

Tx/RxANTENNA

RxANTENNA

DLNB

B

DLNB

A B

RxANTENNA

Tx/RxANTENNA

(SECTOR 2) (SECTOR 1) (SECTOR 2) (SECTOR 1)

M-Cell6 BTS CABINET

DUPLEXER

DUPLEXER

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOADRF LOAD

RF INPUT

Non-HCOMB

Table 13-9 Equipment required for single cabinet, 6 TCU configuration withcombining, diversity and medium power duplexer

Quantity Unit

4 Antennas


6 TCU

Transmitter

2 3-input CBF


Receiver

2 DLNB




30 Sep 200313�26


GMR-0168P02900W21-M

[GSM900] 3 sector (2/2/2), with combining and diversity

A single cabinet, six TCU configuration with combining and diversity, is shown inFigure 13-19. Table 13-10 provides a summary of the equipment required for thisconfiguration.

Figure 13-19 3 sector (2/2/2), combining

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

CBF

A B

6 6

TxANTENNA

RxANTENNAS

DLNB

A B

RxANTENNAS

DLNB

A B

RxANTENNAS

CBF CBF

TxANTENNA

TxANTENNA

(SECTOR 2) (SECTOR 3)(SECTOR 1) (SECTOR 1) (SECTOR 2) (SECTOR 3)

M-Cell6 BTS CABINET

Table 13-10 Equipment required for single cabinet, 6 TCU configuration withcombining and diversity

Quantity Unit

9 Antennas


6 TCU

Transmitter

3 CBF

Receiver

3 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�27

[GSM900] 3 sector (2/2/2), with cavity combining, diversity, andmedium power duplexers

A single cabinet, six TCU configuration with cavity combining, diversity, and mediumpower duplexers, is shown in Figure 13-20. Table 13-11 provides a summary of theequipment required for this configuration.

Figure 13-20 3 sector (2/2/2), combining, medium power duplexers

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

CBF

A B

6 6

Tx/RxANTENNA

RxANTENNA

DLNB

A B

RxANTENNA

DLNB

A B

RxANTENNA

CBF CBF

Tx/RxANTENNA

Tx/RxANTENNA


M-Cell6 BTS CABINET

DUPLEXER

DUPLEXER

DUPLEXER

Table 13-11 Equipment required for single cabinet, 6 TCU configuration withcombining, diversity and medium power duplexers

Quantity Unit

6 Antennas


6 TCU

Transmitter

3 CBF

Receiver

3 DLNB




30 Sep 200313�28


GMR-0168P02900W21-M

[GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexers (3 antenna per sector)

A dual cabinet, 12 TCU configuration with air combining, diversity, and medium powerduplexers, is shown in Figure 13-21. Table 13-12 provides a summary of the equipmentrequired for this configuration.

Figure 13-21 3 sector (4/4/4), air combining, medium power duplexers

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


CBF0CBF1CBF2

IADU

DLNB Rx EXTBLOCK D

UP

LEX

ER

Tx/RxANTENNA

(SECTOR 1)

TxANTENNA

(SECTOR 2)

IADU

DLNB DLNBDU

PLE

XE

R

DU

PLE

XE

R

CBF0CBF1CBF2

Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 3)

RxANTENNA

(SECTOR 1)

TxANTENNA

(SECTOR 1)

RxANTENNA

(SECTOR 2)

TxANTENNA

(SECTOR 3)

RxANTENNA

(SECTOR 2)

Table 13-12 Equipment required for dual cabinet, 12 TCU configuration with aircombining, diversity and medium power duplexers (3 antenna per sector)

Quantity Unit

9 Antennas


12 TCU

Transmitter

6 CBF

Receiver

3 DLNB





30 Sep 2003


68P02900W21-M

GMR-0113�29

[GSM900] 3 sector (4/4/4), with air combining, diversity, and mediumpower duplexers (2 antenna per sector)

A multiple cabinet, 12 TCU configuration with air combining, diversity, and medium powerduplexers, is shown in Figure 13-22. Table 13-13 provides a summary of the equipmentrequired for this configuration.

Figure 13-22 3 sector (4/4/4), air combining, medium power duplexers

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


CBF0CBF1CBF2

IADU

DLNB Rx EXTBLOCK

DU

PLE

XE

R

Tx/Rx ANTENNA(SECTOR 1)Tx/Rx ANTENNA (SECTOR 2)

IADU

DLNB DLNB

DU

PLE

XE

R

DU

PLE

XE

R

DU

PLE

XE

R

DU

PLE

XE

R

DU

PLE

XE

R

CBF0CBF1CBF2

Tx/Rx ANTENNA(SECTOR 3)

Table 13-13 Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity and medium power duplexers (2 antenna per sector)

Quantity Unit

6 Antennas


12 TCU

Transmitter

6 CBF

Receiver

3 DLNB





30 Sep 200313�30


GMR-0168P02900W21-M

[GSM900] 3 sector (4/4/4), with cavity combining and diversity

A multiple cabinet, 12 TCU configuration with cavity combining and diversity, is shown inFigure 13-23. Table 13-14 provides a summary of the equipment required for thisconfiguration.

Figure 13-23 3 sector (4/4/4), cavity combining

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

DLNB

CCB(EXTENSION)

CCB(OUTPUT)

A B

4 4


Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.

(SECTOR 1)(SECTOR 1)

MASTER M-Cell6 CABINET

Table 13-14 Equipment required for multiple cabinet, 12 TCU configuration with hybridcombining and diversity

Quantity Unit

6 Antennas


12 TCU

Transmitter

3 CCB (output)

3 CCB (extension)

Receiver

3 DLNB


30 Sep 2003


68P02900W21-M

GMR-0113�31

[GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining anddiversity

A dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity, isshown in Figure 13-24. Table 13-15 provides a summary of the equipment required forthis configuration.

Figure 13-24 3 sector (4/4/4), 3-input CBF, hybrid combining

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


IADU

DLNB Rx EXTBLOCK

TxANTENNA

(SECTOR 1)

TxANTENNA

(SECTOR 2)

IADU

DLNB DLNB

RxANTENNA

(SECTOR 3)

TxANTENNA

(SECTOR 3)

HCOMB3-INPUT

CBF3-INPUT

CBF3-INPUT

CBF HCOMBHCOMB

RxANTENNA

(SECTOR 1)

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RxANTENNA

(SECTOR 2)

Table 13-15 Equipment required for dual cabinet, 12 TCU configuration with 3-inputCBF, hybrid combining and diversity

Quantity Unit

9 Antennas


12 TCU

Transmitter

3 3-input CBF

3 Hybrid combiner module (HCOMB)

Receiver


30 Sep 200313�32


GMR-0168P02900W21-M

Table 13-15 Equipment required for dual cabinet, 12 TCU configuration with 3-inputCBF, hybrid combining and diversity

Quantity Unit

3 DLNB



30 Sep 2003


68P02900W21-M

GMR-0113�33

[GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity,and medium power duplexersA multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity, andmedium power duplexers, is shown in Figure 13-25. Table 13-16 provides a summary ofthe equipment required for this configuration.

Figure 13-25 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


IADU

Tx/RxANTENNA

(SECTOR 1)

Tx/Rx & RxANTENNA

(SECTOR 2)

IADU

DU

PLE

XE

R

RxANTENNA

(SECTOR 3)

Tx/RxANTENNA

(SECTOR 3)

HCOMB 3-INPUTCBF

3-INPUTCBF

3-INPUTCBF HCOMBHCOMB

RxANTENNA

(SECTOR 1)

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RF INPUT

DU

PLE

XE

R

DU

PLE

XE

R

DLNB Rx EXTBLOCK DLNB DLNB

Table 13-16 Equipment required for multiple cabinet, 12 TCU configuration with3-input CBF, air combining, diversity and medium power duplexers

Quantity Unit

6 Antennas


12 TCU

Transmitter

3 3-input CBF


Receiver

3 DLNB





30 Sep 200313�34


GMR-0168P02900W21-M

[GSM900] 3 sector (5/5/5), with 3-input CBF, air combining, diversity,and medium power duplexers (3 antenna per sector)

A three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, andmedium power duplexers, is shown in Figure 13-26. Table 13-17 provides a summary ofthe equipment required for this configuration.


TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

DLNB

RxANTENNA

TxANTENNA

(SECTOR 1) (SECTOR 1) (SECTOR 1)


DUPLEXER

Non-HCOMB

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOAD

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the mastercabinet for sectors 2 and 3.

Table 13-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-inputCBF, air combining, diversity and medium power duplexers (3 antennas/sector)

Quantity Unit

9 Antennas


15 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB




30 Sep 2003


68P02900W21-M

GMR-0113�35

[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity,and medium power duplexers (2 antenna per sector)

A three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, andmedium power duplexers, is shown in Figure 13-27. Table 13-18 provides a summary ofthe equipment required for this configuration.

Figure 13-27 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

DLNB

(SECTOR 1) (SECTOR 1)


DUPLEXER

Non-HCOMB

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOAD


DUPLEXER

Tx/RxANTENNA

Table 13-18 Equipment required for 3 cabinets, 15 TCU configuration with 3-inputCBF, combining, diversity and medium power duplexers (2 antennas/sector)

Quantity Unit

6 Antennas


15 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB




30 Sep 200313�36


GMR-0168P02900W21-M

[GSM900] 3 sector (6/6/6), with cavity combining, diversity, and highpower duplexersA multiple cabinet, 18 TCU configuration with cavity combining, diversity, and high powerduplexers, is shown in Figure 13-28. Table 13-19 provides a summary of the equipmentrequired for this configuration.

An external equipment rack/cabinet is required for a high�power duplexer in an indoorinstallation.

Figure 13-28 3 sector (6/6/6), cavity combining, high power duplexers

IADU

DLNB

AB

66

RxANTENNA

Tx/RxANTENNA

Tx

Rx

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

CCB(OUTPUT)

CCB(EXTENSION)

ANT

MASTER M-Cell6 BTS CABINET M-Cell6 SIDE CABINET

HIGH POWERDUPLEXER

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 high power duplexer in the side cabinet.

Table 13-19 Equipment required for 3 RF cabinets, 18 TCU configuration withcavity combining, diversity and high power duplexers

Quantity Unit

6 Antennas



18 TCU

Transmitter

3 CCB (output)

3 CCB (extension)

Receiver

3 DLNB




30 Sep 2003


68P02900W21-M

GMR-0113�37


A three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, andmedium power duplexers, is shown in Figure 13-29. Table 13-20 provides a summary ofthe equipment required for this configuration.


TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

DLNB

RxANTENNA

TxANTENNA

(SECTOR 1) (SECTOR 1) (SECTOR 1)


DUPLEXER

Non-HCOMB

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOADRF LOAD

RF INPUT



Quantity Unit

9 Antennas


18 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB




30 Sep 200313�38


GMR-0168P02900W21-M


A three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, andmedium power duplexers, is shown in Figure 13-30. Table 13-21 provides a summary ofthe equipment required for this configuration.

Figure 13-30 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

DLNB

(SECTOR 1) (SECTOR 1)


DUPLEXER

Non-HCOMB

3-INPUTCBF

3-INPUTCBF

RF INPUT

RF LOADRF LOAD

RF INPUT


DUPLEXER

Tx/RxANTENNA

Table 13-21 Equipment required for 3 cabinets, 18 TCU configuration with 3-input CBF, combining, diversity and medium power duplexers (2 antennas/sector)

Quantity Unit

6 Antennas


18 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB




30 Sep 2003


68P02900W21-M

GMR-0113�39

[GSM900] 3 sector (8/8/8), with cavity combining, diversity andmedium power duplexers

A four cabinet, 24 TCU configuration with cavity combining, diversity and medium powerduplexers, is shown in Figure 13-31/ Figure 13-32. Table 13-22 provides a summary ofthe equipment required for this configuration.

Figure 13-31 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1)

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

CBF 0

Tx/RxANTENNA

Tx/RxANTENNA



DU

PLE

XE

R 2

DU

PLE

XE

R 1

DU

PLE

XE

R 0

CBF 1CBF 2

Rx REVBLOCK 0

IADU IN EXTENDER 1 M-Cell6 BTS CABINET


Rx REVBLOCK 1

Rx REVBLOCK 2

DLNB 0 IN EXTENDER 2 M-Cell6 BTS CABINET





30 Sep 200313�40


GMR-0168P02900W21-M

Figure 13-32 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)

IADU

DLNB

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

CCB(OUTPUT)

CCB(EXTENSION)

EXTENDER 1 M-Cell6 BTS CABINET

Extender 2 and extender 3 M-Cell6 cabinets configured similar tothe extender 1 cabinet for sectors 2 and 3.

TOMASTERM-Cell6

BTS CABINET

Rx REV BLOCK 0Rx REV BLOCK 1Rx REV BLOCK 2

RxANTENNA

(SECTOR 1)

TxANTENNA

(SECTOR 1)DUPLEXER 2DUPLEXER 1DUPLEXER 0

Table 13-22 Equipment required for 4 RF cabinets, 24 TCU configuration with cavitycombining, diversity and medium power duplexers

Quantity Unit

9 Antennas


24 TCU

Transmitter

3 CCB (output)

3 CCB (extension)

3 CBF

Receiver

3 DLNB

3 Rx extender block




30 Sep 2003


68P02900W21-M

GMR-0113�41

[GSM900] 3 sector (8/8/8), with cavity combining, diversity and bothhigh and medium power duplexers

A multiple cabinet, 24 TCU configuration with cavity combining, diversity and both highand medium power duplexers, is shown in Figure 13-33/ Figure 13-34. Table 13-23provides a summary of the equipment required for this configuration.

An external equipment rack/cabinet is required for a high power duplexer in an indoorinstallation.

Figure 13-33 3 sector (8/8/8), cavity combining, high and medium power duplexers(Part 1)

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

6 6

Tx/RxANTENNA

CBF 0

Tx/RxANTENNA

Tx/RxANTENNA



DU

PLE

XE

R 2

DU

PLE

XE

R 1

DU

PLE

XE

R 0

CBF 1CBF 2

Rx REVBLOCK 0



Rx REVBLOCK 1

Rx REVBLOCK 2






30 Sep 200313�42


GMR-0168P02900W21-M

Figure 13-34 3 sector (8/8/8), cavity combining, high and medium power duplexers(Part 2)

IADU

DLNB

A

66

Tx

RxTCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

CCB(OUTPUT)

CCB(EXTENSION)

ANT

EXTENDER 1 M-Cell6 BTS CABINET M-Cell6 SIDE CABINET

HIGH POWERDUPLEXERS

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 high power duplexer in the side cabinet.

Tx

Rx

ANT

Tx

Rx

ANT

AA





TOMASTERM-Cell6

BTS CABINET

DUPLEXER 2

Rx REV BLOCK 0

DUPLEXER 1DUPLEXER 0

Rx REV BLOCK 1Rx REV BLOCK 2

Tx/RxANTENNA

Tx/RxANTENNA

Tx/RxANTENNA


Table 13-23 Equipment required for 4 RF cabinets, 24 TCU configuration with cavitycombining, diversity and both high and medium power duplexers

Quantity Unit

6 Antennas



24 TCU

Transmitter

3 CCB (output)

3 CCB (extension)

3 CBF

Receiver

3 DLNB

3 Rx extender block





30 Sep 2003


68P02900W21-M

GMR-0113�43


A four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, andmedium power duplexers, is shown in Figure 13-35/ Figure 13-36. Table 13-24 provides asummary of the equipment required for this configuration.

Figure 13-35 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers(Part 1)

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

IADU

Rx EXTBLOCK

Tx/RxANTENNA

(SECTOR 3)

IADU

DLNB

DU

PLE

XE

R

RxANTENNA

(SECTOR 3)

TxANTENNA

(SECTOR 3)

HCOMB3-INPUT

CBF3-INPUT

CBF3-INPUT

CBF HCOMBHCOMB

TxANTENNA

(SECTOR 2)

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

Rx EXTBLOCK

TOEXTENDER 1

M-Cell6BTS CABINET

IADU

EXTENDER 2 M-Cell6 BTS CABINETEXTENDER 3 M-Cell6 BTS CABINET


30 Sep 200313�44


GMR-0168P02900W21-M

Figure 13-36 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers(Part 2)

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


IADU

DLNB Rx EXTBLOCK

Tx/RxANTENNA

(SECTOR 1)

TxANTENNA

(SECTOR 1)

IADU

DLNBDU

PLE

XE

R

DU

PLE

XE

R

RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 2)

HCOMB3-INPUT

CBF3-INPUT

CBF3-INPUT

CBF HCOMBHCOMB

RxANTENNA

(SECTOR 1)

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

TO EXTENDER 2M-Cell6 BTS CABINET

Rx EXT BLOCK


Quantity Unit

9 Antennas


24 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB





30 Sep 2003


68P02900W21-M

GMR-0113�45


A four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and mediumpower duplexers, is shown in Figure 13-37/ Figure 13-38. Table 13-25 provides asummary of the equipment required for this configuration.

Figure 13-37 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers(Part 1)

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


IADU

Rx EXTBLOCK

Tx/RxANTENNA

(SECTOR 3)

IADU

DLNB

DU

PLE

XE

R

DU

PLE

XE

R

TxANTENNA

(SECTOR 3)

HCOMB3-INPUT

CBF3-INPUT

CBF3-INPUT

CBF HCOMBHCOMB

RF INPUT

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

Rx EXTBLOCK

TOEXTENDER 1

M-Cell6BTS CABINETIADU

DUPLEXER


30 Sep 200313�46


GMR-0168P02900W21-M

Figure 13-38 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers(Part 2)

66

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


6 6

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB


IADU

DLNB Rx EXTBLOCK

Tx/RxANTENNA

(SECTOR 1)

Tx/RxANTENNA

(SECTOR 1)

IADU

DLNBDU

PLE

XE

R

DU

PLE

XE

R

DU

PLE

XE

R

Tx/RxANTENNA

(SECTOR 2)

Tx/RxANTENNA

(SECTOR 2)

HCOMB3-INPUT

CBF

3-INPUTCBF

3-INPUTCBF HCOMBHCOMB

RF LOAD

RF INPUT

RF LOAD

RF INPUT

RF LOAD

TO EXTENDER 2M-Cell6 BTS CABINET

DUPLEXERRx REV BLOCK 1

DU

PLE

XE

R

RF INPUT

Table 13-25 Equipment required for 4 cabinets, 24 TCU configuration with 3-inputCBF, combining, diversity and medium power duplexers (2 antennas/sector)

Quantity Unit

6 Antennas


24 TCU

Transmitter

6 3-input CBF


Receiver

3 DLNB





30 Sep 2003


68P02900W21-M

GMR-0113�47

[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown inFigure 13-39. Table 13-26 provides a summary of the equipment required for thisconfiguration.

Figure 13-39 3 sector (2/2/2), hybrid combining

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

LNA

HYBRID

A B

2

TxANTENNA

RxANTENNAS

LNA

A B

RxANTENNAS

LNA

A B

RxANTENNAS

HYBRID HYBRID

TxANTENNA

TxANTENNA


M-Cell6 BTS CABINET

2 2 2 2 2

TxBPFTxBPFTxBPF


Quantity Unit

9 Antennas


6 TCU

Transmitter

3 TxBPF

3 Hybrid combiner

Receiver

3 LNA


30 Sep 200313�48


GMR-0168P02900W21-M

[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, andmedium power duplexers

A single cabinet, six TCU configuration with hybrid combining, diversity, and mediumpower duplexers, is shown in Figure 13-40. Table 13-27 provides a summary of theequipment required for this configuration.

Figure 13-40 3 sector (2/2/2), hybrid combining, medium power duplexers

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

TCU

AB

LNA

HYBRID 2

Tx/RxANTENNA

RxANTENNAS

LNA

RxANTENNAS

LNA

RxANTENNAS

HYBRID HYBRID

Tx/RxANTENNA

Tx/RxANTENNA


M-Cell6 BTS CABINET

2 2 2 2 2

DU

PLE

XE

R

DU

PLE

XE

R

DU

PLE

XE

R

Table 13-27 Equipment required for single cabinet, 6 TCU configuration with hybridcombining, diversity and medium power duplexers

Quantity Unit

6 Antennas


6 TCU

Transmitter

3 Hybrid combiner

Receiver

3 LNA




30 Sep 2003


68P02900W21-M

GMR-0113�49

M-Cell2 cabinetsNOTE DIversity is assumed in all figures, unless stated otherwise.

[GSM900] 2 carrier, single sector, with hybrid combining anddiversityA single cabinet, two TCU configuration with hybrid combining and diversity, is shown inFigure 13-41. Table 13-28 provides a summary of the equipment required for thisconfiguration.

Figure 13-41 2 carrier, single sector, hybrid combining

2

TCU

AB

TCU

AB

CBF 2

RxANTENNAS

DLNB

A B

TxANTENNA

M-Cell2 BTS CABINET


Quantity Unit

3 Antennas


2 TCU

Transmitter

1 CBF

Receiver

1 DLNB


30 Sep 200313�50


GMR-0168P02900W21-M

[GSM900] 2 carrier, single sector, with hybrid combining, diversity,and medium power duplexer

A single cabinet, two TCU configuration with hybrid combining, diversity, and mediumpower duplexer, is shown in Figure 13-42. Table 13-29 provides a summary of theequipment required for this configuration.

Figure 13-42 2 carrier, single sector, hybrid combining, medium power duplexer

2

TCU

AB

TCU

AB

CBF 2

RxANTENNA

DLNB

A B

Tx/RxANTENNA

M-Cell2 BTS CABINET

DUPLEXER


Quantity Unit

2 Antennas


2 TCU

Transmitter

1 CBF

Receiver

1 DLNB




30 Sep 2003


68P02900W21-M

GMR-0113�51

[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-43.Table 13-30 provides a summary of the equipment required for this configuration.

Figure 13-43 2 sectors (1 carrier per sector)

TCU

AB

TCU

AB

RxANTENNAS

DLNB

A B

TxANTENNA

M-Cell2 BTS CABINET

RxANTENNAS

DLNB

A B

CBF

TxANTENNA

CBF

Table 13-30 Equipment required for single cabinet, 2 TCU configuration withdiversity

Quantity Unit

6 Antennas


2 TCU

Transmitter

2 CBF

Receiver

2 DLNB


30 Sep 200313�52


GMR-0168P02900W21-M

[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU configuration with air combining and diversity, is shown inFigure 13-44. Table 13-31 provides a summary of the equipment required for thisconfiguration.

Figure 13-44 2 carrier, single sector, air combining

2

TCU

AB

TCU

AB

2

RxANTENNA

LNA

AB

TxANTENNA

M-Cell2 BTS CABINET

TxBPF

DUPLEXER

Tx/RxANTENNA

Table 13-31 Equipment required for single cabinet, 2 TCU configuration with aircombining and diversity

Quantity Unit

3 Antennas


2 TCU

Transmitter

1 TxBPF

Receiver

1 LNA




30 Sep 2003


68P02900W21-M

GMR-0113�53

[DCS1800] 2 sectors, with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-45.Table 13-32 provides a summary of the equipment required for this configuration.

Figure 13-45 2 sectors

TCU

AB

TCU

AB

RxANTENNAS

LNA

A B

TxANTENNA

M-Cell2 BTS CABINET

TxBPF

RxANTENNAS

LNA

A B

TxBPF

TxANTENNA

Table 13-32 Equipment required for single cabinet, 2 TCU configuration with diversity

Quantity Unit

6 Antennas


2 TCU

Transmitter

2 TxBPF

Receiver

2 LNA


30 Sep 200313�54


GMR-0168P02900W21-M

30 Sep 2003


68P02900W21-M

GMR-0114�1

Chapter 14

Previous generation BSC planning

steps and rules

GSR6 (Horizon II)

30 Sep 200314�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-0114�3

Chapter overview

Introduction

This chapter (included for reference purposes only) provides the planning steps andrules for the previous generation of BSC equipment. The planning steps and rules for thepre M-Cell range of BTS equipment are contained in Chapter 15 of this manual.

NOTE This chapter is not indexed as it is provided for referencepurposes only.


S BSC planning overview.

S Capacity calculations.

� Determining the required BSS signalling link capacities.

� Determine the number of RSLs required.

� Determine the number of MTLs required.

� BSC GPROC functions and types.

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

GSR6 (Horizon II)BSC planning overview

30 Sep 200314�4


GMR-0168P02900W21-M

BSC planning overview

Introduction

To plan the equipage of a BSC certain information must be known. The major itemsinclude:

S The number of BTS sites to be controlled.

S The number of RF carriers (RTF) at each BTS site.

S The number of TCHs at each site.

S The total number of TCHs under the BSC.

S The number of cells controlled from each BSC site should not exceed themaximum per BSC given in the BSC system capacity section of Chapter 5.

S The physical interconnection of the BTS sites to the BSC.

S The location of the XCDR function.

S The path for the OML links to the OMC-R.



S The traffic load to be handled (also take future growth into consideration).

S The number of MSC to BSC trunks.

GSR6 (Horizon II) BSC planning overview

30 Sep 2003


68P02900W21-M

GMR-0114�5


Planning a BSC involves the following steps:

1. Plan the number of E1 or T1 links between the BSC and BTS site(s), refer to thesection Determining the required BSS signalling link capacities in thischapter.

2. Plan the number of RSL links between the BSC and BTS site(s), refer to thesection Determining the RSLs required in this chapter.

3. Plan the number of MTL links between the BSC and MSC, refer to the sectionDetermining the number of MTLs required in this chapter.

4. Plan the number of GPROCs required, refer to the section Generic processor(GPROC, GPROC2) in this chapter.

5. Plan the number of XCDR/GDPs required, refer to the section Transcoding in thischapter.

6. Plan the number of MSI/MSI-2s required, refer to the section Multiple serialinterface (MSI, MSI-2) in this chapter.

7. Plan the number of KSWs and timeslots required, refer to the section Kiloportswitch (KSW) in this chapter.

8. Plan the number of BSU shelves, refer to the section BSU shelves in this chapter.

9. Plan the number of KSWXs required, refer to the section Kiloport switchextender (KSWX) in this chapter.

10. Plan the number of GCLKs required, refer to the section Generic clock (GCLK) inthis chapter.

11. Plan the number of CLKXs required, refer to the section Clock extender (CLKX)in this chapter.

12. Plan the number of LANXs required, refer to the section LAN extender (LANX) inthis chapter.

13. Plan the number of PIXs required, refer to the section Parallel interface extender(PIX) in this chapter.

14. Plan the number of BIB or T43s required, refer to the section Line interfaces(BIB, T43) in this chapter.

15. Plan the power requirements, refer to the section Digital shelf power supply inthis chapter.

16. Plan the number of BBBXs required, refer to the section Battery backup board(BBBX) in this chapter.

17. Verify the planning process, refer to the section Verify the number of BSUshelves and BSSC2 cabinets in this chapter.


30 Sep 200314�6


GMR-0168P02900W21-M


Introduction

The throughput capacities of the BSC processing elements (for example, GPROC,GPROC2) and the throughput capacities of its data links, determines the number ofsupported traffic channels (TCHs). These capacities are limited by the ability of theprocessors, and links to handle the signalling information associated with these TCHs.

This section provides information on how to calculate processor requirements, signallinglink capacities and BSC processing capacities. This section describes:

S Traffic models.





30 Sep 2003


68P02900W21-M

GMR-0114�7


BSC signalling traffic model

For a GSM system the throughput of network entities, including sub-components,depends upon the assumed traffic model used in the network design or operation. Trafficmodels are fundamental to a number of planning actions.

The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends onits ability to process information transported through signalling links connecting it to theother network elements. These elements include MSC, BTSs, and the OMC-R.Depending on its device type and BSC configuration, a GPROC may be controllingsignalling links to one or more other network elements. A capacity figure can be statedfor each GPROC device type in terms of a static capacity such as the number of physicalsignalling links supported, and a dynamic capacity such as processing throughput.

In general telephony environments, processing and link throughput capacities can bestated in terms of the offered call load. To apply this for the GSM BSC, all signallinginformation to be processed by the BSC, is related to the offered call load (the amount oftraffic offered/generated by subscribers). When calls are blocked due to all trunks or allTCHs busy, most of the signalling associated with call setup and clearing still takes place,even though few or no trunk resources are utilized. Therefore, the offered call load (whichincludes the blocked calls) should be used in planning the signalling resources (forexample; MTLs and RSLs).

In the case where the BSC has more than enough trunks to handle the offered traffic,adequate signalling resources should be planned to handle the potential carried traffic.The trunk count can be used as an approximate Erlang value for the potential carriedload.

As a result, the signalling links and processing requirements should be able to handle thegreater of the following:

S The offered load.

S The potential carried load.

To determine the link and processing requirements of the BSC, the number of trunks orthe offered call load in Erlangs (whichever is greater) should be used.

BSC capacity planning requires a model that associates the signalling generated from allthe pertinent GSM procedures: call setup and clearing, handover, location updating andpaging, 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 thenumber of call attempts processed. The rate at which call attempts are processed is afunction of the offered call load and the average call hold time.

Figure 14-1 graphically depicts various factors that should be taken into account whenplanning a BSS.


30 Sep 200314�8


GMR-0168P02900W21-M


MSC

A INTERFACE (TERRESTRIAL LINKS)�C7 SIGNALLING LINKS�X.25 CONTROL LINK*�REQUIRED TRUNKS

WITH SUBMULTIPLEXING TRANSCODING AT MSC1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK*1 x 64 kbit/s CIRCUIT/ XBL1 x 64 kbit/s CIRCUIT/4 TRUNKS

WITHOUT SUBMULTIPLEXING TRANSCODING AT BSC1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK*1 x 64 kbit/s CIRCUIT/TRUNK

1 x 64 kbit/s CIRCUIT/LAPD SIGNALLING LINK2 x 64 kbit/s CIRCUITS/DRCU/SCU


AIR INTERFACE�TCHs AND SIGNALLING TSs�TYPICALLY 2% BLOCKING TRANSCODING MUST BE LOCATED AT THE

BSC, OR BETWEEN THE BSC AND MSC


OR MSC SITE

THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED FROM THE # OFTRUNKS REQUIRED TO CARRY THE SUMMATION OF AIR INTERFACE TRAFFIC(IN ERLANGS, TYPICALLY USING 1% BLOCKING) FROM ALL BTSs




THE # OF TCHs REQUIRED (USING TYPICALLY 2% BLOCKING) TO CARRYSUBSCRIBER TRAFFIC THE TCHs PLUS THE REQUIRED SIGNALLING TSs DIVIDED BY EIGHTDETERMINES THE CARRIERS REQUIRED (ON A BTS/SECTOR BASIS)

TRANSCODER

BSC

BTS




30 Sep 2003


68P02900W21-M

GMR-0114�9


The parameters required to calculate BSC processing and signalling link capacities arelisted in Table 14-1 with their typical values.

Two methods for determining capacity are given. The first method is based on the typicalcall parameters given in Table 14-1 and simplifies planning to lookup tables, or simpleformulae indicated in standard traffic model planning steps. When the call parametersbeing planned for differ significantly from the standard traffic model given in Table 14-1 inthis case more complex formulae must be used as indicated in non-standard trafficmodel planning steps.





Number of handovers per call H = 2.5



Location update factor L = 2

Paging rate in pages per second P = 3

Ratio of intra-BSC handovers to all handovers i = 0.6

Percent link utilization (MSC to BSS) U (MSC � BSS) = 0.20



Blocking for MSC�BSS Trunks PB�Trunks = 1%

The location update factor (L) is a function of the ratio of location updates to calls (l), theratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) orlong message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSIdetach is disabled) as in the first formula given below. When IMSI detach is enabled, thesecond or third of the formulas given below should be used. The type of IMSI detachused is a function of the MSC.


L = I


L = I + 0.2 * I


L = I + 0.5 * I


30 Sep 200314�10


GMR-0168P02900W21-M






Pages per call PPC = P * (T/N)


To calculate link and processing capacity values, certain signalling message sequencepatterns and message sizes have been assumed for the various procedures included inthe signalling traffic model. New capacity values may have to be calculated if the actualmessage patterns and message sizes differ significantly from those assumed. Theassumptions used for the capacity calculations in this manual are summarized below.The number of uplink and downlink messages with the respective average messagesizes (not including link protocol overhead) for each procedure are provided inTable 14-3.

Table 14-3 Procedure capacities

Procedure MSC to BSC link





SMS-P to P (see note below)




Paging 1 downlink message with average size of 30 bytes

NOTE The actual number and size of messages required by SMSdepend on the implementation of the SMS service centre. Thenumbers given are estimates for a typical implementation. Thesenumbers may vary.

An additional assumption, which is made in determining the values listed in Table 14-3, isthat the procedures not included in the traffic model are considered to have negligibleeffect.


30 Sep 2003


68P02900W21-M

GMR-0114�11

Link capacities

The level of link utilization is largely a matter of choice of the system designer. A designthat has more links running at a lower message rate can have the advantage of offeringbetter 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 offerreduced queueing delays for signalling messages. A design that utilizes fewer links at ahigher message rate, reduces the number of 64 kbit/s circuits required for signalling, andpotentially reduces the number of resources (processors, data ports) required in theMSC. 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 (LCF�MTLs)may become overloaded.

C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from thefailed link to be redistributed among the remaining functioning links. A C7 link set officiallyhas at least two and at most 16 links. The failure of links, for any reason, cause thesignalling to be shared across the remaining members of the link set. Therefore, thedesign must plan for reserve link and processing capacity to support a certain number offailed signalling links.

GSR6 (Horizon II)Determining the RSLs required

30 Sep 200314�12


GMR-0168P02900W21-M

Determining the RSLs required

Introduction

Each BTS site which is connected directly to the BSC, including the first site in a daisychain, must be considered individually. Once individual RSL requirements are calculatedthe total number of LCFs can be determined for the BSC.


The following factors should be considered when planning the provision of RSL (LAPDsignalling) links from the BSC to BTS sites:

S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTSsite. One link can support multiple collocated cells. As the system grows,additional signalling links may be required. Refer to the section Determining therequired BSS signalling link capacities in this chapter to determine the numberof RSL links required.

S If closed loop daisy chains are used, each site requires an RSL in both directions.

S The provision of additional RSL links for redundancy.


The number of BSC to BTS signalling links (RSL) must be determined for each BTS.This number depends on the number of TCHs at the BTS. Table 14-4 gives the numberof RSLs required for a BTS to support the given number of TCHs. These numbers arebased on the typical call parameters given in the standard traffic model column ofTable 14-1. If the call parameters differ significantly from the standard traffic model, usethe formulae for the non-standard traffic model.


n = number of TCHs at the BTS Number of 64 kbit/sRSLs

Number of 16 kbit/sRSLs

n <= 30 1 1

30 < n <= 60 1 2

60 < n <= 90 1 3

90 < n <= 120 1 4

120 < n <= 150 2 5

150 < n <= 180 2 6

180 < n <= 210 2 7

210 < n <= 240 2 8

A BTS shall support either 64 kbit/s RSLs or 16 kbit/s RSLs, but not both.

NOTE

GSR6 (Horizon II) Determining the RSLs required

30 Sep 2003


68P02900W21-M

GMR-0114�13


If the call parameters differ significantly from those given in Table 14-1, use the followingformula to determine the required number of 64 kbit/s RSLs (rounded up to the nextnearest integer).

NBSC�BTS �(n * (95 � 67 * S � 35 * H � 25 * L))

(1000 * U * T)� 6 * P

(1000 * U)

If the call parameters differ significantly from those given in Table 5-2, use the followingformula to determine the required number of 16 kbit/s RSLs (rounded up to the nextnearest integer).

NBSC�BTS � �(n * (95 � 67 * S � 35 * H � 25 * L))(1000 * U * T)

� 6 * P(1000 * U)

� * 4

Where: NBSC to BTS is: the number of MSC to BSC signalling links.

n the number of TCHs at the BTS site.


H the number of handover per call.


U the percent link utilization (0.25).


P the paging rate in pages per second.


Determine the number of E1 links required to connect to a BTS. Redundant links may beadded, if required.

N �[(nTCH + L16) / 4] + L64

31

Where: N is: the minimum number of E1 links required (rounded upto an integer).

nTCH the number of traffic channels at the BTS.



NOTE This formula includes both L16 and L64 to provide necessarynumber of RSLs. As above, either L16 or L64 RSL can be used,but not both, to a single BTS.


30 Sep 200314�14


GMR-0168P02900W21-M


Determine the number of T1 links required to connect to a BTS. Redundant links may beadded, if required.

N �[(nTCH + L16) / 4] + L64

24

Where: N is: the minimum number of T1 links required (rounded upto an integer).

nTCH the number of traffic channels at the BTS.



NOTE This formula includes both L16 and L64 to provide necessarynumber of RSLs. As above, either L16 or L64 RSL can be used,but not both, to a single BTS.

GSR6 (Horizon II) Determining the RSLs required

30 Sep 2003


68P02900W21-M

GMR-0114�15

Calculate the number of LCFs for RSL processing

LCFs for BSC to BTS links and Layer 3 call processing

There are three steps needed to determine the number of LCF GPROCs required tosupport the BSC to BTS signalling links (RSL) and layer 3 call processing.

1. Calculate the number of LCFs required to support the RSLs.

2. Calculate the number of LCFs required to support the layer 3 call processing.

3. The larger of the numbers calculated in steps 1 and 2 is the number of LCFsrequired to support the RSLs signalling links and layer 3 call processing.

Step 1

Determine the number of LCFs required to support RSLs. There are two equations; onefor release GSR3; and one for GSR2 and 1.4.x.x.

For GSR3 using only GPROC2.

GRSL �(R � 2 * B)

120

For GSR2 and 1.4.x.x, or GSR3 using GPROC.

GRSL �(R � 2 * B)

40

Where: GRSL is: the number of LCFs required to support the BSC toBTS signalling links (RSL).

R the number RTFs (radio carriers).


Step 2

The second step is to determine the number of GPROCs required to support the layer 3call processing. There are two methods for calculating this number. The first is usedwhen the call parameters are similar to those listed in Table 14-1. The second method isto be used when call parameters differ significantly from those listed in Table 14-1.


For a GPROC2:

GL3 � � n440

� B15

� C35� * � 1

2.5�

For a GPROC:

GL3 � n440

� B15

� C35

Where: GL3 is: the number of LCF GPROCs or LCF GPROC2srequired to support the layer 3 call processing.

n the number of TCH under the BSC.




30 Sep 200314�16


GMR-0168P02900W21-M



For a GPROC2:

GL3 � �n * (1 � 0.7 * S � 0.5 * H * (1 � 0.3 * i) � 0.5 * L)(11.3 * T)

� (0.006 � 0.02 * P) * B � C35� * � 1

2.5�

For a GPROC:

GL3 �(n * (1 � 0.7 * S � 0.5 * H * (1 � 0.3 * i) � 0.5 * L))

(11.3 * T)� (0.006 � 0.02 * P) * B � C

35

Where: GL3 is: the number of LCF GPROCs or LCF GPROC2srequired to support the layer 3 call processing.

n the number of TCHs under the BSC.



i the ratio of intra-BSC handover to all handover.



P the paging rate in pages per second.



Step 3

The number of LCFs required is the greater of GRSL and GL3.

Assigning BTSs to LCFs

The BTSs must be assigned to the LCFs in such a way as to not overload any one LCF.Verify that the following conditions are met for each LCF:

For a GPROC2:

2 * (number of RSLs) + number of carriers supported is NOT greater 120 for GSR3.

For a GPROC:

2 * (number of RSLs) + number of carriers supported is NOT greater than 40.

NOTE If these conditions are exceeded, one or more additionalprocessors will be needed to share the load.


30 Sep 2003


68P02900W21-M

GMR-0114�17


Introduction

MTLs carry signalling traffic between the MSC and BSC. The number of required MTLsdepends upon the BSS configuration size and traffic model. MTLs are carried on E1 orT1 links between the MSC and BSC, which are also used for traffic.


The following factors should be considered when planning the links from the BSC toMSC:

S Determine traffic requirements for the BSC. Traffic may be determined using eitherof the following methods:

� Multiply the number of subscribers expected to use the BSC by the averagetraffic per subscriber.

or

� Sum the traffic potential of each BTS under the BSC; determined by thenumber of TCHs available, the number of TCHs required or the subscriberpotential.

S Determine the number of trunks to support the traffic requirements of the BSCusing Erlang B tables at the required blocking rate.


30 Sep 200314�18


GMR-0168P02900W21-M


The number of MSC to BSC signalling links (MTL) required depends on the desired linkutilization, the type and capacity of the GPROCs controlling the MTLs. C7 uses a 4 bitnumber, the Signalling Link Selection (SLS) generated by the upper layer to load sharemessage traffic among the in service links of a link set. When the number of in servicelinks is not a power of 2, some links may experience a higher load than others.

The number of MTLs is a function of the number of MSC to BSC trunks or the offeredcall load. Table 14-5 gives the recommended minimum number of MSC to BSC signallinglinks based on the typical call parameters given in Table 14-1. The value for N is thegreater of the following:

S The offered call load (in Erlangs) from all the BTSs controlled by the BSCwhichever is greater.


The offered call load for a BSS is the sum of the offered call load from all of the cells ofthe 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 TCHsand 2% blocking, the offered call load is 9.01 Erlangs.

Table 14-5 Number of MSC to BSC signalling links

N = the number of MSC to BSC Trunksor the offered load from the BTSs

( hi h i th t t)

Minimum numberof MTLs

Recommendednumber of MTLs

(whichever is the greatest) (each MTL at <= 20% link utilization)

N <= 145 1 2

145< N <=290 2 3

290 < N <= 385 3 4

385 < N <= 580 4 5

580 < N <= 775 6 7

775 < N <= 1160 8 9

1160 < N <= 1375 16 16

NOTE The capacities shown are based on the standard traffic modelshown in Table 14-1.


30 Sep 2003


68P02900W21-M

GMR-0114�19


If the call parameters differ significantly from those given in Table 14-1, the followingprocedure is used to determine the required number of MSC to BSC signalling links:

1. Use the formula given below to determine the maximum number of Erlangssupported by a C7 signalling link (nllink).

nllink �(1000 * U * T)

((67 � 47 * S � 31 * H * (1 � 0.8 * i) � 25 * L) � 14 * PPC)

2. Use the formula given below to determine the maximum number of Erlangssupported by a GPROC or GPROC2 (LCF�MTL) supporting a C7 signalling link(nlLCF�MTL).

For a BSC with a mix of GPROC and GPROC2:

nlLCF�MTL �3.6 * T

((1 � 0.7 * S � 0.5 * H * (1 � 0.6 * i) � 0.5 * L) � PPC * (0.01 * B � 0.05))

For a BSC with only GPROC2:

nlLCF�MTL �2.5 * (3.6 * T)

((1 � 0.7 * S � 0.5 * H * (1 � 0.6 * i) � 0.5 * L) � PPC * (0.01 * B � 0.05))

3. The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is thesmaller of the two numbers from Steps 1 and 2.

4. Since the signalling traffic is uniformly distributed over 16 logical links, and theselogical links will be assigned to the MTLs (physical links). We need to firstdetermine the amount of traffic each logical link holds (nllogical):

nllogical � N16

5. Next we need to determine the number of logical links each MTL (physical link)can handle (nlog-per-MTL):

nlog�per�MTL � ROUND DOWN � nlmin

nllogical�


mtls � ROUND UP � 16nlog�per�MTL

�� R � 16

NOTE mtls should not exceed 16.


30 Sep 200314�20


GMR-0168P02900W21-M

Where: U is: the percent link utilization (0.25).




i the ratio of intra-BSC handover to all handover.


PPC

B

mtls

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.

ROUNDUP rounding up to the next integer.

N the greater of either the offered traffic load orpotential traffic load carried (approximately equal tothe number of MSC to BSC trunks).


30 Sep 2003


68P02900W21-M

GMR-0114�21


The purpose of the LCF GPROC or LCF GPROC2 device type is to support the functionsof MSC link protocol, layer 3 call processing, and the BTS link protocol. It isrecommended that an LCF GPROC supports either an MTL or one to eight BTSs, withup to 15 RSLs and layer 3 call processing; and that an LCF GPROC2 supports either twoMTLs or one to 15 BTSs (GSR3), with up to 31 RSLs and layer 3 call processing.

NOTE It is not recommended that an LCF support both an MTL andBSC to BTS signalling links.

The higher capacities available with GPROC2 are only achievedif GPROC2s are the only processor type in use in a GSR3system. If GPROC is also used then GPROC planning formulaeshould be used, even for GPROC2.


Since one LCF GPROC can support one MTL, the number of required LCF is the sameas the number of required MTLs (MSC to BSC links) obtained from Table 14-1 or frommtls calculated in the non-standard traffic model from the previous section.

For GPROC2, if the number of required MTLs is obtained from Table 14-1 the number ofLCF is:

NLCF � ROUNDUP�MTLs2�

However, if the traffic model does not conform to the standard model:

NLCF � mtls, if 2 � nllink � nlLCF�MTL

otherwise:





nllink calculated in the previous section.


MSC to BSC signalling over a satellite link

The BSC supports preventive cyclic retransmission (PCR) to interface to the MSC over asatellite link. PCR retransmits unacknowledged messages when there are no newmessages to be sent. This puts an additional processing load on the GPROCs(LCF�MTLs) controlling the C7 signalling links. It is recommended that when PCR isused, that the number of MTLs (and thus the number of LCF�MTLs) be doubled from thenumber normally required.

GSR6 (Horizon II)Generic processor (GPROC, GPROC2)

30 Sep 200314�22


GMR-0168P02900W21-M

Generic processor (GPROC, GPROC2)

Introduction

The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as ageneric control processor board. GPROCs are assigned functions and are then known bytheir function names.

This section describes the BSC GPROC types and their functions. The BSCconfiguration type and GPROC device type, are essential factors for BSC planning.

GPROC functions and types

There are two GPROC hardware types, GPROC and GPROC2. GPROC2 is needed, inGSR3, for master processor functionality.

The GPROC is the basic building block of a distributed architecture. The GPROCprovides the processing platform for the BSC. By using multiple GPROCs software taskscan be distributed across GPROCs to provide greater capacity. The set of tasks that aGPROC is assigned, depends upon the configuration and capacity requirements of theBSC. Although every GPROC is similar from a hardware standpoint, when a group oftasks are assigned to a GPROC, it is considered to be a unique GPROC device type orfunction in the BSC configuration management scheme.

There are a limited number of defined task groupings in the BSC, which result in thenaming of four unique GPROC device types for the BSC. The processing requirement ofa particular BSC determines the selection and quantity of each GPROC device type.

The possible general task groupings or functions for assignment to GPROCs are:

S BSC common control functions.

S OMC-R communications � OML (X.25) including statistic gathering.

S MSC link protocol (C7).

S BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD).

S Cell broadcast centre link (CBL).

The defined GPROC devices and functions for the BSC are:

S Base Site Control Processor (BSP).

S Link Control Function (LCF).

S Operations and Maintenance Function (OMF).

S Code Storage Facility Processor (CSFP).

At a combined BSC BTS site the BTF and DHP are additional GPROC function and typein the network element.

NOTE Prior to GSR3 a separate OMF was needed if OML trafficexeeded a defined threshold. With GSR3 and GPROC2 the useof a separate OMF becomes optional.

GSR6 (Horizon II) Generic processor (GPROC, GPROC2)

30 Sep 2003


68P02900W21-M

GMR-0114�23

BSC types

The BSC is configured as one of three types; the type is determined by the GPROCspresent.

NOTE With GSR3, and the use of GPROC2s, BSC type 1 is the onlyconfiguration required.

S BSC type 0

� Master GPROC.

Running the BSP.

NOTE BSC type 0 is not recommended for operating BSC. Beginningwith 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 operationsand maintenance functionalities.

� Link control function (LCF).

Running the radio signalling link (RSL) and layer 3 processing or MTL (C7signalling 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 controllinks to the OMC-R).

The number of serial links per GPROC must be determined for each site. The currentvalues are either 8 or 16, with 16 being the default value. One link is reserved for eachmodule, so the number of available serial links is either 7 or 15.


30 Sep 200314�24


GMR-0168P02900W21-M


The following factors should be considered when planning the GPROC complement:

S Each BSC requires:

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

S 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 A maximum of eight GPROCs can be supported in a BSU shelf.

S The master GPROC slot (20) in the first shelf should always be populated toenable communication with the OMC-R.

S For redundancy each BSC should be equipped with a redundant BSP and anadditional GPROC to provide redundancy for the signalling LCFs. Where multipleshelves exist, each shelf should have a minimum of two GPROCs to provideredundancy within that shelf.


30 Sep 2003


68P02900W21-M

GMR-0114�25

Link control function, using GPROC2 exclusively (GSR3 only)

The planning rules for LCFs exclusively using GPROC2 are:

S A single GPROC2 will support two MTLs, each working at 20% link utilization.

S A single GPROC2 will support up to 15 BTS sites and 31 RSLs, limited to thefollowing calculation:



NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limitof 24 carriers).

S The link utilization of an RSL should not exceed 25%.

S Up to 17 LCFs can be equipped.

NOTE 1. If both GPROC2 and GPROC are used in the same BSCthen the GPROC maximums apply to GPROC2. That is, theGPROC2s can handle only as much traffic as a GPROC.

2. In some cases the software will allow maximums greater thanthe planning guide, to allow ease of capacity expansion in futurereleases, but it is not supported with this software release.

3. Combining MTL and RSL processing on a single GPROC2 isnot recommended.

S A maximum of 15 BTS sites can be controlled by a single LCF. All RSLs (LAPDlinks) for the BTSs must terminate on the same GPROC2, so if return loops areused the maximum number of BTS sites will be 15 (if GPROC_slot parameter =31). If the GPROC_slot parameter is set to 16 then at most 15 RSLs may existwhich would support up to seven BTS sites.

NOTE The number of serial links per GPROC must be determined foreach site, the current values are either:

For GPROC2; 16 or 32, with 16 being the default value.

For GPROC; 8 or 16, with 16 being the default value.

One link is reserved for each board (GPROC test purposes) sothe number of available serial links is either 15 or 31 forGPROC2, and is 7 or 15 for GPROC.

When GPROC2s are not used exclusively, the LCF planning rules using GPROCs in thenext section should be used.


30 Sep 200314�26


GMR-0168P02900W21-M

Link control function, using GPROC

LCF planning rules using GPROC are:

S A single GPROC will support a single MTL working at 20% link utilization.

S A single GPROC will support up to 8 BTS sites and 15 RSLs, limited to thefollowing calculation:



NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limitof 24 carriers).

S The link utilization of an RSL should not exceed 25%.

S Up to 17 LCFs can be equipped.

NOTE Combining MTL and RSL processing on a single GPROC is notrecommended.

S A maximum of 8 BTS sites can be controlled by a single LCF. All RSLs (LAPDlinks) for the BTSs must terminate on the same GPROC, so if return loops areused the maximum number of BTS sites will be seven (if GPROC_slotparameter =16). If the GPROC_slot parameter is set to 8 then at most 7 RSLsmay exist which would support up to 3 BTS sites.

NOTE The number of serial links per GPROC must be determined foreach site.

For GPROC the valid values are:Eight or 16 (default). One link is reserved for each board(GPROC test purposes) so that the number of available seriallinks is either 7 or 15.

GPROC planning actions (GSR3)

Determine the number of GPROC or GPROC2s required.

NGPROC2 � 2B � L � C � R

Where: NGPROC2 is: the total number of GPROC or GPROC2s required.

B the number of BSP GPROC or GPROC2s (2B forredundancy).

L the number of LCF GPROC or GPROC2s.

C the number of CSFP GPROC or GPROC2s.

R the number of pool GPROC or GPROC2s (forredundancy).

NOTE If dedicated GPROC or GPROC2s are required for either theCSFP or OMF functions then they should be provisionedseparately.


30 Sep 2003


68P02900W21-M

GMR-0114�27

GPROC planning actions (GSR2 and earlier)

Determine the number of GPROCs required.

NGPROC � 2B � L � C � O � R

Where: NGPROC is: the total number of GPROCs required.

B the number of BSP GPROCs (2B for redundancy).

L the number of LCF GPROCs.

C the number of CSFP GPROCs.

O OMF GPROCs.

R the number of pool GPROCs (for redundancy).

Cell broadcast link

The cell broadcast link (CBL) connects the BSC to the cell broadcast centre. For typicalapplications (less than ten messages per second), this link can exist on the same LCF asthat used to control BTSs. The CBL should not be controlled by a LCF�MTL (a GPROCcontrolling an MTL).

OMF GPROC required

The BSC type 2 configuration offloads many of the O&M functions and control of theinterface to the OMC-R from the BSP. One of the major functions off loaded from theBSP is the central statistics process. When determining the total number of statistics,consider the number of instances of that statistic.

NST � (ECS � C) � (TCS � n) � SX25LAPD (L � X � B)

Where: NST is: the total number of statistics.

ECS the number of enabled cell statistics


Tcs the number of traffic enabled channel statistics.

n the number of traffic channels.

SX25LAPD the number of X.25/LAPD statistics.

L the number of RSLs.

X the number of OMLs.

B the number of XBLs

NOTE The formula assumes that the same cell and channel statisticsare enabled across all cells.


30 Sep 200314�28


GMR-0168P02900W21-M

Code storage facility processor

The BSS supports a GPROC acting as the code storage facility processor (CSFP). TheCSFP allows pre-loading of a new software release while the BSS is operational.

If a dedicated GPROC is to exist for the CSFP, an additional GPROC will be required.

When M-Cell BTSs are connected to the BSC, a dedicated CSFP is required at the BSCand a second dedicated CSFP should be equipped for redundancy.

The BSS supports a method whereby a dedicated CSFP GPROC is not required. Thismethod is called configure CSFP and works as follows:

The system can borrow certain devices and temporarily convert them into a CSFP, andwhen the CSFP functionality is no longer needed the device can be converted back intoits previous device. The devices the system can borrow are a redundant BSP/BTP or apooled GPROC.

This functionality allows an operator who already has either a redundant BSP/BTP or apooled GPROC in service to execute a command from the OMC-R to borrow the deviceand convert it into a CSFP. The operator can then download the new software load ordatabase and execute a CSFP swap. Once the swap has been completed and verifiedas successful, the operator can return the CSFP back to the previous redundant orpooled device type via a separate command from the OMC-R.

See Service Manual: BSC/RXCDR (68P02901W38) for more details.

GPROC redundancy

BSP redundancy

The failure of the BSP GPROC will cause a system outage. If the BSC is equipped with aredundant BSP GPROC, then the system will restart under the control of the redundantBSP GPROC. If the BSC is not equipped with a redundant BSP and the BSP GPROCwere to fail, the BSC would be inoperable.

Pooled GPROCs for LCF and OMF redundany

The BSS supports pooled GPROCs for LCF and OMF redundancy. By equippingadditional GPROCs for spares, if an LCF or the OMF GPROC were to fail, the systemsoftware will automatically activate a spare GPROC from the GPROC pool to replace thefailed GPROC.


30 Sep 2003


68P02900W21-M

GMR-0114�29

Transcoding

Introduction

Transcoding reduces the number of cellular subscriber voice/data trunks required by afactor of four. If transcoding takes place at the switch using a RXCDR, the number oflinks between the RXCDR and the BSC is reduced to approximately one quarter of thenumber 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. Thecapacity of one RXU shelf can support up to 16 GDP/XCDRs or GDPs and typicallyprovides a better solution of the transcoding function for larger commercial systems.Refer to the section Remote transcoder planning overview in Chapter 6.

GDP/XCDR planning considerations

The following factors should be considered when planning the GDP/XCDR complement:

S A GDP/XCDR can process 30 voice channels (GDP-E1/XCDR) or 24 voicechannels (GDP-T1), will support enhanced full rate speech, uplink/downlink volumecontrol and is capable of terminating one E1 or T1 link from the MSC.

S The master MSI slot(s) should always be populated to enable communication withOMC-R. The master MSI slot may contain a GDP/XCDR, if the OML goes throughthe MSC.

S The A interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1links; whereas an XCDR can only terminate E1 links (refer to T1 conversionsbelow).

NOTE The fitting of a GDP in place of an XCDR does not affect theplanning calculations for E1 links. For T1 links an MSI-2 is notrequired.


30 Sep 200314�30


GMR-0168P02900W21-M

T1 conversion


When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done inone of two ways. In either case the conversion may be part of an existing networkelement or a standalone network element which would appear as a RXCDR.


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

With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1circuits may be done. This uses the ability of the KSW to switch between groups usingnailed connections. Although more efficient in XCDR utilization, this method may causeadditional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2sneeded for T1 to E1 conversion is:

m = T + E

2





30 Sep 2003


68P02900W21-M

GMR-0114�31

Planning actions transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the numberof E1 or T1 links for the A interface. This text should be read in conjunction with the BSSplanning diagram Figure 14-1.

Using E1 links

The minimum number of E1 links required is the greater of two calculations that follow(fractional values should be rounded up to the next integer value).

N = T30

N = C + X + T

31

Where: N is: the minimum number of E1 links required.



T the number of trunks between the MSC and theBSC.

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 = T23

N = C + X + T

24

Where: N is: the minimum number of T1 links required.



T the number of trunks between the MSC and theBSC.


30 Sep 200314�32


GMR-0168P02900W21-M


Introduction

A multiple serial interface provides the interface for the links between a BSSC cabinetand other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI caninterface only E1 links, an MSI-2 can interface both E1 and T1 links, but notsimultaneously.




S Each MSI-2 can interface two T1 links.






If the OML links go directly to the MSC the master slot should be filled with anGDP/XCDR, otherwise the slot should be filled with an MSI/MSI-2 whichterminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 linksdo not need to go directly to the OMC-R, they may go to another network elementfor concentration.


30 Sep 2003


68P02900W21-M

GMR-0114�33


The following formulae assume local transcoding. Refer to the Multiple serial interface(MSI, MSI-2) section of Chapter 6 RXCDR planning steps and rules for MSI planningformulae for remote transcoding.

With E1 links

Determine the number of MSIs required.

M = B2

Where: M is: the number of MSIs required.

B the number of BSC to BTS links.

With T1 links

Determine the number of MSI-2s required.

M = B2� m

Where: M is: the number of MSI/MSI-2s required.

B the number of BSC to BTS links.

m the number of MSI/MSI-2s used for T1 to E1conversion.


30 Sep 200314�34


GMR-0168P02900W21-M


Introduction

The kiloport switch (KSW) card provides digital switching for the TDM highway of theBSC.



S A minimum of one KSW is required for each BSC site.

S The KSW capacity of 1,024 64 kbit/s ports can be expanded by adding up to threeadditional KSWs, giving a total switching capacity of 4, 096 64 kbit/s ports ofwhich, eight timeslots are reserved by the system for test purposes and are notavailable for use.

S For planning purposes assume fourteen MSI maximum per KSW. Each MSI maybe replace with four GDP/XCDRs.

S Using twelve MSIs per KSW may reduce the number of shelves required at a costof additional KSWs. For example, a BSC with 28 MSIs could be housed in threeshelves with three KSW modules or four shelves with two KSW modules.

S Verify that each KSW uses fewer than 1016 ports. There are three devices in aBSC that require TDM timeslots. They are:






N = (G * n) + (R * 16) + (M * 64)


G the number of GPROC/GPROC2s.



M the number of MSI/MSI-2s (do not count MSI-2swhich are doing on board E1 to T1 conversion,when determining TDM bandwidth).


NOTE Any BSC site which contains a DRIM has 352 timeslots allocatedto DRIMs irrespective of the number of DRIMs equipped.


30 Sep 2003


68P02900W21-M

GMR-0114�35


Determine the number of KSWs required:

N = (G * n) + (R * 16) + (M * 64)

(1016)





M the number of MSI/MSI-2s (do not count MSI-2swhich are doing on board E1 to T1 conversion).

GSR6 (Horizon II)BSU shelves

30 Sep 200314�36


GMR-0168P02900W21-M

BSU shelves

Introduction

The number of BSU shelves is normally a function of the number of GPROC/GPROC2,MSI/MSI-2s, and GDP/XCDRs required.


The following factors should be considered when planning the number of BSU shelves:

S Each BSU shelf supports up to eight GPROCs or GPROC2s, if the number ofthese exceed the number of slots available an additional BSU shelf is required.

S Each shelf is allocated to a single KSW and extension shelves are differentiated bythe presence of the KSW; extension shelves are those which do not contain aprimary KSW.

S A BSU shelf can support up to 12 MSI/MSI-2 boards.

S A BSU shelf can support up to six GDP/XCDRs boards.(reducing appropriately, the number of MSI/MSI-2 boards).

BSU shelf planning actions

Determine the number of BSU shelves required.

The number of BSU shelves required is the greater of three calculations that follow(fractional values should be rounded up to the next integer value).

Bs = G8

Bs = M + R

12

Bs = R6

Where: Bs is: the minimum number of BSU shelves required.




NOTE The number of shelves may be larger if an attempt to reduce thenumber 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.


30 Sep 2003


68P02900W21-M

GMR-0114�37


Introduction

The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUsand supplies clock signals to all shelves in multi-shelf configurations. The KSWX isrequired whenever a network element grows beyond a single shelf.







� KSWXL (Local) are used in shelves that have KSWs to drive the clock bus inthat shelf and in shelves that do not not KSWs to drive both the local TDMhighway and the clock bus in that shelf.


S The maximum number of KSWX slots per shelf is 18, 9 per KSW.


The number of KSWXs required is the sum of the KSWXE, KSWXL and KSWXR.


NKXE � K � (K � 1)

NKXR � SE

NKXL � K � SE






SE the number of extension selves.

NOTE Ensure that SE = 0 for extension shelves and 1 for expansionshelves.


30 Sep 200314�38


GMR-0168P02900W21-M

For example


Extensionshelves


1 2 3 4

0 1 4 9 16

1 3 6 11 18

2 5 8 13 20

3 7 10 15 22

4 9 12 17 24


Extensionshelves


1 2 3 4

0 2 8 18 32

1 6 12 22 36

2 10 16 26 40

3 14 20 30 44

4 18 24 34 48

GSR6 (Horizon II) Generic clock (GCLK)

30 Sep 2003


68P02900W21-M

GMR-0114�39


Introduction

The generic clock (GCLK) generates all the timing reference signals required by a BSU.



S One GCLK is required at each BSC.

S The maximum number of GCLK slots per shelf is two.

S For redundancy add a second GCLK at each site in the same cabinet as the firstGCLK.




GSR6 (Horizon II)Clock extender (CLKX)

30 Sep 200314�40


GMR-0168P02900W21-M


Introduction

A clock extender (CLKX) board provides expansion of GCLK timing to more than oneBSU.



S One CLKX is required in the first BSU shelf, which contains the GCLK, whenexpansion beyond the shelf occurs.


S There are three CLKX slots for each GCLK, allowing each GCLK to support up to18 shelves (LAN extension only allows 14 shelves in a single network element).







NCLKX � ROUNDUP�E6� * (1 � RF)



E the number of expansion/expension shelves.

RF Redundancy factor.(1 if redundancy required (recommended),0 for no redundancy).

GSR6 (Horizon II) LAN extender (LANX)

30 Sep 2003


68P02900W21-M

GMR-0114�41

LAN extender (LANX)

Introduction

The local area network extender (LANX) provides a LAN interconnection forcommunications between all GPROCs at a site.








NLANX � NBSU * (1 � RF)




BSU � 14

GSR6 (Horizon II)Parallel interface extender (PIX)

30 Sep 200314�42


GMR-0168P02900W21-M


Introduction

The parallel interface extender (PIX) provides eight inputs and four outputs for sitealarms.






Choose the number of PIXs required.


or

PIX � 8.

GSR6 (Horizon II) Line interfaces (BIB, T43)

30 Sep 2003


68P02900W21-M

GMR-0114�43


Introduction




S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T11.544 Mbit/s) 3 V (peak pulse) line use a BIB.

S To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peakpulse) line use a T43 Board (T43).


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




S Determine the number of BIBs or T43s required.

Minimum number of BIBs or T43s = Number of MSIs

3 =



30 Sep 200314�44


GMR-0168P02900W21-M


Introduction

A BSSC cabinet can be supplied to operate from either a +27 V dc or �48/�60 V dcpower source.


The following factors should be considered when planning the PSU complement:

S Two DPSMs are required for each shelf in the BSSC.

S Two IPSMs are required for each shelf in the BSSC2 (�48/�60 V dc).

S Two EPSMs are required for each shelf in the BSSC2 (+27 V dc).

S For redundancy, add one DPSM, IPSM, or EPSM for each shelf.


Determine the number of PSUs required.

PSUs = 2 * Number of BSUs + RF * Number of BSUs

Where: RF is: Redundancy factor.(1 if redundancy required (recommended),0 for no redundancy).


30 Sep 2003


68P02900W21-M

GMR-0114�45


Introduction

The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from anexternal battery to maintain power to the GPROC DRAM and the optical circuitry on theLANX in the event of a mains power failure.



S One BBBX is required per shelf; if the battery backup option is to be used.





GSR6 (Horizon II)Verify the number of BSU shelves and BSSC2 cabinets

30 Sep 200314�46


GMR-0168P02900W21-M

Verify the number of BSU shelves and BSSC2 cabinets

Verification


S The number of shelves is greater than one eighth the number of GPROC (orGPROC2) modules.



S The number of KSWX, LANX, CLKX, and GPROCs is correct.

S The number of MSI/MSI-2 and GDP/XCDR


S The number of GDP/XCDR


S The number of BTS sites

� 40.

S The number of BTS cells

� 126.

S RSLs

� 80.

S Carriers

� 255.

S Erlangs

� 1375.

If necessary, add extra BSU shelves. Each BSSC2 cabinet supports two BSU shelves.

30 Sep 2003


68P02900W21-M

GMR-0115�1

Chapter 15

Planning and equipment

descriptions for pre M-Cell BTSs

GSR6 (Horizon II)

30 Sep 200315�2


GMR-0168P02900W21-M


30 Sep 2003


68P02900W21-M

GMR-0115�3

Chapter overview

Introduction

This chapter (included for reference only) covers Motorola BTS equipment producedprior to the introduction of the M-Cell BTS range.

NOTE This chapter is not indexed as it is provided for referencepurposes only.

The chapter is divided into two sections and describes:

S BTS planning steps and rules.

S BTS RF configurations.

GSR6 (Horizon II)BTS planning steps and rules

30 Sep 200315�4


GMR-0168P02900W21-M

BTS planning steps and rules

Introduction

This section provides the planning steps and rules for the BTS, including ExCell andTopCell. This chapter contains:

S BTS planning overview:

S Capacity calculations for the number of control channels required.

S Capacity calculations for the number of GPROCs required.

� Planning rules for BTS cabinets.

� Planning rules for the receiver front end.

� Planning rules for the transmit combiner shelf.

� Planning rules for the carrier equipment.

� Planning rules for the line interconnections.

� Planning rules for the digital modules.

� Planning rules for the digital shelf power supply.

GSR6 (Horizon II) BTS planning steps and rules

30 Sep 2003


68P02900W21-M

GMR-0115�5


BTS site

The steps required to plan a BTS site (including ExCell and TopCell sites) are listedbelow:

1. Determine if the site has equipment shelters.

2. Determine the number of BTS cabinets required, refer to the section BTScabinets in this chapter.

3. Determine the receiver front end configuration, refer to the section Receiver frontend in this chapter.

4. Determine the transmit combining configuration, refer to the section Transmitcombiner shelf in this chapter.

5. Determine the number of bandpass filters required, refer to the section Duplexerin this chapter.

6. Determine the antenna configuration, refer to the section Duplexer in this chapter.

7. Determine the amount of carrier equipment required, refer to the section Carrierequipment (DRCU/SCU/TCU, DRIM, DRIX) in this chapter.

8. Determine the number of E1/T1 line interfaces required, refer to the section Lineinterface (BIB, T43) in this chapter.

9. Determine the number of MSIs required, refer to the section Multiple serialinterfaces (MSI, MSI-2) in this chapter.

10. Determine the number of GPROC, GPROC2s required, refer to the sectionGeneric processor (GPROC, GPROC2) in this chapter.

11. Determine the number of TSWs required, refer to the section Timeslot switch(TSW) in this chapter.

12. Determine the number of KSWXs required, refer to the section Kiloport switchextender (KSWX) in this chapter.

13. Determine the number of GCLKs required, refer to the section Generic clock(GCLK) in this chapter.

14. Determine the number of CLKXs required, refer to the section Clock extender(CLKX) in this chapter.

15. Determine the number of LANXs required, refer to the section LAN extender(LANX) in this chapter.

16. Determine the number of PIXs required, refer to the section Parallel interfaceextender (PIX) in this chapter.

17. Determine the number of DRIX3cs required, refer to the section Digital radiointerface extender (DRIX3c) in this chapter.

18. Determine the number of BBBXs boards required, refer to the section Batterybackup board (BBBX) in this chapter.

19. Determine the power requirements, refer to the section Digital shelf powersupply in this chapter.


30 Sep 200315�6


GMR-0168P02900W21-M


IntroductionThis section provides information on how to determine the number of control channelsand 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 whencalculating the exact configuration of the BSC required to support a given BSS.

Typical call parametersThe number of control channels and GPROC, GPROC2s required at a BTS depend on aset of call parameters; typical call parameters for BTS planning are given in Table 15-1.


Parameter Assumed value



Ratio of location updates to calls: non-border location area l = 2

Ratio of location updates to calls: border location area l = 7

Ratio of IMSI detaches to calls Id = 0

Location update factor: non-border location area (see below) L = 2

Location update factor: border location area (see below) L = 7

Number of handovers per call H = 2.5

Paging Rate in pages per second P = 3

Time duration for location update TL = 4 seconds

Time duration for SMSs TSMS = 6 seconds

Time duration for call setups TC = 5 seconds

Guard time for SDCCHs Tg = 4 seconds

Probability of blocking for TCHs PB-TCH < 2%

Probability of blocking for SDCCHs PB-SDCCH < 1%

The location update factor (L) is a function of the ratio of location updates to calls (I), theratio of IMSI detaches to calls (Id) and whether the short message sequence (type 1) orlong message sequence (type 2) is used for IMSI detach; typically Id = 0 (that is IMSIdetach is disabled) as in the first formula given below. When IMSI detach is enabled, thesecond or third of the formulas given below should be used. The type of IMSI detachused is a function of the MSC.

If IMSI detached is disabled:

L = I


L = I + 0.2 * Id


L = I + 0.5 * Id


30 Sep 2003


68P02900W21-M

GMR-0115�7

Control channel calculations

Introduction

There are four types of air interface control channels, they are:

S Broadcast control channel (BCCH).

S Common control channel (CCCH).

S Standalone dedicated control channel (SDCCH).

S Cell broadcast channel (CBCH), which uses one SDCCH.

There are three configurations of control channels, each occupies one radio timeslot:

S A combined control channel.

One BCCH plus three CCCH plus four SDCCH.

S A non-combined control channel.

One BCCH plus nine CCCH (no SDCCH).

S An SDCCH control channel.

Eight SDCCH.

Each sector/cell requires a BCCH, so at least one of the first two configurations is alwaysrequired.

The number of air interface control channels required for a site, is dependent on the:

S Number of pages.

S Location updates.

S Short message services.

S Call loading.

S Setup time.

Only the number of pages and access grants affects the CCCH. The other informationuses the SDCCH.

GSR6 (Horizon II)Calculations for determining BTS GPROC, GPROC2 requirements

30 Sep 200315�8


GMR-0168P02900W21-M

Calculations for determining BTS GPROC, GPROC2 requirements

Introduction

This section discusses the basic planning dependencies for determining the number ofGPROC, GPROC2s required for a BTS site. Some background information regarding thecall processing functions at the BTS is also provided.

Call processing functions

Three major call processing functions exist at a BTS. These are:

S Cell resource manager (CRM).

S Radio resource state machine (RRSM).

S Radio subsystem (RSS).

The CRM and RRSM are associated with the call processing function for the entire BTSsite. The BTS site supports a single instance of the CRM and RRSM and multipleinstances of RSS. An instance of RSS controls a number of RTFs. Each instance of RSSonly performs call processing for its assigned, individual, or group of digital radiointerfaces (DRIMs). A DRIM is controlled by one instance of RSS, and must reside in thesame shelf as the GPROC, GPROC2 running the instance of RSS. A DRIM provides theprocessor interface to one DRCU/SCU/TCU. The DRIM, DRIX, and DRCU/SCU/TCU areviewed 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 transceiverprocessor (BTP), undertakes the master operations and maintenance (O&M) function forthe site, together with the CRM and RRSM functions. The term BTP refers to theGPROC, GPROC2 performing the CRM and RRSM functions. The term digital hostprocessor (DHP) refers to the GPROC, GPROC2 performing the call processing functionof RSS. When the BTS is colocated with the BSC, the CRM and RRSM functions areperformed by the BTF. The same planning rules apply to a BTF as the BTP.

GSR6 (Horizon II) Calculations for determining BTS GPROC, GPROC2 requirements

30 Sep 2003


68P02900W21-M

GMR-0115�9

GPROC, GPROC2 managementThis section discusses topics associated with the GPROC, GPROC2. These are themax_dris parameter, the reassign command, and redundancy considerations.

Maximum number of DRIMsThe max_dris parameter defines the maximum number of DRIMs that may be controlledfrom the BTP or DHP. The parameter can be changed on an individual BTP or DHPbasis.

When the sum of max_dris for all BTPs and DHPs in a shelf is less than the number ofDRIMs in the shelf, only the number of DRIMs equivalent to the sum of max_dris willcome into service. For example, if a shelf has five DRIMs with two DHPs (and no BTP),and assuming that the max_dris parameter is set to 2, for both the DHPs (giving a totalof four), then only four of the DRIMs will come into service, and will be able to supportactive RTFs.

For the purposes of redundancy, when equipping additional DHPs in a BTS shelf, themax_dris parameter for each DHP must be set to take account if a DHP fails. Thismeans that the sum of max_dris must still be equal to, or greater than, the number ofDRIMs equipped in the specific shelf after the failure of a GPROC, GPROC2 in the shelf.

Control of DRIM loadingThe system software attempts to balance the DRIM process load across the GPROC,GPROC2s in a shelf. Unbalanced conditions can arise where certain GPROC,GPROC2s are heavily loaded, while others are lightly loaded. The DRIM process loadcan be redistributed using the reassign command.

The reassign command allows the moving of DRIM control from one GPROC, GPROC2to another: one DHP to another DHP, the BTP to a DHP, DHP to the BTP. The GPROC,GPROC2s must be in the same shelf as the DRIM.

When a site has been reset, the system will revert to the original pre-reset allocation ofDRIMs to GPROC, GPROC2s. During execution of the reassign command, the DRIMand RTF supported by the DRIM is momentarily taken out of service.

Redundancy considerationsA BTS should always be configured with sufficient redundancy such that a singleGPROC, GPROC2 failure will not:

S Degrade system performance.

S Reduce capacity.

S Cause the BTS site to become inoperative.

Each BTS site should be equipped with a redundant BTP, since failure of the BTP willresult in an inoperative BTS.

An additional DHP should be equipped in each BTS shelf already containing a DHP. Thisredundant 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 DHPwere to fail, and the sum of the max_dris for the remaining DHP(s) was less than thenumber of DRIMs, some RTF(s) would become inoperative. Under these conditions, ifthere were only a single DHP in a shelf, all RTFs using DRIMs in that shelf would beinoperative. If a DHP were to fail in the shelf with the BTP and the BTP was controlling anumber 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 itsmax_dris setting.

Where the number of DHPs is greater than the number of RTFs, some DHPs will remainin an idle condition.


30 Sep 200315�10


GMR-0168P02900W21-M

GPROC, GPROC2 planning

The number of GPROC, GPROC2s required at a given BTS site is dependent on carrierand channel configuration together with the projected call mix at the BTS. The projectedcall mix must be done on an individual BTS basis. When determining the requirednumber of GPROC, GPROC2s for a given BTS shelf, the call mix associated with thecells supported by the RTFs in the shelf, must be used.

BTS type 0

A BTS type 0 only supports one active GPROC, which is referred to as the BTP.Although a second BTP may exist to meet redundancy requirements, only one may beactive at any given time.

For the typical call mix a type 0 BTS supports up to two RTFs. For a BTS with more thanthree RTFs then a type 1 BTS should be used. For the border location area call mix atype 0 BTS supports up to two RTFs. If the call parameters differ significantly from thosegiven in Table 15-1 then the formula given below should be used.

BTS type 1

A BTS type 1 supports multiple active GPROC, GPROC2s. The RRSM and CRMfunctions reside on the BTP, in addition to an optional instance of the RSS. A BTS type 1also supports DHPs.

The number of RTFs a BTP can control depends on the total number of RTFs at the BTSsite. Table 15-2 gives the max_dris setting (the number of RTFs a BTP can control) forthe BTP for the typical and border location area call mix for a given number of RTFs andErlangs for a BTS. If the call parameters differ significantly from those given inTable 15-1, the formula given below should be used. If the formula gives two RTFs perDHP, then the border location area call mix rules should be used. If the formula gives oneRTF per DHP, then the BTP may control one RTF for BTS sites of less than three RTFs.

Table 15-2 Maximum number of Erlangs supported by the BTP

max_drisvalue for

Typical call mix Location area border call mix_value for

BTPMaximum

RTFsMaximumErlangs

MaximumRTFs

MaximumErlangs

0 30 200 20 120

1 22 140 15 85

2 14 80 10 50


30 Sep 2003


68P02900W21-M

GMR-0115�11

Call mixes

The factors that determine call mixes are highly site dependent. The main factors beingthe ratio of location updates to calls and call hold time. Those BTSs that contain cells onthe edge of location areas, will have a greater loading of location updates. This impactsthe number of required DHPs and control channel configurations and the maximumnumber 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 upto 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 15-1, the formula givenhere should be used to determined the maximum number of RTFs a DHP or the BTPshould control; the result should be rounded down to an integer value.

NRTF �0.8

0.2 + (1 + 1.4 � L + 0.9 � S + 0.5 � H) / T

Where: NRTF is: the maximum number of RTFs supported perDHP (type 0 BTS).


S the ratio of SMSs per call.



BTS shelf configurations

The number of RTFs supported by a DHP and the BTP must be determined beforedetermining the BTS shelf configurations.

The sections Shelf configurations for typical call mix and Shelf configurations forborder location area call mix respectively, provide recommended shelf configurationsfor the normal call mixes given in Table 15-3 and Table 15-4, and border location area callmixes given in Table 15-5 and Table 15-6. The number of RTFs referred to in thesesections is the number of active RTFs. Inactive, or standby carriers do not utilizeGPROC, GPROC2 resources. The numbers given are the number of GPROC,GPROC2s required with and without redundancy. For redundancy the number ofGPROC, GPROC2s given is the number required such that no single GPROC, GPROC2failure will cause a loss of RTFs or capacity. See Redundant GPROC, GPROC2s belowfor more details on GPROC, GPROC2 redundancy.

Command max_dris

The max_dris setting for the DHP should be the same as the number of RTFs per DHP.For the BTP the max_dris setting should be the value from Table 15-3, Table 15-4,Table 15-5 and Table 15-6; or from the formula given in the previous section.

Redundant GPROC, GPROC2s

For redundancy the BTP should be duplicated. The letter (R) next to the max_dris valuenumber in the following tables indicates that this DHP is optional and only required forredundancy.


30 Sep 200315�12


GMR-0168P02900W21-M

Shelf configurations for typical call mix

Table 15-3 and Table 15-4 give the recommended number of GPROC, GPROC2s andmax_dris values for the first shelf and the other shelves, respectively for a BTS with thetypical call mix parameters. The BTP is duplicated when redundancy (R) is specified.

Table 15-3 Recommended BTP/DHP configurations and max_dris values for thefirst shelf of a BTS (3 RTFs per DHP)

Number max_dris values Total GPROCs

of RTFs BTP DHP1 DHP 2 DHP 3 Withoutredundancy

Withredundancy

With 6 or fewer RTFs at BTS site

1 � 2 2 1 2

3 � 5 2 3 3(R) 2 4

6 2 3 3(R) 3 5

With 7 to 14 RTFs at BTS site

2 2 3 1 2

3 � 5 2 3 3(R) 2 4

6 2 3 3 3(R) 3 5

With 15 to 22 RTFs at BTS site

1 1 3 1 2

2 � 4 1 3 3(R) 2 4

5 � 6 1 3 3 3(R) 3 5

With more than 22 RTFs at BTS site

1 � 3 0 3 3(R) 1 2

4 � 6 0 3 3 3(R) 2 3

Table 15-4 Other shelves (3 RTFs per DHP)


of RTFs DHP1

DHP 2 DHP 3 DHP 4 Withoutredundancy

Withredundancy

1 � 3 3 3(R) N/A 1 2

3 � 6 3 3 3(R) N/A 2 3


30 Sep 2003


68P02900W21-M

GMR-0115�13

Shelf configurations for border location area call mix

Table 15-5 and Table 15-6 give the recommended number of GPROC, GPROC2s andmax_dris values for the first shelf and the other shelves, respectively for a BTS with theborder location area call mix parameters. The BTP is duplicated when redundancy (R) isspecified.

Table 15-5 Recommended BTP/DHP configurations and max_dris values for the firstshelf of a BTS (3 RTFs per DHP)


of RTFs BTP DHP1 DHP2 DHP3 DHP 4 Withoutredundancy

Withredundancy


1 � 2 2 1 2

3 � 4 2 2 2(R) 2 4

5 � 6 2 2 2 2(R) 3 5


1 1 1 2

2 � 3 1 2 2(R) 2 4

4 � 5 1 2 2 2(R) 3 5

6 1 2 2 2 2(R) 4 6


1 � 2 0 2 2(R) 2 4

3 � 4 0 2 2 2(R) 3 5

4 � 6 0 2 2 2 2(R) 4 6

Table 15-6 Other shelves (3 RTFs per DHP)


of RTFs DHP1 DHP 2 DHP 3 DHP 4 Withoutredundancy

Withredundancy

1 � 3 2 2(R) 1 2

3 � 4 2 2 2(R) 2 3

5 � 6 2 2 2 2(R) 3 4

GSR6 (Horizon II)BTS equipment cabinets

30 Sep 200315�14


GMR-0168P02900W21-M

BTS equipment cabinets

Introduction

Each BTS6 cabinet can support up to six cells and six carriers, earlier cabinets supportedfewer carriers. The minimum number of cabinets required can be determined by dividingthe total number of carriers by six. Keeping all the carrier equipment in a cell in theminimum number of cabinets makes interconnection simpler.

However, consider a three cell site with two carriers per cell. This fits well in a singlecabinet. When this site needs to expand, an additional cabinet must be added and atleast one cell needs to move to the second cabinet.

A three cell site which will grow to four carriers per cell can be accommodated in twoBTS cabinets, if the cell which is split between cabinets can use hybrid combining. If aremotely tuneable combiner (RTC) is to be housed in an external equipment cabinet, athird BTS cabinet may provide a better alternative as well as room to expand later.

Cabinet planning actions


S Determine if ExCell or TopCell cabinets are required.

S Determine the number of cabinets required and number of cells to be supported byeach cabinet.

GSR6 (Horizon II) Receiver front end

30 Sep 2003


68P02900W21-M

GMR-0115�15

Receiver front end

Introduction

The receiver front end (RFE) provides the termination and distribution of the receivedsignals from the Rx antennas. RFE equipment is required for each Rx signal in everycabinet in which it is used. Each Rx antenna must terminate on a single cabinet. It willnormally be one of the BTS cabinets but it may be the external equipment cabinet. If thesignal needs to go to multiple cabinets it will be distributed from the first cabinet. For RFEplanning purposes include inactive RF carriers in the number of carriers considered.

RFE in cabinet types EG, FG and BTS6

Cabinet types EG, FG, BTS6 come equipped with a DPP shelf which has the capacity tohold up to three modules of the following types:

S Dual path preselector (DPP) modules.

One DPP is required for every two Rx signals.

and/or

S Single path preselector (SPP) modules.

One SPP is required for each Rx signal.

and/or

S Passive splitter modules.

One passive splitter is required for every two Rx signals (may be fed from anunused output of a DPP or from the expansion port of a DPP2 in the cabinetterminating the Rx antenna).

Each module has the ability to distribute the Rx signal to six DRCU/SCU/TCUs in thecabinet.

RFE in cabinet types AG, BG and DG

Cabinet types AG, BG, DG come equipped with a preselector shelf which has thecapacity to hold up to three preselectors each with its own 6-way splitter. If more thanthree Rx antennas need to be terminated, a second preselector shelf is required. Thissecond shelf displaces Tx equipment.

One preselector with 6-way splitter is required for each Rx signal.

The splitter/preselector shelf can be removed from the BG and DG cabinets and a DPPshelf fitted.

GSR6 (Horizon II)Receiver front end

30 Sep 200315�16


GMR-0168P02900W21-M

Distributing Rx signals between multiple cabinets

When one Rx signal is feeding multiple cabinets additional equipment and cabling isrequired. There are several options which depend primarily on other equipment at thesite, the number of cabinets to which the signal must be brought, and the number ofDRCU/SCU/TCUs in each of the cabinets. Care must be taken to ensure that the BTScabinet has enough RF ports for the termination and expansion of the Rx signals. This isonly a potential issue when diversity is used.

In order to terminate the Rx antenna on a BTS cabinet when the cell�s DRCU/SCU/TCUsare spread across multiple cabinets, check the number of Rx ports on the cabinet andthe availability of RFE outputs not being used for carriers in the cabinet. Without usingthe Tx ports and combiner coupler ports there is a total of six Rx ports available. The sixports allow for up to three cells with diversity and without extension. If there are threecells with diversity supported in the cabinet, any cell which has DRCU/SCU/TCUs inother cabinets must have the Rx antenna terminated on the other cabinet.

The cabinet which terminates the Rx antenna should provide the input to all othercabinets supporting the cell. If the cell is spread across three or more cabinets, ensurethat there are cabinet Rx ports and available RFE outputs for each cabinet.

Single cabinet rules

The following rules apply for a cabinet to be able to support the Rx termination andextension when the cabinet supports:

S Single cell.

Rx ports exist. Must have a DPP2 or fewer than six DRCU/SCU/TCUs.

S Two cell.

Ability to extend only one cell if diversity is used. Splitter port(s) exist.

S Three cell.

No ability to extend, if diversity is used. Splitter port(s) exist.

Distribution methods

There are three methods of distributing Rx signals between cabinets:

S BTS Cabinet with DPP2

The DPP2 has an additional test/extender port which may be used to drive apassive 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. Eachoutput requires a 6 dB attenuator to feed the preselector/DPP/SPP in the adjacentBTS cabinet.

S Receiver multicoupler

When the Rx antenna distribution is to a large number of cabinets, a GSM receivermulticoupler can be equipped in an external equipment cabinet at the site.

One of the four types of multicoupler extender is required on each activemulticoupler output.

A multicoupler should be installed in an external equipment cabinet.

GSR6 (Horizon II) Receiver front end

30 Sep 2003


68P02900W21-M

GMR-0115�17

RFE planning actions


1. Determine the number of cells.

2. Determine number of cells which have DRCU/SCU/TCUs in more than onecabinet.

3. Determine the number of Rx antennas per cell supported in each cabinet.

A cell without diversity requires one Rx antenna. A cell with diversity requires twoRx antennas.

4. Determine the type and quantity of RFE equipment required.

GSR6 (Horizon II)Transmit combiner shelf

30 Sep 200315�18


GMR-0168P02900W21-M

Transmit combiner shelf

Introduction

The transmit combiner shelf is mounted directly above the upper bank of fans. If asecond preselector shelf is equipped, the Tx combining must be done externally.

Transmit RF signals to be combined inside a BTS cabinet can come either fromDRCU/SCU/TCUs within the cabinet or from a second BTS cabinet. A BTS cabinet hassix Tx ports and two combiner coupling ports.

Transmit combining equipment

The following equipment may be mounted on the transmit combiner shelf:

S Up to five hybrid combiner modules.

A hybrid combiner combines two inputs into one antenna, five combiners willcombine six inputs.

Unused ports must be terminated with a suitable load.

or

S One remotely tuneable combiner.

A RTC combines up to five inputs (four for a four cavity combiner) into oneantenna.

The channels to which RTC cavities are tuned, must be separated by 800 kHz.

With a phasing harness, up to ten channels (eight for four-cavity combiners) maybe combined together into one antenna.

The cavities of an RTC do not have to be connected to a single antenna.

and

S Up to three transmit bandpass filters.

A Tx BPF is a mandatory requirement for every transmitting antenna.

If an RTC or more than four hybrid combiners are installed, a maximum of two TxBPFs can be accommodated, allowing two cells to be serviced.

or

S Up to two cavity combining blocks (CCB).

A CCB (output) combines up to three inputs into one antenna.

The channels to which CCB cavities are tuned, must be separated by 400 kHz.

A CCB (extention) enables up to six inputs into one antenna.

GSR6 (Horizon II) Transmit combiner shelf

30 Sep 2003


68P02900W21-M

GMR-0115�19


The following factors should be considered when planning the combining equipment:

S When there is only one carrier for each sector, combining is not required.

S When two or more DRCU/SCU/TCUs are combined on to one antenna, therequired power output must be known in order to determine the type of combinerto be used.

S There is a greater than 3 dB power loss through each hybrid combiner stage.

S With all cavities of an RTC connected to one antenna, the maximum signal loss forany one input is approximately 3 dB.

S All combining may be done in an external equipment cabinet if desired, thisreduces heat generated in the BTS cabinet.

CAUTION The remotely tuneable combiner and multicoupler have not beenEMC tested for use in the external equipment rack. Since theend of 1995 these items have not been available for use in thisconfiguration within the European Union.

Transmit combiner shelf planning actions


1. Determine the number of cells required.

2. Determine the output power required.

3. Determine the number and type (hybrid or remotely tuneable) of combinersrequired.

GSR6 (Horizon II)Duplexer

30 Sep 200315�20


GMR-0168P02900W21-M

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


The following factors should be considered when planning combined antennas:

S A duplexer can be installed in an ExCell cabinet.

S A duplexer can be fitted to a TopCell cabinet.

S A duplexer cannot be fitted into a BTS4, BTS5, or BTS6 cabinet.

S Duplexers may be installed in an external equipment cabinet.

S The inter-modulation performance may be degraded due to the use of commonantenna/feeder, putting the receiver at risk.

S Duplexers have approximately a 0.5 dB loss in both transmit and receive directions.

Duplexer planning actions


1. Determine if a common antenna is to be used for Tx and Rx.

2. If common antennas are to be used for Tx and Rx, determine the number ofduplexers required.

An external equipment cabinet will be required when duplexers are used withBTS4, BTS5, or BTS6 cabinets.

GSR6 (Horizon II) Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)

30 Sep 2003


68P02900W21-M

GMR-0115�21

Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)

Introduction

A carrier equipment kit consists of:

S For BTS; a DRCU/SCU/TCU, DRIM, and DRIX.

Together these three units provide a single RF carrier, which can be referred to as anRTF.


The following factors should be considered when planning carrier equipment:

S The number of carriers should be based on traffic considerations.

S Plan for future growth.

S Allowance must be made for BCCH and SDCCH control channels.

Information about how to determine the number of control channels required is inthe section Control channel calculations in this chapter.

S Normally, one carrier equipment kit is required to provide each RF carrier.

S Include redundancy requirements; redundancy can be achieved by installingexcess capacity in the form of additional carrier equipment kits.

Carrier equipment planning actions


1. Determine the number of carriers required.

2. Make an allowance for redundancy.

3. Determine the number of carrier equipment kits required.

GSR6 (Horizon II)Line interfaces (BIB, T43)

30 Sep 200315�22


GMR-0168P02900W21-M


Introduction

The line interfaces, balanced line interface board (BIB) and T43 board (T43), provideimpedance matching for E1 and T1 links.



S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544Mbit/s) 3 V (peak pulse) line use a BIB.

S To match a single ended 75 ohm 2.37 V (peak pulse) line use a T43 Board (T43).

S Each BIB or or T43 can interface six E1/T1 links.

S The BTS cabinet can interface up to twelve bidirectional E1/T1 links using twoBIBs (six links connected to each board).

S The BTS cabinet can interface up to twelve bidirectional E1 links using two T43boards (six links connected to each board).



1. Determine the number and type of link (E1 or T1) to be driven.

2. Determine the number of BIBs or T43s required.

Number of BIBs or T43s = Number of MSIs

3 =



30 Sep 2003


68P02900W21-M

GMR-0115�23


Introduction

A multiple serial interface provides the interface between a BTS cabinet and the linksfrom the BSC. An MSI can interface only E1 links, an MSI-2 can interface both E1 andT1 links.


The following factors should be considered when planning the MSI complement:

S To calculate the required number of 64 kbit/s channels, the site must be viewed asconsisting of its own equipment and that of other sites which are connected to it bythe 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 14, Previous generation BSC planning steps and rules.


S Each MSI-2 can interface two E1/T1 links.



S A minimum of one MSI/MSI-2 is required for each BTS site.


S Plan for a maximum of ten MSIs in each BTS site (with no BSC).

S Plan for a maximum of eight MSIs or ten MSI-2s for each KSW/TSW.

S The master MSI slot of the first shelf should always be populated to enablecommunication with the BSC.

S Refer to Table 15-7 for the number of traffic channels (TCH) per radio signallinglink (RSL).


30 Sep 200315�24


GMR-0168P02900W21-M


n = number of TCHs at the BTS Number of 64 kbit/sRSLs

Number of 16 kbit/sRSLs

n <= 30 1 1

30 < n <= 60 1 2

60 < n <= 90 1 3

90 < n <= 120 1 4

120 < n <= 150 2 5

150 < n <= 180 2 6

180 < n <= 210 2 7

210 < n <= 240 2 8

NOTE A BTS shall support either 64 kbit/s RSLs or 16 kbit/s RSLs, butnot both.



1. Determine the number and type of link (E1 or T1) to be interfaced.

2. Determine, M, the number of MSIs or MSI-2s required.

M = Number of E1/T1 links

2


30 Sep 2003


68P02900W21-M

GMR-0115�25

Generic processor (GPROC, GPROC2)

Introduction

The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as ageneric control processor.


The following factors should be considered when planning the GPROC, GPROC2complement:

S At least one GPROC, GPROC2 is required for each digital shelf.

S If more than one cabinet is used, the first cabinet requires a minimum of two activeGPROCs to support the additional cabinets.

S Additional GPROC, GPROC2s may be required to cope with additional load.

S The master GPROC, GPROC2 slot of the BSU shelf should always be populatedto enable communication with the BSC.

GPROC, GPROC2 planning actions

Determine the number of GPROC, GPROC2s required.

Use the information to be found in the section Calculations for determining BTSGPROC, GPROC2 requirements in this chapter.

GSR6 (Horizon II)Timeslot switch (TSW)

30 Sep 200315�26


GMR-0168P02900W21-M

Timeslot switch (TSW)

Introduction

The timeslot switch (TSW) provides digital switching on the TDM highway of the BTS.

The TSW is designed for use in BTSs, although the KSW can continue to be used.

It should be borne in mind that the KSW provides all the TSW functionality plus subrateswitching and third-party conference functionality, but at an increased cost.


The following factors should be considered when planning the TSW complement:

S A minimum of one TSW is required for each BTS site.

S In a BTS, one TSW can support up to eight MSIs or ten MSI-2s.

S As a site grows beyond 25 DRCU/SCU/TCUs, an additional TSW will be requiredfor switch expansion.

S All DRIMs which support RTFs in a cell must be on a single TDM bus controlled bythe same TSW.

S For redundancy, duplicate all TSW boards.

TSW planning actions

Determine the number of TSWs required.


30 Sep 2003


68P02900W21-M

GMR-0115�27


Introduction

The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUsand supplies clock signals to all shelves in multi-shelf configurations. The KSWX isrequired whenever a network element grows beyond a single shelf. Although not requiredin a single BTS cabinet configuration, if expansion to multiple cabinets is expected,equipping the KSWX (and CLKX) will allow for easier expansion.



S For redundancy, duplicate all KSWX boards (requires redundant KSW/TSW).




� KSWXL (Local) are used in shelves that have KSWs to drive the clock bus inthat shelf and in shelves that do not not KSWs to drive both the local TDMhighway and the clock bus in that shelf.


S The maximum number of KSWX slots per shelf is 18, 9 per KSW/TSW.


The number of KSWXs required is the sum of the KSWXE, KSWXL, and KSWXR.


NKXE � K � (K � 1)

NKXR � SE

NKXL � K � SE






SE the number of extension/expansion shelves.

NOTE Ensure that SE = 0 for extension shelves and 1 for expansionshelves.

GSR6 (Horizon II)Generic clock (GCLK)

30 Sep 200315�28


GMR-0168P02900W21-M


Introduction

The generic clock (GCLK) generates all the timing reference signals required by a BTS.



S One GCLK is required at each BTS site.

S For redundancy add a second GCLK at each site in the same cabinet as the firstGCLK.




GSR6 (Horizon II) Clock extender (CLKX)

30 Sep 2003


68P02900W21-M

GMR-0115�29


Introduction

A clock extender (CLKX) provides expansion of GCLK timing to more than one BSU.Although not required in a single BTS cabinet configuration; if expansion to multiplecabinets is expected, equipping the CLKX (and KSWX) will allow for easier expansionlater.



S One CLKX is required if expansion is planned.




NCLKX � ROUNDUP �E6�� (1 � RF)



E the number of expansion/expension shelves.

RF Redundancy factor(1 if redundancy required (recommended).0 for no redundancy).

NOTE Each BTS cabinet has one BSU shelf.

GSR6 (Horizon II)Local area extender (LANX)

30 Sep 200315�30


GMR-0168P02900W21-M

Local area extender (LANX)

Introduction

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








NLANX � NBSU � (1 � RF)




BSU � 14

GSR6 (Horizon II) Parallel interface extender (PIX)

30 Sep 2003


68P02900W21-M

GMR-0115�31


Introduction

The parallel interface extender (PIX) provides eight inputs and four outputs for sitealarms.






Determine the number of PIXs required.


or

PIX � 8.

GSR6 (Horizon II)Digital radio interface extender (DRIX3c)

30 Sep 200315�32


GMR-0168P02900W21-M

Digital radio interface extender (DRIX3c)

Introduction

The Digital radio interface extender (DRIX3c) provides the electrical-optical interface forthe downlink (Tx) data and the optical-electrical interface for the uplink (Rx) data betweenthe DRCU/SCU/TCU/PCU and the DRIM.


The following factors should be considered when planning the DRIX3c complement:

S The maximum number of DRIX3c board slots per shelf is six.

S The maximum number of DRIX3c board slots per site is six.

DRIX planning actions

Determine the number of DRIX3cs required.


30 Sep 2003


68P02900W21-M

GMR-0115�33


Introduction

The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from anexternal battery. It maintains power to the GPROC, GPROC2 DRAM and the opticalcircuitry on the LANX, in the event of a mains power failure.



S One BBBX is required in each shelf.






30 Sep 200315�34


GMR-0168P02900W21-M


Introduction

A BTS and PCC cabinet can be supplied to operate from either a +27 V dc or�48 V/�60 V dc power source.


The following factors should be considered when planning the power supply module(PSM) complement:

S The +27 V dc BTS4/BTS5 cabinet option includes two digital power supplymodules (DPSM) required to power the BSU shelf. An additional DPSM may beequipped for redundancy.

S The �48 V/�60 V dc BTS4 cabinet option includes the two DPSMs required topower the BSU shelf, and a power converter unit for the DRCU/SCU/TCUs. Anadditional 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. Afourth converter module can be ordered separately to provide redundancy.

S The BTS6 cabinet power supplies, required to power both the digital shelf andDRCU/SCU/TCUs, are provided:

� In a +27 V dc cabinet, by one enhanced power supply module (EPSM) perthree DRCU/SCU/TCUs (two EPSM for a six DRCU/SCU fit). A third EPSMcan be fitted for redundancy.

� In a �48 V/�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 thirdIPSM can be fitted for redundancy.

NOTE The EPSM and IPSM fitted to a BTS6 cabinet are notinterchangeable with the DPSM fitted to BTS4 and BTS5cabinets.

S ExCell operates internally from +27 V dc and contains up to three EPSMs. ExCellalso contains a battery backup facility. A �48 V/�60 V dc supply is available forcustomer supplied communications equipment.

S TopCell operates internally from +27 V dc and uses the EPSM. Battery backup isprovided for each cabinet. A �48 V/�60 V dc supply is available for customersupplied communications equipment.


Determine the number of PSMs required.

GSR6 (Horizon II) BTS RF configurations

30 Sep 2003


68P02900W21-M

GMR-0115�35

BTS RF configurations

Introduction

This section provides diagrams of the logical interconnections of the RF components invarious standard BTS site configurations, including ExCell and TopCell.


S Typical BTS configurations.

S Single cabinet RF configurations.

S Multiple cabinet RF configurations.

GSR6 (Horizon II)Typical BTS configurations

30 Sep 200315�36


GMR-0168P02900W21-M

Typical BTS configurations

BTS configuration

The digital module and RF configuration for a BTS cabinet with four RF carriers andhybrid combining is shown in Figure 15-1.

Figure 15-1 Single BTS or ExCell site with 4 RF carriers using hybrid combining

Tx BPF

DUAL SERIAL BUS

DUAL MCAP BUS

FROM RECEIVE ANTENNATO TRANSMIT ANTENNA

BSC

KSWB

REDUNDANT

MSIGCLK

REDUNDANT

BTC

DRIM1

DRIM2

DRIM3

DRIM4

DRIX4

DRIX3

DRIX2

DRIX1

DUAL IEEE802.5 LAN

PRESELECTOR/6-WAY SPLITTERORDUAL PATH PRESELECTOR

BTS CABINET

1

GCLK KSW A

MSI

PIX

LINKS FROM/TO BSC


ONE RF CARRIER CONSISTS OF ONEDRIM, DRIX AND DRCU/SCU

BTC

LANX A

RF EQUIPMENT

A

B

LANXB

BSU SHELF

HYBRID

HYBRIDHYBRID

FIBRE OPTIC LINKS

GPROCGPROC GPROC

2 3 4

DRCU/SCUs

GSR6 (Horizon II) Typical BTS configurations

30 Sep 2003


68P02900W21-M

GMR-0115�37

TopCell BTS configuration

The digital module and RF configuration for a TopCell BTS cabinet with six RF carriersand hybrid combining is shown in Figure 15-2. TopCell supports a maximum of sixcarriers.

Figure 15-2 TopCell with 6 RF carriers using hybrid combiners

Tx BPF

DUAL MCAP BUS

RxTx

BSC

MSIBTC

DRIM1

DRIM2

DRIM3

DRIM4

DRIX4

DRIX3

DRIX2

DRIX1

DUAL IEEE802.5 LAN

DPP

GCLK KSW

LINKS FROM/TO BSC


BTC

LANXA

A

B

LANXB

TDU

HYBRID

FIBRE OPTIC LINKS

GPROCGPROC GPROC

1 2

DRIM5

DRIX5

DRIM6

DRIX6

Tx BPF

RxTx

DPP

HYBRID

5 6

Tx BPF

RxTx

DPP

HYBRID

3 4

TRU1 TRU2 TRU3

DRCU/SCUs

DRCU/SCUs

DRCU/SCUs

GSR6 (Horizon II)Single cabinet RF configurations

30 Sep 200315�38


GMR-0168P02900W21-M

Single cabinet RF configurations

Single cabinet, single DRCU/SCU without diversity

A single cabinet, single DRCU/SCU configuration is shown in Figure 15-3. Table 15-8provides a summary of the equipment required for this configuration. The following rulesapply:

S As only one DRCU/SCU is used a combiner is not required.

S One dual path preselector is required for the receive signal entering the cabinet.

S An external equipment cabinet is not necessary.

Figure 15-3 Single cabinet, one DRCU/SCU, no diversity

DUAL PATHPRESELECTOR

DRCU/SCU

BTS CABINET

Tx BPF

Tx Rx

Table 15-8 Equipment required for single cabinet, single DRCU/SCU configuration

Quantity Unit

2 Antennas

1 BTS cabinet

1 DRCU/SCU

Transmitter

1 Bandpass filter

Receiver

1 Dual path preselector

GSR6 (Horizon II) Single cabinet RF configurations

30 Sep 2003


68P02900W21-M

GMR-0115�39

Single cabinet, single DRCU/SCU with diversity

A single cabinet, single DRCU/SCU configuration with diversity is shown in Figure 15-4.Table 15-9 provides a summary of the equipment required for this configuration. Thefollowing rules apply:

S As only one DRCU/SCU is used a combiner is not required.

S One dual path preselector is required for every two receive signals entering thecabinet.


Figure 15-4 Single cabinet, one DRCU/SCU, diversity

DRCU/SCU

BTS CABINET

Tx BPF

Tx Rx Rx


Table 15-9 Equipment required for single cabinet, single DRCU/SCU configuration withdiversity

Quantity Unit

3 Antennas

1 BTS cabinet

1 DRCU/SCU

Transmitter

1 Bandpass filter

Receiver



30 Sep 200315�40


GMR-0168P02900W21-M

Single cabinet, five DRCU/SCUs with combining

A single cabinet, five DRCU/SCU configuration with remotely tuneable or hybridcombining but without diversity is shown in Figure 15-5. Table 15-10 provides a summaryof the equipment required for this configuration. The following rules apply:

S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can beaccommodated.

S If operation from a negative power supply voltage is required, only fourDRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will beoccupied by the dc/dc converters.

S If, when using hybrid combining, there are unequal levels of loss, the output powerfor the BTS (sector) is that of the DRCU/SCU with the greatest loss. The otherDRCU/SCUs should be adjusted to lower their output to provide the same outputpower level.


Figure 15-5 Single cabinet, 5 DRCU/SCUs, remotely tuneable or hybrid combining,no diversity


BTS CABINET

Tx BPF

1 2 3 4 5

Tx Rx

DRCU/SCUs

REMOTELY TUNEABLE COMBINER

HYBRIDHYBRID

HYBRID

HYBRID

Tx BPF

HYBRIDCOMBINERS


30 Sep 2003


68P02900W21-M

GMR-0115�41

Table 15-10 Equipment required for single cabinet, 5 DRCU/SCU configuration withremotely tuneable or hybrid combining

Quantity Unit

2 Antennas

1 BTS cabinet

5 DRCU/SCU

Transmitter

1 Bandpass filter

4 Hybrid combiner

or

1 Remotely tuneable combiner

Receiver



30 Sep 200315�42


GMR-0168P02900W21-M

Single cabinet, six DRCU/SCUs with combining and diversity

A single cabinet, six DRCU/SCU configuration with remotely tuneable or hybridcombining is shown in Figure 15-6. Table 15-11 provides a summary of the equipmentrequired for this configuration. The following rules apply:

S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can beaccommodated.

S If operation from a negative power supply voltage is required, only fourDRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will beoccupied by the dc/dc converters.

S If, when using hybrid combining, there are unequal levels of loss, the output powerfor the BTS (sector) is that of the DRCU/SCU with the greatest loss. The otherDRCU/SCUs should be adjusted to lower their output to provide the same outputpower level.


Figure 15-6 Single cabinet, 6 DRCU/SCUs, remotely tuneable or hybridcombining, diversity

6

Tx BPF

1 2 3 4 5

Tx Rx

BTS CABINET

DRCU/SCUs


HYBRIDHYBRIDHYBRID

HYBRID

HYBRID

Rx


30 Sep 2003


68P02900W21-M

GMR-0115�43

Table 15-11 Equipment required for single cabinet, 6 DRCU/SCU configuration withdiversity and remotely tuneable or hybrid combining

Quantity Unit

3 Antennas

1 BTS cabinet

6 DRCU/SCU

Transmitter

1 Bandpass filter

5 Hybrid combiner

or

1 Remotely tuneable combiner

1 Hybrid combiner

Receiver



30 Sep 200315�44


GMR-0168P02900W21-M

Single cabinet, multiple antennas

A single cabinet, multiple antenna configuration is shown in Figure 15-7. Table 15-12provides a summary of the equipment required for this configuration. The following rulesapply:

S If only one DRCU/SCU is used per carrier, combining is not required.


Figure 15-7 Single cabinet, multiple antenna (3 sector minimum) configuration

BTS CABINET

1 2 3

Tx Rx

DRCU/SCUs

Tx BPFs DUAL PATHPRESELECTORS

Tx Tx Rx Rx

Table 15-12 Equipment required for single cabinet, multiple antenna configuration

Quantity Unit

6 Antennas

1 BTS cabinet

3 DRCU/SCU

Transmitter

3 Bandpass filter

Receiver



30 Sep 2003


68P02900W21-M

GMR-0115�45

Single cabinet, multiple antennas with diversity

A single cabinet, multiple antenna configuration with diversity is shown in Figure 15-8;this configuration provides for three sectors. Table 15-13 provides a summary of theequipment required for this configuration. The following rules apply:

S A maximum of six receive signals, two per DRCU/SCU, are allowed per BTScabinet.

S If only one DRCU/SCU is used per carrier, combining is not required.


Figure 15-8 Single cabinet multiple antenna configuration, diversity

DUAL PATHPRESELECTORS

BTS CABINET

1 2 3

Tx

Tx BPF

Rx

DRCU/SCUs

Tx Tx Rx Rx Rx Rx Rx

Table 15-13 Equipment required for single cabinet, multiple antenna configuration withdiversity

Quantity Unit

9 Antennas

1 BTS cabinet

3 DRCU/SCU

Transmitter

3 Bandpass filter

Receiver


GSR6 (Horizon II)Multiple cabinet RF configurations

30 Sep 200315�46


GMR-0168P02900W21-M

Multiple cabinet RF configurations

Multiple cabinet, single antenna, four DRCU/SCUs

A multiple cabinet, single antenna configuration without diversity is shown in Figure 15-9.This configuration provides eight carriers on one antenna using hybrid combiners.Table 15-14 provides a summary of the equipment required for this configuration. Thefollowing rules apply:

S DRCU/SCUs can be connected to the combiners in any order. The transmit powerof a DRCU/SCU at the top of the cabinet depends on the number of combinerlevels it goes through. Each level of hybrid combining results in a loss of up to3.2 dB of carrier power.

S The antenna feed to cabinet 2 originates from the test (unused) 6-way splitter portin cabinet 1. An inline attenuator is required to ensure specified performance.

S This configuration may not be implemented using ExCell.


Figure 15-9 Multiple cabinet, single antenna, 4 DRCU/SCUs

BTS CABINET 1

1 2 3 4

Rx

BTS CABINET 2

Tx BPF

1 2 3 4

Tx

ATTENUATOR

HYBRID

HYBRID HYBRID HYBRID HYBRID

HYBRID

HYBRID

DRCU/SCUs DRCU/SCUs



GSR6 (Horizon II) Multiple cabinet RF configurations

30 Sep 2003


68P02900W21-M

GMR-0115�47

Table 15-14 Equipment required for multiple cabinet, single antenna 4 DRCU/SCUconfiguration

Quantity Unit

2 Antennas

2 BTS cabinet

8 DRCU/SCU

Transmitter

7 Hybrid combiners

1 Bandpass filter

Receiver

1 Attenuator



30 Sep 200315�48


GMR-0168P02900W21-M

Multiple cabinet, single antenna, ten DRCU/SCUs

A multiple cabinet, single antenna configuration is shown in Figure 15-10. Thisconfiguration provides ten carriers on one antenna using hybrid combiners. Table 15-15provides a summary of the equipment required for this configuration. The following rulesapply:

S If one site/sector requires ten carriers, this configuration provides the best solutionfrom the point of view of output power.

S If the antenna feed to cabinet 2 originates from the auxiliary port on the rear of theDPP2 in cabinet 1, a passive splitter is required to ensure specified performance.

S If the antenna feed to cabinet 2 originates from a DPP or a preselector in cabinet1, an Rx extender is required to ensure specified performance.



Figure 15-10 Multiple cabinet, single antenna, 10 DRCU/SCUs, remotelytuneable combiners

PASSIVESPLITTER

BTS CABINET 1

1 2 3 4 5

Rx ANTENNA

BTS CABINET 2

Tx BPF

1 2 3 4 5

Tx ANTENNA

PHASINGHARNESS

REMOTELY TUNEABLECOMBINER

DRCU/SCUs

DRCU/SCUs

DPP2

REMOTELY TUNEABLECOMBINER

DPP2


30 Sep 2003


68P02900W21-M

GMR-0115�49

Table 15-15 Equipment required for multiple cabinet, single antenna 10 DRCU/SCUconfiguration using remotely tuneable combiners

Quantity Unit

2 Antennas

2 BTS cabinet

10 DRCU/SCU

Transmitter

2 Remotely tuneable combiners

1 Phasing harness

1 Bandpass filter

Receiver

1 Passive splitter

2 Dual path preselector 2


30 Sep 200315�50


GMR-0168P02900W21-M

Multiple cabinet, multiple antenna

A multiple cabinet, multiple antenna configuration is shown in Figure 15-11. Thisconfiguration represents the minimum amount of equipment that will provide for sixsectors. Table 15-16 provides a summary of the equipment required for thisconfiguration. The following rules apply:

S If only one DRCU/SCU is used per sector, a combiner is not required.



Figure 15-11 Multiple cabinet, multiple antenna (6 sector minimum) configuration

BTS CABINET 1

Tx BPF

BTS CABINET 2

Tx BPF

4 5 6

Tx

2 31

Rx

DRCU/SCUs DRCU/SCUs



TxTx

RxRx Rx

RxRx Tx

TxTx

Table 15-16 Equipment required for multiple cabinet, multiple antenna configuration

Quantity Unit

12 Antennas

2 BTS cabinet

6 DRCU/SCU

Transmitter

6 Bandpass filter

Receiver



30 Sep 2003


68P02900W21-M

GMR-0115�51

Six sector configurationA four cabinet six sector configuration is shown in Figure 15-12; this configurationprovides for three sectors. Table 15-17 provides a summary of the equipment required forthis configuration. The following rules apply:

S The site configuration can make a difference to the equipment required.

S When a receiver multicoupler is used, a multicoupler extender must also be used.One of four types is used depending on the number of cabinets the signal is routedto.

S The multicoupler may not be required for all sectors, if this is the case, theantennas connects directly to the BTS cabinet preselectors and bypasses themulticoupler.

S The large multicoupler extender could be replaced by three 6 dB splitters.

S In this configuration, while DRCU/SCUs 3, 8, 13, 16�18 meet the Motorola-statedtop of cabinet output power specification, DRCU/SCUs 1, 2, 4, 5, 6,7, 9, 10�12,14, and 15 do not because of two levels of hybrid combining. The site does notmeet the specification and the DRCU/SCUs with the higher available transmitpower would have their power reduced.

S The remotely tuneable combiner and multicoupler have not been EMC tested foruse in the external equipment rack. Since the end of 1995 these items have notbeen available for use in this configuration within the European Union.

S This configuration may not be implemented using ExCell or TopCell.

S An external equipment cabinet is required.

Figure 15-12 Four cabinet six sector configuration

Rx Rx Rx Rx Rx Rx

EXTERNALEQUIPMENT

CABINET

BTS CABINET 1 BTS CABINET 2 BTS CABINET 3

1 2 3 4 5

BTS CABINET 4

15

11

12

13

6 7 8 9 10

16

17

18

Tx Tx TxTx Tx Tx

14

MULTICOUPLER

LARGEMULTICOUPLER

EXTENDER


30 Sep 200315�52


GMR-0168P02900W21-M

Table 15-17 Equipment required for a four cabinet, six sector configuration

Quantity Unit

12 Antennas

4 BTS cabinet

1 External equipment cabinet

18 DRCU/SCU

Transmitter

6 Bandpass filter

12 Hybrid combiners

Receiver


1 Multicoupler

1 Multicoupler extender


30 Sep 2003


68P02900W21-M

GMR-0115�53

Six sector BTS6 configuration

A six sector configuration using BTS6s is shown in Figure 15-13; this configurationprovides for three sectors with only three cabinets. Table 15-18 provides a summary ofthe equipment required for this configuration. The following rules apply:

S The site configuration can make a difference to the equipment required.

S In this configuration, while DRCU/SCUs 3, 4, 9, 10, 15, and 16 meet theMotorola-stated top of cabinet output power specification DRCU/SCUs 1, 2, 5, 6,7, 8, 11, 12, 13, 14, 17, and 18 do not because of two levels of hybrid combining.Therefore, the site does not meet the specification and the DRCU/SCUs with thehigher available transmit power would have their power reduced.

S This configuration may not be implemented using ExCell or TopCell.


Figure 15-13 Multiple cabinet, 6 sector BTS6 (3 carriers per sector) configuration

17

18

11

12

BTS CABINET 2 BTS CABINET 3

Tx

BTS CABINET 1

TxRx Rx Tx Rx

1 2 3 4 15

13

7 8 9 10

16

14

5 6

Tx Rx Tx Rx Tx Rx

Table 15-18 Equipment required for multiple cabinet, 6 sector BTS6 configuration

Quantity Unit

12 Antennas

3 BTS cabinet

18 DRCU/SCU

Transmitter

6 Bandpass filter

12 Hybrid combiners

Receiver



30 Sep 200315�54


GMR-0168P02900W21-M

30 Sep 2003


68P02900W21-M

GMR-01 I�1

Index

GSR6 (Horizon II)

30 Sep 2003 I�2


GMR-0168P02900W21-M

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01 I�3

A

Acronyms, 1�16

Air interface control channels, 3�82

Alarm reporting, E1/T1 links, 2�14

Alternative call model, planning examples, 9�19

Antenna gain, 3�29

Antennas, 4�12

Ater interfaceauto�connect mode, 2�21backwards compatibility mode, 2�21

Auto�connect mode, XBL links, 5�34

Average call duration, 11�5

B

Backhaul requirements, 5�22

Baseband hopping, 1�11, 3�44, 3�76

BBBXplanning factors and calculations (BSC), 5�60planning factors and calculations (RXCDR), 6�27

BCCH carrier, options, 3�100

BIBplanning calculations (BSC), 5�58planning calculations (RXU), 6�25planning factors (BSC), 5�58planning factors (RXU), 6�25

Blocking, 3�11

BSCequipage planning, 5�4LCS signalling link capacities, 8�12planning steps outline, 5�5planning steps outline for LCS, 8�10scaleable architecture, 5�8signalling link capacities, 5�9system capacity, 5�7to BTS interconnections, 2�5

BSC to BTS link, procedure capacities, 5�14

BSSblock diagram, 1�6code storage facility processor, 1�11interfaces, 2�4maximum network parameter values to support

GPRS, 7�10planning checklist, 1�15planning diagram, 5�10, 6�7planning for GPRS, 7�4planning overview, 1�13standard configurations, 12�4system architecture, 1�6system components, 1�7typical hardware configuration diagrams, 12�5upgrade rules to support GPRS, 7�9

BSS timeslot allocation, 3�106

BSU shelvesplanning calculations, 5�51planning factors, 5�50

BTSsite restrictions, 2�6standard configurations, 12�4to BSC interconnections, 2�5

BTS concentrationblocking, 2�26concepts and rules, 2�23emergency call handling, 2�27examples, 2�37planning guidelines, 2�35reserved allocation, 2�26resource optimization for handovers (BCROH),

2�43

BTS planning , 4�4

CC7 protocol, 5�15

Call parameters, 3�80, 5�11, 8�12, 11�4sample statistic calculations, 11�10

Carrier timeslot allocation, examples, 3�102

CBL, 5�41

CCCH calculations, 3�85

Cell architecture, 3�69

Cell broadcast channel, 1�11

Cell resource manager, 7�7

Cell site sectorization, 3�43

CLKXplanning calculations (BSC), 5�55planning calculations (RXU), 6�22planning factors (BSC), 5�55planning factors (RXU), 6�22

GSR6 (Horizon II)

30 Sep 2003 I�4


GMR-0168P02900W21-M

Co�channel interference, 3�42

Code storage facility processor, 1�11

Coding schemesGPRS, 3�59impact on interconnect planning, 5�22

Comfort noise, 3�62

Control channel configurations, 3�83, 3�89border location area, 3�93non�border location area, 3�92

CSFP, 5�41

CTU and CTU2, power supply considerations, 4�14

CTU2, in Horizonmacro, 12�47

DDecibel, conversion factors, 3�14

Digital shelf power supplyplanning calculations (BSC), 5�59planning calculations (RXCDR), 6�26planning factors (BSC), 5�59planning factors (RXCDR), 6�26

Directed retry, 7�7

Diversity, 1�10Horizon II macro, 12�23

DPROC, PCU planning process, 7�15, 7�16

DRI and combiner configurations, 4�29

Dynamic allocationBSC to BTS, 7�6BTS links, 2�29network configurations, 2�28performance issues, 2�34RXCDR to BSC circuits, 2�21

DYNETdescription, 2�25device, 2�23

EE1 circuit

daisy chain connection, 2�8multiplexing, 2�11star connection, 2�7

E1 link calculations, 5�45BSC to BTS, 5�22BSC to RXCDR, 6�8RXCDR to MSC, 6�9

E1 linkscable requirements for a fully configured PCU,

7�12PCU to BSC, 7�24

E1/T1, daisy chain examples, 2�9

E1/T1 link connections, 4�17

Emergency call pre�emption, 7�7

EncodingGSM circiut�switched data channel, 3�52GSM control channel, 3�51GSM speech channel, 3�48

enhanced full rate, 3�50

Enhanced auto�connect mode, XBL links, 5�34

Enhanced BSC capacity, 5�8

Enhanced one phaseGSL planning, 5�36RSL planning, 5�20

Equalization, 3�64

Erlang, definition, 2�23

Erlang B, definition, 2�23

Error coding schemes, 3�46

ExpansionBTS sites, 4�26Horizon II macro, 4�21

FFile transit delay, 3�122

FMUX, 4�22

FOX, 4�22

Frequency bands, all systems, 3�38

Frequency channel re�use, 3�38

Frequency hopping, 1�10, 3�44, 7�7

Frequency planning, 3�72

Frequency spectrumDCS1800, 3�7GSM900, 3�6UK network operators, 3�7

Fresnel zone, 3�13, 3�15

GGaussian minimum shift keying, 3�9, 3�44

Gb entities, 7�25

Gb interface, 7�5

Gb link, PCU to SGSN, 7�30

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01 I�5

Gb load, 7�29

Gb signalling overhead, 7�27

GCLKplanning calculations (BSC), 5�54planning calculations (RXU), 6�21planning factors (BSC), 5�54planning factors (RXU), 6�21

GDP, planning factors, 6�12

GDS link, PCU termination, 7�8

GPROC, parameters used to determinerequirements, 5�12

GPROC2acting as CSFP, 5�41BSC types, 5�39BSP redundancy, 5�42enhanced, 6�10LCF and OMF redundancy, 5�42planning factors (BSC), 5�39planning factors (RXCDR), 6�10task groupings and functions, 5�38

GPRS, 1�12air interface planning, 3�114BSS maximum network parameter values, 7�10BSS planning, 7�4BSS to PCU planning example, 7�35BSS upgrade provisioning, 7�9data rates, 3�124dynamic timeslot allocation, 3�99estimating traffic throughput, 3�115LCF GPROC2 provisioning, 5�26load planning, 3�94planning factors, 3�95radio and packet data traffic channels, 3�82timeslot usage, 3�96

GPRS carrier, 3�100

GPRS traffic, timeslot allocation, 3�113

Grade of service, definition, 2�24

GSL, planning calculations, 5�36

GSN, 3�96

H

Handover, 2G � 3G, 3�77

Handovers, ratio per call, 11�7

HDSLcable installation, 2�49cable selection, 2�48OMC�R link management, 2�47

HIISC, 4�20

Horizon II macrocabinet overview, 4�6connecting to Horizonmacro, 12�40connecting to M�Cell6, 12�48four cabinet configuration, 12�14RF configuration diagrams, 12�16single cabinet configuration, 12�8three cabinet configuration, 12�12two cabinet configuration, 12�10

Horizoncompact and Horizoncompact2, cabinetoverview and differences, 4�6

Horizoncompact2, RF configuration diagrams, 12�33

Horizonmacrocabinet overview, 4�6four cabinet configuration, 12�15restrictions when using CTU2s, 4�13RF configuration diagrams, 12�24single cabinet configuration, 12�9three cabinet configuration, 12�13two cabinet configuration, 12�11

Horizonmicro and Horizonmicro2, cabinet featuresand differences, 4�8

Horizonmicro2RF configuration diagrams, 12�37system configuration, 2�51

IIMSI detaches, ratio per call, 11�8

Interface modules, 4�28

Interleaving, 3�53

Intra�BSS handovers, 11�7

JJoint Radio Committee (JRC) of the Nationalized

Power Industries, 3�13

KKSW

planning calculations (BSC), 5�49planning calculations (RXU), 6�17planning factors (BSC), 5�48planning factors (RXU), 6�16

GSR6 (Horizon II)

30 Sep 2003 I�6


GMR-0168P02900W21-M

KSW switching, 5�44

KSWXplanning calculations (BSC), 5�52planning calculations (RXU), 6�19planning factors (BSC), 5�52planning factors (RXU), 6�19

LLANX

planning calculations (BSC), 5�56planning calculations (RXU), 6�23planning factors (BSC), 5�56planning factors (RXU), 6�23

Lapse rate, 3�18

LCF, 5�40GPROC2 provisioning for GPRS, 5�26

LCF calculations, for MTL processing, 5�33

LCF�GPROC2 calculations, for RSL processing,5�24

LCSprovisioning example, 9�42system architecture, 8�6

LLC_PDU, frame layout, 3�120

LMTL, planning calculations, 8�27

Location area planning, 10�3example procedure, 10�4

Location services, overview, 8�4

Location update factor, 3�81, 5�12, 11�9

Location updates, ratio per call, 11�8

MM�Cell, standard configurations, 13�4

M�Cell2cabinet overview, 4�7RF configuration diagrams, 13�49single cabinet configuration, 13�11three cabinet configuration, 13�13

M�Cell6cabinet overview, 4�7connecting to Horizon II macro, 12�48four cabinet configuration, 13�14RF configuration diagrams, 13�16single cabinet configuration, 13�10two cabinet configuration, 13�12

M�Cellaccesshardware configuration diagrams, 13�5PCC cabinet equipage, 4�4system configuration, 2�53

Macrocell, 3�70

MCU, 4�20

MCUF, 4�20

Micro base control unit (microBCU), 4�16

Microcell, 3�70system planning, 2�51

MSC to BSC link, procedure capacities, 5�13

MSI / MSI�2planning calculations (BSC), 5�47planning calculations (RXCDR), 6�15planning factors (BSC), 5�46planning factors (RXCDR), 6�14

MSI�2T1 to E1 conversion, 5�44T1 to E1 conversion for XCDR, 6�12

MTL, planning factors, 5�27

MTL calculationsnon�standard traffic model, 5�31standard traffic model, 5�28

Multipath fading, 3�63

Multiplexing, 2�11

NNailed paths, 2�30

Network interface unit (NIU), 4�17

Network planning exercise, 9�3initial requirements, 9�4

Network planning factors, 3�4

Network topologyBTS site restrictions, 2�6interface restrictions, 2�6

NVM boardplanning factors and calculations (BSC), 5�61planning factors and calculations (RXCDR), 6�28

OOkumura, 3�32

OMC�R, HDSL link management, 2�47

OMC�R planning, reference documents, 1�3

OMF, 5�41

GSR6 (Horizon II)

30 Sep 2003


68P02900W21-M

GMR-01 I�7

One phase accessGSL planning, 5�36RSL planning, 5�20

Output power, mobile handset, 3�65

P

Pages per call, 11�10

Paging rate, 11�9location area planning, 10�3

PCC cabinet, 4�27typical hardware configurations, 13�5

PCU, 1�12device alarms, 7�6frame relay interface parameters, 7�31hardware layout diagram, 7�13interface to SGSN, 7�5link diagram, 7�34provisioning goals, 7�23redundancy planning, 7�20upgrading, 7�23

PCU shelf (cPCI), planning factors, 7�14

Picocell, 3�70system planning, 2�53

PICP board, planning factors, 7�16

PIXplanning calculations (BSC), 5�57planning calculations (RXU), 6�24planning factors (BSC), 5�57planning factors (RXU), 6�24

PMC module, planning factors, 7�18

Power supplies, CTU and CTU2 considerations, 4�14

Power supply, BTS requirements, 4�25

Preventive cyclic retransmission, 5�33

Propagation losses, 3�13

PRP board, planning factors, 7�17

R

RACH arrivals, RSL planning, 5�21

Radio Sonds, 3�17

Radio wave propagationantenna gain, 3�29clutter factor, 3�29DCS1800 path loss, 3�37environmental effects, 3�20free space loss, 3�26GSM900 path loss, 3�36plane earth loss, 3�27power budget and system balance, 3�35Rayleigh environment, 3�24Rician environment, 3�25within buildings, 3�31

Refractometers, 3�17

Reserved allocation, 2�24

Reserved allocation algorithm, uses, 2�36

RF carriers, limitations, 3�8

RF configuration diagramsHorizon II macro, 12�16Horizoncompact2, 12�33Horizonmacro, 12�24Horizonmicro2, 12�37M�Cell2, 13�49M�Cell6, 13�16mixed cabinets, 12�41

RRI measurements, 3�16

RSL, 2�17definition, 2�24planning, 2�27planning constraints, 2�19planning factors, 5�16planning calculations, 5�17

RSL calculationsnon�standard traffic model, 5�20standard traffic model, 5�18

RTFdefinition, 2�24types, 2�17

RTF path, fault containment, 2�15, 2�31, 7�8

RXCDRas E1 switching interface (PCU to SGSN), 7�5equipage planning, 6�4GDP/XCDR planning factors, 5�43links to BSC/MSC, 5�43planning steps, 6�5

RXU shelfplanning calculations, 6�18planning factors, 6�18

SSACCH multiframe, 3�62

GSR6 (Horizon II)

30 Sep 2003 I�8


GMR-0168P02900W21-M

Satellite link, MSC to BSC signalling, 5�33

Satellite links, delay times, 2�34

SDCCH calculations, 3�90

SGSN, 7�5

Short message service, 1�11

Signalling link capacities, BSC, 5�9

Signalling link capacities (LCS), BSC, 8�12

Signalling message sequence, 5�13

Site expansion board, 4�22

SMS, ratio per call, 11�6

Software planning tools, 3�5

Spatial diversity, 3�63

State models, MS and SGSN, 3�98

Static allocation, 2�24

Switchable timeslots, provisioning, 3�108

Synthesizer hopping, 1�11, 3�45, 3�72

System dimensioning, Erlang B model, 3�11

TT1 circuit

daisy chain connection, 2�8multiplexing, 2�11star connection, 2�7

T1 link calculations, 5�45BSC to BTS, 5�23BSC to RXCDR, 6�8RXCDR to MSC, 6�9

T1 to E1 conversion, 5�44for the XCDR, 6�12

T43planning calculations (BSC), 5�58planning calculations (RXU), 6�25planning factors (BSC), 5�58planning factors (RXU), 6�25

TCH to SDCCH conversion, 7�8

TCP/IP, 3�120

TDMA frame structure, 3�53

Terrestrial backhaul, definition, 2�24

Terrestrial backhaul resources, 2�27, 2�32

Timeslot, allocation algorithms, 2�13

Timeslot allocationdynamic (GPRS), 3�99GPRS traffic, 3�113

Timeslot multiplexer site, 2�30

Timeslot provisioning, GPRS, 3�117

Timeslots, 3�119switchable and reserved (GPRS), 3�100switchable utilization (GPRS), 3�110

Traffic intensity, 3�12

Traffic model and capacity calculations, 1�13

Training sequence code, 3�64

Transceiver, types, 1�7

Transceivers, 4�13

Transcoder, BSSC cabinet hardware diagram, 12�7

Transcoding, at the BSC, 5�45

Transition module, planning factors, 7�19

Transmit configurations, M�Cell and Horizonmacro,4�11

TRAU32 kbit/s, 3�61definition, 2�25

UUMTS, 3�77

XXBL, 2�20

planning calculations, 5�34planning factors, 5�34

XCDRplanning factors, 6�12sub�multiplexing and speech transcoding, 6�11T1 to E1 conversion, 6�12

XMUX, 4�22

bss equipment planning

Documents