BSC6900 Configuration guide

BSC6900 GSM V900R011C00

Initial Configuration Guide Issue

07

Date

2010-09-15

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 07 (2010-09-15)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

BSC6900 GSM Initial Configuration Guide

About This Document

About This Document Purpose This document describes the initial configuration of BSC6900.

Product Version The following table lists the product version related to this document. Product Name

Product Version

BSC6900

V900R011C00

Intended Audience This document is intended for: l

Field engineers

l

Network operators

l

System engineers

Organization 1 Changes in BSC6900 GSM Initial Configuration Guide This chapter describes the changes in the BSC6900 GSM Initial Configuration Guide. 2 Introduction to Initial Configuration Initial configuration refers to the process of creating the script for the equipment to start to operate. 3 Data Preparation for Initial Configuration In the BSC6900 initial configuration, some data is obtained from the data sheets after negotiation with other network elements. The negotiated data includes the global data, equipment data, interface data, base station data, and cell data. Issue 07 (2010-09-15)


iii


About This Document

4 Initial Configuration Procedures This chapter describes the process of creating the script of BSC6900 initial configuration. 5 Typical Configuration Script The typical configuration scripts used in this document derive from the documents related to the BSC6900. The typical configuration scripts concern global data, equipment data, network interfaces, base stations, and cells. 6 Configuring the Global Information BSC6900This chapter describes how to configure the global information. The global data configuration provides a basis for all the other configurations, and is thus determined during network planning. After the BSC6900 global data configuration takes effect, do not modify it unless the network is planned again. 7 Configuring the Equipment Data This chapter provides the example script for configuring the equipment data for the BSC6900, including the system information and the data about the cabinet, subrack, and board. 8 Configuring the Interfaces This chapter describes how to configure the GSM interfaces, including the Ater, A, Gb, and Pb interfaces. 9 Configuring the BTS This chapter describes how to configure a GSM BTS and its cells for the BSC6900. The configuration enables the radio receive/transmit functionality of the BTS and meets the requirements of the radio coverage in the cells. The configuration also enables the BSC6900 to perform centralized control and management on the BTS and allocate radio resources for the BTS. 10 Configuration Reference Information This chapter describes the concepts, principles, rules, and conventions related to data configuration.

Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol

Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results.

iv


Issue 07 (2010-09-15)


About This Document

Symbol

Description Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.

General Conventions The general conventions that may be found in this document are defined as follows. Convention

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

Examples of information displayed on the screen are in Courier New.

Command Conventions The command conventions that may be found in this document are defined as follows. Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italics.

[]

Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... }

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[ x | y | ... ]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{ x | y | ... }*

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[ x | y | ... ]*

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

GUI Conventions The GUI conventions that may be found in this document are defined as follows. Issue 07 (2010-09-15)


v


About This Document

Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.

>

Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format

Description

Key

Press the key. For example, press Enter and press Tab.

Key 1+Key 2

Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently.

Key 1, Key 2

Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operations The mouse operations that may be found in this document are defined as follows.

vi

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

Press and hold the primary mouse button and move the pointer to a certain position.


Issue 07 (2010-09-15)


Contents

Contents About This Document...................................................................................................................iii 1 Changes in BSC6900 GSM Initial Configuration Guide....................................................1-1 2 Introduction to Initial Configuration.....................................................................................2-1 3 Data Preparation for Initial Configuration...........................................................................3-1 4 Initial Configuration Procedures............................................................................................4-1 5 Typical Configuration Script...................................................................................................5-1 6 Configuring the Global Information.....................................................................................6-1 6.1 Configuring the Basic Information.................................................................................................................6-2 6.2 Configuring the OPC and DPC.......................................................................................................................6-2 6.3 Configuring the M3UA Local and Destination Entities..................................................................................6-3

7 Configuring the Equipment Data...........................................................................................7-1 7.1 Configuring the System Information...............................................................................................................7-2 7.2 Configuring a Cabinet.....................................................................................................................................7-2 7.3 Configuring a Subrack....................................................................................................................................7-2 7.4 Configuring a Board........................................................................................................................................7-3 7.5 Configuring an EMU.......................................................................................................................................7-4 7.6 Configuring the Clocks...................................................................................................................................7-4 7.7 Configuring the Time......................................................................................................................................7-5

8 Configuring the Interfaces.......................................................................................................8-1 8.1 Configuring the Ater Interface........................................................................................................................8-2 8.2 Configuring the A Interface (over TDM)........................................................................................................8-3 8.3 Configuring the A Interface (over IP).............................................................................................................8-3 8.3.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over IP)...............................8-4 8.3.2 Configuring the Control Plane of the A Interface (over IP)...................................................................8-7 8.3.3 Configuring the Mapping Between Service Types and Transmission Resources..................................8-8 8.3.4 Configuring the User Plane of the A Interface (over IP).......................................................................8-8 8.4 Configuring the Gb Interface (over FR)..........................................................................................................8-9 8.5 Configuring the Gb Interface (over IP)...........................................................................................................8-9 8.6 Configuring the Pb Interface.........................................................................................................................8-10

9 Configuring the BTS..................................................................................................................9-1 Issue 07 (2010-09-15)


vii


Contents

9.1 Configuring Equipment Data..........................................................................................................................9-2 9.2 Configuring the Logical Data..........................................................................................................................9-4 9.3 Configuring the Transmission Data................................................................................................................9-5 9.3.1 TDM/HDLC...........................................................................................................................................9-5 9.3.2 IP over FE/GE........................................................................................................................................9-5 9.3.3 IP over E1...............................................................................................................................................9-7 9.4 Configuring the BTS Clock.............................................................................................................................9-8 9.5 Activating the BTS Configuration..................................................................................................................9-8 9.6 Optional Functions of BTS.............................................................................................................................9-9 9.6.1 Configuring the Neighboring Cell Relations.........................................................................................9-9 9.6.2 Configuring the BTS Timeslots.............................................................................................................9-9

10 Configuration Reference Information...............................................................................10-1 10.1 Data Configuration Principles for Equipment.............................................................................................10-2 10.1.1 Configuration Rules of the Cabinets..................................................................................................10-2 10.1.2 Configuration Rules of the Subracks.................................................................................................10-2 10.1.3 Configuration Rules of the Boards.....................................................................................................10-3 10.1.4 Configuration Rules of the Clock.......................................................................................................10-5 10.1.5 Introduction to Time Synchronization...............................................................................................10-6 10.2 Data Configuration Principles for Interfaces...............................................................................................10-6 10.2.1 Links on the A and Ater Interfaces....................................................................................................10-6 10.2.2 Timeslot Assignment on the Ater Interface.......................................................................................10-8 10.2.3 Configuration Rules of the Gb Interface Links..................................................................................10-9 10.3 Data Configuration Principles for Base Stations.......................................................................................10-12 10.3.1 Numbering Rules of BTS Components............................................................................................10-13 10.3.2 Configuration Rules of the BTS Boards..........................................................................................10-17 10.3.3 Configuration Rules of the TRX Send and Receive Modes.............................................................10-22 10.3.4 Configuration Rules of the BTS Clock Sources...............................................................................10-26 10.3.5 BTS Network Topologies.................................................................................................................10-28 10.3.6 TDM-Based Networking on the Abis Interface...............................................................................10-31 10.3.7 IP-Based Networking on the Abis Interface.....................................................................................10-32 10.3.8 Typical Configuration Scenarios of the Radio Layer ......................................................................10-34 10.3.9 Concepts of the BTS Multiplexing Mode........................................................................................10-34 10.3.10 Instances of BTS Multiplexing Modes...........................................................................................10-36 10.3.11 Principles of DFCU/DFCB Configuration.....................................................................................10-40 10.3.12 Configuration Rules of Upgrading Cabinets from Version 8.x to Version 9.0..............................10-41 10.3.13 Configuration Guidelines for Typical TRX Power........................................................................10-47 10.4 Data Configuration Guidelines for Specifications....................................................................................10-47 10.5 Data Configuration Principles for Numbering..........................................................................................10-49 10.5.1 BSC6900 Subrack Number..............................................................................................................10-50 10.5.2 Transmission Resource Mapping Record Index..............................................................................10-50 10.5.3 Activity Factor Table Index.............................................................................................................10-50 10.5.4 SCTP Link Number..........................................................................................................................10-51 viii


Issue 07 (2010-09-15)


Contents

10.5.5 Adjacent Node ID.............................................................................................................................10-51 10.5.6 MTP3/M3UA DSP Index.................................................................................................................10-51 10.5.7 Signaling Link Set Index..................................................................................................................10-51 10.5.8 MSC ID............................................................................................................................................10-52 10.5.9 Logical Cell ID.................................................................................................................................10-52 10.5.10 GSM Cell ID..................................................................................................................................10-53 10.5.11 NRI.................................................................................................................................................10-53 10.5.12 PLMN ID........................................................................................................................................10-53 10.5.13 LA Identifiers.................................................................................................................................10-54 10.5.14 RA Identifiers.................................................................................................................................10-54 10.5.15 PLMN Value Tag...........................................................................................................................10-55

Issue 07 (2010-09-15)


ix


Figures

Figures Figure 10-1 Links on the A and Ater interfaces (TCS configured locally) .......................................................10-7 Figure 10-2 Links on the A and Ater interfaces (TCS configured remotely) ...................................................10-8 Figure 10-3 Logical connections at the NS and BSSGP layers.......................................................................10-12 Figure 10-4 Star topology.................................................................................................................................10-28 Figure 10-5 Chain topology.............................................................................................................................10-29 Figure 10-6 Bypass function of the BTS..........................................................................................................10-30 Figure 10-7 Tree topology................................................................................................................................10-30 Figure 10-8 Ring topology...............................................................................................................................10-31 Figure 10-9 TDM-based networking on the Abis interface.............................................................................10-32 Figure 10-10 IP over E1 Networking...............................................................................................................10-32 Figure 10-11 IP over Ethernet networking (layer 2)........................................................................................10-33 Figure 10-12 IP over Ethernet networking (layer 3)........................................................................................10-33 Figure 10-13 Components of the PLMN ID....................................................................................................10-53 Figure 10-14 Components of the LAI..............................................................................................................10-54 Figure 10-15 Components of the RAI..............................................................................................................10-54 Figure 10-16 Example of planning the value ranges of PLMN value tags......................................................10-55

Issue 07 (2010-09-15)


xi


Tables

Tables Table 10-1 Board classification..........................................................................................................................10-3 Table 10-2 Functions of boards..........................................................................................................................10-4 Table 10-3 Links on the A and Ater interfaces..................................................................................................10-7 Table 10-4 Bandwidth of OM timeslots and signaling timeslots on the Ater interface.....................................10-8 Table 10-5 Description of the configuration parameters..................................................................................10-10 Table 10-6 Numbering rules of cabinets..........................................................................................................10-14 Table 10-7 Cabinet selection............................................................................................................................10-14 Table 10-8 Numbering rules of subracks.........................................................................................................10-15 Table 10-9 Numbering rules of slots................................................................................................................10-16 Table 10-10 Numbering rules of the non-SingleRAN BTS components.........................................................10-17 Table 10-11 Configuration rules of the BTS3900 boards................................................................................10-17 Table 10-12 Configuration rules of the DBS3900 boards................................................................................10-18 Table 10-13 Configuration rules of the BTS3900A boards.............................................................................10-19 Table 10-14 Configuration rules of the BTS3900B boards..............................................................................10-19 Table 10-15 Configuration rules of the BTS3900E boards..............................................................................10-20 Table 10-16 Configuration rules of the BTS3012 boards................................................................................10-20 Table 10-17 Configuration rules of the DBS3900 boards................................................................................10-20 Table 10-18 Configuration rules of the BTS3900 boards................................................................................10-21 Table 10-19 Configuration rules of the BTS3900A boards.............................................................................10-22 Table 10-20 Configuration rules of the TRX send and receive modes............................................................10-23 Table 10-21 Configuration rules of the BTS clock sources.............................................................................10-27 Table 10-22 Timeslot assignment in 1:1 multiplexing mode...........................................................................10-36 Table 10-23 Timeslot assignment in 2:1 multiplexing mode...........................................................................10-37 Table 10-24 Timeslot assignment in 3:1 multiplexing mode...........................................................................10-38 Table 10-25 Timeslot assignment in 4:1 multiplexing mode...........................................................................10-39 Table 10-26 Instances of the physical 16 kbit/s multiplexing mode................................................................10-39 Table 10-27 Configuration rules of upgrading the BBU subrack....................................................................10-41 Table 10-28 Configuration rules of upgrading the RFU (not supporting the filler panel)...............................10-42 Table 10-29 Configuration rules of upgrading the RFU (supporting the filler panel).....................................10-42 Table 10-30 Configuration rules of upgrading the RRU..................................................................................10-43 Table 10-31 IP addresses of the monitoring boards.........................................................................................10-44 Table 10-32 Configuration rules for upgrading the monitoring boards...........................................................10-45 Table 10-33 BSC6900 specifications...............................................................................................................10-47 Issue 07 (2010-09-15)


xiii


1

1 Changes in BSC6900 GSM Initial Configuration Guide

Changes in BSC6900 GSM Initial Configuration Guide

This chapter describes the changes in the BSC6900 GSM Initial Configuration Guide.

07 (2010-09-15) This is the seventh commercial release. Compared with issue 06 (2010-05-31) of V900R011C00, this issue includes the following new topics: l

10.5 Data Configuration Principles for Numbering

Compared with issue 06 (2010-05-31) of V900R011C00, this issue does not incorporate any changes. Compared with issue 06 (2010-05-31) of V900R011C00, this issue does not exclude any topics.

06 (2010-05-31) This is the sixth commercial release. Compared with issue 05 (2010-03-25) of V900R011C00, this issue includes the following new topics: l

10.4 Data Configuration Guidelines for Specifications


05 (2010-03-25) This is the fifth commercial release. Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not include any new topics. Compared with issue 04 (2010-01-30) of V900R011C00, this issue incorporates the following changes. Issue 07 (2010-09-15)


1-1



Item

Change Description

Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/GOUc Board

The description of the link aggregation group is added.

Compared with issue 04 (2010-01-30) of V900R011C00, this issue does not exclude any topics.

04 (2010-01-30) This is the fourth commercial release. Compared with issue 03 (2009-12-05) of V900R011C00, this issue includes the following new topics: l

9.6.2 Configuring the BTS Timeslots

l

10.3.12 Configuration Rules of Upgrading Cabinets from Version 8.x to Version 9.0

Compared with issue 03 (2009-12-05) of V900R011C00, this issue incorporates the following changes. Item

Change Description

Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/GOUc Board

The procedure for configuring an IP route is modified.

Compared with issue 03 (2009-12-05) of V900R011C00, this issue does not exclude any topics.

03 (2009-12-05) This is the third commercial release. Compared with issue 02 (2009-10-30) of V900R011C00, this issue includes the following new topics: l

10.1 Data Configuration Principles for Equipment

l

10.2 Data Configuration Principles for Interfaces

l

10.3 Data Configuration Principles for Base Stations


02 (2009-10-30) This is the second commercial release. Compared with issue 01 (2009-07-30) of V900R011C00, this issue includes the following new topics: 1-2


Issue 07 (2010-09-15)



l

Typical Configuration Scripts

l

9.4 Configuring the BTS Clock

l

9.6.1 Configuring the Neighboring Cell Relations

l

10.3.1 Numbering Rules of BTS Components

l

10.3.2 Configuration Rules of the BTS Boards

l

10.3.3 Configuration Rules of the TRX Send and Receive Modes

l

10.3.4 Configuration Rules of the BTS Clock Sources

Compared with issue 01 (2009-07-30) of V900R011C00, this issue incorporates the following changes. Item

Change Description

Data Preparation for Initial Configuration

GSM data preparation for the initial configuration is updated.

Configuring a Subrack

The procedure for enabling the monitoring function of the power distribution box after the subrack is configured is added.

9.1 Configuring Equipment Data

The procedure for configuring the TDM over Packet switching relations of the MRRU/ MRFU board is added.

9.1 Configuring Equipment Data

The procedure for configuring BTS power sharing is added.

9.2 Configuring the Logical Data

The procedure for configuring a GSM cell by running the atom commands is added.

9.3.2 IP over FE/GE

The procedure for configuring the BTS Abis Mux function is added.

9.3.2 IP over FE/GE

The procedure for configuring the BFD detection function is added.

9.3.2 IP over FE/GE

The procedure for activating the IPPM detection function is added.

9.3.2 IP over FE/GE

The procedure for configuring the service VLAN mapping on the Abis interface is added.

Compared with issue 01 (2009-07-30) of V900R011C00, this issue excludes the following topics: l

Configuring a Connection Path Between Subracks

01 (2009-07-30) This is the first commercial release.

Issue 07 (2010-09-15)


1-3


2

2 Introduction to Initial Configuration

Introduction to Initial Configuration

Initial configuration refers to the process of creating the script for the equipment to start to operate. l

It is recommended that the command script be created on the BSC6900 LMT.

l

During commissioning, the script is imported to the BSC6900. For data modification after the BSC6900 starts operating, see the GBSS Reconfiguration Guide.

Issue 07 (2010-09-15)


2-1


3

3 Data Preparation for Initial Configuration

Data Preparation for Initial Configuration In the BSC6900 initial configuration, some data is obtained from the data sheets after negotiation with other network elements. The negotiated data includes the global data, equipment data, interface data, base station data, and cell data. For the data preparation for BSC6900 initial configuration, see GSM Data Preparation for the Initial Configuration.

Issue 07 (2010-09-15)


3-1


4 Initial Configuration Procedures

4

Initial Configuration Procedures

