RF Unit and Topology Management SRAN8 0 Draft B PDF

SRAN8.
RF Unit and Topology Management
Issue Draft B
Date 2013-02-08
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SRAN8.0
RF Unit and Topology Management Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..................................................................................................................................................................1
1.2 Intended Audience..............................................................................................................................................1
1.3 Change History...................................................................................................................................................1
2 Overview.........................................................................................................................................3
2.1 Introduction to RF Modules...............................................................................................................................3
2.2 Introduction to RRU/RFU Topologies...............................................................................................................3
3 RRU/RFU Modules........................................................................................................................4
3.1 Overview............................................................................................................................................................4
3.2 RRU/RFU Modules in GSM Mode....................................................................................................................4
3.3 RRU/RFU Modules in UMTS Mode..................................................................................................................6
3.4 RRU/RFU Modules in LTE Mode.....................................................................................................................8
3.5 RRU/RFU Modules in Multimode Scenarios...................................................................................................12
4 RRU/RFU Topologies.................................................................................................................13
4.1 Star Topology...................................................................................................................................................14
4.2 Chain Topology................................................................................................................................................14
4.3 Ring Topology..................................................................................................................................................15
4.3.1 Cold-Backup Ring Topology on One Baseband Signal Processing Board or Interface Board...............16
4.3.2 Cold-Backup Ring Topology Between Two Baseband Signal Processing Boards.................................17
4.3.3 Hot-Backup Ring Topology....................................................................................................................18
4.3.4 Intra-Board Load-Sharing Ring Topology..............................................................................................19
4.3.5 Inter-Board Load-Sharing Ring Topology..............................................................................................20
4.4 Dual-Star Topology..........................................................................................................................................21
5 Related Features...........................................................................................................................23
6 Network Impact...........................................................................................................................24
7 Engineering Guidelines (GSM_GBTS)...................................................................................25
7.1 When to Use RF Unit and Topology Management..........................................................................................25
7.2 Required Information.......................................................................................................................................25
7.3 Network Planning.............................................................................................................................................25
7.4 Deployment......................................................................................................................................................25
7.4.1 Requirements...........................................................................................................................................25
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential ii

SRAN8.0
7.4.2 Data Preparation......................................................................................................................................25

7.4.3 Precautions...............................................................................................................................................30
7.4.4 Initial Configuration................................................................................................................................31
7.4.5 Activation Observation............................................................................................................................31
7.4.6 Reconfiguration.......................................................................................................................................32
7.5 Performance Optimization................................................................................................................................34
7.6 Troubleshooting................................................................................................................................................34
8 Engineering Guidelines (GSM_eGBTS).................................................................................37

8.4 Deployment......................................................................................................................................................37
8.4.1 Requirements...........................................................................................................................................37
8.4.3 Precautions...............................................................................................................................................43
9 Engineering Guidelines (UMTS).............................................................................................49

9.4 Deployment......................................................................................................................................................49
9.4.1 Requirements...........................................................................................................................................49
9.4.3 Precautions...............................................................................................................................................56
10 Engineering Guidelines (LTE)................................................................................................62

10.1 When to Use RF Unit and Topology Management........................................................................................62
10.2 Required Information.....................................................................................................................................62
10.3 Network Planning...........................................................................................................................................62
10.4 Deployment....................................................................................................................................................62
10.4.1 Requirements.........................................................................................................................................62
10.4.2 Data Preparation....................................................................................................................................63
10.4.3 Precautions.............................................................................................................................................72
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential iii

SRAN8.0
10.4.4 Initial Configuration..............................................................................................................................72

10.4.5 Activation Observation..........................................................................................................................72
10.4.6 Reconfiguration.....................................................................................................................................73
10.5 Performance Optimization..............................................................................................................................74
10.6 Troubleshooting..............................................................................................................................................74
11 Engineering Guidelines (Dual Modes).................................................................................76

11.1 When to Use RF Unit and Topology Management........................................................................................76
11.2 Required Information.....................................................................................................................................76
11.3 Network Planning...........................................................................................................................................76
11.4 Deployment....................................................................................................................................................76
11.4.1 Requirements.........................................................................................................................................76
11.4.2 Data Preparation....................................................................................................................................76
11.4.3 Precautions.............................................................................................................................................81
11.4.4 Initial Configuration..............................................................................................................................81
11.4.5 Activation Observation..........................................................................................................................82
11.4.6 Reconfiguration.....................................................................................................................................82
11.5 Performance Optimization..............................................................................................................................83
11.6 Troubleshooting..............................................................................................................................................83
12 Reference Documents...............................................................................................................84
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential iv

SRAN8.0
RF Unit and Topology Management Figures
Figures
Figure 4-1 Star topology for RRUs/RFUs.............................................................................................................14

Figure 4-2 Chain topology for RRUs/RFUs..........................................................................................................15
Figure 4-3 GSM ring topology..............................................................................................................................16
Figure 4-4 Cold-backup ring topology on one baseband signal processing board or interface board..................17
Figure 4-5 Cold-backup ring topology between two baseband signal processing boards.....................................18
Figure 4-6 Hot-backup ring topology....................................................................................................................19
Figure 4-7 Intra-board load-sharing ring topology................................................................................................20
Figure 4-8 Inter-board load-sharing ring topology................................................................................................20
Figure 4-9 Dual-star topology...............................................................................................................................21
Figure 7-1 Command result example....................................................................................................................31
Figure 10-1 Command result example..................................................................................................................73
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential v

SRAN8.0
RF Unit and Topology Management Tables
Tables
Table 7-1 RF-related alarms in GSM mode...........................................................................................................34

Table 8-1 RF-related alarms in GSM mode...........................................................................................................46
Table 9-1 RF-related alarms and events in UMTS mode......................................................................................58
Table 10-1 RF-related alarms and events in LTE mode........................................................................................74
Table 11-1 Multimode base station common parameters......................................................................................77
Table 11-2 RF-related alarms and events in multiple modes................................................................................83
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential vi

SRAN8.0
RF Unit and Topology Management 1 About This Document
1 About This Document
1.1 Scope
This document describes the RF Unit and Topology Management feature. This document is
applicable to the following 3900 series base stations:
l BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D)

l BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D)
l BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D)
l BTS3900AL (Ver.A)
l DBS3900
l BTS3900C, BTS3900C (Ver.B), and BTS3900C (Ver.C)
Any managed objects (MOs), parameters, alarms, or counters described below correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with the latest software release.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand RF Unit and Topology Management

l Work with Huawei LTE products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
refers to a change in the RF Unit and Topology Management feature of a specific product
version.
l Editorial change:
Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 1

SRAN8.0
RF Unit and Topology Management 1 About This Document
refers to a change in wording or the addition of information that was not described in the
earlier version.
Document Versions
The document versions are as follows:
l Draft B (2013-02-08)
l Draft A (2012-12-30)
Draft B (2013-02-08)
This is the first commercial release of Draft B of the document for GBSS15.0, RAN15.0,
eRAN6.0, and SRAN8.0. Compared with Draft A (2012-12-30) for SRAN8.0, Draft B
(2013-02-08) includes the following changes.
Change Change Description Parameter

Type Change
Feature Added the Long Term Evolution (LTE) load-sharing ring None
change topology and engineering guidelines for this topology.
Draft A (2012-12-30)
This is the first commercial release of Draft A of the document for GBSS15.0, RAN15.0,
eRAN6.0, and SRAN8.0. Compared with Issue 05 (2012-09-15) for SRAN7.0, Draft A
(2012-12-30) includes the following changes.
Change Type Change Description Parameter Change
Feature change Added new RF modules. None
Deleted RRU/RFU None

topologies from the CPRI
MUX topology and added the
deleted part to CPRI MUX
Feature Parameter
Description.

SRAN8.0
RF Unit and Topology Management 2 Overview
2 Overview
2.1 Introduction to RF Modules

Radio frequency (RF) modules are classified into the following types:
l Remote radio unit (RRU): applies to distributed and macro base stations
l Radio frequency unit (RFU): applies to macro base stations
RRUs and RFUs modulate and demodulate baseband and RF signals, process data, amplify
power, and detect standing waves.
2.2 Introduction to RRU/RFU Topologies

RRU/RFU topologies are networking between the baseband unit (BBU) and RRUs/RFUs over
common public radio interface (CPRI) ports. Common RRU/RFU topologies include the star,
chain, ring, dual-star, and CPRI multiplexing (MUX) topologies.

SRAN8.0
RF Unit and Topology Management 3 RRU/RFU Modules
3 RRU/RFU Modules
3.1 Overview
This chapter describes the RRU/RFU models, logical types, TX/RX channel, and topologies
supported in Global System for Mobile communications (GSM), Universal Mobile
Telecommunications System (UMTS), and LTE modes, and multimode scenarios. A logical
type is an RRU/RFU type displayed on the local maintenance terminal (LMT) and Configuration
Management Express (CME). In GSM mode, RXU specifications must be configured to identify
RF capabilities for different RF modules.
3.2 RRU/RFU Modules in GSM Mode

Model Logical Type TX/RX RRU/RFU Topology
Channel Specifications
RRU3004 DRRU 2T2R - Star, chain, or

ring topology
RRU3008 V1 GRRU 2T2R RRU3008_V1 Star, chain, or

(RRU3008 V1 ring topology
SPEC)
RRU3008 V2 GRRU 2T2R RRU3008_V2 Star, chain, or

(RRU3008 V2 ring topology
SPEC)
RRU3908 V1 MRRU 2T2R RRU3908_V1 Star or chain

(RRU3908 V1 topology
SPEC)
RRU3908 V2 MRRU 2T2R RRU3908_V2 Star or chain

(RRU3908 V2 topology
SPEC)

SRAN8.0

RRU3922E MRRU 2T2R RRU3922E Star or chain

(RRU3922E topology
SPEC)
RRU3926 MRRU 1T2R RRU3926 Star or chain

(RRU3926 topology
SPEC)

(RRU3936 topology
SPEC)

(RRU3928 topology
SPEC)

(RRU3961 topology
SPEC)

(RRU3929 topology
SPEC)

(RRU3942 topology
SPEC)
DRFU DRFU 2T2R - Star or chain

topology
GRFU V1 GRFU 1T2R GRFU_V1 Star or chain

(GRFU V1 topology
SPEC)
GRFU V2 GRFU 1T2R GRFU_V2 Star or chain

(GRFU V2 topology
SPEC)
GRFU V2a GRFU 1T2R GRFU_V2a Star or chain

(GRFU V2a topology
SPEC)
MRFU V1 MRFU 1T2R MRFU_V1 Star or chain

(MRFU V1 topology
SPEC)
MRFU V2 MRFU 1T2R MRFU_V2 Star or chain

(MRFU V2 topology
SPEC)

SRAN8.0

MRFU V2a MRFU 1T2R MRFU_V2a Star or chain

(MRFU V2a topology
SPEC)
MRFUd MRFU 2T2R MRFUd Star or chain

(MRFUd topology
SPEC)
MRFUe MRFU 1T2R MRFUe Star or chain

(MRFUe SPEC) topology
NOTE
The symbol "-" indicates that RRU/RFU specifications are not involved.
3.3 RRU/RFU Modules in UMTS Mode

