ENodeB Technical Description (V100R003C00 - 14) (PDF) - en

eNodeB
V100R003C00
Technical Description
Issue 14
Date 2013-11-30
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 14 (2013-11-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
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, typical hardware
configurations, and technical specifications.
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

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
eNodeB
Technical Description About This Document
ii
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, GLONASS clock, IEEE1588 V2
clock, Clock over IP, synchronous Ethernet, 1 PPS+TOD clock, BITS clock, and E1/T1 line
clock. If an eNodeB fails to obtain clock signals, it works in free-run mode for a certain period
of time.
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 the topologies on the S1 interface, topologies on the common public radio
interface (CPRI), and CPRI port specifications.
10 Typical Hardware Configurations of an eNodeB
This chapter describes the hardware configurations of an eNodeB.
11 Product Specifications
eNodeB
iii
Product specifications of the eNodeB include technical specifications of the BBU3900, radio
frequency unit (RFU), and remote radio unit (RRU) and engineering specifications of each type
of cabinet.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

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
eNodeB
iv
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.
{ 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
eNodeB
v
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.
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.
eNodeB
vi
Contents
About This Document.....................................................................................................................ii
1 Changes in the eNodeB Technical Description.......................................................................1
2 LTE-SAE System Architecture....................................................................................................9
3 eNodeB Functions.......................................................................................................................11
4 eNodeB Structure.........................................................................................................................13
4.1 Logical Structure of BBU3900.....................................................................................................................................14
4.2 Logical Structure of RRUs/RFUs.................................................................................................................................15
5 Environment Monitoring Principles........................................................................................18
6 eNodeB Synchronization Modes..............................................................................................22
7 Operation and Maintenance of eNodeBs................................................................................24
7.1 OM Modes....................................................................................................................................................................25
7.2 OM Functions...............................................................................................................................................................26
8 eNodeB Reliability......................................................................................................................29
8.1 System Reliability.........................................................................................................................................................30
8.2 Hardware Reliability.....................................................................................................................................................31
8.3 Software Reliability......................................................................................................................................................32
9 eNodeB Topologies.....................................................................................................................34
9.1 eNodeB Transport Network Topologies.......................................................................................................................35
9.2 eNodeB CPRI-based Topologies..................................................................................................................................37
10 Typical Hardware Configurations of an eNodeB...............................................................44
10.1 Typical Hardware Configurations and Subrack Numbers..........................................................................................45
10.2 Hardware Configurations of BTS3900 LTE..............................................................................................................51
10.3 Hardware Configurations of BTS3900A LTE............................................................................................................54
10.4 Hardware Configurations of BTS3900L LTE............................................................................................................57
10.5 Hardware Configurations of DBS3900 LTE..............................................................................................................60
11 Product Specifications..............................................................................................................62
11.1 Technical Specifications for BBU3900......................................................................................................................63
11.2 Technical Specifications of RFUs..............................................................................................................................64
eNodeB
Technical Description Contents
vii
11.2.1 Technical Specifications of the LRFU....................................................................................................................65
11.2.2 Technical Specifications of the LRFUe...................................................................................................................68
11.2.3 Technical Specifications of the MRFU...................................................................................................................70
11.2.4 Technical Specifications of the MRFUd.................................................................................................................72
11.3 Technical Specifications of RRUs..............................................................................................................................75
11.3.1 Technical Specifications of the RRU3201..............................................................................................................77
11.3.9 Technical Specifications of the RRU3908............................................................................................................103
11.3.10 Technical Specifications of the RRU3928..........................................................................................................107
11.3.11 Technical Specifications of the RRU3929..........................................................................................................110
11.4 Engineering Specifications.......................................................................................................................................113
11.4.1 BTS3900 Engineering Specifications....................................................................................................................113
11.4.2 BTS3900L Engineering Specifications.................................................................................................................116
11.4.3 BTS3900A Engineering Specifications.................................................................................................................118
11.4.4 DBS3900 Engineering Specifications...................................................................................................................122
eNodeB
Technical Description Contents
viii
1 Changes in the eNodeB Technical
Description
This chapter describes the changes in the eNodeB Technical Description.
14 (2013-11-30)
This is the fourteenth official release.
Compared with issue 13 (2013-05-30) of V100R003C00, this issue does not add topics.
Compared with issue 13 (2013-05-30) of V100R003C00, this issue incorporates the changes
described in the following table.
Topic Change Description
11.3.3 Technical
Specifications of the
RRU3220
Changed the TMA support capability of RRU3220 to not
supported.

Compared with issue 13 (2013-05-30) of V100R003C00, this issue does not delete topics.
13 (2013-05-30)
This is the thirteenth official release.
10.1 Typical Hardware
Configurations and Subrack
Numbers
Added auxiliary cabinets IBBS700D and IBBS700T.
eNodeB
Technical Description 1 Changes in the eNodeB Technical Description
1
11.2.4 Technical
MRFUd
Modified the maximum power consumption.

12 (2013-01-24)
This is the twelfth official release.
Compared with issue 11 (2012-10-19) of V100R003C00, this issue adds the following new
section:
l 11.4 Engineering Specifications
4.2 Logical Structure of
RRUs/RFUs
Changed the filter to duplexer in the logic structure of an RF
module.
Numbers
l Removed description about the BTS3900A (Ver.D1)
cabinets, and renamed the BTS3900A (Ver.D2) cabinets
BTS3900A (Ver.D).
l Removed description about the DBS3900 (Ver.D1)
cabinets, and renamed the DBS3900 (Ver.D2) cabinets
DBS3900 (Ver.D).
11.2.1 Technical
Specifications of the LRFU
l Removed description about the AWS frequency band.
l Modified the maximum power consumption.
11.2.3 Technical
Specifications of the MRFU
Modified the receiver sensitivity when it operates in the 1800
MHz frequency band.
11.2.4 Technical
MRFUd
l Modified the receiver sensitivity when it operates in the
1800 MHz frequency band.
l Modified the maximum power consumption.
11.3.1 Technical
RRU3201
Modified the receiver sensitivity when it operates in the 700
MHz frequency band (band 13).
11.3.3 Technical
RRU3220
Modified the bandwidth and maximum power consumption.
eNodeB
2
11.3.10 Technical
RRU3928
Modified the receiver sensitivity
11.3.11 Technical
RRU3929
Modified the receiver sensitivity

11 (2012-10-19)
This is the eleventh official release.
11.2 Technical
Specifications of RFUs
Added the hybrid configuration rule for RFUs.
11.3 Technical
Specifications of RRUs
Added the hybrid configuration rule for RRUs.

10 (2012-09-20)
This is the tenth official release.
section:
l 11.1 Technical Specifications for BBU3900
7.2 OM Functions Added description about board-in-cabinet transportation.
Numbers
Added the support for Ver.D cabinets.
eNodeB
3
11.2 Technical
Specifications of RFUs
Added the transmit and receive capabilities of the RFU, and
the frequency bands and RATs supported by the RFU.
11.3 Technical
Added the transmit and receive capabilities of the RRU, and
the frequency bands and RATs supported by the RRU.
11.3.2 Technical
RRU3203
Updated the weight specifications.
11.3.9 Technical
RRU3908
Added the RRU3908 V1's support for the 15 MHz
bandwidth.

09 (2012-06-10)
This is the ninth official release.
11.3 Technical
Updated the operating environment of RRUs.
11.3.8 Technical
RRU3841
Updated the output power of an RRU3841.

08 (2012-04-16)
This is the eighth official release.
section:
l 11.3.8 Technical Specifications of the RRU3841
eNodeB
4
4.2 Logical Structure of
RRUs/RFUs
The logical structure of time division duplex (TDD) remote
radio units (RRUs) is deleted.
9.2 eNodeB CPRI-based
Topologies
l The eNodeB CPRI-based topologies for TDD and
RRU3232 common public radio interface (CPRI) port
specifications are deleted.
l The radio frequency (RF) CPRI port specifications are
modified.
Numbers
Typical configurations for TDD are deleted.
11 Product Specifications l Specifications about receive (RX) sensitivity and power
consumption are added.
l Specifications about radio frequency unit (RFU)
dimensions and weights are added.

07 (2012-02-28)
This is the seventh official release.
6 eNodeB Synchronization
Modes
The GLONASS clock and free-running synchronization
modes are added.
9.2 eNodeB CPRI-based
Topologies
CPRI port specifications are added.

06 (2011-11-25)
This is the sixth official release.
section:
l 11 Product Specifications
eNodeB
5
4.2 Logical Structure of RRUs/RFUs The description of an RRU and an RFU is added.
9 eNodeB Topologies The full names of LRRU and MRRU are added.

05 (2011-09-30)
This is the fifth official release.
10.1 Typical Hardware Configurations
and Subrack Numbers
l The hardware quantities of a frequency
division duplex (FDD) eNodeB in typical
configurations are modified.
l The hardware quantities of a time division
duplex (TDD) eNodeB in typical
configurations are modified.
l Ver.B and Ver.C cabinets are distinguished
between each other.
10.2 Hardware Configurations of
BTS3900 LTE
The positions of the BTS3900 LTE components
in typical configurations and the hardware
configuration descriptions are modified.
BTS3900A LTE
The positions of the BTS3900A LTE components
BTS3900L LTE
The positions of the BTS3900L LTE components
DBS3900 LTE
The hardware configuration descriptions of the
DBS3900 LTE are modified.
Hardware Configurations of DBS3900
LTE TDD
The hardware configuration descriptions of the
DBS3900 LTE TDD are modified.

eNodeB
6
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.
02 (2011-03-15)
This is the second official release.
Numbers
Hardware quantities of a frequency division duplex (FDD)
eNodeB in typical configurations are modified.
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
eNodeB
7
4.2 Logical Structure of RRUs/
RFUs
l The logical structures of FDD RRUs and RFUs are all
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.
4.2 Logical Structure of RRUs/
RFUs
Descriptions of RRU/RFU logical structures are
combined into one section.
Numbers
Typical FDD/TDD configurations are updated.

eNodeB
8
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
UTRAN
EPC: Evolved Packet Core
network
MME: Mobility
Management Entity
S-GW: Serving Gateway UE: User Equipment

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
9
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 2 LTE-SAE System Architecture
10
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
eNodeB
Technical Description 3 eNodeB Functions
11
l Selection of an MME for a UE when the UE is in a network
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 3 eNodeB Functions
12
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 remote radio unit (RRU) or radio frequency unit (RFU) contains logical units such as the
CPRI module, transceiver (TRX), power module, power amplifier (PA), low noise amplifier
(LNA), duplexer, and TX/RX switch.
eNodeB
Technical Description 4 eNodeB Structure
13
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 LTE main processing
transmission unit (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 universal satellite card and clock unit (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
14
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 remote radio unit (RRU) or radio frequency unit (RFU) contains logical units such as the
CPRI module, transceiver (TRX), power module, power amplifier (PA), low noise amplifier
(LNA), duplexer, and TX/RX switch.
An 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 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 RRUs and RFUs.
eNodeB
15
Figure 4-2 Logical structure of RRUs and RFUs

RRU3240 is designed with 2T4R, RRU3841 is designed with 4T4R, other RRUs and the LTE
radio frequency unit (LRFU) are designed with 2T2R, and the multi-mode radio frequency unit
(MRFU) is designed with 1T2R.
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.
eNodeB
16
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.
Duplexer
A duplexer isolates the RX and TX signals so that signals can be received and transmitted
synchronously.
eNodeB
17
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
Technical Description 5 Environment Monitoring Principles
18
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 (Ver.B) LTE
Installation Guide or BTS3900 (Ver.C) 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
Port
X1 End X2 End Wire
Color
Description Pin
Assignment
EXT-
ALM0
X1.1 X2.1 Orange and
white
Boolean input 1+ Twisted pair
X1.2 X2.2 Orange Boolean input 1-
(GND)
X1.3 X2.3 Green and
white
X1.6 X2.6 Green Boolean input 2-
(GND)
X1.5 X2.5 Blue and
white
X1.4 X2.4 Blue Boolean input 3-
(GND)
eNodeB
19
Alarm
Port
X1 End X2 End Wire
Color
Description Pin
Assignment
X1.7 X2.7 Brown and
white
X1.8 X2.8 Brown Boolean input 4-
(GND)
EXT-
ALM1
X1.1 X2.1 Orange and
white
X1.2 X2.2 Orange Boolean input 5-
(GND)
X1.3 X2.3 Green and
white
X1.6 X2.6 Green Boolean input 6-
(GND)
X1.5 X2.5 Blue and
white
X1.4 X2.4 Blue Boolean input 7-
(GND)
X1.7 X2.7 Brown and
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 (Ver.B) LTE
Installation Guide or BTS3900A (Ver.C) 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
eNodeB
20
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 (Ver.B) LTE Installation Guide or BTS3900
(Ver.C) Installation Guide.
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
21
6 eNodeB Synchronization Modes
This chapter describes the clock synchronization modes of eNodeBs. eNodeBs support
synchronization with the following clocks: GPS/RGPS clock, GLONASS clock, IEEE1588 V2
clock, Clock over IP, synchronous Ethernet, 1 PPS+TOD clock, BITS clock, and E1/T1 line
clock. If an eNodeB fails to obtain clock signals, it works in free-run mode for a certain period
of time.
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.
GLONASS Clock
If an eNodeB synchronizes with the GLONASS clock, it achieves synchronization by obtaining
clock signals from a GLONASS receiver. The GLONASS clock supports both frequency
synchronization and time synchronization, with a precision to microseconds. To synchronize
with the GLONASS clock, an eNodeB must be equipped with a USCU board.
eNodeB
Technical Description 6 eNodeB Synchronization Modes
22
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
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.
Free-Run
Without an external clock source, a base station continues to work for at least 90 days in free-
run mode.
eNodeB
Technical Description 6 eNodeB Synchronization Modes
23
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
Technical Description 7 Operation and Maintenance of eNodeBs
24
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
25
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.
eNodeB
26
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.
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.
eNodeB
27
l Patch management includes query, download, loading, activation, deactivation, rollback,
and removal of patches. Installing patches does not affect system services.
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 Board-in-cabinet transportation indicates that base stations come with RFUs, PMUs, PSUs,
and BBU3900s installed and with cables laid. Board-in-cabinet transportation shortens
onsite hardware installation duration.
l With the automatic discovery of the eNodeB, users do not need to set the IP addresses of
the eNodeB 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.
NOTE
The security of the USB port is ensured by encryption.
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
28
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
Technical Description 8 eNodeB Reliability
29
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
30
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
31
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.
eNodeB
32
l Task monitoring: eNodeBs monitor the running status of every task for all types of errors
and faults, if any. When an error or a fault occurs in a task, an alarm is reported and self-
healing measures are taken to restore the task.
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: eNodeBs detect system faults through the software and hardware watchdogs.
When an error occurs in an eNodeB, the eNodeB automatically resets to restore itself to a
normal running status.
eNodeB
33
9 eNodeB Topologies
About This Chapter
This chapter describes the topologies on the S1 interface, topologies on the common public radio
interface (CPRI), and CPRI port specifications.
9.1 eNodeB Transport Network Topologies
eNodeBs support the star, chain, and tree topologies on IP networks.
9.2 eNodeB CPRI-based Topologies
eNodeBs support various topologies on the common public radio interface (CPRI): remote radio
units (RRUs) support the star, chain, hot backup ring, intra-board cold backup ring, and inter-
board cold backup ring topologies; radio frequency units (RFUs) support the star topology. In
addition to topologies, CPRI specifications cover the number of CPRI ports on a board or radio
frequency (RF) module, CPRI data rate, cascading capability, and maximum distance between
a baseband unit (BBU) and an RF module.
eNodeB
Technical Description 9 eNodeB Topologies
34
9.1 eNodeB Transport Network Topologies
eNodeBs support the star, chain, and tree topologies on IP networks.
An eNodeB communicates with a mobility management entity (MME) or serving gateway (S-
GW) through an S1 interface based on E1/T1 or FE/GE transmission. (FE is short for fast
Ethernet, and GE is short for gigabit Ethernet.) The S1 interface supports the star, chain, and
tree topologies, as shown in Figure 9-1.
Figure 9-1 Topologies on the S1 interface

Table 9-1 describes usage scenarios and characteristics of the preceding topologies.
eNodeB
35
Table 9-1 Usage scenarios and characteristics of the topologies
To
pol
og
y
Usage Scenario Advantage Disadvantage
Sta
r
The star topology is the
most common topology
and is applicable to
densely populated areas.
l Each eNodeB is
directly connected to
an MME or S-GW
through a transport
network. This simple
topology features easy
engineering,
maintenance, and
capacity expansion.
l Each eNodeB directly
exchanges data with an
MME or S-GW.
Signals travel through
few nodes, and
therefore network
reliability is high.
The star topology requires
more transport resources than
the other topologies.
Ch
ain
The chain topology is
applicable to belt-
shaped and sparsely
populated areas, such as
areas along highways
and railways.
This topology helps reduce
expenditure on
transmission equipment,
engineering, and leased
transmission cables.
l Signals travel through
many nodes, which lowers
network reliability.
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.
l The number of levels in a
chain topology cannot
exceed five.
eNodeB
36
To
pol
og
y
Usage Scenario Advantage Disadvantage
Tre
e
The tree topology is
applicable to areas with
complicated network
architecture, site
distribution, and
subscriber distribution,
for example, hot spot
areas in which
subscribers are widely
distributed.
This topology helps reduce
expenditure on
transmission equipment,
engineering, and leased
transmission cables.
l Signals travel through
many nodes, which lowers
network reliability.
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.
l The number of levels in a
tree topology cannot
exceed five.

9.2 eNodeB CPRI-based Topologies
eNodeBs support various topologies on the common public radio interface (CPRI): remote radio
units (RRUs) support the star, chain, hot backup ring, intra-board cold backup ring, and inter-
board cold backup ring topologies; radio frequency units (RFUs) support the star topology. In
addition to topologies, CPRI specifications cover the number of CPRI ports on a board or radio
frequency (RF) module, CPRI data rate, cascading capability, and maximum distance between
a baseband unit (BBU) and an RF module.
CPRI-based Topologies
On the CPRI interface, eNodeBs support the star, chain, and ring topologies.
Figure 9-2 shows the star topology.
eNodeB
37
Figure 9-2 Star

The star topology has the following advantages:
l Transmission reliability is high. When an RRU/RFU or an optical cable is faulty, only the
related sector is affected.
l This topology is easy. Installation and maintenance are convenient.
The disadvantage is that the star topology requires a larger number of optical cables than other
topologies.
Figure 9-3 shows the chain topology.
Figure 9-3 Chain

The chain topology helps reduce expenditure on transmission equipment.
The chain topology has the following disadvantages:
l The number of cascading levels and cascading distances are restricted.
l RRUs working in different modes cannot be cascaded.
eNodeB
38
l Faults in an upper-level RRU may affect the operation of its lower-level RRUs.
NOTE
RFUs do not support the chain topology.
Ring topologies are classified into the following types: hot backup ring, intra-board cold backup
ring, and inter-board cold backup ring. Figure 9-4, Figure 9-5, and Figure 9-6 show these
topologies respectively.
Figure 9-4 Hot backup ring
In the hot backup ring topology, two CPRI links transmit identical service data, but the LTE
baseband processing unit (LBBP) where the cell is established and the RRU process data on one
link only. If a CPRI port is faulty, services are switched over to the other CPRI link, with a
maximum interruption time of 500 ms. If the LBBP where the cell is established is faulty, the
cell is reestablished on the other LBBP, with a maximum service interruption time of 20s.
NOTE
The hot backup ring topology has the following constraints:
l Only ports 0, 1, and 2 on the two LBBPs can be used in this topology.
l The two LBBPs are installed in two slots among slots 0, 1, 2, and 3 in the BBU. If one is installed in slot 0,
the other can be installed only in slot 2 or 3.
l If the two LBBPs are installed in slots 2 and 3 in the BBU, a maximum of three rings are supported between
the LBBPs. In other situations, only one ring is supported.
eNodeB
39
Figure 9-5 Intra-board cold backup ring
In the intra-board cold backup ring topology, if a CPRI port is faulty, the cell is reestablished,
with a service interruption time shorter than 20s.
Figure 9-6 Inter-board cold backup ring
In the inter-board cold-backup ring topology, if a CPRI port or LBBP is faulty, the cell is
reestablished on the LBBP or the other LBBP, with a service interruption time shorter than 20s.
The advantage of ring topologies is that they are a redundancy type of the chain topology and
therefore provide higher transmission reliability.
Ring topologies have the following disadvantages:
l The number of cascading levels and cascading distances are restricted.
l RRUs working in different modes cannot be cascaded.
l Faults on the forwarding link of an upper-level RRU affect the operation of its lower-level
RRUs.
eNodeB
40
NOTE
RFUs do not support the ring topologies.
Specifications of CPRI Ports
The number of cells supported varies according to CPRI data rates, as listed in Table 9-2.
Table 9-2 CPRI data rate and the number of cells supported
CPRI
Data
Rate
(Gbit/s)
Number of Cells Supported (4 x 4
MIMO)
Number of Cells Supported (2 x 2
MIMO)
1.25 Due to the limited transmission
bandwidth of CPRI ports, a 4x4 MIMO
cell is not recommended.
1
2.5 1 if the cell bandwidth is less than or
equal to 10 MHz
l 2 if the cell bandwidth is less than
or equal to 10 MHz
l 1 if the cell bandwidth is 15 MHz or
20 MHz
4.9 l 2 if the cell bandwidth is less than
or equal to 10 MHz
20 MHz
l 4 if the cell bandwidth is less than
or equal to 10 MHz
20 MHz

Table 9-3 lists the specifications of CPRI ports on different LBBPs.
Table 9-3 Specifications of CPRI ports on LBBPs
Board Number of CPRI
Ports
CPRI Data Rate
(Gbit/s)
Topology
LBBPc 6 1.25, 2.5, or 4.9 Star, chain, or ring

Table 9-4 lists the specifications of CPRI ports on different RF modules.
Table 9-4 Specifications of CPRI ports on RF modules
Mod
ule
Number
of CPRI
Ports
CPRI Data
Rate (Gbit/s)
Topology Cascading Levels Maximu
m
Distance
from the
BBU (km)
LRFU 2 1.25 or 2.5 Star N/A N/A
eNodeB
41
Mod
ule
Number
of CPRI
Ports
CPRI Data
Rate (Gbit/s)
Topology Cascading Levels Maximu
m
Distance
from the
BBU (km)
LRFU
e
2 1.25, 2.5, or 4.9 Star N/A N/A
MRF
U V2
2 1.25 or 2.5 Star N/A N/A
MRF
Ud
2 1.25, 2.5, or 4.9 Star N/A N/A
RRU3
201
2 1.25 or 2.5 Star, chain,
or ring
l Three levels are
supported if the
cell bandwidth is
less than or
equal to 5 MHz.
l Two levels are
supported if the
cell bandwidth is
10 MHz.
l Cascading is not
recommended if
the cell
bandwidth is
greater than or
equal to 15
MHz.
20
RRU3
203
or ring
20
RRU3
220
or ring
20
RRU3
221
2 1.25, 2.5, or 4.9 Star, chain,
or ring
20
RRU3
222
or ring
20
RRU3
808
or ring
20
RRU3
240
2 1.25, 2.5, or 4.9 Star, chain,
or ring
N/A 20
RRU3
2841
2 1.25, 2.5, or 4.9 Star, chain,
or ring
N/A 20
RRU3
908
V1
2 1.25 or 2.5 Star N/A 20
RRU3
908
V2
2 1.25 or 2.5 Star N/A 20
RRU3
928
2 1.25, 2.5, or 4.9 Star N/A 20
RRU3
929
2 1.25, 2.5, or 4.9 Star N/A 20

eNodeB
42
NOTE
The Cascading Levels column in Table 9-4 lists the cascading capability of an RF module where a single carrier
is configured and the maximum CPRI rate is used.
eNodeB
43
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.
eNodeB
Technical Description 10 Typical Hardware Configurations of an eNodeB
44
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 eNodeB in typical configurations.
Table 10-1 Hardware quantities of an eNodeB in typical configurations
Configuration Number of
LMPTs
Number of
LBBPcs
Number of
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, 4x2 downlink
MIMO/Uplink 4-way receive
diversity
1 1 6
3 x 15 MHz/20 MHz, 4x2 downlink
MIMO/Uplink 4-way receive
diversity
1 3 6

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 15 MHz, 4 x 2 MIMO
indicates that the eNodeB is configured with three cells of 15 MHz bandwidth, and each cell uses four 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.
eNodeB
45
l The subrack number of the BBU3900 components is the same as the subrack number of
BBU3900.
Table 10-2 lists the mapping between eNodeB models and cabinets. Table 10-3 shows the
subrack numbers of cabinets.
Table 10-2 Mapping between eNodeB models and cabinets
eNodeB Model Cabinet Used
BTS3900 LTE l BTS3900 (Ver.B): supports -48 V DC, +24 V DC, 220 V AC, or
110 V AC power input.
l BTS3900 (Ver.C): supports -48 V DC, 220 V AC, or 110 V AC
power input.
l BTS3900 (Ver.D): supports -48 V DC or 220 V AC power input.
BTS3900L LTE A BTS3900L can use a BTS3900L (Ver.B) cabinet, a BTS3900L
(Ver.C) cabinet, or a BTS3900L (Ver.D) cabinet. A single cabinet can
house a maximum of 12 radio frequency (RF) modules and 2 baseband
units (BBUs). Both types of cabinets support -48 V DC power input.
BTS3900A LTE l Power cabinets: APM30, APM30H (Ver.A), APM30H (Ver.B),
APM30H (Ver.C), APM30H (Ver.D).
l RF cabinet: RFC (Ver.B), RFC (Ver.C), RFC (Ver.D)
l Transmission cabinets: TMC, TMC11H (Ver.A), TMC11H
(Ver.B), TMC11H (Ver.C), TMC11H (Ver.D).
l Battery cabinets: BBC, IBBS200T (Ver.A), IBBS200T (Ver.B),
IBBS200T (Ver.C), IBBS200T (Ver.D), IBBS200D (Ver.B),
IBBS200D (Ver.C), IBBS200D (Ver.D), IBBS700D, and
IBBS700T.
DBS3900 LTE l Power cabinets: APM30, APM30H (Ver.A), APM30H (Ver.B),
APM30H (Ver.C), APM30H (Ver.D).
l Outdoor power cabinet: TP48600A.
l Transmission cabinets: TMC, TMC11H (Ver.A), TMC11H
(Ver.B), TMC11H (Ver.C), TMC11H (Ver.D).
l Battery cabinets: BBC, IBBS200T (Ver.A), IBBS200T (Ver.B),
IBBS200T (Ver.C), IBBS200T (Ver.D), IBBS200D (Ver.B),
IBBS200D (Ver.C), IBBS200D (Ver.D), IBBS700D, and
IBBS700T.
l Other cabinets: OMB, IMB03, and 19-inch rack.

NOTE
IBBS700D and IBBS700T are used only when APM30H (Ver.D) is used.
eNodeB
46
Table 10-3 Subrack numbers
Cabinet Subrack Number
BTS3900 (Ver.B),
BTS3900 (Ver.C)
and BTS3900
(Ver.D) cabinet
eNodeB
47
BTS3900L
(Ver.B),
BTS3900L
(Ver.C), and
BTS3900L(Ver.D)
cabinet
eNodeB
48
APM30H (Ver.B),
APM30H (Ver.C),
and APM30H
(Ver.D) cabinet
RFC (Ver.B), RFC
(Ver.C), and RFC
(Ver.D) cabinet
eNodeB
49
TMC11H (Ver.B),
TMC11H (Ver.C),
and TMC11H
(Ver.D) cabinet
IBBS200D/
IBBS200T (Ver.B),
IBBS200D/
IBBS200T (Ver.C),
and IBBS200D/T
(Ver.D) cabinet
eNodeB
50
IBBS700D and
IBBS700T 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
51
Figure 10-1 Positions of the components of BTS3900 LTE in typical configurations
35MHz/10MHz
DL 4x2 MIMO /
UL 4Rx Diversity
LMPT
LBBPc
LRFU
65MHz/10MHz 22MIMO
315MHz/20MHz
DL 4x2 MIMO /
UL 4Rx Diversity
315MHz/20MHz 22MIMO

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, DL 4x2 MIMO / UL 4Rx Diversity.
eNodeB
52
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.
Figure 10-3 Hardware configuration of BTS3900 LTE in the case of 6 x 5 MHz/10 MHz, 2 x
2 MIMO

eNodeB
53
Figure 10-4 Hardware configuration of BTS3900 LTE in the case of 3 x 5 MHz/10 MHz, DL
4x2 MIMO / UL 4Rx Diversity

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
54
Figure 10-5 Positions of the components of BTS3900A LTE in typical configurations
315MHz/20MHz 22MIMO 65MHz/10MHz 22MIMO
35MHz/10MHz
DL 4x2 MIMO /
UL 4Rx Diversity
315MHz/20MHz
LMPT
LBBPc
LRFU
DL 4x2 MIMO /
UL 4Rx Diversity

eNodeB
55
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, DL 4x2 MIMO / UL 4Rx Diversity.
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
56
Figure 10-8 Hardware configuration of BTS3900A LTE in the case of 3 x 5 MHz/10 MHz, DL

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
57
Figure 10-9 Positions of the components of BTS3900L LTE in typical configurations
315MHz/20MHz 22MIMO
LMPT
LBBPc
LRFU
65MHz/10MHz 22MIMO
35MHz/10MHz
DL 4x2 MIMO /
UL 4Rx Diversity
315MHz/20MHz
DL 4x2 MIMO /
UL 4Rx Diversity
65MHz/10MHz 22MIMO
MRFU

eNodeB
58
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
59
Figure 10-12 Hardware configuration of BTS3900L LTE in the case of 3 x 5 MHz/10 MHz,
DL 4x2 MIMO / UL 4Rx Diversity

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
60
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, DL
eNodeB
61
11 Product Specifications
About This Chapter
Product specifications of the eNodeB include technical specifications of the BBU3900, radio
frequency unit (RFU), and remote radio unit (RRU) and engineering specifications of each type
of cabinet.
11.1 Technical Specifications for BBU3900
This section describes the technical specifications of the BBU, which include equipment
specifications, input power specifications, environment specifications, and transmission ports.
11.2 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.3 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.4 Engineering Specifications
This section describes engineering specifications of each base station, including input power
specifications, equipment specifications, environment specifications, surge protection
specifications, and standards that have been complied with.
eNodeB
Technical Description 11 Product Specifications
62
11.1 Technical Specifications for BBU3900
This section describes the technical specifications of the BBU, which include equipment
specifications, input power specifications, environment specifications, and transmission ports.
Equipment Specifications
Table 11-1 lists the size and weight of the BBU.
Table 11-1 Size and weight of the BBU
Item Specification
Dimensions (H x W
x D)
86 mm x 442 mm x 310 mm
Weight 12 kg (full configuration)

Input Power Specifications
Table 11-2lists the input power specifications of the BBU.
Table 11-2 Input power specifications of the BBU
Input power voltage range
-48V DC -57 V DC to -38.4 V DC

Environment Specifications
Table 11-3 lists the environment specifications of the BBU.
Table 11-3 Environment specifications of the BBU
Item Specification
Operating
temperature
l -20 C to +50 C (working in a long time)
l +50 C to +55 C (working in a short time)
NOTE
Short term indicates that a base station does not work for over 15 days within
a year or that a base station does not continuously work for over 72 hours.
Relative humidity 5% RH to 95% RH
Ingress Protection
(IP) rating
IP 20
eNodeB
63
Item Specification
Atmospheric
pressure
70 kPa to 106 kPa

Transmission Port Specifications
Table 11-4 lists transmission ports on a BBU.
Table 11-4 Transmission ports on a single-mode BBU
Mode Transmission port
LTE l Two FE/GE electrical ports.
l Or two FE/GE optical ports.
l Or one FE/GE electrical port and one FE/GE optical port.
l Two optional E1/T1 ports. Each port provides four E1/T1s.

CPRI port Specifications
Table 11-5 lists the CPRI ports specifications of the BBU.
Table 11-5 CPRI ports on a single-mode BBU
Mode CPRI port
LTE l Supporting six CPRI ports per LBBP.
l The standard CPRI 4.0 port is supported and is backward compatible
with the CPRI 3.0 port.

11.2 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,
Type
Table 11-6 describes capabilities, working modes and frequency bands of the RFU.
eNodeB
64
Table 11-6 RFU capabilities, working modes and frequency bands
RFU Model TX and RX
Mode
Frequency
Band
Capacity Maximum
Output Power
(W)
LRFU 2T2R 2600 (band 7) One carrier. The
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz,
or 20.
2 x 40
LRFUe 2T2R DD 800MHz
(band 20)
One carrier. The
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz,
or 20 MHz.
2 x 60
MRFU 1T2R l 900 (band 8)
l 1800 (band
3)
One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz,
10 MHz, 15
MHz, or 20
MHz.
1 x 60
MRFUd 2T2R l 900 (band 8)
l 900 (P25)
l 1800 (band
3)
One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz,
10 MHz, 15
MHz, or 20
MHz.
2 x 60

Hybrid Configuration Rule
In an LTE network, hybrid configuration refers to connecting two RF modules on the same
frequency band to the same LBBP. The two RF modules serve one sector and support higher
system capacity. For example, two 1T2R RFUs can be configured into a 2T2R cell.
The hybrid configuration rule for RFUs is as follows:
l Two 1T2R RFUs of the same type can be used together and configured to work in 2T mode.
l Two 2T2R RFUs of the same type can be used together and configured to work in 4T mode.
11.2.1 Technical Specifications of the LRFU
This section describes the technical specifications of the LRFU.
eNodeB
65
Working Mode and Frequency Band
Table 11-7 describes the working mode and frequency bands of the LRFU.
Table 11-7 Working mode and frequency bands of the LRFU
Type Worki
ng
Mode
Frequency Band
(MHz)
RX Band (MHz) TX Band (MHz)
LRFU LTE
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-8 describes the RF specifications of the LRFU.
The receiver sensitivity, as recommended in 3GPP TS 36.104, is measured under 5 MHz channel
bandwidth @ FRC A1-3 in Annex A.1 (QPSK, R=1/3, 25 RB).
Table 11-8 RF specifications of the LRFU
Type RX
and
TX
Chan
nels
Capacity Receiver
Sensitivity (dBm)
Maximu
m
Output
Power
(W)
Maximum
Power
Consumption
(W)
1T1R 1T2R
LRF
U
2T2R One carrier. The
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz, or
20.
-105.8 -108.6 2 x 40 335

NOTE
A x Bin Output Power (W) indicates that the eNodeB uses A transmit (TX) channels and the output power
of each channel is B W.
Engineering Specifications
Table 11-9 describes the physical specifications of the LRFU.
eNodeB
66
Table 11-9 Equipment specifications of an LRFU
Type Dimensions (H x W x D) Weight (kg)
LRFU 9U x 14HP x 308.5mm (with
the panel)
12

Table 11-10 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-10 Surge protection specifications for the ports on the LRFU
Port Applicatio
n Scenario
Surge Protection Mode Specification
DC power
supply
socket
All Surge Differential
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
Antenna port All Surge
current
Differential
mode
8 kA
Common
mode
40 kA
Monitoring
port
All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Table 11-11 describes the antenna capability of the LRFU.
eNodeB
67
Table 11-11 Antenna capability of the LRFU
Type TMA Support Capability RET Antenna Support
Capability
LRFU TMA supported AISG2.0-complied RET
antennas supported

NOTE
If an RRU supports RET antennas, the feeding voltage and feeding current are 12 V and 2.3 A, respectively.
11.2.2 Technical Specifications of the LRFUe
This section describes the technical specifications of the LRFUe.
Table 11-12 describes the working mode and frequency bands of the LRFUe.
Table 11-12 Working mode and frequency bands of the LRFUe
Type Worki
ng
Mode
Frequency Band
(MHz)
LRFUe LTE
FDD
DD 800MHz (band
20)
832 to 862 791 to 821

RF Specifications
Table 11-13 describes the RF specifications of the LRFUe.
Table 11-13 RF specifications of the LRFUe
Type RX
and
TX
Chan
nels
Capacity Receiver Sensitivity
(dBm)
Maximu
m
Output
Power
(W)
Maximum
Power
Consumpt
ion (W)
1T1R 1T2R
LRF
Ue
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz,
or 20 MHz.
-106.3 -109.1 2 x 60 440
eNodeB
68

NOTE
Table 11-14 describes the physical specifications of the LRFUe.
Table 11-14 Equipment specifications of an LRFUe
LRFUe 9U x 14HP x 308.5mm (with
the panel)
12

Table 11-15 describes the surge protection specifications for the ports on the LRFUe.
NOTE
s.
Table 11-15 Surge protection specifications for the ports on the LRFUe
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
Monitoring
port
All Surge
current
Differential
mode
3 kA
eNodeB
69
Port Applicatio
n Scenario
Common
mode
5 kA

Antenna Capability
Table 11-16 describes the antenna capability of the LRFUe.
Table 11-16 Antenna capability of the LRFUe
Capability
LRFUe TMA supported AISG2.0-complied RET
antennas supported

NOTE
11.2.3 Technical Specifications of the MRFU
This section describes the technical specifications of the MRFU.
Table 11-17 describes the working mode and frequency bands of the MRFU.
Table 11-17 Working mode and frequency bands of the MRFU
Type Worki
ng
Mode
Frequency Band
(MHz)
MRFU LTE
FDD
900 (band 8) 880 to 915 925 to 960
1800 (band 3) 1710 to 1770 1805 to 1865
1725 to 1785 1820 to 1880

RF Specifications
Table 11-18 describes the RF specifications of the MRFU.
eNodeB
70
Table 11-18 RF specifications of the MRFU
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
MRF
U
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
l 900:
-106.1
l 1800:
-106.6
l 900:
-108.9
l 1800:
-109.4
1 x 60 l 900:
290
l 1800:
345

NOTE
Table 11-19 describes the physical specifications of the MRFU.
Table 11-19 Equipment specifications of an MRFU
MRFU 9U x 14HP x 308.5mm (with
the panel)
12

Table 11-20 describes the surge protection specifications for the ports on the MRFU.
NOTE
s.
Table 11-20 Surge protection specifications for the ports on the MRFU
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
eNodeB
71
Port Applicatio
n Scenario
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
Monitoring
port
All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Table 11-21 describes the antenna capability of the MRFU.
Table 11-21 Antenna capability of the MRFU
Capability
MRFU TMA supported AISG2.0-complied RET
antennas supported

NOTE
11.2.4 Technical Specifications of the MRFUd
This section describes the technical specifications of the MRFUd.
Table 11-22 describes the working mode and frequency bands of the MRFUd.
eNodeB
72
Table 11-22 Working mode and frequency bands of the MRFUd
Type Worki
ng
Mode
Frequency Band
(MHz)
MRFUd LTE
FDD
900 (band 8) 880 to 915 925 to 960
900 (P25) 890 to 915 935 to 960
1800 (band 3) 1710 to 1785 1805 to 1880

RF Specifications
Table 11-23 describes the RF specifications of the MRFUd.
Table 11-23 RF specifications of the MRFUd
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
MRF
Ud
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
l 900:
-106.3
l 900
(P25):
-106.3
l 1800:
-106.6
l 900:
-109.1
l 900
(P25):
-109.1
l 1800:
-109.4
2 x 60 l 900:
475
l 900
(P25):
475
l 1800:
495

NOTE
Table 11-24 describes the physical specifications of the MRFUd.
Table 11-24 Equipment specifications of an MRFUd
MRFUd 9U x 14HP x 308.5mm (with
the panel)
12
eNodeB
73

Table 11-25 describes the surge protection specifications for the ports on the MRFUd.
NOTE
s.
Table 11-25 Surge protection specifications for the ports on the MRFUd
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
Monitoring
port
All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Table 11-26 describes the antenna capability of the MRFUd.
Table 11-26 Antenna capability of the MRFUd
Capability
MRFUd TMA supported AISG2.0-complied RET
antennas supported

eNodeB
74
NOTE
11.3 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,
Type
Table 11-27 describes capabilities, working modes and frequency bands of the RRU.
Table 11-27 RRU capabilities, working modes and frequency bands
RRU
Model
TX and RX
Mode
Frequency
Band
Capacity Maximum
Output Power
(W)
RRU3201 2T2R l 700 (band 13)
l 2600 (band 7)
One carrier. The
bandwidth of
each carrier can
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
2 x 40
RRU3203 2T2R 700 (band 12) One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz, 10
MHz, or 15 MHz.
2 x 40
RRU3220 2T2R DD 800 (band
20)
One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 40
eNodeB
75
RRU
Model
TX and RX
Mode
Frequency
Band
Capacity Maximum
Output Power
(W)
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 40
RRU3222 2T2R DD 800 (band
20)
One carrier. The
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz, or
20MHz.
2 x 40
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 40
RRU3808 2T2R l AWS (band
4)
l 2100 (band 1)
One carrier. The
bandwidth of
each carrier can
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.
2 x 40
RRU3841 4T4R AWS (band 4) One carriers. The
bandwidth of
each carrier can
be 5, 10, 15, or 20
MHz.
For details, see
Table 3 Output
Power of an
RRU3841
eNodeB
76
RRU
Model
TX and RX
Mode
Frequency
Band
Capacity Maximum
Output Power
(W)
RRU3908
V1
2T2R 1800 (band 3) One carrier. The
bandwidth of
each carrier can
be 5 MHz, 10
MHz, 15 MHz, or
20MHz.
2 x 30
RRU3908
V2
2T2R 900 (band 8) One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 40
RRU3928 2T2R l 900 (band 8)
l 1800 (band 3)
One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 40
RRU3929 2T2R l 900 (band 8)
l 1800 (band 3)
One carrier. The
bandwidth of
each carrier can
be 1.4 MHz, 3
MHz, 5 MHz, 10
MHz, 15 MHz, or
20 MHz.
2 x 60

Hybrid Configuration Rule
In an LTE network, hybrid configuration refers to connecting two RF modules on the same
frequency band to the same LBBP. The two RF modules serve one sector and support higher
system capacity. For example, two 2T2R RRUs can be configured into a 4T4R cell.
The hybrid configuration rule for RRUs is as follows:
l Two 1T2R RRUs of the same type can be used together and configured to work in 2T mode.
l Two 2T2R RRUs of the same type can be used together and configured to work in 4T mode.
11.3.1 Technical Specifications of the RRU3201
This section describes the technical specifications of the RRU3201.
eNodeB
77
Table 11-28 describes the working mode and frequency bands of the RRU3201.
Table 11-28 Working mode and frequency bands of the RRU3201
Type Workin
g Mode
Frequency
Band (MHz)
RRU3201 LTE
FDD
700 (band 13) 777 to 787 746 to 756
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-29 describes the RF specifications of the RRU3201.
Table 11-29 RF specifications of the RRU3201
Type RX
and
TX
Chann
els
Capacity Receiver
Sensitivity (dBm)
Maximu
m Output
Power
(W)
Maximum
Power
Consumpt
ion (W)
1T1R 1T2R
RRU3
201
bandwidth of each
carrier can 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
l 700
(band
13):
-105.
8
l 2600:
-105.
8
l 700
(band
13):
-108.
6
l 2600:
-108.
6
2 x 40 l 700
(band
13): 304
l 2600:
370

NOTE
Table 11-30 describes the physical specifications of the RRU3201.
eNodeB
78
Table 11-30 Physical specifications of the RRU3201
Type Input Power Dimensions (Height x
Width x Depth)
Weight (kg)
RRU3201 48 V DC; voltage
range: 36 V DC to
57 V DC
l 480 mm x 270 mm x 140
mm (18 L without the
housing)
l 485 mm x 285 mm x 170
mm (23.5 L with the
housing)
l 17.5 kg
(without the
housing)
l 19 kg (with the
housing)

Table 11-31 describes the environmental specifications of the RRU3201.
Table 11-31 Environmental specifications of the RRU3201
Type Temperature Relative
Humidity
Absolute
Humidity
Atmospheri
c Pressure
RRU3201
l 40
C to +50
C
(with solar radiation
of 1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Table 11-32 describes the compliance standards for the RRU3201.
Table 11-32 Compliance standards of the RRU3201
Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3201 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"
NEBS GR63 zone4 IP65

Table 11-33 describes the surge protection specifications for the ports on the RRU3201.
eNodeB
79
NOTE
s.
Table 11-33 Surge protection specifications for the ports on the RRU3201
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
CPRI port All Surge 250 A
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Table 11-34 describes the antenna capability of the RRU3201.
Table 11-34 Antenna capability of the RRU3201
Capability
RRU3201 TMA supported AISG2.0 and AISG1.1

NOTE
eNodeB
80
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3203 LTE
FDD
700 (band 12) 698 to 716 728 to 746

RF Specifications
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
203
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, or
15 MHz.
-105.8 -108.6 2 x 40 304

NOTE
eNodeB
81
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 356 mm x 140
housing)
l 485 mm x 381 mm x 170
mm (31.4 L with the
housing)
l 22 kg (without
the housing)
l 24 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospheric
Pressure
RRU32
03
l 40
C to
+50
C (with
solar
radiation of
1120 W/
m
2
)
l 40
C to
+55
C
(without
solar
radiation)
5% RH to 100% RH
1 g/m
3
to 30 g/m
3
70 kPa to 106 kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3203 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

eNodeB
82
NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability

eNodeB
83
NOTE
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3220 LTE
FDD
DD 800 (band 20) 832 to 847 791 to 806
842 to 862 801 to 821

RF Specifications
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
220
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
-106.1 -108.9 2 x 40 290

NOTE
eNodeB
84
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 400 mm x 220 mm x 140
housing)
l 400 mm x 240 mm x 160
mm (15 L with the
housing)
l 13.5 kg
(without the
housing)
l 15 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospheri
c Pressure
RRU3220
l 40
C to +50
C
(with solar
radiation of 1120
W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3220 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

eNodeB
85
NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
Alarm port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability
RRU3220 Not supported AISG2.0 and AISG1.1
eNodeB
86

NOTE
l When an RRU3220 uses a tower mounted amplifier (TMA), a bias tee (BT) is required.
l If an RRU supports RET antennas, the feeding voltage and feeding current are 12 V and 2.3 A, respectively.
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3221 LTE
FDD
2600 (band 7) 2500 to 2570 2620 to 2690

RF Specifications
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
221
bandwidth of each
carrier can be 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
-106.0 -108.8 2 x 40 370

NOTE
eNodeB
87
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 270 mm x 140
housing)
l 485 mm x 300 mm x 170
mm (25 L with the
housing)
l 20 kg (without
the housing)
l 22 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospher
ic Pressure
RRU3221
l 40
C to +50
C (with
solar radiation of
1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3221 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

eNodeB
88
NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
eNodeB
89
Capability

NOTE
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3222 LTE
FDD
DD 800 (band 20) 832 to 862 791 to 821

RF Specifications
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
222
bandwidth of each
carrier can be 5
MHz, 10 MHz, 15
MHz, or 20MHz.
-106.4 -109.2 2 x 40 310

eNodeB
90
NOTE
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 270 mm x 140
housing)
l 485 mm x 300 mm x 170
mm (25 L with the
housing)
l 17.5 kg
(without the
housing)
l 20 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospheric
Pressure
RRU322
2
l 40
C to +50
C
(with solar
radiation of
1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/m
3
70 kPa to 106
kPa

eNodeB
91
Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3222 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
eNodeB
92
Port Applicatio
n Scenario
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability

NOTE
Type Working
Mode
Frequency Band
(MHz)
RRU3240 LTE FDD 2600 (band 7) 2500 to 2570 2620 to 2690

RF Specifications
eNodeB
93
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
240
bandwidth of each
carrier can be 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
-106.0 -108.8 2 x 40 400

NOTE
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 270 mm x 140
housing)
l 485 mm x 300 mm x 170
mm (25 L with the
housing)
l 20 kg (without
the housing)
l 22 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospher
ic Pressure
RRU3240
l 40
C to +50
C (with
solar radiation of 1120
W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to
100% RH
1 g/m
3
to 30 g/
m
3
70 kPa to
106 kPa

eNodeB
94
Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3240 l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
eNodeB
95
Port Applicatio
n Scenario
Common
mode
5 kA

Antenna Capability
Capability

NOTE
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU380
8
LTE
FDD
AWS (band 4) 1710 to 1755 2110 to 2155
2100 (band 1) 1920 to 1980 2110 to 2170

RF Specifications
eNodeB
96
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
808
bandwidth of each
carrier can 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.
l AWS:
-106.5
l 2100:
-106.5
l AWS:
-109.3
l 2100:
-109.3
2 x 40 320

NOTE
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 270 mm x 140
housing)
l 485 mm x 285 mm x 170
mm (23.5 L with the
housing)
l 17.5 kg
(without the
housing)
l 19 kg (with the
housing)

eNodeB
97
Humidity
Absolute
Humidity
Atmospher
ic Pressure
RRU3808
l 40
C to +50
C (with
W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3808 l 3GPP TS 25.141
l 3GPP TS 36.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
"Non-
weatherprotected
locations"

NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
eNodeB
98
Port Applicatio
n Scenario
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability

NOTE
Supported Modes and Frequency Bands
Table 11-77 lists the modes and frequency bands supported by an RRU3841.
eNodeB
99
Table 11-77 Modes and frequency bands supported by an RRU3841
Type Mode Frequency Band
(MHz)
Receive
Frequency Band
(MHz)
Transmit
Frequency Band
(MHz)
RRU3841 LTE FDD AWS (band 4) 1710 to 1755 2110 to 2155

RF Specifications
Table 11-78 lists radio frequency (RF) specifications of an RRU3841.
Table 11-78 RF specifications of an RRU3841
Type Trans
mit
and
Recei
ve
Chan
nels
(dBm)
Maximu
m Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
841
4T4R One carriers. The
bandwidth of each
carrier can be 5, 10,
15, or 20 MHz.
-106.3 -109.1 For
details, see
Table 3
Output
Power of
an
RRU3841
l 500 W
in the
2T4R
config
uration
l 560 W
in the
4T4R
config
uration

Table 11-79 Output Power of an RRU3841
TX and RX Mode TX RF Port Combination
Mode
Maximum Output Power
(W)
2T2R Port A is used with port B 2 x 60
1T1R Port A or port B 1 x 60
2T4R Port A is used with port B 2 x 60

eNodeB
100
NOTE
Table 11-80 lists the equipment specifications of an RRU3841.
Table 11-80 Equipment specifications of an RRU3841
Type Input Power Dimension (H x W x D) Weight (kg)
RRU3841 -48 V DC; voltage
range: -57 V DC to
-36 V DC
l 480 mm x 356 mm x 140
mm (24 L, without the
housing)
l 485 mm x 380 mm x 170
mm (31 L, with the
housing)
l 24.5 (without
the housing)
l 26 (with the
housing)

Table 11-81 lists the environmental specifications of an RRU3841.
Table 11-81 Environmental specifications of an RRU3841
Type Operating
Temperature
Relative
Humidity
Absolute
Humidity
Atmospheric
Pressure
RRU3841
l -40
C to +50
C
(with solar
radiation of 1120
W/m
2
)
l -40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/m
3
70 kPa to 106
kPa

Table 11-82 lists the compliance standards for an RRU3841.
Table 11-82 Compliance standards for an RRU3841
Type Operating Environment Anti-seismic
Performance
Protection Rating
RRU3841 l 3GPP TS 36.141
l ETSI EN 300019-1-4
V2.1.2 (2003-04) Class
4.1: "Non-
weatherprotected
locations"
eNodeB
101

Table 11-83 lists the surge protection specifications of ports on an RRU3841.
NOTE
l Unless otherwise specified, the surge protection specifications depend on the surge waveform of 8/20 s.
l All the surge current items, unless otherwise specified as Maximum discharge current, refer to Nominal
discharge current.
Table 11-83 Surge protection specifications of ports on an RRU3841
Port Usage
Scenario
DC power
supply port
Applicable
to all
scenarios
Surge Differential
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
Antenna port Applicable
to all
scenarios
Surge
current
Differential
mode
8 kA
Common
mode
40 kA
CPRI port Applicable
to all
scenarios
Surge 250 A
RET antenna
port
Applicable
to all
scenarios
Surge
current
Differential
mode
3 kA
Common
mode
5 kA
Alarm port Applicable
to all
scenarios
Surge
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Table 11-84 lists the antenna capability of an RRU3841.
eNodeB
102
Table 11-84 Antenna capability of an RRU3841
Type TMA Support Supported RET Antennas
RRU3841 Supported AISG2.0 and AISG1.1

NOTE
For RRUs supporting RET antennas, the feeding voltage is 12 V and feeding current is 2.3 A.
RRU3908s are classified into RRU3908 V1 and RRU3908 V2. This section describes the
technical specifications of the RRU3908.
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3908
V1
LTE
FDD
1800 (band 3) 1710 to 1755 1805 to 1850
1740 to 1785 835 to 1880
RRU3908
V2
LTE
FDD
900 (band 8) 880 to 915 925 to 960

RF Specifications
eNodeB
103
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
908
V1
bandwidth of each
carrier can be 5
MHz, 10 MHz, 15
MHz, or 20MHz.
-106.3 -109.1 2 x 30 320
RRU3
908
V2
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
-106.1 -108.9 2 x 40 350

NOTE
Width x Depth)
Weight (kg)
RRU3908
V1
48 V DC; voltage
range: 36 V DC to
57 V DC
l 480 mm x 356 mm x 140
housing)
l 485 mm x 380 mm x 170
mm (31 L with the
housing)
l 21 kg (without
the housing)
l 23 kg (with the
housing)
RRU3908
V2
48 V DC; voltage
range: 36 V DC to
57 V DC
l 480 mm x 356 mm x 140
housing)
l 485 mm x 380 mm x 170
mm (31 L with the
housing)
l 21 kg (without
the housing)
l 23 kg (with the
housing)

eNodeB
104
Humidity
Absolute
Humidity
Atmospheri
c Pressure
RRU3908
V1
l 40
C to +50
C
of 1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa
RRU3908
V2
l 40
C to +50
C
of 1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3908
V1
l 3GPP TS 45.005
l 3GPP TS 25.141
l 3GPP TS 36.141
l 3GPP TS 37.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
Non-
weatherprotected
locations
RRU3908
V2

NOTE
s.
eNodeB
105
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability
RRU3908 V1 TMA supported AISG2.0 and AISG1.1
RRU3908 V2 TMA supported AISG2.0 and AISG1.1

NOTE
eNodeB
106
Type Worki
ng
Mode
Frequency Band
(MHz)
RRU3928 LTE
FDD
900 (band 8) 880 to 915 925 to 960
1800 (band 3) 1710 to 1785 1805 to 1880

RF Specifications
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
928
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
l 900:
-106.3
l 1800:
-106.6
l 900:
-109.1
l 1800:
-109.4
2 x 40 l 900:
320
l 1800:
325

NOTE
eNodeB
107
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 220 mm x 140
housing)
l 485 mm x 340 mm x 160
mm (15 L with the
housing)
l 13.5 kg
(without the
housing)
l 15 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospheri
c Pressure
RRU3928
l 40
C to +50
C (with
solar radiation of
1120 W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to 100%
RH
1 g/m
3
to 30 g/
m
3
70 kPa to 106
kPa

Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3928 l 3GPP TS 45.005
l 3GPP TS 25.141
l 3GPP TS 36.141
l 3GPP TS 37.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
Non-
weatherprotected
locations

eNodeB
108
NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
eNodeB
109
Capability

NOTE
Type Working
Mode
Frequency
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
Type RX
and
TX
Chan
nels
(dBm)
Maximu
m
Output
Power
(W)
Maximu
m Power
Consum
ption (W)
1T1R 1T2R
RRU3
929
bandwidth of each
carrier can be 1.4
MHz, 3 MHz, 5
MHz, 10 MHz, 15
MHz, or 20 MHz.
l 900:
-106.3
l 1800:
-106.6
l 900:
-109.1
l 1800:
-109.4
2 x 60 l 900:
455
l 1800:
465

eNodeB
110
NOTE
Width x Depth)
Weight (kg)
range: 36 V DC to
57 V DC
l 480 mm x 356 mm x 140
housing)
l 485 mm x 380 mm x 170
mm (31 L with the
housing)
l 23.5 kg
(without the
housing)
l 25 kg (with the
housing)

