eNodeB Technical Description (V100R003C00 - 06) (PDF) - EN PDF

eNodeB
V100R003C00
Technical Description
Issue 06
Date 2011-11-25
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 06 (2011-11-25) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eNodeB
Technical Description About This Document
About This Document
Purpose
This document provides the LTE-SAE system architecture and the following information about
the eNodeB: basic functions, structures, environment monitoring principles, clock
synchronization modes, operation and maintenance, reliability, topologies, and typical hardware
configurations.
Product Versions
The following table lists the product versions related to this document.
Product Name Version
BTS3900 LTE V100R003C00
BTS3900A LTE V100R003C00
BTS3900L LTE V100R003C00
DBS3900 LTE V100R003C00
DBS3900 LTE TDD V100R003C00
Intended Audience
The intended audiences of this document are:
l Network planning engineers
l Field engineers
l System engineers
Organization
1 Changes in the eNodeB Technical Description
Issue 06 (2011-11-25) Huawei Proprietary and Confidential ii

eNodeB
This chapter describes the changes in the eNodeB Technical Description.
2 LTE-SAE System Architecture
This chapter describes Long Term Evolution-System Architecture Evolution (LTE-SAE) system
architecture, including the position of eNodeBs in the system and the functions of the Network
Elements (NEs) in the network.
3 eNodeB Functions
This chapter describes the functions of eNodeBs. As the radio access equipment in the LTE-
SAE system, eNodeBs perform radio resource management, packet compression and ciphering,
user plane packet routing, MME selection, and message scheduling and transmission.
4 eNodeB Structure
This chapter describes the structure of an eNodeB. eNodeBs are designed based on a distributed
architecture. Each eNodeB consists of two basic types of component: baseband unit BBU3900
and Radio Frequency (RF) unit RRU or RFU.
5 Environment Monitoring Principles
This chapter describes environment monitoring principles for eNodeBs. Environment

monitoring detects the following environmental conditions of an eNodeB: temperature,
humidity, water damage, smoke, unauthorized access, and power distribution faults. To
implement environment monitoring, the eNodeB is equipped with environment monitoring
devices and configured with external environment alarms, including Boolean alarms and an
EMUA alarm.
6 eNodeB Synchronization Modes
This chapter describes the clock synchronization modes of eNodeBs. eNodeBs support
synchronization with the following clocks: GPS/RGPS clock, IEEE1588 V2 clock, Clock over
IP, synchronous Ethernet, 1 PPS+TOD clock, BITS clock, and E1/T1 line clock.
7 Operation and Maintenance of eNodeBs
This chapter describes operation and maintenance of eNodeBs. The operation and maintenance
(OM) system of eNodeBs manages, monitors, and maintains the software, hardware, and
configuration data of the eNodeBs. In addition, the OM system provides various OM modes to
meet requirements.
8 eNodeB Reliability
This chapter describes eNodeB reliability, which includes system reliability, hardware
reliability, and software reliability.
9 eNodeB Topologies
This chapter describes eNodeB topologies on the S1 and CPRI interfaces.
10 Typical Hardware Configurations of an eNodeB
This chapter describes the hardware configurations of an eNodeB.
11 Technical Specifications of Radio Frequency Units
This chapter describes the technical specifications of radio frequency (RF) units, such as the
working mode, frequency band, output power, and antenna capability.
Issue 06 (2011-11-25) Huawei Proprietary and Confidential iii

eNodeB
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
Issue 06 (2011-11-25) Huawei Proprietary and Confidential iv

eNodeB
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Issue 06 (2011-11-25) Huawei Proprietary and Confidential v

eNodeB
Action Description
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Issue 06 (2011-11-25) Huawei Proprietary and Confidential vi

eNodeB
Technical Description Contents
Contents
About This Document.....................................................................................................................ii

1 Changes in the eNodeB Technical Description.......................................................................1
2 LTE-SAE System Architecture....................................................................................................5
3 eNodeB Functions.........................................................................................................................7
4 eNodeB Structure...........................................................................................................................9
4.1 Logical Structure of BBU3900.........................................................................................................................10
4.2 Logical Structure of RRUs/RFUs.....................................................................................................................11
5 Environment Monitoring Principles........................................................................................15

6 eNodeB Synchronization Modes..............................................................................................19
7 Operation and Maintenance of eNodeBs................................................................................21
7.1 OM Modes........................................................................................................................................................22
7.2 OM Functions...................................................................................................................................................23
8 eNodeB Reliability......................................................................................................................26
8.1 System Reliability.............................................................................................................................................27
8.2 Hardware Reliability.........................................................................................................................................28
8.3 Software Reliability..........................................................................................................................................29
9 eNodeB Topologies.....................................................................................................................31
10 Typical Hardware Configurations of an eNodeB...............................................................37
10.1 Typical Hardware Configurations and Subrack Numbers..............................................................................38
10.2 Hardware Configurations of BTS3900 LTE..................................................................................................43
10.3 Hardware Configurations of BTS3900A LTE................................................................................................46
10.4 Hardware Configurations of BTS3900L LTE................................................................................................49
10.5 Hardware Configurations of DBS3900 LTE..................................................................................................52
10.6 Hardware Configurations of DBS3900 LTE TDD.........................................................................................54
11 Technical Specifications of Radio Frequency Units...........................................................55

11.1 Technical Specifications of RFUs..................................................................................................................56
11.1.1 Technical Specifications of the LRFU..................................................................................................56
11.1.2 Technical Specifications of the LRFUe.................................................................................................58
11.1.3 Technical Specifications of the MRFU.................................................................................................59
Issue 06 (2011-11-25) Huawei Proprietary and Confidential vii

eNodeB
Technical Description Contents
11.1.4 Technical Specifications of the MRFUd...............................................................................................61

11.2 Technical Specifications of RRUs..................................................................................................................63
11.2.1 Technical Specifications of the RRU3201............................................................................................63
11.2.10 Technical Specifications of the RRU3929..........................................................................................91
11.2.11 Technical Specifications of the RRU3232..........................................................................................94
Issue 06 (2011-11-25) Huawei Proprietary and Confidential viii

eNodeB
Technical Description 1 Changes in the eNodeB Technical Description
1 Changes in the eNodeB Technical

Description
This chapter describes the changes in the eNodeB Technical Description.
06 (2011-11-25)
This is the sixth official release.
Compared with issue 05 (2011-09-30) of V100R003C00, this issue adds the following new
section:
l 11 Technical Specifications of Radio Frequency Units
Compared with issue 05 (2011-09-30) of V100R003C00, this issue incorporates the changes
described in the following table.
Topic Change Description
4.2 Logical Structure of RRUs/RFUs Added the description of an RRU and an RFU.
9 eNodeB Topologies Added the full name of the LRRU and MRRU.
Compared with issue 05 (2011-09-30) of V100R003C00, this issue does not delete topics.
05 (2011-09-30)
This is the fifth official release.
Compared with issue 04 (2011-06-10) of V100R003C00, this issue does not add topics.
Issue 06 (2011-11-25) Huawei Proprietary and Confidential 1

eNodeB
Topic Change Description
10.1 Typical Hardware Configurations l Modified the hardware quantities of a

and Subrack Numbers frequency division duplex (FDD) eNodeB in
typical configurations.
l Modified the hardware quantities of a time
division duplex (TDD) eNodeB in typical
configurations.
l Distinguished between Ver.B and Ver.C
cabinets.
10.2 Hardware Configurations of Modified the positions of the components of

BTS3900 LTE BTS3900 LTE in typical configurations and the
hardware configuration descriptions.

BTS3900A LTE BTS3900A LTE in typical configurations and the

BTS3900L LTE BTS3900L LTE in typical configurations and the
10.5 Hardware Configurations of Modified the hardware configuration

DBS3900 LTE descriptions of the DBS3900 LTE.
10.6 Hardware Configurations of Modified the hardware configuration

DBS3900 LTE TDD descriptions of the DBS3900 LTE TDD.
04 (2011-06-10)
This is the fourth official release.
Compared with issue 03 (2011-04-15) of V100R003C00, this issue does not incorporate any
change.
03 (2011-04-15)
This is the third official release.
Compared with issue 02 (2011-03-15) of V100R003C00, this issue does not incorporate any
change.

eNodeB
02 (2011-03-15)
This is the second official release.
Change Type Description
10.1 Typical Hardware Hardware quantities of a frequency division duplex (FDD)

Configurations and Subrack eNodeB in typical configurations are modified.
Numbers Hardware quantities of a time division duplex (TDD)
eNodeB in typical configurations are modified.
01 (2011-01-20)
This is the first official release.
Compared with draft A (2010-12-15) of V100R003C00, this issue does not add topics.
Compared with draft A (2010-12-15) of V100R003C00, this issue incorporates the changes
4.2 Logical Structure of RRUs/ l The logical structures of FDD RRUs and RFUs are all
RFUs illustrated in one figure.
l The figure showing the logical structure of TDD RRUs
with 2T2R is deleted.
l The logical structures of TDD RRUs are all illustrated
in one figure.
Compared with draft A (2010-12-15) of V100R003C00, this issue does not delete topics.
Draft A (2010-12-15)
This is the draft.
9 eNodeB Topologies The description of CPRI port rates is added.

eNodeB
4.2 Logical Structure of RRUs/ Descriptions of RRU/RFU logical structures are

RFUs combined into one section.
10.1 Typical Hardware Typical FDD/TDD configurations are updated.

Configurations and Subrack
Numbers