Model Logical Type TX/RX Channel Topology
RRU3801E MRRU 1T2R Star topology, chain

topology, or cold-
backup ring topology
between two
baseband signal
processing boards
RRU3801C MRRU 1T2R Star topology, chain

topology, or cold-
between two
baseband signal
processing boards
RRU3804 MRRU 1T2R Star topology, chain

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards

SRAN8.0

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards

topology, or cold-
between two
baseband signal
processing boards
RRU3908 V1 MRRU 2T2R Star topology
RRU3908 V2 MRRU 2T2R Star topology
RRU3926 MRRU 1T2R Star topology

SRAN8.0
RRU3821E PRRU 2T2R Star topology, chain

topology, or cold-
between two
baseband signal
processing boards
WRFU WRFU 1T2R Star or chain

topology
WRFUa WRFU 1T2R Star topology
WRFUd WRFU 2T2R Star topology
WRFUe WRFU 2T2R Star topology
MRFU V1 MRFU 1T2R Star topology
MRFU V2a MRFU 1T2R Star topology
MRFUd MRFU 2T2R Star topology
MRFUe MRFU 1T2R Star topology
3.4 RRU/RFU Modules in LTE Mode

Duplex Model Logic TX/RX Topology
Mode al Chann
Type el
Frequency RRU3201 LRRU 2T2R Star topology, chain topology, cold-backup

division ring topology on one baseband signal
duplex processing board, cold-backup ring
(FDD) topology between two baseband signal
processing boards, or hot-backup ring
topology
RRU3203 LRRU 2T2R Star topology, chain topology, cold-backup

ring topology on one baseband signal
processing board, cold-backup ring
topology between two baseband signal
topology

SRAN8.0

Mode al Chann
Type el

topology

processing boards, hot-backup ring
topology, or load-sharing ring topology

topology

topology




SRAN8.0

Mode al Chann
Type el

RRU3821E PRRU 2T2R Star topology, chain topology, or cold-

backup ring topology between two
baseband signal processing boards
RRU3908 MRR 2T2R Star or chain topology

V1 U

V2 U

U

U

U

U
LRFU LRFU 2T2R Star topology or hot-backup ring topology
LRFUe LRFU 2T2R Star topology or hot-backup ring topology
MRFU V1 MRF 1T2R Star topology

U
MRFU V2 MRF 1T2R Star topology

U
MRFU V2a MRF 1T2R Star topology

U
MRFUd MRF 2T2R Star topology

U
CRFUd MRF 2T2R Star topology

U

U

U

SRAN8.0

Mode al Chann
Type el

U
Time RRU3232 MRR 4T4R Star topology, chain topology, cold-backup

division U ring topology on one baseband signal
duplex processing board, cold-backup ring
(TDD) topology between two baseband signal
RRU3251 MRR 2T2R Star topology, chain topology, cold-backup

U ring topology on one baseband signal
processing boards, or load-sharing ring
topology
RRU3152-e MRR 2T2R Star topology, chain topology, or load-

U sharing ring topology
RRU3702 MRR 4T4R Star topology, cold-backup ring topology

U on one baseband signal processing board,
or cold-backup ring topology between two
baseband signal processing boards
RRU3235 MRR 4T4R Star topology

U
RRU3253 MRR 8T8R Star topology or load-sharing ring topology

U

topology

topology

topology

SRAN8.0

Mode al Chann
Type el
pRRU3901 MPR 2T2R Star or chain topology

U
3.5 RRU/RFU Modules in Multimode Scenarios

RRU3908 V1 MRRU 2T2R Dual-star topology
RRU3908 V2 MRRU 2T2R Dual-star topology
RRU3926 MRRU 1T2R Dual-star topology
MRFU V1 MRFU 1T2R Dual-star topology
MRFU V2 MRFU 1T2R Dual-star topology
MRFUd MRFU 2T2R Dual-star topology
MRFUe MRFU 1T2R Dual-star topology
RRU3821E PRRU 2T2R Star topology, chain

topology, or cold-
between two
baseband signal
processing boards

SRAN8.0
RF Unit and Topology Management 4 RRU/RFU Topologies
4 RRU/RFU Topologies
RRU/RFU topologies are networking between the BBU and RRUs/RFUs over CPRI ports.
Common RRU/RFU topologies include the star, chain, ring, dual-star, and CPRI MUX
topologies.
NOTE
For details about RRU/RFU topologies in the CPRI MUX topology, see CPRI MUX Feature Parameter
Description.

SRAN8.0
4.1 Star Topology

Figure 4-1 shows a star topology for RRUs/RFUs.
Figure 4-1 Star topology for RRUs/RFUs
In a star topology, each RRU/RFU is directly connected to a different CPRI port on a baseband
signal processing board or interface board in the BBU. The transport link between an RRU/RFU
and a baseband signal processing board or interface board is called a CPRI link, which is used
to transmit user and control plane data between the RRU/RFU and the baseband signal
processing board or interface board. If the CPRI link is faulty, communication between the RRU/
RFU and the baseband signal processing board or interface board is interrupted.
Star topologies are highly reliable. If an RRU/RFU or the optical channel between the RRU/
RFU and a baseband signal processing board or interface board is faulty, only the cell served by
this RRU/RFU is affected.
Star topologies apply to most areas, especially densely populated areas. Star topologies require
more optical fibers than other topologies.
4.2 Chain Topology

Figure 4-2 shows a chain topology for RRUs/RFUs.

SRAN8.0
Figure 4-2 Chain topology for RRUs/RFUs
In a chain topology, only the first-level RRU/RFU is directly connected to a baseband signal
processing board or interface board, and other RRUs/RFUs are cascaded to their upper-level
RRUs/RFUs one by one. The lowest-level RRU/RFU is the chain tail.
Data of a lower-level RRU/RFU is forwarded by its upper-level RRUs/RFUs. The total physical
bandwidth of RRUs/RFUs in a chain cannot exceed the physical bandwidth capacity of the
connected CPRI port on the baseband signal processing board or interface board.
An operation and maintenance (OM) link is set up between each RRU/RFU on the chain and
the baseband signal processing board or interface board. User and control plane data are
transmitted on the corresponding CPRI link.
The following are the maximum numbers of cascading levels supported in different modes if
the physical bandwidth is sufficient:
l GSM supports a maximum of 21 cascading levels for RRUs (GTMUb supports in a GBTS
and GBBP supports in an eGBTS) or three cascading levels for RFUs.
l UMTS supports a maximum of eight cascading levels for RRUs or two cascading levels
for RFUs.
l LTE FDD supports a maximum of four cascading levels for RRUs or eight cascading levels
for pRRUs.
Chain topologies apply to long and narrow, and loosely populated areas, such as highways and
railways. Chain topologies require less optical fibers than other topologies.
Chain topologies are less reliable. If an RRU/RFU or the optical channel is faulty, all cells served
by its lower-level RRUs/RFUs are affected.
4.3 Ring Topology

For GSM, the main control board or interface board in the BBU connects to RRUs in a ring
topology, with RRUs at the two ends of the CPRI cable on the main control board or interface
board functioning as the ring head and tail, respectively. Figure 4-3 shows the GSM ring
topology.

SRAN8.0
Figure 4-3 GSM ring topology
For UMTS and LTE, the baseband signal processing board in the BBU connects to RRUs in a
ring topology, with RRUs at the two ends of CPRI cable on the baseband signal processing board
functioning as the ring head and tail, respectively. Two types of ring topologies, cold-backup
and hot-backup, are available. A cold-backup ring topology can be on one baseband signal
processing board or between two baseband signal processing boards. A hot-backup ring topology
is always between two baseband signal processing boards. The LTE mode also supports the
load-sharing ring topology, which includes the intra-board load-sharing ring topology and inter-
board load-sharing ring topology.
4.3.1 Cold-Backup Ring Topology on One Baseband Signal

Processing Board or Interface Board
Figure 4-4 shows a cold-backup ring topology on one baseband signal processing board or
interface board.

SRAN8.0
Figure 4-4 Cold-backup ring topology on one baseband signal processing board or interface
board
In a cold-backup ring topology on one baseband signal processing board or interface board, if
a baseband signal processing board is faulty, services carried by all RRUs on the ring are
interrupted.
If a failure occurs in a CPRI port on a baseband signal processing board through which RRUs
on the ring communicate with the BBU, services carried by the RRUs are interrupted for a
maximum of 20 seconds.
l GSM supports a maximum of 21 cascading levels for RRUs (GTMUb supports in a GBTS
and GBBP supports in an eGBTS).
l UMTS supports a maximum of eight cascading levels for RRUs.
l LTE FDD supports a maximum of four cascading levels for RRUs.
4.3.2 Cold-Backup Ring Topology Between Two Baseband Signal

Processing Boards
Figure 4-5 shows a cold-backup ring topology between two baseband signal processing boards.

SRAN8.0
Figure 4-5 Cold-backup ring topology between two baseband signal processing boards
In a cold-backup ring topology between two baseband signal processing boards, if one baseband
signal processing board is faulty and the other baseband signal processing board works properly
and has sufficient baseband resources, services carried by the faulty baseband signal processing
board are interrupted for a maximum of 20 seconds.
If a failure occurs in a CPRI port through which RRUs on the ring communicate with the BBU,
services carried by the RRUs are interrupted for a maximum of 20 seconds. If a failure occurs
in the CPRI port that is not used for communications, RRU services will not be interrupted.
l UMTS supports a maximum of eight cascading levels for RRUs.
l LTE FDD supports a maximum of four cascading levels for RRUs or eight cascading levels
for PRRUs.
l GSM does not support the cold-backup ring topology.
4.3.3 Hot-Backup Ring Topology

4.3.3 Hot-Backup Ring Topology shows a hot-backup ring topology.

SRAN8.0
Figure 4-6 Hot-backup ring topology
In a hot-backup ring topology, each RRU is connected to two baseband signal processing boards
or interface boards in the BBU, and one ring has only one RRU. An OM link is set up between
an RRU and one baseband signal processing board or interface board in the BBU. The same data
on the user plane is simultaneously transmitted on two CPRI links.
Hot-backup ring topologies apply only between two baseband signal processing boards or
interface boards. If one CPRI link is faulty, services are quickly switched over to the other CPRI
link, with service interruption for a maximum of 500 ms. If one baseband signal processing
board or interface board is faulty, cells carried by the baseband signal processing board or
interface board are set up on the other baseband signal processing board or interface board, with
service interruption for a maximum of 20 seconds.
Hot-backup ring topologies are more reliable than cold-backup ring topologies.
4.3.4 Intra-Board Load-Sharing Ring Topology

Figure 4-7 shows the intra-board load-sharing ring topology.

SRAN8.0
Figure 4-7 Intra-board load-sharing ring topology
If the physical bandwidth of a CPRI port is insufficient to support a cell, the intra-board load-
sharing ring topology can be used. In this topology, one RRU is connected to two CPRI ports
on one LBBP. The two CPRI ports ensure sufficient bandwidth for the cell.
4.3.5 Inter-Board Load-Sharing Ring Topology

Figure 4-8 shows the inter-board load-sharing ring topology.
Figure 4-8 Inter-board load-sharing ring topology

