Sie sind auf Seite 1von 74

eRAN

AAS Feature Parameter Description

Issue 01
Date 2017-03-10

HUAWEI TECHNOLOGIES CO., LTD.


Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.


Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com

Issue 01 (2017-03-10) Huawei Proprietary and Confidential i


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description Contents

Contents

1 About This Document.................................................................................................................. 1


1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Change History............................................................................................................................................................... 2
1.5 Differences Between Base Station Types....................................................................................................................... 2

2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 3
2.3 Architecture.................................................................................................................................................................... 3
2.3.1 AAS Hardware............................................................................................................................................................ 3
2.3.2 RET..............................................................................................................................................................................5
2.3.3 AAS Configuration......................................................................................................................................................6

3 AAS Virtual Four Uplink Channels for LTE............................................................................9


4 AAS User Specific Tilting for LTE...........................................................................................11
5 AAS Vertical Multiple Sectors for LTE...................................................................................12
6 AAS Dividual Tilts by Carrier for LTE................................................................................... 14
7 AAS RAT Specific Tilting (LTE).............................................................................................. 16
8 Related Features...........................................................................................................................17
9 Network Impact........................................................................................................................... 18
9.1 AAS Virtual Four Uplink Channels for LTE................................................................................................................ 18
9.1.1 System Capacity........................................................................................................................................................ 18
9.1.2 Network Performance................................................................................................................................................18
9.1.3 NEs............................................................................................................................................................................ 18
9.1.4 Hardware................................................................................................................................................................... 18
9.1.5 Inter-NE Interfaces.................................................................................................................................................... 18
9.1.6 Operation and Maintenance.......................................................................................................................................19
9.2 AAS User Specific Tilting for LTE.............................................................................................................................. 20
9.2.1 System Capacity........................................................................................................................................................ 20
9.2.2 Network Performance................................................................................................................................................20

Issue 01 (2017-03-10) Huawei Proprietary and Confidential ii


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description Contents

9.2.3 NEs............................................................................................................................................................................ 20
9.2.4 Hardware................................................................................................................................................................... 20
9.2.5 Inter-NE Interfaces.................................................................................................................................................... 20
9.2.6 Operation and Maintenance.......................................................................................................................................21
9.3 AAS Vertical Multiple Sectors for LTE........................................................................................................................21
9.3.1 System Capacity........................................................................................................................................................ 21
9.3.2 Network Performance................................................................................................................................................22
9.3.3 NEs............................................................................................................................................................................ 22
9.3.4 Hardware................................................................................................................................................................... 22
9.3.5 Inter-NE Interfaces.................................................................................................................................................... 22
9.3.6 Operation and Maintenance.......................................................................................................................................22
9.4 AAS Dividual Tilts by Carrier for LTE........................................................................................................................ 23
9.4.1 System Capacity........................................................................................................................................................ 23
9.4.2 Network Performance................................................................................................................................................23
9.4.3 NEs............................................................................................................................................................................ 23
9.4.4 Hardware................................................................................................................................................................... 23
9.4.5 Inter-NE Interfaces.................................................................................................................................................... 23
9.4.6 Operation and Maintenance.......................................................................................................................................23
9.5 AAS RAT Specific Tilting (LTE)................................................................................................................................. 24
9.5.1 System Capacity........................................................................................................................................................ 24
9.5.2 Network Performance................................................................................................................................................24
9.5.3 NEs............................................................................................................................................................................ 24
9.5.4 Hardware................................................................................................................................................................... 24
9.5.5 Inter-NE Interfaces.................................................................................................................................................... 24
9.5.6 Operation and Maintenance.......................................................................................................................................24

10 Engineering Guidelines........................................................................................................... 26
10.1 Deployment of Passive Antennas............................................................................................................................... 27
10.1.1 Requirements........................................................................................................................................................... 27
10.1.2 Data Preparation...................................................................................................................................................... 27
10.1.3 Precautions...............................................................................................................................................................29
10.1.4 Hardware Adjustment..............................................................................................................................................29
10.1.5 Initial Configuration................................................................................................................................................ 29
10.1.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................29
10.1.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................. 31
10.1.5.3 Using the CME to Perform Single Configuration................................................................................................ 31
10.1.5.4 Using MML Commands....................................................................................................................................... 31
10.1.5.5 MML Command Examples.................................................................................................................................. 32
10.1.6 Activation Observation............................................................................................................................................32
10.2 Deployment of Active Antennas................................................................................................................................ 32
10.2.1 Requirements........................................................................................................................................................... 32
10.2.2 Data Preparation...................................................................................................................................................... 32
10.2.3 Precautions...............................................................................................................................................................34

Issue 01 (2017-03-10) Huawei Proprietary and Confidential iii


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description Contents

10.2.4 Hardware Adjustment..............................................................................................................................................34


10.2.5 Initial Configuration................................................................................................................................................ 34
10.2.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs................................................34
10.2.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................. 35
10.2.5.3 Using the CME to Perform Single Configuration................................................................................................ 35
10.2.5.4 Using MML Commands....................................................................................................................................... 36
10.2.5.5 MML Command Examples.................................................................................................................................. 36
10.2.6 Activation Observation............................................................................................................................................37
10.3 Deployment of AAS Virtual Four Uplink Channels for LTE.....................................................................................37
10.3.1 Application Suggestions.......................................................................................................................................... 37
10.3.2 Required Information.............................................................................................................................................. 37
10.3.3 Planning................................................................................................................................................................... 38
10.3.4 Deployment............................................................................................................................................................. 38
10.3.4.1 Requirements........................................................................................................................................................ 38
10.3.4.2 Data Preparation................................................................................................................................................... 38
10.3.4.3 Precautions............................................................................................................................................................38
10.3.4.4 Hardware Adjustment...........................................................................................................................................39
10.3.4.5 Initial Configuration............................................................................................................................................. 39
10.3.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................39
10.3.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 41
10.3.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 41
10.3.4.5.4 Using MML Commands.................................................................................................................................... 41
10.3.4.5.5 MML Command Examples............................................................................................................................... 42
10.3.4.6 Activation Observation.........................................................................................................................................43
10.3.5 Performance Monitoring..........................................................................................................................................44
10.3.6 Parameter Optimization........................................................................................................................................... 45
10.3.7 Possible Issues......................................................................................................................................................... 45
10.4 Deployment of AAS User Specific Tilting for LTE................................................................................................... 45
10.4.1 Application Suggestions.......................................................................................................................................... 45
10.4.2 Required Information.............................................................................................................................................. 45
10.4.3 Planning................................................................................................................................................................... 46
10.4.4 Deployment............................................................................................................................................................. 47
10.4.4.1 Requirements........................................................................................................................................................ 47
10.4.4.2 Data Preparation................................................................................................................................................... 47
10.4.4.3 Precautions............................................................................................................................................................47
10.4.4.4 Hardware Adjustment...........................................................................................................................................47
10.4.4.5 Initial Configuration............................................................................................................................................. 47
10.4.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................47
10.4.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 48
10.4.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 48
10.4.4.5.4 Using MML Commands.................................................................................................................................... 48
10.4.4.5.5 MML Command Examples............................................................................................................................... 49

Issue 01 (2017-03-10) Huawei Proprietary and Confidential iv


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description Contents

10.4.4.6 Activation Observation.........................................................................................................................................50


10.4.5 Performance Monitoring..........................................................................................................................................50
10.4.6 Parameter Optimization........................................................................................................................................... 51
10.4.7 Possible Issues......................................................................................................................................................... 52
10.5 Deployment of AAS Vertical Multiple Sectors for LTE.............................................................................................52
10.5.1 Application Suggestions.......................................................................................................................................... 52
10.5.2 Required Information.............................................................................................................................................. 52
10.5.3 Planning................................................................................................................................................................... 52
10.5.4 Deployment............................................................................................................................................................. 53
10.5.4.1 Requirements........................................................................................................................................................ 53
10.5.4.2 Data Preparation................................................................................................................................................... 54
10.5.4.3 Precautions............................................................................................................................................................54
10.5.4.4 Hardware Adjustment...........................................................................................................................................54
10.5.4.5 Initial Configuration............................................................................................................................................. 54
10.5.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................54
10.5.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 54
10.5.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 55
10.5.4.5.4 Using MML Commands.................................................................................................................................... 55
10.5.4.5.5 MML Command Examples............................................................................................................................... 56
10.5.4.6 Activation Observation.........................................................................................................................................57
10.5.5 Performance Monitoring..........................................................................................................................................57
10.5.6 Parameter Optimization........................................................................................................................................... 58
10.5.7 Possible Issues......................................................................................................................................................... 59
10.6 Deployment of AAS Dividual Tilts by Carrier for LTE............................................................................................. 59
10.6.1 Application Suggestions.......................................................................................................................................... 59
10.6.2 Required Information.............................................................................................................................................. 59
10.6.3 Planning................................................................................................................................................................... 59
10.6.4 Deployment............................................................................................................................................................. 60
10.6.4.1 Requirements........................................................................................................................................................ 60
10.6.4.2 Data Preparation................................................................................................................................................... 60
10.6.4.3 Precautions............................................................................................................................................................60
10.6.4.4 Hardware Adjustment...........................................................................................................................................60
10.6.4.5 Initial Configuration............................................................................................................................................. 60
10.6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs.............................................60
10.6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs.......................................................... 60
10.6.4.5.3 Using the CME to Perform Single Configuration............................................................................................. 61
10.6.4.5.4 Using MML Commands.................................................................................................................................... 61
10.6.4.5.5 MML Command Examples............................................................................................................................... 62
10.6.4.6 Activation Observation.........................................................................................................................................63
10.6.5 Performance Monitoring..........................................................................................................................................63
10.6.6 Parameter Optimization........................................................................................................................................... 64
10.6.7 Possible Issues......................................................................................................................................................... 64

Issue 01 (2017-03-10) Huawei Proprietary and Confidential v


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description Contents

10.7 Deployment of AAS RAT Specific Tilting (LTE)...................................................................................................... 64


10.7.1 Application Suggestions.......................................................................................................................................... 64
10.7.2 Required Information.............................................................................................................................................. 64
10.7.3 Planning................................................................................................................................................................... 64
10.7.4 Deployment............................................................................................................................................................. 65
10.7.4.1 Requirements........................................................................................................................................................ 65
10.7.4.2 Data Preparation................................................................................................................................................... 65
10.7.4.3 Precautions............................................................................................................................................................65
10.7.4.4 Hardware Adjustment...........................................................................................................................................65
10.7.4.5 Initial Configuration............................................................................................................................................. 65
10.7.4.6 Activation Observation.........................................................................................................................................65
10.7.5 Performance Monitoring..........................................................................................................................................65
10.7.6 Parameter Optimization........................................................................................................................................... 66
10.7.7 Possible Issues......................................................................................................................................................... 66

11 Reference Documents............................................................................................................... 67

Issue 01 (2017-03-10) Huawei Proprietary and Confidential vi


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 1 About This Document

1 About This Document

1.1 Scope
This document describes the LTE AAS, including its technical principles, related features,
network impact, and engineering guidelines. The AAS in this document indicates the
AAU3902.

This document covers the following features:

l LOFD-261101 AAS Virtual Four Uplink Channels for LTE


l LOFD-261102 AAS User Specific Tilting for LTE
l LOFD-261103 AAS Vertical Multiple Sectors for LTE
l LOFD-261105 AAS Dividual Tilts by Carrier for LTE
l MRFD-261105 AAS RAT Specific Tilting (LTE)

This document applies to macro base stations, DBS3900 LampSite base stations, and micro
base stations. Macro base stations include BTS3900, BTS3900L, BTS3900A, BTS3900AL,
BTS3900C, and DBS3900.

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 Audience


This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products

1.3 Change History


This section provides information about the changes in different document versions. There are
two types of changes:

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 1


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 1 About This Document

l Feature change
Changes in features and parameters of a specified version as well as the affected entities.
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.

eRAN12.1 01 (2017-03-10)
This issue includes the following changes.

Change Type Change Description Parameter


Change

Feature change None None

Editorial change Added differences between base None


station types. For details, see 1.5
Differences Between Base Station
Types.

eRAN12.1 Draft A (2016-12-30)


This issue does not include any changes.

1.4 Change History


This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities.
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.

SRAN15.0 Draft A (2018-07-16)


This issue does not introduce any changes to SRAN13.1 01 (2018-04-10).

1.5 Differences Between Base Station Types


The features described in this document are implemented in the same way on macro and
LampSite base stations.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 2


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

2 Overview

2.1 Introduction
The AAS is a new type of radio frequency (RF) module that uses common public radio
interface (CPRI) ports to connect to baseband signal processing boards in the same way as the
remote radio unit (RRU) and radio frequency unit (RFU). The AAS can incorporate the
functions 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. Beam
adjustments help improve radio coverage and increase network capacity.

2.2 Benefits
The AAS provides the following benefits:
l Saves antenna space
The AAS occupies less antenna space than an RRU and traditional antenna, thereby
helping operators free up more antenna space for other devices.
l Supports the beamforming function
The AAS can be used to increase network capacity in heavy traffic areas.

2.3 Architecture

2.3.1 AAS Hardware


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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 3


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

Figure 2-1 AAS structure

The following table describes the slot assignment of an AAU.

Table 2-1 AAU slot assignment


Slot Configured Maxi Optio Description
Module mum nal/
Quant Mand
ity atory

Slot 0 AAMU (Active 1 Manda The AAMU connects to the BBU using
Antenna- tory common public radio interface (CPRI)
Management Unit) ports and to the AAS's other units using
cables.

Slot 1 l AARU (Active 1 Option l The AARU serves as the RF


Antenna-Radio al subsystem of the AAS. It is used to
Unit) implement the transceiver function
Slot 3 1 Option and provide the phase calibration
l AACU (Active al
Antenna-Cover function.
Unit) l The AACU protects the AAAU from
rainwater and dust. If no AARUs are
configured, one AACU must be
configured.

Slot 2 N/A N/A N/A N/A

NOTE

For more information, see AAU3902 Hardware Description.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 4


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

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

RET Function for Passive Antennas


The RET function for passive antennas implements external or internal control, depending on
which device the AAS is connected to.

The RET function implements external control when the AAAU is connected to RRUs using
RF feeders and the ALD control line to control the RET. (Note that these RRUs can belong to
either the same base station as the AAS or to a different base station.) External control
complies with the Antenna Interface Standards Group (AISG) protocol and requires RET
signal processing of the remote control units (RCUs) in the AAAU.

The RET function implements internal control when the AAMU connects to the BBU using a
CPRI 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 the
RCUs for signal processing.

Figure 2-2 External and internal control

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 5


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

RET Function for Active Antennas


The RET function for active antennas adjusts the downlink downtilt angles of beams from
AASs by modifying the downtilt angle attribute of the related virtual RET subunits. Features
related 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 shown
in Figure 2-3.
Connection method required by RET for active antennas

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

2.3.3 AAS Configuration


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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 6


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

Figure 2-4 Configuration objects of AAS and RRU

NOTE

In Figure 2-4, "1:x" indicates the ratio of the number of left configuration objects to the number of right
configuration 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:
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 standard, and number of transmit or receive channels in the
AARU hardware.
l VRET: automatically created with the AARU configuration object and used to control
the number of virtual RET subunits. VRET is the parent object of VRETSUBUNIT.
l VRETSUBUNIT: automatically created with the AARU configuration object. VRET
has eight configuration objects VRETSUBUNIT by default. Each VRETSUBUNIT
corresponds 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
meanings of X and Y are as follows:
– 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. Beam
characteristics can be defined for each port separately. Downtilt angles on the
vertical plane can be defined for AAU3902.
– Y indicates the number of a logical channel on the horizontal plane and can be set to
A or B. A indicates +45° polarization; B indicates -45° polarization.
Figure 2-5 shows the diagram of logical channels and logical ports.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 7


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 2 Overview

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.

Antenna Logical Logical Port


Polarizatio Channel
n

+45° A R0A R1A R2A R3A R4A R5A R6A R7A

-45° B R0B R1B R2B R3B R4B R5B R6B R7B

NOTE

1. 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 port
switch at the module level.
3. The AAU3902 does not support the modification of the RX logical port switch at both the channel
level and the module level by running the MOD RXBRANCH command.
NOTE

The downtilt angle difference between AAS beams is restricted by the maximum capability of the digital
tilt (DT). All such differences among features or within any features comply with this restriction. For
more information, see "Technical Specifications of AAUs" in 3900 Series Base Station Technical
Description.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 8


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 3 AAS Virtual Four Uplink Channels for LTE

3 AAS Virtual Four Uplink Channels for LTE

This chapter describes LOFD-261101 AAS Virtual Four Uplink Channels for LTE.
To implement 4-antenna receive diversity, a traditional RRU/RFU uses two dual-polarized
antennas, whereas an AAS with this feature uses only one active antenna polarized at +45°
and -45°. Specifically, the AAS assigns different weights to received signals, forms two
uplink beams on the vertical plane in each polarization direction, and obtains a total of four
channels of signals. In this way, the AAS provides receive diversity gain, beamforming gain,
and interference mitigation gain. The AAS increases uplink throughput and network
performance.
To support this feature, the AAS requires that the four virtual antenna ports (CONNPN1 to
CONNPN4) of each virtual RET subunit be bound to the same sector. In addition, the AAS
requires that the number of receive antennas in this sector (ANTNUM) be set to 4 so that the
sector has a 4-antenna reception (4R) capability. Under this configuration, the AAS generates
a 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 R1A
are configured in one polarization direction and R0B and R1B in the other polarization
direction. The generated four uplink channels are shown in Figure 3-1.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 9


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 3 AAS Virtual Four Uplink Channels for LTE

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 10


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 4 AAS User Specific Tilting for LTE

4 AAS User Specific Tilting for LTE

This 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 direction
for a total of four transmit beams in the two polarization directions. Together with
LOFD-001003 DL 4x2 MIMO or LOFD-001060 DL 4x4 MIMO in closed-loop mode, the
AAS 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 the
other three beams are narrow beams generated for traffic channels. These narrow beams are
formed for different UEs based on the precoding matrix indicators (PMIs) reported by these
UEs and the associated codebooks.
This feature increases the signal power of UEs close to the AAS and reduces the interference
with other cells, thereby increasing system capacity.

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 11


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 5 AAS Vertical Multiple Sectors for LTE

5 AAS Vertical Multiple Sectors for LTE

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

NOTE

To expand uplink capacity (possibly due to heavy uplink load), use the AAS Virtual Four Uplink
Channels 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 interference
easily occurs. After the AAS Vertical Multiple Sectors for LTE feature is applied, the outer
and inner cells overlap and these two cells cause strong interference for each other in
overlapping areas. When using this feature in urban areas, adjust the downtilt angles of beams
in these cells to minimize the interference.
The area covered by an inner cell is small because of the large downtilt angles of the beams in
the inner cell and interference from the outer cell. The lower the AAS is placed, the smaller
the area covered by the inner cell. With this feature, the throughput in inner cells accounts for
a large proportion of the throughput of the entire site.
This feature is implemented by setting the ULTILT and DLTILT parameters in
VRETSUBUNIT 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 the
same frequency. For details of the angle difference between α1 and α2 of beams 1 and 2 on
the vertical plane, see "AAU3902 Technical Specifications" in the 3900 Series Base Station
Technical Description.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 12


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 5 AAS Vertical Multiple Sectors for LTE

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 13


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 6 AAS Dividual Tilts by Carrier for LTE

6 AAS Dividual Tilts by Carrier for LTE

This chapter describes LOFD-261105 AAS Dividual Tilts by Carrier for LTE, which is also
referred to as carrier specific tilting in this document.
The AAS Dividual Tilts by Carrier for LTE feature enables multiple carriers operating at
different frequencies on the same frequency band to use different downtilt angles. Carriers
that use smaller downtilt angles deliver contiguous coverage, and carriers that use larger
downtilt 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. These
two carriers correspond to cells 1 and 2, respectively. The two cells use different frequencies
F1 and F2 on the same frequency band. The downtilt angle of beam 1 is smaller than that of
beam 2, which reduces the interference among F2 cells and increases network capacity.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 14


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 6 AAS Dividual Tilts by Carrier for LTE

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 15


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 7 AAS RAT Specific Tilting (LTE)

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 RAT


specific tilting.

To meet different RAT requirements on coverage and capacity, the AAS generally applies
different downtilt angles to these RATs. An AAU3902 of SRAN9.0 can use one AARU to
support 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 DLTILT
parameters in the VRETSUBUNIT MO to control the downtilt angles of two beams on the
vertical plane. Beams 1 and 2 correspond to cells 1 and 2 respectively, and the two cells use
different RATs and frequencies. Figure 7-1 illustrates RAT specific tilting.

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 16


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 8 Related Features

8 Related Features

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

Table 8-1 Prerequisite features and mutually exclusive features


AAS Feature Prerequisite Feature Mutually Exclusive
Feature

AAS Virtual Four l LOFD-001005 UL 4-Antenna l AAS Vertical Multiple


Uplink Channels for Receive Diversity Sectors for LTE
LTE (Vertical)

AAS User Specific l LOFD-001001 DL 2x2 MIMO l AAS Vertical Multiple


Tilting for LTE l LOFD-001003 DL 4x2 MIMO Sectors for LTE
l LOFD-001060 DL 4x4 MIMO
l LOFD-001005 UL 4-Antenna
Receive Diversity

AAS Vertical None l AAS Virtual Four Uplink


Multiple Sectors for Channels for LTE
LTE (Vertical)
l AAS User Specific Tilting
for LTE

AAS Dividual Tilts None None


by Carrier for LTE

AAS RAT Specific None None


Tilting (LTE)

NOTE

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 17


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

9 Network Impact

9.1 AAS Virtual Four Uplink Channels for LTE

9.1.1 System Capacity


This feature increases the uplink cell capacity by 10% to 45% in densely populated areas and
common urban areas.

9.1.2 Network Performance


The 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 dB
for 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 from
the AAS but lower gain for UEs far from the AAS.

9.1.3 NEs
This feature is implemented on the eNodeB.

