BSC6900 GSM Initial Configuration Guide V900R013C00 03 PDF en

BSC6900 GSM
V900R013C00
Initial Configuration Guide

Issue
03
Date
2011-08-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. 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:
support@huawei.com
Issue 03 (2011-08-31)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
BSC6900 GSM
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
V900R013C00
Intended Audience
This document is intended for:
l
Field engineers
Network operators
System engineers
Organization
1 Changes in the BSC6900 GSM Initial Configuration Guide
This chapter describes the changes in the BSC6900 GSM Initial Configuration Guide.
2 Introduction to Initial Configuration
Initial configuration creates the configuration 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.
4 Initial Configuration Procedures
Issue 03 (2011-08-31)

ii
BSC6900 GSM
About This Document
This chapter describes the process of creating the initial configuration script for the BSC6900.
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
This chapter describes how to configure the global information. The global data configuration
provides a basis for all the other configurations, and therefore must be determined during network
planning. After the BSC6900 global data configuration takes effect, do not modify it unless the
network is replanned.
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 a BTS
This section describes how to configure a BTS and its cells for BSC6900. The configurations
described in this section enable a BTS to receive and transmit signals over air interfaces and
meet the requirements of the radio coverage in the cells. In addition, they also enable
BSC6900 to centrally control and manage 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.
Indicates a tip that may help you solve a problem or save
time.
Issue 03 (2011-08-31)

iii
BSC6900 GSM
About This Document
Symbol
Description
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 03 (2011-08-31)

iv
BSC6900 GSM
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.
Issue 03 (2011-08-31)
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.

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

7.1 Configuring the System Information................................................................................................................14
7.2 Configuring a Cabinet......................................................................................................................................14
7.3 Configuring a Subrack......................................................................................................................................14
7.4 Configuring a Board.........................................................................................................................................15
7.5 Configuring an EMU........................................................................................................................................16
7.6 Configuring the Clocks.....................................................................................................................................16
7.7 Configuring the Time.......................................................................................................................................19
7.8 Configuring BSC Custom Alarm.....................................................................................................................19
8 Configuring the Interfaces.........................................................................................................20

8.1 Configuring the Ater Interface (over TDM).....................................................................................................21
8.2 Configuring the Ater Interface (over IP)..........................................................................................................22
8.3 Configuring the A Interface (over TDM).........................................................................................................23
8.4 Configuring the A Interface (over IP)..............................................................................................................23
8.4.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over IP)................................23
8.4.2 Configuring the Control Plane of the A Interface (over IP)....................................................................27
8.4.3 Configuring the Mapping Between Service Types and Transmission Resources...................................28
8.4.4 Configuring the User Plane of the A Interface (over IP).........................................................................28
8.5 Configuring the Gb Interface (over FR)...........................................................................................................29
8.6 Configuring the Gb Interface (over IP)............................................................................................................29
Issue 03 (2011-08-31)

vi
BSC6900 GSM
Contents
8.7 Configuring the Pb Interface............................................................................................................................30
9 Configuring a BTS.......................................................................................................................32
9.1 Configuring the Equipment Data......................................................................................................................34
9.1.1 Configuring a BTS...................................................................................................................................34
9.1.2 Configuring BTS Cabinet........................................................................................................................35
9.1.3 Configuring BTS Boards.........................................................................................................................35
9.1.4 Configuring RF Units..............................................................................................................................36
9.2 Configuring the Logical Data...........................................................................................................................37
9.3 Configuring the Transmission Data..................................................................................................................38
9.3.1 TDM/HDLC............................................................................................................................................38
9.3.2 IP over FE/GE.........................................................................................................................................38
9.3.3 IP over E1................................................................................................................................................40
9.4 Configuring a Clock for a BTS.........................................................................................................................41
9.5 Activating the BTS Configuration....................................................................................................................41
9.6 Optional Functions of BTS...............................................................................................................................42
9.6.1 Configuring the Neighboring Cell Relations...........................................................................................42
9.6.2 Configuring the BTS Timeslots...............................................................................................................42
9.6.3 Configuring Parameters for Monitoring Boards......................................................................................44
9.6.4 Configuring a Custom BTS Alarm..........................................................................................................45
9.6.5 Configuring BTS Power Alarms.............................................................................................................46
9.6.6 Configuring IP Port Backup....................................................................................................................48
9.6.7 Configuring Connection of Monitoring Devices Through IP Ports........................................................49
9.7 Configuration in the Typical Scenario..............................................................................................................50
9.7.1 Typical BTS3900 Configuration.............................................................................................................50
9.7.2 Typical BTS3900A Configuration..........................................................................................................59
10 Configuration Reference Information...................................................................................68

10.1 Data Configuration Principles for Equipment................................................................................................69
10.1.1 Configuration Rules of the Cabinets.....................................................................................................69
10.1.2 Configuration Rules of the Subracks.....................................................................................................69
10.1.3 Configuration Rules of the Boards........................................................................................................69
10.1.4 Configuration Rules of the Clock..........................................................................................................72
10.1.5 Introduction to Time Synchronization...................................................................................................73
10.2 Data Configuration Principles for Interfaces..................................................................................................73
10.2.1 Data Configuration Principles for the A Interface.................................................................................73
10.2.2 Data Configuration Principles for the Ater Interface............................................................................89
10.2.3 Data Configuration Principles for the Gb Interface...............................................................................92
10.2.4 Data Configuration Principles for the Pb interface................................................................................98
10.3 Configuration Guidelines for the GBTS.......................................................................................................102
10.3.1 Configuration Guidelines for Cabinet Numbers..................................................................................102
10.3.2 Configuration Guidelines for Subracks...............................................................................................102
10.3.3 Configuration Guidelines for Slot Numbers........................................................................................103
10.3.4 Mapping Between Base Stations and Optional Cabinets....................................................................105
Issue 03 (2011-08-31)

vii
BSC6900 GSM
Contents
10.3.5 Configuration Rules of the BTS Boards..............................................................................................109

10.3.6 Configuration Guidelines for Monitoring Boards...............................................................................115
10.3.7 Configuration Guidelines for Power Systems.....................................................................................120
10.3.8 List of User-Defined Alarm Ports.......................................................................................................121
10.3.9 Guidelines for Configuring Send and Receive Modes for RF Modules..............................................128
10.3.10 Configuration Guidelines for Typical TRX Power...........................................................................131
10.3.11 Configuration Guidelines for BTS Clock Sources............................................................................131
10.3.12 BTS Network Topologies..................................................................................................................133
10.3.13 TDM-Based Networking on the Abis Interface.................................................................................137
10.3.14 IP-Based Networking on the Abis Interface......................................................................................137
10.3.15 Typical Configuration Scenarios of the Radio Layer .......................................................................139
10.3.16 Concepts of the BTS Multiplexing Mode..........................................................................................140
10.3.17 Instances of BTS Multiplexing Modes..............................................................................................141
10.3.18 Timeslot Assignment on the Abis Interface......................................................................................145
10.3.19 Timeslot Arrangement on the Abis Interface....................................................................................147
10.3.20 Manual Timeslot Assignment on the Abis Interface.........................................................................149
10.3.21 Semipermanent Connection...............................................................................................................150
10.3.22 Principles of Idle Timeslot Assignment............................................................................................150
10.3.23 Configuration Guidelines for DFCU/DFCB......................................................................................151
10.3.24 Configuration Guidelines for Upgrading Cabinets from Version 8.x to Version 9.0........................152
10.4 Data Configuration Guidelines for Specifications........................................................................................158
Issue 03 (2011-08-31)

viii
BSC6900 GSM
Changes in the BSC6900 GSM Initial

Configuration Guide
This chapter describes the changes in the BSC6900 GSM Initial Configuration Guide.
03 (2011-08-31)
This is the third commercial release of V900R013C00.
Compared with issue 02 (2011-04-25), this issue includes the following new topics:
l
10.3.18 Timeslot Assignment on the Abis Interface
10.3.19 Timeslot Arrangement on the Abis Interface
10.3.20 Manual Timeslot Assignment on the Abis Interface
10.3.21 Semipermanent Connection
10.3.22 Principles of Idle Timeslot Assignment
Compared with issue 02 (2011-04-25), this issue incorporates the following changes:
Content
Description
9.6.1 Configuring the Neighboring Cell

Relations
The configurations of LTE external cells are

added.
10.3.7 Configuration Guidelines for Power

Systems
The APM30(Ver.C) and the BTS3900

(Ver.C) are added.
10.3.3 Configuration Guidelines for Slot

Numbers
The description of the UBRI board is

modified.
Compared with issue 02 (2011-04-25), this issue does not exclude any topics.
02 (2011-04-25)
This is the second commercial release of V900R013C00.
Compared with issue 01 (2011-03-30), this issue does not include any new topics.
Compared with issue 01 (2011-03-30), this issue incorporates the following changes:
Issue 03 (2011-08-31)

BSC6900 GSM
Content
Description
GSM Data Preparation for the Initial

Configuration
The recommended configurations of some

parameters are added.
Configuring the Clocks
The procedure for configuring the external

clock, line clock, and GPS clock is optimized.
Compared with issue 01 (2011-03-30), this issue excludes the following topics:
l
Data Configuration Principles for Numbering
01 (2011-03-30)
This is the first commercial release of V900R013C00.
Compared with issue Draft A (2011-01-31), this issue does not include any new topics.
Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes.
Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.
Draft A (2011-01-31)
This is the Draft A release of V900R013C00.
Compared with issue 04 (2010-11-30) of V900R012C01, this issue includes the following new
topics:
l
9.6.5 Configuring BTS Power Alarms
9.6.6 Configuring IP Port Backup
9.6.7 Configuring Connection of Monitoring Devices Through IP Ports
Compared with issue 04 (2010-11-30) of V900R012C01, this issue incorporates the following
changes:
Content
Description
10.4 Data Configuration Guidelines for

Specifications
The specifications are updated.
Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not exclude any topics.
Issue 03 (2011-08-31)

BSC6900 GSM
2 Introduction to Initial Configuration
Introduction to Initial Configuration
Initial configuration creates the configuration script for the equipment to start to operate.
l
The configuration script can be created by running MML commands on the BSC6900 LMT.
For the LMT operation guide, see the BSC6900 GSM LMT User Guide.
During commissioning, the script is imported to the BSC6900. For data modification after
the BSC6900 starts operating, see the GBSS Reconfiguration Guide.
After the BSC6900 starts operating, operators can enable or disable features based on site
requirements. The related data configuration does not belong to initial configuration. For
details, see the GBSS Feature Activation Guide.
Issue 03 (2011-08-31)

BSC6900 GSM
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.
For the restrictions on the parameter settings in MML commands, see BSC6900 GSM MML
Command Reference.
Issue 03 (2011-08-31)

BSC6900 GSM
Initial Configuration Procedures
This chapter describes the process of creating the initial configuration script for the BSC6900.
Figure 4-1 shows the initial configuration process.
Figure 4-1 Initial configuration process
For details about loading the BSC6900 initial configuration data, see the BSC6900 GSM
Commissioning Guide.
Scenario: BM/TC separated and built-in PCU

The initial configuration process is as follows:
Issue 03 (2011-08-31)

BSC6900 GSM
1.
Open the initial configuration tool. For example, log in to the BSC6900 LMT.
2.
Configure the global information.
3.
Configure the equipment data.

(1) Configure the MPR, EPR, and TCR.
(2) Configure the MPS, EPS, and TCS.
(3) Configure the SCU, OMU, GCU, XPU, SPU, DPU, EIUa, FG2a, GOUa, OIUa, POUc,
and PEUa boards.
4.
Configure the GSM interfaces.

(1) Configure the Ater interface by referring to Configuring the Ater Interface (over TDM)
or Configuring the Ater Interface (over IP).
(2) Configure the A interface by referring to Configuring the A Interface (over TDM) or
Configuring the A Interface (over IP).
(3) Configure the Gb interface by referring to Configuring the Gb Interface (over FR) or
Configuring the Gb Interface (over IP).
5.
Configure a BTS.
6.
Save the initial configuration script.
Scenario: BM/TC separated and external PCU

1.
2.
3.

(1) Configure the MPR, EPR, and TCR.
(2) Configure the MPS, EPS, and TCS.
and PEUa boards.
4.

(1) Configure the Ater interface by referring to Configuring the Ater Interface (over TDM)
or Configuring the Ater Interface (over IP).
(3) Configure the Pb interface.
5.
Configure a BTS.
6.
Scenario: BM/TC combined and built-in PCU

1.
2.
3.

(1) Configure the MPR and EPR.
Issue 03 (2011-08-31)

BSC6900 GSM
(2) Configure the MPS and EPS.

and PEUa boards.
4.

(2) Configure the Gb interface by referring to Configuring the Gb Interface (over FR) or
Configuring the Gb Interface (over IP).
5.
Configure a BTS.
6.
Scenario: BM/TC combined and external PCU

1.
2.
3.

(1) Configure the MPR and EPR.
(2) Configure the MPS and EPS.
and PEUa boards.
4.

(2) Configure the Pb interface.
5.
Configure a BTS.
6.
Issue 03 (2011-08-31)

BSC6900 GSM
5 Typical Configuration Script
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 03 (2011-08-31)

BSC6900 GSM
Configuring the Global Information
About This Chapter

This chapter describes how to configure the global information. The global data configuration
provides a basis for all the other configurations, and therefore must be determined during network
planning. After the BSC6900 global data configuration takes effect, do not modify it unless the
network is replanned.
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 03 (2011-08-31)

BSC6900 GSM
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.
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. In this step, set
Operator Type to PRIM(Primary Operator).
Step 3 Optional: To add more secondary GSM operators, run the ADD GCNOPERATOR command
for each operator you want to add. In this step, set Operator Type to SEC(Secondary
Operator).
Step 4 Optional: Run the LST GLOBALROUTESW command to query the setting 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
switch to OFF.
----End
6.2 Configuring the OPC and DPC

This section describes how to configure the OPC and DPC.
Prerequisite
l
The basic data of the BSC6900 has been configured. For details, see Configuring the Basic
Data.
The MSC server is not directly connected to the BSC6900. Instead, routes are configured
on the MGW to transfer data between the BSC6900 and the MSC server.
The network ID and the signaling point code must be planned in the SS7 network.
When configuring a DPC, specify the signaling route mask for load sharing. When
configuring 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.
Context
Procedure
Step 1 Run the ADD OPC command to add an OPC, repeat this step until all desired OPCs are added.
Issue 03 (2011-08-31)

10
BSC6900 GSM
Step 2 Run the ADD N7DPC command to add a DPC. To add more DPCs, repeat this step until all
desired DPCs are added.
----End
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 03 (2011-08-31)

11
BSC6900 GSM
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 interface boards, clock source of the system, and work 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.
8.
7.8 Configuring BSC Custom Alarm
Issue 03 (2011-08-31)

12
BSC6900 GSM
This section describes how to configure alarm ports, alarm IDs, and alarm names of the
BSC.
Issue 03 (2011-08-31)

13
BSC6900 GSM
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 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.
Prerequisite
Context
The Main Processing Rack (MPR) is configured by default. You do not need to add it 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 has been configured. For details, see Configuring the Basic Data.
Issue 03 (2011-08-31)

14
BSC6900 GSM
Context
The Main Processing Subrack (MPS) is configured by default. You do not need to add this
subrack by running an MML command.
Procedure
Step 1 To add an Extended Processing Subrack (EPS) for the BSC6900, run the ADD SUBRACK
command. To add more EPSs, repeat this step until all desired EPSs are added.
Step 2 To add a TransCoder Subrack (TCS) for the BSC6900, run the ADD SUBRACK command. To
add more TCSs, repeat this step until all desired TCSs are added.
Step 3 After a subrack is added, run the SET SCUPORT command to enable the corresponding port
on the SCU board in the MPS.
Step 4 Run the SET CFGDATAEFFECTIVE command to set the subrack to effective mode.
----End
Follow-up Procedure
To enable the monitoring function of the power distribution box, complete the following steps:
1.
Run the MOD SUBRACK command to enable the monitoring function of the power
distribution box. In this step:
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.
NOTE
If output-alarm information needs to be viewed, set the corresponding switch on the PDB to ON.
Otherwise, set the corresponding switch on the PDB to OFF. There is no need to set the input switch
on the PDB for input alarms.
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.
For details about the board configuration rules, 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.
Issue 03 (2011-08-31)

15
BSC6900 GSM
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
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.
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 interface boards, clock source of the system, and work mode of the system clock source.
Prerequisite
Context
NOTE
The BSC6900 clock information is determined during network planning. In an all-IP over FE/GE network,
you do not need to configure a clock source for the BSC6900, and at this time, the BSC use the local
oscillator as default.
The clock source of the BSC6900 can be an external clock, line clock, or GPS clock.
l
External clock
An external clock can be a BITS clock or an external 8 kHz clock. When the clock source
is an external clock, the BSC6900 receives the external clock from CLKIN0 or CLKIN1
on the GCUa/GCGa board.
Line clock
The line clock is the 8 kHz clock transmitted from an interface board to the GCUa board.
It can be an A interface line clock or an Abis interface line clock. An A interface line clock
is extracted by a BSC6900 A interface board from the MSC. An Abis interface line clock
Issue 03 (2011-08-31)

16
BSC6900 GSM
is extracted from a BSC6900 Abis interface board from the transport network, and the base
station can synchronize its clock with the BSC6900 clock.
NOTE
l A interface line clock

l When the BSC uses the A interface line clock and FR transmission is used on the Gb interface,
if the the Gb interface is configured on the independent board, the clock is selected as follows:
If the SGSN and the MSC use the same clock source, you do not need to configure the Gb
interface clock. If the SGSN and the MSC use different clock sources, you need to configure
line clocks on both the A and Gb interface boards. In the latter case, set Use SGSN clock
source to YES, and set Port for LINE1 and Back-up port for LINE1 to the numbers of
the interface board ports carrying BC.
l When the BSC uses the A interface line clock and FR transmission is used on the Gb interface,
if the Gb interface and the A/Ater/Abis interface are configured on the same board, you can
not set Use SGSN clock source to YES.
l Abis interface line clock
When the BSC6900 uses the Abis interface line clock, the TDM transport network must provide
stable clock information. The Abis interface line clock is recommended when the A interface
uses IP transmission and the Abis interface uses TDM transmission.If the Gb interface and the
A/Ater/Abis interface are configured on the same board, you can not set Use SGSN clock
source to YES.
GPS clock
The GPS clock is the satellite synchronization clock. When the GCGa board is configured
with a satellite card, the BSC6900 can use the satellite antenna port on the GCGa board to
receive GPS clock signals.
Procedure
l
Configuring the external clock

1.
Run the ADD CLKSRC command to add a system clock source and the clock source
priority.
NOTE
l Clock source type

l If the clock signals are extracted from the CN by the interface board (such as the OIUa/
EIUa/PEUa interface board) in the EPS and then sent to the GCUa/GCGa board in the
MPS through the panels, Clock source type of the MPS needs to be set to
BITS1-2MHZ or BITS2-2MHZ.
l If the clock signals are extracted from the CN by the interface board in the MPS and
then sent to the GCUa/GCGa board through the backplane of the MPS, Clock source
type should be set to LINE1_8KHZ or LINE2_8KHZ.
l If the clock signals are provided by the external BITS, Clock source type should be
set to BITS1-2MBPS, BITS2-2MBPS, BITS1-1.5MBPS, or BITS2-1.5MBPS.
l If the clock signals are provided by the GPS and then sent to the GCGa board, Clock
source type should be set to GPS.
l If the clock signals are provided by the external 8 kHz clock, Clock source type should
be set to 8KHZ.
l Clock source priority
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.
2.
Issue 03 (2011-08-31)
Run the SET CLKMODE command to set the work mode of the system clock source.
17
BSC6900 GSM

NOTE
It is recommended that System clock working mode be set to AUTO(Auto Handover) so

that the system can switch to the highest-priority clock source when the current clock source
is unavailable.
Configuring the line clock

1.
Run the SET CLK command to set the clock source of the interface board.
NOTE
When the system clock is the line clock, interface boards need to be configured with clock
sources.
l A interface line clock
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.
In BM/TC separated configuration mode, the interface boards in both the TCS and MPS
need to be configured with clock sources.
l For 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 a line clock,
and different TCSs need to be configured with different clock sources.
l For 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 Abis interface line clock
The Abis interface board 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.
2.
priority.
3.
NOTE

is unavailable.
Configuring the GPS clock

1.
If the clock source is the line clock, run the SET CLK command to set the clock source
for the interface board.
2.
priority.
3.
NOTE

is unavailable.
----End
Issue 03 (2011-08-31)

18
BSC6900 GSM
Follow-up Procedure
To reconfigure the system clock source and clock source priority, run the SET CLKMODE
command.
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.
Prerequisite
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.8 Configuring BSC Custom Alarm

This section describes how to configure alarm ports, alarm IDs, and alarm names of the BSC.
Prerequisite
l
An environment monitoring unit and the sensor regarding environment alarms are installed.
Data of the environment monitoring unit is configured. For details, see Configuring an
EMU.
Context
Each environment alarm is allocated a unique alarm ID. The IDs of the BSC environment alarms
range from 65334 to 65383.
Procedure
Step 1 Run the SET ALMPORT command to set the environment alarm input port of the BSC.
Step 2 Run the SET ENVALMPARA command. In this step, set Alarm ID, Alarm Name, Alarm
Severity, and Event Type.
----End
Issue 03 (2011-08-31)

19
BSC6900 GSM
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 (over TDM)
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 Ater Interface (over IP)
This section describes how to configure the IP-based Ater interface to improve the transmission
efficiency and reduce transmission cost over the Ater interface when the BSC6900 is in BM/TC
separated and remote TCS mode.
8.3 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.4 Configuring the A Interface (over IP)
This section describes how to configure the IP-based A interface.
8.5 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.6 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.7 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 03 (2011-08-31)

