eNodeB Technical Description (V100R004C00 - 03) (PDF) - EN PDF

eNodeB V100R004C00
Technical Description
Issue Date 03 2011-12-24
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 03 (2011-12-24)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
eNodeB Technical Description
About This Document
About This Document
Purpose
This document provides the LTE-SAE system architecture and the following information about the eNodeB: basic functions, structures, environment monitoring principles, clock synchronization modes, operation and maintenance, reliability, topologies, and typical hardware configurations.
Product Versions
The following table lists the product versions related to this document. Product Name BTS3900 LTE BTS3900A LTE BTS3900L LTE DBS3900 LTE DBS3900 LTE TDD Version V100R004C00 V100R004C00 V100R004C00 V100R004C00 V100R004C00
Intended Audience
The intended audiences of this document are: l l l Network planning engineers Field engineers System engineers
Organization
1 Changes in the eNodeB Technical Description
Issue 03 (2011-12-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ii
About This Document
This chapter describes the changes in the eNodeB Technical Description. 2 LTE-SAE System Architecture This chapter describes the LTE-SAE system architecture, including the position of eNodeBs and the functions of Network Elements (NEs). LTE stands for Long Term Evolution, and SAE stands for System Architecture Evolution. 3 eNodeB Functions This chapter describes the functions of eNodeBs. As the radio access equipment in the LTESAE 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. 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 environment monitoring unit type A (EMUA) alarm. 6 eNodeB Synchronization Modes This chapter describes the clock synchronization modes for eNodeBs. 7 Operation and Maintenance of eNodeBs This chapter describes operation and maintenance of eNodeBs. The operation and maintenance (OM) system of eNodeBs manages, monitors, and maintains the software, hardware, and configuration data of the eNodeBs. In addition, the OM system provides various OM modes to meet requirements. 8 eNodeB Reliability This chapter describes eNodeB reliability, which includes system reliability, hardware reliability, and software reliability. 9 eNodeB Topologies This chapter describes eNodeB topologies on the S1 and CPRI interfaces. 10 Typical Hardware Configurations of an eNodeB This chapter describes the hardware configurations of an eNodeB. 11 Technical Specifications of Radio Frequency Units This chapter describes the technical specifications of radio frequency (RF) units, such as the working mode, frequency band, output power, and antenna capability.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows.
Issue 03 (2011-12-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
Symbol
Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iv
Issue 03 (2011-12-24)
About This Document
Convention { x | y | ... }*
Description 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. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description 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 Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Issue 03 (2011-12-24)
Contents
Contents
About This Document.....................................................................................................................ii 1 Changes in the eNodeB Technical Description.......................................................................1 2 LTE-SAE System Architecture....................................................................................................4 3 eNodeB Functions.........................................................................................................................6 4 eNodeB Structure...........................................................................................................................8
4.1 Logical Structure of the Baseband Unit.............................................................................................................9 4.2 Logical Structure of Radio Frequency Units....................................................................................................10
5 Environment Monitoring Principles........................................................................................14 6 eNodeB Synchronization Modes..............................................................................................18 7 Operation and Maintenance of eNodeBs................................................................................20
7.1 OM Modes........................................................................................................................................................21 7.2 O&M Functions................................................................................................................................................22
8 eNodeB Reliability......................................................................................................................25
8.1 System Reliability.............................................................................................................................................26 8.2 Hardware Reliability.........................................................................................................................................28 8.3 Software Reliability..........................................................................................................................................29
9 eNodeB Topologies.....................................................................................................................31 10 Typical Hardware Configurations of an eNodeB...............................................................39

10.1 Typical Hardware Configurations and Subrack Numbers..............................................................................40 10.2 Hardware Configurations of BTS3900 LTE..................................................................................................45 10.3 Hardware Configurations of BTS3900A LTE................................................................................................48 10.4 Hardware Configurations of BTS3900L LTE................................................................................................51 10.5 Hardware Configurations of DBS3900 LTE..................................................................................................54 10.6 Hardware Configurations of DBS3900 LTE TDD.........................................................................................56
11 Technical Specifications of Radio Frequency Units...........................................................57

11.1 Technical Specifications of RFUs..................................................................................................................58 11.1.1 Technical Specifications of the LRFU..................................................................................................58 11.1.2 Technical Specifications of the LRFUe.................................................................................................60 11.1.3 Technical Specifications of the MRFU.................................................................................................61 Issue 03 (2011-12-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vi
Contents
11.1.4 Technical Specifications of the MRFUd...............................................................................................63 11.2 Technical Specifications of RRUs..................................................................................................................65 11.2.1 Technical Specifications of the RRU3201............................................................................................66 11.2.2 Technical Specifications of the RRU3203............................................................................................69 11.2.3 Technical Specifications of the RRU3220............................................................................................71 11.2.4 Technical Specifications of the RRU3221............................................................................................74 11.2.5 Technical Specifications of the RRU3222............................................................................................77 11.2.6 Technical Specifications of the RRU3240............................................................................................80 11.2.7 Technical Specifications of the RRU3808............................................................................................83 11.2.8 Technical Specifications of the RRU3908............................................................................................86 11.2.9 Technical Specifications of the RRU3928............................................................................................90 11.2.10 Technical Specifications of the RRU3929..........................................................................................93 11.2.11 Technical Specifications of the RRU3232..........................................................................................96
Issue 03 (2011-12-24)
vii
1
03 (2011-12-24)
Changes in the eNodeB Technical Description
This chapter describes the changes in the eNodeB Technical Description.
This is the third official release. Compared with issue 02 (2011-11-15), this issue does not add any topics. Compared with issue 02 (2011-11-15), this issue incorporates the changes described in the following table. Topic 9 eNodeB Topologies Change Description l Deleted the chain topology on the CPRI interface in time division duplex (TDD) mode. l Deleted the description of cascading levels of RRUs.
Compared with issue 02 (2011-11-15), this issue does not delete any topics.
02 (2011-11-15)
This is the second official release. Compared with issue 01 (2011-09-15), this issue adds the following new topic: l 11 Technical Specifications of Radio Frequency Units Compared with issue 01 (2011-09-15), this issue incorporates the changes described in the following table.
Issue 03 (2011-12-24)
Topic 4.2 Logical Structure of Radio Frequency Units 10.2 Hardware Configurations of BTS3900 LTE 10.3 Hardware Configurations of BTS3900A LTE 10.4 Hardware Configurations of BTS3900L LTE 10.5 Hardware Configurations of DBS3900 LTE 10.6 Hardware Configurations of DBS3900 LTE TDD
Change Description Added the description of an RRU and an RFU. Modified the positions of the components of BTS3900 LTE in typical configurations and the hardware configuration descriptions. Modified the positions of the components of BTS3900A LTE in typical configurations and the hardware configuration descriptions. Modified the positions of the components of BTS3900L LTE in typical configurations and the hardware configuration descriptions. Modified the hardware configuration descriptions of the DBS3900 LTE. Modified the hardware configuration descriptions of the DBS3900 LTE TDD.
Compared with issue 01 (2011-09-15), this issue does not delete any topics.
01 (2011-09-15)
This is the first official release. Compared with draft A (2011-07-15), this issue adds the following new topic: l 10.3 Hardware Configurations of BTS3900A LTE Compared with draft A (2011-07-15), this issue incorporates the changes described in the following table. Topic 10.1 Typical Hardware Configurations and Subrack Numbers Change Description l Modified the hardware quantities of a frequency division duplex (FDD) eNodeB in typical configurations. l Modified the hardware quantities of a TDD eNodeB in typical configurations. l Distinguished between Ver.B and Ver.C cabinets. 10.2 Hardware Configurations of BTS3900 LTE l Deleted the hardware configurations of BTS3900A LTE. l Modified the positions of the components of BTS3900 LTE in typical configurations. 10.4 Hardware Configurations of BTS3900L LTE Modified the positions of the components of BTS3900L LTE in typical configurations.
Issue 03 (2011-12-24)
Compared with draft A (2011-07-15), this issue does not delete any topics.
Draft A (2011-07-15)
This is the draft. Compared with issue 04 (2011-06-10) of V100R003C00, this issue includes the new information described in the following table. Topic 8.1 System Reliability Description Added the description of inter-board cell reestablishment, CPRI port redundancy, OM channel backup, and route backup. Added the description of topologies for load sharing.
9 eNodeB Topologies
Compared with issue 04 (2011-06-10) of V100R003C00, this issue incorporates the changes described in the following table. Topic 10.1 Typical Hardware Configurations and Subrack Numbers Change Description l Modified the hardware quantities of an FDD eNodeB in typical configurations. l Modified the hardware quantities of a TDD eNodeB in typical configurations.
Compared with issue 04 (2011-06-10) of V100R003C00, this issue does not delete any topics.
Issue 03 (2011-12-24)
2 LTE-SAE System Architecture
2
Position of eNodeBs
LTE-SAE System Architecture
This chapter describes the LTE-SAE system architecture, including the position of eNodeBs and the functions of Network Elements (NEs). LTE stands for Long Term Evolution, and SAE stands for System Architecture Evolution.
The LTE-SAE system architecture consists of the evolved UMTS terrestrial radio access network (E-UTRAN) and evolved packet core (EPC). Figure 2-1 shows the system architecture. Figure 2-1 LTE-SAE system architecture
E-UTRAN NodeB
Evolved UMTS terrestrial radio access network
Evolved packet core
MME: mobility management entity S-GW: serving gateway
UE: user equipment
As shown in Figure 2-1, one or more eNodeBs constitute an E-UTRAN, enabling UEs to access the LTE-SAE system. An eNodeB communicates with a UE, another eNodeB, or the EPC through the Uu, X2, and S1 interfaces, respectively.
Issue 03 (2011-12-24)
2 LTE-SAE System Architecture
Functions of NEs
The NEs in the LTE-SAE system include eNodeBs, MMEs, and S-GWs. Table 2-1 describes the functions of the NEs. Table 2-1 Functions of the NEs in the LTE-SAE system NE eNodeB Function l Radio resource management, including radio bearer control, radio admission control, connection mobility control, and scheduling resource l Packet compression and ciphering l Routing of user plane packets towards an S-GW l MME selection l Scheduling and transmission of messages, including 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
Issue 03 (2011-12-24)
3 eNodeB Functions
3
Radio Resource Management
l l l l
eNodeB Functions
This chapter describes the functions of eNodeBs. As the radio access equipment in the LTESAE system, eNodeBs perform radio resource management, packet compression and ciphering, user plane packet routing, MME selection, and message scheduling and transmission.
Radio resource management covers radio bearer control, admission control, mobility management, and dynamic resource allocation: Radio bearer control involves setup, maintenance, and release of radio bearers and resource configuration for radio bearers. Admission control accepts or rejects radio bearer setup requests. Mobility management involves management of radio resources for UEs in idle mode and UEs in connected mode. 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 l Header compression for downlink packets and header decompression for uplink packets using compression algorithms 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 l
Issue 03 (2011-12-24)
Selection of an MME for a UE during the Attach procedure of the UE Reselection of an MME for a UE when the UE is in a network
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6
3 eNodeB Functions
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 l Reception of paging messages and broadcast information from an MME and operation and maintenance (O&M) messages from the operation and maintenance center (OMC) Transmission of paging messages, broadcast information, and O&M messages over the Uu interface according to specific scheduling rules
Issue 03 (2011-12-24)
4 eNodeB Structure
4
About This Chapter
eNodeB Structure
This chapter describes the structure of an eNodeB. 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 the Baseband Unit The baseband unit BBU3900 consists of four logical subsystems: control, transport, baseband, and power and environment monitoring. 4.2 Logical Structure of Radio Frequency Units A radio frequency (RF) unit consists of logical components such as the common public radio interface (CPRI) module, transceiver (TRX), power module, power amplifier (PA), low noise amplifier (LNA), filter, and circulator.
Issue 03 (2011-12-24)
4 eNodeB Structure
4.1 Logical Structure of the Baseband Unit

The baseband unit 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 and transmission unit (LMPT). This subsystem performs operation and maintenance (O&M) functions, processes signaling, and provides the system clock. It manages the entire eNodeB. l l The OM functions include configuration management, fault management, performance management, security management, and deployment. The signaling includes Packet Data Convergence Protocol (PDCP) signaling on the Uu interface and Stream Control Transmission Protocol (SCTP) signaling on the S1 and X2 interfaces. The system clock can be one of the following types: Global Positioning System (GPS), Remote Global Positioning System (RGPS), IEEE 1588 V2, synchronous Ethernet, clock over IP, 1 pulse per second (PPS)+time of day (TOD), building integrated timing supply (BITS), and E1/T1.
Transport Subsystem
The functions of the transport subsystem are implemented by the LMPT and universal transmission processing units (UTRPs), which support IP over FE/GE and IP over E1/T1, respectively. The transport subsystem performs the following functions:
Issue 03 (2011-12-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9
4 eNodeB Structure
l l
Provides ports for communication between the eNodeB and the evolved packet core (EPC). Provides the O&M channel between the eNodeB and the local maintenance terminal (LMT) or M2000.
Baseband Subsystem
The functions of the baseband subsystem are implemented by LTE baseband processing units (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 radio frequency (RF) units. l Based on the uplink scheduling instruction, 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 mobility management entity (MME) or serving gateway (S-GW) through the transport subsystem. In addition, the module performs measurements on uplink channels. Based on the downlink scheduling instruction, 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 multiplexing (OFDM) processing, and then transmits the signals over the CPRI interface. 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 universal power and environment interface unit (UPEU) and environment monitoring units. The power and environment monitoring subsystem performs the following functions: l l l Supplies power to BBU3900. Monitors the power status of BBU3900. Provides ports for connections to environment monitoring units and receives and forwards signals from the environment monitoring units.
4.2 Logical Structure of Radio Frequency Units

A radio frequency (RF) unit consists of logical components such as the common public radio interface (CPRI) module, transceiver (TRX), power module, power amplifier (PA), low noise amplifier (LNA), filter, and circulator. An RF unit can be an remote radio unit (RRU) or radio frequency unit (RFU). 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 a frequency division duplex (FDD) RRU or RFU.
4 eNodeB Structure
Figure 4-2 Logical structure of an FDD RRU or RFU
Figure 4-3 shows the logical structure of a time division duplex (TDD) RRU. Figure 4-3 Logical structure of a TDD RRU
Issue 03 (2011-12-24)
11

NOTE
4 eNodeB Structure
In the preceding figures, m denotes the number of PAs, and n denotes the number of LNAs. For example, in the logical structure of an RRU with 2T4R, m and n are equal to 2 and 4, respectively.
CPRI Module
A CPRI module performs the following functions: l l l Receives downlink baseband data from BBU3900. Transmits uplink baseband data to BBU3900. Forwards the data sent from the cascaded RRUs.
TRX
A TRX provides receive (RX) and transmit (TX) channels. l The TRX performs the following functions at an RX channel: Down-converts the received signals to intermediate frequency (IF) signals. Amplifies the IF signals. Performs analog-to-digital conversion. Performs digital down-conversion. Performs matched filtering. Performs channel filtering. Performs automatic gain control. l The TRX performs the following functions at a TX channel: Performs deframing of In-phase or Quadrature (I/Q) signals on the CPRI interface. Performs the following functions on the downlink IQ signals: filtering, digital-to-analog conversion, up-conversion, power amplification, and RF filtering. Reports TX power. Provides overload protection for PAs. Shuts down and opens the TX channel. Provides the closed-loop power control function.
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.
Filter
A filter multiplexes RX and TX signals over RF channels so that they can share an antenna path. In addition, the filter performs filtering of RX and TX signals.
4 eNodeB Structure
Circulator
A circulator is used by a TDD RRU for switching between uplink and downlink transmissions of RF signals.
Issue 03 (2011-12-24)
13
5 Environment Monitoring Principles
5
Ports on a UPEU
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 environment monitoring unit type A (EMUA) alarm.
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, status of power supply units (PSUs) 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 equipped 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 EMUA, which is an environment monitoring device outside an APM30H cabinet, for centralized monitoring of environment outside the APM30H cabinet.
The EMUA is 1 U high. It can be installed in a 19-inch-wide rack or cabinet with its depth exceeding 300 mm. 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 are collectively called peer alarm devices in the subsequent sections. The devices can be dry contacts, sensors, and EMUAs.
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 DBS3900 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 EXTALM1 port.
Table 5-1 Pin assignment for wires of the BBU alarm cable Alarm Port EXTALM0 X1 End X1.1 X1.2 X1.3 X1.6 X1.5 X1.4 X1.7 X2 End X2.1 X2.2 X2.3 X2.6 X2.5 X2.4 X2.7 Wire Color Orange and white Orange Green and white Green Blue and white Blue Brown and white Description Positive Boolean input 1 Negative Boolean input 1 (GND) Positive Boolean input 2 Negative Boolean input 2 (GND) Positive Boolean input 3 Negative Boolean input 3 (GND) Positive Boolean input 4 Twisted pair Twisted pair Twisted pair Pin Assignment Twisted pair
Issue 03 (2011-12-24)
15
Alarm Port
X1 End X1.8
X2 End X2.8 X2.1 X2.2 X2.3 X2.6 X2.5 X2.4 X2.7 X2.8
Wire Color Brown Orange and white Orange Green and white Green Blue and white Blue Brown and white Brown
Description Negative Boolean input 4 (GND) Positive Boolean input 5 Negative Boolean input 5 (GND) Positive Boolean input 6 Negative Boolean input 6 (GND) Positive Boolean input 7 Negative Boolean input 7 (GND) Positive Boolean input 8 Negative Boolean input 8 (GND)
Pin Assignment
EXTALM1
X1.1 X1.2 X1.3 X1.6 X1.5 X1.4 X1.7 X1.8
Twisted pair
Twisted pair
Twisted pair
Twisted pair
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 DBS3900 Installation Guide. In a radio frequency cabinet (RFC), connect one end of a monitoring signal cable between the CMUA and the BBU to the MON0 port on the UPEU and the other end of the cable to the COM_IN port on the CMUA. For details about how to install the cable, see the BTS3900A Installation Guide. In a BTS3900 cabinet, connect one end of a monitoring signal cable for the power and environment monitoring unit (PMU) to the MON0 port on the UPEU and the other end of the cable to the COM port on the PMU. In addition, connect one end of a monitoring signal cable for the FAN unit to the MON1 port on the UPEU and the other end of the cable to
Issue 03 (2011-12-24)
the COM IN port on the FAN unit. For details about how to install the cable, see the BTS3900 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, install 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.
Issue 03 (2011-12-24)
17
6 eNodeB Synchronization Modes
6
l l
eNodeB Synchronization Modes
This chapter describes the clock synchronization modes for eNodeBs. Two or more signals reach synchronization if the phase or frequency deviation falls within a specified range at a valid instant. There are two types of synchronization: frequency synchronization and time synchronization. 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. 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. UTC is a universal timing standard, in which the atomic clock is maintained accurately to ensure time synchronization worldwide, with a precision of microseconds.
The subsequent sections describe reference clocks. For details about clock synchronization, see the Synchronization Feature Parameter Description.
GPS/RGPS Clock
Synchronization with a Global Positioning System (GPS) or Remote Global Positioning System (RGPS) clock requires that each eNodeB be equipped with a GPS or RGPS receiver. Using the receiver, the eNodeB can receive 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 available. To implement synchronization with an RGPS clock, the eNodeB must be equipped with a universal satellite card and clock unit (USCU).
IEEE 1588 V2 Clock

IEEE 1588 defines the Precision Time Protocol (PTP), which targets synchronization of clocks in the Ethernet, with the precision to microseconds. In synchronization with an IEEE 1588 V2 clock, both frequency synchronization and time synchronization are available. To implement this type of synchronization, eNodeBs must be connected to reference clocks, such as Huawei IPCLK1000.
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
6 eNodeB Synchronization Modes
to eNodeBs based on a server/client architecture. In synchronization with a clock over IP, only frequency synchronization is available, with the frequency accuracy lower than 0.05 parts per million (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 available, with the frequency accuracy lower than 0.05 ppm.
1 PPS+TOD Clock
In synchronization with a 1 PPS+TOD clock, an eNodeB obtains the 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. To implement synchronization with a 1 PPS clock, the eNodeB must be equipped with a USCU.
BITS Clock
In synchronization with a building integrated timing supply (BITS) clock, an 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 by 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, an eNodeB obtains frequency synchronization signals from the physical layer of E1/T1 lines. This clock synchronization mode is available 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 universal transmission processing unit (UTRP).
Issue 03 (2011-12-24)
19
7 Operation and Maintenance of eNodeBs
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 O&M Functions This section describes the O&M functions of eNodeBs, covering configuration management, fault management, performance management, security management, software management, deployment management, equipment management, and inventory management.
Issue 03 (2011-12-24)
20
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 l In local OM mode, maintenance personnel use the Local Maintenance Terminal (LMT) to operate and maintain a single eNodeB. 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 l LMT: is mainly used to assist eNodeB deployment, identify faults, and rectify faults locally. 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. 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.
Issue 03 (2011-12-24)
21
Table 7-1 OM software Software iManager M2000 Function 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 O&M Functions

This section describes the O&M 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 the M2000. The data configuration is based on Managed Objects (MOs) of the following categories: device, transport, and service. These categories are independent of each other. Generally, modifications of the service configuration do not require modifications of the device configuration, and modifications of the device configuration do not require modifications of the service configuration either.
Fault Management
Fault management includes fault detection, fault isolation and self-healing, alarm reporting, and alarm correlation. The faults might be related to hardware, environment, software, transmission, cells, and different types of services in cells. l Fault isolation and self-healing bring the following advantages: (1) prevents a fault in some part of an eNodeB from affecting the entire eNodeB. (2) re-establishes a cell of lower specifications to minimize the impact of the fault on services.
Issue 03 (2011-12-24)
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, 30, or 60 minutes. eNodeBs 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.
Tracing Management
Message tracing management traces interfaces, signaling links, UEs, and internal messages for routine maintenance, commissioning, and fault diagnosis.
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 element management system (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 l l l Encryption: encryption of important user information Authentication: management of user accounts and authentication of users Access control: control of operation access Security protocol: support for SSL and IPSec
Software Management
Software management includes software version management, software version upgrade, and patch management. l l Software version management involves query, backup, and restore of software versions. Software version upgrade can be performed on a batch of eNodeBs remotely. With the oneclick upgrade wizard provided by the 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.
Issue 03 (2011-12-24)
Patch management includes query, download, loading, activation, deactivation, rollback, confirmation, and removal of patches.
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 l By using automatic discovery of eNodeBs, users do not need to set the IP addresses of the eNodeBs and EMS. 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. During remote deployment, software commissioning is performed in the operation and maintenance center (OMC) rather than on site. Customers can perform acceptance tests on the eNodeB deployment in the OMC.
Equipment Management
Equipment management includes data configuration, status management, and fault detection and handling for all the devices in an eNodeB. On the device panel, users can view the device status and perform blocking, reset, and switchover.
Inventory Management
Inventory management includes collection and reporting of the inventory information about eNodeBs. With inventory management, users can manage network equipment (NE) assets in the OMC in a centralized manner.
Issue 03 (2011-12-24)
24
8 eNodeB Reliability
8
About This Chapter
eNodeB Reliability
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 following schemes: intra-board baseband resource pool, inter-board cell reestablishment, LMPT cold redundancy, common public radio interface (CPRI) port redundancy, RRU channel cross-connection under multiple-input multiple output (MIMO), operation and maintenance (OM) channel backup, and route backup. 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, data, and boards and by the powerful tolerance of software errors.
Issue 03 (2011-12-24)
25
8.1 System Reliability

System reliability is ensured by using the following schemes: intra-board baseband resource pool, inter-board cell reestablishment, LMPT cold redundancy, common public radio interface (CPRI) port redundancy, RRU channel cross-connection under multiple-input multiple output (MIMO), operation and maintenance (OM) channel backup, and route backup.
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 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. 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.
Inter-Board Cell Reestablishment

Inter-board cell reestablishment is designed to enable mutual backup between LBBPs. If errors occur in a cell because of the relevant LBBP is faulty, the eNodeB checks whether resources are available on another LBBP that is connected to the RRU providing the cell. If resources meet the relevant conditions, the eNodeB reestablishes the cell on the LBBP that provides available resources. The cell can be restored within 20 seconds.
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.
CPRI Port Redundancy

CPRI port redundancy can be classified into hot redundancy and cold redundancy. In hot redundancy of CPRI ports, an RRU is connected to two CPRI ports on different LBBPs to form a hot ring topology. In this topology, two CPRI links transmit identical service data, but the 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 interruption time of 20s.
In cold redundancy of CPRI ports, an RRU is connected to two CPRI ports to form a cold ring topology. The two CPRI ports are provided by either one or two LBBPs. In this topology, only one CPRI link transmits service data. If a CPRI port or LBBP is faulty, the cell is reestablished, with an interruption time of shorter than 20s.
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. Figure 8-1 Cross-connections between RRUs and antennas under MIMO and data streams
Issue 03 (2011-12-24)
27
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. 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. If RRU 0 shown in Figure 8-1 is faulty, user plane data of sector 0 can be exchanged through RRU 1.
l l
OM Channel Backup
An OM channel, also called OM interface, connects an eNodeB and the M2000. OM channel backup enhances reliability. The M2000 detects channel connectivity by employing the handshake mechanism at the application layer, and the eNodeB checks channel connectivity based on results of handshakes with the M2000. If the M2000 detects that the active channel is disconnected, the M2000 initiates a channel switchover through the standby channel, instructing the eNodeB to perform the switchover. The eNodeB automatically switches from the route for the active channel to the route for the standby channel.
Route Backup
Route backup enhances transmission reliability. Primary and secondary routes are two routes with the same destination address but different next-hop IP addresses. The primary/secondary roles of two routes are determined by route priorities. A high priority represents the primary route, and a low priority represents the secondary route. An eNodeB selects a reachable route and, if both routes are reachable, the primary route to send packets. Figure 8-2 shows an example of route backup. In the figure, the IP addresses are port IP addresses. Figure 8-2 Route backup
8.2 Hardware Reliability

Hardware reliability is ensured by the anti-misinsertion design of boards, overtemperature protection, reliable power supply, and surge protection design.
Issue 03 (2011-12-24)
28
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.
Overtemperature Protection
When the temperature near the power amplifier (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 l l l Support for wide-range voltages and surge protection Power failure protection for programs and data Protection of power supply against overvoltage, overcurrent, and reverse connection of positive and negative poles on boards Support for a maximum configuration of two UPEUs in an eNodeB to provide 1+1 redundancy
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, data, and boards and by the powerful tolerance of software errors.
Redundancy
To ensure proper operation of the eNodeB when errors occur in these files and data, the eNodeB provides the following redundancy functions: l Redundancy of software versions: An eNodeB stores software versions, including the BootROM version, in different areas to provide redundancy. If a current version is abnormal, the eNodeB switches to the backup version. Redundancy of data configuration files: An eNodeB stores data configuration files in different areas to provide redundancy. If a current file is damaged, the eNodeB can continue working properly by loading the backup file. 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 Capability

When software errors occur, the eNodeB will not collapse, because of its self-healing capability. The software error tolerance covers the following aspects:
Scheduled checks of key resources: The eNodeB performs occupancy checks on software resources. If resource hang-up occurs in an eNodeB due to software errors, the eNodeB can release the unavailable resources and export logs and alarms. Task monitoring: When software is running, the eNodeB checks for internal software errors and some hardware faults by monitoring processes and tasks. When an error occurs, an alarm is reported and self-healing measures are taken to restore the task. Data check: The eNodeB performs scheduled or event-triggered data consistency checks and restores data consistency selectively or preferentially. In addition, the eNodeB generates related logs and alarms. Watchdog: The eNodeB can detect software errors by using software and hardware watchdogs. When an error is detected, the eNodeB resets automatically.
Issue 03 (2011-12-24)
30
9 eNodeB Topologies
9
Topologies on the S1 Interface
eNodeB Topologies
This chapter describes eNodeB topologies on the S1 and CPRI interfaces.
eNodeBs support the star, chain, and tree topologies on the S1 interface. Figure 9-1 shows the topologies.
Issue 03 (2011-12-24)
31
9 eNodeB Topologies
Figure 9-1 Topologies on the S1 interface
Table 9-1 describes the characteristics of the three topologies.
Issue 03 (2011-12-24)
32
9 eNodeB Topologies
Table 9-1 Topologies on the S1 interface Topol ogy Star topolo gy Advantage l Each eNodeB is connected directly to an MME through a transport network. Therefore, this simple topology features easy engineering, maintenance, and capacity expansion. l Each eNodeB exchanges data with the MME directly. Signals travel through only a few nodes, and therefore network reliability is high. Chain topolo gy The costs of transport equipment, engineering, and transport line lease are relatively low. l Signals travel through many nodes, and therefore network reliability is low. l Each lower-level eNodeB occupies some transmission bandwidth of its upper-level eNodeB. Reliability of the upper-level eNodeB affects operation of the lower-level eNodeB. Tree topolo gy The costs of transport equipment, engineering, and transport line lease are relatively low. l Signals travel through many nodes, and therefore network reliability is low. l Each lower-level eNodeB occupies some transmission bandwidth of its upper-level eNodeB. Reliability of the upper-level eNodeB affects operation of the lower-level eNodeB. Disadvantage Compared with the other two topologies, the star topology requires more transport resources.
Topologies on the CPRI Interface

Frequency division duplex (FDD) RRUs support the following topologies: star, chain, hot backup ring, intra-board cold backup ring, and inter-board cold backup ring. RFUs support the star and hot backup ring topologies. Time division duplex (TDD) RRUs support the star topologies and the topologies for intra-board load sharing and inter-board load sharing.
NOTE
l The CPRI rate is adaptive between 2.5 Gbit/s and 4.9 Gbit/s. l The distance between BBU3900 and the farthest RRU in a CPRI chain cannot exceed 20 km.
Figure 9-2 shows the star topology.
Issue 03 (2011-12-24)
33
9 eNodeB Topologies
Figure 9-2 Star topology
Figure 9-3 shows the chain topology. Figure 9-3 Chain topology
Figure 9-4 shows the hot backup ring topology.
Issue 03 (2011-12-24)
34
9 eNodeB Topologies
Figure 9-4 Hot backup ring topology
Figure 9-5 shows the intra-board cold backup ring topology. Figure 9-5 Intra-board cold backup ring topology
Figure 9-6 shows the inter-board cold backup ring topology.
Issue 03 (2011-12-24)
35
9 eNodeB Topologies
Figure 9-6 Inter-board cold backup ring topology
Figure 9-7 shows the topology for intra-board load sharing. Figure 9-7 Topology for intra-board load sharing
Figure 9-8 shows the topology for inter-board load sharing.
Issue 03 (2011-12-24)
36
9 eNodeB Topologies
Figure 9-8 Topology for inter-board load sharing
Table 9-2 describes the characteristics of various topologies. Table 9-2 Topologies on the CPRI interface To pol og y Sta r top olo gy Advantage Disadvantage Remarks
l This topology features high reliability. Faults in an RRU/RFU or optical fiber affect one sector at most. l This simple topology facilitates installation and maintenance.
This topology requires a relatively large amount of transport resources.
Ch ain top olo gy
This topology requires relatively low costs of transport equipment.
l Limitations are applied to the number of levels in a chain and the distance between units in a chain. l Any fault on the forwarding link of an upper-level RRU affects the operations of its lower-level RRUs.
l Cascading between an RFU and an RRU is not supported. l A chain supports only one rate at a time, because interconnected CPRI ports on two RRUs in a chain must work at the same rate.
Issue 03 (2011-12-24)
37
9 eNodeB Topologies
To pol og y Rin g top olo gy
Advantage
Disadvantage
Remarks
This topology provides high transmission reliability.
l Limitations are applied to the number of levels in a ring and the distance between units in a ring. l Any fault on the forwarding link of an upper-level RRU affects the operations of its lower-level RRUs. If a fault occurs, services carried on the lowerlevel RRUs restore in reverse direction of the ring. The maximum interruption duration is 20 minutes.
The ring topology is a redundancy type of the chain topology.
To pol ogy for loa d sha rin g
l This topology provides high transmission reliability. l A relatively large bandwidth of a cell is supported at CPRI ports.
This topology requires a relatively large amount of transport resources.
Issue 03 (2011-12-24)
38
10 Typical Hardware Configurations of an eNodeB
10
Typical Hardware Configurations of an eNodeB
About This Chapter

This chapter describes the hardware configurations of an eNodeB. 10.1 Typical Hardware Configurations and Subrack Numbers This section describes the typical hardware configurations and the mapping between hardware components and their subrack numbers. 10.2 Hardware Configurations of BTS3900 LTE This section describes the positions and types of the components of BTS3900 LTE in typical configurations. 10.3 Hardware Configurations of BTS3900A LTE This section describes the positions and types of the components of BTS3900A LTE in typical configurations. 10.4 Hardware Configurations of BTS3900L LTE This section describes the positions and types of the components of BTS3900L LTE in typical configurations. 10.5 Hardware Configurations of DBS3900 LTE This section describes the hardware configurations of DBS3900 LTE in typical cases. 10.6 Hardware Configurations of DBS3900 LTE TDD This section describes the hardware configurations of DBS3900 LTE TDD in typical cases.
Issue 03 (2011-12-24)
39
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 a frequency division duplex (FDD) eNodeB in typical configurations. Table 10-2 lists the number of components of a time division duplex (TDD) eNodeB in typical configurations. Table 10-1 Hardware quantities of an FDD eNodeB in typical configurations Configuration 3 x 5 MHz/10 MHz 3 x 15 MHz/20 MHz 6 x 5 MHz/10 MHz 6 x 5 MHz/10 MHz 3 x 15 MHz/20 MHz MIMO 4 x 2 MIMO 4 x 2 MIMO 2 x 2 MIMO 2 x 2 MIMO 2 x 2 MIMO Quantity of LBBPs 1 3 1 2 1 Quantity of RRUs/ RFUs 6 6 6 12 (MRFUs) 3 Or 6, if MRFUs are required 3 x 5 MHz/10 MHz 2 x 2 MIMO 1 6 (MRFUs)
Table 10-2 Hardware quantities of a TDD eNodeB in typical configurations Configuration 3 x 10 MHz 3 x 10 MHz 3 x 20 MHz 3 x 20 MHz 3 x 10 MHz 3 x 20 MHz MIMO 2 x 2 MIMO 4 x 2 MIMO 2 x 2 MIMO 4 x 2 MIMO 4T4R beamforming 4T4R beamforming Quantity of LBBPs 1 1 1 3 1 3 Quantity of RRUs 3 3 3 3 3 3
Issue 03 (2011-12-24)
40

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

Subrack numbers are defined for components of an eNodeB for operation, administration, and maintenance. l l l The fan monitoring unit (FMU) shown in the following figures is the name of the FAN unit used in operation and maintenance. 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. The subrack number of the BBU3900 components is the same as the subrack number of BBU3900.
Table 10-3 lists the mapping between eNodeB models and cabinets. Table 10-4 shows the subrack numbers of cabinets. Table 10-3 Mapping between eNodeB models and cabinets eNodeB Model BTS3900 LTE BTS3900L LTE BTS3900A LTE Cabinet Used BTS3900 (Ver.B) and BTS3900 (Ver.C) cabinets BTS3900L (Ver.B) and BTS3900L (Ver.C) cabinets APM30H (Ver.B), APM30H (Ver.C), RFC (Ver.B), RFC (Ver.C), TMC11H (Ver.B), TMC11H (Ver.C), IBBS200D/IBBS200T (Ver.B), and IBBS200D/IBBS200T (Ver.C) cabinets APM30H (Ver.B), APM30H (Ver.C), TMC11H (Ver.B), TMC11H (Ver.C), IBBS200D/IBBS200T (Ver.B), and IBBS200D/IBBS200T (Ver.C) cabinets APM30H (Ver.B), APM30H (Ver.C), TMC11H (Ver.B), TMC11H (Ver.C), IBBS200D/IBBS200T (Ver.B), and IBBS200D/IBBS200T (Ver.C) cabinets
DBS3900 LTE
DBS3900 LTE TDD
Issue 03 (2011-12-24)
41
Table 10-4 Subrack numbers Cabinet BTS3900 (Ver.B) and BTS3900 (Ver.C) cabinets Subrack Number
Issue 03 (2011-12-24)
42
Cabinet BTS3900L (Ver.B) and BTS3900L (Ver.C) cabinets
Subrack Number
Issue 03 (2011-12-24)
43
Cabinet APM30H (Ver.B) and APM30H (Ver.C) cabinets
Subrack Number
RFC (Ver.B) and RFC (Ver.C) cabinets
Issue 03 (2011-12-24)
44
Cabinet TMC11H (Ver.B) and TMC11H (Ver.C) cabinets
Subrack Number
IBBS200D/ IBBS200T (Ver.B) and IBBS200D/ IBBS200T (Ver.C) cabinets
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.
Issue 03 (2011-12-24)
45
Figure 10-1 Positions of the components of BTS3900 LTE in typical configurations
35MHz/10MHz 42 MIMO 315MHz/20MHz 42 MIMO LMPT LBBPc LRFU
65MHz/10MHz 22 MIMO 315MHz/20MHz 22 MIMO
Hardware Configurations
Figure 10-2, Figure 10-3, and Figure 10-4 show the hardware configurations of BTS3900 LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.
Issue 03 (2011-12-24)
46
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.
Issue 03 (2011-12-24)
47
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.
Issue 03 (2011-12-24)
48
Figure 10-5 Positions of the components of BTS3900A LTE in typical configurations
35MHz/10MHz 42 MIMO 315MHz/20MHz 42 MIMO LMPT LBBPc LRFU
Figure 10-6, Figure 10-7, and Figure 10-8 show the hardware configurations of BTS3900A LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.
Issue 03 (2011-12-24)
49
Figure 10-6 Hardware configuration of BTS3900A LTE in the case of 3 x 15 MHz/20 MHz, 2 x 2 MIMO
NOTE
Issue 03 (2011-12-24)
50
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.
Issue 03 (2011-12-24)
51
Figure 10-9 Positions of the components of BTS3900L LTE in typical configurations
35MHz/10MHz 42 MIMO 315MHz/20MHz 42 MIMO 65MHz/10MHz 22 MIMO LMPT LBBPc LRFU MRFU
Issue 03 (2011-12-24)
52
Figure 10-10, Figure 10-11, and Figure 10-12 show the hardware configurations of BTS3900L LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO. 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
Issue 03 (2011-12-24)
53
Figure 10-12 Hardware configuration of BTS3900L LTE in the case of 3 x 5 MHz/10 MHz, 4 x 2 MIMO
10.5 Hardware Configurations of DBS3900 LTE

This section describes the hardware configurations of DBS3900 LTE in typical cases. Figure 10-13, Figure 10-14, and Figure 10-15 show the hardware configurations of DBS3900 LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO. Figure 10-13 Hardware configuration of DBS3900 LTE in the case of 3 x 15 MHz/20 MHz, 2 x 2 MIMO
Issue 03 (2011-12-24)
54
Figure 10-14 Hardware configuration of DBS3900 LTE in the case of 6 x 5 MHz/10 MHz, 2 x 2 MIMO
Figure 10-15 Hardware configuration of DBS3900 LTE in the case of 3 x 5 MHz/10 MHz, 4 x 2 MIMO
Issue 03 (2011-12-24)
55
10.6 Hardware Configurations of DBS3900 LTE TDD

This section describes the hardware configurations of DBS3900 LTE TDD in typical cases. Figure 10-16 and Figure 10-17 show the hardware configurations of DBS3900 LTE TDD in the following cases: (1) 3 x 20 MHz, 2 x 2 MIMO; (2) 3 x 20 MHz, 4 x 2 MIMO. Figure 10-16 Hardware configuration of DBS3900 LTE TDD in the case of 3 x 20 MHz, 2 x 2 MIMO
Figure 10-17 Hardware configuration of DBS3900 LTE TDD in the case of 3 x 20 MHz, 4 x 2 MIMO
Issue 03 (2011-12-24)
56
11 Technical Specifications of Radio Frequency Units
11
Technical Specifications of Radio Frequency Units
About This Chapter

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

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

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

Table 11-1 describes the working mode and frequency bands of the LRFU. Table 11-1 Working mode and frequency bands of the LRFU Type Worki ng Mode LTE FDD Frequency Band (MHz) AWS (band 4) 2600 (band 7) RX Band (MHz) TX Band (MHz)
LRFU
1710 to 1755 Band C: 2500 to 2520 Band D: 2510 to 2560 Band E: 2550 to 2570
2110 to 2155 Band C: 2620 to 2640 Band D: 2630 to 2680 Band E: 2670 to 2690
RF Specifications
Table 11-2 describes the RF specifications of the LRFU. Table 11-2 RF specifications of the LRFU Type LRFU RX and TX Channels 2T2R Capacity An LRFU supports one carrier. The bandwidth of each carrier can be: l 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz in the AWS band l 5 MHz, 10 MHz, 15 MHz, or 20 MHz in the 2600 MHz band Output Power 2 x 40 W
NOTE
A x B W indicates that the eNodeB uses A transmit (TX) channels and the output power of each channel is B W.
Issue 03 (2011-12-24)
58
Surge Protection Specifications

Table 11-3 describes the surge protection specifications for the ports on the LRFU.
NOTE
l Unless otherwise specified, the surge protection specifications are based on the surge waveform of 8/20 s. l All the items of discharge current, unless otherwise specified as the maximum discharge current, refer to those of the nominal discharge current.
Table 11-3 Surge protection specifications for the ports on the LRFU Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Antenna port All Surge current Differential mode Common mode Monitoring port All Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 3 kA 5 kA
Antenna Capability
Table 11-4 describes the antenna capability of the LRFU. Table 11-4 Antenna capability of the LRFU Type LRFU TMA Support Capability TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
Issue 03 (2011-12-24)
59

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

This section describes the technical specifications of the LRFUe.

Table 11-5 describes the working mode and frequency bands of the LRFUe. Table 11-5 Working mode and frequency bands of the LRFUe Type Worki ng Mode LTE FDD Frequency Band (MHz) DD 800MHz (band 20) RX Band (MHz) TX Band (MHz)
LRFUe
832 to 862
791 to 821
RF Specifications
Table 11-6 describes the RF specifications of the LRFUe. Table 11-6 RF specifications of the LRFUe Type LRFUe RX and TX Channels 2T2R Capacity An LRFUe supports two carriers. The bandwidth of each carrier can be 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed 30MHz. Output Power 2 x 60 W
NOTE

Table 11-7 describes the surge protection specifications for the ports on the LRFUe.
NOTE
Issue 03 (2011-12-24)
60
Table 11-7 Surge protection specifications for the ports on the LRFUe Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Antenna port All Surge current Differential mode Common mode Monitoring port All Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 3 kA 5 kA
Antenna Capability
Table 11-8 describes the antenna capability of the LRFUe. Table 11-8 Antenna capability of the LRFUe Type LRFUe TMA Support Capability TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
NOTE
11.1.3 Technical Specifications of the MRFU

This section describes the technical specifications of the MRFU.

Table 11-9 describes the working mode and frequency bands of the MRFU.
Table 11-9 Working mode and frequency bands of the MRFU Type Worki ng Mode LTE FDD Frequency Band (MHz) 900 (band 8) 1800 (band 3) RX Band (MHz) TX Band (MHz)
MRFU
880 to 915 1710 to 1770 1725 to 1785
925 to 960 1805 to 1865 1820 to 1880
RF Specifications
Table 11-10 describes the RF specifications of the MRFU. Table 11-10 RF specifications of the MRFU Type MRFU RX and TX Channels 1T2R Capacity An MRFU supports one carrier. The bandwidth of each carrier can be 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz. Output Power 1 x 60 W
NOTE

Table 11-11 describes the surge protection specifications for the ports on the MRFU.
NOTE
Table 11-11 Surge protection specifications for the ports on the MRFU Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode
Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s)
Issue 03 (2011-12-24)
62
Port
Applicatio n Scenario
Surge Protection Mode Surge current Differential mode Common mode
Specification 10 kA 20 kA 8 kA 40 kA 3 kA 5 kA
Antenna port
All
Surge current
Differential mode Common mode
Monitoring port
All
Surge current
Antenna Capability
Table 11-12 describes the antenna capability of the MRFU. Table 11-12 Antenna capability of the MRFU Type MRFU TMA Support Capability TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
NOTE
11.1.4 Technical Specifications of the MRFUd

This section describes the technical specifications of the MRFUd.

Table 11-13 describes the working mode and frequency bands of the MRFUd.
Issue 03 (2011-12-24)
63
Table 11-13 Working mode and frequency bands of the MRFUd Type Worki ng Mode LTE FDD Frequency Band (MHz) 900 (band 8) 900 (P25) 1800 (band 3) RX Band (MHz) TX Band (MHz)
MRFUd
880 to 915 890 to 915 1710 to 1785
925 to 960 935 to 960 1805 to 1880
RF Specifications
Table 11-14 describes the RF specifications of the MRFUd. Table 11-14 RF specifications of the MRFUd Type MRFUd RX and TX Channels 2T2R Capacity An MRFUd supports two carriers. The bandwidth of each carrier can be 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed: l 35 MHz in the 900 MHz (band 8) l 25 MHz in the 900 MHz (P25) l 40 MHz in the 1800 MHz (band 3) Output Power l Two carriers: 2 x 80 W l One carrier: 2 x 60 W
NOTE

Table 11-15 describes the surge protection specifications for the ports on the MRFUd.
NOTE
Issue 03 (2011-12-24)
64
Table 11-15 Surge protection specifications for the ports on the MRFUd Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Antenna port All Surge current Differential mode Common mode Monitoring port All Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 3 kA 5 kA
Antenna Capability
Table 11-16 describes the antenna capability of the MRFUd. Table 11-16 Antenna capability of the MRFUd Type MRFUd TMA Support Capability TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
NOTE
11.2 Technical Specifications of RRUs

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

This section describes the technical specifications of the RRU3201.

Table 11-17 describes the working mode and frequency bands of the RRU3201. Table 11-17 Working mode and frequency bands of the RRU3201 Type RRU3201 Workin g Mode LTE FDD Frequency Band (MHz) 700 (band 13) 2600 (band 7) RX Band (MHz) 777 to 787 Band C: 2500 to 2520 Band D: 2510 to 2560 Band E: 2550 to 2570 TX Band (MHz) 746 to 756 Band C: 2620 to 2640 Band D: 2630 to 2680 Band E: 2670 to 2690
RF Specifications
Table 11-18 describes the RF specifications of the RRU3201. Table 11-18 RF specifications of the RRU3201 Type RRU3201 RX and TX Channels 2T2R Capacity An RRU3201 supports 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 Output Power 2 x 40 W
NOTE
Engineering Specifications
Table 11-19 describes the physical specifications of the RRU3201.
Issue 03 (2011-12-24)
66
Table 11-19 Physical specifications of the RRU3201 Type RRU3201 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) 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) Weight (kg) l 17.5 kg (without the housing) l 19 kg (with the housing)
Table 11-20 describes the environmental specifications of the RRU3201. Table 11-20 Environmental specifications of the RRU3201 Type RRU3201 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospheri c Pressure 70 kPa to 106 kPa
Table 11-21 describes the compliance standards for the RRU3201. Table 11-21 Compliance standards of the RRU3201 Type Operating Environment Compliance standards: l 3GPP TS 25.141 V3.0.0 l ETSI EN 300019-1-4 V2.1.2 (2003-04) Class 4.1: "Nonweatherprotected locations" Anti-Seismic Performance NEBS GR63 zone4 Ingress Protection (IP) Rating IP65
RRU3201
Table 11-22 describes the surge protection specifications for the ports on the RRU3201.

NOTE
Table 11-22 Surge protection specifications for the ports on the RRU3201 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Antenna port All Surge current Differential mode Common mode CPRI port RET port All All Surge Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 250 A 3 kA 5 kA
Antenna Capability
Table 11-23 describes the antenna capability of the RRU3201. Table 11-23 Antenna capability of the RRU3201 Type RRU3201 TMA Support Capability TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
NOTE
Issue 03 (2011-12-24)
68


Table 11-24 describes the working mode and frequency bands of the RRU3203. Table 11-24 Working mode and frequency bands of the RRU3203 Type Worki ng Mode LTE FDD Frequency Band (MHz) 700 (band 12) RX Band (MHz) TX Band (MHz)
RRU3203
698 to 716
728 to 746
RF Specifications
Table 11-25 describes the RF specifications of the RRU3203. Table 11-25 RF specifications of the RRU3203 Type RRU3203 RX and TX Channels 2T2R Capacity An RRU3203 supports one carrier. The bandwidth of each carrier can be 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, or 15 MHz. Output Power 2 x 40 W
NOTE
Table 11-26 describes the physical specifications of the RRU3203. Table 11-26 Physical specifications of the RRU3203 Type RRU3203 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) l 480 mm x 356 mm x 140 mm (24 L without the housing) l 485 mm x 381 mm x 170 mm (31.4 L with the housing)
Issue 03 (2011-12-24) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Weight (kg) l 21 kg (without the housing) l 24 kg (with the housing)
69
Table 11-27 describes the environmental specifications of the RRU3203. Table 11-27 Environmental specifications of the RRU3203 Type RRU32 03 Temperature l 40C to +50C (with solar radiation of 1120 W/ m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/m3 Atmospheric Pressure 70 kPa to 106 kPa
RRU3203
NOTE
Issue 03 (2011-12-24)
70
Table 11-29 Surge protection specifications for the ports on the RRU3203 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Antenna port All Surge current Differential mode Common mode CPRI port RET port All All Surge Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 250 A 3 kA 5 kA
Antenna Capability
NOTE


Table 11-31 describes the working mode and frequency bands of the RRU3220.
Table 11-31 Working mode and frequency bands of the RRU3220 Type Worki ng Mode LTE FDD Frequency Band (MHz) DD 800 (band 20) RX Band (MHz) TX Band (MHz)
RRU3220
832 to 847 842 to 862
791 to 806 801 to 821
RF Specifications
Table 11-32 describes the RF specifications of the RRU3220. Table 11-32 RF specifications of the RRU3220 Type RRU3220 RX and TX Channels 2T2R Capacity An RRU3220 supports one carrier. The bandwidth of each carrier can be 5 MHz, 10 MHz, 15 MHz, or 20 MHz. Output Power 2 x 40 W
NOTE
Table 11-33 describes the physical specifications of the RRU3220. Table 11-33 Physical specifications of the RRU3220 Type RRU3220 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) l 400 mm x 220 mm x 140 mm (12 L without the housing) l 400 mm x 240 mm x 160 mm (15 L with the housing) Weight (kg) l 13.5 kg (without the housing) l 15 kg (with the housing)
Table 11-34 describes the environmental specifications of the RRU3220.
Issue 03 (2011-12-24)
72
Table 11-34 Environmental specifications of the RRU3220 Type RRU3220 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospheri c Pressure 70 kPa to 106 kPa
RRU3220
NOTE
Table 11-36 Surge protection specifications for the ports on the RRU3220 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Specification 2 kV (1.2/50 s)
Issue 03 (2011-12-24)
73
Port
Surge Protection Mode Common mode Surge current Differential mode Common mode
Specification 4 kV (1.2/50 s) 10 kA 20 kA 8 kA 40 kA 250 A
Antenna port
All
Surge current
CPRI port RET port
All All
Surge Surge current Differential mode Common mode
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
NOTE

Issue 03 (2011-12-24)
74

Table 11-38 describes the working mode and frequency bands of the RRU3221. Table 11-38 Working mode and frequency bands of the RRU3221 Type Worki ng Mode LTE FDD Frequency Band (MHz) 2600 (band 7) RX Band (MHz) TX Band (MHz)
RRU3221
2500 to 2570
2620 to 2690
RF Specifications
Table 11-39 describes the RF specifications of the RRU3221. Table 11-39 RF specifications of the RRU3221 Type RRU3221 RX and TX Channels 2T2R Capacity An RRU3221 supports two carriers. The bandwidth of each carrier can be 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed 40 MHz. Output Power 2 x 40 W
NOTE
Table 11-40 describes the physical specifications of the RRU3221. Table 11-40 Physical specifications of the RRU3221 Type RRU3221 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) l 480 mm x 270 mm x 140 mm (18 L without the housing) l 485 mm x 300 mm x 170 mm (25 L with the housing) Weight (kg) l 20 kg (without the housing) l 22 kg (with the housing)
Issue 03 (2011-12-24)
75
Table 11-41 describes the environmental specifications of the RRU3221. Table 11-41 Environmental specifications of the RRU3221 Type RRU3221 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospher ic Pressure 70 kPa to 106 kPa
RRU3221
NOTE
Table 11-43 Surge protection specifications for the ports on the RRU3221 Port DC power supply socket
Issue 03 (2011-12-24)
Applicatio n Scenario All
Surge Protection Mode Surge Differential mode
Specification 2 kV (1.2/50 s)
76
Port
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
NOTE

Issue 03 (2011-12-24)
77

Table 11-45 describes the working mode and frequency bands of the RRU3222. Table 11-45 Working mode and frequency bands of the RRU3222 Type Worki ng Mode LTE FDD Frequency Band (MHz) DD 800 (band 20) RX Band (MHz) TX Band (MHz)
RRU3222
832 to 862
791 to 821
RF Specifications
Table 11-46 describes the RF specifications of the RRU3222. Table 11-46 RF specifications of the RRU3222 Type RRU3222 RX and TX Channels 2T2R Capacity An RRU3222 supports one carrier. The bandwidth of each carrier can be 5 MHz, 10 MHz, 15 MHz, or 20MHz. Output Power 2 x 40 W
NOTE

Table 11-48 Environmental specifications of the RRU3222 Type RRU322 2 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/m3 Atmospheric Pressure 70 kPa to 106 kPa
RRU3222
NOTE
Table 11-50 Surge protection specifications for the ports on the RRU3222 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Specification 2 kV (1.2/50 s)
Issue 03 (2011-12-24)
79
Port
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
NOTE

Issue 03 (2011-12-24)
80

Table 11-52 describes the working mode and frequency bands of the RRU3240. Table 11-52 Working mode and frequency bands of the RRU3240 Type RRU3240 Working Mode LTE FDD Frequency Band (MHz) 2600 (band 7) RX Band (MHz) 2500 to 2570 TX Band (MHz) 2620 to 2690
RF Specifications
Table 11-53 describes the RF specifications of the RRU3240. Table 11-53 RF specifications of the RRU3240 Type RRU3240 RX and TX Channels 2T4R Capacity An RRU3240 supports two carriers. The bandwidth of each carrier can be 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed 40MHz. Output Power 2 x 40 W
NOTE
Table 11-54 describes the physical specifications of the RRU3240. Table 11-54 Physical specifications of the RRU3240 Type RRU3240 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) l 480 mm x 270 mm x 140 mm (18 L without the housing) l 485 mm x 300 mm x 170 mm (25 L with the housing) Weight (kg) l 20 kg (without the housing) l 22 kg (with the housing)

Table 11-55 Environmental specifications of the RRU3240 Type RRU3240 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospher ic Pressure 70 kPa to 106 kPa
RRU3240
NOTE
Table 11-57 Surge protection specifications for the ports on the RRU3240 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode
Issue 03 (2011-12-24)
82
Port
Specification 10 kA 20 kA 8 kA 40 kA 250 A
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA
Antenna Capability
NOTE


Issue 03 (2011-12-24)
83
Table 11-59 Working mode and frequency bands of the RRU3808 Type Worki ng Mode LTE FDD Frequency Band (MHz) AWS (band 4) 2100 (band 1) RX Band (MHz) TX Band (MHz)
RRU380 8
1710 to 1755 1920 to 1980
2110 to 2155 2110 to 2170
RF Specifications
Table 11-60 describes the RF specifications of the RRU3808. Table 11-60 RF specifications of the RRU3808 Type RRU3808 RX and TX Channels 2T2R Capacity An RRU3808 supports 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. Output Power 2 x 40 W
NOTE
Table 11-61 describes the physical specifications of the RRU3808. Table 11-61 Physical specifications of the RRU3808 Type RRU3808 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) 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) Weight (kg) l 17.5 kg (without the housing) l 19 kg (with the housing)

