RSR10 BTS Equipment Planning Guide 68P02909W13-A

Equipment Planning Guide
RSR10
68P02909W13-A
2008 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 modified 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.
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 Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms 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 Office.
PRELIMINARY - UNDER DEVELOPMENT
Dec 2008
Table
of
Contents
Contents
RSR10 BTS Equipment Planning Guide

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
10
11
11
11
11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-3
1-3
1-3
1-3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS planning overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
2-3
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 definitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: BSS equipment overview

System architecture . . .
System components .
Abis BTS overview . . . .
Supported BTS types.
BSS topologies . . . .
Abis BTS architecture
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
overview
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 2: BTS planning steps and rules
68P02909W13-A
Dec 2008
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-3
2-3
2-5
2-5
2-6
2-8
2-8
2-9
2-11
2-11
2-11
2-14
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-3
3-3
3-3
3-3
3-4
3-4
3-6
3-6
3-7
3-9
3-9
3-10
3-10
3-11
3-11
3-12
3-12
3-16
3-16
RSL/OML dimensioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E1 interconnect dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4-3
Introduction . . . . . . . . . . . . . . . .
Outline of planning steps . . . . . . . . .
Macrocell cabinets . . . . . . . . . . . . . . .
Horizon II macro . . . . . . . . . . . . . .
Horizonmacro . . . . . . . . . . . . . . .
Microcell enclosures . . . . . . . . . . . . . .
Horizon II mini . . . . . . . . . . . . . . .
Horizon II micro . . . . . . . . . . . . . .
EGPRS configuration. . . . . . . . . . . . . .
EGPRS configuration limitations . . . . . .
EDGE capacity reporting. . . . . . . . . .
Dynamic allocation of EDGE sub-timeslots .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 3: Timeslots on the Abis interface

Introduction . . . . . . . . . . . . . . . . . . . . . . . .
BTS topologies . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Star topology . . . . . . . . . . . . . . . . . . . . .
Chain topology . . . . . . . . . . . . . . . . . . . . .
Tree topology . . . . . . . . . . . . . . . . . . . . .
Ring topology . . . . . . . . . . . . . . . . . . . . .
Timeslots assignment on the Abis interface . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Principles of timeslot assignment on the Abis interface
Principles of Idle Timeslot Assignment. . . . . . . . .
Principles of Monitor Timeslot Assignment . . . . . .
BTS multiplexing mode . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Timeslot assignment in N:1 multiplexing mode . . . .
2:1 Multiplexing mode . . . . . . . . . . . . . . . . .
4:1 Multiplexing mode . . . . . . . . . . . . . . . . .
Timeslot assignment in tree topology . . . . . . . . .
Manual timeslot assignment on the Abis interface . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 4: RSL/OML/E1 dimensioning rules
Chapter 5: Glossary
Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
5-2
68P02909W13-A
Dec 2008
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1:
1-2:
3-1:
3-2:
3-3:
3-4:
3-5:
3-6:
BSS block diagram . . . . . . . . .

Logic Abis BTS architecture diagram
Star topology . . . . . . . . . . . .
Chain topology . . . . . . . . . . .
Tree topology . . . . . . . . . . . .
Ring topology . . . . . . . . . . . .
FlexAbis (PS) algorithm . . . . . . .
Multiple multiplexing modes. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W13-A
Dec 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-4
3-3
3-4
3-4
3-5
3-6
3-10
iii
List of Figures
iv
68P02909W13-A
Dec 2008
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1-1:
2-1:
2-2:
2-3:
2-4:
2-5:
2-6:
3-1:
3-2:
3-3:
3-4:
3-5:
3-6:
Supported BTS types . . . . . . . . . . . . . . . .

Horizon II macro cabinet configuration . . . . . . .
Horizonmacro cabinet configuration . . . . . . . .
Horizon II mini cabinet configuration . . . . . . . .
Horizon II micro cabinet configuration . . . . . . .
TRX hardware and software configuration mismatch
EDGE capability of BBH and/or BCCH configured .
Timeslot assignment in 2:1 multiplexing mode . . .
Timeslot assignment in 4:1 multiplexing mode . . .
Timeslot assignment on A0 . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W13-A
Dec 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-3
2-5
2-7
2-8
2-9
2-12
2-13
3-11
3-12
3-13
3-14
3-15
3-15
List of Tables
vi
68P02909W13-A
Dec 2008
About
This
Manual
What is covered in this manual?

This document covers the BTS architecture overview and BTS planning for the RSR10 Feature
FR33950, FR33657, FR33602, FR33601, FR33658, and FR33951. This specification document
provides clear and understandable BTS planning. BSC planning and PCU planning is out of
scope of this document.
68P02909W13-A
Dec 2008
Revision history
Revision history
Version information
The following shows the status of this document since it was first released.
Issue
Date of issue
Remarks
Dec 2008
Initial release
Resolution of Service Requests