SRAN8.0
The inter-board load-sharing ring topology applies to RRUs serving multiple carriers (At present,
the LTE mode supports a maximum of two carriers on one RRU). In this topology, one RRU is
connected to the CPRI port on two LBBPs. One CPRI link transmits data for one carrier. The
OM channel can only be set up on one of the two CPRI links.
If the CPRI port that carries the OM channel becomes faulty, the OM channel automatically
switches over to the other CPRI port on the other LBBP. If either of the two CPRI ports becomes
faulty and the physical bandwidth of the CPRI port is insufficient to support a cell, cell
specifications will be degraded. For example, the antenna mode of the sector corresponding to
the cell will be degraded from 8T8R to 4T4R.
4.4 Dual-Star Topology

This section describes the following multimode features:
l MRFD-210002 Multi-mode BS RRU/RFU star-connection with separate CPRI interface

(GBTS)
(NodeB)
(eNodeB)
In a GU or GL dual-mode scenario, both RRUs and RFUs support dual-star topologies. In a UL

dual-mode scenario, only RRUs support dual-star topologies.
In a dual-star topology (for example, a GU base station), a dual-mode RRU/RFU is connected

to a UBRI and a WBBP that use different radio access technologies (RATs), as shown in Figure
4-9.
Figure 4-9 Dual-star topology

SRAN8.0
In this scenario, a CPRI link is set up between a dual-mode RRU/RFU and the baseband signal
processing board or interface board. Each CPRI link is dedicated to one RAT so that user and
control plane data for the two RATs are transmitted over the two CPRI links independently.
If one CPRI port on one baseband signal processing board or interface board is faulty, the services
of the other RAT are not affected. Therefore, dual-star topologies are highly reliable.

SRAN8.0
RF Unit and Topology Management 5 Related Features
5 Related Features
None

SRAN8.0
RF Unit and Topology Management 6 Network Impact
6 Network Impact
No impact.

SRAN8.0
RF Unit and Topology Management 7 Engineering Guidelines (GSM_GBTS)
7 Engineering Guidelines (GSM_GBTS)
7.1 When to Use RF Unit and Topology Management

RF unit and topology management is a basic feature and must be enabled.
7.2 Required Information

l Obtain the names of RF modules.
l Select a topology for the network based on the network plan and specific topology
characteristics.
7.3 Network Planning

None
7.4 Deployment
7.4.1 Requirements
RF modules are installed and connected to the BBU based on the required topology. For details,
see the installation guide for the corresponding type of base station.
7.4.2 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for a
specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the evolved packet core (EPC) or peer transmission equipment

SRAN8.0
l User-defined: parameter values set by users
Required Data
Collect the following information before preparing required data:
l RRU/RFU model
l RRU/RFU topology, which is used to determine the configuration of RRU/RFU links
1. The following table describes the parameters related to BTSRXUCHAIN.
Parame Parame Setting Notes Data

ter ter ID Source
Name
RRU RCN This parameter uniquely identifies an RRU/RFU Network

Chain chain or ring in a GBTS. plan
No. (negotiation
not
required)
Topo TT l In the star and chain topologies, this parameter Network

Type must be set to CHAIN. In the star topology, plan
only one RRU/RFU is configured on a chain. (negotiation
l In the ring topology, set this parameter to not
RING and configure two CPRI ports. required)
Head HCN Cabinet number, subrack number, slot number, User-

Cabinet and CPRI port number of the board on which the defined
No. CPRI port serving as the chain/ring head and ring
tail is located. These parameters are set according
Head HSRN to site configuration. User-
Subrack defined
When configuring cabinet, subrack, slot, and port
No.
numbers, satisfy the following requirements:
Head HSN l Cabinet number: 0 to 7. User-
Slot No. l Subrack number: 0 or 1. defined
Head HPN l When the GTMU is used to connect an RRU/ User-

Port No. RFU, you can only set a slot number to 6. defined
l When the UBRI is used to connect RRU/RFU,
Tail TCN User-
set a slot number to 2.
Cabinet defined
No. l When the GBBP is used to connect an RRU/
RFU, you can set a slot number to a value in
Tail TSRN the range of 0 to 4. User-
Subrack l Optical port number: 0 to 5. The values of defined
No. Head Port No. and Tail Port No. cannot be
the same.
Tail Slot TSN User-
No. defined
Tail Port TPN User-

No. defined

SRAN8.0
2. The following table describes the parameters related to BTSRXUBRD.

ter ter ID Source
Name
Board BT Set this parameter based on the type of the RF Network

Type module in use. For details, see 3 RRU/RFU plan
Modules. (negotiation
not
required)
RXU RXUSP This parameter specifies the capability of an RF Network

Specific EC module to transmit RF signals. Set this parameter plan
ation based on the hardware type for the RF module. (negotiation
For details, see 3 RRU/RFU Modules. not
required)
Cabinet CN l This parameter for an RRU must be set to 0. User-

No. l This parameter for an RFU can be set to a defined
value ranging from 0 to 62.
Subrack SRN l This parameter for an RRU can be set to a User-

No. value ranging from 60 to 254. defined
l This parameter can be set to 4 or 5 for an RFU
in a BTS3900L cabinet, and must be set to 4
for an RFU in other types of cabinets.
Slot No. SN l This parameter for an RRU must be set to 0. User-

l This parameter can be set from 0 to 8 for an defined
RFU in a BTS3900AL cabinet, and can be set
from 0 to 5 for an RFU in other types of
cabinets.
RXU RXUCH Set this parameter based on site requirements. Network

Chain AINNO plan
No. (negotiation
not
required)
RXU RXUPO This parameter specifies the position of an RRU/ Network

Board S RFU on an RRU/RFU chain or ring. The value of plan
Position this parameter is set sequentially from 1. The (negotiation
value of this parameter for an RRU/RFU must not
differ from that for any other RRU/RFU required)
configured on the same RRU/RFU chain.
In the chain topology, an RRU/RFU directly
connected to the BBU is the chain head and is
sequentially numbered from 1.

SRAN8.0

ter ter ID Source
Name
Power PWRM Set this parameter based on the specified power Network
Class ODE mode. plan
(negotiation
not
required)
3. The following table describes the parameters related to BTSRXUBP.

Parame Paramet Setting Notes Data
ter er ID Source
Name
RXU RXUCH Set this parameter based on site requirements. Network

Chain AINNO plan
No. (negotiation
not
required)
RXU RXUNA This parameter is optional. Set this parameter to Network

Name ME a string containing 1 to 64 characters based on site plan
requirements. (negotiation
not
required)
RXU RXUTY Set this parameter based on the type of the RXU Network
Board PE in use. The setting must be consistent with that of plan
Type the BT parameter. For details, see 3 RRU/RFU (negotiation
Modules. not
required)
Workin WORKI This parameter specifies the working mode of an Network

g NGSTA RXU. Set this parameter based on site plan
Standar NDARD requirements. (negotiation
d not
required)
Scenario-specific Data
Scenario 1: Star topology
l The following table describes the parameter related to BTSRXUCHAIN.

SRAN8.0

ter er ID Source
Name
Topo TT Set this parameter to CHAIN. Network

Type plan
(negotiation
not
required)
l The following table describes the parameters related to BTSRXUBRD.

ter er ID Source
Name
RXU RXUCH Set this parameter to the number of the RRU/RFU Network
Chain AINNO chain. plan
No. (negotiation
not
required)
RXU RXUPO Set this parameter to 1. Network

Board S plan
Position (negotiation
not
required)
Scenario 2: Chain topology

ter er ID Source
Name

Type plan
(negotiation
not
required)

SRAN8.0

ter er ID Source
Name
RXU RXUCH Set this parameter to the number of the RRU/RFU Network
Chain AINNO chain. plan
No. (negotiatio
n not
required)
RXU RXUPO Set this parameter based on the number of RRUs/ Network
Board S RFUs. For example, set the parameter to 1 for the plan
Position first RRU/RFU and 2 for the second RRU/RFU. (negotiatio
n not
required)
Scenario 3: Ring topology

ter er ID Source
Name
Topo TT Set this parameter to RING. Network

Type plan
(negotiatio
n not
required)

ter er ID Source
Name
RXU RXUCH Set this parameter to the number of the RRU ring. Network
Chain AINNO plan
No. (negotiatio
n not
required)
RXU RXUPO Set this parameter based on the number of RRUs. Network
Board S For example, set the parameter to 1 for the first plan
Position RRU and 2 for the second RRU. (negotiatio
n not
required)
7.4.3 Precautions
N/A

SRAN8.0
7.4.4 Initial Configuration

When you use an RRU/RFU or let an MRRU/MRFU work in single-mode scenarios, the slot
numbers must be different for RFUs that work in different network modes in the same RFC.
The following describes the initial configuration in a GSM network.
Configuring a Single GBTS Using the GUI

For detailed operations, see 3900 Series Base Station Initial Configuration Guide and follow
the "Procedure" according to the following path: 3900 Series Base Station Initial
Configuration (Based on CME) > Creating Base Stations > Creating GBTSs > Creating s
Single GBTS > Configuring GBTS Device Data > Configuring RF Units
Configuring GBTSs in Batches

Configuration (Based on CME) > Creating Base Stations > Creating GBTSs > Creating
GBTSs in Batches
Configuring a Single GBTS Using MML Commands

1. Run the ADD BTSRXUCHAIN command to add an RXU chain/ring. In this step, set RRU/
RFU chain or ring parameters in 7.4.2 Data Preparation.
2. Run the ADD BTSRXUBRD command to add an RRU/RFU. In this step, set RRU/RFU
parameters in 7.4.2 Data Preparation.
3. Run the SET BTSRXUBP command to set RXU board parameters. For the parameter
settings, see 7.4.2 Data Preparation.
7.4.5 Activation Observation

After configuration data is activated, make sure that no RRU/RFU alarm appears on the Alarm/
Event tab page on the GSM LMT. For the description of RRU/RFU alarms, see 7.6
Troubleshooting.
On the BSC LMT or the M2000, run the DSP BTSBRD command to check the status of the
RRU/RFU.
The status of the RRU/RFU is normal if the value of Board State is Normal, as shown in Figure
7-1.
Figure 7-1 Command result example

SRAN8.0
7.4.6 Reconfiguration
Adjusting RRU/RFU Topologies

The RRU/RFU topology is adjusted by modifying the connection mode of RRUs/RFUs during
capacity expansion. In GSM mode, topology adjustment includes splitting one RXU ring into
one or more RXU chains and combining one or more RXU chains into one RXU ring.
l Splitting an RXU ring into one or more RXU chains
Step 1 Run the SET BTSBREAKPOINT command to set breakpoints of an RXU ring.
Parameter Parameter ID Remarks

Name
Chain No. RCN This parameter uniquely identifies an RXU chain/ring

in a GBTS.
Position of BP1 Set this parameter based on site requirements.

Break Point 1/ BP2 l If you want to split one RXU ring into one RXU
Position of chain, set BP1 at the end of the chain.
Break Point 2
l If you want to split one RXU ring into two RXU
chains, set BP1 and BP2 on the RXU ring. It is
recommended that BP1 and BP2 overlap.
Step 2 Run the SPT BTSRXUCHAIN command to split the RXU ring into one or more RXU chains.