9.1.4 Hardware
This feature requires that the baseband processing unit be the BBU3900 or BBU3910.

This feature requires that the baseband processing unit support 4R.

9.1.5 Inter-NE Interfaces


None.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 18


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

9.1.6 Operation and Maintenance


License
Feature ID Feature Name License Control NE Sales Unit
Item

LOFD-00100 LOFD-001005 UL LT1S0U4ARD00 eNodeB per cell


5 4-Antenna Receive
Diversity

LOFD-261101 AAS Virtual Four WDMS0AVFUC0 eNodeB per RU


Uplink Channels 0
for LTE

Configuration Management
The following MML commands and parameters have been introduced on the eNodeB side to
accommodate this feature.

Table 9-1 New MML commands


Change MML Command Description
Type

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 parameters


Change MO Parameter ID MML Command Description
Type

New VRETS ULTILT MOD Indicates the uplink


UBUNI VRETSUBUNIT downtilt angle of the
T virtual RET subunit.

New VRETS DLTILT MOD Indicates the downlink


UBUNI VRETSUBUNIT downtilt angle of the
T virtual RET subunit.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 19


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

Performance Management
None.

Fault Management
Table 9-3 lists the alarms with online help information that was updated after this feature was
introduced.

Table 9-3 New alarms


Change Alarm Alarm Name Alarm Applicable
Type ID Severity Product

New 26560 AAS Board Not In Position Major AAU3902

New 26561 AAS Hardware Fault Major AAU3902

9.2 AAS User Specific Tilting for LTE

9.2.1 System Capacity


This feature provides beamforming gain and inter-cell interference mitigation gain in
continuous coverage areas. In addition, this feature reduces downlink interference with
neighboring 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 Performance


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

9.2.3 NEs
This feature is implemented on the eNodeB.

9.2.4 Hardware
This feature requires that the baseband processing unit be the BBU3900 or BBU3910.

This feature requires that the baseband processing unit support 4T.

9.2.5 Inter-NE Interfaces


None.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 20


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

9.2.6 Operation and Maintenance

License
Feature ID Feature Name License Control NE Sales Unit
Item

LOFD-00100 UL 4-Antenna LT1S0U4ARD00 eNodeB per cell


5 Receive Diversity

LOFD-00100 DL 2x2 MIMO LT1S0D2I2O00 eNodeB per cell


1

LOFD-00100 DL 4x2 MIMO LT1S0D4I2O00 eNodeB per cell


3

LOFD-00106 DL 4x4 MIMO LT1S0DMIMO00 eNodeB per cell


0

LOFD-261102 AAS User Specific AAS User Specific eNodeB per RU


Tilting for LTE Tilting for LTE

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

Performance Management
None.

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

9.3 AAS Vertical Multiple Sectors for LTE

9.3.1 System Capacity


This feature increases uplink and downlink system capacity. The capacity gain depends on the
site 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 the
percentage of users in inner cells is 40% to 80%, this feature provides positive gain in both
inner and outer cells but may provide negative gain for CEUs. When there are many small
packets on the network, the perceptible throughput may decrease.

In the uplink, the average throughput increases by 30% to 60%. This feature provides positive
gain mainly in inner cells but slight positive gain or even negative gain in outer cells.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 21


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

Together with LOFD-001066 Intra-eNodeB UL CoMP, this feature provides positive gain for
CEUs.
With interference between beams of inner and outer cells, the signal quality deteriorates and
KPIs may also decrease in the overlapping areas between these cells.

9.3.2 Network Performance


This feature improves uplink and downlink service-related KPIs. However, this feature has
adverse impacts on the call completion rate, service drop rate, and handover-related KPIs.
This feature requires the addition of a new intra-frequency cell, which leads to additional
interference. In the overlapping areas between these cells, the interference is higher than that
in other areas, the SINRs of UEs greatly decrease, and KPIs may also deteriorate.

9.3.3 NEs
This feature is implemented on the eNodeB.

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

9.3.5 Inter-NE Interfaces


None.

9.3.6 Operation and Maintenance


License
Feature ID Feature Name License NE Sales Unit
Control Item

LOFD-001001 DL 2x2 MIMO LT1S0D2I2O00 eNodeB per cell

LOFD-261103 AAS Vertical AAS Vertical eNodeB per RU


Multiple Multiple
Sectors for LTE Sectors for LTE

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

Performance Management
None.

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 22


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

9.4 AAS Dividual Tilts by Carrier for LTE

9.4.1 System Capacity


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

9.4.2 Network Performance


By applying different downtilt angles to different carriers, this feature can optimize the
coverage and capacity of different areas and improve service-related KPIs of these areas. For
example, this feature uses one carrier for continuous coverage and another carrier for hop-spot
traffic absorption.
In addition, this feature improves both network KPIs and service-related KPIs by adjusting
the coverage areas of different carriers, which cannot be achieved in scenarios where multiple
carriers share the same antenna system.

9.4.3 NEs
This feature is implemented on the eNodeB.

9.4.4 Hardware
None.

9.4.5 Inter-NE Interfaces


None.

9.4.6 Operation and Maintenance


License
Feature ID Feature Name License NE Sales Unit
Control Item

LOFD-261105 AAS Dividual AAS Dividual eNodeB per RU


Tilts by Carrier Tilts by Carrier
for LTE for LTE

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

Performance Management
None.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 23


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

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

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 the
downtilt angles for these RATs.

9.5.2 Network Performance


As this feature optimizes the coverage of each RAT, it improves KPIs such as the access
success rate, service drop rate, and handover success rate.

9.5.3 NEs
This feature is implemented on the eNodeB.

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

9.5.5 Inter-NE Interfaces


None.

9.5.6 Operation and Maintenance


License
Feature ID Feature Name License Control NE Sales Unit
Item

MRFD-261105 AAS RAT Specific AAS RAT Specific eNodeB per RU


Tilting (LTE) Tilting (LTE)

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

Performance Management
None.

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 24


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 9 Network Impact

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 25


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10 Engineering Guidelines

About This Chapter


This chapter provides engineering guidelines for the AAU3902. For details about engineering
guidelines for other AASs (such as the AAS3910), see 3900 Series Base Station Initial
Configuration Guide.

A downtilt angle is equal to the sum of mechanical downtilt angle and configured downtilt
angle:

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 TILT
parameter.
– 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 ranges

Unit Mechanical Electrical Downtilt Angle Electrical Downtilt


Involved Downtilt of a Passive Antenna Angle of an Active
Angle Antenna

MO AAS RETSUBUNIT VRETSUBUNIT

AAU3902 -3°, -1.5°, 0°, Low-frequency passive [0, 12]


1.5°, 3° antennas operating in the If the AARU operating in
790-960 MHz frequency the 1800 MHz frequency
band: [0, 10] band is used, the maximum
High-frequency passive difference between beam
antennas operating in the downtilt angles is 6°.
1710-2690 MHz frequency
band: [2, 10]

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 26


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.1 Deployment of Passive Antennas

10.1.1 Requirements
Passive antennas are not license-controlled.

10.1.2 Data Preparation


Table 10-2 describes the parameters that must be set in an RET MO.

Table 10-2 Key parameters in an RET MO

Parameter Parameter ID Setting Notes Data


Name Source

Device No. DEVICENO All antenna line devices (ALDs) Equipment


(including RET antennas and the plan
TMA) in a base station must have a
unique device number.

Device Name DEVICENAME This parameter identifies an RET Engineering


antenna. All RET antennas must have design
a unique device name. If an entered
device name already exists, the
system returns an error message. The
format of the parameter value is:
sector+port+device type_network
type.
This parameter is optional.

Control Port CTRLCN These parameters specify the Equipment


Cabinet No. numbers of the cabinet, subrack, and plan
slot, respectively, where an AAS is
Control Plane CTRLSRN located. Equipment
Subrack No. plan

Control Plane CTRLSN Equipment


Slot No. plan

RET Type RETTYPE For passive antennas, set this Equipment


parameter to MULTI_RET. plan

Number of SUBUNITNUM When the RETTYPE parameter is set Equipment


RET Subunits to MULTI_RET, the plan
SUBUNITNUM parameter must be
set. Set this parameter to the number
of the highest number of RET
subunits to be used.

Polar Type POLARTYPE Set this parameter based on the AAS Equipment
specifications. plan

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 27


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Parameter Parameter ID Setting Notes Data


Name Source

Antenna SCENARIO Set this parameter to REGULAR for Equipment


Scenario passive antennas. plan

Vendor Code VENDORCODE This parameter is mandatory in Equipment


cascading scenarios. Set this plan
parameter based on the manufacturer
information, for example:
l KA: Kathrein RET antenna
l AN: Andrew RET antenna
l HW: Huawei Agisson RET
antenna

Serial No. SERIALNO This parameter is mandatory in Equipment


cascading scenarios. Set this plan
parameter according to the device
serial number of the target antenna.

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

Table 10-3 Key parameters in an RETSUBUNIT MO


Parameter Name Parameter ID Setting Notes Data
Source

Subunit No. SUBUNITNO This parameter specifies the RET Equipment


subunit number, which starts from plan
1.

Connect Port 1 CONNCN1 Set each of these parameters based Equipment


Cabinet No. on the connection between the plan
target AAS and the peer RRU or
Connect Port 1 CONNSRN1 RFU. Equipment
Subrack No. plan

Connect Port 1 Slot CONNSN1 Equipment


No. plan

Connect Port 1 Port CONNPN1 Equipment


No. plan

Connect Port 2 CONNCN2 Equipment


Cabinet No. plan

Connect Port 2 CONNSRN2 Equipment


Subrack No. plan

Connect Port 2 Slot CONNSN2 Equipment


No. plan

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 28


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Parameter Name Parameter ID Setting Notes Data


Source

Connect Port 2 Port CONNPN2 Equipment


No. plan

Tilt TILT Set this parameter based on the Engineering


engineering design. design

10.1.3 Precautions
None.

10.1.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.1.5 Initial Configuration

10.1.5.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 10-4 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
file.
l Some MOs in Table 10-4 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 the
parameters.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 29


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Table 10-4 MOs related to passive antennas


MO Sheet in Parameter Group Remarks
the
Summary
Data File

RRUCH User- Chain No., Topo Type, Backup Mode, N/A


AIN defined Access Type, Head Cabinet No., Head
sheet Subrack No., Head Slot No., Head Port
No., Tail Cabinet No., Tail Subrack No.,
Tail Slot No., Tail Port No., BreakPoint
Position1, BreakPoint Position2, CPRI
Line Rate(Gbit/s), Local Slot No., Protocol
Type

AAS User- Cabinet No., Subrack No., AAS Name, N/A


defined AAU Specification
sheet

AARU User- Cabinet No., Subrack No., Slot No., When


defined Administrative State, AARU Work multiple
sheet Standard, AARU Name, Number of RX AARUs are
channels, Number of TX channels, configured
Intermediate Frequency Offset(100KHz), in the AAS,
Logical Switch of TX Channel, Frequency the
Min Bandwidth, VRET No. information
about all
AARUs is
required.

AAMU User- Cabinet No., Subrack No., Slot No., RRU N/A
defined Topo Position, RRU Chain No., AAS
sheet Position

