aas(eran8.1_03)

eRAN

AAS Feature Parameter Description

Issue 03Date 2015-08-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. 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 respectiveholders. 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 orrepresentations of 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 a 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 (2015-08-31) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

Contents

1 About This Document.................................................................................................................. 11.1 Scope.............................................................................................................................................................................. 11.2 Intended Audience..........................................................................................................................................................11.3 Change History............................................................................................................................................................... 22 Overview......................................................................................................................................... 52.1 Introduction.................................................................................................................................................................... 52.2 Benefits...........................................................................................................................................................................52.3 Architecture.................................................................................................................................................................... 52.3.1 AAS Hardware............................................................................................................................................................ 52.3.2 RET..............................................................................................................................................................................72.3.3 AAS Configuration......................................................................................................................................................92.4 AAS Features................................................................................................................................................................113 AAS Virtual Four Uplink Channels for LTE..........................................................................124 AAS User Specific Tilting for LTE...........................................................................................145 AAS Vertical Multiple Sectors for LTE...................................................................................156 AAS Dividual Tilts by Carrier for LTE................................................................................... 177 AAS RAT Specific Tilting (LTE).............................................................................................. 198 Related Features...........................................................................................................................209 Network Impact........................................................................................................................... 219.1 AAS Virtual Four Uplink Channels for LTE................................................................................................................ 219.1.1 System Capacity........................................................................................................................................................ 219.1.2 Network Performance................................................................................................................................................219.1.3 NEs............................................................................................................................................................................ 219.1.4 Hardware................................................................................................................................................................... 219.1.5 Inter-NE Interfaces.................................................................................................................................................... 219.1.6 Operation and Maintenance.......................................................................................................................................229.2 AAS User Specific Tilting for LTE.............................................................................................................................. 239.2.1 System Capacity........................................................................................................................................................ 239.2.2 Network Performance................................................................................................................................................239.2.3 NEs............................................................................................................................................................................ 23

eRANAAS Feature Parameter Description Contents


ii

9.2.4 Hardware................................................................................................................................................................... 239.2.5 Inter-NE Interfaces.................................................................................................................................................... 239.2.6 Operation and Maintenance.......................................................................................................................................249.3 AAS Vertical Multiple Sectors for LTE........................................................................................................................249.3.1 System Capacity........................................................................................................................................................ 249.3.2 Network Performance................................................................................................................................................249.3.3 NEs............................................................................................................................................................................ 259.3.4 Hardware................................................................................................................................................................... 259.3.5 Inter-NE Interfaces.................................................................................................................................................... 259.3.6 Operation and Maintenance.......................................................................................................................................259.4 AAS Dividual Tilts by Carrier for LTE........................................................................................................................ 259.4.1 System Capacity........................................................................................................................................................ 259.4.2 Network Performance................................................................................................................................................259.4.3 NEs............................................................................................................................................................................ 269.4.4 Hardware................................................................................................................................................................... 269.4.5 Inter-NE Interfaces.................................................................................................................................................... 269.4.6 Operation and Maintenance.......................................................................................................................................269.5 AAS RAT Specific Tilting (LTE)................................................................................................................................. 269.5.1 System Capacity........................................................................................................................................................ 269.5.2 Network Performance................................................................................................................................................279.5.3 NEs............................................................................................................................................................................ 279.5.4 Hardware................................................................................................................................................................... 279.5.5 Inter-NE Interfaces.................................................................................................................................................... 279.5.6 Operation and Maintenance.......................................................................................................................................2710 Engineering Guidelines........................................................................................................... 2810.1 Deployment of Passive Antennas............................................................................................................................... 2910.1.1 Requirements........................................................................................................................................................... 2910.1.2 Data Preparation...................................................................................................................................................... 2910.1.3 Precautions...............................................................................................................................................................3110.1.4 Hardware Adjustment..............................................................................................................................................3110.1.5 Initial Configuration................................................................................................................................................ 3110.1.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................3110.1.5.2 Using the CME to Perform Batch Configuration for Existing NodeBs............................................................... 3310.1.5.3 Using the CME to Perform Single Configuration................................................................................................ 3310.1.5.4 Using MML Commands.......................................................................................................................................3310.1.5.5 MML Command Examples.................................................................................................................................. 3410.1.6 Activation Observation............................................................................................................................................3410.2 Deployment of Active Antennas................................................................................................................................ 3410.2.1 Requirements........................................................................................................................................................... 3510.2.2 Data Preparation...................................................................................................................................................... 3510.2.3 Precautions...............................................................................................................................................................3610.2.4 Hardware Adjustment..............................................................................................................................................36



iii

10.2.5 Initial Configuration................................................................................................................................................ 3610.2.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................3610.2.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................. 3710.2.5.3 Using the CME to Perform Single Configuration................................................................................................ 3810.2.5.4 Using MML Commands.......................................................................................................................................3810.2.5.5 MML Command Examples.................................................................................................................................. 3810.2.6 Activation Observation............................................................................................................................................3910.3 Deployment of AAS Virtual Four Uplink Channels for LTE.....................................................................................3910.3.1 Application Suggestions.......................................................................................................................................... 4010.3.2 Required Information.............................................................................................................................................. 4010.3.3 Planning................................................................................................................................................................... 4010.3.4 Deployment............................................................................................................................................................. 4010.3.4.1 Requirements........................................................................................................................................................ 4010.3.4.2 Data Preparation................................................................................................................................................... 4010.3.4.3 Precautions............................................................................................................................................................4010.3.4.4 Hardware Adjustment...........................................................................................................................................4110.3.4.5 Initial Configuration............................................................................................................................................. 4110.3.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................4110.3.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 4310.3.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 4310.3.4.5.4 Using MML Commands....................................................................................................................................4310.3.4.5.5 MML Command Examples............................................................................................................................... 4410.3.4.6 Activation Observation.........................................................................................................................................4510.3.5 Performance Monitoring..........................................................................................................................................4610.3.6 Parameter Optimization...........................................................................................................................................4710.3.7 Troubleshooting....................................................................................................................................................... 4710.4 Deployment of AAS User Specific Tilting for LTE................................................................................................... 4710.4.1 Application Suggestions.......................................................................................................................................... 4710.4.2 Required Information.............................................................................................................................................. 4810.4.3 Planning................................................................................................................................................................... 4810.4.4 Deployment............................................................................................................................................................. 4910.4.4.1 Requirements........................................................................................................................................................ 4910.4.4.2 Data Preparation................................................................................................................................................... 4910.4.4.3 Precautions............................................................................................................................................................4910.4.4.4 Hardware Adjustment...........................................................................................................................................4910.4.4.5 Initial Configuration............................................................................................................................................. 4910.4.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................4910.4.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 5010.4.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 5010.4.4.5.4 Using MML Commands....................................................................................................................................5010.4.4.5.5 MML Command Examples............................................................................................................................... 5110.4.4.6 Activation Observation.........................................................................................................................................52



iv

