Professional Documents
Culture Documents
BSC6900 GSM Initial Configuration Guide PDF
BSC6900 GSM Initial Configuration Guide PDF
V900R013C00
Issue 03
Date 2011-08-31
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.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes the initial configuration of BSC6900.
Product Version
The following table lists the product version related to this document.
BSC6900 V900R013C00
Intended Audience
This document is intended for:
l Field engineers
l Network operators
l 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
This chapter describes the process of creating the initial configuration script for the BSC6900.
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.
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.
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.
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.
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
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
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.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
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
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
l 10.3.19 Timeslot Arrangement on the Abis Interface
l 10.3.20 Manual Timeslot Assignment on the Abis Interface
l 10.3.21 Semipermanent Connection
l 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 The configurations of LTE external cells are
Relations added.
10.3.7 Configuration Guidelines for Power The APM30(Ver.C) and the BTS3900
Systems (Ver.C) are added.
10.3.3 Configuration Guidelines for Slot The description of the UBRI board is
Numbers 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:
Content Description
GSM Data Preparation for the Initial The recommended configurations of some
Configuration parameters are added.
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
l 9.6.6 Configuring IP Port Backup
l 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
Compared with issue 04 (2010-11-30) of V900R012C01, this issue does not exclude any topics.
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.
l During commissioning, the script is imported to the BSC6900. For data modification after
the BSC6900 starts operating, see the GBSS Reconfiguration Guide.
l 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.
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.
This chapter describes the process of creating the initial configuration script for the BSC6900.
Figure 4-1 shows the initial configuration process.
For details about loading the BSC6900 initial configuration data, see the BSC6900 GSM
Commissioning Guide.
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.
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.
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.
Prerequisite
l All the subracks are switched to the ineffective mode by running the SET
CFGDATAINEFFECTIVE command.
l The basic data is not configured.
Procedure
Step 1 Run the SET BSCBASIC command to set the basic GSM data.
Step 2 Run the ADD GCNOPERATOR command to add a primary GSM operator. 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
Prerequisite
l The basic data of the BSC6900 has been configured. For details, see Configuring the Basic
Data.
Context
l 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.
l The network ID and the signaling point code must be planned in the SS7 network.
l 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.
Procedure
Step 1 Run the ADD OPC command to add an OPC, repeat this step until all desired OPCs are added.
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
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
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
This section describes how to configure alarm ports, alarm IDs, and alarm names of the
BSC.
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
Prerequisite
The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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
Prerequisite
The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.
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.
Context
l For the data to be negotiated and planned for configuring a board for the BSC6900, see
Data Preparation for Initial Configuration.
l For details 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.
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
Prerequisite
The subrack for housing the EMU is already configured.
Context
l The EMU gathers Boolean values, analog values, and alarm threshold information and
reports them to the LMT.
l One cabinet can be configured with only one EMU.
Procedure
Step 1 Run the ADD EMU command to add an EMU.
----End
Prerequisite
The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.
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.
l 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
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
Procedure
l Configuring the external clock
1. Run the ADD CLKSRC command to add a system clock source and the clock source
priority.
NOTE
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. Run the ADD CLKSRC command to add a system clock source and the clock source
priority.
3. Run the SET CLKMODE command to set the work mode of the system clock source.
NOTE
----End
Follow-up Procedure
To reconfigure the system clock source and clock source priority, run the SET CLKMODE
command.
Prerequisite
The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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
Prerequisite
l An environment monitoring unit and the sensor regarding environment alarms are installed.
l 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
This chapter describes how to configure the GSM interfaces, including the Ater, A, Gb, and Pb
interfaces.
Prerequisite
l The subrack to be configured with an Ater connection path is configured.
l The EIUa/OIUa/POUc board is configured in the subrack to be configured with an Ater
connection path.
Context
l If the TCS is configured locally, the Ater connection path must be configured. If the TCS
is configured remotely, the Ater connection path, Ater OML, and Ater signaling link must
be configured and the Ater OML needs to be established only between the MPS and the
main TCS.
l The Ater connection path is established between EIUa boards or between OIUa boards.
You can specify different ports to configure more than one Ater connection path between
interface boards.
Procedure
l If the TCS is configured locally:
1. Configure an Ater connection path.
(1) Run the ADD ATERCONPATH command to add an Ater connection path
between the MPS and the TCS.
(2) In TC pool mode, run the ADD ATERE1T1 command to add an Ater connection
path between the BSC6900 and the TC.
l If the TCS is configured remotely:
1. Configure an Ater connection path.
(1) Run the ADD ATERCONPATH command to add an Ater connection path
between the MPS and the main TCS.
(2) In TC pool mode, run the ADD ATERE1T1 command to add an Ater connection
path between the BSC6900 and the TC.
2. Run the ADD ATEROML command to add an Ater OML between the MPS and the
main TCS.
NOTE
l At least four consecutive timeslots except timeslot 1 must be used for Ater OMLs.
l It is recommended that a pair of active and standby Ater OMLs be configured.
l If the BIOS version of the EIUa/OIUa board is earlier than 215, the 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. Run the ADD ATERSL command to add an Ater signaling link between the MPS/
EPS and the TCS.
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
Prerequisite
l A license for implementing IP transmission over the Ater interface has been obtained.
l The subrack to be configured with an Ater connection path is configured.
l The POUc board is configured in the subrack to be configured with an Ater connection
path.
l 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.
----End
Prerequisite
l The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
l The OPC and DPC are configured. For details, see Configuring the OPC and DPC.
l The EIUa/OIUa/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
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
The basic data of the BSC6900 has been configured. For details, see Configuring the Basic Data.
Procedure
Step 1 Set the Ethernet port attributes.
1. Run the LST ETHPORT command to list the attributes of the Ethernet port.
2. Optional: If the planned data is inconsistent with the default data, run the SET
ETHPORT command to set the attributes of the Ethernet port.
Step 2 Optional: Run the ADD ETHREDPORT command to configure Ethernet port backup.
Step 3 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.
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.
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
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
The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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 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 3 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform
the corresponding step.
----End
Configuring the Physical Layer and Data Link Layer for the POUc Board
This section describes how to configure the physical layer and data link layer for the POUc
board, which is used as the interface board of the BSC6900. You need to set the E1/T1 attributes,
optical port attributes, and attributes of a channelized optical port. In addition, you need to
configure the PPP link, MP link group, and MP link.
Prerequisite
The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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 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 4 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 5 Determine the type of link carried on the E1/T1 link (PPP link or MP link group) and perform
the corresponding step.
----End
Prerequisite
l The M3UA local and destination entities are configured. For details, see Configuring the
M3UA Local and Destination Entities.
l The physical layer and data link layer of the A interface are configured. For details, see
8.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.
----End
Prerequisite
The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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
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.
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
Prerequisite
l The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
l The DPUd/XPUa/PEUa board is configured. For details, see Configuring a Board.
Context
l At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified
by the NSEI.
l In Gb over FR mode, a BC is a physical bearer channel, which is composed of a certain
number of timeslots of the E1/T1.
l An NSVC is carried by a BC and belongs to only one BC and only one NSE, whereas a
BC or NSE can be configured with multiple NSVCs.
l An NSVC maps to a PVC. When configuring an NSVC, specify its mapping PVC.
l BSSGP is short for Base Station Subsystem GPRS Protocol.
l A GPRS cell refers to a cell that is GPRS enabled.
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
Prerequisite
l The basic data of the BSC6900 has been configured. For details, see Configuring the Basic
Data.
l The DPUd/FG2a/XPUa board is configured. For details, see Configuring a Board.
l A license for implementing IP transmission over the Gb interface is granted.
Context
l At the Network Service (NS) layer, NSE is represented by a set of NSVCs and is identified
by the NSEI.
l BSSGP is short for Base Station Subsystem GPRS Protocol.
l A GPRS cell indicates a cell that is GPRS capable.
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 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
Prerequisite
l The basic data of the BSC6900 is configured. For details, see Configuring the Basic Data.
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.
----End
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.
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
l 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
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.
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.
l Idle ports are available on interface boards.
Context
l Separate mode indicates that boards and carriers that are configured for a BTS must be
configured separately.
l 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.
Procedure
Step 1 Run the ADD BTS command to add a BTS.
Parameter Setting
Is Support Normalized Data Configuration For SingleRAN base stations, this parameter
must be set to SUPPORT(Support).
----End
Prerequisite
l The BTS data are configured. For details, see 9.1.1 Configuring a BTS.
Context
l The boards in the common slots are automatically added according to the default setting.
l Antenna boards and TRX boards need to be manually added.
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
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.
l Idle ports are available on interface boards.
l 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.
----End
Prerequisite
l The BTS boards are configured. For details, see 9.1.3 Configuring BTS Boards.
Context
l 3X series and double-transceiver series base stations
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.
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
Prerequisite
l The data of the operator is configured. For details, see Configuring the Basic Data.
l The OPC data is configured. For details, see Configuring the OPC and DPC.
l The equipment data of the BTS is configured. For details, see 9.1 Configuring 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
1. Run the ADD GCELL command to add a cell.
2. Run the ADD GCELLFREQ command to add frequencies to the cell.
3. Run the ADD GCELLOSPMAP command to add the mapping between the cell and
the originating signaling point.
4. Run the ADD GTRX command to add a TRX.
5. When the GPRS function is enabled, run the MML command SET GCELLGPRS to
set the GPRS attributes of the cell.
Step 2 Run the ADD CELLBIND2BTS command to add the binding relation between the cell and the
BTS.
Step 3 Run the ADD TRXBIND2PHYBRD command to add the binding relation between the logical
TRX and the physical TRX board.
Step 4 Run the SET GTRXCHAN command to set the channel attributes of the TRX.
Step 5 Run the SET GTRXDEV command to set the device attributes of the TRX.
----End
9.3.1 TDM/HDLC
This section describes how to configure the transmission data when the BTS is in TDM/HDLC
transmission mode.
Prerequisite
l The equipment data of the BTS is configured. For details, see 9.1 Configuring the
Equipment Data.
l The logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
Context
l All types of BTSs support TDM/HDLC transmission.
l The TDM/HDLC transmission networking, refer to 10.3.13 TDM-Based Networking on
the Abis Interface.
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
Prerequisite
l Equipment data of the BTS is configured. For details, see 9.1 Configuring the Equipment
Data.
l Logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
Context
l Double-transceiver and 3900 series base stations support IP over FE/GE transmission.
l For details about IP over FE/GE transmission networking, see 10.3.14 IP-Based
Networking on the Abis Interface.
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 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. Run the ADD BTSBFD command to add a BFD session on the BTS side.
2. Run the ACT IPPM command to start the IPPM function on the BSC6900 side.
3. Run the ACT BTSIPPM command to start the IPPM function on the BTS side.
Step 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 The equipment data of the BTS is configured. For details, see 9.1 Configuring the
Equipment Data.
l The logical data of the BTS is configured. For details, see 9.2 Configuring the Logical
Data.
Context
l Only the 3900 series base stations support IP over E1.
l The IP over E1 transmission networking, refer to 10.3.14 IP-Based Networking on the
Abis Interface.
Procedure
Step 1 Run the ADD BTSCONNECT command to add a connection between the BTS and the
BSC6900, between BTSs (including the internal connection of a BTS), or between the BTS and
the DXX. To add multiple BTS connections, run this command repeatedly.
Step 2 Determine the type of link carried on the E1/T1 link (PPP link or MLPPP group) and perform
the corresponding step.
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 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
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
Prerequisite
The BTS and its cells are already configured.
Procedure
Step 1 Run the CHK BTS command to check the data integrity of a BTS.
Step 2 Run the ACT BTS command to activate the configuration of a BTS.
----End
Context
l The cell on which an MS camps before the handover is called the originating cell. The cell
on which the MS will camp after the handover is called the target cell.
l The cells in the BSC6900 can be set to bidirectional neighboring cells or unidirectional
neighboring cells.
l An external cell, that is, a cell in another BSC6900, can be configured only as a
unidirectional neighboring cell.
Procedure
Step 1 Run the ADD GEXT2GCELL command to add a 2G external cell.
Step 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
Prerequisite
The data of the BTS is configured.
Context
l During network construction, the existing transmission links of the BTS can be used to
obtain the required monitoring data. This meets the maintenance requirements of operators,
monitors various data on the network, and reduces the transmission link costs. With regard
to hardware deployment, a monitoring terminal needs to be installed on the BTS side, and
a monitoring device needs to be installed on the BSC6900 side. In terms of software
configuration, some of the BTS timeslots need to be used as monitoring timeslots to transmit
monitoring data.
l The idle timeslots of the BTS are used to carry GPRS service data. If the idle timeslots of
the BTS do not meet the bandwidth requirement of GPRS traffic, additional idle timeslots
can be configured to increase the bandwidth available for GPRS traffic.
l Some of the allocated timeslots of a BTS can be disabled. This operation is applicable to
scenarios where leased transmission links are used. For example, an operator leases only
some timeslots on an E1 for traffic purposes.
Procedure
l Configuring the BTS monitoring timeslots
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 sub-
timeslots 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.
l Configuring the BTS idle timeslots
1. Run the SET BTSIDLETS command to configure idle timeslots of the BTS.
NOTE
Idle timeslots are configured on the basis of BTS cabinet groups. With respect to each cabinet group,
no more than 128 idle timeslots can be configured at a time. With respect to each BTS, a maximum
of 512 idle timeslots can be configured.
l Configuring the BTS forbidden timeslots
1. Run the SET BTSFORBIDTS command to disable or enable the timeslots of a BTS.
----End
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.
l 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.
----End
Prerequisite
l The monitoring board and the required cables are installed. For details, see the Hardware
Description of the base station.
l The monitoring board is configured. For details, see 9.1.3 Configuring BTS Boards.
l 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
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
Prerequisite
l A third-party power system is used, and batteries are used when the mains supply is
unavailable.
l The customized alarms, "No Mains Supply" and "DC Low Voltage", are configured. For
details, see 9.6.4 Configuring a Custom BTS Alarm.
l The alarms "No Mains Supply" and "DC Low Voltage" can be configured only on
customized alarm ports on the UPEU and UEIU.
l 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
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.
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
Prerequisite
l The equipment data of the BTS has been configured. For details, see 9.1 Configuring the
Equipment Data.
l The logical data of the BTS has been configured. For details, see 9.2 Configuring the
Logical Data.
l 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.
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 multi-
hop 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.
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
Prerequisite
l The equipment data of the BTS has been configured. For details, see 9.1 Configuring the
Equipment Data.
l The logical data of the BTS has been configured. For details, see 9.2 Configuring the
Logical Data.
l 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.
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
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.
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:
Seperate SUPPORT
Mode
Service IP
Type
Is Support SUPPORT
Normalize
d Data
Configurati
on
Cabinet
0, 1 Internal planning
No.
Is Support
Cabinet SingleRA SUPPORT
N Mode Network planning
Cabinet BTS3900
Type
Cabinet
0
No.
Slot No. 0
Chain No. 0
Head 0
Cabinet
Physical No.
Internal planning
TRX
Head 0
Subrack
No.
Head Slot 6
No.
Head Port 0
No.
Cabinet 0
No.
Network planning
Subrack 4
No.
Slot No. 0
RXU Chain 0
No.
Internal planning
RXU 1
Board
Position
The logical data that requires negotiation and planning is listed in Table 9-5:
Cell Index 8
MCC 460
Cell
Basic MNC 01
Informati Negotiation with the peer
on Cell LAC H'0001
Cell CI 1
Frequency
520
1 Network planning
OSP Code 163
TRX ID 8
TRX
Informati Frequency 520 Network planning
on
TRX No. 0, 1
Timeslot 1, 2
Priority
The transmission data that requires negotiation and planning is listed in Table 9-6.
BTS In Port
0
No.
In Port 0
Cabinet No.
In Port 0
Subrack
No.
BTS
Connecti In Port Slot 6 Network planning
on No.
Subrack 0
No.
Slot No. 26
Port No. 0
Subrack
0
PPP links No.
of BSC Internal planning
Slot No. 26
side
Board type PEUa
Logic Abis_IP
function
type
PPP link
0
No.
E1T1 port 0
No.
TS1-1&TS2-1&TS3-1&TS4-1
&TS5-1&TS6-1&TS7-1&TS8 Internal planning
Bearing
-1&TS9-1&TS10-1&TS11-1
time slot
&TS12-1&TS13-1&TS14-1&
TS15-1
Borrow NO
DevIP
Local IP
9.69.200.1
address
Subnet 255.255.255.0
Network planning
mask
Peer IP 9.69.200.192
address
PPP Link
0
No.
Port No. 0
Port 0
Cabinet No.
Port 0
Subrack
No. Internal planning
Local IP
9.69.200.192
Address
Network planning
Subnet 255.255.255.0
Mask
Peer IP 9.69.200.1
Address
Adjacent
0
Node ID
Adjacent IP
Adjacent Node Name Internal planning
Node
Adjacent ABIS
Node Type
Site Index 8
BTS PPP/MP
Communic
ation Type
BTS IP Network planning
BTS IP 9.69.200.192
BSC IP 9.69.200.1
IP path ID 0
Interface ABIS
Type
IP path type EF
IP path Network planning
Forward 1000
Bandwidth
Backward
1000
Bandwidth
The parameters of monitoring boards that require negotiation and planning are listed in Table
9-7.
FMU 0 11 0 0 14
FMU 1 11 0 0 15
GATM 0 50 0 0 22
GATM 0 51 0 1 22
EMU 0 40 0 1 2
BTS user-defined alarms that require negotiation and planning are listed in Table 9-8:
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;
ADD BTSCABINET: IDTYPE=BYID, BTSID=8, CN=1, SRANMODE=SUPPORT,
TYPE=BTS3900;
//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 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;
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.
Data Planning
The equipment data that requires negotiation and planning is listed in Table 9-9:
BTS Index 9
Internal planning
BTS Name BTS3900A_9
Service IP
Type
IP Phy IP_OVER_E1
Trans Type
Is Support SUPPORT
Normalize
d Data
Configurati
on
Cabinet
0, 1, 2, 3, 4 Internal planning
No.
Is Support
Cabinet SingleRA SUPPORT
N Mode Network planning
Cabinet APM30, RFC-6, TMC, BBC,
Type BBC,
Cabinet
0
No.
Slot No. 1, 2, 3
Chain No. 0
Head 0
Cabinet
No.
Head Port 0
No.
Subrack 4
No.
Slot No. 0, 1
RXU Chain 0
No.
Internal planning
RXU 1, 2
Board
Position
The logical data that requires negotiation and planning is listed in Table 9-10:
Cell Index 5, 6
MCC 460
Frequency
513, 517
1
The transmission data that requires negotiation and planning is listed in Table 9-11:
Port No. 1
Subrack 0
Number Internal planning
IP
address of Slot 19
an Number
Ethernet
port Local IP 166.101.121.220 Network planning
address
Subnet 255.255.0.0
mask
Port No. 0
Port 0
IP Cabinet No.
address Internal planning
and Subrack 0
informati No.
on of an
Slot No. 6
Ethernet
Port on a Physical IP 203.26.0.5 Network planning
BTS
IP Mask 255.255.255.0
MTU 1500
BTS
Communic PORTIP
ation Type
BTS IP Network planning
BTS IP 203.26.0.5
BSC IP 203.26.0.1
Adjacent
0
Node ID
Adjacent BTS3900A_9
Adjacent Node Name Internal planning
Node
Adjacent ABIS
Node Type
Site Index 9
IP path ID 0
Interface
ABIS
Type
IP path type EF
IP path Network planning
Forward
1000
Bandwidth
Backward
1000
Bandwidth
BTS clock data that requires negotiation and planning is listed in Table 9-12:
Clock
Protocol HW_DEFINED
Type
Clock UNSUPPORT
Reference
Source
BTS IP Redundanc
Clock y Network planning
Server
Clock 16.16.16.50
Server 0 IP
Address
Clock CONSYN
Synchroniz
ation Mode
The parameters of monitoring boards that require negotiation and planning are listed in Table
9-13:
PMU 0 7 0 1 3
TCU 0 8 0 1 7
TCU 2 8 0 0 6
TCU 3 8 0 1 23
TCU 4 8 0 1 24
FMU 1 11 0 0 14
GATM 0 50 0 0 22
GATM 0 51 0 1 22
BTS user-defined alarms that require negotiation and planning are listed in Table 9-14:
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;
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=0, SRANMODE=SUPPORT, TYPE=APM30;
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=2, SRANMODE=SUPPORT, TYPE=TMC;
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=3, SRANMODE=SUPPORT, TYPE=BBC,
CABINETDESC="IBBS";
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=4, SRANMODE=SUPPORT, TYPE=BBC,
CABINETDESC="IBBS";
//Adding a TRX
ADD GTRX: IDTYPE=BYID,CELLID=5,TRXID=9, FREQ=513,ISMAINBCCH=YES;
ADD GTRX: IDTYPE=BYID,CELLID=5,TRXID=10, FREQ=515;
ADD GTRX: IDTYPE=BYID,CELLID=6,TRXID=11, FREQ=517,ISMAINBCCH=YES;
ADD GTRX: IDTYPE=BYID,CELLID=6,TRXID=12, FREQ=519;
//Activating a BTS
ACT BTS:IDTYPE=BYID, BTSID=9;
This chapter describes the concepts, principles, rules, and conventions related to data
configuration.
Classification of Boards
Table 10-1 provides the classification of the BSC6900 boards.
FR
HDLC
Abis_IP
EIUa/OIUa Abis_TDM
Ater_TDM
A_TDM
Pb_TDM
POUc TDM
IP
FG2a IP
GbIP
GOUa/GOUc/FG2c IP
DPUb GTC
GPCU
DPUd/DPUg GPCU
MCP
Functions of boards
The BSC6900 boards provide different functions when being loaded with different software, as
described in Table 10-2.
IP IP interface processing
FR FR interface processing
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.
NOTE
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.
l Frame structure, synchronization, and timing comply with ITU-T G.705.
l Fault management complies with ITU-T G.732.
l 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.
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
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
l New services and functions in mobile communications networks, intelligent networks, and
intelligent management
l Integrated Services Digital Network (ISDN) supplementary services
l 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:
l 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.
l 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.
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.
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.
l 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.
l 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.
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 MSC-
controlled 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.
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.
Release of Radio When processing finishes, the MSC sends a Clear Command
Resources and message to the BSS. After receiving the message, the BSS starts a
Terrestrial Resources 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.
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.
Function Description
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.
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.
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.
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.
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.
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
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.
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 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.
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.
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.
l In single indication mode, the BSS immediately returns a Resource Indication message
about the relevant cell to the MSC.
l 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.
l 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.
Figure 10-10 shows the resource clearing procedure initiated by the MSC.
Figure 10-11 shows the resource clearing procedure initiated by the BSS.
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.
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.
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.
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.
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.
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.
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.
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 Each subrack needs to be configured with at least four Ater signaling links.
l Two 64 kbit/s Ater signaling links are configured for the 512 CICs.
l 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.
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
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.
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).
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.
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.
l Network congestion detection: When the NS layer detects that congestion occurs on lower-
layer 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.
l 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.
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.
l 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.
l 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.
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) 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.
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.
Figure 10-22 shows the logical connections at the NS and BSSGP layers between the
BSC6900 and the SGSN.
l 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.
l In the case of Gb over FR, services are carried on the NSVC and BC. In the case of Gb
over IP, services are carried on the links specified by the local and remote NSVLs.
Characteristics of Gb Interface
This section describes the characteristics of the Gb interface.
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.
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.
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.
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.
l 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.
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.
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.
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.
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.
l 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.
l 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.
l 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
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.
A site can be configured with both the virtual cabinet and the physical cabinet.
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
2-3 Reserved. -
6 Reserved. -
9 Reserved. -
10 Reserved. -
12
PMU 7 0
PSU 1~6
TCU 8 0
No board 9 No board is
configured in
slot 9.
FMU 11~12 0
DGPS/EMU/ 40~59 0
GATM
DRRU/GRRU/ 60~254 0
MRRU
GATM 16~17
GTMU 0 6
UBFA 16
Table 10-11 Mapping Between the SingleRAN Base Stations and Optional Cabinets
BTS Type Physical Silk Screen of Optical Description
Cabinet a Cabinet Cabinet (The
Nameplate types are
consistent
with the
correspondin
g values on
the LMT)
APM30 APM30
APM30H APM30
APM200 APM200
PS4890 PS4890
TMC TMC
TMC cabinets
TMC11H TMC
No BBC is
BBC
configured.
Battery group
IBBS200D BBC
IBBS200T BBC
BTS3900
BTS3900 GSM BTS3900
cabinets
APM30 APM30
AMP cabinets
BTS3900A APM30H APM30
TMC TMC
TMC cabinets
TMC11H TMC
IBBS200D BBC
IBBS200T BBC
Battery group
BBC No BBC is
configured.
BTS3900L BTS3900L
BTS3900L
cabinets GSM
Table 10-12 Mapping Between the Non-SingleRAN Base Stations and Optional Cabinets
BTS30 BTS30
BTS312 BTS312
BTS3001C BTS3001C
BTS3001C+ BTS3001CP
BTS3002C BTS3002C
BTS3012A BTS3012A
BTS3006A BTS3006A
BTS3012 BTS3012
BTS3006C BTS3006C
BTS3002E BTS3002E
BTS3012AE BTS3012AE
BTS3012 II BTS3012_II
BTS3900_GSM_6RFC l Recommended.
l The filler panel can be set
through the Configure
RFU by Slot parameter in
the ADD BTS command.
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
BTS3900A
BTS3900L
BTS3900E
BTS3012
DBS3900
BTS3900
BTS3900A
Wall-mounted
Environment
EMU All cabinets
Monitoring Unit in
EMU an equipment room
Power Monitoring
PMU All cabinets
Unit
Temperature Control
TCU All cabinets
Unit
Cabinet 0 PMU0 0 7 0 1 3
(AMP30)
Cabinet 1 PMU1 5 7 0 0 3
(AMP30)
Cabinet 2 PMU2 6 7 0 1 4
(AMP30)
Cabinet 0 TCU0 0 8 0 1 7
(AMP30)
Cabinet 1 TCU1 5 8 0 0 7
(AMP30)
Cabinet 2 TCU2 6 8 0 1 6
(AMP30)
Cabinet 0 TCU3 8 8 0 0 6
(TMC)
Cabinet 0 FMU0 1 11 0 0 14
(RFC)
Cabinet 1 FMU1 2 11 0 0 15
(RFC)
Cabinet 2 FMU2 3 11 0 1 14
(RFC)
Cabinet 3 FMU3 4 11 0 1 15
(RFC)
Cabinet 0 BBC/ 9 8 0 1 23
(APM30)/ TCU0
Cabinet 0
(BBC)
Cabinet 0 BBC/ 10 8 0 1 24
(APM30)/ TCU1
Cabinet 1
(BBC)
Cabinet 1 BBC/ 11 8 0 0 23
(APM30)/ TCU0
Cabinet 0
(BBC)
Cabinet 1 BBC/ 12 8 0 0 24
(APM30)/ TCU1
Cabinet 1
(BBC)
Cabinet 2 BBC/ 13 8 0 1 25
(APM30)/ TCU0
Cabinet 0
(BBC)
Cabinet 2 BBC/ 14 8 0 1 26
(APM30)/ TCU1
Cabinet 1
(BBC)
Cabinet 0 EMU/ 0 40 0 1 2
(AMP30) EMUA
Cabinet 0 GATM0 0 50 0 0 22
(AMP30)
Cabinet 0 GATM1 0 51 0 1 22
(AMP30)
Cabinet 0 FMU0 0 11 0 0 14
(indoor
macro
BTS3900
cabinet)
Cabinet 1 FMU1 1 11 0 0 15
(indoor
macro
BTS3900
cabinet)
Cabinet 2 FMU2 2 11 0 1 14
(indoor
macro
BTS3900
cabinet)
Cabinet 0 PMU0 0 7 0 1 3
(indoor
macro
BTS3900
cabinet)
Cabinet 1 PMU1 1 7 0 0 3
(indoor
macro
BTS3900
cabinet)
Cabinet 2 PMU2 2 7 0 1 4
(indoor
macro
BTS3900
cabinet)
BTS3900 EMU/ 0 40 0 1 2
cabinet (or EMUA
wall-
mounted)
Cabinet 0 GATM0 0 50 0 0 22
(AMP30)
Cabinet 0 GATM1 0 51 0 1 22
(AMP30)
Cabinet 0 PMU0 20 7 0 1 3
(AMP30)
Cabinet 1 PMU1 21 7 0 0 3
(AMP30)
Cabinet 0 TCU0 20 8 0 1 7
(AMP30)
Cabinet 1 TCU1 21 8 0 0 6
(AMP30)
Cabinet 0 TCU2 28 8 0 0 7
(TMC)
Cabinet 0 BBC/ 29 8 0 1 23
(APM30)/ TCU0
Cabinet 0
(BBC)
Cabinet 0 BBC/ 30 8 0 1 24
(APM30)/ TCU1
Cabinet 1
(BBC)
Cabinet 1 BBC/ 31 8 0 0 23
(APM30)/ TCU0
Cabinet 0
(BBC)
Cabinet 1 BBC/ 32 8 0 0 24
(APM30)/ TCU1
Cabinet 1
(BBC)
Cabinet 0 EMUA 20 40 0 1 2
(AMP30)
Cabinet 0 PMU0 0 7 0 1 3
(OMB)
Cabinet 0 TCU0 0 8 0 1 7
(OMB)
Cabinet 1 TCU1 5 8 0 1 6
(OMB)
Cabinet 0 FMU0 0 11 0 0 14
(indoor
macro
BTS3900
L cabinet)
Cabinet 0 FMU1 0 12 0 0 15
(indoor
macro
BTS3900
L cabinet)
BTS3900 EMU/ 0 40 0 1 2
L cabinet EMUA
(or wall-
mounted)
Cabinet 0 GATM0 0 50 0 0 22
(AMP30)
Cabinet 0 GATM1 0 51 0 1 22
(AMP30)
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
APM30 APM30 -
APM30H APM30 -
APM100 APM100 -
APM200 APM200 -
BTS3900(Ver.C) EPS4890 -
SC48200 SC48200 -
Solar power system
SC4850 SC48200 -
Applies to the
scenario of reuse of
BTS3012AE DPMU the double-
transceiver series
base stations.
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.
S4+/S4- 3
S5+/S5- 4
S6+/S6- 5
S7+/S7- 6
S8+/S8- 7
S9+/S9- 8
S10+/S10- 9
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
S29+/S29- 28
S30+/S30- 29
S31+/S31- 30
S32+/S32- 31
Analog 33
sensor of the
current type:
24V2
(12V2)/
ANA2
Analog
sensor of the
voltage type:
24V2
(12V2)/
ANA2/GND
Analog 34
sensor of the
current type:
24V3
(12V3)/
ANA3
Analog
sensor of the
voltage type:
24V3
(12V3)/
ANA3/GND
Analog 35
sensor of the
current type:
24V4
(12V4)/
ANA4
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
user-defined alarms ports and cables.
UEIU
The UEIU is configured in slot 18 of subracks 0. Table 10-31 lists the mapping of UEIU user-
defined alarms ports and cables.
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.
PMU
The PMU is configured in slot 0 of subrack 7. Table 10-33 lists the mapping of PMU user-
defined alarms ports and cables.
FMU
The FMU is configured in slot 0 of subracks 11 to 12. Table 10-34 lists the mapping of FMU
user-defined alarms ports and cables.
SW3 3
Double 1/S2
feeder [2TX
2RX]
Double 1/S2
feeder [2TX
2RX]
Double 1/S2
feeder [2TX
4RX]
Double 1/S2
feeder [1TX
2RX]
Double 1/S2
feeder [1TX
1RX]
Double 1/S3-S8
feeder [2TX
4RX]
GT DBS3 IP Sup Not Sup Sup Sup Supp Not Supp Supp
MU 900 over port supp port port port orted supp orted orted
BTS3 FE ed orte ed ed ed orted
900 d
BTS3 IP Sup Sup Sup Not Not Supp Not Supp Not
900A over port port port supp supp orted supp orted supp
BTS3 E1 ed ed ed orte orte orted orted
900L d d
HDL Sup Sup Sup Not Not Supp Not Supp Not
C port port port supp supp orted supp orted supp
ed ed ed orte orte orted orted
d d
TDM Sup Sup Sup Not Not Supp Not Supp Not
port port port supp supp orted supp orted supp
ed ed ed orte orte orted orted
d d
DT BTS3 IP Sup Not Sup Sup Sup Supp Not Not Not
MU 012 over port supp port port port orted supp supp supp
BTS3 FE ed orte ed ed ed orted orted orted
012A d
E
IP Sup Sup Sup Not Not Supp Not Not Not
BTS3 over port port port supp supp orted supp supp supp
012II E1 ed ed ed orte orte orted orted orted
d d
HDL Sup Sup Sup Not Not Supp Not Not Not
C port port port supp supp orted supp supp supp
ed ed ed orte orte orted orted orted
d d
TDM Sup Sup Sup Not Not Supp Not Not Not
port port port supp supp orted supp supp supp
ed ed ed orte orte orted orted orted
d d
DO BTS3 HDL Sup Sup Sup Not Not Supp Not Not Not
MU 006C C port port port supp supp orted supp supp supp
BTS3 ed ed ed orte orte orted orted orted
002E d d
TDM Sup Sup Sup Not Not Supp Not Not Not
port port port supp supp orted supp supp supp
ed ed ed orte orte orted orted orted
d d
BT BTS3 IP Sup Not Not Sup Not Not Supp Supp Supp
S39 900B over port supp supp port supp supp orted orted orted
00B FE ed orte orte ed orte orted
d d d
BT BTS3 IP Sup Not Sup Sup Sup Not Not Not Not
S39 900E over port supp port port port supp supp supp supp
00E FE ed orte ed ed ed orted orted orted orted
d
HDL Sup Sup Sup Not Not Not Not Not Not
C port port port supp supp supp supp supp supp
ed ed ed orte orte orted orted orted orted
d d
TDM Sup Sup Sup Not Not Not Not Not Not
port port port supp supp supp supp supp supp
ed ed ed orte orte orted orted orted orted
d d
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.
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.
Advantages: The chain topology can reduce the costs of transmission equipment and engineering
construction and save the rent for the transmission links.
Disadvantages:
l The reliability of the transmission link is poor because the signal transmission passes
through multiple nodes.
l A faulty BTS may affect the normal operation of its lower-level BTSs.
l The number of cascading levels must not exceed five.
To minimize the impact of the faulty upper-level BTS on lower-level BTSs, the Abis bypass
function is provided.
In bypass mode, a relay switch is installed on the BTS. When a BTS is running normally, the
timeslots of the lower-level BTSs are switched over from the incoming E1 port to the outgoing
E1 port through the switching board of the BTS. When the BTS fails to provide services due to
power-off or other reasons, the relay switch works to ensure the direct connection between the
incoming E1 port and the outgoing E1 port on the BTS. Therefore, the lower-level BTSs still
retain the connection to the BSC6900. Figure 10-26 shows the 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.
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.
l A faulty BTS may affect the normal operation of its lower-level BTSs.
l It is inconvenient to expand the capacity of the network.
l The number of cascading levels must not exceed five.
Ring Topology
The ring topology is a special chain topology. Several BTSs form a chain, and the lowest-level
BTS is connected to the BSC6900, 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.
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.
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.
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.
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.
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.
l Semi
Monitoring timeslot of a BTS, which has a rate of 8 kbit/s, 16 kbit/s, 32 kbit/s, or 64 kbit/
s and cannot be multiplexed with timeslots of other types.
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.
1 RSL00
4 RSL01
7 RSL02
10 RSL03
12 T03C6 T03C7
...
31 OML0
3 RSL01+RSL02
8 RSL03
10 T03C6 T03C7
11
...
31 OML0+RSL00
5 RSL02+RSL03
12 T03C6 T03C7
13
...
31 OML0+RSL00+RSL01
7 RSL03
9 T03C6 T03C7
10
...
31 OML0+RSL00+RSL01+RSL02
...
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 pre-
empted 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.
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.
l 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.
l 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.
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
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 Sub-Timeslot
0, 1 2, 3 4, 5 6, 7
Timeslot Sub-Timeslot
0, 1 2, 3 4, 5 6, 7
When manually assigning timeslots on the Abis interface, adhere to the following principles:
l The objects that support manual timeslot assignment are OMLs.
l When BTSs are cascaded, only the OML timeslots for the current level BTS can be allocated
manually.
l The occupied source timeslots are cleared and then allocated again.
l 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.
l 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 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.
l 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.
l You can run the MML command SET BTSIDLETS to configure the number of idle
timeslots for a single BTS.
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.
l The spacing between the two TRXs in both tributaries A and B must be at least three
frequencies. The frequency spacing between tributary A and tributary B has no restriction
because the two tributaries are independent of each other.
l In the antenna feeder connections of the DFCB, none of the TRXs can be configured with
RF FH.
l In the antenna feeder connections of the DFCB, the transmit mode of any TRX cannot be
set to wideband combination.
l The DFCB does not require extension connections. The extension connections are
configured on the DFCU.
DPMU PS4890
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.
l 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 Cabinet, Cabinet, Then, Modify the
BTS Is... Subrack, Slot Subrack, Slot Type of Cabinet 0
Numbers Before Numbers After to...
Upgrade Are... Upgrade Are...
l 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)
Numbe BTS CPRI CPRI Numbe Cabine Subrac Slot
r of Model Cascad Port r of t k Numbe
Cabine ing Numbe Cascad Numbe Numbe r After
ts r ing r After r After Upgrad
Before Levels Upgrad Upgrad e
Upgrad on e e
e CPRI
Chain
Before
Upgrad
e
EMU 2
PMU 3, 4
TCU 7, 6
FMU 14, 15
GATM 22
The following table provides the configuration rules of upgrading the monitoring boards from
a 8.x version to the 9.0 version.
l The DPMU/APMU is
renamed PMU.
l You need to modify the
parameters of the PMU
and add the relation
information of the
management object.
The following is an example: View the settings of the PMU and determine how many PSUs are
configured. Assume that three PSUs are configured in PMU0 by running the following
command: SET BTSAPMUBP: IDTYPE=BYID, BTSID=1000, CN=0, SRN=7, SN=0,
CFGFLAG=YES, APMUBRDTYPE=APM30, PSU0=YES, PSU1=YES, PSU2=YES. After
the PMU0 is added, three PSUs are added. In the 9.0 version, the PSU is treated as a board, and
therefore you need to add a PSU in the same way as adding a board. The MML command for
adding a PSU is as follows:
Item Specification
Item Specification