20
BSC6900 GSM
8.1 Configuring the Ater Interface (over TDM)

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.
The EIUa/OIUa/POUc board is configured in the subrack to be configured with an Ater

connection path.
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 and the Ater OML needs to be established only between the MPS and the
main TCS.
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.
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.
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 Ater OML of the primary
BSC must be configured on the Ater connection path that is carried on port 0.
l In TC pool mode, the secondary BSCs do not need to be configured with Ater OMLs.
3.
Issue 03 (2011-08-31)
Run the ADD ATERSL command to add an Ater signaling link between the MPS/
EPS and the TCS.
21
BSC6900 GSM

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 Ater Interface (over IP)

This section describes how to configure the IP-based Ater interface to improve the transmission
efficiency and reduce transmission cost over the Ater interface when the BSC6900 is in BM/TC
separated and remote TCS mode.
Prerequisite
l
A license for implementing IP transmission over the Ater interface has been obtained.
The subrack to be configured with an Ater connection path is configured.
The POUc board is configured in the subrack to be configured with an Ater connection
path.
The Ater connection path, OMLs, and signaling links are configured. For details, see
Configuring the Ater Interface (over TDM).
Context
In the case of IP over Ater, IP over Ethernet is not supported over the Ater interface, and the
user plane can adopt only the IP over E1/T1 transmission mode. The data configuration for the
signaling plane similar to that in the case of TDM over Ater.
Procedure
Step 1 Configure the physical layer and data link layer for the POUc board.
Step 2 Run the SET BSCBASIC command. In this step:
l Set Service mode to SEPARATE.
l Set Ater Interface Transfer Mode to IP.
Step 3 Run the ADD ADJNODE command to add an adjacent node. In this step, set Adjacent Node
Type to BSC.
Step 4 Optional: Configure transmission resource mapping.
1.
Run the ADD TRMMAP command to add a transmission resource mapping table for the
Ater interface.
2.
Run the ADD TRMFACTOR command to add an activation factor table for the Ater
interface.
3.
Run the ADD ADJMAP command to add the TRM mapping to the adjacent node and to
add the mapping from interface transmission type to TRMMAP index and factor index.
Step 5 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.
----End
Issue 03 (2011-08-31)

22
BSC6900 GSM
8.3 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 OPC and DPC are configured. For details, see Configuring the OPC and DPC.
The EIUa/OIUa/POUc/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.4 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.
8.4.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
Issue 03 (2011-08-31)

23
BSC6900 GSM
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 Optional: Run the ADD DEVIP command to add the device IP address of the board in the case
of logical IP networking. In this step, 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 7.
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 Optional: Run the ADD VLANID command to add an IP address to the VLAN ID mapping
table.
Step 7 In link aggregation mode, complete the following steps:
1.
Run the ADD ETHTRK command to add a link aggregation group.

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 carrying 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.
----End
Issue 03 (2011-08-31)

24
BSC6900 GSM
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.
Prerequisite
Context
The MP link group is also referred to as PPP link group. 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 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform
the corresponding step.
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. In this step:
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. In this step:
l Set Board type to PEUa.
l Set Logic function type to IP.
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
Issue 03 (2011-08-31)

25
BSC6900 GSM
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 attributes of a channelized optical port. In addition, you need to
configure the PPP link, MP link group, and MP link.
Prerequisite
Context
The MP link group is also referred to as PPP link group. 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 Set the optical port attributes.

1.
Run the LST OPT command to list the attributes of an optical port.
2.
Optional: If the planned data is inconsistent with the default data, run the SET OPT
command to set the attributes of the optical port.
Step 3 Optional: When the BSC6900 needs to interconnect with the equipment from another vendor,
run the SET COPTLNK command to set the attributes of a channelized optical port on the
interface board.
Step 5 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform
If the E1/T1 link carries a/an...
Then...
PPP link
Go to Step 6.
MP link group
Go to Step 7.

Run the ADD PPPLNK command to add a PPP link. To add more PPP links, repeat this step
until all desired PPP links are added. In this step:
l Set Board type to POUc.
Step 7 Add an MP link group.
1.
Run the ADD MPGRP command to add an MP link group. In this step:
l Set Board type to POUc.
Issue 03 (2011-08-31)

26
BSC6900 GSM

2.
Run the ADD MPLNK command to add an MP link. To add more MP links, repeat this
step until all desired MP links are added. Set Board Type to POUc.
----End
8.4.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.
The physical layer and data link layer of the A interface are configured. For details, see
8.4.1 Configuring the Physical Layer and Data Link Layer of the A Interface (over
IP).
Procedure
Step 1 Run the ADD GCNNODE command to add a GSM CN node.
Step 2 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run this
command repeatedly. In this step:
l Set Signalling link mode to CLIENT.
l Set Application type to M3UA.
Step 3 Run the ADD M3LKS command to add an M3UA link set. In this step:
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 4 Run the ADD M3RT command to add an M3UA route.

Step 5 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, run this
command repeatedly.
Step 6 Run the ADD ADJNODE command to add an adjacent node. Set Adjacent Node Type to A.
----End
Issue 03 (2011-08-31)

27
BSC6900 GSM
8.4.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 with different priorities.
Prerequisite
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 with different priorities.
----End
8.4.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 GLOBALROUTESW command 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.
Issue 03 (2011-08-31)

28
BSC6900 GSM
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.5 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
The DPUd/XPUa/PEUa board is configured. For details, see Configuring a Board.
At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified
by the NSEI.
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.
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.
An NSVC maps to a PVC. When configuring an NSVC, specify its mapping PVC.
BSSGP is short for Base Station Subsystem GPRS Protocol.
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 the cell supports GPRS, run the ADD PTPBVC command
to add a PTPBVC and bind the GPRS cell to its NSE.
Step 7 Run the SET BTSIDLETS command to add an idle timeslots of the BTS.
----End
8.6 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 03 (2011-08-31)

29
BSC6900 GSM
Prerequisite
l
The basic data of the BSC6900 has been configured. For details, see Configuring the Basic
Data.
The DPUd/FG2a/XPUa board is configured. For details, see Configuring a Board.
A license for implementing IP transmission over the Gb interface is granted.
At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified
by the NSEI.
BSSGP is short for Base Station Subsystem GPRS Protocol.
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.
Step 7 Optional: Run the ADD IPRT command to add an IP route when the layer 3 networking mode
is used between the BSC6900 and the MGW. To add more IP routes, repeat this step until all
desired IP routes are added.
----End
8.7 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
The EIUa/OIUa/POUc board is configured. For details, see Configuring a Board.
Procedure
Step 1 Run the SET BSCPCUTYPE command to set the PCU type as external.
Issue 03 (2011-08-31)

30
BSC6900 GSM
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.
Step 4 Run the ADD PBSL command to add a signaling link over the Pb interface.
----End
Issue 03 (2011-08-31)

31
BSC6900 GSM
9 Configuring a BTS
Configuring a BTS
About This Chapter

This section describes how to configure a BTS and its cells for BSC6900. The configurations
described in this section enable a BTS to receive and transmit signals over air interfaces and
meet the requirements of the radio coverage in the cells. In addition, they also enable
BSC6900 to centrally control and manage radio resources for the BTS.
Context
BTSs are classified in the following two ways:
l
By software version:
SingleRAN base stations: 3900 series base stations whose software versions are
V100R009 or later
Non-SingleRAN base stations: 3x series base stations, double-transceiver base stations,
and 3900 series base stations whose software versions are earlier than V100R009
By base station type:

3x series base stations: BTS30, BTS312, BTS3012A, and BTS3006A
Double-transceiver base stations: BTS3012, BTS3012II, BTS3012AE, BTS3006C,
BTS3002E
3900 series base stations: BTS3900, BTS3900A, BTS3900L, DBS3900, BTS3900B,
and BTS3900E
Procedure
----End
1.
9.1 Configuring the 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
Issue 03 (2011-08-31)

32
BSC6900 GSM
9 Configuring a BTS
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 a Clock for a BTS

This section describes how to configure a clock for a BTS, including the configuration of
a clock source and a clock server required by an IP-based BTS.
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, and activate the BTS configuration.
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 03 (2011-08-31)

33
BSC6900 GSM
9 Configuring a BTS
9.1 Configuring the 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.
9.1.1 Configuring a BTS

This section describes how to configure data for a BTS.
Prerequisite
l
All types of base stations support the Time Division Multiplexing (TDM), High-Level Data
Link Control (HDLC), and Internet Protocol (IP) transmission schemes.
Idle ports are available on interface boards.
Separate mode indicates that boards and carriers that are configured for a BTS must be
configured separately.
Normalization mode indicates that the method for numbering slots, subracks, and cabinets
is normalized, the method for naming boards is normalized, the method for numbering
transmission ports is normalized, and the method for numbering ports reporting customized
alarms is normalized when multiple modes are supported at a base station.
Context
Procedure
Step 1 Run the ADD BTS command to add a BTS.
Table 9-1 Settings of key parameters
Parameter
Setting
BTS Name
A BTS name must not contain any of the

following symbols:
, (comma), ; (semicolon), " (double quotation
marks), ' (single quotation marks), =, %, \,
+, &, #
Separate Mode
For 3900 series base stations, this parameter

must be set to SUPPORT(Support).
For BTS3012, BTS3012II, and BTS3012AE,
this parameter is set to either SUPPORT
(Support) or UNSUPPORT(Not Support).
For 3x series base stations, this parameter
must be set to UNSUPPORT(Not
Support).
Is Support Normalized Data Configuration
Issue 03 (2011-08-31)
For SingleRAN base stations, this parameter

must be set to SUPPORT(Support).

34
BSC6900 GSM
9 Configuring a BTS
----End
9.1.2 Configuring BTS Cabinet

This section describes how to configure data for BTS cabinet.
Prerequisite
l
The BTS data are configured. For details, see 9.1.1 Configuring a BTS.
The boards in the common slots are automatically added according to the default setting.
Antenna boards and TRX boards need to be manually added.
Context
Procedure
Step 1 Run the ADD BTSCABINET command to add a cabinet to the base station.
NOTE
l For the numbering rule of base station equipment, see 10.3.1 Configuration Guidelines for Cabinet
Numbers.
l For the configuration rule of base station boards, see 10.3.4 Mapping Between Base Stations and
Optional Cabinets.
l When Is Support SingleRAN Mode is set to SUPPORT(Support SRAN), the SingleRAN base
stations can be configured.
----End
9.1.3 Configuring BTS Boards

This section describes how to configure data for boards installed at a BTS.
Prerequisite
l
Cabinets of the BTS have been configured. For details on how to configure a BTS cabinet,
see 9.1.2 Configuring BTS Cabinet.
Idle ports are available on interface boards.
The eXtensible Processing Unit REV:a (XPUa) has been configured. For details on how
to configure the XPUa board, see Configuring a Board.
Context
For the rule for configuring boards, see 10.3.3 Configuration Guidelines for Slot Numbers.
Some boards have been configured automatically together with cabinets. For details, see 10.3.5
Configuration Rules of the BTS Boards. For the rule for configuring radio frequency (RF)
modules, see 9.1.4 Configuring RF Units.
Procedure
Step 1 Run the ADD BTS command to add a board to a BTS.
Issue 03 (2011-08-31)

35
BSC6900 GSM
9 Configuring a BTS
l If a monitoring board is to be added, do as follows:

To configure Subrack No. and Slot No. for a monitoring board, see 10.3.6 Configuration
Guidelines for Monitoring Boards.
To configure other parameters for a monitoring board, see 9.6.3 Configuring Parameters
for Monitoring Boards.
l Board Type can be set to PTU(PTU) only when an IP interface board is added to a doubletransceiver base station.
----End
9.1.4 Configuring RF Units

This section describes how to configure data for TRX boards, and antenna boards.
Prerequisite
l
The BTS boards are configured. For details, see 9.1.3 Configuring BTS Boards.
3X series and double-transceiver series base stations
Context
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

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.
Procedure
Step 1 Add TRX boards to the base station.
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.
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).
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 BTS3900B.
2.
Run the ADD BTSRXUBRD command to add RXU boards.

l For the SingleRAN base stations, Cabinet No., Subrack No., and Subrack No. must
be configured.
l For the 3900 series base stations RF boards, see 10.3.5 Configuration Rules of the
BTS Boards.
l If Is Configure Check threshold is set to NO(NO), need set the bandwidth manually.
Issue 03 (2011-08-31)

36
BSC6900 GSM
9 Configuring a BTS
l RXU Specification must be specified. You can set this parameter based on the actual
hardware type of the RXU. For example, if the hardware type is RRU3029, set Board
Type to GRRU(GRRU) and RXU Specification to RRU3029(RRU3029 SPEC), and
if the hardware type is MRFU V3, set Board Type to MRFU(MRFU) and RXU
Specification to MRFU_V3(MRFU V3 SPEC).
3.
Run the SET BTSRXUBP command to set the sending receiving mode and working mode
of the RXU board.
l The GRRU/GRFU board supports only the GSM(GSM) working mode.
l The MRRU/MRFU board supports the GSM(GSM), UMTS(UMTS), and
GSM_AND_UMTS(GSM AND UMTS) working modes.
l TRX Send and receive modes, see 10.3.9 Guidelines for Configuring Send and
Receive Modes for RF Modules.
l If a site is configured with a TMA, you need to set the related TMA switch parameters.
Step 2 Optional: Run the ADD BTSANTFEEDERBRD command to add antenna boards to the base
station.
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.
The OPC data is configured. For details, see Configuring the OPC and DPC.
The equipment data of the BTS is configured. For details, see 9.1 Configuring the
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
Issue 03 (2011-08-31)
1.
Run the ADD GCELL command to add a cell.
2.
Run the ADD GCELLFREQ command to add frequencies to the cell.

37
BSC6900 GSM
9 Configuring a BTS
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.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.
Prerequisite
l
Equipment Data.
The logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
All types of BTSs support TDM/HDLC transmission.
The TDM/HDLC transmission networking, refer to 10.3.13 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 transmission data when the BTS is in IP over FE/GE
transmission mode.
Issue 03 (2011-08-31)

38
BSC6900 GSM
9 Configuring a BTS
Prerequisite
l
Equipment data of the BTS is configured. For details, see 9.1 Configuring the Equipment
Data.
Logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
Double-transceiver and 3900 series base stations support IP over FE/GE transmission.
For details about IP over FE/GE transmission networking, see 10.3.14 IP-Based
Networking on the Abis Interface.
Context
Procedure
Step 1 Optional: When the planned data is inconsistent with the database configuration data, run the
SET ETHPORT command to set attributes of the Ethernet port.
Step 2 Optional: Run the ADD ETHREDPORT command to add a backup Ethernet port.
Step 3 Optional: If the BSC6900 device IP address is required for communication, run the ADD
DEVIP command to add the device IP address of an Abis IP interface board.
Step 4 Run the ADD ETHIP command to add the port IP address of the Abis IP interface 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 on the BSC6900 side.
NOTE
If the global route management function is not required, run the SET GLOBALROUTESW command to turn
off the global route management switch.
Step 6 Run the MML command ADD BTSDEVIP to add an IP address to an Ethernet port of the BTS.
Step 7 Run the SET BTSIP command to set the IP address of the BTS.
Step 8 Run the SET BTSETHPORT command to set port attributes of the BTS.
Step 9 Optional: When the BSC6900 and the BTS are on different network segments, run the ADD
BTSIPRT command to add an IP route on the BTS side.
Step 10 Run the ADD BTSESN command to add the equipment serial number (ESN) of the BTS.
Step 11 Run the ADD ADJNODE command to add an adjacent node.
Step 12 Run the ADD IPPATH command to add an IP path. To add more IP paths, repeat this step.
Step 13 Optional: If the IP transmission efficiency over the Abis interface needs to be improved,
configure the Abis-MUX function by performing the following procedure:
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 14 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 by
performing the following procedure:
1.
Issue 03 (2011-08-31)
Run the ADD BTSBFD command to add a BFD session on the BTS side.
39
BSC6900 GSM
9 Configuring a BTS
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 15 Optional: If the service VLAN mapping over the Abis interface needs to be configured, perform
the following steps:
1.
Run the ADD IPPATH and SET BSCABISPRIMAP commands 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
Equipment Data.
The logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
Only the 3900 series base stations support IP over E1.
The IP over E1 transmission networking, refer to 10.3.14 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
If the E1/T1 link carries a/an ...
Then...
PPP link
Go to Step 3.
MLPPP group
Go to Step 4.

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.
Issue 03 (2011-08-31)
Run the ADD MPGRP command to add an MLPPP group.

40
BSC6900 GSM
9 Configuring a BTS
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.
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 a Clock for a BTS

This section describes how to configure a clock for a BTS, including the configuration of a clock
source and a clock server required by an IP-based BTS.
Prerequisite
Data of the BTS's equipment has been configured. For details, see 9.1 Configuring the
Equipment Data.
Context
For the rule for configuring a clock source for a BTS, see 10.3.11 Configuration Guidelines
for BTS Clock Sources. If TDM and IP over E1 are applied, TRCBSC_CLK(Trace BSC
Clock) is selected by default. If IP over FE is applied, IP_TIME(IP Clock) is selected by default.
Procedure
Step 1 Optional: To change the clock source for a BTS, run the SET BTSCLK command.
Step 2 Optional: To set a clock server for a BTS adopting the IP clock, run the SET
BTSIPCLKPARA command.
----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, and activate the BTS configuration.
Prerequisite
The BTS and its cells are already configured.
Issue 03 (2011-08-31)

41
BSC6900 GSM
9 Configuring a BTS
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.
----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, external LTE 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.
The cells in the BSC6900 can be set to bidirectional neighboring cells or unidirectional
neighboring cells.
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 GEXTLTECELL command to add a LTE external cell.
Step 4 Run the ADD G2GNCELL command to add a 2G neighboring cell for the specified originating
cell.
Step 5 Run the ADD G3GNCELL command to add a 3G neighboring cell for the specified originating
cell.
Step 6 Run the ADD GLTENCELL command to add a LTE 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 03 (2011-08-31)

42
BSC6900 GSM
9 Configuring a BTS
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.
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.
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.
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 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.
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.
l
Issue 03 (2011-08-31)
Configuring the BTS forbidden timeslots

43
BSC6900 GSM
1.
9 Configuring a BTS
Run the SET BTSFORBIDTS command to disable or enable the timeslots of a BTS.
----End
9.6.3 Configuring Parameters for Monitoring Boards

This section describes how to configure parameters for monitoring boards of a base station.
Monitoring units can monitor the temperature and environment condition of the equipment room.
Users can configure monitoring units according to the corresponding plan.
Prerequisite
l
For configuration details, see 9.1.3 Configuring BTS Boards.
Context
For the configuration rule of each monitoring board of a base station, see 10.3.6 Configuration
Guidelines for Monitoring Boards.
Procedure
l
Configuring parameters for an EMU

1.
Run the command SET BTSDEMUBP to set parameters for a DEMU or EMU.
Configuring parameters for a PMU

1.
Run the command SET BTSAPMUBP to set parameters for an AMPU or PMU.
Set Board Parameter Configuration Enabled to YES(YES).
For the configuration of the parameter Power System Type, see 10.3.7
Configuration Guidelines for Power Systems.
If a BBC or IBBS is configured at a base station, the following parameters should be
set:
Set Board Parameter Configuration Enabled to YES(YES).
Set Battery Type to VRLA_INNER_BAT(VRLA Inner Battery).
Set Battery Capacity according to the actual configured capacity.
CAUTION
You must configure Battery Capacity according to the required capacity.
Otherwise, Battery would be faulty.
l
Configuring parameters for an FMU

1.
Configuring parameters for a TCU

1.
Run the command SET BTSFMUABP to set parameters for an FMUA or FMU.
Run the command SET BTSDHEUBP to set parameters for a DHEU, DTCU, or
TCU.
Configuring parameters for a GATM

1.
Run the command SET BTSDATUBP to set parameters for a GATM.
----End
Issue 03 (2011-08-31)

44
BSC6900 GSM
9 Configuring a BTS
9.6.4 Configuring a Custom BTS Alarm

This section describes how to configure a custom BTS alarm. Custom alarms are defined to
allow the monitoring board of the BTS to monitor and report ambient environment such as
temperature and humidity.
Prerequisite
l
The monitoring board and the required cables are installed. For details, see the Hardware
Description of the base station.
The monitoring board is configured. For details, see 9.1.3 Configuring BTS Boards.
The parameters related to the monitoring board are set. For details, see 10.3.6
Configuration Guidelines for Monitoring Boards.
Context
Table 9-2 lists the data to be negotiated and planned for configuring a custom BTS alarm.
Table 9-2 Data to be negotiated and planned for configuring custom BTS alarms
Parameter
Category
Parameter Name
Example
Source
Basic Information
BTS Name
BTS01
Network planning
Cabinet No.
Network planning
Subrack No.
Network planning
Slot No.
40
Network planning
Switch
OPEN
Network planning
Port No.
Network planning
Port Type
BOOL
Network planning
Alarm VOL.
HIGH
Network planning
Alarm ID.
65133
Network planning
Alarm Name
Smoke alarm
Network planning
Alarm Severity
Critical
Network planning
Event Type
env
Network planning
Port No.
32
Network planning
Port Type
VALUE
Network planning
Alarm ID.
65366
Network planning
Upper Limit
30000
Network planning
Lower Limit
2000
Network planning
Digit Port
Analog Port
Issue 03 (2011-08-31)