10.4.5 Performance Monitoring..........................................................................................................................................5210.4.6 Parameter Optimization...........................................................................................................................................5310.4.7 Troubleshooting....................................................................................................................................................... 5410.5 Deployment of AAS Vertical Multiple Sectors for LTE.............................................................................................5410.5.1 Application Suggestions.......................................................................................................................................... 5410.5.2 Required Information.............................................................................................................................................. 5410.5.3 Planning................................................................................................................................................................... 5410.5.4 Deployment............................................................................................................................................................. 5610.5.4.1 Requirements........................................................................................................................................................ 5610.5.4.2 Data Preparation................................................................................................................................................... 5610.5.4.3 Precautions............................................................................................................................................................5610.5.4.4 Hardware Adjustment...........................................................................................................................................5610.5.4.5 Initial Configuration............................................................................................................................................. 5610.5.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................5610.5.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 5710.5.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 5710.5.4.5.4 Using MML Commands....................................................................................................................................5710.5.4.5.5 MML Command Examples............................................................................................................................... 5810.5.4.6 Activation Observation.........................................................................................................................................5910.5.5 Performance Monitoring..........................................................................................................................................5910.5.6 Parameter Optimization...........................................................................................................................................6110.5.7 Troubleshooting....................................................................................................................................................... 6110.6 Deployment of AAS Dividual Tilts by Carrier for LTE............................................................................................. 6110.6.1 Application Suggestions.......................................................................................................................................... 6110.6.2 Required Information.............................................................................................................................................. 6210.6.3 Planning................................................................................................................................................................... 6210.6.4 Deployment............................................................................................................................................................. 6210.6.4.1 Requirements........................................................................................................................................................ 6210.6.4.2 Data Preparation................................................................................................................................................... 6210.6.4.3 Precautions............................................................................................................................................................6210.6.4.4 Hardware Adjustment...........................................................................................................................................6210.6.4.5 Initial Configuration............................................................................................................................................. 6210.6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................6210.6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 6310.6.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 6310.6.4.5.4 Using MML Commands....................................................................................................................................6310.6.4.5.5 MML Command Examples............................................................................................................................... 6410.6.4.6 Activation Observation.........................................................................................................................................6510.6.5 Performance Monitoring..........................................................................................................................................6610.6.6 Parameter Optimization...........................................................................................................................................6610.6.7 Troubleshooting....................................................................................................................................................... 6610.7 Deployment of AAS RAT Specific Tilting (LTE)...................................................................................................... 66



v

10.7.1 Application Suggestions.......................................................................................................................................... 6710.7.2 Required Information.............................................................................................................................................. 6710.7.3 Planning................................................................................................................................................................... 6710.7.4 Deployment............................................................................................................................................................. 6710.7.4.1 Requirements........................................................................................................................................................ 6710.7.4.2 Data Preparation................................................................................................................................................... 6710.7.4.3 Precautions............................................................................................................................................................6710.7.4.4 Hardware Adjustment...........................................................................................................................................6810.7.4.5 Initial Configuration............................................................................................................................................. 6810.7.4.6 Activation Observation.........................................................................................................................................6810.7.5 Performance Monitoring..........................................................................................................................................6810.7.6 Parameter Optimization...........................................................................................................................................6810.7.7 Troubleshooting....................................................................................................................................................... 6811 Reference Documents............................................................................................................... 70



vi

1 About This Document1.1 Scope

This document describes the LTE AAS, including its working principles, related features,network impact, and engineering guidelines. The AAS in this document indicates theAAU3902.This document covers the following features:l LOFD-261101 AAS Virtual Four Uplink Channels for LTEl LOFD-261102 AAS User Specific Tilting for LTEl LOFD-261103 AAS Vertical Multiple Sectors for LTEl LOFD-261105 AAS Dividual Tilts by Carrier for LTEl MRFD-261105 AAS RAT Specific Tilting (LTE)Any managed objects (MOs), parameters, alarms, or counters described herein correspond tothe software release delivered with this document. Any future updates will be described in theproduct documentation delivered with future software releases.This document applies to the following types of eNodeBs.

eNodeB Type ModelMacro 3900 series eNodeB

This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,and "eNodeB" refers to LTE FDD eNodeB."AAU3902" in this document refers to the Huawei product of AAS.

1.2 Intended AudienceThis document is intended for personnel who:l Need to understand the features described herein

eRANAAS Feature Parameter Description 1 About This Document


1

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:l Feature change

Changes in features of a specific product version.l Editorial change

Changes in wording or addition of information that was not described in the earlierversion.

eRAN8.1 03 (2015-08-31)This issue includes the following changes.

Change Type Change Description ParameterChange

Feature change None NoneEditorial change Added relationships between the

logical channel and logical port. Fordetails, see 2.3.3 AASConfiguration.

None



Feature change None None



2


Editorial change l Added descriptions onconfigurations when multipleAARUs are configured on theAAS. For details, see 10.1.5Initial Configuration,10.2.5Initial Configuration,10.3.4.5Initial Configuration,10.4.4.5Initial Configuration,10.5.4.5Initial Configuration and10.6.4.5 Initial Configuration.

l Modified the description on angledifference between 1 and 2 ofbeams 1 and 2. For details, see 5AAS Vertical Multiple Sectorsfor LTE.

None



Feature change Changed the hardware specificationdescription to keep consistency withthat in the MIMO FeatureParameter Description. For details,see 10.3.3 Planning,10.4.3Planning and 10.5.3 Planning.

None

Editorial change None None

eRAN8.1 Draft A (2015-01-15)Compared with Issue 04 (2014-11-15) of eRAN7.0, this issue includes the following changes.



3

Change Type Change Description Parameter ChangeFeature change Modified MML command

examples and added celloperator configurationcommands. For details, see10.3.4.5.5 MML CommandExamples,10.4.4.5.5 MMLCommand Examples,10.5.4.5.5 MML CommandExamples and 10.6.4.5.5MML CommandExamples.

None.

Editorial change None. None.



4

2 Overview2.1 Introduction

The AAS is a new type of radio frequency (RF) module that uses common public radiointerface (CPRI) ports to connect to baseband signal processing boards in the same way as theremote radio unit (RRU) and radio frequency unit (RFU). The AAS can incorporate thefunctions of RF modules and antennas. Each AAS has multiple transmit and receive channels.Beams from an AAS can be adjusted on both vertical and horizontal planes. Beamadjustments help improve radio coverage and increase network capacity.

2.2 BenefitsThe AAS provides the following benefits:l Saves antenna space

The AAS occupies less antenna space than an RRU and traditional antenna, therebyhelping operators free up more antenna space for other devices.

l Supports the beamforming functionThe AAS can be used to increase network capacity in heavy traffic areas.

2.3 Architecture2.3.1 AAS Hardware

The AAS has a modular design. Figure 2-1 shows its logical structure.

eRANAAS Feature Parameter Description 2 Overview


5

Figure 2-1 AAS logical structure

NOTEThe AASs of different models have different structures. For more information, see associated AAShardware descriptions.

The AAS consists of the following units:l Active Antenna-Antenna Unit (AAAU): includes active and passive antennas. Passive

antennas can work for both the base station to which the AAS is connected and otherbase stations.