RET User- Device No., RET Type, Polar Type, N/A


defined Antenna Scenario, RET Subunit Number,
sheet Device Name, Control Port Cabinet No.,
Control Port Subrack No., Control Port Slot
No., Vendor Code, Serial No.

RETSUB User- Device No., Subunit No., Connect Port 1 N/A


UNIT defined Cabinet No., Connect Port 1 Subrack No.,
sheet Connect Port 1 Slot No., Connect Port 1
Port No., Connect Port 2 Cabinet No.,
Connect Port 2 Subrack No., Connect Port
2 Slot No., Connect Port 2 Port No.,
Tilt(0.1degree), Tilt Alarm Error
Range(0.1degree), Subunit Name

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 30


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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

Step 1 Choose CME > Customize Summary Data File from the main menu of a U2000 client, or
choose 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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized 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 from
the 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 Configuration


On the CME, set the parameters listed in 10.1.2 Data Preparation for a single eNodeB. For
configuration steps, see CME Single Configuration Operation Guide.

10.1.5.4 Using MML Commands


Perform 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 AARU
in UMTS mode in slot 1, perform the following operation:

Run the ADD AARU command to add an AARU. In this step, set AARU Work Standard to
UO, Number of RX channels to 2, Number of TX channels to 2, and Slot No. to 1.

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 angles
of the RET antenna match the configured downtilt angles.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 31


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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 as
5.6°.
Step 8 (Optional) Run the MOD RETTILT command to configure the downtilt angle of the
previously added RET antenna. In this step, set RETCLASS to RET(RET) and Tilt to a
planned value such as 6.0°.

----End

10.1.5.5 MML Command Examples


//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;
//Adding an AAS to the RRU chain or ring
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";
//Adding an AARU
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;
//Scanning an antenna line device
SCN ALD: CTRLCN=0, CTRLSRN=60, CTRLSN=0;
//Adding an RET antenna
ADD RET: DEVICENO=0, DEVICENAME="RET", CTRLCN=0, CTRLSRN=60, CTRLSN=0,
RETTYPE=MULTI_RET, SUBUNITNUM=1, SCENARIO=REGULAR;
//Calibrating the RET antenna
CLB RET: OPMODE=SITE;
//Setting parameters under an RETSUBUNIT MO
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, SUBNAME="RET", CONNCN1=0, CONNSRN1=60,
CONNSN1=0, CONNPN1=R0A, CONNCN2=0, CONNSRN2=60, CONNSN2=0, CONNPN2=R0B, TILT=60;
//(Optional) Configuring the downtilt angle of the previously added RET antenna
MOD RETTILT: RETCLASS=RET, OPMODE=DEVICENO, DEVICENO=0, TILT=60;

10.1.6 Activation Observation


Perform 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

10.2.1 Requirements
Active antennas are not license-controlled.

10.2.2 Data Preparation


Table 10-5 describes the parameters that must be set in a VRET MO.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 32


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Table 10-5 Key parameters in a VRET MO


Parameter Parameter Setting Notes Data Source
Name ID

Device No. DEVICENO This parameter specifies the number of User-defined


the virtual antenna device to which a
virtual RET subunit belongs. The
parameter value must be consistent with
the subrack number of the target AAS.
The value range is 60 to 255.

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

Table 10-6 Key parameters in a VRETSUBUNIT MO


Parameter Parameter Setting Notes Data Source
Name ID

Subunit No. SUBUNITNO One AAS can be configured with a User-defined


maximum of eight virtual RET
subunits.
Value range: 1 to 8

Subunit Name SUBNAME This parameter is user-defined. It User-defined


contains 0 to 64 characters. All virtual
RET subunits must have a unique name.

PORTNUM PORTNUM This parameter specifies the number of User-defined


connection ports that can be configured
for a virtual RET subunit. This
parameter can be set to 0, 1, 2, or 4.

Connect Port CONNPNn This parameter specifies a connection User-defined


No. n port. The n value ranges from 1 to 4. A
connection port is in RXY form, and
each connection port belongs only to
one virtual RET subunit.

Polar Type n POLARTYPE Polarization is a property of a User-defined


n connection port. This parameter
specifies the polarization type of a
connection port. The n value ranges
from 1 to 4.

Uplink Tilt ULTILT Each virtual RET subunit can be User-defined


configured with only one uplink
downtilt angle.

Downlink Tilt DLTILT Each virtual RET subunit can be User-defined


configured with only one downlink
downtilt angle.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 33


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Parameter Parameter Setting Notes Data Source


Name ID

BeamAzimuth BEAMAZIM Retain the default value. User-defined


UTH

Beamwidth BEAMWIDT Retain the default value. User-defined


H

10.2.3 Precautions
None.

10.2.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.2.5 Initial Configuration

10.2.5.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 10-7 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
parameters.

Table 10-7 MOs related to active antennas


MO Sheet in the Parameter Group Remarks
Summary
Data File

VRET User-defined Device No., Cabinet No., Subrack No., N/A


sheet Slot No., Device Name, Subunit
Quantity

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 34


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

MO Sheet in the Parameter Group Remarks


Summary
Data File

VRETSUBU User-defined Device No., Subunit No., Subunit N/A


NIT sheet Name, Cabinet No., Subrack No., Slot
No., PORTNUM, Connected Port 1,
Polar Type1, Connected Port 2, Polar
Type2, Connected Port 3, Polar Type3,
Connected Port 4, Polar Type4, Uplink
Tilt(0.1degree), Downlink
Tilt(0.1degree),
BeamAzimuth(0.1degree),
BeamWidth(0.1degree)

SECTOR User-defined Sector ID, Sector Name, Location N/A


sheet Name, User Label, Antenna
Azimuth(0.1degree), Sector Antenna

SECTOREQ User-defined Sector Equipment ID, Sector ID, N/A


M sheet Sector Equipment Antenna

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

Step 1 Choose CME > Customize Summary Data File from the main menu of a U2000 client, or
choose 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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized 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
the main menu of the CME client, to import the summary data file into the CME.

----End

10.2.5.3 Using the CME to Perform Single Configuration


On the CME, set the parameters listed in 10.2.2 Data Preparation for a single eNodeB. For
configuration steps, see CME Single Configuration Operation Guide.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 35


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.2.5.4 Using MML Commands


Perform 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 AARU
in 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 AARU
Work Standard to UO, Number of RX channels to 2, Number of TX channels to 2, and Slot
No. to 1.
Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. In
this step, set the DEVICENAME and SUBUNITQUANTITY parameters to appropriate
values. The default value of the SUBUNITQUANTITY parameter is 8. Note that the value of
the DEVICENO parameter must be the same as the value of the SRN parameter for the
previously added AAS.
Step 5 Run the MOD VRETSUBUNIT command. In this step, set DLTILT to the planned value for
a 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 and sector equipment
antenna.
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 Examples


The following is a 2T2R configuration example:
//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;
//Adding an AAS
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";
//Adding an AARU
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 MO
MOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;
//Modifying the configurations of a virtual RET subunit
MOD 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,

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 36


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

BEAMAZIMUTH=0, BEAMWIDTH=650;
//Associating a virtual RET subunit with a sector
ADD 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 equipment and sector equipment antennas
ADD 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 cell
ADD 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 equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=10;
//Setting the cell power parameters
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=152, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB_3_P_A;
//Activating the cell
ACT CELL: LocalCellId=0;

NOTE

1. VRETNO and DEVICENO are used for the same object and their values must be identical.
2. VRETSUBUNIT provides the RET configuration for a port, which must be identical with the
RX/TX port in SECTOREQM.
3. When the AAU3902 is working in multiple modes, all the AARUs must be configured on each
working mode and the working mode of each AARU must be set according to the actual situation.
Otherwise, services will be interrupted. For example, when an AAU3902 is working in 1800 MHz
(LO) and 2100 MHz (UO) bands, all AARUs of the AAU must be configured on both the UMTS
and LTE sides and the working mode of the AARUs must be set to UL.

10.2.6 Activation Observation


Perform 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 Channels


for LTE

10.3.1 Application Suggestions


This 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 Information


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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 37


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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


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

10.3.3 Planning

RF 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 Planning
None.

Hardware Planning
The hardware planning for this feature is the same as that for LOFD-001005 UL 4-Antenna
Receive Diversity, and the LBBPd, UBBPd and UBBPe are required.

NOTE

l The LBBPd1, LBBPd3, and UBBPd3 do not support LOFD-001005 UL 4-Antenna Receive
Diversity.
l The UBBPd4 do not support hybrid configuration of 2R and 4R cells.
l The LBBPd2 and UBBPd5 support hybrid configuration of 2R and 4R cells. In this scenario, a
maximum of three cells are supported.
l The UBBPd6 supports hybrid configuration of 2R and 4R cells. In this scenario, a maximum of three
2R cells and three 4R cells are supported.
l Under hybrid configuration of 2R and 4R cells supported by the LBBPd2, UBBPd5, and UBBPd6,
there is no activation sequence when 2R and 4R cells are being activated.

10.3.4 Deployment

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

10.3.4.2 Data Preparation


For 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 Precautions
None.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 38


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.3.4.4 Hardware Adjustment


For 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 eNodeBs
Enter the values of the parameters listed in Table 10-8 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.

The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
parameters.

Table 10-8 MOs related to AAS Virtual Four Uplink Channels for LTE

MO Sheet in the Parameter Group Remarks


Summary
Data File

RRUCHAIN EQUIPMENT Chain No., Topo Type, Backup Mode, N/A


Access Type, Head Cabinet No., Head
Subrack No., Head Slot No., Head
Port No., Tail Cabinet No., Tail
Subrack No., Tail Slot No., Tail Port
No., BreakPoint Position1, BreakPoint
Position2, CPRI Line Rate(Gbit/s),
Local Slot No., Protocol Type

AAS EQUIPMENT Cabinet No., Subrack No., AAS N/A


Name, AAU Specification

AARU AAS Cabinet No., Subrack No., Slot No., When


Administrative State, AARU Work multiple
Standard, AARU Name, Number of AARUs
RX channels, Number of TX channels, are
Intermediate Frequency configure
Offset(100KHz), Logical Switch of d in the
TX Channel, Frequency Min AAS, the
Bandwidth, VRET No. informati
on about
all
AARUs
is
required.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 39


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

MO Sheet in the Parameter Group Remarks


Summary
Data File

AAMU User-defined Cabinet No., Subrack No., Slot No., N/A


sheet RRU Topo Position, RRU Chain No.,
AAS Position

VRET AARU Device No., Cabinet No., Subrack N/A


No., Slot No., Device Name, Subunit
Quantity

VRETSUBU VRET Device No., Subunit No., Subunit N/A


NIT Name, Cabinet No., Subrack No., Slot
No., PORTNUM, Connected Port 1,
Polar Type1, Connected Port 2, Polar
Type2, Connected Port 3, Polar Type3,
Connected Port 4, Polar Type4, Uplink
Tilt(0.1degree), Downlink
Tilt(0.1degree),
BeamAzimuth(0.1degree),
BeamWidth(0.1degree)

SECTOR CARRIERRES Sector ID, Sector Name, Location N/A