Humidity
Absolute
Humidity
Atmospher
ic Pressure
RRU3929
l 40
C to +50
C (with
W/m
2
)
l 40
C to +55
C
(without solar
radiation)
5% RH to
100% RH
1 g/m
3
to 30 g/
m
3
70 kPa to
106 kPa

eNodeB
111
Type Operating
Environment
Anti-Seismic
Performance
Ingress
Protection (IP)
Rating
RRU3929 l 3GPP TS 45.005
l 3GPP TS 25.141
l 3GPP TS 36.141
l 3GPP TS 37.141
l ETSI EN
300019-1-4 V2.1.2
(2003-04) Class 4.1:
Non-
weatherprotected
locations

NOTE
s.
Port Applicatio
n Scenario
DC power
supply
socket
mode
2 kV (1.2/50 s)
Common
mode
4 kV (1.2/50 s)
Surge
current
Differential
mode
10 kA
Common
mode
20 kA
current
Differential
mode
8 kA
Common
mode
40 kA
eNodeB
112
Port Applicatio
n Scenario
RET port All Surge
current
Differential
mode
3 kA
Common
mode
5 kA
current
Differential
mode
3 kA
Common
mode
5 kA

Antenna Capability
Capability

NOTE
11.4 Engineering Specifications
This section describes engineering specifications of each base station, including input power
specifications, equipment specifications, environment specifications, surge protection
specifications, and standards that have been complied with.
11.4.1 BTS3900 Engineering Specifications
BTS3900 engineering specifications include input power specifications, equipment
specifications, environment specifications, surge protection specifications, and standards that
have been complied with.
Table 11-106 lists the input power specifications of a BTS3900. The BTS3900 (Ver.B) cabinet
supports -48 V DC, +24 V DC, 110 V AC, and 220 V AC power input. The BTS3900 (Ver.C)
and BTS3900 (Ver.D) cabinets support -48 V DC, 110 V AC, and 220 V AC power input.
eNodeB
113
Table 11-106 Input power supported by the BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900
(Ver.D) cabinets
Input Power Voltage Range
-48 V DC -38.4 V DC to -57 V DC
+24 V DC +21.6 V DC to +29 V DC
110 V AC +90 V AC to +135 V AC
200 V AC +176 V AC to +280 V AC

The BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D) cabinets have the same size
and weight, as provided in Table 11-107.
Table 11-107 Equipment specifications of the BTS3900 (Ver.B), BTS3900 (Ver.C), and
BTS3900 (Ver.D) cabinets
Item Specification
Dimension (H x W x D) 900 mm x 600 mm x 450 mm
Weight l 60 kg (empty cabinet)
l 135 kg (full configuration and without
transmission devices)

The BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D) cabinets have the same
environment specifications, as provided in Table 11-108.
Table 11-108 Environment specifications of the BTS3900 (Ver.B), BTS3900 (Ver.C), and
BTS3900 (Ver.D) cabinets
Item Specification
Operating temperature l Long term: -20C to +55C
l Short term: +50C to +55C
NOTE
Short term indicates that a base station does not
work for over 15 days within a year or that a base
station does not continuously work for over 72
hours.
Atmospheric pressure 70 kPa to 106 kPa

eNodeB
114
Surge Protection Specifications
The BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D) cabinets have the same surge
protection specifications, as provided in Table 11-109.
NOTE
discharge current.
Table 11-109 Surge protection specifications of ports on the BTS3900 (Ver.B), BTS3900
(Ver.C), and BTS3900 (Ver.D) cabinets
Port Surge Protection
Mode
Specification
DC power supply port Differential mode 2 kV (1.2/50 s)
Common mode 4 kV (1.2/50 s)
AC power supply port Differential mode 5 kA
Common mode 5 kA