l Active Antenna-Management Unit (AAMU): controls the AAS. The AAMU connects tothe BBU using common public radio interface (CPRI) ports and to the AAS's other unitsusing cables.

l Active Antenna Passive Unit (AAPU): serves as the RF signal interface of the AAS,used to provide an interface for external RRUs/RFUs and transfer RF signals.

l Active Antenna-Radio Unit (AARU): serves as the RF subsystem of the AAS, used toimplement the transceiver function and provide the phase calibration function.

l Active Antenna-Cover Unit (AACU): protects the AAAU from rainwater and dust. If noAARUs are configured, one AACU must be configured.

Table 2-1 lists AAU3902 slot configuration.



6

Table 2-1 AAU3902 slot configurationSlotNo.

Unit Supported Frequency Bands Supported Mode

0 AAMU N/A UMTS, LTE FDD,and GL

1 AARU or AACU AARU: 2.1 GHz UMTS2 AAPU 1.8 GHz, 2.1 GHz, and 2.6 GHz

(An AAPU supports the threefrequency bands.)

N/A

3 AARU or AACU AARU: 1.8 GHz LTE FDD and GL

2.3.2 RETThe logical objects of the remote electrical tilt (RET) function for passive antennas are RETsubunits, and the logical objects of the RET function for active antennas are virtual RETsubunits.

RET for Passive AntennasThe RET function for passive antennas implements external or internal control, depending onwhich device the AAS is connected to.The RET function implements external control when the AAAU is connected to RRUs usingRF feeders and the ALD control line to control the RET. (Note that these RRUs can belong toeither the same base station as the AAS or to a different base station.) External controlcomplies with the Antenna Interface Standards Group (AISG) protocol and requires RETsignal processing of the remote control units (RCUs) in the AAAU.The RET function implements internal control when the AAMU connects to the BBU using aCPRI cable. This connection method is used because the AAAU does not have AISG ports.Internal control requires the AAMU to use one CPRI port to forward RET signals to theRCUs for signal processing.



7

Figure 2-2 External and internal control

For details about the RET function for passive antennas, see ALD Management FeatureParameter Description.

RET for Active AntennasThe RET function for active antennas adjusts the downlink downtilt angles of beams fromAASs by modifying the downtilt angle attribute of the related virtual RET subunits. Featuresrelated to the RET function for active antennas are described later in this document.The RET function for active antennas requires that the BBU connect to the AAMU, as shownin Figure 2-3.Connection method required by RET for active antennas



8

Figure 2-3 Connection method required by RET for active antennas

2.3.3 AAS ConfigurationThe AAS configuration is different from the RRU configuration. Figure 2-4 shows thedifferent configuration objects of an AAS compared to an RRU.

Figure 2-4 Configuration objects of AAS and RRU

NOTEIn Figure 2-4, "1:x" indicates the ratio of the number of left configuration objects to the number of rightconfiguration objects. The value of a ranges from 1 to 8. The values of b and c range from 1 to 8.

As shown in Figure 2-4, one AAS has the following configuration objects:



9

l AAS: used to set physical attributes of the module, such as the subrack number.l AARU: corresponds to the physical AARU and used to set its physical attributes, such as

the slot number, working mode, and number of transmit or receive channels in theAARU hardware.

l VRET: automatically created with the AARU configuration object and used to controlthe number of virtual RET subunits. VRET is the parent object of VRETSUBUNIT.

l VRETSUBUNIT: automatically created with the AARU configuration object. VREThas eight configuration objects VRETSUBUNIT by default. Each VRETSUBUNITcorresponds to a virtual RET subunit. Each VRETSUBUNIT can be configured with 1,2, or 4 connection ports. Connection ports are numbered in an RXY format. The meaningof x and y is as follows:

Y indicates the number of a logical channel on the horizontal plane and can be set toA or B. A indicates +45 polarization; B indicates -45 polarization. X indicates the number of a logical port on the vertical plane and is an integer

ranging from 0 to 7. Each logical channel can have multiple logical ports. Beamharacteristics can be defined for each port separately. Downtilt angles on thevertical plane can be defined for AAU3902.

Figure 2-5 shows the diagram of logical channels and logical ports.

Figure 2-5 Diagram of logical channels and logical ports

Take AAU3902 as an example. The relationships between the logical channel, logical port,and antenna polarization are as follows.

AntennaPolarization

LogicalChannel

Logical Port

+45 A R0A R1A R2A R3A R4A R5A R6A R7A-45 B R0B R1B R2B R3B R4B R5B R6B R7B



10

NOTE1. Either logical channel A or B of the AAU3902 can transmit and receive signals simultaneously.2. The AAU3902 does not support the modification of the TX logical port switch at the channel level

by running the MOD TXBRANCH command but supports the modification of the TX logical portswitch at the module level.

3. The AAU3902 does not support the modification of the RX logical port switch at both the channellevel and the module level by running the MOD RXBRANCH command.

2.4 AAS FeaturesTable 2-2 lists the AAS features and their version information.

Table 2-2 AAS features and version informationFeature Name AAU3902 (1.8Ghz, LTE)AAS Virtual Four Uplink Channels for LTE SRAN8.0 and later versionsAAS User Specific Tilting for LTE SRAN8.0 and later versionsAAS Vertical Multiple Sectors for LTE SRAN8.0 and later versionsAAS Dividual Tilts by Carrier for LTE SRAN8.0 and later versionsAAS RAT Specific Tilting (LTE) SRAN9.0 and later versions

NOTEThe downtilt angle difference between AAS beams is restricted by the maximum capability of the digitaltilt (DT). All such differences among features or within any feature comply with this restriction. Formore information, see "Technical Specifications of AAUs" in 3900 Series Base Station TechnicalDescription.



11

3 AAS Virtual Four Uplink Channels for LTEThis chapter describes LOFD-261101 AAS Virtual Four Uplink Channels for LTE.To implement 4-antenna receive diversity, a traditional RRU/RFU uses two dual-polarizedantennas, whereas an AAS with this feature uses only one active antenna polarized at +45and -45. Specifically, the AAS assigns different weights to received signals, forms twouplink beams on the vertical plane in each polarization direction, and obtains a total of fourchannels of signals. In this way, the AAS provides receive diversity gain, beamforming gain,and interference mitigation gain. The AAS increases uplink throughput and networkperformance.To support this feature, the AAS requires that the four virtual antenna ports (CONNPN1 toCONNPN4) of each virtual RET subunit be bound to the same sector. In addition, the AASrequires that the number of receive antennas in this sector (ANTNUM) be set to 4 so that thesector has a 4-antenna reception (4R) capability. Under this configuration, the AAS generatesa total of four beams, corresponding to four receive ports. Together with LOFD-001005 UL 4-Antenna Receive Diversity, the AAS generates four uplink virtual channels for different UEs.Assume that four antenna ports are named R0A, R0B, R1A, and R1B, where R0A and R1Aare configured in one polarization direction and R0B and R1B in the other polarizationdirection. The generated four uplink channels are shown in Figure 3-1.

eRANAAS Feature Parameter Description 3 AAS Virtual Four Uplink Channels for LTE