45
BSC6900 GSM
9 Configuring a BTS
Parameter
Category
Parameter Name
Example
Source
Sensor Type
CURRENT
Network planning
Measure Upper
Limit Of Sensor
30000
Network planning
Measure Lower
Limit Of Sensor
Network planning
Upper Limit Of
Sensor Output
2000
Network planning
Lower Limit Of
Sensor Output
400
Network planning
Alarm Name
Oil Level Alarm
Network planning
Procedure
Step 1 Run the MML command SET BTSENVALMPORT to set the alarm port of BTS environment
alarms.
l The setting of Subrack No. differs by objects. For example, the value for PMU is 7, 8 for
TCU, 4-50 for EMU, and 11 for FMU.
l Port No. is the port number of a custom alarm. Port No. must map Port on the Monitoring
Unit. For details, see 10.3.8 List of User-Defined Alarm Ports.
l Switch is OPEN(Open).
l For the EMU:
Port on the Monitoring Unit is the port for monitoring Boolean signals. Port Type is
BOOL(Digital Port).
Port on the Monitoring Unit is the port for monitoring analog signals. Port Type is
VALUE(Analog Port).
l A unique alarm ID is assigned to each environment alarm.
The effective environment Alarm ID range of SingleRAN base stations is
65033-65233.
The effective environment Alarm ID range of non-SingleRAN base stations is
65384-65533.
Step 2 Run the MML command SET ENVALMPARA to set the name and severity of a custom alarm.
l Alarm ID must be the same as that set in SET BTSENVALMPORT.
----End
9.6.5 Configuring BTS Power Alarms

This section describes how to configure BTS power alarms. After the BTS power alarms are
configured, the BTS will not be reset or report GSM cell out-of-service alarms repeatedly when
the mains supply is unavailable.
Issue 03 (2011-08-31)

46
BSC6900 GSM
9 Configuring a BTS
Prerequisite
l
A third-party power system is used, and batteries are used when the mains supply is
unavailable.
The customized alarms, "No Mains Supply" and "DC Low Voltage", are configured. For
details, see 9.6.4 Configuring a Custom BTS Alarm.
The alarms "No Mains Supply" and "DC Low Voltage" can be configured only on
customized alarm ports on the UPEU and UEIU.
A BBU cabinet with a +24 V power supply does not support the function.
Context
When a third-party power system is used, the "No Mains Supply" alarm can be correlated with
the "DC Low Voltage" alarm by configuring BTS power alarms. This prevents the BTS from
being reset or reporting GSM cell out-of-service alarms repeatedly.
Table 9-3 lists the data to be negotiated and planned for configuring BTS power alarms.
Table 9-3 Data to be negotiated and planned for configuring BTS power alarms
Parameter
Example
Source
BTS Name
BTS3900_IP
Network planning
Alarm Parameter
Configuration Enabled
YES
Network planning
No Mains Supply Alarm

Cabinet No.
Network planning
No Mains Supply Alarm

Subrack No.
40
Network planning
No Mains Supply Alarm Slot

No.
Network planning
No Mains Supply Alarm Port

No.
Network planning
DC Low Voltage Alarm

Cabinet No.
Network planning
DC Low Voltage Alarm

Subrack No.
40
Network planning
DC Low Voltage Alarm Slot

No.
Network planning
DC Low Voltage Alarm Port

No.
Network planning
Procedure
Step 1 Run the MML command SET BTSALMPORT to set the BTS ports for the "No Mains Supply"
alarm and the "DC Low Voltage" alarm.
Issue 03 (2011-08-31)

47
BSC6900 GSM
9 Configuring a BTS
l The cabinet number, subrack number, slot number, and port number for the "No Mains
Supply" alarm and the "DC Low Voltage" alarm must be consistent with those configured
for customized alarms.
----End
9.6.6 Configuring IP Port Backup

This section describes how to configure IP port backup of the BTS. The IP port backup function
enables services to be quickly switched to the other port when one port fails. This improves
transmission reliability.
Prerequisite
l
The equipment data of the BTS has been configured. For details, see 9.1 Configuring the
Equipment Data.
The logical data of the BTS has been configured. For details, see 9.2 Configuring the
Logical Data.
IP over FE/GE has been configured for the BTS and the BTS communication type has been
set to logical IP. For details, see 9.3.2 IP over FE/GE.
Context
The BTS has two FE ports, which are configured with IP addresses on different network
segments. Address Resolution Protocol (ARP) detection is used to check the status of the two
transmission links on the two FE ports. If the transmission on one FE port is interrupted, the
BTS transmits data on the transmission link of the other port. IP port backup adopts layer 3
networking in IP over FE mode, as shown in Figure 9-1.
Figure 9-1 IP port backup networking
CAUTION
ARP detection and single-hop Bidirectional Forwarding Detection (BFD) cannot be used
together. If BFD sessions need to be configured during transmission configurations, only multihop BFD can be configured.
Procedure
Step 1 Run the MML command ADD BTSDEVIP to add an IP address for the idle FE port of the BTS.
Issue 03 (2011-08-31)

48
BSC6900 GSM
9 Configuring a BTS
NOTE
The other FE port of the BTS has been configured during IP over FE/GE configuration. You can run the LST
BTSDEVIP command to query the number of the configured FE port.
Step 2 Run the MML command ADD BTSIPRT to add a route from the BTS to the BSC6900.
NOTE
Different priorities need to be set for this route and the route that is configured during IP over FE/GE
configuration. You can run the MML command DSP BTSIPRT to query the priority of the route configured
for IP over FE/GE transmission.
Step 3 Run the MML command ADD BTSARPSESSION to add an uplink ARP session for the BTS
with Route Associated set to YES.
NOTE
ARP sessions need to be configured between the BTS and the next hop IP addresses of the two FE ports.
----End
9.6.7 Configuring Connection of Monitoring Devices Through IP

Ports
This section describes how to configure connection of monitoring devices through IP ports.
Prerequisite
l
The equipment data of the BTS has been configured. For details, see 9.1 Configuring the
Equipment Data.
The logical data of the BTS has been configured. For details, see 9.2 Configuring the
Logical Data.
IP over FE/GE or IP over E1 has been configured for the BTS. For details, see 9.3.2 IP
over FE/GE and 9.3.3 IP over E1.
Context
An external monitoring device is used to monitor the ambient environment of the equipment
room. Connection of monitoring devices through IP ports is implemented by connecting an
Ethernet port on an external monitoring device to an FE port on the GTMU. In this manner, the
BTS can transmit the monitoring data to the maintenance terminal of the monitoring device on
the IP transport network for processing.
The transmission port on the BTS can be an FE or E1/T1 port, depending on the configured
transmission mode. The maintenance terminal of the monitoring device can be connected to the
IP transport network directly or through the BSC. In the latter case, the BSC forwards the
monitoring data from the BTS to the maintenance terminal.
Figure 9-2 shows the IP access networking adopted when the maintenance terminal of the
monitoring device is directly connected to the IP transport network.
Issue 03 (2011-08-31)

49
BSC6900 GSM
9 Configuring a BTS
Figure 9-2 IP access networking of monitoring devices
Procedure
Step 1 Run the MML command ADD BTSDEVIP to add an IP address for the BTS FE port that
connects to the monitoring device.
NOTE
The IP address of the BTS FE port and the IP address of the monitoring device must be on the same network
segment.
Step 2 Optional: If the BTS and the maintenance terminal of the monitoring device are on different
network segments, run the MML command ADD BTSIPRT to add an IP route from the BTS
to the maintenance terminal of the monitoring device.
Step 3 Optional: If the status of the transmission between the BTS and the monitoring device needs to
be checked, run the MML command ADD BTSARPSESSION to add an ARP session between
the BTS and the monitoring device with Route Associated set to NO.
Step 4 Optional: If monitoring data needs to be forwarded by the BSC6900, run the MML command
ADD IPRT to add an IP route from the BSC6900 to the maintenance terminal of the monitoring
device.
NOTE
l Routes must be configured between the monitoring device and its maintenance terminal for uplink and
downlink data transmission.
l If the BTS and the maintenance terminal of the monitoring device are on different network segments, a route
from the maintenance terminal to the BTS must be configured.
----End
9.7 Configuration in the Typical Scenario

This section provides BTS configuration examples in the typical scenario.
9.7.1 Typical BTS3900 Configuration

This section describes BTS3900 configuration examples in typical scenarios. The contents of
this section include configuration scenarios, monitoring principles, data planning, and task
examples.
Issue 03 (2011-08-31)

50
BSC6900 GSM
9 Configuring a BTS
Prerequisite
l
BSC6900 global data and equipment data has been configured.
Context
The BTS3900 and BSC6900 communicate with each other through the SDH or PDH network.
The BTS3900 and BSC6900 are connected through E1/T1 ports on the GTMU and PEUa, as
shown in Figure 9-3.
Figure 9-3 IP over E1 networking
When a single site is configured with two BTS3900s (-48V DC), monitoring principles and cable
connections are shown in Figure 9-4.
Figure 9-4 BTS3900 (-48V DC) monitoring principles and cable connections
Data Planning
The equipment data that requires negotiation and planning is listed in Table 9-4:
Table 9-4 Equipment Data
Parameter
BTS
Issue 03 (2011-08-31)
BTS Index
Example
Data Source
Internal planning

51
BSC6900 GSM
9 Configuring a BTS
Parameter
Cabinet
Example
BTS Name
BTS3900_8
BTS Type
BTS3900_GSM
Seperate
Mode
SUPPORT
Service
Type
IP
IP Phy
Trans Type
IP_OVER_E1
Is Support
Normalize
d Data
Configurati
on
SUPPORT
Work
Mode
E1
Negotiation with the peer
Cabinet
No.
0, 1
Internal planning
Is Support
SingleRA
N Mode
SUPPORT
Cabinet
Type
Cabinet
No.
Board
Physical
TRX
Issue 03 (2011-08-31)
Data Source
Network planning
Network planning
BTS3900
Subrack
No.
50, 51
Slot No.
Board Type
GATM
Chain No.
Topo Type
CHAIN
Head
Cabinet
No.
Head
Subrack
No.
Head Slot
No.
Internal planning
Network planning
Internal planning

52
BSC6900 GSM
9 Configuring a BTS
Parameter
Example
Head Port
No.
Board Type
DRFU
Cabinet
No.
Subrack
No.
Slot No.
RXU Name
kkk
RXU Chain
No.
RXU
Board
Position
Data Source
Network planning
Internal planning
The logical data that requires negotiation and planning is listed in Table 9-5:
Table 9-5 Logical Data
Parameter
Cell
Basic
Informati
on
TRX
Informati
on
Issue 03 (2011-08-31)
Example
Cell Index
Cell Name
cell-8
Freq. Band
DCS1800
MCC
460
MNC
01
Cell LAC
H'0001
Cell CI
Frequency
1
520
OSP Code
163
TRX ID
Frequency
520
TRX No.
0, 1

Data Source
Network planning
Network planning
Network planning
53
BSC6900 GSM
9 Configuring a BTS
Parameter
Binding
relation
between
the
logical
TRX and
the
physical
TRX
board
Example
Channel
Type
MBCCH, SDCCH8
Timeslot
Priority
1, 2
TRX Board
Pass No.
RXU Index
Type
Data Source
0
RXUNAME
Network planning
The transmission data that requires negotiation and planning is listed in Table 9-6.
Table 9-6 Transmission Data (IP over E1)
Parameter
Example
BTS In Port
No.
BTS
Connecti
on
PPP links
of BSC
side
Issue 03 (2011-08-31)
Data Source
In Port
Cabinet No.
In Port
Subrack
No.
In Port Slot
No.
Dest Node
Type
BSC
Subrack
No.
Slot No.
26
Port No.
Subrack
No.
Slot No.
26
Board type
PEUa

Network planning
Internal planning
54
BSC6900 GSM
9 Configuring a BTS
Parameter
Example
Logic
function
type
PPP link
No.
E1T1 port
No.
Bearing
time slot
Borrow
DevIP
Local IP
address
PPP links
of BTS
side
Issue 03 (2011-08-31)
Abis_IP
0
0
TS1-1&TS2-1&TS3-1&TS4-1
&TS5-1&TS6-1&TS7-1&TS8
-1&TS9-1&TS10-1&TS11-1
&TS12-1&TS13-1&TS14-1&
TS15-1
Internal planning
NO
9.69.200.1
Subnet
mask
255.255.255.0
Peer IP
address
9.69.200.192
PPP Link
No.
Port No.
Port
Cabinet No.
Port
Subrack
No.
Port Slot
No.
Network planning
Internal planning
Bearing
Time Slot
TS1-1&TS2-1&TS3-1&TS4-1
&TS5-1&TS6-1&TS7-1&TS8
-1&TS9-1&TS10-1&TS11-1
&TS12-1&TS13-1&TS14-1&
TS15-1
Local IP
Address
9.69.200.192
Subnet
Mask
Data Source
255.255.255.0

Network planning
55
BSC6900 GSM
9 Configuring a BTS
Parameter
BTS
Equipme
nt Serial
Number
Example
Peer IP
Address
9.69.200.1
BTS
Interface
Board Bar
Code 1
21021127226T93020663
Adjacent
Node ID
Adjacent
Node
BTS IP
IP path
Data Source
Adjacent
Node Name
IP
Adjacent
Node Type
ABIS
Site Index
BTS
Communic
ation Type
PPP/MP
BTS IP
9.69.200.192
BSC IP
9.69.200.1
IP path ID
Interface
Type
ABIS
IP path type
EF
Forward
Bandwidth
1000
Backward
Bandwidth
Internal planning
Internal planning
Network planning
Network planning
1000
The parameters of monitoring boards that require negotiation and planning are listed in Table
9-7.
Table 9-7 Monitoring Board Parameter
Issue 03 (2011-08-31)
Board
Name
Cabinet
Number
Subrack
Number
Slot
Number
Manager
Port
Number
Communic
ation
Address
FMU
11
14
FMU
11
15

56
BSC6900 GSM
9 Configuring a BTS
Board
Name
Cabinet
Number
Subrack
Number
Slot
Number
Manager
Port
Number
Communic
ation
Address
GATM
50
22
GATM
51
22
EMU
40
BTS user-defined alarms that require negotiation and planning are listed in Table 9-8:
Table 9-8 BTS User-Defined Alarm
Alarm ID
Alarm
Name
Alar
m
Seve
rity
Event
Type
Ca
bi
net
No
.
Su
bra
ck
No
.
Slo
t
No
.
Port
No.
Swit
ch
Port
Typ
e
Alar
m
VO
L
65033
Water
Alarm
Criti
cal
env
40
OPE
N
BOO
L
HIG
H
65034
Smoke
Alarm
Criti
cal
env
40
OPE
N
BOO
L
HIG
H
65035
Ambie
nt
Temper
ature
Abnor
mal
Criti
cal
env
11
OPE
N
BOO
L
HIG
H
65036
Ambie
nt
Temper
ature
Abnor
mal
Criti
cal
env
11
OPE
N
BOO
L
HIG
H
Example
//Adding a BTS and a cabinet
ADD BTS: BTSID=8, BTSNAME="BTS3900_8", BTSTYPE=BTS3900_GSM,
SEPERATEMODE=SUPPORT, SERVICEMODE=IP, IPPHYTRANSTYPE=IP_OVER_E1,
SRANMODE=SUPPORT, WORKMODE=E1;
ADD BTSCABINET: IDTYPE=BYID, BTSID=8, CN=0, SRANMODE=SUPPORT,
TYPE=BTS3900;
TYPE=BTS3900;
//Adding a BTS board
ADD BTSBRD: IDTYPE=BYID, BTSID=8, CN=0, SRN=50, SN=0, BT=GATM;
Issue 03 (2011-08-31)

57
BSC6900 GSM
ADD
ADD
ADD
ADD
BTSBRD:
BTSBRD:
BTSBRD:
BTSBRD:
9 Configuring a BTS
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
IDTYPE=BYID,
BTSID=8,
BTSID=8,
BTSID=8,
BTSID=8,
//Configuring parameters of
SET BTSDATUBP: IDTYPE=BYID,
MPN=0, ADDR=22;
MPN=1, ADDR=22;
SET BTSDEMUBP: IDTYPE=BYID,
MPN=1, ADDR=2;
SET BTSFMUABP: IDTYPE=BYID,
MPN=0, ADDR=14;
MPN=0, ADDR=15;
CN=0,
CN=0,
CN=1,
CN=0,
SRN=51,
SRN=11,
SRN=11,
SRN=40,
SN=0,
SN=0,
SN=0,
SN=0,
BT=GATM;
BT=FMU;
BT=FMU;
BT=EMU;
a DATU/DATM/GATM board
BTSID=8, CN=0, SRN=50, SN=0, CFGFLAG=YES,
//Adding an RXU chain or ring

ADD BTSRXUCHAIN: IDTYPE=BYID, BTSID=8, RCN=0, TT=CHAIN, HCN=0, HSRN=0,
HSN=6, HPN=0;
ADD BTSRXUBRD: IDTYPE=BYID, BTSID=8, BT=DRFU, CN=0, SRN=4, SN=0,
RXUNAME="kkk", RXUCHAINNO=0, RXUPOS=1;
//Adding data to GSM internal cells
ADD GCELL:CELLID=8,CELLNAME="cell-8", TYPE=DCS1800, MCC="460", MNC="01",
LAC=H'0001, CI=1;
ADD GCELLFREQ: IDTYPE=BYID,CELLID=8, FREQ1=520;
ADD GCELLOSPMAP: IDTYPE=BYID, CELLID=8, OPC=163;
//Adding a TRX
ADD GTRX: IDTYPE=BYID,CELLID=8,TRXID=8, FREQ=520;
SET GTRXCHAN: TRXID=8, CHNO=0,CHTYPE=MBCCH, TSPRIORITY=1;
SET GTRXCHAN: TRXID=8, CHNO=1, CHTYPE=SDCCH8, TSPRIORITY=2;
//Adding a cell to a BTS
ADD CELLBIND2BTS: IDTYPE=BYID,CELLID=8,BTSID=8;
//Adding binding between logic TRX and channel on TRX board
ADD TRXBIND2PHYBRD: TRXID=8, TRXTP=DRFU, TRXPN=0, RXUIDTYPE=RXUNAME,
RXUNAME="kkk";
//Adding a connection between the BTS and the BSC6900
ADD BTSCONNECT: IDTYPE=BYID, BTSID=8, INPN=0, INCN=0, INSRN=0, INSN=6,
DESTNODE=BSC, SRN=0, SN=26, PN=0;
// Adding a PPP link
ADD PPPLNK: SRN=0, SN=26, BRDTYPE=PEUa, LGCAPPTYPE=Abis_IP, PPPLNKN=0,
DS1=0,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1
1-1&TS12-1&TS13-1&TS14-1&TS15-1, BORROWDEVIP=No, LOCALIP="9.69.200.1",
MASK="255.255.255.0", PEERIP="9.69.200.192", AUTHTYPE=NO_V,
FLOWCTRLSWITCH=ON;
// Adding a PPP link on a BTS in IP over E1 transmission mode
ADD BTSPPPLNK: IDTYPE=BYID, BTSID=8, PPPLNKN=0, PN=0, CN=0, SRN=0,
SN=6,TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS101&TS11-1&TS12-1&TS13-1&TS14-1&TS15-1, LOCALIP="9.69.200.192",
MASK="255.255.255.0", PEERIP="9.69.200.1";
//Adding an adjacent node
ADD ADJNODE: ANI=0, NAME="IP", NODET=ABIS, BTSID=8;
Issue 03 (2011-08-31)

58
BSC6900 GSM
9 Configuring a BTS
//Setting the communication address of a BTS that uses the IP transmission

mode
SET BTSIP: IDTYPE=BYID, BTSID=8, BTSCOMTYPE=PPP/MP, BTSIP="9.69.200.192",
BSCIP="9.69.200.1";
//Adding an equipment serial number (ESN) to response to the DHCP request
from the BTS
ADD BTSESN: IDTYPE=BYID, BTSID=8,MAINDEVTAB="21021127226T93020663";
// Adding an IP path
ADD IPPATH: ANI=0, PATHID=0, ITFT=ABIS, PATHT=EF, TXBW=100000,
RXBW=100000, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Activating a BTS
ACT BTS:IDTYPE=BYID, BTSID=8;
//Setting the alarm port of the BTS environment alarms
SET BTSENVALMPORT: IDTYPE=BYID, BTSID=8, CN=0, SRN=40, SN=0, PN=0,
SW=OPEN, AID=65033, PT=BOOL, AVOL=HIGH;
SET ENVALMPARA: AID=65033, ANM="Water Alarm", ALVL=Critical, ASS=env;
SET ENVALMPARA: AID=65034, ANM="Smoke Alarm", ALVL=Critical, ASS=env;
SET ENVALMPARA: AID=65035, ANM="Ambient Temperature Abnormal",
ALVL=Critical, ASS=env;
9.7.2 Typical BTS3900A Configuration

This section describes BTS3900A configuration examples in typical scenarios. The contents of
this section include configuration scenarios, monitoring principles, data planning, and task
examples.
Prerequisite
l
BSC6900 global data and equipment data has been configured.
Context
The BTS3900A and BSC6900 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 BTS3900A and BSC6900 are connected through FE/GE ports on the GTMU and
FG2a, as shown in Figure 9-5.
Figure 9-5 IP over FE/GE networking
Issue 03 (2011-08-31)

59
BSC6900 GSM
9 Configuring a BTS
In the typical scenario, 1 APM30H, 1 RFC, 2 IBBS200D/IBBS200T, and 1 TMC11H are

configured at the BTS3900A (110V/220V AC). Monitoring principles and cable connections
are shown in Figure 9-6.
Figure 9-6 BTS3900A (110V/220V AC) Monitoring Principles
Data Planning
The equipment data that requires negotiation and planning is listed in Table 9-9:
Table 9-9 Equipment Data
Parameter
BTS
Issue 03 (2011-08-31)
Example
BTS Index
BTS Name
BTS3900A_9
BTS Type
BTS3900A_GSM
Seperate
Mode
SUPPORT
Service
Type
IP
Data Source
Internal planning
Network planning

60
BSC6900 GSM
9 Configuring a BTS
Parameter
Cabinet
Board
Physical
TRX
Issue 03 (2011-08-31)
Example
Data Source
IP Phy
Trans Type
IP_OVER_E1
Is Support
Normalize
d Data
Configurati
on
SUPPORT
Work
Mode
E1
Cabinet
No.
0, 1, 2, 3, 4
Internal planning
Is Support
SingleRA
N Mode
SUPPORT
Cabinet
Type
APM30, RFC-6, TMC, BBC,

