RF Unit and Topology Management (SRAN8.0 - Draft B)

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

Copyright Huawei Technologies Co., Ltd.
SRAN8.0
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

ii
SRAN8.0
Contents
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

iii
SRAN8.0
Contents
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

iv
SRAN8.0
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

SRAN8.0
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

vi
SRAN8.0
1 About This Document
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)
BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D)
BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D)
BTS3900AL (Ver.A)
DBS3900
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
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.
Editorial change:

SRAN8.0
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)
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
Type
Change Description
Parameter
Change
Feature
change
Added the Long Term Evolution (LTE) load-sharing ring

topology and engineering guidelines for this topology.
None
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
topologies from the CPRI
MUX topology and added the
deleted part to CPRI MUX
Feature Parameter
Description.
None

SRAN8.0
2 Overview
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
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
3 RRU/RFU Modules
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
Channel
RRU/RFU
Specifications
Topology
RRU3004
DRRU
2T2R
Star, chain, or
ring topology
RRU3008 V1
GRRU
2T2R
RRU3008_V1
(RRU3008 V1
SPEC)
Star, chain, or
ring topology
RRU3008 V2
GRRU
2T2R
RRU3008_V2
(RRU3008 V2
SPEC)
Star, chain, or
ring topology
RRU3908 V1
MRRU
2T2R
RRU3908_V1
(RRU3908 V1
SPEC)
Star or chain
topology
RRU3908 V2
MRRU
2T2R
RRU3908_V2
(RRU3908 V2
SPEC)
Star or chain
topology

SRAN8.0
3 RRU/RFU Modules
Model
Logical Type
TX/RX
Channel
RRU/RFU
Specifications
Topology
RRU3922E
MRRU
2T2R
RRU3922E
(RRU3922E
SPEC)
Star or chain
topology
RRU3926
MRRU
1T2R
RRU3926
(RRU3926
SPEC)
Star or chain
topology
RRU3936
MRRU
1T2R
RRU3936
(RRU3936
SPEC)
Star or chain
topology
RRU3928
MRRU
2T2R
RRU3928
(RRU3928
SPEC)
Star or chain
topology
RRU3961
MRRU
2T2R
RRU3961
(RRU3961
SPEC)
Star or chain
topology
RRU3929
MRRU
2T2R
RRU3929
(RRU3929
SPEC)
Star or chain
topology
RRU3942
MRRU
2T4R
RRU3942
(RRU3942
SPEC)
Star or chain
topology
DRFU
DRFU
2T2R
Star or chain
topology
GRFU V1
GRFU
1T2R
GRFU_V1
(GRFU V1
SPEC)
Star or chain
topology
GRFU V2
GRFU
1T2R
GRFU_V2
(GRFU V2
SPEC)
Star or chain
topology
GRFU V2a
GRFU
1T2R
GRFU_V2a
(GRFU V2a
SPEC)
Star or chain
topology
MRFU V1
MRFU
1T2R
MRFU_V1
(MRFU V1
SPEC)
Star or chain
topology
MRFU V2
MRFU
1T2R
MRFU_V2
(MRFU V2
SPEC)
Star or chain
topology

SRAN8.0
3 RRU/RFU Modules
Model
Logical Type
TX/RX
Channel
RRU/RFU
Specifications
Topology
MRFU V2a
MRFU
1T2R
MRFU_V2a
(MRFU V2a
SPEC)
Star or chain
topology
MRFUd
MRFU
2T2R
MRFUd
(MRFUd
SPEC)
Star or chain
topology
MRFUe
MRFU
1T2R
MRFUe
(MRFUe SPEC)
Star or chain
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 coldbackup ring topology
between two
baseband signal
processing boards
RRU3801C
MRRU
1T2R

between two
baseband signal
processing boards
RRU3804
MRRU
1T2R

between two
baseband signal
processing boards
RRU3805
MRRU
2T2R

between two
baseband signal
processing boards

SRAN8.0
3 RRU/RFU Modules
Model
Logical Type
TX/RX Channel
Topology
RRU3806
MRRU
1T2R

between two
baseband signal
processing boards
RRU3808
MRRU
2T2R

between two
baseband signal
processing boards
RRU3828
MRRU
2T2R

between two
baseband signal
processing boards
RRU3829
MRRU
2T2R

between two
baseband signal
processing boards
RRU3832
MRRU
2T4R

between two
baseband signal
processing boards
RRU3838
MRRU
2T2R

between two
baseband signal
processing boards
RRU3908 V1
MRRU
2T2R
Star topology
RRU3908 V2
MRRU
2T2R
Star topology
RRU3926
MRRU
1T2R
Star topology
RRU3936
MRRU
1T2R
Star topology
RRU3841
MRRU
4T4R
Star topology
RRU3928
MRRU
2T2R
Star topology

SRAN8.0
3 RRU/RFU Modules
Model
Logical Type
TX/RX Channel
Topology
RRU3929
MRRU
2T2R
Star topology
RRU3942
MRRU
2T4R
Star topology
RRU3821E
PRRU
2T2R

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 V2
MRFU
1T2R
Star topology
MRFU V2a
MRFU
1T2R
Star topology
MRFU V3
MRFU
1T2R
Star topology
MRFUd
MRFU
2T2R
Star topology
MRFUe
MRFU
1T2R
Star topology
3.4 RRU/RFU Modules in LTE Mode

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

ring topology on one baseband signal
processing board, cold-backup ring
topology between two baseband signal
processing boards, or hot-backup ring
topology
RRU3203
LRRU
2T2R

topology

SRAN8.0
Duplex
Mode
3 RRU/RFU Modules
Model
Logic
al
Type
TX/RX
Chann
el
Topology
RRU3220
LRRU
2T2R

topology
RRU3221
LRRU
2T2R

processing boards, hot-backup ring
topology, or load-sharing ring topology
RRU3222
LRRU
2T2R

topology
RRU3229
LRRU
2T2R

topology
RRU3240
LRRU
2T4R

RRU3808
LRRU
2T2R

RRU3841
LRRU
4T4R


SRAN8.0
Duplex
Mode
3 RRU/RFU Modules
Model
Logic
al
Type
TX/RX
Chann
el
Topology
RRU3268
LRRU
2T2R

