RSR10 BTS Equipment Planning Guide 68P02909W13-A

Motorola B2B Collateral Branding UK Manual Cover insert A4 Text Field Template (02/10/07)

Sign o� ........................................ date ................ Sht no 1 of 1 ag-UK-Manual Cover insert A4 Text Fields Template-00001-v02-ai-sw

Customer Documetation UK 2007

Equipment Planning Guide

68P02909W13-A

RSR10

Using this template follow these procedures.

1. Complete all the text fields using provided spreadsheet and specification information2. Save file using appropriate naming title/convention in PDF format

© 2008 Motorola, Inc. All Rights Reserved.

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes noliability resulting from any inaccuracies or omissions in this document, or from use of the information obtainedherein. 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 contenthereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liabilityarising out of the application or use of any product, software, or circuit described herein; neither does it conveylicense under its patent rights or the rights of others. It is possible that this publication may contain references to, orinformation about Motorola products (machines and programs), programming, or services that are not announcedin your country. Such references or information must not be construed to mean that Motorola intends to announcesuch Motorola products, programming, or services in your country.

Copyrights

This document, Motorola products, and 3rd Party Software products described in this document may includeor describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductormemories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, andother 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive rightto 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 theMotorola 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 purchaseof Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, anylicense 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 aproduct.

Restrictions

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No partof the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any language or computer language, in any form or by any means, without prior written permissionof Motorola, Inc.

License Agreements

The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by expresslicense 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 NOTdesigned, manufactured, or intended for use as on-line control equipment in the following hazardous environmentsrequiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft CommunicationSystems, 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 servicenames are the property of their respective owners.

The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copiesof the Declaration of Compliance and installation information in accordance with the requirements of EN50385 canbe 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 CustomerNetwork Resolution Center contact information. Alternatively if you do not have access to CNRC or theinternet, contact the Local Motorola Office.

PRELIMINARY - UNDER DEVELOPMENT Dec 2008

Tableof

Contents

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

RSR10 BTS Equipment Planning GuideRevision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Incorporation of Change Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524–hour support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Questions and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9In EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9In non-EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Ordering documents and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Document banner definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1: BSS equipment overviewSystem architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Abis BTS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Supported BTS types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3BSS topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Abis BTS architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Chapter 2: BTS planning steps and rulesIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2BTS planning overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

68P02909W13-A i

Dec 2008 PRELIMINARY - UNDER DEVELOPMENT

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Outline of planning steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Macrocell cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Horizon II macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Microcell enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Horizon II mini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Horizon II micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

EGPRS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11EGPRS configuration limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11EDGE capacity reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Dynamic allocation of EDGE sub-timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Chapter 3: Timeslots on the Abis interfaceIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2BTS topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Star topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Chain topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Tree topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Ring topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Timeslots assignment on the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Principles of timeslot assignment on the Abis interface . . . . . . . . . . . . . . . . . . . 3-7Principles of Idle Timeslot Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Principles of Monitor Timeslot Assignment . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

BTS multiplexing mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Timeslot assignment in N:1 multiplexing mode . . . . . . . . . . . . . . . . . . . . . . . 3-112:1 Multiplexing mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114:1 Multiplexing mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Timeslot assignment in tree topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Manual timeslot assignment on the Abis interface . . . . . . . . . . . . . . . . . . . . . . . . 3-16Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Chapter 4: RSL/OML/E1 dimensioning rulesRSL/OML dimensioning rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2E1 interconnect dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Chapter 5: GlossaryGlossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

ii 68P02909W13-A


Listof

Figures

List of Figures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Figure 1-1: BSS block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Figure 1-2: Logic Abis BTS architecture diagram . . . . . . . . . . . . . . . . . . . . . . . . 1-4Figure 3-1: Star topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Figure 3-2: Chain topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Figure 3-3: Tree topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Figure 3-4: Ring topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Figure 3-5: FlexAbis (PS) algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Figure 3-6: Multiple multiplexing modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

68P02909W13-A iii


List of Figures

iv 68P02909W13-A


Listof

Tables

List of Tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Table 1-1: Supported BTS types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Table 2-1: Horizon II macro cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-5Table 2-2: Horizonmacro cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Table 2-3: Horizon II mini cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Table 2-4: Horizon II micro cabinet configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-9Table 2-5: TRX hardware and software configuration mismatch . . . . . . . . . . . . . . . . . 2-12Table 2-6: EDGE capability of BBH and/or BCCH configured . . . . . . . . . . . . . . . . . . 2-13Table 3-1: Timeslot assignment in 2:1 multiplexing mode . . . . . . . . . . . . . . . . . . . . 3-11Table 3-2: Timeslot assignment in 4:1 multiplexing mode . . . . . . . . . . . . . . . . . . . . 3-12Table 3-3: Timeslot assignment on A0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Table 3-4: Timeslot assignment on A1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Table 3-5: Timeslot assignment on A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Table 3-6: Timeslot assignment on A3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

68P02909W13-A v


List of Tables

vi 68P02909W13-A


AboutThisManual

RSR10 BTS Equipment Planning Guide■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

What is covered in this manual?

This document covers the BTS architecture overview and BTS planning for the RSR10 FeatureFR33950, FR33657, FR33602, FR33601, FR33658, and FR33951. This specification documentprovides clear and understandable BTS planning. BSC planning and PCU planning is out ofscope of this document.

68P02909W13-A 1


Revision history

Revision history■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Version information

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

Issue Date of issue Remarks

A Dec 2008 Initial release

Resolution of Service Requests

The following Service Requests are resolved in this document:

Service Request CMBPNumber Remarks

NA NA

Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document:

CN Date CN Number Title

NA NA NA

2 68P02909W13-A


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 allpersonnel engaged in such activities be properly trained by Motorola.

Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss orreduction 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 byMotorola. They can be used to supplement and enhance the knowledge gained through suchtraining.

NOTEIf this document was obtained when attending a Motorola training course, it is notupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then Motorola automatically supplies corrections and posts on the Motorolacustomer 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 arenot numbered, but are individually named at the top of each page, and are listed in the table ofcontents.

68P02909W13-A 3


Text conventions

Text conventions

The following conventions are used in the Motorola documents to represent keyboard inputtext, 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 orCTRL+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.

4 68P02909W13-A


Contacting Motorola

Contacting Motorola■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola appreciates feedback from the users of our documents.

24–hour support

If you have problems regarding the operation of your equipment, contact the Customer NetworkResolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listedat https://mynetworksupport.motorola.com. Select Customer Network Resolution Centercontact information. Alternatively if you do not have access to CNRC or the internet, contactthe Local Motorola Office.

Questions and comments

Send questions and comments regarding user documentation to the email address:[email protected].

Errors

To report a documentation error, call the CNRC (Customer Network Resolution Center) andprovide 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 5


Security advice

Security advice■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola systems and equipment provide security parameters that the operator configuresbased on their particular operating environment. Motorola recommends setting and usingthese parameters following industry recognized security practices. Consider protecting theconfidentiality, integrity, and availability of information and assets. Assets include the abilityto communicate, information about the nature of the communications, and information aboutthe parties involved.

In certain instances, Motorola makes specific recommendations regarding security practices.The implementation of these recommendations and final responsibility for the security of thesystem lies with the operator of the system.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information, from the menu located to the left of theLogin box. Alternatively if you do not have access to CNRC or the internet, contact the LocalMotorola Office.

6 68P02909W13-A


Warnings, cautions, and notes

Warnings, cautions, and notes■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following describes how warnings and cautions are used in this document and in alldocuments of this Motorola document set.

Warnings

Warnings precede instructions that contain potentially hazardous situations. Warnings areused to alert the reader to possible hazards that could cause loss of life or physical injury. Awarning has the following format:

WARNINGWarning 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 presentsno danger to personnel. A caution has the following format:

CAUTIONCaution 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 additionalinformation to help the reader understand a topic or concept. A note has the following format:

NOTENote text.

68P02909W13-A 7


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 InternationalElectrotechnical Commission (IEC) safety standards.

NOTERefer 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 Exposureto Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• Council recommendation of 12 July 1999 on the limitation of exposure of the generalpublic to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective nationalregulations.

• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 onthe minimum health and safety requirements regarding the exposure of workers to therisks arising from physical agents (electromagnetic fields) (18th individual Directive withinthe meaning of Article 16(1) of Directive 89/391/EEC).

8 68P02909W13-A


Caring for the environment

Caring for the environment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following information describes national or regional requirements for the disposal ofMotorola supplied equipment and for the approved disposal of surplus packaging.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information. Alternatively if you do not have accessto CNRC or the internet, contact the Local Motorola Office.

In EU countries

The following information is provided to enable regulatory compliance with the EuropeanUnion (EU) directives and any amendments to these directives when using Motorola equipmentin 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 conjunctionwith a recycling partner ensures that equipment is collected and recycled according to therequirements 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 recipient’sresponsibility to ensure that packaging materials are collected and recycled according to therequirements of EU environmental law.

In non-EU countries

In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordancewith national and regional regulations.

68P02909W13-A 9


CMM labeling and disclosure table