This chapter describes the process of creating the script of BSC6900 initial configuration.

Prerequisite l

The license has been obtained.

l

The data negotiated between the BSC6900 and other network elements is ready. For details, see Data Preparation for Initial Configuration.

Context For details of the typical configuration scripts, see Typical Configuration Scripts.

Procedure Step 1 Open the initial configuration tool. The BSC6900 LMT is recommended. Step 2 Create an initial configuration script. 1.

6 Configuring the Global Information.

2.

7 Configuring the Equipment Data.

3.

8 Configuring the Interfaces.

4.

9 Configuring the BTS.

Step 3 Save the initial configuration script. ----End

Postrequisite For details about loading the BSC6900 initial configuration data, see BSC6900 GSM Commissioning Guide.

Issue 07 (2010-09-15)


4-1


5 Typical Configuration Script

5

Typical Configuration Script

The typical configuration scripts used in this document derive from the documents related to the BSC6900. The typical configuration scripts concern global data, equipment data, network interfaces, base stations, and cells. For details of the BSC6900 typical configuration scripts, see the GSM Typical Configuration Scripts.

Issue 07 (2010-09-15)


5-1


6

6 Configuring the Global Information

Configuring the Global Information

About This Chapter BSC6900This chapter describes how to configure the global information. The global data configuration provides a basis for all the other configurations, and is thus determined during network planning. After the BSC6900 global data configuration takes effect, do not modify it unless the network is planned again. 1.

6.1 Configuring the Basic Information This section describes how to configure the basic data of the BSC6900. The configuration of the BSC6900 basic data is the prerequisite for the initial configuration.

2.

6.2 Configuring the OPC and DPC This section describes how to configure the OPC and DPC.

3.

6.3 Configuring the M3UA Local and Destination Entities This section describes how to configure the local and destination M3UA entities. You need to configure the M3UA entities when the IP-based networking is used.

Issue 07 (2010-09-15)


6-1



6.1 Configuring the Basic Information This section describes how to configure the basic data of the BSC6900. The configuration of the BSC6900 basic data is the prerequisite for the initial configuration.

Prerequisite l

All the subracks are switched to the ineffective mode by running the SET CFGDATAINEFFECTIVE command.

l

The basic data is not configured.

Procedure Step 1 Run the SET BSCBASIC command to set the basic GSM data. Step 2 Run the ADD GCNOPERATOR command to add a primary GSM operator. Set Operator Type to PRIM(Primary Operator). Step 3 Optional: To add more secondary GSM operators, run the ADD GCNOPERATOR command repeatedly. Set Operator Type to SEC(Secondary Operator). Step 4 Optional: Run the LST GLOBALROUTESWcommand to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route management switch to OFF. ----End

6.2 Configuring the OPC and DPC This section describes how to configure the OPC and DPC.

Prerequisite The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.

Context l

The network ID and the signaling point code must be planned in the SS7 network.

l

When you configure a DPC, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the policy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0.

Procedure Step 1 Run the ADD OPC command to add an OPC. Step 2 Run the ADD N7DPC command to add a DPC. To add more DPCs, run this command repeatedly. ----End 6-2


Issue 07 (2010-09-15)



6.3 Configuring the M3UA Local and Destination Entities This section describes how to configure the local and destination M3UA entities. You need to configure the M3UA entities when the IP-based networking is used.

Prerequisite The OPC and DPC are configured. For details, see Configuring the OPC and DPC.

Procedure Step 1 Run the ADD M3LE command to add an M3UA local entity. Step 2 Run the ADD M3DE command to add an M3UA destination entity. ----End

Issue 07 (2010-09-15)


6-3


7

7 Configuring the Equipment Data

Configuring the Equipment Data

About This Chapter This chapter provides the example script for configuring the equipment data for the BSC6900, including the system information and the data about the cabinet, subrack, and board.

Context Familiarize yourself with 10.1 Data Configuration Principles for Equipment before performing the operations described in this chapter. 1.

7.1 Configuring the System Information This section describes how to configure the system information of the BSC6900.

2.

7.2 Configuring a Cabinet This section describes how to configure a cabinet for the BSC6900. You need to configure the cabinet based on the requirements specified in the actual network planning.

3.

7.3 Configuring a Subrack This section describes how to configure a subrack for the BSC6900. You need to configure the subrack based on the requirements specified in the actual network planning.

4.

7.4 Configuring a Board This section describes how to configure a board for the BSC6900. You need to configure the board based on the requirements specified in the actual network planning.

5.

7.5 Configuring an EMU This section describes how to configure an EMU. An EMU is required for the BSC6900 to collect the Boolean value, analog value, and alarm threshold information.

6.

7.6 Configuring the Clocks This section describes how to configure the BSC6900 clocks. You need to configure the clock source of the interface board, clock source of the system, and working mode of the system clock source.

7.

7.7 Configuring the Time This section describes how to configure the time of the BSC6900. You need to set the time zone, daylight saving time, and (Simple Network Time Protocol) SNTP synchronization server.

Issue 07 (2010-09-15)


7-1



7.1 Configuring the System Information This section describes how to configure the system information of the BSC6900.

Prerequisite The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.

Context The system information consists of the system description, system ID, contact information of the vendor, system location, and system services.

Procedure Step 1 Optional: Run the SET SYS command to set the system information. ----End

7.2 Configuring a Cabinet This section describes how to configure a cabinet for the BSC6900. You need to configure the cabinet based on the requirements specified in the actual network planning.


Context The Main Processing Rack (MPR) is configured by default. It need not be added through the MML command.

Procedure Step 1 Run the ADD CAB command to add an Extended Processing Rack (EPR). Step 2 Optional: In BM/TC separated mode, run the ADD CAB command to add a TransCoder Rack (TCR). ----End

7.3 Configuring a Subrack This section describes how to configure a subrack for the BSC6900. You need to configure the subrack based on the requirements specified in the actual network planning.

Prerequisite The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data. 7-2


Issue 07 (2010-09-15)



Context l

The Main Processing Subrack (MPS) is configured by default. You need not add this subrack by running the MML command.

Procedure Step 1 To add an Extended Processing Subrack (EPS) for the BSC6900, run the ADD SUBRACK command. To add more EPSs, run this command repeatedly. Step 2 To add a TransCoder Subrack (TCS) for the BSC6900, run the ADD SUBRACK command. To add more TCSs, run this command repeatedly. Step 3 After a subrack is added, run the SET SCUPORT command to enable the corresponding port on the SCU board in the main subrack. ----End

Postrequisite To enable the monitoring function of the power distribution box, do as follows: 1.

Run the MOD SUBRACK command to enable the monitoring function of the power distribution box. The details are as follows: l Set Subrack No. to the number of the subrack connected to the power distribution box. l Set Connect power monitoring board to YES.

2.

Run the SET PWRPARA command to set the parameters of the power monitoring board.

3.

Run the SET PWRALMSW command to set the alarm switch on the power monitoring board.

7.4 Configuring a Board This section describes how to configure a board for the BSC6900. You need to configure the board based on the requirements specified in the actual network planning.

Context l

For the data to be negotiated and planned for configuring a board for the BSC6900, see Data Preparation for Initial Configuration.

l

For details of the board configuration rule, see Configuration Rules of the Boards.

Procedure Step 1 Run the ADD BRD command to add a board to the BSC6900. To add more boards, run this command repeatedly. Step 2 Optional: When the boards work in active/standby mode, run the SET MSP command to set the attributes of the Multiplex Section Protection (MSP). ----End Issue 07 (2010-09-15)


7-3



7.5 Configuring an EMU This section describes how to configure an EMU. An EMU is required for the BSC6900 to collect the Boolean value, analog value, and alarm threshold information.

Prerequisite The subrack for housing the EMU is already configured.

Context l

The EMU gathers Boolean values, analog values, and alarm threshold information and reports them to the LMT.

l

One cabinet can be configured with only one EMU.

Procedure Step 1 Run the ADD EMU command to add an EMU. ----End

7.6 Configuring the Clocks This section describes how to configure the BSC6900 clocks. You need to configure the clock source of the interface board, clock source of the system, and working mode of the system clock source.


Context You need to determine the clock source of the interface board, clock source of the system, and working mode of the system clock source through network planning. The line clock is the 8 kHz clock transmitted from the interface board to the GCUa board. Therefore, when the system uses the line clock, a clock source needs to be configured for the interface board. l

In BM/TC combined configuration mode, the A interface board of the MPS needs to be configured with a clock source. In addition, the link number for the clock source needs to be specified, and the backplane 8 kbit/s clock output switch needs to be turned on.

l

In BM/TC separated configuration mode, the interface boards in both the TCS and MPS need to be configured with clock sources. – In the case of the TCS, the A interface board of the TCS needs to be configured with a clock source. In addition, the link number for the clock source needs to be specified, and the backplane 8 kbit/s clock output switch needs to be turned on. If multiple TCSs are configured, the A interface board of each TCS needs to be configured with the line clock.

7-4


Issue 07 (2010-09-15)



– In the case of the MPS, the Ater interface board of the MPS needs to be configured with a clock source. In addition, the link number for the clock source needs to be specified, and the backplane 8 kbit/s clock output switch needs to be turned on. l

If the BSC6900 is configured with FR-based Gb interface boards and the SGSN and MSC use different clock sources, set Use SGSN clock source to Yes. Configure the clock source for the Gb interface boards. Set Port for LINE1 and Back-up port for LINE1 to the port number of the bearer channel (BC). NOTE

In the case of IP transmission, you need not configure clocks for the BSC6900.

Procedure Step 1 Run the SET CLK command to set the clock source of the interface board. Step 2 Run the ADD CLKSRC command to add the clock source of the system. l Clock source priority ranges from 1 to 4. The clock source of priority 0 is configured by default. Priority 0 is the lowest priority. The descending ranking of priorities is 1, 2, 3, and 4. l Clock source type should be set according to the mode of obtaining the clock signals. – If the clock signals are extracted from the CN by the interface board (for example, OIUa/ EIUa/PEUa/FG2a/GOUa) in the EPS and then sent to the GCUa board through the line clock signal cable, Clock source type should be set to BITS1-2MHZ or BITS2-2MHZ. – If the clock signals are extracted from the CN by the interface board in the MPS and then sent to the GCUa board through the backplane of the MPS, Clock source type should be set to LINE1_8KHZ or LINE2_8KHZ. – If the clock signals are provided by the external BITS, Clock source type should be set to BITS1-2MBPS, BITS2-2MBPS, BITS1-T1BPS, or BITS2-T1BPS. – If the clock signals are provided by the external 8 kHz clock, Clock source type should be set to 8KHZ. Step 3 Optional: Run the SET CLKMODE command to set the working mode of the system clock source. NOTE

It is recommended that System clock working mode be set to AUTO(Auto Handover) so that the system can switch to the clock source of the highest priority when the current clock source is unavailable.

----End

7.7 Configuring the Time This section describes how to configure the time of the BSC6900. You need to set the time zone, daylight saving time, and (Simple Network Time Protocol) SNTP synchronization server.


Issue 07 (2010-09-15)


7-5



Procedure Step 1 Run the SET TZ command to set the time zone and daylight saving time of the BSC6900. Step 2 Run the ADD SNTPSRVINFO command to add the information about the SNTP synchronization server. Step 3 Run the SET SNTPCLTPARA command to set the synchronization period of the SNTP client. ----End

7-6


Issue 07 (2010-09-15)


8 Configuring the Interfaces

8

Configuring the Interfaces

About This Chapter This chapter describes how to configure the GSM interfaces, including the Ater, A, Gb, and Pb interfaces. 8.1 Configuring the Ater Interface This section describes how to configure the TDM-based Ater interface to implement the communication between the MPS/EPS and the TCS when the BSC6900 is in BM/TC separated mode. 8.2 Configuring the A Interface (over TDM) This section describes how to configure the TDM-based A interface in BM/TC separated mode or BM/TC combined mode. 8.3 Configuring the A Interface (over IP) This section describes how to configure the IP-based A interface. 8.4 Configuring the Gb Interface (over FR) This section describes how to configure the FR-based Gb interface for the communication between the SGSN and the BSC6900 configured with the built-in PCU. You need to configure the Network Service Entity (NSE), Bearer Channel (BC), Network Service Virtual Connection (NSVC), and Point to Point BSSGP Virtual Connection (PTPBVC). 8.5 Configuring the Gb Interface (over IP) This section describes how to configure the IP-based Gb interface for communication between the SGSN and the BSC6900 configured with the built-in PCU. You need to configure the NSE, local NSVL, remote NSVL, and PTPBVC. 8.6 Configuring the Pb Interface This section describes how to configure the Pb interface for the communication between the PCU and the BSC6900 configured with the external PCU. You need to configure the E1 link and signaling link.

Issue 07 (2010-09-15)


8-1



8.1 Configuring the Ater Interface This section describes how to configure the TDM-based Ater interface to implement the communication between the MPS/EPS and the TCS when the BSC6900 is in BM/TC separated mode.

Prerequisite l

The subrack to be configured with an Ater connection path is configured.

l

The EIUa/OIUa board is configured in the subrack to be configured with an Ater connection path.

l

If the TCS is configured locally, the Ater connection path must be configured. If the TCS is configured remotely, the Ater connection path, Ater OML, and Ater signaling link must be configured.

l

If the TCS is configured remotely, the Ater connection path needs to be established only between the MPS/EPS and the main TCS.

l

The Ater connection path is established between EIUa boards or between OIUa boards. You can specify different ports to configure more than one Ater connection path between interface boards.

l

If the TCS is configured locally:

Context

Procedure 1.

Configure an Ater connection path. (1) Run the ADD ATERCONPATH command to add an Ater connection path between the MPS and the TCS. (2) In TC pool mode, run the ADD ATERE1T1 command to add an Ater connection path between the BSC6900 and the TC.

l

If the TCS is configured remotely: 1.

Configure an Ater connection path. (1) Run the ADD ATERCONPATH command to add an Ater connection path between the MPS and the main TCS. (2) In TC pool mode, run the ADD ATERE1T1 command to add an Ater connection path between the BSC6900 and the TC.

2.

Run the ADD ATEROML command to add an Ater OML between the MPS and the main TCS. NOTE

l At least four consecutive timeslots except timeslot 1 must be used for Ater OMLs. l It is recommended that a pair of active and standby Ater OMLs be configured. l If the BIOS version of the EIUa/OIUa board is earlier than 215, the active Ater OML must be configured on the Ater connection path that is carried on port 0. l In TC pool mode, the secondary BSC6900s do not need to be configured with Ater OMLs.

3.

8-2

Run the ADD ATERSL command to add an Ater signaling link between the MPS/ EPS and the TCS. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 07 (2010-09-15)


8 Configuring the Interfaces NOTE

l Timeslot 1 of the local main TCS and remote main TCS is reserved and cannot be configured. Timeslot 1 of other TCSs can be configured. l A maximum of 64 timeslots on each Ater interface board can be used for Ater signaling links.

----End

8.2 Configuring the A Interface (over TDM) This section describes how to configure the TDM-based A interface in BM/TC separated mode or BM/TC combined mode.

Prerequisite l

The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.

l

The OPC and DPC are configured. For details, see Configuring the OPC and DPC.

l

The EIUa/OIUa/XPUa board is configured. For details, see Configuring a Board.

Procedure Step 1 Run the ADD GCNNODE command to add a GSM CN node. Step 2 Run the ADD AE1T1 command to add an E1/T1 over the A interface. Step 3 Run the ADD MTP3LKS command to add an MTP3 signaling link set. Step 4 Run the ADD MTP3LNK command to add an MTP3 signaling link. Step 5 Run the ADD MTP3RT command to add an MTP3 route. ----End

8.3 Configuring the A Interface (over IP) This section describes how to configure the IP-based A interface.

Prerequisite A license for implementing IP transmission over the A interface is granted. 1.

8.3.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over IP) This section describes how to configure the physical layer and data link layer of the A interface on the BSC6900 in IP transmission mode. Before the configuration, specify the type of interface board according to network planning.

2.

8.3.2 Configuring the Control Plane of the A Interface (over IP) This section describes how to configure the control plane of the IP-based A interface on the BSC6900 side. You need to configure the SCTP link, M3UA link set, M3UA route, M3UA link, and adjacent node.

3.

8.3.3 Configuring the Mapping Between Service Types and Transmission Resources This section describes how to configure the mapping between the service types and transmission resources for the adjacent node. You can configure the TRM mapping table and activity factor table for users of different priorities.

Issue 07 (2010-09-15)


8-3



4.

8.3.4 Configuring the User Plane of the A Interface (over IP) This section describes how to configure the user plane of the A interface on the BSC6900 in IP transmission mode. You need to configure the IP path and IP route.

8.3.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over IP) This section describes how to configure the physical layer and data link layer of the A interface on the BSC6900 in IP transmission mode. Before the configuration, specify the type of interface board according to network planning.

Configuring the Physical Layer and Data Link Layer for the FG2a/GOUa/FG2c/ GOUc Board This section describes how to configure the physical layer and data link layer for the FG2a/FG2c/ GOUa/GOUc board, which is used as the interface board of the BSC6900. You need to set the Ethernet port attributes, add the standby Ethernet port, add the IP address of the Ethernet port, add the link aggregation group, add the link to the link aggregation group, add the IP address of the link aggregation group, and add the device IP address.

Prerequisite The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.

Procedure Step 1 Set the Ethernet port attributes. 1.

Run the LST ETHPORT command to list the attributes of the Ethernet port.

2.

Optional: If the planned data is inconsistent with the default data, run the SET ETHPORT command to set the attributes of the Ethernet port.