RRU3821E
PRRU
2T2R
Star topology, chain topology, or coldbackup ring topology between two

baseband signal processing boards
RRU3908
V1
MRR
U
2T2R
Star or chain topology
RRU3908
V2
MRR
U
2T2R
RRU3928
MRR
U
2T2R
RRU3938
MRR
U
2T2R
RRU3929
MRR
U
2T2R
RRU3942
MRR
U
2T4R
LRFU
LRFU
2T2R
Star topology or hot-backup ring topology
LRFUe
LRFU
2T2R
Star topology or hot-backup ring topology
MRFU V1
MRF
U
1T2R
Star topology
MRFU V2
MRF
U
1T2R
Star topology
MRFU V2a
MRF
U
1T2R
Star topology
MRFUd
MRF
U
2T2R
Star topology
CRFUd
MRF
U
2T2R
Star topology
RRU3961
MRR
U
2T2R
RRU3936
MRR
U
1T2R

10
SRAN8.0
Duplex
Mode
Time
division
duplex
(TDD)
3 RRU/RFU Modules
Model
Logic
al
Type
TX/RX
Chann
el
Topology
RRU3926
MRR
U
1T2R
RRU3232
MRR
U
4T4R

RRU3251
MRR
U
2T2R

processing boards, or load-sharing ring
topology
RRU3152-e
MRR
U
2T2R
Star topology, chain topology, or loadsharing ring topology
RRU3702
MRR
U
4T4R
Star topology, cold-backup ring topology

on one baseband signal processing board,
or cold-backup ring topology between two
baseband signal processing boards
RRU3235
MRR
U
4T4R
Star topology
RRU3253
MRR
U
8T8R
Star topology or load-sharing ring topology
RRU3252
MRR
U
4T4R

topology
RRU3254
MRR
U
4T4R

topology
RRU3256
MRR
U
4T4R

topology

11
SRAN8.0
Duplex
Mode
3 RRU/RFU Modules
Model
Logic
al
Type
TX/RX
Chann
el
Topology
pRRU3901
MPR
U
2T2R
3.5 RRU/RFU Modules in Multimode Scenarios

Model
Logical Type
TX/RX Channel
Topology
RRU3908 V1
MRRU
2T2R
Dual-star topology
RRU3908 V2
MRRU
2T2R
Dual-star topology
RRU3926
MRRU
1T2R
Dual-star topology
RRU3928
MRRU
2T2R
Dual-star topology
RRU3929
MRRU
2T2R
Dual-star topology
RRU3942
MRRU
2T4R
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

between two
baseband signal
processing boards

12
SRAN8.0
4 RRU/RFU Topologies
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.

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

14
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.
UMTS supports a maximum of eight cascading levels for RRUs or two cascading levels
for RFUs.
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.

15
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 interboard 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.

16
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).
UMTS supports a maximum of eight cascading levels for RRUs.
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.

17
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.
LTE FDD supports a maximum of four cascading levels for RRUs or eight cascading levels
for PRRUs.
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.

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

19
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 loadsharing 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

20
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

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

22
SRAN8.0
5 Related Features
Related Features
None

23
SRAN8.0
6 Network Impact
Network Impact
No impact.

24
SRAN8.0
7 Engineering Guidelines (GSM_GBTS)
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.
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
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the evolved packet core (EPC) or peer transmission equipment

25
SRAN8.0
User-defined: parameter values set by users
Required Data
Collect the following information before preparing required data:
l
RRU/RFU model
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
ter
Name
Parame
ter ID
Setting Notes
Data
Source
RRU
Chain
No.
RCN
This parameter uniquely identifies an RRU/RFU

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

must be set to CHAIN. In the star topology, plan
only one RRU/RFU is configured on a chain. (negotiation
not
l In the ring topology, set this parameter to
required)
RING and configure two CPRI ports.
Head
Cabinet
No.
HCN
Head
Subrack
No.
HSRN
Head
Slot No.
HSN
Head
Port No.
HPN
Tail
Cabinet
No.
TCN
Tail
Subrack
No.
TSRN
Tail Slot
No.
TSN
Cabinet number, subrack number, slot number,

and CPRI port number of the board on which the
CPRI port serving as the chain/ring head and ring
tail is located. These parameters are set according
to site configuration.
When configuring cabinet, subrack, slot, and port
numbers, satisfy the following requirements:
l Cabinet number: 0 to 7.
l Subrack number: 0 or 1.
l When the GTMU is used to connect an RRU/
RFU, you can only set a slot number to 6.
l When the UBRI is used to connect RRU/RFU,
set a slot number to 2.
l When the GBBP is used to connect an RRU/
RFU, you can set a slot number to a value in
the range of 0 to 4.
l Optical port number: 0 to 5. The values of
Head Port No. and Tail Port No. cannot be
the same.
Tail Port
No.
TPN

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

Parame
ter
Name
Parame
ter ID
Setting Notes
Data
Source
Board
Type
BT
Set this parameter based on the type of the RF

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

module to transmit RF signals. Set this parameter
based on the hardware type for the RF module.
For details, see 3 RRU/RFU Modules.
Network
plan
(negotiation
not
required)
Cabinet
No.
CN
l This parameter for an RRU must be set to 0.
Userdefined
Subrack
No.
SRN
l This parameter for an RFU can be set to a

value ranging from 0 to 62.
l This parameter for an RRU can be set to a
Userdefined
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 can be set from 0 to 8 for an
RFU in a BTS3900AL cabinet, and can be set
from 0 to 5 for an RFU in other types of
cabinets.
Userdefined
RXU
Chain
No.
RXUCH
AINNO
Set this parameter based on site requirements.
Network
plan
(negotiation
not
required)
RXU
Board
Position
RXUPO
S
This parameter specifies the position of an RRU/

RFU on an RRU/RFU chain or ring. The value of
this parameter is set sequentially from 1. The
value of this parameter for an RRU/RFU must
differ from that for any other RRU/RFU
configured on the same RRU/RFU chain.
Network
plan
(negotiation
not
required)
In the chain topology, an RRU/RFU directly

connected to the BBU is the chain head and is
sequentially numbered from 1.

27
SRAN8.0
3.
Parame
ter
Name
Parame
ter ID
Setting Notes
Data
Source
Power
Class
PWRM
ODE
Set this parameter based on the specified power