OURCE Name, User Label, Antenna
Azimuth(0.1degree), Sector Antenna

SECTOREQ CARRIERRES Sector Equipment ID, Sector ID, N/A


M OURCE Sector Equipment Antenna

CELL eNodeBFunctio Local Cell ID, Cell Name, Cell ID, N/A
n Uplink cyclic prefix length, Downlink
cyclic prefix length, Frequency band,
Uplink EARFCN indication, Uplink
EARFCN, Downlink EARFCN,
Downlink bandwidth, Uplink
bandwidth, PCI, Additional spectrum
emission, Cell active state, Cell admin
state, Cell middle block timer, Cell
FDD TDD indication, Cell specific
offset, Frequency offset, Root
sequence index, High speed flag,
Preamble format, Cell radius,
Customized bandwidth configure
indicator, Customized uplink
bandwidth, Customized downlink
bandwidth, Emergency Area Id
indicator, Emergency Area Id
indicator, Ue max power allowed
configure indicator, Max transmit
power allowed, Cell transmission and
reception mode

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 40


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

MO Sheet in the Parameter Group Remarks


Summary
Data File

CnOperator eNodeBFunctio CN Operator ID, CN Operator name, N/A


n CN Operator type, Mobile country
code, Mobile network code

CnOperator eNodeBFunctio Local tracking area ID, Tracking area N/A


TA n code, CN Operator ID

CellOp Cell Local cell ID, Local tracking area ID N/A

eUCellSecto Cell Local cell ID, Sector equipment ID, N/A


rEqm Baseband equipment ID

PDSCHCFg Cell Local cell ID, Reference signal power N/A

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

Step 1 Choose CME > Customize Summary Data File from the main menu of a U2000 client, or
choose 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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-8 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
the main menu of the CME client, to import the summary data file into the CME.

----End

10.3.4.5.3 Using the CME to Perform Single Configuration


On the CME, set the parameters listed in 10.3.4.2 Data Preparation for a single eNodeB. For
configuration steps, see CME Single Configuration Operation Guide.

10.3.4.5.4 Using MML Commands


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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 41


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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 AARU
in 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 AARU
Work Standard to UO, Number of RX channels to 2, Number of TX channels to 2, and Slot
No. to 1.
Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. In
this step, set the DEVICENAME and SUBUNITQUANTITY parameters to appropriate
values. The default value of the SUBUNITQUANTITY parameter is 8. Note that the value of
the DEVICENO parameter must be the same as the value of the VRETNO parameter for the
AARU.
Step 5 Run the MOD VRETSUBUNIT command to configure virtual RET subunit 1. In this step:
l Set the PORTNUM parameter to 4.
l Set all of the POLARTYPE1, POLARTYPE2, POLARTYPE3, and POLARTYPE4
parameters to POSITIVE_NEGATIVE_45(POSITIVE_NEGATIVE_45).
Step 6 Run the ADD SECTOR command to associate virtual RET subunits with sectors. In this step:
l For sector 0:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 1.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 1, respectively.
l For sector 1:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 2.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 2, respectively.
Step 7 Run the ADD SECTOREQM command to add sector equipment and sector equipment
antennas.
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.3.4.5.5 MML Command Examples


The following is a 2T4R configuration example:
//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;
//Adding an AAS to the RRU chain or ring
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 42


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

//Adding an AARU
ADD AARU: CN=0, SRN=60, SN=3, RS=LO, AN="AARU_1", RXNUM=4, 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 MO
MOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;
//Configuring a virtual RET antenna
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=1, PORTNUM=4, CONNPN1=R0A, CONNPN2=R0B,
CONNPN3=R1A, CONNPN4=R1B, ULTILT=40, DLTILT=40;
//Adding a sector
ADD SECTOR: SECTORID=0, SECNAME="sector", LOCATIONNAME="huawei", ANTNUM=4,
ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=3, ANT3N=R1A, ANT4CN=0, ANT4SRN=60,
ANT4SN=3, ANT4N=R1B, CREATESECTOREQM=FALSE;
//Adding sector equipment and sector equipment antennas
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANTTYPE2=RXTx_MODE, ANT3CN=0, ANT3SRN=60, ANT3SN=3, ANT3N=R1A,
ANTTYPE3=RX_MODE, ANT4CN=0, ANT4SRN=60, ANT4SN=3, ANT4N=R1B, ANTTYPE4=RX_MODE;
//Adding operator information for a cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Adding a local cell
ADD CELL: LocalCellId=0, CellName="lte", 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=2T4R;
//Adding a relationship between the cell and the sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
//Setting the cell power parameters
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=152, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB_3_P_A;
//Activating the cell
ACT CELL: LocalCellId=0;

NOTE

1. VRETNO and DEVICENO are used for the same object and their values must be identical.
2. VRETSUBUNIT provides the RET configuration for a port, which must be identical with the
RX/TX port in SECTOREQM.
3. When the AAU3902 is working in multiple modes, all the AARUs must be configured on each
working mode and the working mode of each AARU must be set according to the actual situation.
Otherwise, services will be interrupted. For example, when an AAU3902 is working in 1800 MHz
(LO) and 2100 MHz (UO) bands, all AARUs of the AAU must be configured on both the UMTS
and LTE sides and the working mode of the AARUs must be set to UL.

10.3.4.6 Activation Observation


Perform the following operations after the Vertical Four Uplink Channels feature was
activated:
l Check whether any alarms were falsely generated.
l Run the DSP VRETSUBUNIT, DSP SECTOR, and DSP CELL commands to query
the status of virtual RET subunits, sectors, and cells, respectively.
On the U2000 client, perform the following steps:

Step 1 Choose Monitor > Signaling Trace > Signaling Trace Management.
Step 2 In the navigation tree of the Signaling Trace Management window, choose Cell
Performance Monitoring > RSSI Statistic Monitoring.
Step 3 In the displayed dialog box, select an eNodeB and set the local ID of the cell to be traced.
Then, click Finish to start a tracing task.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 43


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Step 4 Observe the real-time values of antenna 0 RSSI(dBm), antenna 1 RSSI(dBm), antenna 2
RSSI(dBm), and antenna 3 RSSI(dBm). If none of the values is N/A, four receive antennas
have been configured and this feature have been activated.

----End

10.3.5 Performance Monitoring


After the feature is activated, monitor the following counters related to access, service, and
handover.

Table 10-9 Counters to query


Counter Name Formula

RRC Setup Success Rate Number of successful RRC connection setups in a cell/Number
of RRC connection setup attempts in a cell = L.RRC
ConnReq.Succ/L.RRC.ConnSetup x 100%

eRAB Setup Success Number of successful E-RAB setups in a cell/Number of E-


Rate RAB setup attempts in a cell = L.E-RAB.SuccEst/L.E-
RAB.AttEst x 100%

