BSS Planing

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
INTRODUCTION TO TRANSMISSION SYSTEMS BSS CELL PLANNING BTS PLANNING STEPS AND BSC PLANNING STEPS AND
PLANNING RULES RULES
RXCDR PLANNING STEPS PCU UPGRADE FOR THE BSC PLANNING STEPS AND OMC-R PLANNING STEPS PLANNING EXERCISE
AND RULES BSS RULES FOR LCS AND RULES
PAGING & LOCATION CALL MODEL PARAMETERS STANDARD BSS & HORIZON M-CELL BTS PREVIOUS GENERATION
AREA PLANNING BTS CONFIGURATIONS CONFIGURATIONS BSC PLANNING STEPS
CHAPTER 16
EQUIPMENT DESCRIPTIONS
FOR PRE M-CELL BTSs
GSM-001-103
Manual Revision
GMR-01
68P02900W21-K 30th Jun 02
Motorola manual
affected
Incorporate this GMR only in the manual number and version listed below:
68P02900W21-K System Information: BSS Equipment Planning

Software Release GSR6
Problem reports
This revision provides a fix to the following problem reports:
SR1030458
Reason for
revision
This revision provides additional and updated information as follows:
Chap. 5: Page 5-21: Note relating to 70% GPROC2 utilization removed.

Chap. 7: Page 7-12: PCU shelf (MPROC board) planning considerations clarified.
Action
Remove and replace pages in the Manual as follows:
Remove Insert
All pages between the clear acetate All pages of the GMR between the
front sheet and the blank backing front sheet and the blank backing
sheet, remove from binder. sheet, 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 or
back of the manual, for future reference.
System Information: BSS Equipment Planning

30th Jun 02 68P02900W21-K GMR Page 1
GMR-01
GSM-001-103

GMR Page 2 68P02900W21-K 30th Jun 02
GMR-01
BSS Equipment Planning
6
GSR System Information
GSM-001-103
GSM Software Release 6
GMR-01
68P02900W21-K
Positin mark for TED spine
Information
BSS Equipment
68P02900W21-K
System
GMR-01
6
System Information
Planning
GSM-001-103
GSR
GSM Software Release 6
GMR-01
GSM-001-103
Software Release GSR6
System Information
E Motorola 1994-2002
All Rights Reserved
Printed in the UK.

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103
Copyrights, notices and trademarks
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
and MOTOROLA are registered trademarks of Motorola Inc.

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

ii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Contents
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 1
Introduction to planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Introduction to BSS planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Manual overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
BSS equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
Transceiver units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
BSS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Features that affect planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Short message service, cell broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
PCU for GPRS upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
BSS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Initial information required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Planning methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
Acronym list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
Chapter 2
Transmission systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Interconnecting the BSC and BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Interconnection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3

30th Jun 02 68P02900W21-K iii
GMR-01
GSM-001-103
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
Daisy chain connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Daisy chain planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
Aggregate Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
RTF path fault containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
16 kbit/s RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
16 kbit/s XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Dynamic allocation of RXCDR to BSC circuits (DARBC) . . . . . . . . . . . . . . . . . . . . 2–19
BTS concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–21
DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–23
Blocking considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–24
Radio signalling link (RSL) planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–25
Network topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–26
Performance issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–32
Configuration and compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–32
Recommended BTS concentration planning guidelines . . . . . . . . . . . . . . . . . . . . . 2–33
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–35
BTS concentration resource optimization for handovers (BCROH) . . . . . . . . . . . 2–41
BCROH description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–41
Managed HDSL on micro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–45
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–45
Integrated HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–46
General HDSL guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–48
Microcell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–49
Picocell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–51
Chapter 3
BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
BSS cell planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
BSS planning requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Planning factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Planning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
GSM frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
The GSM900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
The DCS1800 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
The PCS1900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Horizonmacro adaptation for 850/1900 MHz operation . . . . . . . . . . . . . . . . . . . . . 3–6
Absolute radio frequency channel capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Modulation techniques and channel spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Channel blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
Traffic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Grade of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10

iv 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Propagation effects on GSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11

Propagation production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11
Decibels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Fresnel zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13
Radio refractive index (RRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Environmental effects on propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Multipath propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–21
GSM900 path loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34
Path loss GSM900 vs DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Frequency re-use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Introduction to re-use patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37
Carrier/ Interference (C/I) ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–40
Other sources of interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–41
Sectorization of sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–41
Overcoming adverse propagation effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
Hardware techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
Error protection and detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–44
GSM speech channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–46
GSM speech channel coding for enhanced full rate . . . . . . . . . . . . . . . . . . . . . . . . 3–48
GSM control channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49
GSM circuit-switched data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Mapping logical channels onto the TDMA frame structure . . . . . . . . . . . . . . . . . . . 3–51
GPRS channel coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–57
32 kbit/s TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–59
Voice activity detection (VAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–60
Discontinuous transmission (DTX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–60
Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–61
Subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63
Subscriber hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63
Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Hand portable subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–65
Future planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–66
The microcellular solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–67
Layered architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–67
Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–68
Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–69
Expansion solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–69
Frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Introduction to frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Rules for synthesizer frequency hopping (SFH) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Rules for baseband hopping (BBH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
2G–3G handovers using inter-radio access technology . . . . . . . . . . . . . . . . . . . . . . . . . . 3–75
Introduction to 2G–3G handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–75
2G–3G handover description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–75
Impact of 2G–3G handovers on GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–76
System considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–77
Call model parameters for capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78

30th Jun 02 68P02900W21-K v
GMR-01
GSM-001-103
Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80
Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–81
Number of CCCHs per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–83
Number of SDCCHs per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–87
Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–89
GPRS traffic planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–91
Determination of expected load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–91
Network planning flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–91
GPRS network traffic estimation and key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–92
Introduction to the GPRS network traffic estimation and key concepts . . . . . . . . 3–92
Dynamic timeslot mode switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–96
Carrier timeslot allocation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–99
BSS timeslot allocation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–103
Provisioning the network with switchable timeslots . . . . . . . . . . . . . . . . . . . . . . . . . 3–105
Recommendation for switchable timeslot usage . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–109
Timeslot allocation process on carriers with GPRS traffic . . . . . . . . . . . . . . . . . . . 3–110
GPRS air interface planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–111
Introduction to the GPRS air interface planning process . . . . . . . . . . . . . . . . . . . . 3–111
Estimating the air interface traffic throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–112
GPRS data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–121
Chapter 4
BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
BTS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Macrocell cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Horizoncompact and Horizoncompact2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Microcell enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Horizonmicro and Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Receive configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Receiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Transmit planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Antenna planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Carrier equipment (transceiver unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
Transceiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11

vi 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Micro base control unit (microBCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
MicroBCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Network interface unit (NIU) and site connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
NIU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Main control unit, with dual FMUX (MCUF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
MCUF planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
Main control unit (MCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
MCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Cabinet interconnection (FMUX/FOX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
FMUX/FOX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Power planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Network expansion using macro/micro/picocell BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Expansion considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Mixed site utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
PCC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
Line interface modules (HIM-75, HIM-120) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
HIM-75/HIM-120 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
DRI/Combiner operability components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
DRI and combiner relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
Chapter 5
BSC planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
BSC system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
System capacity summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Scaleable BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Enhanced BSC capacity option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6

30th Jun 02 68P02900W21-K vii
GMR-01
GSM-001-103
Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13
Determining the number of RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Determining the number of RSLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–19
BSC to BTS T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Determining the number of LCF-GPROC2s for RSL processing . . . . . . . . . . . . . 5–21
Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30
Determining the number of XBLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–31
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–31
Determining the number of XBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–31
Non standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32
Determining the number of GSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–33
Generic processor (GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–35
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–35
GPROC2 functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–35
BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–36
GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
OMF GPROC2 required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
GPROC2 redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
GDP/XCDR planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–41
Planning actions for transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–43
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–43
MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Kiloport switch (KSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–45
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–45
KSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46

viii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–47

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–47
BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–48
Kiloport switch extender (KSWX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–49
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–49
KSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–49
Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–51
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–51
GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–51
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
Local area network extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–53
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–53
LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–53
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
Line interface boards (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–55
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–55
BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–55
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–56
Battery backup board (BBBX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–57
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–57
BBBX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–57
Non volatile memory (NVM) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
Chapter 6
RXCDR planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
Remote transcoder planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2

30th Jun 02 68P02900W21-K ix
GMR-01
GSM-001-103
RXCDR to BSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
RXCDR to MSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Generic processor (GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
GPROC planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
Planning actions for transcoding at the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
MSI planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–13
RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
RXU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–18
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–19
LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–21

x 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Non volatile memory (NVM) board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
Verify the number of RXU shelves and BSSC cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Chapter 7
PCU upgrade for the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Introduction to BSS planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
PCU to SGSN interface planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
Feature compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4
BSS upgrade to support GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
BSS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
Maximum BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8
PCU hardware layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
PCU shelf (cPCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–12
MPROC board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13
Planning considerations (PSP use) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13
DPROC board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
Planning considerations (PICP or PRP use) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
PMC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–16
Transition module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
PCU equipment redundancy and provisioning goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–18
Support for N + 1 equipment redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–18
PCU redundancy planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–18
Upgrading the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–21

30th Jun 02 68P02900W21-K xi
GMR-01
GSM-001-103
E1 link provisioning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–22

E1 interface provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–22
PCU – SGSN: traffic and signalling planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–23
Gb entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–23
General planning guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–24
Specific planning guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–24
The Gb signalling overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–25
Determine the net Gb load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–27
Gb link timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–28
Frame relay parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–29
BSS – PCU hardware planning example for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–32
Introduction to BSS – PCU hardware planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–32
BSS – PCU planning example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–33
Chapter 8
BSC planning steps and rules for LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to LCS planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
LCS description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
LCS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
The positioning mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
Overview of BSC planning for LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Introduction to GSR6 LCS provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9
BSC LCS signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Determining the number of RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
Determining the number of RSLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
Determine the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . 8–17
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–18
Planning actions for transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–24

xii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Determining the number of LMTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–25

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–25
Determining the number of LMTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–25
Generic processor (GPROC2) for LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
GPROC2 functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Chapter 9
OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview of OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Introduction to OMC-R planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
The OMC-R and GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Planning a GSR4.x or GSR5 OMC-R scaleable system . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
OMC-R capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
Server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Server ancillary equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
GUI server hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Optional printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Datacomms equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
Additional optional items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
Network support program (NSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
Upgrading the OMC-R system from GSR 4.x to GSR5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Introduction to upgrading the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Hardware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Upgrading the OMC-R to GSR6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Introduction to upgrading the OMC-R to GSR6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Hardware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Chapter 10
Planning exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Introduction to the planning exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
Initial requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
The exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Determine the hardware requirements for BTS B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–6
Determine the hardware requirements for BTS K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8
Receiver requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8
Transmitter combining requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–9

30th Jun 02 68P02900W21-K xiii
GMR-01
GSM-001-103
Determine the hardware requirements for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–11

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–11
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13
Determine the hardware requirements for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
MSI requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
Transcoder requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
Link interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
GPROC2 requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
KSW requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
KSWX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
GCLK requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
CLKX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
PIX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
BBBX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
LANX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–16
Determine the requirements for the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–17
OMC-R example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–17
Calculations using alternative call models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–19
Planning example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–19
Planning example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–31
A planning example of BSS support for LCS provisioning . . . . . . . . . . . . . . . . . . . . . . . . . 10–42
Introduction to the LCS planning example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–42
LCS planning example calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–43
Chapter 11
Paging rate and location area planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Location area planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
Introduction to location area planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
Location area planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
Location area planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Example procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Chapter 12
Deriving call model parameters from network statistics . . . . . . . . . . . . . . . i
Introduction to deriving call model parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
Deriving call model parameters from network statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
Standard call model parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
Call duration (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
Ratio of SMSs per call (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4
Ratio of handovers per call (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
Ratio of intra BSS handovers to all handovers (i) . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
Ratio of location updates per call (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Ratio of IMSI detaches per call (Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Location update factor (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
Paging rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
Pages per call (PPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
Sample statistic calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8

xiv 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Chapter 13
Standard BSS and Horizon BTS configurations . . . . . . . . . . . . . . . . . . . . . . . i
BSS/BTS equipment covered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Standard configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–2
Introduction to standard configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–2
Typical BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
BSC with 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
BSC with full redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–4
Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–5
Single cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–6
Single cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–6
Two cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
Two cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
Three cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8
Three cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8
Four cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–9
Four cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–9
Horizon macrocell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–10
Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–10
Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–10
Horizoncompact2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–19
Microcell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
Connecting Horizon BTS cabinets to M-Cell6 BTS cabinets . . . . . . . . . . . . . . . . . . . . . . . 13–26
Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–26
900 MHz BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–26
1800 MHz BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–27
Chapter 14
M-Cell BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
M-Cell equipment covered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1
Standard M-Cell configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–2
Introduction to standard M-Cell configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–2
Picocell (M-Cellaccess) configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3
Single site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3
Two site cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5
Single cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–7
Single cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–7
Single cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–8
Two cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–9
Two cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–9
Three cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–10
Three cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–10
Four cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–11
Four cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–11

30th Jun 02 68P02900W21-K xv
GMR-01
GSM-001-103
M-Cell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–12

Overview of M-Cell configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–12
M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–13
M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–44
Chapter 15
Previous generation BSC planning steps and rules . . . . . . . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–4
BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–5
Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–9
Determining the RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–10
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–10
Calculate the number of LCFs for RSL processing . . . . . . . . . . . . . . . . . . . . . . . . . 15–13
Assigning BTSs to LCFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–14
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–15
MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–19
Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–20
GPROC functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–20
BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–21
GPROC planning actions (GSR3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–24
GPROC planning actions (GSR2 and earlier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–25
Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–25
OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–25
GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–26
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–27
T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–28
Planning actions transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–29

xvi 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–30
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–32
BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–34
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–34
BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–34
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–35
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–37
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–38
LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–39
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–39
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–40
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–41
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–42
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–43
Verify the number of BSU shelves and BSSC2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 15–44
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–44
Chapter 16
Planning and equipment descriptions for pre M-Cell BTSs . . . . . . . . . . . . . i
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1

30th Jun 02 68P02900W21-K xvii
GMR-01
GSM-001-103
BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5
Calculations for determining BTS GPROC, GPROC2 requirements . . . . . . . . . . . . . . . . 16–6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–6
Call processing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–6
GPROC, GPROC2 management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–7
GPROC, GPROC2 planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–8
BTS shelf configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–9
Shelf configurations for typical call mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–10
Shelf configurations for border location area call mix . . . . . . . . . . . . . . . . . . . . . . . 16–11
BTS equipment cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–12
Cabinet planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–12
Receiver front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–13
RFE in cabinet types EG, FG and BTS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–13
RFE in cabinet types AG, BG and DG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–13
Distributing Rx signals between multiple cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 16–14
RFE planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–15
Transmit combiner shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–16
Transmit combining equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–16
Transmit combiner shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–17
Duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18
Duplexer planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18
Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–19
Carrier equipment planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–21
Generic processor (GPROC, GPROC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–23
GPROC, GPROC2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–23

xviii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Timeslot switch (TSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–24

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–24
TSW planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–26
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–27
Local area extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–29
Digital radio interface extender (DRIX3c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–30
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–30
DRIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–30
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–31
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–32
BTS RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–33
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–33
Typical BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–34
BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–34
TopCell BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–35
Single cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–36
Single cabinet, single DRCU/SCU without diversity . . . . . . . . . . . . . . . . . . . . . . . . 16–36
Single cabinet, single DRCU/SCU with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–37
Single cabinet, five DRCU/SCUs with combining . . . . . . . . . . . . . . . . . . . . . . . . . . 16–38
Single cabinet, six DRCU/SCUs with combining and diversity . . . . . . . . . . . . . . . 16–40
Single cabinet, multiple antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–42
Single cabinet, multiple antennas with diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–43

30th Jun 02 68P02900W21-K xix
GMR-01
GSM-001-103
Multiple cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–44

Multiple cabinet, single antenna, four DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . 16–44
Multiple cabinet, single antenna, ten DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . . . . . 16–46
Multiple cabinet, multiple antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–48
Six sector configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–49
Six sector BTS6 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–51
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–1

xx 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
List of Figures
Figure 1-1 BSS block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

Figure 2-1 BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Figure 2-2 Possible network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Figure 2-3 Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
Figure 2-4 Closed loop and open ended daisy chains . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Figure 2-5 Simple daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
Figure 2-6 Daisy chain with branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Figure 2-7 Typical low capacity BSC/BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Figure 2-8 Example using a switching network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Figure 2-9 Timeslot allocation using new and old algorithms . . . . . . . . . . . . . . . . . . . . . . 2–11
Figure 2-10 Alternative network configuration with E1/T1 switching network . . . . . . . . 2–12
Figure 2-11 A configuration with a BTS equipped with two redundant RTFs . . . . . . . . 2–14
Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs . . . . 2–14
Figure 2-13 Fully equipped RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Figure 2-14 Sub-equipped RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Figure 2-15 XBL utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Figure 2-16 A dynamic pool of terrestrial backhaul resources . . . . . . . . . . . . . . . . . . . . . 2–25
Figure 2-17 Spoke configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–26
Figure 2-18 Daisy chain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–26
Figure 2-19 Closed loop daisy chain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–26
Figure 2-20 Spoke configuration with three links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–27
Figure 2-21 Daisy chain configuration with two links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–27
Figure 2-22 Closed loop daisy chain configuration with three links . . . . . . . . . . . . . . . . . 2–27
Figure 2-23 Closed loop daisy chain configuration with third party multiplexer . . . . . . . 2–28
Figure 2-24 Extra path definition for nailed connections . . . . . . . . . . . . . . . . . . . . . . . . . . 2–28
Figure 2-25 Terrestrial backhaul resource nailed connection before a call . . . . . . . . . . 2–30
Figure 2-26 Terrestrial backhaul resource connections during a call . . . . . . . . . . . . . . . 2–30
Figure 2-27 Using redundancy for extra capacity before failure . . . . . . . . . . . . . . . . . . . 2–31
Figure 2-28 Using redundancy for extra capacity after failure . . . . . . . . . . . . . . . . . . . . . 2–31
Figure 2-29 BSC controlled intra cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–41
Figure 2-30 BSC controlled inter cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–42
Figure 2-31 Method 1 (override_intra_bss_pre_transfer is enabled) . . . . . . . . . . . . . . . 2–43
Figure 2-32 Method 2 (override_intra_bss_pre_transfer is disabled) . . . . . . . . . . . . . . . 2–44
Figure 2-33 Conversion of E1 to HDSL links by modem and microsite . . . . . . . . . . . . . 2–48
Figure 2-34 Microcell daisy chain network configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2–49
Figure 2-35 Microcell star network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–49
Figure 2-36 Microcell configuration using E1/HDSL links . . . . . . . . . . . . . . . . . . . . . . . . . 2–50
Figure 2-37 M-Cellaccess picocell system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–51

30th Jun 02 68P02900W21-K xxi
GMR-01
GSM-001-103
Figure 3-1 UK network operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5

Figure 3-2 Eight TDMA timeslots per RF carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Figure 3-3 Modulation techniques and channel spacing . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Figure 3-4 First Fresnel zone radius calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13
Figure 3-5 Refraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Figure 3-6 Measurement of the RRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
Figure 3-7 Refraction effects on a microwave system . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
Figure 3-8 Attenuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Figure 3-9 Reflection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Figure 3-10 Scattering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–19
Figure 3-11 Diffraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–19
Figure 3-12 Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Figure 3-13 Propagation effect – Rayleigh fading environment . . . . . . . . . . . . . . . . . . . . 3–22
Figure 3-14 Rayleigh distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Figure 3-15 Propagation effect – Rician environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–23
Figure 3-16 Rician distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–23
Figure 3-17 Plane earth loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Figure 3-18 Focusing of power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–27
Figure 3-19 Measurement of gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Figure 3-20 In building propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–29
Figure 3-21 Okumura propagation graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–31
Figure 3-22 BTS antenna height of 50 m, MS height of 1.5 m (GSM900) . . . . . . . . . . . 3–34
Figure 3-23 BTS antenna height of 100 m, MS height of 1.5 m (GSM900) . . . . . . . . . . 3–34
Figure 3-24 Path loss vs cell radius for small cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Figure 3-25 Adjacent cell interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Figure 3-26 7 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37
Figure 3-27 4 site – 3 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Figure 3-28 2 site – 6 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39
Figure 3-29 Carrier interference measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–40
Figure 3-30 The coding process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–44
Figure 3-31 Error protection and detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–45
Figure 3-32 Speech channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–47
Figure 3-33 Preliminary coding for enhanced full rate speech . . . . . . . . . . . . . . . . . . . . . 3–48
Figure 3-34 Control channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49
Figure 3-35 Data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–50
Figure 3-36 Diagonal interleaving – speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–52
Figure 3-37 Rectangular interleaving – control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–54
Figure 3-38 Diagonal interleaving – CS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–56
Figure 3-39 GPRS channel coding scheme 1 (CS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–57

xxii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103

Figure 3-43 SACCH multiframe (480 ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–60
Figure 3-44 Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–61
Figure 3-45 Training sequence code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–62
Figure 3-46 The subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–63
Figure 3-47 Subscriber distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–64
Figure 3-48 Layered architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–67
Figure 3-49 Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–68
Figure 3-50 Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–69
Figure 3-51 Separating BCCH and TCH bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Figure 3-52 Band usage for macrocells with microcells . . . . . . . . . . . . . . . . . . . . . . . . . . 3–70
Figure 3-53 Frequency split for TCH re-use planning example . . . . . . . . . . . . . . . . . . . . 3–72
Figure 3-54 Avoiding co-channel and adjacent channel interference . . . . . . . . . . . . . . . 3–73
Figure 3-55 BBH frequency spectrum allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–74
Figure 3-56 GSM and UMTS system nodes and interfaces . . . . . . . . . . . . . . . . . . . . . . . 3–77
Figure 3-57 Location area diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–87
Figure 3-58 MM state models for MS and SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–95
Figure 3-59 Carrier with reserved and switchable GPRS timeslots . . . . . . . . . . . . . . . . 3–104
Figure 3-60 1 circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots 3–106
Figure 3-61 One carrier, all timeslots (8 TCHs) designated as switchable . . . . . . . . . . 3–106
Figure 3-62 LLC_PDU frame layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–117
Figure 4-1 DRI and combiner relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
Figure 5-1 BSS planning diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Figure 6-1 BSS planning diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
Figure 6-2 Sub-multiplexing and speech transcoding at the RXCDR . . . . . . . . . . . . . . . 6–8
Figure 7-1 Gb interface alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
Figure 7-2 PCU shelf layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11
Figure 7-3 Goal: maximum throughput and coverage, fully redundant configuration . . 7–19
Figure 7-4 Goal: maximum throughput and coverage, full redundancy not required . . 7–20
Figure 7-5 Frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–29
Figure 7-6 PCU equipment and link planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–32
Figure 8-1 Generic LCS logical architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
Figure 8-2 NSS-based architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
Figure 8-3 BSS-based architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7
Figure 10-1 Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
Figure 11-1 Four BSCs in one LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Figure 11-2 Four BSCs divided into two LACs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4

30th Jun 02 68P02900W21-K xxiii
GMR-01
GSM-001-103
Figure 13-1 BSC controlling 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3

Figure 13-2 Fully redundant BSC controlling 34 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–4
Figure 13-3 BSSC cabinet equipped to provide transcoding . . . . . . . . . . . . . . . . . . . . . . 13–5
Figure 13-4 Macrocell BTS with one Horizonmacro cabinet . . . . . . . . . . . . . . . . . . . . . . 13–6
Figure 13-5 Macrocell BTS with two Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . 13–7
Figure 13-6 Macrocell BTS with three Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . 13–8
Figure 13-7 Macrocell BTS with four Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . 13–9
Figure 13-8 4 carrier omni, duplexed hybrid and air combining . . . . . . . . . . . . . . . . . . . . 13–11
Figure 13-9 6 carrier omni, duplexed dual-stage hybrid and air combining . . . . . . . . . . 13–12
Figure 13-10 2 sector (3/3), duplexed dual-stage hybrid combining . . . . . . . . . . . . . . . . 13–13
Figure 13-11 2 sector (6/6), duplexed dual-stage hybrid and air combining . . . . . . . . . 13–14
Figure 13-12 3 sector (2/2/2), duplexed hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . 13–15
Figure 13-13 3 sector (4/4/4), duplexed hybrid and air combining . . . . . . . . . . . . . . . . . 13–16
Figure 13-14 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1) 13–17
Figure 13-15 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2) 13–18
Figure 13-16 Horizoncompact2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–20
Figure 13-17 Horizoncompact2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Figure 13-18 Horizoncompact2 three BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–22
Figure 13-19 Horizonmicro2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
Figure 13-20 Horizonmicro2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
Figure 13-21 Horizonmicro2 three BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
Figure 13-22 900 MHz Horizonmacro and 900 MHz M-Cell6 interconnections . . . . . . 13–26
Figure 13-23 1800 MHz Horizonmacro and 1800 MHz M-Cell6 interconnections . . . . 13–27
Figure 14-1 Single BTS site with 6 PCUs using fibre optic links . . . . . . . . . . . . . . . . . . . 14–3
Figure 14-2 Single BTS site with 6 PCUs using HDSL links . . . . . . . . . . . . . . . . . . . . . . 14–4
Figure 14-3 Two BTS site with 12 PCUs using optical fibre links . . . . . . . . . . . . . . . . . . 14–5
Figure 14-4 Two BTS site with 12 PCUs using HDSL links . . . . . . . . . . . . . . . . . . . . . . . 14–6
Figure 14-5 Single cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–7
Figure 14-6 Single cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–8
Figure 14-7 Two cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–9
Figure 14-8 Three cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–10
Figure 14-9 Four cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–11
Figure 14-10 3 carrier omni, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–13
Figure 14-11 3 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . . . . 14–14
Figure 14-12 4 carrier omni, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–15
Figure 14-13 4 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . . . 14–16
Figure 14-14 6 carrier omni, cavity combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–17
Figure 14-15 6 carrier omni, cavity combining, high power duplexer . . . . . . . . . . . . . . . 14–18
Figure 14-16 8 carrier omni, combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–19

xxiv 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Figure 14-17 2 sector (3/3), hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–20

Figure 14-18 2 sector (3/3), hybrid combining, medium power duplexers . . . . . . . . . . . 14–21
Figure 14-19 3 sector (2/2/2), combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–22
Figure 14-20 3 sector (2/2/2), combining, medium power duplexers . . . . . . . . . . . . . . . 14–23
Figure 14-21 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . . . 14–24
Figure 14-22 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . . . 14–25
Figure 14-23 3 sector (4/4/4), cavity combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–26
Figure 14-24 3 sector (4/4/4), 3-input CBF, hybrid combining . . . . . . . . . . . . . . . . . . . . . 14–27
Figure 14-25 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers . 14–28
Figure 14-27 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers . . . . 14–30
Figure 14-28 3 sector (6/6/6), cavity combining, high power duplexers . . . . . . . . . . . . . 14–31
Figure 14-30 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers . . . . 14–33
Figure 14-31 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1) . . 14–34
Figure 14-32 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2) . . 14–35
Figure 14-33 3 sector (8/8/8), cavity combining, high and medium power duplexers
(Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–36
(Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–37
Figure 14-35 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers
(Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–38
(Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–39
Figure 14-37 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers
(Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–40
(Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–41
Figure 14-39 3 sector (2/2/2), hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–42
Figure 14-40 3 sector (2/2/2), hybrid combining, medium power duplexers . . . . . . . . . 14–43
Figure 14-41 2 carrier, single sector, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–44
Figure 14-42 2 carrier, single sector, hybrid combining, medium power duplexer . . . . 14–45
Figure 14-43 2 sectors (1 carrier per sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–46
Figure 14-44 2 carrier, single sector, air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–47
Figure 14-45 2 sectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–48
Figure 15-1 BSS planning diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–6
Figure 16-1 Single BTS or ExCell site with 4 RF carriers using hybrid combining . . . . 16–34
Figure 16-2 TopCell with 6 RF carriers using hybrid combiners . . . . . . . . . . . . . . . . . . . 16–35
Figure 16-3 Single cabinet, one DRCU/SCU, no diversity . . . . . . . . . . . . . . . . . . . . . . . . 16–36
Figure 16-4 Single cabinet, one DRCU/SCU, diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–37
Figure 16-5 Single cabinet, 5 DRCU/SCUs, remotely tuneable or hybrid combining,
no diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–38

30th Jun 02 68P02900W21-K xxv
GMR-01
GSM-001-103
Figure 16-6 Single cabinet, 6 DRCU/SCUs, remotely tuneable or hybrid

combining, diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–40
Figure 16-7 Single cabinet, multiple antenna (3 sector minimum) configuration . . . . . 16–42
Figure 16-8 Single cabinet multiple antenna configuration, diversity . . . . . . . . . . . . . . . 16–43
Figure 16-9 Multiple cabinet, single antenna, 4 DRCU/SCUs . . . . . . . . . . . . . . . . . . . . . 16–44
Figure 16-10 Multiple cabinet, single antenna, 10 DRCU/SCUs, remotely
tuneable combiners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–46
Figure 16-11 Multiple cabinet, multiple antenna (6 sector minimum) configuration . . . 16–48
Figure 16-12 Four cabinet six sector configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–49
Figure 16-13 Multiple cabinet, 6 sector BTS6 (3 carriers per sector) configuration . . . 16–51

xxvi 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
List of Tables
Table 1-1 Transceiver unit usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5

Table 1-2 Acronym list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
Table 2-1 BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Table 2-2 RTF types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Table 2-3 Summary of required resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–36
Table 2-4 Summary of common pool planning when BTS 1 and 2 have reserved
resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–37
Table 2-5 Summary of traffic and GOS requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–38
Table 2-6 Summary of common pool planning when BTSs have reserved resources . 2–39
Table 2-7 Blocking activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–40
Table 3-1 dBm and dBW to power conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Table 3-2 Interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–51
Table 3-3 Distribution of 456 bits from one 20 ms speech sample . . . . . . . . . . . . . . . . . 3–53
Table 3-4 Coding parameters for GPRS coding schemes . . . . . . . . . . . . . . . . . . . . . . . . 3–59
Table 3-5 Frequency and parameter setting plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–72
Table 3-6 Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–78
Table 3-7 Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–86
Table 3-8 SDCCH planning for typical parameters (non-border location area) . . . . . . . 3–89
Table 3-9 SDCCH planning for typical parameters (border location area) . . . . . . . . . . . 3–90
Table 3-10 MM state model of MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–94
Table 3-11 Options for use_bcch_for_gprs element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–97
Table 3-12 Switchable timeslot utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–107
Table 3-13 Air interface planning inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–111
Table 3-14 1 x 3 2/6 hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–113
Table 3-15 1 x 1 2/18 hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–113
Table 3-16 Non-hopping TU-3 model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–113
Table 3-17 Cell coverage versus carrier to interface (C/I) . . . . . . . . . . . . . . . . . . . . . . . . 3–114
Table 3-18 GPRS data rates (kbit/s) with UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–122
Table 3-19 GPRS data rates (kbit/s) with TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–123
Table 4-1 Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Table 4-2 Site connection requirements for M-Cell2 and M-Cell6 . . . . . . . . . . . . . . . . . . 4–14
Table 4-3 Horizonmacro FMUX requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Table 5-1 BSC maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Table 5-2 Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Table 5-3 Other parameters used in determining GPROC and link requirements . . . . 5–10
Table 5-4 Procedure capacities (MSC – BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
Table 5-5 Procedure capacities (BSC – BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
Table 5-6 Procedure capacities (BSC – RXCDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12

30th Jun 02 68P02900W21-K xxvii
GMR-01
GSM-001-103
Table 5-7 Number of BSC to BTS signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15

Table 5-8 Typical values for GPRS LCF GPROC2 provisioning . . . . . . . . . . . . . . . . . . . 5–23
Table 5-9 Number of MSC and BSC signalling links (20% utilization) . . . . . . . . . . . . . . 5–26
Table 5-10 Number of MSC and BSC signalling links (40% utilization) . . . . . . . . . . . . . 5–27
Table 5-11 Number of BSC to RXCDR signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–31
Table 5-12 KSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Table 5-13 KSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Table 6-1 KSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
Table 6-2 KSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
Table 7-1 BSS upgrade in support of GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
Table 7-2 Maximum BSS network parameter values in support of GPRS (part A) . . . 7–8
Table 7-3 Maximum BSS network parameter values in support of GPRS (part B) . . . 7–9
Table 7-4 Maximum BSS network parameter values in support of GPRS (part C) . . . 7–10
Table 7-5 PCU provisioning goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–21
Table 7-6 Gb entities and identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–23
Table 7-7 Signalling overhead per GMM signaling procedure . . . . . . . . . . . . . . . . . . . . . 7–25
Table 7-8 Overhead on each downlink GMM/SM message . . . . . . . . . . . . . . . . . . . . . . . 7–25
Table 7-9 PDU data transfer overhead on each downlink GMM/SM message . . . . . . . 7–26
Table 8-1 Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Table 8-2 Other parameters used in determining GPROC and link requirements . . . . 8–11
Table 8-3 LCS procedure capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–12
Table 8-4 Number of BSC to BTS signalling links – LCS supported . . . . . . . . . . . . . . . . 8–14
Table 8-5 Number of MSC and BSC signalling links
(NSS-based LCS at 20% utilization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–20
(BSS-based LCS at 20% utilization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
(NSS-based LCS at 40% utilization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
(BSS-based LCS at 40% utilization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–22
Table 9-1 OMC-R scaleable software – full capacity software load . . . . . . . . . . . . . . . . 9–3
Table 9-2 OMC-R scaleable software – specific capacity software load . . . . . . . . . . . . 9–3
Table 9-3 E3500 server hardware selection (GSR4.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Table 9-4 E3500 server hardware selection (GSR5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Table 10-1 Busy hour demand and number of carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Table 10-2 Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . . . . . . 10–6
Table 10-3 Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . . . . . . 10–7
Table 10-4 Customer ordering guide 1800 MHz (Horizonmacro indoor) . . . . . . . . . . . . 10–9
Table 10-5 Customer ordering guide 1800 MHz (Horizonmacro indoor) . . . . . . . . . . . . 10–10
Table 10-6 GPROC2s required at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–11
Table 10-7 BSC timeslot requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–12

xxviii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Table 10-8 Equipment required for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13

Table 10-9 Equipment required for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–16
Table 10-10 Customer ordering guide for the OMC-R (compulsory items) . . . . . . . . . . 10–17
Table 10-11 Customer ordering guide for the OMC-R (available options) . . . . . . . . . . . 10–18
Table 10-12 Typical LCS call model parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–42
Table 12-1 Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
Table 12-2 Sample statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
Table 13-1 Equipment required for single cabinet, four CTU configuration,
duplexed hybrid and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–11
Table 13-2 Equipment required for single cabinet, six CTU configuration,
duplexed dual-stage hybrid and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–12
duplexed dual-stage hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–13
Table 13-4 Equipment required for dual cabinet, 12 CTU configuration,
duplexed hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–15
Table 13-6 Equipment required for dual cabinet, 12 CTU configuration
duplexed hybrid and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–16
Table 13-7 Equipment required for four cabinet, 24 CTU configuration,
Table 14-1 Equipment required for single cabinet, 4 TCU configuration with hybrid
combining and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–13
combining, diversity and medium power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–14
Table 14-5 Equipment required for single cabinet, 6 TCU configuration with cavity
combining, diversity and high power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–18
Table 14-7 Equipment required for multiple cabinet, 8 TCU configuration with
Table 14-9 Equipment required for single cabinet, 6 TCU configuration with
combining, diversity and medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–23
Table 14-12 Equipment required for dual cabinet, 12 TCU configuration with air
combining, diversity and medium power duplexers (3 antenna per sector) . . . . . . . . . . 14–24
Table 14-13 Equipment required for multiple cabinet, 12 TCU configuration with air
combining, diversity and medium power duplexers (2 antenna per sector) . . . . . . . . . . 14–25
Table 14-14 Equipment required for multiple cabinet, 12 TCU configuration with hybrid

30th Jun 02 68P02900W21-K xxix
GMR-01
GSM-001-103
Table 14-15 Equipment required for dual cabinet, 12 TCU configuration with 3-input
CBF, hybrid combining and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–27
3-input CBF, air combining, diversity and medium power duplexers . . . . . . . . . . . . . . . . 14–28
Table 14-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-input
CBF, air combining, diversity and medium power duplexers (3 antennas/sector) . . . . . 14–29
CBF, combining, diversity and medium power duplexers (2 antennas/sector) . . . . . . . . 14–30
Table 14-19 Equipment required for 3 RF cabinets, 18 TCU configuration with
cavity combining, diversity and high power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–31
CBF, combining, diversity and medium power duplexers (2 antennas/sector) . . . . . . . 14–33
Table 14-22 Equipment required for 4 RF cabinets, 24 TCU configuration with cavity
combining, diversity and both high and medium power duplexers . . . . . . . . . . . . . . . . . . 14–37
CBF, combining, diversity and medium power duplexers (2 antennas/sector) . . . . . . . . 14–41
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–46
Table 14-31 Equipment required for single cabinet, 2 TCU configuration with air
Table 14-32 Equipment required for single cabinet, 2 TCU configuration with diversity 14–48
Table 15-1 Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–7
Table 15-2 Other parameters used in determining GPROC and link requirements . . . 15–8
Table 15-3 Procedure capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–8
Table 15-4 Number of BSC to BTS signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–10
Table 15-5 Number of MSC to BSC signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–16
Table 15-6 KSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–36
Table 15-7 KSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–36
Table 16-1 Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
Table 16-2 Maximum number of Erlangs supported by the BTP . . . . . . . . . . . . . . . . . . . 16–8
Table 16-3 Recommended BTP/DHP configurations and max_dris values for the
first shelf of a BTS (3 RTFs per DHP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–10
Table 16-4 Other shelves (3 RTFs per DHP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–10

xxx 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
Table 16-5 Recommended BTP/DHP configurations and max_dris values for the first
shelf of a BTS (3 RTFs per DHP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–11
Table 16-6 Other shelves (3 RTFs per DHP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–11
Table 16-7 Number of BSC to BTS signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–22
Table 16-8 Equipment required for single cabinet, single DRCU/SCU configuration . . 16–36
Table 16-9 Equipment required for single cabinet, single DRCU/SCU configuration with
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–37
Table 16-10 Equipment required for single cabinet, 5 DRCU/SCU configuration with
remotely tuneable or hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–39
diversity and remotely tuneable or hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–41
Table 16-12 Equipment required for single cabinet, multiple antenna configuration . . 16–42
Table 16-13 Equipment required for single cabinet, multiple antenna configuration with
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–43
Table 16-14 Equipment required for multiple cabinet, single antenna 4 DRCU/SCU
configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–45
configuration using remotely tuneable combiners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–47
Table 16-16 Equipment required for multiple cabinet, multiple antenna configuration . 16–48
Table 16-17 Equipment required for a four cabinet, six sector configuration . . . . . . . . . 16–50
Table 16-18 Equipment required for multiple cabinet, 6 sector BTS6 configuration . . . 16–51

30th Jun 02 68P02900W21-K xxxi
GMR-01
GSM-001-103

xxxii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Issue status of this manual
Issue status of this manual
Introduction
The following shows the issue status of this manual since it was first released.
Version information
The following lists the versions of this manual in order of manual issue:
Manual Date of Remarks

issue issue
O 3rd Oct 94 Original issue – Software release 1.2.2.x
A 30th Dec 94 Issue A – Software release 1.2.3.x
B 1st Sep 95 Issue B – Software release 1.3.0.x
C 31st May 96 Issue C – Software release 1.4.0.x
D 28th Mar 97 Issue D – (also supercedes 68P02900W31-B)
E 29th Aug 97 Issue E – includes GSM Software Release 3
F 27th Apr 98 Issue F – includes GSM Software Release 4
G 15th Apr 00 Issue G – includes GSM Software Release 4.1
(1.6.1.3)
H 27th Feb 01 Issue H – includes GSM Software Release 5
J 15th Aug 01 Issue J – includes GSM Software Release 5.1
K 15th Apr 02 Issue K – includes GSM Software Release 6
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
Service GMR Remarks

Request Number
SR1030458 01 Revision to GPROC2 utilization in Chapter 5.

30th Jun 02 68P02900W21-K 1
GMR-01
General information GSM-001-103
General information
Important notice
If this manual was obtained when attending a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel
in the operation, installation and maintenance of the Motorola cellular infrastructure
equipment and ancillary devices. It is recommended that all personnel engaged in such
activities be properly trained by Motorola.
WARNING Failure to comply with Motorola’s operation, installation and

maintenance instructions may, in exceptional circumstances,
lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
About this manual

The 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 and M-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.

2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 General information
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to
represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
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 (Carriage Return) key. The Return key is
identified by the ↵ symbol on both the PC and the Sun
keyboards. The keyboard Return key may also be identified
by the word Return.

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

4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Reporting safety issues
Reporting safety issues
Introduction
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1. Make the equipment concerned safe, for example, by removing power.
2. Make no further attempt to tamper with the equipment.
3. Report the problem directly to the Customer Network Resolution Centre, Swindon
+44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with a
written report by fax, Swindon +44 (0)1793 430987 or China +86 10
68423633 (fax).
4. Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.

30th Jun 02 68P02900W21-K 5
GMR-01
Warnings and cautions GSM-001-103
Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of 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, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

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

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

6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 General warnings
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals. Failure to comply with
these warnings, or with specific warnings elsewhere in the Motorola manuals, violates
safety standards of design, manufacture and intended use of the equipment. Motorola
assumes no liability for the customer’s failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and
within the text of this manual. These must be observed by all personnel at all times when
working with the equipment, as must any other warnings given in text, on the illustrations
and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single
phase or 415 V ac three phase supply which is potentially lethal. Therefore, the areas
where the ac supply power is present must not be approached until the warnings and
cautions in the text and on the equipment have been complied with.
To achieve isolation of the equipment from the ac supply, the ac input isolator must be
set to off and locked.
Within the United Kingdom (UK) regard must be paid to the requirements of the
Electricity at Work Regulations 1989. There may also be specific country legislation
which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment
when in operation. Ensure that all transmitters are switched off when any antenna
connections have to be changed. Do not key transmitters connected to unterminated
cavities or feeders.
Refer to the following standards:
S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10 kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.

30th Jun 02 68P02900W21-K 7
GMR-01
General warnings GSM-001-103
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent
responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Do not ...
... substitute parts or modify equipment.
Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modification of equipment. Contact Motorola if in doubt to
ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain equipment may incorporate components containing the highly toxic material
Beryllium or its oxide Beryllia or both. These materials are especially hazardous if:
S Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
S The dust created by breakage of Beryllia is inhaled.
S Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
Beryllium warning labels are fitted to equipment incorporating Beryllium or Beryllium
Oxide. Observe all safety instructions given on warning labels.
Beryllium Oxide is used within some components as an electrical insulator. Captive within
the component it presents no health risk whatsoever. However, if the component should
be broken open or burnt, the Beryllium Oxide, in the form of dust or fumes, could be
released, with the potential for harm.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium
batteries must not be removed or replaced. Any boards containing defective lithium
batteries must be returned to Motorola for repair.

8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola manuals. Failure to comply with these cautions or
with specific cautions elsewhere in the Motorola manuals may result in damage to the
equipment. Motorola assumes no liability for the customer’s failure to comply with these
requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge.
Although the damage caused by static discharge may not be immediately apparent,
CMOS devices may be damaged in the long term due to static discharge caused by
mishandling. Wear an approved earth strap when adjusting or handling digital boards.
See Devices sensitive to static for further information.

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

In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
S 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 to
replace 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 cotton
overall is preferable.
S If possible work on an earthed metal surface. Wipe insulated plastic 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 an
earthed surface.
S Take care when removing components connected to electrostatic sensitive
devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less
susceptible to electrostatic damage. However PCBs should be handled with care,
preferably by their edges and not by their tracks and pins, they should be transferred
directly from their packing to the equipment (or the other way around) and never left
exposed on the workbench.

10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Motorola manual set
Motorola manual set
Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola equipment.
Generic GSM manuals

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

30th Jun 02 68P02900W21-K 11
GMR-01
Motorola manual set GSM-001-103
Related GSM manuals

The following are related Motorola GSM manuals:
Classification
GSM-001-103 System Information: BSS Equipment Planning . . . . 68P02900W21
GSM-002-103 System Information: DataGen . . . . . . . . . . . . . . . . . . 68P02900W22
GSM-002-703 Software Release Notes: DataGen . . . . . . . . . . . . . . 68P02900W76
GSM-005-103 System Information: GSM Advance Operational
Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02900W25
GSM-008-103 System Information: Network Health Analyst . . . . . . 68P02900W36
GSM-008-703 Software Release Notes: Network Health Analyst . 68P02900W77
GSM-TOOLS-001 System Information: Cell Optimization (COP) . . . . . 68P02900W90
GSM-TOOLS-002 System Information: Motorola Analysis and
Reporting System (MARS) . . . . . . . . . . . . . . . . . . . . . 68P02900W94
GSM-TOOLS-701 Software Release Notes: Cell Optimization (COP) . 68P02900W69
GSM-TOOLS-702 Software Release Notes: Motorola Analysis and
Reporting System (MARS) . . . . . . . . . . . . . . . . . . . . . 68P02900W68
GSM-006-202 Operating Information: OMC-R System
Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W10
GSM-006-413 Installation & Configuration: OSI Clean Install . . . . . 68P02901W39
GSM-006-712 Software Release Notes: OMC-R OSI System . . . . 68P02901W70
Generic GPRS manuals

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

The following are related Motorola GPRS manuals:
Classification
GPRS-001-103 System Information: GPRS Equipment Planning . . 68P02903W02
GPRS-005-103 System Information: GSN Advance Operational
Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02903W38

12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Motorola manual set
BSS service manuals

The following are the Motorola Base Station service manuals, these manuals are not
release dependent. The internal organization and makeup of service manual sets may
vary, they may consist of from one to four separate manuals, but they can all be ordered
using the overall catalogue number shown below:
Classification
GSM-100-020 Service Manual: BTS . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W37
GSM-100-030 Service Manual: BSC/RXCDR . . . . . . . . . . . . . . . . . . 68P02901W38
GSM-105-020 Service Manual: M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . 68P02901W75
GSM-106-020 Service Manual: M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . 68P02901W85
GSM-201-020 Service Manual: M-Cellcity and M-Cellcity+ . . . . . . . 68P02901W95
GSM-202-020 Service Manual: M-Cellaccess . . . . . . . . . . . . . . . . . . 68P02901W65
GSM-203-020 Service Manual: Horizonmicro . . . . . . . . . . . . . . . . . . 68P02902W36
GSM-206-020 Service Manual: Horizoncompact . . . . . . . . . . . . . . . 68P02902W15
GSM-205-020 Service Manual: Horizonmacro Indoor . . . . . . . . . . . 68P02902W06
GSM-204-020 Service Manual: Horizonmacro Outdoor . . . . . . . . . . 68P02902W12
GSM-207-020 Service Manual: Horizonoffice . . . . . . . . . . . . . . . . . . 68P02902W46
GSM-209-020 Service Manual: Horizonmicro2 Horizoncompact2 . 68P02902W61
GSM-208-020 Service Manual: Horizonmacro 12 Carrier Outdoor 68P02902W66
GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include the
Packet Control Unit (PCU) service manual which becomes part of the BSS for GPRS:
Classification
GPRS-301-020 Service Manual:GPRS Support Nodes (GSN) . . . . . 68P02903W05
GPRS-302-020 Service Manual: Packet Control Unit (PCU) . . . . . . . 68P02903W10
Classification number
The classification number is used to identify the type and level of a manual. For example,
manuals with the classification number GSM-100-2xx contain operating information.
Order number
The Motorola 68P order (catalogue) number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the order (catalogue) number. Motorola
manual sets may also be ordered on CD-ROM.

30th Jun 02 68P02900W21-K 13
GMR-01
GMR amendment GSM-001-103
GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual
using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals
as and when required. A GMR has the same identity as the target manual. Each GMR is
identified by a number in a sequence that starts at 01 for each manual at each issue.
GMRs are issued in the form of loose leaf pages, with a pink instruction sheet on the
front.
GMR procedure
When a GMR is received, remove and replace pages in this manual, as detailed on the
GMR pink instruction sheet.

14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GMR amendment record
GMR amendment record
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the pink instruction sheet that accompanies each GMR and
insert it in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number Incorporated by (signature) Date

01 Incorporated (this GMR) 30th Jun 2002
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

30th Jun 02 68P02900W21-K 15
GMR-01
GMR amendment record GSM-001-103

16 68P02900W21-K 30th Jun 02
GMR-01
Chapter 1
Introduction to planning

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Chapter overview
Chapter overview
Introduction to BSS planning

This chapter provides an overview of this manual and the various elements of a BSS and
the BSS planning methodology. This chapter contains:
S 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.

30th Jun 02 68P02900W21-K 1–1
GMR-01
Manual overview GSM-001-103
Manual overview
Introduction
The manual contains information about planning a GSM network; utilizing a combination
of 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 planning
methodology.
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 and
M-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 location
services.
S Chapter 9: OMC-R planning steps and rules
Provides the planning steps and rules for the OMC-R.
S Chapter 10: Planning exercise
Provides a planning exercise designed to illustrate the use of the rules and
formulae provided in Chapter 3, 4, 5, 6 7 and 8.
S Chapter 11: Paging rate and location area planning
Provides the planning steps and rules for location area planning.
S Chapter 12: Deriving call model parameters from network statistics
Provides the planning steps and rules for deriving call model parameters from
network statistics collected at the OMC-R.

1–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Manual overview
S Chapter 13: Standard BSS and Horizon BTS configurations

Provides diagrams of the logical interconnections of the components in various
standard BSS and Horizon BTS site configurations.
S Chapter 14: M-Cell BTS configurations
Provides diagrams of the logical interconnections of the components in various
M-Cell BTS site configurations.
S Chapter 15: Previous generation BSC planning steps and rules
This chapter (included for reference only) provides the planning steps and rules
for the BSC up to software release GSR3.
S Chapter 16: Planning and equipment descriptions for pre M-Cell BTSs
This chapter (included for reference only) provides the planning steps and rules
for pre M-Cell BTS equipment.

30th Jun 02 68P02900W21-K 1–3
GMR-01
BSS equipment overview GSM-001-103
BSS equipment overview
System architecture
The architecture of the Motorola Base Station System (BSS) is extremely versatile, and
allows many possible configurations for a given system. The BSS is a combination of
digital and RF equipment that communicates with the Mobile Switching Centre (MSC),
the Operations and Maintenance Centre Radio (OMC-R), and the Mobile Stations (MS)
as shown in Figure 1-1.
Figure 1-1 BSS block diagram
OMC-R
A INTERFACE
MSC
LRs
RXCDR BSS
O&M
PCU BSC BSS
ABIS INTERFACE
BTS 1 BTS 5 BTS 8 ... BTS n
BTS 2 BTS 6
BTS 3 BTS 7
BTS 4
AIR INTERFACE
MS MS ... MS MS ...
NOTE: 1. THE OMC-R CAN BE LINKED THROUGH THE RXCDR AND/OR TO THE BSS/BSC DIRECT.
2. THE EXAMPLE OF MULTIPLE MSs CONNECTED TO BTS 4 AND BTS 7, CAN BE ASSUMED
TO BE CONNECTED TO ALL OTHER BTSs SHOWN.

1–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS equipment overview
System components
The BSS can be divided into a Base Station Controller (BSC), and one or more Base
Transceiver 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 of
the traffic and can be located at the BSC or between the BSC and MSC. When the
XCDR/GDP is located at the MSC it reduces the number of communication links to the
BSC. When transcoding is not performed at the BSC, the XCDR is referred to as a
remote transcoder (RXCDR). The RXCDR is part of the BSS but may serve more than
one BSS.
Transceiver units
In the Motorola BTS product line, the radio transmit and receive functions are provided
as listed in Table 1-1:
Table 1-1 Transceiver unit usage

Transceiver unit Where used ...
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 compatible

by switching from TCU to SCU on the front panel, all other
transceiver units are only compatible with the equipment listed.
CTU
In Horizonmacro, the transceiver functions are provided by the CTU. Description and
planning rules for the CTU are provided in Chapter 4 of this manual. Configuration
diagrams are shown in Chapter 12. The receivers can support receive diversity.
DTRX
In Horizonmicro, Horizonmicro2, Horizoncompact and Horizoncompact2 the transceiver
functions are provided by the dual transceiver module (DTRX). System planning is
described in Chapter 2 and configuration diagrams are shown in Chapter 12. The
receivers do not support receive diversity.
TCU/TCU-B
In M-Cell6, M-Cell2 and BTS6, the transceiver functions are provided by the TCU or
TCU-B (not BTS6). Description and planning rules for the TCU/TCU-B are provided in
Chapter 4 of this manual. Configuration diagrams are shown in Chapter 13. The
receivers can support receive diversity.

30th Jun 02 68P02900W21-K 1–5
GMR-01
BSS equipment overview GSM-001-103
TCU-m
In M-Cellmicro, M-Cellcity and M-Cellcity+ the transceiver functions are provided by a
pair of TCU-ms. The receivers do not support receive diversity.
PCU
In M-Cellaccess, the transceiver functions are provided by the PCU. System planning is
described in Chapter 2 and configuration diagrams are shown in Chapter 13. The
receivers can support receive diversity.
NOTE Do not confuse the PCU in M-Cellaccess with the PCU (Packet
Control Unit) hardware that is required for GPRS support.
DRCU/SCU
In BTS4, BTS5, BTS6, TopCell and ExCell, the the transceiver functions are provided by
the DRCU/SCU. Planning rules for the DRCU and SCU are provided in Chapter 14 and
configuration diagrams are shown in Chapter 15. The receivers can support receive
diversity.

1–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS features
BSS features
Features that affect planning

This section provides a description of the software features that might affect the required
equipment, and that should be taken into consideration before planning actual
equipment. Check with the appropriate Motorola sales office regarding software
availability with respect to these features.
S 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 two
uncorrelated receive signals to the transceiver. Each transceiver unit includes two
receivers, which independently process the two received signals and combine the results
to produce an output. This results in improved receiver performance when multipath
propagation is significant and in improved interference protection.
Two Rx antennas are required for each sector. Equivalent overlapping antenna patterns,
and sufficient physical separation between the two antennas are required to obtain the
necessary de-correlation.
Frequency hopping
There are two methods of providing frequency hopping: synthesizer hopping and
baseband hopping. Each method has different hardware requirements.
The main differences are:
S Synthesizer hopping requires the use of wideband (hybrid) combiners for transmit
combining, while baseband hopping does not.
S Baseband hopping requires the use of one transceiver for each allocated
frequency, while synthesizer hopping does not.

30th Jun 02 68P02900W21-K 1–7
GMR-01
BSS features GSM-001-103
Synthesizer hopping
Synthesizer hopping uses the frequency agility of the transceiver to change frequencies
on a timeslot basis for both receive and transmit. The transceiver calculates the next
frequency and re-programs its synthesizer to move to the new frequency. There are three
important points to note when using this method of providing frequency hopping:
S Hybrid combining must be used; cavity combining is not allowed when using
synthesizer hopping.
S The output power available with the use of the hybrid combiners must be
consistent with coverage requirements.
S It is only necessary to provide as many transceivers as required by the traffic. Note

that one transceiver in each sector must be on a fixed frequency to provide the
BCCH carrier.
Baseband hopping
For baseband hopping each transceiver operates on preset frequencies in the transmit
direction. Baseband signals for a particular call are switched to a different transceiver at
each TDM frame in order to achieve frequency hopping. There are three important points
to note when using this method of providing frequency hopping:
S 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 GSM

specifications; this is addressed in the Phase 2 GSM procedures, but at this time
there are no Phase 2 MSs capable of implementing this. Consequently, calls could
be dropped, if a single 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 unilaterally
transmitting data to MSs on a per cell basis. This feature is provided, by a Cell Broadcast
Channel (CBCH). The data originates from either a Cell Broadcast Centre (CBC) or
OMC-R (operator-defined messages may be entered using the appropriate MMI
command). The CBC or OMC-R downloads cell broadcast messages to the BSC,
together with indications of the repetition rate, and the number of broadcasts required per
message. The BSC transmits these updates to the appropriate BTSs, which will then
ensure that the message is transmitted as requested.
Code storage facility processor

Beginning with software release 1.3.0.0, the BSS supports a GPROC acting as the Code
Storage Facility Processor (CSFP). The CSFP allows pre-loading of a new software
release while the BSS is operational. When BTSs are connected to the BSC, a CSFP is
required at the BSC and a second CSFP should be equipped for redundancy as required.
NOTE If GPROC2 is used this feature will not require additional

hardware.

1–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS features
PCU for GPRS upgrade

The PCU hardware provides GPRS functionality, and is considered as part of the BSS
equipment.
GPRS introduced packet data services (from GSR4.1 onwards) and GPRS planning is
fundamentally different from the planning of circuit-switched networks. One of the
fundamental reasons for the difference, is that a GPRS network allows the queueing of
data traffic instead of blocking a call when a circuit is unavailable. Consequently, the use
of Erlang B tables for estimating the number of trunks or timeslots required, is not a valid
planning approach for the GPRS packet data provisioning process.

30th Jun 02 68P02900W21-K 1–9
GMR-01
BSS planning overview GSM-001-103
BSS planning overview
Introduction
A brief overview of the planning process is provided in this section.
Initial information required

The information required before planning can begin can be categorized into three main
areas:
S 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.

1–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS planning overview
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, typically
Erlang 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 and
associated equipment.
S Redundancy level requirements, determined for each item.
S Supply voltage.

30th Jun 02 68P02900W21-K 1–11
GMR-01
BSS planning overview GSM-001-103
Planning methodology
A GSM digital cellular system is usually made up of several BSSs. The planning cycle
begins with defining the BSS cell, followed by the BTS(s), then the BSC(s), and finally
the RXCDR(s).
The text that follows provides a brief checklist of the steps in planning a BSS:
1. Choose the configuration, omni or sectored and the frequency re-use scheme that
satisfies traffic, interference and growth requirements.
2. Plan all BTS sites first:
– Use an appropriate RF planning tool to determine the geographical location
of sites on and the RF parameters of the chosen terrain.
– Determine which equipment affecting features are required at each site. For
example, diversity or frequency hopping.
– Plan the RF equipment portion and cabinets for each BTS site.
– Plan the digital equipment portion for each BTS site.
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, subsequent
hardware implementation.

1–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Acronyms
Acronyms
Acronym list
Table 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

30th Jun 02 68P02900W21-K 1–13
GMR-01
Acronyms GSM-001-103
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
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
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
DYNET Dynamic network
e Erlang
E1 32 channel 2.048 Mbps span line
EFR Enhanced full rate
(E)GSM (Enhanced) global system for mobile communication
E-OTD Enhanced observed time difference
FACCH Fast access control channel

1–14 68P02900W21-K 30th Jun 02
GMR-01
Acronym Meaning
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
HSC Hot swap controller
HSN Hopping sequence number
IADU Integrated antenna distribution unit
IMSI International mobile subscriber identity
INS In service
IP Internet protocol
IPL Initial program load
ISDN Integrated services digital network
ISI Inter symbol interference
ISP Internet service provider

30th Jun 02 68P02900W21-K 1–15
GMR-01
Acronym Meaning
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)
NTP Network time protocol
NVM Non volatile memory
O&M Operations and maintenance
OLM Off line MIB

1–16 68P02900W21-K 30th Jun 02
GMR-01
Acronym Meaning
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
PTCCH/D Packet timing advance control channel / downlink
PTCCH/U Packet timing advance control channel / uplink
PTP Point to point
PVC Permanent virtual circuit

30th Jun 02 68P02900W21-K 1–17
GMR-01
Acronym Meaning
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
STP Shielded twisted pair
SURF Sectorized universal receiver front end
TBF Temporary block flow
TCCH Timing access control channel

1–18 68P02900W21-K 30th Jun 02
GMR-01
Acronym Meaning
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 adaption 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

30th Jun 02 68P02900W21-K 1–19
GMR-01

1–20 68P02900W21-K 30th Jun 02
GMR-01
Chapter 2
Transmission systems

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter provides diagrams of the logical interconnections and descriptions of BSS
interconnections.
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.

30th Jun 02 68P02900W21-K 2–1
GMR-01
BSS interfaces GSM-001-103
BSS interfaces
Introduction
Figure 2-1 and Table 2-1 indicate the type of interface, rate(s) and transmission systems
used to convey information around the various parts of the BSS system.
Figure 2-1 BSS interfaces
OMC-R
X.25
OML (LAPB)
Gb OPTION B
MSC
Air interface Abis interface A interface

MS BTS BSC RXCDR
(LAPDm) RSL (LAPD) MTL (C7), XBL (LAPD)
OML (X.25) SGSN
GDS
Gb OPTION A
Gb OPTION C
PCU
X.25
CBL (LAPB)
CBC
Table 2-1 BSS interfaces

Interface From/To Signalling by ... Rate Using ...
Air MS – BTS RACH, SDCCH, LAPDm
SACCH, FACCH
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 Frame
Relay
GDS PCU – BSC GSL 64 kbits/s LAPD

2–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Interconnecting the BSC and BTSs
Interconnecting the BSC and BTSs
Introduction
Network topology is specified in terms of the path(s) between the BSC and the BTS
sites. A path is determined by which E1 or T1 circuits, and possible intervening BTS sites
are used to provide the connection. Transcoding may be carried out at the BSC or
RXCDR.
Interconnection rules
The following rules must be observed when interconnecting a BSC and BTSs:
S The BSC may share MSI boards between BTSs. When there are two or more E1
or T1 circuits, at least two MSIs are recommended for redundancy.
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, each
requiring 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 circuit
capacity. A carrier unit will require two 64 kbit/s timeslots on a E1 or T1 circuit. In a
redundant connection, each carrier unit requires two 64 kbit/s timeslots on two
different E1 or T1 circuits.
S At the BSC, one E1 or T1 circuit is required to connect to a daisy chain. If the
connection is a closed loop daisy chain, two E1 or T1 circuits are required. To
provide redundancy, the two E1 or T1 circuits should be terminated on different
MSIs.
S In a closed loop daisy chain the primary RSLs for all BTS sites should be routed in
the same direction with the secondary RSLs routed in the opposite direction. The
primary RSL at each BTS site in the daisy chain should always be equipped on the
multiple serial interface link (MMS) equipped in CAGE 15 slot 16 port A. The
secondary RSL at each BTS site should be equipped on the MMS equipped in
either cage 15 slot 16 port B or cage 15 slot 14 port A or cage 14 slot 16 port A.
S Additional bandwidth may be required to support GPRS traffic using CS3/CS4
coding schemes (CS3 and CS4 require GSR5.1 or higher).
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.

30th Jun 02 68P02900W21-K 2–3
GMR-01
Network topology GSM-001-103
Network topology
Introduction
The user can specify what traffic is to use a specific path. Any direct route between any
two adjacent sites in a network may consist of one or more E1 or T1 circuits. Figure 2-2
shows a possible network topology.
Figure 2-2 Possible network topology
BSC
BTS 10 BTS 1 BTS 5
BTS 2 BTS 6
BTS 11 BTS 3 BTS 7 BTS 9
BTS 4 BTS 8
Each BTS site in the network must obey the following maximum restrictions:
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 or
eight BTS(s) in a path, including the terminating BTS for T1 circuit connection.
S One signalling link per Horizonmacro BTS site.
S Four 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. This
is known as a redundant path, and is used to provide voice/data redundancy, that is loop
redundancy. The presence of multiple paths does not imply redundancy.
Each signalling link has a single path. When redundant paths exist, redundant signal links
are required, and the signalling is load shared over these links. In the case of a path
failure, the traffic may be rerouted, but the signalling link(s) go out of service, and the
load is carried on the redundant link(s).

2–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Network topology
Star connection
A star connection is defined by installing E1 or T1 circuits between each BTS site and the
BSC, as shown in Figure 2-3.
Figure 2-3 Star connection
BTS 3
BTS 2 BTS 4
BTS 1
BSC BTS 5
MSC
BTS 7
BTS 9
BTS 8
A star connection may require more MSI cards at the BSC than daisy chaining for the
same number of BTS sites. The star connection will allow for a greater number of carrier
units per BTS site.
An E1 circuit provides for 15 carriers plus one signalling link. A T1 circuit provides for 11
carriers plus 1 or 2 signalling links.

30th Jun 02 68P02900W21-K 2–5
GMR-01
Daisy chain connection

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

2–6 68P02900W21-K 30th Jun 02
GMR-01
Daisy chain planning

The introduction of multiple E1 or T1 circuits and branches increases the complexity of
the network topology. Since the network can have multiple E1 or T1 circuits, branches,
multiple paths over the same E1 or T1 circuit, and closed loop interconnections, each E1
or T1 circuit should be individually planned.
Simple daisy chain

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

Rx Tx Rx Tx
Rx Tx
...
......
...
Tx Rx
Tx Rx Tx Rx
USED IN CLOSED LOOP BTS 3

CONNECTION ONLY BTS 4 BTS X
Rx Tx Rx Tx
The capacity of a closed loop single E1 or T1 circuit daisy chain is the same as that for
an open ended daisy chain. The closed loop daisy chain has redundant signalling links
for each BTS, although they transverse the chain in opposite directions back to the BSC.
Maximum carrier capacity of the chain, with one signal link per BTS site is given by:
31 – b
n+
2
for E1 links
24 – b
n+
2
for 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.

30th Jun 02 68P02900W21-K 2–7
GMR-01
Example
A single E1 circuit daisy chain with three BTSs, the maximum capacity of the chain is
given by:
31 – 3
+ 14 carriers
2
A single T1 circuit daisy chain with three BTSs, the maximum capacity of the chain is is
given by:
24 – 3
+ 10 carriers
2
These carriers can be distributed between the three sites. If the loop is closed, the BSC
has additional signalling links, although the same number of carriers are supported.
Daisy chain with branch BTS site

The addition of a branch BTS site (BTS Y), as shown in Figure 2-6, affects the capacity
of the links between the BSC and the site from which the branch originates as these are
used for the path to the branched site.
Figure 2-6 Daisy chain with branch
Tx Rx Tx Rx
BSC BTS 1 BTS 2

Rx Tx Rx Tx
Rx Tx
Tx Rx
Tx Rx Tx Rx
BTS 3 BTS 4 BTS X

Rx Tx Rx Tx
USED IN CLOSED LOOP

CONNECTION ONLY
Rx
BTS Y
Tx
A branch may have multiple BTS sites on it. A branch may be closed, in which case
there would be redundant signalling links on different E1 or T1 circuits. In a closed loop,
which requires redundant signalling links for each BTS site, with an open branch, the E1
or T1 circuit to the branch needs to carry redundant signalling links.

2–8 68P02900W21-K 30th Jun 02
GMR-01
Aggregate Abis
This is an option designed to allow greater flexibility when network planning. It can also
help reduce leasing costs of E1/T1 links by optimizing the link usage over the greatest
distance between a BSC and BTS.
This is achieved by the introduction of third party multiplexer equipment enabled by
Motorola software. This equipment allows timeslots on one E1/T1 link to be multiplexed
to more than one BTS. Therefore, if the situation arises where several single carrier
BTSs would each require their own dedicated E1/T1 link, greatly under utilizing each link
capacity.
Now, providing the geographical locations of the sites and distances of the E1/T1 links
work out advantageously, it is possible to send all the traffic channels for every site
initially over one E1/T1 link to the third party multiplexer and then distribute them over
much shorter distances to the required sites.
Providing the distance between the BSC and the multiplexer site is sufficiently large, this
should result in significant leasing cost savings over the original configuration. Below are
two diagrams illustrating the before (Figure 2-7) and after (Figure 2-8) scenarios.
Figure 2-7 Typical low capacity BSC/BTS configuration
BSC
5x64 kbit/s TIMESLOTS USED 5x64 kbit/s TIMESLOTS USED

26x64 kbit/s TIMESLOTS UNUSED 26x64 kbit/s TIMESLOTS UNUSED
BTS BTS
TWO CARRIER TWO CARRIER

ONE RSL ONE RSL
5x64 kbit/s TIMESLOTS USED
26x64 kbit/s TIMESLOTS UNUSED
BTS
TWO CARRIER
ONE RSL

30th Jun 02 68P02900W21-K 2–9
GMR-01
Figure 2-8 Example using a switching network
BSC
MORE EFFICIENT USE OF

LONGEST E1/T1 LINK
20x64 kbit/s TIMESLOTS USED
11x64 kbit/s TIMESLOTS UNUSED
TWO CARRIER
ONE RSL
5x64 kbit/s TIMESLOTS USED 10x64 kbit/s TIMESLOTS USED
26x64 kbit/s TIMESLOTS UNUSED E1/T1 21x64 kbit/s TIMESLOTS UNUSED
BTS MULTIPLEXER BTS
TWO CARRIER
ONE RSL 5x64 kbit/s TIMESLOTS USED 5x64 kbit/s TIMESLOTS USED
26x64 kbit/s TIMESLOTS UNUSED 26x64 kbit/s TIMESLOTS UNUSED
BTS BTS
TWO CARRIER TWO CARRIER

ONE RSL ONE RSL
Another advantage of introducing the multiplexer is the improvement in the timeslot

mapping onto the Abis interface.
Currently they are allocated from timeslot 1 upwards for RSLs and timeslot 31
downwards for the RTF traffic channels. Most link providers lease timeslots in contiguous
blocks (that is, no gaps between timeslots). Under the existing timeslot allocation scheme
it often means leasing a whole E1/T1 link for a few timeslots. There is a new algorithm
for allocating timeslots on the Abis interface. This is only used on the links connected
directly to the new aggregate service; the existing algorithm for allocating timeslots is
used on the other links.
Under the new software the timeslots are allocated from timeslot 1 upwards. The RSLs
are allocated first and the RTF timeslots next, with each site being equipped
consecutively, thus allowing contiguous blocks of timeslots to be leased.
It is important that the sites are equipped in the order that they will be presented, also
that the RSLs are equipped first on a per site basis to coincide with the default timeslots
for the software downloads to the BTSs.

2–10 68P02900W21-K 30th Jun 02
GMR-01
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
ORIGINAL
NEW ALGORITHM
BSC ALGORITHM
1 RSL1 6 RSL2
2 1 RSL3
RTF1 7 RTF3 31
3 RTF1 8 RTF3 RTF5
4 ALLOCATION 30 RTF5
RTF2 9 RTF4 29
5 RTF2 10 RTF4 UNAFFECTED RTF6
28 RTF6
11 RSL3 16 RSL4
12 RTF5 17 RTF7
13 RTF5 18 RTF7 ALLOCATION
14 RTF6 19 RTF8 AFFECTED
15 RTF6 20 RTF8 NEW ALGORITHM
1 RSL3 6 RSL4
2 RTF5 7 RTF7
3 RTF5 8 RTF7
4 RTF6 9 RTF8
5 RTF6 10 RTF8
ALLOCATION AFFECTED
E1/T1
BTS 1 MULTIPLEXER BTS 3
1 RSL1 ALLOCATION AFFECTED
2 RTF1
TWO CARRIER 3 NEW
ONE RSL RTF1 ORIGINAL
4 ALGORITHM ALGORITHM
RTF2
5 RTF2 1 RSL2 1 RSL4
2 ALLOCATION
RTF3 ALLOCATION 31 RTF7 UNAFFECTED
NEW 3 RTF3 AFFECTED
ALGORITHM 30 RTF7
4 RTF4 29 RTF8
5 RTF4 28 RTF8
BTS 2 BTS 4
Similar problems can be encountered when equipping redundant RSL devices onto paths
containing aggregate services. Because of the new way of allocating timeslots when
connecting to a aggregate service from timeslot 1 upwards, there is no way of reserving
the default download RSL timeslot. This gives rise to the situation where the default RSL
timeslot has already been allocated to another device, RTF for example.
To avoid this happening, the primary and redundant RSLs can be equipped first (in an
order that results in the correct allocation of default RSL timeslots), or reserve the default
download RSL timeslot so that it may be allocated correctly when the primary or
redundant RSL is equipped.
If it is envisaged to expand the site in future to preserve blocks of contiguous timeslots
on the links, it is possible to reserve the timeslots needed for the expansion so that they
can be made free in the future.

30th Jun 02 68P02900W21-K 2–11
GMR-01
Alarm reporting
This feature has an impact on the alarm reporting for the E1/T1 links. If the link is
connected to a third party switching network and is taken out of service, the BTS will
report the local alarm, but the remote alarm will only go to the third party aggregate
service supporting the E1/T1 link.
There may also be a case where the internal links within the E1/T1 switching network fail,
causing the RSL to go out of service with no link alarms generated by GSM network
entities (BTS, BSC). In these cases it is the responsibility of the third party aggregate
service provider to inform the users of the link outage. The only indication of failure is the
RSL state change to out of service.
Figure 2-10 shows a possible network configuration using several switching networks.
Figure 2-10 Alternative network configuration with E1/T1 switching network
BSC
E1/T1
MULTIPLEXER E1/T1
MULTIPLEXER
BTS BTS
BTS BTS
BTS BTS BTS
BTS
E1/T1
MULTIPLEXER E1/T1
MULTIPLEXER
BTS BTS BTS BTS
Restrictions/limitations
The ability to nail path timeslots along a link containing an E1/T1 switching network is
supported. The user is still able to reserve, nail, and free timeslots.
The maximum number of sites within a path is ten for E1/T1 networks. Even though it is
a pseudo site, the aggregate service is counted as a site in the path. Hence the number
of BTSs that can be present in a path is reduced from ten to nine.
GCLK synchronization functions, but any BTS sites connected downlink from a switching
network will synchronize to it and not the uplink GSM network entity (BTS, BSC).

2–12 68P02900W21-K 30th Jun 02
GMR-01
RTF path fault containment

Each transceiver at a BTS requires a receive/transmit function enabled which tells it
various operating parameters to use. These include the ARFCN, type of carrier, and
primary/secondary path, among others. It is the path that is of concern here. An RTF
may be assigned different paths. The path is the route which the two 64 kbit/s timeslots
assigned to the 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 in
the same cell.
One path is designated the primary, the other the secondary. In the event of the primary
path failing, the RTF chooses the secondary path and the carrier remains in call
processing. At present, if all the paths to one RTF fail, the whole cell is taken out of call
processing, regardless of whether there are other transceivers/RTFs with serviceable
paths in the same cell.
This feature allows the cell to remain in call processing if the failure of all paths to one
RTF occurs, as described in the previous paragraphs. Any call in progress on the failed
path is handed over to the remaining RTFs in the same cell, if there are available
timeslots. If there are not enough available timeslots, the call is released. Also, the
timeslots on the transceiver of the failed path are barred from traffic until the path is
re-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, then
the cell is barred from traffic.
Advantages
By using this feature, and removing any redundant paths that would normally be
equipped to manage path failure, the customer could save on timeslot usage. Figure 2-11
shows the conventional redundant set-up, requiring in this case four extra timeslots to
provide for redundant paths. Figure 2-12 shows the configuration using the new software,
which if one RTF path fails will allow call processing to continue via the other path,
though with reduced capacity. This configuration only requires four timeslots instead of
eight for Figure 2-11. The customer has to weigh up the cost saving advantages of the
new software against the reduced capacity in the event of failure of a RTF path.

30th Jun 02 68P02900W21-K 2–13
GMR-01
Figure 2-11 A configuration with a BTS equipped with two redundant RTFs
BSC
RTF1 EQUIPPED RTF1 EQUIPPED

ON PATH 1 ON PATH 2
(2 TIMESLOTS) (2 TIMESLOTS)
BTS 3 BTS 1

ON PATH 1 ON PATH 2
BTS 2
Figure 2-12 A configuration with a BTS equipped with two non-redundant RTFs
BSC

ON PATH 1 ON PATH 2
BTS 3 BTS 1
BTS 2

2–14 68P02900W21-K 30th Jun 02
GMR-01
16 kbit/s RSL
The 16 kbit/s RSL (introduced at GSR3) reduces the transmission costs between the
BSC 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 the
64 kbit/s RSL and two for the 16 kbit/s traffic channels. The two 64 kbit/s timeslots
dedicated to the traffic channels can accommodate eight traffic channels normally.
In the case of a single carrier site; it was not possible to use all eight traffic channels of
the two 64 kbit/s timeslots. The reason is that, in the case of a single carrier site, the
carrier is the BCCH carrier and the air interface timeslot 0 of the BCCH carrier is
reserved for BCCH information. This information is generated at the BTS not the BSC.
The TSW at the BTS routes the traffic channels from the two specified timeslots on the
Abis interface to the dedicated transceiver for transmission.
Due to this, the traffic channel on the Abis interface corresponding to the timeslot 0 on
the air interface is unused and available to bear signalling traffic. This results in one
16 kbit/s sub-channel unused on the Abis interface – a waste of resources.
With the introduction of the 16 kbit/s RSL, it is possible to place it on this unused
sub-channel because the RSL is not transmitting on the air interface. The advantage is
that it frees up one 64 kbit/s timeslot on the Abis interface, reducing the requirement to
serve a single carrier system to only two 64 kbit/s timeslots. This operates with Horizon
BTSs and InCell BTSs using KSW switching.
Figure 2-13 (fully-equipped RTF) and Figure 2-14 (sub-equipped RTF) show the eight
types of RTF which are possible using the previously described options. They are listed
in 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.

30th Jun 02 68P02900W21-K 2–15
GMR-01
Fully equipped RTF
Figure 2-13 Fully equipped RTF
FULLY EQUIPPED RTF
BCCH NON-BCCH
16 kbit/s 16 kbit/s
BTS only BTS only
NO NO
ASSOCIATED ASSOCIATED
16 kbit/s RSL 16 kbit/s RSL
Configuration 1 2 3 4
Timeslot X
Timeslot Y
KEY 16 kbit/s sub-channel unavailable for use.

16 kbit/s sub-channel used for 16 kbit/s RSL.
16 kbit/s sub-channel available for voice traffic.

2–16 68P02900W21-K 30th Jun 02
GMR-01
Sub-equipped RTF
Figure 2-14 Sub-equipped RTF
SUB-EQUIPPED RTF
BCCH NON-BCCH
16 kbit/s 16 kbit/s
BTS only BTS only
NO NO
Configuration 5 6 7 8
Timeslot X
Timeslot Y
KEY 16 kbit/s sub-channel used for 16 kbit/s RSL.

16 kbit/s sub-channel available for voice traffic.
Planning constraints
The 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 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 a
16 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 a
64 kbit/s E1/T1 timeslot for BSU based sites.
S An associated 16 kbit/s RSL is supported on redundant RTF paths where one
exists on the primary path.

30th Jun 02 68P02900W21-K 2–17
GMR-01
16 kbit/s XBL
The 16 kbit/s XBL (introduced at GSR3) provides a lower cost solution to the customer
by reducing the interconnect costs between an RXCDR and BSC.
This is achieved by reducing the XBL data rate from its current 64 kbit/s to 16 kbit/s. This
frees three 16 kbit/s sub-channels on the E1/T1 64 kbit/s timeslot to enable them to be
used as TCHs. The maximum number of XBLs able to be configured between a single
BSC and RXCDR remains the same as before, at two, with a total number of XBL links to
an RXCDR of nine. There is no restriction on which timeslot an XBL can be configured.
It will be possible to select a rate of 16 kbit/s or 64 kbit/s on an XBL basis, so it would be
possible to have two different rates at the same BSC to RXCDR, although this would not
be considered a typical configuration. As a result of the introduction of the 16 kbit/s RSL
there is no reduction in processing capacity of the BSC or RXCDR.
Figure 2-15 demonstrates XBL utilization.
Figure 2-15 XBL utilization
BSC 1 XBL XBL
BSC 2 XBL XBL
BSC 3 XBL XBL RXCDR
BSC 8 XBL XBL
BSC 9 XBL XBL
MAXIMUM OF TWO XBLs BETWEEN THE BSC AND XCDR OF EITHER 64 kbit/s OR 16 kbit/s
ON THE E1/T1 LINK.
MAXIMUM OF NINE BSCs CONNECTED TO AN RXCDR OR VICE VERSA.

2–18 68P02900W21-K 30th Jun 02
GMR-01
Dynamic allocation of RXCDR to BSC circuits (DARBC)

The dynamic allocation of RXCDR to BSC circuits feature introduces fault management
for call traffic on the BSC to RXCDR interface (referred to as the Ater interface) by
managing the individual 16 kbit/s channels (called Ater channels) on this interface. In
addition, this feature provides for validation of the CIC and Ater channel provisioning
between the BSC and RXCDR to ensure that calls are placed on the correct circuit
between the BSC and the MSC. Without this feature in place, no fault management of
the Ater channels would be possible, and all Ater and CIC information must be manually
verified 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-connect
mode or in the backwards compatibility mode. These modes are managed on a per
AXCDR basis.
Auto-connect mode
This is an operator selectable mode which refers to a BSC in which Ater channels are
allocated and released dynamically as resources are provisioned, unprovisioned or
during handling of fault condition. Auto-connect mode provides the fault tolerance
together with the call processing efficiency of backwards compatibility mode. This is the
recommended 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 Ater
channels and CICs are statically switch connected. This mode does not provide any fault
tolerance and CIC validations, and is intended only to provide an upgrade path. Once
both BSC and RXCDR are upgraded, the use of auto–connect mode is recommended.
NOTE When upgrading the network and the BSC is being upgraded
before the RXCDR, backwards compatibility mode must be used
for the corresponding AXCDR.
Prior to introduction of this feature, all Ater channels were statically assigned and use of
XBL links was not mandatory. From GSR5, should an operator decide to use the
auto-connect, it becomes imperative to equip XBL links on the RXCDR and BSC. If
no XBLs are equipped, and the AXCDR is operating in the auto-connect mode, all CICs
at the BSC associated with that AXCDR will be blocked and no call traffic will go to that
AXCDR.

30th Jun 02 68P02900W21-K 2–19
GMR-01
BTS concentration GSM-001-103
BTS concentration
Introduction
The BTS concentration feature (introduced at GSR4) reduces the number of BTS–BSC
terrestrial backhaul resources that are planned on the E1/T1 link between the BTS and
BSC. This feature is made possible by dynamically allocating terrestrial backhaul
resources 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), for
coverage purposes, than deployed terrestrial backhaul resources. This planning
approach takes advantage of the trunking efficiencies gained by sharing terrestrial
backhaul resources among multiple BTS RTFs. This feature is particularly useful for
in-building systems.
Prior to the introduction of BTS concentration, terrestrial backhaul resources were
statically allocated when RTFs were equipped. This feature preserves the existing
mechanism (static allocation), but allows the operator the choice, on a per BTS site
basis, of whether to use the existing mechanism, or the new dynamic allocation method.
The BTS concentration feature is particularly useful when a large BTS daisy chain
configuration is planned. For a daisy chain network configuration using E1s, there can be
up to ten BTS sites connected together in a serial fashion to a serving BSC. The BTS
concentration feature greatly increases the terrestrial backhaul trunking efficiency in this
large network configuration by allocating E1/T1 16 kbit/s backhaul resources over the
entire daisy chain complex instead of allocating resources on a per BTS site basis.
The BTS concentration feature introduces a new device, referred to as the DYNET
device. The control of the DYNET device enables a network operator to configure the
dynamic allocation of terrestrial backhaul resources from the BSC to BTSs. Additionally,
the process of creating a DYNET will cause automatic E1/T1 PATH assignments to be
made, where a PATH identifies the network topology of BSC to specific BTS connections.
The DYNET is more fully described later in this chapter.

2–20 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BTS concentration
Key terms
Key networking concepts and terms used in the following sections are: network traffic
load expressed in Erlangs, network blocking expressed as grade of service (GOS), and
Network traffic modeling using the Erlang B formula. The concepts and terms that will be
used to describe the BTS Concentration feature are defined 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 of
16 kbit/s backhaul resources. It enables the terrestrial backhaul to be most
efficiently planned by dynamically allocating these resources and requires a
significant software component to be installed on the BSC.
S BTS site
A BTS site may have one or more BTS cells at the same site. The radio signalling
link (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 the
BSC. Additionally, this communication link could be a daisy chain through multiple
BTS sites connected to a serving BSC.
S Common pool
The common pool refers to the pool of resources that are available for unrestricted
assignment on the BTS–BSC E1/T1 link to any cell or site requesting terrestrial
backhaul resources.
S DYamic NETwork (DYNET) device
This is a new device created for the BTS concentration feature. A DYNET device
is used to specify the BTS sites sharing of dynamic resources and how they are
interconnected. When a DYNET is equipped, using the equip command, the PATH
devices for the BTSs that support dynamic allocation are also equipped. See the
DYNET section for more details.
S Dynamic allocation
This is the way the BTS concentration feature allocates terrestrial backhaul
between 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 time
that a resource (channel or link) is busy). One Erlang represents 3600 call seconds
in a one hour time period. This is equivalent to one call holding a circuit for one
hour. Typically a cellular call is held in the range of 120 seconds. A 120 second
hold time would correspond to 33 milli-Erlangs (0.033 Erlangs).
S Erlang B
Erlang B refers to the call model used to determine the number of circuits required
in order to satisfy a given GOS and call load measured in Erlangs. The formula is
based on a call arrival rate with a Poisson probability distribution.

30th Jun 02 68P02900W21-K 2–21
GMR-01
S Grade of Service (GOS)
The GOS is specified in percent. A 1% GOS means that, on average, 1 call out of
100 calls will be blocked, often referred to as a 1% blocking rate. Typically, a 1%
GOS is a desirable terrestrial backhaul design goal.
S PATH devices
This term refers to the E1/T1 connectivity from the BSC to the BTS site or multiple
BTS sites in the case of a BTS daisy chain.
S Radio Signalling Link (RSL)
This is the signalling link between the BSC and BTS. It can be allocated 16 kbit/s
or 64 kbit/s resources over the E1/T1. Each BTS site has at least one 16 kbit/s or
64 kbit/s RSL, and more than one can be allocated per BTS up to a maximum
number specified by each individual BTS product.
S Radio Transmit Function (RTF)
An RTF corresponds to one BTS carrier which can support up to 8 x 16 kbit/s

backhaul resources.
S Reserved allocation
The BTS concentration feature permits the reserved allocation of terrestrial

backhaul resources. For example, in a daisy chain of BTS sites, each cell in a BTS
site can have a reserved number of terrestrial backhaul resources that cannot be
allocated to the other BTS cells or to other BTS sites in the daisy chain.
S Reserve pool
The reserve pool is a term used to describe the number of available terrestrial
backhaul resources that can be used by a specific BTS cell and cannot be
dynamically allocated to another cell.
S Static allocation
Prior to the introduction of the BTS concentration feature, the allocation of

resources over the BTS–BSC E1/T1 link was by static allocation. Static allocation
permits up to 8 (16 with redundancy) terrestrial backhaul resources to be assigned
directly 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 concentration
feature to describe the resources that are available over the BTS–BSC E1/T1 link
or Abis Interface. An E1 link comprises 32 x 64 kbit/s timeslots, of which up to 31
can be allocated to voice traffic and to RSL signaling channels. A T1 can be
allocated with up to 24 x 64 kbit/s timeslots. Each E1/T1 time slot can carry up to
four calls at 16 kbit/s per traffic channel. When terrestrial backhaul is used in the
more general sense, the term additionally refers to the E1/T1 links between the
BSC and RXCDR and to the links between the RXCDR and the MSC.
S Timeslot (TS) 64 kbit/s
A timeslot is one 64 kbit/s channel on an E1 or T1 as provided by terrestrial

backhaul. A timeslot can carry up to four 16 kbit/s traffic channels.

2–22 68P02900W21-K 30th Jun 02
GMR-01
S Traffic CHannel (TCH) 16 kbit/s
The term TCH refers to the BTS radio air interface traffic channel. The bandwidth
required to carry one cellular call over the terrestrial backhaul, in support of the
TCH, is 16 kbit/s.
S Transcoder Rate Adaption Unit (TRAU):
The TRAU corresponds to one transcoding hardware unit per traffic channel. The
TRAU hardware unit processes TRAU frames from the BSS and performs the
bidirectional conversion to PCM frames for transmission to the MSC.
TRAU hardware allocation is not performed by the BSC as part of the dynamic
allocation of terrestrial backhaul resources. Instead, TRAU allocation is performed
when the MSC allocates a link from the MSC to the RXCDR, then to the BSC for a
specific call.
DYNET
DYNET description
To support the functionality of this feature, the DYNET device has been added. A DYNET
device is used to specify the BTSs sharing dynamic resources and how they are
interconnected. This device exists as a construct to specify a BTS network and does not
exist as a managed device. A DYNET may be equipped or unequipped, but may not be
locked, unlocked, or shut down. If third party timeslot multiplexer sites, or marker sites,
are used, they may be included in the definition of a DYNET.
All DYNETs that share the same first identifier must have exactly the same BTSs, or
marker sites, in the same order. These DYNETs must also have different links used by
the BTSs that use dynamic allocation within a BTS network. These limitations allow
multiple link BTS networks to be defined for sharing purposes, whilst limiting the
configuration to simplify sharing.
Equipping DYNETs and PATHs

When a DYNET is equipped, using the equip command, the PATH devices for the BTSs
that support dynamic allocation are also equipped. PATH devices are not automatically
equipped for BTSs that do not support dynamic allocation. A PATH equipped for a non
closed loop daisy chain has a second identifier equal to the second identifier of the
DYNET multiplied by two. In the case of a closed loop daisy chain, an additional PATH
device is equipped automatically. This has a second identifier that is one greater than the
second identifier of the first automatically equipped PATH device.
NOTE The indentifiers of the PATHS automatically equipped when a

DYNET is equipped are not allowed to be used when equipping
the PATH device.
The amount of resources reserved for dynamic allocation is set to zero timeslots when
the DYNET is initially equipped.
Equipping RSLs
RSLs for BTS sites that support dynamic allocation must be equipped to the
automatically equipped PATHs associated with the DYNET.

30th Jun 02 68P02900W21-K 2–23
GMR-01
Blocking considerations
Dynamic allocation allows greater RF channel capacity to be equipped (RTFs) than there
are terrestrial backhaul resources, whether at a BTS site, or within a BTS dynamic
network. This allows RTF equipage for coverage purposes rather than for network
capacity purposes. Additionally, the dynamic allocation method allows terrestrial backhaul
resource capacity to move dynamically between radio units in the same network based
upon traffic considerations. The system planner needs to be aware that if enough users
try to gain access to a system planned with many more RTFs than terrestrial backhaul
resources, some of the call attempts will be blocked because of the limited number of
terrestrial backhaul resources.
Blocking control
The BTS concentration feature provides a facility to reserve terrestrial backhaul
resources on a per BTS cell basis along with the dynamic allocation of these resources.
This reservation capability can be used to ensure that any given BTS cell has some
E1/T1 resources available independent of the other BTS cells or other BTS site traffic
loads, thereby providing a guaranteed method of blocking control. However, the best use
of terrestrial backhaul resources is obtained by statistically planning the network, using
the dynamic allocation method to achieve a low blocking probability (a good GOS).
Reserved allocation algorithm

The feature allows reserved resources to be allocated to specific cells. In configuring a
network with BTS concentration, a pool of terrestrial backhaul resources must be set
aside for dynamically allocating to the relevant cells/BTS sites. This pool is called the
dynamic pool in the following discussion. In addition, the feature allows each cell to
specify an amount of reserved resources, which are taken (dynamically allocated) from
the dynamic pool. Once a number of resources are reserved for a cell, these resources
are allocated specifically to the cell and, therefore, are not available for sharing.
To facilitate this discussion from the planning perspective, imagine that there is a
common pool that holds the remaining resources in the dynamic pool after resources
are reserved for specific cells. Figure 2-16 shows what the dynamic pool of terrestrial
backhaul resources consists of from the planning perspective: a common pool and n
reserved pools, one for each BTS site.
Each reserved pool consists of the resources associated with a 16 kbit/s RSL timeslot as
well as any additional resources that are specifically reserved on a per cell basis. The
16 kbit/s RSL timeslot-associated resources are shared among the cells at the BTS site,
but cannot be shared with other BTS sites. The reserved pool of an individual BTS site
can be set to zero. For each 16 kbit/s RSL, there will always be three resources available
for reserved allocation among cells at the same site. If there are two 16 kbit/s RSL, six
reserved resources are available, and so on. However, 16 kbit/s RSLs equipped for
redundancy do not provide any reserved resources. For example, if there are six
16 kbit/s RSLs and three of which are for redundancy, a total of nine RSL associated
resources are available to be included in the reserved pool.
When a new call arrives to a cell, the BSC always first allocates a resource from the
reserved pool of the corresponding BTS site. Specifically, it will first attempt to allocate an
RSL-associated resource. If none is available, it allocates a resource from the additional
resources specifically reserved for the cell. If all reserved resources are depleted, the
BSC then allocates a resource from the common pool. If again no resource is available in
the common pool, the call is blocked.
If the BTS site is assigned a 64 kbit/s RSL instead of a 16 kbit/s RSL, then there are no
RSL timeslot-associated resources available for dynamic allocation.

2–24 68P02900W21-K 30th Jun 02
GMR-01
Figure 2-16 A dynamic pool of terrestrial backhaul resources
COMMON POOL
BTS site n Cell 1 additional
reserved resources
BTS site 1 RESERVED POOL

reserved resources
BTS site 2 RESERVED POOL

reserved resources
RSL–associated reserved
resources (Quantity = 0,
BTS site n RESERVED POOL 3, 6..)
Emergency call handling

With BTS concentration, emergency calls take precedence over non-emergency calls in
the allocation of terrestrial backhaul resources. The emergency calls precedence in
backhaul resource allocation is independent of whether Emergency Call Pre-emption
(ECP) is on or off. If no terrestrial backhaul resources are available when an emergency
call requests a resource, the oldest existing non-emergency call is terminated in order to
provide the needed resource. In addition, emergency calls take precedence over
reserved resources allocated to specific cells. Emergency calls use whatever free
terrestrial backhaul resource becomes available first. The BSC will pre-empt
non-emergency calls in the same cell. The BSC next pre-empts non-emergency calls at
the site. Finally, the BSC will terminate non-emergency calls from other sites within the
same DYNET. If all available terrestrial backhaul resources are in use by emergency calls
or if no terrestrial backhaul resources are available, then the new emergency call is
blocked.
Radio signalling link (RSL) planning

When a BTS daisy chain is configured during the configuration management phase, the
operator has to equip each BTS site in the daisy chain at least one 64 kbit/s timeslot for
RSL use. This is necessary so that when a BTS site is initialized it can communicate with
the BSC at 64 kbit/s. After the initialization process concludes, the BTS site can then be
allocated this 64 kbit/s E1/T1 timeslot as one 16 kbit/s RSL and three 16 kbit/s terrestrial
backhaul resources. These three 16 kbit/s resources are always considered part of a
reserved resources on a per site basis and can be used by any cell within a site. These
three RSL associated resources may not be shared from one BTS site to another. A site
always allocates RSL associated 16 kbit/s resources before allocating other reserved
resources or before requesting allocation from the common pool of resources.
Alternatively, the BTS site can continue to use this 64 kbit/s E1/T1 timeslot as one
64 kbit/s RSL. When the RSL is used as a 64 kbit/s signalling link, there are no RSL
associated resources to be used as reserved resources at the site.

30th Jun 02 68P02900W21-K 2–25
GMR-01
Network topologies
BTS concentration does not support all possible network topologies. Dynamic allocation
is limited to spoke, daisy chain, and closed loop daisy chain network configurations.
Figure 2-17, Figure 2-18 and Figure 2-19 illustrate the network configurations to which
these 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

2–26 68P02900W21-K 30th Jun 02
GMR-01
Links between BTSs

Even with dynamic allocation, greater bandwidth than that provided by a single link may
be required. To provide this, networks following the configurations shown in Figure 2-20,
Figure 2-21 and Figure 2-22 may have one to three links between each BTS–BSC or
BTS–BTS pair in the configuration. The same number of links must be specified between
each 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 the
BTSs that use dynamic allocation. This capacity forms the pool from which terrestrial
backhaul resources are allocated.

30th Jun 02 68P02900W21-K 2–27
GMR-01
Third party multiplexer equipment

This feature supports the use of third party multiplexer equipment within a network
configuration. Such equipment defines a terrestrial network outside of the knowledge of
the BSS. To the BSS, this terrestrial network appears as a timeslot multiplexer site (also
known as a marker site) within the BSS configuration.
Figure 2-23 illustrates the use of third party multiplexer equipment in a closed loop
configuration.
Figure 2-23 Closed loop daisy chain configuration with third party multiplexer
BSC
THIRD PARTY THIRD PARTY

MULTIPLEXER MULTIPLEXER
EQUIPMENT EQUIPMENT
BTS 1 BTS 2 BTS 3
Nailed paths
It may be required to declare additional paths to a BTS that uses dynamic allocation for
nail connection purposes. This feature supports this functionality.
Figure 2-24 shows a closed loop daisy chain with an additional path (shown as a dashed
line) to BTS 2. No BSS managed resources can be placed on this additional path, it
exists solely as a convenience for defining nailed connections.
Figure 2-24 Extra path definition for nailed connections
BSC
BTS 1 BTS 2 BTS 3
Additional path definition

2–28 68P02900W21-K 30th Jun 02
GMR-01

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

30th Jun 02 68P02900W21-K 2–29
GMR-01
Allocating and freeing terrestrial backhaul resources

This feature attempts to minimize the BTS interaction needed to allocate or free a
terrestrial backhaul resource. The terrestrial backhaul resources are initially a set of
nailed connections throughout a BTS network (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. A
connection to the TCH is made in place of the nailed connection. When the resource is
freed, the BTS re-establishes the nailed connection. No change in connections is
required at any other BTS in the BTS network.
Figure 2-26 shows a resource allocated to BTS 2. BTS 2 connects the resource to the
TCH using one of the two possible paths to the BSC. BTS 2 changes the connection if
the path being used fails during the call. BTS 2 connects the unused path to the Abis idle
tone.
Figure 2-26 Terrestrial backhaul resource connections during a call
BSC
BTS 1 BTS 2 BTS 3

2–30 68P02900W21-K 30th Jun 02
GMR-01
Redundancy
This feature does not support the use of closed loop daisy chains for additional capacity
when all links are available. This feature treats the closed loop nature of the closed loop
daisy chain as existing for purposes of redundancy. Such a design ensures that no calls
are dropped when a link becomes unavailable in a closed loop configuration. This design
also simplifies the tracking of terrestrial backhaul resources.
For the purposes of this feature, the configuration shown in Figure 2-27 is considered a
closed loop daisy chain configuration.
Figure 2-27 Using redundancy for extra capacity before failure
Call 2
BSC
Call 1
BTS 1 BTS 2 BTS 3
The closed loop daisy chain has the potential to use the same resource in both parts of
the loop. For example, in Figure 2-28, both BTS 1 and BTS 3 could be using the same
resource. BTS 1 could use the resource on the link between the BSC and BTS 1. BTS 3
could use the resource on the link between the BSC and BTS 3. If either link fails, one of
the calls is no longer able to use the resource.
Figure 2-28 Using redundancy for extra capacity after failure
Failed link
BSC
Call 1
BTS 1 BTS 2 BTS 3

30th Jun 02 68P02900W21-K 2–31
GMR-01
Performance issues
The use of satellites to carry links introduces an additional 600 millisecond one way delay
to messages sent on the links. Dynamic allocation requires a BTS to BSC request and a
BSC to BTS response. These messages incur a 1.2 second delay beyond the normal
transmit and queuing delay times. These delay times affect call setup and handover
delay times, especially if retransmission of the request/reply scenario is necessary due to
message loss.
This feature addresses this problem by adding an operator specified parameter that
provides the retry time for dynamic allocation requests. For non-satellite systems, the
retry time should be set to its minimum value. For satellite systems, the retry should be
set to 1.2 seconds plus the minimum retry value. The minimum retry time chosen is 150
milliseconds to account for transmit and queuing delay times (for 16 kbit/s links, a longer
retry time is recommended to avoid excessive retries).
Configuration and compatibility issues

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

2–32 68P02900W21-K 30th Jun 02
GMR-01
Recommended BTS concentration planning guidelines

This section recommends some planning guidelines for planning the BTS concentration
feature and discusses some uses for the reserved allocation algorithm of the feature.
Applications of the guidelines are illustrated by the examples in the next section.
The BTS concentration feature allows terrestrial backhaul resources to be shared among
multiple BTS sites and cells (as if the resources are allocated to a common resource pool
for sharing). In addition, a number of resources can be optionally reserved for specific
BTS cells. It is recommended that network planning favours sharing resources and that
the reserved allocation is used more sparingly, unless reserved resources are available
by default due to the use of 16 kbit/s RSL (see the Radio Signalling Link Planning
section in this chapter). This strategy allows more efficient use of the terrestrial backhaul
resources.
Guideline 1
For a common pool of terrestrial backhaul resources that is to be shared among a
number of cells with different GOSs, enough resources should be allocated to meet the
most stringent GOS among all relevant cells.
This guideline addresses the case when a daisy chain is planned and not all of the BTSs
in the daisy chain need to have the same GOS. For example, in a daisy chain of three
BTS sites the planning objective may be to plan BTS 1 with a 1% GOS, BTS 2 with a 2%
GOS, and BTS 3 with a 1% GOS.
However, when the BTS concentration feature allows terrestrial backhaul resources to be
shared among these three BTS sites, only one GOS may be used for the purposes of
planning the resources. Therefore, Guideline 1 recommends that the best GOS needed
in the daisy chain, that is 1% over 2%, be specified when planning.
Guideline 1 is used in the first example in the following section.
Guideline 2
Due to trunking efficiency, resources are more efficiently utilized if allocated to the
common pool than if reserved for individual cells. Therefore, share the resources among
cells by putting as many of them in the common pool as possible.
The exception to this guideline is when reserved resources are available by default;
those 16 kbit/s circuits that are associated with the same timeslot (on E1 or T1) with the
16 kbit/s RSL/s. In this case, follow Guideline 3 to estimate the overflow traffic from the
default reserved resources and then to determine the required number of resources in
the common pool for meeting the most stringent GOS.
Reserved allocation is intended only as a safeguard mechanism, as implemented in the
BTS concentration feature. Therefore, Guideline 2 recommends that the dynamic
allocation from the common pool be used almost exclusively in order to minimize the
required terrestrial backhaul resources.

30th Jun 02 68P02900W21-K 2–33
GMR-01
Guideline 3
If resources are reserved for specific cells (either by default or by design), the traffic
overflowed from the reserved resources are handled by the resources in the common
pool. The size of the common pool for meeting a certain GOS can be determined using
the following steps:
1. Use the Erlang B model to determine the blocking probability of the reserved
resources, given the offered traffic load at each cell.
2. The traffic overflowed from reserved resources is simply the product of the
expected 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 be
in the common pool, in order to handle the total overflow traffic at the most
stringent GOS requirement among all cells (according to Guideline 1).
Although the call arrival process at the resources might not be Poisson, the use of Erlang
B model in steps 1 and 4 are reasonable approximations and has been verified in
simulations.
The application of these steps is illustrated in examples 1 and 2 in the Examples section
of this chapter.
Uses of reserved allocation algorithm

The following are a few possible applications of the reserved allocation algorithm, which
allows the operators to reserve resources for specific BTS cells:
S If there is insufficient knowledge of the traffic load on the individual BTS sites of a
recently deployed network, resources may be allocated to reserved pools until
some traffic statistics can be accumulated.
S As a transition strategy for moving from the static allocation planning method to the
dynamic allocation of terrestrial backhaul resources out of a common resource
pool, the BTS concentration feature can be added to an existing network and then
planned by allocating resources to only the reserved pools resulting in no effective
change in the planned terrestrial backhaul resources. A follow-up planning process
can later be taken to take advantage of dynamic allocation of terrestrial backhaul
resources out of a common resource pool.
S Suppose in an existing system with BTS concentration, better GOSs are deemed
necessary for some specific and important cells, but for whatever reason it is not
feasible to immediately deploy more terrestrial backhaul resources to the common
pool to achieve the required GOSs.
A possible strategy might be to re-allocate some resources from the common pool
to the reserved pools of the important cells to improve their GOSs. However, as a
trade-off, reducing the size of the common pool will result in worst GOS for the
other cells that rely on the common pool. Nonetheless, the more extensive use of
the reserved pool could be considered a transition strategy until more terrestrial
backhaul resources become available.

2–34 68P02900W21-K 30th Jun 02
GMR-01
Examples
The following examples provide a better understanding for how the guidelines in the
previous section might be applied when planning a network with the BTS concentration
feature.
The first two examples, Examples 1 and 2, demonstrate the trunking efficiency gained
by the BTS concentration feature as well as the use of Guidelines 1, 2, and 3.
Additionally, Guideline 2 is applied by limiting the use of reserved facilities to only those
reserved facilities that are planned as part of the RSL 64 kbit/s timeslot.
The third example, Example 3, demonstrates the case when a combination of reserved
resources and call loading causes blocking to occur at a particular cell, even though
there is still some terrestrial backhaul resource available.
All examples are worked using the Erlang B formula/model.

30th Jun 02 68P02900W21-K 2–35
GMR-01
Example 1
The number of required 16 kbit/s terrestrial backhaul resources between the BSC and
BTS or daisy chain of BTSs depends on the amount of traffic (in Erlangs) expected at
each BTS cell/site and the blocking probability for the resources. (A new call is blocked
when all resources have been allocated to other on-going calls.) This example illustrates
how planning can be carried out. The DYNET in Figure 2-28 is used in the examples and
each BTS site is assumed to have only one cell. Suppose 3 Erlangs of traffic is expected
to come through the cell in BTS 1, 2 Erlangs through BTS 2, and 5 Erlangs through
BTS 3.
NOTE It is important not to confuse the blocking at the terrestrial

backhaul resources with the blocking at the channels over the air
(TCHs) and the blocking at the links between a MSC and a BSC.
If choosing to share the pool of terrestrial backhaul resources freely among all BTSs, and
to allow an 1% blocking probability for these resources, a total of 18 resources are
needed to handle the 10 Erlangs of expected traffic, according to Erlang B formula.
However, to reserve some resources for each BTS site to provide the required blocking
probability, calculate the required number of resources for each BTS site. Assume that
the desired blocking probabilities for the terrestrial backhaul resources are 1%, 2% and
1% for BTS 1, BTS 2 and BTS 3, respectively. Again, using the Erlang B formula,
reserve eight resources to handle the 3 Erlangs of expected traffic through BTS 1 with
1% blocking. Also reserve six resources to handle the 2 Erlangs through BTS 2 at 2%
blocking. Finally, 11 resources are needed at BTS 3 to handle the 5 Erlangs at 1%.
Therefore, 25 resources in total are needed.
Table 2-3 summarizes these key results.
Table 2-3 Summary of required resources

BTS Expected traffic Blocking Required number
(Erlangs) probability (GOS) of 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 expected traffic refers to the amount of traffic arriving at the
backhaul resources. Since the limited number of TCHs gives rise
to another level of blocking (GOS), the traffic expected at the
backhaul resources is in general smaller than the traffic
generated by the subscribers. For example, with 1% blocking at
the TCHs, on average only 99% of the traffic make it to the
backhaul resources. Therefore, the expected or offered traffic at
the backhaul resources is the product of the expected traffic from
the subscribers and (1 – blocking probability).

2–36 68P02900W21-K 30th Jun 02
GMR-01
Note that when the 100% reserved planning approach is used, more resources (25
instead of 18) are required and, in addition, BTS 2 is planned at a higher blocking (a
worse GOS). This example demonstrates the power of trunking efficiency and the reason
why allocation to the common pool should be favoured over allocation to the reserved
pool when planning terrestrial backhaul resources for individual BTS sites or cells.
Reserving terrestrial backhaul resources for individual cells, however, does isolate the
cell from the statistical traffic fluctuation of other cells. When other cells experience
higher call arrivals than average, a cell with its own n reserved terrestrial backhaul
resources will never be in a situation where all its calls are blocked. The cell is
guaranteed that it has at least n ongoing calls before a new call is blocked. The tradeoff,
however, is that a greater number of terrestrial backhaul resources are necessary.
As described in the Radio Signalling Link Planning section in this chapter, some
reserved resources may exist by default if 16 kbit/s RSLs are used at the BTS site. The
16 kbit/s backhaul resources associated with the same timeslot on the E1/T1 as the
16 kbit/s RSL are considered reserved resources for all cells in the BTS site. Suppose
BTS 1 and BTS 2 in this example both use one 16 kbit/s RSL and, therefore, each has
three backhaul resources available by default. Follow Guideline 3 to determine the
number of resources needed in this situation:
1. For BTS 1, given that it has three reserved resources and 3 Erlangs of offered
traffic, the calculated blocking probability for the resources is 0.35. Similarly, for
BTS 2, three reserved resources handling 2 Erlangs gives a blocking probability of
0.21.
2. The traffic overflowed from the reserved resources is 3 x 0.35 = 1.04 Erlangs for
BTS 1 and is 2 x 0.21 = 0.42 Erlangs for BTS 2.
3. The total traffic to be handled by the common pool is, therefore, the sum of the
overflow traffic from BTS 1 and BTS 2 and the 5 Erlangs from BTS 3. The sum
turns out to be 6.46 Erlangs.
4. Using the Erlang B model, the calculated common pool needs to have 13 backhaul
resources in order to meet the 1% GOS.
As a result, a total of 19 resources are needed in this case. Although this approach
requires one more resource than the 100% common allocation approach, six of the
resources are available by default. Only 13 additional resources are really needed.
In summary, it has been demonstrated that the 100% reserved approach resulted in less
efficient use of resources and, therefore, required the most number of resources to meet
the design requirements. The 100% common approach resulted in the most efficient
utilization of resources. However, if reserved resources are readily available, using the
planning approach given in Guideline 3 can make use of them and reduce the number of
additional resources needed to be provisioned (see Table 2-4).
Table 2-4 Summary of common pool planning when BTS 1 and 2 have reserved
resources
BTS Expected Number of Blocking Overflowed traffic
traffic reserved probability from reserved
(Erlangs) resources for 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.

30th Jun 02 68P02900W21-K 2–37
GMR-01
Example 2
As Example 2 demonstrates, the trunking efficiency gain by the BTS concentration

feature can be rather significant. To show the advantage in a large system, this example
looks into the planning of BTS concentration for a daisy chain of 10 single cell BTS sites.
Table 2-5 summarizes the expected amount of traffic at the backhaul resources and the
GOS requirement associated with each cell.
Table 2-5 Summary of traffic and GOS requirements

BTS Expected traffic Blocking Required number
(Erlangs) probability (GOS) of 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 planning
approaches (the rightmost column). The total traffic load of the 10 BTS sites is
290 Erlangs. If each BTS resource allocation is planned as in the static allocation or
100% reserved methods (resources are actually reserved for the cell in the
corresponding BTS site, since they are reserved on a per cell basis), the resources that
need to be planned over the terrestrial backhaul are 400. However, if the resource
allocation is performed over all 10 BTS sites, the number of required terrestrial backhaul
resources drops to 314, a saving of 86 resources.
The saving of 86 resources is significant because, without it, the daisy chain would have
required 400 resources (using the 100% reserved approach) and would not be able to fit
into three E1 links, the most a DYNET can have. Note that three E1 links together can
provide only 372 (= 3 x 31 x 4) 16 kbit/s channels, and, inevitably, some of which will be
allocated for 16 and 64 kbit/s RSLs. The 100% common approach of planning BTS
concentration reduces the number of required resources and makes it possible to offer
1% blocking to the entire daisy chain with three E1 links.
To expand this example further, assume that each BTS site has some default reserved
backhaul resources ranging from 1 to 3 (see Table 2-3). Following Guideline 3, the
calculation in Table 2-6 shows that about a total of 272 Erlangs of traffic will be
overflowed to the common pool. Therefore, the common pool needs 295 additional
resources in order to provide an 1% GOS, making a total of 315 backhaul resources in
this scenario.

2–38 68P02900W21-K 30th Jun 02
GMR-01
Table 2-6 Summary of common pool planning when BTSs have reserved resources
BTS Expected Number of Blocking Overflowed traffic
traffic reserved probability from reserved
(Erlangs) resources for 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.

30th Jun 02 68P02900W21-K 2–39
GMR-01
Example 3
This example uses a call blocking situation in a three cell BTS site to illustrate the
operation of BTS concentration. First, the assumptions about the configuration and the
state of the three cell BTS site:
S There are 24 terrestrial backhaul resources (that is six timeslots) in the dynamic
pool, 12 of which are in the common pool for assignment to any of the three cells
and the other 12 are reserved as illustrated in Table 2-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 1
reserved pool. Cell 1 cannot take any more new calls without getting resource
allocation from the common pool.
S Cell 2 has 17 calls in progress, five of which are counted against cell 2 reserved
pool and 12 were counted against the common pool. As a result, the common pool
is depleted.
S Cell 3 has three calls in progress, and all three calls are counted against cell 3
reserved pool. Cell 3 has the reserved pool capacity to take one more call before
needing resources from the common pool.
Suppose a new call arrives to cell 1. Since resources in both cell 1 reserved pool and the
common pool are in use, the new call attempt will be blocked. This blocking occurs even
though there is one available resource in the dynamic pool. This remaining resource can
only be allocated to cell 3 since it has not used up its reserved pool (see Table 2-7).
Table 2-7 Blocking activity

BTS New call Calls in Reserved pool Resources used out
attempt progress resources of common pool
1 X 3 3 0
2 17 5 12
3 3 4 0

2–40 68P02900W21-K 30th Jun 02
GMR-01
BTS concentration resource optimization for handovers (BCROH)

The BCROH (introduced at GSR5) optimises the terrestrial backhaul between a BSC and
BTS during handovers when BTS concentration is applied. Previously when a handover
occurred, a new circuit for the destination radio channel was always allocated between
the BSC and the BTS. The BCROH however, means that if the source and destination
BTS in a handover are the same then a new circuit is not allocated and the existing
circuit is re-used for the radio destination channel.
BCROH description
For the BCROH to operate, BTS concentration (dynamic allocation of BSC to BTS
circuits) must be employed. It can, therefore, only be used in conjunction with the BTS
equipment that supports BTS concentration.
This reduces the number of resources, (that is, 16 kbit/s backhaul) required when intra
cell handovers or inter cell handovers (within the same site) occur and are controlled by
the BSC. This means that in these handover scenarios, the switch connections for the
voice traffic from the radio channel to the MSC are no longer made at the BSC during the
handover. The BTS to MSC path remains constant and the BTS must simply move the
switch connection of the Abis circuit from the source radio channel to the destination
radio channel.
Figure 2-29 illustrates BSC controlled intra cell handover (cell A to cell A )with BTS
concentration and BCROH enabled.
Figure 2-29 BSC controlled intra cell handover
BSC
In this case the dynamically assigned channel
between BTS and BSC is re-used for the
destination path. The BTS moves the Abis
connection from the source radio channel to the
destination radio channel.
BTS
Cell A
Radio Channel Radio Channel

A B
Mobile is handed over to a new frequency

30th Jun 02 68P02900W21-K 2–41
GMR-01
Figure 2-30 illustrates BSC controlled inter cell handover (cell A to cell B) with BTS
concentration and BCROH enabled.
Figure 2-30 BSC controlled inter cell handover
BSC
In this case the dynamically assigned
channel between BTS and BSC is re-used
for the destination path. The BTS moves the
Abis connection from the source radio
channel to the destination radio channel.
BTS
Cell A Cell B
BCROH cannot be applied when:

S If the handover (H/O) is controlled by the MSC, then the BSC BTS link cannot
re-use the same resource because a new signalling connection control part SCCP
connection is made. Even if the H/O is intra cell (cell A to cell A) or inter cell (cell A
to cell B) within the same site the resource cannot be reused (when H/O is MSC
controlled 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 (link
between a remote BSC and BTS) channel.
NOTE By making the switch connection at the BTS, the connection is

made sooner than a connection made at the BSC, therefore
reducing the audio hole.
The database parameter override_intra_bss_pre_transfer indicates whether the

connection is made in two steps or not.

2–42 68P02900W21-K 30th Jun 02
GMR-01
Method 1
NOTE This is when the override_intra_bss_pre_transfer
parameter is enabled.
When the destination channel receives HO detect, the BTS connects the existing
Abis circuit to the new destination channel. The connection between the Abis
circuit and the source channel is broken, they are now disconnected (see
Figure 2-31).
Figure 2-31 Method 1 (override_intra_bss_pre_transfer is enabled)
Abis Abis
Destination channel
receives HO detect
Source Destination Source Destination

Channel Channel Channel Channel

30th Jun 02 68P02900W21-K 2–43
GMR-01
Method 2
NOTE This is when the override_intra_bss_pre_transfer
parameter is disabled.
S A two step process. When a backing resource is requested for a new channel, the
downlink Abis channel is connected to a destination channel. Then when the
destination channel receives HO detect, the BTS connects the uplink Abis channel
to the new destination channel and the Abis circuit and source channel are
disconnected (see Figure 2-32).
Figure 2-32 Method 2 (override_intra_bss_pre_transfer is disabled)
STEP 1
Abis Abis
Backing resource is
requested for new
BTS channel BTS
Source Destination Source Destination

Channel Channel Channel Channel
STEP 2
Abis
Destination channel
receives HO detect
BTS
Source Destination
Channel Channel

2–44 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Managed HDSL on micro BTS
Managed HDSL on micro BTS
Introduction
Managed HDSL brings the benefits of full OMC-R management to those products that
support integrated HDSL technology. Specifically, it allows remote configuration, status,
control, and quality of service information to be handled by the OMC-R. External HDSL
modems configured as slave devices may also be managed by the same mechanism as
long as they are connected to an integrated master HDSL port.
This enables such an HDSL link to be managed entirely from the OMC-R. Following
introduction of this feature, the initial basic version of the product will no longer be
supported.
NOTE Horizonmicro2 microcell BTSs (and Horizoncompact2

macrocell BTSs) shipped after 31st December 2001 are
not fitted with an internal HDSL modem. A suitable
external HDSL modem must be used if a HDSL link to the
BSC is required for these BTSs.
The local Motorola office can provide assistance prior to
purchasing a HDSL modem for this purpose.

30th Jun 02 68P02900W21-K 2–45
GMR-01
Managed HDSL on micro BTS GSM-001-103
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 be
used 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 they
are 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 HDSL
applications. The following cable types should be avoided:
S Twisted quad cable is unsuitable for use in HDSL applications and must not be
used.
S Drop wire that consists of two parallel conductors with supporting steel cable. This
will work with HDSL but because it is not twisted, it provides little immunity from
noise, and is therefore not recommended.
S Information cable is typically of non-twisted, multicore construction, for example
ribbon cable. Its use is not recommended.

2–46 68P02900W21-K 30th Jun 02
GMR-01
HDSL cable installation

If cabling does not exist between two end sites, guidelines follow for the installation of
cable, that must meet the selection guidelines given above:
S The conductor pair(s) should be connected point-to-point only, not point to
multipoint.
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 SELV
voltage levels).
S The isolation between tip and earth should be greater than 1 Mohm (at SELV
voltage levels).
S The isolation between ring and earth should be greater than 1 Mohm (at SELV
voltage levels).
HDSL range
HDSL range is affected by many factors which should be taken into account when
planning the system.
S Picocell systems should have distances of less than 1 km due to the link quality
requirements of these systems.
S Microcell systems can have longer distances, typically 2 km or so, because of their
different 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 voice
traffic.
NOTE However, standard E1 traffic will affect (and be affected by)

HDSL systems running in the same cable binder, if unshielded
from each other.

30th Jun 02 68P02900W21-K 2–47
GMR-01
General HDSL guidelines

Conversion of E1 to HDSL at a site away from the BSC requires either an external
modem or a microsite. It may be better to utilize the microsite to do this conversion, if
possible (see Figure 2-33).
Figure 2-33 Conversion of E1 to HDSL links by modem and microsite
E1 LINK HDSL
SLAVE M
EXTERNAL
MODEM Horizonmicro2
E1 LINK E1 LINK HDSL HDSL

SLAVE M S M S
BSC
EXTERNAL
Horizonmicro2 MODEM
Horizonmicro2 Horizonmicro2
E1 LINK
BTS HDSL
E1 LINK HDSL HDSL

S M S M M
Horizonmacro Horizonmicro2 Horizonmicro2 Horizonmicro2
M = MASTER S = SLAVE
Microcell BTSs have a maximum of two 2.048 Mbit/s links. If the HDSL equipped version
is purchased (not available for Horizonmicro2 after December 2001), the links are
automatically configured as either E1 or HDSL via a combination of database settings
and auto-detection mechanisms. The setting of master/slave defaults can be changed by
database settings for those scenarios, such as a closed loop daisy chain, where the
defaults are not appropriate.

2–48 68P02900W21-K 30th Jun 02
GMR-01
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 its
slave port to the master port of the Horizonmicro2. The slave port of the Horizonmicro2
connects to the next Horizonmicro2 master port and so on, until the last Horizonmicro2
port is connected.
Figure 2-34 Microcell daisy chain network configuration
E1 LINK HDSL HDSL HDSL

BSC SLAVE M S M S M
EXTERNAL
MODEM Horizonmicro2 Horizonmicro2 Horizonmicro2
Star configuration
Figure 2-35 shows a BSC which is again connected to an external modem, which then
connects from its slave port to the master port of a Horizonmicro2. In this configuration
an external modem is used every time a link to a Horizonmicro2 is used, hence the star
formation.
Figure 2-35 Microcell star network configuration
E1 LINK HDSL
SLAVE M
EXTERNAL
MODEM Horizonmicro2
E1 LINK HDSL
BSC SLAVE M
EXTERNAL
MODEM Horizonmicro2
E1 LINK HDSL
SLAVE M
EXTERNAL
MODEM
Horizonmicro2
M = MASTER

30th Jun 02 68P02900W21-K 2–49
GMR-01
E1 link
In Figure 2-36 an E1 link is used from the BSC to the first Horizonmicro2. From there
onwards HDSL links are used running from master to slave in each Horizonmicro2, or
conversion can be at any BTS, in either direction.
Figure 2-36 Microcell configuration using E1/HDSL links
E1 LINK HDSL HDSL

S M S M
Horizonmicro2 Horizonmicro2 Horizonmicro2
BSC

2–50 68P02900W21-K 30th Jun 02
GMR-01
Picocell system planning
M-Cellaccess
The M-Cellaccess picocell system comprises a cabinet housing a maximum of two site
controllers (see Figure 2-37). These can each control up to six single carrier Picocell
Control Units (PCUs) which operate in all frequency bands that adopt the GSM standard
(GSM900 and DCS1800).
Figure 2-37 M-Cellaccess picocell system
PCC CABINET SITE B
PCU
PCU
BSU PCU
PCU
PCU
PCU
PCU
PCU
PCU
BSU
PCU
PCU
PCU
SITE A
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.

30th Jun 02 68P02900W21-K 2–51
GMR-01

2–52 68P02900W21-K 30th Jun 02
GMR-01
Chapter 3
BSS cell planning

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS cell planning
BSS cell planning
BSS planning requirements

When planning a mobile telephone system, the aim is to create a communications
network 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 the
operating network is always a solution achieved through compromise.
The cost of different network configurations can vary considerably. From an engineering
point of view it would be worth while using the most frequency efficient solutions despite
their high cost, but a mobile telephone network is so huge an investment that the
financial factors are always going to limit the possibilities. The effect of limited funds is
particularly obvious when the first stage of the network is being built. Consequently,
economical planning is a condition for giving the best possible service from the start.
The use of the GSM850, GSM900, EGSM900, DCS1800 and PCS1900 frequency bands
create many propagation based problems. Because the channel characteristics are not
fixed, they present design challenges and impairments that must be dealt with to protect
MS telephone users from experiencing excessively varying signal levels and lack of voice
quality.
It is important to be able to predict the RF path loss between the BTS and the MS within
the coverage area in different types of environment. To do this it is necessary to have
knowledge of the transmitter and receiver antenna heights, the nature of the environment
and the terrain variations.

30th Jun 02 68P02900W21-K 3–1
GMR-01
BSS cell planning GSM-001-103
Planning factors
When planning a network there are a number of major factors which must be considered
to 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.

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

30th Jun 02 68P02900W21-K 3–3
GMR-01
GSM frequency spectrum GSM-001-103
GSM frequency spectrum
The GSM900 frequency spectrum

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

3–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GSM frequency spectrum
The DCS1800 frequency spectrum

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

This is another adaptation of GSM into the 1900 MHz band. It is used in the United
States where the Federal Communications Commission has divided the band into 300
ARFCNs and issued licences to various operators to implement GSM networks. The
frequency separation is 80 MHz. The frequency range is:

30th Jun 02 68P02900W21-K 3–5
GMR-01
GSM frequency spectrum GSM-001-103
Horizonmacro adaptation for 850/1900 MHz operation

Horizonmacro BTSs are now available to support the GSM850 or PCS1900 MHz
frequency bands instead of the GSM900 or DCS1800 MHz frequency bands. These
850/1900 MHz BTSs require GSR5.1 or higher.
The frequency range for GSM850 is as follows:

The frequency range for PCS1900 is defined in the previous section.
Absolute radio frequency channel capacity

Each RF carrier supports eight time division multiplexed physical channels and each of
these is capable of supporting speech or signalling information (see Figure 3-2).
The maximum number of RF carriers at any one BTS site is 24 for Horizonmacro and
M-Cell6, and 25 for BTS6. Therefore the maximum number of physical channels
available at a BTS site is 24 x 8 = 192 for Horizonmacro and M-Cell6, and 25 x 8 = 200
for BTS6.
Figure 3-2 Eight TDMA timeslots per RF carrier
0 1 2 3 4 5 6 7
BTS Maximum 24 carriers for

Horizonmacro and M-Cell6
Maximum 25 carriers for BTS6

3–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GSM frequency spectrum
Modulation techniques and channel spacing

The modulation technique used in GSM is Gaussian minimum shift keying (GMSK). This
works by shaping the data to be modulated with a Gaussian filter. The filter removes
some of the harmonics from the data square wave producing a more rounded shape.
When this is applied to a phase modulator the result is a modified envelope shape at the
output of the modulator. The bandwidth of this envelope is narrower than that of a
comparable one produced from non-filtered data. With each modulating carrier occupying
a narrower bandwidth, more efficient use can be made of the overall bandwidth available.
The bandwidth allocated to each carrier frequency in GSM is 200 kHz. The actual
bandwidth occupied by a transmitted GSM carrier is far greater than 200 kHz, even with
Gaussian filtering. The signal therefore overlaps into surrounding frequencies, as
illustrated in Figure 3-3.
Figure 3-3 Modulation techniques and channel spacing
–10 dB POINT
CHANNEL 1 CHANNEL 2 CHANNEL 3

dB
0
–10
–20
–30
–40
–50
–60
–70
200 kHz
If two carriers from the same or adjacent cells are allocated adjacent frequencies or
channel numbers they will interfere with each other because of the described
overlapping. This interference is unwanted signal noise. All noise is cumulative, so
starting with a large amount by using adjacent channels our wanted signal will soon
deteriorate below the required quality standard. For this reason adjacent frequencies
should never be allocated to carriers in the same or adjacent cells.
Figure 3-3 illustrates the fact that the actual bandwidth of a GMSK modulated signal is
considerably wider than the 200 kHz channel spacing specified by GSM. At the channel
overlap point the signal strength of the adjacent channel is only –10 dB below that of the
wanted signal. While this just falls within the minimum carrier to interference ratio of 9 dB,
it is not insignificant and must be planned around so that allocation of adjacent
frequencies in adjacent cells never occurs.
One other consideration about channel spacing that must be considered is when using
combiners. If a cavity combining block is used, the frequencies for combining must be
separated by at least three ARFCNs otherwise it could cause intermodulation products
and spurious frequency generation. These could interfere with other carriers further away
in the radio spectrum, possibly in adjacent cells, so they would not necessarily be a
problem to the home cell so the source of interference becomes more difficult to locate.

30th Jun 02 68P02900W21-K 3–7
GMR-01
Traffic capacity GSM-001-103
Traffic capacity
Dimensioning
One of the most important steps in cellular planning is system dimensioning. To
dimension a system correctly and hence all the supporting infrastructure, some idea of
the projected usage of the system must be obtained (for example, the number of people
wishing to use the system simultaneously). This means traffic engineering.
Consider a cell with N voice channels; the cell is therefore capable of carrying N
individual simultaneous calls. The traffic flow can be defined as the average number of
concurrent calls carried in the cell. The unit of traffic intensity is the Erlang; traffic defined
in this way can be thought of as a measure of the voice load carried by the cell. The
maximum carried traffic in a cell is N Erlangs, which occurs when there is a call on each
voice channel all of the time.
If during a time period T (seconds), a channel carries traffic is busy for t (seconds), then
the average carried traffic, in Erlangs, is t/T. The total traffic carried by the cell is the sum
of the traffic carried by each channel. The mean call holding time is the average time a
channel is serving a call.

3–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Traffic capacity
Channel blocking
The standard model used to dimension a system is the Erlang B model, which models
the number of traffic channels or trunks required or a given grade of service and given
offered traffic. There will be times when a call request is made and all channels or trunks
are in use, this call is then blocked. The probability of this happening is the grade of
service of the cell. If blocking occurs then the carried traffic will be less than the offered
traffic. If a call is blocked, the caller may try again within a short interval.
Repeated call attempts of this type increase the offered traffic above the level if there had
been an absence of blocking. Because of this effect the notion of offered traffic is
somewhat confused, however, if the blocking probability is small, it is reasonable to
ignore the effect of repeated call attempts and assume that blocked calls are abandoned.
The number of calls handled during a 24 hour period varies considerably with time. There
are usually two peaks during week days, although the pattern can change from day to
day. Across the typical day the variation is such that a one hour period shows greater
usage than any other. From the hour with the least traffic to the hour with the greatest
traffic, the variation can exceed 100:1.
To add to these fairly regular variations, there can also be unpredictable peaks caused by
a wide variety of events (for example; the weather, natural disasters, conventions, sports
events). In addition to this, system growth must also be taken into account. There are a
set of common definitions to describe this busy hour traffic loading.
Busy Hour: The busy hour is a continuous period during which traffic volume or number
of call attempts is the greatest.
Peak Busy Hour: The busy hour each day it is not usually the same over a number of
days.
Time Constant Busy Hour: The one hour period starting at the same time each day for
which the average traffic volume or call attempts count is greatest over the days under
consideration.
Busy Season Busy Hour: The engineering period where the grade of service criteria is
applied for the busiest clock hour of the busiest weeks of the year.
Average Busy Season Busy Hour The average busy season busy hour is used for
trunk groups and always has a grade of service criteria applied. For example, for the
Average Busy Season Busy Hour load, a call requiring a circuit in a trunk group should
not encounter All Trunks Busy (ATB) no more than 1% of the time.
Peak loads are of more concern than average loads when engineering traffic routes and
switching equipment.

30th Jun 02 68P02900W21-K 3–9
GMR-01
Traffic capacity GSM-001-103
Traffic flow
If mobile traffic is defined as the aggregate number of MS calls (C) in a cell with regard to
the duration of the calls (T) as well as their number, then traffic flow (A) can be defined
as:
Traffic Flow (A) = C x T
Where: C 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 busy
hour is 120, then the traffic flow would be 120 x 1.5 = 180 call minutes or 3 call hours.
One Erlang of traffic intensity on one traffic channel means a continuous occupancy of
that particular traffic channel.
Considering a group of traffic channels, the traffic intensity in Erlangs is the number of
call-seconds per second or the number of call-hours per hour. As an example; if there
were a group of 10 traffic channels which had a call intensity of 5 Erlangs, then half of the
circuits would be busy at the time of measurement.
Grade of service
One measure of the quality of service is how many times a subscriber is unsuccessful in
setting up a call (blocking). Blocking data states what grade of service is required and is
given as a percentage of the time that the subscriber is unable to make a call. Typical
blocking for the 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 of
channels. The customers desired grade of service has a direct effect on the number of
channels needed in the network.

3–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Propagation effects on GSM frequencies
Propagation effects on GSM frequencies
Propagation production
Most of the methods used to predict propagation over irregular terrain are actually terrain
based, since they are designed to compute the diffraction loss and free space loss based
upon the path profile between the transmitter and the receiver. A widely used technique
in the United Kingdom is the prediction method used by the Joint Radio Committee (JRC)
of the Nationalized Power Industries. This method utilizes a computerized topographical
map in a data base, providing some 800,000 height reference points at 0.5 km intervals
covering the whole of the UK. The computer predicts the received signal level by
constructing the ground path profile between the transmitter and receiver using the data
base. The computer then tests the path profile for a line of sight path and whether
Fresnel zone clearance is obtained over the path. The free space and plane earth
propagation losses are calculated and the higher value is chosen. If the line of sight and
Fresnel-zone clearance test fails, then the programme evaluates the loss caused by any
obstructions and grades them into single or multiple diffraction edges. However, this
method fails to take any buildings into account when performing its calculation, the
calculations are totally based upon the terrain features.
Although the use of topographical based calculations are useful when designing mobile
communication systems, most mobile systems are centred around urban environments.
In these urban environments, the path between transmitter and the receiver maybe
blocked by a number of obstacles (buildings for example), so it is necessary to resort to
approximate methods of calculating diffraction losses since exact calculations for each
obstacle then become extremely difficult.

30th Jun 02 68P02900W21-K 3–11
GMR-01
Propagation effects on GSM frequencies GSM-001-103
Decibels
The decibel (dB) is used to express power output levels, receiver input levels and path
losses and enables calculations used when planning radio systems to be simplified. Any
number may be expressed as a decibel. The only requirement is that the original
description and unit scale is appended to the dB, so indicating a value which can be used
when adding, subtracting, or converting decibels.
For example, for a given power of 1 mW it may be expressed as 0 dBm, the m refers to
the 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 be
more easily expressed and calculated. For example take a power of 20 watts transmitted
from a BTS which was .000000001 W at the receiver. It is very difficult to accurately
express the total power loss in a simple way. By converting both figures to decibels
referenced to 1 mW, 20 W becomes 32 dBm and .000000001 W is –60 dBm. The path
loss can now be expressed as 92 dBm.
Multiplication and division also become easier when using decibels. Multiplication simply
requires adding the dB figures together, while division simply requires subtracting one dB
figure from the other. Another example is for every doubling of power figures, the
increase is 3 dB and for every halving of power the decrease is 3 dB. Table 3-1 gives
examples of dB conversions.
The basic equation used to derive power (dB) from power (W) is:
N dB = 10 x log10(PL/RPL)
Where: N is: the required power level in dB.
PL the power level being converted.
RPL 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 8W +4 –26 2.5 mW –80 –110 0.01 nW
+36 6 4W +1 –29 1.25 mW –90 –120 1 pW
+33 3 2W 0 ** –30 1 mW –100 –130 0.1 pW
+30 0* 1W –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.

3–12 68P02900W21-K 30th Jun 02
GMR-01
Fresnel zone
The Fresnel zone actually consists of several different zones, each one forming an
ellipsoid around the major axis of the direct propagation path. Each zone describes a
specific area depending on the wavelength of the signal frequency. If a signal from that
zone is reflected of an obstacle which protrudes into the zone, it means that a reflected
signal as well as the direct path signal will arrive at the receiver. Radio waves reflected in
the first Fresnel zone will arrive at the receiver out of phase with those taking the direct
path and so combine destructively. This results in a very low received signal strength. It
is important when planning a cell to consider all the radio paths for obstacles which may
produce reflections from the first Fresnel zone because if they exist it is like planning
permanent areas of no coverage in certain parts of the cell.
In order to calculate whether or not this condition exists, the radius of the first Fresnel
zone at the point where the object is suspected of intruding into the zone must be
calculated. The formula, illustrated in Figure 3-4, is as follows:
Ǹd1 < d2 < l

F1 +
d
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
FREQUENCY = 900 MHz

WAVELENGTH = 30 cm
F1
d
d1 d2
Once the cell coverage has been calculated the radio path can be checked for any
objects intruding into the first Fresnel zone. Ideally the link should be planned for no
=intrusions but in some cases they are unavoidable. If that is the case then the next best
clearance for the first Fresnel zone is 0.6 of the radius.
When siting a BTS on top of a building care must be taken with the positioning and
height of the antenna to ensure that the roof edge of the building does not intrude into the
first Fresnel zone.

30th Jun 02 68P02900W21-K 3–13
GMR-01
Radio refractive index (RRI)

It is important when planning a cell or microwave radio link to have an understanding of
the effects changes in the RRI can have on microwave communications, also what
causes these changes.
RRI measurements provide planners with information on how much a radio wave will be
refracted by the atmosphere at various heights above sea level. Refraction (see
Figure 3-5) is the changing of direction of propagation of the radio wave as it passes from
a more dense layer of the atmosphere to a less dense layer, which is usual as one
increases in height above sea level. It also occurs when passing from a less dense layer
to a more dense layer. This may also occur under certain conditions, even at higher
altitudes.
Figure 3-5 Refraction
REFRACTION OCCURS AS THE RADIO WAVE PASSES THROUGH

LAYERS OF DIFFERENT ATMOSPHERIC DENSITY
EARTH
The main effect to cell planners is that changes in the RRI can increase or decrease the
cell radius depending on conditions prevailing at the time.
The RRI is normally referenced to a value n at sea level. The value will vary with seasons
and location but for the UK the mean value is 1.00034. This figure is very cumbersome to
work with so convention has converted n to N.
Where: N is: (n–1) x 106.
The value of N now becomes 340 units for the UK. The actual seasonal and global
variations 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 as
height 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 has
significant effects on the RRI.
S Finally the temperature, pressure, and water vapour pressure have major effects
on 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 mixed
atmosphere the RRI will fall by 40 N units per 1 km increase in height above sea level.

3–14 68P02900W21-K 30th Jun 02
GMR-01
Measurement of the RRI

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

30th Jun 02 68P02900W21-K 3–15
GMR-01
Effects of deviations from the normal lapse rate

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

3–16 68P02900W21-K 30th Jun 02
GMR-01
Events which can modify the clear sky lapse rate

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

30th Jun 02 68P02900W21-K 3–17
GMR-01
Environmental effects on propagation

At the frequency range used for GSM it is important to consider the effects that objects
in the path of the radio wave will have on it. As the wave length is approximately 30 cm
for GSM900 and 15 cm for DCS1800, most objects in the path will have some effect on
the signal. Such things as vehicles, buildings, office fittings even people and animals will
all affect the radio wave in one way or another.
The main effects can be summarized as follows:
S 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 on
the type of materials and dimensions of the object in relation to the wavelength used.
Buildings, trees and people will all cause the signal to be attenuated by varying degrees.
Figure 3-8 Attenuation
INCOMING WAVE
OUTGOING WAVE
ATTENUATED BY THE OBJECT
OBJECT
ABSORBS
THE
ENERGY
IN THE
RADIO
WAVE
Reflection
This is caused when the radio wave strikes a relatively smooth conducting surface. The
wave is reflected at the same angle at which it arrived (see Figure 3-9). The strength of
the reflected signal depends on how well the reflector conducts. The greater the
conductivity the stronger the reflected wave. This explains why sea water is a better
reflector than sand.
Figure 3-9 Reflection
INCIDENT WAVE REFLECTED WAVE
EQUAL ANGLES
SMOOTH SURFACE, SUCH AS WATER,

VERY REFLECTIVE
AMOUNT OF REFLECTION DEPENDS ON

CONDUCTIVITY OF THE SURFACE

3–18 68P02900W21-K 30th Jun 02
GMR-01
Scattering
This occurs when a wave reflects of a rough surface (see Figure 3-10). The rougher the
surface and the relationship between the size of the objects and the wave length will
determine the amount of scattering that occurs.
Figure 3-10 Scattering
INCIDENT WAVE
ENERGY IS
SCATTERED
ROUGH STONY GROUND
Diffraction
Diffraction is where a radio wave is bent off its normal path. This happens when the radio
wave passes over an edge, such as that of a building roof or at street level that of a
corner of a building (see Figure 3-11). The amount of diffraction that takes place
increases as the frequency used is increased.
Diffraction can be a good thing as it allows radio signals to reach areas where they would
not normally be propagated.
Figure 3-11 Diffraction
SIDE VIEW
EXPECTED PATH
SHADOW DIFFRACTED
AREA WAVE
DIFFRACTED WAVE GIVING

PLAN VIEW COVERAGE AROUND THE CORNER
MICRO BTS AT
STREET LEVEL
DIFFRACTED WAVE GIVING

COVERAGE AROUND THE CORNER

30th Jun 02 68P02900W21-K 3–19
GMR-01
Polarization changes
This can happen any time with any of the above effects of due to atmospheric conditions
and geomagnetic effects such as the solar wind striking the earths atmosphere. These
polarisation changes mean that a signal may arrive at the receiver with a different
polarisation than that which the antenna has been designed to accept. If this occurs the
received signal will be greatly attenuated by the antenna.
Figure 3-12 shows the effects of polarization on a transmitted signal.
Figure 3-12 Polarization
ÎÎ ÎÎÎÎÎÎ
ELECTRICAL PART OF WAVE ELECTRICAL PART OF WAVE
VERTICALLY POLARIZED HORIZONTALLY POLARIZED
ÎÎÎÎ
ÎÎ ÎÎÎÎÎÎ
(CHANGED BY ELECTRICAL STORM)
ELECTRICAL STORM
ÎÎ
ÎÎÎÎ
ÎÎ ÎÎÎÎÎ
ÎÎÎÎÎÎ
ÎÎ
ÎÎ
ÎÎ ÎÎ ÎÎÎÎÎ
ÎÎÎÎÎÎ
ÎÎÎÎÎ
Tx
ÎÎÎÎÎ
ÎÎÎÎÎ Rx

3–20 68P02900W21-K 30th Jun 02
GMR-01
Multipath propagation
Rayleigh and Rician fading

As a result of the propagation effects on the transmitted signal, the receiver will pick up
the same signal which has been reflected from many different objects resulting in what is
known as multipath reception. The signals arriving from the different paths will all have
travelled different distances and will therefore arrive at the receiver at different times with
different signal strengths. Because of the reception time difference the signals may or
may not be in phase with each other. The result is that some will combine constructively
resulting in a gain of signal strength while others will combine destructively resulting in a
loss of signal strength.
The receiving antenna does not have to be moved very far for the signal strength to vary
by many tens of decibels. For GSM900, a move of just 15 cm or half a wavelength will
suffice to observe a change in signal strength. This effect is known as multipath fading. It
is typically experienced in urban areas where there are lots of buildings and the only
signals received are from reflections and refractions of the original signal.

30th Jun 02 68P02900W21-K 3–21
GMR-01
Rayleigh environment
This type of environment has been described by Rayleigh. He analysed the signal
strength along a path with a moving receiver and plotted a graph of the typical signal
strength measured due to multipath fading. The plot is specifically for non line of sight
(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
SIGNAL
STRENGTH
THRESHOLD
DEEP NULLS
1/2 WAVELENGTH
DISTANCE

3–22 68P02900W21-K 30th Jun 02
GMR-01
Rician environment
Where the signal path is predominantly line of sight (see Figure 3-15) with insignificant
reflections or diffractions arriving at the receiver, this is know as Rician distribution (see
Figure 3-16). There are still fades in signal strength but they rarely dip below the
threshold below which they will not be processed by the receiver.
Figure 3-15 Propagation effect – Rician environment
Rx
Tx
Figure 3-16 Rician distribution
SIGNAL
STRENGTH
THRESHOLD
DISTANCE
Comparison of DCS1800 and GSM900
From a pure frequency point of view it would be true to say that DCS1800 generally has
more fades than GSM900. However, they are usually less pronounced.

30th Jun 02 68P02900W21-K 3–23
GMR-01
Receive signal strength

A moving vehicle in an urban environment seldom has a direct line of sight path to the
base station. The propagation path contains many obstacles in the form of buildings,
other structures and even other vehicles. Because there is no unique propagation path
between transmitter and receiver, the instantaneous field strength at the MS and BTS
exhibits a highly variable structure.
The received signal at the mobile is the net result of many waves that arrive via multiple
paths formed by diffraction and scattering. The amplitudes, phase and angle of arrival of
the waves are random and the short term statistics of the resultant signal envelope
approximate a Rayleigh distribution.
Should a microcell be employed where part of a cell coverage area is predominantly line
of 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 through
free space. Free space is defined as the condition where there are no sources of
reflection in the signal path. This is impossible to achieve in reality but it does give a good
starting point for all propagation loss calculations.
Equally important in establishing path losses is the effect that the devices radiating the
signal have on the signal itself. As a basis for the calculation it is assumed the device is
an isotropic radiator. This is a theoretical pin point antenna which radiates equally in
every direction. If the device was placed in the middle of a sphere it would illuminated the
entire inner surface with an equal field strength.
In order to find out what the power is covering the sphere, the following formula is used:
P+ Pt
4 p < d2
Where: Pt is: the input power to the isotropic antenna.

d the distance from the radiator to the
surface of the sphere.
This formula illustrates the inverse square law that the power decreases with the square
of the distance.
In order to work out the power received at a normal antenna, the effective aperture (Ae)
of the receiving antenna must be calculated.
2
Ae + l
4 p
The actual received power can be calculated as follows:
Pr + P < Ae
Now if P is substituted with the formula for the power received over the inner surface of a
sphere and Ae with its formula, the result is:
Pr + ǒ4 pPt< d Ǔ < 4l p
2
2

3–24 68P02900W21-K 30th Jun 02
GMR-01
Free space path loss

This is the ratio of the actual received power to the transmitted power from an isotropic
radiator and can be calculated by the formula:
Free space loss in dB + 20 log ǒ4 pl< dǓ

Logs are used to to make the figures more manageable. Note that the formula is
dependant on distance and frequency. The higher the frequency the shorter the
wavelength, and therefore the greater the path loss.
The formula above is based on units measured in metres. To make the formula more
convenient, it can be modified to use kilometre and megahertz for the distance and
frequency. It becomes:
Free space loss + 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 by
itself when calculating the path loss in a multipath environment. To provide a more
realistic model, the earth in its role as a reflector of signals must be taken into account.
When calculating the plane earth loss the model assumes that the signal arriving at the
receiver consists of a direct path component and a reflective path component. Together
these are often called the space wave.
The formula for calculating the plane earth loss is:
L + 20 log ǒh1 <d h2Ǔ dB

2
This takes into account the different antenna heights at the transmitter and receiver.
Although this is still a simple representation of path loss. When this formula is used is
implies the inverse fourth law as opposed to the inverse square law. So, for every
doubling of distance there is a 12 dB loss instead of 6 dB, as with the free space loss
calculation.
The final factors in path loss are the ground characteristics. These will increase the path
loss even further depending on the type of terrain (refer to Figure 3-17). The earth
characteristics can be divided into three groups:
1. Excellent earth. For example sea water, this provides the least attenuation, so a
lower 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 the
highest losses and are typically found when planning urban cells.

30th Jun 02 68P02900W21-K 3–25
GMR-01
Figure 3-17 illustrates plane earth loss, taking all factors into account.
Figure 3-17 Plane earth loss
Tx
FREE SPACE LOSS Rx
d
1
PATH LOSS INCREASES 6 dB FOR A DOUBLING OF d.
Tx
Rx
h1
2
h2
PLANE EARTH LOSS INCLUDES ONE EARTH REFLECTOR.

PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d.
Tx
Rx
h1
3
h2
PLANE EARTH + CORRECTION FACTOR FOR TYPE OF TERRAIN.

PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d + A FACTOR
FOR TYPE OF TERRAIN.

3–26 68P02900W21-K 30th Jun 02
GMR-01
Clutter factor
The propagation of the RF signal in an urban area is influenced by the nature of the
surrounding urban environment. An urban area can then be placed into two sub
categories; the built up area and the suburban area. The built up area contains tall
buildings, office blocks, and high-rise residential tower blocks, whilst a suburban area
contains residential houses, playing fields and parks as the main features. Problems may
arise in placing areas into one of these two categories, so two parameters are utilized, a
land usage factor describing the percentage of the area covered by buildings and a
degree of urbanization factor, describing the percentage of buildings above storeys in the
area.
B(dB) + 20 ) ǒ40F Ǔ ) 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 occupied
by buildings.
H the difference in height between the squares containing
the transmitter and receiver.
K 0.094U – 5.9
U the percentage of L occupied by buildings above four
storeys.
A good base station site should be high enough to clear all the surrounding obstacles in
the immediate vicinity. However, it should be pointed out that although employing high
antennas increases the coverage area of the base station, this can also have adverse
effects on channel re-use distances because of the increased possibility of co-channel
interference.
Antenna gain
The additional gain provided by an antenna can be used to enhance the distance that the
radio wave is transmitted. Antenna gain is measured against an isotropic radiator. Any
antenna has a gain over an isotropic radiator because in practice it is impossible to
radiate the power equally in all directions. This means that in some directions the
radiated power will be concentrated. This concentration, or focusing of power, is what
enables the radio waves to travel further than those that if it were possible were radiated
from an isotropic radiator. See Figure 3-18.
Figure 3-18 Focusing of power
ISOTROPIC RADIATOR VERTICAL DIPOLE RADIATION PATTERN

(A SPHERICAL PATTERN) (SIDE VIEW)
TRANSMITTER

30th Jun 02 68P02900W21-K 3–27
GMR-01
Measuring antenna gain

The gain of a directional antenna is measured by comparing the signal strength of a
carrier emitted from an isotropic antenna and the directional antenna. First the power of
the isotropic radiator is increased so that both receive levels are the same. The emitted
powers required to achieve that are then compared for both antennas. The difference is a
measure of gain experienced by the directional antenna. It will always have some gain
when compared to an isotropic radiator. See example in Figure 3-19.
Figure 3-19 Measurement of gain
10 W
MEASUREMENT POINT MEASUREMENT POINT
1000 W
TRANSMITTER
In this example, to achieve a balanced receive level the isotropic radiator must have an
input power of 1000 W, as opposed to the directional antenna which only requires 10 W.
The gain of the directional antenna is 100 or 20 dBi.
Where: i is: for isotropic.
The more directional the antenna is made then the more gain it will experience. This is
apparent when sectorizing cells. Each sectored cell will require less transmit power than
the equivalent range omni cell due to the gain of its directional antenna, typically 14 dBi
to 17 dBi.
The gain is also present in the receive path, though in all cases the gain decreases as
the frequency increases. This is why the uplink mobile to BTS frequency is usually the
lowest part of the frequency range. This gives a slight gain advantage to the lower power
mobile transmitter.

3–28 68P02900W21-K 30th Jun 02
GMR-01
Propagation in buildings
With the increased use of hand portable equipment in mobile cellular systems, combined
with the increased availability of cordless telephones, it has become essential to study
RF propagation into and within buildings.
When calculating the propagation loss inside a building (see Figure 3-20) a building loss
factor is added to the RF path loss. This building loss factor is included in the model to
account for the increase in attenuation of the received signal when the mobile is moved
from outside to inside a building. This is fine if all users stand next to the walls of the
building when making calls, but this does not happen, so the internal distance through
which the signal must pass which has to be considered. Due to the internal construction
of a building, the signal may suffer from spatial variations caused by the design of the
interior of the building.
Figure 3-20 In building propagation
TRANSMITTER
W dBm
X dBm
X dBm = SIGNAL STRENGTH OUTSIDE BUILDING

W dBm = SIGNAL STRENGTH INSIDE BUILDING
BUILDING INSERTION LOSS (dBm) = X –W = B dBm
GAIN
TRANSMITTER
REFERENCE POINT
The building loss tends to be defined as the difference in the median field intensity at the
adjacent area just outside the building and the field intensity at a location on the main
floor of the building. This location can be anywhere on the main floor.
This produces a building median field intensity figure, which is then used for plotting
cell coverage areas and grade of service.
When considering coverage in tall buildings, coverage is being considered throughout the
building, if any floors of that building are above the height of the transmitting antenna a
path gain will be experienced.

30th Jun 02 68P02900W21-K 3–29
GMR-01
The Okumura method

In the early 1960s, a Japanese engineer named Okumura carried out a series of detailed
propagation tests for land mobile radio services at various different frequencies. The
frequencies were 200 MHz in the VHF band and 453 MHz, 922 MHz, 1310 MHz,
1430 MHz, and 1920 MHz in the UHF band. The results were statistically analyzed and
described for distance and frequency dependencies of median field strength, location
variabilities and antenna height gain factors for the base and mobile stations in urban,
suburban, and open areas over quasi-smooth terrain.
The correction factors corresponding to various terrain parameters for irregular terrain,
such as rolling hills, isolated mountain areas, general sloped terrain, and mixed land/sea
path were defined by Okumura.
As a result of these tests, carried out primarily in the Tokyo area, a method for predicting
field strength and service area for a given terrain of a land mobile radio system was
defined. The Okumura method is valid for the frequency range of 150 to 2000 MHz, for
distances between the base station and the mobile stations of 1 to 100 km, with base
station effective antenna heights of 30 to 100 m.
The results of the median field strength at the stated frequencies were displayed
graphically (see Figure 3-21). Different graphs were drawn for each of the test
frequencies in each of the terrain environments (for example; urban, suburban, hilly
terrain) Also shown on these graphs were the various antenna heights used at the test
transmitter base stations. The graphs show the median field strength in relation to the
distance in km from the site.
As this is a graphical representation of results, it does not transfer easily into a computer
environment. However, the results provided by Okumura are the basis on which path loss
prediction equations have been formulated. The most important work has been carried
out by another Japanese engineer named Hata. Hata has taken Okumura’s graphical
results and derived an equation to calculate the path loss in various environments. These
equations have been modified to take into account the differences between the Japanese
terrain and the type of terrain experienced in Western Europe.

3–30 68P02900W21-K 30th Jun 02
GMR-01
Figure 3-21 Okumura propagation graphs
110
922 MHz
100 h.= 320 m
h.= 220 m
X h.= 140 m
90
h.= 45m
FIELD STRENGTH (dB rel. 1 uV/m) FOR 1 kW ERP

h.= 3 m
80 X
Free Space
70 X
X
X X
60
X
X
50
X X
X
X
X
40
X
X
X
30 X
X X
20
X
X
X
10
X X
0 X
–10
0.6 1 2 3 5 7 10 20 30 40 50 60 70 80 90 100
LINEAR SCALE
LOG SCALE
DISTANCE (km)
PROPAGATION GRAPH FOR 922 MHz

30th Jun 02 68P02900W21-K 3–31
GMR-01
Hata’s propagation formula

Hata used the information contained in Okumura’s propagation loss report of the early
1960’s, which presented its results graphically, to define a series of empirical formulas to
allow propagation prediction to be done on computers. The propagation loss in an urban
area can be presented as a simple formula of:
A + B log 10R
Where: A 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 VHF
frequency ranges, Hata added an error factor to the basic formula to produce a series of
equations to predict path loss. To facilitate this action, Hata has set a series of limitations
which must be observed when using this empirical calculation method:
Where: Frequency range (fc) 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 path
loss, not the final signal strength at the receiver.
Urban Area:
Lp = 69.55 + 26.16 log10fc – 13.82.log10hb – a (hm)# + (44.9 – 6.66. log10hb).log10R dB
Where: # is: 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

3–32 68P02900W21-K 30th Jun 02
GMR-01
Power budget and system balance

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

30th Jun 02 68P02900W21-K 3–33
GMR-01
GSM900 path loss

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

3–34 68P02900W21-K 30th Jun 02
GMR-01
Path loss GSM900 vs DCS1800

Figure 3-24 illustrates the greater path loss experienced by the higher DCS1800
frequency range compared to the GSM900 band. The cell size is typical of that found in
urban or suburban locations. The difference in path loss for the GSM900 band at 0.2 km
compared with 3 km is 40 dB, a resultant loss factor of 10,000 compared to the
measurement at 0.2 km.
Figure 3-24 Path loss vs cell radius for small cells
170
160
DCS1800
(METROPOLITAN CENTRES)
150
PATH LOSS (dB)
140
130
GSM900
120
DCS1800
110 (MEDIUM SIZED CITIES AND
SUBURBAN CENTRES)
100
0.1 0.3 1.0 3.0
CELL RADIUS (km)

30th Jun 02 68P02900W21-K 3–35
GMR-01
Frequency re-use GSM-001-103
Frequency re-use
Introduction to re-use patterns

The network planner designs the cellular network around the available carriers or
frequency channels. The frequency channels are allocated to the network provider from
the GSM850, GSM/EGSM900, DCS1800 or PCS1900 band as shown below:
Frequency Band Tx Range Rx Range No. RF Carriers
GSM850 869 – 894 MHz 824 – 849 MHz 124
GSM900 935 – 960 MHz 890 – 915 MHz 124
EGSM900 925 – 960 MHz 880 – 915 MHz 174
DCS1800 1805 – 1880 MHz 1710 – 1785 MHz 374
PCS1900 1930 – 1990 MHz 1850 – 1910 MHz 299
Within this range of frequencies only a finite number of channels may be allocated to the
planner. The number of channels will not necessarily cover the full frequency spectrum
and there has to be great care taken when selecting/allocating the channels.
Installing a greater number of cells will provide greater spectral efficiency with more
frequency re-use of available frequencies. However, a balance must be struck between
spectral efficiency and all the costs of the cell. The size of cells will also indicate how the
frequency spectrum is used. Maximum cell radius is determined in part by the output
power of the mobile subscriber (MS) (and therefore, its range) and interference caused
by adjacent cells (see Figure 3-25).
Remember that the output power of the MS is limited in all frequency bands. Therefore to
plan a balanced transmit and receive radio path, the planner must make use of the path
loss and thus the link budget.
The effective range of a cell will vary according to location, and can be as much as 35 km
in rural areas and as little as 1 km in a dense urban environment.
Figure 3-25 Adjacent cell interference
CARRIER INTERFERING CARRIER

F 33 F 33
RECEIVE
SIGNAL
LEVEL
– 75dBm
– 100dBm
SERVING BTS INTERFERING BTS

DISTANCE
MOBILE POSITION

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

30th Jun 02 68P02900W21-K 3–37
GMR-01
4 site – 3 cell re-use pattern

Due to the increase in frequency robustness within GSM, different re-use frequency
patterns can be adopted which gives an overall greater frequency efficiency.
The most common re-use pattern is 4 site with 3 cells (see Figure 3-27). With the
available 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 between
cells is at least 2 to 1.
Figure 3-27 4 site – 3 cell re-use pattern
c1
c2
d1 c3 d1
d2 d2
b1 d3 b1 d3
b2 b2
b3 a1 b3 a1
a2 a2
c1 a3 c1 a3
c2 c2
c3 d1 c3 d1
d2 d2
b1 d3 b1 d3
b2 b2
b3 a1 b3
a2
a3 NEW CELL CAN
USE d1–3 FREQ
ALLOCATION
EXAMPLE
b1
b2
a1 b3
a2 a2
a3 c1
c2
c3
The other main advantage of this re-use pattern is if a new cell is required to be inserted
in the network, then there is always a frequency channel set available which will not
cause any adjacent channel interference.

3–38 68P02900W21-K 30th Jun 02
GMR-01
2 site – 6 cell re-use pattern

Another solution to possible network operator capacity problems may be an even higher
frequency re-use pattern. The re-use pattern, shown in Figure 3-28, uses a 2 site – 6 cell
re-use.
Figure 3-28 2 site – 6 cell re-use pattern
a1
a6 a2
b1 a5 a3
b6 b2 a4
b5 b3 b5
b4 b6 b4
a4 b1 b3
a5 a3 b2
a6 a2
a1
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 to
use 2 carriers per cell. However this may be extremely difficult and may not be possible
to implement. It also may not be possible due to the current network configuration.
However, the subscribers per km ratio would be improved.

30th Jun 02 68P02900W21-K 3–39
GMR-01
Carrier/ Interference (C/I) ratio

When a channel is re-used there is a risk of co-channel interference, which is where
other base stations are transmitting on the same frequency.
As the number of channel sets increases, the number of available channels per cell
reduces and therefore capacity reduces. But the interference level will also reduce,
increasing the quality of service.
The capacity of any one cell is limited by the interference that can be tolerated for a given
grade of service. A number of other factors, apart from the capacity, affect the
interference 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 a
cell can be compared to a previously defined acceptable criterion. For instance, the
criterion for the C/I ratio maybe set at 8 dB, with the expectation that the C/I
measurements will be better than that figure for 90% of cases (C/I90).
For a given re-use pattern, the predicted C/I ratio related to the D/R ratio can be
determined (see Figure 3-29) to give overall system comparison.
Figure 3-29 Carrier interference measurements
GSM system : 9dB ǒCIǓ + 7.94

(DńR)4
+ + 7.94
6
Therefore (D) 4 + 47.66

R
Thus ǒDRǓ + Ǹ47.66 + 2.62

4
(2 CELLS USING THE SAME BCCH FREQUENCY)

C/ D
I CAN BE RELATED TO /R
BS BS
R
MS
DISTANCE BETWEEN CELLS
D
ANALOGUE SYSTEM D/R = 4.4
GSM SYSTEM D/R= 2.62

3–40 68P02900W21-K 30th Jun 02
GMR-01
Other sources of interference

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

30th Jun 02 68P02900W21-K 3–41
GMR-01
Overcoming adverse propagation effects GSM-001-103
Overcoming adverse propagation effects
Hardware techniques
Multipath fading is responsible for more than just deep fades in the signal strength. The
multipath signals are all arriving at different times and the demodulator will attempt to
recover all of the time dispersed signals. This leads to an overlapping situation where
each signal path influences the other, making the original data very hard to distinguish.
This problem is known as inter symbol interference (ISI) and is made worse by the fact
that the output from the demodulator is rarely a square wave. The sharp edges are
normally rounded off so that when time dispersed signals are combined it makes it
difficult to distinguish the original signal state.
Another factor which makes things even more difficult is that the modulation technique
Gaussian minimum shift keying, itself introduces a certain amount of ISI. Although this is
a known distortion and can under normal conditions be filtered out, when it is added to
the ISI distortion caused by the time delayed multipath signals, it makes recovery of the
original data that much harder.
Frequency hopping
Frequency hopping is a feature that can be implemented on the air interface (the radio
path to the MS, for example) to help overcome the effects of multipath fading. GSM
recommends only one type of frequency hopping – baseband hopping; but the
Motorola BSS will support an additional type of frequency hopping, called synthesizer
hopping.
Baseband hopping
Baseband hopping is used when a base station has several transceivers available. The
data flow is simply routed in the baseband to various transceivers, each of which
operates on a fixed frequency, in accordance with the assigned hopping sequence. The
different transceivers will receive a specific individual timeslot in each TDMA frame
containing information destined for different MSs.
There are important points to note when using this method of providing frequency
hopping:
S There is a need to provide as many transceivers as the number of allocated

frequencies.
S Within Horizonmacro equipment applications, the use of any type of Tx block (TDF,
DCF, DDF) or cavity combining blocks (CCBs) is acceptable.
NOTE Baseband hopping or CCBs cannot be used with the GSM850 or

PCS1900 Horizonmacro BTS variants.
S Within M-Cell equipment applications, the use of either combining bandpass

filter/hybrid or cavity combining blocks is acceptable.
S The use of remote tuning combiners, cavity combining blocks or hybrid combiners
is acceptable in BTS6 equipment applications.

3–42 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Overcoming adverse propagation effects
Synthesizer hopping
Synthesizer hopping uses the frequency agility of the transceiver to change frequencies
on a timeslot basis for both transmit and receive. The transceiver board in the CTU, the
digital processing and control board in the TCU and the SCB in the DRCU calculates the
next frequency and programmes one of the pair of Tx and Rx synthesizers to go to the
calculated frequency. As the transceiver uses a pair of synthesizers for both transmit and
receive, 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 plus
one for the BCCH carrier.
S The output power available with the use of hybrid combiners must be consistent
with 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 good
candidates for synthesizer hopping, whilst cells with many carriers will be good
candidates for baseband hopping.
There is also one other rule: there can only be one type of hopping at a BTS site, not
a combination of the two.

30th Jun 02 68P02900W21-K 3–43
GMR-01
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 be
encoded. All logical channels require some form of convolutional encoding, but since
protection needs are different, the code rates may also differ.
The coding protection schemes, shown in Figure 3-30, are:
S Speech channel encoding.
S Common control channel encoding.
S Data channel encoding.
Figure 3-30 The coding process
20 ms 0.577 ms
INFORMATION INFORMATION
BLOCK BURSTS
SPEECH (260 BITS) SPEECH (8 BURSTS)
CONTROL (184 BITS) ENCODING INTERLEAVING CONTROL (4 BURSTS)
DATA (240 BITS) 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 speech
can still be reproduced.
Common control channel encoding

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

The data information is spread over 22 bursts. This is because every bit of data
information is very important. Therefore, when the data is reconstructed at the receiver, if
a burst is lost, only a very small proportion of the 20 ms block of data will be lost. The
error encoding mechanisms should then enable the missing data to be reconstructed.

3–44 68P02900W21-K 30th Jun 02
GMR-01
Figure 3-31 illustrates the coding process for speech, control and data channels; the
sequence is very complex.
Figure 3-31 Error protection and detection
EFR SPEECH FR SPEECH BCCH, PCH, AGCH, SDCCH, DATA TRAFFIC RACH + SCH
FRAME FRAME FACCH, SACCH, CBCH 9.6/4.8/2.4 k P0 BITS
244 BITS 244 BITS 184 BITS N0 BITS
CYCLIC CODE FIRECODE + TAIL ADD IN TAIL CYCLIC CODE + TAIL

+ REPETITION IN: 184 IN: N0 BITS IN: P0 BITS
IN: 244 OUT: 228 OUT: N1 BITS OUT: P1 BITS
OUT: 260
CLASS 1a
CYCLIC CODE
+ TAIL
IN: 260
OUT: 267
CONVOLUTION CODE CONVOLUTION CODE CONVOLUTION CODE CONVOLUTION CODE

IN: 267 BITS IN: 248 BITS + PUNCTURE IN: P1 BITS
OUT: 456 BITS OUT: 456 BITS IN: N1 BITS OUT: 2 x P1 BITS
OUT: 456 BITS
TCH/2.4
RE-ORDERING & PARTITIONING

+ STEALING FLAG
IN: 456 BITS
OUT: 8 SUB-BLOCKS DIAGONAL INTERLEAVING +
STEALING FLAG
IN: BLOCKS OF 456 BITS
OUT: 22 SUB-BLOCKS
BLOCK DIAGONAL BLOCK RECTANGULAR

INTERLEAVING INTERLEAVING
IN: 8 BLOCKS IN: 8 SUB-BLOCKS
OUT: PAIRS OF BLOCKS OUT: PAIRS OF SUB-BLOCKS
8 x TCH FR (BURSTS) 4 x BCCH, PCH, AGCH 1 x RACH

8 x TCH EFR (BURSTS) 4 x SDCCH, SACCH 1 x SCH (BURST)
8 x FACCH/TCH (BURSTS) 4 x CBCH (BURSTS)
8 x TCH 2-4 kBIT/S (BURSTS)
19 x TCH 9.6 kBIT/S (BURST)

30th Jun 02 68P02900W21-K 3–45
GMR-01
GSM speech channel encoding

The BTS receives transcoded speech over the Abis interface from the BSC. At this point
the speech is organized into its individual logical channels by the BTS. These logical
channels of information are then channel coded before being transmitted over the air
interface.
The transcoded speech information is received in frames, each containing 260 bits. The
speech bits are grouped into three classes of sensitivity to errors, depending on their
importance to the intelligibility of speech.
Class 1a
Three parity bits are derived from the 50 Class 1a bits. Transmission errors within these
bits are catastrophic to speech intelligibility, therefore, the speech decoder is able to
detect uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the
whole block is usually ignored.
Class 1b
The 132 Class 1b bits are not parity checked, but are fed together with the Class 1a and
parity bits to a convolutional encoder. Four tail bits are added which set the registers in
the receiver to a known state for decoding purposes.

3–46 68P02900W21-K 30th Jun 02
GMR-01
Class 2
The 78 least sensitive bits are not protected at all.
The resulting 456 bit block is then interleaved before being sent over the air interface.
NOTE Over the Abis link, when using full rate speech vocoding, 260
bits are transmitted in 20 ms equalling a transmission rate of
13 kbit/s. If enhanced full rate is used then 244 bits are
transmitted over the Abis link for each 20 ms sample. The EFR
frame is treated to some preliminary coding to build it up to 260
bits before being applied to the same channel coding as full rate.
The encoded speech now occupies 456 bits, but is still transmitted in 20 ms thus raising
the transmission rate to 22.8 kbit/s.
Figure 3-32 shows a diagrammatic representation of speech channel encoding.
Figure 3-32 Speech channel encoding
260 BITS
CLASS 1a CLASS 1b CLASS 2

50 BITS 132 BITS 78 BITS
TAIL
BITS
PARITY
CHECK
50 3 132 4
CONVOLUTIONAL CODE
378 78
456 BITS

30th Jun 02 68P02900W21-K 3–47
GMR-01
GSM speech channel coding for enhanced full rate

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

EFR speech frame:
S 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 to
Class 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 full
rate speech.
Figure 3-33 Preliminary coding for enhanced full rate speech
244 BITS

8
REPETITION
BITS ADDED
8 BIT CRC ADDED TO
TO CLASS 2
CLASS 1b BITS
BITS

260 BITS

3–48 68P02900W21-K 30th Jun 02
GMR-01
GSM control channel encoding

Figure 3-34 shows the principle of the error protection for the control channels. This
scheme is used for all the logical signalling channels, the synchronization channel (SCH)
and the random access burst (RACH). The diagram applies to SCH and RACH, but with
different numbers.
Figure 3-34 Control channel coding
184 BITS
184 PARITY BITS
FIRE CODE
TAIL BITS
184 40 4
CONVOLUTIONAL CODE
456
456 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 40
parity bits. Before the convolutional encoding, four tail bits are added which set the
registers in the receiver to a known state for decoding purposes.
The output from the encoding process for each block of 184 bits of signalling data is 456
bits, exactly the same as for speech. The resulting 456 bit block is then interleaved
before being sent over the air interface.

30th Jun 02 68P02900W21-K 3–49
GMR-01
GSM circuit-switched data channel encoding

Figure 3-35 shows the principle of the error protection for the 9.6 kbit/s data channel. The
other data channels at rates of 4.8 kbit/s and 2.4 kbit/s are encoded slightly differently,
but the principle is the same.
Figure 3-35 Data channel encoding
DATA CHANNEL 9.6 kbit/s

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

3–50 68P02900W21-K 30th Jun 02
GMR-01
Mapping logical channels onto the TDMA frame structure
Interleaving
Having encoded or error protected the logical channel, the next step is to build its
bitstream into bursts that can then be transmitted within the TDMA frame structure. It is
at this stage that the process of interleaving is carried out. Interleaving spreads the
content of one traffic block across several TDMA timeslots. The following interleaving
depths are used:
S 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 interface
radio environment.
Because of interference, noise, or physical interruption of the radio path, bursts may be
destroyed or corrupted as they travel between MS and BTS, a figure of 10–20% is quite
normal. The purpose of interleaving is to ensure that only some of the data from each
traffic block is contained within each burst. By this means, when a burst is not correctly
received, the loss does not affect overall transmission quality because the error
correction techniques are able to interpolate for the missing data. If the system worked
by simply having one traffic block per burst, then it would be unable to do this and
transmission quality would suffer.
It is interleaving (summarized in Table 3-2) that is largely responsible for the robustness
of the GSM air interface, enabling it to withstand significant noise and interference and
maintain the quality of service presented to the subscriber.
Table 3-2 Interleaving

TRAU frame type Number of GSM bursts spread over
Speech 8
Control 4
CS data 22

30th Jun 02 68P02900W21-K 3–51
GMR-01
Diagonal interleaving – speech

Figure 3-36 illustrates, in a simplified form, the principle of the interleaving process
applied to a full-rate speech channel.
Figure 3-36 Diagonal interleaving – speech
20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS 20 ms SPEECH SAMPLE 456 BITS
BITS 4, 12, 20, 28 ..... 452 BITS 0, 8, 16, 24 ..... 448 BITS 0, 8, 16, 24 ..... 448
MAPPED TO ODD BITS MAPPED TO EVEN BITS MAPPED TO EVEN BITS

OF BURST OF BURST OF BURST
BITS 4, 12, 20, 28 ..... 452
MAPPED TO ODD BITS

OF BURST
ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ
ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ ÍÍ
012345678 .... 113 012345678 .... 113
The diagram shows a sequence of speech blocks after the encoding process previously
described, all from the same subscriber conversation. Each block contains 456 bits,
these blocks are then divided into eight blocks each containing 57 bits. Each block will
only contain bits from even bit positions or bits from odd bit positions.
The GSM burst will now be produced using these blocks of speech bits.
The first four blocks will be placed in the even bit positions of the first four bursts. The
last four blocks will be placed in the odd bit positions of the next four bursts.
As each burst contains 114 traffic carrying bits, it is in fact shared by two speech blocks.
Each block will share four bursts with the block preceding it, and four with the block that
succeeds it, as shown. In the diagram block 5 shares the first four bursts with block 4
and the second four bursts with block 6.

3–52 68P02900W21-K 30th Jun 02
GMR-01
Transmission – speech
Each burst will be transmitted in the designated timeslot of eight consecutive TDMA
frames, providing the interleaving depth of eight.
Table 3-3 shows how the 456 bits resulting from a 20 ms speech sample are distributed
over 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 a

different channel combination: traffic, broadcast, dedicated or combined.
NOTE Note that FACCH, because it steals speech bursts from a

subscriber channel, experiences the same kind of interleaving as
the speech data that it replaces (interleaving depth = 8).
The FACCH will steal a 456 bit block and be interleaved with the speech. Each burst
containing a FACCH block of information will have the appropriate stealing flag set.

30th Jun 02 68P02900W21-K 3–53
GMR-01
Rectangular interleaving – control

Figure 3-37 illustrates, in a simplified form, the principle of rectangular interleaving. This
is applied to most control channels.
Figure 3-37 Rectangular interleaving – control
CONTROL 2 3
1 4 5 6
BLOCKS
456 BITS
4 5 6
114 114 114 114

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

3–54 68P02900W21-K 30th Jun 02
GMR-01
Diagonal interleaving – CS data

Figure 3-38 illustrates, in a simplified form, diagonal interleaving applied to a 9.6 kbit/s
data channel.
The diagram shows a sequence of data blocks after the encoding process previously
described, all from the same subscriber. Each block contains 456 bits, these blocks are
divided into four blocks each containing 114 bits. These blocks are then interleaved
together.
The first 6 bits from the first block are placed in the first burst. The first 6 bits from the
second block will be placed in the second burst and so on. Each 114 bit block is spread
across 19 bursts and the total 456 block will be spread across 22 bursts.
Data channels are said to have an interleaving depth of 22, although this is sometimes
also referred to as an interleaving depth of 19.

30th Jun 02 68P02900W21-K 3–55
GMR-01
Transmission – CS data
The data bits are spread over a large number of bursts, to ensure that the data is
protected. Therefore, if a burst is lost, only a very small amount of data from one data
block will actually be lost. Due to the error protection mechanisms used, the lost data has
a higher chance of being reproduced at the receiver.
This wide interleaving depth, although providing a high resilience to error, does introduce
a time delay in the transmission of the data. If data transmission is slightly delayed, it will
not effect the reception quality, whereas with speech, if a delay were introduced this
could be detected by the subscriber. This is why speech uses a shorter interleaving
depth.
Figure 3-38 shows a diagrammatic representation of diagonal interleaving for CS data.
Figure 3-38 Diagonal interleaving – CS data
DATA
BLOCKS 1 2 3 4 5 6
456 BITS
114 114 114 114

BITS BITS BITS BITS
114 114 114 114
FIRST FIRST FIRST FIRST LAST LAST LAST LAST

6 6 6 6 6 6 6 6
BITS BITS BITS BITS BITS BITS BITS BITS
Í ÍÍÍ ÍÍ ÍÍ
Í ÍÍÍ
Í ÍÍ
Í Í ÍÍ ÍÍ Í Í Í Í
ÍÍÍÍÍÍÍ
1 2 ÍÍÍÍ
3 ÍÍÍÍ
4 ÍÍÍÍÍÍÍÍÍÍ
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

3–56 68P02900W21-K 30th Jun 02
GMR-01
GPRS channel coding schemes

Four 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 carrying
RLC data blocks, that consists of a half rate convolutional code for FEC and a 40 bit fire
code for BCS. The radio block using CS1 contains 181 data bits, excluding the USF and
BCS. CS1 provides a user data rate of 9.05 kbit/s.
Figure 3-39 GPRS channel coding scheme 1 (CS1)
USFF Header and Data (181 bits) BCS 224 bits

3 40
4 tail bits
½ convolutional coding
6
456 bits

CS2 (see Figure 3-40) uses a punctured version of the same half rate convolutional code
as CS1 for FEC and a 16-bit CRC for BCS. The radio block using CS2 contains 268 data
bits, excluding the USF and BCS. CS2 provides a user data rate of 13.4 kbit/s.

6 16
4 tail bits
12
588 bits
Puncturing
(132 bits)
456 bits
12

30th Jun 02 68P02900W21-K 3–57
GMR-01

CS3 (see Figure 3-41) uses another punctured version of the same half rate
convolutional code as CS1 for FEC and a 16-bit CRC for BCS. The radio block using
CS3 contains 312 data bits, excluding the USF and BCS. CS3 provides a user data rate
of 15.6 kbit/s.

6 16
4 tail bits
12
676 bits
Puncturing
(220 bits)
456 bits
12

CS4 (see Figure 3-42) is a coding scheme that has no coding for error correction and
has a 16-bit CRC for BCS. The radio block using CS4 contains 428 data bits, excluding
the USF and BCS. CS4 provides a user data rate of 21.4 kbit/s.

12 16
No Coding
12
456 bits

3–58 68P02900W21-K 30th Jun 02
GMR-01
All control channels except for the PRACH use CS1. Two types of packet random access
burst may be transmitted on the PRACH: an 8 information bits random access burst, or
an 11 information bits random access burst (called the extended packet random access
burst). The mobile must support both random access burst types.
GPRS traffic channels may use scheme CS1, CS2, CS3 or CS4. This allows the coding
scheme to be dynamically adapted to the channel conditions and thereby maximising
throughput 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 to
a MS to transmit. The BCS is Block Check Sequence, which is used for the detection of
errors 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 Code USF Pre- Radio BCS Tail Coded Punc- Data
rate coded blocks bits tured rate
USF excl. bits kbit/s
USF
and
BCS
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 coders
in the BTS to the PCU is currently implemented using 16 kbit/s TRAU-like links. These
links are carried over sub-rate switched E1 timeslots which have some signalling included
to 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 carry
CS3 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 a
32 kbit/s TRAU channel. The two 16 kbit/s channels are referred to as the left and right
channels. The left channel is the primary channel which is currently used for all GPRS
traffic. The right (or auxiliary) channel is used for the larger CS3 and CS4 GPRS
TRAU-like frames.
NOTE Only one 16 kbit/s timeslot (CIC) is used between the BSC and
RXCDR for a CS call, therefore termination is necessary.

30th Jun 02 68P02900W21-K 3–59
GMR-01
Voice activity detection (VAD)

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

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

3–60 68P02900W21-K 30th Jun 02
GMR-01
Receive diversity
In its simplest case, multipath fading arises from destructive interference between two
transmission paths. The deepest instantaneous fade occurring at the frequency for which
the effective path length difference is an odd multiple of half wavelengths.
If two receive antennas are mounted a defined distance apart, then it follows that the
probability of them simultaneously experiencing maximum fade depth at a given
frequency is very much less than for the single antenna situation.
There are three ways of utilizing this concept:
S The receiver can be switched between the two RF receive paths provided two
antennas.
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 the
multipath transmission.
Each of the methods has advantages and disadvantages.
In the case of the switched configuration, it simply chooses the better of the two RF
signals which is switched through to the receiver circuitry.
Phase alignment has the advantage of being a continuously optimized arrangement in
terms of signal level, but phase alignment diversity does not minimize distortion. The
Motorola transceivers use this diversity concept.
The distortion minimizing approach, whilst being an attractive concept, has not yet been
implemented in a form that works over the full fading range capabilities of the receivers
and therefore has to switch back to phase alignment at low signal levels. This means a
rather complex control system is required.
It must be emphasized that diversity will not usually have any significant effect on the
mean depression component of fading, but the use of phase alignment diversity can help
increase the mean signal level received.
NOTE Remember in microcellular applications that the M-Cellcity and

Horizonmicro / Horizonmicro2 do not support spatial diversity.
Figure 3-44 Receive diversity
MOBILE
PATH LENGTH
IN WAVELENGTHS
ANTENNAS
(approx 10 wavelengths)
METHODS OF UTILIZATION:
SPACE BETWEEN
a. SWITCHED.
b. PHASE ALIGNED AND SUMMED.
c. PHASE ALIGNED WITH MINIMUM DISTORTION.
BTS

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

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

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

URBAN/CITY
ENVIRONMENTS
RURAL AREAS
BUILDINGS
LIFTS TUNNELS

30th Jun 02 68P02900W21-K 3–63
GMR-01
Subscriber environment GSM-001-103
Distribution
Not only do network designers have to identify the types of subscriber that use the
cellular network now and in the future, but at what location these subscribers are
attempting to use their phones.
Dense urban environments require an entirely different design approach, due to
considerations mentioned earlier in this chapter, than the approach used to design
coverage for a sparsely populated rural environment.
Road and rail networks have subscribers moving at high speed, so this must be
accounted for when planning the interaction between network entities whilst the
subscriber is using the network. Even in urban areas, the network designer must be
aware that traffic is not necessarily evenly distributed. As Figure 3-47 illustrates, an
urban area may contain sub-areas of uneven distribution such as a business or industrial
district, and may have to plan for a seasonal increase of traffic due to, say, a convention
centre. It is vitally important that the traffic distribution is known and understood prior to
network design, to ensure that a successful quality network is implemented.
Figure 3-47 Subscriber distribution
HIGH SPEED MOBILES

(RAILWAYS)
RURAL
URBAN
BUSINESS AREAS
40%
ROAD/RAIL
NETWORK
EXHIBITIONS
INDUSTRIAL 10%
20%
RESIDENTIAL
30%
SUBSCRIBERS DISTRIBUTION CHANGES ON A HOURLY BASIS

3–64 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Subscriber environment
Hand portable subscribers

The network designer must ensure that the network is designed to ensure a quality
service for the most demanding subscriber. This is the hand portable subscriber. The
hand portable now represents the vast majority of all new subscriber units introduced into
cellular networks. So clearly the network operators, and hence the network designers,
must recognise this.
Before commencing network design based around hand portable coverage, the network
designer must first understand the limitations of the hand portable unit and secondly,
what the hand portable actually requires from the network.
The hand portable phone is a small lightweight unit which is easy to carry and has the
ability to be used from any location. The ability of the unit to be used at any location
means that the network must be designed with the provision of good in-building coverage
as an essential element.
To further complicate the network designers job, these hand portable units have a low
output power. 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 RF
propagation limitations.
For practical purposes, the actual transmit power of the hand portable should be kept as
low as possible during operation. This helps not only from an interference point of view,
but this also helps to extend the available talk time of the subscriber unit, which is limited
by battery life.

30th Jun 02 68P02900W21-K 3–65
GMR-01
Subscriber environment GSM-001-103
Future planning
Normal practice in network planning is to choose one point of a well know re-use model
as a starting point. Even at this early stage, the model must be improved because any
true traffic density does not follow the homogeneous pattern assumed in any theoretical
models.
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 traffic
when leaving city areas. It is uneconomical to build the whole network using a standard
cell size, it becomes necessary to use cells of varying sizes.
Connecting areas with different cell sizes brings about new problems. In principle it is
possible to use cells of different size side by side, but without careful consideration this
may lead to a wasteful frequency plan. This is due to the fact that the re-use distance of
larger cells is greater than that of smaller cells. The situation is often that the borders are
so close to the high density areas that the longer re-use distances mean decreased
capacity. Another solution, offering better frequency efficiency, is to enlarge the cell size
gradually from small cells into larger cells.
In most cases, the traffic concentrations are so close to each other that the expansion
cannot be completed before it is time to start approaching the next concentration, by
gradually decreasing the cell size. This is why the practical network is not a regular
cluster composition, but a group of directional cells of varying size.
Besides this need for cells of different size, the unevenness of the traffic distribution also
causes problems in frequency planning. Theoretical frequency division methods
applicable to homogenous clusters cannot be used. It is quite rare that two or more
neighbouring cells need the same amount of channels. It must always be kept in mind
that the values calculated for future traffic distribution are only crude estimates and that
the real traffic distribution always deviates from these estimates. In consequence, the
network plan should be flexible enough to allow for rearrangement of the network to meet
the real traffic needs.
Conclusion
In conclusion, there are no fixed rules for radio network planning. It is a case of
experimenting and reiterating. By comparing different alternatives, the network designers
should find a plan that both fulfils the given requirements and keeps within practical
limitations. When making network plans, the designers should always remember that
every location in a network has its own conditions, and all local problems must be tackled
and solved on an individual basis.

3–66 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 The microcellular solution
The microcellular solution
Layered architecture
The basic term layered architecture is used in the microcellular context to explain how
macrocells overlay microcells. It is worth noting that when talking of the traffic capacity of
a microcell it is additional capacity to that of the macrocell in the areas of microcellular
coverage.
The traditional cell architecture design, Figure 3-48, ensures that, as far as possible, the
cell gives almost total coverage for all the MSs within its area.
Figure 3-48 Layered architecture
MACROCELL
MICROCELL A MICROCELL B
TOP VIEW
SIDE VIEW MACROCELL
MICROCELL A MICROCELL B

30th Jun 02 68P02900W21-K 3–67
GMR-01
The microcellular solution GSM-001-103
Combined cell architecture

A combined cell architecture system, as illustrated in Figure 3-49, is a multi-layer system
of macrocells and microcells. The simplest implementation contains two layers. The bulk
of the capacity in a combined cell architecture is provided by the microcells. Combined
cell systems can be implemented into other vendors networks.
Figure 3-49 Combined cell architecture
UNDERLAYED MICROCELL
(COULD BE A DIFFERENT VENDOR)
CONTIGUOUS COVERAGE OVER AREAS OF

HIGH SLOW MOVING TRAFFIC DENSITY
OVERLAYED MACROCELLS
Macrocells: Implemented specifically to cater for the fast-moving MSs and to provide a
fallback service in the case of coverage holes and pockets of interference in the microcell
layer. Macrocells form an umbrella over the smaller microcells.
Microcells: Microcells handle the traffic from slow-moving MSs. The microcells can give
contiguous coverage over the required areas of heavy subscriber traffic.
Picocells: Low cost installation by using in-building fibre optics or telephone wiring with
a HDSL modem, easily expanded to meet capacity requirements. Efficient use of the
frequency spectrum due to low power transceivers causing low interference to external
networks. Higher quality speech compared with external illumination of the building due
to improved uplink quality.

3–68 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 The microcellular solution
Combined cell architecture structure

A combined cell architecture employs cells of different sizes overlaid to provide
contiguous coverage. This structure is shown in Figure 3-50.
Figure 3-50 Combined cell architecture structure

LINK TO IMPLEMENT MICROCELLS AS A SEPARATE SYSTEM
ALTERNATIVE SYSTEM (MICROCELLS CONTROLLED BY THE SAME BSC AS MACROCELLS)
MSC
BSC A
SYSTEM 2
MICROCELL
BSC B
SYSTEM 1 BTS 2 BTS 5

MACROCELL
BTS 1 BTS 4
BTS 3
MICROCELL
COVERAGE
PICOCELL
MACROCELL COVERAGE
SYSTEM 1= OVERLAY SYSTEM

SYSTEM 2= UNDERLAY SYSTEM
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 of
traffic.
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 solution
As the GSM network evolves and matures its traffic loading will increase as the number
of subscribers grow. Eventually a network will reach a point of traffic saturation. The use
of microcells can provide high traffic capacity in localised areas.
The expansion of a BTS site past its original designed capacity can be a costly exercise
and the frequency re-use implications need to be planned carefully (co-channel and
adjacent channel interference). The use of microcells can alleviate the increase in
congestion, the microcells could be stand-alone cells to cover traffic hotspots or a
contiguous cover of cells in a combined architecture. The increased coverage will give
greater customer satisfaction.

30th Jun 02 68P02900W21-K 3–69
GMR-01
Frequency planning GSM-001-103
Frequency planning
Introduction to frequency planning

The ultimate goal of frequency planning in a GSM network is attaining and maintaining
the highest possible C/I ratio everywhere within the network coverage area. A general
requirement is at least 12 dB C/I, allowing tolerance in signal fading above the 9dB
specification 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 planning
cycle time.
Rules for synthesizer frequency hopping (SFH)

As the BCCH carrier is not hopping, it is strongly recommended to separate bands for
BCCH and TCH, as shown in Figure 3-51.
Figure 3-51 Separating BCCH and TCH bands
n channels m channels
BCCH TCH
Guard Band
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 is
suggested.
Figure 3-52 Band usage for macrocells with microcells
Macro BCCH Micro Macro TCH

Micro TCH BCCH (SFH)

3–70 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Frequency planning
Practical rules for TCH 1x3 re-use pattern

S BCCH re-use plan: 4x3 or 5x3, depending on the bandwidth available and
operating environment.
S Divide the dedicated band for TCH into 3 groups with an equal number of
frequencies (N). These frequencies will be the ARFCN equipped in the MA list of a
hopping system (FHI).
S Use an equal number of frequencies in all cells within the hopping area. The
allocation of frequencies to each sector is recommended to be in a regular or
continuous sequence (see planning example).
S The number of frequencies (N) in each group is determined by the design loading
factor (or carrier-to-frequency ratio). A theoretical maximum of 50% is permitted in
1x3 SFH. Any value higher than 50% would practically result unacceptable quality.
Some commonly used loading factors (sometimes termed as fractional load
factors) are 40%, 33%, 25%, etc.
As a general guideline,
(highest non BCCH transceiver count in a cell)
N+
(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 for
different sites. This will help to randomize the co-channel interference level
between the sites.
S Use different MAIOs to control adjacent channel interference between the sectors
within a site
NOTE Mobile Allocation (MA) is the set of frequencies that the
mobile/BTS is allowed to hop over. Two timeslots on the same
transceiver of a cell may be configured to operate on different
MAs. MA is the subset of the total allocated spectrum for the
GSM operator and the maximum number of frequencies in a MA
list is limited to 64 by GSM recommendations.
Mobile Allocation Index Offset (MAIO) is an integer offset that
determines which frequency within the MA will be the operating
frequency. If there are N frequencies in the MA list, then MAIO =
{0, 1, 2, … N–1}.
Hopping Sequence Number (HSN) is an integer parameter that
determines how the frequencies within the MA list are arranged.
There are 64 HSNs defined by GSM. HSN = 0 sets a cyclical
hopping sequence where the frequencies within the MA list are
repeated in a cyclical manner.
HSN = 1 to 63 provides a pseudo random hopping sequence.
The pseudo random pattern repeats itself after every
hyperframe, which is equal to 2,715,648 (26 x 51 x 2048) TDMA
frames, or about 3 hours 28 minutes and 54 seconds.
Motorola defines a Frequency Hopping Indicator (FHI) that is
made up of the above three GSM defined parameters. Up to 4
different FHIs can be defined for a cell in a Motorola BSS and
every timeslot on a transceiver can be independently assigned
one of the defined FHI. MAI is an integer that points to the
frequency within a MA list, where MAI = 0 and MAI = N–1 being
the lowest and highest frequencies in the MA list of N
frequencies. MAI is a function of the TDMA frame number (FN),
HSN and MAIO of a frequency hopping system.

30th Jun 02 68P02900W21-K 3–71
GMR-01
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
8 channels
Macro BCCH Micro Macro TCH

Micro TCH BCCH (SFH)
12 channels 27 channels
A total of 49 channels are available and the first and last one are reserved as guard
bands. Thus, there are 47 usable channels. 12 channels are used in the BCCH layer with
a 4x3 re-use pattern.
Based on 33% loading and a 4-4-4 configuration, N is calculated as N = 3 / 0.33 = 9
hopping frequencies per cell. Thus, a total of 27 channels are required for the hopping
TCH 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, Any from 0, 2, 4
33, 36, 39, 42, 45 {1, 2, … 63}
Sector B 22, 25, 28, 31, Same as above 1, 3, 5
34, 37, 40, 43, 46
Sector C 23, 26, 29, 32, Same as above 0, 2, 4
35, 38, 41, 44, 47
The above MAIO setting will avoid all possible adjacent channel interference among
sectors within the same site. The interference (co or adjacent channel) between sites will
still exist but it is reduced by the randomization effect of the different HSNs.

3–72 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Frequency planning
Practical rules for TCH 1x1 re-use pattern

S 1x1 is usually practical in rural area of low traffic density, where the average
occupancy of the hopping frequencies is low. With careful planning, it can be used
in high traffic areas as well.
S BCCH re-use plan: 4X3 or 5X3, depending on the bandwidth available and
operating environment.
S The allocation of TCH frequencies to each sector is recommended to be in a
regular or continuous sequence.
S Use different HSNs to reduce interference (co and adjacent channel) between the
sites.
S Use the same HSNs for all carriers within a site and use MAIOs to avoid adjacent
and co–channel interference between the carriers. Repeated or adjacent MAIOs
are not to be used within the same site to avoid co-channel and adjacent channel
interference respectively.
S A maximum loading factor of 1/6 or 16.7% is inherent in a continuous sequence of
frequency allocation. Since adjacent MAIOs are restricted, the maximum number
of MAIOs permitted is:
Max MAIOs + 1 * (Total allocated channels)

2
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 to
avoid co-channel
interference
HSN = 1
HSN = 1 HSN = 1
Non adjacent MAIOs to

avoid adjacent channel
interference

30th Jun 02 68P02900W21-K 3–73
GMR-01
Rules for baseband hopping (BBH)

All the rules outlined for SFH are generally applicable to BBH. As the BCCH is in the
hopping 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
Micro BCCH
BBH channels and micro TCH

3–74 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 2G–3G handovers using inter-radio access technology
2G–3G handovers using inter-radio access technology
Introduction to 2G–3G handovers

An optional feature of GSR6 is support for handovers between different Radio Access
Technology (RAT) networks in the circuit switched domain. The RAT can be 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 is
described here. For further information on UMTS, refer to System Information: UMTS
Equipment Planning, 68P02905W22 (UMTS-500-103).
2G–3G handover description

The 2G–3G handover feature supports handovers between different RAT networks. The
RAT can be either 2G (GSM) or 3G (UMTS).
Current evolving 3G UMTS networks will soon allow operators to provide UMTS
coverage along with GSM/GPRS coverage in their networks.
This feature enables a multi-RAT MS (a mobile station that can function in multiple Radio
Access Networks (RANs)) to handover between a GSM RAN and a 3G RAN (UMTS
Radio 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 idle
mode.
Restrictions
There is currently an upper limit of 16 FDD UTRAN neighbours in the GSM/GPRS
system.
Implementation
BSS changes allow 2G (GSM) to 3G (UMTS) cell reselection in GSM idle mode, and 3G
to 2G handovers in circuit-switched dedicated mode.
The BSS Inter-RAT handover GSM function is an option that must be unrestricted by
Motorola. It also requires unrestricting on site by the user with the inter_rat_enabled
parameter.
A future feature (not yet implemented) will contain BSS changes to allow 2G–3G
handovers in circuit-switched dedicated mode.
With the arrival of UMTS systems, there are likely to be small UMTS coverage areas
within larger GSM coverage areas. In such environments the call would drop when a
UMTS 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 the
UMTS coverage area is high. A GSM subscriber may wish to access a service with
specific QoS characteristic (for example, very high bit rate data service) that may not be
supported in the GSM system.
To avoid these problems the operator may wish to configure their network such that
handover and cell reselection between UMTS and GSM is possible. The GSM BSS
inter-RAT handover function provides a solution to these problems by allowing a
multi-RAT MS to perform cell reselection while in idle mode, and to hand over while in
dedicated mode from a UMTS FDD mode cell to a GSM cell.

30th Jun 02 68P02900W21-K 3–75
GMR-01
2G–3G handovers using inter-radio access technology GSM-001-103
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 HANDOVER
COMMAND messages will be updated to allow a multi-RAT MS to perform
measurements on UMTS Frequency Division Duplex (FDD) neighbour cells for the
purpose of cell reselection. The CLASSMARK UPDATE message is updated to support
the MS revision level (2) multi-RAT MS.
CCDSP firmware has been updated to store multiple instances of the SI2ter and
SI2quater messages.
Abis interface
The Abis Interface supports changes to the A-interface required for messages passed
from the BSC to the BTS.
A-interface
The HANDOVER REQUEST message sent from the MSC is updated with a new serving
area identifier within the cell identifier (serving). This indicates that the handover
originates from a UMTS network. This interface also provides support for the Information
Interface Equipment (IE) at the handing over BSS to that at the receiving BSS. This
container can contain a number of User Equipment (UE) specific IEs relating to the
capabilities of the multi-RAT MS.
BSS database
The BSS database is updated to allow the provisioning of UTRAN cells to be specified as
neighbours of existing GSM cells. The database also supports the configuration of new
parameters associated with the messaging to the multi-RAT MS.

3–76 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 2G–3G handovers using inter-radio access technology
System architecture
shows the system architecture for the GSM BSS inter-RAT handover feature.
Figure 3-56 GSM and UMTS system nodes and interfaces
E-Interface
GSM Core Network UMTS Core Network
(MSC/GSN) Gn-Interface (3G MSC/SGSN)
A-Interface Gb-Interface Iu-Cs-Interface
Iu-Ps--Interface
GSM/GPRS UTRAN
BSS PCU RNS RNS

Iur
RNC RNC
BSC
Iub Iub
Abis
BTS BTS Node B Node B
Um Uu
Multi-RAT MS
System considerations
Existing 2G core network (CN) nodes must be able to interact with the 3G CN nodes
through MAP procedures defined on the E-interface between a 2G CN node and 3G CN
node.
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 RELEASE
message.
S Blind search.
S The sending of SI2quater on extended BCCH.
S The BSS restricts the maximum number of UTRAN neighbours per GSM cell to
16.
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 unique
RNC-id and cell id combination within the BSS database.

30th Jun 02 68P02900W21-K 3–77
GMR-01
Call model parameters for capacity calculations GSM-001-103
Call model parameters for capacity calculations
Introduction
This section provides information on how to determine the number of control channels
required at a BTS.
This information is required for the sizing of the links to the BSC, and is required when
calculating the exact configuration of the BSC required to support a given BSS.
Typical call parameters

The number of control channels 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 P=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%
(continued)

3–78 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Call model parameters for capacity calculations
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 = 12
Coding scheme rates (CS1 to CS4) CS1 = 9.05 kbit/s
CS2 = 13.4 kbit/s
CS3 = 15.6 kbit/s
CS4 = 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), the
ratio of IMSI detaches to calls (I) and whether the short message sequence (type 1) or
long message sequence (type 2) is used for IMSI detach; typically I = 0 (that is IMSI
detach is disabled) as in the first formula given below. When IMSI detach is enabled, the
second or third of the formulas given below should be used. The type of IMSI detach
used is a function of the MSC.
If IMSI detach is disabled:
L=I
If IMSI detach type 1 is enabled:
L = I + 0.2 * I
L = I + 0.5 * I

30th Jun 02 68P02900W21-K 3–79
GMR-01
Control channel calculations GSM-001-103
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. As

PCCCH is not allocated, the information for packet switched
operation 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 several
PDTCHs.
– 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 the
first GPRS release.
– Packet Paging CHannel
Downlink 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 several
PDTCHs, 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 physical
channel 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 transceiver
uses these bursts to estimate the timing advance for an MS when it is in
transfer state.
– Packet Timing advance Control CHannel (PTCCH/D)
Downlink channel, used to transmit timing advance updates to several MSs
at the same time.

3–80 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Control channel calculations
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 requirements
with the GPRS signalling requirements in order to plan the appropriate level of control
channel support. This planning guide provides the planning rules that enable the network
planner to evaluate whether a combined BCCH can be used, or if a non-combined BCCH
is required. The decision to use a non-combined BCCH is a function of the combined
GPRS and GSM signalling load on the PAGCH, and on the number of SDCCH channels
required to support the GSM circuit-switched traffic.
The use of a combined BCCH is desirable because it may permit the use of only one
timeslot on a carrier that is used for signalling. A combined BCCH can offer four more
SDCCH blocks for use by the GSM circuit-switched signalling traffic. If more than an
average of three CCCH blocks, or more than four SDCCH blocks, are required to handle
the signalling load, more control channel timeslots are required.
The planning approach for GPRS/GSM control channel provisioning is to determine
whether a combined BCCH is possible, given the combined GPRS and GSM load on the
CCCH control channel. When more than three and less than nine CCCH blocks are
required to handle the combined load, the use of a combined BCCH is not possible.
When more than nine CCCH blocks are needed, one or more timeslots are required to
handle the CCCH signalling. In this case, it may be advantageous to use a combined
BCCH again, depending on the CCCH and SDCCH load.
The determination of how many CCCH and SDCCH blocks are required to support the
circuit-switched GSM traffic is deferred to the network planning that is performed with the
aid of the relevant planning information for GSM. The network planning that is performed
using the planning information determines how many CCCH and SDCCH blocks are
required, and subsequently how many timeslots in total, are required to support the
CCCH and SDCCH signalling load.
Downlink control channels

The downlink control channels are FCCH, SCH, BCCH and PAGCH. The PAGCH
consists of paging messages and access grant messages. The downlink control channel
load is determined by evaluating the combined GSM circuit-switched signalling traffic
load and the GPRS signalling traffic load on the PAGCH.
Uplink control channel

The uplink control channel is the random access channel (RACH). It is assumed that by
adequate provisioning of the downlink part of the CCCH, the uplink part is implicitly
provisioned with sufficient capacity.

30th Jun 02 68P02900W21-K 3–81
GMR-01
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 information
uses the SDCCH.

3–82 68P02900W21-K 30th Jun 02
GMR-01
Number of CCCHs per BTS cell

The following factors should be considered when calculating the number of CCCHs per
BTS cell:
S The CCCH channels comprise the paging and access grant channel (PAGCH) in
the downlink, and the random access channel (RACH) in the uplink. The PAGCH
is subdivided into access grant channel (AGCH) and paging channel (PCH).
S If the CCCH has a low traffic requirement, the CCCH can share its timeslot with
SDCCHs (combined BCCH). If the CCCH carries a high traffic, a non-combined
BCCH must be used:
– Combined BCCH (with four 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 control
channels (in addition to the mandatory BCCH on timeslot 0). These additional
CCCH control channels are added, in order, on timeslots 2, 4, and 6 of the BCCH
carrier, thus creating cells with 18, 27, and 36 CCCH blocks. These configurations
would only be required for very high capacity cells or in large location areas with a
large number of pages.
S Each CCCH block can carry one message. The message capacity of each CCCH
block is 4.25 messages/second.
S The AGCH is used to send immediate assignment and immediate assignment
reject messages for GSM and GPRS MSs. Each AGCH immediate assignment
message can convey channel assignments for up to two MSs. Each AGCH
immediate assignment reject message can reject channel requests from up to four
MSs.
S The PCH is used to send GSM and GPRS paging messages. Each PCH paging
message can contain pages for up to four MSs using TMSI or two MSs using
IMSI. If no paging messages are to be sent in a particular CCCH block, then an
immediate assignment/immediate assignment reject message can be sent instead.
The current Motorola BSS implementation applies the following priority (highest to
lowest) for downlink CCCH messages:
– Paging message (if not reserved for AGCH).
– Immediate assignment message.
– Immediate assignment reject message.
Thus, for example, if for a particular PAGCH sub-channel there are always paging
messages (that is high paging load) waiting to be sent, no immediate assignment
or immediate assignment reject messages will be sent on that PAGCH
sub-channel. Hence the option to reserve CCCH channels for AGCH.

30th Jun 02 68P02900W21-K 3–83
GMR-01
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 group
and only needs to listen to the PCH sub-channel corresponding to that
group. Paging group size is a trade off between MS idle-mode battery life
and speed of access (for example, a lot of paging groups, means the MS
need only listen very occasionally to the PCH, but as a consequence it takes
longer to page that MS, resulting in slower call set-up as perceived by a
PSTN calling party).
– Number of repetitions for MSs attempting to access the network on the
RACH.
– Time MS must wait between repetitions on the RACH.
S Precise determination of the CCCH requirements may be difficult. However, a
number of statistics can be collected (for example ACCESS_PER_PCH,
ACCESS_PER_AGCH) by the BSS and these may be used to determine the
CCCH loading and hence perform adjustments.
Calculate the number of CCCHs per BTS cell

The provisioning of the PAGCH is estimated by calculating the combined load from the
GPRS pages, GSM pages, GPRS access grant messages and GSM access grant
messages. The calculation is performed by adding the estimated GPRS and GSM paging
blocks for the BTS cell to the estimated number of GPRS and GSM access grant blocks
for the BTS cell, and dividing that sum by the CCCH utilization factor. The blocking factor
and Erlang B table are then used to provide the number of CCCHs required.
NOTE Introducing the GPRS feature into a cell may cause noticeable
delays for paging in that cell. Similarly, a cell in a heavy paging
environment may be unable to support GPRS unless the paging
parameters for that cell are updated. Motorola advises operators
to re-check the NPAGCH and NPCH equations provided here when
adding GPRS to a cell.

3–84 68P02900W21-K 30th Jun 02
GMR-01
The following planning actions are required:

S Determine the number of CCCHs per BTS.
The average number of blocks required to support AGCH and PCH is given by:
N PAGCH = (NAGCH + N PCH) 1

UCCCH
The average number of blocks required to support AGCH only is given by:
N AGCH + NAGCH_GSM ) NAGCH_GPRS
The average number of blocks required to support AGCH for GSM traffic is given
by:
l AGCH
N AGCH_GSM +
2 * 4.25
The average number of blocks required to support AGCH for GPRS traffic is given
by:
RACH_Arrivals_per_sec * 1.1
N AGCH_GPRS +
4.25
Where:
RACH_Arrivals_per_sec + GPRS_Users * Avg_Sessions_per_user
The access grant rate is given by:
l AGCH + lcall ) lL ) lS ) l LCS
The call rate (calls per hour) is given by:
l call + e
T
The location update rate (LU per hour) is given by:
lL + L * e
T
The SMS rate (SMSs per hour) is given by:
lS + S * e
T
The LCS rate (LCSs per hour) is given by:
l LCS + L CS * e
T
The average number of blocks required to support PCH only is given by:
N PCH + NPCH_GPRS ) NPCH_GSM
The average number of blocks required to support GSM CS traffic TMSI paging
only is given by:
PGSM * (1 ) L CS * LR MT)
N PCH_GSM +
4 * 4.25
The average number of blocks required to support GSM CS traffic IMSI paging
only is given by:
PGSM * (1 ) L CS * LR MT)
N PCH_GSM +
2 * 4.25
The number of paging blocks required at a cell to support GPRS is given by:
RACH_Arrivals_per_sec * 1.2
N PCH_GPRS +
4.25

30th Jun 02 68P02900W21-K 3–85
GMR-01
Where: UCCCH is: the CCCH utilization.

lAGCH the access grant rate (per
second).
GPRS_Users the number of GPRS users on a
cell.
Avg_Sessions_per_user the average number of sessions
originated by user (this includes
the sessions for signalling).
P the paging rate per second.
lcall the call arrival rate per second.
lL the location update rate per
second.
lS the number of SMSs per second.
e the number of Erlangs per cell.
T the average call length, in
seconds.
PGSM the number of GSM circuit
switched traffic pages transmitted
to a BTS cell per second.
PGPRS the number of GPRS pages
transmitted to a BTS cell per
second.
Table 3-7 Control channel configurations

Timeslot 0 Other timeslots Notes
1 BCCH + 3 CCCH N x 8 SDCCH One combined BCCH. The other timeslot
+ 4 SDCCH may or may not be required, depending on
the support of circuit-switched traffic
where 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, Non-combined BCCH. This is an example
9 CCCH of one extra timeslot of CCCHs added in
support of GPRS traffic. The value of N is
>= 1.

3–86 68P02900W21-K 30th Jun 02
GMR-01
Number of SDCCHs per BTS cell

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

30th Jun 02 68P02900W21-K 3–87
GMR-01
Calculate the number of SDCCHs per BTS cell

S Determine the number of SDCCHs per BTS.
The average number of SDCCHs is given by:
N SDCCH = lcall * T c ) lLU * ǒT L ) T gǓ ) l S * ǒT S ) T gǓ ) l LCS * ǒT LCS ) T gǓ
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 service
set-up).
lLCS the number of LCSs per second.
TLCS the time duration of LCS (location service
set–up).

3–88 68P02900W21-K 30th Jun 02
GMR-01
Control channel configurations

Table 3-8 and Table 3-9 give typical control channel configurations based on the typical
BTS 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 to
calls is 2.
Table 3-8 SDCCH planning for typical parameters (non-border location area)
Number Number Number Number Timeslot utilization
of of of of
RTFs TCHs Erlangs 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 8 SDCCH
+ 4 SDCCH
5 38 29.2 12 1 BCCH + 3 CCCH 8 SDCCH
+ 4 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 61 50.6 20 1 BCCH + 3 CCCH 2 x 8 SDCCH
+ 4 SDCCH
9 69 58.2 20 1 BCCH + 3 CCCH 2 x 8 SDCCH
+ 4 SDCCH
10 77 65.8 20 1 BCCH + 3 CCCH 2 x 8 SDCCH
+ 4 SDCCH
NOTE The CBCH reduces the number of SDCCHs by one and may
require another channel.

30th Jun 02 68P02900W21-K 3–89
GMR-01
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 is
7.
Table 3-9 SDCCH planning for typical parameters (border location area)
Number Number Number Number Timeslot utilization
of of of of
RTFs TCHs Erlangs 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 8 SDCCH
+ 4 SDCCH
3 21 14.0 16 1 BCCH + 9 CCCH 2 x 8 SDCCH
4 29 21.0 20 1 BCCH + 3 CCCH 2 x 8 SDCCH
+ 4 SDCCH
5 36 27.3 24 1 BCCH + 9 CCCH 3 x 8 SDCCH
6 44 34.7 28 1 BCCH + 3 CCCH 3 x 8 SDCCH
+ 4 SDCCH
7 51 41.2 36 1 BCCH + 3 CCCH 4 x 8 SDCCH
+ 4 SDCCH
8 59 48.7 36 1 BCCH + 3 CCCH 4 x 8 SDCCH
+ 4 SDCCH
9 66 55.3 40 1 BCCH + 9 CCCH 5 x 8 SDCCH
10 74 62.8 44 1 BCCH + 3 CCCH 5 x 8 SDCCH
+ 4 SDCCH

3–90 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GPRS traffic planning
GPRS traffic planning
Determination of expected load

The planning process begins by determining the expected GPRS load (applied load) to
the system. The next step is to determine the effective load to the system by weighting
the applied load by network operating parameters. These parameters consist of the
expected BLock Error Rate (BLER) based on the cell RF plan, the protocol overhead
(GPRS protocol stack, that is TCP/IP, LLC, SNDCP, RLC/MAC), the expected advantage
from V.42bis compression and TCP/IP header compression, and the multislot operation
of the mobiles and infrastructure.
The effective load at a cell is used to determine the number of GPRS timeslots required
to provision a cell. The provisioning process can be performed for a uniform load
distribution across all cells in the network or on an individual cell basis for varying GPRS
cell loads. The number of GPRS timeslots is the key piece of information that drives the
BSS provisioning process in support of GPRS.
The planning process also uses network generated statistics, available after initial
deployment, for replanning a network. The statistics fall into two categories: PCU specific
statistics, and GSN (SGSN + GGSN) statistics.
Network planning flow

The remaining sections of this chapter are presented in support of the GPRS network
planning:
S GPRS network traffic estimation and key concepts
This text is intended to introduce the key concepts involved in planning a network.
Because GPRS introduces the concept of a switchable timeslot that can be shared
by both the GSM circuit-switched infrastructure and by the GPRS infrastructure,
much of the following text is dedicated to the discussion of this topic.
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 table
of inputs. A key piece of information that is needed for the planning process is the
RF cell plan. This subsection discusses the impact of different cell plans on the
GPRS provisioning process, and how to use this information in order to determine
the number of GPRS timeslots that are required on a per cell basis.

30th Jun 02 68P02900W21-K 3–91
GMR-01
GPRS network traffic estimation and key concepts GSM-001-103
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 circuit
switched networks. One of the fundamental reasons for the difference is that a GPRS
network allows the queuing of data traffic instead of blocking a call when a circuit is
unavailable. Consequently, the use of Erlang B tables for estimating the number of trunks
or timeslots required is not a valid planning approach for the GPRS packet data
provisioning process.
The GPRS traffic estimation process starts by looking at the per cell GPRS data traffic
profile such as fleet management communications, E-mail communications, web
browsing, and large file transfers. Once a typical data traffic profile mix is determined, the
required network throughput per cell can be calculated as measured in kbits per second.
The desired network throughput per cell is used to calculate the number of GPRS
timeslots required to support this throughput on a per cell basis.
The estimated GPRS network delay is derived based on computer modelling of the delay
between the Um interface and the Gi interface. The results are provided in this planning
guide. The network delay can be used to determine the mean or average time it takes to
transfer a file of arbitrary length. In order to simulate the delay, the following factors are
considered:
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.

3–92 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GPRS network traffic estimation and key concepts
Use of timeslots
The use of timeslots for GPRS traffic is different from how they are used in the GSM
circuit-switched case. In circuit-switched mode, an MS is either in idle mode or dedicated
mode. In dedicated mode, a circuit is assigned through the infrastructure, whether or not
a subscriber is transporting voice or data. In idle mode, the network knows where the MS
is, but there is no circuit assigned. In GPRS mode, a subscriber uses the infrastructure
timeslots for carrying data only when there is data to be sent. However, the GPRS
subscriber can be attached and not sending data, and this still presents a load to the
GSN part of the GPRS system, which must be accounted for when provisioning the
GPRS infrastructure, that is, in state 2 as explained below.
The GPRS mobile states and conditions for transferring between states are provided in
Table 3-10 and shown in Figure 3-58 in order to specify when infrastructure resources
are being used to transfer data. The comment column specifies what the load is on the
infrastructure equipment for that state, and only in state 3 does the infrastructure
equipment actually carry user data.
The infrastructure equipment is planned such that many more MSs can be attached to
the GPRS network, that is in state 2, than there is bandwidth available to simultaneously
transfer data. One of the more significant input decisions for the network planning
process is to determine and specify how many of the attached MSs are actively
transmitting data in the Ready state 3. In the Standby state 2, no data is being
transferred but the MS is using network resources to notify the network of its location.
The infrastructure has equipment limits as to how many MSs can be in state 2. When the
MS is in state 1, the only required infrastructure equipment support is the storage of MS
records in the HLR.
Network provisioning requires planning for traffic channels and for signalling channels,
also referred to as control channels. The BSS GSR 4.1 release (or higher) combines the
circuit-switched and GPRS control channels together as BCCH/CCCH. This chapter
provides planning information for determining the BCCH/CCCH control channel capacity
needed.

30th Jun 02 68P02900W21-K 3–93
GMR-01
Table 3-10 MM state model of MS

Present Present Next state Condition for Comments
state # state state transfer (present state)
1 IDLE READY(3) GPRS Attach Subscriber is not
monitored by the
infrastructure, that is not
attached to GPRS MM,
and therefore does not
load the system other
than the HLR records.
2 STANDBY READY(3) PDU Transmission Subscriber is attached to
GPRS MM and is being
actively monitored by the
infrastructure, that is MS
and SGSN establish MM
context for subscriber
IMSI, but no data
transmission occurs in
this state.
3 READY IDLE(1) GPRS Detach Data transmission
through the infrastructure
occurs in the Ready state
3 READY STANDBY(2) Ready timer expiry The ready timer (T3314)
or default time is 32
seconds. The timer value
force to Standby can be modified during
(The network or the the signalling process by
MS can send a MS request.
GMM signalling 2 – 60 s in 2 s increments
message to invoke
force to Standby.) or
61 – 1800 s in 60 s
increments.

3–94 68P02900W21-K 30th Jun 02
GMR-01
The MS and SGSN state models are illustrated in Figure 3-58.
Figure 3-58 MM state models for MS and SGSN
IDLE IDLE
GPRS Detach
GPRS Attach GPRS Detach GPRS Attach or
Cancel Location
STANDBY timer READY

expiry READY STANDBY timer expiry
or
Cancel Location
PDU transmission READY timer expiry

READY timer expiry
or PDU reception
or
Force to STANDBY
Force to STANDBY or
Abnormal RLC condition
STANDBY STANDBY
MM State Model of MS MM State Model of SGSN

30th Jun 02 68P02900W21-K 3–95
GMR-01
Dynamic timeslot mode switching

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

3–96 68P02900W21-K 30th Jun 02
GMR-01
Background and discussion

From GSR6 onwards, multiple carriers per cell can be configured with GPRS timeslots by
the operator for GPRS traffic handling capability. By doing so, it can meet the expanding
base 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 network
with the capability to configure all the reserved and switchable GPRS timeslots in a
cell contiguously to maximize performance. The contiguous GPRS timeslots
configured on a carrier in a cell provide ease in scheduling packet data and the
capability to service multiple timeslot GPRS mobiles.
2. Operator specified.
This provides the customer with the flexibility to configure reserve and switchable
GPRS timeslots on a per carrier basis in a cell.
The carrier with GPRS timeslots can also be the BCCH/CCCH carrier or not, which is
determined 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 GPRS
timeslots.
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. The
sum of reserved and switchable GPRS timeslots should not exceed 30.
When configuring timeslots in a cell, carriers with 32K TRAU enabled with higher priority
when configuring GPRS timeslots. The only exception to this rule is when the
use_bcch_for_gprs elements is set to 2, in which case the BCCH carrier will be the first
carrier in the cell configured with GPRS timeslots.
Reserved GPRS timeslots are placed above the switchable GPRS timeslots on the air
interface TDMA frame.
The GPRS carriers can be provisioned to carry a mix of circuit-switched traffic and GPRS
traffic. There are three provisioning choices combined with timeslot configuration options
selected above:
• Reserved GPRS timeslots allocated only for GPRS use.
• Switchable timeslots dynamically allocated for either GSM circuit-switched traffic or
GPRS traffic (designated as switchable timeslots by Motorola).
• Remaining timeslots on the carrier with GPRS timeslots, if any, only for
circuit-switched use.

30th Jun 02 68P02900W21-K 3–97
GMR-01
Planning Goals – reserved vs switchable timeslots

The network planner may have some of the following network planning goals in mind
when trying to determine when to use reserved timeslots versus when to use
switchable 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 GPRS
throughput when the voice busy hour and the GPRS busy hour do not coincide.
S Use switchable timeslots to provide higher GPRS throughput without increasing
the circuit-switched blocking rate.
If all the GPRS timeslots are provisioned as switchable, the last available timeslot
is not given to a circuit-switched call until transmission of all the GPRS traffic on
that last timeslot is completed. Therefore, there is a circuit-switched blocking on
that last timeslot on the cell until the timeslot becomes free.
S Use switchable timeslots to provide some GPRS service coverage in low GPRS
traffic volume areas.
S Use switchable timeslots to provide extra circuit-switched capacity in spectrum
limited areas.
In order to make the decision on how to best allocate reserved and switchable
timeslots, the network planner needs to have a good idea of the traffic level for both
services. The proposal in this planning guide is to drive the allocation of switchable
timeslots and reserved GPRS timeslots from a circuit-switched point of view.
Start by looking at the circuit-switched grade of service objectives and the busy hour
traffic level, as measured in Erlangs. Once the circuit-switched information is known, the
potential impact on switchable timeslots can be analysed. The GPRS quality of service
can be planned by counting the number of available reserved GPRS timeslots, and by
evaluating the expected utilization of the switchable timeslots by the circuit-switched
part of the network during the GPRS busy hour.

3–98 68P02900W21-K 30th Jun 02
GMR-01
Carrier timeslot allocation examples

The following configuration examples explore different ways to configure timeslots in a
cell.
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.
Example 1
There are 15 switchable GPRS timeslots and 10 reserved GPRS timeslots in a 5 carrier
cell and the use_bcch_for_gprs = 2. The GPRS timeslots are configured contiguously
for 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 equipping
GPRS timeslots due to use_bcch_for_gprs being set to 2. After the BCCH carrier has
been allocated, the BTS first chooses non-BCCH carriers with 32K TRAU enabled to be
used for GPRS traffic and allocates as many GPRS timeslots as possible (up to 8).
Reserved GPRS timeslots are allocated before switchable GPRS timeslots, as described
previously.
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
Example 2
for performance.
In this example, the BCCH carrier is not preferred to be used as the first carrier for
GPRS traffic due to use_bcch_for_gprs being set to 1. So TS2 to TS7 on the BCCH
carrier is allocated to circuit switch TCH only. Then the BTS first chooses non-BCCH
carriers with 32K TRAU enabled to be used for GPRS traffic and allocates as many
GPRS timeslots as possible (up to 8).
previously.
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

30th Jun 02 68P02900W21-K 3–99
GMR-01
Example 3
cell. 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 GPRS
traffic due to use_bcch_for_gprs being set to 0. So TS2 to TS7 on the BCCH carrier is
allocated to circuit switch TCH only. Then the BTS first chooses non-BCCH carriers with
32K TRAU enabled to be used for GPRS traffic and allocates as many GPRS timeslots
as possible on these carriers. GPRS timeslots allocated on each carrier are in the range
between min_gprs_ts_carrier and max_gprs_ts_carrier.
previously.

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
Example 4
cell. 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”.
previously.

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 T T S S S S

3–100 68P02900W21-K 30th Jun 02
GMR-01
Example 5
There are 8 switchable GPRS timeslots and 4 reserved GPRS timeslots in a 5 carrier cell
and 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 has
32K TRAU enabled.
GPRS timeslots due to use_bcch_for_gprs being set to 2 and the GPRS timeslots
allocated on the BCCH carrier must be between the min_gprs_ts_carrier and
max_gprs_ts_carrier values. Then the BTS chooses non-BCCH carriers with 32K
TRAU enabled to be used for GPRS traffic and allocates as many GPRS timeslots as
possible on these carriers. GPRS timeslots allocated on each carrier are in the range
between 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 between
min_gprs_ts_carrier and max_gprs_ts_carrier.
previously.

BCCH 32K B SD T T R R R R
Example 6
There are 8 switchable GPRS timeslots and 4 reserved GPRS timeslots in a 5 carrier cell
and 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”.
previously.

Non-BCCH 32K T T T T R R R R
Non-BCCH 32K T T T T S S S S

30th Jun 02 68P02900W21-K 3–101
GMR-01
Example 7
for performance, which means allocating as many GPRS timeslots as possible (up to 8)
on non-BCCH carriers. The BCCH carrier has 32K TRAU enabled.
GPRS timeslots due to use_bcch_for_gprs being set to 2. After the BCCH carrier has
been allocated, the BTS first chooses non-BCCH carriers with 32K TRAU enabled to be
used for GPRS traffic and allocates as many GPRS timeslots as possible (up to 8) on
these carriers.
previously.

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
Non-BCCH 16K T T T T T T T T

3–102 68P02900W21-K 30th Jun 02
GMR-01
BSS timeslot allocation methods

The BSS algorithm that is used in order to determine allocation of switchable timeslots
gives priority to circuit-switched calls. Consequently, if a switchable timeslot is being used
by a GPRS mobile and a circuit-switched call is requested after all other circuit switched
timeslots are used, the BSS takes the timeslot away from the GPRS mobile and gives it
to the circuit-switched mobile, except when the switchable timeslot to be stolen is the last
GPRS 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 circuit
switched call ends. The number of reserved GPRS timeslots can be changed by the
operator in order to guarantee a minimum number of dedicated GPRS timeslots at all
times. The operator provisions the GPRS timeslots on a carrier by selecting the number
of timeslots that are allocated as reserved and switchable, and not by specifically
assigning timeslots on the carrier.
Motorola has implemented an idle circuit-switched parameter that enables the operator to
strongly favour circuit-switched calls from a network provisioning perspective. By setting
the idle parameter to 0, this capability is essentially turned off.
The use of the idle circuit-switched parameter is as follows:
When a circuit-switched call ends on a switchable GPRS timeslot and the number of idle
circuit-switched timeslots is greater than an operator defined threshold, the BSS
re-allocates the borrowed timeslot for GPRS service. When the number of idle timeslots
is less than or equal to a programmable threshold, the BSS does not allocate the timeslot
back for GPRS service, even if it is the last available timeslot for GPRS traffic.
Stolen timeslots
A switchable timeslot can be “stolen” at any time for use by a CS call, except when the
switchable timeslot to be stolen is the last GPRS timeslot in the cell and the
protect_last_ts element is enabled.
When a switchable timeslot needs to be stolen for use by a CS call, the switchable
timeslot to be stolen is the last GPRS timeslot in the cell, and the protect_last_ts
element is enabled, the timeslot will only be stolen if there is no data transfer active or
queued for the timeslot.
If there are any reserved GPRS timeslots in the cell, the switchable timeslots are not
protected from being stolen for use by circuit-switched calls.
The BSS supports dynamic switching between switchable timeslots and circuit-switched
timeslots and vice versa.
Switchable GPRS timeslots are stolen starting with the lowest numbered GPRS timeslot
on 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 carrier
does not contain RES GPRS timeslots).
contains RES GPRS timeslots).
does not contain RES GPRS timeslots).
contains RES GPRS timeslots).

30th Jun 02 68P02900W21-K 3–103
GMR-01
Contiguous timeslots
Multislot mobile operation requires that contiguous timeslots are available. The BSS
takes the lowest numbered switchable timeslot in such a manner as to maintain
contiguous GPRS timeslots for multislot GPRS operation. The BSS attempts to allocate
as many timeslots as requested in multislot mode, and then backoff from that number as
timeslots are not available. For example, suppose that timeslots 3 and 4 are switchable,
and timeslots 5,6, and 7 are GPRS reserved (see Figure 3-59). When the BSS needs to
re-allocate a switchable timeslot from GPRS mode to circuit-switched mode, the BSS
assigns timeslot 3 before it assigns timeslot 4 for circuit-switched mode.
Figure 3-59 provides a timeslot allocation with reserved and switchable timeslots.
Figure 3-59 Carrier with reserved and switchable GPRS timeslots
S S R R R
TS0 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 timeslot
that 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).

3–104 68P02900W21-K 30th Jun 02
GMR-01
Provisioning the network with switchable timeslots

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

30th Jun 02 68P02900W21-K 3–105
GMR-01
Timeslot allocation for 2 carrier site (1 circuit‘-switched + 1 GPRS)

Figure 3-60 shows one circuit-switched carrier with one BCCH/CCCH timeslot, one
SDCCH timeslot, and six TCH timeslots.
Figure 3-60 1 circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots
B SD
TS0 TS7
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 as
switchable.
Figure 3-61 One carrier, all timeslots (8 TCHs) designated as switchable
S S S S S S S S
TS0 TS7
S: Switchable TCH.

3–106 68P02900W21-K 30th Jun 02
GMR-01
Table 3-12 shows the switchable timeslot utilization.
Table 3-12 Switchable timeslot utilization

GOS Planned Total Number of Comments
circuit number of switchable
switched circuit timeslots
Erlangs/cell switched necessary
timeslots to provide
required, GOS
including
switchable
2% 2 6 0 Outside busy hour time
periods, the carrier most
likely carries only GPRS
traffic. Therefore, GPRS
network planning should
be performed, assuming
there are 8 timeslots
available for GPRS traffic.
0.1% 2 8 2 During circuit-switched
busy hour, at least 2 of the
switchable timeslots are
occasionally used by the
circuit-switched side of the
network in an attempt to
provide the best possible
GOS – assumed to be in
the order of 0.1%.
2% 3 8 2 During the circuit-switched
busy hour, 2 of the
provide the 2% GOS.
0.1% 3 10 4 During the circuit-switched
busy hour, 4 of the
provide the best possible
GOS – assumed to be in
the 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 switchable
timeslots are occasionally
used to provide the 0.1%
GOS.
(continued)

30th Jun 02 68P02900W21-K 3–107
GMR-01
GOS Planned Total Number of Comments

circuit number of switchable
switched circuit timeslots
Erlangs/cell switched necessary
timeslots to provide
required, GOS
including
switchable
2% 6 12 6
0.1% 6 15 9 There are not enough
switchable timeslots to
provide the 0.1% GOS.
2% 7 13 7
2% 8 14 8 All of the switchable
timeslots are occasionally
used to provide the 2%
GOS.
2% 9 15 9 There are not enough
provide the 2% GOS

3–108 68P02900W21-K 30th Jun 02
GMR-01
Recommendation for switchable timeslot usage

The following recommendation is offered when using switchable timeslots. It is important
to determine the GOS objectives for circuit-switched traffic and QoS objectives for GPRS
traffic prior to selecting the number of switchable timeslots to deploy.
During the circuit-switched busy hour, potentially all switchable timeslots are occasionally
used by the circuit-switched calls. The circuit-switched timeslot allocation mechanism
continues to assign switchable timeslots as circuit-switched timeslots as the
circuit-switched traffic continues to increase. Therefore, if there is a minimum capacity
requirement for GPRS services, the network planner should plan the carrier with enough
reserved timeslots in order to handle the expected GPRS data traffic. This ensures that
there is a minimum guaranteed network capacity for the GPRS data traffic during the
circuit-switched busy hour.
During the circuit-switched off busy hours, the switchable timeslots could be considered
as available for use by the GPRS network. Therefore, in the circuit-switched off busy
hours, potentially all switchable timeslots could be available for the GPRS network traffic.
The BSS call statistics should be inspected to determine the actual use of the switchable
timeslots by the circuit-switched services.
The circuit-switched busy hour and the GPRS busy hour should be monitored to see if
they overlap when switchable timeslots are in use. If the busy hours overlap, an
adjustment may be needed to the number of reserved timeslots allocated to the GPRS
portion of the network in order to guarantee a minimum GPRS quality of service as
measured by GPRS throughput and delay. Furthermore, one or more circuit-switched
carriers may need to be added to the cell being planned or replanned so that the
switchable timeslots are not required in order to offer the desired circuit-switched grade
of service.
In conclusion, assume switchable timeslots are occasionally unavailable for GPRS traffic
during the circuit-switched portion of the network busy hour. Provision enough reserved
timeslots for GPRS traffic during the circuit-switched busy hour to meet the desired
minimum GPRS quality of service objectives, as measured by GPRS data throughput.

30th Jun 02 68P02900W21-K 3–109
GMR-01
Timeslot allocation process on carriers with GPRS traffic

The following process is proposed when determining how best to allocate GPRS
timeslots.
Step 1: Estimate reserved timeslot requirements

Determine how many reserved GPRS timeslots are needed on a per cell basis in order to
satisfy a GPRS throughput QoS. The GPRS reserved timeslots should equal the sum of
the active and standby timeslots that are allocated to a carrier.
Step 2: Allocate switchable timeslots

Determine how many reserved GPRS timeslots are needed on a per cell basis. The use
of switchable timeslots can potentially offer increased capacity to both the GPRS and
circuit–switched traffic if the traffic is staggered in time.
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 satisfy
the circuit switched GOS objectives and the timeslot requirement overlaps with the
number of reserved GPRS timeslots, consider adding another circuit-switched carrier to
the cell.
Step 4: Monitor network statistics

After deploying the GPRS timeslots on the cell, review the collected network statistics on
a continuous basis in order to determine whether the reserved GPRS timeslots,
switchable GPRS timeslots, and circuit-switched timeslots are truly serving the GOS and
QoS objectives. As previously discussed, the use of switchable timeslots can offer
network capacity advantages to both circuit-switched traffic and GPRS traffic as long as
the demand for these timeslots is staggered in time.

3–110 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 GPRS air interface planning process
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. If
network values are not available at the time a network is planned, typical or
recommended values are provided where appropriate. The minimum values are given for
the maximum capacity of a minimum system, and the typical values are used as
standard model parameters.
Table 3-13 Air interface planning inputs

Variable Minimum Typical Maximum Assumptions/ variable
value value value use
CS1 0% 10% 100 % Coding scheme
CS2 0% 50% 100 % percentages are
determined by the cell
CS3 0% 20% 100 % plan, mean TBF size and
CS4 0% 20% 100 % use of Acknowledge
mode. Refer to cell plan
Table 3-14, Table 3-15 and
Table 3-16.
After the initial launch, the
operator needs to collect
the percentage of time
each CS is used for all the
cells with GPRS capability,
and to adjust the system
planning accordingly as an
ongoing optimization
process.
V.42 bis 1 2.5 4 A ratio of 1 means there is
compression no compression and a ratio
ratio of 4 is the theoretical
maximum, which is most
likely never realized. Most
users see a compression
advantage in the range of 2
to 3 over the air interface
between the MS and the
SGSN.
BLER 0 10% 100% The BLock Error Rate
(BLER) is largely
determined by the cell RF
plan. The typical value is
an average rate. There are
separate BLERs for the
various coding schemes
that are RF plan specific.

30th Jun 02 68P02900W21-K 3–111
GMR-01
GPRS air interface planning process GSM-001-103
Estimating the air interface traffic throughput

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

The following steps 1 and 2 are used for dimensioning the system. Step 1 needs to be
performed prior to step 2 in order to calculate the number of GPRS timeslots that should
be provisioned on a per cell basis.
Steps 3 and 4 are optional. These steps are included in this section so that an over the
air file transfer time can be calculated for any size file. The results from steps 3 and 4
depend on the choices made in steps 1 and 2.

3–112 68P02900W21-K 30th Jun 02
GMR-01
Step 1: Choose a cell plan

Choose a cell plan in order to determine the expected BLER and percentage of time data
is transferred at the CS1, CS2, CS3 and CS4 rate. The cell plan that is chosen for GPRS
may be determined by the plan currently in use for the GSM circuit-switched part of the
network. However, it may be necessary to change an existing cell plan used for GSM
circuit-switched in order to get better BLER performance for the GPRS part of the
network.
After the cell plan is chosen, the network planner can move on to step 2.
The PCU dynamically selects the best CS rate in order to maximize the GPRS data
throughput on a per mobile basis. The CS rate selection is performed periodically during
the temporary block flow (TBF).
When planning frequency, it is required that there are no more than 48 frequencies in a
cell 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 is
hopping on 2 carriers over 6 frequencies), and results for a 1x1 cell reuse pattern with
2/18 hopping are shown in Table 3-15 (which is hopping on 2 carriers over 18
frequencies).
Results for a non-hopping cell configuration with a TU-3 model is shown in Table 3-16,
providing a chart of the cell coverage area and cell C/I performance for the non-hopping
case. The following tables were created, based on the simulations, in order to indicate
the percentage of the time a particular CS rate would be chosen over another CS rate
and at what mean BLER. The simulation results indicate that the higher data rate of the
CS4 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, better
throughput may be obtained by provisioning the GPRS timeslots on the BCCH carrier, as
indicated 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 cell
area coverage for the TU-3 model.

30th Jun 02 68P02900W21-K 3–113
GMR-01
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 the
allocation of frequencies. The computer simulation generated the above cell plan using a
typical urban 3 kph model, a propagation law with a Radius (R) exponent of –3.7 and a
shadowing function standard deviation of 5 dB.
NOTE The numbers shown in the above tables are for reference
purposes only. The operator should collect the usage figures of
each CS at all GPRS-enabled sites after the system launch and
adjust the planning accordingly.
The collection of CS usage information should be considered as
part of the ongoing system optimization process.
If non-regular patterns are used, a specific simulation study may be required to match the
particular cell characteristics. The simulation process is outside the scope of this planning
guide and the network planner should contact Motorola for additional simulation results.
Step 2: Estimate timeslot provisioning requirements

Step 2 determines the number of GPRS timeslots that need to be provisioned on a per
cell basis. Timeslot provisioning is based on the expected per cell mean GPRS traffic
load, as measured in kbit/s. The GPRS traffic load includes all SMS traffic routed through
the GSN. The SMS traffic is handled by the GPRS infrastructure in the same manner as
all other GPRS traffic originating from the PDN. The cell BLER and CS rate
characteristics chosen in step 1 provide the needed information for evaluating the
following equation:
No_PDCH_TS + Roundup ǊTS_Data_Rate

Mean_traffic_load
* Mean_load_factor
ǋ
NOTE The above equation is based on the DL traffic load and it is

assumed that the DL provisioning would be sufficient to handle
UL traffic, without additional provisioning.
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

3–114 68P02900W21-K 30th Jun 02
GMR-01
Where:
TS_Data_Rate + ƪ%CS1
100
* (1 * CS1BLER) * 9.05 * Ǌ1 * ǋƫ ) ƪ
3
23
%CS2
100
* (1 * CS2BLER) * 13.4 * Ǌ1 * ǋƫ
3
33
) ƪ%CS3
100
* (1 * CS3BLER) * 15.6 * Ǌ1 * ǋƫ ) ƪ
3
39
%CS4
100
* (1 * CS4BLER) * 21.4 * Ǌ1 * ǋƫ
3
53
and: Mean_traffic_load is: the mean traffic load, as measured

in kbit/s, is defined at the LLC layer,
therefore all the higher layer protocol
overheads (for example, TCP, UDP,
IP, SNDCP, LLC) are encapsulated
in this load figure.
No_PDCH_TS the number of timeslots per cell,
maximum 8.
%CS1 the percentage of time data
transmission occurs using the CS1
coding scheme.
CS1BLER the mean BLER rate for CS1.
coding scheme.
coding scheme.
coding scheme.
3/23 the CS1 RLC/MAC overhead
percentage, that is 20 bytes payload.
Mean_load_factor the mean load factor for the number
of active timeslots to provision at a
cell. The recommended value is 0.5
(50%) of the number of GPRS
timeslots provisioned at the cell.
Avg_Sessions_per_sub the number of average data
sessions originated by a MS in a cell
in a busy hour.
Data_per_sub_per_session the amount of data transmitted by a
MS in kbits per session.
GPRS_subs_per_cell the number of GPRS subscribers
under a cell in a busy hour.

30th Jun 02 68P02900W21-K 3–115
GMR-01
Number of timeslots
The number of PDCH timeslots calculated in step 2 denotes the number of timeslots that
need to be provisioned on the cell to carry the mean traffic load on the cell. The
Mean_load_factor of 50% has been applied to the traffic load to account for any surges in
the data traffic and to carry packet switched signalling traffic.
It is important to differentiate between the required number of timeslots processed at any
instance in time and the total provisioned timeslots because it directly affects the
provisioning of the communication links and the PCU hardware. The active timeslots are
timeslots that are simultaneously carrying data being processed by the PRP on the PCU
at any instance in time. From GSR6, however, it is possible to originate PS calls on each
of the 1080 timeslots simultaneously. The PCU will rapidly multiplex all the timeslots with
a maximum of 270 timeslots at any instance in time. For example, if there are MSs on
each of 1080 timeslots provisioned on the air interface, the PCU will process timeslots in
4 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 270
timeslots (assuming that all 9 PRPs are configured on the PCU) at any instance and the
other timeslots behaved as standby timeslots, from GSR6 onwards all timeslots can
potentially 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 by
the 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 enables
several cells to share the PCU resource. While one cell is experiencing a high load
condition, using all eight GPRS timeslots for instance, another cell operating below its
mean load averages out the GPRS traffic load at the PCU.
The E1s between the BTS and BSC must be provisioned to handle the number of
timeslots calculated above because all of the timeslots can become active under high
load conditions.

3–116 68P02900W21-K 30th Jun 02
GMR-01
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 be
used as an aid in determining the size of a file that is to be transferred as an LLC PDU
from the mobile to the SGSN.
The file size consists of the application file to be transferred, which includes any
application-related overhead. In addition to the application file, there is transport and
network layer protocol overhead, TCP and IP. Finally, there is GPRS link layer control
(LLC) and sub network convergence (SNDCP) protocol overhead. The application file
plus all of the protocol overhead summed together makes up the one or more LLC_PDU
frames that constitute the file to be transferred.
The percentage of protocol overhead depends on the transport layer used, such as TCP
or UDP. For example, the TCP/IP protocol overhead is 40 bytes when TCP/IP header
compression is not used. When TCP/IP header compression is used, the TCP/IP header
can be reduced to 5 bytes from 40 bytes after the first LLC frame is transferred. The use
of header compression continues for as long as the IP address remains the same.
Figure 3-62 illustrates a typical LLC_PDU frame with the user application payload and all
of the protocol overhead combined for the case of no TCP/IP header compression.
Figure 3-62 LLC_PDU frame layout
7 2 20 20 4
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 is
reduced by the data compression factor which can range from 1 to 4. Typically, V.42bis
yields a 2.5 compression advantage on a text file, and close to no compression
advantage (factor = 1) on image files and very short files:
File_size_LLC +
Appln
V.42bis_factor
) roundup Ǌ
Appln
V.42bis_factor * LLC_payload
* protocol_overhead ǋ
Where: File_size_LLC is: The file size in bytes to be
transferred, measured at the LLC
layer.
Appln The user application data file size,
measured in bytes.
LLC_payload The maximum LLC PDU payload of
1527 bytes.
protocol_overhead The protocol overhead for
TCP/IP/SNDCP/LLC/CRC is
53 bytes without header
compression, and 18 bytes with
header compression.
V.42bis_factor Application data compression is
over the range of 1 to 4, a typical
value is equal to 2.5.

30th Jun 02 68P02900W21-K 3–117
GMR-01
Step 3 example calculation

A 3 kbyte application file transfer requires the following number of bytes to be transferred
at the LLC_PDU layer:
Application = 3 kbytes.
Assume V.42bis_factor = 1, that is no application data compression.
No header compression:
File_size_LLC = 3000 + roundup (3000/1527) x 53 = 3106 bytes
With header compression:
The first LLC_PDU header is not compressed, and all subsequent LLC_PDUs are
compressed. For this size file of 3000 bytes, only 2 LLC_PDU transmissions are required
so the File_size_LLC is:
File_size_LLC = 3000 + 53+18 = 3071 bytes

3–118 68P02900W21-K 30th Jun 02
GMR-01
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 an
arbitrary size over the Um to Gi interface. The application file is segmented into LLC PDU
frames as illustrated previously. The File Transit Delay (FTD) is calculated using the
following information: total number of RLC blocks of the file, BLER, number of timeslots
used during the transfer, and mean RLC Transit Delay (RTD) value:
RLC_Blocks * 0.02 * (1 ) CSBLER)
FTD + RTD )
mslot
Where: FTD is: the file transit delay measured in seconds.

RTD the transit delay time from the Um interface to
the Gi interface for a file size of only one
RLC/MAC block of data. RTD is estimated to be
0.9 s when the system running at 50% capacity.
This parameter will be updated when field test
data is available.
RLC_Blocks the total number of RLC blocks of the file. This
can be calculated by dividing file_size_LLC by
the corresponding RLC data size of 20 bytes for
CS1, 30 bytes for CS2, 36 bytes for CS3 and
50 bytes for CS4.
mslot the mobile multislot operating mode; the value
can be from 1 to 4.
CSBLER the BLER for the specific CS rate. The value is
specified in decimal form. Typical values range
form 0.1 to 0.2.
The above equation does not include the effects of acknowledgement messages. The
reason is that the largest effect is in the uplink direction, and it is expected that the
downlink direction will dominate the cell traffic. The DL sends an acknowledgement
message on an as-needed basis, whereas the uplink generates an acknowledgement
message every 2 out of 12 RLC_Blocks. It is expected that the downlink
acknowledgement messages will not significantly effect the file transit delay in the
downlink direction.
The RTD parameter is directly correlated to the system utilization and the mean packet
size. When the cell approaches its throughput capacity limit, the RTD value increases
dramatically, and the infrastructure starts to drop packets. Simulation data indicates that
when traffic load is minimal, the RTD value is at a minimum limit of 0.7 seconds. At a cell
throughput capacity of 50%, the RTD increases to 0.9 seconds. It is recommended that
cell throughput provisioning be performed at the mean cell capacity level of 50%.
Provisioning for a mean cell throughput greater than 50% greatly increases the likelihood
of dropped packets, and RTD values of over 2.6 seconds can occur. The assumptions
used in the simulation to determine the RTD value at a mean cell throughput level of 50%
are: 25% of the cell traffic at the 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, mean
LLC_PDU packet size of 435 bytes.

30th Jun 02 68P02900W21-K 3–119
GMR-01
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 previous
example).
CS2 payload = 30 bytes.
Air time for one RLC/MAC = 0.02 seconds.
block
(1 + CSBLER) = 1.1.
Multislot operation = 1.

3–120 68P02900W21-K 30th Jun 02
GMR-01
GPRS data rates

NOTE This information is provided for reference only. It may be used to
calculated timeslot data rates at each layer, if required.
These are purely theoretical calculated values, based on the
protocol overheads at each layer. They do not necessarily
represent 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 the
GPRS 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 highly
variable 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, for
example) is considered insignificant.
S Increased efficiencies gained from lowered overhead as a result of using higher
numbers 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.

30th Jun 02 68P02900W21-K 3–121
GMR-01
Table 3-18 GPRS data rates (kbit/s) with UDP

Protocol CS1, 1 TS CS1, 2 TS CS1, 3 TS CS1, 4 TS
Stack
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

Stack
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

Stack
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

Stack
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

3–122 68P02900W21-K 30th Jun 02
GMR-01
Table 3-19 GPRS data rates (kbit/s) with TCP

Stack
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

Stack
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

Stack
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

Stack
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

30th Jun 02 68P02900W21-K 3–123
GMR-01

3–124 68P02900W21-K 30th Jun 02
GMR-01
Chapter 4
BTS planning steps and rules

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter provides the planning steps and rules for the BTS, including macrocell,
microcell and picocell. The planning steps and rules for the BSC are in Chapter 5, and
remote transcoder (RXCDR) are in Chapter 6 of this manual. This chapter contains:
S 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 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).

30th Jun 02 68P02900W21-K 4–1
GMR-01
BTS planning overview GSM-001-103
BTS planning overview
Introduction
To plan the equipage of a BTS site certain information must be known. The major items
include:
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 combining
method and antenna configuration provides sufficient output power. Alternatives
include changing combiner types or using more than one transmitting antenna.
Duplexers may be used to reduce the amount of cabling and the number of
antennas.
S 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 make
intelligent trade offs between fewer cabinets/enclosures initially and ease of
expansion later.
S Whether or not there are equipment shelters at the site.
Macro/micro/picocell outdoor equipments should be included in the BTS planning
for locations where there are no equipment shelters. Macro/micro/picocell should
be included where rooftop mounting or distributed RF coverage is required or
where space and access are restricted.
To plan the equipage of a PCC cabinet (M-Cellaccess) certain information must be
known. The major items include:
S 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.

4–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BTS planning overview
Outline of planning steps
Macrocell and microcell BTS sites

The information required for planning a macro/microcell BTS site is outlined in the
following 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 Microcell
enclosures.
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 base
control units.
9. The number of network interface units required, refer to the section Network
interface unit and site interconnection.
10. The number of E1/T1 links required, refer to the section Network interface unit
and 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 Cabinet
interconnection.
13. The power supply requirements, refer to the section Power requirements.
Picocell site
The information required for planning a picocell (macro/micro/picocell) site is outlined in
this chapter.

30th Jun 02 68P02900W21-K 4–3
GMR-01
Macrocell cabinets GSM-001-103
Macrocell cabinets
Horizonmacro
A Horizonmacro cabinet (indoor or outdoor) can support six carriers (CTUs). Expansion
beyond six carriers requires additional cabinets. The Horizonmacro 12 carrier outdoor is,
in effect, an outdoor enclosure which can accommodate either one or two indoor cabinets
for six or 12 carrier operation.
NOTE CCBs cannot be used with the Horizonmacro indoor cabinet if

the cabinet is to be installed in the 12 carrier outdoor enclosure.
Also, CCBs cannot be used with the GSM850 or PCS1900
Horizonmacro BTS variants.
All Horizonmacro cabinets/enclosures incorporate heat management systems. The

Horizonmacro outdoor can operate at ambient temperatures up to 50 _C. The
Horizonmacro 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 for
outdoor operation and consists of:
S The BTS unit. This is similar to Horizonmicro / Horizonmicro2 and is a two-carrier
cell with combining.
S The booster unit. This incorporates two Tx amplifiers, delivering 10 W (nominal) at
each 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 to
50 _C.
NOTE The main difference between the Horizoncompact and the

Horizoncompact2 is that the latter can be expanded to support
an additional two BTSs (requires GSR5 or later software).
For the purposes of this document, future references to
Horizoncompact2 also include Horizoncompact unless
specifically stated otherwise.
M-Cell6
The MCell6 cabinet can support six carriers (TCUs). Expansion beyond six carriers
requires additional cabinets. Outdoor cell sites are provided with an ancillary cabinet
and a side cabinet.
The M-Cell6 HMS offers the following options:
S Fans that circulate ambient air through the cabinet, for both indoor and outdoor
units.
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 cabinets
only.

4–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Macrocell cabinets
M-Cell2
An M-Cell2 cabinet can support two carriers (TCUs). Expansion beyond two carriers
requires additional cabinets.
The M-Cell2 outdoor cabinet accommodates all the elements in an indoor cabinet, in
addition, limited accommodation for LTUs and battery backup is provided. Cooling is
provided by a fan within the cabinet.
Unlike M-Cell6 outdoor cabinets where the antenna terminations are in a side cabinet,
M-Cell2 terminations are on the main cabinet.
The M-Cell2 HMS offers the following options:
S Fans that circulate ambient air through the cabinet, for both indoor and outdoor
units.
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 cabinets
only.

30th Jun 02 68P02900W21-K 4–5
GMR-01
Microcell enclosures GSM-001-103
Microcell enclosures
Horizonmicro and Horizonmicro2

The Horizonmicro / Horizonmicro2 is an integrated cell site, designed primarily for
outdoor operation and consists of a single small two carrier BTS unit.
The Horizonmicro / Horizonmicro2 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 to
50 _C.
NOTE The main difference between the Horizonmicro and the

Horizonmicro2 is that the latter can be expanded to support an
additional two BTSs (requires GSR5 software).
For the purposes of this document, future references to
Horizonmicro2 also include Horizonmicro unless specifically
stated otherwise.

4–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Receive configurations
Receive configurations
Introduction
The receiver equipment provides the termination and distribution of the received signals
from the Rx antennas. Receiver equipment is required for each Rx signal in every cabinet
or enclosure in which it is used. Each Rx antenna must terminate on a single cabinet or
enclosure. If the signal needs to go to multiple cabinets it will be distributed from the first
cabinet.
NOTE Horizonmicro2 is two carrier only, combined to a single antenna.
Horizoncompact2 is two carrier only, with two antennas. Two
versions of the Horizonmicro2 and Horizoncompact2 BTSs are
available. One version can operate on GSM900 frequencies and
the other can operate on DCS1800 frequencies.
The factors affecting planning for GSM900 and DCS1800 BTSs are provided in this
section.
NOTE Horizonmacro BTSs are also available for GSM850 or PCS1900
operation. The SURF and Tx blocks for these are modified for
operation in the appropriate frequency band.
All planning and operational aspects are the same as for the
900/1800 MHz Horizonmacros except that the SURFs are single
band only and GSR5.1 or higher is required.
GSM900
The following factors should be considered when planning the GSM900 receive
equipment:
S Horizonmacro BTSs require one 900 MHz SURF for each cabinet. This has dual
band (900/1800 Mhz) capability.
S Receive antennas can be extended across Horizonmacro cabinets by using the
900 SURF expansion ports to feed a SURF in another cabinet.
S M-Cell2 and M-Cell6 BTSs require one DLNB for each sector.
S Receive antennas can be extended across M-Cell6 cabinets by using the IADU
expansion ports to feed an IADU in another cabinet.
DCS1800
The following factors should be considered when planning the DCS1800 receive
equipment:
S Horizonmacro BTSs require one 1800 MHz SURF for each cabinet.
S Receive antennas can be extended across Horizonmacro cabinets by using the
1800 SURF expansion ports to feed a SURF in another cabinet.
NOTE Two types of 1800 SURF are available. One is 1800 MHz single
band and the other is 1800/900 MHz dual band.
S M-Cell2 and M-Cell6 BTSs require one LNA for each sector.
S Receive antennas can be extended across M-Cell6 cabinets by using the LNA
expansion ports to feed an LNA in another cabinet.

30th Jun 02 68P02900W21-K 4–7
GMR-01
Receive configurations GSM-001-103
Receiver planning actions

1. Determine the number of cells.
2. Determine number of cells which have CTUs/TCUs in more than one cabinet.
3. Determine the number of Rx antennas per cell supported in each cabinet.
4. Determine the type and quantity of receive equipment required.

4–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Transmit configurations
Transmit configurations
Introduction
The transmit equipment provides bandpass filtering and signal combining for the BTS
cabinets. For M-Cell2 and M-Cell6 cabinets, a TxBPF is required for each antenna.
NOTE Horizonmicro2 is two carrier only and these are combined to a
single antenna. Horizoncompact2 is two carrier only, with two
antennas.
The transmit configurations available for Horizonmacro, M-Cell2 and M-Cell6 BTSs are
listed in Table 4-1.
Table 4-1 Transmit configurations

Cabinet Transmit
Number Cabinet Transmit
Configurations
of Configurations Notes
Wide Band
Carriers Cavity Combining
Combining
1 1 DCF or TDF Not available Horizonmacro only
1 1 TxBPF Not available M-Cell2 and M-Cell6
2 1 DCF 1 CCB output Horizonmacro only
1 Hybrid combiner plus
2 1 CCB output M-Cell2 and M-Cell6
1 TxBPF
3 2 DCF or 1 DDF 1 CCB output Horizonmacro only
2 Hybrid combiner plus
3 1 CCB output M-Cell6 only
1 TxBPF
1 DDF and HCU 1 CCB output +
4 Horizonmacro only
1 CCB extension
2 Hybrid combiner plus 1 CCB output +
4 M-Cell6 only
1 TxBPF 1 CCB extension
2 DDF and Air 1 CCB output +
5 Horizonmacro only
1 CCB extension
5 M-Cell6 only
2 DDF and Air 1 CCB output +
6 Horizonmacro only
1 CCB extension
6 M-Cell6 only
NOTE A CCB output includes a TxBPF; a CCB extension does not.
Transmit planning actions

Determine the transmit equipment required.

30th Jun 02 68P02900W21-K 4–9
GMR-01
Antenna configurations GSM-001-103
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 (two
cabinets 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.

4–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Carrier equipment (transceiver unit)
Carrier equipment (transceiver unit)
Introduction
The transceiver unit for Horizonmacro is a CTU.
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 a
development 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 an SCU (in pre M-Cell equipment).
References to TCU in the text include TCU-B, except where stated otherwise.
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 in
the Control channel calculations section in Chapter 3, BSS cell planning in this
manual.
S Normally, one transceiver unit is required to provide each RF carrier.
S Include redundancy requirements. Redundancy can be achieved by installing
excess capacity in the form of additional transceiver units.
Transceiver planning actions

Determine the number of transceivers required.

30th Jun 02 68P02900W21-K 4–11
GMR-01
Micro base control unit (microBCU) GSM-001-103
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 Horizonmacro
Each Horizonmacro cabinet has a built-in digital module shelf. This provides the
Horizonmacro equivalent of M-Cell6 mBCU cage functionality.
The digital module shelf can be equipped for redundancy and/or additional E1/T1
link capacity.
S M-Cell6
Each M-Cell6 cabinet requires one mBCU cage.
Two mBCU cages can be equipped for redundancy and/or additional E1/T1 link
capacity.
S M-Cell2
The first M-Cell2 cabinet requires one mBCU2 cage.
Two mBCU2 cages can be equipped for redundancy and/or additional E1/T1 link
capacity.
Additional cabinets do not require mBCU2 cages.
MicroBCU planning actions

For M-Cell equipment, determine the number of mBCUs required.

4–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Network interface unit (NIU) and site connection
Network interface unit (NIU) and site connection
Introduction
The NIU provides the interface for the Horizonmacro or M-Cell2/6 BTS to the terrestrial
network.
NOTE M-Cellcity and M-Cellcity+ are fitted with a single NIU-m only.
The equivalent modules in Horizoncompact2 and Horizonmicro2
are RHINO/DINO.
The following factors should be considered when planning the NIU complement:
S The first NIU in a digital module shelf (Horizonmacro) or mBCU cage (M-Cell6) can
interface two E1/T1 links.
S The second NIU in a digital module shelf or mBCU cage can interface one E1/T1
link.
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 its
own equipment, and that of other sites which are connected to it by the drop and
insert (daisy chain) method.
– Two 64 kbit/s links are required for each active transceiver.
– A 64 kbit/s link is required for every RSL (LAPD signalling channel) to the
site. In the drop and insert (daisy chain) configuration, every site will require
its own 64 kbit/s link for signalling.
S Redundancy for the NIU module depends on the number of redundant E1/T1 links
running to the site.
S Plan for a maximum of two NIUs per digital module shelf or mBCU cage (three E1
or T1 links).
S Plan for a maximum of one NIU per mBCU2 cage for M-Cell2 cabinets (two E1 or
T1 links).

30th Jun 02 68P02900W21-K 4–13
GMR-01
Network interface unit (NIU) and site connection GSM-001-103
The minimum number of NIUs and mBCU cages required for a given number of E1/T1
links to a single M-Cell cabinet is shown in Table 4-2.
Table 4-2 Site connection requirements for M-Cell2 and M-Cell6

Number of Minimum Number of Notes
E1/T1 links number of NIU mBCU cages
required required
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 Horizonmacro.
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.

4–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Main control unit, with dual FMUX (MCUF)
Main control unit, with dual FMUX (MCUF)
Introduction
The MCUF provides the main site control functions for a Horizonmacro BTS site.
The following factors should be considered when planning the MCUF complement:
S Only the first cabinet requires an MCUF.
S An optional (PCMCIA) memory card may be installed for non-volatile code storage.
S For redundancy, add a second MCUF in the digital module shelf of the first
cabinet.
MCUF planning actions

Determine the number of MCUFs required.

30th Jun 02 68P02900W21-K 4–15
GMR-01
Main control unit (MCU) GSM-001-103
Main control unit (MCU)
Introduction
The MCU provides the main site control functions for M-Cell6 and M-Cell2 BTS sites.
The following factors should be considered when planning the MCU complement:
S Only the first cabinet requires an MCU.
S An optional (PCMCIA) memory card may be installed for non-volatile code storage.
S For redundancy add a second mBCU cage and MCU in the first cabinet.
MCU planning actions

Determine the number of MCUs required.

4–16 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Cabinet interconnection (FMUX/FOX)
Cabinet interconnection (FMUX/FOX)
Introduction
Horizonmacro
The FMUX multiplexes and demultiplexes full duplex transceiver links between an MCUF
and up to six CTUs.
M-Cell6 and M-Cell2

The FOX provides the bidirectional electrical to optical interface between an MCU or
FMUX and up to six TCUs.
The FMUX multiplexes and demultiplexes electrical connections for up to six TCUs onto
a single fibre optic connection operating at the rate of 16.384 Mbit/s.
Horizonmacro
The following factors should be considered when planning the FMUX complement:
S An FMUX is not required in the master cabinet for two or three cabinet
configurations (see Table 4-3).
S A fourth Horizonmacro cabinet requires one FMUX plus one FMUX in the master
cabinet (see Table 4-3).
S Redundancy requires duplication of an FMUX and associated MCUF.
Table 4-3 Horizonmacro FMUX 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 plus
one FMUX in the first cabinet.
S Redundancy requires duplication of all FOX and FMUX boards and associated
MCU and mBCU cages.

30th Jun 02 68P02900W21-K 4–17
GMR-01
Cabinet interconnection (FMUX/FOX) GSM-001-103
FMUX/FOX planning actions
Horizonmacro
Determine the number of FMUXs required.
M-Cell6 and M-Cell2

Determine the number of FOX/FMUXs required.

4–18 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Power requirements
Power requirements
Introduction
Macrocell cabinets and Microcell enclosures can operate from a variety of power
supplies.
The following factors should be considered when planning the power supply
requirements:
S 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 carrier

outdoor.
S Horizonmicro2 and Horizoncompact2

The Horizonmicro2 and Horizoncompact2 enclosures operate from a 88 to 265 V
ac 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 or
230 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 ac
power source.
Power planning actions

Determine the power supply required.

30th Jun 02 68P02900W21-K 4–19
GMR-01
Network expansion using macro/micro/picocell BTSs GSM-001-103
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. The
Network topology can be any of those specified in Chapter 2 of this manual. A
macro/micro/picocell BTS may occupy any position in a network.
Expansion considerations
The following factors should be considered when expanding an existing network using
macro/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 BTS
are given in Table 4-2 of this chapter.
S The rules governing the number of MSIs required at the BSC are given in the
Multiple 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 appropriate
modules until the cabinets are full.
2. To further expand a previous generation site, the equipment in the previous
generation cabinet must be re-configured so that it serves a complete set of
sectors in the target configuration.
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 to
the existing site.
5. Customers who have not purchased the daisy chaining feature should order the
free of charge feature M-Cell – InCell Interworking, SWVN2460, to obtain a
suitable licence for upgrading.
Example
To upgrade a BTS6 2/2/2 to a 3/3/3, reconfigure the BTS6 to a 3/3, order an M-Cell omni
3 and install it to serve the third sector.

4–20 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 PCC cabinet
PCC cabinet
Introduction
Each PCC cabinet (M-Cellaccess) can support up to two sites (one cage = one site); and
up to a maximum of six carriers (PCU enclosures) per site.
If a mix of 900 MHz and 1800 MHz equipments are required, then one shelf must be
used for each frequency.
XCDR/GDP options can be planned for the lower BSU shelf only, refer to Chapter 5, BSC
planning steps and rules and Chapter 6, RXCDR planning steps and rules.
Cabinet planning actions

S Determine the number of sites required.
S Determine the mix of frequencies.
S Determine the method of PCU/PCC interconnection.

30th Jun 02 68P02900W21-K 4–21
GMR-01
Line interface modules (HIM-75, HIM-120) GSM-001-103
Line interface modules (HIM-75, HIM-120)
Introduction
The line interface modules, HDSL interface module, 75 ohm (HIM-75), and HDSL
interface module, 120 ohm (HIM-120), provide impedance matching for E1, T1 and
HDSL links.
The following factors should be considered when planning the line interface complement:
S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1
1.544 Mbit/s) 3 V (peak pulse) line use a HIM-120.
S To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak
pulse) 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 12
HDSL 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.
Number of PCUs
Minimum number of HIM–75s or HIM–120s =
2

4–22 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 DRI/Combiner operability components
DRI/Combiner operability components
Overview
This enhancement improves the operability of the Digital Radio Interface (DRI) and
combiner 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 equipping
the DRI.

30th Jun 02 68P02900W21-K 4–23
GMR-01
DRI/Combiner operability components GSM-001-103
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
Primary Combiner proc Secondary Combiner proc
COMB 0 0 COMB 0 1
Controlling DRI Standby DRI
DRI 0 0 DRI 0 1
GSR5 CONFIGURATION
COMB 0
First controlling Second controlling

DRI DRI
DRI 0 0 DRI 0 1

4–24 68P02900W21-K 30th Jun 02
GMR-01
Chapter 5
BSC planning steps and rules

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter provides the planning steps and rules for the BSC. The planning steps and
rules for the BTS are in Chapter 4 of this manual. This chapter contains:
S 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.
– Determining the number of XBLs required.
– Determining the number of GSLs required.
– BSC GPROC functions and types.
– Traffic models.
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.

30th Jun 02 68P02900W21-K 5–1
GMR-01
BSC planning overview GSM-001-103
BSC planning overview
Introduction
To plan the equipage of a BSC certain information must be known. The major items
include:
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 PDTCHs at each site.
S The total number of TCHs and PDTCHs under the BSC.
S The number of cells controlled from each BTS site should not exceed the
maximum 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.

5–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSC planning overview

Planning a BSC involves the following steps, which are all described in detail in this
chapter:
1. Plan the number of E1 or T1 links between the BSC and BTS site(s), refer to the
section Determine the required BSS signalling link capacities.
2. Plan the number of RSL links between the BSC and BTS site(s), refer to the
section Determine the RSLs required.
3. Plan the number of MTL links between the BSC and MSC, refer to the section
Determine the number of MTLs required.
4. Plan the number of XBL links required between the BSC and AXCDR, refer to the
section Determining the number of XBLs required.
5. Plan the number of GSL links required between the BSC and the PCU, refer to
Determining the number of RSLs 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 serial
interface (MSI, MSI-2.
9. Plan the number of KSWs and timeslots required, refer to the section Kiloport
switch (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 switch
extender (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 interface extender
(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 volatile
memory (NVM) board.
20. Verify the planning process, refer to the section Verify the number of BSU
shelves and BSSC cabinets.

30th Jun 02 68P02900W21-K 5–3
GMR-01
Capacity calculations GSM-001-103
Capacity calculations
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC,
GPROC2) and the throughput capacities of its data links, determine the number of
supported traffic channels (TCHs). These capacities are limited by the ability of the
processors, and links to handle the signalling information associated with these TCHs.
This section provides information on how to calculate processor requirements, signalling
link capacities and BSC processing capacities. This section describes:
S 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.

5–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSC system capacity
BSC system capacity
System capacity summary

Table 5-1 provides a summary of BSC maximum capacities.
Table 5-1 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 note 960 1680 1920 1920 2400 2400 2400 *
below)
C7 links 16 16 16 16 16 16 16
T1 or E1 links 72 96 102 102 102 102 102
Maximum busy 38,000 50,400 57,600 57,600 72,000 72,000 90,000
hour call attempts
* 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 the
GPRS traffic is carried on the BSS, the GSM circuit-switched traffic handling capacity
reduces in direct proportion to the timeslots configured for GPRS traffic.
The maximum Busy Hour Call Attempts (BHCA) is computed for the standard call
model. 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-1
should not be exceeded for the GSR version used. The first element to reach its limit
sets the capacity of the BSC. For example, when dimensioning a BSC with a specific
non-standard call model, there is possibility that the LCF or C7 limit will be reached
before the Erlang limit is reached.

30th Jun 02 68P02900W21-K 5–5
GMR-01
BSC system capacity GSM-001-103
Scaleable BSC
With the launch of the scaleable BSC, Motorola moved to a position where the diverse
requirements of network operators in terms of BSC size are addressed by a single
platform that can be efficiently configured in small, medium or large models.
For existing customers the move to a scaleable BSC is enabled through the migration of
the processing boards within the BSC to use the GPROC2 throughout. BSSs targeted at
small, medium, or large networks are efficiently addressed by the scaleable BSC where
minimal incremental hardware is required to be added as the networks grow.
Being able to expand capacity within a BSC is appealing from an operational viewpoint
because there is less time and effort involved than compared with having to move sites
from one BSC to another, or even from one OMC-R to another.
Put into context, the BSC capacity prior to GSR3 supports in the order of 40 sites of
three sectors and one carrier per sector; or alternatively, 20 sites of three sectors and
two carriers per sector. At GSR3, the capacity increased to allow the operator to move to
support in the order of 40 sites of three sectors and two carriers per sector. At GSR4, the
capacity increased to allow the operator to move to support in the order of 64 sites of
three sectors and two carriers per sector.
The scaleable BSC also offers a substantial advantage for microcellular deployment
where a single BSC is able to support up to 100 microcellular BTSs, each equipped with
two carriers per site.
The scaleable BSC capacity is enabled because of the increased processing
performance and memory of the GPROC2. The maximum capacity is increased as
shown in Table 5-1.
This increased capacity is achieved through the deployment of GPROC2s for each
function at the BSC, including base station processor (BSP) and link control function
(LCF).
Enhanced BSC capacity option

This feature is introduced at GSR6 as a restrictable option. If the feature is restricted, the
BSC 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 to
512 carriers and 3200 trunks.
Specific hardware upgrades are required by the BSS to support implementation if this
optional 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.

5–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the required BSS signalling link capacities
Determining the required BSS signalling link capacities
BSC signalling traffic model

For a GSM system the throughput of network entities, including sub-components,
depends upon the assumed traffic model used in the network design or operation. Traffic
models are fundamental to a number of planning actions.
The capacity of the BSC as a whole, or the capacity of a particular GPROC, depends on
its ability to process information transported through signalling links connecting it to the
other network elements. These elements include MSC, BTSs, and the OMC-R.
Depending on its device type and BSC configuration, a GPROC may be controlling
signalling links to one or more other network elements. A capacity figure can be stated
for each GPROC device type in terms of a static capacity such as the number of physical
signalling links supported, and a dynamic capacity such as processing throughput.
In general telephony environments, processing and link throughput capacities can be
stated in terms of the offered call load. To apply this for the GSM BSC, all signalling
information to be processed by the BSC, is related to the offered call load (the amount of
traffic offered/generated by subscribers). When calls are blocked due to all trunks or all
TCHs busy, most of the signalling associated with call setup and clearing still takes place,
even though few or no trunk resources are utilized. Therefore, the offered call load (which
includes the blocked calls) should be used in planning the signalling resources (for
example; MTLs and RSLs).
In the case where the BSC has more than enough trunks to handle the offered traffic,
adequate signalling resources should be planned to handle the potential carried traffic.
The trunk count can be used as an approximate Erlang value for the potential carried
load.
As a result, the signalling links and processing requirements should be able to
handle the greater of the following:
S The offered load.
S The potential carried load.
To determine the link and processing requirements of the BSC, the number of trunks or
the offered call load in Erlangs (whichever is greater) should be used.
BSC capacity planning requires a model that associates the signalling generated from all
the pertinent GSM procedures: call setup and clearing, handover, location updating, and
paging, to the offered call load. To establish the relationship between all the procedures,
the traffic model expresses processing requirements for these procedures as ratios to the
number of call attempts processed. The rate at which call attempts are processed is a
function of the offered call load and the average call hold time.
NOTE A standard traffic model can be assumed when initially planning
a network. However, once the network is running, it is
absolutely critical to continuously monitor and measure the real
call parameters (described in Chapter 11) from the live network
to ascertain the true network call model.
Future planning should then be based on this actual (non
standard) call model instead of the standard call model. Past
studies have shown that the actual call model in some networks
differs considerably from the standard call model, and this has a
direct impact on dimensioning requirements.
Figure 5-1 graphically depicts various factors that should be taken into account when
planning a BSS.

30th Jun 02 68P02900W21-K 5–7
GMR-01
Determining the required BSS signalling link capacities GSM-001-103
Figure 5-1 BSS planning diagram
MSC
TRANSCODER
WITH SUBMULTIPLEXING TRANSCODING AT MSC
1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK
1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK *
A INTERFACE (TERRESTRIAL LINKS) 1 x 64 KBIT/S CIRCUIT/ XBL
–C7 SIGNALLING LINKS 1 x 64 KBIT/S CIRCUIT/4 TRUNKS
–X.25 CONTROL LINK *
–REQUIRED TRUNKS WITHOUT SUBMULTIPLEXING TRANSCODING AT BSC
1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK*
1 x 64 KBIT/S CIRCUIT/TRUNK
GDS INTERFACE ** THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED

– GDS TRAU CHANNELS FROM THE # OF TRUNKS REQUIRED TO CARRY THE
– GSL LINKS
SUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS,
TYPICALLY USING 1% BLOCKING) FROM ALL BTSs
BSC TO PCU – PLUS –
GDS–TRAU THE # OF GDS TRAU LINKS (DETERMINED FROM THE
CIRCUITS NUMBER OF GPRS TIMESLOTS UNDER A BSC)
GBL PCU – PLUS –
THE # OF GSLs THE # OF C7 SIGNALLING LINKS
THE # OF GBLs – PLUS – (IF APPLICABLE*)
THE # OF X.25 LINKS (USUALLY ONE PER BSC)
1 x 16 KBIT/S CIRCUIT / – PLUS –
GPRS TIMESLOT THE # OF XBL LINKS
1 x 64 KBIT/S GSL LINK
– PLUS –
THE # OF GSL LINKS
BSC
1 x 64 KBIT/S OF 1 x 16 KBIT/S SCU CIRCUIT/LAPD

MOTOROLA BSC/BTS INTERFACE SIGNALLING LINK
NON-BLOCKING 2 x 64 KBIT/S CIRCUITS/DRCU/SCU
1 x 16 KBIT/S GSL CIRCUITS/TIMESLOT
THE # OF TCHs REQUIRED (USING TYPICALLY 2%

BLOCKING) TO CARRY SUBSCRIBER TRAFFIC.
THE TCHs PLUS THE REQUIRED SIGNALLING TSs
DIVIDED BY EIGHT DETERMINES THE CARRIERS
REQUIRED (ON A BTS/SECTOR BASIS)
BTS
AIR INTERFACE
–TCHs, PDTCHs AND SIGNALLING TSs
–TYPICALLY 2% BLOCKING FOR CS TRANSCODING MUST BE LOCATED AT THE
TRAFFIC
BSC, OR BETWEEN THE BSC AND MSC
AIR INTERFACE
(TRAFFIC IN ERLANGS) TCH = TRAFFIC CHANNEL
TS = TIMESLOT
* X.25 MAY BE PASSED TO RXCDR
OR MSC SITE
** GDS–TRAU AND GSL ARE
CARRIED ON SEPARATE LINKS
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT

HARDWARE FOR THE ‘A’ AND ‘BSC TO BTS’ INTERFACE.

5–8 68P02900W21-K 30th Jun 02
GMR-01
Typical parameter values

The parameters required to calculate BSC processing and signalling link capacities are
listed in Table 5-2 with their typical values.
Two methods for determining capacity are given. The first method is based on the typical
call parameters given in Table 5-2 and simplifies planning to lookup tables, or simple
formulae indicated in Standard traffic model planning steps. When the call parameters
being planned for differ significantly from the standard traffic model, more complex
formulae must be used as indicated in Non-standard traffic model planning steps.
Table 5-2 Typical call parameters

GPRS parameters
CS2 = 13.4 kbit/s
CS3 = 15.6 kbit/s
CS4 = 21.4 kbit/s

30th Jun 02 68P02900W21-K 5–9
GMR-01
Location update factor

The location update factor (L) is a function of the ratio of location updates to calls (l), the
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 in
Table 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 = P * (T/N)

5–10 68P02900W21-K 30th Jun 02
GMR-01
Assumptions used in capacity calculations
Signalling message sequence and size assumptions

To calculate link and processing capacity values, certain signalling message sequence
patterns and message sizes have been assumed for the various procedures included in
the signalling traffic model. New capacity values may have to be calculated if the actual
message patterns and message sizes differ significantly from those assumed. The
assumptions used for the capacity calculations in this manual are summarized below.
The number of uplink and downlink messages with the respective average message
sizes (not including link protocol overhead) for each procedure are provided in Table 5-4,
Table 5-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 bytes
11 uplink messages with average size of 26 bytes
Handover, incoming and 5 downlink messages with average size of 33 bytes
outgoing 7 uplink messages with average size of 24 bytes
Location update 7 downlink messages with average size of 22 bytes
SMS-P to P 7 downlink messages with average size of 30 bytes
(see note below) 7 uplink messages with average size of 42 bytes
IMSI detach (type 1) 1 downlink messages with average size of 30 bytes
Paging 1 downlink message with average size of 30 bytes
NOTE The actual number and size of messages required by SMS

depend on the implementation of the SMS service centre. The
numbers given are estimates for a typical implementation. These
numbers may vary.

30th Jun 02 68P02900W21-K 5–11
GMR-01
Table 5-5 Procedure capacities (BSC – BTS)

Procedure BSC to BTS link
Paging 1 downlink message. Message size depends on the
number 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 bytes
1 uplink message with average size of 21 bytes
Preload messages 2 downlink messages of 20 bytes and 1 byte respectively
2 uplink messages with an average size of 4 bytes
NOTE From GSR6 onwards, the BSS software uses a new small
message header (compact header) for delivering messages
between the BSC/PCU and the BTS. The new message header
contains the minimum information necessary to deliver the
messages between the processes. The size of the new message
header is 8 bytes, as compared to 28 bytes in pre GSR6
releases. This reduces the signalling link utilization between the
BSC–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 bytes
1 uplink message with average size of 41 bytes
An additional assumption, which is made in determining the values listed in the above
tables, is that the procedures not included in the traffic model are considered to have a
negligible effect.
NOTE Supplementary Service (SS) messaging has not been taken into
account. This could contribute a significant signalling overhead in
some networks.

5–12 68P02900W21-K 30th Jun 02
GMR-01
Paging assumptions
In calculating the average DL message size for paging, it is assumed that paging is by
LAC (or LAI) only. Paging by LAC only is the recommended method. Paging by LAC
and 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 through
the setting of the Cell Identification Discriminator in the BSSMAP paging message.
The BSC can determine from its Configuration Management database which cells
need to be paged from the location area code only. Therefore, the MSC does not
need to send a list of each individual cell identity. Paging by LAC and Cell ID will
increase the length of the BSSMAP paging considerably and will also
significantly increase the C7 signalling load between the MSC and BSC.
S Paging by LAC only reduces the possibility of paging channel overload on the air
interface caused by any database mismatches between the BSC and MSC. If the
BSC receives a cell identity in the paging message from the MSC that does not
exist in its Configuration Management database, it defaults to paging all cells in the
BSS for safety reasons. This can cause overload of the paging channel on the
radio interface.
Link capacities
The level of link utilization is largely a matter of choice of the system designer. A design
that has more links running at a lower message rate can have the advantage of offering
better fault tolerance, since the failure of any one link affects less signalling traffic.
Reconfiguration around the fault could be less disruptive. Such a design could offer
reduced queueing delays for signalling messages. A design that utilizes fewer links at a
higher message rate, reduces the number of 64 kbit/s circuits required for signalling, and
potentially reduces the number of resources (processors, data ports) required in the
MSC. It is recommended that the C7 links be designed to operate at no more than 20%
link utilization when the MTL is running on a GPROC; and no more than 40% utilization
when the MTL is running on a GPROC2. However, before use of the 40% utilization for
GPROC2, it is imperative that the operator verifies that the MSC vendor can also support
40% utilization at the MSC end; if not, only 20% link utilization should be used for
GPROC2.
If higher link utilizations are used, the controlling GPROCs (LCF–MTLs) may become
overloaded.
NOTE Overloading GPROCs can cause the BSC to become
unstable. Links must be monitored closely to ensure that link
utilization does not exceed the maximum.
If link utilization is regularly approaching the maximum, additional
capacity should be added to reduce the possibility of overloading
the GPROCs.
C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from the
failed link to be redistributed among the remaining functioning links. A C7 link set officially
has at least two and at most 16 links. The failure of links, for any reason, cause the
signalling to be shared across the remaining members of the link set. Therefore, the
design must plan for reserve link and processing capacity to support a certain number of
failed signalling links.

30th Jun 02 68P02900W21-K 5–13
GMR-01
Determining the number of RSLs required GSM-001-103
Determining the number of RSLs required
Introduction
Each BTS site which is connected directly to the BSC, including the first site in a daisy
chain, must be considered individually. Once individual RSL requirements are calculated
the total number of LCFs can be determined for the BSC.
The following factors should be considered when planning the provision of RSL (LAPD
signalling) links from the BSC to BTS sites:
S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTS
site. One link can support multiple collocated cells. As the system grows,
additional signalling links may be required. Refer to the section Determining the
required BSS signalling link capacities in this chapter to determine the number
of RSL links required.
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.
S The number of 16 kbit/s RSL links is limited, depending on the platform. See
16 kbit/s RSL in Chapter 2 for further details. 64 kbit/s RSLs must be used when
allowable numbers are exceeded.
Determining the number of RSLs

The RSL signalling link provisioning has a contribution from the GSM circuit-switched
part of the network and from the GPRS part. The equation for determining the number of
RSL links for the combined signalling load is as follows:
RSL GPRS)GSM + RSL GPRS ) RSL GSM
This is evaluated for 16 kbit/s RSLs or for 64 kbit/s RSLs. The interface between the BTS
and BSC does not permit mixing the two RSL rates.
Where: RSLGPRS+GSM is: The combined number of RSL

signalling links on a per BTS site
basis operating at a 16 kbit/s RSL
rate or at a 64 kbit/s RSL rate.
RSLGPRS This is the number of RSL
signalling links required to serve
the GPRS part of the network at
16 kbit/s or at 64 kbit/s.
RSLGSM This is the number of RSL
the GSM part of the network at

5–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the number of RSLs required
Standard traffic model

The number of BSC to BTS signalling links (RSL) must be determined for each BTS.
This number depends on the number of TCHs and PDTCHs at the BTS. Table 5-7 gives
the number of RSLs required (rounded up integer value) for a BTS to support the given
number of TCHs and PDTCHs, based on the typical call parameters given in the
standard traffic model column of Table 5-2. If the call parameters differ significantly
from the standard traffic model, use the formulae for the non-standard traffic model.
Table 5-7 Number of BSC to BTS signalling links

With Preload With One Phase Access
# # # 64 kbit/s # 16 kbit/s # 64 kbit/s # 16 kbit/s
TCHs/BTS PDTCHs/BTS RSLs RSLs RSLs RSLs
(n) (Ngprs)
<= 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)

30th Jun 02 68P02900W21-K 5–15
GMR-01

(n) (Ngprs)
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 GPRS
timeslots, even if the cells do not have traffic channels
configured as PDTCHs, it may have paging traffic.
RACH_Arrivals/sec figures have been calculated assuming
Avg_Sessions_per_user is as in the call model table.
GPRS_Users_BTS has been calculated based on the number of
timeslots configured on the cell.
A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, but
not both.

5–16 68P02900W21-K 30th Jun 02
GMR-01
Non-standard traffic model

64 kbit/s RSLs
If the call parameters differ significantly from those given in Table 5-2, use the following
formula to determine the required number of 64 kbit/s RSLs.
RSL GSM@64k +
n * (49 ) 50 * S ) 32 * H ) 20 * L) (27 ) 3 * C) * P GSM

)
1000 * U * T 8000 * U
The RSL traffic load for GPRS depends on the access mechanism used on the air
interface. From GSR6 onwards, Motorola BSCs allow use of one phase access or a
Motorola proprietary pre-load mechanism.
With one phase access
RSL GPRS@64k +
(32 ) C) * P GPRS RACH_Arrivalsńsec * 4 RACH_Arrivalsńsec * 5 * 0.3

) )
8000 * U 1000 * U 1000 * U
With pre-load
RSL GPRS@64k +
(32 ) C) * P GPRS RACH_Arrivalsńsec * 6 RACH_Arrivalsńsec * 5 * 0.3

) )
8000 * U 1000 * U 1000 * U
Therefore:
RSL (GSM)GPRS)@64k + Round up(RSL GSM@64k ) RSL GPRS@64k)
16 kbit/s RSLs
formula to determine the required number of 16 kbit/s RSLs.
RSL GSM@16k +
ƪn * (49 ) 501000
* S ) 32 * H ) 20 * L) (27 ) 3 * C) * P
*U*T
)
8000 * U
ƫ GSM
* 4

RSL GPRS@16k +
ƪ(32 )8000C) ** UP GPRS

)
RACH_Arrivalsńsec * 4 RACH_Arrivalsńsec * 5 * 0.3
1000 * U
)
1000 * U
ƫ * 4
With pre-load
RSL GPRS@16k +
ƪ(32 )8000C) ** UP GPRS

)
RACH_Arrivalsńsec * 6 RACH_Arrivalsńsec * 5 * 0.3
1000 * U
)
1000 * U
ƫ * 4
Therefore:
RSL (GSM)GPRS)@16k + Round up(RSL GSM@16k ) RSL GPRS@16k)

30th Jun 02 68P02900W21-K 5–17
GMR-01
RACH arrivals
The number of RACH arrivals per second is roughly calculated as follows:
GPRS_Users_BTS * Avg_Sessions_per_user
RACH_Arrivalsńsec +
3600
In the above equations:
RSLGSM + GPRS is: the number of MSC to BSC signalling

links.
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 example
0.20).
T the average call duration.
PGSM the GSM paging rate in pages per
second.
PGPRS the GPRS paging rate in pages per
second.
C the number of cells at the BTS.
RACH_Arrivals/sec the number of RACH arrivals per
second per BTS.
GPRS_Users_BTS the number of GPRS users on the BTS.
Avg_Sessions_per_user the average number of sessions per
user in a busy hour. This includes the
sessions 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 the
same amount of data transferred in per user in a busy hour, if the
traffic is predominantly WAP then the number of RACH arrivals
will be very high compared to when the data traffic is
predominantly FTP transfers. The traffic profile needs to be
calculated based on applications running on the network.
With the introduction of the Interleaving TBF feature in GSR6, it
is expected that the sessions arrival rate in each cell may
potentially be higher than for previous GSRs. With interleaving
TBFs it is possible to have multiple MSs on each timeslot.
Customers should take this fact into account when estimating the
sessions for the above formula.

5–18 68P02900W21-K 30th Jun 02
GMR-01
BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links may be
added, if required.
Impact of different coding schemes on interconnect planning

32 kbit/s TRAU links are required to accommodate additional bandwidth required to
support CS3 and CS4 coding schemes. The method used to achieve a 32 kbit/s TRAU
channel is to combine two component 16 kbit/s TRAU channels. As a result, the
interconnect capacity is affected.
Currently, 32 kbit/s TRAU is implemented on a per GPRS carrier basis.
Planning actions without CS3 and CS4

Use the following equation:
[(nTCH + nPDTCH + L16) / 4] + L64
N BSC*BTS +
31
Where: NBSC–BTS is: the minimum number of E1 links required

(rounded up to an integer).
nTCH the number of GSM traffic channels at the BTS.
nPDTCH the number of GPRS traffic channels at the BTS.
L16 the number of 16 kbit/s RSLs (LAPD links).
NOTE Refer to Chapter 2 in this manual, for a discussion on TCH

planning for the BTS concentration feature.
This formula includes both L16 and L64 to provide the necessary
number of RSLs. As above, either L16 or L64 RSL can be used,
but not both, to a single BTS.
Planning actions with CS3 and CS4

For carriers supplying the CS3/CS4 coding schemes, 32 kbit/s TRAU is required for each
channel on a carrier basis. Hence, the number of E1s required to connect to a BTS is
calculated as follows:
{[nCGPRS * 8 * 2 ) (nTCH * nTCH GPRS) ) L16]ń4} ) L64
N BSC*BTS +
31
Where: nCGPRS is: the number of GPRS carriers with CS3 and CS4
enabled.
nTCHGPRS the number of reserved TCHs within the GPRS
carrier with CS3 and CS4 enabled.

30th Jun 02 68P02900W21-K 5–19
GMR-01
BSC to BTS T1 interconnect planning actions

Determine the number of T1 links required to connect to a BTS. Redundant links may be
added, if required.
NOTE GPRS is not currently supported over a T1 interface.

[(nTCH + L16) / 4] + L64
N BSC*BTS +
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 TCH

planning for the BTS concentration feature.
This formula includes both L16 and L64 to provide the necessary

5–20 68P02900W21-K 30th Jun 02
GMR-01
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 call
parameters are similar to those listed in Table 5-2 (standard traffic model). The second
method is used when the call parameters differ significantly from those listed in Table 5-2
(non-standard traffic model).

Use the formula:
G L3 + n ) B ) C
1060 160 120
Where: GL3 is: the number of LCF GPROC2s required to support the
layer 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 alternative
formula given below should be used to determine the recommended number of LCFs.
G L3 +
ƪn * (1 ) 0.42 * S ) 0.45(23.2* H**T(1) * 0.4 * i) ) 0.36 * L) ) (0.00072 * P ) 0.004) * B ) 120

C ƫ
n the number of TCHs under the BSC.
i the ratio of intra-BSC handovers to all handovers.
P the paging rate in pages per second.
NOTE Having calculated the LCF-GPROC2s for RSLs, ensure that the
traffic is evenly distributed across the LCFs. This may be difficult
in cases where large sites are being used, and in such cases
additional LCFs may be required. Alternatively, use the above
formula for traffic channels on each LCF. If the calculated value
exceeds 1, the sites should be redistributed on the other
available LCFs, or additional LCFs should be equipped.

30th Jun 02 68P02900W21-K 5–21
GMR-01
The LCF GPROC2 can simultaneously handle signalling traffic from both the GSM and
GPRS parts of the network. It is possible to calculate the GPRS part of the signalling
load for the LCF GPROC2 in fractional increments. The GPRS LCF GPROC2
requirements can be directly added to the GSM requirements in order to determine the
total number of LCF GPROC2s to equip at a BSC.
The MSC can send GSM alerting pages to a GPRS mobile that operates in class A or
class B modes. The significance of this is that GPRS mobile stations capable of class A
and B operation create a larger population of GSM capable mobile stations that should
be considered when provisioning the LCF GPROC2.
The planning information provided here should be used for this provisioning.
N C
GPRS GRPS
G *T
) (0.006 ) 0.02 * P GPRS) * (B RA_GPRS) ) 35
GPRS_PF GPRS
G L3_GPRS +
2.5
Where: GL3_GPRS is: Number of LCF GPROC2s to

handle GPRS related RSL
signalling traffic.
NGPRS Number of active GPRS timeslots
served at the BSC.
GGPRS_PF GPROC2 GPRS performance
factor for RSL processing.
TGPRS Mean duration of a TBF in
seconds.
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:

N GPRS + MIN[No_PRP_boards * 30, No_GPRS_ts * Mslot_Util_factor]
Where: NGPRS is: Number of active GPRS timeslots

served at the BSC.
No_PRP_boards Number of PRP boards in the PCU.
No_GPRS_ts Number of GPRS timeslots in all of
the BTS cells served by the BSC.
Mslot_Util_factor This is the ratio of the mean
number of active timeslots on a
GPRS carrier to the total number of
provisioned GPRS timeslots on a
carrier.

5–22 68P02900W21-K 30th Jun 02
GMR-01
Using the figures in Table 5-8, it can be determined that six LCF GPROC2s may be
required for a maximally configured PCU.
Table 5-8 Typical values for GPRS LCF GPROC2 provisioning

Parameter Value
NGPRS 30 to 270 is the range for the number of active timeslots
provisioned at one PCU.
GGPRS_PF 100.
TGPRS 1 second, corresponds to the duration of time to transmit two
mean length LLC PDUs at the CS2 rate.
PGPRS 12, for a fully configured redundant PCU with a 10% paging
load based on a mean number of active timeslots equal to
120.
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.

30th Jun 02 68P02900W21-K 5–23
GMR-01
Determining the number of MTLs required GSM-001-103
Determining the number of MTLs required
Introduction
MTLs carry signalling traffic between the MSC and BSC. The number of required MTLs
depends upon the BSS configuration size and traffic model. MTLs are carried on E1 or
T1 links between the MSC and BSC, which are also used for traffic.
The following factors should be considered when planning the links from the BSC to
MSC:
S Determine traffic requirements for the BSC. Traffic may be determined using either
of the following methods:
– Multiply the number of subscribers expected to use the BSC by the average
traffic per subscriber.
or
– Total the traffic potential of each BTS under the BSC; determined by the
number of TCHs available, the number of TCHs required or the subscriber
potential.
S Determine the number of trunks to support the traffic requirements of the BSC
using Erlang B tables at the required blocking rate.
S Determine the MTL loadshare granularity to be used for the BSC. MTL loadshare
granularity determines the number of logical links that will be mapped onto the
physical links. Setting the mtl_loadshare_granularity database element to 1 results
in a more even distribution of traffic across the MTL links. This feature allows a
more gradual increase in the number of MTLs required with the increased traffic
load 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, if
using 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 difference
between setting the load share granularity to 0 and 1 respectively. Table 5-9 and
Table 5-10 illustrate the difference between setting the loadshare granularity to 0 and 1.
NOTE These calculations are for the MTLs required from the BSS
perspective, using the BSS planning rules. If the MSC vendor
supplies their own planning rules for a given configuration, the
more conservative MTL provisioning figures should be used. If
the MSC vendor does not provide the planning rules for the
MTLs required in a downlink direction, then use a load share
granularity of 0 to be conservative in MTL provisioning.
Load sharing of MTLs in the downlink direction depends on the
mechanism used by the MSC to load share the signalling links
from the MSC to BSC.

5–24 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the number of MTLs required

The number of MSC to BSC signalling links (MTL) required depends on the desired link
utilization, the type and capacity of the GPROCs controlling the MTLs and the MTL
loadshare granularity. The BSS software distributes call signalling traffic across 16 or 64
logical links, which are then evenly spread across the active MTLs.
CCITT C7 uses a 4 bit number, the Signalling Link Selection (SLS), generated by the
upper layer to load share message traffic among the in-service links of a link set. When
the number of in-service links is not a power of 2, some links may experience a higher
load than others. From GSR5 release onwards, the BSS supports distribution of
signalling in the uplink direction, over 64 logical links. The BSS evenly distributes the 64
logical links over the active MTLs.
The number of MTLs is a function of the number of MSC to BSC trunks or the offered
call load and signalling for the call load. Table 5-9 and Table 5-10 give the recommended
minimum 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 BSC
trunks).
The offered call load for a BSS is the sum of the offered call load from all of the cells of
the BSS. The offered call load at a cell is a function of the number of TCHs and blocking.
As blocking increases the offered call load increase. For example, for a cell with 15 TCHs
and 2% blocking, the offered call load is 9.01 Erlangs.
NOTE Before setting the load share granularity to 1, it is recommended

that confirmation is gained from the Motorola local contact, or
local office, that the switch is compatible with the load share
granularity set to 1.

30th Jun 02 68P02900W21-K 5–25
GMR-01
Table 5-9 and Table 5-10 show how to estimate the number of MTLs to be used for the
BSC, with 20% and 40% link utilization, respectively.
Table 5-9 Number of MSC and BSC signalling links (20% utilization)
No. of MTLs with 16 No. of MTLs with 64
N = the greater of logical links logical links
number of MSC-BSC
trunks or the offered Minimum Recommended Minimum Recommended
load from the BTSs required required
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

5–26 68P02900W21-K 30th Jun 02
GMR-01
Table 5-10 Number of MSC and BSC signalling links (40% utilization)
number of MSC-BSC
trunks or the offered Minimum Recommended Minimum Recommended
load from the BTSs required required
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-9 and Table 5-10 are based on
the standard traffic model shown in Table 5-2.
It is recommended that the C7 links be designed to operate at no
more than 20% link utilization when the MTL is running on a
GPROC, and no more than 40% utilization when the MTL is
running on a GPROC2. However, before using MTLs with 40%
utilization, it is imperative that the operator verifies if the MSC
vendor 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 is
supported on the BSC.

30th Jun 02 68P02900W21-K 5–27
GMR-01

If the call parameters differ significantly from those given in Table 5-2, the following
procedure is used to determine the required number of MSC to BSC signalling links:
1. Use the formula detailed below to determine the maximum number of Erlangs
supported by a C7 signalling link (nlink).
(1000 * U * T)
n link +
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 9 * P PC)
supported by a GPROC2 (LCF–MTL) supporting a C7 signalling link (nlLCF–MTL).
(20 * T)
nl LCF*MTL +
(1 ) 0.16 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.42 * L ) P PC * (0.005 * B ) 0.05))
3. The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is the
smaller of the two numbers from steps 1 and 2.
nl min + MIN(n link, nl LCF_MTL)
4. Signalling over the A–interface is uniformly distributed over a number of logical

links. The number of logical links is defined on the BSC by database parameter
mtl_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 amount
of traffic that a logical link would hold, is calculated as:
N logical + N
Ng
5. Next we need to determine the number of logical links each MTL (physical link)
can handle (nlog-per-mtl):
n log_per_mtl + round down ǒ nl min

Nlogical
Ǔ
6. Finally, the number of required MTLs (mtls) is:
mtls + round up ǒn Ng
log_per_mtl
Ǔ)R v 16
NOTE mtls should not exceed 16 per BSC.

The formula in step 2 has been calculated using 70% mean
utilization of GPROC2.
Field experience suggests it is good practice to maintain the
mean utilization of GPROCs at or below 70%.
Taking LCS into consideration, C7 is also used for LCS signalling
between the BSC and MSC and LCS signalling between BCS
and SMLC if BSS based LCS architecture is supported. Refer to
Chapter 8, Determining the required BSS signalling link
capacities.

5–28 68P02900W21-K 30th Jun 02
GMR-01
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 all
handovers.
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.

30th Jun 02 68P02900W21-K 5–29
GMR-01
Calculate the number of LCFs for MTL processing

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

BSC to BTS signalling links.
LCFs for MSC to BSC links

Since one LCF GPROC2 can support two MTLs, the number of required LCFs is:
N LCF + ROUND UP ǒmtls

2
Ǔ
However, if the traffic model does not conform to the standard model:
if 2 * n link u nl LCF*MTL, then NLCF + mtls
otherwise:

2
Ǔ
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 over
a satellite link. PCR retransmits unacknowledged messages when there are no new
messages to be sent. This puts an additional processing load on the GPROC2
(LCF–MTLs) controlling the C7 signalling links. It is recommended that when PCR is
used, that the number of MTLs (and thus the number of LCF–MTLs) be doubled from the
number normally required.

5–30 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the number of XBLs required
Determining the number of XBLs required
Introduction
XBLs carry the signaling traffic between the BSC and AXCDR. The number of XBL links
required depends upon the number of CICs and/or the number of Ater interface
channels.
The following factors need to be considered when planning the number of XBL links from
the 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 auto
connect) in which the BSC and RXCDR operate. See Chapter 2 for a description
of the modes.
S A maximum of 18 XBLs (64 kbit/s or 16 kbit/s) can be configured for a
BSC/RXCDR.
S A BSC can connect to a maximum of 9 RXCDRs and vice versa.
Determining the number of XBLs

The number of XBL links depends on the number of trunks on the BSC-RXCDR interface
and whether or not the auto-connect mode or enhanced auto-connect mode is enabled at
the RXCDR/BSC. Table 5-11 details the minimum number of XBLs required to support
the given number of trunks between the BSC and RXCDR, with auto-connect mode or
enhanced auto-connect mode.
Table 5-11 Number of BSC to RXCDR signalling links

N = number of No redundancy With redundancy
MSC to BSC
trunks
Number of Number of Number of Number of
64kb/s XBLs 16kb/s XBLs 64kb/s XBLs 16kb/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%. Above this level,
queueing delays could become substantial. Although both auto-connect mode and
enhanced auto-connect mode apply a load, it is the enhanced auto-connect mode load
that can vary depending on system configuration. When operating in this mode, the XBL
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 start up and
reconfigurations due to faults and maintenance.
XBL link utilization is a network statistic, calculated on a per XBL basis.

30th Jun 02 68P02900W21-K 5–31
GMR-01
Determining the number of XBLs required GSM-001-103

The minimum number of XBL links required as given in Table 5-11 were verified using a
standard set of call parameters. These are given in Table 5-2.
Non standard traffic model

formula to determine the required number of 64 kbit/s XBLs (rounded up to the next
integer):
XBL + N * 5.1
1000 * UXBL * T
Use the following formula to determine the required number of 16 kbit/s XBLs (rounded
up to the next integer):
XBL + ƪ1000N**U5.1 * Tƫ
XBL
* 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 example
0.40).
T The average call duration in seconds.

5–32 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the number of GSLs required
Determining the number of GSLs required
The PCU requires one E1 in order to carry GSL signalling, and a second E1 for
redundancy. The PCU can support up to six primary GSL 64 kbit/s timeslots and six
redundant. Each 64 kbit/s timeslot is one LAPD channel. Provisioned GSL timeslots are
load-balanced over two E1 links, as the mechanism for providing resiliency against link
failures. It is recommended that two GSL E1 links are provisioned for resilience
purposes, even when the GSL is lightly loaded.
Each GSL message consists of three parts: LAPD protocol, BSS executive header
protocol, and the application message carrying actual signalling information. The LAPD
and BSS protocol parts can be considered messaging overhead. Also, in a similar
manner to RSL, the GSL traffic depends on the access mechanism used on the Air
interface. 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 and
GSL due to pre-load messaging and immediate assignment messages for UL TBF
setups.

6 * PGPRS ) Total_RACHńsec * 4 ) Total_RACHńsec * 1.5
GSL +
1000 * U
With pre-load
6 * PGPRS ) Total_RACHńsec * 6 ) Total_RACHńsec * 1.5
GSL +
1000 * U
Therefore:
GPRS_subs_per_PCU * Avg_session_per_subs
Total_RACHńsec +
3600
Where: GSL is: the number of 64 kbit/s LAPD GSL

timeslots to provision.
PGPRS the GPRS paging rate in pages per
second.
Total_RACH/sec the sum of all RACH arrivals on the
BSC.
U the link utilization, typically 0.25.
GPRS_subs_per_PCU the total GPRS users under a PCU
in the busy hour.
Avg_session_per_subss the average number of sessions
per subscriber in a busy hour (this
includes sessions for signalling).

30th Jun 02 68P02900W21-K 5–33
GMR-01
Determining the number of GSLs required GSM-001-103
Load balancing
The GSL traffic is load balanced over all GSLs. The first E1 carries up to six LAPD links
and the second E1 up to another six. For LAPD-type GDS resiliency, two E1s are
recommended, regardless of the number of LAPD channels required.
NOTE All available GSL timeslots are used to enable fast synchronized
PCU software downloads. This reduces the PCU software
download time considerably.
For example, if only one channel is required to carry the expected signalling load, two
E1s with one LAPD channel per E1 should be used. The MPROC load balancing
software distributes the load evenly between the two LAPD channels.

5–34 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Generic processor (GPROC2)
Generic processor (GPROC2)
Introduction
The generic processor (GPROC2) is a direct replacement for the original GPROC and is
used throughout the Motorola BSS as a generic control processor board. GPROC2s are
assigned functions and are then known by their function names.
This section describes the BSC GPROC types and their functions. The BSC
configuration type and GPROC device type are essential factors for BSC planning.
From GSR4 onwards, GPROC2s must be installed in all the slots at the BSC.
NOTE GSR5.1 introduced improved GPROC2 availability by reducing

the reset time. Where possible, a reset causes the GPROC code
to be loaded from RAM into RAM rather than from the slower
ROM into RAM.
GPROC2 functions and types

The GPROC2 is the basic building block of a distributed architecture. The GPROC2
provides the processing platform for the BSC. By using multiple GPROC2s, software
tasks can be distributed across GPROC2s to provide greater capacity. The set of tasks
that a GPROC2 is assigned, depends upon the configuration and capacity requirements
of the BSC. Although every GPROC2 is similar from a hardware standpoint, when a
group of tasks are assigned to a GPROC2, it is considered to be a unique GPROC2
device type or function in the BSC configuration management scheme.
There are a limited number of defined task groupings in the BSC, which result in the
naming of four unique GPROC2 device types for the BSC. The processing requirement
of a particular BSC determines the selection and quantity of each GPROC2 device type.
The possible general task groupings or functions for assignment to GPROC2s are:
S 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 and
type in the network element.

30th Jun 02 68P02900W21-K 5–35
GMR-01
Generic processor (GPROC2) GSM-001-103
BSC types
The BSC is configured as one of two types; the type is determined by the GPROCs
present.
S BSC type 1
– Master GPROC2.
Running the base site control processor (BSP) and carrying out operations
and maintenance functionalities.
– Link control processor (LCF).
Running the radio signalling link (RSL) and layer 3 processing or MTL (C7
signalling link) communications links. It also runs the GSLs for GPRS
signalling 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 control
links 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 to
enable communication with the OMC-R.
S For redundancy, each BSC should be equipped with a redundant BSP controller
and an additional GPROC2 to provide redundancy for the signalling LCFs. Where
multiple shelves exist, each shelf should have a minimum of two GPROC2s to
provide redundancy within that shelf.

5–36 68P02900W21-K 30th Jun 02
GMR-01
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 For RSL handling the maximum number of carriers that can be supported by an
LCF depends on the number of BTSs controlled by that LCF. The sum of 2 x (the
number of BTSs) and the number of carriers cannot exceed 120 for a GPROC2
LCF.
NOTE There is a limit of 24 carriers in a single Horizonmacro or M-Cell6
site.
S A LCF can handle up to 500 messages per second.

NOTE Combining MTL and RSL processing on a single GPROC2 is not
recommended.
The planning rules for LCFs exclusively using GPROC2 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 per
LCF depends on the Erlangs supported per LCF and MTL for that particular call
model.
S A single GPROC2 will support up to 31 BTS sites and 31 RSLs, limited to the
following calculations:
2 * rsls ) carriers v 120
Where carriers = the total number of radios for the BTS site(s).
ȍƪRACHńsecƫ * 4.6 v 500

i+1
n LCF * (21 ) 14 * S ) 14 * H ) 9 * L)
) P ) P GPRS )
T n
Where nLCF = the number of TCHs on the sites under a LCF

and
n = the total number of sites on the LCF.
If any LCF does not satisfy the above criteria, either rebalancing of sites on the
available LCF–GPROC2s at the BSC is required or additional LCF–GPROC2s
may need to be equipped at the BSC to handle the traffic load.
S The link utilization of a RSL should not exceed 25%.
S Up to 25 LCFs can be supported.
S A maximum of 31 BTS sites can be controlled by a single LCF. All RSLs (LAPD
links) for the BTSs will terminate on the same GPROC2, so if return loops are
used the maximum number of BTS sites will be 15 (if GPROC_slots = 31). If
GPROC_slots is set to 16 then at most 15 RSLs may exist which would support
up to seven BTS sites.
NOTE The number of serial links per GPROC2 must be determined for
each site. The current values are 16 or 32 with 16 being the
default value. One link is reserved for each board (for GPROC
test purposes) so the number of available serial links is either 15
or 31. However, when the links are running at high load, the
GPROC2 may experience some performance problems when
terminating 31 links. Hence, the use of more than 15 links per
board is not recommended.

30th Jun 02 68P02900W21-K 5–37
GMR-01
Generic processor (GPROC2) GSM-001-103
GPROC2 planning actions

Determine the number of GPROC2s required.
N GPROC2 + 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 OMF
functions then they should be provisioned separately.
Cell broadcast link

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

The BSC type 2 configuration offloads many of the O&M functions and control of the
interface to the OMC-R from the BSP. One of the major functions offloaded from the BSP
is the central statistics process. When determining the total number of statistics, consider
the number of instances of that statistic.
N ST + (ECS < C) ) (T CS < n) ) SX25LAPD (L ) X ) B)
Where: NST 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 statistics
are enabled across all cells.

5–38 68P02900W21-K 30th Jun 02
GMR-01

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

The BSS supports pooled GPROC2s for LCF and OMF redundancy. By equipping
additional GPROC2s for spares, if an LCF or the OMF GPROC2 were to fail, the system
software will automatically activate a spare GPROC2 from the GPROC2 pool to replace
the failed GPROC2.

30th Jun 02 68P02900W21-K 5–39
GMR-01
Transcoding GSM-001-103
Transcoding
Introduction
Transcoding reduces the number of cellular subscriber voice/data trunks required by a
factor of four. If transcoding takes place at the switch using a RXCDR, the number of
links between the RXCDR and the BSC is reduced to approximately one quarter of the
number of links between the RXCDR and the MSC.
The capacity of one BSU shelf is 12 MSI slots, six of which may contain a transcoder
(XCDR) or generic DSP (GDP); this limitation is due to power constraints. An RXU shelf
can support up to 16 GDP/XCDRs or GDPs and typically provides a better solution of the
transcoding function for larger commercial systems. Refer to the section Remote
transcoder planning overview in Chapter 6.
GDP/XCDR planning considerations

The following factors should be considered when planning the GDP/XCDR complement:
S The GDP board consists of 15 DSPs, each of which is capable of supporting the
transcoding 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 24
voice channels on T1, will support full rate, enhanced full rate speech,
uplink/downlink volume control and is capable of terminating one E1 or T1 link
from 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 is
capable of terminating one E1 link from the MSC.
S The master MSI slot(s) should always be populated to enable communication with
OMC-R. The master MSI slot may contain a GDP/XCDR, if the OML goes through
the MSC.
S The A-interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1
links; whereas an XCDR can only terminate E1 links (refer to T1 conversions
below).
NOTE The fitting of a GDP in place of an XCDR does not affect the
planning calculations for E1 links. For T1 links an MSI-2 is not
required.

5–40 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Transcoding
T1 conversion
T1 to E1 conversion is needed for XCDR, but not for GDP.
When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done in
one of two ways. In either case, the conversion may be part of an existing network
element or a standalone network element which would appear as 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 the
simplest method, but uses at most 23 of the transcoding circuits on the XCDR. This
method has no impact on the TDM bus ports, but does require MSI slots. This method
requires the number of GDP/XCDRs and additional MSI-2s to be equal to the number of
T1 links.
With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1
circuits may be done. This uses the ability of the KSW to switch between groups using
nailed connections. Although more efficient in XCDR utilization, this method may cause
additional KSWs to be used. Each MSI-2 requires an MSI slot. The number of MSI-2s
needed for T1 to E1 conversion is:
T+E
m=
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.

30th Jun 02 68P02900W21-K 5–41
GMR-01
Planning actions for transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the number
of E1 or T1 links for the A-interface. This text should be read in conjunction with the BSS
planning diagram, Figure 5-1.
Using E1 links
The minimum number of E1 links required for the A-interface is the greater of the two
calculations that follow (fractional values should be rounded up to the next integer value).
N= T
30
C+ X+ T
N=
31
Where: N is: the minimum number of E1 links required.

C the number of MTL links (C7 signalling links) to the
MSC.
X the number of OML links (X.25 control links to the
OMC-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 two
N= T
23
C+ X+ T
N=
24
Where: N is: the minimum number of T1 links required.

C the number of MTL links (C7 signalling links) to the
MSC.
X the number of OML links (X.25 control links to the
OMC-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).

5–42 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Multiple serial interface (MSI, MSI-2)
Multiple serial interface (MSI, MSI-2)
Introduction
A multiple serial interface provides the interface for the links between a BSSC cabinet
and other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI can
interface only E1 links, an MSI-2 can interface both E1 and T1 links, but not
simultaneously.
The following factors should be considered when planning the transcoder complement:
S 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 on

each 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/T1
links connected to the site.
OMC-R.
If the OML links go directly to the MSC, the master slot should be filled with an
GDP/XCDR, otherwise the slot should be filled with an MSI/MSI-2 which
terminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 links
do not need to go directly to the OMC-R, they may go to another network element
for concentration.

30th Jun 02 68P02900W21-K 5–43
GMR-01
Multiple serial interface (MSI, MSI-2) GSM-001-103
MSI/MSI-2 planning actions

The following formulae assume local transcoding. Refer to Chapter 6 RXCDR planning
steps and rules for MSI planning formulae for remote transcoding.
With E1 links
Determine the number of MSIs required.
ǒSNBSC*BTSi ) NBSC*RXCDR ) NGDS*TRAU ) N GSL*E1Ǔ
N MSI +
2
With T1 links
Determine the number of MSI-2s required.
ǒSNBSC*BTSi ) NBSC*RXCDR ) NGDS*TRAU ) N GSL*E1Ǔ
N MSI + )m
2
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 the
RXCDRs.
NGDS–TRAU the number of links from the BSC to the PCU
carrying GDS TRAU traffic (refer to Chapter 7).
NGSL–E1 the number of links between the BSC and the
PCU carrying GSL signalling links.
m the number of MSI/MSI-2s used for T1 to E1
conversion.

5–44 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Kiloport switch (KSW)
Kiloport switch (KSW)
Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the
BSC.
The following factors should be considered when planning the KSW complement:
S 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 expanded
by adding up to three additional KSWs, giving a total switching capacity of 4096 x
64 kbit/s or 16384 x 16 kbit/s ports, of which 8 x 64 kbit/s timeslots are reserved by
the 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 of
additional KSWs. For example, a BSC with 28 MSIs could be housed in three
shelves with three KSW modules, or four shelves with two KSW modules.
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 that
require 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_slots
database parameter).
R the number of GDP/XCDRs.
M the number of MSI/MSI-2s (do not count MSI-2s which
are doing on-board E1 to T1 conversion, when
determining TDM bandwidth).
NOTE Any BSC site which contains a DRIM has 352 timeslots allocated
to DRIMs, irrespective of the number of DRIMs equipped.

30th Jun 02 68P02900W21-K 5–45
GMR-01
Kiloport switch (KSW) GSM-001-103
KSW planning actions

Calculate the minimum number of KSWs required per BSC:
(G * n) + (R * 16) + (M * 64)
N=
(1016)
Where: N is: the number of KSWs required.

n 16 or 32 (depending on the value of the gproc_slots
database parameter).
M the number of MSI/MSI-2s (do not count MSI-2s which
are doing on-board E1 to T1 conversion).
Each KSW has to serve the boards in its shelf plus the boards of any extension shelf
connected 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 into
a common unique TDM highway across all shelves. That is, a KSW in one cage cannot
serve boards in other expansion shelves.
For example, in the case of a BSC consisting of two shelves each having 32 unused
timeslots per KSW free, an additional MSI board CANNOT be added even if a MSI slot is
free at each shelf. (But one GPROC2 per shelf can be added if one GPROC slot per
shelf is free.)

5–46 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSU shelves
BSU shelves
Introduction
The number of BSU shelves is normally a function of the number of GPROC2s,
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 GPROC2s. If the number of these exceeds
the number of slots available, an additional BSU shelf is required.
S Each expansion shelf is allocated to a single KSW and extension shelves are
differentiated by the presence of the KSW. Extension shelves are those which do
not contain a primary KSW. Shelves containing a KSW are called expansion
shelves.
S An extension shelf extends the TDM highway. It is constrained to the same
number of (aggregate) timeslots as the shelf containing the KSW.
S An expansion shelf adds an additional TDM highway. It increases the number of
timeslots 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 GDP/XCDRs boards (reducing the
number of MSI/MSI-2 boards appropriately).

30th Jun 02 68P02900W21-K 5–47
GMR-01
BSU shelves GSM-001-103
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 = G
8
M+ R
Bs =
12
Bs = R
6
Verify that the timeslot usage requirements are met for each shelf, as given in the
following equation:
(G * n) ) (R * 16) ) (M * 64) t+ 1016
If they are not, the configuration of MSI, GPROC and GDP boards may be adjusted, or
an additional cage or cages may be required.
Where: Bs is: the minimum number of BSU shelves required.

M the number of MSI/MSI-2s.
n 16 or 32 (depending on the value of the
gproc_slots database parameter).
NOTE The number of shelves may be larger if an attempt to reduce the

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

5–48 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Kiloport switch extender (KSWX)
Kiloport switch extender (KSWX)
Introduction
The KSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals
to all shelves in multi-shelf configurations. The KSWX is required whenever a network
element 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 or
extension is not required).
S For redundancy, duplicate all KSWX boards (requires redundant KSW).
S KSWXs are used in three modes:
– KSWX E (Expansion) are required to interconnect the KSWs for sites with
multiple KSWs.
– KSWX R (Remote) are required in shelves with KSWs to drive the TDM
highway in shelves that do not have KSWs.
– KSWX L (Local) are used in shelves that have KSWs to drive the clock bus in
that shelf and in shelves that do not have KSWs to drive both the local TDM
highway 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:
N KX + NKXE ) NKXR ) NKXL
N KXE + K * (K * 1)
N KXR + SE
N KXL + K ) S E
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.

30th Jun 02 68P02900W21-K 5–49
GMR-01
Kiloport switch extender (KSWX) GSM-001-103
For example:
Table 5-12 KSWX (non-redundant)
Extension KSW (non redundant)
shelves
h 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
Table 5-13 KSWX (redundant)

Extension 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

5–50 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Generic clock (GCLK)
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 first
GCLK.
GCLK planning actions

Determine the number of GCLKs required.
GCLKs = 1 + 1 redundant.

30th Jun 02 68P02900W21-K 5–51
GMR-01
Clock extender (CLKX) GSM-001-103
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 when
expansion 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 to
18 shelves (LAN extension only allows fourteen shelves in a single network
element).
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 each
of the expansion/extension cages.
S For redundancy, duplicate each CLKX (requires a redundant GCLK).
CLKX planning actions

Determine the number of CLKXs required.
N CLKX + ROUND UP ǒE6Ǔ * (1 ) R )

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

5–52 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Local area network extender (LANX)
Local area network extender (LANX)
Introduction
The LANX provides a LAN interconnection for communications between all GPROC2s at
a 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.
N LANX + NBSU * (1 ) R F)
Where: NLANX is: the number of LANX required.

NBSU the number of BSU shelves.
BSU 14

30th Jun 02 68P02900W21-K 5–53
GMR-01
Parallel interface extender (PIX) GSM-001-103
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.

5–54 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Line interface boards (BIB, T43)
Line interface boards (BIB, T43)
Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide
impedance matching for E1 and T1 links.
1.544 Mbit/s) 3 V (peak pulse) line use a BIB.
pulse) 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.
Number of MSIs Number of E1/T1 links
Minimum number of BIBs or T43s = =
3 6

30th Jun 02 68P02900W21-K 5–55
GMR-01
Digital shelf power supply GSM-001-103
Digital shelf power supply
Introduction
A BSSC 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 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 + R F * Number of BSUs
Where: RF is: Redundancy factor


5–56 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Battery backup board (BBBX)
Battery backup board (BBBX)
Introduction
The BBBX provides a backup supply of +5 V dc at 8 A from an external battery to
maintain power to the GPROC2 DRAM and the optical circuitry on the LANX in the event
of a 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.

30th Jun 02 68P02900W21-K 5–57
GMR-01
Non volatile memory (NVM) board GSM-001-103
Non volatile memory (NVM) board
Introduction
The optional non volatile memory board provides the BSC with an improved recovery
facility following a total power loss. With the NVM board installed, data is retrieved from
the 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 cage 0 (master) of the BSC, which is an
unused slot.
S The appropriate software required to support the NVM board must be loaded at
the OMC-R and downloaded to the BSC.
NVM planning actions

The NVM board is optional.

5–58 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Verify the number of BSU shelves and BSSC2 cabinets
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 GPROC2
modules.
S Each non-redundant KSW has its own shelf.
S Each extension shelf supports extension of a single KSW.
S The number of KSWX, LANX, CLKX, and GPROC2s is correct.
S The number of MSI/MSI-2 and GDP/XCDR
12 * number of shelves.
S The number of GDP/XCDR
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.

30th Jun 02 68P02900W21-K 5–59
GMR-01
Verify the number of BSU shelves and BSSC2 cabinets GSM-001-103

5–60 68P02900W21-K 30th Jun 02
GMR-01
Chapter 6
RXCDR planning steps and rules

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter provides the planning steps and rules for the RXCDR. This chapter
contains:
S RXCDR planning overview.
S RXCDR planning:
– Planning rules for RXCDR to BSC links.
– Planning rules for RXCDR to MSC links.

30th Jun 02 68P02900W21-K 6–1
GMR-01
Remote transcoder planning overview GSM-001-103
Remote transcoder planning overview
Introduction
To plan the equipage of an RXCDR, certain information must be known. The major items
include:
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 number
of slots required at the RXCDR.

6–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Remote transcoder planning overview

Planning a RXCDR involves the following steps, which are all described in detail in this
chapter:
1. Plan the number of links between the XCDR and BSC site(s), refer to the section
RXCDR to BSC links.
2. Plan the number of E1 or T1 links between the RXCDR and MSC site(s), refer to
the 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 GDP/XCDRs required, refer to the section Transcoding.
interface (MSI, MSI-2).
switch (KSW).
7. Plan the number of RXU shelves, refer to the section RXU shelves.
extender (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).
(PIX).
(BIB, T43).
14. Plan the power requirements, refer to the section Digital shelf power supply.
(BBBX).
16. Decide whether an NVM board is required, refer to the section Non volatile
memory (NVM) board.
17. Verify the planning process, refer to the section Verify the number of RXU
shelves and BSSC cabinets.

30th Jun 02 68P02900W21-K 6–3
GMR-01
RXCDR to BSC links GSM-001-103
RXCDR to BSC links
Introduction
The number of E1 or T1 links between the RXCDR and the BSCs is the number required
to support the A-interface from the RXCDR to the BSC.
This text should be read in conjunction with the BSS planning diagram, Figure 6-1.
MSC
TRANSCODER
A INTERFACE (TERRESTRIAL LINKS) 1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK *
–C7 SIGNALLING LINKS 1 x 64 KBIT/S CIRCUIT/ XBL
–X.25 CONTROL LINK * 1 x 64 KBIT/S CIRCUIT/4 TRUNKS
1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK*
1 x 64 KBIT/S CIRCUIT/TRUNK
GDS INTERFACE **
– GDS TRAU CHANNELS THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED
– GSL LINKS FROM THE # OF TRUNKS REQUIRED TO CARRY THE
SUMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS,
BSC TO PCU TYPICALLY USING 1% BLOCKING) FROM ALL BTSs
GDS–TRAU – PLUS –
CIRCUITS THE # OF GDS TRAU LINKS (DETERMINED FROM THE
GBL PCU NUMBER OF GPRS TIMESLOTS UNDER A BSC)
THE # OF GSLs – PLUS –
THE # OF GBLs THE # OF C7 SIGNALLING LINKS
– PLUS – (IF APPLICABLE*)
1 x 16 KBIT/S CIRCUIT /
GPRS TIMESLOT – PLUS –
1 x 64 KBIT/S GSL LINK THE # OF XBL LINKS
– PLUS –
THE # OF GSL LINKS
BSC
1 x 64 KBIT/S OF 1 x 16 KBIT/S SCU CIRCUIT/LAPD

SIGNALLING LINK
MOTOROLA BSC/BTS INTERFACE
2 x 64 KBIT/S CIRCUITS/DRCU/SCU
NON-BLOCKING
1 x 16 KBIT/S GSL CIRCUITS/TIMESLOT
THE # OF TCHs REQUIRED (USING TYPICALLY 2%

BLOCKING) TO CARRY SUBSCRIBER TRAFFIC.
THE TCHs PLUS THE REQUIRED SIGNALLING TSs
DIVIDED BY EIGHT DETERMINES THE CARRIERS
REQUIRED (ON A BTS/SECTOR BASIS)
BTS
AIR INTERFACE TRANSCODING MUST BE LOCATED AT THE

–TCHs, PDTCHs AND SIGNALLING TSs
–TYPICALLY 2% BLOCKING FOR CS BSC, OR BETWEEN THE BSC AND MSC.
TRAFFIC
TCH = TRAFFIC CHANNEL
AIR INTERFACE TS = TIMESLOT
(TRAFFIC IN ERLANGS) * X.25 MAY BE PASSED TO RXCDR
OR MSC SITE
** GDS–TRAU AND GSL ARE
CARRIED ON SEPARATE LINKS


6–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 RXCDR to BSC links
E1 interconnect planning actions

Determine the number of E1 links required.
C + X + B64 + (T + B16) / 4
N BSC*RXCDR +
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 to
the OMC-R) through the RXCDR.
B64 the number of 64 kbit/s XBL links.
T the number of trunks between the MSC and the
BSC.
NOTE Each E1 link carries up to 120 trunks with a signalling link or 124
trunks without a signalling link. Redundant E1 links carrying extra
trunks may be added.
T1 interconnect planning actions

Determine the number of T1 links required.
C + X + B64 + (T + B16) / 4
N BSC*RXCDR +
24
Where: NBSC-RXCDR is: the minimum number of T1 links required.

C the number of C7 signalling links to the MSC.
the OMC-R) through the RXCDR.
BSC.
NOTE Each T1 link carries up to 92 trunks with a signalling link or 96

trunks without a signalling link. Redundant T1 links carrying extra
trunks may be added.

30th Jun 02 68P02900W21-K 6–5
GMR-01
RXCDR to MSC links GSM-001-103
RXCDR to MSC links
Introduction
The number of E1 or T1 links between the RXCDR and the MSC is the number required
to support the A-interface from the RXCDR to the MSC.
E1 interconnect planning actions

Determine the number of E1 links required.
The minimum number of E1 links required for the A-interface is the greater of two
N RXCDR*MSC + T
30
C+ X+T
N RXCDR*MSC +
31
Where: NRXCDR-MSC is: the minimum number of E1 links required.

C the number of MTL links (C7 signalling links) to
the MSC.
the OMC-R) through the MSC.
BSC.
T1 interconnect planning actions

Determine the number of T1 links required.
C+ X+T
N RXCDR*MSC +
24
Where: NRXCDR-MSC is: the minimum number of T1 links required.

the MSC.
BSC.

6–6 68P02900W21-K 30th Jun 02
GMR-01
Generic processor (GPROC2)
Introduction
Generic processor (GPROC) boards are used throughout the Motorola BSS as a control
processor.
The following factors should be considered when planning the generic processor boards
at 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 master

and standby BSP slots in cage 0.
GPROC planning actions

An 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 into
account in this planning.

30th Jun 02 68P02900W21-K 6–7
GMR-01
Transcoding
Introduction
Transcoders (XCDRs) provide the interface for the E1 (or converted T1) links between
the MSC and the BSC. The XCDR performs the transcoding/rate adaption function which
converts the information on the trunks to 16 kbit/s.
Figure 6-2 shows sub-multiplexing and speech transcoding at the RXCDR.
S Each trunk requires a quarter (1/4th) of a 64 kbit/s circuit between the RXCDR and
BSC.
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 BSC HORIZONMACRO BTS
M M M
S S S M ONE RF
X I K I N C C CARRIER
M K I/
C / S / I U T
S S M
D M W M U F U
C W S
R I S S
2 I I
2 2
64 kbit/s 4 TRUNKS PER 64 kbit/s

A–LAW 64 kbit/s CIRCUIT 4 TCHs
TRUNKS
THE KSW SUBRATE

SWITCHES 16 kbit/s 8 x 22.8 kbit/s
THE XCDR TRANSCODES 64 kbit/s TIMESLOTS. TIMESLOTS
A–LAW PCM TO/ FROM 13 kbit/s THE CTU ENCODES/DECODES
MAPPED ONTO 16 kbit/s, AND 13 kbit/s TO/FROM 22.8 kbit/s FOR 8
SUBMULTIPLEXES 4 TRUNKS TIMESLOTS, AND SUBMULTIPLEXES 4
TO/FROM 1 x 64 kbit/s CIRCUIT. (13 kbit/s MAPPED ON 16 kbit/s)
TIMESLOTS ONTO 1 x 64 kbit/s CIRCUIT,
OR THE OTHER WAY AROUND.

6–8 68P02900W21-K 30th Jun 02
GMR-01

S A GDP/XCDR can process 30 voice channels (GDP-E1/XCDR) or 24 voice
channels (GDP-T1), will support enhanced full rate speech, uplink/downlink volume
control and is capable of terminating one E1 or T1 link from the MSC.
the MSC.
S The A interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1
below).
required.
S Slot 24 (XCDR 0) in the RXU cage 0 (master) will be lost if an optional NVM board
is required.
T1 conversion
one of two ways. In either case the conversion may be part of an existing network
element or a standalone network element which would appear as a RXCDR.

simplest method but uses at most 23 of the transcoding circuits on the XCDR. This
T1 links.
With KSW switching

For better utilization of the GDP/XCDRs a mapping of five T1 circuits onto four E1
T+E
m=
2


30th Jun 02 68P02900W21-K 6–9
GMR-01
Planning actions for transcoding at the RXCDR

The number of transcoders at the RXCDR is proportional to the number of E1 or T1 links
between the RXCDR and the MSC.
Using E1 links
Each GDP/XCDR card can terminate one E1 link.
Using T1 links
Each GDP card can terminate one T1 link. See T1 conversion (described previously) for
XCDR.

6–10 68P02900W21-K 30th Jun 02
GMR-01
Introduction
A multiple serial interface provides the interface for the links between a RXCDR site and
other network entities, RXCDR to OMC-R and RXCDR to BSC. An MSI can interface
only E1 links, an MSI-2 can interface both E1 and T1 links.
S Each MSI-2 can interface two E1/T1 links.


S When one remote transcoder site is supporting multiple BSCs, each BSC requires
its own E1 interface(s) as follows:
– The number of MSI/MSI-2s should be equal to half the number of RXCDR to
BSC E1 or T1 links. Redundancy requires additional links and MSI/MSI-2s.
– If the OMLs (X.25 links) do not go through the MSC, a dedicated E1 or T1
link (half an MSI/MSI-2) is required for the X.25 links to the OMC-R.
– At least one MSI/MSI-2 is required for every eight GDP/XCDR modules.
Additional MSI/MSI-2s will be used if the links are not fully occupied.
If the XCDR is using all 30 ports in a T1 network, use one MSI-2 for
approximately every ten GDPs.
– Additional E1 or T1 links may be required to concentrate X.25 links from
other network entities.
– Each BSC may use one to four 64 kbit/s or 16 kbit/s channels for XBL fault
management communications. Refer to Technical Description: BSS/RXCDR
(GSM-100-323A) or Service Manual: BSC/RXCDR (GSM-100-030) for more
details.
OMC-R.
If the OML links go directly to the MSC, the master slot should be filled with an
XCDR, otherwise the slot should be filled with an MSI/MSI-2 which terminates the
E1/T1 link caring the OML link to the OMC-R. These E1/T1 links do not need to go
directly to the OMC-R, they may go to another network element for concentration.

30th Jun 02 68P02900W21-K 6–11
GMR-01
MSI planning actions
With E1 links
Determine the number of MSI or MSI-2s required.
NBSC*RXCDR
N MSI +
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 this
chapter).
With T1 links
If MSI-2s are used, T1 to E1 conversion is not needed. Therefore the number of MSI-2s
required is:
NBSC*RXCDR
N MSI +
2

chapter).
If MSIs are used, conversion becomes necessary. Therefore the number of MSIs
required is:
NBSC*RXCDR
N MSI + )m
2

chapter).
m the number of MSI-2s used for T1 to E1
conversion.

6–12 68P02900W21-K 30th Jun 02
GMR-01
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 expanded
by adding up to three additional KSWs, giving a total switching capacity of 4096 x
64 kbit/s or 16384 x 16 kbit/s ports, of which 8 x 64 kbit/s timeslots are reserved by
the 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 RXCDR
that require TDM timeslots are:
N = (G * n) + (R * 16) + (M * 64)

gproc_slots database parameter).
M the number of MSI/MSI-2s (do not count MSI-2s
which are doing on-board E1 to T1 conversion,
when determining TDM bandwidth).

30th Jun 02 68P02900W21-K 6–13
GMR-01

S Determine the number of KSWs required.
(G * n) + (R * 16) + (M * 64)
N=
(1016)

G the number of GPROC2s (or GPROCs).
GPROC_slot database parameter).
which are doing on-board E1 to T1 conversion).

6–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 RXU shelves
RXU shelves
Introduction
The number of RXU shelves is normally a function of the number of MSI/MSI2s and
GDP/XCDRs 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 differentiated
by the presence of the KSW. Extension shelves are those which do not contain a
primary KSW. Shelves containing a KSW are called expansion shelves.
S An extension shelf extends the TDM highway. It is constrained to the same
number of (aggregate) timeslots as the shelf containing the KSW.
S An expansion shelf adds an additional TDM highway. It increases the number of
timeslots to that of the additional KSW.
S The number of devices that can be served by a KSW is governed by the TDM
timeslot allocation required for each device. This is discussed previously in the
KSW Planning considerations. The number and type of shelves can then be
determined from the devices required.
For example:
Two shelves, each equipped with three MSI/MSI-2s and 16 GDP/XCDRs, can
be served by a single KSW.
If each shelf has five MSI/MSI-2s with 14 GDP/XCDRs, the KSW can serve
only one shelf, and two KSWs will be required.
S The existing RXU shelf has connectivity for up to five MSI/MSI-2s (2 x E1
connections). The remaining 14 slots have one E1 connection. All slots may be
used for GDPs/XCDRs 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:
R X + max M
5
ǒ , (R ) N NVM)ń16 Ǔ
Where: Rx is: the minimum number of RXU shelves required.
NNVM the number of optional NVM boards (0 or 1).

30th Jun 02 68P02900W21-K 6–15
GMR-01
Introduction
The KSWX extends the TDM highway of a RXU to other RXUs and supplies clock
signals to all shelves in multi-shelf configurations. The KSWX is required whenever a
network element grows beyond a single shelf.
S KSWXs are not required in a single shelf configuration (that is, when expansion or
extension is not required).
multiple KSWs.
that shelf and in shelves that do not have KSWs to drive both the local TDM
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.
N KXE + K * (K * 1)
N KXR + SE
N KXL + K ) S E
Where: NKX is: the number of KSWX required.

SE the number of extension shelves.

6–16 68P02900W21-K 30th Jun 02
GMR-01
For example:
shelves
h 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

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

30th Jun 02 68P02900W21-K 6–17
GMR-01
Generic clock (GCLK) GSM-001-103
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

6–18 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Clock extender (CLKX)
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, when
18 shelves (LAN extension only allows fourteen shelves in a single network
element).

Determine the number of CLKXs required:
N CLKX + ROUND UP ǒE6Ǔ * (1 ) R )

F

E the number of shelves.
(1 if redundancy required (recommended),

30th Jun 02 68P02900W21-K 6–19
GMR-01
LAN extender (LANX) GSM-001-103
LAN extender (LANX)
Introduction
The LANX provides a LAN interconnection for communications between all GPROC2s at
a site.

N LANX + NRXU * (1 ) R F)

NRXU the number of RXU shelves.
(1 if redundancy required (recommended).
RXU 14

6–20 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Parallel interface extender (PIX)
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

30th Jun 02 68P02900W21-K 6–21
GMR-01
Line interfaces (BIB, T43) GSM-001-103
Line interfaces (BIB, T43)
Introduction
S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544
Mbit/s) 3 V (peak pulse) line use a BIB.
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 in
the cabinet, for example, between RXU and BSU or links used for T1 to E1
conversion.
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.

Number of E1/T1 links
Minimum number of BIBs or T43s =
6

6–22 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Digital shelf power supply
Introduction
A BSSC cabinet can be supplied to operate from either a +27 V dc or –48/–60 V dc
power source.
The following factors should be considered when planning the 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.
Where: RF is: Redundancy factor


30th Jun 02 68P02900W21-K 6–23
GMR-01
Battery backup board (BBBX) GSM-001-103
Introduction
The BBBX provides a backup supply of +5 V dc at 8 A from an external battery to
maintain power to the GPROC DRAM and the optical circuitry on the LANX in the event
of a mains power failure.
S One BBBX is required per shelf.


6–24 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Non volatile memory (NVM) board
Non volatile memory (NVM) board
Introduction
The non volatile memory board provides the Remote Transcoder with an improved
recovery facility following a total power loss. With the NVM board installed, data is
retrieved from the 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 RXCDR.
S The NVM board uses slot 24 on the RXU cage 0 (master) of the RXCDR. In the
case that a XCDR board is already occupying that slot, the XCDR board and
associated interface cabling can be moved from slot 24 to the spare slot. If there
are no spare slots, then the XCDR board occupying slot 24 must be removed to
accommodate the NVM board, with a subsequent reduction in capacity of the
RXCDR.
S The appropriate software required to support the NVM board must be loaded at
the OMC-R and downloaded to the RXCDR.
NVM planning actions

The NVM board is optional.

30th Jun 02 68P02900W21-K 6–25
GMR-01
Verify the number of RXU shelves and BSSC cabinets GSM-001-103
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.

6–26 68P02900W21-K 30th Jun 02
GMR-01
Chapter 7
PCU upgrade for the BSS

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter provides the following information for the PCU upgrade to the BSS to
support 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 BSS – PCU planning example for GPRS.

30th Jun 02 68P02900W21-K 7–1
GMR-01
BSS planning for GPRS GSM-001-103
BSS planning for GPRS
Introduction to BSS planning for GPRS

The BSS planning process for GPRS may involve adding additional BSS equipment and
software to the BSS, in addition to the PCU hardware and software. The extent of the
additional BSS equipment depends on the amount of traffic expected to be carried over
the 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 is
intended to provide the network planner with the rules to determine the number of GPRS
timeslots that are to be provisioned at the BTS, subsequently provisioned in PCU
hardware, and provisioned with communication links.
The BSS planning process described here focuses on the provisioning of the PCU
hardware 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 the
entire document from a planning perspective.

7–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS planning for GPRS
PCU to SGSN interface planning

The PCU to SGSN interface is referred to as the Gb Interface. The Gb interface
connects the BSS PCU to the GPRS SGSN. Motorola supports three Gb interface
options (options A, B, and C), as shown in Figure 7-1.
Figure 7-1 Gb interface alternatives
MSC
A INTERFACE
RXCDR Gb OPTION A
Gb OPTION B
OMC-R BSC
FOR OPTION A
and B
PCU
Gb OPTION C
BTS1 BTSn
The RXCDR can be used as an E1 switching interface between the PCU and SGSN, as
shown in option A.
Alternatively, the BSC can be used as an E1 switching interface, as shown in option B.
Option C is the case where there is no BSS E1 switching element between the PCU and
SGSN.
The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. The
PCU is connected directly to the BSC E1 interfaces and the BSC is configured to provide
the E1 master clock. If the PCU is connected to a GSN that does not have a master
clock source, some interface equipment that does have a master clock source (such as a
DACs) should be used. The Motorola BSC and RXCDR equipment can be used in place
of a DACs for this purpose.
When an RXCDR or BSC is used as a E1 switching element, as shown in option A and
option B, respectively, additional equipment provisioning of these network elements may
be required in order to support the PCU E1 interfaces, in accordance with the
provisioning rules for adding E1 interfaces to the RXCDR and BSC network elements.

30th Jun 02 68P02900W21-K 7–3
GMR-01
Feature compatibility
Alarms consolidation
No additional BSS or GPRS network planning is required.
PCU device alarms impact only PCU functional unit severity, and not the cell functional
unit severities. Therefore, the impact is to the following PCU devices: DPROC and PCU
System Processor (PSP).
BSC-BTS dynamic allocation

The dynamic allocation feature specifies how the BSC configures and shares the
terrestrial backing between the GPRS data traffic and the Circuit-Switched (CS) traffic.
The terrestrial backing, between the BTS and BSC, must have enough capacity to carry
the radio timeslots assigned to both GPRS and circuit switched. If there is not enough
capacity, because there are not enough physical channels, the BSC allocates the
backing to CS first. The remaining capacity is assigned to GPRS (reserved GPRS
timeslots first, and then to switchable GPRS timeslots).
Any terrestrial backing resources not used by circuit-switched calls are allocated for
switchable use. However, circuit-switched calls can take resources away from the
switchable pool when traffic demands require more terrestrial capacity. Terrestrial
resources available in the switchable pool are available for GPRS traffic use.
The BSC may reassign GPRS switchable or reserved backing to CS if backing is
required for emergency circuit-switched calls. In this case, the backing is reassigned so
that the remaining GPRS radio timeslots within a carrier are contiguous.
The CS3/CS4 feature, which requires 32 kbit/s bandwidth on backhaul, has been
designed 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 handling
network capability for GSM voice and circuit data traffic. Additional loading on the BSS
elements, due to the GPRS traffic, may require additional BSS equipment and interface
circuits to be added.
There are three classes of mobile devices, which permit non-simultaneous attachment to
the circuit-switched and packet data channels. This means that the BSS does not need
to be provisioned to simultaneously handle the call processing and signalling for both
circuit-switched traffic and GPRS packet data services on a per subscriber basis. The
BSS treats class A mobiles like class B mobiles. Therefore, the BSS part of the network
supports the simultaneous attachment, activation, and monitoring of circuit-switched and
packet data services. Simultaneous GPRS and circuit-switched traffic is not supported.
The mobile user can make and/or receive calls on either of the two services sequentially,
but not simultaneously. The selection of the appropriate service is performed
automatically.
Concentric cells
GPRS timeslots are available in the outer zone carriers.

7–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS planning for GPRS
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 the
switchable GPRS timeslots, but it cannot reconfigure the reserved GPRS timeslots under
any circumstances.
Directed retry
The BSC uses directed retry to relieve cell congestion by redistributing traffic across
cells. For the GPRS traffic part of the BSS, the BSC treats switchable GPRS timeslots
like 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 select
the 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 timeslot
that 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 to
35 kilometres. This range extension is not supported for GPRS.
Frequency hopping and redefinition

The GSM radio uses slow frequency hopping to improve data reliability and to increase
the number of active users. The GPRS timeslots assigned to the uplink and downlink
channels must have the same frequency parameters. GPRS may have a different
timeslot activity factor to voice, and thereby causes the cell C/I performance to change
from a GSM-only system.
The frequency redefinition feature extends the GSM 4.08 capabilities to GPRS.

30th Jun 02 68P02900W21-K 7–5
GMR-01
Global reset
The global reset procedure initializes the BSS and MSC in the event of a failure. A global
reset does not affect any resources assigned to GPRS.
Integrated Horizon HDSL interface

No additional BSS or GPRS network planning is required other than to plan for the GDS
link.
The PCU does not support a high bit-rate subscriber line (HDSL) between the PCU and
the BSC. However, the BSC can use an MSI board (with HDSL capabilities) to terminate
a GDS link to the PCU if an E1 is used for the connection.
Multiband handovers
The BSC treats switchable GPRS timeslots like idle TCHs in the case of multiband
handovers.
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 flow
control for the circuit-switched mobiles feature.

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

The CBCH can reside on a switchable GPRS timeslot. Therefore, switchable GPRS
timeslots may be reconfigured as SDCCHs. However, GPRS reserved timeslots cannot
be reconfigured as SDCCHs.
SD placement prioritization
A GPRS carrier cannot be configured so that the sum of the number of SDCCHs allowed
and the number of GPRS timeslots, exceed the capacity of the carrier.

7–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS upgrade to support GPRS
BSS upgrade to support GPRS
BSS upgrade provisioning rules

Table 7-1 identifies the BSS network elements that may require upgrading to support
GPRS. Consult the relevant planning information for the chassis-level planning rules
covering the BSC, BTS, OMC-R, and RXCDR.
The PCU provisioning rules are described later in this chapter.
Table 7-1 BSS upgrade in support of GPRS

Equipment Additional BSS upgrade
element
BSC Chassis Add KSWs, LCF GPROC2s, MSIs per BSC as needed
(optional) in support of the Gb, GDS TRAU, GDS LAPD (GSL),
RSL, BSC-BTS traffic carrying E1 links.
BTS (BTS4, Replace Provision with DRCU2/3 or later version transceivers.
BTS5, BTS6, DRCU with Follow BTS provisioning rules for the number of
ExCell, DRCU2/3 transceivers required at the BTS and other supporting
TopCell) boards, including DHP processor boards, as
necessary. The same carrier dimensioning rules can be
used for a GPRS carrier as for a circuit-switched
carrier. (The TSW must be replaced with the KSW
when GPRS support of the BSC-BTS dynamic
allocation feature is enabled.)
OMC-R Software One per 64 BSS network elements, with any mix of
upgrade for circuit or packet (GPRS) channels supported; software
GPRS in support of the PCU.
support
RXCDR Chassis Add KSWs, GPROC2s, MSIs per RXCDR as needed
(optional) to support the Gb interface shown as option A in
Figure 7-1.

30th Jun 02 68P02900W21-K 7–7
GMR-01
BSS upgrade to support GPRS GSM-001-103
Maximum BSS configuration

Table 7-2, Table 7-3 and Table 7-4 provide the maximum BSS network parameter values
in support of GPRS per BSS network element.
Table 7-2 Maximum BSS network parameter values in support of GPRS (part A)
Network Network Parameter Maximum Value
Element
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 each 4
direction
BSS (BTS) Timeslots per active user DL 4
BSS (BTS) Timeslots per active user UL 1
BSS (BTS) Switchable GPRS timeslots 8
per carrier
BSS (BTS) Reserved GPRS timeslots per 8
carrier
BSS (BTS) Switchable GPRS timeslots 30
per cell
BSS (BTS) Reserved GPRS timeslots per 30
cell
BSS (PCU) Air interface timeslots 240, see Figure 7-3.
processed at any instance in
time (with redundancy)
BSS (PCU) Total air interface timeslots 960, see Figure 7-3.
(with redundancy) *
BSS (PCU) Air interface timeslots 270, see Figure 7-4.
time
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 PCU
can support traffic, unlike in previous releases where only 270
timeslots could be used to originate traffic at any instance in
time. All additional calls attempts were blocked. This is now
possible because of rapid multiplexing of four sets of 30
timeslots by the PRP. The data throughput, however, is still
limited to 30 timeslots per PRP and 270 per PCU in
non-redundant configuration.

7–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS upgrade to support GPRS
Table 7-3 Maximum BSS network parameter values in support of GPRS (part B)
Element
PCU Air interface timeslots 30 at any instance in time;
(PRP DPROC) processing per PRP 120 total timeslots.
PCU GDS TRAU E1 interface 6, if every TRAU-type GDS E1
(PICP DPROC) handled per PICP handles 124×16 kbit/s timeslots.
Actually, the PICP number is tied
with total timeslots number a PICP
processor can support. In other
words, one PICP board is required
per 744×16 kbit/s timeslots.
3, if every TRAU-type GDS E1
handles 62x32 kbit/s timeslots. That
is, 372×32 kbit/s timeslots per PICP.
PCU PCU-SGSN (Gb) interface 1 Gb E1 to carry frame relay
(PICP DPROC) channellized or non channellized
GPRS traffic per 150 active CS
timeslots deployed over the BSC to
PCU interface. The Gb E1 carries
both data and signalling traffic
between 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 sites 100
supported
GSL E1 links Max. physical E1s between 2
BSC & PCU (one primary E1
and one redundant)
LAPD-type Max. per E1 link (corresponds 6
GDS (GSL) to a quantity of six 64 kbit/s
links LAPD channels)
TRAU-type Max. per PCU 18
GDS links
(E1s)

30th Jun 02 68P02900W21-K 7–9
GMR-01
BSS upgrade to support GPRS GSM-001-103
Table 7-4 Maximum BSS network parameter values in support of GPRS (part C)
Element
GBL links (E1s) Max. per PCU 4
Gb PVCs Max. on one bearer Link 318
T43 boards Max. per PCU 4
Cable To connect 4 x T43 sites 2
harnesses
Gb frame relay Max. 1600 bytes
frame octet size
NOTE The total number of air interface timeslots supported by the PCU
is affected by the fact that all of the timeslots of a cell are
allocated to the same PRP board. Allocation of a portion of the
GPRS timeslots for a cell to one PRP and another portion of the
GPRS timeslots of the same cell to a different PRP is not
supported. This fragmentation of the cells across PRP boards
may result in not all GPRS timeslots for a cell being assigned to
a PRP and may even result in not all cells being assigned to a
PRP. When planning the BSS, if the number of GPRS timeslots
in the BSS does not exceed max_GPRS TSg, all GPRS
timeslots 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 per
PCU 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 in
the BSS with the most GPRS timeslots.
Note that there are special cases where 120 timeslots are
guaranteed to be assigned per PRP board. These special cases
are where all the cells in the BSS with GPRS timeslots have the
same number of GPRS timeslots and the number of GPRS
timeslots 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 be
populated.
Before GSR6, a cable harness is staged with the PCU containing 18 E1 RJ45 to RJ45
cables.
Under GSR6, a second cable harness needs to be caged to hold an extra 6 E1 RJ45 to
RJ45 cables.

7–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 PCU hardware layout
PCU hardware layout

There is one PCU per BSS. Figure 7-2 shows the PCU shelf layout.
Figure 7-2 PCU shelf layout
DEFAULT LAPD DEFAULT LAPD

LINKS TO BSC LINK TO BSC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
D D D D D D M M D D D D D D
P P P P P P P P P P P P P P
R R R R R R R R R R R R R R
O O O O O O O O O O O O O O
C C C C C C C C C C C C C C
A B
DEFAULT LAPD DEFAULT LAPD

LINK TO BSC LINKS TO BSC
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
D D D D D D H M H M D D D D D D
P P P P P P S P S P P P P P P P
R R R R R R C R C R R R R R R R
O O O O O O O O O O O O O O
C C C C C C A C B C C C C C C C
T T T T T T B A T T T T T T
M M M M M M M M M M M M
T T
M M
NOTE Any two of the three available default LAPD link slots may be
used.

30th Jun 02 68P02900W21-K 7–11
GMR-01
PCU shelf (cPCI) GSM-001-103
PCU shelf (cPCI)
Introduction
The PCU cabinet can hold up to three PCU (cPCI) shelves. Each PCU is connected to
only one BSC, so one PCU cabinet can serve up to three BSCs. There are no PCU to
PCU interconnects within the cabinet.
Each cabinet is pre-wired with a panel in the rear of the cabinet for the desired E1
termination type, balanced 120 ohm, or unbalanced 75 ohm terminations with 1500 volt
lightning protection per E1.
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 time
per 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 in
the fully redundant configuration (see Figure 7-2).
S 3 fan/power supply units per cPCI shelf provide N+1 hot-swap redundancy. A
minimum 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. MPROC
redundancy is not required for normal PCU operation, but is necessary for the
PCU to achieve high availability.
S Each MPROC board requires one bridge board and one transition module for a
redundant 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 auxiliary
equipment such as tape drives, CD-ROM drives, and hard disks. The PCU is
configured without any auxiliary equipment and this area of the shelf is covered
with blank panels.
NOTE Additional T43 modules and interconnect cables are required for
the PCU cage to support 18 GDS TRAU links.

7–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 MPROC board
MPROC board
Introduction
The PCU planning process determines the type and number of MPROC boards to
populate in the PCU. The PCU provisioning requirements take the MPROC redundancy
solution 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 bus
synchronization and arbitration. It also performs centralized configuration and fault
handling 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 should
be enabled. The MPROC cards should be inserted in slot 7 and 9 (see Figure 7-2). A
MPROC (PSP 0) card is inserted into slot 7 and the other MPROC (PSP 1) is inserted
into slot 9. MPROC (PSP 0) in slot 7 is paired with a hot swap controller/bridge module in
slot 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 or
9 of the PCU cage. The MPROC redundancy flag specified during the equipping of the
PCU should be disabled. The MPROC (PSP 0) in slot 7 is paired with a hot swap
controller/bridge module in slot 10 or MPROC (PSP 1) in slot 9 is paired with a hot swap
controller/bridge module (HSC) in slot 8. If both MPROCs are present but redundancy is
not desired or the equip flag is disabled, the MPROC in slot 7 is the primary MPROC and
is responsible for powering off the MPROC in slot 9. In this case, the MPROC in slot 9 is
considered transparent.
For a non redundant solution, no inter-MPROC connection (RS232 or Ethernet) is

required.
The MPROC card is a Motorola MCP750HA microprocessor board with a TMCP700

transition module.

30th Jun 02 68P02900W21-K 7–13
GMR-01
DPROC board GSM-001-103
DPROC board
Introduction
The PCU planning process determines the type and number of DPROC boards to
populate in the PCU. The PCU provisioning requirements use the number of GPRS
timeslots as the planning rule input. The estimation process for determining the number
of GPRS timeslots is provided in GPRS network traffic estimation and key concepts
in Chapter 3.
Planning considerations (PICP or PRP use)

DPROC board slots can be used for either PICP or PRP purposes. Each DPROC has an
E1 transition module mounted in the rear of the shelf directly behind it.
A DPROC may be configured as a PICP with zero, one, or two E1 PMC modules, and
with PICP software. The DPROC may be configured as a PRP with up to two E1 PMC
modules, and with PRP software.
The PICP provisioned boards should be populated from left to right. For system
availability reasons, PICPs should be evenly distributed between the two backplanes
within the PCU shelf. The left and right backplanes are connected together through the
bridge board located behind the MPROC processor board. Therefore, the first PICP
would occupy board slot 1, PICP 2 would occupy board slot 11, PICP 3 would be in slot
2, and PICP 4 in slot 12.
PRP provisioning should also be performed in a similar fashion, alternating provisioned
boards 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 GDS
E1 handles 124 x 16 kbit/s timeslots. Actually, the PICP number is tied with the
total timeslots number a PICP processor can support. In other words, one PICP
board is required per 744 × 16 kbit/s timeslots or 372 × 32 kbit/s timeslots.
S N+1 board redundancy is supported.

7–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 DPROC board
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 PICP
redundancy, Gb link redundancy, LAPD-Type GDS redundancy, and TRAU-type
GDS link redundancy.
S PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module, but
cannot 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 of
timeslots processed at any instance to 30 for each PRP. Therefore, one E1
carrying 124 active timeslots can supply up to five PRPs with active timeslots. The
software load balances, in this case, such that four of the PRPs receives 25 active
timeslots and the fifth receives 24.
NOTE The actual distribution of timeslots may be slightly different from

that shown here depending on cell configurations. That is, all
timeslots for a single cell must terminate on a single PRP, which
can lead to slight imbalances when multiple timeslots are
configured per cell.
S A PRP board has up to two PMC modules.

S N+1 board redundancy is supported.

30th Jun 02 68P02900W21-K 7–15
GMR-01
PMC module GSM-001-103
PMC module
Introduction
The number of PMC modules installed depends on the number of PICP and PRP
configured 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 PMC
module.
S Only one TRAU-type GDS per PMC module on a PRP board is allowed. The other
E1 termination on the PMC module cannot be used.
S Each PMC processor in the PCU is capable of processing 124 x 16 kbit/s TRAU
channels or 62 x 32 kbit/s TRAU channels.
S Up to two Gb E1 links per PMC module is allowed.

7–16 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Transition module
Transition module
Introduction
The number of transition modules installed depends on the number of PICP and PRP
configured boards in the PCU.
The following factors should be considered when planning the number of transition
modules required:
S One transition module is required per PRP board.
S One transition module is required per PICP board.

30th Jun 02 68P02900W21-K 7–17
GMR-01
PCU equipment redundancy and provisioning goals GSM-001-103
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 pairs
redundant (requires future software release, redundant configuration not available
in GSR 4.1).
S E1 redundancy requires the provisioning of the redundant hardware with active E1
links. The E1 redundancy is available for GSL, GDS, and GBL links. Load
balancing is performed across the GDS, GSL, and GBL E1 links so that if a link
should fail, the existing load is redistributed to the other links.
PCU redundancy planning

For redundant PCU operation, the PCU should be planned such that there are N+1
boards provisioned as shown in Figure 7-3. That is, only eight PRP boards and two PICP
boards are required to handle the expected maximum GPRS traffic load. The ninth PRP
board and third PICP board offer the N+1 hardware redundancy. The third PICP board
provides redundancy for the software processes that run on the first two PICP boards.
For a fully configured PCU with nine GDS TRAU E1s, at least two PICP boards are
required in order to provide enough processing capability.
The GDS TRAU E1 link redundancy is obtained with the N+1 PRP board. The GSL E1
link redundancy is obtained by provisioning a second GSL E1 on the second PICP. One
PICP is required per six GDS TRAU E1 links. The PCU load-balances across the GDS
TRAU and LAPD GSL links. If a PRP or PICP board fails, the PCU automatically
re-distributes the load to the other boards in-service.
Two Gb E1s are required to handle the traffic for a fully configured PCU. Gb E1 link
resiliency is obtained by adding an additional two Gb E1s and load balancing across all of
the Gb E1s.
The PRP and PICP (DPROC) boards are hot swappable, so that when a board failure is
detected, a replacement board may be inserted without disrupting ongoing GPRS traffic
on the other boards. The DPROC must be locked before removal, and unlocked following
board insertion. The PRP and PICP boards have associated transition module boards not
shown in the figures below. There is an associated redundant transition module board
with each redundant PRP and PICP board.
The PCU shelf hardware allows for N+1 MPROC board redundancy. This N+1
redundancy capability is subject to MPROC redundancy software availability. The
MPROC board(s) and the MPROC bridge boards are not shown in the figure below, but
the redundant MPROC has an associated redundant bridge board.
The PCU shelf comes with N+1 power supply/fan redundancy. The power supplies are
hot swappable. The power supply/fan units are not shown in figures below.
The PCU architecture offers the network planner a considerable degree of provisioning
flexibility. Figure 7-3 and Figure 7-4 demonstrate this flexibility where the provisioning
goals 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 and
Figure 7-4.

7–18 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 PCU equipment redundancy and provisioning goals
Figure 7-3 Goal: maximum throughput and coverage, fully redundant configuration
124 @ 16k / GDS TRAU

CHANNELS PCU HARDWARE
GDS PRP1
BSC PMC SGSN
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
GDS
PMC PRP2
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
TO
GDS PRP8
PMC
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
REDUNDANT
GDS PRP9
PMC REDUNDANT
REDUNDANT
120 TS MAX.
GDS
PMC 30 TS MAX.
ACTIVE
GSL PMC PICP1
PMC 6 LAPD TS
GBL
REDUNDANT
GSL GBL
PMC PICP2
6 LAPD TS
PMC REDUNDANT
GBL
PMC
PICP3
REDUNDANT
PMC
REDUNDANT
GBL

30th Jun 02 68P02900W21-K 7–19
GMR-01
PCU equipment redundancy and provisioning goals GSM-001-103
Figure 7-4 Goal: maximum throughput and coverage, full redundancy not required
124 @ 16k / GDS TRAU

CHANNELS PCU HARDWARE
GDS PRP1
BSC PMC SGSN
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
GDS
PMC PRP2
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
TO
GDS PRP9
PMC
120 TS MAX.
GDS 30 TS MAX.
PMC ACTIVE
GSL PMC PICP1
PMC 6 LAPD TS
GBL
REDUNDANT
GSL GBL
PMC PICP2
6 LAPD TS REDUNDANT
PMC
GBLs
Refer to Table 7-5 for a matrix of provisioning goals achieved with this instance of PCU
provisioning.
NOTE Figure 7-4 shows18 GDSs, as required for CS3/CS4. Only 9

GDSs are required for CS1/CS2.

7–20 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 PCU equipment redundancy and provisioning goals
Table 7-5 PCU provisioning goals

Metric Goal
Maximum coverage with Maximum coverage,
redundant configuration; redundancy not required;
see Figure 7-3. see Figure 7-4.
Number of timeslots 240 270
time
Total number of provisioned 960 1080
timeslots at a BSS
No. MPROCs 2 1
No. PRPs 8 9
No. PICPs 3 3
No. TRAU-Type GDS E1s 18 18
No. LAPD-Type GDS (GSL) 2 2
E1s
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 PICP
board at a time. This upgrade must adhere to the PICP to GDS TRAU E1 ratio rule, of
one PICP board per six GDS TRAU E1 links if every TRAU-type GDS E1 handles 124 x
16 kbit/s timeslots. Actually, the PICP number is tied with the total timeslots number a
PICP processor can support. In other words, one PICP board is required per 744 x
16 kbit/s timeslots or 372 x 32 kbit/s timeslots.

30th Jun 02 68P02900W21-K 7–21
GMR-01
E1 link provisioning for GPRS GSM-001-103
E1 link provisioning for GPRS
E1 interface provisioning
The BSC to PCU E1 links should not go through any network elements. The E1 links
should meet the ITU-T Recommendation G.703. This recommendation includes an E1
length specification.
The PCU is configured for E1 loop timing recovery on all of the PCU E1 interfaces. The
PCU is connected directly to the BSC E1 interfaces and the BSC is configured to provide
the E1 master clock. If the PCU attaches to a GSN that does not have a master clock
source, an interface piece of equipment, such as a Digital Cross Connect switch (DACs)
that does have a master clock source, should be used. The Motorola BSC and RXCDR
equipment can be used in place of a DACs for this purpose.
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 one
TRAU-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 LAPD
links and the second E1 up to another six. For LAPD-type GDS resiliency, two E1s
are recommended, regardless of the number of LAPD channels required. For
example, if only one channel is required to carry the expected signalling load, two
E1s with one LAPD channel per E1 should be used. The MPROC load balancing
software distributes the load evenly between the two LAPD channels.
GPROC2 LCF
S The GPROC2 LCF available at the BSC needs to terminate 12 LAPD channels in
the 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 capacity
available on the LCFs.
PCU Gb E1
S There may be up to four Gb E1s per PCU.

7–22 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 PCU – SGSN: traffic and signalling planning
PCU – SGSN: traffic and signalling planning
Introduction
The PCU is connected to the SGSN through the Gb interface as a Data Terminal
Equipment (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 using
either 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 on
how 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 reserved
for E1 signalling. Each timeslot uses a rate of 64 kbit/s.
Frame relay bearer channel The bearer channel allows the frame relay protocol to
(FR BC) map its resources to the E1 layer.
Permanent virtual circuit A frame relay virtual circuit. This allows the packet
(PVC) switched FR network to act as a circuit-switched
network by guaranteeing an information rate and time
delay for a specific PVC.
Data link connection A unique number assigned to a PVC end point in a
identifier (DLCI) frame relay network.
Network service entity (NSE) An instance of the NS layer. Typically, one NSE is used
for each PCU being served by a SGSN. The NSE has
significance across the network, and is therefore the
same at the SGSN and PCU.
Network service entity Uniquely identifies a NSE.
identifier (NSEI)
Network service virtual A logical circuit that connects the NSE peers between
circuit (NSVC) the SGSN and PCU. The NSVC has significance across
the network. Therefore, it is configured identically at the
SGSN and PCU.
Network service virtual Uniquely identifies a NSVC. There is a one-to-one
circuit identifier (NSVCI) mapping between the NSVCI and DLCI.
BSSGP virtual circuit (BVC) A logical circuit that connects the BSSGP peers
between the BSS and SGSN. This has significance
across the Gb interface, but is only configured in the
PCU. The PCU contains one point-to-point BVC per an
actively serving cell.
BSSGP virtual circuit Uniquely identifies a BVC.
identifier (BVCI)

30th Jun 02 68P02900W21-K 7–23
GMR-01
PCU – SGSN: traffic and signalling planning GSM-001-103
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 and
dynamically 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 same
timeslot 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 the
network.
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 case
with other vendors, who may use more than one PCU per BSS.

7–24 68P02900W21-K 30th Jun 02
GMR-01
The Gb signalling overhead

This section describes the Gb protocol signalling overhead. The signalling overhead and
the Gb link capacity limitations must be considered in each Gb link plan.
Gb protocol signalling overhead

Table 7-7 shows the corresponding uplink and downlink overhead on the Gb link per
GPRS 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 the
uplink (UL) or the downlink (DL). Since most traffic models assume the majority of data
transfer is in the downlink direction, only the downlink control messaging is considered.
Table 7-8 shows the overhead required on all GPRS mobility management/session
management messages (GMM/SM).
Table 7-8 Overhead on each downlink GMM/SM message
Layer Field Byte Count
LLC Address 1
Control 2
CRC 3
BSSGP PDU type 1
TLLI 6
QoS profile 5
Lifetime 4
Priority 3 (optional)
DRX 4 (optional)
Old TLLI 6 (optional)
IMSI 10
Alignment 5
Bits radio access capability 10
NS Spare 1
PDU type 1
BVCI 2
Frame relay Header 2
Total signalling overhead 66 bytes
Therefore, in the DL direction, the following protocol requirements per signalling message
are applied:
GMM_Signalling_Requirement = Overhead + Message_Contents

30th Jun 02 68P02900W21-K 7–25
GMR-01
Data overhead
Table 7-9 shows the corresponding UL and DL overhead on the Gb link per PDU data
transfer 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 1
Control 3 (typical value for this
variable, max = 36)
CRC 3
BSSGP PDU type 1
TLLI 6
QoS profile 5
Lifetime 4
Priority 3
DRX 4
Old TLLI 6 (optional)
IMSI 10
Alignment 5
Bits radio access capability 10
NS Spare 1
PDU type 1
BVCI 2
Frame Relay Header 2
Total Data Overhead 71 bytes

7–26 68P02900W21-K 30th Jun 02
GMR-01
Determine the net Gb load

Consider the network equipment, traffic model and protocol overheads to determine the
net load that must be delivered to each PCU served by the SGSN.
Base formulae
Use the following base formulae to determine the load expected on the Gb interface:
ISignalling_Data_Rate (bytesńs) +
Subscribers_per_PCU
(324 * PS AttachńDetach ) 111 * RAU ) 162 * PDPActńDeact) * ) 87 * PGPRS
3600
User_Data_Rate (bytesńs) +
ǊSubscribers_per_PCU * Data_per_Subscriber * 1000 * (1 ) PK

71
SIZE
) ǋ
3600
Therefore:
Total_Data_Rate (bytesńs) + Signalling_Data_Rate ) User_Data_Rate
Where: Total_Data_Rate is: defined by the equation above, and

represents the required bandwidth
(bps) for GPRS data transmission
over a GBL interface between the
PCU and SGSN after all of the
protocol and signalling overhead is
accounted for.
Signalling_Data_Rate the required rate (bytes/s) for
GPRS signalling transmission over
a GBL interface between the PCU
and SGSN after all of the protocol.
User_Data_Rate the required rate (bytes/s) for
GPRS user application data over a
GBL interface between the PCU
and SGSN after all of the protocol.
PSATTACH/DETACH the detach rate per sub/BH.
RAU the periodic, Intra and inter routeing
area update rate per sub/BH.
PDPACT/DEACT the PDP context activation/
deactivation rate per sub/busy
hour.
PGPRS the GPRS paging rate (per
second).
PKSIZE the average packet size, in bytes.
Subscribers_per_PCU the average number of subscribers
supported on a PCU.
Data_per_Subscriber the data traffic per subscriber in a
busy hour (kbytes per busy hour).

30th Jun 02 68P02900W21-K 7–27
GMR-01
Gb link timeslots
The traffic and signalling is carried over the same E1 on the Gb link (GBL). The number
of required 64 kbit/s Gb link timeslots can be calculated using the equation given below.
Each E1 can carry up to 31 timeslots. When fewer than 31 timeslots are needed on an
E1, specifying a fractional E1 may be more cost effective.
Total_Data_Rate
No_GBL_TS +
8000 * U GBL
No_GBL_TS
N PCU*SGSN +
31
Where: No_GBL_TS is: the number of timeslots to provision

on the GBL E1 between the PCU
and SGSN. This value can be used
to specify a fractional E1.
Total_Data_Rate defined by the equation in the
previous section, and represents
the required bandwidth (bps) for
GPRS data transmission over a
GBL interface between the PCU
and SGSN after all of the protocol
and signalling overhead is
accounted for.
UGBL the link utilization.
NPCU–SGSN the E1 link between the PCU and
SGSN.

7–28 68P02900W21-K 30th Jun 02
GMR-01
Frame relay parameter values

The network planner needs to specify the values for the following three frame relay
interface 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 text
and illustrated in Figure 7-5.
Figure 7-5 Frame relay parameters

30th Jun 02 68P02900W21-K 7–29
GMR-01
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 Motorola
PCU distributes the use of all the NSVCs by the subscribers evenly in a round-robin
manner. The round-robin algorithm continuously assigns subscribers to the next NSVC in
a sequential manner when a subscriber PDP context is established. If an NSVC
becomes unavailable, it is skipped over, and the next available NSVC in the round-robin
is used. This is the BSSGP feature that inherently provides load sharing over all available
NSVCs. The load sharing capability over multiple Gb links is provided by the BSSGP
high level protocol layer, which results in link resiliency.
The recommended cumulative CIR value for all PVCs should be greater than, or equal
to, half the cumulative information rate of the active timeslots routed to the NSVC. This
mapping is actually determined as a mean load, evenly distributed over all of the
available NSVCs as next described.
Over many cells, it is expected that the PCU will handle the traffic throughput equal to the
number of timeslots planned for the busy hour traffic load.
The recommended frame relay network CIR value is calculated as follows:
F * Total_Data_Rate * 8
CIR_Value +
Num_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 the
net Gb load, and represents the required
bandwidth (bps) for GPRS data transmission
over a GBL interface between the PCU and
SGSN after all of the protocol and signalling
overhead is accounted for.
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 timeslots
is served by the combination of the CIR and Bc frame relay network rated capacity. It
should be noted that this strategy makes use of the overload carrying capacity of the
frame relay network when more than half of the planned timeslots are in use.
When a cell uses all of its provisioned timeslots as active timeslots (that is, timeslots
being processed by the PCU at that instance in time), other cells must use fewer of their
timeslots being processed in order for the overall PCU Gb interface bandwidth allocation
to be within configured frame relay network interface parameter (CIR, Bc, Be) values.
The BSS attempts to utilize as many timeslots as are supported in PCU hardware and in
communication links simultaneously.

7–30 68P02900W21-K 30th Jun 02
GMR-01
Committed burst rate (Bc)

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

The Be is the maximum amount of uncommitted data (in bits) in excess of Bc that a
frame relay network can attempt to deliver, during a time interval Tc. The network treats
Be data as discard eligible.

30th Jun 02 68P02900W21-K 7–31
GMR-01
BSS – PCU hardware planning example for GPRS GSM-001-103
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 link
provisioning 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 relevant
planning rules for adding additional E1 interface hardware in support of the GDS and
GSL links.
The provisioning of the SGSN hardware is not covered in this planning guide.
Figure 7-6 PCU equipment and link planning
GDS
BSC PCU SGSN
1 to 18 E1s
GBL
GSL
1 to 4 E1s
1 or 2 E1s
GSM + GPRS E1s
BTS

7–32 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSS – PCU hardware planning example for GPRS
BSS – PCU planning example

Use this example to provision a BSS with 10 sites consisting of 20 cells with one GPRS
carrier per cell with the following GPRS call model:

Traffic per sub/BH (kbytes/hr) – uplink ULRATE = 30
Traffic per sub/BH (kbytes/hr) – downlink Data_rate_per_sub = 65
PDP context activation/deactivation (per sub/BH) PDPACT/DEACT = 0.5
GPRS users per cell 250
Average 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 in
Chapter 3) to determine what the values to use for CS rate and BLER for the
chosen cell RF plan. For this example, use for the 1x3 2/6 hopping RF plan.
Step 2: Determine number of GPRS carrier timeslots

Use the equation below to determine the number of GPRS timeslots that are
required on a per cell basis. In order to use this equation, the network planner
should have the expected cell load in kbit/s.
GPRS_Users * Data_rate_per_sub * 8
Mean_traffic_load (kbitńs) +
3600
+ 250 * 65 * 8 X 36 kbitńs
3600
No_PDCH_TS + Roundup ǊTS_Data_Rate

Mean_traffic_load
* Mean_load_factor
ǋ
No_PDCH_TS + 36 +6
12.68 * 0.5
Therefore, provision 6 timeslots on the cell.

30th Jun 02 68P02900W21-K 7–33
GMR-01
Step 3: Calculate the number of GDS E1 links

Compute the number of GDS TRAU E1 channels required for the air interface
timeslots required to carry the traffic. Remember, each CS1/CS2 timeslot requires
16K TRAU channel and CS3/CS4 timeslots requires 32K TRAU on GDS TRAU
interface. Also, CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for
that carrier would require 32K TRAU. For this case it can calculated that 2 GDS
TRAU E1s are required.
20 Cells * 6 TSńCell * 32kńTS
Total GDS E1s + + 2 E1s
31 * 64k
Each PRP board can process 30 active timeslots at any given time for a total of
120 timeslots. Assuming that we need to provide coverage to at least half of the
timeslots at any instance, the number of mean PDCHs = 3 from step 2, the
number of PRPs required to serve 20 cells is:
(3 active timeslots per cell) * (20 cells per BSC)
+ 2 PRPs
(30 active timeslots per PRP)
These 2 PRPs have more than enough capacity to handle the additional 3 standby
timeslots per cell. Using the conservative provisioning rule of one GDS TRAU E1
per PRP, we would provision 2 GDS TRAU E1s.
Refer to the appropriate section of this chapter for the PCU provisioning rules. A
more aggressive GDS TRAU E1 provisioning approach can be taken where 60
active and 64 standby timeslots are provisioned on only one GDS TRAU E1. The
PCU load-balancing software would distribute the load over the two PRP boards.
The advantage of the more aggressive provisioning approach is that one less E1
(if CS1 or CS2 is used) would need to be provisioned at the BSC. The
disadvantage is that if the one GDS TRAU E1 were to fail, 100% of the PCU
service would be lost.
Step 4: Calculate the PCU hardware to support the PCU traffic

For the calculation bear the following in mind:
– Qty 2 PRP boards, 1 PRP board per GDS E1 link.
– Qty 1 PICP board, 1 PICP board per 4 GDS TRAU links (2 links
provisioned).
– Qty 1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy).
– Qty 1 PCU shelf with alarm board and 3 power supply / fan assemblies, 1
PCU shelf per 9 PRP boards.
– Qty 1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.

7–34 68P02900W21-K 30th Jun 02
GMR-01
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 the
equivalent of 150 active timeslots. This figure includes the GBL signalling traffic
and the GPRS packet data traffic including protocol overhead. Therefore, the
number of GBL E1 links required is:
60 active BSC * PCU timeslots
+ 0.4 E1s
150 active timeslots per GBL E1
This answer would be rounded up to 1 E1 without redundancy unless a fractional

E1 is available for use. If a fractional E1 is available, it is not necessary to round
up to the nearest integer value for the number of E1s to specify.
Option 2
Using the standard traffic model and Gb formulae:
Signalling_Data_Rate +
(324 * PS ATTACHńDETACH ) 111 * RAU ) 162 * PDP ACTńDEACT) * GPRS_Users_PCU

) 87 * P GPRS
3600
(324 * 0.5 ) 111 * 1.5 ) 162 * 0.5) * 250 * 20

+ ) 87 * 12 + 1612 bytesńs
3600
User_Data_Rate +
(GPRS_Users_PCU * Data_rate_per_sub * 1000)

3600
* ƪ1 ) PK71 ƫ SIZE
+
(250 * 20 * 65 * 1000)
3600
* ƪ1 ) 270
71 ƫ + 114017 bytesńs
No_GBL_TS +
Total_Data_Rate
8000 * U GBL
+ 1612 ) 114017 + 57.8

8000 * 0.25
N PCU*SGSN +
No_GBL_TS
31
+ 57.8 + 1.86
31
Hence, 2 Gb links need to be provisioned.

30th Jun 02 68P02900W21-K 7–35
GMR-01
Step 6: Calculate the number of GSL links

Use the following equation to calculate how many 64 kbits/s GSL links are
required. For this example, the number of users on a PCU is 5000. Evaluating this
equation and the supporting expressions results in one 64 kbit/s GSL link being
required, assuming that preload is enabled, after rounding up to the nearest
integer value (but not including redundancy).
5000 * (5 ) 1.5 ) 0.5 ) 0.5)

Total_RACHńsec + + 10.38 per second
3600
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 in

Chapter 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, make
sure that there are a sufficient number of PICP boards to cover the GBL and GSL
E1 links, and to satisfy the 1:6 ratio of GDS TRAU E1s to PICP boards. The PCU
hardware calculation in step 4 calculated the number of PICP boards based only
on the ratio of PICP boards to PRP boards. This step takes into account the
number of E1 links terminated on the PICP boards for the GBL and GSL E1 links.
A PICP board can terminate both GBL and GSL links on the board, but not on the
same PMC module. Each PICP has two PMC modules.
In step 5 it was determined that 2 E1 links are required for the GBL. Each PICP
can terminate up to 4 GBL links. Therefore, 2/4 (1/2) of a PICP is required for the
GBL E1 links.
In step 6 it was determined that 1 E1 link is required for the GSL (redundant GSL
not provided for). Each PICP can terminate up to 2 E1 GSL links and up to 12 GSL
64 kbit/s timeslots distributed over two E1s. Note that there is a limit of 2 GSL E1s
per PCU. Therefore, 1/4 of a PICP is required for the GSL E1 link.
Reviewing the GBL and GSL E1 link requirements, we can see that one PICP is
sufficient to handle the link provisioning requirements.
Step 8: Calculate the increased data traffic load on the E1s between
the BSC and BTSs
It is assumed that the GPRS traffic is in addition to the existing circuit-switched
traffic. In step 2 it was determined that 6 timeslots would be required for the GPRS
timeslot 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 to

allocate the GPRS carrier timeslots. That is, they are reserved or switchable. If
GSM circuit-switched statistics are available, they could be reviewed to aid in this
decision. Refer to Dynamic timeslot mode switching in Chapter 3.

7–36 68P02900W21-K 30th Jun 02
GMR-01
Step 9: Calculate the increased signalling traffic load (RSL load) on

the E1s between the BSC and BTSs
The BTS combines the additional signalling load for the GPRS data traffic with the
existing circuit-switched traffic load. This results in an additional load on the
existing RSL links between each BTS and the BSC.
The additional load on the RSL for GPRS is based on the evaluation of the
following equation and other supporting equations (see Determining the number
of RSLs in Chapter 5). For 6 timeslots per cell, approximately 0.23 RSL channels
would be required.
The network planner should calculate the RSL load for the GSM circuit-switched
part of the network, and then add the the GSM number of RSLs to the GPRS
requirements in order to determine the total number of RSL links to provision per
the above equation. The GSM RSL calculation should be performed with 64 kbit/s
RSL in order to be consistent with the GPRS calculation.
Step 10: Calculate the increased load due to GPRS traffic on the
common control channel at each BTS cell
N PAGCH = (NAGCH + N PCH) 1

UCCCH
The BTS combines the additional control channel load for the GPRS data traffic
with the existing circuit-switched traffic load onto the CCCH. The network planner
needs the expected paging rate and the access grant rate in order to calculate the
number CCCH blocks needed to support the additional GPRS traffic load. This
calculation should be performed using the guidelines given in the Control channel
calculations section of Chapter 3.
Step 11: BSC provisioning impact

The BSC may require additional hardware in order to support the addition of the
GPRS network traffic. For BSC provisioning, the planning rules given in Chapter 5
should be consulted.
The BSC may require more E1 terminations in support of the additional E1 links to
the PCU and in support of the additional GPRS traffic over the BTS to BSC
interface. In this example, two E1s were added for the GDS links and one E1
added for the GSL link.
The BSC LCF GPROC2 processor load is increased by the volume of GPRS
signalling traffic. The BSS planning rule for LCF provisioning in the following
equation should be used.
N C
GPRS GRPS
G *T
) (0.006 ) 0.02 * P GPRS) * (B RA_GPRS) ) 35
GPRS_PF GPRS
G L3_GPRS +
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 to
examine the GSM circuit-switched provisioning to see whether an existing LCF
GPROC2 could handle this additional load.

30th Jun 02 68P02900W21-K 7–37
GMR-01
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 the
PCU. The BSC merges the PCU statistics with the rest of the BSS statistics for
uploading to the OMC-R over the 64 kbits/s X.25 link. No change in this link
provisioning is required.

7–38 68P02900W21-K 30th Jun 02
GMR-01
Chapter 8
BSC planning steps and rules for
LCS

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
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 not
affected, refer to Chapter 5.
S LCS overview.
S BSC planning for LCS overview.
– 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 between
BSC and SMLC.
– BSC GPROC functions and types with LCS.
– Traffic models with LCS.
S BSC planning.
– Planning rules for BSC to SMLC links (LMTL).

30th Jun 02 68P02900W21-K 8–1
GMR-01
LCS description GSM-001-103
LCS description
LCS overview
Location services (LCS) provides a set of capabilities that determine location estimates
of mobile stations and makes that information available to location applications.
Applications requesting location estimates from LCS can be located in the MS, the
network, or external to the PLMN. LCS is not classified as a supplementary service and
can be subscribed to without subscribing to a basic telecommunication service. LCS is
applicable to any target MS, whether or not the MS supports LCS, but with restrictions on
choice of positioning method or notification of a location request to the MS user when
LCS 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 a
mobile 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 air
interface. While an MO–LR could be used to request the location of another MS, its
primary purpose is to obtain an estimate of the client MS’s own location, either for the
client 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 the
PLMN 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 any
of the PLMN entities currently serving the target MS. In this case, the LCS client is also
within the LCS server. Examples of a NI–LR include a location request needed for
supplementary services, for emergency call origination and by O&M in a visited PLMN.

8–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 LCS description
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 that
provides 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 serving
BTS. To obtain TA values in case the MS is in idle mode a special call, not noticed by the
GSM subscriber (no ringing tone), is set up. The cell ID of the serving cell and the TA is
returned 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 signal
sent from the mobile and received at three or more measurement units. The known
signal is the access bursts generated by having the mobile perform an asynchronous
handover. The method requires additional measurement unit (LMU) hardware in the
network at the geographical vicinity of the mobile to be positioned to accurately measure
the TOA of the bursts. Since the geographical coordinates of the measurement units are
known, the mobile position can be calculated via hyperbolic triangulation. This method
will 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 of
bursts of nearby pairs of BTSs. For E-OTD measurement synchronization, normal and
dummy 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, for
non-synchronized BTSs, RTD or ATD measurements are needed for at least three
distinct pairs of geographically dispersed BTSs. Based on the measured E-OTD values
the location of MS can be calculated either in the network or in the MS itself, if all the
needed information is available in the MS.
NOTE E-OTD is not supported in GSR6.

30th Jun 02 68P02900W21-K 8–3
GMR-01
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 differential
GPS 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 a
MS-based or network-based application, the assistance data from the reference network is
transmitted to the MS to increase performance of the GPS sensor. For classification, when
the position is calculated at the network, it is called a mobile assisted solution. When the
position 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 assisted
data, such as differential GPS corrections, approximate handset location or cell
base station location and others, can be transmitted to improve the location
accuracy and decrease acquisition time.
NOTE A-GPS is not supported in GSR6.
System architecture
Figure 8-1 shows the LCS architecture.
Figure 8-1 Generic LCS logical architecture
Lp
CBC SMLC SMLC
LMU
Type A
Lb HLR
Ls
Um
Lh
BTS
Abis A Lg Gateway Le External
MS (LMU BSC MSC/VLR
Type B) MLC LCS Client
Lg Lc
Abis
Gateway
LMU MLC gsmSCF
Type A
Other PLMN
BSS
The BSS is involved in the handling of various positioning procedures. The BSS needs to
be 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.
LCS client
The LCS client is outside the scope of this standard.

8–4 68P02900W21-K 30th Jun 02
GMR-01
GMLC
The gateway mobile location centre (GMLC) contains functionality required to support
LCS. 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, the
Le reference point is supported by the GMLC). The GMLC may request routeing
information from the HLR via the Lh interface. After performing registration authorization,
it sends positioning requests to and receives final location estimates from the VMSC
through the Lg interface.
SMLC
The serving mobile location centre (SMLC) contains functionality required to support
LCS. In one PLMN there may be more than one SMLC.
The SMLC manages the overall co-ordination and scheduling of resources required to
perform positioning of a mobile. It also calculates the final location estimate and
accuracy.
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 Ls
interface to the visited MSC. A BSS-based SMLC supports positioning via signalling on
the Lb interface to the BSC serving the target MS. Both types of SMLC may support the
Lp 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 interface
measurements to locate or help locate MS subscribers in the area that it serves. The
SMLC is administered with the capabilities and types of measurement produced by each
of its LMUs. Signalling between a NSS-based SMLC and LMU is transferred via the MSC
serving the LMU using the Ls interface and either the Um interface for a Type A LMU or
the Abis interface for a Type B LMU. Signalling between a BSS based SMLC and LMU is
transferred via the BSC that serves or controls the LMU using the Lb interface and either
the 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 may
interface to a CBC in order to broadcast assistance data using existing cell broadcast
capabilities. The SMLC behaves as a user, cell broadcast entity, to the CBC.
MS
The MS may be involved in the various positioning procedures.
LMU
A LMU makes radio measurements to support one or more positioning methods. These
measurements fall into one of two categories:
S Location measurements specific to one MS used to compute the location of this
MS.
S Assistance measurements specific to all MSs in a certain geographic area.
All location and assistance measurements obtained by an LMU are supplied to a
particular SMLC associated with the LMU. Instructions concerning the timing, the nature
and any periodicity of these measurements are either provided by the SMLC or are
pre-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.

30th Jun 02 68P02900W21-K 8–5
GMR-01
MSC
The MSC contains functionality responsible for MS subscription authorization and
managing call-related and non call-related positioning requests of GSM LCS. The MSC is
accessible to the GMLC through the Lg interface and the SMLC via the Ls interface.
HLR
The HLR contains LCS subscription data and routing information. The HLR is accessible
from the GMLC through the Lh interface. For roaming MSs, the HLR may be in a
different PLMN that the current SMLC.
The system architecture is differentiated by which network entity the SMLC is connected
to. When SMLC is connected to a MSC, the system architecture is referred as an
NSS-based LCS architecture; otherwise, a BSS based LCS architecture when SMLC is
connected to a BSC.
NSS-based LCS architecture

In 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
OMC–L
GPS
Serving HLR
LMU MLC
Lh
Ls
Le
Gateway External
BTS BSC MSC
MLC LCS Clients
Lg
External Le Gateway
LCS Clients MLC
Location
capable Other PLMN LMU: Location measurement unit
mobile MLC: Mobile location centre

8–6 68P02900W21-K 30th Jun 02
GMR-01
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 two
entities.
Figure 8-3 BSS-based architecture
OMC–L
GPS
Serving HLR
LMU MLC
Lh
Lb
Le
Gateway External
BTS BSC MSC
MLC LCS Clients
Lg
External Le Gateway
LCS Clients MLC
Location
capable Other PLMN LMU: Location measurement unit
mobile MLC: Mobile location centre

30th Jun 02 68P02900W21-K 8–7
GMR-01
Overview of BSC planning for LCS GSM-001-103
Overview of BSC planning for LCS
Introduction to GSR6 LCS provisioning

In GSR6, the Motorola BSS provides the interfaces, protocols and messages to support
the GSM standards-based LCS architecture and Cell-ID and timing advance (TA)
positioning technology.
In GSR6, the BSS supports the network sub-system (NSS) based serving mobile
location 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 TA
positioning method for LCS will be provided for NSS-based and BSS-based LCS
architecture respectively in the following sections.
To plan the equipage of a BSC supporting LCS, certain information must be known. In
addition 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 LCS
also involves the following steps, which result from Chapter 5:
1. Determine the LCS architecture a BSS will support. That is, the BSS will support
either a NSS-based LCS architecture or a BSS-based LCS architecture, but not
both.
2. Plan the number of E1 or T1 links between the BSC and BTS site(s). Refer to the
section Determine the required BSS signalling link capacities in this chapter.
3. Plan the number of RSL links between the BSC and BTS site(s) based on the LCS
architecture supported. Refer to the section Determine the RSLs required in this
chapter.
4. Plan the number of MTL links between the BSC and the MSC based on the LCS
architecture supported. Refer to the section Determine the number of MTLs
required in this chapter.
5. Plan the number of LMTL links required between the BSC and the SMLC for BSS
based LCS architecture. Refer to Determine the number of LMTLs required in
this chapter. If the BSS only supports NSS-based LCS architecture, this step
should be skipped.
6. Plan the number of GPROC2s required with support of LCS. Refer to the section
Generic processor (GPROC2) in this chapter.
7. Verify the planning process with support of LCS. Refer to the section Verify the
number of BSU shelves and BSSC cabinets in Chapter 5.

8–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Capacity calculations
Introduction
In addition to the capacity calculations in Chapter 5, the additional traffic load resulting
from LCS needs to be taken into consideration in the capacity calculations.
link 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.

30th Jun 02 68P02900W21-K 8–9
GMR-01
BSC LCS signalling traffic model

Besides the factors described in Determining the required BSS signaling link
capacity in Chapter 5 and Figure 5-1, LCS needs to be taken into account when
planning a BSS.
S MTL link provisioning to support LCS signaling between the MSC and BSC for
either 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.

listed in Table 8-1 and Table 8-2 with their typical values.

Location update factor L=2
Ratio of LCSs per call LCS = 0.2
Mobile originated LCS ratio LRMO = 0.05
(continued)

8–10 68P02900W21-K 30th Jun 02
GMR-01
GPRS parameters
CS2 = 13.4 kbit/s
CS3 = 15.6 kbit/s
CS4 = 21.4 kbit/s

30th Jun 02 68P02900W21-K 8–11
GMR-01
Signalling message sequence and size assumptions

Refer to Chapter 5 for the signalling message sequence and size assumptions.
sizes for each procedure are provided in Table 8-3.
Table 8-3 LCS procedure capacities

MSC to BSC link including protocol header
LCS request and response 7 downlink messages with average size of 29 bytes
(NSS-based architecture) 6 uplink messages with average size of 28 bytes
(BSS-based architecture) 6 uplink messages with average size of 29 bytes
SMLC to BSC link including protocol header
BSC to BTS link
(NSS-based architecture) 5 uplink messages with average size of 19 bytes
(BSS-based architecture) 5 uplink messages with average size of 19 bytes
An additional assumption, which is made in determining the values listed above in
Table 8-3, is that the procedures not included in the traffic model are considered to have
negligible 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 all
provided for by C7 links. The total number of MTLs, and/or LMTLs should not exceed 16.

8–12 68P02900W21-K 30th Jun 02
GMR-01
Determining the number of RSLs required
Introduction
In this section, the RSL number with LCS supported is calculated for the GSM circuit
switched part.
LCS signalling has no impact on GPRS RSL.
Refers to Chapter 5, RSL planning considerations.
Determining the number of RSLs

The RSL signalling link provisioning has a contribution from the GSM circuit-switched
part of the network and from the GPRS part. LCS is included in the GSM circuit-switched
part. 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 is
as follows:
This is evaluated for 16 kbit/s RSLs or for 64 kbit/s RSLs. The interface between the BTS
and BSC does not permit mixing the two RSL rates.
Where: RSLGPRS+GSM is: The combined number of RSL

signalling links on a per BTS site
basis operating at a 16 kbit/s RSL
rate or at a 64 kbit/s RSL rate.
RSLGPRS This is the number of RSL
RSLGSM This is the number of RSL

30th Jun 02 68P02900W21-K 8–13
GMR-01

This number depends on the number of TCHs and PDTCHs at the BTS. Table 8-4 gives
the number of RSLs required (rounded up integer value) for a BTS to support the given
number of TCHs and PDTCHs, based on the typical call parameters given in the
standard traffic model column of Table 8-1. If the call parameters differ significantly from
the standard traffic model, use the formulae for the non-standard traffic model.
For NSS-based or BSS-based LCS architecture, there is no difference when calculating

RSL provisioning from the Abis point of view.
Table 8-4 Number of BSC to BTS signalling links – LCS supported

(n) (Ngprs)
<= 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)

8–14 68P02900W21-K 30th Jun 02
GMR-01
Table 8-4 Number of BSC to BTS signalling links – LCS supported

(n) (Ngprs)
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 GPRS
timeslots, even if the cells do not have traffic channels
configured as PDTCHs, it may have paging traffic.
RACH_Arrivals/sec figures have been calculated assuming
Avg_Sessions_per_user is as in the call model table.
GPRS_Users_BTS has been calculated based on the number of
timeslots configured on the cell.
A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, but
not both.

30th Jun 02 68P02900W21-K 8–15
GMR-01

Use the following formula to determine the required number of 64 kbit/s RSLs for CS
signalling with LCS supported. Sum up the result with the RSLGPRS@64k and round up to
the next integer to get the total 64kbit/s RSLs.
RSL GSM@64k +
n * (49 ) 50 * S ) 32 * H ) 20 * L ) 24 * L CS) (27 ) 3 * C) * P GSM * (1 ) L CS)

)
1000 * U * T 8000 * U
64 kbit/s RSLs for GPRS signalling refers to Chapter 5, Determining the RSL number
required.
formula to determine the required number of 16 kbit/s RSLs for CS signalling with LCS
supported. Sum up the result with the RSLGPRS@16k and round up to the next integer to
get the total 16kbit/s RSLs.
RSL GSM@16k +
ƪ 1000 * U * T
)
8000 * U
ƫ
n * (49 ) 50 * S ) 32 * H ) 20 * L ) 24 * L CS) (27 ) 3 * C) * P GSM * (1 ) L CS)
*4
16 kbit/s RSLs for GPRS signalling refers to Chapter 5, Determining the RSL number
required.
Where: RSLGSM is: the number of BSC to BTS signalling links for
GSM.
N the number of TCHs at the BTS site.
Lcs the ratio of LCSs to calls
U the percent link utilization (for example 0.20).
PGSM the GSM paging rate in pages per second.
NOTE A BTS can support either 64 kbit/s RSLs or 16 kbit/s RSLs, but
not both.

Refer to Chapter 5, BSC to BTS E1 interconnect planning actions.

Refer to Chapter 5, BSC to BTS T1 interconnect planning actions.

8–16 68P02900W21-K 30th Jun 02
GMR-01
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 call
parameters are similar to those listed in Table 8-1 (standard traffic model). The second
method is to be used when call parameters differ significantly from those listed in
Table 8-1.
G L3 + n ) B * (1 ) 0.45 * L ) ) C
CS
1060 160 120
Where: GL3 is: the number of LCF GPROC2s required to support

the layer 3 call processing.
n the number of TCHs at the BSC.
Lcs the ratio of LCSs to calls (0.2).
NOTE As an approximation, the LCS procedure will not exceed 45% of

processor resources compared with CS calls and may be
updated by statistics results from performance simulations.

G L3 +
ƪ n * (1 ) 0.42 * S ) 0.45 * H * (1 * 0.4 * i) ) 0.36 * L ) 0.45 * L CS)

(23.2 * T)
) (0.004 ) 0.000722 * P GSM * (1 ) L CS)) * B )
C
ƫ
120
N the number of TCHs under the BSC.
Lcs the ratio of LCSs to calls (0.2).
i the ratio of intra-BSC handovers to all handovers.
PGSM the paging rate in pages per second.
NOTE The above formula has been calculated using 70% mean
The planning information GL3_GPRS provided in Chapter 5 should be combined with this
provisioning.

30th Jun 02 68P02900W21-K 8–17
GMR-01
Introduction
MTLs carry signalling traffic between the MSC and the BSC for circuit-switched call and
LCS signalling. The number of required MTLs depends upon the BSS configuration size
and traffic model. MTLs are carried on E1 or T1 links between the MSC and BSC, which
are also used for traffic.
In addition to those considerations described in Determining the number of MTLs
required in Chapter 5, the following factors should be considered when planning the LCS
signalling links from the BSC to MSC:
S Determine the LCS architecture supported by the BSC. The BSC may support
either 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 determined
using the following method:
LCS 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 BSS
perspective, using the BSS planning rules. If the MSC vendor
supplies their own planning rules for a given configuration, the
more conservative MTL provisioning figures should be used. If
the MSC vendor does not provide the planning rules for the
MTLs required in a downlink direction, then use a load share
granularity of 0 to be conservative in MTL provisioning.
Load sharing of MTLs in the downlink direction depends on the
mechanism used by the MSC to load share the signalling links
from the MSC to BSC.

8–18 68P02900W21-K 30th Jun 02
GMR-01

The required number of MSC to BSC signalling links (MTLs) depends on the desired link
utilization, the type and capacity of the GPROCs controlling the MTLs and the MTL
loadshare granularity. The BSS software distributes call signalling traffic across 16 or 64
logical links, which are then evenly spread across the active MTLs.
CCITT C7 uses a 4-bit number, the signalling link selection (SLS), generated by the
upper layer to load share message traffic among the in-service links of a link set. When
the number of in-service links is not a power of 2, some links may experience a higher
load than others. From GSR5 release onwards, the BSS supports distribution of
signalling in the uplink direction, over 64 logical links. The BSS evenly distributes the 64
logical links over the active MTLs.
call load and signalling for the call load. Table 8-5 to Table 8-8 give the recommended
minimum 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.
trunks).
the BSS. The offered call load at a cell is a function of the number of TCHs and blocking.
NOTE Before setting the load share granularity to 1, it is recommended

that confirmation is gained from the Motorola local contact, or
local office, that the switch is compatible with the load share
granularity set to 1.

30th Jun 02 68P02900W21-K 8–19
GMR-01
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.

(NSS-based LCS at 20% utilization)
number of MSC-BSC
trunks or the offered load Minimum Recommended Minimum Recommended
from the BTSs required required
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

8–20 68P02900W21-K 30th Jun 02
GMR-01

(BSS-based LCS at 20% utilization)
number of MSC-BSC
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

(NSS-based LCS at 40% utilization)
number of MSC-BSC
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

30th Jun 02 68P02900W21-K 8–21
GMR-01

(BSS-based LCS at 40% utilization)
number of MSC-BSC
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 the
standard traffic model shown in Table 8-1.
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% utilization when the MTL is
running on a GPROC2. However, before use of the 40%
utilization of GPROC2, it is imperative that the operator verifies
that the MSC vendor can also support 40% utilization at the MSC
end, if not, then only 20% link utilization should be used for
GPROC2.

8–22 68P02900W21-K 30th Jun 02
GMR-01

supported by a C7 signalling link (nlink).
n link_bss +
(1000 * U * T)
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 31 * L CS) ) 9 * P PC * (1 ) L CS)
n link_nss +
(1000 * U * T)
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 26 * L CS) ) 9 * P PC * (1 ) L CS)
supported by a GPROC2 (LCF–MTL) supporting a C7 signalling link (nlLCF–MTL).
nl LCF*MTL +
(20 * T)
(1 ) 0.16 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.42 * L ) 0.45 * L CS) ) PPC * (0.005 * B ) 0.05) * (1 ) LCS)
smaller of the two numbers from Steps 1 and 2.
nl min + MIN (n link, nl LCF_MTL)
4. Signalling over the A–interface is uniformly distributed over a number of logical

links. The number of logical links is defined on the BSC by database parameter
mtl_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 amount
of traffic that a logical link would hold, is calculated as:
N logical + N
Ng
Where Ng= 16 or 64.
can handle (nlog–per–mtl):

Nlogical
Ǔ
log_per_mtl
Ǔ)R v 16
NOTE mtls should not exceed 16 per BSC.

The formula in step 2 has been calculated using 70% mean
Field experience suggests it is good practice to maintain the
mean 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 down
due to queueing of internal BSS messages, thus impacting on
system performance.

30th Jun 02 68P02900W21-K 8–23
GMR-01

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


Since one LCF GPROC2 can support two MTLs, the number of required LCF is:

2
Ǔ
However, if the traffic model does not conform to the standard model, below formula will
be used:
if 2 * n link u nl LCF*MTL, then NLCF + mtls
otherwise:

2
Ǔ
nlink calculated in the previous section.
Planning actions for transcoding at the BSC

Refer to Chapter 5.

8–24 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the number of LMTLs required
Determining the number of LMTLs required
Introduction
LMTLs carry the LCS signaling traffic between the BSC and the SMLC. This is only
applicable for BSS-based LCS architecture.
The number of required LMTLs depends upon the BSS configuration size and traffic
model. 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 links
from 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 traffic
model.
See Table 8-1 and Table 8-3.
LMTL number
Use the following formula to determine the required number of 64 kbit/s LMTLs (rounded
up to the next integer):
L MTL + ROUND UP ǒ LCS_BSC_Rate * 19

1000 * U BSC_SMLC
Ǔ
Where: LMTL is: the number of BSC to SMLC signalling
links.
LCS_BSC_Rate requests number per BSC per second.
UBSC_SMLC the percentage of the link utilization.

30th Jun 02 68P02900W21-K 8–25
GMR-01
Generic processor (GPROC2) for LCS GSM-001-103
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 in
Chapter 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 the
GPROC2 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 considered
when 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 for
LCS.
following calculation:
ȍ
i+1
nLCF * (21 ) 14 * S ) 14 * H ) 9 * L ) 11 * LCS)
) P ) P GPRS ) [RACHńsec] * 4.6 v 500
T
n
Where nLCF = the number of TCHs on the sites under a LCF

and
n = the total number of sites on the LCF.
If any LCF does not satisfy the above criteria, either rebalancing of sites on the available
LCF–GPROC2s at the BSC is required or additional LCF–GPROC2s may need to be
equipped at the BSC to handle the traffic load.
NOTE It is not recommended that an LCF supports both an LMTL and


8–26 68P02900W21-K 30th Jun 02
GMR-01
Chapter 9
OMC-R planning steps and rules

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Overview of OMC-R planning steps and rules
Overview of OMC-R planning steps and rules
Introduction to OMC-R planning steps and rules

The purpose of this chapter is to enable the customer to identify the items required for an
OMC-R scaleable system, depending on their requirements or current configuration.
This chapter covers three main topics:
S Planning steps and rules for creating a GSR4.x or GSR5 OMC-R scaleable
system.
S Upgrading the OMC-R system from GSR4.x to GSR5.
S Upgrading an OMC-R system to GSR6.
Specific details of equipment required/available for different GSRs, optional items and all
part numbers are provided in the Motorola OMC-R ordering guide web pages.
The OMC-R and GPRS

PCU hardware is required if GPRS is to be supported under the OMC-R. A maximum of
64 BSCs are supported per OMC-R serving area, each requiring one PCU. The size of
the PCU is determined from the GPRS subscriber profile.
Terminology
In order to avoid confusion, certain terms used are described. These are not mutually
exclusive and may be combined.
Expansion
This is where the system size is expanded, usually to increase capacity (for example,
from 5kTCH to 30kTCH).
Upgrade
This is where the software is upgraded (for example, from GSR4 to GSR5). There may
be an associated hardware upgrade at the same time.

30th Jun 02 68P02900W21-K 9–1
GMR-01
Planning a GSR4.x or GSR5 OMC-R scaleable system GSM-001-103
Planning a GSR4.x or GSR5 OMC-R scaleable system

Planning an OMC-R configuration involves the following steps:
1. Determine the capacity requirements (traffic channels – TCHs).
2. Select the server initial program load (IPL) software appropriate to the TCH
capacity required (compulsory).
3. Select the server hardware (compulsory)
4. Select the server ancillary equipment according to the country of use
(compulsory).
5. Select the GUI server hardware and software (compulsory).
6. Choose the appropriate data communications equipment.
7. Select the optional items and quantities required.
8. If required, determine the level of NSP support that can be provided by Motorola.
9. Ensure that the order quantities are correct according to the on-line product
ordering guide.
NOTE Many OMC-R system components, such as keyboards, power

cables, modems and datacomms equipment, are common to
both GSR4.x and GSR5. Where the equipment required
depends on the GSR version, this is described at the appropriate
places in the text.

9–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Planning a GSR4.x or GSR5 OMC-R scaleable system
OMC-R capacity
The maximum OMC-R capacity is determined by the GSR version, the scaleable
software license(s) purchased and the server hardware.
Table 9-1 and Table 9-2 show the traffic channels (TCHs), radio transmit functions
(RTFs) and network elements (NEs) that can be supported by the OMC-R for a full or
specific capacity load, depending on the GSR version and the scaleable software
license(s) purchased for use on the Sun E3500 server(s).
Table 9-1 OMC-R scaleable software – full capacity software load

Sun scaleable software license order number Max. Max. Max.
TCH RTF NE
GSR4.x GSR5
SWDN5027 SWDN7490 500 71 15
SWDN5035 SWDN7491 5000 714 15
n/a SWDN7522 10,000 1428 64
SWDN5036 SWDN7492 20,000 2857 64
SWDN6667 SWDN7525 30,000 4286 120
n/a SWDN7527 45,000 6429 120
Table 9-2 OMC-R scaleable software – specific capacity software load

Sun scaleable software license order number Max. Max. Max.
TCH RTF NE
GSR4.x GSR5
SWDN5027 SWDN7490 500 71 15
SWDN5027 + SWDN5028 SWDN7490 + SWDN5028 1000 142 15
+ SWDN5029 + SWDN5029
SWDN5035 SWDN7491 5000 714 15
SWDN5035 + SWDN5031 SWDN7522 10,000 1428 64
+ SWDN5032
SWDN5035 + SWDN5031 SWDN7522 + SWDN5033 15,000 2142 64
+ SWDN5032 +SWDN5033
SWDN5036 SWDN7492 20,000 2857 64
SWDN5036 + SWDN6660 SWDN7492 + SWDN6660 25,000 3571 120
SWDN6667 SWDN7525 30,000 4286 120
n/a SWDN7525 + SWDN6497 35,000 5000 120
n/a SWDN7525 + SWDN6497 40,000 5714 120
+ SWDN6498
n/a SWDN7527 45,000 6429 120
or
SWDN7525 + SWDN7994
NOTE In calculating the capacity of the OMC-R, whichever limit is

reached first (TCH, RTF or NE) will determine the size of the
OMC-R.

30th Jun 02 68P02900W21-K 9–3
GMR-01
Server hardware
Table 9-3 and Table 9-4 show the Sun E3500 servers available. Select the server
hardware according to the OMC-R software version and the capacity required (see
Table 9-1 and Table 9-2).
Table 9-3 E3500 server hardware selection (GSR4.x)

Capacity required Server hardware order number
Up to 5kTCH SWDN5916
5kTCH to 30kTCH SWDN5917
Table 9-4 E3500 server hardware selection (GSR5)

Capacity required Server hardware order number
Up to 10kTCH SWDN7764
10kTCH to 45kTCH SWDN7521
Server ancillary equipment

The compulsory server ancillary equipment required comprises the following:
S Server keyboard (x 1).
S Modem (x 1).
S Server power cables (x 5).
The items selected will depend on the country in which the equipment will be used. The
OMC-R on-line ordering guide provides all the necessary information required to make
the correct choice.

9–4 68P02900W21-K 30th Jun 02
GMR-01
GUI server hardware and software

A minimum of one local or remote Sun Ultra 5 GUI server is required, together with the
following ancillary items:
S GUI server software (GSR4.x or GSR5).
S GUI server keyboard (x 1).
S GUI server power cable (x 2).
NOTE The local/remote GUI server hardware and software required for
GSR4.x is different from that required for GSR5.
The total number of GUI sessions that can be supported depends on the GSR software
used and the system capacity.
Under GSR4.x, up to four GUI sessions (at least one GUI server plus up to three clients)
are supported in a 0 to 5kTCH system. Up to ten GUI sessions (at least two GUI servers
plus up to eight clients) are supported in a 5 to 30kTCH system.
Under GSR5, up to six GUI sessions (at least one GUI server plus up to five clients) are
supported in a 0 to 10kTCH system (five client support requires an additional memory
upgrade to enhance performance). Up to ten GUI sessions (at least two GUI servers plus
up to eight clients) are supported in a 10 to 45kTCH system.
NOTE If a remote GUI server is required, an Ultra 5 remote upgrade kit

will also be required.
Optional equipment, such as a V.35 connectivity kit, Vanguard 320 router, remote printer
and RJ45 – AUI transceiver, are also available.
Optional printer
A printer is available as an option for connection to the E3500 server or Ultra 5 GUI
server. Two printer options are available:
S Local (requires one printer power cable), part number SWDN6650.
S Remote (requires two printer power cables), part number SWDN4886.

30th Jun 02 68P02900W21-K 9–5
GMR-01
Datacomms equipment
The basic building block for datacomms is the Vanguard 6560.
NOTE The Vanguard 6560 was previously known as the 6560

Multi-Protocol Router.
Multiple Vanguard 6560s can be connected in a ring in order to expand the datacomms
capability. However, although each Vanguard 6560 has two E1 connectors, it can support
only 30 timeslots (network elements).
Provisioning recommendations for the Vanguard 6560 are as follows:
GSR4.x
S Order one Vanguard 6560 for a 0 to 5kTCH system (30 timeslots).
S Order two Vanguard 6560s for a 5kTCH to 30kTCH system (60 timeslots).
S Order one power cable for the appropriate country per Vanguard 6560 ordered.
GSR5
S Order one Vanguard 6560 for a 0 to 10kTCH system (30 timeslots).
S Order two Vanguard 6560s for a 10kTCH to 30kTCH system (60 timeslots).
S Order three Vanguard 6560s for a 30kTCH to 45kTCH system (90 timeslots).
S Order one power cable for the appropriate country per Vanguard 6560 ordered.
Additional Vanguard 6560s may be ordered to provide extra timeslots or redundancy.
However, no more than 120 timeslots can be supported.
For further information regarding configurations and interconnections of Vanguard 6560s,
refer to Installation and Configuration: OMC-R Clean Install, 68P02901W47.

9–6 68P02900W21-K 30th Jun 02
GMR-01
Additional optional items

Additional optional items for the OMC-R system include the following:
S Single OMC-R map.
S Vanguard 6560 optional equipment:
– Stand-alone PSU (if Vanguard 6560 is powered separately).
– Vanguard 6560 enclosure (holds up to six Vanguard 6560s/6520s).
– Rack-mount kit (for Vanguard 6560s mounted in an enclosure).
– RJ45 – AUI transceiver (if the Vanguard 6560 is used as a router for a
remote GUI server).
– Informix 7 third party documentation.
– Circuit error rate monitoring software.
Network support program (NSP)

The NSP is an option that can be subscribed to by the customer when ordering a new
OMC-R. It is an integrated support solution that is modular in construction, providing a
comprehensive, seamless package. Support packages may be built and tailored to
individual customer needs. These act as a supplement to the existing Motorola warranty
provided with Motorola solutions and may also be continued after warranty has expired.
The NSP, depending upon purchased options, can offer many benefits to a network
operator, including:
S Reduced cost of ownership:
– Reduced engineering expertize requirement.
– Reduced spares holding requirement.
– Fixed support costs and easy budgeting.
S Increased system availability:
– Reduced downtime.
– Motorola expertise available 365 days/year.
– Fast replacement of faulty modules.
– Delivers certainty, regardless of failure circumstances.
S Increased subscriber confidence through system availability:
– Reduce subscriber turnover.
– Increase subscriber base.
S Single point of contact for all network issues:
– 24 x 7 x 365 basis.
– Local (in-country) engineering expertize.
– Understanding of local network issues.
– Local language support.

30th Jun 02 68P02900W21-K 9–7
GMR-01
Upgrading the OMC-R system from GSR 4.x to GSR5 GSM-001-103
Upgrading the OMC-R system from GSR 4.x to GSR5
Introduction to upgrading the OMC-R

Information required to upgrade an existing GSR4.x OMC-R system to a GSR5 OMC-R
system is provided here.
Hardware upgrade
No hardware upgrades are required when upgrading an existing OMC-R system from
GSR4.x to GSR5, except in the following situations:
S The system capacity is to be expanded at the same time (for example, to beyond
30kTCH).
S Sun Sparcstations are currently used as GUI servers.
Sun Sparcstations are not supported as servers under GSR5. If any are used in an
existing system, they will need to be replaced by Sun Ultra 5s.
NOTE Sun Sparcstations can still be used as GUI clients under GSR5.
Software upgrade
The OMC-R software upgrade from GSR4.x to GSR5 requires the following steps:
S Upgrading the software on the E3500 server(s) to match the capacity required
(see Table 9-1 and Table 9-2).
S Upgrading the software on the GUI server(s).
S Purchasing an OMC-R software upgrade kit, one per OMC-R, as per the ordering
guide.
NOTE Upgrading from GSR4 1600 OMC-R to GSR5 1620 OMC-R

requires that all BSS software has been previously upgraded to
release 1600.
Similarly, upgrading from GSR4.1 1613 OMC-R to GSR5 1620

OMC-R requires that all BSS software has been previously
upgraded to release 1614.
The only BSS software releases that are supported in GSR5 are
1600, 1614 and 1620.

9–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Upgrading the OMC-R to GSR6
Upgrading the OMC-R to GSR6
Introduction to upgrading the OMC-R to GSR6

Information required to upgrade an earlier OMC-R system to a GSR6 OMC-R system is
provided here.
Hardware upgrade
The hardware requirements for GSR6 are similar to those for GSR5. However, the
memory requirement for the E3x00 equipment is more stringent.
The following minimum memory requirements are necessary on all OMC-R E3x00
equipment running GSR6:
S For a 0 to 10kTCH system: 1 Gb RAM.
S For systems above 10kTCH: 2 Gb RAM.
1 Gb or 2 Gb memory expansion kits are available and can be ordered from Motorola
(refer to the on-line ordering guide for further details).
NOTE Check the installed memory on all equipment prior to ordering

memory upgrade kits. E3500 equipment shipped from 2001
should already have the required memory fitted.
Software upgrade
The OMC-R software upgrade to GSR6 requires the following basic steps:
S Upgrading the software on the E3500 server(s) to match the capacity required.
S Upgrading the software on the GUI server(s).
S Purchasing an OMC-R software upgrade kit, one per OMC-R, as per the ordering
guide.
NOTE GSR6 runs under the Solaris 8 operating system.

30th Jun 02 68P02900W21-K 9–9
GMR-01
Upgrading the OMC-R to GSR6 GSM-001-103

9–10 68P02900W21-K 30th Jun 02
GMR-01
Chapter 10
Planning exercise

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction to the planning exercise

This chapter contains planning exercises designed to illustrate the use of the rules and
formulae provided in earlier chapters.
The tables of required equipment in this chapter list only the major Motorola supplied
items. Equipment not covered in these examples includes: cable, external power supplies
and air conditioning equipment. Consult the appropriate Motorola local office for
assistance in ensuring that all necessary items are purchased.
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.

30th Jun 02 68P02900W21-K 10–1
GMR-01
Initial requirements GSM-001-103
Initial requirements
Requirements
In the area of interest, a demand analysis has identified the requirement for 11 BTSs with
the busy hour Erlang requirement shown in column two of Table 10-1.
Column three of Table 3-8 or Table 3-9 (depending on position in location area) in the
Control channel configurations section of Chapter 3 provides the maximum Erlang
capacity for a given number of carriers at 2% blocking. Column one of the same tables
lists the number of carriers (RTF) required; column three of Table 10-1 lists this
information.
If other blocking factors at the air interface are required, the number of Erlangs for
column three of Table 3-8 or Table 3-9 in the Control channel configurations section of
Chapter 3 can be found by reference to standard Erlang B tables for the number of traffic
channels in column two of Table 3-8 or Table 3-9 in the Control channel configurations
section of Chapter 3 at the required blocking factor.
Table 10-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

10–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Initial requirements
Network topology
Using a frequency planning tool it is possible to assign adequate frequencies to support
the BTS antenna configurations of Table 10-1. Based on this, initial planning of the
network gives the topology shown in Figure 10-1.
Figure 10-1 Network topology
RXCDR MSC
BSC
OMC-R
BTS K BTS A BTS E
BTS B BTS F
BTS L BTS C BTS G BTS J
BTS D BTS H

30th Jun 02 68P02900W21-K 10–3
GMR-01
The exercise GSM-001-103
The exercise
Introduction
In order to illustrate the planning steps, the individual hardware requirements for BTS B
and BTS K will be calculated, followed by the calculation to produce the hardware
requirements for the BSC, RXCDR, and the OMC-R. Where parameters are required for
the database generation they are noted.
The calculations for the hardware capacity use the standard call model given in Chapter
3 and Chapter 5.

10–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for BTS B
Determine the hardware requirements for BTS B
Introduction
From Figure 10-1 and Table 10-1 it can be seen that BTS B requires two RF carriers in
an omni configuration to carry a peak demand of five Erlangs.
Cabinet
From the site requirements and the potential future expansion it can be determined that
this site should be built using an M-Cell6 indoor cabinet. For the cabinet and any of the
following 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 the
Motorola local office if part numbers are required.
Digital redundancy
It is not considered that the purpose of this site justifies the expense of digital
redundancy.
Alarm inputs
More that eight alarm inputs are not required, so nothing is needed here.
Memory
Requirement is to have non-volatile code storage and the ability to download code in
background mode. Contact the Motorola local office if part numbers are required.
Database option

30th Jun 02 68P02900W21-K 10–5
GMR-01
Determine the hardware requirements for BTS B GSM-001-103
Summary
The equipment required, and an example of customer order creation for an M-Cell6
indoor (900 MHz) configuration, to implement BTS B is listed in Table 10-2 and
Table 10-3.
Table 10-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)

10–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for BTS B
Table 10-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? Yes
(Provided by local office) 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

30th Jun 02 68P02900W21-K 10–7
GMR-01
Determine the hardware requirements for BTS K GSM-001-103
Determine the hardware requirements for BTS K
Introduction
From Figure 10-1 and Table 10-1 it can be seen that BTS K requires 12 RF carriers in a
sector 4/4/4 configuration to carry a peak demand of 20 Erlangs per sector.
Cabinet
From the site requirements and the potential future expansion it can be determined that
this site will be contained in two or three Horizonmacro cabinets.
Receiver requirements
A two cabinet solution and a three cabinet solution are provided below.
Two cabinet solution

Each cabinet will have four carriers of a sector plus two carriers of a shared sector. Two
SURF modules will support the four carriers in each sector. The shared sector will be
supported by interconnecting the SURF in the master cabinet to the SURF in the
extender cabinet.
Three cabinet solution

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

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

Each sector requires two DCF modules. The shared sector will have one DCF module in
the master cabinet and the other DCF in the extender cabinet.
Three cabinet solution

Each cabinet will be dedicated to a sector, which requires one DDF and HCU modules.

10–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for BTS K
Summary
The equipment required, and an example of customer order creation for a two cabinet
Horizonmacro indoor (1800 MHz) configuration, to implement BTS 10 is listed in
Table 10-4 and Table 10-5.
Table 10-4 Customer ordering guide 1800 MHz (Horizonmacro 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 n
5
6
7
8
How many cabinets are required for the RF configuration? 1
2 n
3
4
What type of combining is required? DCF (Hybrid)
DCF & Air n
TDF
DDF
DDF & HCU
DDF, HCU &
Air
DDF & Air
What line interface is required? T43 (E1)
(75 ohm)
BIB (E1) n
(120 ohm)

30th Jun 02 68P02900W21-K 10–9
GMR-01
Determine the hardware requirements for BTS K GSM-001-103
Table 10-5 Customer ordering guide 1800 MHz (Horizonmacro indoor)

Question Options n
Is digital redundancy required? Yes n
No
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 memory card required? Yes n
No
Is a stacking bracket required? Yes n
No
Is battery backup required? Yes n
No
Is database required? Yes n
(Provided by local office) No

10–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for the BSC
Determine the hardware requirements for the BSC
Introduction
From Figure 10-1 and Table 10-1 it can be seen that this BSC controls 11 BTSs with 32
carriers in 13 cells to carry a peak demand of 119 Erlangs.
BSC to BTS links

Figure 10-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 requires
138 traffic channels.
One OML link, one XBL link and one C7 signalling link are required. The number of
trunks required is given by:
[(1 ) 1) ) (1 ) 1) ) (1 ) 1) ) (138ń4)]ń31 + 1.3
This value should be rounded up to 2.
Transcoder requirement
None required, remote transcoding.
MSI requirement
Minimum number of MSIs required is given by:
(4 ) 2)ń2 + 3
Line interface
Depending on the interface standard (balanced or unbalanced) used, one BIB or one T43
is adequate for three MSIs.
GPROC2 requirement
GPROC function requirements are listed in Table 10-6.
Table 10-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 for
redundancy.

30th Jun 02 68P02900W21-K 10–11
GMR-01
Determine the hardware requirements for the BSC GSM-001-103
KSW requirement
Device timeslot requirements are listed in Table 10-7.
Table 10-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 are
required. Use one for this example.
BBBX requirement
One BBBX is required in each shelf.
LANX requirement
An adequate number of LANXs are provided for non redundant operation. A redundant
LAN requires one additional LANX per cabinet.
Power supply
Depending on the power supply voltage, two EPSM plus one for redundancy or two
IPSM plus one for redundancy will be required.

10–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for the BSC
Summary
The equipment required to implement the BSC is listed in Table 10-8.
Table 10-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) 2+1
(–48 V)
redundancy.

30th Jun 02 68P02900W21-K 10–13
GMR-01
Determine the hardware requirements for the RXCDR GSM-001-103
Determine the hardware requirements for the RXCDR
MSI requirements
It is necessary to provide enough MSIs to communicate on the links to the BSC, for E1
links the traffic connection comes directly from the transcoder card.
Links to the BSC

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

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

From the foregoing it can be seen that three E1 links are required.
The number of MSI cards is given by:
3ń2 + 1.5
Transcoder requirement
From the calculation in the previous section BSC to MSC links, it can be seen that 138
traffic channels and two C7 links are required.
The number of transcoder cards is given by:
138ń30 + 5
This applies to either XCDR or GDP cards.
Link interface
From the MSI requirements it can be seen that two E1 links to the BSC and one to the
OMC-R are required. From the transcoder requirements it can be seen that a further five
E1 links are required. A total of eight E1 links are required.
The number of BIB/T43s is given by:
8ń6 + 1.3
GPROC2 requirement
One GPROC2 is required, plus one for redundancy.
KSW requirement
From the number of MSIs, transcoders and E1 links, it can be seen that the total number
of timeslots is given by:
2 * 16 ) 5 * 16 ) 2 * 64 + 240
One KSW is required, plus one for redundancy.

10–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the hardware requirements for the RXCDR
KSWX requirement
The RXU is contained in one shelf so there is no requirement for a KSWX.
GCLK requirement
One GCLK is required plus one for redundancy.
CLKX requirement
The RXU is contained in one shelf, so there is no requirement for a CLKX.
PIX requirement
The number of PIX boards required depends on the number of external alarms that are
required. Use one for this example.
BBBX requirement
One BBBX is required in each shelf.
LANX requirement
An adequate number of LANXs are provided for non redundant operation. A redundant
LAN requires one additional LANX per cabinet.
Power supply
Depending on the power supply voltage, two EPSMs plus one for redundancy or two
IPSMs plus one for redundancy will be required.

30th Jun 02 68P02900W21-K 10–15
GMR-01
Determine the hardware requirements for the RXCDR GSM-001-103
Summary
The equipment required to implement the RXCDR is listed in Table 10-9.
Table 10-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) 2+1
(–48 V)
redundancy.

10–16 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determine the requirements for the OMC-R
Determine the requirements for the OMC-R

OMC-R example
The following is an example of customer order creation for a GSR5 OMC-R system
configuration. The procedure given here is similar for any GSR release.
S Basic configuration items required (compulsory):
Sun scaleable software licence for a 5000 TCH full capacity GSR5 software load.
0 to 10kTCH E3500 server hardware.
OMC-R server ancillary equipment for the UK (modem, keyboard and power
cables).
Sun Ultra 5 GUI server and GSR5 software.
GUI server ancillary equipment for the UK (keyboard and power cables).
S Optional items required:
Local GUI client workstation.
GUI workstation ancillary equipment for the UK (keyboard and power cables).
Vanguard 6560 router and UK power cable.
OMC-R map 1.
NSP subscription.
Table 10-10 and Table 10-11 provide a guide for compulsory and optional equipment for
the OMC-R, based on the above requirements.
Table 10-10 Customer ordering guide for the OMC-R (compulsory items)
Question Options Selection (n)
OMC-R software version? GSR5 n
GSR5.1
GSR6
How many traffic channels (TCHs) are required 500 TCH
for a full capacity GSR5 software load? 5kTCH n
10kTCH
20kTCH
30kTCH
45kTCH
E3500 server hardware required? 0 to 10kTCH n
10 to 45kTCH
UK-specific E3500 ancillary items? Keyboard n
Modem n
Power cables (x5) n
GUI server hardware required? Local n
(Remote GUI server hardware requires remote Remote
upgrade kit)
GUI server software required? GSR4.x
GSR5 n
UK-specific GUI server ancillary items? Keyboard n
Power cables (x2) n

30th Jun 02 68P02900W21-K 10–17
GMR-01
Determine the requirements for the OMC-R GSM-001-103
Table 10-11 Customer ordering guide for the OMC-R (available options)
Question Options Selection (n)
Are local GUI client workstations required Yes n
(maximum 5)? No
UK-specific GUI client ancillary items? Keyboard n
Power cables (x2) n
Is a Vanguard 6560 router required? Yes n
No
UK-specific Vanguard 6560 ancillary items? Power cable n
Are Vanguard 6560 optional items required? Yes
No n
Is a local printer required? Yes
No n
Is a remote printer required? Yes
No n
Are OMC-R maps required? Yes n
Is third party documentation required? Yes

No n
Are any optional software features required? Yes
No n
Is NSP subscription required? Yes n
No

10–18 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Calculations using alternative call models
Calculations using alternative call models
Introduction
This section is provided to assist users for whom the planning models given in Chapter 4,
Chapter 5 and Chapter 6 are inappropriate. Where this is the case, the various planning
tables that are used in the previous example in this chapter will not be correct and the
actual 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.
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 site = 3.
S GSM paging rate in pages per second PGSM = 10.
S GPRS paging rate in pages per second PGPRS = 10.
S Mean_TBF_Rate = 1.
S Number of GPRS timeslots NGPRS= 0.

30th Jun 02 68P02900W21-K 10–19
GMR-01
Calculations using alternative call models GSM-001-103
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 BTS connectivity = star configuration.
S IMSI/TMSI paging = TMSI.
S MTL load balancing granularity = 16.
GSR6 limitations
S Max. BTS sites = 100.
S Max. BTS cells = 250.
S Active RF carriers = 512.
S Trunks = 3000.
S C7 links = 16.

10–20 68P02900W21-K 30th Jun 02
GMR-01
Step 1 : Cell planning – control channel calculations

From Erlang B tables, the number of Erlangs supported by 32 TCHs with grade of
service (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:
l call + eńT + 23.72ń75 + 0.316
Ratio of SMSs to call:

l s + S * eńT + 0 * 23.72ń75 + 0.032
Ratio of location updates to calls:

l LU + L * eńT + 2.1 * 23.72ń75 + 0.664
Access grant rate is given by:

l AGCH + lcall ) lS ) lL + 1.012
From the call model parameters, paging rate P, is 10, so the average number of
CCCH blocks required to support paging only is:
N PCH + PGSMń(4 * 4.25) + 10ń(4 * 4.25) + 0.588
The average number of CCCH blocks required to support AGCH only is given by:
N AGCH_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 CCCH
block required to support both PCH and AGCH is given by:
N PAGCH + (NAGCH ) NPCH)ńU CCCH + (0.119 ) 0.588)ń0.33 + 2.143
Assuming 1% blocking, the Erlang B tables show that 7 CCCHs are required. This
can be supported using a non-combined BCCH with 9 CCCH timeslots. It is
recommended 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 model
parameters, the average number of SDCCHs, NSDCCH is given by formulae
detailed in Chapter 3 as:
N SDCCH + lcall * T C ) lLU * (T L ) T g) ) l s * (T S ) T g)
+ 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.211

with 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 each
timeslot offering 8 SDCCHs.

30th Jun 02 68P02900W21-K 10–21
GMR-01
4 carrier cell – determining the number of TCHs

The total number of signalling timeslots required for a 4 carrier configuration with
the given call model parameters is 3 (1 non-combined BCCH timeslot with 9
CCCHs 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:
l call + eńT + 9.83ń75 + 0.131
l S * eńT + 0.1 * 9.83ń75 + 0.013
l LU + L * eńT + 2.1 * 9.83ń75 + 0.275
From the call model parameters paging rate P, is 10, so the average number of
N PCH + PGSMń(4 * 4.25) + 10ń(4 * 4.25) + 0.588
N AGCH + 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 CCCH
can be supported using a non-combined BCCH timeslot with 9 CCCH blocks. It is
recommended to reserve 2 CCCH blocks for access grant messages.
Omni 2 cell – determine the number of SDCCHs per cell
parameters, the average number of SDCCHs, NSDCCH is given by formula
detailed in Chapter 3:
+ 0.131 * 5 ) 0.275 * (4 ) 4) ) 0.013 * (6 ) 4) + 2.988

with 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 with
the given call model parameters is 3 (1 non-combined timeslot BCCH with 9
CCCHs 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.

10–22 68P02900W21-K 30th Jun 02
GMR-01
Step 2 : BSS planning – determining the number of RSLs

The number of 64 kbits/sec RSLs required is given by :
RSL GSM)GPRS@64k +
n * (95 ) 67 * S ) 35 * H ) 25 * L) (47 ) 3 * C) * PGSM ) (52 ) C) * PGPRS 6 * Mean_TBF_Rate * N GPRS

) )
1000 * U * T 8000 * U 1000 * U
Where, n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS):
RSL GSM)GPRS@64k +
29 * 3 * (95 ) 67 * 0.1 ) 35 * 2 ) 25 * 2.1) (47 ) 3 * 3) * 10 ) (52 ) 3) * 10 6*0

) )
1000 * 0.25 * 75 8000 * 0.25 1000 * 0.25
= 1.73
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:
[(nTCH + nPDTCH + L16) / 4] + L64
N BSC*BTS +
31
Number of E1 links required between each 4/4/4 BTS and BSC:
+ ((29 * 3)ń4 ) 2)ń31 X 1
Number of E1 links required between each omni 2 BTS and BSC:

+ (16ń4 ) 1)ń31 X 1
Hence, only one E1 interconnect is required between each BTS and BSC for the
given site configurations (provided they are in star configurations), giving a total of
30 E1 links.
Number of LCF-RSLs required if given by:
G L3 +
ƪn * (1 ) 0.42 * S ) 0.45(23.2* H**T)(1 * 0.4 * i) ) 0.36 * L) ) (0.00072 * P ) 0.004) * B ) 120

C ƫ
Where n is the number of TCHs under a BSC:
ƪ2464 * (1 ) 0.42 * 0.1 ) 0.45 * 2 * (1 * 0.4 * 0.5) ) 0.36 * 2.1)

(23.2 * 75)
) (0.00072 * 10 ) 0.004) * 30 )
86 ƫ
120
The number of LCFs for RSL processing is 5.

30th Jun 02 68P02900W21-K 10–23
GMR-01
Determining the number of MTLs

Total Erlangs offered by the BSC with 28 sites with 4/4/4 configuration and 2 omni
2 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 omni
2 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:
P pc + P * TńN + 10 * 75ń1812 + 0.42
Using the call model parameters the number of MTLs can be calculated using
formulae detailed in Chapter 5.
Maximum number of Erlangs supported by a C7 link is given by:
(1000 * U * T)
n link +
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 9 * P PC)
(1000 * 0.25 * 75)
n link +
(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 signalling
link is given by:
(20 * T)
nl LCF*MTL +
(1 ) 0.16 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.42 * L ) P PC * (0.005 * B ) 0.05))
(20 * 75)
nlLCF*MTL +
(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:
+ nl min + min(n link, nl LCF*MTL) + 150 Erlangs
Amount of traffic (or number of trunks) each logical link will hold:
N logical + 1812ń16 + 113.25
using a MTL load sharing granularity of 16.
The number of logical links each MTL can handle:
n log_per_mtl + round down ǒ113.25

150 Ǔ X 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 * n link t nl LCF*MTL
N LCF + ROUND UP ǒ162Ǔ + 8

10–24 68P02900W21-K 30th Jun 02
GMR-01
XBL requirements
Referring to Table 5-11 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 within
limits.
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 X 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 of
MSIs 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 the

number of GDP/XCDRs in the BSC:
N + 17 * 32 ) 23 * 64 + 2016
Each KSW provides 1016 TDM timeslots. Hence, 2 non-redundant KSWs would
be required for this configuration. For redundancy, an additional 2 KSWs are
required.
Total KSWs required (with redundancy) = 4.
BSU shelves
The number of BSU shelves required is the greater of the two calculations (since
we have no local transcoding):
N BSU + Gń8 + 17ń8 X 3 BSU cages
N BSU + (M ) R)ń12 + 23ń12 X 2 BSU cages
Therefore, 3 BSU cages are required to accommodate all the hardware needed for
this configuration. Ensure the following is true for each cage:
N ) (G * n) ) (M * 64) ) (R * 16) v 1016

30th Jun 02 68P02900W21-K 10–25
GMR-01
KSWX requirements
KSWX extends the TDM highway of a BSU to other BSUs and supplies clock
signals to all shelves in the multi-shelf configuration. KSWX maybe used in
expansion, remote and local modes. We require 3 BSU cages with 4 non
redundant KSWs, which implies we shall have 2 expansion cages and 1 extension
cage.
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 of
CLKXs required is given by:
N CLKX + ROUND UP(Eń6) * (1 ) RF)
Where E is the number of expansion/extension shelves and RF is the redundancy

factor:
N CLKX + ROUND UP(3ń6) * (1 ) 1) + 1
The number of CLKXs required (with redundancy) = 2.

LANX requirements
N LANX + NBSU * (1 ) R F) + 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 v 2 * NUMBER of BSUs + 6
Line interfaces
Number of T43s + Number of MSIsń3 + 23ń3 X 8
The number of T43 boards required is 8.

10–26 68P02900W21-K 30th Jun 02
GMR-01
Digital power supply requirements

Number of PSUs required is given by:
PSUs + N BSU * (2 ) RF)
PSUs + 3 * (2 ) 1) + 9
One redundant PSU is required for each BSU shelf, hence total number of PSUs
required 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

30th Jun 02 68P02900W21-K 10–27
GMR-01
Step 3 : RXCDR planning

Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharing
and redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRs
so that the signalling traffic and voice traffic is equally distributed over 2 RXCDRs, each
RXCDR 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:
N RXCDR*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.
N RXCDR*MSC + (16 ) 2 ) 1812)ń31 + 60
Each XCDR card terminates one E1 interconnect, hence, number of

non-redundant XCDR cards required is 60.
MSI requirements for RXCDR
As calculated in MSI requirements, the number of BSC–RXCDR links is 16 and
each MSI card interfaces 2 E1 links. Hence, 8 MSI cards are required on the
RXCDR.
RXU shelves
The number of RXU shelves required is given by (assumes NVM board fitted):
N RXU + maxƪMń5, (R ) N NVM)ń16ƫ + max(8ń5, 61ń16) X 4
Hence, 4 RXU shelves are required to equip 58 XCDR cards and 8 MSI cards.
Ensure the following is true for each cage:
N ) (G * n) ) (M * 64) ) (R * 16) v 1016
GPROC2 requirements for RXCDR

Each shelf should have minimum of one GPROC2. Hence, 4 non-redundant
GPROC2s are required. If the operator chooses to use redundancy 8 GPROC2s
would 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-redundant

KSWs are required for the RXCDR with this configuration.

10–28 68P02900W21-K 30th Jun 02
GMR-01
KSWX requirements for RXCDR

Number of KSWXs required is sum of KSWXE, KSWXR, and KSWXL. We require
4 RXU cages with 2 non-redundant KSWs, which implies we shall have 1
expansion cage and 2 extension cages.
N KXE + K * (K * 1) + 2 * 1 + 2
K is the number of non-redundant KSWs.

N KXR + SE + 2
SE is the number of extension shelves.

N KXL + K ) S E + 4
N KX + 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.
N CLKX + ROUND UP(Eń6) * (1 ) RF)
Where:
E is the number of expansion/extension shelves.
RF is the redundancy factor.
N CLKX + ROUND UP(4ń6) + 1
The number of redundant CLKXs required is 2.

LANX requirements
Number of LANXs required is given by:
N LANX + NRXU * (1 ) R F) + 4 * 2 ) 8

Total number of LANXs required with redundancy = 8.
PIX requirements
PIX v 2 * Number of RXUs + 8
Hence, 8 PIX cards are required for the RXCDRs.

30th Jun 02 68P02900W21-K 10–29
GMR-01
Line interfaces
Number of T43s + Number of E1sń6 + (60 ) 15)ń6 X 13

PSUs + 2 * RXUs + 8
One redundant PSU is required for each RXU shelf, hence total number of PSUs
required 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)

10–30 68P02900W21-K 30th Jun 02
GMR-01
Planning example 2
Dimension a network with following requirements:
S GSM software release = GSR6.
S Number of sites 2/2/2 sites (BTS: M-Cell6) = 55.
S Number of omni 2 sites (BTS: M-Cell2) = 5.
Call model
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 C = 3.
S GSM paging rate in pages per second PGSM = 10.
S GPRS paging rate in pages per second PGPRS = 10.
S Mean_TBF_Rate = 1.
S Number of GPRS timeslots NGPRS = 0.
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 BTS connectivity = Star configuration.
S IMSI/TMSI paging = TMSI.
S MTL load balancing granularity = 64.
S NVM board fitted at RXCDR.

30th Jun 02 68P02900W21-K 10–31
GMR-01
GSR6 limitations
S Max. BTS sites = 100.
S Max. BTS cells = 250.
S Active RF carriers = 512.
S Trunks = 3000.
S C7 links = 16.

10–32 68P02900W21-K 30th Jun 02
GMR-01
Step 1 : Cell planning – control channel calculations

From Erlang B tables, the number of Erlangs supported by 16 TCHs (2 carrier cell) with
GOS 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:
l call + eńT + 9.83ń100 + 0.0983
l S + S * eńT + 0.12 * 9.83ń100 + 0.012
l LU + L * eńT + 2.5 * 9.83ń100 + 0.246
From the call model parameters, the paging rate P is 8, so the average number of
N PCH + PGSMń(4 * 4.25) + 8ń(4 * 4.25) + 0.471
N AGCH + 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 CCCH
can be supported using a non-combined BCCH with 9 CCCH timeslots. It is
recommended to reserve 3 CCCH blocks for access grant messages.
Determine the number of SDCCHs per cell
parameters, the average number of SDCCHs, NSDCCH, is given by the formula
mentioned in Chapter 3:
+ 0.098 * 5 ) 0.246 * (4 ) 4) ) 0.012 * (6 ) 4) + 2.575

with 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 the
timeslot offering 8 SDCCHs.
Determining the number of TCHs
Total number of signalling timeslots required for a 2 carrier configuration with the
given call model parameters is 2 (1 non-combined BCCH timeslot with 9 CCCHs
and 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.

30th Jun 02 68P02900W21-K 10–33
GMR-01
Step 2 : BSS planning – determining the number of RSLs

The number of 64 kbits/sec RSLs required with the given by:
RSLGSM)GPRS@64k +
n * (95 ) 67 * S ) 35 * H ) 25 * L) (47 ) 3 * C) * P GSM ) (52 ) C) * P GPRS 6 * Mean_TBF_Rate * NGPRS

) )
1000 * U * T 8000 * U 1000 * U
Where n is the number of TCHs under the BTS. Hence, for a 2/2/2 site (no GPRS):
RSLGSM)GPRS@64k +
14 * 3 * (95 ) 67 * 0.12 ) 35 * 2.6 ) 25 * 2.5) (47 ) 3 * 3) * 10 ) (52 ) 3) 6*0

) )
1000 * 0.25 * 100 8000 * 0.25 1000 * 0.25
+ 0.95
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:
[(nTCH + nPDTCH + L16) / 4] + L64
N BSC*BTS +
31
Number of E1 links required between each 2/2/2 BTS and BSC:
+ [(14 * 3)ń4 ) 2]ń31 X 1
Number of E1 links required between each omni 2 BTS and BSC:

+ [(14ń4) ) 1]ń31 X 1
Hence, only one E1 interconnect is required between each BTS and BSC for the
given site configurations (provided they are in star configurations), giving a total of
60 E1 links.
Number of LCF–RSLs required if given by:
G L3 +
ƪn * (1 ) 0.42 * S ) 0.45(23.2* H**T)(1 * 0.4 * i) ) 0.36 * L) ) (0.00072 * P ) 0.004) * B ) 120

C ƫ
Where, n is the number of TCHs under a BSC:
ƪ 2380 * (1 ) 0.42 * 1.12 ) 0.45 * 2.6 * (1 * 0.4 * 0.6) ) 0.36 * 2.5)

(23.2 * 100)
) (0.00072 * 8 ) 0.004) * 60 )
170
120
ƫ
The number of LCFs for RSL processing is 5.

10–34 68P02900W21-K 30th Jun 02
GMR-01
Determining the number of MTLs

Total Erlangs offered by the BSC with 55 sites with 2/2/2 configuration and 5 omni
2 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 omni
2 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:
P pc ) P * TńN + 8 * 100ń1423 + 0.57
Using the call model parameters, the number of MTLs can be calculated using
formulae mentioned in Chapter 5 of this manual.
Maximum number of Erlangs supported by a C7 link is given by:
(1000 * U * T)
n link +
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 9 * P PC)
(1000 * 0.25 * 100)
n link +
(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 signalling
link is given by:
(20 * T)
nl LCF*MTL +
(1 ) 0.16 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.42 * L ) P PC * (0.005 * B ) 0.05))
(20 * 100)
nl LCF*MTL +
(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:
nl min + min(nlink , nlLCF*MTL) + 178 Erlangs
Amount of traffic (or number of trunks) each logical link will hold:
N logical + 1423ń64 + 22.23
using a MTL load sharing granularity of 64.

The number of logical links each MTL can handle:
n log_per_mtl + round down(178ń22.23) X 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 t nl LCF*MTL
N LCF + ROUND UP 8 + 4
2
ǒǓ

30th Jun 02 68P02900W21-K 10–35
GMR-01
XBL requirements
Referring to Table 5-11 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 X 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 of
MSIs 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 the

number of GDP/XCDRs in the BSC.
N + 13 * 32 ) 36 * 64 + 2720
Each KSW provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs would
be 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 (since
we have no local transcoding):
N BSUGń8 + 13ń8 X 2 BSU cages
N BSU(M ) R)ń12 + 36ń12 X 3 BSU cages
Therefore, 3 BSU cages are required to accommodate all the hardware needed for
this configuration. Ensure the following is true for each cage:
N ) (G * n) ) (M * 64) ) (R * 16) v 1016

10–36 68P02900W21-K 30th Jun 02
GMR-01
KSWX requirements
KSWX extends the TDM highway of a BSU to other BSUs and supplies clock
signals to all shelves in the multi-shelf configuration. The KSWX maybe used in
expansion, remote and local modes. We require 3 BSU cages with 3 master/
redundant KSWs, which implies 2 expansion cages.
Number of KSWXs required is sum of KSWXE, KSWXR, and KSWXL:
N KX + NKXE ) N KXR ) N KXL
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 CLKXs
required is given by:
N CLKX + ROUND UP(E6) * (1 ) R F)
Where E is the number of expansion/extension shelves and RF is the redundancy

factor.
N CLKX + ROUND UP(3ń6) * (1 ) 1) + 2
The number of CLKX required (with redundancy) = 2.

LANX requirements
N LANX + NBSU * (1 ) RF) + 3 * 2 + 6
Where, RF it the redundancy factor.

Total number of LANXs required (with redundancy) = 6.
PIX requirements
PIX v Number of BSUs + 6
Line interfaces
Number of T43s + Number of MSIsń3 + 36ń3 X 12

30th Jun 02 68P02900W21-K 10–37
GMR-01

The number of PSUs required is given by:
PSUs + N BSU * (2 ) R F)
PSUs + 3 * (2 ) 1) + 9
One redundant PSU is required for each BSU shelf, hence total number of PSUs
required is 9.
BBBX = Number of BSUs for battery backup (recommended) = 3.
Non volatile memory (NVM) board for BSC (optional)
NVM + 0 or 1

10–38 68P02900W21-K 30th Jun 02
GMR-01
Step 3 : RXCDR planning

Conventionally, multiple BSCs connect to an RXCDR and vice versa, for load sharing
and redundancy purposes. Assuming that two same sized BSCs connect to 2 RXCDRs
so that the signalling traffic and voice traffic is equally distributed over 2 RXCDRs, each
RXCDR 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:
N RXCDR*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.
N RXCDR*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 the
RXCDR.
RXU shelves
The number of RXU shelves required is given by (assumes an NVM board is
fitted):
N RXU + max(Mń5, (R ) N NVM)ń16) + max(6ń5, (47 ) 1)ń16) X 3
Hence, 3 RXU shelves are required to equip 47 XCDR cards and 6 MSI cards.
Ensure the following is true for each cage:
N ) (G * n) ) (M * 64) ) (R * 16) v 1016
GPROC2 requirements for RXCDR

Each shelf should have minimum of one GPROC2. Hence, 3 non-redundant
GPROC2s are required. If the operator chooses to use redundancy 6 GPROC2s
would 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-redundant

KSWs are required for RXCDR with this configuration.

30th Jun 02 68P02900W21-K 10–39
GMR-01
KSWX requirements for RXCDR

The number of KSWXs required is the sum of KSWXE, KSWXR, and KSWXL. The
above calculations imply 1 expansion and 1 extension cage are required.
N KX + NKXE ) N KXR ) N KXL
N KXE + K * (K * 1) + 2 * 1 + 2
K is the number of non-redundant KSWs.

N KXR + S E + 1
SE is the number of extension shelves.

N KXL + K ) S E + 3
N KX + 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:
N CLKX + ROUND UP(Eń6) * (1 ) R F)
Where:
E is the number of expansion/extension shelves.
RF is the redundancy factor.
N CLKX + ROUND UP(2ń6) * (1 ) 1) + 2
The number of redundant CLKXs required is 2.

LANX requirements
Number of LANXs required is given by:
N LANX + NRXU * (1 ) RF) + 3 * 2 + 6

Total number of LANXs required with redundancy = 6.
PIX requirements
PIX v 2 * Number of RXUs + 6
Hence, 6 PIX cards are required for RXCDR.

10–40 68P02900W21-K 30th Jun 02
GMR-01
Line interfaces
Number of T43s + Number of E1sń6 + (47 ) 12)ń6 X 10

PSUs + 2 * RXUs + 6
One redundant PSU is required for each RXU shelf, hence total number of PSUs
required is 9.
BBBX = Number of BSUs for battery backup (recommended) = 3.
Non volatile memory (NVM) board for RXCDR (optional)
NVM + 1 (in this example)

30th Jun 02 68P02900W21-K 10–41
GMR-01
A planning example of BSS support for LCS provisioning GSM-001-103
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 on
information provided in Chapter 8.

Use this example to plan the equipment of a BSC supporting a traffic model with the
parameters listed in Table 10-12 and their typical values. This indicates a large
configuration with 64 sites/BSC, 3 cells/BTS and 2 carriers/cell.
Table 10-12 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

10–42 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 A planning example of BSS support for LCS provisioning
LCS planning example calculations

Step 1: Determine LCS architecture
BSS–based LCS architecture will be supported.
Step 2: Calculate MTLs (actually needed trucks number is 1812)

n link_bss +
(1000 * U * T)
(40 ) 47 * S ) 22 * H * (1 * 0.8 * i) ) 24 * L ) 31 * L CS) ) 9 * P PC * (1 ) L CS)
=
(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
nl LCF*MTL +
(20 * T)
(1 ) 0.16 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.42 * L ) 0.45 * L CS) ) 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
nl min + MIN (n link, nl LCF_MTL) + 151.468
N logical + N + 1812 + 2831

Ng 64

Nlogical
Ǔ + 5
Finally, the number of required MTLs with 64 logical links is:
log_per_mtl
Ǔ + 13
Step 3: Calculate MTL LCFs

N LCF_MTL + 13 + 6
2
Step 4: Calculate RSLs

According to Chapter 3 , TCHs per BTS is 29*3. Then,
RSL GSM@64k +
n * (49 ) 50 * S ) 32 * H ) 20 * L ) L CS * 24) (27 ) 3 * C) * P GSM * (1 ) L CS)

)
1000 * U * T 8000 * U
=
87 * (49 ) 50 * 0.1 ) 32 * 2.5 ) 20 * 2 ) 0.05 * 24) (27 ) 3 * 3) * 3 * (1 ) 0.05)
)
1000 * 0.25 * 120 8000 * 0.25
= 0.87

30th Jun 02 68P02900W21-K 10–43
GMR-01
A planning example of BSS support for LCS provisioning GSM-001-103
Step 5: Calculate RSL LCFs

G L3 +
ƪ n * (1 ) 0.42 * S ) 0.45 * H * (1 * 0.4 * i) ) 0.36 * L ) 0.45 * L CS)

(23.2 * T)
) (0.004 ) 0.000722 * P GSM * (1 ) L CS)) * B )
C
120
ƫ
=
ƪ 3000 * (1 ) 0.42 * 0.1 ) 0.45 * 2.5 * (1 * 0.4 * 0.6) ) 0.36 * 2 ) 0.45 * 0.05)
(23.2 * 120)
) (0.004 ) 0.000722 * 1.0225 * 3) * 30 ) ƫ
86
120
= 4.64
So the RSL LCFs number is 5.
Step 5: Calculate LMTLs
L MTL + ROUND UP ǒ LCS_BSC_Rate * 19

1000 * U BSC_SMLC
Ǔ
+ ROUND UP ǒ1000
2 * 19 Ǔ
* 0.2
=1
Step 6: Calculate LMTL LCFs

NLCF_LSL = 1.

10–44 68P02900W21-K 30th Jun 02
GMR-01
Chapter 11
Paging rate and location area
planning

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Location area planning overview
Location area planning overview
Introduction to location area planning

This chapter provides, by example, a description of location area planning. This exercise
should be undertaken by each operator to optimize the network configurations based on
the paging load on the BSC.
Location area planning considerations

Prior to the GSR4 BSS software release, the traffic handled by the BSC was limited by
the number of BTSs and carriers that could be handled by the BSC. Increasing BSC
capacities have an impact on some of the call model parameters, especially the paging
load on the BSC.
Since an MS is paged in a location area, paging rate depends on the number and size of
BSCs in that location area. If there are too many BSCs in a location area, each with large
number of BTS sites and high traffic handling capacity, it results in high paging load on
each 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 to
break 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 location
updates on the cells bordering the location area. More SDCCHs have to be provisioned
for this increased signalling on the border cells and hence, fewer channels are available
for traffic.
A well planned network should have similar paging loads in each location area. A very
small paging load would suggest that the location area is too small and could be
combined with neighbouring location areas, minimising location update activity and
reducing use of SDCCH resources. A paging load too close to the theoretical maximum
paging load (calculated using the number of PCHs used and if mobile is paged using
IMSI or TMSI) would suggest that the location area is too large and should be split into
multiple location areas, to avoid paging overload and the need for extra hardware.
This exercise should be undertaken by each operator to optimise the network
configurations based on the paging load on the BSC. This topic is explained further, with
an example, in the following text.

30th Jun 02 68P02900W21-K 11–1
GMR-01
Location area planning GSM-001-103
Location area planning
Example procedure
Assume a network with four BSCs under a location area (see Figure 11-1) each with
following call model parameters:
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/2
configurations and 2 sites with omni 2 configuration) of traffic.
Figure 11-1 Four BSCs in one LAC
MSC
LAC=1
BSC BSC BSC BSC
ig.069.rh

11–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Location area planning
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 using
the formula detailed in chapter 5:
(2044 * (1 ) 0.7 * 0.05 ) 0.5 * 2 * (1 * 0.3 * 0.4) ) 0.5 * 2.1)ń11.3 * 70 )
(0.006 ) 0.02 * 24) * 50 ) 148ń35)ń2.5 + 13.8
The number of GPROC2s required for RSL is 14.

Since most of the cells in the BSC are non-border cells, the location updates per cell is
around 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 GOS
of 2% is 9.83 Erlangs.
Using the formulae for control channel calculations, as provided in Chapter 3:
Call arrival rate:
l call + eńT + 9.83ń60 + 0.164

l S + S * eńT + 0.05 * 9.83ń60 + 0.008

l LU + L * eńT + 2.1 * 9.83ń60 + 0.344
The average number of SDCCHs, NSDCCH is given by:

N SDCCH + lcall * T C ) lLU * (T L ) T g) ) l S * (T S ) T g)
+ 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, with
less that 1% blocking as determined by use of Erlang B tables, is 7. Hence the number of
timeslots required to carry SDCCH signalling traffic is 1 with each timeslot offering 8
SDCCHs.
Now, use the same call model parameters and divide the location area so that each
location area contains two BSCs (see Figure 11-2). Dividing the location area into two
location areas increase the location updates on the border cells. Assume that 25% of the
cells under a BSC become border cells (a conservative estimate) and the number of
location updates per call go up to 6 on cells on the location area border. The average
number of location updates per call for the BSC would approximately equal 3 (0.25*6 +
0.75*2).

30th Jun 02 68P02900W21-K 11–3
GMR-01
Location area planning GSM-001-103
Figure 11-2 Four BSCs divided into two LACs
MSC
LAC = 1 LAC = 2
BSC BSC BSC BSC
ig.068.rh
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 = 10 (use the formula).

Call arrival rate:
l call + eńT + 9.83ń60 + 0.164

l S + S * eńT + 0.05 * 9.83ń60 + 0.008

l LU + L * eńT + 6.1 * 9.83ń60 + 0.999
The average number of SDCCHs for border cells, NSDCCH is given by :

N SDCCH + lcall * T C ) lLU * (T L ) T g) ) l S * (T S ) T g)
+ 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 with
less than 1% blocking as determined by use of Erlang B tables, is 13. Hence the number
of timeslots required to carry SDCCH signalling traffic is 2, with each timeslot offering 8
SDCCHs.
If the network planner is careful enough to divide the location area such that not too
much traffic crosses the border of the location area (resulting in a lower number of
location updates), even less resources might be required of the air interface for location
update signalling.

11–4 68P02900W21-K 30th Jun 02
GMR-01
Chapter 12
Deriving call model parameters
from network statistics

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction to deriving call model parameters

This chapter describes the derivation of call model parameter values from the GSM
network statistics collected at the OMC-R. Most of the calculations used for equipment
planning use the standard call model parameters. Each network behaves uniquely, and
operators 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 the
configurations on a network.
All the statistics used for determining the call model parameters must be collected during
busy 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 at
the BSC level for equipment dimensioning purposes. This would give more scope of
averaging out the load from the network entities.

30th Jun 02 68P02900W21-K 12–1
GMR-01
Deriving call model parameters from network statistics GSM-001-103
Deriving call model parameters from network statistics

Standard call model parameters
Table 12-1 lists the standard call model parameters.
Ratio of LCSs per call Lcs = 0.2
Mobile orginated LCS ratio LRMO = 0.05
GPRS parameters
CS2 = 13.4 kbit/s
CS3 = 15.6 kbit/s
CS4 = 21.4 kbit/s
L is a function of l, Id and whether short message sequence (type 1) or long message

sequence (type 2) is used for IMSI detach. Typically Id = 0 (disabled), but when it is
enabled:
Type 1: L = I + 0.2 * Id
Type 2: L = I + 0.5 * Id

12–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Deriving call model parameters from network statistics
Call duration (T)

Average call duration for a network may be derived from the statistics
BUSY_TCH_MEAN and TOTAL_CALLS using the following formula:
ȍ(BUSY_TCH_MEAN) * stat_interval_in_sec
N
i+1
T+
ȍ(TOTAL_CALLS ) ASSIGNMENT_REDIRECTION)
N
i+1
Where: N is: the number of cells under the

BSC.
BUSY_TCH_MEAN the average number of busy TCHs
in the cell and is updated each
time an allocation or de-allocation
of a TCH occurs. It provides a
mean value indicating the average
number of TCHs in use. The time
recorded for a TCH in use includes
the guard time (T3111), which is
the time allowed between ending a
call and being allowed to start
another call.
TOTAL_CALLS the number of circuit oriented calls
that are originated in the cell. It is
pegged only once per connection
at the time of the first successful
TCH assignment procedure.
Subsequent channel changes are
not counted.
ASSIGNMENT_REDIRECTION the total number of assignments
that were redirected to another
cell, due to redirected retry
handover procedure, multiband
band re-assignment procedure, or
handover during assignment
procedure.
stat_interval_in_sec the interval in which statistics are
collected. It is 3600 if the statistic
interval is one hour and 1800 if the
statistic interval is 30 minutes.
Call duration (T) in the above formula is calculated for one cell and should be calculated
as an average of call durations of all the BSCs in the network.
NOTE The ASSIGNMENT_REDIRECTION statistic is only available

from software release GSR5 onwards.

30th Jun 02 68P02900W21-K 12–3
GMR-01
Ratio of SMSs per call (S)

The number of SMSs per call, may be calculated using the SMS related statistics
parameters in the following formula:
ȍ(SMS_NO_BCAST_MSG ) SMS_INT_ON_SDCCH ) SMS_INIT_ON_TCH)

N
i+1
S+
N
i+1

BSC.
SMS_NO_BCAST_MSG the number of times a message is
broadcast on the CBCH.
SMS_INIT_ON_SDCCH the number of times an SMS
transaction occurred on a SDCCH.
SMS_INIT_ON_TCH the number of times an SMS
transaction occurred on a TCH.
procedure.
The ratio of SMSs per call must be averaged over all the BSCs in the network.

12–4 68P02900W21-K 30th Jun 02
GMR-01
Ratio of handovers per call (H)

Handovers may be inter-BSS, intra-BSS or intra-cell. Therefore, the number of
handovers per call may be calculated using the following formula:
ȍ(out_inter_bss_req_to_msc ) out_intra_bss_ho_atmp ) intra_cell_ho_atmp)

N
i+1
H+
N
i+1

BSC.
out_inter_bss_req_to_msc the number of outgoing inter-BSS
handover requests to the MSC.
out_intra_bss_ho_atmpt the number of times assignment
command is sent to an MS to
initiate an outgoing intra-BSS
handover attempt.
intra_cell_ho_atmpt the number of times an
assignment command is sent to an
MS to initiate an intra-cell
handover attempt.
procedure.
H should be averaged over all the BSCs in the network.
NOTE The TOTAL_CALLS parameter is the count of the total

circuit-switched calls in a cell. It should be summed for all the
cells 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:
ȍ(out_intra_bss_ho_atmpt ) intra_cell_ho_atmp)
N
i+1
i+
ȍ out_inter_bss_req_to_mac ) out_intra_bss_ho_atmpt ) intra_cell_ho_atmp)
N
i+1

BSC.
i should be averaged over all the cells in the network.

30th Jun 02 68P02900W21-K 12–5
GMR-01
Ratio of location updates per call (I)

The ratio of location updates per call, for a cell, may be calculated using the following
formula:
ȍ OK_ACC_PROC[location update]
N
i+1
I+
N
i+1

BSC.
OK_ACC_PROC[location_update] counts the number of MS
requests for location updates.
ASSIGNMENT_REDIRECTION counts the total number of
assignments that were
redirected to another cell, due to
redirected retry handover
procedure, multiband band
re-assignment procedure, or
procedure.
I ratio should be averaged over all the BSCs in the network.
Ratio of IMSI detaches per call (Id)

IMSI detaches is 0 if disabled. If enabled, it may be calculated per cell as follows:
ȍ OK_ACC_PROC[imsi_detach]
N
i+1
Id +
N
i+1

BSC.
OK_ACC_PROC[imsi_detach] counts the number of MS
requests for IMSI detach.
ASSIGNMENT_REDIRECTION counts the total number of
assignments that were
redirected to another cell, due to
redirected retry handover
procedure, multiband band
re-assignment procedure, or
procedure.
Id should be averaged over all the BSCs in the network.

12–6 68P02900W21-K 30th Jun 02
GMR-01

The location update factor is calculated using the ration of location updates per call (l)
and the ratio of IMSI detaches per call (Id). For networks with IMSI detach disabled, the
location 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. Id=0 )
S L = l + 0.2* Id (type 1)
S L = l + 0.5* Id (type 2)
IMSI detach types have to do with the way the MSC clears the connection with the BSS
after receiving the IMSI detach. When using IMSI detach type 1, the MSC clears the
SCCP connection, a clearing procedure that involves only one uplink (average size of
42 bytes) and one downlink message (average size of 30 bytes). When using IMSI
detach type 2, the MSC sends the CLEAR COMMAND and the BSS sends CLEAR
COMPLETE, etc., which involves three uplink (average size of 26 bytes) and three
downlink messages (average size of 30 bytes). A location update procedure itself takes
five downlink messages (average size of 30 bytes) and six uplink messages (average
size of 26 bytes).
Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number of
messages as a location update and a IMSI detach (type 2) takes 6/11 (approximately
0.5) of the messages of a location update.
Paging rate (P)

PAGE_REQ_FROM_MSC counts the number of paging messages received by the BSS
from the MSC during the statistics time interval. The paging message is then sent to the
BSS in an attempt to locate a particular MS. Each message refers to only one MS. The
BSS In turn will transmit a paging message over the PCH, which may include identities
for 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 also
be 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 cell
basis, the value of this counter for any cell in that location area for a given statistics
interval, would denote the pages in the location area in that statistics interval time.
ȍ(PAGE_REQ_FROM_MSC)
N
i+1
P+
stat_interval_in_seconds [ith location area in BSC]
Where: PAGE_REQ_FROM_MSC is: the number of paging messages

received from the MSC by the
BSS. This statistic is pegged
when a paging message is
received pertaining to the cell in
which the MS is paged.

30th Jun 02 68P02900W21-K 12–7
GMR-01
Pages per call (PPC)

Pages per call for a BSC may be calculated as:
ȍ PAGE_REQ_FROM_MSC
N
i+1
P pc +
N
i+1
Where: N is: the number of cells under the BSC.
Alternatively, pages per call may be calculated using the formula:
P pc + P * TńN
Where: N is: the number of MSC–BSC trunks.

T the call duration, in seconds.
Or:
P pc + P * Tńe
Where: e is: the BSC Erlang.
Sample statistic calculations

Table 12-2 shows a sample of statistics collected for one BTS in the BSC for a one hour
interval.
Table 12-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 be
calculated as follows:

12–8 68P02900W21-K 30th Jun 02
GMR-01
Call duration (T)

Call duration is given by:
ȍ BUSY_TCH_MEAN * stat_interval_in_sec
N
i+1
T+
ȍ(TOTAL_CALLS_ ) ASSIGNMENT_REDIRECTION
N
i+1
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 duration
value used for dimensioning purposes should be the average of call durations over all the
BSCs in the network.
No. of SMSs per call (S)

The number of SMSs per call is given by:
ȍ(SMS_NO_BCAST_MSG ) SMS_INIT_ON_SDCCH ) SMS_INIT_ON_TCH)

N
i+1
S+
ȍ TOTAL_CALLS ) ASSIGNMENT_REDIRECTION
N
i+1
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:
ȍ(out_inter_bss_req_to_msc ) out_intra_bss_ho_atmpt ) intra_cell_ho_atmpt)

N
i)1
H+
N
i+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:
ȍ(out_intra_bss_ho_atmpt ) intra_cell_ho_atmp)
N
i+1
i+
ȍ(out_inter_bss_req_to_msc_ ) out_intra_bss_ho_atmpt_ ) intra_cell_ho_atmpt)
N
i+1
[(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:
ȍ(OK_ACC_PROC[location_update])
N
i+1
l+
N
i+1
l=(746+1056+268) / (571+927+1407) + 0 + 0 + 0 = 0.712

30th Jun 02 68P02900W21-K 12–9
GMR-01
IMSI detaches per call (Id)

The number of IMSI detaches per call is given by:
ȍ(OK_ACC_PROC[imsi_detach])
N
i+1
ld +
N
i+1
Id = (28+49+76) / (571+927+1407 +0 +0 + 0) = 0.052

The location update is given by:
L + l ) 0.5 * l d
L = 0.712 + 0.5 * 0.052 = 0.738
Paging Rate (P) for a BSC

The paging rate for a BSC (with multiple location areas) can be calculated as:
S I (PAGE_REQ_FROM_MSC)
P+
stat_interval_in_seconds[ith location area]
Since, in this case the BSC has only one location area, P is given by:
P + 43696ń3600 + 12.13 pages per second
All call model parameters should be calculated by taking an average over all the BSCs in
the entire network.
This example illustrates the computation of call model parameters from the network
statistics obtained from the OMC-R. As previously mentioned, It is recommended that
statistics collected at busy hours over a long period of time (a couple of months) are used
for all calculation purposes.

12–10 68P02900W21-K 30th Jun 02
GMR-01
Chapter 13
Standard BSS and Horizon BTS
configurations

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
BSS/BTS equipment covered

This chapter provides diagrams of the logical interconnections of the components in
various standard BSS and Horizon BTS site configurations, for macrocell and microcell
systems. Typical RF configurations are also provided.
Previous generation (M-Cell) BTS site / RF configurations are provided in Chapter 13.
This chapter contains the following information:
S Typical BSS configurations.
S One cabinet Horizonmacro configurations.
S Two cabinet Horizonmacro configurations.
S Three cabinet Horizonmacro configurations.
S Four cabinet Horizonmacro configurations.
S Horizonmacro and Horizoncompact2 macrocell RF configurations.
S Horizonmicro2 microcell RF configurations.
S Connecting Horizon BTSs to M-Cell6 BTSs.

30th Jun 02 68P02900W21-K 13–1
GMR-01
Standard configurations GSM-001-103
Standard configurations
Introduction to standard configurations

The examples in this section are shown with individual antennas for transmit and receive
signals. 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 typical
configuration using that specific equipment. Rather, they are meant to highlight the
configurations that, within the constraints of the BSS architecture, are feasible when the
macrocell hardware is deployed in a digital equipment shelf controlled BTS. The
diagrams also show possible cabinet boundaries. Cabinet designs, however, allow for a
number of different arrangements of the same configuration.
Rather than showing redundancy for all Horizonmacro BTS configurations, the control
redundancy is depicted only for one Horizonmacro cabinet diagram (see Figure 13-4).

13–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Typical BSS configurations
Typical BSS configurations
BSC with 24 BTSs

The digital module configuration for a BSC controlling 24 BTSs is shown in Figure 13-1.
Figure 13-1 BSC controlling 24 BTSs
DUAL IEEE LAN

LANX LANX
BSU SHELF 1
A B DUAL MCAP BUS
DUAL SERIAL BUS
GPROC GPROC GPROC GPROC KSW GCLK GCLK

PIX BTC 0 1 2 3 A
REDUNDANT
A
DUAL TDM HIGHWAY BUS B
RMT LCL CLKX LCL

KSWX CLKX KSWX KSWX BTC MSI MSI MSI MSI
A A B 0 1 2 7
2 Mbit/s LINKS
BTS 1 BTS 2 BTS 3 BTS 12

FIBRE OPTIC LINKS
MSC/RXCDR
2.048 Mbit/s LINK INTERFACES

FROM/TO MSC AND TO/FROM BTS
SITES
BTS 13 BTS 14 BTS15,16 BTS 23, 24
2 Mbit/s LINKS
DUAL SERIAL BUS
LCL LCL RMT

KSWX KSWX KSWX BTC MSI MSI MSI MSI
A B B 0 1 2 6
B
DUAL TDM HIGHWAY BUS
BTC GPROC GPROC GPROC KSW

0 1 2 B
REDUNDANT DUAL MCAP BUS

LANX LANX
A B
DUAL IEEE LAN BSU SHELF 2
BSSC CABINET

30th Jun 02 68P02900W21-K 13–3
GMR-01
Typical BSS configurations GSM-001-103
BSC with full redundancy

The digital module configuration for a fully redundant BSC controlling 34 BTSs is shown
in Figure 13-2.
Figure 13-2 Fully redundant BSC controlling 34 BTSs
DUAL IEEE LAN

BSU SHELF 1
LANX LANX
A B
DUAL SERIAL BUS DUAL MCAP BUS
GPROC GPROC GPROC GPROC KSW KSW GCLK GCLK

PIX BTC A B
0 1 2 3 A B
REDUNDANT
A
B
EXP EXP LCL

KSWX KSWX CLKX LCL
KSWX CLKX KSWX BTC MSI MSI MSI MSI
A B B 0 1 2 9
A
2 Mbit/s LINKS
BTS 1 BTS 2 BTS 3 BTS 16,17
FIBRE OPTIC LINKS

MSC
2.048 Mbit/s LINK INTERFACES

FROM/TO MSC AND TO/FROM BTS
SITES
BTS 18 BTS 19 BTS 20 BTS 33,34
2 Mbit/s LINKS
EXP EXP LCL LCL

KSWX A KSWX KSWX KSWX BTC MSI MSI MSI MSI
B A B 0 1 2 9
A
B
GPROC GPROC GPROC GPROC
BTC 0 1 2 3 KSW KSW DUAL MCAP BUS
A B
REDUNDANT
DUAL SERIAL BUS LANX LANX
A B
DUAL IEEE LAN BSU SHELF 2
BSSC CABINET

13–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Typical BSS configurations
Transcoder
The digital module configuration for a BSSC cabinet equipped to provide transcoding is
shown in Figure 13-3.
Figure 13-3 BSSC cabinet equipped to provide transcoding
DUAL IEEE 802.5 LAN

RXU SHELF 1
LANX LANX
A B
DUAL SERIAL BUS DUAL MCAP BUS
BTC GPROC GPROC KSW GCLK GCLK

0 1 A
REDUNDANT
A
B
RMT LCL LCL

KSWX BTC MSI MSI XCDR XCDR
KSWX CLK KSWX CLKX
B 0 1 0 15
A X A
FIBRE OPTIC LINKS 2.048 Mbit/s LINK 2.048 Mbit/s LINK

INTERFACES FROM/TO INTERFACES FROM/TO
BSCS MSC
LCL LCL RMT

KSWX KSWX KSWX MSI MSI XCDR XCDR
B B BTC
A 0 1 0 15

B
BTC GPROC GPROC KSW

0 1 DUAL MCAP BUS
B
REDUNDANT
DUAL SERIAL BUS
LANX LANX B
A
DUAL IEEE LAN
RXU SHELF 2
REMOTE TRANSCODER CABINET

30th Jun 02 68P02900W21-K 13–5
GMR-01
Single cabinet BTS configuration GSM-001-103
Single cabinet BTS configuration
Single cabinet Horizonmacro BTS

The configuration shown in Figure 13-4 is an example of a one-cabinet Horizonmacro.
This configuration supports six carriers.
Figure 13-4 Macrocell BTS with one Horizonmacro cabinet
DIGITAL EQUIPMENT SHELF

N N
I I
U U
MCUF MCUF
(FOR
REDUNDANCY)
12 12
2 2 2 2 2 2
C C C C C C
T T T T T T
U U U U U U
2 2 2 2 2 2
Horizonmacro
CABINET

13–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Two cabinet BTS configuration
Two cabinet BTS configuration
Two cabinet Horizonmacro BTS

The configuration shown in Figure 13-5 is an example of a two cabinet Horizonmacro.
This configuration supports 12 carriers. The MCUF interfaces to the CTUs in the second
cabinet through an FMUX in the second cabinet.
Figure 13-5 Macrocell BTS with two Horizonmacro cabinets
N DIGITAL EQUIPMENT SHELF Horizonmacro

I CABINET
U
2
MCUF
12
2 2 2 2 2 2
C C C C C C
T T T T T T
U U U U U U
Horizonmacro
CABINET 2 2 2 2 2 2 DIGITAL
12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X

30th Jun 02 68P02900W21-K 13–7
GMR-01
Three cabinet BTS configuration GSM-001-103
Three cabinet BTS configuration
Three cabinet Horizonmacro BTS

The configuration shown in Figure 13-6 is an example of a three cabinet Horizonmacro.
This configuration supports 18 carriers. The MCUF interfaces to the CTUs in the other
cabinets through the FMUXs.
Figure 13-6 Macrocell BTS with three Horizonmacro cabinets

I CABINET
U
MCUF
2
12
2 2 2 2 2 2
C C C C C C
T T T T T T
U U U U U U
Horizonmacro
2 2 2 2 2 2 DIGITAL
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X
Horizonmacro
2 2 2 2 2 2 DIGITAL
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X

13–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Four cabinet BTS configuration
Four cabinet BTS configuration
Four cabinet Horizonmacro BTS

The configuration shown in Figure 13-7 is an example of a four cabinet Horizonmacro.
This configuration supports 24 carriers. The MCUF interfaces to the CTUs in the other
cabinets through the FMUXs. An additional FMUX is required in the main cabinet to
support the third extension cabinet.
Figure 13-7 Macrocell BTS with four Horizonmacro cabinets

I CABINET
U
F
M 2
12 U
X
MCUF 2
12
2 2 2 2 2 2
C C C C C C
T T T T T T
U U U U U U
Horizonmacro 2 2 2 2 2 2 DIGITAL
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T F
U U U U U U M
U
X

30th Jun 02 68P02900W21-K 13–9
GMR-01
Horizon macrocell RF configurations GSM-001-103
Horizon macrocell RF configurations
Overview of configuration diagrams

The Horizon macrocell BTS cabinets/enclosures are presented as follows:
S Horizonmacro cabinets.
S Horizoncompact2 enclosures.
Horizonmacro cabinets
The following series of Horizonmacro RF configuration diagrams show suggested ways
of connecting together Horizonmacro SURF and Tx blocks to meet different operational
requirements. The series of diagrams is by no means exhaustive, and numerous
alternative configurations may be adopted to achieve the same aim.
Each diagram is applicable to either EGSM900 or DCS1800 operation, though the SURF
module 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 as
those 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 provided
for dual band 900 use.
NOTE GSR5.1 or higher supports the use of the GSM850 and

PCS1900 frequency bands in Horizonmacro BTSs. RF
configurations for these BTSs are the same as for those shown
in this chapter for EGSM900/DCS1800 BTSs.
Note that the 850 and 1900 SURFs are single band only and do
not support dual band operation. Also, the GSM850 and
PCS1900 BTS variants do not support the use of CCBs or dual
band TDFs.
Rules for equipping Horizonmacro cabinets

The following rules apply when equipping any Horizonmacro cabinet for the
configurations shown in Figure 13-8 to Figure 13-15:
S A maximum of six CTUs can be accommodated.
S An external equipment cabinet is not required.

13–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Horizon macrocell RF configurations
[DCS1800] 4 carrier omni, with duplexed hybrid and air combining

Figure 13-8 shows a single cabinet, four CTU configuration with duplexed hybrid and air
combining. Table 13-1 provides a summary of the equipment required for this
configuration.
Figure 13-8 4 carrier omni, duplexed hybrid and air combining
Tx/Rx Tx/Rx
ANTENNA ANTENNA
A B
B2 1 0 A 2 1 0 B A
SURF
DCF DCF
C C C C
T T T T
U U U U
A A A A
B B B B
Horizonmacro CABINET
Table 13-1 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
Transmitter/receiver
2 DCF

30th Jun 02 68P02900W21-K 13–11
GMR-01
[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and air

combining
Figure 13-9 shows a single cabinet, six CTU configuration with duplexed dual-stage
hybrid and air combining. Table 13-2 provides a summary of the equipment required for
this configuration.
Figure 13-9 6 carrier omni, duplexed dual-stage hybrid and air combining
Tx/Rx Tx/Rx
ANTENNA ANTENNA
A B
B2 1 0 A 2 1 0 B A
SURF
FEED
THROUGH DDF
DDF
C C C C C C
T T T T T T
U U U U U U
A A A A A A
B B B B B B
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

13–12 68P02900W21-K 30th Jun 02
GMR-01
[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining

Figure 13-10 shows a single cabinet, six CTU configuration with duplexed dual-stage
hybrid combining. Table 13-3 provides a summary of the equipment required for this
configuration.
Figure 13-10 2 sector (3/3), duplexed dual-stage hybrid combining
Tx/Rx Tx/Rx Rx Rx
ANTENNA ANTENNA ANTENNA ANTENNA
(SECTOR 1) (SECTOR 2) (SECTOR 1) (SECTOR 2)
B B A A
B2 1 0 A 2 1 0 B A
SURF
FEED
THROUGH
DDF DDF
C C C C C C
T T T T T T
U U U U U U
A A A A A A
B B B B B B
duplexed dual-stage hybrid combining
Quantity Unit
4 Antennas
6 CTU
Receiver
1 SURF
2 DDF

30th Jun 02 68P02900W21-K 13–13
GMR-01
[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and air

combining
Figure 13-11 shows a dual cabinet, 12 CTU configuration with duplexed dual-stage hybrid
and air combining. Table 13-4 provides a summary of the equipment required for this
configuration.
Figure 13-11 2 sector (6/6), duplexed dual-stage hybrid and air combining
Tx/Rx Tx/Rx Tx/Rx Tx/Rx

A B A B
B2 1 0 A 2 1 0 B A B2 1 0 A 2 1 0 B A
SURF SURF
FEED
FEED
THROUGH
THROUGH
DDF DDF DDF DDF
C C C C C C C C C C C C
T T T T T T T T T T T T
U U U U U U U U U U U U
A A A A A A A A A A A A
B B B B B B B B B B B B
EXTENDER Horizonmacro CABINET MASTER Horizonmacro CABINET
Table 13-4 Equipment required for dual cabinet, 12 CTU configuration,

Quantity Unit
4 Antennas
2 Horizonmacro cabinets
12 CTU
Receiver
2 SURF
4 DDF

13–14 68P02900W21-K 30th Jun 02
GMR-01
[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining

Figure 13-12 shows a single cabinet, six CTU configuration with duplexed hybrid
configuration.
Figure 13-12 3 sector (2/2/2), duplexed hybrid combining
Tx/Rx Tx/Rx Tx/Rx Rx Rx Rx

ANTENNA ANTENNA ANTENNA ANTENNAS ANTENNAS ANTENNAS
(SECTOR 3) (SECTOR 2) (SECTOR 1) (SECTOR 3) (SECTOR 2) (SECTOR 1)
B B B A A A
B2 1 0 A 2 1 0 B A
SURF
DCF DCF DCF
C C C C C C
T T T T T T
U U U U U U
A A A A A A
B B B B B B
duplexed hybrid combining
Quantity Unit
6 Antennas
6 CTU
Receiver
1 SURF
3 DCF

30th Jun 02 68P02900W21-K 13–15
GMR-01
[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining

Figure 13-13 shows a dual cabinet, 12 CTU configuration with duplexed hybrid and air
configuration.
Figure 13-13 3 sector (4/4/4), duplexed hybrid and air combining

Tx/Rx Tx/Rx Tx/Rx Tx/Rx
A B A B A B
B2 1 0 A 2 1 0 B A B2 1 0 A 2 1 0 B A
SURF SURF
DCF DCF DCF DCF DCF DCF
EXTENDER Horizonmacro CABINET MASTER Horizonmacro CABINET
Table 13-6 Equipment required for dual cabinet, 12 CTU configuration

duplexed hybrid and air combining
Quantity Unit
6 Antennas
2 Horizonmacro BTS cabinets
12 CTU
2 SURF
6 DCF

13–16 68P02900W21-K 30th Jun 02
GMR-01
[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and air

combining
Figure 13-14 and Figure 13-15 show a four cabinet, 24 CTU configuration with duplexed
dual-stage hybrid and air combining. Table 13-7 provides a summary of the equipment
required for this configuration.
Figure 13-14 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1)
TO
SURF EXT A EXTENDER 1
Tx/Rx Tx/Rx Tx/Rx Horizonmacro
ANTENNA ANTENNA ANTENNA SURF B0 CABINET
(SECTOR 3) (SECTOR 3) (SECTOR 1)
A B A
B2 1 0 A 2 1 0 B A B2 1 0 A 2 1 0 B A
SURF SURF
HCU HCU HCU

DDF DDF DDF
EXTENDER 3 Horizonmacro EXTENDER 2 Horizonmacro

CABINET CABINET

30th Jun 02 68P02900W21-K 13–17
GMR-01
Figure 13-15 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2)
TO EXTENDER 2 SURF A0
Horizonmacro CABINET SURF EXT B
Tx/Rx Tx/Rx Tx/Rx

ANTENNA ANTENNA ANTENNA
B A B
B2 1 0 A 2 1 0 B A B2 1 0 A 2 1 0 B A
SURF SURF
HCU HCU HCU

DDF DDF DDF
EXTENDER 1 Horizonmacro CABINET MASTER Horizonmacro CABINET
Table 13-7 Equipment required for four cabinet, 24 CTU configuration,

Quantity Unit
6 Antennas
4 Horizonmacro cabinets
24 CTU
Transmitter
6 Hybrid combiner unit (HCU)
Receiver
4 SURF
6 DDF

13–18 68P02900W21-K 30th Jun 02
GMR-01
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 provide
a two or three BTS site.
NOTE Expansion of a single Horizoncompact2 site is only supported

from GSR5 software onwards.
The Horizoncompact2 BTS system supports the following site configurations using
GSM900 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 DCS1800
Horizoncompact2 BTSs are used:
S 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800
carriers.
S 3 BTS cell: Two BTSs with a total of four GSM900 carriers and one BTS with two
DCS1800 carriers
or
Two BTSs with a total of four DCS1800 carriers and one BTS with two GSM900
carriers.

30th Jun 02 68P02900W21-K 13–19
GMR-01
[GSM900/DCS1800] Horizoncompact2 single BTS system

Figure 13-16 shows the configuration for a single Horizoncompact2 BTS system.
Figure 13-16 Horizoncompact2 single BTS system
Tx2 Tx1/Rx
ANTENNA ANTENNA
ANT ANT
FILTER DUPLEXER
Tx Rx Tx
AMP AMP
HORIZONCOMPACT2 BOOSTER
Rx
Tx2 Tx1
ISOLATOR ISOLATOR
MODULE MODULE
Rx IN Tx2 OUT Tx1 OUT
DINO / RHINO DTRX
HORIZONCOMPACT2 BTS

13–20 68P02900W21-K 30th Jun 02
GMR-01
[GSM900/DCS1800] Horizoncompact2 two BTS system

Figure 13-17 shows the configuration for a two Horizoncompact2 BTS system using fibre
optic cables. An HDSL option is available which allows the BTSs to be connected
through HDSL links. Refer to Figure 13-16 for internal connections within the BTS and
booster.
Figure 13-17 Horizoncompact2 two BTS system
Tx2 Tx1/Rx Tx2 Tx1/Rx

HORIZONCOMPACT2 BOOSTER HORIZONCOMPACT2 BOOSTER
DINO / RHINO DINO / RHINO
HORIZONCOMPACT2 MASTER BTS HORIZONCOMPACT2 SLAVE BTS
FIBRE OPTIC LINK

30th Jun 02 68P02900W21-K 13–21
GMR-01
[GSM900/DCS1800] Horizoncompact2 three BTS system

Figure 13-18 shows the configuration for a three Horizoncompact2 BTS system using
fibre optic cables. An HDSL option is available which allows the BTSs to be connected
through HDSL links. Refer to Figure 13-16 for internal connections within the BTS and
booster.
Figure 13-18 Horizoncompact2 three BTS system
Tx2 Tx1/Rx Tx2 Tx1/Rx Tx2 Tx1/Rx

ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
HORIZONCOMPACT2 BOOSTER HORIZONCOMPACT2 BOOSTER
HORIZONCOMPACT2 MASTER BTS HORIZONCOMPACT2 SLAVE BTS
FIBRE OPTIC LINK
HORIZONCOMPACT2 BOOSTER
FIBRE OPTIC LINK

DINO / RHINO
HORIZONCOMPACT2 SLAVE BTS

13–22 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Microcell RF configurations
Microcell RF configurations
Horizonmicro2
The Horizonmicro2 BTS is similar to the Horizoncompact2, but does not include (or
support) a booster enclosure. One or two additional Horizonmicro2 BTSs may be added
as slaves to provide a two or three BTS site.
NOTE Expansion of a single Horizonmicro2 site is only supported from

GSR5 software onwards.
The Horizonmicro2 BTS supports the following site configurations using GSM900 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 DCS1800
Horizonmicro2 BTSs are used:
S 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800
carriers.
S 3 BTS cell: Two BTSs with a total of four GSM900 carriers and one BTS with two
DCS1800 carriers
or
Two BTSs with a total of four DCS1800 carriers and one BTS with two GSM900
carriers.

30th Jun 02 68P02900W21-K 13–23
GMR-01
Microcell RF configurations GSM-001-103
[GSM900/DCS1800] Horizonmicro2 single BTS system

Figure 13-19 shows the configuration for a single Horizonmicro2 BTS system.
Figure 13-19 Horizonmicro2 single BTS system
Tx1/Tx2/Rx
ANTENNA
ANT
COMBINER/
DUPLEXER ISOLATOR
Rx Tx MODULE
Tx Tx Tx
Rx IN Tx2 OUT Tx1 OUT
DINO / RHINO DTRX
HORIZONMICRO2 BTS
[GSM900/DCS1800] Horizonmicro2 two BTS system

Figure 13-20 shows the configuration for a two Horizonmicro2 BTS system using fibre
through HDSL links. Refer to Figure 13-19 for internal connections within the BTS.
Figure 13-20 Horizonmicro2 two BTS system
Tx1/Tx2/Rx Tx1/Tx2/Rx
ANTENNA ANTENNA
HORIZONMICRO2 MASTER BTS HORIZONMICRO2 SLAVE BTS
FIBRE OPTIC LINK

13–24 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Microcell RF configurations
[GSM900/DCS1800] Horizonmicro2 three BTS system

Figure 13-21 shows the configuration for a three Horizonmicro2 BTS system using fibre
through HDSL links. Refer to Figure 13-19 for internal connections within the BTS.
Figure 13-21 Horizonmicro2 three BTS system
Tx1/Tx2/Rx Tx1/Tx2/Rx Tx1/Tx2/Rx

HORIZONMICRO2 MASTER BTS HORIZONMICRO2 SLAVE BTS
FIBRE OPTIC LINK
FIBRE OPTIC LINK
DINO / RHINO
HORIZONMICRO2 SLAVE BTS

30th Jun 02 68P02900W21-K 13–25
GMR-01
Connecting Horizon BTS cabinets to M-Cell6 BTS cabinets GSM-001-103
Connecting Horizon BTS cabinets to M-Cell6 BTS cabinets
Connection overview
This section provides examples of how previous generation BTS equipment (M-Cell6)
can be connected to the current generation BTS equipment (Horizon).
NOTE M-Cell2 BTS cabinets cannot be connected to Horizon BTS
cabinets.
900 MHz BTSs

Figure 13-22 shows how a 900 MHz Horizonmacro BTS cabinet may be connected to a
900 MHz M-Cell6 BTS cabinet to create a 3 sector (4/4/4) configuration.
Figure 13-22 900 MHz Horizonmacro and 900 MHz M-Cell6 interconnections
Tx/Rx ANTENNA Tx/Rx ANTENNA Tx/Rx ANTENNA
DUPLEXER
DUPLEXER
DUPLEXER
0B B 2 1 0 0A A 2 1 0 B A
900 SURF DLNB DLNB
IADU
6 6
DCF DCF DCF

CBF2 CBF1 CBF0
C C C C C C T T T T T T
T T T T T T C C C C C C
Horizonmacro CABINET M-Cell6 BTS CABINET

13–26 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Connecting Horizon BTS cabinets to M-Cell6 BTS cabinets
1800 MHz BTSs

Figure 13-23 shows how an 1800 MHz Horizonmacro BTS cabinet may be connected to
an 1800 MHz M-Cell6 BTS cabinet to create a 3 sector (4/4/4) configuration.
NOTE –13 dB attenuators are required between the SURF and LNA
connections in 1800 MHz configurations. (Attenuators are not
required for 900 MHz configurations.)
Figure 13-23 1800 MHz Horizonmacro and 1800 MHz M-Cell6 interconnections
Tx/Rx Tx/Rx Tx/Rx

ATTENUATOR
ATTENUATOR
DUPLEXER
–13 dB
–13 dB
DUPLEXER
DUPLEXER
B2 1 0 A 2 1 0 B A LNA LNA
1800 SURF
6 6
DCF DCF DCF CBF2 CBF1 CBF0
C C C C C C T T T T T T
T T T T T T C C C C C C
Horizonmacro CABINET M-Cell6 BTS CABINET

30th Jun 02 68P02900W21-K 13–27
GMR-01
Connecting Horizon BTS cabinets to M-Cell6 BTS cabinets GSM-001-103

13–28 68P02900W21-K 30th Jun 02
GMR-01
Chapter 14
M-Cell BTS configurations

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
M-Cell equipment covered

This chapter is included for reference purposes. It provides diagrams of the logical
interconnections of the components in previous generation M-Cell BTS equipment and
typical RF configurations.
Examples of how M-Cell equipment may be connected to current generation Horizon
equipment 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 M-Cell6 RF configurations.
S M-Cell2 RF configurations.

30th Jun 02 68P02900W21-K 14–1
GMR-01
Standard M-Cell configurations GSM-001-103
Standard M-Cell configurations
Introduction to standard M-Cell configurations

The examples in this section are shown with individual antennas for transmit and receive
signals. 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 typical
configuration using that specific equipment. Rather, they are meant to highlight the
configurations that, within the constraints of the BSS architecture, are feasible when the
macrocell hardware is deployed in an M-Cell BTS. The diagrams also show possible
cabinet boundaries. Cabinet designs, however, allow for a number of different
arrangements of the same configuration.
NOTE For typical BSS configurations, refer to Figure 13-1 and

Figure 13-2 in Chapter 12.
Rather than showing redundancy for all M-Cell BTS configurations, the control
redundancy is depicted only for one M-Cell6, and one M-Cell2 cabinet diagram (see
Figure 14-5 and Figure 14-6).

14–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Picocell (M-Cellaccess) configurations
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 14-1.
Figure 14-1 Single BTS site with 6 PCUs using fibre optic links
TO/FROM TRANSMIT/RECEIVE ANTENNA
P P P P P P ONE RF CARRIER
CONSISTS OF ONE
C C C C C C DRIM, DRIX AND PCU
U U U U U U
1 2 3 4 5 6
PCC CABINET
BSU SHELF FIBRE OPTIC LINKS
DRIX DRIX DRIX DRIX DRIX DRIX DUAL SERIAL BUS

1 2 3 4 5 6
BTC DRIM DRIM DRIM DRIM DRIM DRIM

5 6 DUAL MCAP BUS
1 2 3 4

A
BTC GCLK TSW MSI GPROC GPROC GPROC

A
DUAL IEEE
802.5 LAN LANX
LINKS FROM/TO BSC A
BSC

30th Jun 02 68P02900W21-K 14–3
GMR-01
Picocell (M-Cellaccess) configurations GSM-001-103
HDSL links
The digital module and RF configuration for a PCC cabinet with six PCUs (RF carriers)
and HDSL links is shown in Figure 14-2.
Figure 14-2 Single BTS site with 6 PCUs using HDSL links
TO/FROM TRANSMIT/RECEIVE ANTENNA
P P P P P P ONE RF CARRIER
CONSISTS OF ONE
C C C C C C DRIM, HRIX AND PCU
U U U U U U
1 2 3 4 5 6
PCC CABINET
HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120
TOP OF CABINET
LOWER BSU SHELF
HRIX HRIX HRIX HRIX HRIX HRIX DUAL SERIAL BUS

1 2 3 4 5 6

5 6 DUAL MCAP BUS
1 2 3 4

A

A
DUAL IEEE
802.5 LAN LANX
LINKS FROM/TO BSC A
BSC

14–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Picocell (M-Cellaccess) configurations
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 14-3.
Figure 14-3 Two BTS site with 12 PCUs using optical fibre links
PCU 1 to 6 PCU 7 to 12
FIBRE OPTIC LINKS FIBRE OPTIC LINKS
PCC CABINET

1 2 3 4 5 6

5 6 DUAL MCAP BUS
1 2 3 4

A

A
DUAL IEEE
802.5 LAN LANX
UPPER BSU SHELF LINKS FROM/TO BSC A

1 2 3 4 5 6

5 6 DUAL MCAP BUS
1 2 3 4

A

A
DUAL IEEE
802.5 LAN LANX
LOWER BSU SHELF LINKS FROM/TO BSC A
BSC

30th Jun 02 68P02900W21-K 14–5
GMR-01
Picocell (M-Cellaccess) configurations GSM-001-103
HDSL links
The digital module and RF configuration for a PCC cabinet with 12 PCUs (RF carriers)
and HDSL links is shown in Figure 14-4.
Figure 14-4 Two BTS site with 12 PCUs using HDSL links
PCU 1/2 PCU 3/4 PCU 5/6 PCU 7/8 PCU 9/10 PCU 11/12
HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120 HIM-75/HIM-120
TOP OF
CABINET

1 2 3 4 5 6

5 6 DUAL MCAP BUS
1 2 3 4

A

A
DUAL IEEE
802.5 LAN LANX
UPPER BSU SHELF LINKS FROM/TO BSC A
PCC CABINET

1 2 3 4 5 6

5 6 DUAL MCAP BUS
1 2 3 4

A

A
DUAL IEEE
802.5 LAN LANX
LOWER BSU SHELF LINKS FROM/TO BSC A
BSC

14–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Single cabinet BTS configurations
Single cabinet BTS configurations
Single cabinet M-Cell6 BTS

The configuration shown in Figure 14-5 is an example of a single cabinet M-Cell6 BTS.
Figure 14-5 Single cabinet M-Cell6 BTS
mBCU mBCU
N N
I I
U U
MCU MCU
12 12
F F
O O
X X (FOR
REDUNDANCY)
12 12
2 2 2 2 2 2
T T T T T
T
C C C C C
C U U U
U U U
2 2 2 2 2 2
M-CELL6 BTS CABINET

30th Jun 02 68P02900W21-K 14–7
GMR-01
Single cabinet BTS configurations GSM-001-103
Single cabinet M-Cell2 BTS

The configuration shown in Figure 14-6 is an example of a single cabinet M-Cell2 BTS.
This configuration supports two carriers.
Figure 14-6 Single cabinet M-Cell2 BTS
mBCU mBCU
N N
I I
U U
MCU MCU
(FOR
REDUNDANCY)
2 2
T T
C C
U U
2 2
M-CELL2 CABINET

14–8 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Two cabinet BTS configuration
Two cabinet BTS configuration
Two cabinet M-Cell6 BTS

The configuration shown in Figure 14-7 is an example of a two cabinet M-Cell6 BTS. This
configuration supports 12 carriers. The MCUs interface to the TCUs through the FOX or
the FMUX/FOX.
Figure 14-7 Two cabinet M-Cell6 BTS
M-CELL6
N mBCU BTS CABINET
I
U
F
12 M 2
MCU
U
X
12
F
O
X
12
2 2 2 2 2 2
T T T T T T
C C C C C C
U U U U U U
12
M-CELL6 mBCU
BTS CABINET 2 2 2 2 2 2
F
F
T T T M
T T T O
C U
C C C C C X
U U X
U U U U

30th Jun 02 68P02900W21-K 14–9
GMR-01
Three cabinet BTS configuration GSM-001-103
Three cabinet BTS configuration
Three cabinet M-Cell2 BTS

The configuration shown in Figure 14-8 is an example of a three cabinet M-Cell2 BTS.
Figure 14-8 Three cabinet M-Cell2 BTS
M-CELL2 CABINET
N mBCU
I
U
12 F 12
MCU O
X 2 2
T T
C C 4 4
U U
M-CELL2 CABINET
2 2
T T
C C
U U
M-CELL2 CABINET
2 2
T T
C C
U U

14–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Four cabinet BTS configuration
Four cabinet BTS configuration
Four cabinet M-Cell6 BTS

The configuration shown in Figure 14-9 is an example of a four cabinet M-Cell6 BTS.
This configuration supports 24 carriers. The MCUs interface to the TCUs through the
FOX or the FMUX/FOX.
Figure 14-9 Four cabinet M-Cell6 BTS
M-CELL6
N mBCU BTS CABINET
I F
U 12 M 2
U
X
MCU F
12 M 2
U
X
12
F
12 M 2
F U
O X
X
12
2 2 2 2 2 2
T T T T T T
C C C C C C
U U U U U U
12
M-CELL6 mBCU
F
F
T T T M
T T T O
C U
C C C C C X
U U X
U U U U
M-CELL6 12
mBCU
F
F
T T T T T T M
O
C C C C C C U
X
U U U U U U X
M-CELL6 12
mBCU
F
F
T T T T T M
T O
C C C C C U
C X
U U U U U X
U

30th Jun 02 68P02900W21-K 14–11
GMR-01
M-Cell RF configurations GSM-001-103
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 shown
in Figure 14-10 to Figure 14-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 text
accompanying the configuration diagram.
S In an M-Cell6 side cabinet, a maximum of three high power duplexers can be
accommodated.

14–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 M-Cell RF configurations
M-Cell6 cabinets
NOTE DIversity is assumed in all figures, unless stated otherwise.
[GSM900] 3 carrier omni, with hybrid combining and diversity

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in
Figure 14-10. Table 14-1 provides a summary of the equipment required for this
configuration.
Figure 14-10 3 carrier omni, hybrid combining

Tx ANTENNA Rx ANTENNAS
A B
DLNB
RF INPUT IADU
RF LOAD
3-INPUT
Non- CBF
HCOMB 4 4
T T T
C C C
U U U
A A A
B B B
M-Cell6 BTS CABINET
combining 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

30th Jun 02 68P02900W21-K 14–13
GMR-01
[GSM900] 3 carrier omni, with hybrid combining, diversity, and

medium power duplexer
configuration.
Figure 14-11 3 carrier omni, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
DLNB
RF INPUT
RF LOAD
IADU
3-INPUT
Non- CBF
HCOMB 4 4
T T T
C C C
U U U
A A A
B B B
M-Cell6 BTS CABINET
combining, diversity and medium power duplexer
Quantity Unit
2 Antennas
3 TCU
Transmitter
1 3-input CBF
Receiver
1 DLNB
1 Medium power duplexer

14–14 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 4 carrier omni, with hybrid combining and diversity

configuration.
Figure 14-12 4 carrier omni, hybrid combining

A B
DLNB
RF INPUT
RF LOAD IADU
3-INPUT
HCOMB CBF
4 4
T T T T
C C C C
U U U U
A A A A
B B B B
M-Cell6 BTS CABINET
Quantity Unit
3 Antennas
4 TCU
Transmitter
1 3-input CBF
1 Hybrid combining block (HCOMB)
Receiver
1 DLNB

30th Jun 02 68P02900W21-K 14–15
GMR-01
[GSM900] 4 carrier omni, with hybrid combining, diversity, and

medium power duplexer
A single cabinet, four TCU configuration with hybrid combining, diversity, and medium
power duplexer, is shown in Figure 14-13. Table 14-4 provides a summary of the
equipment required for this configuration.
Figure 14-13 4 carrier omni, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
RF INPUT
RF LOAD
DLNB
3-INPUT
HCOMB IADU
CBF
4 4
T T T T
C C C C
U U U U
A A A A
B B B B
M-Cell6 BTS CABINET
Quantity Unit
2 Antennas
4 TCU
Transmitter
1 3-input CBF
1 Hybrid combining block (HCOMB)
Receiver
1 DLNB

14–16 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 6 carrier omni, with cavity combining and diversity

A single cabinet, six TCU configuration with cavity combining and diversity, is shown in
configuration.
Figure 14-14 6 carrier omni, cavity combining

A B
DLNB
CCB CCB
(EXTENSION) (OUTPUT)
IADU
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
3 Antennas
6 TCU
Transmitter
1 CCB (Output)
1 CCB (Extension)
Receiver
1 DLNB

30th Jun 02 68P02900W21-K 14–17
GMR-01
[GSM900] 6 carrier omni, with cavity combining, diversity, and high

power duplexer
A single cabinet, six TCU configuration with cavity combining, diversity, and high power
duplexer, is shown in Figure 14-15. Table 14-6 provides a summary of the equipment
An external equipment rack/cabinet is required for a high power duplexer in an indoor
installation.
Figure 14-15 6 carrier omni, cavity combining, high power duplexer

Rx Tx/Rx
ANTENNA ANTENNA
B A
DLNB
ANT
IADU
Rx
CCB CCB
Tx
6 6
HIGH POWER
DUPLEXER
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET M-Cell6 SIDE CABINET
combining, 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

14–18 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 8 carrier omni, with combining and diversity

A dual cabinet, eight TCU configuration with combining and diversity, is shown in
configuration.
Figure 14-16 8 carrier omni, combining
Tx Tx/Rx Rx
A B
DUPLEXER
Rx EXT
BLOCK DLNB
IADU IADU
CBF
CCB CCB
2 2
6 6
T T T T T T T T
C C C C C C C C
U U U U U U U U
A A A A A A A A
B B B B B B B B
EXTENDER M-Cell6 BTS CABINET MASTER M-Cell6 BTS CABINET
Quantity Unit
3 Antennas
8 TCU
Transmitter
1 CBF
1 CCB (Output)
1 CCB (Extension)
Receiver
1 DLNB
1 Rx extension block

30th Jun 02 68P02900W21-K 14–19
GMR-01
[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in
configuration.
Figure 14-17 2 sector (3/3), hybrid combining
Tx Tx Rx Rx
A B A B
DLNB DLNB
RF INPUT RF INPUT
RF LOAD RF LOAD
IADU
3-INPUT 3-INPUT
CBF CBF
Non-
HCOMB
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
6 Antennas
6 TCU
Transmitter
2 3-input CBF
Receiver
2 DLNB

14–20 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 2 sector (3/3), with hybrid combining, diversity, and

medium power duplexers
A single cabinet, six TCU configuration with hybrid combining, diversity, and medium
power duplexers, is shown in Figure 14-18. Table 14-9 provides a summary of the
Figure 14-18 2 sector (3/3), hybrid combining, medium power duplexers

Tx/Rx Tx/Rx Rx Rx
A A B B
DUPLEXER
DUPLEXER
RF INPUT RF INPUT DLNB DLNB

RF LOAD RF LOAD
IADU
3-INPUT 3-INPUT
CBF CBF
Non-
HCOMB
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
4 Antennas
6 TCU
Transmitter
2 3-input CBF
Receiver
2 DLNB

30th Jun 02 68P02900W21-K 14–21
GMR-01
[GSM900] 3 sector (2/2/2), with combining and diversity

A single cabinet, six TCU configuration with combining and diversity, is shown in
configuration.
Figure 14-19 3 sector (2/2/2), combining
Tx Tx Tx Rx Rx Rx
A B A B A B
DLNB DLNB DLNB
IADU
CBF CBF CBF
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
9 Antennas
6 TCU
Transmitter
3 CBF
Receiver
3 DLNB

14–22 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 3 sector (2/2/2), with cavity combining, diversity, and

A single cabinet, six TCU configuration with cavity combining, diversity, and medium
Figure 14-20 3 sector (2/2/2), combining, medium power duplexers

A A A B B B
DUPLEXER
DUPLEXER
DUPLEXER
DLNB DLNB DLNB
IADU
CBF CBF CBF
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
combining, diversity and medium power duplexers
Quantity Unit
6 Antennas
6 TCU
Transmitter
3 CBF
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–23
GMR-01
[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium

power duplexers (3 antenna per sector)
A dual cabinet, 12 TCU configuration with air combining, diversity, and medium power
duplexers, is shown in Figure 14-21. Table 14-12 provides a summary of the equipment
Figure 14-21 3 sector (4/4/4), air combining, medium power duplexers
Rx Tx/Rx Tx Tx/Rx Tx Tx/Rx Tx Rx Rx
ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
(SECTOR 2) (SECTOR 3) (SECTOR 3) (SECTOR 2) (SECTOR 2) (SECTOR 1) (SECTOR 1) (SECTOR 2) (SECTOR 1)
DUPLEXER
DUPLEXER
DUPLEXER
DLNB Rx EXT DLNB DLNB
BLOCK
IADU IADU
CBF2 CBF1 CBF0 CBF2 CBF1 CBF0
6 6 6 6
Table 14-12 Equipment required for dual cabinet, 12 TCU configuration with air
combining, diversity and medium power duplexers (3 antenna per sector)
Quantity Unit
9 Antennas
12 TCU
Transmitter
6 CBF
Receiver
3 DLNB

14–24 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium

power duplexers (2 antenna per sector)
A multiple cabinet, 12 TCU configuration with air combining, diversity, and medium power
Figure 14-22 3 sector (4/4/4), air combining, medium power duplexers

Tx/Rx ANTENNA Tx/Rx ANTENNA
(SECTOR 3) Tx/Rx ANTENNA (SECTOR 2) (SECTOR 1)
DUPLEXER
DUPLEXER
DUPLEXER
DUPLEXER
DUPLEXER
DUPLEXER
DLNB Rx EXT
DLNB DLNB
BLOCK
IADU IADU
CBF2 CBF1 CBF0 CBF2 CBF1 CBF0
6 6 6 6
Table 14-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

30th Jun 02 68P02900W21-K 14–25
GMR-01
[GSM900] 3 sector (4/4/4), with cavity combining and diversity

A multiple cabinet, 12 TCU configuration with cavity combining and diversity, is shown in
configuration.
Figure 14-23 3 sector (4/4/4), cavity combining
(SECTOR 1) (SECTOR 1)
A B
DLNB
IADU
CCB CCB
4 4
T T T T
C C C C
U U U U
A A A A
B B B B
MASTER M-Cell6 CABINET
Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.
Table 14-14 Equipment required for multiple cabinet, 12 TCU configuration with hybrid
Quantity Unit
6 Antennas
12 TCU
Transmitter
3 CCB (output)
3 CCB (extension)
Receiver
3 DLNB

14–26 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining and

diversity
A dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining and diversity, is
shown in Figure 14-24. Table 14-15 provides a summary of the equipment required for
this configuration.
Figure 14-24 3 sector (4/4/4), 3-input CBF, hybrid combining
Rx Tx Tx Tx Rx Rx
(SECTOR 3) (SECTOR 3) RF INPUT (SECTOR 2) (SECTOR 1) (SECTOR 2) (SECTOR 1)
RF LOAD

BLOCK
IADU IADU
6 6
RF INPUT RF INPUT
RF LOAD RF LOAD
6 6
3-INPUT 3-INPUT 3-INPUT

HCOMB CBF HCOMB CBF HCOMB CBF
Table 14-15 Equipment required for dual cabinet, 12 TCU configuration with 3-input
CBF, hybrid combining and diversity
Quantity Unit
9 Antennas
12 TCU
Transmitter
3 3-input CBF
3 Hybrid combiner module (HCOMB)
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–27
GMR-01
[GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity,

and medium power duplexers
A multiple cabinet, 12 TCU configuration with 3-input CBF, air combining, diversity, and
medium power duplexers, is shown in Figure 14-25. Table 14-16 provides a summary of
the equipment required for this configuration.
Rx Tx/Rx Tx/Rx & Rx Tx/Rx Rx
ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
(SECTOR 3) (SECTOR 3) RF INPUT (SECTOR 2) (SECTOR 1) (SECTOR 1)
RF LOAD
DUPLEXER
DUPLEXER
DUPLEXER
BLOCK
IADU IADU
RF INPUT RF INPUT
6 6
6 6 RF LOAD RF LOAD
HCOMB 3-INPUT 3-INPUT 3-INPUT

HCOMB HCOMB
CBF CBF CBF
3-input CBF, air combining, diversity and medium power duplexers
Quantity Unit
6 Antennas
12 TCU
Transmitter
3 3-input CBF
Receiver
3 DLNB

14–28 68P02900W21-K 30th Jun 02
GMR-01

and medium power duplexers (3 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, and
Tx/Rx Tx Rx
DUPLEXER
RF INPUT
DLNB
RF LOAD
IADU
3-INPUT 3-INPUT
CBF CBF
Non-
HCOMB
6 6
T T T T T
C C C C C
U U U U U
A A A A A
B B B B B
MASTER M-Cell6 BTS CABINET
Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master

cabinet for sectors 2 and 3.
CBF, air combining, diversity and medium power duplexers (3 antennas/sector)
Quantity Unit
9 Antennas
15 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–29
GMR-01
[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity,

A three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, and
Tx/Rx Tx/Rx
ANTENNA ANTENNA
DUPLEXER
DUPLEXER
RF INPUT
RF LOAD DLNB
3-INPUT 3-INPUT IADU

CBF CBF
Non-
HCOMB
6 6
T T T T T
C C C C C
U U U U U
A A A A A
B B B B B

CBF, combining, diversity and medium power duplexers (2 antennas/sector)
Quantity Unit
6 Antennas
15 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

14–30 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 3 sector (6/6/6), with cavity combining, diversity, and high

power duplexers
A multiple cabinet, 18 TCU configuration with cavity combining, diversity, and high power
An external equipment rack/cabinet is required for a high–power duplexer in an indoor
installation.
Figure 14-28 3 sector (6/6/6), cavity combining, high power duplexers

Rx Tx/Rx
ANTENNA ANTENNA
B A
DLNB
ANT
IADU
Rx
CCB CCB
Tx
6 6
HIGH POWER
DUPLEXER
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
MASTER M-Cell6 BTS CABINET M-Cell6 SIDE CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master cabinet for sectors 2 and 3.
Each extender cabinet terminates in a high power duplexer in the side cabinet.
Table 14-19 Equipment required for 3 RF cabinets, 18 TCU configuration with

cavity combining, diversity and high power duplexers
Quantity Unit
6 Antennas
18 TCU
Transmitter
3 CCB (output)
3 CCB (extension)
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–31
GMR-01

A three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, and
Tx/Rx Tx Rx
DUPLEXER
RF INPUT RF INPUT DLNB
RF LOAD RF LOAD
IADU
3-INPUT 3-INPUT
CBF CBF
Non-
HCOMB
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B

Quantity Unit
9 Antennas
18 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

14–32 68P02900W21-K 30th Jun 02
GMR-01

A three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, and
Tx/Rx Tx/Rx
ANTENNA ANTENNA
DUPLEXER
DUPLEXER
RF INPUT RF INPUT
RF LOAD RF LOAD DLNB
IADU
3-INPUT 3-INPUT
CBF CBF
Non-
HCOMB
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B

Quantity Unit
6 Antennas
18 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–33
GMR-01
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and

A four cabinet, 24 TCU configuration with cavity combining, diversity and medium power
duplexers, is shown in Figure 14-31/ Figure 14-32. Table 14-22 provides a summary of
Figure 14-31 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1)
Tx/Rx Tx/Rx Tx/Rx

DLNB 0 IN EXTENDER 2 M-Cell6 BTS CABINET

IADU IN EXTENDER 2 M-Cell6 BTS CABINET

DUPLEXER 2
DUPLEXER 1
DUPLEXER 0
Rx REV Rx REV Rx REV

BLOCK 2 BLOCK 1 BLOCK 0
IADU
CBF 2 CBF 1 CBF 0
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B

14–34 68P02900W21-K 30th Jun 02
GMR-01
Figure 14-32 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)
Rx Tx
ANTENNA ANTENNA
DUPLEXER 2
DUPLEXER 1
TO
MASTER DUPLEXER 0
M-Cell6
BTS CABINET Rx REV BLOCK 2
Rx REV BLOCK 1
Rx REV BLOCK 0
DLNB
IADU
CCB CCB
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
EXTENDER 1 M-Cell6 BTS CABINET

Extender 2 and extender 3 M-Cell6 cabinets configured similar to
the extender 1 cabinet for sectors 2 and 3.
Quantity Unit
9 Antennas
24 TCU
Transmitter
3 CCB (output)
3 CCB (extension)
3 CBF
Receiver
3 DLNB
3 Rx extender block

30th Jun 02 68P02900W21-K 14–35
GMR-01
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and both

high and medium power duplexers
A multiple cabinet, 24 TCU configuration with cavity combining, diversity and both high
and medium power duplexers, is shown in Figure 14-33/ Figure 14-34. Table 14-23
provides a summary of the equipment required for this configuration.
An external equipment rack/cabinet is required for a high power duplexer in an indoor
installation.
(Part 1)
Tx/Rx Tx/Rx Tx/Rx



DUPLEXER 2
DUPLEXER 1
DUPLEXER 0
Rx REV Rx REV Rx REV

BLOCK 2 BLOCK 1 BLOCK 0
IADU
CBF 2 CBF 1 CBF 0
6 6
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B

14–36 68P02900W21-K 30th Jun 02
GMR-01
(Part 2)
DUPLEXER 2
TO Tx/Rx Tx/Rx Tx/Rx
DUPLEXER 1
MASTER ANTENNA ANTENNA ANTENNA
M-Cell6 DUPLEXER 0 (SECTOR 3) (SECTOR 2) (SECTOR 1)
BTS CABINET Rx REV BLOCK 2
Rx REV BLOCK 1 A A A
Rx REV BLOCK 0


DLNB
ANT
IADU
CCB CCB
(EXTENSION) (OUTPUT) Rx
ANT
6 6 Tx
T T T T T T Rx
ANT
C C C C C C
U U U U U U Tx
A A A A A A Rx
B B B B B B
HIGH POWER Tx
DUPLEXERS
EXTENDER 1 M-Cell6 BTS CABINET M-Cell6 SIDE CABINET
Extender 2 and extender 3 M-Cell6 cabinets configured similar to the extender 1 cabinet for sectors 2 and 3.
The master, extender 1 and extender 2 cabinets terminate in a high power duplexer in the side cabinet.
combining, 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

30th Jun 02 68P02900W21-K 14–37
GMR-01

A four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, and
medium power duplexers, is shown in Figure 14-35/ Figure 14-36. Table 14-24 provides a
summary of the equipment required for this configuration.
(Part 1)
TO
EXTENDER 1
IADU M-Cell6
BTS CABINET
Tx Tx/Rx Rx
ANTENNA Tx
(SECTOR 2)
RF INPUT
RF LOAD
DUPLEXER
Rx EXT
BLOCK Rx EXT
DLNB
BLOCK
IADU
IADU
6 6
6 6 RF INPUT RF INPUT
RF LOAD RF LOAD

EXTENDER 3 M-Cell6 BTS CABINET EXTENDER 2 M-Cell6 BTS CABINET

14–38 68P02900W21-K 30th Jun 02
GMR-01
(Part 2)
TO EXTENDER 2 Rx EXT BLOCK
M-Cell6 BTS CABINET
Rx Tx/Rx Tx Tx/Rx Rx
ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
(SECTOR 2) (SECTOR 2) (SECTOR 1) (SECTOR 1) (SECTOR 1)
RF INPUT
RF LOAD
DUPLEXER
DUPLEXER
DLNB Rx EXT DLNB
BLOCK
IADU IADU
RF INPUT RF INPUT
RF LOAD RF LOAD 6 6
6 6

EXTENDER 1 M-Cell6 BTS CABINET MASTER M-Cell6 BTS CABINET
Quantity Unit
9 Antennas
24 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–39
GMR-01

A four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and medium
power duplexers, is shown in Figure 14-37/ Figure 14-38. Table 14-25 provides a
summary of the equipment required for this configuration.
(Part 1)
Tx Tx/Rx TO
ANTENNA ANTENNA DUPLEXER EXTENDER 1
(SECTOR 3) (SECTOR 3) M-Cell6
IADU BTS CABINET
RF INPUT
RF LOAD
DUPLEXER
Rx EXT DUPLEXER
BLOCK Rx EXT
DLNB
BLOCK
IADU
IADU
6 6
6 6 RF INPUT RF INPUT
RF LOAD RF LOAD

EXTENDER 3 M-Cell6 BTS CABINET EXTENDER 2 M-Cell6 BTS CABINET

14–40 68P02900W21-K 30th Jun 02
GMR-01
(Part 2)
TO EXTENDER 2 DUPLEXER
M-Cell6 BTS CABINET Rx REV BLOCK 1
Tx/Rx Tx/Rx
ANTENNA ANTENNA
Tx/Rx (SECTOR 1) (SECTOR 1)
Tx/Rx
ANTENNA ANTENNA
(SECTOR 2) RF INPUT
(SECTOR 2)
RF LOAD
DUPLEXER
DUPLEXER
DUPLEXER
DUPLEXER
DLNB Rx EXT DLNB
BLOCK
IADU IADU
RF INPUT RF INPUT
6 6
6 6 RF LOAD RF LOAD

EXTENDER 1 M-Cell6 BTS CABINET MASTER M-Cell6 BTS CABINET
Quantity Unit
6 Antennas
24 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB

30th Jun 02 68P02900W21-K 14–41
GMR-01
[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in
configuration.
Figure 14-39 3 sector (2/2/2), hybrid combining
Tx Tx Tx Rx Rx Rx
A B A B A B
LNA LNA LNA
TxBPF TxBPF TxBPF
2 2 2 2 2
HYBRID HYBRID 2
HYBRID
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
9 Antennas
6 TCU
Transmitter
3 TxBPF
3 Hybrid combiner
Receiver
3 LNA

14–42 68P02900W21-K 30th Jun 02
GMR-01
[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and

A single cabinet, six TCU configuration with hybrid combining, diversity, and medium
Figure 14-40 3 sector (2/2/2), hybrid combining, medium power duplexers

DUPLEXER
DUPLEXER
DUPLEXER
LNA LNA LNA
HYBRID HYBRID HYBRID 2 2 2 2 2 2
T T T T T T
C C C C C C
U U U U U U
A A A A A A
B B B B B B
M-Cell6 BTS CABINET
Quantity Unit
6 Antennas
6 TCU
Transmitter
3 Hybrid combiner
Receiver
3 LNA

30th Jun 02 68P02900W21-K 14–43
GMR-01
M-Cell2 cabinets
NOTE DIversity is assumed in all figures, unless stated otherwise.
[GSM900] 2 carrier, single sector, with hybrid combining and

diversity
A single cabinet, two TCU configuration with hybrid combining and diversity, is shown in
configuration.
Figure 14-41 2 carrier, single sector, hybrid combining

Tx Rx
ANTENNA ANTENNAS
A B
DLNB
CBF 2 2
T T
C C
U U
A A
B B
M-Cell2 BTS CABINET
Quantity Unit
3 Antennas
2 TCU
Transmitter
1 CBF
Receiver
1 DLNB

14–44 68P02900W21-K 30th Jun 02
GMR-01
[GSM900] 2 carrier, single sector, with hybrid combining, diversity,

and medium power duplexer
A single cabinet, two TCU configuration with hybrid combining, diversity, and medium
power duplexer, is shown in Figure 14-42. Table 14-29 provides a summary of the
Figure 14-42 2 carrier, single sector, hybrid combining, medium power duplexer
Tx/Rx Rx
ANTENNA ANTENNA
A B
DUPLEXER
DLNB
CBF 2 2
T T
C C
U U
A A
B B
M-Cell2 BTS CABINET
Quantity Unit
2 Antennas
2 TCU
Transmitter
1 CBF
Receiver
1 DLNB

30th Jun 02 68P02900W21-K 14–45
GMR-01
[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 14-43.
Table 14-30 provides a summary of the equipment required for this configuration.
Figure 14-43 2 sectors (1 carrier per sector)
Tx Tx Rx Rx
ANTENNA ANTENNA ANTENNAS ANTENNAS
A B A B
DLNB DLNB
CBF CBF
T T
C C
U U
A A
B B
M-Cell2 BTS CABINET
diversity
Quantity Unit
6 Antennas
2 TCU
Transmitter
2 CBF
Receiver
2 DLNB

14–46 68P02900W21-K 30th Jun 02
GMR-01
[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU configuration with air combining and diversity, is shown in
configuration.
Figure 14-44 2 carrier, single sector, air combining
Tx Tx/Rx Rx
B A
DUPLEXER
LNA
TxBPF
2 2
T T
C C
U U
A A
B B
M-Cell2 BTS CABINET
Table 14-31 Equipment required for single cabinet, 2 TCU configuration with air
Quantity Unit
3 Antennas
2 TCU
Transmitter
1 TxBPF
Receiver
1 LNA

30th Jun 02 68P02900W21-K 14–47
GMR-01
[DCS1800] 2 sectors, with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 14-45.
Table 14-32 provides a summary of the equipment required for this configuration.
Figure 14-45 2 sectors
Tx Tx Rx Rx
ANTENNA ANTENNA ANTENNAS ANTENNAS
A B A B
LNA LNA
TxBPF TxBPF
T T
C C
U U
A A
B B
M-Cell2 BTS CABINET
Table 14-32 Equipment required for single cabinet, 2 TCU configuration with diversity
Quantity Unit
6 Antennas
2 TCU
Transmitter
2 TxBPF
Receiver
2 LNA

14–48 68P02900W21-K 30th Jun 02
GMR-01
Chapter 15
Previous generation BSC planning
steps and rules

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter (included for reference purposes only) provides the planning steps and
rules for the previous generation of BSC equipment. The planning steps and rules for the
pre 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 reference

purposes only.

S BSC planning overview.
– 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.

30th Jun 02 68P02900W21-K 15–1
GMR-01
BSC planning overview GSM-001-103
BSC planning overview
Introduction
To plan the equipage of a BSC certain information must be known. The major items
include:
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 the
maximum 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.

15–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BSC planning overview

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 the
section Determining the required BSS signalling link capacities in this
chapter.
2. Plan the number of RSL links between the BSC and BTS site(s), refer to the
section Determining the RSLs required in this chapter.
3. Plan the number of MTL links between the BSC and MSC, refer to the section
Determining 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 this
chapter.
interface (MSI, MSI-2) in this chapter.
switch (KSW) in this chapter.
8. Plan the number of BSU shelves, refer to the section BSU shelves in this chapter.
extender (KSWX) in this chapter.
10. Plan the number of GCLKs required, refer to the section Generic clock (GCLK) in
this 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) in
this chapter.
(PIX) in this chapter.
(BIB, T43) in this chapter.
15. Plan the power requirements, refer to the section Digital shelf power supply in
this chapter.
(BBBX) in this chapter.
17. Verify the planning process, refer to the section Verify the number of BSU
shelves and BSSC2 cabinets in this chapter.

30th Jun 02 68P02900W21-K 15–3
GMR-01
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC,
GPROC2) and the throughput capacities of its data links, determines the number of
supported traffic channels (TCHs). These capacities are limited by the ability of the
processors, and links to handle the signalling information associated with these TCHs.
link capacities and BSC processing capacities. This section describes:
S Traffic models.

15–4 68P02900W21-K 30th Jun 02
GMR-01
BSC signalling traffic model

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

30th Jun 02 68P02900W21-K 15–5
GMR-01
MSC
TRANSCODER

1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK
1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK*
A INTERFACE (TERRESTRIAL LINKS) 1 x 64 kbit/s CIRCUIT/ XBL
–C7 SIGNALLING LINKS 1 x 64 kbit/s CIRCUIT/4 TRUNKS
–X.25 CONTROL LINK*
1 x 64 kbit/s CIRCUIT/C7 SIGNALLING LINK
1 x 64 kbit/s CIRCUIT/X.25 SIGNALLING LINK*
1 x 64 kbit/s CIRCUIT/TRUNK
THE BSC TO MSC 64 kbit/s CIRCUITS ARE DETERMINED FROM THE # OF

TRUNKS REQUIRED TO CARRY THE SUMMATION OF AIR INTERFACE TRAFFIC
(IN ERLANGS, TYPICALLY USING 1% BLOCKING) FROM ALL BTSs
– PLUS –
THE # OF C7 SIGNALLING LINKS
– PLUS – (IF APPLICABLE*)
– PLUS –
THE # OF XBL LINKS
BSC
MOTOROLA BSC/BTS INTERFACE 1 x 64 kbit/s CIRCUIT/LAPD SIGNALLING LINK

NON-BLOCKING 2 x 64 kbit/s CIRCUITS/DRCU/SCU
THE # OF TCHs REQUIRED (USING TYPICALLY 2% BLOCKING) TO CARRY

SUBSCRIBER TRAFFIC
THE TCHs PLUS THE REQUIRED SIGNALLING TSs DIVIDED BY EIGHT
DETERMINES THE CARRIERS REQUIRED (ON A BTS/SECTOR BASIS)
BTS
AIR INTERFACE
–TCHs AND SIGNALLING TSs
–TYPICALLY 2% BLOCKING TRANSCODING MUST BE LOCATED AT THE
BSC, OR BETWEEN THE BSC AND MSC
AIR INTERFACE TCH = TRAFFIC CHANNEL

(TRAFFIC IN ERLANGS) TS = TIMESLOT
* X.25 MAY BE PASSED TO RXCDR
OR MSC SITE


15–6 68P02900W21-K 30th Jun 02
GMR-01

listed in Table 15-1 with their typical values.
Two methods for determining capacity are given. The first method is based on the typical
call parameters given in Table 15-1 and simplifies planning to lookup tables, or simple
formulae indicated in standard traffic model planning steps. When the call parameters
being planned for differ significantly from the standard traffic model given in Table 15-1 in
this case more complex formulae must be used as indicated in non-standard traffic
model 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), the
L=I

L = I + 0.2 * I

L = I + 0.5 * I

30th Jun 02 68P02900W21-K 15–7
GMR-01

To calculate link and processing capacity values, certain signalling message sequence
patterns and message sizes have been assumed for the various procedures included in
the signalling traffic model. New capacity values may have to be calculated if the actual
message patterns and message sizes differ significantly from those assumed. The
assumptions used for the capacity calculations in this manual are summarized below.
sizes (not including link protocol overhead) for each procedure are provided in
Table 15-3.
Table 15-3 Procedure capacities

Procedure MSC to BSC link
(see note below) 7 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 SMS

depend on the implementation of the SMS service centre. The
numbers given are estimates for a typical implementation. These
numbers may vary.
An additional assumption, which is made in determining the values listed in Table 15-3, is
that the procedures not included in the traffic model are considered to have negligible
effect.

15–8 68P02900W21-K 30th Jun 02
GMR-01
Link capacities
The level of link utilization is largely a matter of choice of the system designer. A design
that has more links running at a lower message rate can have the advantage of offering
better fault tolerance since the failure of any one link affects less signalling traffic.
Reconfiguration around the fault could be less disruptive. Such a design could offer
reduced queueing delays for signalling messages. A design that utilizes fewer links at a
higher message rate, reduces the number of 64 kbit/s circuits required for signalling, and
potentially reduces the number of resources (processors, data ports) required in the
MSC. It is recommended that the C7 links be designed to operate at no more than 20%
link utilization. If higher link utilizations are used, the controlling GPROCs (LCF–MTLs)
may become overloaded.
C7, the protocol used for the MSC to BSC links, allows for the signalling traffic from the
failed link to be redistributed among the remaining functioning links. A C7 link set officially
has at least two and at most 16 links. The failure of links, for any reason, cause the
signalling to be shared across the remaining members of the link set. Therefore, the
design must plan for reserve link and processing capacity to support a certain number of
failed signalling links.

30th Jun 02 68P02900W21-K 15–9
GMR-01
Determining the RSLs required GSM-001-103
Determining the RSLs required
Introduction
Each BTS site which is connected directly to the BSC, including the first site in a daisy
chain, must be considered individually. Once individual RSL requirements are calculated
the total number of LCFs can be determined for the BSC.
The following factors should be considered when planning the provision of RSL (LAPD
signalling) links from the BSC to BTS sites:
S With the Motorola BSC/BTS interface there is a need for an RSL link to every BTS
site. One link can support multiple collocated cells. As the system grows,
additional signalling links may be required. Refer to the section Determining the
required BSS signalling link capacities in this chapter to determine the number
of RSL links required.
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.

This number depends on the number of TCHs at the BTS. Table 15-4 gives the number
of RSLs required for a BTS to support the given number of TCHs. These numbers are
based on the typical call parameters given in the standard traffic model column of
Table 15-1. If the call parameters differ significantly from the standard traffic model, use
the formulae for the non-standard traffic model.

n = number of TCHs at the BTS Number of 64 kbit/s Number of 16 kbit/s
RSLs RSLs
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, but not both.

15–10 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the RSLs required

formula to determine the required number of 64 kbit/s RSLs (rounded up to the next
nearest integer).
(n * (95 ) 67 * S ) 35 * H ) 25 * L))
N BSC*BTS + ) 6*P
(1000 * U * T) (1000 * U)
formula to determine the required number of 16 kbit/s RSLs (rounded up to the next
nearest integer).
N BSC*BTS + ǒ(n * (95 ) 67(1000

* S ) 35 * H ) 25 * L))
* U * T)
) 6*P Ǔ*4
(1000 * U)
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).

Determine the number of E1 links required to connect to a BTS. Redundant links may be
added, if required.
[(nTCH + L16) / 4] + L64
N+
31
Where: N is: the minimum number of E1 links required (rounded up

to an integer).
nTCH the number of traffic channels at the BTS.
NOTE This formula includes both L16 and L64 to provide necessary

30th Jun 02 68P02900W21-K 15–11
GMR-01

Determine the number of T1 links required to connect to a BTS. Redundant links may be
added, if required.
[(nTCH + L16) / 4] + L64
N+
24
Where: N is: the minimum number of T1 links required (rounded up

to an integer).
nTCH the number of traffic channels at the BTS.
NOTE This formula includes both L16 and L64 to provide necessary

15–12 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Determining the RSLs required
Calculate the number of LCFs for RSL processing
LCFs for BSC to BTS links and Layer 3 call processing

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

For a GPROC2:
G L3 + ǒ440
n ) B ) CǓ*ǒ 1 Ǔ
15 35 2.5
For a GPROC:
G L3 + n ) B ) C
440 15 35
Where: GL3 is: the number of LCF GPROCs or LCF GPROC2s

required to support the layer 3 call processing.
n the number of TCH under the BSC.

30th Jun 02 68P02900W21-K 15–13
GMR-01

For a GPROC2:
G L3 + ǒn * (1 ) 0.7 * S ) 0.5(11.3
* H * (1 * 0.3 * i) ) 0.5 * L)
* T)
) (0.006 ) 0.02 * P) * B ) C Ǔ * ǒ 1 Ǔ
35 2.5
For a GPROC:
(n * (1 ) 0.7 * S ) 0.5 * H * (1 * 0.3 * i) ) 0.5 * L))
G L3 + ) (0.006 ) 0.02 * P) * B ) C
(11.3 * T) 35
Where: GL3 is: the number of LCF GPROCs or LCF GPROC2s

required 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.
Step 3
The number of LCFs required is the greater of GRSL and GL3.
Assigning BTSs to LCFs

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

processors will be needed to share the load.

15–14 68P02900W21-K 30th Jun 02
GMR-01
Introduction
MTLs carry signalling traffic between the MSC and BSC. The number of required MTLs
depends upon the BSS configuration size and traffic model. MTLs are carried on E1 or
T1 links between the MSC and BSC, which are also used for traffic.
The following factors should be considered when planning the links from the BSC to
MSC:
S Determine traffic requirements for the BSC. Traffic may be determined using either
of the following methods:
traffic per subscriber.
or
– Sum the traffic potential of each BTS under the BSC; determined by the
number of TCHs available, the number of TCHs required or the subscriber
potential.
S Determine the number of trunks to support the traffic requirements of the BSC
using Erlang B tables at the required blocking rate.

30th Jun 02 68P02900W21-K 15–15
GMR-01

The number of MSC to BSC signalling links (MTL) required depends on the desired link
utilization, the type and capacity of the GPROCs controlling the MTLs. C7 uses a 4 bit
number, the Signalling Link Selection (SLS) generated by the upper layer to load share
message traffic among the in service links of a link set. When the number of in service
links is not a power of 2, some links may experience a higher load than others.
call load. Table 15-5 gives the recommended minimum number of MSC to BSC signalling
links based on the typical call parameters given in Table 15-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
whichever is greater.
trunks).
the BSS. The offered call load at a cell is a function of the number TCHs and blocking.
Table 15-5 Number of MSC to BSC signalling links

N = the number of MSC to BSC Trunks Minimum number Recommended
or the offered load from the BTSs of MTLs number of MTLs
( hi h
(whichever is
i the
th greatest)
t t)
(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 model
shown in Table 15-1.

15–16 68P02900W21-K 30th Jun 02
GMR-01

1. Use the formula given below to determine the maximum number of Erlangs
supported by a C7 signalling link (nllink).
(1000 * U * T)
nl link +
((67 ) 47 * S ) 31 * H * (1 * 0.8 * i) ) 25 * L) ) 14 * P PC)
2. Use the formula given below to determine the maximum number of Erlangs
supported by a GPROC or GPROC2 (LCF–MTL) supporting a C7 signalling link
(nlLCF–MTL).
For a BSC with a mix of GPROC and GPROC2:
nl LCF*MTL + 3.6 * T
((1 ) 0.7 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.5 * L) ) P PC * (0.01 * B ) 0.05))
For a BSC with only GPROC2:

2.5 * (3.6 * T)
nl LCF*MTL +
((1 ) 0.7 * S ) 0.5 * H * (1 * 0.6 * i) ) 0.5 * L) ) P PC * (0.01 * B ) 0.05))
smaller of the two numbers from Steps 1 and 2.
4. Since the signalling traffic is uniformly distributed over 16 logical links, and these
logical links will be assigned to the MTLs (physical links). We need to first
determine the amount of traffic each logical link holds (nllogical):
nl logical + N
16
can handle (nlog-per-MTL):
n log*per*MTL + ROUND DOWN ǒ nl min

nl logical
Ǔ
mtls + ROUND UP ǒn 16
log*per*MTL
Ǔ)R v 16
NOTE mtls should not exceed 16.

30th Jun 02 68P02900W21-K 15–17
GMR-01
Where: U is: the percent link utilization (0.25).

i the ratio of intra-BSC handover to all handover.
PPC the number of pages per call.
B the number of BTSs supported by the BSC.
mtls 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 or
potential traffic load carried (approximately equal to
the number of MSC to BSC trunks).

15–18 68P02900W21-K 30th Jun 02
GMR-01

The purpose of the LCF GPROC or LCF GPROC2 device type is to support the functions
of MSC link protocol, layer 3 call processing, and the BTS link protocol. It is
recommended that an LCF GPROC supports either an MTL or one to eight BTSs, with
up to 15 RSLs and layer 3 call processing; and that an LCF GPROC2 supports either two
MTLs or one to 15 BTSs (GSR3), with up to 31 RSLs and layer 3 call processing.
NOTE It is not recommended that an LCF support both an MTL and

The higher capacities available with GPROC2 are only achieved

if GPROC2s are the only processor type in use in a GSR3
system. If GPROC is also used then GPROC planning formulae
should be used, even for GPROC2.

Since one LCF GPROC can support one MTL, the number of required LCF is the same
as the number of required MTLs (MSC to BSC links) obtained from Table 15-1 or from
mtls calculated in the non-standard traffic model from the previous section.
For GPROC2, if the number of required MTLs is obtained from Table 15-1 the number of
LCF is:
N LCF + ROUNDUP MTLs

2
ǒ Ǔ
However, if the traffic model does not conform to the standard model:
N LCF + mtls, if 2 < nl link u nl LCF*MTL
otherwise:

2
Ǔ
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 a
satellite link. PCR retransmits unacknowledged messages when there are no new
messages to be sent. This puts an additional processing load on the GPROCs
(LCF–MTLs) controlling the C7 signalling links. It is recommended that when PCR is
used, that the number of MTLs (and thus the number of LCF–MTLs) be doubled from the
number normally required.

30th Jun 02 68P02900W21-K 15–19
GMR-01
Generic processor (GPROC, GPROC2) GSM-001-103
Generic processor (GPROC, GPROC2)
Introduction
The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as a
generic control processor board. GPROCs are assigned functions and are then known by
their function names.
This section describes the BSC GPROC types and their functions. The BSC
configuration type and GPROC device type, are essential factors for BSC planning.
GPROC functions and types

There are two GPROC hardware types, GPROC and GPROC2. GPROC2 is needed, in
GSR3, for master processor functionality.
The GPROC is the basic building block of a distributed architecture. The GPROC
provides the processing platform for the BSC. By using multiple GPROCs software tasks
can be distributed across GPROCs to provide greater capacity. The set of tasks that a
GPROC is assigned, depends upon the configuration and capacity requirements of the
BSC. Although every GPROC is similar from a hardware standpoint, when a group of
tasks are assigned to a GPROC, it is considered to be a unique GPROC device type or
function in the BSC configuration management scheme.
There are a limited number of defined task groupings in the BSC, which result in the
naming of four unique GPROC device types for the BSC. The processing requirement of
a particular BSC determines the selection and quantity of each GPROC device type.
The possible general task groupings or functions for assignment to GPROCs are:
S 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 type
in the network element.
NOTE Prior to GSR3 a separate OMF was needed if OML traffic

exeeded a defined threshold. With GSR3 and GPROC2 the use
of a separate OMF becomes optional.

15–20 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Generic processor (GPROC, GPROC2)
BSC types
The BSC is configured as one of three types; the type is determined by the GPROCs
present.
NOTE With GSR3, and the use of GPROC2s, BSC type 1 is the only
configuration required.
S BSC type 0
– Master GPROC.
Running the BSP.
NOTE BSC type 0 is not recommended for operating BSC. Beginning

with release 1.4.0.x, BSC type 0 is not supported.
S BSC type 1
– Master GPROC.
Running the base site control processor (BSP) and carring out operations
and maintenance functionalities.
– Link control function (LCF).
Running the radio signalling link (RSL) and layer 3 processing or MTL (C7
signalling link) communications links.
S BSC type 2
– Master GPROC.
Running the BSP.
– LCF.
– OMF.
Running the O&M, including statistics collection, and OML link (X.25 control
links to the OMC-R).
The number of serial links per GPROC must be determined for each site. The current
values are either 8 or 16, with 16 being the default value. One link is reserved for each
module, so the number of available serial links is either 7 or 15.

30th Jun 02 68P02900W21-K 15–21
GMR-01
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 to
enable communication with the OMC-R.
S For redundancy each BSC should be equipped with a redundant BSP and an
additional GPROC to provide redundancy for the signalling LCFs. Where multiple
shelves exist, each shelf should have a minimum of two GPROCs to provide
redundancy within that shelf.

15–22 68P02900W21-K 30th Jun 02
GMR-01
Link control function, using GPROC2 exclusively (GSR3 only)

S A single GPROC2 will support two MTLs, each working at 20% link utilization.
NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limit

of 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 BSC
then the GPROC maximums apply to GPROC2. That is, the
GPROC2s can handle only as much traffic as a GPROC.
2. In some cases the software will allow maximums greater than

the planning guide, to allow ease of capacity expansion in future
releases, but it is not supported with this software release.
3. Combining MTL and RSL processing on a single GPROC2 is

not recommended.
links) for the BTSs must terminate on the same GPROC2, so if return loops are
used the maximum number of BTS sites will be 15 (if GPROC_slot parameter =
31). If the GPROC_slot parameter is set to 16 then at most 15 RSLs may exist
which would support up to seven BTS sites.
NOTE The number of serial links per GPROC must be determined for
each site, the current values are either:
For GPROC2; 16 or 32, with 16 being the default value.
For GPROC; 8 or 16, with 16 being the default value.
One link is reserved for each board (GPROC test purposes) so

the number of available serial links is either 15 or 31 for
GPROC2, and is 7 or 15 for GPROC.
When GPROC2s are not used exclusively, the LCF planning rules using GPROCs in the
next section should be used.

30th Jun 02 68P02900W21-K 15–23
GMR-01
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 the
NOTE There is a limit of 30 carriers in a single site (M-Cell6 has a limit

of 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 not

recommended.
links) for the BTSs must terminate on the same GPROC, so if return loops are
used the maximum number of BTS sites will be seven (if GPROC_slot
parameter =16). If the GPROC_slot parameter is set to 8 then at most 7 RSLs
may exist which would support up to 3 BTS sites.
NOTE The number of serial links per GPROC must be determined for
each site.
For GPROC the valid values are:

Eight or 16 (default). One link is reserved for each board
(GPROC test purposes) so that the number of available serial
links is either 7 or 15.
GPROC planning actions (GSR3)

Determine the number of GPROC or GPROC2s required.
N GPROC2 + 2B ) L ) C ) R
Where: NGPROC2 is: the total number of GPROC or GPROC2s required.

B the number of BSP GPROC or GPROC2s (2B for
redundancy).
L the number of LCF GPROC or GPROC2s.
C the number of CSFP GPROC or GPROC2s.
R the number of pool GPROC or GPROC2s (for
redundancy).
NOTE If dedicated GPROC or GPROC2s are required for either the

CSFP or OMF functions then they should be provisioned
separately.

15–24 68P02900W21-K 30th Jun 02
GMR-01
GPROC planning actions (GSR2 and earlier)

Determine the number of GPROCs required.
N GPROC + 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 typical
applications (less than ten messages per second), this link can exist on the same LCF as
that used to control BTSs. The CBL should not be controlled by a LCF–MTL (a GPROC
controlling an MTL).
OMF GPROC required

The BSC type 2 configuration offloads many of the O&M functions and control of the
interface to the OMC-R from the BSP. One of the major functions off loaded from the
BSP is the central statistics process. When determining the total number of statistics,
consider the number of instances of that statistic.
N ST + (ECS < C) ) (T CS < n) ) SX25LAPD (L ) X ) B)
Where: NST 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 statistics
are enabled across all cells.

30th Jun 02 68P02900W21-K 15–25
GMR-01

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

The BSS supports pooled GPROCs for LCF and OMF redundancy. By equipping
additional GPROCs for spares, if an LCF or the OMF GPROC were to fail, the system
software will automatically activate a spare GPROC from the GPROC pool to replace the
failed GPROC.

15–26 68P02900W21-K 30th Jun 02
GMR-01
Transcoding
Introduction
Transcoding reduces the number of cellular subscriber voice/data trunks required by a
factor of four. If transcoding takes place at the switch using a RXCDR, the number of
links between the RXCDR and the BSC is reduced to approximately one quarter of the
number of links between the RXCDR and the MSC.
The capacity of one BSU shelf is 12 MSI slots, six of which may contain a transcoder
(XCDR) or generic DSP processor (GDP); this limitation is due to power constraints. The
capacity of one RXU shelf can support up to 16 GDP/XCDRs or GDPs and typically
provides a better solution of the transcoding function for larger commercial systems.
Refer to the section Remote transcoder planning overview in Chapter 6.

S A GDP/XCDR can process 30 voice channels (GDP-E1/XCDR) or 24 voice
channels (GDP-T1), will support enhanced full rate speech, uplink/downlink volume
control and is capable of terminating one E1 or T1 link from the MSC.
the MSC.
S The A interface must terminate on the GDP/XCDR. A GDP can terminate T1 or E1
below).
required.

30th Jun 02 68P02900W21-K 15–27
GMR-01
T1 conversion
one of two ways. In either case the conversion may be part of an existing network
element or a standalone network element which would appear as a RXCDR.

simplest method, but uses at most 24 of the transcoding circuits on the XCDR. This
T1 links.
With KSW switching

For better utilization of the GDP/XCDRs, a mapping of five T1 circuits onto four E1
T+E
m=
2


15–28 68P02900W21-K 30th Jun 02
GMR-01
Planning actions transcoding at the BSC

Planning transcoding at the BSC must always be performed as it determines the number
of E1 or T1 links for the A interface. This text should be read in conjunction with the BSS
planning diagram Figure 15-1.
Using E1 links
The minimum number of E1 links required is the greater of two calculations that follow
(fractional values should be rounded up to the next integer value).
N= T
30
C+ X+ T
N=
31
Where: N is: the minimum number of E1 links required.

the MSC.
BSC.
Using T1 links
The minimum number of T1 links required is the greater of two calculations that follow
N= T
23
C+ X+ T
N=
24
Where: N is: the minimum number of T1 links required.

the MSC.
BSC.

30th Jun 02 68P02900W21-K 15–29
GMR-01
Introduction
A multiple serial interface provides the interface for the links between a BSSC cabinet
and other network entities in the BSS, BSC to BTS and BSC to RXCDR. An MSI can
interface only E1 links, an MSI-2 can interface both E1 and T1 links, but not
simultaneously.
S Each MSI-2 can interface two T1 links.


OMC-R.
If the OML links go directly to the MSC the master slot should be filled with an
GDP/XCDR, otherwise the slot should be filled with an MSI/MSI-2 which
terminates the E1/T1 link carrying the OML link to the OMC-R. These E1/T1 links
do not need to go directly to the OMC-R, they may go to another network element
for concentration.

15–30 68P02900W21-K 30th Jun 02
GMR-01

The following formulae assume local transcoding. Refer to the Multiple serial interface
(MSI, MSI-2) section of Chapter 6 RXCDR planning steps and rules for MSI planning
formulae for remote transcoding.
With E1 links
Determine the number of MSIs required.
M= B
2
Where: M 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 = B)m
2
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 E1
conversion.

30th Jun 02 68P02900W21-K 15–31
GMR-01
Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the
BSC.
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 three
additional KSWs, giving a total switching capacity of 4, 096 64 kbit/s ports of
which, eight timeslots are reserved by the system for test purposes and are not
available for use.
S For planning purposes assume fourteen MSI maximum per KSW. Each MSI may
be replace with four GDP/XCDRs.
S Using twelve MSIs per KSW may reduce the number of shelves required at a cost
of additional KSWs. For example, a BSC with 28 MSIs could be housed in three
shelves with three KSW modules or four shelves with two KSW modules.
S Verify that each KSW uses fewer than 1016 ports. There are three devices in a
BSC that require TDM timeslots. They are:
N = (G * n) + (R * 16) + (M * 64)

G the number of GPROC/GPROC2s.
which are doing on board E1 to T1 conversion,
when determining TDM bandwidth).
NOTE Any BSC site which contains a DRIM has 352 timeslots allocated
to DRIMs irrespective of the number of DRIMs equipped.

15–32 68P02900W21-K 30th Jun 02
GMR-01

Determine the number of KSWs required:
(G * n) + (R * 16) + (M * 64)
N=
(1016)

which are doing on board E1 to T1 conversion).

30th Jun 02 68P02900W21-K 15–33
GMR-01
BSU shelves GSM-001-103
BSU shelves
Introduction
The number of BSU shelves is normally a function of the number of GPROC/GPROC2,
MSI/MSI-2s, and GDP/XCDRs required.
The following factors should be considered when planning the number of BSU shelves:
S Each BSU shelf supports up to eight GPROCs or GPROC2s, if the number of
these exceed the number of slots available an additional BSU shelf is required.
S Each shelf is allocated to a single KSW and extension shelves are differentiated by
the presence of the KSW; extension shelves are those which do not contain a
primary KSW.
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
Bs = G
8
M+ R
Bs =
12
Bs = R
6
Where: Bs is: the minimum number of BSU shelves required.

NOTE The number of shelves may be larger if an attempt to reduce the

number of KSWs is made.
For GSR3 the number of shelves (cages) = 94.
For GSR3 the number of cabinets = 90.
There is a database limitation of 50 cabinets/shelves.
M-Cell sites do not require a cage to be equipped, only a cabinet.

15–34 68P02900W21-K 30th Jun 02
GMR-01
Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUs
and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is
required whenever a network element grows beyond a single shelf.
multiple KSWs.
that shelf and in shelves that do not not KSWs to drive both the local TDM
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.
N KXE + K < (K * 1)
N KXR + SE
N KXL + K ) S E

SE the number of extension selves.
NOTE Ensure that SE = 0 for extension shelves and 1 for expansion

shelves.

30th Jun 02 68P02900W21-K 15–35
GMR-01
For example

shelves
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

shelves
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

15–36 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Generic clock (GCLK)
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 first
GCLK.


30th Jun 02 68P02900W21-K 15–37
GMR-01
Clock extender (CLKX) GSM-001-103
Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one
BSU.
S One CLKX is required in the first BSU shelf, which contains the GCLK, when
18 shelves (LAN extension only allows 14 shelves in a single network element).

ǒǓ
N CLKX + ROUNDUP E * (1 ) RF)
6

E the number of expansion/expension shelves.
RF Redundancy factor.

15–38 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 LAN extender (LANX)
LAN extender (LANX)
Introduction
The local area network extender (LANX) provides a LAN interconnection for
communications between all GPROCs at a site.

N LANX + NBSU * (1 ) R F)

BSU 14

30th Jun 02 68P02900W21-K 15–39
GMR-01
Parallel interface extender (PIX) GSM-001-103
Introduction
The parallel interface extender (PIX) provides eight inputs and four outputs for site
alarms.

Choose the number of PIXs required.
or
PIX 8.

15–40 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Line interfaces (BIB, T43)
Introduction
1.544 Mbit/s) 3 V (peak pulse) line use a BIB.
pulse) 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.

Minimum number of BIBs or T43s = =
3 6

30th Jun 02 68P02900W21-K 15–41
GMR-01
Introduction
A BSSC cabinet can be supplied to operate from either a +27 V dc or –48/–60 V dc
power source.
The following factors should be considered when planning the PSU complement:
S 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.
Where: RF is: Redundancy factor.


15–42 68P02900W21-K 30th Jun 02
GMR-01
Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an
external battery to maintain power to the GPROC DRAM and the optical circuitry on the
LANX in the event of a mains power failure.
S One BBBX is required per shelf; if the battery backup option is to be used.


30th Jun 02 68P02900W21-K 15–43
GMR-01
Verify the number of BSU shelves and BSSC2 cabinets GSM-001-103
Verify the number of BSU shelves and BSSC2 cabinets
Verification
S The number of shelves is greater than one eighth the number of GPROC (or
GPROC2) 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.

15–44 68P02900W21-K 30th Jun 02
GMR-01
Chapter 16
Planning and equipment
descriptions for pre M-Cell BTSs

30th Jun 02 68P02900W21-K i
GMR-01
GSM-001-103

ii 68P02900W21-K 30th Jun 02
GMR-01
Chapter overview
Introduction
This chapter (included for reference only) covers Motorola BTS equipment produced
prior to the introduction of the M-Cell BTS range.
NOTE This chapter is not indexed as it is provided for reference

purposes only.
The chapter is divided into two sections and describes:

S BTS planning steps and rules.
S BTS RF configurations.

30th Jun 02 68P02900W21-K 16–1
GMR-01
BTS planning steps and rules GSM-001-103
BTS planning steps and rules
Introduction
This section provides the planning steps and rules for the BTS, including ExCell and
TopCell. 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.

16–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BTS planning steps and rules
BTS site
The steps required to plan a BTS site (including ExCell and TopCell sites) are listed
below:
1. Determine if the site has equipment shelters.
2. Determine the number of BTS cabinets required, refer to the section BTS
cabinets in this chapter.
3. Determine the receiver front end configuration, refer to the section Receiver front
end in this chapter.
4. Determine the transmit combining configuration, refer to the section Transmit
combiner shelf in this chapter.
5. Determine the number of bandpass filters required, refer to the section Duplexer
in 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 Carrier
equipment (DRCU/SCU/TCU, DRIM, DRIX) in this chapter.
8. Determine the number of E1/T1 line interfaces required, refer to the section Line
interface (BIB, T43) in this chapter.
9. Determine the number of MSIs required, refer to the section Multiple serial
interfaces (MSI, MSI-2) in this chapter.
10. Determine the number of GPROC, GPROC2s required, refer to the section
Generic 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 switch
extender (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 interface
extender (PIX) in this chapter.
17. Determine the number of DRIX3cs required, refer to the section Digital radio
interface extender (DRIX3c) in this chapter.
18. Determine the number of BBBXs boards required, refer to the section Battery
backup board (BBBX) in this chapter.
19. Determine the power requirements, refer to the section Digital shelf power
supply in this chapter.

30th Jun 02 68P02900W21-K 16–3
GMR-01
Introduction
This section provides information on how to determine the number of control channels
and the number of GPROC, GPROC2s required at a BTS.
This information is required for the sizing of the links to the BSC, and is required when
calculating the exact configuration of the BSC required to support a given BSS.
Typical call parameters

The number of control channels and GPROC, GPROC2s required at a BTS depend on a
set of call parameters; typical call parameters for BTS planning are given in Table 16-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), the
ratio of IMSI detaches to calls (Id) and whether the short message sequence (type 1) or
long message sequence (type 2) is used for IMSI detach; typically Id = 0 (that is IMSI
If IMSI detached is disabled:
L=I
L = I + 0.2 * I d

L = I + 0.5 * I d

16–4 68P02900W21-K 30th Jun 02
GMR-01
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 always
required.
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 information
uses the SDCCH.

30th Jun 02 68P02900W21-K 16–5
GMR-01
Calculations for determining BTS GPROC, GPROC2 requirements GSM-001-103
Calculations for determining BTS GPROC, GPROC2 requirements
Introduction
This section discusses the basic planning dependencies for determining the number of
GPROC, GPROC2s required for a BTS site. Some background information regarding the
call processing functions at the BTS is also provided.
Call processing functions

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

16–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Calculations for determining BTS GPROC, GPROC2 requirements
GPROC, GPROC2 management

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

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

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

30th Jun 02 68P02900W21-K 16–7
GMR-01
GPROC, GPROC2 planning

The number of GPROC, GPROC2s required at a given BTS site is dependent on carrier
and channel configuration together with the projected call mix at the BTS. The projected
call mix must be done on an individual BTS basis. When determining the required
number of GPROC, GPROC2s for a given BTS shelf, the call mix associated with the
cells supported by the RTFs in the shelf, must be used.
BTS type 0
A BTS type 0 only supports one active GPROC, which is referred to as the BTP.
Although a second BTP may exist to meet redundancy requirements, only one may be
active at any given time.
For the typical call mix a type 0 BTS supports up to two RTFs. For a BTS with more than
three RTFs then a type 1 BTS should be used. For the border location area call mix a
type 0 BTS supports up to two RTFs. If the call parameters differ significantly from those
given in Table 16-1 then the formula given below should be used.
BTS type 1
A BTS type 1 supports multiple active GPROC, GPROC2s. The RRSM and CRM
functions reside on the BTP, in addition to an optional instance of the RSS. A BTS type 1
also supports DHPs.
The number of RTFs a BTP can control depends on the total number of RTFs at the BTS
site. Table 16-2 gives the max_dris setting (the number of RTFs a BTP can control) for
the BTP for the typical and border location area call mix for a given number of RTFs and
Erlangs for a BTS. If the call parameters differ significantly from those given in
Table 16-1, the formula given below should be used. If the formula gives two RTFs per
DHP, then the border location area call mix rules should be used. If the formula gives one
RTF per DHP, then the BTP may control one RTF for BTS sites of less than three RTFs.
Table 16-2 Maximum number of Erlangs supported by the BTP

max_dris Typical call mix Location area border call mix
value for
Maximum Maximum Maximum Maximum
BTP RTFs Erlangs RTFs Erlangs
0 30 200 20 120
1 22 140 15 85
2 14 80 10 50

16–8 68P02900W21-K 30th Jun 02
GMR-01
Call mixes
The factors that determine call mixes are highly site dependent. The main factors being
the ratio of location updates to calls and call hold time. Those BTSs that contain cells on
the edge of location areas, will have a greater loading of location updates. This impacts
the number of required DHPs and control channel configurations and the maximum
number of RTFs supported by a BTS site.
An RTF is controlled by one DHP or the BTP. For the typical call mix a DHP supports up
to three RTFs and for the border location area call mix a DHP supports up to two RTFs.
If the call parameters differ significantly from those given in Table 16-1, the formula given
here should be used to determined the maximum number of RTFs a DHP or the BTP
should control; the result should be rounded down to an integer value.
N RTF + 0.8
0.2 + (1 + 1.4 < L + 0.9 < S + 0.5 < H) / T
Where: NRTF is: the maximum number of RTFs supported per

DHP (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 before
determining the BTS shelf configurations.
The sections Shelf configurations for typical call mix and Shelf configurations for
border location area call mix respectively, provide recommended shelf configurations
for the normal call mixes given in Table 16-3 and Table 16-4, and border location area call
mixes given in Table 16-5 and Table 16-6. The number of RTFs referred to in these
sections is the number of active RTFs. Inactive, or standby carriers do not utilize
GPROC, GPROC2 resources. The numbers given are the number of GPROC,
GPROC2s required with and without redundancy. For redundancy the number of
GPROC, GPROC2s given is the number required such that no single GPROC, GPROC2
failure will cause a loss of RTFs or capacity. See Redundant GPROC, GPROC2s below
for more details on GPROC, GPROC2 redundancy.
Command max_dris
The max_dris setting for the DHP should be the same as the number of RTFs per DHP.
For the BTP the max_dris setting should be the value from Table 16-3, Table 16-4,
Table 16-5 and Table 16-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 value
number in the following tables indicates that this DHP is optional and only required for
redundancy.

30th Jun 02 68P02900W21-K 16–9
GMR-01
Shelf configurations for typical call mix

Table 16-3 and Table 16-4 give the recommended number of GPROC, GPROC2s and
max_dris values for the first shelf and the other shelves, respectively for a BTS with the
typical call mix parameters. The BTP is duplicated when redundancy (R) is specified.
Table 16-3 Recommended BTP/DHP configurations and max_dris values for the
first shelf of a BTS (3 RTFs per DHP)
Number max_dris values Total GPROCs
of RTFs BTP DHP1 DHP 2 DHP 3 Without With
redundancy redundancy
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 16-4 Other shelves (3 RTFs per DHP)

of RTFs DHP DHP 2 DHP 3 DHP 4 Without With
1 redundancy redundancy
1–3 3 3(R) N/A 1 2
3–6 3 3 3(R) N/A 2 3

16–10 68P02900W21-K 30th Jun 02
GMR-01
Shelf configurations for border location area call mix

Table 16-5 and Table 16-6 give the recommended number of GPROC, GPROC2s and
max_dris values for the first shelf and the other shelves, respectively for a BTS with the
border location area call mix parameters. The BTP is duplicated when redundancy (R) is
specified.
Table 16-5 Recommended BTP/DHP configurations and max_dris values for the first
shelf of a BTS (3 RTFs per DHP)
of RTFs BTP DHP1 DHP2 DHP3 DHP 4 Without With
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 16-6 Other shelves (3 RTFs per DHP)

of RTFs DHP1 DHP 2 DHP 3 DHP 4 Without With
1–3 2 2(R) 1 2
3–4 2 2 2(R) 2 3
5–6 2 2 2 2(R) 3 4

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

S Determine if ExCell or TopCell cabinets are required.
S Determine the number of cabinets required and number of cells to be supported by
each cabinet.

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

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

Cabinet types AG, BG, DG come equipped with a preselector shelf which has the
capacity to hold up to three preselectors each with its own 6-way splitter. If more than
three Rx antennas need to be terminated, a second preselector shelf is required. This
second shelf displaces Tx equipment.
One preselector with 6-way splitter is required for each Rx signal.
The splitter/preselector shelf can be removed from the BG and DG cabinets and a DPP
shelf fitted.

30th Jun 02 68P02900W21-K 16–13
GMR-01
Receiver front end GSM-001-103
Distributing Rx signals between multiple cabinets

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

The following rules apply for a cabinet to be able to support the Rx termination and
extension when the cabinet supports:
S 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 a
passive splitter in the DPP slot in an adjacent BTS cabinet.
S BTS Cabinet without DPP2
Unused splitter outputs may be used for extension to an adjacent cabinet. Each
output requires a 6 dB attenuator to feed the preselector/DPP/SPP in the adjacent
BTS cabinet.
S Receiver multicoupler
When the Rx antenna distribution is to a large number of cabinets, a GSM receiver
multicoupler can be equipped in an external equipment cabinet at the site.
One of the four types of multicoupler extender is required on each active
multicoupler output.
A multicoupler should be installed in an external equipment cabinet.

16–14 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Receiver front end
RFE planning actions

1. Determine the number of cells.
2. Determine number of cells which have DRCU/SCU/TCUs in more than one
cabinet.
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 two
Rx antennas.
4. Determine the type and quantity of RFE equipment required.

30th Jun 02 68P02900W21-K 16–15
GMR-01
Transmit combiner shelf GSM-001-103
Transmit combiner shelf
Introduction
The transmit combiner shelf is mounted directly above the upper bank of fans. If a
second preselector shelf is equipped, the Tx combining must be done externally.
Transmit RF signals to be combined inside a BTS cabinet can come either from
DRCU/SCU/TCUs within the cabinet or from a second BTS cabinet. A BTS cabinet has
six Tx ports and two combiner coupling ports.
Transmit combining equipment

The following equipment may be mounted on the transmit combiner shelf:
S Up to five hybrid combiner modules.
A hybrid combiner combines two inputs into one antenna, five combiners will
combine six inputs.
Unused ports must be terminated with a suitable load.
or
S One remotely tuneable combiner.
A RTC combines up to five inputs (four for a four cavity combiner) into one
antenna.
The channels to which RTC cavities are tuned, must be separated by 800 kHz.
With a phasing harness, up to ten channels (eight for four-cavity combiners) may
be combined together into one antenna.
The cavities of an RTC do not have to be connected to a single antenna.
and
S Up to three transmit bandpass filters.
A Tx BPF is a mandatory requirement for every transmitting antenna.
If an RTC or more than four hybrid combiners are installed, a maximum of two Tx
BPFs can be accommodated, allowing two cells to be serviced.
or
S Up to two cavity combining blocks (CCB).
A CCB (output) combines up to three inputs into one antenna.
The channels to which CCB cavities are tuned, must be separated by 400 kHz.
A CCB (extention) enables up to six inputs into one antenna.

16–16 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Transmit combiner shelf
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, the
required power output must be known in order to determine the type of combiner
to 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 for
any one input is approximately 3 dB.
S All combining may be done in an external equipment cabinet if desired, this
reduces heat generated in the BTS cabinet.
CAUTION The remotely tuneable combiner and multicoupler have not been
EMC tested for use in the external equipment rack. Since the
end of 1995 these items have not been available for use in this
configuration within the European Union.
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 combiners
required.

30th Jun 02 68P02900W21-K 16–17
GMR-01
Duplexer GSM-001-103
Duplexer
Introduction
If a single antenna is shared between a Tx and an Rx, a duplexer must be fitted.
Performance may be degraded and the use of separate Tx and Rx antennas is
recommended.
The following factors should be considered when planning combined antennas:
S 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 common
antenna/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 of
duplexers required.
An external equipment cabinet will be required when duplexers are used with
BTS4, BTS5, or BTS6 cabinets.

16–18 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)
Carrier equipment (DRCU/SCU/TCU, DRIM, DRIX)
Introduction
A carrier equipment kit consists of:
S For BTS; a DRCU/SCU/TCU, DRIM, and DRIX.
Together these three units provide a single RF carrier, which can be referred to as an
RTF.
The following factors should be considered when planning carrier equipment:
S 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 in
the 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 installing
excess 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.

30th Jun 02 68P02900W21-K 16–19
GMR-01
Line interfaces (BIB, T43) GSM-001-103
Introduction
The line interfaces, balanced line interface board (BIB) and T43 board (T43), provide
S To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544
Mbit/s) 3 V (peak pulse) line use a BIB.
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 two
BIBs (six links connected to each board).
S The BTS cabinet can interface up to twelve bidirectional E1 links using two T43
boards (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 = =
3 6

16–20 68P02900W21-K 30th Jun 02
GMR-01
Introduction
A multiple serial interface provides the interface between a BTS cabinet and the links
from the BSC. An MSI can interface only E1 links, an MSI-2 can interface both E1 and
T1 links.
The following factors should be considered when planning the MSI complement:
S To calculate the required number of 64 kbit/s channels, the site must be viewed as
consisting of its own equipment and that of other sites which are connected to it by
the drop and insert method.
Two 64 kbit/s channels are required for each active RTF.
A 64 kbit/s channel is required for every RSL (LAPD signalling channel) to the site.
In the drop and insert configuration, every site requires its own RSL for signalling.
With closed loop, two RSLs are required per site, one in each direction.
More information can be found in the Multiple serial interface (MSI, MSI-2)
Chapter 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 enable
communication with the BSC.
S Refer to Table 16-7 for the number of traffic channels (TCH) per radio signalling
link (RSL).

30th Jun 02 68P02900W21-K 16–21
GMR-01

n = number of TCHs at the BTS Number of 64 kbit/s Number of 16 kbit/s
RSLs RSLs
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, but
not 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.
Number of E1/T1 links
M=
2

16–22 68P02900W21-K 30th Jun 02
GMR-01
Generic processor (GPROC, GPROC2)
Introduction
The generic processor (GPROC, GPROC2) is used throughout the Motorola BSS as a
generic control processor.
The following factors should be considered when planning the GPROC, GPROC2
complement:
S 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 active
GPROCs 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 populated
to enable communication with the BSC.
GPROC, GPROC2 planning actions

Determine the number of GPROC, GPROC2s required.
Use the information to be found in the section Calculations for determining BTS
GPROC, GPROC2 requirements in this chapter.

30th Jun 02 68P02900W21-K 16–23
GMR-01
Timeslot switch (TSW) GSM-001-103
Timeslot switch (TSW)
Introduction
The timeslot switch (TSW) provides digital switching on the TDM highway of the BTS.
The TSW is designed for use in BTSs, although the KSW can continue to be used.
It should be borne in mind that the KSW provides all the TSW functionality plus subrate
switching and third-party conference functionality, but at an increased cost.
The following factors should be considered when planning the TSW complement:
S 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 required
for switch expansion.
S All DRIMs which support RTFs in a cell must be on a single TDM bus controlled by
the same TSW.
S For redundancy, duplicate all TSW boards.
TSW planning actions

Determine the number of TSWs required.

16–24 68P02900W21-K 30th Jun 02
GMR-01
Introduction
The kiloport switch extender (KSWX) extends the TDM highway of a BSU to other BSUs
and supplies clock signals to all shelves in multi-shelf configurations. The KSWX is
required whenever a network element grows beyond a single shelf. Although not required
in a single BTS cabinet configuration, if expansion to multiple cabinets is expected,
equipping the KSWX (and CLKX) will allow for easier expansion.
S For redundancy, duplicate all KSWX boards (requires redundant KSW/TSW).
multiple KSWs.
that shelf and in shelves that do not not KSWs to drive both the local TDM
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.
N KXE + K < (K * 1)
N KXR + SE
N KXL + K ) S E

SE the number of extension/expansion shelves.
NOTE Ensure that SE = 0 for extension shelves and 1 for expansion

shelves.

30th Jun 02 68P02900W21-K 16–25
GMR-01
Generic clock (GCLK) GSM-001-103
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 first
GCLK.


16–26 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Clock extender (CLKX)
Introduction
A clock extender (CLKX) provides expansion of GCLK timing to more than one BSU.
Although not required in a single BTS cabinet configuration; if expansion to multiple
cabinets is expected, equipping the CLKX (and KSWX) will allow for easier expansion
later.
S One CLKX is required if expansion is planned.

N CLKX + ROUNDUP ǒE6Ǔ < (1 ) R )F

E the number of expansion/expension shelves.
(1 if redundancy required (recommended).
NOTE Each BTS cabinet has one BSU shelf.

30th Jun 02 68P02900W21-K 16–27
GMR-01
Local area extender (LANX) GSM-001-103
Local area extender (LANX)
Introduction
The local area network extender (LANX) provides a LAN interconnection for
communications between all GPROC, GPROC2s at a site.

N LANX + NBSU < (1 ) R F)

BSU 14

16–28 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Parallel interface extender (PIX)
Introduction
The parallel interface extender (PIX) provides eight inputs and four outputs for site
alarms.

Determine the number of PIXs required.
or
PIX 8.

30th Jun 02 68P02900W21-K 16–29
GMR-01
Digital radio interface extender (DRIX3c) GSM-001-103
Digital radio interface extender (DRIX3c)
Introduction
The Digital radio interface extender (DRIX3c) provides the electrical-optical interface for
the downlink (Tx) data and the optical-electrical interface for the uplink (Rx) data between
the DRCU/SCU/TCU/PCU and the DRIM.
The following factors should be considered when planning the DRIX3c complement:
S 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.

16–30 68P02900W21-K 30th Jun 02
GMR-01
Introduction
The battery backup board (BBBX) provides a backup supply of +5 V dc at 8 A from an
external battery. It maintains power to the GPROC, GPROC2 DRAM and the optical
circuitry on the LANX, in the event of a mains power failure.
S One BBBX is required in each shelf.


30th Jun 02 68P02900W21-K 16–31
GMR-01
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 supply
modules (DPSM) required to power the BSU shelf. An additional DPSM may be
equipped for redundancy.
S The –48 V/–60 V dc BTS4 cabinet option includes the two DPSMs required to
power the BSU shelf, and a power converter unit for the DRCU/SCU/TCUs. An
additional DPSM may be added for redundancy.
The power converter unit is required to supply +27 V dc to the DRCU/SCU/TCUs,
and includes three dc/dc converter modules housed in the fifth DRCU/SCU slot. A
fourth converter module can be ordered separately to provide redundancy.
S The BTS6 cabinet power supplies, required to power both the digital shelf and
DRCU/SCU/TCUs, are provided:
– In a +27 V dc cabinet, by one enhanced power supply module (EPSM) per
three DRCU/SCU/TCUs (two EPSM for a six DRCU/SCU fit). A third EPSM
can be fitted for redundancy.
– In a –48 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 third
IPSM can be fitted for redundancy.
NOTE The EPSM and IPSM fitted to a BTS6 cabinet are not
interchangeable with the DPSM fitted to BTS4 and BTS5
cabinets.
S ExCell operates internally from +27 V dc and contains up to three EPSMs. ExCell
also contains a battery backup facility. A –48 V/–60 V dc supply is available for
customer supplied communications equipment.
S TopCell operates internally from +27 V dc and uses the EPSM. Battery backup is
provided for each cabinet. A –48 V/–60 V dc supply is available for customer
supplied communications equipment.

Determine the number of PSMs required.

16–32 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 BTS RF configurations
BTS RF configurations
Introduction
This section provides diagrams of the logical interconnections of the RF components in
various standard BTS site configurations, including ExCell and TopCell.
S Typical BTS configurations.
S Single cabinet RF configurations.
S Multiple cabinet RF configurations.

30th Jun 02 68P02900W21-K 16–33
GMR-01
Typical BTS configurations GSM-001-103
Typical BTS configurations
BTS configuration
The digital module and RF configuration for a BTS cabinet with four RF carriers and
hybrid combining is shown in Figure 16-1.
Figure 16-1 Single BTS or ExCell site with 4 RF carriers using hybrid combining
BTS CABINET TO TRANSMIT ANTENNA FROM RECEIVE ANTENNA
RF EQUIPMENT Tx BPF
PRESELECTOR/6-WAY SPLITTER
HYBRID OR
DUAL PATH PRESELECTOR
HYBRID
HYBRID
DRCU/SCUs
ONE RF CARRIER CONSISTS OF ONE

DRIM, DRIX AND DRCU/SCU
1 2 3 4
BSU SHELF FIBRE OPTIC LINKS
DRIX DRIX DRIX DRIX DUAL SERIAL BUS PIX

1 2 3 4
BTC DRIM DRIM DRIM DRIM DUAL MCAP BUS

1 2 3 4

A
BTC GCLK GCLK KSW KSW MSI MSI GPROC GPROC GPROC
A B
REDUNDANT REDUNDANT DUAL IEEE

802.5 LAN
LANX LANX
A B
LINKS FROM/TO BSC
BSC

16–34 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Typical BTS configurations
TopCell BTS configuration

The digital module and RF configuration for a TopCell BTS cabinet with six RF carriers
and hybrid combining is shown in Figure 16-2. TopCell supports a maximum of six
carriers.
Figure 16-2 TopCell with 6 RF carriers using hybrid combiners
Tx Rx Tx Rx Tx Rx
TRU1 TRU2 TRU3

Tx BPF Tx BPF Tx BPF
DPP DPP DPP
HYBRID HYBRID HYBRID
1 2 3 4 5 6
DRCU/ DRCU/ DRCU/
SCUs SCUs SCUs
TDU
FIBRE OPTIC LINKS
DRIX DRIX DRIX DRIX DRIX DRIX

1 2 3 4 5 6
DRIM DRIM DRIM DRIM DRIM DRIM BTC

2 3 4 5 6
1
B
BTC GCLK KSW MSI GPROC GPROC GPROC
DUAL MCAP BUS
DUAL IEEE LANX LANX

LINKS FROM/TO BSC 802.5 LAN A B
BSC

30th Jun 02 68P02900W21-K 16–35
GMR-01
Single cabinet RF configurations GSM-001-103
Single cabinet RF configurations
Single cabinet, single DRCU/SCU without diversity

A single cabinet, single DRCU/SCU configuration is shown in Figure 16-3. Table 16-8
provides a summary of the equipment required for this configuration. The following rules
apply:
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 16-3 Single cabinet, one DRCU/SCU, no diversity
Tx Rx
DUAL PATH
PRESELECTOR
Tx BPF
DRCU/SCU
BTS CABINET
Table 16-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

16–36 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Single cabinet RF configurations
Single cabinet, single DRCU/SCU with diversity

A single cabinet, single DRCU/SCU configuration with diversity is shown in Figure 16-4.
Table 16-9 provides a summary of the equipment required for this configuration. The
following 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 the
cabinet.
Figure 16-4 Single cabinet, one DRCU/SCU, diversity
Tx Rx Rx
DUAL PATH
PRESELECTOR
Tx BPF
DRCU/SCU
BTS CABINET
Table 16-9 Equipment required for single cabinet, single DRCU/SCU configuration with
diversity
Quantity Unit
3 Antennas
1 BTS cabinet
1 DRCU/SCU
Transmitter
1 Bandpass filter
Receiver

30th Jun 02 68P02900W21-K 16–37
GMR-01
Single cabinet, five DRCU/SCUs with combining

A single cabinet, five DRCU/SCU configuration with remotely tuneable or hybrid
combining but without diversity is shown in Figure 16-5. Table 16-10 provides a summary
of the equipment required for this configuration. The following rules apply:
S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can be

accommodated.
S If operation from a negative power supply voltage is required, only four

DRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will be
occupied by the dc/dc converters.
S If, when using hybrid combining, there are unequal levels of loss, the output power
for the BTS (sector) is that of the DRCU/SCU with the greatest loss. The other
DRCU/SCUs should be adjusted to lower their output to provide the same output
power level.
Figure 16-5 Single cabinet, 5 DRCU/SCUs, remotely tuneable or hybrid combining,

no diversity
Tx Rx
DUAL PATH
PRESELECTOR
Tx BPF
HYBRID
COMBINERS
Tx BPF
REMOTELY TUNEABLE COMBINER

HYBRID
HYBRID
HYBRID HYBRID
1 2 3 4 5
DRCU/SCUs
BTS CABINET

16–38 68P02900W21-K 30th Jun 02
GMR-01
remotely 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

30th Jun 02 68P02900W21-K 16–39
GMR-01
Single cabinet, six DRCU/SCUs with combining and diversity

A single cabinet, six DRCU/SCU configuration with remotely tuneable or hybrid
combining is shown in Figure 16-6. Table 16-11 provides a summary of the equipment
required for this configuration. The following rules apply:
S In a BTS6 or ExCell6 cabinet, a maximum of six DRCU/SCUs can be
accommodated.
S If operation from a negative power supply voltage is required, only four
DRCU/SCUs can be accommodated in a BTS4 cabinet. The fifth slot will be
occupied by the dc/dc converters.
S If, when using hybrid combining, there are unequal levels of loss, the output power
for the BTS (sector) is that of the DRCU/SCU with the greatest loss. The other
DRCU/SCUs should be adjusted to lower their output to provide the same output
power level.
Figure 16-6 Single cabinet, 6 DRCU/SCUs, remotely tuneable or hybrid

combining, diversity
Tx Rx Rx
Tx BPF
DUAL PATH
PRESELECTOR
HYBRID
HYBRID
HYBRID HYBRID HYBRID
1 2 3 4 5 6
DRCU/SCUs
BTS CABINET

16–40 68P02900W21-K 30th Jun 02
GMR-01
diversity 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

30th Jun 02 68P02900W21-K 16–41
GMR-01
Single cabinet, multiple antennas

A single cabinet, multiple antenna configuration is shown in Figure 16-7. Table 16-12
apply:
S If only one DRCU/SCU is used per carrier, combining is not required.
Figure 16-7 Single cabinet, multiple antenna (3 sector minimum) configuration
Tx Tx Tx Rx Rx Rx
DUAL PATH
Tx BPFs
PRESELECTORS
1 2 3
DRCU/
SCUs
BTS CABINET
Table 16-12 Equipment required for single cabinet, multiple antenna configuration
Quantity Unit
6 Antennas
1 BTS cabinet
3 DRCU/SCU
Transmitter
3 Bandpass filter
Receiver

16–42 68P02900W21-K 30th Jun 02
GMR-01
Single cabinet, multiple antennas with diversity

A single cabinet, multiple antenna configuration with diversity is shown in Figure 16-8;
this configuration provides for three sectors. Table 16-13 provides a summary of the
equipment required for this configuration. The following rules apply:
S A maximum of six receive signals, two per DRCU/SCU, are allowed per BTS
cabinet.
S If only one DRCU/SCU is used per carrier, combining is not required.
Figure 16-8 Single cabinet multiple antenna configuration, diversity
Tx Tx Tx Rx Rx Rx Rx Rx Rx
DUAL PATH
Tx BPF PRESELECTORS
1 2 3
DRCU/SCUs
BTS CABINET
Table 16-13 Equipment required for single cabinet, multiple antenna configuration with
diversity
Quantity Unit
9 Antennas
1 BTS cabinet
3 DRCU/SCU
Transmitter
3 Bandpass filter
Receiver

30th Jun 02 68P02900W21-K 16–43
GMR-01
Multiple cabinet RF configurations GSM-001-103
Multiple cabinet RF configurations
Multiple cabinet, single antenna, four DRCU/SCUs

A multiple cabinet, single antenna configuration without diversity is shown in Figure 16-9.
This configuration provides eight carriers on one antenna using hybrid combiners.
Table 16-14 provides a summary of the equipment required for this configuration. The
following rules apply:
S DRCU/SCUs can be connected to the combiners in any order. The transmit power
of a DRCU/SCU at the top of the cabinet depends on the number of combiner
levels it goes through. Each level of hybrid combining results in a loss of up to
3.2 dB of carrier power.
S The antenna feed to cabinet 2 originates from the test (unused) 6-way splitter port
in cabinet 1. An inline attenuator is required to ensure specified performance.
S This configuration may not be implemented using ExCell.
Figure 16-9 Multiple cabinet, single antenna, 4 DRCU/SCUs
Rx Tx
ATTENUATOR
Tx BPF
DUAL PATH HYBRID DUAL PATH

PRESELECTOR PRESELECTOR
HYBRID HYBRID
HYBRID HYBRID HYBRID HYBRID
1 2 3 4 1 2 3 4
DRCU/SCUs DRCU/SCUs
BTS CABINET 1 BTS CABINET 2

16–44 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103 Multiple cabinet RF configurations
configuration
Quantity Unit
2 Antennas
2 BTS cabinet
8 DRCU/SCU
Transmitter
7 Hybrid combiners
1 Bandpass filter
Receiver
1 Attenuator

30th Jun 02 68P02900W21-K 16–45
GMR-01
Multiple cabinet, single antenna, ten DRCU/SCUs

A multiple cabinet, single antenna configuration is shown in Figure 16-10. This
configuration provides ten carriers on one antenna using hybrid combiners. Table 16-15
apply:
S If one site/sector requires ten carriers, this configuration provides the best solution
from the point of view of output power.
S If the antenna feed to cabinet 2 originates from the auxiliary port on the rear of the
DPP2 in cabinet 1, a passive splitter is required to ensure specified performance.
S If the antenna feed to cabinet 2 originates from a DPP or a preselector in cabinet
1, an Rx extender is required to ensure specified performance.
Figure 16-10 Multiple cabinet, single antenna, 10 DRCU/SCUs, remotely

tuneable combiners
Rx ANTENNA Tx ANTENNA
Tx BPF
PHASING
PASSIVE HARNESS
SPLITTER
DPP2 DPP2
REMOTELY TUNEABLE REMOTELY TUNEABLE
COMBINER COMBINER
1 2 3 4 5 1 2 3 4 5
DRCU/ DRCU/
SCUs SCUs

16–46 68P02900W21-K 30th Jun 02
GMR-01
configuration 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

30th Jun 02 68P02900W21-K 16–47
GMR-01
Multiple cabinet, multiple antenna

A multiple cabinet, multiple antenna configuration is shown in Figure 16-11. This
configuration represents the minimum amount of equipment that will provide for six
sectors. Table 16-16 provides a summary of the equipment required for this
configuration. The following rules apply:
S If only one DRCU/SCU is used per sector, a combiner is not required.
Figure 16-11 Multiple cabinet, multiple antenna (6 sector minimum) configuration
Tx Tx Rx Rx Rx Rx Tx Tx
Tx Rx Rx Tx
DUAL PATH DUAL PATH

Tx BPF PRESELECTORS PRESELECTORS Tx BPF
1 2 3 4 5 6
DRCU/SCUs DRCU/SCUs
Table 16-16 Equipment required for multiple cabinet, multiple antenna configuration
Quantity Unit
12 Antennas
2 BTS cabinet
6 DRCU/SCU
Transmitter
6 Bandpass filter
Receiver

16–48 68P02900W21-K 30th Jun 02
GMR-01
Six sector configuration

A four cabinet six sector configuration is shown in Figure 16-12; this configuration
provides for three sectors. Table 16-17 provides a summary of the equipment required for
this 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 routed
to.
S The multicoupler may not be required for all sectors, if this is the case, the
antennas connects directly to the BTS cabinet preselectors and bypasses the
multicoupler.
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-stated
top 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 not
meet the specification and the DRCU/SCUs with the higher available transmit
power would have their power reduced.
S The remotely tuneable combiner and multicoupler have not been EMC tested for
use in the external equipment rack. Since the end of 1995 these items have not
been available for use in this configuration within the European Union.
S This configuration may not be implemented using ExCell or TopCell.
S An external equipment cabinet is required.
Figure 16-12 Four cabinet six sector configuration

Tx Tx Tx Rx Rx Rx Rx Rx Rx Tx Tx Tx
EXTERNAL
EQUIPMENT
CABINET
MULTICOUPLER
LARGE
MULTICOUPLER
EXTENDER
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
BTS CABINET 1 BTS CABINET 2 BTS CABINET 3 BTS CABINET 4

30th Jun 02 68P02900W21-K 16–49
GMR-01
Table 16-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

16–50 68P02900W21-K 30th Jun 02
GMR-01
Six sector BTS6 configuration

A six sector configuration using BTS6s is shown in Figure 16-13; this configuration
provides for three sectors with only three cabinets. Table 16-18 provides a summary of
the 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 the
Motorola-stated top of cabinet output power specification DRCU/SCUs 1, 2, 5, 6,
7, 8, 11, 12, 13, 14, 17, and 18 do not because of two levels of hybrid combining.
Therefore, the site does not meet the specification and the DRCU/SCUs with the
higher available transmit power would have their power reduced.
S This configuration may not be implemented using ExCell or TopCell.
Figure 16-13 Multiple cabinet, 6 sector BTS6 (3 carriers per sector) configuration
Tx Tx Rx Rx Tx Tx Rx Rx Tx Tx Rx Rx
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
BTS CABINET 1 BTS CABINET 2 BTS CABINET 3
Table 16-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

30th Jun 02 68P02900W21-K 16–51
GMR-01

16–52 68P02900W21-K 30th Jun 02
GMR-01
Index

30th Jun 02 68P02900W21-K I–1
GMR-01
GSM-001-103

I–2 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
A BSS
block diagram, 1–4
code storage facility processor, 1–8
Acronyms, 1–13 interfaces, 2–2
maximum network parameter values to support
Air interface control channels, 3–80 GPRS, 7–8
planning checklist, 1–12
Alarm reporting, E1/T1 links, 2–12 planning diagram, 5–8, 6–4
planning for GPRS, 7–2
Alternative call model, planning examples, 10–19 planning overview, 1–10
standard configurations, 13–2
Antenna gain, 3–27 system architecture, 1–4
system components, 1–5
Antennas, 4–10 typical hardware configuration diagrams, 13–3
upgrade rules to support GPRS, 7–7
Ater interface
BSS timeslot allocation, 3–103
auto–connect mode, 2–19
backwards compatibility mode, 2–19 BSU shelves
planning calculations, 5–48
Auto–connect mode, XBL links, 5–31 planning factors, 5–47
BTS
Average call duration, 12–3 site restrictions, 2–4
standard configurations, 13–2
to BSC interconnections, 2–3
BTS concentration
blocking, 2–24
B concepts and rules, 2–21
emergency call handling, 2–25
examples, 2–35
Baseband hopping, 1–8, 3–42, 3–74
planning guidelines, 2–33
reserved allocation, 2–24
BBBX
resource optimization for handovers (BCROH),
planning factors and calculations (BSC), 5–57 2–41
planning factors and calculations (RXCDR), 6–24
BTS planning , 4–2
BCCH carrier, options, 3–97
BIB C
planning calculations (BSC), 5–55 C7 protocol, 5–13
planning calculations (RXU), 6–22
Call parameters, 3–78, 5–9, 8–10, 12–2
planning factors (BSC), 5–55
sample statistic calculations, 12–8
planning factors (RXU), 6–22
Carrier timeslot allocation, examples, 3–99
Blocking, 3–9 CBL, 5–38
BSC CCCH calculations, 3–83
equipage planning, 5–2 Cell architecture, 3–67
LCS signalling link capacities, 8–10 Cell broadcast channel, 1–8
planning steps outline, 5–3
Cell resource manager, 7–5
planning steps outline for LCS, 8–8
scaleable architecture, 5–6 Cell site sectorization, 3–41
signalling link capacities, 5–7 CLKX
system capacity, 5–5 planning calculations (BSC), 5–52
to BTS interconnections, 2–3 planning calculations (RXU), 6–19
BSC to BTS link, procedure capacities, 5–12 planning factors (RXU), 6–19

30th Jun 02 68P02900W21-K I–3
GMR-01
GSM-001-103
Co–channel interference, 3–40 E1/T1 link connections, 4–13

Code storage facility processor, 1–8 Emergency call pre–emption, 7–5
Coding schemes Encoding
GPRS, 3–57 GSM circiut–switched data channel, 3–50
impact on interconnect planning, 5–19 GSM control channel, 3–49
GSM speech channel, 3–46
Comfort noise, 3–60
enhanced full rate, 3–48
Control channel configurations, 3–81, 3–86
Enhanced auto–connect mode, XBL links, 5–31
border location area, 3–90
non–border location area, 3–89 Enhanced BSC capacity, 5–6
CSFP, 5–39 Equalization, 3–62
Erlang, definition, 2–21
Erlang B, definition, 2–21
D
Error coding schemes, 3–44
Decibel, conversion factors, 3–12
Expansion, BTS sites, 4–20
planning calculations (BSC), 5–56
planning calculations (RXCDR), 6–23 F
planning factors (RXCDR), 6–23 File transit delay, 3–119
Directed retry, 7–5 FMUX/FOX, 4–17
Diversity, 1–7 Frequency bands, all systems, 3–36
DPROC, PCU planning process, 7–13, 7–14 Frequency channel re–use, 3–36
DRI and combiner configurations, 4–24 Frequency hopping, 1–7, 3–42, 7–5
Dynamic allocation Frequency planning, 3–70
BSC to BTS, 7–4 Frequency spectrum
BTS links, 2–27 DCS1800, 3–5
network configurations, 2–26 GSM900, 3–4
performance issues, 2–32 PCS1900, 3–5
RXCDR to BSC circuits, 2–19 UK network operators, 3–5
DYNET Fresnel zone, 3–11, 3–13
description, 2–23
device, 2–21
G
E Gaussian minimum shift keying, 3–7, 3–42
Gb entities, 7–23
E1 circuit
daisy chain connection, 2–6 Gb interface, 7–3
multiplexing, 2–9 Gb link, PCU to SGSN, 7–28
star connection, 2–5
Gb load, 7–27
E1 link calculations, 5–42
BSC to BTS, 5–19 Gb signalling overhead, 7–25
BSC to RXCDR, 6–5 GCLK
RXCDR to MSC, 6–6 planning calculations (BSC), 5–51
E1 links planning calculations (RXU), 6–18
cable requirements for a fully configured PCU,
7–10 planning factors (RXU), 6–18
PCU to BSC, 7–22 GDP, planning factors, 6–9
E1/T1, daisy chain examples, 2–7 GDS link, PCU termination, 7–6

I–4 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
GPROC, parameters used to determine Horizonmacro

requirements, 5–10 850/1900 MHz operation, 3–6
cabinet overview, 4–4
GPROC2 four cabinet configuration, 13–9
acting as CSFP, 5–39 RF configuration diagrams, 13–10
BSC types, 5–36 single cabinet configuration, 13–6
BSP redundancy, 5–39 three cabinet configuration, 13–8
enhanced, 6–7 two cabinet configuration, 13–7
LCF and OMF redundancy, 5–39 Horizonmicro and Horizonmicro2, cabinet features
planning factors (BSC), 5–36 and differences, 4–6
planning factors (RXCDR), 6–7
task groupings and functions, 5–35 Horizonmicro2
RF configuration diagrams, 13–23
GPRS, 1–9 system configuration, 2–49
air interface planning, 3–111
BSS maximum network parameter values, 7–8
BSS planning, 7–2 I
BSS to PCU planning example, 7–33 IMSI detaches, ratio per call, 12–6
BSS upgrade provisioning, 7–7
data rates, 3–121 Interface modules, 4–22
dynamic timeslot allocation, 3–96 Interleaving, 3–51
estimating traffic throughput, 3–112 Intra–BSS handovers, 12–5
LCF GPROC2 provisioning, 5–23
load planning, 3–91
planning factors, 3–92 J
radio and packet data traffic channels, 3–80
timeslot usage, 3–93 Joint Radio Committee (JRC) of the Nationalized
Power Industries, 3–11
GPRS carrier, 3–97
GPRS traffic, timeslot allocation, 3–110 K

Grade of service, definition, 2–22 KSW
GSL, planning calculations, 5–33
GSN, 3–93 planning factors (BSC), 5–45
KSW switching, 5–41
KSWX
H planning calculations (BSC), 5–49
Handover, 2G – 3G, 3–75
Handovers, ratio per call, 12–5
HDSL L
cable installation, 2–47
LANX
cable selection, 2–46
OMC–R link management, 2–45
Horizon, connecting to M–Cell6, 13–26 planning factors (BSC), 5–53
Horizoncompact and Horizoncompact2, cabinet Lapse rate, 3–16
overview and differences, 4–4
LCF, 5–37
Horizoncompact2, RF configuration diagrams, 13–19 GPROC2 provisioning for GPRS, 5–23

30th Jun 02 68P02900W21-K I–5
GMR-01
GSM-001-103
LCF calculations, for MTL processing, 5–30 MSI–2

T1 to E1 conversion, 5–41
LCF–GPROC2 calculations, for RSL processing,
T1 to E1 conversion for XCDR, 6–9
5–21
MTL, planning factors, 5–24
LCS
provisioning example, 10–42 MTL calculations
system architecture, 8–4 non–standard traffic model, 5–28
standard traffic model, 5–25
LLC_PDU, frame layout, 3–117
Multipath fading, 3–61
LMTL, planning calculations, 8–25 Multiplexing, 2–9
Location area planning, 11–1
example procedure, 11–2
N
Location services, overview, 8–2
Nailed paths, 2–28
Location update factor, 3–79, 5–10, 12–7
Network interface unit (NIU), 4–13
Location updates, ratio per call, 12–6
Network planning exercise, 10–1
initial requirements, 10–2
Network planning factors, 3–2
M
Network support program (NSP), 9–7
M–Cell, standard configurations, 14–2 Network topology
M–Cell2 BTS site restrictions, 2–4
cabinet overview, 4–5 interface restrictions, 2–4
RF configuration diagrams, 14–44 NVM board
single cabinet configuration, 14–8 planning factors and calculations (BSC), 5–58
three cabinet configuration, 14–10 planning factors and calculations (RXCDR), 6–25
M–Cell6
cabinet overview, 4–4 O
connecting to Horizon, 13–26
four cabinet configuration, 14–11 Okumura, 3–30
RF configuration diagrams, 14–13 OMC–R
single cabinet configuration, 14–7 capacity, 9–3
two cabinet configuration, 14–9 datacomms equipment, 9–6
M–Cellaccess GUI server, 9–5
hardware configuration diagrams, 14–3 HDSL link management, 2–45
PCC cabinet equipage, 4–2 planning example, 10–17
system configuration, 2–51 planning steps, 9–2
system server, 9–4
Macrocell, 3–68 upgrading to GSR5, 9–8
Main control unit (MCU), 4–16 upgrading to GSR6, 9–9
OMF, 5–38
Main control unit, with dual FMUX (MCUF), 4–15
One phase access
Micro base control unit (microBCU), 4–12 GSL planning, 5–33
Microcell, 3–68 RSL planning, 5–17
system planning, 2–49 Output power, mobile handset, 3–63
MSC to BSC link, procedure capacities, 5–11
MSI / MSI–2 P
planning calculations (RXCDR), 6–12 Pages per call, 12–8
planning factors (BSC), 5–43 Paging rate, 12–7
planning factors (RXCDR), 6–11 location area planning, 11–1

I–6 68P02900W21-K 30th Jun 02
GMR-01
GSM-001-103
PCC cabinet, 4–21 RF configuration diagrams

typical hardware configurations, 14–3 Horizoncompact2, 13–19
Horizonmacro, 13–10
PCU, 1–9
Horizonmicro2, 13–23
device alarms, 7–4
M–Cell2, 14–44
frame relay interface parameters, 7–29
M–Cell6, 14–13
hardware layout diagram, 7–11
interface to SGSN, 7–3 RRI measurements, 3–14
link diagram, 7–32 RSL, 2–15
provisioning goals, 7–21 definition, 2–22
redundancy planning, 7–18 planning, 2–25
upgrading, 7–21 planning constraints, 2–17
PCU shelf (cPCI), planning factors, 7–12 planning factors, 5–14
Picocell, 3–68
system planning, 2–51 RSL calculations
non–standard traffic model, 5–17
PICP board, planning factors, 7–14 standard traffic model, 5–15
PIX RTF
planning calculations (BSC), 5–54 definition, 2–22
planning calculations (RXU), 6–21 types, 2–15
RTF path, fault containment, 2–13, 2–29, 7–6
RXCDR
PMC module, planning factors, 7–16
as E1 switching interface (PCU to SGSN), 7–3
Power supply, BTS requirements, 4–19 equipage planning, 6–2
GDP/XCDR planning factors, 5–40
Pre–load, RSL planning, 5–17
links to BSC/MSC, 5–40
Preventive cyclic retransmission, 5–30 planning steps, 6–3
Propagation losses, 3–11 RXU shelf
PRP board, planning factors, 7–15
planning factors, 6–15
R S
RACH arrivals, RSL planning, 5–18 SACCH multiframe, 3–60
Radio Sonds, 3–15 Satellite link, MSC to BSC signalling, 5–30
Radio wave propagation Satellite links, delay times, 2–32
antenna gain, 3–27
SDCCH calculations, 3–87
clutter factor, 3–27
DCS1800 path loss, 3–35 SGSN, 7–3
environmental effects, 3–18 Short message service, 1–8
free space loss, 3–24
GSM900 path loss, 3–34 Signalling link capacities, BSC, 5–7
plane earth loss, 3–25 Signalling link capacities (LCS), BSC, 8–10
power budget and system balance, 3–33
Signalling message sequence, 5–11
Rayleigh environment, 3–22
Rician environment, 3–23 SMS, ratio per call, 12–4
within buildings, 3–29 Software planning tools, 3–3
Refractometers, 3–15 Spatial diversity, 3–61
Reserved allocation, 2–22 State models, MS and SGSN, 3–95
Reserved allocation algorithm, uses, 2–34 Static allocation, 2–22
RF carriers, limitations, 3–6 Switchable timeslots, provisioning, 3–105

30th Jun 02 68P02900W21-K I–7
GMR-01
GSM-001-103
Synthesizer hopping, 1–8, 3–43, 3–70 Traffic intensity, 3–10

System dimensioning, Erlang B model, 3–9 Traffic model and capacity calculations, 1–10
Training sequence code, 3–62
T Transceiver, types, 1–5
T1 circuit Transceivers, 4–11

daisy chain connection, 2–6 Transcoder, BSSC cabinet hardware diagram, 13–5
multiplexing, 2–9
star connection, 2–5 Transcoding, at the BSC, 5–42
T1 link calculations, 5–42 Transition module, planning factors, 7–17
BSC to BTS, 5–20
Transmit configurations, M–Cell and Horizonmacro,
BSC to RXCDR, 6–5 4–9
RXCDR to MSC, 6–6
TRAU
T1 to E1 conversion, 5–41
32 kbit/s, 3–59
for the XCDR, 6–9
definition, 2–23
T43
planning factors (BSC), 5–55 U
UMTS, 3–75
TCH to SDCCH conversion, 7–6
TCP/IP, 3–117
TDMA frame structure, 3–51 V
Terrestrial backhaul, definition, 2–22 Vanguard 6560, 9–6
Terrestrial backhaul resources, 2–25, 2–30
Timeslot, allocation algorithms, 2–11
Timeslot allocation X
dynamic (GPRS), 3–96
GPRS traffic, 3–110 XBL, 2–18
Timeslot multiplexer site, 2–28 planning factors, 5–31
Timeslot provisioning, GPRS, 3–114 XCDR
Timeslots, 3–116 planning factors, 6–9
switchable and reserved (GPRS), 3–97 sub–multiplexing and speech transcoding, 6–8
switchable utilization (GPRS), 3–107 T1 to E1 conversion, 6–9

I–8 68P02900W21-K 30th Jun 02
GMR-01

BSS Planing

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSS Planing

Hochgeladen von

Copyright:

Verfügbare Formate

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5

68P02900W21-K System Information: BSS Equipment Planning

Chap. 5: Page 5-21: Note relating to 70% GPROC2 utilization removed.

System Information: BSS Equipment Planning

System Information: BSS Equipment Planning

BSS Equipment Planning

System Information: BSS Equipment Planning

Copyrights, notices and trademarks

and MOTOROLA are registered trademarks of Motorola Inc.

System Information: BSS Equipment Planning

System Information: BSS Equipment Planning

Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

System Information: BSS Equipment Planning

Propagation effects on GSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11

System Information: BSS Equipment Planning

Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–80

System Information: BSS Equipment Planning

Micro base control unit (microBCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12

System Information: BSS Equipment Planning

Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

System Information: BSS Equipment Planning

BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–47

System Information: BSS Equipment Planning

RXCDR to BSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4

System Information: BSS Equipment Planning

Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22

System Information: BSS Equipment Planning

E1 link provisioning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–22

System Information: BSS Equipment Planning

Determining the number of LMTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–25

System Information: BSS Equipment Planning

Determine the hardware requirements for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–11

System Information: BSS Equipment Planning

System Information: BSS Equipment Planning

M-Cell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–12

System Information: BSS Equipment Planning

Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–30

System Information: BSS Equipment Planning

BTS planning steps and rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2

System Information: BSS Equipment Planning

Timeslot switch (TSW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–24

System Information: BSS Equipment Planning

Multiple cabinet RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–44

System Information: BSS Equipment Planning

Figure 1-1 BSS block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

System Information: BSS Equipment Planning

Figure 3-1 UK network operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5

System Information: BSS Equipment Planning

Figure 3-40 GPRS channel coding scheme 2 (CS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–57

System Information: BSS Equipment Planning

Figure 13-1 BSC controlling 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3

System Information: BSS Equipment Planning

Figure 14-17 2 sector (3/3), hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–20

System Information: BSS Equipment Planning

Figure 16-6 Single cabinet, 6 DRCU/SCUs, remotely tuneable or hybrid

System Information: BSS Equipment Planning

Table 1-1 Transceiver unit usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5

System Information: BSS Equipment Planning

Table 5-7 Number of BSC to BTS signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15

System Information: BSS Equipment Planning

Table 10-8 Equipment required for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13

System Information: BSS Equipment Planning

System Information: BSS Equipment Planning