RRU3808
NOTE
Issue 03 (2011-12-24)
85
Port
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA
Antenna Capability
NOTE

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

Issue 03 (2011-12-24)
86
Table 11-66 Working mode and frequency bands of the RRU3908 Type Worki ng Mode LTE FDD LTE FDD Frequency Band (MHz) 1800 (band 3) RX Band (MHz) TX Band (MHz)
RRU3908 V1 RRU3908 V2
1710 to 1755 1740 to 1785
1805 to 1850 835 to 1880 869 to 894 925 to 960
850 (band 5) 900 (band 8)
824 to 849 880 to 915
RF Specifications
Table 11-67 describes the RF specifications of the RRU3908. Table 11-67 RF specifications of the RRU3908 Type RX and TX Channels Capacity An RRU3908 V1 supports one carrier. The bandwidth of each carrier can be 5 MHz, 10 MHz, or 20MHz. An RRU3908 V2 supports one carrier. The bandwidth of each carrier can be: l 1.4 MHz, 3 MHz, 5 MHz, or 10 MHz in the 850 MHz band. l 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz in the 900 MHz band. Output Power 2 x 30 W
RRU3908 V1 2T2R
RRU3908 V2 2T2R
2 x 40 W
NOTE
Table 11-68 describes the physical specifications of the RRU3908.
Issue 03 (2011-12-24)
87
Table 11-68 Physical specifications of the RRU3908 Type RRU3908 V1 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) 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) RRU3908 V2 48 V DC; voltage range: 36 V DC to 57 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) Weight (kg) l 21 kg (without the housing) l 23 kg (with the housing)
l 21 kg (without the housing) l 23 kg (with the housing)
Table 11-69 describes the environmental specifications of the RRU3908. Table 11-69 Environmental specifications of the RRU3908 Type RRU3908 V1 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) RRU3908 V2 l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) 5% RH to 100% RH 1 g/m3 to 30 g/ m3 70 kPa to 106 kPa Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospheri c Pressure 70 kPa to 106 kPa
Table 11-70 describes the compliance standards for the RRU3908.
Issue 03 (2011-12-24)
88
Table 11-70 Compliance standards of the RRU3908 Type Operating Environment Compliance standards: l 3GPP TS 25.141 V3.0.0 l ETSI EN 300019-1-4 V2.1.2 (2003-04) Class 4.1: "Nonweatherprotected locations" RRU3908 V2 Compliance standards: l 3GPP TS 25.141 V3.0.0 l ETSI EN 300019-1-4 V2.1.2 (2003-04) Class 4.1: "Nonweatherprotected locations" NEBS GR63 zone4 IP65 Anti-Seismic Performance NEBS GR63 zone4 Ingress Protection (IP) Rating IP65
RRU3908 V1
NOTE
Table 11-71 Surge protection specifications for the ports on the RRU3908 Port DC power supply socket Applicatio n Scenario All Surge Protection Mode Surge Differential mode Common mode Surge current Differential mode Common mode Specification 2 kV (1.2/50 s) 4 kV (1.2/50 s) 10 kA 20 kA
Issue 03 (2011-12-24)
89
Port Antenna port
Applicatio n Scenario All
Specification 8 kA 40 kA 250 A
CPRI port RET port
All All
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
Table 11-72 describes the antenna capability of the RRU3908. Table 11-72 Antenna capability of the RRU3908 Type RRU3908 V1 RRU3908 V2 TMA Support Capability TMA supported TMA supported RET Antenna Support Capability AISG2.0-complied RET antennas supported AISG2.0-complied RET antennas supported
NOTE