BBC,
Cabinet
No.
Network planning
Subrack
No.
Slot No.
1, 2, 3
Board Type
PSU
Chain No.
Topo Type
CHAIN
Head
Cabinet
No.
Head
Subrack
No.
Head Slot
No.
Head Port
No.
Board Type
DRFU
Cabinet
No.

Internal planning
Network planning
Internal planning
Network planning
61
BSC6900 GSM
9 Configuring a BTS
Parameter
Example
Subrack
No.
Slot No.
0, 1
RXU Name
drfu0, drfu1
RXU Chain
No.
RXU
Board
Position
1, 2
Data Source
Internal planning
The logical data that requires negotiation and planning is listed in Table 9-10:
Table 9-10 Logical Data
Parameter
Cell
Basic
Informati
on
TRX
Informati
on
Binding
relation
between
the
Issue 03 (2011-08-31)
Example
Cell Index
5, 6
Cell Name
cell-11, cell-22
Freq. Band
DCS1800
MCC
460
MNC
164
Cell LAC
Cell CI
1, 2
Frequency
1
513, 517
Frequency
2
515, 519
OSP Code
163
TRX ID
9, 10, 11, 12
Frequency
513, 515, 517, 519
Is Main
BCCH
TRX
YES, NO, YES, NO
TRX ID
9, 10, 11, 12
TRX Board
Pass No.
0, 1, 0, 1

Data Source
Network planning
Network planning
Network planning
Network planning
62
BSC6900 GSM
9 Configuring a BTS
Parameter
logical
TRX and
the
physical
TRX
board
Example
RXU Index
Type
RXUNAME
RXU Name
drfu0, drfu1, drfu0, drfu1
Data Source
The transmission data that requires negotiation and planning is listed in Table 9-11:
Table 9-11 Transmission Data (IP over FE)
Parameter
IP
address of
an
Ethernet
port
IP
address
and
informati
on of an
Ethernet
Port on a
BTS
BTS IP
Issue 03 (2011-08-31)
Example
Port No.
Subrack
Number
Slot
Number
19
Local IP
address
166.101.121.220
Subnet
mask
255.255.0.0
Port No.
Port
Cabinet No.
Subrack
No.
Slot No.
Physical IP
203.26.0.5
IP Mask
255.255.255.0
MTU
1500
BTS
Communic
ation Type
PORTIP
BTS IP
203.26.0.5
BSC IP
203.26.0.1
Data Source
Internal planning
Network planning
Internal planning
Network planning
Network planning

63
BSC6900 GSM
9 Configuring a BTS
Parameter
BTS
Equipme
nt Serial
Number
BTS
Interface
Board Bar
Code 1
Adjacent
Node ID
Adjacent
Node
IP path
Example
Data Source
1000000000000000
Internal planning
Adjacent
Node Name
BTS3900A_9
Adjacent
Node Type
ABIS
Site Index
IP path ID
Interface
Type
ABIS
IP path type
EF
Forward
Bandwidth
1000
Backward
Bandwidth
1000
Internal planning
Network planning
BTS clock data that requires negotiation and planning is listed in Table 9-12:
Table 9-12 BTS Clock
Parameter
Example
Clock
Protocol
Type
BTS IP
Clock
Server
Issue 03 (2011-08-31)
Data Source
HW_DEFINED
Clock
Reference
Source
Redundanc
y
UNSUPPORT
Clock
Server 0 IP
Address
16.16.16.50
Clock
Synchroniz
ation Mode
CONSYN
Network planning

64
BSC6900 GSM
9 Configuring a BTS
The parameters of monitoring boards that require negotiation and planning are listed in Table
9-13:
Table 9-13 Monitoring Boards
Board
Name
Cabinet
Number
Subrack
Number
Slot
Number
Manager
Port
Number
Communic
ation
Address
PMU
TCU
TCU
TCU
23
TCU
24
FMU
11
14
GATM
50
22
GATM
51
22
BTS user-defined alarms that require negotiation and planning are listed in Table 9-14:
Table 9-14 BTS User-Defined Alarm
Alarm ID
Alarm
Name
Alar
m
Seve
rity
Event
Type
Ca
bi
net
No
.
Su
bra
ck
No
.
Slo
t
No
.
Port
No.
Swit
ch
Port
Typ
e
Alar
m
VO
L
65033
Ambie
nt
Temper
ature
Abnor
mal
Criti
cal
env
OPE
N
BOO
L
HIG
H
Example
//Adding a BTS and a cabinet
ADD BTS: BTSID=9, BTSNAME="BTS3900A_9", BTSTYPE=BTS3900A_GSM,
BTSDESC="3900A", SEPERATEMODE=SUPPORT,
SERVICEMODE=IP, SRANMODE=SUPPORT;
CABINETDESC="IBBS";
CABINETDESC="IBBS";
Issue 03 (2011-08-31)

TYPE=APM30;
TYPE=TMC;
TYPE=BBC,
TYPE=BBC,
65
BSC6900 GSM
9 Configuring a BTS
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=1, SRANMODE=SUPPORT, TYPE=RFC-6;

//Adding a BTS board
ADD BTSBRD: IDTYPE=BYID,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
BTSID=9,
//Configuring parameters of
SET BTSAPMUBP: IDTYPE=BYID,
MPN=1, ADDR=3;
SET BTSDHEUBP: IDTYPE=BYID,
MPN=1, ADDR=7;
MPN=0, ADDR=6;
MPN=1, ADDR=23;
MPN=1, ADDR=24;
MPN=0, ADDR=14;
MPN=0, ADDR=22;
MPN=1, ADDR=22;
CN=0,
CN=0,
CN=0,
CN=0,
CN=0,
CN=0,
CN=0,
CN=2,
CN=3,
CN=4,
CN=1,
SRN=7, SN=0, BT=PMU;

SRN=7, SN=1, BT=PSU;
SRN=8, SN=0, BT=TCU;
SRN=50, SN=0, BT=GATM;
SRN=51, SN=0, BT=GATM;
SRN=11, SN=0, BT=FMU;
a DATU/DATM/GATM board
//Adding an RXU chain or ring

ADD BTSRXUCHAIN: IDTYPE=BYID, BTSID=9, RCN=0, TT=CHAIN, HCN=0, HSRN=0,
HSN=6, HPN=0;
RXUNAME="drfu0", RXUCHAINNO=0, RXUPOS=1;
RXUNAME="drfu1", RXUCHAINNO=0, RXUPOS=2;
//Adding data to GSM internal cells
ADD GCELL:CELLID=5,CELLNAME="cell-11", TYPE=DCS1800, MCC="460",
MNC="164", LAC=6, CI=1;
ADD GCELL:CELLID=6,CELLNAME="cell-22", TYPE=DCS1800, MCC="460",
MNC="164", LAC=6, CI=2;
ADD GCELLFREQ: IDTYPE=BYID,CELLID=5, FREQ1=513,FREQ2=515;
ADD GCELLFREQ: IDTYPE=BYID,CELLID=6, FREQ1=517,FREQ2=519;
// Adding the mapping between a cell and an originating signaling point
(OSP)
//Adding a TRX
ADD GTRX: IDTYPE=BYID,CELLID=5,TRXID=9, FREQ=513,ISMAINBCCH=YES;
ADD GTRX: IDTYPE=BYID,CELLID=6,TRXID=11, FREQ=517,ISMAINBCCH=YES;
//Adding a cell to a BTS
Issue 03 (2011-08-31)

66
BSC6900 GSM
9 Configuring a BTS

//Adding binding between logic TRX and channel on TRX board
RXUNAME=" drfu0";
ADD TRXBIND2PHYBRD: TRXID=10, TRXTP= DRFU, TRXPN=1, RXUIDTYPE=RXUNAME,
RXUNAME=" drfu0";
ADD TRXBIND2PHYBRD: TRXID=11, TRXTP= DRFU, TRXPN=0, RXUIDTYPE=RXUNAME,
RXUNAME=" drfu1";
RXUNAME=" drfu1";
//Configuring transmission data when the IP over FE/GE transmission mode
is used
ADD ETHIP:SRN=0, SN=19, PN=1, IPINDEX=0, IPADDR="166.101.121.220",
MASK="255.255.0.0";
ADD BTSDEVIP: IDTYPE=BYID, BTSID=9, PN=0, CN=0, SRN=0, SN=6,
IP="203.26.0.5", MASK="255.255.255.0";
SET BTSIP: IDTYPE=BYID, BTSID=9, BTSCOMTYPE=PORTIP, BTSIP="203.26.0.5",
BSCIP="203.26.0.1";
SET BTSETHPORT: IDTYPE=BYID, BTSID=9, PN=0, CN=0, SRN=0, SN=6, MTU=1500;
ADD BTSESN: IDTYPE=BYID, BTSID=9, MAINDEVTAB="1000000000000000";
ADD ADJNODE: ANI=0, NAME="BTS3900A_9", NODET=ABIS, BTSID=9;
ADD IPPATH:ANI=0, PATHID=0, ITFT=ABIS, PATHT=EF, TXBW=100000,
RXBW=100000, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Setting parameters of the IP clock server
SET BTSIPCLKPARA: IDTYPE=BYID, BTSID=9, CLKPRTTYPE=HW_DEFINED,
ISCLKREDUCY=UNSUPPORT, MASTERIPADDR="16.16.16.50",SYNMODE=CONSYN;
//Activating a BTS
ACT BTS:IDTYPE=BYID, BTSID=9;
//Setting the alarm port of the BTS environment alarms
SW=OPEN, AID=65033, PT=BOOL, AVOL=LOW;
Issue 03 (2011-08-31)

67
BSC6900 GSM
10
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
BSC6900 interfaces.
10.3 Configuration Guidelines for the GBTS
This section describes the configuration rules and reference information related to a base station.
10.4 Data Configuration Guidelines for Specifications
This document describes the specifications of the BSC6900.
Issue 03 (2011-08-31)

68
BSC6900 GSM
10.1 Data Configuration Principles for Equipment

BSC6900 equipment.
10.1.1 Configuration Rules of the Cabinets

This section describes the configuration rules for 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).
The MPR is configured by default. You cannot add or remove this cabinet by running the
MML command.
If a TCS is configured in the local cabinet, the remote TCR cannot be configured.
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

BSC6900 subracks.
The configuration rules of the BSC6900 subracks are as follows:
l
The Main Processing Subrack (MPS) is configured by default. You do not need to add this
subrack by running the MML command.
Before adding a subrack, ensure that the cabinet to which the subrack is added exists, and
that the MPS works properly.
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.
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.
After a subrack is added, run the MML command to enable the corresponding port on the
SCU board in the MPS.
The relationship between Subrack No. and Cabinet No. is determined as follows: Cabinet
No. equals the quotient of Subrack No. divided by three.
10.1.3 Configuration Rules of the Boards

BSC6900 boards.
Classification of Boards
Table 10-1 provides the classification of the BSC6900 boards.
Issue 03 (2011-08-31)

69
BSC6900 GSM
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)
DPUd/DPUg
GPCU
XPUa/XPUb
GCP
RGCP
MCP
TDM switching Network

Unit (TNU)
TNUa
TDM_Switching
Operation and Maintenance

Unit (OMU)
OMUa/OMUb/OMUc
OAM
Service Aware Unit (SAU)
SAUa/SAUc
SAU
Functions of boards
The BSC6900 boards provide different functions when being loaded with different software, as
described in Table 10-2.
Issue 03 (2011-08-31)

70
BSC6900 GSM
Table 10-2 Functions of boards
Issue 03 (2011-08-31)
Logical Function Type
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
Interference-based channel allocation
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
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

71
BSC6900 GSM
NOTE
l It is recommended that the services of the boards in each subrack be controlled by the MPU subsystem
in the same subrack to avoid a large data flow transmitted between subracks.
l At least one XPUb board out of every three pairs of XPUb boards must be of the RGCP type. It is
recommended that you configure one XPUb board of the RGCP type out of every two pairs of
XXPUb boards.
l It is recommended that service processing boards and interface boards be evenly distributed in each
subrack to reduce data exchanging between subracks.
l It is recommended that interface boards, XPU boards, and DPU boards be evenly distributed in each
subrack.
10.1.4 Configuration Rules of the Clock

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.
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.
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.
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.
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.
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) in the EPS and then sent to the GCUa/GCGa 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/GCGa 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-1.5MBPS, or BITS2-1.5MBPS.
If the clock signals are provided by the GPS and then sent to the GCGa board, Clock
source type should be set to GPS.
If the clock signals are provided by the external 8 kHz clock, Clock source type should
be set to 8KHZ.
Issue 03 (2011-08-31)

72
BSC6900 GSM
10.1.5 Introduction to Time Synchronization

The time synchronization function enables the time synchronization of the nodes of the GBSS
system.
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 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 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 Daylight
Saving Time (DST). If DST is set, you need to configure the start date/time and end date/time
of DST and the time offset.
10.2 Data Configuration Principles for Interfaces

BSC6900 interfaces.
10.2.1 Data Configuration Principles for the A Interface

The A interface is a standard interface between the BSS and the MSC. It supports 64 kbit/s
signaling channels and traffic channels.
Layered Model of the A interface protocol

This section describes the protocol structure for the A interface.
Physically, the A interface provides trunk circuits and ports for connecting the BSS to the MSC.
Figure 10-1 shows the protocol structure for A interface signaling.
Figure 10-1 Protocol structure for A interface signaling
Issue 03 (2011-08-31)

73
BSC6900 GSM
NOTE
l BSSAP: Base Station Subsystem Application Part

l DTAP: Direct Transfer Application Part
l BSSMAP: Base Station Subsystem Management Application Part
l SCCP: Signaling Connection Control Part
l MTP: Message Transfer Part
Physical layer
The physical layer of the A interface can use a 2 Mbit/s 120-ohm twisted pair cable or 75-ohm
coaxial cable.
The physical layer of the A interface has the following characteristics:
l
The 2 Mbit/s transmission rate complies with ITU-T G.703.
Frame structure, synchronization, and timing comply with ITU-T G.705.
Fault management complies with ITU-T G.732.
Cyclic redundancy check 4 (CRC4) complies with ITU-T G.704.
MTP
The main function of Message Transfer Part (MTP) is to ensure reliable signaling transfer in the
signaling network. In the case of system and signaling network failures, MTP takes measures
to avoid or reduce packet loss, duplication, and disorder. MTP comprises three functional levels:
signaling data link, signaling link, and signaling network. MTP complies with ITU-T Q.701
through ITU-T Q.710.
Signaling Data Link Functional Level (Level 1)

Signaling data link functional level (level 1) is used for signaling transmission. It consists of two
channels that have the same data rate but transmit signaling in opposite directions. A semipermanent connection is established between BSS signaling processing equipment and digital
trunk equipment through a digital switching network. It occupies a 64 kbit/s Pulse Code
Modulation (PCM) timeslot for signaling transmission. The digital trunk equipment actually
implements the level 1 function of MTP. The advantage of a semi-permanent connection is that
any timeslot (except the synchronous timeslot) can be used as a signaling data link, which can
be configured by running an MML command.
Signaling Link Functional Level (Level 2)

Signaling link functional level (level 2) defines the functions and procedures for sending
signaling to signaling data links. In combination with level 1, this level guarantees reliable
signaling transfer between two directly connected signaling points. Level 2 functions consist of
signaling-unit delimitation, signaling-unit alignment, error detection, error correction, initial
alignment, processor fault, level2 flow control, and error-rate monitoring.
These functions are performed by signaling processing equipment of the BSS. Error control
methods of signaling processing equipment can be set on the OMC. The basic error correction
method is applicable to international signaling links with unidirectional transmission delay less
than 15 ms and to terrestrial signaling links. The preventive cyclic retransmission mode is
applicable to international signaling links with unidirectional transmission delay greater than or
equal to 15 ms and to all satellite signaling links.
Issue 03 (2011-08-31)

74
BSC6900 GSM
Signaling Network Functional Level (Level 3)

Signaling network functional level (level 3) defines the functions of and procedures for
transferring management messages between signaling points. It guarantees reliable signaling
transfer when signaling links or signaling transfer points in the signaling network fail. Signaling
network functions are signaling message processing and signaling network management.
l
Signaling message processing

The signaling message processing part sends signaling messages to the corresponding
signaling links or user parts (such as TUP, ISUP and SCCP) according to message flags.
Signaling message processing involves message routing, message discrimination, and
message distribution, as shown in Figure 10-2.
Figure 10-2 Signaling message processing flowchart
Message routing
The message routing part selects a route (signaling link) for transmitting a signaling
message to its destination (DSP) according to the Destination Point Code (DPC) and
Signaling Link Selection (SLS) in the route flag.
Message discrimination
The message discrimination part receives a message from level 2 and then decides
whether the destination of the messages is the local signaling point. If the destination
is the local signaling point, the message discrimination part will send the message to
the message distribution part. Otherwise, the message discrimination part will send the
message to the message routing part.
Message distribution
The message distribution part allocates messages received from the message
discrimination part to the user part, signaling network management part, and test and
maintenance part.
l
Signaling network management

Signaling network management reconstructs a signaling network and resumes normal
signaling transfer when the signaling network fails. Signaling network management
Issue 03 (2011-08-31)

75
BSC6900 GSM
comprises signaling traffic management, signaling link management and signaling route
management.
Signaling traffic management
Signaling Traffic Management (STM) switches a signaling flow from one link or route
to one or more available links or routes when the signaling network fails. It also reduces
signaling traffic temporarily when a signaling point is congested.
Signaling link management
Signaling link management restores, establishes, and releases signaling links in the
signaling network, and ensures provision of certain pre-determined link groups.
Connections between signaling data links and signaling terminals are generally
established by running MML commands. These connections cannot be changed by
operations performed in the signaling system.
Signaling route management
Signaling route management ensures reliable exchange of information about whether
signaling routes are available between signaling points, so that signaling routes can be
blocked or unblocked when necessary. It mainly comprises procedures such as transfer
prohibited, transfer allowed, controlled transfer, restricted transfer, signaling route
group test, and signaling route group congestion test.
SCCP
Signaling Connection and Control Part (SCCP) is designed to provide complete network-layer
functions with the help of MTP level 3. According to the OSI model, the network layer provides
connectionless services and connection-oriented services. SCCP complies with ITU-T Q.711
through ITU-T Q.716.
SCCP Functions
SCCP application enables:
l
Interconnection between signaling networks
New services and functions in mobile communications networks, intelligent networks, and
intelligent management
Integrated Services Digital Network (ISDN) supplementary services
Data transfer between network management centers
In general, SCCP provides reliable services for any information exchange based on MTP. SCCP
not only provides network services but also performs functions of routing and network
management. The SCCP routing function mainly performs addressing with such information as
Destination Point Code (DPC), Subsystem Number (SSN), and Global Title (GT). The SCCP
network management function mainly manages the signaling point state and subsystem state,
switches over active/standby subsystems, broadcasts state information, and tests the subsystem
state.
SCCP Services
SCCP services can be classified into basic connectionless services (class 0), in-sequence delivery
connectionless services (class 1), basic connection-oriented services (class 2), and flow control
connection-oriented services (class 3). Classes 0 and 1 are connectionless service, whereas
classes 2 and 3 are connection-oriented services.
The classes of SCCP services are described as follows:
Issue 03 (2011-08-31)

76
BSC6900 GSM
Connectionless service
In connectionless service, users do not establish signaling connection before data transfer,
but instead use the routing functions of SCCP and MTP to transfer data directly in the
signaling network. This flexible and simple service is applicable to the transfer of a small
amount of data. Class 0 service does not guarantee sequential transfer of messages. Class
1 service guarantees sequential transfer of messages by using Signaling Link Selection
(SLS) and MTP.
Connectionless services transmit user data by adopting the Unit Data (UDT) message and
Enhanced Unit Data (XUDT) message. UDT messages do not have data segmentation or
reassembly capabilities and carry only a small amount of user data. XUDT messages have
data segmentation and reassembly capabilities and carry up to 2 KB of user data.
Connection-oriented service
Connection-oriented services require establishment of a signaling connection (virtual
connection) in acknowledged mode between the originating point and the destination point
before signaling transfer. In this case, data is transmitted through the established signaling
connection instead of by using the SCCP routing function. When data transfer finishes,
users need to release the signaling connection. This class of service is applicable to the
transfer of a large amount of data because the destination has acknowledged the capability
of receiving data. This avoids invalid transmission of a large amount of data. In addition,
the pre-established connection enables subsequent data to be transmitted without SCCP
routing, reducing data-transfer delay.
SCCP Routing Control

SCCP routing control performs routing and addressing according to SCCP address information.
The following types of address information can be found in SCCP:
l
DPC
DPC + SSN or GT (or both)
GT+ (SSN)
The Destination Point Code (DPC) is used by MTP in addressing. The Subsystem Number (SSN)
is used to identify different SCCP users in the same node, such as ISUP, MAP, TCAP, and
BSSAP. MTP supports only a small number of users, whereas SCCP enables the addressing
range to be expanded to meet the requirements of future new services.
Global Titles (GTs) are dialing numbers, such as international and national telephone numbers,
ISDN numbers, and E.214 numbers specific to GSM. They do not directly represent routing
information in the signaling network. The routing information can be obtained through GT
translation. Different from DPCs, GTs are valid globally. The addressing range of GTs is far
larger than that of DPC. GTs enable the transfer of information irrelevant to circuits between
any two signaling points worldwide. The powerful addressing capability of GTs is an important
characteristic of SCCP.
SCCP Management
SCCP management (SCMG) ensures normal network operation by re-routing or adjusting traffic
in case of network failure or congestion. This function is implemented by transferring SCCP
management messages and primitives. The management messages adopt class-0 UDT. SCCP
management consists of signaling point management, subsystem management, active/standby
subsystem switchover, state information broadcast, and faulty subsystem state testing.
Issue 03 (2011-08-31)

