eNodeB Technical Description(V100R004C00_03)(PDF)-EN.pdf

eNodeBV100R004C00

Technical Description

Issue 03Date 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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 03 (2011-12-24) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

PurposeThis document provides the LTE-SAE system architecture and the following information aboutthe eNodeB: basic functions, structures, environment monitoring principles, clocksynchronization modes, operation and maintenance, reliability, topologies, and typical hardwareconfigurations.

Product VersionsThe following table lists the product versions related to this document.

Product Name VersionBTS3900 LTE V100R004C00BTS3900A LTE V100R004C00BTS3900L LTE V100R004C00DBS3900 LTE V100R004C00DBS3900 LTE TDD V100R004C00

Intended AudienceThe intended audiences of this document are:l Network planning engineersl Field engineersl System engineers

Organization1 Changes in the eNodeB Technical Description

eNodeBTechnical Description About This Document


ii

This chapter describes the changes in the eNodeB Technical Description.2 LTE-SAE System ArchitectureThis chapter describes the LTE-SAE system architecture, including the position of eNodeBs andthe functions of Network Elements (NEs). LTE stands for Long Term Evolution, and SAE standsfor System Architecture Evolution.3 eNodeB FunctionsThis chapter describes the functions of eNodeBs. As the radio access equipment in the LTE-SAE system, eNodeBs perform radio resource management, packet compression and ciphering,user plane packet routing, MME selection, and message scheduling and transmission.4 eNodeB StructureThis chapter describes the structure of an eNodeB. Each eNodeB consists of two basic types ofcomponent: baseband unit BBU3900 and Radio Frequency (RF) unit RRU or RFU.5 Environment Monitoring PrinciplesThis chapter describes environment monitoring principles for eNodeBs. Environmentmonitoring detects the following environmental conditions of an eNodeB: temperature,humidity, water damage, smoke, unauthorized access, and power distribution faults. Toimplement environment monitoring, the eNodeB is equipped with environment monitoringdevices and configured with external environment alarms, including Boolean alarms and anenvironment monitoring unit type A (EMUA) alarm.6 eNodeB Synchronization ModesThis chapter describes the clock synchronization modes for eNodeBs.7 Operation and Maintenance of eNodeBsThis chapter describes operation and maintenance of eNodeBs. The operation and maintenance(OM) system of eNodeBs manages, monitors, and maintains the software, hardware, andconfiguration data of the eNodeBs. In addition, the OM system provides various OM modes tomeet requirements.8 eNodeB ReliabilityThis chapter describes eNodeB reliability, which includes system reliability, hardwarereliability, and software reliability.9 eNodeB TopologiesThis chapter describes eNodeB topologies on the S1 and CPRI interfaces.10 Typical Hardware Configurations of an eNodeBThis chapter describes the hardware configurations of an eNodeB.11 Technical Specifications of Radio Frequency UnitsThis chapter describes the technical specifications of radio frequency (RF) units, such as theworking mode, frequency band, output power, and antenna capability.

ConventionsSymbol ConventionsThe symbols that may be found in this document are defined as follows.



iii

Symbol DescriptionIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.Indicates a tip that may help you solve a problem or savetime.Provides additional information to emphasize or supplementimportant points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention DescriptionTimes New Roman Normal paragraphs are in Times New Roman.Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.Italic Book titles are in italics.Courier New Examples of information displayed on the screen are in

Courier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface The keywords of a command line are in boldface.Italic Command arguments are in italics.[ ] Items (keywords or arguments) in brackets [ ] are optional.{ x | y | ... } Optional items are grouped in braces and separated by

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

vertical bars. One item is selected or no item is selected.



iv

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

vertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface 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 OperationsThe keyboard operations that may be found in this document are defined as follows.

Format DescriptionKey Press the key. For example, press Enter and press Tab.Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse OperationsThe mouse operations that may be found in this document are defined as follows.

Action DescriptionClick Select and release the primary mouse button without moving

the pointer.Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.Drag Press and hold the primary mouse button and move the

pointer to a certain position.



v

Contents

About This Document.....................................................................................................................ii1 Changes in the eNodeB Technical Description.......................................................................12 LTE-SAE System Architecture....................................................................................................43 eNodeB Functions.........................................................................................................................64 eNodeB Structure...........................................................................................................................8

4.1 Logical Structure of the Baseband Unit.............................................................................................................94.2 Logical Structure of Radio Frequency Units....................................................................................................10

5 Environment Monitoring Principles........................................................................................146 eNodeB Synchronization Modes..............................................................................................187 Operation and Maintenance of eNodeBs................................................................................20

7.1 OM Modes........................................................................................................................................................217.2 O&M Functions................................................................................................................................................22

8 eNodeB Reliability......................................................................................................................258.1 System Reliability.............................................................................................................................................268.2 Hardware Reliability.........................................................................................................................................288.3 Software Reliability..........................................................................................................................................29

9 eNodeB Topologies.....................................................................................................................3110 Typical Hardware Configurations of an eNodeB...............................................................39

10.1 Typical Hardware Configurations and Subrack Numbers..............................................................................4010.2 Hardware Configurations of BTS3900 LTE..................................................................................................4510.3 Hardware Configurations of BTS3900A LTE................................................................................................4810.4 Hardware Configurations of BTS3900L LTE................................................................................................5110.5 Hardware Configurations of DBS3900 LTE..................................................................................................5410.6 Hardware Configurations of DBS3900 LTE TDD.........................................................................................56

11 Technical Specifications of Radio Frequency Units...........................................................5711.1 Technical Specifications of RFUs..................................................................................................................58

11.1.1 Technical Specifications of the LRFU..................................................................................................5811.1.2 Technical Specifications of the LRFUe.................................................................................................6011.1.3 Technical Specifications of the MRFU.................................................................................................61

eNodeBTechnical Description Contents


vi

11.1.4 Technical Specifications of the MRFUd...............................................................................................6311.2 Technical Specifications of RRUs..................................................................................................................65

11.2.1 Technical Specifications of the RRU3201............................................................................................6611.2.2 Technical Specifications of the RRU3203............................................................................................6911.2.3 Technical Specifications of the RRU3220............................................................................................7111.2.4 Technical Specifications of the RRU3221............................................................................................7411.2.5 Technical Specifications of the RRU3222............................................................................................7711.2.6 Technical Specifications of the RRU3240............................................................................................8011.2.7 Technical Specifications of the RRU3808............................................................................................8311.2.8 Technical Specifications of the RRU3908............................................................................................8611.2.9 Technical Specifications of the RRU3928............................................................................................9011.2.10 Technical Specifications of the RRU3929..........................................................................................9311.2.11 Technical Specifications of the RRU3232..........................................................................................96