Step 2 Optional: Run the ADD ETHREDPORT command to configure Ethernet port backup. Step 3 Run the ADD DEVIP command to add the device IP address of the interface board. Set Device IP Address Type to LOGIC_IP. Step 4 Check whether the link aggregation function is required and then perform the corresponding step. If you select...

Then...

Link non-aggregation mode

Go to Step 5.

Link aggregation mode

Go to Step 6.

Step 5 In link non-aggregation mode, run the ADD ETHIP command to add the IP address of the Ethernet port. When multiple VLAN gateways are planned, repeat this step until all the IP addresses are added. Step 6 In link aggregation mode, do as follows: 1. 8-4

Run the ADD ETHTRK command to add a link aggregation group. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 07 (2010-09-15)


8 Configuring the Interfaces NOTE

You can run the DSP ETHTRK command to query the status of a link aggregation group.

2.

Run the ADD ETHTRKLNK command to add a link to the link aggregation group. To add more links to the link aggregation group, repeat this step until all desired links are added. NOTE

l You can run the DSP ETHTRKLNK command to query the status of a link in a link aggregation group and the related statistics. l The links in a link aggregation group can be carried by non-adjacent ports. l The port to which a link aggregation group is bound and a port on another board cannot work in active/standby mode or load sharing mode. l If a link in a link aggregation group becomes faulty, the system automatically removes this link. When this link becomes normal, the port carries this link automatically negotiates with the peer end. If the negotiation is successful, the link is automatically added to the link aggregation group.

3.

Run the ADD ETHTRKIP command to add the IP address of the link aggregation group. When multiple VLAN gateways are planned, repeat this step until all the IP addresses are added.

Step 7 Optional: In the case of layer 3 networking, if the BSC6900 and the NodeB are located on different network segments, run the ADD IPRT command to add an IP route. ----End

Configuring the Physical Layer and Data Link Layer for the PEUa Board This section describes how to configure the physical layer and data link layer for the PEUa board, which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes and device IP address, and configure the PPP link, MP link group, and MP link.


Context MP link group is also referred to as PPP link group. At least either a PPP link or an MP link group must be configured.

Procedure Step 1 Set the E1/T1 link attributes. 1.

Run the LST E1T1 command to list the attributes of an E1/T1 link.

2.

Optional: If the planned data is inconsistent with the default data, run the SET E1T1 command to set the attributes of the E1/T1 link.

Step 2 Run the ADD DEVIP command to add the device IP address of the interface board. Set Device IP Address Type to LOGIC_IP. Step 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform the corresponding step. Issue 07 (2010-09-15)


8-5



If the E1/T1 link carries a/an ...

Then...

PPP link

Go to Step 4.

MP link group

Go to Step 5.

Step 4 Configure a PPP link. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. The details are as follows: l Set Board type to PEUa. l Set Logic function type to IP. l It is recommended that Borrow DevIP be set to YES. Step 5 Add an MP link group. 1.

Run the ADD MPGRP command to add an MP link group. The details are as follows: l Set Board type to PEUa. l Set Logic function type to IP. l It is recommended that Borrow DevIP be set to YES.

2.

Run the ADD MPLNK command to add an MP link. To add more MP links, run this command repeatedly. Set Board type to PEUa.

----End

Configuring the Physical Layer and Data Link Layer for the POUc Board This section describes how to configure the physical layer and data link layer for the POUc board, which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes, optical port attributes, and channel attributes of a channelized optical port. In addition, configure the PPP link, MLPPP group, and MLPPP link.


Procedure Step 1 Run the SET E1T1 command to set the E1/T1 attributes. Step 2 Run the SET OPT command to set the attributes of the optical port. Step 3 Run the SET COPTLNK command to set the channel attributes of a channelized optical port. Step 4 Run the ADD DEVIP command to add the device IP address of the interface board. Step 5 Determine the type of link carried on the E1/T1 link (PPP link or MLPPP group) and perform the corresponding step. If the E1/T1 link carries a/an...

Then...

PPP link

Go to Step 6.

MLPPP group

Go to Step 7.

Step 6 Configure a PPP link. 8-6


Issue 07 (2010-09-15)



Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. Step 7 Configure an MLPPP group. 1.

Run the ADD MPGRP command to add an MLPPP group.

2.

Run the ADD MPLNK command to add an MLPPP link.

----End

8.3.2 Configuring the Control Plane of the A Interface (over IP) This section describes how to configure the control plane of the IP-based A interface on the BSC6900 side. You need to configure the SCTP link, M3UA link set, M3UA route, M3UA link, and adjacent node.

Prerequisite l

The M3UA local and destination entities are configured. For details, see Configuring the M3UA Local and Destination Entities.

l

The physical layer and data link layer of the A interface are configured. For details, see 8.3.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over IP).

Procedure Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run this command repeatedly. The details are as follows: l Set Signalling link model to CLIENT. l Set Application type to M3UA. Step 2 Run the ADD M3LKS command to add an M3UA link set. The details are as follows: l When Local entity type is set to M3UA_IPSP, Work mode of the M3UA link set must be set to M3UA_IPSP. l When Local entity type is set to M3UA_ASP, Work mode of the M3UA link set must be set to M3UA_IPSP if Destination entity type is set to M3UA_SP, or Work mode of the M3UA link set must be set to M3UA_ASP if the destination entity type is either of the other two values. NOTE

You can set Local entity type through the ADD M3LE command and set Destination entity type through the ADD M3DE command.

Step 3 Run the ADD M3RT command to add an M3UA route. Step 4 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, run this command repeatedly. Step 5 Run the ADD ADJNODE command to add an adjacent node. Set Adjacent Node Type to A. ----End

Issue 07 (2010-09-15)


8-7



8.3.3 Configuring the Mapping Between Service Types and Transmission Resources This section describes how to configure the mapping between the service types and transmission resources for the adjacent node. You can configure the TRM mapping table and activity factor table for users of different priorities.


Procedure Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table. Step 3 Run the ADD ADJMAP command to configure the TRM mapping table and activity factor table for users of different priorities. ----End

8.3.4 Configuring the User Plane of the A Interface (over IP) This section describes how to configure the user plane of the A interface on the BSC6900 in IP transmission mode. You need to configure the IP path and IP route.

Prerequisite The control plane of the IP-based A interface is configured. For details, see Configuring the Control Plane of the A Interface (over IP).

Procedure Step 1 Run the ADD IPPATH command to add an IP path. To add more IP paths, repeat this step until all desired IP paths are added. NOTE

l If the type of IP path is QoS, the IP path can match any path type in the TRMMAP table. l If the type of IP path is non-QoS, the type should be the one mapped to the service in the TRMMAP table. l You can run the SET PHBMAP command to set the priority of an IP path type. l The transmission bandwidth and reception bandwidth can be set according to the actual network planning.

Step 2 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode is used between the BSC6900 and the MSC/MGW. To add more IP routes, repeat this step until all desired IP routes are added. Step 3 Optional: Run the LST GLOBALROUTESWcommand to query the value of the global route management switch. If the global route management function is not required but the global route management switch is set to ON, run the SET GLOBALROUTESW command to set the global route management switch to OFF. 8-8


Issue 07 (2010-09-15)



Step 4 Run the SET TCTYPE command to set the TC DSP resource type. In this step, set The type of TC resource to ITC. ----End

8.4 Configuring the Gb Interface (over FR) This section describes how to configure the FR-based Gb interface for the communication between the SGSN and the BSC6900 configured with the built-in PCU. You need to configure the Network Service Entity (NSE), Bearer Channel (BC), Network Service Virtual Connection (NSVC), and Point to Point BSSGP Virtual Connection (PTPBVC).

Prerequisite l


l

The DPUd/XPUa/PEUa board is configured. For details, see Configuring a Board.

l

At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified by the NSEI.

l

In Gb over FR mode, a BC is a physical bearer channel, which is composed of a certain number of timeslots of the E1/T1.

l

An NSVC is carried by a BC and belongs to only one BC and only one NSE, whereas a BC or NSE can be configured with multiple NSVCs.

l

An NSVC maps to a PVC. When configuring an NSVC, specify its mapping PVC.

l

BSSGP is short for Base Station Subsystem GPRS Protocol.

l

A GPRS cell refers to a cell that is GPRS enabled.

Context

Procedure Step 1 Run the SET BSCPCUTYPE command to set the PCU type. Set PCU Type to INNER. Step 2 Run the ADD SGSNNODE command to add an SGSN node. Step 3 Run the ADD NSE command to add an NSE. Step 4 Run the ADD BC command to add a BC. Step 5 Run the ADD NSVC command to add an NSVC. Step 6 If the BSC6900 cell is configured and activated and the cell supports GPRS, run the ADD PTPBVC command to add a PTPBVC and bind the GPRS cell to its NSE. ----End

8.5 Configuring the Gb Interface (over IP) This section describes how to configure the IP-based Gb interface for communication between the SGSN and the BSC6900 configured with the built-in PCU. You need to configure the NSE, local NSVL, remote NSVL, and PTPBVC. Issue 07 (2010-09-15)


8-9



Prerequisite l

The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.

l

The DPUd/FG2a/XPUa board is configured. For details, see Configuring a Board.

l

A license for implementing IP transmission over the Gb interface is granted.

l

The interface board is configured with the device IP address or port IP address.

l

At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified by the NSEI.

l

BSSGP is short for Base Station Subsystem GPRS Protocol.

l

A GPRS cell indicates a cell that is GPRS capable.

Context

Procedure Step 1 Configure the physical layer and data link layer for the FG2a/FG2c/GOUa/GOUc board. Step 2 Run the SET BSCPCUTYPE command to set the PCU type as built-in. Step 3 Run the ADD SGSNNODE command to add an SGSN node. Step 4 Run the ADD NSE command to add an NSE. Step 5 Configuring an NSVL 1.

Run the ADD NSVLLOCAL command to add an NSVL on the BSC6900 side.

2.

Optional: If the NSE is in static configuration mode, run the ADD NSVLREMOTE command to add an NSVL on the SGSN side.

Step 6 If the cell is configured and the cell supports GPRS, run the ADD PTPBVC command to add a PTPBVC and bind the GPRS cell and its NSE. ----End

8.6 Configuring the Pb Interface This section describes how to configure the Pb interface for the communication between the PCU and the BSC6900 configured with the external PCU. You need to configure the E1 link and signaling link.

Prerequisite l


l

The EIUa/OIUa board is configured. For details, see Configuring a Board.

Procedure Step 1 Run the SET BSCPCUTYPE command to set the PCU type as external. Step 2 Run the ADD PCU command to add a PCU. Step 3 Run the ADD PBE1T1 command to add an E1/T1 over the Pb interface. 8-10


Issue 07 (2010-09-15)



Step 4 Run the ADD PBSL command to add a signaling link over the Pb interface. ----End

Issue 07 (2010-09-15)


8-11


9 Configuring the BTS

9

Configuring the BTS

About This Chapter This chapter describes how to configure a GSM BTS and its cells for the BSC6900. The configuration enables the radio receive/transmit functionality of the BTS and meets the requirements of the radio coverage in the cells. The configuration also enables the BSC6900 to perform centralized control and management on the BTS and allocate radio resources for the BTS. 1.

9.1 Configuring Equipment Data This section describes how to configure data for base station equipment. You need to configure data for the base station, cabinet, base station boards, TRX boards, and antenna boards.

2.

9.2 Configuring the Logical Data This section describes how to configure the logical data for the BTS. You need to configure cell data, binding relation between the cell and the BTS, binding relation between the logical TRX and the physical TRX board, channel attributes of the TRX, and device attributes of the TRX.

3.

9.3 Configuring the Transmission Data This section describes how to configure the transmission data for the BTS. The transmission mode can be TDM/HDLC, IP over FE/GE, or IP over E1.

4.

9.4 Configuring the BTS Clock This section describes how to configure a clock for a BTS. You need to configure the clock source for the BTS and configure the clock server for the BTS in IP transmission mode.

5.

9.5 Activating the BTS Configuration This section describes how to activate the configuration of a BTS. You need to check the data integrity of the BTS, activate the BTS configuration, and set the BTS environment alarms.

6.

9.6 Optional Functions of BTS In addition to the basic functions, the BTS provides some optional functions. You can configure the optional functions as required.

Issue 07 (2010-09-15)


9-1



9.1 Configuring Equipment Data This section describes how to configure data for base station equipment. You need to configure data for the base station, cabinet, base station boards, TRX boards, and antenna boards.

Prerequisite l

All types of base stations support TDM/HDLC/IP transmission mode.

l

The XPUa boards are configured. For details, see Configuring a Board.

l

There are idle ports on the interface board.

l

For the numbering rule of base station equipment, see 10.3.1 Numbering Rules of BTS Components.

l

For the configuration rule of base station boards, see 10.3.2 Configuration Rules of the BTS Boards.

l

For the configuration rule of the TRX sending and receiving mode, see 10.3.3 Configuration Rules of the TRX Send and Receive Modes.

Context

Procedure Step 1 Run the ADD BTS command to add a base station. NOTE

l In the case of the 3900 series base stations, Separate Mode must be set to SUPPORT(Support). In the case of the BTS3012, BTS3012II, and BTS3012AE, Separate Mode can be set to SUPPORT (Support) or UNSUPPORT(Not Support). In the case of the 3X series base stations, Separate Mode must be set to UNSUPPORT(Not Support). l In the case of the SingleRAN base stations, Is Support Normalized Data Configuration must be set to SUPPORT(Support). l BTS Name should not contain the following forbidden characters: , (comma), ; (semicolon), " (double quotation marks), ' (single quotation marks), =, %, \, +, &, and #.

Step 2 Run the ADD BTSCABINET command to add a cabinet to the base station. NOTE

l The boards in the common slots are automatically added according to the default setting. Antenna boards and TRX boards need to be manually added. l When Is Support SingleRAN Mode is set to SUPPORT(Support SRAN), the SingleRAN base stations can be configured.

Step 3 Run the ADD BTSBRD command to add boards to the base station. l When Board Type is set to PTU(PTU), this parameter can only be used to add IP interface boards to the double-transceiver BTS. l When the APMU and DTCU boards are configured in a remote monitoring subrack, the relevant RRUs must be specified. You can do so by running the SET BTSAPMUBP command and the SET BTSDHEUBP command respectively. Step 4 Add TRX boards to the base station. 9-2


Issue 07 (2010-09-15)



l 3X series and double-transceiver series base stations 1.

Run the ADD BTSTRXBRD command to add TRX boards to a base station of the 3X series or double-transceiver series. NOTE

l In the case of the BTS3012, BTS3012II, and BTS3012AE, the DTRU or QTRU board can be configured if Separate Mode is set to SUPPORT(Support). l The DTRU board enables two logical TRXs to be bound to one physical TRX board. The QTRU board enables six logical TRXs to be bound to one physical TRX board.

l 3900 series base stations 1.

Run the ADD BTSRXUCHAIN command to add an RXU chain or ring. NOTE

There is no need to add RXU boards or a RXU chain/ring for the 3900B.

2.

Run the ADD BTSRXUBRD command to add RXU boards. NOTE

l For the SingleRAN base stations, Cabinet No., Subrack No., and Subrack No. must be configured. l For the 3900 series base stations, the DRRU/GRRU/MRRU/DRFU/GRFU/MRFU board can be configured. The DRRU/GRRU/MRRU board can be configured only for the DBS3900 GSM and DBS3036. The DRFU/GRFU/MRFU board can be configured only for the BTS3900 GSM/BTS3900A GSM and BTS3036/BTS3036A. l The DRRU/DRFU board enables two logical TRXs to be bound to one physical TRX board. The MRRU/GRFU/MRFU/GRRU board enables eight logical TRXs to be bound to one physical TRX board. l If Is Configure Check threshold is set to NO(NO), run the ADD BTSBRDCAP command to set the bandwidth manually. l For base stations to V1 specifications: Forward Bandwidth of the GRRU board cannot exceed 12.5 Mbit/s. Forward Bandwidth of the MRRU board in the 900/850/1900 MHz frequency band cannot exceed 12.5 Mbit/s. Forward Bandwidth of the MRRU board in the 1800 MHz frequency band cannot exceed 15 Mbit/s. l For base stations to V2 specifications, Forward Bandwidth of the GRRU/MRRU board cannot exceed 20 Mbit/s.

3.

Run the SET BTSRXUBP command to set the sending receiving mode and working mode of the RXU board. NOTE

l If a site is configured with a TMA, you need to set the related TMA switch parameters. l The GRRU/GRFU board supports only the GSM(GSM) working mode. The MRRU/MRFU board supports the GSM(GSM), UMTS(UMTS), and GSM_AND_UMTS(GSM AND UMTS) working modes.

4.

If the working mode of the MRRU/MRFU is set to GSM_AND_UMTS(GSM AND UMTS), run the ADD BTSTOPCONFIG command to configure the TDM over Packet (TOP) switching relation of the MRRU/MRFU board. This facilitates common E1/T1 transmission between GSM and UMTS.

Step 5 Optional: If power sharing needs to be configured for the base station, run the SET GCELLCHMGAD command to set the advanced channel management parameters of the cell. In this step, set Multi-Density TRX Power Sharing to DYNAMIC(Dynamic power sharing). Step 6 Optional: Run the ADD BTSANTFEEDERBRD command to add antenna boards to the base station. Issue 07 (2010-09-15)


9-3


9 Configuring the BTS NOTE

The 3900 series base stations do not need to be configured with antenna boards.

----End

9.2 Configuring the Logical Data This section describes how to configure the logical data for the BTS. You need to configure cell data, binding relation between the cell and the BTS, binding relation between the logical TRX and the physical TRX board, channel attributes of the TRX, and device attributes of the TRX.