Name
Chain No. RCN This parameter uniquely identifies an RXU chain/ring

in a GBTS.
Separate SEPARATEPO Set this parameter based on site requirements.

Position S l If you want to split an RXU ring into an RXU chain,
set SEPARATEPOS at the end of the chain.
l If you want to split an RXU ring into two RXU
chains, set SEPARATEPOS on the RXU ring. It is
recommended that the setting be consistent with that
of BP1 and BP2.
----End
NOTE
If breakpoints are added on an RRU/RFU chain or ring, remove these breakpoints and restore the link after
adjusting the RRU/RFU topology.
l Combining one or more RXU chains into an RXU ring
Run the CBN BTSRXUCHAIN command to combine one or more RXU chains.

SRAN8.0

Name
Combine Type CHAINTORIN This parameter identifies the combination type.

G CHAINTORING indicates combining an RXU chain
as an RXU ring, and COMBINECHAINS indicates
combining two RXU chains as an RXU ring.
First RXU RCN1 The two parameters identify the numbers of the first and
Chain No. second RXU chains.
Second RXU RCN2

Chain No.
Tail Cabinet TCN The four parameters are mandatory only when the value
No. of Combine Type is CHAINTORING. Set them to the
onsite cabinet number, subrack number, slot number of
Tail Subrack TSRN the tail CPRI port, and the tail CPRI port number,
No. respectively.
Tail Slot No. TSN
Tail Port No. TPN
Adding an RRU/RFU to an RRU/RFU Chain or Ring

An RRU/RFU can be added to any position in an RRU/RFU chain or ring without changing the
original topology.
Step 1 Run the SET BTSBREAKPOINT command to set breakpoints for adding an RRU/RFU to an
RRU/RFU chain or ring.
Name
Chain No. RCN This parameter uniquely identifies an RRU/RFU chain

or ring in a GBTS.

Break Point 1/ BP2 l Only one breakpoint is allowed in one RXU chain,
Position of and the value of this parameter must be smaller than
Break Point 2 or equal to the number of boards under the chain.
l Two breakpoints are required for each RXU ring,
and the value of BP1 must be smaller than or equal
to that of BP2. The values of BP1 and BP2 must be
smaller than or equal to the number of boards under
the ring.
Step 2 Run the ADD BTSRXUBRD command to add an RRU/RFU. For the setting of parameters, see
the description of collecting information about an RRU chain or ring in 7.4.2 Data
Preparation.
----End

SRAN8.0
NOTE
Removing an RRU/RFU from an RRU/RFU Chain or Ring

Step 1 Run the SET BTSBREAKPOINT command to set breakpoints for removing an RRU/RFU
from an RRU/RFU chain or ring.

Name
Chain No. RCN This parameter uniquely identifies an RRU/RFU chain

or ring in a GBTS.

Break Point 1/ BP2 l Only one breakpoint is allowed in one RXU chain,
Position of and the value of this parameter must be smaller than
Break Point 2 or equal to the number of boards under the chain.
l Two breakpoints are required for each RXU ring,
and the value of BP1 must be smaller than or equal
to that of BP2. The values of BP1 and BP2 must be
smaller than or equal to the number of boards under
the ring.
Step 2 Run the RMV BTSRXUBRD command to remove an RRU/RFU.
----End
NOTE
7.5 Performance Optimization

N/A
7.6 Troubleshooting
For the description of RF-related alarms and events in GSM mode, see BSC6910/BSC6900 GSM
Alarm Reference and BSC6910/BSC6900 GSM Event Reference.
Table 7-1 RF-related alarms in GSM mode
Alarm ID Alarm Name Alarm Alarm Event

Type Severity Type
ALM-26501 RF Unit Optical Module or Electrical Fault Major Commu

Port Not Ready nication

SRAN8.0

Type Severity Type
ALM-26502 RF Unit Optical Module Type Mismatch Fault Major Commu

nication
ALM-26503 RF Unit Optical Module Transmit/ Fault Major Commu

Receive Fault nication
ALM-26504 RF Unit CPRI Interface Error Fault Major Commu

nication
EVT-26505 RF Unit CPRI Interface Switchover Event Minor Commu

nication
ALM-26506 RF Unit Optical Interface Performance Fault Major/ Commu

Degraded Minor nication
ALM-26507 RF Unit Optical Module Fault Fault Warning Commu

nication
ALM-26520 RF Unit TX Channel Gain Out of Range Fault Minor Hardwar

e
ALM-26521 RF Unit RX Channel RTWP/RSSI Too Fault Minor Hardwar

Low e
ALM-26522 RF Unit RX Channel RTWP/RSSI Fault Minor Hardwar

Unbalanced e
ALM-26524 RF Unit PA Overcurrent Fault Major Hardwar

e
ALM-26525 RF Unit Temperature Unacceptable Fault Major/ Hardwar

Minor e
EVT-26526 RF Unit TX Channel Switched Off Event Major Hardwar

e
ALM-26527 RF Unit Input Power Out of Range Fault Major Hardwar

e
EVT-26528 RF Unit TX Channel Switched On Event Minor Hardwar

e
ALM-26529 RF Unit VSWR Threshold Crossed Fault Major/ Hardwar

Minor e
ALM-26530 RF Unit ALD Current Out of Range Fault Minor Hardwar

Warning e
ALM-26531 RF Unit ALD Switch Configuration Fault Minor Hardwar

Mismatch e
ALM-26532 RF Unit Hardware Fault Fault Major/ Hardwar

Minor e
ALM-26533 RF Unit Software Program Error Fault Major Running

SRAN8.0

Type Severity Type
ALM-26534 RF Unit Overload Fault Minor Running
EVT-26535 RF Unit Startup Event Minor Hardwar

e
ALM-26536 RF Unit Multi-Mode Configuration Fault Minor Running

Conflict
ALM-26538 RF Unit Clock Problem Fault Major Hardwar

e
ALM-26540 RF Unit AC Input Power Failure Fault Major Power
ALM-26541 ALD Maintenance Link Failure Fault Major Commu

nication
ALM-26542 RF Unit Backup Power Device Fault Major Commu

Maintenance Link Failure nication
ALM-26543 RF Unit External Device Maintenance Fault Major Commu

Link Failure nication
ALM-26544 RF Unit Power Surge Protector Fault Fault Major Hardwar

e
ALM-26545 RF Unit TX Channel Switched Off Fault Warning Running

Through Command
ALM-26546 RF Unit External Power Supply Fault Major Hardwar

Insufficient Minor e
ALM-26751 RET Antenna Motor Fault Fault Minor Hardwar

e
ALM-26752 ALD Hardware Fault Fault Major/ Hardwar

Minor e
ALM-26753 RET Antenna Not Calibrated Fault Minor Hardwar

e
ALM-26754 RET Antenna Data Loss Fault Minor Hardwar

e
ALM-26755 TMA Bypass Fault Major Hardwar

e
ALM-26757 RET Antenna Running Data and Fault Minor Hardwar

Configuration Mismatch e
ALM-26758 TMA Running Data and Configuration Fault Minor Hardwar

Mismatch e

SRAN8.0
RF Unit and Topology Management 8 Engineering Guidelines (GSM_eGBTS)
8 Engineering Guidelines (GSM_eGBTS)

RF Unit and Topology Management is a basic feature and must be enabled.

characteristics.

None
8.4 Deployment
8.4.1 Requirements

necessary for all scenarios and must be collected. Collect scenario-specific data when necessary
for a specific feature deployment scenario.
There are three types of data sources:
negotiated with the EPC or peer transmission equipment

SRAN8.0
Required Data
l RRU/RFU model
1. The following table describes the parameters related to RRUCHAIN.
Paramete Paramet Setting Notes Data

r Name er ID Source

Chain No. chain or ring in an eGBTS. plan
(negotiati
on not
required)
Topo Type TT l In the star and chain topology, this parameter Network
must be set to CHAIN, and therefore the plan
TCN, TSRN, TSN, and TPN parameters are (negotiati
invalid. In the star topology, only one RRU/ on not
RFU is configured on a chain. required)
l In the ring topology, set this parameter to
RING and configure two CPRI ports and
backup mode.
Backup BM l If the TT parameter is set to CHAIN, the Network

Mode BM parameter must be set to COLD. plan
l If the TT parameter is set to RING, the BM (negotiati
parameter can be set to either COLD (cold- on not
backup ring topology) or HOT (hot-backup required)
ring topology). If the hot backup mode is used,
the ring head and ring tail must belong to
different interface boards, and only one RRU/
RFU can be added.
Access AT l This parameter specifies the access type of Network

Type RXUs. If the access type is local port, the plan
baseband signal processing board is (negotiati
connected to the RRU/RFU through a CPRI on not
port. If the access type is peer port, the local required)
baseband signal processing board is
connected to the peer baseband signal
processing board through the sCPRI channel
on the backplane, and the peer baseband
signal processing board is then connected to
the RRU/RFU.
Head HCN Cabinet number, subrack number, slot number, User-

Cabinet and CPRI port number of the board on which the defined
No. CPRI port serving as the chain/ring head and ring

SRAN8.0

r Name er ID Source
Head HSRN tail is located. These parameters are set according User-
Subrack to site configuration. defined
No.
Head Slot HSN User-

No. defined
Head Port HPN User-

No. defined
Tail TCN User-

Cabinet defined
No.
Tail TSRN User-

Subrack defined
No.
Tail Slot TSN User-

No. defined
Tail Port TPN User-

No. defined
BreakPoin BRKPOS This parameter indicates the sequence number Network

t Position1 1 (counting from the ring or chain head) of an RRU/ plan
RFU behind which a ring or chain breaks. (negotiati
l Only one breakpoint can be configured for an on not
RRU/RFU chain. Two breakpoints must be required)
configured for an RRU/RFU ring.
BreakPoin BRKPOS Network
t Position2 2 l For an RRU/RFU ring, the value of breakpoint plan
1 must not be greater than the value of (negotiati
breakpoint 2. If only one breakpoint can be on not
configured, the values of BreakPoint required)
Position1 and BreakPoint Position2 must be
the same, indicating that the two breakpoints
are the same.
CPRI Line CR This parameter is set by the user or negotiated User-

Rate automatically. defined
2. The following table describes the parameters related to RRU.

r Name er ID Source
Cabinet CN l This parameter for an RRU must be set to 0. User-

No. l This parameter for an RFU can be set to a value defined
ranging from 0 to 62.

SRAN8.0

r Name er ID Source

Slot No. SN l This parameter for an RRU must be set to 0. User-

l This parameter can be set from 0 to 8 for an defined
RFU in a BTS3900AL cabinet, and can be set
cabinets.
RRU TP This parameter specifies the position where an Network

Topology RRU/RFU is installed in the topology. Set this plan
Position parameter to TRUNK. (negotiat
ion not
required)
RRU RCN Set this parameter based on site requirements. Network

Chain No. plan
(negotiat
ion not
required)
RRU PS This parameter specifies the position of an RRU/ Network

Inserted RFU on an RRU/RFU chain or ring. The value of plan
Position this parameter is set sequentially from 0. The (negotiat
value of this parameter for an RRU/RFU must ion not
differ from that for any other RRU/RFU required)
configured on the same RRU/RFU chain.
RRU type RT Set this parameter based on the type of the RF Network
module in use. For details, see 3 RRU/RFU plan
Modules. (negotiat
ion not
required)
RRU RS This parameter specifies the working mode of an Network