eNodeBTechnical Description Contents


vii

1 Changes in the eNodeB TechnicalDescription

This chapter describes the changes in the eNodeB Technical Description.

03 (2011-12-24)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 thefollowing table.

Topic Change Description9 eNodeB Topologies l Deleted the chain topology on the CPRI

interface in time division duplex (TDD)mode.

l Deleted the description of cascading levels ofRRUs.

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 UnitsCompared with issue 01 (2011-09-15), this issue incorporates the changes described in thefollowing table.

eNodeBTechnical Description 1 Changes in the eNodeB Technical Description


1

Topic Change Description4.2 Logical Structure of RadioFrequency Units

Added the description of an RRU and an RFU.

10.2 Hardware Configurations ofBTS3900 LTE

Modified the positions of the components ofBTS3900 LTE in typical configurations and thehardware configuration descriptions.

10.3 Hardware Configurations ofBTS3900A LTE

Modified the positions of the components ofBTS3900A LTE in typical configurations and thehardware configuration descriptions.

10.4 Hardware Configurations ofBTS3900L LTE

Modified the positions of the components ofBTS3900L LTE in typical configurations and thehardware configuration descriptions.

10.5 Hardware Configurations ofDBS3900 LTE

Modified the hardware configurationdescriptions of the DBS3900 LTE.

10.6 Hardware Configurations ofDBS3900 LTE TDD

Modified the hardware configurationdescriptions 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 LTECompared with draft A (2011-07-15), this issue incorporates the changes described in thefollowing table.

Topic Change Description10.1 Typical Hardware Configurationsand Subrack Numbers

l Modified the hardware quantities of afrequency division duplex (FDD) eNodeB intypical configurations.

l Modified the hardware quantities of a TDDeNodeB in typical configurations.

l Distinguished between Ver.B and Ver.Ccabinets.

10.2 Hardware Configurations ofBTS3900 LTE

l Deleted the hardware configurations ofBTS3900A LTE.

l Modified the positions of the components ofBTS3900 LTE in typical configurations.

10.4 Hardware Configurations ofBTS3900L LTE

Modified the positions of the components ofBTS3900L LTE in typical configurations.



2

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 informationdescribed in the following table.

Topic Description8.1 System Reliability Added the description of inter-board cell

reestablishment, CPRI port redundancy, OMchannel backup, and route backup.

9 eNodeB Topologies Added the description of topologies for loadsharing.

Compared with issue 04 (2011-06-10) of V100R003C00, this issue incorporates the changesdescribed in the following table.

Topic Change Description10.1 Typical Hardware Configurationsand Subrack Numbers

l Modified the hardware quantities of an FDDeNodeB in typical configurations.

l Modified the hardware quantities of a TDDeNodeB in typical configurations.

Compared with issue 04 (2011-06-10) of V100R003C00, this issue does not delete any topics.



3

2 LTE-SAE System ArchitectureThis chapter describes the LTE-SAE system architecture, including the position of eNodeBs andthe functions of Network Elements (NEs). LTE stands for Long Term Evolution, and SAE standsfor System Architecture Evolution.

Position of eNodeBsThe 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 radioaccess 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 accessthe LTE-SAE system. An eNodeB communicates with a UE, another eNodeB, or the EPCthrough the Uu, X2, and S1 interfaces, respectively.

eNodeBTechnical Description 2 LTE-SAE System Architecture


4

Functions of NEsThe NEs in the LTE-SAE system include eNodeBs, MMEs, and S-GWs. Table 2-1 describesthe functions of the NEs.

Table 2-1 Functions of the NEs in the LTE-SAE systemNE FunctioneNodeB l Radio resource management, including radio bearer control, radio

admission control, connection mobility control, and scheduling resourcel Packet compression and cipheringl Routing of user plane packets towards an S-GWl MME selectionl Scheduling and transmission of messages, including broadcast

information and paging messagesl Measurement and measurement reporting configuration

MME l Paging message distributionl Security controll Mobility management in idle model SAE bearer controll Ciphering and integrity protection of non-access stratum (NAS) signaling

S-GW l Termination of user plane packets that are generated for paging reasonl Support for user plane handovers caused by UE mobility

eNodeBTechnical Description 2 LTE-SAE System Architecture


5

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

Radio Resource ManagementRadio resource management covers radio bearer control, admission control, mobilitymanagement, and dynamic resource allocation:l Radio bearer control involves setup, maintenance, and release of radio bearers and resource

configuration for radio bearers.l Admission control accepts or rejects radio bearer setup requests.l Mobility management involves management of radio resources for UEs in idle mode and

UEs in connected mode.l Dynamic resource allocation involves allocation and release of radio resources on the

control plane and user plane. The resources include the buffer, processes, and resourceblocks.

Packet Compression and CipheringPacket compression and ciphering include the following functions:l Header compression for downlink packets and header decompression for uplink packets

using compression algorithmsl Encryption and decryption of packets using ciphering algorithms

User Plane Packet RoutingEach eNodeB provides routing of user plane packets towards an S-GW.

MME SelectionMME selection includes the following functions:l Selection of an MME for a UE during the Attach procedure of the UEl Reselection of an MME for a UE when the UE is in a network

eNodeBTechnical Description 3 eNodeB Functions


6

l Determination of the route to an MME based on the information provided by the UE whenno routing information is available

Message Scheduling and TransmissionMessage scheduling and transmission include the following functions: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)l Transmission of paging messages, broadcast information, and O&M messages over the Uu

interface according to specific scheduling rules

eNodeBTechnical Description 3 eNodeB Functions


7

4 eNodeB StructureAbout This Chapter

This chapter describes the structure of an eNodeB. Each eNodeB consists of two basic types ofcomponent: baseband unit BBU3900 and Radio Frequency (RF) unit RRU or RFU.

4.1 Logical Structure of the Baseband UnitThe baseband unit BBU3900 consists of four logical subsystems: control, transport, baseband,and power and environment monitoring.4.2 Logical Structure of Radio Frequency UnitsA radio frequency (RF) unit consists of logical components such as the common public radiointerface (CPRI) module, transceiver (TRX), power module, power amplifier (PA), low noiseamplifier (LNA), filter, and circulator.

eNodeBTechnical Description 4 eNodeB Structure


8