Standards
The BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900 (Ver.D) cabinets comply with the same
standards, as provided in Table 11-110.
Table 11-110 Standards with which the BTS3900 (Ver.B), BTS3900 (Ver.C), and BTS3900
(Ver.D) cabinets comply
Item Standard
Protection rating IP20
Storage ETSI EN300019-1-1 V2.1.4 (2003-04) class1.2 "Weatherprotected,
not temperature-controlled storage locations"
Transportation ETSI EN300019-1-2 V2.1.4 (2003-04) class 2.3 "Public
transportation"
Anti-seismic
performance
IEC 60068-2-57: Environmental testing -Part 2-57: Tests -Test Ff:
Vibration -Time-history method
YD5083: Interim Provisions for Test of Anti-seismic Performances
of Telecommunications Equipment (telecom industry standard in
People's Republic of China)
Anti-earthquake
performance
ETSI EN 300019-1-3: "Earthquake"
eNodeB
115
Item Standard
EMC
NOTE
The BTS3900 complies with the following standards. If interference exists
because the BTS3900 is installed near antennas or other radio receive
devices, you are advised to extend the distance between them or adjust the
location and direction of antennas.
l R&TTE Directive 1999/5/EC
l R&TTE Directive 89/336/EEC
l 3GPP TS 36.113
l ETSI EN 301489-1/23
l ETSI EN 301908-1 V2.2.1 (2003-10)
l ITU-R SM.329-10

11.4.2 BTS3900L Engineering Specifications
BTS3900L engineering specifications include input power specifications, equipment
The BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D) cabinets support the same
power input, as provided in Table 11-111.
Table 11-111 Input power supported by the BTS3900L (Ver.B), BTS3900L (Ver.C), and
BTS3900L (Ver.D) cabinets
-48 V DC -38.4 V DC to -57 V DC

The BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D) cabinets have the same
size and weight, as provided in Table 11-112.
Table 11-112 Equipment specifications of the BTS3900L (Ver.B), BTS3900L (Ver.C), and
Item Specification
Dimension (H x W x D) 1600 mm x 600 mm x 450 mm
eNodeB
116
Item Specification
l 235 kg (full configuration and without
transmission devices)

Table 11-113 Environment specifications of the BTS3900L (Ver.B), BTS3900L (Ver.C), and
Item Specification
NOTE
hours.

surge protection specifications, as provided in Table 11-114.
NOTE
discharge current.
Table 11-114 Surge protection specifications of ports on the BTS3900L (Ver.B), BTS3900L
(Ver.C), and BTS3900L (Ver.D) cabinets
Port Surge Protection
Mode
Specification
DC power supply port Differential mode 2 kV (1.2/50 s)
Common mode 4 kV (1.2/50 s)

eNodeB
117
Standards
The BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L (Ver.D) cabinets comply with the
same standards, as provided in Table 11-115.
Table 11-115 Standards with which the BTS3900L (Ver.B), BTS3900L (Ver.C), and BTS3900L
(Ver.D) cabinets comply
Item Standard
Storage ETSI EN300019-1-1V2.1.4 (2003-04) class1.2 "Weatherprotec-
ted, not temperature-controlled storage locations"
Transportation ETSI EN300019-1-2V2.1.4 (2003-04) class 2.3 "Public
transportation"
Anti-seismic
performance
IEC 60068-2-57: Environmental testing -Part 2-57: Tests -Test
Ff:Vibration -Time-history method
YD5083: Interim Provisions for Test of Anti-seismic
Performances of Telecommunications Equipment (telecom
industry standard in People's Republic of China)
Anti-earthquake
performance
EMC
NOTE
The BTS3900L complies with the following standards. If interference
exists because the BTS3900L is installed near antennas or other radio
receive devices, you are advised to extend the distance between them or
adjust the location and direction of antennas.
l 3GPP TS 36.113
l ETSI EN 301489-1/23
l ETSI EN 301908-1 V2.2.1 (2003-10)
l ITU-R SM.329-10

11.4.3 BTS3900A Engineering Specifications
BTS3900A engineering specifications include input power specifications, equipment
The BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D) cabinets support the same
power input, as provided in Table 11-116
eNodeB
118
Table 11-116 Input power supported by the BTS3900A (Ver.B), BTS3900A (Ver.C), and
BTS3900A (Ver.D) cabinets
-48 V DC -38.4 V DC to -57 V DC
110 V AC +90 V AC to +135 V AC
220 V AC +176 V AC to +280 V AC

