68P02900W21

SYSTEM INFORMATION
BSS EQUIPMENT PLANNING

GSM SOFTWARE RELEASE 8.0
GSR8.0
GMR- 01
68P02900W21-R
SYSTEM INFORMATION
BSS EQUIPMENT PLANNING
GSM SOFTWARE RELEASE 8.0
GMR-01
GSR8.0
68P02900W21-R
System Information: BSS Equipment

Planning
68P02900W21-R
Nov 2007
GMR-01
1993-2007 Motorola, Inc.
All Rights Reserved
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. 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, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modied 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 or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted 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, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Trafc Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specically disclaim any expressed or implied warranty of tness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Ofce. All other product or service
names are the property of their respective owners.
The CE mark conrms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Ofce.
GMR-01
Nov 2007
Table
of
Contents
Contents
System Information: BSS Equipment Planning

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
3
4
4
4
5
6
6
6
6
7
8
8
8
8
9
9
9
10
10
10
11
12
12
12
12
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
Broadcast (SMS CB)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-2
1-4
1-4
1-5
1-8
1-8
1-8
1-9
1-9
Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
In EU countries . . . . . . . . . .
In non-EU countries . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner denitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: Introduction to planning

Manual overview . . . . . . . .
Introduction . . . . . . . .
Contents . . . . . . . . . .
BSS equipment overview. . . .
System architecture . . . .
System components . . . .
BSS features . . . . . . . . . .
Planning impacts. . . . . .
Diversity . . . . . . . . . .
Frequency hopping . . . .
Short Message Service, Cell
68P02900W21-R
Nov 2007
GMR-01
Contents
Code Storage Facility Processor (CSFP)

PCU for GPRS upgrade . . . . . . . .
Enhanced-GPRS (EGPRS) . . . . . . .
Adaptive Multi-Rate (AMR) . . . . . .
GSM half rate . . . . . . . . . . . . .
LoCation Services (LCS) . . . . . . . .
BSC Reset Management (BRM) . . . .
Advanced Speech Call Item (ASCI). . .
VersaTRAU backhaul for EGPRS . . . .
Quality of Service (QoS) . . . . . . . .
Improved Timeslot Sharing (ITS) . . .
BSS planning overview. . . . . . . . . . .
Introduction . . . . . . . . . . . . . .
Background information . . . . . . . .
Planning methodology . . . . . . . . .
Acronyms . . . . . . . . . . . . . . . . .
Acronym list . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-10
1-10
1-10
1-11
1-12
1-13
1-14
1-14
1-15
1-15
1-17
1-18
1-18
1-18
1-20
1-21
1-21
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
(DARBC)
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-4
2-4
2-4
2-6
2-6
2-7
2-8
2-9
2-12
2-16
2-18
2-21
2-22
2-25
2-25
2-25
2-27
2-28
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-3
3-3
3-4
3-4
3-4
3-5
3-6
3-8
3-8
3-8
3-9
3-9
3-10
3-10
3-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 2: Transmission systems

BSS interfaces . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
Interconnecting the BSC and BTSs . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
Interconnection rules . . . . . . . . . . . .
Network topology . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
Star connection . . . . . . . . . . . . . . .
Daisy chain connection . . . . . . . . . . .
Daisy chain planning . . . . . . . . . . . . .
Aggregate Abis. . . . . . . . . . . . . . . .
RTF path fault containment . . . . . . . . .
16 kbit/s RSL. . . . . . . . . . . . . . . . .
16 kbit/s XBL . . . . . . . . . . . . . . . .
Dynamic allocation of RXCDR to BSC circuits
Managed HDSL on micro BTSs . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
Integrated HDSL interface . . . . . . . . . .
General HDSL guidelines . . . . . . . . . .
Microcell system planning . . . . . . . . . .
Chapter 3: BSS cell planning

Planning tools . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
GSM frequency spectrum . . . . . . . . . . . .
GSM900 frequency spectrum . . . . . . . .
DCS1800 frequency spectrum . . . . . . . .
Absolute radio frequency channel capacity .
Modulation techniques and channel spacing .
Trafc capacity . . . . . . . . . . . . . . . . .
Dimensioning . . . . . . . . . . . . . . . .
Channel blocking . . . . . . . . . . . . . .
Trafc ow. . . . . . . . . . . . . . . . . .
Grade of service . . . . . . . . . . . . . . .
Adaptive multi-rate (AMR) . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . .
Capacity and coverage . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
Contents
Quality of service . . . . . . . . . . . . . . . . . . .
Applications . . . . . . . . . . . . . . . . . . . . . .
Migration to AMR half rate . . . . . . . . . . . . . .
Interoperability with GSM half rate . . . . . . . . . .
Interoperability with EGPRS . . . . . . . . . . . . . .
GSM half rate . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Capacity and coverage . . . . . . . . . . . . . . . . .
Quality of service . . . . . . . . . . . . . . . . . . .
Applications . . . . . . . . . . . . . . . . . . . . . .
Migration to half rate . . . . . . . . . . . . . . . . .
Interoperability with AMR half rate . . . . . . . . . .
Interoperability with EGPRS . . . . . . . . . . . . . .
Propagation effects on GSM frequencies. . . . . . . . . .
Propagation production . . . . . . . . . . . . . . . .
Decibels . . . . . . . . . . . . . . . . . . . . . . . .
Fresnel zone . . . . . . . . . . . . . . . . . . . . . .
Radio refractive index (RRI) . . . . . . . . . . . . . .
Environmental effects on propagation . . . . . . . . .
Attenuation . . . . . . . . . . . . . . . . . . . . . .
Multipath propagation . . . . . . . . . . . . . . . . .
GSM900 path loss . . . . . . . . . . . . . . . . . . .
Path loss GSM900 against DCS1800 . . . . . . . . . .
Frequency re-use . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Re-use pattern . . . . . . . . . . . . . . . . . . . . .
Carrier/Interference (C/I) ratio . . . . . . . . . . . .
Sources of interference . . . . . . . . . . . . . . . .
Sectorization of sites. . . . . . . . . . . . . . . . . .
Overcoming adverse propagation effects . . . . . . . . .
Hardware techniques . . . . . . . . . . . . . . . . .
Error protection and detection. . . . . . . . . . . . .
GSM speech channel encoding for full rate . . . . . .
GSM speech channel encoding for enhanced full rate .
GSM speech channel encoding for half rate . . . . . .
GSM speech channel encoding for AMR full rate . . .
GSM speech channel encoding for AMR half rate . . .
Link adaptation for AMR channels . . . . . . . . . . .
GSM control channel encoding . . . . . . . . . . . .
GSM circuit-switched data channel encoding . . . . .
Mapping logical channels in the TDMA frame structure
GPRS channel coding schemes. . . . . . . . . . . . .
16/32 kbit/s TRAU . . . . . . . . . . . . . . . . . . .
EGPRS channel coding schemes . . . . . . . . . . . .
64 kbit/s TRAU for EGPRS . . . . . . . . . . . . . . .
Link adaptation (LA) in GPRS/EGPRS . . . . . . . . .
Voice activity detection (VAD) . . . . . . . . . . . . .
Discontinuous transmission (DTX) . . . . . . . . . . .
Receive diversity . . . . . . . . . . . . . . . . . . . .
Subscriber environment . . . . . . . . . . . . . . . . . .
Subscriber hardware. . . . . . . . . . . . . . . . . .
Environment . . . . . . . . . . . . . . . . . . . . . .
Distribution . . . . . . . . . . . . . . . . . . . . . .
Hand portable subscribers . . . . . . . . . . . . . . .
Future planning . . . . . . . . . . . . . . . . . . . .
Microcellular solution . . . . . . . . . . . . . . . . . . .
Layered architecture. . . . . . . . . . . . . . . . . .
Combined cell architecture . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-11
3-12
3-13
3-13
3-13
3-14
3-14
3-14
3-15
3-15
3-16
3-16
3-16
3-17
3-17
3-17
3-19
3-20
3-23
3-24
3-27
3-40
3-42
3-43
3-43
3-44
3-46
3-47
3-48
3-49
3-49
3-50
3-56
3-58
3-59
3-60
3-62
3-64
3-65
3-66
3-68
3-75
3-81
3-82
3-92
3-93
3-93
3-94
3-96
3-99
3-99
3-99
3-100
3-101
3-102
3-103
3-103
3-104
iii
GMR-01
Contents
Combined cell architecture structure . . . . . . . . . . . . . . .

Expansion solution . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rules for Synthesizer Frequency Hopping (SFH) . . . . . . . . .
Rules for BaseBand Hopping (BBH) . . . . . . . . . . . . . . . .
Inter-radio access technology (2G-3G) cell reselection and handovers .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2G-3G handover description . . . . . . . . . . . . . . . . . . . .
Impact of 2G-3G handovers on GSM system architecture . . . . .
System consideration . . . . . . . . . . . . . . . . . . . . . . .
Call model parameters for capacity calculations . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical call parameters . . . . . . . . . . . . . . . . . . . . . .
Control channel calculations . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations . . . . . . . . . . . . . . . . . . . . . .
Number of CCCHs and PCCCHs per BTS cell . . . . . . . . . . .
Number of PCCCHs per BTS cell . . . . . . . . . . . . . . . . .
User data capacity on the PCCCH timeslot . . . . . . . . . . . .
Number of SDCCHs per BTS cell . . . . . . . . . . . . . . . . .
Control channel congurations . . . . . . . . . . . . . . . . . .
GPRS/EGPRS trafc planning . . . . . . . . . . . . . . . . . . . . .
Determination of expected load . . . . . . . . . . . . . . . . . .
Network planning ow . . . . . . . . . . . . . . . . . . . . . . .
GPRS/EGPRS network trafc estimation and key concepts . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic timeslot allocation . . . . . . . . . . . . . . . . . . . .
Carrier timeslot allocation examples . . . . . . . . . . . . . . . .
BSS timeslot allocation methods . . . . . . . . . . . . . . . . . .
Provisioning the network with switchable timeslots . . . . . . . .
Recommendation for switchable timeslot usage . . . . . . . . . .
Timeslot allocation process on carriers with GPRS trafc . . . . .
GPRS/EGPRS air interface planning process . . . . . . . . . . . . . .
Inuential factors in GPRS/EGPRS cell planning and deployment .
Estimating the air interface trafc throughput. . . . . . . . . . .
Select a cell plan . . . . . . . . . . . . . . . . . . . . . . . . . .
Estimating timeslot provisioning requirements . . . . . . . . . .
Optimum le size calculation . . . . . . . . . . . . . . . . . . .
File transit times calculations . . . . . . . . . . . . . . . . . . .
Congurable initial coding scheme . . . . . . . . . . . . . . . .
GPRS/EGPRS data rates . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-104
3-106
3-107
3-107
3-107
3-111
3-113
3-113
3-113
3-114
3-115
3-116
3-116
3-116
3-119
3-119
3-120
3-122
3-129
3-132
3-133
3-136
3-140
3-140
3-140
3-141
3-141
3-143
3-147
3-155
3-157
3-161
3-162
3-163
3-163
3-170
3-170
3-172
3-179
3-180
3-182
3-182
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-2
4-2
4-3
4-3
4-3
4-4
4-5
4-5
4-5
4-10
4-11
4-11
Chapter 4: AMR and {22064} GSM planning

Introduction . . . . . . . . . . . . . . . . . . . . . .
AMR basic operation . . . . . . . . . . . . . . . .
{22064} GSM half rate basic operation . . . . . .
AMR and {22064} GSM half rate interaction . . .
New hardware . . . . . . . . . . . . . . . . . . .
Inuencing factors . . . . . . . . . . . . . . . . .
Planning . . . . . . . . . . . . . . . . . . . . . .
Quality and capacity . . . . . . . . . . . . . . . . . .
Benets of AMR . . . . . . . . . . . . . . . . . .
AMR Full Rate and AMR Half Rate speech quality .
AMR voice quality improvement and coverage . . .
{22064} Benets of GSM half rate . . . . . . . .
GSM Half Rate speech quality . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-11
4-15
4-16
4-16
4-16
4-17
4-18
4-19
4-19
4-19
4-21
4-21
4-21
4-22
4-22
4-22
4-26
4-29
4-29
4-31
4-36
BTS planning overview. . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . .
Outline of planning steps . . . . . . . . . . . . . . .
Macrocell cabinets . . . . . . . . . . . . . . . . . . . . .
Horizon II macr . . . . . . . . . . . . . . . . . . . .
Horizonmacro . . . . . . . . . . . . . . . . . . . . .
Horizoncompact and Horizoncompact2 . . . . . . . .
M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . .
M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . .
Microcell enclosures . . . . . . . . . . . . . . . . . . . .
Horizon II mini . . . . . . . . . . . . . . . . . . . . .
Horizonmicro and Horizonmicro2 . . . . . . . . . . .
Horizon II micro . . . . . . . . . . . . . . . . . . . .
Receive congurations . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Planning considerations . . . . . . . . . . . . . . . .
Transmit congurations . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Transmit planning actions . . . . . . . . . . . . . . .
EGPRS enabled CTU2 conguration . . . . . . . . . . . .
EGPRS enabled CTU2 conguration limitations . . . .
EGPRS general conguration . . . . . . . . . . . . .
BaseBand Hopping (BBH) . . . . . . . . . . . . . . .
Broadcast Control CHannel (BCCH) RTF conguration
Antenna congurations . . . . . . . . . . . . . . . . . .
Antenna planning actions . . . . . . . . . . . . . . .
Carrier equipment (transceiver unit). . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Restrictions in CTU2s usage in Horizonmacro BTSs . .
CTU/CTU2 power supply considerations . . . . . . . .
Transceiver planning actions . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-3
5-4
5-4
5-4
5-5
5-5
5-5
5-7
5-7
5-8
5-8
5-9
5-9
5-9
5-12
5-12
5-12
5-13
5-14
5-14
5-14
5-14
5-15
5-16
5-16
5-16
5-17
5-17
5-17
5-18
5-20
5-20
Capacity increase due to half rate usage .

Timeslot usage . . . . . . . . . . . . . .
Rate adaptation . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . .
Codec modes. . . . . . . . . . . . . . .
Thresholds and hystereses . . . . . . . .
Downlink adaptation MS monitor . . . .
Handover and power control . . . . . . . . .
Introduction . . . . . . . . . . . . . . .
Handover and power control thresholds .
Miscellaneous information . . . . . . . . . .
Emergency call handling . . . . . . . . .
Circuit pooling . . . . . . . . . . . . . .
Half rate utilization . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . .
Parameter descriptions . . . . . . . . .
Operational aspects . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . . . . .
Equipment descriptions . . . . . . . . .
Backhaul . . . . . . . . . . . . . . . . .
Summary. . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 5: BTS planning steps and rules
68P02900W21-R
Nov 2007
GMR-01
Contents
Micro base control unit (microBCU) . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . .
MicroBCU planning actions . . . . . . . . . . . . . . . . . . . . . . .
Network interface unit (NIU) and site connection . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NIU planning actions . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS main control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations Horizon II macro/Horizon II mini as expansion
Planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabinet interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horizon II mini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations - Horizon II macro as master cabinet . . . . . .
Planning considerations - Horizon II mini as master cabinet . . . . . . .
XMUX/FMUX/FOX planning actions . . . . . . . . . . . . . . . . . . .
Site expansion board planning actions (Horizon II macro only) . . . . .
Battery back-up provisioning. . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External power requirements . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power planning actions . . . . . . . . . . . . . . . . . . . . . . . . .
Network expansion using macro/microcell BTSs . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expansion considerations . . . . . . . . . . . . . . . . . . . . . . . .
Mixed site utilization. . . . . . . . . . . . . . . . . . . . . . . . . . .
Line interface modules (HIM-75, HIM-120) . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HIM-75/HIM-120 planning actions . . . . . . . . . . . . . . . . . . . .
DRI/Combiner operability components . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRI and combiner relationship. . . . . . . . . . . . . . . . . . . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
cabinet
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-21
5-21
5-21
5-21
5-22
5-22
5-22
5-24
5-25
5-25
5-25
5-26
5-27
5-28
5-28
5-29
5-29
5-31
5-32
5-32
5-32
5-33
5-33
5-33
5-34
5-34
5-34
5-35
5-36
5-36
5-36
5-36
5-37
5-37
5-37
5-37
5-38
5-38
5-38
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-3
6-3
6-3
6-4
6-6
6-6
6-6
6-7
6-7
6-8
6-9
6-9
6-10
6-10
6-13
6-16
Chapter 6: BSC planning steps and rules

BSC planning overview . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Mixing of equipment types . . . . . . . . . . . . .
Outline of planning . . . . . . . . . . . . . . . .
Capacity calculations . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Remote transcoding . . . . . . . . . . . . . . . .
BSC system capacity . . . . . . . . . . . . . . . . . .
System capacity summary . . . . . . . . . . . . .
Scaleable BSC . . . . . . . . . . . . . . . . . . .
Enhanced BSC capacity option. . . . . . . . . . .
LCS option . . . . . . . . . . . . . . . . . . . . .
Determining the required BSS signaling link capacities
BSC signaling trafc model . . . . . . . . . . . .
Typical parameter values . . . . . . . . . . . . .
Assumptions used in capacity calculations . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
Contents
Link capacities . . . . . . . . . . . . . . . . . . . . . . .
Determining the number of RSLs required . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations . . . . . . . . . . . . . . . . . .
Determining the number of RSLs . . . . . . . . . . . . .
One phase access and enhanced one phase . . . . . . . .
Standard trafc model . . . . . . . . . . . . . . . . . . .
Non-standard trafc model . . . . . . . . . . . . . . . .
With enhanced one phase access . . . . . . . . . . . . .
BSC to BTS E1 interconnect planning actions . . . . . . .
BSC to BTS E1 interconnect planning example . . . . . .
Determining the number of LCF GPROCs for RSL and GSL
Determining the number of MTLs required . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Non-standard trafc model . . . . . . . . . . . . . . . .
Calculate the number of LCFs for MTL processing. . . . .
LCFs for 64 k MTL links . . . . . . . . . . . . . . . . . .
MSC to BSC signaling over a satellite link . . . . . . . . .
Determining the number of LMTLs required . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Determining the number of LMTLs . . . . . . . . . . . .
BSC to SMLC interconnection planning actions . . . . . .
Calculate the number of LCFs for LMTL processing . . . .
Determining the number of XBLs required. . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Determining the number of XBLs . . . . . . . . . . . . .
Non standard trafc model . . . . . . . . . . . . . . . .
Determining the number of GSLs required. . . . . . . . . . .
With one phase access . . . . . . . . . . . . . . . . . . .
With enhanced one phase access . . . . . . . . . . . . .
Load balancing. . . . . . . . . . . . . . . . . . . . . . .
Generic processor (GPROC) . . . . . . . . . . . . . . . . . .
GPROC nomenclature . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
GPROC functions and types . . . . . . . . . . . . . . . .
GPROC3 planning assumptions . . . . . . . . . . . . . .
BSC types . . . . . . . . . . . . . . . . . . . . . . . . .
Cell broadcast link . . . . . . . . . . . . . . . . . . . . .
OMF GPROC required . . . . . . . . . . . . . . . . . . .
Code storage facility processor . . . . . . . . . . . . . .
GPROC redundancy . . . . . . . . . . . . . . . . . . . .
GPROC planning actions . . . . . . . . . . . . . . . . . .
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . .
GDP/XCDR/EGDP/GDP2 planning considerations . . . . .
EGDP provisioning . . . . . . . . . . . . . . . . . . . . .
T1 conversion . . . . . . . . . . . . . . . . . . . . . . .
Planning actions for transcoding at the BSC . . . . . . . .
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
MSI/MSI-2 planning actions . . . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
processing
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-18
6-20
6-20
6-20
6-21
6-21
6-22
6-26
6-27
6-30
6-31
6-32
6-35
6-35
6-35
6-36
6-38
6-40
6-40
6-41
6-42
6-42
6-42
6-42
6-43
6-43
6-44
6-44
6-44
6-44
6-45
6-45
6-47
6-47
6-47
6-48
6-49
6-52
6-52
6-52
6-52
6-54
6-54
6-55
6-56
6-57
6-57
6-57
6-58
6-59
6-60
6-61
6-63
6-64
6-66
6-66
6-66
6-66
vii
GMR-01
Contents
Kiloport switch (KSW) and double kiloport switch (DSW2) . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . .
KSW/DSW2 planning actions. . . . . . . . . . . . . . . . . . . . . . . .
BSU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . .
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX)
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KSWX/DSWX planning actions . . . . . . . . . . . . . . . . . . . . . . .
Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GCLK planning actions. . . . . . . . . . . . . . . . . . . . . . . . . . .
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local area network extender (LANX) . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LANX planning actions. . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line interface boards (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . .
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . .
Non Volatile Memory (NVM) board . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the number of BSU shelves and BSSC cabinets . . . . . . . . . . .
Verication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-68
6-68
6-68
6-70
6-71
6-71
6-71
6-71
6-74
6-74
6-74
6-75
6-77
6-77
6-77
6-77
6-78
6-78
6-78
6-79
6-80
6-80
6-80
6-80
6-81
6-81
6-81
6-81
6-82
6-82
6-82
6-83
6-84
6-84
6-84
6-84
6-85
6-85
6-85
6-85
6-86
6-86
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-2
7-2
7-4
7-4
7-5
7-5
7-5
7-6
7-6
7-7
7-8
7-9
Chapter 7: RXCDR planning steps and rules

Overview of remote transcoder planning.
Introduction . . . . . . . . . . . . .
Outline of planning steps . . . . . .
RXCDR system capacity . . . . . . . . .
System capacity summary . . . . . .
RXCDR to BSC connectivity . . . . . . .
Introduction . . . . . . . . . . . . .
Capacity . . . . . . . . . . . . . . .
RXCDR to BSC links . . . . . . . . . . .
Introduction . . . . . . . . . . . . .
E1 interconnect planning actions . .
T1 interconnect planning actions . .
RXCDR to MSC links . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . .
T1 interconnect planning actions . . . . . . . . . . . . . . . . . . . . .
Generic processor (GPROC) . . . . . . . . . . . . . . . . . . . . . . . . . .
GPROC nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
XCDR/GDP/EGDP/GDP2 planning considerations . . . . . . . . . . . . .
EGDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning actions for transcoding at the RXCDR . . . . . . . . . . . . . .
Multiple serial interface (MSI, MSI-2) . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSI planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . .
Kiloport switch (KSW) and double kiloport switch (DSW2) . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KSW/DSW2 planning actions. . . . . . . . . . . . . . . . . . . . . . . .
RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXU shelf planning actions . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KSWX/DSWX planning actions . . . . . . . . . . . . . . . . . . . . . . .
Generic clock (GCLK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GCLK planning actions. . . . . . . . . . . . . . . . . . . . . . . . . . .
Clock extender (CLKX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLKX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN extender (LANX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LANX planning actions. . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel interface extender (PIX) . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PIX planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line interfaces (BIB, T43) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BIB/T43 planning actions . . . . . . . . . . . . . . . . . . . . . . . . .
Digital shelf power supply . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power supply planning actions . . . . . . . . . . . . . . . . . . . . . . .
Non Volatile Memory (NVM) board . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NVM planning actions . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify the number of RXU shelves and BSSC cabinets . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-9
7-9
7-9
7-10
7-10
7-10
7-10
7-11
7-11
7-13
7-14
7-16
7-17
7-19
7-19
7-19
7-20
7-21
7-21
7-21
7-22
7-24
7-24
7-24
7-25
7-27
7-27
7-27
7-28
7-30
7-30
7-30
7-30
7-31
7-31
7-31
7-32
7-33
7-33
7-33
7-33
7-34
7-34
7-34
7-34
7-35
7-35
7-35
7-36
7-37
7-37
7-37
7-37
7-38
7-38
7-38
7-38
7-39
ix
GMR-01
Contents
Verication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-39
Chapter 8: PCU upgrade for BSS

BSS planning for GPRS/EGPRS . . . . . . . . . . . . . . . .
Introduction to BSS planning for GPRS/EGPRS . . . . . .
PCU to SGSN interface planning . . . . . . . . . . . . .
Feature compatibility . . . . . . . . . . . . . . . . . . .
BSS upgrade to support GPRS/EGPRS . . . . . . . . . . . . .
BSS upgrade provisioning rules . . . . . . . . . . . . . .
Maximum BSS conguration . . . . . . . . . . . . . . . .
E1 cable requirements for a fully congured PCU . . . . .
PCU hardware layout . . . . . . . . . . . . . . . . . . . . .
PCU shelf (cPCI) . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
MPROC board . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
PSP planning considerations . . . . . . . . . . . . . . .
DPROC board . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
PICP or PRP planning considerations . . . . . . . . . . .
PMC module . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Transition module . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
PCU equipment redundancy and provisioning goals . . . . . .
Support for equipment redundancy . . . . . . . . . . . .
PCU equipment redundancy planning . . . . . . . . . . .
Upgrading the PCU . . . . . . . . . . . . . . . . . . . .
Multiple (3xPCU) PCUs per BSC . . . . . . . . . . . . . . . .
Introduction to multiple PCUs . . . . . . . . . . . . . . .
PCU example congurations . . . . . . . . . . . . . . . .
E1 link provisioning for GPRS and EGPRS . . . . . . . . . . .
E1 interface provisioning . . . . . . . . . . . . . . . . .
E1 Planning considerations . . . . . . . . . . . . . . . .
QoS capacity . . . . . . . . . . . . . . . . . . . . . . . . . .
MTBR allocation . . . . . . . . . . . . . . . . . . . . . .
PRP-PDTCH QoS planning . . . . . . . . . . . . . . . . .
PCU-SGSN: trafc and signal planning . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Gb entities . . . . . . . . . . . . . . . . . . . . . . . . .
General planning guidelines . . . . . . . . . . . . . . . .
Specic planning guidelines . . . . . . . . . . . . . . . .
Gb signaling . . . . . . . . . . . . . . . . . . . . . . . .
Determining net Gb load . . . . . . . . . . . . . . . . . .
Gb link timeslots . . . . . . . . . . . . . . . . . . . . . .
Frame relay parameter values . . . . . . . . . . . . . . .
BSS-PCU hardware planning example for GPRS . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
BSS - PCU planning example for GPRS . . . . . . . . . .
BSS-PCU hardware planning example for EGPRS . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
BSS - PCU planning example for EGPRS . . . . . . . . .
BSS - PCU planning example for EGPRS with QoS enabled
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-2
8-2
8-4
8-11
8-11
8-12
8-15
8-16
8-18
8-18
8-18
8-19
8-19
8-19
8-20
8-20
8-20
8-24
8-24
8-24
8-25
8-25
8-25
8-26
8-26
8-26
8-32
8-34
8-34
8-34
8-34
8-37
8-37
8-37
8-39
8-41
8-44
8-46
8-46
8-46
8-47
8-47
8-47
8-48
8-49
8-50
8-52
8-52
8-52
8-60
8-60
8-60
8-68
68P02900W21-R
GMR-01
Nov 2007
Contents
Chapter 9: Planning exercises

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-2
9-2
9-3
9-4
9-4
9-5
9-5
9-6
9-8
9-8
9-8
9-8
9-9
9-9
9-11
9-11
9-13
9-14
9-14
9-14
9-15
9-15
9-15
9-15
9-15
9-15
9-16
9-16
9-16
9-16
9-17
9-17
9-17
9-29
9-41
9-55
9-73
9-73
9-73
Location area planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location area planning calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-2
10-3
10-3
Pre-requisites . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . .
Network topology . . . . . . . . . . . . . . . . .
Exercises. . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Determine the hardware requirements for BTS B . . .
Cabinet . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . .
Determine the hardware requirements for BTS K . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Cabinet . . . . . . . . . . . . . . . . . . . . . .
Receiver requirements . . . . . . . . . . . . . . .
Transmitter combining requirements . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . .
Determine the hardware requirements for the BSC . .
Introduction . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . .
Determine the hardware requirements for the RXCDR.
MSI requirements . . . . . . . . . . . . . . . . .
Transcoder requirement . . . . . . . . . . . . . .
Link interface . . . . . . . . . . . . . . . . . . .
GPROC requirement . . . . . . . . . . . . . . . .
KSW/DSW2 requirement . . . . . . . . . . . . . .
KSWX/DSWX requirement . . . . . . . . . . . . .
GCLK requirement . . . . . . . . . . . . . . . . .
CLKX requirement . . . . . . . . . . . . . . . . .
PIX requirement . . . . . . . . . . . . . . . . . .
LANX requirement . . . . . . . . . . . . . . . . .
Power supply. . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . .
Calculations using alternative call models . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Planning example 1 . . . . . . . . . . . . . . . .
Planning example 4 (using AMR) . . . . . . . . .
Planning example of BSS support for LCS provisioning
Typical parameter values . . . . . . . . . . . . .
LCS planning example calculations . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 10: Location area planning
Chapter 11: Call model parameters

Deriving call model parameters from network statistics
Standard call model parameters . . . . . . . . . .
Call duration (T) . . . . . . . . . . . . . . . . . .
Ratio of SMSs per call (S) . . . . . . . . . . . . .
Ratio of handovers per call (H). . . . . . . . . . .
Ratio of intra BSS handovers to all handovers (i) .
Ratio of location updates per call (I) . . . . . . . .
Ratio of IMSI detaches per call (I) . . . . . . . . .
.
.
.
.
.
.
.
.
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11-2
11-2
11-4
11-5
11-6
11-6
11-7
11-7
xi
GMR-01
Contents
Location update factor (L) . .

Paging rate (PGSM) . . . . . .
Pages per call (PPC) . . . . .
Sample statistic calculations .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11-8
11-8
11-9
11-10
Chapter 12: Standard BSS and Horizon BTS congurations

Standard congurations . . . . . . . . . . . . . . . . . . . . .
Typical BSS congurations. . . . . . . . . . . . . . . . . . . .
BSC with 24 BTSs . . . . . . . . . . . . . . . . . . . . . .
BSC with full redundancy . . . . . . . . . . . . . . . . . .
Transcoder. . . . . . . . . . . . . . . . . . . . . . . . . .
Single cabinet BTS congurations . . . . . . . . . . . . . . . .
Single cabinet Horizon II macro BTS . . . . . . . . . . . .
Single cabinet Horizon II mini BTS . . . . . . . . . . . . .
Single cabinet Horizon II micro BTS . . . . . . . . . . . . .
Single cabinet Horizonmacro BTS . . . . . . . . . . . . . .
Two cabinet BTS congurations . . . . . . . . . . . . . . . . .
Two cabinet Horizon II macro BTS . . . . . . . . . . . . . .
Two cabinet Horizon II mini BTS. . . . . . . . . . . . . . .
Two cabinet Horizonmacro BTS . . . . . . . . . . . . . . .
Three cabinet BTS congurations . . . . . . . . . . . . . . . .
Three cabinet Horizon II macro BTS . . . . . . . . . . . . .
Three cabinet Horizon II mini BTS . . . . . . . . . . . . . .
Three cabinet Horizon II micro BTS . . . . . . . . . . . . .
Three cabinet Horizonmacro BTS . . . . . . . . . . . . . .
Four cabinet BTS congurations . . . . . . . . . . . . . . . . .
Four cabinet Horizon II macro BTS . . . . . . . . . . . . .
Four cabinet Horizon II mini BTS . . . . . . . . . . . . . .
Four cabinet Horizonmacro BTS . . . . . . . . . . . . . . .
Horizon macrocell RF congurations . . . . . . . . . . . . . .
Overview of conguration diagrams . . . . . . . . . . . . .
Horizon II macro cabinets . . . . . . . . . . . . . . . . . .
Horizon II macro cabinets with PGSM Duplexer . . . . . . .
Horizon II mini cabinets . . . . . . . . . . . . . . . . . . .
Horizon II micro cabinets . . . . . . . . . . . . . . . . . .
Horizonmacro cabinets . . . . . . . . . . . . . . . . . . .
Horizoncompact2 . . . . . . . . . . . . . . . . . . . . . .
Microcell RF congurations . . . . . . . . . . . . . . . . . . .
Horizonmicro2 . . . . . . . . . . . . . . . . . . . . . . . .
Connecting Horizon II macro cabinets to Horizonmacro cabinets
Connection overview . . . . . . . . . . . . . . . . . . . . .
Compatibility issues . . . . . . . . . . . . . . . . . . . . .
Examples of mixed cabinet congurations . . . . . . . . . .
Connecting Horizon II macro cabinets to M-Cell6 cabinets . . .
Connection overview . . . . . . . . . . . . . . . . . . . . .
Compatibility issues . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-2
12-3
12-3
12-4
12-5
12-6
12-6
12-7
12-8
12-9
12-10
12-10
12-11
12-12
12-13
12-13
12-14
12-15
12-16
12-18
12-18
12-19
12-20
12-22
12-22
12-22
12-32
12-39
12-47
12-50
12-60
12-65
12-65
12-68
12-68
12-68
12-68
12-76
12-76
12-76
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-2
13-3
13-3
13-4
13-5
13-5
13-6
13-7
Chapter 13: M-Cell BTS congurations

Standard M-Cell congurations . . . . . . . . .
Single cabinet BTS congurations . . . . . . . .
Single cabinet M-Cell6 BTS . . . . . . . . .
Single cabinet M-Cell2 BTS . . . . . . . . .
Two cabinet BTS conguration. . . . . . . . . .
Two cabinet M-Cell6 BTS . . . . . . . . . .
Two cabinet M-Cell6 BTS with CTU2 Adapter
Three cabinet BTS conguration . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
Contents
Three cabinet M-Cell2 BTS

Four cabinet BTS conguration
Four cabinet M-Cell6 BTS .
M-Cell RF congurations. . . .
Overview. . . . . . . . . .
M-Cell6 cabinets . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-7
13-8
13-8
13-9
13-9
13-9
13-47
xiii
GMR-01
Contents
xiv
68P02900W21-R
GMR-01
Nov 2007
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1: BSS block diagram . . . . . . . . . . . . . . . . . . . . . . . . .

2-1: BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2: Possible network topology . . . . . . . . . . . . . . . . . . . . . .
2-3: Star connection . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4: Closed loop and open ended daisy chains . . . . . . . . . . . . . .
2-5: Simple daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6: Daisy chain with branch . . . . . . . . . . . . . . . . . . . . . . .
2-7: Typical low capacity BSC/BTS conguration . . . . . . . . . . . . .
2-8: Example using a switching network . . . . . . . . . . . . . . . . .
2-9: Timeslot allocation using new and old algorithms . . . . . . . . . .
2-10: Alternative network conguration with E1 switching network . . .
2-11: A conguration with a BTS equipped with two redundant RTFs . .
2-12: A conguration with a BTS equipped with two non-redundant RTFs
2-13: Fully equipped RTF. . . . . . . . . . . . . . . . . . . . . . . . .
2-14: Sub-equipped RTF . . . . . . . . . . . . . . . . . . . . . . . . .
2-15: XBL utilization . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-16: Conversion of E1 to HDSL links by modem and microsite . . . . .
2-17: Microcell daisy chain network conguration . . . . . . . . . . . .
2-18: Microcell star network conguration . . . . . . . . . . . . . . . .
2-19: Microcell conguration using E1/HDSL links. . . . . . . . . . . .
3-1: UK network users . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2: Eight TDMA timeslots per RF carrier . . . . . . . . . . . . . . . .
3-3: Modulation techniques and channel spacing. . . . . . . . . . . . .
3-4: AMR half rate capacity increase . . . . . . . . . . . . . . . . . . .
3-5: AMR full rate call quality improvements . . . . . . . . . . . . . . .
3-6: GSM half rate capacity increase . . . . . . . . . . . . . . . . . . .
3-7: GSM half rate codec comparison . . . . . . . . . . . . . . . . . .
3-8: First Fresnel zone radius calculation . . . . . . . . . . . . . . . .
3-9: Refraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-10: Measurement of the RRI . . . . . . . . . . . . . . . . . . . . . .
3-11: Refraction effects on a microwave system . . . . . . . . . . . . .
3-12: Attenuation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-13: Reection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-14: Scattering . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-15: Diffraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-16: Polarization. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17: Propagation effect - Rayleigh fading environment . . . . . . . . .
3-18: Rayleigh distribution . . . . . . . . . . . . . . . . . . . . . . . .
3-19: Propagation effect - Rician environment . . . . . . . . . . . . . .
3-20: Rician distribution . . . . . . . . . . . . . . . . . . . . . . . . .
3-21: Plane earth loss . . . . . . . . . . . . . . . . . . . . . . . . . .
3-22: Focusing of power . . . . . . . . . . . . . . . . . . . . . . . . .
3-23: Measurement of gain . . . . . . . . . . . . . . . . . . . . . . . .
3-24: Building propagation . . . . . . . . . . . . . . . . . . . . . . . .
3-25: Okumura propagation graphs . . . . . . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-4
2-2
2-6
2-7
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-17
2-17
2-19
2-20
2-21
2-28
2-28
2-29
2-29
3-5
3-6
3-7
3-11
3-12
3-14
3-15
3-19
3-20
3-21
3-22
3-24
3-25
3-25
3-26
3-27
3-28
3-29
3-29
3-30
3-33
3-35
3-36
3-37
3-38
xv
GMR-01
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
3-26:
3-27:
3-28:
3-29:
3-30:
3-31:
3-32:
3-33:
3-34:
3-35:
3-36:
3-37:
3-38:
3-39:
3-40:
3-41:
3-42:
3-43:
3-44:
3-45:
3-46:
3-47:
3-48:
3-49:
3-50:
3-51:
3-52:
3-53:
3-54:
3-55:
3-56:
3-57:
3-58:
3-59:
3-60:
3-61:
3-62:
3-63:
3-64:
3-65:
3-66:
3-67:
3-68:
3-69:
3-70:
3-71:
3-72:
3-73:
3-74:
3-75:
3-76:
3-77:
3-78:
3-79:
3-80:
3-81:
3-82:
3-83:
BTS antenna height of 50 m, MS height of 1.5 m (GSM900) . . . . . .

BTS antenna height of 100 m, MS height of 1.5 m (GSM900) . . . . .
Path loss against cell radius for small cells . . . . . . . . . . . . . . .
Adjacent cell interference . . . . . . . . . . . . . . . . . . . . . . .
7 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . . . . . .
4 site - 3 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . .
2 site - 6 cell re-use pattern . . . . . . . . . . . . . . . . . . . . . .
Carrier interference measurements . . . . . . . . . . . . . . . . . .
Coding process . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coding process illustration (full rate and enhanced full rate speech) . .
Coding process illustration (AMR full rate and AMR half rate speech) .
Coding process illustration (GSM HR speech, control and data) . . . .
Speech channel encoding . . . . . . . . . . . . . . . . . . . . . . .
Preliminary coding for enhanced full rate speech . . . . . . . . . . .
Speech channel encoding for {22064} GSM half rate speech . . . . .
Speech channel encoding for AMR full rate . . . . . . . . . . . . . .
Speech channel encoding for AMR half rate . . . . . . . . . . . . . .
Control channel coding . . . . . . . . . . . . . . . . . . . . . . . . .
Data channel encoding . . . . . . . . . . . . . . . . . . . . . . . . .
Diagonal interleaving - full rate speech. . . . . . . . . . . . . . . . .
Diagonal interleaving - half rate speech . . . . . . . . . . . . . . . .
Rectangular interleaving control . . . . . . . . . . . . . . . . . . .
Diagonal interleaving - CS data . . . . . . . . . . . . . . . . . . . .
GPRS channel coding scheme 1 (CS1) . . . . . . . . . . . . . . . . .
EGPRS channel coding scheme 1 (MCS-1) . . . . . . . . . . . . . . .
SACCH multiframe (480 ms) for DTX and full rate . . . . . . . . . . .
SACCH multiframe (480 ms) for DTX and half rate . . . . . . . . . . .
Receive diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Training sequence code . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber environment . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber distribution . . . . . . . . . . . . . . . . . . . . . . . . .
Layered architecture . . . . . . . . . . . . . . . . . . . . . . . . . .
Combined cell architecture . . . . . . . . . . . . . . . . . . . . . . .
Combined cell architecture structure . . . . . . . . . . . . . . . . .
Separating BCCH and TCH bands . . . . . . . . . . . . . . . . . . .
Band usage for macrocells with microcells . . . . . . . . . . . . . . .
Frequency split for TCH re-use planning example . . . . . . . . . . .
Avoiding co-channel and adjacent channel interference . . . . . . . .
BBH frequency spectrum allocation . . . . . . . . . . . . . . . . . .
GSM and UMTS system nodes and interfaces . . . . . . . . . . . . .
CCCH and PCCCH decision tree . . . . . . . . . . . . . . . . . . . .
Location area diagram . . . . . . . . . . . . . . . . . . . . . . . . .
MM state models for MS and SGSN . . . . . . . . . . . . . . . . . .
Carrier with reserved and switchable GPRS/EGPRS timeslots . . . . .
Circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots
1 carrier, all timeslots (8 TCHs) designated as switchable . . . . . . .
Generic planning and dimensioning process . . . . . . . . . . . . . .
xvi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-41
3-41
3-42
3-43
3-44
3-45
3-46
3-47
3-51
3-53
3-54
3-55
3-57
3-59
3-60
3-62
3-64
3-66
3-67
3-69
3-70
3-73
3-75
3-77
3-78
3-79
3-80
3-83
3-84
3-85
3-86
3-87
3-88
3-89
3-90
3-91
3-94
3-95
3-97
3-98
3-100
3-101
3-103
3-104
3-105
3-107
3-107
3-109
3-111
3-111
3-115
3-121
3-134
3-143
3-157
3-161
3-161
3-163
68P02900W21-R
GMR-01
Nov 2007
List of Figures
Figure 3-84: Multiplexing 4 TBFs on an air timeslot . . . . . . . . . . . . . . . . . . .

Figure 3-85: LLC_PDU frame layout . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-86: LLC PDU to TDMA burst`
s . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-1: AMR FR/clean speech versus EFR versus performance requirements . . . .
Figure 4-2: AMR FR/clean speech codec modes . . . . . . . . . . . . . . . . . . . . .
Figure 4-3: AMR HR/clean speech versus EFR versus GSM FR versus GSM HR versus
performance requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-4: AMR HR/clean speech codec modes . . . . . . . . . . . . . . . . . . . . .
Figure 4-5: 3 carriers, only one hr-capable carrier. . . . . . . . . . . . . . . . . . . .
Figure 4-6: 3 carriers, all hr-capable. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-7: 5 carriers, only one hr-capable carrier. . . . . . . . . . . . . . . . . . . .
Figure 4-8: 5 carriers, only 3 hr-capable carriers . . . . . . . . . . . . . . . . . . . .
Figure 4-9: 5 carriers, all hr-capable carriers . . . . . . . . . . . . . . . . . . . . . .
Figure 4-10: Rate adaptations: codec modes, thresholds and hysterese . . . . . . . . .
Figure 4-11: Congestion threshold settings for AMR half rate . . . . . . . . . . . . . .
Figure 4-12: Alternative congurations for the BSSC3 cabinet . . . . . . . . . . . . .
Figure 4-13: AMR backhaul paths . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-14: hr backhaul paths - ESS mode enabled . . . . . . . . . . . . . . . . . . .
Figure 5-1: DRI and combiner relationship . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-1: BSS planning diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-2: EGDP conguration with the additional E1 termination in use. . . . . . . .
Figure 6-3: EGDP conguration without the additional E1 termination in use . . . . . .
Figure 7-1: Sub-multiplexing and speech transcoding at the RXCDR . . . . . . . . . .
Figure 7-2: EGDP conguration with the additional E1 termination in use. . . . . . . .
Figure 7-3: EGDP conguration without the additional E1 termination in use . . . . . .
Figure 8-1: PCU to SGSN interface planning . . . . . . . . . . . . . . . . . . . . . .
Figure 8-2: PCU shelf layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-3: GPRS maximum throughput and coverage, fully redundant conguration . .
Figure 8-4: GPRS maximum throughput and coverage, full redundancy not required . .
Figure 8-5: EGPRS maximum throughput and coverage, full redundancy not required .
Figure 8-6: PCU example congurations . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-7: Frame relay parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-8: PCU equipment and link planning for GPRS . . . . . . . . . . . . . . . . .
Figure 8-9: PCU Equipment and link planning for EGPRS . . . . . . . . . . . . . . . .
Figure 9-1: Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10-1: Four BSCs in one LAC . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10-2: Four BSCs divided into two LACs. . . . . . . . . . . . . . . . . . . . . .
Figure 12-1: BSC controlling 24 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12-2: Fully redundant BSC controlling 34 BTSs . . . . . . . . . . . . . . . . .
Figure 12-3: BSSC cabinet equipped to provide transcoding. . . . . . . . . . . . . . .
Figure 12-4: Macrocell BTS with one Horizon II macro cabinet . . . . . . . . . . . . .
Figure 12-5: Macrocell BTS with one Horizon II mini cabinet . . . . . . . . . . . . . .
Figure 12-6: Macrocell BTS with one Horizon II micro cabinet . . . . . . . . . . . . .
Figure 12-7: Macrocell BTS with one Horizonmacro cabinet. . . . . . . . . . . . . . .
Figure 12-8: Macrocell BTS with two Horizon II macro cabinets. . . . . . . . . . . . .
Figure 12-9: Macrocell BTS with two Horizon II mini cabinets. . . . . . . . . . . . . .
Figure 12-10: Macrocell BTS with two Horizonmacro cabinets . . . . . . . . . . . . .
Figure 12-11: Macrocell BTS with three Horizon II macro cabinets . . . . . . . . . . .
Figure 12-12: Macrocell BTS with three Horizon II mini cabinets . . . . . . . . . . . .
Figure 12-13: Macrocell BTS with three Horizon II micro cabinets . . . . . . . . . . .
Figure 12-14: Macrocell BTS with three Horizonmacro cabinets . . . . . . . . . . . .
Figure 12-15: Macrocell BTS with four Horizon II macro cabinets . . . . . . . . . . . .
Figure 12-16: Macrocell BTS with four Horizon II mini cabinets . . . . . . . . . . . . .
Figure 12-17: Macrocell BTS with four Horizonmacro cabinets . . . . . . . . . . . . .
Figure 12-18: [DCS1800] 4 or 8 carrier omni with HCUs and air combining . . . . . . .
Figure 12-19: [DCS1800] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . .
Figure 12-20: [DCS1800] 2 sector 3/3 or 6/6 with DHUs. . . . . . . . . . . . . . . . .
Figure 12-21: [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-167
3-179
3-183
4-6
4-7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-8
4-9
4-12
4-13
4-13
4-14
4-14
4-17
4-28
4-31
4-34
4-35
5-38
6-12
6-62
6-63
7-13
7-15
7-16
8-3
8-16
8-28
8-29
8-30
8-36
8-50
8-52
8-60
9-3
10-4
10-5
12-3
12-4
12-5
12-6
12-7
12-8
12-9
12-10
12-11
12-12
12-13
12-14
12-15
12-16
12-18
12-19
12-20
12-23
12-24
12-25
12-26
xvii
GMR-01
List of Figures
Figure 12-22: [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs . . . . . . . . . . . . . . . . .

Figure 12-23: [DCS1800] 2 cabinets, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining .
Figure 12-24: [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and 4 branch Rx
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12-25: [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining . . . . . . .
Figure 12-26: [PGSM900] 4 or 8 carrier omni with HCUs and air combining . . . . . . . .
Figure 12-27: [PGSM900] 6 or 12 carrier omni with DHUs . . . . . . . . . . . . . . . . .
Figure 12-28: [PGSM900] 2 sector 3/3 or 6/6 with HCUs . . . . . . . . . . . . . . . . . .
Figure 12-29: [PGSM900] 2 cabinets, 2 sector 4/4 or 8/8 with HCUs and air combining . . .
Figure 12-30: [PGSM900] 3 sector 2/2/2 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . .
Figure 12-31: [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining . . .
Figure 12-32: DCS1800/EGSM900 HP Omni-1/SP Omni-2 . . . . . . . . . . . . . . . . . .
Figure 12-33: DCS1800/EGSM900 HP Omni-2/SP Omni-4 . . . . . . . . . . . . . . . . . .
Figure 12-34: DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4 . . . . . . . . . . . . . . . .
Figure 12-35: DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2 . . . . . . . . . . . . .
Figure 12-36: DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4 . . . . . . . . . . . . .
Figure 12-37: DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2 . . . . . . . . . . .
Figure 12-38: DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4 . . . . . . . . . . .
Figure 12-39: [DCS1800/EGSM900] Horizon II micro one-cabinet conguration . . . . . .
Figure 12-40: [DCS1800/EGSM900] Horizon II micro three cabinet conguration. . . . . .
Figure 12-41: 4 carrier omni, duplexed hybrid and air combining . . . . . . . . . . . . . .
Figure 12-42: 6 carrier omni, duplexed dual-stage hybrid and air combining . . . . . . . .
Figure 12-43: 2 sector (3/3), duplexed dual-stage hybrid combining . . . . . . . . . . . . .
Figure 12-44: 2 sector (6/6), duplexed dual-stage hybrid and air combining . . . . . . . . .
Figure 12-45: 3 sector (2/2/2), duplexed hybrid combining . . . . . . . . . . . . . . . . .
Figure 12-46: 3 sector (4/4/4), duplexed hybrid and air combining . . . . . . . . . . . . .
Figure 12-47: 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1). . . .
Figure 12-48: 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2). . . .
Figure 12-49: Horizoncompact2 single BTS system . . . . . . . . . . . . . . . . . . . . .
Figure 12-50: Horizoncompact2 two BTS system . . . . . . . . . . . . . . . . . . . . . .
Figure 12-51: Horizoncompact2 three BTS system . . . . . . . . . . . . . . . . . . . . .
Figure 12-52: Horizonmicro2 single BTS system. . . . . . . . . . . . . . . . . . . . . . .
Figure 12-53: Horizonmicro2 two BTS system . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12-54: Horizonmicro2 three BTS system . . . . . . . . . . . . . . . . . . . . . . .
Figure 12-55: Sector 4/4 conguration with Horizon II macro and Horizonmacro cabinets .
Figure 12-56: Sector 6/6 conguration with Horizon II macro and Horizonmacro cabinets .
Figure 12-57: Sector 2/2/2 conguration (Horizon II macro as master cabinet) . . . . . . .
Figure 12-58: Sector 2/2/2 conguration (Horizonmacro as master cabinet). . . . . . . . .
Figure 12-59: Sector 4/4/4 conguration with Horizon II macro and Horizonmacro cabinets
Figure 12-60: Sector 6/6/6 conguration with Horizon II macro and Horizonmacro cabinets
Figure 12-61: Horizonmacro cabinet conguration using CTUs and CTU2s . . . . . . . . .
Figure 12-62: 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections. . . . . .
Figure 12-63: 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections . . . .
Figure 13-1: Single cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-2: Single cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-3: Two cabinet M-Cell6 BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-4: Two cabinet M-Cell6 BTS with CTU2 Adapters . . . . . . . . . . . . . . . . .
Figure 13-5: Three cabinet M-Cell2 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-6: Four cabinet M-Cell6 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-7: 3 carrier omni, hybrid combining. . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-8: 3 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . .
Figure 13-9: 4 carrier omni, hybrid combining. . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-10: 4 carrier omni, hybrid combining, medium power duplexer . . . . . . . . . .
Figure 13-11: 6 carrier omni, cavity combining . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-12: 6 carrier omni, cavity combining, high power duplexer . . . . . . . . . . . .
Figure 13-13: 8 carrier omni, combining. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-14: 2 sector (3/3), hybrid combining . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-15: 2 sector (3/3), hybrid combining, medium power duplexers . . . . . . . . . .
xviii
. .
. .
12-27
12-28
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-29
12-31
12-33
12-34
12-35
12-36
12-37
12-38
12-40
12-41
12-42
12-43
12-44
12-45
12-46
12-48
12-49
12-51
12-52
12-53
12-55
12-56
12-57
12-59
12-60
12-62
12-63
12-64
12-66
12-66
12-67
12-69
12-70
12-71
12-72
12-73
12-74
12-75
12-77
12-78
13-3
13-4
13-5
13-6
13-7
13-8
13-10
13-11
13-12
13-13
13-15
13-16
13-17
13-18
13-19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02900W21-R
GMR-01
Nov 2007
List of Figures
Figure 13-16: 3 sector (2/2/2), combining . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13-17: 3 sector (2/2/2), combining, medium power duplexers . . . . . . . . . . . .
Figure 13-18: 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . .
Figure 13-19: 3 sector (4/4/4), air combining, medium power duplexers . . . . . . . . . . .
Figure 13-20: 3 sector (4/4/4), cavity combining . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-21: 3 sector (4/4/4), 3-input CBF, hybrid combining . . . . . . . . . . . . . . . .
Figure 13-22: 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers . . . .
Figure 13-24: 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers . . . . . .
Figure 13-25: 3 sector (6/6/6), cavity combining, high power duplexers . . . . . . . . . . .
Figure 13-27: 3 sector (6/6/6), 3-input CBF, combining, medium power duplexers . . . . . .
Figure 13-28: 3 sector (8/8/8), cavity combining, medium power duplexers (Part 1) . . . . .
Figure 13-29: 3 sector (8/8/8), cavity combining, medium power duplexers (Part 2) . . . . .
Figure 13-30: 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 1)
Figure 13-31: 3 sector (8/8/8), cavity combining, high and medium power duplexers (Part 2)
Figure 13-32: 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers (Part
1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-33: 3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers (Part
2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-34: 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 1) .
Figure 13-35: 3 sector (8/8/8), 3-input CBF, combining, medium power duplexers (Part 2) .
Figure 13-36: 3 sector (2/2/2), hybrid combining . . . . . . . . . . . . . . . . . . . . . .
Figure 13-37: 3 sector (2/2/2), hybrid combining, medium power duplexers . . . . . . . . .
Figure 13-38: 2 carrier, single sector, hybrid combining . . . . . . . . . . . . . . . . . . .
Figure 13-39: 2 carrier, single sector, hybrid combining, medium power duplexer. . . . . .
Figure 13-40: 2 sectors (1 carrier per sector) . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13-41: 2 carrier, single sector, air combining . . . . . . . . . . . . . . . . . . . . .
Figure 13-42: 2 sectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-21
13-22
13-23
13-24
13-26
13-27
13-28
13-29
13-31
13-32
13-33
13-34
13-36
13-37
13-38
13-39
. .
13-41
.
.
.
.
.
.
.
.
.
.
13-42
13-43
13-44
13-45
13-47
13-48
13-49
13-50
13-51
13-53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xix
GMR-01
List of Figures
xx
68P02900W21-R
GMR-01
Nov 2007
List
of
Tables
List of Tables
Table 1-1: Transceiver unit usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 1-2: Acronym list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-1: BSS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-2: RTF types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-1: dBm and dBW to power conversion . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2: Speech channel coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-3: AMR codecs, convolutional output bits and punctured bits . . . . . . . . . . . .
Table 3-4: X, Y and Z bit values for AMR FR speech channel encoding. . . . . . . . . . . .
Table 3-5: X, Y, Z and W bit values for AMR HR speech channel encoding . . . . . . . . . .
Table 3-6: Interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-7: Distribution of 456 bits from one 20 ms full rate speech sample . . . . . . . . .
Table 3-8: Distribution of 228 bits from one 20 ms half rate speech sample . . . . . . . . .
Table 3-9: Coding parameters for GPRS coding schemes . . . . . . . . . . . . . . . . . .
Table 3-10: Coding parameters for EGPRS coding schemes . . . . . . . . . . . . . . . . .
Table 3-11: Frequency and parameter setting plan . . . . . . . . . . . . . . . . . . . . .
Table 3-12: Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . .
Table 3-13: Control channel congurations . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-14: Example Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-15: Control channel congurations for non-border location area . . . . . . . . . .
Table 3-16: Control channel congurations for border location area . . . . . . . . . . . . .
Table 3-17: MM state model of MS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-18: Capping settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-19: Arrangement of packet data timeslots for example 1 . . . . . . . . . . . . . .
Table 3-27: Switchable timeslot utilization (Part A) . . . . . . . . . . . . . . . . . . . . .
Table 3-28: Switchable timeslot utilization (Part B) . . . . . . . . . . . . . . . . . . . . .
Table 3-29: Typical TCP throughput against RLC/MAC throughput at zero block error rate .
Table 3-30: ARP mobile selection (ARP Rank) order . . . . . . . . . . . . . . . . . . . . .
Table 3-31: Percentage of code utilization in a 4x3 non-hopping re-use pattern at 20% BLER
Table 3-32: MTBR Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-33: MTBR Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-34: THP Weight Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-35: THP Weight Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-36: QoS Conguration Examples . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-37: QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS . . .
Table 3-38: QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS. . . .
Table 3-39: GPRS downlink data rates (kbit/s) with TCP (CS1). . . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-5
1-21
2-2
2-18
3-18
3-52
3-56
3-61
3-63
3-68
3-71
3-71
3-81
3-92
3-109
3-116
3-126
3-136
3-137
3-138
3-142
3-145
3-148
3-149
3-150
3-151
3-152
3-153
3-154
3-155
3-158
3-160
3-169
3-169
3-171
3-174
3-174
3-175
3-175
3-175
3-176
3-177
3-184
3-184
3-184
xxi
GMR-01
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
3-42: GPRS downlink data rates (kbit/s) with TCP (CS4). . . . . . . . . . . . . . . .

3-43: GPRS downlink data rates (kbit/s) with UDP (CS1) . . . . . . . . . . . . . . .
3-47: EGPRS downlink data rates (kbit/s) with TCP (MCS1) . . . . . . . . . . . . . .
3-56: EGPRS downlink data rates (kbit/s) with UDP (MCS1). . . . . . . . . . . . . .
4-1: AMR potential coverage gains . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2: Supported AMR codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-3: BSS parameters used to determine MS threshold and hysteresis . . . . . . . . .
4-4: Handover and power control - Full and Half Rate default values . . . . . . . . .
4-5: Backhaul conguration based on parameter settings . . . . . . . . . . . . . . .
4-6: Call placement on terrestrial backhaul . . . . . . . . . . . . . . . . . . . . . .
4-7: Voice call mapping on the backhaul for a 64 K RTF . . . . . . . . . . . . . . . .
5-1: Transmit congurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2: BBH capability for Horizon II macro Site Controller . . . . . . . . . . . . . . .
5-3: BBH capability for Horizonmacro Site Controller . . . . . . . . . . . . . . . . .
5-4: CTU/CTU2 power requirements. . . . . . . . . . . . . . . . . . . . . . . . . .
5-5: CTU/CTU2 power requirements for M-Cell cabinets . . . . . . . . . . . . . . .
5-6: Site connection requirements for M-Cell2 and M-Cell6 . . . . . . . . . . . . . .
5-7: Horizon II macro XMUX expansion requirements . . . . . . . . . . . . . . . . .
5-8: Horizon II mini only network XMUX expansion requirements . . . . . . . . . . .
5-9: Horizon II macro as master - Horizon II mini as expansion XMUX requirements .
5-10: Horizon II macro as master - Horizon II mini as expansion XMUX requirements
5-11: Horizonmacro FMUX expansion requirements. . . . . . . . . . . . . . . . . .
6-1: BSC maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2: Typical call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3: Other parameters used in determining GPROC and link requirements . . . . . .
6-4: Signaling message procedures . . . . . . . . . . . . . . . . . . . . . . . . . .
6-5: BTS support for 16 kbit/s RSLs . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6: Number of BSC to BTS signaling links (without LCS) . . . . . . . . . . . . . . .
6-7: Backhaul requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-8: Number of MSC and BSC signaling links without LCS (20% utilization) . . . . .
6-9: Number of MSC and BSC signaling links without LCS (40% utilization) . . . . .
6-10: Number of BSC to RXCDR signaling links . . . . . . . . . . . . . . . . . . . .
6-11: Typical call parameters relating to XBLs . . . . . . . . . . . . . . . . . . . .
6-12: GPROC type/function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-13: KSWX/DSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . .
6-14: KSWX/DSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1: RXCDR maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2: KSWX/DSWX (non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . .
7-3: KSWX/DSWX (redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-185
3-185
3-185
3-186
3-186
3-186
3-187
3-187
3-187
3-188
3-188
3-188
3-189
3-189
3-189
3-190
3-190
3-190
3-191
3-191
3-191
3-192
3-192
4-10
4-16
4-18
4-19
4-32
4-32
4-33
5-12
5-15
5-15
5-18
5-19
5-24
5-29
5-30
5-30
5-30
5-31
6-7
6-13
6-16
6-16
6-21
6-22
6-30
6-37
6-37
6-44
6-45
6-53
6-75
6-76
7-4
7-29
7-29
68P02900W21-R
GMR-01
Nov 2007
List of Tables
Table 8-1: VersaTRAU backhaul recommendations for a given number of PDTCHs . . . . .

Table 8-2: Expected throughput/TS and coding schemes (conservative) . . . . . . . . . . .
Table 8-3: Expected throughput/TS and coding schemes (aggressive) . . . . . . . . . . . .
Table 8-4: BSS upgrade in support of GPRS/EGPRS . . . . . . . . . . . . . . . . . . . . .
Table 8-5: Recommended maximum BSS network parameter values (part A) . . . . . . . .
Table 8-6: Recommended maximum BSS parameter values (part B) . . . . . . . . . . . . .
Table 8-7: Recommended maximum BSS network parameter (part C) . . . . . . . . . . . .
Table 8-8: Provisioning goals (per PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8-9: Upgrade scenarios for PRP conguration . . . . . . . . . . . . . . . . . . . . .
Table 8-10: Local Timeslot Zone Level capacity 4MS/PDTCH . . . . . . . . . . . . . . . .
Table 8-11: PRP Board Service Level Capacity 4MS/PDTCH . . . . . . . . . . . . . . . . .
Table 8-12: Maximum MTBR in UL/DL per multislot capability . . . . . . . . . . . . . . .
Table 8-13: Gb entities and identiers . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8-14: GPRS call mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8-15: EGPRS call model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8-16: EGPRS with QoS enabled call model. . . . . . . . . . . . . . . . . . . . . . .
Table 9-1: Busy hour demand and number of carriers . . . . . . . . . . . . . . . . . . . .
Table 9-2: Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . .
Table 9-3: Customer ordering guide 900 MHz (M-Cell6 indoor) . . . . . . . . . . . . . . .
Table 9-4: Customer ordering guide 1800 MHz (Horizon II macro indoor) . . . . . . . . . .
Table 9-5: Customer ordering guide 1800 MHz (Horizon II macro indoor) . . . . . . . . . .
Table 9-6: GPROCs required at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-7: BSC timeslot requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-8: Equipment required for the BSC . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-9: Equipment required for the RXCDR . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-10: BSU Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-11: RXU shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-12: Control channel calculation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-13: BSU Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-14: Determining the number of XCDR/GDP/GDP2 cards . . . . . . . . . . . . . . .
Table 9-15: RXU3 shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-16: Typical LCS call model parameter . . . . . . . . . . . . . . . . . . . . . . . .
Table 10-1: Example of values for the parameters for location area planning . . . . . . . .
Table 11-1: Typical parameters for BTS call planning . . . . . . . . . . . . . . . . . . . .
Table 11-2: Sample statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-1: Equipment required for 4 or 8 carrier omni with HCUs and air combining . . .
Table 12-2: Equipment required for 6 or 12 carrier omni with DHUs . . . . . . . . . . . .
Table 12-3: Equipment required for 2 sector 3/3 or 6/6 with DHUs . . . . . . . . . . . . .
Table 12-4: Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-5: Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs . . . . . . . . . . .
Table 12-6: Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-7: Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity . . . . . .
Table 12-8: Equipment required for 3 sector 2/2/2 and 2/2/2 . . . . . . . . . . . . . . . .
Table 12-9: Equipment required for 4 or 8 carrier omni with HCUs and air combining . . .
Table 12-10: Equipment required for 6 or 12 carrier omni with DHUs . . . . . . . . . . . .
Table 12-11: Equipment required for 2 sector 3/3 or 6/6 with HCUs . . . . . . . . . . . . .
Table 12-12: Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-13: Equipment required for 3 sector 2/2/2 or 4/4/4 . . . . . . . . . . . . . . . . .
Table 12-14: Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-15: Equipment required for HP Omni-1/SP Omni-2 . . . . . . . . . . . . . . . . .
Table 12-16: Equipment required for HP Omni-1/SP Omni-2 . . . . . . . . . . . . . . . . .
Table 12-17: Equipment required for HP Bowtie-2/SP Bowtie-4 . . . . . . . . . . . . . . .
Table 12-18: Equipment required for HP 2 sector 1/1/SP 2 sector 2/2 . . . . . . . . . . . .
Table 12-19: Equipment required for HP 2 sector 2/2/SP 2 sector 4/4 . . . . . . . . . . . .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-8
8-8
8-9
8-11
8-12
8-13
8-14
8-31
8-32
8-40
8-41
8-43
8-46
8-52
8-61
8-69
9-2
9-6
9-6
9-9
9-10
9-11
9-12
9-13
9-16
9-49
9-53
9-57
9-65
9-69
9-70
9-73
10-3
11-2
11-10
12-23
12-24
12-25
. .
. .
12-26
12-27
.
.
.
.
.
.
.
.
.
.
.
.
12-28
12-29
12-30
12-33
12-34
12-35
. .
. .
12-36
12-37
.
.
.
.
.
.
12-38
12-39
12-41
12-42
12-43
12-44
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xxiii
GMR-01
List of Tables
Table 12-20: Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2 . . . . . . . . . . . .

Table 12-21: Equipment required for HP 3 sector 2/2/2/SP 3 sector 4/4/4 . . . . . . . . . . . .
Table 12-22: Equipment required for Horizon II micro one cabinet conguration . . . . . . . .
Table 12-23: Equipment required for Horizon II micro three cabinet conguration . . . . . . .
Table 12-24: Equipment required for 1 cabinet, 4 CTU conguration, duplexed hybrid and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-25: Equipment required for 1 cabinet, 6 CTU conguration, duplex dual-stage hybrid
and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-26: Equipment required for 1 cabinet, 6 CTU conguration, duplexed dual-stage hybrid
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-27: Equipment required for dual cabinet, 12 CTU conguration, duplexed dual-stage
hybrid and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-28: Equipment required for 1 cabinet, 6 CTU conguration, duplexed hybrid
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-29: Equipment required for dual cabinet, 12 CTU conguration duplexed hybrid and air
combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 12-30: Equipment required for 4 cabinet, 24 CTU conguration, duplex dual-stage hybrid
and air combining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-1: Equipment required for single cabinet, 4 TCU conguration with hybrid combining
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-2: Equipment required for single cabinet, 4 TCU conguration with hybrid combining,
diversity and medium power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-5: Equipment required for single cabinet, 6 TCU conguration with cavity combining
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-6: Equipment required for single cabinet, 6 TCU conguration with cavity combining,
diversity and high power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-7: Equipment required for multiple cabinet, 8 TCU conguration with combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-9: Equipment required for single cabinet, 6 TCU conguration with combining, diversity
and medium power duplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-10: Equipment required for single cabinet, 6 TCU conguration with combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-11: Equipment required for single cabinet, 6 TCU conguration with combining,
diversity and medium power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-12: Equipment required for dual cabinet, 12 TCU conguration with air combining,
diversity and medium power duplexers (3 antenna per sector). . . . . . . . . . . . . . . . . .
Table 13-13: Equipment required for multiple cabinet, 12 TCU conguration with air combining,
diversity and medium power duplexers (2 antenna per sector). . . . . . . . . . . . . . . . . .
Table 13-14: Equipment required for multiple cabinet, 12 TCU conguration with hybrid
combining and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-15: Equipment required for dual cabinet, 12 TCU conguration with 3-input CBF,
hybrid combining and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-16: Equipment required for multiple cabinet, 12 TCU conguration with 3-input CBF,
air combining, diversity and medium power duplexers. . . . . . . . . . . . . . . . . . . . . .
Table 13-17: Equipment required for 3 cabinets, 15 TCU conguration with 3-input CBF, air
combining, diversity and medium power duplexers (2 antennas/sector) . . . . . . . . . . . . .
Table 13-19: Equipment required for 3 RF cabinets, 18 TCU conguration with cavity combining,
diversity and high power duplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiv
12-45
12-47
12-48
12-50
12-51
12-52
12-54
12-54
12-56
12-58
12-58
13-10
13-11
13-13
13-14
13-14
13-16
13-17
13-19
13-20
13-20
13-22
13-23
13-25
13-25
13-27
13-28
13-30
13-30
13-32
13-33
68P02900W21-R
GMR-01
Nov 2007
List of Tables
Table 13-21: Equipment required for 3 cabinets, 18 TCU conguration with 3-input CBF,
diversity and both high and medium power duplexers . . . . . . . . . . . . . . . . . . . . . .
Table 13-25: Equipment required for 4 cabinets, 24 TCU conguration with 3-input CBF,
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
and diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-30: Equipment required for single cabinet, 2 TCU conguration with diversity . . . .
Table 13-31: Equipment required for single cabinet, 2 TCU conguration with air combining and
diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 13-32: Equipment required for single cabinet, 2 TCU conguration with diversity . . . .
68P02900W21-R
Nov 2007
13-35
13-35
13-39
13-40
13-44
13-46
13-46
13-48
13-49
13-51
13-52
13-52
xxv
GMR-01
List of Tables
xxvi
68P02900W21-R
GMR-01
Nov 2007
About
This
Manual
System Information: BSS Equipment

Planning
What is covered in this manual?

This manual provides an overview of the various BSS elements and BSS planning methodology.
It describes the requirements and procedures for planning a BSS cell site, a BTS including
Horizon and M-cell range of equipments, a BSC including the scenario when a LCS is used, an
RXCDR and location area. It provides an overview of AMR and its usage in the Motorola system.
It describes about obtaining the call model parameters from network statistics collected at the
OMC-R. This manual also deals with standard BSS, Horizon BTS and M-Cell BTS congurations.
68P02900W21-R
Nov 2007
GMR-01
Revision history
Revision history
Version information
The following shows the status of this document since it was rst released.
Issue
Date of issue
Remarks
Sep 2003
Issue P - includes GSM Software Release 7 and EGPRS
Mar 2004
Issue Q - includes GSM Half Rate
Feb 2006
Issue R - includes GSM Software Release 8
Resolution of Service Requests

The following Service Requests are resolved in this document:
Service Request
CMBP
Number
Remarks
SR1085673
Added recommendation for evenly distributing GSLs

in Load balancing on page 6-49.
SR1098032
Expand on the existing planning guidelines and rules,

which predominantly assumes actual data trafc is to
be handled by the network.
SR2004750
In Table 6-1, correct text should read that GSR7

supports 512 DRIs.
SR2021297
Corrected the content under section Link control

function on page 6-55.
SR2099238
Formula for evaluation of necessary quantity of GDS

TRAU E1 on page 8-37 links for E1 link provisioning
is updated.
68P02900W21-R
GMR-01
Nov 2007
Incorporation of Change Notices
Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:
CN Date
CN Number
Title
26 Apr 2005
00W21002
Incorrect DRI Planning Limit in GSR7 68PO2900W21-Q, GSM

BSS Equipment Planning Guide.
26 Apr 2005
00W21004
Add guidelines to dimension PRP and PDTCH planning with

primarily GPRS signaling trafc in System Information: BSS
Equipment Planning (68P02900W21) manual.
07 Sep 2005
00W21005
Incorrect MTL Link Utilization.
03 Oct 2005
00W21006
Incorrect value of Average XBL message length.
17 Jul 2006
00W21007
Updated the Multiple serial interface planning considerations

section.
18 Oct 2006
00W21008
Formula for evaluation of necessary quantity of GDS TRAU E1

links for E1 link provisioning is updated.
68P02900W21-R
Nov 2007
GMR-01
General information
General information
Purpose
Motorola cellular communications documents 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.
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 customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
If this document 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 are supplied automatically by Motorola and posted
on the Motorola customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that 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
GMR-01
Nov 2007
Text conventions
Text conventions
The following conventions are used in the Motorola cellular infrastructure documents to
represent keyboard input text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Items of interest within a command appear like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Items of interest within a screen display appear like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or
CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02900W21-R
Nov 2007
GMR-01
Contacting Motorola
Contacting Motorola
Motorola appreciates feedback from the users of our documents.
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Ofce.
Questions and comments

Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number with the error
A detailed description of the error and if possible the proposed solution
68P02900W21-R
GMR-01
Nov 2007
Security advice
Security advice
Motorola systems and equipment provide security parameters that can be congured 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 condentiality, 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 specic recommendations regarding security practices.
The implementation of these recommendations and nal responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
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 Ofce.
68P02900W21-R
Nov 2007
GMR-01
Warnings, cautions, and notes
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
Warning text and consequence for not following the instructions in the warning.
Cautions
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following format:
Note text.
68P02900W21-R
GMR-01
Nov 2007
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment:
The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Power down or unplug the equipment before servicing.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable 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.
Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic elds (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic elds) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02900W21-R
Nov 2007
GMR-01
Caring for the environment
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Ofce.
In EU countries
The following information is provided to enable regulatory compliance with the European Union
(EU) directives identied and any amendments made to these directives when using Motorola
equipment in EU countries.
Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landll sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landll sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
10
68P02900W21-R
GMR-01
Nov 2007
CMM labeling and disclosure table
CMM labeling and disclosure table
The Peoples Republic of China require that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identied in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identied in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years, fty years in the example
shown.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution, or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
eld-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
68P02900W21-R
Nov 2007
11
GMR-01
Motorola document set
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard copy documents or CD-ROMs with your Motorola
Local Ofce or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner denitions

A banner (oversized text on the bottom of the page, for example, PRELIMINARY UNDER
DEVELOPMENT) indicates that some information contained in the document is not yet approved
for general customer use.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels as individually standardized, or may not be
present at all in some parts of the network in which it is normally implemented. The document
set, of which this document 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.
12
68P02900W21-R
GMR-01
Nov 2007
Chapter
1
Introduction to planning
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-18
Acronyms on page 1-21
OMC-R planning is beyond the scope of this manual.
For information on installing a new OMC-R, refer to the manual Installation

and Conguration: OMC-R Clean Install (68P02901W47). For information on
upgrading an existing OMC-R, refer to the software release Software Release
Notes: OMC-R System (68P02901W74).
68P02900W21-R
Nov 2007
1-1
GMR-01
Manual overview
Manual overview
Introduction
The manual contains information about planning a GSM network, and utilizing a combination of
Horizon and M-Cell BTS equipment.
Contents
The manual contains the following chapters:
Chapter 1 Introduction to planning

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 the AMR and usage in the Motorola system.
Chapter 5 BTS planning steps and rules

Provides the planning steps and rules for the BTS, including the Horizon and M-Cell range
of equipments.
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 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.
Chapter 10 Location area planning

Provides the planning steps and rules for location area planning.
1-2
68P02900W21-R
GMR-01
Nov 2007
Contents
Chapter 11 Call model parameters

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 congurations

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

Provides diagrams of the logical interconnections of the components in various M-Cell
BTS site congurations.
68P02900W21-R
1-3
GMR-01
Nov 2007
BSS equipment overview
BSS equipment overview
System architecture
The architecture of the Motorola Base Station System (BSS) is versatile, and allows several
possible congurations for a given system. The BSS is a combination of digital and RF
equipment that communicates with the Mobile Switching Centre (MSC), the Operations and
Maintenance Centre Radio (OMC-R), and the Mobile Stations (MS) as shown in Figure 1-1.
Figure 1-1
BSS block diagram

A INTERF ACE
MSC LRs
OMC-R
RXCDR
SGSN
BS S
O&M
PCU
BS S
BSC
ABIS INTERFACE
BTS 1
BTS 5
BTS 2
BTS 6
BTS 3
BTS 7
BTS 8
...
BTS n
BTS 4
AIR INTERF ACE

MS
MS
...
MS
MS
...
ti-GS M-BS S _block_dia gra m-00001-a i-s w
1-4
68P02900W21-R
GMR-01
Nov 2007
System components
The OMC-R can be linked through the RXCDR and/or to the BSS/BSC direct.
The example of multiple MSs connected to BTS 4 and BTS 7, is assumed to be

connected to all the other BTSs as shown in Figure 1-1.
System components
The BSS is 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 trafc, and can be located at the BSC or between the BSC and MSC. When
half rate is in use, it is possible to achieve a greater reduction (refer to the transcoding sections
of Chapter 6 BSC planning steps and rules and Chapter 7 RXCDR planning steps and rules
for a 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 can 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), M-Cell6 and MCell-2 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 and BTS6.
Transceiver Control Unit (TCU-B)
M-Cell6 and M-Cell2.
Transceiver Control Unit, micro

(TCU-m)
M-Cellmicro, M-Cellcity and M-Cellcity+.
Except for 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.
68P02900W21-R
1-5
GMR-01
Nov 2007
System components
CTU2
In Horizon II macro, the transceiver functions are provided by the CTU2, which can be
congured to operate in single or double density mode.
This CTU2 can also be used by Horizonmacro as a CTU replacement with restrictions (see
NOTE on page 1-7). Depending on the number of CTU/CTU2s in the Horizonmacro cabinet,
there are output power restrictions that needs a mandatory third power supply installed in the
Horizonmacro cabinet. This can affect the battery hold-up module in ac-powered cabinets,
as the location for the third power supply means that the battery hold-up module has to be
removed, and an external battery backup unit added. There are no available slots for the
redundant power supply if three power supplies are required.
The CTU2 can also be used by M-Cell6 and M-Cell2 with a CTU2 Adapter. The M-Cell6 cabinet
requires up to three power supplies when used with CTU2s. The M-Cell2 cabinet requires up to
two power supplies when used with CTU2s.
Description and planning rules for the CTU2 are provided in Chapter 5 BTS planning steps and
rules of this manual. Conguration diagrams are shown in Chapter 12 Standard BSS and
Horizon BTS congurations. The receivers can support receive diversity.
CTU2s do not support the use of CCBs. A CTU2 cannot be CCB equipped and does
not act as a full replacement or swap for the CTU. The CTU2 only acts as a CTU
replacement in the non-controller or standby controller mode. Contact the Motorola
Local Ofce 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 BTS planning steps and rules of this manual.
Conguration diagrams are shown in Chapter 12 Standard BSS and Horizon BTS congurations.
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 Transmission systems and conguration diagrams are shown in Chapter 12 Standard
BSS and Horizon BTS congurations. 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 BTS
planning steps and rules of this manual. Conguration diagrams are shown in Chapter 13
M-Cell BTS congurations. The receivers can support receive diversity.
1-6
68P02900W21-R
GMR-01
Nov 2007
System components
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
GMR-01
Nov 2007
BSS features
BSS features
Planning impacts
This section provides a description of the software features that might affect the required
equipment before planning the actual equipment. Check with the appropriate Motorola sales
ofce regarding software availability with respect to these features.
Diversity on page 1-8
Frequency hopping on page 1-9
Short Message Service, Cell Broadcast (SMS CB) on page 1-9
Code Storage Facility Processor (CSFP) on page 1-10
PCU for GPRS upgrade on page 1-10
Enhanced-GPRS (EGPRS) on page 1-10
Adaptive Multi-Rate (AMR) on page 1-11
{22064} GSM half rate on page 1-12

LoCation Services (LCS) on page 1-13
{22322} BSC Reset Management (BRM) on page 1-14
{24347} Advanced Speech Call Item (ASCI) on page 1-14
{23769} VersaTRAU backhaul for EGPRS on page 1-15
{23956} Quality of Service (QoS) on page 1-15)
{28075} Improved Timeslot Sharing (ITS) on page 1-17
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 signicant and in
improved interference protection. Two Rx antennas are required for each sector. Equivalent
overlapping antenna patterns and sufcient physical separation between the two antennas are
required to obtain the necessary de-correlation.
1-8
68P02900W21-R
GMR-01
Nov 2007
Frequency hopping
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 as follows:
Synthesizer hopping needs the use of wideband (hybrid) combiners for transmit combining,
while baseband hopping does not.
Baseband hopping needs 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:
Use Hybrid combining. 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 trafc. One

transceiver in each sector must be on a xed 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 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.
Calls could be dropped, if a single transceiver fails, due to the inability to inform the MSs.
Short Message Service, Cell Broadcast (SMS CB)

The Short Message Service, Cell Broadcast (SMS CB) feature, is a means of unilaterally
transmitting data to MSs on a per cell basis. A Cell Broadcast Channel (CBCH) provides this
feature. The data originates from either a Cell Broadcast Centre (CBC) or OMC-R (user-dened
messages are 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 ensures that the message is transmitted as requested.
68P02900W21-R
1-9
GMR-01
Nov 2007

The BSS supports a GPROC acting as the Code Storage Facility Processor (CSFP). The CSFP
allows preloading 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 is equipped for
redundancy as required.
PCU for GPRS upgrade

The PCU hardware provides GPRS functionality and is part of the BSS equipment. GPRS
introduced packet data services and GPRS planning are fundamentally different from the
planning of circuit-switched networks. One of the reasons for the difference is that a GPRS
network allows the queuing of data trafc 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.
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 also provides support for the 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 users packet data throughput from a maximum of 21.4 kbit/s per air timeslot with GPRS
to a maximum of 59.2 kbit/s per air timeslot with EGPRS.
The maximum data throughput for a multi-slot mobile utilizing all eight air timeslots with
EGPRS is 473.6 kbit/s compared to 171.2 kbit/s in GPRS.
The initial release of EGPRS provides support for a multi-slot mobile using four downlink
and two uplink air timeslots.
Support for the mobile classes, which dictate the multi-slot capabilities of a mobile and is
the same for EGPRS as in GPRS (classes 1-12).
Although a large portion of the EGPRS impact, the BSS software is focused on the air interface.
Impacts also exist on the terrestrial interfaces to carry the large volume of data trafc produced
by these new data rates.
The data rates used here are theoretical values.
1-10
68P02900W21-R
GMR-01
Nov 2007
Adaptive Multi-Rate (AMR)
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. It provides increased capacity by allocating
half rate channels to some or all mobiles. AMR selects the optimum channel rate as 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 is tuned by the network user on a cell-by-cell
basis to obtain the best balance between quality and capacity. AMR is introduced using current
hardware components, or it can utilize new hardware that further enhances the benets of AMR.
Due to the increased processing requirements of AMR, the existing GDP (which currently
supports 30 voice channels and data services) only supports 15 AMR voice channels. However,
two GDPs are paired to support a full E1s worth of channels (30). This results in an overall
reduction in transcoding shelf (or cage) capacity - 30 channels per GDP pair.
The AMR program introduces new transcoder equipment (the GDP2), capable of supporting 60
voice (AMR or non-AMR) channels, thus reducing footprint. The existing RXU shelf has only one
E1 connection per transcoder slot, hence the GDP2 only supports 30 channels when used in this
conguration. A new RXU shelf (RXU3) and BSSC cabinet (BSSC3) have been introduced to
utilize the added capacity.
When using the GDP2 within the new RXU3 shelf in a non-MSI slot, enhanced
capacity mode must be enabled to access the second E1.
The GDP2 can be used to full capacity in the existing BSU shelf, which has
no associated E1 limitation.
The existing hardware 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 to fully utilize all 16 half rate channels. The
existing hardware also supports 16 kbit/s switching on the backhaul between the BSC and
RXCDR, requiring 16 kbit/s per voice channel.
The Double Kiloport Switch (DSW2) has been introduced to address the problem. 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 an 8
kbit/s subchannel, rather than the 16 kbit/s subchannel required with KSWs. This eliminates the
need for the two additional 64 kbit/s timeslots required per half rate capable RTF. There is one
exception, that is, when the 7.95 kbit/s half rate codec mode is included in the half rate Active
Codec Set. This codec mode needs 16 kbit/s backhaul, mandating the extra backhaul resources.
The half rate Active Codec Set is provisioned on a per cell basis.
Before 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/reconguration. With AMR, when a half rate trafc channel is assigned, the voice
stream utilizes an 8 kbit/s channel (depending upon the codec modes employed). The DSW2
benet of 8 kbit/s subrate switching allows this capability to be realized. Dynamic assignment of
BSC to RXCDR channels is employed to maximize Ater channel usage. The BSC assigns 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 some calls are utilizing half rate backhaul.
68P02900W21-R
1-11
GMR-01
Nov 2007
GSM half rate
Extended range cells

AMR is only supported on the normal range timeslots and not 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 has to handover to EFR/FR on the extended range timeslot.
Handovers in the opposite direction can handover to AMR.
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
subchannels, 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 and is considered a viable option for high-density areas.
GSM half rate is introduced using current hardware components, or utilizing new hardware
that further enhances the benets 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. As the current RXU shelf has only one E1 connection per
transcoder slot, the GDP2 supports 30 channels when used in this conguration. The new RXU
shelf (RXU3) and BSSC cabinet (BSSC3) are used to utilize the full capacity.
The backhaul between the BTS and BSC is 8 kbit/s or 16 kbit/s. 8 kbit/s needs that the subrate
(8 K) 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 to fully utilize all 16 half rate channels. The
existing hardware also supports 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) 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 is carried in an 8 kbit/s subchannel, rather than the 16 kbit/s subchannel
required with KSWs. This eliminates the need for the two additional 64 kbit/s timeslots required
per half rate capable RTF.
As with AMR half rate, a GSM half rate call can t within an 8 kbit/s timeslot (an Ater channel) on
the terrestrial resource from the BSC to the RXCDR, rather than the 16 kbit/s timeslot required
for full rate calls. If a percentage of the active calls are assumed to be half rate, then efciency
can be gained by reducing the number of terrestrial resources between the BSC and RXCDR.
The DSW2 benet of 8 kbit/s subrate switching allows this capability to be realized. Dynamic
assignment of BSC to RXCDR channels is employed to maximize Ater channel usage. The BSC
can assign an 8 kbit/s or 16 kbit/s channel as required, based upon the backhaul in use across
the BSCBTS interface. This allows the user to equip fewer channels than previously possible,
with the assumption that some calls are 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.
1-12
68P02900W21-R
GMR-01
Nov 2007
LoCation Services (LCS)

GSM half rate is only supported on the normal range timeslots and not on extended range
timeslots (it is envisaged that the C/I ratio in the extended range portion of an extended range
cell does not support a half rate call).
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 classied as a supplementary service and can be subscribed to without subscribing to a
basic telecommunication service. LCS is applicable to any target MS, whether the MS supports
LCS. However, there are restrictions on choice of positioning method or notication of a location
request to the MS user when the LCS or individual positioning methods respectively are not
supported by the MS.
LCS utilizes one or more positioning mechanisms to determine the location of a mobile station.
Positioning an MS involves two main steps:
Signal measurements.
Location estimate computation based on the measured signals.
Location service requests are 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 location of the client MS, 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 an LCS client where the client is treated as 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 considered to be within 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.
LCS architecture
The LCS architecture can be one of the following:
NSS-based
The Serving Mobile Location Centre (SMLC) is connected to an MSC instead of a BSC. The
MSC acts as a relay point for LCS signaling between the SMLC and BSC.
68P02900W21-R
1-13
GMR-01
Nov 2007
BSC Reset Management (BRM)
BSS-based
The SMLC is connected to a BSC instead of an MSC. The LCS signaling between the SMLC
and BSC goes directly between the two entities.
BSC Reset Management (BRM)

{22322}
BSC Reset Management (BRM) provides the option for fast failover of the BSC, for certain types
of equipment failure. This minimizes the BSS outage, reducing the downtime from 10 minutes
to 20 minutes to less than two minutes for most occurrences.
Equip the BSC with a redundant secondary GPROC3 to utilize this feature.
Advanced Speech Call Item (ASCI)

{24347}
The Advanced Speech Call Item (ASCI) feature includes the enhanced Multi-Level Precedence
and Preemption (eMLPP) feature.
Enhanced Multi-level Precedence and Pre-emption

{24347}
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.
With the eMLPP feature, the following functions are supported:
Pre-emption: The Motorola BSS supports resource pre-emption based on a full set of A
interface priority levels and procedures as dened in 3GPP TS 48.008. 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 where calls do not necessarily require to be terminated due to a
single failure on the linkset between an RXCDRBSC or due to MSC indicated
CIC changes.
1-14
68P02900W21-R
GMR-01
Nov 2007
VersaTRAU backhaul for EGPRS
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.
VersaTRAU backhaul for EGPRS

{23769}
VersaTRAU reduces EGPRS backhaul costs by taking advantage of statistical multiplexing. This
is 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 does 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 64 kbit/s 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 or over provisioned.
Trafc from all PDTCHs on a carrier is packed efciently into a Versachannel of one
or more terrestrial timeslots associated with this carrier. Versachannel is dened as
the portion of the backhaul associated with an RTF that is used to carry TRAU frames
associated with the air timeslots congured 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.
Quality of Service (QoS)

{23956}
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), is provided for Interactive and Background
trafc classes. QoS for conversational and streaming trafc classes is not supported, however,
conversational and streaming trafc is allowed into the GPRS network and downgraded to
Interactive class and is not subject to further downgrade or pre-emption.
68P02900W21-R
1-15
GMR-01
Nov 2007
Quality of Service (QoS)
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 ensures that the subscribers receive the best possible
service specic to the types of applications used and specic to the type of tariff selected.
QoS dimensioning
The two most signicant factors that inuence quality of a service are:
Delay
Throughput
In R99 and beyond, four trafc classes are dened to accommodate the need for different levels
of these factors for different applications. These are as follows:
Conversational
Streaming
Interactive
Background
The BSS has internally dened additional trafc classes created by grouping similar PFC
characteristics. The internally dened trafc classes are as follows:
Short-Term Non-Negotiated Trafc (STNNT)
Pre-Admission PFC (PAP)
QoS disabled
As the specication for conversational and streaming is still evolving, the BSS is implementing
differentiation of service among interactive and background trafc classes. Requests to create
packet ows for streaming or conversational mode are treated as interactive trafc ows.
Support for streaming or conversational trafc class at the BSS is limited in its scope, that is,
streaming and conversational trafc classes get QoS of interactive trafc class when admitted.
However, the BSS does not make any guarantees regarding sustaining applications using the
streaming and conversational trafc classes.
QoS impacts on BSS

The QoS feature inuence the following BSS entities:
Gb interface
PFM procedures over the Gb interface are dened 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.
1-16
68P02900W21-R
GMR-01
Nov 2007
Improved Timeslot Sharing (ITS)
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 reect 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 user
congurable parameters for MTBR for each Trafc Class and Coding Scheme usage to
determine the maximum number of PDTCHs to assign to a PRP.
Improved Timeslot Sharing (ITS)

{23956}
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 switch rapidly between
Double Density modulation (GMSK) and Single Density modulation (8PSK). The power output is
not affected for GMSK and 8PSK. Thus, the EGPRS PDTCH can only be congured 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.
68P02900W21-R
1-17
GMR-01
Nov 2007
BSS planning overview
BSS planning overview
Introduction
A brief overview of the planning process is provided in this section.
Background information
Before planning, the required information is categorized into three main areas:
Trafc model and capacity calculations
Category of service
Site planning
Trafc model and capacity calculations

The following information is required to calculate the capacity required:
Trafc information (Erlangs/BTS) over desired service area
Average trafc 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
1-18
68P02900W21-R
GMR-01
Nov 2007
Background information
eMLPP impact on BSS equipment and capacity calculations

{24347}
With eMLPP feature, preferential service is provided for higher priority calls by pre-empting the
resource from lower priority calls when the system is under congestion. When planning radio
and terrestrial resources, the adequate resources require to be planned by treating all calls
equal without considering preemption. That is, BSS planning focuses on providing planning
steps and rules under normal trafc load without congestion, with certain capacity margin
planned for trafc surge or congestion, such as link provisioning based on 25% or 35% or 40%
signaling link utilization, or processor provisioning based on 70% utilization.
Therefore, BSS equipment planning disregards the eMLPP feature, and capacity or equipment
calculation formula is not updated for this 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 conguration in each category, sector against omni.
Frequency re-use scheme to meet trafc and C/I requirements.
Number of RF carriers in cell/sector to support trafc.
Grade of service of the trunks between the MSC/BSC, that is, Erlang B at 1%.
Grade of service of the trafc channels (TCH) between the MS and BTS, that is, Erlang
B at 2%.
Cell grid plan, a function of the following:

Desired grade of service or acceptable level of blockage.
Typical cell radio link budget.
Results of eld tests.
Site planning
The following information is required to plan each site.
Location of the BSC and BTSs.
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 specication.
68P02900W21-R
1-19
GMR-01
Nov 2007
Planning methodology
Diversity requirement, diversity doubles the number of Rx antennas and associated

equipment.
Redundancy level requirements (determined for each item).
Supply voltage.
Planning methodology
A GSM digital cellular system consists of several BSSs. The planning cycle begins with dening
the BSS cell, followed by the BTS(s), BSC(s), and the RXCDR(s).
Planning a BSS involves the following:
Select the conguration, omni or sectored and the frequency re-use scheme that satises
trafc, interference and growth requirements.
Plan all the BTS sites as follows:

Use an appropriate RF planning tool to determine the geographical location of sites
and the RF parameters of the selected terrain.
Determine which equipment affecting features are required at each site. For example,
diversity or frequency hopping.
Plan the RF equipment portion and cabinets for each BTS site.
Plan the digital equipment portion for each BTS site.
Plan the BSCs after the BTS sites are congured and determine the following:
Sites for each BSC.
Which BTSs are connected to which BSC.
How the BTSs are connected to the BSCs.
Trafc requirements for the BSCs.
Digital equipment for each BSC site.
Shelf, cabinets, and power requirements for each BSC.
Plan the remote transcoder (RXCDR) requirements and, if required, the subsequent
hardware implementation.
Plan the Packet Control Unit (PCU) for the desired packet data capacity for the system.
1-20
68P02900W21-R
GMR-01
Nov 2007
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
AMR
ARFCN
{23956} ARP
Advanced load management

Adaptive multi-rate
Absolute radio frequency channel number
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
BIB
BLER
Busy hour call attempts

Balanced line interface board
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)
BSU
Base station unit
BTC
Bus termination card

Continued
68P02900W21-R
1-21
GMR-01
Nov 2007
Acronym list
Table 1-2
Acronym list (Continued)

Acronym
Meaning
BTF
Base transceiver function
BTP
Base transceiver processor
BTS
Base transceiver station
BVC(I)
C/I
BSSGP virtual circuit (identier)

Carrier to interference ratio
CBC
Cell broadcast centre
CBF
Combining bandpass lter
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
DARBC
dB
Compact transceiver unit 2

Dynamic allocation of RXCDR to BSC
circuits
Decibel
DCF
Duplexed combining bandpass lter
DDF
Dual stage duplexed combining lter
DCS
Digital cellular system
DECT
Digital enhanced cordless telephony
DDM
Dual density mode
DHU
Dual hybrid combiner unit
DL
DLCI
Downlink
Data link connection identier
Continued
1-22
68P02900W21-R
GMR-01
Nov 2007
Table 1-2
Acronym list

Acronym
DLNB
Meaning
Dual low noise block
DPROC
Data processor
(D)RAM
(Dynamic) random access memory
DRCU
DRI
DRIM
Diversity radio control unit

Digital radio interface
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
e
E1
EAC
EDGE
EFR
EGDP
Dynamic network
Erlang
32 channel 2.048 Mbps span line
Enhanced auto-connect
Enhanced data rates for global evolution
Enhanced full rate
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
ePCU
Evolved PCU (Enhanced PCU)
{24347} eMLPP
FACCH
Enhanced multi-level precedence and

pre-emption
Fast access control channel
FEC
Forward error correction
FHI
Frequency hopping index
FM
Fault management
FMUX
FN
Fiber optic multiplexer (Horizonmacro)

Frame number
Continued
68P02900W21-R
1-23
GMR-01
Nov 2007
Acronym list
Table 1-2

Acronym
FOX
Meaning
Fiber 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)

GCLK
GDP(2)
GDS
Gb link
Generic clock
Generic digital processor (2)
GPRS data stream
GGSN
Gateway GPRS support node
GMLC
Gateway mobile location centre
GMM
GPRS mobility management
GMSK
Gaussian minimum shift keying
GOS
GPROC(n)
Grade of service
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
HCU
Hybrid combiner
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 or GSM), referring to the

channel rate
HR
Half rate (AMR or GSM), referring to the

speech codec
HSC
{23956} HSNI
Hot swap controller

Hopping sequence number interactive
Continued
1-24
68P02900W21-R
GMR-01
Nov 2007
Table 1-2
Acronym list

Acronym
IADU
{22404} IMRM
Meaning
Integrated antenna distribution unit
Intelligent multi-layer resource
management
IMSI
International mobile subscriber identity
INS
In service
IP
Internet protocol
IPL
Initial program load
IR
Incremental redundancy
ITS
Improved Timeslot Sharing
ISDN
Integrated services digital network
ISI
Inter symbol interference
ISP
Internet service provider
KSW(X)
LA
LAC
Kiloport switch (extender)

Link adaptation
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 amplier
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

Continued
68P02900W21-R
1-25
GMR-01
Nov 2007
Acronym list
Table 1-2

Acronym
MPROC
MS
MSC
MSI (-2)
{23956} MTBR
Meaning
Master processor
Mobile station
Mobile switching centre
Multiple serial interface (2)
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 (identier)
NSP
Network support program
NSS
Network subsystem
NSVC (I)
Network service layer virtual circuit

(identier)
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
PAR
Pre-admission PFC
Peak to average ratio
PBCCH
Packet broadcast control channel
PCCCH
Packet common control channel
PCH
Paging channel
PCI
Peripheral component interconnect
PCM
PCMCIA
Pulse code modulation

Personal computer memory card
international association
Continued
1-26
68P02900W21-R
GMR-01
Nov 2007
Table 1-2
Acronym list

Acronym
Meaning
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
PDU
Packet data trafc channel

Protocol data unit
{23956} PFC
Packet ow context
{23956} PFM
Packet ow management
PICP
Packet interface control processor
PIX
Parallel interface extender
PLMN
Public land mobile network
PMC
PCI mezzanine card
PNCH
Packet notication 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
RAU
Routing area update
RDB
Requirements database
Continued
68P02900W21-R
1-27
GMR-01
Nov 2007
Acronym list
Table 1-2

Acronym
RF
Meaning
Radio frequency
RLC
Radio link control
ROM
Read only memory
RRI
Radio refractive index
RSL
Radio signaling link
RTD
RLC transit delay
RTF
Radio transceiver function
RX (or Rx)
RXCDR
RXU
SACCH
SB
SCC
Receive
Remote transcoder
Remote transcoder unit
Slow access control channel
Stealing bit
Serial channel controller
SCCP
SS7 signaling connection control part
SCH
Synchronization channel
SCM
Status control manager
SCU
Slim channel unit
SD
SDCCH
Single Density
Stand alone dedicated control channel
SDM
Single density mode
SFH
Synthesizer frequency hopping
SGSN
Serving GPRS support node
SID
Silence descriptor
SLS
Signaling link selection
SM
Session management
SMLC
SMS
SNDCP
Serving mobile location centre

Short message service
Sub network dependent convergence
protocol
SS7
CCITT signaling system number 7
{23956} STNNT
Short-term non-negotiated trafc
STP
SURF
Shielded twisted pair

Sectorized universal receiver front end
(Horizonmacro)
Continued
1-28
68P02900W21-R
GMR-01
Nov 2007
Table 1-2
Acronym list

Acronym
SURF2
TBF
TCCH
Meaning
Sectorized universal receiver front end 2
(Horizon II macro)
Temporary block ow
Timing access control channel
TCH
Trafc 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
TS
TSW
TX (or Tx)
Transcoder rate adaptation unit

Timeslot
Timeslot switch
Transmit
UE
User equipment
UL
Uplink
UMTS
Universal mobile telecommunication

system
USF
Uplink state ag
UTP
Unshielded twisted pair
UTRAN
{23769} VersaTRAU
UMTS radio access network

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
Nov 2007
1-29
GMR-01
Acronym list
1-30
68P02900W21-R
GMR-01
Nov 2007
Chapter
2
Transmission systems
This chapter contains possible logical interconnections and descriptions of BSS interconnections.
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-25
68P02900W21-R
Nov 2007
2-1
GMR-01
BSS interfaces
BSS interfaces
Introduction
Figure 2-1 and Table 2-1 indicate the type of interface, rates, 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
MS
(LAPDm)
Abis interface
A interface
BSC
BTS
RXCDR
MTL (C7), XBL

(LAPD)
OML (X.25)
RSL (LAPD)
SGSN
GDS
Gb OPTION A
Gb OPTION C
PCU
CBL
X.25
(LAPB)
CBC
ti-GSM-BSS_interfaces-00005-ai-sw
Table 2-1
BSS interface
Interface
From/To
Signaling by
Air
MS-BTS
RACH, SDCCH,
SACCH, FACCH
Rate
Using
LAPDm
E1links
Abis (Mobis)
BTS - BSC
RSL
16/64 kbit/s
LAPD
Continued
2-2
68P02900W21-R
GMR-01
Nov 2007
Introduction
Table 2-1 BSS interface (Continued)

Interface
From/To
Signaling by
Rate
Using
BSS - MSC
MTL (OML, CBL)
64 kbit/s
C7
RXCDR - BSC
XBL
16/64 kbit/s
LAPD
MSC - OMCR
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 kbit/s
LAPD
68P02900W21-R
2-3
GMR-01
Nov 2007
Interconnecting the BSC and BTSs
Introduction
Network topology is specied in terms of the path(s) between the BSC and the BTS sites. A
path is determined by E1 circuits, and possible intervening BTS sites are used to provide the
connection. Transcoding is performed at the BSC or RXCDR.
Interconnection rules
The following rules must be observed while interconnecting a BSC and BTSs:
The BSC shares 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 needs two 64 kbit/s timeslots on an E1 circuit. An RTF is congured
as half rate capable, which means it can support AMR half rate and/or GSM half rate. Once
an RTF is congured 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 GSM half rate) 8 kbit/s subrate switching is not available. For example, if
16 kbit/s is used for the backhaul, then the carrier unit assigned to that RTF needs four
64 kbit/s timeslots on the E1 circuit (Refer to the NOTE).
In a redundant connection, each carrier unit needs 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 dened as- A carrier which is assigned an RTF
congured as (AMR or GSM) half rate capable, and 8 kbit/s subrate switching is not
available (for example, 16 kbit/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 specic and is congured 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 must be terminated on different MSIs.
In a closed loop daisy chain, the primary RSLs for all BTS sites are 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 is always equipped on the multiple serial interface
link (MMS) equipped in CAGE 15, slot 16, port A. The secondary RSL at each BTS site is
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.
2-4
68P02900W21-R
GMR-01
Nov 2007
Interconnection rules
When discussing the BSC or RXCDR, cage is a legacy term used in BSS
commands that has been replaced by shelf in this manual. That is, cage and
shelf mean the same thing.
Additional backhaul bandwidth is required to support GPRS trafc using CS3/CS4 coding
schemes. Each timeslot, on a CS3/CS4 capable carrier, needs 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 trafc using MCS1-MCS9

coding schemes. Each non-signaling timeslot, {23769} shares the Versachannel backhaul
associated with the particular carrier. Backhaul is provisioned based on expected EGPRS
usage and recommendation in Table 8-1 of Chapter 8 PCU upgrade for BSS. Versachannel
is dened as the portion of the RTF backhaul that is used to carry the data for the air
timeslots congured as PDTCHs, at any given time.
The following rules must be observed while interconnecting InCell and M-Cell equipment:
Recongure the InCell BTS to have integral sectors in the cabinet.
Install M-Cell cabinets to serve the remaining sectors.
Daisy chain the M-Cell E1 links to the BSC.
68P02900W21-R
2-5
GMR-01
Nov 2007
Network topology
Network topology
Introduction
The operator can specify the trafc that is to use a specic path. A direct route between any
two adjacent sites in a network can 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 1
BTS 1
BTS 5
BTS 2
BTS 6
BTS 3
BTS 7
BTS 4
BTS 8
BTS 9
ti-GSM-Network_topologies-00006-ai-sw
2-6
68P02900W21-R
GMR-01
Nov 2007
Star connection
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 signaling links per Horizon II macro BTS site (maximum of four per path).
Six RSL signaling links per Horizonmacro or M-Cell BTS site (maximum of two per path).
An alternative path is reserved for voice/data trafc 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 signaling link has a single path. When redundant paths exist, redundant signal links
are required, and the signaling is load shared over these links. In case of a path failure, the
trafc can be rerouted, but the signaling links go out of service, and the load is carried on
the redundant links.
Star connection
A star connection is dened 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 4
BTS 2
BTS 1
BTS 5
BSC
MSC
BTS 7
BTS 9
BTS 8
ti-GSM-Star_connection-00007-ai-sw
68P02900W21-R
2-7
GMR-01
Nov 2007
Daisy chain connection
A star connection requires more MSI cards at the BSC than daisy chaining, for the same number
of BTS sites. The star connection allows for a greater number of carrier units per BTS site. An
E1 circuit provides for one signaling link, along with 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 congured
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 dened in the section Interconnecting the BSC
and BTSs on page 2-4.

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 efcient utilization of
the E1 circuit and interconnects smaller sites back to the BSC.
2-8
68P02900W21-R
GMR-01
Nov 2007
Daisy chain planning
The daisy chain can 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 4
BTS 2
BTS 10
DAISY CHAIN
CLOSED LOOP
BTS 1
BRANCH OF THE
DAISY CHAIN
BTS 6
BTS 5
BSC
MSC
DAISY CHAIN
CLOSED LOOP
BTS 1 1
BTS 7
BTS 9
BTS 8
SINGLE MEMBER
DAISY CHAIN, A S TAR
ti-GS M-Clos e d_loop_ope n_e nde d_da is y_cha in-00008-a i-s w
The closed loop version provides for redundancy while the open ended version does not.
Longer daisy chains (ve or more sites) cannot meet the suggested round-trip delay.

The introduction of multiple E1 circuits and branches increases the complexity of the network
topology. Since the network can contain multiple E1 circuits, branches, multiple paths over the
same E1 circuit, and closed loop interconnections, each E1 circuit is planned individually.
68P02900W21-R
2-9
GMR-01
Nov 2007
Simple daisy chain

A daisy chain without branches and with 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 rst BTS in the chain. A
simple daisy chain is shown in Figure 2-5.
Figure 2-5 Simple daisy chain
Tx
Rx
BSC
Tx
Rx
Rx
Tx
Rx
BTS 1
Rx
Tx
BTS 2
Tx
Tx
USED IN CLOSED LOOP
CONNECTION ONL Y
Rx
Tx
Rx
Rx
Tx
BTS 3
Tx
Rx
Rx
Tx
BTS 4
BTS X
ti-GS M-S imple _da is y_cha in-00009-a i-s w
The capacity of a closed loop single E1 circuit daisy chain is the same as that of a daisy
chain. The closed loop daisy chain has redundant signaling 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:
{23769}
Where:
Is:
Minimum number of E1 links required (rounded up to an integer).
Total number of carriers in the daisy chain with EGPRS enabled.
Total number of carriers in the daisy chain with GPRS CS3 and CS4
enabled.
the total number of carriers in the daisy chain with GPRS CS1 and
CS2 enabled, and GSM voice only carriers where the half rate
exception case does not apply.
Continued
2-10
68P02900W21-R
GMR-01
Nov 2007
Where:
Is:
{23769} Value of rtf_ds0_count for the RTF.
Total number of GSM voice only carriers in the daisy chain where
the half rate exception applies.
Number of BTS sites in the chain.
Example
Consider a daisy chain with 3 BTSs, each with 1 GSM voice carrier, 1 CS3/4 enabled carrier and
1 EGPRS enabled carrier for which the 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) is shown:
Two E1s are required to support daisy chaining between the BTSs and the BSC.
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
Tx
Rx
Rx
Tx
BSC
Daisy chain with branch
Tx
Rx
Rx
Tx
Rx
BTS 1
BTS 2
Tx
Tx
USED IN CLOSED LOOP
CONNECTION ONL Y
Rx
Tx
Rx
Rx
Tx
BTS 3
Tx
Rx
Rx
Tx
BTS 4
BTS X
Rx
BTS Y
Tx
ti-GS M-Da is y_cha in_with_bra nch-00010-a i-s w
A branch can have multiple BTS sites on it. A branch can be closed, in which case there are
redundant signaling links on different E1 circuits. In a closed loop, which needs redundant
signaling links for each BTS site, with an open branch, the E1 circuit to the branch needs
to carry redundant signaling links.
68P02900W21-R
2-11
GMR-01
Nov 2007
Aggregate Abis
Aggregate Abis
This is an option designed to allow greater exibility while planning the network. It can also
help reduce leasing costs of E1 links by optimizing link usage over the greatest distance
between a BSC and a 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 each need their own
dedicated E1 link, this greatly under utilizes each link capacity.
If the geographical locations of the sites and the distances of the E1 links are advantageous, it is
possible to initially send all the trafc channels for every site over one E1 link to the third party
multiplexer and then distribute them over much shorter distances to the required sites.
If the distance between the BSC and the multiplexer site is sufciently large, this results in
signicant leasing cost savings compared to the original conguration. There are two diagrams
illustrating the following (Figure 2-7) and subsequent (Figure 2-8) scenarios.
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
RTF trafc channels. Most link providers lease timeslots in contiguous blocks (that is, there are
no gaps between timeslots). Under the existing timeslot allocation scheme this 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 that are directly connected to the new
aggregate service; the existing algorithm for allocating timeslots is used on the other links.
Figure 2-7 Typical low capacity BSC/BTS conguration
BSC
5x64 kbit/s TIMESLOTS USED
26x64 kbit/s TIMESLOTS UNUSED

BTS
BTS
TWO CARRIER
ONE RSL
TWO CARRIER
ONE RSL
BTS
TWO CARRIER
ONE RSL
ti-GSM-Low_capacity_BSC/BTS_configuration-0001
2-12
1-ai-sw
68P02900W21-R
GMR-01
Nov 2007
Aggregate Abis
Figure 2-8 Example using a switching network
BSC
MORE EFFICIENT USE OF

LONGEST E1 LINK

TWO CARRIER
ONE RSL
BTS
TWO CARRIER
ONE RSL

E1
MULTIPLEXER


BTS

BTS
BTS
TWO CARRIER
ONE RS L
TWO CARRIER
ONE RSL
ti-GS M-s witching_ne twork-00012-a i-s w
The new software allocates timeslots from timeslot 1 upwards. The RSLs are allocated rst 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 are presented. Also, RSLs
must be equipped rst on a per site basis to coincide with the default timeslots for 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.
68P02900W21-R
2-13
GMR-01
Nov 2007
Aggregate Abis
Figure 2-9 Timeslot allocation using new and old algorithms
NEW ALGORITHM
RSL1
6
RSL2
1
RTF1
RTF3
2
7
RTF1
3
RTF3
8
RTF2
4
9
RTF4
RTF2
5
RTF4
10
11
12
13
14
15
RSL3
RTF5
RTF5
RTF6
RTF6
TWO CARRIER
ONE RSL
1
2
3
4
5
RSL1
RTF1
RTF1
RTF2
RTF2
NEW
ALGORITHM
13
13
02
92
8
ALLOCATION
UNAFFECTED
16
17
18
19
20
ALLOCATION AFFECTED
BTS 1
ORIGINAL
ALGORITHM
BSC
RSL4
RTF7
RTF7
RTF8
RTF8
ALLOCATION
AFFECTED
1
2
3
4
5
RSL3
RTF5
RTF5
RTF6
RTF6
NEW ALGORITHM
RSL3
RTF5
RTF5
RTF6
RTF6
6
7
8
9
10
RSL4
RTF7
RTF7
RTF8
RTF8
E1
MULTIPLEXER
BTS 3
ALLOCATION AFFECTED
NEW
ALGORITHM
RSL2
1
RTF3
2
RTF3
3
4
RTF4
RTF4
5
ALLOCATION
AFFECTED
BTS 2
ORIGINAL
ALGORITHM
RSL4
13
RTF7
13
02
RTF7
RTF8
92
RTF8
8
ALLOCATION
UNAFFECTED
BTS 4
ti-GS M-Time s lot_a lloca tion-00013-a i-s w
Similar problems are encountered while equipping redundant RSL devices onto paths containing
aggregate services. The new method of allocating timeslots when connecting to an aggregate
service is from timeslot 1 upwards, so there is no way of reserving the default download RSL
timeslot. This gives rise to a situation where the default RSL timeslot is already allocated to
another device, for example RTF.
To avoid this situation, the primary and redundant RSLs can be equipped rst (in an order that
results in the correct allocation of default RSL timeslots), or reserve the default download RSL
timeslot so that it is correctly allocated when the primary or redundant RSL is equipped.
If the site needs to be expanded in the 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.
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 reports the local alarm, but
the remote alarm only goes to the third party aggregate service supporting the E1 link.
A situation may arise 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.
2-14
68P02900W21-R
GMR-01
Nov 2007
Aggregate Abis
Figure 2-10 shows a possible network conguration using several switching networks.
Figure 2-10 Alternative network conguration with E1 switching network
BSC
E1
MULTIPLEXER
BTS
BTS
BTS
E1
MULTIPLEXER
BTS
BTS
BTS
BTS
BTS
E1
MULTIPLEXER
BTS
BTS
E1
MULTIPLEXER
BTS
BTS
ti-GSM-Alternative_network_configuration-00014-ai-sw
Restrictions/limitations
The ability to nail path timeslots along a link containing an E1 switching network is supported.
The operator is 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 synchronizes to it and not to the uplink GSM network entity (BTS, BSC).
68P02900W21-R
2-15
GMR-01
Nov 2007
RTF path fault containment

Each transceiver at a BTS needs a receive/transmit function to be enabled which noties the
transceiver about various operating parameters which can be used. These include the ARFCN,
type of carrier, and primary/secondary path, among others. The path is of utmost importance.
An RTF can 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, including RTFs that are in the same cell.
One path is designated as the primary, the other as the secondary. In the event of primary path
failure, the RTF selects the secondary path, and the carrier remains in call processing. If all the
paths to one RTF fail, the entire 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 all paths to one RTF fail, 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 timeslots are unavailable, the call is
released. In addition, the timeslots on the transceiver of the failed path are barred from trafc
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 trafc.
Advantages
The customer can save on timeslot usage by using this feature, and removing any redundant
paths that are normally equipped to manage path failure. Figure 2-11 shows the conventional
redundant set-up, which needs four extra timeslots to provide for redundant paths. Figure 2-12
shows the alternative conguration, where if one RTF path fails, call processing continues
through the other path, although with reduced capacity. This conguration only needs 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.
The customer has to weigh up the cost saving advantages of the alternative conguration
against the reduced capacity in the event of failure of an RTF path.
2-16
68P02900W21-R
GMR-01
Nov 2007
Figure 2-11 A conguration with a BTS equipped with two redundant RTFs
BSC
RTF1 EQUIPPED
ON P ATH 1
(2 TIMESLOTS)
RTF1 EQUIPPED
ON P ATH 2
(2 TIMESLOTS)
BTS 3
BTS 1
RTF2 EQUIPPED
ON P ATH 1
(2 TIMESLOTS)
RTF2 EQUIPPED
ON P ATH 2
(2 TIMESLOTS)
BTS 2
ti-GS M-BTS _with_two_re dunda nt_RTFs -00015-a i-s w
Figure 2-12 A conguration with a BTS equipped with two non-redundant RTFs
BSC
RTF1 E QUIPP ED
ON PATH 2
(2 TIMES LOTS )
RTF2 EQUIPP ED
ON PATH 1
(2 TIMESLOTS )
BTS 3
BTS 1
BTS 2
ti-GS M-BTS _with_two_non_re dunda nt_RTFs -00016-a i-s w
68P02900W21-R
2-17
GMR-01
Nov 2007
16 kbit/s RSL
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.
Before 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 trafc channels. The two 64 kbit/s
timeslots dedicated to the trafc channels can normally accommodate eight trafc channels.
In the case of a single carrier site, it is not possible to use all eight trafc 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. The TSW at the BTS routes the trafc
channels from the two specied timeslots on the Abis interface to the dedicated transceiver
for transmission.
The trafc channel on the Abis interface corresponding to the timeslot 0 on the air interface
is unused and is available to carry the signaling trafc. Therefore one 16 kbit/s subchannel
remains unused on the Abis interface, which is a waste of resources.
With the introduction of the 16 kbit/s RSL, it is possible to place it on this unused subchannel
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 the 7.95 codec rate for AMR 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 ve to four. (This is not shown in the table and gures.)
Figure 2-13 (fully-equipped RTF) and Figure 2-14 (sub-equipped RTF) show the eight types of
RTF which are possible using the previously described options. They are listed in Table 2-2.
Table 2-2
Type
RTF types
Options
A fully equipped BCCH RTF with an associated 16 kbit/s RSL.
A fully equipped BCCH RTF with no associated 16 kbit/s RSL.
A fully equipped non-BCCH RTF with an associated 16 kbit/s RSL.
A fully equipped non-BCCH RTF with no associated 16 kbit/s RSL.
A sub-equipped BCCH RTF with an associated 16 kbit/s RSL.
A sub-equipped BCCH RTF with no associated 16 kbit/s RSL.
A sub-equipped non-BCCH RTF with an associated 16 kbit/s RSL.
A sub-equipped non-BCCH RTF with no associated 16 kbit/s RSL.
2-18
68P02900W21-R
GMR-01
Nov 2007
16 kbit/s RSL
Fully equipped RTF
Figure 2-13 Fully equipped RTF
FULLY EQUIPPED R TF
BCCH
NON-BCCH
16 kbit/s
BTS only
16 kbit/s
BTS only
ASSOCIATED
16 kbit/s RSL
NO
ASSOCIATED
16 kbit/s RSL
Configuration
ASSOCIATED
16 kbit/s RSL
3
NO
ASSOCIATED
16 kbit/s RSL
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 traf
fic.
ti-GS M-Fully_e quippe d_RTF-00017-a i-s w
68P02900W21-R
2-19
GMR-01
Nov 2007
16 kbit/s RSL
Sub-equipped RTF
Figure 2-14 Sub-equipped RTF
SUB-EQUIPPED R TF
BCCH
NON-BCCH
16 kbit/s
BTS only
16 kbit/s
BTS only
ASSOCIATED
16 kbit/s RSL
NO
ASSOCIATED
16 kbit/s RSL
ASSOCIATED
16 kbit/s RSL
Configuration
NO
ASSOCIATED
16 kbit/s RSL
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 traf
fic.
ti-GS M-S ub_e quippe d_RTF-00018-a i-s w
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 support a mix of both fully equipped and sub-equipped RTFs.
2-20
68P02900W21-R
GMR-01
Nov 2007
16 kbit/s XBL
A ROM download is carried out over a 64 kbit/s RSL, even at a site designated as 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 can only be congured on CCITT subchannel 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 the current 64 kbit/s to 16 kbit/s. This frees
three 16 kbit/s subchannels on the E1 64 kbit/s timeslot and enables them to be used as TCHs.
A BSC can interconnect up to ten RXCDRs and vice-versa. A total of 20 XBL links are deployed
in any conguration. An XBL can be congured without restriction in any timeslot.
It is possible to select a rate of 16 kbit/s or 64 kbit/s on a XBL basis. Therefore, there can
be two different rates at the same BSC to RXCDR, although this is not considered a typical
conguration. As a result of the introduction of the 16 kbit/s RSL, there is no reduction in the
processing capacity of the BSC or the RXCDR.
Figure 2-15 demonstrates XBL utilization.
Figure 2-15 XBL utilization
BSC 1
XBL
XBL
BSC 2
XBL
XBL
BSC 3
XBL
XBL
BSC 9
XBL
XBL
BSC 10
XBL
XBL
RXCDR
ti-GS M-XBL_utiliza tion-00019-a i-s w
68P02900W21-R
2-21
GMR-01
Nov 2007
Dynamic allocation of RXCDR to BSC circuits (DARBC)
In Figure 2-15 a maximum of two XBLs can be utilized between the BSC and
XCDR of either 64 kbit/s or 16 kbit/s on the E1 link.
A maximum of ten BSCs can be connected to an RXCDR or vice versa.

The DARBC feature introduces fault management for call trafc 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, fault management of the
Ater channels is not possible. All Ater and CIC information must be manually veried 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 a mode which can be selected by the operator. This mode refers to a BSC in which Ater
channels are allocated and released dynamically as resources are provisioned, unprovisioned, or
while handling a fault condition. Auto-connect mode provides fault tolerance along with the
call processing efciency of the backwards compatibility mode. This is the recommended mode
of operation for the BSC.
Backward compatibility mode
Backward compatibility mode cannot be used in conjunction with the AMR or GSM
half rate features. Auto-connect or enhanced auto-connect mode must be specied.
This is a user 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. It is intended only to provide an upgrade path. Once both the BSC and RXCDR are
upgraded, the use of auto-connect mode is recommended.
2-22
68P02900W21-R
GMR-01
Nov 2007
While upgrading the network, if the BSC is upgraded before the RXCDR, backwards
compatibility mode must be used for the corresponding AXCDR.
Before the introduction of this feature, all Ater channels were statically assigned and use of
XBL links was not mandatory. Currently, if an operator decides to use the auto-connect, it is
necessary to equip XBL links on the RXCDR and BSC. If XBLs are not equipped, and the AXCDR
is operating in the auto-connect mode, all CICs at the BSC associated with that AXCDR are
blocked and call trafc does not go to that AXCDR.
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 must consider when planning and provisioning the BSC/RXCDR
network.
EAC mode is introduced with the AMR feature and also applies to the {22064} GSM half rate
feature. It takes advantage of the use of half rate trafc channels where only 8 kbit/s backhaul
to the RXCDR is required. EAC mode is user enabled across a BSC - RXCDR interface and only
provides benets 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 xed position on the Ater interface. Rather, a CIC
can be considered 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 allocates 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. XBL links are required between the
BSC and RXCDR as in the auto-connect mode.
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 to be false, some capacity is
lost as CICs are unusable due to a 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 automatically reverts to
auto-connect mode even if EAC is enabled). EAC mode also needs XBL bandwidth. Use of EAC
mode (specically 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 can be handled by the Ater
channels, there is a possibility that a call assignment may fail because Ater channels are
unavailable. To prevent such assignments from failing, the BSC provides a facility that
automatically blocks at the MSC, all idle CICs that go through a particular RXCDR when the
number of available Ater channels to RXCDR reaches a congurable threshold. The operator
controls such thresholds through the cic_block_thresh and cic_unblock_thresh values. These
thresholds are used to maintain Ater resources, to ensure that resources are available when a
fault occurs and also to balance the call load.
68P02900W21-R
2-23
GMR-01
Nov 2007
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.
2-24
68P02900W21-R
GMR-01
Nov 2007
Managed HDSL on micro BTSs
Introduction
Managed HDSL brings the benets of full OMC-R management to those products that support
integrated HDSL technology. Specically, it allows remote conguration, status, control, and
quality of service information to be handled by the OMC-R. External HDSL modems congured
as slave devices can 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 the
introduction of this feature, the initial basic version of the product is no longer supported.
Horizonmicro2 microcell BTSs (and Horizoncompact2 macrocell BTSs) shipped

after 31st December 2001 are not tted 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 ofce can provide assistance before 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) can 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.
Certain types of cables are known to perform suitably in HDSL applications, provided
they are correctly installed, and the guidelines for selection and installation are
observed.Recommendations for the types of cables are as follows:
68P02900W21-R
2-25
GMR-01
Nov 2007
Integrated HDSL interface
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 following kinds of cables should be avoided for HDSL applications:
Twisted quad cable is unsuitable for use in HDSL applications.
A drop wire that consists of two parallel conductors with supporting steel cable works with
HDSL but since it is not twisted, it provides little immunity from noise, and is therefore
not recommended.
An information cable which is typically made of non-twisted, multicore construction, for

example, ribbon cable, is not recommended.
HDSL cable installation

If cabling does not exist between two end sites, the guidelines to be followed for the installation
of cables are given:
The conductor pairs 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 the tip and the ring should be greater than 1 M ohm (at SELV
voltage levels).
The isolation between the tip and earth should be greater than 1 M ohm (at SELV voltage
levels).
The isolation between the ring and earth should be greater than 1 M ohm (at SELV voltage
levels).
HDSL range
HDSL range is affected by many factors, which should be taken into account when planning
the system.
2-26
68P02900W21-R
GMR-01
Nov 2007
General HDSL guidelines
Microcell systems can have longer distances, typically 2 km or so, because of their
different link error requirements.
The following factors reduce the available distances:

Bridge gaps add unwanted loads onto the cables
Gauge changes add unwanted signal reections
Small gauge cables increase the signal attenuations
Other noise sources
HDSL is specied not to affect other digital subscriber link systems and voice trafc.
However, standard E1 trafc affects (and is affected by) HDSL systems running in
the same cable binder, if unshielded from each other.
General HDSL guidelines

Conversion of E1 to HDSL at a site away from the BSC needs either an external modem or a
microsite. It is better to utilize the microsite to carry out this conversion (refer to Figure 2-16).
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
congured as either E1 or HDSL through 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-27
GMR-01
Nov 2007
Microcell system planning
Figure 2-16 Conversion of E1 to HDSL links by modem and microsite

E1 LINK
HDSL
SLAVE
EXTERNAL
MODEM
Horizon micro2
E1 LINK
E1 LINK
BSC
Horizon micro2
E1 LINK
SLAVE
HDSL
EXTERNAL
MODEM
HDSL
Horizon micro2
Horizon micro2
BTS
HDSL
E1 LINK
Horizon macro
HDSL
HDSL
Horizon micro2
Horizon micro2
Horizon micro2
M - MASTER
S - SLA VE
ti-GS M-Conve rs ion_of_E1_to_HDS L_links -00020-a i-s w

Network congurations 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
BSC
Microcell daisy chain network conguration
E1 LINK
SLAVE
EXTERNAL
MODEM
M - MASTER
S - SLA VE
HDSL
HDSL
Horizon micro2
Horizon micro2
HDSL
Horizon micro2
ti-GS M-Microce ll_da is y_cha in_ne twork-ooo21-a i-s w
2-28
68P02900W21-R
GMR-01
Nov 2007
Star conguration
Figure 2-18 shows a BSC which is connected to an external modem, which then connects from
its slave port to the master port of a Horizonmicro2. In this conguration, an external modem is
used every time a link to a Horizonmicro2 is used, hence the star formation.
Figure 2-18 Microcell star network conguration
E1 LINK
SLAVE
HDSL
EXTERNAL
MODEM
E1 LINK
BSC
SLAVE
Horizon micro2
HDSL
EXTERNAL
MODEM
E1 LINK
SLAVE
Horizon micro2
HDSL
EXTERNAL
MODEM
Horizon micro2
M - MASTER
ti-GS M-Microce ll_s ta r_ne twork_configura tion-00022-a i-s w
E1 link
In Figure 2-19, an E1 link is used from the BSC to the rst 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 conguration using E1/HDSL links
E1 LINK
S
Horizon micro2
HDSL
Horizon micro2
HDSL
M
Horizon micro2
BSC
M - MASTER
S - SLA VE
ti-GS M-Microce ll_configura tion_us ing_E1/HDS L_links -00023-a i-s w
68P02900W21-R
Nov 2007
2-29
GMR-01
2-30
68P02900W21-R
GMR-01
Nov 2007
Chapter
3
BSS cell planning
When planning a mobile telephone system, the aim is to create a communications network that
fulls the following requirements:
Provides the desired capacity
Offers good frequency efciency
Implemented at low cost
High grade service
These requirements, when analyzed, actually conict with one another. Therefore, the operating
network is always a solution achieved through compromise. The cost of different network
congurations can vary considerably. From an engineering point of view, it would be worthwhile
to use efcient solutions despite high costs. However, a mobile telephone network is so huge
an investment that the nancial factors are always going to limit the possibilities. The effect
of limited funds is particularly obvious during the rst stage of the network. Consequently,
economical planning is a condition for giving the best possible service from the onset.
The use of the GSM900, EGSM900, and DCS1800 frequency bands create many
propagation-based problems. As the channel characteristics are not xed, design challenges
and impairments arise. These impediments must be dealt with to protect MS telephone users
from experiencing excessively varying signal levels and lack of voice quality.
It is important to predict the RF path loss between the BTS and the MS within the coverage area
in different types of environment. Knowledge of the transmitter and receiver antenna heights,
nature of the environment, and terrain variations is essential.
When planning a network, there are several major factors to be considered. These are described
in the following topics:
Planning tools on page 3-3
GSM frequency spectrum on page 3-4
Trafc capacity on page 3-8
Adaptive multi-rate (AMR) on page 3-10
{22064} GSM half rate on page 3-14
Propagation effects on GSM frequencies on page 3-17
68P02900W21-R
Nov 2007
3-1
GMR-01
Frequency re-use on page 3-43
Overcoming adverse propagation effects on page 3-49
Subscriber environment on page 3-99
Microcellular solution on page 3-103
Frequency planning on page 3-107
{22879} Inter-radio access technology (2G-3G) cell reselection and handovers on page
3-113
Call model parameters for capacity calculations on page 3-116
Control channel calculations on page 3-119
GPRS/EGPRS trafc planning on page 3-140
GPRS/EGPRS network trafc estimation and key concepts on page 3-141
GPRS/EGPRS air interface planning process on page 3-163
3-2
68P02900W21-R
GMR-01
Nov 2007
Planning tools
Planning tools
Introduction
It is essential to make many calculations at regular intervals from the BTS to predict the signal
strength in a cell area. The smaller the interval, the more accurate is the propagation model. In
addition, calculations should 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, which is time
consuming, but for the intervention of the software-planning tool.
The planning tool 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 required to provide an accurate picture of
the propagation paths of the cell.
Several planning tools are available in the market, such as Netplan or Planet, and it is up to the
operators to select the tool(s) that suit them best.
Check the gures by practical measurements after the calculation and implementation of the
cell. This is because, with all the variable factors in propagation modeling, an accuracy of
80% is considered excellent.
68P02900W21-R
3-3
GMR-01
Nov 2007
GSM frequency spectrum
GSM frequency spectrum
GSM900 frequency spectrum

The original GSM frequency spectrum was allocated in 1979. This consisted of two subbands 25
MHz wide. The frequency range is as follows:
Uplink range: 890 MHz to 915 MHz
Downlink range: 935 MHz to 960 MHz
The uplink frequencies (mobiles transmitting to the BTS) are 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. One of the
pair is allocated for uplink and one for the downlink. Each subband 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 has one frequency to transmit 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. 124 ARFCNs
are allocated to the various network users. These ARFCNs are 1 to 124 inclusive.
More frequencies were allocated to the GSM as they became available to provide for future
network expansion. An extra 10 MHz was added on to the two GSM bands and this is known as
Extended GSM (EGSM). The EGSM frequency range is as follows:
This allows another 50 ARFCNs to be used, bringing the total to 174. These additional ARFCNs
are 975 to 1023 inclusive.
The original Phase 1 MSs can only work with the original GSM frequency range and it
needs a Phase 2 MS to take advantage of the extra ARFCNs.
The operator cannot guarantee that the network has a signicant number of Phase 2 MSs.
Care should be taken when using EGSM frequencies not to make holes in the network for
Phase 1 MSs.
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 modied frequency range is as follows:
3-4
68P02900W21-R
GMR-01
Nov 2007
Absolute radio frequency channel capacity
This provides 374 ARFCNs with a frequency separation of 95 MHz between the uplink and
downlink frequencies. In the UK, these ARFCNs are shared between the four network users
(refer to Figure 3-1). Two of these network users, 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.
Digital Enhanced Cordless Telephony (DECT) uses the part at the top of the band.
Figure 3-1 UK network users

Downlink
Uplink
DECT
178 5MHz
178 1.5MHz
1880MHz
DECT
1876.5MHz
Ora nge
Orang e
T-mobile
T-mobile
172 1.5MHz
1816.5MHz
Voda fone /O 2
Voda fone /O 2
171 0MHz
1805MHz
ti-GSM-UK_network_users-00124-ai-sw
Absolute radio frequency channel capacity

Each RF carrier supports 8 time division multiplexed physical channels and each of these is
capable of supporting speech or signaling information (refer to Figure 3-2). When AMR half rate
or {22064} GSM half rate are enabled, each timeslot is divided into 2 subchannels, 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 supports a maximum of 16 physical channels.
68P02900W21-R
3-5
GMR-01
Nov 2007
Modulation techniques and channel spacing
Figure 3-2
1
BTS
Eight TDMA timeslots per RF carrier

3
Maximum 24 ca rriers for

Horizonma cro a nd M-Ce ll6
Maximum 25 ca rriers for BTS 6
ti-GSM-Eight_TDMA_timeslots_per_RF_carrier-00125-ai-sw

The modulation techniques 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 lter. The lter 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 modied envelope shape at the output of the modulator. The bandwidth of this
envelope is narrower than that of a comparable one produced from non-ltered data. With
each modulating carrier occupying a narrower bandwidth, more efcient use can be made
of the available overall bandwidth.
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 ltered to ensure that GSM
spectrum mask is preserved. This lter is a linearized GMSK pulse, that is, the main component
in a Laurant decomposition of the GMSK modulation (refer to 3GPP TS 05.04 V8.4.0).
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 ltering.
The signal therefore overlaps into surrounding frequencies, as illustrated in Figure 3-3.
3-6
68P02900W21-R
GMR-01
Nov 2007
Figure 3-3 Modulation techniques and channel spacing

-10 dB P OINT
CHANNEL 1
CHANNEL 2
CHANNEL 3
dB
0
-10
-20
-30
-40
-50
-60
-70
200 kHz
ti-GSM-Modulation_techniques_and_channel_spacing-00126-ai-sw
If two carriers from the same or adjacent cells are allocated adjacent frequencies or channel
numbers, they interfere with each other because of the described overlapping. This interference
is an unwanted signal noise. All noise is cumulative, so starting with a large amount by using
adjacent channels our wanted signal soon deteriorates 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
possesses approximately the same spectrum mask) is considerably wider than the 200 kHz
channel spacing specied by GSM. At the channel overlap point, the signal strength of the
adjacent channel is only -10 dB the wanted signal. While this falls within the minimum carrier
to interference ratio of 9 dB, it is signicant and must be planned around so that allocation of
adjacent frequencies in adjacent cells never occurs.
One other consideration about channel spacing is when using combiners. If a cavity-combining
block is used, the frequencies for combining should be separated by at least three ARFCNs
else 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. The
source of interference becomes more difcult to locate as they would not necessarily be a
problem to the home cell.
68P02900W21-R
3-7
GMR-01
Nov 2007
Trafc capacity
Trafc capacity
Dimensioning
One of the most important steps in cellular planning is system dimensioning. Some idea of the
projected usage of the system must be obtained (for example, the number of people wishing to
use the system simultaneously) to dimension a system correctly. This means trafc engineering.
Consider a cell with N voice channels; the cell is therefore capable of carrying N individual
simultaneous calls. The trafc ow is dened as the average number of concurrent calls carried
in the cell. The unit of trafc intensity is the Erlang. The trafc dened in this way can be
thought of as a measure of the voice load carried by the cell. The maximum carried trafc in a
cell is N Erlangs, which occurs when there is a call on each voice channel all the time.
If during a time period T (seconds), a channel carrying trafc is busy for t (seconds), then the
average carried trafc, in Erlangs, is t/T. The total trafc carried by the cell is the sum of the
trafc 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 trafc channels or trunks required or a given grade of service and given offered
trafc. There are times when a call request is made and all the 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 trafc is less than the offered trafc. If a call is blocked, the
caller can try again within a short interval.
If there is an absence of blocking, repeated call attempts increase the offered trafc the
level. Because of this effect, the notion of offered trafc is somewhat confusing. However, if
the blocking probability is small, ignore the effect of repeated call attempts and assume that
the blocked calls are abandoned.
The number of calls handled during a 24-hour period varies considerably with time. There are
two peaks during weekdays, 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
does. From the hour with the least trafc to the hour with the greatest trafc, the variation can
exceed 100:1.
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
should be taken into account. There are a set of common denitions to describe this busy
hour trafc loading.
Busy Hour: The busy hour is a continuous period during which trafc volume or number of
call attempts is the greatest.
Peak Busy Hour: The busy hour each day, it is not usually the same over some days.
Time Constant Busy Hour: The one-hour period starting at the same time each day for which
the average trafc volume or call attempts count is greatest over the days under consideration.
3-8
68P02900W21-R
GMR-01
Nov 2007
Trafc ow
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 trafc routes and switching equipment.
Trafc ow
If mobile trafc is dened 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 trafc ow (A) can be dened as:
Trafc Flow (A) = C x T
Where:
Is:
the calling rate per hour.
the average holding time per call.
Suppose an average hold time of 1.5 minutes is assumed and the calling rate in the busy hour is
120, then the trafc ow would be 120 x 1.5 = 180 call minutes or 3 call hours. One Erlang
of trafc intensity on one trafc channel means a continuous occupancy of that particular
trafc channel.
Considering a group of trafc channels, the trafc intensity in Erlangs is the number of
call-seconds per second or the number of call-hours per hour. For example, if there are a group
of 10 trafc 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. It 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
GMR-01
Nov 2007
Adaptive multi-rate (AMR)
Adaptive multi-rate (AMR)
Introduction
AMR offers two strong benets:
Expands air interface capacity through AMR half rate.
Expands the area of high call quality coverage through AMR full rate.
The ability of the AMR codec to 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). A codec with a higher level of error protection (and a corresponding decrease in speech
quality) is selected as channel quality deteriorates, leading to an increase in the 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 is secondary then {22064} GSM half rate is employed as an alternative. For
details about GSM half rate, see 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 are 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 higher trafc loading. However, the benets of AMR do not extend to the signaling
channels, or to the use of non-AMR codecs and data services. Capacity gains of this type are
dependent upon other factors (for example, 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 benets.
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 that are 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 (refer to Figure 3-4).
3-10
68P02900W21-R
GMR-01
Nov 2007
Figure 3-4
Quality of service
AMR half rate capacity increase
AMR Full Rate, Enhanced Full Rate

and Full Rate coverage area
Timeslot 1
AMR Full Rate
AMR Half Rate coverage area
Timeslot 3
Timeslot 2
2 3 4
16 kbit/s
AMR Half Rate
1 23 4 567 81 23 4 5 678 1 2 3 45 6 7 8
8 kbit/s
2 X voice calls supported

per timeslot in AMR Half Rate
coverage area
ti-GS M-AMR_half_rate_capacity_increase
-00127-a i-s w
Quality of service
AMR full rate delivers improved voice quality in poorer radio environments, providing high
quality in poorer signaling conditions:
AMR full rate offers 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 improves voice quality across the entire network, by supporting high quality
voice codecs in radio environments that cannot support Enhanced Full Rate (EFR).
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 proles of these codecs.
68P02900W21-R
3-11
GMR-01
Nov 2007
Applications
Figure 3-5
AMR full rate call quality improvements
In good radio environments:

AMR Full Rate voice quality = EFR V oice Quality
AMR Quality Improvements:

High voice quality in reduced radio quality
Mean Opinion
Score (MOS)
of voice
5.0
quality
4.0
3.0
2.0
1.0
EFR
12.2
10.2
7.95
7.4
6.7
5.9
5.15
4.75
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
ti-GS M-AMR_full_rate_call_quality_improvements
-00128-a i-s w
In comparison to the EFR curve, AMR full rate offers a signicantly higher quality codec solution
in marginal radio environments (C/I = 13 to 4 dB). This enables operators to offer high voice
quality in radio environments that does not support EFR. This improvement is paramount in
urban environments, which usually have a C/I between 11dB and 13 dB.
Applications
With the exibility of the AMR system, it is possible to customize the application of AMR to meet
specic network and service needs. Some of the potential application scenarios are identied
together with the advantages offered and the types of networks to which they suit.
Full rate only - High quality over full range of channel errors
Due to the robust error correction, ability of AMR, improved resilience to errors compared to
GSM EFR is provided. So that when in call, the speech quality varies little with channel errors.
It also provides signicantly improved quality under marginal coverage conditions (for example,
at cell edge, coverage holes, and so on). Some capacity advantage is also derived from the
improved resilience under low C/I conditions. It supports tighter frequency re-use.
Potential service applications - Suitable for operators who do not require to increase capacity
through half rate operation, but wish to offer the best speech quality possible to all users.
Half rate only - Improved quality over current HR codec

The AMR codec can be operated in half rate channel mode to gain maximum capacity
advantage. 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.
3-12
68P02900W21-R
GMR-01
Nov 2007
Migration to AMR half rate
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 also species a handover of half rate capable mobiles from a full rate channel to a
half rate channel 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, 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 efciency
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 GSM half rate

{22064}
AMR half rate and {22064} GSM half rate can coexist within a system, down to the RTF level.
One subrate operates as AMR half rate, the other as GSM half rate.
Interoperability with EGPRS

{23769}
When AMR half rate is enabled on an EGPRS capable carrier (pkt_radio_type = 3) in order
to maximize the VersaTRAU backhaul utilization, only 8 kbit/s switching on the backhaul is
supported.
68P02900W21-R
3-13
GMR-01
Nov 2007
GSM half rate
GSM half rate
{22064}
Introduction
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
subchannels, each containing a half rate channel. Although the speech quality is considered
inferior to other speech codecs, {22064} 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

GSM half rate doubles the number of voice calls that can be supported over the air interface as
with AMR half rate, thus allowing up to double the number of subscribers that are 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 (refer to Figure 3-6).
Figure 3-6 GSM half rate capacity increase

GSM Full Rate, Enhanced Full Rate
and Full Rate coverage area
Timeslot 1
Full Rate
GSM Half Rate coverage area
Timeslot 3
Timeslot 2
2 3 4
16 kbit/s
GSM Half Rate
1 23 4 567 81 23 4 5 678 1 2 3 45 6 7 8
8 kbit/s
2 X voice calls supported

per timeslot in GSM Half Rate
coverage area
ti-GS M-GSM_half_rate_capacity_increase
3-14
-00129-a i-s w
68P02900W21-R
GMR-01
Nov 2007
Quality of service
Quality of service
The {22064} 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 against the other codecs.
Figure 3-7 GSM half rate codec comparison
ti-GSM-GSM_half_rate_codec_comparison-00130-ai-sw
Applications
GSM half rate is best suited for use when spectral efciency is required. Two useful application
scenarios are identied together with the advantages offered and the types of networks to
which they are suited.
GSM half rate can be controlled at the cell level and is suitable to deal with high
user density clusters.
68P02900W21-R
3-15
GMR-01
Nov 2007
Migration to half rate
Half rate
The {22064} GSM half rate codec can be operated in half rate channel mode to gain maximum
capacity advantage. All qualifying calls are 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 {22064} GSM half
rate channels. The operator also species a handover of half rate capable mobiles from a
full rate channel to a half rate channel 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, care should be taken to ensure that the call capacity rating of the various
components of the system are not exceeded. Use of {22064} GSM half rate improves the
spectral efciency 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
subrate is operating as GSM half rate, the other as AMR half rate.

{23769} When GSM half rate is enabled on an EGPRS capable carrier (pkt_radio_type =
3) in order to maximize the VersaTRAU backhaul utilization, only 8 kbit/s switching on the
backhaul is supported.
3-16
68P02900W21-R
GMR-01
Nov 2007
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 prole 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 database,
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 prole
between the transmitter and receiver using the database. The computer then tests the path
prole for a line of sight path and tests whether the Fresnel zone clearance is obtained over the
path. The free space and plane earth propagation losses are calculated, and the higher value is
selected. If the line of sight and Fresnel-zone clearance test fails, then the program evaluates
the loss caused by any obstructions and grades them into single or multiple diffraction edges.
However, this method fails to take buildings into account when performing its calculation. The
calculations are based upon the terrain features.
Although the use of topographical based calculations are useful when designing mobile
communication systems, most mobile systems are centered around urban environments. In the
urban environments, the path between the transmitter and receiver can be blocked by some
obstacles (buildings for example). Therefore, it is necessary to resort to approximate methods of
calculating diffraction losses since exact calculations for each obstacle becomes difcult.
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 simplied. Any number is
expressed as a decibel. The only requirement is that the original description and unit scale
is appended to the dB, indicating a value, which can be used when adding, subtracting, or
converting decibels.
For example, for a given power of 1 mW that is 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 large or 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 difcult to express accurately the total power loss in a
simple way. By converting both gures 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 needs
adding the dB gures together, while division needs subtracting one dB gure from the other.
Another example is for every doubling of power gures, 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
GMR-01
Nov 2007
Decibels
N dB = 10 x log10 (PL/RPL)
Where:
Is:
the required power level in dB.
PL
the power level being converted.
RPL
the reference power level.
Table 3-1
dBm and dBW to power conversion
dBm
dBW
Power
dBm
dBW
Power
dBm
dBW
Power
+59
29
800 W
+ 24
-6
250
mW
-9
-39
0.125 mW
+56
26
400 W
+ 21
-9
125
mW
-10
-40
0.1 mW
+53
23
200 W
+ 20
-10
100
mW
-20
-50
0.01 mW
+50
20
100 W
+17
-13
50 mW
-30
-60
1 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
8 W
+4
-26
2.5 mW
-80
-110
0.01 nW
+36
4 W
+1
-29
1.25
mW
-90
-120
1 pW
+33
2 W
0 **
-30
1 mW
-100
-130
0.1 pW
+30
0 *
1 W
-3
-33
0.5 mW
-110
-140
0.01 pW
+27
-3
500
mW
-6
-36
0.25
mW
-120
-150
0.001 pW
* 1W reference value.
** 1 mW reference value.
The reference value is measured across a 50-ohm non-reactive load.
3-18
68P02900W21-R
GMR-01
Nov 2007
Fresnel zone
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 specic area
depending on the wavelength of the signal frequency. If a signal from that zone is reected on
an obstacle, which protrudes into the zone, it means that a reected signal as well as the direct
path signal arrives at the receiver. Radio waves reected in the rst Fresnel zone arrives at
the receiver out of phase with those taking the direct path and so combine destructively. This
results in low received signal strength. It is important when planning a cell to consider all the
radio paths for obstacles, which can produce reections from the rst Fresnel zone. If they
exist, it is like planning permanent areas of no coverage in certain parts of the cell.
To calculate whether this condition exists, the radius of the rst Fresnel zone at the point where
the object is suspected of intruding into the zone must be calculated.
Figure 3-8 illustrates the formula.
Where:
Is:
F1
the rst Fresnel zone.
d1
distance from Tx antenna to the obstacle.
d2
distance from Rx antenna to the obstacle.
wavelength of the carrier wave.
total path length.
Figure 3-8 First Fresnel zone radius calculation

FRE QUENCY = 900 M Hz
WAVELENGTH = 30 c m
F1
d
d2
d1
ti-GSM-First_Fresnel_zone_radius_calculation-00131-ai-sw
Once the cell coverage has been calculated, the radio path can be checked for any objects
intruding into the rst 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 rst
Fresnel zone is 0.6 of the radius.
68P02900W21-R
3-19
GMR-01
Nov 2007
Radio refractive index (RRI)
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 rst Fresnel zone.

It is important when planning a cell or microwave radio link to have an understanding of the
effects the RRI can have on microwave communications, and also what causes these changes.
RRI measurements provide planners with information on how much a radio wave is 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 denser layer of the atmosphere
to a less dense layer. It also occurs when passing from a less dense layer to a denser layer. This
can also occur under certain conditions, even at higher altitudes.
Figure 3-9 Refraction

RE FRACTION OCCURS AS THE RADIO WAVE PAS S ES THROUGH
LAYERS OF DIFFERENT ATMOS P HERIC DENS ITY
EARTH
ti-GSM-Refraction-00132-ai-sw
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 referenced to a value n at sea level. The value varies with seasons and location but
for the UK, the mean value is 1.00034. This gure is cumbersome to work with, so convention
has converted n to N.
Where:
N
Is:
(n-1) x 106
The value of N now becomes 340 units for the UK. The actual seasonal and global variations are
only a few tens of units at sea level.
3-20
68P02900W21-R
GMR-01
Nov 2007
The following inuence the value of N:
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. Although they affect the RRI, the affect does not vary.
The quantity of water vapor in the atmosphere. This is a variable and has signicant
effects on the RRI.
The temperature, pressure, and water vapor pressure have major effects on the RRI.
All either increases or decreases the RRI depending on local conditions, resulting in more or
less refraction of a radio wave. Although for a well-mixed atmosphere, the RRI falls by 40 N
units per 1 km increase in height sea level.
Measurement of RRI
There are two main ways of measuring the RRI at any moment in time. The rst method is by
use of Radio Sounds. This is an instrument, which is released into the atmosphere, normally
attached to a balloon. It measures the temperature, pressure, and humidity as it rises. 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 are carried by a balloon, aircraft, or 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 ner measurement showing variations in the RRI over height differences of a little over
one meter. This is illustrated in the graph as shown 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 )
RRI (N)
34 0
ti-GSM-Measurement_of_the_RRI-00133-ai-sw
68P02900W21-R
3-21
GMR-01
Nov 2007
Effects of deviations
The lapse rate of 40 N per km is based on clear sky readings with good atmosphere mixing. A
radio system is calibrated during these conditions and the height alignment in the case of a
microwave point-to-point link is determined.
It is easier to see the effects on a microwave point-to-point system when examining the effects of
uneven variations of the RRI. Figure 3-11 (A) shows an exaggerated curved radio path between
two antennas under normal conditions. The atmosphere refracts the signal and the signal
arrives at the receiving antenna.
Figure 3-11 (B) illustrates the condition known as super refraction, 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 does not cause any interference (as with sub refraction), it
could result in areas of no coverage.
Figure 3-11 (C) 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 misses 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
EARTH
EARTH
EARTH
NORMAL REFR ACTION
SUPER REFR ACTION
SUB-REFR ACTION
ti-GSM-Refraction_ef fects_on_a_microwave_system-00134-ai-sw
3-22
68P02900W21-R
GMR-01
Nov 2007
Environmental effects on propagation
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 subjected to any.
Events modifying the clear sky lapse rate

There are four main events that can modify the clear sky lapse rate and they are as follows:
Radiation nights
This is the result of a 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 prole no longer has a uniform lapse rate.
This effect only occurs over land 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 blown back over land, the trapped
cool air causes a temperature inversion. It persists until the air mass strikes high ground
where the increase in height mixes and dissipates the inversion.
Subsidence
This occurs again in a high-pressure system. This time over land, when air descending
from high altitude is heated by compression as it descends. This heated air then spreads
over the cooler air. This type of temperature inversion occurs at an altitude of 1 km but
can occasionally drop to 100 m where it causes 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 dissipates quickly.
Although those described are the four main causes of RRI deviations, local pressure, humidity
and temperature conditions could well give rise to events that affect the RRI.
Environmental effects on propagation

It is important to consider the effects that objects in the path of the radio wave have on it at
the frequency range used for GSM. Most objects in the path have some effect on the signal as
the wavelength is approximately 30 cm for GSM900 and 15 cm for DCSI1800. Such things
as vehicles, buildings, ofce ttings even people and animals affect the radio wave in one
way or another.
68P02900W21-R
3-23
GMR-01
Nov 2007
Attenuation
The main effects can be summarized as follows:
Attenuation
Reection
Scattering
Diffraction
Polarization changes
Attenuation
Any object obstructing the wave path causing absorption of the signal (refer to Figure 3-12)
causes attenuation. The effects are quite signicant 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 cause the signal to be attenuated by varying degrees.
Figure 3-12 Attenuation

INCOMING WAVE
OBJ ECT
ABS ORBS
THE
ENERGY
IN THE
RADIO
WAVE
OUTGOING WAVE
ATTENUATED BY THE OBJE CT
ti-GSM-Attenuation-00135-ai-sw
3-24
68P02900W21-R
GMR-01
Nov 2007
Attenuation
Reection
This is caused when the radio wave strikes a relatively smooth conducting surface. The wave is
reected at the same angle at which it arrived (see Figure 3-13). The strength of the reected
signal depends on how well the reector conducts. The greater the conductivity, the stronger is
the reected wave. This explains why seawater is a better reector than sand.
Figure 3-13 Reection

INCIDENT WAVE
REFLECTED WAVE
EQUAL ANGLES
SMO OTH S URFACE, SU CH AS WATER,

VERY REFLECTIVE
AMOUNT OF REFLECTION DEP ENDS ON

CONDUCTIVITY OF THE S URFACE
ti-GSM-Reflection-00136-ai-sw
Scattering
This occurs when a wave reects off a rough surface (see Figure 3-14). The rougher the surface
and the relationship between the size of the objects and the wavelength determines the amount
of scattering that occurs.
Figure 3-14
INCIDENT WAVE
Scattering
ENE RGY IS
SC ATTERED
ROUG H S TONY GROUND
ti-GSM-Scattering-00137-ai-sw
68P02900W21-R
3-25
GMR-01
Nov 2007
Attenuation
Diffraction
Diffraction occurs when a radio wave is bent off its normal path. This happens when the
radio wave passes over an edge, such as the edge of a building roof or at street level (see
Figure 3-15). The amount of diffraction that takes place increases as the frequency used is
increased. Diffraction can be a good thing as it allows radio signals to reach areas where they
would not be propagated.
Figure 3-15 Diffraction

SIDE VIEW
EXPECTED PATH
SHADOW
AREA
DIFFR ACTED
WAVE
DIFFR ACTED WAVE GIVING

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

COVERAGE AROUND THE CORNER
ti-GSM-Diffraction-00138-ai-sw
3-26
68P02900W21-R
GMR-01
Nov 2007
Multipath propagation
Polarization changes
This can happen with any of the effects due to atmospheric conditions and geomagnetic effects
such as the solar wind striking the atmosphere of the earth. These polarization changes mean
that a signal can arrive at the receiver with a different polarization than that which the antenna
has been designed to accept. If this occurs, the antenna attenuates the received signal.
Figure 3-16 shows the effects of polarization on a transmitted signal.
Figure 3-16 Polarization

ELECTRICAL PART OF WAVE
HORIZONTALLY P OLARIZED
(CHANGED BY ELECTRICAL S TORM)
ELECTRICAL PART OF WAVE

VERTICALLY P OLARIZED
ELECTRICAL S TORM
Rx
Tx
ti-GSM-Polarization-00139-ai-sw
Rayleigh and Rician fading
The receiver picks up the same signal as a result of the propagation effects on the transmitted
signal, which has been reected from many different objects resulting in what is known as
multipath reception. The signals arriving from the different paths have traveled different
distances and therefore arrive at the receiver at different times with different signal strengths.
Because of the reception time difference, the signals can or cannot be in phase with each other.
The result is that some combine constructively resulting in a gain of signal strength while others
combine destructively resulting in a loss of signal strength.
The receiving antenna is not required to be moved far for the signal strength to vary by many
tens of decibels. For GSM900, a move of just 15 cm or half a wavelength can sufce to observe a
change in signal strength. This effect is known as multipath fading. It is experienced in urban
areas where there are many buildings and the only signals received are from reections and
refractions of the original signal.
68P02900W21-R
3-27
GMR-01
Nov 2007
Rayleigh environment
Rayleigh has described this type of environment. Rayleigh analyzed 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 specically for non line of sight (refer to Figure 3-17) and is known
as Rayleigh distribution (refer to Figure 3-18).
Figure 3-17
Propagation effect - Rayleigh fading environment
Rx
Tx
ti-GSM-Propagation_ef fect_Rayleigh_fading_environment-00140-ai-sw
3-28
68P02900W21-R
GMR-01
Nov 2007
Figure 3-18 Rayleigh distribution

S IGNAL
S TRENGTH
THRES HOLD
1 2
WAVELENG TH
DEEP NULLS
DISTANCE
ti-GSM-Rayleigh_distribution-00141-ai-sw
Rician environment
When the signal path is predominantly in line of sight (see Figure 3-19) with insignicant
reections or diffractions arriving at the receiver, this is known as Rician distribution (see
Figure 3-20). There are still fades in signal strength but they rarely dip the threshold which
the receiver cannot process them.
Figure 3-19
Propagation effect - Rician environment
Rx
Tx
ti-GSM-Propagation_ef fect_Rician_environment-00142-ai-sw
68P02900W21-R
3-29
GMR-01
Nov 2007
Figure 3-20 Rician distribution

SIGNAL
STRENGTH
THRES HOLD
DISTANCE
ti-GSM-Rician_distribution-00143-ai-sw
Comparison of DCS1800 and GSM900

From a pure frequency point of view, DCS1800 generally has more fades than GSM900.
However, they are usually less pronounced.
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 the transmitter
and receiver, the instantaneous eld 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 through 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 a Rayleigh
distribution.
Rician distribution is exhibited if a microcell is employed where part of a cell coverage area
is predominantly the line of sight.
Free space loss

This is the loss of signal strength that occurs as the radio waves are propagated through free
space. Free space is dened as the condition where there are no sources of reection in the
signal path. This is impossible to achieve in reality but it does give a good starting point for
all propagation loss calculations.
3-30
68P02900W21-R
GMR-01
Nov 2007
Equally important in establishing path losses is the effect that the devices radiating the signal
have on the signal itself. The device is assumed as an isotropic radiator as a basis for the
calculation. This is a theoretical pinpoint antenna, which radiates equally in every direction.
If the device is placed in the middle of a sphere it would illuminate the entire inner surface
with an equal eld strength.
The following formula is used to nd out what the power covering the sphere is:
Where:
Is:
Pt
the input power to the isotropic antenna.
the distance from the radiator to the surface of the sphere.
This formula illustrates the inverse square law that the power decreases with the square of the
distance. The effective aperture (Ae) of the receiving antenna must be calculated to work
out the power received at a normal antenna.
The actual received power can be calculated as follows:
If P is substituted with the formula for the power received over the inner surface of a sphere
and Ae with its formula, then 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 is calculated by the following formula:
Logs are used to make the gures more manageable. The formula is dependent on distance
and frequency. The higher the frequency, the shorter is the wavelength, and therefore the
greater the path loss.
68P02900W21-R
3-31
GMR-01
Nov 2007
The formula is based on units measured in meters. For convenience, modify the formula to use
kilometer and megahertz for the distance and frequency. It becomes:
Where:
Is:
the distance in km.
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. The earth in its role as a reector
of signals must be taken into account to provide a more realistic model. When calculating the
plane earth loss, the model assumes that the signal arriving at the receiver consists of a direct
path component and a reective path component. Together these are called the space wave.
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 it 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 nal factors in path loss are the ground characteristics. These increase the path loss even
further depending on the type of terrain (refer to Figure 3-21).
3-32
68P02900W21-R
GMR-01
Nov 2007
Figure 3-21 Plane earth loss

Tx
FR EE S PACE LOSS
Rx
PATH LOSS INCREAS ES 6 dB FOR A DOUBLING OF d.
Tx
d
Rx
h1
2
h2
PLANE EARTH LOSS INC LUDES ONE EA RTH REFLEC TOR .

PATH LOSS INCREASES 12 dB FOR A DOUBLING OF d.
Tx
d
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.
ti-GSM-Plane_earth_loss-00144-ai-sw
The earths characteristics can be divided into three groups:
68P02900W21-R
3-33
GMR-01
Nov 2007
Excellent earth: For example seawater; this provides the least attenuation, so a lower
path loss.
Good earth: For example, rich agricultural land, moist loamy lowland, and forests.
Poor earth: For example, industrial or urban areas, and rocky land. These give the
highest losses and are found when planning urban cells.
Figure 3-21 illustrates plane earth loss, taking all factors into account.
Clutter factor
The nature of the surrounding urban environment inuences the propagation of the RF signal in
an urban area. 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, ofce blocks, and high-rise
residential tower blocks, whilst a suburban area contains residential houses, playing elds,
and parks as the main features. Problems can 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 of four storeys in the area.
Where:
B(dB)
Is:
the clutter factor in dB.
the frequency of RF signal.
the percentage of land within 500 m square occupied by buildings.
the difference in height between the squares containing the transmitter

and receiver.
0.094U - 5.9
the percentage of L occupied by buildings of four storeys.
A good base station site should be high enough to clear all the surrounding obstacles in the
immediate vicinity. 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
Nov 2007
Antenna gain
The additional gain provided by an antenna can be used to enhance the distance that the radio
wave transmits. 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 is concentrated. This
concentration, or focusing of power, is what enables the radio waves to travel further and if it
was possible to be radiated from an isotropic radiator. Refer to Figure 3-22.
Figure 3-22 Focusing of power

ISOTROPIC RADI ATOR
(ASPHERICAL PATTERN)
VERTICAL DIPOLE RADIATION PATTERN

(SIDE VIEW)
TRANSMITTER
ti-GSM-Focusing_of_power-00145-ai-sw
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 always has some gain when compared to an isotropic
radiator. See example in Figure 3-23.
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 needs 10 W. The gain of
the directional antenna is 100 dBi or 20 dBi.
Where:
Is:
isotropic
The more directional the antenna is made than the more gain it experiences. This is apparent
when sectorizing cells. Each sectored cell needs less transmit power than the equivalent range
omni cell due to the gain of its directional antenna, 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.
68P02900W21-R
3-35
GMR-01
Nov 2007
Figure 3-23
Measurement of gain
10 W
MEAS UREMENT P OINT
MEAS UREMENT P OINT

1000 W
TRANS MITTER
ti-GSM-Measurement_of_gain-00146-ai-sw
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 ne if all operators stand next to
the walls of the building when making calls, but this does not happen, so the internal distance
through which the signal passes should be considered. Due to the internal construction of a
building, the signal can suffer from spatial variations caused by the design of the interior of the
building.
3-36
68P02900W21-R
GMR-01
Nov 2007
Figure 3-24
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
ti-GSM-Building_propagation-00147-ai-sw
The building loss tends to be dened as the difference in the median eld intensity at the
adjacent area just outside the building and the eld intensity at a location on the main oor of
the building. This location can be anywhere on the main oor. This produces a building median
eld intensity gure, which is then used for plotting cell coverage areas and grade of service.
When considering coverage in tall buildings, if any oors of that building are the height of the
transmitting antenna, a path gain is experienced.
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 eld strength, location variabilities, and antenna height gain factors for
the base and mobile stations in urban, suburban, and open areas over quasi-smooth terrain.
Okumura dened the correction factors corresponding to various terrain parameters for
irregular terrain, such as rolling hills, isolated mountain areas, general sloped terrain, and
mixed land or sea path.
68P02900W21-R
3-37
GMR-01
Nov 2007
A method for predicting eld strength and service area for a given terrain of a land mobile radio
system was dened as a result of these tests carried out primarily in the Tokyo area. The
Okumura method is valid for the frequency range of 150 MHz to 2000 MHz, for distances
between the base station and the mobile stations of 1 km to 100 km, with base station effective
antenna heights of 30m to 100m.
The results of the median eld 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, and hilly terrain). The various antenna
heights used at the test transmitter base stations are also shown on these graphs. The graphs
show the median eld strength in relation to the distance in km from the site.
It does not transfer easily into a computer environment as this is a graphical representation of
results. However, the results provided by Okumura are the basis on which path loss prediction
equations have been formulated. Another Japanese engineer named Hata has carried out the
most important work. Hata has taken Okumuras graphical results and derived an equation to
calculate the path loss in various environments. These equations have been modied 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
11 0
922 MHz
h.= 320 m
h.= 220 m
h.= 140 m
h.= 45m
h.= 3 m
10 0
x
FIELD STREN GTH (dB rel. 1 uV/m) FOR 1 kW ERP
90
x
80
Fre e S pa ce
x
70
x
60
x
x
50
x
x
40
x
x
x
30
x
x
x
x
x
20
x
x
10
x
x
0
-10
0.6
10
20
LOG SCALE
30
40
50
LINEAR S CALE
60
70
80
90
100
DIS TANCE (km)

PR OPAGATION GRAP H FOR 922 MHz
ti-GSM-Okumura_propagation_graphs-00148-ai-sw
3-38
68P02900W21-R
GMR-01
Nov 2007
Hatas propagation formula

Hata used the information contained in Okumuras propagation loss report of the early 1960s,
which presented its results graphically, to dene 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 logR
Where:
Is:
the frequency.
the antenna height function.
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. Hata has set a series of limitations, which must be observed when using this
empirical calculation method 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 to 1500 MHz
Distance (R)
1 to 20 km
Base station antenna height (hb)
30 to 200 m
Vehicular antenna height (hm)
1 to 10 m
Hata dened three basic formulas based upon three dened types of coverage area: urban,
suburban, and open. Hatas formula predicts the actual path loss, and not the nal signal
strength at the receiver.
Urban Area:
Where:
#
Is:
the correction factor for vehicular station antenna
height.
Medium - Small City:
Large City:
68P02900W21-R
3-39
GMR-01
Nov 2007
GSM900 path loss
Where:
Is:
fc
> 400 MHz
Suburban Area:
Rural Area:
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 ampliers 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 has a service area far greater
than that which the mobile is 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.
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 decides 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 the calculated level for system balance. Although
this seems a simple way to increase coverage, the system balance is different and the mobile
cannot make a call in the new coverage area.
Increase the gain of the antenna, to increase the cell coverage. This affects both the uplink
and downlink therefore maintaining system balance. Separate antennas used for transmit and
receive must be of similar gain. If the cell size is reduced, the BTS power can be altered as the
mobiles output power is adaptive all the time.
There is a statistic in the BTS that checks the path balance every 480 ms for each call in
progress. The latest uplink and downlink gures reported along with the actual mobile and BTS
transmit powers are used in a formula to give an indication of the path balance.
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.
3-40
68P02900W21-R
GMR-01
Nov 2007
GSM900 path loss
Figure 3-26 BTS antenna height of 50 m, MS height of 1.5 m (GSM900)

220
210
200
S UBURBAN
190
URBAN INDOOR
PATH LOSS (dB)
180
URBAN
170
160
150
140
130
RURAL (QUAS I OP EN)
120
110
RURAL (OP EN)
100
90
100
10
CELL RADIUS (km)

ti-GSM-BTS_antenna_height_of_50 m_MS_height_of_1.5 m-00149-ai-sw
Figure 3-27 BTS antenna height of 100 m, MS height of 1.5 m (GSM900)

220
210
200
S UBURBAN
190
URBAN INDOOR
PATH LOSS (dB)
180
URBAN
170
160
150
140
130
RURAL (QUAS I OP EN)
120
110
RURAL (OP EN)
100
90
1
10
100
CELL RADIUS (km)

ti-GSM-BTS_antenna_height_of_100 m_MS_height_of_1.5 m-00150-ai-sw
68P02900W21-R
3-41
GMR-01
Nov 2007
Path loss GSM900 against DCS1800
Path loss GSM900 against 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 against cell radius for small cells
170
160
DCS1800
(METRO P OLITAN CENTRES )
PATH LOS S (dB)
150
140
130
GS M900
120
DCS 1800 (MEDIUM SIZED
CITIES AND S UBURBAN
CENTR ES )
110
100
0.1
0.3
CELL RADIUS (km)
1.0
3.0
ti-GSM-Path_loss_against_cell_radius_for_small_cells-00151-ai-sw
3-42
68P02900W21-R
GMR-01
Nov 2007
Frequency re-use
Frequency re-use
Introduction
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.
Frequency Band
Tx Range
Rx Range
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 nite number of channels are allocated to the planner.
The number of channels does not necessarily cover the full frequency spectrum and care should
be taken when selecting or allocating the channels.
Installing a greater number of cells provides greater spectral efciency with more frequency
re-use of available frequencies. However, a balance must be struck between the spectral
efciency and all the costs of the cell. The size of cells also indicates how the frequency
spectrum is used. Maximum cell radius is determined in part by the output power of the mobile
subscriber (MS) and interference caused by adjacent cells (see Figure 3-29).
Figure 3-29 Adjacent cell interference

INTERFERING CARRIER
F 33
CARR IER
F 33
RE CE IVE
SIGNAL
LEVEL
- 75dBm
- 100dBm
SE RVING BTS
DIS TANCE
INTERFERING BTS
MOBILE P OS ITION
ti-GSM-Adjacent_cell_interference-00152-ai-sw
68P02900W21-R
3-43
GMR-01
Nov 2007
Re-use pattern
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 the link budget.
The effective range of a cell varies according to the location, and can be as much as 35 km in
rural areas and as little as 1 km in a dense urban environment.
Re-use pattern
The total number of radio frequencies allocated is split into some channel groups or sets. These
channel groups are assigned on a per cell basis in a regular pattern, which repeats across all the
cells. Thus, each channel set can be re-used several times throughout the coverage area, giving
rise to a particular re-use pattern (for example, 7-cell re-use pattern shown in Figure 3-30).
Figure 3-30
7
6
5
3
3
4
2
1
EACH US ING
CHANNEL S ETS
3
4
7 cell re-use pattern
2
1
4
7
5
3
4
7 C ELL RE-USE
1
6
2
7
1
5
ti-GSM_cell_re_use_pattern-00153-ai-sw
The number of available channels per cell reduces and therefore the system capacity falls as
the number of channel sets increases. However, as the number of channel sets increases, the
distance between co-channel cells also increases, thus the interference reduces. Therefore
selecting the optimum number of channel sets is a compromise between quality and capacity.
3-44
68P02900W21-R
GMR-01
Nov 2007
Re-use pattern
4 site- 3 cell re-use pattern

Due to the increase in frequency robustness within the GSM, different re-use frequency patterns
can be adopted which gives an overall greater frequency efciency.
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 2 to 1.
Figure 3-31 4 site - 3 cell re-use pattern
c1
c2
d1
c3
d3
b1
d2
b1
d1
d2
b2
d3
b2
b3
a1
b3
a2
c1
a1
a2
a3
c1
a3
d1
c3
d1
d3
b1
c2
c2
c3
d2
b1
d2
b2
d3
b2
b3
a1
b3
a2
a3
NEW CELL CAN

USE d1-3 FREQ
ALLOCATION
EXAMPLE
b1
b2
a1
b3
a3
c1
a2
a2
c2
c3
ti-GSM-3_cell_re_use_pattern-00154-ai-sw
The other main advantage of this re-use pattern is if a new cell is inserted in the network,
then there is always a frequency channel set available which does not cause any adjacent
channel interference.
68P02900W21-R
3-45
GMR-01
Nov 2007
Carrier/Interference (C/I) ratio
2 site- 6 cell re-use pattern

Another solution to network user capacity problems can 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
a2
a6
b1
a5
b5
b3
b4
b5
b1
a3
a6
b4
b6
a4
a5
a3
a4
b2
b6
b3
b2
a2
a1
60 S ECTORS
ti-GSM-2_site_6_cell_reuse_pattern-00155-ai-sw
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 can be difcult and cannot be possible to implement. It also
cannot be possible due to the current network conguration. However, the subscribers per
km ratio can be improved.
Carrier/Interference (C/I) ratio

When a channel is re-used, there is a risk of co-channel interference, 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. However, the interference level also reduces, 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. Some 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-46
68P02900W21-R
GMR-01
Nov 2007
Sources of interference
Carrier or interference measurements taken at different locations within the coverage of a cell
can be compared to a previously dened acceptable criterion. For instance, the criterion for
the C/I ratio maybe set at 8 dB, with the expectation that the C/I measurements are better
than that gure for 90% of the 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 the overall system comparison.
Figure 3-33 Carrier interference measurements

(2 CELLS USIN G THE S AME BCCH FREQUENCY)
CAN BE RELATED TO D/R
C/
I
BS
BS
R
MS
DIS TANCE BETWEE N CELLS

D
ANALOG UE SYST EM D/R
GSM S YSTEM D/R = 2.62
= 4.4
ti-GSM-Carrier_interference_measurements-00156-ai-sw
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 inuenced by the spacing of RF channels, its effect can
be reduced by increasing the frequency spacing of the channels. However, this has 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.
68P02900W21-R
3-47
GMR-01
Nov 2007
Sectorization of sites
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 insignicant to levels that 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 some
surrounding cells, not just one.
What effect do the directional antennas have when employed?
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 an omni cell, co-channel interference is received from six surrounding
cells, all using the same channel sets. Therefore, one way of signicantly 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 trafc channels available at a cell site, which means more
trafc channels available for subscribers to use. In addition, by installing more capacity at the
same site, there is a signicant reduction in the overall implementation and operating costs
experienced by the network user. By using sectorized antennas, sectorization allows the use of
geographically smaller cells and a tighter economic re-use of the available frequency spectrum.
This results in better network performance to the subscriber and greater spectrum efciency.
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 exibility to meet uneven
subscriber distribution by allowing, if required, an uneven distribution of trafc resources
across the cells on a particular site. This allows a more efcient 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-48
68P02900W21-R
GMR-01
Nov 2007
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 attempts to recover
all the time-dispersed signals. This leads to an overlapping situation where each signal path
inuences the other, making the original data 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 difcult to distinguish the original signal state.
Another factor that makes things even more difcult is that the modulation technique Gaussian
minimum shift keying introduces a certain amount of ISI. Although this is a known distortion
and can under normal conditions be ltered out, when it is added to the ISI distortion caused by
the time delayed multipath signals, it makes recovery of the original data that much harder.
Frequency hopping
Frequency hopping is a feature that can be implemented on the air interface (for example, the
radio path to the MS) to help overcome the effects of multipath fading. GSM recommends only
one type of frequency hopping - baseband hopping; but the Motorola BSS supports 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 ow
is routed in the baseband to various transceivers, each of which operates on a xed frequency,
in accordance with the assigned hopping sequence. The different transceivers receive a specic
individual timeslot in each TDMA frame containing information destined for different MSs.
There are important points to note when using this method of providing frequency hopping:
There is a requirement 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. 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.
68P02900W21-R
3-49
GMR-01
Nov 2007
Error protection and detection
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 lter or
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 programs 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 used the other pair is 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 requirement to provide as many transceivers as determined by trafc 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 make good candidates for
synthesizer hopping, whilst cells with many carriers are good candidates for baseband hopping.
There is also another rule: there can only be one type of hopping at a BTS site, not a
combination of the two.

Many different coding schemes are used to protect the logical channels from transmission
errors introduced by the radio path. The coding and interleaving schemes depend on the type of
logical channel to be encoded. All logical channels need 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.
3-50
68P02900W21-R
GMR-01
Nov 2007
Common control channel encoding

20 ms of information over the air carries 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 important. Therefore, when the data is reconstructed at the receiver, if a burst is lost,
only a small proportion of the 20 ms block of data is lost. The error encoding mechanisms
should then enable the missing data to be reconstructed.
Figure 3-34
Coding process
0.577 ms
INFORMATION
BURST S
20 ms
INFOR MATION
BLOC K
SP EE CH
(8 BURST S FULL RATE OR
ENHANCED FULL RATE,
OR B BURS TS AMR)
SP EE CH
(260 B ITS FULL RATE OR
ENHANCED FULL R ATE,
OR A BITS AMR)
ENC ODING
INTERLEAVING
CO NTROL (184 BITS )
CONTROL (4 BURS TS )
DATA (240 BITS )
DATA (22 BURS TS )

ti-GSM-coding_process-00157-ai-sw
68P02900W21-R
3-51
GMR-01
Nov 2007
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.
Table 3-2 Speech channel coding

Channel type
Is channel type
supported?
Number of speech bits

delivered per block (A)
Number of speech bursts

delivered per block (B)
TCH/AFS12.2
Yes
244
TCH/AFS10.2
Yes
204
TCH/AFS7.95
No
159
TCH/AFS7.4
Yes
148
TCH/AFS6.7
Yes
134
TCH/AFS5.9
No
118
TCH/AFS5.15
Yes
103
TCH/AFS4.75
No
95
TCH/AHS7.95
Yes
159
TCH/AHS7.4
Yes
148
TCH/AHS6.7
Yes
134
TCH/AHS5.9
Yes
118
TCH/AHS5.15
Yes
103
TCH/AHS4.75
No
95
TCH/FS
Yes
260
TCH/EFS
Yes
244
TCH/HS
Yes
112
AFS = AFR = AMR full rate (speech)
AHS = AHR = AMR half rate (speech)
HS = HR = GSM half rate (speech)
Figure 3-35 illustrates the coding process for full rate and enhanced full rate speech, control,
and data channels; the sequence is complex.
3-52
68P02900W21-R
GMR-01
Nov 2007
Figure 3-35
EFR SPEECH
FRAME
244 BITS
Coding process illustration (full rate and enhanced full rate speech)
FR SPEECH
FRAME
260 BITS
BCCH, PCH, AGCH, SDCCH,

FACCH, S ACCH, CBCH
184 BITS
DATA TRAFFIC
9.6/4.8/2.4 k
N0 BITS
FIRECO DE + TAIL
IN: 184
OUT: 22 8
ADD IN TAIL
IN: N0 BITS
OUT: N1 BITS
CYCLIC CODE + TAIL

IN: P0 BITS
OUT: P1 BITS
CON VOLUTION CODE

IN: 248 BITS
OUT: 456 BITS
CON VOLUTION CODE

+ PUNCTURE
IN: N1 BITS
OUT: 456 BITS
CON VOLUTION CODE

IN: P1 BITS
OUT: 2 x P1 BITS
CYCLIC CODE
+ REPETITION
IN: 244
OUT: 260
RACH + SCH
P0 BITS
CLASS 1a
CYCLIC CODE
+ TAIL
IN: 260
OUT: 267
CON VOLUTION CODE

IN: 267 BITS
OUT: 456 BITS
TCH/2.4
RE-ORDERING & PARTITIONING

+ STEALING FL AG
IN: 456 BITS
OUT: 8 SUB-BLOCKS
BLOCK DIAGONAL
INTERLEAVING
IN: 8 BLOCKS
OUT: PAIRS OF BLOCKS
8x
8x
8x
8x
TCH FR ( BURSTS)
TCH EFR ( BURSTS)
FACCH/TCH ( BURSTS)
TCH 2-4 kBIT/S ( BURSTS)
DIAGONAL INTERLEAVING +
STEALING FLAG
IN: BLOCKS OF 456 BITS
OUT: 22 SUB-BLOCKS
BLOCK RE CTANGULAR
INTERLEAVING
IN: 8 SUB -BLOCKS
OUT: PAIRS OF SUB-BLOCKS
4 x BCCH, PCH, AGCH

4 x SDCCH, S ACCH
4 x CBCH ( BURSTS)
1 x R ACH
1 x SCH ( BURST)
19 x TCH 9.6 kBIT/S ( BURST)
ti-GSM-full_rate_and_enhanced_full_rate_speech-00158-ai-sw
Figure 3-36 illustrates the coding process for AMR full rate and AMR half rate speech, control
and data channels.
68P02900W21-R
3-53
GMR-01
Nov 2007
Figure 3-36 Coding process illustration (AMR full rate and AMR half rate speech)
AMR S PE ECH
FR AME
"A" BITS
(se e )
BCCH, P CH, AGC H, SD CC H,

FACC H, S ACC H, CBCH
184 BITS
DATA TRAFFIC
9.6 /4.8 /2.4 k
N0 BITS
CLASS 1 a C YCLIC
CO DE (6) + TAIL (4)
IN: "A"
OUT: "A" + 10 BITS
FIREC ODE + TAIL

IN: 18 4
OUT: 22 8
ADD IN TAIL
IN: N0 BITS
OUT: N1 BITS
CYCLIC CODE + TAIL

IN: P0 BITS
OUT: P1 BITS
CO NVOLUTION CO DE
IN: 24 8 BITS
OUT: 45 6 BITS
CO NVOLUTION CO DE
+ P UNCTURE
IN: N1 BITS
OUT: 45 6 BITS
CO NVOLUTION CO DE
IN: P1 BITS
OUT: 2 x P1 BITS
RACH + S CH
P0 BITS
CO NVOLUTION CO DE
IN: A" + 10 BITS
OUT: se e
CO DE PU NCTURING
IN: se e
OUT (AFR ): 44 8 BITS
OUT (AHR): 22 4 BITS
INBAND S IGNALLING
IN (AFR): 44 8 BITS
IN (AHR): 22 4 BITS
OUT (AFR ): 45 6 BITS
OUT (AHR): 22 8 BITS
TCH/2.4
DIAGO NAL INTERLEAVING +

ST EALING F LAG
IN: BLOC KS OF 45 6 BITS
OUT: 22 SU B-BLOCKS
RE -OR DERING & PARTITIONING

+ S TEALING FLAG
IN: 45 6 BITS
OUT: 8 S UB-BLOC KS
BLOC K DIAGO NAL

INTER LEAVING
IN: 8 B LOCKS
OUT: PAIRS O F BLOCKS
8x
8x
8x
8x
TCH FR (BURST S)
TCH EFR (BURST S)
FACC H/TCH (BURST S)
TCH 2-4 kBIT/S (BURST S)
BLOC K REC TANGULAR

INTER LEAVING
IN: 8 SU B-BLOCKS
OUT: PAIRS O F S UB-BLOC KS
4 x BCCH, P CH, AGC H

4 x SD CC H, S ACC H
4 x CBCH (BURS TS )
1 x RACH
1 x SC H (BURST )
19 x TCH 9.6 KBIT/S (BURST )

AFR = AMR F ull Rate
AHR = AMR Half Rate
ti-GSM-AMR_full_rate_and_AMR_half_rate_speech-00159-ai-sw
Code puncturing is performed to remove some of the encoded bits. In addition,

for AMR half rate codecs, Class 2 bits are added to the Class 1 bits.
3-54
68P02900W21-R
GMR-01
Nov 2007
The inband signaling bits (8 for AFR and 4 for AHR) are block-coded
representations of the codec identier, 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.
Figure 3-37 illustrates the coding process for {22064} GSM half rate speech, control, and
data channels.
Figure 3-37
Coding process illustration (GSM HR speech, control and data)
HR
112 bits
EFR Speech
Frame
244 bits
Cyclic code +
Tail
In: 112 bits
Out: 121 bits
Cyclic code +
Repetition
In: 244 bits
Out: 260 bits
FR Speech
Frame
260 bits
BCCH, PCH, AGCH, SDCCH,

FACCH, SACCH, CBCH
184 bits
Data Traffic
9.6/4.8/2.4K
No Bits
RACH + SCH
PO Bits
Firecode +
Tail
In: 184 bits
Out: 228 bits
Add In Tail
In: No bits
Out: N1 bits
Cyclic code +
Tail
In: P0 bits
Out: P1 bits
Convolution Code
+ Puncture
In: N1 bits
Out: 456 bits
Convolution Code
In: P1 bits
Out: 2 X P1 bits
Class 1 A Cyclic
Code + Tail
In: 160 bits
Out: 267 bits
Convolution Code
In: 121 bits
Out: 228 bits
Convolution Code
In: 267 bits
Out: 456 bits
Convolution Code
In: 248 bits
Out: 456 bits
TCH/2.4
Re-ordering & Partitioning
+ Stealing Flag
In: 228 bits
Out: 4 sub-blocks
Re-ordering & Partitioni ng

+ Stealing Flag
In: 456 bits
Out: 8 sub-blocks
Block Diagonal
Interleaving
In: 4 blocks
Out: Pairs of blocks
Block Diagonal
Interleaving
In: 8 blocks
Out: Pairs of blocks
4 X TCH HR (bursts)
8 X TCH FR (bursts)
8 X TCH EFR (bursts )
8 X FACCH/TCH (bursts)
8 X TCH 2-4 kBits/S ( bursts)
DIAGONAL INTERLEAVING
STEALING FLAG
In: Blocks of 456 bits
Out: 22 Sub-blocks
Block Rectangular
Interleaving
In: 8 sub-blocks
Out: Pairs of sub-blocks
1 X RACH
1 X SCH (burst)
4 X BCCH, PCH, AGCH

4 X SDCCH, SACCH
4 X CBCH (bursts)
19 x TCH 9.6 kBIT/S (BURST)
ti-GSM-GSM_HR_speech_control_and_data-00160-ai-sw
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).
68P02900W21-R
3-55
GMR-01
Nov 2007
GSM speech channel encoding for full rate
Table 3-3
AMR codecs, convolutional output bits and punctured bits
Codec mode
Is codec mode
supported?
Rate
Number of output bits from

convolutional coder
Number of
punctured bits
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

The BTS receives transcoded speech over the Abis interface from the BSC. At this point, the
speech is organized into its individual logical channels by the BTS. These logical channels of
information are then channel coded before being transmitted over the air interface.
The transcoded speech information is received in frames, each containing 260 bits. The speech
bits are grouped into three classes of sensitivity to errors, depending on their importance to
the intelligibility of speech.
Class 1a
Three parity bits are derived from the 50 Class 1a bits. Transmission errors within these
bits are catastrophic to speech intelligibility; therefore, the speech decoder is able to detect
uncorrectable errors within the Class 1a bits. If there are Class 1a bit errors, the whole block
is ignored.
3-56
68P02900W21-R
GMR-01
Nov 2007
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 equaling 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 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
50 BITS
PARITY
CHEC K
CLAS S 1b
132 BITS
CLAS S 2
78 BITS
TAIL
BITS
50
132
CO NVOLUTIONAL CODE
78
378
456 BITS
ti-GSM-Speech_channel_encoding-00161-ai-sw
68P02900W21-R
3-57
GMR-01
Nov 2007
GSM speech channel encoding for enhanced full rate
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.
3-58
68P02900W21-R
GMR-01
Nov 2007
GSM speech channel encoding for half rate
Figure 3-39 Preliminary coding for enhanced full rate speech

244 BITS
CLASS 1a
50 BITS
CLASS 1b
124 BITS
8 BIT CR C ADDED TO
CLASS 1b BITS
CLASS 1a
50 BITS
CLASS 1b
132 BITS
CLASS 2
70 BITS
8
REPETITION
BITS ADDED
TO CLASS 2
BITS
CLASS 2
78 BITS
260 BITS
ti-GSM-Preliminary_coding_for_enhanced_full_rate_speech-00162-ai-sw
GSM speech channel encoding for half rate

{22064}
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 signicant 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 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.
68P02900W21-R
3-59
GMR-01
Nov 2007
GSM speech channel encoding for AMR full rate
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 {22064} GSM half rate speech
CLASS 1a
22 BITS
PARITY
CHEC K
CLAS S 1b
73 BITS
CLAS S 2
17 BITS
TAIL
BITS
CLASS 1a
22 BITS
CLAS S 1b
73 BITS
CLAS S 2
211 Convoluted Bits
17 BITS
228 BITS
ti-GSM-Speech_channel_encoding_for_GSM_half_rate_speech-00163-ai-sw

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 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
is 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.
3-60
68P02900W21-R
GMR-01
Nov 2007
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 selected for AMR are more complex and expensive than the NSNR codecs
for EFR and FR. However, they provide better error protection.
InBand signaling
InBand signaling bits are used to coordinate the codec usage between the BTS and MS because
the utilized channel codec can vary dynamically from speech frame to speech frame (see Link
adaptation for AMR channels on page 3-64 section). 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 signaling bits are added
to the encoded and punctured Class 1a, 1b, and parity bits. The InBand signaling bits are the
block-coded representation of the appropriate 2-bit codec identier. The resulting 456-bit block
is then interleaved before being sent over the air interface.
The encoded speech now occupies 456 bits, but is still transmitted in 20 ms, thus raising the
transmission rate to 22.8 kbit/s.
Table 3-4
X, Y and Z bit values for AMR FR speech channel encoding
Codec mode
Is codec mode
supported?
X bits
Y bits
Z bits
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.
68P02900W21-R
3-61
GMR-01
Nov 2007
GSM speech channel encoding for AMR half rate
Figure 3-41 Speech channel encoding for AMR full rate

CLASS 1a
Y BITS
PARITY
CHEC K
CLAS S 1b
Z BITS
TAIL
BITS
CON VOLUTIONAL CODE
COD E PU NCTURING
INBAND
S IGNALLING
BITS
8
44 8
456 BITS
ti-GSM-Speech_channel_encoding_for_AMR_full_rate-00164-ai-sw

The BTS receives transcoded speech over the Abis interface from the BSC. 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
is 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 convolutionally coded symbols are punctured to reduce the
resulting data rate to that supported over the air interface.
3-62
68P02900W21-R
GMR-01
Nov 2007
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
selected for AMR are more complex and expensive than the NSNR codecs for HR. However,
they provide better error protection.
Class 2
Any channel coding does not protect the W Class 2 bits. 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 signaling
InBand signaling bits are used to coordinate the codec usage between the BTS and MS because
the utilized channel codec can vary dynamically from speech frame to speech frame (see Link
adaptation for AMR channels on page 3-64 section). 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 signaling bits are added to the encoded and punctured class 1a, 1b, parity, and
Class 2 bits. The InBand signaling bits are the block-coded representation of the appropriate
2-bit codec identier. The resulting 228-bit block is then interleaved before being sent over
the air interface.
The encoded speech now occupies 228 bits, but is still transmitted in 20 ms, thus raising the
transmission rate to 11.4 kbit/s. Two half rate subchannels sharing the same timeslot have a
total transmission rate of 22.8 kbit/s.
Table 3-5 X, Y, Z and W bit values for AMR HR speech channel encoding
Is codec mode
supported?
X bits
Y bits
Z bits
W bits
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
Codec mode
Figure 3-42 shows a diagrammatic representation of speech channel encoding for AMR half rate.
68P02900W21-R
3-63
GMR-01
Nov 2007
Link adaptation for AMR channels
Figure 3-42
Speech channel encoding for AMR half rate
CLASS 1a
Y BITS
CLAS S 1b
Z BITS
CLAS S 2
W BITS
TAIL
BITS
PARITY
CHECK
INBAND
S IGNALLING
BITS
CON VOLUTIONAL CODE
CODE PUN CTUR ING
228 BITS
ti-GSM-Speech_channel_encoding_for_
AMR_half_rate-00165-ai-sw
Link adaptation for AMR channels

The fundamental performance benet of the AMR trafc channel is the networks 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.
A non-AMR trafc channel, such as full rate or Enhanced full rate, is permitted to use one xed
speech and channel codec combination only. In favorable 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 signicantly degrade
sound quality.
Conversely, an AMR trafc channel, based on the observed channel conditions, is permitted
to select dynamically 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 trafc channel limits erased frames to a permitted level yet provides the highest sound
quality possible for that condition.
For example, under good channel conditions, the AMR trafc channel selects the codec
combination with the highest vocoding and lowest channel coding rates. Here, the minimal
channel coding is sufcient to maintain the permitted FER level. Moreover, the vocoding
provides high sound quality rivaling that of EFR operating in a good channel condition. Under
poor channel conditions, the AMR channel selects the codec combination with the lowest
vocoding and highest channel coding rates. Here, the increased channel coding is sufcient
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.
3-64
68P02900W21-R
GMR-01
Nov 2007
GSM control channel encoding
Measuring channel conditions: C/I

On an AMR trafc 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 congurable C/I ranges which dene 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 the 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 signaling

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
signaling 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
signaling 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.
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.
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 signaling channels, the synchronization channel (SCH) and the random
access burst (RACH). The diagram applies to SCH and RACH, but with different numbers.
68P02900W21-R
3-65
GMR-01
Nov 2007
GSM circuit-switched data channel encoding
Figure 3-43 Control channel coding
184 BITS
184
PARITY BITS
FIRE CODE
TAIL BITS
184
40
CO NVOLUTIONAL CODE
456
456 BITS
ti-GSM-Control_channel_coding-00166-ai-sw
When control information is received by the BTS it is received as a block of 184 bits. These bits
are rst 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 signaling 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.

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.
3-66
68P02900W21-R
GMR-01
Nov 2007
Figure 3-44
Data channel encoding
DATA CHANNEL 9.6 kbit/s

240 BITS
240
TAIL
BITS
240
CON VOLUTIONAL CODE
488
P UNCTURE
456
456 BITS
ti-GSM-Data_channel_encoding-00167-ai-sw
Data channels are encoded using a convolutional code only. With the 9.6 kbit/s data, some coded
bits require to be removed (punctuated) before interleaving, so that like the speech and control
channels, they contain 456 bits every 20 ms.
The data trafc channels need a higher net rate than their actual transmission rate (net rate
means the bit rate before the coding bits have been added). For example, the 9.6 kbit/s service
needs 12 kbit/s, because status signals (such as the RS-232 DTR) have to be transmitted as well.
The output from the encoding process for each block of 240 bits of data trafc 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.
Over the PCM link, 240 bits were transmitted in 20 ms, equaling a transmission rate
of 12 kbit/s, 9.6 kbit/s raw data, and 2.4 kbit/s signaling 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.
68P02900W21-R
3-67
GMR-01
Nov 2007

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 trafc
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 the MS and BTS. A gure of 10 to 20% is
quite normal. The purpose of interleaving is to ensure that only some of the data from each
trafc block is contained within each burst. Thus when a burst is not correctly received, the loss
does not affect the overall transmission quality because the error correction techniques are able
to interpolate for the missing data. If the system worked by simply having one trafc 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 signicant noise and interference, and maintain the
quality of service presented to the subscriber.
Table 3-6 Interleaving

Transcoder Rate Adaptation Unit
(TRAU) frame type
Number of GSM bursts the trafc block

is spread over
Speech (full rate)
Speech (half rate)
Control
CS data
22
3-68
68P02900W21-R
GMR-01
Nov 2007
Diagonal interleaving - full rate speech

Figure 3-45 illustrates, in a simplied form, the principle of the interleaving process applied to a
full rate speech channel.
Figure 3-45 Diagonal interleaving - full rate speech
20 ms SP EE CH SAMPLE 45 6 BITS
BITS 4 , 12 , 2 0, 2 8 .... . 45 2
MAPP ED TO O DD BITS
OF BURST
BITS 0 , 8, 16, 24 .... . 44 8
BITS 0 , 8, 16 , 24 .... . 44 8
MAPP ED TO E VEN BITS

OF BURST

OF BURST
BITS 4 , 12 , 2 0, 2 8 .... . 45 2
OF BURST
012 345 678 ... . 11 3
012 345 678 ... . 11 3

ti-GSM-Diagonal_interleaving_full_rate_speech-00168-ai-sw
The diagram shows a sequence of speech blocks after the encoding process. Each block
contains 456 bits, these blocks are then divided into eight blocks each containing 57 bits. Each
block contains bits from even bit positions or bits from odd bit positions. The GSM burst is
produced using these blocks of speech bits.
The rst four blocks is placed in the even bit positions of the rst four bursts. The last four
blocks are placed in the odd bit positions of the next four bursts.
As each burst contains 114 trafc-carrying bits, it is shared by two speech blocks. Each block
shares four bursts with the block preceding it, and four with the block that succeeds it, as
shown. In the diagram, block 5 shares the rst four bursts with block 4 and the second four
bursts with block 6.
68P02900W21-R
3-69
GMR-01
Nov 2007
Diagonal interleaving - half rate speech

Figure 3-46 illustrates, in a simplied form, the principle of the interleaving process applied to a
half rate speech channel.
Figure 3-46 Diagonal interleaving - half rate speech
BITS 4 , 12 , 2 0, 2 8 .... . 22 5
OF BURST
20 ms SP EE CH S AMPLE 2 28 BITS
BITS 0 , 8, 16, 24 .... . 22 4
BITS 0 , 8, 16 , 24 ..... 22 4

OF BURST

OF BURST
BITS 4 , 12 , 2 0, 2 8 .... . 22 5
OF BURS T
012 345 678 ... . 11 3
012 345 678 ... . 11 3

ti-GSM-Diagonal_interleaving_half_rate_speech-00169-ai-sw
The diagram shows a sequence of speech blocks after the encoding process. Each block
contains 228 bits, these blocks are then divided into four blocks each containing 57 bits. Each
block contains bits from even bit positions or bits from odd bit positions. The GSM burst is
produced using these blocks of speech bits.
The rst two blocks are placed in the even bit positions of the rst two bursts. The last two
blocks are placed in the odd bit positions of the next two bursts.
As each burst contains 114 trafc-carrying bits, it is shared by two speech blocks. Each block
shares two bursts with the block preceding it, and two with the block that succeeds it, as
shown. In the diagram, block 5 shares the rst two bursts with block 4 and the second two
bursts with block 6.
3-70
68P02900W21-R
GMR-01
Nov 2007
Transmission - full rate speech

Each burst is 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
2 10 18 26 34 42 .............450
even bits of burst N + 2
3 11 19 27 35 43..............451
4 12 20 28 36 44..............452
odd bits of burst N + 4
5 13 21 29 37 45...............453
6 14 22 30 38 46...............454
7 15 23 31 39 47...............455
It is important to remember that each timeslot on this carrier is occupied by a different channel
combination: trafc, broadcast, dedicated or combined.
As FACCH steals speech bursts from a subscriber channel, it experiences the same
kind of interleaving as the speech data that it replaces (interleaving depth = 8).
The FACCH steals a 456-bit block and is interleaved with the speech. Each burst containing a
FACCH block of information has the appropriate stealing ag set.
Transmission - half rate speech

For half rate speech, two independent subchannels share the same air interface timeslot. While
each subchannels 20 ms speech sample is encoded and diagonally interleaved into its own 4
bursts separately, both subchannels must share the physical channel at transmission time. To do
this, both subchannels 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
subchannel 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
2 6 10 14 18 22 ................226

Continued
68P02900W21-R
3-71
GMR-01
Nov 2007
Table 3-8 Distribution of 228 bits from one 20 ms half rate speech sample (Continued)
Distribution
Burst
1 5 9 13 17 21 ..................225
3 7 11 15 19 23 ................227
It is important to remember that each timeslot on this carrier is occupied by a different channel
combination: trafc, broadcast, dedicated or combined.
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 steals a 456-bit block and is interleaved with the speech. Each burst containing
a FACCH block of information has the appropriate stealing ag 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 rst two bursts, both the
even and odd of the middle two bursts, and the odd bits of the last two bursts.
Rectangular interleaving - control

Figure 3-47 illustrates, in a simplied form, the principle of rectangular interleaving. This is
applied to most control channels.
3-72
68P02900W21-R
GMR-01
Nov 2007
Figure 3-47 Rectangular interleaving control

CONT ROL
BLOCKS
456 BITS
114
BITS
114
BITS
EVEN
ODD
11 4 114
BITS BITS
ODD
EVEN
BURST S
FRAME 1
FRAME 3
FRAME 2
TDMA FRAMES
ti-GS M-Re cta ngula r_inte rle a ving_control-00170-a i-s w
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 contains bits for even or odd bit positions.
The GSM burst is produced using these blocks of control.
Transmission - control
Each burst is 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 to 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 simplied 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.
68P02900W21-R
3-73
GMR-01
Nov 2007
The rst 6 bits from the rst block are placed in the rst burst. The rst 6 bits from the second
block is placed in the second burst and so on. Each 114-bit block is spread across 19 bursts and
the total 456 block is spread across 22 bursts.
Data channels have an interleaving depth of 22, although this is sometimes also referred to as
an interleaving depth of 19.
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 small amount of data from one data block is actually 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 does
not effect the reception quality, whereas with speech, if a delay was 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.
3-74
68P02900W21-R
GMR-01
Nov 2007
Figure 3-48
GPRS channel coding schemes
Diagonal interleaving - CS data
DATA
BLOCKS
45 6 BITS
114
BITS
114
BITS
114
114
FIRST
6
BITS
FIRST
6
BITS
10
114
BITS
114
114
FIRST
6
BITS
FIRST
6
BITS
114
BITS
LAST
6
BITS
LAST
6
BITS
LAST
6
BITS
LAST
6
BITS
11 12 13 14 15 16 17 18 19 20 21 22
ti-GSM-Diagonal_interleaving_CS_data-00171-ai-sw

Four different coding schemes have been dened 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 and CS3) leading to various effective code rates. Coding is not applied to CS4.
68P02900W21-R
3-75
GMR-01
Nov 2007
The following applies to all four coding schemes:
User data (RLC data block, segmented LLC PDUs) and RLC/MAC header are coded
together.
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.
3-76
68P02900W21-R
GMR-01
Nov 2007
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 rst 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 8 kbits/s.
Figure 3-49 GPRS channel coding scheme 1 (CS1)

3 bits
21 bi ts
160 bits
40 bits
US F
RLC/MAC He ader
Da ta
BCS
Block co ded
4 bits
TB
224 bi ts
Ra te 1/ 2 c onvolutional coding
465 bit s
Punctu ring
465 bits
Block inte rleaving over 4 burs ts
114 bit s
114 bi ts
114 bits
114 bits
Mapped to 4 TDMA burst s ; coding s cheme

signall ed t hrough 8 st eali ng b its (2 per burs t)
TB
3 bits
Header & dat a

57 b its
SB
1 bit
TS
26 bits
SB
He a de r & da ta
TB
1 bit
57 bits
3 bits
ti-GS M-GP RS_ cha nne l_coding_s che me _1-00172-a i-s w
68P02900W21-R
3-77
GMR-01
Nov 2007

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 rst 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 12 kbits/s.

6 bits
(pre -co de d)
USF
28 bits
24 0 bits
16 bits
RLC/MAC Head er
Data
BCS
Block code d
4 bits
TB
29 0 bits
Rate 1/2 convolutiona l coding
58 8 bits
Pun cturing
54 6 bits
11 4 bits
11 4 bits
11 4 bits
11 4 bits
Mapp ed to 4 TDMA burs ts ; cod ing s che me

s igna lle d throu gh 8 s te aling bits (2 pe r burs t)
TB
Header & data
SB
TS
3 bits
57 bits
1 bit
26 bits
SB
1 bit
Header & data

57 bits
TB
3 bits
ti-GSM-GPRS_channel_coding_scheme_2-00173-ai-sw
3-78
68P02900W21-R
GMR-01
Nov 2007

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 rst stage of coding, these 318 bits are protected according
to the 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.4 kbits/s.

6 bits
(pre -co de d)
USF
24 bits
28 8 bits
16 bits
RLC/MAC Head er
Data
BCS
Block code d
4 bits
TB
34 4 bits
Rate 1/2 convolutiona l coding
67 6 bits
Pun cturing
45 6 bits
11 4 bits
11 4 bits
11 4 bits
11 4 bits

TB
Header & data
SB
TS
3 bits
57 bits
1 bit
26 bits
SB
1 bit
Header & data

57 bits
TB
3 bits
68P02900W21-R
3-79
GMR-01
Nov 2007

CS4 is the least robust GPRS coding scheme and 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 20 kbits/s.

12 bits
(pre -co de d)
USF
28 bits
40 0 bits
16 bits
RLC/MAC Head er
Data
BCS
Block code d
45 6 bits (0 bits TB)
No c onvolutional cod ing
45 6 bits
No p un cturing
45 6 bits
11 4 bits
11 4 bits
11 4 bits
11 4 bits

TB
Header & data
SB
TS
SB
3 bits
57 bits
1 bit
26 bits
1 bit
Header & data

57 bits
TB
3 bits
All control channels except for the PRACH use CS1. Two types of packet random access burst
are 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.
3-80
68P02900W21-R
GMR-01
Nov 2007
16/32 kbit/s TRAU
GPRS trafc channels use scheme CS1, CS2, CS3, or CS4. This allows the coding scheme to
be dynamically adapted to the channel conditions and thereby maximizing throughput and
optimizing the performance.
Coding schemes CS3 and CS4 are not used before GSR5.1.
USF is the Uplink State Flag, which is transmitted on the downlink and is an invitation to an 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
1/2
2/3
3/4
USF
Pre-coded USF
12
21
28
24
28
181
268
312
428
BCS
40
16
16
16
Tail
456
588
676
456
Punctured bits
132
220
User Data rate at RLC/MAC kbit/s
12
14.4
20
Effective Code rate after 1/2

convolutional coding and puncturing
RLC/MAC header/bits
User bits (RLC blocks; segmented LLC
PDUCs)
Coded bits
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 subrate switched E1 timeslots, which have some signaling 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 trafc. The right (or
auxiliary) channel is used for the larger CS3 and CS4 GPRS TRAU-like frames.
68P02900W21-R
3-81
GMR-01
Nov 2007
EGPRS channel coding schemes
Only one 16 kbit/s timeslot (CIC) is used between the BSC and RXCDR for a CS call,
therefore termination is necessary.

Nine different coding schemes have been dened 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 timeslot (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-82
68P02900W21-R
GMR-01
Nov 2007
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. Extra 12 bits (BCS) for error
detection (used in ARQ) protect the user data. The subsequent 196 bits (including tail bits, FBI
and E bits) are then convolutionally coded, punctured, and interleaved over four bursts. Extra
8 bits (HCS) for error detection protect the header data. 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.8 kbits/s.
Figure 3-53 EGPRS channel coding scheme 1 (MCS-1)

196 bits
3 bits
USF
8 bits 2 bits
28 bits
176 bits
12 bits 6 bits
BCS TB
RLC/MAC Header HCS FBI E Data
Block
coded
12 bits
Rate 1/3 convolutional coding
108 bits
588 bits
Puncturing
SB = 12
12 bits
68 bits
Burst 1
TB
3 bits
P1
P2
372 bits
372 bits
Burst 2
Header & data

57 bits
Burst 3
SB
1 bit
TS
26 bits
SB
1 bit
Burst 4
Header & data

57 bits
TB
3 bits
ti-GSM-EGPRS_channel_coding_scheme_1-00176-ai-sw
68P02900W21-R
3-83
GMR-01
Nov 2007

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. Extra 12 bits (BCS)
for error detection (used in ARQ) protect the user data. The subsequent 244 bits (including
tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four
bursts. Extra 8 bits (HCS) for error detection protect the header data. 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.2 kbits/s.

244 bits
3 bits
USF
8 bits 2 bits
28 bits
224 bits
12 bits 6 bits
BCS TB
Block
coded
12 bits
108 bits
672 bits
Puncturing
SB = 12
12 bits
68 bits
Burst 1
TB
3 bits
P1
P2
372 bits
372 bits
Burst 2
Header & data

57 bits
Burst 3
SB
1 bit
TS
26 bits
SB
1 bit
Burst 4
Header & data

57 bits
TB
3 bits
3-84
68P02900W21-R
GMR-01
Nov 2007

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. Extra 12
bits (BCS) for error detection (used in ARQ) protect the user data. The subsequent 316 bits
(including tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved
over four bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent
36 bits are then convolutionally coded, punctured, and interleaved over four bursts. MCS-3
provides a user data rate (excluding RLC/MAC header) of 14.8 kbits/s.

244 bits
3 bits
USF
8 bits 2 bits
28 bits
224 bits
12 bits
108 bits
672 bits
Puncturing
Puncturing
P1
SB = 12
12 bits
68 bits
Burst 1
TB
3 bits
BCS TB
Block
coded
P2
372 bits
372 bits
Burst 2
Header & data

57 bits
12 bits 6 bits
Burst 3
SB
1 bit
TS
26 bits
SB
1 bit
P3
372 bits
Burst 4
Header & data

57 bits
TB
3 bits
68P02900W21-R
3-85
GMR-01
Nov 2007

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. Extra 12 bits (BCS) for error detection (used in ARQ)
protect the user data. The subsequent 372 bits (including tail bits, FBI and E bits) are then
convolutionally coded, punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error
detection protect the header data. The subsequent 36 bits are then convolutionally coded,
punctured, and interleaved over four bursts. MCS-4 provides a user data rate (excluding
RLC/MAC header) of 17.6 kbits/s.

372 bits
3 bits
USF
8 bits 2 bits
28 bits
352 bits
BCS TB
Block
coded
12 bits
12 bits 6 bits
108 bits
1116 bits
Puncturing
Puncturing
P1
SB = 12
12 bits
68 bits
Burst 1
TB
3 bits
P2
372 bits
372 bits
Burst 2
Header & data

57 bits
Burst 3
SB
1 bit
TS
26 bits
SB
1 bit
P3
372 bits
Burst 4
Header & data

57 bits
TB
3 bits
3-86
68P02900W21-R
GMR-01
Nov 2007

MCS-5 is the most robust coding scheme of the ve 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. Extra 12 bits (BCS) for error detection (used in ARQ) protect the user data.
The subsequent 468 bits (including tail bits, FBI and E bits) are then convolutionally coded,
punctured, and interleaved over four bursts. Extra 8 bits (HCS) for error detection protect the
header data. The subsequent 33 bits are then convolutionally coded, punctured, and interleaved
over four bursts. MCS-5 provides a user data rate (excluding RLC/MAC header) of 22.4 kbits/s.

468 bits
3 bits
USF
25 bits
8 bits 2 bits
99+1 spare bits
1404 bits
No
puncturing
Puncturing
P2
P1
SB = 8
36 bits
Burst 1
TB
9 bits
12 bits 6 bits
BCS TB
Block
coded
36 bits
448 bits
1248 bits
100 bits
Burst 2
Data
156 bits
U SB
12 5 1 bit
bits bits
1248 bits
Burst 3
TS
78 bits
SB U H
1 4 13
bit bits bits
Burst 4
Data
57 bits
TB
9 bits
68P02900W21-R
3-87
GMR-01
Nov 2007

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. Extra 12 bits (BCS)
for error detection (used in ARQ) protect the user data. The subsequent 612 bits (including
tail bits, FBI and E bits) are then convolutionally coded, punctured, and interleaved over four
bursts. Extra 8 bits (HCS) for error detection protect the header data. The subsequent 33 bits
are then convolutionally coded, punctured, and interleaved over four bursts. MCS-6 provides a
user data rate (excluding RLC/MAC header) of 29.6 kbits/s.

612 bits
3 bits
USF
25 bits
8 bits 2 bits
Data
RLC/MAC Header HCS FBI E
Block
coded
36 bits
592 bits
99+1 spare bits
1836 bits
Puncturing
P2
P1
36 bits
Burst 1
TB
9 bits
BCS TB
No
puncturing
SB = 8
12 bits 6 bits
1248 bits
100 bits
Burst 2
Data
156 bits
U SB
12 5 1 bit
bits bits
1248 bits
Burst 3
TS
78 bits
SB U H
1 4 13
bit bits bits
Burst 4
Data
57 bits
TB
9 bits
3-88
68P02900W21-R
GMR-01
Nov 2007

MCS-7 coding scheme is less robust than MCS-5 and MCS-6. It also carries two radio blocks per
20 ms. 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. Extra
12 bits (BCS) for error detection (used in ARQ) protect each user data block. The subsequent
468 bits per radio block (including tail bits, FBI and E bits) are then convolutionally coded,
punctured, and interleaved over two bursts. Extra 8 bits (HCS) for error detection protect the

468 bits
3
bits
USF
37
bits
8
bits
2
bits
RLC/MAC HCS FBI E

Header
Block
coded
36 bits
135 bits
Burst 1
TB
9
bits
153 bit s
2
bits
448
bits
BCS TB FBI E Data
12
bits
6
bits
BCS TB
1404 bits
Puncturing
612 bits
124 bits
Puncturing
P1
P3
P2
Burst 2
Data
Da ta
6
bits
1404 bits
P1
36 bits
12
bits
Puncturing
SB = 8
448
bits
612 bits
612 bits
Burst 3
P2
612 bits
612 bits
P3
612 bits
Burst 4
U SB
TS
SB U
15
bits
5 1
bits bit
78
bits
1 4 16
bit bits bits
Data
TB
153 bit s
9
bits
68P02900W21-R
3-89
GMR-01
Nov 2007

MCS-8 coding scheme carries two user data blocks like 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. Extra 12 bits (BCS) for error detection (used in ARQ) protect each user data
block. The subsequent 564 bits per radio block (including tail bits, FBI and E bits) are then
convolutionally coded, punctured, and interleaved over two bursts. Extra 8 bits (HCS) for error
detection protect the header data. 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.4 kbits/s.

564 bits
3
bits
USF
37
bits
8
bits
2
bits
RLC/MAC HCS FBI E

Header
Block
coded
36 bits
135 bits
Burst 1
TB
9
bits
153 bit s
2
bits
544
bits
BCS TB FBI E Data
12
bits
6
bits
BCS TB
1692 bits
Puncturing
612 bits
124 bits
Puncturing
P1
P3
P2
Burst 2
Data
Da ta
6
bits
1692 bits
P1
36 bits
12
bits
Puncturing
SB = 8
544
bits
612 bits
612 bits
Burst 3
P2
612 bits
612 bits
P3
612 bits
Burst 4
U SB
TS
SB U
15
bits
5 1
bits bit
78
bits
1 4 16
bit bits bits
Data
TB
153 bit s
9
bits
3-90
68P02900W21-R
GMR-01
Nov 2007

MCS-9 coding scheme carries two user data blocks like 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. Extra 12 bits (BCS) for error detection (used in ARQ) protect each
user data block. 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. Extra 8 bits (HCS) for error detection protect the

612 bits
3
bits
USF
37
bits
8
bits
2
bits
RLC/MAC HCS FBI E

Header
Block
coded
36 bits
135 bits
Burst 1
TB
9
bits
153 bit s
2
bits
592
bits
BCS TB FBI E Data
12
bits
6
bits
BCS TB
1836 bits
Puncturing
612 bits
124 bits
Puncturing
P1
P3
P2
Burst 2
Data
Da ta
6
bits
1836 bits
P1
36 bits
12
bits
Puncturing
SB = 8
592
bits
612 bits
612 bits
Burst 3
P2
612 bits
612 bits
P3
612 bits
Burst 4
U SB
TS
SB U
15
bits
5 1
bits bit
78
bits
1 4 16
bit bits bits
Data
TB
153 bit s
9
bits
EGPRS trafc channels use coding schemes MCS-1 to MCS-9. This allows the coding scheme
to be dynamically adapted to the channel conditions like GPRS through the (LA) process (see
Link adaptation (LA) in GPRS/EGPRS on page 3-93 ) and thereby maximizing throughput and
68P02900W21-R
3-91
GMR-01
Nov 2007
64 kbit/s TRAU for EGPRS
optimizing the performance. The IR feature of EGPRS also allows the LA process to be more
aggressive in terms of BLER on the rst transmissions and thereby increasing the utilization of
higher code rates over a larger percentage of a cell.
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
Effective Code rate

after 1/2 convolutional
coding and puncturing
Effective Header
Code rate after 1/2
convolutional coding
and puncturing
1.0
0.92
0.76
0.49
0.37
1.0
0.85
0.66
0.53
0.36
0.36
0.36
1/3
1/3
0.53
0.53
0.53
0.53
8-PSK
Modulation
RLC blocks per Radio
Block (20 ms)
Raw Data within one
Radio Block
Family
2x592 2x544
A
BCS
Tail payload
GMSK
2x448
592
448
352
296
224
176
14.8
11.2
8.8
2x12
12
2x6
HCS
User Data rate at
RLC/MAC kb/s
8
59.2
54.4
44.8
29.6
22.4
17.6
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 subrate switched E1 timeslots, which have some signaling 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 congured as a
PDTCH on the RTF backhaul available for use as Versachannel.
{23769} For EGPRS, any enabled carrier has a certain amount (ranging from 3 to 8 DS0s) of
terrestrial backhaul congured and a portion of this backhaul is used as the Versachannel to
carry the data for the air timeslots congured as PDTCHs. The EGPRS feature needs additional
backhaul to provision EGPRS carriers. The additional backhaul is either 7 DS0s to implement
EGPRS on a BCCH carrier or 8 DS0s to implement EGPRS on a non-BCCH carrier, if VersaTRAU
feature is restricted. If VersaTRAU feature is unrestricted, the backhaul for an EGPRS carrier
can be congured using the rtf_ds0_count parameter.
3-92
68P02900W21-R
GMR-01
Nov 2007
Link adaptation (LA) in GPRS/EGPRS
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 maximizing user or system throughput, under the
constraint of keeping the systems 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 sufcient information and guidelines to facilitate the development of proprietary
algorithms. This is achieved through specic information elements in the various header and
control messages communicated between the 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 specied in the standards.
The LA impact in improving the system performance is greater in EGPRS compared to GPRS
due to:
Higher number of codes, that is, better granularity.
Richer MS measurement reports.
Incremental redundancy (Hybrid ARQ type II).
The LA process uses the measurement reports as inputs to move between various codes per
packet downlink Ack/Nack period. In Motorolas implementation, a code change is applied to
all the blocks and timeslots. In addition, IR is the only mode used in EGPRS, and appropriate
measures are taken to comply with the constraints specied in the standards.
Voice activity detection (VAD)

VAD is a mechanism whereby the source transmitter equipment identies the presence or
absence of speech. VAD implementation is affected 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 the comfort noise, the total silence between the speech would be considered to be
disturbing by the listener.
68P02900W21-R
3-93
GMR-01
Nov 2007

DTX overview
DTX increases the efciency 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 (that is background noise when the 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 are 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 much at the discretion of the network
provider and there are different specications 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
S
A
C
C
H
52-59
S
A
C
C
H
SID
S
A
C
C
H
S
A
C
C
H
103
SID
4 x S ACCH 26 FRAME MU LTIFRAMES (120 m s)

8 x SILENCE DESCRIP TOR (SID)
ti-GSM-SACCH_multiframe_480ms_for_DTX_and_full_rate-00185-ai-sw
3-94
68P02900W21-R
GMR-01
Nov 2007
DTX and GSM half rate

DTX is implemented over a SACCH multiframe (480 ms), as illustrated in Figure 3-63 for each
subchannel. During this time, of the possible 104 frames, only the 4 SACCH frames and 8
Silence Descriptor (SID) frames per subchannel are transmitted.
Figure 3-63 SACCH multiframe (480 ms) for DTX and half rate
52
-89
53
54
55
7...
56
11
57
12
58
13
59 -63
14 15 16 17 18
64
65
66
67
20 21-24
19
68
69
70
71
90
38 39-50
25 26-37
72
91-102
73-76
103
77 78
SACCH (S ub -Chan ne l 0)
PS: In ha lf ra te the re a re 2 s ub cha nne ls a nd in the 104
Multi-fra me , S ub-Cha nne l 0 a nd 1 a re s e nt a lte rna te ly. For e xa mple ,
Fra me 0 will ha ve informa tion for S ub-Cha nne l
0, 1 will be for S ub-Cha nne l 1, 2 for S ub-Cha nne l 0 a nd s o on.
ti-GS M-SACCH_multifra me _480 ms _ for_ DTX_a nd_ha lf_ra te -00186-a i-s w
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.

The receiver to generate comfort noise for the listener during the silence period uses this.
68P02900W21-R
3-95
GMR-01
Nov 2007
Receive diversity
NO_DATA: Non-transmitted block during a silence period.
ONSET: Indicates end of silence period and the start of a speech period.
Unlike full rate or Enhanced full rate DTX, AMR DTX is not designed with xed 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 and seven NO_DATA
sequence repeat for as long as the silence period lasts.
One ONSET DTX block is transmitted immediately before the rst speech block of the new
speech period is sent. This ONSET is interleaved immediately before the rst encoded
speech block.
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 (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 signaling bits to allow link adaptation
to be performed during silence periods (refer to Link adaptation for AMR
channels on page 3-64 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 dened distance apart, then it follows that the probability
of them simultaneously experiencing maximum fade depth at a given frequency is much less
than for the single antenna situation.
3-96
68P02900W21-R
GMR-01
Nov 2007
Receive diversity
There are three ways of utilizing this concept:
The receiver can be switched between the two RF receive paths provided with 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 conguration, it simply selects 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 does not usually have any signicant effect on the mean
depression component of fading, but the use of phase alignment diversity can help increase the
mean signal level received.
In microcellular applications, the M-Cellcity and Horizonmicro or Horizonmicro2

do not support spatial diversity.
Figure 3-64 Receive diversity
MOBILE
ANTENNAS
(approx 10
wavelengths)
S PACE BETWEEN
PATH
LENGTH
IN
WAVELENGTHS
METHODS OF UTILIZ ATION:
a. SWITCHED.
b. PHASE ALIGNED AND SUMMED.
c. PHASE ALIGNED WITH MINIMUM DISTORTION.
BTS
ti-GSM-Receive_diversity-00187-ai-sw
68P02900W21-R
3-97
GMR-01
Nov 2007
Receive diversity
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 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 selected
and the lters set to remove the multipath element from the received signal.
The multipath element can be of benet once it has been identied, as it can then be recombined
with the wanted signal in a constructive way to give a greater received signal strength. Once
the lters have been set, they can be used to lter the random speech data as it is assumed
they 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

Signa l from sh ortest pat h
3 bits
Signa l from d elayed pat h

ti-GSM-Training_sequence_code-00189-ai-sw
3-98
68P02900W21-R
GMR-01
Nov 2007
Subscriber environment
Subscriber environment
Subscriber hardware
System quality (voice quality, for example), system access, and grade of service, as perceived by
the customer, are the most signicant factors in the success of a cellular network. The everyday
subscriber neither knows nor 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 selects the type of
equipment they wish to use on the network. It is up to the network provider to satisfy the
subscriber, whatever they choose. The output power of the mobile subscriber is limited in a
GSM system to a maximum of 8 W for a mobile and a minimum of 0.8 W for a hand portable. For
a DCS1800 system, the mobile subscriber is restricted to a maximum of 1 W and a minimum
of 250 mW hand portable.
Environment
Not only does the network designer have to plan for the subscribers choice of phone, the
designer has to plan for the choice of subscribers as to where they wish to use that phone.
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 rmly
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 oor of a building whether it is 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.
68P02900W21-R
3-99
GMR-01
Nov 2007
Distribution
Figure 3-66 Subscriber environment

URBAN/CITY
ENVIRONMENTS
RURAL AREAS
BUILDINGS
LIFTS
TUNNELS
ti-GSM-Subscriber_environment-00188-ai-sw
Distribution
Not only do network designers have to identify the types of subscriber that use the cellular
network now and in the future, but also at what location these subscribers are attempting
to use their phones.
Dense urban environments need 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 trafc is not necessarily evenly distributed. As Figure 3-67 illustrates, an urban area can
contain sub-areas of uneven distribution such as a business or industrial district, and has to plan
for a seasonal increase of trafc due to, for example, a convention centre. It is vitally important
that the trafc distribution is known and understood before network design, to ensure that a
successful quality network is implemented.
3-100
68P02900W21-R
GMR-01
Nov 2007
Figure 3-67
Hand portable subscribers
Subscriber distribution
HIGH SP EED MOBILES
(RAILWAYS )
RURAL
URBAN
BUS INES S AREAS

40%
ROAD/RAIL
NETWORK
INDUSTRIAL
20%
EXHIBITIONS
10%
RE S IDENTIAL
30%
S UBS CRIBERS DIS TRIBUTION CHANGES ON A HOURLY BAS IS

ti-GSM-Subscriber_distribution-00190-ai-sw
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 users, and hence the network designers, must recognize this.
Before commencing the network design based around hand portable coverage, the network
designer must rst understand the limitations of the hand portable unit and secondly, what the
hand portable actually needs 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.
The 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.
Therefore, 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 from not only an interference point of view, but also helps
to extend the available talk time of the subscriber unit, which is limited by battery life.
68P02900W21-R
3-101
GMR-01
Nov 2007
Future planning
Future planning
Normal practice in network planning is to select one point of a well-known re-use model as a
starting point. Even at this early stage, the model must be improved because any true trafc
density does not follow the homogeneous pattern assumed in any theoretical models.
Small-sized heavy trafc concentrations are characteristic of the real trafc distributions.
Another well-known trafc characteristic feature is the fast descent in the density of trafc
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 leads to a
wasteful frequency plan. This is because 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 efciency, is to enlarge the cell size gradually from small cells into larger cells.
In most cases, the trafc 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 trafc 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 neighboring cells need the same amount of channels. It must always be kept in mind that
the values calculated for future trafc distribution are only crude estimates and that the real
trafc distribution always deviates from these estimates. In consequence, the network plan
should be exible enough to allow for rearrangement of the network to meet the real trafc
needs.
Conclusion
In conclusion, there are no xed rules for radio network planning. It is a case of experimenting
and reiterating. By comparing different alternatives, the network designers should nd a plan
that both fulls 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-102
68P02900W21-R
GMR-01
Nov 2007
Microcellular solution
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 trafc 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
S IDE VIEW
MACROCELL
MICROCELL A
MICROCELL B
ti-GSM-Layered_architecture-00191-ai-sw
68P02900W21-R
3-103
GMR-01
Nov 2007
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 vendor networks.
Figure 3-69

UNDERLAYED
MICR OC ELL (CO ULD BE A
DIFFERENT VENDOR)
OVER LAYED MACR OC ELLS
CO NTIGUOUS COVERAGE OVER AREAS OF

HIGH S LOW MOVING TRAFFIC DENS ITY
ti-GSM-Combined_cell_architecture-00192-ai-sw
Macrocells: Implemented specically to cater to the fast-moving MSs and to provide a fallback
service for coverage of holes and pockets of interference in the microcell layer. Macrocells
form an umbrella over the smaller microcells.
Microcells: Microcells handle the trafc from slow-moving MSs. The microcells can give
contiguous coverage over the required areas of heavy subscriber trafc.
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.
3-104
68P02900W21-R
GMR-01
Nov 2007
Combined cell architecture structure
Figure 3-70 Combined cell architecture structure

LINK TO IMPLEMENT MICROCELLS AS A SE PARATE SYSTEM
ALTERN ATIVE SYSTEM (MICROCELLS CONTROLLED BY THE SAME BSC AS MACROCELLS)
MSC
BSC A
SYSTEM 2
MICROCELL
BSC B
SYSTEM 1
MACROCELL
BTS 1
BTS 5
BTS 2
BTS 4
BTS 3
MICROCELL
COVERAGE
MACROCELL COVERAGE
SYSTEM 1 = OVER LAY SYSTEM

SYSTEM 2 = UNDER LAY SYSTEM
ti-GSM-Combined_cell_architecture_structure-00193-ai-sw
Macrocell and microcell networks are operated as individual systems.
The macrocell network is more dominant as it handles the greater amount of

trafc.
Microcells can be underlaid into existing networks.
68P02900W21-R
3-105
GMR-01
Nov 2007
Expansion solution
Expansion solution
As the GSM network evolves and matures, its trafc loading increases as the number of
subscribers grow. Eventually a network reaches a point of trafc saturation. The use of
microcells can provide high trafc capacity in localized areas.
The expansion of a BTS site past its original designed capacity can be a costly exercise and the
frequency re-use implications require 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 trafc hotspots or a contiguous cover of cells in a combined
architecture. The increased coverage gives greater customer satisfaction.
3-106
68P02900W21-R
GMR-01
Nov 2007
Frequency planning
Frequency planning
Introduction
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 the 9dB specication of GSM.
The actual plan of a real network is a function of its operating environment (geography, RF and
so on) 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

m channels
n channels
TCH
BCCH
Gua rd Ba nd
ti-GSM-Separating_BCCH_and_TCH_bands-00194-ai-sw
The benets are as follows:
Makes 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

Mac ro BC CH
Micro
Ma cro TCH
Micro TCH
BCCH
(S FH)
ti-GSM-Band_usage_for_macrocells_with_microcells-00195-ai-sw
68P02900W21-R
3-107
GMR-01
Nov 2007
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 are 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 in unacceptable quality. Some
commonly used loading factors (sometimes termed as fractional load factors) are 40%,
33%, 25% and so on.
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 helps to randomize the co-channel interference level between the sites.
Use different MAIOs to control adjacent channel interference between the sectors within a
site.
Mobile Allocation (MA) is the set of frequencies that the mobile or BTS
is allowed to hop over. Two timeslots on the same transceiver of a cell are
congured to operate on different MAs. MA is the subset of the total allocated
spectrum for the GSM user 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 is 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 dened
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.
3-108
68P02900W21-R
GMR-01
Nov 2007
Motorola denes a Frequency Hopping Indicator (FHI) that is made up of the

three GSM dened parameters. Up to 4 different FHIs can be dened for a cell
in a Motorola BSS and every timeslot on a transceiver can be independently
assigned one of the dened 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.
TCH re-use planning example
Bandwidth: 10 MHz
Site conguration: 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 chann els
Mac ro BCC H
Micro
Macro TCH
Micro TCH
BCCH
(S FH)
12 channels
27 channels
ti-GSM-Frequency_split_for_TCH_re-use_planning_example-00196-ai-sw
A total of 49 channels are available and the rst 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 conguration, 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,

39, 42, 45
Any from {1, 2, 63}
0, 2, 4
Sector B
22, 25, 28, 31, 34, 37,

40, 43, 46
Same as above
1, 3, 5
Sector C
23, 26, 29, 32, 35, 38,

41, 44, 47
Same as above
0, 2, 4
68P02900W21-R
3-109
GMR-01
Nov 2007
The MAIO setting avoids all possible adjacent channel interference among sectors within the
same site. The interference (co or adjacent channel) between sites still exists but it is reduced
by the randomization effect of the different HSNs.
Practical rules for TCH 1x1 re-use pattern
1x1 is practical in rural area of low trafc density, where the average occupancy of the
hopping frequencies is low. With careful planning, it can be used in high trafc 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 conguration, 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.
3-110
68P02900W21-R
GMR-01
Nov 2007
Rules for BaseBand Hopping (BBH)
Figure 3-74 Avoiding co-channel and adjacent channel interference

1
Diffe re nt MAIOs to
avoid co-cha nne l
inte rfe re nce
13
HSN = 1
15
11
HSN = 1
17
HS N = 1
Non adj ace nt MAIOs to

avoid adjacen t channe l
inter fer enc e
ti-GSM-Avoiding_co-channel_and_adjacent_channel_interference-00197-ai-sw

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 is not essential.
An example of frequency spectrum allocation is shown in Figure 3-75.
Figure 3-75 BBH frequency spectrum allocation

Micro BCCH
BBH cha nne ls a nd micro TCH

ti-GSM-BBH_frequency_spectrum_allocation-00198-ai-sw
{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 congured in the MA list.
68P02900W21-R
3-111
GMR-01
Nov 2007
For effective utilization of the ITS feature and to maintain stability, it is recommended to use the
parameter re_rtf_id to map the DD CTU2 Carrier A to 64 k RTF and exclude these ARFCNs
from the MA list if BBH must be applied for the cell.
3-112
68P02900W21-R
GMR-01
Nov 2007
Inter-radio access technology (2G-3G) cell reselection and handovers
Inter-radio access technology (2G-3G) cell reselection

and handovers
{22879}
Introduction
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 the manual 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 soon allows 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 neighbors) and GERAN in idle mode.
Handovers between 3G (UMTS-FDD) and 2G (GSM) in active mode.
Restriction
There is currently an upper limit of 32 FDD UTRAN neighbors in the GSM/GPRS system.
68P02900W21-R
3-113
GMR-01
Nov 2007
Impact of 2G-3G handovers on GSM system architecture
Implementation
The BSS Inter-RAT handover GSM function is an option that must be unrestricted by Motorola.
It also needs unrestricting on site by the operator 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 an environment the call would drop when a UMTS
subscriber goes out of a UMTS coverage area and into a GSM coverage area.
Congestion in the smaller UMTS areas could become a problem when the trafc in the UMTS
coverage area is high. A GSM subscriber may wish to access a service with specic QoS
characteristic (for example, high bit rate data service) that may not be supported in the GSM
system.
To avoid these problems the operator may wish to congure 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.
3-114
68P02900W21-R
GMR-01
Nov 2007
System consideration
Figure 3-76 GSM and UMTS system nodes and interfaces

E-Inter face
GSM Core Net work
(MSC/GSN)
A-Interface
UMTS Core Net work

(3G MSC/SGSN)
Gn-Int er face
Iu-Cs-Inter face
Gb-Inter face
Iu-Ps--Inter face
GSM/GPR S
UTRAN
PCU
BSS
RNS
RNS
RNC
BSC
Iub
Abis
BTS
BTS
Node B
Um
Iur
RNC
Iub
Node B
Uu
Multi-RAT MS
ti-GSM-GSM_and_UMTS_system_nodes_and_interfaces-00199-ai-sw
System consideration
Existing 2G CoreNetwork (CN) nodes must be able to interact with the 3G CN nodes through
MAP procedures dened 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 neighbor cells or CDMA2000 neighbor cells.
Extended measurement reporting.
Enhanced measurement reporting.
Blind handovers.
The sending of SI2quater on extended BCCH.
The BSS restricts the maximum number of UTRAN neighbors per GSM cell to 32.
68P02900W21-R
3-115
GMR-01
Nov 2007
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 conguration of the BSC required to support a given BSS.
Typical call parameters

The number of control channels required at a BTS depends 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 signaling trafc model
Parameter reference
Call duration
T = 120 seconds
Ratio of SMSs per call
S = 0.1
H = 2.5
Ratio of location updates to calls: non-border

location area
l=2
Ratio of location updates to calls: border

location area
l=7
Ratio of IMSI detaches to calls
I=0
Location update factor: non-border location

area
L=2
Location update factor: border location area
L=7
GSM circuit-switched paging rate in pages per

second
PGSM = 15
Ratio of intra-BSC handovers to all handovers
i = 0.6
Ratio of LCSs per call
Lcs = 0.2
Mobile terminated LCS ratio
LRMT = 0.95
Mobile originated LCS ratio
LRMO = 0.05
Percent link utilization (MSC to BSS) for

GPROC2/GPROC3
U(MSC - SS) = 0.20
Percent link utilization (BSC to BTS)
U(BSC - BTS) = 0.25
Percent link utilization (BSC to RXCDR)
UBSC-RXCDR = 0.4
Continued
3-116
68P02900W21-R
GMR-01
Nov 2007
Table 3-12 Typical parameters for BTS call planning (Continued)

Busy hour peak signaling trafc model
Parameter reference
Percent link utilization (BSC to SMLC) for

GPROC2/GPROC3
UBSC-SMLC = 0.2
Percent CCCH utilization
UCCCH = 0.33
Block Rate for TCHs
PB-TCHs = 2%
Block Rate for MSC-BSS trunks
PB-Trunks = 1%
Number of cells per BTS
CBTS = 3
Average SMS message size (payload only)
SMSSIZE = 100 bytes
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
GPRS parameters
GPRS Average packet size (bytes)
PKSIZE = 270
GPRS Trafc per subscriber /BH (kbytes/hr)

- Uplink
ULRATE = 30
GPRS Trafc per subscriber /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
Routing area update
RAU = 1.5
GPRS paging rate in pages per second
PGPRS = 3
Coding scheme rates (CS1 to CS4) at the

RLC/MAC layer
CS1
CS2
CS3
CS4
Cell updates (per sub/BH)
CellUpdate = 1.5
EGPRS coding scheme rates (MCS-1 to

MCS-9) at the RLC/MAC layer
MCS1
MCS2
MCS3
MCS4
MCS5
MCS6
MCS7
MCS8
MCS9
68P02900W21-R
= 9.2 kbit/s
= 13.6 kbit/s
= 15.8 kbit/s
= 21.8 kbit/s
= 10.55 kbit/s
= 12.95 kbit/s
= 16.55 kbit/s
= 19.35 kbit/s
= 23.90 kbit/s
= 29.60 kbit/s
= 31.10 kbit/s
= 46.90 kbit/s
= 61.30 kbit/s
3-117
GMR-01
Nov 2007
Number of handovers per call and ratio of intra-BSC handovers to all handovers
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 rst formula given . When IMSI detach is enabled, the second or third of the formulas given
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 *
If IMSI detach type 2 is enabled: L = I + 0.5 *
3-118
68P02900W21-R
GMR-01
Nov 2007
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
GPRS/EGPRS denes several new radio channels and packet data trafc 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 on BCCH or PDTCH.
Packet Notication CHannel (PNCH)

Downlink only. Used to notify the MS of a PTM-M. This is not used in the rst GPRS/EGPRS
release.
Packet Paging Channel (PPCH)

Downlink only, mapped on DTCH 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 Trafc CHannel (PDTCH)

A PDTCH corresponds to the resource allocated to a single MS on one physical channel for
user data transmission.
68P02900W21-R
3-119
GMR-01
Nov 2007
Planning considerations
Packet Dedicated Control CHannels (PDCCHs)
Packet Associated Control CHannel (PACCH)

The PACCH is bi-directional. It is used for MS-PCU control signaling 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.
In planning the GSM/GPRS/EGPRS control channel conguration, the network planner must
consider three main variables:
Signaling requirements of the CCCH
Signaling requirements of the PCCCH (if enabled)
Signaling requirements of the SDCCH
SDCCH planning can be done independently, but CCCH planning depends on PCCCH planning.
It is assumed that by adequate provisioning of the downlink part of the CCCH or PCCCH, the
uplink part is implicitly provisioned with sufcient capacity.
CCCH and PCCCH planning

When PCCCH is disabled (pccch_enabled is set to zero), all control signaling for GSM and
GPRS/EGPRS occur on the CCCH. When PCCCH is enabled, control signaling for GPRS/EGPRS
occurs on the PCCCH instead of the CCCH. Thus, CCCH signaling 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 should monitor paging channels on both
PCCCH and CCCH.
Network Operation Mode II is currently not supported in the Motorola BSS.
3-120
68P02900W21-R
GMR-01
Nov 2007
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 signaling capacity requirements.
Figure 3-77 CCCH and PCCCH decision tree
pccch_e na bled = 1
pccch_e na bled = 0
(1) Decide whe the r or not pa ging co ordina tion will be us e d in the ne twork.
(2) Calcula te the numbe r of CCCHs pe r BTS ce ll whe n P CCCH is e na ble d.
(3) Calcula te the numbe r of P RACH blocks pe r BTS ce ll.
(4) Calcula te the numbe r of PAGCHblocks pe r BTS ce ll.
(5) Calcula te the numbe r of P P CH blocks pe r BTS ce ll.
(6) Calcula te the numbe r of P BCCH blocks pe r BTS ce ll.
Calcula te the numbe r of CCCHs pe r BTS ce ll whe n P CCCH is dis a ble d.

ti-GSM-CCCH_and_PCCCH_decision_tree-00201ai-sw
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.
The use of a combined BCCH is desirable because it permits the use of only one timeslot on
a carrier that is used for signaling. A combined BCCH can offer four more SDCCH blocks for
use by the GSM circuit-switched signaling trafc. If more than an average of three CCCH
blocks, or more than four SDCCH blocks, are required to handle the signaling 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 signaling. In this case, it is 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 trafc 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
signaling load.
68P02900W21-R
3-121
GMR-01
Nov 2007
Number of CCCHs and PCCCHs per BTS cell

The following factors should be considered when calculating the number of CCCHs per BTS cell
are as follows:
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 signaling 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 trafc requirement, the CCCH can share its timeslot with SDCCHs
(combined BCCH). If the CCCH carries high trafc, 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 congurations would only be required for
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.
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 or immediate assignment reject message
can be sent instead.
3-122
68P02900W21-R
GMR-01
Nov 2007
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 subchannel there are always paging messages
(that is high paging load) waiting to be sent, no immediate assignment or immediate
assignment reject messages are sent on that CCCH subchannel. Hence the option to
reserve CCCH channels for AGCH.
It can normally be assumed that sufcient capacity exists on the uplink CCCH (RACH) once
the downlink CCCH is correctly dimensioned.
Some other parameters can be used to congure 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 subchannel 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 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.
The time MS must wait between repetitions on the RACH.
Precise determination of the CCCH requirements is difcult. However, some statistics can
be collected (for example ACCESS_PER_PCH, ACCESS_PER_AGCH) by the BSS and can be
used to determine the CCCH loading and hence perform adjustments.
Calculating 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.
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. Enable PCCCH in
cells with heavy paging.
68P02900W21-R
3-123
GMR-01
Nov 2007
The following planning actions are required:
In the following paragraphs, GPRS notation represents GPRS/EGPRS.

Determine the number of CCCHs per BTS. The average number of blocks required to support
AGCH and PCH is given by the following equation:
The average number of blocks required to support AGCH and PCH is given by the following
equation:
The average number of blocks required to support AGCH only is given by the following equation:
The average number of blocks required to support AGCH for GSM trafc is given by the
following equation:
The number of access grants per AGCH block is 2.
The average number of blocks required to support AGCH for GPRS/EGPRS trafc is given
by the following equation:
Where:
3-124
68P02900W21-R
GMR-01
Nov 2007
The access grant rate is given by the following equation:
The call rate (calls per hour) is given by the following equation:
The location update rate (LU per hour) is given by the following equation:
The SMS rate (SMSs per hour) is given by the following equation:
The LCS rate (LCSs per hour) is given by the following equation:
The average number of blocks required to support PCH only is given by the following equation:
The average number of blocks required to support GSM CS paging only is given by the following
equation:
The number of pages per paging PCH block depends on whether paging is performed using
TMSI or IMSI.
For TMSI paging: N
For IMSI paging: N
pages/Block
pages/Block
=4
=2
The number of paging blocks required at a cell to support GPRS/EGPRS is given by:
68P02900W21-R
3-125
GMR-01
Nov 2007
Where:
Is:
UCCCH
CCCH utilization.
lAGCH
access grant rate (per second).
GPRS_Users
Avg_Sessions_per_user
lcall
number of GPRS and EGPRS users on a cell.

average number of sessions originated by user per busy hour
(this includes the sessions for signaling).
call arrival rate per second.
lL
location update rate per second.
lS
number of SMSs per second.
number of Erlangs per cell.
average call length, in seconds.
PGSM
number of GSM circuit-switched trafc pages transmitted to

a BTS cell per second.
PGPRS
number of GPRS or EGPRS pages transmitted to a BTS cell per

second.
Table 3-13 provides the control channel congurations.
Table 3-13 Control channel congurations

Timeslot 0
Other timeslots
Comments
1 BCCH + 3 CCCH +
4 SDCCH
N x 8 SDCCH
Combined BCCH. The other

timeslot may or may not be
required, depending on the
support of circuit-switched
trafc where the value of N
is 0.
1 BCCH + 9 CCCH
N x 8 SDCCH
Non-combined BCCH. The

value of N is 1.
1 BCCH + 9 CCCH
N x 8 SDCCH, 9 CCCH
Non-combined BCCH. This

is an example of one extra
timeslot of CCCHs added in
support of GPRS trafc. The
value of N is 1.
Calculating 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 and Network Operation Mode is I,
then circuit-switched pages for Class A and Class B mobiles (mobiles that are capable of both
GSM and GPRS) and pages for EGPRS mobiles are sent on the PCCCH instead of the CCCH.
Regardless of paging coordination though, all GPRS/EGPRS control signaling occurs on the
PCCCH. Hence, the following planning rules should be used.
3-126
68P02900W21-R
GMR-01
Nov 2007
The average number of blocks required to support AGCH, NCH and PCH is given by the
following equation:
The average number of blocks required to support AGCH and PCH is given by the following
equation:
The average number of blocks required to support AGCH only is given by the following equation:
The number of access grants per AGCH block is 2.
The location update rate (LU per hour) is given by the following equation:
The SMS rate (SMSs per hour) is given by the following equation:
The LCS rate (LCSs per hour) is given by the following equation:
68P02900W21-R
3-127
GMR-01
Nov 2007
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 the following equation:
If paging coordination is enabled, the average number of blocks required to support GSM
CS paging is given by the following equation:
The number of pages per paging PCH block depends on whether paging is performed using
TMSI or IMSI.
For TMSI paging: N
For IMSI paging: N
pages/Block
pages/Block
=4
=2
The number of paging blocks required at a cell to support GPRS/EGPRS is given by the
following equation:
Where:
Is:
UCCCH
CCCH utilization.
lAGCH
access grant rate (per second).
P
lcall
paging rate per second.

lL
location update rate per second.
lS
number of Erlangs per cell.
average call length, in seconds.
PGSM
the number of GSM circuit-switched trafc pages transmitted to a

BTS cell per second.
NGSM_Only_MS
number of mobiles in the system that do not support GPRS/EGPRS
NGSM_Capable_MS
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.
3-128
68P02900W21-R
GMR-01
Nov 2007
Number of PCCCHs per BTS cell

The network planner can provision up to 1 PCCCH timeslot per BTS cell. If the PCCCH is
enabled, then the PCCCH occupies a reserved PDTCH timeslot on the BCCH carrier. 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 can reserve 1 to 12 of the radio blocks on the uplink PCCCH as PRACH,
For GPRS/EGPRS random access, using the cells 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 can 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 signaling. The PCCCH timeslot is used for user
data for up to 2 mobiles.
For the subsequent calculations, the message capacity for each PCCCH block is 1 message per
0.240 second.
To 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 cells bs_prach_blks parameter.

bs_prach_blk = Roundup(NPRACH)
68P02900W21-R
3-129
GMR-01
Nov 2007
The average number of blocks required to support PRACH is given by the following equation:
The average number of PRACH arrivals per second is given by the following equation:
Where:
UCCCH
GPRS_RACH/sec
GPRS_Users
Is:
desired PCCCH utilization.
GPRS/EGPRS random access rate (per second).
Calculating 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 cells bs_pag_blk parameter.
bs_pag_blk = Roundup(NPAGCH)
The average number of blocks required to support PAGCH is given by the following equation:
The average number of PAGCH arrivals per second is given by the following equation:
Where:
UCCCH
GPRS_RACH/sec
GPRS_Users
Is:
GPRS/EGPRS random access rate (per second).
3-130
68P02900W21-R
GMR-01
Nov 2007
Calculating the number of PPCH blocks per BTS cell

The average number of blocks required to support PPCH is given by:

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 following equation:
The average number of PPCH blocks required to support GPRS/EGPRS paging only is given
Where:
UCCCH
NGSM_GPRS_MS
NALL_MS
Is:
number of mobiles in the system that are capable of both GSM and
GPRS/EGPRS services.
total number of mobiles in the system.
PGSM
number of GSM circuit-switched trafc pages transmitted to a BTS

cell per second PGPRS number of GPRS/EGPRS pages transmitted
to a BTS cell per second.
PGPRS
the number of GPRS/EGPRS pages transmitted to a BTS cell per

second.
68P02900W21-R
3-131
GMR-01
Nov 2007
User data capacity on the PCCCH timeslot
Selecting 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 cells bs_pbcch_blks parameter.
An allocation of 4 PBCCH blocks minimizes the time required for the mobile to acquire the
GPRS/EGPRS broadcast system information of the cell. In turn, this minimizes the delay before
the mobile can start data transmission upon cell selection or 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 choosing the number of PBCCH
blocks per BTS cell is a trade-off between the data transmission delay following cell selection or
reselection against radio resources available for PPCH, PAGCH, and PDTCH.
The number of PCCCH blocks available for PBCCH is given by the following equation:
AvailablePBCCH = 12 Roundup(NPAGCH) Roundup(NPPCH)
So, the network planner must select the number of PBCCH block (NPBCCH) such that it does
not exceed the blocks available (maximum of 4 blocks). The network planner must also consider
the trade-off with PDTCH capacity on the PCCCH timeslot.
It is recommended that the network planner maximize the PBCCH blocks instead of PDTCH
capacity on the PCCCH timeslot. The PCCCH timeslot is only 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 or reselection. The network user chooses to prioritize PDTCH capacity when only
a single PDTCH exists in the cell, that is, the PCCCH timeslot is the only GPRS/EGPRS timeslot.
User data capacity on the PCCCH timeslot

The PCCCH timeslot can support user data trafc (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. If other PDTCHs are available in the cell,
PDTCHs are 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 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.
The raw downlink PDTCH capacity is given by the following equation:
The raw uplink PDTCH capacity is given by the following equation:
3-132
68P02900W21-R
GMR-01
Nov 2007
Number of SDCCHs per BTS cell
Where:
TS_Data_Rate
Is:
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
In this case, the average data rate is calculated as follows:
So the raw data capacity for the downlink PCCCH can be calculated using the following equation:

Determining the SDCCH requirement is an important part of the planning process. The SDCCH
is where a large portion of signaling 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 user congurable 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 require to be accounted for. Refer to the equations
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 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 takes place over the TCH, and does not need the use of an SDCCH. Further, if
the network is congured to send SMS over GPRS, SMS does not need the use of a SDCCH.
Calculating the number of SDCCHs required is necessary for each cell at a BTS site.
68P02900W21-R
3-133
GMR-01
Nov 2007
The equation for NSDCCH is used to determine the average number of SDCCHs.
There is a limit of 124 or 128 SDCCHs (depending on whether control channels are
combined or not) per cell. This limits the number of supportable TCHs within a cell.
A change in the call model also affects 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-15 and Table 3-16 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.
The number of TCHs in a cell vary depending upon the number of carriers that are (AMR
or GSM) half rate capable. The number of calls that use the half rate capable carriers
varies depending upon such factor as cell loading, mobile penetration and so on. In
Table 3-15 and Table 3-16, 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 is higher for sites located on the borders of location areas,
as compared to inner sites of a location area (refer to Figure 3-78).
Figure 3-78 Location area diagram
BORDER BTS =
INNER BTS =
LOCATION AREA
ti-GSM-Location_area_diagram-00202-ai-sw
3-134
68P02900W21-R
GMR-01
Nov 2007
Calculating the number of SDCCHs per BTS cell

Determine the number of SDCCHs per BTS cell. The average number of SDCCHs is given
{24620}
Where:
Is:
NSDCCH
average number of SDCCHs.
lcall
Tc
time duration for call set-up.
Tu
the Fast Call Setup component. This is set to 1 if Fast Call Setup is
disabled or not purchased otherwise this is set to (100 - TCH usage
threshold)/100.
lL
location update rate.
TL
time duration of location updates.
Tg
guard time for SDCCH.
lS
TS
time duration of SMS (Short Message Service set-up).
lLCS
number of LCSs per second.
TLCS
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.
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).
PBCCH: If PBCCH is congured, the NON BCCH carrier has preference over the BCCH
carrier.
Number of available TCH barred timeslots: Available TCH barred timeslots are TCH barred
timeslots which are not congured as SDCCH timeslots yet. TCH or PDTCH cannot be
congured 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.
PGSM/EGSM: The PGSM carrier is preferred over EGSM carriers.
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.
Half Rate: Non Half Rate carriers are preferred over Half Rate capable carriers.
68P02900W21-R
3-135
GMR-01
Nov 2007
Control channel congurations
Sdcch loading (Not the db parameter sd_load, but the actual number of SDCCH timeslots
congured). Carriers with fewer sdcch loading are selected 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
congured as SDCCH in a single carrier.
Carrier id: Carrier id is used as a tie breaker among two carriers. Carrier with lower
carrier id is selected over carrier with higher carrier id.
SDCCH conguration 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 congures at the system
initialization time.
When channel_reconguration_switch is enabled, then based on SDCCH usage, the TCH in
the cell can be recongured to SDCCH up to max_number_of_sdcchs based on need.
When SDCCH blocking is perceived to be high at a cell, 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. Table 3-14 provides a set of example congurations.
Table 3-14 Example Congurations

Number of
SDCCH/ cell
SDCCH
on BCCH
carrier
SDCCH
on second
carrier
SDCCH
on third
carrier
SDCCH
on fourth
carrier
SDCCH
on fth
carrier
SDCCH
on sixth
carrier
60
12
16
16
16
64
16
16
16
92
12
16
16
16
16
16

Table 3-15 and Table 3-16 give typical control channel congurations 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 congurations for non-border location area

Table 3-15 shows the congurations for non-border location area cell, where the ratio of location
updates to calls is 2.
3-136
68P02900W21-R
GMR-01
Nov 2007
Table 3-15 Control channel congurations for non-border location area

Number of
RTFs
Number of
TCHs
Number of
Erlangs
Number of
SDCCHs
1 fr
2.94
1 hr
12
2 fr
Timeslot utilization
Timeslot 0
Other timeslots
1 BCCH +3
CCCH + 4
SDCCH
N/A
6.61
1 BCCH + 9
CCCh
8 SDCCH
14
8.20
1 BCCH + 9
CCCh
8 SDCCH
1 fr
1 hr
22
14.90
1 BCCH + 9
CCCH
8 SDCCH
2 hr
28
20.15
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
3 fr
22
14.9
1 BCCH + 9
CCCH
8 SDCCH
2 fr
1 hr
30
21.93
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
1 fr
2 hr
38
29.2
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
3 hr
42
32.84
16
1 BCCH + 9
CCCH
2 * 8 SDCCH
4 fr
30
21.9
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
3 fr
1 hr
38
29.2
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
5 fr
38
29.2
12
1 BCCH + 3
CCCH + 4
SDCCH
8 SDCCH
6 fr
45
35.6
16
1 BCCH + 9
CCCH
2 * 8 SDCCH
5 fr
1 hr
53
43.1
16
1 BCCH + 9
CCCH
2 * 8 SDCCH
3 fr
3 hr
68
57.2
20
1 BCCH + 9
CCCH
3 * 8 SDCCH
6 hr
88
73.4
24
1 BCCH + 9
CCCH
3 * 8 SDCCH
7 fr
53
43.1
16
1 BCCH + 9
CCCH
2 * 8 SDCCH
Continued
68P02900W21-R
3-137
GMR-01
Nov 2007
Table 3-15
Control channel congurations for non-border location area (Continued)
Number of
RTFs
Number of
TCHs
Number of
Erlangs
Number of
SDCCHs
8 fr
60
49.6
9 fr
68
10 fr
76
Timeslot 0
Other timeslots
20
1 BCCH + 9
CCCH
3 * 8 SDCCH
57.23
20
1 BCCH + 9
CCCH
3 * 8 SDCCH
64.9
20
1 BCCH + 9
CCCH
3 * 8 SDCCH
The CBCH reduces the number of SDCCHs by one and needs another channel.
Control channel congurations for border location area

Table 3-16 shows the congurations for the border location area cell, where the ratio of location
updates to calls is 7.
Table 3-16 Control channel congurations for border location area

Number
of RTFs
Number
of TCHs
Number of
Erlangs
Number of
SDCCHs
1 fr
2.28
1 BCCH + 9
CCCH
8 SDCCH
1 hr
12
6.61
12
1 BCCH +3
CCCH + 4
SDCCH
8 SDCCH
2 fr
14
8.2
12
{26987} 1 BCCH
+3 CCCH + 4
SDCCH
8 SDCCH
1fr
1hr
21
14.0
16
1 BCCH +
3 CCCH+ 4
SDCCH
2 * 8 SDCCH
2 hr
26
18.4
20
1 BCCH +
3 CCCH+ 4
SDCCH
2 * 8 SDCCH
3 fr
21
14
16
1 BCCH + 9
CCCH
2 * 8 SDCCH
2 fr
1hr
29
21
20
1 BCCH +
3 CCCH+ 4
SDCCH
2 * 8 SDCCH
Timeslot 0
Other
timeslots
Continued
3-138
68P02900W21-R
GMR-01
Nov 2007
Table 3-16 Control channel congurations for border location area (Continued)
Number
of RTFs
Number
of TCHs
Number of
Erlangs
Number of
SDCCHs
1 fr
2hr
36
27.3
24
1 BCCH +
9CCCH
3 * 8 SDCCH
3 hr
40
31
28
1 BCCH +
3 CCCH+ 4
SDCCH
3 * 8 SDCCH
4 fr
29
21
20
1 BCCH +
3 CCCH+ 4
SDCCH
2 * 8 SDCCH
3 fr
1 hr
36
27.3
24
1 BCCH +
9CCCH
3 * 8 SDCCH
5 fr
36
27.3
24
1 BCCH +
9CCCH
3 * 8 SDCCH
6 fr
44
33.8
28
1 BCCH + 9
CCCH
4 * 8 SDCCH
5 fr
1 hr
51
41.2
32
1 BCCH + 9
CCCH
4 * 8 SDCCH
3 fr
3 hr
66
55.3
40
1 BCCH + 9
CCCH
5 * 8 SDCCH
7 fr
51
41.2
32
1 BCCH + 9
CCCH
4 * 8 SDCCH
8 fr
58
47.8
36
1 BCCH +
9CCCH
5 * 8 SDCCH
9 fr
66
55.3
40
1 BCCH + 9
CCCH
5 * 8 SDCCH
10 fr
73
62
44
1 BCCH + 9
CCCH
6 * 8 SDCCH
Timeslot 0
Other
timeslots
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.
For the ITS feature, to congure more EGPRS PDs on DD CTU2 Carrier A, set
sd_priority to lowest value and set sd_load to 0 for both carrier A and B.
68P02900W21-R
3-139
GMR-01
Nov 2007
GPRS/EGPRS trafc planning
GPRS/EGPRS trafc 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 weighing 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, SIP signaling 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 specic statistics, and
GSN (SGSN + GGSN) statistics.
Network planning ow
The following sections are presented in support of the GPRS/EGPRS network planning:
GPRS/EGPRS network trafc estimation and key concepts

This section introduces 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 content is dedicated to the discussion of this topic.
GPRS/EGPRS air interface 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.
3-140
68P02900W21-R
GMR-01
Nov 2007
GPRS/EGPRS network trafc estimation and key concepts
GPRS/EGPRS network trafc estimation and key

concepts
Introduction
Packet data notation is interchangeably used in this section.

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 trafc 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 trafc estimation process starts by looking at the per cell GPRS/EGPRS
data trafc prole such as eet management communications, E-mail communications, web
browsing, audio/video playing, PoC service and large le transfers. Once a typical data trafc
prole mix is determined, the required network throughput per cell can be calculated as
measured in kbit/s. 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 modeling 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 le
of arbitrary length. In order to simulate the delay, the following factors are considered:
Trafc 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
Use of timeslots
The use of timeslots for GPRS/EGPRS trafc 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
68P02900W21-R
3-141
GMR-01
Nov 2007
Introduction
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 in state 2 as explained.
The GPRS/EGPRS mobile states and conditions for transferring between states are provided in
Table 3-17 and shown in Figure 3-79 in order to specify when infrastructure resources are being
used to transfer data. The comment column species 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 signicant 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 needs planning for trafc channels and for signaling 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 conguring the
PBCCH/PCCCH for GPRS/EGPRS control channels.
Table 3-17 MM state model of MS

Present
state
number
Next state
Present state
IDLE
READY(3)
GPRS/EGPRS
Attach
Subscriber is not monitored

by the infrastructure that is
not attached to GPRS/EGPRS
MM, and therefore does not
load the system other than
the HLR records.
STANDBY
READY(3)
PDU
Transmission
Subscriber is 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.
READY
IDLE(1)S
GPRS/EGPR
Detach
Data transmission through

the infrastructure occurs in
the Ready state.
READY
STANDBY(2)
Ready timer
expiry or force to
Standby (network
or the MS can send
a GMM signaling
message to invoke
force to Standby).
The ready timer (T3314)

default time is 32 seconds.
The timer value can be
modied during the signaling
process by MS request.2 - 60
s in 2 s increments or 61 1800 s in 60 s increments.
Condition for state

transfer
Comments (present state)
The MS and SGSN state models are illustrated in Figure 3-79.

3-142
68P02900W21-R
GMR-01
Nov 2007
Figure 3-79
Dynamic timeslot allocation
MM state models for MS and SGSN
IDLE
GPRS Attach
S TANDBY timer
expiry
IDLE
GPRS Detach
READY
GPRS Attach
S TANDBY timer expiry

or
Cancel Location
PDU t ransmission
READY timer expiry

or
Force to S TANDBY
GPRS Detach
or
Cancel Location
READY
READY timer expiry

or
PDU reception
Force to S TANDBY
or
Abno rmal RLC condition
S TANDBY
S TANDBY
MM State Model of MS
MM State Model of SGSN

ti-GSM-MM_state_models_for_MS_and_SGSN-00203-ai-sw

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 user 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. 64 kbit/s TRAU are allocated
before 32 kbit/s TRAU, 32 kbit/s TRAU are allocated before 16 kbit/s TRAU. In addition, TRAU
types are given priority over the BCCH carrier.
68P02900W21-R
3-143
GMR-01
Nov 2007
For EGPRS, 64 kbit/s 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 64
kbit/s and not adjacent 16 kbit/s subrate timeslots. For Non-BCCH carriers all timeslots should
have 64 kbit/s while for BCCH, the BCCH times slot uses 16 kbit/s 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.
Background and discussion

Multiple carriers per cell can be congured with GPRS/EGPRS timeslots by the operator for
packet data trafc 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 congure GPRS/EGPRS timeslots on multiple carriers per cell:
Congure for performance

This is the network default option. Congure for performance provides the network with
the capability to congure all the reserved and switchable GPRS/EGPRS timeslots in a cell
contiguously to maximize performance. The contiguous GPRS/EGPRS timeslots congured
on a carrier in a cell provide ease in scheduling packet data and the capability to service
multiple timeslot GPRS mobiles.
Operator specied
This provides the customer with the exibility to congure reserve and switchable
GPRS/EGPRS timeslots on a per carrier basis in a cell.
Depending on hardware conguration at a cell, there maybe some limitations on how timeslots
are allocated to EGPRS on a carrier.
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 amplier 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 operate in SDM and 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 congured 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 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-18.
3-144
68P02900W21-R
GMR-01
Nov 2007
Table 3-18 Capping settings

Step
Data base parameter value
5dB higher
2dB higher
1dB higher
> 2
0dB difference
Therefore, depending on the conguration 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) can have one EGPRS carrier and one GSM full power carrier.
Some of the timeslots of a 1-carrier cell (1/1/1) are allocated to EGPRS. Different powers
are on timeslot by timeslot basis.
On the same timeslot allocated to EGPRS, operators can operate on MCS-1 to MCS-4
and MCS-5 to MCS-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 trafc if all 8 timeslots on a carrier are congured as TCH
and the additional third DS0 provides the bare minimum backhaul required for congurations
when 1 to 3 timeslots on the carrier are congured as PDTCHs. The third DS0 also helps in
reducing the time required to start servicing the rst 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 64 K backhaul necessary
to support EGPRS and makes it possible to congure RTFs on which GPRS data is specically
disallowed. Technical Description: BSS Implementation (68PO2901W36) provides a complete
description of these commands.
Depending on the restrictions imposed on GPRS (32 kbit/s TRAU) and EGPRS (enabled or
disabled), pkt_radio_type can be set between 0 (no packet data) and 3 (64 k).
{23769} Every RTF equipped as pkt_radio_type = 3 (64 K) also has a congurable attribute
rtf_ds0_count. If the VersaTRAU feature is unrestricted, the operator can congure the RTF
backhaul for an EGPRS capable carrier to be between 3 and 8 64 kbit/s terrestrial timeslots.
{28075} When the RTF to DRI mapping is performed, the RTFs equipped for EGPRS (that is, 64
kbit/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 64 k 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 signaling, 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 is only able to support GSM voice calls or 16 K data.
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 attempts to
maintain both EGPRS service and keep the BCCH on a CTUII if at all possible. If the BCCH RTF
68P02900W21-R
3-145
GMR-01
Nov 2007
is congured for EGPRS and there is only one SDM CTUII available, the BCCH RTF is mapped
onto that CTUII, since EGPRS service and EGPRS one phase access would still be available.
However, if the BCCH RTF is not congured with 64 kbps terrestrial backing and there is only
one CTUII available, the BCCH is moved to a non-CTUII radio.
At initialization the BSS should load up non-CTUII hardware with 16 k/32 k carriers as much
as possible. Thus, the BSS software attempts to assign EGPRS carriers onto EGPRS-capable
hardware rst, and then assign carriers to the rest of the hardware in its usual fashion. The BSS
ignores the pkt_radio_type value of the BCCH carrier if PBCCH/PCCCH is enabled in the cell.
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 trafc and
GPRS trafc. There are three provisioning choices combined with timeslot conguration options
selected:
Reserved GPRS/EGPRS timeslots allocated only for packet data use.
Switchable timeslots dynamically allocated for either GSM circuit-switched trafc or

GPRS/EGPRS trafc (designated as switchable timeslots by Motorola).
Remaining timeslots on the carrier with GPRS/EGPRS timeslots, if any, only for
circuit-switched use.
Planning goals - reserved against switchable timeslots

The network planner can consider the following network planning goals when trying to
determine when to use reserved timeslots against 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 trafc 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
trafc 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 trafc 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 trafc
level, as measured in Erlangs. Once the circuit-switched information is known, the potential
impact on switchable timeslots can be analyzed. The GPRS/EGPRS QoS can be planned by
3-146
68P02900W21-R
GMR-01
Nov 2007
Carrier timeslot allocation examples
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.
The priority of timeslot allocation takes into account the factors in the following list. The highest
priority starts with number 1 and the lowest priority is number 5. In the examples that follows,
priorities 3 and 4 are not considered.
1.
TRAU-Type - in the order 64 K, 32 K, and 16 K.
2.
BCCH Carrier.
3.
Most INS number of timeslots: At this step, the following are taken into account:
Continuous timeslots
SD load (signaling load)
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:

Reserved
Switchable
Circuit-switched (T)
{28075} The 64 k DDM CTU2 carrier A is less preferred for 64 k PDCH placement and its
paired 32 k carrier B is less preferred for 32 k PDCH placement.

The following conguration examples explore different ways to congure timeslots in a cell.
{23769} Some of these examples also illustrate the usage of the PDTCH/backhaul proportion
when conguring the timeslots on an EGPRS capable carrier (pkt_radio_type set to 3) with a
congurable RTF backhaul (using the rtf_ds0_count parameter).
In the examples, the following annotations are used:
B = BCCH/CCCH timeslot for GPRS/GSM signaling.
SD = {28075} The ith SDCCH timeslot for GSM signaling. The subscript represents the
ascending order in which the SDCCH timeslots are allocated across carriers.
P = PCCCH timeslot for GPRS/EGPRS signaling.
RG = Reserved GPRS timeslot (EGPRS cannot be used, if non-64 K RTF).
RE = Reserved EGPRS timeslot (GPRS can be used).
SG = Switchable GPRS timeslot (EGPRS cannot be used, if non-64 K RTF).
SE = Switchable EGPRS timeslot (GPRS can be used).
68P02900W21-R
3-147
GMR-01
Nov 2007
T = Circuit-switched use only timeslots.

{28075} X = Blanked-out timeslots (on DDM CTU2 Carrier B as Carrier A is capable of EGPRS).
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 (64 K) 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 is set to:

{28075} PGSM BCCH RTF: 64 K (3)
EGSM 2 non-BCCH carriers: 32 K (2)
PGSM 1 non-BCCH carrier: 16 K (1)
PGSM 1 non-BCCH carrier: None (0)
One CTUII and four non-CTUII
GPRS 32 K 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 congured contiguously for performance.
The packet data timeslots are arranged as shown in Table 3-19. The BCCH RTF is mapped
to CTUII and all the reserved timeslots are EGPRS capable. The non-BCCH 32 K carriers
are used for GPRS CS1 to CS4. The remaining switchable timeslots are mapped to one of
the non-BCCH 16 K carrier.
{28075}
Table 3-19 Arrangement of packet data timeslots for example 1

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
SD5
SD6
RE
RE
RE
RE
RE
Non-BCCH 32 K
(non-CTUII)
SD7
SG
SG
RG
RG
RG
RG
RG
Non-BCCH 32 K(non-CTUII)
SD8
SG
SG
SG
SG
SG
SG
SG
Non-BCCH 16 K
(non-CTUII)
SD3
SD4
SG
SG
SG
SG
SG
SG
Non-BCCH
SD1
SD2
BCCH 64 K (CTUII)
3-148
68P02900W21-R
GMR-01
Nov 2007
Example 2
a 5 carrier cell.

{28075}
{28075} PGSM BCCH RTF: None (0)
EGSM 1 non-BCCH carriers: 64 K (3)
PGSM non-BCCH carrier: 32 K (2)
(HR enabled) PGSM non-BCCH carrier: 32 K (2)
EGSM 1 non-BCCH carrier: 16 K (1)
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 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 congured contiguously for performance. The packet data
timeslots are arranged as shown in Table 3-20. The BCCH RTF is mapped to non-CTUII DRI
and all the circuit-switched timeslots are allocated to it. The EGPRS and GPRS timeslots are
allocated to non-BCCH carriers as shown.

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH (non-CTUII)
SD1
SD2
Non-BCCH 64 K
(CTUII)
RE
RE
RE
RE
RE
RE
RE
RE
Non-BCCH 32 K
(non-CTUII)
SD3
SD4
SG
SG
SG
SG
RG
RG
Non-BCCH 32 K
(non-CTUII)
SD5
SD6
SG
SG
SG
SG
SG
SG
Non-BCCH 16 K
(non-CTUII)
SD7
SD8
SG
SG
SDG
SDG
SG
68P02900W21-R
3-149
GMR-01
Nov 2007
Example 3
There are 8 switchable GPRS/EGPRS timeslots and 4 reserved GPRS/EGPRS timeslots in a 5
carrier cell.
RTF backhaul for an RTF with pkt_radio_type set to 3 (64 K) is defaulted to 7 DS0s, if it is the

PGSM BCCH RTF: 64 K (3) and PBCCH enabled with sd_priority = 255
PGSM 2 non-BCCH carriers: 32 K (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 in Table 3-21.
{28075}

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
RE
RE
RE
RE
Non-BCCH 32 K
(non-CTUII)
SD1
SD3
SG
SG
SG
SG
Non-BCCH 32
K(non-CTUII)
SD2
SD4
SG
SG
SG
SG
Non-BCCH 16 K
(non-CTUII)
SD7
SD8
Non-BCCH 16 K
(non-CTUII)
SD5
SD6
BCCH 64 K
(CTUII)
3-150
68P02900W21-R
GMR-01
Nov 2007
Example 4
a 5 carrier cell.
RTF backhaul for an RTF with pkt_radio_type set to 3 (64 K) is defaulted to 7 DS0s, if it is the

BCCH RTF: None (0)
2 non-BCCH carriers: 64 k (3)
1 non-BCCH carrier: 32 k (2)
1 non-BCCH carrier: None (0)
Two CTUII and three non-CTUII
pccch_enabled = 1
In this example, the BCCH carrier is not congured 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 congured with 64 k
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. Table 3-22 shows the timeslot allocation.
The PCCCH timeslot counts as one of the reserved timeslots.

{28075}

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH 16 K (CTUII)
SD
Non-BCCH 64 K
(CTUII)
RE
RE
RE
RE
RE
RE
RE
RE
Non-BCCH 64
K(non-CTUII)
Non-BCCH 32 K
(non-CTUII)
SG
SG
SG
SG
SG
SG
SG
SG
Non-BCCH 32 K
(non-CTUII)
68P02900W21-R
3-151
GMR-01
Nov 2007
Example 5
a 6 carrier cell.

BCCH RTF: 64 K (3)
1 non-BCCH carrier: 64 K (3)
1 non-BCCH carrier: 32 K (2)
3 non-BCCH carriers: None (0)
Three CTUII and three non-CTUII
Two (AMR or GSM) half-rate enabled carriers
Table 3-23 shows the timeslot allocation.

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH 64 K (CTUII)
SD
RE
RE
RE
RE
RE
RE
Non-BCCH 64 K (CTUII)
SE
SE
SE
SE
RE
RE
RE
RE
Non-BCCH 32
K(non-CTUII
SG
SG
SG
SG
SG
SG
SG
SG
Non-BCCH 16 K
(non-CTUII)
Non-BCCH 16 K (hr
enabled) (non-CTUII)
Non-BCCH 16 K (hr
enabled) (non-CTUII)
3-152
68P02900W21-R
GMR-01
Nov 2007
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 64 k (3)
3 CTUIIs
EGPRS unrestricted

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH 64 K (CTUII)
SD
SE
SE
RE
RE
RE
RE
Non-BCCH 64 K
(CTUII)
SE
SE
SE
SE
RE
RE
RE
RE
Non-BCCH 64 K
(CTUII)
Non-BCCH 64 K
(CTUII)
SE
SE
68P02900W21-R
3-153
GMR-01
Nov 2007
Example 7
{23769}
There are 10 switchable GPRS/EGPRS timeslots and 12 reserved GPRS/EGPRS timeslots in a
6 carrier cell. The following are assumed:
pkt_radio_type set to:

BCCH RTF: 64 k (3), rtf_ds0_count = 4
1 non-BCCH carrier: 64 k (3), rtf_ds0_count = 5
3 non-BCCH carriers None (0)
Three CTUII and three non-CTUII
GPRS 32 K and VersaTRAU (and therefore EGPRS) unrestricted
Two (AMR or GSM) half-rate enabled carriers

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH 64 K
(CTUII)
SD
RE
RE
RE
RE
RE
RE
Non-BCCH 64 K
(CTUII)
SE
SE
RE
RE
RE
RE
RE
RE
Non-BCCH 32
K(CTUII)
SG
SG
SG
SG
SG
SG
SG
SG
Non-BCCH 16 K
(non-CTUII)
Non-BCCH 16
K (hr enabled)
(non-CTUII)
Non-BCCH 16
K (hr enabled)
(non-CTUII)
3-154
68P02900W21-R
GMR-01
Nov 2007
BSS timeslot allocation methods
Example 8
{28075}
There are 5 switchable GPRS/EGPRS timeslots and 4 reserved GPRS/EGPRS timeslots in a 2
carrier cell.
The following are assumed:
pkt_radio_type set to:

BCCH RTF: 64 K (3), rtf_ds0_count = 6
1 non-BCCH carrier: 64 K (3), rtf_ds0_count = 6
CTUII (DDM)
EGPRS and VersaTRAU unrestricted
pccch_enabled = 1

Carrier
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
BCCH 64 K (CTUII DD
Carrier A)
SD
SE
RE
RE
RE
Non-BCCH 64 K (CTUII
DD Carrier A)
SG
SG
SG
Non-BCCH 64 K are downgraded to 16 K. The maximum PDs conguration for two carriers of
DD CTU2 is 8 if Carrier A has EGPRS PDs. The requested 9 PDs cannot be all met.

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 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 specically assigning timeslots on the carrier.
Motorola has implemented an idle circuit-switched parameter that enables the operator to
strongly favor circuit-switched calls from a network provisioning perspective. By setting the
idle parameter to 0, this capability is essentially turned off.
68P02900W21-R
3-155
GMR-01
Nov 2007
When a circuit-switched call ends on a switchable packet data timeslot and the number of idle
circuit-switched timeslots is greater than an user dened 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 trafc.
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 is stolen only 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 {23769} on an algorithm
that takes into account the pkt_radio_type (GPRS/EGPRS capability), the associated RTF
backhaul (congured 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
switchable or reserved timeslots already on the carrier. A rank order based on the backhaul
to PDTCH ratio is 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 trafc.
When (AMR or 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 attempts
to ensure that the last timeslots to be allocated within a cell are half rate capable. Therefore
switchable timeslots are allocated to full rate calls before 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 congured back to OOS.
3-156
68P02900W21-R
GMR-01
Nov 2007
Provisioning the network with switchable timeslots
Contiguous timeslots
Multislot mobile operation needs 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 (refer to 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
timeslot allocation with reserved and switchable timeslots.
Figure 3-80 Carrier with reserved and switchable GPRS/EGPRS timeslots
R
TS 7
TS0
R: Re se rve d PDTC H.
S: Sw itcha ble P DTCH.
Blan k: Circu it-switche d us e only time slots .
ti-GSM-Carrier_with_reserved_and_switchable_GPRS_EGPRS_timeslots-00204-ai-sw
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 rst):
Idle circuit-switched
Idle or in-service switchable GPRS/EGPRS timeslot (from lowest to highest)
In-service circuit-switched
Idle or in-service reserved GPRS/EGPRS timeslot (from lowest to highest)

Provisioning the network with switchable timeslots can offer exibility in the provisioning
process for combining circuit-switched and GPRS/EGPRS service. This exibility is in the
form of additional available network capacity to both the circuit-switched and GPRS/EGPRS
subscribers, but not simultaneously. Because the BSS favors 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.
68P02900W21-R
3-157
GMR-01
Nov 2007
During the circuit-switched busy hour, the circuit-switched use of these switchable timeslots
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.
Table 3-27 assumes that the planning is being performed for a cell that has two carriers. The
rst carrier is for circuit-switched used as shown in Figure 3-81. The second carrier is a carrier
with GPRS/EGPRS timeslots; all eight timeslots are congured 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 trafc 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 trafc increases, as
measured in Erlangs.
This example shows some Erlang trafc 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 trafc level, 2 carriers is not enough
to serve the circuit-switched trafc at a 2% GOS. This would indicate a need for a second
circuit-switched carrier, in addition to the rst 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 depend
upon such factors as user (both BSS and MSC) preference, mobile (AMR capable, GSM half
rate) penetration, mobile preference, RF conditions, handoff parameter and threshold setting,
cell congestion levels, and so on. Once an estimate of half rate usage is determined, it can be
used to determine if the GOS can be met. Table 3-27 and Table 3-28 show two examples using
half rate assumptions.
Table 3-27 Switchable timeslot utilization (Part A)
GOS
Planned circuitswitched
Erlangs/cell
Total number of
circuit- switched
timeslots required
Number of
switchable
timeslots
necessary to
provide GOS
2%
Comments
Outside busy hour time

periods, the carrier
most likely carries only
packet data trafc.
Therefore, packet
data. network planning
should be performed,
assuming there are 8
timeslots available for
GPRS trafc.
Continued
3-158
68P02900W21-R
GMR-01
Nov 2007
Table 3-27 Switchable timeslot utilization (Part A) (Continued)
GOS
Erlangs/cell
Total number of
circuit- switched
timeslots required
Number of
switchable
timeslots
necessary to
provide GOS
0.1%
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 0.1%.
2%
During the
circuit-switched
busy hour, 2 of the
switchable timeslots
the 2% GOS.
0.1%
10
During the
circuit-switched
busy hour, 4 of the
the best possible GOS assumed to be 0.1%.
2%
0.1%
12
2%
10
0.1%
14
2%
12
0.1%
15
There are not enough

switchable timeslots to
provide 0.1% GOS.
2%
13
0.1%
17
11

provide 0.1% GOS.
Comments
All the switchable

timeslots are
occasionally used to
provide 0.1% GOS.
Continued
68P02900W21-R
3-159
GMR-01
Nov 2007
Table 3-27 Switchable timeslot utilization (Part A) (Continued)
GOS
Erlangs/cell
Total number of
circuit- switched
timeslots required
Number of
switchable
timeslots
necessary to
provide GOS
2%
14
0.1%
18
12
Table 3-28
Comments
All the switchable

timeslots are
provide 2% GOS.
provide 0.1% GOS.
Switchable timeslot utilization (Part B)
GOS
Erlangs/cell
Total number of
circuit- switched
timeslots required
Number of
switchable
timeslots
necessary to
provide GOS
2%
15

to provide the 2%
GOS.
0.1%
20
14

to provide the 0.1%
GOS.
2%
10
20 half rate calls
at 2 subchannels
per timeslot
Assumption is 100%
half rate utilization
and all carriers are
capable of half rate.
0.1%
14
9 full rate calls
(9 timeslots) +
9 half rate calls
(5 timeslots)
All of the switchable

timeslots are
satisfy the 2% GOS.
Assumption is 50%
half rate utilization
and all carriers are
capable of half rate.
3-160
Comments
68P02900W21-R
GMR-01
Nov 2007
Recommendation for switchable timeslot usage
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 Circuit-switched carrier, 1 BCCH/CCCH + 1 SDCCH + 6 TCH timeslots
SD
TS 7
TS0
B: BCC H/CC CH for GP RS /GS M s igna lling.
SD : S DCCH for GS M s igna lling.
Blank : Circuit-switched us e only time s lots.
ti-GSM-Circuit_switched_carrier_1_BCCH_CCCH+1_SDCCH+6_TCH_timeslots-00206-ai-sw
Figure 3-82 shows one carrier for GPRS/EGPRS trafc with all timeslots (eight TCHs) designated
as switchable.
Figure 3-82 1 carrier, all timeslots (8 TCHs) designated as switchable
S
TS 7
TS0
S: Switchable TCH
ti-GSM-1_carrier_all_timeslots_8_TCHs_designated_as_switchable-00207-ai-sw
Table 3-27 and Table 3-28 show the switchable timeslot utilization.
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 trafc and QoS objectives for packet data
trafc before 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 trafc. This ensures that there is a minimum guaranteed network
capacity for the data trafc during the circuit-switched busy hour.
During the non-busy hours, the switchable timeslots are 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 trafc. The BSS call statistics should
be inspected to determine the actual use of the switchable timeslots by the circuit-switched
services.
68P02900W21-R
3-161
GMR-01
Nov 2007
Timeslot allocation process on carriers with GPRS trafc
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 is
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 requires 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.
Assume that switchable timeslots are occasionally unavailable for packet data trafc during
the circuit-switched portion of the network busy hour. Provision enough reserved timeslots for
packet data trafc during the circuit-switched busy hour to meet the desired minimum packet
data QoS objectives, as measured by packet data throughput.
Timeslot allocation process on carriers with GPRS trafc

The following procedure helps in determining how to allocate GPRS/EGPRS timeslots.
Procedure 3-1 Determining the allocation of GPRS/EGPRS timeslots
Estimate reserved timeslot requirement:

Determine the number of reserved GPRS/EGPRS timeslots are needed on a
per cell basis in order to satisfy a packet data throughput QoS. The use of
PBCCH in a cell needs 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.
Allocate switchable timeslots:

Determine the number of 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 circuitswitched
trafc if the trafc is staggered in time.
Add an extra circuit-switched carrier:

If there is a require 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.
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 trafc and packet data trafc as
long as the demand for these timeslots is staggered in time.
3-162
68P02900W21-R
GMR-01
Nov 2007
Inuential 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 behavior 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 minimize the number of sites and timeslots (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 qualied by the bitrate or delay experienced.
This should be at least like 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
Numbe r of sub sc riber s

(GPR S /EGP RS s plit)
Are a to co ve r cover ag e
re qu iremen ts
RF Informat ion
Tra ffic P rofile a nd S er vice mix
QoS re qu iremen ts
Ba ndwidth a va ilable
Ne twork con figurat ions
RLC/MAC ove rhea ds
Inpu t par amete rs
Tra ffic ch ar ac te risat ion

RF ce ll plann ing
BTS dime ns ioning
TS dimen sion ing
BS S dime ns ioning
Inte rface dimen sion ing
P la nning tools
Ce ll s ize s
Numbe r of cells
TS re qu ireme nts
BS S re quire men ts
Inte rface re qu iremen ts
Output pa ra me te rs
ti-GSM-Generic_planning_and_dimensioning_process-00208-ai-sw
At a higher level, the cell planning and deployment can be broken down into two activities, which
become inter-related depending on the trafc volumes supported and bandwidth available.
These are cell coverage and cell dimensioning. In addition, there are some deployment rules
that are applied if there is sufcient exibility in the choice of carrier and segregation of
timeslots; this depends on the network conguration. Issues and inuential factors that should
be consider in carrying out the process shown are qualied.
68P02900W21-R
3-163
GMR-01
Nov 2007
Inuential factors in GPRS/EGPRS cell planning and deployment
Network conguration
Network congurations in which packet data (GPRS or EGPRS) can 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 rst conguration 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 congurations are less of concern as they can be ne tuned to provide adequate
coverage and grade of service. So, only the rst conguration 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 also change.
BTS power amplier capability and how it is set for GMSK and 8-PSK modes.
Cell sizes and cell border design criteria.
BSS algorithms (for example, LA).
EGPRS can be introduced in an existing GSM network with full EGPRS coverage. The following
factors are to be considered:
{23956} When the QoS feature is not enabled, the system employs the best effort packet
data services (no high QoS requirements are supported) with RLC acknowledge mode
(ARQ). The choice of operating BLER point is exible within a certain range. In Motorolas
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
Motorolas implementation, the LA algorithm attempts to maximize 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
3-164
68P02900W21-R
GMR-01
Nov 2007
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 is 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 trafc carriers are based on assuming certain
activity factors (DTX). When GPRS/EGPRS are introduced, the level of interference goes up
because of the following factors:
Higher activity: This depends on how the timeslot dimensioning is carried out
to account for packet data users. If timeslots are driven hard, then the level of
activity can be higher than that assumed for the voice only system. Also due to
behavior of packet data users being different, data ow control throughout the
network, multiplexing of users on the same timeslot, the activity prole are different.
Maintaining the same quality of service for the voice users means loading due to
packet data users needs scaling.
8-PSK signal peak to average ratio (PAR): due to 8-PSK envelop variation, the GMSK
symbols are 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 should 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 the impact of lower
average power prevails the impact of PAR, and the average powers in GMSK and
8-PSK modes should be set equal.
Cell/timeslot dimensioning
The following factors inuence 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.
{23956} QoS required (user experience).
Number of users multiplexed on the same timeslot.
Multiplexing of GPRS and EGPRS users on the same timeslot.
Signaling overhead (control channels).
RLC/MAC protocol parameters setting.
Multi-slot operation.
QoS feature enable or disabled.
Cell selection and re-selection.
Hardware limitations, for example, number of timeslots supported per cell.
Re-use pattern: BCCH carrier, FH carrier.
Of the inuences listed, the last two can be easily dealt with while the remaining ones need
detailed investigation, through simulation, to fully quantify their impacts. The following shed
light on some of the issues that are encountered:
68P02900W21-R
3-165
GMR-01
Nov 2007
{23956} If QoS is enabled, the number of PDTCHs required to support the MTBR specied
is 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 has varying impacts on system capacity. Short messages do not benet
from higher code rates for those users in good radio conditions since LA process needs
time to converge to higher code rates. Moreover, RLC protocols, such as TBF holding
time, 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 is closer to the
ideal throughput for long messages.
Up to four users can be multiplexed on a timeslot. Depending on system loading the

apparent bit pipe seen by a user is subsequently reduced as in Figure 3-84. In addition,
this could impact the throughput per timeslot since the LA process suffers due to
variation of radio channel conditions between scheduling opportunities. Thus, even for
long messages the ideal throughput is hardly achieved. In Motorolas 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 improves the overall
system and operators QoS performance depending on the bandwidth provisioned for the
packet data users. {23956} The QoS feature extends this general concept to provide per
trafc class MTBR.
Multiplexing of GPRS and EGPRS users on the same timeslot 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 Motorolas implementation, the
PCU scheduler algorithm is designed to minimize 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, impacts the
throughput per timeslot and as such number of users that can be supported.
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 like other coding schemes at low
C/I values, but the corresponding BLER is 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 Motorolas implementation, the LA algorithm attempts to maximize 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, timeslot dimensioning for packet data trafc should consider the
blocks used for control signaling.
3-166
68P02900W21-R
GMR-01
Nov 2007
Figure 3-84 Multiplexing 4 TBFs on an air timeslot

4 TBFs /TS
Us e r 1
Us e r 2
Us e r 3
80 ms
Us e r 4
20 ms block
Time
ti-GSM-Multiplexing_4_TBFs_on_an_air_timeslot-00209-ai-sw
68P02900W21-R
3-167
GMR-01
Nov 2007
QoS dimensioning
The two most signicant factors that inuence quality of a service are:
Delay
Throughput
In R99 and beyond, four trafc classes are dened to accommodate the need for different levels
of these factors for different applications. These are:
Conversational
Streaming
Interactive
Background
The BSS has internally dened additional trafc classes created by grouping similar PFC
characteristics. The internally dened trafc classes are:
Short-Term Non-Negotiated Trafc (STNNT)
Pre-admission PFC (PAP)
QoS Disabled
Since the specication for conversational and streaming is still evolving, the BSS is
implementing differentiation of service among interactive and background trafc classes.
Requests to create packet ows for streaming or conversational mode are treated as interactive
trafc ows. Support for streaming or conversational trafc class at the BSS is limited in
its scope, that is, streaming and conversational trafc classes get QoS of Interactive Trafc
class when admitted. However, the BSS does not make any guarantees regarding sustaining
applications using the streaming and conversational trafc classes.
Trafc handling priority (THP)

Three priorities are dened in the standards for handling the trafc pertaining to the interactive
trafc 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, dened at a BSS level. These weights are user congurable.
In addition to the three standardized priorities, a fourth and a fth THP are dened internally by
the BSS for the background and best effort trafc classes respectively. The assigned weights for
these internally dened THPs act relative to the three THPs that are dened for the interactive
trafc class by the standards.
THP provides a mechanism to differentiate services among different PFCs that may or may not
belong to the same user.
3-168
68P02900W21-R
GMR-01
Nov 2007
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 2 kbit/s for each admitted PFC.
The operator is allowed to congure 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 that no
more users are admitted than the system can handle without compromising service.
MTBR is not achieved by a TBF with insufcient data to transmit. MTBR is set and regulated in
terms of throughput at the RLC/MAC layer. Throughputs at the application layer are 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-29 shows typical TCP throughput for each
10 kbit/s of RLC/MAC throughput at zero block error rate. The TCP throughput depends upon
the IP packet size and the LLC PDU size. Several typical values are shown in Table 3-29.
Table 3-29
rate
Typical TCP throughput against RLC/MAC throughput at zero block error
RLC/MAC
throughput (kbit/s)
IP packet size (octets)
LLC PDU size (octets)
Typical TCP throughput

(kbit/s)
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 dened in specication 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. ARP ranges from 1 to 3 with 1 being the highest priority.
The BSS maps the ARP parameter and the trafc class into ARP Rank, as shown in Table 3-30.
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-30 ARP mobile selection (ARP Rank) order

ARP value
THP 1
THP 2
THP 3
Effort
Background
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, refer to Chapter 8
PCU upgrade for BSS and QoS capacity on page 8-39.
68P02900W21-R
3-169
GMR-01
Nov 2007
Estimating the air interface trafc throughput
Estimating the air interface trafc 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.
Some wired LAN/WAN trafc studies have shown that packet interarrival rates are not
exponentially distributed. Recent work argues that LAN trafc is much better modeled using
statistically self-similar processes instead of Poisson or Markovian processes. Self-similar trafc
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 trafc pattern is not known due to lack of
eld data.
In order to minimize the negative impact of under-estimating the nature of the GPRS/EGPRS
trafc, it is proposed in this planning guide to adjust the mean GPRS/EGPRS cell loading
value, by a factor of 200% to account for the burstiness of GPRS/EGPRS trafc. When
mean_load_factor parameter is assumed 200%, it means peak trafc is twice of mean trafc.
This parameter impacts the connection between RS PDCH and SW PDCH with different overlap
scenarios. Using this cell loading factor has the following advantages:
Cell overloading due to the bursty nature of GPRS/EGPRS trafc is minimized.
The variance in le 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 le of arbitrary size.
LAN/WAN wireline studies have also shown that even when statistically valid studies are
performed, the results come out different in follow-up studies. It turns out that web trafc
patterns are difcult to predict accurately and, therefore, it is highly recommended that the
network planner makes routine use of the GPRS/EGPRS network statistics.
The following sections describe dimensioning the system:
Select a cell plan on page 3-170
Estimating timeslot provisioning requirements on page 3-172
Optimum le size calculation on page 3-179
File transit times calculations on page 3-180
Sections Optimum le size calculation on page 3-179 and File transit times calculations on
page 3-180 are optional. These should be followed if an over the air le transfer time can be
calculated for any size le. The results depend on the choices made in sections Select a cell plan
on page 3-170 and Estimating timeslot provisioning requirements on page 3-172 .
Select a cell plan

Select a cell plan to determine the expected BLER and percentage of time data is transferred at
the GPRS/EGPRS data rates. The cell plan that is selected for GPRS/EGPRS can be determined
by the plan currently in use for the GSM circuit-switched part of the network. However, it is
necessary to change an existing cell plan used for GSM circuit-switched to get better BLER
performance for the GPRS/EGPRS part of the network.
3-170
68P02900W21-R
GMR-01
Nov 2007
Select a cell plan
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 ow (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-31 shows
the percentage utilization of GPRS and EGPRS coding schemes at a xed 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 specic simulation study is 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.
Table 3-31 Percentage of code utilization in a 4x3 non-hopping re-use pattern at

20% BLER
Coding scheme
% of code utilization
CS1
15
CS2
14
CS3
20
CS4
51
MCS-1
MCS-2
MCS-3
MCS-4
MCS-5
MCS-6
14
MCS-7
12
MCS-8
MCS-9
50
68P02900W21-R
3-171
GMR-01
Nov 2007
Estimating timeslot provisioning requirements

Here, we determine the number of GPRS/EGPRS timeslots that require to be provisioned on
a per cell basis. Timeslot provisioning is based on the expected per cell mean GPRS/EGPRS
trafc load, as measured in kbit/s. The packet data trafc load includes all SMS trafc routed
through the GSN. The SMS trafc is handled by the GPRS/EGPRS infrastructure in the same
manner as all other GPRS trafc originating from the PDN. The cell BLER and CS rate
characteristics selected, 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 equation is based on the DL trafc load and it is assumed that the DL
provisioning would be sufcient to handle UL trafc, without additional
provisioning.
{23956} The Mean_load_factor of 50% has been applied to the trafc load for
systems without the QoS feature enabled to account for any surges in the data
trafc and to carry packet switched signaling trafc. 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 are not downgraded during
peak usage at a cell.
For systems without the QoS feature enabled, Mean_trafc_load for each cell can be calculated
using the following formulae:
The units for Data_per_sub_per_session is kbyte/hr.
3-172
68P02900W21-R
GMR-01
Nov 2007
{23956} For systems without the QoS feature enabled:
{23956} For systems with the QoS feature enabled:
(M)CS_USAGE is the percentage of usage of (E)GPRS coding schemes.
Number of timeslots
{23956} The number of PDTCH timeslots calculated in the section Estimating timeslot
provisioning requirements on page 3-172, denotes the number of timeslots that need to be
provisioned on the cell to carry the mean trafc 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 congured, legacy deployment mode),
The PCU 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 processes 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 its mean load averages
out the packet data trafc load at the PCU.
Up to 3 PCUs may be managed by a BSC. If 3 PCUs are congured, the number of timeslots
increases by a factor of 3. Thus, it is 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 timeslots usage, the number of
timeslots 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
68P02900W21-R
3-173
GMR-01
Nov 2007
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 processes
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
trafc load. If redundancy is desired, the operator may designate a rst and (optionally) second
redundant PCU. If a PCU that has cells mapped to it (the primary PCU) becomes unavailable,
the cells are remapped to the rst (or second if the rst 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 because all of the timeslots can become active under high load conditions.
Timeslot renement with QoS enabled

{23956}
The number of PDTCHs determined for support of QoS should be compared to the examples
given. Refer to the examples to determine a rened number of PDTCHs to support QoS with a
given set of conguration parameters.
Table 3-32 MTBR Mix

MTBR Mix
Percentage
DL
UL
I1
14
I2
10
I3
BG
BE
Table 3-33 MTBR Constant

MTBR Constant
Percentage
DL
UL
I1
I2
I3
BG
BE
3-174
68P02900W21-R
GMR-01
Nov 2007
Table 3-34 THP Weight Mix

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

THP Weight Constant
I1
40
I2
40
I3
20
BG
20
BE
20
Table 3-36 shows the QoS Conguration Examples.
Table 3-36 QoS Conguration Examples
QOS
PDTCHs
THP
weight
Mobile
Trau
Multi-slot
Type
class
Number of PFCs admitted

Subs
(Valid for MTBR/THP
Subscriber
allowed
MTBR
mix only)
Mix
on
carrier 11 12 13 BG BE
No
NA
16/32
No
MTBR
NA
18
Yes
Constant
64
3DL/1UL
Mix
14
Yes
Constant
64
3DL/1UL
Mix
Yes
Constant
16/32
3DL/1UL
Yes
Constant
16/32
Yes
Constant
Yes
Constant
Yes
Yes
Mix
3DL/1UL
Mix
16/32
3DL/1UL
Mix
10
16/32
4DL/1UL
Mix
Constant
16/32
3DL/1UL Constant 11
Constant
10
16/32
3DL/2UL Constant 12
Yes
Mix
10
16/32
4DL/1UL Constant 8
Yes
Mix
10
64
4DL/1UL Constant 8
Yes
Constant
16/32
3DL/1UL
Mix
10
Yes
Mix
10
16/32
4DL/1UL
Mix
Yes
Mix
10
64
4DL/1UL
Mix
10
4
Continued
68P02900W21-R
3-175
GMR-01
Nov 2007
Table 3-36 QoS Conguration Examples (Continued)
QOS
THP
PDTCHs
weight
Mobile
Trau
Multi-slot
Type
class
Number of PFCs admitted

Subs
(Valid for MTBR/THP
Subscriber
allowed
MTBR
mix only)
Mix
on
carrier 11 12 13 BG BE
Yes
Constant
10
16/32
4DL/1UL Constant 10
Yes
Constant
10
16/32
3DL/2UL Constant 12
Yes
Constant
16/32
3DL/2UL Constant 12
Comparison: Number of Class 4 Mobiles in a Cell with 6 PDTCHs; TRAU = 16 K, all THP
weight = 40, MTBR = 2.
Table 3-37 and Table 3-38 show the impact of QoS on the number of PDTCHs required to
support a given trafc mix. The colored cells highlight the additional mobile being added for
the specied time period.
Table 3-37 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18) TS
Mobiles
Link
MS per TS
33
33
33
DL
0.50
100
UL
33
33
33
33
33
33
DL
100
100
UL
33
33
33
333
83
83
DL
100
100
100
UL
33
33
83
83
83
84
DL
100
100
100
100
UL
133
33
83
83
83
83
DL
100
100
100
100
100
UL
133
133
83
83
83
83
DL
100
200
100
100
100
UL
133
133
183
83
83
83
DL
100
200
100
100
100
200
UL
133
133
183
83
183
83
DL
100
200
100
100
200
200
UL
133
133
183
183
183
83
DL
100
200
100
200
200
200
UL
133
133
183
183
183
183
DL
100
200
100
200
200
300
UL
233
133
183
183
183
183
DL
200
200
100
200
200
300
UL
10
11
1.00
1.33
1.67
1.83
2.00
2.17
2.33
2.50
2.67
2.83
Continued
3-176
68P02900W21-R
GMR-01
Nov 2007
Table 3-37 QoS Disabled; Capacity: 18 users, DL Throughput per MS: 0.33 (6/18)
TS (Continued)
Mobiles
Link
MS per TS
12
233
233
183
183
183
183
DL
3.00
200
300
100
200
200
300
UL
233
233
283
183
183
183
DL
200
300
200
200
200
300
UL
233
233
283
183
283
183
DL
200
300
200
200
300
300
UL
233
233
283
283
283
183
DL
200
300
200
300
300
300
UL
233
233
283
283
283
283
DL
200
300
200
300
300
400
UL
333
233
283
283
283
283
DL
300
300
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
333
333
283
283
283
283
DL
300
400
200
300
300
400
UL
13
14
15
16
17
18
19
20
21
22
23
3.17
3.33
3.50
3.67
3.83
Table 3-38 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11) TS
Mobiles
Link
MS per TS
33
33
33
DL
0.50
100
UL
33
33
33
33
33
33
DL
100
100
UL
33
33
67
67
67
33
DL
100
100
100
UL
1.00
1.50
Continued
68P02900W21-R
3-177
GMR-01
Nov 2007
Table 3-38 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11)
TS (Continued)
Mobiles
Link
MS per TS
83
83
67
67
67
333
DL
1.83
100
100
100
UL
83
83
67
67
117
83
DL
100
100
100
100
100
UL
83
117
100
100
117
83
DL
100
100
100
100
100
100
UL
83
117
150
150
117
83
DL
100
100
100
200
100
200
UL
83
117
150
150
167
133
DL
100
100
100
200
100
200
UL
133
167
150
150
167
133
DL
100
200
100
200
100
200
UL
133
167
150
150
167
233
DL
100
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
1200
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
300
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
100
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
10
11
12
13
14
15
16
17
18
19
20
2.17
2.67
3.00
3.33
3.67
3.83
4.00
Continued
3-178
68P02900W21-R
GMR-01
Nov 2007
Optimum le size calculation
Table 3-38 QoS Enabled; Capacity: 11 users, DL Throughput per MS: 0.54 (6/11)
TS (Continued)
Mobiles
Link
21
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
233
167
150
150
167
233
DL
200
200
100
200
100
300
UL
22
23
MS per TS
Optimum le size calculation

This section is intended to be used as an aid in determining the size of a le that is to be
transferred as an LLC PDU from the mobile to the SGSN.
The le size consists of the application le to be transferred, which includes any
application-related overhead. In addition to the application le, 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 le plus all of the
protocol overhead summed together makes up the one or more LLC_PDU frames that constitute
the le 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 rst 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
7
LLC
LLC_PDU frame layout
2
SNDC P
20
IP
20
TCP
APP LICATION
4
CR C
64 BYTES < L < 1580 BYTES

ti-GSM-LLC_PDU_frame_layout-00210-ai-sw
68P02900W21-R
3-179
GMR-01
Nov 2007
File transit times calculations
If V.42bis application data compression is used, the effective le 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 le, and close to no compression advantage (factor = 1) on
image les and short les:
Where:
File_size_LLC
Appln
LLC_payload
Is:
le size in bytes to be transferred, measured at the LLC layer.
user application data le size, measured in bytes.
maximum LLC PDU payload of 1527 bytes.
protocol_overhead
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.
Example
A 3 kbyte/s application le transfer needs the following number of bytes to be transferred at
the LLC_PDU layer:
Application = 3 kbytes
Assume that V.42bis_factor = 1, that is no application data compression.
Without Header compression:
File_size_LLC = 3000/1 + roundup (3000/2/1527) x 53 = 3106 bytes
With header compression:
The rst LLC_PDU header is not compressed, and all subsequent LLC_PDUs are compressed. For
this size le of 3000 bytes, only 2 LLC_PDU transmissions are required so the File_size_LLC is:
File_size_LLC = 3000 + 53+18 = 3071 bytes

The network planner can follow this section to determine how long it takes to transfer a le of
an arbitrary size over the Um to Gi interface. The application le 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 le, BLER, number of timeslots used during the
transfer, and mean RLC Transit Delay (RTD) value:
3-180
68P02900W21-R
GMR-01
Nov 2007
Where:
Is:
FTD
le transit delay measured in seconds.
RTD
transit delay time from the Um interface to the Gi interface for a le 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 is updated when eld
test data is available.
RLC_Blocks
mslot
total number of RLC blocks of the le. This can be calculated by dividing
le_size_LLC by the corresponding RLC data size for various GPRS and
EGPRS code rates.
mobile multislot operating mode; the value can be from 1 to 4.
CSBLER
the BLER for the specic coding rate. The value is specied in decimal
form. Typical values range form 0.1 to 0.2
The 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 l
dominates the cell trafc. 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 do not signicantly effect the le transit delay in the
downlink direction.
The RTD parameter is directly correlated to the system utilization and the mean packet size.
When the cell approaches its throughput capacity limit, the RTD value increases dramatically,
and the infrastructure starts to drop packets. Simulation data indicates that when trafc 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 trafc at the CS1 rate and 75% of the
cell trafc 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.
Example of calculations
Example 1:
A 3 kbyte/s application le transit time at the CS2 rate, using one timeslot, BLER = 10%, and no
header or V.42bis compression is:
3 kbyte/s le 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
(1 + CS_BLER)
Multislot operation
0.02 seconds
1.1
1
68P02900W21-R
3-181
GMR-01
Nov 2007
Congurable initial coding scheme
Congurable initial coding scheme

Before 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 (using 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 feature also applies to EGPRS, for example, MCS-2 can be selected as the initial coding
scheme.
GPRS/EGPRS data rates
The information provided is for reference only. It is also used to calculate

timeslot data rates at each layer, if required. These are theoretical calculated
values, based on the protocol overheads at each layer. They do not necessarily
represent the data rates that the system can support.
The nal throughput at application layer is less than those quoted in the tables
due to various protocol overheads and the behavior of various layers in response
to packet data ow.
The following assumptions are 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 signicant overhead at RLC/MAC level due 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. This parameter is also congured in SGSN).
The behavior of TCP, for example, slow start, is not taken into consideration, that is, perfect
TCP response is assumed. In practice, this imposes additional overhead since the channel
is not fully utilized for certain portion of time.
Increased efciencies gained from lowered overhead, as a result of using higher numbers
of timeslots, is not calculated for this analysis.
C/I for each coding scheme is sufcient to support error free transport, that is, BLER = 0.
H/C = Header compression.
TS = Timeslot.
3-182
68P02900W21-R
GMR-01
Nov 2007
The rates are calculated bottom to top as follows (refer to Figure 3-85 and Figure 3-86):
Physical layer: GSM data rates.
RLC/MAC: Error free data rate including RLC/MAC headers (see earlier description of
various coding schemes, user and header encoding procedures.
LLC: Error free user data rate excluding RLC/MAC header, that is, LLC broken into RLC
blocks (Figure 3-86).
SNDCP: Includes header associated with LLC (7 bytes + 4 bytes CRC, Figure 3-83).
IP user rate: Includes header associated with SNDCP (2 bytes, Figure 3-83).
TCP: includes header associated with IP (20 bytes, Figure 3-83). The header compression
is not applied to the rst LLC IP frame.
App. user rate: Includes header associated with TCP (20 bytes, Figure 3-83).
For more than 1 timeslot, the overheads are applied only to one of the timeslots.
Figure 3-86 LLC PDU to TDMA burst`

s
LLC frame
LLC
layer
RLC block
Segmen t
Segmen t
Segment
RLC/MAC
layer
Heade r
RLC dat a
Tail
Radio link
layer
Co nvolutional encoding (dictates code
Burst 1
Burst 2
rate), Punctu ring and Inte rleaving
Burst 3
Burst 4
Transmission ac ross the radio link

ti-GSM-LLC_PDU_to_TDMA_bursts-0021 1-ai-sw
68P02900W21-R
3-183
GMR-01
Nov 2007
Table 3-39 through Table 3-64 provide illustrations of the data rates by application at each
layer in the GPRS stack.
Table 3-39 GPRS downlink data rates (kbit/s) with TCP (CS1)
Protocol Stack
CS1 and TS = 1
CS1 and TS = 2
CS1 and TS = 3
CS1 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
7.73
7.91
15.73
15.93
23.73
23.93
31.73
31.93
TCP
7.83
7.92
15.83
15.93
23.83
23.93
31.83
31.93
IP user rate
7.93
15.93
23.93
31.93
SNDCP
7.94
15.94
23.94
31.94
LLC
8.00
16
24
32.9
20
18.4
27.6
36.8
33.86
67.72
101.58
135.44
RLC/MAC
Physical layer
Protocol Stack
CS2 and TS = 1
CS2 and TS = 2
CS2 and TS = 3
CS2 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
11.60
11.86
23.60
23.89
35.60
35.89
47.60
47.89
TCP
11.75
11.89
23.75
23.90
35.75
35.90
47.75
47.90
IP user rate
11.90
23.90
35.90
47.90
SNDCP
11.92
23.92
35.92
47.92
12
24
36
48
13.6
27.1
40.65
54.2
33.86
67.72
101.58
135.44
LLC
RLC/MAC
Physical layer
Protocol Stack
CS3 and TS = 1
CS3 and TS = 2
CS3 and TS = 3
CS3 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
13.92
14.24
28.32
28.67
42.72
43.07
57.12
57.47
TCP
14.10
14.26
28.50
28.68
42.90
43.08
57.30
57.48
IP user rate
14.28
28.68
43.08
57.48
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
33.86
67.72
101.58
135.44
Physical layer
3-184
68P02900W21-R
GMR-01
Nov 2007
Protocol Stack
CS4 and TS = 1
CS4 and TS = 2
CS4 and TS = 3
CS4 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
19.34
19.77
39.33
39.82
59.33
59.82
79.33
79.82
TCP
19.58
19.81
39.58
39.83
59.58
59.83
79.58
79.83
IP user rate
19.84
39.84
59.84
79.84
SNDCP
19.86
39.86
59.86
79.86
20
40
60
80
21.8
43.1
64.7
86.2
33.86
67.72
101.58
135.44
LLC
RLC/MAC
Physical layer
Table 3-43 GPRS downlink data rates (kbit/s) with UDP (CS1)
Protocol Stack
CS1 and TS = 1
CS1 and TS = 2
CS1 and TS = 3
CS1 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
7.79
7.92
15.79
15.93
23.79
23.93
31.79
31.93
UDP
7.83
7.92
15.83
15.93
23.83
23.93
31.83
31.93
IP user rate
7.93
15.93
23.93
31.93
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
33.86
67.72
101.58
135.44
Physical layer
Table 3-44 GPRS downlink data rates (kbit/s) with UDP (CS2)
Protocol Stack
CS2 and TS = 1
CS2 and TS = 2
CS2 and TS = 3
CS2 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
11.69
11.88
23.69
23.89
35.69
35.89
47.69
47.89
UDP
11.75
11.89
23.75
23.90
35.75
35.90
47.75
47.90
IP user rate
11.90
23.90
35.90
47.90
SNDCP
11.92
23.92
35.92
47.92
12
24
36
48
13.6
27.1
40.65
54.2
33.86
67.72
101.58
135.44
LLC
RLC/MAC
Physical layer
68P02900W21-R
3-185
GMR-01
Nov 2007
Table 3-45
Protocol Stack
GPRS downlink data rates (kbit/s) with UDP (CS3)

CS3 and TS = 1
CS3 and TS = 2
CS3 and TS = 3
CS3 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
14.03
14.25
28.43
28.67
42.83
43.07
57.23
57.47
UDP
14.10
14.26
28.50
28.68
42.90
43.08
57.30
57.48
IP user rate
14.28
28.68
43.08
57.48
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
33.86
67.72
101.58
135.44
Physical layer
Table 3-46
Protocol Stack
GPRS downlink data rates (kbit/s) with UDP (CS4)

CS4 and TS = 1
CS4 and TS = 2
CS4 and TS = 3
CS4 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
19.49
19.80
39.48
39.82
59.48
59.82
79.48
79.82
UDP
19.58
19.81
39.58
39.83
59.58
59.83
79.58
79.83
IP user rate
19.84
39.84
59.84
79.84
SNDCP
19.86
39.86
59.86
79.86
20
40
60
80
21.6
43.1
64.7
86.2
33.86
67.72
101.58
135.44
LLC
RLC/MAC
Physical layer
Table 3-47 EGPRS downlink data rates (kbit/s) with TCP (MCS1)
Protocol Stack
MCS1 and TS = 1
MCS1 and TS = 2
MCS1 and TS = 3
MCS1 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
8.51
8.70
17.31
17.52
26.11
26.32
34.91
35.12
TCP
8.62
8.72
17.42
17.52
26.22
26.32
35.02
35.12
IP user rate
8.73
17.53
26.33
35.13
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 layer
33.86
67.72
101.58
135.44
3-186
68P02900W21-R
GMR-01
Nov 2007
Table 3-48
EGPRS downlink data rates (kbit/s) with TCP (MCS2)
Protocol Stack
MCS2 and TS = 1
MCS2 and TS = 2
MCS2 and TS = 3
MCS2 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
10.83
11.07
22.03
22.30
33.23
33.50
44.43
44.70
TCP
10.97
11.09
22.17
22.30
33.37
33.50
44.57
44.70
IP user rate
11.11
22.31
33.51
44.71
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 layer
33.86
67.72
101.58
135.44
Table 3-49
Protocol Stack
MCS3 and TS = 1
MCS3 and TS = 2
MCS3 and TS = 3
MCS3 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
14.31
14.63
29.11
29.46
43.91
44.26
58.70
59.06
TCP
14.49
14.66
29.29
29.47
44.09
44.27
58.89
59.07
IP user rate
14.68
29.48
44.28
59.08
SNDCP
1470
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 layer
33.86
67.72
101.58
135.44
Table 3-50
Protocol Stack

MCS4 and TS = 1
MCS4 and TS = 2
MCS4 and TS = 3
MCS4 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
17.02
17.40
34.61
35.04
52.21
52.64
69.81
70.24
TCP
17.23
17.43
34.83
35.05
52.43
52.65
70.03
70.25
IP user rate
17.46
35.06
52.66
70.26
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 layer
33.86
67.72
101.58
135.44
68P02900W21-R
3-187
GMR-01
Nov 2007
Protocol Stack
MCS5 and TS = 1
MCS5 and TS = 2
MCS5 and TS = 3
MCS5 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
21.66
22.15
44.05
44.59
66.45
66.99
88.85
89.39
TCP
21.93
22.19
44.33
44.61
66.73
67.01
88.13
89.41
IP user rate
22.22
44.62
67.02
89.42
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
101.58
203.16
304.74
406.32
Physical layer
Protocol Stack
MCS6 and TS = 1
MCS6 and TS = 2
MCS6 and TS = 3
MCS6 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
28.62
29.26
58.21
58.93
87.81
88.53
117.41
118.13
TCP
28.99
29.32
58.58
58.94
88.18
88.54
117.78
118.14
IP user rate
29.36
58.96
88.56
118.16
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
101.58
203.16
304.74
406.32
Physical layer
Protocol Stack
MCS7 and TS = 1
MCS7 and TS = 2
MCS7 and TS = 3
MCS7 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
43.31
44.29
88.11
89.19
132.90
133.99
177.70
178.79
TCP
43.87
44.38
88.67
89.21
`
133.47
134.01
178.27
178.81
IP user rate
44.43
89.23
134.03
178.83
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
101.58
203.16
304.74
406.32
Physical layer
3-188
68P02900W21-R
GMR-01
Nov 2007
Table 3-54
Protocol Stack
MCS8 and TS = 1
MCS8 and TS = 2
MCS8 and TS = 3
MCS8 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
52.60
53.78
106.99
108.30
161.38
162.70
215.78
217.10
TCP
53.27
53.88
107.67
108.33
162.07
162.73
216.47
217.13
IP user rate
53.95
108.35
162.75
217.15
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
101.58
203.16
304.74
406.32
Physical layer
Table 3-55
Protocol Stack
MCS9 and TS = 1
MCS9 and TS = 2
MCS9 and TS = 3
MCS9 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user rate
57.24
58.53
116.43
117.85
175.62
177.05
234.82
236.25
TCP
57.97
58.64
117.17
117.89
176.37
177.09
235.57
236.29
IP user rate
58.71
117.91
177.11
236.31
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
101.58
203.16
304.74
406.32
Physical layer
Table 3-56 EGPRS downlink data rates (kbit/s) with UDP (MCS1)
Protocol Stack
MCS1 and TS = 1
MCS1 and TS = 2
MCS1 and TS = 3
MCS1 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
8.57
8.71
17.37
17.52
26.17
26.32
34.97
35.12
UDP
8.62
8.72
17.42
17.52
26.22
26.32
35.02
35.12
IP user rate
8.73
17.53
26.33
35.13
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 layer
33.86
67.72
101.58
135.44
68P02900W21-R
3-189
GMR-01
Nov 2007
Protocol Stack
MCS2 and TS = 1
MCS2 and TS = 2
MCS2 and TS = 3
MCS2 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
10.91
11.09
22.11
22.30
33.31
33.50
44.51
44.70
UDP
10.97
11.09
22.17
22.30
33.37
33.50
44.57
44.70
IP user rate
11.11
22.31
33.51
44.71
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
layer
33.86
67.72
101.58
135.44
Protocol Stack
MCS3 and TS = 1
MCS3 and TS = 2
MCS3 and TS = 3
MCS3 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
14.42
14.65
29.22
29.47
44.02
44.27
58.82
59.07
UDP
14.49
14.66
29.29
29.47
44.09
44.27
58.89
59.07
IP user rate
14.68
29.48
44.28
59.08
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
layer
33.86
67.72
101.58
135.44
Protocol Stack
MCS4 and TS = 1
MCS4 and TS = 2
MCS4 and TS = 3
MCS4 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
17.15
17.42
34.75
35.04
52.34
52.64
69.94
70.24
UDP
17.23
17.43
34.83
35.05
52.43
52.65
70.03
70.25
IP user rate
17.46
35.06
52.66
70.26
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
layer
33.86
67.72
101.58
135.44
3-190
68P02900W21-R
GMR-01
Nov 2007
Protocol Stack
MCS5 and TS = 1
MCS5 and TS = 2
MCS5 and TS = 3
MCS5 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
21.82
22.17
44.22
44.60
66.62
67.00
89.02
89.40
UDP
21.93
22.19
44.33
44.61
66.73
67.01
88.13
89.41
IP user rate
22.22
44.62
67.02
89.42
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
101.58
203.16
304.74
406.32
Physical
layer
Protocol Stack
MCS6 and TS = 1
MCS6 and TS = 2
MCS6 and TS = 3
MCS6 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
28.84
29.30
58.44
58.94
88.03
88.54
117.63
118.14
UDP
28.99
29.32
58.58
58.94
88.18
88.54
117.78
118.14
IP user rate
29.36
58.96
88.56
118.16
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
101.58
203.16
304.74
406.32
Physical
layer
Protocol Stack
MCS7 and TS = 1
MCS7 and TS = 2
MCS7 and TS = 3
MCS7 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
43.65
44.35
88.44
89.20
133.24
134.00
178.04
178.80
UDP
43.87
44.38
88.67
89.21
133.47
134.01
178.27
178.81
IP user rate
44.43
89.23
134.03
178.83
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
101.58
203.16
304.74
406.32
Physical
layer
68P02900W21-R
3-191
GMR-01
Nov 2007
Protocol Stack
MCS8 and TS = 1
MCS8 and TS = 2
MCS8 and TS = 3
MCS8 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
53.00
53.85
107.39
108.32
161.79
162.72
216.19
217.12
UDP
53.27
53.88
107.67
108.33
162.07
162.73
216.47
217.13
IP user rate
53.95
108.35
162.75
217.15
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
101.58
203.16
304.74
406.32
Physical
layer
Protocol Stack
MCS9 and TS = 1
MCS9 and TS = 2
MCS9 and TS = 3
MCS9 and TS = 4
No H/C
H/C
No H/C
H/C
No H/C
H/C
No H/C
H/C
App. user
rate
57.68
58.60
116.87
117.88
176.07
177.08
235.27
236.28
UDP
57.97
58.64
117.17
117.89
176.37
177.09
235.57
236.29
IP user rate
58.71
117.91
177.11
236.31
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
101.58
203.16
304.74
406.32
Physical
layer
3-192
68P02900W21-R
GMR-01
Nov 2007
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 their operation within the Motorola system. The {22064} GSM half rate and
the half rate portion of AMR are similar. Hence, the information here covers both features.
The benets of the features are outlined, and performance discussed. The manual gives an
understanding of how AMR and {22064} GSM half rate works and how they are congured.
The various parameters controlling AMR operation are discussed. However, not all of the
commands and parameters are shown in detail.
The topics described are as follows:
Introduction on page 4-2
Quality and capacity on page 4-5
Rate adaptation on page 4-16
Handover and power control on page 4-19
Miscellaneous information on page 4-21
Half rate utilization on page 4-22
Hardware on page 4-29
68P02900W21-R
Nov 2007
4-1
GMR-01
Introduction
Introduction
AMR basic operation

Existing GSM speech codecs operate at a xed coding rate. Channel protection is also xed.
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 is enhanced by allocating half rate channels to some or all mobiles. In order to obtain
the best balance between quality and capacity, the system allocates a half rate (hr) or full rate
(fr) channel according to channel quality and the trafc load on the cell.
The control system is not xed but can be tuned to meet particular needs. The three primary
levels of adaptation of the control system are:
Handovers between hr and fr channels according to trafc demands.
Variable partitioning between speech and channel coding bit rates to adapt to channel
conditions for best speech quality.
Optimization of channel and codec control algorithms to meet specic user 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.
{22064} GSM half rate basic operation

GSM half rate was introduced in phase 2 of the standards, and operates at a xed 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 trafc load on the cell. Handovers
between hr and fr channels vary according to trafc demands.
The best examples of applying the codec are:
hr only for maximum capacity advantage.
Mixed hr/fr operation allowing a tradeoff between quality and capacity.
4-2
68P02900W21-R
GMR-01
Nov 2007
AMR and {22064} GSM half rate interaction
AMR and {22064} GSM half rate interaction

AMR and {22064} GSM half rate can co-exist in a cell. A carrier could have a mix of {22064}
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 rmware, provides
the capabilities necessary to 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 is used without the benet of any of the new hardware;
although not as efciently (this is discussed later in the chapter).
Without new hardware, AMR needs the use of GDPs congured as EGDP(s).
Inuencing factors
There are many factors to be taken into account when conguring/operating a system in which
AMR and/or {22064} GSM half rate is present. These include the following:
AMR-capable handset penetration (see the rst NOTE)
{22064} GSM half rate-capable handset penetration (see the second NOTE)
Transceiver capability
Carrier conguration
Use of reserved channels/cell congestion
68P02900W21-R
4-3
GMR-01
Nov 2007
Planning
It is assumed that an AMR-capable handset or mobile includes both fr and hr

capability.
{22064} Most handsets or mobiles are GSM half rate capable.
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. Utilization of the half rate capability of AMR
and/or {22064} GSM half rate. Quality and capacity on page 4-5 describes the benets 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 benets in coverage of AMR Full Rate. The capacity increases made possible with half rate
are discussed, with examples showing the potential gains under a variety of congurations
and (half rate) capable handset penetration.
The information in Quality and capacity on page 4-5 can be used to help determine how AMR
full rate and AMR/{22064} GSM half rate is utilized. As stated earlier, there are three primary
methods of AMR usage, two of which apply to {22064} GSM half rate:
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 is particularly suited to areas where adverse propagation
conditions prevail.
Forced half rate: This is used when capacity is paramount. Voice quality is sacriced
to carry more calls per carrier. It is used in severely congested areas, or where voice
quality is not a concern.
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 conguration provides quality voice coverage
until congestion is reached. This capacity on demand conguration is well suited for
environments with varying trafc patterns. The information contained in Half rate
utilization on page 4-22 can be used to help congure the system to maximum effectiveness
when half rate is used.
Rate adaptation on page 4-16 provides information on the rate adaptation characteristics of
AMR. Miscellaneous information on page 4-21 provides information on emergency call handling
and circuit pooling. Hardware on page 4-29 contains a description of the new hardware and
what advantages it delivers.
4-4
68P02900W21-R
GMR-01
Nov 2007
Quality and capacity
Quality and capacity
Benets of AMR
The ability of the AMR codec to change dynamically 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 because of the ability to
operate at a lower C/I threshold. This can result in potentially higher trafc loading. However,
the benets of AMR do not extend to the signaling channels, or to the use of non-AMR codecs
and data services. Capacity gains of this type are dependent on other factors (for example,
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, is selected. This allows 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
signaling channels (presumed to be at least 2 dB, and possibly as high as 4 dB or 6 dB). This
can be exploited for range extension, or improved coverage in buildings. Range extension is
discussed further in AMR voice quality improvement and coverage on page 4-10 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. Mean Opinion Scores (MOS) are subjective. Test conditions affect
MOS. However, the relative performance of the codecs to each other is 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-3 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.
68P02900W21-R
4-5
GMR-01
Nov 2007
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 versus EFR versus 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
Sel. Requirements
4.01
4.01
4.01
AMR-FR
4.06
4.06
4.13
4.08
3.96
3.59
EFR
4.01
4.01
3.65
3.05
1.53
C/I= 1 dB
3.65
2.66
ti-GS M-AMR_FR_cle a n_s pe e ch_ve rs us _EFR-00112-a i-s w
Figure 4-2 shows the individual codec modes for AMR FR/clean speech, as illustrated in
Figure 4-1.
4-6
68P02900W21-R
GMR-01
Nov 2007
Figure 4-2
AMR FR/clean speech codec modes
MOS
5.0
4.0
3.0
EFR
12.2
10.2
7.95
7.4
6.7
5.9
5.15
4.75
2.0
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
4.01
3.65
3.05
1.53
4.13
3.93
3.44
1.46
C/I= 1 dB
EFR
4.01
12.2
4.01
10.2
4.06
3.96
4.05
3.80
2.04
7.95
3.91
4.01
4.08
3.96
3.26
1.43
7.4
3.83
3.94
3.98
3.84
3.11
1.39
6.7
3.77
3.80
3.86
3.29
1.87
5.9
3.72
3.69
3.59
2.20
5.15
3.50
3.58
3.44
2.43
4.75
3.50
3.52
3.43
2.66
4.06
ti-GS M-AMR_FR_cle a n_s pe e ch_code c_mode s -00113-a i-s w
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.
68P02900W21-R
4-7
GMR-01
Nov 2007
Figure 4-3 AMR HR/clean speech versus EFR versus GSM FR versus GSM HR versus
performance requirements
MOS
5.0
4.0
3.0
Sel. Requirements
AMR-HR
2.0
EFR
FR
HR
Conditions
1.0
Sel. Requirements
AMR-HR
No Errors
C/I=19 dB
C/I=16 dB
3.99
3.99
3.99
4.11
4.04
3.96
C/I=13 dB
C/I=10 dB
C/I= 7 dB
C/I= 4 dB
3.14
2.74
1.50
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
ti-GS M-AMR_HR_EFR_GS M_FR_GS M_HR_ve rs us _pe rform_re qnts -00114-a i-s w
4-8
68P02900W21-R
GMR-01
Nov 2007
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
5.15
4.75
FR
HR
2.0
1.0
Conditions
No Error s
C/I=19 d B
C/I=16 d B
C/I=13 d B
C/I=10 d B
C/I= 7 d B
C/I= 4 dB
4.21
3.74
3.74
3.9 6
3.3 7
2.5 3
1.60
3.9 5
3.5 2
2.7 4
1.78
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
3.46
3.42
3.30
3.10
2.00
3.14
2.74
1.50
3.24
2.80
1.92
EFR
4.21
7.95
4.1 1
4.0 4
7.4
3.9 3
3.9 3
6.7
4.75
3.59
FR
3.50
HR
3.35
3.50
1.58
ti-GSM-AMR HR_clean_speech_codec_modes-001
15-ai-sw
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 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 provides the capacity benet of
allowing two calls to exist in the space of one timeslot.
This behavior suggests that one viable deployment strategy is to use the 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 can also be moved to a fr channel through an interference-based handover, depending on
the congestion state of the cell and system parameter settings.
The Motorola system supports this conguration, 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 user. MOS scores are subjective and
vary depending upon customer expectations.
68P02900W21-R
4-9
GMR-01
Nov 2007
AMR voice quality improvement and coverage
AMR voice quality improvement and coverage

Analysis has shown that AMR FR under C/I = 13 dB provides the same quality of service (MOS
= 4) as GSM FR/EFR under C/I = 15 dB. AMR FR provides 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
are used:
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 are 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
modied or new networks where it has to be selected. The majority of terminals are AMR.
Non-AMR terminal performance could be degraded under these conditions.
Table 4-1
AMR potential coverage gains
Frequency
re-use pattern
Coverage at
15 dB
Coverage at
13 dB
Gain in coverage
(increase in cell
radius)
Gain in
coverage area
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%
First digit = # cell sites, second digit = # sectors/cell and third digit = # carriers/cell.
4-10
68P02900W21-R
GMR-01
Nov 2007
{22064} Benets of GSM half rate
{22064} Benets 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 benets 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 a needed basis.
GSM Half Rate speech quality

{22064}
Figure 4-1 shows how GSM Half Rate compares with the EFR, FR, and AMR HR codecs. Mean
Opinion Scores (MOS) are subjective and can vary depending upon customer expectations. Test
conditions affect MOS. However, the relative performance of the codecs to each other is 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 is also
moved to a fr channel through 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 neighbor cells exist.
The Motorola system supports this conguration, 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 user.
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 efcient.
In Figure 4-4 to Figure 4-8, the carried Erlangs (at 2% blocking) are shown for a variety of
carrier congurations. For each conguration, the capacity increase is shown as a function
of the handset penetration level.
68P02900W21-R
4-11
GMR-01
Nov 2007
The results shown were obtained through simulation and under the following assumptions:
A hr-capable handset is given a hr timeslot if available, else a fr timeslot on a fr carrier.
Preference is to assign a fr-capable only handset to a fr carrier if available; else, it is

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

timeslot that has the other subchannel 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. The actual
carried Erlangs can be slightly less than the Erlangs in the graphs.
Figure 4-5
3 carriers, only one hr-capable carrier
Ca rried E rlang s
(at ~2 % blocking)
25 .00 0
20 .000
15 .00 0
10 .000
5.0 00
0.0 00
0.00
0.10
0.20
0.30
0.40
0.50
0.60
0.90
1.00
ti-GSM-3_carriers_only_one_hr_capable_ carrier-001
16-ai-sw
0.70
0.80
AMR Ca pa ble MS Pen etr ation
4-12
68P02900W21-R
GMR-01
Nov 2007
Figure 4-6 3 carriers, all hr-capable

Car rie d Erlan gs
(at ~ 2% blocking)
40 .00 0
35 .00 0
30 .00 0
25 .00 0
20 .00 0
15 .00 0
10 .00 0
5.00 0
0.00 0
0.00
0.20
0.40
0.60
0.80
1.00
AMR Ca pa ble MS Pe ne tra tion

ti-GSM-3_carriers_all_ hr_capabler-001
Figure 4-7
17-ai-sw
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.60
0.40
0.80
1.00
AMR Ca pa ble MS Penetration

ti-GSM-5_carriers_only_one_hr_capable_carrier-001
68P02900W21-R
18-ai-sw
4-13
GMR-01
Nov 2007
Figure 4-8 5 carriers, only 3 hr-capable carriers

Carried Er langs
(at ~2% blocking)
60. 000
50. 000
40. 000
30. 000
20. 000
10. 000
0.000
0.10
0.00
0.20
0.30
0.40
0.50
0.60
0.70
0.80
0.90
1.00
AMR Capa ble MS Pe ne tra tion

ti-GSM-5_carriers_only_3 hr_capable_carriers-0019-ai-sw
Figure 4-9
5 carriers, all hr-capable carriers
Ca rried Er langs
(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
AMR Cap a ble MS Pe ne tra tion

ti-GSM-5_carriers_all_hr_capable_carriers-00120-ai-sw
4-14
68P02900W21-R
GMR-01
Nov 2007
Timeslot usage
Conclusions
Figure 4-4 to Figure 4-8 are useful in illustrating that, for some deployment strategies such as a
maximum capacity conguration, more carrier equipment should be congured as hr-capable
when hr capable handset penetration raises. 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 conguration and a 5 (all) hr-capable carrier conguration. The 5 hr-capable carrier
conguration is better able to utilize the extra capacity that hr offers as the handset penetration
rises. {22064} GSM hr-capable handset penetration is expected to be high.
When migrating a system to one that includes half rate, ensure that the call capacity rating of
the various components of the system have not exceeded. Use of hr improves the spectral
efciency 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 need fewer
hr-capable carriers. Figure 4-4 to Figure 4-8 demonstrates how even adding one hr-capable
carrier can increase Erlang capacity.
Timeslot usage
This section briey describes timeslot conguration and the algorithm used to optimize usage.
A GSM carrier consists of 8 timeslots, some or all of which can be used for voice trafc. In
full rate, each voice call occupies one timeslot. In half rate, the timeslot is split into two
subchannels, each of which is capable of supporting one hr call. A fr call cannot be carried
within two subchannels split across two timeslots. At any instance, depending on conguration,
a carrier contains a combination of fr and hr calls. To optimize capacity, it is desirable not to
have fragmented hr usage. That is, it is best to use both subchannels of a single timeslot rather
than one subchannel on two timeslots. This frees up contiguous subchannels for use in a fr call.
The Motorola algorithm attempts rst to assign new calls to timeslots that have one subchannel
in use before using a timeslot with both subchannels idle. This provides a large degree of
concentration. Some degree of fragmenting is unavoidable as calls begin and end and the
algorithm attempts to ll in the holes as new calls arrive. This applies to all arriving calls (for
example, originations, handovers, and so on).
It was also considered whether to further pack hr calls together through intra-cell handover
whenever fragmenting reaches a level where a fr call can be blocked. Simulations have been
carried out under a variety of congurations and conditions, and it was determined that the
negative aspects of performing the otherwise unnecessary handover outweighs the slight
capacity gain. Although the results varied according to penetration rate and conguration, 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.
68P02900W21-R
4-15
GMR-01
Nov 2007
Rate adaptation
Rate adaptation
Introduction
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
14 codec modes are dened for AMR; 8 for the fr channel mode, and 6 for the hr channel mode.
Up to 4 codec modes are utilized for any given voice call. This is called the Active Codec Set
(ACS). The uplink and downlink directions can 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 can be selected from the supported codec modes. An analysis has been performed to
determine that 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 is 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 bit

rate (fr)
Is codec mode
supported?
Speech codec bit

rate (hr)
Supported?
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
Yes
7.4 kbit/s
Yes
7.4 kbit/s
Yes
6.7 kbit/s
Yes
6.7 kbit/s
Yes
5.9 kbit/s
No
5.9 kbit/s
Yes
5.15 kbit/s
Yes
5.15 kbit/s
Yes
4.75 kbit/s
Yes
4.75 kbit/s
No
Through simulation and testing, default values were determined for the ACS and initial codec
modes. These initial values are subjected to change and are appropriate for all conditions.
4-16
68P02900W21-R
GMR-01
Nov 2007
Thresholds and hystereses
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 (that is 4 x 64 kbit/s timeslots per hr
carrier) then the 7.95 kbit/s codec mode is added to the hr ACS.
An initial codec mode is also required. The 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 the changing radio conditions as illustrated
in Figure 4-10.
Figure 4-10 Rate adaptations: codec modes, thresholds and hysterese

C/I
CODE C_ MODE_4
THR_3 + HYS T_3 = THR_MX_Up (3)
THR_3
= THR_MX_Dn (4)
CODE C_ MODE_3
THR_2
= THR_MX_Dn (3)
CODE C_ MODE_2
CODE C_ MODE_1
THR_1
= THR_MX_Dn (2)
ti-GSM-Rate_adaptations_codec_modes_thresholds_and_hystereses-00121-ai-sw
Rate adaptation thresholds and hystereses are set on a per cell basis.
68P02900W21-R
4-17
GMR-01
Nov 2007
Downlink adaptation MS monitor
Downlink adaptation MS monitor

There is a risk that certain mobiles have an impaired ability to estimate correctly the C/I for
a channel in certain conditions. For these mobiles the codec mode adaptation threshold and
hysteresis values proves to be inefcient, 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 efciently. 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 inefcient, and increase
or decrease the threshold and hysteresis values accordingly. The BSS instructs the MS of the
change in threshold and hysteresis values using the Channel Mode Modify procedure.
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
Minimum
Maximum
Default
amr_ms
_monitor
_period
10SACCH
periods
120SACCH
periods
40SACCH
periods
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.
amr_ms_high 0QBand
_rxqual
Units
7QBand
Units
4QBand
Units
Threshold for monitoring AMR

MSs continually requesting
the highest codec mode.
The threshold defaults to 2.5%
BER or RXQUAL4
amr_ms_low
_rxqual
0QBand
Units
7QBand
Units
2QBand
Units
Threshold for monitoring

MSs continually requesting
the lowest mode.
The threshold defaults to
0.5% BER or RXQUAL 2
1 dB
7 dB
3 dB
amr_dl_thresh
_adjust
4-18
Description
Used for detecting MSs
continually requesting the
highest or lowest modes.
If the user species a value
of zero, then the MS monitor
functionality is disabled.
For applying compensation to

the C/I adaptation thresholds.
Range is 1 to 7 dB in steps of 1
dB.
68P02900W21-R
GMR-01
Nov 2007
Handover and power control
Handover and power control
Introduction
This section explains the new AMR and {22064} GSM half rate specic handover and power
control threshold parameters. It does not explain how they are used, as this is according to
current operation. The ranges are not indicated either, as they are like 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-specic 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-specic 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-16. The default database
values follow the recommendations of Rxlev Handovers Disabled and Uplink diversity.
Table 4-4 Handover and power control - Full and Half Rate default values
Thresholds (UL/DL) - all gures in Q Band Units
Threshold
name
Non Frequency Hopping

No UL Diversity
Frequency Hopping
UL Diversity
RXLEV
enabled
RXLEV
disabled
RXLEV
enabled
RXLEV
disabled
l_rxqua
l_XX_p_
amr_fr
3/3
3/3
4/3
4/3
l_rxqua
l_XX_h_
amr_fr
4/4
4/4
5/4
5/4
l_rxqua
l_XX_p_
hopping
_amr_fr
No UL Diversity
UL Diversity
RXLEV
enabled
RXLEV
disabled
RXLEV
enabled
RXLEV
disabled
4/4
4/4
5/4
5/4
Continued
68P02900W21-R
4-19
GMR-01
Nov 2007
Handover and power control thresholds
Table 4-4
Handover and power control - Full and Half Rate default values (Continued)
Thresholds (UL/DL) - all gures in Q Band Units
Threshold
name
Non Frequency Hopping

No UL Diversity
RXLEV
enabled
RXLEV
disabled
Frequency Hopping
UL Diversity
RXLEV
enabled
RXLEV
disabled
No UL Diversity
UL Diversity
RXLEV
enabled
RXLEV
disabled
RXLEV
enabled
RXLEV
disabled
5/5
5/5
6/5
6/5
l_rxqua
l_XX_p_
hopping
_hr
2/2
2/2
2/2
2/2
l_rxqua
l_XX_h_
hopping
_hr
3/3
3/3
3/3
3/3
l_rxqua
l_XX_h_
hopping
_amr_fr
l_rxqua
l_XX_p_
hr
2/2
2/2
2/2
2/2
l_rxqua
l_XX_h_
hr
3/3
3/3
3/3
3/3
u_rxqua
l_XX_p_
hr
0/0
0/0
0/0
0/0
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 is attempted either if 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 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 neighbor cells, and both
hr_intracell_ho_allowed and force_hr_usage allow for it.
4-20
68P02900W21-R
GMR-01
Nov 2007
Miscellaneous information
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 is pre-empted. When selecting a call to pre-empt, the software attempts
to minimize the disruption by choosing rst a fr call of lower priority. Failing that, a lower
priority single occupancy hr call (the other subchannel 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 the 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 ask for resources from the BSS
that it knows are not 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 selected
taking into account the circuit pool the circuit belongs to and the required channel type.
The GDP supports FR, {22064} GSM HR and EFR speech only, while the EGDP supports fr,
EFR, and AMR. {22064} The GDP2 supports FR, GSM HR, EFR, and AMR. 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 select 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 select an EGDP/GDP2 CIC. If the call is not AMR possible, the MSC should select
a GDP CIC. If AMR is indicated as the only option and a CIC attached to a GDP is selected,
the call is 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, nor the circuit pool
and circuit pool list elements. Therefore, it is incumbent upon the MSC to do the selection. The
MSC vendors (Alcatel, Siemens, Nokia, and Nortel) support circuit pooling. (Specically 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-59 in Chapter 6 BSC planning steps and
rules, and Transcoding on page 7-11 in Chapter 7 RXCDR planning steps and rules.
For more detailed information on circuit pooling, refer to GSM 08, Mobile-services Switching
Centre - Base Station System (MSC - BSS) interface; Layer 3 specication.
68P02900W21-R
4-21
GMR-01
Nov 2007
Half rate utilization
Half rate utilization
Description
Some 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
their impact to 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 is 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 enable or disable and defaults to disable. It is congurable 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 (that is, busy
trafc 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 on page 4-24.
This parameter range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is
disabled and is the default value. It is congurable 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.
4-22
68P02900W21-R
GMR-01
Nov 2007
Advanced congestion relief allows the operator to set thresholds, in units of percentage, on a
cell basis that can trigger the handover of some calls to neighboring cells in order to reduce
congestion in the triggering cell.
There are two sets of thresholds dened within a cell that control the triggering of congestion
based intercell handovers:
tch_congest_prevent_thres (1-101)
mb_tch_congest_thres (1-101)
The tch_congest_prevent_thres parameter species the level at which the congestion relief
procedure is initiated. The mb_tch_congest_thres parameter species 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) exceeds, 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 call as meet the congestion handover criteria.
Calls within the cell consider RF conditions, so only the MSs near the candidate cell(s) are
moved.
Directed retry (mb_tch_congest_thres) redirects new trafc when the cell is congested,
resulting in the new call being moved to an alternative cell.
Call reconguration threshold

Intra-cell fr to hr call reconguration threshold (recong_fr_to_hr)
When the indicated threshold is exceeded, some fr calls within a cell are recongured (by
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 needs 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 qualication criteria to the half rate capable full rate calls before
allowing the reconguration to a half rate trafc channel. The qualication is based
upon the existing congestion relief (directed retry alternatives) criteria for congestion
based inter-cell handovers. The criteria identify calls, which are at the extremities
of the cell by using a power budget calculation involving the neighbor handover
congestion margin. The BSS does not perform reassignment to a half rate trafc
channel for a call, which is identied by the existing congestion relief calculations as
being at the extremities of the cell. This qualication is performed in an attempt to
ensure that the operator is provided with adequate QoS when the call is reassigned to
a half rate trafc 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 on page 4-24.
68P02900W21-R
4-23
GMR-01
Nov 2007
Once triggered, the BSS recongures, as many qualifying existing hr-capable calls (currently
using fr) to use hr as there are hr resources available.
This parameter range is 0-101 in steps of 1%. The value of 101 indicates the mechanism is
disabled and is the default value. It is congurable on a cell basis.
Inner zone utilization threshold

Inner zone utilization threshold (inner_hr_usage_thres)
This parameter is necessary because the recong_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 recong_fr_to_hr
threshold is exceeded. The BSS attempts 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
attempts to recongure 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 recongurations 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 recong_fr_to_hr being exceeded and when new_calls_hr is exceeded.
If the threshold recong_fr_to_hr has been exceeded, half rate capable full rate calls residing
on the inner zone are eligible as candidates for reconguration 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 are 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 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 congurable on a cell basis.
Reserved timeslots
Half rate resource guard limit (hr_res_ts)
When congestion triggered half rate usage either is employed, through call assignments
(cell congestion threshold forcing hr usage) or through recongurations (call reconguration
threshold), there must be available hr resources for the mechanism to work properly. This is
normally accounted for by setting recong_fr_to_hr and new_calls_hr such that when they are
triggered, there are sufcient 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) trafc 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 before the reserved timeslots in the inner zone
being considered.
4-24
68P02900W21-R
GMR-01
Nov 2007
The reserved timeslots are applied to the inner zone only, although it is congurable on all cells
and not just multi-zone cells. It has no effect when set on a non multi-zone cell.
The actual value within the inner zone can be dynamically limited to be less than hr_res_ts
by the BSS. The BSS limits the hr_res_ts for the inner zone if the BSS detects that the
inner_hr_usage_thres is not able to exceed if the hr_res_ts element is left as the user dened.
hr_res_ts is also limited by the number of half rate capable resources available in the cell or
zone.
This parameter range is 0-255 in steps of one timeslot. The default value is 2 timeslots (each
timeslot is capable of supporting two hr calls). It is congurable 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, 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. 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 range is 0-255 in steps of 1. The default value is 1 hop. It is congurable 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 species the
possible target channel types - full and/or half rate. Quality based handovers always target a
full rate channel when handovers are enabled. The force_hr_usage element overrides any
preference specied with the hr_intracell_ho_allowed element. The value of the element
causes the following behavior: 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 species the
possible target channel types - full and/or half rate. Quality based handovers always target a
68P02900W21-R
4-25
GMR-01
Nov 2007
Operational aspects
full rate channel when handovers are enabled. The force_hr_usage element overrides any
preference specied with the hr_intracell_ho_allowed element. The value of the element
causes the following behavior:
If hr_intracell_ho_allowed is set to hr intra-cell, handovers are disabled. If handover required
is 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 specied by the element:
intra_cell_handover_allowed.
If hr_intracell_ho_allowed is set such that hr intracell handovers are disabled. Then no
Handover Required is sent to MSC, then hr intra-cell handovers are not supported within the
cell. The intra-cell handover request is ignored by the BSS.
This functionality mirrors the fr functionality specied by the element:
intra_cell_handover_allowed.
If hr_intracell_ho_allowed is set such that hr intra-cell handovers are enabled and fr is 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 and hr is
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
user preference. A quality-based handover always targets a fr channel.
This parameter range is 0-3 and is congurable on a cell basis. The default value is 3.
Where:
Is:
Half-rate intra-cell handovers are not initiated by the BSS. Handover

required sent to MSC.
Half-rate intra-cell handovers are disabled. Handover required not sent

to MSC.
Half-rate intra-cell handovers are enabled. Full-rate only allowed.
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
maximize capacity gains by 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 using 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 can 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 (that is MSC allows AMR
hr and/or GSM hr, the CIC is capable of the transcoding, a hr channel is available, and so on).
4-26
68P02900W21-R
GMR-01
Nov 2007
Operational aspects
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 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 is congured 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 congurable 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, and so on).
By using the existing congestion relief feature and the cell reconguration threshold, additional
capacity can be attained. As described earlier, the congestion relief feature can be used to
identify calls most likely to benet from a switch to another, less congested, cell, and perform a
handover to move them. When this mechanism is employed, the operator can then use the cell
reconguration capability to increase capacity further by reconguring 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 prevents unnecessary inner zone recongurations. The conguration of
parameters takes place as follows:
The congestion threshold for hr usage (new_calls_hr) is selected.
If it is desired to attain additional capacity through call recongurations, and the congestion
relief feature is enabled, then the cell reconguration threshold is set at a level at which it
wishes to force qualifying MSs (on a fr channel) to be recongured to hr (recong_fr_to_hr).
This can be set above or below the congestion relief threshold, as calls qualifying for congestion
relief are not candidates for fr to hr reconguration. If voice quality (that is, fr) is the
primary concern, then congestion relief handover should be performed rst. In addition, the
reconguration threshold must not be set the congestion threshold for hr usage (new_calls_hr),
otherwise calls could be assigned fr and immediately recongured to hr. For multi-zone cells,
an inner zone utilization threshold is selected. In many cases, the criteria for inner zone hr
utilization is the same as the outer zone. In these cases, the inner zone utilization threshold can
be set the same as the new call threshold or the reconguration threshold.
Following the descriptions, the thresholds could be set in the pattern shown in Figure 4-11.
68P02900W21-R
4-27
GMR-01
Nov 2007
Operational aspects
Figure 4-11 Congestion threshold settings for AMR half rate

CONGE S TION
HIGH
rec onfig_fr_to _hr
new_c alls_hr a nd inne r_hr_us a ge _thre s
Conges tion re lie f thre s hold
LOW
ti-GSM-Cong estion_thr eshold_se ttings_for_AMR_half_rate-00122-ai-sw
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
congured. The value of these settings is particular to the system being optimized.
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 are capable of supporting both AMR and
GSM calls. The selection of AMR or GSM is dependent upon the MSC preferences (indicated
in the Channel Type element of the Assignment Request or Handover Request messages) and
the capabilities of the selected CIC.
4-28
68P02900W21-R
GMR-01
Nov 2007
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 one 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 ts 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 needs 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 needs all DSW2s to be used (within the BSC or RXCDR). KSWXs and DSWXs
are used (exclusively or mixed), with the restriction that a KSWX cannot 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 (that is MSIs, GDPs, EGDPs, and GDP2s) needs a specic
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 the later chapters of this manual.)
EC mode needs 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 cannot be connected
to a DSWX or vice-versa.
68P02900W21-R
4-29
GMR-01
Nov 2007
Equipment descriptions
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 conguration through a
rmware upgrade, can support a and 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 efcient solution is provided through 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 are 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 are 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.
4-30
68P02900W21-R
GMR-01
Nov 2007
Backhaul
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.
Like the BSSC2, the BSSC3 cabinet can function as a BSC (BSC2) or an RXCDR (RXCDR2),
depending on how the cabinet shelves are equipped. Figure 4-12 shows the alternative
congurations available for the BSSC3.
Earlier BSUs/RXUs were used in the BSSC3 cabinet instead of or in conjunction

with the BSU2/RXU3.
Figure 4-12 Alternative congurations for the BSSC3 cabinet

BSC2 Configuration
RXCDR2 Configuration
BSU2
RXU3
BSU2
BSU2
BSU2
Basic B SC 2
With
expansion
shel f, or as 2
sepa rat e
BSC2s
BSC2 w ith
transcod ing
RXU3
RXU3
Basic
RXCDR2
RXU3
RXCDR2 w ith
expansion
shelf
ti-GSM-Alternative_configurations_for_the_BSSC3_cabinet-00123-ai-sw
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
congured for each timeslot for a given RTF is based on database parameter settings.
68P02900W21-R
4-31
GMR-01
Nov 2007
Backhaul
The amount of terrestrial backing allocated for an RTF is based on three parameters:
hr_enabled (with values 0 = no half rate, 1 = half rate)
allow_8k_trau (with values 0 = no 8 k TRAU, 1 = 8 k TRAU)
pkt_radio_type (adds EGPRS support and supersedes allow_32k_trau)
Table 4-5
Backhaul conguration based on parameter settings
hr_enabled
pkt_radio_type
allow_8 k
_trau
0 = voice
only
1 = 16 k data
and voice
2 = 32 k data
and voice
3 = 64 k data and voice
16 k
16 k
32 k
{23769} VersaTRAU
32 k
32 k (data
uses only
16 k)
32 k
{23769} Not
Supported (allow_
8 k_trau cannot be
set to 0 if pkt_radio_
type is 3)
16 k
16 k
32 k
{23769} VersaTRAU
Table 4-6 shows how a fr call or two hr calls are placed onto the terrestrial backhaul.
Table 4-6
Call placement on terrestrial backhaul
hr_enabled
pkt_radio_type
allow_8 k
_trau
0 = voice
only
1 = 16 k data
and voice
Full rate
call on 16
k
Full rate call on left most 16

k subrate group of the 32 k
(duplicated on both 16 k in
the UL)
2 half rate calls on separate 16

k subrates
2 half rate calls share one 16 k subrate
4-32
2 = 32 k data
and voice
3 = 64 k data and voice

Full rate call
on 16 k subrate
corresponding to the
air timeslot - see
Table 4-7.
{23769} Not
supported.
{23769} Half rate
with 8 K switching
assigns the two half
rate voice channels to
the two bits allocated
to an air timeslot. The
rst 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 rst half
rate channel assigned
to B0 and the second
half rate channel
assigned to B1 see
Table 4-7.
68P02900W21-R
GMR-01
Nov 2007
Backhaul
{23769}
Table 4-7 Voice call mapping on the backhaul for a 64 K RTF

VersaTRAU
subchannel
DS0 Bit
0
DS0
Bit 1
DS0 Bit
2
DS0 Bit
3
DS0 Bit
4
DS0
Bit 5
DS0
Bit 6
DS0
Bit 7
A0
A1
B0
B1
C0
C1
D0
D1
E0
E1
F0
F1
G0
G1
H0
H1
2
Key: A - H are air timeslots 0 - 7 respectively.
The VersaTRAU Subchannel2 and any higher numbered VersaTRAU Subchannels

are always used to carry the multiplexed data for all the PDCHs congured on
this carrier.
The tables give sample congurations for 16 kbit/s, 32 kbit/s, and 64 kbit/s
backhaul. Figure 4-13 and Figure 4-14 apply only to the 16 kbit/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.
68P02900W21-R
4-33
GMR-01
Nov 2007
Backhaul
Figure 4-13
16 kbit/s
After-CIC
connection
AMR backhaul paths

CIC
EGDP/GDP2
16 kbit/s
Ate r-CIC
co nne ction
CIC
EGDP/GDP2
RXCDR
S witch
RXCDR
S witch
16 kbit/s Ate r
a lloca te d
16 kbit/s Ate r
a lloca te d
BS C
S witch
BS C
S witch
16 kbit/s Abis
ba ckha ul
16 kbit/s Abis
ba ckha ul
BTS
S witch
CCU
BTS
S witch
AMR fr ca ll over
a ir inte rfa ce
CCU
hr ca ll ove r a ir
inte rfa ce
(w / 7.95 kbit/s )
ti-GSM-AMR_backhaul_paths-00124-ai-sw
For a connected AMR hr call not requiring the 7.95 codec rate or a {22064} 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 the BSC and the
RXCDR then the path showed on the right in Figure 4-14 results. (The idle tone insertion is
used internally to ll the 16 kbit/s timeslot.)
4-34
68P02900W21-R
GMR-01
Nov 2007
Backhaul
Figure 4-14 hr backhaul paths - ESS mode enabled

16 kbit/s
Ate r-CIC
co nn ec tion
8 kbit/s
Ate r-CIC
co nn ec tion
CIC
EGDP / GDP 2
CIC
EGDP / GDP 2
8 kbit/s
idle tone
RXCDR
S witch
RXCDR
S witch
8 kbit/s Ate r
alloca te d
16 kbit/s Ate r
alloca te d
8 kbit/s
idle tone
BS C
S witch
BS C
S witch
8 kbit/s Abis
ba ckha ul
8 kbit/s Abis
ba ckha ul
BTS
S witch
BTS
S witch
CCU
CCU
hr call over a ir
inte rface
hr call over a ir
inte rface
ti-GSM-hr_backhaul_paths_ESS_mode_enabled-00125-ai-sw
68P02900W21-R
4-35
GMR-01
Nov 2007
Summary
Summary
AMR transcoding is supported using existing GDPs working in a tandem conguration,

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 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 nonMSI slots). The existing BSU shelf provides two E1 connectors per card slot, for
local transcoding congurations.
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 should be tailored per network.
4-36
68P02900W21-R
GMR-01
Nov 2007
Chapter
5
BTS planning steps and rules
This chapter describes the planning steps and rules for the BTS, including the macrocell and the
microcell. The planning steps and rules for the BSC are provided in Chapter 6 BSC planning
steps and rules, and that for the remote transcoder (RXCDR) are in Chapter 7 RXCDR planning
steps and rules. This chapter details the following sections:
BTS planning overview on page 5-2.
Macrocell cabinets on page 5-4.
Microcell enclosures on page 5-7.
Receive congurations on page 5-9.
Transmit congurations on page 5-12.
EGPRS enabled CTU2 conguration on page 5-14.
Antenna congurations on page 5-16.
Carrier equipment (transceiver unit) on page 5-17.
Micro base control unit (microBCU) on page 5-21.
Network interface unit (NIU) and site connection on page 5-22.
BTS main control unit on page 5-25.
Cabinet interconnection on page 5-28.
Battery back-up provisioning on page 5-33.
External power requirements on page 5-34.
Network expansion using macro/microcell BTSs on page 5-36.
Line interface modules (HIM-75, HIM-120) on page 5-37.
DRI/Combiner operability components on page 5-38.
68P02900W21-R
Nov 2007
5-1
GMR-01
BTS planning overview
BTS planning overview
Introduction
The following information should be available to plan the equipage of a BTS site:
Number of cells controlled by the site
Number of carriers required
Number of standby carriers per cell
Output power per cell

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

The potential future growth of the site must be known to make intelligent trade offs
between fewer cabinets/enclosures initially and ease of expansion later.
Existence of equipment shelters at the site

Macro or 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.
Requirement of battery backup equipment for the outdoor equipment
5-2
68P02900W21-R
GMR-01
Nov 2007
Outline of planning steps

Macrocell and microcell BTS sites
The information required for planning a macro/microcell BTS site is as follows:
Determine if the site is indoor or outdoor.
Number of macrocell cabinets required, refer to the section Macrocell cabinets on page 5-4.
For number of microcell enclosures required, refer to the section Microcell enclosures on
page 5-7.
For receiver conguration (including planning for Dual Band), refer to the section Receive
congurations on page 5-9.
For transmit conguration, refer to the section Transmit congurations on page 5-12.
For EGPRS enabled CTU2 conguration, refer to the section EGPRS enabled CTU2
conguration on page 5-14.
For antenna conguration, refer to the section Antenna congurations on page 5-16.
For the amount of carrier equipment required, refer to the section Carrier equipment
(transceiver unit) on page 5-17.
For the number of micro base control units required, refer to the section Micro base
control unit (microBCU) on page 5-21.
For the number of network interface units required, refer to the section Network interface
unit (NIU) and site connection on page 5-22.
For the number of E1/T1 links required, refer to the section Network interface unit (NIU)
and site connection on page 5-22.
For the number of main control units required, refer to the section BTS main control
unit on page 5-25.
For the number of FOX and FMUX boards required, refer to the section Cabinet
interconnection on page 5-28.
For battery back-up provisioning, refer to the section Battery back-up provisioning on
page 5-33.
For external power supply requirements, refer to the section External power requirements
on page 5-34.
68P02900W21-R
5-3
GMR-01
Nov 2007
Macrocell cabinets
Macrocell cabinets
Horizon II macr
Horizon II macro is the next generation replacement for Horizonmacro. Horizon II macro and
Horizonmacro are identical in terms of capacity and support the same numbers of carriers,
RSLs, and E1s. The Horizon II macro supports equipping of four RSLs per E1, thus reducing
the amount of E1 spans needed at a site that needs more than two RSLs. Horizonmacro and
M-Cell BTSs currently support two RSLs per E1.
A Horizon II macro cabinet (indoor or outdoor) can support 12 carriers when populated fully
with six CTU2s, used in double density mode, or can support six carriers when the six CTU2s
are used in single density mode. Expansion beyond 12 carriers per cabinet needs additional
cabinets. The 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 -40C to 50C.
The Horizon II macro does not support the use of CCBs.
Horizonmacro
A Horizonmacro cabinet (indoor or outdoor) can support six carriers (CTUs). Expansion beyond
six carriers needs additional cabinets. The Horizonmacro 12 carrier outdoor is, in effect, an
outdoor enclosure which can accommodate either one or two indoor cabinets for 6 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 50C. The Horizonmacro 12
carrier outdoor can operate at ambient temperatures up to 45C.
5-4
68P02900W21-R
GMR-01
Nov 2007
Horizoncompact and Horizoncompact2
Horizoncompact and Horizoncompact2

The Horizoncompact and the Horizoncompact2 are an integrated cell site, designed primarily
for outdoor operation and consist of:
BTS unit
This is like Horizonmicro / Horizonmicro2 and is a two-carrier cell with combining.
Booster unit
This incorporates two Tx ampliers, delivering 10 W (nominal) at each antenna.
The BTS can be wall-mounted or pole-mounted. The wall can be concrete, brickwork, stonework,
dense aggregate block work, or reconstituted stone, with or without rendering.
Cooling is by natural convection, and the unit can operate at ambient temperatures up to 50C.
The main difference between the Horizoncompact and the Horizoncompact2 is

that the latter can be expanded to support two additional BTSs.
In this document, future references to Horizoncompact2 also include

Horizoncompact unless specically stated otherwise.
M-Cell6
The M-Cell6 cabinet can support six carriers (TCUs or CTU2 Adapter in an EGPRS conguration)
or 12 carriers (TCUs or CTU2 Adapter in a non-EGPRS conguration). Expansion beyond
this needs additional cabinets. Outdoor cell sites are provided with an ancillary cabinet and
a side cabinet.
The M-Cell6 HMS has the following options:
Fans that circulate ambient air through the cabinet, for both indoor and outdoor units.
An air conditioning unit for ambient temperatures up to 55C, for outdoor cabinets only.
A heat exchanger for ambient temperatures up to 45C, for outdoor cabinets only.
M-Cell2
The M-Cell2 cabinet can support two carriers (CTU2 Adapter in EGPRS conguration) or
four carriers (CTU2 Adapter in non-EGPRS conguration). The M-Cell2 outdoor cabinet
accommodates all the elements in an indoor cabinet. It also provides limited accommodation for
LTUs and battery backup. A fan within the cabinet provides cooling. Unlike M-Cell6 outdoor
cabinets where the antenna terminations are in a side cabinet, M-Cell2 terminations are
on the main cabinet.
68P02900W21-R
5-5
GMR-01
Nov 2007
M-Cell2
The M-Cell2 HMS has 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 45C, for outdoor cabinets only.
An air conditioning unit for ambient temperatures up to 55C, for outdoor cabinets only.
5-6
68P02900W21-R
GMR-01
Nov 2007
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 signicant functionality that enables it to be classed as a Mini Macro BTS like the
M-Cell2 BTS. The architecture is based on the Horizon II macro architecture and effectively
Horizon II mini operates like 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 two
CTU2s that can be congured in both single density and double density mode. As a result, the
carrier capacity is 1-4 carriers, for a maximum network conguration of 16 to 24 carriers per
site dependent on cabinet capacity.
Horizon II mini is available as indoor and outdoor variant, and can be mounted on wall, oor,
or rack. The wall may be concrete, brickwork, stonework, dense aggregate block work, or
reconstituted stone, with or without rendering.
Software parameters are added to distinguish Horizon II mini cabinets to allow easier
conguration. 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 third party SDH module
requiring a 48 V dc power supply up to a maximum dissipation of 60W.
When the outdoor enclosure is congured with the SDH module, it can be a standalone only BTS.
68P02900W21-R
5-7
GMR-01
Nov 2007
Horizonmicro and Horizonmicro2
The outdoor enclosure conguration cannot be expanded in a network, as the

communications power card, to supply -48 V dc, should be inserted in the Site I/O slot.
Horizonmicro and Horizonmicro2

The Horizonmicro and the Horizonmicro2 are an integrated cell site, designed primarily for
outdoor operation and consist of a single small two-carrier BTS unit. The Horizonmicro and
Horizonmicro2 can be wall or pole-mounted. The wall may be concrete, brickwork, stonework,
dense aggregate block work, or reconstituted stone, with or without rendering.
Cooling is by natural convection, and the unit can operate at ambient temperatures up to 50C.
The main difference between the Horizonmicro and the Horizonmicro2 is that
the latter can be expanded to support two additional BTSs.
In this document, future references to Horizonmicro2 also include Horizonmicro

unless specically 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 congured
for two carriers in double density mode for GSM/GPRS or one 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 it 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 and 1800 MHz bands.
The Horizon II micro can be wall or pole-mounted. The wall may be concrete, brickwork,
stonework, dense aggregate block work, 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 50C.
5-8
68P02900W21-R
GMR-01
Nov 2007
Receive congurations
Receive congurations
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 is to go to multiple cabinets, it is distributed from the rst cabinet.
Horizonmicro2 and Horizon II micro are two-carriers only, combined to a single

antenna. Horizoncompact2 is two-carriers 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.
GSM900
The following factors should be considered when planning the GSM900 receive equipment:
Horizon II macro and Horizon II mini BTSs need 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.
68P02900W21-R
5-9
GMR-01
Nov 2007
Horizonmacro BTSs need 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 need 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.
DCS1800
The following factors should be considered when planning the DCS1800 receive equipment:
Horizon II macro and Horizon II mini BTSs need one 1800 MHz SURF2 for each cabinet.
Currently, the SURF2 is not dual band and only supports 900 MHz/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 need 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 MHz/900 MHz dual band.
M-Cell2 and M-Cell6 BTSs need one LNA for each sector. Receive antennas can be
extended across M-Cell6 cabinets by using the LNA expansion ports to feed an LNA
in another cabinet.
DCS1800 and GSM900

It should be considered that Horizon II macro Dual Band capable cabinets need 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 number of transceiver units for a dual band cabinet conguration
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.
5-10
68P02900W21-R
GMR-01
Nov 2007
Contact your Motorola Local Ofce for more information.
Refer to Chapter 12 Standard BSS and Horizon BTS congurations, for Dual
Band cabinet physical conguration.
Receiver planning actions

Determine the number of cells.
Determine the number of cells which have CTU2s/CTUs/TCUs in more than one cabinet
Determine the number of Rx antennas per cell supported in each cabinet.
Determine the type and quantity of receive equipment required.
When using CTU2s in double density mode, both carriers should be in the same
sector and can be individually reset. Dropping one carrier does not affect the second
CTU2 carrier.
68P02900W21-R
5-11
GMR-01
Nov 2007
Transmit congurations
Introduction
The transmit equipment provides bandpass ltering and signal combining for the BTS cabinets.
The CTU2 used in Horizon II macro can be congured 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 congurations available for Horizon II macro, Horizon II mini, Horizonmacro,
M-Cell2 and M-Cell6 BTSs are listed in Table 5-1.
Table 5-1
Cabinet Transmit
Congurations
Wide Band
Combining
Cabinet Transmit
Congurations Cavity
Combining
Number of Carriers
BTS Types
M-Cell2 and
M-Cell6
Horizonmacro 1 DCF or 1 TDF
Not available
Horizon II
1 DUP
Not available
2 DUP (BowtieCombiner)
Not available
mini
2
M-Cell2 and
M-Cell6
1 HCOMB + 1
TxBPF
1 CCB output
Horizonmacro 1 DCF
1 CCB output
M-Cell6
1 CCB output
1 or 2
1 TxBPF
Not available
macro
1 or 2
Horizon II
2 HCOMB + 1
TxBPF
Continued
5-12
68P02900W21-R
GMR-01
Nov 2007
Transmit planning actions
Table 5-1 Transmit congurations (Continued)
Number of Carriers
3
3 or 4
BTS Types
Cabinet Transmit
Congurations Cavity
Combining
Horizonmacro 2 DCF or 1 DDF
1 CCB output
Horizon II
DUP + 1 HCU or
2 DUP and Air
CCBs not supported
2 DUP (BowtieCombiner) and

Air
CCBs not supported
2 HCOMB + 1
TxBPF
1 CCB output + 1 CCB

extension
macro
3 or 4
Cabinet Transmit
Congurations
Wide Band
Combining
Horizon II
mini
4
M-Cell6
Horizonmacro 1 DDF + 1 HCU

extension
M-Cell6
3 HCOMB + 1
TxBPF

extension
Horizonmacro 2 DDF and Air

extension
M-Cell6
4 HCOMB + 1
TxBPF

extension
Horizonmacro 2 DDF and Air

extension
Horizon II
CCBs not supported
macro
1 DUP + 1 DHU
or 2 DUP + 1 HCU
and Air
A CCB output includes a TxBPF, but a CCB extension does not include it. {28075} If
the ITS feature is unrestricted and enabled,
EGPRS supports single density CTU2 conguration only.
The Tx conguration 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-13
GMR-01
Nov 2007
EGPRS enabled CTU2 conguration
EGPRS enabled CTU2 conguration
EGPRS enabled CTU2 conguration limitations

EGPRS is a restricted feature. This conguration is supported only when this feature
is unrestricted. {28075} If ITS feature is unrestricted and enabled, the EGPRS can be
congured on double density CTU2. The CTU2 radio is supported in the Horizon II macro and
Horizonmacro BTS cabinet platforms. In addition, the CTU2 radio is supported in the M-Cell6
and M-Cell2 cabinet platforms when the CTU2 Adapter is used.
EGPRS general conguration

The EGPRS feature needs additional backhaul to provision EGPRS carriers. The additional
backhaul is either seven DS0s to implement EGPRS on a BCCH carrier or eight 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 congured using
the rtf_ds0_count parameter.
{23769} If VersaTRAU is restricted, the maximum number of EGPRS carriers that can be
equipped for a three sector site is 21. The total number of E1s available at a Horizonmacro or
Horizon II macro site is 6. Some numbers of these DS0s are needed for RSLs to the BSC (up to 6
with MCUF, and H2 site controller). The rest of the DS0s are available for TRAU. An entire RTF
must be congured to the same physical E1. This allows conguration of three non-BCCHs.
EGPRS RTFs on each E1 (using 24 DS0s) for a total of 18 EGPRS non-BCCH carriers.
The remaining 7 DS0s can be used for BCCH RTFs and RSLs. Therefore, the worst-case
conguration when every possible timeslot is congured 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.
Three BCCH carriers (with 7 air timeslots on each RTF)
The remaining DS0s are available for use as RSLs.
{23769} If VersaTRAU is unrestricted, the maximum number of EGPRS carriers for the same
conguration can be up to 24. If the recommended non-aggressive backhaul of ve DS0s per
EGPRS carrier is used, six EGPRS carriers (using 30 DS0s) can be congured on each E1. This
would need four E1s for the 24 EGPRS carriers leaving the remaining four DS0s available
for RSLs.
BaseBand Hopping (BBH)

There are several restrictions for an EGPRS enabled CTU2.
5-14
68P02900W21-R
GMR-01
Nov 2007
Baseband hopping (BBH) is only allowed with other EGPRS enabled CTU2 radios in the same
hopping group. Table 5-2 and Table 5-3 show the restrictions for the Horizon II macro Site
Controller and the Horizonmacro Site Controller respectively. {28075} In ITS mode, EGPRS
double density carrier A and its pair are excluded for BBH.
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
EGPRS)
CTU2 (DD
GSM)
CTU2 (SD
GSM)
CTU (SD
GSM)
CTU2 (SD EGPRS)
CTU2 (DD GSM)
CTU2 (SD GSM)
CTU (SD GSM)
Table 5-3
BBH capability for Horizonmacro Site Controller

CTU2 (SD
EGPRS)
CTU2 (DD
GSM)
CTU2 (SD
GSM)
CTU (SD
GSM)
CTU2 (SD EGPRS)
CTU2 (DD GSM)
CTU2 (SD GSM)
CTU (SD GSM)

The Broadcast control channel (BCCH) Radio Transceiver Function (RTF) should be congured
as a 64 K carrier. For EGPRS, the only radio that supports 64 K is the CTU2. It is not necessary
that the CTU2 used for the BCCH RTF is EGPRS enabled.
68P02900W21-R
5-15
GMR-01
Nov 2007
Antenna congurations
Antenna congurations
The following factors should be considered when planning the antenna conguration:
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 conguration.
5-16
68P02900W21-R
GMR-01
Nov 2007
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
congured 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.
CCBs are not supported by the CTU2.

The transceiver unit for Horizonmacro is a CTU. This is eventually 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 Ofce.
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 an
enhancement of the original TCU and can be used as a direct replacement for the TCU. However,
TCU-B has 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 in CTU2s usage 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.
68P02900W21-R
5-17
GMR-01
Nov 2007
CTU/CTU2 power supply considerations
RF power output from the CTU2s is reduced.
Fully populated Horizonmacro cabinets that contain two or more CTU2s need three PSUs.
PSU redundancy is not available in these congurations.

Under normal circumstances, the Horizonmacro only needs 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 can be necessary to install a third PSM, thus losing
the internal battery backup facility. In cases where battery backup is required, an external
battery backup unit (BBS) needs to be added. In addition, where a third (redundant) PSM is
already installed, redundancy is 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 needs only one power
supply as minimum/maximum.
Table 5-4
CTU/CTU2 power requirements

Horizonmacro
Horizon II macro
Number of CTUs
Number of
CTU2s
Number
of power
supplies
required
Number of
CTU2s
Number of
power supplies
required
2
Continued
5-18
68P02900W21-R
GMR-01
Nov 2007
Table 5-4 CTU/CTU2 power requirements (Continued)

Horizonmacro
Horizon II macro
Number of CTUs
Number of
CTU2s
Number
of power
supplies
required
Number of
CTU2s
Number of
power supplies
required
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 are populated with TCUs.
Table 5-5
CTU/CTU2 power requirements for M-Cell cabinets
Number of CTU2 Adapters
Number of power supplies required
M-Cell6 AC Indoor:
16
14
56
14
56
2 (add one more for redundancy)
1 (add one more for redundancy)
M-Cell6 AC Outdoor:
M-Cell6 DC Indoor:
M-Cell2 AC Indoor and

M-Cell2 AC Outdoor:
68P02900W21-R
5-19
GMR-01
Nov 2007
The following factors should be considered when planning carrier equipment:
The number of carriers based on trafc 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-119 section in Chapter 3 BSS cell planning.
{28075} One transceiver unit is 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; one CTU2 can support one RF carrier or be congured to
support two RF carriers. The exception to this is for EGPRS. An EGPRS enabled CTU2 can
only be congured in single density mode (that is, one CTU2 per carrier). If ITS feature
is unrestricted and enabled, an EGPRS enabled CTU2 can also be congured in double
density mode but with timeslot blanking on the paired carrier.
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.
Transceiver planning actions

Determine the number of transceivers required and the number of power supplies required
to power the transceivers.
5-20
68P02900W21-R
GMR-01
Nov 2007
Micro base control unit (microBCU)
Micro base control unit (microBCU)
Introduction
The microBCU (or m BCU) is the macro/microcell implementation of a BTS site controller.
The following factors should be considered when planning the m BCU complement:
Horizon II macro/Horizon II mini

The Horizon II macro/Horizon II mini is like 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 needs 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 rst M-Cell2 cabinet needs one microBCU2 cage. Two microBCU2 cages can be
equipped for redundancy and/or additional E1/T1 link capacity. Additional cabinets do not
need microBCU2 cages.
MicroBCU planning actions

For M-Cell equipment, determine the number of microBCUs required.
68P02900W21-R
5-21
GMR-01
Nov 2007
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 tted 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:
Both Horizon II macro and Horizon II mini use the Horizon II site controller (HIISC).
NIU functionality is integrated into the HIISC. From the functional point of view, the
Integrated NIU functions in the same way as the standalone NIU with the exception that
support for four RSL links per E1 and a maximum of six 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 need
redundant site expansion boards and redundant XMUXs.
5-22
68P02900W21-R
GMR-01
Nov 2007
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 rst 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 signaling channel) to the site. In the
drop and insert (daisy chain) conguration, every site needs its own 64 kbit/s link
for signaling.
Redundancy for the NIU module depends on the number of redundant E1/T1 links to the
site.
Plan for a maximum of two NIUs per digital module shelf or microBCU cage (three E1or
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.
68P02900W21-R
5-23
GMR-01
Nov 2007
NIU planning actions
Table 5-6 Site connection requirements for M-Cell2 and M-Cell6

Number of E1/T1
links
Minimum number
of NIU required
Number of BCU
cages required
Notes
M-Cell2 and M-Cell6
M-Cell2 and M-Cell6
M-Cell6
M-Cell2 and M-Cell6
M-Cell2 and M-Cell6
M-Cell6 only
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.
5-24
68P02900W21-R
GMR-01
Nov 2007
BTS main control unit
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:
Both Horizon II macro and Horizon II mini 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 backward
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 maximum of 24 RF carriers across the sites.
The HIISC used in Horizon II macro can also support 24 RF carriers.
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 needs a HIISC.
For redundancy, add another 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 conguration also needs a redundant site expansion board in

all Horizon II macro cabinets at sites where more than one cabinet is installed.
68P02900W21-R
5-25
GMR-01
Nov 2007
Planning considerations Horizon II macro/Horizon II mini as expansion cabinet
Horizon II mini
Only the master Horizon II mini cabinet needs a HIISC. The HIISC used can support a
maximum 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 needs a MCUF.
An optional 20 MB PCMCIA memory card is installed for non-volatile code storage.
For redundancy, add another 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 an M-Cell6
or M-Cell2 site:
Only the master cabinet needs a MCU.
An optional 20 MB PCMCIA memory card is installed for non-volatile code storage.
For redundancy, add another mBCU cage and MCU in the master cabinet.
Planning considerations Horizon II macro/Horizon II mini as

expansion cabinet
This information describes the factors that require 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.
5-26
68P02900W21-R
GMR-01
Nov 2007
Planning actions
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 needs an MCUF.
A 20 MB 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.
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 needs an MCU.
A 20 MB PCMCIA memory card installed 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
Determine the number of HIISCs required.
Horizonmacro
Determine the number and conguration of MCUFs required.
M-Cell6 and M-Cell2

Determine the number and conguration of MCUs required.
68P02900W21-R
5-27
GMR-01
Nov 2007
Cabinet interconnection
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 two CTU2s in a Horizon II mini expansion cabinet.
Horizon II micro
Horizon II micro supports up to three cabinets. It can be connected to either another Horizon
II micro or any legacy macro or mini product through an expansion board like 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 and FMUX
and up to six TCUs.
The FMUX multiplexes and demultiplexes electrical connections for up to six TCUs or CTU2
Adapters onto a single ber optic connection operating at the rate of 16.384 Mbit/s.
5-28
68P02900W21-R
GMR-01
Nov 2007
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 need 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 needs 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
1 (master)
None
1 site expansion
board only
1 XMUX + 1
site expansion
board
1 site expansion
board only
1 XMUX + 1
site expansion
board
1 XMUX + 1
site expansion
board
1 site expansion
board only
1 XMUX + 1
site expansion
board
1 XMUX + 1
site expansion
board
Expansion 3
1 XMUX + 1
site expansion
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 need 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 to Table 5-10).
68P02900W21-R
5-29
GMR-01
Nov 2007
Horizon II mini
Table 5-8
Horizon II mini only network XMUX expansion requirements
Cabinet
Master
1 (master)
None
Expansion 1
Expansion 2
1 site
expansion
board only
1 XMUX + 1 site
expansion board
1 site
expansion
board only
1 XMUX + 1 site
expansion board
1 XMUX + 1
site expansion
board
1 site
expansion
board only
1 XMUX + 1 site
expansion board
1 XMUX + 1
site expansion
board
Expansion 3
1 XMUX + 1
site expansion
board
Table 5-9 Horizon II macro as master - Horizon II mini as expansion XMUX

requirements
Cabinet
Master
1 (master)
None
Expansion 1
Expansion 2
1 site
expansion
board only
1 XMUX + 1
site expansion
board
1 site
expansion
board only
1 XMUX + 1
site expansion
board
1 XMUX + 1 site
expansion board
1 site
expansion
board only
1 XMUX + 1
site expansion
board
1 XMUX + 1 site
expansion board
Expansion 3
1 XMUX + 1 site
expansion board
Table 5-10 Horizon II macro as master - Horizon II mini as expansion XMUX

requirements
Cabinet
Master
Expansion 1
Expansion 2
1 (master)
None
None
1 XMUX + 1
site expansion
board
None
1 XMUX + 1
site expansion
board
1 XMUX + 1
site expansion
board
1 FMUX
1 XMUX + 1
site expansion
board
1 XMUX + 1
site expansion
board
Expansion 3
1 XMUX + 1 site
expansion board
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.
5-30
68P02900W21-R
GMR-01
Nov 2007
Planning considerations - Horizon II macro as master cabinet
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 congurations
(see Table 5-11).
A fourth Horizonmacro cabinet needs one FMUX plus one FMUX in the master cabinet
(see Table 5-11).
Redundancy needs duplication of an FMUX and associated MCUF.
Table 5-11 Horizonmacro FMUX expansion requirements

Cabinet
Master
Expansion 1
Expansion 2
1 (master)
None
None
None
Expansion 3
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 needs a minimum of one FOX and FMUX plus one FMUX
in the rst cabinet.
Redundancy needs duplication of all FOX and FMUX boards and associated MCU and
microBCU cages.
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 while 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.
68P02900W21-R
5-31
GMR-01
Nov 2007
Planning considerations - Horizon II mini as 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 needs an additional HIISC and site
expansion board. Each Horizonmacro slave cabinet needs an additional FMUX, and each
M-Cell6 slave cabinet needs 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 conguration.
Horizon II mini outdoor variant needs a -230 V dc supply.
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.
5-32
68P02900W21-R
GMR-01
Nov 2007
Battery back-up provisioning
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 inuence the planning for battery back-up for a Horizon II outdoor
enclosure.
Two optional internal batteries to provide a minimum of 5 minutes back-up.
An optional external battery cabinet has dimensions 1555 x 799 x 760 mm 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 (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 xed to the ground housing
the batteries and an oversized shroud tted over it xed onto the main cabinet.
Size: 350 mm wide x 687 mm deep x 1441 mm high.
Weight: Without batteries including metalwork and interconnect cables, the weight is
40 kg. With batteries, the weight is 160 kg.
The frame can house a maximum of two strings of SBS C11 batteries (each string consisting of 2
batteries) which provides 1 hour back-up power.
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 a visual display of outdoor battery voltages.
68P02900W21-R
5-33
GMR-01
Nov 2007
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
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 88 to 265 V ac power
source.
Horizon II micro
The Horizon II micro enclosure operates from 88 to 300 V ac power source.
5-34
68P02900W21-R
GMR-01
Nov 2007
Power planning actions
M-Cell6
The M-Cell6 BTS cabinet can be congured 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 congured to operate from either a +27 V dc or 230
V/110 V ac power source.
M-Cellcity and M-Cellcity+

The M-Cellcity and M-Cellcity+ BTS enclosures operate from 88 to 265 V ac power source.
Power planning actions

Determine the power supply required.
68P02900W21-R
5-35
GMR-01
Nov 2007
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 can be expanded using macro/microcell. The Network topology can
be any of those specied in Chapter 2 Transmission systems of this manual. A macro/microcell
BTS can 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-66 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:
Sites with previous generation equipment should be expanded with the appropriate
modules, until the cabinets are full.
To expand a previous generation site, the equipment in the previous generation cabinet
must be re-congured so that it serves a complete set of sectors in the target conguration.
A macro site should then be added to the site to serve the remaining sectors.
The macro site should then be connected into the network by daisy chaining it to the
existing site.
Customers who have not purchased the daisy-chaining feature should order the free of
charge feature M-Cell - InCell Interworking, SWVN2460, to obtain a suitable license for
upgrading.
Example
To upgrade a BTS6 2/2/2 to a 3/3/3, recongure the BTS6 to a 3/3, order an M-Cell omni 3 and
install it to serve the third sector.
5-36
68P02900W21-R
GMR-01
Nov 2007
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 specic 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-37
GMR-01
Nov 2007
DRI/Combiner operability components
DRI/Combiner operability components
Overview
This enhancement improves the operability of the Digital Radio Interface (DRI) and combiner
devices by increasing the exibility 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
Firs t co ntrolling
S e con d con trolling
DRI
DRI
DRI 0 0
DRI 0 1
ti-GSM-DRI_and_combiner_relationship-00126-ai-sw
5-38
68P02900W21-R
GMR-01
Nov 2007
Chapter
6
BSC planning steps and rules
The plans for setting up a BSC and the relevant rules to be followed are described in this
chapter. The topics described in this chapter 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 signaling link capacities on page 6-10.
Determining the number of RSLs required on page 6-20.
Determining the number of MTLs required on page 6-35.
Determining the number of LMTLs required on page 6-42.
Determining the number of XBLs required on page 6-44.
Determining the number of GSLs required on page 6-47.
Generic processor (GPROC) on page 6-52.
Transcoding on page 6-59.
Multiple serial interface (MSI, MSI-2) on page 6-66.
Kiloport switch (KSW) and double kiloport switch (DSW2) on page 6-68.
BSU shelves on page 6-71.
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) on page
6-74.
Generic clock (GCLK) on page 6-77.
Clock extender (CLKX) on page 6-78.
Local area network extender (LANX) on page 6-80.
Parallel interface extender (PIX) on page 6-81.
Line interface boards (BIB, T43) on page 6-82.
68P02900W21-R
Nov 2007
6-1
GMR-01
DRI and combiner relationship
Digital shelf power supply on page 6-84.
Non Volatile Memory (NVM) board on page 6-85.
Verifying the number of BSU shelves and BSSC cabinets on page 6-86.
6-2
68P02900W21-R
GMR-01
Nov 2007
BSC planning overview
BSC planning overview
Introduction
Information pertaining to the NEs must be known to plan the equipage of a BSC. The NE
conguration needs the following information:
Number of BTS sites to be controlled.
Number of RF carriers (RTF) at each BTS site.
Number of TCHs and PDTCHs at each site.
Total number of AMR half rate or {22064} GSM half rate capable TCHs at each site.
Total number of TCHs and PDTCHs under the BSC.
Number of cells controlled from each BTS site should not exceed the maximum number of
cells per BSC detailed in Table 6-1.
Physical interconnection of the BTS sites to the BSC.
Location of the XCDR function.
Path for the OML links to the OMC-R.
Use of E1 links.
Use of balanced or unbalanced E1.
Trafc load to be handled (also take future growth into consideration).
Number of MSCs to BSC trunks.
LCS architecture.
Mixing of equipment types

The planning rules for each type of shelf should be taken into account, when mixing the BSU and
RXU shelves at a BSC. This needs using the information contained in this chapter (for the BSC)
and those in Chapter 7 RXCDR planning steps and rules (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 is
required in the BSC when the RXU3 shelf or shelves are used.
68P02900W21-R
6-3
GMR-01
Nov 2007
Outline of planning
Outline of planning
Planning a BSC involves the following steps:
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-20.
Plan the number of E1 links between the BSC and BTS site(s). Refer to the section BSC to
BTS E1 interconnect planning actions on page 6-30.
Plan the number of MTL links between the BSC and MSC. Refer to the section Determining
the number of MTLs required on page 6-35.
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-44.
Plan the number of GSL links required between the BSC and the PCU. Refer to Determining
the number of GSLs required on page 6-47.
Plan the number of GPROCs required. Refer to the section Generic processor (GPROC)
on page 6-52.
Plan the number of XCDR/GDP/EGDP/GDP2s required. Refer to the section Transcoding

on page 6-59.
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-42. Ignore this if the BSS supports
only the NSS-based LCS architecture.
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-42. Ignore this if the BSS supports only the NSS-based
LCS architecture.
Plan the number of MSIs required. Refer to the section Multiple serial interface (MSI,
MSI-2) on page 6-66.
Plan the number of KSWs/DSW2s and timeslots required. Refer to the section Kiloport
switch (KSW) and double kiloport switch (DSW2) on page 6-68.
Plan the number of BSU shelves. Refer to the section BSU shelves on page 6-71.
Plan the number of KSWXs/DSWXs required. Refer to the section Kiloport switch extender
(KSWX) and double kiloport switch extender (DSWX) on page 6-74.
Plan the number of GCLKs required. Refer to the section Generic clock (GCLK) on page
6-77.
Plan the number of CLKXs required. Refer to the section Clock extender (CLKX) on page
6-78.
Plan the number of LANXs required. Refer to the section Local area network extender
(LANX) on page 6-80.
Plan the number of PIXs required. Refer to the section Parallel interface extender (PIX)
on page 6-81.
6-4
68P02900W21-R
GMR-01
Nov 2007
Outline of planning
Plan the number of (P) BIB or (P) T43s required. Refer to the section Line interface boards
(BIB, T43) on page 6-82.
Plan the power requirements. Refer to the section Digital shelf power supply on page 6-84.
Decide whether an NVM board is required. Refer to the section Non Volatile Memory
(NVM) board on page 6-85.
Verify the planning process. Refer to the section Verifying the number of BSU shelves
and BSSC cabinets on page 6-86.
68P02900W21-R
6-5
GMR-01
Nov 2007
Capacity calculations
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 trafc channels
(TCHs). These capacities are limited by the ability of the processors, and the links to process
the signaling information associated with these TCHs.
The following sections, discussed, provide information on how to calculate processor
requirements, signaling link capacities and BSC processing capacities:
BSC system capacities
BSS signaling link capacities
Trafc models
BSC GPROC functions and types
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:
In certain congurations, the RXCDR call (CIC) capacity is greater than that of a BSC.
A failure of an RXCDR or communication line does not result in a complete failure of

the BSC to handle calls.
Each BSC connects to up to nine RXCDRs, and vice-versa. The level of connectivity is
constrained by the number of XBLs supported. The connectivity is limited to 20 at each BSC and
RXCDR (see Determining the number of XBLs required on page 6-44 required in this chapter).
The operator determines the level of connectivity. 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 the major factors in deciding the
conguration.
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 conguration 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
Nov 2007
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
384a,b
384a,b
DRIs
512
512
512
RSLs
250
250
250
PCUs
GSLs
12
180c
180c
MMS
128
128
128
PATHs
250
250
250
DHPs
232
232
232
LCFs
25
25
25
2400a
2400a,b
2400a,b
C7 links to MSC
16
16
16
C7 links to SMLC
16
16
16
102
102
102
90,000
90,000
90,000
Trunks (see NOTE )
E1 links
Maximum busy hour call
attempts
a - The capacity 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. For example, slot 20 and
slot 24 in shelf 0 and slot 20 in shelf 1.
c - 60 per PCU.
68P02900W21-R
6-7
GMR-01
Nov 2007
Scaleable BSC
The capacities represent the BSS capacities for GSM circuit-switched trafc. If the GPRS trafc
is carried on the BSS, the GSM circuit-switched trafc handling capacity reduces in direct
proportion to the timeslots congured for GPRS trafc.
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 rst element to reach its limit sets the capacity
of the BSC. For example, when dimensioning a BSC with a specic non-standard call model,
there is a possibility that the LCF or C7 limit is 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 users in terms of BSC size are addressed by a single platform that can
be efciently congured in small, medium, or large models.
Before 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 efciently addressed by the scaleable BSC
where minimal incremental hardware is required to be added as the networks grow. From
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 slot 24 in shelf 0 and slot 20 in shelf 1). Being
able to expand capacity within a BSC is benecial 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 before 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 was 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 is 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).
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.
6-8
68P02900W21-R
GMR-01
Nov 2007
Enhanced BSC capacity option
Enhanced BSC capacity option

This feature is introduced as a restricted 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.
BTP processors at the InCell BTSs must be replaced with GPROC2s.
From GSR8, GPROC3s are required in the BSP slots.
LCS option
This feature is a restricted 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 Center (SMLC) architecture or the BSS-based SMLC architecture, and
the BSS supports new LCS signaling for cell ID +TA positioning method:
New LCS signaling messages on the A-interface or Lb interface.
New LCS signaling 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 is provided for NSS-based and BSS-based LCS architectures respectively in
the following sections.
68P02900W21-R
6-9
GMR-01
Nov 2007
BSC signaling trafc model

For a GSM system, the throughput of network entities, including subcomponents, depends
upon the assumed trafc model used in the network design or operation. Trafc models are
fundamental to some 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 signaling links connecting it to the other
network elements. These elements include MSC, BTSs, and the OMC-R. Depending on its device
type and BSC conguration, a GPROC controls signaling links to one or more other network
elements. A capacity gure can be stated for each GPROC device type in terms of a static
capacity such as the number of physical signaling 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 signaling information to be
processed by the BSC is related to the offered call load (the amount of trafc offered/generated
by subscribers). When calls are blocked due to all trunks or all TCHs being busy, most of the
signaling 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 signaling resources (for example; MTLs and RSLs).
In the case where the BSC has more than enough trunks to handle the offered trafc, adequate
signaling resources should be planned to handle the potential carried trafc. The trunk count
can be used as an approximate Erlang value for the potential load carried.
As a result, the signaling links and processing requirements should be able to handle the
greater of the following:
Offered load
Potential load
The number of trunks or the offered call load in Erlangs (whichever is greater) should be used
to determine the link and processing requirements of the BSC.
BSC capacity planning needs a model that takes into consideration the signaling 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
trafc 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.
6-10
68P02900W21-R
GMR-01
Nov 2007
A standard trafc model can be assumed when initially planning a network.

However, once the network is running, it is critical to monitor and measure the
real call parameters (described in Chapter 11 Call model parameters) from the
live network to ascertain the true network call model.
Future planning should then be based on this actual (non-standard) call model
instead of the standard call model. Past studies have shown that the actual call
model in some networks differs considerably from the standard call model, and
this has a direct impact on dimensioning requirements.
Figure 6-1 graphically depicts various factors that should be taken into account when planning a
BSS.
68P02900W21-R
6-11
GMR-01
Nov 2007
{23769}
Figure 6-1 BSS planning diagram

MS C
TRANS CODER
WITH S UBMULTIP LEXING TRANS CODING AT MS C
1 x 64 KBIT/S CIRCUIT/C7 S IGNALLING LINK
1 x 64 KBIT/S CIRCUIT/X.25 S IGNALLING LINK *
1 x 64 KBIT/S CIRCUIT/ XBL
1 x 64 KBIT/S CIRCUIT/4 TRUNKS
1 x 64 KBIT/S CIRCUIT/8 TRUNKS
(HALF RATE WITH 8 KBIT/S S UBMULTIP LEXING ENABLED)
A INTERFACE (TERRES TRIAL LINKS )

-C7 S IGNALLING LINKS
-X.25 CONTROL LINK *
-REQUIRED TRUNKS
WITH S UBMULTIP LEXING TRANS CODING AT BS C

1 x 64 KBIT/S CIRCUIT/C7 S IGNALLING LINK
1 x 64 KBIT/S CIRCUIT/X.25 S IGNALLING LINK*
1 x 64 KBIT/S CIRCUIT/TRUNK
GDS INTERFACE **
- GDS TRAU CHANNELS
- GS L LINKS
GBL
BS C TO P CU
GDS -TRAU
CIRCUITS
THE # OF GS Ls
THE # OF GBLs
P CU
1 x 16 KBIT/S CIRCUIT/GP RS TIMES LOT

FOR CS 1 AND CS 2
2 x 16 KBIT/S CIRCUIT/GP RS TIMES LOTS
FOR CS 3 AND CS 4
1 x 64 KBIT/S GS L LINK
RTF_DS 0_COUNT x 64 KBIT/S
FOR EACH EGP RS RTF
THE BS C TO MS C 64 kbit/s CIRCUITS ARE DETERMINED

FROM THE # OF TRUNKS REQUIRED TO CARRY THE
S UMMATION OF AIR INTERFACE TRAFFIC (IN ERLANGS ,
TYP ICALLY US ING 1% BLOCKING) FROM ALL BTS s
- P LUS THE # OF GDS TRAU LINKS (DETERMINED FROM THE
NUMBER OF GP RS TIMES LOTS UNDER A BS C)
- P LUS THE # OF C7 S IGNALLING LINKS
- P LUS - (IF AP P LICABLE*)
THE # OF X.25 LINKS (US UALLY ONE P ER BS C)
- P LUS THE # OF XBL LINKS
- P LUS THE # OF GS L LINKS
BS C
1 x 64 KBIT/S OF 1 x 16 KBIT/S RTF CIRCUIT/LAP D
S IGNALLING LINK
2 x 64 KBIT/S CIRCUITS /RTF
4 x 64 KBIT/S CIRCUITS /RTF (S EE NOTE)
MOTOROLA BS C/BTS INTERFACE

NON-BLOCKING
THE # OF TCHs REQUIRED (US ING TYP ICALLY 2%

BLOCKING) TO CARRY S UBS CRIBER TRAFFIC.
THE TCHs P LUS THE REQUIRED S IGNALLING TS s
DIVIDED BY EIGHT (OR 16 WITH HALF RATE
MANDATED) DETERMINES THE CARRIERS REQUIRED
(ON A BTS /S ECTOR BAS IS )
BTS
AIR INTERFACE
-TCHs , P DTCHs AND S IGNALLING TS s
-TYP ICALLY 2% BLOCKING FOR CS
TRAFFIC
AIR INTERFACE
TRANS CODING MUS T BE LOCATED AT THE

BS C, OR BETWEEN THE BS C AND MS C
8 pt. le ft a ligne d te xt
TCH
= TRAFFIC
CHANNEL TS
=
TIMES LOT
USING TRAFFIC, TO DETERMINE THE E1 LINK INTER CONNECT

HARDWARE FOR THE A AND BSC TO BTS INTERFACE
ti-GSM-BSS_planning_diagram-00127-ai-sw
6-12
68P02900W21-R
GMR-01
Nov 2007
Typical parameter values
4 x 64 kbit/s circuits/RTF for a (AMR or 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 require to be taken into account when planning a BSS:
MTL link provisioning to support LCS signaling between the MSC and BSC for either NSS
based LCS architecture or BSS-based LCS architecture, but not both.
LMTL link provisioning for BSS-based LCS architecture only.
RSL link provisioning with LCS supported.

The parameters required to calculate BSC processing and signaling link capacities are listed in
Table 6-2 with their typical values.
Two methods for determining the BSC link capacity are given. The rst method is based on the
typical call parameters given in Table 6-2 and simplies planning to look up tables, or the simple
formulae indicated in the standard trafc model planning steps. When the call parameters being
planned differ signicantly from the standard trafc model, more complex formulae must be
used as indicated in Nonstandard trafc model planning steps.
Table 6-2
Busy hour peak signaling trafc parameter

Call duration
Reference parameter
T = 120 seconds
S = 0.1
H = 2.5
Ratio of location updates to calls:

non-border location area
l = 2

location area
l = 7
I = 0
Location update factor: non-border

location area using IMSI type 2
L = 2
Location update factor: border location

area using IMSI type 2
L = 7
GSM circuit-switched paging rate in

pages per second
PGSM = 15
Continued
68P02900W21-R
6-13
GMR-01
Nov 2007
Table 6-2 Typical call parameters (Continued)

Reference parameter
i = 0.6
Ratio of intra-BSC handovers to all

handovers
Lcs = 0.2

LRMT = 0.95
LRMO = 0.05
Percent link utilization (MSC to BSS)
U(MSC BSS) = 0.20
U(MSC BTS) = 0.25
UBSC-RXCDR = 0.40
Percent link utilization (BSC to SMLC)
UBSC-SMLC = 0.20
UCCCH = 0.33
Block Rate for TCHs
PB-TCHs = 2%
PB-Trunks = 1%
CBTS = 3

SMSSIZE = 100 bytes
GPRS parameters
GPRS Average packet size (bytes)
PKSIZE = 270
GPRS Trafc per sub/BH (bytes/hr)

Uplink
ULRATE = 30
GPRS Trafc per sub/BH (bytes/hr)

Downlink
DLRATE = 65

sub/BH)
PSATT/DETACH = 0.6
PDPACT/DEACT = 1
RAU = 1.4
Routing area update

RLC/MAC layer
PGPRS = 3
CS1
CS2
CS3
CS4
= 9.2
= 13.6
= 15.8
= 21.8
kbit/s
kbit/s
kbit/s
kbit/s
CellUpdate = 1.5
XBL (enhanced auto connect)

parameters
MNEWCALL = 1

handover
MHANDOVER = 1
Continued
6-14
68P02900W21-R
GMR-01
Nov 2007
Table 6-2 Typical call parameters (Continued)

Reference parameter
Length of an average XBL message, in

bytes
LXBL =50
Hhr-fr = 1
EGPRS parameters
EGPRS Average packet size (bytes) Uplink
PKDLULSIZE = 287
EGPRS Average packet size (bytes) Downlink
PKDLDLSIZE = 700
EGPRS Trafc per sub/BH (kbytes/hr) Uplink
ULRATE = 39
EGPRS Trafc per sub/BH (kbytes/hr) Downlink
DLRATE = 85

sub/BH)
Avg Sessions per sub = 3

PSATT/DETACH = 0.6
PDPACT/DEACT = 1
RAU = 1.4
Routing area update

Coding scheme rates (MSC1-MSC9) at
the RLC/MAC layer
PGPRS = 3
MCS1
MCS2
MCS3
MCS4
MCS5
MCS6
MCS7
MCS8
MCS9
=
=
=
=
=
=
=
=
=
10.55
12.95
16.55
19.35
23.90
31.10
46.90
56.50
61.30
These include 2G-3G handovers.
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 rst formula given . When IMSI detach is enabled, the second or third of the formulas given
should be used. The type of IMSI detach used is a function of the MSC.
If IMSI detach is disabled:
L=1
68P02900W21-R
6-15
GMR-01
Nov 2007
Assumptions used in capacity calculations
If IMSI detach type 1 is enabled:

L = 1+ 0.2 * I
If IMSI detach type 2 is enabled:
L = 1+ 0.5 * I
Other parameters
Other parameters used to determine GPROC and link requirements are listed in Table 6-3.
Table 6-3 Other parameters used in determining GPROC and link requirements
Busy hour peak signaling
trafc mode
Reference parameter
Number of MSC - BSC trunks
Number of BTSs per BSS
Number of cells per BSS
Pages per call

LCS request rate
(req/sec/BSC)
PPC = PGSM * (T/N)

LCS_BSC_Rate = (N/T) * LCS

Signaling message sequence and size assumptions
Certain signaling message sequence patterns and message sizes have been assumed to calculate
link and processing capacity values for the various procedures included in the signaling trafc
model. These assumptions translate into specic formula coefcients 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 signicantly different behavior. The
procedures used for the calculations are provided in Table 6-4.
Table 6-4 Signaling message procedures

MSC - BSC
BSC - BTS
SMLC - BSC
Call setup and clearing
Call setup and clearing
N/A
Handover, incoming and

outgoing
Handover, incoming and

outgoing
N/A
Location update
Location update
N/A
SMS - P to P
SMS - P to P
N/A
IMSI detach (type 1)
Paging
N/A
Continued
6-16
68P02900W21-R
GMR-01
Nov 2007
Table 6-4
Signaling message procedures (Continued)
MSC - BSC
IMSI detach (type 2)
BSC - BTS
SMLC - BSC
One phase access and

Enhanced one phase access
N/A
Enhanced One
Phase is not
supported with
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 signaling link
utilization between the BSC-BTS and BSC-PCU.
An additional assumption, which is made in determining the formula coefcients, is that the
procedures not included in the trafc model are considered to have a negligible effect.
Supplementary Service (SS) messaging has not been taken into account. This could
contribute a signicant signaling 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 signaled to the BSC through the
setting of the Cell Identication Discriminator in the BSSMAP paging message. The BSC
can determine from its Conguration Management database the cells that require to be
paged from the location area code only. Therefore, the MSC does not require to send a
list of each individual cell identity. Paging by LAC and Cell ID increases the length of the
BSSMAP paging considerably and signicantly increases the C7 signaling 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 mismatch 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 Conguration
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.
68P02900W21-R
6-17
GMR-01
Nov 2007
Link capacities
Half rate assumptions

An (AMR or {22064} GSM) half rate enabled carrier is capable of carrying two half rate calls in
each timeslot, for 16 (half rate) TCHs. The actual number in use at a given instance depends
upon such factors as user (both BSS and MSC) preference, mobile (that is, AMR capable)
penetration, RF conditions, handoff parameter, and threshold setting, cell congestion levels,
and so on.
If it is known to a large degree of certainty what is the mix of half rate and full rate calls, 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 signaling link capacity
required, and half rate usage is expected to be no more than 50%, and there are two (both half
rate enabled) carriers, a mix of 9 fr and 10 hr (plus 2 timeslots for signaling) TCHs can be used
(for a total of 19). A worst case estimate assumes 16 TCHs per half rate enabled carrier, for 28
TCHs. If only one carrier is half rate enabled, worst case results in (16 hr, 6 fr) 22 TCHs.
When 8 kbit/s subrate switching is not available, or an RTF is congured 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 needs 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 cannot include 7.95 kbit/s, when pkt_radio_type is set to 3.
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 impact of failure of any one link on the signaling trafc is less.
Reconguration around the fault could be less disruptive. Such a design could offer reduced
queuing delays for signaling messages. A design that utilizes fewer links at a higher message
rate, reduces the number of 64 kbit/s circuits required for signaling, 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 veries 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) become
overloaded.
6-18
68P02900W21-R
GMR-01
Nov 2007
Link capacities
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.
The protocol C7, used for the MSC to BSC links and SMLC to BSC links, allows for the signaling
trafc from the failed link to be redistributed among the remaining functioning links. Both the
MSC-BSC and SMLC-BSC C7 link set ofcially have at least two and at most 16 links. The
failure of links, for any reason, causes the signaling 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 signaling links.
68P02900W21-R
6-19
GMR-01
Nov 2007
Determining the number of RSLs required
Determining the number of RSLs required
Introduction
Each BTS site that is connected directly to the BSC, including the rst 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 signaling)
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
signaling links are required. Refer to the section Determining the required BSS signaling
link capacities on page 6-10 in this chapter to determine the number of RSL links required.
If closed loop daisy chains are used, each site needs a RSL in both directions.
The provision of additional RSL links for redundancy.
PCCCH signaling 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 is removed from the RSL.
If LCS is enabled in the BSS, the signaling 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 in Chapter 2
Transmission systems for further details. 64 kbit/s RSLs must be used when allowable
numbers are exceeded.
6-20
68P02900W21-R
GMR-01
Nov 2007
Determining the number of RSLs
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

Number of 16 kbit/s RSLs
Supported
BTS Platform
A BSU-based BTS
Horizon II macro and Horizonmacro
Horizonmicro2 / Horizoncompact2
M-Cell6
M-Cell2
M-Cellmicro and M-Cellcity
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.
Determining the number of RSLs

The equation for determining the number of RSL links for the combined signaling 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 signaling links on a per BTS site basis
operating at a 16 kbit/s RSL rate or at a 64 kbit/s RSL rate.
RSLGPRS
the number of RSL signaling links required to serve the GPRS part of
the network at 16 kbit/s or at 64 kbit/s.
RSLGSM
the number of RSL signaling 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 a mobile station can use to
establish an uplink TBF. The packet access performs in either one phase or in two phases.
In GPRS software architecture before GSR6, the BSS supports only the two phase-access
procedure. Now, one phase access mode and enhanced one phase access mode are supported.
68P02900W21-R
6-21
GMR-01
Nov 2007
Standard trafc model
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 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 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 reduces
by approximately 60 ms or more.

The number of BSC to BTS signaling 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 to the nearest integer value) for a BTS to support the given number of
TCHs and PDTCHs, based on the typical call parameters given in the standard trafc model
column of Table 6-2. If the call parameters differ signicantly from the standard trafc model,
use the formulae for the non-standard trafc model.
Table 6-6 assumes that there are no cells with PCCCH enabled.
Enhanced One Phase is not supported with EGPRS carriers.
For assumptions specic to half rate refer to section Half rate assumptions
on page 6-18.
Table 6-6 Number of BSC to BTS signaling links (without LCS)

With Enhanced One Phase
Access
With One Phase Access
#TCHs/BTS
(n)
#PDTCHs/
BTS (Ngprs)
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
<= 30
15
30
45
60
3
Continued
6-22
68P02900W21-R
GMR-01
Nov 2007
Table 6-6 Number of BSC to BTS signaling links (without LCS) (Continued)
Access
#TCHs/BTS
(n)
31 to 60
61 to 90
91 to 120
121 to 150
#PDTCHs/
BTS (Ngprs)
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
75
90
15
30
45
60
75
90
15
30
45
60
75
90
15
30
45
60
75
90
15
30
45
60
75
90
6
Continued
68P02900W21-R
6-23
GMR-01
Nov 2007
Access
#TCHs/BTS
(n)
#PDTCHs/
BTS (Ngprs)
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
151 to 180
15
30
45
60
75
90
181 to 210
211 to 240
241 to 270
15
30
45
60
75
90
15
30
45
60
75
90
15
30
45
60
75
90
10
9
Continued
6-24
68P02900W21-R
GMR-01
Nov 2007
Access
#TCHs/BTS
(n)
#PDTCHs/
BTS (Ngprs)
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
# 64 kbit/s
RSLs
# 16 kbit/s
RSLs
271 to 300
15
10
10
30
10
10
45
10
10
60
10
10
75
10
10
90
10
10
10
10
15
11
11
30
11
11
45
11
11
60
11
11
75
11
11
90
11
11
11
11
15
12
12
30
12
12
45
12
12
60
12
12
75
12
12
11
11
15
12
12
30
12
12
301 to 330
331 to 360
361 to 384
The RSL calculations assume PGPRS = 0 for cells in which NGPRS = 0. This is not
necessarily true. If the BSC has GPRS timeslots, even if the cells do not have
trafc channels congured as PDTCHs, it may have paging trafc.
RACH_Arrivals/sec gures have been calculated using Avg_Sessions_per_user

as in the call model table. GPRS_Users_BTS has been calculated based on the
number of timeslots congured on the cell.
68P02900W21-R
6-25
GMR-01
Nov 2007
Non-standard trafc model
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 tables may not be valid. 64 kbit/s RSLs must be used
if the allowable number of 16 kbit/s RSLs is exceeded.

64 kbit/s RSLs
If the call parameters differ signicantly 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 signaling (+ 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 (NOM I) is enabled and every cell in the BTS site has PCCCH enabled
(pccch_enabled = 1):
Otherwise:
The RSL trafc 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
6-26
68P02900W21-R
GMR-01
Nov 2007
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 signicantly 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 signaling (+ 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 (for example NOM I) is enabled and every cell in the BTS site has PCCCH
enabled (pccch_enabled = 1):
RSLGSM@16K={(n)*(59+S*(25+SMSSIZE*0.125)+38*H+24*L+24*LCS)/(1000*U*T)+
((31+3*C BTS)*PGSM/(8000*U))*(NGSM_only_MS/NGSM_Capable_-MS) }*4
Otherwise:
RSLGSM@16K={(n)*(59+S*(25+SMSSIZE*0.125)+38*H+24*L+24*LCS)/(1000*U*T)+(31+3*CBTS)*
PGSM/(8000 *U) }*4
68P02900W21-R
6-27
GMR-01
Nov 2007
Therefore, the total number of 16 kbit/s RSLs required is:
When all cells in the BTS have PCCCH enabled then RSLGPRS@16k = 0.
GPRS RACH arrivals

The average number of RACH arrivals per second is given by:
RACH/sec depends on the trafc prole on the network. For the same amount of data
transferred per user in a busy hour, if the trafc is predominantly WAP, then the
number of RACH arrivals is high compared to what is observed when the data trafc
is predominantly FTP transfers. The trafc prole should be calculated based on the
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 in GSRs before GSR6. With interleaving, TBFs it is possible to have
multiple MSs on each timeslot. Customers should consider this fact when estimating
the sessions for the formula.
6-28
68P02900W21-R
GMR-01
Nov 2007
In the equations:
Where:
RSLGSM + GPRS
Is:
the number of BSC-BTS signaling links.
the number of TCHs at the BTS site.
the ratio of SMSs to calls.
SMSSIZE
the average size of the SMS message (payload only).
the number of handovers per call.
the location update factor
LCS
the number of LCSs per call.
the percent link utilization (example 0.25).
the average call duration.
PGSM
the GSM paging rate in pages/second.
PGPRS
the GPRS paging rate in pages/second.
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 signaling (attach, detach, PDP
context activation/ deactivation, routing area updates, and so on).
NGSM_Only_MS
NGSM_Capable_MS
PCCCH_BTS
RPCCCH_Cells_in_BTS
the number of mobiles in the system that do not support GPRS.

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.
Equals 0, if all cells in the BTS have PCCCH enabled, otherwise,
this equals 1.
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) trafc. The default value of this
parameter is 55%, which means that GPRS trafc cannot utilize more than 45% of the total RSL
bandwidth, that is, 45% of the total link capacity (16 k or 64 k).
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 trafc (much higher than the planned 25%) the ratio of CS to GPRS trafc is maintained, the
default value (55%) for percent_traf_cs can be adjusted to reect it.
Take an example where total RSL MEAN utilization is 25%, and the ratio of CS to GPRS trafc
4 to 1. In other words, CS contributes 20% to RSL utilization and GPRS contributes 5%.
Maintaining the same ratio during a surge suggests to set percent_traf_cs to 80%, meaning
that GPRS cannot occupy more than 20% of total RSL bandwidth.
68P02900W21-R
6-29
GMR-01
Nov 2007
BSC to BTS E1 interconnect planning actions
BSC to BTS E1 interconnect planning actions

Determine the number of E1 links required to connect to a BTS. Redundant links are 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,
either L16 or L64 RSL can be used to a single BTS, but not both.
Table 6-7 denes the backhaul required for the different coding schemes and congurations.
Table 6-7 Backhaul requirements

16 kbit/s
32 kbit/s
GSM Voice only carries

where the half rate
exception case does not
apply.
GSM Voice only carriers

where the half rate
exception case does
apply.
Carriers with only GPRS

CS1 and CS2 enabled.
Carriers with only GPRS

CS1, CS2, CS3, and CS4
enabled.
6-30
{23769} VersaTRAU backhaul

EGPRS capable carriers
(MCS1-MCS9).
68P02900W21-R
GMR-01
Nov 2007
BSC to BTS E1 interconnect planning example
{23769} All EGPRS carriers (pkt_radio_type = 3) 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 three 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 is calculated as follows:
In this example, 3 E1s are required to backhaul this BTS to the BSC. To nd out the total
number of E1s required for a BSC, all of the BTSs backhaul requirements would require to be
calculated and then added together.
Refer to the network conguration 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.
{23769} The same example is presented 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, and CS4.
1 carrier of EGPRS, VersaTRAU is unrestricted and RTF backhaul is set to 5.
68P02900W21-R
6-31
GMR-01
Nov 2007
Determining the number of LCF GPROCs for RSL and GSL processing
The number of E1s would be calculated as follows:

The number of E1s is calculated as follows:
In this example, 3 E1s are required to backhaul this BTS to the BSC. To nd out the total
number of E1s required for a BSC, all of the BTSs backhaul requirements would require to be
calculated and then added together.
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) on page 6-52 later in this chapter.
The calculations are performed separately for the number of GPROCs required for GSM trafc
and for GPRS trafc.
The LCF GPROCs can simultaneously handle signaling trafc from both the GSM and GPRS
parts of the network. It is possible to calculate the GPRS/EGPRS part of the signaling 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 rst is used when the call parameters
are like those listed in Table 6-2 (standard trafc model). The second method is used when
the call parameters differ signicantly from those listed in the tables (that is non-standard
trafc model).
Standard trafc model (without LCS)
Use the formula:
GL3 = n/1060+B/160+C/120
6-32
68P02900W21-R
GMR-01
Nov 2007
Where:
GL3
Is:
the number of LCF GPROCs required to support the layer 3 call processing.
the number of TCHs at the BSC (see Half rate assumptions on page 6-18
earlier in this chapter).
the number of BTS sites.
the number of cells.

If the call parameters differ signicantly from those given in Table 6-2, the alternative formula
given should be used to determine the recommended number of LCFs.
GL3 = n*(1+0.35*S+0.34*H*(1-0.4*i)+0.32*L+0.35*LCS)/(19.6*T) +
(0.00075*PGSM+0.004)*B+C/120
The 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.
the number of TCHs under the BSC (see Half rate assumptions on page
6-18 earlier in this chapter).
the ratio of SMSs to calls.
the ratio of intra-BSC handovers to all handovers.
the location update factor.
the average call duration.
PGSM
the GSM paging rate in pages per second.
the number of cells.
LCS
Having calculated the LCF GPROCs for RSLs, ensure that the trafc is evenly
distributed across the LCFs. This can be difcult in cases where large sites are being
used, and in such cases additional LCFs are required. Alternatively, use the formula
for trafc 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.
68P02900W21-R
6-33
GMR-01
Nov 2007
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 signicance 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. The planning information provided here should
be used for this provisioning.
Where
Where:
GL3_GPRS
Total_RACH/sec
RPCCCH_Cells
B
PCCCH_BSS
PGPRS
Is:
the number of LCF GPROCs to handle GPRS related RSL
signalling trafc.
the sum of all GPRS RACH arrivals at the BSC.
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.
0 if all cells in the BSS have PCCCH enabled, otherwise = 1.
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 signaling).
6-34
68P02900W21-R
GMR-01
Nov 2007
Determining the number of MTLs required
Determining the number of MTLs required
Introduction
MTLs carry signaling trafc between the MSC and BSC. BSC supports MTL with 64 kbit/s
and 2 Mbit/s. The number of required MTLs depends upon the BSS conguration size and
trafc model. 64 kbit/s MTLs are carried on E1 links between the MSC and BSC, which are
also used for trafc.
The following factors should be considered when planning the links from the BSC to MSC:
Determine trafc requirements for the BSC. Trafc is determined using either of the
following methods:
Multiply the number of subscribers expected to use the BSC by the average trafc
per subscriber.
or
Total the trafc 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 trafc 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 is mapped onto the physical links.
Setting the mtl_loadshare_granularity database element to 1 results in a more even
distribution of trafc across the MTL links. This feature allows a more gradual increase in
the number of MTLs required with the increased trafc load on the BSC.
Determine if LCS is enabled in the BSS and which LCS architecture is supported by
the BSC. The BSC can 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 1550 to 1600, with
20% link utilization, the number of 64 k 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 64 k MTLs is required.
This results from the enhanced load sharing of 64 k MTLs and illustrates the difference
between setting the load share granularity to 0 and 1 respectively.
68P02900W21-R
6-35
GMR-01
Nov 2007

The number of MSC to BSC signaling 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-signaling trafc across 16 or 64 logical links,
which are then evenly spread across the active MTLs.
{25779} GPROC3s are required in the BSP slots.

CCITT C7 uses a 4-bit number, the Signaling Link Selection (SLS), generated by the upper
layer to load share message trafc among the in-service links of a link set. When the number
of in-service links is not a power of 2, some links experience a higher load. The BSS supports
distribution of signaling 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 signaling for the call load. Table 6-8 and
Table 6-9 give the recommended minimum number of MSC to BSC signaling 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 also increases. 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 conrmation is

gained from the Motorola local contact, or local ofce, that the switch is compatible
with the load share granularity set to 1.
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.
6-36
68P02900W21-R
GMR-01
Nov 2007
Table 6-8 Number of MSC and BSC signaling links without LCS (20% utilization)
N = the greater of
number of MSC-BSC
trunks or the offered
load from the BTSs
Number of MTLs with 16

logical links

logical links
Minimum
required
With
redundancy
Minimum
required
With
redundancy
N <= 170
170< N <=370
370 < N <= 500
500 < N <= 550
550 < N <= 760
760< N <= 940
940< N <= 1020
1020< N <= 1120
1120< N <= 1230
1230< N <= 1550
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
Table 6-9 Number of MSC and BSC signaling links without LCS (40% utilization)
N = the greater
of number of
MSC-BSC trunks
or the offered load
from the BTSs

logical links

logical links
Minimum
required
With
redundancy
Minimum
required
With
redundancy
N <= 370
370< N <=760
760 < N <= 1020
1020 < N <=

1120
1120 < N <=

1550
1550< N <= 1910
1910< N <= 2070
2070< N <= 2270
3120< N <= 3200
16
16
10
11
68P02900W21-R
6-37
GMR-01
Nov 2007
The capacities shown in Table 6-8 , Table 6-9 are based on the standard trafc
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 64 k 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 veries 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.

If the call parameters differ signicantly from those given in Table 6-2, the following procedure
is used to determine he required number of 64 k DS0 MSC to BSC signaling links:
Use the formula to determine the maximum number of Erlangs supported by a C7 signaling
link (nlink).
Use the formula to determine the maximum number of Erlangs supported by a GPROC
(LCF-MTL) supporting a C7 signaling link (nlLCF-MTL).
The maximum amount of trafc an MTL (a physical link) can handle (nlmin) is the smaller
of the two numbers from:
Signaling over the A-interface is uniformly distributed over some logical links. The number
of logical links is dened 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
signaling is load shared. Hence, the total amount of trafc that a logical link would hold, is
calculated as:
Next we require to determine the number of logical links each MTL (physical link) can
6-38
68P02900W21-R
GMR-01
Nov 2007
handle
Finally, the number of required MTLs (mtls) is:
mtls should not exceed 16 per BSC.
The formula to determine the maximum number of Erlangs supported by a

GPROC (LCF-MTL) has been calculated using 70% mean utilization of GPROC2
(see Calculate the number of LCFs for MTL processing on page 6-40 later in this
section). Field experience suggests it is good practice to maintain the mean
utilization of GPROCs at or below 70%.
Where:
Is:
the percent link utilization (for example 0.20).
call hold time.
the ratio of SMSs per call
SMSSIZE
the average size of the SMS message (payload only).
the ratio of intra-BSC handovers to all handovers.
the location update factor.
Clcs
26 for NSS-based architecture. 31 for BSS based architecture.
LCS
PPC
the number of pages per call.
the number of BTSs supported by the BSC.
mtls
the number of MTLs required
round up
round up to the next integer.
round down
MIN
Ng
R
round down to the next integer.

the minimum of two values.
the number of logical links (16 or 64).
the number of redundant MTLs.
68P02900W21-R
6-39
GMR-01
Nov 2007
Calculate the number of LCFs for MTL processing
Calculate the number of LCFs for MTL processing

The purpose of the MTL LCF GPROC is to support the functions of MSC link protocol.
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) on page 6-52 later in this chapter. {25779} For
GSR8, if the MTL is assigned to the BSP, a GPROC3 is required.
It is not recommended that an LCF supports both MTLs and RSLs. It is not
permitted for a LCF to support both MTLs and LMTLs.
LCFs for 64 k MTL links

Since one LCF GPROC can support two 64 k MTLs, the number of required LCFs is:
However, if the trafc model does not conform to the standard model:
If
then NLCF=mtls
Otherwise,
Where:
NLCF
ROUND UP
Is:
the number of LCF GPROCs required.
rounding up to the next integer.
mtls
calculated in the previous section.
nlink
nlLCF-MTL
6-40
68P02900W21-R
GMR-01
Nov 2007
MSC to BSC signaling over a satellite link
MSC to BSC signaling 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
signaling 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.
68P02900W21-R
6-41
GMR-01
Nov 2007
Determining the number of LMTLs required
Determining the number of LMTLs required
Introduction
LMTLs carry the LCS signaling trafc 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 conguration size and trafc model.
LMTLs are carried on E1 between the SMLC and BSC.
The following factors require to be considered when planning the number of LMTL links from
the BSC to the SMLC:
Determine the LCS trafc requirements of the BSC.
A BSC can only connect to one SMLC.
Determining the number of LMTLs

Trafc model
The number of required LMTLs depends upon the BSS conguration size and trafc 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:
LLMTL
Is:
the number of BSC to SMLC signaling links.
LCS_BSC_Rate
requests number per BSC per second.
UBSC_SMLC
the percentage of the link utilization.
ROUND UP
6-42
68P02900W21-R
GMR-01
Nov 2007
BSC to SMLC interconnection planning actions
BSC to SMLC interconnection planning actions

Determine the number of E1 links required to connect to a SMLC. Redundant links are added, if
required.
Where:
Is:
NBSC-SMLC
the minimum number of E1 links required (rounded up to an integer).
ROUND UP
The BSC-SMLC signaling 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) on page 6-52 later in this chapter. {25779} From
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-43
GMR-01
Nov 2007
Determining the number of XBLs required
Determining the number of XBLs required
Introduction
XBLs carry the signaling trafc 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 require to be considered when planning the number of XBL links from the
BSC to the RXCDR:
Determine the trafc 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 Transmission systems for a description
of the modes.
A maximum of 20 XBLs (64 kbit/s or 16 kbit/s) can be congured for a BSC/RXCDR.
A BSC can connect to a maximum of 10 RXCDRs and vice-versa.
Determining the number of XBLs

The calculations 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 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.
Table 6-10
Number of BSC to RXCDR signaling links

No redundancy
With redundancy
N = number of
redundancy MSC
to BSC trunks
Number of 64 kbit/s
XBLs
Number of 16
kbit/s XBLs
Number of 64
kbit/s XBLs
Number of 16
kbit/s XBLs
N 1200
1200 < N
2400
16
2400 < N
3200
11
22*
* This exceeds the 20 XBL limit and is therefore not a valid conguration.
6-44
68P02900W21-R
GMR-01
Nov 2007
It is recommended that the XBL link utilization does not exceed 40%. This allows a link to
double the capacity (to 80%) under fault conditions (in some congurations). 80% utilization,
queuing 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 conguration. 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 is a minimum number that are required, regardless of measured utilization. This is due
to peak usage requirements during start up and recongurations 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 was veried 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
40%
Link utilization
120 s
Call duration
Average XBL message size
50 bytes
XBL messages per new call *
XBL messages per full rate <-> half rate

handover
Full rate <-> half rate handovers per call
* Mobile origination, mobile termination, hand-in from MSC.
Non standard trafc model

If the call parameters differ signicantly 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:
68P02900W21-R
6-45
GMR-01
Nov 2007
Non standard trafc model
Where:
Is:
XBL
the number of BSC to RXCDR signaling links.
the number of MSC-BSC trunks.
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-46
68P02900W21-R
GMR-01
Nov 2007
Determining the number of GSLs required
Determining the number of GSLs required
When only E1 is used, PCU needs one E1 in order to carry GSL signaling, and a second E1 for
redundancy. In this conguration, PCU can support up to 30 primary GSL 64 kbit/s timeslots and
30 redundant. Each 64 kbit/s timeslot is one LAPD channel. 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 signaling information. The LAPD and BSS protocol parts
can be considered messaging overhead. In addition, in a similar manner to RSL, the GSL trafc
depends on the access mechanism used on the Air interface. The calculation for the required
number of GSL links during runtime (after the system stabilizes) is as shown.
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-47
GMR-01
Nov 2007
Where:
GPRS paging is performed per routing area (RA). A GPRS page is 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. The
GSL requirements for GPRS paging is given by the following:
Where:
GSL
Is:
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 signaling while the system

is stable.
PGPRS
Total_RACH/sec
U
the GPRS paging rate in pages per second.

the sum of all GPRS RACH arrivals on the BSC.
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 signaling).
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
6-48
68P02900W21-R
GMR-01
Nov 2007
Load balancing
Load balancing
When applying even distribution of GSLs terminated on LCFs, the GSL trafc is load balanced
over all GSLs. Furthermore, should more than one GSL terminate on a LCF, the load is 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 trafc.
The rst 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 automatically distributes the
GSLs to different LCFs (Auto mode) or if the operator should specify the LCF (Manual mode)
that terminates the GSL.
In Auto mode, the user 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.
In Manual mode, the user 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 require to specify LCFs outside of sysgen mode or wish to congure the
system manually, the GSLs should be evenly distributed among the LCFs that terminate the
RSLs.
Algorithm description for GSL distribution (Auto mode)

When the Auto mode is selected, the following algorithm is used to distribute the GSLs on
the LCFs.
Procedure 6-1 Algorithm description for GSL distribution (Auto mode)
Use the following equation to determine the maximum number of GSLs that
have to be terminated on a LCF.
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.
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.
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.
Go through the rst 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.
Continued
68P02900W21-R
6-49
GMR-01
Nov 2007
Load balancing
Procedure 6-1 Algorithm description for GSL distribution (Auto mode) (Continued)
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.
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.
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.
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 fromMAX_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 signicantly reduces the messaging between GPROCs. Previously,
it was common to assign all or most GSLs to a single LCF, which resulted in unnecessary
trafc between this LCF and other LCFs carrying RSL trafc. 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
signicantly reduced. This is the sole purpose of this procedure.
The operator can choose to distribute manually the GSLs, but it is recommended to use a similar
approach - evenly distribute among LCFs carrying RSL trafc. Although it is not necessary,
the operator can chose to consider the total count of PDTCHs on each LCF and assign more
GSLs to those LCFs having more PDTCHs.
Example
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 algorithm GSL 0 from PCU 0, GSL 0 from PCU 1 and GSL 0 from PCU
2 is 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 is terminated on LCF 1.
Using step 6 from the above algorithm GSL 2 and GSL 8 from all the PCUs is terminated on
LCF 0.
6-50
68P02900W21-R
GMR-01
Nov 2007
Load balancing
Again, using step 6 from the above algorithm GSL 3 and GSL 9 from all the PCUs is terminated
on LCF 1.
Using step 8 from the above algorithm GSL 10 from all the PCUs is terminated on LCF 0.
Again, using step 8 from the above algorithm GSL 11 from all the PCUs is terminated on LCF 1.
Therefore, the nal distribution of GSLs on the LCFs is as follows:
LCF
LCF
LCF
LCF
LCF
LCF
0 has GSL 0, GSL 2, GSL 8 and GSL 11 from all the PCUs.
3 has GSL 5, GSL 14 and GSL 18 from all the PCUs.
4 has GSL 6, GSL 15 and GSL 19 from all the PCUs.
5 has GSL 7 and GSL 16 from all the PCUs.
68P02900W21-R
6-51
GMR-01
Nov 2007
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 specically refers to the original GPROC.
GPROC2 specically refers to the GPROC2.
GPROC3 specically refers to the GPROC3.
GPROC is used in this manual as a non-specic 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 conguration 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 except in the BSP slots where a GPROC3 is
required. GPROC3s cannot be used with 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 conguration 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
conguration management scheme.
There are a limited number of dened 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.
6-52
68P02900W21-R
GMR-01
Nov 2007
GPROC functions and types
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).
Optimization link (OPL).
The dened 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 denes the GPROC types/functions for different software releases.
Table 6-12
Software
Release
GPROC type/function
BSP
MTL-LCF
LMTLLCF
RSL-LCF
OMF
CSFP
GSR7
GPROC2
or
GPROC3
GPROC2
or
GPROC3
GPROC2 or
GPROC3
GPROC2 or
GPROC3
GPROC2 or
GPROC3
GPROC2
or
GPROC3
GSR 8
onwards
GPROC3
GPROC2
or
GPROC3
GPROC2 or
GPROC3
GPROC2 or
GPROC3
GPROC2 or
GPROC3
GPROC2
or
GPROC3
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} A GPROC3 is mandatory in the BSP capable slots.
68P02900W21-R
6-53
GMR-01
Nov 2007
GPROC3 planning assumptions
GPROC3 planning assumptions

The following assumptions are made regarding planning GPROC3 usage:
GPROC3 processing performance is improved, when compared with GPROC2.
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. 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 sees 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 congured 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-signaling link (RSL) and layer 3 processing or MTL/LMTL (C7
signaling link) communications links. It also runs the GSLs for GPRS signaling
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).
6-54
68P02900W21-R
GMR-01
Nov 2007
The following factors should be considered when planning the GPROC complement:
BSP limitation
{25779} From 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 needs:

One master GPROC3 (BSP).
One OMF (if it is a type 2 BSC).
Some LCFs for MTLs, see Link control function.
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 signaling 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 signaling LCFs. Where multiple shelves
exist, each shelf should have a minimum of two GPROCs to provide redundancy within
that shelf.
Link control function

The following factors should be considered when planning the number of LCFs:
MTLs are assigned to dedicate 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_overload_
threshold is set to 100. The default value is 80, meaning that the 641st non-emergency
call is rejected (80% x 800 = 640 active calls). Refer to Technical Description: BSS
Command Reference (68P02901W23) for further details.
68P02900W21-R
6-55
GMR-01
Nov 2007
Cell broadcast link
For optimum performance, GSL handling should be distributed among the LCFs that
terminate RSLs. (See Load balancing on page 6-49 in the previous section).
Combining MTL and RSL processing on a single GPROC is not recommended.
The planning rules for LCFs using GPROCs are:
A single GPROC supports two MTLs each working at 20% link utilization. However, if the
link utilization 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 criteria, either rebalancing of sites on the available LCF
GPROCs at the BSC is required or additional LCF GPROCs are required to be equipped at
the BSC to process the trafc 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 terminate on the same GPROC, so if return loops are used, then the maximum
number of BTS sites is 15 (if GPROC_slots = 32). If GPROC_slots is set to 16 then at the
most 15 RSLs may exist which would support up to 7 BTS sites, and if GPROC_slots is set
to 24 then at the 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
experiences 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 an LCF MTL (a GPROC controlling
an MTL).
6-56
68P02900W21-R
GMR-01
Nov 2007
OMF GPROC required
OMF GPROC required

The BSC type 2 conguration ofoads many of the O&M functions and control of the interface
to the OMC-R from the BSP. One of the major functions ofoaded from the BSP is the central
statistics process. It is recommended to equip an OMF.
Code storage facility processor

The BSS supports a GPROC acting as the code storage facility processor (CSFP). The CSFP
allows preloading of a new software release while the BSS is operational.
If a dedicated GPROC is to exist for the CSFP, an additional GPROC is 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 congure_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 veried as successful, the operator can
return the CSFP back to the previous redundant or pooled device type through a separate
command from the OMC-R.
See Technical Description: BSS Command Reference (68P02901W23) for more details on the
congure_csfp command.
GPROC redundancy
BSP redundancy
A failure of the BSP GPROC3 causes a system outage. If the BSC is equipped with a redundant
BSP GPROC3, the system restarts under the control of the redundant BSP GPROC3s. If the
BSC is not equipped with a redundant BSP and the BSP GPROC3 was 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. This
reduces the outage time from 10 to 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 automatically
activates a spare GPROC from the GPROC pool to replace the failed GPROC.
68P02900W21-R
6-57
GMR-01
Nov 2007
GPROC planning actions
GPROC planning actions

Determine the number of GPROCs required.
Where:
NGPROC
Is:
the total number of GPROCs required.
the number of BSP GPROC3s.
the number of LCF GPROCs.
the number of CSFP GPROC3s.
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-58
68P02900W21-R
GMR-01
Nov 2007
Transcoding
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. In most congurations,
half rate is used only for part of the time, thus yielding a reduction factor of less than eight. If
transcoding takes place at the switch using an 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) 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 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.
An 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 is 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 cannot 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 Overview of remote transcoder
planning 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 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. 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. The EGDP does not
support GSM half rate. The EGDP can also terminate one Abis E1 link, thus reducing the
number of MSIs boards required (see EGDP provisioning on page 6-61). Due to the ability of the
GDP2 to function as a GDP, it can replace one or both of the GDPs in the EGDP conguration.
This is not an optimal use of the GDP2 and is most likely to occur in emergency situations (for
example, 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 user
conguration. When the MSC is capable of choosing the MSC-RXCDR trunk (CIC) based upon
the preferred codec type, a mix of transcoding equipment can be used. If this capability (called
circuit pooling) is not present, then some equipment combinations can result in non-optimal
behavior.
When circuit pooling is available in an AMR enabled system, both AMR capable (EGDP/GDP2)
and non- AMR capable (XCDR/GDP) equipment can 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 sufcient GDP2 and EGDP equipment available to
handle the expected AMR trafc. The proportion of AMR capable transcoding circuits versus
non-AMR capable transcoding circuits should be no less than the proportion of AMR capable
MSs versus non-AMR capable MSs.
68P02900W21-R
6-59
GMR-01
Nov 2007
GDP/XCDR/EGDP/GDP2 planning considerations
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). Each AMR half rate call needs 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 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 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 rst select a CIC attached to an EGDP, followed by one attached to a GDP2. For a
non-AMR capable mobile the MSC would rst select 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.
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), supports {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), supports GSM FR, enhanced Full Rate speech
(EFR), GSM half rate speech (GSM HR), uplink/downlink volume control and is capable
of terminating one E1 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 (FR and HR) speech and Phase 2 data
services, and terminates one E1 link from the MSC. GSM HR is not supported on an EGDP.
The primary GDP of an EGDP terminates the E1 interface to the MSC.
{22064} GSM HR is not supported on an EGDP.
{22064} The secondary GDP of an EGDP terminates an E1 interface to the BTS. See
EGDP provisioning on page 6-61.
The GDP2 can process 60 channels of FR, EFR, AMR (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.
6-60
68P02900W21-R
GMR-01
Nov 2007
EGDP provisioning
The proportion of AMR-capable circuits (GDP2/EGDP) to non AMR-capable circuits

(XCDR/GDP) should be sufcient to handle the expected AMR trafc.
The master MSI slot(s) should always be populated to enable communication with the
OMC-R. The master MSI slot contains 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.
An XCDR card is incompatible with a GPROC3 in the BSP slots. XCDRs must be
replaced with GDP/GDP2s.
EGDP provisioning
The secondary GDP of an EGDP can use the E1 connection to terminate an Abis link. This
reduces the need for MSIs and makes more efcient use of the available TDM timeslots. 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 congurations with and without the additional
E1 termination in use respectively.
68P02900W21-R
6-61
GMR-01
Nov 2007
EGDP provisioning
Figure 6-2 EGDP conguration with the additional E1 termination in use

TDM Bus
Primary
GDP
15
DSPs
E1 Span
to MSC
Secondary
GDP
15
DSPs
E1 S pan
from an RXCDR
to a BSC or from
a BS C to a BTS
ti-GSM-EGDP_configuration_with_the_additional_E1_termination_in_use-00128-ai-sw
6-62
68P02900W21-R
GMR-01
Nov 2007
T1 conversion
Figure 6-3 EGDP conguration without the additional E1 termination in use
Static
Pass-thru
connections
(at 64kbps)
Subrate
channels
carried onto
the TDM bus
(TRAU frames
using 16Kbps)
RXCDR: Static
or dynamic call
connections
between CICs
for GDP pair
and after
channels
(TRAU frames
using 16Kbps)
BSC: Dynamic call

connections between
CICs for a GDP pair
and Abis channels
(TRAU frames
using 16Kbps)
TDM Bus
Primary
GDP
E1 Span
to MSC
15
DSPs
MSI
E1 Span
from an RXCDR
to a BSC or from
a BSC to a BTS
Secondary
GDP
15
DSPs
ti-GSM-EGDP_configuration_without_the_additional_E1_termination_in_use-00129-ai-sw
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.
68P02900W21-R
6-63
GMR-01
Nov 2007
Planning actions for transcoding at the BSC
With KSW switching

For better utilization of the GDP/XCDRs, a mapping of ve 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 efcient 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:
the number of MSI-2s required for T1 to E1

conversion.
the number of T1 circuits required.
the number of E1 circuits required.

Planning transcoding at the BSC must always be performed as it determines the number of
E1 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:
the minimum number of E1 links required.
the number of MTL links (C7 signalling links) to the MSC.
the number of OML links (X.25 control links to the OMC-R) through the
MSC.
the number of trunks between the MSC and the BSC (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)).
6-64
68P02900W21-R
GMR-01
Nov 2007
The equipment can be mixed within the following calculation:
Where:
Is:
the minimum number of E1 links required.
XGE
the number of XCDR/GDP/EGDPs.
G2
the number of GDP2s.
Verify that the number of AMR circuits is sufcient to handle the expected AMR trafc. If
necessary, adjust the number of EGDP/GDP2s. The following formula is used to determine the
percentage of AMR capable circuits:
Count primary and secondary EGDPs as one EGDP in the equation.
Using T1 links
The minimum number of T1 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:
the minimum number of T1 links required.
the number of OML links (X.25 control links to the OMC-R) through
the MSC.
the number of trunks between the MSC and the BSC (refer Figure 6-1).
68P02900W21-R
6-65
GMR-01
Nov 2007
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 congurable 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 lled with a XCDR/GDP/EGDP
(primary or secondary) /GDP2, else the slot should be lled 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 require
to go directly to the OMC-R, they can go to another network element for concentration.
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 NBSCRXCDR element.
6-66
68P02900W21-R
GMR-01
Nov 2007
MSI/MSI-2 planning actions
With E1 links
Determine the number of MSIs required.
Without LCS:
With LCS for BSS-based LCS architecture:
The BSC-SMLC signaling link LMTL terminates only on an E1.
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.
NSC-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 trafc
(refer Chapter 8 PCU upgrade for BSS).
NGSL-E1
m
the number of links between the BSC and the PCU(s) carrying GSL
signalling links.
the number of MSI/MSI-2s used for T1 to E1 conversion.
68P02900W21-R
6-67
GMR-01
Nov 2007
Kiloport switch (KSW) and double kiloport switch (DSW2)
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, 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 extended subrate switching mode and enhanced capacity mode, the
DSW2 can further switch 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 needs that the DSW2s are not operated in the enhanced
capacity mode.
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 congurations are dependent upon timeslot usage.
For redundancy, duplicate all KSWs/DSW2s. In mixed congurations (KSWs and DSW2s),
KSWs can be redundant to DSW2s and vice-versa.
Verify that each KSW or DSW2 that is 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).
6-68
68P02900W21-R
GMR-01
Nov 2007
The devices in a BSC that need 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 = 64 timeslots.
PSI2 = tdm_ts_blocks timeslots *32 (64 ~ 320 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 rst 16 or last 16) can be allocated within a block.
However, the GDP2 is a special case, as it needs 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
are unusable. As each device needs at a minimum 16 timeslots, this does not have any
signicant effect on timeslot planning.
The number of TDM timeslots is given by:
Where:
Is:
the number of timeslots required.
the number of GPROCs.
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 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-69
GMR-01
Nov 2007
KSW/DSW2 planning actions

Calculate the minimum number of KSWs/DSW2s required per BSC:
Where:
Is:
the number of KSWs/DSW2s required.
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 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 and 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 an MSI slot is free at each
shelf, (but one GPROC per shelf can be added if one GPROC slot per shelf is free).
6-70
68P02900W21-R
GMR-01
Nov 2007
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.
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 limited 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. Refer to Kiloport switch (KSW) and
double kiloport switch (DSW2) on page 6-68 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.
An XCDR card is incompatible with a GPROC3 in the BSP slots.

XCDRs must be replaced with GDP/GDP2s.
BSU shelf planning actions

Determine the number of BSU shelves required.
68P02900W21-R
6-71
GMR-01
Nov 2007
The number of BSU shelves required is the highest value result of the following three
calculations (fractional values should be rounded up to the next integer value):
Where:
Is:
Bs
the minimum number of BSU shelves required.
the number of MSIs.
the number of XCDR/GDP/EGDP/GDP2s (see NOTE).
For EGDPs, both the primary and the secondary EGDPs must be counted.
The number of timeslots equipped to each shelf must be veried. This verication procedure
is like Planning considerations (the KSW/DSW2 timeslot validation prevents a shelf from
exceeding the timeslot limit) and is repeated here for completeness.
Where:
Is:
the number of GPROCs in the shelf.
16, 24 or 32 (depending on the value of the gproc_slots database 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.
the number of MSI/MSI-2s in the shelf (do not count MSI-2s which are
doing on-board E1 to T1 conversion).
6-72
68P02900W21-R
GMR-01
Nov 2007
If the result of the above equation exceeds 1016, the conguration of MSIs, GPROCs and GDPs
may be adjusted, or an additional shelf or shelves may be required.
The number of shelves should be larger if an attempt to reduce the number of

KSWs/DSW2s is made. The maximum number of shelves at a site = 8.
The maximum number of cabinets at a site = 8.
Horizon and M-Cell sites need only a cabinet to be equipped and not a shelf.
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 the MSIs require an additional 4 BSU
extension shelves (4 x 2 = 8 MSIs).
68P02900W21-R
6-73
GMR-01
Nov 2007
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 congurations. 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 can be used).
The following factors should be considered when planning the KSWX/DSWX complement:
KSWXs/DSWXs are not required in a single shelf conguration (that is, when expansion or
extension is not required).
For redundancy, duplicate all KSWX/DSWX boards (needs redundant KSW/DSW2). In mixed
congurations (KSWXs and DSWXs), KSWXs can be redundant to DSWXs and vice-versa.
KSWXs/DSWXs are used in three modes:

KSWX/DSWXE (Expansion) is required to interconnect the KSWs/DSW2s for sites
with multiple KSWs/DSW2s.
KSWX/DSWXR (Remote) is 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 can both be used, however they should always be used with like pairs,
for example DSWXs with DSWXs and KSWXs with KSWXs.
6-74
68P02900W21-R
GMR-01
Nov 2007
KSWX/DSWX planning actions

The number of KSWXs/DSWXs required is the sum of the KSWX/DSWXE, KSWX/DSWXL and
KSWX/DSWXR.
When SE = 0, NKXL = 0
When SE > 0, NKXL = K + SE
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.
the number of non-redundant KSWs/DSW2s.
SE
the number of extension shelves.
Table 6-13 KSWX/DSWX (non-redundant)

KSW/DSW2 (non redundant)
Extension shelves
16
11
18
13
20
10
15
22
12
17
24
68P02900W21-R
6-75
GMR-01
Nov 2007
Table 6-14
KSWX/DSWX (redundant)
KSW/DSW2 (redundant)
Extension shelves
18
32
12
22
36
10
16
26
40
14
20
30
44
18
24
34
48
6-76
68P02900W21-R
GMR-01
Nov 2007
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 rst GCLK.
GCLK planning actions

Determine the number of GCLKs required.
GCLKs = 1 + 1 redundant
68P02900W21-R
6-77
GMR-01
Nov 2007
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 rst BSU shelf, which contains the GCLK when expanding
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 allows only fourteen shelves in a single network element).
(LAN extension allows only 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 (needs a redundant GCLK).
6-78
68P02900W21-R
GMR-01
Nov 2007
CLKX planning actions

Determine the number of CLKXs required.
Where:
Is:
NCLKX
the number of CLKXs required.
ROUND UP
the number of expansion/extension shelves.
RF
redundancy factor (1 if redundancy is required

(recommended), 0 for no redundancy).
68P02900W21-R
6-79
GMR-01
Nov 2007
Local area network extender (LANX)
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.
RF
redundancy factor (1 if redundancy is required (recommended), 0 for no

redundancy).
6-80
68P02900W21-R
GMR-01
Nov 2007
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

Select the number of PIXs required.
or
68P02900W21-R
6-81
GMR-01
Nov 2007
Line interface boards (BIB, T43)
Line interface boards (BIB, T43)
Introduction
The line interfaces, balanced-line interface board (BIB) and T43 board (T43), provide impedance
matching for E1 and T1 links.
Use a BIB or PBIB to match a balanced 120-ohm (E1 2.048 Mbit/s) or balanced 110-ohm 3
V (peak pulse) line.
Use a T43 Board (T43) or PT43 board to match a single ended unbalanced 75 ohm (E1
2.048 Mbit/s) 2.37 V (peak pulse) line.
Each BIB/T43 can interface six E1 links to specic slots on one shelf.
Each PBIB/PT43 can interface four E1 links and one Ethernet link to specic slots on
one shelf.
Up to four (P)BIBs or (P)T43s per shelf can be mounted on a BSSC2 cabinet.

A maximum of 24 E1 links can be connected to a BSU shelf.
A BSSC2 cabinet with two BSU shelves can interface a maximum of 48 E1 links.
A BSSC3 cabinet can have up to seven (P)BIBs or (P)T43s per shelf

mounted, but in the BSU conguration this additional connectivity is not
needed.
6-82
68P02900W21-R
GMR-01
Nov 2007
BIB/T43 planning actions

Determine the number and type of link (E1) to be driven.
Determine the number of (P)BIBs or (P)T43s required.
68P02900W21-R
6-83
GMR-01
Nov 2007
Digital shelf power supply
Introduction
A BSSC2 or BSSC3 cabinet can be supplied to operate from a +27 V dc or -48 V/-60 V dc
power source.
In 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:
RF
Is:
the redundancy factor (1 if redundancy is required (recommended), 0 for
no redundancy).
6-84
68P02900W21-R
GMR-01
Nov 2007
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-85
GMR-01
Nov 2007
Verifying the number of BSU shelves and BSSC cabinets
Verifying the number of BSU shelves and BSSC cabinets
Verication
After planning is complete, verify that:
The number of shelves is greater than one eighth of the number of GPROC modules.
Each non-redundant KSW/DSW2 has its own shelf. Each extension shelf supports
extension of a single KSW/DSW2.
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, PSI2s and XCDR/GDP/EGDP/GDP2s 12 * number of shelves.
The number of XCDR/GDP/EGDP/GDP2s 6 * number of shelves.
For the two calculations, the EGDP consists of a primary and a secondary board.
The number of BTS sites 100
The number of BTS cells 250
RSLs 250
Carriers 384
LCFs 25
Erlangs 3000
If necessary, add extra BSU shelves. Each BSSC cabinet supports two BSU shelves.
6-86
68P02900W21-R
GMR-01
Nov 2007
Chapter
7
RXCDR planning steps and rules
This chapter provides an overview of the manual. It also provides information on various
elements of BSS, BSS planning methodology, and BSS system architecture, components and
features.
This chapter describes the planning steps and rules for the RXCDR in the following sections:
Overview of remote transcoder planning 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-10
Transcoding on page 7-11
Multiple serial interface (MSI, MSI-2) on page 7-19
Kiloport switch (KSW) and double kiloport switch (DSW2) on page 7-21
RXU shelves on page 7-24
Kiloport switch extender (KSWX) and double kiloport switch extender (DSWX) on page 7-27
Generic clock (GCLK) on page 7-30
Clock extender (CLKX) on page 7-31
LAN extender (LANX) on page 7-33
Parallel interface extender (PIX) on page 7-34
Line interfaces (BIB, T43) on page 7-35
Digital shelf power supply on page 7-37
Non Volatile Memory (NVM) board on page 7-38
Verify the number of RXU shelves and BSSC cabinets on page 7-39
68P02900W21-R
Nov 2007
7-1
GMR-01
Overview of remote transcoder planning
Overview of remote transcoder planning
Introduction
The following information is required to plan the equipage of an RXCDR:
BSC trafc requirements.
Number of trunks (including redundancy) from the MSC.
Each RXCDR can support multiple BSCs.
The sum of the MSIs/MSI-2s and the XCDR/GDP/EGDP/GDP2s for each BSC dene the
number of slots required at the RXCDR.
Each EGDP comprises two GDP cards.
The use of E1 links.
The use of balanced or unbalanced E1.

Follow Procedure 7-1 to plan an RXCDR.
Procedure 7-1 Planning an RXCDR
Plan the number of links between the XCDR and BSC sites by referring to the
section RXCDR to BSC connectivity on page 7-5.
Plan the number of E1 links between the RXCDR and MSC sites by referring
to the section RXCDR to MSC links on page 7-9.
Plan the number of GPROCs required by referring to the section Generic

processor (GPROC) on page 7-10.
Plan the number of XCDR/GDP/EGDP/GDP2s required by referring to the

section Transcoding on page 7-11.
Plan the number of MSIs required by referring to the section Multiple serial
interface (MSI, MSI-2) on page 7-19.
Continued
7-2
68P02900W21-R
GMR-01
Nov 2007
Procedure 7-1 Planning an RXCDR (Continued)

6
Plan the number of KSWs/DSW2s and timeslots required by referring to the

section Kiloport switch (KSW) and double kiloport switch (DSW2) on page
7-21.
Plan the number of RXU shelves by referring to the section RXU shelves
on page 7-24.
Plan the number of KSWXs/DSWXs required by referring to the section

on page 7-27.
Plan the number of GCLKs required by referring to the section Generic clock
(GCLK) on page 7-30.
10
Plan the number of CLKXs required by referring to the section Clock extender
(CLKX) on page 7-31.
11
Plan the number of LANXs required by referring to the section LAN extender
(LANX) on page 7-33.
12
Plan the number of PIXs required by referring to the section Parallel interface
extender (PIX) on page 7-34.
13
Plan the number of BIB or T43s required by referring to the section Line
interfaces (BIB, T43) on page 7-35.
14
Plan the power requirements by referring to the section Digital shelf power
supply on page 7-37.
15
Decide whether an NVM board is required by referring to the section Non

Volatile Memory (NVM) board on page 7-38.
16
Verify the planning process by referring to the section Verify the number of
RXU shelves and BSSC cabinets on page 7-39.
68P02900W21-R
7-3
GMR-01
Nov 2007
RXCDR system capacity
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
CICs
2,400
4,800*
4,800*
OMLs
GCLK board
KSW/DSW2
LANX2
PIX
CLKX
KSWX/DSWX
19
19
19
NVM
E1/T1s per MSI
E1/T1s per GDP
E1/T1s per
GDP2
E1/T1s per
XCDR
GPROCs per
shelf
MSI/GDP/GDP2
* Increased to 4,800 CICs when AMR (and/or {22064} GSM half rate) are both enabled.
7-4
68P02900W21-R
GMR-01
Nov 2007
RXCDR to BSC connectivity
RXCDR to BSC connectivity
Introduction
A single BSC can have multiple RXCDRs connected to it and vice-versa. This is useful for the
following reasons:
In some congurations, the RXCDR call (CIC) capacity is greater than that of a BSC.
Failure of an RXCDR, or the communication path between BSC and RXCDR results in loss
of capacity but not a complete failure of the serving BSC.
Capacity
Each BSC can connect to up to ten RXCDRs and vice-versa. The level of connectivity is
constrained by the number of XBLs (limit of 20 at each BSC and RXCDR) that can be supported.
Refer to the section Determining the number of XBLs required on page 6-44 for further details.
The level of connectivity is determined by the operator. Excess RXCDR capacity should not be
wasted. Larger BSCs should not be connected to only one RXCDR. Each BSC should connect
to four RXCDRs. System size, capacity, and cost are the major inuences on the selected
conguration.
With the introduction of advanced transcoding capabilities (that is, 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 conguration where all are interconnected and there are a limited number
of transcoder cards capable of AMR (for example, GDP2s), optimally the cards are distributed
equally among the RXCDRs.
68P02900W21-R
7-5
GMR-01
Nov 2007
RXCDR to BSC links
RXCDR to BSC links
Introduction
Refer to Figure 6-1 for the RXCDR to BSC links. The number of E1 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, 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.
In most congurations, half rate is likely to be used only a part of the time, thus
yielding a reduction factor of less than eight.
8 kbit/s backhaul can 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 is assumed to be half rate, the efciency can be increased 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 is a possibility that a call assignment may fail because of a resource shortage.
Therefore, ensure the accuracy of half rate usage estimations. The number depends on a
combination of factors, which includes (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
Nov 2007
E1 interconnect planning actions

Determine the number of E1 links required.
Where:
Is:
NBSC-RXCDR
minimum number of E1 links required.
the number of C7 signalling links to the MSC.
number of OML links (X.25 control links to the OMC-R) through the
RXCDR.
B64
number of 64 kbit/s XBL links.
number of trunks between the MSC and the BSC (refer to Figure 6-1).
PHR
percentage in decimal (for example, 0.35) of expected half rate usage

(meeting the criteria stated previously).
B16
PHR is zero if Enhanced Auto Connect mode is not in use.
Each E1 link carries up to 120 (240 at half rate) trunks with a signaling link or
124 (248 at half rate) trunks without a signaling link.
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
GMR-01
Nov 2007
T1 interconnect planning actions

Determine the number of T1 links required.
Where:
Is:
NBSC-RXCDR
minimum number of T1 links required.
number of C7 signalling links to the MSC.
number of OML links (X.25 control links to the OMC-R)

through the RXCDR.
B64
T
B16

number of trunks between the MSC and the BSC (refer to
Figure 6-1).
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
Nov 2007
RXCDR to MSC links
RXCDR to MSC links
Introduction
The number of E1 links between the RXCDR and the MSC is the number required to support
the A-Interface from the RXCDR to the MSC.

Determine the number of E1 links required. The minimum number of E1 links required for
the A-Interface is the greater of the two following calculations (fractional values should be
rounded-up to the next integer value):
Where:
NRXCDR-MSC
Is:
number of OML links (X.25 control links to the OMC-R) through the
MSC.

Determine the number of T1 links required.
Where:
NRXCDR-MSC
Is:
number of MTL links (C7 signalling links) to the MSC.
number of OML links (X.25 control links to the OMC-R) through

the MSC.
68P02900W21-R
7-9
GMR-01
Nov 2007
GPROC nomenclature
In this manual, the different versions of the Generic Processor are as follows:
GPROC2: Refers to GPROC2
GPROC3: Refers to GPROC3
GPROC: Refers 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.
The following factors should be considered when planning the GPROC complement at the
RXCDR:
Each shelf needs at least one GPROC board, along with one for redundancy.
A maximum of two GPROCs per shelf are supported:

One BSP GPROC3.
One GPROC that can be congured 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, a GPROC2 can still be used in this position.
7-10
68P02900W21-R
GMR-01
Nov 2007
Transcoding
Transcoding
Introduction
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.
In most congurations, half rate is 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) 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 conguration of the GDP board, which is 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 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.
This results in an overall reduction in transcoding shelf capacity, which is 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 can also terminate one Ater E1 link, thus reducing the
number of MSI boards required (Refer to EGDP provisioning on page 7-14). The GDP2 can
function as GDP and hence it can replace one or both the GDPs in the EGDP conguration. This
is not an optimal use of the GDP2 and occurs in emergency situations (for example, board
replacement). As a result, it is not considered in the planning procedures.
68P02900W21-R
7-11
GMR-01
Nov 2007
Introduction
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 factors such as MS capabilities and operator
conguration. When the MSC is capable of selecting the MSC-RXCDR trunk (CIC) based upon
the preferred codec type, a mix of transcoding equipment can be used. If this circuit pooling
capability is not present, some equipment combinations can result in non-optimal behavior.
When circuit pooling is available in an AMR enabled system, both AMR-capable (EGDP/GDP2)
and non -AMR-capable (XCDR/GDP) equipment are 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 sufcient GDP2 and EGDP equipment available to handle
the expected AMR trafc. The proportion of AMR-capable transcoding circuits versus nonAMR-capable transcoding circuits should not be less than the proportion of AMR-capable MSs
versus 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).
Each AMR half rate call needs 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 mobiles 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 need GSM half rate. It becomes necessary to update all transcoding to support
GSM HR in order to guarantee that GSM half rate can be used when required. Without this
upgrade, calls on non-GSM HR capable CICs 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 selecting 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 rst select a CIC attached to an EGDP, followed by one attached to a GDP2. For a
non-AMR capable mobile the MSC would rst select 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.
Each trunk needs a quarter (1/4th) (or an eighth (1/8th) in some cases for AMR half rate as
described ) 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 shows sub-multiplexing and speech transcoding at the RXCDR.
7-12
68P02900W21-R
GMR-01
Nov 2007
XCDR/GDP/EGDP/GDP2 planning considerations
Figure 7-1 Sub-multiplexing and speech transcoding at the RXCDR

BSC
RXCDR
X
C
D
R/
G
D
P/
G
D
P
2
M
S
C
64 kbit/s
A-LAW
TRUNKS
K
S
W
/
D
S
W
2
M
S
I
/
M
S
I
2
M
S
I
/
M
S
I
2
Horizon II macro BTS
K
S
W
/
D
S
W
2
M
S
I
/
M
S
I
2
ONE RF
CARRIER
C
T
U
2
HIISC
4 TO 8 TRUNKS PER
64 kbit/s CIRCUIT
THE XCDR/GDP/GDP2 TRANSCODES 64 kbit/s

A-LAW PCM TO/ FROM 13 kbit/s MAPPED
ONTO 16 kbit/s OR UP TO 8 kbit/s MAPPED
ONTO 8 kbit/s, AND SUBMU LTIPLEXES 4 to 8
TRUNKS TO/FROM 1 x 64 kbit/s CIRCUI T.
N
I
U
64 kbit/s
4 OR 8 TCHs
THE KSW (DSW2)

SUBR ATE SWITCHES
16 kbit/s (8 kbit/s)
TIMESLOTS.
THE CTU2 ENCODES/DECODES
13 (UP TO 8 FOR HALF R ATE) kbit/s
TO/FROM 22.8 (11.4) kbit/s FOR 8 (16)
TIMESLOTS, AND SUBMU LTIPLEXES 4
(13 kbit/s MAPPED ON 16 kbit/s) OR 8
(UP TO 8 kbit/s MAPPED ON 8 kbit/s
FOR HALF R ATE) TIMES LOTS ONTO 1 x
64 kbit/s CIRCUI T, OR THE OTHER W AY
AROUND.
8 x 22.8 kbit/s TIMES LOTS OR

16 x 11.4 kbit/s TIMES LOTS
ti-GSM-Sub_multiplexing_and_speech_transcoding_at_the_RXCDR-00130-ai-sw
In Figure 7-1, the CTU2 operates 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:
An XCDR can process 30 voice channels (E1), 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), 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.
68P02900W21-R
7-13
GMR-01
Nov 2007
EGDP provisioning
{22064} The secondary GDP of an EGDP may terminate an E1 interface to the BSC.
Refer to EGDP provisioning on page 7-14.
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 is used to terminate 2 E1s (that is, 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 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 sufcient to handle the expected AMR trafc.
The master MSI slot(s) should always be populated to enable communication with the
OMC-R. The master MSI slot can 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). EGDPs and GDP2s do not support T1s.
Slot 24 (XCDR 0) in the RXU shelf 0 (master) is lost if an optional NVM board is required.
An XCDR card is incompatible with a GPROC3 in the BSP slots. XCDRs must
be replaced with GDP/GDP2s.
EGDP provisioning
The secondary GDP of an EGDP uses the E1 connection to terminate an Ater link. This reduces
the requirement for MSIs and makes more efcient use of the available TDM timeslots.
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 congurations with and without the additional
E1 termination in use, respectively.
7-14
68P02900W21-R
GMR-01
Nov 2007
EGDP provisioning
Figure 7-2 EGDP conguration with the additional E1 termination in use

TDM Bus
Primary
GDP
15
DSPs
E1 Spam
to MSC
15
DSPs
S e condary
GDP
E1 Span
from an RXCDR
to a BSC or from
a BSC to a BTS
ti-GSM-EGDP_configuration_with_the_additional_E1_termination_in_use-00131-ai-sw
68P02900W21-R
7-15
GMR-01
Nov 2007
T1 conversion
Figure 7-3 EGDP conguration without the additional E1 termination in use
Static
Pass-thru
connections
(at 64kbps)
Subrate
channels
carried onto
the TDM bus
(TRAU frames
using 16Kbps)
RXCDR: Static
or dynamic call
connections
between CICs
for GDP pair
and after
channels
(TRAU frames
using 16Kbps)
BSC: Dynamic call

connections between
CICs for a GDP pair
and Abis channels
(TRAU frames
using 16Kbps)
TDM Bus
Primary
GDP
E1 Span
to MSC
15
DSPs
MSI
E1 Span
from an RXCDR
to a BSC or from
a BSC to a BTS
Secondary
GDP
15
DSPs
ti-GSM-EGDP_configuration_without_the_additional_E1_termination_in_use-00132-ai-sw
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.
7-16
68P02900W21-R
GMR-01
Nov 2007
Planning actions for transcoding at the RXCDR
With KSW switching

For better utilization of the GDP/XCDRs a mapping of ve 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 efcient 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:
number of MSI-2s required for T1 to E1 conversion.
number of T1 circuits required.
number of E1 circuits required.

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)].
Plan the equipment according to the following formula:
Where:
Is:
XGE
number of XCDRs, GDPs and EGDPs.
G2
number of GDP2s.
NRXCDR-MSC
minimum number of E1 links required (as N is calculated in

RXCDR to MSC links on page 7-9).
Verify that the number of AMR circuits is sufcient to handle the expected AMR trafc. If
necessary, adjust the number of EGDP/GDP2s.
Use the following formula to determine the percentage of AMR-capable circuits:
68P02900W21-R
7-17
GMR-01
Nov 2007
In the equation, count the primary and secondary EGDPs as one EGDP.
Using T1 links
Each GDP card can terminate one T1 link. Refer to T1 conversion (described previously)
for XCDR.
7-18
68P02900W21-R
GMR-01
Nov 2007
Introduction
A multiple serial interface provides the interface for the links between an 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.
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 congurable 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 supports 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 needs 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 are required to concentrate X.25 links from other network
entities.
Each BSC uses one to four 64 kbit/s or 16 kbit/s channels for XBL fault management
communications. Refer to Service Manual: BSC/RXCDR (68P02901W38) for further
details.
68P02900W21-R
7-19
GMR-01
Nov 2007
MSI planning actions
The master MSI slots should always be populated to enable communication with the
OMC-R.
If the OML links go directly to the MSC, the master slot should be lled with a
XCDR/GDP/EGDP (primary or secondary)/GDP2, else the slot should be lled 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 require to go directly to the OMC-R, they can go to another network
element for concentration.
MSI planning actions

With E1 links
Use the following equation to determine the number of MSIs required:
Where:
NMSI
NBSC-RXCDR
Is:
number of MSIs required.
number of E1 links required (as N calculated in RXCDR to
BSC links on page 7-6).
With T1 links
If MSI-2s are used, T1 to E1 conversion is not required. Therefore, the number of MSI-2s
required is as follows:
Where:
NMSI
NBSC-RXCDR
Is:
If MSIs are used, conversion becomes necessary. Therefore the number of MSIs required is:
Where:
NMSI
NBSC-RXCDR
m
Is:
number of MSI-2s used for T1 to E1 conversion.
7-20
68P02900W21-R
GMR-01
Nov 2007
Kiloport switch (KSW) and double kiloport switch (DSW2)
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.
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 which is not in enhanced capacity mode, has a capacity of 1,024 x
64 kbit/s ports or 4,096 x 16 kbit/s ports, which can be expanded by adding up to three
additional KSW/DSW2s, giving a total switching capacity of 4,096 x 64 kbit/s ports or
16,384 x 16 kbit/s ports.
When operating in enhanced capacity mode, the DSW2 has a capacity of 2048 x 64 kbit/s
ports or 8192 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 8,192 x 8 kbit/s ports which can be expanded by adding up to
three additional DSW2s, giving a total switching capacity of 32,768 x 8 kbits/s ports.
When operating in extended subrate switching mode and enhanced capacity mode, the
DSW2 can further switch 16,384 x 8 kbit/s ports which can be expanded by adding up to
three additional DSW2s, giving a total switching capacity of 65,536 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.
For redundancy, duplicate all KSWs/DSW2s. In mixed congurations (KSWs and DSW2s),
KSWs can be redundant to DSW2s and vice-versa.
68P02900W21-R
7-21
GMR-01
Nov 2007
Verify that each KSW or DSW2 not in enhanced capacity mode uses no more than 1,016
ports, or that each DSW2 in enhanced capacity mode uses no more than 2,040 ports (8
ports are used internally). The devices in an RXCDR that need 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:
number of timeslots required.
number of GPROCs.
16 or 32 (depending on the value of the

gproc_slots database parameter).
RGDPXCDR
number of GDPs/XCDRs.
REGDP
number of EGDPs.
REDP2
number of GDP2s.
number of MSI/MSI-2s (do not count

MSI-2s which are doing on-board E1 to
T1 conversion, when determining TDM
bandwidth).

Use the following formula to determine the number of KSWs or DSW2s required when enhanced
capacity mode is not enabled:
Use this formula when enhanced capacity mode is enabled:
7-22
68P02900W21-R
GMR-01
Nov 2007
Where:
Is:
number of KSWs/DSW2s required.
number of GPROCs.

gproc_slots database parameter).
RGDPXCDR
number of GDPs/XCDRs.
REGDP
number of EGDPs.
REDP2
number of GDP2s.
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 along with the boards of any extension
shelf connected to its shelf by its TDM highway of 1,016 available timeslots (or 2,040 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 an 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).
68P02900W21-R
7-23
GMR-01
Nov 2007
RXU shelves
RXU shelves
Introduction
The number of RXU shelves is a function of the number of MSI/MSI2s and
XCDR/GDP/EGDP/GDP2s required.
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 ve MSI/MSI-2s with 14 GDP/XCDRs, the KSW can serve only one shelf,
and two KSWs are required.
The existing RXU shelf has connectivity for up to ve MSI/MSI-2s (2 x E1 connections).

The remaining 14 slots have one E1 connection. All slots are used for XCDR/GDP/EGDP
(primary or secondary) /GDP2s.
The RXU3 shelf has connectivity for two E1s per slot. All slots are used for
XCDR/GDP/EGDP/GDP2s and MSI/MSI-2s.
The GDP2 can be used to terminate 2 x E1s, (that is, 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.
7-24
68P02900W21-R
GMR-01
Nov 2007
RXU shelf planning actions
An XCDR card is incompatible with a GPROC3 in the BSP slots. XCDRs must
be replaced with GDP/GDP2s.

Use the appropriate formula (fractional values should be rounded up to the next integer) to
determine the number of RXU shelves required:
For the current generation RXU shelf:
For the new generation RXU3 shelf:
Where:
Is:
RX
minimum number of RXU shelves required.
RX3
minimum number of RXU3 shelves required.
number of MSI/MSI-2s.
number of XCDR/GDP/EGDP/GDP2s. Refer Note.
NNVM
number of optional NVM boards (0 or 1).
For EGDPs, both the primary and the secondary must be counted.
The number of timeslots equipped to each shelf must be veried using the appropriate equation
given.
68P02900W21-R
7-25
GMR-01
Nov 2007
Enhanced capacity mode is not enabled

The verication procedure is like the KSW/DSW2 planning consideration.
Where:
Is:
number of GPROCs in the shelf.

gproc_slot database parameter).
RGDPXCDR
number of GDP/XCDRs in the shelf.
REGDP
number of EGDPs in the shelf.
RGDP2
number of GDP2s in the shelf.
number of MSI/MSI-2s in the shelf. (Do not

count MSI-2s which are doing on-board E1
to T1 conversion).
Enhanced capacity mode is enabled (non-extension shelf)
Enhanced capacity mode is enabled (extension shelf)
If the result of using the appropriate equation exceeds the value quoted, the conguration of
MSIs, GPROCs and GDPs can be adjusted, or an additional shelf or shelves are required.
7-26
68P02900W21-R
GMR-01
Nov 2007

extender (KSWX) and double kiloport switch extender (DSWX)
Kiloport switch
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 congurations. 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 (2,048 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 conguration (that is, when expansion or
extension is not required).
For redundancy, duplicate all KSWX/DSWX boards (requires redundant KSW/DSW2).
In mixed congurations (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 can both be used. However, KSWXs and DSWXs should always be used
with like pairs, that is, DSWXs with DSWXs and KSWXs with KSWXs.
Operation in enhanced capacity mode requires the use of all DSWXs (and DSW2s).
68P02900W21-R
7-27
GMR-01
Nov 2007
Variable length bre 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.

The number of KSWXs/DSWXs required is the sum of the KSWX/DSWXE, KSWX/DSWXL and
KSWX/DSWXR.
Where:
When SE = 0, NKXL = 0
When SE > 0, NKXL = K + SE

Is:
NKX
number of KSWXs/DSWXs required.
NKXE
number of KSWX/DSWXE.
NKXR
number of KSWX/DSWXR.
NKXL
number of KSWX/DSWXL.
number of non-redundant KSWs/DSW2s.
SE
number of extension shelves.
7-28
68P02900W21-R
GMR-01
Nov 2007
For example:
Table 7-2 KSWX/DSWX (non-redundant)

Extension shelves
KSW/DSW2 (non redundant)

1
16
11
18
13
20
10
15
22
12
17
24
Table 7-3 KSWX/DSWX (redundant)

Extension shelves
KSW/DSW2 (redundant)
1
18
32
12
22
36
10
16
26
40
14
20
30
44
18
24
34
48
68P02900W21-R
7-29
GMR-01
Nov 2007
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

Use the following formula to determine the number of GCLKs required:
GCLKs = 1 + 1 redundant
7-30
68P02900W21-R
GMR-01
Nov 2007
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 rst RXU shelf, which contains the GCLK, when expansion
beyond the shelf occurs.
Each CLKX can supply the GCLK signals to six 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 (needs a redundant GCLK).
68P02900W21-R
7-31
GMR-01
Nov 2007

Use the following formula to determine the number of CLKXs required:
Where:
NCLKX
ROUNDUP
Is:
number of CLKXs required.
number of shelves.
RF
redundancy factor (1 if redundancy is required

(recommended), 0 for no redundancy).
7-32
68P02900W21-R
GMR-01
Nov 2007
LAN extender (LANX)
LAN extender (LANX)
Introduction
The LANX provides a LAN interconnection for communications among all GPROCs at a site.
The following factors should be considered when planning the LANX complement:
A 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

Use the following formula to determine the number of LANXs required:
Where:
Is:
NLANX
number of LANXs required.
NRXU
number of RXU shelves.
RF
redundancy factor (1 is the recommended value if

redundancy is required, 0 for no redundancy).
68P02900W21-R
7-33
GMR-01
Nov 2007
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 as follows:
PIX ? 2 * number of RXUs
or
PIX ? 8
7-34
68P02900W21-R
GMR-01
Nov 2007
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 specic 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 are four unused
E1/T1 links on two of the BIB/T43s.
GDP2s must be used to utilize fully two E1s per slot.
68P02900W21-R
7-35
GMR-01
Nov 2007

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.
Minimum number of BIBs or T43s required per shelf = (Number of E1/T1 links)/6.
Sum up across all shelves for the total.
7-36
68P02900W21-R
GMR-01
Nov 2007
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 while 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

Use the following formula to determine the number of PSMs required:
Where:
RF
Is:
the Redundancy factor (recommended value is 1 if
redundancy is required, 0 for no redundancy).
68P02900W21-R
7-37
GMR-01
Nov 2007
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.
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-38
68P02900W21-R
GMR-01
Nov 2007
Verify the number of RXU shelves and BSSC cabinets
Verify the number of RXU shelves and BSSC cabinets
Verication
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
Nov 2007
7-39
GMR-01
Verication
7-40
68P02900W21-R
GMR-01
Nov 2007
Chapter
8
PCU upgrade for 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
PCU hardware layout on page 8-16
PCU shelf (cPCI) on page 8-18
MPROC board on page 8-19
DPROC board on page 8-20
PMC module on page 8-24
Transition module on page 8-25
PCU equipment redundancy and provisioning goals on page 8-26
E1 link provisioning for GPRS and EGPRS on page 8-37
QoS capacity on page 8-39
PCU-SGSN: trafc and signal planning on page 8-46
BSS-PCU hardware planning example for GPRS on page 8-52
BSS-PCU hardware planning example for EGPRS on page 8-60
68P02900W21-R
Nov 2007
8-1
GMR-01
BSS planning for GPRS/EGPRS
BSS planning for GPRS/EGPRS
Introduction to BSS planning for GPRS/EGPRS

The BSS planning process for GPRS/EGPRS involves 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 trafc 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 trafc estimation and key concepts on page 3-141 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. Refer to BSS-PCU hardware planning example for GPRS on page 8-52 and
BSS-PCU hardware planning example for EGPRS on page 8-60. Its purpose is to unite the
information presented in the entire document from a planning perspective.
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.
8-2
68P02900W21-R
GMR-01
Nov 2007
PCU to SGSN interface planning
Figure 8-1 PCU to SGSN interface planning
ti-GSM-PCU_to_SGSN_interface_planning-00133-ai-sw
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 congured for E1 loop timing recovery on all the PCU E1 interfaces. The PCU
is connected directly to the BSC E1 interfaces and the BSC is congured 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 has a master clock source (such as DACs) should be used. The
Motorola BSC and RXCDR equipment can be used in place of DACs for this purpose.
When an RXCDR or BSC is used as an E1 switching element, as shown in option A and option
B, respectively, additional equipment provisioning of these network elements are required to
support the PCU E1 interfaces. This is 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.
Each PCU connected to a BSC must be connected to the same SGSN in terms of
the Gb interface.
68P02900W21-R
8-3
GMR-01
Nov 2007
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 species how the BSC congures and shares the terrestrial
backing between the GPRS data trafc and the Circuit-Switched (CS) trafc. The terrestrial
backing between the BTS and BSC should have enough capacity to carry the radio timeslots
assigned to both GPRS and circuit switched trafc. If there is not enough capacity, because
there are not enough physical channels, the BSC allocates the backing to CS rst. The
remaining capacity is assigned to GPRS (reserved GPRS timeslots rst, 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
trafc demands need more terrestrial capacity. Terrestrial resources available in the switchable
pool are available for GPRS trafc use.
The BSC reassigns GPRS switchable or reserved backing to CS if backing is required for
emergency circuit-switched calls. In this case, the switchable and reserved backing is
reassigned so that the remaining GPRS radio timeslots within a carrier are contiguous.
The CS3/CS4 feature and EGPRS feature that need 32 kbit/s and 64 kbit/s bandwidth {23769}
(variable bandwidth in terms of a congurable 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 trafc and signaling handling
network capability for GSM voice and circuit data trafc. Additional loading on the BSS
elements due to the GPRS/EGPRS trafc needs additional BSS equipment and interface circuits.
Three classes of mobile devices permit non-simultaneous attachment to the circuit-switched and
packet data channels. Hence, the BSS need not be provisioned to simultaneously handle the call
processing and signaling for both circuit-switched trafc 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 trafc 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.
8-4
68P02900W21-R
GMR-01
Nov 2007
Concentric cells
GPRS/EGPRS timeslots are available in the outer zone carriers.
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 reconguration

No additional BSS or GPRS/EGPRS network planning is required.
The Cell Resource Manager (CRM) dynamic reconguration feature can use the switchable
GPRS/EGPRS timeslots, but it cannot recongure the reserved GPRS/EGPRS timeslots under
any circumstance.
Directed retry
The BSC uses directed retry to relieve cell congestion by redistributing trafc across cells. For
the GPRS/EGPRS trafc part of the BSS, the BSC treats switchable GPRS/EGPRS timeslots
like idle TCHs.
Emergency call pre-emption

The BSS can congure any GPRS and/or EGPRS timeslot to carry out emergency calls. If an
emergency call has to be made within a cell with a GPRS or EGPRS carrier, the BSS selects the
air timeslot in the following order:
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 select the air timeslot from the
following list in the following order:
Idle TCH
Switchable GPRS timeslot (from lowest to highest)
Switchable EGPRS timeslot (from lowest to highest)
In-use TCH
Reserved GPRS timeslot (from lowest to highest)
Reserved EGPRS timeslot (from lowest to highest)
PBCCH/PCCCH timeslot
68P02900W21-R
8-5
GMR-01
Nov 2007
Emergency TCH channels will never be pre-empted.
All available GPRS timeslots are assigned to be switchable before any EGPRS timeslot.

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
kilometers up to a maximum range of 121 kilometers (depending on limiting factors). This range
extension is not supported for GPRS or EGPRS carriers.
Frequency hopping and redenition

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 timeslots can have a
different timeslot activity factor to voice, and hence cause the cell C/I performance to change
from a GSM-only system.
The frequency redenition 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
No additional BSS, GPRS, or EGPRS network planning is required.
The BSC treats switchable GPRS/EGPRS timeslots like idle TCHs in the case of multiband
handovers.
8-6
68P02900W21-R
GMR-01
Nov 2007
Over the air ow control for circuit-switched mobiles

The BSC treats switchable GPRS/EGPRS timeslots like idle TCHs in the case of over the air ow
control for the circuit-switched mobiles feature.

The BSC uses 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 can also convert TCH barred switchable GPRS/EGPRS timeslots, 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 can be recongured as SDCCHs. However, GPRS/EGPRS reserved
timeslots cannot be recongured as SDCCHs.
SD placement prioritization
A GPRS/EGPRS carrier cannot be congured such that the sum of the number of allowed
SDCCHs 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.
VersaTRAU backhaul
VersaTRAU backhaul feature allows the operator to congure the backhaul required for an
EGPRS capable RTF using the rtf_ds0_count parameter associated with the RTF. The backhaul
per RTF has to be planned 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 congured
PDTCHs per carrier. The recommendations are based on the achievement of average coding
scheme of at least MCS6.
68P02900W21-R
8-7
GMR-01
Nov 2007
Table 8-1 VersaTRAU backhaul recommendations for a given number of PDTCHs

Recommended aggressive VersaTRAU
backhaul (average 28 kbit/s)
Number of
PDTCH
Recommended non-aggressive
VersaTRAU backhaul
Number of
DS0
Average kbit/s (effective MCS)
Number of
DS0
Average kbit/s
(effective MCS)
28 kbit/s (MCS5)
34 kbit/s (MCS6)
24 kbit/s (MCS5)
31 kbit/s (MCS6)
28 kbit/s (MCS5)
37 kbit/s (MCS6)
33 kbit/s (MCS6)
33 kbit/s (MCS6)
28 kbit/s (MCS5)
41 kbit/s (MCS6)
37 kbit/s (MCS6)
37 kbit/s (MCS6)
28 kbit/s (MCS5)
28 kbit/s (MCS5)
59 kbit/s (MCS9)
59 kbit/s (MCS9)
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 rst 2 rows show the different initial congurations ranging from 1 PDTCH per carrier to
8 PDTCHs per carrier (non- BCCH carrier). The next row shows the number of DS0s forming
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. In this table, the recommended backhaul for the Versachannel is conservative, and
generally results in 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 benets of the statistical multiplexing).
Table 8-3 is more aggressive and shows the recommended number of DS0s forming the
VersaTRAU, which generally results in MCS5.
Table 8-2
Expected throughput/TS and coding schemes (conservative)
# of PD/carrier
# DS0 for
VersaTRAU
including voice
VersaTRAU %
saving versus
Today
38
38
38
50
50
50
63
63
#TRAU
34
31
37
33
41
37
28
59
# PDs left
Average
datarate/TS
CS used
MCS6 MCS6 MCS6
MCS6
MCS6 MCS6 MCS9
MCS9
Continued
8-8
68P02900W21-R
GMR-01
Nov 2007
Table 8-2
Expected throughput/TS and coding schemes (conservative) (Continued)
#TRAU
# PDs left
Average
datarate/TS
31
37
44
41
37
59
59
MCS6 MCS6 MCS6
CS used
MCS6
MCS6 MCS9 MCS9
#TRAU
# PDs left
37
44
59
37
59
59
Average
datarate/TS
MCS6 MCS6 MCS9
CS used
#TRAU
MCS6
MCS9 MCS9
# PDs left
Average
datarate/TS
44
59
59
59
59
MCS9
MCS9
MCS6 MCS9 MCS9
CS used
#TRAU
# PDs left
59
59
59
59
Average
datarate/TS
MCS9 MCS9 MCS9
CS used
#TRAU
# PDs left
Average
datarate/TS
59
59
59
MCS9 MCS9 MCS9
CS used
Table 8-3
MCS9
Expected throughput/TS and coding schemes (aggressive)
# of PD/carrier
# DS0 for
VersaTRAU
including voice
VersaTRAU %
saving versus.
Today
50
50
50
50
50
63
63
63
# PDs left
Average
datarate/TS
28
24
28
33
28
37
28
59
CS used
MCS5
MCS5
MCS5
MCS6
MCS5
MCS9
#TRAU
MCS5 MCS6
Continued
68P02900W21-R
8-9
GMR-01
Nov 2007
Table 8-3 Expected throughput/TS and coding schemes (aggressive) (Continued)

#TRAU
# PDs left
Average
datarate/TS
24
28
33
41
37
59
59
CS used
MCS5
MCS5
MCS6
MCS6
# PDs left
Average
datarate/TS
28
33
41
37
59
59
CS used
MCS6
MCS6
MCS6
MCS6
# PDs left
Average
datarate/TS
33
41
37
59
59
CS used
MCS6
MCS6
MCS6
MCS9
MCS9
# PDs left
Average
datarate/TS
44
39
59
59
CS used
MCS6
MCS6
MCS9
MCS9
# PDs left
Average
datarate/TS
37
59
59
CS used
MCS7
MCS9
MCS9
#TRAU
#TRAU
#TRAU
#TRAU
8-10
MCS6 MCS9
MCS9
MCS9 MCS9
68P02900W21-R
GMR-01
Nov 2007
BSS upgrade to support GPRS/EGPRS
BSS upgrade to support GPRS/EGPRS
BSS upgrade provisioning rules

Table 8-4 identies the BSS network elements that require upgrading to support GPRS/EGPRS.
Refer to the relevant planning information for the chassis-level planning rules covering the
BSC, BTS and RXCDR.
Table 8-4 BSS upgrade in support of GPRS/EGPRS

Equipment
BSC
Additional element
Chassis (optional)
Software upgrade
BSS upgrade
Add KSWs/DSW2s, LCF GPROC2s
{25779} /GPROC3s, BSP GPROC3,
MSIs per BSC as needed in support
of the Gb (where Gb is connected
through the BSC), RSL, BSC-BTS
trafc carrying E1 links.
BTS (Horizon
II macro,
Horizonmacro,
M-Cell6, M-Cell2)
CTU2 Transceiver, with

EGPRS Firmware upgrade
(M-Cell6 and M-Cell2 need
the CTU Adapter with the
CTU2s)
EGPRS enabled CTU2 radios are

required.
CTU2D radios on Horizon II
macro also support EGPRS.
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
includes a patch panel (75 or 120 )
and two cable management brackets.
OMC-R
Software upgrade for

EGPRS support
One per 64 BSS network elements,

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
GMR-01
Nov 2007
Maximum BSS conguration

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.
Table 8-5 Recommended maximum BSS network 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, GPRS and EGPRS)
BSS (BTS)
TBF per cell UL
120
BSS (BTS)
TBF per cell DL
120
BSS (BTS)
Users per timeslot in each

direction
BSS (BTS)
Timeslots per active user

DL
BSS (BTS)
Timeslots per active user

UL
BSS (BTS)
GPRS/EGPRS timeslots
per cell (total of switchable
and reserved)
BSS (BSC)
PCUs per BSC
BSS (PCU)
Air interface timeslots

processed at any instance
in time (with redundancy)
240, refer to Figure 8-3
BSS (PCU)
Total air interface

timeslots (with
redundancy) **
BSS (PCU)

in time
BSS (PCU)
Total air interface

timeslots **
BSS (PCU)
Max. TBF per PCU - UL
2700
BSS (PCU)
Max. TBF per PCU - DL
2700
30
3 ***
BSS (3xPCU)

in time (with redundancy)
720***, refer to Figure 8-3
BSS (3xPCU)
Total air interface

timeslots (with
redundancy)**
2880*** (1080****), refer

to Figure 8-3
Continued
8-12
68P02900W21-R
GMR-01
Nov 2007
Table 8-5 Recommended maximum BSS network parameter values (part A)

(Continued)
Network Element
Network Parameter
Maximum Value
BSS (3xPCU)

in time
810***, refer to Figure 8-4
BSS (3xPCU)
Total air interface

timeslots**
3240*** (1080****), refer

to Figure 8-4
BSS (3xPCU)
Max. TBF - UL
8100
BSS (3xPCU)
Max. TBF - DL
8100
* Maximum if all carriers at a BTS are EGPRS enabled.
** All 1080 timeslots under a PCU can support trafc, unlike in previous
releases where only 270 timeslots could be used to originate trafc 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 conguration.
*** Up to three PCUs (3xPCU) can be managed by the same BSC. The impact
on air interface timeslots is cumulative (that is, two PCUs in a non-redundant
conguration have 2160 total timeslots and three PCUs 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 conguration, 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.
Table 8-6
Recommended maximum BSS parameter values (part B)
Network Element
Network Parameter
Maximum Value
PCU (PRP DPROC)

processing per PRP
30 at any instance in time; 120

total timeslots.
PCU (PICP DPROC)
PCU-SGSN (Gb) interface

(GBL) 1
Gb E1 to carry frame relay

channellized or non-channellized
GPRS trafc deployed over the
BSC to PCU interface. The Gb E1
carries both data and signalling
trafc between the PCU and
SGSN. The utilization of the Gb
should be planned to not exceed
70%.
Continued
68P02900W21-R
8-13
GMR-01
Nov 2007
Table 8-6
Recommended maximum BSS parameter values (part B) (Continued)
Network Element
Network Parameter
Maximum Value
PCU
Maximum PSP MPROCs
2 (for redundancy)
1 (no redundancy)
PCU
Maximum PICP DPROCs
PCU
Maximum PRP DPROCs
PCU
Number of cells supported
250
PCU
Number of BTS sites

supported
100
GSL E1 links
Maximum physical E1s

between BSC & PCU
(one primary E1 and one
redundant)
LAPD-type GDS
(GSL) links
Maximum per E1 link

(corresponds to a quantity
of thirty 64 kbit/s LAPD
channels)
TRAU-type GDS
links (E1s)
Maximum per PCU
30
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.
Table 8-7
Recommended maximum BSS network parameter (part C)
Network Element
Network Parameter
Maximum Value
GBL links (E1s)
Maximum per PCU
4
12**
20**
Gb PVCs
Maximum on one bearer

Link
318
T43 boards
Maximum per PCU
4
8***
Cable harnesses
To connect 4 x T43 sites
Gb frame relay frame

octet size
Maximum
1,600 bytes
8-14
68P02900W21-R
GMR-01
Nov 2007
E1 cable requirements for a fully congured PCU
* Maximum number when EGPRS supported carriers are being employed.
** Maximum number in a 3xPCU conguration 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, and PRPs are used.
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. This fragmentation of the cells across PRP
boards 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 or max_EGPRS TSg, all
GPRS/EGPRS timeslots of all cells are assigned to a PRP.
max GPRS/max EGPRS TSg = (nPRP * 120) - (max_GPRS/max_EGPRS TS_cell).
Where:
Is:
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.
E1 cable requirements for a fully congured 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 E1 s for a fully congured PCU, 4 x
T43 boards require to be populated.
With EGPRS carriers, a second interconnect panel can be added if the number of E1s is greater
than 24.
The number of T43 boards in the second interconnect panel is dependent 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 has to be caged to hold an extra 6 E1 RJ45 to RJ45 cables.
68P02900W21-R
8-15
GMR-01
Nov 2007
PCU hardware layout
PCU hardware layout
There is one PCU per BSS. Figure 8-2 shows the PCU shelf layout.
Figure 8-2 PCU shelf layout

DEFAULT LAP D
LINK TO BS C
DEFAULT LAP D
LINKS TO BSC
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
M
P
R
O
C
M
P
R
O
C
10 11 12 13 14 15 16
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
H
S
C
A
M
P
R
O
C
B
T
M
D
P
R
O
C
DEFAULT LAP D
LINKS TO BS C
DEFAULT LAP D
LINK TO BS C
16 15 14 13 12 11 10 9
D
P
R
O
C
H
S
C
B
M
P
R
O
C
A
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
4 3
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
D
P
R
O
C
T
M
ti-GSM-PCU_shelf_layout-00135-ai-sw
8-16
68P02900W21-R
GMR-01
Nov 2007
PCU hardware layout
Any of the two available default LAPD link slots is used.
68P02900W21-R
8-17
GMR-01
Nov 2007
PCU shelf (cPCI)
PCU shelf (cPCI)
Introduction
The PCU cabinet can hold up to three PCU (cPCI) shelves; only two PCU shelves can be tted
when EGPRS is used. Each PCU is connected to only one BSC.
Each cabinet is pre-wired with a panel in the rear of the cabinet for the desired E1 termination
type, balanced 120 ohm, or unbalanced 75 ohm terminations with 1500 volt lightning protection
per E1.
The following factors should be considered when planning the cPCI complement:
The maximum number of timeslots that can be processed at any instance in time per PCU
is 960 in the fully redundant conguration (refer 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 conguration (refer Table 8-5 to Table 8-7).
Three fan/power supply units per cPCI shelf provide N+1 hot-swap redundancy. A
minimum of two power supply units are required, with a fan-only unit required in the third
location if a power supply unit is not tted.
One air lter per fan/power supply unit is required (Maximum of 3 per PCU).
Each PCU cPCI shelf needs 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 conguration, or if the Web MMI feature is enabled.
One alarm board per PCU is required.
One main circuit breaker panel per PCU is required.
There are four bays on the right side of the shelf that can be used for auxiliary equipment
such as tape drives, CD-ROM drives and hard disks. The PCU is congured without any
auxiliary equipment and this area of the shelf is covered with blank panels.
If E1 connectivity is used, 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.
8-18
68P02900W21-R
GMR-01
Nov 2007
MPROC board
MPROC board
Introduction
The PCU planning process determines the type and number of MPROC boards to populate
in the PCU. The PCU provisioning requirements take the MPROC redundancy solution into
consideration.
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 conguration and fault handling for the PCU site.
If MPROC redundancy is required, each PCU cPCI shelf requires two MPROC cards (boards).
The MPROC redundancy ag specied during the equipping of the PCU should be enabled. The
MPROC cards should be inserted in slot 7 and 9 (refer to Figure 8-2). A MPROC (PSP 0) card is
inserted into slot 7 and the other MPROC (PSP 1) is inserted into slot 9. The 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 ag specied 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 ag 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 or MCP750 microprocessor board with a TMCP700
transition module.
68P02900W21-R
8-19
GMR-01
Nov 2007
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 trafc estimation and key concepts on page 3-141 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 can be congured as a PICP with zero, one, or two E1 PMC modules, and with PICP
software. The DPROC can be congured 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 four 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 rst 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 complement PICP board:
The PCU can support up to six PICP boards but the recommended maximum for most
congurations is four. Conguring more than four PICPs per PCU would normally require
multiple PCUs.
A PICP board supports a maximum of two PMC modules or MSIs.
The PICP boards can terminate the following links: LAPD-Type GDS links (GSL), and
Gb links (GBL).
8-20
68P02900W21-R
GMR-01
Nov 2007
PRP board
The following factors should be considered when planning the complement PRP board:
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 the PICP
boards.
PRP boards with PMCs can terminate one GDS TRAU E1 per PMC module for GPRS and
two GDS TRAU E1s when congured 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 can be slightly different from that shown
here depending on cell congurations, that is, all timeslots for a single cell must
terminate on a single PRP, which can lead to slight imbalances when multiple
timeslots are congured 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 so on) such that the trafc 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 means in determining
whether the boards are overloaded. In a system with multiple PRPs, the load is generally
balanced across all PRPs and the CPU utilization is similar as well. The general rule is to
consider adding a PRP in a PCU if the CPU utilization on any of the PRPs consistently exceeds
80% during peak hours.
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) can be considered
in order to make a consistent decision. CPU utilization plots versus time can help observe a
pattern in increased CPU utilization.
68P02900W21-R
8-21
GMR-01
Nov 2007
PRP load (modied per service pack 1670.27t1)

This statistic to determine the actual load on the PRP and help to understand the trafc patterns
in the system. For instance, when the majority of the GPRS trafc 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 trafc is expected to produce a PRP_LOAD value
in the range of 5-10. However, the PRP_LOAD is higher when the PRP handles actual data
transfer (WAPs, FTPs and so on).
This statistic reports a MEAN value by default, but it is important to congure the individual bins
to get a ner resolution on the trafc in order to determine a change of trafc volume over time
when QoS is critical. A MEAN value greater than 100 implies that more than 30 TS are pending
service, which generally indicates a non-optimal throughput. This is optimal for networks that
allow some PDTCH congestion level at the cells (refer to DL_PDTCH_CONGESTION statistics).
However, PRP_LOAD MEAN values in the range of 101-160 are acceptable if the trafc density
per PDTCH on a cell level is moderate. This results in good throughputs.
For a MEAN PRP_LOAD exceeding 160, it is recommended to consider adding a PRP.
Maintaining a MEAN PRP_LOAD over 160 results 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 congure at least 4 PDTCH/cell on the BCCCH
carrier for optimizing the throughput of multi-slot mobiles that are capable of 4 TS on the DL
(downlink). Conguring more than 4 TS/cell normally assumes the expectancy of high volumes
of actual data trafc and the planning guidelines described in Chapter 3 BSS cell planning.
However, if most of the trafc is signaling (attaches/detaches, PDP Context Act/Deact, Cell
Updates, RAUs), several statistics are to be monitored 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. The following
statistics are useful in determining the PDTCH requirements for a cell.
DL_BUSY_PDTCH
This statistic measures the MEAN, MAX and MIN number of occupied PDTCH carrying downlink
packet trafc. 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 congured to report 10 bins. By default, bin 0 is pegged every block period (20 ms)
when no TBFs are allocated on any of the PDTCHs on the cell. Bin 1 is pegged when 1 to 2
PDTCHs are busy; bin 2 is pegged when 3 to 4 PDTCHs are busy, and so on. For example, a cell
congured with 10 PDTCHs, with a MEAN value reported as 9.2 implies that all 10 congured
PDTCHs are being utilized and needs a further look at the DL_PDTCH_CONGESTION statistic.
However, if the MEAN is 5, the congured PDTCHs are probably under utilized and the number
of PDTCHs can be reduced. Before reducing the number of PDTCHs, other statistics have
to be evaluated rst.
8-22
68P02900W21-R
GMR-01
Nov 2007
AVAILABLE_PDTCH
This statistic enables to optimize the number of switchable versus reserved TSs in a cell. If the
busy hour of voice trafc does not interleave with GPRS busy hour, some TS can be congured as
switchable, carrying voice trafc during CS busy hour and data trafc during GPRS busy hour.
Example:
8 of 10 TSs are congured 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 where TSs is stolen to handle voice trafc and therefore
needs the addition of TSs to this cell to handle the GPRS trafc.
MS_CLASS_1_10_REQ
This statistic enables to determine the average number of TSs used by the average mobile on
the DL and UL. Hence, it provides an indication what kind of throughput can be expected. For
example, a class 10 mobile (capable of 4 DL and 2 UL TS) expects high throughputs.
NO_PDTCH_AVAIL
This statistic is pegged in extreme conditions when the last switchable TS are stolen for a voice
call. This condition indicates that GPRS service is not available at this time on the cell and
requires a reconguration of switchable versus reserved TS, or the addition of TS in the cell.
DL_PDTCH_CONGESTION
This statistic is pegged when the average trafc density in a cell exceeds 2 MS/PDTCH.
Although each PDTCH can interleave up to 4 MS, it is not the recommended trafc 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 that 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
does 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 trafc (higher than 90%) is known to be signaling, a congestion
level of up to 50% of the busy hour statistics time interval can be allowed. Under this level of
congestion and when the intended PRP_LOAD is already high (<100), those 10% of subscribers
who attempt to transfer data experience throughput degradation.
GBL_DL_DATA_THRPUT
This statistic is compared with the SGSN statistic to determine the actual data sent across the
network that does not result from signaling trafc.
68P02900W21-R
8-23
GMR-01
Nov 2007
PMC module
PMC module
Introduction
The number of PMC modules installed depends on the number of PICP /PRP congured boards
in the PCU.
The following factors should be considered when planning the PMC complement for the DPROC
board:
Each PRP board needs at least one PMC module.
Each PICP board has up to two PMC modules. TRAU-type GDS terminate on a PMC module
in a PRP board. LAPD-type GDS (GSL) and Gb E1 (GBL) links terminate on a PMC module
in 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 congured 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 12416 kbit/s TRAU, 62-32
bit/s TRAU and 62-64 kbit/s {23769} (each individual DS0 that is part of a Versachannel is
a single 64 kbit/s TRAU channel) TRAU such that the following equation is satised:
{23769}
#16 kbit/s TS + (2 x #32 kbit/s TS) + (2 x 64 kbit/s DS0s) < 124
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 equation.
The PMC NIB has sufcient CPU capacity to support a 124-16 kbit/s TRAU or one full span.
Since 32 kbit/s TRAU is actually composed of two 16 kbit/s TRAU channels, the PMC NIB
can support half as many 32 kbit/s TRAU, or one full span. With the channelized subrate
insert/extraction removed in the 64 kbit/s {23769} (VersaTRAU) TRAU, the PMC NIB can
achieve twice as much bandwidth, which is 62 of the 64 kbit/s TRAU channels, or two full
spans of 64 kbit/s TRAU. The PMC NIB can support an arbitrary combination of 16 kbit/s
and 64 kbit/s {23769} (VersaTRAU) TRAU channels, or channels with channelized subrate
insertion/extraction and those without, trading off at a ratio of two 16 kbit/s timeslots to one 64
kbit/s timeslot. When mixed trafc is used, the two spans on the PMC NIB are not fully utilized.
8-24
68P02900W21-R
GMR-01
Nov 2007
Transition module
Transition module
Introduction
The number of rear transition modules installed depends on the number of PICP/PRP boards
congured in the PCU.
The following factors should be considered when planning the number of rear transition
modules required:
One rear transition module is required per PRP board.
One rear transition module is required per PICP board.
68P02900W21-R
8-25
GMR-01
Nov 2007
PCU equipment redundancy and provisioning goals
PCU equipment redundancy and provisioning goals
Support for equipment redundancy

The PCU supports four types of redundancy:
2N
1MPROC/bridge board pair (non-redundant), 2 MPROC/bridge board pairs (redundant).
N+1
2PS/FAN units (non-redundant), 3 PS/FAN unit (redundant). Use 3 fan units.
Load shared
The signaling 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 signaling 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 automatically balances the number of air
timeslots across the available PRPs. In the event of a GDS link failure, the BSC and
PCU attempt to move the air timeslots to another available GDS link. In the event of a
PRP failure, all the air timeslots on the failed PRP are 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 sufcient 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 trafc 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 rst 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 trafc for a fully congured 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 when EGPRS carriers are equipped.
8-26
68P02900W21-R
GMR-01
Nov 2007
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 trafc on the other
boards. The DPROC must be locked before removal and unlocked after board insertion. The PRP
and PICP boards have associated transition module boards. 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 or 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 a considerable degree of provisioning exibility. Figure 8-3 and
Figure 8-4 demonstrate this exibility where the provisioning goals 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).
Table 8-8 summarizes the provisioning goals demonstrated with Figure 8-3, Figure 8-4 and
Figure 8-5.
68P02900W21-R
8-27
GMR-01
Nov 2007
Figure 8-3 GPRS maximum throughput and coverage, fully redundant conguration
12 4 @ 16K/GDS TRAU
CHANNELS
PCU HARDWARE
GDS
PMC
P RP 1
120 TS MAX, 30
TS MAX ACTIVE
BSC
GDS
PMC
S GS N
GDS
PMC
P RP 2
120 TS MAX, 30
TS MAX ACTIVE
GDS
PMC
TO
GDS
P RP 8
120 TS MAX, 30
TS MAX ACTIVE
PMC
GDS
PMC
REDU NDANT
GDS
REDU NDANT
GDS
P RP 9
REDUNDANT
120 TS MAX, 30
TS MAX ACTIVE
PMC
PMC
GSL
PMC
P ICP 1
PMC
30 LAP D
TX MAX
REDU NDANT
GSL
GBL
GBL
P ICP 2
PMC
30 LAP D
TX MAX
PMC
PMC
REDUNDANT
GBL
P ICP 3
REDUNDANT
PMC
REDUNDANT
GBL
ti-GSM-Provisioning_goals_full_redundancy-00136-ai-sw
Refer to Table 8-8 for a matrix of provisioning goals achieved with this instance of PCU
provisioning.
8-28
68P02900W21-R
GMR-01
Nov 2007
Figure 8-4
GPRS maximum throughput and coverage, full redundancy not required
ti-GSM-Provisioning_goals_Maximum_coverage-00137-ai-sw
provisioning.
Figure 8-4 shows 18 GDSs, as required for CS3/CS4. Only 9 GDSs are required for
CS1/CS2.
68P02900W21-R
8-29
GMR-01
Nov 2007
Figure 8-5 EGPRS maximum throughput and coverage, full redundancy not required
ti-GSM-EGPRS_maximum_throughput_and_coverage_full_redundancy_not_required-00138-ai-sw
provisioning.
8-30
68P02900W21-R
GMR-01
Nov 2007
Table 8-8 Provisioning goals (per PCU)

Metric
Goal
GPRS maximum
coverage with
redundant
conguration
(Figure 8-3).
GPRS maximum
coverage, redundancy
not required
(Figure 8-4).
EGPRS maximum
coverage,
redundancy
not required
(Figure 8-5).
Number of timeslots
processed at any
instance in time
240
270
270
Total number
of provisioned
timeslots at a BSS
960
1080
1080
Number of MPROCs
Number of PRPs
Number of PICPs
Number of
TRAU-Type GDS
E1s
18
18
{23769} 36**
Number of
LAPD-Type GDS
(GSL)E1s
Number of Gb E1s
MPROC board
redundancy
Yes
No
No
PRP board
redundancy
Yes
No
No*
PICP board
redundancy
Yes
No
No*
GDS TRAU E1
redundancy
Yes
No
No*
GSL E1 redundancy
Yes
Yes
Yes
Gb E1 redundancy
Yes
Yes
Yes
* Capacity does not meet calculated maximums in the event of a failure. This can
or cannot affect customer usage dependant on the current load of the system.
** {23769} The maximum number of GDS resources can be less if VersaTRAU is

unrestricted and EGPRS carriers are equipped with less than 8 DS0s of backing
on the backhaul.
68P02900W21-R
8-31
GMR-01
Nov 2007
Upgrading the PCU
Upgrading the PCU

The PCU can be incrementally upgraded for additional capacity, by adding one PRP board or by
one PICP board at a time. Table 8-9 shows different upgrade scenarios based on the number of
timeslots supported by PRP and redundancy required. The actual number of boards and links
required is based upon the formulas in this chapter.
Table 8-9 shows maximum congurations for EGPRS.
Table 8-9 Upgrade scenarios for PRP conguration

No. of air
timeslots
No. of
PRP
No. of
PICP
No. of
GDS
No. of
GBL
No. of
GSL
Total
links
120
240
12
No Gb
redundancy
240
16
With
redundant
links
360
12
20
With
redundant
links
480
16
24
With
redundant
links
600
20
24
No Gb
redundancy
600
20
28
With
redundant
links
720
24
10
36
With
redundant
links
840
28
10
40
With
redundant
links
960
32
10
44
With
redundant
links
1,080
36
10
48
With
redundant
links
8-32
Remarks
Minimum.
conguration,
no
redundancy
68P02900W21-R
GMR-01
Nov 2007
Upgrading the PCU
* All air timeslots are assumed to be EGPRS capable and {23769} assumed to have a
backing on the backhaul of 64 kbit/s/air timeslot. If VersaTRAU is unrestricted, the
number of GDS resources is between 18 and 36 and depends on the number of DS0s
equipped for each EGPRS RTF on the backhaul.
68P02900W21-R
8-33
GMR-01
Nov 2007
Multiple (3xPCU) PCUs per BSC
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 trafc 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 trafc load.
Redundancy is provided for when more than one PCU is equipped. For each PCU, a rst
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.
PCU example congurations

Figure 8-6 demonstrates some of the various physical congurations that are supported. The
actual conguration 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 congurations supported.
Figure 8-6 (a) illustrates a common one PCU per BSC conguration.
Figure 8-6 (b) illustrates a conguration 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
conguration 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.
8-34
68P02900W21-R
GMR-01
Nov 2007
Figure 8-6 (c) illustrates a very likely conguration. This assumes an initial conguration of (a).
As the GPRS trafc increases and equipment is added, additional PCU shelves are added and
connected to the BSC. In this case, BSCa expanded rst 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 lled out
the remaining shelves in cabinet 3.
Figure 8-6 (d) illustrates a conguration that has some benets in expansion cost but yet
provides some direct correlation between shelf location and the BSC. In this case, BSCa requires
more trafc 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.
68P02900W21-R
8-35
GMR-01
Nov 2007
Figure 8-6 PCU example congurations

PCUa
BSCa
PCUb
PCUc
Cabinet 1
BSCa
BSCb
BSCc
PCUa
PCUb
PCUa
SGSN
BSCb
PCUb
PCUc
PCUc
Cabinet 1
Cabinet 2
SGSN
PCUa
(a) Current
BSCc
PCUb
PCUc
Cabinet 3
(b) High initial cost / best maintenance
PCUa
BSCa
PCUa
PCUb
BSCa
PCUc
Cabinet 1
Cabinet 1
PCUa
BSCb
PCUb
PCUa
SGSN
BSCb
PCUb
PCUc
PCUc
Cabinet 2
Cabinet 2
PCUa
BSCc
PCUb
PCUc
PCUa
PCUb
BSCc
PCUb
PCUc
PCUc
Cabinet 3
Cabinet 3
(c) Most likely
SGSN
(d) Cabinet cost and maintenance considered
8-36
68P02900W21-R
GMR-01
Nov 2007
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 E1 length specication.
The PCU is congured 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 congured 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 DACs for this purpose.
E1 Planning considerations
The following factors should be considered when planning the E1 interfaces.
GDS TRAU E1
On the PMC NIB, the PCU can support an arbitrary mixture
of 12416 kbit/s TRAU, 6232 kbit/s TRAU and 6264 kbit/s {23769}
(VersaTRAU DS0s) TRAU such that the following equation is satised:
{23769}
#16 kbit/s TS + (2 x #32 kbit/s TS) + (2 x 64 kbit/s DS0s) < 124
Calculation of the number of GDS E1 TRAU = (a/4 + b/2 +c)/31 where:
a - is a number of 16 kbps slots
b - is a number of 32 kbps slots
c - is a number of 64 kbps slots
When GPRS is congured, each PMC on a PRP supports one E1 link. If EGPRS is
congured, each PMC can support two E1 links. However, the second E1 can only
be used for EGPRS.
PCU GDS E1
There can be up to 18 TRAU-type GDS E1 links per PCU for GPRS and 36 TRAU-type GDS E1
links per PCU for EGPRS.
68P02900W21-R
8-37
GMR-01
Nov 2007
E1 Planning considerations
GSL LAPD (GSL) E1

The GSL trafc is load balanced over all GSLs. Each E1 carries up to 30 LAPD links. 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 signaling
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.
PCU Gb E1 (GBL)
There can be up to 4 Gb E1s per PCU for GPRS and 12 Gb E1s per PCU for EGPRS.
GPROC LCF
The GPROC LCFs available at the BSC terminate up to 12 LAPD channels. Up to 60 LAPD-type
links can be provisioned at the PCU. The LAPD links can be distributed on the LCF automatically,
based on the capacity available on the LCFs.
Either the GPROC2 or the GPROC3 can perform LAPD-type link processing.
8-38
68P02900W21-R
GMR-01
Nov 2007
QoS capacity
QoS capacity
{23956}
The QoS feature retains the 120 mobile per PRP board limit from previous loads. 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 rst. 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 trafc classes are set to high values, or there are multiple PFCs per mobile,
fewer mobiles can be serviced per PRP board.
A simple example is when there is only one GPRS timeslot equipped and in-service, and a
high ARP value 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 value cannot be
assigned to that timeslot without compromising the service of the rst high ARP value PFC
and are subsequently rejected. Four mobiles can be allocated on each PDTCH provided there
is sufcient available throughput.
When the BSS is managing its pool of MTBR resources, it reserves headroom (16.7%), 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 rst 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,
does 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 boards
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 veries that there is sufcient headroom at both of
these levels. If there is insufcient headroom to admit the new mobile, other mobiles can be
downgraded and/or pre-empted and the requesting mobile can 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 kbit/s
of MTBR can be allocated for GPRS and 14 kbit/s for EGPRS per timeslot. This maximum
value is used for all the capacity calculations.
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 the timeslot zones on the PRP board.
68P02900W21-R
8-39
GMR-01
Nov 2007
QoS capacity
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 8 kbit/s committable bandwidth per slot). 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.
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 PRP
board. By dividing the summation of the local timeslot zones (the available MTBR commitment)
by the commitment made to each mobile (2 kbit/s) 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 kbit/s 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

Parameter
Coding scheme
CS-1/2
CS-3/4
EGPRS
12000
20000
59200
Local timeslot zone MTBR

throughput per TS (bit/s)
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 throughput
over PRP (bit/s)
960000
960000
960000
Theoretical limitation based

solely on local timeslot zone
restriction Max MS at 2
kbit/s/MS
480
480
480
Local timeslot zone

Maximum MS at 2 kbit/s/MS
120
120
120
Peak throughput per TS

(bit/s)
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 8 kbit/s committable bandwidth per
slot). CS-1 is the worst case.
8-40
68P02900W21-R
GMR-01
Nov 2007
Table 8-11
MTBR allocation
PRP Board Service Level Capacity 4MS/PDTCH
Parameter
Coding scheme
CS-1
CS-1/2
CS-3/4
EGPRS
Peak throughput per TS (bit/s)
8000
11200
15360
25120
Number of PDCH every block

period (PRP board, 30/120
mode)
30
30
30
30
240000
336000
460800
753600
16.7
16.7
16.7
16.7
Summation of local timeslot

zone level MTBR throughput
over PRP (bit/s)
200000
280000
384000
628000
Theoretical limitation based

solely on local timeslot zone
restriction Maximum MS at 2
kbit/s/MS
100
140
192
314
Local timeslot zone Maximum

MS at 2 kbit/s/MS
100
120
120
120
Local timeslot zone MTBR

throughput
Local timeslot zone total
headroom (%)
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 kbit/s
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. While considering the overall PRP capacity, the PRP service level headroom usually limits
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 kbit/s in both uplink and downlink for all trafc
classes, interleaving is limited to one mobile per timeslot in the uplink and 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 combination 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
The BSS attempts to maintain its MTBR commitments to PFCs in the order of priority by ARP
Value. In other words, PFCs of a higher ARP Value are more likely to get access to the system
and get their requested MTBR.
The BSS attempts to ensure the ARP Value ordering of MTBR commitments through
downgrading and pre-emption.
68P02900W21-R
8-41
GMR-01
Nov 2007
MTBR allocation
Per timeslot commitment

The BSS commits a maximum of 6 kbit/s of MTBR in the downlink and in the uplink per GPRS
timeslot on the air interface (and 12 kbit/s per EGPRS timeslot) 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 the commitment is headroom and is allocated to the mobiles according to their THP
weights. For timeslots that are congured as PCCCH timeslots, the BSS commits 0 kbit/s of
MTBR. PCCCH timeslots share both user data and control signaling. Therefore, the BSS does
not make any MTBR commitments on the PCCCH timeslot. There could be a large amount of
control signaling transmitting (which has 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 can be used to admit a fourth mobile on to a timeslot, effectively
increasing the committable bandwidth on that GPRS timeslot to 8 kbit/s (and 14 kbit/s per
EGPRS timeslot). 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 allows 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. The headroom allows
the MTBR commitments to be maintained regardless of any coding scheme changes made
by the mobile.
Each trafc class has an associated MTBR that is congurable by the operator, or is xed
at zero. Within the interactive trafc class, each THP has its own associated MTBR that is
congurable 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 trafc classes except for interactive THP 1 and interactive THP 2, the maximum MTBR
can be t into a single timeslot allocation no matter how the MTBR is set. This guarantees that
these classes are not rejected by the system when timeslots are idle in the cell and available
throughput exists on the PRP board.
Within the interactive trafc class, the THP 3 class has a maximum MTBR that can be t into a
single timeslot allocation no matter how the MTBR is set. This means that a THP 3 is not
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 kbit/s in the downlink and 6
kbit/s in the uplink. THP 1 and THP 2 are downgradable to THP3 so that they can be t into a
single timeslot and thus are not 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 allocates no more than 6 kbit/s 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
is downgraded.
Refer to Table 8-12 for maximum MTBR in downlink and uplink for each multislot class.
8-42
68P02900W21-R
GMR-01
Nov 2007
MTBR allocation
Table 8-12 Maximum MTBR in UL/DL per multislot capability

Mobile multislot
class
Multislot class
supported
Maximum MTBR
(uplink)
Maximum MTBR
(downlink)
1 uplink timeslot
1 downlink timeslot
1 uplink timeslot
2 downlink timeslots
12
1 uplink timeslot
18
2 uplink timeslots
12
2 uplink timeslots
or
1 uplink timeslot
12
1 uplink timeslot
24
2 uplink timeslots
18
10
10
1 uplink timeslot
or
2 uplink timeslots
18
11
11
Class 10 or
3 uplink timeslots
2m
12
12
Class 10 or
4 uplink timeslots
1 downlink timeslot
Possible congure
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 xed in each direction. Thus, multislot class 6 is committed at most
12 kbit/s (2 timeslots) in the downlink and 6 kbit/s (1 timeslot) in the uplink, and class 10 is
committed at most 18 kbit/s (3 timeslots) in the downlink and 6 kbit/s (1 timeslot) in the uplink.
Per timeslot zone commitment

The BSS limits its MTBR commitment to a timeslot zone to 6 kbit/s of MTBR in the downlink
and in the uplink per timeslot in that timeslot zone unless a fourth mobile is scheduled on that
timeslot. When scheduling the fourth mobile on a timeslot, the BSS allows a commitment to be 8
kbit/s on all timeslots where there are four mobiles assigned.
68P02900W21-R
8-43
GMR-01
Nov 2007
PRP-PDTCH QoS planning
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.

The maximum number of PDTCHs to assign per PRP based on the information provided in
{23956} QoS capacity is calculated using the following steps:
Calculate the PRP board throughput based on coding schemes used while subtracting
PRP board headroom.
Calculate the average downlink MTBR to determine the amount to reserve for each QoS
subscriber.
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:
%CS1_USAGE
%CS2_USAGE
%CS3/4_USAGE
%EGPRS_USAGE
Is:
the percentage of time the relevant coding
scheme is used by subscribers in the cells
attached to a given PCU.
Calculating average downlink MTBR

Average downlink MTBR is calculated as follows:
8-44
68P02900W21-R
GMR-01
Nov 2007
Where:
I1_MTBR
Is:
The downlink MTBR values set for each of the
trafc classes.
I2_MTBR
I3_MTBR
BG_MTBR
BE MTBR
% subs
The percentage of subs allocated to each of

the trafc 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 trafc class.
The MTBR values are dened at the cell level. The values to use for this equation are
either the average MTBRs for each trafc class across all cells connected to a PCU or
the maximum MTBR values set at a cell for each trafc class.
Calculating MAX_QOS_MS_PER_PRP
MAX_QOS_MS_PER_PRP is calculated as follows:
MAX_QOS_ MS_PER PRP = PRP_BOARD_THROUGHPUT/AVERAGE_DOWNLINK_MTBR
68P02900W21-R
8-45
GMR-01
Nov 2007
PCU-SGSN: trafc and signal planning
PCU-SGSN: trafc and signal 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 identiers.
Table 8-13 Gb entities and identiers

Description
Gb Entity and Identier

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 specic PVC.
Data link connection identier

(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
signicance across the network, and is therefore the
same at the SGSN and PCU.
Network service entity

identier (NSEI)
Uniquely identies a NSE.
Continued
8-46
68P02900W21-R
GMR-01
Nov 2007
General planning guidelines
Table 8-13 Gb entities and identiers (Continued)

Description
Gb Entity and Identier

Network Service Virtual Circuit
(NSVC)
A logical circuit that connects the NSE peers between

the SGSN and PCU. The NSVC has signicance across
the network. Therefore, it is congured identically at
the SGSN and PCU.
Network Service Virtual Circuit

Identier (NSVCI)
Uniquely identies 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. It is only congured in the PCU. The
PCU contains one point-to-point BVC per an actively
serving cell.
BSSGP Virtual Circuit Identier

(BVCI)
Uniquely identies a BVC.
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 congured at the PCU and dynamically
congured 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 signicance only while the NSVCI has signicance across the network.
One E1 can be fractionalized into several bearer channels.
Specic planning guidelines

Motorola deploys one NSEI per PCU. Each NSEI must be unique.
Gb signaling
This section describes the Gb protocol signaling. The signaling and the Gb link capacity
limitations must be considered in each Gb link plan.
68P02900W21-R
8-47
GMR-01
Nov 2007
Determining net Gb load
Gb protocol signaling
The GPRS/EGPRS Mobility Management (GMM/EGMM) signaling procedures that 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.
Determining net Gb load

Consider the network equipment, trafc 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:
Where:
Is:
Total Data Rate
the required bandwidth (bit/s) for GPRS data

transmission over a GBL interface between the PCU
and SGSN after all of the protocol and signaling
overhead is accounted for.
Signaling_Data_Rate
the required rate (bytes/s) for GPRS signaling

transmission over a GBL interface between the PCU
and SGSN after all of the protocol.
User Data Rate
the required rate (bytes/s) for GPRS user application

data over a GBL interface between the PCU and
SGSN, including protocol overhead.
Continued
8-48
68P02900W21-R
GMR-01
Nov 2007
Gb link timeslots
Where:
Is:
PSattach/detach
the attach/detach rate per sub/BH.
RAU
the periodic, Intra and inter area update rate per

sub/BH.
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 trafc per subscriber in a busy hour

(kbytes/busy hour).
CellUpdate
the cell reselections rate per sub/busy hour.
To simplify Gb planning, the Signaling_Data_Rate can be ignored since it is

insignicant compared to the Total_Data_Rate.
Gb link timeslots
The trafc and signaling 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 . Each E1 can
carry up to 31 timeslots. When fewer than 31 timeslots are needed on an E1, specifying a
fractional E1 is 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
dened by the equation in the previous section, and

represents the required bandwidth (bps) for GPRS
data transmission over a GBL interface between the
PCU and SGSN after all of the protocol and signaling
UGBL
the link utilization.
NPCU-SGSN
the E1 link between the PCU and SGSN.
68P02900W21-R
8-49
GMR-01
Nov 2007
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)
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
ti-GSM-Frame_relay_parameters-00142-ai-sw
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. The BSSGP feature 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 handles the trafc throughput equal to the number
of timeslots planned for the busy hour trafc load.
8-50
68P02900W21-R
GMR-01
Nov 2007
The recommended frame relay network CIR value is calculated as follows:
Where:
Is:
CIR_Value
the committed Information rate per NSVC (PVC).
the CIR provisioning factor, equal to 0.5.
Total_Data_Rate
dened in Determining net Gb load on page 8-48, and

represents the required bandwidth (bit/s) for GPRS
data transmission over a GBL interface between the
PCU and SGSN after all of the protocol and signaling
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
congured 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 congured 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 discardable.
68P02900W21-R
8-51
GMR-01
Nov 2007
BSS-PCU hardware planning example for GPRS
BSS-PCU hardware planning example for GPRS
Introduction
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
ti-GSM-PCU_equipment_and_link_planning_for_GPRS-00143-ai-sw
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 (that is, NOM I), PCCCH enabled (pccch_enabled = 1) at some
cells, and with the following GPRS call model:
Table 8-14 GPRS call mode

Item
Value
Average packet size (bytes)
PKSIZE=270
Trafc per sub/BH (kbytes/hr) uplink
ULRATE=30
Trafc per sub/BH (kbytes/hr) downlink

Data rate_per sub=65

PSattach/detach=0.5
Continued
8-52
68P02900W21-R
GMR-01
Nov 2007
Table 8-14
GPRS call mode (Continued)

Item
Value

sub/BH)
PDPact/deact=0.5
RAU=1.5
Routing area update

Cell Updates
CellUpdate =1.5
PGPRS=3
200
GPRS users per cell
Average sessions per user per hour

GSM circuit-switched paging rate
(pages/second)
PGSM=3
LCS=0.2
LRMT=0.95

Ratio of mobiles in the system that are both
GSM and GPRS capable
NGSM GPRS Ms/NaII MS=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
Selecting a cell RF plan

Use the 4 x 3 non-hopping table (Table 8-14) to determine what values to use for CS rate and
BLER for the selected cell RF plan.
Determining 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 trafc with the existing circuit-switched trafc 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 reduces the GSM
circuit-switched signaling load on the CCCH with paging coordination.
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 on page
3-119 section of Chapter 3 BSS cell planning.
68P02900W21-R
8-53
GMR-01
Nov 2007
Determining 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 trafc 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
Determining the number of GPRS carrier timeslots at each BTS cell

Use the equation 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 congured on one of those 6
timeslots.
8-54
68P02900W21-R
GMR-01
Nov 2007
Calculating the number of GDS E1

Compute the number of GDS TRAU E1 channels required for the air interface timeslots required
to carry the trafc. Remember:
Each CS1/CS2 timeslot requires 16 K TRAU channel.
CS3/CS4 timeslots require 32 K 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 for capacity.
Calculating 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 (calculated previously in Determining the number of GPRS
carrier timeslots at each BTS cell on page 8-54 ), 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.
Partition the load across multiple PCUs

If additional PCU(s) are 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.
Calculating 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 Partitioning the load across another PCU (another BSS), the
number of PRPs required is:
These 2 PRPs have more than enough capacity to handle the additional 3 standby timeslots
per cell.
Refer to the appropriate section of this chapter for the PCU provisioning rules.
68P02900W21-R
8-55
GMR-01
Nov 2007
Calculating the BSC LCF impact to support GPRS trafc

The BSC LCF GPROC processor load is increased by the volume of GPRS signaling trafc. The
BSS planning rule for LCF provisioning in the following equation should be used.
Where B is the number of BTS sites.

In this instance, B=10.
The network planner can select to add an additional LCF GPROC or to examine the GSM
circuit-switched provisioning to check if an existing LCF GPROC can process this additional load.
Calculating the number of GBL links

Using the standard trafc model and Gb formulae:
Hence, 2 Gb links have to be provisioned.
Calculating 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 this step. 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).
8-56
68P02900W21-R
GMR-01
Nov 2007
Refer to Determining the number of GSLs required on page 6-47 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:
Balancing the GSL load across the LCF

This step can 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
on page 6-49 section of Determining the number of GSLs required on page 6-47 in Chapter 6
BSC planning steps and rules.
Calculating the PCU hardware to support the PCU trafc

To calculate the PCU hardware for supporting the PCU trafc, the following requirements
are to be considered:
2 PRP boards, 1 PRP board per GDS E1 link.
1 PICP board, 1 PICP board to process GDS LAPD.
1 MPROC board per PCU shelf (2 for redundancy).
1 PCU shelf with alarm board and 3 power supply/fan assemblies, 1 PCU shelf per 9 PRP
boards.
1 PCU cabinet per 3 PCU shelves (cages).
After calculating the number of GDS, GBL and GSL E1 links, ensure that there are sufcient
number of PICP boards to cover the GBL and GSL E1 links. The PCU hardware calculation
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.
Two E1 links are required for the GBL. Each PICP can terminate up to 4 GBL links. Therefore,
2/4 (1/2) PICP is required for the GBL E1 links.
68P02900W21-R
8-57
GMR-01
Nov 2007
One E1 link is required for the GSL (redundant GSL not provided). Each PICP can terminate up
to 2 E1 GSL links and up to 12 GSL 64 kbit/s timeslots distributed over two E1s.
There is a limit of 2 GSL E1s per PCU. Therefore, 1/4 of a PICP is required for the
GSL E1 link.
The GBL and GSL E1 link requirements show that one PICP is sufcient to process the link
provisioning requirements.
Calculating the increased data trafc load on the E1s between the BSC
and BTSs
It is assumed that the GPRS trafc is in addition to the existing circuit-switched trafc. Six
timeslots are required for the GPRS timeslot trafc on a per cell basis. Therefore, an additional
12 x 16 kbits/s timeslots (CS1/CS2) or 32 kbit/s timeslots (CS3/CS4) are required on a per BTS
site basis, 2 cells per site, in order to carry the GPRS trafc.
The allocation of GPRS carrier timeslots has to be decided, that is, they are reserved or
switchable. GSM circuit-switched statistics can be used to decide about the allocation. Refer to
Dynamic timeslot allocation on page 3-143 in Chapter 3 BSS cell planning.
Calculating the changes in signaling trafc load (RSL load) on the E1s
between the BSC and BTSs
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling
load for the GPRS data trafc with the existing circuit-switched trafc 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 signicant additional control channel load on the RSL. In this case, however,
PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging coordination.
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-20 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.
8-58
68P02900W21-R
GMR-01
Nov 2007
BSC link provisioning impact

The BSC needs additional hardware to support the addition of the GPRS network trafc. For
BSC provisioning, refer to the planning rules given in Chapter 6 BSC planning steps and rules.
The BSC needs more E1 terminations in support of the additional E1 links to the PCU and in
support of the additional GPRS trafc over the BTS to BSC interface. In this example, 4 E1s
were added for the GDS links and 3 E1s added for the GSL link.
BTS provisioning impact

GPRS has no impact on the hardware provisioning of a Horizon II macro, Horizonmacro or
M-Cell BTS.
68P02900W21-R
8-59
GMR-01
Nov 2007
BSS-PCU hardware planning example for EGPRS
BSS-PCU hardware planning example for EGPRS
Introduction
This section builds upon the previous example shown in BSS-PCU hardware planning
example for GPRS on page 8-52 by adding EGPRS into the system.
The main additions are:
New EGPRS carriers.
Calculation of the impact of increased data capacity on the system.
The provisioning of the SGSN hardware is not covered in this planning guide.
Figure 8-9 PCU Equipment and link planning for EGPRS
ti-GSM-PCU_equipment_and_link_planning_for_EGPRS-00144-ai-sw
BSS - PCU planning example for EGPRS

The example for EGPRS has new call model parameters for increased data usage.
Refer to BSS - PCU planning example for GPRS on page 8-52 to compare the
GPRS/EGPRS call model parameters.
8-60
68P02900W21-R
GMR-01
Nov 2007
Use this example to provision a BSS with 10 sites consisting of 20 cells, one GPRS carrier per
cell, PCCCH disabled (pccch_enabled = 0) at cells.
Additional data
{23956} The QoS feature is not enabled. Add one EGPRS carrier per cell with the following
call model:
Table 8-15 EGPRS call model

Item
Value
PKULSIZE=287
PKDLSIZE=701
Trafc per sub/BH (kbytes/hr) - uplink
Trafc per sub/BH (kbytes/hr) - downlink

sub/BH)
ULRATE=40

PSATT/DETACH=0.78
PDPACT/DEACT=1
RAU=1.1
Routing area update

Cell Updates
CellUpdate=2.86
PGPRS=1.4
250
GPRS/EGPRS users per cell


(pages/second)
PGSM=0.32
LCS=0.2
LRMT=0.95

Ratio of mobiles in the system that are
both GSM and GPRS capable
NGSM GPRS MS/NAU MS=100%
Percentage of mobiles that are EGPRS

capable
5%
Number of PCCCH-enabled cells in the

BSS
10
20
I1_MTBR_USAGE
5%
I2_MTBR_USAGE
10%

Use the 4 x 3 non-hopping table (Table 3-20 in Chapter 3 BSS cell planning) to determine the
values to use for CS rate and BLER for the selected cell RF plan.
68P02900W21-R
8-61
GMR-01
Nov 2007

circuit-switched signaling load on the CCCH with paging coordination. 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 Control channel calculations
on page 3-119 in Chapter 3 BSS cell planning.
Determine the number of PCCCHs at each BTS cell

be considered.
8-62
68P02900W21-R
GMR-01
Nov 2007
four.
Determining number of GPRS and EGPRS carrier timeslots at each BTS cell
basis. To use this equation, the expected cell load in kbit/s should be known.
Therefore, provision 4 timeslots on the cell. The PCCCH will be congured on one of those 4
timeslots. This is a lower number than in the previous example. The number of users and
Mean_trafc_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 congured as
switchable or packet data from the original GPRS carrier and 8 timeslots dened 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.
Calculating the number of GDS E1 links

to carry the trafc. The following requirements have to be considered:
Each CS1/CS2 timeslot needs 16 K TRAU channel.
CS3/CS4 timeslots needs 32 K TRAU.
MCS1 through MCS9 need {23769} a variable VersaTRAU backhaul in units of 64 K 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
conguration needs less GDS resources.
CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier would need
32 K TRAU and the EGPRS carrier would need 64 K TRAU.
68P02900W21-R
8-63
GMR-01
Nov 2007
For this case, it can be calculated that 8 GDS TRAU E1s are required

A PRP board can be assigned up to 120 timeslots but only 30 are serviced (active) at any given
time. The PRP algorithms handle the scheduling of timeslots in an efcient 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:
loading factor
Is:
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.
Partition the load across multiple PCUs

evenly divided.
8-64
68P02900W21-R
GMR-01
Nov 2007

Each PRP board can process 30 active timeslots at any given time for a total of 120 timeslots.
Using the value calculated earlier 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.
Refer to the appropriate section of this chapter for the PCU provisioning rules.
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 signaling trafc increases the BSC LCF GPROC2 processor
load. The BSS planning rule for LCF provisioning in the following equation should be used.
An additional LCF GPROC2 can be added or the GSM circuit-switched provisioning can be
examined to check if an existing LCF GPROC2 can process this additional load.

Hence, 3 Gb links are to be provided.

68P02900W21-R
8-65
GMR-01
Nov 2007

Use the following equation to calculate the number of 64 kbits/s GSL links required. In this
example, the number of users on a PCU is 5000. It assumes that all 20 cells are attached to a
single LCF card in the BSC. 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).
steps and rules for further details on the following equations:
The number of GSL TS for run time is represented by:
The number of GSL required is
Balancing the GSL load across the LCFs

This step is performed either optionally or automatically by the system at sysgen. If it is desired
to perform the operation manually, suggestions are given in the Load balancing on page 6-49
section of Determining the number of GSLs required on page 6-47 in Chapter 6 BSC planning
steps and rules.
8-66
68P02900W21-R
GMR-01
Nov 2007

The following is the required PCU hardware:
6 PRP boards, 8 GDS E1 links (GDS) timeslot balanced across the PRPs.
2 PICP boards, 1 PICP board to process GDS LAPD (GSL) and 1 PICP board to process
the GBL trafc.
1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy).
boards.
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 sufcient 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 3 E1 links are required for the GBL. Each PICP can terminate up to 4
GBL links. Therefore, 3/4 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 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.
Reviewing the GBL and GSL E1 link requirements shows that one PICP is sufcient to process
the link provisioning requirements.
and BTSs
It is assumed that the EGPRS trafc is in addition to the existing circuit-switched trafc and
GPRS trafc already available in the system. In Determining the number of CCCHs at each BTS
cell on page 8-70, it was determined that 8 timeslots would be required for the EGPRS required
on a per BTS site basis, 2 cells per site, in order to carry the GPRS trafc.
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 require 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-143 in Chapter 3 BSS cell planning.
68P02900W21-R
8-67
GMR-01
Nov 2007
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling load
for the EGPRS data trafc with the existing circuit-switched trafc 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 signicant additional control channel load on the RSL. In this case, however,
PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging coordination.
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 GSLs required on page 6-47 in
Chapter 6 BSC planning steps and rules for further details on the following equation.
Perform the GSM RSL calculation with 64 kbit/s RSL to be consistent with the EGPRS
calculation.

The BSC can need additional hardware in order to support the addition of the EGPRS network
trafc. For BSC provisioning, refer to the planning rules given in Chapter 6 BSC planning
steps and rules.
The BSC needs more E1 terminations in support of the additional EGPRS trafc over the BTS to
BSC interface.

{23956}
This example uses the same base call model parameters as those used in BSS - PCU planning
example for EGPRS on page 8-60 except that the QoS feature is enabled. QoS needs new call
model parameters to be specied based on QoS usage.
Refer to BSS - PCU planning example for EGPRS on page 8-60 to compare the
GPRS/EGPRS call model parameters.
Additional data
The QoS feature is enabled.
Add one EGPRS carrier per cell with the following call model:
8-68
68P02900W21-R
GMR-01
Nov 2007
Table 8-16 EGPRS with QoS enabled call model

Item
Value
PKULSIZE=287
PKDLSIZE=701
Trafc per sub/BH (kbytes/hr) - uplink

Trafc per sub/BH (kbytes/hr) downlink
ULRATE=40
PSATT/DETACH=0.78
PDP context activation/deactivation

(per sub/BH)
PDPACT/DEACT=1
RAU=1.1
Routing area update

Cell Updates
CellUpdate=2.86
PGPRS=1.4
250
GPRS/EGPRS users per cell

5
PGSM=0.32

(pages/second)
LCS=0.2
LRMT=0.95

Ratio of mobiles in the system that
are both GSM and GPRS capable
NGSM GPRS MS/NAU MS=100%
Percentage of mobiles that are EGPRS

capable
5%
Number of PCCCH-enabled cells in

the BSS
10
20
I1_MTBR
14
I2_MTBR
10
I3_MTBR
BG_MTBR
BE_MTBR
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%
Continued
68P02900W21-R
8-69
GMR-01
Nov 2007
Table 8-16 EGPRS with QoS enabled call model (Continued)

Item
Value
CS3/4_USAGE
68.25%
EGPRS_USAGE
25%
TRAU TYPE
64
Mobile Class Type
10

BLER is compensated by the PRP board headroom required for QoS. The CS coding schemes are
set as pre-dened values determined by the QoS feature. For GPRS, the maximum rate is 8 K
and for EGPRS the maximum rate is 14 K.

circuit-switched signaling load on the CCCH with paging coordination.
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 Control channel calculations on page 3-119 in
Chapter 3 BSS cell planning.
Determine the number of PCCCHs at each BTS cell

8-70
68P02900W21-R
GMR-01
Nov 2007
be considered.
four.
Determining number of GPRS and EGPRS carrier timeslots at each BTS cell
basis. In order to use this equation, the n expected cell load in kbit/s should be known.
The equation takes into account the amount of local timeslot headroom to allow to the required
MTBR. The mean load factor is set to 0.75 to accommodate peak data scenarios since the mean
trafc load is based on averages. The dened timeslot throughput and the PRP board headroom
allocated by the QoS feature cover the signaling peak periods.
Calculating the number of GDS E1 links

to carry the trafc.
Each CS1/CS2 timeslot needs 16 K TRAU channel.
CS3/CS4 timeslots need 32 K TRAU.
MCS1 through MCS9 need a variable VersaTRAU backhaul in units of 64 K {23769} DS0s
on the GDS TRAU interface.
68P02900W21-R
8-71
GMR-01
Nov 2007
The example here assumes that each EGPRS RTF is equipped with a backhaul of
8 DS0s (rtf_ds0_count = 8).
CS3/CS4 is enabled on a carrier hence all the GPRS timeslots for that carrier would need
32 K TRAU and the EGPRS carrier would need 64 K TRAU.
For this case, it can be calculated that 8 GDS TRAU E1s are required.
If the number of active timeslots exceeds the limit for one PCU, those cells have to be moved to
another BSS. Since the limit is 3360 active timeslots, only one PCU is required.

A PRP board can be assigned up to 120 timeslots but only 30 are serviced (active) at any given
time. The PRP algorithms handle the scheduling of timeslots in an efcient manner dependent
on available resources. The QoS feature provides further guidelines on the number of timeslots
to assign to a PRP to achieve the requested MTBR per subscriber.
PRP board throughput is calculated as follows:
Therefore
Therefore
MAX_QOS_PDTCHS_PER_PRP is calculated as follows:
8-72
68P02900W21-R
GMR-01
Nov 2007
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 provides 8 timeslots of data capacity that is
the required 6. In this example, we have 8 GPRS timeslots congured as switchable or packet
data from the original GPRS carrier and 8 timeslots dened 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.
320 PDTCHs/112 MAX per board = 4 PRP boards.
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.
Partitioning the load across multiple PCUs

evenly divided.

The volume of GPRS and EGPRS signaling trafc increases the BSC LCF {23956} GPROC2
processor load. The BSS planning rule for LCF provisioning in the following equation should be
used.
An additional LCF GPROC2 can be added or the GSM circuit-switched provisioning can be
examined to check whether an existing LCF GPROC2 can process this additional load.
68P02900W21-R
8-73
GMR-01
Nov 2007

Hence, 3 Gb links are required.

Use the following equation to calculate the number of 64 kbit/s GSL links required. In this
example, the number of users on a PCU is 5000. It assumes that all 20 cells are parented to a
single LCF card in the BSC. 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).
steps and rules, for further details on the following equations.
The number of GSL TS for run time is represented by:
The number of GSL required is
Balancing the GSL load across the LCFs

This step is performed either optionally or 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
on page 6-49 section of Determining the number of GSLs required on page 6-47 in Chapter 6
BSC planning steps and rules.
8-74
68P02900W21-R
GMR-01
Nov 2007

The following hardware is required:
4 PRP boards, 8 GDS E1 links (GDS) timeslot balanced across the PRPs.
2 PICP boards, 1 PICP board to process GDS LAPD (GSL) and 1 PICP board to process
the GBL trafc.
1 MPROC board, 1 MPROC board per PCU shelf (2 for redundancy).
boards.
1 PCU cabinet, 1 PCU cabinet per 3 PCU shelves.
After calculating the number of GDS, GBL and GSL E1 links, ensure that there are a sufcient
number of PICP boards to cover the GBL and GSL E1 links. The PCU hardware calculation gives
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 3 E1 links are required for the GBL. Each PICP can terminate up to 4
GBL links. Therefore, 3/4 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). Each
PICP can terminate up to 2 E1 GSL links and up to 60 GSL 64 kbit/s timeslots distributed over
two E1s. 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 that a PMC cannot share a GSL and GBL, a second PICP is
required. The GBL and GSL E1 link requirements show that one PICP is sufcient to process
the link provisioning requirements.
and BTSs
It is assumed that the EGPRS trafc is in addition to the existing circuit-switched trafc and
GPRS trafc already available in the system. 8 timeslots would be required for the EGPRS
timeslot trafc on a per cell basis. Therefore, 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 trafc.
A decision can be made at this stage on how to allocate the EGPRS carrier timeslots. When
EGPRS is 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 require 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 can be
used. Refer to Dynamic timeslot allocation on page 3-143 in Chapter 3 BSS cell planning.
68P02900W21-R
8-75
GMR-01
Nov 2007
For cells without PCCCH (pccch_enabled = 0), the BTS combines the additional signaling
load for the EGPRS data trafc with the existing circuit-switched trafc 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 signicant additional control channel load on the RSL. In this
case, however, PCCCH reduces the GSM circuit-switched signaling load on the RSL with paging
coordination. The new load on the RSL for GPRS is based on the evaluation of the following
equation and other supporting equations.
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 EGPRS calculation.

The BSC can need additional hardware in order to support the addition of the EGPRS network
trafc. For BSC provisioning, refer to the planning rules in Chapter 6 BSC planning steps
and rules.
The BSC needs more E1 terminations in support of the additional E1 links to the PCU and in
support of the additional EGPRS trafc over the BTS to BSC interface. In this example, eight
E1s were added for the GDS links and one E1 added for the GSL link.
8-76
68P02900W21-R
GMR-01
Nov 2007
Chapter
9
Planning exercises
This chapter explains the planning exercises designed to illustrate the use of the rules and
formulae. The tables of required equipment lists only the major Motorola supplied items.
Equipment such as not cable, external power supplies, and air conditioning equipment are not
covered. Refer to the Motorola local ofce for assistance in ensuring that all necessary items
are purchased.
This chapter includes the following sections:
Pre-requisites on page 9-2.
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-11.
Determine the hardware requirements for the RXCDR on page 9-14.
Calculations using alternative call models on page 9-17.
Planning example of BSS support for LCS provisioning on page 9-73.
68P02900W21-R
Nov 2007
9-1
GMR-01
Pre-requisites
Pre-requisites
Requirements
In the area of interest, a demand analysis has identied the requirement for 11 BTSs with the
busy hour Erlang requirement shown in second column 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-116 section of Chapter 3 BSS cell planning, provides the
maximum Erlang capacity for a given number of carriers at 2% blocking. The third column of
Table 9-1 provides the number of carriers (RTFs) required.
If hr (AMR) is used, hr usage needs 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-116
section of Chapter 3 BSS cell planning can be found by reference to standard Erlang B tables for
the equivalent number of trafc channels at the required blocking factor.
Table 9-1
Busy hour demand and number of carriers
BTS identication
Erlangs
Antenna conguration
Omni 2
Omni 2
Omni 1
Omni 2
14
Omni 3
10
Omni 3
Omni 2
Omni 1
Omni 2
20/20/20
Sector 4/4/4
Omni 2
Total
119
32 carriers
9-2
68P02900W21-R
GMR-01
Nov 2007
Network topology
Network topology
Using a frequency-planning tool, assigns adequate frequencies to support the BTS antenna
congurations 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
BS C
OMC-R
BTS K
BTS L
BTS A
BTS E
BTS B
BTS F
BTS C
BTS G
BTS D
BTS H
BTS J
ti-GSM-Network_topology-00145-ai-sw
68P02900W21-R
9-3
GMR-01
Nov 2007
Exercises
Exercises
Introduction
In order to illustrate the planning steps, the individual hardware requirements for BTS B and
BTS K is calculated, followed by the calculation to produce the hardware requirements for the
BSC, and RXCDR. The parameters required for the database generation they are noted.
The calculations for the hardware capacity use the standard call model given in Chapter 3 BSS
cell planning and Chapter 6 BSC planning steps and rules. Half rate usage is not specied
for this exercise.
9-4
68P02900W21-R
GMR-01
Nov 2007
Determine the hardware requirements for BTS B
Determine the hardware requirements for BTS B
From Figure 9-1 and Table 9-1, it can be seen that BTS B needs two RF carriers in an omni
conguration to carry a peak demand of ve 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 ofce if part numbers are required.
Main site number

Contact the Motorola local ofce if part numbers are required.
Interface option
Power redundancy
Duplexing
Only two antennas are used on this site, so we require to specify duplexing. Contact the
Motorola local ofce if part numbers are required.
Digital redundancy
It is not considered that the purpose of this site justies the expense of digital redundancy.
Alarm inputs
More that eight alarm inputs are not required, so nothing is needed here.
Memory
Requirement is to have non-volatile code storage and the ability to download code in background
mode. Contact the Motorola local ofce if part numbers are required.
68P02900W21-R
9-5
GMR-01
Nov 2007
Summary
Database option
Summary
The equipment required and an example of customer order creation for an M-Cell6 indoor (900
MHz) conguration 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?

(RF conguration)
1 2345678
How many cabinets are required for the RF

conguration?
1234
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)
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 or external

rack required?
Yes
No
Are 16-way alarm inputs required?
Yes
No
Is a memory card required?
Yes
No
Continued
9-6
68P02900W21-R
GMR-01
Nov 2007
Summary
Table 9-3 Customer ordering guide 900 MHz (M-Cell6 indoor) (Continued)
Question
Options
Is database required? (Provided by local

ofce)
Yes
No
Is ac battery backup required?
Yes
No
Select ac battery box options?
Yes
No
Is -48 V power supply module (APSM)

required?
Yes
No
Is Comms Power Supply Module (CPSM)

required?
Yes
No
68P02900W21-R
9-7
GMR-01
Nov 2007
Determine the hardware requirements for BTS K
Introduction
From Figure 9-1 and Table 9-1, it can be seen that BTS K needs 12 RF carriers in a 4/4/4 sector
conguration 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 is included in two or three Horizonmacro cabinets.
Alternatively, the site can be included is a better word 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.
Single cabinet Horizon II macro solution

The single cabinet consists of six CTU2 transceivers, operating in pairs and in dual carrier mode
to provide the 3 sector 4/4/4 conguration.
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 conguration. Refer to Chapter 12 Standard
BSS and Horizon BTS congurations for details on conguration.
Two cabinet Horizonmacro solutions

Each cabinet has four carriers of a sector plus two carriers of a shared sector. Two SURF
modules support the four carriers in each sector. The shared sector is supported by
interconnecting the SURF in the master cabinet to the SURF in the extender cabinet.
Three cabinet Horizonmacro solutions

Each cabinet is dedicated to a sector, to support easy expansion.
9-8
68P02900W21-R
GMR-01
Nov 2007
Transmitter combining requirements

A one, two, and three cabinet solution is provided.
Single cabinet Horizon II macro solution

Each sector needs two DUPs, one for each CTU2.
Two cabinet Horizonmacro solutions

Each sector needs two DCF modules. The shared sector has one DCF module in the master
cabinet and the other DCF in the extender cabinet.
Three cabinet Horizonmacro solutions

Each cabinet is dedicated to a sector, which needs one DDF and one HCU modules.
Summary
The equipment required, and an example of customer order creation for a single cabinet
Horizon II macro indoor (1800 MHz) conguration, to implement BTS K is listed in Table 9-4
and Table 9-5.
Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor)
Question
Voltage used
Compulsory
+27 V dc
-48 V/60 V dc
240 V ac
How many cells are

required?
1
2
3
How many carriers are

required per cell? (RF
conguration)
1
2
3
4
5
6
7
8
One carrier (single density)

or two carriers (double
density) required per CTU2?
1
2
How many cabinets are

required for the RF
conguration?
1
2
3
4
Continued
68P02900W21-R
9-9
GMR-01
Nov 2007
Summary
Table 9-4 Customer ordering guide 1800 MHz (Horizon II macro indoor) (Continued)
Question
What type of combining is
required?
Compulsory
DUP and Air
DUP and HCU
DUP and DHU
DUP, HCU and Air DUP,
DHU and Air DUP,
HCU, DHU and Air
What line interface is

required?
T43 (E1) (75 ohm)

BIB (E1) (120 ohm)
Table 9-5 Customer ordering guide 1800 MHz (Horizon II macro indoor)
Questions
Options
Is digital redundancy required?
Yes
No
Is power redundancy required?
Yes
No
Is an extra line interface required?
Yes
No
Are 16-way alarm inputs required?
Yes
No
Is a compact ash (memory) card required?
Yes
No
Is a stacking bracket required?
Yes
No
Is battery backup required?
Yes
No
Is database required? (Provided by local

ofce)
Yes
No
9-10
68P02900W21-R
GMR-01
Nov 2007
Determine the hardware requirements for the BSC
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 table shows that 119 Erlangs at 1% blocking needs 138 trafc
channels. One OML link, one XBL link and one C7 signaling link are required. The number of
trunks required is given by:
[(1+1)+(1+1)+(1+1)+(138/4)]/31=1.3
Transcoder requirement
None required, remote transcoding.
MSI requirement
Minimum number of MSIs required is given by:
(4+2)/2=3
Line interface
Depending on the interface standard used, one BIB or one T43 is sufcient for three MSIs.
GPROC requirement
GPROC function requirements are listed in Table 9-6.
Table 9-6 GPROCs required at the BSC

Function
Number required
BSP
1 (GPROC3)
LCFs for MTLs
LCFs for RSLs
1
Continued
68P02900W21-R
9-11
GMR-01
Nov 2007
Introduction
Table 9-6 GPROCs required at the BSC (Continued)

Function
Number required
Optional GPROC requirements

Redundant BSP (GPROC3), CSFP
Redundant LCP
Total GPROC3s
1+1
Total GPROC2s/GPROC3s
2+1
The notation n + m means that n is the items required and m the 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
None
XCDR
MSI
3*64 = 192
352
Total timeslots
Therefore, the BSC can be accommodated in one BSU shelf and one KSW/DSW2 is required.
KSWX/DSWX requirement
The BSC is included 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 included 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.
9-12
68P02900W21-R
GMR-01
Nov 2007
Summary
LANX requirement
An adequate number of LANXs are provided for non-redundant operation. A redundant LAN
needs 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 is 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
BSU shelf
MSI
BIB or T43
GPROC3
1+1
GPROC2/GPROC3
2+1
KSW/DSW2
1+1
GCLK
1+1
PIX (provides up to 8 external alarms)
LANX
1
2+1
EPSM/IPSM (+27 V) (-48 V)
The notation n + m means that n the items required plus m the redundancy.
68P02900W21-R
9-13
GMR-01
Nov 2007
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
trafc connection comes directly from the transcoder card.
Links to the BSC

From the calculation in the previous section BSC to MSC links on page 9-11, it can be seen
that there are two links to the BSC.
Links to the OMC-R

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

Three E1 links are required.
The number of MSI cards is given by:
3/ 2 =1.5
This value should be rounded off to 2.
Transcoder requirement
From the calculation in the previous section BSC to MSC links on page 9-11, it can be seen that
138 trafc channels and two C7 links are required. The number of transcoder cards is given by:
138/30 = 5
A GDP2 can transcode 60 channels and if used exclusively is determined by:
138/60 = 3
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 are mixed within a
shelf.
9-14
68P02900W21-R
GMR-01
Nov 2007
Link interface
The GDP2 needs that the RXU3 shelf be used. The BSSC3 cabinet with two RXU3 shelves can
interface up to 76 E1/T1 links. The BSSC2 cabinet can interface only up to 48 E1/T1 link.
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 ve E1 links are
required. A total of eight E1 links are required.
The number of BIB/T43s is given by:
8/6 =1.3
This value should be rounded off to 2.
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:
2 *16 + 5*16 + 2 * 64 = 240
One KSW/DSW2 is required, plus one for redundancy.
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.
68P02900W21-R
9-15
GMR-01
Nov 2007
PIX requirement
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
needs 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 is required.
Summary
The equipment required to implement the RXCDR is listed in Table 9-9.
Table 9-9 Equipment required for the RXCDR

Equipment
Number required
BSSC2 or BSSC3 cabinet
RXU or RXU3 shelf
MSI
XCDR/GDP-E1
BIB or T43
GPROC2/GPROC3
1+1
KSW or DSW2
1+1
GCLK
1+1
PIX (provides up to 8 external alarms)
LANX
1
2+1
EPSM/IPSM (+27 V) (-48 V)
The notation n + m means that n the items required plus m the redundancy.
9-16
68P02900W21-R
GMR-01
Nov 2007
Calculations using alternative call models
Calculations using alternative call models
Introduction
This section is provided to assist the 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 is not correct and the actual values require
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. The 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
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
Number 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%
68P02900W21-R
9-17
GMR-01
Nov 2007
Planning example 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
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 conguration
IMSI/TMSI paging = TMSI
MTL load balancing granularity = 16
GSR6 (Horizon II) limitations
Maximum BTS sites = 100
Maximum BTS cells = 250
Active RF carriers = 512
Trunks = 3000
C7 links = 16
9-18
68P02900W21-R
GMR-01
Nov 2007
Planning example 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 Erlang
4-carrier cell - determining the number of CCCHs
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 utilization gure, 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.
68P02900W21-R
9-19
GMR-01
Nov 2007
Planning example 1
4 carrier cell - determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the
average number of SDCCHs and NSDCCH is given by formulae detailed in Chapter 3 BSS
cell planning as:
To support an average number of busy SDCCHs of 7.211 with less than 1% blocking is 14 as
determined by use of Erlang B tables. Hence, the number of timeslots required to carry SDCCH
signaling trafc is two, with each timeslot offering 8 SDCCHs.
4-carrier cell - determining the number of TCHs
The total number of signaling timeslots required for a 4-carrier conguration with the given
call model parameters is three (1 non-combined BCCH timeslot with 9 CCCHs and 2 timeslots
with 8 SDCCHs each).
Hence, the number of trafc channels per 4 carrier cell = 32 - 3 = 29.
Omni 2 cell - determining the number of CCCHs
Call arrival rate:
SMS Rate:
From the call model parameters paging rate PGSM is 10, so the average number of CCCH
9-20
68P02900W21-R
GMR-01
Nov 2007
Planning example 1
Using a CCCH utilization gure, UCCCH of 0.33, the average number of CCCH blocks required
supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve 2
CCCH block for access grant messages.
Omni 2 cell - determine the number of SDCCHs per cell
Using the values calculated in the previous section and other call model parameters, the average
number of SDCCHs, NSDCCH is given by formula detailed in Chapter 3 BSS cell planning:
The number of SDCCHs to support an average number of busy SDCCHs of 2.988 with less
than 1% blocking as determined by use of Erlang B tables is approximately 8. The number of
timeslots required to carry SDCCH signaling trafc is 1.
Omni 2 cell - determining the number of TCHs
The total number of signaling timeslots required for a 4-carrier conguration with the given
call model parameters is three (1 non-combined timeslot BCCH with 9 CCCHs and 2 timeslots
with 8 SDCCHs each).
Therefore, the number of trafc channels per 2 carrier cell = 16 - 2 = 14
Hence, trafc 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.
BSS planning - determining the number of RSLs

The number of 64 kbit/s RSLs required is given by:
Where, n is the number of TCHs under the BTS. Hence, for a 4/4/4 site (no GPRS):
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).
68P02900W21-R
9-21
GMR-01
Nov 2007
Planning example 1
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).

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 is given by:
Hence, only one E1 interconnection is required between each BTS and BSC for the given site
congurations (provided they are in star congurations), 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, 4/4/4 conguration and 2 omni 2 site.
= 283* 21.04 + 2 *8.04 = 1784 Erlangs
Total Erlangs carried by the BSC with 28 sites, 4/4/4 conguration and 2 omni 2 site.
= 28*3* 20.62 + 2*8.04 =1748 Erlangs
The number of trunks required to carry trafc on the A-Interface with less than 1% blocking is
1812; check that the gure is within limits.
Number of pages per call is given by:
9-22
68P02900W21-R
GMR-01
Nov 2007
Planning example 1
Using the call model parameters, the number of MTLs can be calculated using formulae detailed
in Chapter 6 BSC planning steps and rules.
Maximum number of Erlangs supported by a C7 link is given by:
Maximum number of Erlangs supported by a GPROC supporting a C7 signaling link is given by:
= 560 Erlangs
Hence:
Amount of trafc (or number of trunks) each logical link holds:
Using a MTL load-sharing granularity of 16, the number of logical links each MTL can handle:
The number of required MTLs are given by:
Check that the gure is within limits.
68P02900W21-R
9-23
GMR-01
Nov 2007
Planning example 1
Determining the number of LCFs for MTL processing

Using the formula detailed in Chapter 6 BSC planning steps and rules, since:
XBL requirements
Refer 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 gure 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 needs 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
Number of TDM timeslots is given by:
N = (G * n) + (M*64) = (R *16)
Where G is the number of GPROCs; M is the number of MSIs, and R is the number of
XCDR/GDPs at the BSC.
N = 17 *32 + 23* 64 = 2016
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 2 non-redundant KSWs/DSW2s are
required for this conguration. For redundancy, an additional 2 KSWs/DSW2s are required.
Total KSWs/DSW2s required (with redundancy) = 4
9-24
68P02900W21-R
GMR-01
Nov 2007
Planning example 1
BSU shelves
The number of BSU shelves required is the greater of the two calculations (since we have
no local transcoding):
Ensure that the following is true for each shelf.

N + (G * n) + (M*64) + (R *16) 1016
Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this
conguration.
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 conguration. The KSWX/DSWX can be used in expansion,
remote and local modes. We need 3 BSU shelves with 2 non-redundant KSWs/DSW2s, which
implies that we have 1 expansion shelf and 1 extension shelf.
Number of KSWXs/DSWXs required is sum of the 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
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.
68P02900W21-R
9-25
GMR-01
Nov 2007
Planning example 1
The number of CLKXs required (with redundancy) = 2

LANX requirements
Where RF is the redundancy factor.

Total number of LANXs required (with redundancy) = 6
PIX requirements
PIX provides eight inputs and four outputs for site alarms.
PIX 2* Number of BSUs = 6
Line interfaces
Number of T43s = Number of MSIs/3 = 23/3 ~ 8
The number of T43 boards required is 8.
Digital power supply requirements
Number of PSUs required is given by:
One redundant PSU is required for each BSU shelf, hence, the total number of PSUs required
is 12.
Non Volatile Memory (NVM) board for BSC (optional).
NVM = 0 or 1
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
signaling trafc and voice trafc 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:
9-26
68P02900W21-R
GMR-01
Nov 2007
Planning example 1
Where:
Is:
number of MTL links required.
number of OML links required.
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 (assuming that NVM board is tted).
Ensure the following is true for each shelf:
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 is required.
KSW/DSW2 requirements for RXCDR
The number of TDM slots required for GPROCs, MSIs and XCDRs is given by:
TDM timeslots required = G* n + R *16 +M*64
TDM timeslots required = 8*32 + 8*64 + 60*16 =1728
Each KSW/DSW2 provides 1016 timeslots on the TDM highway, hence, 2 non-redundant
KSWs/DSW2s are required for the RXCDR with this conguration.
68P02900W21-R
9-27
GMR-01
Nov 2007
Planning example 1
KSWX/DSWX requirements for RXCDR

The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. We need 4
RXU shelves with 2 non-redundant KSWs/DSW2s, which implies that there is 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:
Is:
number of expansion/extension shelves.
RF
the redundancy factor.
The number of redundant CLKXs required is 2.
9-28
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
LANX requirements
Number of LANXs required is given by:

Total number of LANXs required with redundancy = 8
PIX requirements
PIX 2* Number of RXUs = 8
Hence, 8 PIX cards are required for the RXCDRs.
Line interfaces
Number of T43s = Number of E1s/6 = (60 +15)/6 ~ 13
PSUs = 2*RXUs = 8
One redundant PSU is required for each RXU shelf, hence, total number of PSUs required is 12.
Non-volatile memory (NVM) board for RXCDR (optional)
NVM =1 (in this example)
Planning example 2
Dimension a network with the following requirements:
GSM software release = GSR6 (Horizon II)
Number of omni 2 sites (BTS: M-Cell2) = 5
68P02900W21-R
9-29
GMR-01
Nov 2007
Planning example 2
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
Number 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
9-30
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
Type of combining used = Hybrid (CBF)
BTS connectivity = Star conguration
NVM board tted at RXCDR
GSR6 (Horizon II) limitations
Trunks = 3000
C7 links = 16
68P02900W21-R
9-31
GMR-01
Nov 2007
Planning example 2

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
Call arrival rate:
SMS Rate:
From the call model parameters, the paging rate PGSM is 8, so the average number of CCCH
Using a CCCH utilization gure (UCCCH) of 0.33, the average number of CCCH blocks required
supported using a non-combined BCCH with 9 CCCH timeslots. It is recommended to reserve
3 CCCH blocks for access grant messages.
9-32
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
4 carrier cell - determine the number of SDCCHs per cell

Using the values calculated in the previous section and other call model parameters, the average
number of SDCCHs, NSDCCH, is given by the formula mentioned in Chapter 3 BSS cell planning:
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 signaling trafc is 1, with the timeslot offering 8, SDCCHs.
Determining the number of TCHs
Total number of signaling timeslots required for a 2-carrier conguration with the given call
model parameters is two (1 non-combined BCCH timeslot with 9 CCCHs and 1 timeslot with 8
SDCCHs each).
Therefore, the number of trafc channels per 2 carrier cell = 16 2 = 14.
Hence, trafc offered by a 2-carrier cell is 8.2 Erlangs (14 channels at 2 % GOS). Carried
Erlangs for the cells is 8.04 Erlangs.
BSS planning - determining the number of RSLs

Where, n is the number of TCHs under the BTS. Hence, for a 2/2/2 site (no GPRS):
For both 2/2/2 site and an omni 2 site, the number of RSLs required is one.
{23769}
(CS3 and CS4 are not used)

68P02900W21-R
9-33
GMR-01
Nov 2007
Planning example 2
Number of E1 links required between each omni 2 BTS and BSC is given by:
Hence, only one E1 interconnect is required between each BTS and BSC for the given site
congurations (provided they are in star congurations), giving a total of 60 E1 links.
The number of LCFs for RSL processing is 6.

Total Erlangs offered by the BSC with 55 sites, 2/2/2 conguration and 5 omni 2 sites:
=55*3*8.2+5*8.2=1394 Erlangs
Total Erlangs carried by the BSC with 55 sites, 2/2/2 conguration and 5 omni 2 site:
=55*3*8.04+5*8.04=1366.8 Erlangs
1423. Check gure is within limits.
Number of pages per call is calculated by using the following formula:
Using the call model parameters, the number of MTLs can be calculated using formulae detailed
in Chapter 6 BSC planning steps and rules.
9-34
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
Maximum number of Erlangs supported by a GPROC supporting a C7 signaling link is given by:
Hence:
Amount of trafc (or number of trunks) each logical link can hold is given by:
using a MTL load-sharing granularity of 64.

The number of logical links each MTL can handle is given by:
The number of required MTLs:
Check this gure is within limits.

Using the formula mentioned 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 = 4
Number of GPROCs required for RSL processing = 5
68P02900W21-R
9-35
GMR-01
Nov 2007
Planning example 2
Total number of LCF GPROCs required = 9 (Check this gure 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)
MSI requirements
Each MSI interfaces two E1 links.
Number of E1 links required at the BSC for interconnecting with the RXCDR and without
redundancy is:
(8 + 2 + 2 + 1423/4)/31 ~ 12
Hence, the number of MSIs required for BSC to RXCDR interface = 6.
Each BTS site in this example needs one E1 interconnect. Hence, the number of MSIs required
for BTSs is 60/2 = 30.
Total number of MSIs required at the BSC = 36.
Number of TDM timeslots is given by:
N = (G * n) + (M * 64) + (R * 16)
Where:
Is:
the number of MSIs.
the number of GDP/XCDRs in the BSC.
N = 13 * 32 + 36 * 64 = 2720
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s is
required for this conguration. 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):

N + (G *n) + (M * 64) + (R * 16) 1016
Therefore, 3 BSU shelves are required to accommodate all the hardware needed for this
conguration.
9-36
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
to all shelves in the multi-shelf conguration. The KSWX/DSWX is used in expansion, remote
and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which implies
2 expansion shelves.
Number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL:

NKXL = K + SE = 3
NKX = 6 + 0 + 3 = 9
The number of KSWXs/DSWXs required (with redundancy) = 18
GCLK requirements
CLKX requirements
Provides expansion of GCLK timing to more than one BSU. Number of CLKXs required is
given by:

LANX requirements

PIX requirements
PIX provides eight inputs and four outputs for site alarms:
PIX 2* Number of BSUs = 6
Line interfaces
Number of T43s = Number of MSIs/3 = 36/3 ~ 12
68P02900W21-R
9-37
GMR-01
Nov 2007
Planning example 2

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)
NVM = 0 or 1
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
signaling trafc and voice trafc 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.
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.
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.
9-38
68P02900W21-R
GMR-01
Nov 2007
Planning example 2
RXU shelves
The number of RXU shelves required is given by (assumes an NVM board is tted):
Ensure the following is true for each shelf:

N + (G * n) + (M * 64) + (R * 16) 1016
Hence, 3 RXU shelves are required to equip 47 XCDR cards and 6 MSI cards.
If the operator chooses to use redundancy, 6 GPROCs are required.
Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by:
TDM timeslots required = G * n + M * 64 + R * 16
TDM timeslots required = 6 * 32 + 6 * 64 + 47 * 16 = 1328
KSWs/DSW2s are required for RXCDR with this conguration.
The number of KSWXs/DSWXs required is the sum of KSWXE, KSWXR, and KSWXL. The
calculations imply that 1 expansion and 1 extension shelf are required.
The number of KSWXs/DSWXs (with redundancy) = 12
68P02900W21-R
9-39
GMR-01
Nov 2007
Planning example 2
GCLK requirements
The generic clock generates all the timing reference signals required by a RXU. One GLCK is
CLKX requirements
Provides expansion of GCLK timing to more than one RXU:
Where:
Is:
RF
The number of redundant CLKXs required is 2.

LANX requirements
Where RF it the redundancy factor.

PIX requirements
PIX 2 * Number of RXUs = 6
Hence, 6 PIX cards are required for RXCDR.
Line interfaces
Number of T43s = Number of E1s/6 = (47 + 12)/6 ~ 10
PSUs = 2 * RXUs = 6
One redundant PSU is required for each RXU shelf, hence, the total number of PSUs required is
9.
NVM =1 (in this example)
9-40
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
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
68P02900W21-R
9-41
GMR-01
Nov 2007
Planning example 3
NVM board tted 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.
Call arrival rate:
SMS Rate:
9-42
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
From the call model parameters, the paging rate P is 8, so the average number of CCCH blocks
required to support paging only is:
Determining the number of SDCCHs per cell
average number of SDCCHs and NSDCCH is given by the formula mentioned in Chapter 3
BSS cell planning.
To support an average number of busy SDCCHs of 8.126 Erlangs signaling trafc with less that
1% blocking is 14 as determined by use of Erlang B tables. Hence, the number of timeslots
required to carry SDCCH signaling trafc is 2, with each timeslot offering maximum 8 SDCCHs.
Total number of signaling timeslots required for a 6-carrier conguration, with the given call
model parameters is 3 (1 non-combined BCCH timeslot with 9 CCCHs and 2 timeslots with 8
SDCCHs each).
Therefore, the number of trafc channels per 6 carrier cell = 48 - 3 = 45.
Hence, trafc offered by a 6-carrier cell is 35.61 Erlangs (45 trafc channels at 2% GOS).
Carried Erlangs is 34.90 Erlangs.
Total channels/carrier = 48
68P02900W21-R
9-43
GMR-01
Nov 2007
Planning example 3
Total trafc channels (voice) = 45

Control/signaling channels = 3
BSS planning
The major steps for planning the BSC system include:
The number of RSL links between the BSC and BTSs
The number of E1 links between BSC and BTSs
The number of LCFs for RSL processing
The number of MTL links between BSC and MSC
The number of LCFs for MTL processing
The number of XBL links between BSC and RXCDR
The number of GSL links between BSC and RXCDR
The number of GPROCs
The number of XCDR/GDP/GDP2s
The number of MSI cards
The number of KSWs/DSW2s
The number of BSU shelves
The number of KSWXs/DSWXs
The number of GCLKs
The number of CLKXs
The number of LANXs
The number of PIXs
The number of line interface cards (T43s)
The number of digital power supplies
Whether or not an optional NVM board is tted
9-44
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
RSL requirements
Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (no GPRS):
= Roundup (1.351)
The number of RSLs required per 6/6/6 site is 2.
{23769}
Number of E1 links required between each 6/6/6 BTS and BSC is given by:
Hence, 2 E1 interconnections are required between each BTS and BSC for the given site
congurations (provided they are in star congurations). There are total of 20 * 2 = 40 E1
links needed.
The number of E1s between the BSC and BTS is 40.

Total Erlangs offered by the BSC with 20 sites and 6/6/6 conguration is given by:
68P02900W21-R
9-45
GMR-01
Nov 2007
Planning example 3
20 * 3 * 35.61 = 2136.6 Erlangs

Total Erlangs carried by the BSC with 20 sites and 6/6/6 conguration is given by:
20 * 3 * 34.40 = 2094 Erlangs
2165 (using offered Erlangs to calculate). Verify that this gure is within limits (< 3200 for a
big BSC system). Number of pages per call:
Using the call model parameters, the number of MTLs can be calculated using formulae
mentioned in Chapter 6 BSC planning steps and rules of this manual.
Maximum number of Erlangs supported by GPROC supporting a C7 signaling link is given by:
Hence:
Amount of trafc each logical link holds:

The number of logical links each MTL can handle:
9-46
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
The number of required MTLs.
Check this gure is within limits (<16).

The number of MTLs required = 9
Using the formula mentioned 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 (using N = 2165)
GSL requirements
N/A (signaling links between BSC and PCU).
GPROC requirements
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
XCDR/GDP/GDP2 requirements
N/A (no local RXCDR).
68P02900W21-R
9-47
GMR-01
Nov 2007
Planning example 3
MSI requirements
NMSI = Number of MSIs required.

NBSC-RXCDR = Number of E1 links required.
Number of E1 links required at the BSC for interconnecting with the RXCDR is:
~ 18
PHR in the 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 needs 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
Determine the number of KSWs/DSW2s (N) required by using the following formula:
Where:
Is:
16 or 32 (16 in this example).
RGDP2
M
N/A in this example (RXCDR case).

the number of MSIs (29).
RGDPXCDR and REGDP are not considered in the equation.

Therefore, the total number of timeslots required is:
12 * 16 + 29 * 64 = 2048
9-48
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
Each KSW/DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant KSWs/ DSW2s are
required for this conguration. For redundancy, 3 additional KSWs/ DSW2s are required.
Thus total KSWs/DSW2s required (with redundancy) = 3 + 3 = 6
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 as follows:
Roundup (29/12) = 3 BSU shelves
Total GPROCs = 12 and total MSIs = 29, split between 3 BSU shelves.
Table 9-10
BSU Shelves
BSU 1
BSU 2
BSU 3
Check
Limit
< = 8
12
< = 12
GPROCs
MSI cards

(G * n) + (M * 64) + (R * 16) 1016
That is,
(4 * 16) + (12 * 64) + (0 * 16) 1016
Therefore, the number of BSU shelves required to accommodate all the hardware needed
for this conguration is NBSU = 3.
KSWXs/DSWXs should be considered for this example as the conguration needs more than
one shelf.
to all shelves in the multi-shelf conguration. The KSWX/DSWX can be used in expansion,
remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which
implies that 2 expansion shelves are required.
The number of KSWXs/DSWXs required (NKX) is the sum of KSWXDSWXE, KSWX/DSWXR, and
KSWX/DSWXL:

NKXL = K + SE = 3
NKX = 6 + 0 + 3 = 9
68P02900W21-R
9-49
GMR-01
Nov 2007
Planning example 3
The maximum number of KSWX/DXWX slots per shelf 18.
KSWXs and DSWXs can be used together in a shelf, provided that they are used
with like pairs, KSWX is connected to KSWX and DSWX connected to DSWX.
GCLK requirements
The number of GCLKs required (with redundancy) = 2
CLKX requirements
given by:

LANX requirements

PIX requirements
PIX Number of BSUs = 6
Line interfaces
Number of T43s = Roundup (Number of MSIs/3)
Number of T43s = 29/3 ~10
9-50
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
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.

NVM = 0 or 1
An NVM board is required in this example, so NVM = 1.
RXCDR planning
The following planning steps are performed for this example:
The number of links between the RXCDR and BSC
The number of E1 links between the RXCDR and MSC
The number of XCDR/GDP2/GDP2s
The number of MSIs
The number of RXU shelves
The number of GCLKs
The number of CLKXs
The number of LANXs
The number of PIXs
The number of line interface boards (T43s)
The number of digital power supply units
Determining the number of E1 links between the RXCDR and BSC

Number of RXCDR to BSC links is given by:
68P02900W21-R
9-51
GMR-01
Nov 2007
Planning example 3
Determining the number of E1 links between the RXCDR and MSC

Where:
Is:
the number of MTL links required.
the number of OML links required.
the number of trunks between MSC and BSC.
The number of E1 links between the RXCDR and MSC = 71

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
If the operator chooses to use redundancy, 10 GPROCs are required.
The number of GPROCs required for RXCDR = 5 + 5 (for redundancy) = 10
interfaces 2 E1 links, hence, 9 MSI cards are required on the RXCDR.
MSI requirements for RXCDR = 9
Number of TDM slots required for the GPROCs, MSIs and XCDRs is given by:
TDM timeslots required = G * n + M * 64 + R * 16
TDM timeslots required = 12 * 32 + 9 * 64 + 71 * 16 = 2096
KSWs/DSW2s are required for RXCDR with this conguration.
KSWs/DSW2s required for the RXCDR = 3 + 3 (redundant) = 6
9-52
68P02900W21-R
GMR-01
Nov 2007
Planning example 3
RXU shelves
The number of RXU shelves required is given by (assuming that an NVM board is tted):
Table 9-11 RXU shelves

RXU 1
RXU 2
RXU 3
RXU 4
RXU 5
MSIS
XCDRs/GDPs
GDP2s
GPROCs
Ensure that the following holds good for each shelf.

N + (G * n) + (M * 64) + (R * 16) 1016
Hence, 5 RXU shelves are required to equip 71 XCDR/GDP/GDP2 cards and 9 MSI cards.
The number of RXU shelves required = 5
The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and
KSWX/DSWXL. The calculations imply 2 expansion and 2 extension shelves are required.
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26
KSWXs and DSWXs are used together in a shelf, provided that they are used with like
pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.
68P02900W21-R
9-53
GMR-01
Nov 2007
Planning example 3
GCLK requirements
The generic clock generates all the timing reference signals required by an RXU. One GLCK is
Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements
Provides expansion of GCLK timing to more than one RXU:
Where:
Is:
RF
The number of CLKXs required = 1 + 1 (redundant) = 2

LANX requirements

PIX requirements
PIX 2 * Number of RXUs = 2 * 5 = 10
Hence, 10 PIX cards are required for the RXCDR.
Line interfaces
Number of T43s = Number of E1s/6 = (18 +71)/6 ~ 15
The number of T43 boards required = 15
PSUs = 2 * RXUs + RF * RXUs = 2 * 5 + 1 * 5 = 15
One redundant PSU is required for each RXU shelf, hence, the total number of PSUs required
= 15.
NVM = 1 (required in this example)
9-54
68P02900W21-R
GMR-01
Nov 2007
Planning example 4 (using AMR)

GSM software release = GSR 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 trafc supported AMR hr
GPROC3 is mandatory for the BSP
GDP2 is considered to support AMR hr
New RXCDR shelf is mandatory
No local XCDR
8 K/16 K switching is used, (needs DSW2 support)
No enhanced capacity mode support
No GPRS in the system
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-55
GMR-01
Nov 2007
NVM board tted at BSC and RXCDR
GSR 8 limitations (assuming big BSC system)
Trunks = 3200
C7 links = 16
9-56
68P02900W21-R
GMR-01
Nov 2007
Cell planning - control channel calculations (based on Erlang B models)

Table 9-12 Control channel calculation
All full rate
AMR (hr) Carrier
Total
Carriers
AMR HR/
Carriers
Total
TCH
Signaling
/ Control
TCH
Total
Voice
TCH
Total
TCH
Signaling
/Control
TCH
Total
Voice
TCH
AMR
HR TCH
AMR
HR
TCH
%
1 / 6
48
45
56
53
16
30.2
2 / 6
48
45
64
60
32
53.3
3 / 6
48
45
72
68
48
70.6
4 / 6
48
45
80
76
64
84.2
5 / 6
48
45
-88
-4
-84
-80
95.2
6 / 6
48
45
96
88
88
100
For planning purposes, it is assumed that the AMR-capable MSs uses AMR FR channels, and
that hr is used under conditions of congestion. The estimated AMR penetration rate is 35%, of
which half of those calls are 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, it is 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 can be assumed for the remainder of this exercise.
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 support paging only is given
68P02900W21-R
9-57
GMR-01
Nov 2007
Determining the number of SDCCHs per cell
average number of SDCCHs and NSDCCH is given by the formula mentioned in Chapter 3 BSS cell
planning.
To support an average number of busy SDCCHs of 11.31 Erlangs signaling trafc with less than
1% blocking is 18 as determined by use of Erlang B tables. Hence, the number of timeslots
required to carry SDCCH signaling trafc is 3, with each timeslot offering a maximum of 8
SDCCHs.
Total number of signaling timeslots required for a 6-carrier conguration, with the given call
model parameters is 4 (1 non-combined BCCH timeslot with 9 CCCHs and 3 timeslots with 8
SDCCHs each).
Therefore, the number of trafc channels per 6 carrier cell (4 fr carriers + 2 hr carriers)
= 4 * 8 + 16 * 2 - 4 = 60
Hence, trafc offered by a 6-carrier cell is 49.64 Erlangs (60 trafc channels at 2% GOS).
Carried Erlangs is
49.64 * 98% = 48.65 Erlangs.
Total Erlangs offered by the BSC with 20 sites, and 6/6/6 conguration is given by:
20 * 3 * 49.64 = 2978.4 Erlangs
Total Erlangs carried by the BSC with 20 sites, and 6/6/6 conguration is given by:
20* 3 * 48.65 = 2919 Erlangs
3003. Check this is within the limit of <=3200.
If the number of trunks (3003) exceeds the limit by a small number, (less than a quarter of a
percent or so) it can be considered negligible and planning can continue. However, there is an
alternative approach, particularly for the half rate usage, which is discussed here. In fact, we
can assume that the trunk limit was 3000 in order to provide a working example.
9-58
68P02900W21-R
GMR-01
Nov 2007
The carried Erlangs were calculated for worst case planning. It is assumed that all AMR half
rate enabled carriers would, at worst case, be handling all AMR half rate calls. However, given
that the AMR-capable mobile penetration is 35%, it is unlikely that all the AMR half rate enabled
carriers are carrying all halfrate trafc. 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 can carry 14 HR calls and 1
FR call. This results the following:
1 HR carrier = 16 AMR HR TCH = 14 AMR HR TCH + 1 FR TCH = 15 TCH
The total number of AMR voice TCH = 4 * 8 + 1 * 16 + 14 TCH + 1 - 4 = 59
The trafc offered by a 6 carrier/cell is (based on 59 TCH with 2% of GOS) = 48.70 Erlangs
Carried Erlangs by such system conguration (per BTS) = 48.70 *98% = 47.73 Erlangs
Total Erlangs carried by the BSC with 20 sites, and 6/6/6 conguration is given:
20 * 3 * 48.70 = 2922 Erlangs
2946.
This alternatively calculated number (2946) can be used for the remainder of the calculations
in this section.
# of sites (BTS) per BSC:
20
# of cells per BTS:
# of carriers per cell:
# TCHs per carrier:
63 (AMR HR, AMR FR, GSM FR/EFR, and so on)
# Control channels per carrier:
# 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 trafc:
(using Erlangs B calculation) 2946
68P02900W21-R
9-59
GMR-01
Nov 2007
BSS planning
The major steps for planning the BSC system include:
The number of RSL links between the BSC and BTSs
The number of E1 links between BSC and BTSs
The number of LCFs for RSL processing
The number of MTL links between BSC and MSC
The number of LCFs for MTL processing
The number of XBL links between BSC and RXCDR
The number of GSL links between BSC and RXCDR
The number of XCDR/GDP/GDP2s
The number of MSI cards
The number of BSU shelves
The number of GCLKs
The number of CLKXs
The number of LANXs
The number of PIXs
The number of line interface cards (T43s)
The number of digital power supplies
9-60
68P02900W21-R
GMR-01
Nov 2007
RSL requirements
Where n is the number of TCHs under the BTS. Hence, for a 6/6/6 site (with AMR but no GPRS):
= Roundup (1.70)
The number of RSLs required per 6/6/6 site (with 2 carriers of AMR HR) = 2
{23769}

= [((0*8)+(6*4)+(12*2)+(0/4))/31] ~ 1.61
Hence, two E1 interconnections are required between each BTS and BSC for the given site
congurations (provided they are in star congurations). Thus, a total of 20*2=40 E1 links are
required.
The number of E1s between the BSC and BTS is 40.
Number of LCF-RSLs required, assuming only GPROC3s are used, is given by:

Total Erlangs carried by the BSC with 20 sites, and 6/6/6 conguration is given by:
=20*3*48.70=2922 Erlangs
2946.
68P02900W21-R
9-61
GMR-01
Nov 2007
Number of pages per call is given by:
Using the call model parameters, the number of MTLs can be calculated using formulae
mentioned in Chapter 6 BSC planning steps and rules of this manual.
Maximum number of Erlangs supported by a GPROC3 supporting a C7 signaling link is given by:
= 1393.1Erlangs
Hence, for GPROC3 only:
n1min=min (nLINK, n1LCF-MTL-GPROC3) = 312 Erlangs
Amount of trafc each logical link can hold is given by:

The number of logical links each MTL can handle:
The number of required MTLs:

mtls = roundup (16/2)+R = 9
Check this gure is within limits (<12).
The number of MTLs required = 9
9-62
68P02900W21-R
GMR-01
Nov 2007
If GPROC3s are used exclusively:
The number of LCFs for MTL processing = 3

XBL requirements
The required number of XBLs is given by:
XBM = [{(N/T)* (Mnewcall+Mhandovers+Hfr-hr)*LXBL*8}/(64000*UBSC-RXCDR)]
Referring to Table 6-10 in Chapter 6 BSC planning steps and rules,
Number of 64 kbit/s XBLs required = 3 (6 with redundancy)
GSL requirements
N/A (signaling links between BSC and PCU is not considered in this example).
GPROC3 requirements
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 = 3
C = Number of CSFP GPROCs (optional) = 1
R = Number of pool GPROCs (for redundancy) = 1
Total number of GPROC3s (exclusively) for BSC = (2 * 3 + 3 +1 + 1) = 11
XCDR/GDP/GDP2 requirements
N/A (no local RXCDR).
MSI requirements
68P02900W21-R
9-63
GMR-01
Nov 2007
NMSI = Number of MSIs required.

NBSC-RXCDR = Number of E1 links required.
Number of E1 links required at the BSC for interconnecting with the RXCDR is:
Hence the number of MSIs required for the BSC to RXCDR interface is 25/2 = 13.
Each BTS site in this example needs two E1 interconnections. Hence, the number of MSIs
required for BTSs is 20 * 2 / 2 = 20.
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
9-64
68P02900W21-R
GMR-01
Nov 2007
DSW2 requirements
Extended subrate switching mode (8 kbit/s switching) is required, so DSW2s are used.
Determine the number of DSW2s (N) required:
Where:
Is:
the number of GPROCs (11).
16 or 32 (16 in this example).
RGDPXCDR
N/A in this example.
REGDP
RGDP2
the number of MSIs (33).
Therefore the total number of timeslots required is:

11*16+33*64 = 2288
Each DSW2 provides 1016 TDM timeslots. Hence, 3 non-redundant DSW2s are required for this
conguration. For redundancy, 3 additional DSW2s are required.
Thus, total DSW2s required = 3 + 3 (redundant) = 6.
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.
Roundup (33/12) = 3BSU shelves
Total GPROC3s = 11 and total MSIs = 33, split between 3 BSU shelves
Table 9-13
GPROCs
MSI cards
BSU Shelves
BSU 1
BSU 2
BSU 3
Check Limit
< = 8
11
11
11
< = 12
Ensure that the following is true for each shelf:

(G*n) + (M*64) + (R*16) 1016
That is,
(4*16) + (12*64) + (0*16) 1016
Therefore, the number of BSU shelves required to accommodate all the hardware needed
for this conguration is NBSU = 3.
68P02900W21-R
9-65
GMR-01
Nov 2007
KSWXs/DSWXs should be considered for this example as the conguration needs more than one
shelf. The KSWX/DSWX extends the TDM highway of a BSU to other BSUs and supplies clock
signals to all shelves in the multi-shelf conguration. The KSWX/DSWX can be used in expansion,
remote and local modes. We need 3 BSU shelves with 3 master/redundant KSWs/DSW2s, which
implies that 2 expansion shelves are required. The number of KSWXs/DSWXs required (NKX) is
the sum of KSWXDSWXE, KSWX/DSWXR, and KSWX/DSWXL.

NKXL = K + SE = 3
NKX = 6 + 0 + 3 = 9
The maximum number of KSWX/DXWX slots per shelf 18.
KSWXs and DSWXs can be used together in a shelf, provided that they are used
with like pairs, KSWX is connected to KSWX and DSWX connected to DSWX.
GCLK requirements
The number of GCLKs required (with redundancy) = 2
CLKX requirements
given by:

LANX requirements

9-66
68P02900W21-R
GMR-01
Nov 2007
PIX requirements
PIX Number of BSUs = 6
Line interfaces
Number of T43s = RoundUp (Number of MSIs) /3)
Number of T43s = 33/3 = 11
The number of T43 boards required is 11
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.

An NVM board is required in this example, so NVM = 1.
68P02900W21-R
9-67
GMR-01
Nov 2007
RXCDR planning
The following planning steps are performed (for this example):
The number of links between the RXCDR and BSC
The number of E1 links between the RXCDR and MSC
The number of XCDR/GDP2/GDP2s
The number of MSIs
The number of DSW2s
The number of RXU3 shelves
The number of GCLKs
The number of CLKXs
The number of LANXs
The number of PIXs
The number of line interface boards (T43s)
The number of digital power supply units
Determining the number of E1 links between the RXCDR and BSC
Determining the number of E1 links between the RXCDR and MSC

9-68
68P02900W21-R
GMR-01
Nov 2007
Where:
Is:
the number of MTL links required.
the number of OML links required.
the number of trunks between MSC and BSC.
~ 96
The number of E1 links between the RXCDR and MSC = 96
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 trafc, we only require to allocate
enough GDP2 cards for the additional AMR HR trafc.
During the system planning exercise, we learnt 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 trafc
among 6 carriers/cell.
Therefore, the number of GDP2 cards needed to support AMR HR trafc is:
30/59 (% AMR HR TCH) * 2946 (total trunks in BSC) /60 (GDP2 carries 60 calls) = GDP2 = 25
Table 9-14 Determining the number of XCDR/GDP/GDP2 cards

Total number needed
Number of E1s supported
GDP2 cards
25 (each GDP2 can offer 60

voice calls in RXU3 shelf
(with enhanced capacity
mode enabled) for AMR HR
or FR voice calls).
25 * 2 = 50
XCDR/GDP cards
46 (each card supports 30

FR voice trafc calls)
46 * 1 = 46
XCDR/GDP/GDP2
71
Total number of cards (mix)
96
Total E1s supported

GPROC3 requirements for RXCDR
Each shelf should have minimum of one GPROC3. Hence, 5 non-redundant GPROCs are
required. If the operator selects to use redundancy, 10 GPROC3s are required.
The number of GPROC3s required for RXCDR = 5 + 5 (for redundancy) = 10
68P02900W21-R
9-69
GMR-01
Nov 2007

interfaces 2 E1 links, hence, 13 MSI cards are required on the RXCDR.
MSI requirements for RXCDR = 13
DSW2 requirements for RXCDR
No enhanced capacity mode is assumed as timeslot usage per shelf is not a limiting
factor in this conguration.
Number of TDM slots required for the GPROC3s, MSIs and XCDRs is given by:
N= (G*n) (RGDPXCDR*16) + (REGDP * 80) + (RGDP2 * 24) + (M * 64)
TDM timeslots required = 8*16 _46*16+ 25* 24 +13*64 = 2296
Each DSW2 provides 1016 timeslots on the TDM highway, hence, 3 non-redundant DSW2s are
required for RXCDR with this conguration.
DSW2s required for the RXCDR = 3 + 3 (redundant) = 6
RXU3 shelves
The number of RXU3 shelves required is given by (assuming that an NVM board is tted):
~5
Table 9-15
RXU3 shelves
RXU 1
RXU 2
RXU 3
RXU 4
RXU 5
MSIs / 2 E1s (M)
GDP2s (R)
GDPs (R)
10
Ensure that the following is true for each shelf:

N + (G*n) + (M*64) + (R*16) 1016
Hence, 5 RXU3 shelves are required to equip 71 transcoder cards and 13 MSI cards.
The number of RXU3 shelves required = 5
9-70
68P02900W21-R
GMR-01
Nov 2007

The number of KSWXs/DSWXs required is the sum of KSWX/DSWXE, KSWX/DSWXR, and
KSWX/DSWXL. The calculations imply 2 expansion and 2 extension shelves are required.
The number of KSWXs/DWSXs required = 13 + 13 (redundant) = 26
KSWXs and DSWXs are used together in a shelf, provided that they are used with like
pairs, that is, KSWX connected to KSWX and DSWX connected to DSWX.
GCLK requirements
The generic clock generates all the timing reference signals required by the RXU3. One GLCK is
Number of GCLKs required = 1 + 1 (redundant) = 2
CLKX requirements
Provides expansion of GCLK timing to more than one RXU3:
Where:
Is:
RF
68P02900W21-R
9-71
GMR-01
Nov 2007
The number of CLKXs required = 1 + 1 (redundant) = 2

LANX requirements
Where RF it the redundancy factor.

PIX requirements
PIX 2 * Number of RXU3s = 2 * 5 = 10
Hence, 10 PIX cards are required for the RXCDR.
Line interfaces
Number of T43s = Number of E1s/6 = (25+96)/6 ~ 21
The number of T43 boards required = 15
PSUs = 2*RXU3s + RF*RXU3s = 2*5 + 1*5 = 15
One redundant PSU is required for each RXU3 shelf, hence total number of PSUs required = 15.
NVM= 1 (required in this example)
9-72
68P02900W21-R
GMR-01
Nov 2007

Use this example to plan the equipment of a BSC supporting a trafc model, with the parameters
listed in Table 9-16 and their typical values
This example is for 28 sites/BSC with 3 cells/BTS and 4 carriers/cell.
Table 9-16
Typical LCS call model parameter

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
T = 75 S
Call duration
Call rate [call/sub/BH]
Call_Sub_Rate = 1
LCS = 5%
LCS penetration rate [%]
LCS_BSC_Rate = 2
LCS request rate2: [req/sec/BSC]

Link utilization factor UMSC_BSC
0.35
Link utilization factor UBSC_BTS
0.25
LCS planning example calculations

Determine LCS architecture
BSS-based LCS architecture is supported.
68P02900W21-R
9-73
GMR-01
Nov 2007
Calculate MTLs (actually needed trunks number is 1812)
n1LCF-MTL = (20*T)/(1 0.16*S 0.5*H*(1 0.6*i) 0.42*L 0.45*L ) + PPC *(0.005*B 0.05)*(1 LCS ))
= 20 * 75 / (1 0.6*0.1 0.5*2.5*(1 0.6*0.6) 0.42*0.05) 0.124*(0.005*56 0.05)*(1 0.05))
= 559.268
n1min = MIN (nllink, n1LCF-MTL )= 151.468
nllogical = N/Ng = (1812/64) = 28.31
nlog_per_mtl = RoundDown (n1min/Nlogical) = 5
Finally, the number of required MTLs with 64 logical links is:
mtls = RoundUp (Ng/ Nlog_per_mtl) = 13
Calculate MTL LCFs

NLCF-MTL = 13/2 = 6
Calculate RSLs
According to Chapter 3 BSS cell planning, TCHs per BTS is 29*3. Then,
Calculate RSL LCFs
Therefore, the RSL LCFs number is 4.

9-74
68P02900W21-R
GMR-01
Nov 2007
Calculate LMTLs
Calculate LMTL LCFs

N
LCF _LSL
=1
68P02900W21-R
Nov 2007
9-75
GMR-01
9-76
68P02900W21-R
GMR-01
Nov 2007
Chapter
10
Location area planning
This section provides a description of location area planning with an example. Each operator
should undertake this exercise to optimize the network congurations 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
Nov 2007
10-1
GMR-01
Location area planning considerations
Location area planning considerations
Before the GSR4 BSS software release, the trafc 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 trafc 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. Increasing the number of location areas increases the number of location updates
on the cells bordering the location area. Provision more SDCCHs for this increased signaling
on the border cells. Fewer channels are available for trafc.
A well-planned network should have similar paging loads in each location area. A small paging
load suggests that the location area is too small and could be combined with neighboring
location areas, minimizing 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 optimize the network congurations
based on the paging load on the BSC. This topic is explained further, with an example, in the
following sections.
10-2
68P02900W21-R
GMR-01
Nov 2007
Location area planning calculations
Location area planning calculations
Example procedure
Assume a network with four BSCs under a location area (refer to Figure 10-1) each with call
model parameters as shown in Table 10-1
Table 10-1 Example of values for the parameters for location area planning
Parameter
Value
Call duration, T
90 s
Number of SMSs per call, S
0.05
Number of location updates per call (nonborder)

IMSI detaches per call, Id
2
0.2 (type 2)
2 + 0.5*0.2 = 2.1
Location update factor
Number of handovers per call, H

Number of intra-BSC handovers to all handovers, i
0.4
MTL link utilization
20%
RSL link utilization
25%
CCCH utilization
33%
Probability of blocking TCH PB-TCH
< 2%
Probability of blocking SDCCH PB-SDCCH
< 1%
Probability of blocking on A-Interface
< 1%
Paging repetition
1.2
Ratio of incoming calls to total calls
0.25
Further assume that each of the BSC handles about 1200 Erlangs (48 sites with 2/2/2
congurations and 2 sites with omni 2 conguration) of trafc.
68P02900W21-R
10-3
GMR-01
Nov 2007
Example procedure
Figure 10-1 Four BSCs in one LAC
MSC
LAC=1
BS C
BS C
BS C
BS C
ti-GSM-Four_BSCs_in_one_LAC-00146-ai-sw
The paging rate in the location area can be calculated using the following formula:
Now, calculate the number of GPROC LCF-RSLs required with this paging load using the
formula detailed in Chapter 6 BSC planning steps and rules.
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 gure, calculate the number of SDCCHs required for each cell.
From Erlang B tables, the number of Erlangs supported by 16 TCHs (2 carrier cell) with GOS of
2% is 9.83 Erlangs.
Use the formulae provided in Chapter 3 BSS cell planning for control channel calculations
as follows:
10-4
68P02900W21-R
GMR-01
Nov 2007
Example procedure
Call arrival rate:
Ratio of SMSs to calls:
The average number of SDCCHs, NSDCCH is given by:
The number of SDCCHs to support an average number of busy SDCCHs of 4.28, with less that
1% blocking as determined by use of Erlang B tables, is 10. Hence, the number of timeslots
required to carry SDCCH signaling trafc is 2 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 (refer to 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 goes
up to 6 on cells on the location area border. The average number of location updates per call for
the BSC would approximately be equal to 3 (0.25*6 + 0.75*2).
Figure 10-2 Four BSCs divided into two LACs
MSC
LAC = 1
LAC = 2
BS C
BS C
BS C
BS C
ti-GSM-Four_BSCs_divided_into_two_LACs-00147-ai-sw
68P02900W21-R
10-5
GMR-01
Nov 2007
Example procedure
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 calls:
The average number of SDCCHs for border cells, NSDCCH is given by:
The number of SDCCHs to support an average number of busy SDCCHs of 5.096 with less than
1% blocking as determined by use of Erlang B tables, is 11. Hence, the number of timeslots
required to carry SDCCH signaling trafc is 2, with each timeslot offering 8 SDCCHs.
If the network planner divides the location area such that not too much trafc crosses the border
of the location area (resulting in a lower number of location updates), even fewer resources
are required of the air interface for location update signaling.
10-6
68P02900W21-R
GMR-01
Nov 2007
Chapter
11
The derivation of call model parameter values from the GSM network statistics collected at the
OMC-R are described in this chapter. Most of the calculations used for equipment planning
use the standard call model parameters. Each network behaves in a unique way. Hence, the
operators must compute their own set of call model parameter values for a network based on
the performance statistics collected at the OMCR. This helps to optimize the congurations
on a network.
All the statistics used for determining the call model parameters must be collected during the
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 helps in averaging out the load from
the network entities.
The topic is described in Chapter 11 Call model parameters.
68P02900W21-R
Nov 2007
11-1
GMR-01
Standard call model parameters

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

Busy hour peak signalling trafc model
Parameter reference
Call duration
T = 120 seconds
S = 0.1
Number of handovers per call (Refer to

NOTE)
H = 2.5
Ratio of location updates to

calls: non-border location area.
location area
l = 2I = 7
I=0
Location update factor:

non-border location area
(Refer to NOTE)
Location update factor: border
location area (Refer to NOTE)
L = 2L = 7
GSM circuit-switched paging rate in

pages per second
PGSM = 15
Ratio of intra-BSC handovers to all

handovers (Refer to NOTE)
i = 0.6
LCS = 0.2
LRMT = 0.95
LRMO = 0.05
Percent link utilization (MSC to BSS) for

GPROC2/GPROC3
U(MSC - BSS) = 0.20
U(BSC - BTS) = 0.25
UBSC-RXCDR = 0.40
Percent link utilization (BSC to SMLC) for

GPROC2/GPROC3
UBSC-SMLC = 0.20
UCCCH = 0.33
Block Rate for TCHs
PB-TCHs = 2%
PB-Trunks = 1%
Continued
11-2
68P02900W21-R
GMR-01
Nov 2007
Standard call model parameters

Parameter reference
CBTS = 3
SMSSIZE = 100 bytes
GPRS parameters
PKSIZE = 270
Trafc per sub/BH (kbytes/hr) - Uplink
ULRATE = 30
Trafc per sub/BH (kbytes/hr) - Downlink
DLRATE = 65
SMSSIZE = 100 bytes
PSATT/DETACH = 0.6

sub/BH)
PDPACT/DEACT = 1
Routing area update
RAU = 1.4
PGPRS = 3

RLC/MAC layer
CS1
CS2
CS3
CS4
CellUpdate = 1.5
= 9.2 kbit/s
= 13.6 kbit/s
= 15.8 kbit/s
= 21.8 kbit/s
XBL (enhanced auto connect) parameters

MNEWCALL = 1

handover
MHANDOVER = 1
Length of an average XBL message, in

bytes
LXBL = 50
Hhr-fr = 1
EGPRS parameters
Average packet size (bytes) - Uplink
PKULSIZE = 287
Average packet size (bytes) - Downlink
PKDLSIZE = 700
Trafc per sub/BH (kbytes/hr) - Uplink
ULRATE = 39
Trafc per sub/BH (kbytes/hr) - Downlink
DLRATE = 85
PSATT/DETACH = 0.6

sub/BH)
PDPACT/DEACT = 1
Routing area update
RAU = 1.4
PGPRS = 3
Continued
68P02900W21-R
11-3
GMR-01
Nov 2007
Call duration (T)

Parameter reference
Coding scheme rates (MCS1 to MCS9) at

the RLC/MAC layer
MCS1
MCS2
MCS3
MCS4
MCS5
MCS6
MCS7
MCS8
MCS9
= 10.55 kbit/s
= 12.95 kbit/s
= 16.55 kbit/s
= 19.35 kbit/s
= 23.90 kbit/s
= 31.10 kbit/s
= 46.90 kbit/s
= 56.50 kbit/s
= 61.30 kbit/s
The handovers include 2G-3G handovers.
L is a function of I. It depends on the following message sequences used for IMSI

detach: short message sequence (type 1) and long message sequence (type 2)
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
Call duration (T)

Average call duration for a network can be derived from the statistics BUSY_TCH_MEAN and
TOTAL_CALLS using the following formula:
Where:
N
BUSY_TCH_MEAN
Is:
number of cells under the BSC.
average number of busy TCHs in the cell.
It 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
starting another call.
Continued
11-4
68P02900W21-R
GMR-01
Nov 2007
Ratio of SMSs per call (S)
Where:
Is:
TOTAL_CALLS
number of circuit-oriented calls that originate

in the cell. It is pegged only once per
connection at the time of the rst successful
TCH assignment procedure. Subsequent
channel changes are not counted.
ASSIGNMENT_REDIRECTIONtotal 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
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 formula is calculated for one cell and should be calculated as an average
of call durations of all the BSCs in the network.
Ratio of SMSs per call (S)

The number of SMSs per call can be calculated using the SMS related statistics parameters
in the following formula:
Where:
Is:
SMS_NO_BCAST_MSG
number of times a message is broadcast

on the CBCH.
SMS_INIT_ON_SDCCH
number of times an SMS transaction

occurs on a SDCCH.
SMS_INIT_ON_TCH
number of times an SMS transaction

occurs on a TCH.
ASSIGNMENT_REDIRECTIONtotal 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.
The ratio of SMSs per call must be averaged over all the BSCs in the network.
68P02900W21-R
11-5
GMR-01
Nov 2007
Ratio of handovers per call (H)

Handovers can be inter-BSS, intra-BSS or intra-cell. Therefore, the number of handovers per
call can be calculated using the following formula:
Where:
N
Is:
out_inter_bss_req_to_msc number of outgoing inter-BSS handover requests

to the MSC.
out_intra_bss_ho_atmpt
number of times the assignment command is

sent to an MS to initiate an outgoing intra- BSS
handover attempt.
intra_cell_ho_atmpt
number of times an assignment command is

sent to an MS, to initiate an intra-cell handover
attempt.
ASSIGNMENT
_REDIRECTION
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.
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 formula.
Ratio of intra BSS handovers to all handovers (i)

Using the statistics previously detailed, this ratio can be calculated for a cell as follows:
11-6
68P02900W21-R
GMR-01
Nov 2007
Where:
N
Ratio of location updates per call (I)
Is:
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, can be calculated using the following formula:
Where:
Is:
OK_ACC_PROC
[location_update]
counts the number of MS requests for location

updates.
ASSIGNMENT_REDIRECTIONcounts 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.
The ratio I should be averaged over all the BSCs in the network.
Ratio of IMSI detaches per call (I)

IMSI detaches is 0 if disabled. If enabled, it is calculated per cell as follows:
68P02900W21-R
11-7
GMR-01
Nov 2007
Where:
Is:
the number of cells under the BSC.
OK_ACC_PROC
[imsi_detach]
counts the number of MS requests for IMSI

detach.
ASSIGNMENT_REDIRECTIONcounts 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.
The ratio I should be averaged over all the BSCs in the network.

The location update factor is calculated using the ratio 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, L is calculated as follows depending on whether short message
sequence (type 1) or long message sequence (type 2) is used:
L = l (IMSI detach disabled, that is, I = 0)
L = l + 0.2* I (type 1)
L = l + 0.5* I (type 2)
IMSI detach types indicate 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, which involves three uplink (average
size of 26 bytes) and three downlink messages (average size of 30 bytes). A location update
procedure itself takes ve downlink messages (average size of 30 bytes) and six uplink messages
(average size of 26 bytes).
Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the total number of
messages as a location update and an IMSI detach (type 2) takes 6/11 (approximately 0.5) of
the messages of a location update.
Paging rate (PGSM)

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 only to one MS. The BSS in turn
transmits 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).
11-8
68P02900W21-R
GMR-01
Nov 2007
Pages per call (PPC)
An MS is paged in a location area, which encompasses multiple BSCs. It is also possible to

have multiple location areas within a BSC. The paging rate, therefore, is 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, denotes the pages in the location area during
that statistics interval.
Where:
Is:
PAGE_REQ_FROM_MSC
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.
Pages per call (PPC)

Pages per call for a BSC can be calculated as:
Where:
N
Is:
number of cells under the
BSC.
Alternatively, pages per call can be calculated using the formula:
Where:
Is:
number of MSC-BSC trunks.
call duration, in seconds.
68P02900W21-R
11-9
GMR-01
Nov 2007
Sample statistic calculations
Or:
Where:
Is:
BSC Erlang.

Table 11-2 shows a sample of the 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
SMS_INIT_ON_SD-CCH
15
SMS_INIT_ON_TCH
out_inter_bss_req_to_msc
531
1214
141
out_intra_bss_ho_atm
512
747
1844
746
1056
268
28
49
76
43696
43696
43696
intra_cell_ho_atmpt
OK_ACC_PROC
[location_update]
OK_ACC_PROC
[imsi_detach]
PAGE_REQ_FROM_MSC
ASSIGNMENT_REDIRECTION
Using the formulae detailed in the previous sections, call model parameters can be calculated
as follows:
11-10
68P02900W21-R
GMR-01
Nov 2007
Call duration (T)

Call duration is given by:
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 the call durations over all the BSCs
in the network.
Number of SMSs per call (S)

The number of SMSs per call is given by:

The ratio of handovers per call is given by:
68P02900W21-R
11-11
GMR-01
Nov 2007
Ratio of intra-BSS handovers to all handovers (i)

Using the statistics previously detailed, this ratio can be calculated for a BSS as follows:
Number of location updates per call (l)

Location updates per call can be calculated as:
IMSI detaches per call (I)

The number of IMSI detaches per call is given by:

The location update is given by:
11-12
68P02900W21-R
GMR-01
Nov 2007
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.
68P02900W21-R
Nov 2007
11-13
GMR-01
11-14
68P02900W21-R
GMR-01
Nov 2007
Chapter
12
Standard BSS and Horizon BTS
congurations
This chapter provides the diagrams of the logical interconnections of the components in various
standard BSS and Horizon BTS site congurations for macrocell and microcell systems. Typical
RF congurations are also provided.
Older generation (M-Cell) BTS site or RF congurations are provided in Chapter 13 M-Cell
BTS congurations.
This chapter includes the following sections:
Standard congurations on page 12-2
Typical BSS congurations on page 12-3
Single cabinet BTS congurations on page 12-6
Two cabinet BTS congurations on page 12-10
Three cabinet BTS congurations on page 12-13
Four cabinet BTS congurations on page 12-18
Horizon macrocell RF congurations on page 12-22
Microcell RF congurations on page 12-65
Connecting Horizon II macro cabinets to Horizonmacro cabinets on page 12-68
Connecting Horizon II macro cabinets to M-Cell6 cabinets on page 12-76
68P02900W21-R
Nov 2007
12-1
GMR-01
Standard congurations
Standard congurations
The examples shown here are with individual antennas for transmit and receive signals.
Duplexers are required if individual antennas are not used. However, duplexers can result in
performance degradation. For carrier redundancy, the RF carrier equipment must be duplicated
for each BTS.
The diagrams that follow are not intended to imply the maximum capacity nor a typical
conguration using that specic equipment. Rather, they are meant to highlight the
congurations that are within the constraints of the BSS architecture, and 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 some different
arrangements of the same conguration.
Rather than showing redundancy for all Horizon II macro/Horizonmacro BTS congurations, the
control redundancy is depicted only for one Horizon II macro/Horizonmacro cabinet diagram
(Refer to Figure 12-4 and Figure 12-7).
12-2
68P02900W21-R
GMR-01
Nov 2007
Typical BSS congurations
Typical BSS congurations
BSC with 24 BTSs

The digital module conguration for a BSC controlling 24 BTSs is shown in Figure 12-1.
Figure 12-1 BSC controlling 24 BTSs
DUAL IEEE LAN
BS U S HELF 1
LANX
A
LANX
B
GP ROC
1
GP ROC
2
DUAL MCAP BUS
DUAL S ERIAL BUS

PIX
GP ROC
0
BTC
KSW
A
GP ROC
3
GC LK
REDUND
ANT
GC LK
A
B
DUAL TDM HIGHWAY BUS

RMT
KSWX
A
CLKX
LCL
KSWX
A
CLKX
LCL
KSWX
B
BTC
MS I
2
MS I
1
MS I
0
MS I
7
2 Mbit/s LINKS
BTS 1
BTS 2
BTS 3
BTS 12
FIBRE OP TIC LINKS
MS C/RXCDR
2.0 48 Mbit/s LINK INTERFACES
FROM/TO MS C AND TO/FROM BTS
SITES
BTS 1 3
BTS 14
BTS 15,16
BTS 23, 24
2 Mbit/s LINKS
DUAL S ERIAL BUS

LCL
KSWX
B
LCL
KSWX
A
RMT
KSWX
B
BTC
MS I
0
MS I
2
MS I
1
MS I
6
A
B
DUAL TDM HIGHWAY BUS

BTC
GP ROC
0
GP ROC
1
KSW
B
REDUNDANT
GP ROC
2
DUAL MCAP BUS

LANX
A
LANX
B
BS U S HELF 2
DUAL IEEE LAN
BS S C CABINET
ti-GSM-BSC_controlling_ 24_BTSs-00148-ai-sw
68P02900W21-R
12-3
GMR-01
Nov 2007
BSC with full redundancy
BSC with full redundancy

The digital module conguration 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 L
AN
LANX
A
LANX
B
GPROC
1
GPROC
2
BSU SHELF 1
DUAL SERIAL BUS
DUAL MCAP
GPROC
0
BTC
PIX
KSW
A B
GPROC
3
GCLK
A
KSW
BUS
GCLK
B
REDUNDANT
A
DUAL TDM HIGHWA Y BUS
B
EXP
KSWX
A
EXP
KSWX
B
LCL
KSWX
A
CLKX
CLKX
LCL
KSWX
B
BTC
MSI
1
MSI
0
MSI
2
MSI
9
2 Mbit/s LINKS
BTS 1
BTS 2
BTS 3
BTS 16,17
MSC
FIBRE OPTIC LINKS
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
KSW
A
EXP
KSWX
B
LCL
KSWX
A
LCL
KSWX
B
BTC
MSI
0
MSI
1
MSI
2
MSI
9
A
B
BTC
GPROC
0
GPROC
1
GPROC
2
GPROC
3
KSW
A
KSW
B
DUAL MCAP
BUS
REDUNDANT
DUAL SERIAL BUS
LANX
A
LANX
B
DUAL IEEE L
AN
BSU SHELF 2
BSSC CABINET
ti-GSM-Fully_redundant_BSC_controlling_34_BTSs-00149-ai-sw
12-4
68P02900W21-R
GMR-01
Nov 2007
Transcoder
Transcoder
The digital module conguration 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.5ANL
RXU SHELF 1
LANX
B
LANX
A
DUAL SERIAL BUS
DUAL MCAP
BTC
GPROC
0
GPROC
1
KSW
A
GCLK
BUS
GCLK
REDUNDANT
A
B
RMT
KSWX
A
CLK
X
LCL
KSWX
A
CLKX
LCL
KSWX
B
LCL
KSWX
B
MSI
0
MSI
1
2.048 Mbit/s LINK

INTERFACES FROM/TO
BSCS
FIBRE OPTIC LINKS
LCL
KSWX
A
BTC
RMT
KSWX
B
BTC
MSI
0
MSI
1
XCDR
0
XCDR
15
2.048 Mbit/s LINK

INTERFACES FROM/TO
MSC
XCDR
0
XCDR
15
A

B
BTC
GPROC
0
GPROC
1
KSW
B
DUAL MCAP
BUS
REDUNDANT
DUAL SERIAL BUS

LANX
A
LANX B
DUAL IEEE L
AN
RXU SHELF 2
REMOTE TRANSCODER
CABINET
ti-GSM-BSSC_cabinet_ equipped_to_provide_transcoding-00150-ai-sw
68P02900W21-R
12-5
GMR-01
Nov 2007
Single cabinet BTS congurations
Single cabinet Horizon II macro BTS

The conguration shown in Figure 12-4 is an example of a one-cabinet Horizon II macro. This
conguration can support 6 carriers in single density mode or 12 carriers in double density
mode.
Figure 12-4
Macrocell BTS with one Horizon II macro cabinet
INTEGR ATED
NIU
INTEGRATED
NIU
HIISC
HIIS C
(FOR
REDUNDANCY)
12
12
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
Horizon II macro
CABINET
ti-GSM-Macrocell_BTS_with_one_HorizonII_macro_cabinet-00151-ai-sw
12-6
68P02900W21-R
GMR-01
Nov 2007
Single cabinet Horizon II mini BTS
Single cabinet Horizon II mini BTS

The conguration shown in Figure 12-5 is an example of a one-cabinet Horizon II mini. This
conguration can support a maximum of four carriers.
Figure 12-5
Macrocell BTS with one Horizon II mini cabinet
INTEGR ATED
NIU
INTEGRATED
NIU
HIISC
HIIS C
(FOR
REDUNDANCY)
4
4
2
C
T
U
2
C
T
U
2
Horizon II mini
CABINET
ti-GSM-Macrocell_BTS_with_one_HorizonII_mini_cabinet-00152-ai-sw
68P02900W21-R
12-7
GMR-01
Nov 2007
Single cabinet Horizon II micro BTS

The conguration shown in Figure 12-6 is an example of a one-cabinet Horizon II micro. This
conguration can support a maximum of two carriers.
Figure 12-6 Macrocell BTS with one Horizon II micro cabinet
INTEGR ATED
NIU
HIISC
2
2
2
C
T
U
2
Horizon II micro
CABINET
ti-GSM-Macrocell_BTS_with_one_HorizonII_micro_cabinet-00153-ai-sw
12-8
68P02900W21-R
GMR-01
Nov 2007
Single cabinet Horizonmacro BTS
Single cabinet Horizonmacro BTS

The conguration shown in Figure 12-7 is an example of a one-cabinet Horizonmacro. This
conguration can support a maximum of six carriers.
Figure 12-7
Macrocell BTS with one Horizonmacro cabinet
DIGITAL EQUIPMENT SHE LF

N
I
U
N
I
U
MCUF
MCUF
(FOR
REDUNDANCY)
12
12
2
2
C
T
U
Horizonmacro
CABINET
C
T
U
2
C
T
U
2
2
C
T
U
2
2
C
T
U
C
T
U
2
ti-GSM-Macrocell_BTS_with_one_Horizonmacro_cabinet-00154-ai-sw
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 the CSFP
to accommodate the added memory requirements of the GSR6 (Horizon II) objects.
In addition, the CTU2 can support only baseband hopping in single density mode
when installed in Horizonmacro.
68P02900W21-R
12-9
GMR-01
Nov 2007
Two cabinet BTS congurations
Two cabinet BTS congurations
Two cabinet Horizon II macro BTS

The conguration shown in Figure 12-8 is an example of a two cabinet Horizon II macro. This
conguration can support a maximum of 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 through ber 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 required only when
site expansion is required.
Figure 12-8 Macrocell BTS with two Horizon II macro cabinets
ti-GSM-Macrocell_BTS_with_two_HorizonII_macro_cabinet-00155-ai-sw
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.
12-10
68P02900W21-R
GMR-01
Nov 2007
Two cabinet Horizon II mini BTS
Two cabinet Horizon II mini BTS

The conguration shown in Figure 12-9 is an example of a two cabinet Horizon II mini. This
conguration can support a maximum of four carriers in single density mode and eight carriers
in double density mode. The HIISC interfaces to the CTU2s in the second (slave) cabinet
through site expansion boards in both cabinets (connected through ber 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 required only when
site expansion is required.
Figure 12-9 Macrocell BTS with two Horizon II mini cabinets

Horizon II mini
MAS TER CABINET
INTEGR ATED
XMUX
S ITE
EXPANS ION
BOARD
CON NECTION VIA BACKP LANE
HIISC
2
C
T
U
2
2
C
T
U
2
C
T
U
2
C
T
U
2
4
X
M
U
X
S ITE
EXPANS ION
BOARD
Horizo n II mini
S LAVE CABINET
ti-GSM-Macrocell_BTS_with_two_HorizonII_mini_cabinet-00156-ai-sw
68P02900W21-R
12-11
GMR-01
Nov 2007
Two cabinet Horizonmacro BTS
Two cabinet Horizonmacro BTS

The conguration shown in Figure 12-10 is an example of a two cabinet Horizonmacro. This
conguration can support a maximum of 12 carriers. The MCUF interfaces to the CTUs in the
second cabinet through a FMUX in the second cabinet.
Figure 12-10 Macrocell BTS with two Horizonmacro cabinets

Horizonma cro
CABINET
DIGITAL EQUIPMENT S HELF
N
I
U
MCUF
12
2
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
2
C
T
U
Horizon macr oC ABINET
12
C
T
U
DIGITAL
EQUIP MENT
SH ELF
F
M
U
X
ti-GSM-Macrocell_BTS_with_two_Horizonmacro_cabinet-00157-ai-sw
12-12
68P02900W21-R
GMR-01
Nov 2007
Three cabinet BTS congurations
Three cabinet BTS congurations
Three cabinet Horizon II macro BTS

The conguration shown in Figure 12-11 is an example of a three cabinet Horizon II macro. Like
a two cabinet conguration, the HIISC interfaces to the CTU2s in the slave cabinets through
site expansion boards in all cabinets (connected through ber 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
ti-GSM-Macrocell_BTS_with_three_HorizonII_macro_cabinet-00158-ai-sw
68P02900W21-R
12-13
GMR-01
Nov 2007
Three cabinet Horizon II mini BTS
Three cabinet Horizon II mini BTS

The conguration shown in Figure 12-12 is an example of a three cabinet Horizon II mini. Like
the site expansion boards in all cabinets (connected through ber optic cables) and an XMUX
Figure 12-12 Macrocell BTS with three Horizon II mini cabinets

Horizon II mini
MASTER
CABINET
CON NEC TION VIA BACKP LANE
INTEGR ATED
XMUX
SITE
EXPANSION
BOARD
HIISC
2
4
2
C
T
U
2
2
C
T
U
2
2
2
C
T
U
2
C
T
U
2
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
Horizon II mini
S LAVE CABINET
2
C
T
U
2
2
C
T
U
2
Horizon II mini
S LAVE CABINET
ti-GSM-Macrocell_BTS_with_three_HorizonII_mini_cabinet-00159-ai-sw

12-14
68P02900W21-R
GMR-01
Nov 2007
Three cabinet Horizon II micro BTS
Three cabinet Horizon II micro BTS

The conguration 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 the site expansion boards in all
cabinets (connected using ber 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
INTEGR ATED
XMUX
CON NEC TION VIA BACKP LANE
SITE
EXPANSION
BOARD
HIISC
2
2
2
2
C
T
U
2
C
T
U
2
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
Horizon II micro
S LAVE CABINET
2
C
T
U
2
Horizon II micro
S LAVE CABINET
ti-GSM-Macrocell_BTS_with_three_HorizonII_micro_cabinet-00160-ai-sw

68P02900W21-R
12-15
GMR-01
Nov 2007
Three cabinet Horizonmacro BTS

The conguration shown in Figure 12-14 is an example of a three cabinet Horizonmacro. This
conguration can support a maximum of 18 carriers. The MCUF interfaces to the CTUs in the
other cabinets through the FMUXs.
Figure 12-14 Macrocell BTS with three Horizonmacro cabinets

Horizon mac ro
CABINET
DIGITAL EQUIP MENT SH ELF
N
I
U
2
MCUF
2
12
2
Horizonma cro
CABINET
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
Horizonma cro
CABINET
C
T
U
C
T
U
2
C
T
U
C
T
U
2
C
T
U
2
C
T
U
C
T
U
C
T
U
C
T
U
12
C
T
U
2
C
T
U
F
M
U
X
12
C
T
U
DIGITAL
EQUIPMENT
SH ELF
DIGITAL
EQUIPMENT
SH ELF
F
M
U
X
ti-GSM-Macrocell_BTS_with_three_Horizonmacro_cabinet-00161-ai-sw
12-16
68P02900W21-R
GMR-01
Nov 2007
68P02900W21-R
12-17
GMR-01
Nov 2007
Four cabinet BTS congurations
Four cabinet BTS congurations
Four cabinet Horizon II macro BTS

The conguration shown in Figure 12-15 is an example of a four cabinet Horizon II macro. Like
the site expansion boards in all cabinets (connected through ber optic cables) and an XMUX
Figure 12-15 Macrocell BTS with four Horizon II macro cabinets

Horizon II macro
MASTER CABINET
CONNEC TION VIA BACKP LANE
INTEGR ATED
XMUX
SITE
EXPANSION
BOARD
HIISC
12
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
2
C
T
U
2
2
C
T
U
2
C
T
U
2
12
C
T
U
2
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
Horizon II macro
S LAVE CABINET
2
C
T
U
2
12
C
T
U
2
Horizon II macro
S LAVE CABINET
2
C
T
U
2
2
C
T
U
2
12
Horizon II macro
S LAVE CABINET
ti-GSM-Macrocell_BTS_with_four_HorizonII_macro_cabinet-00162-ai-sw
12-18
68P02900W21-R
GMR-01
Nov 2007
Four cabinet Horizon II mini BTS
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.
Four cabinet Horizon II mini BTS

The conguration shown in Figure 12-16 is an example of a four cabinet Horizon II mini. Like
site expansion boards in all cabinets (connected through ber optic cables) and an XMUX
Figure 12-16 Macrocell BTS with four Horizon II mini cabinets

Horizon II macro
MASTER CABINET
CONNECTION VIA BACKP LANE
INTEGR ATED
XMUX
SITE
EXPANSION
BOARD
HIISC
12
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
C
T
U
2
2
C
T
U
2
2
C
T
U
2
C
T
U
2
12
C
T
U
2
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
X
M
U
X
SITE
EXPANSION
BOARD
Horizon II macro
S LAVE CABINET
2
C
T
U
2
12
C
T
U
2
Horizon II macro
S LAVE CABINET
2
C
T
U
2
2
C
T
U
2
12
Horizon II macro
S LAVE CABINET
ti-GSM-Macrocell_BTS_with_four_HorizonII_mini_cabinet-00163-ai-sw
68P02900W21-R
12-19
GMR-01
Nov 2007
Four cabinet Horizonmacro BTS

The conguration shown in Figure 12-17 is an example of a four cabinet Horizonmacro. This
conguration 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

Horizonmacro
CABINET
DIGITAL EQUIPMENT SHELF
N
I
U
F
M
U
X
12
2
2
MCUF
12
2
Horizonmacro
CABINET
C
T
U
C
T
U
C
T
U
C
T
U
C
T
U
2
C
T
U
Horizonmacro
CABINET
C
T
U
C
T
U
Horizonmacro
CABINET
2
C
T
U
C
T
U
2
C
T
U
2
C
T
U
C
T
U
C
T
U
C
T
U
2
C
T
U
C
T
U
2
C
T
U
2
C
T
U
C
T
U
C
T
U
2
C
T
U
12
F
M
U
X
12
C
T
U
DIGITAL
EQUIP MENT
SH ELF
F
M
U
X
12
C
T
U
DIGITAL
EQUIP MENT
SH ELF
DIGITAL
EQUIP MENT
SH ELF
F
M
U
X
ti-GSM-Macrocell_BTS_with_four_Horizonmacro_cabinet-00164-ai-sw
12-20
68P02900W21-R
GMR-01
Nov 2007
68P02900W21-R
12-21
GMR-01
Nov 2007
Horizon macrocell RF congurations
Horizon macrocell RF congurations
Overview of conguration diagrams

The Horizon macrocell BTS cabinets/enclosures are explained in the following order:
Horizon II macro cabinets
Horizon II mini cabinets
Horizonmacro cabinets
Horizoncompact2 enclosures

The following series of Horizon II macro RF conguration diagrams show the 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 congurations can
be adopted to achieve the same aim.
Each diagram (except for the PGSM diagrams) is applicable to either EGSM900 or DCS1800
operation, though the SURF2 module illustrated is an 1800 MHz SURF2. For EGSM900
operation, a 900 MHz SURF2 is required.
Two SURF2s can be installed in the Horizon II macro cabinet (Refer to 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 congurations
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 three CTU2s per band
can be accommodated.
An external equipment cabinet is not required.
12-22
68P02900W21-R
GMR-01
Nov 2007
[DCS1800] 4 or 8 carrier omni with HCUs and air combining

Table 12-1 provides a summary of the equipment required for this conguration. Figure 12-18
shows a single cabinet, four CTU2 conguration with duplexers, hybrid combiner units and
air combining.
Table 12-1 Equipment required for 4 or 8 carrier omni with HCUs and air combining
Quantity
Equipment
Antennas
Horizon II macro cabinet
CTU2
Receiver
SURF2
Transmitter/Receiver
DUP
HCU
Figure 12-18 [DCS1800] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx
Tx/Rx
ANTENNA ANTENNA
RX
2B
RX
1B
RX
0B
EXP EXP RX
B
A
0A
RX
1A
RX
2A
SURF2
5
HCU
RX
HCU
ANT
BLANK
EMP TY
CTU2
ANT
DUP
BLANK
CTU2
EMP TY
0
RX
DUP
CTU2
CTU2
Horizon II macro CABINET

ti-GSM-[DCS1800]_4or8 _carrier_omni_with_ HCUs-00165-ai-sw
68P02900W21-R
12-23
GMR-01
Nov 2007
[DCS1800] 6 or 12 carrier omni with DHUs

Figure 12-19 shows a single cabinet, six CTU2 conguration with duplexers and dual hybrid
combiner units. Table 12-2 provides a summary of the equipment required for this conguration.
Figure 12-19 [DCS1800] 6 or 12 carrier omni with DHUs

Tx/Rx
Tx/Rx
ANTENNA ANTENNA
RX
2B
RX
1B
RX
0B
EXP EXP
B
A
RX
0A
RX
1A
RX
2A
SU RF2
DHU
DHU
RX
RX
ANT
BLANK
CTU2
CTU2
ANT
DUP
BLANK
CTU2
CTU2
DUP
CTU2
CTU2
Horizon II ma cro CABINET

ti-GSM-[DCS1800]_6or12 _carrier_omni_with_ DHUs-00166-ai-sw
Table 12-2
Equipment required for 6 or 12 carrier omni with DHUs
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
DHU
12-24
68P02900W21-R
GMR-01
Nov 2007
[DCS1800] 2 sector 3/3 or 6/6 with DHUs

combiner units. Table 12-3 provides a summary of the equipment required for this conguration.
Figure 12-20
[DCS1800] 2 sector 3/3 or 6/6 with DHUs
SEC TOR 2
Tx/Rx
ANTENNA
SEC TOR 1
Rx
ANTENNA
RX
2B
Rx
ANTENNA
RX
1B
RX
0B
EXP EXP RX
B
A
0A
RX
1A
Tx/Rx
ANTENNA
RX
2A
SUR F2
DHU
RX
RX
ANT
DUP
BLANK
CTU2
CTU2
DHU
CTU2
ANT
DUP
BLANK
CTU2
CTU2
CTU2

ti-GSM-[DCS1800]_2sector3/3or6/6_with_ DHUs-00167-ai-sw
Table 12-3 Equipment required for 2 sector 3/3 or 6/6 with DHUs
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
DHU
68P02900W21-R
12-25
GMR-01
Nov 2007
[DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
Figure 12-21 shows a two cabinet conguration, 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 conguration.
Figure 12-21 [DCS1800] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
SECTOR 2
SECTOR 1
Tx/Rx ANTEN
NAS
RX
2B
RX
1B
RX
0B
Tx/Rx ANTENNAS
EXP EXP RX
B
A
0A
RX
1A
RX
2A
RX
2B
SURF2
RX
HCU
DUP
CTU2
CTU2
3
XMUX
Horizon IImacro
SLAVE CABINE
T
EXP
B
RX
HCU
ANT
BLANK
RX
0B
EXP
A
RX
0A
RX
1A
RX
2A
SURF2
EMPTY
RX
1B
HCU
ANT
BLANK
EMPTY
CTU2
BLANK
CTU2
EMPTY
SITEEXPANSION
BOARD
RX
HCU
ANT
DUP
RX
ANT
DUP
BLANK
CTU2
CTU2
EMPTY
Horizon II macro
MASTERCABINET
SITE EXPANSION
BOARD
DUP
CTU2
CTU2
0
HIISC
Fibre Optic Link (x2)

ti-GSM-[DCS1800]_2 cabinet_2 sector_4/4_or_8/8_with_HCUs-00168-ai-s
Table 12-4 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and
air combining
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
HCU
12-26
68P02900W21-R
GMR-01
Nov 2007
[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs

Figure 12-22 shows a single cabinet, six CTU2 conguration with duplexers and hybrid combiner
units. Table 12-5 provides a summary of the equipment required for this conguration.
Figure 12-22
[DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs
SEC TOR 3
SE CTOR 2
Tx/Rx
Rx
ANTENNA ANTENNA
SE CTOR 1
Rx
Tx/Rx
ANTENNA ANTENNA
RX
2B
RX
1B
RX
0B
EXP EXP
B
A
Rx
Tx/Rx
ANTENNA ANTENNA
RX
0A
RX
1A
RX
2A
SURF2
5
RX
HCU
CTU2
RX
HCU
2
HCU
0
RX
ANT
ANT
ANT
DUP
DUP
DUP
CTU2
CTU2
CTU2
CTU2
CTU2

ti-GSM-[DCS1800]_3sect or_222or444_with_HCUs -00169-a i-sw
Table 12-5 Equipment required for 3 sector 2/2/2 or 4/4/4 with HCUs
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
HCU
68P02900W21-R
12-27
GMR-01
Nov 2007
[DCS1800] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air

combining
Figure 12-23 shows a two cabinet conguration, each cabinet containing six CTU2s with
Figure 12-23 [DCS1800] 2 cabinets, 3 sector 4/4/4 or 8/8/8 with HCUs and air
combining
RX
2B
SECTOR3
SECTOR1
SECTOR2
Tx/Rx ANTENNAS
Tx/Rx ANTENNAS
Tx/Rx ANTENNAS
RX
1B
RX
0B
EXP
B
EXP
A
RX
0A
RX
1A
RX
2A
RX
2B
SURF2
RX
0B
EXP
B
EXP
A
RX
0A
RX
1A
RX
2A
SURF2
5
HCU
RX
1B
RX
3
HCU
2
RX
HCU
RX
RX
HCU
3
HCU
2
RX
HCU
0
RX
ANT
ANT
ANT
ANT
ANT
ANT
DUP
DUP
DUP
DUP
DUP
DUP
CTU2
CTU2
CTU2
CTU2
CTU2
CTU2
CTU2
XMUX
Horizon II m a cro
S LAVE CABINET
SITE E XPANSION
BOARD
CTU2
CTU2
Horizon II ma cro
MAS TER CABINET
CTU2
S ITE EXPANS ION

BOARD
CTU2
CTU2
0
HIIS C

ti-GSM-[DCS1800]_2cab,3sector_222or444_with_HCUs-00170-ai-sw
Table 12-6 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs
and air combining
Quantity
Equipment
Antennas
12
CTU2
Receiver
SURF2
DUP
HCU
12-28
68P02900W21-R
GMR-01
Nov 2007
[DCS1800] 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity

Figure 12-24 shows a single cabinet, six CTU2 conguration for 4 branch Rx diversity with
Figure 12-24 [DCS1800] 3 sector 2/2/2 or 4/4/4 with air combining and 4 branch Rx
diversity
S E C TO R 3
S E C TO R 2
SE CTOR 1
RX
2C
RX
1C
RX
0C
EXP EXP
C
D
RX
0D
RX
1D
RX
2D
SURF2
RX
2B
RX
1B
RX
0B
EXP EXP
B
A
RX
0A
RX
1A
RX
2A
SURF2
5
RX
RX
3
RX
2
RX
RX
RX
ANT
ANT
ANT
ANT
ANT
ANT
DUP
DUP
DUP
DUP
DUP
DUP
CTU2
CTU2
CTU2
CTU2
CTU2
CTU2

ti-GS M-[DCS 1800]_3s e ctor_222or444_with_4bra nchRx_dive rs ity-00171-a i-sw
Table 12-7 Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity
Quantity
Equipment
12
Antennas
CTU2
Continued
68P02900W21-R
12-29
GMR-01
Nov 2007
Table 12-7
(Continued)
Equipment required for 3 sector 2/2/2 or 4/4/4, 4 branch Rx diversity
Quantity
Equipment
Receiver
SURF2
DUP
[DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2

shows a single cabinet, three CTU2 (1800 MHz) and three CTU2 (900 MHz) conguration with
duplexers and air combining. This is a typical Horizon II macro dual band conguration, which
supports both 900 MHz and 1800 MHz within the same cabinet.
Table 12-8
Equipment required for 3 sector 2/2/2 and 2/2/2
Quantity
Equipment
12
Antennas
Dual band adaptor
1800 MHz CTU2
900 MHz CTU2/ SURF2

Receiver
1800 MHz SURF2
900 MHz SURF2

1800 MHz DUP
900 MHz DUP

Power supply
Power supply
A fourth power supply is

recommended - contact your
Motorola Local Ofce for full
details.
12-30
68P02900W21-R
GMR-01
Nov 2007
Figure 12-25 [DCS1800/GSM900] 3 sector 2/2/2 and 2/2/2 with air combining
1800
1800
1800
SEC TOR 2 SEC TOR 1 SEC TOR 0
900
900
900
SEC TOR 2 SEC TOR 1 SEC TOR 0
A
A2
A B
B0
A0
900 S URF2
B2
B A
1800 S URF2
DB Ada ptor
900
DUP
900
DUP
900
DUP
1800
DUP
1800
DUP
1800
DUP
CTU2
900
CTU2
900
CTU2
900
CTU2
1800
CTU2
1800
CTU2
1800
A
B
HorizonII ma cro CABINET

ti-GSM-[DCS1800GSM900]_3sector_222and222_with_air_combining-00172-ai-sw
68P02900W21-R
12-31
GMR-01
Nov 2007
Horizon II macro cabinets with PGSM Duplexer
The HII Dual band adaptor allows 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 is plugged 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 can be congured with the
dual band adaptor in a Horizon II cabinet. The rear SURF2 controls CTU2 radio slots
from 3 to 5; the front SURF2 controls CTU2 radio slots from 0 to 2.

The following series of Horizon II macro RF conguration diagrams suggests the ways of
connecting together Horizon II macro cabinets with PGSM Duplexers. The series of diagrams is
by no means exhaustive, and numerous alternative congurations can 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 congurations
shown in Figure 12-26 to Figure 12-31:
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.
[PGSM] 4 or 8 carrier omni with HCUs and air combining

Figure 12-26 shows a single cabinet, four CTU2 conguration with duplexers, hybrid combiner
units and air combining. Table 12-9 provides a summary of the equipment required for this
conguration.
12-32
68P02900W21-R
GMR-01
Nov 2007
Figure 12-26 [PGSM900] 4 or 8 carrier omni with HCUs and air combining
Tx/Rx
ANTENNA
RX
2B
RX
1B
RX
0B
Tx/Rx
ANTENNA
EXP
B
EXP
A
RX
0A
RX
1A
RX
2A
SURF 2
5
HCU
RX
HCU
ANT
BLANK
EMP TY
5
CTU2
4
RX
ANT
DUP
BLANK
CTU2
EMP TY
DUP
CTU2
1
CTU2
0

ti-GSM-[PGSM900]_4or8_carrier_omni_with_HCUs-00173-ai-sw
Table 12-9 Equipment required for 4 or 8 carrier omni with HCUs and air combining
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
HCU
68P02900W21-R
12-33
GMR-01
Nov 2007
[PGSM900] 6 or 12 carrier omni with DHUs

combiner units. Table 12-10 provides a summary.
Figure 12-27 [PGSM900] 6 or 12 carrier omni with DHUs

Tx/Rx
Tx/Rx
ANTENNA ANTENNA
RX
2B
RX
1B
RX
0B
EXP EXP RX
B
A
0A
RX
1A
RX
2A
SU RF2
DHU
DHU
RX
RX
ANT
DUP
BLANK
CTU2
CTU2
CTU2
ANT
DUP
BLANK
CTU2
CTU2
CTU2

ti-GSM-[PGSM900] _6or12_carrier_omni_ with_ DHUs-00174-ai-sw
Table 12-10 Equipment required for 6 or 12 carrier omni with DHUs

Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
DHU
12-34
68P02900W21-R
GMR-01
Nov 2007
[PGSM900] 2 sector 3/3 or 6/6 with HCUs

Figure 12-28 shows a single cabinet, six CTU2 conguration with duplexers and hybrid combiner
units. Table 12-11 provides a summary of the equipment required for this conguration.
Figure 12-28 [PGSM900] 2 sector 3/3 or 6/6 with HCUs

SE CTOR 2
S ECTOR 1
Rx
Tx/Rx
ANTENNA ANTENNA
RX
2B
RX
1B
Rx
Tx/Rx
ANTENNA ANTENNA
RX
0B
EXP EXP
B
A
RX
0A
RX
1A
RX
2A
SURF2
RX
HCU
RX
ANT
ANT
DUP
CTU2
CTU2
RX
HCU
RX
ANT
DUP
DUP
CTU2
CTU2
ANT
DUP
CTU2
CTU2

ti-GSM-[PGSM900]_2_sector_3/3or6/6_with_HCUs-00175-ai-sw
Table 12-11 Equipment required for 2 sector 3/3 or 6/6 with HCUs
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
HCU
68P02900W21-R
12-35
GMR-01
Nov 2007
[PGSM900] 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and air combining
Figure 12-29 shows a two cabinet conguration, each cabinet containing four CTU2s with
Figure 12-29
[PGSM900] 2 cabinets, 2 sector 4/4 or 8/8 with HCUs and air combining
0.0056 in
ti-GSM-[PGSM900]_2_cab_2_sector_4/4_or_ 8/8_with_HCUs_and_air_combining-00176-ai-sw
Table 12-12 Equipment required for 2 cabinet, 2 sector 4/4 or 8/8 with HCUs and
air combining
Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
HCU
12-36
68P02900W21-R
GMR-01
Nov 2007
[PGSM900] 3 sector 2/2/2 or 4/4/4

Figure 12-30 shows a single cabinet, six CTU2 conguration with duplexers. Table 12-13
provides a summary of the equipment required for this conguration.
Figure 12-30 [PGSM900] 3 sector 2/2/2 or 4/4/4

SECTOR 3
SECTOR 2
SECTOR 1
Tx/Rx
Tx/Rx
Rx
Rx
Rx
Tx/Rx
ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA ANTENNA
RX
2B
RX
1B
RX
0B
EXP EXP RX
B
A
0A
RX
1A
RX
2A
SURF2
RX
RX
RX
RX
RX
ANT
DUP
ANT
ANT
DUP
ANT
DUP
ANT
ANT
DUP
DUP
DUP
CTU2
CTU2
CTU2
CTU2
CTU2
CTU2
RX
1
0
ti-GSM-[PGSM900] 3 sector 2/2/2 or 4/4/ 4-00177-ai-sw
Table 12-13 Equipment required for 3 sector 2/2/2 or 4/4/4

Quantity
Equipment
Antennas
CTU2
Receiver
SURF2
DUP
68P02900W21-R
12-37
GMR-01
Nov 2007
[PGSM900] 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs and air

combining
Figure 12-31 shows a two cabinet conguration, each cabinet containing six CTU2s with
Figure 12-31 [PGSM900] 2 cab, 3 sector 4/4/4 or 8/8/8 with HCUs and air combining
ti-GSM-[PGSM900]2cab 3sector4/ 4/4or 8/8/8 with_HCUs_an d_air_combini ng 4-00179-ai-sw
Table 12-14 Equipment required for 2 cabinet, 3 sector 4/4/4 or 8/8/8 with HCUs
and air combining
Quantity
Equipment
Antennas
12
CTU2
Receiver
SURF2
DUP
HCU
12-38
68P02900W21-R
GMR-01
Nov 2007

The following series of Horizon II mini RF conguration diagrams suggests the 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
congurations can be adopted to achieve the same aim.
Each diagram is applicable to either EGSM900 or DCS1800 operation, though the MiniSURF2
module illustrated is an 1800 MHz SURF2. For EGSM900 operation, a 900 MHz MiniSURF2
is required. For PGSM900 operation, only certain congurations 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 congurations
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).
[DCS1800/EGSM900/PGSM900] High power Omni-1, standard power

Omni-2
shows a single cabinet, one CTU2, high power (HP) Omni-1/standard power (SP) Omni-2
conguration.
Table 12-15 Equipment required for HP Omni-1/SP Omni-2

Quantity
Equipment
Antennas
Horizon II mini cabinet
CTU2
Receiver
MiniSURF2
68P02900W21-R
12-39
GMR-01
Nov 2007
Figure 12-32 DCS1800/EGSM900 HP Omni-1/SP Omni-2
BATTERY
1B
0B
0A
1A
HIISC
ALARM
Se ctor 1:
2 ca rrie rs
T43/BIB
RE AR
FRONT
Horizon II mini CABINET

ti-GSM-DCS_800/EGSM900_HP_Omni-1/SP_Omni-2-00180-ai-sw
[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 conguration. Table 12-16 provides a summary of the equipment required for this
conguration.
12-40
68P02900W21-R
GMR-01
Nov 2007
Figure 12-33 DCS1800/EGSM900 HP Omni-2/SP Omni-4
1B
0B
0A
BATTERY
1A
HIISC
ALARM
S e ctor 1:
4 ca rrie rs
T43/BIB
REAR
FRO NT

ti-GSM-DCS1800/EGSM900 HP Omni-2/SP Omni-4-00181-ai-sw
Table 12-16 Equipment required for HP Omni-1/SP Omni-2

Quantity
Equipment
Antennas
CTU2
Receiver
MiniSURF2
[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 conguration. Table 12-17 provides a summary of the equipment required for this
conguration.
68P02900W21-R
12-41
GMR-01
Nov 2007
Figure 12-34 DCS1800/EGSM900 HP Bowtie-2/SP Bowtie-4

Antenna 1:
4 carriers
Antenna 2:
4 carriers
1B
0B
0A
BATTER Y
1A
HIISC
ALARM
Hybrid
T43/BIB
REAR
FRONT

ti-GSM-DCS1800/EGSM900_HP_Bowtie-2/SP Bowtie-4-00182-ai-sw
Table 12-17 Equipment required for HP Bowtie-2/SP Bowtie-4

Quantity
Equipment
Antennas
CTU2 Bowtie-4 conguration

Receiver
MiniSURF2
Hybrid combiner
12-42
68P02900W21-R
GMR-01
Nov 2007
[DCS1800/EGSM900] High power 2 sector 1/1, standard power 2 sector

2/2
Figure 12-35 shows a single cabinet, two CTU2, HP 2 sector 1/1/SP 2 sector 2/2 conguration.
Table 12-18 provides a summary of the equipment required for this conguration.
Figure 12-35 DCS1800/EGSM900 HP 2 sector 1/1/SP 2 sector 2/2

Se ctor 2:
2 ca rrie rs
BATTERY
1B 0B
0A 1A
HIISC
ALARM
Sector 1:
2 carriers
T43/BIB
RE AR
FRONT

ti-GSM-DCS1800/EGSM900HP2sector1/1/SP2sector2/2-00183-ai-sw
Table 12-18 Equipment required for HP 2 sector 1/1/SP 2 sector 2/2

Quantity
Equipment
Antennas

Continued
68P02900W21-R
12-43
GMR-01
Nov 2007
Table 12-18 Equipment required for HP 2 sector 1/1/SP 2 sector 2/2 (Continued)
Quantity
Equipment
CTU2
Receiver
MiniSURF2
[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 conguration. Table 12-199 provides a summary of
the equipment required for this conguration.
Figure 12-36 DCS1800/EGSM900 HP 2 sector 2/2/SP 2 sector 4/4

Sector 2:
4 carriers
Sector 1:
4 carriers
SITE EXP
0A 1A
1B 0B
T43/BIB
FRONT
BATTER Y
ALARM
HIISC
BATTERY
1B 0B
0A 1A
ALARM
HIISC
SITE E XP
T43/BIB
REAR
Horizon II mini
S LAVE CABINET
FRONT
REAR
Horizon II mini
MASTER CABINET
ti-GSM-DCS1800/EGSM900HP2sector2/2/SP2sector4/4-00184-ai-sw
Table 12-19 Equipment required for HP 2 sector 2/2/SP 2 sector 4/4

Quantity
Equipment
Antennas
Site I/O board
CTU2
Receiver
MiniSURF2
12-44
68P02900W21-R
GMR-01
Nov 2007
[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
conguration. Table 12-20 provides a summary of the equipment required for this conguration.
Figure 12-37 DCS1800/EGSM900 HP 3 sector 1/1/1/SP 3 sector 2/2/2

Sector 3:
4 carriers
Se ctor 1:
2 c ar riers
Se ctor 2:
2 c ar riers
S ITE EXP
0A 1A
1B 0B
T43 /BIB
FRON T
BATTERY
ALARM
HIISC
BATTERY
1B 0B
0A 1A
ALARM
HIISC
SITE EXP
T43/BIB
REAR
FR ONT
Horizo n II mini
S LAVE CABINET
RE AR
Horizon II mini
MAS TER CABINET
ti-GSM-DCS1800/EGSM900HP3sector1/1/1/SP3sector2/2/2-00185-ai-sw
Table 12-20 Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2

Quantity
Equipment
Antennas
Site I/O board
CTU2
Receiver
MiniSURF2
68P02900W21-R
12-45
GMR-01
Nov 2007
[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 conguration.
Figure 12-38 DCS1800/EGSM900 HP 3 sector 2/2/2/SP 3 sector 4/4/4

Sec tor 2:
4 ca rriers
S e ctor 1:
4 ca rrie rs
2
S ITE EXP
1B 0B
T43 /BIB
T43/BIB
REAR
FRONT
BATTERY
0A 1A
ALARM
HIIS C
BATTERY
1B 0B
0A 1A
ALARM
HIIS C
SITE EXP
Horizon II mini
S LAVE CABINET
FRONT
RE AR
Horizon II mini
MAS TER CABINET
BATTERY
1B 0B
0A 1A
ALARM
HIIS C
S ITE EXP
Sec tor 3:
4 ca rriers
T43 /BIB
FRONT
REAR
Horizon II mini
S LAVE CABINET
ti-GS M-DCS180 0/EGSM 900_HP _3_s e ctor_2/2/2/SP _3_s e ctor_4/4 /4-00186-a i-s w
12-46
68P02900W21-R
GMR-01
Nov 2007
Horizon II micro cabinets
Table 12-21 Equipment required for HP 3 sector 2/2/2/SP 3 sector 4/4/4

Quantity
Equipment
Antennas
Site I/O board
CTU2
Receiver
MiniSURF2

The following series of Horizon II micro RF conguration diagrams show the 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 congurations can
be adopted to achieve the same aim.
Each diagram is applicable to either EGSM900 or DCS1800 operation, though the MiniSURF2
module illustrated is an 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 congurations
shown in Figure 12-39 and Figure 12-40:
[DCS1800/EGSM900] Single cabinet - Horizon II micro

Figure 12-39 shows a single cabinet conguration. Table 12-22 provides a summary of the
68P02900W21-R
12-47
GMR-01
Nov 2007
Figure 12-39 [DCS1800/EGSM900] Horizon II micro one-cabinet conguration
1B
0B
0A
BATTERY
1A
HIISC
ALARM
Se ctor 1:
2 ca rrie rs
T43/BIB
POWE R SU PP LY
RE AR
FRONT
Horizon II micro CABINET

ti-GSM-[DCS1800/EGSM900]_Horizon_II_micro_one_cabinet_configuration-00187-ai-sw
Table 12-22 Equipment required for Horizon II micro one cabinet conguration
Quantity
Equipment
Antennas
Horizon II micro cabinet
CTU2
Receiver
MiniSURF2
12-48
68P02900W21-R
GMR-01
Nov 2007
[DCS1800/EGSM900] Three cabinet - Horizon II micro

Figure 12-40 shows a three cabinet conguration. Table 12-23 provides a summary of the
Figure 12-40 [DCS1800/EGSM900] Horizon II micro three cabinet conguration

Sector 2:
2 carriers
Sector 1:
2 carriers
2
S ITE EXP
1B 0B
T43/ BIB
BATTERY
0A 1A
ALARM
HIIS C
BATTERY
1B 0B
0A 1A
ALARM
XMUX
S ITE EXP
T43/BIB
PO WER S UPP LY
PO WER SUP P LY
REAR
FRON T
Horizon II micro
S LAVE CABINET
FRO NT
RE AR
Horizon II micro
MAS TER CABINET
BATTERY
1B 0B
0A 1A
ALARM
XMUX
S ITE EXP
Sect or 3:
2 car rie rs
T43/ BIB
PO WER S UPP LY
FRON T
REAR
Horizon II micro
S LAVE CABINET
ti-GSM-[DCS1800/EGSM900]Horizon_II_micro_three_cabinet_configuration-00188-ai-sw
68P02900W21-R
12-49
GMR-01
Nov 2007
Table 12-23
Equipment required for Horizon II micro three cabinet conguration
Quantity
Equipment
Antennas
Horizon II micro cabinet
CTU2
Receiver
MiniSURF2
Site I/O board (expansion)
The following series of Horizonmacro RF conguration diagrams show the 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 congurations can 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 identied similar 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 congurations
A maximum of six CTUs can be accommodated.
[DCS1800] 4 carrier omni, with duplexed hybrid and air combining

Figure 12-41 shows a single cabinet, four CTU conguration with duplexed hybrid and air
combining. Table 12-24 provides a summary of the equipment required for this conguration.
12-50
68P02900W21-R
GMR-01
Nov 2007
Figure 12-41 4 carrier omni, duplexed hybrid and air combining

Tx/Rx
ANTENNA
Tx/Rx
ANTENNA
B
B2 1 0 A 2 1 0
B A
S URF
DCF
DCF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
Horizonma cro CABINET

ti-GSM-carrier_omni_d up lexed _hybrid_and_air_combi ning -00189-ai-sw
Table 12-24 Equipment required for 1 cabinet, 4 CTU conguration, duplexed hybrid
and air combining
Quantity
Equipment
Antennas
Horizon macro cabinet
CTU
Receiver
SURF
DCF
68P02900W21-R
12-51
GMR-01
Nov 2007
[DCS1800] 6 carrier omni, with duplexed dual-stage hybrid and air

combining
Figure 12-42 shows a single cabinet, six CTU conguration with duplexed dual-stage hybrid and
air combining. Table 12-25 provides a summary of the equipment required for this conguration.
Figure 12-42 6 carrier omni, duplexed dual-stage hybrid and air combining
Tx/Rx
ANTENNA
A
Tx/Rx
ANTENNA
B
B2 1 0 A2 1 0
B A
S URF
FEED
THROUGH
DDF
C
T
U
A
B
C
T
U
C
T
U
A
B
A
B
C
T
U
A
B
DDF
C
T
U
A
B
C
T
U
A
B

ti-GSM-carrier_omni_d up lexed_dual-st age_h ybrid_and _air_combining-00190-ai-sw
Table 12-25 Equipment required for 1 cabinet, 6 CTU conguration, duplex

dual-stage hybrid and air combining
Quantity
Equipment
Antennas
Horizonmacro cabinet
CTU
Receiver
SURF
Continued
12-52
68P02900W21-R
GMR-01
Nov 2007

dual-stage hybrid and air combining (Continued)
Equipment
Quantity
2
DDF
Feed through, with two

through connectors
[DCS1800] 2 sector (3/3), with duplexed dual-stage hybrid combining

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

Tx/Rx
ANTENNA
(SEC TOR 1)
B
Tx/Rx
ANTENNA
(SEC TOR 2)
B
Rx
ANTENNA
(SEC TOR 1)
A
B2 1 0
Rx
ANTENNA
(SEC TOR 2)
A
A2 1 0
BA
SURF
FEED
THROUGH
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
DDF
C
T
U
A
B
C
T
U
A
B
Horizonmacro CABINET
ti-GSM-2_sector_(3/3)_duplexed_dual-stage_hybrid_combining-00191-ai-sw
68P02900W21-R
12-53
GMR-01
Nov 2007
Table 12-26 Equipment required for 1 cabinet, 6 CTU conguration, duplexed

dual-stage hybrid combining
Quantity
Equipment
Antennas
CTU
Receiver
SURF
DDF

through connectors
[DCS1800] 2 sector (6/6), with duplexed dual-stage hybrid and air

combining
shows a dual cabinet, 12 CTU conguration with duplexed dual-stage hybrid and air combining.
Table 12-27 Equipment required for dual cabinet, 12 CTU conguration, duplexed
Quantity
Equipment
Antennas
12
CTU
Receiver
SURF
DDF

through connectors
12-54
68P02900W21-R
GMR-01
Nov 2007
Figure 12-44 2 sector (6/6), duplexed dual-stage hybrid and air combining
Tx/Rx
ANTENNA
(SEC TOR 1)
A
B2 1 0
A2 1 0
Tx/Rx
ANTENNA
(SEC TOR 1)
B
Tx/Rx
ANTENNA
(S ECTOR 2)
Tx/Rx
ANTENNA
(S ECTOR 2)
A
B A
B2 1 0
SURF
A2 1 0
B A
S URF
FEE D
THROUGH
FE ED
THROUGH
DDF
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
DDF
C
T
U
A
B
A
B
C
T
U
A
B
EXTENDER Horizonmacr o CABINET
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
MAS TER Ho rizonma cro CABINET
ti-GSM-2_sector_(6/6)_dup lexed_dual-st age_h ybrid_and _air_combining-0 0192-ai-sw
[DCS1800] 3 sector (2/2/2), with duplexed hybrid combining

Figure 12-45 shows a single cabinet, six CTU conguration with duplexed hybrid combining.
68P02900W21-R
12-55
GMR-01
Nov 2007
Figure 12-45 3 sector (2/2/2), duplexed hybrid combining

Tx/Rx
ANTENNA
(SEC TOR 3)
Tx/Rx
ANTENNA
(SEC TOR 2)
Tx/Rx
Rx
Rx
Rx
ANTENNA ANTENNAS ANTENNAS ANTENNAS
(SEC TOR 1) (S ECTOR 3) (S ECTOR 2) (S ECTOR 1)
B2 1 0
A2 1 0
B A
S URF
C
T
U
C
T
U
A
B
DCF
DCF
DCF
C
T
U
A
B
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B

ti-GSM-2_3 sector (2/2/2)_dup lexed_hybrid_combinin g-00193-ai-sw
Table 12-28 Equipment required for 1 cabinet, 6 CTU conguration, duplexed hybrid
combining
Quantity
Equipment
Antennas
CTU
Receiver
SURF
DCF
12-56
68P02900W21-R
GMR-01
Nov 2007
[DCS1800] 3 sector (4/4/4), with duplexed hybrid and air combining

Figure 12-46 shows a dual cabinet, 12 CTU conguration with duplexed hybrid and air
Figure 12-46 3 sector (4/4/4), duplexed hybrid and air combining

Tx/Rx
Tx/Rx
ANTENNA ANTENNA
(SEC TOR 3) (SEC TOR 1)
A B
A
Tx/Rx
ANTENNA
(SE CTOR 1)
B
Tx/Rx
ANTENNA
(S ECTOR 2)
A
B
B2 1 0 A 2 1 0 B A
B2 1 0 A 2 1 0 B A
SURF
SURF
DCF
C
T
U
A
B
DCF
C
T
U
A
B
C
T
U
A
B
DCF
C
T
U
A
B
C
T
U
A
B
DCF
C
T
U
A
B
C
T
U
A
B
EXTENDER Ho rizonma cro CAB INET
C
T
U
A
B
DCF
DCF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
MASTER Horizonma cro CABINET
ti-GSM-3_sector_(4/4/4)_duple xed_hybrid_and_air_combining-0019 4-ai-sw
68P02900W21-R
12-57
GMR-01
Nov 2007
Table 12-29 Equipment required for dual cabinet, 12 CTU conguration duplexed
hybrid and air combining
Quantity
Equipment
Antennas
12
CTU
SURF
DCF
[DCS1800] 3 sector (8/8/8), with duplexed dual-stage hybrid and air

combining
and Figure 12-48 show a four cabinet, 24 CTU conguration with duplexed dual-stage hybrid
and air combining.

Quantity
Equipment
Antennas
24
CTU
Transmitter
Hybrid combiner unit (HCU)

Receiver
SURF
DDF
12-58
68P02900W21-R
GMR-01
Nov 2007
Figure 12-47 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 1)
Tx/Rx
ANTENNA
(S ECTOR 3)
Tx/Rx
ANTENNA
(S EC TOR 3)
B2 1 0 A2 1 0
TO
SU RF EXT A EXTENDER 1
Horizon mac ro
SU RF B0
CABINET
Tx/Rx
ANTENNA
(S EC TOR 1)
A
B2 1 0
B A
SU RF
A2 1 0
B A
SU RF
HCU
HCU
DDF
C
T
U
A
B
HCU
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
DDF
C
T
U
A
B
A
B
EXTENDER 3 Horizo nm acr o

CABINET
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
EXTENDER 2 Horizonm acr o

CABINET
ti-GSM-3_sector_(8/8/8)_duple xed_dual-stage_hybrid_and _air_combining_(Part 1)-00195-ai-sw
68P02900W21-R
12-59
GMR-01
Nov 2007
Horizoncompact2
Figure 12-48 3 sector (8/8/8), duplexed dual-stage hybrid and air combining (Part 2)
SURF A0
TO EXTENDER 2
Horizonmacro CABINET SURF EXT B
Tx/Rx
Tx/Rx
ANTENNA ANTENNA
(SE CTOR 2) (SEC TOR 2)
Tx/Rx
ANTENNA
(SEC TOR 1)
B2 1 0 A 2 1 0 B A
B2 1 0 A 2 1 0
SURF
BA
SURF
HCU
HCU
HCU
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
DDF
DDF
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
EXTENDER 1 Ho rizonmacro CABINET
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
C
T
U
A
B
MASTER Ho rizonmacro CABINET
ti-GSM-3_sector_888_du plexed_du al-stage_h ybrid_a ir_combi ning _Part_2-00196-ai-sw
Horizoncompact2
The Horizoncompact2 BTS system comprises a BTS enclosure and a booster enclosure. One
or two additional Horizoncompact2 BTS systems can be added as slaves to provide a two or
three BTS site.
12-60
68P02900W21-R
GMR-01
Nov 2007
Horizoncompact2
The Horizoncompact2 BTS system supports the following site congurations 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, and 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 congurations are supported when GSM900 and DCS1800
Horizoncompact2 BTSs are used:
2 BTS site
One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
3 BTS site
Two BTSs with four GSM900 carriers and one BTS with two DCS1800 carriers.
or
Two BTSs with four DCS1800 carriers and one BTS with two GSM900 carriers.
[GSM900/DCS1800] Horizoncompact2 single BTS system

Figure 12-49 shows the conguration for a single Horizoncompact2 BTS system.
68P02900W21-R
12-61
GMR-01
Nov 2007
Horizoncompact2
Figure 12-49 Horizoncompact2 single BTS system

Tx2
ANTENNA
Tx1/Rx
ANTENNA
ANT
ANT
DUPLEXER
Rx
Tx
FILTER
Tx
AMP
AMP
Horizoncompact2 BOOSTER
Rx
Rx IN
DINO / RHINO
Tx2
Tx1
ISOLATOR
MODULE
ISOLATOR
MODULE
Tx2 OUT
Tx1 OUT
DTRX
Horizoncompact2 BTS
ti-GSM-Horizoncompact2_single_BTS_system-00197-ai-sw
12-62
68P02900W21-R
GMR-01
Nov 2007
Horizoncompact2
[GSM900/DCS1800] Horizoncompact2 two BTS system

Figure 12-50 shows the conguration for a two Horizoncompact2 BTS system using ber 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
ANTENNA
Tx1/Rx
ANTENNA
Horizon compa ct2 BOOSTER
Tx2
ANTENNA
Tx1/Rx
ANTENNA
Horizoncompa ct2 BOOS TER
DINO / RHINO
DINO / RHINO
Horizon compa ct2 MASTER BTS
Horizoncompa ct2 S LAVE BTS
FIBRE OPTIC LINK
ti-GSM-Horizoncompact2_two_BTS_system-00198-ai-sw
[GSM900/DCS1800] Horizoncompact2 three BTS system

Figure 12-51 shows the conguration for a three Horizoncompact2 BTS system using ber 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.
68P02900W21-R
12-63
GMR-01
Nov 2007
Horizoncompact2
Figure 12-51 Horizoncompact2 three BTS system

Tx2
Tx1/Rx
ANTENNA ANTENNA
Horizoncompa ct2 BOOSTE R
DINO / RHINO
Tx2
Tx1/Rx
Tx2
Tx1/Rx
ANTENNA ANTENNA ANTENNA ANTENNA
DINO / RHINO
Horizoncompa ct2 MAS TER BTS
FIBRE OPTI C LINK
FIBRE OPTI C LINK

DINO / RHINO
ti-GSM-Horizonc ompact2_t hree_BTS_system-00199-ai-sw
12-64
68P02900W21-R
GMR-01
Nov 2007
Microcell RF congurations
Microcell RF congurations
Horizonmicro2
The Horizonmicro2 BTS is like the Horizoncompact2, but does not include (or support) a booster
enclosure. One or two additional Horizonmicro2 BTSs can be added as slaves to provide a
two or three BTS site.
The Horizonmicro2 BTS supports the following site congurations 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 congurations are supported when GSM900 and DCS1800
Horizonmicro2 BTSs are used:
2 BTS site
One BTS with two GSM900 carriers and one BTS with two DCS1800 carriers.
3 BTS site
Two BTSs with four GSM900 carriers and one BTS with two DCS1800 carriers.
Or
Two BTSs with four DCS1800 carriers and one BTS with two GSM900 carriers.
[GSM900/DCS1800] Horizonmicro2 single BTS system

Figure 12-52 shows the conguration for a single Horizonmicro2 BTS system.
68P02900W21-R
12-65
GMR-01
Nov 2007
Horizonmicro2
Figure 12-52 Horizonmicro2 single BTS system

Tx1/Tx2/Rx
ANTENNA
ANT
DUPLEXER
Rx
Tx
COMBINER/
IS OLATOR
MODULE
Tx Tx
Rx IN
DINO / RHINO
Tx2 OUT
Tx
Tx1 OUT
DTRX
Horizonmicro2 BTS
ti-GSM-Horizo nmicro 2_s ingle _BTS_ syst e m-00200-a i-sw
[GSM900/DCS1800] Horizonmicro2 two BTS system

Figure 12-53 shows the conguration for a two Horizonmicro2 BTS system using ber optic
cables. An HDSL option is available, which allows the BTSs to be connected through HDSL
links. Refer to Figure 12-52 for internal connections within the BTS.
Figure 12-53 Horizonmicro2 two BTS system

Tx1/Tx2/Rx
ANTENNA
Tx1/Tx2/Rx
ANTENNA
DINO / RHINO
DINO / RHINO
Horizon micro2 MASTER BTS
Horizon micro2 SLAVE BTS
FIBRE O P TIC LINK
12-66
ti-GSM-Horizonmicro2_two_BTS_system-00201-ai-sw
68P02900W21-R
GMR-01
Nov 2007
Horizonmicro2
[GSM900/DCS1800] Horizonmicro2 three BTS system

Figure 12-54 shows the conguration for a three Horizonmicro2 BTS system using ber optic
cables. An HDSL option is available, which allows the BTSs to be connected through HDSL
links. Refer to Figure 12-52 for internal connections within the BTS.
Figure 12-54 Horizonmicro2 three BTS system

Tx1/Tx2/Rx
ANTENNA
Tx1/Tx2/Rx
ANTENNA
DINO / RHINO
Tx1/Tx2/Rx
ANTENNA
DINO / RHINO
Horizonmicro2 MASTER BTS
Horizonmicro2 SL AVE BTS
FIBRE OPTIC L INK
FIBRE OPTIC LINK

DINO / RHINO
Horizonmicro2 SL AVE BTS
ti-GSM-Horizonmicro2_three_BTS_system-00202-ai-sw
68P02900W21-R
12-67
GMR-01
Nov 2007
Connecting Horizon II macro cabinets to Horizonmacro cabinets Chapter 12: Standard BSS and Horizon BTS congurations
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 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 the CSFP
Examples of mixed cabinet congurations

Figure 12-55 to Figure 12-60 are examples of possible congurations for mixed Horizon II
macro and Horizonmacro cabinets.
12-68
68P02900W21-R
GMR-01
Nov 2007
Sector 4/4 conguration using two cabinets

Figure 12-55 shows the conguration for sector 4/4, using one Horizon II macro cabinet with
duplexers and one Horizonmacro cabinet.
Figure 12-55 Sector 4/4 conguration with Horizon II macro and Horizonmacro
cabinets
S ECTOR 2
SECTOR 1
RX
2B
RX
1B
RX
0B
EXP EXP RX
B
A
0A
RX
1A
RX
2A
2B
1B
0B 2A 1A
0A
S URF
SURF2
RX
ANT
BLANK
DCF
DCF
ANT
BLANK
DUP
BLANK
BLANK
DUP
EMPT Y
E MP TY
CTU2
EMPT Y
E MP TY
CTU2
SITE EXPANSION
BOARD
Horizon II mac ro
master cabinet
EXT
RX
BLANK
HIISC
FMUX
Horizonmacro
slave cabinet
ti-GSM-Sector4/4_c onfigura tion_with_Horizo nIIma cro _a nd_Horizonma cro -00203-a i-sw
68P02900W21-R
12-69
GMR-01
Nov 2007
Sector 6/6 conguration using two cabinets

Figure 12-56 shows the conguration for sector 6/6, using one Horizon II macro cabinet with
duplexers and hybrid combiner units and one Horizonmacro cabinet.
Figure 12-56
cabinets
Sector 6/6 conguration with Horizon II macro and Horizonmacro
SECTOR 1
RX
2B
RX
1B
RX
0B
SECTOR 2
EXP EXP RX
B
A
0A
RX
1A
RX
2A
2B
1B
0B 2A 1A
0A
EXT
SURF
SURF2
4
HCU
RX
ANT
DUP
BLANK
2
HCU
DDF
FTHRU
DDF
RX
ANT
DUP
BLANK
LOAD
EMPTY
EMPTY
CTU2
EMPTY
CTU2
SITE EX PANSION
BOARD
CTU2
HIISC
Horizon II macro
master cabinet
FMUX
Horizonmacro
slave cabinet
ti-GSM-Sector6/6_configuration_with_HorizonIImacro_and_Horizonmacro-00204-ai-sw
12-70
68P02900W21-R
GMR-01
Nov 2007
Sector 2/2/2 conguration using two cabinets

Figure 12-57 and Figure 12-58 show the congurations 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 conguration (Horizon II macro as master cabinet)

SECTOR 1
RX
2B
RX
1B
RX
0B
S ECTOR 3
EXP EXP RX
0A
B
A
RX
1A
RX
2A
S ECTOR 2
2B
1B
0B 2A 1A
0A
B
EXT
S URF
SURF2
BLANK
DCF
DCF
RX
ANT
DUP
BLANK
BLANK
BLANK
BLANK
BLANK
EMP TY
E MP TY
EMP TY
EMP TY
E MP TY
SITE EXPANS ION

BOARD
CTU2
HIISC
Horizon II macro
master cabinet
FMUX
Horizonmacro
slave cabinet
ti-GSM-Sector2/2/2_configuration_HorizonIImacro_as_master_cabinet-00205-ai-sw
68P02900W21-R
12-71
GMR-01
Nov 2007
Figure 12-58 Sector 2/2/2 conguration (Horizonmacro as master cabinet)

SECT
OR3
RX
2B
RX
1B
RX
0B
SECT
OR2
EXP EXP RX
B
A
0A
RX
1A
RX
2A
SECT
OR1
2B 1B
0B 2A 1A
0A
SURF
SURF2
EXT
BLANK
DCF
DCF
RX
BLANK
BLANK
BLANK
BLANK
BLANK
ANT
DUP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
CTU2
SITE EX PANSION
BOARD
XMUX
Horizon II macro
slave cabinet
MCUF
Horizonma cro
ma st e r ca bine t
ti-GSM-Sector222_confi gura tion_Horizonma cro_a s _ma s te r_ca bine t-00206-a i-s w
12-72
68P02900W21-R
GMR-01
Nov 2007

Figure 12-59 shows the conguration for sector 4/4/4, using one Horizon II macro cabinet
with duplexers and one Horizonmacro cabinet.
Figure 12-59 Sector 4/4/4 conguration with Horizon II macro and Horizonmacro
cabinets
SECTOR 2
RX
2B
RX
1B
RX
0B
EXP EXP
B
A
RX
0A
RX
1A
RX
2A
2B
1B
0B 2A 1A
0A
RX
RX
BLANK
ANT
DUP
ANT
DUP
EMP TY
CTU2
CTU2
RX
RX
BLANK
ANT
DUP
ANT
DUP
EMP TY
CTU2
CTU2
SITE EXPANSION
BOARD
BLANK
HIIS C
Horizon II macro
master cabinet
EXT
S URF
SURF2
S ECTOR 3
SEC TOR 1
DCF
DCF
FMUX
Horizonmacro
slave cabinet
ti-GSM-Se ctor4/4/4_configura tion_with_Horizo nIIma cro _a nd_ Horizo nma cro _ca bine ts-0 0207-a i-sw
68P02900W21-R
12-73
GMR-01
Nov 2007

Figure 12-60 shows the conguration 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 conguration with Horizon II macro and Horizonmacro
cabinets
SECTOR 2
RX
2B
SECTOR 1
RX
1B
RX
0B
EXP EXP
B
A
RX
0A
RX
1A
SEC TOR 3
RX
2A
2B
1B
0B 2A 1A
0A
SU RF
5
DHU
BLANK
2
DHU
RX
ANT
DUP
BLANK
EXT
DDF
FTHRU
DDF
RX
ANT
DUP
CTU2
CTU2
CTU2
CTU2
CTU2
CTU2
SITE EX PANSION
BOARD
Horizon II mac ro
master cabinet
HIISC
FMUX
Horizonma cro
sla ve ca bine t
ti-GSM-Sector6/6/6_configuration_with_HorizonIImacro_and_Horizonmacro_cabinets-00208-ai-sw
12-74
68P02900W21-R
GMR-01
Nov 2007
Using CTU2s in Horizonmacro cabinets

Figure 12-61 shows an example of a conguration with CTU2s (operating in single density
mode) installed in a Horizonmacro cabinet.
Figure 12-61
Horizonmacro cabinet conguration using CTUs and CTU2s
SEC TOR 3
S ECTOR 2
2B
1B
0B 2A 1A
SE CTOR 1
0A
A
EXT
SURF
DCF
DCF
DCF
CTU2 CTU2
5
Horizon ma cro c a binet
0
MCUF
ti-GSM-Horizonmacro_ cabinet_using_ CTUs_ and_ CTU2s-00209-ai-sw
68P02900W21-R
12-75
GMR-01
Nov 2007
Connecting Horizon II macro cabinets to M-Cell6 cabinets
Connecting Horizon II macro cabinets to M-Cell6

cabinets
Connection overview
This section provides the 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.
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 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 the 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 the 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.
900 MHz BTSs

Figure 12-62 shows how a 900 MHz Horizon II macro BTS cabinet can be connected to a 900
MHz M-Cell6 BTS cabinet to create a 2 sector (4/4) conguration.
12-76
68P02900W21-R
GMR-01
Nov 2007
Figure 12-62 900 MHz Horizon II macro and 900 MHz M-Cell6 interconnections
DUP LE XE R
SE CTOR 2
DUP LE XE R
SE CTO R 1
RX RX RX EXP EXP RX RX RX
2B 1B 0B B
A
0A 1A 2A
DLNB
SU RF2
IADU
RX
0
RX
ANT
ANT
BLANK
BLANK
DUP
BLANK
BLANK
DUP
EMPTY
EMPTY
CTU2
EMPTY
EMPTY
CTU2
Horizon II macro
mas ter c abin et
SITE EXPANS ION

BOARD
BLANK
CBF1
T
C
U
T
C
U
CBF0
T
C
U
T
C
U
FMUX
HIIS C
M-Cell6 s lave cabi net

ti-GSM-900_MHz_ Horizon IIma cro _a nd_M-Ce ll6_inte rco nne ctions-0 0210-a i-sw
68P02900W21-R
12-77
GMR-01
Nov 2007
1800 MHz BTSs

Figure 12-63 shows how a 1800 MHz Horizon II macro BTS cabinet can be connected to a 1800
MHz M-Cell6 BTS cabinet to create a 2 sector (4/4) conguration.
Figure 12-63 1800 MHz Horizon II macro and 1800 MHz M-Cell6 interconnections
DUP LE XE R
SE CTOR 2
DUP LE XE R
SE CTO R 1
RX RX RX EXP EXP RX RX RX
2B 1B 0B B
A 0A 1A 2A
LNA
SU RF2
RX
0
RX
ANT
ANT
BLANK
DUP
BLANK
BLANK
DUP
EMP TY EMP TY
CTU2
EMP TY
EMP TY
CTU2
BLANK
Horizon II macro
mas ter c abin et
SITE E XPANS ION

BOARD
BLANK
CBF1
T
C
U
T
C
U
CBF0
T
C
U
T
C
U
FMUX
HIIS C
M-Cell6 s lave cab inet

ti-GSM-1800MHz_HorizonIImacro_and_M-Cell6_interconnections-00253-ai-sw
12-78
68P02900W21-R
GMR-01
Nov 2007
Chapter
13
M-Cell BTS congurations
This chapter 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
congurations. Examples of how M-Cell equipment is connected to current generation Horizon
equipment are provided in Chapter 12 Standard BSS and Horizon BTS congurations.
The topics described here are as follows:
Standard M-Cell congurations on page 13-2
Single cabinet BTS congurations on page 13-3
Two cabinet BTS conguration on page 13-5
Three cabinet BTS conguration on page 13-7
Four cabinet BTS conguration on page 13-8
M-Cell RF congurations on page 13-9
68P02900W21-R
Nov 2007
13-1
GMR-01
Standard M-Cell congurations
Standard M-Cell congurations
The examples in this section are shown with individual antennas for transmit and receive
signals. Duplexers are required if individual antennas are not used. However, duplexers can
result in performance degradation. For carrier redundancy, the RF carrier equipment must be
duplicated for each BTS.
The diagrams that follow do not indicate the maximum capacity or a typical conguration
using that specic equipment. The diagrams highlight the congurations that are feasible
when the macrocell hardware is deployed in an M-Cell BTS, within the constraints of the BSS
architecture. The diagrams also show possible cabinet boundaries. Cabinet designs, however,
allow for some different arrangements of the same conguration.
For typical BSS congurations, refer to Figure 12-1 and Figure 12-2 in
Chapter 12 Standard BSS and Horizon BTS congurations.
The control redundancy is depicted only for one M-Cell6, and one M-Cell2
cabinet diagram (refer to Figure 13-1 and Figure 13-2).
13-2
68P02900W21-R
GMR-01
Nov 2007
Single cabinet M-Cell6 BTS

The conguration shown in Figure 13-1 is an example of a single cabinet M-Cell6 BTS. This
conguration supports six carriers.
Figure 13-1 Single cabinet M-Cell6 BTS
N
I
U
mBCU
N
I
U
MCU
MCU
12
12
F
O
X
F
O
X
mBCU
(FOR
RE DUNDANCY)
12
12
T
C
U
T
C
U
T
C
U
2
T
C
U
T
C
U
2
T
C
U
M-CELL6 BTS CABINET

ti-GSM-BSC_single_ cabinet_M-cell_6_BTS-0021
68P02900W21-R
1-ai-sw
13-3
GMR-01
Nov 2007

The conguration shown in Figure 13-2 is an example of a single cabinet M-Cell2 BTS. This
conguration supports two carriers.
Figure 13-2 Single cabinet M-Cell2 BTS
N
I
U
mBCU
N
I
U
mBCU
MCU
MCU
(FOR
RE DUNDANCY)
T
C
U
2
T
C
U
M-CELL2 CABINET
ti-GSM-Single_cabinet_M-Cell2_BTS-00212-ai-sw
13-4
68P02900W21-R
GMR-01
Nov 2007
Two cabinet BTS conguration
Two cabinet BTS conguration
Two cabinet M-Cell6 BTS

The conguration shown in Figure 13-3 is an example of a two cabinet M-Cell6 BTS. This
conguration 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
BTS CABINET
mBCU
N
I
U
F
M
U
X
12
MCU
12
F
O
X
12
2
T
C
U
M-CELL6
BTS CABINET
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
12
2
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
mBCU
F
O
X
F
M
U
X
ti-GSM-BTwo_cabinet_M-Cell6_BT S-00213-ai-sw
68P02900W21-R
13-5
GMR-01
Nov 2007

The conguration shown in Figure 13-4 is an example of a two cabinet M-Cell6 BTS when
CTU2 Adapters are used. This conguration 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
BTS CABINET
mBCU
N
I
U
F
M
U
X
12
MCU
12
F
O
X
12
2
T
C
U
M-CELL6
BTS CABINET
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
12
2
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
mBCU
F
O
X
F
M
U
X
ti-GSM-Two_cabinet_M-Cell6_BT S_with_CTU2_Adapters-00214-ai-sw
13-6
68P02900W21-R
GMR-01
Nov 2007
Three cabinet BTS conguration
Three cabinet BTS conguration
Three cabinet M-Cell2 BTS

The conguration shown in Figure 13-5 is an example of a three cabinet M-Cell2 BTS. This
conguration supports six carriers.
Figure 13-5 Three cabinet M-Cell2 BTS
MCU
M-CELL2 CABINET
mBCU
N
I
U
12
F
O
X
12
2
T
C
U
2
T
C
U
M-CELL2 CABINET
2
T
C
U
T
C
U
M-CELL2 CABINET
2
T
C
U
T
C
U
ti-GSM-Three cabinet M-Cell2 BTS-00215-ai-sw
68P02900W21-R
13-7
GMR-01
Nov 2007
Four cabinet M-Cell6 BTS

The conguration shown in Figure 13-6 is an example of a four cabinet M-Cell6 BTS. This
conguration supports 24 carriers. The MCUs interface to the TCUs through the FOX or the
FMUX/FOX.
Figure 13-6 Four cabinet M-Cell6 BTS

M-CELL6
BTS CABINET
mBCU
N
I
U
F
M
U
X
12
MCU
F
M
U
X
12
12
F
M
U
X
12
F
O
X
12
2
T
C
U
T
C
U
M-CELL6
BTS
CABINET
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
mBCU
F
M
U
X
F
O
X
T
C
U
T
C
U
12
2
T
C
U
T
C
U
M-CELL6
BTS
CABINET
12
2
T
C
U
M-CELL6
BTS
CABINET
T
C
U
T
C
U
T
C
U
mBCU
F
M
U
X
F
O
X
T
C
U
12
2
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
2
T
C
U
mBCU
F
O
X
F
M
U
X
ti-GS M-Four_ca bine t_M-Ce ll6_BTS -00216-a i-s w
13-8
68P02900W21-R
GMR-01
Nov 2007
M-Cell RF congurations
M-Cell RF congurations
Overview
The M-Cell BTS cabinets can be congured 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 congurations shown in
Figure 13-7 to Figure 13-42:
An M-Cell6 BTS cabinet accommodates a maximum of six TCUs.
An M-Cell6 BTS cabinet accommodates a maximum of twelve carriers when CTU2

Adapters are used.
An M-Cell2 BTS cabinet accommodates a maximum of two TCUs.
An external equipment cabinet is not required, unless specically stated in the text
accompanying the conguration diagram.
An M-Cell6 side cabinet accommodates a maximum of three high power duplexers.
M-Cell6 cabinets
Diversity is assumed in all gures, unless stated otherwise.
[GSM900] 3 carrier omni, with hybrid combining and diversity

A single cabinet, four TCU conguration with hybrid combining and diversity, is shown in
Figure 13-7. Table 13-1 provides a summary of the equipment required for this conguration.
68P02900W21-R
13-9
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-7
3 carrier omni, hybrid combining

Tx ANTENNA
Rx ANTENNAS
DLNB
IADU
RF INPUT
RF LOAD
3-INP UT
CBF
NonHCOMB
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
M-Ce ll6 BTS CABINET
ti-GSM-3_carrier_omni,_hybrid_combining-00217-ai-sw
Table 13-1 Equipment required for single cabinet, 4 TCU conguration with hybrid
combining and diversity
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF
Non-hybrid combiner (Non-HCOMB)

Receiver
DLNB
13-10
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
[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 INPU T
RF LOAD
IADU
3-INP UT
CBF
Non HCOMB
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
ti-GSM-3_carrier_omni,_hybrid_combining,_medium_power_duplexer-00218-ai-sw
combining, diversity and medium power duplexer
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF

Continued
68P02900W21-R
13-11
GMR-01
Nov 2007
M-Cell6 cabinets
combining, diversity and medium power duplexer (Continued)
Equipment
Quantity
Receiver
DLNB
1
Medium power duplexer
[GSM900] 4 carrier omni, with hybrid combining and diversity

Figure 13-9
4 carrier omni, hybrid combining

Tx ANTENNA
Rx ANTENNAS
DLNB
RF INPUT
IADU
RF LOAD
3-INP UT
CBF
HCOMB
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
ti-GSM-4_carrier_omni,_hybrid_combining-00219-ai-sw
13-12
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF
Hybrid combining block (HCOMB)

Receiver
DLNB
[GSM900] 4 carrier omni, with hybrid combining, diversity, and medium

power duplexer
A single cabinet, four TCU conguration 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 conguration.
Figure 13-10 4 carrier omni, hybrid combining, medium power duplexer

Tx/Rx ANTENNA
Rx ANTENNA
DUPLE XER
RF INP UT
RF LOAD
DLNB
3-INPUT
CBF
HCOMB
IADU
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
ti-GSM-4_carrier_omni,_hybrid_combining,_medium_power_duplexer-00220-ai-sw
68P02900W21-R
13-13
GMR-01
Nov 2007
M-Cell6 cabinets
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF
Hybrid combining block (HCOMB)

Receiver
DLNB
1
[GSM900] 6 carrier omni, with cavity combining and diversity

Table 13-5 provides a summary of the equipment required for this conguration. A single
cabinet, six TCU conguration with cavity combining and diversity, is shown in Figure 13-11.
Table 13-5 Equipment required for single cabinet, 6 TCU conguration with cavity
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
CCB (Output)
CCB (Extension)
Receiver
DLNB
13-14
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-11 6 carrier omni, cavity combining

Tx ANTENNA
Rx ANTENNAS
DLNB
CC B
CC B
(OUTP UT)
(EXTENS ION)
IADU
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B

ti-GSM-6_carrier_omni,_cavity_combining-00221-ai-sw
[GSM900] 6 carrier omni, with cavity combining, diversity, and high

power duplexer
A single cabinet, six TCU conguration with cavity combining, diversity, and high power
An external equipment rack/cabinet is required for a high power duplexer in an indoor
installation.
68P02900W21-R
13-15
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-12
6 carrier omni, cavity combining, high power duplexer
Rx
ANTENNA
Tx/Rx
ANTENNA
DLNB
ANT
IADU
CCB
(EXTENSION)
6
Rx
CCB
(OUTPU T)
Tx
HIGH P OWER
DUP LEXER
T
C
U
A
B
T
C
U
A
B
T
C
U
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
A
B
M-Cell6 BTS CABINET
M-Ce ll6 SIDE CABINET
ti-GSM-6_carrier_omni,_cavity_combining,_high_power_duplexer-00222-ai-sw
Table 13-6 Equipment required for single cabinet, 6 TCU conguration with cavity
combining, diversity and high power duplexer
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
M-Cell6 side cabinet
`
6
TCU
Transmitter
CCB (Output)
CCB (Extension)
Receiver
DLNB
1
High power duplexer
13-16
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
[GSM900] 8 carrier omni, with combining and diversity

A dual cabinet, 8 TCU conguration with combining and diversity, is shown in Figure 13-13.
Figure 13-13 8 carrier omni, combining

Tx
ANTENNA
Tx/Rx
ANTENNA
Rx
ANTENNA
DUP LEXER
Rx EXT
BLOCK
DLNB
IADU
CBF
IADU
CCB
(EXTENSION)
CCB
(OUTPUT)
6
2
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
EXTENDER M-Cell6 BTS CABINET
MASTER M-Ce ll6 BTS CABINET

ti-GSM-8_carrier_omni,_combining-00223-ai-sw
Table 13-7 Equipment required for multiple cabinet, 8 TCU conguration with
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
CBF
CCB (Output)
CCB (Extension)
Continued
68P02900W21-R
13-17
GMR-01
Nov 2007
M-Cell6 cabinets
combining and diversity (Continued)
Equipment
Quantity
Receiver
1
DLNB
Rx extension block
[GSM900] 2 sector (3/3), with hybrid combining and diversity

A single cabinet, six TCU conguration with hybrid combining and diversity, is shown in
Figure 13-14.
Figure 13-14 2 sector (3/3), hybrid combining

Tx
ANTENNA
(S EC TOR 1)
Tx
ANTENNA
(S ECT OR 2)
Rx
ANTENNA
(S EC TOR 2)
Rx
ANTENNA
(S ECTOR 1)
DLNB
DLNB
RF INPUT
RF INPU T
RF LOAD
RF LOAD
3-INP UT
CBF
IADU
3-INP UT
CBF
NonHCOMB
6
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
M-Cell6 BTS CABINET
ti-GSM-2_sector_(3/3),_hybrid_combining-00224-ai-sw
13-18
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF

Receiver
DLNB
[GSM900] 2 sector (3/3), with hybrid combining, diversity, and medium

power duplexers
A single cabinet, six TCU conguration with hybrid combining, diversity, and medium power
duplexers, is shown in Figure 13-15. Table 13-9 provides a summary of the equipment required
Figure 13-15
2 sector (3/3), hybrid combining, medium power duplexers
Tx/Rx
ANTENNA
(SECTOR 2)
Tx/Rx
ANTENNA
(S ECTOR 1)
Rx
ANTENNA
(S ECTOR 2 )
Rx
ANTENNA
(S ECTOR 1)
DLNB
DLNB
DUP LEXER
DUP LEXER
RF INPUT
RF INPUT
RF LOAD
RF LOAD
IADU
3-INP UT
CBF
3-INPU T
CBF
Non HCOMB
6
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
M-Cell6 BTS CABINET
ti-GSM-2 sector_(3/3),_hybrid_combining,_medium_power_duplexers-00225-ai-sw
68P02900W21-R
13-19
GMR-01
Nov 2007
M-Cell6 cabinets
Table 13-9 Equipment required for single cabinet, 6 TCU conguration with
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
3-input CBF

Receiver
DLNB
2
[GSM900] 3 sector (2/2/2), with combining and diversity

cabinet, six TCU conguration with combining and diversity, is shown in Figure 13-16.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
CBF
Receiver
DLNB
13-20
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-16 3 sector (2/2/2), combining

Tx
ANTENNA
(SEC TOR 1)
Tx
ANTENNA
(SEC TOR 3)
Tx
ANTENNA
(SEC TOR 2)
Rx
ANTENNAS
(SEC TOR 1)
DLNB
Rx
ANTENNAS
(SEC TOR 2)
Rx
ANTENNAS
(SEC TOR 3)
DLNB
DLNB
IADU
CBF
CBF
CBF
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B

ti-GSM-3_sector_(2_2_2),_combining-00226-ai-sw
[GSM900] 3 sector (2/2/2), with cavity combining, diversity, and medium

power duplexers
A single cabinet, six TCU conguration with cavity combining, diversity, and medium power
68P02900W21-R
13-21
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-17
Tx/Rx
ANTENNA
(SEC TOR 3)
3 sector (2/2/2), combining, medium power duplexers

Tx/Rx
ANTENNA
(SEC TOR 2)
Tx/Rx
ANTENNA
(SEC TOR 1)
Rx
ANTENNA
(SEC TOR 3)
Rx
ANTENNA
(SEC TOR 2)
Rx
ANTENNA
(SEC TOR 1)
DLNB
DLNB
DLNB
DUPLE XER
DUPLEXER
DUPLEXER
IADU
CBF
CBF
CBF
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
ti-GSM-3_sector_(2_2_2),_combining,_medium_power_duplexers-00227-ai-sw
combining, diversity and medium power duplexers
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
CBF
Receiver
DLNB
3
13-22
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium

power duplexers (3 antenna per sector)
A dual cabinet, 12 TCU conguration with air combining, diversity, and medium power
Figure 13-18
Tx/Rx
Tx
Tx/Rx
ANTENNA ANTENNA ANTENNA
(SEC TOR 3) (SEC TOR 3)(SEC TOR 2)
DUPLEXER
Rx EXT
BLOCK
DLNB
Rx
Rx
Tx
Tx/Rx
Tx
ANTENNA
ANTENNA ANTENNA ANTENNA ANTENNA
(S ECTOR 2)(S ECTOR 1) (S ECTOR 1) (S ECTOR 2) (S ECTOR 1)
DUP LE XE R
DUP LE XE R
Rx
ANTENNA
(SEC TOR 2)
3 sector (4/4/4), air combining, medium power duplexers
DLNB
IADU
IADU
CBF2
6
DLNB
CBF1
CBF0
CBF2
CBF 1
CBF 0
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
EXTENDER M-Ce ll6 BTS CABINET
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
MAS TER M-Ce ll6 BTS CABINET
ti-GSM-3_sector_(4_4_4),_air_combining,_medium_power_duplexers-00228-ai-sw
Table 13-12 Equipment required for dual cabinet, 12 TCU conguration with air
combining, diversity and medium power duplexers (3 antenna per sector)
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
12
TCU
Transmitter
CBF
Continued
68P02900W21-R
13-23
GMR-01
Nov 2007
M-Cell6 cabinets
Table 13-12 Equipment required for dual cabinet, 12 TCU conguration with air
combining, diversity and medium power duplexers (3 antenna per sector) (Continued)
Equipment
Quantity
Receiver
3
DLNB
Rx extension block
[GSM900] 3 sector (4/4/4), with air combining, diversity, and medium

power duplexers (2 antenna per sector)
A multiple cabinet, 12 TCU conguration with air combining, diversity, and medium power
Figure 13-19 3 sector (4/4/4), air combining, medium power duplexers
DUP LE XE R
Tx/Rx ANTENNA
(S ECTOR 1)
DUP LE XE R
DUP LE XE R
DUP LE XE R
Rx EXT
BLOCK
DLNB
Tx/Rx ANTENNA (S ECTOR 2)
DUP LE XE R
DUP LE XE R
Tx/Rx ANTENNA
(SEC TOR 3)
DLNB
IADU
IADU
CBF2
6
DLNB
CBF1
CBF0
CBF 2
CBF 1
CBF 0
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
EXTENDER M-Ce ll6 BTS C ABINET
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
MAST ER M-Ce ll6 BTS CABINET
ti-GSM-3_sector_(4/4/4),_air_combining,_medium_power_duplexers-00229-ai-sw
13-24
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Table 13-13 Equipment required for multiple cabinet, 12 TCU conguration with air
combining, diversity and medium power duplexers (2 antenna per sector)
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
12
TCU
Transmitter
CBF
Receiver
DLNB
Rx extension block
[GSM900] 3 sector (4/4/4), with cavity combining and diversity

Table 13-14 provides a summary of the equipment required for this conguration. A multiple
cabinet, 12 TCU conguration with cavity combining and diversity, is shown in Figure 13-20.
hybrid combining and diversity
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
12
TCU
Transmitter
CCB (output)
CCB (extension)
Receiver
DLNB
68P02900W21-R
13-25
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-20 3 sector (4/4/4), cavity combining

Tx ANTENNA
(SE CTOR 1)
Rx ANTENNAS
(SE CTOR 1)
DLNB
IADU
CCB
CCB
(EXTENS ION)
(OUTPU T)
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
MASTER M-Cell6 CABINET
ti-GSM-3_sector_(4/4/4),_cavity_combining-00230-ai-sw
Extender 1 and extender 2 M-Cell6 cabinets congured similar to the master cabinet
for sectors 2 and 3.
[GSM900] 3 sector (4/4/4), with 3-input CBF, hybrid combining and

diversity
Table 13-15 provides a summary of the equipment required for this conguration. A dual
cabinet, 12 TCU conguration with 3-input CBF, hybrid combining and diversity, is shown
in Figure 13-21.
13-26
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Table 13-15 Equipment required for dual cabinet, 12 TCU conguration with 3-input
CBF, hybrid combining and diversity
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
12
TCU
Transmitter
3-input CBF
Hybrid combiner module (HCOMB)

Receiver
DLNB
Rx extension block
Figure 13-21 3 sector (4/4/4), 3-input CBF, hybrid combining

Rx
ANTENNA
(SEC TOR 3)
Tx
ANTENNA
(SEC TOR 3)
Tx
Tx
Rx
ANTENNA
ANTENNA ANTENNA
(S ECTOR 2) (S ECTOR 1) (S ECTOR 2)
RF INP UT
Rx
ANTENNA
(S ECTOR 1)
RF LOAD
Rx EXT
BLOCK
DLNB
DLNB
IADU
DLNB
IADU
RF INPUT
RF INP UT
RF LOAD
RF LOAD
HCOMB
3-INPUT
CBF
HCOMB
3-INP UT
CBF
HCOMB
3-INP UT
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
A
B
A
B
T
C
U
A
B
T
C
U
A
B
A
B
EXTENDER M-Cell6 BTS CABIN ET
A
B
T
C
U
A
B
A
B
T
C
U
A
B
A
B
A
B
MASTER M-Ce ll6 BTS C ABINET

ti-GSM-3_sector_(4/4/4),_3-input_CBF
68P02900W21-R
T
C
U
,_hybrid_combining-00231-ai-sw
13-27
GMR-01
Nov 2007
M-Cell6 cabinets
[GSM900] 3 sector (4/4/4), with 3-input CBF, air combining, diversity,

and medium power duplexers
A multiple cabinet, 12 TCU conguration 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
Figure 13-22 3 sector (4/4/4), 3-input CBF, air combining, medium power duplexers
Rx
ANTENNA
(S EC TOR 3)
Tx/Rx
ANTENNA
(S EC TOR 3)
Tx/Rx & Rx
ANTENNA
(S ECTOR 2)
RF INP UT
Tx/Rx
ANTENNA
(S ECTOR 1)
Rx
ANTENNA
(S ECTOR 1)
Rx EXT
BLOCK
DLNB
DUP LE XE R
DUP LE XE R
DUP LE XE R
RF LOAD
DLNB
IADU
IADU
RF INPUT
6
DLNB
RF INP UT
6
RF LOAD
RF LOAD
HCOMB
3-INP UT
CBF
HCOMB
3-INP UT
CBF
HCOMB
3-INP UT
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
A
B
A
B
T
C
U
A
B
T
C
U
A
B
A
B
A
B
T
C
U
A
B
A
B
EXTENDE R M-Ce ll6 BTS CABINET
T
C
U
A
B
A
B
T
C
U
A
B
,_air_combining,_medium_power_duplexers-00232-ai-sw
3-input CBF, air combining, diversity and medium power duplexers
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
12
TCU
Continued
13-28
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
3-input CBF, air combining, diversity and medium power duplexers (Continued)
Equipment
Quantity
Transmitter
3
3-input CBF

Receiver
DLNB
Rx extension block

and medium power duplexers (3 antenna per sector)
A three cabinet, 15 TCU conguration with 3-input CBF, air combining, diversity, and medium
power duplexers, is shown in Figure 13-23. Table 13-17 provides a summary of the equipment
Tx/Rx
ANTENNA
(SEC TOR 1)
Tx
ANTENNA
(S ECTOR 1)
Rx
ANTENNA
(S ECTOR 1)
DUPLEXER
RF INP UT
DLNB
RF LOAD
IADU
3-INPUT
CBF
3-INP UT
CBF
NonHCOMB
6
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
MAS TER M-Cell6 BTS CABINET
Exten de r 1 and exte nd e r 2 M-Cell6 ca binet s c onfigure d s imila r to the ma s te r

cabinet for sectors 2 a nd 3.
68P02900W21-R
13-29
GMR-01
Nov 2007
M-Cell6 cabinets
Table 13-17 Equipment required for 3 cabinets, 15 TCU conguration with 3-input
CBF, air combining, diversity and medium power duplexers (2 antennas/sector)
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
15
TCU
Transmitter
3-input CBF

Receiver
DLNB
3
[GSM900] 3 sector (5/5/5), with 3-input CBF, combining, diversity, and

medium power duplexers (2 antenna per sector)
Table 13-18 provides a summary of the equipment required for this conguration. A three
cabinet, 15 TCU conguration with 3-input CBF, combining, diversity, and medium power
duplexers, is shown in Figure 13-24.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
15
TCU
Transmitter
3-input CBF

Receiver
DLNB
6
13-30
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-24 3 sector (5/5/5), 3-input CBF, combining, medium power duplexers
Tx/Rx
ANTENNA
(S ECTOR 1)
Tx/Rx
ANTENNA
(S ECTOR 1)
DUP LEXER
DUPLE XER
RF INPUT
RF LOAD
3-INP UT
CBF
DLNB
3-INPU T
CBF
IADU
NonHCO MB
6
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
Exte nde r 1 a nd extender 2 M-Cel l6 cabin e ts configure d s imila r to the ma s te r

cabin e t for sectors 2 a nd 3.
,_combining,_medium_power_duplexers-00234-ai-sw
[GSM900] 3 sector (6/6/6), with cavity combining, diversity, and high

power duplexers
A multiple cabinet, 18 TCU conguration with cavity combining, diversity, and high power
for this conguration. An external equipment rack/cabinet is required for a high-power duplexer
in an indoor installation.
68P02900W21-R
13-31
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-25
3 sector (6/6/6), cavity combining, high power duplexers
Rx
ANTENNA
Tx/Rx
ANTENNA
DLNB
ANT
IADU
CCB
(EXTENSION)
6
Rx
CCB
(OUTPU T)
Tx
HIGH P OWER
DUP LEXER
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
MASTER M-Cell6 BTS CABINET
M-Ce ll6 S IDE CABINET
Exte nde r 1 a nd exte nd er 2 M-Cell6 cabine ts con figure d s imila r to the ma s te r ca bine t for se ctors 2 a nd 3.
Each exte nd er cabin et te rminates in a high p owe r duplexe r in the side ca bine t.
ti-GSM-3_sector_(6/6/6),_cavity_combining,_high_power_duplexers-00235-ai-sw
Table 13-19 Equipment required for 3 RF cabinets, 18 TCU conguration with cavity
combining, diversity and high power duplexers
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
18
TCU
Transmitter
CCB (output)
CCB (extension)
Receiver
DLNB
3
High power duplexer
13-32
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets

A three cabinet, 18 TCU conguration with 3-input CBF, air combining, diversity, and medium
Tx/Rx
ANTENNA
(SEC TOR 1)
Tx/Rx
ANTENNA
(SE CTOR 1)
DUP LEXER
DUP LEXER
RF INP UT
RF LOAD
3-INP UT
CBF
DLNB
3-INP UT
CBF
IADU
NonHCOMB
6
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
Exten de r 1 a nd exte nd er 2 M-Ce ll6 cab inets con figure d similar to the ma s te r
cab inet for sector s 2 an d 3.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
18
TCU
Transmitter
3-input CBF

Continued
68P02900W21-R
13-33
GMR-01
Nov 2007
M-Cell6 cabinets
(Continued)
Equipment
Quantity
Receiver
DLNB
3

A three cabinet, 18 TCU conguration with 3-input CBF, combining, diversity, and medium
Tx/Rx
ANTENNA
(SEC TOR 1)
Tx
ANTENNA
(S ECTOR 1)
Rx
ANTENNA
(S ECTOR 1)
DUPLEXER
RF INP UT
DLNB
RF INP UT
RF LOAD
RF LOAD
IADU
3-INPUT
CBF
3-INP UT
CBF
NonHCOMB
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
MAS TER M-Cell6 BTS CABINET

Exten de r 1 and exte nd e r 2 M-Cell6 ca binet s c onfigure d s imila r to the ma s te r
cabinet for sectors 2 a nd 3.
,_combining,_medium_power_duplexers-00237-ai-sw
13-34
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
CBF, combining, diversity and medium power duplexers (2 antennas/sector)
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
18
TCU
Transmitter
3-input CBF

Receiver
DLNB
6s
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and medium

power duplexers
Table 13-22 provides a summary of the equipment required for this conguration. A four
cabinet, 24 TCU conguration with cavity combining, diversity and medium power duplexers,
is shown in Figure 13-28 and Figure 13-29.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
24
TCU
Transmitter
CCB (output)
CCB (extension)
CBF
Receiver
DLNB
Rx extender block
68P02900W21-R
13-35
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-28
3 sector (8/8/8), cavity combining, medium power duplexers (Part 1)
ti-GSM-3_sector_(8/8/8),_cavity_combinin,_medium_power_duplexers (Part 1)-00238-ai-sw
13-36
68P02900W21-R
GMR-01
Nov 2007
Figure 13-29
M-Cell6 cabinets
3 sector (8/8/8), cavity combining, medium power duplexers (Part 2)

Rx
ANTENNA
(S ECTO R 1)
TO
MAS TER M-Cel l6
BTS CA BINET
Tx
ANTENNA
(S ECTO R 1)
DUPLEXE R 2
DUP LEXER 1
DUPLEXE R 0
Rx REV B LOCK 2
Rx REV B LOCK 1
Rx REV B LOCK 0
DLNB
IADU
CC B
(EXTENS ION)
CC B
(OUTPUT)
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
EXTENDER 1 M-Ce ll6 BTS C ABINET

Exte nde r 2 a nd extender 3 M-Ce ll6 ca bine ts c onfigure d s imilar to
the extender 1 ca bine t for s e ctors 2 and 3.
ti-GSM-3_sector_(8/8/8),_cavity_combining,_medium_power_duplexers_(Part 2)-00239-ai-sw
[GSM900] 3 sector (8/8/8), with cavity combining, diversity and both

high and medium power duplexers
A multiple cabinet, 24 TCU conguration with cavity combining, diversity and both high and
medium power duplexers, is shown in Figure 13-30 and Figure 13-31. Table 13-23 provides
a summary of the equipment required for this conguration.
An external equipment rack/cabinet is required for a high power duplexer in an indoor
installation.
68P02900W21-R
13-37
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-30 3 sector (8/8/8), cavity combining, high and medium power duplexers
(Part 1)
ti-GSM-3_sector_(8/8/8),_cavity_combining,_high)_and_medium_power_duplexers_(Part 1)-00240-ai-sw
13-38
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-31 3 sector (8/8/8), cavity combining, high and medium power duplexers
(Part 2)
TO MASTER
M-Cell6
BTS CABINET
DUPLEXER 2
DUPLEXER 1
DUPLEXER 0
RxREV B
LOCK2
RxREV B
LOCK1
RxREV B
LOCK0
Tx/Rx
Tx/Rx
ANTENNA ANTENNA
(SECTOR3) (SECTOR2)
Tx/Rx
ANTENNA
(SECTOR1)
EXTENDER 2 Cell6
M- BTSCABINET
EXTENDER 1 Cell6
M- BTSCABINET
EXTENDER 2 Cell6
M- BTSCABINET
EXTENDER 1 Cell6
M- BTSCABINET
DLNB
ANT
IADU
CCB
(EXTENSION)
CCB
(OUTPUT)
Rx
ANT
Tx
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
Rx
ANT
Tx
Rx
Tx
HIGHPOWER
DUPLEXERS
EXTEN
DER1 M-Cell6 BT
S 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.
ti-GSM-3_sector_(8/8/8),_cavity_combining,_high_and_medium_power_duplexers_(Part 2)-00241-ai-sw
combining, diversity and both high and medium power duplexers
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
24
TCU
Transmitter
CCB (output)
CCB (extension)
CBF
Continued
68P02900W21-R
13-39
GMR-01
Nov 2007
M-Cell6 cabinets
combining, diversity and both high and medium power duplexers (Continued)
Equipment
Quantity
Receiver
3
DLNB
Rx extender block
High power duplexer

Table 13-24 provides a summary of the equipment required for this conguration. A four
cabinet, 24 TCU conguration with 3-input CBF, air combining, diversity, and medium power
duplexers, is shown in Figure 13-32 and Figure 13-33.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
24
TCU
Transmitter
3-input CBF

Receiver
DLNB
Rx extender block
13-40
68P02900W21-R
GMR-01
Nov 2007
Figure 13-32
(Part 1)
M-Cell6 cabinets
3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers
IADU
Tx
ANTENNA
(SECTOR 3)
Tx/Rx
ANTENNA
(SEC TOR 3)
TO
EXTENDER 1
M-Ce ll6
BTS CAB INET
Rx
ANTENNA
(SEC TOR 3)
Tx
ANTENNA
(SEC TOR 2)
RF INP UT
DUP LE XE R
RF LOAD
Rx EXT
BLOCK
Rx EXT
BLOCK
DLNB
IADU
IADU
RF INPUT
RF INP UT
RF LOAD
RF LOAD
HCOMB
3-INPUT
CBF
HCOMB
3-INPU T
CBF
HCOMB
3-INPU T
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
A
B
A
B
EXTENDER 3 M-Ce ll6 BTS CABINET

T
C
U
A
B
A
B
T
C
U
A
B
A
B
T
C
U
A
B

,_air_combining,_medium_power_duplexers_(Part 1)-00242-ai-sw
68P02900W21-R
13-41
GMR-01
Nov 2007
M-Cell6 cabinets
Figure 13-33
(Part 2)
3 sector (8/8/8), 3-input CBF, air combining, medium power duplexers
TO EXTENDER 2
Rx EXT BLOCK
M-Cell6 BTS CABINET
Tx/Rx
ANTENNA
(SEC TOR 2)
Rx
ANTENNA
(SEC TOR 2)
Tx/Rx
ANTENNA
(SEC TOR 1)
Tx
ANTENNA
(SEC TOR 1)
RF INP UT
Rx
ANTENNA
(SEC TOR 1)
Rx EXT
BLOCK
DLNB
DUP LE XE R
DUP LE XE R
RF LOAD
DLNB
IADU
IADU
RF INPU T
RF INP UT
RF LOAD
6
RF LOAD
HCOMB
3-INPUT
CBF
HCOMB
3-INPU T
CBF
HCOMB
3-INPU T
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
A
B
T
C
U
A
B
A
B
A
B

T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
MASTER M-Ce ll6 BTS CABINET

,_air_combining,_medium_power_duplexers_(Part 2)-00243-ai-sw

A four cabinet, 24 TCU conguration with 3-input CBF, combining, diversity, and medium power
duplexers, is shown in Figure 13-34 and Figure 13-35. Table 13-25 provides a summary of the
13-42
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
(Part 1)
Tx/Rx
ANTENNA
(S ECTOR 3)
Tx
ANTENNA
(SECTO R 3)
DUP LEXER
IADU
TO
EXTENDER 1
M-Cell6
BTS CABINET
RF INP UT
DUP LE XE R
DUP LE XE R
RF LOAD
Rx EXT
BLOC K
Rx EXT
BLOCK
DLNB
IADU
IADU
RF INP UT
RF INP UT
RF LOAD
RF LOAD
HCOMB
3-INP UT
CBF
HCOMB
3-INPU T
CBF
HCOMB
3-INPU T
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
T
C
U
A
B
A
B
T
C
U
A
B
A
B
T
C
U
A
B
A
B
EXTENDER 3 M -Cell6 BTS CABINET

68P02900W21-R
T
C
U
A
B
A
B
T
C
U
A
B
A
B
T
C
U
A
B
EXTENDER 2 M-Cell6 BTS CABINET

,_combining,_medium_power_duplexers_(Part 1)-00244-ai-sw
13-43
GMR-01
Nov 2007
M-Cell6 cabinets
(Part 2)
DUP LEXER
Rx REV B LOCK 1
TO E XTENDER 2
M-Cell6 BTS C ABINET
Tx/Rx
ANTENNA
(SE CTOR 2)
Tx/Rx
ANTENNA
(SE CTOR 2)
Tx/Rx
ANTENNA
(S ECTOR 1)
Tx/Rx
ANTENNA
(S ECTOR 1)
RF INP UT
DUP LE XE R
Rx EXT
BLOCK
DLNB
DUP LE XE R
DUP LE XE R
DUP LE XE R
RF LOAD
DLNB
IADU
IADU
RF INPU T
6
RF INPUT
RF LOAD
RF LOAD
HCOMB
3-INPUT
CBF
HCOMB
3-INPUT
CBF
HCOMB
3-INPU T
CBF
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
T
C
U
A
B
A
B
A
B
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
A
B
EXTENDER 1 M-Cel l6 BTS CABINET
A
B
T
C
U
A
B
A
B
T
C
U
A
B
,_combining,_medium_power_duplexers_(Part 2)-00245-ai-sw
CBF, combining, diversity and medium power duplexers (2 antennas/sector)
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
24
TCU
Transmitter
3-input CBF

Continued
13-44
68P02900W21-R
GMR-01
Nov 2007
M-Cell6 cabinets
CBF, combining, diversity and medium power duplexers (2 antennas/sector) (Continued)
Equipment
Quantity
Receiver
3
DLNB
Rx extender block
[DCS1800] 3 sector (2/2/2), with hybrid combining and diversity

A single cabinet, six TCU conguration with hybrid combining and diversity, is shown in
Figure 13-36 3 sector (2/2/2), hybrid combining

Tx
ANTENNA
(SEC TOR 1)
Tx
ANTENNA
(SEC TOR 3)
Tx
ANTENNA
(SEC TOR 2)
Rx
ANTENNAS
(SEC TOR 1)
LNA
TxBPF
TxBPF
TxBP F
HYBRID
HYBRID
HYBRID
T
C
U
T
C
U
A
B
A
B
T
C
U
A
B
T
C
U
A
B
T
C
U
A
B
Rx
ANTENNAS
(SEC TOR 2)
LNA
Rx
ANTENNAS
(SEC TOR 3)
LNA
T
C
U
A
B
ti-GSM-3_sector_(2/2/2),_hybrid_combining-00246-ai-sw
68P02900W21-R
13-45
GMR-01
Nov 2007
M-Cell6 cabinets
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
TxBPF
Hybrid combiner
Receiver
LNA
[DCS1800] 3 sector (2/2/2), with hybrid combining, diversity, and

medium power duplexers
cabinet, six TCU conguration with hybrid combining, diversity, and medium power duplexers,
is shown in Figure 13-37.
Quantity
Equipment
Antennas
M-Cell6 BTS cabinet
TCU
Transmitter
Hybrid combiner
Receiver
LNA
3
13-46
68P02900W21-R
GMR-01
Nov 2007
M-Cell2 cabinets
Figure 13-37 3 sector (2/2/2), hybrid combining, medium power duplexers
DUP LE XE R
Rx
ANTENNAS
(S ECTOR 1)
LNA
HYBRID
HYBRID
T
C
U
T
C
U
A
B
Tx/Rx
ANTENNA
(SE CTOR 3)
A
B
T
C
U
A
B
HYBRID
T
C
U
A
B
Rx
ANTENNAS
(S ECTOR 2)
Rx
ANTENNAS
(S ECTOR 3)
DUP LE XE R
Tx/Rx
ANTENNA
(SE CTOR 2)
DUP LE XE R
Tx/Rx
ANTENNA
(SE CTOR 1)
T
C
U
A
B
LNA
LNA
T
C
U
A
B
ti-GSM-3_sector_(2/2/2),_hybrid_combining,_medium_power_duplexers-00247-ai-sw
M-Cell2 cabinets
Diversity is assumed in all gures, unless stated otherwise.
68P02900W21-R
13-47
GMR-01
Nov 2007
M-Cell2 cabinets
[GSM900] 2 carrier, single sector, with hybrid combining and diversity

A single cabinet, two TCU conguration with hybrid combining and diversity, is shown in
Figure 13-38
2 carrier, single sector, hybrid combining
Tx
ANTENNA
Rx
ANTENNAS
DLNB
CBF
T
C
U
T
C
U
A
B
A
B

ti-GSM-2_carrier ,_single_sector ,_hybr id_combining-00248-ai-sw
Quantity
Equipment
Antennas
M-Cell2 BTS cabinet
TCU
Transmitter
CBF
Receiver
DNLB
13-48
68P02900W21-R
GMR-01
Nov 2007
M-Cell2 cabinets
[GSM900] 2 carrier, single sector, with hybrid combining, diversity, and

medium power duplexer
A single cabinet, two TCU conguration with hybrid combining, diversity, and medium power
Figure 13-39 2 carrier, single sector, hybrid combining, medium power duplexer
Rx
ANTENNA
Tx/Rx
ANTENNA
DUPLEXER
DLNB
CBF
T
C
U
T
C
U
A
B
A
B

ti-GSM-2_carrier ,_single_sector ,_hybr id_combining,_medium_power_duplexer-00249-ai-sw
Quantity
Equipment
Antennas
M-Cell2 BTS cabinet
TCU
Transmitter
CBF
Continued
68P02900W21-R
13-49
GMR-01
Nov 2007
M-Cell2 cabinets
combining, diversity and medium power duplexer (Continued)
Equipment
Quantity
Receiver
DNLB
1
[GSM900] 2 sectors (1 carrier per sector), with diversity

A single cabinet, two TCU conguration with diversity, is shown in Figure 13-40. Table 13-30
provides a summary of the equipment required for this conguration.
Figure 13-40
Tx
ANTENNA
Tx
ANTENNA
2 sectors (1 carrier per sector)

Rx
ANTENNAS
DLNB
CBF
CBF
T
C
U
T
C
U
A
B
Rx
ANTENNAS
DLNB
A
B

ti-GSM-2_sectors_(1_carrier_per_sector)-00250-ai-sw
13-50
68P02900W21-R
GMR-01
Nov 2007
M-Cell2 cabinets
Table 13-30 Equipment required for single cabinet, 2 TCU conguration with diversity
Quantity
Equipment
Antennas
M-Cell2 BTS cabinet
TCU
Transmitter
CBF
Receiver
DNLB
[DCS1800] 2 carrier, single sector, with air combining and diversity

A single cabinet, two TCU conguration with air combining and diversity, is shown in
Figure 13-41.
Figure 13-41
Tx
ANTENNA
2 carrier, single sector, air combining

Rx
ANTENNA
Tx/Rx
ANTENNA
DUP LEXER
LNA
TxBP F
T
C
U
T
C
U
A
B
A
B

ti-GSM-2_carrier ,_single_sector ,_air _combining-00251-ai-sw
68P02900W21-R
13-51
GMR-01
Nov 2007
M-Cell2 cabinets
Table 13-31 Equipment required for single cabinet, 2 TCU conguration with air
Quantity
Equipment
Antennas
M-Cell2 BTS cabinet
TCU
Transmitter
TxBPF
Receiver
LNA
1
[DCS1800] 2 sectors, with diversity

cabinet, two TCU conguration with diversity, is shown in Figure 13-42.
Table 13-32 Equipment required for single cabinet, 2 TCU conguration with diversity
Quantity
Equipment
Antennas
M-Cell2 BTS cabinet
TCU
Transmitter
TxBPF
Receiver
LNA
13-52
68P02900W21-R
GMR-01
Nov 2007
M-Cell2 cabinets
Figure 13-42 2 sectors

Tx
ANTENNA
Tx
ANTENNA
Rx
ANTENNAS
LNA
TxBPF
TxBPF
T
C
U
T
C
U
A
B
Rx
ANTENNAS
LNA
A
B

ti-GSM-2_sectors-00252-ai-sw
68P02900W21-R
Nov 2007
13-53
GMR-01
M-Cell2 cabinets
13-54
68P02900W21-R
GMR-01
Nov 2007
Index
Index
A
Acronyms . . . . . . . . . . .
Adaptive multi-rate (AMR) . .
Applications. . . . . . . . .
Capacity and coverage . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-21
3-10
3-12
3-10
3-13
Adaptive multi-rate (AMR) (contd.)

Interoperability with GSM half
Introduction. . . . . . . . . .
Migration to AMR half rate . .
Quality of service . . . . . . .
rate .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
3-13
3-10
3-13
3-11
B
BSS equipment overview . . . . . . . . . . 1-4
System architecture. . . . . . . . . . . . 1-4
System components . . . . . . . . . . . . 1-5
BSS features . . . . . . . . . . . . . . . . 1-8
Adaptive Multi-Rate (AMR) . . . . . . .
1-11
Advanced Speech Call Item (ASCI) . . .
1-14
BSC Reset Management (BRM) . . . . .
1-14
Code Storage Facility Processor
(CSFP) . . . . . . . . . . . . . . . . .
1-10
Diversity . . . . . . . . . . . . . . . . . 1-8
Enhanced-GPRS (EGPRS) . . . . . . . .
1-10
Frequency hopping . . . . . . . . . . . . 1-9
GSM half rate . . . . . . . . . . . . . .
1-12
Improved Timeslot Sharing (ITS) . . . .
1-17
LoCation Services (LCS) . . . . . . . .
1-13
PCU for GPRS upgrade . . . . . . . . .
1-10
Planning impacts . . . . . . . . . . . . . 1-8
Quality of Service (QoS). . . . . . . . .
1-15
Short Message Service, Cell Broadcast (SMS
CB) . . . . . . . . . . . . . . . . . . . . 1-9
VersaTRAU backhaul for EGPRS . . . .
1-15
BSS interfaces . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
BSS planning for GPRS/EGPRS . . . . . .
Feature compatibility . . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
PCU to SGSN interface planning . . . .
BSS planning overview . . . . . . . . . .
Background information . . . . . . . .
Introduction. . . . . . . . . . . . . . .
Planning methodology . . . . . . . . .
BSS-PCU hardware planning example for
EGPRS . . . . . . . . . . . . . . . . . .
BSS - PCU planning example for E
GPRS . . . . . . . . . . . . . . . . . .
QoS enabled, QoS2 not enabled. . . . .
Introduction. . . . . . . . . . . . . . .
BSS-PCU hardware planning example for
GPRS . . . . . . . . . . . . . . . . . . .
BSS - PCU planning example for GPRS. .
Introduction. . . . . . . . . . . . . . .
.
.
.
.
.
.
2-2
2-2
8-2
8-4
8-2
8-2
1-18
1-18
1-18
1-20
8-60
8-60
with
8-68
8-60
8-52
8-52
8-52
C
Calculations using alternative call mod
els. . . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . .
Planning example 1 . . . . . . . . . .
Planning example 4 (using AMR) . . .
Call model parameters for capacity
calculations . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . .
.
.
.
.
.
.
9-17
9-17
9-17
9-29
9-41
9-55
. 3-116
. 3-116

(contd.)
Typical call parameters . . . . . . . . .
Connecting Horizon II macro cabinets to
Horizonmacro cabinets . . . . . . . . . .
Compatibility issues. . . . . . . . . . .
Connection overview . . . . . . . . . .
Examples of mixed cabinet congura
tions . . . . . . . . . . . . . . . . . .
68P02900W21-R
Nov 2007
3-116
12-68
12-68
12-68
12-68
IX-1
GMR-01
Index
Connecting Horizon II macro cabinets to

cabinets . . . . . . . . . . . . . . . . .
Compatibility issues. . . . . . . . . .
Connection overview . . . . . . . . .
Control channel calculations . . . . . .
Control channel congurations . . . .
Introduction. . . . . . . . . . . . . .
M-Cell6
. 12-76
. 12-76
. 12-76
. 3-119
. 3-136
. 3-119
Control channel calculations (contd.)

Number of CCCHs and PCCCHs per
cell . . . . . . . . . . . . . . . . .
Number of SDCCHs per BTS cell . .
Planning considerations. . . . . . .
User data capacity on the PCCCH
timeslot . . . . . . . . . . . . . . .
BTS
. . 3-122
. . 3-133
. . 3-120
. . 3-132
D
Deriving call model parameters from network
statistics . . . . . . . . . . . . . . . . .
11-2
Call duration (T) . . . . . . . . . . . .
11-4
Location update factor (L) . . . . . . .
11-8
Pages per call (PPC) . . . . . . . . . .
11-9
Paging rate (PGSM) . . . . . . . . . . .
11-8
Ratio of handovers per call (H) . . . . .
11-6
Ratio of IMSI detaches per call (I) . . .
11-7
Ratio of intra BSS handovers to all handovers
(i) . . . . . . . . . . . . . . . . . . . .
11-6
Ratio of location updates per call (I) . .
11-7
Ratio of SMSs per call (S) . . . . . . . .
11-5
Sample statistic calculations . . . . . . 11-10
Standard call model parameters . . . .
11-2
Determine the hardware requirements for BTS
B . . . . . . . . . . . . . . . . . . . . . . 9-5
Cabinet . . . . . . . . . . . . . . . . . . 9-5
Summary . . . . . . . . . . . . . . . . . 9-6
Determine the hardware requirements for BTS
K . . . . . . . . . . . . . . . . . . . . . . 9-8
Cabinet . . . . . . . . . . . . . . . . . . 9-8
Introduction. . . . . . . . . . . . . . . . 9-8
Receiver requirements . . . . . . . . . . 9-8
Summary . . . . . . . . . . . . . . . . . 9-9

(contd.)
Determine the hardware requirements
BSC . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . .
Summary . . . . . . . . . . . . . .
Determine the hardware requirements
RXCDR . . . . . . . . . . . . . . . .
CLKX requirement . . . . . . . . .
GCLK requirement . . . . . . . . .
GPROC requirement . . . . . . . .
KSW/DSW2 requirement . . . . . .
KSWX/DSWX requirement . . . . .
LANX requirement . . . . . . . . .
Link interface . . . . . . . . . . . .
MSI requirements. . . . . . . . . .
PIX requirement . . . . . . . . . .
Power supply . . . . . . . . . . . .
Summary . . . . . . . . . . . . . .
Transcoder requirement . . . . . .
DPROC board . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . .
. . . 9-9
for the
. .
9-11
. .
9-11
. .
9-13
for the
. .
9-14
. .
9-15
. .
9-15
. .
9-15
. .
9-15
. .
9-15
. .
9-16
. .
9-15
. .
9-14
. .
9-16
. .
9-16
. .
9-16
. .
9-14
. .
8-20
. .
8-20
. .
8-20
E
E1 link provisioning for GPRS
EGPRS . . . . . . . . . . . .
E1 interface provisioning . .
E1 Planning considerations .
and
. . . . . .
. . . . . .
. . . . . .
Exercises . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . . .
8-37
8-37
8-37
9-4
9-4
F
Four cabinet BTS conguration . . .
Four cabinet M-Cell6 BTS . . . . .
Four cabinet BTS congurations . .
Four cabinet Horizon II macro BTS
Four cabinet Horizon II mini BTS .
Four cabinet Horizonmacro BTS .
Frequency planning . . . . . . . . .
Introduction. . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-8
13-8
12-18
12-18
12-19
12-20
3-107
3-107
Frequency planning (contd.)

Rules for BaseBand Hopping (BBH) . . . 3-111
Rules for Synthesizer Frequency Hopping
(SFH) . . . . . . . . . . . . . . . . . . 3-107
Frequency re-use . . . . . . . . . . . . .
3-43
Carrier/Interference (C/I) ratio . . . . .
3-46
Introduction. . . . . . . . . . . . . . .
3-43
Re-use pattern . . . . . . . . . . . . .
3-44
IX-2
68P02900W21-R
GMR-01
Nov 2007
Index
Frequency re-use (contd.)
Frequency re-use (contd.)
Sectorization of sites . . . . . . . . . .
3-48
Sources of interference . . . . . . . . .
3-47
G
GPRS/EGPRS air interface planning
process . . . . . . . . . . . . . . . . . . 3-163
Congurable initial coding scheme . . . 3-182
Estimating the air interface trafc
throughput . . . . . . . . . . . . . . . 3-170
Estimating timeslot provisioning require
ments . . . . . . . . . . . . . . . . . . 3-172
File transit times calculations . . . . . . 3-180
GPRS/EGPRS data rates . . . . . . . . 3-182
Inuential factors in GPRS/EGPRS cell planning
and deployment . . . . . . . . . . . . . 3-163
Optimum le size calculation . . . . . . 3-179
Select a cell plan . . . . . . . . . . . . 3-170
concepts . . . . . . . . . . . . . . . . . 3-141
BSS timeslot allocation methods . . . . 3-155
Carrier timeslot allocation examples . . 3-147
Dynamic timeslot allocation . . . . . . . 3-143
Introduction. . . . . . . . . . . . . . . 3-141
Provisioning the network with switchable
timeslots . . . . . . . . . . . . . . . . 3-157
Recommendation for switchable timeslot
usage . . . . . . . . . . . . . . . . . . 3-161

concepts (contd.)
Timeslot allocation process on carriers with
GPRS trafc. . . . . . . . . . . . . . . 3-162
GPRS/EGPRS trafc planning . . . . . . . 3-140
Determination of expected load . . . . . 3-140
Network planning ow . . . . . . . . . 3-140
GSM frequency spectrum . . . . . . . . . . 3-4
Absolute radio frequency channel
capacity . . . . . . . . . . . . . . . . . . 3-5
DCS1800 frequency spectrum . . . . . . 3-4
GSM900 frequency spectrum . . . . . . . 3-4
Modulation techniques and channel
spacing . . . . . . . . . . . . . . . . . . 3-6
GSM half rate . . . . . . . . . . . . . . .
3-14
Applications. . . . . . . . . . . . . . .
3-15
Capacity and coverage . . . . . . . . .
3-14
Interoperability with AMR half rate . . .
3-16
Interoperability with EGPRS . . . . . .
3-16
Introduction. . . . . . . . . . . . . . .
3-14
Migration to half rate . . . . . . . . . .
3-16
Quality of service . . . . . . . . . . . .
3-15
H
Half rate utilization . . . . . . . . . .
Description . . . . . . . . . . . . .
Operational aspects . . . . . . . . .
Parameter descriptions . . . . . . .
Handover and power control . . . . .
Handover and power control thresh
olds . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . .
Backhaul . . . . . . . . . . . . . .
Equipment descriptions . . . . . . .
.
.
.
.
.
.
.
.
.
.
4-22
4-22
4-26
4-22
4-19
.
.
.
.
.
.
.
.
.
.
4-19
4-19
4-29
4-31
4-29
Horizon macrocell RF congurations . . .

Horizon II macro cabinets. . . . . . . .
Horizon II macro cabinets with PGSM
Duplexer . . . . . . . . . . . . . . . .
Horizon II micro cabinets . . . . . . . .
Horizon II mini cabinets . . . . . . . .
Horizoncompact2 . . . . . . . . . . . .
Horizonmacro cabinets . . . . . . . . .
Overview of conguration diagrams . .
12-22
12-22
12-32
12-47
12-39
12-60
12-50
12-22
I
Inter-radio access technology (2G-3G)
reselection and handovers . . . . . .
2G-3G handover description . . . .
Impact of 2G-3G handovers on GSM
architecture . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . .
System consideration . . . . . . . .
cell
. . 3-113
. . 3-113
system
. . 3-114
. . 3-113
. . 3-115

Interconnection rules . . . . . .
Introduction. . . . . . . . . . .
Introduction. . . . . . . . . . . .
AMR basic operation . . . . . .
GSM half rate basic operation .
68P02900W21-R
Nov 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-4
2-4
2-4
4-2
4-2
4-2
IX-3
GMR-01
Index
Introduction (contd.)
Introduction (contd.)
Inuencing factors . . . . . . . . . . . .
New hardware . . . . . . . . . . . . . .
4-3
4-3
Planning . . . . . . . . . . . . . . . . .
4-4
L
Location area planning calculations. . . .
Example procedure . . . . . . . . . . .
10-3
10-3
Location area planning considerations . .
10-2
M
M-Cell RF congurations . . .
Overview . . . . . . . . . .
General HDSL guidelines . .
Integrated HDSL interface .
Introduction. . . . . . . . .
Microcell system planning .
Manual overview . . . . . . .
Contents . . . . . . . . . .
Introduction. . . . . . . . .
Microcell RF congurations. .
Horizonmicro2 . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-9
13-47
13-9
13-9
2-25
2-27
2-25
2-25
2-28
. 1-2
. 1-2
. 1-2
12-65
12-65
Microcellular solution . . . . . . . .
Combined cell architecture . . . .
Combined cell architecture struc
ture . . . . . . . . . . . . . . . .
Expansion solution . . . . . . . .
Layered architecture . . . . . . .
Miscellaneous information . . . . .
Circuit pooling . . . . . . . . . .
Emergency call handling . . . . .
MPROC board. . . . . . . . . . . .
Introduction. . . . . . . . . . . .
PSP planning considerations . . .
. . . 3-103
. . . 3-104
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3-104
. 3-106
. 3-103
.
4-21
.
4-21
.
4-21
.
8-19
.
8-19
.
8-19
N
Network topology . . . .
16 kbit/s XBL . . . . .
Aggregate Abis . . . .
Daisy chain planning .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . 2-6
.
2-21
.
2-12
. . 2-8
. . 2-9
Network topology (contd.)

Dynamic allocation of RXCDR to
(DARBC) . . . . . . . . . . . .
Introduction. . . . . . . . . . .
RTF path fault containment . . .
Star connection . . . . . . . . .
BSC circuits
. . . .
2-22
. . . . . 2-6
. . . .
2-16
. . . . . 2-7
O
Overcoming adverse propagation e
ffects . . . . . . . . . . . . . . . . . . .
3-49
64 kbit/s TRAU for EGPRS . . . . . . .
3-92
Discontinuous transmission (DTX) . . .
3-94
EGPRS channel coding schemes . . . .
3-82
Error protection and detection . . . . .
3-50
GPRS channel coding schemes . . . . .
3-75
GSM circuit-switched data channel
encoding . . . . . . . . . . . . . . . .
3-66
GSM control channel encoding . . . . .
3-65
GSM speech channel encoding for AMR full
rate . . . . . . . . . . . . . . . . . . .
3-60
Overcoming adverse propagation effects (contd.)

GSM speech channel encoding for AMR half
rate . . . . . . . . . . . . . . . . . . .
3-62
GSM speech channel encoding for enhanced
full rate . . . . . . . . . . . . . . . . .
3-58
GSM speech channel encoding for full
rate . . . . . . . . . . . . . . . . . . .
3-56
GSM speech channel encoding for half
rate . . . . . . . . . . . . . . . . . . .
3-59
Hardware techniques . . . . . . . . . .
3-49
Link adaptation (LA) in GPRS/EGPRS . .
3-93
Link adaptation for AMR channels . . .
3-64
IX-4
68P02900W21-R
GMR-01
Nov 2007
Index
Mapping logical channels in the TDMA frame

structure . . . . . . . . . . . . . . . .
3-68
Receive diversity . . . . . . . . . . . .
Voice activity detection (VAD) . . . . . .
3-96
3-93
Planning example of BSS support for LCS

provisioning . . . . . . . . . . . . . . . .
LCS planning example calculations . . .
Typical parameter values . . . . . . . .
Planning tools . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
PMC module . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
Planning considerations. . . . . . . . .
Pre-requisites . . . . . . . . . . . . . . .
Network topology . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . .
Propagation effects on GSM frequencies. .
Attenuation . . . . . . . . . . . . . . .
Decibels. . . . . . . . . . . . . . . . .
Environmental effects on propagation. .
Fresnel zone . . . . . . . . . . . . . .
GSM900 path loss. . . . . . . . . . . .
Multipath propagation . . . . . . . . .
Path loss GSM900 against DCS1800 . .
Propagation production . . . . . . . . .
Radio refractive index (RRI) . . . . . .
9-73
9-73
9-73
3-3
3-3
8-24
8-24
8-24
9-2
9-3
9-2
3-17
3-24
3-17
3-23
3-19
3-40
3-27
3-42
3-17
3-20
P
(Packet) Rear Transition Module
Introduction. . . . . . . . . . . . . . .
8-25
8-25
PCU
multiple PCUs. . . . . . . . . . . . . .
8-34
PCU equipment redundancy and provisioning
goals . . . . . . . . . . . . . . . . . . .
8-26
PCU equipment redundancy planning. .
8-26
Support for equipment redundancy . . .
8-26
Upgrading the PCU . . . . . . . . . . .
8-32
PCU hardware layout . . . . . . . . . . .
8-16
PCU shelf (cPCI) . . . . . . . . . . . . .
8-18
Introduction. . . . . . . . . . . . . . .
8-18
8-18
PCU-SGSN: trafc and signal planning . .
8-46
Determining net Gb load . . . . . . . .
8-48
Frame relay parameter values . . . . .
8-50
Gb entities . . . . . . . . . . . . . . .
8-46
Gb link timeslots . . . . . . . . . . . .
8-49
Gb signaling . . . . . . . . . . . . . .
8-47
General planning guidelines . . . . . .
8-47
Introduction. . . . . . . . . . . . . . .
8-46
Specic planning guidelines . . . . . .
8-47
.
.
.
.
.
Q
QoS capacity . . . . . . . . . . . . . . .
8-39
MTBR allocation . . . . . . . . . . . .
8-41
PRP-PDTCH QoS planning . . . . . . .
8-44
Quality and capacity . . . . . . . . . . . . 4-5
AMR Full Rate and AMR Half Rate speech
quality . . . . . . . . . . . . . . . . . . 4-5
AMR voice quality improvement and
coverage . . . . . . . . . . . . . . . .
4-10
Quality and capacity (contd.)

Benets of AMR. . . . . . . .
Benets of GSM half rate . . .
Capacity increase due to half
usage . . . . . . . . . . . . .
GSM Half Rate speech quality
Timeslot usage . . . . . . . .
. . .
. . .
rate
. . .
. . .
. . .
. . . 4-5
. .
4-11
. .
. .
. .
4-11
4-11
4-15
Introduction. . . . . . . . . . . . . . .
Thresholds and hystereses . . . . . . .
4-16
4-17
R
Rate adaptation . . . . . . . . . . . . . .
Codec modes . . . . . . . . . . . . . .
Downlink adaptation MS monitor . . . .
4-16
4-16
4-18
Rate adaptation (contd.)
S
Single cabinet BTS congurations . . 12-6, 13-3
68P02900W21-R
Nov 2007
IX-5
GMR-01
Index
Standard M-Cell congurations .

Subscriber environment. . . . .
Distribution . . . . . . . . . .
Environment . . . . . . . . .
Future planning . . . . . . . .
Hand portable subscribers . .
Subscriber hardware . . . . .
Summary . . . . . . . . . . . .
Single cabinet BTS congurations (contd.)

Single cabinet Horizon II macro BTS
Single cabinet Horizon II mini BTS .
Single cabinet Horizon macro BTS .
Single cabinet M-Cell2 BTS . . . . .
Single cabinet M-Cell6 BTS . . . . .
Standard congurations . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-6
12-8
12-7
12-9
13-4
13-3
12-2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-2
.
3-99
. 3-100
.
3-99
. 3-102
. 3-101
.
3-99
.
4-36
T
Three cabinet BTS conguration . . .
Three cabinet M-Cell2 BTS . . . . .
Three cabinet BTS congurations . . .
Three cabinet Horizon II macro BTS
Three cabinet Horizon II micro BTS.
Three cabinet Horizon II mini BTS .
Three cabinet Horizonmacro BTS . .
Trafc capacity . . . . . . . . . . . .
Channel blocking . . . . . . . . . .
Dimensioning . . . . . . . . . . . .
Grade of service. . . . . . . . . . .
Trafc ow . . . . . . . . . . . . .
Transition Module. . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-7
13-7
12-13
12-13
12-15
12-14
12-16
. 3-8
. 3-8
. 3-8
. 3-9
. 3-9
8-25
Two cabinet BTS conguration . . . . .

Two cabinet M-Cell6 BTS . . . . . . .
Two cabinet M-Cell6 BTS with CTU2
Adapter . . . . . . . . . . . . . . . .
Two cabinet BTS congurations. . . . .
Two cabinet Horizon II macro BTS . .
Two cabinet Horizon II mini BTS . . .
Two cabinet Horizonmacro BTS . . . .
Typical BSS congurations . . . . . . .
BSC with 24 BTSs. . . . . . . . . . .
BSC with full redundancy . . . . . . .
Transcoder . . . . . . . . . . . . . .
IX-6
.
.
13-5
13-5
.
.
.
.
.
.
.
.
.
13-6
12-10
12-10
12-11
12-12
12-3
12-3
12-4
12-5
68P02900W21-R
GMR-01
Nov 2007
Standard Printing Instructions

Part Number
68P02900W21-R
Manual Title
Date
Nov 2007
A4 Ring Bound - GSD (UK)

Binder
Printing
Finishing
4 D-ring binder - A4 size (210mm x 297mm) white PVC.
40mm or 65mm capacity depending on the size of the manual.
Clear pockets on front and spine.
Cover / spine text printed in colour.
Body- printed double sided onto white A4 (210mm x 297mm) 80g

4 hole paper.
A4 size (210mm x 297mm) clear PVC sheet front page for

protection.
Bag wrapped with clear polythene.
If this is to be used by manufacturing as an Inbox document, then refer to appropriate

Materials or Methods Specification.

68P02900W21

Uploaded by

Document Information

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

68P02900W21

Uploaded by

Copyright:

Available Formats

SYSTEM INFORMATION

BSS EQUIPMENT PLANNING

System Information: BSS Equipment

All Rights Reserved

System Information: BSS Equipment Planning

Chapter 1: Introduction to planning

Code Storage Facility Processor (CSFP)

Chapter 2: Transmission systems

Chapter 3: BSS cell planning

System Information: BSS Equipment Planning

Combined cell architecture structure . . . . . . . . . . . . . . .

Chapter 4: AMR and {22064} GSM planning

System Information: BSS Equipment Planning

BTS planning overview. . . . . . . . . . . . . . . . . . .

Capacity increase due to half rate usage .

Chapter 5: BTS planning steps and rules

Micro base control unit (microBCU) . . . . . . . . . . . . . . . . . . . . .

Chapter 6: BSC planning steps and rules

System Information: BSS Equipment Planning

Kiloport switch (KSW) and double kiloport switch (DSW2) . . . . . . . . . . .

Chapter 7: RXCDR planning steps and rules

System Information: BSS Equipment Planning

Chapter 8: PCU upgrade for BSS

System Information: BSS Equipment Planning

Chapter 9: Planning exercises

Location area planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10: Location area planning

Chapter 11: Call model parameters

Location update factor (L) . .

Chapter 12: Standard BSS and Horizon BTS congurations

Chapter 13: M-Cell BTS congurations

Three cabinet M-Cell2 BTS

1-1: BSS block diagram . . . . . . . . . . . . . . . . . . . . . . . . .

BTS antenna height of 50 m, MS height of 1.5 m (GSM900) . . . . . .

System Information: BSS Equipment Planning

Figure 3-84: Multiplexing 4 TBFs on an air timeslot . . . . . . . . . . . . . . . . . . .

Figure 12-22: [DCS1800] 3 sector 2/2/2 or 4/4/4 with HCUs . . . . . . . . . . . . . . . . .

Figure 13-16: 3 sector (2/2/2), combining . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 1-1: Transceiver unit usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-42: GPRS downlink data rates (kbit/s) with TCP (CS4). . . . . . . . . . . . . . . .

System Information: BSS Equipment Planning

Table 8-1: VersaTRAU backhaul recommendations for a given number of PDTCHs . . . . .

Table 12-20: Equipment required for HP 3 sector 1/1/1/SP 3 sector 2/2/2 . . . . . . . . . . . .

System Information: BSS Equipment

What is covered in this manual?

Issue P - includes GSM Software Release 7 and EGPRS

Issue Q - includes GSM Half Rate

Issue R - includes GSM Software Release 8

Resolution of Service Requests

Added recommendation for evenly distributing GSLs

Expand on the existing planning guidelines and rules,

In Table 6-1, correct text should read that GSR7

Corrected the content under section Link control

Formula for evaluation of necessary quantity of GDS

Incorporation of Change Notices

Incorporation of Change Notices

Incorrect DRI Planning Limit in GSR7 68PO2900W21-Q, GSM

Add guidelines to dimension PRP and PDTCH planning with

Incorrect MTL Link Utilization.

Incorrect value of Average XBL message length.

Updated the Multiple serial interface planning considerations

Formula for evaluation of necessary quantity of GDS TRAU E1

Special key sequences

Press the Ctrl and C keys at the same time.