eNodeB
Technical Description 2 LTE-SAE System Architecture
2 LTE-SAE System Architecture
This chapter describes Long Term Evolution-System Architecture Evolution (LTE-SAE) system
architecture, including the position of eNodeBs in the system and the functions of the Network
Elements (NEs) in the network.
eNodeB in the LTE-SAE System

The LTE-SAE system architecture consists of the E-UTRAN and EPC. Figure 2-1 shows the
system architecture.
Figure 2-1 LTE-SAE system architecture
eNodeB: E-UTRAN NodeB E-UTRAN: Evolved EPC: Evolved Packet Core

UTRAN network
MME: Mobility S-GW: Serving Gateway UE: User Equipment

Management Entity
As shown in Figure 2-1, an eNodeB is radio access equipment in the LTE-SAE system. One or
more eNodeBs constitute an E-UTRAN. An eNodeB communicates with a UE, another eNodeB,
or the EPC through the Uu interface, X2 interface, or S1 interface, respectively.

eNodeB
Technical Description 2 LTE-SAE System Architecture
Functions of NEs
The NEs in the LTE-SAE system include eNodeBs, MMEs, and S-GWs. Table 2-1 describes
the functions of the NEs.
Table 2-1 Functions of the NEs in the LTE-SAE system

NE Function
eNodeB l Radio resource management, including radio bearer control, radio

admission control, connection mobility control, and scheduling
l Packet compression and ciphering
l Routing of user plane data towards an S-GW
l MME selection
l Scheduling and transmission of broadcast information and paging
messages
l Measurement and measurement reporting configuration
MME l Paging message distribution

l Security control
l Mobility management in idle mode
l SAE bearer control
l Ciphering and integrity protection of Non-Access Stratum (NAS)
signaling
S-GW l Termination of user plane packets that are generated for paging reason
l Support for user plane handovers caused by UE mobility

eNodeB
Technical Description 3 eNodeB Functions
3 eNodeB Functions
This chapter describes the functions of eNodeBs. As the radio access equipment in the LTE-
SAE system, eNodeBs perform radio resource management, packet compression and ciphering,
user plane packet routing, MME selection, and message scheduling and transmission.
Radio Resource Management

Radio resource management covers radio bearer control, admission control, mobility
management, and dynamic resource allocation.
l Radio bearer control involves setup, maintenance, and release of radio bearers and resource
configuration for radio bearers.
l Admission control accepts or rejects radio bearer setup requests.
l Mobility management involves management of radio resources for UEs in idle mode and
UEs in connected mode.
l Dynamic resource allocation involves allocation and release of radio resources on the
control plane and user plane. The resources include the buffer, processes, and resource
blocks.
Packet Compression and Ciphering

Packet compression and ciphering include the following functions:
l Header compression for downlink packets and header decompression for uplink packets
using compression algorithms
l Encryption and decryption of packets using ciphering algorithms
User Plane Packet Routing

Each eNodeB provides routing of user plane packets towards an S-GW.
MME Selection
MME selection includes the following functions:
l Selection of an MME for a UE during the Attach procedure of the UE

l Selection of an MME for a UE when the UE is in a network

eNodeB
Technical Description 3 eNodeB Functions
l Indirect determination of the route to an MME based on the information provided by the
UE when no routing information is available
Message Scheduling and Transmission

Message scheduling and transmission include the following functions:
l Reception of paging messages and broadcast information from an MME and Operation and
Maintenance (OM) messages from the Operation and Maintenance Center (OMC)
l Transmission of paging messages, broadcast information, and OM messages over the Uu
interface according to specific scheduling rules

eNodeB
Technical Description 4 eNodeB Structure
4 eNodeB Structure
About This Chapter
This chapter describes the structure of an eNodeB. eNodeBs are designed based on a distributed
architecture. Each eNodeB consists of two basic types of component: baseband unit BBU3900
and Radio Frequency (RF) unit RRU or RFU.
4.1 Logical Structure of BBU3900

BBU3900 consists of four logical subsystems: control, transport, baseband, and power and
environment monitoring.
4.2 Logical Structure of RRUs/RFUs
An RRU or RFU contains logical units such as the CPRI module, transceiver (TRX), power
module, power amplifier (PA), low noise amplifier (LNA), filter, and TX/RX switch.

eNodeB
4.1 Logical Structure of BBU3900

BBU3900 consists of four logical subsystems: control, transport, baseband, and power and
environment monitoring.
Figure 4-1 shows the logical structure of BBU3900.
Figure 4-1 Logical structure of BBU3900
Control Subsystem
The functions of the control subsystem are implemented by the LMPT.
This subsystem performs OM functions, processes signaling, and provides the system clock. It
manages the entire eNodeB.
l The OM functions include configuration management, fault management, performance

management, security management, and deployment.
l The signaling involves Packet Data Convergence Protocol (PDCP) signaling on the Uu
interface and Stream Control Transmission Protocol (SCTP) signaling on the S1 and X2
interfaces.
l The system clock can be one of the following types: Global Positioning System (GPS),
Remote Global Positioning System (RGPS), IEEE1588 V2, synchronous Ethernet, or
Clock over IP.
NOTE
To support the RGPS clock, an eNodeB must be equipped with a USCU.
Transport Subsystem
The functions of the transport subsystem are implemented by the LMPT and UTRPs, which
support IP over FE/GE and IP over E1/T1, respectively.
The transport subsystem performs the following functions:

eNodeB
l Provides ports for communication between the eNodeB and the EPC.
l Provides the OM channel between the eNodeB and the Local Maintenance Terminal (LMT)
or M2000.
l Provides ports for communication between the eNodeB and 2G/3G base stations so that
the E1/T1 transmission resources can be shared by the eNodeB and the 2G/3G base stations.
Baseband Subsystem
The functions of the baseband subsystem are implemented by LBBPs.
The baseband subsystem performs the functions for the user plane of the Uu interface, including
uplink and downlink scheduling and data processing. In addition, this subsystem provides the
Common Public Radio Interface (CPRI) for communication between BBU3900 and RF units.
l According to the indication of uplink scheduling result, the uplink processing module
receives data over uplink channels, demodulates and decodes the data, assembles the data
into packets, and then transmits the data to the MME or S-GW through the transport
subsystem. In addition, the module performs measurements on uplink channels.
l According to the indication of downlink scheduling result, the downlink processing module
assembles the data received from the transport subsystem into packets, encodes and
modulates the data, performs Multiple Input Multiple Output (MIMO) and Orthogonal
Frequency Division Multiplex (OFDM) processing, and then transmits the signals over the
CPRI interface.
l The CPRI interface is used for transmission of data between BBU3900 and RF units.
Power and Environment Monitoring Subsystem

The functions of the power and environment monitoring subsystem are implemented by the
UPEU and environment monitoring units.
The power and environment monitoring subsystem performs the following functions:
l Supplies power to BBU3900.

l Monitors power status of BBU3900.
l Provides ports for connections to environment monitoring units and receives and forwards
signals from the environment monitoring units.
4.2 Logical Structure of RRUs/RFUs

An RRU or RFU contains logical units such as the CPRI module, transceiver (TRX), power
module, power amplifier (PA), low noise amplifier (LNA), filter, and TX/RX switch.
An radio frequency unit (RFU) is a radio frequency unit, which is used for a macro eNodeB.
RFUs modulate and demodulate baseband signals and RF signals, process data, amplify power,
and detect standing waves.
An remote radio unit (RRU) is a remote radio unit. One or more RRUs constitute the RF part of
a distributed eNodeB. RRUs modulate and demodulate baseband signals and RF signals, process
data, amplify power, and detect standing waves.
Figure 4-2 shows the logical structure of Frequency Division Duplex (FDD) RRUs and RFUs.

eNodeB
Figure 4-2 Logical structure of FDD RRUs and RFUs
FDD RRUs and the LTE radio frequency unit (LRFU) are designed with 2T2R, and the multi-
mode radio frequency unit (MRFU) is designed with 1T2R.
Figure 4-3 shows the logical structure of Time Division Duplex (TDD) RRUs.
Figure 4-3 Logical structure of TDD RRUs

eNodeB
TDD RRUs are designed with 2T2R,2T4R and 4T4R.
NOTE
In the preceding figures, m denotes the number of PAs, and n denotes the number of LNAs. For example,
in the logical structure of the RRU with 4T4R, m and n are both equal to 4.
CPRI Module
A CPRI module performs the following functions:
l Receives downlink baseband data from BBU3900.

l Transmits uplink baseband data to BBU3900.
l Forwards the data sent from the cascaded RRUs.
TRX
A TRX provides RX and TX channels.
l The TRX performs the following functions at an RX channel:

– Down-converts the received signals to Intermediate Frequency (IF) signals.
– Amplifies the IF signals.
– Performs analog-to-digital conversion.
– Performs digital down-conversion.
– Performs matched filtering.
– Performs automatic gain control.
l The TRX performs the following functions at a TX channel:
– Performs deframing of In-phase or Quadrature (I/Q) signals on the CPRI interface.
– Performs the following functions on the downlink IQ signals: filtering, digital-to-analog
conversion, up-conversion, power amplification, and RF filtering.
– Reports TX power.
– Provides overload protection for PAs.
– Shuts down and opens the TX channel.
– Provides the closed-loop power control function.
– Filters downlink spread spectrum signals.
Power Module
A power module converts the input power into the power required by an RRU or RFU.
PA and LNA
A PA amplifies the low-power RF signals received from the TRX.
An LNA amplifies signals received from antennas.