Working RRU/RFU. Set this parameter based on site plan
Standard requirements. (negotiat
ion not
required)
RRU RN This parameter is optional. Set this parameter to Network

Name a string containing 0 to 40 characters based on site plan
requirements. (negotiat
This parameter is valid for an RRU. ion not
required)

SRAN8.0

r Name er ID Source
Number of RXNUM Set this parameter to the number of RX channels Network

RX of an RRU/RFU. plan
channels (negotiat
ion not
required)
Number of TXNUM Set this parameter to the number of TX channels Network

TX of an RRU/RFU. plan
channels (negotiat
ion not
required)
l The following table describes the parameters related to RRUCHAIN.
r Name er ID Source
Topo Type TT Set this parameter to CHAIN. Network

plan
(negotiat
ion not
required)
Backup BM Set this parameter to COLD. Network

Mode plan
(negotiat
ion not
required)
Access AT Set this parameter to LOCALPORT. Network

Type plan
(negotiat
ion not
required)
When the dual-star topology is used, set the TT parameter to CHAIN for each mode on the
separate-MPT base station and set the TT parameter to LOADBALANCE on the co-MPT base
station.
l The following table describes the parameters related to RRU.

SRAN8.0
Paramete Paramete Setting Notes Data

r Name r ID Source
RRU RCN Set this parameter to the number of the RRU Network
Chain No. chain. plan
(negotiati
on not
required)
RRU PS Set this parameter to 0. Network

Position plan
(negotiati
on not
required)

r Name er ID Source

plan
(negotiati
on not
required)

Mode plan
(negotiati
on not
required)

Type plan
(negotiati
on not
required)

r Name er ID Source
Chain No. chain. plan
(negotiati
on not
required)

SRAN8.0

r Name er ID Source
RRU PS Set this parameter based on the number of Network

Position RRUs/RFUs. For example, set the parameter to plan
0 for the first RRU/RFU and 1 for the second (negotiati
RRU/RFU. on not
required)

Parameter Paramet Setting Notes Data
Name er ID Source
Topo Type TT Set this parameter to RING. Network

plan
(negotiati
on not
required)
Backup BM Set this parameter to COLD or HOT based on Network

Mode the configuration of the ring topology. plan
(negotiati
on not
required)

Parameter Paramet Setting Notes Data
Name er ID Source
RRU Chain RCN Set this parameter to the number of the RRU Network
No. ring. plan
(negotiati
on not
required)
RRU PS l If the BM parameter is set to COLD, set this Network

Position parameter based on the number of RRUs. For plan
example, set the parameter to 0 for the first (negotiati
RRU and 1 for the second RRU. on not
l If the BM parameter is set to HOT, configure required)
an RRU in position 0.
8.4.3 Precautions
None

SRAN8.0

Obey the following rules when you use an RRU/RFU, or let an MRRU/MRFU work in single-
mode scenarios:
l In the same RFC, the slot numbers must be different for RFUs that work in different network
modes.
l Before adding RRUs/RFUs, you must add RRU/RFU chains or rings.
The following describes the initial configuration in a GSM network.
Configuring a Single eGBTS Using the GUI

Configuration (based on CME) > Creating Base Stations > Creating eGBTSs > Creating
a Single eGBTS > Configuring eGBTS Device Data > Configuring RF Units
Configuring eGBTSs in Batches

Configuration (Based on CME) > Creating Base Stations > Creating eGBTSs > Creating
eGBTSs in Batches
Configuring a Single eGBTS Using MML Commands

1. Run the ADD RRUCHAIN command to add an RRU/RFU chain or ring. In this step, set
RRU/RFU chain or ring parameters in 8.4.2 Data Preparation.
2. Run the ADD RRU command to add an RRU/RFU. In this step, set RRU/RFU parameters
in 8.4.2 Data Preparation.

Event tab page on the eGBTS LMT. For the description of RRU/RFU alarms, see 7.6
Troubleshooting.
On the eGBTS LMT or the M2000, run the DSP BRD command to check the status of the RRU/
RFU.
The status of the RRU/RFU is normal if the value of Availability Status is Normal, as shown
in Figure 8-1.

SRAN8.0
Combining RRU Chains as an RRU Ring
A cold-backup ring topology can be set up by combining two RRU chains during capacity
expansion. The precautions for combining RRU chains as an RRU ring are as follows:
l Before combining two RRU chains into a ring, run the DSP CPRILBR command to check
the consistency between their CPRI data rates. If the CPRI data rates are inconsistent, run
the STR CPRILBRNEG command after combining the RRU chains into a ring.
l The numbers of the two RRU chains to be combined must be different, and the value of
Topo Type must be CHAIN.
l A maximum of eight levels of cascaded RRUs in total are allowed on two RRU chains
before the two RRU chains are combined.
Run the CMB RRUCHAIN command, and set the First RRU Chain No. and Second RRU
Chain No. parameters (parameter IDs: RCN1 and RCN2) to combine the two RRU chains and
set up a cold-backup ring topology.

original topology.
Step 1 Run the MOD RRUCHAIN command to set breakpoints for adding an RRU/RFU to an RRU/
RFU chain or ring. For the settings of related parameters, see 7.4.2 Data Preparation.
Step 2 Run the ADD RRU command to add an RRU/RFU to an RRU/RFU chain or ring. For the settings
of related parameters, see 7.4.2 Data Preparation.
----End
NOTE

Step 1 Run the MOD RRUCHAIN command to set breakpoints for removing an RRU/RFU from an
RRU/RFU chain or ring. For the settings of related parameters, see 7.4.2 Data Preparation.
Step 2 Run the RMV RRU command to remove an RRU/RFU from an RRU/RFU ring or chain. In
this step, set Cabinet No., Subrack No., and Slot No. of the RRU/RFU to be removed.
----End
NOTE

N/A

SRAN8.0
8.6 Troubleshooting
For the description of RF-related alarms and events in GSM mode, see eGBTS Alarm
Reference and eGBTS Event Reference.
Table 8-1 RF-related alarms in GSM mode

Type Severit Type
y

ALM-26502 RF Unit Optical Module Type Fault Major Commu

Mismatch nication


nication

nication
ALM-26506 RF Unit Optical Interface Performance Fault Major Commu


nication

e

Low e

Unbalanced e

e
ALM-26525 RF Unit Temperature Unacceptable Fault Major Hardwar

Minor e

e

e

e

SRAN8.0

Type Severit Type
y
ALM-26529 RF Unit VSWR Threshold Crossed Fault Major Hardwar

Minor e

Warning e

Mismatch e
ALM-26532 RF Unit Hardware Fault Fault Major Hardwar

Minor e

e

Conflict

e

nication



e

Through Command


e
ALM-26752 ALD Hardware Fault Fault Major Hardwar

Minor e

SRAN8.0

Type Severit Type
y

e

e

e
ALM-26756 SASU VSWR Threshold Crossed Fault Major Hardwar

e


Mismatch e
ALM-26759 SASU Running Data and Configuration Fault Minor Hardwar

Mismatch e
ALM-26760 SASU Bypass Fault Major Hardwar

e

SRAN8.0
RF Unit and Topology Management 9 Engineering Guidelines (UMTS)
9 Engineering Guidelines (UMTS)

RF Unit and Topology Management is a basic feature and must be enabled.

characteristics.

None
9.4 Deployment
9.4.1 Requirements

The following types of data sources are available:

SRAN8.0
Required Data
l RRU/RFU model
l RRU/RFU topology, which is used for determining how to configure RRU/RFU links
1. The following table describes the parameters related to RRUCHAIN.
Paramet Parameter Remarks Data
er Name ID Source
RRU RCN This parameter uniquely identifies an RRU/ Network

Chain No. RFU chain or ring in a NodeB. plan
(negotiatio
n not
required)
Topo TT l In the star and chain topologies, this Network

Type parameter must be set to CHAIN, and plan
therefore the TCN, TSRN, TSN, and TPN (negotiatio
parameters are invalid. In the star topology, n not
only one RRU/RFU can be configured for required)
each chain.
l In the ring topology, set this parameter to
RING. Two CPRI ports and the BM
parameter must be configured.
l In the CPRI MUX topology, UMTS is used
as the converging party; therefore, this
parameter is also set to CHAIN for the
CPRI MUX star and chain topologies, the
same as the configurations for the UMTS
star and chain topologies.

l If the TT parameter is set to RING, the (negotiatio
BM parameter can be set to either COLD n not
(cold-backup ring topology) or HOT (hot- required)
backup ring topology). If the hot backup
mode is used, the ring head and ring tail
must belong to different interface boards,
and only one RRU/RFU can be added.

SRAN8.0

er Name ID Source
Access AT l This parameter specifies the access type of Network

Type RXUs. If the access type is local port, the plan
baseband signal processing board is (negotiatio
connected to the RRU/RFU through a CPRI n not
port. If the access type is peer port, the local required)
baseband signal processing board is
connected to the peer baseband signal
processing board through the sCPRI
channel on the backplane, and the peer
baseband signal processing board is then
connected to the RRU/RFU.
Head HCN The cabinet number, subrack number, slot User-

Cabinet number, and CPRI port number of the board on defined
No. which the CPRI port serving as the chain/ring
head and ring tail is located. These parameters
Head HSRN are set according to the onsite configuration. User-
Subrack defined
No.
Head Slot HSN User-

No. defined
Head Port HPN User-

No. defined
Tail TCN User-

Cabinet defined
No.
Tail TSRN User-

Subrack defined
No.
Tail Slot TSN User-

No. defined
Tail Port TPN User-

No. defined
BreakPoi BRKPOS1 This parameter indicates the sequence number Network

nt (counting from the ring or chain head) of an plan
Position1 RRU/RFU behind which a ring or chain (negotiatio
breaks. n not
l Only one breakpoint can be configured for required)
an RRU/RFU chain. Two breakpoints must
be configured for an RRU/RFU ring.
l For an RRU/RFU ring, the value of
breakpoint 1 must not be larger than the
value of breakpoint 2. If only one
breakpoint can be configured, the values of

SRAN8.0

er Name ID Source
BreakPoi BRKPOS2 breakpoint 1 and breakpoint 2 must be the Network

nt same, indicating that the two breakpoints plan
Position2 are the same. (negotiatio
n not
required)
CPRI CR This parameter is set by the user or negotiated User-

Line Rate automatically. defined
2. The following table describes the parameters related to RRU.

er Name ID Source
Cabinet CN l This parameter for an RRU must be set to User-

No. 0. defined
l This parameter for an RFU can be set to a
value ranging from 0 to 62.

l This parameter can be set to 4 or 5 for an
RFU in a BTS3900L cabinet, and must be
set to 4 for an RFU in other types of
cabinets.
Slot No. SN l This parameter for an RRU must be set to User-

0. defined
l This parameter can be set to a value ranging
from 0 to 8 for an RFU in a BTS3900AL
cabinet, and can be set to a value ranging
cabinets.

Topology RRU/RFU is installed in the topology. Set this plan
Position parameter to TRUNK. (negotiatio
n not
required)