mode.
Network
plan
(negotiation
not
required)
The following table describes the parameters related to BTSRXUBP.

Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
RXU
Chain
No.
RXUCH
AINNO
Network
plan
(negotiation
not
required)
RXU
Name
RXUNA
ME
This parameter is optional. Set this parameter to

a string containing 1 to 64 characters based on site
requirements.
Network
plan
(negotiation
not
required)
RXU
Board
Type
RXUTY
PE
Set this parameter based on the type of the RXU

in use. The setting must be consistent with that of
the BT parameter. For details, see 3 RRU/RFU
Modules.
Network
plan
(negotiation
not
required)
Workin
g
Standar
d
WORKI
NGSTA
NDARD
This parameter specifies the working mode of an

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

28
SRAN8.0
Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
Topo
Type
TT
Set this parameter to CHAIN.
Network
plan
(negotiation
not
required)

Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
RXU
Chain
No.
RXUCH
AINNO
Set this parameter to the number of the RRU/RFU

chain.
Network
plan
(negotiation
not
required)
RXU
Board
Position
RXUPO
S
Set this parameter to 1.
Network
plan
(negotiation
not
required)
Scenario 2: Chain topology

l

Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
Topo
Type
TT
Network
plan
(negotiation
not
required)

29
SRAN8.0
Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
RXU
Chain
No.
RXUCH
AINNO
Set this parameter to the number of the RRU/RFU

chain.
Network
plan
(negotiatio
n not
required)
RXU
Board
Position
RXUPO
S
Set this parameter based on the number of RRUs/ Network

RFUs. For example, set the parameter to 1 for the plan
first RRU/RFU and 2 for the second RRU/RFU. (negotiatio
n not
required)
Scenario 3: Ring topology

l

Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
Topo
Type
TT
Set this parameter to RING.
Network
plan
(negotiatio
n not
required)

Parame
ter
Name
Paramet
er ID
Setting Notes
Data
Source
RXU
Chain
No.
RXUCH
AINNO
Set this parameter to the number of the RRU ring.
Network
plan
(negotiatio
n not
required)
RXU
Board
Position
RXUPO
S
Set this parameter based on the number of RRUs.

For example, set the parameter to 1 for the first
RRU and 2 for the second RRU.
Network
plan
(negotiatio
n not
required)
7.4.3 Precautions
N/A

30
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

31
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
Name
Parameter ID
Remarks
Chain No.
RCN
This parameter uniquely identifies an RXU chain/ring

in a GBTS.
Position of
Break Point 1/
Position of
Break Point 2
BP1
BP2
l If you want to split one RXU ring into one RXU

chain, set BP1 at the end of the chain.
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.
Parameter
Name
Parameter ID
Remarks
Chain No.
RCN
This parameter uniquely identifies an RXU chain/ring

in a GBTS.
Separate
Position
SEPARATEPO
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.
Combining one or more RXU chains into an RXU ring
Run the CBN BTSRXUCHAIN command to combine one or more RXU chains.

32
SRAN8.0
Parameter
Name
Parameter ID
Remarks
Combine Type
CHAINTORIN
G
This parameter identifies the combination type.

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

second RXU chains.
Second RXU
Chain No.
RCN2
Tail Cabinet
No.
TCN
Tail Subrack
No.
TSRN
Tail Slot No.
TSN
Tail Port No.
TPN
The four parameters are mandatory only when the value

of Combine Type is CHAINTORING. Set them to the
onsite cabinet number, subrack number, slot number of
the tail CPRI port, and the tail CPRI port number,
respectively.
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.
Parameter
Name
Parameter ID
Remarks
Chain No.
RCN
This parameter uniquely identifies an RRU/RFU chain

or ring in a GBTS.
Position of
Break Point 1/
Position of
Break Point 2
BP1
BP2
l Only one breakpoint is allowed in one RXU chain,

and the value of this parameter must be smaller than
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

33
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.
Parameter
Name
Parameter ID
Remarks
Chain No.
RCN
This parameter uniquely identifies an RRU/RFU chain

or ring in a GBTS.
Position of
Break Point 1/
Position of
Break Point 2
BP1
BP2
l Only one breakpoint is allowed in one RXU chain,

and the value of this parameter must be smaller than
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
Type
Alarm
Severity
Event
Type
ALM-26501
RF Unit Optical Module or Electrical

Port Not Ready
Fault
Major
Commu
nication

34
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severity
Event
Type
ALM-26502
RF Unit Optical Module Type Mismatch
Fault
Major
Commu
nication
ALM-26503
RF Unit Optical Module Transmit/

Receive Fault
Fault
Major
Commu
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

Degraded
Fault
Major/
Minor
Commu
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

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

Unbalanced
Fault
Minor
Hardwar
e
ALM-26524
RF Unit PA Overcurrent
Fault
Major
Hardwar
e
ALM-26525
RF Unit Temperature Unacceptable
Fault
Major/
Minor
Hardwar
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/
Minor
Hardwar
e
ALM-26530
RF Unit ALD Current Out of Range
Fault
Minor
Hardwar
e
Warning
ALM-26531
RF Unit ALD Switch Configuration

Mismatch
Fault
Minor
Hardwar
e
ALM-26532
RF Unit Hardware Fault
Fault
Major/
Minor
Hardwar
e
ALM-26533
RF Unit Software Program Error
Fault
Major
Running

35
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severity
Event
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

Conflict
Fault
Minor
Running
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

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

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

Through Command
Fault
Warning
Running
ALM-26546
RF Unit External Power Supply

Insufficient
Fault
Major
Hardwar
e
ALM-26751
RET Antenna Motor Fault
Fault
Minor
Hardwar
e
ALM-26752
ALD Hardware Fault
Fault
Major/
Minor
Hardwar
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

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

Mismatch
Fault
Minor
Hardwar
e

Minor
36
SRAN8.0
8 Engineering Guidelines (GSM_eGBTS)
Engineering Guidelines (GSM_eGBTS)

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

l
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:
l
negotiated with the EPC or peer transmission equipment

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

Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
RRU
Chain No.
RCN

chain or ring in an eGBTS.
Network
plan
(negotiati
on not
required)
Topo Type
TT
l In the star and chain topology, this parameter