eNodeB
Filter
A filter multiplexes RX and TX signals over RF channels so that they can share an antenna path.
In addition, the filter performs filtering of RX and TX signals.
TX/RX Switch
A TX/RX switch is used by a TDD RRU for switching between uplink and downlink
transmissions of RF signals.

eNodeB
Technical Description 5 Environment Monitoring Principles
5 Environment Monitoring Principles
This chapter describes environment monitoring principles for eNodeBs. Environment

monitoring detects the following environmental conditions of an eNodeB: temperature,
humidity, water damage, smoke, unauthorized access, and power distribution faults. To
implement environment monitoring, the eNodeB is equipped with environment monitoring
devices and configured with external environment alarms, including Boolean alarms and an
EMUA alarm.
Ports on a UPEU
The Universal Power and Environment Interface Unit (UPEU) is a mandatory board of an
eNodeB. It is configured in slot 18 or 19 in BBU3900. A UPEU provides two EXT-ALM ports
and two MON ports for connections to environment monitoring devices. The ports are described
as follows:
l Each EXT-ALM port supports four Boolean inputs. The two ports are used for connections
to Boolean signal sensors and to dry contacts in a cabinet.
– The EXT-ALM ports can be connected to the environment monitoring ports, including
the alarm port and in-position signal port, on a +24 V DC/DC power subrack in a
BTS3900 cabinet. In this way, PSU status is monitored.
– The EXT-ALM ports can also be used for eight Boolean inputs from sensors, such as
a door status sensor and water sensor. In this solution, data configuration is required.
For example, door status and water damage alarms must be defined for the eNodeB.
l Each MON port supports one RS485 monitoring signal input. The two ports are used for
connections to environment monitoring devices inside and outside a cabinet.
– A MON port can be connected to an environment monitoring device in a cabinet. The
type of the device varies depending on the type of the cabinet.
For example, an APM30H cabinet is installed with a Central Monitoring Unit type A
(CMUA) for centralized monitoring of environment in the APM30H cabinet. The
CMUA provides ports for connections to the door status sensor and smoke sensor and
also provides a port used for three Boolean signal inputs.
Signals of environmental alarms detected by the sensors connected to the CMUA are
processed directly by the LMPT. Therefore, no data configuration is required.
– A MON port can also be connected to an Environment Monitoring Unit type A (EMUA),
which is an environment monitoring device outside an APM30H cabinet, for centralized
monitoring of environment outside the APM30H cabinet.

eNodeB
The EMUA is 1 U high. It can be installed in a 19-inch rack with its depth exceeding
300 mm or in a 19-inch cabinet.
The EMUA provides dedicated ports for connections to sensors such as door status,
smoke, water, temperature, and humidity sensors. In addition, the EMUA provides
extended ports for 32 Boolean and analog signal inputs. If the EMUA is used to monitor
environment outside a cabinet, data configuration is required. If the dedicated ports on
the EMUA are insufficient for environment monitoring, the extended ports can be used
and related data configuration is required.
The alarm monitoring devices connected to the UPEU (such as dry contacts, sensors, and the
EMU) are collectively called peer alarm devices in the subsequent sections.
Connections to EXT-ALM Ports

The type of the cable connected to an EXT-ALM port varies depending on the type of the peer
alarm device.
l If the peer alarm device is a +24 V DC/DC power subrack in a cabinet, two signal cables
are required. For details about how to install the cables, see the BTS3900 Installation
Guide.
– Connect one end of an in-position signal cable for the PSU (DC/DC) to the EXT-ALM0
port and the other end to the in-position signal port on the power subrack.
– Connect one end of a monitoring signal cable for the PSU (DC/DC) to the EXT-ALM1
port and the other end to the alarm port on the power subrack.
l If the peer alarm devices are Boolean signal sensors, add a terminal to one end of a BBU
alarm cable by referring to Table 5-1, connect the terminal to a Boolean signal sensor, and
then connect the RJ45 connector at the other end of the cable to the EXT-ALM0 or EXT-
ALM1 port.
Table 5-1 Pin assignment for wires of the BBU alarm cable
Alarm X1 End X2 End Wire Description Pin

Port Color Assignment
EXT- X1.1 X2.1 Orange and Boolean input 1+ Twisted pair

ALM0 white
X1.2 X2.2 Orange Boolean input 1-

(GND)
X1.3 X2.3 Green and Boolean input 2+ Twisted pair

white
X1.6 X2.6 Green Boolean input 2-

(GND)
X1.5 X2.5 Blue and Boolean input 3+ Twisted pair

white
X1.4 X2.4 Blue Boolean input 3-

(GND)
X1.7 X2.7 Brown and Boolean input 4+ Twisted pair

white

eNodeB
Alarm X1 End X2 End Wire Description Pin

Port Color Assignment
X1.8 X2.8 Brown Boolean input 4-

(GND)
EXT- X1.1 X2.1 Orange and Boolean input 5+ Twisted pair

ALM1 white
X1.2 X2.2 Orange Boolean input 5-

(GND)
X1.3 X2.3 Green and Boolean input 6+ Twisted pair

white
X1.6 X2.6 Green Boolean input 6-

(GND)
X1.5 X2.5 Blue and Boolean input 7+ Twisted pair

white
X1.4 X2.4 Blue Boolean input 7-

(GND)
X1.7 X2.7 Brown and Boolean input 8+ Twisted pair

white
X1.8 X2.8 Brown Boolean input 8-

(GND)
The EXT-ALM0 port is connected to dry contacts 0 to 3, and the EXT-ALM1 port is connected
to dry contacts 4 to 7.
Connections to MON Ports

The UPEU can be connected to either a unit in a cabinet or an EMUA outside a cabinet.
If the UPEU needs to be connected to a unit in a cabinet, cable connections vary depending on
the type of the cabinet.
l In an APM30H cabinet, connect one end of a monitoring signal cable between the CMUA
and the BBU to the MON1 port on the UPEU and the other end of the cable to the COM_IN
port on the CMUA. For details about how to install the cable, see the BBU3900 Installation
Guide.
l In an RFC, connect one end of a monitoring signal cable between the CMUA and the BBU
to the MON0 port on the UPEU and the other end of the cable to the COM_IN port on the
CMUA. For details about how to install the cable, see the BTS3900A Installation Guide.
l In a BTS3900 cabinet, connect one end of a monitoring signal cable for the PMU to the
MON0 port on the UPEU and the other end of the cable to the COM port on the PMU. In
addition, connect one end of a monitoring signal cable for the FAN unit to the MON1 port
on the UPEU and the other end of the cable to the COM IN port on the FAN unit. For details
about how to install the cable, see the BTS3900 Installation Guide.

eNodeB
If the UPEU needs to be connected to an EMUA outside a cabinet, connect one end of an RS485
monitoring signal cable to an unused MON port on the UPEU and the other end of the cable to
a 2-input RS485 port on the EMUA.
NOTE
If both MON ports on the UPEU are in use, configure a Universal Environment Interface Unit (UEIU) in the
eNodeB. Then, connect one end of an RS485 monitoring signal cable to the MON0 port on the UEIU and the
other end of the cable to a 2-input RS485 port on the EMUA.

eNodeB
Technical Description 6 eNodeB Synchronization Modes
6 eNodeB Synchronization Modes
This chapter describes the clock synchronization modes of eNodeBs. eNodeBs support
synchronization with the following clocks: GPS/RGPS clock, IEEE1588 V2 clock, Clock over
IP, synchronous Ethernet, 1 PPS+TOD clock, BITS clock, and E1/T1 line clock.
Synchronization refers to maintenance of the relation that at a valid point of time, the phase error
or frequency error between two or more signals stays within the specified range. There are two
types of synchronization: frequency synchronization and time synchronization.
l Frequency synchronization means that the frequency of a signal is the same as the reference
frequency but the origin of the timescale for the signal does not need to be the same as that
for the reference clock.
l Time synchronization is also referred to as time-of-day synchronization, where the origin
of the timescale for a signal needs to be synchronized with the Universal Time Coordinated
(UTC). Therefore, time synchronization implies synchronization in absolute time. The
UTC time is a universal timing standard, in which the atomic clock is maintained accurately
to ensure time synchronization across the world, with the precision to microseconds.
The subsequent sections describe the preceding reference clocks. For details about clock
synchronization, see the Synchronization Feature Parameter Description.
GPS/RGPS Clock
Synchronization with a GPS or RGPS clock requires that each eNodeB be equipped with a GPS
or RGPS receiver. Using the receiver, the eNodeB receives GPS or RGPS clock signals with the
precision to microseconds. In synchronization with a GPS or RGPS clock, both frequency
synchronization and time synchronization are applicable. To implement synchronization with
an RGPS clock, the eNodeB must be equipped with a USCU.
IEEE1588 V2 Clock
IEEE1588 defines the Precision Time Protocol (PTP), which targets synchronization of clocks
in the Ethernet, with the precision to microseconds. In synchronization with an IEEE1588 V2
clock, both frequency synchronization and time synchronization are applicable.
Clock over IP
Clock over IP is a Huawei proprietary frequency synchronization technology, in which
frequency synchronization packets are transmitted over IP. Clock-over-IP signals are transmitted