SRAN8.0

er Name ID Source

Chain plan
No. (negotiatio
n not
required)
RRU PS This parameter specifies the position of an Network

Inserted RRU/RFU on an RRU/RFU chain or ring. The plan
Position value of this parameter is set sequentially from (negotiatio
0. The value of this parameter for an RRU/ n not
RFU must differ from that for any other RRU/ required)
RFU configured on the same RRU/RFU chain.
RRU RT Set this parameter based on the RRU/RFU type Network

type onsite. For details, see chapter 3 "RRU/RFU plan
Modules." (negotiatio
n not
required)
RRU RS This parameter specifies the working mode of Network

Working an RRU/RFU. Set this parameter based on site plan
Standard requirements. (negotiatio
n not
required)
RRU RN This parameter is optional. Set this parameter Network

Name to a string containing 0 to 40 characters based plan
on site requirements. (negotiatio
This parameter is valid for an RRU. n not
required)
Number RXNUM Set this parameter to the number of RX Network

of RX channels of an RRU/RFU onsite. plan
channels (negotiatio
n not
required)
Number TXNUM Set this parameter to the number of TX Network

of TX channels of an RRU/RFU onsite. plan
channels (negotiatio
n not
required)

SRAN8.0

er Name ID Source

Type plan
(negotiatio
n not
required)

Mode plan
(negotiatio
n not
required)

Type plan
(negotiatio
n not
required)
station.
Paramete Parameter Remarks Data
r Name ID Source
Chain No. chain onsite. plan
(negotiatio
n not
required)

Position plan
(negotiatio
n not
required)


SRAN8.0

r Name ID Source

plan
(negotiatio
n not
required)

Mode plan
(negotiatio
n not
required)

Type plan
(negotiatio
n not
required)

r Name ID Source
Chain No. chain onsite. plan
(negotiatio
n not
required)
RRU PS Set this parameter based on the number of Network

Position RRUs/RFUs. For example, set this plan
parameter to 0 for the first RRU/RFU and 1 (negotiatio
for the second RRU/RFU. n not
required)

r Name ID Source
Topo Type TT Set this parameter to RING. Network

plan
(negotiati
on not
required)

SRAN8.0

r Name ID Source
Backup BM Set this parameter to COLD or HOT based Network

Mode on the configuration of the ring topology plan
onsite. (negotiati
on not
required)
Parameter Parameter Remarks Data

Name ID Source
RRU Chain RCN Set this parameter to the number of the RRU Network
No. ring onsite. plan
(negotiatio
n not
required)
RRU PS l If the BM parameter is set to COLD, set Network

Position this parameter based on the number of plan
RRUs. For example, set this parameter (negotiatio
to 0 for the first RRU and 1 for the second n not
RRU. required)
l If the BM parameter is set to HOT,
configure an RRU/RFU in position 0.
9.4.3 Precautions
None

mode scenarios:
modes.
l Before adding RRUs/RFUs, you must add RRU/RFU chains or rings.
The following describes the initial configuration in a UMTS network.
Configuring a Single NodeB Using the GUI

Configuration (Based on CME) > Creating Base Stations > Creating NodeB > Creating a
Single NodeB > Configuring NodeB Device Data > Configuring RF Units

SRAN8.0
Configuring NodeBs in Batches

Configuration (Based on CME) > Creating Base Stations > Creating NodeB > Creating
NodeBs in Batches
Configuring a Single NodeB Using MML Commands


Event tab page on the NodeB LMT. For the description of RRU/RFU alarms, see 8.6
Troubleshooting.
On the NodeB LMT or the M2000, run the DSP BRD command to check the status of the RRU/
RFU.
in Figure 9-1.

l A maximum of eight levels of cascaded RRUs in total are allowed on two RRU chains
before the two RRU chains are combined.

SRAN8.0
Chain No. parameters (parameter IDs: RCN1 and RCN2) to combine the two RRU chains and
set up a cold-backup ring topology.

original topology.
Step 1 Run the MOD RRUCHAIN command to set breakpoints for adding an RRU/RFU to an RRU/
RFU chain or ring. For the settings of related parameters, see 9.4.2 Data Preparation.
Step 2 Run the ADD RRU command to add an RRU/RFU to an RRU/RFU chain or ring. For the settings
of related parameters, see 9.4.2 Data Preparation.
----End
NOTE

Step 1 Run the MOD RRUCHAIN command to set breakpoints for removing an RRU/RFU from an
RRU/RFU chain or ring. For the settings of related parameters, see 10.4.2 Data Preparation.
Step 2 Run the RMV RRU command to remove an RRU/RFU from an RRU/RFU ring or chain. In
this step, set Cabinet No., Subrack No., and Slot No. of the RRU/RFU to be removed.
----End
NOTE

N/A
9.6 Troubleshooting
For the description of RF-related alarms and events in UMTS mode, see NodeB Alarm
Reference and NodeB Event Reference.
Table 9-1 RF-related alarms and events in UMTS mode

Type Severit Type
y


SRAN8.0

Type Severit Type
y
ALM-26502 RF Unit Optical Module Type Mismatch Fault Major Commu

nication


nication

nication


nication

e

Low e

Unbalanced e

e
ALM-26525 RF Unit Temperature Unacceptable Fault Major Hardwar

Minor e

e

e

e
ALM-26529 RF Unit VSWR Threshold Crossed Fault Major Hardwar

Minor e

Warning e

Mismatch e

SRAN8.0

Type Severit Type
y

Minor e

e

Conflict

e

nication



e

Through Command


e
ALM-26752 ALD Hardware Fault Fault Major Hardwar

Minor e

e

e

e
ALM-26756 SASU VSWR Threshold Crossed Fault Major Hardwar

e

SRAN8.0

Type Severit Type
y


Mismatch e
ALM-26759 SASU Running Data and Configuration Fault Minor Hardwar

Mismatch e
ALM-26760 SASU Bypass Fault Major Hardwar

e

SRAN8.0
RF Unit and Topology Management 10 Engineering Guidelines (LTE)
10 Engineering Guidelines (LTE)


characteristics.

None
10.4 Deployment
10.4.1 Requirements
CAUTION
If the hot-backup ring topology is used, two CPRI fiber optic cables of the same length are
required.

SRAN8.0

The following types of data sources are available:
Required Data
l RRU/RFU model
l RRU/RFU topology, which is used for determining how to configure RRU/RFU links
l Working mode of the eNodeB: FDD, TDD, or FDD+TDD
1. The following table describes the parameters that must be set in an RRUCHAIN MO to
configure an RRU/RFU chain or ring.
Parame Parameter Remarks Data

ter ID Source
Name

Chain chain or ring in an eNodeB. plan
No. (negotiat
ion not
required
)
Topo TT l In the star and chain topologies, this parameter Network

Type must be set to CHAIN, and therefore the plan
TCN, TSRN, TSN, and TPN parameters are (negotiat
invalid. In the star topology, only one RRU/ ion not
RFU can be configured for each chain. required
l In the ring topology, set this parameter to )
RING. Two CPRI ports and the BM parameter
must be configured.
l In CPRI MUX star and chain topologies, set
this parameter to CHAIN, which is the same
as the parameter setting for the LTE star and
chain topologies.
l In the load-sharing ring topology, set this
parameter to LOADBALANCE and
configure two CPRI ports to implement the
load-sharing ring topology.

SRAN8.0

ter ID Source
Name

l If the TT parameter is set to RING, the BM (negotiat
parameter can be set to either COLD (cold- ion not
backup ring topology) or HOT (hot-backup required
ring topology). If the hot-backup ring topology )
is used, the ring head and tail must belong to
different interface boards, and only one RRU/
RFU can be added.
Head HCN The cabinet number, subrack number, slot User-

Cabinet number, and CPRI port number of the board on defined
No. which the CPRI port serving as the chain/ring
head and ring tail is located. These parameters are
Head HSRN set according to the onsite configuration. User-
Subrack defined
No.
Head HSN User-

Slot No. defined
Head HPN User-

Port No. defined
Tail TCN User-

Cabinet defined
No.
Tail TSRN User-

Subrack defined
No.
Tail Slot TSN User-

No. defined
Tail Port TPN User-

No. defined
BreakPo BRKPOS1 This parameter indicates the sequence number Network

int (counting from the ring or chain head) of an RRU/ plan
position RFU behind which a ring or chain breaks. (negotiat
1 l Only one breakpoint can be configured for an ion not
RRU/RFU chain. Two breakpoints must be required
configured for an RRU/RFU ring. )
BreakPo BRKPOS2 l For an RRU/RFU ring, the value of breakpoint Network

int 1 must not be larger than the value of plan
position breakpoint 2. If only one breakpoint can be (negotiat
2 configured, the values of breakpoint 1 and ion not
breakpoint 2 must be the same, indicating that required
the two breakpoints are the same. )

SRAN8.0

ter ID Source
Name
Access AT If an LTE network adopts the CPRI MUX Network

Type topology, set this parameter to PEERPORT on plan
the LTE side. If an LTE network adopts other (negotiat
topologies, set this parameter to LOCALPORT. ion not
required
)
CPRI CR This parameter is set by the user or negotiated User-

Line automatically. defined
Rate
2. The following table describes the parameters that must be set in an RRU/RFU MO to

ter ID Source
Name
Cabinet CN l This parameter for an RRU MO must be set to User-

No. 0. defined
l This parameter for an RFU MO can be set to
a value ranging from 0 to 62.
Subrack SRN l This parameter for an RRU MO can be set to User-

No. a value ranging from 60 to 254. defined
Slot No. SN l This parameter for an RRU MO must be set to User-

0. defined
l This parameter can be set to a value ranging
from 0 to 8 for an RFU in a BTS3900AL
cabinet, and can be set to a value ranging from
0 to 5 for an RFU in other types of cabinets.
RRU RN This parameter is optional. Set this parameter to a Network

Name string containing 0 to 40 characters based on site plan
requirements. (negotiat
This parameter is valid for an RRU. ion not
required
)
RRU RT Set this parameter based on the RRU/RFU type Network

type onsite. For details, see chapter 3 "RRU/RFU plan
Modules." (negotiat
ion not
required
)

SRAN8.0

ter ID Source
Name
RRU PS This parameter specifies the position of an RRU/ Network

Inserted RFU on an RRU/RFU chain or ring. The value of plan
Position this parameter is set sequentially from 1. The value (negotiat
of this parameter for an RRU or RFU MO must ion not
differ from that for any other RRU or RFU MOs required
configured on the same RRUCHAIN MO. )

Chain plan
No. (negotiat
ion not
required
)

Topolog RRU/RFU is installed in the topology. Set this plan
y parameter to TRUNK. (negotiat
Position ion not
required
)
RRU RS This parameter specifies the working mode of an Network

Workin RRU/RFU. Set this parameter based on site plan
g requirements. (negotiat
Standar ion not
d required
)
Number RXNUM Set this parameter to the number of RX channels Network

of RX of an RRU/RFU onsite. plan
channels (negotiat
ion not
required
)
Number TXNUM Set this parameter to the number of TX channels Network

of TX of an RRU/RFU onsite. plan
channels (negotiat
ion not
required
)

SRAN8.0
l The following table describes the parameters that must be set in an RRUCHAIN MO to
ter ID Source
Name