12

Figure 3-1 Working principle of AAS Virtual Four Uplink Channels for LTE (side view)

eRANAAS Feature Parameter Description 3 AAS Virtual Four Uplink Channels for LTE


13

4 AAS User Specific Tilting for LTEThis chapter describes LOFD-261102 AAS User Specific Tilting for LTE.The AAS can use an active antenna to form two transmit beams in each polarization directionfor a total of four transmit beams in the two polarization directions. Together withLOFD-001003 DL 4x2 MIMO or LOFD-001060 DL 4x4 MIMO in closed-loop mode, theAAS generates four downlink channels on the vertical plane in a cell.As shown in Figure 4-1, the red beam is a wide beam generated for control channels and theother three beams are narrow beams generated for traffic channels. These narrow beams areformed for different UEs based on the precoding matrix indicators (PMIs) reported by theseUEs and the associated codebooks.This feature increases the signal power of UEs close to the AAS and reduces the interferencewith other cells, thereby increasing system capacity.

Figure 4-1 Working principle of AAS User Specific Tilting for LTE(side view)

eRANAAS Feature Parameter Description 4 AAS User Specific Tilting for LTE


14

5 AAS Vertical Multiple Sectors for LTEThis chapter describes LOFD-261103 AAS Vertical Multiple Sectors for LTEThis feature splits a sector served by AASs into an inner sector and an outer sector. The innerand outer sectors correspond to an inner cell and an outer cell, respectively. These cells usethe same frequency but have overlapping areas.This feature is mainly used to expand downlink capacity in hot spots (possibly due to cellresource insufficiency) when no extra frequencies are available.

NOTETo expand uplink capacity (possibly due to heavy uplink load), use the AAS Virtual Four UplinkChannels for LTE feature described in 3 AAS Virtual Four Uplink Channels for LTE.

In hot spots (such as urban areas), base stations are close together and strong interferenceeasily occurs. After the AAS Vertical Multiple Sectors for LTE feature is applied, the outerand inner cells overlap and these two cells cause strong interference for each other inoverlapping areas. When using this feature in urban areas, adjust the downtilt angles of beamsin these cells to minimize the interference.The area covered by an inner cell is small because of the large downtilt angles of the beams inthe inner cell and interference from the outer cell. The lower the AAS is placed, the smallerthe area covered by the inner cell. With this feature, the throughput in inner cells accounts fora large proportion of the throughput of the entire site.This feature is implemented by setting the ULTILT and DLTILT parameters inVRETSUBUNIT MOs. One beam is split into two (beams 1 and 2) on the vertical plane,corresponding to cells 1 and 2 respectively, as shown in Figure 5-1. The two cells have thesame frequency. For detail of angle difference between 1 and 2 of beams 1 and 2 on thevertical plane, please refer to the 'AAU3902 Technical Specifications' chapter in the 3900Series Base Station Technical Description.

eRANAAS Feature Parameter Description 5 AAS Vertical Multiple Sectors for LTE


15

Figure 5-1 Working principle of AAS Vertical Multiple Sectors for LTE (side view)

eRANAAS Feature Parameter Description 5 AAS Vertical Multiple Sectors for LTE


16

6 AAS Dividual Tilts by Carrier for LTEThis chapter describes LOFD-261105 AAS Dividual Tilts by Carrier for LTE, which is alsoreferred to as carrier specific tilting in this document.The AAS Dividual Tilts by Carrier for LTE feature enables multiple carriers operating atdifferent frequencies on the same frequency band to use different downtilt angles. Carriersthat use smaller downtilt angles deliver contiguous coverage, and carriers that use largerdowntilt angles ensure capacity expansion for hotspots.Figure 6-1 shows the working principle of AAS Dividual Tilts by Carrier for LTE.

Figure 6-1 Working principle of AAS Dividual Tilts by Carrier for LTE (side view)

In Figure 6-1, each carrier has an individual beam, which has a unique downtilt angle. Thesetwo carriers correspond to cells 1 and 2, respectively. The two cells use different frequenciesF1 and F2 on the same frequency band. The downtilt angle of beam 1 is smaller than that ofbeam 2, which reduces the interference among F2 cells and increases network capacity.

eRANAAS Feature Parameter Description 6 AAS Dividual Tilts by Carrier for LTE


17

With the AAS Dividual Tilts by Carrier for LTE feature, operators who have two or morefrequencies can add carriers to cells to expand network capacity. In SRAN8.0 and later, amaximum of eight carriers can be added to a cell.This feature can be used in sector-level network planning or network optimization to obtainoptimal downtilt angles for carriers. Operators determine the downtilt angle of the carrier thatcovers hot spots based on traffic distribution.

eRANAAS Feature Parameter Description 6 AAS Dividual Tilts by Carrier for LTE


18

7 AAS RAT Specific Tilting (LTE)This chapter describes MRFD-261105 AAS RAT Specific Tilting (LTE).In addition to intra-RAT carrier specific tilting, an AAU3902 of SRAN9.0 supports RATspecific tilting.To meet different RAT requirements on coverage and capacity, the AAS generally appliesdifferent downtilt angles to these RATs. An AAU3902 of SRAN9.0 can use one AARU tosupport both GSM and LTE on the 1.8 GHz frequency and performs separate tilting for them.Similar to carrier specific tilting, RAT specific tilting uses the ULTILT and DLTILTparameters in the VRETSUBUNIT MO to control the downtilt angles of two beams on thevertical plane. Beams 1 and 2 correspond to cells 1 and 2 respectively, and the two cells usedifferent RATs and frequencies. Figure 7-1 illustrates RAT specific tilting.

Figure 7-1 Working principle of AAS RAT Specific Tilting (LTE) (side view)

eRANAAS Feature Parameter Description 7 AAS RAT Specific Tilting (LTE)


19

8 Related FeaturesTable 8-1 lists the prerequisite features and mutually exclusive features related to AAS.

Table 8-1 Prerequisite features and mutually exclusive featuresAAS Feature LTE

Prerequisite Feature Mutually Exclusive FeatureAAS Virtual FourUplink Channels forLTE (Vertical)

l LOFD-001005 UL 4-AntennaReceive Diversity

l AAS Vertical MultipleSectors for LTE

AAS User SpecificTilting for LTE

l LOFD-001003 DL 4x2 MIMOl LOFD-001060 DL 4x4 MIMO

l AAS Vertical MultipleSectors for LTE

AAS VerticalMultiple Sectors forLTE

None l AAS Virtual Four UplinkChannels for LTE(Vertical)

l AAS User Specific Tiltingfor LTE

AAS Dividual Tiltsby Carrier for LTE

None None

AAS RAT SpecificTilting (LTE)

None None

NOTE

Mutually exclusive features cannot be activated in the same sector or cell.

eRANAAS Feature Parameter Description 8 Related Features


20

9 Network Impact9.1 AAS Virtual Four Uplink Channels for LTE

9.1.1 System CapacityThis feature increases the uplink cell capacity by 10% to 45% in densely populated, andcommon urban areas, and others.