Prerequisite l

The data of the operator is configured. For details, see Configuring the Basic Data.

l

The OPC data is configured. For details, see Configuring the OPC and DPC.

l

The equipment data of the BTS is configured. For details, see 9.1 Configuring Equipment Data.

Procedure Step 1 Add the cell data by running the compound command or atom commands. l Adding the cell data quickly by running the compound command 1.

Run the ADD GCELLQUICKSETUP command to quickly add data to a GSM cell. NOTE

l Currently, GSM900 cells or DCS1800 cells support quick configuration. Co-BCCH cells, such as GSM900/DCS1800 co-BCCH cells do not support quick configuration. l The symbol "&" is used to separate different frequencies. For example, 22&33&44&55.

l Adding the cell data by running the atom commands 1.

Run the ADD GCELL command to add a cell.

2.

Run the ADD GCELLFREQ command to add frequencies to the cell.

3.

Run the ADD GCELLOSPMAP command to add the mapping between the cell and the originating signaling point.

4.

Run the ADD GTRX command to add a TRX.

5.

When the GPRS function is enabled, run the MML command SET GCELLGPRS to set the GPRS attributes of the cell.

Step 2 Run the ADD CELLBIND2BTS command to add the binding relation between the cell and the BTS. Step 3 Run the ADD TRXBIND2PHYBRD command to add the binding relation between the logical TRX and the physical TRX board. Step 4 Run the SET GTRXCHAN command to set the channel attributes of the TRX. Step 5 Run the SET GTRXDEV command to set the device attributes of the TRX. ----End 9-4


Issue 07 (2010-09-15)



9.3 Configuring the Transmission Data This section describes how to configure the transmission data for the BTS. The transmission mode can be TDM/HDLC, IP over FE/GE, or IP over E1. 9.3.1 TDM/HDLC This section describes how to configure the transmission data when the BTS is in TDM/HDLC transmission mode. 9.3.2 IP over FE/GE This section describes how to configure the transmission data when the BTS is in IP over FE/ GE transmission mode. 9.3.3 IP over E1 This section describes how to configure the transmission data when the BTS is in IP over E1 transmission mode.

9.3.1 TDM/HDLC This section describes how to configure the transmission data when the BTS is in TDM/HDLC transmission mode.

Prerequisite l


l

The logical data of the BTS is configured. For details, see 9.2 Configuring the Logical Data.

l

All types of BTSs support TDM/HDLC transmission.

l

The TDM/HDLC transmission networking, refer to 10.3.6 TDM-Based Networking on the Abis Interface.

Context

Procedure Step 1 Run the ADD BTSCONNECT command to add a connection between the BTS and the BSC6900, between BTSs (including the internal connection of a BTS), or between the BTS and the DXX. To add multiple BTS connections, run this command repeatedly. ----End

9.3.2 IP over FE/GE This section describes how to configure the transmission data when the BTS is in IP over FE/ GE transmission mode.

Prerequisite l

Issue 07 (2010-09-15)

The equipment data of the BTS is configured. For details, see 9.1 Configuring Equipment Data. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

9-5



l


l

The double-transceiver series and 3900 series base stations support IP over FE/GE transmission.

l

The IP over FE/GE transmission networking, refer to 10.3.7 IP-Based Networking on the Abis Interface.

Context

Procedure Step 1 Optional: If the planned data is inconsistent with the default data, run the SET ETHPORT command to set the attributes of the Ethernet port. Step 2 Optional: Run the ADD ETHREDPORT command to configure Ethernet port backup. Step 3 Optional: Run the ADD DEVIP command to add the device IP address of the Abis IP board. Step 4 Run the ADD ETHIP command to add the port IP address of the Abis IP board. Step 5 Optional: When the BSC6900 and the BTS are on different network segments, run the ADD IPRT command to add an IP route to the BSC6900 side. NOTE

If the global route management function is not required, run the SET GLOBALROUTESW command to set the global route management switch to OFF.

Step 6 Run the SET BTSIP command to set the IP address of the BTS. Step 7 Run the SET BTSETHPORT command to set the port attributes of the BTS. Step 8 Optional: When the BSC6900 and the BTS are on different network segments, run the ADD BTSIPRT command to add an IP route to the BTS side. Step 9 Run the ADD BTSESN command to add the equipment serial number (ESN) of the BTS. Step 10 Run the ADD ADJNODE command to add an adjacent node. Step 11 Run the ADD IPPATH command to add an IP path. To add more IP paths, repeat this step until all desired IP paths are added. Step 12 Optional: If the IP transmission efficiency over the Abis interface needs to be improved, you need to configure the Abis-MUX function. The operation steps are as follows: 1.

Run the ADD IPMUX command to add an IP MUX pipe. In this step, set IP MUX Type to ABISMUX.

2.

Run the ADD BTSABISMUXFLOW command to add the Abis MUX flow to the BTS.

Step 13 Optional: If the QoS of the IP transport network needs to be monitored, configure the Bidirectional Forwarding Detection (BFD) and IP Performance Monitor (IPPM) functions. The operation steps are as follows: 1.

Run the ADD BTSBFD command to add a BFD session on the BTS side.

2.

Run the ACT IPPM command to start the IPPM function on the BSC6900 side.

3.

Run the ACT BTSIPPM command to start the IPPM function on the BTS side.

Step 14 Optional: If the service VLAN mapping over the Abis interface needs to be configured, perform the following steps: 9-6


Issue 07 (2010-09-15)



1.

Run the ADD IPPATH and SET BSCABISPRIMAP command to configure the Abis priority mapping on the BSC6900 side.

2.

Run the SET BTSVLAN command to set the VLAN ID and VLAN priority on the BTS side.

----End

9.3.3 IP over E1 This section describes how to configure the transmission data when the BTS is in IP over E1 transmission mode.

Prerequisite l


l


l

Only the 3900 series base stations support IP over E1.

l

The IP over E1 transmission networking, refer to 10.3.7 IP-Based Networking on the Abis Interface.

Context

Procedure Step 1 Run the ADD BTSCONNECT command to add a connection between the BTS and the BSC6900, between BTSs (including the internal connection of a BTS), or between the BTS and the DXX. To add multiple BTS connections, run this command repeatedly. Step 2 Determine the type of link carried on the E1/T1 link (PPP link or MLPPP group) and perform the corresponding step. If the E1/T1 link carries a/an ...

Then...

PPP link

Go to Step 3.

MLPPP group

Go to Step 4.

Step 3 Configure a PPP link. 1.

Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly.

2.

Run the ADD BTSPPPLNK command to add a BTS PPP link. To add more PPP links, run this command repeatedly.

Step 4 Add an MLPPP group. 1.

Run the ADD MPGRP command to add an MLPPP group.

2.

Run the ADD MPLNK command to add an MLPPP link. To add more MLPPP links, run this command repeatedly.

3.

Run the ADD BTSMPGRP command to add a BTS MLPPP group.

Issue 07 (2010-09-15)


9-7



4.

Run the ADD BTSMPLNK command to add a BTS PPP link. To add more PPP links, run this command repeatedly.

Step 5 Run the ADD ADJNODE command to add an adjacent node. Step 6 Run the SET BTSIP command to set the IP address of the BTS. Step 7 Run the ADD BTSESN command to add the ESN of the BTS. Step 8 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly. ----End

9.4 Configuring the BTS Clock This section describes how to configure a clock for a BTS. You need to configure the clock source for the BTS and configure the clock server for the BTS in IP transmission mode.

Prerequisite The equipment data of the BTS is configured. For details, see 9.1 Configuring Equipment Data.

Context For the configuration rule of the BTS clock source, see 10.3.4 Configuration Rules of the BTS Clock Sources.

Procedure Step 1 Optional: If the BTS uses IP over FE/GE transmission, run the SET BTSIPCLKPARA command to configure the clock server for the BTS. Step 2 Optional: If the clock source type for the BTS needs to be set, run the SET BTSCLK command to configure the BTS clock source. ----End

9.5 Activating the BTS Configuration This section describes how to activate the configuration of a BTS. You need to check the data integrity of the BTS, activate the BTS configuration, and set the BTS environment alarms.

Prerequisite The BTS and its cells are already configured.

Procedure Step 1 Run the CHK BTS command to check the data integrity of a BTS. Step 2 Run the ACT BTS command to activate the configuration of a BTS. 9-8


Issue 07 (2010-09-15)



Step 3 Run the SET BTSENVALMPORT command to set the environment alarms of a BTS. ----End

9.6 Optional Functions of BTS In addition to the basic functions, the BTS provides some optional functions. You can configure the optional functions as required. 9.6.1 Configuring the Neighboring Cell Relations This section describes how to configure the neighboring cell relations between the cells in a BSC6900 or between the cells in different BSC6900s. To configure the neighboring cell relations, you need to configure the external 2G cell, external 3G cell, and neighboring cells for a cell to meet the handover requirement. 9.6.2 Configuring the BTS Timeslots In the network deployment or adjustment phase, you may need to configure the idle timeslots or monitoring timeslots of the BTS according to service requirements.

9.6.1 Configuring the Neighboring Cell Relations This section describes how to configure the neighboring cell relations between the cells in a BSC6900 or between the cells in different BSC6900s. To configure the neighboring cell relations, you need to configure the external 2G cell, external 3G cell, and neighboring cells for a cell to meet the handover requirement.

Context l

The cell on which an MS camps before the handover is called the originating cell. The cell on which the MS will camp after the handover is called the target cell.

l

The cells in the BSC6900 can be set to bidirectional neighboring cells or uni-directional neighboring cells.

l

An external cell, that is, a cell in another BSC6900, can be configured only as a unidirectional neighboring cell.

Procedure Step 1 Run the ADD GEXT2GCELL command to add a 2G external cell. Step 2 Run the ADD GEXT3GCELL command to add a 3G external cell. Step 3 Run the ADD G2GNCELL command to add a 2G neighboring cell for the specified originating cell. Step 4 Run the ADD G3GNCELL command to add a 3G neighboring cell for the specified originating cell. ----End

9.6.2 Configuring the BTS Timeslots In the network deployment or adjustment phase, you may need to configure the idle timeslots or monitoring timeslots of the BTS according to service requirements. Issue 07 (2010-09-15)


9-9



Prerequisite The data of the BTS is configured.

Context l

During network construction, the existing transmission links of the BTS can be used to obtain the required monitoring data. This meets the maintenance requirements of operators, monitors various data on the network, and reduces the transmission link costs. With regard to hardware deployment, a monitoring terminal needs to be installed on the BTS side, and a monitoring device needs to be installed on the BSC6900 side. In terms of software configuration, some of the BTS timeslots need to be used as monitoring timeslots to transmit monitoring data.

l

The idle timeslots of the BTS are used to carry GPRS service data. If the idle timeslots of the BTS do not meet the bandwidth requirement of GPRS traffic, additional idle timeslots can be configured to increase the bandwidth available for GPRS traffic.

l

Some of the allocated timeslots of a BTS can be disabled. This operation is applicable to scenarios where leased transmission links are used. For example, an operator leases only some timeslots on an E1 for traffic purposes.

l

Configuring the BTS monitoring timeslots

Procedure 1.

Run the ADD BTSMONITORTS command to add a monitoring timeslot at the BTS. NOTE

l During timeslot assignment, the transparent transmission rules must be met, that is, the subtimeslots have fixed locations inside a 64 kbit/s timeslot. For example, if sub-timeslot 2 is assigned as the monitoring timeslot of the local BTS, the monitoring timeslot of the upper-level BTS must also be located in sub-timeslot 2. In addition, the board where the BTS is connected to the BSC can be configured only in the BM subrack, and this board must be a TDM interface board or an HDLC interface board. l If a 64 kbit/s monitoring timeslot is configured, the number of its sub-timeslots starts from 0. If a 32 kbit/s monitoring timeslot is configured, the number of its sub-timeslots starts from 0 or 4. If a 16 kbit/s monitoring timeslot is configured, the number of its sub-timeslots starts from 0, 2, 4, or 6. If an 8 kbit/s timeslot is configured, the number of its sub-timeslots can be that of any sub-timeslot in a 64 kbit/s timeslot. l If an OIU board of the BSC is to be monitored, the numbers of the incoming timeslots of the BSC start from 2. l Timeslot 1 of the E1/T1 on the Ater interface of the main TCS is reserved by the system. Therefore, do not configure any monitoring timeslot, semi-permanent link, or SS7 signaling link on this timeslot. l If the BTS uses the physical 16 kbit/s multiplexing mode, the bandwidth of the monitoring timeslot must be 16 kbit/s or 64 kbit/s. l If a BTS or its upper-level BTS uses the HDLC transmission mode, the monitoring timeslot of this BTS must be 64 kbit/s, and the outgoing BTS port of the monitoring timeslot must be an idle port or be the outgoing BTS port of another monitoring timeslot.

l

Configuring the BTS idle timeslots 1.

Run the SET BTSIDLETS command to configure idle timeslots of the BTS. NOTE

Idle timeslots are configured on the basis of BTS cabinet groups. With respect to each cabinet group, no more than 128 idle timeslots can be configured at a time. With respect to each BTS, a maximum of 512 idle timeslots can be configured.

9-10


Issue 07 (2010-09-15)


l


Configuring the BTS forbidden timeslots 1.

Run the SET BTSFORBIDTS command to disable or enable the timeslots of a BTS.

----End

Issue 07 (2010-09-15)


9-11


10

10 Configuration Reference Information

Configuration Reference Information

About This Chapter This chapter describes the concepts, principles, rules, and conventions related to data configuration. 10.1 Data Configuration Principles for Equipment This section describes the configuration rules and reference information related to the BSC6900 equipment. 10.2 Data Configuration Principles for Interfaces This section describes the configuration rules and reference information related to the BSC6900 interfaces. 10.3 Data Configuration Principles for Base Stations This section describes the configuration rules and reference information related to a base station. 10.4 Data Configuration Guidelines for Specifications This document provides the specifications of the BSC6900. 10.5 Data Configuration Principles for Numbering This section describes the numbering rules and reference information related to the BSC6900.

Issue 07 (2010-09-15)


10-1



10.1 Data Configuration Principles for Equipment This section describes the configuration rules and reference information related to the BSC6900 equipment. 10.1.1 Configuration Rules of the Cabinets This section describes the configuration rules of the BSC6900 cabinets. 10.1.2 Configuration Rules of the Subracks This section describes the configuration rules and reference information related to the BSC6900 subracks. 10.1.3 Configuration Rules of the Boards This section describes the configuration rules and reference information related to the BSC6900 boards. 10.1.4 Configuration Rules of the Clock This section describes the configuration rules and reference information related to the BSC6900 clock. 10.1.5 Introduction to Time Synchronization The time synchronization function enables the time of the nodes of the GBSS system to be synchronized.

10.1.1 Configuration Rules of the Cabinets This section describes the configuration rules of the BSC6900 cabinets. The configuration rules of the BSC6900 cabinets are as follows: l

The cabinets consist of the Main Processing Rack (MPR), Extended Processing Rack (EPR), and TransCoder Rack (TCR).

l

The MPR is configured by default. You cannot add or remove this cabinet by running the MML command.

l

If a TCS is configured in the local cabinet, the remote TCR cannot be configured.

l

According to service requirements, one to three cabinets can be configured. The number of remote TCRs cannot exceed two.

10.1.2 Configuration Rules of the Subracks This section describes the configuration rules and reference information related to the BSC6900 subracks. The configuration rules of the BSC6900 subracks are as follows:

10-2

l

The Main Processing Subrack (MPS) is configured by default. You need not add this subrack by running the MML command.

l

Before adding a subrack, ensure that the cabinet to which the subrack is added exists, and that the MPS works properly.

l

Each subrack needs to be equipped with a fan box. The power distribution box can be configured as required. Generally, only one subrack in a cabinet can be connected to the monitoring board of the power distribution box. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 07 (2010-09-15)



l

The actual board type in a subrack must be consistent with the configured type. The subrack number of the EPS/TCS must be consistent with the setting of the DIP switch.

l

After a subrack is added, run MML command to enable the corresponding port on the SCU board in the main subrack.

l

The relation between Subrack No. and Cabinet No. is as follows: Cabinet No. equals the quotient of Subrack No. divided by three.

10.1.3 Configuration Rules of the Boards This section describes the configuration rules and reference information related to the BSC6900 boards.

Classification of Boards Table 10-1 provides the classification of the BSC6900 boards. Table 10-1 Board classification Board Class

Board Type

Logical Function Type

Interface board

PEUa

IP FR HDLC Abis_IP

EIUa/OIUa

Abis_TDM Ater_TDM A_TDM Pb_TDM

POUc

TDM IP

FG2a

IP GbIP

Data Processing Unit (DPU)

GOUa/GOUc/FG2c

IP

DPUa/DPUc/DPUf

GTC

DPUb

GTC GPCU

Signaling Processing Unit (XPU)

Issue 07 (2010-09-15)

DPUd

GPCU

XPUa/XPUb

GCP


RGCP 10-3



Board Class

Board Type

Logical Function Type MCP

TDM switching Network Unit (TNU)

TNUa

TDM_Switching

Operation and Maintenance Unit (OMU)

OMUa/OMUb

OAM

Service Aware Unit (SAU)

SAUa

SAU

Functions of Boards When being loaded with different software, the BSC6900 boards provide different functions, as described in Table 10-2. Table 10-2 Functions of boards

10-4


Description

OAM

Operation and maintenance management

TDM_Switching

TDM switching

GCP

All the subsystems are configured as CPU for Service (CPUS) subsystems, which are used to process the services in the control plane of the GSM BSC.