eNodeB
Technical Description 6 eNodeB Synchronization Modes
to eNodeBs based on a server/client architecture. In synchronization with a clock over IP, only
frequency synchronization is applicable, with the frequency accuracy lower than ±0.05 ppm.
Synchronous Ethernet
The synchronous Ethernet technology has the basic principles that a downstream node traces
the upstream clock by recovering clock signals from the serial data bit streams received at the
physical layer. In synchronous Ethernet, only frequency synchronization is applicable, with the
frequency accuracy lower than ±0.05 ppm.
1 PPS+TOD Clock
In synchronization with a 1 PPS+TOD clock, the eNodeB obtains 1 PPS signals and Time of
Day (TOD) signals to implement time synchronization. The 1 PPS signals are used for time
synchronization. The TOD signals are used to transmit the time information, type of the reference
clock, and working status of the reference clock.
BITS Clock
In synchronization with a BITS clock, the eNodeB is connected to a BITS synchronization
network through the BITS clock card in the eNodeB to obtain frequency synchronization signals.
After phase lock and frequency division, the main clock unit in the eNodeB converts the
synchronization signals into various types of clock signals required for the eNodeB. To
implement synchronization with a BITS clock, the eNodeB must be equipped with a USCU.
E1/T1 Line Clock

In synchronization with an E1/T1 line clock, the eNodeB obtains frequency synchronization
signals from the physical layer of E1/T1 lines. This clock synchronization mode is applicable
when S1 data is transmitted over an E1/T1 network. To implement synchronization with an E1/
T1 line clock, the eNodeB must be equipped with a UTRP.

eNodeB
Technical Description 7 Operation and Maintenance of eNodeBs
7 Operation and Maintenance of eNodeBs
About This Chapter
This chapter describes operation and maintenance of eNodeBs. The operation and maintenance
(OM) system of eNodeBs manages, monitors, and maintains the software, hardware, and
configuration data of the eNodeBs. In addition, the OM system provides various OM modes to
meet requirements.
7.1 OM Modes
This section describes the operation and maintenance (OM) modes for eNodeBs.
7.2 OM Functions
This section describes the OM functions of eNodeBs, covering configuration management, fault
management, performance management, security management, software management,
deployment management, equipment management, and inventory management.

eNodeB
7.1 OM Modes
This section describes the operation and maintenance (OM) modes for eNodeBs.
eNodeBs support both local and remote operation and maintenance.
l In local OM mode, maintenance personnel use the Local Maintenance Terminal (LMT) to
operate and maintain a single eNodeB.
l In remote OM mode, maintenance personnel use the M2000 or LMT to operate and
maintain eNodeBs in a centralized manner in the operation and maintenance center (OMC).
Figure 7-1 OM system of eNodeBs
As shown in Figure 7-1, the OM system of eNodeBs consists of the following elements:
l LMT: is mainly used to assist eNodeB deployment, identify faults, and rectify faults locally.
l M2000: is Huawei centralized OM system, which consists of the M2000 server and the
M2000 client. M2000 can be connected to eNodeBs of different models and versions
through an OM network for remote centralized operation and maintenance. This mode is
recommended when eNodeBs communicate with M2000 properly.
l eNodeB: is the object of the operation and maintenance.
The required OM software, as described in Table 7-1, must be installed on maintenance
terminals for operation and maintenance of eNodeBs.

eNodeB
Table 7-1 OM software
Software Function
iManager M2000 l Topology management

l Fault management
l Configuration management
l Performance management
l Security management
l Software and hardware management
LMT l Man-machine language (MML)

command execution
l Alarm management
l Batch processing
l Tracing management
l Performance monitoring
l Self-check management
l Software management
l Comprehensive maintenance and
commissioning
7.2 OM Functions
This section describes the OM functions of eNodeBs, covering configuration management, fault
management, performance management, security management, software management,
deployment management, equipment management, and inventory management.
Configuration Management
Configuration management includes data configuration, query, export, backup and restore, and
configuration synchronization with M2000.
The data configuration is based on Managed Objects (MOs) of the following categories: device,
transport, and service. These categories are independent of each other. Generally, modifications
of the service configuration do not require modifications of the device configuration, and
modifications of the device configuration do not require modifications of the service
configuration either.
Fault Management
Fault management includes fault detection, fault isolation and self-healing, alarm reporting, and
alarm correlation. The faults might be related to hardware, environment, software, transmission,
cells, and different types of services in cells.
l Fault isolation and self-healing bring the following advantages: (1) prevents a fault in some
part of an eNodeB from affecting the entire eNodeB; (2) re-establishes a cell of lower
specifications to minimize the impact of the fault on services.

eNodeB
l The alarm correlation function enables the system to report only the alarm indicating the
root fault and the ultimate impact on services though there are chains of problems caused
by the root fault.
Performance Management
Performance management includes the periodic control on eNodeB performance measurement
and the collection, storage, and reporting of performance statistics.
eNodeBs collect performance statistics every 15 or 60 minutes. If communication between an

eNodeB and the mobile Element Management System (EMS) fails, the eNodeB can store a
maximum of three days of performance measurement results. The performance measurement
covers eNodeB-level and cell-level performance, neighboring cells, transmission, standard
interfaces, and the device usage.
eNodeBs support real-time monitoring of Key Performance Indicators (KPIs) at intervals of one
minute, which helps detect and identify faults in time.
Security Management
Security management provides the eNodeB authentication and access control functions, which
include user account management, rights management, login management, identity
authentication, and operation authentication.
In addition, security management involves security control on the channels between eNodeBs
and an EMS. The channels support encryption using Secure Socket Layer (SSL) or IP Security
(IPSec).
Security management provides network- and user-level security service. It provides the
following functions:
l Encryption: encryption of important user information
l Authentication: management of user accounts and authentication of users
l Access control: control of operation access
l Security protocol: support for SSL and IPSec
Software Management
Software management includes software version management, software version upgrade, and
patch management.
l Software version management involves query, backup, and restore of software versions.
l Software version upgrade can be performed on a batch of eNodeBs remotely. With the one-
click upgrade wizard provided by M2000, users can perform health checks before and after
the upgrade and back up, download, and activate the software. During this process, users
can check the upgrade status and results. eNodeBs support automatic updates of
configurations during upgrades, and users only need to follow the instructions in the
upgrade wizard. In addition, eNodeBs support rapid version rollback by running a single
command, reducing the impact of upgrade failures on the system.
l Patch management includes query, download, loading, activation, deactivation, rollback,
and removal of patches. Installing patches does not affect system services.

eNodeB
Deployment Management
The eNodeB deployment solutions include board-ready transportation, automatic discovery of
eNodeBs, initial configuration by using a USB disk, and remote deployment. These solutions
greatly reduce the workload and efforts of field installation personnel. No computer is required.
The personnel only need to install the hardware.
l By using automatic discovery of eNodeBs, users do not need to set the IP addresses of the
eNodeBs and EMS.
l Users can download software and data of an eNodeB from a USB disk, thereby saving time
especially when the bandwidth of transmission between the eNodeB and the EMS is
insufficient.
l During remote deployment, software commissioning is performed in the Operation and
Maintenance Center (OMC) rather than on site. Customers can perform acceptance tests
on the eNodeB deployment in the OMC.
Equipment Management
Equipment management includes data configuration, status management, and fault detection
and handling for all the devices in an eNodeB. On the device panel, users can view the device
status and perform blocking, reset, and switchover.
Inventory Management
Inventory management includes collection and reporting of the inventory information about
eNodeBs. With inventory management, users can manage network equipment (NE) assets in the
OMC in a centralized manner.

eNodeB
Technical Description 8 eNodeB Reliability
8 eNodeB Reliability
About This Chapter
This chapter describes eNodeB reliability, which includes system reliability, hardware
reliability, and software reliability.
8.1 System Reliability

System reliability is ensured by using the intra-board baseband resource pool, LMPT cold
redundancy, and RRU channel cross-connection under MIMO.
8.2 Hardware Reliability
Hardware reliability is ensured by the anti-misinsertion design of boards, overtemperature
protection, reliable power supply, and surge protection design.
8.3 Software Reliability
Software reliability is ensured by the redundancy of important files and data and the powerful
error tolerance of software.

eNodeB
8.1 System Reliability

System reliability is ensured by using the intra-board baseband resource pool, LMPT cold
redundancy, and RRU channel cross-connection under MIMO.
Intra-Board Baseband Resource Pool

Intra-board baseband resource pool is designed to enable dynamic allocation of baseband
resources based on the specifications and load status of an LBBP. This increases the usage of
baseband resources and improves system reliability.
The functions of the baseband resource pool are as follows:
l If all resources of an LBBP are used to serve a single cell, users are allocated different
baseband resources in a fair manner based on the baseband load on the LBBP.
l Full redundancy of intra- or inter-cell baseband resources is achieved. When some baseband
resources are unavailable, the associated services can be diverted to other available
baseband resources. In this way, the services in the cell can be restored.
LMPT Cold Redundancy

Each eNodeB supports LMPT cold redundancy, in which two LMPTs in BBU3900 work in
active/standby mode. When the active LMPT experiences a major fault or a user runs the
switchover command, an active/standby switchover is performed automatically or manually,
respectively.
LMPT cold redundancy prevents system collapse caused by LMPT failures and therefore ensures
system reliability of eNodeBs. An active/standby switchover, however, interrupts eNodeB
services for less than three minutes.
RRU Channel Cross-Connection Under MIMO

RRU channel cross-connection under MIMO is implemented by cross-connections of RF
jumpers between RRUs/RFUs and antennas and data switching in the connected LBBP. This
function improves reliability of the entire network with no requirement for additional hardware.
It partially achieves self-healing, preventing permanent failures to provide services in cells
caused by faults in a single RRU or RFU.
This function is applicable in scenarios where three sectors are configured on three 2T2R RF
units. When an RRU or RFU serving a sector fails, the sector is degraded from MIMO to Single
Input Single Output (SISO), preventing total service failure in the entire sector. At the same
time, another sector using the RRU or RFU is also degraded from MIMO to SISO. After the
fault of the RRU or RFU is rectified, the sectors change from SISO back to MIMO automatically.
In this way, self-healing is achieved.
Figure 8-1 shows the cable connections between RRUs and antennas and data streams. The
cable connections and service data flows for RFUs are the same as those for RRUs.