77
BSC6900 GSM
BSSAP
The Base Station Subsystem Application Part (BSSAP) is an A interface specification. It
describes two types of messages: BSSMAP messages and Direct Transfer Application Part
(DTAP) messages. BSSAP messages are responsible for traffic flow control and need to be
processed by the internal functional module of the A interface. In DTAP messages, the A
interface functions as a transmission channel. DTAP messages are directly transmitted to a radio
channel on the BSS side and to the corresponding functional processing unit on the Network
SubSystem (NSS) side. BSSAP protocols are defined in ETSI GSM 08.08 and ETSI GSM 04.08.
Typical Message Contents

l
DTAP messages
According to the functional units of the NSS that processes DTAP messages, DTAP
messages can be classified into Mobile Management (MM) messages and Call Control
(CC) messages.
MM messages include authentication, CM service request, identification request, IMSI
detach, location update, MM state, and TMSI re-allocation messages.
CC messages include alerting, call proceeding, connection, setup, modification, release,
disconnection, notification, state query, and DTMF startup messages.
BSSMAP messages
BSSMAP messages can be classified into connectionless and connection-oriented
messages.
Connectionless messages include block/unblock, handover, resource, reset, and paging
messages.
Block/unblock messages include block, block ACK, unblock, and unblock ACK
messages. Circuit group block/unblock messages include circuit group block, circuit
group block ACK, circuit group unblock, and circuit group unblock ACK messages.
Handover messages include handover candidate enquiry and handover candidate
enquiry response messages.
Resource messages include resource request and resource indication messages.
Reset messages include reset and reset ACK messages.
Connection-oriented messages include assignment, handover, clear, and cipher
messages.
Assignment messages include assignment request, assignment completion, and
assignment failure messages.
Handover messages include handover request, handover request ACK, handover
command, handover completion, and handover failure messages.
Clear messages include clear request, clear command, and clear completion messages.
Cipher messages include cipher mode command and cipher mode completion messages.
BSSAP Protocol Functionality

BSSAP performs its functions by using connection-oriented and connectionless SCCP services.
When an MS needs to exchange messages with the network side but there is no SCCP connection
for the MS between the MSC and the BSS, a new connection is established. External handovers
also require a new connection.
A connection needs to be established in either of the following conditions:
Issue 03 (2011-08-31)

78
BSC6900 GSM
When an MS sends an Access Request message on the RACH, the BSS allocates a dedicated
radio resource (DCCH or TCH) to the MS. After a layer 2 connection is set up on the
SDCCH (or FACCH) where resources are allocated, the BSS starts to set up the connection.
When an MSC decides to perform an external handover (the target BSS may be the source
BSS), it must reserve a new DCCH or TCH from the target BSS. In this scenario, the MSC
starts to set up the connection.
BSSAP implements the functions described in Table 10-3 by using connection-oriented or

connectionless messages.
Table 10-3 BSSAP functions
Issue 03 (2011-08-31)
Function
Description
Assignment
Assignment ensures that dedicated radio resources are properly

allocated or re-allocated to an MS. The initial MS random access
and immediate assignment to a DCCH is processed automatically
by the BSS but not controlled by the MSC.
Block/Unblock
During an assignment procedure, the MSC selects an available

terrestrial circuit. If this circuit is no longer available, the BSS
instructs the MSC to block/unblock the circuit.
Resource Indication
Resource indication notifies the MSC of the number of idle radio

resources that can be used as traffic channels and the total number
of available radio resources (idle or have already been occupied).
The MSC cannot get these radio resource numbers from the MSCcontrolled services. However, the MSC must obtain the numbers
before it decides an external handover.
Reset
Reset initializes the faulty BSS or MSC. For example, if the BSS
becomes faulty or loses all reference information for service
processing, the BSS sends a reset message to the MSC, instructing
the MSC to release the affected calls, delete the affected reference
information, and set all circuits related to the BSS to idle. If the MSC
or BSS is only partially faulty, the affected parts can be cleared using
the clear procedure.

79
BSC6900 GSM
Function
Description
Handover Request
In any of the following conditions, the BSS may send a Handover

Request message to the MSC to request a handover of the MS to
which dedicated resources have been allocated:
l The BSS detects a radio cause for handover.
l The MSC starts a handover candidate enquiry procedure and an
MS is waiting for a handover.
l Due to congestion, the serving cell needs to be changed during
call setup, for example, through a directed retry.
The BSS resends a handover request message at intervals until one
of the following situations occurs:
l The BSS receives a Handover Command message from the
MSC.
l The BSS receives a Reset message.
l All communications with the MS are interrupted and the
processing is aborted.
l Processing is complete, for example, a call is cleared.
Issue 03 (2011-08-31)
Handover Resource
Allocation
Handover Resource Allocation enables the MSC to request

resources from the target BSS based on the handover request. The
target BSS will reserve resources and wait for an MS to access this
channel.
Handover Procedure
In a handover procedure, the MSC instructs an MS to access the

radio resources of another cell. When the handover is performed,
the original dedicated radio resources and terrestrial resources are
maintained until the MSC sends a Clear Command message or a
reset occurs.
Release of Radio
Resources and
Terrestrial Resources
When processing finishes, the MSC sends a Clear Command

message to the BSS. After receiving the message, the BSS starts a
Clear procedure on the air interface, sets the configured terrestrial
circuit to idle, and returns a clear completion message to the MSC.
The MSC then releases the terrestrial resources at the local end. If
resources need to be released by the BSS, the BSS sends a Clear
Request message to the MSC, requesting the MSC to start a release
procedure to release the terrestrial and radio resources concerning
the MSC and BSS.
Paging
The paging to MS is transmitted by using the SCCP connectionless

services of BSSMAP. After the BSS receives a Paging Response
message from the air interface, it establishes an SCCP connection
to the MSC. The paging response message, which is contained in
the BSSMAP Full L3 Message, is transmitted to the MSC through
the SCCP connection.
Flow Control
Flow control prevents network entities from receiving too much

traffic so that the traffic volume is balanced. Flow control on the A
interface controls the traffic at the traffic source. It is classified into
five levels and can be implemented based on subscriber classes.

80
BSC6900 GSM
Function
Description
Classmark Update
Classmark update notifies a receiving entity of classmark messages

received from an MS. Generally, the BSS notifies the MSC of a
classmark message from an MS. After a handover finishes, the MSC
sends the corresponding MS classmark message to the new BSS
over the A interface.
Cipher Mode Control
The Cipher Mode Control procedure allows the MSC to transmit

the cipher mode control message to the BSS and start the subscriber
equipment and signaling cipher equipment with a correct Kc.
Queuing Indication
This procedure notifies the MSC that the BSS will delay the
allocation of necessary radio resources. This procedure is valid only
when the queuing function is introduced for traffic channel
assignment and traffic channel handover in the BSS.
Load Indication
Load indication notifies all the neighboring BSSs of the load status
of a cell so that all handovers in an MSC are under control. In a
certain validity period, the neighboring BSSs will consider the load
status of neighboring cells during handovers.
A interface circuit resource management

Terrestrial channel management between the BSS and the MSC keeps the states of terrestrial
circuits at both ends consistent. This ensures that a proper circuit can be found for a call or
handover. Procedures involved in A interface circuit resource management are Circuit Block/
Unblock, Circuit Group Block/Unblock, Unequipped Circuit, and Reset Circuit.
Circuit Control Principles

The general principles of circuit control are as follows:
l
Circuit management messages, except Reset Circuit messages, are initiated by the BSC.
The MSC can block/unblock only the local circuits without affecting the circuit states on
the BSS side.
The BSS cannot change the circuit states on the MSC side. For example, if a circuit is
blocked on the MSC maintenance console, the BSS is not allowed to unblock or reset the
circuit.
Circuit Block
A circuit block procedure blocks circuits on both the BSS and MSC sides. This procedure can
be initiated on the BSC maintenance console. It can also be initiated when a circuit is assigned,
a handover is performed, or a device becomes faulty. This procedure can be used in GSM Phase
I and Phase II. Figure 10-3 shows the circuit block procedure.
Issue 03 (2011-08-31)

81
BSC6900 GSM
Figure 10-3 Circuit block procedure
If the BSC does not receive a Block acknowledge message within a certain period of time, it
retransmits the Block circuit message to the MSC. The circuit on the BSC side is still in the
blocked state even if the BSC does not receive a Block acknowledge message from the MSC.
When the BSC sends a Block circuit message to the MSC, the BSC generates an alarm. Circuit
block does not affect circuits in service. Therefore, busy circuits will not be blocked until
communication finishes.
Circuit Unblock
A Circuit Unblock procedure unblocks circuits blocked by the BSC. This procedure can be
initiated on the BSC maintenance console. Circuit unblock can be used in GSM Phase I and
Phase II. Figure 10-4 shows the circuit unblock procedure.
Figure 10-4 Circuit unblock procedure
If the BSC does not receive an Unblock acknowledged message before the associated timer
expires, it retransmits an Unblock circuit message to the MSC. The circuit on the BSC side is
still idle even if the BSC does not receive an Unblock acknowledged message from the MSC.
When the BSC sends an Unblock circuit message to the MSC, the BSC generates an alarm.
Circuit Group Block

A Circuit Group Block procedure blocks multiple A-interface circuits at one time. This
procedure can be initiated on the BSC maintenance console or by trunk equipment itself. Circuit
Group Block can be used only in GSM Phase II. Figure 10-5 shows the circuit group block
procedure.
Issue 03 (2011-08-31)

82
BSC6900 GSM
Figure 10-5 Circuit group block procedure
If the BSC does not receive a Group block acknowledged message before the associated timer
expires, it retransmits a Group block message to the MSC. The circuits on the BSC side are still
blocked even if the BSC does not receive a Group block acknowledged message from the MSC.
When the BSC sends a Group block message to the MSC, the BSC generates an alarm. Circuit
group block does not affect circuits in service. Therefore, busy circuits will not be blocked until
communication finishes.
Circuit Group Unblock

A Circuit Group Unblock procedure unblocks multiple A-interface circuits simultaneously. This
procedure can be initiated on the BSC maintenance console or by trunk equipment itself. Circuit
Group Unblock can be used only in GSM Phase II. Figure 10-6 shows the circuit group unblock
procedure.
Figure 10-6 Circuit group unblock procedure
If the BSC does not receive a Group unblock acknowledged message before the associated timer
expires, it retransmits a Group unblock message to the MSC. The circuits on the BSC side are
still idle even if the BSC does not receive a Group unblock acknowledged message from the
MSC. When the BSC sends a Group unblock message to the MSC, the BSC generates an alarm.
Unequipped Circuit
An Unequipped Circuit procedure is used by the BSC or MSC to inform the peer end that a
circuit does not exist and cannot be used. This procedure can be initiated during any procedures
related to circuits. When the BSC or MSC receives a message indicating that a circuit is
Issue 03 (2011-08-31)

83
BSC6900 GSM
unequipped, an Unequipped Circuit procedure is initiated. Unequipped Circuit can be used only
in GSM Phase II. Figure 10-7 shows the unequipped circuit procedure.
Figure 10-7 Unequipped circuit procedure
An unequipped circuit message will be sent only once. When the BSC or MSC sends an
Unequipped Circuit message, an alarm will be generated.
Circuit Reset
A Circuit Reset procedure recovers the system resource information of the MSC and BSC when
a fault (for example, abnormal release of an SCCP connection) affects only a few network
elements. Figure 10-8 shows the circuit reset procedure.
Figure 10-8 Circuit reset procedure
Figure 10-8 shows a circuit reset procedure initiated by the BSC. When the MSC receives a
Reset circuit message, it clears the calls carried by the circuit and sets the circuit state to idle.
The MSC, then, returns the Reset circuit acknowledged message to the BSC. A circuit reset
procedure initiated by the MSC is similar to that in the preceding figure. The only difference
lies in the transmission direction of the messages.
If the BSC does not receive a Reset circuit acknowledged message before the associated timer
expires, it retransmits the Reset circuit message. The retransmission times can be set through
software. The circuit on the BSC side is still idle even if the BSC does not receive a Reset circuit
acknowledged message from the MSC. When the BSC sends a Reset circuit message to the
MSC, the BSC generates an alarm. A similar procedure is performed on the MSC side.
Circuit Reset can also be initiated on the BSC maintenance console for maintenance and testing.
Issue 03 (2011-08-31)

84
BSC6900 GSM
A-interface radio resources management

A interface radio resource management mainly involves resource indication and resource
clearing procedures.
Resource Indication
A resource indication procedure notifies the MSC of the number of idle radio resources that can
be used as traffic channels and the total number of available radio resources (can be allocated
or have already been allocated) in the BSS. The MSC may consider the radio resource
information when deciding an external handover. Figure 10-9 shows the resource indication
procedure.
Figure 10-9 Resource indication procedure
There are four types of resource indications: automatic indication, single indication, periodical
indication, and no indication. No indication is the default mode.
l
In automatic indication mode, the BSS continuously sends Resource Indication messages
to the MSC at the interval specified in the Resource Indication Request message when the
relevant cell meets the conditions predefined at the OMC.
In single indication mode, the BSS immediately returns a Resource Indication message
about the relevant cell to the MSC.
In periodical indication mode, the BSS continuously sends Resource Indication messages
to the MSC at the interval specified in the Resource Indication Request message, until it
receives a new Resource Request or Reset message. The interval is set at the MSC with the
unit 100 ms.
In no indication mode, the BSS immediately returns a single Resource Indication message
without any resource information, and the procedure is finished.
For each idle channel, the BSS calculates the average interference level within a period. Based
on the average interference level, five interference bands are classified for idle channels. The
Resource Indication information element contains two types of information about each
interference band: number of idle half-rate traffic channels and number of idle full-rate traffic
channels in the interference band.
Resource Clearing
A resource clearing procedure releases all relevant terrestrial circuit resources and radio
resources. It can be initiated by the MSC or by the BSS.
Issue 03 (2011-08-31)

85
BSC6900 GSM
Figure 10-10 shows the resource clearing procedure initiated by the MSC.
Figure 10-10 Resource clearing procedure initiated by the MSC
Figure 10-11 shows the resource clearing procedure initiated by the BSS.
Figure 10-11 Resource clearing procedure initiated by the BSS
Other A-interface management procedures

Other management procedures on the A interface are classmark update, reset, flow control,
queuing, error handling, SCCP link control, and load indication.
Classmark Update
A classmark update procedure notifies the MSC of a classmark message received from an MS.
This procedure is initiated when the power classmark of a dedicated resource occupied by an
MS changes. Figure 10-12 shows the classmark update procedure.
Issue 03 (2011-08-31)

86
BSC6900 GSM
Figure 10-12 Classmark update procedure
Reset
A reset procedure initializes a faulty BSC or MSC so that all resources can be released.
When the BSC is reset, it releases all resources and sends a Reset message to the MSC. After
receiving the Reset message, the MSC releases all calls and connection resources and sets all
circuits associated with the BSC to idle. When timer T2 expires, the MSC returns a Reset
acknowledged message to the BSC, indicating that the reset is successful. Figure 10-13 shows
the BSC reset procedure.
Figure 10-13 BSC reset procedure
When the MSC is reset, it releases all resources and sends a Reset message to the BSC. After
receiving the Reset message, the BSC releases all calls and connection resources. When timer
T13 expires, the BSC returns a Reset acknowledged message to the MSC, indicating that the
reset is successful. Figure 10-14 shows the MSC reset procedure.
Issue 03 (2011-08-31)

87
BSC6900 GSM
Figure 10-14 MSC reset procedure
Flow Control
Flow control on the BSC side controls traffic flow from MSs when the MSC is overloaded,
preventing system malfunction or congestion. This enables the traffic flow of calls to be
controlled within a reasonable range.
When the MSC is overloaded, the MSC sends an Overload message to the BSC, instructing the
BSC to control the traffic flow. The flow control algorithm complies with GSM specifications.
It adopts a dynamic sliding window, which is started when the MSC is overloaded. The size of
the window can be modified to control the traffic according to the amount of traffic. This window
is invalid once the MSC is no longer overloaded. Figure 10-15 shows the flow control procedure.
Figure 10-15 Flow control procedure
NOTE
When the BSC is overloaded, it sends an Overload message to the MSC. Then, the MSC performs flow
control. The BSC also takes flow control measures.
Load Indication
A load indication procedure informs neighboring BSSs of the load conditions of a cell. This
procedure is used to control handovers.
After the MSC receives a Load Indication message, it forwards the information to the BSS. The
BSS considers the load conditions in subsequent handovers.
Issue 03 (2011-08-31)

88
BSC6900 GSM
SCCP Link Control

When an SS7 link is abnormally disconnected, transmission of control messages over the A
interface is stopped through software. When the SS7 link recovers, control messages are sent
again over the A interface. If an SS7 link is disconnected for a long time, a resource clearing
procedure is initiated as soon as the link is recovered. This prevents resource deadlock.
Error Handling
As errors may occur on transmission links, messages received may not be understandable.
Therefore, erroneous messages are omitted and "confusion" messages (these messages are used
in GSM Phase II) are selectively sent over the A interface.
10.2.2 Data Configuration Principles for the Ater Interface

The Ater interface connects an MPS or EPS to a TCS.
Links on the Ater Interface

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-4 lists the links that need to be
configured on the A and Ater interfaces.
Table 10-4 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-16 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.
Issue 03 (2011-08-31)

89
BSC6900 GSM
Figure 10-16 Links on the A and Ater interfaces (TCS configured locally)
Figure 10-17 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.
Figure 10-17 Links on the A and Ater interfaces (TCS configured remotely)
The configuration rules of the signaling links on the Ater interface are as follows:
l
Issue 03 (2011-08-31)
Each subrack needs to be configured with at least four Ater signaling links.
90
BSC6900 GSM
Two 64 kbit/s Ater signaling links are configured for the 512 CICs.
If the number of Ater signaling links calculated according to the second rule is less than
four Ater signaling links per subrack, then follow the first configuration rule. If the number
of Ater signaling links calculated is greater than four Ater signaling links per subrack,
configure the actual number of Ater signaling links.
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-5 lists the bandwidth of OM timeslots and signaling timeslots on the
Ater interface.
Table 10-5 Bandwidth of OM timeslots and signaling timeslots on the Ater interface
Issue 03 (2011-08-31)
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.
MPS+EPS+2TCS
Each BM subrack is
configured with four
timeslots of 64 kbit/s.
MPS+2EPS+3TCS
Each BM subrack is
MPS+3EPS+4TCS
Each BM subrack is
MPS+EPS+TCS
Each BM subrack is
MPS+3EPS+2TCS
Each BM subrack is
configured with eight

91
BSC6900 GSM
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 Data Configuration Principles for the Gb Interface

The Gb interface is the standard open interface between the BSS and the SGSN. Through this
interface, the SGSN communicates with the BSS to implement functions such as packet data
transfer, flow control, and mobility management. The location of the Gb interface in a GPRS
system is similar to the location of the A interface between the BSS and the MSC in a GSM
system. Their main difference is that the Gb interface is used to provide packet switched services.
Layered Model of the Gb interface protocol

This section describes the protocol structure for the Gb interface.
Figure 10-18 shows the protocol structure for Gb interface signaling.
Figure 10-18 Protocol structure for Gb interface signaling
NOTE
l The physical layer (layer 1) of the Gb interface, based on the Frame Relay (FR) protocol, can be
implemented through point-to-point frame relay connections or multipoint-to-multipoint frame relay
network connections.
l The Network Service (NS) layer (layer 2) of the Gb interface transmits Service Data Units (SDUs) on
the Gb interface, configures NS Virtual Connections (VCs), and manages the NS VC state.
l The Base Station Subsystem GPRS Protocol (BSSGP) layer (layer 3) of the Gb interface performs
operation and maintenance functions, such as transmitting uplink and downlink upper-layer (LLC
layer) signaling and data, performing downlink data flow control, and blocking, unblocking, and
restarting BSSGP Virtual Connections (BVCs).
Issue 03 (2011-08-31)

92
BSC6900 GSM
FR
The physical layer of the Gb interface adopts the Frame Relay (FR) protocol. The physical media
of the Gb interface can be E1 or T1.
The frame relay module enables interworking between sub-networks so that the PCU and the
SGSN can connect with each other either directly (point-to-point connection) or through a frame
relay network (intermediate network connection), as shown in Figure 10-19 and Figure
10-20, respectively.
Figure 10-19 Point-to-point connection
Figure 10-20 Intermediate network connection
NS
The Network Service (NS) layer is distributed on both sides of the Gb interface and has
symmetrical functions on both sides.
The NS layer provides the following functions for the BSSGP layer:
l
Upper-layer SDU transmission: All messages from the BSSGP layer are encapsulated in
Service Data Units (SDUs) at the NS layer. The NS layer provides reliable channels and
protection for normal operation of the upper layer.
Network congestion detection: When the NS layer detects that congestion occurs on lowerlayer links or congestion is relieved, it notifies the upper layer of the condition through a
congestion indication message so that the upper layer can handle it accordingly.
Network state detection: When the NS layer finds that a lower-layer link fails to transmit
data or the fault is rectified, it notifies the upper layer of the faulty point (recovery point)
so that the upper layer can handle it accordingly.
BSSGP
The Base Station Subsystem GPRS Protocol (BSSGP) layer is distributed on both sides of the
Gb interface but has different functions on both sides.
Figure 10-21 shows the service models of the BSSGP protocol on the BSS and SGSN sides.
Issue 03 (2011-08-31)

93
BSC6900 GSM
Figure 10-21 Service models of the BSSGP protocol on the BSS and SGSN sides
The BSSGP layer provides the following functions for the upper layer:
l
Network Management BSSGP (NMBSSGP). This part performs the network management
function on the Gb interface. The network management function includes downlink data
flow control, blocking, unblocking and resetting of BSSGP Virtual Connections (BVCs),
and MS tracing.
GPRS Mobility Management BSSGP (GMMBSSGP). This part performs the GPRS
mobility management function on the Gb interface. The GPRS mobility management
function includes MS paging, synchronization of MS radio access capability, and
suspending and resuming of GPRS services.
Uplink and downlink data transfer. This part transparently transmits uplink and downlink
data. The data transfer service is called RL BSSGP service on the BSS side but LLC BSSGP
service on the SGSN side.
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-6 describes the configuration parameters.
Issue 03 (2011-08-31)