RGCP

Subsystem 0 is configured as the MPU subsystem, which is used to manage resources. All the other subsystems are configured as CPUS subsystems, which are used to process the services in the control plane of the GSM BSC.

MCP

Calculation of interference-based channel allocation (IBCA) data

GTC

GSM speech service processing

GPCU

GSM packet service processing

IP

IP interface processing

FR

FR interface processing

HDLC

HDLC interface processing

TDM

TDM interface processing

GbIP

GbIP interface processing

Abis_TDM

TDM-based Abis interface processing Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 07 (2010-09-15)




Description

Ater_TDM

TDM-based Ater interface processing

Pb_TDM

TDM-based Pb interface processing

A_TDM

TDM-based A interface processing

Abis_IP

IP-based Abis interface processing

SAU

Service aware unit

10.1.4 Configuration Rules of the Clock This section describes the configuration rules and reference information related to the BSC6900 clock. The configuration rules of the board clock are as follows: l

The interface boards in the EPS cannot provide 8 kHz clock output through the backplane.

l

Each channel of 8 kHz backplane clock has only one clock source. The clock output switch on multiple interface boards for the same channel of 8 kHz backplane clock cannot be turned on at the same time.

l

If both data and voice services are carried by the board, the clock source for the two types of services must be the same in the core network. Otherwise, the data or voice service may fail.

l

For the EIUa boards, the LINE1 clock is extracted from Port for LINE1, and the LINE2 clock is extracted from Port for LINE2. For other interface boards, both the LINE1 clock and LINE2 clock are extracted from Port for LINE.

l

If Use SGSN clock source is set to YES, the POUc board can be used only as a Gb interface board rather than an Abis, Ater, Pb, or A interface board.

The configuration rules of the system clock are as follows: l

Clock source priority ranges from 1 to 4. The clock source of priority 0 is configured by default. Priority 0 is the lowest priority. The descending ranking of priorities is 1, 2, 3, and 4.

l

Clock source type needs to be set according to the mode of obtaining the clock signals. – If the clock signals are extracted from the CN by the interface board (for example, OIUa/ EIUa/PEUa/FG2a/GOUa) in the EPS and then sent to the GCUa board through the line clock signal cable, Clock source type should be set to BITS1-2MHZ or BITS2-2MHZ. – If the clock signals are extracted from the CN clock by the interface board in the MPS and then sent to the GCUa board through the backplane of the MPS, Clock source type should be set to LINE1_8KHZ or LINE2_8KHZ. – If the clock signals are provided by the external BITS clock, Clock source type should be set to BITS1-2MBPS, BITS2-2MBPS, BITS1-T1BPS, or BITS2-T1BPS. – If the clock signals are provided by the external 8 kHz clock, Clock source type should be set to 8KHZ.

Issue 07 (2010-09-15)


10-5



10.1.5 Introduction to Time Synchronization The time synchronization function enables the time of the nodes of the GBSS system to be synchronized. Synchronization is critical for identifying faults. For example, if an E1 link between the BSC6900 and the base station is broken, time synchronization between the BSC6900 and the base station ensures that the same fault is reported to the M2000 by the BSC6900 and by the base station is at the same time point. The Simple Network Time Protocol (SNTP) is used to synchronize the time of the nodes of the GBSS system. SNTP serves the time synchronization between a server and multiple clients. Therefore, an SNTP server must be configured in the GBSS system. The SNTP server broadcasts time synchronization information to the SNTP clients. Either the BSC6900 or the M2000 functions as an SNTP server. You can configure an SNTP server by taking the field condition into consideration. SNTP works on the basis of the Greenwich Mean Time (GMT). Therefore, when setting the time at different nodes, you need to set the time zone where the node is located and decide whether to set the Daylight Saving Time (DST). If the DST is set, you need to configure the start time and end time of the DST and the time offset.

10.2 Data Configuration Principles for Interfaces This section describes the configuration rules and reference information related to the BSC6900 interfaces. 10.2.1 Links on the A and Ater Interfaces This section describes the configuration rules and reference information related to the A and Ater interface links. 10.2.2 Timeslot Assignment on the Ater Interface This section describes the timeslot assignment principles of the Ater OMLs and signaling links and the dynamic assignment principles of traffic timeslots. 10.2.3 Configuration Rules of the Gb Interface Links This section describes the configuration rules and reference information related to the Gb interface links.

10.2.1 Links on the A and Ater Interfaces This section describes the configuration rules and reference information related to the A and Ater interface links. In BM/TC separated mode, the TCS can be configured locally or remotely. Accordingly, links need to be configured on the A and Ater interfaces. Table 10-3 lists the links that need to be configured on the A and Ater interfaces.

10-6


Issue 07 (2010-09-15)



Table 10-3 Links on the A and Ater interfaces Interface

TCS Configured Locally

TCS Configured Remotely

A interface

SS7 link

SS7 link

Ater interface

-

Ater OML and Ater signaling link

Figure 10-1 shows the links that need to be configured on the A and Ater interfaces when the TCS is configured locally. The MPS communicates with the main TCS through the SCU boards to transmit SS7 signaling, BSC6900 internal signaling, and OM information. The SS7 signaling is transparently transmitted to the XPU board in the MPS/EPS through the SCU board. Figure 10-1 Links on the A and Ater interfaces (TCS configured locally)

Figure 10-2 shows the links that need to be configured on the A and Ater interfaces when the TCS is configured remotely. The SS7 signaling is transparently transmitted to the EIUa or XPUa board in the MPS/EPS for processing through the Ater interface.

Issue 07 (2010-09-15)


10-7



Figure 10-2 Links on the A and Ater interfaces (TCS configured remotely)

10.2.2 Timeslot Assignment on the Ater Interface This section describes the timeslot assignment principles of the Ater OMLs and signaling links and the dynamic assignment principles of traffic timeslots.

OM Timeslots and Signaling Timeslots on the Ater Interface In BM/TC separated mode, the data related to the Ater interface needs to be configured. When the TCS is configured locally, the SS7 signaling that is transparently transmitted over the Ater interface occupies the timeslots on the Ater interface. The occupied bandwidth is the same as that on the A interface. When the TCS is configured remotely, the Ater OMLs, Ater signaling links, and transparently transmitted SS7 signaling occupy the timeslots on the Ater interface. The bandwidth occupied by the SS7 signaling on the Ater interface is the same as that on the A interface. The timeslot bandwidth occupied by the Ater OMLs and Ater signaling links is subject to the BSC6900 configuration. Table 10-4 lists the bandwidth of OM timeslots and signaling timeslots on the Ater interface. Table 10-4 Bandwidth of OM timeslots and signaling timeslots on the Ater interface

10-8

Typical Configuration

Bandwidth of Ater OMLs

Bandwidth of Ater Signaling Links

MPS+TCS

16 timeslots of 64 kbit/s

The MPS is configured with four timeslots of 64 kbit/s.


Issue 07 (2010-09-15)



Typical Configuration

Bandwidth of Ater OMLs

Bandwidth of Ater Signaling Links

MPS+EPS+2TCS


Each BM subrack is configured with four timeslots of 64 kbit/s.

MPS+2EPS+3TCS



MPS+3EPS+4TCS



MPS+EPS+TCS



MPS+3EPS+2TCS


Each BM subrack is configured with eight timeslots of 64 kbit/s.

Traffic Timeslots on the Ater Interface The traffic timeslots on the Ater interface are assigned dynamically. Except for the timeslots occupied by the OMLs and signaling links, all the other timeslots on the Ater interface are traffic timeslots, which form a resource pool. The unit of the resources in the resource pool is 16 kbit/s sub-timeslot. All the idle sub-timeslots form an FIFO queue. If required, the sub-timeslots will be taken out of the queue. For example, to establish a call, the EIUa board in the TCS selects a 16 kbit/s sub-timeslot (head element of the FIFO queue) that is not used for the longest time from the resource pool and uses it as the Ater path for the call. When the call is terminated, the sub-timeslot is released to the resource pool and is added to the tail of the FIFO queue.

10.2.3 Configuration Rules of the Gb Interface Links This section describes the configuration rules and reference information related to the Gb interface links. The Gb interface can use the FR protocol or the IP protocol. For different protocols, the configuration parameters and configuration rules of the Gb interface links are different. When the Gb interface uses the FR protocol, the configuration of Gb interface links involves the NSE, BC, NSVC, and PTPBVC. When the Gb interface uses the IP protocol, the configuration of Gb interface links involves the NSE, local NSVL, remote NSVL, and PTPBVC. Table 10-5 describes the configuration parameters.

Issue 07 (2010-09-15)


10-9



Table 10-5 Description of the configuration parameters Configuration Parameter

Description

BC (Bearer Channel)

BC is the bearer channel for the frame relay. It is an E1/T1 timeslot group used to transfer data and signaling on the Gb interface. Bandwidth = Number of timeslots x 64 kbit/ s. One or several BCs can be configured on one E1. Each BC on an E1 is assigned a number to facilitate local management. This number is called BC ID. For an E1, the BC ID at the local end and the BC ID at the peer end can be different, but the timeslot distribution at both ends must be consistent.

NSVC (Network Service Virtual Connection)

NSVC is the end-to-end virtual connection between the BSC6900 and the SGSN. The NSVC on the BSC6900 side and the NSVC on the SGSN side have a one-to-one relation. Their NSVCIs are the same. The NS divides the NSVCs into different groups. Each group is identified by an NSEI. The NSVCs in the same group work in load sharing mode. If one NSVC fails, the NS switches the data on this NSVC to another NSVC for transmission. One NSVC group of the BSC6900 is connected to one SGSN. In an FR network, one NSVC corresponds to one PVC. In an IP network, one NSVC is identified by the combination of the local IP address, local port, peer IP address, and peer port.

PVC (Permanent Virtual Connection)

10-10

PVC is the permanent virtual connection for the frame relay. It is a logical transmission channel. Multiple PVCs can be established on one BC. The PVCs are identified by Data Link Connection Identifiers (DLCIs). The DLCI on the BSC6900 side and that on the SGSN side must be the same. The PVC is created together with the NSVC.


Issue 07 (2010-09-15)



Configuration Parameter

Description

NSE

The NSE is represented by a BVC set at the BSSGP layer and an NSVC set at the NS layer. The NSE is identified by the NSEI. The NSEI on the BSC6900 side and that on the SGSN side must be consistent. The NSE can be configured to use the FR protocol or IP protocol. In the case of Gb over FR, BC and NSVC need to be configured. In the case of Gb over IP, device IP address, port number, routing, and NSVL need to be configured.

Local NSVL and remote NSVL

A local NSVL is an IP end point at the local end. It is used to carry the services on a specific NSE. The configuration parameters related to a local NSE are IP address and UDP port number, which are configured on the FG2a/FG2c/GOUc board. A remote NSVL is an IP end point at the remote end. It is a connection parameter provided by the SGSN. The local and remote NSVLs specify a communication link.

PTPBVC (Point To Point BSSGP Virtual Connection)

PTPBVC is the point-to-point virtual connection at the BSSGP layer.

Figure 10-3 shows the logical connections at the NS and BSSGP layers between the BSC6900 and the SGSN.

Issue 07 (2010-09-15)


10-11



Figure 10-3 Logical connections at the NS and BSSGP layers

l

As shown in Figure 10-3, the NSE is represented by a BVC set at the BSSGP layer and an NSVC set at the NS layer. The NS layer provides data transmission channels for the BSSGP layer. The data transmission channels for the cells under one NSE must be selected from the NSVC group under this NSE so that the traffic is evenly distributed among the NSVCs.

l

In the case of Gb over FR, services are carried on the NSVC and BC. In the case of Gb over IP, services are carried on the links specified by the local and remote NSVLs.

10.3 Data Configuration Principles for Base Stations This section describes the configuration rules and reference information related to a base station. 10.3.1 Numbering Rules of BTS Components This section describes the numbering rules of the BTS components, including the cabinets, subracks, and boards of the SingleRAN and non-SingleRAN 3900 series base stations. 10.3.2 Configuration Rules of the BTS Boards This section describes the configuration rules of the SingleRAN and non-SingleRAN BTS boards. 10.3.3 Configuration Rules of the TRX Send and Receive Modes This section describes the configuration rules of the send mode, receive mode, and send and receive modes of the TRX boards of all types. 10.3.4 Configuration Rules of the BTS Clock Sources This section provides the configuration rules of the BTS clock sources. 10.3.5 BTS Network Topologies 10-12


Issue 07 (2010-09-15)



The BSC6900 provides flexible BTS network topologies on the Abis interface. These topologies are star topology, chain topology, tree topology, and ring topology. 10.3.6 TDM-Based Networking on the Abis Interface In TDM-based networking mode, the BSC6900 and the base station communicate with each other through the SDH/PDH network, and TDM transmission is applied to the Abis interface. 10.3.7 IP-Based Networking on the Abis Interface In IP-based networking mode, the BSC6900 and the base station communicate with each other through the IP/SDH/PDH network, and layer 3 of the protocol stack for the Abis interface uses the IP protocol. 10.3.8 Typical Configuration Scenarios of the Radio Layer This section provides several typical configuration modes of the BTS radio layer in terms of cells and TRXs. The difference between different configuration modes mainly lies in the number of cells and TRXs at different BTSs. 10.3.9 Concepts of the BTS Multiplexing Mode This section describes BTS multiplexing, that is, the multiplexing of the LAPD signaling on the E1 timeslots of the Abis interface. The BSC6900 provides the 64 kbit/s statistical multiplexing mode and the physical 16 kbit/s multiplexing mode. 10.3.10 Instances of BTS Multiplexing Modes This section describes the E1 timeslot assignment in 1:1, 2:1, 3:1, and 4:1 multiplexing modes. 10.3.11 Principles of DFCU/DFCB Configuration The filter combiner unit for DTRU BTS is located in the DAFU subrack of the BTS3012 or BTS3012AE or BTS3012 II. The filter combiner unit features a lower combination loss, and therefore, can meet the requirements of large coverage and save antennas when large-scale BTSs are used. 10.3.12 Configuration Rules of Upgrading Cabinets from Version 8.x to Version 9.0 This section describes the configuration rules of upgrading cabinets from an 8.x version to the 9.0 version. The components involved in the upgrade are the BBU subrack, RF subrack, and monitoring boards. 10.3.13 Configuration Guidelines for Typical TRX Power The typical TRX power specifications are only used as reference for onsite configurations. Specific data configurations should be adjusted according to onsite situations.

10.3.1 Numbering Rules of BTS Components This section describes the numbering rules of the BTS components, including the cabinets, subracks, and boards of the SingleRAN and non-SingleRAN 3900 series base stations.

Numbering Rules of the SingleRAN BTS Components Cabinet configuration A site can be configured with both the virtual cabinet and the physical cabinet. Components that a physical cabinet can house depend on the cabinet type. A virtual cabinet, however, can house all possible components. The following table provides the numbering rules of cabinets.

Issue 07 (2010-09-15)


10-13



Table 10-6 Numbering rules of cabinets Cabinet Number

Description

0

Cabinet 0 houses the BBU where the main controlling board is located. The BTS type determines whether a virtual or a physical cabinet is used. 1. In the case of a distributed base station without a physical cabinet, a virtual cabinet can be used. 2. In the case of a distributed base station with a physical cabinet or a macro base station, a physical cabinet can be used. Cabinets 1-62 are numbered by the user according to the actual situation.

1-62

NOTE According to the preceding application scenario analysis, a maximum of eight cabinets can be configured for the GU mode when the TCS is configured locally.

Table 10-7 Cabinet selection BTS Model

Optional Cabinet Type

Description

DBS3900

APM30/APM100/APM200/ TMC/BBC/PS4890/OMB/ VIRTUAL

Generally, the APM30 cabinet is used.

BTS3900/BTS3900A

APM30/APM100/APM200/ TMC/BBC/PS4890/OMB/ RFC-6/BTS3900/ BTS3900L/VIRTUAL

l For the BTS3900, the BTS3900, PS4890, or TMC cabinet is generally used. l For the BTS3900A, the APM30, RF cabinet, or TMC cabinet is generally used.

Subrack configuration 1.

If the cabinet type is determined, physical subracks, such as the BBU3900 subrack and the RFU subrack, are installed before delivery.

2.

Some optional peripherals, such as the EMU and the GPS receiver, can occupy an independent subrack for easy maintenance and extensibility.

All the subracks use the same numbering rule. For a subrack that is installed in the cabinet before delivery, the subrack number cannot be modified. For an extension subrack, the user can define the subrack number. The following table provides the numbering rules of subracks. 10-14


Issue 07 (2010-09-15)



Table 10-8 Numbering rules of subracks Subrack Number

Subrack Type

Description

0

Physical subrack

The number of the BBU subrack is 0.

1

Reserved

This subrack number is used only when two BBUs are interconnected.

2-3

Reserved

-

4

Physical subrack

RFU

5

Physical subrack

RFU

6

Reserved

-

7

Physical subrack

PMU

8

Physical subrack

TCU

9

Physical subrack

BAT

10

Reserved

This subrack number is not used currently.

11

Physical subrack

FMU

12

Physical subrack

FMU

13-39

Reserved

Reserved for physical subracks

40-59

Extension subrack

Generally, a site is configured with the following peripherals: one GPS receiver, one EMU, one site management unit (SMU), and a maximum of four GATMs. The peripherals do not need to be configured in sequence.

Physical subrack

60-254

RRU subrack

Slot configuration The mapping between the slot number and the board type depends on the hardware specifications, as listed in the following table.

Issue 07 (2010-09-15)


10-15



Table 10-9 Numbering rules of slots Cabinet Number