must be set to CHAIN, and therefore the
TCN, TSRN, TSN, and TPN parameters are
invalid. In the star topology, only one RRU/
RFU is configured on a chain.
Network
plan
(negotiati
on not
required)

RING and configure two CPRI ports and
backup mode.
Backup
Mode
BM
l If the TT parameter is set to CHAIN, the

BM parameter must be set to COLD.
l If the TT parameter is set to RING, the BM
parameter can be set to either COLD (coldbackup ring topology) or HOT (hot-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.
Network
plan
(negotiati
on not
required)
Access
Type
AT
l This parameter specifies the access type of

RXUs. If the access type is local port, the
baseband signal processing board is
connected to the RRU/RFU through a CPRI
port. If the access type is peer port, the local
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.
Network
plan
(negotiati
on not
required)
Head
Cabinet
No.
HCN
Cabinet number, subrack number, slot number,

and CPRI port number of the board on which the
CPRI port serving as the chain/ring head and ring
Userdefined

38
SRAN8.0
2.
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Head
Subrack
No.
HSRN
tail is located. These parameters are set according

to site configuration.
Userdefined
Head Slot
No.
HSN
Userdefined
Head Port
No.
HPN
Userdefined
Tail
Cabinet
No.
TCN
Userdefined
Tail
Subrack
No.
TSRN
Userdefined
Tail Slot
No.
TSN
Userdefined
Tail Port
No.
TPN
Userdefined
BreakPoin
t Position1
BRKPOS
1
BreakPoin
t Position2
BRKPOS
2
CPRI Line
Rate
CR
This parameter indicates the sequence number

(counting from the ring or chain head) of an RRU/
RFU behind which a ring or chain breaks.
l Only one breakpoint can be configured for 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 greater than the value of
breakpoint 2. If only one breakpoint can be
configured, the values of BreakPoint
Position1 and BreakPoint Position2 must be
the same, indicating that the two breakpoints
are the same.
Network
plan
(negotiati
on not
required)
This parameter is set by the user or negotiated

automatically.
Userdefined
Network
plan
(negotiati
on not
required)
The following table describes the parameters related to RRU.
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Cabinet
No.
CN
Userdefined
l This parameter for an RFU can be set to a value

ranging from 0 to 62.

39
SRAN8.0
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Subrack
No.
SRN

Userdefined

Slot No.
SN

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

RRU/RFU is installed in the topology. Set this
parameter to TRUNK.
Network
plan
(negotiat
ion not
required)
RRU
Chain No.
RCN
Network
plan
(negotiat
ion not
required)
RRU
Inserted
Position
PS

this parameter is set sequentially from 0. The
value of this parameter for an RRU/RFU must
differ from that for any other RRU/RFU
configured on the same RRU/RFU chain.
Network
plan
(negotiat
ion not
required)

RRU type
RT
Set this parameter based on the type of the RF

module in use. For details, see 3 RRU/RFU
Modules.
Network
plan
(negotiat
ion not
required)
RRU
Working
Standard
RS

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

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

40
SRAN8.0
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Number of
RX
channels
RXNUM
Set this parameter to the number of RX channels

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

of an RRU/RFU.
Network
plan
(negotiat
ion not
required)
l

Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Topo Type
TT
Network
plan
(negotiat
ion not
required)
Backup
Mode
BM
Set this parameter to COLD.
Network
plan
(negotiat
ion not
required)
Access
Type
AT
Set this parameter to LOCALPORT.
Network
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

41
SRAN8.0
Paramete
r Name
Paramete
r ID
Setting Notes
Data
Source
RRU
Chain No.
RCN
Set this parameter to the number of the RRU

chain.
Network
plan
(negotiati
on not
required)
RRU
Position
PS
Network
plan
(negotiati
on not
required)

l

Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
Topo Type
TT
Network
plan
(negotiati
on not
required)
Backup
Mode
BM
Network
plan
(negotiati
on not
required)
Access
Type
AT
Network
plan
(negotiati
on not
required)
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
RRU
Chain No.
RCN

chain.
Network
plan
(negotiati
on not
required)

42
SRAN8.0
Paramete
r Name
Paramet
er ID
Setting Notes
Data
Source
RRU
Position
PS
Set this parameter based on the number of

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

l

Parameter
Name
Paramet
er ID
Setting Notes
Data
Source
Topo Type
TT
Network
plan
(negotiati
on not
required)
Backup
Mode
BM
Set this parameter to COLD or HOT based on

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

Parameter
Name
Paramet
er ID
Setting Notes
Data
Source
RRU Chain
No.
RCN

ring.
Network
plan
(negotiati
on not
required)
RRU
Position
PS
l If the BM parameter is set to COLD, set this

parameter based on the number of RRUs. For
example, set the parameter to 0 for the first
Network
plan
(negotiati
on not
required)
l If the BM parameter is set to HOT, configure

an RRU in position 0.
8.4.3 Precautions
None

43
SRAN8.0

Obey the following rules when you use an RRU/RFU, or let an MRRU/MRFU work in singlemode scenarios:
l
In the same RFC, the slot numbers must be different for RFUs that work in different network
modes.
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.

44
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.
The numbers of the two RRU chains to be combined must be different, and the value of
Topo Type must be CHAIN.
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

45
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
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26501

Port Not Ready
Fault
Major
Commu
nication
ALM-26502
RF Unit Optical Module Type

Mismatch
Fault
Major
Commu
nication
ALM-26503

Receive Fault
Fault
Major
Commu
nication
ALM-26504
Fault
Major
Commu
nication
EVT-26505
Event
Minor
Commu
nication
ALM-26506

Degraded
Fault
Major
Commu
nication
ALM-26507
Fault
Warning
Commu
nication
ALM-26520
Fault
Minor
Hardwar
e
ALM-26521

Low
Fault
Minor
Hardwar
e
ALM-26522

Unbalanced
Fault
Minor
Hardwar
e
ALM-26524
Fault
Major
Hardwar
e
ALM-26525
Fault
Major
Hardwar
e
Minor
Minor
EVT-26526
Event
Major
Hardwar
e
ALM-26527
Fault
Major
Hardwar
e
EVT-26528
Event
Minor
Hardwar
e

46
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26529
Fault
Major
Hardwar
e
Minor
ALM-26530
Fault
Minor
Warning
Hardwar
e
ALM-26531

Mismatch
Fault
Minor
Hardwar
e
ALM-26532
Fault
Major
Minor
Hardwar
e
ALM-26533
Fault
Major
Running
ALM-26534
RF Unit Overload
Fault
Minor
Running
EVT-26535
RF Unit Startup
Event
Minor
Hardwar
e
ALM-26536

Conflict
Fault
Minor
Running
ALM-26538
Fault
Major
Hardwar
e
ALM-26540
Fault
Major
Power
ALM-26541
Fault
Major
Commu
nication
ALM-26542

Fault
Major
Commu
nication
ALM-26543

Link Failure
Fault
Major
Commu
nication
ALM-26544
Fault
Major
Hardwar
e
ALM-26545

Through Command
Fault
Warning
Running
ALM-26546

Insufficient
Fault
Major
Hardwar
e
ALM-26751
Fault
Minor
Hardwar
e
ALM-26752
ALD Hardware Fault
Fault
Major
Hardwar
e
Minor
Minor

47
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26753
Fault
Minor
Hardwar
e
ALM-26754
Fault
Minor
Hardwar
e
ALM-26755
TMA Bypass
Fault
Major
Hardwar
e
ALM-26756
SASU VSWR Threshold Crossed
Fault
Major
Hardwar
e
ALM-26757

Fault
Minor
Hardwar
e
ALM-26758

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

Mismatch
Fault
Minor
Hardwar
e
ALM-26760
SASU Bypass
Fault
Major
Hardwar
e

48
SRAN8.0
9 Engineering Guidelines (UMTS)
Engineering Guidelines (UMTS)

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

l
characteristics.

None
9.4 Deployment
9.4.1 Requirements

The following types of data sources are available:
l

49
SRAN8.0
Required Data
l
RRU/RFU model
RRU/RFU topology, which is used for determining how to configure RRU/RFU links
1.

Paramet
er Name
Parameter
ID
Remarks
Data
Source
RRU
Chain No.
RCN
This parameter uniquely identifies an RRU/

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

parameter must be set to CHAIN, and
therefore the TCN, TSRN, TSN, and TPN
parameters are invalid. In the star topology,
only one RRU/RFU can be configured for
each chain.
Network
plan
(negotiatio
n not
required)

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.
Backup
Mode
BM

l If the TT parameter is set to RING, the
BM parameter can be set to either COLD
(cold-backup ring topology) or HOT (hotbackup 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.

Network
plan
(negotiatio
n not
required)
50
SRAN8.0
Paramet
er Name
Parameter
ID
Remarks
Data
Source
Access
Type
AT
l This parameter specifies the access type of

RXUs. If the access type is local port, the
connected to the RRU/RFU through a CPRI
port. If the access type is peer port, the local
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.
Network
plan
(negotiatio
n not
required)
Head
Cabinet
No.
HCN
Userdefined
Head
Subrack
No.
HSRN
The cabinet number, subrack number, slot

number, and CPRI port number of the board on
which the CPRI port serving as the chain/ring
head and ring tail is located. These parameters
are set according to the onsite configuration.
Head Slot
No.
HSN
Userdefined
Head Port
No.
HPN
Userdefined
Tail
Cabinet
No.
TCN
Userdefined
Tail
Subrack
No.
TSRN
Userdefined
Tail Slot
No.
TSN
Userdefined
Tail Port
No.
TPN
Userdefined
BreakPoi
nt
Position1
BRKPOS1

(counting from the ring or chain head) of an
RRU/RFU behind which a ring or chain
breaks.
l Only one breakpoint can be configured for
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

Userdefined
Network
plan
(negotiatio
n not
required)
51
SRAN8.0
2.
Paramet
er Name
Parameter
ID
BreakPoi
nt
Position2
BRKPOS2
CPRI
Line Rate
CR
Remarks
breakpoint 1 and breakpoint 2 must be the
same, indicating that the two breakpoints
are the same.

automatically.
Data
Source
Network
plan
(negotiatio
n not
required)
Userdefined

Paramet
er Name
Parameter
ID
Remarks
Data
Source
Cabinet
No.
CN
l This parameter for an RRU must be set to

0.
Userdefined
l This parameter for an RFU can be set to a

Subrack
No.
SRN

Userdefined
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.
Userdefined
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.
RRU
Topology
Position
TP

parameter to TRUNK.

Network
plan
(negotiatio
n not
required)
52
SRAN8.0
Paramet
er Name
Parameter
ID
Remarks
Data
Source
RRU
Chain
No.
RCN
Network
plan
(negotiatio
n not
required)
RRU
Inserted
Position
PS
This parameter specifies the position of an

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

RRU
type
RT
Set this parameter based on the RRU/RFU type

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

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

to a string containing 0 to 40 characters based
on site requirements.
Network
plan
(negotiatio
n not
required)

Number
of RX
channels
RXNUM
Set this parameter to the number of RX

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

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

53
SRAN8.0

Paramet
er Name
Parameter
ID
Remarks
Data
Source
Topo
Type
TT
Network
plan
(negotiatio
n not
required)
Backup
Mode
BM
Network
plan
(negotiatio
n not
required)
Access
Type
AT
Network
plan
(negotiatio
n not
required)
station.
l

Paramete
r Name
Parameter
ID
Remarks
Data
Source
RRU
Chain No.
RCN

chain onsite.
Network
plan
(negotiatio
n not
required)
RRU
Position
PS
Network
plan
(negotiatio
n not
required)

l

54
SRAN8.0
Paramete
r Name
Parameter
ID
Remarks
Data
Source
Topo Type
TT
Network
plan
(negotiatio
n not
required)
Backup
Mode
BM
Network
plan
(negotiatio
n not
required)
Access
Type
AT
Network
plan
(negotiatio
n not
required)

Paramete
r Name
Parameter
ID
Remarks
Data
Source
RRU
Chain No.
RCN

chain onsite.
Network
plan
(negotiatio
n not
required)
RRU
Position
PS
Set this parameter based on the number of

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

l
Paramete
r Name
Parameter
ID
Remarks
Data
Source
Topo Type
TT
Network
plan
(negotiati
on not
required)

55
SRAN8.0
Paramete
r Name
Parameter
ID
Remarks
Data
Source
Backup
Mode
BM
Set this parameter to COLD or HOT based

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

Parameter
Name
Parameter
ID
Remarks
Data
Source
RRU Chain
No.
RCN

ring onsite.
Network
plan
(negotiatio
n not
required)
RRU
Position
PS
l If the BM parameter is set to COLD, set

this parameter based on the number of
RRUs. For example, set this parameter
to 0 for the first RRU and 1 for the second
RRU.
Network
plan
(negotiatio
n not
required)
l If the BM parameter is set to HOT,

configure an RRU/RFU in position 0.
9.4.3 Precautions
None

l
modes.
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

56
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

1.
2.

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.

57
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
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26501

Port Not Ready
Fault
Major
Commu
nication

58
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26502
RF Unit Optical Module Type Mismatch
Fault
Major
Commu
nication
ALM-26503

Receive Fault
Fault
Major
Commu
nication
ALM-26504
Fault
Major
Commu
nication
EVT-26505
Event
Minor
Commu
nication
ALM-26506

Degraded
Fault
Major
Commu
nication
ALM-26507
Fault
Warning
Commu
nication
ALM-26520
Fault
Minor
Hardwar
e
ALM-26521

Low
Fault
Minor
Hardwar
e
ALM-26522

Unbalanced
Fault
Minor
Hardwar
e
ALM-26524
Fault
Major
Hardwar
e
ALM-26525
Fault
Major
Hardwar
e
Minor
Minor
EVT-26526
Event
Major
Hardwar
e
ALM-26527
Fault
Major
Hardwar
e
EVT-26528
Event
Minor
Hardwar
e
ALM-26529
Fault
Major
Hardwar
e
Minor
ALM-26530
Fault
Minor
Warning
ALM-26531

Mismatch

Fault
Minor
Hardwar
e
Hardwar
e
59
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26532
Fault
Major
Minor
Hardwar
e
ALM-26533
Fault
Major
Running
ALM-26534
RF Unit Overload
Fault
Minor
Running
EVT-26535
RF Unit Startup
Event
Minor
Hardwar
e
ALM-26536

Conflict
Fault
Minor
Running
ALM-26538
Fault
Major
Hardwar
e
ALM-26540
Fault
Major
Power
ALM-26541
Fault
Major
Commu
nication
ALM-26542

Fault
Major
Commu
nication
ALM-26543

Link Failure
Fault
Major
Commu
nication
ALM-26544
Fault
Major
Hardwar
e
ALM-26545

Through Command
Fault
Warning
Running
ALM-26546

Insufficient
Fault
Major
Hardwar
e
ALM-26751
Fault
Minor
Hardwar
e
ALM-26752
ALD Hardware Fault
Fault
Major
Hardwar
e
Minor
Minor
ALM-26753
Fault
Minor
Hardwar
e
ALM-26754
Fault
Minor
Hardwar
e
ALM-26755
TMA Bypass
Fault
Major
Hardwar
e
ALM-26756
SASU VSWR Threshold Crossed
Fault
Major
Hardwar
e

60
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26757

Fault
Minor
Hardwar
e
ALM-26758

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

Mismatch
Fault
Minor
Hardwar
e
ALM-26760
SASU Bypass
Fault
Major
Hardwar
e

61
SRAN8.0
10 Engineering Guidelines (LTE)
10
Engineering Guidelines (LTE)


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

62
SRAN8.0

The following types of data sources are available:
l
Required Data
l
RRU/RFU model
RRU/RFU topology, which is used for determining how to configure RRU/RFU links
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
ter
Name
Parameter
ID
Remarks
Data
Source
RRU
Chain
No.
RCN

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

must be set to CHAIN, and therefore the
TCN, TSRN, TSN, and TPN parameters are
invalid. In the star topology, only one RRU/
RFU can be configured for each chain.
Network
plan
(negotiat
ion not
required
)

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.

63
SRAN8.0
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
Backup
Mode
BM

Network
plan
(negotiat
ion not
required
)
l If the TT parameter is set to RING, the BM

parameter can be set to either COLD (coldbackup ring topology) or HOT (hot-backup
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
Cabinet
No.
HCN
The cabinet number, subrack number, slot

number, and CPRI port number of the board on
which the CPRI port serving as the chain/ring
head and ring tail is located. These parameters are
set according to the onsite configuration.
Head
Subrack
No.
HSRN
Head
Slot No.
HSN
Userdefined
Head
Port No.
HPN
Userdefined
Tail
Cabinet
No.
TCN
Userdefined
Tail
Subrack
No.
TSRN
Userdefined
Tail Slot
No.
TSN
Userdefined
Tail Port
No.
TPN
Userdefined
BreakPo
int
position
1
BRKPOS1
BreakPo
int
position
2
BRKPOS2

(counting from the ring or chain head) of an RRU/
RFU behind which a ring or chain breaks.
Userdefined
Userdefined
l Only one breakpoint can be configured for an

RRU/RFU chain. Two breakpoints must be
configured for an RRU/RFU ring.
Network
plan
(negotiat
ion not
required
)
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 breakpoint 1 and
breakpoint 2 must be the same, indicating that
the two breakpoints are the same.
Network
plan
(negotiat
ion not
required
)

64
SRAN8.0
2.
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
Access
Type
AT
If an LTE network adopts the CPRI MUX

topology, set this parameter to PEERPORT on
the LTE side. If an LTE network adopts other
topologies, set this parameter to LOCALPORT.
Network
plan
(negotiat
ion not
required
)
CPRI
Line
Rate
CR

automatically.
Userdefined
The following table describes the parameters that must be set in an RRU/RFU MO to
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
Cabinet
No.
CN
l This parameter for an RRU MO must be set to

0.
Userdefined
l This parameter for an RFU MO can be set to

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

a value ranging from 60 to 254.
Userdefined

Slot No.
SN
l This parameter for an RRU MO must be set to

0.
Userdefined
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
Name
RN
This parameter is optional. Set this parameter to a

string containing 0 to 40 characters based on site
requirements.
RRU
type
RT
Set this parameter based on the RRU/RFU type

onsite. For details, see chapter 3 "RRU/RFU
Modules."

Network
plan
(negotiat
ion not
required
)
Network
plan
(negotiat
ion not
required
)
65
SRAN8.0
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
RRU
Inserted
Position
PS

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

RRU
Chain
No.
RCN
Network
plan
(negotiat
ion not
required
)
RRU
Topolog
y
Position
TP

parameter to TRUNK.
Network
plan
(negotiat
ion not
required
)
RRU
Workin
g
Standar
d
RS

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

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

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

66
SRAN8.0
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
Topo
Type
TT
Network
plan
(negotia
tion not
required
)
Backup
Mode
BM
Network
plan
(negotia
tion not
required
)
Access
Type
AT
Network
plan
(negotia
tion not
required
)
station.
l
configure an RRU/RFU.
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
RRU
Chain
No.
RCN
Set this parameter to the number of the RRU or

RFU chain onsite.
Network
plan
(negotia
tion not
required
)
RRU
Inserted
Position
PS
Network
plan
(negotia
tion not
required
)


67
SRAN8.0
configure an RRU chain or ring.
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
Topo
Type
TT
Network
plan
(negotia
tion not
required
)
Backup
Mode
BM
Network
plan
(negotia
tion not
required
)
Access
Type
AT
Network
plan
(negotia
tion not
required
)
The following table describes the parameters that must be set in an RRU MO to configure
an RRU.
Parame
ter
Name
Parameter
ID
Remarks
Data
Source
RRU
Chain
No.
RCN
Set this parameter to the number of the RRU chain

onsite.
Network
plan
(negotiat
ion not
required
)
RRU
Inserted
Position
PS
Set this parameter based on the number of RRUs.

For example, set the parameter to 0 for the first
Network
plan
(negotiat
ion not
required
)
Scenario 3: Cold-backup or hot-backup ring topology

l
configure an RRU chain or ring.

68
SRAN8.0
Paramet
er Name
Paramete
r ID
Remarks
Data
Source
Topo
Type
TT
Network
plan
(negotiati
on not
required)
Backup
Mode
BM
Set this parameter to COLD or HOT based on the

configuration of the ring topology onsite.
Network
plan
(negotiati
on not
required)
an RRU.
Paramet
er Name
Paramete
r ID
Remarks
Data
Source
RRU
Chain
No.
RCN
Set this parameter to the number of the RRU ring

onsite.
Network
plan
(negotiati
on not
required)
RRU
Inserted
Position
PS
l If the BM parameter is set to COLD, set this

parameter based on the number of RRUs. For
example, set the parameter to 0 for the first
Network
plan
(negotiati
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.
Paramet
er
Name
Paramete
r ID
Remarks
Data
Source
Topo
Type
TT
Set this parameter to LOADBALANCE.
Network
plan
(negotiati
on not
required)
an RF unit.

69
SRAN8.0
Parame
ter
Name
Paramete
r ID
Remarks
Data
Source
RRU
Chain
No.
RCN
Set this parameter to the number of the RRU chain

or ring onsite.
Network
plan
(negotiati
on not
required)
RRU
Inserted
Position
PS
Set this parameter to 0. The LTE load-sharing ring

topology supports only one-level RRU cascading.
Network
plan
(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.
Paramet
er
Name
Paramete
r ID
Remarks
Data
Source
Topo
Type
TT
This parameter indicates the topology type for an

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

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

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

70
SRAN8.0
Parame
ter
Name
Paramete
r ID
Remarks
Data
Source
RHUB
Work
Standard
RS

RHUB. Set this parameter to TDL(LTE TDD).
Network
plan
(negotiati
on not
required)
configure a pRRU.
Parameter
Name
Parame
ter ID
Remarks
Data
Source
RRU Topo
Position
TP
This parameter specifies the position where a

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

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

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

parameter to MPRRU.
Network
plan
(negotiatio
n not
required)
RF Unit
Working
Mode
RS
This parameter specifies the working mode of

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

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

71
SRAN8.0
10.4.3 Precautions
N/A

l
modes.
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

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

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.

72
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.
If the AT parameters of RRU chains are set to PEERPORT, the RRU chains cannot be
combined.
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

73
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
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26235
RF Unit Maintenance Link Failure
Fault
Major
Hardwar
e
ALM-26236
RRU Cascading Levels and Configuration

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

Fault
Major
Hardwar
e
ALM-26239
RX Channel RTWP/RSSI Unbalanced

Between RF Units
Fault
Minor
Hardwar
e
ALM-26503

Receive Fault
Fault
Major
Commu
nication
ALM-26504
Fault
Major
Commu
nication
ALM-26506

Degraded
Fault
Major
Commu
nication

Minor
74
SRAN8.0
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26507
Fault
Warning
Commu
nication
ALM-26520
Fault
Minor
Hardwar
e
ALM-26521

Low
Fault
Minor
Hardwar
e
ALM-26522

Unbalanced
Fault
Minor
Hardwar
e
ALM-26532
Fault
Major
Minor
Hardwar
e
ALM-26533
Fault
Major
Running
ALM-26545

Through Command
Fault
Warning
Running

75
SRAN8.0
11
11 Engineering Guidelines (Dual Modes)
Engineering Guidelines (Dual Modes)


l
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

76
SRAN8.0
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.
For details about eGBTSs, see 8.4.2 Data Preparation.
For details about NodeBs, see 9.4.2 Data Preparation.
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.
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
eter
Name
Param
eter
ID
Conf
igura
tion
Com
man
d
Para
meter
Name
Para
mete
r ID
Confi
gurat
ion
Com
mand
Para
meter
Name
Para
meter
ID
Co
nfig
urat
ion
Co
mm
and
Topo
Type
TT
ADD
BTS
RXU
CHA
IN
Topo
Type
TT
ADD
RRU
CHA
IN
Topo
Type
TT
AD
D
RR
UC
HA
IN
Set this
parameter
to
CHAIN.
Back
up
Mode
BM
ADD
RRU
CHA
IN
Back
up
Mode
BM
AD
D
RR
UC
HA
IN
Set this
parameter
to COLD.

77
SRAN8.0
Board
type
BT
ADD
BTS
RXU
BRD
RRU
type
RT
ADD
/
MO
D
RRU
RRU
type
RT
AD
D/
MO
D
RR
U
Set this
parameter
based on
the type of
the RF
module in
use. For
details,
see 3
RRU/
RFU
Modules.
Worki
ng
Standa
rd
WOR
KING
STAN
DAR
D
SET
BTS
RXU
BP
RRU
Work
Stand
ard
RS
ADD
/
MO
D
RRU
RRU
Work
ing
Stand
ard
RS
AD
D/
MO
D
RR
U
Set this
parameter
to GU,
GL, or
UL based
on site
configurat
ion.
MRR
U/
GRRU
Sendin
g
Receiv
ing
Mode
MRFU
/
GRFU
Sendin
g
Receiv
ing
Mode
SndR
cvMo
de2
SndR
cvMo
de3
SET
BTS
RXU
BP
Numb
er of
RX
chann
els
RXN
UM
ADD
/
MO
D
RRU
Numb
er of
RX
chann
els
RXN
UM
AD
D/
MO
D
RR
U
Set this
parameter
based on
site
configurat
ion.
SET
BTS
RXU
BP
Numb
er of
TX
chann
els
TXN
UM
ADD
/
MO
D
RRU
Numb
er of
TX
chann
els
TXN
UM
AD
D/
MO
D
RR
U
Set this
parameter
based on
site
configurat
ion.
Associ
ated
Board
CN
RELA
TED
CN
SET
BTS
RXU
BP
Set this
parameter
based on
site
configurat
ion.
Associ
ated
Board
SRN
RELA
TEDS
RN
SET
BTS
RXU
BP
Set this
parameter
based on
site
configurat
ion.

78
SRAN8.0
Associ
ated
Board
SN
RELA
TEDS
N
SET
BTS
RXU
BP
Set this
parameter
based on
site
configurat
ion.
IF
Offset
IFOF
FSET
SET
BTS
RXU
BP
IfOffs
et
IFO
FFS
ET
ADD
/
MO
D
RRU
Set this
parameter
to 0.
Lvl1
Vswr
Lvl1V
swr
SET
BTS
RXU
BP
VSW
R
alarm
thresh
old
ALM
THR
HLD
ADD
/
MO
D
RRU
VSW
R
alarm
thresh
old
ALM
THR
HLD
AD
D/
MO
D
RR
U
Set this
parameter
to 20.
Seriou
s
VSW
R
Alarm
Postproces
sing
Mode
VSW
RAL
MDIS
POSE
SET
BTS
RXU
BP
VSW
R
alarm
postproce
ssing
switc
h
ALM
PRO
CSW
ADD
/
MO
D
RRU
VSW
R
alarm
postproce
ssing
switc
h
ALM
PRO
CSW
AD
D/
MO
D
RR
U
Set this
parameter
to ON.
Lvl2
Vswr
Lvl2
Vswr
SET
BTS
RXU
BP
VSW
R
alarm
postproce
ssing
thresh
old
ALM
PRO
CTH
RHL
D
ADD
/
MO
D
RRU
VSW
R
alarm
postproce
ssing
thresh
old
ALM
PRO
CTH
RHL
D
AD
D/
MO
D
RR
U
Set this
parameter
to 20.
Anten
na
Tribut
ary 1
Factor
MRR
UATT
ENF
ACT
OR1
SET
BTS
RXU
BP
Atten
uation
ATT
EN
MO
D
RXB
RAN
CH
Rx
Chan
nel
Atten
uation
ATT
EN
MO
D
RX
BR
AN
CH
Set this
parameter
to 0.
Anten
na
Tribut
ary 2
Factor
MRR
UATT
ENF
ACT
OR2
SET
BTS
RXU
BP
Atten
uation
ATT
EN
MO
D
RXB
RAN
CH
Rx
Chan
nel
Atten
uation
ATT
EN
MO
D
RX
BR
AN
CH
Set this
parameter
to 0.

79
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
er Name
Parameter
ID
Setting Notes
Data
Source
RRU
Chain
No.
RCN

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

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

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

PEERPORT.
Network
plan
(negotiatio
n not
required)
Head
Cabinet
No.
HCN
Set the cabinet, subrack, slot, and port numbers to

numbers of the cabinet, subrack, slot, and port
corresponding to the converging party's optical port
that is directly connected to the RRU onsite.
Userdefined

80
SRAN8.0
Paramet
er Name
Parameter
ID
Setting Notes
Data
Source
Head
Subrack
No.
HSRN
Userdefined
Head Slot
No.
HSN
Userdefined
Head
Port No.
HPN
Userdefined
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.
For details about eGBTSs, see 8.4.4 Initial Configuration.
For details about NodeBs, see 9.4.4 Initial Configuration.
For details about eNodeBs, see 10.4.4 Initial Configuration.

81
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.
For details about eGBTSs, see 8.4.5 Activation Observation.
For details about NodeBs, see 9.4.5 Activation Observation.
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

82
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
Alarm ID
Alarm Name
Alarm
Type
Alarm
Severit
y
Event
Type
ALM-26272
Inter-System RF Unit Parameter Settings

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

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

Capability Mismatch
Fault
Major
Hardwar
e

Warning
83
SRAN8.0
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

84

RF Unit and Topology Management (SRAN8.0 - Draft B)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RF Unit and Topology Management (SRAN8.0 - Draft B)

Hochgeladen von

Copyright:

Verfügbare Formate

SRAN8.

RF Unit and Topology Management

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

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

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

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

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

Huawei Proprietary and Confidential

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

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

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

1 About This Document

About This Document

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

BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D)

BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D)

BTS3900C, BTS3900C (Ver.B), and BTS3900C (Ver.C)

1.2 Intended Audience

Need to understand RF Unit and Topology Management

Work with Huawei LTE products

1.3 Change History

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

1 About This Document

Added the Long Term Evolution (LTE) load-sharing ring

Added new RF modules.

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

2.1 Introduction to RF Modules

Radio frequency unit (RFU): applies to macro base stations

2.2 Introduction to RRU/RFU Topologies

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

3.2 RRU/RFU Modules in GSM Mode

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

3.3 RRU/RFU Modules in UMTS Mode

Star topology, chain

Star topology, chain

Star topology, chain

Star topology, chain

Issue Draft B (2013-02-08)

Huawei Proprietary and Confidential

Star topology, chain

Star topology, chain

Star topology, chain

Star topology, chain

Star topology, chain

Star topology, chain