eNodeB
Figure 8-1 Cross-connections between RRUs and antennas under MIMO and data streams
l In the uplink as shown in Figure 8-1, the CPRI ports receive data from RRU 0 and RRU
1. After user plane data of sector 0 is separated from data of the other sectors, the user plane
data of sector 0 is sent to the module in the LBBP that processes data of sector 0.
l In the downlink as shown in Figure 8-1, user plane data of sector 0 in the LBBP is sent
through different CPRI ports to RRU 0 and RRU 1.
l If RRU 0 shown in Figure 8-1 is faulty, user plane data of sector 0 can be exchanged
through RRU 1.
8.2 Hardware Reliability

Hardware reliability is ensured by the anti-misinsertion design of boards, overtemperature
protection, reliable power supply, and surge protection design.
Anti-misinsertion Design of Boards

When a board of one type is inserted into a slot for another type of board, the board cannot
connect to the backplane. This protects the equipment from damage.

eNodeB
Overtemperature Protection
When the temperature near the PA in an RF unit of an eNodeB is too high, the eNodeB generates
overtemperature alarms and immediately shuts down the PA. This protects PA from damage
caused by overtemperature.
Reliable Power Supply

The reliable power supply is achieved using the following techniques:
l Support for wide-range voltages and surge protection
l Power failure protection for programs and data
l Protection of power supply against overvoltage, overcurrent, and reverse connection of
positive and negative poles on boards
Surge Protection Design

Surge protection is applied to AC and DC power ports and various input and output signal ports
such as E1/T1 and FE/GE ports of eNodeBs.
8.3 Software Reliability

Software reliability is ensured by the redundancy of important files and data and the powerful
error tolerance of software.
Redundancy
eNodeBs provide the redundancy function for important files and data, such as software versions
and data configuration files, to ensure proper operation of the eNodeBs when errors occur in
these files and data.
l Redundancy of software versions: An eNodeB stores software versions, including the
BootROM version, in different areas to provide redundancy. If the active version is
abnormal, the eNodeB switches to the backup version.
l Redundancy of data configuration files: An eNodeB stores data configuration files in
different areas to provide redundancy. If the current file is damaged, the eNodeB can
continue working properly by loading the backup file.
l Redundancy of boards: Two boards of the same type can work in active/standby mode.
When the active board fails or is faulty, the standby board takes over, ensuring proper
operation of the eNodeB.
Error Tolerance
When software errors occur, eNodeBs will not collapse, because of their self-healing capability.
The software error tolerance covers the following aspects:
l Scheduled check of key resources: eNodeBs perform occupancy check on software
resources. If resource hang-up occurs in an eNodeB due to software errors, the eNodeB
can release the unavailable resources in time and export logs and alarms.
l Task monitoring: When software is running, eNodeBs monitor tasks for all types of internal
software errors and some hardware faults, if any. When an error occurs in a task, an alarm
is reported and self-healing measures are taken to restore the task.

eNodeB
l Data check: eNodeBs perform scheduled or event-triggered data consistency checks and
restore data consistency selectively or preferentially. In addition, eNodeBs generate related
logs and alarms.
l Watchdog: When a software error occurs in an eNodeB, the eNodeB detects the error
through the software and hardware watchdogs and automatically resets.

eNodeB
Technical Description 9 eNodeB Topologies
9 eNodeB Topologies
This chapter describes eNodeB topologies on the S1 and CPRI interfaces.
Topologies on the S1 Interface

eNodeBs support the star, chain, and tree topologies on the S1 interface. Figure 9-1 shows the
topologies.

eNodeB
Figure 9-1 Topologies on the S1 interface
Table 9-1 describes the characteristics of the three topologies.

eNodeB
Table 9-1 Topologies on the S1 interface

Topol Advantage Disadvantage
ogy
Star l Each eNodeB is connected directly to Compared with the other two topologies,
topolo an MME through a transport the star topology requires more
gy network. Therefore, this simple transmission resources.
topology features easy engineering,
maintenance, and capacity
expansion.
l Each eNodeB exchanges data with
the MME directly. Signals travel
through only a few nodes, and
therefore network reliability is high.
Chain The costs of transmission equipment, l Signals travel through many nodes,
topolo engineering, and transport line lease are and therefore network reliability is
gy relatively low. low.
l Each lower-level eNodeB occupies
some transmission bandwidth of its
upper-level eNodeB. Reliability of
the upper-level eNodeB affects
operation of the lower-level eNodeB.
Tree The costs of transmission equipment, l Signals travel through many nodes,
topolo engineering, and transport line lease are and therefore network reliability is
gy relatively low. low.
l Each lower-level eNodeB occupies
some transmission bandwidth of its
upper-level eNodeB. Reliability of
the upper-level eNodeB affects
operation of the lower-level eNodeB.
Topologies on the CPRI Interface

On the CPRI interfaces between BBU3900 and LTE remote radio units (LRRUs), the star, chain,
and ring topologies are applicable. The star or chain topology is recommended. On the CPRI
interfaces between BBU3900 and LRFUs/multi-mode remote radio units (MRRUs)/MRFUs,
only the star topology is applicable.
NOTE
l The CPRI rate is adaptive between 2.5 Gbit/s and 4.9 Gbit/s.
l The distance between BBU3900 and the farthest RRU in a CPRI chain cannot exceed 20 km.
Figure 9-2 shows the topologies.

eNodeB
Figure 9-2 Topologies on the CPRI interface
Table 9-2 describes the characteristics of the three topologies.

eNodeB
Table 9-2 Topologies on the CPRI interface

To Advantage Disadvantage Remarks
pol
og
y
Sta l This topology features Compared with the other -

r high reliability. Faults two topologies, the star
top in an RRU/RFU or topology requires more
olo optical cable affect one transmission resources.
gy sector at most.
l This simple topology
facilitates installation
and maintenance.
Ch This topology requires l Limitations are applied l Cascading between

ain relatively low costs of to the number of levels LRFU and LRRU is not
top transmission equipment. in a chain and the supported.
olo distance between units l An LRRU chain can
gy in a chain. contain a maximum of
l LRRUs in different three LRRUs.
duplex modes cannot (Cascading is
be cascaded in a chain. applicable only when
l Any fault on the the channel bandwidth
forwarding link of an is 1.4 MHz, 3 MHz, or
upper-level LRRU 5 MHz.)
affects the operations of l A chain supports only
its lower-level LRRUs. one rate at a time,
because interconnected
CPRI ports on two
LRRUs in a chain must
work at the same rate.

eNodeB
To Advantage Disadvantage Remarks

pol
og
y
Rin The ring topology provides l Limitations are applied The ring topology is a
g high transmission to the number of levels redundancy type of the
top reliability. in a ring and the chain topology.
olo distance between units
gy in a ring.
l LRRUs in different
duplex modes cannot
be cascaded in a ring.
l Any fault on the
forwarding link of an
upper-level LRRU
affects the operations of
its lower-level LRRUs.
If a fault occurs,
services carried on the
lower-level LRRUs
restore in reverse
direction of the ring.
The maximum
interruption duration is
20 minutes.

eNodeB
Technical Description 10 Typical Hardware Configurations of an eNodeB
10 Typical Hardware Configurations of an

eNodeB
About This Chapter
This chapter describes the hardware configurations of an eNodeB.
10.1 Typical Hardware Configurations and Subrack Numbers

This section describes the typical hardware configurations and the mapping between hardware
components and their subrack numbers.
10.2 Hardware Configurations of BTS3900 LTE
This section describes the positions and types of the components of BTS3900 LTE in typical
configurations.
10.3 Hardware Configurations of BTS3900A LTE
This section describes the positions and types of the components of BTS3900A LTE in typical
configurations.
10.4 Hardware Configurations of BTS3900L LTE
This section describes the positions and types of the components of BTS3900L LTE in typical
configurations.
10.5 Hardware Configurations of DBS3900 LTE
This section describes the hardware configurations of DBS3900 LTE in typical cases.
10.6 Hardware Configurations of DBS3900 LTE TDD
This section describes the positions and types of the components of DBS3900 LTE TDD in

eNodeB
10.1 Typical Hardware Configurations and Subrack

Numbers
This section describes the typical hardware configurations and the mapping between hardware
components and their subrack numbers.
Hardware Quantities in Typical Configurations

Table 10-1 lists the number of components of an FDD eNodeB in typical configurations. Table
10-2 lists the number of components of a TDD eNodeB in typical configurations.
Table 10-1 Hardware quantities of an FDD eNodeB in typical configurations

Configuration Number of Number of Number of
LMPTs LBBPcs RRUs/RFUs
3 x 5 MHz/10 MHz, 2 x 2 MIMO 1 1 6(MRFU)
3 x 15 MHz/20 MHz, 2 x 2 MIMO 1 1 3

(6, if MRFUs are
required)
6 x 5 MHz/10 MHz, 2 x 2 MIMO 1 1 6
6 x 5 MHz/10 MHz, 2 x 2 MIMO 1 2 12(MRFU)
3 x 5 MHz/10 MHz, 4 x 2 MIMO 1 1 6
3 x 15 MHz/20 MHz, 4 x 2 MIMO 1 3 6
Table 10-2 Hardware quantities of a TDD eNodeB in typical configurations