Table 11-117 lists the equipment specifications of the BTS3900A (Ver.B), BTS3900A (Ver.C),
and BTS3900A (Ver.D) cabinets.
Table 11-117 Equipment specifications of the BTS3900A (Ver.B), BTS3900A (Ver.C), and
Item Specification
Dimension (H x W x
D)
l APM30H: 700 mm x 600 mm x 480 mm
l RFC: 700 mm x 600 mm x 480 mm
APM30H: 68 kg
RFC: 44 kg
l 194 kg (full configuration and without transmission devices)
APM30H: 87 kg
RFC: 107 kg

The BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D) cabinets have the same
eNodeB
119
Table 11-118 Environment specifications of the BTS3900A (Ver.B), BTS3900A (Ver.C), and
Item Specification
NOTE
hours.

The BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D) cabinets have the same
surge protection specifications, as provided in Table 11-119.
NOTE
discharge current.
Table 11-119 Surge protection specifications of ports on the BTS3900A (Ver.B), BTS3900A
(Ver.C), and BTS3900A (Ver.D) cabinets
Port Usage
Scenario
Surge
Protection
Mode
Specification
-48 V DC output
remote port
Applicable to
all scenarios
Differential
mode
10 kA
Common mode 20 kA
-48 V DC input port Applicable to
the scenario
where
transmission
cabinets,
battery
cabinets, or a
BTS3900A
(DC) is used
Differential
mode
10 kA
Common mode 20 kA
Applicable to
the scenario
where only
Differential
mode
3 kA
eNodeB
120
Port Usage
Scenario
Surge
Protection
Mode
Specification
RFC cabinets
are used
Common mode 5 kA
AC power supply
port
Applicable to
the scenario
where RF
modules are
configured
remotely or
are placed
outdoors
together with
the
correspondin
g base station
Differential
mode
30 kA
Common mode 30 kA