94
BSC6900 GSM
Table 10-6 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)
Issue 03 (2011-08-31)
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.

95
BSC6900 GSM
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-22 shows the logical connections at the NS and BSSGP layers between the
BSC6900 and the SGSN.
Issue 03 (2011-08-31)

96
BSC6900 GSM
Figure 10-22 Logical connections at the NS and BSSGP layers
As shown in Figure 10-22, 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 set under this NSE so that the traffic is evenly distributed among the
NSVCs.
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.
Characteristics of Gb Interface
This section describes the characteristics of the Gb interface.
The Gb interface has the following characteristics:
l
Flexible physical port and LMI support

The M900/M1800 PCU supports E1 ports that comply with ITU-T recommendations.
The Local Management Interface (LMI) supports ITU-T Q933 appendix A, specified in
GSM protocols, CISCO LMI, and ANSI T1-617 appendix D. This enables Huawei PCU
to interwork with another vendor's equipment.
Flexible FR BC bandwidth and NS Virtual Connection (VC) bandwidth

A physical bearer channel of the frame relay layer of the M900/M1800 PCU can be
configured with a bandwidth between 1 x 64 kbit/s and 31 x 64 kbit/s. An NS VC at the
NS layer can be configured with a bandwidth between 1 kbit/s and 1,984 kbit/s. This
facilitates network planning.
l
Issue 03 (2011-08-31)
Load sharing at the NS layer

97
BSC6900 GSM
The M900/M1800 PCU supports load sharing among all NS VCs under one NSE. NS VCs
can be located on different boards. This is crucial in improving the transmission reliability
and utilization of the Gb interface.
l
BSSGP entity switchover

The M900/M1800 PCU supports switchovers between BSSGP PTP entities and between
BSSGP SIG entities. When a PTP entity is unavailable, services carried by this entity are
automatically switched over to another available PTP entity, regardless of whether the
available PTP entity is located on the same physical board as the faulty PTP entity. When
a SIG entity is unavailable, services carried by this entity are automatically switched over
to another available SIG entity, regardless of whether the available SIG entity is located
on the same physical board as the faulty SIG entity. The entity switchover function
improves reliability of the BSSGP layer.
10.2.4 Data Configuration Principles for the Pb interface

The Pb interface connects the PCU and the BSC. It manages cells, packet channels, and various
shared resources such as E1 trunk cables and system information, between the PCU and the
BSC. In addition, the Pb interface supports dynamic channel conversion and MS access to
CCCH.
Internal Structure of Pb Interface

This section describes the internal structure of the Pb interface.
The Pb interface, as an internal protocol, has three layers:
l
The physical layer (layer 1) uses E1 sub-timeslots to implement its functions. In fact, the
Pb interface and the G-Abis interface share the same physical link by using sub-timeslot
multiplexing. One E1 is divided into 128 sub-timeslots of 16 kbit/s each, with 4 subtimeslots used for synchronization. Some of these sub-timeslots are used for the physical
link on the G-Abis interface, some are used for the physical link on the Pb interface, and
the rest may serve as idle sub-timeslots or are multiplexed for the A interface. The G-Abis
interface is the internal interface between the PCU and the BTS.
The link layer (layer 2) is based on the Link Access Protocol D-channel (LAPD) protocol,
which is a general data link layer protocol. It receives data from the physical layer and
provides connection-oriented or connectionless services for layer 3. LAPD provides peerto-peer reliable message transfer between layer 3 entities.
The layer 3 protocol consists of a series of self-defined signaling messages and it is the
core of the Pb interface. It mainly manages various GPRS resources between the PCU and
the BSC, supports conversion of dynamic channels between packet services and speech
services, and provides functions such as MS access to CCCH and speech paging message
transmission.
Management of the trunk circuits on the Pb interface

Managing trunk circuits on the Pb interface helps keep consistency in trunk circuit status between
the BSC and the PCU. This ensures that an idle circuit can be assigned when the PCU requests
a PDCH or dynamically changes channel coding.
The procedures for Pb interface circuit management involve circuit block, circuit unblock,
unequipped circuit, and circuit reset. A procedure is initiated when maintenance is performed
or the state of Pb interface equipment changes.
Issue 03 (2011-08-31)

98
BSC6900 GSM
The following principles are employed for Pb interface circuit management:

l
The BSC records only the maintenance status of a circuit but not the use status.
The BSC initiates circuit management messages.
The PCU can block, unblock, and reset circuits at the local end, without affecting the circuit
status on the BSC side.
The BSC cannot unblock a circuit that is blocked on the maintenance console of the PCU.
The procedures for circuit block, circuit unblock, unequipped circuit, and reset circuit are almost
the same as those on the A interface. The only difference is that the MSC is changed to the PCU
and the Circuit Identification Code (CIC) on the A interface is changed to the Packet Circuit
Identification Code (PCIC) on the Pb interface. Figure 10-23 shows a circuit block procedure
on the Pb interface.
Figure 10-23 Circuit block procedure on the Pb interface
Packet radio resource management

Packet radio resource management on the Pb interface refers to the management of radio
resources related to packet services.
Packet radio resource management adopts the following principles:
l
All information about radio resources is configured on the BSC side. The PCU obtains
radio resource information from the BSC.
A cell initialization process over the Pb interface involves three procedures: The cell is
reset on both the BSC and PCU sides; the BSC notifies the PCU of the packet radio resource
configuration of the cell; packet system information is broadcast.
Circuit services and packet services share radio resources. Radio resources are allocated
on demand but circuit services have priority over packet services.
Dynamic allocation of resources on demand requires the BSC to adjust radio resources
between circuit services and packet services in real time based on service requests. This
means dynamic conversion between TCHs and PDCHs. There are three channel conversion
procedures on the Pb interface:
When there is no PDCH for a packet assignment, the PCU requests the BSC to convert
a TCH into a PDCH. The BSC accepts or rejects the request according to the available
resources. If there are many idle TCHs, the BSC accepts the request, converts a TCH
into a PDCH, and then notifies the BTS to modify channel attributes.
Issue 03 (2011-08-31)

99
BSC6900 GSM
When the BSC finds that TCHs are insufficient, it requests the PCU to release some
PDCHs for conversion into TCHs. Releasing PDCHs in this case is mandatory because
circuit services have priority over packet services.
When the PCU finds many idle PDCHs, it automatically releases some PDCHs, also
for conversion into TCHs. This is also because circuit services have priority over packet
services.
l
The BSC is responsible for assigning TCHs, whereas the PCU is responsible for assigning
PDCHs.
After the PCU has been assigned a PDCH, allocating and releasing this PDCH is decided
by the PCU. Similarly, the BSC is responsible for the allocation and release of TCHs.
The status of radio resources on the BSC and PCU sides must be consistent.
To keep state consistency between the PCU and BSC sides, the BSC needs to notify the
PCU of state changes of radio resource in time. For example, when the OMC blocks a
certain PDCH, the BSC must notify the PCU to update the channel state.
Packet service access

To support GPRS, the system broadcasts system information type 13 on the BCCH, and at the
same time modifies system information type 3 and system information type 7 so that they contain
GPRS information such as GPRS Indicator. Based on these types of system information, an MS
decides whether and how to access the current serving cell for packet services.
When no PCCCH is configured in the serving cell, the MS requests packet services through the
CCCH. This mainly involves three procedures: packet call access initiated by the MS, packet
call access terminated by the MS, and packet service suspension and resumption of class-B MSs.
Other management procedures on the Pb interface

Other management procedures on the Pb interface are transmission management, PbSL
management, error handling, and PbSL check.
Transmission Management
In a conversion from TCH to PDCH, the BSC needs to connect the trunk circuit on the Abis
interface to the trunk circuit on the Pb interface. During packet data transmission, the BSC needs
to forward packet data between the BTS and the PCU. In a conversion from PDCH to TCH, the
BSC needs to disconnect the trunk circuit on the Abis interface from the trunk circuit on the Pb
interface.
In general, each PDCH corresponds to a 16 kbit/s terrestrial timeslot. If transmission quality is
satisfactory, the PCU can use a more efficient channel coding scheme, such as CS-3 or CS-4.
In this case, the BSC needs to allocate one more 16 kbit/s timeslot to the PDCH, giving it a 32
kbit/s terrestrial timeslot.
PbSL Management
The Pb interface signaling link (PbSL) is a LAPD link. PbSL management involves the
transmission and reception of Pb interface message packets and PbSL load sharing.
If there is no PCCCH in a cell, disconnecting all the PbSLs or restoring any PbSL to normal
operation subsequently leads to the release of resources in the cell on both sides of the Pb
interface.
Issue 03 (2011-08-31)

100
BSC6900 GSM
Error Handling
Some bits of a message may become erroneous during transmission. The Pb interface has an
error handling function to combat this. By using this function, erroneous messages are omitted
and some "confusion" messages are transmitted selectively.
PbSL Check
A PbSL between the PCU and the BSC may experience one-way audio because the E1 between
them may be connected incorrectly. Therefore, a mechanism for detecting one-way audio on
PbSL is introduced. In this mechanism, the PCU actively sends a PbSL detection message to the
BSC. If the BSC receives this message, it responds with an ACK message. The PCU determines
whether one-way audio occurs based on whether it receives the ACK message.
Characteristics of Pb Interface
This section describes the characteristics of the Pb interface.
The Pb interface has the following characteristics:
l
Maintaining consistency in resource status between the BSC and the PCU
The PCU and the BSC are located in two separate places, but the information about all
shared resources (such as cells, channels, PCIC trunk cables, and system information
parameters) should be consistent between them. This is a major function of the Pb interface.
Maintaining resource status consistency involves managing and maintaining cell parameter
configuration, cell restarting, channel blocking and unblocking, PCIC blocking and
unblocking, PCIC restarting, packet system information parameter configuration, and
regular check of all resource data.
Supporting dynamic channel conversion between packet services and circuit services
Channels are classified into three types according to their properties: fixed packet channels,
voice traffic channels, and dynamic channels. Fixed packet channels, such as PBCCH and
PCCCH, are dedicated for packet services. Voice traffic channels, such as TCH, BCCH
and SDCCH, are dedicated for voice services. Dynamic channels are initialized as TCHs
at first. Dynamic channels can be converted between the former two types of channels.
When packet traffic is heavy and voice traffic is light, the PCU requests the BSC to convert
dynamic channels into dynamic packet channels. When voice traffic is heavy, the BSC
requests the PCU to release the converted dynamic channels and then reuses them as voice
channels. In this process, voice services have priority over packet services to guarantee the
original voice services.
Supporting transmission of packet service requests over CCCH

The BTS cannot identify an access request message sent by an MS on the CCCH. After the
BSC interprets the message and finds that it is a packet access request, the BSC forwards
this message to the PCU. Similarly, an immediate assignment message from the PCU must
be processed by the BSC before it is sent to the BTS. This indicates that when an MS sends
an access request over the CCCH and the PCCCH, the processing in the BSS is different.
MSs sending packet access requests through the CCCH are not complex, and therefore their
costs are low. MSs of this type are widely used in the early phase of GPRS service
deployment. This function enables the PCU to support two types of access modes,
enhancing system adaptability.
Supporting GPRS suspension and resumption messages sent by class B MSs

Class B MSs cannot process CS services and PS services simultaneously. Therefore, when
an MS in packet transfer mode starts processing a voice service, it sends a GPRS suspension
Issue 03 (2011-08-31)

101
BSC6900 GSM
request to the BSC. The BSC then forwards this message to the PCU through the Pb
interface. When the voice service is finished, the BSC sends a GPRS resumption request
to the PCU through the Pb interface. The system capability for supporting class B MSs is
enhanced as the Pb interface processes GPRS suspension and resumption messages.
l
Terrestrial and satellite transmission

The Pb interface supports terrestrial and satellite transmission. These two transmission
modes allow the BSC and PCU to be located in different equipment rooms. This solves the
problem of long-distance transmission when one PCU is connected to multiple BSCs.
10.3 Configuration Guidelines for the GBTS

This section describes the configuration rules and reference information related to a base station.
10.3.1 Configuration Guidelines for Cabinet Numbers

This section describes the numbering rules of the 3900 series SingleRAN BTS cabinets,
subracks.
A site can be configured with both the virtual cabinet and the physical cabinet.
Table 10-7 provides the numbering rules of cabinets.
Table 10-7 Numbering rules of cabinets
Cabinet Number
Description
0-62
l BBU can be configured in cabinet 0-7.

l In the case of a distributed base station
with a physical cabinet or a macro base
station, a physical cabinet can be used.
l In the case of a distributed base station
without a physical cabinet, a virtual
cabinet can be used.
l In the case of BBU being configured in
APM30 physical cabinet and BBU not
monitoring BTS boards in the base station
cabinet, the cabinet BBU is configured in
should be configured as virtual cabinet.
l A maximum of eight cabinets can be
configured for the GU mode when the
TCS is configured locally.
10.3.2 Configuration Guidelines for Subracks

This section describes the principles for configuring the subrack No. of 3900 series SingleRAN
base stations.
Issue 03 (2011-08-31)

102
BSC6900 GSM
1.
In the case of the type of cabinet is fixed, physical subracks (such as BBU3900, RFU) are
existed fixedly.
2.
Some optional peripherals (such as EMS, GPS receiver) can be configured in a independent
cabinet for consistency and expansibility.
The numbering rules of the subrack for each type of cabinet are the same. The user cannot define
the fixed subrack No., but can define the subrack No. of extended subracks. The numbering rules
of the subracks are shown in Table 10-8.
Table 10-8 The numbering rules of the subrack for SingleRAN BTS
Subrack No.
Type
Description
Physical subrack.
The BBU subrack in cabinet

0-7.
2-3
Reserved.
Physical subrack.
RFU
Reserved.
Physical subrack.
PMU
Physical subrack.
TCU
Reserved.
10
Reserved.
11
Physical subrack.
FMU
13-39
Reserved.
Reserve for physical subrack.

It is lied on the type of
cabinet.
40-59
Extended subrack.
These subracks can house the

GPS receiver (one for a site),
EMU (one for a site
generally).
60-254
Physical subrack.
RRU
12
10.3.3 Configuration Guidelines for Slot Numbers

This section describes the numbering rules of slots of the SingleRAN and non-SingleRAN 3900
series base stations.
Issue 03 (2011-08-31)

103
BSC6900 GSM
Numbering Rules of Slots of the SingleRAN Base Stations

The mapping between a slot number and a board type depends on hardware specifications, as
listed in Table 10-9.
Table 10-9 Numbering Rules of Slots of the SingleRAN Base Stations
Board Type
Cabinet
Number
Subrack
Number
Slot Number
USCU
0~7
0~1
0~4
UBRI
1~2
You are advised

to install the
UBRI board in
slot 2.
GTMU
The GTMU
must be
configured in
slot 6.
FAN
16
The FAN must

be configured in
slot 16.
UPEU/UEIU
18~19
The UPEU or
UEIU must be
configured in
slots 18 and 19.
DRFU/GRFU/
MRFU
PMU
0~62
4~5
0~5
PSU
Issue 03 (2011-08-31)
Description
1~6
TCU
No board
No board is
configured in
slot 9.
FMU
11~12
DGPS/EMU/
GATM
40~59
DRRU/GRRU/
MRRU
60~254

104
BSC6900 GSM
Numbering Rules of Slots of the Non-SingleRAN Base Stations

Table 10-10 Numbering Rules of Slots of the Non-SingleRAN Base Stations
Board Type
Subrack Number
Slot Number
Description
DEMU
0~1
The APMU and

DTCU can be
configured in slots 0
to 23 of subrack 5.
APMU or DPMU
2~5
DTCU
6~7
FMU or FMUA
8~11
GATM
16~17
GTMU
UBFA
16
UEIU or UPEU
18~19
10.3.4 Mapping Between Base Stations and Optional Cabinets

This section describes the mapping between the SingleRAN 3900 series base stations and
optional cabinets.
Mapping Between the SingleRAN Base Stations and Optional Cabinets

Table 10-11 Mapping Between the SingleRAN Base Stations and Optional Cabinets
BTS Type
DBS3900
Issue 03 (2011-08-31)
Physical
Cabinet
APM cabinets
Silk Screen of
a Cabinet
Nameplate
Optical
Cabinet (The
types are
consistent
with the
correspondin
g values on
the LMT)
APM30
APM30
APM30H
APM30
APM100
APM100
APM200
APM200
PS4890
PS4890

Description
105
BSC6900 GSM
BTS Type
Physical
Cabinet
TMC cabinets
Battery group
Silk Screen of
a Cabinet
Nameplate
Optical
Cabinet (The
types are
consistent
with the
correspondin
g values on
the LMT)
Description
OMB
OMB
When an OMB
is used in a
BTS3900C, the
silk screen of the
cabinet
nameplate
should be
BTS3900C.
TMC
TMC
TMC11H
TMC
BBC
No BBC is
configured.
IBBS200D
BBC
IBBS200T
BBC
Virtual cabinet
BTS3900
BTS3900A
BTS3900
cabinets
BTS3900 GSM
BTS3900
PS4890
PS4890
PS4890
Virtual cabinet
AMP cabinets
RFC cabinets
Issue 03 (2011-08-31)
VIRTUAL
VIRTUAL
APM30
APM30
APM30H
APM30
RFC
RFC-6

If a cabinet is
different from
the preceding
cabinets, this
cabinet should
be configured as
a virtual cabinet.
If a cabinet is
different from
the preceding
cabinets, this
cabinet should
be configured as
a virtual cabinet.
106
BSC6900 GSM
BTS Type
Physical
Cabinet
TMC cabinets
Battery group
Silk Screen of
a Cabinet
Nameplate
Optical
Cabinet (The
types are
consistent
with the
correspondin
g values on
the LMT)
TMC
TMC
TMC11H
TMC
IBBS200D
BBC
IBBS200T
BBC
BBC
No BBC is
configured.
Virtual cabinet
BTS3900L
cabinets
VIRTUAL
BTS3900L
GSM
Virtual cabinet
Description
If a cabinet is
different from
the preceding
cabinets, this
cabinet should
be configured as
a virtual cabinet.
BTS3900L
VIRTUAL
BTS3900L
If a cabinet is
different from
the preceding
cabinets, this
cabinet should
be configured as
a virtual cabinet.
Mapping Between the Non-SingleRAN Base Stations and Optional Cabinets

Table 10-12 Mapping Between the Non-SingleRAN Base Stations and Optional Cabinets
Issue 03 (2011-08-31)
BTS Type
Optical Cabinet (The

types are consistent with
the corresponding values
on the LMT)
BTS30
BTS30
BTS312
BTS312
BTS3001C
BTS3001C
Description
107
BSC6900 GSM
BTS Type
Optical Cabinet (The

types are consistent with
the corresponding values
on the LMT)
BTS3001C+
BTS3001CP
BTS3002C
BTS3002C
BTS3012A
BTS3012A
BTS3006A
BTS3006A
BTS3012
BTS3012
BTS3006C
BTS3006C
BTS3002E
BTS3002E
BTS3012AE
BTS3012AE
BTS3012 II
BTS3012_II
BTS3900B GSM
BTS3900B_GSM
BTS3900E GSM
BTS3900E_GSM
BTS3900 GSM
BTS3900_GSM
BTS3900_GSM_6RFC
Description
l Recommended.
l The filler panel can be set
through the Configure
RFU by Slot parameter in
the ADD BTS command.
BTS3900A GSM
BTS3900A_GSM
BTS3900A_GSM_6RFC
l Recommended.
l The filler panel can be set
through the Configure
RFU by Slot parameter in
the ADD BTS command.
DBS3900 GSM
DBS3900_GSM
BTS3036
BTS3036
BTS3036_6RFC
BTS3036A
BTS3036A
BTS3036A_6RFC
DBS3036
Issue 03 (2011-08-31)
DBS3036

The configuration principle

of the BTS3036 is the same
as that of the BTS3900.
of the BTS3036A is the same
as that of the BTS3900A.
of the DBS3036 is the same
as that of the BTS3900.
108
BSC6900 GSM
10.3.5 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-13 Configuration rules of the BTS3900 boards
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 an RET antenna or a
TMA.
PSU
GTMU
Automatic configuration
FAN
UEIU
UPEU
UBRI
USCU
DRFU
GRFU
MRFU
DBS3900
Issue 03 (2011-08-31)

109
BSC6900 GSM
Table 10-14 Configuration rules of the DBS3900 boards

Board Type

Configuration
EMU

PMU
DTCU
GTMU
FAN
UEIU
UPEU
UBRI
USCU
DRRU
GRRU
MRRU
BTS3900A
Table 10-15 Configuration rules of the BTS3900A boards
Issue 03 (2011-08-31)
Board Type

Configuration
EMU

PMU
DTCU
FMUA/FMU
GATM

TMA.
GTMU
110
BSC6900 GSM
Board Type

Configuration
FAN
UEIU
UPEU
UBRI
USCU
DRFU
GRFU
MRFU
BTS3900L
Table 10-16 Configuration rules of the BTS3900L boards
Issue 03 (2011-08-31)
Board Type

Configuration
EMU

PMU
DTCU
FMUA/FMU
GATM

TMA.
GTMU
FAN
UEIU
UPEU
UBRI
USCU
DRFU

111
BSC6900 GSM
Board Type

Configuration
GRFU
MRFU
Configuration Rules of the Non-SingleRAN BTS Boards

BTS3900B
Table 10-17 Configuration rules of the BTS3900B boards
Board Type

Configuration
3900B
BTS3900E
Table 10-18 Configuration rules of the BTS3900E boards
Board Type