Configuration Number of Number of Number of RRUs
LMPTs LBBPcs
3 x 10 MHz, 2 x 2 MIMO 1 1 3
3 x 10 MHz, 4 x 2 MIMO 1 1 3
3 x 20 MHz, 2 x 2 MIMO 1 1 3
3 x 20 MHz, 4 x 2 MIMO 1 3 3
3 x 20 MHz, 4T4R, beamforming 1 3 3

eNodeB
NOTE
A x B MHz indicates that an eNodeB is configured with A cells of B MHz bandwidth. xTyR indicates that
each cell uses x transmit (TX) channels and y receive (RX) channels. m x n MIMO indicates that each cell
uses m transmit (TX) channels and n receive (RX) channels. For example, "3 x 10 MHz, 4T4R" indicates
that the eNodeB is configured with three cells of 10 MHz bandwidth, and each cell uses two TX channels
and two RX channels.
Definitions of Subrack Numbers

Subrack numbers are defined for components of an eNodeB for operation, administration, and
maintenance.
l The Fan Monitoring Unit (FMU) shown in the following figures is the name of the FAN
unit used in operation and maintenance.
l The Temperature Control Unit (TCU) shown in the following figures is the name of the
Central Monitoring Unit type A (CMUA) used in operation and maintenance.
l The subrack number of the BBU3900 components is the same as the subrack number of
BBU3900.
Table 10-3 lists the mapping between eNodeB models and cabinets. Table 10-4 shows the
subrack numbers of cabinets.
Table 10-3 Mapping between eNodeB models and cabinets

eNodeB Model Cabinet Used
BTS3900 LTE BTS3900 (Ver.B), BTS3900 (Ver.C) cabinet
BTS3900L LTE BTS3900L (Ver.B), BTS3900L (Ver.C) cabinet
BTS3900A LTE APM30H (Ver.B), APM30H (Ver.C), RFC (Ver.B), RFC (Ver.C),
TMC11H (Ver.B), TMC11H (Ver.C), IBBS200D or IBBS200T
(Ver.B), IBBS200D or IBBS200T (Ver.C) cabinets
DBS3900 LTE APM30H (Ver.B), APM30H (Ver.C), TMC11H (Ver.B), TMC11H

(Ver.C), IBBS200D or IBBS200T (Ver.B), IBBS200D or IBBS200T
(Ver.C) cabinets
DBS3900 LTE APM30H (Ver.B), APM30H (Ver.C), TMC11H (Ver.B), TMC11H

TDD (Ver.C), IBBS200D or IBBS200T (Ver.B), IBBS200D or IBBS200T
(Ver.C) cabinets

eNodeB
Table 10-4 Subrack numbers

Cabinet Subrack Number
BTS3900 (Ver.B)
and BTS3900
(Ver.C) cabinet

eNodeB
BTS3900L (Ver.B)
and BTS3900L
(Ver.C) cabinet

eNodeB
APM30H (Ver.B)
and APM30H
(Ver.C) cabinet
RFC (Ver.B) and

RFC (Ver.C)

eNodeB
TMC11H (Ver.B)
and TMC11H
(Ver.C) cabinet
IBBS200D/
IBBS200T (Ver.B)
and IBBS200D/
IBBS200T (Ver.C)
cabinet
10.2 Hardware Configurations of BTS3900 LTE

This section describes the positions and types of the components of BTS3900 LTE in typical
configurations.
Installation Positions
Figure 10-1 shows the positions of the components of BTS3900 LTE in typical configurations.

eNodeB
Figure 10-1 Positions of the components of BTS3900 LTE in typical configurations
3×5MHz/10MHz 4×2 MIMO 3×15MHz/20MHz 4×2 MIMO

LMPT
LBBPc
LRFU
Hardware Configurations
Figure 10-2, Figure 10-3, and Figure 10-4 show the hardware configurations of BTS3900 LTE
in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2
MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.

eNodeB
Figure 10-2 Hardware configuration of BTS3900 LTE in the case of 3 x 15 MHz/20 MHz, 2 x
2 MIMO
NOTE
An alternative way to provide the 3 x 15 MHz/20 MHz and 2 x 2 MIMO configuration is to use six MRFUs.
2 MIMO

eNodeB
2 MIMO
10.3 Hardware Configurations of BTS3900A LTE

This section describes the positions and types of the components of BTS3900A LTE in typical
configurations.
Figure 10-5 shows the positions of the components of BTS3900A LTE in typical configurations.

eNodeB
Figure 10-5 Positions of the components of BTS3900A LTE in typical configurations
LMPT
LBBPc
LRFU
Figure 10-6, Figure 10-7, and Figure 10-8 show the hardware configurations of BTS3900A
LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2
x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.

eNodeB
Figure 10-6 Hardware configuration of BTS3900A LTE in the case of 3 x 15 MHz/20 MHz, 2
x 2 MIMO
NOTE
Figure 10-7 Hardware configuration of BTS3900A LTE in the case of 6 x 5 MHz/10 MHz, 2 x
2 MIMO

eNodeB
Figure 10-8 Hardware configuration of BTS3900A LTE in the case of 3 x 5 MHz/10 MHz, 4 x
2 MIMO
10.4 Hardware Configurations of BTS3900L LTE

This section describes the positions and types of the components of BTS3900L LTE in typical
configurations.
Figure 10-9 shows the positions of the components of BTS3900L LTE in typical configurations.

eNodeB
Figure 10-9 Positions of the components of BTS3900L LTE in typical configurations
3×5MHz/10MHz 4×2 MIMO 3×15MHz/20MHz 4×2 MIMO 6×5MHz/10MHz 2×2 MIMO
LMPT
LBBPc
LRFU
MRFU

eNodeB
Figure 10-10, Figure 10-11, and Figure 10-12 show the hardware configurations of BTS3900L
Figure 10-10 Hardware configuration of BTS3900L LTE in the case of 3 x 15 MHz/20 MHz,
2 x 2 MIMO
NOTE
Figure 10-11 Hardware configuration of BTS3900L LTE in the case of 6 x 5 MHz/10 MHz, 2
x 2 MIMO

eNodeB
Figure 10-12 Hardware configuration of BTS3900L LTE in the case of 3 x 5 MHz/10 MHz, 4
x 2 MIMO
10.5 Hardware Configurations of DBS3900 LTE

This section describes the hardware configurations of DBS3900 LTE in typical cases.
Figure 10-13, Figure 10-14, and Figure 10-15 show the hardware configurations of DBS3900
Figure 10-13 Hardware configuration of DBS3900 LTE in the case of 3 x 15 MHz/20 MHz, 2
x 2 MIMO

eNodeB
Figure 10-14 Hardware configuration of DBS3900 LTE in the case of 6 x 5 MHz/10 MHz, 2 x
2 MIMO
Figure 10-15 Hardware configuration of DBS3900 LTE in the case of 3 x 5 MHz/10 MHz, 4 x
2 MIMO

eNodeB
10.6 Hardware Configurations of DBS3900 LTE TDD

This section describes the positions and types of the components of DBS3900 LTE TDD in
Figure 10-16 and Figure 10-17 show the hardware configurations of DBS3900 LTE TDD in
the following cases: (1) 3 x 20 MHz, 2 x 2 MIMO; (2) 3 x 20 MHz, 4 x 2 MIMO.
Figure 10-16 Hardware configuration of DBS3900 LTE TDD in the case of 3 x 20 MHz, 2 x 2
MIMO
Figure 10-17 Hardware configuration of DBS3900 LTE TDD in the case of 3 x 20 MHz, 4 x 2
MIMO

eNodeB
Technical Description 11 Technical Specifications of Radio Frequency Units
11 Technical Specifications of Radio

Frequency Units
About This Chapter
This chapter describes the technical specifications of radio frequency (RF) units, such as the
working mode, frequency band, output power, and antenna capability.
11.1 Technical Specifications of RFUs

An RFU is a radio frequency unit. One or more RFUs constitute the radio frequency (RF) part
of a macro eNodeB. RFUs can be installed in an indoor cabinet or a protective outdoor cabinet.
This chapter describes the technical specifications of RFUs, such as the working mode,
frequency band, output power, and antenna capability.
11.2 Technical Specifications of RRUs
An RRU is a remote radio unit. One or more RRUs constitute the radio frequency (RF) part of
a distributed eNodeB. RRUs can be installed on a pole, wall, or stand. They can also be installed
close to antennas to shorten the feeder length, reduce feeder loss, and improve system coverage.
This chapter describes the technical specifications of RRUs, such as the working mode,

eNodeB
11.1 Technical Specifications of RFUs

An RFU is a radio frequency unit. One or more RFUs constitute the radio frequency (RF) part
of a macro eNodeB. RFUs can be installed in an indoor cabinet or a protective outdoor cabinet.
This chapter describes the technical specifications of RFUs, such as the working mode,
11.1.1 Technical Specifications of the LRFU

This section describes the technical specifications of the LRFU.
Working Mode and Frequency Band

Table 11-1 describes the working mode and frequency bands of the LRFU.
Table 11-1 Working mode and frequency bands of the LRFU

Type Worki Frequency Band RX Band (MHz) TX Band (MHz)
ng (MHz)
Mode
LRFU LTE AWS (band 4) 1710 to 1755 2110 to 2155

FDD
2600 (band 7) Band C: 2500 to 2520 Band C: 2620 to 2640
Band D: 2510 to 2560 Band D: 2630 to 2680
Band E: 2550 to 2570 Band E: 2670 to 2690
RF Specifications
Table 11-2 describes the RF specifications of the LRFU.
Table 11-2 RF specifications of the LRFU