9.1.2 Network PerformanceThe network performance gain can be evaluated as follows:l In ideal scenarios:

If the inter-site distance is short, this feature lowers the transmit power by 3 dB to 6 dBfor UEs not far from the AAS and therefore conserves UE battery power. In addition,this feature reduces uplink interference and increases uplink network performance.

l In non-ideal scenarios:If the inter-site distance is long, this feature provides higher gain for UEs not far fromthe AAS but lower gain for UEs far from the AAS.

9.1.3 NEsThis feature is implemented on the eNodeB.

9.1.4 HardwareThis feature requires the baseband processing unit be the BBU3900 or BBU3910.This feature requires that the baseband processing unit support 4R.

9.1.5 Inter-NE InterfacesNone.

eRANAAS Feature Parameter Description 9 Network Impact


21

9.1.6 Operation and MaintenanceLicense

Feature ID Feature Name License ControlItem

NE Sales Unit

LOFD-261101 AAS Virtual FourUplink Channelsfor LTE

AAS Virtual FourUplink Channelsfor LTE

eNodeB per RU

Configuration ManagementThe following MML commands and parameters have been introduced on the eNodeB side toaccommodate this feature.

Table 9-1 New MML commandsChangeType

MML Command Description

New ADD AAS Used to add an AAS to an RRU chain or ring.New ADD AARU Used to add an AARU.New MOD VRET Used to modify parameter settings for a managed

object (MO) VRET.New MOD VRETSUBUNIT Used to modify configurations of a virtual RET

subunit.

Table 9-2 New parametersChangeType

MO Parameter ID MML Command Description

New VRETSUBUNIT

ULTILT MODVRETSUBUNIT

Indicates the uplinkdowntilt angle of thevirtual RET subunit.

New VRETSUBUNIT

DLTILT MODVRETSUBUNIT

Indicates the downlinkdowntilt angle of thevirtual RET subunit.

Performance ManagementNone.



22

Fault ManagementTable 9-3 lists the alarms with online help information that was updated after this feature wasintroduced.

Table 9-3 New alarmsChangeType

AlarmID

Alarm Name AlarmSeverity

ApplicableProduct

New 26560 AAS Board Not In Position Major AAU3902New 26561 AAS Hardware Fault Major AAU3902

9.2 AAS User Specific Tilting for LTE9.2.1 System Capacity

This feature provides beamforming gain and inter-cell interference mitigation gain incontinuous coverage areas. In addition, this feature reduces downlink interference withneighboring cells and increases downlink throughput.In the full buffer traffic model, this feature increases the average cell throughput by 15 to 30%in continuous coverage areas if all UEs support downlink 4x2 MIMO.

9.2.2 Network PerformanceThis feature provides positive gain in scenarios with high interference but negative gain forCEUs in scenarios with weak coverage. Compared with traditional 2-antenna transmission(2T), this feature decreases the beamforming gain by approximately 3 dB for the widereference signal (RS) beam and reduces the RS level on the cell edge by approximately 3-5dB.


9.2.4 HardwareThis feature requires that the baseband processing unit be the BBU3900 or BBU3910.This feature requires that the baseband processing unit support 4T.




23



NE Sales Unit

LOFD-261102 AAS User SpecificTilting for LTE

AAS User SpecificTilting for LTE

eNodeB per RU

Configuration ManagementFor a list of MML commands and parameters that have been introduced on the eNodeB sideto accommodate this feature, see Table 9-1 and Table 9-2.


Fault ManagementFor a list of alarms with updated online help information, see Table 9-3.

9.3 AAS Vertical Multiple Sectors for LTE9.3.1 System Capacity

This feature increases uplink and downlink system capacity. The capacity gain depends on thesite height, coverage, and user distribution.In the downlink, the average throughput increases 20% to 40%. If users are evenly distributed,this feature provides positive gain mainly in inner cells but negative gain in outer cells. If thepercentage of users in inner cells is 40% to 80%, this feature provides positive gain in bothinner and outer cells but may provide negative gain for CEUs. When there are many smallpackets on the network, the perceptible throughput may decrease.In the uplink, the average throughput increases by 30% to 60%. This feature provides positivegain mainly in inner cells but slight positive gain or even negative gain in outer cells.Together with LOFD-001066 Intra-eNodeB UL CoMP, this feature provides positive gain forCEUs.With interference between beams of inner and outer cells, the signal quality deteriorates andKPIs may also decrease in the overlapping areas between these cells.

9.3.2 Network PerformanceThis feature improves uplink and downlink service-related KPIs. However, this feature hasadverse impacts on the call completion rate, service drop rate, and handover-related KPIs.



24

This feature requires the addition of a new intra-frequency cell, which leads to additionalinterference. In the overlapping areas between these cells, the interference is higher than thatin other areas, the SINRs of UEs greatly decrease, and KPIs may also deteriorate.


9.3.4 HardwareThis feature requires that the baseband processing unit be the BBU3900 or BBU3910.



Feature ID Feature Name LicenseControl Item

NE Sales Unit

LOFD-261103 AAS VerticalMultipleSectors for LTE

AAS VerticalMultipleSectors for LTE

eNodeB per RU




9.4 AAS Dividual Tilts by Carrier for LTE9.4.1 System Capacity

This feature increases downlink capacity by applying appropriate downtilt angles for differentcarriers.

9.4.2 Network PerformanceBy applying different downtilt angles to different carriers, this feature can optimize thecoverage and capacity of different areas and improve service-related KPIs of these areas. For



25

example, this feature uses one carrier for continuous coverage and another carrier for hop-spottraffic absorption.In addition, this feature improves both network KPIs and service-related KPIs by adjustingthe coverage areas of different carriers, which cannot be achieved in scenarios where multiplecarriers share the same antenna system.


9.4.4 HardwareNone.



Feature ID Feature Name LicenseControl Item

NE Sales Unit

LOFD-261105 AAS DividualTilts by Carrierfor LTE

AAS DividualTilts by Carrierfor LTE

eNodeB per RU




9.5 AAS RAT Specific Tilting (LTE)9.5.1 System Capacity

This feature optimizes the coverage and capacity of different RATs by separately adjusting thedowntilt angles for these RATs.



26

9.5.2 Network PerformanceAs this feature optimizes the coverage of each RAT, it improves KPIs such as the accesssuccess rate, service drop rate, and handover success rate.


9.5.4 HardwareThis feature requires that the baseband processing unit be the BBU3900 or BBU3910.




NE Sales Unit

MRFD-261105 AAS RAT SpecificTilting (LTE)

AAS RAT SpecificTilting (LTE)

eNodeB per RU






27

10 Engineering GuidelinesAbout This Chapter

This chapter provides engineering guidelines for the AAU3902. For details about engineeringguidelines for other AASs (such as the AAS3910), see 3900 Series Base Station InitialConfiguration Guide.A downtilt angle is equal to the sum of mechanical downtilt angle and configured downtiltangle:l A mechanical downtilt angle is fixed and cannot be changed after installation.l A configured downtilt angle may be one of the following:

Electrical downtilt angle of a passive antenna, which can be set using the TILTparameter. Electrical downtilt angle of an active antenna, which can be set using the DLTILT