Type plan
(negotia
tion not
required
)

Mode plan
(negotia
tion not
required
)

Type plan
(negotia
tion not
required
)
station.
l The following table describes the parameters that must be set in an RRU/RFU MO to
configure an RRU/RFU.
ter ID Source
Name
RRU RCN Set this parameter to the number of the RRU or Network
Chain RFU chain onsite. plan
No. (negotia
tion not
required
)

Inserted plan
Position (negotia
tion not
required
)

SRAN8.0
configure an RRU chain or ring.

ter ID Source
Name

Type plan
(negotia
tion not
required
)

Mode plan
(negotia
tion not
required
)

Type plan
(negotia
tion not
required
)
l The following table describes the parameters that must be set in an RRU MO to configure
an RRU.

ter ID Source
Name
RRU RCN Set this parameter to the number of the RRU chain Network
Chain onsite. plan
No. (negotiat
ion not
required
)
RRU PS Set this parameter based on the number of RRUs. Network

Inserted For example, set the parameter to 0 for the first plan
Position RRU and 1 for the second RRU. (negotiat
ion not
required
)
Scenario 3: Cold-backup or hot-backup ring topology
configure an RRU chain or ring.

SRAN8.0
Paramet Paramete Remarks Data

er Name r ID Source
Topo TT Set this parameter to RING. Network

Type plan
(negotiati
on not
required)
Backup BM Set this parameter to COLD or HOT based on the Network

Mode configuration of the ring topology onsite. plan
(negotiati
on not
required)
an RRU.

er Name r ID Source
RRU RCN Set this parameter to the number of the RRU ring Network
Chain onsite. plan
No. (negotiati
on not
required)
RRU PS l If the BM parameter is set to COLD, set this Network

Inserted parameter based on the number of RRUs. For plan
Position example, set the parameter to 0 for the first(negotiati
RRU and 1 for the second RRU. on not
l If the BM parameter is set to HOT, configure required)
an RRU in position 0.
Scenario 4: Load-sharing ring topology
l The following table describes the parameter that must be set in an RRUCHAIN MO to
configure an RRU chain.

er r ID Source
Name
Topo TT Set this parameter to LOADBALANCE. Network

Type plan
(negotiati
on not
required)
an RF unit.

SRAN8.0
Parame Paramete Remarks Data

ter r ID Source
Name
RRU RCN Set this parameter to the number of the RRU chain Network
Chain or ring onsite. plan
No. (negotiati
on not
required)
RRU PS Set this parameter to 0. The LTE load-sharing ring Network

Inserted topology supports only one-level RRU cascading. plan
Position (negotiati
on not
required)
Scenario 5: RHUB-based star topology

l The following table describes the parameter that must be set in an RRUCHAIN MO to
configure an RRU chain.
er r ID Source
Name
Topo TT This parameter indicates the topology type for an Network

Type RHUB. Set this parameter to CHAIN. plan
(negotiati
on not
required)
l The following table describes the parameters that must be set in an RHUB MO to configure
an RHUB.
ter r ID Source
Name
RRU RCN This parameter uniquely identifies an RHUB Network

No. (negotiati
on not
required)
RRU PS This parameter specifies the position of an RHUB Network

Position on an RHUB chain or ring. For example, set this plan
parameter to 0 for the first-level RHUB and 1 for (negotiati
the second-level RHUB, and so on. on not
required)

SRAN8.0

ter r ID Source
Name
RHUB RS This parameter specifies the working mode of an Network

Work RHUB. Set this parameter to TDL(LTE TDD). plan
Standard (negotiati
on not
required)
l The following table describes the parameters that must be set in an RRU/RFU MO to
configure a pRRU.
Parameter Parame Remarks Data
Name ter ID Source
RRU Topo TP This parameter specifies the position where a Network

Position pRRU is installed in the topology. Set this plan
parameter to CHAIN. (negotiatio
n not
required)
RRU Chain RCN This parameter uniquely identifies an RHUB Network

No. chain or ring in an eNodeB. plan
(negotiatio
n not
required)
RRU PS This parameter specifies the position of an Network

Position RHUB on an RHUB chain or ring. For example, plan
set this parameter to 0 for the first-level RHUB (negotiatio
and 1 for the second-level RHUB, and so on. n not
required)
RRU type RT This parameter specifies a pRRU type. Set this Network
parameter to MPRRU. plan
(negotiatio
n not
required)
RF Unit RS This parameter specifies the working mode of Network

Working a pRRU. Set this parameter to TDL plan
Mode (LTE_TDD). (negotiatio
n not
required)
Branch Port PI This parameter specifies the port number of a Network

pRRU on the RHUB. plan
(negotiatio
n not
required)

SRAN8.0
10.4.3 Precautions
N/A

mode scenarios:
modes.
l Configure only one MRRU/MRFU, which cannot contain cascaded RRUs/RFUs.
The following describes the initial configuration in an LTE network.
Configuring a Single eNodeB Using the GUI

Configuration (Based on CME) > Creating Base Stations > Creating an eNodeB > Creating
a Single eNodeB > Configuring eNodeB Device Data > Configuring RF Units
Configuring eNodeBs in Batches

Configuration (Based on CME) > Creating Base Stations > Creating an eNodeB > Creating
eNodeBs in Batches
Configuring a Single eNodeB Using MML Commands

2. Run the ADD RHUB command to add an RHUB. (This step applies only to scenario 5.)

Event tab page on the eNodeB LMT. For the description of RRU/RFU alarms, see 10.6
Troubleshooting.
On the eNodeB LMT or the M2000, run the DSP BRD command to check the status of the RRU/
RFU.
in Figure 10-1.

SRAN8.0

l The FDD mode allows a maximum of four levels of cascaded RRUs in total on the two
RRU chains to be combined.
l If the AT parameters of RRU chains are set to PEERPORT, the RRU chains cannot be
combined.
l The chain, cold-backup ring, and hot-backup ring topologies cannot be configured
concurrently on one LBBPb/LBBPc.
Chain No. parameters (parameter IDs: RCN1 and RCN2) to combine two RRU chains, and set
up a cold-backup ring topology.
Adding an RRU to an RRU Chain or Ring

An RRU can be added to any position in an RRU chain or ring without changing the original
topology.
Step 1 Run the MOD RRUCHAIN command to set breakpoints for adding an RRU to an RRU chain
or ring. For the settings of parameters, see the information about the RRUCHAIN MO in "10.4.2
Data Preparation."
Step 2 Run the ADD RRU command to add an RRU to an RRU chain or ring. For the settings of
parameters, see the information about the RRU MO in "10.4.2 Data Preparation."
----End
NOTE

SRAN8.0
Removing an RRU from an RRU Chain or Ring

Step 1 Run the MOD RRUCHAIN command to set breakpoints for removing an RRU from an RRU
chain or ring. For the settings of parameters, see the information about the RRUCHAIN MO in
"10.4.2 Data Preparation."
Step 2 Run the RMV RRU command to remove an RRU from an RRU ring or chain. In this step, set
Cabinet No., Subrack No., and Slot No. of the RRU to be removed.
----End
NOTE

None
10.6 Troubleshooting
For the description of RF-related alarms and events in LTE mode, see eNodeB Alarm
Reference and eNodeB Event Reference.
Table 10-1 RF-related alarms and events in LTE mode

Type Severit Type
y
ALM-26235 RF Unit Maintenance Link Failure Fault Major Hardwar

e
ALM-26236 RRU Cascading Levels and Configuration Fault Major Hardwar

Mismatch e
ALM-26237 RRU Network Breakpoint Fault Major Hardwar

e
ALM-26238 RRU Network Topology Type and Fault Major Hardwar

ALM-26239 RX Channel RTWP/RSSI Unbalanced Fault Minor Hardwar

Between RF Units e


nication


SRAN8.0

Type Severit Type
y

nication

e

Low e

Unbalanced e

Minor e

Through Command

SRAN8.0
RF Unit and Topology Management 11 Engineering Guidelines (Dual Modes)
11 Engineering Guidelines (Dual Modes)


characteristics.

N/A
11.4 Deployment
11.4.1 Requirements

necessary for all scenarios and must be collected. Collect scenario-specific data when necessary
for a specific feature deployment scenario.
Required Data

SRAN8.0
l RRU/RFU model
In addition, collect required data specific to each mode by referring to the corresponding section.
l For details about GBTSs, see 7.4.2 Data Preparation.
l For details about eGBTSs, see 8.4.2 Data Preparation.
l For details about NodeBs, see 9.4.2 Data Preparation.
l For details about eNodeBs, see 10.4.2 Data Preparation.
Obey the following rules when preparing data for RRUs/RFUs working in multimode scenarios:
l The RRUs/RFUs are configured for and monitored by the base stations of different network
modes together.
l The configurations of the RRUs/RFUs are the same on the base stations of different network
modes. If the configurations are inconsistent, the ALM-26274 Inter-System Board Object
Configuration Conflict alarm is generated. Cabinet, subrack, and slot information must be
consistent. Table 11-1 describes other parameters that must be consistent.
Table 11-1 Multimode base station common parameters

GSM Parameters UMTS Parameters LTE Parameters Setting
Notes
Param Param Conf Para Para Confi Para Para Co
eter eter igura meter mete gurat meter meter nfig
Name ID tion Name r ID ion Name ID urat
Com Com ion
man mand Co
d mm
and
Topo TT ADD Topo TT ADD Topo TT AD Set this

Type BTS Type RRU Type D parameter
RXU CHA RR to
CHA IN UC CHAIN.
IN HA
IN
- - - Back BM ADD Back BM AD Set this

up RRU up D parameter
Mode CHA Mode RR to COLD.
IN UC
HA
IN

SRAN8.0
Board BT ADD RRU RT ADD RRU RT AD Set this

type BTS type / type D/ parameter
RXU MO MO based on
BRD D D the type of
RRU RR the RF
U module in
use. For
details,
see 3
RRU/
RFU
Modules.
Worki WOR SET RRU RS ADD RRU RS AD Set this

ng KING BTS Work / Work D/ parameter
Standa STAN RXU Stand MO ing MO to GU,
rd DAR BP ard D Stand D GL, or
D RRU ard RR UL based
U on site
configurat
ion.
MRR SndR SET Numb RXN ADD Numb RXN AD Set this
U/ cvMo BTS er of UM / er of UM D/ parameter
GRRU de2 RXU RX MO RX MO based on
Sendin SndR BP chann D chann D site
g cvMo els RRU els RR configurat
Receiv de3 U ion.
ing
Mode SET Numb TXN ADD Numb TXN AD Set this
BTS er of UM / er of UM D/ parameter
MRFU
RXU TX MO TX MO based on
/
BP chann D chann D site
GRFU
els RRU els RR configurat
Sendin
U ion.
g
Receiv
ing
Mode
Associ RELA SET - - - - - - Set this

ated TED BTS parameter
Board CN RXU based on
CN BP site
configurat
ion.

ated TEDS BTS parameter
Board RN RXU based on
SRN BP site
configurat
ion.

SRAN8.0

ated TEDS BTS parameter
Board N RXU based on
SN BP site
configurat
ion.
IF IFOF SET IfOffs IFO ADD - - - Set this