Configuration
DEMU
APMU
DTCU
3900E
BTS3012
Issue 03 (2011-08-31)
Board Type

Configuration
DTMU
DEMU
DCSU
DCCU
DATU
112
BSC6900 GSM
Board Type

Configuration
DPTU
DABB
DCMB
Automatic configuration in the case of 12

TRXs
ECMB
Automatic configuration in the case of 18

TRXs
DBS3900
Table 10-20 Configuration rules of the DBS3900 boards
Board Type

Configuration
APMU
DTCU
DEMU
Manual configuration. A DEMU needs to be

GATM

TMA.
GTMU
UBFA
UEIU
UPEU
BTS3900
Issue 03 (2011-08-31)
Board Type

Configuration
FMU

113
BSC6900 GSM
Board Type

Configuration
DEMU

GATM

TMA.
GTMU
UBFA
UEIU
UPEU
BTS3900A
Table 10-22 Configuration rules of the BTS3900A boards
Issue 03 (2011-08-31)
Board Type

Configuration
APMU
DTCU
FMUA
DEMU

GATM

TMA.
GTMU
UBFA
UEIU
UPEU

114
BSC6900 GSM
10.3.6 Configuration Guidelines for Monitoring Boards

This section describes configuration rules and reference information related to monitoring
boards.
Monitoring boards consist of Environment Monitoring Unit (EMU), Power Monitoring Unit
(PMU), Fan Monitoring Unit (FMU), and Temperature Control Unit (TCU). Table 10-23
describes the mapping between their logical names and physical devices.
Table 10-23 Monitoring Boards of a Base Station
Logical Name
Physical Device
Cabinet Type
Description
EMU
All cabinets
Wall-mounted
Environment
Monitoring Unit in
an equipment room
EMUA
All cabinets
PMU
All cabinets
EPMU01
APM30
Embedded Power
and Environment
Monitoring Unit type
01
EPMU01B
APM30
Embedded Power
and Environment
01B
EPMU03
OMB
Embedded Power
and Environment
03
FMU
All cabinets
Fan Monitoring Unit
FMUB
BTS3900
Fan Monitoring Unit

type B
TCU
All cabinets
Temperature Control
Unit
AFMU
BTS3900A/APM30/
TMC
APM Fan
Monitoring Unit
HEUA
APM30/TMC/OMB
Heat Exchange Unit

type A
CMUA
APM30/TMC/BBC
Central Monitoring
Unit type A
EMU
PMU
FMU
TCU
Issue 03 (2011-08-31)

Environment
Monitoring Unit
installed in a cabinet
Power Monitoring
Unit
115
BSC6900 GSM
Table 10-24 lists rules of configuring monitoring boards of the BTS3900A.

Table 10-24 Rules of configuring monitoring boards of the BTS3900A
Issue 03 (2011-08-31)
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 0
(AMP30)
PMU0
Cabinet 1
(AMP30)
PMU1
Cabinet 2
(AMP30)
PMU2
Cabinet 0
(AMP30)
TCU0
Cabinet 1
(AMP30)
TCU1
Cabinet 2
(AMP30)
TCU2
Cabinet 0
(TMC)
TCU3
Cabinet 0
(RFC)
FMU0
11
14
Cabinet 1
(RFC)
FMU1
11
15
Cabinet 2
(RFC)
FMU2
11
14
Cabinet 3
(RFC)
FMU3
11
15
Cabinet 0
(APM30)/
Cabinet 0
(BBC)
BBC/
TCU0
23
Cabinet 0
(APM30)/
Cabinet 1
(BBC)
BBC/
TCU1
10
24
Cabinet 1
(APM30)/
Cabinet 0
(BBC)
BBC/
TCU0
11
23

116
BSC6900 GSM
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 1
(APM30)/
Cabinet 1
(BBC)
BBC/
TCU1
12
24
Cabinet 2
(APM30)/
Cabinet 0
(BBC)
BBC/
TCU0
13
25
Cabinet 2
(APM30)/
Cabinet 1
(BBC)
BBC/
TCU1
14
26
Cabinet 0
(AMP30)
EMU/
EMUA
40
Cabinet 0
(AMP30)
GATM0
50
22
Cabinet 0
(AMP30)
GATM1
51
22
Table 10-25 lists rules of configuring monitoring boards of the BTS3900.

Table 10-25 Rules of configuring monitoring boards of the BTS3900
Issue 03 (2011-08-31)
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 0
(indoor
macro
BTS3900
cabinet)
FMU0
11
14
Cabinet 1
(indoor
macro
BTS3900
cabinet)
FMU1
11
15

117
BSC6900 GSM
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 2
(indoor
macro
BTS3900
cabinet)
FMU2
11
14
Cabinet 0
(indoor
macro
BTS3900
cabinet)
PMU0
Cabinet 1
(indoor
macro
BTS3900
cabinet)
PMU1
Cabinet 2
(indoor
macro
BTS3900
cabinet)
PMU2
BTS3900
cabinet (or
wallmounted)
EMU/
EMUA
40
Cabinet 0
(AMP30)
GATM0
50
22
Cabinet 0
(AMP30)
GATM1
51
22
Table 10-26 lists rules of configuring monitoring boards of the DBS3900.

Table 10-26 Rules of configuring monitoring boards of the DBS3900
Issue 03 (2011-08-31)
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 0
(AMP30)
PMU0
20

118
BSC6900 GSM
Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 1
(AMP30)
PMU1
21
Cabinet 0
(AMP30)
TCU0
20
Cabinet 1
(AMP30)
TCU1
21
Cabinet 0
(TMC)
TCU2
28
Cabinet 0
(APM30)/
Cabinet 0
(BBC)
BBC/
TCU0
29
23
Cabinet 0
(APM30)/
Cabinet 1
(BBC)
BBC/
TCU1
30
24
Cabinet 1
(APM30)/
Cabinet 0
(BBC)
BBC/
TCU0
31
23
Cabinet 1
(APM30)/
Cabinet 1
(BBC)
BBC/
TCU1
32
24
Cabinet 0
(AMP30)
EMUA
20
40
Cabinet 0
(OMB)
PMU0
Cabinet 0
(OMB)
TCU0
Cabinet 1
(OMB)
TCU1
Table 10-27 lists rules of configuring monitoring boards of the BTS3900L.
Issue 03 (2011-08-31)

119
BSC6900 GSM
Table 10-27 Rules of configuring monitoring boards of the BTS3900L

Cabinet
No.
(Cabinet
Name)
Part No./
Part
Name
Cabinet
No.
Subrack
No.
Slot No.
Serial
Port No.
Commun
ication
Address
Cabinet 0
(indoor
macro
BTS3900
L cabinet)
FMU0
11
14
Cabinet 0
(indoor
macro
BTS3900
L cabinet)
FMU1
12
15
BTS3900
L cabinet
(or wallmounted)
EMU/
EMUA
40
Cabinet 0
(AMP30)
GATM0
50
22
Cabinet 0
(AMP30)
GATM1
51
22
10.3.7 Configuration Guidelines for Power Systems

This section describes the configuration guideline for the power system of a base station.
The configuration guideline for the power system of a base station is listed in Table 10-28.
Table 10-28 Configuration Guideline for the Power System of a Base Station
Physical Cabinet
APM Cabinets
Issue 03 (2011-08-31)
Silk Screen of a
Cabinet
Nameplate
Power System
(The types are
consistent with
the corresponding
values on the
LMT)
Description
APM30
APM30
APM30H
APM30
APM30(Ver.C)
APM30
APM100
APM100
APM200
APM200

120
BSC6900 GSM
Physical Cabinet
Silk Screen of a
Cabinet
Nameplate
Power System
(The types are
consistent with
the corresponding
values on the
LMT)
Description
PS4890
PS4890
EPS4890
BTS3900
BTS3900 XXXX
EPS4890
Only applies to the

alternating current
cabinet of the
BTS3900. xxxx
indicates the mode of
the BTS3900, such as
GSM or WCDMA.
BTS3900(Ver.C)
EPS4890
OMB
EPS4815
SC48200
SC48200
SC4850
SC48200
BTS3012AE
DPMU
Applies to the
scenario of reuse of
the doubletransceiver series
base stations.
BTS3012
DPMU
Applies to the
base stations.
BTS3012II
DPMU
Applies to the
base stations.
OMB
Solar power system
Double-transceiver
series base stations
10.3.8 List of User-Defined Alarm Ports

This section describes the mapping of user-defined alarm ports and cables of SingleRAN
BTS3900 series. The monitoring units of the BTS3900 series for monitoring external alarms are
EMU, TCU, UPEU, UEIU, FMU, and PMU.
EMU
The EMU is configured in slot 0 of subracks 40 to 59. Table 10-29 lists the mapping of EMU
user-defined alarms ports and cables.
Issue 03 (2011-08-31)

121
BSC6900 GSM
Table 10-29 List of EMU user-defined alarm ports
Issue 03 (2011-08-31)
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
S1+/S1-
N/A
N/A
S2+/S2-
Sensorequipped
cable
S3+/S3-
Ports for
monitoring
Boolean
signals
S4+/S4-
S5+/S5-
S6+/S6-
S7+/S7-
S8+/S8-
S9+/S9-
S10+/S10-
S11+/S11-
10
S12+/S12-
11
S13+/S13-
12
S14+/S14-
13
S15+/S15-
14
S16+/S16-
15
S17+/S17-
16
S18+/S18-
17
S19+/S19-
18
S20+/S20-
19
S21+/S21-
20
S22+/S22-
21
S23+/S23-
22
S24+/S24-
23
S25+/S25-
24
S26+/S26-
25
S27+/S27-
26
S28+/S28-
27

122
BSC6900 GSM
Port on the
Monitorin
g Unit
Port No.
S29+/S29-
28
S30+/S30-
29
S31+/S31-
30
S32+/S32-
31
Analog
sensor of the
current type:
24V1
(12V1)/
ANA1
32
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
Ports for
monitoring
analog
signals
Analog
sensor of the
voltage type:
24V1
(12V1)/
ANA1/GND
Analog
sensor of the
current type:
24V2
(12V2)/
ANA2
33
Analog
sensor of the
voltage type:
24V2
(12V2)/
ANA2/GND
Analog
sensor of the
current type:
24V3
(12V3)/
ANA3
34
Analog
sensor of the
voltage type:
24V3
(12V3)/
ANA3/GND
Issue 03 (2011-08-31)

123
BSC6900 GSM
Port on the
Monitorin
g Unit
Port No.
Analog
sensor of the
current type:
24V4
(12V4)/
ANA4
35
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
Analog
sensor of the
voltage type:
24V4
(12V4)/
ANA4/GND
UPEU
The UPEU is configured in slot 18 or 19 of subracks 0. Table 10-30 lists the mapping of UPEU
Table 10-30 List of UPEU user-defined alarm ports
Issue 03 (2011-08-31)
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
EXT-ALM0
BBU
Boolean
alarm cable
X1.1/X1.2
Orangewhite/orange
Boolean
input 0+/
Boolean
input 0(GND)
X1.3/X1.6
Green-white/
green
Boolean
input 1+/
Boolean
input 1(GND)
10
X1.5/X1.4
Blue-white/
blue
Boolean
input 2+/
Boolean
input 2(GND)
11
X1.7/X1.8
Brownwhite/brown
Boolean
input 3+/
Boolean
input 3(GND)

124
BSC6900 GSM
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
EXT-ALM1
12
BBU
Boolean
alarm cable
X1.1/X1.2
Orangewhite/orange
Boolean
input 4+/
Boolean
input 4(GND)
13
X1.3/X1.6
Green-white/
green
Boolean
input 5+/
Boolean
input 5(GND)
14
X1.5/X1.4
Blue-white/
blue
Boolean
input 6+/
Boolean
input 6(GND)
15
X1.7/X1.8
Brownwhite/brown
Boolean
input 7+/
Boolean
input 7(GND)
UEIU
The UEIU is configured in slot 18 of subracks 0. Table 10-31 lists the mapping of UEIU userdefined alarms ports and cables.
Table 10-31 List of UEIU user-defined alarm ports
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
EXT-ALM0
BBU
Boolean
alarm cable
X1.1/X1.2
Orangewhite/orange
Boolean
input 0+/
Boolean
input 0(GND)
X1.3/X1.6
Green-white/
green
Boolean
input 1+/
Boolean
input 1(GND)
Issue 03 (2011-08-31)

125
BSC6900 GSM
Port on the
Monitorin
g Unit
EXT-ALM1
Port No.
Wire
Wire Color
Descriptio
n
X1.5/X1.4
Blue-white/
blue
Boolean
input 2+/
Boolean
input 2(GND)
X1.7/X1.8
Brownwhite/brown
Boolean
input 3+/
Boolean
input 3(GND)
X1.1/X1.2
Orangewhite/orange
Boolean
input 4+/
Boolean
input 4(GND)
X1.3/X1.6
Green-white/
green
Boolean
input 5+/
Boolean
input 5(GND)
X1.5/X1.4
Blue-white/
blue
Boolean
input 6+/
Boolean
input 6(GND)
X1.7/X1.8
Brownwhite/brown
Boolean
input 7+/
Boolean
input 7(GND)
Monitorin
g Signal
Cable
BBU
Boolean
alarm cable
TCU
The TCU is configured in slot 0 of subrack 8. Table 10-32 lists the mapping of TCU user-defined
alarms ports and cables.
Issue 03 (2011-08-31)

126
BSC6900 GSM
Table 10-32 List of TCU user-defined alarm ports

Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
IN1
N/A
N/A
IN2
Sensorequipped
cable
IN3
Descriptio
n
PMU
The PMU is configured in slot 0 of subrack 7. Table 10-33 lists the mapping of PMU userdefined alarms ports and cables.
Table 10-33 List of PMU user-defined alarm ports
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
N/A
Sensorequipped
cable
N/A
N/A
Descriptio
n
2
3
4
5
6
FMU
The FMU is configured in slot 0 of subracks 11 to 12. Table 10-34 lists the mapping of FMU
Table 10-34 List of FMU user-defined alarm ports
Issue 03 (2011-08-31)
Port on the
Monitorin
g Unit
Port No.
Monitorin
g Signal
Cable
Wire
Wire Color
SW0
N/A
N/A
SW1
Sensorequipped
cable
SW2
2
Descriptio
n
127
BSC6900 GSM
Port on the
Monitorin
g Unit
Port No.
SW3
Monitorin
g Signal
Cable
Wire
Wire Color
Descriptio
n
10.3.9 Guidelines for Configuring Send and Receive Modes for RF