CMM labeling and disclosure table■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The People’s Republic of China requires that our products comply with China ManagementMethods (CMM) environmental regulations. (China Management Methods refers to theregulation 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 concentrationvalue for materials identified in the China Management Methods regulation.

• Logo 2 means that the product may contain substances in excess of the maximumconcentration value for materials identified in the China Management Methods regulation,and has an Environmental Friendly Use Period (EFUP) in years. The example shownuses 50 years.

Logo 1 Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxicand 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 theEIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certainfield-replaceable parts, such as battery modules, can have a different EFUP and are markedseparately.

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

10 68P02909W13-A


Motorola document set

Motorola document set■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Motorola document sets provide the information to operate, install, and maintain theMotorola equipment.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visitthe Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, orcontact your Motorola account representative.

Without internet access available, order hard-copy documents or CD-ROMs from your MotorolaLocal Office or Representative.

If Motorola changes the content of a document after the original printing date, Motorolapublishes 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 forgeneral 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 thenetwork is encrypted. In order to comply with the export and import requirements of particularcountries, this encryption occurs at different levels. The encryption may be individuallystandardized or may not be present at all in some parts of the network in which it is normallyimplemented. The document set covers encryption as if fully implemented. Limitations on theencryption included in the particular software being delivered, are covered in the Release Notesthat accompany the individual software release.

68P02909W13-A 11


Data encryption

12 68P02909W13-A


Chapter

1

BSS equipment overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02909W13-A 1-1


System architecture Chapter 1: BSS equipment overview

System architecture■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The architecture of the Motorola Base Station System (BSS) is versatile, and allows severalpossible configurations for a given system. The BSS is a combination of digital and RFequipment that communicates with the Mobile Switching Centre (MSC), Serving GPRS SupportNode (SGSN), the Operations & Maintenance Centre (OMC), and the Mobile Stations (MS), asshown in Figure 1-1.

Figure 1-1 BSS block diagram

BSC/PCU/XCDR

BTS BTS BTS

MS MSMS MS MS

…

…

Air interface

Abis interface

Gb interface

SGSN MSC OMC

A interface

BSS

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 canbe in-building or externally located Horizon II macro, Horizon II Mini, Horizon II Micro,Horizonmacro BTS cabinets or enclosures.

1-2 68P02909W13-A


RSR10 BTS Equipment Planning Guide 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 CTU2CTU2D

HorizonmacroHorizon II macro

Horizon II mini CTU2CTU2D

None

Horizon II micro CTU2CTU2D

None

NOTEThe Horizonmacro outdoor and indoor cabinets are powered at 110 V ac and thereforecannot 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


Abis BTS architecture overview Chapter 1: BSS equipment overview

Figure 1-2 Logic Abis BTS architecture diagram

ti-GSM-Hardware-Logic Abis_BTS Architecture-00002-ai-sw

BTS BSC/PCU

RSL (S igna ling)

Abis Inter face

OML(O&M)

TRAU (Data )

The OML is the communication link between the BTS and the BSC according to 12.21Manufacturer 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 betweenthe BSS and BTS per site.

The RSL is the communication link between the BTS and the BSC according to TS 48.058. TheRSL is used to carry traffic management-related messages. One RSL is needed per carrier.

1-4 68P02909W13-A


Chapter

2

BTS planning steps and rules■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02909W13-A 2-1


Introduction Chapter 2: BTS planning steps and rules

Introduction■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The planning steps and rules for the BTS, including Horizonmacro, Horizon II macro, Horizon IImini 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


RSR10 BTS Equipment Planning Guide 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 methodand antenna configuration provides sufficient output power. Alternatives include changingcombiner types or using more than one transmitting antenna. Duplexers may be used toreduce 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 wherethere are no equipment shelters. Include Macro or microcell where rooftop mounting ordistributed 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 offbetween 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 Macrocelland microcell BTS sites on page 2-4.

68P02909W13-A 2-3


Outline of planning steps Chapter 2: BTS planning steps and rules

Macrocell and microcell BTS sites

The following information for planning a macrocell or microcell BTS site is outlined in thelist 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 onpage 2-5.

• Determine the number of microcell enclosures required, refer to Microcell enclosures onpage 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 NIUfunctionality. 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 EquipmentPlanning manual.

2-4 68P02909W13-A


RSR10 BTS Equipment Planning Guide Macrocell cabinets

Macrocell cabinets■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Horizon II macro

The BSS supports the Horizon II macro site type. The major architecture and capacityrequirements 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 isintegrated into the BTP. From a functional standpoint, the Integrated NIU functions aresame as the standalone.

• The Horizon II macro site supports a single OML and multiple RSLs with 2:1 or 4:1multiplexing mode. The Horizon II macro supports equipping each RSL to one carrier, thatis, 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 densitymode, DCTU2 TRX type is CTU2/CTU2D configured in double density mode and supportedITS (Improve Timeslot Sharing) feature, CCTU2 TRX type is CTU2D configured in doubledensity mode and support the CTU2D Capacity feature. CCTU2 is only allowed to beconfigured 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 macroCabinet 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 IImacro supports the addition of up to 3 Extension cabinets. This means a Horizon II macrosite is restricted to a maximum of 4 cabinets.

NOTEIn FR33950/33951 feature scope, Horizon II mini and Horizon II microconfigured as expansion cabinets are not recommended as an officialconfiguration, only the cabinet combination in Table 2-1 is supported for HorizonII macro site type.

Table 2-1 Horizon II macro cabinet configuration


Horizon II macro CTU2CTU2D


• A minimum of one BTP (with integrated NIU functionality) is required in the master cabinetfor each Horizon II macro BTS site. Redundancy for the NIU functionality depends on aredundant BTP. It means if a redundant BTP is installed, the integrated NIU functionality isalso supported.

68P02909W13-A 2-5


Horizonmacro Chapter 2: BTS planning steps and rules

• The integrated NIU within the redundant BTP has connectivity to all the E1 links forthat site through the use of relays and switches. The redundant BTP can be switchedautomatically 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 capacityrequirements 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 adigital 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 digitalmodule shelf can interface to two E1 links and the fourth NIU (or MSI) in a digital moduleshelf can interface to one E1 link. The maximum 4 NIU (or MSI) boards can supportmaximum 6 E1 ports.

• The Horizonmacro site supports a single OML and multiple RSLs with 2:1 or 4:1multiplexing 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, SCTU2and DCTU2. CTU2D is not supported in Horizonmacro cabinet.

• The Horizonmacro site has a fixed Master Cabinet (Cabinet 0) of Horizonmacro CabinetType, and supports the addition of extension cabinets (Cabinet 1,2, and so on) withHorizonmacro, Horizon II macro, Horizon II mini, Horizon II micro. The Horizonmacrosupports the addition of up to 3 Extension cabinets. This means a Horizonmacro isrestricted to a maximum of 4 cabinets.

NOTEIn FR33950/33951 feature scope, Horizon II mini and Horizon II microconfigured as expansion cabinets are not recommended as an officialconfiguration, only the following cabinet combination in Table 2-2 is supportedin Horizonmacro site type.

2-6 68P02909W13-A


RSR10 BTS Equipment Planning Guide Horizonmacro

Table 2-2 Horizonmacro cabinet configuration


Horizonmacro CTUCTU2


• The master cabinet of Horizonmacro requires one BTP. For redundancy, add a standby BTPin the digital module shelf of the master cabinet. Redundancy for the NIU module dependson 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


Microcell enclosures Chapter 2: BTS planning steps and rules

Microcell enclosures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Horizon II mini

The BSS supports the Horizon II mini site type. Horizon II mini can satisfy all the currentHorizon II macro requirements but also add significant functionality that enables it to be classedas a Mini Macro BTS. The architecture is based on the Horizon II macro architecture andeffectively Horizon II mini behaves as a Horizon II macro cabinet.

So the major architecture and capacity requirements of Horizon II mini are like Horizon IImacro 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 integratedinto the BTP. From a functional standpoint, the Integrated NIU functions is same as thestandalone.

• The Horizon II mini site supports a single OML and multiple RSLs with 2:1 or 4:1multiplexing 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 CabinetType, and supports the addition of extension cabinets (Cabinet 1,2, and so on) withHorizonmacro, Horizon II macro, Horizon II mini and Horizon II micro. The Horizon II minisupports the addition of up to 3 Extension cabinets. This means a Horizon II mini siteis restricted to a maximum of 4 cabinets.

NOTEIn FR33950/33951 feature scope, Horizon II mini and Horizon II microconfigured as expansion cabinet are not recommended as an officialconfiguration, only the following cabinet combination in Table 2-3 is supportedin Horizon II mini site type.

Table 2-3 Horizon II mini cabinet configuration


Horizon II mini CTU2CTU2D

None

2-8 68P02909W13-A


RSR10 BTS Equipment Planning Guide Horizon II micro

Some software parameters have been added to limit Horizon II mini cabinets as a Mini BTS. TheHorizon II mini parameters allow the following:

• Equip only one BTP to a Horizon II mini master cabinet. Horizon II mini does not supporthardware redundancy.

• Equip a maximum of two physical TRX to a Horizon II mini cabinet. So the Horizon II minisite 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 cellsite, designed for indoor and outdoor microcellular applications and consists of a single smalltwo carrier BTS unit.

The architecture is based on the Horizon II macro architecture and effectively Horizon II microbehaves as if a Horizon II macro cabinet. So the major architecture and capacity requirementsof 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 isintegrated into the BTP. From a functional standpoint, the Integrated NIU functions aresame as the standalone NIU.

• The Horizon II micro site supports a single OML and multiple RSLs with 2:1 or 4:1multiplexing 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 microCabinet 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 IImicro support the addition of up to 3 Extension cabinets. This means a Horizon II microsite is restricted to a maximum of 4 cabinets.

NOTEIn FR33950/33951 feature scope, Horizon II mini and Horizon II microconfigured as expansion cabinets are not recommended as an officialconfiguration, only the following cabinet combination in Table 2-4 is supportedin Horizon II micro site type.

Table 2-4 Horizon II micro cabinet configuration


Horizon II micro CTU2CTU2D

None

68P02909W13-A 2-9


Horizon II micro Chapter 2: BTS planning steps and rules

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 notsupport hardware redundancy.

• Equip only one physical radio to a Horizon II micro cabinet. So the Horizon II micro sitewithout expansion cabinet only supports a maximum of 2 carriers.

2-10 68P02909W13-A


RSR10 BTS Equipment Planning Guide EGPRS configuration

EGPRS configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

EGPRS configuration limitations

EDGE is only supported in CTU2 and CTU2D hardware radio type. Following factors affectEDGE 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 orunrestricted, refer to Table 2-5.

• Determine if the TRX is configured for Baseband hopping and BCCH timeslot, refer toTable 2-6.

68P02909W13-A 2-11


EDGE capacity reporting Chapter 2: BTS planning steps and rules

Table 2-5 TRX hardware and software configuration mismatch

CTU SCTU2 DCTU2 CCTU2TRX

type/HWtype

Alarmindi-cation

GPRS/EDGEcapa-bility

Alarmindi-cation

GPRS/EDGEcapa-bility

Alarmindi-cation

GPRS/EDGE capability

Alarmindication

GPRS/EDGE capability

CTU OK CSGPRSCS1-4

MAJOR CSGPRSCS1-4

CRITICAL OOS CRITICAL OOS

CarrierA

CarrierB

ITSUnrest-ricted:CSGPRSCS1-4EDGEMCS1-9

CTU2 WARN-ING

CSGPRSCS1-4

OK CSGPRSCS1-4EDGEMCS1-9

OK

ITSRest-ricted:CSGPRSCS1-4

CSGPRSCS1-4

MAJOR CSGPRS CS1-4

CarrierA

CarrierB

CarrierA

CarrierB

ITSUnrest-ricted:CSGPRSCS1-4EDGEMCS1-9

CAPUnrest-ricted:CSGPRSCS1-4EDGEMCS1-9

CTU2D WARN-ING

CSGPRSCS1-4

OK CSGPRSCS1-4EDGEMCS1-9

OK

ITSRest-ricted:CSGPRSCS1-4

CSGPRSCS1-4

OK

CAPRest-ricted:revertstoDCTU2opera-tion.

CSGPRSCS1-4

2-12 68P02909W13-A


RSR10 BTS Equipment Planning Guide EDGE capacity reporting

NOTE

• If the warning alarm is raised (TRX hardware and software configurationmismatched), no action is taken, service is unaffected.

• If the major alarm is raised (TRX hardware and software configurationmismatched), TRX capability is affected and downgraded.

• If the critical alarm is raised (TRX hardware and software configurationmismatched), impacted TRXs are taken OOS.

Table 2-6 EDGE capability of BBH and/or BCCH configured

Carrier A Carrier BTRX Type

BBH BCCH BBH BCCH

CarrierA EDGECapability

CarrierB EDGECapability

NO N/A NULL NULL YES NULLSCTU2

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

DCTU2

YES N/A N/A N/A NO NO

NO N/A N/A N/A YES NOCCTU2

YES N/A N/A N/A NO NO

For example:

Example 1

If one CTU2D radio board is configured as CCTU2, and CAP feature is unrestricted, refer toTable 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 Bhave Non-EDGE capability.

Example 3

If one CTU2D radio board is configured as DCUT2 and carrier A is configured as BBH, and ITSfeature is unrestricted, refer to Table 2-5. Carrier A has EDGE capability and Carrier B isblank if Carrier A if EDGE traffic in Carrier A, so refer to Table 2-6. Carrier A has no EDGEcapability and Carrier B has no EDGE capability.

68P02909W13-A 2-13


Dynamic allocation of EDGE sub-timeslots Chapter 2: BTS planning steps and rules

Dynamic allocation of EDGE sub-timeslots

GPRS/EDGE backhaul allocations are made on a dynamic basis. Initially a 16 k resource isallocated to the PDCH, as the requirements for bandwidth change, the BSC may decide toincrease/decrease the backhaul allocations and will add/delete 16 k resources to the sameair timeslot.

• For GPRS, each PDCH is initially assigned a single 16 k, a single additional sub-timeslotcan be added for support of CS3/4.

• For EDGE, each PDCH is initially assigned a single 16 k, a maximum of three additionalsub-timeslot can be added for support of higher data rates.

The FlexAbis (PS) has superseded the VersaTRAU feature, which allowed a pool of DS0resources to be shared by multiple air timeslots. (Refer to Timeslots assignment on the Abisinterface on page 3-6.)

2-14 68P02909W13-A


Chapter

3

Timeslots on the Abis interface■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02909W13-A 3-1


Introduction Chapter 3: Timeslots on the Abis interface

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 startopology, 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 Abisinterface, the principles of semi-permanent connection and the principles of idle timeslotassignment.

• 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. Themultiplexing 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. Timeslotassignment 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


RSR10 BTS Equipment Planning Guide BTS topologies

BTS topologies■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction

The BSC provides flexible BTS topologies on the Abis interface. These topologies are startopology, chain topology, tree topology, and ring topology. Theses topologies can be mixedunder 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 topologydue to a simple network structure, convenient capacity expansion, and high reliability.

Figure 3-1 Star topology

ti-GSM-Hardware-Star topology-00003-ai-sw

BSC

BTS0

BTS1

BTS2

Chain topology

In the belt-shaped areas (such as highways) where the traffic volume is low, it is a waste oftransmission 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 transparentlytransmits the timeslots of the lower-level BTSs.

The chain topology has some disadvantages, such as inconvenient capacity expansion andreduced fault tolerance.

In the chain topology, a maximum seven level cascades BTS connection can be supported.

68P02909W13-A 3-3


Tree topology Chapter 3: Timeslots on the Abis interface

Figure 3-2 Chain topology

ti-GSM-Hardware-Chain topology-00004-ai-sw

BSC BTS0 BTS1 BTS2

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 eachchild BTS. The tree topology combines the features of star topology and chain topology. Its faulttolerance is lower than the star topology but higher than the chain topology. The structure ofthe tree topology is complicated. Therefore, the capacity expansion and maintenance of thenetwork is difficult.

In the tree topology, a maximum seven level cascades BTS connection can be supported.

Figure 3-3 Tree topology

ti-GSM-Hardware-Tree topology-00005-ai-sw

BSC BTS0

BTS1

BTS2

Ring topology

Ring topology is a special type of chain topology. All the BTSs connect with each other as anormal chain and the last-level BTS connects with the BSC to form a ring. If the communicationat a point in the ring is broken, the topology of the BTSs before the breakpoint remains the sameand 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 therobustness of the system.

In the ring topology, a maximum five level cascades BTS connection can be supported.

3-4 68P02909W13-A


RSR10 BTS Equipment Planning Guide Ring topology

Figure 3-4 shows the ring topology.

Figure 3-4 Ring topology

ti-GSM-Hardware- Ring topology-00006-ai-sw

BSC BTS0 BTS1 BTS2

68P02909W13-A 3-5


Timeslots assignment on the Abis interface Chapter 3: Timeslots 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 statisticmultiplexing mode or the BTS supports 16 kbit/s switching.

The statistic multiplexing means that n signaling channels use one 64 kbit/s timeslot. The nsignaling channels work in different time slices, that is, Time Division Multiplexing (TDM). Instatistic 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

ti-GSM-FlexAbis_algorithm -00007-ai-sw

Link 0 Link 2

PS Idle Pool 0

PS Idle Pool1

PS Id le Pool2 PS Id le Pool2PS Id le Pool2

PS Id le Pool1

Fixed0 Fixed1 Fixed2

B

S

C

B

T

S

Site2

B

T

S

Site0

B

T

S

Site1Link 1

• Link 0 in Abis interface is composed of Fixed 0 and PS Idle Pool 0/1/2. Link 1 in Abisinterface is composed of Fixed 1 and PS Idle Pool 1/2. Link 3 in Abis interface is composedof 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 isdynamically allocated from PS Idle Pool 0/1/2. TS dynamic allocation from PS Idle Pool canbe 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 canonly be allocated to PS slave link in Site1. TS in PS idle Pool 2 can only be allocated to PSslave link in Site 2. TS in PS idle Pool 0/1/2 cannot be shared between Site 0/1/2.

3-6 68P02909W13-A


RSR10 BTS Equipment Planning Guide Principles of timeslot assignment on the Abis interface

• TS number of PS Idle Pool in link 0/1/2 are equally allocated Abis TS resource. Forinstance, if PS Idle Pool 2 allocates 8 TS, then in link 0, link 1 and link 2 the TS number ofPS 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 64kbit/s timeslot and the relative positions of their corresponding sub-timeslot numbersmust 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 bedynamically 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, BSConly sends the message to inform the specific site and no need to inform other cascadedBTS.

Principles of timeslot assignment on the Abis interface

BSC supports FlexAbis (PS) algorithm which are offered as Fixed 16 k and Fixed 64 k switchesfrom LMT GUI.

FlexAbis (PS->Fixed 16 k) can be supported when BTS support 16 kbit/s switching. Theprinciples of timeslot assignment on the Abis interface are as follows:

• Each E1 port of the BTS manages sub-timeslots 0–255. Sub-timeslots 0–7 are used forsynchronization. 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 OMLis assigned on sub-timeslot 3 of timeslot 31.

• On one link, n:1 64 kbit/s statistic multiplexing and physical 16 kbit/s multiplexing cannotcoexist. The OMLs, RSLs, idle timeslots, monitoring timeslots, and TCHs are assignedbased on sub-timeslots.

• In physical 16 kbit/s multiplexing mode, the OMLs, RSLs, idle timeslots, monitoringtimeslots, 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/stimeslot.

Use one 64 kbit/s timeslot even if only one signaling channel or traffic channelis 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/stimeslot must stay in the same 64 kbit/s timeslot and the relative positions of theircorresponding sub-timeslot numbers must remain the same.

68P02909W13-A 3-7


Principles of timeslot assignment on the Abis interface Chapter 3: Timeslots on the Abis interface

The timeslots of different equipment groups in one BTS cannot be transmitted onthe 64 kbit/s bandwidth of the same E1.

Idle timeslots and the timeslots on TRXs cannot use the same 64 kbit/s bandwidthwith 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 timeslotson the Abis interface. The resources on the Abis interface are assigned to the followingobjects: 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 connectedto the BSC, this E1 port is selected preferentially during the timeslot assignment of theupper-level BTS.

Due to the switching fabric within the BTS only capable of switching at a rate of 64 kbps, theFlexAbis (PS->Fixed 16 k) solution allocates terrestrial ABIS resources at 16 kbps sub-timeslotand therefore restrictions are required on the LMT to operate within the boundaries imposedby 64 kbps switching limitations.

Besides the restrictions/principles that are valid for FlexAbis (PS->Fixed 64 k), there are morerestrictions/principles as follows:

• The BSC multiplexes RSLs which are allocated to logical TRXs located on the same physicalTRX 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 BSCassigns 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 cannotexceed 8.

• The total number of integrated E1 TSs allocated to a NON EDGE capable logical TRXcannot exceed 4.

3-8 68P02909W13-A


RSR10 BTS Equipment Planning Guide Principles of Idle Timeslot Assignment

Principles of Idle Timeslot Assignment

Idle timeslots carry the GPRS/EDGE services in the BSS. The principles of idle timeslotassignment are as follows:

• Idle timeslots are assigned based on BTSs. Each BTS can be assigned maximum 128idle timeslots.

• When assigning idle timeslots for a BTS, the user can manually assign timeslots on theAbis 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, aBTS has three idle timeslots. Two of them are deleted and then added again. In thiscase, the relative positions of the sub-timeslots of these three idle timeslots must remainunchanged.

Principles of Monitor Timeslot Assignment

Monitoring timeslot is a special semi-permanent connection. It is a semi-fixed transparent pathin the BSC. This path monitors the running status of the BSS. This transparent path connectsthe 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


BTS multiplexing mode Chapter 3: Timeslots on the Abis interface

BTS multiplexing mode■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction

The BTS multiplexing in the BSC refers to the multiplexing of the LAPD signaling on the E1timeslots of the Abis interface. The BSC offers two 64 kbit/s statistic multiplexing modes 2:1and 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 interfaceboard of BSC. The BTS multiplexing mode is only used for signaling link (RSL or OML), anddoes 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 onthe Abis interface. BSC supports multiple BTS multiplexing modes. Because of the transparenttransmission relation between cascaded BTSs, one E1 supports multiple multiplexing modes, asshown in Figure 3-6.

Figure 3-6 Multiple multiplexing modes

ti-GSM-Hardware-Multiple multiplexing_modes-00008-ai-sw

BSC

BTS0 BTS1

(2:1)

BTS3

(4:1)

BTS2

(4:1)

BTSn

(n:1)

A0 A3

A2

(2:1)

A1

As shown in Figure 3-6, the four E1s are A0, A1, A2, and A3. Assume that the multiplexingmodes of BTS 0, BTS 1, BTS 2, and BTS 3 are 2:1, 2:1, 4:1, and 4:1. Then two multiplexingmodes exist on the BSC. The multiplexing mode of each E1 on the link where the BTS is locatedis 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


RSR10 BTS Equipment Planning Guide 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 followingconditions:

• 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/stimeslot 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 thetimeslots on the T00C0 and T00C1. Therefore, T00C0 and T00C1 are not listed in thefollowing tables.

2:1 Multiplexing mode

Assume that BTS 0 is configured with a cell, the cell is configured with four TRXs, the channelsin the cell use default settings, and the multiplexing mode is 2:1. Table 3-1 lists the timeslotassignment 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

0 Synchronization Synchronization Synchronization Synchronization

1 T00C2 T00C3 T00C4 T00C5

2 T00C6 T00C7 * *

3 RSL01+RSL02

4 T01C0 T01C1 T01C2 T01C3

5 T01C4 T01C5 T01C6 T01C7

6 T02C0 T02C1 T02C2 T02C3

7 T02C4 T02C5 T02C6 T02C7

8 RSL03

9 T03C0 T03C1 T03C2 T03C3

10 T03C4 T03C5 T03C6 T03C7

11

...

31 OML0+RSL00

68P02909W13-A 3-11


4:1 Multiplexing mode Chapter 3: Timeslots on the Abis interface

NOTESub-timeslot 4 to 7 of TS2 cannot be shared with other TRX.

4:1 Multiplexing mode

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

Table 3-2 Timeslot assignment in 4:1 multiplexing mode


0 and 1 2 and 3 4 and 5 6 and 7


1 T00C2 T00C3 T00C4 T00C5

2 T00C6 T00C7 * *

3 T01C0 T01C1 T01C2 T01C3

4 T01C4 T01C5 T01C6 T01C7

5 T02C0 T02C1 T02C2 T02C3

6 T02C4 T02C5 T02C6 T02C7

7 RSL03

8 T03C0 T03C1 T03C2 T03C3

9 T03C4 T03C5 T03C6 T03C7

10

...

31 OML0+RSL00+RSL01+RSL02


Timeslot assignment in tree topology

The timeslot assignment on the Abis interface in the tree topology is more complicated. Themultiplexing modes of BTS 0, BTS 1, BTS 2, and BTS 3 are 2:1, 2:1, 4:1, and 4:1. Each BTSis configured with one cell, the cell is configured with two carriers, and the channels in thecell use default settings. BTS 0 is the parent node. Table 3-3 to Table 3-6 shows the timeslotassignment on E1s (A0–A3) of BTSs.

3-12 68P02909W13-A


RSR10 BTS Equipment Planning Guide Timeslot assignment in tree topology

NOTEThe timeslot assignment of each multiplexing mode is based on the followingconditions:

• Flexible Abis Mode is FlexAbis (PS->Fixed 64 k)

• The speech rate (Full Rate) is 16 kbit/s. Four channels of speech occupy one 64kbit/s timeslot on the Abis interface.

• For the TRX00, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is theSDCCH.

• The BCCH and the SDCCH use the RSL, that is, the timeslots on the RSL containthe timeslots on the T00C0 and T00C1. Therefore, T00C0 and T00C1 are notlisted in the following tables.

• T00C2 to T00C7 and T01C0 to T01C7 are assigned for CS TS of BTS0. T10C2 toT10C7 and T11C0 to T11C7 are assigned for CS TS of BTS1. T20C2 to T20C7and T21C0 to T21C7 are assigned for the CS TS of BTS2. T30C2 to T30C7 andT31C0 to T31C7 are assigned for CS TS of BTS3.

• T00C0additional to T00C03additional are assigned for the PS idle TS Pool ofBTS0.T10C0additional to T10C03additional are assigned for the PS idle TS Pool ofBTS1.T20C0additional to T20C03additional are assigned for the PS idle TS Pool ofBTS2.T30C0additional to T30C03additional are assigned for the PS idle TS Poolof BTS3.

Table 3-3 Timeslot assignment on A0


0 and 1 2 and 3 4 and 5 6 and 7


1 T00C2 T00C3 T00C4 T00C5

2 T00C6 T00C7 * *

3 RSL01

4 T01C0 T01C1 T01C2 T01C3

5 T01C4 T01C5 T01C6 T01C7

6 OML1+RSL10

7 T10C2 T10C3 T10C4 T10C5

8 T10C6 T10C7 * *

9 RSL11

10 T11C0 T11C1 T11C2 T11C3

11 T11C4 T11C5 T11C6 T11C7

12 OML2+RSL20+RSL21

Continued

68P02909W13-A 3-13


Timeslot assignment in tree topology Chapter 3: Timeslots on the Abis interface

Table 3-3 Timeslot assignment on A0 (Continued)


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




...

31 OML0+RSL00



0 and 1 2 and 3 4 and 5 6 and 7


1 T10C2 T10C3 T10C4 T10C5

2 T10C6 T10C7 * *

3 RSL11

4 T11C0 T11C1 T11C2 T11C3

5 T11C4 T11C5 T11C6 T11C7

6 OML3+RSL30+RSL31

7 T30C2 T30C3 T30C4 T30C5

8 T30C6 T30C7 * *

9 T31C0 T31C1 T31C2 T31C3

10 T31C4 T31C5 T31C6 T31C7



...

31 OML1+RSL10

3-14 68P02909W13-A


RSR10 BTS Equipment Planning Guide Timeslot assignment in tree topology



0 and 1 2 and 3 4 and 5 6 and 7


1 T20C2 T20C3 T20C4 T20C5

2 T20C6 T20C7 * *

3 T21C0 T21C1 T21C2 T21C3

4 T21C4 T21C5 T21C6 T21C07


11

...

31 OML2+RSL20+RSL21



0 and 1 2 and 3 4 and 5 6 and 7


1 T30C2 T30C3 T30C4 T30C5

2 T30C6 T30C7 * *

3 T31C0 T31C1 T31C2 T31C3

4 T31C4 T31C5 T31C6 T31C7


...

31 OML3+RSL30+RSL31


68P02909W13-A 3-15


Manual timeslot assignment on the Abis interface Chapter 3: Timeslots 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, andmonitoring timeslots are added. By default, the timeslots are assigned automatically. User canalso manually assign timeslots on the Abis interface if required, also a site reset triggered toaffect 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 acascaded 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 timeslotcannot be manually assigned unless the object using the timeslot is deleted or movedto another timeslot.

• The multiplexing mode of assigned timeslots must be the same as the multiplexing mode ofthe BTS. For instance, if the BTS uses the 2:1 multiplexing mode, do not multiplex foursignaling links together.

• In the incoming E1 and outgoing E1 links of all the cascaded BTSs on a link, locate all theobjects multiplexed onto one 64 kbit/s timeslot in the same 64 kbit/s timeslot and all therelative positions of sub-timeslots must remain unchanged.

• When adding BTSs, cells, TRXs, idle timeslots, and monitoring timeslots, user can manuallyassign timeslots for new added objects.

• When user wants to change the assignment mode of the timeslots of an object from manualmode to auto mode, the assignment mode of the timeslots that are already assigned cannotbe changed. When user wants to change the assignment mode of the timeslots of anobject from auto mode to manual mode, the user has to release the timeslots that areautomatically assigned for the object.

• User can assign the timeslots on the Abis interface for the BTSs on only one link of atopology at a time.

3-16 68P02909W13-A


Chapter

4

RSL/OML/E1 dimensioning rules■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02909W13-A 4-1


RSL/OML dimensioning rules Chapter 4: RSL/OML/E1 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 isenabled in the site.

• Adopt 4:1 OML/RSL multiplexing mode if no half rate call (AMR half rate call or GSM halfrate call) is enabled in the site.

• Only one OML/RSL multiplexing mode is allowed in one BTS, mixture of differentmultiplexing mode is not allowed in one BTS.

4-2 68P02909W13-A


RSR10 BTS Equipment Planning Guide E1 interconnect dimensioning

E1 interconnect dimensioning■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Determine the number of E1 links required to connect to a BTS. If required, add redundantlinks. To determine the impact of different coding schemes on interconnect planning, use thefollowing equation:

NBSC−BTS = Roundup

{[(nEGPRS∗8) + (nCGPRS∗4) + (nGGPRS∗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 aninteger).

nEGPRS the number of carriers with EGPRS enabled.

nCGPRS the number of carriers with GPRS CS3 and CS4 enabled and GSMvoice only carriers where the half rate exception case applies.

nGGPRS the number of carriers with GPRS CS1 and CS2 enabled andGSM voice only carriers where the half rate exception case doesnot apply.

L 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 tocarry GPRS CS3 and CS4 service, 6 carriers are used to carry GPRS CS1 and CS2 and GSMvoice service, and AMR half rate call is enabled. So nEGPRS is 2, nCGPRS is 4, nGGPRS is 6, 32kbit/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 4-3


E1 interconnect dimensioning Chapter 4: RSL/OML/E1 dimensioning rules

4-4 68P02909W13-A


Chapter

5

Glossary■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02909W13-A 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


RSR10 BTS Equipment Planning Guide Glossary of terms

RSL Radio Signaling Link

TS Timeslot

VersaTRAU Versatile Transcoder Rate Adaptation Unit

XCDR Transcoder

XMUX Expansion Multiplexer

68P02909W13-A 5-3


Glossary of terms Chapter 5: Glossary

5-4 68P02909W13-A


Index

Index■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

A

Abis BTS overview . . . . . . . . . . . . . 1-3Abis BTS architecture overview. . . . . . 1-3BSS topologies . . . . . . . . . . . . . . 1-3

Abis BTS overview (contd.)Supported BTS types . . . . . . . . . . . 1-3

B

BTS multiplexing mode . . . . . . . . . . 3-102:1 multiplexing mode . . . . . . . . . 3-114:1 multiplexing mode . . . . . . . . . 3-12Introduction. . . . . . . . . . . . . . . 3-10Timeslot assignment in N:1 multiplexingmode . . . . . . . . . . . . . . . . . . 3-11Timeslot assignment in tree topology . . 3-12

BTS planning overview . . . . . . . . . . . 2-3Introduction. . . . . . . . . . . . . . . . 2-3

BTS planning overview (contd.)Outline of planning steps . . . . . . . . . 2-3Macrocell and microcell BTS sites . . . 2-4

BTS topologies . . . . . . . . . . . . . . . 3-3Chain topology . . . . . . . . . . . . . . 3-3Introduction. . . . . . . . . . . . . . . . 3-3Ring topology . . . . . . . . . . . . . . . 3-4Star topology . . . . . . . . . . . . . . . 3-3Tree topology . . . . . . . . . . . . . . . 3-4

E

E1 interconnect dimensioning . . . . . . . 4-3EGPRS configuration . . . . . . . . . . . 2-11Dynamic allocation of EDGE sub-timeslots . . . . . . . . . . . . . . . . 2-14

EGPRS configuration (contd.)EDGE capacity reporting . . . . . . . . 2-11EGPRS configuration limitations . . . . 2-11

G

Glossary of terms . . . . . . . . . . . . . . 5-2

I

Introduction. . . . . . . . . . . . . . . 2-2, 3-2

M

Macrocell cabinets . . . . . . . . . . . . . 2-5Horizon II macro . . . . . . . . . . . . . 2-5Horizonmacro. . . . . . . . . . . . . . . 2-6

Manual timeslot assignment on the Abisinterface . . . . . . . . . . . . . . . . . 3-16Introduction. . . . . . . . . . . . . . . 3-16

Microcell enclosures . . . . . . . . . . . . 2-8

68P02909W13-A IX-5


Index

Microcell enclosures (contd.)Horizon II micro . . . . . . . . . . . . . 2-9

Microcell enclosures (contd.)Horizon II mini . . . . . . . . . . . . . . 2-8

R

RSL/OML dimensioning rules . . . . . . . . 4-2

S

System architecture. . . . . . . . . . . . . 1-2System components . . . . . . . . . . . . 1-2

T

Timeslots assignment on the Abis inter-face . . . . . . . . . . . . . . . . . . . . . 3-6Introduction. . . . . . . . . . . . . . . . 3-6

Timeslots assignment on the Abis interface (contd.)Principles of timeslot assignment on the Abisinterface . . . . . . . . . . . . . . . . . 3-7

IX-6 68P02909W13-A


Documents

RSR10 BTS Equipment Planning Guide 68P02909W13-A