or ULTILT parameters.Table 10-1 lists the ranges of mechanical downtilt angles and electrical downtilt angles.

Table 10-1 Downtilt angle rangesUnitInvolved

MechanicalDowntiltAngle

Electrical Downtilt Angleof a Passive Antenna

Electrical DowntiltAngle of an ActiveAntenna

MO AAS RETSUBUNIT VRETSUBUNITAAU3902 -3, -1.5, 0,

1.5, 3Low-frequency passiveantennas operating in the790-960 MHz frequencyband: [0, 10]High-frequency passiveantennas operating in the1710-2690 MHz frequencyband: [2, 10]

[0, 12]If the AARU operating inthe 1800 MHz frequencyband is used, the maximumdifference between beamdowntilt angles is 6.

eRANAAS Feature Parameter Description 10 Engineering Guidelines


28

10.1 Deployment of Passive Antennas

10.1.1 RequirementsPassive antennas are not license-controlled.

10.1.2 Data PreparationTable 10-2 describes the parameters that must be set in an RET MO.

Table 10-2 Key parameters in an RET MOParameterName

Parameter ID Setting Notes DataSource

Device No. DEVICENO All antenna line devices (ALDs)(including RET antennas and theTMA) in a base station must have aunique device number.

Equipmentplan

Device name DEVICENAME This parameter identifies an RETantenna. All RET antennas must havea unique device name. If an entereddevice name already exists, thesystem returns an error message. Theformat of the parameter value is:sector+port+device type_networktype.This parameter is optional.

Engineeringdesign

Control portcabinet No.

CTRLCN These parameters specify thenumbers of the cabinet, subrack, andslot, respectively, where an AAS islocated.

Equipmentplan

Control PlaneSubrack No.

CTRLSRN Equipmentplan

Control PlaneSlot No.

CTRLSN Equipmentplan

RET type RETTYPE For passive antennas, set thisparameter to MULTI_RET.

Equipmentplan

RET subunitnumber

SUBUNITNUM When the RETTYPE parameter is setto MULTI_RET, theSUBUNITNUM parameter must beset. Set this parameter to the numberof the highest number RET subunit tobe used.

Equipmentplan

Polar type POLARTYPE Set this parameter based on the AASspecifications.

Equipmentplan



29

ParameterName

Parameter ID Setting Notes DataSource

Antennascenario

SCENARIO Set this parameter to REGULAR forpassive antennas.

Equipmentplan

Vendor code VENDORCODE This parameter is mandatory incascading scenarios. Set thisparameter based on the manufacturerinformation, for example:l KA: Kathrein RET antennal AN: Andrew RET antennal HW: Huawei Agisson RET

antenna

Equipmentplan

Serial Number SERIALNO This parameter is mandatory incascading scenarios. Set thisparameter according to the deviceserial number of the target antenna.

Equipmentplan

Table 10-3 describes the parameters that must be set in an RETSUBUNIT MO.

Table 10-3 Key parameters in an RETSUBUNIT MOParameter Name Parameter ID Setting Notes Data

SourceSubunit No. SUBUNITNO This parameter specifies the RET

subunit number, which starts from1.

Equipmentplan

Connect Port 1Cabinet No.

CONNCN1 Set each of these parameters basedon the connection between thetarget AAS and the peer RRU orRFU.

Equipmentplan

Connect Port 1Subrack No.

CONNSRN1 Equipmentplan

Connect Port 1 SlotNo.

CONNSN1 Equipmentplan

Connect Port 1 PortNo.

CONNPN1 Equipmentplan

Connect Port 2Cabinet No.

CONNCN2 Equipmentplan

Connect Port 2Subrack No.

CONNSRN2 Equipmentplan

Connect Port 2 SlotNo.

CONNSN2 Equipmentplan



30

Parameter Name Parameter ID Setting Notes DataSource

Connect Port 2 PortNo.

CONNPN2 Equipmentplan

Tilt TILT Set this parameter based on theengineering design.

Engineeringdesign

10.1.3 PrecautionsNone.

10.1.4 Hardware AdjustmentFor details, see AAU3902 Installation Guide.

10.1.5 Initial Configuration

10.1.5.1 Using the CME to Perform Batch Configuration for Newly DeployedeNodeBs

Enter the values of the parameters listed in Table 10-4 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration.The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:l The managed objects (MOs) in Table 10-4 are contained in a scenario-specific summary

data file. In this situation, set the parameters in the MOs, and then verify and save thefile.

l Some MOs in Table 10-4 are not contained in a scenario-specific summary data file. Inthis situation, customize a summary data file to include the MOs before you can set theparameters.



31

Table 10-4 MOs related to passive antennasMO Sheet in

theSummaryData File

Parameter Group Remarks

RRUCHAIN

User-definedsheet

Chain No., Topo Type, Backup Mode,Access Type, Head Cabinet No., HeadSubrack No., Head Slot No., Head PortNo., Tail Cabinet No., Tail Subrack No.,Tail Slot No., Tail Port No., BreakPointPosition1, BreakPoint Position2, CPRILine Rate(Gbit/s), Local Slot No., ProtocolType

-

AAS User-definedsheet

Cabinet No., Subrack No., AAS Name,AAU Specification

-

AARU User-definedsheet

Cabinet No., Subrack No., Slot No.,Administrative State, AARU WorkStandard, AARU Name, Number of RXchannels, Number of TX channels,Intermediate Frequency Offset(100KHz),Logical Switch of TX Channel, FrequencyMin Bandwidth, VRET No.

WhenmultipleAARUs areconfiguredin the AAS,informationabout allAARUs isrequired.

AAMU User-definedsheet

Cabinet No., Subrack No., Slot No., RRUTopo Position, RRU Chain No., AASPosition

-

RET User-definedsheet

Device No., RET Type, Polar Type,Antenna Scenario, RET Subunit Number,Device Name, Control Port Cabinet No.,Control Port Subrack No., Control Port SlotNo., Vendor Code, Serial No.

-

RETSUBUNIT

User-definedsheet

Device No., Subunit No., Connect Port 1Cabinet No., Connect Port 1 Subrack No.,Connect Port 1 Slot No., Connect Port 1Port No., Connect Port 2 Cabinet No.,Connect Port 2 Subrack No., Connect Port2 Slot No., Connect Port 2 Port No.,Tilt(0.1degree), Tilt Alarm ErrorRange(0.1degree), Subunit Name

-



32

10.1.5.2 Using the CME to Perform Batch Configuration for Existing NodeBsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, formultiple eNodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Customize Summary Data File from the main menu of an U2000 client, orchoose Advanced > Customize Summary Data File from the main menu of a CME client,to customize a summary data file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > Export Base Station Bulk Configuration Data from the main menu of theU2000 client, or choose Advanced > Export Base Station Bulk Configuration Data fromthe main menu of the CME client, to export the eNodeB data stored on the CME into thecustomized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-4 and close the file.Step 4 Choose CME > Import Base Station Bulk Configuration Data from the main menu of the

