BTS Planning Steps and Rules

SYSTEM INFORMATION
BSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 8.0
GSR8.0
GMR- 01
68P02900W21-R
GSR8.0
68P02900W21-R
SYSTEM INFORMATION
GMR-01
BSS EQUIPMENT PLANNING
GSM SOFTWARE RELEASE 8.0
System Information: BSS Equipment
Planning
© 1993 - 2006 Motorola, Inc. 68P02900W21-R

All Rights Reserved GMR-01 28 Feb 2006
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
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
GMR-01 28 Feb 2006

Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
System Information: BSS Equipment Planning

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Resolution of service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Incorporation of CDCNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Feature references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Safety issue reporting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Security Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Failure to comply with warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Caution labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Caring for the environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Disposal of Motorola Networks equipment in EU countries . . . . . . . . . . . . . . . . . . . . . 17
Disposal of Motorola Networks equipment in non-EU countries . . . . . . . . . . . . . . . . . . . 17
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Ordering manuals and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Manual amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
GMR availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CDCN availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CDCN instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CDCN amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 1: Introduction
Manual overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
68P02900W21-R i
28 Feb 2006 GMR-01
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
BSS equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
BSS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Features that affect planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Frequency hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Short message service, cell broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
PCU for GPRS upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Enhanced-GPRS (EGPRS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Adaptive Multi-Rate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Location services (LCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
{22322} BSC Reset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
{24347} Advanced Speech Call Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
{23769} VersaTRAU backhaul for EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
{23956} Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
{28075} Improved Timeslot Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
BSS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Initial information required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Planning methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Acronym list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Chapter 2: Transmission systems

BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Interconnecting the BSC and BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Interconnection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Daisy chain connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Daisy chain planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Aggregate Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
RTF path fault containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
16 kbit/s RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
16 kbit/s XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Dynamic allocation of RXCDR to BSC circuits (DARBC) . . . . . . . . . . . . . . . . . . . . . . 2-23
Managed HDSL on micro BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Integrated HDSL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
General HDSL guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Microcell system planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Chapter 3: BSS cell planning

Planning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
ii 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Contents
GSM frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

The GSM900 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
The DCS1800 frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Absolute radio frequency channel capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Modulation techniques and channel spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Dimensioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Channel blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Traffic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Grade of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Adaptive multi-rate (AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Introduction to AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Capacity and coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Migration to AMR half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
{22064} Interoperability with GSM half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
{23769} Interoperability with EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
{22064) GSM Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Introduction to GSM half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Capacity and coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Migration to half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Interoperability with AMR half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
{23769} Interoperability with EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Propagation effects on GSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Propagation production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Decibels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Fresnel zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Radio refractive index (RRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Environmental effects on propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Multipath propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
GSM900 path loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Path loss GSM900 vs DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Frequency re-use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Introduction to re-use patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Carrier/Interference (C/I) ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Other sources of interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Sectorization of sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Overcoming adverse propagation effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Hardware techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Error protection and detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
GSM speech channel encoding for Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
GSM speech channel encoding for enhanced Full Rate . . . . . . . . . . . . . . . . . . . . . . . . 3-60
{22064} GSM speech channel encoding for Half Rate . . . . . . . . . . . . . . . . . . . . . . . . 3-61
GSM speech channel encoding for AMR Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
GSM speech channel encoding for AMR Half Rate . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Link adaptation for AMR channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
GSM control channel encoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
GSM circuit-switched data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Mapping logical channels onto the TDMA frame structure . . . . . . . . . . . . . . . . . . . . . . 3-70
GPRS channel coding schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
68P02900W21-R iii
28 Feb 2006 GMR-01
Contents
16/32 kbit/s TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

EGPRS channel coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
64 kbit/s TRAU for EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Link adaptation (LA) in GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Voice activity detection (VAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Discontinuous transmission (DTX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Subscriber hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Hand portable subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Future planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
The microcellular solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Layered architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Combined cell architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Expansion solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
Frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Introduction to frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Rules for synthesizer frequency hopping (SFH) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Rules for baseband hopping (BBH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
{22879} Inter-radio access technology (2G-3G) cell reselection and handovers . . . . . . . . . . . . . . 3-119
Introduction to 2G-3G handovers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
2G-3G handover description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Impact of 2G-3G handovers on GSM system architecture . . . . . . . . . . . . . . . . . . . . . . 3-120
System considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121
Call model parameters for capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Control channel calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126
Number of CCCHs and PCCCHs per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129
Number of PCCCHs per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
User data capacity on the PCCCH timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142
Number of SDCCHs per BTS cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143
Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146
GPRS/EGPRS traffic planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
Determination of expected load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
Network planning flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
GPRS/EGPRS network traffic estimation and key concepts. . . . . . . . . . . . . . . . . . . . . . . . 3-152
Introduction to the GPRS/EGPRS network traffic estimation and key concepts . . . . . . . . . . . . 3-152
Dynamic timeslot allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156
Carrier timeslot allocation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-162
BSS timeslot allocation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-171
Provisioning the network with switchable timeslots . . . . . . . . . . . . . . . . . . . . . . . . . 3-173
Recommendation for switchable timeslot usage . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-178
Timeslot allocation process on carriers with GPRS traffic . . . . . . . . . . . . . . . . . . . . . . 3-179
GPRS/EGPRS air interface planning process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-180
Influential factors in GPRS/EGPRS cell planning and deployment . . . . . . . . . . . . . . . . . . 3-180
Estimating the air interface traffic throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-187
Configurable initial coding scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-203
GPRS/EGPRS data rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-203
iv 68P02900W21-R
GMR-01 28 Feb 2006
Chapter 4: AMR and {22064} GSM planning

Introduction to AMR and {22064} GSM planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
AMR basic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
{22064} GSM half rate basic operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
{22064} AMR and GSM half rate interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
New hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Influencing factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Quality and capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Benefits of AMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
AMR Full Rate and AMR Half Rate speech quality . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
AMR voice quality improvement and coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
{22064} Benefits of GSM half rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
{22064} GSM Half Rate speech quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Capacity increase due to half rate usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Timeslot usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Rate adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Introduction to rate adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Codec modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Thresholds and hystereses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Downlink adaptation MS monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Handover and power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Introduction to handover and power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Handover and power control thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Miscellaneous information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Emergency call handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Circuit pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Half rate utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Parameter descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Operational aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Equipment descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Chapter 5: BTS planning steps and rules

BTS planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Macrocell cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Horizon II macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Horizon macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Horizon compact and Horizon compact2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Microcell enclosures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Horizon II mini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Horizonmicro and Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Receive configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
68P02900W21-R v
28 Feb 2006 GMR-01
Contents
Receiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Transmit planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
EGPRS enabled CTU2 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
EGPRS enabled CTU2 configuration limitations . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
EGPRS general configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Baseband hopping (BBH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Broadcast control channel (BCCH) RTF configuration . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Antenna planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Carrier equipment (transceiver unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Restrictions when using CTU2s in Horizonmacro BTSs . . . . . . . . . . . . . . . . . . . . . . . 5-19
CTU/CTU2 power supply considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Transceiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Micro base control unit (microBCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
MicroBCU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Network interface unit (NIU) and site connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
NIU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
BTS main control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Planning considerations - HorizonII macro/HorizonII mini as expansion cabinet . . . . . . . . . . . . 5-30
Planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Cabinet interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Planning considerations - Horizon II macro as master cabinet . . . . . . . . . . . . . . . . . . . . 5-36
Planning considerations - Horizon II mini as master cabinet . . . . . . . . . . . . . . . . . . . . . 5-36
XMUX/FMUX/FOX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Site expansion board planning actions (Horizon II macro only) . . . . . . . . . . . . . . . . . . . . 5-37
Battery back-up provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
External power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Power planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Network expansion using macro/microcell BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Expansion considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Mixed site utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Line interface modules (HIM-75, HIM-120). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
HIM-75/HIM-120 planning actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
vi 68P02900W21-R
GMR-01 28 Feb 2006
DRI/Combiner operability components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
DRI and combiner relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Chapter 6: BSC planning steps and rules

BSC planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Mixing of equipment types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Remote transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
BSC system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
System capacity summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Scaleable BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Enhanced BSC capacity option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
LCS option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Determining the required BSS signalling link capacities . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
BSC signalling traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Assumptions used in capacity calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Link capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Determining the number of RSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Determining the number of RSLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
One phase access and enhanced one phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
BSC to BTS E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Determining the number of LCF GPROCs for RSL and GSL processing . . . . . . . . . . . . . . . 6-38
Determining the number of MTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42
Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43
Non-standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46
Calculate the number of LCFs for MTL processing . . . . . . . . . . . . . . . . . . . . . . . . . 6-47
MSC to BSC signalling over a satellite link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-48
Determining the number of LMTLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49
Determining the number of LMTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
BSC to SMLC interconnection planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50
Calculate the number of LCFs for LMTL processing. . . . . . . . . . . . . . . . . . . . . . . . . 6-51
Determining the number of XBLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Determining the number of XBLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52
Standard traffic model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
Non standard traffic model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
Determining the number of GSLs required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55
Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57
Generic processor (GPROC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
68P02900W21-R vii
28 Feb 2006 GMR-01
Contents
GPROC nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
GPROC functions and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
GPROC3 planning assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
BSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63
Cell broadcast link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
OMF GPROC required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66
Code storage facility processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
GPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67
GPROC planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68
Transcoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
Introduction to transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69
GDP/XCDR/EGDP/GDP2 planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . 6-71
EGDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-72
T1 conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74
Planning actions for transcoding at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-75
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77
MSI/MSI-2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78
Kiloport switch (KSW) and double kiloport switch (DSW2) . . . . . . . . . . . . . . . . . . . . . . . 6-80
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
KSW/DSW2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82
BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83
BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) . . . . . . . . . . . . . 6-87
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
KSWX/DSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
Generic clock (GCLK). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91
GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-91
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-92
CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-93
Local area network extender (LANX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-94
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-95
Line interface boards (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96
BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
viii 68P02900W21-R
GMR-01 28 Feb 2006
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-98
Non volatile memory (NVM) board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-99
Verify the number of BSU shelves and BSSC cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-100
Chapter 7: RXCDR planning steps and rules

Remote transcoder planning overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
RXCDR system capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
System capacity summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
RXCDR to BSC connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
RXCDR to BSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
RXCDR to MSC links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Generic processor (GPROC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
GPROC nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Transcoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Introduction to transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
XCDR/GDP/EGDP/GDP2 planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
EGDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
T1 conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Planning actions for transcoding at the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
MSI planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Kiloport switch (KSW) and double kiloport switch (DSW2) . . . . . . . . . . . . . . . . . . . . . . . 7-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
KSW/DSW2 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
RXU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) . . . . . . . . . . . . . 7-31
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
KSWX/DSWX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Generic clock (GCLK). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
68P02900W21-R ix
28 Feb 2006 GMR-01
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
GCLK planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
LANX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Non volatile memory (NVM) board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Verify the number of RXU shelves and BSSC cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Chapter 8: PCU upgrade for the BSS

BSS planning for GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Introduction to BSS planning for GPRS/EGPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
PCU to SGSN interface planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Feature compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
BSS upgrade to support GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
BSS upgrade provisioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Maximum BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
PCU hardware layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
PCU shelf (cPCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
MPROC board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
PSP planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
DPROC board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
PICP or PRP planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
PMC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Transition module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
x 68P02900W21-R
GMR-01 28 Feb 2006
PCU equipment redundancy and provisioning goals . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Support for equipment redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
PCU equipment redundancy planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Upgrading the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
Multiple (3xPCU) PCUs per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Introduction to multiple PCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
PCU example configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
E1 link provisioning for GPRS and EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
E1 interface provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
{23956} QoS capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43
MTBR allocation philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
PRP-PDTCH QoS planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48
PCU-SGSN: traffic and signalling planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50
Gb entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50
General planning guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
Specific planning guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
Gb signalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52
Determine the net Gb load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53
Gb link timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-55
Frame relay parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-55
BSS-PCU hardware planning example for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58
Introduction to BSS-PCU hardware planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58
BSS - PCU planning example for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59
BSS-PCU hardware planning example for EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-67
Introduction to BSS-PCU hardware planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-67
BSS - PCU planning example for EGPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68
{23956} BSS - PCU planning example for EGPRS with QoS enabled. . . . . . . . . . . . . . . . . 8-76
Chapter 9: Planning exercises

Initial requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
The exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Determine the hardware requirements for BTS B . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Determine the hardware requirements for BTS K . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Receiver requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Transmitter combining requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Determine the hardware requirements for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Determine the hardware requirements for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
MSI requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Transcoder requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Link interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
68P02900W21-R xi
28 Feb 2006 GMR-01
Contents
GPROC requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

KSW/DSW2 requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
KSWX/DSWX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
GCLK requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
CLKX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
PIX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
LANX requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Calculations using alternative call models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Planning example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Planning example 4 (using AMR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-68
A planning example of BSS support for LCS provisioning . . . . . . . . . . . . . . . . . . . . . . . . 9-90
Introduction to the LCS planning example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
Typical parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
LCS planning example calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-91
Chapter 10: Location area planning

Location area planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Location area planning calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Example procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Chapter 11: Deriving call model parameters from network statistics

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

Standard configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Typical BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
BSC with 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
BSC with full redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Single cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Single cabinet Horizon II macro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Single cabinet Horizon II mini BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Single cabinet Horizon II micro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Single cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Two cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Two cabinet Horizon II macro BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
xii 68P02900W21-R
GMR-01 28 Feb 2006
Two cabinet Horizon II mini BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

Two cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Three cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Three cabinet Horizon II macro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Three cabinet Horizon II mini BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
Three cabinet Horizon II micro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Three cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Four cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Four cabinet Horizon II macro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Four cabinet Horizon II mini BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Four cabinet Horizonmacro BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Horizon macrocell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
HorizonII macro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
[DCS1800] 4 or 8 carrier omni with HCUs and air combining . . . . . . . . . . . . . . . . . . . . 12-25
[DCS1800] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
[DCS1800] 2 sector 3/3 or 6/6 with DHUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
[DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . . . . . 12-31
[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
[DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining . . . . . . . . . . . . . . 12-34
[DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity . . . . . . . . . . . . . . . . . . . . . . 12-35
[DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
Horizon II macro cabinets with PGSM Duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
[PGSM] 4 or 8 carrier omni with HCUs and air combining . . . . . . . . . . . . . . . . . . . . . . 12-40
[PGSM900] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
[PGSM900] 2 sector 3/3 or 6/6 with HCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-44
[PGSM900] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . . . . 12-45
[PGSM900] 3 sector 2/2/2 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
[PGSM900] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining . . . . . . . . . . . . . 12-48
HorizonII mini cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
[DCS1800/EGSM900/PGSM900] High power Omni-1, standard power Omni-2. . . . . . . . . . . . 12-50
[DCS1800/EGSM900/PGSM900] High power Omni-2, standard power Omni-4. . . . . . . . . . . . 12-52
[DCS1800/EGSM900] High power Bowtie-2, standard power Bowtie-4 . . . . . . . . . . . . . . . 12-54
[DCS1800/EGSM900] High power 2 sector 1/1, standard power 2 sector 2/2 . . . . . . . . . . . . . 12-56
[DCS1800/EGSM900/PGSM900] High power 2 sector 2/2, standard power 2 sector 4/4 . . . . . . . . 12-58
[DCS1800/EGSM900] High power 3 sector 1/1/1, standard power 3 sector 2/2/2 . . . . . . . . . . . 12-59
[DCS1800/EGSM900] High power 3 sector 2/2/2, standard power 3 sector 4/4/4 . . . . . . . . . . . 12-60
HorizonII micro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-61
[DCS1800/EGSM900] Single cabinet - Horizon II micro. . . . . . . . . . . . . . . . . . . . . . . 12-62
[DCS1800/EGSM900] Three cabinet - Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . 12-64
Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66
[DCS1800] 4 carrier omni, with duplexed hybrid and air combining . . . . . . . . . . . . . . . . . 12-67
[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and air combining . . . . . . . . . . . . 12-69
[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining . . . . . . . . . . . . . . . . 12-71
[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and air combining . . . . . . . . . . . . . 12-73
[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining . . . . . . . . . . . . . . . . . . . . 12-75
[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining . . . . . . . . . . . . . . . . . 12-77
[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and air combining . . . . . . . . . . . . 12-79
Horizoncompact2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-82
[GSM900/DCS1800] Horizoncompact2 single BTS system . . . . . . . . . . . . . . . . . . . . . 12-83
[GSM900/DCS1800] Horizoncompact2 two BTS system . . . . . . . . . . . . . . . . . . . . . . 12-84
[GSM900/DCS1800] Horizoncompact2 three BTS system . . . . . . . . . . . . . . . . . . . . . . 12-85
Microcell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
68P02900W21-R xiii
28 Feb 2006 GMR-01
Contents
[GSM900/DCS1800] Horizonmicro2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . 12-88

[GSM900/DCS1800] Horizonmicro2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . . 12-89
[GSM900/DCS1800] Horizonmicro2 three BTS system . . . . . . . . . . . . . . . . . . . . . . . 12-90
Connecting Horizon II macro cabinets to Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . 12-91
Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-91
Compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-91
Examples of mixed cabinet configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-92
Using CTU2s in Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98
Connecting Horizon II macro cabinets to M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . 12-99
Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
Compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
900 MHz BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-100
1800 MHz BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101
Chapter 13: M-Cell BTS configurations

Standard M-Cell configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Single cabinet BTS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Single cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Single cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Two cabinet BTS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Two cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Two cabinet M-Cell6 BTS with CTU2 Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Three cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Three cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Four cabinet BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Four cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
M-Cell RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Overview of M-Cell configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
M-Cell6 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
M-Cell2 cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
xiv 68P02900W21-R
GMR-01 28 Feb 2006
List
of
Figures
List of Figures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 1-1: BSS block diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Figure 2-1: BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Figure 2-2: Possible network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-3: Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-4: Closed loop and open ended daisy chains . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Figure 2-5: Simple daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Figure 2-6: Daisy chain with branc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Figure 2-7: Typical low capacity BSC/BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Figure 2-8: Example using a switching network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Figure 2-9: Timeslot allocation using new and old algorithms . . . . . . . . . . . . . . . . . . . . . . 2-13
Figure 2-10: Alternative network configuration with E1 switching network . . . . . . . . . . . . . . . . 2-15
Figure 2-11: A configuration with a BTS equipped with two redundant RTFs . . . . . . . . . . . . . . . 2-17
Figure 2-12: A configuration with a BTS equipped with two non-redundant RTFs . . . . . . . . . . . . . 2-17
Figure 2-13: Fully equipped RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Figure 2-14: Sub-equipped RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Figure 2-15: XBL utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Figure 2-16: Conversion of E1 to HDSL links by modem and microsite . . . . . . . . . . . . . . . . . . 2-29
Figure 2-17: Microcell daisy chain network configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Figure 2-18: Microcell star network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Figure 2-19: Microcell configuration using E1/HDSL links. . . . . . . . . . . . . . . . . . . . . . . . 2-31
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: AMR half rate capacity increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Figure 3-5: AMR Full Rate call quality improvements . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Figure 3-6: GSM half rate capacity increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-7: GSM half rate codec comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-8: First Fresnel zone radius calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Figure 3-9: Refraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Figure 3-10: Measurement of the RRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Figure 3-11: Refraction effects on a microwave system . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Figure 3-12: Attenuation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Figure 3-13: Reflection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Figure 3-14: Scattering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Figure 3-15: Diffraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Figure 3-16: Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-17: Propagation effect - Rayleigh fading environment . . . . . . . . . . . . . . . . . . . . . . 3-28
Figure 3-18: Rayleigh distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Figure 3-19: Propagation effect - Rician environment . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Figure 3-20: Rician distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Figure 3-21: Plane earth loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Figure 3-22: Focusing of power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
68P02900W21-R xv
28 Feb 2006 GMR-01
List of Figures
Figure 3-23: Measurement of gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Figure 3-24: In building propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Figure 3-25: Okumura propagation graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Figure 3-26: BTS antenna height of 50 m, MS height of 1.5 m (GSM900) . . . . . . . . . . . . . . . . . 3-42
Figure 3-27: BTS antenna height of 100 m, MS height of 1.5 m (GSM900) . . . . . . . . . . . . . . . . 3-42
Figure 3-28: Path loss vs cell radius for small cells . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Figure 3-29: Adjacent cell interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Figure 3-30: 7 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Figure 3-31: 4 site - 3 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Figure 3-32: 2 site - 6 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Figure 3-33: Carrier interference measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
Figure 3-34: The coding process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Figure 3-35: Coding process illustration (full rate and enhanced full rate speech) . . . . . . . . . . . . . 3-55
Figure 3-36: Coding process illustration (AMR full rate and AMR half rate speech) . . . . . . . . . . . . 3-56
Figure 3-37: Coding process illustration (GSM HR speech, control and data) . . . . . . . . . . . . . . . 3-57
Figure 3-38: Speech channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Figure 3-39: Preliminary coding for enhanced Full Rate speech. . . . . . . . . . . . . . . . . . . . . . 3-60
Figure 3-40: Speech Channel Encoding for GSM Half Rate Speech . . . . . . . . . . . . . . . . . . . . 3-61
Figure 3-41: Speech channel encoding for AMR Full Rate . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Figure 3-42: Speech channel encoding for AMR Half Rate . . . . . . . . . . . . . . . . . . . . . . . . 3-65
Figure 3-43: Control channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
Figure 3-44: Data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
Figure 3-45: Diagonal interleaving - full rate speech . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Figure 3-46: Diagonal interleaving - half rate speech. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Figure 3-47: Rectangular interleaving - control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Figure 3-48: Diagonal interleaving - CS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Figure 3-49: GPRS channel coding scheme 1 (CS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Figure 3-53: EGPRS channel coding scheme 1 (MCS-1) . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Figure 3-62: SACCH multiframe (480 ms) for DTX and Full Rate . . . . . . . . . . . . . . . . . . . . 3-99
Figure 3-63: SACCH multiframe (480 ms) for DTX and Half Rate . . . . . . . . . . . . . . . . . . . . 3-100
Figure 3-64: Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Figure 3-65: Training sequence code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Figure 3-66: The subscriber environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Figure 3-67: Subscriber distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
Figure 3-68: Layered architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Figure 3-69: Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110
Figure 3-70: Combined cell architecture structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Figure 3-71: Separating BCCH and TCH bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Figure 3-72: Band usage for macrocells with microcells . . . . . . . . . . . . . . . . . . . . . . . . . 3-113
Figure 3-73: Frequency split for TCH re-use planning example . . . . . . . . . . . . . . . . . . . . . . 3-116
Figure 3-74: Avoiding co-channel and adjacent channel interference . . . . . . . . . . . . . . . . . . . 3-117
Figure 3-75: BBH frequency spectrum allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Figure 3-76: GSM and UMTS system nodes and interfaces. . . . . . . . . . . . . . . . . . . . . . . . 3-120
xvi 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning List of Figures
Figure 3-77: CCCH and PCCCH decision tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

Figure 3-78: Location area diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-144
Figure 3-79: MM state models for MS and SGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155
Figure 3-80: Carrier with reserved and switchable GPRS/EGPRS timeslots . . . . . . . . . . . . . . . . 3-172
Figure 3-81: 1 circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots . . . . . . . . . . 3-177
Figure 3-82: One carrier, all timeslots (8 TCHs) designated as switchable . . . . . . . . . . . . . . . . . 3-177
Figure 3-83: Generic planning and dimensioning process . . . . . . . . . . . . . . . . . . . . . . . . 3-180
Figure 3-84: Multiplexing 4 TBFs on an air timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-184
Figure 3-85: LLC_PDU frame layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-199
Figure 3-86: LLC PDU to TDMA bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-205
Figure 4-1: AMR FR/clean speech vs EFR vs performance requirements . . . . . . . . . . . . . . . . . 4-7
Figure 4-2: AMR FR/clean speech codec modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Figure 4-3: AMR HR/clean speech vs EFR vs GSM FR vs GSM HR vs perf. reqs . . . . . . . . . . . . . 4-9
Figure 4-4: AMR HR/clean speech codec modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-5: 3 carriers, only one hr-capable carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Figure 4-6: 3 carriers, all hr-capable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Figure 4-7: 5 carriers, only one hr-capable carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Figure 4-8: 5 carriers, only 3 hr-capable carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-9: 5 carriers, all hr-capable carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-10: Rate adaptation: codec modes, thresholds and hystereses . . . . . . . . . . . . . . . . . . 4-18
Figure 4-11: Congestion threshold settings for AMR half rate . . . . . . . . . . . . . . . . . . . . . . 4-31
Figure 4-12: Alternative configurations for the BSSC3 cabinet . . . . . . . . . . . . . . . . . . . . . . 4-35
Figure 4-13: AMR backhaul paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Figure 4-14: hr backhaul paths - ESS mode enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Figure 5-1: DRI and combiner relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Figure 6-1: {23769} BSS planning diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Figure 6-2: EGDP configuration with the additional E1 termination in use. . . . . . . . . . . . . . . . . 6-72
Figure 6-3: EGDP configuration without the additional E1 termination in use . . . . . . . . . . . . . . . 6-73
Figure 7-1: Sub-multiplexing and speech transcoding at the RXCDR . . . . . . . . . . . . . . . . . . . 7-14
Figure 7-2: EGDP configuration with the additional E1 termination in use. . . . . . . . . . . . . . . . . 7-16
Figure 7-3: EGDP configuration without the additional E1 termination in use . . . . . . . . . . . . . . . 7-17
Figure 8-1: Gb interface alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Figure 8-2: PCU shelf layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Figure 8-3: GPRS maximum throughput and coverage, fully redundant configuration . . . . . . . . . . . 8-32
Figure 8-4: GPRS maximum throughput and coverage, full redundancy not required . . . . . . . . . . . . 8-33
Figure 8-5: EGPRS maximum throughput and coverage, full redundancy not required . . . . . . . . . . . 8-34
Figure 8-6: PCU example configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
Figure 8-7: Frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-56
Figure 8-8: PCU equipment and link planning for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . 8-58
Figure 8-9: PCU equipment and link planning for EGPRS . . . . . . . . . . . . . . . . . . . . . . . . 8-68
Figure 9-1: Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Figure 10-1: Four BSCs in one LAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Figure 10-2: Four BSCs divided into two LACs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Figure 12-1: BSC controlling 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Figure 12-2: Fully redundant BSC controlling 34 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Figure 12-3: BSSC cabinet equipped to provide transcoding . . . . . . . . . . . . . . . . . . . . . . . 12-6
Figure 12-4: Macrocell BTS with one Horizon II macro cabinet . . . . . . . . . . . . . . . . . . . . . 12-7
Figure 12-5: Macrocell BTS with one Horizon II mini cabinet . . . . . . . . . . . . . . . . . . . . . . 12-8
Figure 12-6: Macrocell BTS with one Horizon II micro cabinet . . . . . . . . . . . . . . . . . . . . . . 12-9
Figure 12-7: Macrocell BTS with one Horizonmacro cabinet . . . . . . . . . . . . . . . . . . . . . . . 12-10
Figure 12-8: Macrocell BTS with two Horizon II macro cabinets . . . . . . . . . . . . . . . . . . . . . 12-11
Figure 12-9: Macrocell BTS with two Horizon II mini cabinets . . . . . . . . . . . . . . . . . . . . . . 12-12
Figure 12-10: Macrocell BTS with two Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . . 12-13
Figure 12-11: Macrocell BTS with three Horizon II macro cabinets . . . . . . . . . . . . . . . . . . . . 12-14
68P02900W21-R xvii
28 Feb 2006 GMR-01
List of Figures
Figure 12-12: Macrocell BTS with three Horizon II mini cabinets. . . . . . . . . . . . . . . . . . . . . 12-15
Figure 12-13: Macrocell BTS with three Horizon II micro cabinets . . . . . . . . . . . . . . . . . . . . 12-16
Figure 12-14: Macrocell BTS with three Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . 12-17
Figure 12-15: Macrocell BTS with four Horizon II macro cabinets . . . . . . . . . . . . . . . . . . . . 12-19
Figure 12-16: Macrocell BTS with four Horizon II mini cabinets . . . . . . . . . . . . . . . . . . . . . 12-21
Figure 12-17: Macrocell BTS with four Horizonmacro cabinets . . . . . . . . . . . . . . . . . . . . . 12-22
Figure 12-18: [DCS1800] 4 or 8 carrier omni with HCUs and air combining. . . . . . . . . . . . . . . . 12-25
Figure 12-19: [DCS1800] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Figure 12-20: [DCS1800] 2 sector 3/3 or 6/6 with DHUs. . . . . . . . . . . . . . . . . . . . . . . . . 12-29
Figure 12-21: [DCS1800] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . . 12-31
Figure 12-22: [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs . . . . . . . . . . . . . . . . . . . . . . . 12-32
Figure 12-23: [DCS1800] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining . . . . . . . . . . . 12-34
Figure 12-24: [DCS1800] 3 sector 2/2/2 or 4/4/4 with air comb. and 4 branch Rx diversity . . . . . . . . . 12-35
Figure 12-25: [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining . . . . . . . . . . . . . . 12-37
Figure 12-26: [PGSM900] 4 or 8 carrier omni with HCUs and air combining . . . . . . . . . . . . . . . 12-40
Figure 12-27: [PGSM900] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . . . . . . . . 12-42
Figure 12-28: [PGSM900] 2 sector 3/3 or 6/6 with HCUs . . . . . . . . . . . . . . . . . . . . . . . . 12-44
Figure 12-29: [PGSM900] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . 12-45
Figure 12-30: [PGSM900] 3 sector 2/2/2 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
Figure 12-31: [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining. . . . . . . . . . . 12-48
Figure 12-32: DCS1800/EGSM900 HP Omni-1/SP Omni-2 . . . . . . . . . . . . . . . . . . . . . . . 12-50
Figure 12-33: DCS1800/EGSM900 HP Omni-2/SP Omni-4 . . . . . . . . . . . . . . . . . . . . . . . 12-52
Figure 12-34: DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4 . . . . . . . . . . . . . . . . . . . . . . 12-54
Figure 12-35: DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2. . . . . . . . . . . . . . . . . . . . 12-56
Figure 12-36: DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4. . . . . . . . . . . . . . . . . . . . 12-58
Figure 12-37: DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2 . . . . . . . . . . . . . . . . . . 12-59
Figure 12-38: DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4 . . . . . . . . . . . . . . . . . . 12-60
Figure 12-39: [DCS1800/EGSM900] Horizon II micro one cabinet configuration . . . . . . . . . . . . . 12-62
Figure 12-40: [DCS1800/EGSM900] Horizon II micro three cabinet configuration. . . . . . . . . . . . . 12-64
Figure 12-41: 4 carrier omni, duplexed hybrid and air combining . . . . . . . . . . . . . . . . . . . . . 12-67
Figure 12-42: 6 carrier omni, duplexed dual-stage hybrid and air combining . . . . . . . . . . . . . . . . 12-69
Figure 12-43: 2 sector (3/3), duplexed dual-stage hybrid combining. . . . . . . . . . . . . . . . . . . . 12-71
Figure 12-44: 2 sector (6/6), duplexed dual-stage hybrid and air combining . . . . . . . . . . . . . . . . 12-73
Figure 12-45: 3 sector (2/2/2), duplexed hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . 12-75
Figure 12-46: 3 sector (4/4/4), duplexed hybrid and air combining . . . . . . . . . . . . . . . . . . . . 12-77
Figure 12-47: 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1) . . . . . . . . . . . 12-79
Figure 12-48: 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2) . . . . . . . . . . . 12-80
Figure 12-49: Horizoncompact2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-83
Figure 12-50: Horizoncompact2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-84
Figure 12-51: Horizoncompact2 three BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-86
Figure 12-52: Horizonmicro2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-88
Figure 12-53: Horizonmicro2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-89
Figure 12-54: Horizonmicro2 three BTS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90
Figure 12-55: Sector 4/4 configuration with Horizon II macro and Horizonmacro cabs . . . . . . . . . . . 12-92
Figure 12-56: Sector 6/6 configuration with Horizon II macro and Horizonmacro cabs . . . . . . . . . . . 12-93
Figure 12-57: Sector 2/2/2 configuration (Horizon II macro as master cabinet). . . . . . . . . . . . . . . 12-94
Figure 12-58: Sector 2/2/2 configuration (Horizonmacro as master cabinet) . . . . . . . . . . . . . . . . 12-95
Figure 12-59: Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabs . . . . . . . . . . 12-96
Figure 12-60: Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabs . . . . . . . . . . 12-97
Figure 12-61: Horizonmacro cabinet configuration using CTUs and CTU2s . . . . . . . . . . . . . . . . 12-98
Figure 12-62: 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections . . . . . . . . . . . . 12-100
Figure 12-63: 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections . . . . . . . . . . . 12-101
Figure 13-1: Single cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Figure 13-2: Single cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
xviii 68P02900W21-R
GMR-01 28 Feb 2006
List of Figures
Figure 13-3: Two cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

Figure 13-4: Two cabinet M-Cell6 BTS with CTU2 Adapters . . . . . . . . . . . . . . . . . . . . . . 13-6
Figure 13-5: Three cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Figure 13-6: Four cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Figure 13-7: 3 carrier omni, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Figure 13-8: 3 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . . . . . . . . . 13-13
Figure 13-9: 4 carrier omni, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Figure 13-10: 4 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . . . . . . . . . 13-17
Figure 13-11: 6 carrier omni, cavity combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Figure 13-12: 6 carrier omni, cavity combining, high power duplexer . . . . . . . . . . . . . . . . . . . 13-21
Figure 13-13: 8 carrier omni, combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Figure 13-14: 2 sector (3/3), hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Figure 13-15: 2 sector (3/3), hybrid combining, medium power duplexers . . . . . . . . . . . . . . . . . 13-27
Figure 13-16: 3 sector (2/2/2), combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Figure 13-17: 3 sector (2/2/2), combining, medium power duplexers . . . . . . . . . . . . . . . . . . . 13-31
Figure 13-18: 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . . . . . . . . . 13-33
Figure 13-19: 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . . . . . . . . . 13-35
Figure 13-20: 3 sector (4/4/4), cavity combining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
Figure 13-21: 3 sector (4/4/4), 3-input CBF, hybrid combining . . . . . . . . . . . . . . . . . . . . . . 13-39
Figure 13-22: 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers . . . . . . . . . . . 13-41
Figure 13-24: 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers . . . . . . . . . . . . . 13-45
Figure 13-25: 3 sector (6/6/6), cavity combining, high power duplexers . . . . . . . . . . . . . . . . . . 13-47
Figure 13-27: 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers . . . . . . . . . . . . . 13-51
Figure 13-28: 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1) . . . . . . . . . . . . 13-53
Figure 13-29: 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2) . . . . . . . . . . . . 13-54
Figure 13-30: 3 sector (8/8/8), cavity combining, high and medium pwr duplexers (Pt 1) . . . . . . . . . . 13-56
Figure 13-31: 3 sector (8/8/8), cavity combining, high and medium pwr duplexers (Pt 2) . . . . . . . . . . 13-57
Figure 13-32: 3 sector (4/4/4), 3-input CBF, air combining, medium pwr duplexers (Pt 1) . . . . . . . . . 13-59
Figure 13-33: 3 sector (8/8/8), 3-input CBF, air combining, medium pwr duplexers (Pt 2) . . . . . . . . . 13-60
Figure 13-34: 3 sector (8/8/8), 3-input CBF, combining, medium pwr duplexers (Pt 1) . . . . . . . . . . . 13-62
Figure 13-35: 3 sector (8/8/8), 3-input CBF, combining, medium pwr duplexers (Pt 2) . . . . . . . . . . . 13-63
Figure 13-36: 3 sector (2/2/2), hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65
Figure 13-37: 3 sector (2/2/2), hybrid combining, medium power duplexers . . . . . . . . . . . . . . . . 13-67
Figure 13-38: 2 carrier, single sector, hybrid combining . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
Figure 13-39: 2 carrier, single sector, hybrid combining, medium power duplexer . . . . . . . . . . . . . 13-71
Figure 13-40: 2 sectors (1 carrier per sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
Figure 13-41: 2 carrier, single sector, air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-74
Figure 13-42: 2 sectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
68P02900W21-R xix
28 Feb 2006 GMR-01
List of Figures
This page intentionally left blank.
xx 68P02900W21-R
GMR-01 28 Feb 2006
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 3: CDCNs incorporated in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 1-1: Transceiver unit usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Table 1-2: Acronym list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Table 2-1: BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Table 2-2: RTF types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Table 3-1: dBm and dBW to power conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Table 3-2: Speech channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Table 3-3: AMR codecs, convolutional output bits and punctured bits . . . . . . . . . . . . . . . . . . . 3-58
Table 3-4: X, Y and Z bit values for AMR FR speech channel encoding . . . . . . . . . . . . . . . . . . 3-63
Table 3-5: X, Y, Z and W bit values for AMR HR speech channel encoding . . . . . . . . . . . . . . . . 3-65
Table 3-6: Interleaving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
Table 3-7: Distribution of 456 bits from one 20 ms full rate speech sample . . . . . . . . . . . . . . . . 3-74
Table 3-8: Distribution of 228 bits from one 20 ms half rate speech sample . . . . . . . . . . . . . . . . 3-75
Table 3-9: Coding parameters for GPRS coding schemes. . . . . . . . . . . . . . . . . . . . . . . . . 3-84
Table 3-10: Coding parameters for EGPRS coding schemes . . . . . . . . . . . . . . . . . . . . . . . 3-96
Table 3-11: Frequency and parameter setting plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116
Table 3-12: Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
Table 3-13: Control channel configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134
Table 3-14: SDCCH planning for typical parameters (non-border location area) . . . . . . . . . . . . . . 3-146
Table 3-15: SDCCH planning for typical parameters (border location area) . . . . . . . . . . . . . . . . 3-149
Table 3-16: MM state model of MS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-154
Table 3-17: Capping settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157
Table 3-18: Switchable timeslot utilization (Part A) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-174
Table 3-19: Switchable timeslot utilization (Part B) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-176
Table 3-20: Typical TCP throughput versus RLC/MAC throughput at zero block error rate . . . . . . . . . 3-186
Table 3-21: ARP mobile selection (ARP Rank) order . . . . . . . . . . . . . . . . . . . . . . . . . . 3-187
Table 3-22: Utilisation of coding schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-189
Table 3-23: MTBR Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Table 3-24: MTBR Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Table 3-25: THP Weight Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Table 3-26: THP Weight Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Table 3-27: QoS Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-194
Table 3-28: QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS . . . . . . . . . . 3-195
Table 3-29: QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS . . . . . . . . . . . 3-196
Table 3-30: GPRS downlink data rates (kbit/s) with TCP (CS1). . . . . . . . . . . . . . . . . . . . . . 3-206
Table 3-34: GPRS downlink data rates (kbit/s) with UDP (CS1) . . . . . . . . . . . . . . . . . . . . . 3-208
68P02900W21-R xxi
28 Feb 2006 GMR-01
List of Tables
Table 3-38: EGPRS downlink data rates (kbit/s) with TCP (MCS1) . . . . . . . . . . . . . . . . . . . . 3-210
Table 3-47: EGPRS downlink data rates (kbit/s) with UDP (MCS1). . . . . . . . . . . . . . . . . . . . 3-215
Table 4-1: AMR potential coverage gains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Table 4-2: Supported AMR codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Table 4-3: BSS parameters used to determine MS threshold and hysteresis . . . . . . . . . . . . . . . . 4-19
Table 4-4: Handover and power control - Full and Half Rate default values . . . . . . . . . . . . . . . . 4-22
Table 4-5: Backhaul configuration based on parameter settings . . . . . . . . . . . . . . . . . . . . . . 4-36
Table 4-6: Call placement on terrestrial backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Table 4-7: {23769} Voice call mapping on the backhaul for a 64K RTF . . . . . . . . . . . . . . . . . . 4-37
Table 5-1: Transmit configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Table 5-2: BBH capability for Horizon II macro Site Controller . . . . . . . . . . . . . . . . . . . . . 5-17
Table 5-3: BBH capability for Horizonmacro Site Controller . . . . . . . . . . . . . . . . . . . . . . . 5-17
Table 5-4: CTU/CTU2 power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Table 5-5: CTU/CTU2 power requirements for M-Cell cabinets . . . . . . . . . . . . . . . . . . . . . 5-22
Table 5-6: Site connection requirements for M-Cell2 and M-Cell6 . . . . . . . . . . . . . . . . . . . . 5-27
Table 5-7: Horizon II macro XMUX expansion requirements . . . . . . . . . . . . . . . . . . . . . . . 5-33
Table 5-8: Horizon II mini only network XMUX expansion requirements . . . . . . . . . . . . . . . . . 5-34
Table 5-9: Horizon II macro as master - Horizon II mini as expansion XMUX requirements . . . . . . . . 5-34
Table 5-10: M-Cell6 as master - Horizon II mini as expansion XMUX requirements . . . . . . . . . . . . 5-34
Table 5-11: Horizonmacro FMUX expansion requirements . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Table 6-1: BSC maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table 6-2: Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Table 6-3: Other parameters used in determining GPROC and link requirements . . . . . . . . . . . . . . 6-18
Table 6-4: Signalling message procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Table 6-5: BTS support for 16 kbit/s RSLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Table 6-6: Number of BSC to BTS signalling links (without LCS) . . . . . . . . . . . . . . . . . . . . 6-25
Table 6-7: Backhaul requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
Table 6-8: Number of MSC and BSC signalling links without LCS (20% utilization) . . . . . . . . . . . . 6-44
Table 6-9: Number of MSC and BSC signalling links without LCS (40% utilization) . . . . . . . . . . . . 6-45
Table 6-10: Number of BSC to RXCDR signalling links . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
Table 6-11: Typical call parameters relating to XBLs . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53
Table 6-12: GPROC type/function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62
Table 6-13: KSWX/DSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-89
Table 6-14: KSWX/DSWX (redundant). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-90
Table 7-1: RXCDR maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Table 7-2: KSWX/DSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
xxii 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning List of Tables
Table 7-3: KSWX/DSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

Table 8-1: VersaTRAU backhaul recommendations for a given number of PDTCHs . . . . . . . . . . . . 8-8
Table 8-2: Expected throughput/TS and coding schemes (conservative) . . . . . . . . . . . . . . . . . . 8-9
Table 8-3: Expected throughput/TS and coding schemes (aggressive) . . . . . . . . . . . . . . . . . . . 8-10
Table 8-4: BSS upgrade in support of GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Table 8-5: Recommended maximum BSS parameter values (part A) . . . . . . . . . . . . . . . . . . . 8-13
Table 8-6: Recommended maximum BSS network parameter values (part B) . . . . . . . . . . . . . . . 8-15
Table 8-7: Recommended maximum BSS network parameter values (part C) . . . . . . . . . . . . . . . 8-16
Table 8-8: Provisioning goals (per PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Table 8-9: Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
Table 8-10: Local Timeslot Zone Level capacity 4MS/PDTCH . . . . . . . . . . . . . . . . . . . . . . 8-44
Table 8-11: PRP Board Service Level Capacity 4MS/PDTCH . . . . . . . . . . . . . . . . . . . . . . 8-44
Table 8-12: Maximum MTBR in UL/DL per multislot capability . . . . . . . . . . . . . . . . . . . . . 8-47
Table 8-13: Gb entities and identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51
Table 9-1: Busy hour demand and number of carriers . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Table 9-2: Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . . . . . . . . 9-6
Table 9-3: Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . . . . . . . . 9-7
Table 9-4: Customer ordering guide 1800 MHz (Horizon II macro indoor) . . . . . . . . . . . . . . . . 9-10
Table 9-5: Customer ordering guide 1800 MHz (Horizon II macro indoor) . . . . . . . . . . . . . . . . 9-11
Table 9-6: GPROCs required at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Table 9-7: BSC timeslot requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Table 9-8: Equipment required for the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Table 9-9: Equipment required for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Table 9-10: Typical LCS call model parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
Table 11-1: Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Table 11-2: Sample statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Table 12-1: Equip. required for 4 or 8 carrier omni with HCUs and air combining . . . . . . . . . . . . . 12-26
Table 12-2: Equipment required for 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . . . . 12-28
Table 12-3: Equipment required for 2 sector 3/3 or 6/6 with DHUs . . . . . . . . . . . . . . . . . . . . 12-30
Table 12-4: Equip. req. for 2 cab, 2 sctr 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . . 12-31
Table 12-5: Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs . . . . . . . . . . . . . . . . . . 12-33
Table 12-6: Equip. req. for 2 cab, 3 sctr 4/4/4 or 8/8/8 with HCUs and air comb.. . . . . . . . . . . . . . 12-34
Table 12-7: Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity . . . . . . . . . . . . . 12-36
Table 12-8: Equipment required for 3 sector 2/2/2 and 2/2/2 . . . . . . . . . . . . . . . . . . . . . . . 12-38
Table 12-9: Equip. required for 4 or 8 carrier omni with HCUs and air combining . . . . . . . . . . . . . 12-41
Table 12-10: Equip. required for 6 or 12 carrier omni with DHUs. . . . . . . . . . . . . . . . . . . . . 12-43
Table 12-11: Equip. required for 2 sector 3/3 or 6/6 with HCUs. . . . . . . . . . . . . . . . . . . . . . 12-45
Table 12-12: Equip. req. for 2 cab, 2 sctr 4/4 or 8/8 with HCUs and air combining . . . . . . . . . . . . . 12-46
Table 12-13: Equip. required for 3 sector 2/2/2 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Table 12-14: Equip. req. for 2 cab, 3 sctr 4/4/4 or 8/8/8 with HCUs and air comb. . . . . . . . . . . . . . 12-49
Table 12-15: Equip. required for HP Omni-1/SP Omni-2. . . . . . . . . . . . . . . . . . . . . . . . . 12-51
Table 12-16: Equip. required for HP Omni-1/SP Omni-2. . . . . . . . . . . . . . . . . . . . . . . . . 12-53
Table 12-17: Equip. required for HP Bowtie-2/SP Bowtie-4 . . . . . . . . . . . . . . . . . . . . . . . 12-55
Table 12-18: Equip. required for HP 2 sector 1/1/SP 2 sector 2/2 . . . . . . . . . . . . . . . . . . . . . 12-57
Table 12-19: Equip. required for HP 2 sector 2/2/SP 2 sector 4/4 . . . . . . . . . . . . . . . . . . . . . 12-58
Table 12-20: Equip. required for HP 3 sector 1/1/1/SP 3 sector 2/2/2 . . . . . . . . . . . . . . . . . . . 12-59
Table 12-21: Equip. required for HP 3 sector 2/2/2/SP 3 sector 4/4/4 . . . . . . . . . . . . . . . . . . . 12-61
Table 12-22: Equip. required for Horizon II micro one cabinet config. . . . . . . . . . . . . . . . . . . 12-63
Table 12-23: Equip. required for Horizon II microthree cabinet config. . . . . . . . . . . . . . . . . . . 12-65
Table 12-24: Equip. req. for 1 cab, 4 CTU config, duplexed hybrid and air comb. . . . . . . . . . . . . . 12-68
Table 12-25: Equip req. for 1 cab., 6 CTU config, duplex dual-stage hybrid and air comb. . . . . . . . . . 12-70
Table 12-26: Equip. req. for 1 cab, 6 CTU config, duplexed dual-stage hybrid comb. . . . . . . . . . . . 12-72
Table 12-27: Equip. req. for dual cab, 12 CTU config, dplx dual-stg hybrid and air comb . . . . . . . . . 12-74
Table 12-28: Equip. req. for 1 cab., 6 CTU config, duplexed hybrid combining . . . . . . . . . . . . . . 12-76
68P02900W21-R xxiii
28 Feb 2006 GMR-01
List of Tables
Table 12-29: Equip. req. for dual cab, 12 CTU config. duplexed hybrid and air comb . . . . . . . . . . . 12-78
Table 12-30: Equip. req. for 4 cab., 24 CTU config, duplex dual-stg hybrid and air comb . . . . . . . . . 12-81
Table 13-1: Equipment required for single cabinet, 4 TCU configuration with hybrid combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Table 13-2: Equipment required for single cabinet, 4 TCU configuration with hybrid combining, diversity and
medium power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Table 13-5: Equipment required for single cabinet, 6 TCU configuration with cavity combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Table 13-6: Equipment required for single cabinet, 6 TCU configuration with cavity combining, diversity and
high power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Table 13-7: Equipment required for multiple cabinet, 8 TCU configuration with combining and diversity . . 13-24
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Table 13-9: Equipment required for single cabinet, 6 TCU configuration with combining, diversity and
Table 13-10: Equipment required for single cabinet, 6 TCU configuration with combining and diversity . . . 13-30
Table 13-11: Equipment required for single cabinet, 6 TCU configuration with combining, diversity and
medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Table 13-12: Equipment required for dual cabinet, 12 TCU configuration with air combining, diversity and
medium power duplexers (3 antenna per sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34
Table 13-13: Equipment required for multiple cabinet, 12 TCU configuration with air combining, diversity and
medium power duplexers (2 antenna per sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
Table 13-14: Equipment required for multiple cabinet, 12 TCU configuration with hybrid combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
Table 13-15: Equipment required for dual cabinet, 12 TCU configuration with 3-input CBF, hybrid combining
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Table 13-16: Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, air combining,
diversity and medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42
Table 13-17: Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, air combining,
diversity and medium power duplexers (3 antennas/sector) . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Table 13-18: Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, combining, diversity
and medium power duplexers (2 antennas/sector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46
Table 13-19: Equipment required for 3 RF cabinets, 18 TCU configuration with cavity combining, diversity
and high power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
and medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-55
and both high and medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-66
medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
xxiv 68P02900W21-R
GMR-01 28 Feb 2006
List of Tables
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-70
Table 13-30: Equipment required for single cabinet, 2 TCU configuration with diversity . . . . . . . . . . 13-74
Table 13-31: Equipment required for single cabinet, 2 TCU configuration with air combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
Table 13-32: Equipment required for single cabinet, 2 TCU configuration with diversity . . . . . . . . . . 13-77
68P02900W21-R xxv
28 Feb 2006 GMR-01
List of Tables
xxvi 68P02900W21-R
GMR-01 28 Feb 2006
About
This
Manual
System Information: BSS Equipment

Planning
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is Covered In This Manual?

The manual contains information about planning a GSM network utilizing a combination of Horizon and
M-Cell BTS equipment.
For more information about the specific content of the manual, see "Issue status of this manual" on page 2.
68P02900W21-R 1
28 Feb 2006 GMR-01
Issue status of this manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1 Manual version history
Manual
Date of issue Remarks
issue
O 03 Oct 1994 Original issue - Software Release GSR 1.2.2.x
A 30 Dec 1994 Issue A - Software Release 1.2.3.x

B 01 Sep 1995 Issue B - Software Release 1.3.0.x
C 31 May 1995 Issue C - Software Release 1.4.0.x
D 28 Mar 1997 Issue D - (also supersedes 68P02900W31-B)
E 29 Aug 1997 Issue E - includes GSM Software Release 3
F 27 Apr 1998 Issue F - includes GSM Software Release 3
G 15 Apr 2000 Issue G - includes GSM Software Release 4.1 (1.6.1.3)
H 27 Feb 2001 Issue H - includes GSM Software Release 5
J 15 Aug 2001 Issue J - includes GSM Software Release 5.1
K 15 Apr 2002 Issue K - includes GSM Software Release 6
L Not issued
M 13 Mar 2003 Issue M - includes GSM Software Release 6 (Horizon II)
N Not issued
P 11 Sep 2003 Issue P - includes GSM Software Release 7 and EGPRS
Q 15 Mar 2004 Issue Q - includes GSM Half Rate
R 4 Dec 2004 Issue R - includes GSM Software Release 8
2 68P02900W21-R
GMR-01 28 Feb 2006
Resolution of service requests
The following Service Requests are now resolved in this manual:
Table 2 Service requests resolved in this manual
Service GMR
Remarks
Request Number
1085673 01 Added recommendation for evenly distributing GSLs in
Chapter 6 Load balancing.
1098032 01 Expand on the existing planning guidelines and rules, which
predominantly assumes ‘actual data’ traffic is to be handled
by the network.
2004750 01 In Table 6-1 BSC Maximum Capacities, correct text should
read that GSR7 supports 512 DRIs.
Incorporation of CDCNs
The following CDCNs are now incorporated in this manual:

Table 3 CDCNs incorporated in this manual
GMR
CDCN Remarks
Number
00W21–002 01 Incorrect DRI Planning Limit in GSR7 68PO2900W21-Q,
GSM BSS Equipment Planning Guide.
00W21–004 01 Add guidelines to dimension PRP and PDTCH planning
with primarily GPRS signaling traffic in 68P02900W21-M
System Information: BSS Equipment Planning manual
00W21–006 01 Incorrect value of Average XBL message length.
68P02900W21-R 3
28 Feb 2006 GMR-01
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
• Motorola disclaims all liability whatsoever, implied or express, for any risk of damage, loss
or reduction in system performance arising directly or indirectly out of the failure of the
customer, or anyone acting on the customers behalf, to abide by the instructions, system
parameters or recommendations made in this manual
• 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)
or Customer Documentation Change Notices (CDCNs).
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.
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.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released
at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals,
new and amended features are tagged to help users to assess the impact on installed networks. The tags are
the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization
(RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes
the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with
page references and hot links in electronic copy.
4 68P02900W21-R
GMR-01 28 Feb 2006
General information
The tags have the format: {nnnn} or {nnnnn}

Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
New and amended feature information Tag position in text

Complete new sections of content as follows: In the heading immediately after the heading
content as follows:
• All sections under a main heading
• Main heading {nnnn}
• All paragraphs under subheadings
• Subheading {nnnn}
Single paragraphs of new or amended text. Immediately before the affected paragraph.
New or amended complete Figures and Tables After the Figure or Table number and before
the title text.
Warning, Caution and Notes. Immediately before the affected text in the
Warning, Caution or Note.
General command syntax, operator input (in On a separate line immediately above the
special fonts). affected item or immediately before the
affected item.
Computer output displays (in special fonts). On a separate line immediately above the
affected item or immediately before the
affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software
release, refer to the manual System Information: GSM Overview (68P02901W01), or to the manual System
Information: GPRS Overview (68P02903W01), or to the manual System Information: UMTS Overview
(68P02905W21).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names.
The references to external publications are shown in italics, chapter and section name cross references
are emphasised blue 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.
68P02900W21-R 5
28 Feb 2006 GMR-01
General information
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS
network is encrypted. In order to comply with the export and import requirements of particular countries,
this encryption occurs at different levels as individually standardised, or may not be present at all in some
parts of the network in which it is normally implemented. The manual set, of which this manual is a part,
covers encryption as if fully implemented. Because the rules differ in individual countries, limitations
on the encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
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 key.
6 68P02900W21-R
GMR-01 28 Feb 2006
Reporting safety issues
Reporting safety issues

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

Whenever a safety issue arises:
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (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.
68P02900W21-R 7
28 Feb 2006 GMR-01
Security Advice
Security Advice
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola systems and equipment provide configurable security parameters to be set by the operator based on
their particular operating environment. Motorola recommends setting and using these parameters following
industry recognized security practices. Security aspects to be considered are protecting the confidentiality,
integrity, and availability of information and assets. Assets include the ability to communicate, information
about the nature of the communications, and information about the parties involved.
In certain instances Motorola makes specific recommendations regarding security practices, however the
implementation of these recommendations and final responsibility for the security of the system lies with the
operator of the system.
Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone
numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution
Center contact information, from the menu located to the left of the Login box. Alternatively if you do not
have access to CNRC or the internet, contact the Local Motorola Office.
8 68P02900W21-R
GMR-01 28 Feb 2006
Warnings and cautions

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this manual and in all manuals of this
Motorola manual set.
Warnings
A definition and example follow below:
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
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.
Failure to comply with warnings
Observe all 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, or on the equipment itself, 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.
Cautions
A definition and example follow below:
68P02900W21-R 9
28 Feb 2006 GMR-01
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
Do not use test equipment that is beyond its due calibration date; arrange for
calibration to be carried out.
10 68P02900W21-R
GMR-01 28 Feb 2006
General warnings
General warnings
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following specific warnings during all phases of operation, installation and maintenance of
the equipment described in the Motorola manuals:
• Potentially hazardous voltage.
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries,
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
Warnings particularly applicable to the equipment are positioned on the equipment. 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
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into
procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must any other
warnings given in text, in the illustrations and on the equipment.
68P02900W21-R 11
28 Feb 2006 GMR-01
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment from
the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
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.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even death,
may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It
can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for
trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained
first aid or medical assistance arrives.
12 68P02900W21-R
GMR-01 28 Feb 2006
General warnings
RF radiation
High RF potentials and electromagnetic fields are present in this 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.
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• 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
• 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.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

competent responsible person must ensure that adequate lifting facilities are
available. Where provided, lifting frames must be used for these operations.
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 equipment has 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.
68P02900W21-R 13
28 Feb 2006 GMR-01
General warnings
Parts substitution
Do not install substitute parts or perform any unauthorized modification of

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with stand-by battery supplies. Use
only insulated tools.
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.
Contact your local Motorola office for how to return defective lithium batteries.
14 68P02900W21-R
GMR-01 28 Feb 2006
General cautions
General cautions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the
section Devices sensitive to static in the preface of this manual for further
information.
68P02900W21-R 15
28 Feb 2006 GMR-01
Devices sensitive to static
Devices sensitive to static

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 short circuited together, for
example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided
the leads are short circuited 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:
• Always wear an earth strap which must be connected to the electrostatic point (ESP) on the
equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace the
conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material. A cotton overall
is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work
surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic
damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and
pins, they should be transferred directly from their packing to the equipment (or the other way around) and
never left exposed on the workbench.
16 68P02900W21-R
GMR-01 28 Feb 2006
Caring for the environment
Caring for the environment

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following information is provided to enable regulatory compliance with the European Union (EU)
Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) when using Motorola Networks
equipment in EU countries.
Disposal of Motorola Networks equipment in EU countries
Please do not dispose of Motorola Networks equipment in landfill sites.

In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment is collected
and recycled according to the requirements of EU environmental law.
Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone
numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution
Center contact information, from the menu located to the left of the Login box. Alternatively if you do not
have access to CNRC or the internet, contact the Local Motorola Office.
Disposal of Motorola Networks equipment in non-EU countries
In non-EU countries, dispose of Motorola Networks equipment in accordance with national and regional
regulations.
68P02900W21-R 17
28 Feb 2006 GMR-01
Motorola manual set
Motorola manual set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
• Electronic, as fully navigable PDF files on:

◦ The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
◦ CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release,
together with current versions of appropriate hardware manuals, and has additional navigation facilities. A
snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent
point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist products such as
MARS or COP.
Ordering manuals and CD-ROMs
Use the Motorola order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
18 68P02900W21-R
GMR-01 28 Feb 2006
Manual amendment
Manual amendment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Changes to a manual that occur after the printing are incorporated into the manual using either Customer
Documentation Change Notices (CDCNs) or General Manual Revisions (GMRs).
• Small changes are published in CDCNs. These describe the changes rather than replacing large
sections of the manual. They are sent directly to customers and Motorola Local Offices and
are accessible on the Motorola Extranet.
CDCNs are numbered in sequence using the format:
◦ Shortened manual order number
◦ CDCN number
For example: 01W23-001 would be the first CDCN produced for 68P2901W23 relevant
issues are identified in the title.
• Major changes are effected by publishing a GMR. GMRs are also produced in order to
incorporate CDCNs when the numbers applying to a particular manual become significant. In
this case, the CDCNs numbers are listed in Table 3 in the issue status section of the manual.
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.
GMR availability
GMRs are published as follows:
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
◦ Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
• Motorola service web - Updated at the same time as hard copies.
• CD-ROM - Updated periodically as required.
CDCN availability
CDCNs are published as follows:
• PDF distributed electronically - Description of changes, occasionally with replacement

loose leaf pages.
• Motorola service web - Updated at the same time as hard copies.
68P02900W21-R 19
28 Feb 2006 GMR-01
Manual amendment
CDCN instructions
When a CDCN is incorporated in this manual, the record below is completed to record the amendment.
Retain the instruction sheet that accompanies each CDCN and insert it in a suitable place in this manual for
future reference.
CDCN amendment record
Record the manual insertion of CDCNs in this manual in the following table:
CDCN number Incorporated by (signature) Date
20 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
1
Introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
An overview of this manual and the various elements of a BSS and the BSS planning methodology are
provided here. Included is information about BSS system architecture, components and features that can
affect the planning stage together with information required before planning can begin.
The following topics are described:
• "Manual overview" on page 1-2
• "BSS equipment overview" on page 1-4
• "BSS features" on page 1-8
• "BSS planning overview" on page 1-19
• "Acronyms" on page 1-23
OMC-R planning is beyond the scope of this manual.

For information on installing a new OMC-R, refer to 68P02901W47, Installation and
Configuration: OMC-R Clean Install. For information on upgrading an existing OMC-R for this
software release, refer to 68P02901W74, Software Release Notes: OMC-R System.
68P02900W21-R 1-1
28 Feb 2006 GMR-01
Manual overview Chapter 1: Introduction
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:

• Chapter 1, "Introduction,".
Provides an overview of the various elements of a BSS and the BSS planning methodology.
• Chapter 2, "Transmission systems,".

This chapter provides an overview of the transmission systems used in GSM.
• Chapter 3, "BSS cell planning,".

States the requirements and procedures used in producing a BSS cell site plan.
• Chapter 4, "AMR and {22064} GSM planning,".

Provides an overview of AMR and how it is used in the Motorola system.
• Chapter 5, "BTS planning steps and rules,".

Provides the planning steps and rules for the BTS, covering the Horizon and M-Cell range of
equipment.
• Chapter 6, "BSC planning steps and rules,".

Provides the planning steps and rules for the BSC, including when LCS is used.
• Chapter 7, "RXCDR planning steps and rules,".

Provides the planning steps and rules for the RXCDR.
• Chapter 8, "PCU upgrade for the BSS,".

Provides information for the PCU upgrade to the BSS.
• Chapter 9, "Planning exercises,".

Provides planning exercises designed to illustrate the use of the rules and formulae provided in
Chapters 3, 4, 5, 6 7 and 8.
1-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Manual overview
• Chapter 10, "Location area planning,".

Provides the planning steps and rules for location area planning.
• Chapter 11, "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.
• Chapter 12, "Standard BSS and Horizon BTS configurations,"

Provides diagrams of the logical interconnections of the components in various standard
BSS and Horizon BTS site configurations.
• Chapter 13, "M-Cell BTS configurations,"

Provides diagrams of the logical interconnections of the components in various M-Cell
BTS site configurations.
68P02900W21-R 1-3
28 Feb 2006 GMR-01
BSS equipment overview Chapter 1: Introduction
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.
1-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS equipment overview
Figure 1-1 BSS block diagram
MSC A INTERFACE
LRs OMC-R
SGSN 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.
68P02900W21-R 1-5
28 Feb 2006 GMR-01
BSS equipment overview Chapter 1: Introduction
System components
The BSS can be divided into a Base Station Controller (BSC), Remote Transcoder (RXCDR), Packet Control
Unit (PCU) and one or more Base Transceiver Stations (BTSs). These can be in-built or externally located
Horizon II macro, Horizonmacro or M-Cell BTS cabinets or enclosures.
The Transcoder (XCDR) or Generic Digital Processor (GDP, EGDP or GDP2) provides 4:1 multiplexing
of the traffic and can be located at the BSC or between the BSC and MSC. When half rate is in use it may
be possible to achieve a greater reduction (refer to the transcoding sections of Chapter 6 and Chapter 7 for
a more detailed description).
When the XCDR/GDP/EGDP/GDP2 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.
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 2 (CTU2) Horizon II macro, Horizonmacro (with limitations
- see "CTU2" on page 1-6 on next page), M-Cell6
and M-Cell2 with CTU2 Adapter.
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+
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.
CTU2
In Horizon II macro, the transceiver functions are provided by the CTU2, which can be configured to
operate in single or double density mode.
This CTU2 can also be used by Horizonmacro as a CTU replacement with restrictions (see note below).
Depending on the number of CTU/CTU2s in the Horizonmacro cabinet, there are output power restrictions
that may require a mandatory 3rd power supply installed in the Horizonmacro cabinet. This may impact the
battery hold-up module in ac-powered cabinets, as the location for the 3rd power supply may mean the battery
hold-up module may have to be removed, and an external battery backup unit added. In the case where three
power supplies are required, there will be no available slots for the redundant power supply.
1-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS equipment overview
Additionally, the CTU2 can be used by M-Cell6 and M-Cell2 with a CTU2 Adapter. The M-Cell6 cabinet
may require up to three power supplies when used with CTU2s. The M-Cell2 cabinet may require up to two
power supplies when used with CTU2s.
Description and planning rules for the CTU2 are provided in Chapter 5 of this manual. Configuration
diagrams are shown in Chapter 12. The receivers can support receive diversity.
CTU2s do not support the use of CCBs. A CTU2 cannot be CCB equipped and will not act as a
full replacement/swap for the CTU. The CTU2 will only act as a CTU replacement in the
non-controller/standby controller mode. Contact your Motorola Local Office for details.
When installed in Horizonmacro, the CTU2 only supports baseband hopping in single density
mode.
CTU
In Horizonmacro, the transceiver functions are provided by the CTU. Description and planning rules for
the CTU are provided in Chapter 5 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 5 of this manual. Configuration
diagrams are shown in Chapter 13. The receivers can support receive diversity.
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.
68P02900W21-R 1-7
28 Feb 2006 GMR-01
BSS features Chapter 1: Introduction
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.
• Diversity.
• Frequency hopping.
• Short message, cell broadcast.
• Code storage facility processor.
• Packet Control Unit (PCU) for General Packet Data Service (GPRS) upgrade.
• Enhanced-GPRS (EGPRS).
• Adaptive Multi-Rate (AMR).
• {22064} GSM Half Rate
• Location services (LCS)
• {22322} BSC Reset Management (BRM)
• {23769} VersaTRAU backhaul for EGPRS
• {23956} Quality of Service (QoS)
• {26987} Increase SDCCH per cell
• {28075} Improved Timeslot Sharing (ITS)
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.
1-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS features
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:
• Synthesizer hopping requires the use of wideband (hybrid) combiners for transmit combining,
while baseband hopping does not.
• Baseband hopping requires the use of one transceiver for each allocated frequency, while
synthesizer hopping does not.
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:
• Hybrid combining must be used; cavity combining is not allowed when using synthesizer
hopping.
• The output power available with the use of the hybrid combiners must be consistent with
coverage requirements.
• It is only necessary to provide as many 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:
• The number of transceivers must be equal to the number of transmit (or receive) frequencies
required.
• Use of either remote tuning combiners or hybrid combiners is acceptable.
• Frequency redefinition procedures were incomplete in the Phase 1 GSM specifications; this
is addressed in the Phase 2 GSM procedures, but at this time there are no Phase 2 MSs
capable of implementing this. Consequently, calls could be dropped, if a single transceiver
fails, due to the inability to inform the MSs.
68P02900W21-R 1-9
28 Feb 2006 GMR-01
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
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.
PCU for GPRS upgrade
The PCU hardware provides GPRS functionality and is considered as part of the BSS equipment.
GPRS introduced packet data services 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.
1-10 68P02900W21-R
GMR-01 28 Feb 2006
Enhanced-GPRS (EGPRS)
The Enhanced Data Rates for Global Evolution (EDGE) enhances the data throughput of the GPRS to enable
the Enhanced-GPRS (EGPRS) system. The planning guide takes into account the larger data capacity of the
system dependent on the expected EGPRS usage.
The EGPRS feature is an extension to the software architecture introduced by the General Packet Radio
Service (GPRS) feature, and the Coding Scheme 3 / Coding Scheme 4 feature. This means that a network
supporting EGPRS will also provide support for GSM voice and GPRS data. The following are some
of the features included with EGPRS:
• EGPRS employs a new set of GSM modulation and channel coding techniques that increase
a user’s packet data throughput from a maximum of 21.4 Kbps per air timeslot with GPRS
to a maximum of 59.2 Kbps per air timeslot with EGPRS
• The maximum data throughput for a multi-slot mobile utilising all eight air timeslots with
EGPRS is 473.6 Kbps compared to 171.2 Kbps in GPRS.
• The initial release of EGPRS provides support for a multi-slot mobile using 4 downlink and
2 uplink air timeslots.
• Support for the mobile classes, which dictate the multi-slot capabilities of a mobile, will be the
same for EGPRS as in GPRS (classes 1-12).
Although a large portion of the EGPRS impact to the BSS software is focused on the air interface, impacts
also exist on the terrestrial interfaces to carry the large volume of data traffic produced by these new data rates.
The data rates used here are theoretical values.
Adaptive Multi-Rate (AMR)
The AMR feature provides enhanced speech quality by adapting the speech and channel coding rates
according to the quality of the radio channel, and can provide increased capacity by allocating half rate
channels to some or all mobiles. AMR selects the optimum channel rate (full rate (fr) or half rate (hr)) and
codec mode (speech and channel bit rates) to provide the best combination of speech quality and system
capacity. The feature may be tuned by the network operator on a cell by cell basis in order to obtain the best
balance between quality and capacity.
AMR may be introduced using current hardware components, or it may utilize new hardware which further
enhances the benefits of AMR.
Due to the increased processing requirements of AMR, the existing GDP (which currently supports 30 voice
channels (and data services)) can only support 15 AMR voice channels. Two GDPs are therefore “paired" in
order to support a full E1’s worth of channels (30). This results in an overall reduction in transcoding shelf
(or cage) capacity — 30 channels per GDP pair.
68P02900W21-R 1-11
28 Feb 2006 GMR-01
The AMR program introduces new transcoder equipment (the GDP2), capable of supporting 60 voice (AMR
or non-AMR) channels, hence reducing footprint. The existing RXU shelf has only 1 E1 connection per
transcoder slot, hence the GDP2 will only support 30 channels when used in this configuration. A new RXU
shelf (RXU3) and BSSC cabinet (BSSC3) have been introduced in order to fully utilize the added capacity.
When using the GDP2 within the new RXU3 shelf in a non-MSI slot, enhanced capacity mode
(see below) must be enabled in order to access the second E1.
The GDP2 may be used to full capacity in the existing BSU shelf, which has no associated
E1 limitation.
The existing hardware also only supports 16 kbit/s switching on the backhaul between the BSC and BTS.
Therefore, when using existing switching hardware, each half rate equipped RTF must have an additional two
64 kbit/s timeslots equipped in order to fully utilize all 16 half rate channels. The existing hardware will
also support only 16 kbit/s switching on the backhaul between the BSC and RXCDR, requiring 16 kbit/s
per voice channel (as it does currently).
The Double Kiloport Switch (DSW2) has been introduced to address this. The DSW2 supports double the
number of ports (enhanced capacity mode) when used in the RXCDR, as well as subrate switching capability
down to 8 kbit/s (extended subrate switching mode). With 8 kbit/s switching between the BSC and BTS, a
half rate voice stream can be carried in a 8 kbit/s subchannel, rather than the 16 kbit/s subchannel required
with KSWs. This eliminates the need for the 2 additional 64 kbit/s timeslots required per half rate capable
RTF. There is one exception, which is when the 7.95 kbit/s half rate codec mode is included in the Half Rate
Active Codec Set. This codec mode requires 16 kbit/s backhaul, thus mandating the extra backhaul resources.
The Half Rate Active Codec Set is provisioned on a per cell basis.
Prior to AMR (and the use of half rate), all channels between the BSC and RXCDR (referred to as the Ater
interface) required 16 kbit/s Ater channels, which were assigned during initialization/reconfiguration. With
AMR, when a half rate traffic channel is assigned, the voice stream may utilize a 8 kbit/s channel (depending
upon the codec modes employed). The DSW2 benefit of 8 kbit/s subrate switching allows this capability to
be realized. In order to maximize Ater channel usage, dynamic assignment of BSC to RXCDR channels is
employed. The BSC can assign a 8 or 16 kbit/s channel as required, based upon the backhaul in use across
the BSC-BTS interface. This allows the operator to equip fewer channels than previously possible, with the
assumption that a number of calls will always be utilizing half rate backhaul.
Extended range cells

AMR is only supported on the normal range timeslots. It is not supported on extended range timeslots.
Intra-cell handovers are supported between the two types of timeslots with the restriction that an AMR call on
a normal timeslot will have to handover to EFR/FR on the extended range timeslot. Handovers in the opposite
direction can handover to AMR (based on the preferences in effect at the time).
1-12 68P02900W21-R
GMR-01 28 Feb 2006
GSM Half Rate
{22064}
GSM half rate offers enhanced capacity over the air interface, corresponding to the proportion of mobiles
within a coverage area that supports half rate. An air timeslot is split into two sub-channels, each containing a
half rate channel. Speech quality is considered inferior to other speech codecs but has a high penetration level
(of GSM HR capable mobiles) due to its early introduction into the standards. Due to these large penetration
levels it is considered a viable option for high density areas.
GSM half rate may be introduced using current hardware components, or it may utilize new hardware
which further enhances the benefits of this feature. The new hardware is described in detail in "Adaptive
Multi-Rate (AMR)" on page 1-11.
The GDP and GDP2 boards are enhanced to support GSM HR, thus providing 30 and 60 channels of
transcoding capability, respectively. The current RXU shelf has only 1 E1 connection per transcoder slot,
hence the GDP2 will only support 30 channels when used in this configuration. The new RXU shelf (RXU3)
and BSSC cabinet (BSSC3), are used to utilize the full capacity.
The backhaul between the BTS and BSC may be 8kbps or 16kbps. 8kbps requires that subrate (8K) switching
is present at the BSC.
The existing hardware only supports 16 kbit/s switching on the backhaul between the BSC and BTS.
Therefore, when using existing switching hardware, each half rate equipped RTF must have an additional two
64 kbit/s timeslots equipped in order to fully utilize all 16 half rate channels. The existing hardware will also
support only 16 kbit/s switching on the backhaul between the BSC and RXCDR (this interface is called the
Ater interface), requiring 16 kbit/s per voice channel (as it does currently).
The Double Kiloport Switch (DSW2) supports subrate switching capability down to 8 kbit/s (extended
subrate switching mode), as well as double the number of ports (enhanced capacity mode) when used in the
RXCDR. With 8 kbit/s switching between the BSC and BTS, a half rate voice stream can be carried in a 8
kbit/s subchannel, rather than the 16 kbit/s subchannel required with KSWs. This eliminates the need for
the 2 additional 64 kbit/s timeslots required per half rate capable RTF.
As with AMR half rate, a GSM half rate call can fit within an 8kbps timeslot (an Ater channel) on the
terrestrial resource from the BSC to the RXCDR, rather than the 16kbps timeslot required for full rate calls. If
a percentage of the active calls can be assumed to be half rate, then efficiency can be gained by reducing
the number of terrestrial resources between the BSC and RXCDR. The DSW2 benefit of 8 kbit/s subrate
switching allows this capability to be realized. In order to maximize Ater channel usage, dynamic assignment
of BSC to RXCDR channels is employed. The BSC can assign an 8 or 16 kbit/s channel as required, based
upon the backhaul in use across the BSC–BTS interface. This allows the operator to equip fewer channels than
previously possible, with the assumption that a number of calls will always be utilizing half rate backhaul.
This dynamic allocation is an enhancement to the existing Auto Connect mode feature, referred to as
“Enhanced Auto Connect mode”. Enhanced Auto Connect is applicable to both AMR and GSM half rate.

GSM half rate is only supported on the normal range timeslots. It is not supported on extended range
timeslots (it is envisaged that the C/I ratio in the extended range portion of an extended range cell will not be
good enough to support a half rate call).
68P02900W21-R 1-13
28 Feb 2006 GMR-01
Location services (LCS)
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:
• Signal measurements
• 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.
1-14 68P02900W21-R
GMR-01 28 Feb 2006
LCS architecture
The LCS architecture may be one of the following:
• NSS-based.
The serving mobile location centre (SMLC) is connected to a MSC instead of a BSC. The
MSC acts as relay point for LCS signalling between the SMLC and BSC.
• BSS-based.
The serving mobile location centre (SMLC) is connected to a BSC instead of a MSC. The LCS
signalling between the SMLC and BSC goes directly between these two entities.
{22322} BSC Reset Management
BSC Reset Management (BRM) provides the capability for fast failover of the BSC for certain types of
equipment failure. This minimizes the BSS outage, typically reducing the downtime from 10 - 20 minutes to
less than 2 minutes for most occurrences.
In order to make use of this feature, the BSC must be equipped with a redundant secondary
BSP GPROC3.
{24347} Advanced Speech Call Item
The Advanced Speech Call Item (ASCI) features one option enhanced Multi-level Precedence and
Pre-emption (eMLPP).
{24347} Enhanced Multi-level Precedence and Pre-emption

With the enhanced Multi-level Precedence and Pre-emption (eMLPP) feature, operators can provide
preferential services to special users with higher priority such as police and medical personnel during
emergency situations and high priority subscribers.
68P02900W21-R 1-15
28 Feb 2006 GMR-01
With the eMLPP feature, two functions are supported:

• Pre-emption - the Motorola BSS will support resource pre-emption based on a full set of
A-interface priority levels and procedures as defined in 3GPP TS 48.008 and enhancements
based on priority are also provided. Resources of lower priority calls can be pre-empted to
allow higher priority calls to go through. Pre-emption is supported in the following procedures:
◦ CS point-to-point call:
- New call set-up.
- External handovers.
- Internal imperative handovers.
- Call switchover by which calls do not necessarily need to be terminated due to a

single failure on the linkset between an RXCDR–BSC or due to MSC indicated
CIC changes.
The following types of resource pre-emption are supported:

◦ TCH
◦ Ater channel
◦ Queue block
• Priority Protection of switchable PDTCH Resources.
• eMLPP priority support - BSS supports eMLPP priority between the MSC and MS.
{23769} VersaTRAU backhaul for EGPRS
VersaTRAU reduces EGPRS backhaul costs by taking advantage of statistical multiplexing that can be
achieved when packing variable size radio blocks, to be sent over PDTCHs on a carrier, into one large TRAU
frame associated with the carrier. Analysis of the RF conditions of current GPRS networks and predictions for
EGPRS indicate that the average maximum throughput per EGPRS TS will not use the entire DS0 (that is,
reach MCS9). The following are some of the key features included with VersaTRAU:
• VersaTRAU allows the backhaul for an EGPRS capable carrier to be dynamically provisioned
in terms of 64kbps terrestrial timeslots (DS0s).
• Statistics are provided to the operator to measure the backhaul utilization for an EGPRS
capable carrier to detect whether the backhaul is under/over provisioned.
• Traffic from all PDTCHs on a carrier is packed efficiently into a Versachannel of one or more
terrestrial timeslots associated with this carrier. Versachannel is defined as the portion of the
backhaul associated with an RTF that is used to carry TRAU frames associated with the air
timeslots configured as a PDTCH. New TRAU frame formats are introduced to carry the
multiplexed data blocks over the Versachannel.
All EGPRS capable carriers use VersaTRAU frame formats on the backhaul after introduction of VersaTRAU.
If Half Rate (GSM/AMR) is enabled on an EGPRS carrier, in order to maximize the backhaul utilization,
the 16 kbit/s switching format for the half rate calls is not supported on the backhaul and 8 kbit/s switching
(requiring DSWs) has to be used.
1-16 68P02900W21-R
GMR-01 28 Feb 2006
{23956} Quality of Service
With the Quality of Service (QoS) feature, operators are able to enter into varying levels of Service Level
Agreements with end users that guarantee both different probabilities of access to the network and different
throughputs once the network is accessed. Admission and retention control based Allocation/Retention
priority (ARP), are provided for Interactive and Background traffic classes. QoS for conversational and
streaming traffic classes is not supported, however, conversational and streaming traffic will be allowed into
the GPRS network and downgraded to Interactive class and is not subject to further downgrade or pre-emption.
The QoS feature allows operators to charge premium rates for the highest quality of service classes and thus to
focus the resources of their network to their revenue generating customers. The provision of focused QoS
classes will ensure that subscribers receive the best possible service specific to the types of applications they
use and also specific to the type of tariff that they choose to pay for.
QoS dimensioning
The two most significant factors that influence quality of a service are:
• Delay
• Throughput
In R99 and beyond, four traffic classes are defined to accommodate the need for different levels of these
factors for different applications. These are:
• Conversational
• Streaming
• Interactive
• Background
The BSS has internally defined additional traffic classes created by grouping similar PFC characteristics. The
internally defined traffic classes are:
• Short-Term Non-Negotiated Traffic (STNNT)
• Pre-admission PFC (PAP)
• QoS Disabled
Due to the fact that the specification for conversational and streaming is still evolving, the BSS is
implementing differentiation of service among interactive and background traffic classes. Requests to create
packet flows for streaming or conversational mode are treated as interactive traffic flows. Support for
streaming or conversational traffic class at the BSS is limited in its scope, that is, streaming and conversational
traffic classes will get QoS of interactive traffic class when admitted. The BSS however, does not make any
guarantees regarding sustaining applications using the streaming and conversational traffic classes.
68P02900W21-R 1-17
28 Feb 2006 GMR-01
QoS impacts on BSS

The QoS feature impact the following BSS entities:
• Gb interface
PFM procedures over the Gb interface are defined in 48.018 as CREATE_BSS_PFC,
MODIFY_BSS_PFC, DOWNLOAD_BSS_PFC, DELETE_BSS_PFC and their corresponding
ACKs and NACKs. In addition, the support for optional PFI IE in UL_UNITDATA and
DL_UNITDATA PDUs is also dictated by the support for PFM procedures.
• PDTCH planning
To allow QoS to reserve the appropriate amount of throughput per cell, the PDTCH formula in
Chapter 3, "BSS cell planning," has been updated to reflect the QoS design. The updated
equations provide the cell with appropriate amount of throughput for QoS
subscribers based on the input to the formulas.
• PDTCH assignment to PRP

The formula for assigning PDTCHs to a PRP has been updated
to allow subscribers with QoS to have the necessary throughput reserved at the PRP. The
formulas use the operator configurable parameters for MTBR for each Traffic Class and
Coding Scheme usage to determine the maximum number of PDTCHs to assign to a PRP.
{28075} Improved Timeslot Sharing
The Improved Timeslot Sharing feature supports EGPRS on DD CTU2 and retains no HW changes of CTU2,
BSS SW and HII FW allow each CTU2 to be able to rapidly switch between Double Density modulation
(GMSK) and Single Density modulation (8PSK). The power output is not affected for GMSK and 8PSK. In
that way, the EGPRS PDTCH can only be configured on Carrier A of DD CTU2 while the corresponding
timeslots on the paired Carrier B have to be blanked out. Although the feature of ITS does not double the
voice capacity per CTU2, compared with EGPRS on single Density Mode CTU2 it offers more channels to
service voice users with EGPRS service in parallel.
1-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS planning overview
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:
• Traffic model and capacity calculations.
• Category of service.
• Site planning.
Traffic model and capacity calculations

The following information is required to calculate the capacity required:
• Traffic information (Erlangs/BTS) over desired service area.
• Average traffic per site.
• Call duration.
• Number of handovers per call.
• Ratio of location updates to calls.
• Ratio of total pages sent to time in seconds (pages per second).
• Ratio of intra-BSC handovers to all handovers.
• LCS usage.
• Number of TCHs.
• Half Rate (AMR or {22064} GSM) usage.
• Ratio of SDCCHs to TCHs.
• Link utilization (for C7 MSC to BSS links).
• SMS utilization (both cell broadcast and point to point).
• Expected (applied and effective) GPRS load.
68P02900W21-R 1-19
28 Feb 2006 GMR-01
BSS planning overview Chapter 1: Introduction
{24347} eMLPP impact on BSS equipment and capacity calculations

With eMLPP feature, preferential service will be given to higher priority calls by pre-empting resource from
lower priority calls when system is under congestion. When planning radio and terrestrial resources, the
adequate resources need to be planned by treating all calls equal without considering preemption. That is,
BSS planning focuses on providing planning steps and rules under normal traffic load without congestion,
with certain capacity margin planned for traffic surge or congestion, such as link provisioning based on 25%
or 35% or 40% signalling link utilization, or processor provisioning based on 70% utilization.
Therefore, BSS equipment planning disregards the eMLPP feature and capacity or equipment calculation
formula will not be updated for eMLPP feature.
Category of service
The following information is required to decide what category of service is required:
• 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.
• Grade of service of the trunks between MSC/BSC, typically Erlang B at 1%.
• Grade of service of the traffic channels (TCH) between MS and BTS, typically Erlang B at 2%.
• Cell grid plan, a function of:

◦ Desired grade of service or acceptable level of blockage.
◦ Typical cell radio link budget.
◦ Results of field tests.
1-20 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS planning overview
Site planning
The following information is required to plan each site.
• Where the BSC and BTSs will be located.
• Local restrictions affecting antenna heights, equipment shelters, and so on.
• Number of sites required (RF planning issues).
• Re-use plan (frequency planning) omni or sector:

◦ Spectrum availability.
◦ Number of RF carrier frequencies available.
◦ Antenna type(s) and gain specification.
• Diversity requirement. Diversity doubles the number of Rx antennas and associated equipment.
• Redundancy level requirements, determined for each item.
• Supply voltage.
68P02900W21-R 1-21
28 Feb 2006 GMR-01
BSS planning overview Chapter 1: Introduction
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.
5. Plan the Packet Control Unit (PCU) for the desired packet data capacity for the system.
1-22 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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
{22404} ALM Advanced load management
AMR Adaptive multi-rate
ARFCN Absolute radio frequency channel number
{23956} ARP Allocation/retention priority
ARQ Automatic repeat request
{24347} ASCI Advanced speech call item
ATB All trunks busy
BBH Baseband hopping
BCCH Broadcast control channel
BCS Block check sequence
BCU Base controller unit
{23956} BE Best effort
BER Bit error rate
{23956} BG Back ground
BHCA Busy hour call attempts
BIB Balanced line interface board
BLER Block error rate
{22322} BRM BSC reset management
BSC Base station controller
BSP Base station processor
BSS Base station system
BSSC(n) Base station system control (n = 2 or 3)
Cont.
68P02900W21-R 1-23
28 Feb 2006 GMR-01
Acronyms Chapter 1: Introduction
Table 1-2 Acronym list (Continued)

Acronym Meaning
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
CIC Circuit identity code
CIR Committed information rate
CLKX Clock extender
CN Core network
CP Call processing
cPCI Compact PCI
CPU Central processing unit
CRC Cyclic redundancy check
CS(n) Channel coding scheme (number)
CSFP Code storage facility processor
CTU Compact transceiver unit
CTU2 Compact transceiver unit 2
DARBC Dynamic allocation of RXCDR to BSC circuits
dB Decibel
DCF Duplexed combining bandpass filter
DDF Dual stage duplexed combining filter
DCS Digital cellular system
DECT Digital enhanced cordless telephony
DDM Dual density mode
DHU Dual hybrid combiner unit
Cont.
1-24 68P02900W21-R
GMR-01 28 Feb 2006

Acronym Meaning
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
DSW2 Double kiloport switch
DSWX Double kiloport switch (extender)
DTE Data terminal equipment
DTRX Dual transceiver module
DTX Discontinuous transmission
DUP Duplexer
DYNET Dynamic network
e Erlang
E1 32 channel 2.048 Mbps span line
EAC Enhanced auto-connect
EDGE Enhanced data rates for global evolution
EFR Enhanced full rate
EGDP Enhanced generic digital processor
EGPRS Enhanced-GPRS
EGSM Enhanced global system for mobile communication
{22404} ELM EGSM layer management
E-OTD Enhanced observed time difference
{24347} eMLPP Enhanced multi-level precedence and pre-emption
FACCH Fast access control channel
FEC Forward error correction
FHI Frequency hopping index
FM Fault management
FMUX Fibre optic multiplexer (Horizonmacro)
Cont.
68P02900W21-R 1-25
28 Feb 2006 GMR-01

Acronym Meaning
FN Frame number
FOX Fibre optic multiplexer (M-Cell)
fr Full rate referring to the channel rate
FR Frame relay, or full rate referring to the speech codec
FTD File transit delay
FTP File transfer protocol
GBL (or GbL) Gb link
GCLK Generic clock
GDP(2) Generic digital processor (2)
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(n) Generic processor (n = 1, 2 or 3)
GPRS General packet radio system
GPS Global positioning by satellite
GSM Global system for mobile communication
{22064} GSM half rate GSM Half Rate (GSM half rate speech version 1)
feature
GSN GPRS support node
GSR GSM software release
HCOMB Hybrid combiner
HCU Hybrid combining unit
HDLC High level data link control
HDSL High bit rate digital subscriber line
HIISC Horizon II macro site controller
HPM High power mode
hr Half rate (AMR {22064} or GSM), referring to the
channel rate
HR Half rate (AMR {22064} or GSM), referring to the
speech codec
HSC Hot swap controller
Cont.
1-26 68P02900W21-R
GMR-01 28 Feb 2006

Acronym Meaning
HSN{23956} I Hopping sequence number interactive
IADU Integrated antenna distribution unit
{22404} IMRM Intelligent multi-layer resource management
IMSI International mobile subscriber identity
INS In service
IP Internet protocol
IPL Initial program load
IR Incremental redundancy
ISDN Integrated services digital network
ISI Inter symbol interference
ISP Internet service provider
KSW(X) Kiloport switch (extender)
LA Link adaptation
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
Cont.
68P02900W21-R 1-27
28 Feb 2006 GMR-01

Acronym Meaning
MPROC Master processor
MS Mobile station
MSC Mobile switching centre
MSI(-2) Multiple serial interface (2)
{23956} MTBR Minimum throughput budget requirement
MTL MTP transport layer link
MTP Message transfer part
NE Network element
NIU Network interface unit
NPM Normal power mode
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
OMC-R Operations and maintenance centre - radio
OMF Operations and maintenance function
OML Operations and maintenance link
OOS Out of service
OPL Optimization link
PACCH Packet associated control channel
PAGCH Packet access grant channel
{23956} PAP Pre-admission PFC
PAR Peak to average ratio
PBCCH Packet broadcast control channel
PCCCH Packet common control channel
PCH Paging channel
PCI Peripheral component interconnect
PCM Pulse code modulation
Cont.
1-28 68P02900W21-R
GMR-01 28 Feb 2006

Acronym Meaning
PCMCIA Personal computer memory card international
association
PCR Preventive cyclic retransmission
PCS Personal communication system
PCU Packet control unit
PDCCH Packet dedicated control channel
PDN Packet data network
PDP Packet data protocol
PDTCH Packet data traffic channel
PDU Protocol data unit
{23956} PFC Packet flow context
{23956} PFM Packet flow management
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
PSK Phase shift keying
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
QOS (or QoS) Quality of service
RACH Random access channel
RAM Random access memory
RAN Radio access network
RAT Radio access technology
Cont.
68P02900W21-R 1-29
28 Feb 2006 GMR-01

Acronym Meaning
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
SB Stealing bit
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
SDM Single density mode
SFH Synthesizer frequency hopping
SGSN Serving GPRS support node
SID Silence descriptor
SLS Signalling link selection
SM Session management
SMLC Serving mobile location centre
SMS Short message service
SNDCP Sub network dependent convergence protocol
SS7 CCITT signalling system number 7
{23956} STNNT Short-term non-negotiated traffic
STP Shielded twisted pair
Cont.
1-30 68P02900W21-R
GMR-01 28 Feb 2006

Acronym Meaning
SURF Sectorized universal receiver front end
(Horizonmacro)
SURF2 Sectorized universal receiver front end 2 (Horizon
II macro)
TBF Temporary block flow
TCCH Timing access control channel
TCH Traffic channel
TCP Transmission control protocol
TCU Transceiver control unit
TDM Time division multiplexing
TDMA Time division multiple access
TMSI Temporary mobile subscriber identity
TOA Time of arrival
TRAU Transcoder rate adaptation unit
TS Timeslot
TSW Timeslot switch
TX (or Tx) Transmit
UE User equipment
UL Uplink
UMTS Universal mobile telecommunication system
USF Uplink state flag
UTP Unshielded twisted pair
UTRAN UMTS radio access network
VAD Voice activity detection
{23769} VersaTRAU Versatile transcoder rate adaptation unit
WAN Wide area network
WAP Wireless access protocol
XBL Transcoder to BSS link
XCDR Transcoder board
XMUX Expansion multiplexer (Horizon II macro)
68P02900W21-R 1-31
28 Feb 2006 GMR-01
1-32 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
2
Transmission systems
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following topics are described:

• "BSS interfaces" on page 2-2
• "Interconnecting the BSC and BTSs" on page 2-4
• "Network topology" on page 2-6
• "Managed HDSL on micro BTSs" on page 2-26
68P02900W21-R 2-1
28 Feb 2006 GMR-01
BSS interfaces Chapter 2: Transmission systems
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) SGSN
OML (X.25)
GDS
Gb OPTION A
Gb OPTION C
PCU
X.25
CBL (LAPB)
CBC
2-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS interfaces
Table 2-1 BSS interfaces
Interface From/To Signalling by ... Rate Using ...

Air MS - BTS RACH, SDCCH, LAPDm
SACCH, FACCH
E1 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
68P02900W21-R 2-3
28 Feb 2006 GMR-01
Interconnecting the BSC and BTSs Chapter 2: Transmission systems
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 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:
• The BSC may share MSI boards between BTSs. When there are two or more E1 circuits, at
least two MSIs are recommended for redundancy.
• A minimum of one MSI is required at each BTS.
• The maximum number of active carrier units is determined by available E1 circuit capacity.
Typically, a carrier unit requires two 64 kbit/s timeslots on an E1 circuit. A RTF may be
configured as half rate capable, meaning it may support AMR half rate and/or {22064} GSM
half rate. Once a RTF is configured as AMR half rate capable, and (if AMR half rate is
enabled) the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set or
(for either AMR half rate or {22064} GSM half rate) 8 kbit/s subrate switching is not available
(for example, 16kbit/s is used for the backhaul), then the carrier unit assigned to that RTF will
require four 64 kbit/s timeslots on the E1 circuit (see Note below).
In a redundant connection, each carrier unit requires two 64 kbit/s timeslots on two different
E1 circuits. Four 64 kbit/s timeslots are required if the half rate exception case applies. The
AMR half rate exception case is defined as “A carrier which is assigned a RTF configured as
(AMR or {22064} GSM) half rate capable, and 8 kbit/s subrate switching is not available (for
example, 16kbit/s is used for the backhaul), or (for AMR) the 7.95 kbit/s half rate codec mode
is included in the Half Rate Active Codec Set".
The Half Rate Active Codec Set is AMR specific and is configured on a per cell basis.
• At the BSC, one E1 circuit is required to connect to a daisy chain. If the connection is a closed
loop daisy chain, two E1 circuits are required. To provide redundancy, the two E1 circuits
should be terminated on different MSIs.
2-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Interconnecting the BSC and BTSs
• 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 shelf 15 slot 16 port B or shelf 15 slot 14 port A or
shelf 14 slot 16 port A.
When discussing the BSC or RXCDR, “cage" is a legacy term used in BSS
commands that has been replaced by “shelf" in this manual. i.e. Cage and shelf
mean the same thing.
• Additional backhaul bandwidth is required to support GPRS traffic using CS3/CS4 coding
schemes. Each timeslot, on a CS3/CS4 capable carrier, will require 32 kbit/s for a total of four
64 kbit/s timeslots on the E1 circuit, irrespective of the speech coding.
• Additional backhaul bandwidth is required to support EGPRS traffic using MCS1-MCS9

coding schemes. Each non-signalling timeslot, {23769} will share the Versachannel backhaul
associated with the particular carrier and backhaul should be provisioned based on expected
EGPRS usage and recommendation in Table 8-1 in Chapter 8, "PCU upgrade for the BSS,".
Versachannel is defined as the portion of the RTF backhaul that is used to carry the data for
the air timeslots configured as PDTCHs at any given time.
The following rules must be observed when interconnecting InCell and M-Cell equipment:
• Reconfigure the InCell BTS to have integral sector(s) in the cabinet.
• Install M-Cell cabinet(s) to serve the remaining sector(s).
• Daisy chain the M-Cell E1 links to the BSC.
68P02900W21-R 2-5
28 Feb 2006 GMR-01
Network topology Chapter 2: Transmission systems
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 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:
• Six serial interfaces supported at a Horizon II macro BTS.
• Six serial interfaces supported at a Horizonmacro BTS.
• Two serial interfaces supported at a Horizonmicro2 / Horizoncompact2 BTS.
• Six serial interfaces supported at an M-Cell6 BTS.
• Four serial interfaces supported at an M-Cell2 BTS.
• Two serial interfaces supported at an M-Cellcity / M-Cellcity+ BTS.
• Ten BTS(s) in a path, including the terminating BTS for E1 circuit.
• Six RSL signalling links per Horizon II macro BTS site (maximum of four per path).
• Six RSL signalling links per Horizonmacro or M-Cell BTS site (maximum of two per path).
2-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Network topology
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).
Star connection
A star connection is defined by installing E1 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.
68P02900W21-R 2-7
28 Feb 2006 GMR-01
An E1 circuit provides for one signalling link, plus either:

• Fifteen GSM voice carriers,
• Fifteen CS1/CS2 GPRS carriers,
• Seven CS3/CS4 carriers,
• Three {23769} or more EGPRS carriers {23769} (depending on the backhaul configured for
each of these carriers if VersaTRAU is enabled), or
• Some proportionate mix of GSM, GPRS and EGPRS.
The number of carriers on an E1 circuit is reduced by 1 for each carrier to which

the half rate exception case applies.
The half rate exception case is defined in "Interconnecting the BSC and BTSs"
on page 2-4 earlier in this chapter.
Daisy chain connection
Daisy chaining multiple BTS sites together can better utilize the 64 kbit/s timeslots of one E1 circuit
from the BSC. Daisy chaining the sites together provides for the efficient utilization of the E1 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
2-8 68P02900W21-R
GMR-01 28 Feb 2006
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.
Daisy chain planning
The introduction of multiple E1 circuits and branches increases the complexity of the network topology. Since
the network can have multiple E1 circuits, branches, multiple paths over the same E1 circuit, and closed
loop interconnections, each E1 circuit should be individually planned.
Simple daisy chain

A daisy chain with no branches and a single E1 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 BTS 4 BTS X

CONNECTION ONLY
Rx Tx Rx Tx
The capacity of a closed loop single E1 circuit daisy chain is the same as that for a 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.
The following equation determines the number of E1s required for a daisy chain:
68P02900W21-R 2-9
28 Feb 2006 GMR-01
{23769}
_ _
Where: is:
NBSC - BTS the minimum number of E1
links required (rounded up to an
integer).
nEGPRS the total number of carriers in the
daisy chain with EGPRS enabled.
nCGPRS the total number of carriers in the
daisy chain with GPRS CS3 &
CS4 enabled.
nTGPRS the total number of carriers in
the daisy chain with GPRS CS1
& CS2 enabled and GSM voice
only carriers where the half rate
exception case does not apply.
{23769} RTF_DS0_COUNTi Value of rtf_ds0_count for the
RTF.
nTAHRE the total number of GSM voice
only carriers in the daisy chain
where the half rate exception
applies.
b the number of BTS sites in the
chain.
Example
A daisy chain with 3 BTSs, each with 1 GSM voice carrier, 1 CS3/4 enabled carrier and 1 EGPRS enabled
carrier. Half rate exception case does not apply. The number of E1s required {23769} (assuming VersaTRAU
is restricted - RTF_DS0_COUNT = 8 for each EGPRS RTF and all EGPRS RTFs are non-BCCH):
Two E1s would be required to support the daisy chaining between the BTSs to the BSC.
2-10 68P02900W21-R
GMR-01 28 Feb 2006
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 branc
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 circuits. In a closed loop, which requires redundant signalling links for each
BTS site, with an open branch, the E1 circuit to the branch needs to carry redundant signalling links.
Aggregate Abis
This is an option designed to allow greater flexibility when network planning. It can also help reduce leasing
costs of E1 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 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 link, greatly
under utilizing each link capacity.
Now, providing the geographical locations of the sites and distances of the E1 links work out advantageously,
it is possible to send all the traffic channels for every site initially over one E1 link to the third party
multiplexer and then distribute them over much shorter distances to the required sites.
68P02900W21-R 2-11
28 Feb 2006 GMR-01
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
Figure 2-8 Example using a switching network
BSC
MORE EFFICIENT USE OF

LONGEST E1 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 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
2-12 68P02900W21-R
GMR-01 28 Feb 2006
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 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.
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 ALGORITHM
BSC
1 RSL1 6 RSL2
2 RTF1 7 RTF3 13 RSL3
3 RTF1 8 RTF3 13 RTF5
4 RTF2 9 RTF4 02 RTF5
ALLOCATION 92
5 RTF2 10 RTF4 UNAFFECTED RTF6
8 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
BTS 1 MULTIPLEXER BTS 3
1 RSL1 ALLOCATION AFFECTED
2 RTF1
TWO CARRIER 3 RTF1 NEW
ONE RSL ALGORITHM ORIGINAL
4 RTF2 ALGORITHM
5 RTF2
1 RSL2 13 RSL4
2 ALLOCATION
RTF3 ALLOCATION 13 RTF7 UNAFFECTED
NEW 3 RTF3 AFFECTED 02
ALGORITHM 4 RTF7
RTF4 92 RTF8
5 RTF4 8 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.
68P02900W21-R 2-13
28 Feb 2006 GMR-01
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.
2-14 68P02900W21-R
GMR-01 28 Feb 2006
Alarm reporting
This feature has an impact on the alarm reporting for the E1 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 link.
There may also be a case where the internal links within the E1 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 switching network
BSC
E1
MULTIPLEXER E1
MULTIPLEXER
BTS BTS
BTS BTS
BTS BTS BTS
BTS
E1
MULTIPLEXER E1
MULTIPLEXER
BTS BTS BTS BTS
68P02900W21-R 2-15
28 Feb 2006 GMR-01
Restrictions/limitations
The ability to nail path timeslots along a link containing an E1 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 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).
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. A RTF may be assigned different paths. The path is the route which
the two (or four for the half rate exception case) 64 kbit/s timeslots assigned to the transceiver from the E1
link, take to get to and from the BTS/BSC. Each RTF can be assigned a different path for its two (or four)
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 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 alternative
configuration, where if one RTF path fails will still allow call processing to continue via the other path,
though with reduced capacity. This configuration only requires four timeslots instead of eight, as required
for Figure 2-11.
Double the number of timeslots required for RTFs to which the half rate exception case applies.
2-16 68P02900W21-R
GMR-01 28 Feb 2006
The customer has to weigh up the cost saving advantages of the alternative configuration against the reduced
capacity in the event of failure of a RTF path.
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
68P02900W21-R 2-17
28 Feb 2006 GMR-01
16 kbit/s RSL
The 16 kbit/s RSL reduces the transmission costs between the BSC and BTS (Abis interface) for single
carrier sites in particular.
Prior to the introduction of the 16 kbit/s RSL, a single carrier BTS required three E1 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 being 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 using KSW switching.
In a similar manner, when the single carrier is half rate capable and 16 kbit/s backhaul is used (8 kbit/s
switching is unavailable or (for AMR) the 7.95 codec rate is included in the half rate active codec set for
that cell), this feature reduces the number of required E1 64 kbit/s timeslots from five to four. (This is not
shown in the table and figures.)
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.
2-18 68P02900W21-R
GMR-01 28 Feb 2006
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.
68P02900W21-R 2-19
28 Feb 2006 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 ASSOCIATED ASSOCIATED
16 kbit/s RSL 16 kbit/s RSL 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-20 68P02900W21-R
GMR-01 28 Feb 2006
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
ASSOCIATED ASSOCIATED ASSOCIATED ASSOCIATED
16 kbit/s RSL 16 kbit/s RSL 16 kbit/s RSL 16 kbit/s RSL
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.
68P02900W21-R 2-21
28 Feb 2006 GMR-01
Planning constraints
The following RSL planning constraints apply:
• A BTS supports either 16 kbit/s RSLs or 64 kbit/s RSLs, not both.
• A BSC supports both 16 kbit/s and 64 kbit/s RSLs.
• A BSU based BTS supports up to six 16 kbit/s RSLs.
• Up to six 16 kbit/s RSLs are supported by Horizon II macro and Horizonmacro.
• Up to two 16 kbit/s RSLs are supported by Horizonmicro2 / Horizoncompact2.
• Up to six 16 kbit/s RSLs are supported by M-Cell6.
• Up to four 16 kbit/s RSLs are supported by M-Cell2.
• Up to two 16 kbit/s RSLs are supported by M-Cellmicro and M-Cellcity.
• The BTS and BSC supports a mix of both fully equipped and sub-equipped RTFs.
• A ROM download is carried out over a 64 kbit/s RSL, even at a site designated a 16 kbit/s RSL.
• A CSFP download utilizes a 16 kbit/s RSL at a 16 kbit/s designated site.
• The 16 kbit/s RSL is only able to be configured on CCITT sub-channel 3 of a 64 kbit/s

E1 timeslot for BSU based sites.
• An associated 16 kbit/s RSL is supported on redundant RTF paths where one exists on
the primary path.
16 kbit/s XBL
The 16 kbit/s XBL 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 64 kbit/s timeslot to enable them to be used as TCHs. A BSC may interconnect
with up to ten RXCDRs and vice-versa. Up to 20 XBL links total may be deployed in any configuration.
There is no restriction on which timeslot a XBL can be configured.
It is possible to select a rate of 16 kbit/s or 64 kbit/s on a 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.
2-22 68P02900W21-R
GMR-01 28 Feb 2006
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 9 XBL XBL
BSC 10 XBL XBL
MAXIMUM OF TWO XBLs BETWEEN THE BSC AND XCDR OF EITHER 64 kbit/s OR 16 kbit/s
ON THE E1 LINK.
MAXIMUM OF TEN BSCs CONNECTED TO AN RXCDR OR VICE VERSA.
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.
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.
68P02900W21-R 2-23
28 Feb 2006 GMR-01
Backwards compatibility mode
Backwards compatibility mode cannot be used in conjunction with the AMR or {22064} GSM
half rate features. Auto-connect or enhanced auto-connect mode must be specified.
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.
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. Now, 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.
2-24 68P02900W21-R
GMR-01 28 Feb 2006
Enhanced auto-connect (EAC) mode

EAC mode allows for per call allocation of RXCDR to BSC circuits (Ater channels). There are some issues
that the operator should consider when planning and provisioning the BSC/RXCDR network.
EAC mode is introduced with the AMR feature and applies also to the {22064} GSM half rate feature and
takes advantage of the use of half rate traffic channels where only 8 kbit/s backhaul to the RXCDR is
required. EAC mode is operator enabled across a BSC — RXCDR interface and only provides benefits
when the RXCDR is equipped with any number of EGDPs or GDP/GDP2s, and the BSC and RXCDR are
populated exclusively with DSW2s (no KSWs).
When in EAC mode, a CIC no longer has a fixed position on the Ater interface. Rather, a CIC may be thought
of as belonging to a pool of CICs where a separate pool is maintained for each RXCDR connected to the BSC.
When a call is assigned to a CIC, the BSC will allocate an Ater channel that goes to the same RXCDR as
the assigned CIC. One implication of such a “pooling" is that the number of CICs equipped that go through
the RXCDR may not be the same as the number of Ater channels from the BSC to the RXCDR. As in
auto-connect mode, XBL links are required between the BSC and RXCDR.
Equipping less than 16 kbit/s in Ater capacity per equipped CIC relies upon a percentage of the calls to be
utilizing half rate backhaul. If that assumption proves not to be true, some capacity will be lost due to CICs
being unuseable due to lack of Ater resources (if CIC — Ater provisioning is equal (16 kbit/s Ater capacity
per CIC), EAC mode is not required and the system will automatically revert to auto-connect mode even if
EAC is enabled). EAC mode also requires XBL bandwidth. Use of EAC mode (specifically the provisioning
of fewer Ater channels than CICs) is best considered when BSC — RXCDR backhaul costs are a concern.
If the operator chooses to equip a higher number of CICs than there are Ater channels to handle all CICs,
the possibility exists that a call assignment may fail because no Ater channels are available. To prevent
such assignments from failing, the BSC provides a facility that will automatically block at the MSC, all
idle CICs that go through a particular RXCDR when the number of available Ater channels to RXCDR
reaches a configurable threshold. The operator controls such thresholds via the cic_block_thresh and
cic_unblock_thresh values. These thresholds are used to maintain Ater resources, to ensure that resources
will be available when a fault occurs and also to balance the call load.
For AMR, when the 7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec
Set, 16 kbit/s backhaul is required. This is provisioned on a per cell basis and should be taken into
consideration when provisioning Ater resources.
68P02900W21-R 2-25
28 Feb 2006 GMR-01
Managed HDSL on micro BTSs Chapter 2: Transmission systems
Managed HDSL on micro BTSs

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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.
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.
Integrated HDSL interface
HDSL cable selection

The cabling needs to comply with the following selection guidelines:
• Correct number of pairs for an application.
• Each tip and ring pair must be of a twisted construction.
• The tip and ring must not be mixed between the pairs, that is, tip1 must not be used as a
pair with ring 2.
• Either unshielded twisted pair (UTP) or shielded twisted pair (STP) may be used.
• The cable gauge should be between 0.4 mm and 0.91 mm (AWG 26 to AWG 19).
• Attenuation at 260 kHz should be less than 10.5 dB/km.
• Cable runs should be limited to a length depending on the product.
2-26 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Managed HDSL on micro BTSs
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:
• Unshielded twisted pair
◦ BT CW1308 and equivalents.
◦ Category 3 UTP.
◦ Category 4 UTP.
◦ Category 5 UTP.
• Shielded twisted pair

◦ Category 3 STP.
◦ Category 4 STP.
◦ Category 5 STP.
The performance of some types of cable is known to be unacceptable for HDSL applications.
The following cable types should be avoided:
• Twisted quad cable is unsuitable for use in HDSL applications and must not be used.
• Drop wire that consists of two parallel conductors with supporting steel cable. This will
work with HDSL but because it is not twisted, it provides little immunity from noise, and
is therefore not recommended.
• Information cable is typically of non-twisted, multicore construction, for example ribbon

cable. Its use is not recommended.
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:
• The conductor pair(s) should be connected point-to-point only, not point to multipoint.
• The use of different gauges of cable in one link should be avoided.
• Bridge taps in the cable run should be avoided.
• Loading coils in the cable run must be removed.
• The isolation between tip and ring should be greater than 1 Mohm (at SELV voltage levels).
• The isolation between tip and earth should be greater than 1 Mohm (at SELV voltage levels).
• The isolation between ring and earth should be greater than 1 Mohm (at SELV voltage levels).
68P02900W21-R 2-27
28 Feb 2006 GMR-01
HDSL range
HDSL range is affected by many factors which should be taken into account when planning the system.
• Microcell systems can have longer distances, typically 2 km or so, because of their different
link error requirements.
• The following factors will reduce the available distances:

◦ Bridge gaps add unwanted loads on to the cables.
◦ Gauge changes add unwanted signal reflections.
◦ Small gauge cables increase the signal attenuations.
◦ Other noise sources.

HDSL is specified not to affect other digital subscriber link systems and voice traffic.
However, standard E1 traffic will affect (and be affected by) HDSL systems
running in the same cable binder, if unshielded from each other.
2-28 68P02900W21-R
GMR-01 28 Feb 2006
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-16).
Figure 2-16 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
MODEM
Horizonmicro2 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.
68P02900W21-R 2-29
28 Feb 2006 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-17 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-17 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-18 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-18 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
2-30 68P02900W21-R
GMR-01 28 Feb 2006
E1 link
In Figure 2-19 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-19 Microcell configuration using E1/HDSL links
E1 LINK HDSL HDSL

S M S M
Horizonmicro2 Horizonmicro2 Horizonmicro2
BSC
68P02900W21-R 2-31
28 Feb 2006 GMR-01
2-32 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
3
BSS cell planning
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
When planning a mobile telephone system, the aim is to create a communications network that fulfils
the following requirements:
• Provides the desired capacity.
• Offers good frequency efficiency.
• Implemented at low cost.
• High grade of service.
These requirements, when analyzed, actually conflict with one another. Therefore the operating network is
always a solution achieved through compromise.
The cost of different network configurations can vary considerably. From an engineering point of view it
would be worthwhile using the most frequency efficient solutions despite their high cost, but a mobile
telephone network is so huge an investment that the financial factors are always going to limit the possibilities.
The effect of limited funds is particularly obvious when the first stage of the network is being built.
Consequently, economical planning is a condition for giving the best possible service from the start.
The use of the GSM900, EGSM900 and DCS1800 frequency bands create many propagation-based problems.
Because the channel characteristics are not fixed, they present design challenges and impairments that
must be dealt with to protect MS telephone users from experiencing excessively varying signal 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.
68P02900W21-R 3-1
28 Feb 2006 GMR-01
Managed HDSL on micro BTSs Chapter 3: BSS cell planning
When planning a network there are a number of major factors which must be considered to enable the overall
system requirements to be met. These are described in the following topics:
• "Planning tools" on page 3-3
• "GSM frequency spectrum" on page 3-4
• "Traffic capacity" on page 3-8
• "Adaptive multi-rate (AMR)" on page 3-10
• {22064} "{22064) GSM Half Rate" on page 3-14
• "Propagation effects on GSM frequencies" on page 3-17
• "Frequency re-use" on page 3-44
• "Overcoming adverse propagation effects" on page 3-51
• "Subscriber environment" on page 3-104
• "The microcellular solution" on page 3-109
• "Frequency planning" on page 3-113
• "{22879} Inter-radio access technology (2G-3G) cell reselection and handovers" on page 3-119
• "Call model parameters for capacity calculations" on page 3-122
• "Control channel calculations" on page 3-125
• "GPRS/EGPRS traffic planning" on page 3-151
• "GPRS/EGPRS network traffic estimation and key concepts" on page 3-152
• "GPRS/EGPRS air interface planning process" on page 3-180
3-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
• Type of terrain.
• Environment.
• Heights of antennas.
It can perform the necessary number of calculations needed to give an accurate picture of the propagation
paths of the cell.
Several planning tools are available on the market, such as Netplan or Planet, and it is up to the users to
choose the tool(s) which suit them best.
After calculation and implementation of the cell, the figures should then be checked by practical
measurements. This is because, with all the variable factors in propagation modelling, an accuracy of
80% would be considered excellent.
68P02900W21-R 3-3
28 Feb 2006 GMR-01
GSM frequency spectrum Chapter 3: BSS cell planning
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-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
Uplink range 1710 MHz - 1785 MHz.

Downlink range 1805 MHz - 1880 MHz.
This provides 374 ARFCNs with a frequency separation of 95 MHz between uplink 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 T-mobile operate exclusively in the DCS1800 range while the other two, Vodafone and O2
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
T-mobile T-mobile
1721.5MHz 1816.5MHz
Vodafone/O2 Vodafone/O2
1710MHz 1805MHz
68P02900W21-R 3-5
28 Feb 2006 GMR-01
GSM frequency spectrum Chapter 3: BSS cell planning
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). When AMR half rate or {22064} GSM half rate
are enabled, each timeslot is divided into 2 sub-channels, each of which is capable of supporting speech.
The maximum number of RF carriers at any one BTS site is 24 for Horizon II macro, Horizonmacro and
M-Cell6. Therefore the maximum number of physical channels available at a BTS site is 24 x 8 = 192.
When AMR or {22064} GSM half rate is used, each half rate enabled carrier can support a maximum of
16 physical channels.
Figure 3-2 Eight TDMA timeslots per RF carrier
0 1 2 3 4 5 6 7
Maximum 24 carriers for

BTS Horizonmacro and M-Cell6
Maximum 25 carriers for BTS6
Modulation techniques and channel spacing
The modulation technique used in GSM are Gaussian minimum shift keying (GMSK) and 8-Phase Shift
Keying (PSK).
GMSK is used for voice, circuit switched data and GPRS. 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 modulations used in EGPRS are GMSK and 8-PSK. 8-PSK is a multi-level modulation in which 3 bits
are mapped onto a symbol. The symbols are grey coded for reducing the number of bits in error between
adjacent symbols. The 8-PSK signal is then filtered to ensure GSM spectrum mask is preserved. This
filter is a linearised GMSK pulse, that is, the main component in a Laurant decomposition of the GMSK
modulation (see 3GPP TS 05.04 V8.4.0).
3-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning GSM frequency spectrum
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 (8-PSK posseses
approximately the same spectrum mask) 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.
68P02900W21-R 3-7
28 Feb 2006 GMR-01
Traffic capacity Chapter 3: BSS cell planning
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.
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.
3-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Traffic capacity
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.
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: is:
C 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.
68P02900W21-R 3-9
28 Feb 2006 GMR-01
Adaptive multi-rate (AMR) Chapter 3: BSS cell planning
Adaptive multi-rate (AMR)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to AMR
AMR offers two very strong benefits:

• Expands air interface capacity, via AMR Half Rate.
• Expands the area of high call quality coverage, via AMR Full Rate.
The ability of the AMR codec to dynamically change the allocation of source and channel coding bits
provide a high level of speech quality. The overall improvements are dependant upon channel quality
(C/I). As channel quality deteriorates, a codec with a higher level of error protection (and a corresponding
decrease in speech quality) is selected, leading to an increase in sensitivity of the transceivers, thus providing
optimum performance.
The half rate (hr) ability of AMR, which allows for two calls per timeslot, provides the largest increase in
capacity, but at a cost of a decrease in voice quality. Initially the AMR capable MS penetration rate may be low,
suggesting that in circumstances where capacity is paramount and voice quality secondary that GSM half rate
be employed as an alternative. For details about GSM half rate, see "{22064) GSM Half Rate" on page 3-14.
With AMR operating in full rate mode, or in a mix of full rate and half rate where handovers between the
modes is permitted, a capacity gain can be realized as a result of being able to operate at a lower C/I threshold.
This can result in potentially higher traffic loading. Note, however, that the benefits of AMR do not extend to
the signalling channels, or to the use of non-AMR codecs and data services. Capacity gains of this type are
very dependent upon other factors (e.g. propagation conditions) and any improvement gained by a replanning
of existing systems should be considered with care.
The 3GPP document, TR 46.076, Adaptive Multi-Rate (AMR) speech codec; Study Phase Report, is a summary
of a report on AMR which contains additional information regarding the technical aspects and benefits.
3-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Adaptive multi-rate (AMR)
Capacity and coverage
AMR Half Rate doubles the number of voice calls that can be supported over the air interface, thus allowing
up to double the number of subscribers to be supported by a base station. This is achieved by halving the air
interface necessary to support a single voice call using AMR Half Rate. On the backhaul it is possible to
support 8 voice calls per E1 timeslot instead of 4 when 8 kbit/s backhaul is used (see Figure 3-4).
Figure 3-4 AMR half rate capacity increase

AMR Full Rate, Enhanced Full Rate
and Full Rate coverage area AMR Half Rate coverage area
Timeslot 1 Timeslot 2 Timeslot 3

AMR Full Rate 1 2 3 4 1 2 3 4 1 2 3 4
16 kbit/s
AMR Half Rate 123456781234567812345678
8 kbit/s
2 X voice calls supported
per timeslot in AMR Half Rate
coverage area
Quality of service
AMR Full Rate delivers improved voice quality in poorer radio environments, providing high quality in
poorer signalling conditions:
• AMR Full Rate will offer higher quality voice communications in poor radio environments such
as corporate and urban buildings where no dedicated in-building coverage has been provided.
• AMR Full Rate will improve voice quality across the entire network, by supporting high
quality voice codecs in radio environments that cannot support Enhanced Full Rate (EFR).
68P02900W21-R 3-11
28 Feb 2006 GMR-01
Adaptive multi-rate (AMR) Chapter 3: BSS cell planning
AMR Full Rate expands the area of high quality voice coverage within a cell by intelligently selecting the
best from a selection of codecs in various radio environments. Figure 3-5 shows the different profiles
of these codecs.
Figure 3-5 AMR Full Rate call quality improvements

In good radio environments: AMR Quality Improvement:
AMR Full Rate voice quality = EFR Voice Quality High voice quality in reduced radio quality
Mean Opinion
Score (MOS)
of voice 5.0
quality
4.0
3.0
EFR
12.2
10.2
2.0 7.95
7.4
6.7
5.9
5.15
4.75
1.0
No Errors C/I=16 dB C/I=13 dB C/I=10 dB C/I= 7 dB C/I= 4 dB C/I= 1 dB
Conditions
Notice that in comparison to the EFR curve, AMR Full Rate offers a significantly higher quality codec
solution in marginal radio environments (C/I = 13 to 4 dB). This, therefore, enables operators to offer high
voice quality in radio environments that will not support EFR. Note that this improvement is paramount in
urban environments, which usually have a C/I of between 11 and 13 dB.
Applications
With the flexibility of the AMR system, it is possible to customize the application of AMR to meet specific
network and service needs. Some of the potential application scenarios are identified below (in no particular
order) together with the advantages offered and the types of networks to which they may be suited.
Full rate only - High quality over full range of channel errors
Due to the robust error correction ability of AMR, this provides improved resilience to errors compared
to GSM EFR so that when in call, the speech quality varies little with channel errors. It also provides
significantly improved quality under marginal coverage conditions (e.g. at cell edge, coverage holes, etc.).
Some capacity advantage may also be derived from the improved resilience under low C/I conditions.
May support tighter frequency re-use.
Potential service applications: suitable for operators who do not need to increase capacity through half rate
operation, but wish to offer the best speech quality possible to all users.
3-12 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Adaptive multi-rate (AMR)
Half rate only - Improved quality over current HR codec

To gain maximum capacity advantage, the AMR codec can be operated in half rate channel mode only.
Potential service applications: suitable for operators who need the greatest capacity enhancement from half
rate operation. Some loss of quality at high channel error rates and in background noise can be expected.
Full and Half rate operation - HR tied to cell congestion

In this case full rate is used until cell congestion triggers a switch to use of half rate channels. The operator
may also specify a handover of half rate capable mobiles from a full rate channel to a half rate channel in
order to help ease the congestion. This provides a tuneable trade-off between call quality and capacity.
Potential service applications: suitable for operators who want to combine speech quality and capacity
improvements.
Migration to AMR half rate
When migrating a system to one which includes (AMR) half rate, care should be taken to ensure that the
call capacity rating of the various components of the system are not exceeded. Use of AMR HR improves
the spectral efficiency over the air interface (and potentially the backhaul), but from a load perspective a
half rate call has the same impact as a full rate call.
{22064} Interoperability with GSM half rate
AMR half rate and GSM half rate can coexist within a system, down to the RTF level. One sub-rate may be
operating as AMR half rate, the other as GSM half rate.
{23769} Interoperability with EGPRS
When AMR half rate is enabled on an EGPRS capable carrier (pkt_radio_type = 3) in order to maximize the
VersaTRAU backhaul utilization, only 8kbps switching on the backhaul is supported.
68P02900W21-R 3-13
28 Feb 2006 GMR-01
{22064) GSM Half Rate Chapter 3: BSS cell planning
{22064) GSM Half Rate

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to GSM half rate
GSM Half Rate offers enhanced capacity over the air interface, corresponding to the proportion of mobiles
within a coverage area that supports GSM half rate. An air timeslot is split into two sub-channels, each
containing a half rate channel. Although the speech quality is considered inferior to other speech codecs,
GSM half rate capable mobiles have a high penetration level due to its early introduction into the standards
and hence it is considered a viable option for high-density areas.
Capacity and coverage
As with AMR half rate, GSM half rate doubles the number of voice calls that can be supported over the air
interface, thus allowing up to double the number of subscribers to be supported by a base station. This is
achieved by halving the air interface capacity necessary to support a single voice call using GSM half rate. On
the backhaul it is possible to support 8 voice calls per E1 timeslot instead of 4 when 8 kbit/s backhaul is
used (see Figure 3-6).
Figure 3-6 GSM half rate capacity increase

AMR Full Rate, Enhanced Full Rate
and Full Rate coverage area GSM Half Rate coverage area
Timeslot 1 Timeslot 2 Timeslot 3

Full Rate 1 2 3 4 1 2 3 4 1 2 3 4
16 kbit/s
GSM Half Rate 123456781234567812345678
8 kbit/s
2 X voice calls supported
per timeslot in GSM Half Rate
coverage area
3-14 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning {22064) GSM Half Rate
Quality of service
The GSM half rate codec does not perform as well as the AMR half rate codec. Figure 3-7 shows the Mean
Opinion Scores (MOS) for the various coding schemes versus C/I (the 4.75 <-> 7.95 values are for AMR half
rate). This provides a relative comparison of voice quality vs. the other codecs.
Figure 3-7 GSM half rate codec comparison
4.5
EFR
4 FR
HR
3.5
7.95 kbps
MOS
3 7.4 kbps
6.7 kbps
2.5
5.9 kbps
2 5.15 kbps
4.75 kbps
1.5
1
Error 19 16 13 10 7 4
Free
C/I (dB)
Applications
GSM half rate is best suited for use when spectral efficiency is required. Two useful application scenarios
are identified below (in no particular order), together with the advantages offered and the types of networks
to which they may be suited.
GSM half rate can be controlled at cell level so can be particularly suitable to deal with high
user density clusters.
68P02900W21-R 3-15
28 Feb 2006 GMR-01
{22064) GSM Half Rate Chapter 3: BSS cell planning
Half rate only

To gain maximum capacity advantage, the GSM half rate codec can be operated in half rate channel mode
only. All qualifying calls will be placed on a half rate channel.
Potential service applications: suitable for operators who need the greatest capacity enhancement from half
rate operation. A reduction in speech quality is expected.
Full and Half rate operation - HR tied to cell congestion

In this case full rate is used until cell congestion triggers a switch to use of GSM half rate channels. The
operator may also specify a handover of half rate capable mobiles from a full rate channel to a half rate channel
in order to help ease the congestion. This provides a tuneable trade–off between call quality and capacity.
Potential service applications: suitable for operators who want to combine speech quality and capacity
improvements.
Migration to half rate
When migrating a system to one which includes (GSM) half rate, care should be taken to ensure that the call
capacity rating of the various components of the system are not exceeded. Use of GSM half rate improves
the spectral efficiency over the air interface (and potentially the backhaul), but from a load perspective a
half rate call has the same impact as a full rate call.
Interoperability with AMR half rate
GSM half rate and AMR half rate can coexist within a system, down to the RTF level. One sub-rate may be
operating as GSM half rate, the other as AMR half rate.
{23769} Interoperability with EGPRS
When GSM half rate is enabled on an EGPRS capable carrier (pkt_radio_type = 3) in order to maximize the
VersaTRAU backhaul utilization, only 8kbps switching on the backhaul is supported.
3-16 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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.
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 43 dBm and .000000001 W is -60 dBm. The path
loss can now be expressed as 103 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:
68P02900W21-R 3-17
28 Feb 2006 GMR-01
Propagation effects on GSM frequencies Chapter 3: BSS cell planning
N dB = 10 x log10(PL/RPL)
Where: is:
N 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 µW
+49 19 80 W +14 -16 25 mW -40 -70 0.1 µW
+46 16 40 W +11 -19 12.5 mW -50 -80 0.01 µW
+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.
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.
3-18 68P02900W21-R
GMR-01 28 Feb 2006
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-8, is as follows:
Where: is:
F1 the first Fresnel zone.
d1 distance from Tx antenna to the
obstacle.
d2 distance from Rx antenna to the
obstacle.
λ wavelength of the carrier wave.
d total path length.
Figure 3-8 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.
68P02900W21-R 3-19
28 Feb 2006 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-9) 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-9 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: is:
N (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.
3-20 68P02900W21-R
GMR-01 28 Feb 2006
The value of N is influenced by the following:

• 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.
• The quantity of water vapour in the atmosphere. This is extremely variable and has significant
effects on the RRI.
• Finally the temperature, pressure, and water vapour pressure have major effects on the RRI.
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.
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-10. The
aircraft mounted refractometer can give a detailed study over several paths and heights.
Figure 3-10 Measurement of the RRI
HEIGHT (km)
0 340
RRI (N)
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.
68P02900W21-R 3-21
28 Feb 2006 GMR-01
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-11A 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-11B 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-11C 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-11 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-22 68P02900W21-R
GMR-01 28 Feb 2006
Events which can modify the clear sky lapse rate

There are four main events which can modify the clear sky lapse rate and they are as follows:
• Radiation nights
This is the result of a very sunny day followed by clear skies overnight. The Earth absorbs
heat during the day and the air temperature rises. After sunset the Earth radiates heat into the
atmosphere and its surface temperature drops. This heat loss is not replaced resulting in air
closer to the surface cooling faster than air higher up. This condition causes a temperature
inversion and the RRI profile no longer has a uniform lapse rate. This effect will only occur
overland and not water as water temperature variations are over a longer period of time.
• Advection effects
This effect is caused by high pressure weather fronts moving from land to the sea or other large
expanses of water. The result is warm air from the high pressure front covering the relatively
cool air of the water. When this combination is then blown back over land a temperature
inversion is caused by the trapped cool air. It will persist until the air mass strikes high ground
where the increase in height will mix and dissipate the inversion.
• Subsidence
This occurs again in a high pressure system this time overland when air descending from high
altitude is heated by compression as it descends. This heated air then spreads over the cooler
air below. This type of temperature inversion normally occurs at an altitude of 1 km but may
occasionally drop to 100 m where it cause severe disruption to radio signals.
• Frontal systems
This happens when a cold front approaching an area forces a wedge of cold air under the
warmer air causing a temperature inversion. These disturbances tend to be short lived as the
cold front usually dissipate quickly.
Although those described above are the four main causes of RRI deviations, local pressure, humidity and
temperature conditions could well give rise to events which will affect the RRI.
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:
• Attenuation.
• Reflection.
• Scattering.
• Diffraction.
• Polarization changes.
68P02900W21-R 3-23
28 Feb 2006 GMR-01
Attenuation
This is caused by any object obstructing the wave path causing absorption of the signal (see Figure 3-12). 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-12 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-13). 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-13 Reflection
INCIDENT WAVE REFLECTED WAVE
EQUAL ANGLES
SMOOTH SURFACE, SUCH AS WATER,

VERY REFLECTIVE
AMOUNT OF REFLECTION DEPENDS ON

CONDUCTIVITY OF THE SURFACE
3-24 68P02900W21-R
GMR-01 28 Feb 2006
Scattering
This occurs when a wave reflects of a rough surface (see Figure 3-14). 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-14 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-15). The
amount of diffraction that takes place increases as the frequency used is increased.
68P02900W21-R 3-25
28 Feb 2006 GMR-01
Diffraction can be a good thing as it allows radio signals to reach areas where they would not normally
be propagated.
Figure 3-15 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
3-26 68P02900W21-R
GMR-01 28 Feb 2006
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-16 shows the effects of polarization on a transmitted signal.
Figure 3-16 Polarization
ELECTRICAL PART OF WAVE ELECTRICAL PART OF WAVE

VERTICALLY POLARIZED HORIZONTALLY POLARIZED
(CHANGED BY ELECTRICAL STORM)
ELECTRICAL STORM
Tx Rx
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.
68P02900W21-R 3-27
28 Feb 2006 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-17) and is known as Rayleigh distribution (see Figure 3-18).
Figure 3-17 Propagation effect - Rayleigh fading environment
Rx
Tx
Figure 3-18 Rayleigh distribution
SIGNAL
STRENGTH
THRESHOLD
DEEP NULLS
/ WAVELENGTH
1 2
DISTANCE
3-28 68P02900W21-R
GMR-01 28 Feb 2006
Rician environment
Where the signal path is predominantly line of sight (see Figure 3-19) with insignificant reflections or
diffractions arriving at the receiver, this is know as Rician distribution (see Figure 3-20). 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-19 Propagation effect - Rician environment
Rx
Tx
Figure 3-20 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.
68P02900W21-R 3-29
28 Feb 2006 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:
Where: is:
Pt 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.
3-30 68P02900W21-R
GMR-01 28 Feb 2006
In order to work out the power received at a normal antenna, the effective aperture (Ae) of the receiving
antenna must be calculated.
The actual received power can be calculated as follows:
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:
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:
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:
Where: is:
d 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.
68P02900W21-R 3-31
28 Feb 2006 GMR-01
The formula for calculating the plane earth loss is:
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-21). 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.
3-32 68P02900W21-R
GMR-01 28 Feb 2006
Figure 3-21 illustrates plane earth loss, taking all factors into account.
Figure 3-21 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.
68P02900W21-R 3-33
28 Feb 2006 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 four storeys in the area.
Where: is:
B(dB) 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.
3-34 68P02900W21-R
GMR-01 28 Feb 2006
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-22.
Figure 3-22 Focusing of power

ISOTROPIC RADIATOR VERTICAL DIPOLE RADIATION PATTERN
(A SPHERICAL PATTERN) (SIDE VIEW)
TRANSMITTER
68P02900W21-R 3-35
28 Feb 2006 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-23.
Figure 3-23 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: is:
i 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-36 68P02900W21-R
GMR-01 28 Feb 2006
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-24) 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-24 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.
68P02900W21-R 3-37
28 Feb 2006 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-25).
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.
3-38 68P02900W21-R
GMR-01 28 Feb 2006
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.
Figure 3-25 Okumura propagation graphs

110
922 MHz
100 h.= 320 m
h.= 220 m
90 x h.= 140 m
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
xx
40
x
xx
x
30
xxx
20 xx
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
68P02900W21-R 3-39
28 Feb 2006 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: is:
A 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: is:
Frequency range (fc) 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: is:
fc > 400 MHz.
3-40 68P02900W21-R
GMR-01 28 Feb 2006
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
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.
68P02900W21-R 3-41
28 Feb 2006 GMR-01
GSM900 path loss
Figure 3-26 and Figure 3-27 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-26 BTS antenna height of 50 m, MS height of 1.5 m (GSM900)
220
210
200 SUBURBAN
190 URBAN INDOOR
180
PATH LOSS (dB)
URBAN
170
160
150
140
130
RURAL (QUASI OPEN)
120
110
RURAL (OPEN)
100
90
1 10 100
CELL RADIUS (km)
Figure 3-27 BTS antenna height of 100 m, MS height of 1.5 m (GSM900)
220
210
200 SUBURBAN
190 URBAN INDOOR
180
PATH LOSS (dB)
URBAN
170
160
150
140
130
RURAL (QUASI OPEN)
120
110
RURAL (OPEN)
100
90
1 10 100
CELL RADIUS (km)
3-42 68P02900W21-R
GMR-01 28 Feb 2006
Path loss GSM900 vs DCS1800
Figure 3-28 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-28 Path loss vs cell radius for small cells
170
160
DCS1800
(METROPOLITAN CENTRES)
150
PATH LOSS (dB)
140
130
GSM900
120
DCS1800 (MEDIUM SIZED

110 CITIES AND SUBURBAN
CENTRES)
100
0.1 0.3 1.0 3.0
CELL RADIUS (km)
68P02900W21-R 3-43
28 Feb 2006 GMR-01
Frequency re-use Chapter 3: BSS cell planning
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 GSM/EGSM900 and DCS1800 bands
as shown below:
Frequency Band Tx Range Rx Range No. RF Carriers

GSM900 935 - 960 MHz 890 - 915 MHz 124
EGSM900 925 - 960 MHz 880 - 915 MHz 174
DCS1800 1805 - 1880 MHz 1710 - 1785 MHz 374
Within this range of frequencies only a finite number of channels may be allocated to 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-29).
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.
3-44 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Frequency re-use
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-29 Adjacent cell interference

CARRIER INTERFERING CARRIER
F 33 F 33
RECEIVE
SIGNAL
LEVEL
- 75dBm
- 100dBm
SERVING BTS INTERFERING BTS

DISTANCE
MOBILE POSITION
68P02900W21-R 3-45
28 Feb 2006 GMR-01
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-30).
Figure 3-30 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.
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.
3-46 68P02900W21-R
GMR-01 28 Feb 2006
The most common re-use pattern is 4 site with 3 cells (see Figure 3-31). 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-31 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.
68P02900W21-R 3-47
28 Feb 2006 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-32, uses a 2 site - 6 cell re-use.
Figure 3-32 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.
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:
• Power control (both BTS and MS).
• Hardware techniques.
• Frequency hopping (if applied).
• Sectorization.
• Discontinuous transmission (DTX).
3-48 68P02900W21-R
GMR-01 28 Feb 2006
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-33)
to give overall system comparison.
Figure 3-33 Carrier interference measurements

(2 CELLS USING THE SAME BCCH FREQUENCY)
C
/I CAN BE RELATED TO D/R
BS BS
R
MS
DISTANCE BETWEEN CELLS
D
ANALOGUE SYSTEM D
/R = 4.4
GSM SYSTEM D/R = 2.62
68P02900W21-R 3-49
28 Feb 2006 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.
3-50 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Overcoming adverse propagation effects
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.
68P02900W21-R 3-51
28 Feb 2006 GMR-01
Overcoming adverse propagation effects Chapter 3: BSS cell planning
There are important points to note when using this method of providing frequency hopping:
• There is a need to provide as many transceivers as the number of allocated frequencies.
• Within Horizon II macro equipment applications, the use of any type of Tx block (DUP,
HCU, DHU) is acceptable.
CCBs cannot be used with Horizon II macro equipment. Also, if Horizon II

macro CTU2s are used in Horizonmacro equipment and are controlled by a
MCUF, baseband hopping is only supported when the CTU2s are used in single
density mode.
• Within Horizonmacro equipment applications, the use of any type of Tx block (TDF, DCF,
DDF) or cavity combining blocks (CCBs) is acceptable.
• Within M-Cell equipment applications, the use of either combining bandpass filter/hybrid
or cavity combining blocks is acceptable.
• The use of remote tuning combiners, cavity combining blocks or hybrid combiners is
acceptable in BTS6 equipment applications.
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:
• 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.
• The output power available with the use of hybrid combiners must be consistent with
coverage requirements.
• 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.
3-52 68P02900W21-R
GMR-01 28 Feb 2006
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-34, are as follows:
• Speech channel encoding.
The speech information for one 20 ms full rate speech block is divided over eight GSM
bursts. The speech information for one half rate speech block is divided over four 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.
Figure 3-34 The coding process
20 ms 0.577 ms
INFORMATION INFORMATION
BLOCK BURSTS
SPEECH SPEECH
(260 BITS FULL RATE OR (8 BURSTS FULL RATE OR
ENHANCED FULL RATE, ENHANCED FULL RATE,
OR A BITS AMR) OR B BURSTS AMR)
ENCODING INTERLEAVING
CONTROL (184 BITS) CONTROL (4 BURSTS)
DATA (240 BITS) DATA (22 BURSTS)
Refer to Table 3-2 for values of A bits and B bursts on a per channel type basis.
The shaded areas indicate the channel types that are not supported.
68P02900W21-R 3-53
28 Feb 2006 GMR-01
Table 3-2 Speech channel coding
No. of speech No. of speech

Is channel type
Channel type bits delivered per bursts delivered
supported?
block (A) per block (B)
TCH/AFS12.2 Yes 244 8
TCH/AFS7.95 No 159 8
TCH/AFS5.9 No 118 8
TCH/AFS4.75 No 95 8
TCH/AHS7.95 Yes 159 4
TCH/AHS4.75 No 95 4
TCH/FS Yes 260 8
TCH/EFS Yes 244 8
{22064} TCH/HS Yes 112 4
“AFS" = AFR = AMR Full Rate (speech).

“AHS" = AHR = AMR Half Rate (speech).
{22064} “HS" = HR = GSM Half Rate (speech).
3-54 68P02900W21-R
GMR-01 28 Feb 2006
Figure 3-35 illustrates the coding process for full rate and enhanced full rate speech, control and data
channels; the sequence is very complex.
Figure 3-35 Coding process illustration (full rate and enhanced full rate speech)
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 260 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)
68P02900W21-R 3-55
28 Feb 2006 GMR-01
Figure 3-36 illustrates the coding process for AMR full rate and AMR half rate speech, control and data
channels.
Figure 3-36 Coding process illustration (AMR full rate and AMR half rate speech)
AMR SPEECH
FRAME BCCH, PCH, AGCH, SDCCH, DATA TRAFFIC RACH + SCH
"A" BITS FACCH, SACCH, CBCH 9.6/4.8/2.4 k P0 BITS
(see ) 184 BITS N0 BITS
CLASS 1a CYCLIC
CODE (6) + TAIL (4) FIRECODE + TAIL ADD IN TAIL CYCLIC CODE + TAIL
IN: "A" IN: 184 IN: N0 BITS IN: P0 BITS
OUT: "A" + 10 BITS OUT: 228 OUT: N1 BITS OUT: P1 BITS
CONVOLUTION CODE
IN: A" + 10 BITS
OUT: see
CODE PUNCTURING CONVOLUTION CODE

IN: see CONVOLUTION CODE CONVOLUTION CODE
IN: 248 BITS + PUNCTURE IN: P1 BITS
OUT (AFR): 448 BITS OUT: 456 BITS
OUT (AHR): 224 BITS IN: N1 BITS OUT: 2 x P1 BITS
OUT: 456 BITS
INBAND SIGNALLING
IN (AFR): 448 BITS TCH/2.4
IN (AHR): 224 BITS
OUT (AFR): 456 BITS
OUT (AHR): 228 BITS
DIAGONAL INTERLEAVING +
RE-ORDERING & PARTITIONING STEALING FLAG
+ STEALING FLAG IN: BLOCKS OF 456 BITS
IN: 456 BITS OUT: 22 SUB-BLOCKS
OUT: 8 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)
AFR = AMR Full Rate

AHR = AMR Half Rate
Notes to Figure 3-36:

1. Code puncturing is performed to remove some of the encoded bits. Also, for AMR Half Rate
codecs, Class 2 bits are added to the Class 1s.
2. The inband signalling bits (8 for AFR and 4 for AHR) are block-coded representations of the
codec identifier which indicates the AMR codec used for channel encoding in the forward
channel and the AMR codec requested to be used for channel encoding in the reverse channel.
3-56 68P02900W21-R
GMR-01 28 Feb 2006
Figure 3-37 illustrates the coding process for GSM half rate speech, control and data channels.
Figure 3-37 Coding process illustration (GSM HR speech, control and data)
HR EFR Speech FR Speech BCCH, PCH, AGCH, SDCCH, Data Traffic RACH + SCH
Frame Frame FACCH, SACCH, CBCH 9.6/4.8/2.4K PO Bits
112 bits
244 bits 260 bits 184 bits No Bits
Cyclic code + Cyclic code + Firecode + Add In Tail Cyclic code +

Tail Repetition Tail In: No bits Tail
In: 112 bits In: 244 bits In: 184 bits Out: N1 bits In: P0 bits
Out: 121 bits Out: 260 bits Out: 228 bits Out: P1 bits
Class 1A Cyclic
Code + Tail
In: 160 bits
Out: 267 bits
Convolution Code Convolution Code Convolution Code Convolution Code Convolution Code
In: 121 bits In: 267 bits In: 248 bits + Puncture In: P1 bits
Out: 228 bits Out: 456 bits Out: 456 bits In: N1 bits Out: 2 X P1 bits
Out: 456 bits
TCH/2.4
Re-ordering & Partitioning Re-ordering & Partitioning DIAGONAL INTERLEAVING

+ Stealing Flag + Stealing Flag STEALING FLAG
In: 228 bits In: 456 bits In: Blocks of 456 bits
Out: 4 sub-blocks Out: 8 sub-blocks Out: 22 Sub-blocks
Block Diagonal Block Diagonal Block Rectangular

Interleaving Interleaving Interleaving
In: 4 blocks In: 8 blocks In: 8 sub-blocks
Out: Pairs of blocks Out: Pairs of blocks Out: Pairs of sub-blocks 1 X RACH
1 X SCH (burst)
4 X TCH HR (bursts) 8 X TCH FR (bursts) 4 X BCCH, PCH, AGCH

8 X TCH EFR (bursts) 4 X SDCCH, SACCH
8 X FACCH/TCH (bursts) 4 X CBCH (bursts)
8 X TCH 2-4 kBits/S (bursts) 19 x TCH 9.6 kBIT/S (BURST)
68P02900W21-R 3-57
28 Feb 2006 GMR-01
Table 3-3 lists the output bits resulting from the convolutional coder and the number of punctured bits for the
different AMR codecs (see Figure 3-36). The shaded areas indicate the codec modes that are not supported.
Table 3-3 AMR codecs, convolutional output bits and punctured bits
No. of output
Is codec mode bits from No. of
Codec mode Rate
supported? convolutional punctured bits
coder
TCH/AFS12.2 Yes 1/2 508 60
TCH/AFS10.2 Yes 1/3 642 194
TCH/AFS7.95 No 1/3 513 65
TCH/AFS7.4 Yes 1/3 474 26
TCH/AFS6.7 Yes 1/4 576 128
TCH/AFS5.9 No 1/4 520 72
TCH/AFS5.15 Yes 1/5 565 117
TCH/AFS4.75 No 1/5 535 87
TCH/AHS7.95 Yes 1/2 266 78
TCH/AHS7.4 Yes 1/2 260 64
TCH/AHS6.7 Yes 1/2 240 40
TCH/AHS5.9 Yes 1/2 224 16
TCH/AHS5.15 Yes 1/3 303 91
TCH/AHS4.75 No 1/3 285 73

GSM speech channel encoding for Full Rate
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.
3-58 68P02900W21-R
GMR-01 28 Feb 2006
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.
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.
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-38 shows a diagrammatic representation of speech channel encoding.
Figure 3-38 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
68P02900W21-R 3-59
28 Feb 2006 GMR-01
GSM speech channel encoding 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:
• 50 Class 1a + 124 Class 1b + 70 Class 2 = 244 bits.
Preliminary coding:
• Add 8 bits CRC generated from 50 Class 1a + 15 most important Class 1b bits to Class 1b bits.
• Add 8 repetition bits to Class 2 bits.
Output from preliminary coding:

• 50 Class 1a + 132 Class 1b + 78 Class 2 = 260 bits.
EFR frame of 260 bits passed on for similar channel coding as Full Rate.
Figure 3-39 shows a diagrammatic representation of preliminary coding for enhanced Full Rate speech.
Figure 3-39 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-60 68P02900W21-R
GMR-01 28 Feb 2006
{22064} GSM speech channel encoding for Half Rate
The transcoded speech information is received in 20 ms speech frames, each containing 112 bits. The speech
bits are grouped depending on their importance to the intelligibility of speech.
Class 1a
The 22 most significant bits of the 95 Class 1 bits are crucial to the speech intelligibility and hence are
protected by 3 parity bits used for error detection. If there are errors in the Class 1a bits, the whole block is
usually ignored.
Class 1b
The remaining of the Class 1 bits are not parity checked but are fed together with the Class 1a and parity
bits to a convolutional encoder. Six tail bits are added which sets the registers in the receiver to a known
state for decoding purposes.
Class 2
The remaining 17 bits (of the 112 total bits) are known as the Class 2 bits and are not protected. These are
appended to the encoded Class 1 bits.
The resulting 228 bit Block is then interleaved before being sent over the air interface.
Figure 3-40 shows a diagrammatic representation of preliminary coding for GSM HR speech.
Figure 3-40 Speech Channel Encoding for GSM Half Rate Speech

TAIL
BITS
PARITY
CHECK CLASS 1a CLASS 1b
22 BITS 3 73 BITS 6
211 Convoluted Bits CLASS 2

17 BITS
228 BITS
68P02900W21-R 3-61
28 Feb 2006 GMR-01
GSM speech channel encoding for AMR Full Rate
The transcoded speech information is received in frames, each containing “X" bits, where X varies over the
different AMR Full Rate codecs (see Table 3-4 for values of X (the shaded areas indicate the codec modes
that are not supported)). The speech bits are grouped into two classes of sensitivity to errors, depending on
their importance to the intelligibility of speech.
Class 1a
Six parity bits are derived from the “Y" Class 1a bits, where Y varies over the different AMR Full Rate codecs
(see Table 3-4 for values of Y). Transmission errors within these Class 1a 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 “Z" 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. Z varies over the different AMR Full Rate codecs (see Table 3-4 for values of Z).
The convolutionally coded symbols are punctured to reduce the resulting data rate to that supported over
the air interface.
AMR codecs use a set of Systematic Recursive (SR) convolutional codes instead of the Non-Systematic
Non-Recursive (NSNR) convolutional codecs used by Full Rate and enhanced Full Rate. The SR codes
chosen for AMR are more complex and computationally expensive than the NSNR codecs for EFR and FR.
However, overall they provide better error protection.
InBand signalling
Because the utilized channel codec can vary dynamically from speech frame to speech frame (see Link
Adaptation section), InBand signalling bits are used to coordinate the codec usage between the BTS and MS.
These bits alternately indicate to the receiver which codec was used to channel encode the speech frame, and
which codec the sender would like to receive in the opposite direction.
Eight InBand signalling bits are added to the encoded and punctured Class 1a, 1b, and parity bits. The InBand
signalling bits are the block coded representation of the appropriate 2-bit codec identifier.
The encoded speech now occupies 456 bits, but is still transmitted in 20 ms, thus raising the transmission
rate to 22.8 kbit/s.
3-62 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-4 X, Y and Z bit values for AMR FR speech channel encoding
Is codec mode
Codec mode X bits Y bits Z bits
supported?
TCH/AFS12.2 Yes 244 81 163
TCH/AFS10.2 Yes 204 65 139
TCH/AFS7.95 No 159 75 84
TCH/AFS7.4 Yes 148 61 87
TCH/AFS6.7 Yes 134 55 79
TCH/AFS5.9 No 118 55 63
TCH/AFS5.15 Yes 103 49 54
TCH/AFS4.75 No 95 39 56

Figure 3-41 shows a diagrammatic representation of speech channel encoding for AMR Full Rate.
Figure 3-41 Speech channel encoding for AMR Full Rate
CLASS 1a CLASS 1b
Y BITS Z BITS
TAIL
BITS
PARITY
CHECK
Y 6 Z 4
CONVOLUTIONAL CODE
INBAND
SIGNALLING
BITS
CODE PUNCTURING
8
448
456 BITS
68P02900W21-R 3-63
28 Feb 2006 GMR-01
GSM speech channel encoding for AMR Half Rate
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 “X" bits, where X varies over the
different AMR Half Rate codecs (see Table 3-5 for values of X). The speech bits are grouped into three classes
of sensitivity to errors, depending on their importance to the intelligibility of speech.
Class 1a
Six parity bits are derived from the “Y" Class 1a bits, where Y varies over the different AMR Half Rate
codecs (see Table 3-5 for values of Y). Transmission errors within these Class 1a 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 “Z" 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. Z varies over the different AMR Half Rate codecs (see Table 3-5 for values of Z (the
shaded areas indicate the codec modes that are not supported)). The convolutionally coded symbols are
punctured to reduce the resulting data rate to that supported over the air interface.
AMR codecs use a set of Systematic Recursive (SR) convolutional codes instead of the Non-Systematic
Non-Recursive (NSNR) convolutional codecs used by half rate. The SR codes chosen for AMR are more
complex and computationally expensive than the NSNR codecs for HR. However, overall they provide
better error protection.
Class 2
The “W" Class 2 bits are not protected by any channel coding. They are simply appended to the encoded and
punctured class 1a, 1b, and parity bits. W varies over the different AMR Half Rate codecs (see Table 3-5
for values of W).
InBand signalling
Because the utilized channel codec can vary dynamically from speech frame to speech frame (see Link
Adaptation section), InBand signalling bits are used to coordinate the codec usage between the BTS and MS.
These bits alternately indicate to the receiver which codec was used to channel encode the speech frame, and
which codec the sender would like to receive in the opposite direction.
Four InBand signalling bits are added to the encoded and punctured class 1a, 1b, parity, and Class 2 bits. The
InBand signalling bits are the block coded representation of the appropriate 2-bit codec identifier.
The encoded speech now occupies 228 bits, but is still transmitted in 20 ms, thus raising the transmission rate
to 11.4 kbit/s. Note that two half rate subchannels sharing the same timeslot will have a total transmission
rate of 22.8 kbit/s.
3-64 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-5 X, Y, Z and W bit values for AMR HR speech channel encoding
Is codec
Codec mode mode X bits Y bits Z bits W bits
supported?
TCH/AHS7.95 Yes 159 67 56 36
TCH/AHS7.4 Yes 148 61 59 28
TCH/AHS6.7 Yes 134 55 55 24
TCH/AHS5.9 Yes 118 55 47 16
TCH/AHS5.15 Yes 103 49 42 12
TCH/AHS4.75 No 95 39 44 12

Figure 3-42 shows a diagrammatic representation of speech channel encoding for AMR Half Rate.
Figure 3-42 Speech channel encoding for AMR Half Rate

Y BITS Z BITS W BITS
TAIL
BITS
PARITY
CHECK
Y 6 Z 4
CONVOLUTIONAL CODE INBAND

SIGNALLING
BITS
CODE PUNCTURING 4 W
228 BITS
Link adaptation for AMR channels
The fundamental performance benefit of the AMR traffic channel is the network’s ability to dynamically
select the optimal speech and channel codec combination in reaction to the observed channel conditions.
Link adaptation is the process by which the optimal codec is selected.
68P02900W21-R 3-65
28 Feb 2006 GMR-01
A non-AMR traffic channel, such as Full Rate or Enhanced Full Rate, is permitted to use one fixed speech
and channel codec combination only. In favourable channel conditions, this provides high sound quality.
However, as the channel conditions degrade, the Bit Error Rate (BER) and Frame Erasure Rate (FER)
increase. These erased frames and bit errors significantly degrade sound quality.
Conversely, an AMR traffic channel, based on the observed channel conditions, is permitted to dynamically
select the optimal codec combination from a set of up to 4. The AMR codec combination characteristics
range from high vocoding rate / low channel coding rate to low vocoding rate / high channel coding rate. The
optimal codec combination is the one which provides the appropriate amount of voice and channel coding to
maximize the sound quality with the constraint of maintaining a maximum permitted FER level. Thus, in
any channel condition, an AMR traffic channel limits erased frames to a permitted level yet provides the
highest sound quality possible for that condition.
For example, under very good channel conditions, the AMR traffic channel chooses the codec combination
with the highest vocoding and lowest channel coding rates. Here, the minimal channel coding is sufficient
to maintain the permitted FER level. And the vocoding provides high sound quality rivalling that of EFR
operating in a good channel condition. Under poor channel conditions, the AMR channel will choose
the codec combination with the lowest vocoding and highest channel coding rates. Here, the increased
channel coding is sufficient to correct bit errors and thus maintain the permitted FER level. The decreased
vocoding provides sound quality which is noticeably less than EFR operating in a good channel condition.
However, the speech frames are not erased as they would be for EFR and FR operating under a poor channel
condition. Thus, unlike EFR and FR, intelligible voice is still communicated, just with less sound quality.
This is better than no voice at all.
Measuring channel conditions: C/I

On an AMR traffic channel, both the BTS and mobile observe and measure their respective receive channel
conditions. This measurement is converted to a carrier to interference (C/I) value. The measured C/I value is
compared to configurable C/I ranges which define when a particular codec combination (out of the set of
4) should be selected. As C/I increases into the next highest range, the link adaptation process selects the
combination with the next highest vocoding / next lowest channel coding rates. As C/I decreases into the
next lowest range, the link adaptation process selects the combination with the next lowest vocoding / next
highest channel coding rates.
Coordinating adaptation: InBand signalling

Once a codec combination is selected, it must be conveyed to the sender to instruct it to use the selected
combination in future speech transmissions. The BTS selects the optimal codec combination and instructs
the mobile to use it for subsequent uplink speech transmissions. Likewise, the mobile selects the optimal
combination and instructs the BTS to use it for subsequent downlink speech transmissions. These instructions
are conveyed using the InBand signalling bits which reside within each encoded and transmitted speech frame.
Link adaptation, or the selecting of optimal codec combinations, is performed independently and
simultaneously for the uplink and downlink channels. To coordinate these processes, two types of InBand
signalling are used. Each is sent in alternating encoded and transmitted speech frames.
• Codec Mode Indication (CMI).
• Codec Mode Command/Request (CMC/R).
The CMI indicates to the receiver which codec combination was used by the sender to encode the currently
and subsequently transmitted speech frame. Thus, the receiver can determine which combination to use in
decoding the current and next received speech frames.
3-66 68P02900W21-R
GMR-01 28 Feb 2006
The CMR indicates to the BTS which codec combination the mobile would prefer be used in downlink speech
encoding and transmission. Generally, the BTS grants this request. Similarly, the CMC indicates to the mobile
which codec combination the BTS would prefer be used in uplink speech encoding and transmission. This
command is always granted.
68P02900W21-R 3-67
28 Feb 2006 GMR-01
GSM control channel encoding
Figure 3-43 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-43 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.
3-68 68P02900W21-R
GMR-01 28 Feb 2006
GSM circuit-switched data channel encoding
Figure 3-44 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-44 Data channel encoding
DATA CHANNEL 9.6 kbit/s

240 BITS
240
TAIL
BITS
240 4
CONVOLUTIONAL CODE
488
PUNCTURE
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.
68P02900W21-R 3-69
28 Feb 2006 GMR-01
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.
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:
• Speech (full rate) - 8 blocks.
• Speech (half rate) - 4 blocks.
• Control - 4 blocks.
• Data - 22 blocks.
This process is an important one, for it safeguards the data in the harsh air interface radio environment.
Because of interference, noise, or physical interruption of the radio path, bursts may be destroyed or corrupted
as they travel between MS and BTS, a figure of 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-6) 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.
3-70 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-6 Interleaving
Transcoder Rate Adaptation Unit Number of GSM bursts the traffic

(TRAU) frame type block is spread over
Speech (full rate) 8
Speech (half rate) 4
Control 4
CS data 22
68P02900W21-R 3-71
28 Feb 2006 GMR-01
Diagonal interleaving - full rate speech

Figure 3-45 illustrates, in a simplified form, the principle of the interleaving process applied to a full rate
speech channel.
Figure 3-45 Diagonal interleaving - full rate 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-72 68P02900W21-R
GMR-01 28 Feb 2006
Diagonal interleaving - half rate speech

Figure 3-46 illustrates, in a simplified form, the principle of the interleaving process applied to a half rate
speech channel.
Figure 3-46 Diagonal interleaving - half rate speech
20 ms SPEECH SAMPLE 228 BITS 20 ms SPEECH SAMPLE 228 BITS 20 ms SPEECH SAMPLE 228 BITS
BITS 4, 12, 20, 28 ..... 225 BITS 0, 8, 16, 24 ..... 224 BITS 0, 8, 16, 24 ..... 224
MAPPED TO ODD BITS MAPPED TO EVEN BITS MAPPED TO EVEN BITS

OF BURST OF BURST OF BURST
BITS 4, 12, 20, 28 ..... 225
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 228 bits, these blocks are then divided into four 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 two blocks will be placed in the even bit positions of the first two bursts. The last two blocks will be
placed in the odd bit positions of the next two bursts.
As each burst contains 114 traffic carrying bits, it is in fact shared by two speech blocks. Each block will
share two bursts with the block preceding it, and two with the block that succeeds it, as shown. In the diagram
block 5 shares the first two bursts with block 4 and the second two bursts with block 6.
68P02900W21-R 3-73
28 Feb 2006 GMR-01
Transmission - full rate speech

Each burst will be transmitted in the designated timeslot of eight consecutive TDMA frames, providing the
interleaving depth of eight.
Table 3-7 shows how the 456 bits resulting from a 20 ms full rate speech sample are distributed over eight
normal bursts.
Table 3-7 Distribution of 456 bits from one 20 ms full rate 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 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.
3-74 68P02900W21-R
GMR-01 28 Feb 2006
Transmission - half rate speech

For half rate speech, two independent sub channels share the same air interface timeslot. While each sub
channel’s 20 ms speech sample is encoded and diagonally interleaved into its own 4 bursts separately, both
sub channels must share the physical channel at transmission time. To do this, both sub channels alternate
transmitting their associated four bursts on the air interface. Sub channel 0 transmits on the shared timeslot
during the even numbered TDMA frames, while sub channel 1 transmits during the odd numbered frames.
Table 3-8 shows how the 228 bits resulting from a 20 ms half rate speech sample are distributed over eight
normal bursts.
Table 3-8 Distribution of 228 bits from one 20 ms half rate speech sample
Distribution Burst
0 4 8 12 16 20 ..........................224 even bits of burst N
1 5 9 13 17 21 .................... . . .225 odd bits of burst N + 2
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 that FACCH, because it steals speech bursts from a subscriber channel, experiences the same
kind of interleaving as the speech data that it replaces (diagonal interleaving). However, because
the FACCH contains twice as many bits as a half rate speech block, the FACCH steals the bursts
from two encoded half rate speech blocks.
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. Because the FACCH is twice as large as
the half rate speech blocks, the FACCH steals the space of two encoded and interleaved 20 ms speech
samples. It occupies the even bits of the first two bursts, both the even and odd of the middle two bursts,
and the odd bits of the last two bursts.
68P02900W21-R 3-75
28 Feb 2006 GMR-01
Rectangular interleaving - control

Figure 3-47 illustrates, in a simplified form, the principle of rectangular interleaving. This is applied to
most control channels.
Figure 3-47 Rectangular interleaving - control
CONTROL 1 2 3 5 6
4
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.
3-76 68P02900W21-R
GMR-01 28 Feb 2006
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.
Diagonal interleaving - CS data

Figure 3-48 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.
68P02900W21-R 3-77
28 Feb 2006 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-48 shows a diagrammatic representation of diagonal interleaving for CS data.
Figure 3-48 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-78 68P02900W21-R
GMR-01 28 Feb 2006
GPRS channel coding schemes
Four different coding schemes have been defined for GPRS:

• CS1
• CS2
• CS3
• CS4
The mother code used is a half-rate convolutional coder applied to CS1 to CS3 followed by puncturing
(CS2 & CS3) leading to various effective code rates. No coding is applied to CS4.The following applies
to all four coding schemes:
• User data (RLC data block, segmented LLC PDUs) and RLC/MAC header are coded together.
• The coded bits are block interleaved over four bursts.
• Eight stealing bits (SB) are used to signal which coding scheme is used for transmission of a
block.
These are described in the following sections.
68P02900W21-R 3-79
28 Feb 2006 GMR-01
Channel coding scheme 1 (CS1)

CS1 is the most robust coding scheme of the four GPRS coding schemes. Figure 3-49 shows the encoding
of the user data (160 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (24 bits) for
downlink. In the first stage of coding, these 184 bits are protected according to Fire code using extra 40 bits
(BCS) for error detection (used in ARQ). The subsequent 224 bits are then convolutionally coded followed by
interleaving over four bursts. CS1 provides a user data rate (excluding RLC/MAC header) of 8Kbits/s.
Figure 3-49 GPRS channel coding scheme 1 (CS1)
3 bits 21 bits 160 bits 40 bits
USF RLC/MAC Header Data BCS
Block coded
4 bits
224 bits TB
Rate 1/2 convolutional coding
465 bits
Puncturing
465 bits
Block interleaving over 4 bursts
Mapped to 4 TDMA bursts; coding scheme

signalled through 8 stealing bits (2 per burst)
TB Header & data SB TS SB Header & data TB
3 bits 57 bits 1 bit 26 bits 1 bit 57 bits 3 bits
3-80 68P02900W21-R
GMR-01 28 Feb 2006

CS2 is less robust than CS1 at the expense of providing higher user data rate. Figure 3-50 shows the encoding
of the user data (240 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (34 bits) for
downlink. The USF bits (3) are pre-coded to provide additional protection. In the first stage of coding, these
274 bits are protected according to Fire code using extra 16 bits (BCS) for error detection (used in ARQ).
The subsequent 290 bits are then convolutionally coded, punctured, and interleaved over four bursts. CS2
provides a user data rate (excluding RLC/MAC header) of 12Kbits/s.
6 bits
(pre-coded) 16 bits
28 bits 240 bits
Block coded
4 bits
290 bits TB
588 bits
Puncturing
546 bits

68P02900W21-R 3-81
28 Feb 2006 GMR-01

CS3 is less robust than CS1 and CS2 at the expense of providing higher user data rate. Figure 3-51 shows
the encoding of the user data (288 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header
(30 bits) for downlink. The USF bits (3) are pre-coded to provide additional protection. In the first stage of
coding, these 318 bits are protected according to Fire code using extra 16 bits for (BCS) for error detection
(used in ARQ). The subsequent 334 bits are then convolutionally coded, punctured, and interleaved over four
bursts. CS3 provides a user data rate (excluding RLC/MAC header) of 14.4Kbits/s.
6 bits
(pre-coded) 16 bits
24 bits 288 bits
Block coded
4 bits
344 bits TB
676 bits
Puncturing
456 bits

3-82 68P02900W21-R
GMR-01 28 Feb 2006

CS4 is the least robust GPRS coding scheme; it has no FEC capability. Figure 3-52 shows the encoding of
the user data (400 bits RLC data block, segmented LLC PDUs) and the RLC/MAC header (40 bits) for
downlink. The USF bits (3) are pre-coded to provide additional protection. These 440 bits are protected
according to Fire code using extra 16 bits (BCS) for error detection (used in ARQ). The subsequent 456 bits
are then interleaved (no convolutionally coding) over four bursts. CS4 provides a user data rate (excluding
RLC/MAC header) of 20Kbits/s.
12 bits
(pre-coded) 16 bits
28 bits 400 bits
Block coded
456 bits (0 bits TB)
No convolutional coding
456 bits
No puncturing
456 bits

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.
68P02900W21-R 3-83
28 Feb 2006 GMR-01
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-9 summarizes the coding parameters for the GPRS coding schemes.
Table 3-9 Coding parameters for GPRS coding schemes
Coding scheme
CS1 CS2 CS3 CS4
Effective Code 1/2 2/3 3/4 1
rate after 1/2
convolutional
coding and
puncturing
USF 3 3 3 3
Pre-coded USF 3 6 6 12
RLC/MAC 21 28 24 28
header/bits
User bits (RLC 181 268 312 428
blocks; segmented
LLC PDUCs)
BCS 40 16 16 16
Tail 4 4 4 -
Coded bits 456 588 676 456
Punctured bits 0 132 220 0
User Dta rate at 8 12 14.4 20
RLC/MAC kbit/s
3-84 68P02900W21-R
GMR-01 28 Feb 2006
16/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-9 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.
Only one 16 kbit/s timeslot (CIC) is used between the BSC and RXCDR for a CS call, therefore
termination is necessary.
68P02900W21-R 3-85
28 Feb 2006 GMR-01
EGPRS channel coding schemes
Nine different coding schemes have been defined for EGPRS, MCS-1 to MCS-9. MCS-1 to MCS-4 coding
schemes use GMSK and MCS-5 to MCS-9 coding schemes use 8-PSK. The mother code used is a 1/3 rate
convolutional coder applied to all the coding schemes followed by various puncturing schemes leading to
various effective code rates. The following apply to all nine coding schemes:
• User data (RLC data block, segmented LLC PDUs), RLC/MAC header and the USF bits
are coded independently.
• The USF bits (3) are block coded resulting in 12 bits and 36 bits for GMSK and 8-PSK coding
schemes respectively. In case of MCS-1 to MCS-4, USF block coding is identical to CS-4.
This facilitates multiplexing of GPRS and EGPRS on the same time slot (GPRS mobiles must
be able to detect USF sent by EGPRS GMSK block).
• The mother code used is 1/3 rate convolutional encoder.
• There are three different RLC/MAC header types used, which contain information about the
coding and puncturing scheme, used for a block. Header type 1 is used for MCS-7 to MCS-9,
header type 2 is used for MCS-5 and MCS-6, and header type 3 is used for MCS-1 to MCS-4.
• Eight stealing bits (SBs) are used to signal which header type should be used to extract
various information.
• Coding schemes MCS-7 to MCS-9 are interleaved over two bursts and coding schemes MCS-1
to MCS-6 are interleaved over four bursts.
• Two or three puncturing schemes per coding scheme are used enabling Incremental
Redundancy (IR); the code combining process of radio blocks in error thus providing
additional coding gain, particularly for higher code rates.
• There are three code families, A, B, and C. The code families facilitate re-segmentation
of erroneous radio blocks into more robust coding schemes for re-transmission. Coding
schemes MCS-1 and 4 are in family C, MCS-2, 5 and 7 are in family B, and MCS-3, 6, 8
and 9 are in family A.
Hybrid ARQ type I is not supported.
These are described in the following sections.
3-86 68P02900W21-R
GMR-01 28 Feb 2006
Channel coding scheme MCS-1

MCS1 is the most robust coding scheme of the four EGPRS GMSK modulated coding schemes. Figure 3-53
shows the encoding of the user data (176 bits RLC data block, segmented LLC PDUs), the RLC/MAC header
(28 bits, header type 3) for downlink. The user data are protected by extra 12 bits (BCS) for error detection
(used in ARQ). The subsequent 196 bits (including tail bits, FBI and E bits) are then convolutionally coded,
punctured, and interleaved over four bursts. The header data are protected by extra 8 bits (HCS) for error
detection. The subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts.
MCS1 provides a user data rate (excluding RLC/MAC header) of 8.8Kbits/s.
Figure 3-53 EGPRS channel coding scheme 1 (MCS-1)
196 bits
3 bits 28 bits 8 bits 2 bits 176 bits 12 bits 6 bits
USF RLC/MAC Header HCS FBI E Data BCS TB
Block
coded Rate 1/3 convolutional coding
12 bits 108 bits 588 bits
Puncturing
P1 P2
SB = 12 12 bits 68 bits 372 bits 372 bits
Burst 1 Burst 2 Burst 3 Burst 4
68P02900W21-R 3-87
28 Feb 2006 GMR-01

MCS-2 coding scheme is less robust than MCS-1. Figure 3-54 shows the encoding of the user data (224 bits),
the RLC/MAC header (28 bits, header type 3) for downlink. The user data are protected by extra 12 bits
(BCS) for error detection (used in ARQ). The subsequent 244 bits (including tail bits, FBI and E bits) are
then convolutionally coded, punctured, and interleaved over four bursts. The header data are protected by
extra 8 bits (HCS) for error detection. The subsequent 36 bits are then convolutionally coded, punctured, and
interleaved over four bursts. MCS2 provides a user data rate (excluding RLC/MAC header) of 11.2Kbits/s.
244 bits
Block
Puncturing
P1 P2
3-88 68P02900W21-R
GMR-01 28 Feb 2006

MCS-3 coding scheme is less robust than MCS-1 and MCS-2. Figure 3-55 shows the encoding of the user data
(296 bits), the RLC/MAC header (28 bits, header type 3) for downlink. The user data are protected by extra
12 bits (BCS) for error detection (used in ARQ). The subsequent 316 bits (including tail bits, FBI and E bits)
are then convolutionally coded, punctured, and interleaved over four bursts. The header data are protected by
interleaved over four bursts. MCS3 provides a user data rate (excluding RLC/MAC header) of 14.8Kbits/s.
316 bits
Block
Puncturing
Puncturing
P1 P2 P3
SB = 12 12 bits 68 bits 372 bits 372 bits 372 bits
68P02900W21-R 3-89
28 Feb 2006 GMR-01

MCS-4 coding scheme is the least robust GMSK modulated coding scheme; it has no FEC capability.
Figure 3-56 shows the encoding of the user data (352 bits), the RLC/MAC header (28 bits, header type 3)
for downlink. The user data are protected by extra 12 bits (BCS) for error detection (used in ARQ). The
subsequent 372 bits (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and
interleaved over four bursts. The header data are protected by extra 8 bits (HCS) for error detection. The
subsequent 36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS4
provides a user data rate (excluding RLC/MAC header) of 17.6Kbits/s.
372 bits
Block
Puncturing
Puncturing
P1 P2 P3
SB = 12 12 bits 68 bits 372 bits 372 bits 372 bits
3-90 68P02900W21-R
GMR-01 28 Feb 2006

MCS-5 is the most robust coding scheme of the five EGPRS 8-PSK modulated coding schemes. Figure 3-57
shows the encoding of the user data (448 bits), the RLC/MAC header (25 bits, header type 2) for downlink.
The user data are protected by extra 12 bits (BCS) for error detection (used in ARQ). The subsequent 468 bits
(including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four
bursts. The header data are protected by extra 8 bits (HCS) for error detection. The subsequent 33 bits are
then convolutionally coded, punctured, and interleaved over four bursts. MCS5 provides a user data rate
(excluding RLC/MAC header) of 22.4Kbits/s.
468 bits
Block
36 bits 99+1 spare bits 1404 bits
No
puncturing Puncturing
P1 P2
TB Data H U SB TS SB U H Data TB
9 156 bits 12 5 1 78 1 4 13 156 bits 9

bits bits bits bit bits bit bitsbits bits
68P02900W21-R 3-91
28 Feb 2006 GMR-01

MCS-6 coding scheme is less robust than MCS-5. Figure 3-58 shows the encoding of the user data (592 bits),
the RLC/MAC header (25 bits, header type 2) for downlink. The user data are protected by extra 12 bits
(BCS) for error detection (used in ARQ). The subsequent 612 bits (including tail bits, FBI and E bits) are
then convolutionally coded, punctured, and interleaved over four bursts. The header data are protected by
interleaved over four bursts. MCS-6 provides a user data rate (excluding RLC/MAC header) of 29.6Kbits/s.
612 bits
Block
36 bits 99+1 spare bits 1836 bits
No
puncturing Puncturing
P1 P2
9 156 bits 12 5 1 78 1 4 13 156 bits 9

3-92 68P02900W21-R
GMR-01 28 Feb 2006

MCS-7 coding scheme is less robust than MCS-5 and MCS-6. It also carries two radio blocks per 20ms.
Figure 3-59 shows the encoding of the user data which consists of two separate user data blocks, 448 bits
each, the RLC/MAC header (37 bits, header type 1) for downlink. Each user data block is protected by extra
12 bits (BCS) for error detection (used in ARQ). The subsequent 468 bits per radio block (including tail bits,
FBI and E bits) are then convolutionally coded, punctured, and interleaved over two bursts. The header data
are protected by extra 8 bits (HCS) for error detection. The subsequent 45 bits are then convolutionally
coded, punctured, and interleaved over four bursts. MCS-7 provides a user data rate (excluding RLC/MAC
header) of 44.8Kbits/s.
468 bits
3 37 8 2 448 12 6 2 448 12 6
bits bits bits bits bits bits bits bits bits bits bits
USF RLC/MAC HCS FBI E Data BCS TB FBI E Data BCS TB

Header
Block
Puncturing Puncturing Puncturing
P1 P2 P3 P1 P2 P3
SB = 8 36 bits 124 bits 612 bits 612 bits 612 bits 612 bits 612 bits 612 bits
9 153 bits 15 5 1 78 1 4 16 153 bits 9

68P02900W21-R 3-93
28 Feb 2006 GMR-01

MCS-8 coding scheme carries two user data blocks similar to MCS-7. Figure 3-60 shows the encoding of the
two user data blocks, 544 bits each, the RLC/MAC header (37 bits, header type 1) for downlink. Each user
data block is protected by extra 12 bits (BCS) for error detection (used in ARQ). The subsequent 564 bits per
radio block (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved
over two bursts. The header data are protected by extra 8 bits (HCS) for error detection. The subsequent 45
bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-8 provides a user data
rate (excluding RLC/MAC header) of 54.4Kbits/s.
564 bits
3 37 8 2 544 12 6 2 544 12 6

Header
Block
P1 P2 P3 P1 P2 P3
9 153 bits 15 5 1 78 1 4 16 153 bits 9

3-94 68P02900W21-R
GMR-01 28 Feb 2006

MCS-9 coding scheme carries two user data blocks similar to MCS-7 and 8. Figure 3-61 shows the encoding
of the MCS-9 two user data blocks, 592 bits each, the RLC/MAC header (37 bits, header type 1) for downlink.
Each user data block is protected by extra 12 bits (BCS) for error detection (used in ARQ). The subsequent
612 bits per radio block (including tail bits, FBI and E bits) are then convolutionally coded, punctured, and
interleaved over two bursts. The puncturing results in MCS-9 with having no FEC protection. The header
data are protected by extra 8 bits (HCS) for error detection. The subsequent 45 bits are then convolutionally
coded, punctured, and interleaved over four bursts. MCS-9 provides a user data rate (excluding RLC/MAC
header) of 59.2Kbits/s.
612 bits
3 37 8 2 592 12 6 2 592 12 6

Header
Block
P1 P2 P3 P1 P2 P3
9 153 bits 15 5 1 78 1 4 16 153 bits 9

EGPRS traffic channels may use coding schemes MCS-1 to MCS-9. This allows the coding scheme to be
dynamically adapted to the channel conditions similar to GPRS through the Link Adaptation (LA) process
(see Link Adaptation in GPRS/EGPRS below) and thereby maximising throughput and optimising the
performance. The IR feature of EGPRS also allows the LA process to be more aggressive in terms of
BLER on the first transmissions and thereby increasing the utilisation of higher code rates over a larger
percentage of a cell.
68P02900W21-R 3-95
28 Feb 2006 GMR-01
Table 3-10 summarizes the coding parameters for the EGPRS coding schemes.
Table 3-10 Coding parameters for EGPRS coding schemes
Coding scheme: MCS-n

9 8 7 6 5 4 3 2 1
Effec- 1.0 0.92 0.76 0.49 0.37 1.0 0.85 0.66 0.53
tive
Code
rate af-
ter 1/2
convo-
lutional
cod-
ing and
punc-
turing
Effec- 0.36 0.36 0.36 1/3 1/3 0.53 0.53 0.53 0.53
tive
Header
Code
rate af-
ter 1/2
convo-
lutional
cod-
ing and
punc-
turing
Modu- 8-PSK GMSK
lation
RLC 2 2 2 1 1 1 1 1 1
blocks
per
Radio
Block
(20ms)
Raw 2x592 2x544 2x448 592 448 352 296 224 176
Data
within
one
Radio
Block
Family A A B A B C A B C
BCS 2x12 12
Tail 2x6 6
payload
Cont.
3-96 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-10 Coding parameters for EGPRS coding schemes (Continued)

Coding scheme: MCS-n
9 8 7 6 5 4 3 2 1
HCS 8
User 59.2 54.4 44.8 29.6 22.4 17.6 14.8 11.2 8.8
Data
rate at
RLC/MAC
kb/s
64 kbit/s TRAU for EGPRS
In the BSS architecture, the link which the EGPRS 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. In case of GPRS, 32 Kbits/s TRAU is used to carry CS3 and CS4. In case of
EGPRS, Table 3-10 shows that there is not enough bandwidth available on a 32 kbit/s link to carry MCS-7
to 9, therefore {23769} VersaTRAU frame formats are used to statistically multiplex the data for each air
timeslot configured as a PDTCH on the RTF backhaul available for use as Versachannel.
For EGPRS, any enabled carrier {23769} will have a certain amount (ranging from 3 - 8 DS0s) of terrestrial
backhaul configured and a portion of this backhaul will be used as the Versachannel to carry the data for the
air timeslots configured as PDTCHs. The EGPRS feature requires additional backhaul to provision EGPRS
carriers. The additional backhaul will be either 7 DS0s to implement EGPRS on a BCCH carrier or 8 DS0s to
implement EGPRS on a non-BCCH carrier, {23769} if VersaTRAU feature is restricted. If VersaTRAU feature
is unrestricted, the backhaul for an EGPRS carrier can be configured using the rtf_ds0_count parameter.
68P02900W21-R 3-97
28 Feb 2006 GMR-01
Link adaptation (LA) in GPRS/EGPRS
The Link Adaptation (LA) process is used to improve the throughput of users and system by adapting the
highest coding scheme to the prevailing radio channel condition. The development of LA algorithm is
generally based on maximising users’/system’s throughput, under the constraint of keeping the system’s
operating BLER within an acceptable bound. This ensures that the overall throughput performance is not
degraded due to the operation of higher layers protocols.
The implementation of LA is manufacturer dependant and is also mandatory. The standards provide sufficient
information and guidelines to facilitate the development of proprietary algorithms. This is achieved through
specific information elements in the various header and control messages communicated between BTS and
MS. In addition, there are various measurement reports produced by the MS that can be used as inputs to the
LA process. The actual implementation is generally based on guidelines provided by the standards and the
boundaries specified in the standards.
The LA impact in improving the system performance is greater in EGPRS compared to GPRS due to:
• Higher number of codes, i.e. better granularity.
• Richer MS measurement reports.
• Incremental redundancy (Hybrid ARQ type II).
The LA process uses the measurement reports as inputs in order to move between various codes per “packet
downlink Ack/Nack" period. In Motorola’s implementation, a code change is applied to all blocks and all time
slots that a mobile is operating at. In addition, IR is the only mode used in EGPRS, and appropriate measures
are taken to comply with the constraints specified in the standards.
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.
3-98 68P02900W21-R
GMR-01 28 Feb 2006
Discontinuous transmission (DTX)
DTX overview
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 and BTS do not transmit unnecessary message data (ie background
noise when user is not speaking). Instead, background noise information is measured and periodically
transmitted to the other user, where it is played back to generate an agreeable sounding “comfort noise".
DTX can be implemented, as necessary, on a call by call basis. The effects will be 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 often 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 and Full Rate or Enhanced Full Rate

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-62. During this time, of
the possible 104 frames, only the 4 SACCH frames and 8 Silence Descriptor (SID) frames are transmitted.
Figure 3-62 SACCH multiframe (480 ms) for DTX and Full Rate
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)
68P02900W21-R 3-99
28 Feb 2006 GMR-01
DTX and GSM Half Rate

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-63 for each sub-channel.
During this time, of the possible 104 frames, only the 4 SACCH frames and 8 Silence Descriptor (SID)
frames per sub-channel are transmitted.
Figure 3-63 SACCH multiframe (480 ms) for DTX and Half Rate
0 1 2 3 4 5 6 7.. 11 12 13 14 15 16 17 18 19 20 21 - 24 25 26 - 37 38 39 - 50 51
52 53 54 55 56 57 58 59 - 63 64 65 66 67 68 69 70 71 72 73 - 76 77 78 - 89 90 91 - 102 103
SACCH (Sub-Channel 0)
PS: In Half Rate there are 2 subchannels and in the 104
SACCH (Sub-Channel 1) Multi-frame, Sub-channel 0 and 1 are sent alternately. For
e.g. Frame 0 will have information for Sub-channel 0, 1 will
SID (Sub-Channel 0) be for Sub-Channel 1, 2 for Sub-channel 0, etc.
SID (Sub-Channel 1)
ti-GSM-HR sacch-eps-sw.
DTX and AMR Full Rate or Half Rate

Four types of DTX blocks exist for AMR channels. These blocks are transferred between the speech coder
and the channel coder. For example, in downlink DTX, these blocks would be sent from the TRAU to the
channel coder in the same 320 bit frames as that used for 20 ms speech frames.
• SID_FIRST: Indicates end of speech period and the start of a silence (no transmission) period.
• SID_UPDATE: Conveys silence descriptor information periodically during a silence period.

This is used by the receiver to generate comfort noise for the listener during the silence period.
• NO_DATA: Non-transmitted block during a silence period.
• ONSET: Indicates end of silence period and the start of a speech period.
3-100 68P02900W21-R
GMR-01 28 Feb 2006
Unlike Full Rate or Enhanced Full Rate DTX, AMR DTX is not designed with fixed TDMA frames of
transmission during the SACCH multiframe. The four SACCH bursts are always transmitted during the
SACCH TDMA frames. However, transmission during a silence period adheres to the following sequence:
• One SID_FIRST DTX block is transmitted after the last speech block of the speech period. It is
interleaved immediately following the last encoded speech block.
• Two NO_DATA DTX blocks elapse over the next two periods where encoded speech blocks
would normally be transmitted.
• One SID_UPDATE DTX block is transmitted. The SID UPDATE block is encoded and
rectangularly interleaved over 4 TDMA frames.
• Seven NO_DATA DTX blocks elapse over the next seven periods where encoded speech
blocks would normally be transmitted. The one SID_UPDATE, seven NO_DATA sequence
will repeat for as long as the silence period lasts.
• One ONSET DTX block is transmitted immediately before the first speech block of the new
speech period is sent. This ONSET is interleaved immediately before the first encoded
speech block.
Note that an ONSET can occur any time after a SID_FIRST DTX block, depending on how
long the silence period lasts. Thus, for example, no SID_UPDATES would be transmitted if
the silence period did not last long enough for the two NO_DATA periods to elapse.
For AMR channels, silence descriptor information (i.e. SID_UPDATE blocks)

are transmitted every 8 speech blocks compared to every 24 for Full Rate and
Enhanced Full Rate channels. Silence information is more frequently updated
for AMR channels, thereby providing a more accurate representation of comfort
noise to the user.
All four AMR DTX frames contain InBand signalling bits to allow link adaptation
to be performed during silence periods (refer to Link adaptation for AMR
channels for further details).
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.
68P02900W21-R 3-101
28 Feb 2006 GMR-01
There are three ways of utilizing this concept:

• The receiver can be switched between the two RF receive paths provided two antennas.
• The RF signals from two receive paths can be phase aligned and summed.
• The phasing can be made so as to minimize the distortion arising from the multipath
transmission.
Each of the methods has advantages and disadvantages.

In the case of the switched configuration, 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.
Remember in microcellular applications that the M-Cellcity and Horizonmicro / Horizonmicro2

do not support spatial diversity.
Figure 3-64 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
3-102 68P02900W21-R
GMR-01 28 Feb 2006
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 digital signal processing algorithm called
an equalizer is built into the receiver.
The equalizer uses a known bit pattern inserted into every 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 received signal would be unacceptable
for the majority of the time.
Training sequence code

The training sequence code (see Figure 3-65) 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-65 Training sequence code
Signal from shortest path
3 bits
Signal from delayed path
68P02900W21-R 3-103
28 Feb 2006 GMR-01
Subscriber environment Chapter 3: BSS cell planning
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.
3-104 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Subscriber environment
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-66). Thus greater
freedom of use for the subscriber gives the network designer even greater problems when designing and
implementing a cellular system.
Figure 3-66 The subscriber environment

URBAN/CITY
ENVIRONMENTS
RURAL AREAS
BUILDINGS
LIFTS TUNNELS
68P02900W21-R 3-105
28 Feb 2006 GMR-01
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-67 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-67 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-106 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
• 0.8W to 8W (GMSK) and 0.2W to 2W (8-PSK) for GSM900.
• 0.25W to 1W (GMSK) and 0.107W to 1W (8-PSK) 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.
68P02900W21-R 3-107
28 Feb 2006 GMR-01
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-108 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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-68, ensures that, as far as possible, the cell gives almost total
coverage for all the MSs within its area.
Figure 3-68 Layered architecture
MACROCELL
MICROCELL A MICROCELL B
TOP VIEW
SIDE VIEW MACROCELL
MICROCELL A MICROCELL B
68P02900W21-R 3-109
28 Feb 2006 GMR-01
The microcellular solution Chapter 3: BSS cell planning
Combined cell architecture
A combined cell architecture system, as illustrated in Figure 3-69, 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-69 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.
3-110 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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-70.
Figure 3-70 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
MACROCELL COVERAGE
SYSTEM 1 = OVERLAY SYSTEM

SYSTEM 2 = UNDERLAY SYSTEM
Some points to note:

• Macrocell and microcell networks may be operated as individual systems.
• The macrocell network is more dominant as it handles the greater amount of traffic.
• Microcells can be underlayed into existing networks.
68P02900W21-R 3-111
28 Feb 2006 GMR-01
The microcellular solution Chapter 3: BSS cell planning
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.
3-112 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Frequency planning
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-71.
Figure 3-71 Separating BCCH and TCH bands
n channels m channels
BCCH TCH
Guard Band
This has the benefits of:

• Making planning simpler.
• Better control of interference.
If microcells are included in the frequency plan, the band usage shown in Figure 3-72 is suggested.
Figure 3-72 Band usage for macrocells with microcells
Macro BCCH Micro Macro TCH

Micro TCH BCCH (SFH)
68P02900W21-R 3-113
28 Feb 2006 GMR-01
Frequency planning Chapter 3: BSS cell planning
Practical rules for TCH 1x3 re-use pattern

• BCCH re-use plan: 4x3 or 5x3, depending on the bandwidth available and operating
environment.
• 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).
• 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).
• 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,
• No more than 48 frequencies in a cell with multiple carriers with GPRS/EGPRS timeslots.
• 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.
• Use different MAIOs to control adjacent channel interference between the sectors within a site
3-114 68P02900W21-R
GMR-01 28 Feb 2006
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.
68P02900W21-R 3-115
28 Feb 2006 GMR-01
TCH re-use planning example

• Bandwidth: 10 MHz.
• Site configuration: Mix of 2-2-2, 3-3-3 and 4-4-4.
• Loading factor: 33%.
• Environment: Multi layer (micro and macro co-exist).
The spectrum is split as shown in Figure 3-73.
Figure 3-73 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-11.
Table 3-11 Frequency and parameter setting plan
ARFCN HSN MAIO

Sector A 21, 24, 27, 30, 33, 36, Any from 0, 2, 4
39, 42, 45 {1, 2, … 63}
Sector B 22, 25, 28, 31, 34, 37, Same as above 1, 3, 5
40, 43, 46
Sector C 23, 26, 29, 32, 35, 38, Same as above 0, 2, 4
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-116 68P02900W21-R
GMR-01 28 Feb 2006
Practical rules for TCH 1x1 re-use pattern

• 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.
• BCCH re-use plan: 4X3 or 5X3, depending on the bandwidth available and operating
environment.
• The allocation of TCH frequencies to each sector is recommended to be in a regular or

continuous sequence.
• Use different HSNs to reduce interference (co and adjacent channel) between the sites.
• 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.
• 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:
• In a 3 cell site configuration, the logical maximum loading factor is 1/6 or 16.7%.
Figure 3-74 illustrates how co-channel and adjacent channel interference can be avoided.
Figure 3-74 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
68P02900W21-R 3-117
28 Feb 2006 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-75.
Figure 3-75 BBH frequency spectrum allocation
Micro BCCH
BBH channels and micro TCH
{28075} If the ITS feature is unrestricted and enabled, the baseband hopping characteristic is restricted on
the DD CTU2 DRIs of which Carrier A is EGPRS capable. These DRIs do not join the BBH even if in the
database their corresponding ARFCNs are configured in the MA list.
To effectively utilize the ITS feature and maintain the stability, it is recommended to use the parameter
pre_rtf_id to map the DD CTU2 Carrier A to 64k RTF and exclude these ARFCNs from the MA list if BBH
must be applied for the cell.
3-118 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning {22879} Inter-radio access technology (2G-3G) cell reselection and handovers
{22879} Inter-radio access technology (2G-3G) cell

reselection and handovers
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to 2G-3G handovers
An optional feature is supported for handovers and cell reselection between different Radio Access Technology
(RAT) networks in the circuit and packet switched domain. The RAT can be either GSM/GPRS/EDGE
(2G/2.5G) 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.
2G-3G handover description
The 2G-3G handover feature supports handovers between different RAT networks. The RAT can be either
2G/2.5G (GSM/GPRS/EDGE) or 3G (UMTS).
Current evolving 3G UMTS networks will soon allow operators to provide UMTS coverage along with
GSM/GPRS/EGPRS coverage in their networks.
This feature enables a multi-RAT MS (a mobile station that can function in multiple Radio Access Networks
(RANs)) to either reselect or handover between a GSM RAN(GERAN) and a 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:
• Cell reselection across UTRAN (UMTS FDD neighbours) and GERAN in idle mode.
• Handovers between 3G (UMTS-FDD) and 2G (GSM) in active mode.
Restrictions
There is currently an upper limit of 32 FDD UTRAN neighbours in the GSM/GPRS system.
Implementation
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.
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.
68P02900W21-R 3-119
28 Feb 2006 GMR-01
{22879} Inter-radio access technology (2G-3G) cell reselection and handovers Chapter 3: BSS cell planning
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 and handover while
between an UMTS FDD cell and a GSM cell.
Impact of 2G-3G handovers on GSM system architecture
Figure 3-76 shows the system architecture for the GSM BSS inter-RAT handover feature.
Figure 3-76 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
3-120 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning {22879} Inter-radio access technology (2G-3G) cell reselection and handovers
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:
• Cell reselection to UTRAN TDD neighbour cells or CDMA2000 neighbour cells.
• Extended measurement reporting.
• Enhanced measurement reporting.
• Blind handovers.
• The sending of SI2quater on extended BCCH.
• The BSS restricts the maximum number of UTRAN neighbours per GSM cell to 32.
68P02900W21-R 3-121
28 Feb 2006 GMR-01
Call model parameters for capacity calculations Chapter 3: BSS cell planning
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-12.
Table 3-12 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 1) H = 2.5
Ratio of location updates to calls: non-border l = 2I = 7
location areaRatio of location updates to calls:
border location area
Ratio of IMSI detaches to calls I = 0
Location update factor: non-border location area L = 2L = 7
(see below)Location update factor: border location
area (see below)
GSM circuit-switched paging rate in pages per PGSM = 15
second
Ratio of intra-BSC handovers to all handovers (see i = 0.6
Note 1)
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 U (MSC - BSS) = 0.20
GPROC2/GPROC3
Cont.
3-122 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Call model parameters for capacity calculations
Table 3-12 Typical parameters for BTS call planning (Continued)

Percent link utilization (BSC to BTS) U (BSC - BTS) = 0.25
Percent link utilization (BSC to RXCDR) UBSC-RXCDR = 0.4
Percent link utilization (BSC to SMLC) for UBSC-SMLC = 0.20
GPROC2/GPROC3
Percent CCCH utilization UCCCH = 0.33
Blocking for TCHs PB-TCHs = 2%
Blocking for MSC-BSS trunks PB-Trunks = 1%
Number of cells per BTS CBTS = 3
Average SMS message size (payload only) SMSSIZE = 100 bytes
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 = 5
PS attach/detach rate (per sub/BH) PSATT/DETACH = 0.5
PDP context activation/deactivation (per sub/BH) PDPACT/DEACT = 0.5
Routeing area update RAU = 1.5
GPRS paging rate in pages per second PGPRS = 3
Coding scheme rates (CS1 to CS4) at the RLC/MAC CS1 = 9.2 kbit/s
layer CS2 = 13.6 kbit/s
CS3 = 15.8 kbit/s
CS4 = 21.8 kbit/s
EGPRS coding scheme rates (MCS-1 to MCS-9) MCS1 = 10.55 kbit/s
at the RLC/MAC layer MCS2 = 12.95 kbit/s
MCS3 = 16.55 kbit/s
MCS4 = 19.35 kbit/s
MCS5 = 23.90 kbit/s
MCS6 = 29.6 kbit/s
MCS7 = 31.10 kbit/s
MCS8 = 46.90 kbit/s
MCS9 = 61.30 kbit/s
Cell updates (per sub/BH) CellUpdate = 1.5
XBL (enhanced auto connect) parameters
Number of XBL messages per new call MNEWCALL = 1
Number of XBL messages per hr <-> fr handover MHANDOVER = 1
Length of an average XBL message, in bytes LXBL = 50
Number of hr <-> fr handovers per call Hhr-fr = 1
68P02900W21-R 3-123
28 Feb 2006 GMR-01
Call model parameters for capacity calculations Chapter 3: BSS cell planning
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 (Ι) and whether the short message sequence (type 1) or long message sequence (type 2) is
used for IMSI detach; typically Ι = 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 * Ι
L = I + 0.5 * Ι
3-124 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Control channel calculations
Control channel calculations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
There are four types of air interface control channels, they are:
• Broadcast Control CHannel (BCCH).
• Common Control CHannel (CCCH).
• Standalone Dedicated Control CHannel (SDCCH).
• Cell Broadcast CHannel (CBCH), which uses one SDCCH.
68P02900W21-R 3-125
28 Feb 2006 GMR-01
Control channel calculations Chapter 3: BSS cell planning
GPRS/EGPRS defines several new radio channels and packet data traffic channels.
• Packet Common Control CHannels (PCCCHs).
The following channels are mapped onto PCCCH:
◦ Packet Access Grant CHannel (PAGCH)
Downlink only, mapped on AGCH or PDTCH. Used to allocate
one or several PDTCHs.
◦ Packet Broadcast Control CHannel (PBCCH)

Downlink only, mapped BCCH or PDTCH.
◦ Packet Notification CHannel (PNCH)

Downlink only. Used to notify the MS of a PTM-M. This is not
used in the first GPRS/EGPRS release.
◦ Packet Paging CHannel

Downlink only, mapped on PDTCH 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.
• Packet Data Traffic CHannel (PDTCH)

A PDTCH corresponds to the resource allocated to a single MS on one physical channel for
user data transmission.
• Packet Dedicated Control CHannels (PDCCHs)

◦ Packet Associated Control CHannel (PACCH)
The PACCH is bi-directional. It is used for MS-PCU control signalling while the
MS is performing a packet transfer.
◦ 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.
Planning considerations
In planning the GSM/GPRS/EGPRS control channel configuration, the network planner must consider
three main variables:
1. Signalling requirements of the CCCH.
2. Signalling requirements of the PCCCH (if enabled).
3. Signalling requirements of the SDCCH.
3-126 68P02900W21-R
GMR-01 28 Feb 2006
SDCCH planning can be done independently, but CCCH planning depends on PCCCH planning.
It is assumed that by adequate provisioning the downlink part of the CCCH or PCCCH, the uplink part
is implicitly provisioned with sufficient capacity.
CCCH and PCCCH planning

When PCCCH is disabled (pccch_enabled is set to zero), all control signalling for GSM and GPRS/EGPRS
occur on the CCCH. When PCCCH is enabled, control signalling for GPRS/EGPRS occurs on the PCCCH
instead of the CCCH. Thus, CCCH signalling decreases when PCCCH is enabled. In other words, the
CCCH planning is dependent on PCCCH planning.
When PCCCH is enabled (pccch_enabled is set to 1), an additional variable must be considered. The network
planner must decide whether or not to use paging coordination in the system. If the planner decides to use
paging coordination (also called Network Operation Mode I), then a MS only needs to monitor the paging
channel on the PCCCH, and receives circuit-switched pages on the PACCH when it has been assigned a
PDTCH. If the planner decides not to use paging coordination (called Network Operation Mode III), the
MS that needs to receive pages for both circuit-switched and packet-switched services must monitor paging
channels on both PCCCH and CCCH.
Network Operation Mode II is currently not supported in the Motorola BSS.
Summary: CCCH and PCCCH decision tree

Figure 3-77 summarizes the decisions used to determine which planning steps should be used to determine
the CCCH and PCCCH signalling capacity requirements. The steps shown in the diagram are described in
more details in the following sections.
Figure 3-77 CCCH and PCCCH decision tree
(1) Decide whether or not paging coordination will be used in the network.
(2) Calculate the number of CCCHs per BTS cell when PCCCH is enabled.
pccch_enabled = 1 (3) Calculate the number of PRACH blocks per BTS cell.
(4) Calculate the number of PAGCHblocks per BTS cell.
(5) Calculate the number of PPCH blocks per BTS cell.
(6) Calculate the number of PBCCH blocks per BTS cell.
Calculate the number of CCCHs per BTS cell when PCCCH is disabled.
pccch_enabled = 0
Combined BCCH
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 number of CCCH channels required and the number of SDCCH channels required
68P02900W21-R 3-127
28 Feb 2006 GMR-01
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/EGPRS/GSM control channel provisioning is to determine whether
a combined BCCH is possible, given the 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.
3-128 68P02900W21-R
GMR-01 28 Feb 2006
Number of CCCHs and PCCCHs per BTS cell
The following factors should be considered when calculating the number of CCCHs per BTS cell:
• The CCCH channels comprise the paging channel (PCH) and access grant channel (AGCH) in
the downlink, and the random access channel (RACH) in the uplink.
• If PCCCH is enabled (pccch_enabled is set to 1), then the PCCCH relieves all GPRS/EGPRS
control signalling from the CCCH. Further, if paging coordination is also enabled, GSM CS
paging also occurs on the PCCCH for all GPRS/EGPRS-enabled mobiles.
• If the CCCH has a low traffic requirement, the CCCH can share its timeslot with SDCCHs
(combined BCCH). If the CCCH carries 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 bs_ag_blks_res is 0 to 2.
Number of CCCH blocks available for PCH is 1 to 3.
◦ Non-combined BCCH
Number of CCCH blocks = 9.
Number of CCCH blocks reserved for AGCH bs_ag_blks_res is 0 to 7.
Number of CCCH blocks available for PCH is 2 to 9.
• When a non-combined BCCH is used, it is possible to add additional CCCH control channels
(in addition to the mandatory BCCH on timeslot 0). These additional CCCH control channels
are added, in order, on timeslots 2, 4, and 6 of the BCCH carrier, thus creating cells with 18,
27, and 36 CCCH blocks. These configurations would only be required for very high capacity
cells or in large location areas with a large number of pages.
• Each CCCH block can carry one message. The message capacity of each CCCH block is 4.25
messages/second. This is due to the 51-frame multiframe structure of the channel.
• Each PCCCH block can carry one message. The message capacity of each PCCCH block is
4.17 messages/second. This is due to the 52-frame multiframe structure of the channel.
• The AGCH is used to send immediate assignment and immediate assignment reject messages
for GSM MSs and, if PCCCH is not enabled, GPRS/EGPRS 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.
68P02900W21-R 3-129
28 Feb 2006 GMR-01
• The PCH is used to send GSM paging messages and, if PCCCH is not enabled, GPRS/EGPRS
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 CCCH 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 CCCH sub-channel. Hence
the option to reserve CCCH channels for AGCH.
• It can normally be assumed that sufficient capacity exists on the uplink CCCH (RACH) once
the downlink CCCH is correctly dimensioned.
• A number of other parameters may be used to configure the CCCH channels. Some of these are:
◦ Number of paging groups. Each MS is a member of only one paging group and only
needs to listen to the PCH sub-channel corresponding to that group. Paging group size
is a trade off between MS idle-mode battery life and speed of access (for example, a
lot of paging groups, means the MS need only listen very occasionally to the PCH,
but as a consequence it takes longer to page that MS, resulting in slower call 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.
• 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.
3-130 68P02900W21-R
GMR-01 28 Feb 2006
Calculate the number of CCCHs per BTS cell - PCCCH disabled

When PCCCH is disabled (pccch_enabled is set to zero), the provisioning of the CCCH is estimated
by calculating the combined load from the GPRS/EGPRS pages, GSM pages, GPRS/EGPRS access
grant messages and GSM access grant messages. The calculation is performed by adding the estimated
GPRS/EGPRS and GSM paging blocks for the BTS cell to the estimated number of GPRS/EGPRS 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.
Introducing the GPRS/EGPRS feature into a cell may cause noticeable delays for paging in that
cell. Motorola advises operators to re-check the NPAGCH and NPCH equations provided here when
adding GPRS/EGPRS to a cell. Consider enabling PCCCH in cells with heavy paging.
The following planning actions are required:
In the following paragraphs, GPRS notation represents GPRS/EGPRS.
68P02900W21-R 3-131
28 Feb 2006 GMR-01
Determine the number of CCCHs per BTS.

The average number of blocks required to support AGCH, and PCH is given by:
The average number of blocks required to support AGCH and PCH is given by:
The average number of blocks required to support AGCH only is given by:
_ _
The average number of blocks required to support AGCH for GSM traffic is given by:
The number of access grants per AGCH block is 2:
The average number of blocks required to support AGCH for GPRS/EGPRS traffic is given by:
_ _ _
_
Where:
_ _ _ _
_ _ _
The access grant rate is given by:
The call rate (calls per hour) is given by:
3-132 68P02900W21-R
GMR-01 28 Feb 2006
The location update rate (LU per hour) is given by:
The SMS rate (SMSs per hour) is given by:
The LCS rate (LCSs per hour) is given by:
The average number of blocks required to support PCH only is given by:
_ _
The average number of blocks required to support GSM CS paging only is given by:
The number of pages per paging PCH block depends on whether paging is performed using TMSI or IMSI:
The number of paging blocks required at a cell to support GPRS/EGPRS is given by:
Where: is:
UCCCH the CCCH utilization.
λAGCH the access grant rate (per second).
GPRS_Users the number of GPRS and EGPRS
users on a cell.
Cont.
68P02900W21-R 3-133
28 Feb 2006 GMR-01
Where: is:
Avg_Sessions_per_user the average number of sessions
originated by user per busy hour
(this includes the sessions for
signalling).
λcall the call arrival rate per second.
λL the location update rate per
second.
λS 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/EGPRS
pages transmitted to a BTS cell
per second.
Table 3-13 Control channel configurations
Timeslot 0 Other timeslots Notes

1 BCCH + 3 CCCH N x 8 SDCCH One combined BCCH. The
+ 4 SDCCH other timeslot 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
9 CCCH example of one extra timeslot of
CCCHs added in support of GPRS
traffic. The value of N is >= 1.
Calculate the number of CCCHs per BTS cell - PCCCH enabled

When PCCCH is enabled (pccch_enabled is set to 1), the Network Operation Mode becomes relevant to
the planning rules. If paging coordination is used, Network Operation Mode I, then circuit-switched pages
for Class A and Class B mobiles (i.e. mobiles that are both capable of both GSM and GPRS) and pages for
EGPRS mobiles will be sent on the PCCCH instead of the CCCH. Regardless of paging coordination
though, all GPRS/EGPRS control signalling will occur on the PCCCH. Hence, the following planning
rules should be used.
3-134 68P02900W21-R
GMR-01 28 Feb 2006
The average number of blocks required to support AGCH, NCH and PCH is given by:
The average number of blocks required to support AGCH and PCH is given by:
The average number of blocks required to support AGCH only is given by:
The number of access grants per AGCH block is 2:
The access grant rate is given by:
The call rate (calls per hour) is given by:
The location update rate (LU per hour) is given by:
The SMS rate (SMSs per hour) is given by:
68P02900W21-R 3-135
28 Feb 2006 GMR-01
The LCS rate (LCSs per hour) is given by:
The average number of blocks required to support PCH depends on the provisioning of paging coordination
in the cell. If paging coordination is not enabled then the average number of blocks required to support
GSM CS paging is given by:
If paging coordination is enabled, the average number of blocks required to support GSM CS paging is
given by:
_ _
_ _
The number of pages per paging PCH block depends on whether paging is performed using TMSI or IMSI:
Where: is:
UCCCH the CCCH utilization.
λAGCH the access grant rate (per second).
P the paging rate per second.
λL the location update rate per
second.
e the number of Erlangs per cell.
T the average call length, in seconds.
second.
Cont.
3-136 68P02900W21-R
GMR-01 28 Feb 2006
Where: is:
NGSM_Only_MS the number of mobiles in the
system that do not support
GPRS/EGPRS.
NGSM_Capable_MS the number of mobiles in the
system that support GSM and,
optionally, GPRS/EGPRS. This is
also equal to the total number of
mobiles in the system minus the
number of GPRS/EGPRS-only
mobiles in the system.
Number of PCCCHs per BTS cell
The network planner may provision up to 1 PCCCH timeslot per BTS cell. If the PCCCH is enabled, then the
PCCCH will occupy a reserved PDTCH timeslot on the BCCH carrier. Note that the use_bcch_for_gprs
parameter is ignored to allow only the PCCCH timeslot on the BCCH carrier, and the BCCH carrier cannot
be a hopping carrier for PCCCH to be enabled.
The network planner may reserve 1 to 12 of the radio blocks on the uplink PCCCH as PRACH, i.e. for
GPRS/EGPRS random access, using the cell’s bs_prach_blks parameter. Any uplink PCCCH blocks that are
not reserved for PRACH can be used as PDTCH for up to 2 mobiles.
The network planner allocates the 12 radio blocks on the downlink PCCCH among 4 logical channels:
PBCCH, PPCH, PAGCH, and PDTCH. Allocation among these channels is a trade-off between the following
factors:
• The PPCH and PAGCH capacity required for the cell.
• The delay required for mobiles to acquire PBCCH system information upon entering the cell.
This delay is directly related to the delay before a mobile can start a data session following
cell selection.
• The PDTCH capacity available on the PCCCH timeslot.
PBCCH blocks are reserved using the bs_pbcch_blks parameter. PAGCH blocks can be reserved using the
bs_ag_blks_res parameter. All other downlink PCCCH blocks may be used for the PPCH, but there is no
parameter to reserve PPCH blocks. Nevertheless, the network planner should calculate the number of PPCH
blocks required in a BTS cell to determine how many blocks can be allocated to PBCCH blocks.
Any downlink PCCCH blocks that are not reserved for PBCCH, can be used for user data transmission when
not being utilized for control signalling. Note that the PCCCH timeslot may only be used for user data for
up to 2 mobiles.
For the subsequent calculations, note that the message capacity for each PCCCH block is 1 message
/ 0.240 second.
Calculate the number of PRACH blocks per BTS cell

The network planner should use the average number of blocks necessary to support PRACH to set the
cell’s bs_prach_blks parameter.
68P02900W21-R 3-137
28 Feb 2006 GMR-01
_ _
The average number of blocks required to support PRACH is given by:
The average number of PRACH arrivals per second is given by:
_ _ _ _
_
Where: is:
UPCCCH the desired PCCCH utilization.
GPRS_RACH/sec the GPRS/EGPRS random access
rate (per second).
users on a cell.
signalling).
3-138 68P02900W21-R
GMR-01 28 Feb 2006
Calculate the number of PAGCH blocks per BTS cell

The network planner should use the average number of blocks necessary to support PAGCH to set the cell’s
bs_pag_blk_res parameter.
_ _
The average number of blocks required to support PAGCH is given by:
The average number of PRACH arrivals per second is given by:
_ _ _ _
_
Where: is:
GPRS_RACH/sec the GPRS/EGPRS random access
rate (per second).
users on a cell.
signalling).
Calculate the number of PPCH blocks per BTS cell

The average number of blocks required to support PPCH is given by:
_ _
68P02900W21-R 3-139
28 Feb 2006 GMR-01
If paging coordination is not enabled in the network, then the average number of PPCH blocks required to
support GSM CS paging only is zero:
If paging coordination is enabled, then the average number of blocks required to support PPCH is given by:
_ _
_
The average number of PPCH blocks required to support GPRS/EGPRS paging only is given by:
Where: is:
NGSM_GPRS_MS the number of mobiles in the
system that are capable of both
GSM and GPRS/EGPRS services.
NALL_MS the total number of mobiles in the
system.
second.
PGPRS the number of GPRS/EGPRS
pages transmitted to a BTS cell
per second.
3-140 68P02900W21-R
GMR-01 28 Feb 2006
Choose the number of PBCCH blocks per BTS cell

The network planner must allocate between 1 and 4 PBCCH radio blocks on the downlink PCCCH by setting
the cell’s bs_pbcch_blks parameter.
An allocation of 4 PBCCH blocks minimizes the time required for the mobile to acquire the cell’s
GPRS/EGPRS broadcast system information. In turn, this minimizes the delay before the mobile can start data
transmission upon cell selection/reselection. An allocation of 1 PBCCH block minimizes the radio resources
consumed by PBCCH, freeing up more radio resources for PAGCH, PPCH, and user data transmission. Thus,
in summary, choosing the number of PBCCH blocks per BTS cell is a trade-off: data transmission delay
following cell selection/reselection vs. radio resources available for PPCH, PAGCH, and PDTCH.
The number of PCCCH blocks available for PBCCH is given by the following:
So, the network planner must choose the number of PBCCH block (NPBCCH) such that it does not exceed the
blocks available (or the maximum of 4 blocks). The network planner must also consider the trade-off
with PDTCH capacity on the PCCCH timeslot.
In general, it is recommended that the network planner maximize the PBCCH blocks instead of PDTCH
capacity on the PCCCH timeslot. The PCCCH timeslot will only be used for PDTCHs during conditions of
cell congestion. Therefore, the network planner can improve the user experience more by maximizing the
PBCCH blocks and consequently minimizing data transmission delay following cell selection/reselection.
The network operator may choose to prioritise PDTCH capacity when only a single PDTCH exists in the cell,
i.e. the PCCCH timeslot is the only GPRS/EGPRS timeslot.
68P02900W21-R 3-141
28 Feb 2006 GMR-01
User data capacity on the PCCCH timeslot
The PCCCH timeslot can support user data traffic (PDTCH) for up to two mobiles. The radio blocks on
the uplink PCCCH timeslot that are not required for PRACH are available for PDTCH. Similarly, the radio
blocks on the downlink PCCCH timeslot that are not required for PBCCH, PAGCH, or PPCH are available for
PDTCH as well. It should be noted that, if other PDTCHs are available in the cell, PDTCHs are only allocated
on the PCCCH timeslot when the cell is congested.
Accordingly, the network planner can estimate the data capacity on the PCCCH timeslot. The formulas given
below can be use to estimate the raw data capacity of the PCCCH timeslot. The raw data rate estimates are
not adjusted for protocol overhead and possible data compression. They are for informational use only.
Details on planning for data traffic are provided in the section GPRS air interface planning process later
in this chapter.
The raw downlink PDTCH capacity is given by:
_ _ _
The raw uplink PDTCH capacity is given by:
_ _ _
Where: is:
TS_Data_Rate the average data rate of the PCCCH
timeslot based on the expected radio
conditions on the PCCCH carrier.
The radio conditions determine the coding scheme used for the data transmission.
For example, suppose the network planner expects good radio conditions on the PCCCH carrier so that CS4 is
used 80% of the time and CS3 is used 20% of the time. The network planner also calculates the following
when dimensioning the PCCCH:
NPAGCH = 2
NPPCH = 3
NPBCCH = 4
3-142 68P02900W21-R
GMR-01 28 Feb 2006
In this case, the average data rate is calculated as follows:
_ _
So the raw data capacity for the downlink PCCCH can be calculated as:
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 signalling and data messaging takes place for SMS, location update and call set-up. As the
number of calls taking place in a BTS increases, greater demand is placed on the control channel for call
set-up and the same is true if the number of SMS increases.
{24620} The Fast Call Setup feature allows the BSS to allocate an appropriate channel based on the
establishment cause. That is, TCH directly to the MS if the MS intends to make a speech call, or SDCCH if
the MS intends to send a SMS. The operator configurable parameter TCH_usage_threshold keeps track of
the percentage of TCH that are busy in the BCCH band. When the busy percentage is equal or higher to
TCH_usage_threshold, the BSS turns this feature off.
The following factors should be considered when calculating the number of SDCCH per BTS cell:
• To determine the required number of SDCCHs for a given number of TCHs per cell, the call,
location update, and SMS (point to point) rates must be determined.{24620} A TCH is directly
allocated to the MS for a speech call when the Fast Call Setup feature is turned on. The
SDCCH usage drops need to be accounted for.
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.
• 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. Further, if
the network is configured to send SMS over GPRS, SMS does not require the use of a SDCCH.
• Calculating the number of SDCCHs required is necessary for each cell at a BTS site.
• The equation below for NSDCCH is used to determine the average number of SDCCHs.
• There is a limit of {26987} 124 or 128 SDCCHs (depending on whether control channels are
combined or not) per cell. This may limit the number of supportable TCHs within a cell.
• A change in the call model may also affect the number of SDCCHs (and supportable TCHs)
required. The formula should then be used to calculate the number of SDCCHs needed.
• The Number of Erlangs in Table 3-14 and Table 3-15 is the number of Erlangs supported by a
given cell, based on the number of TCHs in that cell. To determine the number of Erlangs
supported by a cell, use Erlang B.
68P02900W21-R 3-143
28 Feb 2006 GMR-01
• The number of TCHs in a cell will vary depending upon the number of carriers that are (AMR
or {22064} GSM} half rate capable. The number of calls that use the half rate capable carriers
may vary depending upon such factor as cell loading, mobile penetration, etc. In Table 3-14
and Table 3-15 a worst case scenario is assumed, where all half rate capable carriers are
used as half rate.
Not all combinations of half rate usage are shown in the tables.
• The call arrival rate is derived from the number of Erlangs (Erlangs divided by call duration).
• Use Erlang B (on the value of NSDCCH) to determine the required number of SDCCHs necessary
to support the desired grade of service.
• The number of location updates will be higher for sites located on the borders of location areas,
as compared to inner sites of a location area (see Figure 3-78).
Figure 3-78 Location area diagram
BORDER BTS =
INNER BTS =
LOCATION AREA
Calculate the number of SDCCHs per BTS cell

• Determine the number of SDCCHs per BTS cell.
The average number of SDCCHs is given by:
3-144 68P02900W21-R
GMR-01 28 Feb 2006
{24620}
Where: is:
NSDCCH the average number of SDCCHs.
Tc the time duration for call set-up.
λL the location update rate.
TL the time duration of location
updates.
Tg the guard time for SDCCH.
TS the time duration of SMS (short
message service set-up).
λLCS the number of LCSs per second.
TLCS the time duration of LCS (location
service set-up).
{26987} The timeslots allocated for SDCCH follows the new algorithm for picking the timeslots based on
the parameter setting.
1. sd_priority (per carrier db parameter sd_priority): The parameter sd_priority takes a value in
the range 0 through 255, and this assigns a priority to the carrier (RTF); the lower, the priority
the higher the possibility to get a SDCCH in the carrier (RTF).
2. PBCCH: If PBCCH is configured, the NON BCCH carrier has preference over the BCCH
carrier.
3. Number of availabe TCH barred timeslots: Available TCH barred timeslots are TCH barred
timeslots which are not configured as SDCCH timeslots yet. TCH or PDTCH cannot be
configured on a TCH barred timeslot since it does not have a terrestrial backhaul. It can only
be used for SDCCHs since SDCCH timeslots do not need terrestrial backhaul.
4. PGSM/EGSM: The PGSM carrier is preferred over EGSM carriers.
5. pkt_radio_type (per carrier db parameter pkt_radio_type): The parameter pkt_radio_type

determines if the RTF can carry GPRS/EDGE or not. Carriers with lower pkt_radio_type are
preferred over carriers with higher pkt_radio_type.
6. Half Rate: Non Half Rate carriers are preferred over Half Rate capable carriers.
7. sdcch loading (Not the db paramter sd_load, but the actual number of SDCCH timeslots
configured). Carriers with fewer sdcch loading are chosen over carriers with higher sdcch
loading so that SDs get distributed among carriers with identical SD related parameters. The
db parameter sd_load determines the number of timeslots in the carrier that can be SDCCH.
This can take a value of 0 through 8; that is, up to 8 timeslots can be configured as SDCCH
in a single carrier.
8. carrier id: Carrier id is used as a tie breaker among two carriers. Carrier with lower carrier id is
chosen over carrier with higher carrier id.
68P02900W21-R 3-145
28 Feb 2006 GMR-01
SDCCH Configuration Recommendations

SDCCH TS should be spread as widely as possible across available carriers.
Only one SDCCH TS is allowed on the BCCH Carrier. This can be achieved by setting “sd_load” parameter
for BCCH RTF to 1. A maximum of 3 SDCCH TS on other carriers are recommended, though 2 SDCCH TS
is a preferred maximum. This can be achieved by setting sd_load on non BCCH RTF to 2 or 3.
Number_sdcchs_preferred is the number of SDCCH the system configures at the system initialization time.
When channel_reconfiguration_switch is enabled, then on based on SDCCH usage, the TCH in the cell can be
reconfigured to SDCCH up to max_number_of_sdcchs based on need.
When SDCCH blocking is perceived to be high at a cell, then it is recommended to set the
max_number_of_sdcchs to be greater than number_sdcchs_preferred by a value of 8 or 16. This can help
alleviate SDCCH blocking in that cell.
Example Configurations
Number of SDCCH on SDCCH on SDCCH on SDCCH on SDCCH on SDCCH on

SDCCH/cell BCCH carrier 2nd carrier 3rd carrier 4th carrier 5th carrier 6th carrier
60 12 16 16 16 — —
64 8 16 16 16 8 —
92 12 16 16 16 16 16
Control channel configurations
Table 3-14 and Table 3-15 give typical control channel configurations based on the typical BTS planning
parameters given in Table 3-12. Due to the many combinations of half rate capable RTFs, only a partial
listing is depicted.
Control channel configurations for non-border location area

Table 3-14 is for the non-border location area cell, where the ratio of location updates to calls is 2.
Table 3-14 SDCCH planning for typical parameters (non-border location area)
Number of Number of Number of Number of Timeslot utilization

RTFs TCHs Erlangs SDCCHs
Timeslot 0 Other
timeslots
1 fr 7 2.94 4 1 BCCH + 3
CCCH + 4
SDCCH
1 hr 12 6.61 8 1 BCCH + 9 8 SDCCH
CCCH
2 fr 14 8.20 8 1 BCCH + 9 8 SDCCH
CCCH
Cont.
3-146 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-14 SDCCH planning for typical parameters (non-border location area) (Continued)
Timeslot 0 Other
timeslots
1 fr 22 14.90 8 1 BCCH + 9 8 SDCCH
1 hr CCCH
2 hr 28 20.15 12 1 BCCH + 3 8 SDCCH
CCCH + 4
SDCCH
3 fr 22 14.90 8 1 BCCH + 9 8 SDCCH
CCCH
2 fr 30 21.93 12 1 BCCH + 3 8 SDCCH
1 hr CCCH + 4
SDCCH
1 fr 38 29.2 12 1 BCCH + 3 8 SDCCH
2 hr CCCH + 4
SDCCH
3 hr 42 32.84 16 1 BCCH + 9 2 x 8 SDCCH
CCCH
4 fr 30 21.9 12 1 BCCH + 3 8 SDCCH
CCCH + 4
SDCCH
3 fr 38 29.2 12 1 BCCH + 3 8 SDCCH
1 hr CCCH + 4
SDCCH
5 fr 38 29.2 12 1 BCCH + 3 8 SDCCH
CCCH + 4
SDCCH
6 fr 45 35.6 16 1 BCCH + 9 2 x 8 SDCCH
CCCH
5 fr 53 43.1 16 1 BCCH + 9 2 x 8 SDCCH
1 hr CCCH
3 fr 68 57.2 20 1 BCCH + 9 3 x 8 SDCCH
3 hr CCCH
6 hr 88 76.4 24 1 BCCH + 9 3 x 8 SDCCH
CCCH
7 fr 53 43.1 16 1 BCCH + 9 2 x 8 SDCCH
CCCH
8 fr 60 49.6 20 1 BCCH + 9 3 x 8 SDCCH
CCCH
9 fr 68 57.23 20 1 BCCH + 9 3 x 8 SDCCH
CCCH
10 fr 76 64.9 20 1 BCCH + 9 3 x 8 SDCCH
CCCH
68P02900W21-R 3-147
28 Feb 2006 GMR-01
The CBCH reduces the number of SDCCHs by one and may require another channel.
3-148 68P02900W21-R
GMR-01 28 Feb 2006
Control channel configurations for border location area

Table 3-15 is for the border location area cell, where the ratio of location updates to calls is 7.
Table 3-15 SDCCH planning for typical parameters (border location area)

Timeslot 0 Other
timeslots
1 fr 6 2.28 8 1 BCCH + 9 8 SDCCH
CCCH
1 hr 12 6.61 12 1 BCCH + 3 8 SDCCH
CCCH + 4
SDCCH
2 fr 14 8.2 12 {26987} 1 8 SDCCH
BCCH + 3
CCCH + 4
SDCCH
1 fr 21 14.0 16 1 BCCH + 3 2 x 8 SDCCH
1 hr CCCH + 4
SDCCH
2 hr 26 18.4 20 1 BCCH + 3 2 x 8 SDCCH
CCCH + 4
SDCCH
3 fr 21 14.0 16 1 BCCH + 9 2 x 8 SDCCH
CCCH
2 fr 29 21.0 20 1 BCCH + 3 2 x 8 SDCCH
1 hr CCCH + 4
SDCCH
1 fr 36 27.3 24 1 BCCH + 9 3 x 8 SDCCH
2 hr CCCH
3 hr 40 31.0 28 1 BCCH + 3 3 x 8 SDCCH
CCCH + 4
SDCCH
4 fr 29 21.0 20 1 BCCH + 3 2 x 8 SDCCH
CCCH + 4
SDCCH
3 fr 36 27.3 24 1 BCCH + 9 3 x 8 SDCCH
1 hr CCCH
5 fr 36 27.3 24 1 BCCH + 9 3 x 8 SDCCH
CCCH
6 fr 44 33.8 28 1 BCCH + 9 4 x 8 SDCCH
CCCH
5 fr 51 41.2 32 1 BCCH + 9 4 x 8 SDCCH
1 hr CCCH
Cont.
68P02900W21-R 3-149
28 Feb 2006 GMR-01
Table 3-15 SDCCH planning for typical parameters (border location area) (Continued)
Timeslot 0 Other
timeslots
3 fr 66 55.3 40 1 BCCH + 9 5 x 8 SDCCH
3 hr CCCH
7 fr 51 41.2 32 1 BCCH + 9 4 x 8 SDCCH
CCCH
8 fr 58 47.8 36 1 BCCH + 9 5 x 8 SDCCH
CCCH
9 fr 66 55.3 40 1 BCCH + 9 5 x 8 SDCCH
CCCH
10 fr 73 62.0 44 1 BCCH + 9 6 x 8 SDCCH
CCCH
(1) There is a limit of 44 or 48 SDCCHs (depending on whether control channels are combined or
not) per cell. This may limit the number of supportable TCHs within a cell.
(2) For theITS feature, to configure more EGPRS PDs on DD CTU2 Carrier A, it is recommended
to set sd_priority to lowest value and set sd_load to 0 for both carrier A and B.
3-150 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning GPRS/EGPRS traffic planning
GPRS/EGPRS traffic planning

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Determination of expected load
The planning process begins by determining the expected GPRS/EGPRS 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/EGPRS 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/EGPRS timeslots is the key piece
of information that drives the BSS provisioning process in support of GPRS/EGPRS.
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/EGPRS network planning:
• GPRS/EGPRS network traffic estimation and key concepts
This text is intended to introduce the key concepts involved in planning a network. Because
GPRS/EGPRS introduces the concept of a switchable timeslot that can be shared by both the
GSM circuit-switched infrastructure and by the GPRS/EGPRS infrastructure, much of the
following text is dedicated to the discussion of this topic.
• 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/EGPRS provisioning process, and
how to use this information in order to determine the number of GPRS/EGPRS timeslots that
are required on a per cell basis.
68P02900W21-R 3-151
28 Feb 2006 GMR-01
GPRS/EGPRS network traffic estimation and key concepts Chapter 3: BSS cell planning
GPRS/EGPRS network traffic estimation and key

concepts
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to the GPRS/EGPRS network traffic estimation and

key concepts
From here on, packet data notation will be interchangeably used.

The GPRS/EGPRS network planning is fundamentally different from the planning of circuit switched
networks. One of the fundamental reasons for the difference is that a GPRS/EGPRS 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/EGPRS packet data provisioning process.
The GPRS/EGPRS traffic estimation process starts by looking at the per cell GPRS/EGPRS 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/EGPRS timeslots required to support this throughput on a per cell basis.
The estimated GPRS/EGPRS 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:
• Traffic load per cell.
• Mean packet size.
• Number of available GPRS/EGPRS timeslots.
• Distribution of CS1 to CS4 and MCS-1 to MCS-9 rate utilization.
• Distribution of Mobile Station (MS) multislot operation (1, 2, 3 or 4).
• BLER.
3-152 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning GPRS/EGPRS network traffic estimation and key concepts
Use of timeslots
The use of timeslots for GPRS/EGPRS 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/EGPRS mode, a
subscriber uses the infrastructure timeslots for carrying data only when there is data to be sent. However,
the GPRS/EGPRS subscriber can be attached and not sending data, and this still presents a load to the GSN
part of the GPRS/EGPRS system, which must be accounted for when provisioning the GPRS infrastructure,
that is, in state 2 as explained below.
The GPRS/EGPRS mobile states and conditions for transferring between states are provided in Table 3-15 and
shown in Figure 3-79 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/EGPRS
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 combines the circuit-switched and GPRS control channels together as
BCCH/CCCH. The software provides the option of configuring the PBCCH/PCCCH for GPRS/EGPRS
control channels. This chapter provides planning information for determining the BCCH/CCCH control
channel capacity needed.
68P02900W21-R 3-153
28 Feb 2006 GMR-01
Table 3-16 MM state model of MS
Condition for Comments

Present state # Present state Next state
state transfer (present state)
1 IDLE READY(3) GPRS/EGPRS Subscriber is not
Attach monitored by the
infrastructure, that
is not attached
to GPRS/EGPRS
MM, and therefore
does not load the
system other than
the HLR records.
2 STANDBY READY(3) PDU Subscriber is
Transmission attached to
GPRS/EGPRS
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/EGPRS Data transmission
Detach through the
infrastructure
occurs in the
Ready state
3 READY STANDBY(2) Ready timer The ready timer
expiryorforce to (T3314) default
Standby (The time is 32 seconds.
network or the MS The timer value can
can send a GMM be modified during
signalling message the signalling
to invoke force to process by MS
Standby.) request.2 - 60 s in
2 s increments or
61 - 1800 s in 60 s
increments.
3-154 68P02900W21-R
GMR-01 28 Feb 2006
The MS and SGSN state models are illustrated in Figure 3-79.
Figure 3-79 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
68P02900W21-R 3-155
28 Feb 2006 GMR-01
Dynamic timeslot allocation
This section proposes a network planning approach when utilizing dynamic timeslot mode switching of
timeslots on a carrier with GPRS/EGPRS timeslots. The radio interface resources can be shared dynamically
between the GSM circuit-switched services and GPRS/EGPRS data services as a function of service load
and operator preference.
The timeslots on any carrier can be reserved for packet data 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
packet data service or for circuit-switched service.
The timeslot allocation is performed such that the GPRS/EGPRS reserved timeslots are allocated for
GPRS/EGPRS 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.
Switchable timeslots are compatible with the AMR and {22064} GSM half rate features.
Timeslots are further allocated by TRAU type and BCCH carrier. 64kbit/s TRAU are allocated before
32kbit/s TRAU, 32kbit/s TRAU are allocated before 16kbit/s TRAU. In addition, TRAU types are given
priority over the BCCH carrier.
For EGPRS, 64Kbps terrestrial timeslots are needed on the link between the BTS and BSC to support the
backhaul required for EGPRS coding schemes MCS-1 to MCS-9. This is a single 64Kbps and not adjacent
16Kbps subrate time slots. For Non-BCCH carriers all time slots should have 64Kbps while for BCCH, the
BCCH times slot uses 16Kbps sub-rate.
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.
3-156 68P02900W21-R
GMR-01 28 Feb 2006
Background and discussion

Multiple carriers per cell can be configured with GPRS/EGPRS timeslots by the operator for packet data
traffic handling capability. By doing so, it can meet the expanding base of packet data subscribers and
enhance performance, that is, increase data throughput.
There are two options to configure GPRS/EGPRS 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/EGPRS timeslots in a cell
contiguously to maximize performance. The contiguous GPRS/EGPRS 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/EGPRS timeslots on a per carrier basis in a cell.
Depending on hardware configuration at a cell, there maybe some limitations on how time slots are allocated
to EGPRS on a carrier, as described below.
EGPRS is available on Horizon macro II through software upgrade. It is also available on Horizon macro
through CTUII upgrade. Since 8-PSK modulated signals do not posses a constant envelope, linearity
requirement on the power amplifier is increased to maintain the out-of-band radiation to a minimum. The
Compact transceiver unit (CTUII) can operate in two modes: High Power Mode (HPM) or Normal Power
Mode (NPM). Each have two sub-modes of operations as far as number of carriers are concerned: Single
Density Mode (SDM) or Dual Density Mode (DDM).
{28075} With the introduction of ITS, EGPRS can not only operate in SDM but also in DDM under which the
output power in GMSK mode (irrespective of whether in EGPRS, GPRS, or voice) can be similar or higher
than the output power in 8-PSK mode, depending on whether operating in NPM or HPM respectively. CTUII
produces the same average output power in EGPRS 8-PSK mode as that of GSM (GMSK) when GSM is
configured in DDM. However, when GSM is in SDM, its output power can be up to 5dB higher than EGPRS.
There is a settable capping of the output power to equalize the average output power in GMSK and 8-PSK
modes, if required. To support EGPRS on DDM CTU2 and retain no HW changes of CTU2, each CTU2 is
able to rapidly switch between Double Density modulation (GMSK) and Single Density modulation (8PSK).
The power output is not be affected by the ITS feature for GMSK and 8PSK. The capping works in 4 steps by
setting a data base parameter to the values as shown in Table 3-17.
Table 3-17 Capping settings
Step Data base parameter value

0 5dB higher
1 2dB higher
2 1dB higher
> 2 0dB difference
68P02900W21-R 3-157
28 Feb 2006 GMR-01
Therefore, depending on the configuration of a cell, it is possible that GMSK signals can be set to have, on
average, higher power than 8-PSK signals. The following are the scenarios in which there can be up to 5dB
difference between GMSK and 8-PSK modulated signals:
• A 2-carrier cell (2/2/2) may have one EGPRS carrier and one GSM full power carrier.
• Some of the time slots of a 1-carrier cell (1/1/1) are allocated to EGPRS. Different powers
on time slot by time slot basis.
• On the same time slot allocated to EGPRS, users operating on MCS-1 to 4 and MCS-5 to 9.
However, as a general deployment rule the GMSK and 8-PSK signal power levels should be set equally
(data base parameter value>2).
{23769} The minimum backhaul requirement is determined to be 3 DS0s since a minimum of 2 DS0s are
required to support voice traffic if all 8 timeslots on a carrier are configured as TCH and the additional third
DS0 provides the bare minimum backhaul required for configurations when 1 to 3 timeslots on the carrier are
configured as PDTCHs. The third DS0 also helps in reducing the time required to start servicing the first
PDTCH timeslot by keeping this backhaul synchronized between the BTS and the PCU even when there are
no PDTCHs active on a carrier (provided there are enough GDS resources available across the cell).
The RTF allow_32k_trau and use_bcch_for_gprs attributes were replaced with a new parameter
pkt_radio_type. pkt_radio_type also accommodates the 64K backhaul necessary to support EGPRS and
makes it possible to configure RTFs on which GPRS data is specifically disallowed. Technical Description:
BSS Implementation (68PO2901W36) provides a complete description of these commands.
Depending on the restrictions imposed on GPRS (32kbps TRAU) and EGPRS (enabled or disabled),
pkt_radio_type can be set between 0 (no packet data) and 3 (64k).
{23769} Every RTF equipped as pkt_radio_type = 3 (64K) also has a configurable attribute rtf_ds0_count.
If the VersaTRAU feature is unrestricted, the operator can configure the RTF backhaul for an EGPRS capable
carrier to be between 3 and 8 64kbps terrestrial timeslots.
{28075} When the RTF to DRI mapping is performed, the RTFs equipped for EGPRS (that is, 64kbit/s
TRAU) are mapped to SDM or DDM equipped CTUII radios if possible. If the ITS feature is unrestricted
and enabled, it is not recommended to map operator preferred 64k RTF to improper DRI because it would
invalidate the ITS feature. If no single-density or double-density CTUIIs are available and other DRI
hardware is available, the EGPRS RTF falls back to 16K TRAU. When such a mapping occurs, the carrier
supports signalling, voice and data.
Due to the importance of the BCCH carrier, the BCCH is remapped onto an available DRI, even if that DRI
is unable to support EGPRS. In the event that the BCCH RTF is remapped onto a DRI that cannot support
EGPRS, the carrier will only be able to support GSM voice calls or 16K data.
Additionally, the BCCH RTF always attempts to migrate to a CTUII if possible. This requirement primarily
comes into play post-initialization when the BCCH RTF fails. The BSS software will attempt to both
maintain EGPRS service and keep the BCCH on a CTUII if at all possible. If the BCCH RTF is configured
for EGPRS and there is only one SDM CTUII available, the BCCH RTF will be mapped onto that CTUII,
since EGPRS service and EGPRS one phase access would still be available. However, if the BCCH RTF
is not configured with 64kbps terrestrial backing and there is only one CTUII available, the BCCH will be
moved to a non-CTUII radio.
At initialisation the BSS should “load up" non-CTUII hardware with 16k/32k carriers as much as possible.
Thus, the BSS software will attempt to assign EGPRS carriers onto EGPRS-capable hardware first, and then
assign carriers to the rest of the hardware in its usual fashion. The BSS will ignore the pkt_radio_type value
of the BCCH carrier if PBCCH/PCCCH is enabled in the cell.
3-158 68P02900W21-R
GMR-01 28 Feb 2006
The BSS supports a minimum of zero to a maximum of 30 GPRS/EGPRS timeslots per cell. The sum of
reserved and switchable GPRS/EGPRS timeslots should not exceed 30.
The GPRS/EGPRS 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/EGPRS timeslots allocated only for packet data use.
• • Switchable timeslots dynamically allocated for either GSM circuit-switched traffic or

GPRS/EGPRS traffic (designated as switchable timeslots by Motorola).
• • Remaining timeslots on the carrier with GPRS/EGPRS timeslots, if any, only for
circuit-switched use.
68P02900W21-R 3-159
28 Feb 2006 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:
• Use reserved timeslots to guarantee a minimum quality of service (QoS) for packet data users.
• Use switchable timeslots to provide low circuit mode blocking and high packet data throughput
when the voice busy hour and the GPRS busy hour do not coincide.
• Use switchable timeslots to provide higher packet data throughput without increasing the
circuit-switched blocking rate.
If all the GPRS/EGPRS timeslots are provisioned as switchable, the last available timeslot is
not given to a circuit-switched call until transmission of all the GPRS/EGPRS 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.
• Use switchable timeslots to provide some GPRS/EGPRS service coverage in low GPRS
traffic volume areas.
• Use switchable timeslots to provide extra circuit-switched capacity in spectrum limited areas.
In order to make the decision on how to best allocate reserved and switchable timeslots, the network planner
needs to have a good idea of the traffic level for both services. The proposal in this planning guide is to
drive the allocation of switchable timeslots and reserved GPRS/EGPRS 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/EGPRS QoS can be planned by counting the number of available reserved
GPRS/EGPRS timeslots, and by evaluating the expected utilization of the switchable timeslots by the
circuit-switched part of the network during the GPRS/EGPRS busy hour.
3-160 68P02900W21-R
GMR-01 28 Feb 2006
The priority of timeslot allocation takes into account the factors in the list below. The highest priority
starts with number 1 and the lowest priority is number 5. In the examples that follow, priorities 3 and
4 are not considered.
1. TRAU-Type - in this order: 64K, then 32K, then 16K.
2. BCCH Carrier.
3. Most INS number of timeslots. At this step, the following are taken into account:
a. Continuous timeslots.
b. SD load (signalling load).
c. SD priority.
4. The highest local carrier id. This may or may not be corresponding to the RTF index. So, the
highest local carrier id may not necessarily be RTF + 3 if there is a 4 carrier cell (RTF + 0 to
RTF +3). Hence, the RTF index is irrelevant.
5. TS priority in the following order:

a. Reserved.
b. Switchable.
c. Circuit swiitched (T).
{28075} The 64k DDM CTU2 carrier A is less preferred for 64k PDCH placement and its paired 32k
carrier B is less preferred for 32k PDCH placement.
68P02900W21-R 3-161
28 Feb 2006 GMR-01
Carrier timeslot allocation examples
The following configuration examples explore different ways to configure timeslots in a cell. {23769}
Some of these examples also illustrate the usage of the PDTCH/backhaul proportion when configuring the
timeslots on an EGPRS capable carrier (pkt_radio_type set to 3) with a configurable RTF backhaul (using
the rtf_ds0_count parameter).
In the examples, the following annotations are used:
B = BCCH/CCCH timeslot for GPRS/GSM signalling.
SD = The {28075} ith SDCCH timeslot for GSM signalling. The subscript represents the ascending order in
which the SDCCH timeslots are allocated across carriers.
P = PCCCH timeslot for GPRS/EGPRS signalling.
RG = Reserved GPRS timeslot (EGPRS cannot be used, if non-64k RTF).
RE = Reserved EGPRS timeslot (GPRS can be used).
SG = Switchable GPRS timeslot (EGPRS cannot be used, if non-64k RTF).
SE = Switchable EGPRS timeslot (GPRS can be used).
T = Circuit-switched use only timeslots.
{28075} X = Blanked-out timeslots (on DDM CTU2 Carrier B as Carrier A is capable of EGPRS).
3-162 68P02900W21-R
GMR-01 28 Feb 2006
Example 1
There are 15 switchable GPRS/EGPRS timeslots and 10 reserved GPRS/EGPRS timeslots in a 5 carrier cell.
{23769} This example assumes that the VersaTRAU feature is not purchased. In this case, the RTF backhaul
for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s if it is the BCCH RTF or 8 DS0s if it
is a non-BCCH RTF. The following is assumed:
• pkt_radio_type set to:
◦ {28075} PGSM BCCH RTF: 64K (3).
◦ EGSM 2 non-BCCH carriers: 32k (2).
◦ PGSM 1 non-BCCH carrier: 16k (1).
◦ PGSM 1 non-BCCH carrier: None (0).
• One CTUII and four non-CTUII.
• GPRS 32K and EGPRS unrestricted.
{28075} Assuming sd_load of 2, sd_priority is the same for all the carriers, and PBCCH is not enabled, the
preferred number of SDCCH is 64, HR is disabled, and the timeslot allocation is shown as illustrated.
The GPRS/EGPRS timeslots are configured contiguously for performance. The packet data time slots are
arranged as shown in the table below. The BCCH RTF is mapped to CTUII and all the reserved time slots are
EGPRS capable. The non-BCCH 32k carriers are used for GPRS CS1 to CS4. The remaining switchable
timeslots are mapped to one of the non-BCCH 16k carrier.
{28075}
Carrier TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

BCCH 64K (CTUII) B SD5 SD6 RE RE RE RE RE
Non-BCCH 32K SD7 SG SG RG RG RG RG RG
(non-CTUII)
Non-BCCH 32K SD8 SG SG SG SG SG SG SG
(non-CTUII)
Non-BCCH 16K SD3 SD4 SG SG SG SG SG SG
(non-CTUII)
Non-BCCH SD1 SD2 T T T T T T
68P02900W21-R 3-163
28 Feb 2006 GMR-01
Example 2
for an RTF with pkt_radio_type set to 3 (64K) is defaulted to 7 DS0s if it is the BCCH RTF or 8 DS0s if it is
a non-BCCH RTF. The following are assumed:
• pkt_radio_type set to: {28075}
◦ PGSM BCCH RTF: None (0).
◦ EGSM 1 non-BCCH carrier: 64k (3).
◦ PGSM non-BCCH carrier: 32k (2).
◦ (HR enabled) PGSM non-BCCH carriers: 32k (2).
◦ EGSM 1 non-BCCH carrier: 16k (1).
{28075} Assuming sd_load of 2, sd_priority is the same for all the carriers, and PBCCH is not enabled, the
preferred number of SDCCH is 64, HR is enabled (at the BSS level and cell level, and at the carrier level
hr_allowed), the timeslot allocation is shown as illustrated.
The GPRS/EGPRS timeslots are configured contiguously for performance. The packet data time slots are
arranged as shown in the table below. The BCCH RTF is mapped to non-CTUII DRI and all the circuit
switched time slots are allocated to it. The EGPRS and GPRS time slots are allocated to non-BCCH carriers
as shown.
{28075}

BCCH (non-CTUII) B SD1 SD2 T T T T T
Non-BCCH 64K RE RE RE RE RE RE RE RE
(CTUII)
Non-BCCH 32K SD3 SD4 SG SG SG SG RG RG
(non-CTUII)
Non-BCCH 32K SD5 SD6 SG SG SG SG SG SG
(non-CTUII)
Non-BCCH 16K SD7 SD8 T SG SG SDG SDG SG
(non-CTUII)
3-164 68P02900W21-R
GMR-01 28 Feb 2006
Example 3
• pkt_radio_type set to: {28075}
◦ PGSM BCCH RTF: 64k (3) and PBCCH enabled with sd_priority = 255.
◦ PGSM 2 non-BCCH carriers: 32k (2) with sd_priority = 100.
◦ EGSM non-BCCH carriers: None (0) with sd_priority = 255.
◦ EGSM non-BCCH carrier: None (0) with sd_priority = 200.
• max_gprs_ts_carrier = 4.
{28075} Assuming sd_load of 2 for all the carriers, and PBCCH not enabled, preferred number of SDCCH
being 64, PBCCH is enabled (BSS level and cell level, and at the carrier level hr_allowed) the timeslot
allocation is shown as illustrated.

BCCH 64K (CTUII) B P T T RE RE RE RE
Non-BCCH 32K SD1 SD3 T T SG SG SG SG
(non-CTUII)
Non-BCCH 32K SD2 SD4 T T SG SG SG SG
(non-CTUII)
Non-BCCH 16K SD7 SD8 T T T T T T
(non-CTUII)
Non-BCCH 16K SD5 SD6 T T T T T T
(non-CTUII)
68P02900W21-R 3-165
28 Feb 2006 GMR-01
Example 4
◦ BCCH RTF: None (0).
◦ 2 non-BCCH carriers: 64k (3).
◦ 1 non-BCCH carrier: 32k (2).
◦ 1 non-BCCH carrier: None (0).
• Two CTUII and three non-CTUII.
• pccch_enabled = 1.
In this example, the BCCH carrier is not configured to be used as the carrier for GPRS/EGPRS. However,
since there are two CTUIIs available, BCCH is mapped to CTUII even though is not capable of supporting
EGPRS. Additionally, the non-BCCH carrier configured with 64k backhaul is not used for packet data.
PCCCH, however, is always allocated on the BCCH carrier. Therefore, on the BCCH carrier, TS2 is allocated
to PCCCH and TS3 to TS7 is allocated to circuit-switch TCH only.
The PCCCH timeslot counts as one of the reserved timeslots.

BCCH 16K (CTUII) B SD P T T T T T
Non-BCCH 64K RE RE RE RE RE RE RE RE
(CTUII)
Non-BCCH 64K T T T T T T T T
(non-CTUII)
Non-BCCH 32K SG SG SG SG SG SG SG SG
(non-CTUII)
(non-CTUII)
3-166 68P02900W21-R
GMR-01 28 Feb 2006
Example 5
◦ BCCH RTF: 64k (3).
◦ 3 non-BCCH carriers: None (0).
• Three CTUII and three non-CTUII.
• Two (AMR or {22064} GSM) half-rate enabled carriers.

BCCH 64K (CTUII) B SD RE RE RE RE RE RE
Non-BCCH 64K SE SE SE SE RE RE RE RE
(CTUII)
(CTUII)
(non-CTUII)
Non-BCCH 16K (hr T T T T T T T T
enabled) (non-CTUII)
68P02900W21-R 3-167
28 Feb 2006 GMR-01
Example 6
There are 4 switchable EGPRS timeslots and 4 reserved EGPRS timeslots in a 4 carrier cell. The following
are assumed:
• pkt_radio_type set to BCCH RTF 64k (3).
• 3 non-BCCH carrier: 64k (3).
• 3 CTUIIs.
• EGPRS unrestricted.
BCCH 64K (CTUII) B SD SE SE RE RE RE RE
Non-BCCH 64K SE SE SE SE RE RE RE RE
(CTUII)
(CTUII)
Non-BCCH 64K T T T T T T SE SE
(CTUII)
3-168 68P02900W21-R
GMR-01 28 Feb 2006
{23769} Example 7
The following are assumed
◦ BCCH RTF: 64k (3), rtf_ds0_count = 4.
◦ 1 non-BCCH carrier: 64k (3), rtf_ds0_count = 5.
◦ 3 non-BCCH carriers: None (0).
• Three CTUII and three non-CTUII.
• GPRS 32K and VersaTRAU (and therefore EGPRS) unrestricted.
• Two (AMR or {22064} GSM) half-rate enabled carriers.

BCCH 64K (CTUII) B SD RE RE RE RE RE RE
Non-BCCH 64K SE SE RE RE RE RE RE RE
(CTUII)
(CTUII)
(non-CTUII)
68P02900W21-R 3-169
28 Feb 2006 GMR-01
{28075} Example 8
The following are assumed:

◦ BCCH RTF: 64k (3), rtf_ds0_count = 6
◦ 1 non-BCCH carrier: 64k (3), rtf_ds0_count = 6.
• One CTUII (DDM)
• EGPRS and VersaTRAU unrestricted.
• pccch_enabled = 1.
BCCH 64K (CTUII DD B SD P T SE RE RE RE
Carrier A)
Non-BCCH 64K SG SG X SG X X X X
(CTUII DD Carrier
B)
Non-BCCH 64k are downgraded to 16k.

The maximum PDs configuration for two carriers of DD CTU2 is 8 if Carrier A has EGPRS PDs. The
requested 9 PDs can not be all met.
3-170 68P02900W21-R
GMR-01 28 Feb 2006
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 packet data mobile and a
circuit-switched call is requested after all other circuit switched timeslots are used, the BSS takes the timeslot
away from the packet data mobile and gives it to the circuit-switched mobile, except when the switchable
timeslot to be stolen is the last packet data timeslot in the cell and the protect_last_ts element is enabled.
The switchable timeslot is re-allocated back to the packet data mobile when the circuit switched call ends. The
number of reserved packet data timeslots can be changed by the operator in order to guarantee a minimum
number of dedicated packet data timeslots at all times. The operator provisions the packet data 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 packet data timeslot and the number of idle circuit-switched
timeslots is greater than an operator defined threshold, the BSS re-allocates the borrowed timeslot for
packet data 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 packet data service, even if it is the last available timeslot
for packet data 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 packet data 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 packet data 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 packet data 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 packet data timeslots are stolen starting with the lowest numbered GPRS timeslot on a carrier to
maintain continuous packet data timeslots.
The BSS selects which switchable packet data timeslot is stolen based on {23769} an algorithm that takes
into account the pkt_radio_type (GPRS/EGPRS capability), the associated RTF backhaul (configured as
rtf_ds0_count for EGPRS capable carriers if VersaTRAU is unrestricted or statically computed in other cases
depending on the pkt_radio_type) and the number of switcahble/reserved timeslots already on the carrier. A
rank order based on the backhaul to PDTCH ratio shall be established at the time of the initial air timeslot
allocation. This rank order is also used at the time of allocating the reserved and switchable timeslots in the
cell. The switchable timeslots are the ones that result in the least degradation in the backhaul to PDTCH ratio
for the cell when they get stolen for voice traffic.
68P02900W21-R 3-171
28 Feb 2006 GMR-01
When (AMR or {22064} GSM) half rate is enabled on one or more (RTFs assigned to) carriers in a cell and
some number of timeslots are reserved for half rate usage (hr_res_ts), then the BSS will attempt to ensure that
the last timeslots to be allocated within a cell are half rate capable. Therefore switchable timeslots will be
allocated to full rate calls prior to the reserved half rate capable timeslots (the only exception to this being
when the only available resource able to support the full rate request is the last GPRS/EGPRS timeslot,
and the “protect last ts" functionality is enabled).
{28075} When the ITS feature is unrestricted and enabled and a voice call steals one EGPRS PD timeslot
on a DD CTU2 Carrier A, the corresponding blanked-out timeslot on Carrier B comes back into service. If
the stolen EGPRS timeslot on DD CTU2 comes back to PDCH, the corresponding blanked-out timeslot on
Carrier B is configured back to OOS.
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/EGPRS timeslots
for multislot GPRS/EGPRS operation {23769} and at the same time maintain an optimum ratio of
PDTCH/available backhaul per carrier across the cell. 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/EGPRS reserved
(see Figure 3-80). When the BSS needs to re-allocate a switchable timeslot from GPRS/EGPRS mode to
circuit-switched mode, the BSS assigns timeslot 3 before it assigns timeslot 4 for circuit-switched mode.
Figure 3-80 provides a timeslot allocation with reserved and switchable timeslots.
Figure 3-80 Carrier with reserved and switchable GPRS/EGPRS timeslots
S S R R R
TS0 TS7
R: Reserved PDTCH.
S: Switchable PDTCH.
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/EGPRS timeslot (from lowest to highest).
3. In-service circuit-switched.
4. Idle or in-service reserved GPRS/EGPRS timeslot (from lowest to highest).
3-172 68P02900W21-R
GMR-01 28 Feb 2006
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/EGPRS service. This flexibility is in the form of additional available
network capacity to both the circuit-switched and GPRS/EGPRS 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/EGPRS
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/EGPRS 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-17 and Table 3-18 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-81. The second carrier is a
carrier with GPRS/EGPRS timeslots; all eight timeslots are configured as switchable, as shown in Figure 3-82.
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/EGPRS 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/EGPRS timeslots.
AMR or {22064} GSM half rate usage should be considered when determining the number of circuit switched
timeslots required. Two half rate circuit-switched calls can be carried in a single timeslot (provided of course
that the (RTF assigned to) carrier is half rate enabled). The number of actual (circuit-switched) calls that can
expect to be using half rate will depend upon such factors as operator (both BSS and MSC) preference, mobile
(AMR capable, {22064} GSM half rate) penetration, mobile preference, RF conditions, handoff parameter and
threshold setting, cell congestion levels, etc. Once an estimate of half rate usage is determined, it can be used to
determine if the GOS can be met. Table 3-18 and Table 3-19 show two examples using half rate assumptions.
68P02900W21-R 3-173
28 Feb 2006 GMR-01
Table 3-18 Switchable timeslot utilization (Part A)
Total no. of
No. of
circuit switched
Planned circuit switchable
timeslots
GOS switched timeslots Comments
required,
Erlangs/cell necessary to
including
provide GOS
switchable
2% 2 6 0 Outside busy hour
time periods,
the carrier most
likely carries only
packet data traffic.
Therefore, packet
data 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 approx. 0.1%.
2% 3 8 2 During the
circuit-switched
busy hour, 2 of
the switchable
timeslots are
occasionally used
by the circuit
switched side of
the network in an
attempt to provide
the 2% GOS.
Cont.
3-174 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-18 Switchable timeslot utilization (Part A) (Continued)

Total no. of
No. of
circuit switched
timeslots
required,
including
provide GOS
switchable
0.1% 3 10 4 During the
circuit-switched
busy hour, 4 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 approx. 0.1%.
2% 4 9 3
0.1% 4 12 6
2% 5 10 4
0.1% 5 14 8 All the switchable
timeslots are
occasionally used
to provide the 0.1%
GOS.
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
enough switchable
the 0.1% GOS.
2% 8 14 8 All the switchable
timeslots are
occasionally used
to provide the 2%
GOS.
enough switchable
the 0.1% GOS.
68P02900W21-R 3-175
28 Feb 2006 GMR-01
Table 3-19 Switchable timeslot utilization (Part B)
Total no. of
No. of
circuit switched
timeslots
required,
including
provide GOS
switchable
2% 9 15 9 There are not
enough switchable
the 2% GOS
enough switchable
the 0.1% GOS.
2% 9 10 * 4 Assumption is
100% half rate
utilization, and all
carriers are capable
of half rate.
0.1% 8 14 ** 8 All of the
switchable
timeslots are
occasionally used
to satisfy the 2%
GOS. Assumption
is 50% half rate
utilization, and all
carriers are capable
of half rate.
* 20 half rate calls @ 2 subchannels per timeslot = 10 timeslots.

** 9 full rate calls (9 timeslots) + 9 half rate calls (5 timeslots) = 14 timeslots.
3-176 68P02900W21-R
GMR-01 28 Feb 2006
Timeslot allocation for 2 carrier site (1 circuit-switched + 1 GPRS/EGPRS)

Figure 3-81 shows one circuit-switched carrier with one BCCH/CCCH timeslot, one SDCCH timeslot,
and six TCH timeslots.
Figure 3-81 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-82 shows one carrier for GPRS/EGPRS traffic with all timeslots (8 TCHs) designated as switchable.
Figure 3-82 One carrier, all timeslots (8 TCHs) designated as switchable
S S S S S S S S
TS0 TS7
S: Switchable TCH.
Table 3-17 and Table 3-18 shows the switchable timeslot utilization.
68P02900W21-R 3-177
28 Feb 2006 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 packet data 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 packet data 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 packet data traffic. This ensures that there is a
minimum guaranteed network capacity for the 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 packet data network. Therefore, in the circuit-switched off busy hours, potentially all switchable
timeslots could be available for the packet data 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 packet data 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 packet data portion of the network in order to guarantee a minimum packet
data quality of service (QoS) as measured by packet data 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 packet data traffic during the
circuit-switched portion of the network busy hour. Provision enough reserved timeslots for packet data
traffic during the circuit-switched busy hour to meet the desired minimum packet data QoS objectives, as
measured by packet data throughput.
3-178 68P02900W21-R
GMR-01 28 Feb 2006
Timeslot allocation process on carriers with GPRS traffic
The following process is proposed when determining how best to allocate GPRS/EGPRS timeslots.
Step 1: Estimate reserved timeslot requirements

Determine how many reserved GPRS/EGPRS timeslots are needed on a per cell basis in order to satisfy a
packet data throughput QoS. Note that the use of PBCCH in a cell requires at least one reserved GPRS/EGPRS
timeslot in that cell. The GPRS/EGPRS 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/EGPRS timeslots are needed on a per cell basis. The use of switchable
timeslots can potentially offer increased capacity to both the GPRS/EGPRS 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/EGPRS timeslots to satisfy the circuit
switched GOS objectives and the timeslot requirement overlaps with the number of reserved GPRS/EGPRS
timeslots, consider adding another circuit-switched carrier to the cell.
Step 4: Monitor network statistics

After deploying the GPRS/EGPRS timeslots on the cell, review the collected network statistics on a continuous
basis in order to determine whether the reserved GPRS/EGPRS timeslots, switchable GPRS/EGPRS 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 packet data
traffic as long as the demand for these timeslots is staggered in time.
68P02900W21-R 3-179
28 Feb 2006 GMR-01
GPRS/EGPRS air interface planning process Chapter 3: BSS cell planning
GPRS/EGPRS air interface planning process

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Influential factors in GPRS/EGPRS cell planning and deployment
The planning and dimensioning of a system containing packet data users is not as straightforward as a system
populated with only circuit switched users. Sophisticated tools are required to properly model the behaviour
of packet data users and dimension the required bandwidth for a given service mix. In GSM, the issues are
further complicated when EGPRS is introduced in an existing GSM network which also supports GPRS.
A generic planning and dimensioning process is shown in Figure 3-83. The main objectives are to minimise
the number of sites and time slots (spectrum) to support a given packet data users load at an acceptable QoS
without compromising the QoS of voice users. Acceptable QoS for the packet data users with best effort type
service is qualified by the delay experienced. This should be at least similar to those experienced while using
the normal wired line analogue modems.{23956} The QoS feature allows the system to differentiate between
subscribers on the basis of the QoS level subscribed to or negotiated by the system.
Figure 3-83 Generic planning and dimensioning process
Number of subscribers Cell sizes

(GPRS/EGPRS split) Traffic characterisation
RF cell planning Number of cells
Area to cover coverage TS requirements
requirements BTS dimensioning
TS dimensioning BSS requirements
RF Information Interface requirements
Traffic Profile and Service mix BSS dimensioning
QoS requirements Interface dimensioning
Bandwidth available
Network configurations
RLC/MAC overheads
Input parameters Planning tools Output parameters
At a high-level the cell planning and deployment can be broken down into two activities, which become
inter-related depending on the traffic volumes supported and bandwidth available. These are cell coverage and
cell dimensioning. In addition, there are some deployment rules that may be applied if there is sufficient
flexibility in the choice of carrier and segregation of time slots; this depends on the network configuration.
Issues and influential factors that should be consider in carrying out the process shown are qualified.
3-180 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning GPRS/EGPRS air interface planning process
Network configuration
Network configurations in which packet data (GPRS or EGPRS) may be introduced include:
• Existing GSM network with GPRS already deployed.
• Existing GSM network without GPRS.
• Rolling out a new GSM network with or without GPRS.
• A new GSM based packet data system only.
Of these, the first configuration is the most likely deployment and the most challenging one. The second one
dictates mass GPRS and/or EGPRS handset deployment to justify its deployment. The last two configurations
are less of concern as they can be fine tuned to provide adequate coverage and grade of service. So, only
the first configuration is considered.
RF cell planning (cell coverage)

The degree of coverage per GPRS and EGPRS coding scheme varies depending on several factors including:
• Spectrum availability.
• Re-use patterns: hopping or non-hopping.
• Environment: as the radio conditions change the subsequent C/I (C/N) requirements at a
given BLER will change.
• BTS power amplifier capability and how it maybe set for GMSK and 8-PSK modes.
• Cell sizes and cell border design criteria.
• BSS algorithms (for example, LA).
68P02900W21-R 3-181
28 Feb 2006 GMR-01
Also, as a general rule, EGPRS can be introduced in an existing GSM network with full EGPRS coverage.
The following should be noted:
• {23956} When the QoS feature is not enabled, the system will employ the best effort packet
data services (no high QoS requirements will be supported) with RLC acknowledge mode
(ARQ). As such, the choice of operating BLER point is flexible within a certain range.
In Motorola’s implementation acceptable BLER operating point is embedded in the LA
algorithms for GPRS and EGPRS.
• {23956} When the QoS feature is enabled, the BSS is able to assign a MTBR per PFC.
This allows the system to reserve throughput at the Local Timeslot Zone (Cell Level) and
PRP (board level).
• CS1 and MCS-1 have been designed such that they match the voice coverage footprint. In
addition, due to IR in EGPRS, higher operating BLERs can be tolerated.
• The higher the operating BLER the higher the coverage per GPRS/EGPRS coding scheme.
However, the operating BLER cannot be excessive since it has undesirable consequences
on system capacity and as such impacts the number of users that can be supported. In
Motorola’s implementation, the LA algorithm attempts to maximise the throughput while
keeping implicitly the BLER operating regions within an acceptable bound in order not to
degrade the overall system performance.
• The PA output power capability does not impact the EGPRS availability at cell borders since
power difference in HPM applies only to 8-PSK modulated coding schemes. This, however,
leads to less coverage (lower C/I or C/N) for higher code rates and impacts the system capacity.
• Frequency re-planning may be required not so much to guarantee GPRS/EGPRS coverage

but more to eliminate possible coverage degradation for voice users. In a conventional GSM
voice network, the frequency planning of the traffic carriers are based on assuming certain
activity factors (DTX). When GPRS/EGPRS are introduced the level of interference might
go up because of the following:
◦ Higher activity. This depends on how the timeslot dimensioning is carried out to account
for packet data users. If time slots are driven hard, then the level of activity can be higher
than that assumed for the voice only system. Also due to behaviour of packet data users
being different, data flow control throughout the network, multiplexing of users on the
same time slot, the activity profile will be different. As such, to maintain the same quality
of service for the voice users mean loading due to packet data users will require scaling.
◦ 8-PSK signal peak to average ratio (PAR): due to 8-PSK envelop variation, the GMSK
symbols may be occasionally hit with higher interference than usual when average power
of GMSK and 8-PSK signals are set to be the same. However, the level of degradation
has to be considered within the context of the likely degradation that may encounter
otherwise as a result of having a lower average power in the 8-PSK mode (thus reducing
the impact of PAR). It is envisaged that impact of lower average power prevails the
impact of PAR, and as such it is recommended to have the average powers in GMSK
and 8-PSK modes set equal.
3-182 68P02900W21-R
GMR-01 28 Feb 2006
Cell/time slot dimensioning

The following influence cell/TS dimensioning since they impact throughput per TS as well as the apparent
throughput seen by a user, that is, pipe size:
• Types of services, applications, and volume of data that are to be supported.
• QoS required (user experience).
• Number of users multiplexed on the same time slot.
• Multiplexing of GPRS and EGPRS users on the same time slot.
• Signalling overhead (control channels).
• RLC/MAC protocols parameters setting.
• Multi-slot operation.
• {23956} QoS feature enable or disabled.
• Cell selection/re-selection.
• Hardware limitations, for example, number of time slots supported per cell.
• Re-use pattern: BCCH carrier, FH carrier.
Of the influences listed, the last two can be easily dealt with while the remaining ones require detailed
investigation, through simulation, to fully quantify their impacts. The following shed light on some of the
issues that may be encountered:
• {23956} If QoS is enabled, the number of PDTCHs required to support the MTBR specified
may be different than when QoS is disabled. The BSS treats all mobiles equally when
scheduling the air interface in a QoS disabled environment.
• Volume of data will have varying impacts on system capacity. Short messages will not benefit
from higher code rates for those users in good radio conditions since LA process requires
time to converge to higher code rates. Moreover, RLC protocols, such as TBF holding time,
will degrade the capacity for short messages. As a general rule, the throughput seen in
practice is lower than the ideal throughput for short messages and will be closer to the ideal
throughput for long messages.
68P02900W21-R 3-183
28 Feb 2006 GMR-01
• Up to 4 users can be multiplexed on a time slot. Depending on system loading the apparent
bit pipe seen by a user is subsequently reduced, see Figure 3-84. In addition, this could
impact the throughput per time slot since the LA process suffers due to variation of radio
channel conditions between scheduling opportunities. Thus, even for long messages the ideal
throughput would be hardly achieved. In Motorola’s implementation, there is an intelligent
load management algorithm in the PCU that attempts to balance the load across resources
allocated to the packet data users. This will improve the overall system and users’ QoS
performance depending on the bandwidth provisioned for the packet data users. {23956} The
QoS feature extends this general concept to provide per traffic class MTBR.
Figure 3-84 Multiplexing 4 TBFs on an air timeslot
4 TBFs/TS
User 1
User 2
User 3
80ms
User 4
20ms block
Time
• Multiplexing of GPRS and EGPRS users on the same time slot is possible. The only impact is
slight degradation in QoS of GPRS users in the uplink direction. This is due to GPRS users
being unable to decode their block allocations in the uplink when downlink transmission is in
8-PSK. However, this is not such a big issue since in Motorola’s implementation, the PCU
scheduler algorithm is designed to minimise this clash as well as the bottleneck is generally
downlink for packet data transmissions.
• RLC protocols such as TBF holding time, poll period (to receive measurement reports and
Ack/Nack status of the transmitted blocks), RLC Ack/Nack window size, etc., will impact the
throughput per time slot and as such number of users that can be supported.
3-184 68P02900W21-R
GMR-01 28 Feb 2006
• The operating BLER is an important parameter in optimizing the end-to-end throughput.

The higher the operating BLER the higher the coverage per GPRS/EGPRS coding scheme.
However, the operating BLER cannot be excessive since it has undesirable consequences on
system capacity and as such impacts the number of users that can be supported. For example,
although IR enables MCS-9 throughput to be similar to other coding schemes at low C/I
values, but the corresponding BLER will be quite high. This from system viewpoint could
have detrimental effects due to the RLC protocol operation such as those in the last bullet
points. In Motorola’s implementation, the LA algorithm attempts to maximise the throughput
while keeping implicitly the BLER operating regions within an acceptable bound in order not
to degrade the system performance.
• If PCCCH is enabled, time slot dimensioning for packet data traffic should consider the
blocks used for control signalling.
{23956} QoS Dimensioning

The two most significant factors that influence quality of a service are:
• Delay
• Throughput
In R99 and beyond, four traffic classes are defined to accommodate the need for different levels of these
factors for different applications. These are:
• Conversational
• Streaming
• Interactive
• Background
The BSS has internally defined additional traffic classes created by grouping similar PFC characteristics. The
internally defined traffic classes are:
• Short-Term Non-Negotiated Traffic (STNNT)
• Pre-admission PFC (PAP)
• QoS Disabled
Due to the fact that the specification for conversational and streaming is still evolving, the BSS is
implementing differentiation of service among interactive and background traffic classes. Requests to
create packet flows for streaming or conversational mode are treated as interactive traffic flows. Support
for streaming or conversational traffic class at the BSS is limited in its scope; that is,. streaming and
conversational traffic classes get QoS of Interactive Traffic class when admitted. However, the BSS does not
make any guarantees regarding sustaining applications using the streaming and conversational traffic classes
68P02900W21-R 3-185
28 Feb 2006 GMR-01
Traffic handling priority (THP)

Three priorities are defined in the standards for handling the traffic pertaining to the interactive traffic
class only. For the BSS, these priorities determine relative throughput assigned to a particular Packet Flow
Context (PFC). This is achieved by applying relative weights for each priority, defined at a BSS level.
These weights are operator configurable.
In addition to the three standardized priorities, a fourth and a fifth THP are defined internally by the BSS for
the background and best effort traffic classes respectively. The assigned weights for these internally defined
THPs act relative to the three THPs that are defined for the interactive traffic class by the standards.
THP provides a mechanism to differentiate services among different PFCs that may or may not belong
to the same user.
Minimum throughput budget requirement (MTBR)

A Minimum Throughput Budget Requirement (MTBR) is non-standards based BSS parameter associated with
each PFC. The MTBR of a given TBF is the sum of MTBRs of all the PFCs that are multiplexed on that TBF.
MTBR allows the BSS to admit each PFC if a minimum budget for resources can be met. The MTBR is
subjected to a minimum of 2Kbps for each admitted PFC. The operator is allowed to configure the minimum
throughput budget requirement in both the uplink and downlink directions separately.
MTBR is measured as raw air throughput at the RLC/MAC layer without factoring in the Block Error
Rate (BLER) and unsolicited retransmissions. It is not a guaranteed bitrate. MTBR is merely a budgeting
guideline for the admission control mechanism. This helps to ensure no more users are admitted than the
system can handle without compromising service.
MTBR will not be achieved by a TBF with insufficient data to transmit.
MTBR is set and regulated in terms of throughput at the RLC/MAC layer. Throughputs at the application layer
will be lower than the RLC/MAC throughput due to overhead consumed by the headers and retransmissions
at the intermediate layers and the application layer. Table 3-20 shows typical TCP throughput for each 10
Kbps of RLC/MAC throughput at zero block error rate. Notice that the TCP throughput depends upon the IP
packet size and the LLC PDU size. Several typical values are shown.
Table 3-20 Typical TCP throughput versus RLC/MAC throughput at zero block error rate
RLC/MAC LLC PDU size Typical TCP

IP packet size (octets)
throughput (kbps) (octets) throughputs (kbps)
10.0 1500 1508 8.73
10.0 1500 600 8.33
10.0 576 604 8.28
Admission control and retention

Allocation/Retention Priority (ARP) is defined in specification 3GPP TS 23.107 Quality of Service (QoS)
concept and architecture, version 4.6.0 Release 4 as a QoS attribute, maintained per PFC, that provides
prioritized allocation and retention. It is a subscription parameter, meaning non-negotiable by the network
entities.
3-186 68P02900W21-R
GMR-01 28 Feb 2006
ARP ranges from 1 to 3 with 1 being the highest priority. The BSS maps the ARP parameter and the traffic
class into ARP Rank, as shown in Table 3-21. The BSS uses ARP Rank to determine which PFCs have
priority access to the system. ARP Rank 6 is higher priority than ARP Rank 1.
Table 3-21 ARP mobile selection (ARP Rank) order
Best Back
ARP value THP 1 THP 2 THP 3
effort ground
1 6 6 6 6 3
2 5 5 5 5 2
3 4 4 4 4 1
Admission Control determines which PFCs get access to the system and which PFCs get pre-empted from the
system to make room for higher ARP Rank PFCs.
For a complete description of allocating resources at the cell and PRP level, see Chapter 8, "PCU upgrade for
the BSS,", "{23956} QoS capacity" on page 8-43.
Estimating the air interface traffic throughput
The GPRS/EGPRS data throughput estimation process given in this chapter is based upon the Poisson process
for determining the GPRS/EGPRS mobile packet transfer arrivals to the network and for determining the size
of GPRS/EGPRS data packets generated or received by the GPRS/EGPRS 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/EGPRS traffic, it is
proposed in this planning guide to limit the mean GPRS/EGPRS cell loading value to 50% of the system
capacity. Using this cell loading factor has the following advantages:
• Cell overloading due to the bursty nature of GPRS/EGPRS traffic is minimized.
• The variance in file transit delay over the Um to Gi interface is minimized such that the
delay can be considered a constant value for the purposes of calculating the time to transfer
a file of arbitrary size.
LAN/WAN wireline studies have also shown that even when statistically valid studies are performed, the
results come out very different in follow-up studies. It turns out that web traffic patterns are very difficult to
predict accurately and, therefore, it is highly recommended that the network planner makes routine use of
the GPRS/EGPRS 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/EGPRS timeslots that should be provisioned on a per cell basis.
68P02900W21-R 3-187
28 Feb 2006 GMR-01
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.
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 GPRS/EGPRS data rates. The cell plan that is chosen for GPRS/EGPRS 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/EGPRS 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 coding scheme in order to maximize the data throughput on a per mobile
basis. The coding scheme 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/EGPRS timeslots.
To demonstrate the performance of various GPRS and EGPRS coding schemes, Table 3-22 shows the
percentage utilisation of GPRS and EGPRS coding schemes at a fixed operating BLER of 20% in a 4x3
BCCH (non-hopping) re-use pattern, and under a TU channel condition. 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.
{23956} When the QoS feature is enabled, the timeslot zone and PRP board level headroom
compensate for BLER.
3-188 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-22 Utilisation of coding schemes
% of code utilisation in a 4x3 non-hopping re-use pattern at 20% BLER

Coding scheme % of code utilisation
CS1 15
CS2 14
CS3 20
CS4 51
MCS-1 2
MCS-2 6
MCS-3 2
MCS-4 0
MCS-5 5
MCS-6 14
MCS-7 12
MCS-8 9
MCS-9 50
68P02900W21-R 3-189
28 Feb 2006 GMR-01
Step 2: Estimate timeslot provisioning requirements

Step 2 determines the number of GPRS/EGPRS timeslots that need to be provisioned on a per cell basis.
Timeslot provisioning is based on the expected per cell mean GPRS/EGPRS traffic load, as measured in kbit/s.
The packet data traffic load includes all SMS traffic routed through the GSN. The SMS traffic is handled by
the GPRS/EGPRS 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 (totally segregated EGPRS and GPRS timeslots):
_ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _ _
No_PDTCH_TS includes the PCCCH timeslot when PCCCH is enabled in the cell.
• 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.
• {23956} The Mean_load_factor of 50% has been applied to the traffic load for systems
without the QoS feature enabled to account for any surges in the data traffic and to
carry packet switched signalling traffic. For systems with the QoS feature enabled the
Mean_load_factor can be used to take into account when multiple QoS enabled mobiles are in
a cell at the same instance. Allocating more PDTCHs has the effect that QoS mobiles will not
be downgraded during peak usage at a cell.
3-190 68P02900W21-R
GMR-01 28 Feb 2006
Mean_traffic_load for each cell can be calculated using the following formulae:
_ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _ _ _ _ _ _
The units for Data_per_sub_per_session is kbytes/hr.

{23956} For systems without the QoS feature enabled:
_ _ _
_ _ _
_ _ _
_ _ _
{23956} For systems with the QoS feature enabled:
_ _ _ _
_ _ _ _
(M)CS_USAGE are the percentage of usage of (E)GPRS coding schemes.
68P02900W21-R 3-191
28 Feb 2006 GMR-01
Number of timeslots
{23956} The number of PDTCH 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.
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. It is possible, however, to transfer packet switched data on each
of the 1080 timeslots of a PCU simultaneously (assuming that all 9 PRPs are configured). 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.
{23956} 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 packet
data timeslots for instance, another cell operating below its mean load averages out the packet data traffic
load at the PCU.
Up to 3 PCUs may be managed by a BSC. If 3 PCUs are configured, the number of timeslots increases by a
factor of 3. Thus, it will be possible to transfer packet switched data on each of the 3240 (1080 per PCU for 3
PCUs) and 1080 timeslots simultaneously for GPRS and EGPRS respectively. Depending on the mix of
GPRS and EGPRS time slots usage, the number of time slots available for packet data users is, therefore,
between 1080 (all EGPRS) and 3240 (all GPRS). Multiplexing of timeslots occurs as described above on a per
PCU basis, for a maximum of 810 (270 per PCU for 3 PCUs) active timeslots at any instance in time. For
example, if there are MSs on each of 3240 timeslots provisioned on the air interface, each PCU will process
timeslots in 3 sets of 270 timeslots, making for a total of 810 timeslots.
PCUs may be added to a BSC for capacity as well as redundancy. When a PCU is added, the operator may
migrate cells from the existing PCU to the new PCU to balance the anticipated traffic load. If redundancy is
desired, the operator may designate a first and (optionally) second redundant PCU. If a PCU that has cells
mapped to it (the primary PCU) becomes unavailable, the cells will be remapped to the first (or second if the
first is also unavailable) redundant PCU. This migration of cells is managed by the BSC.
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-192 68P02900W21-R
GMR-01 28 Feb 2006
{23956} Timeslot Refinement with QoS Enabled

The number of PDTCHs determined above for support of QoS should be compared to the examples given
below. The examples should be consulted to determine a refined number of PDTCHs to support QoS with a
given set of configuration parameters.
Table 3-23 MTBR Mix
MTBR Mix
% DL UL
I1 14 2
I2 10 2
I3 4 2
BG 2 2
BE 2 2
Table 3-24 MTBR Constant
MTBR Constant
% DL UL
I1 2 2
I2 2 2
I3 2 2
BG 2 2
BE 2 2
Table 3-25 THP Weight Mix
THP Weight Mix

I1 40
I2 40
I3 20
BG 20
BE 20
Table 3-26 THP Weight Constant
THP Weight Constant

I1 40
I2 40
I3 40
BG 40
BE 40
68P02900W21-R 3-193
28 Feb 2006 GMR-01
Table 3-27 QoS Configuration Examples
Number of PFCs
admittted (valid
for MTBR/THP
mix only)
Mobile Sub- Subs
THP Trau
QoS PDTCHs Multi- slot scriber MTBR allowed on I1 I2 I3 BG BE
Weight Type
Class Mix Carrier
No 6 NA 4 16/32 No NA 18
MTBR
Yes 2 Constant 4 64 3DL/1UL Mix 14 1 1 1 1
Yes 3 Constant 4 64 3DL/1UL Mix 7 1 1 1 4
Yes 4 Constant 4 16/32 3DL/1UL Mix 5 1 2 1 1
Yes 6 Constant 10 16/32 4DL/1UL Mix 8
Yes 6 Constant 4 16/32 3DL/1UL Con- 11
stant
stant
Yes 6 Mix 10 16/32 4DL/1UL Con- 8 1 3 4
stant
Yes 6 Mix 10 64 4DL/1UL Con- 8 1 3 4
stant
Yes 6 Constant 4 16/32 3DL/1UL Mix 10 1 1 1 1 6
Yes 6 Mix 10 16/32 4DL/1UL Mix 4 1 1 1 1
Yes 6 Mix 10 64 4DL/1UL Mix 10 1 1 1 3 4
stant
stant
stant
3-194 68P02900W21-R
GMR-01 28 Feb 2006
Comparison: Number of Class 4 Mobiles in a Cell with 6 PDTCHs; TRAU = 16K, all THP weight =
40, MTBR = 2
Table 3-28 and Table 3-29 show the impact of QoS on the number of PDTCHs required to support a given
traffic mix. The colored cells highlight the additional mobile being added for the specified time period.
Table 3-28 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS
Mo-
2 3 4 5 6 7 MS per TS
biles
1 0 0 0 33 33 33 DL 0.50
0 0 0 0 100 0 UL
2 33 33 33 33 33 33 DL 1.00
0 100 0 0 100 0 UL
3 33 33 33 333 83 83 DL 1.33
0 100 0 0 100 100 UL
4 33 33 83 83 83 83 DL 1.67
0 100 0 100 100 100 UL

5 133 33 83 83 83 83 DL 1.83
100 100 0 100 100 100 UL
6 133 133 83 83 83 83 DL 2.00
100 200 0 100 100 100 UL
7 133 133 183 83 83 83 DL 2.17
100 200 100 100 100 200 UL
8 133 133 183 83 183 83 DL 2.33
100 200 100 100 200 200 UL
9 133 133 183 183 183 83 DL 2.50
100 200 100 200 200 200 UL
10 133 133 183 183 183 183 DL 2.67
100 200 100 200 200 300 UL
11 233 133 183 183 183 183 DL 2.83
200 200 100 200 200 300 UL
12 233 233 183 183 183 183 DL 3.00
200 300 100 200 200 300 UL
13 233 233 283 183 183 183 UL 3.17
200 300 200 200 200 300 UL
Cont.
68P02900W21-R 3-195
28 Feb 2006 GMR-01
Table 3-28 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS (Continued)
Mo-
2 3 4 5 6 7 MS per TS
biles
14 233 233 283 183 283 183 DL 3.33
200 300 200 200 300 300 UL
15 233 233 283 283 283 183 DL 3.50
200 300 200 300 300 300 UL
16 233 233 283 283 283 283 DL 3.67
200 300 200 300 300 400 UL
17 333 233 283 283 283 283 DL 3.83
300 300 200 300 300 400 UL
18 333 333 283 283 283 283 DL

300 400 200 300 300 400 UL
19 333 333 283 283 283 283 DL

300 400 200 300 300 400 UL
20 333 333 283 283 283 283 DL
300 400 200 300 300 400 UL
21 333 333 283 283 283 283 DL

300 400 200 300 300 400 UL
22 333 333 283 283 283 283 DL
300 400 200 300 300 400 UL
23 333 333 283 283 283 283 DL
300 400 200 300 300 400 UL
Table 3-29 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS
Mo-
2 3 4 5 6 7 MS per TS
biles
1 0 0 0 33 33 33 DL 0.50
0 0 0 0 100 0 UL
2 33 33 33 33 33 33 DL 1.00
0 100 0 0 100 0 UL
3 33 33 67 67 67 33 DL 1.50
0 100 0 100 100 0 UL
Cont.
3-196 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-29 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS (Continued)
Mo-
2 3 4 5 6 7 MS per TS
biles
4 83 83 67 67 67 333 DL 1.83
100 100 0 100 100 0 UL

5 83 83 67 67 117 83 DL 2.17
100 100 0 100 100 100 UL
6 83 117 100 100 117 83 DL 2.67
100 100 100 100 100 100 UL
7 83 117 150 150 117 83 DL 3.00
100 100 100 200 100 100 UL
8 83 117 150 150 167 133 DL 3.33
100 100 100 200 100 200 UL
9 133 167 150 150 167 133 DL 3.67
100 200 100 200 100 200 UL
10 133 167 150 150 167 233 DL 3.83
100 200 100 200 100 300 UL
11 233 167 150 150 167 233 DL 4.00
200 200 100 200 100 300 UL
12 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
13 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
14 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
15 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
16 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
17 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
18 233 167 150 150 167 233 DL

200 200 100 200 100 300 UL
Cont.
68P02900W21-R 3-197
28 Feb 2006 GMR-01
Table 3-29 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS (Continued)
Mo-
2 3 4 5 6 7 MS per TS
biles
19 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
20 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
21 233 167 150 150 167 233 DL

200 200 100 200 100 300 UL
22 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
23 233 167 150 150 167 233 DL
200 200 100 200 100 300 UL
3-198 68P02900W21-R
GMR-01 28 Feb 2006
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/EGPRS 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-85 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-85 LLC_PDU frame layout
7 2 20 20 4
LLC SNDCP IP TCP APPLICATION CRC
64 BYTES < L < 1580 BYTES
68P02900W21-R 3-199
28 Feb 2006 GMR-01
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:
_ _
_
_ _ _
Where: is:
File_size_LLC 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.
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-200 68P02900W21-R
GMR-01 28 Feb 2006
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:
Where: is:
FTD 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 for
various GPRS and EGPRS code
rates.
mslot the mobile multislot operating
mode; the value can be from 1 to
4.
CSBLER the BLER for the specific coding
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 based on downlink commands transmitted at a frequency varying between
2 and 12 RLC blocks. It is expected that the downlink acknowledgement messages will not significantly
effect the file transit delay in the downlink direction.
68P02900W21-R 3-201
28 Feb 2006 GMR-01
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 PDTCH, DL, mean
LLC_PDU packet size of 435 bytes.
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: is:
File_size_LLC = 3106 bytes
(as calculated in the previous
example).
CS2 payload = 30 bytes.
Air time for one RLC/MAC block = 0.02 seconds.
(1 + CSBLER) = 1.1.
Multislot operation = 1.
3-202 68P02900W21-R
GMR-01 28 Feb 2006
Configurable initial coding scheme
Prior to GSR7, Coding Scheme 2 (CS2) was used to start for all downlink and uplink TBFs. Now, the operator
is able to control the initial downlink coding scheme (via database parameters) to improve throughput of cells
in which it is well known that all mobiles are capable of higher coding schemes, such as microcells. CS2 is
still used to start when the carrier or PDTCHs assigned for the TBFs are not capable of the initial coding
scheme CS3 or CS4 if they are set in the database.
The above feature also applies to EGPRS, e.g. MCS-2 can be selected as the initial coding scheme.
GPRS/EGPRS data rates
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-30 through Table 3-55 provide illustrations of the data rates by application at each layer in the
GPRS stack.
In practice, the final throughput at application layer will be less than those quoted in the tables due
to various protocol overheads and the behaviour of various layers in response to packet data flow.
68P02900W21-R 3-203
28 Feb 2006 GMR-01
The following assumptions have been made to arrive at the numbers:

• Mean IP packet size of approximately 5000 bytes.
• LLC in unacknowledged mode. This implies that it is assumed there is no signaling overhead
to acknowledge LLC frames. In practice, the LLC acknowledged mode imposes relatively
significant overhead at RLC/MAC level sue to additional signaling required over the user
data channel.
• V42.bis data compression is disabled (if V42.bis is enabled, the data rate is highly variable
depending on data contents).
• The behaviour of TCP, for example, slow start, has not been taken into consideration, that
is, perfect TCP response is assumed. In practice, this imposes additional overhead since the
channel is not fully utilised for certain portion of time.
• Increased efficiencies gained from lowered overhead as a result of using higher numbers of
timeslots has not been calculated for this analysis.
• C/I for each coding scheme is sufficient to support error free transport, that is, BLER = 0.
H/C = Header compression.
TS = Timeslot.
The rates are calculated bottom to top as follows (see Figure 3-85 and Figure 3-86):
1. Physical layer: GSM data rates.
2. RLC/MAC: Error free data rate including RLC/MAC headers (see earlier description of
various coding schemes, user and header encoding procedures.
3. LLC: Error free user data rate excluding RLC/MAC header, i.e. LLC broken into RLC
blocks (Figure 3-86).
4. SNDCP: Includes header associated with LLC (7 bytes + 4bytes CRC, Figure 3-85).
5. IP user rate: Includes header associated with SNDCP (2 bytes, Figure 3-85).
6. TCP: includes header associated with IP (20 bytes, Figure 3-85). The header compression
is not applied to the first LLC IP frame.
7. App. user rate: Includes header associated with TCP (20 bytes, Figure 3-85).
8. For more than 1 timeslot, the overheads are applied only to one of the timeslots.
3-204 68P02900W21-R
GMR-01 28 Feb 2006
Figure 3-86 LLC PDU to TDMA bursts
LLC frame
LLC
layer
RLC block
Segment Segment Segment
RLC/MAC
layer
Header RLC data Tail
Radio link
layer
Convolutional encoding (dictates code rate), Puncturing and Interleaving
Transmission across the radio link
68P02900W21-R 3-205
28 Feb 2006 GMR-01
Table 3-30 GPRS downlink data rates (kbit/s) with TCP (CS1)
Protocol CS1, TS = 1 CS1, TS = 2 CS1, TS = 3 CS1, TS = 4

Stack
No H/C H/C No H/C H/C No H/C H/C No H/C H/C
App. 7.73 7.91 15.73 15.93 23.73 23.93 31.73 31.93
user rate
TCP 7.83 7.92 15.83 15.93 23.83 23.93 31.83 31.93
IP user 7.93 15.93 23.93 31.93
rate
SNDCP 7.94 15.94 23.94 31.94
LLC 8.00 16 24 32
RLC/MAC 9.20 18.4 27.6 36.8
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 11.60 11.86 23.60 23.89 35.60 35.89 47.60 47.89
user rate
TCP 11.75 11.89 23.75 23.90 35.75 35.90 47.75 47.90
IP user 11.90 23.90 35.90 47.90
rate
SNDCP 11.92 23.92 35.92 47.92
LLC 12 24 36 48
RLC/MAC 13.6 27.1 40.65 54.2
Physical 33.86 67.72 101.58 135.44
layer
3-206 68P02900W21-R
GMR-01 28 Feb 2006

Stack
App. 13.92 14.24 28.32 28.67 42.72 43.07 57.12 57.47
user rate
UDP 14.10 14.26 28.50 28.68 42.90 43.08 57.30 57.48
IP user 14.28 28.68 43.08 57.48
rate
SNDCP 14.30 28.70 43.10 57.50
LLC 14.4 28.8 43.2 57.6
RLC/MAC 15.8 31.5 47.3 63.0
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 19.34 19.77 39.33 39.82 59.33 59.82 79.33 79.82
user rate
TCP 19.58 19.81 39.58 39.83 59.58 59.83 79.58 79.83
IP user 19.84 39.84 59.84 79.84
rate
SNDCP 19.86 39.86 59.86 79.86
LLC 20 40 60 80
RLC/MAC 21.8 43.1 64.7 86.2
Physical 33.86 67.72 101.58 135.44
layer
68P02900W21-R 3-207
28 Feb 2006 GMR-01
Table 3-34 GPRS downlink data rates (kbit/s) with UDP (CS1)

Stack
App. 7.79 7.92 15.79 15.93 23.79 23.93 31.79 31.93
user rate
UDP 7.83 7.92 15.83 15.93 23.83 23.93 31.83 31.93
IP user 7.93 15.93 23.93 31.93
rate
SNDCP 7.94 15.94 23.94 31.94
LLC 8.00 16 24 32
RLC/MAC 9.20 18.4 27.6 36.8
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 11.69 11.88 23.69 23.89 35.69 35.89 47.69 47.89
user rate
UDP 11.75 11.89 23.75 23.90 35.75 35.90 47.75 47.90
IP user 11.90 23.90 35.90 47.90
rate
SNDCP 11.92 23.92 35.92 47.92
LLC 12 24 36 48
RLC/MAC 13.6 27.1 40.65 54.2
Physical 33.86 67.72 101.58 135.44
layer
3-208 68P02900W21-R
GMR-01 28 Feb 2006

Stack
App. 14.03 14.25 28.43 28.67 42.83 43.07 57.23 57.47
user rate
TCP 14.10 14.26 28.50 28.68 42.90 43.08 57.30 57.48
IP user 14.28 28.68 43.08 57.48
rate
SNDCP 14.30 28.70 43.10 57.50
LLC 14.4 28.8 43.2 57.6
RLC/MAC 15.8 31.5 47.3 63.0
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 19.49 19.80 39.48 39.82 59.48 59.82 79.48 79.82
user rate
UDP 19.58 19.81 39.58 39.83 59.58 59.83 79.58 79.83
IP user 19.84 39.84 59.84 79.84
rate
SNDCP 19.86 39.86 59.86 79.86
LLC 20 40 60 80
RLC/MAC 21.6 43.1 64.7 86.2
Physical 33.86 67.72 101.58 135.44
layer
68P02900W21-R 3-209
28 Feb 2006 GMR-01
Table 3-38 EGPRS downlink data rates (kbit/s) with TCP (MCS1)
Protocol MCS1, TS = 1 MCS1, TS = 2 MCS1, TS = 3 MCS1, TS = 4

Stack
App. 8.51 8.70 17.31 17.52 26.11 26.32 34.91 35.12
user rate
TCP 8.62 8.72 17.42 17.52 26.22 26.32 35.02 35.12
IP user 8.73 17.53 26.33 35.13
rate
SNDCP 8.74 17.54 26.34 35.14
LLC 8.80 17.60 26.40 35.20
RLC/MAC 10.55 21.10 31.65 42.20
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 10.83 11.07 22.03 22.30 33.23 33.50 44.43 44.70
user rate
TCP 10.97 11.09 22.17 22.30 33.37 33.50 44.57 44.70
IP user 11.11 22.31 33.51 44.71
rate
SNDCP 11.12 22.32 33.52 44.72
LLC 11.20 22.40 33.60 44.80
RLC/MAC 12.95 25.90 38.85 51.80
Physical 33.86 67.72 101.58 135.44
layer
3-210 68P02900W21-R
GMR-01 28 Feb 2006

Stack
App. 14.31 14.63 29.11 29.46 43.91 44.26 58.70 59.06
user rate
TCP 14.49 14.66 29.29 29.47 44.09 44.27 58.89 59.07
IP user 14.68 29.48 44.28 59.08
rate
SNDCP 14.70 29.50 44.30 59.10
LLC 14.80 29.60 44.40 59.20
RLC/MAC 16.55 33.10 49.65 66.20
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 17.02 17.40 34.61 35.04 52.21 52.64 69.81 70.24
user rate
TCP 17.23 17.43 34.83 35.05 52.43 52.65 70.03 70.25
IP user 17.46 35.06 52.66 70.26
rate
SNDCP 17.48 35.08 52.68 70.28
LLC 17.60 35.20 52.80 70.40
RLC/MAC 19.35 38.70 58.05 77.40
Physical 33.86 67.72 101.58 135.44
layer
68P02900W21-R 3-211
28 Feb 2006 GMR-01

Stack
App. 21.66 22.15 44.05 44.59 66.45 66.99 88.85 89.39
user rate
TCP 21.93 22.19 44.33 44.61 66.73 67.01 88.13 89.41
IP user 22.22 44.62 67.02 89.42
rate
SNDCP 22.24 44.64 67.04 89.44
LLC 22.40 44.80 67.20 89.60
RLC/MAC 23.90 23.90 23.90 23.90
Physical 101.58 203.16 304.74 406.32
layer

Stack
App. 28.62 29.26 58.21 58.93 87.81 88.53 117.41 118.13
user rate
TCP 28.99 29.32 58.58 58.94 88.18 88.54 117.78 118.14
IP user 29.36 58.96 88.56 118.16
rate
SNDCP 29.39 58.99 88.59 118.19
LLC 29.60 59.20 88.80 118.40
RLC/MAC 31.10 62.20 93.30 124.40
Physical 101.58 203.16 304.74 406.32
layer
3-212 68P02900W21-R
GMR-01 28 Feb 2006

Stack
App. 43.31 44.29 88.11 89.19 132.90 133.99 177.70 178.79
user rate
TCP 43.87 44.38 88.67 89.21 133.47 134.01 178.27 178.81
IP user 44.43 89.23 134.03 178.83
rate
SNDCP 44.49 89.29 134.09 178.89
LLC 44.80 89.60 134.40 179.20
RLC/MAC 46.90 93.80 140.70 187.60
Physical 101.58 203.16 304.74 406.32
layer

Stack
App. 52.60 53.78 106.99 108.30 161.38 162.70 215.78 217.10
user rate
TCP 53.27 53.88 107.67 108.33 162.07 162.73 216.47 217.13
IP user 53.95 108.35 162.75 217.15
rate
SNDCP 54.02 108.42 162.82 217.22
LLC 54.40 108.80 163.20 217.60
RLC/MAC 56.50 113.00 169.50 226.00
Physical 101.58 203.16 304.74 406.32
layer
68P02900W21-R 3-213
28 Feb 2006 GMR-01
Pro- MCS9, TS = 1 MCS9, TS = 2 MCS9, TS = 3 MCS9, TS = 4

tocol
Stack
App. 57.24 58.53 116.43 117.85 175.62 177.05 234.82 236.25
user rate
TCP 57.97 58.64 117.17 117.89 176.37 177.09 235.57 236.29
IP user 58.71 117.91 177.11 236.31
rate
SNDCP 58.79 117.99 177.19 236.39
LLC 59.20 118.40 177.60 236.80
RLC/MAC 61.30 122.60 183.90 245.20
Physical 101.58 203.16 307.74 406.32
layer
3-214 68P02900W21-R
GMR-01 28 Feb 2006
Table 3-47 EGPRS downlink data rates (kbit/s) with UDP (MCS1)

Stack
App. 8.57 8.71 17.37 17.52 26.17 26.32 34.97 35.12
user rate
UDP 8.62 8.72 17.42 17.52 26.22 26.32 35.02 35.12
IP user 8.73 17.53 26.33 35.13
rate
SNDCP 8.74 17.54 26.34 35.14
LLC 8.80 17.60 26.40 35.20
RLC/MAC 10.55 21.10 31.65 42.20
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 10.91 11.09 22.11 22.30 33.31 33.50 44.51 44.70
user rate
UDP 10.97 11.09 22.17 22.30 33.37 33.50 44.57 44.70
IP user 11.11 22.31 33.51 44.71
rate
SNDCP 11.12 22.32 33.52 44.72
LLC 11.20 22.40 33.60 44.80
RLC/MAC 12.95 25.90 38.85 51.80
Physical 33.86 67.72 101.58 135.44
layer
68P02900W21-R 3-215
28 Feb 2006 GMR-01

Stack
App. 14.42 14.65 29.22 29.47 44.02 44.27 58.82 59.07
user rate
UDP 14.49 14.66 29.29 29.47 44.09 44.27 58.89 59.07
IP user 14.68 29.48 44.28 59.08
rate
SNDCP 14.70 29.50 44.30 59.10
LLC 14.80 29.60 44.40 59.20
RLC/MAC 16.55 33.10 49.65 66.20
Physical 33.86 67.72 101.58 135.44
layer

Stack
App. 17.15 17.42 34.75 35.04 52.34 52.64 69.94 70.24
user rate
UDP 17.23 17.43 34.83 35.05 52.43 52.65 70.03 70.25
IP user 17.46 35.06 52.66 70.26
rate
SNDCP 17.48 35.08 52.68 70.28
LLC 17.60 35.20 52.80 70.40
RLC/MAC 19.35 38.70 58.05 77.40
Physical 33.86 67.72 101.58 135.44
layer
3-216 68P02900W21-R
GMR-01 28 Feb 2006

Stack
App. 21.82 22.17 44.22 44.60 66.62 67.00 89.02 89.40
user rate
UDP 21.93 22.19 44.33 44.61 66.73 67.01 88.13 89.41
IP user 22.22 44.62 67.02 89.42
rate
SNDCP 22.24 44.64 67.04 89.44
LLC 22.40 44.80 67.20 89.60
RLC/MAC 23.90 23.90 23.90 23.90
Physical 101.58 203.16 304.74 406.32
layer

Stack
App. 28.84 29.30 58.44 58.94 88.03 88.54 117.63 118.14
user rate
UDP 28.99 29.32 58.58 58.94 88.18 88.54 117.78 118.14
IP user 29.36 58.96 88.56 118.16
rate
SNDCP 29.39 58.99 88.59 118.19
LLC 29.60 59.20 88.80 118.40
RLC/MAC 31.10 62.20 93.30 124.40
Physical 101.58 203.16 304.74 406.32
layer
68P02900W21-R 3-217
28 Feb 2006 GMR-01

Stack
App. 43.65 44.35 88.44 89.20 133.24 134.00 178.04 178.80
user rate
UDP 43.87 44.38 88.67 89.21 133.47 134.01 178.27 178.81
IP user 44.43 89.23 134.03 178.83
rate
SNDCP 44.49 89.29 134.09 178.89
LLC 44.80 89.60 134.40 179.20
RLC/MAC 46.90 93.80 140.70 187.60
Physical 101.58 203.16 304.74 406.32
layer

Stack
App. 53.00 53.85 107.39 108.32 161.79 162.72 216.19 217.12
user rate
UDP 53.27 53.88 107.67 108.33 162.07 162.73 216.47 217.13
IP user 53.95 108.35 162.75 217.15
rate
SNDCP 54.02 108.42 162.82 217.22
LLC 54.40 108.80 163.20 217.60
RLC/MAC 56.50 113.00 169.50 226.00
Physical 101.58 203.16 304.74 406.32
layer
3-218 68P02900W21-R
GMR-01 28 Feb 2006
Pro- MCS9, TS = 1 MCS9, TS = 2 MCS9, TS = 3 MCS9, TS = 4

tocol
Stack
App. 57.68 58.60 116.87 117.88 176.07 177.08 235.27 236.28
user rate
UDP 57.97 58.64 117.17 117.89 176.37 177.09 235.57 236.29
IP user 58.71 117.91 177.11 236.31
rate
SNDCP 58.79 117.99 177.19 236.39
LLC 59.20 118.40 177.60 236.80
RLC/MAC 61.30 122.60 183.90 245.20
Physical 101.58 203.16 304.74 406.32
layer
68P02900W21-R 3-219
28 Feb 2006 GMR-01
3-220 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
4
AMR and {22064} GSM planning
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This chapter provides an overview of the Adaptive Multi-Rate (AMR) and {22064} GSM half rate feature and
how they operate within the Motorola system. There are many similarities in {22064} GSM half rate and the
half rate portion of AMR. As a result, the information here covers both features.
The benefits of the features are outlined, and performance discussed. The reader will gain an understanding
of how AMR and {22064} GSM half rate work and how they may be configured. The various parameters
controlling AMR operation are discussed. However, not all of the commands and parameters are shown in
detail. Refer to the applicable command reference manual for additional detail.
The topics described are as follows:
• "Introduction to AMR and {22064} GSM planning" on page 4-2
• "Quality and capacity" on page 4-6
• "Rate adaptation" on page 4-17
• "Handover and power control" on page 4-21
• "Miscellaneous information" on page 4-24
• "Half rate utilization" on page 4-26
• "Hardware" on page 4-33
68P02900W21-R 4-1
28 Feb 2006 GMR-01
Introduction to AMR and {22064} GSM planning Chapter 4: AMR and {22064} GSM planning
Introduction to AMR and {22064} GSM planning

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
AMR basic operation
Existing GSM speech codecs operate at a fixed coding rate. Channel protection is also fixed. AMR adapts
the speech and channel coding rates according to the quality of the radio channel. This gives better channel
quality and better robustness to errors.
Capacity can also be enhanced by allocating half rate channels to some or all mobiles. The system will
allocate a half rate (hr) or full rate (fr) channel according to channel quality and the traffic load on the cell in
order to obtain the best balance between quality and capacity.
The control system is not fixed but can be tuned to meet particular needs and as experience is gained. The
three primary levels of adaptation of the control system are:
• Handovers between hr and fr channels according to traffic demands.
• Variable partitioning between speech and channel coding bit rates to adapt to channel
conditions in order to obtain best speech quality.
• Optimization of channel and codec control algorithms to meet specific operator needs and
network conditions.
This allows the codec to be applied in many ways, of which three important examples are:
• fr only for maximum robustness to channel errors but no capacity advantage.
• hr only for maximum capacity advantage.
• Mixed hr/fr operation allowing a trade-off between quality and capacity.
4-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Introduction to AMR and {22064} GSM planning
{22064} GSM half rate basic operation
GSM half rate was introduced in phase 2 of the standards and operates at a fixed coding rate. Due to this early
introduction into the standards the penetration rate of half rate capable mobiles is high. However the speech
quality is poor when compared to the half rate mode of AMR (as well as all forms of full rate speech).
GSM half rate is used as a means to increase capacity within a cell. As with AMR half rate, capacity is
increased by either always preferring half rate (hr), or by allocating a half rate or full rate (fr) channel
according to channel quality and the traffic load on the cell. Handovers between hr and fr channels vary
according to traffic demands.
The best examples of applying the codec are:
• hr only for maximum capacity advantage.
• Mixed hr/fr operation allowing a trade–off between quality and capacity.
{22064} AMR and GSM half rate interaction
AMR and GSM half rate may co-exist in a cell. A carrier could have a mix of GSM half rate and AMR
(full rate and/or half rate) simultaneously. The parameters that govern half rate operation have been made
generic to facilitate that style of operation.
New hardware
New hardware has been developed to support the AMR and the {22064} GSM half rate features. This
equipment, in conjunction with the supporting software and firmware, provides the capabilities necessary to
fully exploit the advantages of AMR and/or {22064} GSM half rate.
This equipment consists of the following:
• Double Kiloport Switch (DSW2).
• Double Kiloport Switch Extender (DSWX).
• Generic DSP Processing board 2 (GDP2)
• Remote Transcoder Unit 3 (shelf) (RXU3).
• Base Station System Cabinet 3 (BSSC3).
AMR and {22064} GSM half rate may be used without the benefit of any of the new hardware, although not
as efficiently (this is discussed later in this chapter).
Without new hardware, AMR requires the use of GDPs configured as EGDP(s).
68P02900W21-R 4-3
28 Feb 2006 GMR-01
Introduction to AMR and {22064} GSM planning Chapter 4: AMR and {22064} GSM planning
Influencing factors
There are many factors to be taken into account when configuring/operating a system in which AMR and/or
{22064} GSM half rate is present. These include:
• AMR-capable handset penetration (see the first note below).
• {22064} GSM half rate–capable handset penetration (see the second note below).
• Transceiver capability.
• Carrier configuration.
• Use of reserved channels / cell congestion.
It is assumed that an AMR-capable handset or mobile includes both fr and hr capability.
{22064} It is expected that most handsets or mobiles are GSM half rate capable.
4-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Introduction to AMR and {22064} GSM planning
Planning
The system operator must decide how the system should operate with regard to full and half rate, and what
combination of new and old equipment is to be utilized. Other decisions, such as codec rates and backhaul,
must also be made. The information provided in this chapter will aid the reader in understanding what options
are available, what are the advantages of each, what equipment is required and why, and how the system
will operate under the choices made.
One of the main decisions to be made is how to utilize the half rate capability of AMR and/or {22064} GSM
half rate. "Quality and capacity" on page 4-6 describes the benefits of the AMR codecs and how AMR Full
Rate and AMR Half Rate compare to the existing GSM codecs. {22064} The GSM Half Rate codec is
compared to the other GSM codecs. Also discussed are the benefits in coverage of AMR Full Rate. The
capacity increases made possible through the use of half rate are discussed, with examples showing the
potential gains under a variety of configurations and (half rate) capable handset penetration.
The information in "Quality and capacity" on page 4-6 can be used to help determine how AMR full rate and
AMR/{22064} GSM half rate should be utilized. As stated earlier, there are three primary methods of AMR
usage, two of which apply to {22064} GSM half rate:
1. AMR full rate only (AMR only). This has the advantage of providing better voice quality
under a broad range of channel conditions. This method is robust but provides no capacity
advantage per carrier. It may be particularly suited to areas where adverse propagation
conditions prevail, for example.
2. Forced half rate. This is used when capacity is paramount. Voice quality is sacrificed in order
to carry more calls per carrier. It may be a candidate for use in severely congested areas, or
where voice quality is not a concern.
3. A mix of full rate and half rate. Full rate is generally used until the cell becomes congested, at
which time half rate is employed. This configuration will provide quality voice coverage until
congestion is reached. This capacity on demand configuration is well suited for environments
with varying traffic patterns, such as cities. The information contained in "Half rate utilization"
on page 4-26 can be used to help configure the system to maximum effectiveness when
half rate is used in such a manner.
"Rate adaptation" on page 4-17 provides information on the rate adaptation characteristics of AMR.
"Miscellaneous information" on page 4-24 provides information on emergency call handling and circuit
pooling.
"Hardware" on page 4-33 contains a description of the new hardware and what advantages it delivers.
68P02900W21-R 4-5
28 Feb 2006 GMR-01
Quality and capacity Chapter 4: AMR and {22064} GSM planning
Quality and capacity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Benefits of AMR
The ability of the AMR codec to dynamically change the allocation of source and channel coding bits
provides a high level of speech quality. The overall improvements are dependant upon channel quality
(C/I). As channel quality deteriorates, a codec with a higher level of error protection (and a corresponding
decrease in speech quality) is selected, leading to an increase in sensitivity of the transceivers, thus providing
optimum performance.
The half rate mode of AMR can be utilized to obtain a capacity gain on the air interface. This can be tied to
congestion at the cell level to provide capacity gains on an as needed basis.
With AMR operating in full rate mode, or in a mix of full rate and half rate where handovers between the
modes is permitted, a capacity gain can be realized as a result of being able to operate at a lower C/I threshold.
This can result in potentially higher traffic loading. Note however that the benefits of AMR do not extend to
the signalling channels, or to the use of non-AMR codecs and data services. Capacity gains of this type are
very dependent on other factors (e.g. propagation conditions) and are beyond the scope of this chapter.
Under high channel error conditions, an AMR FR codec mode which has a low source coding rate and a high
level of error protection will normally be selected. This will allow good speech quality to be maintained
under conditions 6 dB worse than the corresponding level for EFR. This translates to an improvement in
terminal or BTS sensitivity, but is subject to the limit of robustness of the signalling channels (presumed to be
at least 2 dB, and possibly as high as 4 dB or 6 dB). This may be exploited for range extension, or improved
coverage in buildings. Range extension is discussed further in AMR voice quality improvement and
coverage later in this chapter.
AMR Full Rate and AMR Half Rate speech quality
Introduction
Here, the relative performance of the AMR Full Rate and Half Rate speech codecs is shown for comparative
purposes. Some conclusions can be drawn from the comparisons and are discussed.
Mean Opinion Scores (MOS) are subjective and can be affected by test conditions. However, the relative
performance of the codecs to each other is considered reliable. The conditions used in the tests are no
background impairments, static channel conditions, and ideal frequency hopping.
The graphs in Figure 4-1 to Figure 4-4 and the accompanying information are extracted from
GSM 06.75 (v. 7.2.0), Performance Characterization of the GSM Adaptive Multi-Rate (AMR)
speech codec.
4-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Quality and capacity
AMR Full Rate

In Figure 4-1, AMR FR speech quality (best AMR codec) is compared with EFR and performance
requirements under a range of channel conditions.
Figure 4-1 AMR FR/clean speech vs EFR vs performance requirements
MOS
5.0
4.0
3.0
2.0 Sel. Requirements

AMR-FR
EFR
Conditions
1.0
No Errors C/I=16 dB C/I=13 dB C/I=10 dB C/I= 7 dB C/I= 4 dB C/I= 1 dB
Sel. Requirements 4.01 4.01 4.01 3.65
AMR-FR 4.06 4.06 4.13 4.08 3.96 3.59 2.66
EFR 4.01 4.01 3.65 3.05 1.53
68P02900W21-R 4-7
28 Feb 2006 GMR-01
Figure 4-2 shows the individual codec modes for AMR FR/clean speech, as illustrated in Figure 4-1.
Figure 4-2 AMR FR/clean speech codec modes
MOS
5.0
4.0
3.0 EFR
7.95
7.4
6.7
5.9
2.0 5.15
4.75
FR
HR
Conditions
1.0
No Errors C/I=19 dB C/I=16 dB C/I=13 dB C/I=10 dB C/I= 7 dB C/I= 4 dB
EFR 4.21 4.21 3.74 3.34 1.58
7.95 4.11 4.04 3.96 3.37 2.53 1.60
7.4 3.93 3.93 3.95 3.52 2.74 1.78
6.7 3.94 3.90 3.53 3.10 2.22 1.21

5.9 3.68 3.82 3.72 3.19 2.57 1.33
5.15 3.70 3.60 3.60 3.38 2.85 1.84
4.75 3.59 3.46 3.42 3.30 3.10 2.00
FR 3.50 3.50 3.14 2.74 1.50
HR 3.35 3.24 2.80 1.92
4-8 68P02900W21-R
GMR-01 28 Feb 2006
AMR half rate

Figure 4-3 and Figure 4-4 show performance curves for AMR HR speech quality compared to EFR as
well as GSM FR and HR under the same range of channel conditions as the AMR FR comparison shown
in Figure 4-1 and Figure 4-2.
Figure 4-3 AMR HR/clean speech vs EFR vs GSM FR vs GSM HR vs perf. reqs
MOS
5.0
4.0
3.0
Sel. Requirements
AMR-HR
2.0
EFR
FR
HR
Conditions
1.0
Sel. Requirements 3.99 3.99 3.99 3.14 2.74 1.50

AMR-HR 4.11 4.04 3.96 3.72 3.38 3.10 2.00
EFR 4.21 4.21 3.74 3.34 1.58
FR 3.50 3.50 3.14 2.74 1.50
HR 3.35 3.24 2.80 1.92
68P02900W21-R 4-9
28 Feb 2006 GMR-01
Figure 4-4 AMR HR/clean speech codec modes
MOS
5.0
4.0
3.0 EFR
7.95
7.4
6.7
5.9
2.0 5.15
4.75
FR
HR
Conditions
1.0
EFR 4.21 4.21 3.74 3.34 1.58
7.95 4.11 4.04 3.96 3.37 2.53 1.60
7.4 3.93 3.93 3.95 3.52 2.74 1.78
6.7 3.94 3.90 3.53 3.10 2.22 1.21

5.9 3.68 3.82 3.72 3.19 2.57 1.33
5.15 3.70 3.60 3.60 3.38 2.85 1.84
4.75 3.59 3.46 3.42 3.30 3.10 2.00
FR 3.50 3.50 3.14 2.74 1.50
HR 3.35 3.24 2.80 1.92
Conclusions
The MOS scores for AMR FR are higher than EFR, considerably better at lower C/I levels. AMR HR speech
quality is better than GSM FR and HR, but not as good as EFR. If one considers a MOS score of 3.0 to be
the minimally accepted “communications quality" level, then at lower C/I levels (7 dB and 4 dB) the AMR
HR speech coder quality is poor. AMR hr, of course, provides the capacity benefit of allowing two calls
to exist in the space of one timeslot.
This behaviour suggests that one viable deployment strategy is to use fr mode until capacity limitations
force calls to utilize hr mode, at which time some fr calls can also be moved to hr. A hr call may also be
moved to a fr channel via an interference based handover, depending on the congestion state of the cell
and system parameter settings.
The Motorola system supports this configuration, as well as many others, including forcing all calls to use
hr all the time, equipment permitting.
Selection of a particular mode of operation is up to the operator. MOS scores are subjective and may vary
depending upon customer expectations.
4-10 68P02900W21-R
GMR-01 28 Feb 2006
AMR voice quality improvement and coverage
Analysis has shown that AMR FR under C/I = 13 dB can provide the same quality of service (MOS = 4) as
GSM FR/EFR under C/I = 15 dB. In general, AMR FR will provide better overall voice quality than GSM
FR/EFR under comparable radio conditions. This can translate to an increase in coverage area.
A study has been done to quantify the potential coverage gains. The following assumptions were used in
the study:
• System is interference-limited (the impact of thermal noise is negligible compared with
the level of interference).
• System is 100% loaded: all the available physical resources are used (this is the worst case
assumption - coverage gains increase with less loading).
• Path loss exponent assumed to be 3.76, and the shadowing lognormal standard deviation is
10 dB.
• Power control and any type of DTX not used.
• All terminals are AMR.
The results of the study are shown in Table 4-1.

The coverage reliability is expected to increase by 5 to 8 percentage points depending on the frequency reuse
patterns. The link budget improvement can potentially lead to an increase in cell areas around 27%.
This type of increase in coverage applies to existing networks where site spacing can be modified or new
networks where it has yet to be selected, and where the majority of terminals are AMR. Non-AMR terminal
performance could be degraded under these conditions.
Table 4-1 AMR potential coverage gains
Gain in
Frequency
Coverage at Coverage at coverage Gain in
re-use pattern
15 dB 13 dB (increase in cell coverage area
(see Note)
radius)
1-3-3 44% 36% 8% 16.6%
3-1-3 57% 49% 8% 16.6%
3-3-9 81% 74% 7% 14.5%
4-1-4 70% 62% 8% 16.6%
4-3-12 92% 87% 5% 10.3%
7-1-7 88% 82% 6% 12.4%
7-3-21 98% 96% 2% 4%
68P02900W21-R 4-11
28 Feb 2006 GMR-01
First digit = # cell sites, second digit = # sectors/cell and third digit = # carriers/cell.
{22064} Benefits of GSM half rate
GSM Half Rate offers enhanced capacity over the air interface, corresponding to the proportion of mobiles
within a coverage area that supports Half Rate. GSM half rate has a high penetration level (of GSM HR
capable mobiles) due to its early introduction into the standards. Due to these large penetration levels it is
considered a viable option for high density areas.
The GSM Half Rate codec uses the VSELP (Vector-Sum Excited Linear Prediction) algorithm. The VSELP
algorithm is an analysis-by-synthesis coding technique and belongs to the class of speech coding algorithms
known as CELP (Code Excited Linear Prediction).
The benefits of GSM half rate are an increase in capacity at a cell without requiring additional transceiver
boards or carriers. The use of half rate can be tied to congestion at the cell level to provide capacity gains
on an as needed basis.
{22064} GSM Half Rate speech quality
Figure 4-3 shows how GSM Half Rate compares with the EFR, FR, and AMR HR codecs.
Mean Opinion Scores (MOS) are subjective and may vary depending upon customer expectations. They
can also be affected by test conditions. However, the relative performance of the codecs to each other
is considered reliable. The conditions used in the tests are no background impairments, static channel
conditions, and ideal frequency hopping.
In conclusion, the GSM Half Rate codec voice quality performance is inferior to the other codecs. This
suggests a deployment strategy of using fr mode until capacity limitations force calls to utilize hr mode, at
which time some fr calls can also be moved to hr. A hr call may also be moved to a fr channel via an
interference based handover, depending on the congestion state of the cell and system parameter settings, as
well as a quality based handover when no viable candidate neighbour cells exist.
The Motorola system supports this configuration, as well as many others, including forcing all calls to use
hr all the time, equipment permitting.
Selection of a particular mode of operation is the decision of the operator.
4-12 68P02900W21-R
GMR-01 28 Feb 2006
Capacity increase due to half rate usage
On the air interface up to twice as many calls can be handled in a cell when half rate is used (as previously
mentioned, this is a trade-off with quality). The actual increase in call carrying capacity is typically less than
100% due in part to the penetration level of half rate capable handsets. As the penetration level rises, the
half rate carriers become more efficient.
In Figure 4-5 to Figure 4-9, the carried erlangs (at 2% blocking) are shown for a variety of carrier
configurations. For each configuration the capacity increase is shown as a function of the handset penetration
level.
The results shown were obtained via simulation and under the following assumptions:
• A hr-capable handset is given a hr timeslot if available; otherwise a fr timeslot on a fr carrier.
• Preference is to assign a fr-capable only handset to a fr carrier if available; otherwise it is

assigned to a hr-capable carrier.
• Preference is at call establishment to assign a hr-capable handset an idle sub-channel on a

timeslot that has the other sub-channel occupied with a call.
Graphs
The graphs are intended to illustrate the call carrying effectiveness as a function of hr carriers and hr-capable
MS penetration and do not take into account any control channels. As a result, the actual carried erlangs may
be slightly less than those in the graphs.
Figure 4-5 3 carriers, only one hr-capable carrier
Carried Erlangs
(at ~2% blocking)
25.000
20.000
15.000
10.000
5.000
0.000
0.00 0.10 0.20 0.30 0.40 0.50 0.60 0.70 0.80 0.90 1.00
AMR Capable MS Penetration
68P02900W21-R 4-13
28 Feb 2006 GMR-01
Figure 4-6 3 carriers, all hr-capable
Carried Erlangs
(at ~2% blocking)
40.000
35.000
30.000
25.000
20.000
15.000
10.000
5.000
0.000
0.00 0.20 0.40 0.60 0.80 1.00
Figure 4-7 5 carriers, only one hr-capable carrier
Carried Erlangs
(at ~2% blocking)
40.000
35.000
30.000
25.000
20.000
15.000
10.000
5.000
0.000
0.00 0.20 0.40 0.60 0.80 1.00
4-14 68P02900W21-R
GMR-01 28 Feb 2006
Figure 4-8 5 carriers, only 3 hr-capable carriers
Carried Erlangs
(at ~2% blocking)
60.000
50.000
40.000
30.000
20.000
10.000
0.000
0.00 0.10 0.20 0.30 0.40 0.50 0.60 0.70 0.80 0.90 1.00
Figure 4-9 5 carriers, all hr-capable carriers
Carried Erlangs
(at ~2% blocking)
80.000
70.000
60.000
50.000
40.000
30.000
20.000
10.000
0.000
0.00 0.10 0.20 0.30 0.40 0.50 0.60 0.70 0.80 0.90 1.00
68P02900W21-R 4-15
28 Feb 2006 GMR-01
Conclusions
Figure 4-5 to Figure 4-9 are useful in illustrating that, for some deployment strategies such as a maximum
capacity configuration, more carrier equipment should be configured as hr-capable when hr-capable handset
penetration rises. For example, in a 5 carrier cell with a 50% handset penetration rate, there is not much
difference in erlang capacity between a 3 hr-capable carrier configuration and a 5 (all) hr-capable carrier
configuration. As the handset penetration rises however, the 5 hr-capable carrier configuration is better able to
utilize the extra capacity that hr offers.
{22064} As noted earlier, GSM hr-capable handset penetration is expected to be very high.
When migrating a system to one that includes half rate, take care to ensure that the call capacity rating of the
various components of the system are not exceeded. Use of hr improves the spectral efficiency over the air
interface (and potentially the backhaul), but from a load perspective, a half rate call has the same impact as
a full rate call.
Other strategies, such as utilizing hr only during periods of high demand, would require fewer hr-capable
carriers. Figure 4-5 to Figure 4-9 demonstrate how even adding one hr-capable carrier can increase erlang
capacity.
Timeslot usage
This section briefly describes timeslot configuration and the algorithm used to optimise usage.
A GSM carrier consists of 8 timeslots, some or all of which may be used for voice traffic. In full rate, each
voice call occupies one timeslot. In half rate, the timeslot is split into two sub-channels, each of which is
capable of supporting one hr call. A fr call cannot be carried within two sub-channels split across two
timeslots. At any instance, depending on configuration, a carrier may contain a combination of fr and hr calls.
To optimise capacity, it is desirable to not have fragmented hr usage. That is, it is best to use both
sub-channels of a single timeslot rather than one sub-channel on two timeslots. This frees up contiguous
sub-channels for use in a fr call.
The Motorola algorithm will attempt first to assign new calls to timeslots that have one sub-channel in use
before using a timeslot with both sub-channels idle. This provides a large degree of concentration. As calls
begin and end, some degree of fragmenting is unavoidable and the algorithm will attempt to fill in the holes as
new calls arrive. This applies to all arriving calls (e.g. originations, handovers, etc.).
It was also considered whether to further pack hr calls together via intra-cell handover whenever fragmenting
reaches a level where a fr call might be blocked. Simulations have been carried out under a variety of
configurations and conditions, and it was determined that the slight capacity gain was outweighed by the
negative aspects of performing the otherwise unnecessary handover. Although the results varied according
to penetration rate and configuration, in general, additional blocking of 1.5% or less resulted for the fr
only handsets (as compared with the hr-capable handsets). Limiting the number of hr capable carriers in a
cell can reduce this disparity.
4-16 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Rate adaptation
Rate adaptation
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to rate adaptation
Rate Adaptation (RA) is particular to AMR and refers to the control and selection of the codec mode based
upon channel quality. Another name for it is Codec Mode Adaptation. The term “Codec Mode" refers to one
of the various choices of bit partitioning between the speech and error protection bits.
Codec modes
A total of 14 codec modes are defined for AMR; 8 for the fr channel mode, and 6 for the hr channel mode. Up
to 4 codec modes may be utilized for any given voice call. This is called the Active Codec Set (ACS). The
uplink and downlink directions may each use a different codec mode; hence there are 2 sets of associated
thresholds and hysteresis, one for uplink and one for downlink.
The ACS may be chosen from the supported codec modes. An analysis has been carried out to determine
what common set of codec modes should be supported across all the CCU platforms (not all platforms could
support all of the codec modes). The conditions were a 900 MHz, ideal frequency hopped system with a
co-channel interferer and a typical urban multipath channel model. The speech is at a nominal input level and
is not degraded by background noise. The result is the selection of 5 fr and 5 hr codec modes, as shown in
Table 4-2. The shaded areas indicate the codec modes that are not supported.
Table 4-2 Supported AMR codecs
Speech codec Speech codec

Is codec mode
bit rate bit rate Supported?
supported?
(fr) (hr)
12.2 kbit/s Yes N/A N/A
10.2 kbit/s Yes N/A N/A
7.95 kbit/s No 7.95 kbit/s Y

7.4 kbit/s Yes 7.4 kbit/s Y
5.9 kbit/s No 5.9 kbit/s Y
4.75 kbit/s No 4.75 kbit/s N
Through simulation and testing default values were determined for the ACS and initial codec modes. These
are initial values subject to change and may not be appropriate for all conditions.
68P02900W21-R 4-17
28 Feb 2006 GMR-01
Rate adaptation Chapter 4: AMR and {22064} GSM planning
The analysis provided the following defaults for the ACS:

• Full Rate: 12.2 kbit/s, 10.2 kbit/s, 7.4 kbit/s, and 5.15 kbit/s.
• Half Rate: 7.4 kbit/s, 5.9 kbit/s, and 5.15 kbit/s.
If 16 kbit/s backhaul is used for the BTS-BSC interface (i.e. 4 x 64 kbit/s timeslots per hr carrier) then the
7.95 kbit/s codec mode should be added to the hr ACS.
An initial codec mode is also required. The same analysis provided the following default values:
• FR initial codec mode: 10.2 kbit/s.
• HR initial codec mode: 6.7 kbit/s.
The HR initial codec mode remains at 6.7 kbit/s even if the 7.95 codec mode is added to the HR ACS.
Thresholds and hystereses
Associated with the Active Codec Set are the thresholds and hystereses used for the codec mode adaptation in
the BSS and the MR for both uplink and downlink directions.
The codec mode is changed rapidly in response to changing radio conditions as illustrated in Figure 4-10.
Figure 4-10 Rate adaptation: codec modes, thresholds and hystereses
C/I
CODEC_MODE_4
THR_3 + HYST_3 =THR_MX_Up (3)
THR_3 = THR_MX_Dn (4)
CODEC_MODE_3
CODEC_MODE_2
CODEC_MODE_1
Rate adaptation thresholds and hystereses are set on a per cell basis.
4-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Rate adaptation
Downlink adaptation MS monitor
There is a risk that certain mobiles may have an impaired ability to correctly estimate the C/I for a channel in
certain conditions. For these mobiles the codec mode adaptation threshold and hysteresis values may prove to
be inefficient, meaning that the threshold and hysteresis values are out of the range of the C/I measuring
ability of the MS, resulting in the MS being unable to adapt its codec mode efficiently. For this reason, the
BSS monitors mobiles to detect such scenarios.
The BSS uses the Codec Mode Requests and the reported RXQUAL values from the MS to determine if
the threshold and hysteresis values used by the MS are inefficient, and increase or decrease the threshold
and hysteresis values accordingly. The BSS then instructs the MS of the change in threshold and hysteresis
values using the Channel Mode Modify procedure.
A detailed description of the monitor process is beyond the scope of this chapter. However, a list of parameters
with their ranges and default values (subject to change) is provided in Table 4-3 for completeness.
Table 4-3 BSS parameters used to determine MS threshold and hysteresis
Parameter Min. Max. Default Description

amr_ms_ 10SACCH periods 120SACCH 40SACCH periods Used for detecting
monitor_ periods MSs continually
period requesting the
highest or lowest
modes.
If the operator
specifies a value
of zero, then
the MS monitor
functionality is
disabled.
amr_ms_high_cmr 50% 100% 99% Percentages for
monitoring AMR
MSs continually
requesting the
highest codec
mode.
amr_ms_low_cmr 50% 100% 95% Percentages for
monitoring AMR
MSs continually
requesting the
lowest codec mode.
Cont.
68P02900W21-R 4-19
28 Feb 2006 GMR-01
Rate adaptation Chapter 4: AMR and {22064} GSM planning
Table 4-3 BSS parameters used to determine MS threshold and hysteresis (Continued)
Parameter Min. Max. Default Description
amr_ms_high_ 0QBand Units 7QBand Units 4QBand Units Threshold for
rxqual monitoring AMR
MSs continually
requesting the
highest codec
mode.
The threshold
defaults to 2.5%
BER or RXQUAL
4
amr_ms_low_ 0QBand Units 7QBand Units 2QBand Units Threshold for
rxqual monitoring MSs
continually
requesting the
lowest mode.
The threshold
defaults to 0.5%
BER or RXQUAL
2
amr_dl_thresh 1 dB 7 dB 3 dB For applying
_adjust compensation to
the C/I adaptation
thresholds.
Range is 1 — 7 dB
in steps of 1 dB.
4-20 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Handover and power control
Handover and power control

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to handover and power control
This section explains the new AMR and {22064} GSM half rate specific handover and power control
threshold parameters. It does not explain how they are used, as this is as per current operation. The ranges are
not indicated either, as they are similar to the existing values.
Handover and power control thresholds
The upper and lower Rxqual thresholds for handover and power control are affected by the ACS within a
cell. As a result, new thresholds are provided for AMR-specific use. The existing parameters and levels
are still applicable to non-AMR calls.
{22064} The half rate Rxqual values are used for both GSM half rate and AMR half rate operation, as
behavior at Rxqual decision points is similar.
The Rxlev thresholds are applicable to both AMR and non-AMR calls, hence no new Rxlev parameters
are introduced.
Analysis has been carried out to determine a default set of AMR-specific Rxqual threshold values. These
values (see Table 4-4, which are preliminary and subject to change, are applicable to the fr ACS and the hr
ACS as described in "Rate adaptation" on page 4-17. The default database values follow the recommendations
of Rxlev Handovers Disabled and Uplink diversity.
68P02900W21-R 4-21
28 Feb 2006 GMR-01
Handover and power control Chapter 4: AMR and {22064} GSM planning
Table 4-4 Handover and power control - Full and Half Rate default values
Thresholds (UL/DL) - all figures in QBand Units

Thresh- Non Frequency Hopping Frequency Hopping
old Name
(see No UL Diversity UL Diversity No UL Diversity UL Diversity
Note) RXLEV RXLEV RXLEV RXLEV RXLEV RXLEV RXLEV RXLEV
enabled disabled enabled disabled enabled disabled enabled disabled
l_rxqual_ 3/3 3/3 4/3 4/3
XX_p_amr_
fr
l_rxqual_ 4/4 4/4 5/4 5/4
XX_h_amr_
fr
l_rxqual_ 4/4 4/4 5/4 5/4
XX_p_
hopping_
amr_fr
l_rxqual_ 5/5 5/5 6/5 6/5
XX_h_
hopping_
amr_fr
l_rxqual_ 2/2 2/2 2/2 2/2
XX_p_hr
l_rxqual_ 3/3 3/3 3/3 3/3
XX_h_hr
u_rxqual_ 0/0 0/0 0/0 0/0
XX_p_hr
l_rxqual_ 2/2 2/2 2/2 2/2
XX_p_
hopping_hr
l_rxqual_ 3/3 3/3 3/3 3/3
XX_h_
hopping_hr
“XX" refers to “ul" or “dl".

Regarding intra-cell hr to fr handovers:
An intra-cell handover from a hr channel to a fr channel will be attempted if:
4-22 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Handover and power control
An interference based handover is indicated (the received quality is of a BER greater than l_rxqual_xx_h_hr
and the signal level is above u_rxlev_xx_ih and both hr_intracell_ho_allowed and force_hr_usage allow
for it.
or:
A quality based handover is indicated and there are no viable neighbour cells, and both
hr_intracell_ho_allowed and force_hr_usage allow for it.
68P02900W21-R 4-23
28 Feb 2006 GMR-01
Miscellaneous information Chapter 4: AMR and {22064} GSM planning
Miscellaneous information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Emergency call handling
It is a priority to place an emergency call upon a fr channel, if possible. If necessary to do so, a call of a
lower priority will be pre-empted. When selecting a call to pre-empt, the software attempts to minimize the
disruption by choosing first a fr call of lower priority. Failing that, a lower priority single occupancy hr call
(the other sub-channel is idle) is searched for, followed by a timeslot carrying two hr calls (both being of
lower priority).
Circuit pooling
On the terrestrial route connecting the BSS and MSC, certain circuits can be used for different combinations
of bearer capabilities. This can be realized in practice by grouping the circuits into “pools" supporting the
same channel types. The MSC holds this information as route data. If the MSC allocates an A interface
circuit, it should only ever ask for resources from the BSS that it knows are not totally incompatible with
the nominated circuit.
In the case where several circuit pools (groups of circuits supporting the same channel types) are available on
the BSS MSC interface, the terrestrial circuit allocated by the MSC is chosen taking into account the circuit
pool the circuit belongs to and the required channel type.
The GDP will support FR, {22064} GSM HR and EFR speech only, while the EGDP supports fr, EFR, and
AMR. {22064} The GDP2 will support FR, GSM HR, EFR, and AMR. Note also that the older XCDR card
only supports GSM full rate.
When a mix of transcoding equipment (GDP, EGDP/GDP2) is used in conjunction with AMR being enabled,
the MSC must choose a CIC which is attached to an EGDP or GDP2 if AMR is the only option allowed in the
Channel Type element of the Assignment Request or Handover Request messages. If AMR is one of the
possible options (FR or EFR being the others) then the MSC should choose an EGDP/GDP2 CIC. If the call is
not AMR possible, the MSC should choose a GDP CIC.
If AMR is indicated as the only option and a CIC attached to a GDP is selected, the call will be rejected.
{22064} Similarly, when GSM HR is the only option allowed, the MSC must avoid choosing an EGDP CIC.
The ability of the MSC to select a CIC based on the available channel types is called “circuit pooling". The
BSC does not support the option to do the CIC selection itself, nor the circuit pool and circuit pool list
elements. It is therefore incumbent upon the MSC to do the selection. Previous discussions with MSC
vendors (Alcatel, Siemens, Nokia, and Nortel) have shown that they support or will support circuit pooling.
(Specifically it was asked about circuit pool 26, which all except Alcatel support - Alcatel supports circuit
pool 27.)
This topic is expanded upon in "Transcoding" on page 6-69 in Chapter 6, "BSC planning steps and rules," and
"Transcoding" on page 7-13 in Chapter 7, "RXCDR planning steps and rules,".
4-24 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Miscellaneous information
For more detailed information on circuit pooling, refer to GSM 08.08, Mobile-services Switching Centre
—Base Station System (MSC - BSS) interface; Layer 3 specification.
68P02900W21-R 4-25
28 Feb 2006 GMR-01
Half rate utilization Chapter 4: AMR and {22064} GSM planning
Half rate utilization

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
A number of parameters associated with the usage of half rate (hr) have been introduced to allow the operator
to tailor their system to suit their needs. Brief descriptions of these parameters and how they affect system
operation are provided here.
Parameter descriptions
Unconditionally forcing hr usage

Force hr usage (force_hr_usage)
This parameter allows the operator to force hr usage when assigning a resource. The MSC channel type
preference will be overridden whenever possible. The parameter is checked upon arrival of a new call
entering the system and all handovers.
The parameter can be set to enabled/disabled and defaults to disabled. It is configurable on a BSS basis.
Cell congestion threshold forcing hr usage

Congestion threshold for hr usage (new_calls_hr)
This parameter is used to qualify hr usage in a cell with the level of cell congestion (i.e. busy traffic channels).
When triggered, the MSC channel type preference is overridden whenever possible. The parameter is checked
upon arrival of a new call entering the system and for all handovers.
For multi-zone cells, the BSS considers only outer zone resources when establishing whether the threshold
has been exceeded. Both the fr and hr resources within the outer zone are used for the calculation. See also
the Inner zone utilization threshold.
This parameter’s range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is disabled and is
the default value. It is configurable on a cell basis.
Congestion relief
Some capabilities of hr utilization are similar to, or make use of the calculations of, some parts of the existing
congestion relief feature set; in particular, directed retry and advanced congestion relief. These features must
be enabled in order for those particular hr capabilities to operate properly. A brief description of the pertinent
congestion relief features is provided for completeness.
Advanced congestion relief allows the operator to set thresholds, in units of percentage, on a cell basis
which can trigger the handover of a number of calls to neighbouring cells in order to reduce congestion
in the triggering cell.
4-26 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Half rate utilization
There are two sets of thresholds defined within a cell that control the triggering of congestion based
inter-cell handovers:
• tch_congest_prevent_thres (1-101).
• mb_tch_congest_thres (1-101).
The tch_congest_prevent_thres parameter specifies the level at which the congestion relief
procedure is initiated. The mb_tch_congest_thres parameter specifies the level at which a MultiBand
MS is redirected to the preferred band. mb_tch_congest_thres must be less than or equal to
tch_congest_prevent_thres.
When the congestion relief threshold (tch_congest_prevent_thres) is exceeded, the BSS behaves
according to the setting of the element ho_exist_congest:
• Attempts to handover as many calls as the number of queued requests,
• Attempts to handover as many calls as meet the congestion handover criteria.
Calls within the cell take RF conditions into account, so only the MSs most likely near the candidate cell(s)
are moved.
Directed retry (mb_tch_congest_thres) redirects new traffic when the cell is congested, resulting in
the new call being moved to an alternative cell.
Call reconfiguration threshold

Intra-cell fr to hr call reconfiguration threshold (reconfig_fr_to_hr)
When the indicated threshold is exceeded, some fr calls within a cell are reconfigured (via handover) to a hr
channel within the same cell in order to reduce congestion in that cell. This mechanism works in conjunction
with the congestion relief feature, and requires congestion relief to be enabled (within the cell). The threshold
is calculated upon arrival of a new call entering the system and all handovers.
The BSS applies qualification criteria to the “half rate capable" full rate calls prior to allowing
the reconfiguration to a half rate traffic channel. The qualification is based upon the existing
congestion relief (directed retry alternatives) criteria for congestion based inter-cell handovers.
The criteria identifies calls which are at the extremities of the cell by using a power budget
calculation involving the neighbour handover congestion margin. The BSS does not perform
reassignment to a half rate traffic channel for a call which is identified by the existing congestion
relief calculations as being at the extremities of the cell. This qualification is performed in an
attempt to ensure that the user is provided with adequate QoS when the call is reassigned to a
half rate traffic channel.
For multi-zone cells, the BSS considers only outer zone resources when establishing whether the threshold
has been exceeded. Both the fr and hr resources within the outer zone are used for the calculation. See also
the Inner zone utilization threshold.
Once triggered, the BSS reconfigures as many qualifying existing hr-capable calls (currently using fr) to use
hr as there are hr resources available.
68P02900W21-R 4-27
28 Feb 2006 GMR-01
This parameter’s range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is disabled and is
the default value. It is configurable on a cell basis.
Inner zone utilization threshold

Inner zone utilization threshold (inner_hr_usage_thres)
This parameter is necessary because the reconfig_fr_to_hr and new_calls_hr thresholds are
triggered by the usage of the outer zone only within a cell.
Both concentric cells and dual band cells are multi-zone cells. The situation can occur where the inner zone
has low usage but the outer zone is congested such that the reconfig_fr_to_hr threshold is exceeded.
The BSS will attempt to trigger full rate to half rate intra-cell handovers for the calls that qualify. If some
of the calls that qualify reside within the inner zone, the BSS will attempt to reconfigure these “half rate
capable" full rate calls to half rate when the inner zone is not congested.
A similar situation can occur when the new_calls_hr threshold is exceeded and new calls are assigned. To
prevent these situations from occurring, an additional threshold is applied.
The inner zone utilization threshold (inner_hr_usage_thres) is used for this purpose. It protects against
reconfigurations within, and new hr calls assigned to the inner zone, when the usage of the inner zone is low.
The inner_hr_usage_thres is applied when the utilization of half rate is triggered by
reconfig_fr_to_hr being exceeded and when new_calls_hr is exceeded.
If the threshold reconfig_fr_to_hr has been exceeded, half rate capable full rate calls residing on
the inner zone will only be eligible as candidates for reconfiguration from full rate to half rate if the
inner_hr_usage_thres has also been exceeded.
If the threshold new_calls_hr has been exceeded, half rate capable calls will only be eligible to be assigned
directly to half rate channels within the inner zone if the inner_hr_usage_thres has also been exceeded.
This parameter’s range is 0-101 in steps of 1%. The value of 101 indicates no half rate usage in the inner zone
and is the default value. It is configurable on a cell basis.
Reserved timeslots
Half rate resource guard limit (hr_res_ts)
When congestion triggered half rate usage is employed, either through call assignments (cell congestion
threshold forcing hr usage) or through reconfigurations (call reconfiguration threshold), there must be
available hr resources for the mechanism to work properly. This is normally accounted for by setting
reconfig_fr_to_hr and new_calls_hr such that when they are triggered, there are sufficient
resources available for the half rate calls. However, in multi-zone cells, inner zone resources could be
exhausted before any congestion thresholds are reached (the thresholds only consider outer zone resources).
To ensure that there are half rate resources available, the operator has the option to allow the BSS to reserve
a maximum number of (half rate capable) traffic timeslots within the inner zone. This facility is provided
to ensure that when a multi-zone cell enters into congestion, there are half rate capable resources available
within the inner zone to allow half rate utilization related procedures to be employed. When reserved
timeslots only are left within an inner zone, a full rate resource is sought in the outer zone prior to the
reserved timeslots in the inner zone being considered.
The reserved timeslots are applied to the inner zone only, although it is configurable on all cells and not just
multi-zone cells. It has no effect when set on a non multi-zone cell.
4-28 68P02900W21-R
GMR-01 28 Feb 2006
The actual value within the inner zone can be dynamically limited to be less than hr_res_ts by the BSS. The
BSS will limit the hr_res_ts for the inner zone if the BSS detects that the inner_hr_usage_thres
will not be able to be exceeded if the hr_res_ts element is left as the operator defined. hr_res_ts is
also limited by the number of half rate capable resources available in the cell or zone.
This parameter’s range is 0-255 in steps of one timeslot. The default value is 2 timeslots (note that each
timeslot is capable of supporting two hr calls). It is configurable on a cell basis.
Intra-cell hop count

Number of intra-cell interference handovers (hr_fr_hop_count)
Intra-zone intra-cell hr interference handovers are governed by the BSS in a similar manner to how fr calls are
governed by the existing hop_count and hop_count_timer elements.
The current functionality restricts the number (hop_count) of intra-cell interference based handovers within
a period (hop_count_timer). If the hop_count is exceeded within the hop_count_timer period,
the BSS triggers an inter-cell quality based handover for the call. If so many intra-cell interference based
handovers are performed in a short period of time, it indicates that the cell is experiencing problems with bad
interference and the call would be best served by the network by being moved to another cell.
A similar mechanism is employed for intra-cell half rate interference handovers. All intra-cell half rate
interference handovers contribute to the existing hop_count. The hr_fr_hop_count parameter is
provided to limit the number of intra-cell interference based handovers from hr to fr.
The BSS does not allow an intra-cell congestion handover to be performed by a call for which the
hr_fr_hop_count is met and the hop_count_timer has not expired. This allows a call experiencing
repeated high interference levels to remain on a fr channel rather than hr during congestion. An inter-cell
handover is not triggered by hr_fr_hop_count, for this functionality the existing hop_count parameter
is used. Note that the hop count timer (hop_count_timer) is an existing parameter, used to qualify the
new hr (hr_fr_hop_count) element and the existing element (hop_count).
This parameter’s range is 0-255 in steps of 1. The default value is 1 hop. It is configurable on a cell basis. It
must be set to a value less than or equal to hop_count.
hr intra-cell handover support

Enable/Disable (support) of hr intra-cell handover (hr_intracell_ho_allowed)
The hr_intracell_ho_allowed element contains an option to disable intra-cell quality handovers
for half rate channels. The element has 4 possible values which take effect when a hr intra-cell handover is
triggered by the BSS. For interference based handovers it further specifies the possible target channel
types - full and/or half rate. Quality based handovers always target a full rate channel when handovers
are enabled. Note that the force_hr_usage element overrides any preference specified with the
hr_intracell_ho_allowed element. The value of the element will cause the following behaviour:
If hr_intracell_ho_allowed is set to “hr intra-cell handovers are disabled. Handover Required sent to
MSC", then the control for this hr intra-cell handover is passed to the MSC by sending a Handover Required
message, identifying the current cell as the only handover candidate.
This functionality mirrors the fr functionality specified by the element intra_cell_handover_allowed.
If hr_intracell_ho_allowed is set such that “hr intra-cell handovers are disabled. No Handover
Required sent to MSC", then hr intra-cell handovers are not supported within the cell. The intra-cell handover
request will be ignored by the BSS.
This functionality mirrors the fr functionality specified by the element intra_cell_handover_allowed.
68P02900W21-R 4-29
28 Feb 2006 GMR-01
If hr_intracell_ho_allowed is set such that “hr intra-cell handovers are enabled. fr only allowed",
the BSS attempts to allocate a fr channel as a target resource for the hr intra-cell interference or quality
based handover.
If hr_intracell_ho_allowed is set such that “hr intra-cell handovers are enabled. hr allowed", the
BSS attempts to allocate a hr or fr target resource for the hr intra-cell interference based handover, based
on the congestion levels within the cell, the MSC preference and the operator preference. A quality based
handover will always target a fr channel.
This parameter’s range is 0-3 and is configurable on a cell basis. The default value is 3.
0: “half-rate Intra-Cell handovers are not initiated by
the BSS. Handover Required sent to MSC".
1: “half-rate Intra-Cell handovers are disabled.
Handover Required not sent to MSC".
2: “half-rate Intra-Cell handovers are enabled. Full-rate
only allowed".
3: “half-rate Intra-Cell handovers are enabled.
Half-rate and full-rate allowed".
{22064} It is recommended that hr_intracell_ho_allowed is set to a value of 2 or 3 dependent on the half rate
(AMR or GSM) strategy of the network. Where half rate is being used to maximise capacity gains through
the use of half rate, with call quality of secondary concern, then a value of 3 should be used. Where half
rate is being used to provide capacity gains through the use of half rate but with more emphasis placed
on call quality, then a value of 2 should be used.
Operational aspects
Using half rate exclusively

In some situations the operator may decide to maximize half rate usage in the system by enabling the force
AMR hr usage parameter (force_hr_usage). This forces all hr-capable MSs to be placed upon an
available hr capable carrier, provided it is possible (i.e. MSC allows AMR hr and/or {22064} GSM hr, the
CIC is capable of the transcoding, a hr channel is available, etc.).
This setting maximizes erlang capacity in the system at the expense of call quality (due primarily to the lower
MOS of hr) and to a lesser extent the prohibiting of hr to fr intra-cell handovers).
As an alternative to using force_hr_usage, new_calls_hr can be set very low and hr_intracell_ho_allowed
used to control intra-cell handovers. hr_intracell_ho_allowed can then be set to allow hr to fr intra-cell
handovers, thus improving call quality in some instances.
Using half rate in conjunction with congestion

The system may be configured, on a cell basis, to tie hr usage to the congestion level within a cell
(new_calls_hr). This allows calls to be handled at the higher voice quality (fr) level until cell congestion
reaches a configurable threshold, at which point new hr-capable calls are assigned to hr channels (hr-capable
means that the MSC allows AMR and/or GSM hr, the CIC is capable of the transcoding, a hr channel is
available, etc).
4-30 68P02900W21-R
GMR-01 28 Feb 2006
By using the existing congestion relief feature and the cell reconfiguration threshold, additional capacity
can be attained. As described earlier, the congestion relief feature can be used to identify calls most likely
to benefit from a switch to another, less congested, cell, and perform a handover to move them. When this
mechanism is employed, the operator may then also use the cell reconfiguration capability to increase capacity
further by reconfiguring qualifying fr calls to hr.
Congestion is calculated as a function of busy timeslots (and half timeslots) divided by all timeslots (not
counting control channels).
The inner zone utilization threshold is used in multi-zone cells and will prevent unnecessary inner zone
reconfigurations.
The configuration of parameters takes place as follows:
The congestion threshold for hr usage (new_calls_hr) is chosen.
If it is desired to attain additional capacity through call reconfigurations, and the congestion relief feature is
enabled, then the cell reconfiguration threshold is set at a level at which it wishes to force qualifying MSs
(on a fr channel) to be reconfigured to hr (reconfig_fr_to_hr). This may be set above or below
the congestion relief threshold, as calls qualifying for congestion relief are not candidates for fr to hr
reconfiguration. If voice quality (i.e. fr) is the primary concern, then congestion relief handover should be
performed first. Also, the reconfiguration threshold must not be set below the congestion threshold for hr
usage (new_calls_hr), otherwise calls could be assigned fr and immediately reconfigured to hr.
For multi-zone cells, an inner zone utilization threshold is chosen. In many cases the criteria for inner zone hr
utilization will be the same as the outer zone. In these cases the inner zone utilization threshold may be set
the same as the new call threshold or the reconfiguration threshold.
Following the above descriptions, the thresholds could be set in the pattern shown in Figure 4-11.
Figure 4-11 Congestion threshold settings for AMR half rate
CONGESTION
HIGH
reconfig_fr_to_hr
new_calls_hr and inner_hr_usage_thres

Congestion relief threshold
LOW
hr intra-cell handover control

The intra-cell hop count (hop_count) is set to the desired value. It must be set equal to or less than the
hop_count parameter. The hop count timer (hop_count_timer) is also set to the desired value.
The level of support of hr intra-cell handovers (hr_intracell_ho_allowed) is configured.
The value of these settings is particular to the system being optimized.
68P02900W21-R 4-31
28 Feb 2006 GMR-01
AMR hr and {22064} GSM hr operation

AMR hr and GSM hr are compatible with each other. When GSM half rate and AMR are enabled in the BSS
and in a cell, half rate enabled carriers will be capable of supporting both AMR and GSM calls. The selection
of AMR or GSM will be dependent upon the MSC preferences (indicated in the Channel Type element of the
Assignment Request or Handover Request messages) and the capabilities of the chosen CIC.
4-32 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Hardware
Hardware
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Equipment descriptions
New hardware (and associated software) has been developed to enhance the operation of AMR and/or
{22064} GSM half rate. Each new item is described here.
DSW2 and DSWX

The DSW2 provides two improvements over existing capability:
• It allows for 8 kbit/s subrate switching in the BSC and RXCDR (called extended subrate
switching (ESS) mode).
• When used in the RXCDR along with DSWXs, it allows for double the timeslot capacity (with
1 extension shelf, 1024 timeslots per shelf) (called enhanced capacity (EC) mode).
ESS mode is used to decrease backhaul costs when half rate is in use between the BTS and BSC and (if
also enabled in the RXCDR) the BSC and RXCDR. As long as the 7.95 codec mode (AMR) is not used,
the backhauled TRAU will fit in an 8 kbit/s subchannel. On the BTS - BSC interface, this can result in a
50% saving in backhaul costs per 8 kbit/s hr-capable carrier. Without 8 kbit/s switching, each half rate call
will require a full 16 kbit/s backhaul bearer, or four 64 kbit/s timeslots per carrier. With 8 kbit/s switching,
the same backhaul as is required for full rate (two 64 kbit/s timeslots) is used. A similar saving can be
achieved on the BSC - RXCDR interface.
When ESS mode is enabled in the BSC, 8 kbit/s backhaul can be used between the BTS and BSC. For every
connected RXCDR with ESS enabled, 8 kbit/s backhaul can be used between the BSC and that RXCDR.
Use of ESS mode requires all DSW2s to be used (within the BSC or RXCDR). KSWXs and DSWXs may be
used (exclusively or mixed), with the restriction that a KSWX may not be connected to a DSWX or vice-versa.
EC mode is available in the RXCDR and can be used to increase the number of timeslots available. Each
device (i.e. MSIs, GDPs, EGDPs, and GDP2s) requires a specific number of timeslots. By increasing the
number of timeslots available across two shelves, more combinations of equipment are possible. This
capability is likely to be used in conjunction with the RXU3 shelf, which provides for additional E1
connectivity. (More detailed information is available in later chapters of this manual.)
EC mode requires the use of all DSW2s and DSWXs.
DSW2s and DSWXs are backwards compatible with KSWs and KSWXs, and are interchangeable (in non-ESS
and non-EC modes) with, again, the restriction that a KSWX may not be connected to a DSWX or vice-versa.
68P02900W21-R 4-33
28 Feb 2006 GMR-01
Hardware Chapter 4: AMR and {22064} GSM planning
EGDP and GDP2

The current GDP can terminate 30 terrestrial circuits and handle the transcoding for GSM Full Rate (FR),
Enhanced Full Rate (EFR) and {22064} GSM Half Rate (HR). It takes up one slot and connects to a single E1
span line.
Due to the added processor burden required by AMR, the GDP cannot support 30 channels beyond
FR/EFR/HR. Two cards however, operating in a tandem configuration via a firmware upgrade, can support a
full 30 channels of FR/EFR/AMR. This arrangement of two GDPs is called an EGDP. It occupies two card
slots and can terminate one E1 span line.
{22064} EGDP cannot support GSM HR.

A more efficient solution is provided via a new development, the GDP2. With its upgraded DSP and other
enhancements, the GDP2 is capable of transcoding 60 channels of FR/EFR/HR/AMR. It takes up one card slot
and can terminate two E1 span lines.
All card combinations may be present in a system simultaneously.
When the GDP2 is inserted into a card slot that terminates only one E1 span (a non RXU3 shelf) 30 terrestrial
circuits are supported.
RXU3
The existing RXU shelf provides 19 MSI slots (see Note), of which 5 are considered MSI-capable, meaning
they have connectivity for two E1 span lines. The other 14 slots can terminate only one E1 span line, as they
were designed to hold GDPs (or the older XCDRs).
The RXU3 shelf provides for termination of two E1 span lines per card slot. A combination of MSIs and
XCDR/GDP/EGDP/GDP2s can share these 19 slots without connectivity restriction (timeslot restrictions still
apply). This enables the GDP2s to be used to capacity. Within the RXCDR, enhanced capacity mode must be
enabled to access the second E1 when GDP2s are used.
Within the current BSC, the BSU shelf contains 12 MSI slots, of which up to 6 slots may be used for the
transcoder function. All slots support the connectivity for two E1 terminations per card slot, allowing
GDP2s to be used to capacity.
These are called “MSI" slots, but they may contain either a MSI or a transcoder board.
BSSC3
The BSSC2 cabinet has connectivity for up to 48 E1 span lines, which is the capacity of two of the existing
shelves. To accommodate the additional shelf capacity, a new BSSC3 cabinet has been developed which
can terminate up to 76 E1 span lines. This is accomplished by adding 6 additional T43/BIB boards to
the cabinet top.
4-34 68P02900W21-R
GMR-01 28 Feb 2006
Like the BSSC2, the BSSC3 cabinet can function as a BSC (BSC2) or a RXCDR (RXCDR2), depending
on how the cabinet shelves are equipped. Figure 4-12 shows the alternative configurations available
for the BSSC3.
Earlier BSUs/RXUs may be used in the BSSC3 cabinet instead of or in conjunction with the
BSU2/RXU3.
Figure 4-12 Alternative configurations for the BSSC3 cabinet
BSC2 Configuration RXCDR2 Configuration
BSU2 RXU3 RXU3
BSU2 BSU2 BSU2 RXU3 RXU3
Basic BSC2 With BSC2 with Basic RXCDR2 with

expansion transcoding RXCDR2 expansion
shelf, or as 2 shelf
separate
BSC2s
68P02900W21-R 4-35
28 Feb 2006 GMR-01
Backhaul
Table 4-5 and Table 4-6 show how one fr voice call or two hr calls on a single air timeslot are mapped to
terrestrial resources at the RTF.
Table 4-5 shows how the amount of backhaul configured for each timeslot for a given RTF is based on database
parameter settings. The amount of terrestrial backing allocated for a RTF is based on three parameters:
• hr_enabled (with values 0 = no half rate, 1 = half rate)
• allow_8k_trau (with values 0 = no 8k TRAU, 1 = 8k TRAU)
• pkt_radio_type (adds EGPRS support and supercedes allow_32k_trau)
Table 4-5 Backhaul configuration based on parameter settings
pkt_radio_type
al- 1 = 16k 2 = 32k 3 = 64k
hr_enabled 0 = voice
low_8k_trau data and data and data and
only
voice voice voice
0 Don’t care 16k 16k 32k {23769}
VersaTRAU
1 0 32k 32k (data 32k {23769}
will use only Not Sup-
16k) ported (al-
low_8k_trau
cannot be
set to 0 if
pkt_ra-
dio_type is
3)
1 1 16k 16k 32k {23769}
VersaTRAU
Table 4-6 shows how a fr call or two hr calls are placed onto the terrestrial backhaul.
4-36 68P02900W21-R
GMR-01 28 Feb 2006
Table 4-6 Call placement on terrestrial backhaul
pkt_radio_type
hr_enabled allow_8k_trau 0 = voice 1 = 16k data 2 = 32k data
3 = 64k data and voice
only and voice and voice
0 Don’t care full rate call on 16k full rate call full rate call on {23769} 16k
on left most subrate corresponding to the air
16k subrate timeslot - see Table 4-7
group of the
32k
(duplicated on
both 16k in
the UL)
1 0 2 half rate calls on separate 16k subrates {23769} Not supported
1 1 2 half rate calls share one 16K subrate {23769} Half rate with 8K
switching assigns the two half
rate voice channels to the two
bits allocated to an air timeslot.
The first half rate voice channel is
allocated bit 0. The second half
rate voice channel is allocated
bit 1. For example, air timeslot
B has the first half rate channel
assigned to B0 and the second half
rate channel assigned to B1 - see
Table 4-7
Table 4-7 {23769} Voice call mapping on the backhaul for a 64K RTF
DS0 DS0 DS0 DS0 DS0 DS0 DS0 DS0

Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
VersaTRAU subchannel 0 A0 A1 B0 B1 C0 C1 D0 D1
VersaTRAU subchannel 1 E0 E1 F0 F1 G0 G1 H0 H1
VersaTRAU subchannel 2
Key: A - H are air timeslots 0 - 7 respectively.
The VersaTRAU Subchannel2 and any higher numbered VersaTRAU Subchannels are always
used only to carry the multiplexed data for all the PDCHs configured on this carrier.
68P02900W21-R 4-37
28 Feb 2006 GMR-01
The above tables give sample configurations for 16kbit/s, 32kbit/s and 64kbit/s backhaul.
Figure 4-13 and Figure 4-14 ahead apply only to the 16kbit/s backhaul.
When a fr call is connected, the BTS-BSC-RXCDR backhaul path is as shown on the left in Figure 4-13. 16
kbit/s backhaul is required on all the legs.
When an AMR hr call is connected which includes the 7.95 kbit/s rate in the Active Codec Set, then a similar
backhaul path is needed, as shown on the right in Figure 4-13.
Figure 4-13 AMR backhaul paths
16 kbit/s CIC 16 kbit/s CIC

Ater-CIC Ater-CIC
connection connection
EGDP / GDP2 EGDP / GDP2
RXCDR RXCDR
Switch Switch
16 kbit/s Ater 16 kbit/s Ater

allocated allocated
BSC BSC
Switch Switch
16 kbit/s Abis 16 kbit/s Abis

backhaul backhaul
BTS BTS
Switch Switch
CCU AMR fr call over CCU hr call over air

air interface interface
(w / 7.95 kbit/s)
4-38 68P02900W21-R
GMR-01 28 Feb 2006
For a connected AMR hr call not requiring the 7.95 codec rate{22064} or a GSM hr call, if ESS mode is
enabled in the BSC, but not in the RXCDR, then the backhaul path shown on the left in Figure 4-14 results.
For the same call, if ESS mode is enabled in both the BSC and the RXCDR then the path shown on the right in
Figure 4-14 results. (The idle tone insertion is used internally to fill out the 16 kbit/s timeslot.)
Figure 4-14 hr backhaul paths - ESS mode enabled
16 kbit/s CIC 8 kbit/s CIC

Ater-CIC Ater-CIC
connection connection
EGDP / GDP2 EGDP / GDP2
8 kbit/s
idle tone
RXCDR RXCDR
Switch Switch
16 kbit/s Ater 8 kbit/s Ater

allocated allocated
8 kbit/s
idle tone
BSC BSC
Switch Switch
8 kbit/s Abis 8 kbit/s Abis

backhaul backhaul
BTS BTS
Switch Switch
CCU CCU
hr call over air hr call over air
interface interface
68P02900W21-R 4-39
28 Feb 2006 GMR-01
Summary
AMR transcoding can be supported using existing GDPs working in a tandem configuration, the EGDP, or
with the GDP2. The former provides a capacity of one half (15 channels of FR/EFR/AMR per card slot)
of what is currently supported for the GDP (30 channels FR/EFR/HR per card slot), the latter double the
capacity (60 channels of FR/EFR/HR/AMR per card slot). GSM HR transcoding can be supported with the
GDP (30 channels) or the GDP2 (60 channels).
GDP2s will work in the existing RXU shelf, but only at half capacity because there is connectivity of only one
E1 per card slot (for most slots). The RXU3 shelf provides 2 x E1 connectivity for all card slots (enhanced
capacity mode must be enabled to access the second E1 when GDP2s are used in non–MSI slots). The existing
BSU shelf provides two E1 connectors per card slot, for local transcoding configurations.
The current BSSC2 cabinet provides for 48 E1 terminations. In order to use the RXU3 shelves to capacity the
BSSC3 cabinet has been developed. This can terminate 76 E1 span lines.
The DSW2 can be utilized to reduce backhaul costs between both the BTS and BSC and the BSC and
RXCDR, when hr is used. Additionally, within the RXCDR, use of DSW2s/DSWXs can support a greater
number of timeslots, which translates to more combinations of card types, particularly MSIs.
The proper combination(s) of equipment needs to be tailored per network.
4-40 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
5
BTS planning steps and rules
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The planning steps and rules for the BTS, including macrocell and microcell are provided here. The planning
steps and rules for the BSC are in Chapter 6, "BSC planning steps and rules," and remote transcoder (RXCDR)
are in Chapter 7, "RXCDR planning steps and rules,". The topics described here are as follows:
• "BTS planning overview" on page 5-2
• "Macrocell cabinets" on page 5-4
• "Microcell enclosures" on page 5-7
• "Receive configurations" on page 5-9
• "Transmit configurations " on page 5-13
• "EGPRS enabled CTU2 configuration" on page 5-16
• "Antenna configurations" on page 5-18
• "Carrier equipment (transceiver unit)" on page 5-19
• "Micro base control unit (microBCU)" on page 5-24
• "Network interface unit (NIU) and site connection" on page 5-25
• "BTS main control unit" on page 5-28
• "Cabinet interconnection" on page 5-32
• "Battery back-up provisioning" on page 5-38
• "External power requirements" on page 5-39
• "Network expansion using macro/microcell BTSs" on page 5-41
• "Line interface modules (HIM-75, HIM-120)" on page 5-43
• "DRI/Combiner operability components" on page 5-44
68P02900W21-R 5-1
28 Feb 2006 GMR-01
BTS planning overview Chapter 5: BTS planning steps and rules
BTS planning overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
To plan the equipage of a BTS site certain information must be known. The major items include:
• The number of cells controlled by the site.
• The number of carriers required.
• The number of standby carriers per cell.
• The output power per cell.

The required output power must be known to ensure that the selected combining method
and antenna configuration provides sufficient output power. Alternatives include changing
combiner types or using more than one transmitting antenna. Duplexers may be used to reduce
the amount of cabling and the number of antennas.
• The antenna configuration for each cell.
• The cabinet/enclosure types to be used.
• Future growth potential.

It is useful to know about potential future growth of the site in order to make intelligent trade
offs between fewer cabinets/enclosures initially and ease of expansion later.
• Whether or not there are equipment shelters at the site.

Macro/microcell outdoor equipments should be included in the BTS planning for locations
where there are no equipment shelters. Macro/microcell should be included where rooftop
mounting or distributed RF coverage is required or where space and access are restricted.
• Whether or not battery backup equipment is needed for the outdoor equipment.
5-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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" on page 5-4.
3. Number of microcell enclosures required, refer to the section "Microcell enclosures" on

page 5-7.
4. The receiver configuration (including planning for Dual Band), refer to the section "Receive
configurations" on page 5-9.
5. The transmit configuration, refer to the section "Transmit configurations " on page 5-13.
6. The EGPRS enabled CTU2 configuration, refer to the section "EGPRS enabled CTU2
configuration" on page 5-16.
7. The antenna configuration, refer to the section "Antenna configurations" on page 5-18.
8. The amount of carrier equipment required, refer to the section "Carrier equipment
(transceiver unit)" on page 5-19.
9. The number of micro base control units required, refer to the section "Micro base control
unit (microBCU)" on page 5-24.
10. The number of network interface units required, refer to the section "Network interface unit
(NIU) and site connection" on page 5-25.
11. The number of E1/T1 links required, refer to the section "Network interface unit (NIU) and
site connection" on page 5-25.
12. The number of main control units required, refer to the section "BTS main control unit" on
page 5-28.
13. The number of FOX and FMUX boards required, refer to the section "Cabinet
interconnection" on page 5-32.
14. The battery back-up provisioning, refer to the section "Battery back-up provisioning" on
page 5-38.
15. The external power supply requirements, refer to the section "External power requirements"
on page 5-39.
68P02900W21-R 5-3
28 Feb 2006 GMR-01
Macrocell cabinets Chapter 5: BTS planning steps and rules
Macrocell cabinets
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Horizon II macro
Horizon II macro is the next generation replacement for Horizonmacro. From a capacity perspective, Horizon
II macro and Horizonmacro are identical and support the same numbers of carriers, RSLs and E1s. The
Horizon II macro supports equipping of 4 RSLs per E1, reducing the amount of E1 spans needed at a site that
requires more than 2 RSLs. Horizonmacro and M-Cell BTSs currently support 2 RSLs per E1.
A Horizon II macro cabinet (indoor or outdoor) can support 12 carriers when populated fully with 6 CTU2s,
used in double density mode, or six carriers when the 6 CTU2s are used in single density mode. Expansion
beyond the maximum 12 carriers per cabinet requires additional cabinets, and maximum RF carriers supported
per Horizon II macro site controller (HIISC) is 24.
The Horizon II macro outdoor is a Horizon II macro indoor along with an outdoor enclosure that incorporates
heat management. The Horizon II macro outdoor can operate in the temperature range from -40 °C to 50 °C.
The Horizon II macro does not support the use of CCBs.
Horizon macro
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.
CCBs cannot be used with the Horizonmacro indoor cabinet if the cabinet is to be installed in
the 12 carrier outdoor enclosure.
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.
5-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Macrocell cabinets
Horizon compact and Horizon compact2
The Horizoncompact / Horizoncompact2 is an integrated cell site, designed primarily for outdoor operation
and consists of:
• The BTS unit. This is similar to Horizonmicro / Horizonmicro2 and is a two-carrier cell
with combining.
• 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.
The main difference between the Horizoncompact and the Horizoncompact2 is that the latter can
be expanded to support an additional two BTSs.
For the purposes of this document, future references to Horizoncompact2 also include
Horizoncompact unless specifically stated otherwise.
M-Cell6
The M-Cell6 cabinet can support six carriers (TCUs or CTU2 Adapter in an EGPRS configuration) or twelve
carriers (TCUs or CTU2 Adapter in a non-EGPRS configuration). Expansion beyond this requires additional
cabinets. Outdoor cell sites are provided with an ancillary cabinet and a side cabinet.
TheM-Cell6 HMS offers the following options:
• Fans that circulate ambient air through the cabinet, for both indoor and outdoor units.
• A heat exchanger for ambient temperatures up to 45 °C, for outdoor cabinets only.
• An air conditioning unit for ambient temperatures up to 55 °C, for outdoor cabinets only.
M-Cell2
The M-Cell2 cabinet can support two carriers (CTU2 Adapter in EGPRS configuration) or four carriers
(CTU2 Adapter in non-EGPRS configuration).
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.
68P02900W21-R 5-5
28 Feb 2006 GMR-01
Macrocell cabinets Chapter 5: BTS planning steps and rules
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:
• Fans that circulate ambient air through the cabinet, for both indoor and outdoor units.
• A heat exchanger for ambient temperatures up to 45 °C, for outdoor cabinets only.
• An air conditioning unit for ambient temperatures up to 55 °C, for outdoor cabinets only.
5-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Microcell enclosures
Microcell enclosures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Horizon II mini
Horizon II mini, introduced in GSR7, can satisfy all the current Horizon II macro requirements but also add
significant functionality that enables it to be classed as a Mini Macro BTS similar to the M-Cell2 BTS. The
architecture is based on the Horizon II macro architecture and effectively Horizon II mini will behave as if it
were a Horizon II macro cabinet. The Mini BTS can be expanded from the Horizon II macro, Horizonmacro
and M-Cell6. The Horizon II mini enclosure can house 2 CTU2s that can be configured in both single
density and double density mode. As a result, the carrier capacity is 1-4 carriers, for a maximum network
configuration of 16 to 24 carriers per site dependant on cabinet capacity.
Horizon II mini is available as both an indoor and outdoor variant, and can be wall, floor or rack mounted.
The wall may be concrete, brickwork, stonework, dense aggregate blockwork, or reconstituted stone, with
or without rendering.
Software parameters have been added to distinguish Horizon II mini cabinets to allow for easier configuration.
The Horizon II mini parameters allow for:
• Only one BTP to be equipped to a Horizon II mini master cabinet.
• A maximum of two physical radios to be equipped to a Horizon II mini cabinet.

Due to the compact and low-cost nature of this product, there is no accommodation for redundancy hardware.
Horizon II mini can only be equipped with CTU2 radios and, therefore, supports EGPRS.
The Horizon II mini uses E1 links for both TRAU and RSL and can be expanded from a
Horizonmacro family BTS or be used as a network of Horizon II minis.
SDH feature
Horizon II mini also supports an auxiliary power supply or an optional 3rd party SDH module requiring a 48
V dc power supply up to a maximum dissipation of 60W.
When the outdoor enclosure is configured with the SDH module, it shall be a standalone only BTS.
The outdoor enclosure configuration cannot be expanded in a network as the comms power card
to supply -48 V dc will need to be inserted in the Site I/O slot.
68P02900W21-R 5-7
28 Feb 2006 GMR-01
Microcell enclosures Chapter 5: BTS planning steps and rules
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.
The main difference between the Horizonmicro and the Horizonmicro2 is that the latter can be
expanded to support an additional two BTSs.
For the purposes of this document, future references to Horizonmicro2 also include Horizonmicro
unless specifically stated otherwise.
Horizon II micro
The Horizon II micro is an integrated cell site, designed for indoor and outdoor microcellular applications and
consists of a single small two carrier BTS (CTU2) unit. It can be configured for 2 carriers in double density
mode for GSM/GPRS or 1 carrier in Single Density mode for EGPRS.{28075} If ITS is unrestricted and
enabled, double density mode can be used for EGPRS. It can be seen as a replacement to the Horizonmicro2
where that deems obsolete (because of an obsolete chip set or where features no longer can be supported)
and is to target applications in both 900 MHz or 1800 MHz bands.
The Horizon II micro 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 or by an internal fan. The unit can operate at ambient temperatures up
to 50 °C.
5-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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.
Horizonmicro2 and Horizon II micro are 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.
68P02900W21-R 5-9
28 Feb 2006 GMR-01
Receive configurations Chapter 5: BTS planning steps and rules
GSM900
The following factors should be considered when planning the GSM900 receive equipment:
• Horizon II macro and Horizon II mini BTSs require one 900 MHz SURF2 for each cabinet.
Currently, for Horizon II macro only, a second (optional) 900 MHz SURF2 can be installed to
provide 4 branch diversity.
For Horizon II macro only, an optional SURF2 dual band adaptor allows a 900
MHz SURF2 and an 1800 MHz SURFs to be installed in the same cabinet,
thus providing dual band capability.
Receive antennas can be extended across Horizon II macro/Horizon II mini cabinets by using
the 900 SURF2 expansion ports to feed a SURF2 in another cabinet.
• Horizonmacro BTSs require one 900 MHz SURF for each cabinet. This has dual band
(900/1800 Mhz) capability.
Receive antennas can be extended across Horizonmacro cabinets by using the 900 SURF
expansion ports to feed a SURF in another cabinet.
• M-Cell2 and M-Cell6 BTSs require one DLNB for each sector.
Receive antennas can be extended across M-Cell6 cabinets by using the IADU expansion
ports to feed an IADU in another cabinet.
5-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Receive configurations
DCS1800
The following factors should be considered when planning the DCS1800 receive equipment:
• Horizon II macro and Horizon II mini BTSs require one 1800 MHz SURF2 for each cabinet.
Currently, the SURF2 is not dual band and only supports 900/1800 Mhz capability in separate
cabinets. For Horizon II macro only, a second (optional) 1800 MHz SURF2 can be installed to
provide 4 branch diversity.
Receive antennas can be extended across Horizon II macro/Horizon II mini cabinets by using
the 1800 SURF2 expansion ports to feed a SURF2 in another cabinet.
• Horizonmacro BTSs require one 1800 MHz SURF for each cabinet.
Receive antennas can be extended across Horizonmacro cabinets by using the 1800 SURF
expansion ports to feed a SURF in another cabinet.
Two types of 1800 SURF are available. One is 1800 MHz single band and the
other is 1800/900 MHz dual band.
• M-Cell2 and M-Cell6 BTSs require one LNA for each sector.
Receive antennas can be extended across M-Cell6 cabinets by using the LNA expansion ports
to feed a LNA in another cabinet.
DCS1800 and GSM900

It should be considered that Horizon II macro Dual Band capable cabinets require one 1800 MHz SURF2, one
900 MHz SURF2 and a Dual Band Adaptor, when planning dual band (that is, support for both DCS1800 and
GSM900 within a single cabinet) receive equipment.
• The maximum transceiver units for a dual band cabinet configuration is 3 CTU2s per
band. A third power supply is required.
• The rear SURF2 controls CTU2 radio slots 3, 4 and 5. The front SURF2 controls CTU2
radio slots 0, 1 and 2.
• Contact your Motorola Local Office for more information.
• Refer to Chapter 12, "Standard BSS and Horizon BTS configurations," for Dual Band
cabinet physical configuration.
68P02900W21-R 5-11
28 Feb 2006 GMR-01
Receive configurations Chapter 5: BTS planning steps and rules
Receiver planning actions

1. Determine the number of cells.
2. Determine the number of cells which have CTU2s/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.
When using CTU2s in double density mode, both carriers need to be in the
same sector and can be individually reset. Dropping one carrier does not affect
the second CTU2 carrier.
5-12 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Transmit configurations
Transmit configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The transmit equipment provides bandpass filtering and signal combining for the BTS cabinets. The CTU2
used in Horizon II macro can be configured to use a single high power carrier (single density mode) or two
lower power carriers (double density mode). For M-Cell2 and M-Cell6 cabinets, a TxBPF is required
for each antenna.
Horizonmicro2 and Horizon II micro are two carrier only, combined to a single antenna.
Horizoncompact2 is two carrier only, with two antennas.
The transmit configurations available for Horizon II macro, Horizon II mini, Horizonmacro, M-Cell2 and
M-Cell6 BTSs are listed in Table 5-1.
68P02900W21-R 5-13
28 Feb 2006 GMR-01
Transmit configurations Chapter 5: BTS planning steps and rules
Table 5-1 Transmit configurations
Number of Carriers BTS Type Cabinet Transmit Cabinet Transmit

Configurations Configurations
Wide Band Cavity Combining
Combining
1 M-Cell2 and M-Cell6 1 TxBPF Not available
1 Horizonmacro 1 DCF or 1 TDF Not available
1 or 2 Horizon II macro 1 DUP Not available
1 or 2 Horizon II mini 2 DUP (Bowtie- Not available
Combiner)
2 M-Cell2 and M-Cell6 1 HCOMB + 1 TxBPF 1 CCB output
2 Horizonmacro 1 DCF 1 CCB output
3 M-Cell6 2 HCOMB + 1 TxBPF 1 CCB output
3 Horizonmacro 2 DCF or 1 DDF 1 CCB output
3 or 4 Horizon II macro 1 DUP + 1 HCU or CCBs not supported
2 DUP and Air
3 or 4 Horizon II mini 2 DUP (Bowtie- CCBs not supported
Combiner) and Air
4 M-Cell6 2 HCOMB + 1 TxBPF 1 CCB output +
1 CCB extension
4 Horizonmacro 1 DDF + 1 HCU 1 CCB output +
1 CCB extension
1 CCB extension
5 Horizonmacro 2 DDF and Air 1 CCB output +
1 CCB extension
1 CCB extension
6 Horizonmacro 2 DDF and Air 1 CCB output +
1 CCB extension
6 Horizon II macro 1 DUP + 1 DHU or CCBs not supported
2 DUP + 1 HCU and Air
A CCB output includes a TxBPF; a CCB extension does not.
5-14 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Transmit configurations
{28075} If the ITS feature is unrestricted and enabled, EGPRS supports single density and
double density CTU2 configuration. Otherwise, only single density CTU2 supports EGPRS.
The Tx configuration options apply only for the Horizonmacro and Horizon II macro cases as 1
carrier per CTU2 Radio.
Transmit planning actions
Determine the transmit equipment required.
68P02900W21-R 5-15
28 Feb 2006 GMR-01
EGPRS enabled CTU2 configuration Chapter 5: BTS planning steps and rules
EGPRS enabled CTU2 configuration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
EGPRS enabled CTU2 configuration limitations
EGPRS is a restricted feature. This configuration is only supported when this feature is unrestricted.{28075}
If ITS feature is unrestricted and enabled, the EGPRS can be configured on double density CTU2. The CTU2
radio is supported in the Horizon II macro and Horizonmacro BTS cabinet platforms. Also, the CTU2 radio is
supported in the M-Cell6 and M-Cell2 cabinet platforms when the CTU2 Adapter is used.
EGPRS general configuration
The EGPRS feature requires additional backhaul to provision EGPRS carriers. The additional backhaul will
be either 7 DS0s to implement EGPRS on a BCCH carrier or 8 DS0s to implement EGPRS on a non-BCCH
carrier, {23769} if VersaTRAU feature is restricted. If VersaTRAU feature is unrestricted, the backhaul for an
EGPRS carrier can be configured using the rtf_ds0_count parameter.
{23769} If VersaTRAU is restricted, the max EGPRS carriers that can be equipped for a 3 sector site is 21.
The total number of E1s available at a Horizonmacro or Horizon II macro site is 6. Some number of these
DS0s are needed for RSLs to the BSC (up to 6 with MCUF, and H2 site controller). The rest are available for
TRAU. An entire RTF must be configured to the same physical E1. This allows configuration of 3 non-BCCH
EGPRS RTFs on each E1 (using 24 DS0s) for a total of 18 EGPRS non-BCCH carriers. The remaining 7 DS0
can be used for BCCH RTFs and RSLs. Therefore, the worst case configuration when every possible timeslot
is configured as an EGPRS carrier in a three sector site is 21 carriers:
• 18 (3x6) non-BCCH (with 8 air timeslots on each RTF) carriers at a site.
• 3 BCCH carriers (with 7 air timeslots on each RTF).
• The remaining DS0s are available for use as RSLs.

{23769} If VersaTRAU is unrestricted, the max EGPRS carriers for the same configuration can be up to 24. If
the recommended non-aggressive backhaul of 5 DS0s per EGPRS carrier is used, 6 EGPRS carriers (using
30 DS0s) can be configured on each E1. This would require 4 E1s for the 24 EGPRS carriers leaving the
remaining 4 DS0s available for RSLs.
Baseband hopping (BBH)
There are several restrictions for an EGPRS enabled CTU2.

Baseband hopping (BBH) is only allowed with other EGPRS enabled CTU2 radios in the same hopping
group. When the ITS feature is unrestricted and enabled,Table 5-2 and Table 5-3 show the restrictions for the
Horizon II macro Site Controller and the Horizonmacro Site Controller respectively.
5-16 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning EGPRS enabled CTU2 configuration
Table 5-2 indicates that BBH is not permitted with EDGE enabled CTU2s when Horizonmacro is
the Master Site Controller. BBH is only permitted with EDGE enabled CTU2s when they are
controlled by the Horizon II macro Site controller as Master.
Table 5-2 BBH capability for Horizon II macro Site Controller
CTU2 (SD
CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM)
EGPRS)
CTU2 (SD 4 6 6 6
EGPRS)
CTU2 (DD GSM) 6 4 4 4
CTU2 (SD GSM) 6 4 4 4
CTU (SD GSM) 6 4 4 4
Table 5-3 BBH capability for Horizonmacro Site Controller
CTU2 (SD
CTU2 (DD GSM) CTU2 (SD GSM) CTU (SD GSM)
EGPRS)
CTU2 (SD 6 6 6 6
EGPRS)
CTU2 (DD GSM) 6 6 6 6
CTU2 (SD GSM) 6 6 4 4
CTU (SD GSM) 6 6 4 4
Broadcast control channel (BCCH) RTF configuration
The Broadcast control channel (BCCH) Radio Transceiver Function (RTF) should be configured as a 64K
carrier. For EGPRS, the only radio that supports 64K is the CTU2. It is not mandatory that the CTU2 used
for the BCCH RTF be EGPRS enabled.
68P02900W21-R 5-17
28 Feb 2006 GMR-01
Antenna configurations Chapter 5: BTS planning steps and rules
Antenna configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following factors should be considered when planning the antenna configuration:
• Omni, one sector, two sector, three sector (either 120° or 60°), or six sector (two cabinets
are needed).
• Share existing antenna(s) or new/separate antenna(s).
• Diversity considerations.
• Antenna type:
◦ Gain.
◦ Size.
◦ Bandwidth.
◦ Appearance.
◦ Mounting.
Antenna planning actions
Determine the antenna configuration.
5-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Carrier equipment (transceiver unit)
Carrier equipment (transceiver unit)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The transceiver unit for Horizon II macro and Horizon II mini is the CTU2. This can be configured to operate
in single density (single carrier) or double density (2 carrier) mode. The CTU2 can also be used as a CTU
replacement (subject to restrictions) in a Horizonmacro cabinet, but NOT an outdoor cabinet. Note that
CCBs are not supported by the CTU2.
The transceiver unit for Horizonmacro is a CTU. This will eventually be phased out and replaced by the
CTU2, as used in the Horizon II macro.
For rules relating to replacement of a CTU with a CTU2, contact your Motorola Local Office.
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:
• The TCU-B only supports GSM/EGSM900.
• The TCU-B cannot be used as a SCU (in pre M-Cell equipment).
References to TCU in the text include TCU-B, except where stated otherwise.
AMR and GSM half rate are supported on all transceiver equipment described here, except for the DTRX.
Restrictions when using CTU2s in Horizonmacro BTSs
The following restrictions apply when CTU2s are used to replace CTUs in Horizonmacro BTSs:
• CTU2s cannot be used in Horizonmacro outdoor BTSs.
• CTU2s cannot be used in Horizonmacro indoor BTSs that are powered from 110 V ac.
• BBH is only supported in single density mode when CTU2s are used in Horizonmacro
indoor BTSs.
• CCBs are not supported when CTU2s are used in Horizonmacro indoor BTSs.
• RF power output from the CTU2s is reduced.
• Fully populated Horizonmacro cabinets that contain two or more CTU2s require three PSUs.
PSU redundancy will not be available in these configurations.
68P02900W21-R 5-19
28 Feb 2006 GMR-01
Carrier equipment (transceiver unit) Chapter 5: BTS planning steps and rules
CTU/CTU2 power supply considerations
Under normal circumstances, the Horizonmacro only requires two power supply modules (PSMs) to power
six CTUs and the third PSM slot can be used either for a redundant PSM or for an optional hold-up battery
module (in ac-powered systems).
These power supply requirements change if CTU2s are used in the Horizonmacro cabinet. Depending on the
number of CTU2s used, it may be necessary to install a third PSM, thus losing the internal battery backup
facility. In such cases where battery backup is required, an external battery backup unit (BBS) will need to be
added instead. Also, in cases where a third (redundant) PSM is already installed, redundancy will be lost.
Table 5-4 lists the CTU/CTU2 combinations and power supply requirements in Horizonmacro and Horizon II
macro cabinets. This table applied to both GPRS and the EGPRS feature overlay.
Table 5-4 does not include Horizon II mini, as Horizon II mini requires only 1 power supply
as min/max.
5-20 68P02900W21-R
GMR-01 28 Feb 2006
Table 5-4 CTU/CTU2 power requirements
Horizonmacro Horizon II macro

No. of CTUs No. of CTU2s No. of power No. of CTU2s No. of power
supplies supplies
required required
6 0 2 6 3
5 1 3 5 3
4 1 2 4 3
3 1 2 3 2
2 1 2 2 2
1 1 1 1 1
0 1 1
4 2 3
3 2 2
2 2 2
1 2 2
0 2 2
3 3 3
2 3 3
1 3 2
0 3 2
2 4 3
1 4 3
0 4 2
1 5 3
0 5 3
0 6 3
The Horizon II macro always has a spare fourth power supply slot available for either a redundant
power supply or for a hold-up battery module (in ac-powered cabinets).
Table 5-5 lists the CTU/CTU2 combinations and power supply requirements in M-Cell6 and M-Cell2
cabinets. This table is independent of the CTU2 operating mode or feature overlay. This table assumes that
slots that do not use CTU2 Adapters will be populated with TCUs.
68P02900W21-R 5-21
28 Feb 2006 GMR-01
Carrier equipment (transceiver unit) Chapter 5: BTS planning steps and rules
Table 5-5 CTU/CTU2 power requirements for M-Cell cabinets
No. of CTU2 Adapters No. of power supplies required

M-Cell6 AC Indoor:
1–6 5
M-Cell6 AC Outdoor:
1–4 3
5–6 4
M-Cell6 DC Indoor:
1–4 2
5–6 2 (add one more for redundancy)
M-Cell2 AC Indoor and M-Cell2 AC Outdoor:
1 1
2 1 (add 1 more for redundancy)
The following factors should be considered when planning carrier equipment:

• The number of carriers should be based on traffic considerations.
• Plan for future growth.
• Allowance must be made for BCCH and SDCCH control channels.

Information about how to determine the number of control channels required is in the "Control
channel calculations" on page 3-125 section in Chapter 3, "BSS cell planning,".
• {28075} Previously, one transceiver unit was required to provide each RF carrier. However,
with the introduction of the CTU2 this is no longer true. The CTU2 is capable of single and
double density operation for GSM/GPRS; and one CTU2 can support one RF carrier or be
configured to support two RF carriers. The exception to this is for EGPRS. An EGPRS
enabled CTU2 can be configured in single density mode (that is, one CTU2 per carrier). If the
ITS feature is unrestricted and enabled, an EGPRS enabled CTU2 can also be configured
in double density mode.
• Include redundancy requirements. Redundancy can be achieved by installing excess capacity

in the form of additional transceiver units.
• Plan the number of power supplies required in accordance with the number of transceivers
required.
5-22 68P02900W21-R
GMR-01 28 Feb 2006
Transceiver planning actions
Determine the number of transceivers required.

Determine the number of power supplies required to power the transceivers.
68P02900W21-R 5-23
28 Feb 2006 GMR-01
Micro base control unit (microBCU) Chapter 5: BTS planning steps and rules
Micro base control unit (microBCU)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The microBCU (or µBCU) is the macro/microcell implementation of a BTS site controller.
The following factors should be considered when planning the µBCU complement:
• Horizon II macro/Horizon II mini
The Horizon II macro/Horizon II mini is similar to the Horizonmacro in that it has a built-in
digital module shelf. However, unlike Horizonmacro, the NIU is integrated on the HIISC (the
equivalent of the Horizonmacro MCUF) and external FMUXs and BPSMs are not required.
The digital module shelf can be equipped for redundancy and/or additional E1/T1 link capacity
with the addition of a redundant HIISC.
• Horizonmacro
Each Horizonmacro cabinet has a built-in digital module shelf. This provides the
Horizonmacro equivalent of M-Cell6 microBCU cage functionality.
The digital module shelf can be equipped for redundancy and/or additional E1/T1 link capacity
with the addition of a redundant MCUF, NIU, FMUX and BPSM.
• M-Cell6
Each M-Cell6 cabinet requires one microBCU cage.
Two microBCU cages can be equipped for redundancy and/or additional E1/T1 link capacity
with the addition of a redundant MCU, NIU and FOX/FMUX.
• M-Cell2
The first M-Cell2 cabinet requires one microBCU2 cage.
Two microBCU2 cages can be equipped for redundancy and/or additional E1/T1 link capacity.
Additional cabinets do not require microBCU2 cages.
MicroBCU planning actions
For M-Cell equipment, determine the number of microBCUs required.
5-24 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Network interface unit (NIU) and site connection
Network interface unit (NIU) and site connection

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The NIU provides the interface for the Horizon II macro, Horizonmacro or M-Cell2/6 BTS to the terrestrial
network.
M-Cellcity and M-Cellcity+ are fitted with a single NIU-m only.

The equivalent modules in Horizoncompact2 and Horizonmicro2 are RHINO/DINO.
Depending on the BTS equipment installed, the following factors should be considered when planning
the NIU complement:
Horizon II macro/Horizon II mini

• Both Horizon II macro and Horizon II mini use the Horizon II site controller (HIISC).
• NIU functionality is integrated into the HIISC. From a functional standpoint, the Integrated
NIU functions the same as the standalone NIU with the exception that support for 4 RSL links
per E1 and a maximum of 6 E1s is now supported in Horizon II macro and Horizon II mini.
• A minimum of one HIISC (with integrated NIU functionality) is required in the master cabinet
for each Horizon II macro BTS site. Horizon II mini does not support hardware redundancy.
• For a Horizon II macro master cabinet, redundancy for the NIU functionality depends on a
redundant HIISC. If a redundant HIISC is installed, a redundant site expansion board is also
required. Slave Horizon II macro cabinets connected to the master cabinet also require
redundant site expansion boards and redundant XMUXs.
68P02900W21-R 5-25
28 Feb 2006 GMR-01
Network interface unit (NIU) and site connection Chapter 5: BTS planning steps and rules
For Horizon II macro only: The integrated NIU within the redundant HIISC has
connectivity to all the E1 links for that site through the use of relays and switches.
The redundant HIISC can be switched automatically to become the main HIISC,
taking over all duties of the main HIISC (including controlling all E1 links at that
site) through a BTS reset.
Horizonmacro and M-Cell

• The first NIU in a digital module shelf (Horizonmacro) or microBCU cage (M-Cell6) can
interface two E1/T1 links.
• The second NIU in a digital module shelf or microBCU cage can interface one E1/T1 link.
• Each E1/T1 link provides 31 (E1) or 24 (T1) usable 64 kbit/s links.
• A minimum of one NIU is required for each BTS site.
• One NIU can support two MCUFs (Horizonmacro) or two MCUs (M-Cell6).
• The NIU feeds the active MCUF/MCU.
• To calculate the number of 64 kbit/s links required, view the site as consisting of its own
equipment, and that of other sites which are connected to it by the drop and insert (daisy
chain) method.
◦ Two 64 kbit/s links are required for each active 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.
• Redundancy for the NIU module depends on the number of redundant E1/T1 links running to
the site.
• Plan for a maximum of two NIUs per digital module shelf or microBCU cage (three E1
or T1 links).
• Plan for a maximum of one NIU per microBCU2 cage for M-Cell2 cabinets (two E1 or T1
links).
The minimum number of NIUs and microBCU cages required for a given number of E1/T1 links to a single
M-Cell cabinet is shown in Table 5-6.
5-26 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Network interface unit (NIU) and site connection
Table 5-6 Site connection requirements for M-Cell2 and M-Cell6
Number of E1/T1 Minimum number of Number of µBCU Notes

links NIU required cages 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
Only one digital module shelf is installed in the Horizon II macro and 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.
68P02900W21-R 5-27
28 Feb 2006 GMR-01
BTS main control unit Chapter 5: BTS planning steps and rules
BTS main control unit

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The main control unit provides the main site control functions for a BTS. The main control unit used depends
on the BTS equipment:
• Horizon II macro and Horizon II mini both use a Horizon II macro site controller (HIISC)
with triple XMUX.
• Horizonmacro uses a main control unit with dual FMUX (MCUF).
• M-Cell6 and M-Cell2 use a main control unit (MCU).
The HIISC can only be used in Horizon II macro. The MCUF is backwards
compatible with the MCU and can be used in M-Cell6 and M-Cell2 BTSs.
Horizon II mini is a new small macro BTS and the HIISC used within can support a
max of 24 RF carriers across the sites. The HIISC used in Horizon II macro can
also support 24 RF carriers.
5-28 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BTS main control unit
Horizon II macro
The following factors should be considered when planning the HIISC complement for a Horizon II macro site:
• Only the master Horizon II macro cabinet requires a HIISC.
• For redundancy, add a second HIISC in the digital module shelf of the master cabinet. This also
provides redundancy for the NIU and XMUX as well, since they are integrated in the HIISC.
This redundancy configuration also requires a redundant site expansion board in all
Horizon II macro cabinets at sites where more than one cabinet is installed.
Horizon II mini
• Only the master Horizon II mini cabinet requires a HIISC. The HIISC used can support
a max of 24 RF carriers across the sites.
• There is no accommodation for redundancy in this BTS.
Horizonmacro
The following factors should be considered when planning the MCUF complement for a Horizonmacro site:
• Only the master cabinet requires a MCUF.
• An optional 20 Mbyte PCMCIA memory card may be installed for non-volatile code storage.
• For redundancy, add a second MCUF in the digital module shelf of the master cabinet.
M-Cell6 and M-Cell2

The following factors should be considered when planning the MCU complement for a M-Cell6 or M-Cell2
site:
• Only the master cabinet requires a MCU.
• An optional 20 Mbyte PCMCIA memory card may be installed for non-volatile code storage.
• For redundancy, add a second mBCU cage and MCU in the master cabinet.
68P02900W21-R 5-29
28 Feb 2006 GMR-01
BTS main control unit Chapter 5: BTS planning steps and rules
Planning considerations - HorizonII macro/HorizonII mini as

expansion cabinet
This information describes the factors that need to be taken into account if Horizon II macro cabinets are used
to expand existing Horizonmacro or M-Cell6 sites.
Horizon II macro slave BTS planning considerations

• A XMUX is required instead of a HIISC in the slave cabinet.
• A site expansion board is required.
• If redundancy is required, a redundant XMUX and redundant site expansion board must
be installed.
Horizon II mini slave BTS planning considerations

• A XMUX is required instead of a HIISC in the slave cabinet.
• A site expansion board is required.
• Horizon II mini does not support hardware redundancy.
Horizonmacro master BTS planning considerations

• Only the master cabinet requires an MCUF.
• A 20 Mbyte PCMCIA memory card running CSFP must be installed in the MCUF to
accommodate the use of the CTU2 transceiver from a code storage standpoint. If the site is
equipped with a redundant MCUF, the PCMCIA is also mandatory for the redundant MCUF.
5-30 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BTS main control unit
M-Cell6 master BTS planning considerations
Due to expansion limitations, M-Cell2 BTSs cannot be used with Horizon II macro (or
Horizonmacro) cabinets.
• Only the master cabinet requires an MCU.
• A 20 Mbyte PCMCIA memory card running CSFP must be installed in the MCU to
accommodate the use of the CTU2 transceiver from a code storage standpoint. If the site is
equipped with a redundant MCU, the PCMCIA is also mandatory for the redundant MCU.
• The master cabinet must have a FMUX installed to communicate with the Horizon II
macro BTS.
Planning actions
Horizon II macro/Horizon II mini

Determine the number of HIISCs required.
Horizonmacro
Determine the number and configuration of MCUFs required.
M-Cell6 and M-Cell2

Determine the number and configuration of MCUs required.
68P02900W21-R 5-31
28 Feb 2006 GMR-01
Cabinet interconnection Chapter 5: BTS planning steps and rules
Cabinet interconnection
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Horizon II macro
The XMUX multiplexes and demultiplexes full duplex transceiver links between a site expansion board and
up to six CTU2s in a Horizon II macro expansion cabinet.
Horizon II mini
The XMUX multiplexes and demultiplexes full duplex transceiver links between a site expansion board and
2 CTU2s in a Horizon II mini expansion cabinet.
Horizon II micro
Horizon II micro will support up to three cabinets. It can be connected to either another Horizon II micro or
any legacy macro or mini product via an expansion board similar to the Horizon II macro – Site I/O.
Horizonmacro
The FMUX multiplexes and demultiplexes full duplex transceiver links between a 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 or CTU2 Adapters onto a
single fibre optic connection operating at the rate of 16.384 Mbit/s.
5-32 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Cabinet interconnection
Horizon II macro
The following factors should be considered when planning the XMUX complement:
• A XMUX is required in each Horizon II macro expansion cabinet.
• The master Horizon II macro cabinet does not require a XMUX as a triple XMUX is
integrated on the HIISC.
• There is no support for hardware redundancy in Horizon II mini.
• A site expansion board (unique to Horizon II macro) is required for the master and every
expansion cabinet in the Horizon II macro BTS site when expansion is required (see Table 5-7).
• Redundancy requires duplication of the HIISC in the master cabinet and all XMUXs and
site expansion boards.
Table 5-7 Horizon II macro XMUX expansion requirements
Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) None
2 1 site expansion 1 XMUX +
board only 1 site expansion
board
3 1 site expansion 1 XMUX + 1 XMUX +
board only 1 site expansion 1 site expansion
board board
4 1 site expansion 1 XMUX + 1 XMUX + 1 XMUX +
board only 1 site expansion 1 site expansion 1 site expansion
board board board
Horizon II mini
The following factors should be considered when planning the XMUX complement:
• A XMUX is required in each Horizon II mini expansion cabinet.
• The master Horizon II mini cabinet does not require a XMUX as a triple XMUX is integrated
on the HIISC.
• A site expansion board (unique to Horizon II macro and Horizon II mini) is required for the
master and every expansion cabinet in the Horizon II macro BTS site when expansion is
required (see Table 5-8 through Table 5-10).
68P02900W21-R 5-33
28 Feb 2006 GMR-01
Table 5-8 Horizon II mini only network XMUX expansion requirements
Cabinet Master Expansion 1 Expansion 2 Expansion 3

1 (master) None
board
board board
board board board
Table 5-9 Horizon II macro as master - Horizon II mini as expansion XMUX requirements
Cabinet - Master - Expansion Expansion Expansion

Horizon II Horizon II 1 Horizon II 2 Horizon II 3 Horizon II
macro macro mini mini mini
1 (master) None
board
board board
board board board
Table 5-10 M-Cell6 as master - Horizon II mini as expansion XMUX requirements
Expansion Expansion Expansion

Cabinet - Master -
1 Horizon II 2 Horizon II 3 Horizon II
M-Cell6 M-Cell6
mini mini mini
1 (master) None
2 None 1 XMUX +
1 site expansion
board
3 None 1 XMUX + 1 XMUX +
1 site expansion 1 site expansion
board board
4 1 FMUX 1 XMUX + 1 XMUX + 1 XMUX +
1 site expansion 1 site expansion 1 site expansion
board board board
5-34 68P02900W21-R
GMR-01 28 Feb 2006
The Horizon II mini is a micro family BTS and the HIISC used has RF limitations
of 24 carriers per site in a Horizon II mini network.
Horizonmacro
The following factors should be considered when planning the FMUX complement:
• An FMUX is not required in the master cabinet for two or three cabinet configurations
(see Table 5-11).
• A fourth Horizonmacro cabinet requires one FMUX plus one FMUX in the master cabinet
(see Table 5-11).
• Redundancy requires duplication of an FMUX and associated MCUF.
Table 5-11 Horizonmacro FMUX expansion requirements
Cabinet Master Extender 1 Extender 2 Extender 3

1 (master) None
2 None 1
3 None 1 1
4 1 1 1 1
M-Cell6 and M-Cell2

The following factors should be considered when planning the FOX/FMUX complement:
• A FOX board is required for more than two TCUs.
• Each additional M-Cell6 cabinet requires a minimum of one FOX and FMUX plus one
FMUX in the first cabinet.
• Redundancy requires duplication of all FOX and FMUX boards and associated MCU and
microBCU cages.
68P02900W21-R 5-35
28 Feb 2006 GMR-01
Planning considerations - Horizon II macro as master cabinet
Due to expansion limitations, M-Cell2 BTSs cannot be used with Horizon II macro cabinets.
The following factors should be considered when planning to use a Horizon II macro as a master cabinet
with Horizonmacro or M-Cell6 expansion cabinets:
• A site expansion board is required in the Horizon II macro master cabinet.
• A XMUX is not required in the Horizon II macro master cabinet.
• Each Horizonmacro or M-Cell6 slave cabinet must contain a FMUX (replaces the
MCUF/MCU).
• For redundancy, the master Horizon II macro cabinet requires an additional HIISC and site
expansion board; each Horizonmacro slave cabinet requires an additional FMUX, and each
M-Cell6 slave cabinet requires an additional FMUX and FOX.
Planning considerations - Horizon II mini as master cabinet
Horizon II mini as a Master cabinet and Macro family BTS as expansions are considered a
non-Motorola approved configuration.
Horizon II mini outdoor variant requires a -230 V dc supply.
5-36 68P02900W21-R
GMR-01 28 Feb 2006
XMUX/FMUX/FOX planning actions
Horizon II macro
Determine the number of XMUXs required (applies to expansion cabinets only).
Horizonmacro
Determine the number of FMUXs required.
M-Cell6 and M-Cell2

Determine the number of FOX/FMUXs required.
M-Cell2 BTSs are not supported as an expansion to Horizon II macro or Horizonmacro cabinets.
Site expansion board planning actions (Horizon II macro only)
If more than one cabinet is to be used at a site, determine the number of site expansion boards required.
68P02900W21-R 5-37
28 Feb 2006 GMR-01
Battery back-up provisioning Chapter 5: BTS planning steps and rules
Battery back-up provisioning

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The Horizon II outdoor enclosure can be provisioned to have battery back-up in case of power failure
at the site.
The following factors will influence the planning for battery back-up for a Horizon II outdoor enclosure.
• Two optional internal batteries to provide a minimum of 5 mins back-up.
• An optional external battery cabinet has dimensions 1555x799x760mm and weight 110 kg
when empty, 590 kg with 16 SBS C11 batteries included. This cabinet can house up to 16
Hawker SBS C11 battery cells (i.e. 8 strings) or equivalent. Two string sets can provide a
battery back-up for about one hour, a full cabinet can provide battery back-up for about
four hours.
• The intermediate battery back-up solution consists of a frame fixed to the ground housing the
batteries and an oversized shroud fitted over it fixed onto the main cabinet.
◦ Size: 350mm wide x 687mm deep x 1441mm high.
◦ Weight: without batteries including metalwork and interconnect cables, the weight is
40kg. With batteries, the weight is 160kg.
The frame can house up to 2 strings of SBS C11 batteries (each string consisting of 2 batteries)
which provides 1 hour of back-up.
The back-up times for the internal, intermediate and external battery backup are for a fully loaded
system in a worst case scenario. Longer back-up times are achieved under a typical load.
There is an on-site visual display of outdoor battery voltages.
5-38 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning External power requirements
External 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:
• Horizon II macro
Horizon II macro power requirements are determined by the BTS cabinet type:
Indoor: +27 V dc, -48 V dc, 110-230 V ac
Outdoor: 200-240 V ac single/3-phase only.
• Horizon II mini
Horizon II mini power requirements are determined by the BTS cabinet type:
Indoor: +27 V dc, -48 V dc, 110-230 V ac
Outdoor: 230 V ac only.
• 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.
Only -48 V dc indoor cabinets can be installed in the 12 carrier outdoor.
• Horizonmicro2 and Horizoncompact2

The Horizonmicro2 and Horizoncompact2 enclosures operate from a 88 to 265 V ac power
source.
• Horizon II micro
The Horizon II micro enclosure operates from a 88 to 300 V ac power source.
68P02900W21-R 5-39
28 Feb 2006 GMR-01
External power requirements Chapter 5: BTS planning steps and rules
• 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.
• 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.
• M-Cellcityand 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.
5-40 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Network expansion using macro/microcell BTSs
Network expansion using macro/microcell BTSs

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
An existing network with previous generations of Motorola equipment such as BTS4, BTS5, BTS6,
TopCell, or ExCell may be expanded using macro/microcell. The "Network topology" on page 2-6 can
be any of those specified in Chapter 2, "Transmission systems," of this manual. A macro/microcell BTS
may occupy any position in a network.
Expansion considerations
The following factors should be considered when expanding an existing network using macro/microcell BTS
cabinets:
• A macro/microcell BTS cannot share a cell with a BTS4, BTS5, BTS6, TopCell, or ExCell.
• The rules governing the number of NIUs required at the macro/microcell BTS are given in
Table 5-6 of this chapter.
• The rules governing the number of MSIs required at the BSC are given in the "Multiple serial
interface (MSI, MSI-2)" on page 6-77 section of Chapter 6, "BSC planning steps and rules,".
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.
68P02900W21-R 5-41
28 Feb 2006 GMR-01
Network expansion using macro/microcell BTSs Chapter 5: BTS planning steps and rules
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.
5-42 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Line interface modules (HIM-75, HIM-120)
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:
• To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3 V
(peak pulse) line use a HIM-120.
• To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line
use a HIM-75.
• Each HIM-75/HIM-120 can interface four E1/T1 links to specific slots on one shelf.
HIM-75/HIM-120 planning actions

• Determine the number to be deployed.
• Determine the number of HIM-75s or HIM-120s required.
68P02900W21-R 5-43
28 Feb 2006 GMR-01
DRI/Combiner operability components Chapter 5: BTS planning steps and rules
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.
DRI and combiner relationship
Figure 5-1 illustrates the DRI and combiner relationship.
Figure 5-1 DRI and combiner relationship
COMB 0
First controlling Second controlling

DRI DRI
DRI 0 0 DRI 0 1
5-44 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
6
BSC planning steps and rules
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02900W21-R 6-1
28 Feb 2006 GMR-01
DRI/Combiner operability components Chapter 6: BSC planning steps and rules
The planning steps and rules for the BSC are provided here. The planning steps and rules for the BTS are in
Chapter 5, "BTS planning steps and rules," and remote transcoder (RXCDR) are in Chapter 7, "RXCDR
planning steps and rules,". The topics described here are as follows:
• "BSC planning overview" on page 6-3
• "Capacity calculations" on page 6-6
• "BSC system capacity" on page 6-7
• "Determining the required BSS signalling link capacities" on page 6-11
• "Determining the number of RSLs required" on page 6-22
• "Determining the number of MTLs required" on page 6-42
• "Determining the number of LMTLs required" on page 6-49
• "Determining the number of XBLs required" on page 6-52
• "Determining the number of GSLs required" on page 6-55
• "Generic processor (GPROC)" on page 6-61
• "Transcoding" on page 6-69
• "Multiple serial interface (MSI, MSI-2)" on page 6-77
• "Kiloport switch (KSW) and double kiloport switch (DSW2)" on page 6-80
• "BSU shelves" on page 6-83
• "Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)" on page
6-87
• "Generic clock (GCLK)" on page 6-91
• "Clock extender (CLKX)" on page 6-92
• "Local area network extender (LANX)" on page 6-94
• "Parallel interface extender (PIX)" on page 6-95
• "Line interface boards (BIB, T43)" on page 6-96
• "Digital shelf power supply" on page 6-98
• "Non volatile memory (NVM) board" on page 6-99
• "Verify the number of BSU shelves and BSSC cabinets" on page 6-100
6-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSC planning overview
BSC planning overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
To plan the equipage of a BSC certain information must be known. The major items include:
• The number of BTS sites to be controlled.
• The number of RF carriers (RTF) at each BTS site.
• The number of TCHs and PDTCHs at each site.
• The total number of AMR half rate or {22064} GSM half rate capable TCHs at each site.
• The total number of TCHs and PDTCHs under the BSC.
• The number of cells controlled from each BTS site should not exceed the maximum per
BSC detailed in Table 6-1.
• The physical interconnection of the BTS sites to the BSC.
• The location of the XCDR function.
• The path for the OML links to the OMC-R.
• The use of E1 or T1 links.
• The use of balanced or unbalanced E1.
• The traffic load to be handled (also take future growth into consideration).
• The number of MSC to BSC trunks.
• The LCS architecture
Mixing of equipment types
When mixing BSU and RXU shelves at a BSC the planning rules for each type of shelf must be taken
into account. This will require using the information contained in this chapter (for the BSC) and Chapter
7 (for the RXCDR), as the RXU shelf is primarily used in the RXCDR. This applies to both the legacy
RXU shelf and the new RXU3 shelf.
This is also true for the cabinets. The additional connectivity provided by the new BSSC3 may be required in
the BSC when the RXU3 shelf or shelves are used.
68P02900W21-R 6-3
28 Feb 2006 GMR-01
BSC planning overview Chapter 6: BSC planning steps and rules
Planning a BSC involves the following steps, which are all described in detail in this chapter:
1. Plan the number of RSL links between the BSC and BTS site(s) Refer to the section
"Determining the number of RSLs required" on page 6-22.
2. Plan the number of E1 or T1 links between the BSC and BTS site(s). Refer to the section
"BSC to BTS E1 interconnect planning actions" on page 6-35 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" on page 6-42.
4. Plan the number of XBL links required between the BSC and AXCDR. Refer to the section
"Determining the number of XBLs required" on page 6-52.
5. Plan the number of GSL links required between the BSC and the PCU. Refer to "Determining
the number of GSLs required" on page 6-55.
6. Plan the number of GPROCs required. Refer to the section "Generic processor (GPROC)"
on page 6-61.
7. Plan the number of XCDR/GDP/EGDP/GDP2s required. Refer to the section "Transcoding"

on page 6-69.
8. Plan the number of LMTL links required between the BSC and the SMLC if LCS is enabled in
the BSS and if BSS-based LCS architecture is supported. Refer to the section "Determining
the number of LMTLs required" on page 6-49. Ignore this step if the BSS only supports
NSS-based LCS architecture.
9. Plan the number of E1 links between the BSC and SMLC if LCS is enabled in the BSS and if
BSS-based LCS architecture is supported. Refer to the section "Determining the number
of LMTLs required" on page 6-49. Ignore this step if the BSS only supports NSS-based
LCS architecture.
10. Plan the number of MSI/MSI-2s required. Refer to the section "Multiple serial interface
(MSI, MSI-2)" on page 6-77.
11. Plan the number of KSWs/DSW2s and timeslots required. Refer to the section "Kiloport
switch (KSW) and double kiloport switch (DSW2)" on page 6-80.
12. Plan the number of BSU shelves. Refer to the section "BSU shelves" on page 6-83.
13. Plan the number of KSWXs/DSWXs required. Refer to the section "Kiloport switch extender
(KSWX) and double kiloport switch extender (DSWX)" on page 6-87.
14. Plan the number of GCLKs required. Refer to the section "Generic clock (GCLK)" on
page 6-91.
15. Plan the number of CLKXs required. Refer to the section "Clock extender (CLKX)" on
page 6-92.
16. Plan the number of LANXs required. Refer to the section "Local area network extender
(LANX)" on page 6-94.
6-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSC planning overview
17. Plan the number of PIXs required. Refer to the section "Parallel interface extender
(PIX)" on page 6-95.
18. Plan the number of BIB or T43s required. Refer to the section "Line interface boards
(BIB, T43)" on page 6-96.
19. Plan the power requirements. Refer to the section "Digital shelf power supply" on page 6-98.
20. Decide whether an NVM board is required. Refer to the section "Non volatile memory
(NVM) board" on page 6-99.
21. Verify the planning process. Refer to the section "Verify the number of BSU shelves and
BSSC cabinets" on page 6-100.
68P02900W21-R 6-5
28 Feb 2006 GMR-01
Capacity calculations Chapter 6: BSC planning steps and rules
Capacity calculations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The throughput capacities of the BSC processing elements (for example, GPROC) 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 process 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:
• A summary of BSC maximum capacities.
• The required BSS signalling link capacities.
• Traffic models.
• BSC GPROC functions and types.
• The number of GPROCs required.
Remote transcoding
When the transcoding function resides outside of the BSC cabinet, in the RXCDR, it is possible to have
multiple RXCDRs connected to a single BSC, and vice-versa. This is especially useful for two reasons:
1. In certain configurations the RXCDR call (CIC) capacity may be greater than that of a BSC.
2. A failure of a RXCDR or communication line will not result in a complete failure of the
BSC to handle calls.
Each BSC may connect to up to 10 RXCDRs, and vice-versa. The level of connectivity may be constrained by
the number of XBLs that can be supported, there is a limit of 20 at each BSC and RXCDR (see Determining
the number of XBLs required later in this chapter).
The level of connectivity is determined by the operator, Excess RXCDR capacity should not be wasted, nor
should larger BSCs be connected only to one RXCDR. One guideline is to have each BSC connect to four
RXCDRs. System size, capacity, and cost are major influences on the chosen configuration.
With the introduction of advanced transcoding capabilities such as AMR, care should be taken when
distributing the functions across multiple RXCDRs. For optimum redundancy each RXCDR should have an
appropriate mix of transcoder capability. For example, in a four BSC, four RXCDR configuration where all
are interconnected, and there are a limited number of transcoder cards capable of AMR (for example GDP2s),
optimally the cards would be distributed equally amongst the RXCDRs.
6-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSC system capacity
BSC system capacity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
System capacity summary
Table 6-1 provides a summary of BSC maximum capacities.
Table 6-1 BSC maximum capacities
Item GSR6 GSR7 GSR8

BTS sites 100 100 100
BTSs (cells) 250 250 250
Active RF carriers 384a 384 a,b 384 a,b
DRIs 512 512 512

RSLs 250 250 250
PCUs 1 3 3
GSLs 12 180 c 180 c
MMSs 128 128 128

PATHs 250 250 250
DHPs 232 232 232
LCFs 25 25 25
Trunks (see note below) 2400a 2400 a,b 2400 a,b
C7 links to MSC 16 16 16
C7 links to SMLC 16 16 16
T1 or E1 links 102 102 102
Maximum busy hour call 90,000 90,000 90,000
attempts
68P02900W21-R 6-7
28 Feb 2006 GMR-01
BSC system capacity Chapter 6: BSC planning steps and rules
Notes
a. Can be increased to 512 carriers and 3200 trunks if the optional enhanced BSC capacity feature is
enabled.
b. For GSR8, it is mandatory to deploy GPROC3s in active and/or standby BSP slots in the BSC in any
potential BSP slots on a site, i.e. slot 20 and 24 in shelf 0, slot 20 in shelf 1.
c. 60 per PCU.
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.
Planning is a multi-variant problem. When planning a BSC, any limit given in Table 6-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.
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.
Prior to GSR7, the move to a scaleable BSC is enabled through the migration of the processing boards within
the BSC to use the GPROC2 throughout. Now, GPROC2s can be replaced by the new GPROC3s at board
level in any slot, thus preserving the scaleable BSC architecture. 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. {25779} For GSR8, it is mandatory to deploy GPROC3s in active and/or standby
BSP slots in the BSC in any potential BSP slots on a site (that is, slot 20 and 24 in shelf 0, slot 20 in shelf 1).
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 supported 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
GPROC. The maximum capacity is increased as shown in Table 6-1.
This increased capacity is achieved through the deployment of GPROC2s or GPROC3s for each function at
the BSC, including base station processor (BSP) and link control function (LCF).
6-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSC system capacity
The GPROC3 is a high performance direct replacement for the GPROC2 and the original GPROC
(GPROC1).
{25779} For GSR8, GPROC3s are required in the BSP slots.
Enhanced BSC capacity option
This feature was introduced 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 6-1). If the feature is unrestricted, the
BSC maximum capacity is increased to 512 RF carriers and 3200 trunks.
Hardware upgrades are required by the BSS to support the optional Enhanced BSC capacity. Specifically,
BTP processors at InCell BTSs must be replaced with GPROC2s.
LCS option
This feature is a restrictable option. If the feature is restricted, no location service capability is provided. If
the feature is unrestricted, the BSS supports the network sub-system (NSS) based serving mobile location
centre (SMLC) architecture or the BSS-based SMLC architecture, and the BSS supports new LCS signalling
for cell ID +TA positioning method:
• New LCS signalling messages on the A-interface or Lb interface.
• 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 architectures respectively in the following sections.
68P02900W21-R 6-9
28 Feb 2006 GMR-01
BSC system capacity Chapter 6: BSC planning steps and rules
6-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
• The offered load.
• The potential carried load.
To determine the link and processing requirements of the BSC, the number of trunks or the offered call load
in Erlangs (whichever is greater) should be used.
BSC capacity planning requires a model that associates the signalling generated from all the pertinent GSM
procedures: call setup and clearing, handover, location updating, and paging, to the offered call load. To
establish the relationship between all the procedures, the traffic model expresses processing requirements
for these procedures as ratios to the number of call attempts processed. The rate at which call attempts are
processed is a function of the offered call load and the average call hold time.
68P02900W21-R 6-11
28 Feb 2006 GMR-01
Determining the required BSS signalling link capacities Chapter 6: BSC planning steps and rules
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.
6-12 68P02900W21-R
GMR-01 28 Feb 2006
Figure 6-1 graphically depicts various factors that should be taken into account when planning a BSS.
Figure 6-1 {23769} 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 *
1 x 64 KBIT/S CIRCUIT/ XBL
A INTERFACE (TERRESTRIAL LINKS) 1 x 64 KBIT/S CIRCUIT/4 TRUNKS
-C7 SIGNALLING LINKS 1 x 64 KBIT/S CIRCUIT/8 TRUNKS
-X.25 CONTROL LINK * (HALF RATE WITH 8 KBIT/S SUBMULTIPLEXING ENABLED)
-REQUIRED TRUNKS
WITH SUBMULTIPLEXING TRANSCODING AT BSC
1 x 64 KBIT/S CIRCUIT/C7 SIGNALLING LINK
1 x 64 KBIT/S CIRCUIT/X.25 SIGNALLING LINK*
1 x 64 KBIT/S CIRCUIT/TRUNK
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 THE # OF GSLs PCU - PLUS -
THE # OF GBLs THE # OF C7 SIGNALLING LINKS
- PLUS - (IF APPLICABLE*)
THE # OF X.25 LINKS (USUALLY ONE PER BSC)
- PLUS -
1 x 16 KBIT/S CIRCUIT/GPRS TIMESLOT THE # OF XBL LINKS
FOR CS1 AND CS2 - PLUS -
2 x 16 KBIT/S CIRCUIT/GPRS TIMESLOTS THE # OF GSL LINKS
FOR CS3 AND CS4
1 x 64 KBIT/S GSL LINK
RTF_DS0_COUNT x 64 KBIT/S
FOR EACH EGPRS RTF BSC
1 x 64 KBIT/S OF 1 x 16 KBIT/S RTF CIRCUIT/LAPD
SIGNALLING LINK
MOTOROLA BSC/BTS INTERFACE 2 x 64 KBIT/S CIRCUITS/RTF
NON-BLOCKING 4 x 64 KBIT/S CIRCUITS/RTF (SEE NOTE)
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 (OR 16 WITH HALF RATE
MANDATED) DETERMINES THE CARRIERS REQUIRED
(ON A BTS/SECTOR BASIS)
BTS
AIR INTERFACE
-TCHs, PDTCHs AND SIGNALLING TSs TRANSCODING MUST BE LOCATED AT THE
-TYPICALLY 2% BLOCKING FOR CS BSC, OR BETWEEN THE BSC AND MSC
TRAFFIC 8 pt. left aligned text
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
USING TRAFFIC, TO DETERMINE E1/T1 LINK INTERCONNECT

HARDWARE FOR THE `A' AND `BSC TO BTS' INTERFACE.
68P02900W21-R 6-13
28 Feb 2006 GMR-01
4 x 64 kbit/s circuits/RTF for a (AMR or {22064} GSM) HR RTF and 8 kbit/s switching is not
provisioned, or (for AMR only) the 7.95 kbit/s half rate codec mode is included in the Half
Rate Active Codec Set.
Besides the factors described in Figure 6-1, when LCS is enabled in the BSS, the following factors need to be
taken into account when planning a BSS:
• MTL link provisioning to support LCS signalling between the MSC and BSC for either
NSS-based LCS architecture or BSS-based LCS architecture, but not both.
• LMTL link provisioning for BSS-based LCS architecture only.
• RSL link provisioning with LCS supported.
6-14 68P02900W21-R
GMR-01 28 Feb 2006
Typical parameter values
The parameters required to calculate BSC processing and signalling link capacities are listed in Table 6-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 6-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 6-2 Typical call parameters

area (see below)
second
Note)
Percent link utilization (MSC to BSS) for U(MSC - BSS) = 0.20
GPROC2/GPROC3
Percent link utilization (BSC to BTS) U(BSC - BTS) = 0.25
GPROC2/GPROC3
Cont.
68P02900W21-R 6-15
28 Feb 2006 GMR-01
Table 6-2 Typical call parameters (Continued)

GPRS parameters
PDP context activation/deactivation (per sub/BH) PDPACT/DEACT = 1
CS3 = 15.8 kbit/s
CS4 = 21.8 kbit/s
EGPRS parameters
Average packet size (bytes) - Uplink PKDLSIZE = 287
Average packet size (bytes) - Downlink PKDLSIZE = 700
Traffic per sub/BH (kbytes/hr) - Uplink ULRATE = 39
Traffic per sub/BH (kbytes/hr) - Downlink DLRATE = 85
Average sessions per subscriber (per BH) Avg Sessions per sub = 3
Cont.
6-16 68P02900W21-R
GMR-01 28 Feb 2006
Table 6-2 Typical call parameters (Continued)

Coding scheme rates (MSC1-MSC9) at the MCS1 = 10.55
RLC/MAC layer MCS2 = 12.95
MCS3 = 16.55
MCS4 = 19.35
MCS5 = 23.90
MCS6 = 31.10
MCS7 = 46.90
MCS8 = 56.50
MCS9 = 61.30
Location update factor

The location update factor (L) is a function of the ratio of location updates to calls (l), the ratio of IMSI
detaches to calls (I) and whether the short message sequence (type 1) or long message sequence (type 2) is
used for IMSI detach; typically I = 0 (that is IMSI detach is disabled) as in the first formula given below.
When IMSI detach is enabled, the second or third of the formulas given below should be used. The type of
IMSI detach used is a function of the MSC.
If IMSI detach is disabled:
Other parameters
Other parameters used to determine GPROC and link requirements are listed in Table 6-3.
68P02900W21-R 6-17
28 Feb 2006 GMR-01
Table 6-3 Other parameters used in determining GPROC and link requirements

Number of MSC - BSC trunks N
Number of BTSs per BSS B
Number of cells per BSS C
Pages per call PPC = PGSM * (T/N)
LCS request rate (req/sec/BSC) LCS_BSC_Rate = (N/T) * LCS
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. These
assumptions translate into specific formula coefficients and include a margin of safety. As they are dependent
on call procedures, they are recalculated for every major software release. Link utilization should be monitored
to detect significantly different behaviour. The procedures used for the calculations are provided in Table 6-4.
Table 6-4 Signalling message procedures
MSC - BSC BSC - BTS SMLC - BSC

Call setup and clearing. Call setup and clearing. n/a
Handover, incoming and Handover, incoming and n/a
outgoing. outgoing.
Location update. Location update. n/a
SMS - P to P. SMS - P to P. n/a
IMSI detach (type 1). Paging. n/a
IMSI detach (type 2). One phase access. Enhanced one n/a
phase access
Note: Not supported for EGPRS
carriers.
LCS LCS n/a
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.
6-18 68P02900W21-R
GMR-01 28 Feb 2006
An additional assumption which is made in determining the formula coefficients, is that the procedures not
included in the traffic model are considered to have a negligible effect.
Supplementary Service (SS) messaging has not been taken into account. This could contribute a
significant signalling overhead in some networks.
Paging assumptions
In calculating the average 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:
• 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.
• 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.
Half rate assumptions

A (AMR or {22064} GSM) half rate enabled carrier is capable of carrying two half rate calls in each timeslot,
for a total of 16 (half rate) TCHs. The actual number in use at a given instance will depend upon such factors
as operator (both BSS and MSC) preference, mobile (that is, AMR capable) penetration, RF conditions,
handoff parameter and threshold setting, cell congestion levels, etc.
If it is known to a large degree of certainty what the mix of half rate and full rate calls will be, that number can
be used when considering equipment planning. Otherwise it is recommended that a worst case approach
be taken. For example, when determining the RSL signalling link capacity required, and half rate usage is
expected to be no more than 50%, and there are 2 (both half rate enabled) carriers, a mix of 9 fr and 10 hr
(plus 2 timeslots for signalling) TCHs can be used (for a total of 19). A worst case estimate will assume 16
TCHs per half rate enabled carrier, for a total of 28 TCHs. If only one carrier were half rate enabled, worst
case results in (16 hr, 6 fr) 22 TCHs.
68P02900W21-R 6-19
28 Feb 2006 GMR-01
When 8 kbit/s subrate switching is not available or an RTF is configured as AMR half rate capable and the
7.95 kbit/s half rate codec mode is included in the Half Rate Active Codec Set, then the carrier unit assigned
to that RTF will require four 64 kbit/s timeslots on the E1 circuit (regardless of how they are utilized).
{23769} For an EGPRS capable RTF (pkt_radio_type set to 3), 16 kbit/s switching on the backhaul is not
supported and allow_8k_trau has to be enabled if half rate is supported.
AMR HR Active Codec Set can not include 7.95kbit/s, when pkt_radio_type is set to 3.
6-20 68P02900W21-R
GMR-01 28 Feb 2006
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 GPROC1 and no
more than 40% utilization when the MTL/LMTL is running on a GPROC2 or GPROC3. Before use of the
40% utilization for GPROC2 or GPROC3, it is imperative that the operator verifies that the MSC/SMLC
vendor can also support 40% utilization at the MSC/SMLC end; if not, only 20% link utilization should
be used for GPROC2 and GPROC3.
If higher link utilizations are used, the controlling GPROCs (LCF-MTLs/LCF-LMTLs) may become
overloaded.
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 and SMLC to BSC links, allows for the signalling traffic from
the failed link to be redistributed among the remaining functioning links. Both the MSC-BSC and SMLC-BSC
C7 link set officially have 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.
68P02900W21-R 6-21
28 Feb 2006 GMR-01
Determining the number of RSLs required Chapter 6: BSC planning steps and rules
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:
• With the Motorola BSC/BTS interface there is a need for at least one 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" on page 6-11 in this chapter to determine the number of RSL links required.
• If closed loop daisy chains are used, each site requires a RSL in both directions.
• The provision of additional RSL links for redundancy.
• PCCCH signalling traverses the GDS (on a PDTCH) instead of the RSL. Thus, cells with
PCCCH enabled do not add to the RSL requirements for the BTS.
• If paging coordination is enabled with PCCCH, GSM circuit-switched pages are sent on the
PCCCH. Thus, some of the GSM paging load will be removed from the RSL.
• If LCS is enabled in the BSS, the signalling load due to LCS needs to be taken into account.
• 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.
6-22 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determining the number of RSLs required
Table 6-5 lists the limitations for 16 kbit/s RSLs supported on each BTS platform.
Table 6-5 BTS support for 16 kbit/s RSLs
BTS Platform No. of 16 kbit/s RSLs Supported

A BSU-based BTS 8
Horizon II macro and Horizonmacro 6
Horizonmicro2 / Horizoncompact2 2
M-Cell6 6
M-Cell2 4
M-Cellmicro and M-Cellcity 2
Horizon II macro BTSs support 4 x RSLs per E1, whereas Horizonmacro and M-Cell BTSs only
support 2 x RSLs per E1. This should be taken into consideration when determining the number
of E1s required to support the calculated RSLs per site.
68P02900W21-R 6-23
28 Feb 2006 GMR-01
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: is:
RSLGPRS+GSM 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
signalling links required to serve
the GSM part of the network at
16 kbit/s or at 64 kbit/s.
One phase access and enhanced one phase
In a GPRS network, there are two packet access procedures that the mobile can use to establish an uplink
TBF. The packet access can be done in either one phase or in two phases. In GPRS software architecture
prior to GSR6, the BSS only supports the two phases access procedure. Now, one phase access mode and
enhanced one phase access mode are supported.
One phase access

In a one phase uplink TBF access, the MS initiates an uplink TBF by sending a RACH to the BSS. The
RACH is received at the BTS and is then forwarded to the PCU. The PCU responds to the RACH with an
Immediate Assignment message containing an uplink assignment. The MS moves to the assigned PDTCH
and begins its uplink data transfer. This procedure allows the MS to gain access to the network much quicker
than with the two phase establishment procedure.
Enhanced one phase

The enhanced one phase uplink TBF access procedure speeds up the one phase packet access procedure even
further. The enhanced one phase access procedure allows the PCU to proactively assign resources for a one
phase uplink TBF, allowing the BTS to react quickly to a one phase RACH without forwarding the RACH to
the PCU and incurring excessive RSL delay and increasing RSL load. Depending on the RSL load, the RACH
to Immediate Assignment delay will reduce by approximately 60 ms or more.
6-24 68P02900W21-R
GMR-01 28 Feb 2006
Standard traffic model
The number of BSC to BTS signalling links (RSLs) must be determined for each BTS. This number depends
on the number of TCHs and PDTCHs at the BTS. Table 6-6 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 6-2. If the call parameters differ significantly
from the standard traffic model, use the formulae for the non-standard traffic model.
Table 6-6 assumes that there are no cells with PCCCH enabled.
Enhanced One Phase is not supported with EGPRS carriers.
For assumptions specific to half rate refer to "Half rate assumptions" on page 6-19.
Table 6-6 Number of BSC to BTS signalling links (without LCS)
With Enhanced One With One Phase Access

Phase Access
# TCHs/BTS # # 64 kbit/s # 16 kbit/s # 64 kbit/s # 16 kbit/s
(n) PDTCHs/BTS RSLs RSLs RSLs RSLs
(Ngprs)
<= 30 0 1 2 1 2
15 1 2 1 2
30 1 3 1 3
45 1 3 1 3
60 1 3 1 3
75 1 3 1 3
90 1 3 1 3
31 to 60 0 1 2 1 2
15 1 3 1 3
Cont.
68P02900W21-R 6-25
28 Feb 2006 GMR-01
Table 6-6 Number of BSC to BTS signalling links (without LCS) (Continued)
Phase Access
(Ngprs)
30 1 3 1 3
45 1 4 1 3
60 1 4 1 3
75 1 4 1 4
90 1 4 1 4
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 2 5 1 4
90 2 5 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
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
75 2 6 2 6
90 2 6 2 6
151 to 180 0 2 6 2 6
15 2 7 2 7
30 2 7 2 7
45 2 7 2 7
Cont.
6-26 68P02900W21-R
GMR-01 28 Feb 2006
Phase Access
(Ngprs)
60 2 7 2 7
75 2 7 2 7
90 2 7 2 7
181 to 210 0 2 6 2 6
15 2 7 2 7
30 2 8 2 7
45 2 8 2 8
60 2 8 2 8
75 2 8 2 8
90 2 8 2 8
211 to 240 0 2 7 2 7
15 2 8 2 8
30 2 8 2 8
45 2 8 2 8
60 3 9 2 8
75 3 9 3 9
90 3 9 3 9
241 to 270 0 2 8 2 8
15 3 9 3 9
30 3 9 3 9
45 3 9 3 9
60 3 9 3 9
75 3 9 3 9
90 3 10 3 9
271 to 300 0 3 9 3 9
15 3 10 3 10
30 3 10 3 10
45 3 10 3 10
60 3 10 3 10
75 3 10 3 10
Cont.
68P02900W21-R 6-27
28 Feb 2006 GMR-01
Phase Access
(Ngprs)
90 3 10 3 10
301 to 330 0 3 10 3 10
15 3 11 3 11
30 3 11 3 11
45 3 11 3 11
60 3 11 3 11
75 3 11 3 11
90 3 11 3 11
331 to 360 0 3 11 3 11
15 3 12 3 12
30 3 12 3 12
45 3 12 3 12
60 3 12 3 12
75 3 12 3 12
361 to 384 0 3 11 3 11
15 3 12 3 12
30 3 12 3 12
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. The number of 16
kbit/s RSLs allowable is dependent on the hardware platform and some 16 kbit/s values in the
above tables may not be valid. 64 kbit/s RSLs must be used if the allowable number of 16
kbit/s RSLs is exceeded.
6-28 68P02900W21-R
GMR-01 28 Feb 2006
Non-standard traffic model
64 kbit/s RSLs
If the call parameters differ significantly from those given in Table 6-2, use the following formula to determine
the required number of 64 kbit/s RSLs.
If LCS is enabled at the BSS, LCS signalling (“+ 24 * LCS") needs to be included (as shown) in the following
equations. If LCS is disabled, remove “+ 24 * LCS" from the equations.
If paging coordination (i.e. NOM I) is enabled and every cell in the BTS site has PCCCH enabled
(pccch_enabled = 1):
_ _
_ _
Otherwise:
The RSL traffic load for GPRS depends on the following factors:
• PCCCH provisioning per cell.
• The access mechanism used on the air interface. Motorola BSCs allow use of one phase access
or a Motorola proprietary enhanced one phase mechanism.
With one phase access
_
_ _ _ _
68P02900W21-R 6-29
28 Feb 2006 GMR-01
With enhanced one phase access
_
_ _ _ _
Therefore, the total number of 64 kbit/s RSLs required is:
When all cells in the BTS have PCCCH enabled then RSLGPRS@64k = 0.
16 kbit/s RSLs
If the call parameters differ significantly from those given in Table 6-2, use the following formula to determine
the required number of 16 kbit/s RSLs.
If LCS is enabled at the BSS, LCS signalling (“+ 24 * LCS") needs to be included (as shown) in the following
equations. If LCS is disabled, remove “+ 24 * LCS" from the equations.
6-30 68P02900W21-R
GMR-01 28 Feb 2006
If paging coordination (i.e. NOM I) is enabled and every cell in the BTS site has PCCCH enabled
(pccch_enabled = 1):
_ _
_ _
Otherwise:
_
_ _ _ _
_
_ _ _ _
Therefore, the total number of 16 kbit/s RSLs required is:
When all cells in the BTS have PCCCH enabled then RSLGPRS@16k = 0.
68P02900W21-R 6-31
28 Feb 2006 GMR-01
GPRS RACH arrivals

The average number of RACH arrivals per second is given by:
_ _ _ _ _
_
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, it is expected that the sessions arrival rate
in each cell may potentially be higher than GSRs prior to GSR6. 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.
In the above equations:
Where: is:
RSLGSM + GPRS the number of BSC-BTS
signalling links.
n the number of TCHs at
the BTS site.
S the ratio of SMSs to
calls.
SMSSIZE the average size of the
SMS message (payload
only).
H the number of handovers
per call.
L the location update
factor.
LCS the number of LCSs per
call.
U the percent link
utilization (e.g. 0.25).
T the average call duration.
PGSM the GSM paging rate in
pages/second.
PGPRS the GPRS paging rate in
pages/second.
Cont.
6-32 68P02900W21-R
GMR-01 28 Feb 2006
Where: is:
CBTS the number of cells at the
BTS.
GPRS_RACH/sec the number of RACH
arrivals/second/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.).
NGSM_Only_MS the number of mobiles
in the system that do not
support GPRS.
NGSM_Capable_MS the number of mobiles in
the system that support
GSM and, optionally,
GPRS. This is also equal
to the total number of
mobiles in the system
minus the number of
GPRS only mobiles.
PCCCH_BTS = 0 if all cells in the BTS
have PCCCH enabled,
otherwise = 1.
RPCCCH_Cells_in_BTS the ratio of
PCCCH-enabled cells
at the BTS (the number
of cells at the BTS with
PCCCH enabled divided
by the total number of
cells at the BTS).
The Enhanced Scheduling feature introduces a new parameter percent_traf_cs, which secures a portion of
the bandwidth on the RSL for Circuit Switched (CS) traffic. The default value of this parameter is 55%,
meaning that GPRS traffic cannot utilize more than 45% of the total RSL bandwidth, that is, 45% of the total
link capacity (16K or 64K). Setting percent_traf_cs to zero implies pre-GSR7 conditions, that is, CS and
GPRS have equal privileges to occupy the RSL. Normal RSL planning does not recommend exceeding a
MEAN of 25% RSL utilization, hence the thresholds for this parameter are to be triggered under abnormal
conditions, where unexpected sustained surge occurs.
Assuming that during a surge of traffic (much higher than the planned 25%) the ratio of CS to GPRS traffic is
maintained, the default value (55%) for percent_traf_cs can be adjusted to reflect it.
68P02900W21-R 6-33
28 Feb 2006 GMR-01
Take an example where total RSL MEAN utilization is 25%, and the ratio of CS to GPRS traffic is 4 to 1. In
other words, CS contributes 20% to RSL utilization and GPRS contributes 5%. Maintaining the same ratio
during a surge will suggest to set percent_traf_cs to 80%, meaning that GPRS cannot occupy more than
20% of total RSL bandwidth.
6-34 68P02900W21-R
GMR-01 28 Feb 2006
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.
To determine the impact of different coding schemes on interconnect planning, use the following equation:
{23769}
_ _
Where: is:
NBSC-BTS the minimum number of E1
links required (rounded up to an
integer).
nEGPRS the number of carriers with
EGPRS enabled.
nCGPRS the number of carriers with GPRS
CS3 and CS4 enabled and GSM
voice only carriers where the half
rate exception case applies.
nGGPRS the number of carriers with GPRS
CS1 and CS2 enabled and GSM
voice only carriers where the half
rate exception case does not apply.
L16 the number of 16 kbit/s RSLs
(LAPD links).
L64 the number of 64 kbit/s RSLs
(LAPD links).
{23769} RTF_DSO_COUNTi Value of rtf_dso_count for the
RTF.
This formula includes both L16 and L64 to provide the necessary number of RSLs. As above,
either L16 or L64 RSL can be used to a single BTS, but not both.
68P02900W21-R 6-35
28 Feb 2006 GMR-01
Table 6-7 defines the backhaul required for the different coding schemes and configurations.
Table 6-7 Backhaul requirements
{23769} VersaTRAU
16 kbit/s 32 kbit/s
backhaul
GSM Voice only carries where the GSM Voice only carriers where EGPRS capable carriers
half rate exception case does not the half rate exception case does (MCS1-MCS9).
apply. apply.
Carriers with only GPRS CS1 and Carriers with only GPRS CS1,
CS2 enabled. CS2, CS3 and CS4 enabled.
{23769} All EGPRS carriers (pkt_radio_type = 3) will use VersaTRAU frame formats on the
backhaul between BTS and PCU to carry the data for PDTCHs on this carrier irrespective of
whether VersaTRAU is restricted/unrestricted.
BSC to BTS E1 interconnect planning example

Assume a 3 sector BTS with 8 carriers per sector. Each sector has:
• 2 carriers of GSM voice with no half rate exception,
• 1 carrier with GPRS CS1 and CS2,
• 2 carriers of GSM voice with half rate exception,
• 2 carriers of GPRS CS1, CS2, CS3, CS4,
• 1 carrier of EGPRS, {23769} VersaTRAU is restricted and all EGPRS RTFs are non-BCCH.
The number of E1s would be calculated as follows:

{23769}
In this example, 3 E1s are required to backhaul this BTS to the BSC. To find out the total number of E1s
required for a BSC, all of the BTSs backhaul requirements would need to be calculated and then added
together.
The network configuration would need to be consulted to determine if backhaul from multiple BTSs could be
multiplexed on a single E1. Examples of this type of capability would be if:
• the BTSs are daisy chained,
• the network uses cross connect equipment between BTSs and BSCs.
6-36 68P02900W21-R
GMR-01 28 Feb 2006
{23769} The same example is presented below in a scenario where VersaTRAU is unrestricted. We again
have a 3 sector BTS with 8 carriers per sector. Each sector has:
• 2 carriers of GSM voice with no half rate exception,
• 1 carrier with GPRS CS1 and CS2,
• 2 carriers of GSM voice with half rate exception,
• 2 carriers of GPRS CS1, CS2, CS3, CS4,
• 1 carrier of EGPRS, VersaTRAU is unrestricted and RTF backhaul is set to 5.
The number of E1s would be calculated as follows:
In this example, 3 E1s are required to backhaul this BTS to the BSC. To find out the total number of E1s
required for a BSC, all of the BTSs backhaul requirements would need to be calculated and then added
together.
68P02900W21-R 6-37
28 Feb 2006 GMR-01
Determining the number of LCF GPROCs for RSL and GSL

processing
Determine the number of GPROCs required to support the layer 3 call processing.
Both GPROC2 and GPROC3 or a combination of the two can perform layer 3 call processing
for GSM and GPRS (GPROC3 is a direct board level replacement for GPROC2). See Generic
processor (GPROC) later in this chapter.
The calculations are performed separately for the number of GPROCs required for GSM traffic and for
GPRS traffic.
The LCF GPROCs can simultaneously handle signalling traffic from both the GSM and GPRS parts of the
network. It is possible to calculate the GPRS/EGPRS part of the signalling load for the LCF GPROCs in
fractional increments. The GPRS/EGPRS LCF GPROC requirements can be directly added to the GSM
requirements in order to determine the total number of LCF GPROCs to equip at a BSC.
GSM layer 3
There are two methods for calculating this number. The first is used when the call parameters are similar to
those listed in Table 6-2 (standard traffic model). The second method is used when the call parameters differ
significantly from those listed in the tables (i.e. non-standard traffic model).
Standard traffic model (without LCS)
Use the formula:
Where: is:
GL3 the number of LCF GPROCs
required to support the layer 3 call
processing.
n the number of TCHs at the BSC
(see half rate assumptions earlier
in this chapter).
B the number of BTS sites.
C the number of cells.
6-38 68P02900W21-R
GMR-01 28 Feb 2006

If the call parameters differ significantly from those given in Table 6-2, the alternative formula given below
should be used to determine the recommended number of LCFs.
The above formula has been calculated using 70% mean utilization of the GPROC.
Where: is:
GL3 the number of LCF GPROCs
required to support the layer 3 call
processing.
n the number of TCHs under the
BSC (see half rate assumptions
earlier in this chapter).
S the ratio of SMSs to calls.
H the number of handovers per call.
i the ratio of intra-BSC handovers
to all handovers.
L the location update factor.
LCS the number of LCSs per call.
T the average call duration.
PGSM the GSM paging rate in pages per
second.
C the number of cells.
68P02900W21-R 6-39
28 Feb 2006 GMR-01
Having calculated the LCF GPROCs 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.
GPRS layer 3
The MSC can send GSM alerting pages to a GPRS/EGPRS mobile that operates in class A or class B modes.
The significance of this is that GPRS/EGPRS 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 GPROCs.
6-40 68P02900W21-R
GMR-01 28 Feb 2006
The planning information provided here should be used for this provisioning.
_ _ _
Where
_ _ _ _ _ _
_
Where: is:
GL3_GPRS the number of LCF
GPROCs to handle
GPRS related RSL
signalling traffic.
Total_RACH/sec the sum of all GPRS
RACH arrivals at the
BSC.
RPCCCH_Cells the ratio of
PCCCH-enabled cells
(the number of cells in
the BSS with PCCCH
enabled divided by the
total number of cells in
the BSS.
PCCCH_BSS = 0 if all cells in the BSS
have PCCCH enabled,
otherwise = 1.
PGPRS Paging rate in pages per
second.
GPRS_subs_per_PCU the total number of
GPRS users under a
PCU in the busy hour.
Avg_session_per_subs the average number of
sessions per subscriber
in a busy hour (includes
sessions for signalling).
68P02900W21-R 6-41
28 Feb 2006 GMR-01
Determining the number of MTLs required Chapter 6: BSC planning steps and rules
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:
• 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.
• Determine the number of trunks to support the traffic requirements of the BSC using Erlang B
tables at the required blocking rate.
• 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.
• Determine if LCS is enabled in the BSS and which LCS architecture is supported by the BSC.
The BSC may support either NSS-based LCS architecture or BSS-based LCS architecture,
but not both.
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.
6-42 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determining the number of MTLs required
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.
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. 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 6-8 and Table 6-9 give the recommended minimum number of MSC to BSC signalling
links based on the typical call parameters, detailed in Table 6-2. The value for N is the greater of the following:
• The offered call load (in Erlangs) from all the BTSs controlled by the BSC.
• The potential carried load (approximately equal to the number of MSC to BSC trunks).
The offered call load for a BSS is the sum of the offered call load from all of the cells of the BSS. The offered
call load at a cell is a function of the number 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.
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.
68P02900W21-R 6-43
28 Feb 2006 GMR-01
Table 6-8 and Table 6-9 show how to estimate the number of MTLs to be used for the BSC, with 20%
and 40% link utilization, respectively.
Table 6-8 Number of MSC and BSC signalling links without LCS (20% utilization)
N = the greater No. of MTLs with 16 logical links No. of MTLs with 64 logical links
of number
of MSC-BSC
trunks or the Minimum With Minimum With
offered load required redundancy required redundancy
from the BTSs
N <= 170 1 2 1 2
170< N <=370 2 3 2 3
370 < N <= 500 3 4 3 4
500 < N <= 550 4 5 3 4
550 < N <= 760 6 7 5 6
760< N <= 940 6 7 6 7
940< N <= 1020 6 7 6 7
1020< N <= 1120 8 9 6 7
1120< N <= 1230 8 9 7 8
1230< N <= 1550 8 9 8 9
1550< N <= 1770 16 16 10 11
1770< N <=2070 16 16 11 12
2070< N <=2490 16 16 13 14
2490< N <=3120 16 16 16 16
6-44 68P02900W21-R
GMR-01 28 Feb 2006
Table 6-9 Number of MSC and BSC signalling links without LCS (40% utilization)
N = the greater No. of MTLs with 16 logical links No. of MTLs with 64 logical links
of number
of MSC-BSC
trunks or the Minimum With Minimum With
offered load required redundancy required redundancy
from the BTSs
N <= 370 1 2 1 2
370< N <=760 2 3 2 3
760 < N <= 1020 3 4 3 4
1020 < N <= 1120 4 5 3 4
1120 < N <= 1550 4 5 4 5
1550< N <= 1910 6 7 5 6
1910< N <= 2070 6 7 6 7
2070< N <= 2270 8 9 6 7
2270< N <= 3120 8 9 8 9
3120< N <= 3200 16 16 10 11
The capacities shown in Table 6-8 and Table 6-9 are based on the standard traffic model shown
in Table 6-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 GPROC1 and no more than 40% utilization when the MTL/LMTL
is running on a GPROC2 or GPROC3. Before use of the 40% utilization for GPROC2 or
GPROC3, 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
and GPROC3.
68P02900W21-R 6-45
28 Feb 2006 GMR-01
If the call parameters differ significantly from those given in Table 6-2, the following procedure is used to
determine the required number of MSC to BSC signalling links:
1. Use the formula below to determine the maximum number of Erlangs supported by a
C7 signalling link (nlink).
2. Use the formula below to determine the maximum number of Erlangs supported by a GPROC
(LCF-MTL) supporting a C7 signalling link (nlLCF-MTL).
3. The maximum amount of traffic a MTL (a physical link) can handle (nlmin) is the smaller
of the two numbers from Step 1 and Step 2.
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:
5. Next we need to determine the number of logical links each MTL (physical link) can
handle (nlog-per-mtl):
_ _
6. Finally, the number of required MTLs (mtls) is:
_ _
mtls should not exceed 16 per BSC.

The formula in Step 2 has been calculated using 70% mean utilization of GPROC2 (see Calculate
the number of LCFs for MTL processing later in this section).
Field experience suggests it is good practice to maintain the mean utilization of GPROCs at or
below 70%.
6-46 68P02900W21-R
GMR-01 28 Feb 2006
Where: is:
U the percent link utilization (for
example 0.20).
T call hold time.
S the ratio of SMSs per call.
SMSSIZE the average size of the SMS
message (payload only).
H the number of handovers per call.
i the ratio of intra-BSC handovers
to all handovers.
L the location update factor.
Clcs 26 for NSS-based architecture.
31 for BSS-based architecture.
LCS the number of LCSs per call.
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.
Calculate the number of LCFs for MTL processing
The purpose of the MTL LCF GPROC is to support the functions of MSC link protocol. For the LCF GPROC,
it is recommended that a LCF supports 2 MTLs.
Both GPROC2 and GPROC3 or a combination of the two can perform MTL processing (GPROC3
is a direct board level replacement for GPROC2). See Generic processor (GPROC) later in this
chapter. {25779} For GSR8, if the MTL is assigned to the BSP, a GPROC3 is required.
68P02900W21-R 6-47
28 Feb 2006 GMR-01
It is not recommended that a LCF supports both MTLs and RSLs.

It is not permitted for a LCF to support both MTLs and LMTLs.
LCFs for MSC to BSC links

Since one LCF GPROC can support two MTLs, the number of required LCFs is:
However, if the traffic model does not conform to the standard model:
otherwise:
Where: is:
NLCF the number of LCF GPROCs
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 GPROC (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.
6-48 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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 when LCS is enabled in the BSS.
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:
• Determine the LCS traffic requirements of the BSC.
• A BSC can only connect to one SMLC.
68P02900W21-R 6-49
28 Feb 2006 GMR-01
Determining the number of LMTLs required Chapter 6: BSC planning steps and rules
Determining the number of LMTLs
Traffic model
The number of required LMTLs depends upon the BSS configuration size and traffic model. See Table 6-1,
Table 6-2 and Table 6-4.
LMTL number
Use the following formula to determine the required number of 64 kbit/s LMTLs (rounded up to the next
integer):
_ _
_
Where: is:
LLMTL 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.
ROUND UP rounding up to the next
integer.
BSC to SMLC interconnection planning actions
Determine the number of E1 links required to connect to a SMLC. Redundant links may be added, if required.
Where: is:
NBSC-SMLC the minimum number
of E1 links required
(rounded up to an
integer).
ROUND UP rounding up to the next
integer.
6-50 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determining the number of LMTLs required
The BSC-SMLC signalling link LLMTL can only be terminated on an E1.
Calculate the number of LCFs for LMTL processing
The purpose of the LMTL LCF GPROC is to support the functions of the SMLC link protocol.
For the LCF GPROC, one dedicated LCF-LMTL is required for processing LMTLs
Both GPROC2 and GPROC3 or a combination of the two can perform LMTL processing
(GPROC3 is a direct board level replacement for GPROC2). See Generic processor (GPROC)
later in this chapter. {25779} For GSR8, if the LMTL functionality is assigned to the BSP,
a GPROC3 is required.
It is not recommended that an LCF supports both LMTLs and RSLs.

It is not permitted for a LCF to support both MTLs and LMTLs.
68P02900W21-R 6-51
28 Feb 2006 GMR-01
Determining the number of XBLs required Chapter 6: BSC planning steps and rules
Determining the number of XBLs required

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
XBLs carry the signaling traffic between the BSC and RXCDR. 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:
• Determine the traffic requirements of the BSC and/or the number of trunks (CICs) used
between the BSC and RXCDR.
• 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.
• A maximum of 20 XBLs (64 kbit/s or 16 kbit/s) can be configured for a BSC/RXCDR.
• A BSC can connect to a maximum of 10 RXCDRs and vice-versa.
Determining the number of XBLs
The calculations below should be performed for every connected RXCDR.

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 6-10 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.
6-52 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determining the number of XBLs required
Table 6-10 Number of BSC to RXCDR signalling links
N = number of
MSC to BSC No redundancy With redundancy
trunks
Number of 64 Number of 16 Number of 64 Number of 16
kbit/s XBLs kbit/s XBLs kbit/s XBLs kbit/s XBLs
N ≤ 1200 1 4 2 8
1200 < N ≤ 2400 2 8 4 16
2400 < N ≤ 3200 3 11 6 22 *
* This exceeds the 20 XBL limit and is therefore not a valid configuration.
It is recommended that the XBL link utilization does not exceed 40%. This allows a link to double it’s
capacity (to 80%) under fault conditions (in some configurations). Above 80% utilization, 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.
The minimum number of XBL links required as given in Table 6-10 were verified using a standard set of
call parameters. These are given in Table 6-11.
Table 6-11 Typical call parameters relating to XBLs
Parameter Value
Link utilization 40%
Call duration 120 s
Average XBL message size 50 bytes
XBL messages per new call * 1
XBL messages per full rate <-> half rate handover 1
Full rate <-> half rate handovers per call 1
* Mobile origination, mobile termination, hand-in from MSC.
68P02900W21-R 6-53
28 Feb 2006 GMR-01
Determining the number of XBLs required Chapter 6: BSC planning steps and rules
Non standard traffic model
If the call parameters differ significantly from those given in Table 6-11, use the following formula to
determine if the required number of 64 kbit/s XBLs (rounded up to the next integer) should be adjusted:
Use the following formula to determine if the required number of 16 kbit/s XBLs (rounded up to the next
integer) should be adjusted:
Where: is:
XBL the number of BSC to RXCDR
signalling links.
N the number of MSC-BSC trunks.
T the average call duration in
seconds.
Mnewcall the number of XBL messages per
new call.
Mhandover the number of XBL messages per
hr <-> fr handover.
Hfr-hr the number hr <-> fr handovers
per call.
LXBL the average length of a XBL
message in bytes.
U(BSC-RXCDR) the percentage link utilization
(0.40, for example).
Double the number if redundancy is desired.

The number of XBLs required is then the larger of the number as determined by the formula and the number
given in Table 6-10.
6-54 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determining the number of GSLs required
Determining the number of GSLs required

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Each PCU requires one E1 in order to carry GSL signalling, and a second E1 for redundancy. There may be
up to three PCUs. Each PCU can support up to 30 primary GSL 64 kbit/s timeslots and 30 redundant. Each 64
kbit/s timeslot is one LAPD channel. Provisioned GSL timeslots are load-balanced over two E1 links per
PCU, as the mechanism for providing resiliency against link failures. It is recommended that two GSL E1
links per PCU are provisioned for resilience purposes, even when the GSL is lightly loaded.
The number of GSLs required is calculated as follows:
_ _
The requirement for the number of GSLs during system initialization (GSLinit_time) is 6.
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 during run-time
(after the system stabilizes) is as shown below.
With one phase access, there is additional loading on the RSL and GSL due to enhanced one phase messaging
and immediate assignment messages for UL TBF setups.
68P02900W21-R 6-55
28 Feb 2006 GMR-01
Determining the number of GSLs required Chapter 6: BSC planning steps and rules
_ _
_ _
Where:
_ _ _ _ _ _
_
GPRS paging is performed per routeing area (RA). A GPRS page will be sent to all cells within the RA. If
PCCCH is enabled at a cell then the GPRS page is sent to that cell on the GDS TRAU link.
6-56 68P02900W21-R
GMR-01 28 Feb 2006
The GSL requirements for GPRS paging is given by the following:
_ _ _ _
Where: is:
GSL the number of 64 kbit/s LAPD
GSL timeslots to provision.
GSLinit_time the number of GSLs required for
system initialization.
GSLrun_time the number of GSLs required for
signalling while the system is
stable.
PGPRS the GPRS paging rate in pages per
second.
Total_RACH/sec the sum of all GPRS 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_subs the average number of sessions
per subscriber in a busy hour (this
includes sessions for signalling).
RPCCCH_Cells the ratio of PCCCH-enabled cells
(the number of cells with PCCCH
enabled divided by the total
number of all cells in the BSS).
No_LCFs_for_RSL the number of LCF boards in the
BSC that terminate RSL links.
PCCCH_BSS = 0 if all cells in the BSS have
PCCCH enabled, otherwise = 1.
Load balancing
When applying even distribution of GSLs terminated on LCFs, the GSL traffic is load balanced over all GSLs.
Furthermore, should more than one GSL terminate on a LCF, the load shall be balanced over these GSLs.
The general rule of thumb is to terminate at least one GSL on a SITE LCF in a heavily loaded system to
avoid unnecessary LAN traffic.
The first E1 carries up to 30 LAPD links and the second E1 up to another 30. For LAPD-type GDS resiliency,
two E1s are recommended, regardless of the number of LAPD channels required.
In sysgen, the gsl_lcf_mapping parameter determines if the BSS will automatically distribute the GSLs
to different LCFs (Auto mode) or if the operator should specify the LCF (Manual mode) that will terminate
the GSL.
68P02900W21-R 6-57
28 Feb 2006 GMR-01
In Auto mode, the operator is not prompted for the LCF during the equipage of the GSL and the system
distributes the GSLs as evenly as possible on the LCFs, based on the algorithm defined below.
In Manual mode, the operator is prompted for an LCF during the equipage of the GSL. AUTO mode of
gsl_lcf_mapping is only valid in sysgen. Outside of sysgen, gsl_lcf_mapping is always set to
MANUAL.
Should the operator need to specify LCFs outside of sysgen mode or wish to configure the system manually,
the GSLs should be evenly distributed among the LCFs that terminate the RSLs. The same algorithm as used
in Auto mode can be used to perform the mapping manually.
Algorithm description for GSL distribution (Auto mode)

Following is a high level description of the algorithm that is used to distribute the GSLs on the LCFs when the
Auto mode is selected.
6-58 68P02900W21-R
GMR-01 28 Feb 2006
1. Using the equation below to determine the maximum number of GSLs that have to be
terminated on a LCF.
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _
2. For any LCF, if the result from Step 1 is less than the number of PCUs equipped and the
max_gsls value for that LCF is set to a value more than the number of PCUs, equip at
least one GSL from each PCU on that LCF.
3. For any LCF, if the result from Step 1 is less than the number of PCUs equipped and the
max_gsls value for that LCF is set to a value less than the number of PCUs, equip GSLs
from as many different PCUs as possible.
4. Distribute the default GSLs from all the PCUs. Interleave the default GSLs and distribute
them in sets of n where n is the number of PCUs equipped. Based on the number of sites
equipped on the LCF, go through the LCFs in a descending order of the number of sites
equipped and distribute the default GSLs.
5. Go through the first GDS for all the PCUs and create a list of all the GSLs from all the PCUs
with the GSLs, from all the PCUs, interleaved.
6. Based on the number of sites equipped on the LCF, go through the LCFs in a descending order
of the number of sites equipped and distribute the GSLs from step in sets of n, where n is
the number of PCUs equipped.
7. Go through the second GDS for all the PCUs and create a list of the GSLs from all the PCUs
with the GSLs, from all the PCUs, interleaved.
8. Based on the number of sites equipped on the LCF, go through the LCFs in descending order
of the number of sites equipped and distribute the GSLs from step in sets of n, where n is
the number of PCUs equipped.
9. In Step 6 and Step 8 distribute the GSLs to the LCFs which have sites on them.
10. Repeat Step 6 and Step 8 recursively within the max_gsls limit and the limit computed in
Step 1.
11. If no GSLs are equipped while going through Step 6 or Step 8, go to Step 12.
12. Go through all the LCFs from MAX_LCF to 0 and equip the GSLs on any LCF that has the
capacity to support GSLs.
The Auto mode distribution addresses the disparity in which GSLs were previously assigned to LCFs. The
Auto distribution significantly reduces the messaging between GPROCs. Previously, it was common to assign
all or most GSLs to a single LCF, which resulted in unnecessary traffic between this LCF and other LCFs
carrying RSL traffic. Distributing the GSLs evenly between RSL LCFs alleviates the messaging associated
with GPRS signalling between LCFs and increases the probability that GPRS signalling will be handled by the
same LCF. There may still be instances whereby GPRS signaling will traverse two LCFs, but these instances
will be significantly reduced. This is the sole purpose of this procedure.
The operator may choose to manually distribute the GSLs, but it is recommended to use a similar approach -
evenly distribute among LCFs carrying RSL traffic. Although it is not necessary, the operator may chose to
consider the total count of PDTCHs on each LCF and assign more GSLs to those LCFs having more PDTCHs.
68P02900W21-R 6-59
28 Feb 2006 GMR-01
Example (for reference purposes)

Consider the following:
Number of PCUs = 3 (PCU 0 - PCU 2).
Number of LCFs on the BSC = 6 (LCF 0 - 5).
max_gsls value for every LCF = 12.
Each PCU has 20 GSLs (0 - 19). GSLs 0 - 9 are on GDS 0; GSLs 10 - 19 are on GDS 1.
Total Number of GSLs on the BSC = 3 * 20 = 60.
LCF 0 and LCF 1 each have 5 sites on them.
Default GSLs on all the PCUs are GSL 0 and GSL 1.
Using Step 4 from the above algorithm GSL 0 from PCU 0, GSL 0 from PCU 1 and GSL 0 from PCU 2
will be terminated on LCF 0.
Again, using Step 4 from the above algorithm GSL 1 from PCU 0, GSL 1 from PCU 1 and GSL 1 from
PCU 2 will be terminated on LCF 1.
Using Step 6 from the above algorithm GSL 2 and GSL 8 from all the PCUs will be terminated on LCF 0.
Again, using Step 6 from the above algorithm GSL 3 and GSL 9 from all the PCUs will be terminated
on LCF 1.
Using Step 8 from the above algorithm GSL 10 from all the PCUs will be terminated on LCF 0.
Again, using Step 8 from the above algorithm GSL 11 from all the PCUs will be terminated on LCF 1.
Therefore, the final distribution of GSLs on the LCFs is as follows:
LCF 0 has GSL 0, GSL 2, GSL 8 and GSL 11 from all the PCUs.
LCF 3 has GSL 5, GSL 14 and GSL 18 from all the PCUs.
LCF 4 has GSL 6, GSL 15 and GSL 19 from all the PCUs.
LCF 5 has GSL 7 and GSL 16 from all the PCUs.
6-60 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Generic processor (GPROC)
Generic processor (GPROC)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GPROC nomenclature
For the purposes of this manual only and to avoid confusion between different versions of the generic
processor (GPROC), the following nomenclature is used:
GPROC1 specifically refers to the original GPROC.
GPROC2 specifically refers to the GPROC2.
GPROC is used in this manual as a non-specific term referring to both GPROC2 and GPROC3.
Introduction
Generic processor (GPROC) boards are used throughout the Motorola BSS as a control processor.
This section describes the BSC GPROC types and their functions. The BSC configuration type and GPROC
device type are essential factors for BSC planning.
The GPROC3 is a high performance direct replacement for GPROC2s and GPROC1s. This allows for any
combination of GPROC types to be installed {25779} except in the BSP slots where a GPROC3 is required.
GPROC3s cannot be used wth software versions earlier than GSR7.
GPROC functions and types
GPROCs are assigned functions and are then known by their function names.
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 of the same type (1, 2, or 3) 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.
68P02900W21-R 6-61
28 Feb 2006 GMR-01
Generic processor (GPROC) Chapter 6: BSC planning steps and rules
The possible general task groupings or functions for assignment to GPROCs are:
• BSC common control functions.
• OMC-R communications - OML (X.25) including statistics gathering.
• MSC link protocol (C7).
• SMLC link protocol (C7).
• BSS Layer 3 call processing (BSSAP) and BTS link protocol, RSL (LAPD).
• LAPD-type GDS link protocol, GSL.
• Cell broadcast centre link (CBL).
The defined GPROC devices and functions for the BSC are as follows (also see Table 6-12):
• Base Site Control Processor (BSP).
• Link Control Function (LCF).
• Operations and Maintenance Function (OMF).
• Code Storage Facility Processor (CSFP).
At a combined BSC BTS site, the BTF and DHP are additional GPROC function and type in the network
element.
Table 6-12 defines the GPROC types/functions for different software releases.
Table 6-12 GPROC type/function
Software
BSP MTL-LCF LMTL-LCF RSL-LCF OMF CSFP
Release
GSR7 GPROC2 or GPROC2 or GPROC2 GPROC2 or GPROC2 or GPROC2 or
(see Note) GPROC3 GPROC3 or GPROC3 GPROC3 GPROC3
GPROC3
{25779} {25779} {25779} {25779} {25779} {25779} {25779}
GSR 8 GPROC3 GPROC2 or GPROC2 or GPROC2 or GPROC2 or GPROC2 or
onwards GPROC3 GPROC3 GPROC3 GPROC3 GPROC3
(see Note)
When the enhanced BSC capacity feature and AMR (and/or {22064} GSM half rate) are used
together, it is mandatory for a GPROC3 to be installed in the BSP slot at the BSC. Otherwise,
replacing a GPROC2 with a GPROC3 in the BSP slot is at the discretion of the user. {25779}
For GSR8, a GPROC3 is mandatory in the BSP capable slots.
6-62 68P02900W21-R
GMR-01 28 Feb 2006
GPROC3 planning assumptions
The following assumptions are made regarding planning GPROC3 usage:

• GPROC3 processing performance is improved, when compared with GPROC2.
• {25779} A GPROC3 is required in the BSP slots.
• The GPROC3 can be used for other board functions besides BSP in the BSC only as a board
level replacement and replacement is not mandatory for these functions. The GPROC3 does
not provide any capacity and performance improvements in terms of number of links or sites
supported. The only difference is that an operator will see lower processor utilizations.
• The GPROC3 can be used as board level replacement for GPROC2 and GPROC1 at a BTS. It
is not mandatory for any function.
• The GPROC3 can be used as board level replacement for GPROC2 at the RXCDR. It is
not mandatory for any function.
BSC types
The BSC is configured as one of two types; the type is determined by the GPROCs present.
• BSC type 1
◦ Master GPROC.
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/LMTL (C7
signalling link) communications links. It also runs the GSLs for GPRS signalling
between the BSC and PCU.
• 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).
68P02900W21-R 6-63
28 Feb 2006 GMR-01
The following factors should be considered when planning the GPROC complement:
• BSP limitation.
{25779} For GSR8, it is mandatory to deploy GPROC3s in any potential BSP slot in the site,
both active and standby (that is, slot 20 and 24 in shelf 0 and slot 20 in shelf 1).
• Each BSC requires:

◦ One master GPROC3 (BSP).
◦ One OMF (if it is a type 2 BSC).
◦ A number of LCFs for MTLs, see Link control function below.
◦ One dedicated LCF for LMTL (if LCS is enabled and the BSS LCS architecture is
supported).
◦ LCFs to support the RSL and control of the BTSs.
◦ LCFs to support the GSLs for GPRS signalling between the BSC and PCU.
• Optional GPROCs Include:

◦ One redundant master GPROC3 (BSP).
◦ At least one redundant pool GPROC (covers LCFs).
◦ An optional dedicated CSFP.
• A maximum of eight GPROCs can be supported in a BSU shelf.
• For redundancy, each BSC should be equipped with a redundant BSP controller and an
additional GPROC3 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.
6-64 68P02900W21-R
GMR-01 28 Feb 2006
Link control function

The following factors should be considered when planning the number of LCFs:
• MTLs are assigned to dedicated LCFs.
• LMTLs are handled by one dedicated LCF.
• GPROCs can handle up to two MTLs.
• A single GPROC LCF can process up to 800 active calls if the ssm_critical_over-
load_threshold is set to 100. The default value is 80, meaning that the 641st
non-emergency call will be rejected (80% x 800 = 640 active calls).
Refer to Technical Description: BSS Command Reference (68P02901W23 )

for further details.
• For optimum performance, GSL handling should be distributed among the LCFs that terminate
RSLs. (See Load balancing in the previous section.)
Combining MTL and RSL processing on a single GPROC is not recommended.
68P02900W21-R 6-65
28 Feb 2006 GMR-01
The planning rules for LCFs using GPROCs are:

• A single GPROC will support two MTLs each working at 40% 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.
• If any LCF does not satisfy the above criteria, either rebalancing of sites on the available LCF
GPROCs at the BSC is required or additional LCF GPROCs may need to be equipped at the
BSC to process the traffic load.
• The link utilization of a RSL should not exceed 25%.
• A single GPROC can support up to 12 GSLs. This is set by the GPROC max_gsls parameter.
• Up to 25 LCFs can be supported.
• 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 GPROC, so if return loops are used the maximum number of
BTS sites will be 15 (if GPROC_slots = 32). If GPROC_slots is set to 16 then at most 15
RSLs may exist which would support up to 7 BTS sites, and if GPROC_slots is set to 24
then at most 23 RSLs may exist, supporting up to 11 BTS sites.
The number of serial links per GPROC must be determined. The current values
are 16, 24 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 15,
23 or 31. However, when the links are running at high load, the GPROC may
experience some performance problems when terminating 31 links. Hence, the use
of more than 23 links per board is not recommended.
• Setting GPROC_slots = 24 allows for additional LAPD links up to the recommended

maximum without the timeslot under-utilization associated with a GPROC_slots setting
of 32.
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 a 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 offloaded from the BSP is the central statistics process.
It is strongly recommended to equip an OMF.
6-66 68P02900W21-R
GMR-01 28 Feb 2006
Code storage facility processor
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 Horizon II macro, 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 GPROC is not required. This method is implemented
using the configure_csfp command 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 GPROC3.
This functionality allows an operator who already has either a redundant BSP/BTP or a pooled GPROC3 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 Technical Description: BSS Command Reference (68P02901W23) for more details on the configure_csfp
command.
GPROC redundancy
BSP redundancy
A failure of the BSP GPROC3 will cause a system outage. If the BSC is equipped with a redundant BSP
GPROC3, the system will restart under the control of the redundant BSP GPROC3s. If the BSC is not
equipped with a redundant BSP and the BSP GPROC3 were to fail, the BSC would be inoperable.
{22322} The BSC Reset Management feature is enabled by default. This feature provides fast switchover
between master and redundant BSP processors in the event of a BSP failure. Typically this will reduce the
outage time from 10 - 20 minutes to less than 2 minutes.
Pooled GPROCs for LCF and OMF redundancy

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.
68P02900W21-R 6-67
28 Feb 2006 GMR-01
GPROC planning actions
Determine the number of GPROCs required.
Where: is:
NGPROC the total number of GPROCs
required.
B the number of BSP GPROC3s
(2B for redundancy).
L the number of LCF GPROCs.
C the number of CSFP GPROCs.
R the number of pool GPROCs (for
redundancy).
If dedicated GPROCs are required for either the CSFP or OMF functions then they should be
provisioned separately.
6-68 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Transcoding
Transcoding
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to transcoding
Transcoding reduces the number of cellular subscriber voice/data trunks required by a factor of four. When
(AMR or {22064} GSM) half rate is in use and 8 kbit/s subrate switching is available and (for AMR only) the
7.95 kbit/s half rate codec mode is not included in the Half Rate Active Codec Set, the reduction factor for the
half rate calls becomes eight. Note that in most configurations half rate is likely used only for part of the time,
thus yielding a reduction factor of less than eight. 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 (less when half rate
is employed under the conditions described above) of the number of links between the RXCDR and the MSC.
The GDP2 can process 60 channels of FR, EFR, AMR, GSM HR and Phase 2 data services and is capable of
terminating two E1 links from the MSC. It can also function as a replacement for the GDP.
The capacity of one BSU shelf is 12 MSI slots, six of which may contain a transcoder (XCDR), generic
digital processor (GDP), enhanced digital processor (EGDP), or generic digital processor 2 (GDP2); this
limitation is due to power constraints.
A RXU shelf can support up to 16 GDP/XCDR/EGDP/GDP2s and typically provides a better solution of the
transcoding function for larger commercial systems. The GDP2 may be used to 60 channel capacity in the
BSU shelf, and when used in the new RXU3 shelf and BSSC3 cabinet (within the RXCDR, enhanced capacity
mode must be enabled to access the second E1 when GDP2s are used). The existing RXU shelf has only one
E1 per transcoder slot, therefore the GDP2 can not be used to its full capacity in the existing RXU shelf (the
GDP2 supports only 30 channels when used in the RXU shelf). Refer to the section "Remote transcoder
planning overview" on page 7-2 in Chapter 7, "RXCDR planning steps and rules,".
An EGDP is a new development of the GDP board, used to support AMR. Due to the additional transcoding
requirements of AMR, each of the 15 DSPs on the GDP board is only capable of supporting the transcoding
function for a single channel of GSM speech (AMR, FR, and EFR) and Phase 2 data services. To fully
offer 30 channels of enhanced transcoding using the same E1 span line to the MSC, enhanced GDPs are
equipped as pairs, each providing half of the transcoding resources. Note that this results in an overall
reduction in capacity — equivalent to 30 channels per GDP pair. Use of an EGDP is practical only when
used in conjunction with AMR. {22064} The EGDP does not support GSM half rate. The EGDP may also
terminate one Abis E1 link, thus reducing the number of MSIs boards required (see "EGDP provisioning" on
page 6-72). Due to the ability of the GDP2 to function as a GDP, it may replace one or both of the GDPs in
the EGDP configuration. This is not an optimal use of the GDP2 and is most likely to occur in emergency
situations (e.g. board replacement). As a result, it is not considered in the planning procedures.
The MSC recommends a particular codec type or types to be used on a call-by-call basis. It sends the BSC
a preference-ordered list, based on such factors as MS capabilities and operator configuration. When the
MSC is capable of choosing the MSC-RXCDR trunk (CIC) based upon the preferred codec type, a mix of
transcoding equipment may be used. If this capability (called “circuit pooling”) is not present, then some
equipment combinations may result in non-optimal behaviour.
When circuit pooling is available in an AMR enabled system, both AMR capable (EGDP/GDP2) and
non-AMR capable (XCDR/GDP) equipment may be used. If circuit pooling is not present, GDP2s or EGDPs
should be used exclusively to prevent downgrading or blocking of calls.
68P02900W21-R 6-69
28 Feb 2006 GMR-01
Transcoding Chapter 6: BSC planning steps and rules
When AMR is employed and both XCDR/GDPs and EGDP/GDP2s are present (and circuit pooling is present
at the MSC), there must be sufficient GDP2 and EGDP equipment available to handle the expected AMR
traffic. The proportion of AMR capable transcoding circuits vs. non-AMR capable transcoding circuits should
be no less than the proportion of AMR capable MSs vs. non-AMR capable MSs. A safety factor of no less
than 20% is recommended (20% allows for some variation in the actual number and allows for a period of
growth in AMR capable MS penetration before having to add more AMR transcoding ability). Note that each
AMR half rate call requires one (AMR) transcoder circuit. Lack of an available AMR circuit could cause
a call to be downgraded to another codec type or possibly blocked.
{22064} When GSM half rate is employed and a mix of XCDRs and GDP/GDP2s are present, a similar
situation exists. However, due to the early introduction into the standards of GSM half rate, most mobile are
expected to be GSM half rate capable. Since a CIC is not tied to any particular voice channel, circuit pooling
is rendered ineffective, as there is no way to predict which mobiles may require GSM half rate. It becomes
necessary to update all transcoding to support GSM HR in order to guarantee GSM half rate can be used when
needed. Without this upgrade, calls on non-GSM HR capable CICs will remain on a full rate channel.
{22064} When GSM half rate and AMR are both in use and a combination of AMR transcoding equipment
(EGDP, GDP2) and GSM half rate transcoding equipment (GDP, GDP2) exist, circuit pooling is most effective
when choosing AMR CICs (EGDP, GDP2) for AMR capable mobiles, and the remaining CICs for non-AMR
capable mobiles. Ideally, for AMR capable mobiles the MSC would first choose a CIC attached to a EGDP,
followed by one attached to a GDP2. For a non-AMR capable mobile the MSC would first choose a CIC
attached to a GDP, followed by one attached to a GDP2. The selection of the proper CIC (circuit pool) is
dependent upon the capability of the connected MSC.
6-70 68P02900W21-R
GMR-01 28 Feb 2006
GDP/XCDR/EGDP/GDP2 planning considerations
The following factors should be considered when planning the GDP/XCDR/EGDP/GDP2 complement:
• A XCDR can process 30 voice channels (E1), will support {22064} GSM Full Rate speech
({22064} GSM FR), uplink/downlink volume control and is capable of terminating one
E1 link from the MSC.
• A GDP can process 30 voice channels (E1) or 24 voice channels (T1), will support GSM FR,
enhanced Full Rate speech (EFR), GSM half rate speech (GSM HR), uplink/downlink volume
control and is capable of terminating one E1 or T1 link from the MSC.
• An EGDP consists of a pair of GDP cards, a “primary" and a “secondary". Each EGDP can
process 30 channels of {22064} GSM FR, EFR, AMR {22064} (FR and HR) speech and Phase
2 data services, and terminates one E1 link from the MSC.
{22064} GSM HR is not supported on an EGDP.
• The primary GDP of an EGDP terminates the E1 interface to the MSC.
• {22064} The secondary GDP of an EGDP may terminate an E1 interface to the BTS. See
"EGDP provisioning" on page 6-72.
• The GDP2 can process 60 channels of FR, EFR, AMR {22064} (FR and HR), GSM HR,
and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can
also function as a replacement for the GDP.
• XCDRs, GDPs, EGDPs, and GDP2s can co-exist in a shelf.
• The proportion of AMR-capable circuits (GDP2/EGDP) to non AMR-capable circuits

(XCDR/GDP) should be sufficient to handle the expected AMR traffic.
• The master MSI slot(s) should always be populated to enable communication with the OMC-R.
The master MSI slot may contain an XCDR/GDP/EGDP (see Note) /GDP2, if the OML
goes through the MSC.
• The A-interface must terminate on the XCDR/GDP/EGDP (either the primary or secondary)
/GDP2. A GDP can terminate T1 or E1 links, whereas an XCDR can only terminate E1 links
(refer to T1 conversion below). EGDP/GDP2s do not support T1.
An XCDR card is incompatible with a GPROC3 in the BSP slots. XCDRs must be replaced
with GDP/GDP2s.
68P02900W21-R 6-71
28 Feb 2006 GMR-01
EGDP provisioning
The secondary GDP of an EGDP may use the E1 connection to terminate an Abis link. This reduces the need
for MSIs and makes more efficient use of the available TDM timeslots. Note that the (secondary) GDP has
one E1 interface (instead of two for an MSI), which must be taken into account in site (MSI) planning.
Figure 6-2 and Figure 6-3 show the EGDP used in configurations with and without the additional E1
termination in use respectively.
Figure 6-2 EGDP configuration with the additional E1 termination in use
TDM Bus
Primary
GDP 15
E1 Span
DSPs E1 Span
to MSC
from an RXCDR
15 Secondary to a BSC or from
DSPs GDP a BSC to a BTS
6-72 68P02900W21-R
GMR-01 28 Feb 2006
Figure 6-3 EGDP configuration without the additional E1 termination in use
RXCDR: Static
or dynamic call
connections
Subrate between CICs BSC: Dynamic call
channels for GDP pair connections between
Static carried onto and Ater CICs for a GDP pair
"Pass-thru" the TDM bus channels and Abis channels
connections (TRAU frames (TRAU frames (TRAU frames
(at 64Kbps) using 16Kbps) using 16Kbps) using 16Kbps)
TDM Bus
Primary
GDP
E1 Span
to MSC 15
DSPs
E1 Span
from an RXCDR
MSI to a BSC or from
a BSC to a BTS
Secondary
GDP
15
DSPs
68P02900W21-R 6-73
28 Feb 2006 GMR-01
T1 conversion
T1 to E1 conversion is needed for XCDR, but not for GDP. EGDP and GDP2 do not support T1 connectivity.
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:
Where: is:
m 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.
6-74 68P02900W21-R
GMR-01 28 Feb 2006
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 6-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).
Where: is:
N 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 (see
Figure 6-1).
Each XCDR/GDP/EGDP can terminate one E1 link. Each GDP2 can terminate two E1 links (when used in a
BSU or RXU3 shelf (enhanced capacity mode must be enabled within the RXCDR to access the second E1
when GDP2s are used)). The equipment can be mixed within the following calculation:
Where: is:
N the minimum number of E1 links
required.
XGE the number of
XCDR/GDP/EGDPs.
G2 the number of GDP2s.
68P02900W21-R 6-75
28 Feb 2006 GMR-01
Verify that the number of AMR circuits is sufficient to handle the expected AMR traffic. If necessary,
adjust the number of EGDP/GDP2s. The following formula may be used to determine the percentage of
AMR capable circuits:
Count primary and secondary EGDPs as one EGDP in the above equation.
Using T1 links
The minimum number of T1 links required for the A-interface is the greater of the two calculations that follow
Where: is:
N the minimum number of T1 links
required.
through the MSC.
Figure 6-1).
Each GDP card can terminate one T1 link (see T1 conversion above for XCDR).
6-76 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
• Each MSI can interface two E1 links.
• Each MSI-2 can interface two T1 links.
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.
• Each E1 link provides 31 usable 64 kbit/s channels.
• Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2.
• Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links
connected to the site.
• The master MSI slot(s) should always be populated to enable communication with OMC-R.
If the OML links go directly to the MSC, the master slot should be filled with a
XCDR/GDP/EGDP (primary or secondary)/GDP2, 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.
68P02900W21-R 6-77
28 Feb 2006 GMR-01
Multiple serial interface (MSI, MSI-2) Chapter 6: BSC planning steps and rules
MSI/MSI-2 planning actions
If local transcoding is used then the NBSC-RXCDR element in the following equations can be ignored, otherwise
refer to Chapter 7 RXCDR planning steps and rules for the determination of the NBSC-RXCDR element.
With E1 links
Determine the number of MSIs required.
Without LCS:
With LCS for BSS-based LCS architecture:
The BSC-SMLC signalling link LMTL only terminates on an E1.
6-78 68P02900W21-R
GMR-01 28 Feb 2006
With T1 links
Determine the number of MSI-2s required.
Where: is:
NBSC-BTSi the number of links between the
BSC and the “ith" BTS.
NBSC-RXCDR the number of links from the
BSC to the RXCDRs (remote
transcoding only).
NBSC-SMLC the number of links from the BSC
to the SMLC.
NGDS-TRAU the number of links from the BSC
to the PCU carrying GDS TRAU
traffic (refer to Chapter 8).
NGSL-E1 the number of links between the
BSC and the PCU(s) carrying
GSL signalling links.
m the number of MSI/MSI-2s used
68P02900W21-R 6-79
28 Feb 2006 GMR-01
Kiloport switch (KSW) and double kiloport switch (DSW2) Chapter 6: BSC planning steps and rules
Kiloport switch (KSW) and double kiloport switch

(DSW2)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The kiloport switch (KSW) card provides digital switching for the TDM highway of the BSC.
The double kiloport switch (DSW2) is an enhanced version of the KSW which supports extended subrate
switching capability down to 8 kbit/s. Use of 8 kbit/s subrate switching can reduce backhaul costs when
used in conjunction with the AMR or {22064} GSM half rate feature.
The following factors should be considered when planning the KSW/DSW2 complement:
• A minimum of one KSW/DSW2 is required for each BSC site.
• The KSW/DSW2 capacity of 1024 x 64 kbit/s or 4096 x 16 kbit/s ports can be expanded by
adding up to three additional KSWs/DSW2s, giving a total switching capacity of 4096 x 64
kbit/s or 16384 x 16 kbit/s ports.
• When operating in extended subrate switching mode, the DSW2 can switch an additional
16384 x 8 kbit/s ports.
• Eight (64 kbit/s) timeslots per KSW/DSW2 are reserved by the system for test purposes and
are not available for use.
• A mix of KSWs and DSW2s requires that the DSW2s are operated in the 16 kbit/s switching
mode only.
• Note that enhanced capacity mode is only available at the RXCDR (not the BSC).
• Using 12 MSIs per KSW/DSW2 may reduce the number of shelves required at a cost of
additional KSWs/DSW2s. For example, a BSC with 28 MSIs could be housed in three shelves
with three KSW/DSW2 modules, or four shelves with two KSW/DSW2 modules.
• All configurations are dependent upon timeslot usage, as described below.
• For redundancy, duplicate all KSWs/DSW2s. In mixed configurations (KSWs and DSW2s),
KSWs can be redundant to DSW2s and vice-versa.
6-80 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Kiloport switch (KSW) and double kiloport switch (DSW2)
• Verify that each KSW/DSW2 uses no more than 1016 ports (8 ports are used internally). The
devices in a BSC that require TDM timeslots are:
◦ GPROC1 = 16 timeslots.
◦ GPROC2 or GPROC3 = 32, 24 or 16 timeslots.
◦ GDP or XCDR (or GDP2 acting as a GDP replacement) = 16 timeslots.
◦ EGDP = 96 timeslots.
◦ GDP2 = 24 timeslots.
◦ MSI/MSI-2 = 64 timeslots.
• There is one additional consideration with regard to timeslot usage which is related to the
timeslot allocation policy employed. Timeslots are grouped in 32 blocks of 32 timeslots each.
Generally, groups of 16 (the first 16 or last 16) can be allocated within a block. However,
the GDP2 is a special case as it requires 24 timeslots, a group of 16 and another 8 out of an
additional block. The remaining 8 timeslots (within the block of 16) can only be used by
another GDP2. Hence, if there is an odd number of GDP2s then 8 timeslots will be unusable.
As each device requires at a minimum 16 timeslots, this does not have any significant effect on
timeslot planning.
• The number of TDM timeslots is given by:
Where: is:
N the number of timeslots required.
G the number of GPROCs.
n 16, 24 or 32 (depending on the
value of the gproc_slots database
parameter).
RGDPXCDR the number of GDP/XCDRs.
REGDP the number of EGDPs.
RGDP2 the number of GDP2s.
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).
Any BSC site which contains a DRIM has 352 timeslots allocated to DRIMs, irrespective of
the number of DRIMs equipped.
68P02900W21-R 6-81
28 Feb 2006 GMR-01
Kiloport switch (KSW) and double kiloport switch (DSW2) Chapter 6: BSC planning steps and rules
KSW/DSW2 planning actions
Calculate the minimum number of KSWs/DSW2s required per BSC:
Where: is:
N the number of KSWs/DSW2s
required.
parameter).
RGDPXCDR 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).
Each KSW/DSW2 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/DSW2 in one shelf 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/DSW2
free, an additional MSI board CANNOT be added even if a MSI slot is free at each shelf, (but one GPROC per
shelf can be added if one GPROC slot per shelf is free).
6-82 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSU shelves
BSU shelves
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The number of BSU shelves is normally a function of the number of GPROCs, MSI/MSI-2s and
XCDR/GDP/EGDP/GDP2s required.
68P02900W21-R 6-83
28 Feb 2006 GMR-01
BSU shelves Chapter 6: BSC planning steps and rules
The following factors should be considered when planning the number of BSU shelves:
• Each BSU shelf supports up to eight GPROCs. If the number of these exceeds the number of
slots available, an additional BSU shelf is required.
• Each expansion shelf is allocated to a single KSW/DSW2 and extension shelves are
differentiated by the presence of the KSW/DSW2. Extension shelves are those which do not
contain a primary KSW/DSW2. Shelves containing a KSW/DSW2 are called expansion
shelves.
• An extension shelf extends the TDM highway. It is constrained to the same number of
(aggregate) timeslots as the shelf containing the KSW/DSW2.
• An expansion shelf adds an additional TDM highway. It increases the number of timeslots to
that of the additional KSW/DSW2.
• The following capacities depend on timeslot usage. See "Kiloport switch (KSW) and double
kiloport switch (DSW2)" on page 6-80 for information on how to determine timeslot usage.
◦ A BSU shelf can support up to 12 MSI/MSI-2 boards.
◦ A BSU shelf can support up to six XCDR/GDP/EGDP/GDP2s (reducing the number

of MSI/MSI-2 boards appropriately).
For EGDPs, both the primary and the secondary must be counted.
with GDP/GDP2s.
6-84 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSU shelves
BSU shelf planning actions
Determine the number of BSU shelves required.

The number of BSU shelves required is the highest value result of the three following calculations (fractional
values should be rounded up to the next integer value):
Where: is:
Bs the minimum number of BSU
shelves required.
M the number of MSI/MSI-2s.
R the number of
XCDR/GDP/EGDP/GDP2s
(see Note below).
The number of timeslots equipped to each shelf must be verified. This verification procedure is similar to the
one included in the KSW/DSW2 planning considerations section of this chapter (the KSW/DSW2 timeslot
validation will prevent a shelf from exceeding the timeslot limit) and is repeated here for completeness.
68P02900W21-R 6-85
28 Feb 2006 GMR-01
BSU shelves Chapter 6: BSC planning steps and rules
Where: is:
G the number of GPROCs in the
shelf.
parameter).
RGDPXCDR the number of GDP/XCDRs in
the shelf.
REGDP the number of EGDPs in the shelf.
RGDP2 the number of GDP2s in the shelf.
M the number of MSI/MSI-2s in
the shelf (do not count MSI-2s
which are doing on-board E1 to
T1 conversion).
If the result of the above equation exceeds 1016, the configuration of MSIs, GPROCs and GDPs may be
adjusted, or an additional shelf or shelves may be required.
The number of shelves may be larger if an attempt to reduce the number of KSWs/DSW2s is made.
The maximum number of shelves (cages) at a site = 8.
The maximum number of cabinets at a site = 8.
Horizon and M-Cell sites do not require a shelf to be equipped, only a cabinet.
Although the BSC can support a maximum of 56 MSI/MSI-2s and each of up to 4 BSU shelves
can support 12 MSIs, it is NOT the case that adding one extension shelf will provide the
additional capacity for the extra 8 MSIs.
Each extension shelf only supports 2 MSIs, due to a restriction on the KSW. Therefore, to achieve
the BSC limit for MSIs will require an additional 4 BSU extension shelves (4 x 2 = 8 MSIs).
6-86 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)
Kiloport switch extender (KSWX) and double kiloport

switch extender (DSWX)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 DSWX performs the same function as the KSWX when used in the BSU.
DSWXs are not required to pair with DSW2s when extended subrate switching mode is used
(KSWXs may be used).
68P02900W21-R 6-87
28 Feb 2006 GMR-01
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) Chapter 6: BSC planning steps and rules
The following factors should be considered when planning the KSWX/DSWX complement:
• KSWXs/DSWXs are not required in a single shelf configuration (that is, when expansion or
extension is not required).
• For redundancy, duplicate all KSWX/DSWX boards (requires redundant KSW/DSW2).

In mixed configurations (KSWXs and DSWXs), KSWXs can be redundant to DSWXs
and vice-versa.
• KSWXs/DSWXs are used in three modes:

◦ KSWX/DSWXE (Expansion) are required to interconnect the KSWs/DSW2s for sites
with multiple KSWs/DSW2s.
◦ KSWX/DSWXR (Remote) are required in shelves with KSWs/DSW2s to drive the TDM
highway in shelves that do not have KSWs/DSW2s.
◦ KSWX/DSWXL (Local) are used in shelves that have KSWs/DSW2s to drive the clock
bus in that shelf and in shelves that do not have KSWs/DSW2s to drive both the local
TDM highway and the clock bus in that shelf.
• Five of the redundant KSWX/DSWX slots are also CLKX slots.
• The maximum number of KSWX/DSWX slots per shelf is 18, nine per KSW/DSW2.
• KSWXs and DSWXs may both be used, however they should always be used with like pairs,
i.e. DSWXs with DSWXs and KSWXs with KSWXs.
6-88 68P02900W21-R
GMR-01 28 Feb 2006
KSWX/DSWX planning actions
The number of KSWXs/DSWXs required is the sum of the KSWX/DSWXE, KSWX/DSWXL and
KSWX/DSWXR:
Where: is:
NKX the number of KSWXs/DSWXs
required.
NKXE the number of KSWX/DSWXE.
NKXR the number of KSWX/DSWXR.
NKXL the number of KSWX/DSWXL.
K the number of non-redundant
KSWs/DSW2s.
SE the number of extension shelves.
For example:
Table 6-13 KSWX/DSWX (non-redundant)
Extension KSW/DSW2 (non redundant)

shelves 1 2 3 4
0 0 4 9 16
1 3 6 11 18
2 5 8 13 20
3 7 10 15 22
4 9 12 17 24
68P02900W21-R 6-89
28 Feb 2006 GMR-01
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) Chapter 6: BSC planning steps and rules
Table 6-14 KSWX/DSWX (redundant)
Extension KSW/DSW2 (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
6-90 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Generic clock (GCLK)
Generic clock (GCLK)

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

GCLKs = 1 + 1 redundant.
68P02900W21-R 6-91
28 Feb 2006 GMR-01
Clock extender (CLKX) Chapter 6: BSC planning steps and rules
Clock extender (CLKX)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one BSU.
The following factors should be considered when planning the CLKX complement:
• One CLKX is required in the first BSU shelf which contains the GCLK when expansion
beyond the shelf occurs.
• Each CLKX can supply the GCLK signals to six shelves.
• There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves
(LAN extension only allows fourteen shelves in a single network element).
• The maximum number of CLKX slots per shelf is six.
The CLKX uses six of the redundant KSWX slots.
• With a CLKX, a KSWX/DSWXL is required to distribute the clocks in the master and each of
the expansion/extension shelves.
• For redundancy, duplicate each CLKX (requires a redundant GCLK).
6-92 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Clock extender (CLKX)
CLKX planning actions
Determine the number of CLKXs required.
Where: is:
NCLKX the number of CLKXs required.
E the number of expansion/exten-
sion shelves.
RF Redundancy factor
(1 if redundancy is required
(recommended),
0 for no redundancy).
68P02900W21-R 6-93
28 Feb 2006 GMR-01
Local area network extender (LANX) Chapter 6: BSC planning steps and rules
Local area network extender (LANX)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The LANX provides a LAN interconnection for communications between all GPROCs at a site.
The following factors should be considered when planning the LANX complement:
• One LANX is supplied in each shelf.
• For full redundancy add one LANX for each shelf.
• The LANX can support a maximum network size of 14 shelves.
LANX planning actions
Determine the number of LANXs required.
Where: is:
NLANX the number of LANXs required.
NBSU the number of BSU shelves.
(recommended),
BSU ≤ 14
6-94 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Parallel interface extender (PIX)
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:
• The maximum number of PIX board slots per shelf is two.
• The maximum number of PIX board slots per site is eight.
PIX planning actions
Choose the number of PIXs required.
or
68P02900W21-R 6-95
28 Feb 2006 GMR-01
Line interface boards (BIB, T43) Chapter 6: BSC planning steps and rules
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.
• To match a balanced 120 ohm (E1 2.048 Mbit/s) or balanced 110 ohm (T1 1.544 Mbit/s) 3
V (peak pulse) line use a BIB.
• To match a single ended unbalanced 75 ohm (E1 2.048 Mbit/s) 2.37 V (peak pulse) line
use a T43 Board (T43).
• Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf.
• Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet.

◦ A maximum of 24 E1/T1 links can be connected to a BSU shelf.
◦ A BSSC2 cabinet with two BSU shelves can interface 48 E1/T1 links.
A BSSC3 cabinet can have up to seven BIBs or T43s per shelf mounted, but
in the BSU configuration this additional connectivity is not needed.
6-96 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Line interface boards (BIB, T43)
BIB/T43 planning actions

• Determine the number and type of link (E1 or T1) to be driven.
• Determine the number of BIBs or T43s required.
68P02900W21-R 6-97
28 Feb 2006 GMR-01
Digital shelf power supply Chapter 6: BSC planning steps and rules
Digital shelf power supply

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
A BSSC2 or BSSC3 cabinet can be supplied to operate from either a +27 V dc or -48 V/ -60 V dc power source.
For the purposes of this manual, BSSC is a generic term that means both BSSC2 and/or BSSC3.
The following factors should be considered when planning the PSU complement:
• Two DPSMs are required for each shelf in the BSSC.
• Two IPSMs are required for each shelf in the BSSC2 (-48 V/-60 V dc).
• Two IPSM2s are required for each shelf in the BSSC3 (-48 V/-60 V dc).
• Two EPSMs are required for each shelf in the BSSC (+27 V dc).
• For redundancy, add one DPSM, IPSM, or EPSM for each shelf.
Power supply planning actions
Determine the number of PSUs required.
Where: is:
(recommended),
6-98 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Non volatile memory (NVM) board
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.
The following factors should be considered when planning the NVM complement:
• Only one NVM board can be installed at the BSC.
• The NVM board uses slot 26 in the BSU shelf 0 (master) of the BSC, which is an unused slot.
• 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.
68P02900W21-R 6-99
28 Feb 2006 GMR-01
Verify the number of BSU shelves and BSSC cabinets Chapter 6: BSC planning steps and rules
Verify the number of BSU shelves and BSSC

cabinets
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verification
After planning is complete, verify that:

• The number of shelves is greater than one eighth the number of GPROC modules.
• Each non-redundant KSW/DSW2 has its own shelf.
• Each extension shelf supports extension of a single KSW/DSW2.
• The number of KSWX/DSWXs, LANXs, CLKXs, and GPROCs is correct.
• The number of MSI/MSI-2 and XCDR/GDP/EGDP/GDP2s

≤ 12 * number of shelves.
• The number of XCDR/GDP/EGDP/GDP2s

≤ 6 * number of shelves.
For the above two calculations, the EGDP consists of a primary and a secondary,
counting as two boards.
• The number of BTS sites

≤ 100
• The number of BTS cells

≤ 250
• RSLs.
≤ 250
• Carriers.
≤ 384
6-100 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Verify the number of BSU shelves and BSSC cabinets
• LCFs
≤ 25
• Erlangs.
≤ 3000
If necessary, add extra BSU shelves. Each BSSC cabinet supports two BSU shelves.
68P02900W21-R 6-101
28 Feb 2006 GMR-01
Verify the number of BSU shelves and BSSC cabinets Chapter 6: BSC planning steps and rules
6-102 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
7
RXCDR planning steps and rules
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The planning steps and rules for the RXCDR are provided here. The planning steps and rules for the BTS
are in Chapter 5, "BTS planning steps and rules," and the BSC are in Chapter 6, "BSC planning steps and
rules,". The topics described here are as follows:
• "Remote transcoder planning overview" on page 7-2
• "RXCDR system capacity" on page 7-4
• "RXCDR to BSC connectivity" on page 7-5
• "RXCDR to BSC links" on page 7-6
• "RXCDR to MSC links" on page 7-9
• "Generic processor (GPROC)" on page 7-11
• "Transcoding" on page 7-13
• "Multiple serial interface (MSI, MSI-2)" on page 7-20
• "Kiloport switch (KSW) and double kiloport switch (DSW2)" on page 7-23
• "RXU shelves" on page 7-27
• "Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)" on page
7-31
• "Generic clock (GCLK)" on page 7-34
• "Clock extender (CLKX)" on page 7-35
• "LAN extender (LANX)" on page 7-37
• "Parallel interface extender (PIX)" on page 7-38
• "Line interfaces (BIB, T43)" on page 7-39
• "Digital shelf power supply" on page 7-41
• "Non volatile memory (NVM) board" on page 7-42
• "Verify the number of RXU shelves and BSSC cabinets" on page 7-43
68P02900W21-R 7-1
28 Feb 2006 GMR-01
Remote transcoder planning overview Chapter 7: RXCDR planning steps and rules
Remote transcoder planning overview

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
To plan the equipage of an RXCDR, certain information must be known. The major items include:
• The BSC traffic requirements.
• The number of trunks (including redundancy) from the MSC.
• Each RXCDR may support multiple BSCs.
• The sum of the MSI/MSI-2s and the XCDR/GDP/EGDP (see Note)/GDP2s for each BSC
define the number of slots required at the RXCDR.
Each EGDP comprises two GDP cards.
• The use of E1 or T1 links.
• The use of balanced or unbalanced E1.
7-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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" on page 7-6.
2. Plan the number of E1 or T1 links between the RXCDR and MSC site(s), refer to the section
."RXCDR to MSC links" on page 7-9.
3. Plan the number of GPROCs required, refer to the section "Generic processor (GPROC)"
on page 7-11.
4. Plan the number of XCDR/GDP/EGDP/GDP2s required, refer to the section "Transcoding"

on page 7-13.
5. Plan the number of MSI/MSI-2s required, refer to the section "Multiple serial interface
(MSI, MSI-2)" on page 7-20.
6. Plan the number of KSWs/DSW2s and timeslots required, refer to the section "Kiloport
switch (KSW) and double kiloport switch (DSW2)" on page 7-23.
7. Plan the number of RXU shelves, refer to the section "RXU shelves" on page 7-27.
8. Plan the number of KSWXs/DSWXs required, refer to the section "Kiloport switch extender
(KSWX) and double kiloport switch extender (DSWX)" on page 7-31.
9. Plan the number of GCLKs required, refer to the section "Generic clock (GCLK)" on
page 7-34.
10. Plan the number of CLKXs required, refer to the section "Clock extender (CLKX)" on
page 7-35.
11. Plan the number of LANXs required, refer to the section "LAN extender (LANX)" on
page 7-37.
12. Plan the number of PIXs required, refer to the section "Parallel interface extender (PIX)" on
page 7-38.
13. Plan the number of BIB or T43s required, refer to the section "Line interfaces (BIB, T43)" on
page 7-39.
14. Plan the power requirements, refer to the section "Digital shelf power supply" on page 7-41.
15. Decide whether an NVM board is required, refer to the section "Non volatile memory
(NVM) board" on page 7-42.
16. Verify the planning process, refer to the section "Verify the number of RXU shelves and
BSSC cabinets" on page 7-43.
68P02900W21-R 7-3
28 Feb 2006 GMR-01
RXCDR system capacity Chapter 7: RXCDR planning steps and rules
RXCDR system capacity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
System capacity summary
Table 7-1 provides a summary of RXCDR maximum capacities.
Table 7-1 RXCDR maximum capacities
Item GSR6 GSR7 GSR8

RXCDR per BSC 10 10 10
XBLs 20 20 20
GPROCs per shelf 2 2 2
CICs 2400 4800a 4800a
OMLs 1 1 1
GCLK board 2 2 2
KSW/DSW2 8 8 8
LANX2 2 2 2
PIX 2 2 2
CLKX 2 2 2
KSWX/DSWX 8 8 8
MSI/GDP/GDP2 19 19 19
NVM 1 1 1
E1/T1s per MSI 2 2 2
E1/T1s per GDP 1 1 1
E1/T1s per GDP2 2 2 2
E1/T1s per XCDR 1 1 1
a: Increased to 4800 CICs when AMR (and/or {22064} GSM half rate) are both enabled.
7-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning RXCDR to BSC connectivity
RXCDR to BSC connectivity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
It is possible to have multiple RXCDRs connected to a single BSC, and vice-versa. This is especially
useful for two primary reasons:
1. In certain configurations the RXCDR call (CIC) capacity may be greater than that of a BSC.
2. A failure of a RXCDR, or communication path between a BSC and RXCDR will result in a
loss of capacity but not a complete failure of the serving BSC.
Capacity
Each BSC may connect to up to ten RXCDRs, and vice-versa. The level of connectivity may be constrained
by the number of XBLs that can be supported; there is a limit of 20 at each BSC and RXCDR (see
Determining the number of XBLs required in Chapter 6).
The level of connectivity is determined by the operator, Excess RXCDR capacity should not be wasted, nor
should larger BSCs be connected only to one RXCDR. One guideline is to have each BSC connect to four
RXCDRs. System size, capacity, and cost are major influences on the chosen configuration.
With the introduction of advanced transcoding capabilities (i.e. AMR), care should be taken when distributing
the functions across multiple RXCDRs. For optimum redundancy, each RXCDR should have an appropriate
mix of transcoder capability. For example, in a four BSC, four RXCDR configuration where all are
interconnected and there are a limited number of transcoder cards capable of AMR (e.g. GDP2s), optimally
the cards would be distributed equally amongst the RXCDRs.
68P02900W21-R 7-5
28 Feb 2006 GMR-01
RXCDR to BSC links Chapter 7: RXCDR planning steps and rules
RXCDR to BSC links

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
This text should be read in conjunction with the BSS planning diagram, Figure 6-1.
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.
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 when 16 kbit/s backhaul is used. {22064} When (AMR
or GSM) half rate is in use and 8 kbit/s subrate switching is available and (for AMR only) the 7.95 kbit/s
half rate codec mode is not included in the Half Rate Active Codec Set, the reduction factor for the half
rate calls becomes eight. Note that in most configurations half rate is likely used only a part of the time,
thus yielding a reduction factor of less than eight.
8 kbit/s backhaul may be used when (AMR or {22064} GSM) half rate is in use, the 7.95 kbit/s half rate codec
mode is not included in the Half Rate Active Codec Set, and 8 kbit/s subrate switching is in use.
If a percentage of the active calls can be assumed to be half rate, then efficiencies can be gained by reducing
the number of terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can
dynamically allocate a timeslot to a CIC. This dynamic allocation is performed across a trunked interface
between the BSC and a remote transcoder (RXCDR). This interface is called the Ater interface. The dynamic
allocation is referred to as “Enhanced Auto Connect mode".
Whenever the number of CICs exceeds the number of 16 kbit/s trunks between the RXCDR and BSC, there
exists a possibility that a call assignment may fail because of a resource shortage. Care should be taken to
ensure the accuracy of half rate usage estimations. The number will depend on a combination of factors,
including (AMR or {22064} GSM) capable mobile penetration, whether forced half rate usage is enabled
and/or tied in with congestion, and MSC preferences. It is recommended that a safety factor of at least 20% is
factored into any half rate usage estimate (20% allows for some variation in the actual number).
4 x 64 kbit/s circuits/RTF for a (AMR or {22064} GSM) HR RTF and 8 kbit/s switching is not
provisioned, or, (for AMR only) the 7.95 kbit/s half rate codec mode is included in the Half
Rate Active Codec Set.
7-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning RXCDR to BSC links
E1 interconnect planning actions
Determine the number of E1 links required.
Where: is:
NBSC-RXCDR the minimum number of E1 links
required.
C the number of C7 signalling links
to the MSC.
through the RXCDR.
B64 the number of 64 kbit/s XBL
links.
Figure 6-1).
PHR the percentage in decimal (e.g.
0.35) of expected half rate usage
(meeting the criteria stated
previously).
links.
Each E1 link carries up to 120 (240 at half rate) trunks with a signalling link or 124 (248 at half
rate) trunks without a signalling link. Note that the half rate numbers are only possible with
all calls using half rate.
Redundant E1 links carrying extra trunks may be added.
68P02900W21-R 7-7
28 Feb 2006 GMR-01
RXCDR to BSC links Chapter 7: RXCDR planning steps and rules
T1 interconnect planning actions
Determine the number of T1 links required.
Where: is:
NBSC-RXCDR the minimum number of T1 links
required.
C the number of C7 signalling links
to the MSC.
through the RXCDR.
links.
Figure 6-1).
links.
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.
7-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning RXCDR to MSC links
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 the two calculations that follow
Where: is:
NRXCDR-MSC the minimum number of E1 links
required.
through the MSC.
Figure 6-1).
68P02900W21-R 7-9
28 Feb 2006 GMR-01
RXCDR to MSC links Chapter 7: RXCDR planning steps and rules
T1 interconnect planning actions
Determine the number of T1 links required.
Where: is:
NRXCDR-MSC the minimum number of T1 links
required.
through the MSC.
Figure 6-1).
7-10 68P02900W21-R
GMR-01 28 Feb 2006
Generic processor (GPROC)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GPROC nomenclature
For the purposes of this manual only and to avoid confusion between different versions of the generic
processor (GPROC), the following nomenclature is used:
GPROC is used in this manual as a non-specific term referring to both GPROC2 and GPROC3.
Introduction
Generic processor (GPROC) boards are used throughout the Motorola BSS as a control processor.
The GPROC3 is a high performance direct replacement for GPROC2s and GPROC1s. This allows for
any combination of GPROC types to be installed.
GPROC3s cannot be used with software versions earlier than GSR7.
68P02900W21-R 7-11
28 Feb 2006 GMR-01
Generic processor (GPROC) Chapter 7: RXCDR planning steps and rules
The following factors should be considered when planning the GPROC complement at the RXCDR:
• Each shelf requires at least one GPROC board, plus one for redundancy.
• A maximum of two GPROCs per shelf are supported:

◦ One BSP GPROC3.
◦ One GPROC that can be configured as a redundant BSP GPROC3 or as a CSFP GPROC.
GPROC2s must be used for higher connectivity (up to 10 BSCs).

For GSR6 and GSR6 (Horizon II), GPROC2s are mandatory in the master
and standby BSP slots in shelf 0.
In GSR6 (Horizon II) + SP, GPROC3s can be used.
In the BSC, GPROC3s must replace GPROC2s in the BSP slots. The
RXCDR BSP does not need to be a GPROC3; you can still use a GPROC2 in
this position.
7-12 68P02900W21-R
GMR-01 28 Feb 2006
Transcoding
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to transcoding
Transcoders (XCDR/GDP/EGDP/GDP2s) provide the interface for the E1 (or converted T1) links between
the MSC and the BSC. The XCDR/GDP/EGDP/GDP2s perform the transcoding/rate adaptation function
which compresses the information on the trunks by a factor of four (16 kbit/s). {22064} When (AMR or
GSM) half rate is in use and 8 kbit/s subrate switching is available (and the 7.95 kbit/s half rate codec mode is
not included in the Half Rate Active Codec Set (AMR)) the reduction factor for the half rate calls becomes
eight. Note that in most configurations, half rate is likely used only a part of the time, thus yielding a
reduction factor of less than eight.
The number of links between the RXCDR and the BSC is reduced to approximately one quarter (less when
half rate is employed under the conditions described above) of the number of links between the RXCDR and
the MSC.
The GDP2 can process 60 channels of FR, EFR, AMR, {22064} GSM HR and Phase 2 data services and is
capable of terminating two E1 links from the MSC. It can also function as a replacement for the GDP. Within
the RXCDR, enhanced capacity mode must be enabled to access the second E1 when GDP2s are used.
An EGDP is a new configuration of the GDP board used to support AMR. Due to the additional transcoding
requirements of AMR, each of the 15 DSPs on the GDP board is only capable of supporting the transcoding
function for a single channel of GSM speech (AMR, FR, and EFR) and Phase 2 data services. To fully offer
30 channels of enhanced transcoding using the same E1 span line to the MSC, EGDPs are equipped as pairs,
each providing half of the transcoding resources. Note that this results in an overall reduction in transcoding
shelf capacity — equivalent to 30 channels per GDP pair. Use of an EGDP is practical only when used in
conjunction with AMR. {22064} The EGDP does not support GSM half rate. The EGDP may also terminate
one Ater E1 link, thus reducing the number of MSI boards required (see "EGDP provisioning" on page 7-16).
Due to the ability of the GDP2 to function as a GDP, it may replace one or both of the GDPs in the EGDP
configuration. This is not an optimal use of the GDP2 and is most likely to occur in emergency situations (e.g.
board replacement). As a result, it is not considered in the planning procedures.
The MSC recommends a particular codec type or types to be used on a call by call basis. It sends the BSC
a preference-ordered list, based on such factors as MS capabilities and operator configuration. When the
MSC is capable of choosing the MSC-RXCDR trunk (CIC) based upon the preferred codec type, a mix of
transcoding equipment may be used. If this capability (called “circuit pooling”) is not present, then some
equipment combinations may result in non-optimal behaviour.
When circuit pooling is available in an AMR enabled system, both AMR-capable (EGDP/GDP2) and non
AMR-capable (XCDR/GDP) equipment may be used. If circuit pooling is not present, GDP2s or EGDPs
should be used exclusively to prevent downgrading or blocking of calls.
When AMR is employed and both XCDR/GDPs and EGDP/GDP2s are present (and circuit pooling is present
at the MSC), there must be sufficient GDP2 and EGDP equipment available to handle the expected AMR
traffic. The proportion of AMR-capable transcoding circuits vs. non AMR-capable transcoding circuits
should be no less than the proportion of AMR-capable MSs vs. non AMR-capable MSs. A safety factor of no
less than 20% is recommended (20% allows for some variation in the actual number and allows for a period of
growth in AMR-capable MS penetration before having to add more AMR transcoding ability). Note that each
AMR half rate call requires one (AMR) transcoder circuit. Lack of an available AMR circuit could cause
a call to be downgraded to another codec type or possibly blocked.
68P02900W21-R 7-13
28 Feb 2006 GMR-01
Transcoding Chapter 7: RXCDR planning steps and rules
{22064} When GSM half rate is employed and a mix of XCDRs and GDP/GDP2s are present, a similar
situation exists. However, due to the early introduction into the standards of GSM half rate, most mobile are
expected to be GSM half rate capable. Since a CIC is not tied to any particular voice channel, circuit pooling
is rendered ineffective, as there is no way to predict which mobiles may require GSM half rate. It becomes
necessary to update all transcoding to support GSM HR in order to guarantee GSM half rate can be used when
needed. Without this upgrade, calls on non-GSM HR capable CICs will remain on a full rate channel.
{22064} When GSM half rate and AMR are both in use and a combination of AMR transcoding equipment
(EGDP, GDP2) and GSM half rate transcoding equipment (GDP, GDP2) exist, circuit pooling is most effective
when choosing AMR CICs (EGDP, GDP2) for AMR capable mobiles, and the remaining CICs for non-AMR
capable mobiles. Ideally, for AMR capable mobiles the MSC would first choose a CIC attached to a EGDP,
followed by one attached to a GDP2. For a non-AMR capable mobile the MSC would first choose a CIC
attached to a GDP, followed by one attached to a GDP2. The selection of the proper CIC (circuit pool) is
dependent upon the capability of the connected MSC.
Figure 7-1 shows sub-multiplexing and speech transcoding at the RXCDR.
• Each trunk requires a quarter (1/4th) (or an eighth (1/8th) in some cases for AMR half rate as
described above) of a 64 kbit/s circuit between the RXCDR and BSC.
• Each control link (RSL, OML,XBL,C7) requires one 64 kbit/s circuit.

(RSL and XBL have the option of using 16 kbit/s circuits.)
Figure 7-1 Sub-multiplexing and speech transcoding at the RXCDR
RXCDR BSC Horizon II macro BTS

X
C
D M M M
K S K S
R/ S S S ONE RF
G I I I N C CARRIER
M W / W / I
D / / / T
S P/ M M M U
D S D S U
C G S
S I S I 2
D W I W
P 2 2 2
2 2
2 HIISC
4 TO 8 TRUNKS PER 64 kbit/s

64 kbit/s
A-LAW 64 kbit/s CIRCUIT 4 OR 8 TCHs
TRUNKS
THE KSW (DSW2)
SUBRATE SWITCHES
16 kbit/s (8 kbit/s) 8 x 22.8 kbit/s TIMESLOTS OR
THE XCDR/GDP/GDP2 TRANSCODES 64 kbit/s TIMESLOTS.
A-LAW PCM TO/ FROM 13 kbit/s MAPPED THE CTU2 ENCODES/DECODES 16 x 11.4 kbit/s TIMESLOTS
ONTO 16 kbit/s OR UP TO 8 kbit/s MAPPED 13 (UP TO 8 FOR HALF RATE) kbit/s
ONTO 8 kbit/s, AND SUBMULTIPLEXES 4 to 8 TO/FROM 22.8 (11.4) kbit/s FOR 8 (16)
TRUNKS TO/FROM 1 x 64 kbit/s CIRCUIT. TIMESLOTS, AND SUBMULTIPLEXES 4
(13 kbit/s MAPPED ON 16 kbit/s) OR 8
(UP TO 8 kbit/s MAPPED ON 8 kbit/s
FOR HALF RATE) TIMESLOTS ONTO 1 x
64 kbit/s CIRCUIT, OR THE OTHER WAY
AROUND.
7-14 68P02900W21-R
GMR-01 28 Feb 2006
In Figure 7-1, the CTU2 is shown operating in single density mode (one carrier),
although it can also operate in double density mode (two carriers).
XCDR/GDP/EGDP/GDP2 planning considerations
The following factors should be considered when planning the XCDR/GDP/EGDP/GDP2 complement:
• A XCDR can process 30 voice channels ( E1), will support {22064} GSM Full Rate speech
({22064} GSM FR), uplink/downlink volume control and is capable of terminating one
{22064} E1 link from the MSC.
• A GDP can process 30 voice channels (E1) or 24 voice channels (T1), will support GSM FR,
enhanced Full Rate speech (EFR), GSM half rate speech (GSM HR), uplink/downlink volume
control and is capable of terminating one E1 or T1 link from the MSC.
• An EGDP consists of a pair of GDP cards, a “primary" and a “secondary". Each EGDP can
process 30 channels of {22064} GSM FR, EFR, AMR {22064} (FR and HR speech), and
Phase 2 data services, and terminates one E1 link from the MSC.
• The primary GDP of an EGDP terminates the E1 interface to the MSC.
• {22064} The secondary GDP of an EGDP may terminate an E1 interface to the BSC. See
"EGDP provisioning" on page 7-16.
• The GDP2 can process 60 channels of FR, EFR, AMR {22064} (FR and HR), GSM HR,
and Phase 2 data services and is capable of terminating two E1 links from the MSC. It can
also function as a replacement for the GDP.
• The GDP2 can be used to terminate 2 E1s (i.e. 60 voice channels) only in the RXU3 shelf
and BSSC3 cabinet (enhanced capacity mode must be enabled to access the second E1 when
GDP2s are used). The current RXU shelf has only one E1(T1) per transcoder slot, and the
current BSSC2 cabinet does not have space for additional line interface boards. The GDP2
supports only 30 channels when used in the RXU shelf and/or BSSC2 cabinet.
• XCDRs, GDPs, EGDPs, and GDP2s can co-exist in a shelf.
• The proportion of AMR-capable circuits (GDP2/EGDP) to non AMR-capable circuits

(XCDR/GDP) should be sufficient to handle the expected AMR traffic.
• The master MSI slot(s) should always be populated to enable communication with the OMC-R.
The master MSI slot may contain a XCDR/GDP/EGDP (either the primary or the secondary)
/GDP2, if the OML goes through the MSC.
• The A-interface must terminate on the XCDR/GDP/EGDP (either the primary or the
secondary) /GDP2. A GDP can terminate T1 or E1 links; whereas an XCDR can only terminate
E1 links (refer to T1 conversions below). EGDPs and GDP2s do not support T1s.
• Slot 24 (XCDR 0) in the RXU shelf 0 (master) will be lost if an optional NVM board is required.
68P02900W21-R 7-15
28 Feb 2006 GMR-01
with GDP/GDP2s.
EGDP provisioning
The secondary GDP of an EGDP may use the E1 connection to terminate an Ater link. This reduces the need
for MSIs and makes more efficient use of the available TDM timeslots. Note that the (secondary) GDP has
one E1 interface (instead of two for an MSI), which must be taken into account in site (MSI) planning.
Figure 7-2 and Figure 7-3 show the EGDP used in configurations with and without the additional E1
termination in use respectively.
Figure 7-2 EGDP configuration with the additional E1 termination in use
TDM Bus
Primary
GDP 15
E1 Span
DSPs E1 Span
to MSC
from an RXCDR
15 Secondary to a BSC or from
DSPs GDP a BSC to a BTS
7-16 68P02900W21-R
GMR-01 28 Feb 2006
Figure 7-3 EGDP configuration without the additional E1 termination in use
RXCDR: Static
or dynamic call
connections
Subrate between CICs BSC: Dynamic call
channels for GDP pair connections between
Static carried onto and Ater CICs for a GDP pair
"Pass-thru" the TDM bus channels and Abis channels
connections (TRAU frames (TRAU frames (TRAU frames
(at 64Kbps) using 16Kbps) using 16Kbps) using 16Kbps)
TDM Bus
Primary
GDP
E1 Span
to MSC 15
DSPs
E1 Span
from an RXCDR
MSI to a BSC or from
a BSC to a BTS
Secondary
GDP
15
DSPs
68P02900W21-R 7-17
28 Feb 2006 GMR-01
T1 conversion
T1 to E1 conversion is needed for the XCDR, but not for the GDP. The EGDP and GDP2 do not support
T1 connectivity.
When required, MSI-2s can be used to provide T1 to E1 conversion. This can be done in one of two ways. In
either case the conversion may be part of an existing network element or a standalone network element which
would appear as a RXCDR.
Without KSW switching

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

For better utilization of the GDP/XCDRs a mapping of five T1 circuits onto four E1 circuits may be done.
This uses the ability of the KSW to switch between groups using nailed connections. Although more efficient
in XCDR utilization, this method may cause additional KSWs to be used. Each MSI-2 requires an MSI slot.
The number of MSI-2s needed for T1 to E1 conversion is:
Where: is:
m the number of MSI-2s required
T the number of T1 circuits required.
E the number of E1 circuits required.
7-18 68P02900W21-R
GMR-01 28 Feb 2006
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 XCDR/GDP/EGDP can terminate one E1 link. Each GDP2 can terminate two E1 links (when used in a
RXU3 shelf with enhanced capacity mode enabled (when GDP2s are used)).
The equipment can be mixed within the following formula:
Where: is:
XGE the number of XCDRs, GDPs and
EGDPs.
G2 the number of GDP2s.
NRXCDR-MSC the minimum number of E1 links
required (as N is calculated in
RXCDR to MSC links earlier in
this chapter).
Verify that the number of AMR circuits is sufficient to handle the expected AMR traffic. If necessary
adjust the number of EGDP/GDP2s. The following formula may be used to determine the percentage of
AMR-capable circuits:
In the above equation, count the primary and secondary EGDPs as one EGDP.
Using T1 links
Each GDP card can terminate one T1 link. See T1 conversion (described previously) for XCDR.
68P02900W21-R 7-19
28 Feb 2006 GMR-01
Multiple serial interface (MSI, MSI-2) Chapter 7: RXCDR planning steps and rules
Multiple serial interface (MSI, MSI-2)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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. A MSI can interface only E1 links, an MSI-2 can interface
both E1 and T1 links.
7-20 68P02900W21-R
GMR-01 28 Feb 2006
The following factors should be considered when planning the transcoder complement:
• Each MSI can interface two E1 links.
• Each MSI-2 can interface two E1/T1 links.
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.
• Each E1 link provides 31 usable 64 kbit/s channels.
• Each T1 link provides 24 usable 64 kbit/s channels, T1 links use MSI-2.
• Redundancy for the MSI/MSI-2 depends on the provisioning of redundant E1/T1 links
connected to the site.
• When one remote transcoder site is supporting multiple BSCs, each BSC requires its own E1
interface(s) as follows:
◦ The number of MSI/MSI-2s should be equal to half the number of RXCDR to BSC E1 or
T1 links. Redundancy requires additional links and MSI/MSI-2s.
◦ If the OMLs (X.25 links) do not go through the MSC, a dedicated E1 or T1 link (half an
MSI/MSI-2) is required for the X.25 links to the OMC-R.
◦ 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 Service Manual: BSC/RXCDR (68P02901W38) for more
details.
• The master MSI slot(s) should always be populated to enable communication with OMC-R.
If the OML links go directly to the MSC, the master slot should be filled with a
XCDR/GDP/EGDP (primary or secondary)/GDP2, 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.
68P02900W21-R 7-21
28 Feb 2006 GMR-01
Multiple serial interface (MSI, MSI-2) Chapter 7: RXCDR planning steps and rules
MSI planning actions
With E1 links
Determine the number of MSI or MSI-2s required.
Where: is:
NMSI 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:
Where: is:
If MSIs are used, conversion becomes necessary. Therefore the number of MSIs required is:
Where: is:
m the number of MSI-2s used for T1
to E1 conversion.
7-22 68P02900W21-R
GMR-01 28 Feb 2006
Kiloport switch (KSW) and double kiloport switch

(DSW2)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The KSW/DSW2 provides digital switching for the TDM highway of the RXU.
The double kiloport switch (DSW2) is an enhanced version of the KSW which supports double the number
of ports (enhanced capacity mode), as well as extended subrate switching capability down to 8 kbit/s
(extended subrate switching mode). Use of 8 kbit/s subrate switching can reduce backhaul costs when used in
conjunction with the AMR or {22064} GSM half rate feature.
68P02900W21-R 7-23
28 Feb 2006 GMR-01
Kiloport switch (KSW) and double kiloport switch (DSW2) Chapter 7: RXCDR planning steps and rules
The following factors should be considered when planning the KSW/DSW2 complement:
• A minimum of one KSW/DSW2 is required for each RXU site.
• The KSW, or DSW2 not in enhanced capacity mode, has a capacity of 1024 x 64 kbit/s ports or
4096 x 16 kbit/s ports, which can be expanded by adding up to three additional KSW/DSW2s,
giving a total switching capacity of 4096 x 64 kbit/s ports or 16384 x 16 kbit/s ports.
• When operating in enhanced capacity mode, the DSW2 has a capacity of 2048 x 64 kbit/s ports
or 8196 x 16 kbit/s ports, which can be expanded by adding up to three additional DSW2s,
giving a total switching capacity of 8192 x 64 kbit/s ports or 32768 x 16 kbit/s ports.
• When operating in extended subrate switching mode (but not enhanced capacity mode), the
DSW2 can further switch 8192 x 8 kbit/s ports which can be expanded by adding up to three
additional DSW2s, giving a total switching capacity of 32768 x 8 kbits/s ports.
• When operating in extended subrate switching mode and enhanced capacity mode, the DSW2
can further switch 16384 x 8 kbit/s ports which can be expanded by adding up to three
additional DSW2s, giving a total switching capacity of 65536 x 8 kbits/s ports.
• Eight (64 kbit/s) timeslots per KSW/DSW2 are reserved by the system for test purposes and
are not available for use.
• A mix of KSWs and DSW2s requires that the DSW2s are not operated in the enhanced
capacity mode.
7-24 68P02900W21-R
GMR-01 28 Feb 2006
• For redundancy, duplicate all KSWs/DSW2s. In mixed configurations (KSWs and DSW2s),
KSWs can be redundant to DSW2s and vice-versa.
• Verify that each KSW or DSW2 not in enhanced capacity mode uses no more than 1016 ports,
or that each DSW2 in enhanced capacity mode uses no more than 2040 ports (8 ports are used
internally). The devices in a RXCDR that require TDM timeslots are:
◦ GPROC2 or GPROC3 = 32 (or 16) timeslots.
◦ GDP or XCDR (or GDP2 acting as a GDP replacement) = 16 timeslots.
◦ EGDP = 96 timeslots.
◦ GDP2 = 24 timeslots.
◦ MSI/MSI-2 = 64 timeslots.
The number of TDM timeslots is given by:
Where: is:
N the number of timeslots required.
n 16 or 32 (depending on the value
of the gproc_slots database
parameter).
RGDPXCDR the number of GDPs/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).
68P02900W21-R 7-25
28 Feb 2006 GMR-01
Kiloport switch (KSW) and double kiloport switch (DSW2) Chapter 7: RXCDR planning steps and rules
KSW/DSW2 planning actions
Determine the number of KSWs or DSW2s required.

Use this formula when enhanced capacity mode is not enabled:
Use this formula when enhanced capacity mode is enabled:
Where: is:
N the number of KSWs/DSW2s
required.
parameter).
RGDPXCDR the number of GDPs/XCDRs.
M the number of MSI/MSI-2s (do
not count MSI-2s which are doing
on-board E1 to T1 conversion).
Each KSW/DSW2 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 (or 2040 when operating in enhanced capacity mode).
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/DSW2 in one shelf cannot serve boards in other
expansion shelves.
For example, in the case of a RXCDR consisting of two shelves each having 32 unused timeslots per
KSW/DSW2 free, an additional MSI board CANNOT be added even if a MSI slot is free at each shelf, (but
one GPROC per shelf can be added if one GPROC slot per shelf is free).
7-26 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning RXU shelves
RXU shelves
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The number of RXU shelves is normally a function of the number of MSI/MSI2s and
XCDR/GDP/EGDP/GDP2s required.
68P02900W21-R 7-27
28 Feb 2006 GMR-01
RXU shelves Chapter 7: RXCDR planning steps and rules
The following factors should be considered when planning the number of RXU shelves:
• Each expansion shelf is allocated to a single KSW/DSW2 and shelves are differentiated by the
presence of the KSW/DSW2. Extension shelves are those which do not contain a primary
KSW/DSW2. Shelves containing a KSW/DSW2 are called expansion shelves.
• An extension shelf extends the TDM highway. It is constrained to the same number of
(aggregate) timeslots as the shelf containing the KSW/DSW2.
• An expansion shelf adds an additional TDM highway. It increases the number of timeslots to
that of the additional KSW/DSW2.
• The number of devices that can be served by a KSW/DSW2 is governed by the TDM
timeslot allocation required for each device. This is discussed previously in the KSW/DSW2
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.
• 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 XCDR/GDP/EGDP
(primary or secondary)/GDP2s.
• The RXU3 shelf has connectivity for two E1s per slot. All slots may be used for
XCDR/GDP/EGDP/GDP2s and MSI/MSI-2s.
• The GDP2 can be used to terminate 2 x E1s, (i.e. 60 voice channels) only in the RXU3 shelf
and BSSC3 cabinet (enhanced capacity mode must be enabled to access the second E1 when
GDP2s are used). The current RXU shelf has only one E1 (T1) per transcoder slot, and the
current BSSC2 cabinet does not have space for additional line interface boards. The GDP2
supports only 30 channels when used in the RXU shelf and/or BSSC2 cabinet.
• An NVM board cannot be installed if all the XCDR slots in the RXU shelf 0 (master) are
required.
with GDP/GDP2s.
7-28 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning RXU shelves
RXU shelf planning actions
Determine the number of RXU shelves required using the appropriate formula (fractional values should be
rounded up to the next integer).
For the current generation RXU shelf:
For the new generation RXU3 shelf:
Where: is:
Rx the minimum number of RXU
shelves required.
Rx3 the minimum number of RXU3
shelves required.
M the number of MSI/MSI-2s.
R the number of
XCDR/GDP/EGDP/GDP2s
(see Note).
NNVM the number of optional NVM
boards (0 or 1).
The number of timeslots equipped to each shelf must be verified. Use the appropriate equation given below
to do this.
When enhanced capacity mode is not enabled:
68P02900W21-R 7-29
28 Feb 2006 GMR-01
RXU shelves Chapter 7: RXCDR planning steps and rules
This verification procedure is similar to the one included in the KSW/DSW2 planning considerations section
of this chapter (the KSW/DSW2 timeslot validation will prevent a shelf from exceeding the timeslot limit)
and is repeated here for completeness.
Where: is:
G the number of GPROCs in the
shelf.
parameter).
RGDPXCDR the number of GDP/XCDRs in
the shelf.
REGDP the number of EGDPs in the shelf.
RGDP2 the number of GDP2s in the shelf.
M the number of MSI/MSI-2s in
the shelf (do not count MSI-2s
which are doing on-board E1 to
T1 conversion).
When enhanced capacity mode is enabled (non-extension shelf):
When enhanced capacity mode is enabled (extension shelf):
If the result of using the appropriate equation above exceeds the value quoted, the configuration of MSIs,
GPROCs and GDPs may be adjusted, or an additional shelf or shelves may be required.
7-30 68P02900W21-R
GMR-01 28 Feb 2006
Kiloport switch extender (KSWX) and double kiloport

switch extender (DSWX)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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.
The DSWX performs the same function as the KSWX. It is necessary when enhanced capacity mode (2048
timeslot capability) is used (but not in extended subrate switching mode).
The following factors should be considered when planning the KSWX/DSWX complement:
• KSWXs/DSWXs are not required in a single shelf configuration (that is, when expansion or
extension is not required).
• For redundancy, duplicate all KSWX/DSWX boards (requires redundant KSW/DSW2).

In mixed configurations (KSWXs and DSWXs), KSWXs can be redundant to DSWXs
and vice-versa.
• KSWXs/DSWXs are used in three modes:

◦ KSWX/DSWXE (Expansion) are required to interconnect the KSWs/DSW2s for sites
with multiple KSWs/DSW2s.
◦ KSWX/DSWXR (Remote) are required in shelves with KSWs/DSW2s to drive the TDM
highway in shelves that do not have KSWs/DSW2s.
◦ KSWX/DSWXL (Local) are used in shelves that have KSWs/DSW2s to drive the clock
bus in that shelf and in shelves that do not have KSWs/DSW2s to drive both the local
TDM highway and the clock bus in that shelf.
• Five of the redundant KSWX/DSWX slots are also CLKX slots.
• The maximum number of KSWX/DSWX slots per shelf is 18, nine per KSW/DSW2.
• KSWXs and DSWXs may both be used. However, KSWXs and DSWXs should always be
used with like pairs, i.e. DSWXs with DSWXs and KSWXs with KSWXs (see next point for
an additional restriction).
• Operation in enhanced capacity mode requires the use of all DSWXs (and DSW2s).
68P02900W21-R 7-31
28 Feb 2006 GMR-01
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) Chapter 7: RXCDR planning steps and rules
Variable length fibre optic cables may be used when only DSWX pairs are used at
a transcoder site. This is because the DSWX has an elastic buffer that compensates
for the variable signal delay. The advantage of variable length cables is in the cost
savings of shorter cables between some of the RXU/RXU3 shelves.
KSWX/DSWX planning actions
The number of KSWXs/DSWXs required is the sum of the KSWX/DSWXE, KSWX/DSWXL, and
KSWX/DSWXR.
Where: is:
NKX the number of KSWXsDSWXs
required.
NKXE the number of KSWX/DSWXE.
NKXR the number of KSWX/DSWXR.
NKXL the number of KSWX/DSWXL.
K the number of non-redundant
KSWs/DSW2s.
SE the number of extension shelves.
7-32 68P02900W21-R
GMR-01 28 Feb 2006
For example:
Table 7-2 KSWX/DSWX (non-redundant)
Extension KSW/DSW2 (non redundant)

shelves 1 2 3 4
0 0 4 9 16
1 3 6 11 18
2 5 8 13 20
3 7 10 15 22
4 9 12 17 24
Table 7-3 KSWX/DSWX (redundant)
Extension KSW/DSW2 (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
68P02900W21-R 7-33
28 Feb 2006 GMR-01
Generic clock (GCLK) Chapter 7: RXCDR planning steps and rules
Generic clock (GCLK)

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

GCLKs = 1 + 1 redundant
7-34 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Clock extender (CLKX)
Clock extender (CLKX)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
A clock extender (CLKX) board provides expansion of GCLK timing to more than one RXU.
The following factors should be considered when planning the CLKX complement:
• One CLKX is required in the first RXU shelf, which contains the GCLK, when expansion
beyond the shelf occurs.
• Each CLKX can supply the GCLK signals to six shelves.
• There are three CLKX slots for each GCLK, allowing each GCLK to support up to 18 shelves
(LAN extension only allows fourteen shelves in a single network element).
• The maximum number of CLKX slots per shelf is six.
The CLKX uses six of the redundant KSWX/DSWX slots.
• With a CLKX, a KSWX/DWSXL is required to distribute the clocks in the master and each of
the expansion/extension shelves.
• For redundancy, duplicate each CLKX (requires a redundant GCLK).
68P02900W21-R 7-35
28 Feb 2006 GMR-01
Clock extender (CLKX) Chapter 7: RXCDR planning steps and rules
CLKX planning actions
Determine the number of CLKXs required:
Where: is:
NCLKX the number of CLKXs required.
E the number of shelves.
(1 if redundancy required
(recommended),
7-36 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning LAN extender (LANX)
LAN extender (LANX)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The LANX provides a LAN interconnection for communications between all GPROCs at a site.
The following factors should be considered when planning the LANX complement:
• One LANX is supplied in each shelf.
• For full redundancy add one LANX for each shelf.
• The LANX can support a maximum network size of 14 shelves.
LANX planning actions
Determine the number of LANXs required.
Where: is:
NLANX the number of LANXs required.
NRXU the number of RXU shelves.
(recommended).
RXU ≤ 14
68P02900W21-R 7-37
28 Feb 2006 GMR-01
Parallel interface extender (PIX) Chapter 7: RXCDR planning steps and rules
Parallel interface extender (PIX)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The PIX provides eight inputs and four outputs for site alarms.
The following factors should be considered when planning the PIX complement:
• The maximum number of PIX board slots per shelf is two.
• The maximum number of PIX board slots per site is eight.
PIX planning actions
Determine the number of PIXs required.

PIX ? 2 * number of RXUs
or
PIX ? 8
7-38 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Line interfaces (BIB, T43)
Line interfaces (BIB, T43)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide impedance matching
for E1 and T1 links.
• Use a BIB 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 T43 Board (T43) to match a single-ended 75 ohm 2.37 V (peak pulse) line.
• Each BIB/T43 can interface six E1/T1 links to specific slots on one shelf.
• All E1/T1 links must be terminated, including the links which are fully contained in the
cabinet, for example, between RXU and BSU or links used for T1 to E1 conversion.
• Up to four BIBs or T43s per shelf can be mounted on a BSSC2 cabinet.

◦ A maximum of 24 E1/T1 links can be connected to a RXU shelf.
◦ A BSSC2 cabinet with two RXU shelves can interface 48 E1/T1 links.
• Up to seven BIBs or T43s per shelf can be mounted on a BSSC3 cabinet.

◦ A maximum of 38 E1/T1 links can be connected to a RXU3 shelf.
◦ A BSSC3 cabinet with two RXU3 shelves can interface 76 E1/T1 links.
When fully equipping two RXU3 shelves with 38 E1s each, there will be
four unused E1/T1 links on two of the BIB/T43s.
GDP2s must be used to fully utilize two E1s per slot.
68P02900W21-R 7-39
28 Feb 2006 GMR-01
Line interfaces (BIB, T43) Chapter 7: RXCDR planning steps and rules
BIB/T43 planning actions

• Determine the number and type of link (E1 or T1) to be driven.
• Calculate the number of E1s/T1s to be terminated for each shelf.
• Determine the number of BIBs or T43s required per shelf.
• Sum up across all shelves for the total.
7-40 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Digital shelf power supply
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:
• Two DPSMs are required for each shelf in the BSSC/RXCDR.
• Two IPSMs are required for each shelf in the BSSC2/RXCDR (-48/-60 V dc).
• Two EPSMs are required for each shelf in the BSSC2/RXCDR (+27 V dc).
• For redundancy, add one DPSM, IPSM or EPSM for each shelf.
Power supply planning actions
Determine the number of PSMs required.
Where: is:
(recommended),
68P02900W21-R 7-41
28 Feb 2006 GMR-01
Non volatile memory (NVM) board Chapter 7: RXCDR planning steps and rules
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:
• Only one NVM board can be installed at the RXCDR.
• The NVM board uses slot 24 on the RXU shelf 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.
• 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.
7-42 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Verify the number of RXU shelves and BSSC cabinets
Verify the number of RXU shelves and BSSC

cabinets
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Verification
After planning is complete, verify that:

• Each non-redundant KSW/DSW2 has its own shelf.
• Each extension shelf supports extension of a single KSW/DSW2.
• The number of KSWXs/DSWXs, LANXs, CLKXs, and GPROCs is correct.
If necessary, add extra RXU shelves. Each BSSC cabinet supports two RXU shelves.
68P02900W21-R 7-43
28 Feb 2006 GMR-01
Verify the number of RXU shelves and BSSC cabinets Chapter 7: RXCDR planning steps and rules
7-44 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
8
PCU upgrade for the BSS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following information for the PCU upgrade to the BSS to support GPRS and EGPRS is provided:
• "BSS planning for GPRS/EGPRS" on page 8-2
• "BSS upgrade to support GPRS/EGPRS" on page 8-11
• "PCU hardware layout" on page 8-18
• "PCU shelf (cPCI)" on page 8-20
• "MPROC board" on page 8-22
• "DPROC board" on page 8-23
• "PMC module" on page 8-27
• "Transition module" on page 8-29
• "PCU equipment redundancy and provisioning goals" on page 8-30
• "Multiple (3xPCU) PCUs per BSC" on page 8-38
• "E1 link provisioning for GPRS and EGPRS" on page 8-41
• "{23956} QoS capacity" on page 8-43
• "PCU-SGSN: traffic and signalling planning" on page 8-50
• "BSS-PCU hardware planning example for GPRS" on page 8-58
• "BSS-PCU hardware planning example for EGPRS" on page 8-67
68P02900W21-R 8-1
28 Feb 2006 GMR-01
BSS planning for GPRS/EGPRS Chapter 8: PCU upgrade for the BSS
BSS planning for GPRS/EGPRS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to BSS planning for GPRS/EGPRS
The BSS planning process for GPRS/EGPRS 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/EGPRS part of the network and the
coding schemes used on the air interface.
This section contains planning for both GPRS and EGPRS and notes differences where
appropriate.
The section "GPRS/EGPRS network traffic estimation and key concepts" on page 3-152 in Chapter 3,
"BSS cell planning," is intended to provide the network planner with the rules to determine the number of
GPRS/EGPRS 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-PCU hardware planning example
for GPRS" on page 8-58 and "BSS-PCU hardware planning example for EGPRS" on page 8-67. Its
purpose is to unite the information presented in the entire document from a planning perspective.
8-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS planning for GPRS/EGPRS
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 8-1.
Figure 8-1 Gb interface alternatives
MSC
A INTERFACE
RXCDR Gb OPTION A
Gb OPTION B
OMC-R BSC
FOR OPTION
A and B
SGSN
PCU1
Gb OPTION C
PCU2
Gb OPTION C
PCU3
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.
Up to three PCUs may be connected to the BSC. Option A, B or C may be used independently for each
PCU. Note, however, that each PCU connected to a BSC must be connected to the same SGSN in terms of
the Gb interface.
68P02900W21-R 8-3
28 Feb 2006 GMR-01
Feature compatibility
Alarms consolidation
No additional BSS, GPRS or EGPRS network planning is required.
PCU device alarms impact only PCU functional unit severity, and not the cell functional unit severities.
Therefore, the impact is to the following PCU devices: DPROC and PCU System Processor (PSP).
BSC-BTS dynamic allocation

No additional BSS or GPRS network planning is required.
The dynamic allocation feature specifies how the BSC configures and shares the terrestrial backing between
the GPRS data traffic and the Circuit-Switched (CS) traffic. The terrestrial backing, between the BTS and
BSC, must have enough capacity to carry the radio timeslots assigned to both GPRS and circuit switched.
If there is not enough capacity, 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 and EGPRS feature, that require 32 kbit/s and 64 kbit/s bandwidth {23769} (variable
bandwidth in terms of a configurable rtf_ds0_count if VersaTRAU is unrestricted) respectively on backhaul,
have been designed to work mutually exclusively with the BSC-BTS dynamic allocation feature.
Circuit error rate monitor

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

The addition of GPRS/EGPRS 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/EGPRS 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/EGPRS 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/EGPRS 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/EGPRS timeslots are available in the outer zone carriers.
8-4 68P02900W21-R
GMR-01 28 Feb 2006
Congestion relief
No additional BSS or GPRS/EGPRS network planning is required.
Congestion relief considers switchable GPRS/EGPRS timeslots as idle TCHs.
Cell resource manager dynamic reconfiguration

The Cell Resource Manager (CRM) dynamic reconfiguration feature can use the switchable GPRS/EGPRS
timeslots, but it cannot reconfigure the reserved GPRS/EGPRS timeslots under any circumstances.
Directed retry
The BSC uses directed retry to relieve cell congestion by redistributing traffic across cells. For the
GPRS/EGPRS traffic part of the BSS, the BSC treats switchable GPRS/EGPRS timeslots like idle TCHs.
Emergency call pre-emption

The BSS will be able to configure any GPRS and/or EGPRS timeslot to carry out emergency calls. Should an
emergency call be made within a cell with a GPRS or EGPRS carrier, the BSS will select the air timeslot
that will carry it from the following:
• Idle TCH.
• Switchable GPRS timeslot (from lowest to highest).
• Switchable EGPRS 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:
1. Idle TCH.
2. Switchable GPRS timeslot (from lowest to highest).
3. Switchable EGPRS timeslot (from lowest to highest).
4. In-use TCH.
5. Reserved GPRS timeslot (from lowest to highest).
6. Reserved EGPRS timeslot (from lowest to highest).
7. PBCCH/PCCCH timeslot.
Emergency TCH channels will never be pre-empted.
68P02900W21-R 8-5
28 Feb 2006 GMR-01
Before any EGPRS timeslots are assigned switchable, all GPRS timeslots, if available, will
be assigned to be switchable first.

No additional BSS or GPRS or EGPRS network planning is required.
The extended range cell feature extends the range of a GSM 900 MHz mobile beyond 35 kilometres up to a
maximum range of 121 kilometres (depending on limiting factors). This range extension is not supported
for GPRS or EGPRS carriers.
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/EGPRS timeslots assigned to the uplink and downlink channels must have the same
frequency parameters. GPRS/EGPRS 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 and EGPRS.
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/EGPRS.
Integrated Horizon HDSL interface

No additional BSS, GPRS or EGPRS 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/EGPRS timeslots like idle TCHs in the case of multiband handovers.
Over the air flow control for circuit-switched mobiles

The BSC treats switchable GPRS/EGPRS timeslots like idle TCHs in the case of over the air flow control for
the circuit-switched mobiles feature.
8-6 68P02900W21-R
GMR-01 28 Feb 2006
RTF path fault containment

The BSC may use a switchable GPRS/EGPRS timeslot for a Cell Broadcast CHannel (CBCH) or a Standalone
Dedicated Control 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/EGPRS timeslots that are TCH barred, to SDCCH. The converted
GPRS/EGPRS timeslots are returned to GPRS/EGPRS after the original RTF path fault is cleared.
SMS cell broadcast

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

Seamless cell reselection alleviates heavy performance degradation in the GPRS/EGPRSs system due to
frequent cell reselections by performing the cell change procedure at the RLC/MAC layer rather than at a
higher layer.
68P02900W21-R 8-7
28 Feb 2006 GMR-01
VersaTRAU backhaul
VersaTRAU backhaul feature allows the operator to configure the backhaul required for an EGPRS capable
RTF using the rtf_ds0_count parameter associated with the RTF. This requires planning the backhaul per
RTF based on the number of reserved and switchable timeslots in the cell and expected RF conditions.
Table 8-1 summarizes the recommended VersaTRAU backhaul for a given number of configured PDTCHs per
carrier. The recommendations are based on the achievement of average coding scheme of at least MCS6.
Table 8-1 VersaTRAU backhaul recommendations for a given number of PDTCHs
Recommended aggressive
Number Recommended non-aggressive
VersaTRAU backhaul (average
of PDTCH VersaTRAU backhaul
28 Kbps)
Number of Average Kbps Number of Average Kbps
DS0 (effective MCS) DS0 (effective MCS)
8 4 28 Kbps (MCS5) 5 34 Kbps (MCS6)
Table 8-2 shows the recommended initial settings (non-aggressive in terms of backhaul savings) for the
rtf_ds0_count for an EGPRS RTF when VersaTRAU backhaul feature is unrestricted. The first 2 top
rows show the different initial configurations ranging from 1 PDTCH per carrier to 8 PDTCHs per carrier
(non-BCCH carrier). The first top grey row on of the table shows the number of DS0s constructing the
VersaTRAU frame (Versachannel), the expected throughput and coding scheme with the given VersaTRAU
backhaul. The rows further down the table indicate the number of DS0s constructing the VersaTRAU frame
and throughputs after 1, 2, 3, 4 and 5 TSs are stolen for voice use. In this table, the recommended backhaul for
the Versachannel is conservative, and generally will result in at least MCS6 (if all PDTCHs on the given
carrier are carrying active data transfers at the same time. Higher coding schemes on individual timeslots can
be reached if other timeslots on the carrier are idle due to the benefits of the statistical multiplexing).
Table 8-3 is more aggressive and shows the recommended number of DS0s constructing the VersaTRAU,
which generally will result in at least MCS5.
8-8 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-2 Expected throughput/TS and coding schemes (conservative)
# of PD/carrier 8 7 6 5 4 3 2 1
# DS0 for
VersaTRAU inc. 5 5 5 4 4 4 3 3
voice
VersaTRAU %
38 38 38 50 50 50 63 63
saving vs. Today
# TRAU 5 4 4 3 3 2 1 1
# PDs left 8 7 6 5 4 3 2 1
0
Ave. datarate/TS 34 31 37 33 41 37 28 59
CS used MCS 6 MCS 6 MCS 6 MCS 6 MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 4 4 4 3 2 2 2
# PDs left 7 6 5 4 3 2 1
1
Ave. datarate/TS 31 37 44 41 37 59 59
CS used MCS 6 MCS 6 MCS 6 MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 4 4 4 2 2 1
# PDs left 6 5 4 3 2 1
2
Ave. datarate/TS 37 44 59 37 59 59
CS used MCS 6 MCS 6 MCS 9 MCS 6 MCS 9 MCS 9
# TRAU 4 4 3 2 2
# PDs left 5 4 3 2 1
3
Ave. datarate/TS 44 59 59 59 59
CS used MCS 6 MCS 9 MCS 9 MCS 9 MCS 9
# TRAU 4 3 3 2
# PDs left 4 3 2 1
4
Ave. datarate/TS 59 59 59 59
CS used MCS 9 MCS 9 MCS 9 MCS 9
# TRAU 3 3 3
# PDs left 3 2 1
5
Ave. datarate/TS 59 59 59
CS used MCS9 MCS9 MCS9
68P02900W21-R 8-9
28 Feb 2006 GMR-01
Table 8-3 Expected throughput/TS and coding schemes (aggressive)
# of PD/carrier 8 7 6 5 4 3 2 1
# DS0 for
VersaTRAU inc. 4 4 4 4 4 3 3 3
voice
VersaTRAU %
50 50 50 50 50 63 63 63
saving vs. Today
# TRAU 4 3 3 3 2 2 1 1
# PDs left 8 7 6 5 4 3 2 1
0
Ave. datarate/TS 28 24 28 33 28 37 28 59
CS used MCS 5 MCS 5 MCS 5 MCS 6 MCS 5 MCS 6 MCS 5 MCS 9
# TRAU 3 3 3 3 2 2 2
# PDs left 7 6 5 4 3 2 1
1
Ave. datarate/TS 24 28 33 41 37 59 59
CS used MCS 5 MCS 5 MCS 6 MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 3 3 3 2 2 1
# PDs left 6 5 4 3 2 1
2
Ave. datarate/TS 28 33 41 37 59 59
CS used MCS 5 MCS 6 MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 3 3 2 2 2
# PDs left 5 4 3 2 1
3
Ave. datarate/TS 33 41 37 59 59
CS used MCS 6 MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 3 2 2 2
# PDs left 4 3 2 1
4
Ave. datarate/TS 44 39 59 59
CS used MCS 6 MCS 6 MCS 9 MCS 9
# TRAU 2 2 2
# PDs left 3 2 1
5
Ave. datarate/TS 37 59 59
CS used MCS7 MCS9 MCS9
8-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS upgrade to support GPRS/EGPRS
BSS upgrade to support GPRS/EGPRS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS upgrade provisioning rules
Table 8-4 identifies the BSS network elements that may require upgrading to support GPRS/EGPRS. Consult
the relevant planning information for the chassis-level planning rules covering the BSC, BTS and RXCDR.
The PCU provisioning rules are described later in this chapter.
Table 8-4 BSS upgrade in support of GPRS/EGPRS
Equipment Additional element BSS upgrade

BSC Chassis (optional) Software Add KSWs, LCF
upgrade GPROC2s{25779} /GPROC3s,
BSP GPROC3s, MSIs per BSC
as needed in support of the Gb,
GDS TRAU, GDS LAPD (GSL),
RSL, BSC-BTS traffic carrying
E1 links.
BTS (Horizon II macro, CTU2 Transceiver, with EGPRS enabled CTU2 radios are
Horizonmacro, M-Cell6, EGPRSFirmware upgrade required.
M-Cell2) (M-Cell6 and M-Cell2 require the
CTU Adapter with the CTU2s)
PCU Software upgrade For high capacity PCUs where
more than 24 E1s are needed, it
is necessary to add a second T43
patch panel to the PCUs. The
upgrade kit will include a patch
panel (75Ω or 120Ω) and two
cable management brackets.
OMC-R Software upgrade for EGPRS One per 64 BSS network elements,
support with any mix of circuit or packet
(GPRS) channels supported;
software in support of the PCU.
RXCDR Chassis (optional) Add KSWs, GPROC2s{25779}
/GPROC3s, MSIs per RXCDR as
needed to support the Gb interface
shown as option A in Figure 8-1.
OMC-R planning steps and rules are beyond the scope of this manual.
68P02900W21-R 8-11
28 Feb 2006 GMR-01
BSS upgrade to support GPRS/EGPRS Chapter 8: PCU upgrade for the BSS
Maximum BSS configuration
Table 8-5, Table 8-6 and Table 8-7 provide the recommended maximum BSS network parameter values in
support of GPRS and EGPRS per BSS network element.
8-12 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-5 Recommended maximum BSS parameter values (part A)
Network Element Network Parameter Maximum Value

BSS (BTS) GPRS/EGPRS carriers per cell 12/21*{23769} /24*****
BSS (BTS) Timeslots per carrier (GSM, 8
GPRS and EGPRS)
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 2
BSS (BTS) GPRS/EGPRS timeslots per cell 30
(total of switchable and reserved)
BSS (BSC) PCUs per BSC 3 ***
BSS (PCU) Air interface timeslots processed 240, see Figure 8-3
at any instance in time (with
redundancy)
BSS (PCU) Total air interface timeslots (with 960, see Figure 8-3
redundancy) **
BSS (PCU) Air interface timeslots processed 270, see Figure 8-4
at any instance in time
BSS (PCU) Total air interface timeslots ** 1080, see Figure 8-4
BSS (PCU) Max. TBF per PCU - UL 2700
BSS (PCU) Max. TBF per PCU - DL 2700
BSS (3xPCU) Air interface timeslots processed 720***, see Figure 8-3
at any instance in time (with
redundancy)
BSS (3xPCU) Total air interface timeslots (with 2880*** (1080****) , see
redundancy)** Figure 8-3
BSS (3xPCU) Air interface timeslots processed 810***, see Figure 8-4
at any instance in time
BSS (3xPCU) Total air interface timeslots** 3240*** (1080****), see
Figure 8-4
BSS (3xPCU) Max. TBF - UL 8100
BSS (3xPCU) Max. TBF - DL 8100
68P02900W21-R 8-13
28 Feb 2006 GMR-01
* Maximum when all carriers at a BTS are EGPRS enabled.

** 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.
*** Up to three PCUs (3xPCU) can be managed by the same BSC. The impact on air interface
timeslots is cumulative (i.e. two PCUs in a non-redundant configuration will have 2160 total
timeslots and three PCUs will have 3240.
**** For EGPRS capable systems, the number of air interface timeslots allocated to EGPRS is
limited to 1080. The combination of EGPRS and GPRS air interface timeslots can be greater than
1080 in a 3xPCU configuration, but the impact on BSC interconnect dimensioning should be
taken into consideration.
{23769} ***** If VersaTRAU feature is unrestricted, then the maximum number of carriers
when all carriers at the BTS are EGPRS enabled can be 24.
8-14 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-6 Recommended maximum BSS network parameter values (part B)

PCU Air interface timeslots processing 30 at any instance in time;
(PRP DPROC) per PRP 120 total timeslots.
PCU PCU-SGSN (Gb) interface (GBL) 1 Gb E1 to carry frame relay
(PICP DPROC) channellized or non-channellized
GPRS traffic deployed over the
BSC to PCU interface. The
Gb E1 carries both data and
signalling traffic between the
PCU and SGSN. The utilization
of the Gb should be planned
to not exceed 70%.
PCU Max. PSP MPROCs 2 (for redundancy)
1 (no redundancy)
PCU Max. PICP DPROCs 4
PCU Max. PRP DPROCs 9
PCU Number of cells supported 250
PCU Number of BTS sites supported 100
GSL E1 links Max. physical E1s between BSC 2
& PCU (one primary E1 and one
redundant)
LAPD-type GDS (GSL) links Max. per E1 link (corresponds 30
to a quantity of thirty 64 kbit/s
LAPD channels)
TRAU-type GDS links (E1s) Max. per PCU 18
36*
72**
* Maximum if all supported carriers on the PCU are EGPRS capable. PRPs can support four E1s
when terminating EGPRS timeslots (4 x 9 PRPs = 36 E1s).
** Maximum GDS links when supporting EGPRS carriers for a 3xPCU. This number is less than
3 times a single PCU since the BSC E1 capacity is shared between packet data and voice.
68P02900W21-R 8-15
28 Feb 2006 GMR-01
Table 8-7 Recommended maximum BSS network parameter values (part C)

GBL links (E1s) Max. per PCU 4
12*
20**
Gb PVCs Max. on one bearer Link 318
T43 boards Max. per PCU 4
8***
Cable harnesses To connect 4 x T43 sites 2
Gb frame relay frame octet size Max. 1600 bytes
* Maximum number when EGPRS supported carriers are being employed (12 with 1 PCU,
20 with 3 PCUs).
** Maximum number in a 3xPCU configuration when EGPRS supported carriers are being
employed. This number is less than three times a single PCU since the BSC E1 capacity is
shared between packet data and voice.
*** For high capacity PCUs where more than 24 E1s are needed, it is necessary to add a second
T43 patch panel to the PCUs. {23769} This number is less if VersaTRAU is unrestricted and not
all EGPRS carriers are provisioned with a backhaul of 8 DS0s.
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 part of the
GPRS/EGPRS timeslots for a cell to one PRP and another part of the GPRS/EGPRS timeslots
of the same cell to a different PRP is not supported. (Note that this precludes GPRS/EGPRS
timeslots for a cell to be split between PCUs.) This fragmentation of the cells across PRP
boards may result in not all GPRS/EGPRS 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+EGPRS timeslots in the BSS does not exceed max_GPRS/max_EGPRS TSg, all
GPRS/EGPRS timeslots of all cells will be assigned to a PRP.
max_GPRS/max_EGPRS TSg = (nPRP * 120) - (max_GPRS/max_EGPRS TS_cell - 1)
Where:
max_GPRS/max_EGPRS TSg = maximum number of GPRS/EGPRS 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/EGPRS timeslots in the cell in the BSS with the
most GPRS timeslots.
8-16 68P02900W21-R
GMR-01 28 Feb 2006
E1 cable requirements for a fully configured PCU

Each PCU requires at least one interconnection panel, located on the PCU cabinet, 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.
With EGPRS carriers, there is a potential for a second interconnect panel if the number of E1s is greater than
24. The number of T43 boards in the second interconnect panel is dependant on the number of E1s required.
A cable harness is staged with the PCU containing 18 E1 RJ45 to RJ45 cables.
A second cable harness needs to be caged to hold an extra 6 E1 RJ45 to RJ45 cables.
68P02900W21-R 8-17
28 Feb 2006 GMR-01
PCU hardware layout Chapter 8: PCU upgrade for the BSS
PCU hardware layout

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
There can be up to three PCUs per BSS. Figure 8-2 shows the PCU shelf layout.
Figure 8-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 A O B O O O O O O O
C C C C C C C 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 T T M M M M M M
M M
8-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning PCU hardware layout
Any two of the three available default LAPD link slots may be used.
68P02900W21-R 8-19
28 Feb 2006 GMR-01
PCU shelf (cPCI) Chapter 8: PCU upgrade for the BSS
PCU shelf (cPCI)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The PCU cabinet can hold up to three PCU (cPCI) shelves. Each PCU is connected to only one BSC. When
connecting more than one PCU (up to three) to a BSC, they may reside in the same or different PCU cabinets.
One PCU cabinet can potentially serve up to three BSCs (see "Multiple (3xPCU) PCUs per BSC" on page
8-38 later in this chapter for more information). 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.
8-20 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning PCU shelf (cPCI)
The following factors should be considered when planning the cPCI complement:
• The maximum number of timeslots that can be processed at any instance in time per PCU is
240 in the fully redundant configuration (see Table 8-5 to Table 8-7).
• The maximum number of total timeslots that can be provisioned per PCU is 960 in the fully
redundant configuration (see Table 8-5 to Table 8-7).
• When either of the above limits is reached, consider provisioning another PCU (up to the
maximum of three).
• 3 fan/power supply units per cPCI shelf provide N+1 hot-swap redundancy. A minimum of
2 units required.
• 1 air filter per fan/power supply unit is required. (Maximum of 3 per PCU.)
• 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.
• Each MPROC board requires one bridge board and one transition module for a redundant
MPROC configuration, or if the Web MMI feature is enabled.
• 1 alarm board per PCU is required.
• 1 main circuit breaker panel per PCU is required.
• 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.
Additional T43 modules and interconnect cables are required for the PCU cage to
support 18 GDS TRAU links for GPRS and 36 GDS TRAU links for EGPRS.
68P02900W21-R 8-21
28 Feb 2006 GMR-01
MPROC board Chapter 8: PCU upgrade for the BSS
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.
PSP planning considerations
The MPROC board is used for PSP purposes. The PSP is the PCU system processor, which is a master 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 8-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.
The MPROC card is a Motorola MCP820 microprocessor board with a TMCP700 transition module.
8-22 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning DPROC board
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/EGPRS network traffic
estimation and key concepts" on page 3-152GPRS network traffic estimation and key concepts in
Chapter 3, "BSS cell planning,".
PICP or PRP planning considerations
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 either one or two E1 PMC modules, and with PRP software.
The cPCI shelf supports a total of 16 cards. The redundancy MPROC boards with bridge capability occupy
for slots, leaving 12 slots for PICPs or PRPs.
For system availability reasons, PICPs and PRP boards should be evenly distributed between the two
backplanes within the PCU shelf. The PICP/PCP provisioned boards should be populated from left to right.
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:
• The PCU can support up to six PICP boards but the recommended maximum for most
configurations is four. Configuring more than four PICPs per PCU would normally require
multiple PCUs.
• A PICP board supports a maximum of two PMC modules.
• The PICP boards can terminate the following links: LAPD-Type GDS links (GSL), and
Gb links (GBL).
68P02900W21-R 8-23
28 Feb 2006 GMR-01
DPROC board Chapter 8: PCU upgrade for the BSS
PRP board
The following factors should be considered when planning the PRP board complement:
• The PCU can support up to 10 PRP boards with the recommended maximum being 9 PRP
boards. When 9 PRP boards are populated, there are three slots available for PICP boards.
• PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module for GPRS and two
GDS TRAU E1s when configured exclusively with EGPRS carriers, but cannot terminate GDS
LAPD E1 links (GSL) or Gb E1 links (GBL).
• Each PRP board must terminate at least one GDS TRAU E1. A PRP board that does not
terminate any GDS TRAU E1s has no function.
• Up to 120 air timeslots can be terminated on one PRP.
• The maximum number of air timeslots that can be assigned to a PRP is 120. The number
of air timeslots that can be served at a given time interval is 30. The timeslot assignment to
available PRP is load balanced by software which attempts to equally distribute the timeslots
across PRPs.
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.
• A PRP board supports up to two PMC modules.
PRP planning
The general guidelines dictate the maximum capacity of the PRP at 120 MS and/or 120 TS per board.
There are two key statistics, CPU_Usage, and PRP_LOAD, which further help in optimizing the PRP
planning. These statistics are collected for an extended amount of time (representative of peak hour, during
holidays, and such) such that the traffic patterns can be studied and the PRP planning can be optimized.
CPU usage
Observing the CPU utilization of all PRPs in the PCU is an important avenue in determining whether the
boards are overloaded. In a system with multiple PRPs the load shall be generally balanced across all PRPs
and the CPU utilization should be similar as well. The general rule is to consider adding a PRP in a PCU if the
CPU utilization on any of the PRPs exceeds 80% during peak hours on consistent basis.
This statistics reports 3 values for a given time interval - MIN, MAX and MEAN. Although the MAX value
can reach 100% (for a fraction of a second at a time) this should never be used as the criteria for the load
on the board. In fact, the MEAN value should be the only indicative of the PRP utilization. In addition,
several days’ worth of data (or even weeks) shall be considered in order to make a consistent decision. CPU
utilization plots vs. time can help observe a pattern in increased CPU utilization.
PRP load (modifed per service pack 1670.27t1)
8-24 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning DPROC board
This statistic can be instrumental to determine the actual load on the PRP and help the planner further
understand the traffic patterns in the system. For instance, when the majority of the GPRS traffic is signaling
(primarily attach/detach, PDP Context Act/Deact, Cell Update and RAUs) the PRP_LOAD is expected to
be low. A PRP handling GPRS signaling traffic exclusively is expected to produce a PRP_LOAD value
ranges 5-10. However, the PRP_LOAD will be higher when the PRP is handling actual data transfer
(WAPs, FTPs, and so foth).
This statistic reports a MEAN value by default, but it is important to configure the individual bins to get a
finer resolution on the traffic in order to determine a change of traffic volume over time.
when QoS is critical. A MEAN value greater than 100 implies that more than 30 TS are pending service,
which generally will mean the end-user is seeing non-optimal throughput. This is optimal for networks that
allow some PDTCH congestion level at the cells (see DL_PDTCH_CONGESTION statistics). However,
PRP_LOAD MEAN figures of 101-160 can be acceptable provided the traffic density per PDTCH on a cell
level is moderate. A traffic density per PDTCH is considered moderate when DL_PDTCH_CONGESTION is
low (less than 30% of the time). In this scenario a multi-slot mobile will still see good throughputs.
For a MEAN PRP_LOAD exceeding 160, it is recommended to consider adding a PRP. Maintaining a MEAN
PRP_LOAD over 160 will result in poor throughput for the end-users as well as the trigger of rebalancing
of cells across PRPs.
PDTCH planning
The general guidelines for a new network are to configure at least 4 PDTCH/cell on the BCCCH carrier, in
order to optimize the throughput of multi-slot mobiles capable of 4 TS on the DL (downlink)..
Configuring more than 4 TS/cell normally assumes the expectancy of high volumes of actual data traffic and
the planning guidelines already discussed in this chapter (Chapter 3 - Cell Planning) shall apply. However, if
the planner incurs mostly signaling traffic (attaches/detaches, PDP Context Act/Deact, Cell Updates, RAUs),
he/she needs to monitor several statistics to determine whether the addition of PDTCHs in a cell is required.
In networks where GPRS subscriber base is widely enabled but the general data usage per subscriber is low,
special consideration is required. To help determine the PDTCH requirements for a cell, the following
statistics shall be considered.
DL_BUSY_PDTCH
This statistic measures the MEAN, MAX and MIN number of occupied PDTCH carrying downlink packet
traffic. Normally, observing the MEAN value should be indicative of how the PDTCHs are utilized in the cell.
For a more detailed PDTCH occupancy distribution, this statistics can also be configured to report 10 bins. By
default, bin 0 is pegged every block period (20 ms) when no TBFs are allocated on any of PDTCHs on the
cell. Bin 1 is pegged when 1-2 PDTCHs are busy; bin 2 is pegged when 3-4 PDTCHs are busy, etc.
For example, a cell configured with 10 PDTCHs, with a MEAN value reported as 9.2 implies that all 10
configured PDTCHs are being utilized and warrants a further look at the DL_PDTCH_CONGESTION
statistic. However, if the MEAN is 5 implies that the configured PDTCHs are probably underutilized and
the number of PDTCHs can be reduced. Before reducing the number of PDTCHs, other statistics shall be
evaluated first.
AVAILABLE_PDTCH
This statistic should help the planner optimize the number of switchable vs. reserved TSs in a cell. If the busy
hour of voice traffic does not interleave with GPRS busy hour, some TS may be configured as switchable,
carrying voice traffic during CS busy hour and data traffic during GPRS busy hour.
68P02900W21-R 8-25
28 Feb 2006 GMR-01
DPROC board Chapter 8: PCU upgrade for the BSS
Example:
• 8 of 10 TSs are configured as switchable in a cell
• DL_PDTCH_CONGESTION reports high levels of congestion (more than 30%)
• The DL_BUSY_PDTCH reports a MEAN of 5 This example illustrates a condition whereby

TS are stolen
This example illustrates a condition whereby TS are stolen to handle voice traffic and therefore requires the
addition of TSs to this cell to handle the GPRS traffic.
MS_CLASS_1_10_REQ
This statistic can help determine the average number of TS used by the average mobile on the DL and UL and
hence provide an indication to the planner on what kind of throughput the end user may expect.
For example, a class 10 mobile (capable of 4 DL and 2 UL TS) will expect to see high throughputs.
NO_PDTCH_AVAIL
This statistic is pegged in extreme conditions when the last switchable TS is stolen for a voice call. This
condition shall warrant the planner that GPRS service is not available at this time on the cell and probably
requires a reconfiguration of switchable vs. reserved TS, or alternatively the addition of TS in the cell.
DL_PDTCH_CONGESTION
This statistic is pegged when the average traffic density in a cell exceeds 2 MS/PDTCH. Although each
PDTCH can interleave up to 4 MS, it is not the recommended traffic density. The congestion level in a cell is
measured every block period (20 ms) but the statistic is pegged every 8 seconds (400 block periods) when
the mean is calculated to determine whether the cell was congested. If the mean exceeds 2 MS/TS, it is
determined the cell was congested during the last 8 seconds. The value reported by this statistic represents the
accumulated time (in ms) that the cell was congested. It is recommended that the total time a cell is congested
do not exceed 30% of the busy hour time interval. Considering a 30 minutes statistics time interval, this
translates to 10 minutes (value of 30000).
When the majority of the GPRS traffic (higher than 90%) is known to be signaling, the planner may consider
to allow a congestion level of up to 50% of the busy hour statistics time interval. Keep in mind, that under
this level of congestion and if the intended PRP_LOAD is already high (<100), those 10% of subscriber
that attempt to transfer data may experience throughput degradation.
GBL_DL_DATA_THRPUT
The planner shall compare this statistic with the SGSN statistic to determine the actual data sent across the
network that does not result from signaling traffic.
8-26 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning PMC module
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:
• Each PRP board requires at least one PMC module.
• Each PICP board has up to two PMC modules.
• TRAU-type GDS terminate to a PMC module on a PRP board.
• LAPD-type GDS (GSL), Gb E1 (GBL) links terminate to a PMC module on PICP board
and cannot share a PMC module.
• For GPRS, 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. For EGPRS, the PRP can support two
PMC modules when configured with EGPRS air timeslots each with up to two TRAU-type
GDS links.
• Up to two Gb E1 links (GBL) per PMC module are allowed.
• Up to two LAPD-type GDS E1 (GSL) links per PMC module are allowed.
• On the PMC NIB, the PCU can support an arbitrary mixture of 124-16kbps TRAU, 62-32kbps
TRAU and 62-64kbps {23769} (each individual DS0 that is part of a Versachannel is a single
64kbps TRAU channel) TRAU such that the following equation is satisfied:
{23769}
For VersaTRAU carriers (pkt_radio_type = 3), there is no one-to-one correlation between the number of
air timeslots and the number of DS0s required on the backhaul so the number of DS0s should be used
in the above equation.
68P02900W21-R 8-27
28 Feb 2006 GMR-01
PMC module Chapter 8: PCU upgrade for the BSS
The PMC NIB has sufficient CPU capacity to support a 124-16kbps TRAU or one full span. Since 32kbps
TRAU is actually composed of two 16kbps TRAU channels, the PMC NIB can support half as many 32kbps
TRAU, or one full span. With the channellized subrate insert/extraction removed in the 64kbps {23769}
(VersaTRAU) TRAU, the PMC NIB can achieve twice as much bandwidth, which is 62 of the 64kbps TRAU
channels, or two full spans of 64kbps TRAU. The PMC NIB can support an arbitrary mix of 16kbps and
64kbps {23769} (VersaTRAU) TRAU channels, or channels with channellized subrate insertion/extraction
and those without, trading off at a ratio of two 16kbps timeslots to one 64kbps timeslot. Note that when mixed
traffic is used, the two spans on the PMC NIB are not both fully utilized.
8-28 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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:
• One transition module is required per PRP board.
• One transition module is required per PICP board.
68P02900W21-R 8-29
28 Feb 2006 GMR-01
PCU equipment redundancy and provisioning goals Chapter 8: PCU upgrade for the BSS
PCU equipment redundancy and provisioning goals

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Support for equipment redundancy
The PCU supports four types of redundancy:

• 2N
1 MPROC/bridge board pair non-redundant, 2 MPROC/bridge board pairs redundant.
• N+1
2 PS/FAN units non-redundant, 3 PS/FAN unit redundant.
• Load Shared
The signalling data on the GSL and GBL are load shared across the available links.
Provisioning more links than is required in the event of a failure creates seamless redundancy.
The GSL and GBL use a routing algorithm to dynamically balance the load across all available
links. The individual GSL and GBL links can be distributed across the available PICPs. In the
event of a PICP failure the remaining PICP(s) if equipped will process the signalling load.
• Load Balanced
The air timeslots on the GDS links are terminated on a PRP board. A PRP board can be assigned
up to 120 air timeslots. The PCU will automatically balance the number of air timeslots across
the available PRPs. In the event of a GDS link failure, the BSC and PCU will attempt to move
the air timeslots to another available GDS link. In the event of a PRP failure, all of the air
timeslots on the failed PRP will be moved to other PRPs if adequate resources are available.
PCU equipment redundancy planning
For redundant PCU operation, the PCU should be planned such that there are sufficient boards provisioned as
shown in Figure 8-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 extra capacity to provide
redundancy in the event of a PRP or PCIP failure. The third PICP board provides redundancy for the software
processes that run on the first two PICP boards.
The GDS TRAU E1 (GDS) link redundancy is obtained by calculating the number of PRP boards required and
then adding an additional PRP board. The GSL E1 link redundancy is obtained by provisioning a second GSL
E1. The PCU load-balances across the 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 (GBL) 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 number of
GBLs is increased to 12 per PCU and 20 for 3xPCU when EGPRS carriers are equipped.
8-30 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning PCU equipment redundancy and provisioning goals
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 Figure 8-3/Figure 8-4, 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 Figure 8-3 and Figure 8-4.
The PCU architecture offers the network planner a considerable degree of provisioning flexibility. Figure 8-3
and Figure 8-4 demonstrate this flexibility where the provisioning goals may range from full redundancy (as
shown in Figure 8-3) to maximum coverage (as shown in Figure 8-4 for GPRS and Figure 8-5 for EGPRS).
68P02900W21-R 8-31
28 Feb 2006 GMR-01
Table 8-8 summarizes the provisioning goals demonstrated with Figure 8-3, Figure 8-4 and Figure 8-5.
Figure 8-3 GPRS maximum throughput and coverage, fully redundant configuration
124 @ 16k / GDS TRAU

CHANNELS
PCU HARDWARE
GDS PRP1
BSC PMC SGSN
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
GDS
PMC PRP2
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
TO
GDS PRP8
PMC
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
REDUNDANT
GDS PRP9
PMC
REDUNDANT REDUNDANT
GDS 120 TS MAX. 30
PMC TS MAX. ACTIVE
GSL PMC PICP1
PMC 30 LAPD
TS MAX.
GBL
REDUNDANT
GSL GBL
PMC PICP2
30 LAPD
PMC TS MAX. REDUNDANT
GBL
PMC
PICP3
REDUNDANT
PMC
REDUNDANT
GBL
8-32 68P02900W21-R
GMR-01 28 Feb 2006
Refer to Table 8-8 for a matrix of provisioning goals achieved with this instance of PCU provisioning.
Figure 8-4 GPRS maximum throughput and coverage, full redundancy not required

CHANNELS PCU HARDWARE
GDS PRP1
BSC PMC SGSN
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
GDS
PMC PRP2
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
TO
GDS PRP9
PMC
120 TS MAX. 30
GDS TS MAX. ACTIVE
PMC
GSL PMC PICP1
30 LAPD
PMC TS MAX.
GBL
REDUNDANT
GSL GBL
PMC PICP2
30 LAPD
PMC TS MAX. REDUNDANT
GBLs
68P02900W21-R 8-33
28 Feb 2006 GMR-01
Figure 8-4 shows18 GDSs, as required for CS3/CS4. Only 9 GDSs are required for CS1/CS2.
Figure 8-5 EGPRS maximum throughput and coverage, full redundancy not required

CHANNELS
PCU HARDWARE
GDS
BSC PMC1 SGSN
EGPRS
PRP1
120 TS MAX.
PMC2
GDS
EGPRS
PMC1 PRP2
120 TS MAX.
PMC2
TO
GDS
EGPRS
PMC1 PRP8
120 TS MAX.
PMC2
GDS
PMC1
EGPRS
PRP9
120 TS MAX.
PMC2
GSL PMC1
PICP1
30 LAPD TS
PMC2
GBL
GSL
PMC1
PICP2
30 LAPD TS
PMC2
GBL
PMC1
PICP3
PMC2
GBL
8-34 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-8 Provisioning goals (per PCU)
Metric Goal
GPRS maximum GPRS maximum EGPRS maximum

coverage with coverage, redundancy coverage, redundancy
redundant configuration not required (Figure 8-4) not required (Figure 8-5)
(Figure 8-3)
Number of timeslots 240 270 270
processed at any instance
in time
Total number of 960 1080 1080
provisioned timeslots
at a BSS
No. MPROCs 2 1 1
No. PRPs 8 9 9
No. PICPs 3 2 3
No. TRAU-Type GDS 18 18 36{23769} **
E1s
No. LAPD-Type GDS 2 2 2
(GSL) E1s
No. Gb E1s 4 4 9
MPROC board Yes No No
redundancy
PRP board redundancy Yes No No*
PICP board redundancy Yes No No*
GDS TRAU E1 Yes No No*
redundancy
GSL E1 redundancy Yes Yes Yes
Gb E1 redundancy Yes Yes Yes
* Capacity will not meet calculated maximums in the event of a failure. This may or may not
affect customer usage dependant on the current load of the system.
{23769} ** The maximum number of GDS resources may be less if VersaTRAU is unrestricted
and EGPRS carriers are equipped with less than 8 DS0s of backing on the backhaul.
68P02900W21-R 8-35
28 Feb 2006 GMR-01
Upgrading the PCU
The PCU may be incrementally upgraded for additional capacity, by adding one PRP board and by one PICP
board at a time. Table 8-9 shows different upgrade scenarios based on the number of timeslots supported
and redundancy required. The actual number of boards and links required is based upon the formulas
in this chapter.
Table 8-9 shows maximum configurations for EGPRS.
8-36 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-9 Upgrade scenarios
No. of
No. of No. of No. of No. of No. of Total
air times-
PRP PICP GDS GBL GSL links
lots*
120 1 1 4 2 2 8 Min. con-
fig., no re-
dundancy
240 2 1 8 2 2 12 No Gb re-
dundancy
240 2 2 8 6 2 16 w/
redundant
links
360 3 2 12 6 2 20 w/
redundant
links
480 4 2 16 6 2 24 w/
redundant
links
600 5 1 20 2 2 24 No Gb re-
dundancy
600 5 2 20 6 2 28 w/
redundant
links
720 6 3 24 10 2 36 w/
redundant
links
840 7 3 28 10 2 40 w/
redundant
links
960 8 3 32 10 2 44 w/
redundant
links
1080 9 3 36 10 2 48 w/
redundant
links
* All air timeslots are assumed to be EGPRS capable {23769} and assumed to have a backing
on the backhaul of 64kbps/air timeslot. If VersaTRAU is unrestricted, the number of GDS
resources will be between 18 and 36 and will depend on the number of DS0s equipped for
each EGPRS RTF on the backhaul.
68P02900W21-R 8-37
28 Feb 2006 GMR-01
Multiple (3xPCU) PCUs per BSC Chapter 8: PCU upgrade for the BSS
Multiple (3xPCU) PCUs per BSC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to multiple PCUs
Up to three PCUs may be connected to a BSC for additional capacity. PCU shelves may be added to a BSC at
any time. PCU shelves may be added for redundancy as well as capacity. With this increase in the number
of PCUs, the amount of GPRS traffic may increase by 3x per BSC.
No new hardware components are necessary at the PCU. The BSC may require additional MSI cards and/or
LCF GPROCs to support connectivity to the additional PCU shelves.
All PCU shelves connected to a BSS are managed by the same OMC-R.
The following factors should be considered when adding PCUs to a BSC:

• Each of the PCUs must connect to the same SGSN.
• All GPRS channels at a cell (one sector of a BTS site) must reside on the same PCU shelf.
• An additional PCU is required when either of the following conditions exist:

◦ The number of air interface timeslots exceeds the per PCU limit.
◦ The number of expected active air interface timeslots exceeds the per PCU limit.
• When adding a PCU shelf ,one or more cells may need to be migrated (by the operator) from
one PCU shelf to another to balance the anticipated traffic load.
• Redundancy is provided for when more than one PCU is equipped. For each PCU, a first
and second redundant (if 3 PCUs equipped) PCU mapping can be set (when redundancy is
enabled). During recovery from certain fault conditions that render a PCU inoperable, cells
may be remapped to the next redundant PCU.
8-38 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Multiple (3xPCU) PCUs per BSC
PCU example configurations
Figure 8-6 demonstrates some of the various physical configurations that are supported. The actual
configuration employed will likely contain more BSCs and PCU cabinets than illustrated. The intention of
Figure 8-6 and the supporting text (below) is to provide a brief summary of the types of configurations
supported.
Figure 8-6 (a) illustrates a common one PCU per BSC configuration.
Figure 8-6 (b) illustrates a configuration that has anticipated expansion for all of the BSCs and PCUs and has
elected to keep all PCUs associated with a BSC in a single cabinet. This configuration might be ideal for
purposes of operations and maintenance but may initially be considered costly because shelves may remain
unoccupied until the capacity and availability is needed.
Figure 8-6 (c) illustrates a very likely configuration. This assumes an initial configuration of (a). As the
GPRS traffic increases and equipment is added, additional PCU shelves are added and connected to the BSC.
In this case, BSCa expanded first and required two additional shelves in cabinet 2. Then BSCb expanded and
also required two additional shelves. One of these shelves is in cabinet 2. The other PCU shelf is in cabinet 3.
Then BSCc expanded and filled out the remaining shelves in cabinet 3.
68P02900W21-R 8-39
28 Feb 2006 GMR-01
Multiple (3xPCU) PCUs per BSC Chapter 8: PCU upgrade for the BSS
Figure 8-6 (d) illustrates a configuration that has some benefits in expansion cost but yet provides some direct
correlation between shelf location and the BSC. In this case, BSCa requires more traffic and an additional
PCU shelf. A PCU cabinet is installed but shelves are reserved for BSCb and BSCc in anticipation of future
growth. Later, cabinet 3 is installed and populated the same as the other PCU cabinets.
Figure 8-6 PCU example configurations
PCUa
BSCa PCUb
PCUc
Cabinet 1
BSCa
PCUa PCUa
BSCb PCUb SGSN BSCb PCUb SGSN
PCUc PCUc
BSCc
Cabinet 1 Cabinet 2
(a) Current PCUa

BSCc PCUb
PCUc
Cabinet 3
(b) High initial cost / best maintenance
PCUa PCUa
BSCa PCUb BSCa PCUb
PCUc PCUc
Cabinet 1 Cabinet 1
PCUa PCUa
BSCb PCUb SGSN BSCb PCUb SGSN
PCUc PCUc
Cabinet 2 Cabinet 2
PCUa PCUa
BSCc PCUb BSCc PCUb
PCUc PCUc
Cabinet 3 Cabinet 3
(c) Most likely (d) Cabinet cost and maintenance considered
8-40 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning E1 link provisioning for GPRS and EGPRS
E1 link provisioning for GPRS and EGPRS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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
On the PMC NIB, the PCU can support an arbitary mixture of 124-16kbps TRAU, 62-32kbps TRAU and
62-64kbps {23769} (VersaTRAU DS0s) TRAU such that the following equation is satisfied:
{23769}
PCU GDS E1
• There may be up to 18 TRAU-type GDS E1 links per PCU for GPRS.
• There may be up to 36 TRAU-type GDS E1 links per PCU for EGPRS.
GSL LAPD (GSL) E1

The GSL traffic is load balanced over all GSLs. The first E1 carries up to 30 LAPD links and the second E1
up to another 30. 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.
GPROC LCF
The GPROC LCFs available at the BSC terminate up to 12 LAPD channels. Up to 60 LAPD-type links may
be provisioned at the PCU, for a total of 180 (for three PCUs). The LAPD links may be distributed on the
LCF automatically, based on the capacity available on the LCFs.
68P02900W21-R 8-41
28 Feb 2006 GMR-01
E1 link provisioning for GPRS and EGPRS Chapter 8: PCU upgrade for the BSS
Either the GPROC2 or the GPROC3 can perform LAPD-type link processing.
PCU Gb E1 (GBL)
• There may be up to 4 Gb E1s per PCU for GPRS.
• There may be up to 12 Gb E1s per PCU for EGPRS.
8-42 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning {23956} QoS capacity
{23956} QoS capacity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The QoS feature retains the 120 mobile per PRP board limit from previous releases, however, this feature can
affect the overall capacity of the PRP board. Each PRP board has a capacity in terms of MTBR. When that
capacity is reached, no more non-STNNT mobiles or PFCs can be admitted without preempting other PFCs
first. There is a trade-off between the number of mobiles being serviced and the MTBR of the PFCs of the
mobiles being serviced. If the MTBR of the various traffic classes are set to high values, or there are multiple
PFCs per mobile, fewer mobiles will be able to be serviced per PRP board.
A simple example is when there is only 1 GPRS timeslot equipped and in-service and a high ARP Rank PFC
is allocated a single timeslot of MTBR (calculated from coding scheme and MTBR) for its use. Additional
non-STNNT PFCs of equal or lower ARP Rank cannot be assigned to that timeslot without compromising the
service of the first high ARP Ranked PFC and are subsequently rejected. Four mobiles will be allowed to be
allocated on each PDTCH provided there is sufficient available throughput to do so.
When the BSS is managing its pool of MTBR resources, it reserves headroom, that is, it does not allocate
100% of its resources in terms of MTBR commitments. The purpose of the headroom is to reserve some
throughput in the system so that each PFC has a high probability of meeting its MTBR regardless of coding
scheme changes and to allow short term PFCs (such as PAP and STNNT) to enter the system.
The headroom is managed on two distinct levels:
• The first level of headroom is at local timeslot zone. The BSS reserves headroom within a local
zone of timeslots such that coding scheme changes by any mobile within that local zone of
timeslots, or addition of a STNNT or PAP mobile to that local zone of timeslots, will not affect
the ability of the mobiles within that local zone of timeslot to meet their MTBR requirements.
• The second level of headroom is at the PRP board. This is headroom on the PRP board’s ability
to service 30 timeslots per block period of throughput. Some of this throughput is reserved
for coding scheme changes and STNNT and PAP mobiles.
When admitting a new mobile, the BSS verifies that there is sufficient headroom at both of these levels. If
there is insufficient headroom to admit the new mobile, other mobiles may be downgraded and/or pre-empted
and the requesting mobile may also be downgraded or rejected.
The amount of MTBR throughput that is available on each timeslot to commit to the mobiles is a function
of the number of mobiles scheduled on that timeslot. In the maximum case, 8 kbps of MTBR can be
allocated for GPRS and 14 kbps for EGPRS per timeslot. This maximum value is used for all the capacity
calculations below.
To determine the overall MTBR capacity of a PRP board, both levels of headroom must be considered. The
most constricting of these levels of headroom determines the overall capacity of the PRP board. Table 8-10
shows the summation of the headroom of all of the local timeslot zones on a PRP board for the downlink and
the uplink as well as the corresponding summation of the MTBR throughputs (or committable throughput) of
all of the timeslot zones on the PRP board. It is important to note, that for these calculations it is assumed
there are multislot class 1 mobiles (each using a single uplink and downlink timeslot) and 4 mobiles scheduled
per timeslot (allowing 8kbps committable bandwidth per slot). Note that the local timeslot zone headroom is
a function of the coding scheme in use but the MTBR throughput of the PRP board is independent of the
coding schemes used.
68P02900W21-R 8-43
28 Feb 2006 GMR-01
{23956} QoS capacity Chapter 8: PCU upgrade for the BSS
Table 8-10 takes the coding schemes allowed on a timeslot (for all timeslots) and calculates a Local Timeslot
Zone Level MTBR throughput summed over all timeslots equipped on the board. By dividing the summation
of the local timeslot zones (the available MTBR commitment) by the commitment made to each mobile (2
Kbps) the theoretical limitation based on this restriction is calculated. It is clear from this example that the
Local Timeslot Zone Level Headroom, when there are 120 timeslots equipped on the board and mobiles
with only 1 timeslot and 2 Kbps MTBR requirements, will not be the restricting factor as the 120 mobile per
board restriction is more constraining.
Table 8-10 Local Timeslot Zone Level capacity 4MS/PDTCH
Coding scheme CS-1/2 CS-3/4 EGPRS

Peak throughput per TS (bps) 12000 20000 59200
Local timeslot zone MTBR throughput per TS (bps) 8000 8000 8000
Local timeslot zone total headroom (%) 33.3 60.0 86.5
Number of timeslots equipped 120 120 120
Summation of local timeslot zone level MTBR 960000 960000 960000
throughput over PRP (bps)
Theoretical limitation based solely on local timeslot 480 480 480
zone restriction Max MS @ 2 kbps/MS
Local timeslot zone Max MS @ 2 kbps/MS 120 120 120
Table 8-11 shows the PRP board service headroom and corresponding PRP board service level MTBR
throughput. The PRP board service headroom and corresponding PRP board service throughputs are both
a function of the actual coding schemes of the mobiles on the board at the moment, (that is, the MTBR or
committable throughput of the board is higher when higher coding schemes are in use on the board). It is
important to note that for these calculations it is assumed there are multislot class 1 mobiles (each using a
single uplink and downlink timeslot) and 4 mobiles scheduled per timeslot (allowing 8kbps committable
bandwidth per slot). Note, CS-1 is the worst case.
Table 8-11 PRP Board Service Level Capacity 4MS/PDTCH
Coding scheme CS-1 CS-1/2 CS-3/4 EGPRS
Peak throughput per TS (bps) 8000 11200 15360 25120

Local timeslot zone MTBR throughput 30 30 30 30
per TS (bps)
Local timeslot zone total headroom (%) 240000 336000 460800 753600
Number of timeslots equipped 16.7 16.7 16.7 16.7
Summation of local timeslot zone level 200000 280000 384000 628000
MTBR throughput over PRP (bps)
Theoretical limitation based solely on 100 140 192 314
local timeslot zone restriction Max MS
@ 2 kbps/MS
Local timeslot zone Max MS @ 2 100 120 120 120
kbps/MS
8-44 68P02900W21-R
GMR-01 28 Feb 2006
Table 8-11 takes the current throughput per timeslot and calculates a PRP board service level MTBR based
on the requisite headroom. By dividing the PRP Board Service level MTBR throughput (the maximum
committable bandwidth) by the commitment per mobile (2 Kbps MTBR) a theoretical maximum limitation is
calculated. In all but the worst case scenario (all mobiles experiencing CS-1) the board level Service Capacity
is not the limiting factor in the number of mobiles supported per board. The 120 mobile per board limit is
the constraining factor in all but the worst case.
When looking at overall PRP capacity, the PRP service level headroom will usually limit the number of
mobiles on the PRP board. (that is, as long as there are multiple cells on the PRP board). For example, if the
MTBR is set to 6 kbps in both uplink and downlink for all traffic classes, interleaving is limited to one mobile
per timeslot in the uplink and interleaving is limited to mobiles with multiple slots in the downlink. At the
timeslot zone level 120 mobiles are allowed onto the PRP board. However, at the PRP board service level, in
the worst case (all CS-1) only 30 mobiles can be admitted to the PRP board. With a mix of 20% CS-1 and 80%
CS-2, 70 mobiles can be admitted. With 20% CS-1, 40% CS-3 and 40% CS-4, 60 mobiles can be admitted.
MTBR allocation philosophy
The BSS attempts to maintain its MTBR commitments to PFCs in order of priority by ARP Rank. In other
words, PFCs of a higher ARP Rank are more likely to get access to the system and get their requested MTBR.
The BSS attempts to ensure the ARP Rank ordering of MTBR commitments via downgrading and pre-emption.
Per timeslot commitment

The BSS commits a maximum of 6 kbps of MTBR in the downlink and in the uplink per timeslot on the
air interface when there are less than four mobiles allocated on the timeslot. This maximum commitment
per timeslot is independent of the type of backhaul or the current coding schemes of the mobiles. The
remaining throughput on the timeslot above the commitment is headroom and is allocated to the mobiles
according to their THP weights. For timeslots that are configured as PCCCH timeslots, the BSS commits 0
kbps of MTBR on that timeslot. PCCCH timeslots share both user data and control signalling. Therefore
the BSS does not make any MTBR commitments on the PCCCH timeslot. There could be a large amount
of control signalling transmitting (which is higher priority than user data) that would not allow the BSS to
maintain MTBR on this timeslot.
In order to admit 4 mobiles per timeslot (required to satisfy 120 mobiles per PRP board), some of the
headroom on each timeslot may be used to admit a fourth mobile on to a timeslot, effectively increasing the
committable bandwidth on that timeslot to 8 kbps. This increase only occurs to admit a fourth mobile and is
not done for any other number of mobiles on the timeslot, as using this headroom may allow individual PFCs
to operate further from prescribed MTBR within the tolerance band, as dictated by PDAK polling rates.
This timeslot MTBR commitment forms the basis for the MTBR allocation philosophy. This is a somewhat
conservative approach to making MTBR commitments. It is driven by the headroom, which allows the MTBR
commitments to be maintained regardless of any coding scheme changes made by the mobile.
Each traffic class has an associated MTBR that is configurable by the operator, or is fixed at zero. Within the
interactive traffic class, each THP has its own associated MTBR that is configurable by the operator. The
MTBR of THP 2 must be less than or equal to the MTBR of THP 1, and the MTBR of THP 3 must be less
than or equal to the MTBR of THP 2.
For all traffic classes except for interactive THP 1 and interactive THP 2, the maximum MTBR can be fit into
a single timeslot allocation no matter how the MTBR is set. This guarantees that these classes will not be
rejected by the system when timeslots are idle in the cell and available throughput exists on the PRP board.
68P02900W21-R 8-45
28 Feb 2006 GMR-01
Within the interactive traffic class, the THP 3 class has a maximum MTBR that can be fit into a single timeslot
allocation no matter how the MTBR is set. This means that a THP 3 will not be rejected by the system when
timeslots are idle in the cell and available throughput exists on the PRP board. THP 1 and THP 2 both support
a maximum MTBR of 24 kbps in the downlink and 6 kbps in the uplink. THP 1 and THP 2 are downgradable
to THP3 so they can be fit into a single timeslot and thus will not be rejected by the system when timeslots
are idle in the cell and available throughput exists on the PRP board.
Per mobile commitment

The BSS limits its MTBR commitment to a mobile to a value that the mobile is capable of supporting. The
BSS will allocate no more than 6 kbps per timeslot to the mobile in each direction (UL/DL). If the mobile
does not support enough timeslots in the downlink direction to support the MTBR of its requested THP, which
can only happen for interactive THP 1 and 2, the mobile will be downgraded.
8-46 68P02900W21-R
GMR-01 28 Feb 2006
See Table 8-12 for maximum MTBR in downlink and uplink for each multislot class.
Table 8-12 Maximum MTBR in UL/DL per multislot capability
Max
Mobile Multislot Max
MTBR
multislot class Possible configurations MTBR
(down-
class supported (uplink)
link)
1 1 6 6
2 2 6 12
4 4 6 18
5 5 6 12
6 6 6 12
or
8 8 6 24
9 9 6 18
10 10 6 18
or
Downlink timeslot
Uplink timeslot
Biasable mobile commitment
The BSS limits its MTBR commitment to a biasable mobile (multislot classes 6 and 10, and any that map to
these classes) to the maximum MTBR allowed per timeslot multiplied by the number of timeslots that are
fixed in each direction. Thus, multislot class 6 is committed at most 12 kbps (2 timeslots) in the downlink and
6 kbps (1 timeslot) in the uplink, and class 10 is committed at most 18 kbps (3 timeslots) in the downlink
and 6 kbps (1 timeslot) in the uplink
68P02900W21-R 8-47
28 Feb 2006 GMR-01
Per timeslot zone commitment

The BSS limits its MTBR commitment to a timeslot zone to 6 kbps of MTBR in the downlink and in the
uplink per timeslot in that timeslot zone unless scheduling the fourth mobile on that timeslot. When
scheduling the fourth mobile on a timeslot, the BSS allows a commitment to be 8 kbps on all timeslots
where there are (will be) four mobiles assigned.
Per PRP board commitment

The BSS limits its MTBR commitment to a PRP to 25 active timeslots of throughput in either direction. The
remaining 5 timeslots are reserved as headroom for STNNT and PAP mobiles and for coding scheme changes.
The total committable bandwidth is a function of the coding schemes of the mobiles on the board.
PRP-PDTCH QoS planning
The maximum number of PDTCHs to assign per PRP based on the information provided in "{23956} QoS
capacity" on page 8-43 is calculated using the following steps:
1. Calculate the PRP board throughput based on coding schemes used while subtracting PRP
board headroom.
2. Calculate the average downlink MTBR to determine the amount to reserve for each QoS
subscriber.
3. Divide the PRP board throughput by the average downlink MTBR to determine the
MAX_QOS_PDTCHS_PER_PRP.
Calculating PRP board throughput

PRP board throughput is calculated as follows:
_ _
_ _
_ _
Where: is:
%CS1_USAGE The percentage of time the
%CS2_USAGE relevant coding scheme is used by
%CS3/4_USAGE subscribers in the cells attached to
%EGPRS_USAGE a given PCU.
8-48 68P02900W21-R
GMR-01 28 Feb 2006
Calculating average downlink MTBR

Average downlink MTBR is calculated as follows:
_ _
_ _
_ _ _
Where: is:
I1_MTBR The downlink MTBR values set for each
I2_MTBR of the traffic classes.
I3_MTBR
BG_MTBR
BE_MTBR
The MTBR values are defined

at the cell level. The values to
use for this equation are either
the average MTBRs for each
traffic class across all cells
connected to a PCU or the
maximum MTBR values set
at a cell for each traffic class.
%subs The number of subs allocated to each of
the traffic classes in the system based on
subscription or by default based on no
QoS subscription or roaming subscribers
entering the system and having their QoS
attributes negotiated to a traffic class.
Calculating MAX_QOS_PDTCHS_PER_PRP
MAX_QOS_PDTCHS_PER_PRP is calculated as follows:
_ _
_ _ _ _
_ _
This yields the recommended value of the number of PDTCHs to assign to a given PRP to achieve the
requested MTBR.
68P02900W21-R 8-49
28 Feb 2006 GMR-01
PCU-SGSN: traffic and signalling planning Chapter 8: PCU upgrade for the BSS
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:
• Point-to-point frame relay connection, with DACs.
• 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 8-13 provides a description of the Gb entities and identifiers. A further discussion on how these
should be selected is given later in this chapter.
8-50 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning PCU-SGSN: traffic and signalling planning
Table 8-13 Gb entities and identifiers
Gb Entity and Identifier Description

E1 The physical link contains 32 timeslots. One is
reserved for E1 synchronization. Each timeslot uses
a rate of 64 kbit/s.
Frame relay bearer channel (FR BC) The bearer channel allows the frame relay protocol
to map its resources to the E1 layer.
Permanent virtual circuit (PVC) A frame relay virtual circuit. This allows the packet
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 identifier (DLCI) A unique number assigned to a PVC end point in a
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 identifier (NSEI) Uniquely identifies a NSE.
Network service virtual circuit (NSVC) A logical circuit that connects the NSE peers
between the SGSN and PCU. The NSVC has
significance across the network. Therefore, it is
configured identically at the SGSN and PCU.
Network service virtual circuit identifier (NSVCI) Uniquely identifies a NSVC. There is a one-to-one
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 identifier (BVCI) Uniquely identifies a BVC.
68P02900W21-R 8-51
28 Feb 2006 GMR-01
General planning guidelines
These are the general planning guidelines:

• There can be more than one BVC per NSE/PCU/BSS.
• There is one point-to-point BVCI per cell, statically configured at the PCU and dynamically
configured at the SGSN.
• There are multiple NSVCs serving one NSE.
• There is a one-to-one mapping between NSVCIs and DLCIs.
• 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.
• The DLCI has local significance only, while the NSVCI has significance across the network.
• One E1 can be fractionalized into several bearer channels.
Specific planning guidelines
Motorola deploys one NSEI per PCU, and up to three PCUs per BSS. Each NSEI must be unique.
Gb signalling
This section describes the Gb protocol signalling. The signalling and the Gb link capacity limitations must be
considered in each Gb link plan.
Gb protocol signalling
The GPRS/EGPRS Mobility Management (GMM/EGMM) signalling procedures which contribute to uplink
and downlink overhead on the Gb link are as follows:
• Attach/Detach with ciphering.
• Cell reselection.
• Inter/Intra RAU.
• PDP activate/deactivate.
• Paging.
Gb link PDU data

Each Gb link PDU carries protocol overhead, which is calculated to be 71 bytes.
8-52 68P02900W21-R
GMR-01 28 Feb 2006
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:
_ _
_ _
_ _
_ _ _ _
Therefore:
_ _ _ _ _ _
Where: is:
Total_Data_Rate 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
protocol.
User_Data_Rate the required rate (bytes/s) for
GPRS user application data over
a GBL interface between the PCU
and SGSN, including protocol
overhead.
PSATTACH/DETACH the attach/detach rate per sub/BH.
RAU the periodic, Intra and inter area
update rate per sub/BH.
Cont.
68P02900W21-R 8-53
28 Feb 2006 GMR-01
Where: is:
PDPACT/DEACT the PDP context activation/
deactivation rate per sub/busy
hour.
PGPRS the GPRS paging rate (per sec).
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).
CellUpdate the cell reselections rate per
sub/busy hour.
To simplify Gb planning, the Signalling_Data_Rate can be ignored since it is insignificant

compared to the Total_Data_Rate.
8-54 68P02900W21-R
GMR-01 28 Feb 2006
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.
_ _
_ _
_ _
Where: is:
No_GBL_TS 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
is accounted for.
UGBL the link utilization.
NPCU-SGSN the E1 link between the PCU and
SGSN.
Frame relay parameter values
The network planner needs to specify the values for the following three frame relay interface parameters:
• Committed Information Rate (CIR).
• Committed Burst Rate (Bc).
• Burst Excess Rate (Be).
68P02900W21-R 8-55
28 Feb 2006 GMR-01
These frame relay parameter values are determined as described in the following text and illustrated in
Figure 8-7.
Figure 8-7 Frame relay parameters
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.
8-56 68P02900W21-R
GMR-01 28 Feb 2006
The recommended frame relay network CIR value is calculated as follows:
_ _
_
_
Where: is:
CIR_Value 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
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.
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.
68P02900W21-R 8-57
28 Feb 2006 GMR-01
BSS-PCU hardware planning example for GPRS Chapter 8: PCU upgrade for the BSS
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 8-8. 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.{23956} The QoS feature
is not enabled.
Figure 8-8 PCU equipment and link planning for GPRS
BSC GDS PCU1 SGSN

1 to 18 E1s
GBL
GSL
1 or 2 E1s 1 to 4 E1s
GDS PCU2
1 to 18 E1s
GBL
GSL 1 to 4 E1s
1 or 2 E1s
GDS PCU3
1 to 18 E1s GBL
GSL 1 to 4 E1s
1 or 2 E1s
GSM + GPRS E1s
BTS
8-58 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS-PCU hardware planning example for GPRS
BSS - PCU planning example for GPRS
Use this example to provision a BSS with 10 sites consisting of 20 cells, one GPRS carrier per cell, paging
coordination enabled (i.e. NOM I), PCCCH enabled (pccch_enabled = 1) at some cells, and 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
Cell Updates CellUpdate = 1.5
GPRS users per cell 200
Average sessions per user per hour 5
GSM circuit-switched paging rate (pages/second) PGSM = 3
Ratio of LCSs per call LCS = 0.2
Ratio of mobiles in the system that are both GSM NGSM_GPRS_MS/NAll_MS
and GPRS capable = 0.25
Number of PCCCH-enabled cells in the BSS 10
Total number of cells in the BSS 20
TRAU TYPE 64
Mobile Class Type 10
Step 1: Choose a cell RF plan

Use the 4x3 non-hopping table (Table 3-22 in Chapter 3, "BSS cell planning,") to determine what the values to
use for CS rate and BLER for the chosen cell RF plan.
Step 2: Determine the number of CCCHs at each BTS cell

Use the following equation:
When pccch_enabled = 0 (PCCCH disabled) at the cell, the BTS combines the additional control channel
load for the GPRS data traffic with the existing circuit-switched traffic load onto the CCCH. On the other
hand, when pccch_enabled = 1 at the cell, GPRS does not add any additional control channel load on the
CCCH. In this case, however, PCCCH will reduce the GSM circuit-switched signalling load on the CCCH
with paging coordination.
68P02900W21-R 8-59
28 Feb 2006 GMR-01
The network planner needs to consider paging coordination, the expected paging rate, and the access grant
rate in order to calculate the number of CCCH blocks needed. This calculation should be performed using the
guidelines given in the Control channel calculations section of Chapter 3.
Step 3: Determine the number of PCCCHs at each BTS cell

If the planner intends to use PCCCH in the cell, the PCCCH requirements must be considered before
determining the number of GPRS timeslots for the cell. This is because PCCCH blocks occupy reserved
PDTCHs in the cell.
Since paging coordination is enabled, GSM circuit-switched paging traffic on the PCCCH must be considered.
Opting to balance to minimize the cell reselection delay, choose the number of PBCCHs to be four.
NPBCCH = 4
8-60 68P02900W21-R
GMR-01 28 Feb 2006
Step 4: Determine number of GPRS carrier timeslots at each BTS cell

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.
_ _ _ _
_ _
_ _
_ _
_ _ _ _
_ _
Therefore, provision 6 timeslots on the cell. The PCCCH will be configured on one of those 6 timeslots.
Step 5: 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,
• CS3/CS4 timeslots requires 32K TRAU on GDS TRAU interface,
• CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier would require
32K TRAU.
For this case it can be calculated that 2 GDS TRAU E1s are required.
If the number of GDS E1 links exceeds the limit for one PCU, then one or two additional PCUs will be
required. Since the limit is 18 GDS E1 links, only one PCU is required.
Step 6: Calculate the number of active timeslots

Assuming that we need to provide coverage to at least half of the timeslots at any instance, the number of
mean 6/2= PDTCHs = 3 (from step 4), the number of active timeslots is:
If the number of active timeslots exceeds the limit for one PCU then one or two additional PCUs will be
required. Since the limit is 270 active timeslots (240 with redundancy), only one PCU is required.
68P02900W21-R 8-61
28 Feb 2006 GMR-01
Step 7: Partition the load across multiple PCUs

If, in steps 5 or 6, additional PCU(s) were required, then the cells should be divided amongst the PCU(s). The
load (E1s and active timeslots) may be divided evenly, or proportionally in anticipation of future expansion. If
the redundancy part of the 3xPCU feature is to be used, then ideally the load is evenly divided.
Once partitioning has been performed, then steps 5 and 6 are repeated, but on a per PCU basis. The remainder
of the steps then apply to each PCU separately.
Step 8: Calculate the number of PRP boards

Each PRP board can process 30 active timeslots at any given time for a total of 120 timeslots. Using the value
calculated in step 6, the number of PRPs required to serve 20 cells is:
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.
Step 9: Calculate the BSC LCF impact to support GPRS traffic

The BSC LCF GPROC 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.
_ _ _
Where: is:
In this instance, B=10.

The network planner may choose to add an additional LCF GPROC, or to examine the GSM circuit-switched
provisioning to see whether an existing LCF GPROC could process this additional load.
8-62 68P02900W21-R
GMR-01 28 Feb 2006
Step 10: Calculate the number of GBL links

Using the standard traffic model and Gb formulae:
_ _
_ _
_ _
_ _ _ _ _
_ _
_ _
_ _
Hence, 2 Gb links need to be provisioned.
68P02900W21-R 8-63
28 Feb 2006 GMR-01
Step 11: 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. It assumes that all 20 cells parented to a single LCF card in the BSC, after
performing step 10. Evaluating this equation and the supporting expressions results in one 64 kbit/s GSL
link being required, assuming that enhanced one phase is enabled, after rounding up to the nearest integer
value (but not including redundancy).
Refer to "Determining the number of GSLs required" on page 6-55 in Chapter 6, "BSC planning steps and
rules," for further details on the following equations.
The number of GSL TSs for run-time is represented by:
The number of GSLs required is:
_ _
Step 12: Balance the GSL load across the LCFs

This step may be performed optionally and automatically by the system at sysgen. If it is desired to
perform the operation manually, suggestions and an example are given in the Load balancing section of
"Determining the number of GSLs required" on page 6-55 in Chapter 6, "BSC planning steps and rules,".
8-64 68P02900W21-R
GMR-01 28 Feb 2006
Step 13: 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 to process GDS LAPD (see below).
◦ 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.
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. The PCU
hardware calculation above calculates the number of PICP boards based only on the ratio
of PICP boards to PRP boards. The following calculation 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.
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.
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 shows that one PICP is sufficient to process the link
provisioning requirements.
Step 14: 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, an
additional 12 x16 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 about 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 to "Dynamic timeslot allocation" on page 3-156 in Chapter 3,
"BSS cell planning,".
Step 15: Calculate the changes in signalling traffic load (RSL load) on the E1s between
the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), 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. For cells with PCCCH, GPRS does not add significant additional
control channel load on the RSL. In this case however, PCCCH will reduce the GSM circuit-switched
signalling load on the RSL with paging coordination.
68P02900W21-R 8-65
28 Feb 2006 GMR-01
The new load on the RSL for GPRS is based on the evaluation of the following equation and other supporting
equations.
Refer to "Determining the number of RSLs required" on page 6-22 in Chapter 6, "BSC planning steps and
rules," for further details on the following equation.
The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the GPRS
calculation.
Step 16: BSC link 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 6 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.
Step 17: BTS provisioning impact

GPRS has no impact on the hardware provisioning of a Horizon II macro, Horizonmacro or M-Cell BTS.
8-66 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning BSS-PCU hardware planning example for EGPRS
BSS-PCU hardware planning example for EGPRS

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to BSS-PCU hardware planning
This section builds upon the previous example shown in "BSS-PCU hardware planning
example for GPRS" on page 8-58 by adding EGPRS into the system.
The main additions are:
• the addition of the new EGPRS carriers,
• calculation of the impact of increased data capacity on the system.
68P02900W21-R 8-67
28 Feb 2006 GMR-01
BSS-PCU hardware planning example for EGPRS Chapter 8: PCU upgrade for the BSS
The provisioning of the SGSN hardware is not covered in this planning guide.
Figure 8-9 PCU equipment and link planning for EGPRS
BSC GDS PCU1 SGSN

1 to 36 E1s
GBL
GSL
1 or 2 E1s 1 to 12 E1s
GDS PCU2
1 to 36 E1s
GBL
GSL 1 to 12 E1s
1 or 2 E1s
GDS PCU3
1 to 36 E1s GBL
GSL 1 to 12 E1s
1 or 2 E1s
GSM + GPRS E1s
BTS
BSS - PCU planning example for EGPRS
The example for EGPRS has new call model parameters for increased data usage.
See BSS - PCU planning example for GPRS in "BSS-PCU hardware planning example for
GPRS" on page 8-58 to compare the GPRS/EGPRS call model parameters.
coordination enabled (i.e. NOM I), PCCCH enabled (pccch_enabled = 1) at some cells.
8-68 68P02900W21-R
GMR-01 28 Feb 2006
Additional data:
{23956} The QoS feature is not enabled.
Add one EGPRS carrier per cell with the following call model:
Average packet size (bytes) PKULSIZE = 287

Average packet size (bytes) PKDLSIZE = 701
Traffic per sub/BH (kbytes/hr) - uplink ULRATE = 40
Traffic per sub/BH (kbytes/hr) - downlink Data_rate_per_sub = 85
GPRS paging rate in pages per second PGPRS = 1.4
GPRS/EGPRS users per cell 250
GSM circuit-switched paging rate (pages/second) PGSM = 0.32
and GPRS capable = 100%
Percentage of mobiles that are EGPRS capable 5%

Use the 4x3 non-hopping table (Table 3-22 in Chapter 3, "BSS cell planning,") to determine what the values to
use for CS rate and BLER for the chosen cell RF plan.

68P02900W21-R 8-69
28 Feb 2006 GMR-01
guidelines given in "Control channel calculations" on page 3-125 in Chapter 3, "BSS cell planning,".

PDTCHs in the cell.
NPBCCH = 4
8-70 68P02900W21-R
GMR-01 28 Feb 2006
Step 4: Determine number of GPRS and EGPRS carrier timeslots at each BTS cell
_ _ _
_ _
_ _
_ _
_ _ _ _
_ _
Therefore, provision 4 timeslots on the cell. The PCCCH will be configured on one of those 4 timeslots. This
is a lower number than in the previous example. The number of users and Mean_traffic_load has increased
but the TS_Data_Rate has also increased with the EGPRS capabilities that means the timeslots calculation
does not increase as per the GPRS calculation. The previous example had one GPRS carrier per cell that
provided adequate throughput for the calculated 6 timeslots. The new equation also provides 6 timeslots
but these are divided between GPRS and EGPRS. The new EGPRS carrier will provide 8 timeslots of data
capacity that is above the required 6. In this example we will have 8 GPRS timeslots configured as switchable
or packet data from the original GPRS carrier and 8 timeslots defined as packet data for the new EGPRS
carrier for a total of 16 data capable timeslots per cell. This is a total of 320 data capable timeslots.

• CS3/CS4 timeslots requires 32K TRAU,
• MCS1 through MCS9 require {23769} a variable VersaTRAU backhaul in units of 64K
{23769} DS0s on the GDS TRAU interface,
{23769} The example here assumes that each EGPRS RTF is equipped with
a backhaul of 8 DS0s (rtf_ds0_count = 8). This is the worst case. Typical
configuration may require less GDS resources.
32K TRAU and the EGPRS carrier would require 64K TRAU.
68P02900W21-R 8-71
28 Feb 2006 GMR-01
required. Since the limit is 36 GDS E1 links, only one PCU is required for capacity. Additional PCUs can be
configured for additional redundancy.

A PRP board can be assigned up to 120 timeslots but only 30 will be serviced (active) at any given time. The
PRP algorithms handle the scheduling of timeslots in an efficient manner dependant on resources available.
Assuming that we need to provide coverage to at least half of the timeslots at any instance and since the
equation above resulted in 6 timeslots and the cell will have 16 timeslots between GPRS and EGPRS:
Where: is:
loading factor equal to 1 through 4, depending on
throughput requirements.
By using the assumption that only half of the timeslots will need to be serviced at an interval, a PRP in this
example should be assigned a maximum of 60 timeslots.
If the number of active timeslots exceeds the limit for one PCU then one or two additional PCUs will be
required. The limit is 1080/loading factor (960/loading factor with redundancy) active timeslots per PCU.


Each PRP board can process 30 active timeslots at any given time for a total of 120 timeslots. Using the value
calculated in step 6 and the number to assign to each PRP, the following equation is created:
The provisioning of the 8 GDS E1s to 6 PRPs is required in order not to break the 60 timeslots per PRP.
8-72 68P02900W21-R
GMR-01 28 Feb 2006
Each PRP must terminate at least one GDS TRAU E1 and the timeslots of an entire cell must
terminate on the same PRP.

The volume of GPRS and EGPRS signalling traffic increases the BSC LCF {23956} GPROC2 processor load.
The BSS planning rule for LCF provisioning in the following equation should be used.
_ _ _
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 process this additional load.

_ _
_ _
_ _

number of users on a PCU is 5000. It assumes that all 20 cells parented to a single LCF card in the BSC,
after performing step 10. 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).
68P02900W21-R 8-73
28 Feb 2006 GMR-01
_ _

This step may be performed optionally and automatically by the system at sysgen. If it is desired to perform
the operation manually, suggestions and an example are given in Load balancing section of "Determining
the number of GSLs required" on page 6-55 in Chapter 6, "BSC planning steps and rules,".
8-74 68P02900W21-R
GMR-01 28 Feb 2006
• Qty 6 PRP boards, 8 GDS E1 links (GDS) timeslot balanced across the PRPs.
◦ Qty 2 PICP boards, 1 PICP board to process GDS LAPD (GSL) and 1 PICP board
to process the GBL traffic (see below).
9 PRP boards.
Therefore, 3/4 of a PICP is required for the GBL E1 links.
terminate up to 2 E1 GSL links and up to 60 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. Due to the
limitation of a PMC cannot share a GSL and GBL, a second PICP is required.
It is assumed that the EGPRS traffic is in addition to the existing circuit-switched traffic and GPRS traffic
already available in the system. In step 2 it was determined that 8 timeslots would be required for the EGPRS
timeslot traffic on a per cell basis. Therefore, an additional 16 x 16 kbits/s timeslots (MCS1 - MCS9) 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 EGPRS carrier
timeslots. When EGPRS enabled, all reserved and switchable timeslots are backhauled from the BTS
through the BSC to the PCU. The physical link calculations must take this into account. The CPU processing
equations need to take into account the percentage of backhauled timeslots that are active at a given time
interval. If GSM circuit-switched statistics are available, they could be reviewed to aid in this decision. Refer
to to "Dynamic timeslot allocation" on page 3-156 in Chapter 3, "BSS cell planning,".
68P02900W21-R 8-75
28 Feb 2006 GMR-01
the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signalling load for
the EGPRS 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. For cells with PCCCH, EGPRS does not add
significant additional control channel load on the RSL. In this case however, PCCCH will reduce the GSM
circuit-switched signalling load on the RSL with paging coordination.
equations.
The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the EGPRS
calculation.

The BSC may require additional hardware in order to support the addition of the EGPRS network traffic. For
The BSC will require more E1 terminations in support of the additional E1 links to the PCU and in support
of the additional EGPRS traffic over the BTS to BSC interface. In this example, eight E1s were added for
{23956} BSS - PCU planning example for EGPRS with QoS

enabled
This example uses the same base call model parameters as those used in "BSS - PCU planning example for
EGPRS" on page 8-68 except that the QoS feature is enabled. QoS requires new call model parameters
to be specified based on QoS usage.
See "BSS - PCU planning example for EGPRS" on page 8-68 to compare the GPRS/EGPRS call
model parameters.
coordination enabled (that is, NOM I), PCCCH enabled (pccch_enabled = 1) at some cells.
Additional data:
The QoS feature is enabled.
8-76 68P02900W21-R
GMR-01 28 Feb 2006
Add one EGPRS carrier per cell with the following call model:
Average packet size (bytes) PKULSIZE = 287

Average packet size (bytes) PKDLSIZE = 701
Traffic per sub/BH (kbytes/hr) - uplink ULRATE = 40
Traffic per sub/BH (kbytes/hr) - downlink Data_rate_per_sub = 85
GPRS paging rate in pages per second PGPRS = 1.4
GPRS/EGPRS users per cell 250
GSM circuit-switched paging rate (pages/second) PGSM = 0.32
and GPRS capable = 100%
Percentage of mobiles that are EGPRS capable 5%
I1_MTBR 14
I2_MTBR 10
I3_MTBR 4
BG_MTBR 2
BE_MTBR 2
I1_MTBR_USAGE 5%
I2_MTBR_USAGE 10%
I3_MTBR_USAGE 25%
BG_MTBR_USAGE 20%
BE_MTBR_USAGE 40%
CS1_USAGE 3.75%
CS2_USAGE 3%
CS3/4_USAGE 68.25%
EGPRS_USAGE 25%
TRAU TYPE 64
Mobile Class Type 10
68P02900W21-R 8-77
28 Feb 2006 GMR-01

Compared with "BSS - PCU planning example for EGPRS" on page 8-68, this step has changed with the
addition of the QoS feature. BLER is compensated by the PRP board headroom required for QoS. The CS
coding schemes are set as pre-defined values determined by the QoS feature. For GPRS the maximum rate
is 8K and for EGPRS the maximum rate is 14k.

guidelines given in "Control channel calculations" on page 3-125 in Chapter 3, "BSS cell planning,".
8-78 68P02900W21-R
GMR-01 28 Feb 2006

PDTCHs in the cell.
NPBCCH = 4
68P02900W21-R 8-79
28 Feb 2006 GMR-01
Step 4: Determine number of GPRS and EGPRS carrier timeslots at each BTS cell
_ _ _
_ _
_ _
_ _
_ _ _ _
_ _
The above equation takes into account the amount of local timeslot headroom to allow to the required MTBR.
The mean load factor is set to .75 to accommodate peak data scenarios since the mean traffic load is based
on averages. The defined timeslot throughput and the PRP board headroom allocated by the QoS feature
cover the signalling peak periods. The tables in Chapter 3 should be consulted. Table 3-27shows that with 6
PDTCHs and the above referenced QoS Call model, 10 mobiles can be supported, so 7 should be adquate.

• CS3/CS4 timeslots requires 32K TRAU,
• MCS1 through MCS9 require {23769} a variable VersaTRAU backhaul in units of 64K
{23769} DS0s on the GDS TRAU interface,
{23769} The example here assumes that each EGPRS RTF is equipped with
a backhaul of 8 DS0s (rtf_ds0_count = 8). This is the worst case. Typical
configuration may require less GDS resources.
32K TRAU and the EGPRS carrier would require 64K TRAU.
8-80 68P02900W21-R
GMR-01 28 Feb 2006
required. Since the limit is 36 GDS E1 links, only one PCU is required for capacity. Additional PCUs can be
configured for additional redundancy.

A PRP board can be assigned up to 120 timeslots but only 30 will be serviced (active) at any given time. The
PRP algorithms handle the scheduling of timeslots in an efficient manner dependant on resources available.
The QoS feature provides further guidelines on the number of timeslots to assign to a PRP to achieve
the requested MTBR per subscriber.
68P02900W21-R 8-81
28 Feb 2006 GMR-01
PRP board throughput is calculated as follows:

_ _
_ _
_ _
Therefore:
_ _
Average downlink MTBR is calculated as follows:

_ _
_ _
_ _ _
Therefore:
_ _
MAX_QOS_PDTCHS_PER_PRP is calculated as follows:

_ _
_ _ _ _
_ _
Therefore:
_ _ _ _

The previous example had one GPRS carrier per cell that provided adequate throughput for the calculated 6
timeslots. The new equation also provides 6 timeslots but these are divided between GPRS and EGPRS. The
new EGPRS carrier will provide 8 timeslots of data capacity that is above the required 6. In this example
we will have 8 GPRS timeslots configured as switchable or packet data from the original GPRS carrier and
8 timeslots defined as packet data for the new EGPRS carrier for a total of 16 data capable timeslots per
cell. This is a total of 320 data capable timeslots.
The provisioning of the 8 GDS E1s to 4 PRPs is required in order not to break the 60 timeslots per PRP.
Each PRP must terminate at least one GDS TRAU E1 and the timeslots of an entire cell must
terminate on the same PRP.
8-82 68P02900W21-R
GMR-01 28 Feb 2006


The volume of GPRS and EGPRS signalling traffic increases the BSC LCF GPROC2 processor load. The
BSS planning rule for LCF provisioning in the following equation should be used.
_ _ _
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 process this additional load.

_ _
_ _
_ _
68P02900W21-R 8-83
28 Feb 2006 GMR-01

number of users on a PCU is 5000. It assumes that all 20 cells parented to a single LCF card in the BSC,
after performing step 10. 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).
_ _

This step may be performed optionally and automatically by the system at sysgen. If it is desired to perform
the operation manually, suggestions and an example are given in Load balancing section of "Determining
the number of GSLs required" on page 6-55 in Chapter 6, "BSC planning steps and rules,".
8-84 68P02900W21-R
GMR-01 28 Feb 2006
• Qty 4 PRP boards, 8 GDS E1 links (GDS) timeslot balanced across the PRPs.
◦ Qty 2 PICP boards, 1 PICP board to process GDS LAPD (GSL) and 1 PICP board
to process the GBL traffic (see below).
9 PRP boards.
Therefore, 3/4 of a PICP is required for the GBL E1 links.
terminate up to 2 E1 GSL links and up to 60 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. Due to the
limitation of a PMC cannot share a GSL and GBL, a second PICP is required.
It is assumed that the EGPRS traffic is in addition to the existing circuit-switched traffic and GPRS traffic
already available in the system. In step 2 it was determined that 8 timeslots would be required for the EGPRS
timeslot traffic on a per cell basis. Therefore, an additional 16 x 16 kbits/s timeslots (MCS1 - MCS9) 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 EGPRS carrier
timeslots. When EGPRS enabled, all reserved and switchable timeslots are backhauled from the BTS
through the BSC to the PCU. The physical link calculations must take this into account. The CPU processing
equations need to take into account the percentage of backhauled timeslots that are active at a given time
interval. If GSM circuit-switched statistics are available, they could be reviewed to aid in this decision. Refer
to "Dynamic timeslot allocation" on page 3-156 in Chapter 3, "BSS cell planning,".
the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signalling load for
the EGPRS 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. For cells with PCCCH, EGPRS does not add
significant additional control channel load on the RSL. In this case however, PCCCH will reduce the GSM
circuit-switched signalling load on the RSL with paging coordination.
68P02900W21-R 8-85
28 Feb 2006 GMR-01
equations.
The GSM RSL calculation should be performed with 64 kbit/s RSL in order to be consistent with the EGPRS
calculation.

The BSC may require additional hardware in order to support the addition of the EGPRS network traffic. For
The BSC will require more E1 terminations in support of the additional E1 links to the PCU and in support
of the additional EGPRS traffic over the BTS to BSC interface. In this example, eight E1s were added for
8-86 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
9
Planning exercises
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Planning exercises designed to illustrate the use of the rules and formulae shown earlier are provided here.
The tables of required equipment here 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.
The topics described here are as follows:
• "Initial requirements" on page 9-2
• "The exercises" on page 9-4
• "Determine the hardware requirements for BTS B" on page 9-5
• "Determine the hardware requirements for BTS K" on page 9-8
• "Determine the hardware requirements for the BSC " on page 9-12
• "Determine the hardware requirements for the RXCDR" on page 9-15
• "Calculations using alternative call models" on page 9-19
• "A planning example of BSS support for LCS provisioning" on page 9-90
68P02900W21-R 9-1
28 Feb 2006 GMR-01
Initial requirements Chapter 9: Planning exercises
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 9-1.
Table 3-13 or Table 3-14 (depending on position in location area) in the "Call model parameters for
capacity calculations" on page 3-122 section of Chapter 3, "BSS cell planning," provides the maximum
Erlang capacity for a given number of carriers at 2% blocking. These tables also list the number of carriers
(RTFs) required; column three of Table 9-1 lists this information.
If hr (AMR) is used, hr usage will need to be taken into account for Erlang calculations.
If other blocking factors at the air interface are required, the number of Erlangs quoted in Table 3-14 and
Table 3-15 in the "Call model parameters for capacity calculations" on page 3-122 section of Chapter 3,
"BSS cell planning," can be found by reference to standard Erlang B tables for the equivalent number
of traffic channels at the required blocking factor.
Table 9-1 Busy hour demand and number of carriers
BTS identification Erlangs Antenna configuration

A 6 Omni 2
B 5 Omni 2
C 2 Omni 1
D 5 Omni 2
E 14 Omni 3
F 10 Omni 3
G 5 Omni 2
H 2 Omni 1
J 5 Omni 2
K 20/20/20 Sector 4/4/4
L 5 Omni 2
Total 119 32 carriers
9-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Initial requirements
Network topology
Using a frequency planning tool it is possible to assign adequate frequencies to support the BTS antenna
configurations of Table 9-1. Based on this, initial planning of the network gives the topology shown in
Figure 9-1.
Figure 9-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
68P02900W21-R 9-3
28 Feb 2006 GMR-01
The exercises Chapter 9: Planning exercises
The exercises
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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, and RXCDR.
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 6.
No half rate usage is specified for this exercise.
9-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for BTS B
Determine the hardware requirements for BTS B

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
From Figure 9-1 and Table 9-1 it can be seen that BTS B requires two RF carriers in 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.
68P02900W21-R 9-5
28 Feb 2006 GMR-01
Determine the hardware requirements for BTS B Chapter 9: Planning exercises
Database option
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 9-2 and Table 9-3.
Table 9-2 Customer ordering guide 900 MHz (M-Cell6 indoor)
Question Compulsory
Voltage used +27 V dc
-48 V/60 V dc
110/240 V ac
How many cells are required? 123
How many carriers are required per cell? 1 2345678
(RF configuration)
How many cabinets are required for the RF 1234
configuration?
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)
9-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for BTS B
Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor)
Question Options
Is link redundancy required? Yes
No
Is digital redundancy required? Yes
No
Is power redundancy required? Yes
No
Is duplexing required? Yes
No
Is a high power duplexer shelf and/or external rack Yes
required? 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
68P02900W21-R 9-7
28 Feb 2006 GMR-01
Determine the hardware requirements for BTS K Chapter 9: Planning exercises
Determine the hardware requirements for BTS K

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
From Figure 9-1 and Table 9-1 it can be seen that BTS K requires 12 RF carriers in 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.
Alternatively, the site can be contained in a single Horizon II macro indoor cabinet.
Receiver requirements
A single Horizon II macro cabinet solution, a two cabinet Horizonmacro solution and a three cabinet
Horizonmacro solution are provided below.
Single cabinet Horizon II macro solution

The single cabinet will contain six CTU2 transceivers, operating in pairs and in dual carrier mode to provide
the 3 sector 4/4/4 configuration required.
An optional SURF2 dual band adaptor allows a 900 MHz SURF2 and an 1800 MHz SURFs to be installed
in the same cabinet, thus providing dual band capability. A maximum of 3 CTU2s per band can be
accommodated for 2/2/2 and 2/2/2 configuration. Refer to Chapter 12, "Standard BSS and Horizon BTS
configurations," for details on configuration.
Two cabinet Horizonmacro 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 Horizonmacro solution

Each cabinet will be dedicated to a sector, allowing for easy expansion.
9-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for BTS K
Transmitter combining requirements
A one, two, and three cabinet solution are provided below.
Single cabinet Horizon II macro solution

Each sector requires two DUPs, one for each CTU2.
Two cabinet Horizonmacro solution

Each sector requires two DCF modules. The shared sector will have one DCF module in the master cabinet
and the other DCF in the extender cabinet.
Three cabinet Horizonmacro solution

Each cabinet will be dedicated to a sector, which requires one DDF and HCU modules.
Summary
The equipment required, and an example of customer order creation for a single cabinet Horizon II macro
indoor (1800 MHz) configuration, to implement BTS K is listed in Table 9-4 and Table 9-5.
68P02900W21-R 9-9
28 Feb 2006 GMR-01
Determine the hardware requirements for BTS K Chapter 9: Planning exercises
Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor)
Question Compulsory 4
Voltage used +27 V dc 4
-48 V/60 V dc
240 V ac
How many cells are required? 1 4
2
3
How many carriers are required 1 4
per cell? (RF configuration) 2
3
4
5
6
7
8
One carrier (single density) or two 1 4
carriers (double density) required 2
per CTU2?
How many cabinets are required 1 4
for the RF configuration? 2
3
4
What type of combining is DUP & Air 4
required? DUP & HCU
DUP & DHU
DUP, HCU & Air
DUP, DHU & Air
DUP, HCU, DHU & Air
What line interface is required? T43 (E1) (75 ohm) 4
BIB (E1) (120 ohm)
9-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for BTS K
Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor)
Question Options 4
Is digital redundancy required? Yes 4
No
Is power redundancy required? Yes 4
No
Is an extra line interface required? Yes 4
No
Are 16-way alarm inputs required? Yes 4
No
Is a compact flash (memory) card Yes 4
required? No
Is a stacking bracket required? Yes 4
No
Is battery backup required? Yes 4
No
Is database required? Yes 4
(Provided by local office) No
68P02900W21-R 9-11
28 Feb 2006 GMR-01
Determine the hardware requirements for the BSC Chapter 9: Planning exercises
Determine the hardware requirements for the BSC

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
From Figure 9-1 and Table 9-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 9-1 shows that the number of links connected from the BTSs to the BSC is four.
BSC to MSC links

Reference to standard Erlang B tables shows that 119 Erlangs at 1% blocking 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:
This value should be rounded up to 2.
Transcoder requirement
None required, remote transcoding.
MSI requirement
Minimum number of MSIs required is given by:
Line interface
Depending on the interface standard (balanced or unbalanced) used, one BIB or one T43 is adequate
for three MSIs.
GPROC requirement
GPROC function requirements are listed in Table 9-6.
9-12 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for the BSC
Table 9-6 GPROCs required at the BSC
Function Number required

BSP 1 {25779} (GPROC3)
LCFs for MTLs 1
LCFs for RSLs 1
Optional GPROC requirements
Redundant BSP {25779} (GPROC3), CSFP 1
Redundant LCP 1
{25779} Total GPROC3s 1+1
Total GPROC2s/GPROC3s {25779} 2+1
The notation n + m means that n items are required plus m for redundancy.
KSW/DSW2 requirement
Device timeslot requirements are listed in Table 9-7.
Table 9-7 BSC timeslot requirements
Device Number required

GPROCs 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/DSW2 is required.
KSWX/DSWX requirement
The BSC is contained in one shelf so there is no requirement for a KSWX/DSWX.
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.
68P02900W21-R 9-13
28 Feb 2006 GMR-01
Determine the hardware requirements for the BSC Chapter 9: Planning exercises
PIX requirement
The number of PIX boards required depends on the number of external alarms that are required. Use one
for this example.
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.
Summary
The equipment required to implement the BSC is listed in Table 9-8.
Table 9-8 Equipment required for the BSC
Equipment Number required

BSSC2 or BSSC3 cabinet 1
BSU shelf 1
MSI 3
BIB or T43 1
{25779} GPROC3 1+1
GPROC2/GPROC3 {25779} 2+1
KSW/DSW2 1+1
GCLK 1+1
PIX (provides up to 8 external alarms) 1
LANX 1
EPSM/IPSM (+27 V) (-48 V) 2+1
9-14 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for the RXCDR
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 9-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:
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:
This applies to either XCDR or GDP cards.
68P02900W21-R 9-15
28 Feb 2006 GMR-01
Determine the hardware requirements for the RXCDR Chapter 9: Planning exercises
A GDP2 can transcode 60 channels and if used exclusively is determined by:
Enhanced capacity mode must be enabled within the RXCDR to access the second E1 when
GDP2s are used in non-MSI slots
XCDR, GDP and GDP2s may be mixed within a shelf.
The GDP2 requires that the RXU3 shelf is used. The BSSC3 cabinet with two RXU3 shelves can interface up
to 76 E1/T1 links. The BSSC2 cabinet can only interface up to 48 E1/T1 links.
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:
GPROC requirement
One GPROC2/GPROC3 is required, plus one for redundancy.
KSW/DSW2 requirement
From the number of MSIs, transcoders and E1 links, it can be seen that the total number of timeslots is
given by:
One KSW/DSW2 is required, plus one for redundancy.
9-16 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Determine the hardware requirements for the RXCDR
KSWX/DSWX requirement
The RXU is contained in one shelf so there is no requirement for a KSWX/DSWX.
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.
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.
Summary
The equipment required to implement the RXCDR is listed in Table 9-9.
68P02900W21-R 9-17
28 Feb 2006 GMR-01
Determine the hardware requirements for the RXCDR Chapter 9: Planning exercises
Table 9-9 Equipment required for the RXCDR
Equipment Number required

BSSC2 or BSSC3 cabinet 1
RXU or RXU3 shelf 1
MSI 2
XCDR/GDP-E1 5
BIB or T43 2
GPROC2/GPROC3 1+1
KSW or DSW2 1+1
GCLK 1+1
PIX (provides up to 8 external alarms) 1
LANX 1
EPSM/IPSM (+27 V) (-48 V) 2+1
9-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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 5, "BTS planning steps
and rules,", Chapter 6, "BSC planning steps and rules," and Chapter 7, "RXCDR planning steps and rules," 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 Chapter 5,
"BTS planning steps and rules,", Chapter 6, "BSC planning steps and rules," and Chapter 7, "RXCDR
planning steps and rules,". These necessary calculations are demonstrated in the following examples.
Planning example 1
Dimension a network with following requirements:

• GSM software release = GSR6 (Horizon II) .
• Number of sites 4/4/4 sites (BTS: M-Cell6) = 28.
• Number of omni 2 sites (BTS: M-Cell2) = 2.
68P02900W21-R 9-19
28 Feb 2006 GMR-01
Calculations using alternative call models Chapter 9: Planning exercises
Call model parameters

• Call duration T = 75 s.
• Ratio of SMSs per call S = 0.1.
• Ratio of location updates per call = 2.
• Ratio of IMSI detaches per call I = 0.2 (type 2).
• Location update factor L = 2 + 0.5 * 0.2 = 2.1.
• No. of handovers per call H = 2.
• Ratio of intra-BSC handovers to all handovers i = 0.5.
• MTL link utilization = 35% (0.35).
• RSL link utilization U = 25% (0.25).
• CCCH utilization UCCCH = 33% (0.33).
• Probability of blocking TCH PB-TCH < 2%.
• Probability of blocking SDCCH PB-SDCCH < 1%.
• Probability of blocking on A-interface < 1%.
• Number of BTS sites B = 28 +2 = 30.
• Number of cells per BSS C = 28 * 3 + 2 = 86.
• Number of cells per BTS CBTS = 3.
• GSM paging rate in pages per second PGSM = 10.
• GPRS paging rate in pages per second PGPRS = 0.
• Mean_TBF_Rate = 1.
• Number of GPRS timeslots NGPRS= 0.
9-20 68P02900W21-R
GMR-01 28 Feb 2006
Other considerations
• Line interface type = E1.
• Network termination option = T43.
• Power voltage option = -48/-60 V dc.
• Type of combining used = hybrid (CBF).
• Dedicated CSFP = YES.
• CSFP redundancy = NO.
• Redundancy for all other modules = YES.
• MTL links redundancy = YES.
• RSL link redundancy = NO.
• Coding schemes CS3 and CS4 used = NO.
• BTS connectivity = star configuration.
• IMSI/TMSI paging = TMSI.
• MTL load balancing granularity = 16.
GSR6 (Horizon II) limitations

• Max. BTS sites = 100.
• Max. BTS cells = 250.
• Active RF carriers = 512.
• Trunks = 3000.
• C7 links = 16.
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
68P02900W21-R 9-21
28 Feb 2006 GMR-01
Call arrival rate:
SMS rate:
Location update rate:
Access grant rate is given by:
From the call model parameters, paging rate PGSM, is 10, so the average number of CCCH blocks required to
support paging only is:
The average number of CCCH blocks required to support AGCH only is given by:
Using a CCCH utilisation figure, UCCCH, of 0.33, the average number of CCCH blocks required to support
both PCH and AGCH is given by:
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
9-22 68P02900W21-R
GMR-01 28 Feb 2006
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:
The number of SDCCHs to support an average number of busy SDCCHs of 7.211 with less than 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.
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
68P02900W21-R 9-23
28 Feb 2006 GMR-01
Call arrival rate:
SMS rate:
From the call model parameters paging rate PGSM, is 10, so the average number of CCCH blocks required to
Using a CCCH utilisation figure, UCCCH, of 0.33, the average number of CCCH blocks required to support
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
9-24 68P02900W21-R
GMR-01 28 Feb 2006
Using the values calculated in the previous section and other call model parameters, the average number of
SDCCHs, NSDCCH is given by formula detailed in Chapter 3:
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.
Step 2 : BSS planning - determining the number of RSLs

The number of 64 kbits/sec RSLs required is given by :
_ _
Where, n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS):
= 1.40
The number of RSLs required per 4/4/4 site is 2 and that for an omni 2 site is 1 (calculated in similar way).
BSC to BTS E1 interconnect planning
Number of E1 links required between a BSC and BTS is given by:
{23769}
_ _
(CS3 and CS4 are not used.)
68P02900W21-R 9-25
28 Feb 2006 GMR-01
Number of E1 links required between each 4/4/4 BTS and BSC:
Number of E1 links required between each omni 2 BTS and BSC:
Hence, only one E1 interconnection 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.
Determining the number of LCF GPROCs for RSL processing
Number of LCF-RSLs required is given by:
Where n is the number of TCHs under a BSC:
The number of LCFs for RSL processing is 5.

Determining the number of MTLs
Total Erlangs offered by the BSC with 28 sites with 4/4/4 configuration and 2 omni 2 site
Total Erlangs carried by the BSC with 28 sites with 4/4/4 configuration and 2 omni 2 site
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:
Using the call model parameters the number of MTLs can be calculated using formulae detailed in Chapter 6.
9-26 68P02900W21-R
GMR-01 28 Feb 2006
Maximum number of Erlangs supported by a C7 link is given by:
= 150 Erlangs.
Maximum number of Erlangs supported by a GPROC supporting a C7 signalling link is given by:
= 560 Erlangs.
Hence:
Amount of traffic (or number of trunks) each logical link will hold:
using a MTL load sharing granularity of 16.

The number of logical links each MTL can handle:
_ _
The number of required MTLs:
Check that the figure is within limits.
68P02900W21-R 9-27
28 Feb 2006 GMR-01
Determining the number of LCFs for MTL processing

Using the formula detailed in Chapter 6, "BSC planning steps and rules,", since:
XBL requirements
Referring to Table 6-10 in Chapter 6, "BSC planning steps and rules,",
Number of XBLs required = 2.
GPROC requirements
Number of GPROCs required for MTL processing = 8.
Number of GPROCs required for RSL processing = 5.
Total number of LCF GPROCs required = 13; check that the figure is within limits.
Number of BSP GPROC3s (with redundancy) = 2.
Number of CSFP GPROCs = 1.
Total number of GPROCs 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 the RXCDR is:
Hence number of MSIs required for BSC to RXCDR interface = 8.

Each BTS site in this example requires one E1 interconnection. Hence the number of MSIs required
for BTSs, is 30/2 = 15.
Total number of MSIs required at the BSC = 23.
KSW/DSW2 requirements
9-28 68P02900W21-R
GMR-01 28 Feb 2006
Number of TDM timeslots is given by:
Where G is the number of GPROCs; M is the number of MSIs, and R is the number of XCDR/GDPs at
the BSC:
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 2 non-redundant KSWs/DSW2s would be required
for this configuration. For redundancy, an additional 2 KSWs/DSW2s are required.
Total KSWs/DSW2s 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):
Ensure the following is true for each shelf:
Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this configuration.
KSWX/DSWX requirements
The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock signals to all
shelves in the multi-shelf configuration. The KSWX/DSWX may be used in expansion, remote and local
modes. We require 3 BSU shelves with 2 non-redundant KSWs/DSW2s, which implies we shall have 1
expansion shelf and 1 extension shelf.
Number of KSWXs/DSWXs required is sum of KSWXE, KSWXR, and KSWXL .
NKXE = K*(K-1) = 2 *1 = 2 ( K is the number of non-redundant KSWs/DSW2s).

NKXR = SE = 1 ( SE is the number of extension shelves).
NKXL = K + SE = 3.
NK X = 2 + 1 + 3 = 6.
Therefore, the number of KSWXs/DSWXs required (with redundancy) = 12.
68P02900W21-R 9-29
28 Feb 2006 GMR-01
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:
Where E is the number of expansion/extension shelves and RF is the redundancy factor:
The number of CLKXs required (with redundancy) = 2.

LANX requirements
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:
Line interfaces
The number of T43 boards required is 8.

Digital power supply requirements
Number of PSUs required is given by:
One redundant PSU is required for each BSU shelf, hence total number of PSUs required is 12.
9-30 68P02900W21-R
GMR-01 28 Feb 2006
Non volatile memory (NVM) board for BSC (optional)
68P02900W21-R 9-31
28 Feb 2006 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:
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.
Each XCDR card terminates one E1 interconnection, 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):
Hence, 4 RXU shelves are required to equip 58 XCDR cards and 8 MSI cards.
GPROC requirements for RXCDR
Each shelf should have minimum of one GPROC. Hence, 4 non-redundant GPROCs are required. If the
operator chooses to use redundancy 8 GPROCs would be required.
KSW/DSW2 requirements for RXCDR
9-32 68P02900W21-R
GMR-01 28 Feb 2006
The number of TDM slots required for GPROCs, MSIs and XCDRs is given by:
Each KSW/DSW2 provides1016 timeslots on the TDM highway, hence, 2 non-redundant KSWs/DSW2s are
required for the RXCDR with this configuration.
KSWX/DSWX requirements for RXCDR
The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. We require 4
RXU shelves with 2 non-redundant KSWs/DSW2s, which implies we shall have 1 expansion shelf and 2
extension shelves.
K is the number of non-redundant KSWs/DSW2s.
SE is the number of extension shelves.
The number of KSWXs/DSWXs (with redundancy) = 16.

GCLK requirements
The generic clock generates all the timing reference signals required by a RXU. One GLCK is required at
each RXCDR.
CLKX requirements
Provides expansion of GCLK timing to more than one RXU.
Where:
68P02900W21-R 9-33
28 Feb 2006 GMR-01
E is the number of expansion/extension shelves.

RF is the redundancy factor.
The number of redundant CLKXs required is 2.

LANX requirements
Number of LANXs required is given by:

Total number of LANXs required with redundancy = 8.
PIX requirements
Hence, 8 PIX cards are required for the RXCDRs.

Line interfaces

One redundant PSU is required for each RXU shelf, hence total number of PSUs required of is 12.
Non volatile memory (NVM) board for RXCDR (optional)
9-34 68P02900W21-R
GMR-01 28 Feb 2006
Planning example 2

• GSM software release = GSR6 (Horizon II) .
• Number of omni 2 sites (BTS: M-Cell2) = 5.

• Ratio of location updates per call = 2.4.
• Ratio of IMSI detaches per call I = 0.2 (type 2).
• Location update factor L = 2.4 + 0.5 * 0.2 = 2.5.
• No. of handovers per call H = 2.6.
• Number of BTS sites B = 55 + 5 = 60.
• Number of cells per BTS CBTS = 3.
• GSM paging rate in pages per second PGSM = 10.
• GPRS paging rate in pages per second PGPRS = 0.
• Mean_TBF_Rate = 1.
• Number of GPRS timeslots NGPRS = 0.
68P02900W21-R 9-35
28 Feb 2006 GMR-01
• Type of combining used = Hybrid (CBF).
• BTS connectivity = Star configuration.
• NVM board fitted at RXCDR.
GSR6 (Horizon II) limitations

• Trunks = 3000.
• C7 links = 16.

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 an omni 2 BTS = 9.83 Erlangs.
9-36 68P02900W21-R
GMR-01 28 Feb 2006
Call arrival rate:
SMS rate:
From the call model parameters, the paging rate PGSM is 8, so the average number of CCCH blocks required to
Using a CCCH utilisation figure (UCCCH) of 0.33, the average number of CCCH blocks required to support
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
68P02900W21-R 9-37
28 Feb 2006 GMR-01
Using the values calculated in the previous section and other call model parameters, the average number
of SDCCHs, NSDCCH, is given by the formula mentioned in Chapter 3:
The number of SDCCHs to support an average number of busy SDCCHs of 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.
9-38 68P02900W21-R
GMR-01 28 Feb 2006
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.
Step 2 : BSS planning - determining the number of RSLs

The number of 64 kbits/sec RSLs required with the given by:
_ _
Where n is the number of TCHs under the BTS. Hence, for a 2/2/2 site (no GPRS):
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
{23769}
_ _
(CS3 and CS4 are not used.)

Number of E1 links required between each omni 2 BTS and BSC:
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.
68P02900W21-R 9-39
28 Feb 2006 GMR-01
Determining the number of LCF GPROCs for RSL processing

Where, n is the number of TCHs under a BSC:
The number of LCFs for RSL processing is 6.

Determining the number of MTLs
Total Erlangs offered by the BSC with 55 sites with 2/2/2 configuration and 5 omni 2 sites:
Total Erlangs carried by the BSC with 55 sites with 2/2/2 configuration and 5 omni 2 site:
The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 1423. Check
figure is within limits.
Using the call model parameters, the number of MTLs can be calculated using formulae mentioned in
Chapter 6 of this manual.
9-40 68P02900W21-R
GMR-01 28 Feb 2006
Maximum number of Erlangs supported by GPROC supporting a C7 signalling link is given by:
Hence:
Amount of traffic (or number of trunks) each logical link will hold:

_ _
Check this figure is within limits.

Determining the number of LCFs for MTL processing
68P02900W21-R 9-41
28 Feb 2006 GMR-01
Using the formula mentioned in Chapter 6, since:
XBL requirements
Number of XBLs required = 2.
GPROC requirements
Number of GPROCs required for MTL processing = 4.
Number of GPROCs required for RSL processing = 5.
Total number of LCF GPROCs required = 9. Check this figure is within limits.
Number of BSP GPROC3s (with redundancy) = 2.
Number of CSFP GPROCs = 1.
Total number of GPROCs for BSC = 13 (12 +1 for redundancy).
9-42 68P02900W21-R
GMR-01 28 Feb 2006
MSI requirements
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/DSW2 requirements
Number of TDM timeslots is given by:
Where G is the number of GPROCs; M is the number of MSIs, and R is the number of GDP/XCDRs in
the BSC.
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s would be required
for this configuration. For redundancy, 3 additional KSWs/DSW2s are required.
Total KSWs/DSW2s 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):
Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this configuration.
68P02900W21-R 9-43
28 Feb 2006 GMR-01
KSWX/DSWX requirements
modes. We require 3 BSU shelves with 3 master/ redundant KSWs/DSW2s, which implies 2 expansion
shelves.
Number of KSWXs/DSWXs required is sum of KSWXE, KSWXR, and KSWXL:
NKX = NKXE + NKXR + NKXL.

NKXE = K*(K-1) = 3 *2 = 6 ( K is the number of non-redundant KSWs/DSW2s).
NKXL = K + SE = 3.
NK X = 6 + 0 + 3 = 9.
The number of KSWXs/DSWXs required (with redundancy) = 18.
GCLK requirements
each BSC.
CLKX requirements
Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is given by:
Where E is the number of expansion/extension shelves and RF is the redundancy factor.
The number of CLKX required (with redundancy) = 2.

LANX requirements
Where, RF it the redundancy factor.

PIX requirements
9-44 68P02900W21-R
GMR-01 28 Feb 2006
Line interfaces

The number of PSUs required is given by:
One redundant PSU is required for each BSU shelf, hence total number of PSUs required is 9.
Non volatile memory (NVM) board for BSC (optional)
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
Where:
C is the number of MTL links required.
X is the number of OML links required.
68P02900W21-R 9-45
28 Feb 2006 GMR-01
T is the number of trunks between MSC and BSC.
Each XCDR card terminates one E1 interconnect.

Hence, the number of non-redundant XCDR cards required is 47.
9-46 68P02900W21-R
GMR-01 28 Feb 2006
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):
Hence, 3 RXU shelves are required to equip 47 XCDR cards and 6 MSI cards.
GPROC requirements for RXCDR
KSW/DSW2 requirements for RXCDR
Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by:
Each KSW/DSW2 provides1016 timeslots on the TDM highway, hence, 2 non-redundant KSWs/DSW2s
are required for RXCDR with this configuration.
KSWX/DSWX requirements for RXCDR
68P02900W21-R 9-47
28 Feb 2006 GMR-01
The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. The above
calculations imply 1 expansion and 1 extension shelf are required.
The number of KSWXs/DSWXs (with redundancy) = 12.

GCLK requirements
The generic clock generates all the timing reference signals required by a RXU. One GLCK is required at
each RXCDR.
CLKX requirements
Provides expansion of GCLK timing to more than one RXU:
Where:
The number of redundant CLKXs required is 2.

LANX requirements
9-48 68P02900W21-R
GMR-01 28 Feb 2006

PIX requirements
Hence, 6 PIX cards are required for RXCDR.

Line interfaces

One redundant PSU is required for each RXU shelf, hence total number of PSUs required is 9.
Non volatile memory (NVM) board for RXCDR (optional)
68P02900W21-R 9-49
28 Feb 2006 GMR-01
Planning example 3

• GSM software release = GSR7.
• No AMR support.
• No Enhanced Capacity mode support.

• Ratio of IMSI detaches per call I = 0.
• Location update factor L = 2.4 + 0.5 * 0 = 2.4.
• Paging rate per second PGSM = 8 pages per second.
• Number of cells at the BTS CBTS = 3.
9-50 68P02900W21-R
GMR-01 28 Feb 2006
• NVM board fitted at BSC and RXCDR.
GSR7 limitations (assuming big BSC system)

• Trunks = 3200.
• C7 links = 16.

From Erlang B tables, the number of Erlangs supported by 48 TCHs (6 carrier cell) with GOS of 2% is
38.39 Erlangs.
68P02900W21-R 9-51
28 Feb 2006 GMR-01
Call arrival rate:
SMS rate:
From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks required to
grant messages.
The number of SDCCHs to support an average number of busy SDCCHs of 8.126 Erlangs signalling traffic
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 max. 8 SDCCHs.
9-52 68P02900W21-R
GMR-01 28 Feb 2006

is 3 (1 non-combined BCCH timeslot with 9 CCCHs and 2 timeslots with 8 SDCCHs each).
Therefore, the number of traffic channels per 6 carrier cell = 48 — 3 = 45.
Hence, traffic offered by a 6-carrier cell is 35.61 Erlangs (45 traffic channels at 2% GOS). Carried Erlangs is
34.90 Erlangs.
Total channels/carrier = 48
Total traffic channels (voice) = 45
Control/signalling channels = 3
68P02900W21-R 9-53
28 Feb 2006 GMR-01
Step 2 : BSS planning

The major steps for planning the BSC system include:
1. The number of RSL links between the BSC and BTSs.
2. The number of E1 links between BSC and BTSs.
3. The number of LCFs for RSL processing.
4. The number of MTL links between BSC and MSC.
5. The number of LCFs for MTL processing.
6. The number of XBL links between BSC and RXCDR.
7. The number of GSL links between BSC and RXCDR.
8. The number of GPROCs.
9. The number of XCDR/GDP/GDP2s.
10. The number of MSI cards.
11. The number of KSWs/DSW2s.
12. The number of BSU shelves.
13. The number of KSWXs/DSWXs.
14. The number of GCLKs.
15. The number of CLKXs.
16. The number of LANXs.
17. The number of PIXs.
18. The number of line interface cards (T43s).
19. The number of digital power supplies.
20. Whether or not an optional NVM board is fitted.
9-54 68P02900W21-R
GMR-01 28 Feb 2006
Step 1. RSL requirements

The number of 64 kbit/s RSLs required with the given by:
_ _
Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (no GPRS):
The number of RSLs required per 6/6/6 site is 2.

Step 2. BSC to BTS E1 interconnect planning
{23769}
_ _
Hence, 2 E1 interconnections are required between each BTS and BSC for the given site configurations
(provided they are in star configurations). There are total of 20 * 2 = 40 E1 links needed.
The number of E1s between the BSC and BTS is 40.
Step 3. Determining the number of LCF GPROCs for RSL processing
68P02900W21-R 9-55
28 Feb 2006 GMR-01
Step 4. Determining the number of MTLs

Total Erlangs offered by the BSC with 20 sites with 6/6/6 configuration:
Total Erlangs carried by the BSC with 20 sites with 6/6/6 configuration:
The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2165 (using
offered Erlangs to calculate). Verify that this figure is within limits ( < 3200 for a big BSC system).
9-56 68P02900W21-R
GMR-01 28 Feb 2006
Maximum number of Erlangs supported by GPROC supporting a C7 signalling link is given by:
Hence:
Amount of traffic each logical link will hold:

_ _
Check this figure is within limits (<16).

The number of MTLs required = 9.
Step 5. Determining the number of LCFs for MTL processing
68P02900W21-R 9-57
28 Feb 2006 GMR-01
Using the formula mentioned in Chapter 6, since:
Step 6. XBL requirements

Number of XBLs required = 2 (using N = 2165).
Step 7. GSL requirements
N/A (signalling links between BSC and PCU).
Step 8. GPROC requirements
To determine the number of GPROCs:
B = Number of BSP GPROC3s (x 2 for redundancy) = 3.
A total of 3 BSU shelves are required and each shelf must have at least one GPROC (x 2 for
redundancy).
L = Total number of LCF GPROCs required = 5.
C = Number of CSFP GPROCs (optional) = 0.
R = Number of pool GPROCs (for redundancy) = 1.
Total number of GPROCs for BSC = (2 * 3 + 5 +0 + 1) = 12.
Step 9. XCDR/GDP/GDP2 requirements
N/A (no local RXCDR).
Step 10. MSI requirements
NMSI = Number of MSIs required.
9-58 68P02900W21-R
GMR-01 28 Feb 2006
NBSC-RXCDR = Number of E1 links required.

PHR in the above equation is not considered in non-AMR cases.

Hence the number of MSIs required for the BSC to RXCDR interface is 18/2 = 9.
Each BTS site in this example requires two E1 interconnections. Hence the number of MSIs required
for BTSs is 20 * 2 / 2 = 20.
Total number of MSIs required at the BSC = 20 + 9 = 29.
Step 11. KSW/DSW2 requirements
Determine the number of KSWs/DSW2s (N) required:
G = the number of GPROCs.

n = 16 or 32 (16 in this example).
RGDP2 = N/A in this example (RXCDR case).
M = the number of MSIs (29).
RGDPXCDR and REGDP are not considered in the above equation.

Therefore the total number of timeslots required is:
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s are required for
this configuration. For redundancy, 3 additional KSWs/ DSW2s are required.
Thus total KSWs/DSW2s required (with redundancy) = 3 + 3 = 6.
68P02900W21-R 9-59
28 Feb 2006 GMR-01
Step 12. BSU shelves

Each BSU shelf can support up to 12 MSI cards. A total of 29 MSI cards are required, based on the previous
calculation. The total number of BSU shelves required is:
Total GPROCs = 12 and total MSIs = 29, split between 3 BSU shelves:
BSU 1 BSU 2 BSU 3 Check Limit

GPROCs 4 4 4 < =8
MSI cards 12 9 8 < = 12
i.e.
Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration
is NBSU = 3.
9-60 68P02900W21-R
GMR-01 28 Feb 2006
Step 13. KSWX/DSWX requirements

KSWXs/DSWXs should be considered for this example as the configuration requires more than one shelf.
modes. We require 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies 2 expansion shelves.
The number of KSWXs/DSWXs required (NKX) is sum of KSWXDSWXE, KSWX/DSWXR, and
KSWX/DSWXL:
NKXE = K*(K-1) = 3 *2 = 6 ( K is the number of non-redundant KSWs).

NKXL = K + SE = 3.
NK X = 6 + 0 + 3 = 9.
The maximum number of KSWX/DXWX slots per shelf <=18.

KSWXs and DSWXs may be used together in a shelf, provided that they are used with like pairs,
i.e. KSWX connected to KSWX and DSWX connected to DSWX.
Step 14. GCLK requirements
each BSC.
The number of GCLKs required (with redundancy) = 2.
Step 15. CLKX requirements
68P02900W21-R 9-61
28 Feb 2006 GMR-01
Step 16. LANX requirements

Step 17. PIX requirements
Step 18. Line interfaces

Step 19. Digital power supply requirements
One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is:
The total number of PSUs required is 9.

Step 20. Non volatile memory (NVM) board for BSC (optional)
An NVM board is required in this example, so NVM = 1.
9-62 68P02900W21-R
GMR-01 28 Feb 2006
Step 3: RXCDR planning

The following planning steps will be performed (for this example):
1. The number of links between the RXCDR and BSC.
2. The number of E1 links between the RXCDR and MSC.
3. The number of XCDR/GDP2/GDP2s.
4. The number of GPROCs.
5. The number of MSIs.
6. The number of KSWs/DSW2s.
7. The number of RXU shelves.
13. The number of line interface boards (T43s).
14. The number of digital power supply units.
Step 1. Determining the number of E1 links between the RXCDR and BSC
See Step 10 in the previous section (9 MTLs x 2).

Step 2. Determining the number of E1 links between the RXCDR and MSC
Where:
C is the number of MTL links required (9).
X is the number of OML links required (2).
68P02900W21-R 9-63
28 Feb 2006 GMR-01
T is the number of trunks between MSC and BSC (2165).
The number of E1 links between the RXCDR and MSC = 71.

Step 3. Determining the number of XCDR/GDP/GDP2 cards
Each XCDR/GDP/GDP2 terminates one E1 link (for the RXU shelf).
Hence, the number of non-redundant cards required is 47, which can be a mix of XCDRs, GDPs and GDP2s.
The number of non-redundant XCDR/GDP/GDP2 cards = 47.
Step 4. GPROC requirements for RXCDR
The number of GPROCs required for RXCDR = 5 + 5 (for redundancy) = 10.
Step 5. MSI Requirements for RXCDR
links, hence, 9 MSI cards are required on the RXCDR.
MSI requirements for RXCDR = 9.
Step 6. KSW/DSW2 requirements for RXCDR
Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by:
Each KSW/DSW2 provides1016 timeslots on the TDM highway, hence, 3 non-redundant KSWs/DSW2s
are required for RXCDR with this configuration.
KSWs/DSW2s required for the RXCDR = 3 + 3 (redundant) = 6.
Step 7. RXU shelves
The number of RXU shelves required is given by (assumes an NVM board is fitted):
9-64 68P02900W21-R
GMR-01 28 Feb 2006
RXU 1 RXU 2 RXU 3 RXU 4 RXU 5

MSIs 1 2 2 2 2
XCDRs/GDPs 7 7 7 7 7
GDP2s 7 7 7 7 8
GPROCs 2 2 2 2 2
Hence, 5 RXU shelves are required to equip 71 XCDR/GDP/GDP2 cards and 9 MSI cards.
The number of RXU shelves required = 5.
Step 8. KSWX/DSWX requirements for RXCDR
The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and
KSWX/DSWXL. The above calculations imply 2 expansion and 2 extension shelves are required.
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26.
68P02900W21-R 9-65
28 Feb 2006 GMR-01
The generic clock generates all the timing reference signals required by an RXU. One GLCK is required at
each RXCDR.
Number of GCLKs required = 1 + 1 (redundant) = 2.
Provides expansion of GCLK timing to more than one RXU:
Where:
The number of CLKXs required = 1 + 1 (redundant) = 2.


Hence, 10 PIX cards are required for the RXCDR.

The number of T43 boards required = 15.

One redundant PSU is required for each RXU shelf, hence total number of PSUs required = 15.
9-66 68P02900W21-R
GMR-01 28 Feb 2006
Step 15. Non volatile memory (NVM) board for RXCDR (optional)
68P02900W21-R 9-67
28 Feb 2006 GMR-01
Planning example 4 (using AMR)

• GSM software release = GSR{25779}8.
• AMR MS penetration rate = 35% (AMR fr/hr-capable MSs).
• Total AMR hr usage PHR = 50% * PAMR = 18% (among all MSs).
• BSS provides additional ~35% voice traffic supported AMR hr.
• GPROC3 is {25779} mandatory for the BSP.
• GDP2 is considered to support AMR hr.
• New RXCDR shelf is mandatory.
• No local XCDR.
• 8K/16K switching is used, (needs DSW2 support).
• No enhanced capacity mode support.
• No GPRS in the system.
9-68 68P02900W21-R
GMR-01 28 Feb 2006

• Ratio of IMSI detaches per call I = 0.
• Location update factor L = 2.4 + 0.5 * 0 = 2.4.
• Paging rate per second PGSM = 8 pages per second.
• Number of cells at the BTS CBTS = 3.
68P02900W21-R 9-69
28 Feb 2006 GMR-01
• NVM board fitted at BSC and RXCDR.
GSR{25779} 8 limitations (assuming big BSC system)

• Trunks = 3200.
• C7 links = 16.
9-70 68P02900W21-R
GMR-01 28 Feb 2006
Step 1 : Cell planning - control channel calculations (based on Erlang B models)

All full rate AMR (hr) Carrier
Total AMR Total Sig- Total Total Sig- Total AMR AMR
Carri- HR/ TCH nalling Voice TCH nalling Voice HR HR
ers Carriers / Con- TCH /Control TCH TCH TCH %
trol TCH
TCH
6 1/6 48 3 45 56 3 53 16 30.2
6 2/6 48 3 45 64 4 60 32 53.3
6 3/6 48 3 45 72 4 68 48 70.6
6 4/6 48 3 45 80 4 76 64 84.2
6 5/6 48 3 45 -88 -4 -84 -80 95.2
6 6/6 48 3 45 96 4 88 88 100
For purposes of planning it is assumed that the AMR-capable MSs will be using AMR FR channels, and that
hr will be used under conditions of congestion. The estimated AMR penetration rate is 35%, of which half of
those calls may be in half rate mode due to congestion (as given in the assumptions), yielding about 18% of
the calls in half rate mode. From the pre-calculated table above it can be seen that 1 half rate enabled carrier
would provide about 30% AMR half rate channels. However, to allow for future growth in the penetration
level and to allow for a greater margin of safety, 2 half rate enabled carriers will be assumed for the
remainder of this exercise.
68P02900W21-R 9-71
28 Feb 2006 GMR-01
Call arrival rate:
SMS rate:
From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks required to
grant messages.
The number of SDCCHs to support an average number of busy SDCCHs of 11.31 Erlangs signalling traffic
with less that 1% blocking as determined by use of Erlang B tables is 18. Hence, the number of timeslots
required to carry SDCCH signalling traffic is 3 with each timeslot offering max. 8 SDCCHs.
is 4 (1 non-combined BCCH timeslot with 9 CCCHs and 3 timeslots with 8 SDCCHs each).
9-72 68P02900W21-R
GMR-01 28 Feb 2006
Therefore, the number of traffic channels per 6 carrier cell (4 fr carriers + 2 hr carriers) = 4 * 8 + 16 * 2 - 4 = 60.
Hence, traffic offered by a 6-carrier cell is 49.64 Erlangs (60 traffic channels at 2% GOS). Carried Erlangs is
49.64 * 98% = 48.65 Erlangs.
Total Erlangs offered by the BSC with 20 sites with 6/6/6 configuration:
The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 3003. Check
this is within the limit of <=3200.
If the number of trunks (3003) had exceeded the limit, but by a small number (less than a quarter of a percent
or so) it could be considered negligible and planning could continue. However, there is an alternative
approach, particular to half rate usage, which is discussed here. In fact, we will assume the trunk limit
was 3000 in order to provide a working example.
The carried Erlangs were calculated using worst case planning. It was assumed that all AMR half rate enabled
carriers would, worst case, be handling all AMR half rate calls. However, given that the AMR-capable
mobile penetration is 35%, it’s unlikely that all the AMR half rate enabled carriers will be carrying all half
rate traffic. Certainly, exclusive (forced) AMR half rate usage could have been assumed (in which case the
AMR hr TCH % should be used to calculate the number of (total and AMR half rate enabled) carriers
required) but that is not the assumption made here.
The approach used here is to relax the AMR half rate usage assumption enough to satisfy the trunking limit,
yet provide a large margin of safety as AMR penetration grows.
A minimal assumption is made, that one of the AMR HR carriers will carry 14 HR calls and 1 FR call. This
yields the following:
1 HR carrier = 16 AMR HR TCH = 14 AMR HR TCH + 1 FR TCH = 15 TCH
The total # of AMR voice TCH = 4 * 8 + 1 * 16 + 14 TCH + 1 - 4 = 59
The traffic offered by a 6 carrier/cell is (based on 59 TCH with 2% of GOS)
= 48.70 Erlangs.
Carried Erlangs by such system configuration (per BTS) = 48.70 *98%
= 47.73 Erlangs.
20 * 3 * 48.70 = 2922 Erlangs
The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2946.
68P02900W21-R 9-73
28 Feb 2006 GMR-01
This alternatively calculated number (2946) will be used for the remainder of the calculations in this section.
# of sites (BTS) per BSC: 20

# of cells per BTS: 3
# of carriers per cell: 6
# TCHs per carrier: 63 (AMR HR, AMR FR, GSM FR/EFR, etc.)
# Control channels per carrier: 4
# of available voice TCH: 59 (30 AMR HR + 29 FR)
# of Erlangs offered per BTS: 48.70
# of Erlangs carried per BTS: 47.73
# of Erlangs offered by this BCS system: 20 * 3 * 48.70 = 2922
# of trunks to carry such traffic: (using Erlangs B calculation) 2946
9-74 68P02900W21-R
GMR-01 28 Feb 2006
Step 2 : BSS planning

The major steps for planning the BSC system include:
1. The number of RSL links between the BSC and BTSs.
2. The number of E1 links between BSC and BTSs.
3. The number of LCFs for RSL processing.
4. The number of MTL links between BSC and MSC.
5. The number of LCFs for MTL processing.
6. The number of XBL links between BSC and RXCDR.
7. The number of GSL links between BSC and RXCDR.
8. The number of GPROC3s.
10. The number of MSI cards.
11. The number of DSW2s.
12. The number of BSU shelves.
18. The number of line interface cards (T43s).
19. The number of digital power supplies.
68P02900W21-R 9-75
28 Feb 2006 GMR-01
Step 1. RSL requirements

The number of 64 kbit/s RSLs required with the given by:
_ _
Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (with AMR but no GPRS):
The number of RSLs required per 6/6/6 site (with 2 carriers of AMR HR) = 2.
Step 2. BSC to BTS E1 interconnect planning
{23769}
_ _
Hence, 2 E1 interconnections are required between each BTS and BSC for the given site configurations
(provided they are in star configurations). There are total of 20 * 2 = 40 E1 links needed.
The number of E1s between the BSC and BTS is 40.
Step 3. Determining the number of LCF GPROCs for RSL processing
Number of LCF-RSLs required assuming only GPROC3s are used is given by:
9-76 68P02900W21-R
GMR-01 28 Feb 2006
Step 4. Determining the number of MTLs

The number of trunks required to carry traffic on the A-interface with less than 1% blocking is 2946.
Maximum number of Erlangs supported by a GPROC3 supporting a C7 signalling link is given by:
Hence, for GPROC3 only:
Amount of traffic each logical link will hold:
68P02900W21-R 9-77
28 Feb 2006 GMR-01
_ _
Check this figure is within limits (<12).

The number of MTLs required = 9.
Step 5. Determining the number of LCFs for MTL processing
If GPROC3s are used exclusively:
The number of LCFs for MTL processing = 3.

Step 6. XBL requirements
The required number of XBLs is given by:

Number of 64 kbit/s XBLs required = 3 (6 with redundancy).
Step 7. GSL requirements
N/A (signalling links between BSC and PCU not considered in this example).
9-78 68P02900W21-R
GMR-01 28 Feb 2006
Step 8. GPROC3 requirements

To determine the number of GPROC3s:
B = Number of BSP GPROC3s (x 2 for redundancy) = 3.
A total of 3 BSU shelves are required and each shelf must have at least one GPROC3 (x 2 for
redundancy).
L = Total number of LCF GPROC3s required = 3.
C = Number of CSFP GPROC3s (optional) = 1.
R = Number of pool GPROC3s (for redundancy) = 1.
Total number of GPROC3s (exclusively) for BSC = (2 * 3 + 3 +1 + 1) = 11.
Step 9. XCDR/GDP/GDP2 requirements
N/A (no local RXCDR).
Step 10. MSI requirements
NMSI = Number of MSIs required.

NBSC-RXCDR = Number of E1 links required.
Hence the number of MSIs required for the BSC to RXCDR interface is 25/2 = 13.
Each BTS site in this example requires two E1 interconnections. Hence the number of MSIs required
for BTSs is 20 * 2 / 2 = 20.
68P02900W21-R 9-79
28 Feb 2006 GMR-01
The assumptions are that the system starts allocating AMR HR resources (for AMR HR-capable
MSs through HO procedures) when certain congestion thresholds are reached. Assuming that
50% of AMR-capable MSs are able to HO to HR (total about 18% MSs among all MSs).
Total number of MSIs required at the BSC = 13 + 20 = 33.
Step 11. DSW2 requirements
Extended subrate switching mode (8 kbit/s switching) is required, so DSW2s are used. Determine the
number of DSW2s (N) required:
G = the number of GPROC3s (11).

n = 16 or 32 (16 in this example).
RGDPXCDR = N/A in this example.
REGDP = N/A in this example.
RGDP2 = N/A in this example.
M = the number of MSIs (33).
Therefore the total number of timeslots required is:
Each DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant DSW2s are required for this
configuration. For redundancy, 3 additional DSW2s are required.
Thus total DSW2s required = 3 + 3 (redundant) = 6.
Step 12. BSU shelves
Each BSU shelf can support up to 12 MSI cards. A total of 33 MSI cards are required, based on the previous
calculation. The total number of BSU shelves required is:
Total GPROC3s = 11 and total MSIs = 33, split between 3 BSU shelves:
BSU 1 BSU 2 BSU 3 Check Limit

GPROC3s 4 4 3 < =8
MSI cards 11 11 11 < = 12
9-80 68P02900W21-R
GMR-01 28 Feb 2006
i.e.
Therefore, the number of BSU shelves required to accommodate all the hardware needed for this configuration
is NBSU = 3.
Step 13. KSWX/DSWX requirements
KSWXs/DSWXs should be considered for this example as the configuration requires more than one shelf.
modes. We require 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies 2 expansion shelves.
The number of KSWXs/DSWXs required (NKX) is sum of KSWXDSWXE, KSWX/DSWXR, and
KSWX/DSWXL:
NKXE = K*(K-1) = 3 *2 = 6 ( K is the number of non-redundant KSWs).

NKXL = K + SE = 3.
NK X = 6 + 0 + 3 = 9.
The maximum number of KSWX/DXWX slots per shelf <=18.

each BSC.
The number of GCLKs required (with redundancy) = 2.
68P02900W21-R 9-81
28 Feb 2006 GMR-01



9-82 68P02900W21-R
GMR-01 28 Feb 2006

One redundant PSU is required for each BSU shelf, hence the total number of PSUs required is:
The total number of PSUs required is 9.

Step 20. Non volatile memory (NVM) board for BSC (optional)
An NVM board is required in this example, so NVM = 1.
68P02900W21-R 9-83
28 Feb 2006 GMR-01
Step 3: RXCDR planning

The following planning steps will be performed (for this example):
1. The number of links between the RXCDR and BSC.
2. The number of E1 links between the RXCDR and MSC.
4. The number of GPROC3s.
5. The number of MSIs.
6. The number of DSW2s.
7. The number of RXU3 shelves.
13. The number of line interface boards (T43s).
14. The number of digital power supply units.
Step 1. Determining the number of E1 links between the RXCDR and BSC
See Step 10 in the previous section.

Step 2. Determining the number of E1 links between the RXCDR and MSC
Where:
C is the number of MTL links required (9).
X is the number of OML links required (2).
9-84 68P02900W21-R
GMR-01 28 Feb 2006
T is the number of trunks between MSC and BSC (2165).
The number of E1 links between the RXCDR and MSC = 96.

Step 3. Determining the number of XCDR/GDP/GDP2 cards
Each XCDR/GDP/GDP2 card terminates 2 E1 links in the RXU3 shelf.
Hence, the number of non-redundant cards required = 96/2 = 48, which can be a mix of XCDRs, GDPs
and GDP2s.
The GDP cards can be retained for the existing FR traffic, we only need to allocate enough
GDP2 cards for the additional AMR HR traffic.
During the system planning exercise, we learned that 31 AMR HR channels are needed to support AMR HR
calls (among 2 carriers/6 carriers/cell). There are a total of 59 TCHs for voice traffic among 6 carriers/cell.
Therefore the number of GDP2 cards needed to support AMR HR traffic is:
30/59 (% AMR HR TCH) * 2946 (total trunks in BSC)/60 (GDP2 carries 60 calls) = GDP2 = 25.
XCDR/GDP/GDP2 Total number needed No. of E1s supported

GDP2 cards 25 (each GDP2 can offer 60 25 * 2 = 50
voice calls in RXU3 shelf
(with enhanced capacity mode
enabled) for AMR HR or FR
voice calls).
XCDR/GDP cards 46 (each card supports 30 FR 46 * 1 = 46
voice traffic calls).
Total no. of cards (mix) 71
Total E1s supported 96
Step 4. GPROC3 requirements for RXCDR

Each shelf should have minimum of one GPROC3. Hence, 5 non-redundant GPROCs are required. If the
operator chooses to use redundancy 10 GPROC3s would be required.
The number of GPROC3s required for RXCDR = 5 + 5 (for redundancy) = 10.
Step 5. MSI Requirements for RXCDR
links, hence, 13 MSI cards are required on the RXCDR.
MSI requirements for RXCDR = 13.
68P02900W21-R 9-85
28 Feb 2006 GMR-01
Step 6. DSW2 requirements for RXCDR
No enhanced capacity mode is assumed as timeslot usage per shelf is not a limiting factor in
this configuration.
Number of TDM slots required for the GPROC3s, MSIs and XCDRs is given by:
Each DSW2 provides1016 timeslots on the TDM highway, hence, 3 non-redundant DSW2s are required
for RXCDR with this configuration.
DSW2s required for the RXCDR = 3 + 3 (redundant) = 6.
Step 7. RXU3 shelves
The number of RXU3 shelves required is given by (assumes an NVM board is fitted):
Possible configurations:
RXU 1 RXU 2 RXU 3 RXU 4 RXU 5

MSIs / 2 E1s 3 3 2 2 3
(M)
GDP2s (R) 5 5 5 5 5
GDPs (R) 9 9 9 9 10
Hence, 5 RXU3 shelves are required to equip 71 transcoder cards and 13 MSI cards.
The number of RXU3 shelves required = 5.
9-86 68P02900W21-R
GMR-01 28 Feb 2006
Step 8. KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and
KSWX/DSWXL. The above calculations imply 2 expansion and 2 extension shelves are required.
K is the number of non-redundant DSW2s.
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26.
The generic clock generates all the timing reference signals required by the RXU3. One GLCK is required at
each RXCDR.
Number of GCLKs required = 1 + 1 (redundant) = 2.
68P02900W21-R 9-87
28 Feb 2006 GMR-01

Provides expansion of GCLK timing to more than one RXU3:
Where:
The number of CLKXs required = 1 + 1 (redundant) = 2.


Hence, 10 PIX cards are required for the RXCDR.

The number of T43 boards required = 15.

One redundant PSU is required for each RXU3 shelf, hence total number of PSUs required = 15.
9-88 68P02900W21-R
GMR-01 28 Feb 2006
Step 15. Non volatile memory (NVM) board for RXCDR (optional)
68P02900W21-R 9-89
28 Feb 2006 GMR-01
A planning example of BSS support for LCS provisioning Chapter 9: Planning exercises
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 6.
Typical parameter values
Use this example to plan the equipment of a BSC supporting a traffic model with the parameters listed
in Table 9-10 and their typical values.
This example is for 28 sites/BSC with 3 cells/BTS and 4 carriers/cell.
Table 9-10 Typical LCS call model parameters
Parameter Value
Maximum trunks between MSC and BSC N=3000
Number of BTSs per BSS 28 4*4*4 sites
Number of cells per BSS 28*3
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
9-90 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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.
68P02900W21-R 9-91
28 Feb 2006 GMR-01
Step 2: Calculate MTLs (actually needed trunks number is 1812)
= 151.486
= 559.268
_ _
Finally, the number of required MTLs with 64 logical links is:
_ _
Step 3: Calculate MTL LCFs
9-92 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning A planning example of BSS support for LCS provisioning
Step 4: Calculate RSLs

According to Chapter 3, TCHs per BTS is 29*3. Then,
= 0.87
Step 5: Calculate RSL LCFs
= 3.90
So the RSL LCFs number is 4.
Step 5: Calculate LMTLs
_ _
_
=1
Step 6: Calculate LMTL LCFs

NLCF_LSL = 1.
68P02900W21-R 9-93
28 Feb 2006 GMR-01
9-94 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
10
Location area planning
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
A description of location area planning, by example, is provided here. This exercise should be undertaken
by each operator to optimize the network configurations based on the paging load on the BSC. The topics
described here are as follows:
• "Location area planning considerations" on page 10-2
• "Location area planning calculations" on page 10-3
68P02900W21-R 10-1
28 Feb 2006 GMR-01
Location area planning considerations Chapter 10: Location area planning
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 (LCF GPROCs) 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.
10-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Location area planning calculations
Location area planning calculations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Example procedure
Assume a network with four BSCs under a location area (see Figure 10-1) each with following call model
parameters:
• No. of SMSs per call S = 0.05.
• No. of location updates per call = 2.
• IMSI detaches per call Id = 0.2 (type 2).
• Location update factor = 2 + 0.5*0.2 = 2.1.
• No. of handovers per call H = 2.
• Number of intra-BSC handovers to all handovers i = 0.4.
• MTL link utilisation = 20%.
• RSL link utilisation = 25%.
• CCCH utilisation = 33%.
• Probability of blocking TCH P B-TCH < 2%.
• Probability of blocking SDCCH P B-SDCCH < 1%.
• Paging repetition = 1.2.
• 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.
68P02900W21-R 10-3
28 Feb 2006 GMR-01
Location area planning calculations Chapter 10: Location area planning
Figure 10-1 Four BSCs in one LAC
MSC
LAC=1
BSC BSC BSC BSC
The paging rate in the location area can be calculated by:
Now, calculate the number of GPROC LCF-RSLs required with this paging load using the formula detailed in
Chapter 6:
The number of GPROCs required for RSL is 5.

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:
10-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Location area planning calculations
Call arrival rate:
Ratio of SMSs to call:
Ratio of location updates to calls:
The average number of SDCCHs, NSDCCH is given by:
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 10-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).
Figure 10-2 Four BSCs divided into two LACs
MSC
LAC = 1 LAC = 2
BSC BSC BSC BSC
68P02900W21-R 10-5
28 Feb 2006 GMR-01
Location area planning calculations Chapter 10: Location area planning
Location update factor:
Since the location area now has two BSCs, the paging rate is given by:
The number of GPROC LCFs required for RSL (using the formula) = 4.70 = 5.
Call arrival rate:
Ratio of SMSs to call:
Ratio of location updates to calls:
The average number of SDCCHs for border cells, NSDCCH is given by :
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.
10-6 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
11
Deriving call model parameters from
network statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The derivation of call model parameter values from the GSM network statistics collected at the OMC-R are
described here. 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.
The topic is described in "Deriving call model parameters from network statistics" on page 11-2.
68P02900W21-R 11-1
28 Feb 2006 GMR-01
Deriving call model parameters from network statistics Chapter 11: Deriving call model parameters from network statistics
Deriving call model parameters from network

statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Standard call model parameters
Table 11-1 lists the standard call model parameters.
Table 11-1 Typical parameters for BTS call planning

area (see below)
second
Note)
Percent link utilization (MSC to BSS) for U(MSC - BSS) = 0.20
GPROC2/GPROC3
Percent link utilization (BSC to BTS) U(BSC - BTS) = 0.25
GPROC2/GPROC3
Cont.
11-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Deriving call model parameters from network statistics

GPRS parameters
CS3 = 15.8 kbit/s
CS4 = 21.8 kbit/s
EGPRS parameters
Average packet size (bytes) - Uplink PKULSIZE = 287
Average packet size (bytes) - Downlink PKDLSIZE = 700
Traffic per sub/BH (kbytes/hr) - Uplink ULRATE = 39
Traffic per sub/BH (kbytes/hr) - Downlink DLRATE = 85
Cont.
68P02900W21-R 11-3
28 Feb 2006 GMR-01

Coding scheme rates (MCS1 to MCS9) at the MCS1 = 10.55 kbit/s
RLC/MAC layer MCS2 = 12.95 kbit/s
MCS3 = 16.55 kbit/s
MCS4 = 19.35 kbit/s
MCS5 = 23.90 kbit/s
MCS6 = 31.10 kbit/s
MCS7 = 46.9 kbit/s
MCS8 = 56.5 kbit/s
MCS9 = 61.30 kbit/s

L is a function of l, I and whether short message sequence (type 1) or long message sequence (type 2) is used
for IMSI detach. Typically Ι = 0 (disabled), but when it is enabled:
Type 1: L = I + 0.2 * I
Type 2: L = I + 0.5 * I
11-4 68P02900W21-R
GMR-01 28 Feb 2006
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:
_ _ _ _ _
_ _
Where: is:
N 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.
68P02900W21-R 11-5
28 Feb 2006 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:
_ _ _ _ _ _ _ _ _
_ _
Where: is:
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.
11-6 68P02900W21-R
GMR-01 28 Feb 2006
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:
_ _ _ _ _ _ _ _ _ _ _ _
_ _
Where: is:
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.
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.
68P02900W21-R 11-7
28 Feb 2006 GMR-01
Ratio of intra BSS handovers to all handovers (i)
Using the statistics previously detailed, this ratio can be calculated for a cell as follows:
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
Where: is:
N the number of cells under the BSC.
i should be averaged over all the cells in the network.
Ratio of location updates per call (I)
The ratio of location updates per call, for a cell, may be calculated using the following formula:
_ _
_ _
Where: is:
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 handover during
assignment procedure.
I ratio should be averaged over all the BSCs in the network.
11-8 68P02900W21-R
GMR-01 28 Feb 2006
Ratio of IMSI detaches per call (I)
IMSI detaches is 0 if disabled. If enabled, it may be calculated per cell as follows:
_ _ _
_ _
Where: is:
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 handover during
assignment procedure.
I should be averaged over all the BSCs in the network.
The location update factor is calculated using the ration of location updates per call (l) and the ratio of IMSI
detaches per call (I). For networks with IMSI detach disabled, 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:
• L = l (IMSI detach disabled, i.e. I = 0)
• L = l + 0.2* I (type 1)
• L = l + 0.5* I (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).
68P02900W21-R 11-9
28 Feb 2006 GMR-01
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 ) GSM
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).
A 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.
_ _ _
_ _ _
Where: is:
PAGE_REQ_FROM_MSC 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.
11-10 68P02900W21-R
GMR-01 28 Feb 2006
Pages per call (P ) PC
Pages per call for a BSC may be calculated as:
_ _ _
_ _
Where: is:
N the number of cells under the BSC.
Alternatively, pages per call may be calculated using the formula:
Where: is:
N the number of MSC-BSC trunks.
T the call duration, in seconds.
Or:
Where: is:
e the BSC Erlang.
68P02900W21-R 11-11
28 Feb 2006 GMR-01
Sample statistic calculations
Table 11-2 shows a sample of statistics collected for one BTS in the BSC for a one hour interval.
Table 11-2 Sample statistics
Statistic Parameter Cell 1 Cell 2 Cell 3

BUSY_TCH_MEAN 9.25 14.94 24.12
TOTAL_CALLS 571 927 1407
SMS_NO_BCAST_MSG 0 0 0
SMS_INIT_ON_SD- 0 15 5
CCH
SMS_INIT_ON_TCH 0 2 0
out_in- 531 1214 141
ter_bss_req_to_msc
out_intra_bss_ho_atmpt 512 747 1844
intra_cell_ho_atmpt 0 0 0
OK_ACC_PROC[loca- 746 1056 268
tion_update]
OK_ACC_PROC[imsi_de- 28 49 76
tach]
PAGE_REQ_FROM_MSC 43696 43696 43696
ASSIGNMENT_REDI- 0 0 0
RECTION
Using the formulae detailed in the previous sections, call model parameters can be calculated as follows:
Call duration (T)

Call duration is given by:
_ _ _ _ _
_ _
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.
11-12 68P02900W21-R
GMR-01 28 Feb 2006
No. of SMSs per call (S)

The number of SMSs per call is given by:
_ _ _ _ _ _ _ _ _
_ _
S = [(0+0+0)+(0+15+2)+(0+5+0)]/(571+927+1407)=0.0075
Ratio of handovers per call (H)

The ratio of handovers per call is given by:
_ _ _ _ _ _ _ _ _ _ _ _
_ _
H=[(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:
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
[(512+0)+(747+0)+(1844+0)] / [(531+512+0)+(1214+747+0)+(141+1844+0)]=0.562
Number of location updates per call (l)

Location updates per call may be calculated as:
_ _ _
_ _
l = (746+1056+268) / (571+927+1407) + 0 + 0 + 0 = 0.712
68P02900W21-R 11-13
28 Feb 2006 GMR-01
IMSI detaches per call (I)

The number of IMSI detaches per call is given by:
_ _ _
_ _
I = (28+49+76) / (571+927+1407 +0 +0 + 0) = 0.052

The location update is given by:
L = 0.712 + 0.5 * 0.052 = 0.738
Paging Rate (PGSM) for a BSC

The paging rate for a BSC (with multiple location areas) can be calculated as:
_ _ _
_ _ _
Since, in this case the BSC has only one location area, PGSM is given by:
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.
11-14 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
12
Standard BSS and Horizon BTS
configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Diagrams of the logical interconnections of the components in various standard BSS and Horizon BTS site
configurations, for macrocell and microcell systems are described here. Typical RF configurations are also
provided.
Older generation (M-Cell) BTS site / RF configurations are provided in Chapter 13, "M-Cell BTS
configurations,".
• "Standard configurations" on page 12-2
• "Typical BSS configurations" on page 12-3
• "Single cabinet BTS configurations" on page 12-7
• "Two cabinet BTS configurations" on page 12-11
• "Three cabinet BTS configurations" on page 12-14
• "Four cabinet BTS configurations" on page 12-19
• "Horizon macrocell RF configurations" on page 12-24
• "Microcell RF configurations" on page 12-87
• "Connecting Horizon II macro cabinets to Horizonmacro cabinets" on page 12-91
• "Connecting Horizon II macro cabinets to M-Cell6 cabinets" on page 12-99
68P02900W21-R 12-1
28 Feb 2006 GMR-01
Standard configurations Chapter 12: Standard BSS and Horizon BTS configurations
Standard configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The examples here 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 Horizon II macro/Horizonmacro BTS configurations, the control
redundancy is depicted only for one Horizon II macro/ Horizonmacro cabinet diagram (see Figure 12-4
and Figure 12-7).
12-2 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Typical BSS configurations
Typical BSS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSC with 24 BTSs
The digital module configuration for a BSC controlling 24 BTSs is shown in Figure 12-1.
68P02900W21-R 12-3
28 Feb 2006 GMR-01
Typical BSS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Figure 12-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 REDUND
ANT
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
GPROC GPROC KSW

BTC GPROC B
0 1 2 REDUNDANT
DUAL MCAP BUS
LANX LANX
A B
DUAL IEEE LAN BSU SHELF 2
BSSC CABINET
12-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Typical BSS configurations
BSC with full redundancy
The digital module configuration for a fully redundant BSC controlling 34 BTSs is shown in Figure 12-2.
Figure 12-2 Fully redundant BSC controlling 34 BTSs
DUAL IEEE LAN LANX LANX

BSU SHELF 1
A B
DUAL SERIAL BUS DUAL MCAP BUS
GPROC GPROC GPROC GPROC KSW KSW GCLK GCLK

PIX BTC 1 2 A B A B
0 3
REDUNDANT A
B
EXP EXP LCL LCL

KSWX KSWX CLKX CLKX BTC MSI MSI MSI MSI
KSWX KSWX
A B A B 0 1 2 9
2 Mbit/s LINKS
BTS 1 BTS 2 BTS 3 BTS 16,17
FIBRE OPTIC LINKS

MSC
2.048 Mbit/s LINK INTERFACES

FROM/TO MSC AND TO/FROM BTS
SITES
BTS 18 BTS 19 BTS 20 BTS 33,34
2 Mbit/s LINKS
EXP EXP LCL LCL

KSW KSWX KSWX KSWX BTC MSI MSI MSI MSI
A B A B 1 2 9
0
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
68P02900W21-R 12-5
28 Feb 2006 GMR-01
Typical BSS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Transcoder
The digital module configuration for a BSSC cabinet equipped to provide transcoding is shown in Figure 12-3.
Figure 12-3 BSSC cabinet equipped to provide transcoding
DUAL IEEE 802.5 LAN LANX

RXU SHELF 1
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 KSWX KSWX BTC MSI MSI XCDR XCDR
CLK CLKX 0
A X A B 1 0 15
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
A
B
BTC GPROC GPROC KSW

0 1 B DUAL MCAP BUS
REDUNDANT
DUAL SERIAL BUS
LANX LANX B
A
DUAL IEEE LAN
RXU SHELF 2
REMOTE TRANSCODER CABINET
12-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Single cabinet BTS configurations
Single cabinet BTS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Single cabinet Horizon II macro BTS
The configuration shown in Figure 12-4 is an example of a one-cabinet Horizon II macro. This configuration
supports six carriers in single density mode or 12 carriers in double density mode.
Figure 12-4 Macrocell BTS with one Horizon II macro cabinet
INTEGRATED INTEGRATED
NIU NIU
HIISC HIISC
(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
2 2 2 2 2 2
Horizon II macro
CABINET
68P02900W21-R 12-7
28 Feb 2006 GMR-01
Single cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Single cabinet Horizon II mini BTS
The configuration shown in Figure 12-5 is an example of a one-cabinet Horizon II mini. This configuration
supports a maximum of 4 carriers.
Figure 12-5 Macrocell BTS with one Horizon II mini cabinet
INTEGRATED INTEGRATED
NIU NIU
HIISC HIISC
(FOR
REDUNDANCY)
4
4
2 2
C C
T T
U U
2 2
2 2
Horizon II mini
CABINET
12-8 68P02900W21-R
GMR-01 28 Feb 2006
Single cabinet Horizon II micro BTS
The configuration shown in Figure 12-6 is an example of a one-cabinet Horizon II micro. This configuration
supports a maximum of 2 carriers.
Figure 12-6 Macrocell BTS with one Horizon II micro cabinet
INTEGRATED
NIU
HIISC
2
2
C
T
U
2
Horizon II micro
CABINET
68P02900W21-R 12-9
28 Feb 2006 GMR-01
Single cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Single cabinet Horizonmacro BTS
The configuration shown in Figure 12-7 is an example of a one-cabinet Horizonmacro. This configuration
supports six carriers.
Figure 12-7 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
If CTUs are replaced with CTU2s from the Horizon II macro, the master (and redundant) MCUF
must have a 20 Mbyte PCMCIA card installed running CSFP to accommodate the added memory
requirements of the GSR6 (Horizon II) objects. Also, the CTU2 only supports baseband hopping
in single density mode when installed in Horizonmacro.
12-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Two cabinet BTS configurations
Two cabinet BTS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Two cabinet Horizon II macro BTS
The configuration shown in Figure 12-8 is an example of a two cabinet Horizon II macro. This configuration
supports 12 carriers in single density mode and 24 carriers in double density mode. The HIISC interfaces to
the CTU2s in the second (slave) cabinet through site expansion boards in both cabinets (connected via fibre
optic cables) and an XMUX replaces the HIISC in the second cabinet.
The site expansion board is optional equipment in the master BTS and is only required when site expansion is
required.
Figure 12-8 Macrocell BTS with two Horizon II macro cabinets
Horizon II macro
MASTER CABINET
INTEGRATED CONNECTION VIA BACKPLANE SITE

XMUX EXPANSION
BOARD
HIISC
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
2 2 2 2 2 2 12
C C C C C C X SITE
T T T T T T M EXPANSION
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
68P02900W21-R 12-11
28 Feb 2006 GMR-01
Two cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
If a redundant HIISC is installed in the master cabinet, redundant site expansion boards must
be installed in the master and slave cabinets and a redundant XMUX must be installed in each
slave cabinet.
Two cabinet Horizon II mini BTS
The configuration shown in Figure 12-9 is an example of a two cabinet Horizon II mini. This configuration
supports 4 carriers in single density mode and 8 carriers in double density mode. The HIISC interfaces to
the CTU2s in the second (slave) cabinet through site expansion boards in both cabinets (connected via fibre
optic cables) and an XMUX replaces the HIISC in the second cabinet.
The site expansion board is optional equipment in the master BTS and is only required when site expansion is
required.
Figure 12-9 Macrocell BTS with two Horizon II mini cabinets
Horizon II mini
MASTER CABINET
INTEGRATED CONNECTION VIA BACKPLANE SITE

XMUX EXPANSION
BOARD
HIISC
2 2
C C
T T
U U
2 2
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
12-12 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Two cabinet BTS configurations
Two cabinet Horizonmacro BTS
The configuration shown in Figure 12-10 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 12-10 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
2 2 2 2 2 2 DIGITAL
12
EQUIPMENT
SHELF
C C C C C C
T T T T T T
U F
U U U U U M
U
X
HorizonmacroCABINET
68P02900W21-R 12-13
28 Feb 2006 GMR-01
Three cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Three cabinet BTS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Three cabinet Horizon II macro BTS
The configuration shown in Figure 12-11 is an example of a three cabinet Horizon II macro. As with a two
cabinet configuration, the HIISC interfaces to the CTU2s in the slave cabinets through site expansion boards in
all cabinets (connected via fibre optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-11 Macrocell BTS with three Horizon II macro cabinets
Horizon II macro
MASTER
CABINET
CONNECTION VIA BACKPLANE SITE
INTEGRATED
XMUX EXPANSION
BOARD
HIISC
12
2 2 2 2 2 2
C C C C C C 2
T T T T T T
U U U U U U
2 2 2 2 2 2
2 2 2 2 2 2 12
C C C C C C X SITE
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
2 2 2 2 2 2 12
C C C C C C X SITE
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
12-14 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Three cabinet BTS configurations
Three cabinet Horizon II mini BTS
The configuration shown in Figure 12-12 is an example of a three cabinet Horizon II mini. As with a two
Figure 12-12 Macrocell BTS with three Horizon II mini cabinets
Horizon II mini
MASTER
CABINET
INTEGRATED
XMUX EXPANSION
BOARD
HIISC
2 2
C C 2
T T
U U
2 2
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
68P02900W21-R 12-15
28 Feb 2006 GMR-01
slave cabinet.
Three cabinet Horizon II micro BTS
The configuration shown in Figure 12-13 is an example of a three cabinet Horizon II micro. The HIISC
interfaces to the CTU2s in the slave cabinets through site expansion boards in all cabinets (connected via fibre
optic cables) and an XMUX replaces the HIISC in each of the slave cabinets.
Figure 12-13 Macrocell BTS with three Horizon II micro cabinets
Horizon II micro
MASTER
CABINET
INTEGRATED
XMUX EXPANSION
BOARD
HIISC
C 2
T
U
2
2 2
C X SITE
T M EXPANSION
U U BOARD
2 X
Horizon II micro
SLAVE CABINET
2 2
C X SITE
T M EXPANSION
U U BOARD
2 X
Horizon II micro
SLAVE CABINET
12-16 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Three cabinet BTS configurations
slave cabinet.
Three cabinet Horizonmacro BTS
The configuration shown in Figure 12-14 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 12-14 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
CABINET 2 2 2 2 2 2 DIGITAL
12
EQUIPMENT
SHELF
C C C C C C
T T T T T T
U F
U U U U U M
U
X
Horizonmacro
CABINET 2 2 2 2 2 2 DIGITAL
12
EQUIPMENT
SHELF
C C C C C C
T T T T T T
U F
U U U U U M
U
X
68P02900W21-R 12-17
28 Feb 2006 GMR-01
12-18 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Four cabinet BTS configurations
Four cabinet BTS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Four cabinet Horizon II macro BTS
The configuration shown in Figure 12-15 is an example of a four cabinet Horizon II macro. As with a two
Figure 12-15 Macrocell BTS with four Horizon II macro cabinets
Horizon II macro
MASTER CABINET
CONNECTION VIA BACKPLANE
INTEGRATED SITE
XMUX EXPANSION
BOARD
HIISC
12
2
2 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 2
2 2 2 2 2 2 12
C C C C C C X SITE
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
2 2 2 2 2 2 12
C C C C C C X SITE
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
2 2 2 2 2 2 12
C C C C C C X SITE
U U U U U U U BOARD
2 2 2 2 2 2 X
Horizon II macro
SLAVE CABINET
68P02900W21-R 12-19
28 Feb 2006 GMR-01
Four cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
slave cabinet.
12-20 68P02900W21-R
GMR-01 28 Feb 2006
Four cabinet Horizon II mini BTS
The configuration shown in Figure 12-16 is an example of a four cabinet Horizon II mini. As with a two
Figure 12-16 Macrocell BTS with four Horizon II mini cabinets
Horizon II mini
MASTER CABINET
CONNECTION VIA BACKPLANE
INTEGRATED SITE
XMUX EXPANSION
BOARD
HIISC
4
2
2 2
2
C C
T T
U U 2
2 2
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
2 2 4
C C X SITE
T T M EXPANSION
U U U BOARD
2 2 X
Horizon II mini
SLAVE CABINET
68P02900W21-R 12-21
28 Feb 2006 GMR-01
Four cabinet BTS configurations Chapter 12: Standard BSS and Horizon BTS configurations
Four cabinet Horizonmacro BTS
The configuration shown in Figure 12-17 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 12-17 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
U F
U U U U U M
U
X
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T
U F
U U U U U M
U
X
CABINET 12
EQUIPMENT
SHELF
C C C C C C
T T T T T T
U F
U U U U U M
U
X
12-22 68P02900W21-R
GMR-01 28 Feb 2006
68P02900W21-R 12-23
28 Feb 2006 GMR-01
Horizon macrocell RF configurations Chapter 12: Standard BSS and Horizon BTS configurations
Horizon macrocell RF configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of configuration diagrams
The Horizon macrocell BTS cabinets/enclosures are presented as follows:

• Horizon II macro cabinets.
• Horizon II mini cabinets.
• Horizonmacro cabinets.
• Horizoncompact2 enclosures.
HorizonII macro cabinets
The following series of Horizon II macro RF configuration diagrams show suggested ways of connecting
together Horizon II macro SURF2 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 (except for the PGSM disgrams) is applicable to either EGSM900 or DCS1800 operation,
though the SURF2 module illustrated is a 1800 MHz SURF2. For EGSM900 operation a 900 MHz SURF2 is
required.
Two SURF2s can be installed in the Horizon II macro cabinet (see Figure 12-24), in which case they can be of
the same type (900 and 1800 SURF2s or can be mixed in the same cabinet when the dual band adaptor is
installed.
Rules for equipping Horizon II macro cabinets

The following rules apply when equipping any Horizon II macro cabinet for the configurations shown in
Figure 12-18 to Figure 12-24:
• A maximum of six CTU2s can be accommodated.
• All CTU2s in the cabinet must operate at the same frequency (either 900 MHz or 1800 MHz).
• When operating in double density mode, both CTU2 carriers must be in the same sector.
• When operating in Dual Band mode within a single cabinet, up to 3 CTU2s per band
can be accommodated.
• An external equipment cabinet is not required.
12-24 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Horizon macrocell RF configurations
[DCS1800] 4 or 8 carrier omni with HCUs and air combining
Figure 12-18 shows a single cabinet, four CTU2 configuration with duplexers, hybrid combiner units and air
combining. Table 12-1 provides a summary of the equipment required for this configuration.
Figure 12-18 [DCS1800] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx Tx/Rx
ANTENNA ANTENNA
RX RX RX EXP EXP RX RX RX
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
RX RX
HCU HCU
ANT ANT
BLANK DUP BLANK DUP
EMPTY CTU2 CTU2 EMPTY CTU2 CTU2

5 4 3 2 1 0
Horizon II macro CABINET
68P02900W21-R 12-25
28 Feb 2006 GMR-01
Table 12-1 Equip. required for 4 or 8 carrier omni with HCUs and air combining
Quantity Unit
2 Antennas
1 Horizon II macro cabinet
4 CTU2
Receiver
1 SURF2
Transmitter/receiver
2 DUP
2 HCU
12-26 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 6 or 12 carrier omni with DHUs
Figure 12-19 shows a single cabinet, six CTU2 configuration with duplexers and dual hybrid combiner units.
Table 12-2 provides a summary of the equipment required for this configuration.
Figure 12-19 [DCS1800] 6 or 12 carrier omni with DHUs

Tx/Rx Tx/Rx
ANTENNA ANTENNA
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
DHU DHU
RX RX
ANT ANT
BLANK DUP BLANK DUP
CTU2 CTU2 CTU2 CTU2 CTU2 CTU2

5 4 3 2 1 0
68P02900W21-R 12-27
28 Feb 2006 GMR-01
Table 12-2 Equipment required for 6 or 12 carrier omni with DHUs
Quantity Unit
2 Antennas
6 CTU2
Receiver
1 SURF2
2 DUP
2 DHU
12-28 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 2 sector 3/3 or 6/6 with DHUs
Figure 12-20 [DCS1800] 2 sector 3/3 or 6/6 with DHUs
SECTOR 2 SECTOR 1
Tx/Rx Rx Rx Tx/Rx
ANTENNA ANTENNA ANTENNA ANTENNA
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
DHU DHU
RX RX
ANT ANT
BLANK DUP BLANK DUP

5 4 3 2 1 0
68P02900W21-R 12-29
28 Feb 2006 GMR-01
Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs
Quantity Unit
4 Antennas
6 CTU2
Receiver
1 SURF2
2 DUP
2 DHU
12-30 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air

combining
Figure 12-21 shows a two cabinet configuration, each cabinet containing four CTU2s with duplexers, hybrid
combiner units and air combining. Table 12-4 provides a summary of the equipment required for this
configuration. [DCS1800] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining
Figure 12-21 [DCS1800] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining
SECTOR 2 SECTOR 1
Tx/Rx ANTENNAS Tx/Rx ANTENNAS
RX RX RX EXP EXP RX RX RX RX RX RX EXP EXP RX RX RX

2B 1B 0B B A 0A 1A 2A 2B 1B 0B B A 0A 1A 2A
SURF2 SURF2
5 4 3 2 1 0 5 4 3 2 1 0
RX RX RX RX
HCU HCU HCU HCU
ANT ANT ANT ANT

BLANK DUP BLANK DUP BLANK DUP BLANK DUP
EMPTY CTU2 CTU2 EMPTY CTU2 CTU2 EMPTY CTU2 CTU2 EMPTY CTU2 CTU2
5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION SITE EXPANSION
XMUX BOARD BOARD HIISC
Horizon II macro Horizon II macro
SLAVE CABINET MASTER CABINET
Fibre Optic Link (x2)
Table 12-4 Equip. req. for 2 cab, 2 sctr 4/4 or 8/8 with HCUs and air combining
Quantity Unit
4 Antennas
8 CTU2
Receiver
2 SURF2
4 DUP
4 HCU
68P02900W21-R 12-31
28 Feb 2006 GMR-01
[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs
Figure 12-22 shows a single cabinet, six CTU2 configuration with duplexers and hybrid combiner units.
Figure 12-22 [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs
SECTOR 3 SECTOR 2 SECTOR 1

Tx/Rx Rx Rx Tx/Rx Rx Tx/Rx
ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
RX RX RX
HCU HCU HCU
ANT ANT ANT

DUP DUP DUP

5 4 3 2 1 0
12-32 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs
Quantity Unit
6 Antennas
6 CTU2
Receiver
1 SURF2
3 DUP
3 HCU
68P02900W21-R 12-33
28 Feb 2006 GMR-01
[DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air

combining
Figure 12-23 shows a two cabinet configuration, each cabinet containing six CTU2s with duplexers,
hybrid combiner units and air combining. Table 12-6 provides a summary of the equipment required for
this configuration.
Figure 12-23 [DCS1800] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining

Tx/Rx ANTENNAS Tx/Rx ANTENNAS Tx/Rx ANTENNAS

SURF2 SURF2
5 4 3 2 1 0 5 4 3 2 1 0
RX RX RX RX RX RX
HCU HCU HCU HCU HCU HCU
ANT ANT ANT ANT ANT ANT

DUP DUP DUP DUP DUP DUP
CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2
5 4 3 2 1 0 5 4 3 2 1 0
Table 12-6 Equip. req. for 2 cab, 3 sctr 4/4/4 or 8/8/8 with HCUs and air comb.
Quantity Unit
6 Antennas
12 CTU2
Receiver
2 SURF2
6 DUP
6 HCU
12-34 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity
Figure 12-24 shows a single cabinet, six CTU2 configuration for 4 branch Rx diversity with duplexers,
hybrid combiner units and air combining. Table 12-7 provides a summary of the equipment required for
this configuration.
Figure 12-24 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air comb. and 4 branch Rx diversity
2C 1C 0C C D 0D 1D 2D
SURF2
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
RX RX RX RX RX RX


5 4 3 2 1 0
68P02900W21-R 12-35
28 Feb 2006 GMR-01
Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity
Quantity Unit
12 Antennas
6 CTU2
Receiver
2 SURF2
6 DUP
12-36 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2
Figure 12-25 shows a single cabinet, 3 CTU2 (1800 MHz) and 3 CTU2 (900 MHz) configuration with
duplexers and air combining. This is typical Horizon II Macro dual band configuration that supports both 900
MHz and 1800 MHz within the same cabinet. Table 12-8 provides a summary of the equipment required for
this configuration. Refer to the notes below for required equipment units and software load.
Figure 12-25 [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining
900 900 900 1800 1800 1800

SECTOR 2 SECTOR 1 SECTOR 0 SECTOR 2 SECTOR 1 SECTOR 0
A B A B A B A B A B
A B
A2 1 0 A B B0 1 2
900 SURF2
B2 1 0 B A A0 1 2
1800 SURF2
DB Adaptor
900 900 900 1800 1800 1800


900 900 900 1800 1800 1800
A A A A A A
B B B B B B
5 4 3 2 1 0
68P02900W21-R 12-37
28 Feb 2006 GMR-01
Table 12-8 Equipment required for 3 sector 2/2/2 and 2/2/2
Quantity Unit
12 Antennas
1 Dual band adaptor
3 1800MHz CTU2
3 900MHz CTU2
Receiver
1 1800MHz SURF2
1 900MHz SURF2
3 1800MHz DUP
3 900MHz DUP
Power supply
3 Power supply
A fourth power supply is

recommended - contact your
Motorola Local Office for full
details.
The HII Dual band adaptor will allow a single Horizon II cabinet to be used for both 1800
MHz and 900 MHz frequency bands in a GSM/GPRS network controlled by one BSC. This
implementation places an adaptor module at the bottom of the SURF bay. Each of the 900
MHz and 1800 MHz SURF2 modules will plug into this adaptor module. The adaptor module
interconnects the outputs of the SURF2 modules to the appropriate CTU2 slot in a hardwired
fashion. Each CTU2 uses its primary receive inputs. A maximum of three CTU2 per frequency
band in a Horizon II cabinet can be configured with the dual band adaptor. The rear SURF2
controls CTU2 radio slots from 3-5; the front SURF2 controls CTU2 radio slots from 0-2.
12-38 68P02900W21-R
GMR-01 28 Feb 2006
Horizon II macro cabinets with PGSM Duplexer
The following series of Horizon II macro RF configuration diagrams shows suggested ways of connecting
together Horizon II macro cabinets with PGSM Duplexers. The series of diagrams is by no means exhaustive,
and numerous alternative configurations may be adopted to achieve the same aim.
Rules for equipping Horizon II macro cabinets with PGSM Duplexer

The following rules apply when equipping any Horizon II macro cabinet for the configurations shown in
• A maximum of six CTU2s can be accommodated.
• All CTU2s in the cabinet must operate at the same frequency (PGSM 900 MHz).
• A PGSM duplexer is required for both main and diversity receiver branches.
68P02900W21-R 12-39
28 Feb 2006 GMR-01
[PGSM] 4 or 8 carrier omni with HCUs and air combining
Figure 12-26 shows a single cabinet, four CTU2 configuration with duplexers, hybrid combiner units and air
Figure 12-26 [PGSM900] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx Tx/Rx
ANTENNA ANTENNA
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
RX RX
HCU HCU
ANT ANT
BLANK DUP BLANK DUP

5 4 3 2 1 0
12-40 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-9 Equip. required for 4 or 8 carrier omni with HCUs and air combining
Quantity Unit
2 Antennas
4 CTU2
Receiver
1 SURF2
2 DUP
2 HCU
68P02900W21-R 12-41
28 Feb 2006 GMR-01
[PGSM900] 6 or 12 carrier omni with DHUs
Figure 12-27 [PGSM900] 6 or 12 carrier omni with DHUs

Tx/Rx Tx/Rx
ANTENNA ANTENNA
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
DHU DHU
RX RX
ANT ANT
BLANK DUP BLANK DUP

5 4 3 2 1 0
12-42 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-10 Equip. required for 6 or 12 carrier omni with DHUs
Quantity Unit
2 Antennas
6 CTU2
Receiver
1 SURF2
2 DUP
2 DHU
68P02900W21-R 12-43
28 Feb 2006 GMR-01
[PGSM900] 2 sector 3/3 or 6/6 with HCUs
Figure 12-28 shows a single cabinet, six CTU2 configuration with duplexers and hybrid combiner units.
Figure 12-28 [PGSM900] 2 sector 3/3 or 6/6 with HCUs
SECTOR 2 SECTOR 1
Tx/Rx Rx Rx Tx/Rx
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
HCU HCU
RX RX RX RX
ANT ANT ANT ANT
DUP DUP DUP DUP

5 4 3 2 1 0
Image008.eps
12-44 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-11 Equip. required for 2 sector 3/3 or 6/6 with HCUs
Quantity Unit
4 Antennas
6 CTU2
Receiver
1 SURF2
4 DUP
2 HCU
[PGSM900] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air

combining
Figure 12-29 shows a two cabinet configuration, each cabinet containing four CTU2s with duplexers,
hybrid combiner units and air combining. Table 12-12 provides a summary of the equipment required
for this configuration.
Figure 12-29 [PGSM900] 2 cab, 2 sector 4/4 or 8/8 with HCUs and air combining
SECTOR 2 SECTOR 1
Tx/Rx ANTENNAS Tx/Rx ANTENNAS

SURF2 SURF2
5 4 3 2 1 0 5 4 3 2 1 0
RX RX RX RX
HCU HCU HCU HCU
ANT ANT ANT ANT

BLANK DUP BLANK DUP BLANK DUP BLANK DUP
EMPTY CTU2 CTU2 EMPTY CTU2 CTU2 EMPTY CTU2 CTU2 EMPTY CTU2 CTU2
5 4 3 2 1 0 5 4 3 2 1 0
68P02900W21-R 12-45
28 Feb 2006 GMR-01
Table 12-12 Equip. req. for 2 cab, 2 sctr 4/4 or 8/8 with HCUs and air combining
Quantity Unit
4 Antennas
8 CTU2
Receiver
2 SURF2
4 DUP
4 HCU
12-46 68P02900W21-R
GMR-01 28 Feb 2006
[PGSM900] 3 sector 2/2/2 or 4/4/4
Figure 12-30 shows a single cabinet, six CTU2 configuration with duplexers. Table 12-13 provides a summary
of the equipment required for this configuration.
Figure 12-30 [PGSM900] 3 sector 2/2/2 or 4/4/4

Tx/Rx Rx Tx/Rx Rx Rx Tx/Rx
2B 1B 0B B A 0A 1A 2A
SURF2
5 4 3 2 1 0
RX RX RX RX RX RX

5 4 3 2 1 0
Image012.eps
68P02900W21-R 12-47
28 Feb 2006 GMR-01
Table 12-13 Equip. required for 3 sector 2/2/2 or 4/4/4
Quantity Unit
6 Antennas
6 CTU2
Receiver
1 SURF2
6 DUP
[PGSM900] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air

combining
Figure 12-31 shows a two cabinet configuration, each cabinet containing six CTU2s with duplexers,
hybrid combiner units and air combining. Table 12-14 provides a summary of the equipment required
Figure 12-31 [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining

Tx/Rx ANTENNAS Tx/Rx ANTENNAS Tx/Rx ANTENNAS

SURF2 SURF2
5 4 3 2 1 0 5 4 3 2 1 0
RX RX RX RX RX RX
HCU HCU HCU HCU HCU HCU

CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2 CTU2
5 4 3 2 1 0 5 4 3 2 1 0
12-48 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-14 Equip. req. for 2 cab, 3 sctr 4/4/4 or 8/8/8 with HCUs and air comb.
Quantity Unit
6 Antennas
12 CTU2
Receiver
2 SURF2
6 DUP
6 HCU
HorizonII mini cabinets
The following series of Horizon II mini RF configuration diagrams show suggested ways of connecting
together Horizon II mini MiniSURF2 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 MiniSURF2 module
illustrated is a 1800 MHz SURF2. For EGSM900 operation a 900 MHz MiniSURF2 is required. For
PGSM900 operation, only certain configurations are noted: Omni-2 (with diversity), Omni-4 (with diversity)
and Sector 2/2 (no diversity).
Rules for equipping Horizon II mini cabinets

The following rules apply when equipping any Horizon II mini cabinet for the configurations shown in
• A maximum of two CTU2s can be accommodated.
• Both CTU2s in the cabinet must operate at the same frequency (either 900 MHz or 1800 MHz).
68P02900W21-R 12-49
28 Feb 2006 GMR-01
[DCS1800/EGSM900/PGSM900] High power Omni-1, standard

power Omni-2
Figure 12-32 shows a single cabinet, one CTU2, high power (HP) Omni-1/standard power (SP) Omni-2
configuration. Table 12-15 provides a summary of the equipment required for this configuration.
Figure 12-32 DCS1800/EGSM900 HP Omni-1/SP Omni-2
Sector 1:
2 carriers
ALARM
HIISC
1A
BATTERY
0A
0B
1B
T43/BIB
FRONT REAR
Horizon II mini CABINET
12-50 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-15 Equip. required for HP Omni-1/SP Omni-2
Quantity Unit
2 Antenna
1 Horizon II mini cabinet
1 CTU2
Receiver
1 MiniSURF2
68P02900W21-R 12-51
28 Feb 2006 GMR-01
[DCS1800/EGSM900/PGSM900] High power Omni-2, standard

power Omni-4
Figure 12-33 shows a single cabinet, two CTU2 high power (HP) Omni-2/standard power (SP) Omni-4
Figure 12-33 DCS1800/EGSM900 HP Omni-2/SP Omni-4
Sector 1:
4 carriers
ALARM
HIISC
1A
BATTERY
0A
0B
1B
T43/BIB
FRONT REAR
12-52 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-16 Equip. required for HP Omni-1/SP Omni-2
Quantity Unit
2 Antenna
2 CTU2
Receiver
1 MiniSURF2
68P02900W21-R 12-53
28 Feb 2006 GMR-01
[DCS1800/EGSM900] High power Bowtie-2, standard power

Bowtie-4
Figure 12-34 shows a single cabinet, two CTU2 high power (HP) Bowtie-2/standard power (SP) Bowtie-4
Figure 12-34 DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4
Antenna 1: Antenna 2:
4 carriers 4 carriers
Hybrid
ALARM
HIISC
1A
BATTERY
0A
0B
1B
T43/BIB
FRONT REAR
12-54 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-17 Equip. required for HP Bowtie-2/SP Bowtie-4
Quantity Unit
2 Antenna
2 CTU2 Bowtie-4 configuration
Receiver
1 MiniSURF2
1 Hybrid combiner
68P02900W21-R 12-55
28 Feb 2006 GMR-01
[DCS1800/EGSM900] High power 2 sector 1/1, standard power 2

sector 2/2
Figure 12-35 shows a single cabinet, two CTU2, high power (HP) two sector 1/1/standard power (SP) two
sector 2/2 configuration. Table 12-18 provides a summary of the equipment required for this configuration.
Figure 12-35 DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2
Sector 1: Sector 2:
ALARM
HIISC
0A 1A
BATTERY
1B 0B
T43/BIB
FRONT REAR
12-56 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-18 Equip. required for HP 2 sector 1/1/SP 2 sector 2/2
Quantity Unit
4 Antenna
2 CTU2
Receiver
1 MiniSURF2
68P02900W21-R 12-57
28 Feb 2006 GMR-01
[DCS1800/EGSM900/PGSM900] High power 2 sector 2/2, standard

power 2 sector 4/4
Figure 12-36 shows a two cabinet (each cabinet containing two CTU2s), high power (HP) 2 sector
2/2/standard power (SP) 2 sector 4/4 configuration. Table 12-19 provides a summary of the equipment
required for this configuration.
Figure 12-36 DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4

Sector 2: Sector 1:
2
SITE EXP
SITE EXP
ALARM
ALARM
HIISC
HIISC
0A 1A
0A 1A
BATTERY
BATTERY
1B 0B
1B 0B
T43/BIB T43/BIB
REAR REAR
FRONT FRONT
Horizon II mini Horizon II mini
Table 12-19 Equip. required for HP 2 sector 2/2/SP 2 sector 4/4
Quantity Unit
4 Antenna
2 Site I/O board
4 CTU2
Receiver
2 MiniSURF2
12-58 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800/EGSM900] High power 3 sector 1/1/1, standard power

3 sector 2/2/2
Figure 12-37 shows a two cabinet (the master cabinet containing two CTU2s, the slave cabinet containing
one CTU2), high power (HP) 3 sector 1/1/1/standard power (SP) 3 sector 2/2/2 configuration. Table 12-20
provides a summary of the equipment required for this configuration.
Figure 12-37 DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2

Sector 3:
4 carriers Sector 1: Sector 2:
SITE EXP
SITE EXP
ALARM
HIISC
ALARM
HIISC
0A 1A
0A 1A
BATTERY
BATTERY
1B 0B
1B 0B
T43/BIB
T43/BIB
REAR
FRONT REAR
FRONT
Table 12-20 Equip. required for HP 3 sector 1/1/1/SP 3 sector 2/2/2
Quantity Unit
6 Antenna
2 Site I/O board
3 CTU2
Receiver
2 MiniSURF2
68P02900W21-R 12-59
28 Feb 2006 GMR-01
[DCS1800/EGSM900] High power 3 sector 2/2/2, standard power

3 sector 4/4/4
Figure 12-38 shows a three cabinet (each cabinet containing two CTU2s) high power (HP) 3 sector
2/2/2/standard power 3 sector 4/4/4. Table 12-21 provides a summary of the equipment required for this
configuration.
Figure 12-38 DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4

Sector 2: Sector 1:
2
SITE EXP 2
SITE EXP
ALARM
ALARM
HIISC
HIISC
0A 1A
0A 1A
BATTERY
BATTERY
1B 0B
1B 0B
T43/BIB T43/BIB
REAR REAR
FRONT FRONT
Sector 3:
4 carriers
SITE EXP
ALARM
HIISC
0A 1A
BATTERY
1B 0B
T43/BIB
REAR
FRONT
Horizon II mini
SLAVE CABINET
12-60 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-21 Equip. required for HP 3 sector 2/2/2/SP 3 sector 4/4/4
Quantity Unit
6 Antenna
2 Site I/O board
6 CTU2
Receiver
3 MiniSURF2
HorizonII micro cabinets
The following series of Horizon II micro RF configuration diagrams show suggested ways of connecting
together Horizon II micro MiniSURF2 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 MiniSURF2 module
illustrated is a 1800 MHz SURF2. For EGSM900 operation a 900 MHz MiniSURF2 is required.
Rules for equipping Horizon II micro cabinets

The following rules apply when equipping any Horizon II micro cabinet for the configurations shown in
68P02900W21-R 12-61
28 Feb 2006 GMR-01
[DCS1800/EGSM900] Single cabinet - Horizon II micro
Figure 12-39 shows a single cabinet configuration. Table 12-22 provides a summary of the equipment
Figure 12-39 [DCS1800/EGSM900] Horizon II micro one cabinet configuration
Sector 1:
2 carriers
ALARM
HIISC
1A
BATTERY
0A
0B
1B
T43/BIB
POWER SUPPLY
FRONT REAR
Horizon II micro CABINET
12-62 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-22 Equip. required for Horizon II micro one cabinet config.
Quantity Unit
2 Antenna
1 Horizon II micro cabinet
1 CTU2
Receiver
1 MiniSURF2
68P02900W21-R 12-63
28 Feb 2006 GMR-01
[DCS1800/EGSM900] Three cabinet - Horizon II micro
Figure 12-40 shows a three cabinet configuration. Table 12-23 provides a summary of the equipment required
Figure 12-40 [DCS1800/EGSM900] Horizon II micro three cabinet configuration

Sector 2: Sector 1:
2
2
SITE EXP
SITE EXP
ALARM
ALARM
XMUX
HIISC
0A 1A
0A 1A
BATTERY
BATTERY
1B 0B
1B 0B
T43/BIB T43/BIB
POWER SUPPLY POWER SUPPLY
REAR REAR
FRONT FRONT
Horizon II micro Horizon II micro
Sector 3:
2 carriers
SITE EXP
ALARM
XMUX
0A 1A
BATTERY
1B 0B
T43/BIB
POWER SUPPLY
REAR
FRONT
Horizon II micro
SLAVE CABINET
12-64 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-23 Equip. required for Horizon II microthree cabinet config.
Quantity Unit
2 Antenna
1 Horizon II micro cabinet
1 CTU2
Receiver
1 MiniSURF2
3 Site I/O board (expansion)
68P02900W21-R 12-65
28 Feb 2006 GMR-01
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.
Rules for equipping Horizonmacro cabinets

The following rules apply when equipping any Horizonmacro cabinet for the configurations shown in
• A maximum of six CTUs can be accommodated.
12-66 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 4 carrier omni, with duplexed hybrid and air combining
Figure 12-41 shows a single cabinet, four CTU configuration with duplexed hybrid and air combining.
Figure 12-41 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
68P02900W21-R 12-67
28 Feb 2006 GMR-01
Table 12-24 Equip. req. for 1 cab, 4 CTU config, duplexed hybrid and air comb.
Quantity Unit
2 Antennas
1 Horizonmacro cabinet
4 CTU
Receiver
1 SURF
2 DCF
12-68 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and

air combining
Figure 12-42 shows a single cabinet, six CTU configuration with duplexed dual-stage hybrid and air
Figure 12-42 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
68P02900W21-R 12-69
28 Feb 2006 GMR-01
Table 12-25 Equip req. for 1 cab., 6 CTU config, duplex dual-stage hybrid and air comb.
Quantity Unit
2 Antennas
6 CTU
Receiver
1 SURF
2 DDF
1 Feed through, with two through connectors
12-70 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid

combining
Figure 12-43 shows a single cabinet, six CTU configuration with duplexed dual-stage hybrid combining.
Figure 12-43 2 sector (3/3), duplexed dual-stage hybrid combining

Tx/Rx Tx/Rx Rx Rx
(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
68P02900W21-R 12-71
28 Feb 2006 GMR-01
Table 12-26 Equip. req. for 1 cab, 6 CTU config, duplexed dual-stage hybrid comb.
Quantity Unit
4 Antennas
6 CTU
Receiver
1 SURF
2 DDF
12-72 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and

air combining
Figure 12-44 shows a dual cabinet, 12 CTU configuration with duplexed dual-stage hybrid and air combining.
Figure 12-44 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
THROUGH FEED
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
68P02900W21-R 12-73
28 Feb 2006 GMR-01
Table 12-27 Equip. req. for dual cab, 12 CTU config, dplx dual-stg hybrid and air comb
Quantity Unit
4 Antennas
2 Horizonmacro cabinets
12 CTU
Receiver
2 SURF
4 DDF
12-74 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining
Figure 12-45 shows a single cabinet, six CTU configuration with duplexed hybrid combining. Table 12-28
Figure 12-45 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
68P02900W21-R 12-75
28 Feb 2006 GMR-01
Table 12-28 Equip. req. for 1 cab., 6 CTU config, duplexed hybrid combining
Quantity Unit
6 Antennas
6 CTU
Receiver
1 SURF
3 DCF
12-76 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air

combining
Figure 12-46 shows a dual cabinet, 12 CTU configuration with duplexed hybrid and air combining.
Figure 12-46 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
68P02900W21-R 12-77
28 Feb 2006 GMR-01
Table 12-29 Equip. req. for dual cab, 12 CTU config. duplexed hybrid and air comb
Quantity Unit
6 Antennas
2 Horizonmacro BTS cabinets
12 CTU
2 SURF
6 DCF
12-78 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and

air combining
Figure 12-47 and Figure 12-48 show a four cabinet, 24 CTU configuration with duplexed dual-stage hybrid
and air combining. Table 12-30 provides a summary of the equipment required for this configuration.
Figure 12-47 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
68P02900W21-R 12-79
28 Feb 2006 GMR-01
Figure 12-48 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
12-80 68P02900W21-R
GMR-01 28 Feb 2006
Table 12-30 Equip. req. for 4 cab., 24 CTU config, duplex dual-stg hybrid and air comb
Quantity Unit
6 Antennas
4 Horizonmacro cabinets
24 CTU
Transmitter
6 Hybrid combiner unit (HCU)
Receiver
4 SURF
6 DDF
68P02900W21-R 12-81
28 Feb 2006 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.
The Horizoncompact2 BTS system supports the following site configurations using GSM900 or DCS1800
BTSs:
• 1 BTS site
Omni site - one or two carriers in a single cell.
• 2 BTS site
Omni site - up to four carriers in a single cell.
Two sector site, two carriers per cell.
• 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:
• 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
• 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.
12-82 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900/DCS1800] Horizoncompact2 single BTS system
Figure 12-49 shows the configuration for a single Horizoncompact2 BTS system.
Figure 12-49 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
68P02900W21-R 12-83
28 Feb 2006 GMR-01
[GSM900/DCS1800] Horizoncompact2 two BTS system
Figure 12-50 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 12-49
for internal connections within the BTS and booster.
Figure 12-50 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
12-84 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900/DCS1800] Horizoncompact2 three BTS system
Figure 12-51 shows the configuration for a three Horizoncompact2 BTS system using fibre optic cables. An
for internal connections within the BTS and booster.
68P02900W21-R 12-85
28 Feb 2006 GMR-01
Figure 12-51 Horizoncompact2 three BTS system
Tx2 Tx1/Rx Tx2 Tx1/Rx Tx2 Tx1/Rx

Horizoncompact2 BOOSTER Horizoncompact2 BOOSTER
Horizoncompact2 MASTER BTS Horizoncompact2 SLAVE BTS
FIBRE OPTIC LINK
Horizoncompact2 BOOSTER
FIBRE OPTIC LINK

DINO / RHINO
Horizoncompact2 SLAVE BTS
12-86 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning 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.
The Horizonmicro2 BTS supports the following site configurations using GSM900 or DCS1800 BTSs:
• 1 BTS site
Omni site - one or two carriers in a single cell.
• 2 BTS site
Omni site - up to four carriers in a single cell.
Two sector site, two carriers per cell.
• 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:
• 2 BTS cell: One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
• 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.
68P02900W21-R 12-87
28 Feb 2006 GMR-01
Microcell RF configurations Chapter 12: Standard BSS and Horizon BTS configurations
[GSM900/DCS1800] Horizonmicro2 single BTS system
Figure 12-52 shows the configuration for a single Horizonmicro2 BTS system.
Figure 12-52 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
12-88 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Microcell RF configurations
[GSM900/DCS1800] Horizonmicro2 two BTS system
Figure 12-53 shows the configuration for a two Horizonmicro2 BTS system using fibre optic cables. An
for internal connections within the BTS.
Figure 12-53 Horizonmicro2 two BTS system
Tx1/Tx2/Rx Tx1/Tx2/Rx
ANTENNA ANTENNA
Horizonmicro2 MASTER BTS Horizonmicro2 SLAVE BTS
FIBRE OPTIC LINK
68P02900W21-R 12-89
28 Feb 2006 GMR-01
Microcell RF configurations Chapter 12: Standard BSS and Horizon BTS configurations
[GSM900/DCS1800] Horizonmicro2 three BTS system
Figure 12-54 shows the configuration for a three Horizonmicro2 BTS system using fibre optic cables. An
for internal connections within the BTS.
Figure 12-54 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
12-90 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Connecting Horizon II macro cabinets to Horizonmacro cabinets
Connecting Horizon II macro cabinets to

Horizonmacro cabinets
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Connection overview
This section provides examples of how previous generation Horizonmacro BTS equipment can be connected
to the latest generation Horizon II macro BTS equipment.
Compatibility issues
The following points must be taken into account when connecting Horizon II macro cabinets to Horizonmacro
cabinets:
• Although the Horizon II macro equipment is totally compatible with Horizonmacro equipment,
the CTU2 is the only module that can be used in either cabinet.
• When CTU2s are used in Horizonmacro, baseband hopping is only supported in single
density mode.
• In cases where the Horizonmacro BTS is the master cabinet and the MCUF is the master
site controller, the MCUF must have a 20 Mbyte PCMCIA card installed running CSFP to
accommodate the added memory requirements of the GSR6 (Horizon II) objects.
68P02900W21-R 12-91
28 Feb 2006 GMR-01
Connecting Horizon II macro cabinets to Horizonmacro cabinets Chapter 12: Standard BSS and Horizon BTS configurations
Examples of mixed cabinet configurations
Figure 12-55 to Figure 12-60 are examples of possible configurations for mixed Horizon II macro and
Horizonmacro cabinets.
Sector 4/4 configuration using two cabinets

Figure 12-55 shows a suggested configuration for sector 4/4, using one Horizon II macro cabinet with
duplexers and one Horizonmacro cabinet.
Figure 12-55 Sector 4/4 configuration with Horizon II macro and Horizonmacro cabs
SECTOR 1 SECTOR 2
RX RX RX EXP EXP RX RX RX 2B 1B 0B 2A 1A 0A B A
2B 1B 0B B A 0A 1A 2A
SURF2 SURF EXT
5 4 3 2 1 0 BLANK DCF DCF

RX RX
ANT ANT
BLANK BLANK DUP BLANK BLANK DUP
EMPTY EMPTY CTU2 EMPTY EMPTY CTU2

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD HIISC FMUX
Horizon II macro Horizonmacro

master cabinet slave cabinet
12-92 68P02900W21-R
GMR-01 28 Feb 2006
Sector 6/6 configuration using two cabinets

Figure 12-56 shows a suggested configuration for sector 6/6, using one Horizon II macro cabinet with
duplexers and hybrid combiner units and one Horizonmacro cabinet.
Figure 12-56 Sector 6/6 configuration with Horizon II macro and Horizonmacro cabs
SECTOR 1 SECTOR 2
2B 1B 0B B A 0A 1A 2A
SURF2 SURF EXT
5 4 3 2 1 0 DDF F’THRU DDF

RX RX
HCU HCU
ANT ANT
BLANK DUP BLANK DUP
LOAD
EMPTY EMPTY CTU2 EMPTY CTU2 CTU2

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD HIISC FMUX

68P02900W21-R 12-93
28 Feb 2006 GMR-01
Sector 2/2/2 configuration using two cabinets

Figure 12-57 and Figure 12-58 show a suggested configuration for sector 2/2/2, using one Horizon II macro
cabinet with duplexer and one Horizonmacro cabinet. In Figure 12-57 the Horizon II macro is the master
cabinet, whereas in Figure 12-58 the Horizonmacro is the master cabinet.
Figure 12-57 Sector 2/2/2 configuration (Horizon II macro as master cabinet)
2B 1B 0B B A 0A 1A 2A
SURF2 SURF EXT

RX
ANT
BLANK BLANK BLANK BLANK BLANK DUP
EMPTY EMPTY EMPTY EMPTY EMPTY CTU2

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD HIISC FMUX

12-94 68P02900W21-R
GMR-01 28 Feb 2006
Figure 12-58 Sector 2/2/2 configuration (Horizonmacro as master cabinet)
2B 1B 0B B A 0A 1A 2A
SURF2 SURF EXT

RX
ANT
BLANK BLANK BLANK BLANK BLANK DUP
EMPTY EMPTY EMPTY EMPTY EMPTY CTU2

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD XMUX MCUF

slave cabinet master cabinet
68P02900W21-R 12-95
28 Feb 2006 GMR-01

Figure 12-59 shows a suggested configuration for sector 4/4/4, using one Horizon II macro cabinet with
duplexers and one Horizonmacro cabinet.
Figure 12-59 Sector 4/4/4 configuration with Horizon II macro and Horizonmacro cabs
2B 1B 0B B A 0A 1A 2A
SURF2 SURF EXT

RX RX RX RX
ANT ANT ANT ANT

BLANK DUP DUP BLANK DUP DUP

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD HIISC FMUX

12-96 68P02900W21-R
GMR-01 28 Feb 2006

Figure 12-60 shows a suggested configuration for sector 6/6/6, using one Horizon II macro cabinet with
duplexers and dual hybrid combiner units and one Horizonmacro cabinet.
Figure 12-60 Sector 6/6/6 configuration with Horizon II macro and Horizonmacro cabs
2B 1B 0B B A 0A 1A 2A
SURF EXT
5 4 3 2 1 0 DDF F’THRU DDF

DHU DHU
RX RX
ANT ANT
BLANK DUP BLANK DUP

5 4 3 2 1 0 5 4 3 2 1 0
SITE EXPANSION
BOARD HIISC FMUX

68P02900W21-R 12-97
28 Feb 2006 GMR-01
Using CTU2s in Horizonmacro cabinets
Figure 12-61 shows an example of a configuration with CTU2s (operating in single density mode) installed
in a Horizonmacro cabinet.
Figure 12-61 Horizonmacro cabinet configuration using CTUs and CTU2s
2B 1B 0B 2A 1A 0A B A
SURF EXT
DCF DCF DCF
CTU2 CTU2
5 4 3 2 1 0
MCUF
Horizonmacro cabinet
12-98 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Connecting Horizon II macro cabinets to M-Cell6 cabinets
Connecting Horizon II macro cabinets to M-Cell6

cabinets
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Connection overview
This section provides examples of how older generation M-Cell6 BTS equipment can be connected to the
latest generation Horizon II macro BTS equipment.
M-Cell2 BTS cabinets cannot be connected to Horizon II macro BTS cabinets.
Compatibility issues
The following points must be taken into account when connecting Horizon II macro cabinets to M-Cell6
cabinets:
• Although the Horizon II macro equipment is totally compatible with M-Cell6 equipment, none
of the Horizon II macro components can be used in the M-Cell6.
• In cases where the M-Cell6 BTS is the master cabinet and the MCU is the master site controller,
the MCU must have a 20 Mbyte PCMCIA card installed running CSFP to accommodate the
added memory requirements of the GSR6 (Horizon II) objects.
• In cases where the M-Cell6 BTS is the site controller and has CTU2 Adapters running, the
MCU must have a 20 Mbyte PCMCIA card installed running CSFP to accommodate the use of
the CTU2 transceiver from a code storage standpoint. A CTU2 can be used in an M-Cell6
cabinet when the CTU2 Adapter is used.
• The M-Cell6 must have a FMUX installed to communicate with the Horizon II macro cabinet.
• When DCS1800 cabinets are connected, connections between the Horizon II macro SURF2
and the M-Cell6 LNAs must include -13 dB attenuators.
68P02900W21-R 12-99
28 Feb 2006 GMR-01
Connecting Horizon II macro cabinets to M-Cell6 cabinets Chapter 12: Standard BSS and Horizon BTS configurations
900 MHz BTSs
Figure 12-62 shows how a 900 MHz Horizon II macro BTS cabinet may be connected to a 900 MHz M-Cell6
BTS cabinet to create a 2 sector (4/4) configuration.
Figure 12-62 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections
SECTOR 1 SECTOR 2
DUPLEXER
DUPLEXER
2B 1B 0B B A 0A 1A 2A DLNB
SURF2
IADU
5 4 3 2 1 0
RX RX
ANT ANT
BLANK BLANK DUP BLANK BLANK DUP BLANK CBF1 CBF0
T T T T
EMPTY EMPTY CTU2 EMPTY EMPTY CTU2 C C C C
U U U U FMUX
5 4 3 2 1 0
SITE EXPANSION
HIISC
Horizon II macro BOARD
master cabinet M-Cell6 slave cabinet
12-100 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Connecting Horizon II macro cabinets to M-Cell6 cabinets
1800 MHz BTSs
Figure 12-63 shows how an 1800 MHz Horizon II macro BTS cabinet may be connected to an 1800 MHz
M-Cell6 BTS cabinet to create a 2 sector (4/4) configuration.
Figure 12-63 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections
SECTOR 1 SECTOR 2
DUPLEXER
DUPLEXER
2B 1B 0B B A 0A 1A 2A
SURF2 LNA
5 4 3 2 1 0
RX RX
ANT ANT
BLANK BLANK DUP BLANK BLANK DUP BLANK CBF1 CBF0
T T T T
EMPTY EMPTY CTU2 EMPTY EMPTY CTU2 C C C C
U U U U FMUX
5 4 3 2 1 0
SITE EXPANSION
HIISC
Horizon II macro BOARD
master cabinet M-Cell6 slave cabinet
68P02900W21-R 12-101
28 Feb 2006 GMR-01
Connecting Horizon II macro cabinets to M-Cell6 cabinets Chapter 12: Standard BSS and Horizon BTS configurations
12-102 68P02900W21-R
GMR-01 28 Feb 2006
Chapter
13
M-Cell BTS configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This is included for reference purposes. It provides diagrams of the logical interconnections of the components
in older 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, "Standard BSS and Horizon BTS configurations,".
• "Standard M-Cell configurations" on page 13-2
• "Single cabinet BTS configurations" on page 13-3
• "Two cabinet BTS configuration" on page 13-5
• "Three cabinet BTS configuration " on page 13-7
• "Four cabinet BTS configuration" on page 13-8
• "M-Cell RF configurations" on page 13-10
68P02900W21-R 13-1
28 Feb 2006 GMR-01
Standard M-Cell configurations Chapter 13: M-Cell BTS configurations
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.
For typical BSS configurations, refer to Figure 12-1 and Figure 12-2 in Chapter 12, "Standard
BSS and Horizon BTS configurations,".
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 13-1 and Figure 13-2).
13-2 68P02900W21-R
GMR-01 28 Feb 2006
Single cabinet BTS configurations

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Single cabinet M-Cell6 BTS
The configuration shown in Figure 13-1 is an example of a single cabinet M-Cell6 BTS. This configuration
Figure 13-1 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
68P02900W21-R 13-3
28 Feb 2006 GMR-01
Single cabinet BTS configurations Chapter 13: M-Cell BTS configurations
Single cabinet M-Cell2 BTS
The configuration shown in Figure 13-2 is an example of a single cabinet M-Cell2 BTS. This configuration
supports two carriers.
Figure 13-2 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
13-4 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Two cabinet BTS configuration
Two cabinet BTS configuration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Two cabinet M-Cell6 BTS
The configuration shown in Figure 13-3 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 13-3 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 M
T T T T T T O
C X U
C C C C C X
U U U U U U
68P02900W21-R 13-5
28 Feb 2006 GMR-01
Two cabinet BTS configuration Chapter 13: M-Cell BTS configurations
Two cabinet M-Cell6 BTS with CTU2 Adapter
The configuration shown in Figure 13-4 is an example of a two cabinet M-Cell6 BTS when CTU2 Adapters
are used. This configuration supports 24 carriers. The MCUs interface to the CTU2s through the FOX or
the FMUX/FOX.
Figure 13-4 Two cabinet M-Cell6 BTS with CTU2 Adapters
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
C C C C C C
T T T T T T
U U U U U U
2 2 2 2 2 2
12
M-CELL6 mBCU
BTS CABINET 2 2 2 2 2 2
F
C C F M
C C C C O
T T T T T T X U
U U U U U U X
2 2 2 2 2 2
Image002.eps
13-6 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Three cabinet BTS configuration
Three cabinet BTS configuration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Three cabinet M-Cell2 BTS
The configuration shown in Figure 13-5 is an example of a three cabinet M-Cell2 BTS. This configuration
Figure 13-5 Three cabinet M-Cell2 BTS
mBCU
M-CELL2 CABINET
N
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
68P02900W21-R 13-7
28 Feb 2006 GMR-01
Four cabinet BTS configuration Chapter 13: M-Cell BTS configurations
Four cabinet BTS configuration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Four cabinet M-Cell6 BTS
The configuration shown in Figure 13-6 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.
13-8 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning Four cabinet BTS configuration
Figure 13-6 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
BTS 2 2 2 2 2 2
CABINET F
F M
T T T T T T O
C X U
C C C C C X
U U U U U U
12
M-CELL6
BTS 2 2 2 2 2 2 mBCU
CABINET
F F
T T T T T M
T O U
C C C C C C X
U U U U U X
U
M-CELL6 12
BTS 2 2 2 2 2 2
mBCU
CABINET
F
F M
T T T T T T O
C C C C C U
C X X
U U U U U U
68P02900W21-R 13-9
28 Feb 2006 GMR-01
M-Cell RF configurations Chapter 13: M-Cell BTS configurations
M-Cell RF configurations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of M-Cell configuration diagrams
The M-Cell BTS cabinets are presented as follows:

• M-Cell6 single cabinet.
• M-Cell6 multiple cabinets.
• 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 13-7
to Figure 13-42:
• In an M-Cell6 BTS cabinet, a maximum of six TCUs can be accommodated.
• In an M-Cell6 BTS cabinet, a maximum of twelve carriers can be accommodated when

CTU2 Adapters are used.
• In an M-Cell2 BTS cabinet, a maximum of two TCUs can be accommodated.
• An external equipment cabinet is not required, unless specifically stated in the text
accompanying the configuration diagram.
• In an M-Cell6 side cabinet, a maximum of three high power duplexers can be accommodated.
M-Cell6 cabinets
Diversity is assumed in all figures, unless stated otherwise.
13-10 68P02900W21-R
GMR-01 28 Feb 2006
System Information: BSS Equipment Planning M-Cell RF configurations
[GSM900] 3 carrier omni, with hybrid combining and diversity

A single cabinet, four TCU configuration with hybrid combining and diversity, is shown in Figure 13-7.
Figure 13-7 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
68P02900W21-R 13-11
28 Feb 2006 GMR-01
Table 13-1 Equipment required for single cabinet, 4 TCU configuration with hybrid 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
13-12 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 carrier omni, with hybrid combining, diversity, and medium power duplexer
Figure 13-8 3 carrier omni, hybrid combining, medium power duplexer

Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
DLNB
RF INPUT
RF LOAD
IADU
3-INPUT
CBF
Non-
HCOMB 4 4
T T T
C C C
U U U
A A A
B B B
M-Cell6 BTS CABINET
68P02900W21-R 13-13
28 Feb 2006 GMR-01
Table 13-2 Equipment required for single cabinet, 4 TCU configuration with hybrid combining,
diversity and medium power duplexer
Quantity Unit
2 Antennas
3 TCU
Transmitter
1 3-input CBF
Receiver
1 DLNB
1 Medium power duplexer
13-14 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 4 carrier omni, with hybrid combining and diversity

Figure 13-9 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
68P02900W21-R 13-15
28 Feb 2006 GMR-01
diversity
Quantity Unit
3 Antennas
4 TCU
Transmitter
1 3-input CBF
1 Hybrid combining block (HCOMB)
Receiver
1 DLNB
13-16 68P02900W21-R
GMR-01 28 Feb 2006
[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 13-10. Table 13-4 provides a summary of the equipment required for this configuration.
Figure 13-10 4 carrier omni, hybrid combining, medium power duplexer
Tx/Rx ANTENNA Rx ANTENNA
DUPLEXER
RF INPUT
RF LOAD
DLNB
3-INPUT
HCOMB CBF IADU
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
68P02900W21-R 13-17
28 Feb 2006 GMR-01
Quantity Unit
2 Antennas
4 TCU
Transmitter
1 3-input CBF
1 Hybrid combining block (HCOMB)
Receiver
1 DLNB
13-18 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 6 carrier omni, with cavity combining and diversity

A single cabinet, six TCU configuration with cavity combining and diversity, is shown in Figure 13-11.
Figure 13-11 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
68P02900W21-R 13-19
28 Feb 2006 GMR-01
Table 13-5 Equipment required for single cabinet, 6 TCU configuration with cavity combining and
diversity
Quantity Unit
3 Antennas
6 TCU
Transmitter
1 CCB (Output)
1 CCB (Extension)
Receiver
1 DLNB
13-20 68P02900W21-R
GMR-01 28 Feb 2006
[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 13-12. Table 13-6 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.
Figure 13-12 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
68P02900W21-R 13-21
28 Feb 2006 GMR-01
Table 13-6 Equipment required for single cabinet, 6 TCU configuration with cavity 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
13-22 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 8 carrier omni, with combining and diversity

A dual cabinet, 8 TCU configuration with combining and diversity, is shown in Figure 13-13. Table 13-7
Figure 13-13 8 carrier omni, combining
Tx Tx/Rx Rx
A B
Rx EXT DUPLEXER
BLOCK
DLNB
IADU
CBF
IADU
CCB CCB
6 6
2 2
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
68P02900W21-R 13-23
28 Feb 2006 GMR-01
Table 13-7 Equipment required for multiple cabinet, 8 TCU configuration with combining and
diversity
Quantity Unit
3 Antennas
8 TCU
Transmitter
1 CBF
1 CCB (Output)
1 CCB (Extension)
Receiver
1 DLNB
1 Rx extension block
13-24 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 13-14.
Figure 13-14 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
68P02900W21-R 13-25
28 Feb 2006 GMR-01
diversity
Quantity Unit
6 Antennas
6 TCU
Transmitter
2 3-input CBF
Receiver
2 DLNB
13-26 68P02900W21-R
GMR-01 28 Feb 2006
[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
Figure 13-15 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
68P02900W21-R 13-27
28 Feb 2006 GMR-01
Table 13-9 Equipment required for single cabinet, 6 TCU configuration with combining, diversity
and medium power duplexer
Quantity Unit
4 Antennas
6 TCU
Transmitter
2 3-input CBF
Receiver
2 DLNB
13-28 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 sector (2/2/2), with combining and diversity

A single cabinet, six TCU configuration with combining and diversity, is shown in Figure 13-16. Table 13-10
Figure 13-16 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
68P02900W21-R 13-29
28 Feb 2006 GMR-01
Table 13-10 Equipment required for single cabinet, 6 TCU configuration with combining and
diversity
Quantity Unit
9 Antennas
6 TCU
Transmitter
3 CBF
Receiver
3 DLNB
13-30 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 sector (2/2/2), with cavity combining, diversity, and medium power
duplexers
A single cabinet, six TCU configuration with cavity combining, diversity, and medium power duplexers, is
Figure 13-17 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
68P02900W21-R 13-31
28 Feb 2006 GMR-01
Table 13-11 Equipment required for single cabinet, 6 TCU configuration with combining, diversity
and medium power duplexers
Quantity Unit
6 Antennas
6 TCU
Transmitter
3 CBF
Receiver
3 DLNB
13-32 68P02900W21-R
GMR-01 28 Feb 2006
[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 13-18. Table 13-12 provides a summary of the equipment required for this configuration.
Figure 13-18 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
68P02900W21-R 13-33
28 Feb 2006 GMR-01
Table 13-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
13-34 68P02900W21-R
GMR-01 28 Feb 2006
[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 duplexers, is
Figure 13-19 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
BLOCK DLNB DLNB
IADU IADU
CBF2 CBF1 CBF0 CBF2 CBF1 CBF0
6 6 6 6
68P02900W21-R 13-35
28 Feb 2006 GMR-01
Table 13-13 Equipment required for multiple cabinet, 12 TCU configuration with air combining,
diversity and medium power duplexers (2 antenna per sector)
Quantity Unit
6 Antennas
12 TCU
Transmitter
6 CBF
Receiver
3 DLNB
13-36 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 sector (4/4/4), with cavity combining and diversity

A multiple cabinet, 12 TCU configuration with cavity combining and diversity, is shown in Figure 13-20.
Figure 13-20 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.
68P02900W21-R 13-37
28 Feb 2006 GMR-01
Table 13-14 Equipment required for multiple cabinet, 12 TCU configuration with hybrid combining
and diversity
Quantity Unit
6 Antennas
12 TCU
Transmitter
3 CCB (output)
3 CCB (extension)
Receiver
3 DLNB
13-38 68P02900W21-R
GMR-01 28 Feb 2006
[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 13-21. Table 13-15 provides a summary of the equipment required for this configuration.
Figure 13-21 3 sector (4/4/4), 3-input CBF, hybrid combining

Rx Tx Tx Tx Rx Rx
RF INPUT
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
68P02900W21-R 13-39
28 Feb 2006 GMR-01
Table 13-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
13-40 68P02900W21-R
GMR-01 28 Feb 2006
[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 13-22. Table 13-16 provides a summary of the equipment required for this
configuration.
Figure 13-22 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers
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

CBF HCOMB HCOMB CBF
CBF
68P02900W21-R 13-41
28 Feb 2006 GMR-01
Table 13-16 Equipment required for multiple cabinet, 12 TCU configuration with 3-input CBF, air
combining, diversity and medium power duplexers
Quantity Unit
6 Antennas
12 TCU
Transmitter
3 3-input CBF
Receiver
3 DLNB
13-42 68P02900W21-R
GMR-01 28 Feb 2006
duplexers (3 antenna per sector)
A three cabinet, 15 TCU configuration with 3-input CBF, air combining, diversity, and medium power
configuration.
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
MASTER M-Cell6 BTS CABINET

Extender 1 and extender 2 M-Cell6 cabinets configured similar to the master
cabinet for sectors 2 and 3.
68P02900W21-R 13-43
28 Feb 2006 GMR-01
Table 13-17 Equipment required for 3 cabinets, 15 TCU configuration with 3-input 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
13-44 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity, and medium power
A three cabinet, 15 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers,
is shown in Figure 13-24. Table 13-18 provides a summary of the equipment required for this configuration.
Figure 13-24 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers
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

68P02900W21-R 13-45
28 Feb 2006 GMR-01
Table 13-18 Equipment required for 3 cabinets, 15 TCU configuration with 3-input CBF, combining,
diversity and medium power duplexers (2 antennas/sector)
Quantity Unit
6 Antennas
15 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB
13-46 68P02900W21-R
GMR-01 28 Feb 2006
[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 duplexers, is
An external equipment rack/cabinet is required for a high-power duplexer in an indoor installation.
Figure 13-25 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.
68P02900W21-R 13-47
28 Feb 2006 GMR-01
Table 13-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
13-48 68P02900W21-R
GMR-01 28 Feb 2006
A three cabinet, 18 TCU configuration with 3-input CBF, air combining, diversity, and medium power
configuration.
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

68P02900W21-R 13-49
28 Feb 2006 GMR-01
Quantity Unit
9 Antennas
18 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB
13-50 68P02900W21-R
GMR-01 28 Feb 2006
A three cabinet, 18 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers,
is shown in Figure 13-27. Table 13-21 provides a summary of the equipment required for this configuration.
Figure 13-27 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers
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

68P02900W21-R 13-51
28 Feb 2006 GMR-01
Quantity Unit
6 Antennas
18 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB
13-52 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and medium power duplexers
A four cabinet, 24 TCU configuration with cavity combining, diversity and medium power duplexers, is
shown in Figure 13-28/ Figure 13-29. Table 13-22 provides a summary of the equipment required for
this configuration.
Figure 13-28 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
68P02900W21-R 13-53
28 Feb 2006 GMR-01
Figure 13-29 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)
Rx Tx
ANTENNA ANTENNA
DUPLEXER 2
DUPLEXER 1
TO
MASTER M-Cell6 DUPLEXER 0
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.
13-54 68P02900W21-R
GMR-01 28 Feb 2006
diversity and medium power duplexers
Quantity Unit
9 Antennas
24 TCU
Transmitter
3 CCB (output)
3 CCB (extension)
3 CBF
Receiver
3 DLNB
3 Rx extender block
68P02900W21-R 13-55
28 Feb 2006 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 13-30/ Figure 13-31. Table 13-23 provides a summary of the equipment
An external equipment rack/cabinet is required for a high power duplexer in an indoor installation.
Figure 13-30 3 sector (8/8/8), cavity combining, high and medium pwr duplexers (Pt 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
13-56 68P02900W21-R
GMR-01 28 Feb 2006
Figure 13-31 3 sector (8/8/8), cavity combining, high and medium pwr duplexers (Pt 2)
DUPLEXER 2
TO MASTER Tx/Rx Tx/Rx Tx/Rx
DUPLEXER 1 ANTENNA ANTENNA ANTENNA
M-Cell6
BTS CABINET DUPLEXER 0 (SECTOR 3)(SECTOR 2) (SECTOR 1)
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.
68P02900W21-R 13-57
28 Feb 2006 GMR-01
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
13-58 68P02900W21-R
GMR-01 28 Feb 2006
A four cabinet, 24 TCU configuration with 3-input CBF, air combining, diversity, and medium power
duplexers, is shown in Figure 13-32/ Figure 13-33. Table 13-24 provides a summary of the equipment
Figure 13-32 3 sector (4/4/4), 3-input CBF, air combining, medium pwr duplexers (Pt 1)
TO
EXTENDER 1
IADU M-Cell6
BTS CABINET
Tx Tx/Rx Rx
ANTENNA Tx
(SECTOR 3) ANTENNA ANTENNA ANTENNA
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
68P02900W21-R 13-59
28 Feb 2006 GMR-01
Figure 13-33 3 sector (8/8/8), 3-input CBF, air combining, medium pwr duplexers (Pt 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
13-60 68P02900W21-R
GMR-01 28 Feb 2006
Quantity Unit
9 Antennas
24 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB
68P02900W21-R 13-61
28 Feb 2006 GMR-01
A four cabinet, 24 TCU configuration with 3-input CBF, combining, diversity, and medium power duplexers,
is shown in Figure 13-34/ Figure 13-35. Table 13-25 provides a summary of the equipment required
Figure 13-34 3 sector (8/8/8), 3-input CBF, combining, medium pwr duplexers (Pt 1)
Tx Tx/Rx TO
ANTENNA ANTENNA DUPLEXER EXTENDER 1
(SECTOR 3) (SECTOR 3) M-Cell6
IADU BTS CABINET
RF INPUT
RF LOAD
DUPLEXER
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
13-62 68P02900W21-R
GMR-01 28 Feb 2006
Figure 13-35 3 sector (8/8/8), 3-input CBF, combining, medium pwr duplexers (Pt 2)
TO EXTENDER 2 DUPLEXER
M-Cell6 BTS CABINET Rx REV BLOCK 1
Tx/Rx Tx/Rx
ANTENNA ANTENNA
Tx/Rx Tx/Rx
ANTENNA ANTENNA
(SECTOR 2) (SECTOR 2) RF INPUT
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
68P02900W21-R 13-63
28 Feb 2006 GMR-01
Quantity Unit
6 Antennas
24 TCU
Transmitter
6 3-input CBF
Receiver
3 DLNB
13-64 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU configuration with hybrid combining and diversity, is shown in Figure 13-36.
Figure 13-36 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
68P02900W21-R 13-65
28 Feb 2006 GMR-01
diversity
Quantity Unit
9 Antennas
6 TCU
Transmitter
3 TxBPF
3 Hybrid combiner
Receiver
3 LNA
13-66 68P02900W21-R
GMR-01 28 Feb 2006
[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and medium power
duplexers
A single cabinet, six TCU configuration with hybrid combining, diversity, and medium power duplexers, is
Figure 13-37 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
68P02900W21-R 13-67
28 Feb 2006 GMR-01
diversity and medium power duplexers
Quantity Unit
6 Antennas
6 TCU
Transmitter
3 Hybrid combiner
Receiver
3 LNA
13-68 68P02900W21-R
GMR-01 28 Feb 2006
M-Cell2 cabinets
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 Figure 13-38.
Figure 13-38 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
68P02900W21-R 13-69
28 Feb 2006 GMR-01
diversity
Quantity Unit
3 Antennas
2 TCU
Transmitter
1 CBF
Receiver
1 DLNB
13-70 68P02900W21-R
GMR-01 28 Feb 2006
[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
Figure 13-39 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
68P02900W21-R 13-71
28 Feb 2006 GMR-01
Quantity Unit
2 Antennas
2 TCU
Transmitter
1 CBF
Receiver
1 DLNB
13-72 68P02900W21-R
GMR-01 28 Feb 2006
[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-40. Table 13-30 provides a
summary of the equipment required for this configuration.
Figure 13-40 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
68P02900W21-R 13-73
28 Feb 2006 GMR-01
Table 13-30 Equipment required for single cabinet, 2 TCU configuration with diversity
Quantity Unit
6 Antennas
2 TCU
Transmitter
2 CBF
Receiver
2 DLNB
[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU configuration with air combining and diversity, is shown in Figure 13-41.
Figure 13-41 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
13-74 68P02900W21-R
GMR-01 28 Feb 2006
Table 13-31 Equipment required for single cabinet, 2 TCU configuration with air combining and
diversity
Quantity Unit
3 Antennas
2 TCU
Transmitter
1 TxBPF
Receiver
1 LNA
68P02900W21-R 13-75
28 Feb 2006 GMR-01
[DCS1800] 2 sectors, with diversity

A single cabinet, two TCU configuration with diversity, is shown in Figure 13-42. Table 13-32 provides a
summary of the equipment required for this configuration.
Figure 13-42 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
13-76 68P02900W21-R
GMR-01 28 Feb 2006
Table 13-32 Equipment required for single cabinet, 2 TCU configuration with diversity
Quantity Unit
6 Antennas
2 TCU
Transmitter
2 TxBPF
Receiver
2 LNA
68P02900W21-R 13-77
28 Feb 2006 GMR-01
13-78 68P02900W21-R
GMR-01 28 Feb 2006
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
16/32 kbit/s TRAU . . . . . . . . . . . . . . . 3-85 {24347} Advanced Speech Call Item . . . . . . 1-15
{22322} BSC Reset Management . . . . . . . . 1-15 {24347} eMLPP . . . . . . . . . . . . . . . . 1-15
{23769} VersaTRAU . . . . . . . . . . . . 1-16, 8-8 {24347} Enhanced Multi-level Precedence and
{23956} Quality of Service . . . . . . . . . . . 1-17 Pre-emption . . . . . . . . . . . . . . . . . . 1-15
A
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Acronyms . . . . . . . . . . . . . . . . . . . 1-23 AMR (contd.)

Adaptive multi-rate (AMR) . . . . . . . . . . . 3-10 new hardware . . . . . . . . . . . . . . . . 4-3
Air interface control channels . . . . . . . . . 3-125 AMR Full Rate speech channel encoding. . . . . 3-62
air interface planning . . . . . . . . . . . . . 3-180 AMR Half Rate speech channel encoding . . . . 3-64
Alarm reporting . . . . . . . . . . . . . . . . 2-15 Antenna configurations . . . . . . . . . . . . . 5-18
Alternative call model Antenna gain. . . . . . . . . . . . . . . . . . 3-35
planning examples . . . . . . . . . . . . . . 9-19 Ater interface
AMR auto-connect mode . . . . . . . . . . . . . . 2-23
basic operation. . . . . . . . . . . . . . . . 4-2 backwards compatibility mode . . . . . . . . 2-24
description. . . . . . . . . . . . . . . . . . 1-11 enhanced auto-connect mode . . . . . . . . . 2-25
half rate parameter descriptions . . . . . . . . 4-26 Auto-connect mode
half rate utilization . . . . . . . . . . . . . . 4-26 XBL links . . . . . . . . . . . . . . . . . . 6-52
interaction with GSM half rate . . . . . . . . 4-3 Average call duration . . . . . . . . . . . . . . 11-5
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Backhaul BSC (contd.)

AMR . . . . . . . . . . . . . . . . . . . . 4-36 signalling link capacities . . . . . . . . . . . 6-11
Baseband hopping . . . . . . . . . . . . . 1-9, 3-51 system capacity . . . . . . . . . . . . . . . 6-7
restrictions. . . . . . . . . . . . . . . . . . 5-16 to BTS interconnections . . . . . . . . . . . 2-4
rules for . . . . . . . . . . . . . . . . . . 3-118 BSS
BCCH carrier block diagram . . . . . . . . . . . . . . . . 1-5
options . . . . . . . . . . . . . . . . . . 3-158 code storage facility processor . . . . . . . . 1-10
BCCH RTF interfaces . . . . . . . . . . . . . . . . . . 2-2
configuration . . . . . . . . . . . . . . . . 5-17 maximum network parameter values. . . . . . 8-12
BIB planning checklist . . . . . . . . . . . . . . 1-22
planning (BSC) . . . . . . . . . . . . . . . 6-96 planning for EGPRS . . . . . . . . . . . . . 8-2
planning (RXCDR) . . . . . . . . . . . . . 7-39 planning for GPRS . . . . . . . . . . . . . . 8-2
Blocking. . . . . . . . . . . . . . . . . . . . 3-8 planning overview . . . . . . . . . . . . . . 1-19
BSC standard configurations . . . . . . . . . . . . 12-2
equipage planning . . . . . . . . . . . . . . 6-3 system architecture . . . . . . . . . . . . . . 1-4
mixing equipment types . . . . . . . . . . . 6-3 system components . . . . . . . . . . . . . 1-6
planning steps outline . . . . . . . . . . . . 6-4 typical hardware configuration diagrams . . . . 12-3
scaleable architecture. . . . . . . . . . . . . 6-8 upgrade rules to support GPRS . . . . . . . . 8-11
68P02900W21-R IX-1
28 Feb 2006 GMR-01
Index
BSS timeslot allocation . . . . . . . . . . . . 3-171 BSU shelves

BSS to PCU planning example planning . . . . . . . . . . . . . . . . . . . 6-84
EGPRS BTS
{23956} QoS disabled . . . . . . . . . . . 8-68 site restrictions. . . . . . . . . . . . . . . . 2-6
{23956} QoS enabled . . . . . . . . . . . 8-76 standard configurations . . . . . . . . . . . . 12-2
GPRS . . . . . . . . . . . . . . . . . . . . 8-59 to BSC interconnections . . . . . . . . . . . 2-4
BSSC3 BTS planning . . . . . . . . . . . . . . . . . 5-2
cabinet configurations . . . . . . . . . . . . 4-34
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
C7 protocol . . . . . . . . . . . . . . . . . . 6-21 Coding schemes (contd.)

Call parameters . . . . . . . . . . 3-122, 6-15, 11-2 CS3 . . . . . . . . . . . . . . . . . . . . . 3-82
sample statistic calculations. . . . . . . . . 11-12 CS4 . . . . . . . . . . . . . . . . . . . . . 3-83
Call reconfiguration threshold . . . . . . . . . . 4-27 EGPRS . . . . . . . . . . . . . . . . . . . 3-86
Carrier timeslot allocation GPRS . . . . . . . . . . . . . . . . . . . . 3-79
examples . . . . . . . . . . . . . . . . . 3-162 MCS-1 . . . . . . . . . . . . . . . . . . . 3-87
CCCH calculations . . . . . . . . . . . . . . 3-129 MCS-2 . . . . . . . . . . . . . . . . . . . 3-88
Cell architecture . . . . . . . . . . . . . . . 3-109 MCS-3 . . . . . . . . . . . . . . . . . . . 3-89
Cell broadcast channel . . . . . . . . . . . . . 1-10 MCS-4 . . . . . . . . . . . . . . . . . . . 3-90
Cell broadcast link . . . . . . . . . . . . . . . 6-66 MCS-5 . . . . . . . . . . . . . . . . . . . 3-91
Cell reselection MCS-6 . . . . . . . . . . . . . . . . . . . 3-92
2G-3G . . . . . . . . . . . . . . . . . . 3-119 MCS-7 . . . . . . . . . . . . . . . . . . . 3-93
Cell resource manager . . . . . . . . . . . . . 8-5 MCS-8 . . . . . . . . . . . . . . . . . . . 3-94
Cell site sectorization . . . . . . . . . . . . . . 3-50 MCS-9 . . . . . . . . . . . . . . . . . . . 3-95
Circuit pooling Comfort noise
AMR . . . . . . . . . . . . . . . . . . . . 4-24 (VAD). . . . . . . . . . . . . . . . . . . . 3-98
Clock extender (CLKX) Congestion relief
planning (BSC) . . . . . . . . . . . . . . . 6-92 AMR . . . . . . . . . . . . . . . . . . . . 4-26
planning (RXU) . . . . . . . . . . . . . . . 7-35 control channel configuration planning. . . . . 3-126
Co-channel interference. . . . . . . . . . . . . 3-48 Control channel configurations . . . . . 3-134, 3-146
code storage facility processor. . . . . . . . . . 6-67 border location area . . . . . . . . . . . . 3-149
Code storage facility processor . . . . . . . . . 1-10 non-border location area . . . . . . . . . . 3-146
Codec modes CTU. . . . . . . . . . . . . . . . . . . . . . 5-19
AMR . . . . . . . . . . . . . . . . . . . . 4-17 CTU and CTU2
Coding scheme power supply considerations . . . . . . . . . 5-20
initial configurable . . . . . . . . . . . . . 3-203 CTU2 . . . . . . . . . . . . . . . . . . . . . 5-19
Coding schemes configuration with EGPRS . . . . . . . . . . 5-16
CS1 . . . . . . . . . . . . . . . . . . . . . 3-80 in Horizonmacro . . . . . . . . . . . . . . 12-98
CS2 . . . . . . . . . . . . . . . . . . . . . 3-81
D
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
daisy chain connection . . . . . . . . . . . . . 2-8 Discontinuous transmission

daisy chain examples . . . . . . . . . . . . . . 2-9 (DTX). . . . . . . . . . . . . . . . . . . . 3-99
Decibel Diversity. . . . . . . . . . . . . . . . . . . . 1-8
conversion factors . . . . . . . . . . . . . . 3-17 Horizon II macro. . . . . . . . . . . . . . 12-35
Digital shelf power supply DPROC
planning (BSC) . . . . . . . . . . . . . . . 6-98 PCU planning process . . . . . . . . . . . . 8-23
planning (RXCDR) . . . . . . . . . . . . . 7-41 DRI and combiner configurations . . . . . . . . 5-44
Directed retry . . . . . . . . . . . . . . . . . 8-5 DSW2 . . . . . . . . . . . . . . . . . . . . . 4-33
IX-2 68P02900W21-R
GMR-01 28 Feb 2006
Index
DSW2 (contd.) DTX SACCH multiframe

planning (BSC) . . . . . . . . . . . . . . . 6-80 Full Rate . . . . . . . . . . . . . . . . . . 3-99
planning (RXCDR) . . . . . . . . . . . . . 7-24 Half Rate . . . . . . . . . . . . . . . . . 3-100
DSWX . . . . . . . . . . . . . . . . . . . . 4-33 Dynamic allocation
planning (BSC) . . . . . . . . . . . . . . . 6-88 BSC to BTS . . . . . . . . . . . . . . . . . 8-4
planning (RXU) . . . . . . . . . . . . . . . 7-31 RXCDR to BSC circuits . . . . . . . . . . . 2-23
E
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
E1 circuit EGPRS enabled CTU2

star connection. . . . . . . . . . . . . . . . 2-7 configuration . . . . . . . . . . . . . . . . 5-16
E1 link calculations. . . . . . . . . . . . . . . 6-75 limitations . . . . . . . . . . . . . . . . . . 5-16
BSC to BTS . . . . . . . . . . . . . . . . . 6-35 Emergency call handling
BSC to RXCDR . . . . . . . . . . . . . . . 7-7 AMR . . . . . . . . . . . . . . . . . . . . 4-24
RXCDR to MSC . . . . . . . . . . . . . . . 7-9 Emergency call pre-emption. . . . . . . . . . . 8-5
E1 links Encoding
cable requirements for a fully configured GSM circiut-switched data channel . . . . . . 3-69
PCU . . . . . . . . . . . . . . . . . . . . 8-17 GSM control channel. . . . . . . . . . . . . 3-68
PCU to BSC . . . . . . . . . . . . . . . . . 8-41 GSM speech channel . . . . . . . . . . . . . 3-58
EGDP . . . . . . . . . . . . . . . . . . . . . 4-34 AMR Full Rate . . . . . . . . . . . . . . 3-62
planning . . . . . . . . . . . . . . . . . . . 7-15 AMR Half Rate . . . . . . . . . . . . . . 3-64
EGDP2 . . . . . . . . . . . . . . . . . . . . 4-34 enhanced Full Rate . . . . . . . . . . . . 3-60
EGPRS . . . . . . . . . . . . . . . . . . . . 1-11 Enhanced auto-connect mode
air interface planning . . . . . . . . . . . . 3-180 XBL links . . . . . . . . . . . . . . . . . . 6-52
BSS maximum network parameter values . . . 8-12 Enhanced BSC capacity. . . . . . . . . . . . . 6-9
BSS planning . . . . . . . . . . . . . . . . 8-2 Enhanced Full Rate speech channel encoding. . . 3-60
BSS to PCU planning example Enhanced one phase
{23956} QoS disabled . . . . . . . . . . . 8-68 RSL planning . . . . . . . . . . . . . 6-24, 6-30
{23956} QoS enabled . . . . . . . . . . . 8-76 Enhanced one phase access
carrier . . . . . . . . . . . . . . . . . . . 3-157 GSL planning . . . . . . . . . . . . . . . . 6-56
cell planning/deployment influencing Enhanced-GPRS (EGPRS) . . . . . . . . . . . 1-11
factors. . . . . . . . . . . . . . . . . . . 3-180 Equalization . . . . . . . . . . . . . . . . . 3-103
control channel configuration planning . . . 3-126 Error coding schemes . . . . . . . . . . . . . . 3-53
data rates . . . . . . . . . . . . . . . . . 3-203 Expansion
dynamic timeslot allocation . . . . . . . . . 3-156 BTS sites . . . . . . . . . . . . . . . . . . 5-41
estimating traffic throughput . . . . . . . . 3-187 Horizon II macro. . . . . . . . . . . . . . . 5-30
network planning . . . . . . . . . . . . . 3-152 Horizon II mini . . . . . . . . . . . . . . . 5-30
radio and packet data traffic channels . . . . 3-125 Extended range cells
timeslot usage . . . . . . . . . . . . . . . 3-153 AMR . . . . . . . . . . . . . . . . . . . . 1-12
traffic planning . . . . . . . . . . . . . . 3-151 GSM Half Rate . . . . . . . . . . . . . . . 1-13
F
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
File transit delay . . . . . . . . . . . . . . . 3-201 Frequency hopping . . . . . . . . . . 1-9, 3-51, 8-6

FMUX. . . . . . . . . . . . . . . . . . . . . 5-32 Frequency planning. . . . . . . . . . . . . . 3-113
FOX. . . . . . . . . . . . . . . . . . . . . . 5-32 Frequency spectrum
Frequency bands DCS1800 . . . . . . . . . . . . . . . . . . 3-5
all systems. . . . . . . . . . . . . . . . . . 3-44 GSM900 . . . . . . . . . . . . . . . . . . 3-4
Frequency channel re-use . . . . . . . . . . . . 3-44 UK network operators . . . . . . . . . . . . 3-5
68P02900W21-R IX-3
28 Feb 2006 GMR-01
Index
Fresnel zone . . . . . . . . . . . . . . 3-17 to 3-18 Full Rate speech channel encoding. . . . . . . . 3-58
G
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Gaussian minimum shift keying . . . . . . . 3-6, 3-51 GPRS . . . . . . . . . . . . . . . . . . . . . 1-10

Gb entities . . . . . . . . . . . . . . . . . . . 8-50 air interface planning . . . . . . . . . . . . 3-180
Gb interface . . . . . . . . . . . . . . . . . . 8-3 BSS maximum network parameter values . . . 8-12
Gb link BSS planning . . . . . . . . . . . . . . . . 8-2
PCU to SGSN . . . . . . . . . . . . . . . . 8-55 BSS to PCU planning example . . . . . . . . 8-59
Gb load . . . . . . . . . . . . . . . . . . . . 8-53 BSS upgrade provisioning . . . . . . . . . . 8-11
Gb signalling. . . . . . . . . . . . . . . . . . 8-52 carrier . . . . . . . . . . . . . . . . . . . 3-157
GDP cell planning/deployment influencing
planning . . . . . . . . . . . . . . . . . . . 7-15 factors. . . . . . . . . . . . . . . . . . . 3-180
GDP2 control channel configuration planning . . . 3-126
planning . . . . . . . . . . . . . . . . . . . 7-15 data rates . . . . . . . . . . . . . . . . . 3-203
GDS link dynamic timeslot allocation . . . . . . . . . 3-156
PCU termination . . . . . . . . . . . . . . . 8-6 estimating traffic throughput . . . . . . . . 3-187
Generic clock (GCLK) network planning . . . . . . . . . . . . . 3-152
planning (BSC) . . . . . . . . . . . . . . . 6-91 radio and packet data traffic channels . . . . 3-125
planning (RXU) . . . . . . . . . . . . . . . 7-34 timeslot usage . . . . . . . . . . . . . . . 3-153
GPROC traffic planning . . . . . . . . . . . . . . 3-151
acting as CSFP. . . . . . . . . . . . . . . . 6-67 GPRS RACH arrivals
BSC types . . . . . . . . . . . . . . . . . . 6-63 RSL planning . . . . . . . . . . . . . . . . 6-32
BSP redundancy . . . . . . . . . . . . . . . 6-67 GPRS traffic
nomenclature . . . . . . . . . . . . . 6-61, 7-11 timeslot allocation . . . . . . . . . . . . . 3-179
parameters used to determine requirements. . 6-18, GSL distribution
6-25 algorithm description . . . . . . . . . . . . . 6-58
planning (BSC) . . . . . . . . . . . . . . . 6-64 GSL planning . . . . . . . . . . . . . . . . . 6-55
Signalling message procedures . . . . . 6-18, 6-25 GSM
task groupings and functions . . . . . . . . . 6-61 control channel configuration planning . . . 3-126
GPROC2 . . . . . . . . . . . . . . . . . . . 7-12 GSM half rate . . . . . . . . . . . . . . . . . 3-14
LCF and OMF redundancy . . . . . . . . . . 6-67 basic operation. . . . . . . . . . . . . . . . 4-3
planning (RXCDR) . . . . . . . . . . . . . 7-12 half rate parameter descriptions . . . . . . . . 4-26
GPROC3 interaction with AMR . . . . . . . . . . . . 4-3
planning (BSC) . . . . . . . . . . . . . . . 6-63 new hardware . . . . . . . . . . . . . . . . 4-3
planning (RXCDR) . . . . . . . . . . . . . 7-12 GSM Half Rate
description. . . . . . . . . . . . . . . . . . 1-13
GSN. . . . . . . . . . . . . . . . . . . . . 3-153
H
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Handover HIISC . . . . . . . . . . . . . . . . . . . . . 5-29

2G-3G . . . . . . . . . . . . . . . . . . 3-119 Horizon II macro
Handover and power control cabinet overview . . . . . . . . . . . . . . . 5-4
AMR . . . . . . . . . . . . . . . . . . . . 4-21 connecting to Horizonmacro . . . . . . . . 12-91
Handovers connecting to M-Cell6 . . . . . . . . . . . 12-99
ratio per call . . . . . . . . . . . . . . . . . 11-7 four cabinet configuration . . . . . . . . . 12-19
HDSL RF configuration diagrams . . . . . . . . . 12-24
cable installation . . . . . . . . . . . . . . . 2-27 single cabinet configuration. . . . . . . . . . 12-7
cable selection . . . . . . . . . . . . . . . . 2-26
OMC-R link management . . . . . . . . . . 2-26
IX-4 68P02900W21-R
GMR-01 28 Feb 2006
Index
Horizon II macro (contd.) Horizoncompact and Horizoncompact2

three cabinet configuration . . . . . . . . . 12-14 cabinet overview and differences . . . . . . . 5-5
two cabinet configuration . . . . . . . . . . 12-11 Horizoncompact2
Horizon II macro with PGSM Duplexer RF configuration diagrams . . . . . . . . . 12-82
RF configuration diagrams . . . . . . . . . 12-39 Horizonmacro
Horizon II micro . . . . . . . . . . . . . . . . 5-8 cabinet overview . . . . . . . . . . . . . . . 5-4
RF configuration diagrams . . . . . . . . . 12-61 four cabinet configuration . . . . . . . . . 12-22
single cabinet configuration. . . . . . . . . . 12-9 RF configuration diagrams . . . . . . . . . 12-66
three cabinet configuration . . . . . . . . . 12-16 single cabinet configuration. . . . . . . . . 12-10
Horizon II mini. . . . . . . . . . . . . . . . . 5-7 three cabinet configuration . . . . . . . . . 12-17
four cabinet configuration . . . . . . . . . 12-21 two cabinet configuration . . . . . . . . . . 12-13
RF configuration diagrams . . . . . . . . . 12-49 Horizonmicro and Horizonmicro2
SDH feature . . . . . . . . . . . . . . . . . 5-7 cabinet features and differences . . . . . . . . 5-8
single cabinet configuration. . . . . . . . . . 12-8 Horizonmicro2
three cabinet configuration . . . . . . . . . 12-15 RF configuration diagrams . . . . . . . . . 12-87
two cabinet configuration . . . . . . . . . . 12-12 system configuration . . . . . . . . . . . . . 2-30
hr intra-cell handover support
AMR . . . . . . . . . . . . . . . . . . . . 4-29
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
IMSI detaches Interleaving . . . . . . . . . . . . . . . . . . 3-70

ratio per call . . . . . . . . . . . . . . . . . 11-9 Interoperability
Inner zone utilization threshold GSM half rate with AMR half rate . . . . . . 3-16
AMR . . . . . . . . . . . . . . . . . . . . 4-28 Intra-BSS handovers . . . . . . . . . . . . . . 11-8
Interface modules . . . . . . . . . . . . . . . 5-43 Intra-cell hop count . . . . . . . . . . . . . . . 4-29
J
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Joint Radio Committee (JRC) of the Nationalized Power

Industries . . . . . . . . . . . . . . . . . . . 3-17
K
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
KSW KSWX
planning (BSC) . . . . . . . . . . . . . . . 6-80 planning (BSC) . . . . . . . . . . . . . . . 6-88
planning (RXCDR) . . . . . . . . . . . . . 7-24 planning (RXU) . . . . . . . . . . . . . . . 7-31
KSW switching . . . . . . . . . . . . . . . . 6-74
68P02900W21-R IX-5
28 Feb 2006 GMR-01
Index
L
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
LANX Link adaptation . . . . . . . . . . . . . . . . 3-98

planning (BSC) . . . . . . . . . . . . . . . 6-94 (AMR) . . . . . . . . . . . . . . . . . . . 3-65
planning (RXU) . . . . . . . . . . . . . . . 7-37 Link control function (LCF). . . . . . . . . . . 6-65
Lapse rate . . . . . . . . . . . . . . . . . . . 3-21 LLC_PDU
LCF calculations frame layout . . . . . . . . . . . . . . . . 3-199
for MTL processing . . . . . . . . . . . . . 6-47 LMTL
LCF GPROC calculations planning . . . . . . . . . . . . . . . . . . . 6-49
for GSL processing. . . . . . . . . . . . . . 6-38 Load balancing
for RSL processing. . . . . . . . . . . . . . 6-38 GSL traffic . . . . . . . . . . . . . . . . . 6-57
LCS Location area planning . . . . . . . . . . . . . 10-2
provisioning example. . . . . . . . . . . . . 9-90 Location services (LCS) . . . . . . . . . . . . 1-14
LCS option . . . . . . . . . . . . . . . . . . 6-9 Location update factor . . . . . . . 3-124, 6-17, 11-9
Location updates
ratio per call . . . . . . . . . . . . . . . . . 11-8
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
M-Cell MCUF. . . . . . . . . . . . . . . . . . . . . 5-29

standard configurations . . . . . . . . . . . . 13-2 Micro base control unit (microBCU) . . . . . . . 5-24
M-Cell2 Microcell . . . . . . . . . . . . . . . . . . 3-110
cabinet overview . . . . . . . . . . . . . . . 5-5 system planning . . . . . . . . . . . . . . . 2-30
RF configuration diagrams . . . . . . . . . 13-69 MPROC
single cabinet configuration. . . . . . . . . . 13-4 PCU planning process . . . . . . . . . . . . 8-22
three cabinet configuration . . . . . . . . . . 13-7 MS
M-Cell6 downlink adaptation monitor . . . . . . . . . 4-19
cabinet overview . . . . . . . . . . . . . . . 5-5 MSI / MSI-2
connecting to Horizon II macro . . . . . . . 12-99 planning (BSC) . . . . . . . . . . . . . . . 6-77
four cabinet configuration . . . . . . . . . . 13-8 planning (RXCDR) . . . . . . . . . . . . . 7-21
RF configuration diagrams . . . . . . . . . 13-10 MSI-2
single cabinet configuration. . . . . . . . . . 13-3 T1 to E1 conversion . . . . . . . . . . . . . 6-74
two cabinet configuration . . . . . . . . . . . 13-5 MTL
two cabinet configuration with CTU2 planning . . . . . . . . . . . . . . . . . . . 6-42
Adapter . . . . . . . . . . . . . . . . . . . 13-6 MTL calculations
M-Cellaccess non-standard traffic model . . . . . . . . . . 6-46
PCC cabinet equipage . . . . . . . . . . . . 5-2 standard traffic model . . . . . . . . . . . . 6-43
Macrocell . . . . . . . . . . . . . . . . . . 3-110 Multipath fading . . . . . . . . . . . . . . . 3-101
MCU . . . . . . . . . . . . . . . . . . . . . 5-29 Multiplexing . . . . . . . . . . . . . . . . . . 2-11
N
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Network interface unit (NIU) . . . . . . . . . . 5-25 Network topology (contd.)

Network planning exercises interface restrictions . . . . . . . . . . . . . 2-6
initial requirements. . . . . . . . . . . . . . 9-2 NVM board
Network topology planning (BSC) . . . . . . . . . . . . . . . 6-99
BTS site restrictions . . . . . . . . . . . . . 2-6 planning (RXCDR) . . . . . . . . . . . . . 7-42
IX-6 68P02900W21-R
GMR-01 28 Feb 2006
Index
O
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
One phase access (contd.) One phase access (contd.)

Okumura . . . . . . . . . . . . . . . . . . . 3-38 RSL planning . . . . . . . . . . . . . 6-24, 6-29
OMC-R Output power
HDSL link management . . . . . . . . . . . 2-26 mobile handset. . . . . . . . . . . . . . . 3-104
OMF . . . . . . . . . . . . . . . . . . . . . 6-66
One phase access
GSL planning . . . . . . . . . . . . . . . . 6-56
P
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Pages per call . . . . . . . . . . . . . . . . 11-11 PCU shelf (cPCI)

Paging rate. . . . . . . . . . . . . . . . . . 11-10 planning . . . . . . . . . . . . . . . . . . . 8-21
location area planning . . . . . . . . . . . . 10-2 PDTCH planning . . . . . . . . . . . . . . . . 8-25
PCCCH calculations . . . . . . . . . . 3-129, 3-137 PICP board
PCCCH timeslot planning . . . . . . . . . . . . . . . . . . . 8-23
user data capacity . . . . . . . . . . . . . 3-142 PIX
PCU . . . . . . . . . . . . . . . . . . . . . . 1-10 planning (BSC) . . . . . . . . . . . . . . . 6-95
device alarms . . . . . . . . . . . . . . . . 8-4 planning (RXU) . . . . . . . . . . . . . . . 7-38
frame relay interface parameters . . . . . . . 8-55 PMC module
hardware layout diagram . . . . . . . . . . . 8-18 planning . . . . . . . . . . . . . . . . . . . 8-27
interface to SGSN . . . . . . . . . . . . . . 8-3 Power supply
link diagram for EGPRS . . . . . . . . . . . 8-68 BTS requirements . . . . . . . . . . . . . . 5-39
link diagram for GPRS . . . . . . . . . . . . 8-58 CTU and CTU2 considerations . . . . . . . . 5-20
multiple PCUs . . . . . . . . . . . . . . . . 8-38 Preventive cyclic retransmission . . . . . . . . . 6-48
provisioning goals . . . . . . . . . . . . 8-35, 8-2 Propagation losses . . . . . . . . . . . . . . . 3-17
redundancy planning . . . . . . . . . . . . . 8-30 PRP board
upgrading . . . . . . . . . . . . . . . . . . 8-36 planning factors . . . . . . . . . . . . . . . 8-24
PCU planning PRP planning . . . . . . . . . . . . . . . . . 8-24
DPROC board . . . . . . . . . . . . . . . . 8-23
MPROC board . . . . . . . . . . . . . . . . 8-22
Q
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Quality of service
AMR . . . . . . . . . . . . . . . . . . . . 3-11
R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Radio Sonds . . . . . . . . . . . . . . . . . . 3-21 Radio wave propagation (contd.)

Radio wave propagation power budget and system balance . . . . . . . 3-41
antenna gain . . . . . . . . . . . . . . . . . 3-35 Rayleigh environment . . . . . . . . . . . . 3-28
clutter factor . . . . . . . . . . . . . . . . . 3-34 Rician environment . . . . . . . . . . . . . 3-29
DCS1800 path loss . . . . . . . . . . . . . . 3-43 within buildings . . . . . . . . . . . . . . . 3-37
environmental effects. . . . . . . . . . . . . 3-23 Rate adaptation
free space loss . . . . . . . . . . . . . . . . 3-30 AMR . . . . . . . . . . . . . . . . . . . . 4-17
GSM900 path loss . . . . . . . . . . . . . . 3-42 Receive configurations
plane earth loss . . . . . . . . . . . . . . . 3-31 M-Cell, Horizonmacro and Horizon II mini . . 5-9
68P02900W21-R IX-7
28 Feb 2006 GMR-01
Index
Receive diversity . . . . . . . . . . . . . . . 3-101 RSL (contd.)

Refractometers . . . . . . . . . . . . . . . . . 3-21 planning calculations
Reserved timeslots signalling link provisioning. . . . . . . . . 6-24
AMR . . . . . . . . . . . . . . . . . . . . 4-28 planning constraints . . . . . . . . . . . . . 2-22
RF carriers RSL calculations
limitations . . . . . . . . . . . . . . . . . . 3-6 non-standard traffic model . . . . . . . . . . 6-29
RF configuration diagrams standard traffic model . . . . . . . . . . . . 6-25
Horizon II macro. . . . . . . . . . . . . . 12-24 RTF
Horizon II macro with PGSM Duplexer . . . 12-39 types . . . . . . . . . . . . . . . . . 2-19, 2-96
Horizon II micro . . . . . . . . . . . . . . 12-61 RTF path
Horizon II mini . . . . . . . . . . . . . . 12-49 fault containment . . . . . . . . . . . . 2-16, 8-7
Horizoncompact2 . . . . . . . . . . . . . 12-82 RXCDR
Horizonmacro . . . . . . . . . . . . . . . 12-66 as E1 switching interface (PCU to SGSN) . . . 8-3
Horizonmicro2. . . . . . . . . . . . . . . 12-87 equipage planning . . . . . . . . . . . . . . 7-2
M-Cell2 . . . . . . . . . . . . . . . . . . 13-69 links to BSC/MSC . . . . . . . . . . . . . . 6-69
M-Cell6 . . . . . . . . . . . . . . . . . . 13-10 planning steps . . . . . . . . . . . . . . . . 7-3
mixed cabinets . . . . . . . . . . . . . . . 12-92 system capacity . . . . . . . . . . . . . . . 7-4
RRI measurements . . . . . . . . . . . . . . . 3-20 RXU shelf
RSL . . . . . . . . . . . . . . . . . . . . . . 2-18 planning . . . . . . . . . . . . . . . . . . . 7-28
planning . . . . . . . . . . . . . . . . . . . 6-22 RXU3 . . . . . . . . . . . . . . . . . . . . . 4-34
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
SACCH multiframe SMS (contd.)

Full Rate . . . . . . . . . . . . . . . . . . 3-99 ratio per call . . . . . . . . . . . . . . . . . 11-6
Half Rate . . . . . . . . . . . . . . . . . 3-100 Software planning tools . . . . . . . . . . . . . 3-3
Satellite link speech quality
MSC to BSC signalling. . . . . . . . . . . . 6-48 AMR . . . . . . . . . . . . . . . . . . . . 4-6
SDCCH calculations . . . . . . . . . . . . . 3-143 GSM half rate . . . . . . . . . . . . . . . . 4-12
Seamless cell reselection State models
GPRS . . . . . . . . . . . . . . . . . . . . 8-7 MS and SGSN . . . . . . . . . . . . . . . 3-155
SGSN . . . . . . . . . . . . . . . . . . . . . 8-3 Switchable timeslots
Short message service . . . . . . . . . . . . . 1-10 provisioning . . . . . . . . . . . . . . . . 3-173
Signalling link capacities Synthesizer hopping . . . . . . . . 1-9, 3-52, 3-113
BSC. . . . . . . . . . . . . . . . . . . . . 6-11 System capacity
Signalling message sequence . . . . . . . . . . 6-18 RXCDR . . . . . . . . . . . . . . . . . . . 7-4
Site expansion board . . . . . . . . . . . . . . 5-32 System dimensioning
SMS Erlang B model . . . . . . . . . . . . . . . 3-8
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
T1 link calculations. . . . . . . . . . . . . . . 6-76 TCP/IP . . . . . . . . . . . . . . . . . . . 3-199

BSC to RXCDR . . . . . . . . . . . . . . . 7-8 TDMA frame structure . . . . . . . . . . . . . 3-70
RXCDR to MSC . . . . . . . . . . . . . . . 7-10 Timeslot
T1 to E1 conversion . . . . . . . . . . . . . . 6-74 allocation algorithms . . . . . . . . . . . . . 2-13
for the XCDR . . . . . . . . . . . . . . . . 7-18 Timeslot allocation
T43 dynamic (GPRS/EGPRS) . . . . . . . . . . 3-156
planning (BSC) . . . . . . . . . . . . . . . 6-96 GPRS traffic . . . . . . . . . . . . . . . . 3-179
planning (RXCDR) . . . . . . . . . . . . . 7-39 Timeslot provisioning
TCH to SDCCH conversion . . . . . . . . . . . 8-7 GPRS/EGPRS . . . . . . . . . . . . . . . 3-190
IX-8 68P02900W21-R
GMR-01 28 Feb 2006
Index
Timeslot usage Transcoder

AMR . . . . . . . . . . . . . . . . . . . . 4-16 BSSC cabinet hardware diagram . . . . . . . 12-6
Timeslots . . . . . . . . . . . . . . . . . . 3-192 Transcoding
contiguous. . . . . . . . . . . . . . . . . 3-172 at the BSC . . . . . . . . . . . . . . . . . . 6-75
stolen . . . . . . . . . . . . . . . . . . . 3-171 EGDP provisioning . . . . . . . . . . 6-72, 7-16
switchable and reserved (GPRS/EGPRS) . . 3-157 GDP/XCDR/EGDP/GDP2 planning
switchable utilization (GPRS/EGPRS) . . . . 3-177 considerations . . . . . . . . . . . . . . . . 6-71
Traffic flow . . . . . . . . . . . . . . . . . . 3-9 Transition module
Traffic model and capacity calculations . . . . . 1-19 planning . . . . . . . . . . . . . . . . . . . 8-29
traffic throughput. . . . . . . . . . . . . . . 3-187 Transmit configurations
Training sequence code . . . . . . . . . . . . 3-103 M-Cell, Horizonmacro and Horizon II mini . . 5-13
Tranceiver TRAU
CTU and CTU2 . . . . . . . . . . . . . . . 5-19 16 kbit/s . . . . . . . . . . . . . . . . . . . 3-85
Transceiver 32 kbit/s . . . . . . . . . . . . . . . . . . . 3-85
types . . . . . . . . . . . . . . . . . . . . 1-6 64 kbit/s . . . . . . . . . . . . . . . . . . . 3-97
U
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
UMTS . . . . . . . . . . . . . . . . . . . . 3-119
V
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Voice activity detection . . . . . . . . . . . . . 3-98
X
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
XBL. . . . . . . . . . . . . . . . . . . . . . 2-22 XCDR (contd.)

planning . . . . . . . . . . . . . . . . . . . 6-52 sub-multiplexing and speech transcoding . . . 7-13
XCDR T1 to E1 conversion . . . . . . . . . . . . . 7-18
planning . . . . . . . . . . . . . . . . . . . 7-15 XMUX . . . . . . . . . . . . . . . . . . . . 5-32
68P02900W21-R IX-9
28 Feb 2006 GMR-01

BTS Planning Steps and Rules

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BTS Planning Steps and Rules

Uploaded by

Copyright:

Available Formats

SYSTEM INFORMATION

BSS EQUIPMENT PLANNING

© 1993 - 2006 Motorola, Inc. 68P02900W21-R

GMR-01 28 Feb 2006

System Information: BSS Equipment Planning

Chapter 2: Transmission systems

Chapter 3: BSS cell planning

GSM frequency spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

16/32 kbit/s TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

Chapter 4: AMR and {22064} GSM planning

Chapter 5: BTS planning steps and rules

Receiver planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

DRI/Combiner operability components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

Chapter 6: BSC planning steps and rules

GPROC nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61

Chapter 7: RXCDR planning steps and rules

Chapter 8: PCU upgrade for the BSS

PCU equipment redundancy and provisioning goals . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Chapter 9: Planning exercises

GPROC requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Chapter 10: Location area planning

Chapter 11: Deriving call model parameters from network statistics

Chapter 12: Standard BSS and Horizon BTS configurations

Two cabinet Horizon II mini BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

[GSM900/DCS1800] Horizonmicro2 single BTS system . . . . . . . . . . . . . . . . . . . . . . . 12-88

Chapter 13: M-Cell BTS configurations

Figure 1-1: BSS block diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Figure 3-23: Measurement of gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Figure 3-77: CCCH and PCCCH decision tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

Figure 13-3: Two cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

This page intentionally left blank.

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 7-3: KSWX/DSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

This page intentionally left blank.

System Information: BSS Equipment

What is Covered In This Manual?

Issue status of this manual

Table 1 Manual version history

A 30 Dec 1994 Issue A - Software Release 1.2.3.x

Resolution of service requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

The following CDCNs are now incorporated in this manual:

Failure to comply with Motorola’s operation, installation and maintenance

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

The tags are positioned in text as follows:

New and amended feature information Tag position in text

Special key sequences

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

Reporting safety issues

Safety issue reporting procedure

Procedure 1 Safety issue reporting

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

Warnings and cautions

A definition and example follow below:

Example and format

Failure to comply with warnings

A definition and example follow below:

Example and format

• Potentially hazardous voltage.

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.