Intra-Freq HO Success (Number of successful intra-eNodeB outgoing handovers in a


Rate cell + Number of successful inter-eNodeB outgoing handovers
in a cell)/(Number of intra-eNodeB outgoing handovers
executions in a cell + Number of inter-eNodeB outgoing
handovers executions in a cell) =
(L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%

Call Drop Rate Number of abnormal E-RAB releases in a cell/(Number of


abnormal E-RAB releases in a cell + Number of normal E-RAB
releases in a cell) = L.E-RAB.AbnormRel/(L.E-
RAB.AbnormRel + L.E-RAB.NormRel) x 100%

Distribution of INs on L.UL.Interference.PUSCH


the PUSCH

Maximum uplink L.UL.Interference.Max


interference and noise
received by each PRB in
a cell

Number of Times an L.ChMeas.PUSCH.MCS


MCS Index Is Scheduled
on the PUSCH

Average number of used L.ChMeas.PRB.PUCCH.Avg


PRBs over the PUCCH

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 44


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Counter Name Formula

Uplink user-perceived Uplink traffic volume for PDCP PDUs in a cell/Receive


rate duration of uplink PDCP PDUs in a cell
= L.Thrp.bits.UL/L.Thrp.Time.UL x 100%

10.3.6 Parameter Optimization


If the cell radius is large, reducing the uplink downtilt angle can improve uplink coverage.
However, if the inter-cell distance is short, reducing the uplink downtilt angle increases uplink
interference and deteriorates the performance.

10.3.7 Possible Issues


l Fault symptom
The feature fails to be enabled or this feature is configured but is ineffective.
l Solution
– Check whether the same AAS is configured with any feature that is mutually
exclusive with LOFD-261101 AAS Virtual Four Uplink Channels for LTE. For
details, see 8 Related Features.
– Check whether ALM-26532 RF Unit Hardware Fault is generated on the same
AAS. If so, the AAS Virtual Four Uplink Channels for LTE feature fails to be
enabled.

10.4 Deployment of AAS User Specific Tilting for LTE

10.4.1 Application Suggestions


To expand the capacity on hot spots, this feature is recommended if the following conditions
are all met:
l No extra frequencies are available to the operator.
l Cells selected for user specific tilting provide continuous coverage.
l The coverage is not restricted, for example, in densely populated urban areas or common
urban areas. In densely populated urban areas, the site height is greater than 25 m, and
the distance between two eNodeBs is less than or equal to 500 m. In common urban
areas, the site height is greater than 30 m, and the distance between two eNodeBs is less
than 1000 m.
l The downtilt angle on the site is smaller than or equal to 10°.
l There is traffic in cell centers.
l UEs support DL 4x2 MIMO or DL 4x4 MIMO.

10.4.2 Required Information


l The required information for this feature is the same as that for LOFD-261101 AAS
Virtual Four Uplink Channels for LTE. For details, see 10.3.2 Required Information.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 45


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.4.3 Planning

RF Planning
The suggestions for RF planning are as follows:

l Set the downtilt angles to the values used in 2T.


Compared with the RS beam in 2T, the RS beam generated after user specific tilting has
a decrease of about 3 dB in the main lobe gain and an increase in the beamwidth. It is
recommended that the initially configured downtilt angles be the same as those used in
2T; that is, the outer edges of these beams coincide with those of 2T beams.
l Set the power as follows.
Power planning is different from that of traditional 4T. The reference signal (RS) beam
gain is less than the data beam gain. Therefore, it is good practice to double the power.
That is, set the RS power to be 3 dB greater than the rated power of 2T, set PA to –3,
and set PB to 1 to provide optimal performance. If it is not allowed to double the power,
set the RS power to be about 1.77 dB greater than the power configuration of 2T, set PA
to –4.77, and set PB to 2. In this case, the performance of UST deteriorates.
For example, the normal configurations for 2T are as follows:
Total Power = 40 W, RS Power = 15.2 dBm, PA = -3, PB = 1;
The UST configurations are as follows:
Total Power = 80 W, RS Power = 18.2 dBm, PA = -3, PB = 1.
If it is not allowed to double the power, set the UST as follows:
Total Power = 40 W, RS Power = 16.9 dBm, PA = -4.77, PB = 2.
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 Planning
None.

Hardware Planning
The user specific tilting requires LBBPd, UBBPd or UBBPe.

Table 10-10 lists the required CPRI bit rates and the maximum number of cells under
different configurations of system bandwidths and antennas.

NOTE

The LBBPd1, LBBPd3, UBBPd2, and UBBPd3 boards do not support LOFD-001003 DL 4X2 MIMO
and LOFD-001060 DL 4X4 MIMO.

Table 10-10 CPRI bit rates and maximum number of cells

CPRI Bit Rate Maximum Number of Cells

≤ 10 MHz, 15 or 20 MHz, ≤ 10 MHz, 15 or 20 MHz,


2 Antennas 2 Antennas 4 Antennas 4 Antennas

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 46


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

1.25 Gbit/s 1 Not supported Not supported Not supported

2.5 Gbit/s 2 1 1 Not supported

4.9 Gbit/s 4 2 2 1

6.144 Gbit/s 4 2 2 1

9.8 Gbit/s 4 Not supported 4 Not supported

10.4.4 Deployment

10.4.4.1 Requirements
Purchase the license for LOFD-261102 AAS User Specific Tilting for LTE, LOFD-001001
DL 2x2 MIMO, and LOFD-001003 DL 4x2 MIMO.

To support DL 4x4 MIMO, you also need to purchase the license for LOFD-001060 DL 4x4
MIMO.

10.4.4.2 Data Preparation


For 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.4.4.3 Precautions
None.

10.4.4.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.4.4.5 Initial Configuration

10.4.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 10-8 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.

The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
parameters.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 47


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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

Step 1 Choose CME > Customize Summary Data File from the main menu of a U2000 client, or
choose 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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-8 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
the main menu of the CME client, to import the summary data file into the CME.

----End

10.4.4.5.3 Using the CME to Perform Single Configuration


On the CME, set the parameters for a single eNodeB, as listed in 10.4.4.2 Data Preparation.
For configuration steps, see CME Single Configuration Operation Guide.

10.4.4.5.4 Using MML Commands


Perform 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 4,
and TXNUM to 4.
When multiple AARUs are installed on the AAS, configure all the AARUs. To add an AARU
in 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 AARU
Work Standard to UO, Number of RX channels to 2, Number of TX channels to 2, and Slot
No. to 1.
Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. In
this step, set the Device Name and Subunit Quantity parameters to appropriate values. The
default value of the Subunit Quantity parameter is 8.
Note that the value of the Device No. parameter must be the same as the value of the Subrack
No. parameter for the previously added AAS.
Step 5 Run the MOD VRETSUBUNIT command to configure virtual RET subunit 1. In this step:
l Set the PORTNUM parameter to 4.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 48


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

l Set all of the POLARTYPE1, POLARTYPE2, POLARTYPE3, and POLARTYPE4


parameters to POSITIVE_NEGATIVE_45(POSITIVE_NEGATIVE_45).
Step 6 Run the ADD SECTOR command to associate virtual RET subunits with sectors. In this step:
l For sector 0:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 1.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 1, respectively.
l For sector 1:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 2.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 2, respectively.
Step 7 Run the ADD SECTOREQM command to add sector equipment and sector equipment
antennas.
Step 8 Run the ADD CELL command to add a cell.
Step 9 Run the ADD EUCELLSECTOREQM command to add a relationship between the cell and
the sector equipment.
Step 10 Run the MOD CELLMIMOPARACFG command to set the MIMO mode to TM4.
Step 11 Run the MOD PDSCHCFG and MOD CELLDLPCPDSCHPA commands to set the cell
power parameters, including the ReferenceSignalPwr, PA, and PB.
Step 12 Run the ACT CELL command to activate the cell.

----End

10.4.4.5.5 MML Command Examples


The following is a 4T4R configuration example:
//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;
//Adding an AAS to the RRU chain or ring
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";
//Adding an AARU
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 MO
MOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;
//Configuring a virtual RET subunit
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=1, PORTNUM=4, CONNPN1=R0A, CONNPN2=R0B,
CONNPN3=R1A, CONNPN4=R1B, ULTILT=40, DLTILT=40;
//Adding a sector
ADD SECTOR: SECTORID=0, SECNAME="sector", LOCATIONNAME="huawei", ANTNUM=4,
ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=3, ANT3N=R1A, ANT4CN=0, ANT4SRN=60,
ANT4SN=3, ANT4N=R1B, CREATESECTOREQM=FALSE;
//Adding sector equipment and sector equipment antennas
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANTTYPE2=RXTx_MODE, ANT3CN=0, ANT3SRN=60, ANT3SN=3, ANT3N=R1A,
ANTTYPE3=RXTx_MODE, ANT4CN=0, ANT4SRN=60, ANT4SN=3, ANT4N=R1B,
ANTTYPE4=RXTx_MODE;
//Adding operator information for a cell

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 49


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;


//Adding a local cell
ADD CELL: LocalCellId=0, CellName="lte", 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_4,
TxRxMode=4T4R;
//Adding a relationship between the cell and the sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
//Setting the cell power parameters
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=152, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB_6_P_A;
//Activating the cell
ACT CELL: LocalCellId=0;

NOTE

1. VRETNO and DEVICENO are used for the same object and their values must be identical.
2. VRETSUBUNIT provides the RET configuration for a port, which must be identical with the
RX/TX port in SECTOREQM.
3. When the AAU3902 is working in multiple modes, all the AARUs must be configured on each
working mode and the working mode of each AARU must be set according to the actual situation.
Otherwise, services will be interrupted. For example, when an AAU3902 is working in 1800 MHz
(LO) and 2100 MHz (UO) bands, all AARUs of the AAU must be configured on both the UMTS
and LTE sides and the working mode of the AARUs must be set to UL.

10.4.4.6 Activation Observation


Perform the following operators to check whether the feature has been activated:
l Check whether there are alarms.
l Run the DSP VRETSUBUNIT, DSP SECTOR, and DSP CELL commands to query
the status of virtual RET subunits, sectors, and cells, respectively.

10.4.5 Performance Monitoring


After feature activation, check the values of the counters listed in Table 10-11 to determine
performance gains provided by this feature.

Table 10-11 Counters to query


Counter Name Formula

Number of Used L.ChMeas.MIMO.PRB


Downlink PRBs in
MIMO Mode

RRC Setup Success Rate Number of successful RRC connection setups in a cell/Number
of RRC connection setup attempts in a cell = L.RRC
ConnReq.Succ/L.RRC.ConnSetup x 100%

eRAB Setup Success Number of successful E-RAB setups in a cell/Number of E-


Rate RAB setup attempts in a cell = L.E-RAB.SuccEst/L.E-
RAB.AttEst x 100%

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 50


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Counter Name Formula

Intra-Freq HO Success (Number of successful intra-eNodeB outgoing handovers in a


Rate cell + Number of successful inter-eNodeB outgoing handovers
in a cell)/(Number of intra-eNodeB outgoing handovers
executions in a cell + Number of inter-eNodeB outgoing
handovers executions in a cell) =
(L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%

Call Drop Rate Number of abnormal E-RAB releases in a cell/(Number of


abnormal E-RAB releases in a cell + Number of normal E-RAB
releases in a cell) = L.E-RAB.AbnormRel/(L.E-
RAB.AbnormRel + L.E-RAB.NormRel) x 100%

Downlink PRB Usage Average number of used PDSCH PRBs/Number of available


downlink PRBs = L.ChMeas.PRB.DL.Used.Avg/
L.ChMeas.PRB.DL.Avail x 100%

Number of Times a L.ChMeas.PDSCH.MCS


Specific MCS Index Is
Scheduled on the
PDSCH

Number of OFDM L.ChMeas.PDCCH.SymNum


Symbols Occupied by
the PDCCH

Downlink user- Downlink traffic volume for PDCP SDUs in a cell/Total


perceived rate duration of downlink data transmission in a cell =
L.Thrp.bits.DL/L.Thrp.Time.Cell.DL x 100%

10.4.6 Parameter Optimization


If the call completion rate, service drop rate, or handover success rate deteriorates, use
traditional RF optimization methods to optimize network performance and KPIs.
To achieve the optimal performance, you are advised to set the user specific downtilt angles
and RS power to the values used in 2T, set PA to -6, and set PB to 1. In this situation, the RS
power exceeds the threshold by 1.25 dB. If the symbol power is not allowed to exceed the
threshold, set the RS power to be about 1.2 dB lower than the power configuration of 2T, set
PA to -4.77, and PB to 2.
Compared with the RS beam in 2T, the RS beam generated after user specific tilting has a
decrease of about 3 dB in the main lobe gain, which leads to a reduction of about 3-5 dB in
the edge coverage level. To improve the edge coverage, you can lift the cell transmit power to
increase the RS power.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 51


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.4.7 Possible Issues


l Fault symptom
The feature fails to be enabled or this feature is configured but is ineffective.
l Solution
– Check whether the same AAS is configured with any feature that is mutually
exclusive with LOFD-261102 AAS User Specific Tilting for LTE. For details, see 8
Related Features.
– Check whether ALM-26532 RF Unit Hardware Fault is generated on the same
AAS. If so, LOFD-261102 AAS User Specific Tilting for LTE cannot be used.

10.5 Deployment of AAS Vertical Multiple Sectors for LTE

10.5.1 Application Suggestions


Use this feature in hot spots when the following conditions are met:

l In densely-populated urban areas, the site height is higher than 25 m, and the distance
between two eNodeBs is less than 500 m.
l The downtilt angle on the site is smaller than or equal to 10°.
l Traffic is available near the site. Deploy this feature in scenarios where traffic in inner
cells accounts for 40% to 80% of the total traffic.

If users are mainly located in the overlapping areas between inner and outer cells, or only in
inner cells or outer cells, this feature is not recommended because it cannot provide any gain.

10.5.2 Required Information


The required information is the same as that for LOFD-261101 AAS Virtual Four Uplink
Channels for LTE. For details, see 10.3.2 Required Information.

10.5.3 Planning

RF planning
RF planning involves the following:

l Frequency planning: An inner cell must use the same frequency as its corresponding
outer cell.
l Power configurations: The maximum transmit power of the AAU3902 is 2x40 W.
– If the total transmit power of the inner and outer cells does not reach the maximum
transmit power of the target AAS after sector splitting, it is recommended that the
transmit power of an inner cell and the corresponding outer cell be the same as the
transmit power of the original cell.
For example, if the transmit power of a cell using the AAU3902 is 30 W before
sector splitting, it is recommended that the transmit power of the inner and outer
cells be 30 W respectively after sector splitting. Therefore, the total transmit power
is 60 W, which does not exceed the maximum transmit power of the AAU3902.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 52


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

– If the total transmit power of the inner and outer cells exceeds the maximum
transmit power of the target AAS after sector splitting, it is recommended that the
transmit power of an inner cell and the corresponding outer cell be half of the
transmit power of the original cell.
For example, if the transmit power of a cell using the AAU3902 is 50 W before
sector splitting, the transmit power of the inner and outer cells is still 50 W after
sector splitting. In this case, the maximum transmit power of the AAU3902 is
exceeded and your are advised to reduce the transmit power of the inner and outer
cells to 25 W respectively. In this case, the total transmit power is 50 W, which does
not exceed the maximum transmit power of the AAU3902. You can also increase
the transmit power of each cell, but the total transmit power of inner and outer cells
cannot exceed the maximum transmit power of the AAS. For example, you can
increase the transmit power of each cell to 30 W. As a result, the total transmit
power is 60 W, which is a little higher than that before sector splitting.
l Downtilt angle planning: Ensure that the downtilt angle of the outer cell is equal to that
of the original cell, and downtilt angle of the inner cell is equal to the sum of the outer
cell downtilt angle and the downtilt angle difference. In addition, avoid the sector border
from deviation as possible as you can.
l PRACH/PCI planning: After three sectors are split into six sectors, the number of
PRACH/PCI reuse times becomes smaller, the reuse distance becomes shorter, and the
possibility of PRACH/PCI conflicts will increase. To reduce this possibility, you can use
the U-NET tool to for sector planning.
l Neighboring cell planning: The original neighbor relationships require re-planning or
optimization. You can use the ANR feature and perform drive tests to optimize neighbor
relation tables (NRTs).
If you manually configure an NRT, pay attention to the following:
– For the outer cell, add the intra-frequency inner cells and inter-frequency inner cells
at this site and neighboring sites to the intra-frequency NRT.
– For the inner cell, copy the NRT of the corresponding outer cell and add the outer
cell to this NRT.
– After this feature is enabled, the network topology changes. Therefore, neighboring
cell planning is also affected. For the neighboring cells of the original outer cell,
add the intra-/inter-frequency inner cell in the intra-/inter-frequency neighboring
cell list so that call drops will not occur.

Network Planning
None.

Hardware Planning
This feature requires the addition of new cells. If the existing baseband processing units
cannot accommodate these new cells, additional baseband processing units must be installed.

10.5.4 Deployment

10.5.4.1 Requirements
Purchase the license for LOFD-261103 AAS Vertical Multiple Sectors for LTE.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 53


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

10.5.4.2 Data Preparation


For 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.
Table 10-12 lists the parameters that must be set in a Cell MO.

Table 10-12 Key parameters in the Cell MO


Parameter Paramete Setting Notes Data Source
Name r ID

Uplink UlEarfcn Set the uplink frequencies of the two User-defined


EARFCN cells to the same value.

Downlink DlEarfcn Set the downlink frequencies of the two User-defined


EARFCN cells to the same value.

10.5.4.3 Precautions
None.

10.5.4.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.5.4.5 Initial Configuration

10.5.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 10-8 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
parameters.

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

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 54


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-8 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
the main menu of the CME client, to import the summary data file into the CME.

----End

10.5.4.5.3 Using the CME to Perform Single Configuration


On the CME, set the parameters for a single eNodeB, as listed in 10.5.4.2 Data Preparation.
For configuration steps, see CME Single Configuration Operation Guide.

10.5.4.5.4 Using MML Commands


Perform 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 AARU
in UMTS mode in slot 1, perform the following operation:
Run the ADD AARU command to add an AARU. In this step, set AARU Work Standard to
UO, Number of RX channels to 2, Number of TX channels to 2, and Slot No. to 1.
Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. In
this step, set the DEVICENAME and SUBUNITQUANTITY parameters to appropriate
values. The default value of the SUBUNITQUANTITY parameter is 8.
Note that the value of the DEVICENO parameter must be the same as the value of the SRN
parameter for the previously added AAS.
Step 5 Run the MOD VRETSUBUNIT command to set the ULTILT and DLTILT parameters of
virtual RET subunits 1 and 2 to the planned values.
Step 6 Run the ADD SECTOR command to associate virtual RET subunits with sectors. In this step:
l For sector 0:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 1.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 1, respectively.
l For sector 1:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 2.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 55


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 2, respectively.
Step 7 Run the ADD SECTOREQM command to add sector equipment and sector equipment
antennas.
Step 8 Run the ADD CELL command twice to add two local cells in total.
Step 9 Run the ADD EUCELLSECTOREQM command to add a relationship between a 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.5.4.5.5 MML Command Examples


//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HCN=0, HSN=3, HPN=0;
//Adding an AAS to the RRU chain or ring
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";
//Adding an AARU
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 the configurations of a VRET antenna
MOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;
//Modifying the configurations of virtual RET subunit 1
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=1, PORTNUM=2, CONNPN1=R0A, CONNPN2=R0B,
ULTILT=0, DLTILT=0;
//Modifying the configurations of virtual RET subunit 2
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=2, PORTNUM=2, CONNPN1=R1A, CONNPN2=R1B,
ULTILT=20, DLTILT=20;
//Adding two sectors
ADD SECTOR: SECTORID=10, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R0A,
ANT2CN=0, ANT2SRN=60, ANT2SN=3, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=11, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R1A,
ANT2CN=0, ANT2SRN=60, ANT2SN=3, ANT2N=R1B, CREATESECTOREQM=FALSE;
//Adding two sets of sector equipment and sector equipment antennas
ADD SECTOREQM: SECTOREQMID=10, SECTORID=10, ANTNUM=2, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=11, SECTORID=11, ANTNUM=2, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R1A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R1B, ANTTYPE2=RXTX_MODE;
//Adding operator information for a cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=1, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Adding two cells
ADD CELL: LocalCellId=0, CellName="lte", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1550, UlBandWidth=CELL_BW_N25, DlBandWidth=CELL_BW_N25, CellId=0,
PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
TxRxMode=2T2R;
ADD CELL: LocalCellId=1, CellName="lte", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1550, UlBandWidth=CELL_BW_N25, DlBandWidth=CELL_BW_N25, CellId=1,
PhyCellId=1, FddTddInd=CELL_FDD, RootSequenceIdx=1,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
TxRxMode=2T2R;
//Adding relationships between the cells and the sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=10;
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=11;

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 56


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

//Setting the cell power parameters


MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=122, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB3_P_A;
MOD PDSCHCFG: LocalCellId=1, ReferenceSignalPwr=122, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=1, PaPcOff=DB3_P_A;
//Activating the cells
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1;

NOTE

1. VRETNO and DEVICENO are used for the same object and their values must be identical.
2. VRETSUBUNIT provides the RET configuration for a port, which must be identical with the
RX/TX port in SECTOREQM.
3. When the AAU3902 is working in multiple modes, all the AARUs must be configured on each
working mode and the working mode of each AARU must be set according to the actual situation.
Otherwise, services will be interrupted. For example, when an AAU3902 is working in 1800 MHz
(LO) and 2100 MHz (UO) bands, all AARUs of the AAU must be configured on both the UMTS
and LTE sides and the working mode of the AARUs must be set to UL.

10.5.4.6 Activation Observation


Perform the following operations after the Vertical Multiple Sectors feature was activated:
l Check whether any alarms were falsely generated.
l Run the DSP VRETSUBUNIT and DSP SECTOR commands to query the status of
virtual RET subunits and sectors, respectively.
l Run the DSP CELL command to check whether each pair of inner and outer cells is
successfully set up.

10.5.5 Performance Monitoring


After feature activation, check the values of the counters listed in Table 10-13 to determine
performance gains provided by this feature.

Table 10-13 Counters to query


Counter Name Formula

Number of Used L.ChMeas.MIMO.PRB


Downlink PRBs in
MIMO Mode

RRC Setup Success Rate Number of successful RRC connection setups in a cell/Number
of RRC connection setup attempts in a cell = L.RRC
ConnReq.Succ/L.RRC.ConnSetup x 100%

eRAB Setup Success Number of successful E-RAB setups in a cell/Number of E-


Rate RAB setup attempts in a cell = L.E-RAB.SuccEst/L.E-
RAB.AttEst x 100%

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 57


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Counter Name Formula

Intra-Freq HO Success (Number of successful intra-eNodeB outgoing handovers in a


Rate cell + Number of successful inter-eNodeB outgoing handovers
in a cell)/(Number of intra-eNodeB outgoing handovers
executions in a cell + Number of inter-eNodeB outgoing
handovers executions in a cell) = =
(L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%

Call Drop Rate Number of abnormal E-RAB releases in a cell/(Number of


abnormal E-RAB releases in a cell + Number of normal E-RAB
releases in a cell) = L.E-RAB.AbnormRel/(L.E-
RAB.AbnormRel + L.E-RAB.NormRel) x 100%

Average Number of L.Traffic.User.Avg


Users in a Cell

Average number of used L.ChMeas.PRB.PUCCH.Avg


PRBs over the PUCCH

Number of OFDM L.ChMeas.PDCCH.SymNum


Symbols Occupied by
the PDCCH

Uplink PRB Usage Average number of used uplink PRBs/Number of available


uplink PRBs = L.ChMeas.PRB.UL.Used.Avg/
L.ChMeas.PRB.UL.Avail x 100%

Downlink PRB Usage Average number of used downlink PRBs/Number of available


downlink PRBs = L.ChMeas.PRB.DL.Used.Avg/
L.ChMeas.PRB.DL.Avail x 100%

Uplink user-perceived Uplink traffic volume for PDCP PDUs in a cell/Receive


rate duration of uplink PDCP PDUs in a cell
= L.Thrp.bits.UL/L.Thrp.Time.UL x 100%

Downlink user- Downlink traffic volume for PDCP SDUs in a cell/Total


perceived rate duration of downlink data transmission in a cell =
L.Thrp.bits.DL/ L.Thrp.Time.Cell.DL x
100%L.Thrp.Time.Cell.DL

10.5.6 Parameter Optimization


This feature impacts KPIs such as the call completion rate and service drop rate. Particularly,
the service drop rate decreases by 10% to 20% each day in some scenarios. You can use the
traditional methods for optimization.
To avoid abnormal coverage or strong interference after the AAS Vertical Multiple Sectors for
LTE feature is enabled, use the fixed outer cell downtilt angle and ensure that the absolute RS
power of the outer cell remains the same so that outer cell coverage remains the same. Set the

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 58


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

downtilt angle difference between the outer cell and inner cell to maximum DT value (6° for
the AAU3902 1.8GHz). For details, see "Technical Specifications of AAUs" in 3900 Series
Base Station Technical Description. Therefore, do not optimize the preceding parameters.

10.5.7 Possible Issues


l Fault symptom
The feature fails to be enabled or this feature is configured but is ineffective.
l Solution
– Check whether the same AAS is configured with any feature that is mutually
exclusive with the AAS Vertical Multiple Sectors for LTE feature. For details, see 8
Related Features.
– Check whether ALM-26532 RF Unit Hardware Fault is generated on the same
AAS. If so, the AAS Vertical Multiple Sectors for LTE feature fails to be enabled.
l Fault symptom
KPIs deteriorate after this feature is enabled.
l Solution
Observe the KPIs after this feature is enabled. If KPIs deteriorate, take the same KPI
optimization methodology as for common sites.

10.6 Deployment of AAS Dividual Tilts by Carrier for LTE

10.6.1 Application Suggestions


Use the AAS Dividual Tilts by Carrier for LTE feature when the following conditions are met:

l The operator has two or more frequencies serving the same mode in the same frequency
band.
l Traffic near the cell center is dense.

10.6.2 Required Information


The required information for this feature is the same as that for LOFD-261101 AAS Virtual
Four Uplink Channels for LTE. For details, see 10.3.2 Required Information.

10.6.3 Planning

RF Planning
Before deploying this feature, make a traffic map.

Conduct a network planning simulation test based on the traffic map. Determine the optimal
capacity by adjusting the downtilt angles.

Network Planning
None.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 59


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Hardware Planning
The AAU3902 must be configured.

10.6.4 Deployment

10.6.4.1 Requirements
Purchase the license for AAS Dividual Tilts by Carrier for LTE.

10.6.4.2 Data Preparation


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

For the parameters that must be set in a Cell MO, see Table 10-12.

10.6.4.3 Precautions
None.

10.6.4.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.6.4.5 Initial Configuration

10.6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 10-8 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration.

The summary data file may be a scenario-specific file provided by the CME or a customized
file, 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 the
parameters.

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

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

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 60


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

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 the
U2000 client, or choose Advanced > Export Base Station Bulk Configuration Data from
the main menu of the CME client, to export the eNodeB data stored on the CME into the
customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-8 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
the main menu of the CME client, to import the summary data file into the CME.

----End

10.6.4.5.3 Using the CME to Perform Single Configuration


On the CME, set the parameters listed in 10.6.4.2 Data Preparation for a single eNodeB. For
configuration steps, see CME Single Configuration Operation Guide.

10.6.4.5.4 Using MML Commands


Perform 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 AARU
in UMTS mode in slot 1, perform the following operation:
Run the ADD AARU command to add an AARU. In this step, set AARU Work Standard to
UO, Number of RX channels to 2, Number of TX channels to 2, and Slot No. to 1.
Step 4 (Optional) Run the MOD VRET command to modify parameter settings for a VRET MO. In
this step, set the DEVICENAME and SUBUNITQUANTITY parameters to appropriate
values. The default value of the SUBUNITQUANTITY parameter is 8.
Note that the value of the DEVICENO parameter must be the same as the value of the
VRETNO parameter for the previously added AAS.
Step 5 Run the MOD VRETSUBUNIT command to configure virtual RET subunit 1. In this step:
l Set the PORTNUM parameter to 4.
l Set all of the POLARTYPE1, POLARTYPE2, POLARTYPE3, and POLARTYPE4
parameters to POSITIVE_NEGATIVE_45(POSITIVE_NEGATIVE_45).
Step 6 Run the ADD SECTOR command to associate virtual RET subunits with sectors. In this step:
l For sector 0:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 1.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 1, respectively.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 61


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

l For sector 1:
Set the ANTNUM parameter to the value of the PORTNUM parameter for virtual RET
subunit 2.
Set the ANT1N and ANT2N parameters to the values of the CONNPN1 and CONNPN2
parameters for virtual RET subunit 2, respectively.
Step 7 Run the ADD SECTOREQM command to add sector equipment.

Step 8 Run the ADD CELL command to add a 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.6.4.5.5 MML Command Examples


//Adding an RRU chain or ring
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0;
//Adding an AAS to the RRU chain or ring
ADD AAS: CN=0, SRN=60, TP=TRUNK, RCN=0, PS=0, AN="AAS";
//Adding an AARU
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 MO
MOD VRET: DEVICENO=60, DEVICENAME="VRET", SUBUNITQUANTITY=8;
//Modifying the configurations of virtual RET subunit 1
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=1, PORTNUM=2, CONNPN1=R0A, CONNPN2=R0B,
ULTILT=40, DLTILT=40;
//Modifying the configurations of virtual RET subunit 2
MOD VRETSUBUNIT: DEVICENO=60, SUBUNITNO=2, PORTNUM=2, CONNPN1=R1A, CONNPN2=R1B,
ULTILT=90, DLTILT=90;
//Adding two sectors
ADD SECTOR: SECTORID=10, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R0A,
ANT2CN=0, ANT2SRN=60, ANT2SN=3, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=11, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=3, ANT1N=R1A,
ANT2CN=0, ANT2SRN=60, ANT2SN=3, ANT2N=R1B, CREATESECTOREQM=FALSE;
//Adding two sets of sector equipment and sector equipment antennas
ADD SECTOREQM: SECTOREQMID=10, SECTORID=10, ANTNUM=2, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=11, SECTORID=11, ANTNUM=2, ANT1CN=0, ANT1SRN=60,
ANT1SN=3, ANT1N=R1A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=3,
ANT2N=R1B, ANTTYPE2=RXTX_MODE;
//Adding operator information for a cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=1, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Adding two cells
ADD CELL: LocalCellId=0, CellName="lte", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1550, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0,
PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,
TxRxMode=2T2R;
ADD CELL: LocalCellId=1, CellName="lte", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1800, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=1,
PhyCellId=1, FddTddInd=CELL_FDD, RootSequenceIdx=1,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, CrsPortNum=CRS_PORT_2,

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 62


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

TxRxMode=2T2R;
//Adding relationships between the cells and the sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=10;
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=11;
//Setting the cell power parameters
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=122, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB3_P_A;
MOD PDSCHCFG: LocalCellId=1, ReferenceSignalPwr=122, Pb=1;
MOD CELLDLPCPDSCHPA: LocalCellId=1, PaPcOff=DB3_P_A;
//Activating the cells
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1;

NOTE

1. VRETNO and DEVICENO are used for the same object and their values must be identical.
2. VRETSUBUNIT provides the RET configuration for a port, which must be identical with the
RX/TX port in SECTOREQM.
3. When the AAU3902 is working in multiple modes, all the AARUs must be configured on each
working mode and the working mode of each AARU must be set according to the actual situation.
Otherwise, services will be interrupted. For example, when an AAU3902 is working in 1800 MHz
(LO) and 2100 MHz (UO) bands, all AARUs of the AAU must be configured on both the UMTS
and LTE sides and the working mode of the AARUs must be set to UL.

10.6.4.6 Activation Observation


Perform the following operations after the Dividual Tilts by Carrier feature was activated:
l Check whether any alarms were falsely generated.
l Run the DSP VRETSUBUNIT, DSP SECTOR, and DSP CELL commands to query
the status of virtual RET subunits, sectors, and cells, respectively.

10.6.5 Performance Monitoring


After feature activation, check the values of the counters listed in Table 10-14 to determine
performance gains provided by this feature.

Table 10-14 Counters to query


Counter Name Formula

RRC Setup Success Rate Number of successful RRC connection setups in a cell/
Number of RRC connection setup attempts in a cell = L.RRC
ConnReq.Succ/L.RRC.ConnSetup x 100%

eRAB Setup Success Number of successful E-RAB setups in a cell/Number of E-


Rate RAB setup attempts in a cell = L.E-RAB.SuccEst/L.E-
RAB.AttEst x 100%

Intra-Freq HO Success (Number of successful intra-eNodeB outgoing handovers in a


Rate cell + Number of successful inter-eNodeB outgoing handovers
in a cell)/(Number of intra-eNodeB outgoing handovers
executions in a cell + Number of inter-eNodeB outgoing
handovers executions in a cell) =
(L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 63


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Counter Name Formula

Call Drop Rate Number of abnormal E-RAB releases in a cell/(Number of


abnormal E-RAB releases in a cell + Number of normal E-
RAB releases in a cell) = L.E-RAB.AbnormRel/(L.E-
RAB.AbnormRel + L.E-RAB.NormRel) x 100%

10.6.6 Parameter Optimization


Parameters are optimized in the same way as that for the common sites. After this feature is
enabled, downtilt angles of carriers can be independently adjusted. If the call completion rate,
call drop rate, or handover success rate deteriorates, adjust the downlink downtilt angles of
carriers.

10.6.7 Possible Issues


l Fault symptom
KPIs deteriorate after this feature is enabled.
l Solution
Observe the KPIs after this feature is enabled. If KPIs deteriorate, take the same KPI
optimization method as that in common sites.

10.7 Deployment of AAS RAT Specific Tilting (LTE)

10.7.1 Application Suggestions


This feature is recommended if the following conditions are all met:
l Multiple RATs work concurrently on the AAU3902.
l Cells using different RATs need to be configured with different downtilt angles.

10.7.2 Required Information


l 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.7.3 Planning
RF Planning
Perform RF planning according to the principles for each RAT.

Network Planning
Perform network planning according to the principles for each RAT.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 64


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Hardware Planning
The AAU3902 must be configured.

10.7.4 Deployment

10.7.4.1 Requirements
Purchase the license for AAS RAT Specific Tilting (LTE).

10.7.4.2 Data Preparation


For 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.
For the parameters that must be set in a Cell MO, see Table 10-12.

10.7.4.3 Precautions
The downtilt angle difference between AAS beams is restricted by the maximum capability of
the digital tilt (DT). All such differences among features or within any features comply with
this restriction. For more information, see "Technical Specifications of AAUs" in 3900 Series
Base Station Technical Description.

10.7.4.4 Hardware Adjustment


For details, see AAU3902 Installation Guide.

10.7.4.5 Initial Configuration


For details, see 10.6.4.5 Initial Configuration.

10.7.4.6 Activation Observation


Perform the following operations after the Dividual Tilts by Carrier feature was activated:
l Check whether any alarms were falsely generated.
l Run the DSP VRETSUBUNIT, DSP SECTOR, and DSP CELL commands to query
the status of virtual RET subunits, sectors, and cells, respectively.

10.7.5 Performance Monitoring


After feature activation, check the values of the counters listed in Table 10-15 to determine
performance gains provided by this feature.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 65


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 10 Engineering Guidelines

Table 10-15 Counters to query


Counter Name Formula

RRC Setup Success Rate Number of successful RRC connection setups in a cell/
Number of RRC connection setup attempts in a cell = L.RRC
ConnReq.Succ/L.RRC.ConnSetup x 100%

eRAB Setup Success Number of successful E-RAB setups in a cell/Number of E-


Rate RAB setup attempts in a cell = L.E-RAB.SuccEst/L.E-
RAB.AttEst x 100%

Intra-Freq HO Success Intra-Freq HO Success Rate =


Rate (L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut) x 100%

Call Drop Rate Number of abnormal E-RAB releases in a cell/(Number of


abnormal E-RAB releases in a cell + Number of normal E-
RAB releases in a cell) = L.E-RAB.AbnormRel/(L.E-
RAB.AbnormRel + L.E-RAB.NormRel) x 100%

10.7.6 Parameter Optimization


If the call completion rate, call drop rate, or handover success rate deteriorates, adjust the
downlink downtilt angles of carriers.

10.7.7 Possible Issues


l Fault symptom
The feature fails to be enabled or this feature is configured but is ineffective.
l Solution
– Check whether the same AAS is configured with any feature that is mutually
exclusive with this feature. For details, see 8 Related Features.
– Check whether ALM-26532 RF Unit Hardware Fault is generated on the same
AAS. If so, the AAS RAT Specific Tilting (LTE) feature fails to be enabled.

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 66


Copyright © Huawei Technologies Co., Ltd.
eRAN
AAS Feature Parameter Description 11 Reference Documents

11 Reference Documents

1. ALD Management Feature Parameter Description


2. Cell Management Feature Parameter Description
3. MIMO Feature Parameter Description

Issue 01 (2017-03-10) Huawei Proprietary and Confidential 67


Copyright © Huawei Technologies Co., Ltd.