U2000 client, or choose Advanced > Import Base Station Bulk Configuration Data fromthe main menu of the CME client, to import the summary data file into the CME.----End

10.1.5.3 Using the CME to Perform Single ConfigurationOn the CME, set the parameters listed in 10.1.2 Data Preparation for a single eNodeB. Forconfiguration steps, see CME Single Configuration Operation Guide.

10.1.5.4 Using MML CommandsPerform the following steps on the eNodeB side:

Step 1 Run the ADD RRUCHAIN command to add an RRU chain or ring.Step 2 Run the ADD AAS command to add an AAS to the RRU chain or ring.Step 3 Run the ADD AARU command to add an AARU. In this step, set RS to LO, RXNUM to 2,

and TXNUM to 2.When multiple AARUs are installed on the AAS, configure all the AARUs. To add an AARUin UMTS mode in slot 1, perform the following operation:Run the ADD AARU command on the eGBTS to add an AARU. In this step, set AARU WorkStandard to UO, Number of RX channels to 2, Number of TX channels to 2, and Slot No. to1.

Step 4 Run the SCN ALD command to scan an antenna device connected to RRUs or RFUs.Step 5 Run the ADD RET command with SCENARIO set to REGULAR to add an RET antenna.Step 6 Run the CLB RET command to calibrate the RET antenna to ensure that downtilt angles

supported by the RET antenna can be correctly configured and that the actual downtilt anglesof the RET antenna match the configured downtilt angles.



33

Step 7 Run the MOD RETSUBUNIT command and set parameters under an RETSUBUNIT MO.In this step, set CONNPN1 to R0A, CONNCN2 to R0B, and Tilt to a planned value such as5.6.

Step 8 (Optional) Run the MOD RETTILT command to configure the downtilt angle of thepreviously added RET antenna. In this step, set RETCLASS to RET(RET) and Tilt to aplanned value such as 6.0.----End

10.1.5.5 MML Command Examples//Adding an RRU chain or ringADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;

//Adding an AAS to the RRU chain or ringADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";

//Adding an AARUADD AARU: CN=0, SRN=60, SN=3, RS=LO, AN="AARU_1", RXNUM=2, TXNUM=2, VRETNO=60;

//Adding other AARU boards if an AAS is configured with more than one.ADD AARU: CN=0, SRN=60, SN=1, RS=UO, AN="AARU_2", RXNUM=2, TXNUM=2, VRETNO=61;

//Scanning an antenna deviceSCN ALD: CTRLCN=0, CTRLSRN=60, CTRLSN=0;

//Adding an RET antennaADD RET: DEVICENO=0, DEVICENAME="RET", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=MULTI_RET, SUBUNITNUM=1, SCENARIO=REGULAR;

//Calibrating the RET antennaCLB RET: OPMODE=SITE;

//Setting parameters under an RETSUBUNIT MOMOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, SUBNAME="RET", CONNCN1=0, CONNSRN1=60, CONNSN1=0, CONNPN1=R0A, CONNCN2=1, CONNSRN2=60, CONNSN2=0, CONNPN2=R0B, TILT=40;

//(Optional) Configuring the downtilt angle of the previously added RET antennaMOD RETTILT: RETCLASS=RET, OPMODE=DEVICENO, DEVICENO=0, TILT=40;

10.1.6 Activation ObservationPerform the following operations after passive antennas were deployed:l Check whether any alarms were falsely generated.l Run the DSP RET command to query the dynamic information about an RET or

RETSUBUNIT MO.

10.2 Deployment of Active Antennas



34

10.2.1 RequirementsActive antennas are not license-controlled.

10.2.2 Data PreparationTable 10-5 describes the parameters that must be set in a VRET MO.

Table 10-5 Key parameters in a VRET MOParameterName

ParameterID

Setting Notes Data Source

Device No. DEVICENO This parameter specifies the number ofthe virtual antenna device to which avirtual RET subunit belongs. Theparameter value must be consistent withthe subrack number of the target AAS.The value range is 60 to 255.

User-defined

Table 10-6 describes the parameters that must be set in a VRETSUBUNIT MO.

Table 10-6 Key parameters in a VRETSUBUNIT MOParameterName

ParameterID


Subunit No. SUBUNITNO One AAS can be configured with amaximum of eight virtual RETsubunits.Value range: 1 to 8

User-defined

SubunitName SUBNAME This parameter is user-defined. Itcontains 0 to 64 characters. All virtualRET subunits must have a unique name.

User-defined

PORTNUM PORTNUM This parameter specifies the number ofconnection ports that can be configuredfor a virtual RET subunit. Thisparameter can be set to 0, 1, 2, or 4.

User-defined

Connect Portn Port No.

CONNPNn This parameter specifies a connectionport. The n value ranges from 1 to 4. Aconnection port is in RXY form, andeach connection port belongs only toone virtual RET subunit.

User-defined

Polar type n POLARTYPEn

Polarization is a property of aconnection port. This parameterspecifies the polarization type of aconnection port. The n value rangesfrom 1 to 4.

User-defined



35

ParameterName

ParameterID


Uplink Tilt ULTILT Each virtual RET subunit can beconfigured with only one uplinkdowntilt angle.

User-defined

Downlink Tilt DLTILT Each virtual RET subunit can beconfigured with only one downlinkdowntilt angle.

User-defined

BeamAzimuth BEAMAZIMUTH

Retain the default value. User-defined

Beamwidth BEAMWIDTH

Retain the default value. User-defined

10.2.3 PrecautionsNone.

10.2.4 Hardware AdjustmentFor details, see AAU3902 Installation Guide.

10.2.5 Initial Configuration

10.2.5.1 Using the CME to Perform Batch Configuration for Newly DeployedeNodeBs

Enter the values of the parameters listed in Table 10-7 a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration.The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:l The MOs in Table 10-7 are contained in a scenario-specific summary data file. In this

situation, set the parameters in the MOs, and then verify and save the file.l Some MOs in Table 10-7 are not contained in a scenario-specific summary data file. In

this situation, customize a summary data file to include the MOs before you can set theparameters.



36

Table 10-7 MOs related to active antennasMO Sheet in the

SummaryData File


VRET User-definedsheet

Device No., Cabinet No., Subrack No.,Slot No., Device Name, SubunitQuantity

-

VRETSUBUNIT

User-definedsheet

Device No., Subunit No., SubunitName, Cabinet No., Subrack No., SlotNo., PORTNUM, Connected Port 1,Polar Type1, Connected Port 2, PolarType2, Connected Port 3, Polar Type3,Connected Port 4, Polar Type4, UplinkTilt(0.1degree), DownlinkTilt(0.1degree),BeamAzimuth(0.1degree),BeamWidth(0.1degree)

-

SECTOR User-definedsheet

Sector ID, Sector Name, LocationName, User Label, AntennaAzimuth(0.1degree), Sector Antenna

-

SECTOREQM

User-definedsheet

Sector Equipment ID, Sector ID,Sector Equipment Antenna

-