Type RX and TX Capacity Output Power
Channels
LRFU 2T2R The bandwidth of each carrier can 2 x 40 W

be:
l 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, or 20 MHz in the
AWS band
l 5 MHz, 10 MHz, 15 MHz, or 20
MHz in the 2600 MHz band
NOTE
A x B W indicates that the eNodeB uses A transmit (TX) channels and the output power of each channel is B W.

eNodeB
Surge Protection Specifications

Table 11-3 describes the surge protection specifications for the ports on the LRFU.
NOTE
l Unless otherwise specified, the surge protection specifications are based on the surge waveform of 8/20
μs.
l All the items of discharge current, unless otherwise specified as the maximum discharge current, refer to
those of the nominal discharge current.
Table 11-3 Surge protection specifications for the ports on the LRFU
Port Applicatio Surge Protection Mode Specification

n Scenario
DC power All Surge Differential 2 kV (1.2/50 μs)

supply mode
socket
Common 4 kV (1.2/50 μs)
mode
Surge Differential 10 kA
current mode
Common 20 kA
mode
Antenna port All Surge Differential 8 kA

current mode
Common 40 kA
mode
Monitoring All Surge Differential 3 kA

port current mode
Common 5 kA
mode
Antenna Capability
Table 11-4 describes the antenna capability of the LRFU.
Table 11-4 Antenna capability of the LRFU
Type TMA Support Capability RET Antenna Support

Capability
LRFU TMA supported AISG2.0-complied RET

antennas supported

eNodeB
NOTE
If an RRU supports RET antennas, the feeding voltage and feeding current are 12 V and 2.3 A, respectively.
11.1.2 Technical Specifications of the LRFUe

This section describes the technical specifications of the LRFUe.

Table 11-5 describes the working mode and frequency bands of the LRFUe.
Table 11-5 Working mode and frequency bands of the LRFUe

ng (MHz)
Mode
LRFUe LTE DD 800MHz (band 832 to 862 791 to 821

FDD 20)
RF Specifications
Table 11-6 describes the RF specifications of the LRFUe.
Table 11-6 RF specifications of the LRFUe

Channels
LRFUe 2T2R The bandwidth of each carrier can 2 x 60 W

be 5 MHz, 10 MHz, 15 MHz, or 20
MHz.
NOTE

Table 11-7 describes the surge protection specifications for the ports on the LRFUe.
NOTE
μs.

eNodeB
Table 11-7 Surge protection specifications for the ports on the LRFUe

n Scenario

supply mode
socket
mode
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

port current mode
Common 5 kA
mode
Antenna Capability
Table 11-8 describes the antenna capability of the LRFUe.
Table 11-8 Antenna capability of the LRFUe

Capability
LRFUe TMA supported AISG2.0-complied RET

antennas supported
NOTE
11.1.3 Technical Specifications of the MRFU

This section describes the technical specifications of the MRFU.

Table 11-9 describes the working mode and frequency bands of the MRFU.

eNodeB
Table 11-9 Working mode and frequency bands of the MRFU

ng (MHz)
Mode
MRFU LTE 900 (band 8) 880 to 915 925 to 960

FDD
1800 (band 3) 1710 to 1770 1805 to 1865
1725 to 1785 1820 to 1880
RF Specifications
Table 11-10 describes the RF specifications of the MRFU.
Table 11-10 RF specifications of the MRFU

Channels
MRFU 1T2R The bandwidth of each carrier can 1 x 60 W

be 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, or 20 MHz.
NOTE

Table 11-11 describes the surge protection specifications for the ports on the MRFU.
NOTE
μs.
Table 11-11 Surge protection specifications for the ports on the MRFU
n Scenario

supply mode
socket
mode
current mode

eNodeB

n Scenario
Common 20 kA
mode

current mode
Common 40 kA
mode

port current mode
Common 5 kA
mode
Antenna Capability
Table 11-12 describes the antenna capability of the MRFU.
Table 11-12 Antenna capability of the MRFU

Capability
MRFU TMA supported AISG2.0-complied RET

antennas supported
NOTE
11.1.4 Technical Specifications of the MRFUd

This section describes the technical specifications of the MRFUd.

Table 11-13 describes the working mode and frequency bands of the MRFUd.
Table 11-13 Working mode and frequency bands of the MRFUd

ng (MHz)
Mode
MRFUd LTE 900 (band 8) 880 to 915 925 to 960

FDD
900 (P25) 890 to 915 935 to 960

eNodeB

ng (MHz)
Mode
1800 (band 3) 1710 to 1785 1805 to 1880
RF Specifications
Table 11-14 describes the RF specifications of the MRFUd.
Table 11-14 RF specifications of the MRFUd

Channels
MRFUd 2T2R The bandwidth of each carrier can l Two carriers: 2 x

be 1.4 MHz, 3 MHz, 5 MHz, 10 80 W
MHz, 15 MHz, or 20 MHz. l One carrier: 2 x
60 W
NOTE

Table 11-15 describes the surge protection specifications for the ports on the MRFUd.
NOTE
μs.
Table 11-15 Surge protection specifications for the ports on the MRFUd

n Scenario

supply mode
socket
mode
current mode
Common 20 kA
mode

eNodeB

n Scenario

current mode
Common 40 kA
mode

port current mode
Common 5 kA
mode
Antenna Capability
Table 11-16 describes the antenna capability of the MRFUd.
Table 11-16 Antenna capability of the MRFUd

Capability
MRFUd TMA supported AISG2.0-complied RET

antennas supported
NOTE
11.2 Technical Specifications of RRUs

An RRU is a remote radio unit. One or more RRUs constitute the radio frequency (RF) part of
a distributed eNodeB. RRUs can be installed on a pole, wall, or stand. They can also be installed
close to antennas to shorten the feeder length, reduce feeder loss, and improve system coverage.
This chapter describes the technical specifications of RRUs, such as the working mode,
11.2.1 Technical Specifications of the RRU3201

This section describes the technical specifications of the RRU3201.

Table 11-17 describes the working mode and frequency bands of the RRU3201.

eNodeB
Table 11-17 Working mode and frequency bands of the RRU3201
Type Workin Frequency RX Band (MHz) TX Band (MHz)

g Mode Band (MHz)
RRU3201 LTE 700 (band 13) 777 to 787 746 to 756

FDD
2600 (band 7) Band C: 2500 to 2520 Band C: 2620 to 2640
Band D: 2510 to 2560 Band D: 2630 to 2680
Band E: 2550 to 2570 Band E: 2670 to 2690
RF Specifications
Table 11-18 describes the RF specifications of the RRU3201.
Table 11-18 RF specifications of the RRU3201

Channels
RRU3201 2T2R The bandwidth of each carrier can 2 x 40 W

be:
l 5 MHz or 10 MHz in the 700
MHz band
l 5 MHz, 10 MHz, 15 MHz, or 20
MHz in the 2600 MHz band
NOTE
Engineering Specifications
Table 11-19 describes the physical specifications of the RRU3201.
Table 11-19 Physical specifications of the RRU3201
Type Input Power Dimensions (Height x Weight (kg)

Width x Depth)
RRU3201 –48 V DC; voltage l 480 mm x 270 mm x 140 l ≤17.5 kg (without

range: –36 V DC to – mm (18 L without the the housing)
57 V DC housing) l ≤19 kg (with the
l 485 mm x 285 mm x 170 housing)
mm (23.5 L with the
housing)

eNodeB
Table 11-20 describes the environmental specifications of the RRU3201.
Table 11-20 Environmental specifications of the RRU3201
Type Temperature Relative Absolute Atmospheri

Humidity Humidity c Pressure
RRU3201 l –40ºC to +50ºC 5% RH to 100% 1 g/m3 to 30 g/ 70 kPa to 106

(with solar radiation RH m3 kPa
of 1120 W/m2)
l –40ºC to +55ºC
(without solar
radiation)
Table 11-21 describes the compliance standards for the RRU3201.
Table 11-21 Compliance standards of the RRU3201
Type Operating Anti-Seismic Ingress

Environment Performance Protection (IP)
Rating
RRU3201 Compliance standards: NEBS GR63 zone4 IP65

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
Table 11-22 describes the surge protection specifications for the ports on the RRU3201.
NOTE
μs.
Table 11-22 Surge protection specifications for the ports on the RRU3201

n Scenario

supply mode
socket

eNodeB

n Scenario

mode
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode
CPRI port All Surge 250 A
RET port All Surge Differential 3 kA

current mode
Common 5 kA
mode
Antenna Capability
Table 11-23 describes the antenna capability of the RRU3201.
Table 11-23 Antenna capability of the RRU3201

Capability
RRU3201 TMA supported AISG2.0-complied RET

antennas supported
NOTE



eNodeB

ng (MHz)
Mode
RRU3203 LTE 700 (band 12) 698 to 716 728 to 746

FDD
RF Specifications

Channels

be 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, or 15 MHz.
NOTE