Modules
This section describes how to configure send mode, receive mode, and send and receive mode
for radio frequency (RF) modules.
l
Send Mode can be set to PBT only when a DRFU or DRRU is configured with only one
carrier.
Send Mode can be set to Transmit Diversity only when a DRFU or DRRU is configured
with only one carrier and Send and Receive Mode is set to DOUBLETWO_ANTENNA
(Double Feeder[2TX+2RX] or DOUBLEFOUR_ANTENNA(Double Feeder[2TX
+4RX].
Receive Mode can be set to Four-Way Receive Diversity only when a DRFU is configured
with only one carrier and Send and Receive Mode is set to DOUBLEFOUR_ANTENNA
(Double Feeder[2TX+4RX].
Table 10-35 lists typical configurations of RF modules' send and receive modes.
Table 10-35 Typical configurations of RF modules' send and receive modes
RF Module
Send Mode
Receive
Mode
Send and
Receive
Mode
Number of
Carriers
DRFU
Transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S1
Four-way
receive
diversity
Double
feeder [2TX
4RX]
2/S2
Main
diversity
Single feeder 1/S2

[1TX 1RX]
Independent
transmit or
combination
Issue 03 (2011-08-31)
Double
feeder [1TX
2RX]

Remarks
If a DRFU
has a
cascaded
RXU, the
RXU must
be
configured.
1/S2
128
BSC6900 GSM
RF Module
Send Mode
Issue 03 (2011-08-31)
Send and
Receive
Mode
Number of
Carriers
Double
feeder [2TX
2RX]
1/S2
Remarks
Single feeder 2/S3-S4

[1TX 2RX]
If a DRFU
has a
cascaded
RXU, the
RXU must
be
configured.
Four-way
receive
diversity
Double
feeder [2TX
4RX]
2/S4
If a DRFU
has a
cascaded
RXU, the
RXU must
be
configured.
PBT
Main
diversity
Single feeder 2/S2

[1TX 2RX]
If a DRFU
has a
cascaded
RXU, the
RXU must
be
configured.
Dynamic
transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S2
Four-way
receive
diversity
Double
feeder [2TX
4RX]
1/S2
Main
diversity
Single feeder 1/S2

[1TX 1RX]
Main
diversity
Double
feeder [1TX
2RX]
Main
diversity

[1TX 2RX]
Dynamic
PBT
GRFU/
MRFU
Receive
Mode
Independent
transmit or
combination

1/S2
If a GRFU or
an MRFU
has a
cascaded
RXU, the
RXU must
be
configured.
129
BSC6900 GSM
RF Module
DRRU
Send Mode
Receive
Mode
Send and
Receive
Mode
Number of
Carriers
Main
diversity
Double
feeder [1TX
2RX]
1/S3-S6
Transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S1
Independent
transmit or
combination
Main
diversity
Single feeder 1/S2

[1TX 1RX]
Double
feeder [1TX
2RX]
1/S2
Double
feeder [2TX
2RX]
1/S2

[1TX 2RX]
If a DRRU
has a
cascaded
RXU, the
RXU must
be
configured.
If a DRRU
has a
cascaded
RXU, the
RXU must
be
configured.
PBT
Main
diversity
Single feeder 2/S2

[1TX 2RX]
Dynamic
transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S2
Double
feeder [2TX
4RX]
1/S2
Dynamic
PBT
Main
diversity
Single feeder 1/S2

[1TX 1RX]
Double
feeder [1TX
2RX]
Issue 03 (2011-08-31)
Remarks

1/S2
130
BSC6900 GSM
RF Module
GRRU/
MRRU
Send Mode
Receive
Mode
Send and
Receive
Mode
Number of
Carriers
Double
feeder [1TX
1RX]
1/S2
Transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S3-S8
Independent
transmit or
combination
Main
diversity
Double
feeder [1TX
2RX]
1/S3-S8

[1TX 2RX]
Dynamic
transmit
diversity
Main
diversity
Double
feeder [2TX
2RX]
1/S3-S8
Double
feeder [2TX
4RX]
1/S3-S8
Remarks
If a GRRU or
an MRRU
has a
cascaded
RXU, the
RXU must
be
configured.
10.3.10 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 Multi-Mode Base Station
Typical TRX Power.
10.3.11 Configuration Guidelines for 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.
Issue 03 (2011-08-31)

131
BSC6900 GSM
Table 10-36 Configuration rules of the BTS clock sources

Clock Mode
BT
S
Boa
rd
BTS
Mod
el
Trans
missi
on
Mode
Inte
rnal
Clo
ck
Tra
ce
BS
C
Clo
ck
Exte
rnal
Syn
c
cloc
k
IP
Clo
ck
Tra
ce
Tra
nsp
ort
Clo
ck
Trac
e
GPS
Cloc
k
Um
Cloc
k
Peer
Cloc
k
Syn
Eth
Cloc
k
GT
MU
DBS3
900
BTS3
900
BTS3
900A
BTS3
900L
IP
over
FE
Sup
port
ed
Not
supp
orte
d
Sup
port
ed
Sup
port
ed
Sup
port
ed
Supp
orted
Not
supp
orted
Supp
orted
Supp
orted
IP
over
E1
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Supp
orted
Not
supp
orted
HDL
C
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Supp
orted
Not
supp
orted
TDM
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Supp
orted
Not
supp
orted
IP
over
FE
Sup
port
ed
Not
supp
orte
d
Sup
port
ed
Sup
port
ed
Sup
port
ed
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
IP
over
E1
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
HDL
C
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
TDM
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
HDL
C
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
DT
MU
DO
MU
Issue 03 (2011-08-31)
Clock Source Type
BTS3
012
BTS3
012A
E
BTS3
012II
BTS3
006C
BTS3
002E

132
BSC6900 GSM
Clock Mode
BT
S
Boa
rd
BTS
Mod
el
Clock Source Type
Trans
missi
on
Mode
Inte
rnal
Clo
ck
Tra
ce
BS
C
Clo
ck
Exte
rnal
Syn
c
cloc
k
IP
Clo
ck
Tra
ce
Tra
nsp
ort
Clo
ck
Trac
e
GPS
Cloc
k
Um
Cloc
k
Peer
Cloc
k
Syn
Eth
Cloc
k
TDM
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
BT
S39
00B
BTS3
900B
IP
over
FE
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Sup
port
ed
Not
supp
orte
d
Not
supp
orted
Supp
orted
Supp
orted
Supp
orted
BT
S39
00E
BTS3
900E
IP
over
FE
Sup
port
ed
Not
supp
orte
d
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
HDL
C
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Not
supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
TDM
Sup
port
ed
Sup
port
ed
Sup
port
ed
Not
supp
orte
d
Not
supp
orte
d
Not
supp
orted
Not
supp
orted
Not
supp
orted
Not
supp
orted
10.3.12 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-24 shows the star topology.
Issue 03 (2011-08-31)

133
BSC6900 GSM
Figure 10-24 Star topology
The advantages of the star topology are as follows:

l
Simple network structure
Easy engineering implementation
Convenient network maintenance
Flexible capacity expansion
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-25
shows the chain topology.
Figure 10-25 Chain topology
Advantages: The chain topology can reduce the costs of transmission equipment and engineering
construction and save the rent for the transmission links.
Issue 03 (2011-08-31)

134
BSC6900 GSM
Disadvantages:
l
The reliability of the transmission link is poor because the signal transmission passes
through multiple nodes.
A faulty BTS may affect the normal operation of its lower-level BTSs.
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-26 shows the bypass function of the BTS.
Figure 10-26 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-27 shows the tree topology.
Issue 03 (2011-08-31)

135
BSC6900 GSM
Figure 10-27 Tree topology
Advantages: The number of transmission cables required in the tree topology is smaller than
that in the star topology.
Disadvantages:
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.
A faulty BTS may affect the normal operation of its lower-level BTSs.
It is inconvenient to expand the capacity of the network.
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, 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-28 shows the ring topology.
Issue 03 (2011-08-31)

136
BSC6900 GSM
Figure 10-28 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.13 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-29 shows the TDM-based networking on the Abis interface.
Figure 10-29 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.14 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.
Issue 03 (2011-08-31)

137
BSC6900 GSM
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-30.
Figure 10-30 IP over E1 Networking
IP over Ethernet Networking (Layer 2)

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-31 shows the IP over Ethernet
networking (layer 2).
Figure 10-31 IP over Ethernet networking (layer 2)
IP over Ethernet Networking (Layer 3)

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-32 shows the IP over Ethernet networking
(layer 3).
Issue 03 (2011-08-31)

138
BSC6900 GSM
Figure 10-32 IP over Ethernet networking (layer 3)
Features of Networking Modes

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

The base station provides large-capacity bandwidth through FE/GE ports, facilitating
the upgrade and capacity expansion.
The transmission network supports the evolution from the GSM TDM network to the
IP network.
Disadvantages:
l
This networking mode does not meet the requirements of the evolution from the telecom
network to the IP network.
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.15 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.
The quantity of "x"s represents the number of cells.
The value of "x" indicates the number of TRXs under each cell.
Issue 03 (2011-08-31)

139
BSC6900 GSM
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
S2/2/2
S4/4/4
S6/6/6
S8/8/8
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.16 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:
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.
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.
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.
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.
Packet Data Traffic Channel (PDCH)

The transmission rate is 16kbit/s. There are two types PDCH, static PDCH and dynamic
PDCH, static PDCH can only use for the PS and dynamic PDCH can use both PS and CS.
Issue 03 (2011-08-31)

140
BSC6900 GSM
we need configure SPDCH in the cell and dynamic PDCH can be transferred from TCHF
according to the PS traffic service.
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.
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
2:1
3:1
4:1
5:1
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.
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.17 Instances of BTS Multiplexing Modes

This section describes the E1 timeslot assignment in 1:1, 2:1, 3:1, and 4:1 multiplexing modes.
In the Abis interface, there are two types of timeslots: signaling timeslots and traffic timeslots.
Signaling timeslots are used for the OML and RSLs. Traffic timeslots consist of idle timeslots,
TCHs, PDCHs, and monitoring timeslots (optional). The OML and RSLs have a data rate of 64
kbit/s. Idle timeslots, TCHs, PDCHs, and monitoring timeslots (optional) have a data rate of 16
Issue 03 (2011-08-31)

141
BSC6900 GSM
kbit/s. Signaling links can be multiplexed to save the timeslots on the Abis interface. Signaling
timeslots cannot be multiplexed with traffic timeslots on the same 64 kbit/s timeslots.
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-37 lists the timeslot assignment on the Abis
interface.
Table 10-37 Timeslot assignment in 1:1 multiplexing mode
Issue 03 (2011-08-31)
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
RSL00
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
RSL01
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
RSL02
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
10
RSL03
11
T03C2
T03C3
T03C4
T03C5
12
T03C6
T03C7

142
BSC6900 GSM
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
...
31
OML0

interface.
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
RSL01+RSL02
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
RSL03
T03C2
T03C3
T03C4
T03C5
10
T03C6
T03C7
11
...
31
Issue 03 (2011-08-31)
OML0+RSL00

143
BSC6900 GSM

interface.
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
RSL02+RSL03
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
11
T03C2
T03C3
T03C4
T03C5
12
T03C6
T03C7
13
...
31
OML0+RSL00+RSL01

interface.
Issue 03 (2011-08-31)
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5

144
BSC6900 GSM
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
T00C6
T00C7
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
RSL03
T03C2
T03C3
T03C4
T03C5
T03C6
T03C7
10
...
31
OML0+RSL00+RSL01+RSL02
Instances of the Physical 16 kbit/s Multiplexing Mode

Table 10-41 lists the timeslot assignment on the Abis interface in the physical 16 kbit/s
multiplexing mode.
Table 10-41 Instances of the physical 16 kbit/s multiplexing mode
Timesl
ot
Numb
er
Sub-Timeslot Number
0 and 1
2 and 3
4 and 5
6 and 7
Synchronization
Synchronization
Synchronization
Synchronization
Traffic timeslot
Traffic timeslot
Traffic timeslot
Traffic timeslot
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
...
10.3.18 Timeslot Assignment on the Abis Interface

This describes the principles and algorithm of timeslot assignment on the Abis interface.
Issue 03 (2011-08-31)

145
BSC6900 GSM
NOTE
l Physical 16 kbit/s multiplexing refers to the permanent assignment of a 16 kbit/s timeslot to a channel.
The channel exclusively uses this 16 kbit/s timeslot.
l Statistical multiplexing means that n channels use one 64 kbit/s timeslot. Each channel uses the 64 kbit/
s bandwidth in a different time slice, that is, Time Division Multiplexing (TDM). In statistical
multiplexing mode, more than one channel is multiplexed onto one 64 kbit/s bandwidth.
l DML: Dynamic Maintenance Link. During the loading of the BTS software, the software is loaded on
the OML/EML, besides, the transmission resources allocated to the RSL or TCHs are dynamically preempted to establish the extended loading links to load the software simultaneously. In this way, the
software loading is accelerated. After the software is successfully loaded, the extended links are
released and the pre-empted transmission resources are reallocated to the TCHs or RSL. Then, the
allocation of transmission resources on the Abis interface is restored.
Principles of Timeslot Assignment on the Abis Interface

The principles of timeslot assignment on the Abis interface are as follows:
l
The n:1 statistical multiplexing and physical 16 kbit/s multiplexing cannot coexist on one
link.
The OMLs, RSLs, ESLs, idle timeslots, monitoring timeslots, and TCHs are assigned based
on sub-timeslots.
In physical 16 kbit/s multiplexing mode, any of the OMLs, RSLs, idle timeslots, monitoring
timeslots, and TCHs can coexist on one 64 kbit/s timeslot.
When using the n:1 64 kbit/s statistical multiplexing mode, adhere to the following
principles:
The timeslots of different BTSs cannot be multiplexed onto one 64 kbit/s timeslot.
Traffic channels and signaling channels cannot be multiplexed onto one 64 kbit/s
timeslot.
One 64 kbit/s timeslot must be used even if one signaling channel or traffic channel is
configured.
Monitoring timeslots cannot share the same 64 kbit/s timeslot with other timeslots,
except for the semipermanent connection.
In different E1s of cascaded BTSs, all the objects multiplexed onto one 64 kbit/s timeslot
must stay in the same 64 kbit/s timeslot and the relative positions of their corresponding
sub-timeslot numbers must remain the same.
The timeslots of different device groups in one BTS cannot be transmitted on the 64
kbit/s bandwidth of the same E1.
Idle timeslots and the timeslots on TRXs cannot use the same 64 kbit/s bandwidth with
the semipermanent connection.
The number of OMLs for the GEIUB/GOIUB cannot exceed 384.
The number of RSLs for the GEIUB/GOIUB cannot exceed 384.
The number of OMLs for one GEHUB/GFGUB/GOGUB cannot exceed 384.
The number of RSLs for one GEHUB/GFGUB/GOGUB cannot exceed 384.
For details about specifications of other interface boards, refer to the maximum number
of TRXs supported by each interface board.
Issue 03 (2011-08-31)
When BTSs, cells, TRXs, idle timeslots, or monitoring timeslots are added, timeslots on
the Abis interface must be assigned. The resources on the Abis interface should be assigned
to the following objects: OMLs, RSLs, traffic channels, idle timeslots, and monitoring
timeslots.
146
BSC6900 GSM
Algorithm of Timeslot Assignment on the Abis Interface

The algorithm of timeslot assignment on the Abis interface is as follows:
l
Each E1 port of the BTS manages sub-timeslots 0-255. Sub-timeslots 0-7 are used for
synchronization. They cannot be assigned to any object.
The OML is assigned timeslot 31 on port 0 of the local BTS. In n:1 statistical multiplexing
mode, the OML is assigned to sub-timeslot 0 of timeslot 31; in physical 16 kbit/s
multiplexing mode, the OML is assigned to sub-timeslot 3 of timeslot 31.
Except for the incoming E1 timeslot, the E1 port directly connected to the BSC is selected
preferentially during the timeslot assignment of the upper-level BTS.
Monitoring timeslots and idle timeslots can be assigned only on the ports of the basic
cabinets in the basic cabinet groups.
Lower-level BTSs can be established only on the ports of the basic cabinets in the basic
cabinet groups.
Before the OML between the BTS and the BSC is established, the BTS scans different
timeslots and tries to establish the OML to the BSC. The number of BTS cascades is limited
to reduce the link setup time.
10.3.19 Timeslot Arrangement on the Abis Interface

During the operations involving timeslot assignment on the BSC6900 Local Maintenance
Terminal, if timeslot assignment fails, you can run MML commands to arrange timeslots for the
activated BTSs.
Assume that there are two cascaded BTSs. Level 1 BTS uses timeslots 4-59, and level 2 BTS
uses timeslots 68-127. Four idle timeslots of level 1 BTS are deleted, and timeslots 6, 7, 8, and
9 are released. A new TRX is added to level 2 BTS. The TRX carries six TCHs. Only two
complete 64 kbit/s timeslots and two 32 kbit/s timeslots are available. The RSLs cannot be
multiplexed onto the TCHs and the timeslots of different BTSs also cannot be multiplexed.
Therefore, timeslot resources are insufficient.
In this event, you run the MML command TID BTSABISTS to arrange timeslots.
l
If the existing timeslot distribution meets the requirements for BSC arrangement, the BSC
starts to arrange timeslots.
If the existing timeslot distribution does not meet the requirements for BSC arrangement,
you need to add physical E1 links and run the MML command ADD BTSCONNECT to
add the corresponding site chains on the LMT.
You can use the following methods to arrange timeslots to meet the requirement of the newly
added TRX for timeslots.
l
Arrange the timeslots of level 1 BTS. Move the services on timeslots 4 and 5 to timeslots
8 and 9. Therefore, an E1 contains three complete 64 kbit/s timeslots. There are sufficient
timeslot resources to add a TRX.
The RSL of the added TRX can use timeslots 4, 5, 6, and 7. The remaining two complete
64 kbit/s timeslots can be assigned to six TCHs.
Table 10-42 shows the timeslot distribution on the Abis interface before timeslot arrangement
by the BSC.
Issue 03 (2011-08-31)

147
BSC6900 GSM
Table 10-42 Timeslot distribution on the Abis interface before timeslot arrangement by the BSC
Timeslot
Sub-Timeslot
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
Used by level 1
site
Used by level 1
site
Idle
Idle
Idle
Idle
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
...
...
...
...
...
12
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
13
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
14
Idle
Idle
Idle
Idle
15
Idle
Idle
Idle
Idle
16
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
17
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
...
...
...
...
...
30
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
31
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
Table 10-43 shows the timeslot distribution on the Abis interface after timeslot arrangement by
the BSC.
Table 10-43 Timeslot distribution on the Abis interface after timeslot arrangement by the BSC
Timeslot
Issue 03 (2011-08-31)
Sub-Timeslot
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
Idle
Idle
Idle
Idle

148
BSC6900 GSM
Timeslot
Sub-Timeslot
0, 1
2, 3
4, 5
6, 7
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
...
...
...
...
...
12
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
13
Used by level 1
site
Used by level 1
site
Used by level 1
site
Used by level 1
site
14
Idle
Idle
Idle
Idle
15
Idle
Idle
Idle
Idle
16
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
17
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
...
...
...
...
...
30
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
31
Used by level 2
site
Used by level 2
site
Used by level 2
site
Used by level 2
site
The process of timeslot arrangement by the BSC is as follows:

l
The BSC releases all the timeslots that are used by the cascaded BTSs except for the
timeslots assigned manually.
The BSC reassigns timeslots for each object.
If the reassignment of timeslots fails, a timeslot arrangement failure message is displayed.
The manual assignment of Abis timeslots does not involve timeslot arrangement.
If the timeslot arrangement fails, the timeslot distribution before the timeslot arrangement
is restored.
10.3.20 Manual Timeslot Assignment on the Abis Interface

This describes the manual timeslot assignment on the Abis interface. Timeslot assignment on
the Abis interface is required when you add BTSs, cells, TRXs, idle timeslots, and monitoring
timeslots. By default, the timeslots are assigned automatically. You can also manually assign
the OML timeslots on the Abis interface if required.
You can run the MML command SET BTSOMLTS to manually allocate OML timeslots or run
the MML command SET BTSFORBIDTS to inhibit a timeslot segment.
Issue 03 (2011-08-31)

149
BSC6900 GSM
When manually assigning timeslots on the Abis interface, adhere to the following principles:
l
The objects that support manual timeslot assignment are OMLs.
When BTSs are cascaded, only the OML timeslots for the current level BTS can be allocated
manually.
The occupied source timeslots are cleared and then allocated again.
The multiplexing mode of assigned timeslots must be the same as the multiplexing mode
of the BTS. If the BTS uses the 2:1 multiplexing mode, do not multiplex four signaling
links together.
You can run the MML command CLR BTSMANUAL to clear the Abis timeslot resources
manually set. When you change the assignment mode of the timeslots of an object from
manual mode to auto mode, the timeslots are released and assigned automatically. When
you change the assignment mode of the timeslots of an object from auto mode to manual
mode, the Abis timeslots automatically assigned for the object are released.
When inhibiting timeslots, adhere to the following principles:

l
After a timeslot segment is inhibited, the source timeslots are released and then allocated
again. After the timeslot segment is uninhibited, the source timeslots do not return.
Timeslots allocated manually cannot be inhibited.
If a BTS is connected to a BSC directly and the timeslot segment on the BSC side is occupied
semi-permanently, the timeslot segment cannot be prohibited.
10.3.21 Semipermanent Connection

Semipermanent connection refers to the transmission channel comprised of some idle timeslots
in the existing network. The semipermanent connection is used to transfer business hall
information, alarm information about the BTS AC power supply, and other maintenance
information.
When the network operator needs to transmit some data from one terminal to another terminal
and the data does not have a high requirement for the transmission bandwidth, the idle
transmission resources in the GSM network can be specially used to transfer the data.
Semipermanent connection is a transparent channel that can be used to transmit information
specified by a subscriber. The BSC provides the semipermanent connection of four rates: 8 kbit/
s, 16 kbit/s, 32 kbit/s, and 64 kbit/s.
There are two types of semipermanent links in the BSS system:
l
Semipermanent connection
Connection configured between interface boards.
Monitoring timeslot
Connection configured between the interface board and the BTS. The rates of monitoring
timeslots are 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. You can assign multiple monitoring
timeslots for the BTSs on a link at a time.
10.3.22 Principles of Idle Timeslot Assignment

This describes the principles of idle timeslot assignment. The idle timeslots carry the GPRS
services in the BSS.
The principles of idle timeslot assignment are as follows:
Issue 03 (2011-08-31)

150
BSC6900 GSM
Idle timeslots are configured in the unit of BTS cabinet groups. Each BTS cabinet group
can be added with a maximum of 128 idle timeslots at a time. A BTS can be configured
with 512 idle timeslots.
You can run the MML command SET BTSIDLETS to configure the number of idle
timeslots for a single BTS.
10.3.23 Configuration Guidelines for DFCU/DFCB

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.
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.
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.
In the antenna feeder connections of one DFCU, a maximum of four TRXs can be
configured.
In the antenna feeder connections of the DFCU, none of the TRXs can be configured with
RF FH.
In the antenna feeder connections of the DFCU, the spacing between any two TRXs must
be at least three frequencies.
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.
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

l
A TRX is connected to tributary A or B of the DFCB based on actual conditions.
Both tributary A and tributary B of the DFCB can be configured with a maximum of two
TRXs.
Issue 03 (2011-08-31)

151
BSC6900 GSM
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.
In the antenna feeder connections of the DFCB, none of the TRXs can be configured with
RF FH.
In the antenna feeder connections of the DFCB, the transmit mode of any TRX cannot be
set to wideband combination.
The DFCB does not require extension connections. The extension connections are
configured on the DFCU.
10.3.24 Configuration Guidelines for 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-44 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 do not need to modify the
cabinet type.
The cabinet numbers, subrack numbers, and slots numbers for the boards in the BBU do not
need to 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.
Issue 03 (2011-08-31)

152
BSC6900 GSM
Upgrading a BTS of version 8.x that does not support the filler panel to a BTS of version
9.0
Table 10-45 Configuration rules of upgrading the RFU (not supporting the filler panel)
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]
[Cabinet X,
Subrack 4, Slot Y]
BTS3900
BTS3900A
[Cabinet X,
Subrack 3, Slot Y]
[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-46 Configuration rules of upgrading the RFU (supporting the filler panel)
Issue 03 (2011-08-31)
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
BTS390
0
CPRI
ports
connect
ed in the
star
topolog
y
N (0 <=
N <= 5)
BTS390
0A
CPRI
ports
connect
ed in the
star
topolog
y
N (0 <=
N <= 5)

153
BSC6900 GSM
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
BTS390
0
CPRI
ports at
two
levels of
cascadin
g
N (0 <=
N <= 5)
H (0 <=
H <= 1)
N%2
INT(N/
2) * 2 +
H
BTS390
0A
CPRI
ports at
two
levels of
cascadin
g
N (0 <=
N <= 5)
H (0 <=
H <= 1)
N%2+
1
INT(N/
2) * 2 +
H
BTS390
0
CPRI
ports at
three
levels of
cascadin
g
N (0 <=
N <= 5)
H (0 <=
H <= 2)
N/2
(N % 2)
*3+H
BTS390
0A
CPRI
ports at
three
levels of
cascadin
g
N (0 <=
N <= 5)
H (0 <=
H <= 2)
N/2 + 1
(N % 2)
*3+H
Upgrade of the RRU

Table 10-47 Configuration rules of upgrading the RRU
Issue 03 (2011-08-31)
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.

154
BSC6900 GSM
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-48 IP addresses of the monitoring boards
Monitoring Board
Communication Address
EMU
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.
Issue 03 (2011-08-31)

155
BSC6900 GSM
Table 10-49 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
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
respectively. If two
GATMs are used, the
of the other GATM are
respectively.
One BTS has at most two

GATMs.

parameters of the GATM
and add the relation
information of the
management object.
Issue 03 (2011-08-31)

156
BSC6900 GSM
Monitoring Board
Description
Remarks
Local DPMU/APMU
l If only one DPMU/

APMU is used, the
of the DPMU/APMU are
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.
Issue 03 (2011-08-31)

157
BSC6900 GSM
Monitoring Board
Description
Remarks
l The DPMU/APMU is
renamed PMU.
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.4 Data Configuration Guidelines for Specifications

This document describes the specifications of the BSC6900.
Table 10-50 lists the specifications of the BSC6900.
Table 10-50 BSC6900 specifications
Issue 03 (2011-08-31)
Item
Specification
Maximum Number of TRXs
4096
Maximum Number of GSM Cells
2048
Maximum Number of External Neighboring GSM Cells
10240
Maximum Number of External Neighboring UMTS Cells
10240
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

64
Maximum Number of External Neighboring UMTS Cells

64

158
BSC6900 GSM
Issue 03 (2011-08-31)
Item
Specification
Number of OSPs Supported by a BSC
Number of DSPs
187
Maximum Number of MTP3 (MTP3 & MTP3b) Link Sets
187
Maximum Number of MTP (MTP3 & MTP3b) Links

Supported by an MTP Link Set
16
Maximum Number of MTP Links
2992
Maximum Number of MTP Routes
374
Maximum Number of MTP3 Links Supported by a CPUS
50
Maximum Number of SCTP Links Supported by a CPUS
15
Maximum Number of M3UA Links Supported by a CPUS
15
Maximum Number of M3UA Link Sets
187
Maximum Number of M3UA Links
1024
Maximum Number of M3UA Destination Entities
187
Maximum Number of M3UA Local Entities
187
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
Maximum Number of Signaling Links over Ater Interface

Supported by a TC
64
Maximum Number of Signaling Links over Pb Interface
256
Total Number of Routes
4096
Number of Routes on FG2c/GOUc
512

159

BSC6900 GSM Initial Configuration Guide V900R013C00 03 PDF en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 GSM Initial Configuration Guide V900R013C00 03 PDF en

Uploaded by

Copyright:

Available Formats

BSC6900 GSM

Initial Configuration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Huawei Proprietary and Confidential

About This Document

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

7 Configuring the Equipment Data.............................................................................................12

8 Configuring the Interfaces.........................................................................................................20

Huawei Proprietary and Confidential

8.7 Configuring the Pb Interface............................................................................................................................30

10 Configuration Reference Information...................................................................................68

Huawei Proprietary and Confidential

10.3.5 Configuration Rules of the BTS Boards..............................................................................................109

Huawei Proprietary and Confidential

1 Changes in the BSC6900 GSM Initial Configuration Guide

Changes in the BSC6900 GSM Initial

10.3.18 Timeslot Assignment on the Abis Interface

10.3.19 Timeslot Arrangement on the Abis Interface

10.3.20 Manual Timeslot Assignment on the Abis Interface

10.3.21 Semipermanent Connection

10.3.22 Principles of Idle Timeslot Assignment

9.6.1 Configuring the Neighboring Cell

The configurations of LTE external cells are

10.3.7 Configuration Guidelines for Power

The APM30(Ver.C) and the BTS3900

10.3.3 Configuration Guidelines for Slot

The description of the UBRI board is

Huawei Proprietary and Confidential

1 Changes in the BSC6900 GSM Initial Configuration Guide

GSM Data Preparation for the Initial

The recommended configurations of some

Configuring the Clocks

The procedure for configuring the external

Data Configuration Principles for Numbering