Subrack Number

Subrack Type

Slot Number

Board Type Descriptio n

0-62

0

BBU3900

0-4

USCU

6

GTMU

The GTMU must be fixed in slot 6.

16

FAN

The FAN must be fixed in slot 16.

18-19

UPEU/ UEIU

The UPEU/ UEIU must be fixed in slots 18 and 19.

4-5

RFU

0-5

DRFU/ GRFU/ MRFU

7

PMU

0

PMU

1-10

PSU TCU

8

TCU

0

9

BAT

No board is configured in slot 9.

11-12

FMU

0

FMU

40-59

GPS receiver/ EMU/SMU/ GATM

0

DGPS/ EMU/ GATM

60-254

RRU

0

DRRU/ GRRU/ MRRU

Numbering Rules of the Non-SingleRAN BTS Components NOTE

For a non SingleRAN BTS, the cabinet type is set according to the BTS type, for example, cabinet type BTS3900A_GSM is selected for the BTS3900A.

10-16


Issue 07 (2010-09-15)



Table 10-10 Numbering rules of the non-SingleRAN BTS components Board Type

Optional Slot Number

Optional Subrack Number

DEMU

0, 1

2

APMU/DPMU

2-5

DTCU

6, 7

FMU, FMUA

8-11

GATM

16, 17

GTMU

6

UBFA

16

UEIU

18-19

NOTE The APMU and DTCU boards can be configured in slots 0 to 23 of subrack 5.

0

UPEU

10.3.2 Configuration Rules of the BTS Boards This section describes the configuration rules of the SingleRAN and non-SingleRAN BTS boards.

Configuration Rules of the SingleRAN BTS Boards BTS3900 Table 10-11 Configuration rules of the BTS3900 boards

Issue 07 (2010-09-15)

Board Type

Automatic Configuration or Manual Configuration

EMU

Manual configuration. An EMU needs to be configured when the number of Boolean inputs provided by the UPEU and UEIU cannot meet the requirements.

PMU

Manual configuration

FMU


GATM

Manual configuration. A GATM needs to be configured when the newly deployed GSM BTS is configured with a RET antenna or TMA.

PSU


GTMU

Automatic configuration


10-17



Board Type


FAN


UEIU


UPEU


UBRI


USCU


DRFU


GRFU


MRFU


DBS3900 Table 10-12 Configuration rules of the DBS3900 boards Board Type


EMU


PMU


DTCU


GTMU


FAN


UEIU


UPEU


UBRI


USCU


DRRU


GRRU


MRRU


BTS3900A 10-18


Issue 07 (2010-09-15)



Table 10-13 Configuration rules of the BTS3900A boards Board Type


EMU


PMU


DTCU


FMUA/FMU


GATM


GTMU


FAN


UEIU


UPEU


UBRI


USCU


DRFU


GRFU


MRFU


Configuration Rules of the Non-SingleRAN BTS Boards BTS3900B Table 10-14 Configuration rules of the BTS3900B boards Board Type


3900B


BTS3900E

Issue 07 (2010-09-15)


10-19



Table 10-15 Configuration rules of the BTS3900E boards Board Type


DEMU


APMU


DTCU


3900E


BTS3012 Table 10-16 Configuration rules of the BTS3012 boards Board Type


DTMU


DEMU


DCSU


DCCU


DATU


DPTU


DABB


DCMB

Automatic configuration in the case of 12 TRXs

ECMB

Automatic configuration in the case of 18 TRXs

DBS3900 Table 10-17 Configuration rules of the DBS3900 boards

10-20

Board Type


APMU


DTCU



Issue 07 (2010-09-15)



Board Type


DEMU

Manual configuration. A DEMU needs to be configured when the number of Boolean inputs provided by the UPEU and UEIU cannot meet the requirements.

GATM


GTMU


UBFA


UEIU


UPEU


BTS3900 Table 10-18 Configuration rules of the BTS3900 boards Board Type


FMU


DEMU


GATM


GTMU


UBFA


UEIU


UPEU


BTS3900A

Issue 07 (2010-09-15)


10-21



Table 10-19 Configuration rules of the BTS3900A boards Board Type


APMU


DTCU


FMUA


DEMU


GATM


GTMU


UBFA


UEIU


UPEU


10.3.3 Configuration Rules of the TRX Send and Receive Modes This section describes the configuration rules of the send mode, receive mode, and send and receive modes of the TRX boards of all types. The following table provides the configuration rules of the TRX send and receive modes.

10-22


Issue 07 (2010-09-15)



Table 10-20 Configuration rules of the TRX send and receive modes TR X Bo ard

Send Mode

Receiv e Mode

Send and Receive Mode

Remarks

DR RU

PBT

Main and diversit y

Single feeder [1TX + 1RX]

1. Send Mode can be set to PBT only when the DRRU is configured with one frequency.

Fourway receive diversit y


Transmit diversity Dynamic transmit diversity Dynamic PBT Independe nt transmit or combinati on

Double feeder [2TX + 2RX] Double feeder [2TX + 4RX] Double feeder [1TX + 1RX]

2. Send Mode can be set to DIVERSITY only when the DRRU is configured with one frequency and DRRU Snd Rcv Mode is set to DOUBLE_ANTENNA or DOUBLEFOUR_ANTENNA. 3. Receive Mode can be set to FOURDIVERSITY only when the DRRU is configured with one frequency and DRRU Snd Rcv Mode is set to DOUBLEFOUR_ANTENNA. 4. If SGL_ANTENNA or DOUBLEFOUR_ANTENNA is selected, the relation between the RRUs needs to be configured.

Double feeder [1TX + 2RX]

Issue 07 (2010-09-15)


10-23



TR X Bo ard

Send Mode

Receiv e Mode


Remarks

DR FU

PBT

Main and diversit y


1. Send Mode can be set to PBT only when the DRFU is configured with one frequency.



Transmit diversity Dynamic transmit diversity Dynamic PBT Independe nt transmit or combinati on

Double feeder [2TX + 2RX]

2. Send Mode can be set to DIVERSITY only when the DRFU is configured with one frequency and DRFU Snd Rcv Mode is set to DOUBLE_ANTENNA or DOUBLEFOUR_ANTENNA. Receive Mode can be set to FOURDIVERSITY only when the DRFU is configured with one frequency and DRFU Snd Rcv Mode is set to DOUBLEFOUR_ANTENNA.

Double feeder [2TX + 4RX] Double feeder [1TX + 1RX] Double feeder [1TX + 2RX]

10-24


Issue 07 (2010-09-15)



TR X Bo ard

Send Mode

Receiv e Mode


Remarks

GR RU/ MR RU

Noncombinati on

Main and diversit y


1. If DOUBLEFOUR_ANTENNA is selected, the relation between the RRUs needs to be configured.



Transmit diversity Dynamic transmit diversity

2. Send Mode can be set to DIVERSITY only when DOUBLE_ANTENNA or DOUBLEFOUR_ANTENNA is selected.

Double feeder [2TX + 2RX] Double feeder [2TX + 4RX] Double feeder [1TX + 1RX] Double feeder [1TX + 2RX]

Issue 07 (2010-09-15)


10-25



TR X Bo ard

Send Mode

Receiv e Mode


Remarks

GR FU/ MR FU

Transmit diversity

Main and diversit y


If DOUBLEFOUR_ANTENNA is selected, the relation between the RRUs needs to be configured.



Independe nt transmit or combinati on

Double feeder [2TX + 2RX] Double feeder [2TX + 4RX] Double feeder [1TX + 1RX] Double feeder [1TX + 2RX]

10.3.4 Configuration Rules of the BTS Clock Sources This section provides the configuration rules of the BTS clock sources. The following table lists the configuration rules of the BTS clock sources.

10-26


Issue 07 (2010-09-15)



Table 10-21 Configuration rules of the BTS clock sources Clock Mode BTS Boa rd

BTS Mode l

Trans missio n Mode

Inte rnal Cloc k

Trac e BSC Cloc k

Exte rnal Sync cloc k

IP Cloc k

Trac e Tran spor t Cloc k

Trac e GPS Cloc k

Um Cloc k

Peer Cloc k

GT MU

DBS3 900 BTS39 00 BTS39 00A BTS39 00L

IP over FE

Supp orted

Not supp orted

Supp orted

Supp orted

Supp orted

Supp orted

Not suppo rted

Supp orted

IP over E1

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Supp orted

HDLC

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Supp orted

TDM

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Supp orted

IP over FE

Supp orted

Not supp orted

Supp orted

Supp orted

Supp orted

Supp orted

Not suppo rted

Not suppo rted

IP over E1

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Not suppo rted

HDLC

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Not suppo rted

TDM

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Not suppo rted

BTS30 06C BTS30 02E

HDLC

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Not suppo rted

TDM

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Supp orted

Not suppo rted

Not suppo rted

BTS39 00B

IP over FE

Supp orted

Not supp orted

Not supp orted

Supp orted

Not supp orted

Not suppo rted

Supp orted

Supp orted

DT MU

DO MU

BTS 3900 B

Issue 07 (2010-09-15)

Clock Source Type

BTS30 12 BTS30 12AE BTS30 12II


10-27



Clock Mode

Clock Source Type

BTS Boa rd

BTS Mode l

Trans missio n Mode

Inte rnal Cloc k

Trac e BSC Cloc k

Exte rnal Sync cloc k

IP Cloc k

Trac e Tran spor t Cloc k

Trac e GPS Cloc k

Um Cloc k

Peer Cloc k

BTS 3900 E

BTS39 00E

IP over FE

Supp orted

Not supp orted

Supp orted

Supp orted

Supp orted

Not suppo rted

Not suppo rted

Not suppo rted

HDLC

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Not suppo rted

Not suppo rted

Not suppo rted

TDM

Supp orted

Supp orted

Supp orted

Not supp orted

Not supp orted

Not suppo rted

Not suppo rted

Not suppo rted

10.3.5 BTS Network Topologies The BSC6900 provides flexible BTS network topologies on the Abis interface. These topologies are star topology, chain topology, tree topology, and ring topology.

Star Topology In a star topology, BTSs connect to a BSC6900 directly, and the BTSs do not have lower-level BTSs. Star topology is a commonly used network topology. It is applicable in common scenarios, especially in densely populated areas. Figure 10-4 shows the star topology. Figure 10-4 Star topology

10-28


Issue 07 (2010-09-15)



The advantages of the star topology are as follows: l

Simple network structure

l

Easy engineering implementation

l

Convenient network maintenance

l

Flexible capacity expansion

l

High network reliability

Disadvantages: Compared with other topologies, the star topology requires a largest quantity of transmission cables. Especially for small-scaled BTSs, transmission resource utilization in the star topology is not high. A timeslot integration device can be used to solve this problem.

Chain Topology In a chain topology, BTSs are cascaded. The BTSs on a cascading link can only process the timeslots of their own and transparently transmit the timeslots of the lower-level BTSs. The BTS chain topology is applicable to sparsely populated areas in the strip-like terrain, such as areas along highways and high-speed railways. If the star topology is used in this situation, the transmission resource is wasted. Therefore, the chain topology is recommended. Figure 10-5 shows the chain topology. Figure 10-5 Chain topology

Advantages: The chain topology can reduce the costs of transmission equipment and engineering construction and save the rent for the transmission links. Disadvantages: l

The reliability of the transmission link is poor because the signal transmission passes through multiple nodes.

l

A faulty BTS may affect the normal operation of its lower-level BTSs.

l

The number of cascading levels must not exceed five.

To minimize the impact of the faulty upper-level BTS on lower-level BTSs, the Abis bypass function is provided. In bypass mode, a relay switch is installed on the BTS. When a BTS is running normally, the timeslots of the lower-level BTSs are switched over from the incoming E1 port to the outgoing E1 port through the switching board of the BTS. When the BTS fails to provide services due to power-off or other reasons, the relay switch works to ensure the direct connection between the incoming E1 port and the outgoing E1 port on the BTS. Therefore, the lower-level BTSs still retain the connection to the BSC6900. Figure 10-6 shows the bypass function of the BTS.

Issue 07 (2010-09-15)


10-29



Figure 10-6 Bypass function of the BTS

Tree Topology In a tree topology, one site is connected with two or more subsites. The tree topology is the combination of the chain topology and the star topology. The tree topology is applicable to areas where network structures, BTS distribution, and subscriber distribution are complicated. Figure 10-7 shows the tree topology. Figure 10-7 Tree topology

Advantages: The number of transmission cables required in the tree topology is smaller than that in the star topology. Disadvantages:

10-30


Issue 07 (2010-09-15)



l

In a tree topology, the signal transmission passes through multiple nodes. Therefore, the transmission reliability is relatively low, the engineering construction is difficult, and the maintenance is inconvenient.

l

A faulty BTS may affect the normal operation of its lower-level BTSs.

l

It is inconvenient to expand the capacity of the network.

l

The number of cascading levels must not exceed five.

Ring Topology The ring topology is a special chain topology. Several BTSs form a chain, and the lowest-level BTS is connected to the BSC6900, thus forming a ring. If there is a breakpoint on the ring, the BTSs that precede the breakpoint remain unchanged in the network topology, whereas the BTSs that follow the breakpoint form a new chain connection in the reverse direction. The ring topology is applicable to common scenarios. Due to its strong self-healing capability, the ring topology is preferably applied so long as the transmission links meet the networking requirements. Figure 10-8 shows the ring topology. Figure 10-8 Ring topology

Advantages: The ring topology has a strong self-healing capability. If the E1 link at a point is broken, a new chain connection can be formed without affecting the ongoing services. Disadvantages: In a ring topology, there is always a segment of transmission link that does not transmit any data.

10.3.6 TDM-Based Networking on the Abis Interface In TDM-based networking mode, the BSC6900 and the base station communicate with each other through the SDH/PDH network, and TDM transmission is applied to the Abis interface.

TDM-Based Networking In this networking mode, the EIUa/OIUa/POUc board of the BSC6900 functions as the Abis interface board. The EIUa board provides E1/T1 ports, the OIUa board provides channelized STM-1 ports, and the POUc board provides channelized STM-1 ports and OC-3 ports. Figure 10-9 shows the TDM-based networking on the Abis interface.

Issue 07 (2010-09-15)


10-31



Figure 10-9 TDM-based networking on the Abis interface

Features of Networking Modes Advantages: The networking is mature, QoS-assured, safe, and reliable. Telecom operators can make full use of the SDH/PDH transmission network resources. Disadvantages: The cost of the TDM networking mode is higher than that of the IP networking mode.

10.3.7 IP-Based Networking on the Abis Interface In IP-based networking mode, the BSC6900 and the base station communicate with each other through the IP/SDH/PDH network, and layer 3 of the protocol stack for the Abis interface uses the IP protocol.

IP over E1 Networking In this networking mode, the BSC6900 and the base station communicate with each other through the SDH/PDH network. The PEUa/POUc board functions as the Abis interface board. The PEUa board provides E1/T1 ports, and the POUc board provides STM-1 ports and OC-3 ports. See Figure 10-10. Figure 10-10 IP over E1 Networking

IP over Ethernet Networking (Layer 2) In this networking mode, the BSC6900 and the base station communicate with each other through the IP network, and the data transmitted between them is processed by the switch according to the data link layer protocol. The FG2a/GOUa/FG2c/GOUc board of the BSC6900 functions as the Abis interface board and provides FE/GE ports. Figure 10-11 shows the IP over Ethernet networking (layer 2).

10-32


Issue 07 (2010-09-15)



Figure 10-11 IP over Ethernet networking (layer 2)

IP over Ethernet Networking (Layer 3) In this networking mode, the BSC6900 and the base station communicate with each other through the IP network, and the data transmitted between them is processed by the router according to the IP protocol. The FG2a/GOUa/FG2c/GOUc board of the BSC6900 functions as the Abis interface board and provides FE/GE ports. Figure 10-12 shows the IP over Ethernet networking (layer 3). Figure 10-12 IP over Ethernet networking (layer 3)

Features of Networking Modes Advantages: l

IP over E1 Networking – Telecom operators can make full use of the SDH/PDH transmission network resources. – The networking is mature, QoS-assured, safe, and reliable.

l

IP over Ethernet Networking – The base station provides large-capacity bandwidth through FE/GE ports, thus facilitating the upgrade and capacity expansion. – The transmission network supports the evolution from the GSM TDM network to the IP network.

Disadvantages: l Issue 07 (2010-09-15)

IP over E1 Networking Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

10-33



This networking mode does not meet the requirements of the evolution from the telecom network to the IP network. l

IP over Ethernet Networking The QoS of the network cannot be guaranteed easily. Therefore, the end-to-end QoS mechanism must be adopted.

10.3.8 Typical Configuration Scenarios of the Radio Layer This section provides several typical configuration modes of the BTS radio layer in terms of cells and TRXs. The difference between different configuration modes mainly lies in the number of cells and TRXs at different BTSs.

Definition of Typical Configuration Generally, BTSs have two configuration modes, that is, S x and S x/x/x. l

"S" represents a BTS.

l

The quantity of "x"s represents the number of cells.

l

The value of "x" indicates the number of TRXs under each cell.

For example, S2 indicates that there is one cell under a BTS, and there are two TRXs under this cell. S2/2/2 indicates that there are three cells under a BTS, and two TRXs under each cell.

Typical Configuration Scenarios The typical configuration scenarios of BTSs are as follows: l

S2

l

S2/2/2

l

S4/4/4

l

S6/6/6

l

S8/8/8

l

S12/12/12

The BTS configuration processes in all scenarios are the same. The configuration objects and quantity, however, are different from each other.