Width x Depth)
RRU3203 –48 V DC; voltage l 480 mm x 356 mm x 140 l ≤21 kg (without

mm (31.4 L with the
housing)

eNodeB

Type Temperature Relative Absolute Atmospheric
Humidity Humidity Pressure
RRU32 l –40ºC to 5% RH to 100% RH 1 g/m3 to 30 g/m3 70 kPa to 106 kPa

03 +50ºC (with
solar
radiation of
1120 W/
m2)
l –40ºC to
+55ºC
(without
solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

eNodeB
n Scenario

supply mode
socket
mode
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE



eNodeB

ng (MHz)
Mode
RRU3220 LTE DD 800 (band 20) 832 to 847 791 to 806

FDD
842 to 862 801 to 821
RF Specifications

Channels

MHz.
NOTE

Width x Depth)

mm (15 L with the
housing)

eNodeB


(with solar RH m3 kPa
radiation of 1120
W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket

eNodeB

n Scenario

mode
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode
Alarm port All Surge Differential 3 kA

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE


eNodeB


ng (MHz)
Mode
RRU3221 LTE 2600 (band 7) 2500 to 2570 2620 to 2690

FDD
RF Specifications

Channels

MHz.
NOTE

Width x Depth)
RRU3221 –48 V DC; voltage l 480 mm x 270 mm x 140 l ≤ 20 kg (without

57 V DC housing) l ≤ 22 kg (with the
mm (25 L with the
housing)

eNodeB
Type Temperature Relative Absolute Atmospher

Humidity Humidity ic Pressure
RRU3221 l –40ºC to +50ºC (with 5% RH to 100% 1 g/m3 to 30 g/ 70 kPa to 106

solar radiation of RH m3 kPa
1120 W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE



eNodeB

ng (MHz)
Mode
RRU3222 LTE DD 800 (band 20) 832 to 862 791 to 821

FDD
RF Specifications

Channels

be 5 MHz, 10 MHz, 15 MHz, or
20MHz.
NOTE

Width x Depth)

mm (25 L with the
housing)

eNodeB
Type Temperature Relative Absolute Atmospheric

Humidity Humidity Pressure
RRU322 l –40ºC to +50ºC 5% RH to 100% 1 g/m3 to 30 g/m3 70 kPa to 106

2 (with solar RH kPa
radiation of
1120 W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket

eNodeB

n Scenario

mode
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE


eNodeB

Type Working Frequency Band RX Band (MHz) TX Band (MHz)

Mode (MHz)
RRU3240 LTE FDD 2600 (band 7) 2500 to 2570 2620 to 2690
RF Specifications

Channels

MHz.
NOTE

Width x Depth)
RRU3240 –48 V DC; voltage l 480 mm x 270 mm x 140 l ≤ 20 kg (without

mm (25 L with the
housing)

eNodeB

RRU3240 l –40ºC to +50ºC (with 5% RH to 1 g/m3 to 30 g/ 70 kPa to

solar radiation of 1120 100% RH m3 106 kPa
W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE



eNodeB

ng (MHz)
Mode
RRU380 LTE AWS (band 4) 1710 to 1755 2110 to 2155

8 FDD
2100 (band 1) 1920 to 1980 2110 to 2170
RF Specifications

Channels

be:
l 1.4 MHz, 3MHz, 5 MHz, 10
MHz, 15 MHz, or 20MHz in the
AWS band.
l 5 MHz, 10 MHz, 15 MHz, or
20MHz in the 2100 MHz band.
NOTE

Width x Depth)

mm (23.5 L with the
housing)

eNodeB


solar radiation of 1120 RH m3 kPa
W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE

RRU3908s are classified into RRU3908 V1 and RRU3908 V2. This section describes the
technical specifications of the RRU3908.


eNodeB

ng (MHz)
Mode
RRU3908 LTE 1800 (band 3) 1710 to 1755 1805 to 1850

V1 FDD
1740 to 1785 835 to 1880
RRU3908 LTE 850 (band 5) 824 to 849 869 to 894

V2 FDD
900 (band 8) 880 to 915 925 to 960
RF Specifications

Channels
RRU3908 V1 2T2R The bandwidth of each carrier can 2 x 30 W

be 5 MHz, 10 MHz, or 20MHz.
RRU3908 V2 2T2R The bandwidth of each carrier can 2 x 40 W

be:
l 1.4 MHz, 3 MHz, 5 MHz, or 10
MHz in the 850 MHz band.
l 1.4 MHz, 3 MHz, 5 MHz, 10
MHz, 15 MHz, or 20 MHz in the
900 MHz band.
NOTE

eNodeB

Width x Depth)

V1 range: –36 V DC to – mm (24 L without the the housing)
mm (31 L with the
housing)

V2 range: –36 V DC to – mm (24 L without the the housing)
mm (31 L with the
housing)


V1 (with solar radiation RH m3 kPa
of 1120 W/m2)
(without solar
radiation)

V2 (with solar radiation RH m3 kPa
of 1120 W/m2)
(without solar
radiation)

eNodeB

Rating

V1 l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

V2 l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.
n Scenario

supply mode
socket
mode
current mode
Common 20 kA
mode

eNodeB

n Scenario

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability
RRU3908 V1 TMA supported AISG2.0-complied RET

antennas supported
RRU3908 V2 TMA supported AISG2.0-complied RET

antennas supported
NOTE



eNodeB

ng (MHz)
Mode
RRU3928 LTE 900 (band 8) 880 to 915 925 to 960

FDD
1800 (band 3) 1710 to 1785 1805 to 1880
RF Specifications

Channels

be 1.4 MHz, 3 MHz, 5 MHz, 10
NOTE

Width x Depth)
RRU3928 –48 V DC; voltage l 480 mm x 220 mm x 140 l ≤ 13.5 kg (without

mm (15 L with the
housing)

eNodeB


solar radiation of RH m3 kPa
1120 W/m ) 2
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE



eNodeB

Type Working Frequency RX Band (MHz) TX Band (MHz)
Mode Band (MHz)
RRU3929 LTE FDD 900 (band 8) 880 to 915 925 to 960
1800 (band 3) 1710 to 1785 1805 to 1880
RF Specifications

Channels

be 1.4 MHz, 3 MHz, 5 MHz, 10
NOTE

Width x Depth)
RRU3929 –48 V DC; voltage l 480 mm x 356 mm x 140 l ≤ 23.5 kg (without

mm (31 L with the
housing)

eNodeB

RRU3929 l –40ºC to +50ºC (with 5% RH to 1 g/m3 to 30 g/ 70 kPa to

solar radiation of 1120 100% RH m3 106 kPa
W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability

antennas supported
NOTE



eNodeB
Type Working Mode Frequency Band (MHz)
RRU3232 LTE TDD 2600 (band 38): 2570 to 2620
2600 (band 41): 2496 to 2690
2300 (band 40): 2300 to 2400
3500: 3400 to 3700
1800: 1755 to 1920
RF Specifications

Channels
RRU3232 4T4R The bandwidth of each carrier can l 3500 MHz band:
be 10 MHz or 20 MHz. 4 x 10 W
l Other bands: 4 x
20 W
NOTE

Width x Depth)

mm (24.7 L with the
housing)

eNodeB


solar radiation of 1120 RH m3 kPa
W/m2)
(without solar
radiation)

Rating

l 3GPP TS 25.141
V3.0.0
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NOTE
μs.

n Scenario

supply mode
socket
mode

eNodeB

n Scenario
current mode
Common 20 kA
mode

current mode
Common 40 kA
mode

current mode
Common 5 kA
mode
Antenna Capability

Capability
RRU3232 Not supported AISG2.0-complied RET

antennas supported
NOTE


eNodeB Technical Description (V100R003C00 - 06) (PDF) - EN PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

eNodeB Technical Description (V100R003C00 - 06) (PDF) - EN PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

eNodeB

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2011-11-25) Huawei Proprietary and Confidential i

About This Document

Product Name Version

BTS3900 LTE V100R003C00

BTS3900A LTE V100R003C00

BTS3900L LTE V100R003C00

DBS3900 LTE V100R003C00

DBS3900 LTE TDD V100R003C00

Issue 06 (2011-11-25) Huawei Proprietary and Confidential ii

This chapter describes the changes in the eNodeB Technical Description.

2 LTE-SAE System Architecture

5 Environment Monitoring Principles

This chapter describes environment monitoring principles for eNodeBs. Environment

6 eNodeB Synchronization Modes

7 Operation and Maintenance of eNodeBs

This chapter describes eNodeB topologies on the S1 and CPRI interfaces.

10 Typical Hardware Configurations of an eNodeB

This chapter describes the hardware configurations of an eNodeB.

11 Technical Specifications of Radio Frequency Units

Issue 06 (2011-11-25) Huawei Proprietary and Confidential iii

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

Issue 06 (2011-11-25) Huawei Proprietary and Confidential iv

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

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

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

Issue 06 (2011-11-25) Huawei Proprietary and Confidential v

Double-click Press the primary mouse button twice continuously and

Issue 06 (2011-11-25) Huawei Proprietary and Confidential vi

About This Document.....................................................................................................................ii

5 Environment Monitoring Principles........................................................................................15

11 Technical Specifications of Radio Frequency Units...........................................................55

Issue 06 (2011-11-25) Huawei Proprietary and Confidential vii

11.1.4 Technical Specifications of the MRFUd...............................................................................................61

Issue 06 (2011-11-25) Huawei Proprietary and Confidential viii

1 Changes in the eNodeB Technical

This chapter describes the changes in the eNodeB Technical Description.

Issue 06 (2011-11-25) Huawei Proprietary and Confidential 1

Topic Change Description

10.1 Typical Hardware Configurations l Modified the hardware quantities of a

10.2 Hardware Configurations of Modified the positions of the components of

10.3 Hardware Configurations of Modified the positions of the components of

10.4 Hardware Configurations of Modified the positions of the components of

10.5 Hardware Configurations of Modified the hardware configuration

10.6 Hardware Configurations of Modified the hardware configuration

Issue 06 (2011-11-25) Huawei Proprietary and Confidential 2

Change Type Description