Issue 03 (2011-12-24)
90
Table 11-73 Working mode and frequency bands of the RRU3928 Type Worki ng Mode LTE FDD Frequency Band (MHz) 900 (band 8) 1800 (band 3) RX Band (MHz) TX Band (MHz)
RRU3928
880 to 915 1710 to 1785
925 to 960 1805 to 1880
RF Specifications
Table 11-74 describes the RF specifications of the RRU3928. Table 11-74 RF specifications of the RRU3928 Type RRU3928 RX and TX Channels 2T2R Capacity An RRU3928 supports two carriers. The bandwidth of each carrier can be 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed: l 35 MHz in the 900 MHz band l 40 MHz in the 1800 MHz band Output Power 2 x 40 W
NOTE

Table 11-76 Environmental specifications of the RRU3928 Type RRU3928 Temperature Relative Humidity Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospheri c Pressure 70 kPa to 106 kPa
l 40C to +50C (with 5% RH to 100% RH solar radiation of 2 1120 W/m ) l 40C to +55C (without solar radiation)
RRU3928
NOTE
Issue 03 (2011-12-24)
92
Port
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
NOTE


Table 11-80 Working mode and frequency bands of the RRU3929 Type RRU3929 Working Mode LTE FDD Frequency Band (MHz) 900 (band 8) 1800 (band 3) RX Band (MHz) 880 to 915 1710 to 1785 TX Band (MHz) 925 to 960 1805 to 1880
RF Specifications
Table 11-81 describes the RF specifications of the RRU3929. Table 11-81 RF specifications of the RRU3929 Type RRU3929 RX and TX Channels 2T2R Capacity An RRU3929 supports two carriers. The bandwidth of each carrier can be 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, or 20 MHz. The total bandwidth of two carriers cannot exceed: l 35 MHz in the 900 MHz band l 40 MHz in the 1800 MHz band Output Power 2 x 60 W
NOTE