The following Service Requests are resolved in this document:
Service Request
CMBP Number
NA
NA
Remarks
Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:
CN Date
CN Number
Title
NA
NA
NA
68P02909W13-A
Dec 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola 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 expressed, 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.
NOTE
If this document was obtained when attending a Motorola training course, it is not
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 Motorola automatically supplies corrections and posts 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.
68P02909W13-A
Dec 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
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.
68P02909W13-A
Dec 2008
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 Office.
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
68P02909W13-A
Dec 2008
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.
The implementation of these recommendations and final 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 Office.
68P02909W13-A
Dec 2008
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
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
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
Note text.
68P02909W13-A
Dec 2008
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.
NOTE
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 fields (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 fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02909W13-A
Dec 2008
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 Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments 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 landfill 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 landfill 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.
68P02909W13-A
Dec 2008
CMM labeling and disclosure table
CMM labeling and disclosure table
The Peoples Republic of China requires 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 identified in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
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
field-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.
10
68P02909W13-A
Dec 2008
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 from your Motorola
Local Office 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 definitions

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
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. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02909W13-A
Dec 2008
11
Data encryption
12
68P02909W13-A
Dec 2008
Chapter
1
BSS equipment overview
68P02909W13-A
Dec 2008
1-1
System architecture
System architecture
The architecture of the Motorola Base Station System (BSS) is versatile, and allows several
possible configurations for a given system. The BSS is a combination of digital and RF
equipment that communicates with the Mobile Switching Centre (MSC), Serving GPRS Support
Node (SGSN), the Operations & Maintenance Centre (OMC), and the Mobile Stations (MS), as
shown in Figure 1-1.
Figure 1-1 BSS block diagram
SGSN
MSC
Gb interface
OMC
A interface
BSS
BSC/PCU/XCDR
Abis interface
BTS
BTS
BTS
Air interface
MS
MS
MS
MS
MS
ti-GSM-Harware-BSS block-00001-ai-sw
System components
The BSS can be divided into a Base Station Controller (BSC), Packet Control Unit (PCU),
Transcoder (XCDR) and one or more Base Transceiver Stations (BTSs). These units can
be in-building or externally located Horizon II macro, Horizon II Mini, Horizon II Micro,
Horizonmacro BTS cabinets or enclosures.
1-2
68P02909W13-A
Dec 2008
Abis BTS overview
Abis BTS overview
The interface between the BSC and the BTS is a standard Abis interface.
Supported BTS types

The following BTS types are supported (see Table 1-1):
Table 1-1 Supported BTS types

Master cabinet
Radio in master cabinet
Expansion cabinet
Horizonmacro
CTU
Horizonmacro
Horizon II macro
CTU2
CTU2D
Horizonmacro
Horizon II macro
Horizon II mini
CTU2
CTU2D
None
Horizon II micro
CTU2
CTU2D
None
NOTE
The Horizonmacro outdoor and indoor cabinets are powered at 110 V ac and therefore
cannot support CTU2.
BSS topologies
BSS supports four types of topologies:
Star topology
Chain topology
Tree topology
Ring topology
Refer to Chapter 3 Timeslots on the Abis interface for details of BSS topologies.
Abis BTS architecture overview

Figure 1-2 shows the system architecture of the Abis BTS.
68P02909W13-A
1-3
Dec 2008
Abis BTS architecture overview
Figure 1-2 Logic Abis BTS architecture diagram

Abis Inter face
OML(O&M)
BSC/PCU
BTS
RS L
(S igna ling)
TRAU (Da ta )
ti-GSM-Hardware-Logic Abis_BTS Architecture-00002-ai-sw
The OML is the communication link between the BTS and the BSC according to 12.21
Manufacturer Defined O&M. The OML is used to carry network management-related messages.
Alarm report and Statistics report are also transferred on the OML. There is one OML between
the BSS and BTS per site.
The RSL is the communication link between the BTS and the BSC according to TS 48.058. The
RSL is used to carry traffic management-related messages. One RSL is needed per carrier.
1-4
68P02909W13-A
Dec 2008
Chapter
2
BTS planning steps and rules
68P02909W13-A
Dec 2008
2-1
Introduction
Introduction
The planning steps and rules for the BTS, including Horizonmacro, Horizon II macro, Horizon II
mini and Horizon II micro site types are provided here. The sections described are as follows:
BTS planning overview on page 2-3.
Macrocell cabinets on page 2-5.
Microcell enclosures on page 2-8.
EGPRS configuration on page 2-11.
2-2
68P02909W13-A
Dec 2008
BTS planning overview
BTS planning overview
Introduction
To plan the equipage of a BTS site, the following information is required:
The number of cells controlled by the site.
The number of carriers required.
The output power per TRX.

The required output power must be known to ensure that the selected combining method
and antenna configuration provides sufficient output power. Alternatives include changing
combiner types or using more than one transmitting antenna. Duplexers may be used to
reduce the amount of cabling and the number of antennas.
The antenna configuration for each cell.
The cabinet or enclosure types to be used.
Whether there are equipment shelters at the site.

Include the macro or microcell outdoor equipment in the BTS planning for locations where
there are no equipment shelters. Include Macro or microcell where rooftop mounting or
distributed RF coverage is required or where space and access are restricted.
Whether battery backup equipment is needed for the outdoor equipment.
Future growth potential.

It is useful to know about potential future growth of the site to make intelligent trade off
between fewer cabinets or enclosures initially and ease of expansion later.
Outline of planning steps

The information required for planning a macrocell or microcell BTS site is outlined in Macrocell
and microcell BTS sites on page 2-4.
68P02909W13-A
2-3
Dec 2008
Outline of planning steps
Macrocell and microcell BTS sites

The following information for planning a macrocell or microcell BTS site is outlined in the
list and is provided in this chapter:
Determine if the site is indoor or outdoor.
Determine the number of macrocell cabinets required, refer to Macrocell cabinets on

page 2-5.
Determine the number of microcell enclosures required, refer to Microcell enclosures on

page 2-8.
The receiver configuration (including planning for Dual Band).*
The transmit configuration.*
The EGPRS enabled CTU2 configuration, refer to EGPRS configuration on page 2-11.
The antenna configuration.*
The amount of carrier equipment required.*
The number of micro base control units required.*
The number of network interface units required.*
The number of E1 links required. For Horizonmacro, Horizon II macro, Horizon II mini,
Horizon II micro site type, calculate the number of E1 links required to be carried by NIU
functionality. Refer to E1 interconnect dimensioning on page 4-3.
The number of main control units required.*
The number of XMUX and FMUX boards required.*
The battery back-up provisioning.*
The external power supply requirements.*
* Refer to Chapter 5 BTS planning steps and rules, System Information: BSS Equipment
Planning manual.
2-4
68P02909W13-A
Dec 2008
Macrocell cabinets
Macrocell cabinets
Horizon II macro
The BSS supports the Horizon II macro site type. The major architecture and capacity
requirements are described as follows:
The Horizon II macro site supports a maximum of 24 carriers.
The Horizon II macro site supports up to 6 Cells and a maximum of 12 carriers per Cell.
The Horizon II macro site supports a maximum of 6 E1 Ports. NIU functionality is

integrated into the BTP. From a functional standpoint, the Integrated NIU functions are
same as the standalone.
The Horizon II macro site supports a single OML and multiple RSLs with 2:1 or 4:1
multiplexing mode. The Horizon II macro supports equipping each RSL to one carrier, that
is, a maximum of 24 RSLs allocated to 24 carriers
The Horizon II macro site supports the following physical TRX equipment types: CTU,
SCTU2, DCTU2, and CCTU2. SCTU2 TRX type is CTU2/CTU2D configured in single density
mode, DCTU2 TRX type is CTU2/CTU2D configured in double density mode and supported
ITS (Improve Timeslot Sharing) feature, CCTU2 TRX type is CTU2D configured in double
density mode and support the CTU2D Capacity feature. CCTU2 is only allowed to be
configured in Horizon II macro/Horizon II mini/Horizon II micro cabinets.
The Horizon II macro site has a fixed Master Cabinet (Cabinet 0) of Horizon II macro
Cabinet Type, and supports the addition of extension cabinets (Cabinet 1,2, and so on)
with Horizonmacro, Horizon II macro, Horizon II mini and Horizon II micro. The Horizon II
macro supports the addition of up to 3 Extension cabinets. This means a Horizon II macro
site is restricted to a maximum of 4 cabinets.
NOTE
In FR33950/33951 feature scope, Horizon II mini and Horizon II micro
configured as expansion cabinets are not recommended as an official
configuration, only the cabinet combination in Table 2-1 is supported for Horizon
II macro site type.
Table 2-1 Horizon II macro cabinet configuration
Master cabinet
Expansion cabinet
Horizon II macro
CTU2
CTU2D
Horizonmacro
Horizon II macro
A minimum of one BTP (with integrated NIU functionality) is required in the master cabinet
for each Horizon II macro BTS site. Redundancy for the NIU functionality depends on a
redundant BTP. It means if a redundant BTP is installed, the integrated NIU functionality is
also supported.
68P02909W13-A
2-5
Dec 2008
Horizonmacro
The integrated NIU within the redundant BTP has connectivity to all the E1 links for
that site through the use of relays and switches. The redundant BTP can be switched
automatically to become the master BTP, taking over all the duties of the master BTP
(including controlling all E1 links at that site) through a BTS reset.
The switching fabric within the BTP is only capable of switching at a rate of 64 kbps.
A maximum of six physical TRX can be equipped to a Horizon II macro cabinet.
The Horizon II macro site does not support the use of CCB.
Horizonmacro
The BSS supports the Horizonmacro site type. The major architecture and capacity
requirements are described as follows:
The Horizonmacro site supports a maximum of 24 carriers.
The Horizonmacro site supports up to 6 Cells and a maximum of 12 carriers per Cell.
The Horizonmacro site supports a maximum of 6 E1 Ports. The first NIU (or MSI) in a
digital module shelf (Horizonmacro) can interface to two E1 links, the second NIU (or MSI)
in a digital module shelf can interface to one E1 link, the third NIU (or MSI) in a digital
module shelf can interface to two E1 links and the fourth NIU (or MSI) in a digital module
shelf can interface to one E1 link. The maximum 4 NIU (or MSI) boards can support
maximum 6 E1 ports.
The Horizonmacro site supports a single OML and multiple RSLs with 2:1 or 4:1
multiplexing mode. The Horizonmacro supports equipping each RSL to one logical TRX,
that is, a maximum of 24 RSLs allocated to 24 logical TRX.
The Horizonmacro site supports the following physical TRX equipment types: CTU, SCTU2
and DCTU2. CTU2D is not supported in Horizonmacro cabinet.
The Horizonmacro site has a fixed Master Cabinet (Cabinet 0) of Horizonmacro Cabinet
Type, and supports the addition of extension cabinets (Cabinet 1,2, and so on) with
Horizonmacro, Horizon II macro, Horizon II mini, Horizon II micro. The Horizonmacro
supports the addition of up to 3 Extension cabinets. This means a Horizonmacro is
restricted to a maximum of 4 cabinets.
NOTE
configuration, only the following cabinet combination in Table 2-2 is supported
in Horizonmacro site type.
2-6
68P02909W13-A
Dec 2008
Horizonmacro
Table 2-2 Horizonmacro cabinet configuration

Master cabinet
Expansion cabinet
Horizonmacro
CTU
CTU2
Horizonmacro
Horizon II macro
The master cabinet of Horizonmacro requires one BTP. For redundancy, add a standby BTP
in the digital module shelf of the master cabinet. Redundancy for the NIU module depends
on the number of redundant E1 links running to the site.
A maximum of six physical TRX can be equipped to a Horizonmacro cabinet.
68P02909W13-A
2-7
Dec 2008
Microcell enclosures
Microcell enclosures
Horizon II mini
The BSS supports the Horizon II mini site type. Horizon II mini can satisfy all the current
Horizon II macro requirements but also add significant functionality that enables it to be classed
as a Mini Macro BTS. The architecture is based on the Horizon II macro architecture and
effectively Horizon II mini behaves as a Horizon II macro cabinet.
So the major architecture and capacity requirements of Horizon II mini are like Horizon II
macro and are as follows:
The Horizon II mini site supports a maximum of 24 carriers.
The Horizon II mini site supports up to 6 Cells and a maximum of 12 carriers per Cell.
The Horizon II mini site supports a maximum of 6 E1 Ports. NIU functionality is integrated
into the BTP. From a functional standpoint, the Integrated NIU functions is same as the
standalone.
The Horizon II mini site supports a single OML and multiple RSLs with 2:1 or 4:1
multiplexing mode. The Horizon II mini supports equipping each RSL to one logical TRX,
that is, a maximum of 24 RSLs allocated to 24 logical TRX.
The Horizon II mini site supports the following physical TRX equipment types: CTU,
SCTU2, DCTU2, and CCTU2.
The Horizon II mini site has a fixed Master Cabinet (Cabinet 0) of Horizon II mini Cabinet
Type, and supports the addition of extension cabinets (Cabinet 1,2, and so on) with
Horizonmacro, Horizon II macro, Horizon II mini and Horizon II micro. The Horizon II mini
supports the addition of up to 3 Extension cabinets. This means a Horizon II mini site
is restricted to a maximum of 4 cabinets.
NOTE
configured as expansion cabinet are not recommended as an official
in Horizon II mini site type.
Table 2-3 Horizon II mini cabinet configuration

Master cabinet
Expansion cabinet
Horizon II mini
CTU2
CTU2D
None
2-8
68P02909W13-A
Dec 2008
Horizon II micro
Some software parameters have been added to limit Horizon II mini cabinets as a Mini BTS. The
Horizon II mini parameters allow the following:
Equip only one BTP to a Horizon II mini master cabinet. Horizon II mini does not support
hardware redundancy.
Equip a maximum of two physical TRX to a Horizon II mini cabinet. So the Horizon II mini
site without expansion cabinet only supports a maximum of 4 carriers.
Horizon II micro
The BSS supports the Horizon II micro site type. 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 unit.
The architecture is based on the Horizon II macro architecture and effectively Horizon II micro
behaves as if a Horizon II macro cabinet. So the major architecture and capacity requirements
of Horizon II micro are like Horizon II macro and are as follows:
The Horizon II micro site supports a maximum of 24 carriers.
The Horizon II micro site supports up to 6 Cells and a maximum of 12 carriers per Cell.
The Horizon II micro site supports a maximum of 6 E1 Ports. NIU functionality is

integrated into the BTP. From a functional standpoint, the Integrated NIU functions are
same as the standalone NIU.
The Horizon II micro site supports a single OML and multiple RSLs with 2:1 or 4:1
multiplexing mode. The Horizon II micro supports equipping each RSL to one logical TRX,
that is, maximum of 24 RSLs allocated to 24 logical TRX.
The Horizon II micro site supports the following TRX equipment types: CTU, SCTU2,
DCTU2, and CCTU2.
The Horizon II micro site has a fixed Master Cabinet (Cabinet 0) of Horizon II micro
Cabinet Type, and supports the addition of extension cabinets (Cabinet 1,2, and so on)
with Horizonmacro, Horizon II macro, Horizon II mini and Horizon II micro. Horizon II
micro support the addition of up to 3 Extension cabinets. This means a Horizon II micro
site is restricted to a maximum of 4 cabinets.
NOTE
in Horizon II micro site type.
Table 2-4 Horizon II micro cabinet configuration

Master cabinet
Expansion cabinet
Horizon II micro
CTU2
CTU2D
None
68P02909W13-A
2-9
Dec 2008
Horizon II micro
Some software parameters have been added to limit Horizon II micro cabinets as a Micro BTS.
The Horizon II micro parameters allow the following:
Equip only one BTP to a Horizon II micro master cabinet. Horizon II micro does not
support hardware redundancy.
Equip only one physical radio to a Horizon II micro cabinet. So the Horizon II micro site
without expansion cabinet only supports a maximum of 2 carriers.
2-10
68P02909W13-A
Dec 2008
EGPRS configuration
EGPRS configuration
EGPRS configuration limitations

EDGE is only supported in CTU2 and CTU2D hardware radio type. Following factors affect
EDGE capability:
Radio board type/TRX type (SCTU2/DCTU2/CCTU2) configuration for radio board type.
ITS (Improve Timeslot Sharing) feature and CTU2D Capacity feature.
BBH and BCCH impact.
For additional information, refer to Table 2-5 and Table 2-6.
EDGE capacity reporting

The information required for EDGE capability reporting is as follows:
Determine if the TRX board is matched or mismatched, refer to Table 2-5.
Determine if the Improve Timeslot Sharing and CTU2D Capacity is restricted or

unrestricted, refer to Table 2-5.
Determine if the TRX is configured for Baseband hopping and BCCH timeslot, refer to
Table 2-6.
68P02909W13-A
2-11
Dec 2008
Table 2-5 TRX hardware and software configuration mismatch

CTU
TRX
type/HW
type
Alarm
indication
SCTU2
GPRS/
EDGE
capability
CTU
OK
CS
GPRS
CS1-4
CTU2
WARNING
CS
GPRS
CS1-4
Alarm
indication
GPRS/
EDGE
capability
MAJOR CS
GPRS
CS1-4
OK
CS
GPRS
CS1-4
EDGE
MCS1-9
DCTU2
Alarm
indication
CRITICAL
OK
CCTU2
GPRS/
EDGE capability
Alarm
indication
GPRS/
EDGE capability
OOS
CRITICAL
OOS
Carrier
A
Carrier
B
ITS
Unrestricted:
CS
GPRS
CS1-4
EDGE
MCS1-9
CS
GPRS
CS1-4
MAJOR
CS
GPRS CS1-4
ITS
Restricted:
CS
GPRS
CS1-4
CTU2D WARNING
CS
GPRS
CS1-4
OK
CS
GPRS
CS1-4
EDGE
MCS1-9
OK
Carrier
A
ITS
Unrestricted:
CS
GPRS
CS1-4
EDGE
MCS1-9
Carrier OK
B
CS
GPRS
CS1-4
ITS
Restricted:
CS
GPRS
CS1-4
2-12
Carrier
A
Carrier
B
CAP
Unrestricted:
CS
GPRS
CS1-4
EDGE
MCS1-9
CS
GPRS
CS1-4
CAP
Restricted:
reverts
to
DCTU2
operation.
68P02909W13-A
Dec 2008
NOTE
If the warning alarm is raised (TRX hardware and software configuration

mismatched), no action is taken, service is unaffected.
If the major alarm is raised (TRX hardware and software configuration

mismatched), TRX capability is affected and downgraded.
If the critical alarm is raised (TRX hardware and software configuration

mismatched), impacted TRXs are taken OOS.
Table 2-6 EDGE capability of BBH and/or BCCH configured
BBH
BCCH
BBH
BCCH
Carrier
A EDGE
Capability
NO
N/A
NULL
NULL
YES
NULL
YES
N/A
NULL
NULL
NO
NULL
NO
N/A
NO
NO
YES
NO
NO
N/A
N/A
YES
NO
NO
NO
N/A
YES
N/A
NO
NO
YES
N/A
N/A
N/A
NO
NO
NO
N/A
N/A
N/A
YES
NO
YES
N/A
N/A
N/A
NO
NO
Carrier A
TRX Type
SCTU2
DCTU2
CCTU2
Carrier B
Carrier
B EDGE
Capability
For example:
Example 1
If one CTU2D radio board is configured as CCTU2, and CAP feature is unrestricted, refer to
Table 2-5. Carrier A has EDGE capability, Carrier B has Non-EDGE capability.
Example 2
If One CTU2 radio board is configured as CCTU2, refer to Table 2-5. Carrier A and Carrier B
have Non-EDGE capability.
Example 3
If one CTU2D radio board is configured as DCUT2 and carrier A is configured as BBH, and ITS
feature is unrestricted, refer to Table 2-5. Carrier A has EDGE capability and Carrier B is
blank if Carrier A if EDGE traffic in Carrier A, so refer to Table 2-6. Carrier A has no EDGE
capability and Carrier B has no EDGE capability.
68P02909W13-A
2-13
Dec 2008
Dynamic allocation of EDGE sub-timeslots
Dynamic allocation of EDGE sub-timeslots

GPRS/EDGE backhaul allocations are made on a dynamic basis. Initially a 16 k resource is
allocated to the PDCH, as the requirements for bandwidth change, the BSC may decide to
increase/decrease the backhaul allocations and will add/delete 16 k resources to the same
air timeslot.
For GPRS, each PDCH is initially assigned a single 16 k, a single additional sub-timeslot
can be added for support of CS3/4.
For EDGE, each PDCH is initially assigned a single 16 k, a maximum of three additional
sub-timeslot can be added for support of higher data rates.
The FlexAbis (PS) has superseded the VersaTRAU feature, which allowed a pool of DS0
resources to be shared by multiple air timeslots. (Refer to Timeslots assignment on the Abis
interface on page 3-6.)
2-14
68P02909W13-A
Dec 2008
Chapter
3
Timeslots on the Abis interface
68P02909W13-A
Dec 2008
3-1
Introduction
Introduction
The following decisions affect the reliability and the availability of BSS:
BTS topologies on page 3-3.

The BSC provides flexible BTS topologies on the Abis interface. These topologies are star
topology, chain topology, tree topology, and ring topology.
Timeslots assignment on the Abis interface on page 3-6.

This section describes the principles and algorithm of timeslot assignment on the Abis
interface, the principles of semi-permanent connection and the principles of idle timeslot
assignment.
BTS multiplexing mode on page 3-10.

Multiplexing allows multiple signaling resources to be combined onto a single E1 timeslot.
The operator controls the number of signaling connections that can be multiplexed. The
multiplexing mode to use is dependent on factors such as, call model and usage of HR
(further information in chapter 4 RSL/OML/E1 Dimensioning rules).
Manual timeslot assignment on the Abis interface on page 3-16.

This section describes the manual timeslot assignment on the Abis interface. Timeslot
assignment on the Abis interface is required when the BTSs, cells, TRXs, idle timeslots,
and monitoring timeslots are added. By default, the timeslots are assigned automatically.
If required, the timeslots can also be assigned manually on the Abis interface .
3-2
68P02909W13-A
Dec 2008
BTS topologies
BTS topologies
Introduction
The BSC provides flexible BTS topologies on the Abis interface. These topologies are star
topology, chain topology, tree topology, and ring topology. Theses topologies can be mixed
under a single BSC.
Star topology
Star topology (Figure 3-1) refers to the topology in which the BTSs connect to the BSC directly.
These BTSs do not have lower-level BTSs. Star topology is a commonly used network topology
due to a simple network structure, convenient capacity expansion, and high reliability.
Figure 3-1 Star topology
BTS0
BSC
BTS1
BTS2
ti-GSM-Hardware-Star topology-00003-ai-sw
Chain topology
In the belt-shaped areas (such as highways) where the traffic volume is low, it is a waste of
transmission resources to use the star topology. In this case, the chain topology can be used.
In the chain topology (Figure 3-2), a cascaded BTS processes its own timeslots and transparently
transmits the timeslots of the lower-level BTSs.
The chain topology has some disadvantages, such as inconvenient capacity expansion and
reduced fault tolerance.
In the chain topology, a maximum seven level cascades BTS connection can be supported.
68P02909W13-A
3-3
Dec 2008
Tree topology
Figure 3-2 Chain topology
BSC
BTS0
BTS1
BTS2
ti-GSM-Hardware-Chain topology-00004-ai-sw
Tree topology
In the tree topology (Figure 3-3), the BTS connecting to the BSC are through the parent BTS.
All the child BTS connect to the parent BTS. The parent BTS exchanges timeslots with each
child BTS. The tree topology combines the features of star topology and chain topology. Its fault
tolerance is lower than the star topology but higher than the chain topology. The structure of
the tree topology is complicated. Therefore, the capacity expansion and maintenance of the
network is difficult.
In the tree topology, a maximum seven level cascades BTS connection can be supported.
Figure 3-3 Tree topology
BTS1
BSC
BTS0
BTS2
ti-GSM-Hardware-Tree topology-00005-ai-sw
Ring topology
Ring topology is a special type of chain topology. All the BTSs connect with each other as a
normal chain and the last-level BTS connects with the BSC to form a ring. If the communication
at a point in the ring is broken, the topology of the BTSs before the breakpoint remains the same
and the BTSs after the breakpoint form a new chain connection in the reverse direction.
Therefore, two chains are formed and the BTSs can still offer services. This improves the
robustness of the system.
In the ring topology, a maximum five level cascades BTS connection can be supported.
3-4
68P02909W13-A
Dec 2008
Ring topology
Figure 3-4 shows the ring topology.
Figure 3-4 Ring topology
BSC
BTS0
BTS1
BTS2
ti-GSM-Hardware- Ring topology-00006-ai-sw
68P02909W13-A
3-5
Dec 2008
Timeslots assignment on the Abis interface
Timeslots assignment on the Abis interface
Introduction
The BSS supports flexible Abis resource allocation algorithm.
FlexAbis (PS) can be supported when the BTS supports 64 kbit/s switching with statistic
multiplexing mode or the BTS supports 16 kbit/s switching.
The statistic multiplexing means that n signaling channels use one 64 kbit/s timeslot. The n
signaling channels work in different time slices, that is, Time Division Multiplexing (TDM). In
statistic multiplexing mode, more than one channel is multiplexed onto one 64 kbit/s bandwidth.
BSC offers 2:1 and 4:1 OML/RSL multiplexing mode.
The description of FlexAbis (PS) algorithm is as follows:
Figure 3-5 FlexAbis (PS) algorithm

S ite1
S ite0
Link 1
Link 0
B
S
S ite2
Link 2
P S Id le P oo l 0
P S Id le P oo l1
P S Id le P o o l1
P S Id le P o o l2
P S Id le P oo l2
F ixed1
B
P S Id le P oo l2
C
F ixed0
F ixed2
ti-GSM-FlexAbis_algorithm -00007-ai-sw
Link 0 in Abis interface is composed of Fixed 0 and PS Idle Pool 0/1/2. Link 1 in Abis
interface is composed of Fixed 1 and PS Idle Pool 1/2. Link 3 in Abis interface is composed
of Fixed 2 and PS Idle Pool 2.
CS and PS master TS is entirely fixedly allocated from Fixed 0/1/2. Only PS slave TS is
dynamically allocated from PS Idle Pool 0/1/2. TS dynamic allocation from PS Idle Pool can
be permitted while CS call setup or PS master TS allocated in Site.
TS in PS idle Pool 0 can only be allocated to PS slave link in Site0. TS in PS idle Pool 1 can
only be allocated to PS slave link in Site1. TS in PS idle Pool 2 can only be allocated to PS
slave link in Site 2. TS in PS idle Pool 0/1/2 cannot be shared between Site 0/1/2.
3-6
68P02909W13-A
Dec 2008
TS number of PS Idle Pool in link 0/1/2 are equally allocated Abis TS resource. For
instance, if PS Idle Pool 2 allocates 8 TS, then in link 0, link 1 and link 2 the TS number of
PS Idle Pool 2 are same and not changeable.
In different E1s of cascaded BTSs, the Fixed and PS Idle pool must stay in the same 64
kbit/s timeslot and the relative positions of their corresponding sub-timeslot numbers
must remain the same.
TS in PS idle Pool is allocated for PS slave TS at the 16 k level. TS in PS Idle Pool can be
dynamically allocated as PS slave TS in BTS.
After one 16 k TS in PS Idle Pool has been dynamically allocated to one PS slave TS, BSC
only sends the message to inform the specific site and no need to inform other cascaded
BTS.

BSC supports FlexAbis (PS) algorithm which are offered as Fixed 16 k and Fixed 64 k switches
from LMT GUI.
FlexAbis (PS->Fixed 16 k) can be supported when BTS support 16 kbit/s switching. The
principles of timeslot assignment on the Abis interface are as follows:
Each E1 port of the BTS manages sub-timeslots 0255. Sub-timeslots 07 are used for
synchronization. They cannot be assigned to OML, RSL, TCH, idle TS and monitor TS.
The OML of a BTS is assigned on timeslot 31. In n:1 64 kbit/s statistic multiplexing mode,
the OML is assigned on timeslot 31. In the physical 16 kbit/s multiplexing mode, the OML
is assigned on sub-timeslot 3 of timeslot 31.
On one link, n:1 64 kbit/s statistic multiplexing and physical 16 kbit/s multiplexing cannot
coexist. The OMLs, RSLs, idle timeslots, monitoring timeslots, and TCHs are assigned
based on sub-timeslots.
In physical 16 kbit/s multiplexing mode, the OMLs, RSLs, idle timeslots, monitoring
timeslots, or TCHs can be multiplexed onto one 64 kbit/s timeslot.
In n:1 64 kbit/s statistic multiplexing mode:

The timeslots of different BTSs cannot be multiplexed onto one 64 kbit/s timeslot.
Traffic channels and signaling channels cannot be multiplexed onto one 64 kbit/s
timeslot.
Use one 64 kbit/s timeslot even if only one signaling channel or traffic channel
is configured.
Monitoring timeslots and other timeslots cannot coexist in one 64 kbit/s timeslot,
except for the semipermanent connection.
In different E1s of cascaded BTSs, all the objects multiplexed onto one 64 kbit/s
timeslot must stay in the same 64 kbit/s timeslot and the relative positions of their
corresponding sub-timeslot numbers must remain the same.
68P02909W13-A
3-7
Dec 2008
The timeslots of different equipment groups in one BTS cannot be transmitted on

the 64 kbit/s bandwidth of the same E1.
Idle timeslots and the timeslots on TRXs cannot use the same 64 kbit/s bandwidth
with the semipermanent connection.
The number of OMLs in Abis interface board cannot exceed 256.
The number of RSLs in Abis interface board cannot exceed 256.
When BTSs, cells, TRXs, idle timeslots, or monitoring timeslots are added, assign timeslots
on the Abis interface. The resources on the Abis interface are assigned to the following
objects: OMLs, RSLs, channels, idle timeslots, and monitoring timeslots.
Assign the timeslots for a BTS in the following order: OMLs, RSLs, TCHs, idle timeslots,
and monitoring timeslots.
Except the incoming E1 timeslot, if the upper level BTS has an E1 port directly connected
to the BSC, this E1 port is selected preferentially during the timeslot assignment of the
upper-level BTS.
Due to the switching fabric within the BTS only capable of switching at a rate of 64 kbps, the
FlexAbis (PS->Fixed 16 k) solution allocates terrestrial ABIS resources at 16 kbps sub-timeslot
and therefore restrictions are required on the LMT to operate within the boundaries imposed
by 64 kbps switching limitations.
Besides the restrictions/principles that are valid for FlexAbis (PS->Fixed 64 k), there are more
restrictions/principles as follows:
The BSC multiplexes RSLs which are allocated to logical TRXs located on the same physical
TRX board on the same 64 kbit/s E1 timeslot for Motorola Site Types.
The BSC assigns an integrated 64 k E1 backhaul for traffic channel in a TRX, and BSC
assigns another integrated 64 k E1 backhaul for Idle TS (for PDTCH bandwidth).
The total number of integrated E1 TSs allocated to an EDGE capable logical TRX cannot
exceed 8.
The total number of integrated E1 TSs allocated to a NON EDGE capable logical TRX
cannot exceed 4.
3-8
68P02909W13-A
Dec 2008
Principles of Idle Timeslot Assignment
Principles of Idle Timeslot Assignment

Idle timeslots carry the GPRS/EDGE services in the BSS. The principles of idle timeslot
assignment are as follows:
Idle timeslots are assigned based on BTSs. Each BTS can be assigned maximum 128
idle timeslots.
When assigning idle timeslots for a BTS, the user can manually assign timeslots on the
Abis interface for the newly added idle timeslots and site reset is triggered.
Configuring idle timeslots consists of adding and deleting timeslots.
The relative positions of idle timeslots for BTSs must remain unchanged. For example, a
BTS has three idle timeslots. Two of them are deleted and then added again. In this
case, the relative positions of the sub-timeslots of these three idle timeslots must remain
unchanged.
Principles of Monitor Timeslot Assignment

Monitoring timeslot is a special semi-permanent connection. It is a semi-fixed transparent path
in the BSC. This path monitors the running status of the BSS. This transparent path connects
the A Interface and an E1 port of a BTS. The rates of monitoring timeslot are 64 kbit/s.
Semi-permanent connection supersedes Nail/Path timeslot which is not available any more.
68P02909W13-A
3-9
Dec 2008
BTS multiplexing mode
BTS multiplexing mode
Introduction
The BTS multiplexing in the BSC refers to the multiplexing of the LAPD signaling on the E1
timeslots of the Abis interface. The BSC offers two 64 kbit/s statistic multiplexing modes 2:1
and 4:1. In n:1 multiplexing modes, n signaling timeslots occupy one E1 timeslot (64 kbit/s)
on the Abis interface. All the timeslots perform the 64 kbit/s exchange on the Abis interface
board of BSC. The BTS multiplexing mode is only used for signaling link (RSL or OML), and
does not restrict the CS and PS service. For instance, the speech rate is 16 kbit/s or 8 kbit/s
(half rate), four speech channels (eight channels for half rate) occupy one 64 kbit/s timeslot on
the Abis interface. BSC supports multiple BTS multiplexing modes. Because of the transparent
transmission relation between cascaded BTSs, one E1 supports multiple multiplexing modes, as
shown in Figure 3-6.
Figure 3-6 Multiple multiplexing modes

A0
A1
A3
BTS0
BTS1
BTS3
(2:1)
(2:1)
(4:1)
BSC
A2
BTS2
(4:1)
BTSn
(n:1)
ti-GSM-Hardware-Multiple multiplexing_modes-00008-ai-sw
As shown in Figure 3-6, the four E1s are A0, A1, A2, and A3. Assume that the multiplexing
modes of BTS 0, BTS 1, BTS 2, and BTS 3 are 2:1, 2:1, 4:1, and 4:1. Then two multiplexing
modes exist on the BSC. The multiplexing mode of each E1 on the link where the BTS is located
is subject to the multiplexing mode of the BTS itself.
Two multiplexing modes exist on A0, they are 2:1 and 4:1.
Two multiplexing modes exist on A1, they are 2:1 and 4:1.
One multiplexing mode exists on A2, it is 4:1.
One multiplexing mode exists on A3, it is 4:1.
3-10
68P02909W13-A
Dec 2008
Timeslot assignment in N:1 multiplexing mode
Timeslot assignment in N:1 multiplexing mode

Multiplexing mode 2:1 and 4:1 of E1 timeslot assignment is as follows.
For example, the timeslot assignment of each multiplexing mode is based on the following
conditions:
Flexible Abis Mode is FlexAbis (PS->Fixed 64 k)
The speech rate (Full Rate) is 16 kbit/s. Four channels of speech occupy one 64 kbit/s
timeslot on the Abis interface.
For TRX 00, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is the SDCCH.
The BCCH and the SDCCH use the RSL, that is, the timeslots on the RSL contain the
timeslots on the T00C0 and T00C1. Therefore, T00C0 and T00C1 are not listed in the
following tables.
2:1 Multiplexing mode

Assume that BTS 0 is configured with a cell, the cell is configured with four TRXs, the channels
in the cell use default settings, and the multiplexing mode is 2:1. Table 3-1 lists the timeslot
assignment on the Abis interface.
Table 3-1 Timeslot assignment in 2:1 multiplexing mode

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
RSL01+RSL02
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
RSL03
T03C0
T03C1
T03C2
T03C3
10
T03C4
T03C5
T03C6
T03C7
11
...
31
OML0+RSL00
68P02909W13-A
3-11
Dec 2008
NOTE
Sub-timeslot 4 to 7 of TS2 cannot be shared with other TRX.

Assume that BTS 0 is configured with a cell, the cell is configured with four carriers, the
channels in the cell use default settings, and the multiplexing mode is 4:1. Table 3-2 lists the
timeslot assignment on the Abis interface.
Table 3-2 Timeslot assignment in 4:1 multiplexing mode

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
RSL03
T03C0
T03C1
T03C2
T03C3
T03C4
T03C5
T03C6
T03C7
10
...
31
OML0+RSL00+RSL01+RSL02
NOTE
Timeslot assignment in tree topology

The timeslot assignment on the Abis interface in the tree topology is more complicated. The
multiplexing modes of BTS 0, BTS 1, BTS 2, and BTS 3 are 2:1, 2:1, 4:1, and 4:1. Each BTS
is configured with one cell, the cell is configured with two carriers, and the channels in the
cell use default settings. BTS 0 is the parent node. Table 3-3 to Table 3-6 shows the timeslot
assignment on E1s (A0A3) of BTSs.
3-12
68P02909W13-A
Dec 2008
NOTE
The timeslot assignment of each multiplexing mode is based on the following
conditions:
Flexible Abis Mode is FlexAbis (PS->Fixed 64 k)
The speech rate (Full Rate) is 16 kbit/s. Four channels of speech occupy one 64
kbit/s timeslot on the Abis interface.
For the TRX00, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is the
SDCCH.
The BCCH and the SDCCH use the RSL, that is, the timeslots on the RSL contain
the timeslots on the T00C0 and T00C1. Therefore, T00C0 and T00C1 are not
listed in the following tables.
T00C2 to T00C7 and T01C0 to T01C7 are assigned for CS TS of BTS0. T10C2 to
T10C7 and T11C0 to T11C7 are assigned for CS TS of BTS1. T20C2 to T20C7
and T21C0 to T21C7 are assigned for the CS TS of BTS2. T30C2 to T30C7 and
T31C0 to T31C7 are assigned for CS TS of BTS3.
T00C0additional
BTS0.
T10C0additional
BTS1.
T20C0additional
BTS2.
T30C0additional
of BTS3.
to T00C03additional are assigned for the PS idle TS Pool of

to T30C03additional are assigned for the PS idle TS Pool
Table 3-3 Timeslot assignment on A0

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
RSL01
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
OML1+RSL10
T10C2
T10C3
T10C4
T10C5
T10C6
T10C7
RSL11
10
T11C0
T11C1
T11C2
T11C3
11
T11C4
T11C5
T11C6
T11C7
12
OML2+RSL20+RSL21
Continued
68P02909W13-A
3-13
Dec 2008
Table 3-3 Timeslot assignment on A0 (Continued)

Timeslot No.
Sub-Timeslot No.
13
T20C2
T20C3
T20C4
T20C5
14
T20C6
T20C7
15
T21C0
T21C1
T21C2
T21C3
16
T21C4
T21C5
T21C6
T21C7
17
OML3+RSL30+RSL31
18
T30C2
T30C3
T30C4
T30C5
19
T30C6
T30C7
20
T31C0
T31C1
T31C2
T31C3
21
T31C4
T31C5
T31C6
T31C7
22
T00C0additional T00C1additional
T00C2additional
T00C3additional
23
T10C2additional
T10C3additional
24
T20C2additional
T20C3additional
25
T30C2additional
T30C3additional
...
31
OML0+RSL00

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T10C2
T10C3
T10C4
T10C5
T10C6
T10C7
RSL11
T11C0
T11C1
T11C2
T11C3
T11C4
T11C5
T11C6
T11C7
OML3+RSL30+RSL31
T30C2
T30C3
T30C4
T30C5
T30C6
T30C7
T31C0
T31C1
T31C2
T31C3
10
T31C4
T31C5
T31C6
T31C7
11
T10C2additional
T10C3additional
12
T30C2additional
T30C3additional
...
31
OML1+RSL10
3-14
68P02909W13-A
Dec 2008

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T20C2
T20C3
T20C4
T20C5
T20C6
T20C7
T21C0
T21C1
T21C2
T21C3
T21C4
T21C5
T21C6
T21C07
T20C2additional
T20C3additional
11
...
31
OML2+RSL20+RSL21

Timeslot No.
Sub-Timeslot No.
0 and 1
2 and 3
Synchronization Synchronization
4 and 5
6 and 7
Synchronization
Synchronization
T30C2
T30C3
T30C4
T30C5
T30C6
T30C7
T31C0
T31C1
T31C2
T31C3
T31C4
T31C5
T31C6
T31C7
T30C2additional
T30C3additional
...
31
OML3+RSL30+RSL31
NOTE
68P02909W13-A
3-15
Dec 2008
Manual timeslot assignment on the Abis interface
Manual timeslot assignment on the Abis interface
Introduction
Timeslot assignment on the Abis interface is required when the BTSs, TRXs, idle timeslots, and
monitoring timeslots are added. By default, the timeslots are assigned automatically. User can
also manually assign timeslots on the Abis interface if required, also a site reset triggered to
affect the new timeslots configuration.
When manually assigning timeslots on the Abis interface, adhere to the following principles:
The objects that support the manual timeslot assignment are as follows: OMLs, RSLs,
channels, idle timeslots, and monitoring timeslots.
Assign timeslots on the Abis interface for multiple objects at a time.
If timeslots on the Abis interface are manually assigned for the object that is located in a
cascaded link, also manually assign the incoming Abis timeslots for all the BTSs on the link.
If a timeslot to be manually assigned for an object is used by another object, the timeslot
cannot be manually assigned unless the object using the timeslot is deleted or moved
to another timeslot.
The multiplexing mode of assigned timeslots must be the same as the multiplexing mode of
the BTS. For instance, if the BTS uses the 2:1 multiplexing mode, do not multiplex four
signaling links together.
In the incoming E1 and outgoing E1 links of all the cascaded BTSs on a link, locate all the
objects multiplexed onto one 64 kbit/s timeslot in the same 64 kbit/s timeslot and all the
relative positions of sub-timeslots must remain unchanged.
When adding BTSs, cells, TRXs, idle timeslots, and monitoring timeslots, user can manually
assign timeslots for new added objects.
When user wants to change the assignment mode of the timeslots of an object from manual
mode to auto mode, the assignment mode of the timeslots that are already assigned cannot
be changed. When user wants to change the assignment mode of the timeslots of an
object from auto mode to manual mode, the user has to release the timeslots that are
automatically assigned for the object.
User can assign the timeslots on the Abis interface for the BTSs on only one link of a
topology at a time.
3-16
68P02909W13-A
Dec 2008
Chapter
4
RSL/OML/E1 dimensioning rules
68P02909W13-A
Dec 2008
4-1
RSL/OML dimensioning rules
RSL/OML dimensioning rules
General dimensioning rules for RSL/OML are as follows:
There is one RSL per carrier.
There is one OML per site.
Adopt 2:1 OML/RSL multiplexing mode if AMR half rate call or GSM half rate call is
enabled in the site.
Adopt 4:1 OML/RSL multiplexing mode if no half rate call (AMR half rate call or GSM half
rate call) is enabled in the site.
Only one OML/RSL multiplexing mode is allowed in one BTS, mixture of different
multiplexing mode is not allowed in one BTS.
4-2
68P02909W13-A
Dec 2008
E1 interconnect dimensioning
Determine the number of E1 links required to connect to a BTS. If required, add redundant
links. To determine the impact of different coding schemes on interconnect planning, use the
following equation:
NBSCBT S = Roundup
[(nEGP RS 8) + (nC GP RS 4) + (nGGP RS 2) + (L + 1) /M ]

31
2:1 Multiplexing mode is adopted, M=2.

4:1 Multiplexing mode is adopted, M=4.
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.
the number of RSL which equals to number of carriers per BTS,

1 means one OML link.
For example:
One BTS includes 12 carriers; 2 carriers are used to carry EGPRS service, 4 carriers are used to
carry GPRS CS3 and CS4 service, 6 carriers are used to carry GPRS CS1 and CS2 and GSM
voice service, and AMR half rate call is enabled. So nEGPRS is 2, nCGPRS is 4, nGGPRS is 6, 32
kbit/s RSL is adopted, and L32 is 12, and L16 =0, 32 kbit/s OML is used.
So the required E1 number NBSC-BTS is Roundup {(2*8+4*4+6*2+12/2+0.5)/31} = 2.
68P02909W13-A
Dec 2008
4-3
4-4
68P02909W13-A
Dec 2008
Chapter
5
Glossary
68P02909W13-A
Dec 2008
5-1
Glossary of terms
Chapter 5: Glossary
Glossary of terms
AMR
Adaptive Multi-Rate
BBH
Baseband Hopping
BCCH
Broadcast Control Channel
BSC
Base Station Controller
BSS
Base Station System
BTP
Base Transceiver Processor
BTS
Base Transceiver Station
CCB
Cavity Combining Block
CTU
Compact Transceiver Unit
CTU2
Compact Transceiver Unit 2
CTU2D PWR
CTU2D Double Density Power Mode
CTU2D CAP
CTU2D Double Density Capacity Mode
DRI
Digital Radio Interface
E1
32 channel 2.048 Mbps span line
EDGE
Enhanced Data Rates for Global Evolution
EGPRS
Enhanced-GPRS
FMUX
Fibre Optic Multiplexer
GPRS
General Packet Radio System
GSM
Global System for Mobile Communication
HDLC
High Level Data Link Control
ITS
Improve Timeslot Sharing
LAPD
Link Access Protocol Data
MS
Mobile Station
MSC
Mobile Switching Center
MSI
Multiple Serial Interface
NIU
Network Interface Unit
OML
Operation & Maintenance Link
OMC
Operations and maintenance centre
PCU
Packet control unit
5-2
68P02909W13-A
Dec 2008
Glossary of terms
RSL
Radio Signaling Link
TS
Timeslot
VersaTRAU
Versatile Transcoder Rate Adaptation Unit
XCDR
Transcoder
XMUX
Expansion Multiplexer
68P02909W13-A
Dec 2008
5-3
Glossary of terms
Chapter 5: Glossary
5-4
68P02909W13-A
Dec 2008
Index
Index
A
Abis BTS overview . . . . . . . . . . . . .
Abis BTS architecture overview . . . . . .
BSS topologies . . . . . . . . . . . . . .
1-3
1-3
1-3
Abis BTS overview (contd.)

Supported BTS types . . . . . . . . . . .
1-3
B
BTS multiplexing mode . . . . . . . . . .
2:1 multiplexing mode . . . . . . . . .
4:1 multiplexing mode . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
Timeslot assignment in N:1 multiplexing
mode . . . . . . . . . . . . . . . . . .
Timeslot assignment in tree topology . .
BTS planning overview . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . . .
3-10
3-11
3-12
3-10
BTS planning overview (contd.)

Outline of planning steps . . .
Macrocell and microcell BTS
BTS topologies . . . . . . . . .
Chain topology . . . . . . . .
Introduction. . . . . . . . . .
Ring topology . . . . . . . . .
Star topology . . . . . . . . .
Tree topology . . . . . . . . .
3-11
3-12
2-3
2-3
. . .
sites
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-3
2-4
3-3
3-3
3-3
3-4
3-3
3-4
E
EGPRS configuration . . . . .
Dynamic allocation of EDGE
timeslots . . . . . . . . . .
. . . . . . . 4-3
. . . . . .
2-11
sub. . . . . .
2-14
EGPRS configuration (contd.)

EDGE capacity reporting . . . . . . . .
EGPRS configuration limitations . . . .
2-11
2-11
G
Glossary of terms . . . . . . . . . . . . . .
5-2
I
Introduction. . . . . . . . . . . . . . . 2-2, 3-2
M
Macrocell cabinets . . . . . . . . . . . . .
Horizon II macro . . . . . . . . . . . . .
Horizonmacro . . . . . . . . . . . . . . .
2-5
2-5
2-6
Manual timeslot assignment

interface . . . . . . . . . .
Introduction. . . . . . . .
Microcell enclosures . . . .
68P02909W13-A
Dec 2008
on the Abis
. . . . . . .
3-16
. . . . . . .
3-16
. . . . . . . . 2-8
IX-5
Index
Microcell enclosures (contd.)

Horizon II micro . . . . . . . . . . . . .
Microcell enclosures (contd.)

2-9
Horizon II mini . . . . . . . . . . . . . .
2-8
R
RSL/OML dimensioning rules . . . . . . . .
4-2
S
System architecture. . . . . . . . . . . . .
System components . . . . . . . . . . . .
1-2
1-2
T
Timeslots assignment on the Abis interface . . . . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . . .
Timeslots assignment on the Abis interface (contd.)

3-6
3-6
Principles of timeslot assignment on the Abis

interface . . . . . . . . . . . . . . . . . 3-7
IX-6
68P02909W13-A
Dec 2008

RSR10 BTS Equipment Planning Guide 68P02909W13-A

Uploaded by

Document Information

Original Description:

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

RSR10 BTS Equipment Planning Guide 68P02909W13-A

Uploaded by

Copyright:

Available Formats

Equipment Planning Guide

2008 Motorola, Inc. All Rights Reserved.

PRELIMINARY - UNDER DEVELOPMENT