Standards
The BTS3900A (Ver.B), BTS3900A (Ver.C), and BTS3900A (Ver.D) cabinets comply with the
same standards, as provided in Table 11-120.
Table 11-120 Standards with which the BTS3900A (Ver.B), BTS3900A (Ver.C), and
BTS3900A (Ver.D) cabinets comply
Item Standard
Storage ETSI EN300019-1-1V2.1.4 (2003-04) class1.2 "Weatherprotec-
ted, not temperature-controlled storage locations"
Transportation ETSI EN300019-1-2V2.1.4 (2003-04) class 2.3 "Public
transportation"
Anti-seismic
performance
IEC 60068-2-57: Environmental testing -Part 2-57: Tests -Test
Ff:Vibration -Time-history method
YD5083: Interim Provisions for Test of Anti-seismic
Performances of Telecommunications Equipment (telecom
industry standard in People's Republic of China)
Anti-earthquake
performance
eNodeB
121
Item Standard
EMC
NOTE
The BTS3900A complies with the following standards. If interference
exists because the BTS3900A is installed near antennas or other radio
receive devices, you are advised to extend the distance between them or
adjust the location and direction of antennas.
l 3GPP TS 36.113
l ETSI EN 301489-1/23
l ETSI EN 301908-1 V2.2.1 (2003-10)
l ITU-R SM.329-10

11.4.4 DBS3900 Engineering Specifications
DBS3900 engineering specifications include input power specifications, equipment
Table 11-121 lists the input power specifications of a DBS3900.
Table 11-121 Input power specifications of a DBS3900
Item Input Power Voltage Range
baseband unit (BBU) -48 V DC -38.4 V DC to -57 V DC
remote radio unit (RRU) -48 V DC -36 V DC to -57 V DC
APM30H -48 V DC -38.4 V DC to -57 V DC
110 V AC +90 V AC to +135 V AC
220 V AC +176 V AC to +280 V AC

The equipment specifications of a DBS3900 include the following:
l BBU equipment specifications (for details, see 11.1 Technical Specifications for
BBU3900)
l RRU equipment specifications (for details, see 11.3 Technical Specifications of RRUs)
l Related cabinet equipment specifications (for details, see DBS3900 Hardware
Description)
eNodeB
122
The environment specifications of a DBS3900 include the following:
l BBU environment specifications (for details, see 11.1 Technical Specifications for
BBU3900)
l RRU environment specifications (for details, see 11.3 Technical Specifications of
RRUs)
The surge protection specifications of ports on a DBS3900 include the following:
l Surge protection specifications of ports on the BBU (for details, see 11.1 Technical
Specifications for BBU3900)
l Surge protection specifications of ports on a remote radio unit (RRU) (for details, see 11.3
Technical Specifications of RRUs)
Standards
Table 11-122 lists the standards with which a DBS3900 complies.
Table 11-122 Standards with which a DBS3900 complies
Item Standard
Storage ETSI EN300019-1-1V2.1.4 (2003-04) class 1.2 "Weatherprotected, not
temperature-controlled storage locations"
Transpor
tation
ETSI EN300019-1-2V2.1.4 (2003-04) class 2.3 "Public transportation"
Anti-
seismic
performa
nce
IEC 60068-2-57: Environmental testing -Part 2-57:Tests -Test Ff:Vibration -
Time-history method
YD5083: Interim Provisions for Test of Anti-seismic Performances of
Telecommunications Equipment (telecom industry standard in People's Republic
of China)
Anti-
earthqua
ke
performa
nce
eNodeB
123
Item Standard
EMC
NOTE
The DBS3900 complies with the following standards. If interference exists because the
DBS3900 is installed near antennas or other radio receive devices, you are advised to extend
the distance between them or adjust the location and direction of antennas.
l 3GPP TS 36.113
l ETSI EN 301489-1/23
l ETSI EN 301908-1 V2.2.1 (2003-10)
l ITU-R SM.329-10
eNodeB
124

ENodeB Technical Description (V100R003C00 - 14) (PDF) - en

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ENodeB Technical Description (V100R003C00 - 14) (PDF) - en

Caricato da

Copyright:

Formati disponibili

eNodeB

Potrebbero piacerti anche