10.3.9 Concepts of the BTS Multiplexing Mode This section describes BTS multiplexing, that is, the multiplexing of the LAPD signaling on the E1 timeslots of the Abis interface. The BSC6900 provides the 64 kbit/s statistical multiplexing mode and the physical 16 kbit/s multiplexing mode.

Timeslots and Sub-Timeslots The bandwidth of each E1 link is 2.048 Mbit/s, which consists of 32 timeslots. The transmission rate on each timeslot is 64 kbit/s. Each timeslot is divided into four sub-timeslots, and the transmission rate on each sub-timeslot is 16 kbit/s.

Timeslot Types of the Abis Interface The timeslots of the BTS Abis interface are classified into the following types: 10-34


Issue 07 (2010-09-15)


l


Operation and maintenance link (OML) link for operation and maintenance of a BTS. Each BTS has only one OML, and the transmission rate on the OML is 64 kbit/s. An OML can be multiplexed with only the RSLs of the same BTS.

l

Radio signaling link (RSL) Signaling link of a TRX. Each TRX has one RSL at a rate of 64 kbit/s. RSLs can be multiplexed with only the OML or other RSLs of the same BTS.

l

Extended signaling link (ESL) Extended signaling link. When the timeslot assignment mode on the Abis interface of the BTS is set to FLEX_ABIS, each BTS requires one 64 kbit/s ESL for transmitting the signaling of dynamic Abis timeslot connection. ESL can be multiplexed with only the OML of the same BTS in a 64 kbit/s timeslot of the same E1 link.

l

Traffic channel (TCH) Traffic channel of a TRX. The full transmission rate is 16 kbit/s, and the half transmission rate is 8 kbit/s.

l

Idle Idle timeslot of a BTS, which has a rate of 16 kbit/s. Idle timeslots can be multiplexed with only the TCHs of the same cabinet group.

l

Semi Monitoring timeslot of a BTS, which has a rate of 8 kbit/s, 16 kbit/s, 32 kbit/s, or 64 kbit/ s and cannot be multiplexed with timeslots of other types.

64 kbit/s Statistical Multiplexing Mode Statistical multiplexing is a technology where n channels share one 64 kbit/s timeslot, each in a different time slice, that is, Time Division Multiplexing (TDM). In statistical multiplexing mode, multiple channels are multiplexed onto one 64 kbit/s bandwidth. The 64 kbit/s statistical multiplexing mode consists of the following types: l

1:1

l

2:1

l

3:1

l

4:1

l

5:1

l

6:1

That is, n:1 (n<=6), where n represents the number of signaling links and 1 represents one E1 timeslot (64 kbit/s) on the Abis interface. When the Abis interface uses a 64 kbit/s timeslot for signaling transmission, traffic channels cannot use the same timeslot. RSLs use 64 kbit/s timeslots through multiplexing. In all the n:1 multiplexing modes, the speech rate is 16 kbit/s or 8 kbit/s (half rate). Four fullrate traffic channels or eight half-rate traffic channels occupy one 64 kbit/s timeslot on the Abis interface. The rate of all the signaling links is 64 kbit/s. Based on the multiplexing mode (n:1), n signaling timeslots occupy one E1 timeslot (64 kbit/s) on the Abis interface. All the timeslots implement 64 kbit/s switching in the Abis interface board of the BSC6900. Issue 07 (2010-09-15)


10-35



Physical 16 kbit/s Multiplexing Mode In physical 16 kbit/s multiplexing mode, a 16 kbit/s sub-timeslot is permanently assigned to a channel, that is, this channel exclusively uses this timeslot. When the Abis interface uses a 16 kbit/s rate for signaling transmission, timeslots of the E1 link, excluding timeslot 0 (synchronization timeslot), can be configured as traffic timeslots or signaling timeslots. Therefore, the multiplexing ratio is not involved.

10.3.10 Instances of BTS Multiplexing Modes This section describes the E1 timeslot assignment in 1:1, 2:1, 3:1, and 4:1 multiplexing modes. NOTE

The timeslot assignment of each multiplexing mode is based on the following conditions: l The speech rate is 16 kbit/s permanently. Four channels of speech occupy one 64 kbit/s timeslot on the Abis interface. l For the first TRX, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is the SDCCH. l When the BTSs that support the Flex Abis function use the 5:1 or 6:1 multiplexing mode, each BTS needs to be configured with one ESL. l When the BTSs that support the Flex Abis function use the 5:1 and 6:1 multiplexing modes, the multiplexing ratios of OML, ESL, and RSL are 1:1:3 and 1:1:4 respectively. The differences between the multiplexing modes 5:1 and 4:1, and 6:1 and 4:1 lie in only their multiplexing of the RSLs. BCCHs and SDCCHs use RSLs, that is, the timeslots used by T00C0 and T00C1 are included in the timeslots used by the RSLs. Therefore, the 5:1 or 6:1 mode is not displayed in the tables.

Instances of the 1:1 Multiplexing Mode Assume that BTS0 is configured with one cell and four TRXs, the channels in the cell use default settings, and the multiplexing mode is 1:1. Table 10-22 lists the timeslot assignment on the Abis interface. Table 10-22 Timeslot assignment in 1:1 multiplexing mode

10-36

Timesl ot Numb er

Sub-Timeslot Number 0 and 1

2 and 3

4 and 5

6 and 7

0

Synchronization

Synchronization

Synchronization

Synchronization

1

RSL00

2

T00C2

T00C3

T00C4

T00C5

3

T00C6

T00C7

T01C0

T01C1

4

RSL01

5

T01C2

T01C3

T01C4

T01C5

6

T01C6

T01C7

T02C0

T02C1

7

RSL02

8

T02C2

T02C3

T02C4

T02C5


Issue 07 (2010-09-15)



Timesl ot Numb er


2 and 3

4 and 5

6 and 7

9

T02C6

T02C7

T03C0

T03C1

10

RSL03

11

T03C2

T03C3

T03C4

T03C5

12

T03C6

T03C7

... 31

OML0

Instances of the 2:1 Multiplexing Mode Assume that BTS0 is configured with one cell and four TRXs, the channels in the cell use default settings, and the multiplexing mode is 2:1. Table 10-23 lists the timeslot assignment on the Abis interface. Table 10-23 Timeslot assignment in 2:1 multiplexing mode Timesl ot Numb er


2 and 3

4 and 5

6 and 7

0

Synchronization

Synchronization

Synchronization

Synchronization

1

T00C2

T00C3

T00C4

T00C5

2

T00C6

T00C7

T01C0

T01C1

3

RSL01+RSL02

4

T01C2

T01C3

T01C4

T01C5

5

T01C6

T01C7

T02C0

T02C1

6

T02C2

T02C3

T02C4

T02C5

7

T02C6

T02C7

T03C0

T03C1

8

RSL03

9

T03C2

T03C3

T03C4

T03C5

10

T03C6

T03C7

11

Issue 07 (2010-09-15)


10-37



Timesl ot Numb er


2 and 3

4 and 5

6 and 7

... 31

OML0+RSL00

Instances of the 3:1 Multiplexing Mode Assume that BTS0 is configured with one cell and four TRXs, the channels in the cell use default settings, and the multiplexing mode is 3:1. Table 10-24 lists the timeslot assignment on the Abis interface. Table 10-24 Timeslot assignment in 3:1 multiplexing mode Timesl ot Numb er


2 and 3

4 and 5

6 and 7

0

Synchronization

Synchronization

Synchronization

Synchronization

1

T00C2

T00C3

T00C4

T00C5

2

T00C6

T00C7

T01C0

T01C1

3

T01C2

T01C3

T01C4

T01C5

4

T01C6

T01C7

T02C0

T02C1

5

RSL02+RSL03

7

T02C2

T02C3

T02C4

T02C5

9

T02C6

T02C7

T03C0

T03C1

11

T03C2

T03C3

T03C4

T03C5

12

T03C6

T03C7

13 ... 31

OML0+RSL00+RSL01

Instances of the 4:1 Multiplexing Mode Assume that BTS0 is configured with one cell and four TRXs, the channels in the cell use default settings, and the multiplexing mode is 4:1. Table 10-25 lists the timeslot assignment on the Abis interface. 10-38


Issue 07 (2010-09-15)



Table 10-25 Timeslot assignment in 4:1 multiplexing mode Timesl ot Numb er


2 and 3

4 and 5

6 and 7

0

Synchronization

Synchronization

Synchronization

Synchronization

1

T00C2

T00C3

T00C4

T00C5

2

T00C6

T00C7

T01C0

T01C1

3

T01C2

T01C3

T01C4

T01C5

4

T01C6

T01C7

T02C0

T02C1

5

T02C2

T02C3

T02C4

T02C5

6

T02C6

T02C7

T03C0

T03C1

7

RSL03

8

T03C2

T03C3

T03C4

T03C5

9

T03C6

T03C7

10 ... 31

OML0+RSL00+RSL01+RSL02

Instances of the Physical 16 kbit/s Multiplexing Mode Table 10-26 lists the timeslot assignment on the Abis interface in the physical 16 kbit/s multiplexing mode. Table 10-26 Instances of the physical 16 kbit/s multiplexing mode Timesl ot Numb er


2 and 3

4 and 5

6 and 7

0

Synchronization

Synchronization

Synchronization

Synchronization

1

Traffic timeslot

Traffic timeslot

Traffic timeslot

Traffic timeslot

2

Signaling timeslot

Traffic timeslot

Signaling timeslot

Traffic timeslot

30

Signaling timeslot

Traffic timeslot

Signaling timeslot

Traffic timeslot

31

Signaling timeslot

Signaling timeslot

Signaling timeslot

Signaling timeslot

...

Issue 07 (2010-09-15)


10-39



10.3.11 Principles of DFCU/DFCB Configuration The filter combiner unit for DTRU BTS is located in the DAFU subrack of the BTS3012 or BTS3012AE or BTS3012 II. The filter combiner unit features a lower combination loss, and therefore, can meet the requirements of large coverage and save antennas when large-scale BTSs are used. There are two types of filter combiner unit. One is DFCU with a built-in microband combiner, and the other is DFCB (B as the model) without a built-in microband combiner.

Configuration Rules of the Boards l

The DFCU can be used independently to provide the four-in-one output.

l

The DFCB is a dual two-in-one combiner that provides two outputs, namely, tributary A and tributary B corresponding to COM1 (output) and COM2 (output) of the DFCB. Each tributary can be used to combine the output of at most two TRXs. The DFCB cannot be used independently because it has no diversity receive channel. Therefore, it can be used only with the DFCU in cascading mode to support the S6 and S12 cell configurations.

l

The DFCU/DFCB must be configured in an even slot, such as slot 0, 2, or 4, in the DAFU subrack, namely, the even slots of the original DDPU. The odd slot next to the DFCU/ DFCB slot cannot be configured with any board. In other words, a DFCU/DFCB occupies two slots.

Configuration Rules of Antenna Feeder Connections in the DFCU l

The TRX to be tuned in the DFCU must be configured on downlink tributary A of the DFCU. Tributary B cannot be configured with TRXs.

l

In the antenna feeder connections of one DFCU, a maximum of four TRXs can be configured.

l

In the antenna feeder connections of the DFCU, none of the TRXs can be configured with RF FH.

l

In the antenna feeder connections of the DFCU, the spacing between any two TRXs must be at least three frequencies.

l

In the antenna feeder connections of the DFCU, the transmit mode of any TRX cannot be set to wideband combination. By default, the transmit mode is set to transmit independency.

l

When the DFCU uses six-in-one output mode, it must work with the DFCB. You need to configure the extended connection relation for the DFCU to describe how the DFCB is cascaded to the DFCU. The DFCB provides dual two-in-one outputs.

Configuration Rules of Antenna Feeder Connections in the DFCB

10-40

l

A TRX is connected to tributary A or B of the DFCB based on actual conditions.

l

Both tributary A and tributary B of the DFCB can be configured with a maximum of two TRXs.

l

The spacing between the two TRXs in both tributaries A and B must be at least three frequencies. The frequency spacing between tributary A and tributary B has no restriction because the two tributaries are independent of each other.

l

In the antenna feeder connections of the DFCB, none of the TRXs can be configured with RF FH. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 07 (2010-09-15)



l

In the antenna feeder connections of the DFCB, the transmit mode of any TRX cannot be set to wideband combination.

l

The DFCB does not require extension connections. The extension connections are configured on the DFCU.

10.3.12 Configuration Rules of Upgrading Cabinets from Version 8.x to Version 9.0 This section describes the configuration rules of upgrading cabinets from an 8.x version to the 9.0 version. The components involved in the upgrade are the BBU subrack, RF subrack, and monitoring boards.

Configuration Rules of Upgrading the BBU Subrack You need to determine the type of cabinet 0 according to the BTS type during the upgrade, because the BBU is always installed in cabinet 0. DBS3900/BTS3900A Table 10-27 Configuration rules of upgrading the BBU subrack If Cabinet 0 Has...

Then, Modify the Type of Cabinet 0 to...

DPMU

PS4890

Local APMU and its type is APM4815

OMB

Local APMU and its type is APM30

APM30

Local DTCU

TMC

Other boards

Virtual

BTS3900 During the RFU upgrade, if the type of cabinet 0 is BTS3900, you need not modify the cabinet type. The cabinet numbers, subrack numbers, and slots numbers for the boards in the BBU need not be changed, but the UBFA board needs to be renamed FAN.

Configuration Rules of Upgrading the RF Subrack Upgrade of the RFU An RFU may be upgraded in the following two conditions: upgrading a BTS of version 8.x that does not support the filler panel to a BTS of version 9.0, or upgrading a BTS of version 8.x that supports the filler panel to a BTS of version 9.0. l

Issue 07 (2010-09-15)

Upgrading a BTS of version 8.x that does not support the filler panel to a BTS of version 9.0 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

10-41



Table 10-28 Configuration rules of upgrading the RFU (not supporting the filler panel)

l

If the Type of BTS Is...

Cabinet, Subrack, Slot Numbers Before Upgrade Are...

Cabinet, Subrack, Slot Numbers After Upgrade Are...

Then, Modify the Type of Cabinet 0 to...

BTS3900

[Cabinet X, Subrack 3, Slot Y]


BTS3900

BTS3900A


[Cabinet X+1, Subrack 4, Slot Y]

RFC-6 or add an RFC-6 cabinet

Upgrading a BTS of version 8.x that supports the filler panel to a BTS of version 9.0 Table 10-29 Configuration rules of upgrading the RFU (supporting the filler panel)

10-42

Numbe r of Cabine ts

BTS Model

CPRI Cascad ing

CPRI Port Numbe r Before Upgrad e

Numbe r of Cascad ing Levels on CPRI Chain Before Upgrad e

Cabine t Numbe r After Upgrad e

Subrac k Numbe r After Upgrad e

Slot Numbe r After Upgrad e

1

BTS390 0

CPRI ports connect ed in the star topolog y

N (0 <= N <= 5)

0

0

4

N

1

BTS390 0A

CPRI ports connect ed in the star topolog y

N (0 <= N <= 5)

0

1

4

N

2

BTS390 0

CPRI ports at two levels of cascadin g

N (0 <= N <= 5)

H (0 <= H <= 1)

N%2

4

INT(N/ 2) * 2 + H


Issue 07 (2010-09-15)



Numbe r of Cabine ts

BTS Model

CPRI Cascad ing

CPRI Port Numbe r Before Upgrad e

Numbe r of Cascad ing Levels on CPRI Chain Before Upgrad e

Cabine t Numbe r After Upgrad e

Subrac k Numbe r After Upgrad e

Slot Numbe r After Upgrad e

2

BTS390 0A

CPRI ports at two levels of cascadin g

N (0 <= N <= 5)

H (0 <= H <= 1)

N%2+ 1

4

INT(N/ 2) * 2 + H

3

BTS390 0

CPRI ports at three levels of cascadin g

N (0 <= N <= 5)

H (0 <= H <= 2)

N/2

4

(N % 2) *3+H

3

BTS390 0A

CPRI ports at three levels of cascadin g

N (0 <= N <= 5)

H (0 <= H <= 2)

N/2 + 1

4

(N % 2) *3+H

Upgrade of the RRU Table 10-30 Configuration rules of upgrading the RRU

Issue 07 (2010-09-15)

If the BTS is...

Then...

Remarks

GU dual-mode base station

Number of the RRU subrack = HOP x 6 + (PORT - 3) + 60, where 0 <= HOP <= 2, 0 <= PORT <= 5, and both the cabinet number and cabinet number are 0.

If the ADD BTSSFPMODE command can be executed, the current BTS is a GU dual-mode base station.


10-43



If the BTS is...

Then...

Remarks

Other conditions

Number of the RRU subrack = SLOT x 20 + HOP x 6 + PORT + 60, (GSM) SLOT = 0, 0 <= HOP <= 2, 0 <= PORT <= 5, and both the cabinet number and cabinet number are 0.

Configuration Rules for Upgrading the Monitoring Boards When running MML commands to configure monitoring boards, the following parameters need to be specified: the cabinet number of the management object (MCN), the subrack number of the management object (MSRN), the slot number of the management object (MSN), the number of the port to which the management object connects (MPN), and the IP address of the monitoring board (MADDRESS). Regarding a local board, the management objects refer to the cabinet, subrack, and slots of the BBU. The following table provides the MADDRESS after upgrading the monitoring boards. Table 10-31 IP addresses of the monitoring boards Monitoring Board

Communication Address

EMU

2

PMU

3, 4

TCU

7, 6

FMU

14, 15

GATM

22

TCU (dedicated for the BBC)

23, 24, 25, 26

The following table provides the configuration rules of upgrading the monitoring boards from a 8.x version to the 9.0 version.