10.2.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, formultiple eNodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Customize Summary Data File from the main menu of an U2000 client, orchoose Advanced > Customize Summary Data File from the main menu of a CME client, tocustomize a summary data file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > Export Base Station Bulk Configuration Data from the main menu of theU2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from themain menu of the CME client, to export the eNodeB data stored on the CME into thecustomized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-7 and close the file.Step 4 Choose CME > Import Base Station Bulk Configuration Data from the main menu of the

U2000 client, or choose Advanced > Import Base Station Bulk Configuration Data from themain menu of the CME client, to import the summary data file into the CME.----End



37

10.2.5.3 Using the CME to Perform Single ConfigurationOn the CME, set the parameters listed in 10.2.2 Data Preparation for a single eNodeB. Forconfiguration steps, see CME Single Configuration Operation Guide.

10.2.5.4 Using MML CommandsPerform the following steps on the eNodeB side:

Step 1 Run the ADD RRUCHAIN command to add an RRU chain or ring.Step 2 Run the ADD AAS command to add an AAS.Step 3 Run the ADD AARU command to add an AARU. In this step, set RS to LO, RXNUM to 2,

and TXNUM to 2.When multiple AARUs are installed on the AAS, configure all the AARUs. To add an AARUin UMTS mode in slot 1, perform the following operation:Run the ADD AARU command on the eNodeB to add an AARU. In this step, set AARUWork Standard to UO, Number of RX channels to 2, Number of TX channels to 2, and SlotNo. to 1.

Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. Inthis step, set the DEVICENAME and SUBUNITQUANTITY parameters to appropriatevalues. The default value of the SUBUNITQUANTITY parameter is 8. Note that the value ofthe DEVICENO parameter must be the same as the value of theSRN parameter for thepreviously added AAS.

Step 5 Run the MOD VRETSUBUNIT command. In this step, set DLTILT to the planned value fora virtual RET subunit and set ULTILT to the same value as DLTILT.

Step 6 Run the ADD SECTOR command to associate the virtual RET subunit with a sector.Step 7 Run the ADD SECTOREQM command to add sector equipment.Step 8 Run the ADD CELL command to add a local cell.Step 9 Run the ADD EUCELLSECTOREQM command to add a relationship between the cell and

the sector equipment.Step 10 Run the MOD PDSCHCFG and MOD CELLDLPCPDSCHPA commands to set the cell

power parameters, including the ReferenceSignalPwr, PA, and PB.Step 11 Run the ACT CELL command to activate the cell.

----End

10.2.5.5 MML Command ExamplesThe following is a 2T2R configuration example://Adding an RRU chain or ringADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;

//Adding an AASADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";

//Adding an AARU



38

ADD AARU: CN=0, SRN=60, SN=3, RS=LO, AN="AARU_1", RXNUM=2, TXNUM=2, VRETNO=60;

//Adding other AARU boards if an AAS is configured with more than one AARU.ADD AARU: CN=0, SRN=60, SN=1, RS=UO, AN="AARU_2", RXNUM=2, TXNUM=2, VRETNO=61;

//(Optional) Modifying parameter settings for a VRET MOMOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;

//Modifying the configurations of a virtual RET subunitMOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=1, SUBNAME=" VRETSUBUNIT_01",PORTNUM=2,CONNPN1=R0A, POLARTYPE1= POSITIVE_NEGATIVE_45, CONNPN2=R0B, POLARTYPE2= POSITIVE_NEGATIVE_45, ULTILT=50, DLTILT=50, BEAMAZIMUTH=0, BEAMWIDTH=650;

//Associating a virtual RET subunit with a sectorADD SECTOR: SECTORID=0, SECNAME="sector", LOCATIONNAME="huawei", ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=1, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=1, ANT2N=R0B, CREATESECTOREQM=FALSE;

//Adding sector equipmentADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=1, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=1, ANT2N=R0B, ANTTYPE2=RXTX_MODE;

//Adding a local cellADD CELL: LocalCellId=0, CellName="0", FreqBand=3, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=1800, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0, PhyCellId=48, FddTddInd=CELL_FDD, RootSequenceIdx=48, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2, TxRxMode=2T2R;

//Adding a relationship between the cell and the sector equipmentADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=10;

//Setting the cell power parametersMOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=152, Pb=1;MOD CELLDLPCPDSCHPA: LocalCellId=0, PdschPaAdjSwitch=OFF, PaPcOff=DB_3_P_A;

//Activating the cellACT CELL: LocalCellId=0;

10.2.6 Activation ObservationPerform the following operations after active antennas were deployed:l Check whether any alarms were falsely generated.l Run the DSP VRETSUBUNIT command to query the status of virtual RET subunits.

10.3 Deployment of AAS Virtual Four Uplink Channelsfor LTE



39

10.3.1 Application SuggestionsThis feature is recommended if the following conditions are all met:l There are no problems such as service drop or access failure due to coverage.l The uplink interference over thermal (IoT) in the cell is high.

10.3.2 Required Informationl Traffic statistics: used to identify hot spots.l Measurement report and drive test data: used to analyze traffic distribution and coverage

distribution.l Site engineering parameters: used to obtain engineering information such as installation

information, downtilt angle configuration, and inter-site distance.

10.3.3 PlanningRF Planning

The suggestions for RF planning are as follows:l Set the uplink downtilt angles to the values used in 2T.l Obtain multiple-antenna reception information, and determine the link budget and

capacity in the uplink.l Complete RF planning according to the general network planning procedure.

Network PlanningNone.

Hardware PlanningThe hardware planning for this feature is the same as that for LOFD-001005 UL 4-AntennaReceive Diversity, and the LBBPd and UBBPd are required.

10.3.4 Deployment

10.3.4.1 RequirementsPurchase the license for LOFD-261101 AAS Virtual Four Uplink Channels for LTE andLOFD-001005 UL 4-Antenna Receive Diversity.

10.3.4.2 Data PreparationFor the parameters that must be set in a VRET MO, see Table 10-5.For the parameters that must be set in a VRETSUBUNIT MO, see Table 10-6.

10.3.4.3 PrecautionsNone.



40

10.3.4.4 Hardware AdjustmentFor details, see AAU3902 Installation Guide.

10.3.4.5 Initial Configuration

10.3.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBsEnter the values of the parameters listed in Table 10-8 in a summary data file, which alsocontains other data for the new eNodeBs to be deployed. Then, import the summary data fileinto the CME for batch configuration.The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:l The MOs in Table 10-8 are contained in a scenario-specific summary data file. In this

situation, set the parameters in the MOs, and then verify and save the file.l Some MOs in Table 10-8 are not contained in a scenario-specific summary data file. In

this situation, customize a summary data file to include the MOs before you can set theparameters.

Table 10-8 MOs related to AAS Virtual Four Uplink Channels for LTEMO Sheet in the

SummaryData File


RRUCHAIN EQUIPMENT Chain No., Topo Type, Backup Mode,Access Type, Head Cabinet No., HeadSubrack No., Head Slot No., Head PortNo., Tail Cabinet No., Tail SubrackNo., Tail Slot No., Tail Port No.,BreakPoint Position1, BreakPointPosition2, CPRI Line Rate(Gbit/s),Local Slot No., Protocol Type

-