Offset FSET BTS et FFS / parameter
RXU ET MO to 0.
BP D
RRU
Lvl1 Lvl1V SET VSW ALM ADD VSW ALM AD Set this
Vswr swr BTS R THR / R THR D/ parameter
RXU alarm HLD MO alarm HLD MO to 20.
BP thresh D thresh D
old RRU old RR
U
Seriou VSW SET VSW ALM ADD VSW ALM AD Set this
s RAL BTS R PRO / R PRO D/ parameter
VSW MDIS RXU alarm CSW MO alarm CSW MO to ON.
R POSE BP post- D post- D
Alarm proce RRU proce RR
Post- ssing ssing U
proces switc switc
sing h h
Mode
Lvl2 Lvl2 SET VSW ALM ADD VSW ALM AD Set this
Vswr Vswr BTS R PRO / R PRO D/ parameter
RXU alarm CTH MO alarm CTH MO to 20.
BP post- RHL D post- RHL D
proce D RRU proce D RR
ssing ssing U
thresh thresh
old old
Anten MRR SET Atten ATT MO Rx ATT MO Set this

na UATT BTS uation EN D Chan EN D parameter
Tribut ENF RXU RXB nel RX to 0.
ary 1 ACT BP RAN Atten BR
Factor OR1 CH uation AN
CH
Anten MRR SET Atten ATT MO Rx ATT MO Set this

na UATT BTS uation EN D Chan EN D parameter
Tribut ENF RXU RXB nel RX to 0.
ary 2 ACT BP RAN Atten BR
Factor OR2 CH uation AN
CH

SRAN8.0
Scenario 1: Dual-star topology
The data to be prepared for the dual-star topology integrates those for each mode in the star
topology.
station.
Scenario 2: CPRI MUX topology
The CPRI MUX topology applies only to UL dual-mode base stations. In this scenario, the LTE
and UMTS serve as the converged and converging parties, respectively, and only the star and
chain CPRI MUX topologies are allowed. In the CPRI MUX topology, the RRU configuration
on the LTE takes effect only when the RRU configuration on the UMTS is complete.
For details about data preparation for the CPRI MUX topology on the converging party (the
UMTS mode), see the data preparation for the star and chain topologies used by the UMTS
mode. The CPRI MUX topology on the converged party (the LTE mode) has similar
configurations as the star and chain topologies used by the LTE mode, except the configurations
in the RRUCHAIN MO. The following table lists the differences.
Paramet Parameter Setting Notes Data

er Name ID Source

No. (negotiatio
n not
required)
Topo TT In the CPRI MUX topology, the configurations for Network

Type star and chain convergence are the same as the plan
configurations for the star and chain topologies. Set (negotiatio
this parameter to CHAIN. n not
required)
Backup BM If the TT parameter is set to CHAIN, the BM Network

Mode parameter must be set to COLD. plan
(negotiatio
n not
required)
Access AT For the converged party, set this parameter to Network

Type PEERPORT. plan
(negotiatio
n not
required)
Head HCN Set the cabinet, subrack, slot, and port numbers to User-
Cabinet numbers of the cabinet, subrack, slot, and port defined
No. corresponding to the converging party's optical port
that is directly connected to the RRU onsite.

SRAN8.0
Paramet Parameter Setting Notes Data

er Name ID Source
Head HSRN User-

Subrack defined
No.
Head Slot HSN User-

No. defined
Head HPN User-

Port No. defined
11.4.3 Precautions
None

Configuring a Single Multimode Base Station Using the GUI
the "Procedure" according to the following paths: 3900 Series Base Station Initial
Configuration (Based on CME) > Creating Base Stations > Creating Multimode Base
Stations > Creating a Single Separate-MPT Multimode Base Station > Configuring Device
Data > Configuring RF Units
3900 Series Base Station Initial Configuration (Based on CME) > Creating Base Stations
> Creating Multimode Base Stations > Creating a Single Co-MPT Multimode Base Station
> Configuring Device Data > Configuring RF Units
Configuring Multimode Base Stations in Batches

the "Procedure" according to the following paths: 3900 Series Base Station Initial
Configuration (Based on CME) > Creating Base Stations > Creating Multimode Base
Stations > Creating Separate-MPT Multimode Base Stations in Batches (Summary Data
File)
3900 Series Base Station Initial Configuration (Based on CME) > Creating Base Stations
> Creating Multimode Base Stations > Creating Co-MPT Multimode Base Stations in
Batches (Summary Data File)
Configuring a Single Multimode Base Station Using MML Commands

Perform operations on the single-mode base stations of a multimode base station separately.
l For details about GBTSs, see 7.4.4 Initial Configuration.
l For details about eGBTSs, see 8.4.4 Initial Configuration.
l For details about NodeBs, see 9.4.4 Initial Configuration.
l For details about eNodeBs, see 10.4.4 Initial Configuration.

SRAN8.0

Perform operations on the single-mode base stations of a multimode base station separately.
l For details about GBTSs, see 7.4.5 Activation Observation.

l For details about eGBTSs, see 8.4.5 Activation Observation.
l For details about NodeBs, see 9.4.5 Activation Observation.
l For details about eNodeBs, see 10.4.5 Activation Observation.
In the CPRI MUX topology, you can add an RRU to or remove an RRU from an RRU chain.
Adding an RRU to an RRU Chain

Cascaded RRUs can be added to an RRU chain without changing the original topology. You
need to add the same RRU information on both modes.
Step 1 Run the MOD RRUCHAIN command on the converging party (UMTS) to set breakpoints. For
the settings of parameters, see "9.4.2 Data Preparation."
Step 2 Run the ADD RRU command on the converging party (UMTS) and the converged party (LTE)
to add an RRU. See "9.4.2 Data Preparation" for UMTS parameter settings, "10.4.2 Data
Preparation" for LTE parameter settings, and "10.4.2 Data Preparation" for the settings of
UMTS/LTE common parameters.
Step 3 Adjust the RRU connection in the CPRI MUX topology and add an RRU to the specified
position.
Step 4 Run the MOD RRUCHAIN command on the converging party (UMTS) to remove the
breakpoints.
----End
Removing an RRU from an RRU Chain

Cascaded RRUs can be removed from an RRU chain without changing the original topology.
You need to delete the same RRU information on both modes.
Step 1 Run the MOD RRUCHAIN command on the converging party (UMTS) to set breakpoints. For
the settings of parameters, see "9.4.2 Data Preparation."
Step 2 Run the RMV RRU command on the converging party (UMTS) and the converged party (LTE)
to remove an RRU.
Step 3 Adjust the RRU connection in the CPRI MUX topology and remove an RRU from the specified
position.
Step 4 Run the MOD RRUCHAIN command on the converging party (UMTS) to remove the
breakpoints.
----End

SRAN8.0

None
11.6 Troubleshooting
For the description of RF-related alarms in multiple modes, see 3900 Series Multi-Mode Base
Station Alarm Reference.
Table 11-2 RF-related alarms and events in multiple modes

Type Severit Type
y
ALM-26272 Inter-System RF Unit Parameter Settings Fault Major Hardwar

Conflict Warning e
ALM-26274 Inter-System Board Object Fault Major Hardwar

Configuration Conflict e
ALM-26278 RF Unit Working Mode and Board Fault Major Hardwar

Capability Mismatch e

SRAN8.0
RF Unit and Topology Management 12 Reference Documents
12 Reference Documents
1. Installation guides for the relevant base stations

2. BSC6910/BSC6900 GSM MML Command Reference
3. BSC6910/BSC6900 GSM Parameter Reference
4. BSC6910/BSC6900 GSM Alarm Reference
5. BSC6910/BSC6900 GSM Event Reference
6. NodeB MML Command Reference
7. NodeB Parameter Reference
8. NodeB Alarm Reference
9. NodeB Event Reference
10. eNodeB MML Command Reference
11. eNodeB Parameter Reference
12. eNodeB Alarm Reference
13. eNodeB Event Reference
14. 3900 Series Base Station Alarm Reference
15. 3900 Series Base Station Initial Configuration Guide
16. eNodeB Initial Configuration Guide
17. RAN Reconfiguration Guide
18. eNodeB Reconfiguration Guide


RF Unit and Topology Management SRAN8 0 Draft B PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RF Unit and Topology Management SRAN8 0 Draft B PDF

Uploaded by

Copyright:

Available Formats

SRAN8.

RF Unit and Topology Management

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential ii

7.4.2 Data Preparation......................................................................................................................................25

8 Engineering Guidelines (GSM_eGBTS).................................................................................37

9 Engineering Guidelines (UMTS).............................................................................................49

10 Engineering Guidelines (LTE)................................................................................................62

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential iii

10.4.4 Initial Configuration..............................................................................................................................72

11 Engineering Guidelines (Dual Modes).................................................................................76

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential iv

Figure 4-1 Star topology for RRUs/RFUs.............................................................................................................14

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential v

Table 7-1 RF-related alarms in GSM mode...........................................................................................................34

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential vi

1 About This Document

l BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D)

1.2 Intended Audience

l Need to understand RF Unit and Topology Management

1.3 Change History

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 1

Change Change Description Parameter

Change Type Change Description Parameter Change

Feature change Added new RF modules. None

Deleted RRU/RFU None

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 2

2.1 Introduction to RF Modules

2.2 Introduction to RRU/RFU Topologies

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 3

3.2 RRU/RFU Modules in GSM Mode

RRU3004 DRRU 2T2R - Star, chain, or

RRU3008 V1 GRRU 2T2R RRU3008_V1 Star, chain, or

RRU3008 V2 GRRU 2T2R RRU3008_V2 Star, chain, or

RRU3908 V1 MRRU 2T2R RRU3908_V1 Star or chain

RRU3908 V2 MRRU 2T2R RRU3908_V2 Star or chain

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 4

Model Logical Type TX/RX RRU/RFU Topology

RRU3922E MRRU 2T2R RRU3922E Star or chain

RRU3926 MRRU 1T2R RRU3926 Star or chain

RRU3936 MRRU 1T2R RRU3936 Star or chain

RRU3928 MRRU 2T2R RRU3928 Star or chain

RRU3961 MRRU 2T2R RRU3961 Star or chain

RRU3929 MRRU 2T2R RRU3929 Star or chain

RRU3942 MRRU 2T4R RRU3942 Star or chain

DRFU DRFU 2T2R - Star or chain

GRFU V1 GRFU 1T2R GRFU_V1 Star or chain

GRFU V2 GRFU 1T2R GRFU_V2 Star or chain

GRFU V2a GRFU 1T2R GRFU_V2a Star or chain

MRFU V1 MRFU 1T2R MRFU_V1 Star or chain

MRFU V2 MRFU 1T2R MRFU_V2 Star or chain

Issue Draft B (2013-02-08) Huawei Proprietary and Confidential 5

Model Logical Type TX/RX RRU/RFU Topology

MRFU V2a MRFU 1T2R MRFU_V2a Star or chain

MRFUd MRFU 2T2R MRFUd Star or chain

MRFUe MRFU 1T2R MRFUe Star or chain

3.3 RRU/RFU Modules in UMTS Mode

RRU3801E MRRU 1T2R Star topology, chain

RRU3801C MRRU 1T2R Star topology, chain