10-44


Issue 07 (2010-09-15)



Table 10-32 Configuration rules for upgrading the monitoring boards Monitoring Board

Description

Remarks

DEMU

l If only one DEMU is used, the cabinet number, subrack number, and slot number of the DEMU are changed into 0, 40, and 0 respectively. If two DEMUs are used, the cabinet number, subrack number, and slot number of the other DEMU are changed into 0, 41, and 0 respectively.

One BTS has at most two DEMUs.

l The DEMU is renamed EMU. l You need to modify the parameters of the EMU and add the information about the management objects. GATM

l If only one GATM is used, the cabinet number, subrack number, and slot number of the GATM are changed into 0, 50, and 0 respectively. If two GATMs are used, the cabinet number, subrack number, and slot number of the other GATM are changed into 0, 51, and 0 respectively.

One BTS has at most two GATMs.

l You need to modify the parameters of the GATM and add the relation information of the management object.

Issue 07 (2010-09-15)


10-45



Monitoring Board

Description

Remarks

Local DPMU/APMU

l If only one DPMU/ APMU is used, the cabinet number, subrack number, and slot number of the DPMU/APMU are changed into 0, 7, and 0 respectively.

l You can determine whether a DPMU/APMU is a local one according to its original cabinet number, subrack number, and slot number. If the original subrack number is 2, the DPMU/APMU is a local one. If the original subrack number is 5, the DPMU/APMU is a remote one.

l If two DPMUs/APMUs are used, the cabinet number, subrack number, and slot number of the odd-numbered DPMU/ APMU are changed into 0, 7, and 0 respectively. The other DPMU/APMU is upgraded as follows: – If the BTS model is BTS3900 and the type of cabinet 1 is BTS3900, then the cabinet number, subrack number, and slot number of the other DPMU/APMU are changed into 1, 7, and 0 respectively.

l If there is a DPMU/ APMU in cabinet 0, subrack 2, and slot 4 or in cabinet 0, subrack 2, and slot 5, you need to remove it first. l After the DPMU is renamed, you need to set APMUBRDTYPE to PS4890.

– If the BTS model is BTS3900 and cabinet 1 does not exist, then add cabinet 5, and change the cabinet number, subrack number, and slot number of the other DPMU/APMU into 5, 7, and 0 respectively. Regarding the added number five cabinet, if the other DPMU/ APMU is DPMU, then the cabinet type is PS4890; if the other DPMU/APMU is APM30, then the cabinet type is APM30; if the other DPMU/APMU is APM4815, then the cabinet type is OMB.

10-46


Issue 07 (2010-09-15)



Monitoring Board

Description

Remarks

l The DPMU/APMU is renamed PMU. l You need to modify the parameters of the PMU and add the relation information of the management object.

The following is an example: View the settings of the PMU and determine how many PSUs are configured. Assume that three PSUs are configured in PMU0 by running the following command: SET BTSAPMUBP: IDTYPE=BYID, BTSID=1000, CN=0, SRN=7, SN=0, CFGFLAG=YES, APMUBRDTYPE=APM30, PSU0=YES, PSU1=YES, PSU2=YES. After the PMU0 is added, three PSUs are added. In the 9.0 version, the PSU is treated as a board, and therefore you need to add a PSU in the same way as adding a board. The MML command for adding a PSU is as follows: ADD BTSBRD: IDTYPE=BYID, BTSID=1000, CN=0, SRN=7, SN=1, BT=PSU. In this command, the CN and SRN are the same as those of the PMU0, and the SN is numbered from 1 in ascending order.

10.3.13 Configuration Guidelines for Typical TRX Power The typical TRX power specifications are only used as reference for onsite configurations. Specific data configurations should be adjusted according to onsite situations. This task takes the typical TRX power configurations of the RRU3908 and MRFU as examples. For details about the typical TRX power configurations of other models, see the Product Description of the corresponding base station model. For details about the typical TRX power configuration, see the 3900 Series Multi-Mode Base Station Typical TRX Power.

10.4 Data Configuration Guidelines for Specifications This document provides the specifications of the BSC6900. Table 10-33 lists the specifications of the BSC6900. Table 10-33 BSC6900 specifications

Issue 07 (2010-09-15)

Item

Specification

Maximum Number of TRXs

3072

Maximum Number of GSM Cells

2048

Maximum Number of External Neighboring GSM Cells

3000

Maximum Number of External Neighboring UMTS Cells

3000


10-47



10-48

Item

Specification

Number of SS7 Links

64

Number of 2 Mbit/s SS7 Links

32

Maximum Number of Internal Neighboring GSM Cells Supported by a GSM Cell

64

Maximum Number of External Neighboring GSM Cells Supported by a GSM Cell

64

Maximum Number of External Neighboring UMTS Cells Supported by a GSM Cell

64

Number of OSPs Supported by a BSC

4

Number of DSPs

183

Maximum Number of MTP3 (MTP3&MTP3b) Link Sets

183

Maximum Number of MTP (MTP3&MTP3b) Links Supported by an MTP Link Set

16

Maximum Number of MTP Links

2928

Maximum Number of MTP3 Links Supported by a CPUS

50

Maximum Number of MTP Routes

366

Maximum Number of M3UA Links Supported by a GSM CPUS

15

Maximum Number of M3UA Link Sets

183

Maximum Number of GSM M3UA Links

1024

Maximum Number of M3UA Destination Entities

183

Maximum Number of M3UA Local Entities

183

Number of M3UA Routes

366

Maximum Number of STPs

32

Maximum Number of AAL2 Paths

13000

Maximum Number of IP Paths

13000

Maximum Number of AAL2 Paths and IP Paths

13000

Maximum Number of Signaling Links over Ater Interface

64

Maximum Number of OM Links over Ater Interface

2

Maximum Number of Signaling Links over Ater Interface Supported by a TC

64

Maximum Number of Signaling Links over Pb Interface

256


Issue 07 (2010-09-15)



Item

Specification

Total Number of Routes

4096

Number of Routes on FG2c/GOUc

512

10.5 Data Configuration Principles for Numbering This section describes the numbering rules and reference information related to the BSC6900. 10.5.1 BSC6900 Subrack Number This section describes the principles of and suggestions for numbering BSC6900 subracks. 10.5.2 Transmission Resource Mapping Record Index This section describes the principles of and suggestions for numbering transmission resource mapping records. 10.5.3 Activity Factor Table Index This section describes the principle of numbering activity factor tables. 10.5.4 SCTP Link Number This section describes the principles of and suggestions for numbering SCTP links. 10.5.5 Adjacent Node ID This section describes the principles of and suggestions for numbering adjacent nodes. 10.5.6 MTP3/M3UA DSP Index This section describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs). 10.5.7 Signaling Link Set Index This section describes the principles of and suggestions for numbering signaling link sets. The signaling link set can be the MTP3 signaling link set or the M3UA signaling link set. 10.5.8 MSC ID This section describes the principles of and suggestions for numbering MSCs. 10.5.9 Logical Cell ID This section describes the principles of and suggestions for numbering logical cells. 10.5.10 GSM Cell ID This section describes the principles of numbering GSM cells. 10.5.11 NRI This section describes the principles of setting Network Resource Identifiers (NRIs). 10.5.12 PLMN ID This section defines the PLMN and describes the components of the PLMN ID. 10.5.13 LA Identifiers This section describes the principles of and suggestions for numbering Location Areas (LAs). The identifiers related to the LA are Location Area Code (LAC) and Location Area Identification (LAI). 10.5.14 RA Identifiers Issue 07 (2010-09-15)


10-49



This section describes the principles of and suggestions for numbering Routing Areas (RAs). The identifiers related to the RA are Routing Area Code (RAC) and Routing Area Identification (RAI). 10.5.15 PLMN Value Tag This section defines the PLMN value tag and describes the principles of numbering PLMN value tags.

10.5.1 BSC6900 Subrack Number This section describes the principles of and suggestions for numbering BSC6900 subracks.

Principles A cabinet of the BSC6900 has two types of subrack: MPS and EPS. If the BSC6900 is deployed in a GSM network, the TCS may exist. In this case, the MPS and EPS are collectively known as the Basic Module (BM) subrack, and the TCS is short for the TransCoder (TC) subrack.A BSC6900 supports a maximum of 8 subracks. Each subrack is uniquely but not necessarily consecutively numbered within a BSC6900. l

The mandatory MPS is the switching subrack whose number is always set to 0.

l

The EPS is the service processing subrack whose number ranges from 1 to 3. The number of required EPSs depends on the traffic requirement.

l

The TCS is the speech service processing subrack whose number ranges from 4 to 7. The number of required TCSs depends on the traffic requirement.

Suggestions It is recommended that subracks be numbered in ascending order in the directions from left to right and from bottom to top, seen from the front.

10.5.2 Transmission Resource Mapping Record Index This section describes the principles of and suggestions for numbering transmission resource mapping records.

Principles A BSC6900 supports a maximum of 150 transmission resource mapping records. The numbers of such records range from 14 to 163. NOTE

By default, 14 transmission resource mapping records (indexed from 0 to 13) are added. You cannot modify or remove them.

10.5.3 Activity Factor Table Index This section describes the principle of numbering activity factor tables.

Principles A BSC6900 supports a maximum of 34 activity factor tables. The numbers of such tables range from 0 to 33. 10-50


Issue 07 (2010-09-15)



NOTE

The activity factor table with index 0 is the default table in the BSC6900, and you cannot modify or remove it.

10.5.4 SCTP Link Number This section describes the principles of and suggestions for numbering SCTP links.

Principles The numbers of SCTP links range from 0 to 1199. SCTP links are uniquely numbered within an XPU board. The numbering for SCTP links of the same type may not be consecutive. For example, number an SCTP link on one A interface 10 and an SCTP link on another A interface 12.

10.5.5 Adjacent Node ID This section describes the principles of and suggestions for numbering adjacent nodes.

Principles The numbers of adjacent nodes range from 0 to 4599. Adjacent nodes are uniquely but not necessarily consecutively numbered within a BSC6900. For example, you can number one A adjacent node 10 and another A adjacent node 12.

Suggestions For clear and easy identification, adhere to the following numbering principles: Number the A, Ater, and Abis adjacent nodes in ascending order starting from 0 or in descending order starting from 4599. For example, you can number the A adjacent nodes in ascending order starting from 0 and number the Ater and Abis adjacent nodes in descending order starting from 4599.

10.5.6 MTP3/M3UA DSP Index This section describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs).

Principles A BSC6900 supports a maximum of 186 DSPs, including the DSPs that are either directly or indirectly connected to the Originating Signaling Points (OSPs). The number of the MTP3/ M3UA DSP ranges from 0 to 186. DSPs are uniquely but not necessarily consecutively numbered within a BSC6900 by using the DSP index. For example, you can set the number of an MSC signaling point to 10 and that of another MSC signaling point to 12.

10.5.7 Signaling Link Set Index This section describes the principles of and suggestions for numbering signaling link sets. The signaling link set can be the MTP3 signaling link set or the M3UA signaling link set. Issue 07 (2010-09-15)


10-51



Principles of Numbering MTP3 Signaling Link Sets In a BSC6900, the number of the MTP3 signaling link set ranges from 0 to 186. MTP3 signaling link sets are uniquely but not necessarily consecutively numbered within a BSC6900 by using the signaling link set index. For example, you can set the number of an MTP3 signaling link set towards a neighboring MGW to 10 and the number of an MTP3 signaling link set towards another neighboring MGW to 12.

Principles of Numbering M3UA Signaling Link Sets In a BSC6900, the numbers of M3UA signaling link sets range from 0 to 186. M3UA signaling link sets are uniquely but not necessarily consecutively numbered within a BSC6900 by using the signaling link set index. For example, you can set the number of an M3UA signaling link set towards a neighboring MSC to 11 and the number of an M3UA signaling link set towards another neighboring MSC to 13.

10.5.8 MSC ID This section describes the principles of and suggestions for numbering MSCs.

Principles MSCs are uniquely but not necessarily consecutively numbered within a BSC6900. For example, set the number of an MSC to 0 and that of another MSC to 2. NOTE

Although the number of an MSC ranges from 0 to 4095, a maximum of 64 MSCs can be configured.

Suggestions For clear and easy identification, adhere to the following numbering principles: Specify different ranges for CN nodes in different domains. For example, specify the range of 0 to 15 for CN nodes in the CS domain and the range of 16 to 31 for CN nodes in the PS domain.

10.5.9 Logical Cell ID This section describes the principles of and suggestions for numbering logical cells.

Principles The logical cell ID uniquely identifies a cell in a radio network. The logical cell ID is configured at the BSC6900. The BSC6900 sends the cell ID to the base station during a cell setup procedure. The mapping between logical cell IDs and local cell IDs are configured at the BSC6900. The BSC6900 supports a maximum of 2048 logical cells. Logical cells are uniquely but not necessarily consecutively numbered within a BSC6900. For example, you can set the ID of a logical cell to 0 and that of another logical cell to 2.

Suggestions For clear and easy identification, adhere to the following numbering principles: 10-52


Issue 07 (2010-09-15)



Specify different number ranges for logical cells in different subracks. For example, you can specify the range of 0 to 899 for the logical cells in subrack 0 (MPS) and the range of 900 to 1799 for the logical cells in subrack 1 (EPS).

10.5.10 GSM Cell ID This section describes the principles of numbering GSM cells. A GSM cell ID is used to identify the GSM cell. The BSC6900 supports a maximum of 2048 GSM cells. GSM cells are uniquely but not necessarily consecutively numbered within a BSC6900. For example, you can number a GSM cell 0 and number another GSM cell 3.

10.5.11 NRI This section describes the principles of setting Network Resource Identifiers (NRIs). An NRI uniquely identifies a CN node that serves a pool area. The value range of NRI is variable. The value range depends on the scale of a CN domain and expansion requirements. The maximum number of NRIs is 1,024. For example, a CS domain has a maximum of 16 nodes. In this case, Length of CS NRI in bits is set to 4, which indicates that an NRI is represented by four binary digits. Therefore, the value range of NRI is 0 to 15.

10.5.12 PLMN ID This section defines the PLMN and describes the components of the PLMN ID.

PLMN Public Land Mobile Networks (PLMNs), which are established and operated by executive branches or recognized private operators, provide public land mobile radio telecommunication services. PLMN IDs identify mobile communication operators of different countries. PLMNs of different operators have different PLMN IDs.

PLMN ID The PLMN ID is used to uniquely identify a PLMN worldwide. The PLMN ID consists of two parts: MCC and MNC. Figure 10-13 shows the components of the PLMN ID. Figure 10-13 Components of the PLMN ID

l Issue 07 (2010-09-15)

Mobile Country Code (MCC) is used to identify different countries or regions. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

10-53


l


Mobile Network Code (MNC) is used to identify different network operators.

10.5.13 LA Identifiers This section describes the principles of and suggestions for numbering Location Areas (LAs). The identifiers related to the LA are Location Area Code (LAC) and Location Area Identification (LAI).

LAC The LAC is used to uniquely identify an LA within a PLMN. The LAC is a 2-byte hexadecimal code. It ranges from 0000 to FFFE. The codes 0000 and FFFE are reserved. The LAC is presented in the format of h'X1X2X3X4 or H'X1X2X3X4. h' and H' are the hexadecimal symbols.

LAI The LAI is used to uniquely identify an LA worldwide. The LAI consists of three parts: MCC, MNC, and LAC. Figure 10-14 shows the components of the LAI. Figure 10-14 Components of the LAI

10.5.14 RA Identifiers This section describes the principles of and suggestions for numbering Routing Areas (RAs). The identifiers related to the RA are Routing Area Code (RAC) and Routing Area Identification (RAI).

RAC The RAC is a 1-byte hexadecimal code. It is used to uniquely identify an RA within an LA.

RAI The RAI is used to uniquely identify an RA worldwide. The RAI consists of four parts: MCC, MNC, LAC, and RAC. It can also be presented by LAI + RAC. Figure 10-15 shows the components of the RAI. Figure 10-15 Components of the RAI

10-54


Issue 07 (2010-09-15)



10.5.15 PLMN Value Tag This section defines the PLMN value tag and describes the principles of numbering PLMN value tags. The PLMN value tag is contained in the Master Information Block (MIB) and System Information Block 1 (SIB1) as an information element. The PLMN value tag in the MIB changes after an SIB1 is updated. After the UE detects the change in the PLMN value tag, it automatically reads the new SIB1. When a UE moves between neighboring cells that belong to different LAs or RAs, the UE needs to read the SIB1 of the destination cell to initiate a location update procedure, which requires that the two cells have different PLMN value tags. Therefore, during network planning, different value ranges should be allocated to the PLMN value tags of any two geographically neighboring areas (including scenarios where one area is part of the other area). The two areas can be two LAs, two RAs, or one LA and one RA. During parameter configuration, the PLMN value tags of different value ranges should be assigned to any neighboring areas after negotiation. There is no intersection between the value ranges. The area can be an LA or RA. The PLMN value tags of LAs or RAs vary within the specified range. As a result, a UE can always read different PLMN value tags when moving across the areas and thus correctly reads the SIB1. NOTE

In practice, if a cell supports PS services, the PLMN value tag of the cell varies within the specified value range of the RA to which the cell belongs. If a cell does not support PS services, the PLMN value tag of the cell varies within the specified value range of the LA to which the cell belongs.

Figure 10-16 shows an example of planning the value ranges of PLMN value tags. Figure 10-16 Example of planning the value ranges of PLMN value tags

Issue 07 (2010-09-15)


10-55

BSC6900 Configuration guide

Recommend Documents