RRU3929
NOTE
Issue 03 (2011-12-24)
95
Port
Antenna port
All
Surge current
CPRI port RET port
All All
3 kA 5 kA 3 kA 5 kA
Alarm port
All
Surge current
Antenna Capability
NOTE


Table 11-87 Working mode and frequency bands of the RRU3232 Type RRU3232 Working Mode LTE TDD Frequency Band (MHz) 2600 (band 38): 2570 to 2620 2600 (band 41): 2496 to 2690 2300 (band 40): 2300 to 2400 3500: 3400 to 3700 1800: 1755 to 1920
RF Specifications
Table 11-88 describes the RF specifications of the RRU3232. Table 11-88 RF specifications of the RRU3232 Type RRU3232 RX and TX Channels 4T4R Capacity An RRU3232 supports one carrier. The bandwidth of each carrier can be 10 MHz or 20 MHz. Output Power l 3500 MHz band: 4 x 10 W l Other bands: 4 x 20 W
NOTE
Table 11-89 describes the physical specifications of the RRU3232. Table 11-89 Physical specifications of the RRU3232 Type RRU3232 Input Power 48 V DC; voltage range: 36 V DC to 57 V DC Dimensions (Height x Width x Depth) l 480 mm x 270 mm x 140 mm (18 L without the housing) l 485 mm x 300 mm x 170 mm (24.7 L with the housing) Weight (kg) l 19.5 kg (without the housing) l 21 kg (with the housing)

Table 11-90 Environmental specifications of the RRU3232 Type RRU3232 Temperature l 40C to +50C (with solar radiation of 1120 W/m2) l 40C to +55C (without solar radiation) Relative Humidity 5% RH to 100% RH Absolute Humidity 1 g/m3 to 30 g/ m3 Atmospheri c Pressure 70 kPa to 106 kPa
RRU3232
NOTE
Issue 03 (2011-12-24)
98
Port
Specification 10 kA 20 kA 8 kA 40 kA 3 kA 5 kA
Antenna port
All
Surge current
RET port
All
Surge current
Antenna Capability
Table 11-93 describes the antenna capability of the RRU3232. Table 11-93 Antenna capability of the RRU3232 Type RRU3232 TMA Support Capability Not supported RET Antenna Support Capability AISG2.0-complied RET antennas supported
NOTE
Issue 03 (2011-12-24)
99

eNodeB Technical Description (V100R004C00 - 03) (PDF) - EN PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

eNodeB Technical Description (V100R004C00 - 03) (PDF) - EN PDF

Enviado por

Direitos autorais:

Formatos disponíveis

eNodeB V100R004C00

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.