4.1 Logical Structure of the Baseband UnitThe 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 SubsystemThe functions of the control subsystem are implemented by the LTE main processing andtransmission unit (LMPT).This subsystem performs operation and maintenance (O&M) functions, processes signaling, andprovides the system clock. It manages the entire eNodeB.l The OM functions include configuration management, fault management, performance

management, security management, and deployment.l The signaling includes Packet Data Convergence Protocol (PDCP) signaling on the Uu

interface and Stream Control Transmission Protocol (SCTP) signaling on the S1 and X2interfaces.

l The system clock can be one of the following types: Global Positioning System (GPS),Remote Global Positioning System (RGPS), IEEE 1588 V2, synchronous Ethernet, clockover IP, 1 pulse per second (PPS)+time of day (TOD), building integrated timing supply(BITS), and E1/T1.

Transport SubsystemThe functions of the transport subsystem are implemented by the LMPT and universaltransmission processing units (UTRPs), which support IP over FE/GE and IP over E1/T1,respectively.The transport subsystem performs the following functions:



9

l Provides ports for communication between the eNodeB and the evolved packet core (EPC).l Provides the O&M channel between the eNodeB and the local maintenance terminal (LMT)

or M2000.

Baseband SubsystemThe 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, includinguplink and downlink scheduling and data processing. In addition, this subsystem provides thecommon public radio interface (CPRI) for communication between BBU3900 and radiofrequency (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 measurementson uplink channels.

l Based on the downlink scheduling instruction, the downlink processing module assemblesthe data received from the transport subsystem into packets, encodes and modulates thedata, performs multiple-input multiple-output (MIMO) and orthogonal frequency divisionmultiplexing (OFDM) processing, and then transmits the signals over the CPRI interface.

l The CPRI interface is used for transmission of data between BBU3900 and RF units.

Power and Environment Monitoring SubsystemThe functions of the power and environment monitoring subsystem are implemented by theuniversal power and environment interface unit (UPEU) and environment monitoring units.The power and environment monitoring subsystem performs the following functions:l Supplies power to BBU3900.l Monitors the power status of BBU3900.l Provides ports for connections to environment monitoring units and receives and forwards

signals from the environment monitoring units.

4.2 Logical Structure of Radio Frequency UnitsA radio frequency (RF) unit consists of logical components such as the common public radiointerface (CPRI) module, transceiver (TRX), power module, power amplifier (PA), low noiseamplifier (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 anddemodulate baseband signals and RF signals, process data, amplify power, and detect standingwaves.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.



10

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



11

NOTEIn 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 ModuleA CPRI module performs the following functions:l Receives downlink baseband data from BBU3900.l Transmits uplink baseband data to BBU3900.l Forwards the data sent from the cascaded RRUs.

TRXA 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 ModuleA power module converts the input power into the power required by an RRU or RFU.

PA and LNAA PA amplifies the low-power RF signals received from the TRX.An LNA amplifies signals received from antennas.

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



12

CirculatorA circulator is used by a TDD RRU for switching between uplink and downlink transmissionsof RF signals.



13

5 Environment Monitoring PrinciplesThis chapter describes environment monitoring principles for eNodeBs. Environmentmonitoring detects the following environmental conditions of an eNodeB: temperature,humidity, water damage, smoke, unauthorized access, and power distribution faults. Toimplement environment monitoring, the eNodeB is equipped with environment monitoringdevices and configured with external environment alarms, including Boolean alarms and anenvironment monitoring unit type A (EMUA) alarm.

Ports on a UPEUThe 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 twoMON ports for connections to environment monitoring devices. The ports are described asfollows: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 aBTS3900 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 forconnections 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. TheCMUA provides ports for connections to the door status sensor and smoke sensor andalso provides a port used for three Boolean signal inputs.Signals of environmental alarms detected by the sensors connected to the CMUA areprocessed 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 outsidethe APM30H cabinet.

eNodeBTechnical Description 5 Environment Monitoring Principles


14

The EMUA is 1 U high. It can be installed in a 19-inch-wide rack or cabinet with itsdepth 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 providesextended ports for 32 Boolean and analog signal inputs. If the EMUA is used to monitorenvironment outside a cabinet, data configuration is required. If the dedicated ports onthe EMUA are insufficient for environment monitoring, the extended ports can be usedand related data configuration is required.

The alarm monitoring devices connected to the UPEU are collectively called peer alarm devicesin the subsequent sections. The devices can be dry contacts, sensors, and EMUAs.

Connections to EXT-ALM PortsThe type of the cable connected to an EXT-ALM port varies depending on the type of the peeralarm 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 InstallationGuide.

Connect one end of an in-position signal cable for the PSU (DC/DC) to the EXT-ALM0port 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, andthen connect the RJ45 connector at the other end of the cable to the EXT-ALM0 or EXT-ALM1 port.

Table 5-1 Pin assignment for wires of the BBU alarm cableAlarmPort

X1 End X2 End WireColor

Description PinAssignment

EXT-ALM0

X1.1 X2.1 Orange andwhite

Positive Booleaninput 1

Twisted pair

X1.2 X2.2 Orange Negative Booleaninput 1 (GND)

X1.3 X2.3 Green andwhite


Twisted pair

X1.6 X2.6 Green Negative Booleaninput 2 (GND)

X1.5 X2.5 Blue andwhite


Twisted pair

X1.4 X2.4 Blue Negative Booleaninput 3 (GND)

X1.7 X2.7 Brown andwhite


Twisted pair



15

AlarmPort

X1 End X2 End WireColor

Description PinAssignment

X1.8 X2.8 Brown Negative Booleaninput 4 (GND)

EXT-ALM1

X1.1 X2.1 Orange andwhite


Twisted pair

X1.2 X2.2 Orange Negative Booleaninput 5 (GND)

X1.3 X2.3 Green andwhite


Twisted pair

X1.6 X2.6 Green Negative Booleaninput 6 (GND)

X1.5 X2.5 Blue andwhite


Twisted pair

X1.4 X2.4 Blue Negative Booleaninput 7 (GND)

X1.7 X2.7 Brown andwhite


Twisted pair

X1.8 X2.8 Brown Negative Booleaninput 8 (GND)

The EXT-ALM0 port is connected to dry contacts 0 to 3, and the EXT-ALM1 port is connectedto dry contacts 4 to 7.

Connections to MON PortsThe 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 onthe 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_INport on the CMUA. For details about how to install the cable, see the DBS3900 InstallationGuide.

l In a radio frequency cabinet (RFC), connect one end of a monitoring signal cable betweenthe CMUA and the BBU to the MON0 port on the UPEU and the other end of the cable tothe COM_IN port on the CMUA. For details about how to install the cable, see theBTS3900A Installation Guide.

l In a BTS3900 cabinet, connect one end of a monitoring signal cable for the power andenvironment monitoring unit (PMU) to the MON0 port on the UPEU and the other end ofthe cable to the COM port on the PMU. In addition, connect one end of a monitoring signalcable for the FAN unit to the MON1 port on the UPEU and the other end of the cable to



16

the COM IN port on the FAN unit. For details about how to install the cable, see theBTS3900 Installation Guide.

If the UPEU needs to be connected to an EMUA outside a cabinet, connect one end of an RS485monitoring signal cable to an unused MON port on the UPEU and the other end of the cable toa 2-input RS485 port on the EMUA.

NOTEIf 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 endof the cable to a 2-input RS485 port on the EMUA.



17

6 eNodeB Synchronization ModesThis chapter describes the clock synchronization modes for eNodeBs.Two or more signals reach synchronization if the phase or frequency deviation falls within aspecified range at a valid instant. There are two types of synchronization: frequencysynchronization and time synchronization.l Frequency synchronization means that the frequency of a signal is the same as the reference

frequency but the origin of the timescale for the signal does not need to be the same as thatfor the reference clock.

l Time synchronization is also referred to as time-of-day synchronization, where the originof the timescale for a signal needs to be synchronized with the Universal Time Coordinated(UTC). Therefore, time synchronization implies synchronization in absolute time. UTC isa universal timing standard, in which the atomic clock is maintained accurately to ensuretime synchronization worldwide, with a precision of microseconds.

The subsequent sections describe reference clocks. For details about clock synchronization, seethe Synchronization Feature Parameter Description.

GPS/RGPS ClockSynchronization 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 thereceiver, 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 timesynchronization are available. To implement synchronization with an RGPS clock, the eNodeBmust be equipped with a universal satellite card and clock unit (USCU).

IEEE 1588 V2 ClockIEEE 1588 defines the Precision Time Protocol (PTP), which targets synchronization of clocksin the Ethernet, with the precision to microseconds. In synchronization with an IEEE 1588 V2clock, both frequency synchronization and time synchronization are available. To implementthis type of synchronization, eNodeBs must be connected to reference clocks, such as HuaweiIPCLK1000.

Clock over IPClock over IP is a Huawei proprietary frequency synchronization technology, in whichfrequency synchronization packets are transmitted over IP. Clock-over-IP signals are transmitted

eNodeBTechnical Description 6 eNodeB Synchronization Modes


18

to eNodeBs based on a server/client architecture. In synchronization with a clock over IP, onlyfrequency synchronization is available, with the frequency accuracy lower than 0.05 parts permillion (ppm).

Synchronous EthernetThe synchronous Ethernet technology has the basic principles that a downstream node tracesthe upstream clock by recovering clock signals from the serial data bit streams received at thephysical layer. In synchronous Ethernet, only frequency synchronization is available, with thefrequency accuracy lower than 0.05 ppm.

1 PPS+TOD ClockIn synchronization with a 1 PPS+TOD clock, an eNodeB obtains the 1 PPS signals and Time ofDay (TOD) signals to implement time synchronization. The 1 PPS signals are used for timesynchronization. The TOD signals are used to transmit the time information, type of the referenceclock, and working status of the reference clock. To implement synchronization with a 1 PPSclock, the eNodeB must be equipped with a USCU.

BITS ClockIn synchronization with a building integrated timing supply (BITS) clock, an eNodeB isconnected to a BITS synchronization network through the BITS clock card in the eNodeB toobtain frequency synchronization signals. After phase lock and frequency division, the mainclock unit in the eNodeB converts the synchronization signals into various types of clock signalsrequired by the eNodeB. To implement synchronization with a BITS clock, the eNodeB mustbe equipped with a USCU.

E1/T1 Line ClockIn synchronization with an E1/T1 line clock, an eNodeB obtains frequency synchronizationsignals from the physical layer of E1/T1 lines. This clock synchronization mode is availablewhen 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).

eNodeBTechnical Description 6 eNodeB Synchronization Modes


19

7 Operation and Maintenance of eNodeBsAbout 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, andconfiguration data of the eNodeBs. In addition, the OM system provides various OM modes tomeet requirements.

7.1 OM ModesThis section describes the operation and maintenance (OM) modes for eNodeBs.7.2 O&M FunctionsThis 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.

eNodeBTechnical Description 7 Operation and Maintenance of eNodeBs


20

7.1 OM ModesThis section describes the operation and maintenance (OM) modes for eNodeBs.eNodeBs support both local and remote operation and maintenance.l In local OM mode, maintenance personnel use the Local Maintenance Terminal (LMT) to

operate and maintain a single eNodeB.l In remote OM mode, maintenance personnel use the M2000 or LMT to operate and

maintain eNodeBs in a centralized manner in the operation and maintenance center (OMC).

Figure 7-1 OM system of eNodeBs

As shown in Figure 7-1, the OM system of eNodeBs consists of the following elements:l LMT: is mainly used to assist eNodeB deployment, identify faults, and rectify faults locally.l M2000: is Huawei centralized OM system, which consists of the M2000 server and the

M2000 client. M2000 can be connected to eNodeBs of different models and versionsthrough an OM network for remote centralized operation and maintenance. This mode isrecommended when eNodeBs communicate with M2000 properly.

l eNodeB: is the object of the operation and maintenance.The required OM software, as described in Table 7-1, must be installed on maintenanceterminals for operation and maintenance of eNodeBs.



21

Table 7-1 OM softwareSoftware FunctioniManager M2000 l Topology management

l Fault managementl Configuration managementl Performance managementl Security managementl Software and hardware management

LMT l Man-machine language (MML)command execution

l Alarm managementl Batch processingl Tracing managementl Performance monitoringl Self-check managementl Software managementl Comprehensive maintenance and

commissioning

7.2 O&M FunctionsThis 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 ManagementConfiguration management includes data configuration, query, export, backup and restore, andconfiguration 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, modificationsof the service configuration do not require modifications of the device configuration, andmodifications of the device configuration do not require modifications of the serviceconfiguration either.

Fault ManagementFault management includes fault detection, fault isolation and self-healing, alarm reporting, andalarm 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 lowerspecifications to minimize the impact of the fault on services.



22

l The alarm correlation function enables the system to report only the alarm indicating theroot fault and the ultimate impact on services though there are chains of problems causedby the root fault.

Performance ManagementPerformance management includes the periodic control on eNodeB performance measurementand the collection, storage, and reporting of performance statistics.eNodeBs collect performance statistics every 15, 30, or 60 minutes. eNodeBs can store amaximum of three days of performance measurement results. The performance measurementcovers eNodeB-level and cell-level performance, neighboring cells, transmission, standardinterfaces, and the device usage.eNodeBs support real-time monitoring of Key Performance Indicators (KPIs) at intervals of oneminute, which helps detect and identify faults in time.

Tracing ManagementMessage tracing management traces interfaces, signaling links, UEs, and internal messages forroutine maintenance, commissioning, and fault diagnosis.

Security ManagementSecurity management provides the eNodeB authentication and access control functions, whichinclude user account management, rights management, login management, identityauthentication, and operation authentication.In addition, security management involves security control on the channels between eNodeBsand an element management system (EMS). The channels support encryption using SecureSocket Layer (SSL) or IP Security (IPSec).Security management provides network- and user-level security service. It provides thefollowing functions:l Encryption: encryption of important user informationl Authentication: management of user accounts and authentication of usersl Access control: control of operation accessl Security protocol: support for SSL and IPSec

Software ManagementSoftware management includes software version management, software version upgrade, andpatch management.l Software version management involves query, backup, and restore of software versions.l Software version upgrade can be performed on a batch of eNodeBs remotely. With the one-

click upgrade wizard provided by the M2000, users can perform health checks before andafter 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 ofconfigurations during upgrades, and users only need to follow the instructions in theupgrade wizard. In addition, eNodeBs support rapid version rollback by running a singlecommand, reducing the impact of upgrade failures on the system.



23

l Patch management includes query, download, loading, activation, deactivation, rollback,confirmation, and removal of patches.

Deployment ManagementThe eNodeB deployment solutions include board-ready transportation, automatic discovery ofeNodeBs, initial configuration by using a USB disk, and remote deployment. These solutionsgreatly reduce the workload and efforts of field installation personnel. No computer is required.The personnel only need to install the hardware.l By using automatic discovery of eNodeBs, users do not need to set the IP addresses of the

eNodeBs and EMS.l Users can download software and data of an eNodeB from a USB disk, thereby saving time

especially when the bandwidth of transmission between the eNodeB and the EMS isinsufficient.

l During remote deployment, software commissioning is performed in the operation andmaintenance center (OMC) rather than on site. Customers can perform acceptance tests onthe eNodeB deployment in the OMC.

Equipment ManagementEquipment management includes data configuration, status management, and fault detectionand handling for all the devices in an eNodeB. On the device panel, users can view the devicestatus and perform blocking, reset, and switchover.

Inventory ManagementInventory management includes collection and reporting of the inventory information abouteNodeBs. With inventory management, users can manage network equipment (NE) assets in theOMC in a centralized manner.



24

8 eNodeB ReliabilityAbout This Chapter

This chapter describes eNodeB reliability, which includes system reliability, hardwarereliability, and software reliability.

8.1 System ReliabilitySystem reliability is ensured by using the following schemes: intra-board baseband resourcepool, 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 ReliabilityHardware reliability is ensured by the anti-misinsertion design of boards, overtemperatureprotection, reliable power supply, and surge protection design.8.3 Software ReliabilitySoftware reliability is ensured by the redundancy of important files, data, and boards and by thepowerful tolerance of software errors.

eNodeBTechnical Description 8 eNodeB Reliability


25

8.1 System ReliabilitySystem reliability is ensured by using the following schemes: intra-board baseband resourcepool, 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 PoolIntra-board baseband resource pool is designed to enable dynamic allocation of basebandresources based on the specifications and load status of an LBBP. This increases the usage ofbaseband resources and improves system reliability.The functions of the baseband resource pool are as follows:l If all resources of an LBBP are used to serve a single cell, users are allocated different

baseband resources in a fair manner based on the baseband load on the LBBP.l Full redundancy of intra- or inter-cell baseband resources is achieved. When some baseband

resources are unavailable, the associated services can be diverted to other availablebaseband resources. In this way, the services in the cell can be restored.

Inter-Board Cell ReestablishmentInter-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 whetherresources are available on another LBBP that is connected to the RRU providing the cell. Ifresources meet the relevant conditions, the eNodeB reestablishes the cell on the LBBP thatprovides available resources.The cell can be restored within 20 seconds.

LMPT Cold RedundancyEach eNodeB supports LMPT cold redundancy, in which two LMPTs in BBU3900 work inactive/standby mode. When the active LMPT experiences a major fault or a user runs theswitchover command, an active/standby switchover is performed automatically or manually,respectively.LMPT cold redundancy prevents system collapse caused by LMPT failures and therefore ensuressystem reliability of eNodeBs. An active/standby switchover, however, interrupts eNodeBservices for less than three minutes.

CPRI Port RedundancyCPRI 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 LBBPsto form a hot ring topology. In this topology, two CPRI links transmit identical service data, butthe LBBP where the cell is established and the RRU process data on one link only. If a CPRIport is faulty, services are switched over to the other CPRI link, with a maximum interruptiontime of 500 ms. If the LBBP where the cell is established is faulty, the cell is reestablished onthe other LBBP, with a maximum interruption time of 20s.



26

In cold redundancy of CPRI ports, an RRU is connected to two CPRI ports to form a cold ringtopology. The two CPRI ports are provided by either one or two LBBPs. In this topology, onlyone 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 MIMORRU channel cross-connection under MIMO is implemented by cross-connections of RFjumpers between RRUs/RFUs and antennas and data switching in the connected LBBP. Thisfunction improves reliability of the entire network with no requirement for additional hardware.It partially achieves self-healing, preventing permanent failures to provide services in cellscaused by faults in a single RRU or RFU.This function is applicable in scenarios where three sectors are configured on three 2T2R RFunits. When an RRU or RFU serving a sector fails, the sector is degraded from MIMO to SingleInput Single Output (SISO), preventing total service failure in the entire sector. At the sametime, another sector using the RRU or RFU is also degraded from MIMO to SISO. After thefault 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. Thecable 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



27

l In the uplink as shown in Figure 8-1, the CPRI ports receive data from RRU 0 and RRU

1. After user plane data of sector 0 is separated from data of the other sectors, the user planedata of sector 0 is sent to the module in the LBBP that processes data of sector 0.

l In the downlink as shown in Figure 8-1, user plane data of sector 0 in the LBBP is sentthrough different CPRI ports to RRU 0 and RRU 1.

l If RRU 0 shown in Figure 8-1 is faulty, user plane data of sector 0 can be exchangedthrough RRU 1.

OM Channel BackupAn 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 theapplication layer, and the eNodeB checks channel connectivity based on results of handshakeswith the M2000. If the M2000 detects that the active channel is disconnected, the M2000 initiatesa channel switchover through the standby channel, instructing the eNodeB to perform theswitchover. The eNodeB automatically switches from the route for the active channel to theroute for the standby channel.

Route BackupRoute backup enhances transmission reliability.Primary and secondary routes are two routes with the same destination address but differentnext-hop IP addresses. The primary/secondary roles of two routes are determined by routepriorities. A high priority represents the primary route, and a low priority represents thesecondary route. An eNodeB selects a reachable route and, if both routes are reachable, theprimary route to send packets. Figure 8-2 shows an example of route backup. In the figure, theIP addresses are port IP addresses.

Figure 8-2 Route backup

8.2 Hardware ReliabilityHardware reliability is ensured by the anti-misinsertion design of boards, overtemperatureprotection, reliable power supply, and surge protection design.



28

Anti-misinsertion Design of BoardsWhen a board of one type is inserted into a slot for another type of board, the board cannotconnect to the backplane. This protects the equipment from damage.

Overtemperature ProtectionWhen 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 protectsPA from damage caused by overtemperature.

Reliable Power SupplyThe reliable power supply is achieved using the following techniques:l Support for wide-range voltages and surge protectionl Power failure protection for programs and datal Protection of power supply against overvoltage, overcurrent, and reverse connection of

positive and negative poles on boardsl Support for a maximum configuration of two UPEUs in an eNodeB to provide 1+1

redundancy

Surge Protection DesignSurge protection is applied to AC and DC power ports and various input and output signal portssuch as E1/T1 and FE/GE ports of eNodeBs.

8.3 Software ReliabilitySoftware reliability is ensured by the redundancy of important files, data, and boards and by thepowerful tolerance of software errors.

RedundancyTo ensure proper operation of the eNodeB when errors occur in these files and data, the eNodeBprovides 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 isabnormal, the eNodeB switches to the backup version.

l Redundancy of data configuration files: An eNodeB stores data configuration files indifferent areas to provide redundancy. If a current file is damaged, the eNodeB can continueworking properly by loading the backup file.

l Redundancy of boards: Two boards of the same type can work in active/standby mode.When the active board fails or is faulty, the standby board takes over, ensuring properoperation of the eNodeB.

Error Tolerance CapabilityWhen software errors occur, the eNodeB will not collapse, because of its self-healing capability.The software error tolerance covers the following aspects:



29

l Scheduled checks of key resources: The eNodeB performs occupancy checks on softwareresources. If resource hang-up occurs in an eNodeB due to software errors, the eNodeBcan release the unavailable resources and export logs and alarms.

l Task monitoring: When software is running, the eNodeB checks for internal software errorsand some hardware faults by monitoring processes and tasks. When an error occurs, analarm is reported and self-healing measures are taken to restore the task.

l Data check: The eNodeB performs scheduled or event-triggered data consistency checksand restores data consistency selectively or preferentially. In addition, the eNodeBgenerates related logs and alarms.

l Watchdog: The eNodeB can detect software errors by using software and hardwarewatchdogs. When an error is detected, the eNodeB resets automatically.



30

9 eNodeB TopologiesThis chapter describes eNodeB topologies on the S1 and CPRI interfaces.

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

eNodeBTechnical Description 9 eNodeB Topologies


31

Figure 9-1 Topologies on the S1 interface

Table 9-1 describes the characteristics of the three topologies.



32

Table 9-1 Topologies on the S1 interfaceTopology

Advantage Disadvantage

Startopology

l Each eNodeB is connected directly toan MME through a transportnetwork. Therefore, this simpletopology features easy engineering,maintenance, and capacityexpansion.

l Each eNodeB exchanges data withthe MME directly. Signals travelthrough only a few nodes, andtherefore network reliability is high.

Compared with the other two topologies,the star topology requires more transportresources.

Chaintopology

The costs of transport equipment,engineering, and transport line lease arerelatively low.

l Signals travel through many nodes,and therefore network reliability islow.

l Each lower-level eNodeB occupiessome transmission bandwidth of itsupper-level eNodeB. Reliability ofthe upper-level eNodeB affectsoperation of the lower-level eNodeB.

Treetopology

The costs of transport equipment,engineering, and transport line lease arerelatively low.

l Signals travel through many nodes,and therefore network reliability islow.

l Each lower-level eNodeB occupiessome transmission bandwidth of itsupper-level eNodeB. Reliability ofthe upper-level eNodeB affectsoperation of the lower-level eNodeB.

Topologies on the CPRI InterfaceFrequency division duplex (FDD) RRUs support the following topologies: star, chain, hotbackup ring, intra-board cold backup ring, and inter-board cold backup ring. RFUs support thestar and hot backup ring topologies.Time division duplex (TDD) RRUs support the star topologies and the topologies for intra-boardload 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.



33

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.



34

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.



35

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.



36

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 interfaceTopology

Advantage Disadvantage Remarks

Startopology

l This topology featureshigh reliability. Faultsin an RRU/RFU oroptical fiber affect onesector at most.

l This simple topologyfacilitates installationand maintenance.

This topology requires arelatively large amount oftransport resources.

-

Chaintopology

This topology requiresrelatively low costs oftransport equipment.

l Limitations are appliedto the number of levelsin a chain and thedistance between unitsin a chain.

l Any fault on theforwarding link of anupper-level RRUaffects the operations ofits lower-level RRUs.

l Cascading between anRFU and an RRU is notsupported.

l A chain supports onlyone rate at a time,because interconnectedCPRI ports on twoRRUs in a chain mustwork at the same rate.



37

Topology

Advantage Disadvantage Remarks

Ringtopology

This topology provideshigh transmissionreliability.

l Limitations are appliedto the number of levelsin a ring and thedistance between unitsin a ring.

l Any fault on theforwarding link of anupper-level RRUaffects the operations ofits lower-level RRUs. Ifa fault occurs, servicescarried on the lower-level RRUs restore inreverse direction of thering. The maximuminterruption duration is20 minutes.

The ring topology is aredundancy type of thechain topology.

Topologyforloadsharing

l This topology provideshigh transmissionreliability.

l A relatively largebandwidth of a cell issupported at CPRIports.

This topology requires arelatively large amount oftransport resources.

-



38

10 Typical Hardware Configurations of aneNodeB

About This Chapter

This chapter describes the hardware configurations of an eNodeB.

10.1 Typical Hardware Configurations and Subrack NumbersThis section describes the typical hardware configurations and the mapping between hardwarecomponents and their subrack numbers.10.2 Hardware Configurations of BTS3900 LTEThis section describes the positions and types of the components of BTS3900 LTE in typicalconfigurations.10.3 Hardware Configurations of BTS3900A LTEThis section describes the positions and types of the components of BTS3900A LTE in typicalconfigurations.10.4 Hardware Configurations of BTS3900L LTEThis section describes the positions and types of the components of BTS3900L LTE in typicalconfigurations.10.5 Hardware Configurations of DBS3900 LTEThis section describes the hardware configurations of DBS3900 LTE in typical cases.10.6 Hardware Configurations of DBS3900 LTE TDDThis section describes the hardware configurations of DBS3900 LTE TDD in typical cases.

eNodeBTechnical Description 10 Typical Hardware Configurations of an eNodeB


39

10.1 Typical Hardware Configurations and SubrackNumbers

This section describes the typical hardware configurations and the mapping between hardwarecomponents and their subrack numbers.

Hardware Quantities in Typical ConfigurationsTable 10-1 lists the number of components of a frequency division duplex (FDD) eNodeB intypical 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 configurationsConfiguration MIMO Quantity of

LBBPsQuantity of RRUs/RFUs

3 x 5 MHz/10 MHz 4 x 2 MIMO 1 63 x 15 MHz/20 MHz 4 x 2 MIMO 3 66 x 5 MHz/10 MHz 2 x 2 MIMO 1 66 x 5 MHz/10 MHz 2 x 2 MIMO 2 12 (MRFUs)3 x 15 MHz/20 MHz 2 x 2 MIMO 1 3

Or 6, if MRFUs arerequired

3 x 5 MHz/10 MHz 2 x 2 MIMO 1 6 (MRFUs)

Table 10-2 Hardware quantities of a TDD eNodeB in typical configurationsConfiguration MIMO Quantity of

LBBPsQuantity of RRUs

3 x 10 MHz 2 x 2 MIMO 1 33 x 10 MHz 4 x 2 MIMO 1 33 x 20 MHz 2 x 2 MIMO 1 33 x 20 MHz 4 x 2 MIMO 3 33 x 10 MHz 4T4R

beamforming1 3

3 x 20 MHz 4T4Rbeamforming

3 3



40

NOTEA x B MHz indicates that the eNodeB is configured with A cells with the cell bandwidth of B MHz. xTyRindicates that each cell uses x transmit (TX) channels and y receive (RX) channels. m x n MIMO indicatesthat each cell uses m transmit (TX) channels and n receive (RX) channels. For example, 3 x 10 MHz and4T4R indicates that the eNodeB is configured with three cells of 10 MHz bandwidth, and each cell usesfour TX channels and four RX channels.

Definitions of Subrack NumbersSubrack numbers are defined for components of an eNodeB for operation, administration, andmaintenance.l The fan monitoring unit (FMU) shown in the following figures is the name of the FAN unit

used in operation and maintenance.l The temperature control unit (TCU) shown in the following figures is the name of the central

monitoring unit type A (CMUA) used in operation and maintenance.l The subrack number of the BBU3900 components is the same as the subrack number of

BBU3900.Table 10-3 lists the mapping between eNodeB models and cabinets. Table 10-4 shows thesubrack numbers of cabinets.

Table 10-3 Mapping between eNodeB models and cabinetseNodeB Model Cabinet UsedBTS3900 LTE BTS3900 (Ver.B) and BTS3900 (Ver.C) cabinetsBTS3900L LTE BTS3900L (Ver.B) and BTS3900L (Ver.C) cabinetsBTS3900A LTE 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

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

DBS3900 LTETDD

APM30H (Ver.B), APM30H (Ver.C), TMC11H (Ver.B), TMC11H(Ver.C), IBBS200D/IBBS200T (Ver.B), and IBBS200D/IBBS200T(Ver.C) cabinets



41

Table 10-4 Subrack numbersCabinet Subrack NumberBTS3900 (Ver.B)and BTS3900(Ver.C) cabinets



42

Cabinet Subrack NumberBTS3900L (Ver.B)and BTS3900L(Ver.C) cabinets



43

Cabinet Subrack NumberAPM30H (Ver.B)and APM30H(Ver.C) cabinets

RFC (Ver.B) andRFC (Ver.C)cabinets



44

Cabinet Subrack NumberTMC11H (Ver.B)and TMC11H(Ver.C) cabinets

IBBS200D/IBBS200T (Ver.B)and IBBS200D/IBBS200T (Ver.C)cabinets

10.2 Hardware Configurations of BTS3900 LTEThis section describes the positions and types of the components of BTS3900 LTE in typicalconfigurations.

Installation PositionsFigure 10-1 shows the positions of the components of BTS3900 LTE in typical configurations.



45

Figure 10-1 Positions of the components of BTS3900 LTE in typical configurations

35MHz/10MHz 42 MIMOLMPTLBBPcLRFU

65MHz/10MHz 22 MIMO

315MHz/20MHz 42 MIMO


Hardware ConfigurationsFigure 10-2, Figure 10-3, and Figure 10-4 show the hardware configurations of BTS3900 LTEin the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2 x 2MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.



46

Figure 10-2 Hardware configuration of BTS3900 LTE in the case of 3 x 15 MHz/20 MHz, 2 x2 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.




47


10.3 Hardware Configurations of BTS3900A LTEThis section describes the positions and types of the components of BTS3900A LTE in typicalconfigurations.

Installation PositionsFigure 10-5 shows the positions of the components of BTS3900A LTE in typical configurations.



48

Figure 10-5 Positions of the components of BTS3900A LTE in typical configurations

315MHz/20MHz 22 MIMO65MHz/10MHz 22 MIMO

35MHz/10MHz 42 MIMO 315MHz/20MHz 42 MIMO

LMPT

LBBPcLRFU

Hardware ConfigurationsFigure 10-6, Figure 10-7, and Figure 10-8 show the hardware configurations of BTS3900ALTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2x 2 MIMO; (3) 3 x 5 MHz/10 MHz, 4 x 2 MIMO.



49

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

NOTE


Figure 10-7 Hardware configuration of BTS3900A LTE in the case of 6 x 5 MHz/10 MHz, 2 x2 MIMO



50

Figure 10-8 Hardware configuration of BTS3900A LTE in the case of 3 x 5 MHz/10 MHz, 4 x2 MIMO

10.4 Hardware Configurations of BTS3900L LTEThis section describes the positions and types of the components of BTS3900L LTE in typicalconfigurations.

Installation PositionsFigure 10-9 shows the positions of the components of BTS3900L LTE in typical configurations.



51

Figure 10-9 Positions of the components of BTS3900L LTE in typical configurations


LMPT

LBBPcLRFU

65MHz/10MHz 22 MIMO

35MHz/10MHz 42 MIMO 315MHz/20MHz 42 MIMO 65MHz/10MHz 22 MIMO

MRFU



52

Hardware ConfigurationsFigure 10-10, Figure 10-11, and Figure 10-12 show the hardware configurations of BTS3900LLTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2x 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, 2x 2 MIMO



53

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

10.5 Hardware Configurations of DBS3900 LTEThis 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 DBS3900LTE in the following cases: (1) 3 x 15 MHz/20 MHz, 2 x 2 MIMO; (2) 6 x 5 MHz/10 MHz, 2x 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, 2x 2 MIMO



54

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

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



55

10.6 Hardware Configurations of DBS3900 LTE TDDThis 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 inthe 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 2MIMO

Figure 10-17 Hardware configuration of DBS3900 LTE TDD in the case of 3 x 20 MHz, 4 x 2MIMO



56

11 Technical Specifications of RadioFrequency Units

About This Chapter

This chapter describes the technical specifications of radio frequency (RF) units, such as theworking mode, frequency band, output power, and antenna capability.

11.1 Technical Specifications of RFUsAn RFU is a radio frequency unit. One or more RFUs constitute the radio frequency (RF) partof 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 RRUsAn RRU is a remote radio unit. One or more RRUs constitute the radio frequency (RF) part ofa distributed eNodeB. RRUs can be installed on a pole, wall, or stand. They can also be installedclose 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.

eNodeBTechnical Description 11 Technical Specifications of Radio Frequency Units


57

11.1 Technical Specifications of RFUsAn RFU is a radio frequency unit. One or more RFUs constitute the radio frequency (RF) partof 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 LRFUThis section describes the technical specifications of the LRFU.

Working Mode and Frequency BandTable 11-1 describes the working mode and frequency bands of the LRFU.

Table 11-1 Working mode and frequency bands of the LRFUType Worki

ngMode

Frequency Band(MHz)

RX Band (MHz) TX Band (MHz)

LRFU LTEFDD

AWS (band 4) 1710 to 1755 2110 to 21552600 (band 7) Band C: 2500 to 2520 Band C: 2620 to 2640

Band D: 2510 to 2560 Band D: 2630 to 2680Band E: 2550 to 2570 Band E: 2670 to 2690

RF SpecificationsTable 11-2 describes the RF specifications of the LRFU.

Table 11-2 RF specifications of the LRFUType RX and TX

ChannelsCapacity Output Power

LRFU 2T2R An LRFU supports one carrier. Thebandwidth of each carrier can be:l 1.4 MHz, 3 MHz, 5 MHz, 10

MHz, 15 MHz, or 20 MHz in theAWS band

l 5 MHz, 10 MHz, 15 MHz, or 20MHz in the 2600 MHz band

2 x 40 W

NOTEA x B W indicates that the eNodeB uses A transmit (TX) channels and the output power of each channel is B W.



58

Surge Protection SpecificationsTable 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/20s.

l All the items of discharge current, unless otherwise specified as the maximum discharge current, refer tothose of the nominal discharge current.

Table 11-3 Surge protection specifications for the ports on the LRFUPort Applicatio

n ScenarioSurge Protection Mode Specification

DC powersupplysocket

All Surge Differentialmode

2 kV (1.2/50 s)

Commonmode

4 kV (1.2/50 s)

Surgecurrent

Differentialmode

10 kA

Commonmode

20 kA

Antenna port All Surgecurrent

Differentialmode

8 kA

Commonmode

40 kA

Monitoringport

All Surgecurrent

Differentialmode

3 kA

Commonmode

5 kA

Antenna CapabilityTable 11-4 describes the antenna capability of the LRFU.

Table 11-4 Antenna capability of the LRFUType TMA Support Capability RET Antenna Support

CapabilityLRFU TMA supported AISG2.0-complied RET

antennas supported



59

NOTEIf 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 LRFUeThis section describes the technical specifications of the LRFUe.

Working Mode and Frequency BandTable 11-5 describes the working mode and frequency bands of the LRFUe.

Table 11-5 Working mode and frequency bands of the LRFUeType Worki

ngMode

Frequency Band(MHz)

RX Band (MHz) TX Band (MHz)

LRFUe LTEFDD

DD 800MHz (band20)

832 to 862 791 to 821

RF SpecificationsTable 11-6 describes the RF specifications of the LRFUe.

Table 11-6 RF specifications of the LRFUeType RX and TX

ChannelsCapacity Output Power

LRFUe 2T2R An LRFUe supports two carriers.The bandwidth of each carrier canbe 5 MHz, 10 MHz, 15 MHz, or 20MHz. The total bandwidth of twocarriers cannot exceed 30MHz.

2 x 60 W

NOTEA x B W indicates that the eNodeB uses A transmit (TX) channels and the output power of each channel is B W.

Surge Protection SpecificationsTable 11-7 describes the surge protection specifications for the ports on the LRFUe.

NOTE

l Unless otherwise specified, the surge protection specifications are based on the surge waveform of 8/20s.

l All the items of discharge current, unless otherwise specified as the maximum discharge current, refer tothose of the nominal discharge current.



60

Table 11-7 Surge protection specifications for the ports on the LRFUePort Applicatio

n ScenarioSurge Protection Mode Specification

DC powersupplysocket

All Surge Differentialmode

2 kV (1.2/50 s)

Commonmode

4 kV (1.2/50 s)

Surgecurrent

Differentialmode

10 kA

Commonmode

20 kA

Antenna port All Surgecurrent

Differentialmode

8 kA

Commonmode

40 kA

Monitoringport

All Surgecurrent

Differentialmode

3 kA

Commonmode

5 kA

Antenna CapabilityTable 11-8 describes the antenna capability of the LRFUe.

Table 11-8 Antenna capability of the LRFUeType TMA Support Capability RET Antenna Support

CapabilityLRF

Documents

eNodeB Technical Description(V100R004C00_03)(PDF)-EN.pdf